[Touch-packages] [Bug 2059856]
Fixed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/2059856
Title:
gdb 10.0 fails to examine any global variables in D programs
Status in gdb:
Fix Released
Status in gdb package in Ubuntu:
New
Bug description:
[ Impact ]
* GDB 10.0 introduced a regression where it cannot inspect any global
variables in any D programs compiled by any D compiler.
* LDC2 and GDC upstream stated Focal does not have such a problem and stuck
to this release for their test images.
[ Test Plan ]
Considering the following D program:
```
module t;
class uv {
int i;
}
__gshared uv i;
int main() {
i = new uv();
return 0; // #break
}
```
If you build it using `gdc -g -O0 t.d -o t` or `ldc2 -o t.o t.d -g`,
run the GDB using the following commands ...
```
b t.d:10
p t.i
```
... you will notice GDB will complain that "'t.i' has unknown type;
cast it to its declared type."
[ Where problems could occur ]
* The fix consists of a single line change to the demangler. The worst-case
scenario would be breaking the demangling functionality of other programming
languages. However, the newer D ABI uses a symbol mangling scheme that is very
difficult to confuse with other programming languages.
* Incorrect symbol de-mangling may also cause user confusion. However, the
patch fixed a fundamental usability issue.
[ Other Info ]
* Initial discussion in the LDC2 bug tracker:
https://github.com/ldc-developers/ldc/issues/4389
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/2059856/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1982693] Re: USB-Audio device UMC204HD disappears after suspend
I have in the meantime switched to a new PC and this problem doesn't occur any more. Sorry I cannot be of help. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1982693 Title: USB-Audio device UMC204HD disappears after suspend Status in alsa-driver package in Ubuntu: New Bug description: Coming back from sleep, Behringer UMC204HD is not in the list of devices in Settings > Sound. It comes back if I unplug and plug back in. I tried with/without a USB hub in between, I tried setting "usbcore.autosuspend=-1". No help. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 24 15:04:57 2022 InstallationDate: Installed on 2022-04-21 (93 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:U192k successful Symptom_Card: HD Webcam C525 - HD Webcam C525 Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [USB-Audio - UMC204HD 192k, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.H0 dmi.board.asset.tag: Default string dmi.board.name: H110M PRO-VH (MS-7996) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.H0:bd06/16/2018:br5.12:svnMSI:pnMS-7996:pvr1.0:rvnMSI:rnH110MPRO-VH(MS-7996):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7996 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1982693/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399945] Re: Settings, Preferences, ect. - All keyboard input is added twice
** Changed in: winff (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1399945 Title: Settings, Preferences, ect. - All keyboard input is added twice Status in Winff: Unknown Status in ibus package in Ubuntu: New Status in winff package in Ubuntu: Fix Released Bug description: Test Case: Open winff Try to edit or add something using keyboard. All characters are doubled Screen shows attempt to add /Videos to Output Folder box ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: winff 1.5.3-4ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.15-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Dec 6 10:32:03 2014 InstallationDate: Installed on 2014-11-16 (20 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141114) PackageArchitecture: all SourcePackage: winff UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/winff/+bug/1399945/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037879] [NEW] package initramfs-tools 0.140ubuntu13.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported:
i got this bug, when iam trying install apps through terminal
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: initramfs-tools 0.140ubuntu13.4
ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-33-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
AptOrdering:
fuse:amd64: Remove
fuse3:amd64: Install
gnome-remote-desktop:amd64: Install
gnome-control-center:amd64: Install
NULL: ConfigurePending
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
Date: Sun Oct 1 14:42:33 2023
DpkgHistoryLog:
Start-Date: 2023-10-01 14:42:29
Commandline: apt install gnome-control-center
Requested-By: avinash (1000)
Install: gnome-remote-desktop:amd64 (42.9-0ubuntu0.22.04.1, automatic),
fuse3:amd64 (3.10.5-1build1, automatic), gnome-control-center:amd64
(1:41.7-0ubuntu0.22.04.7)
Remove: fuse:amd64 (2.9.9-5ubuntu3)
ErrorMessage: subprocess installed post-installation script returned error exit
status 1
InstallationDate: Installed on 2023-09-17 (13 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
PackageArchitecture: all
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal,
3.10.6-1~22.04
PythonDetails: N/A
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.140ubuntu13.4 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-package jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2037879
Title:
package initramfs-tools 0.140ubuntu13.4 failed to install/upgrade:
subprocess installed post-installation script returned error exit
status 1
Status in initramfs-tools package in Ubuntu:
New
Bug description:
i got this bug, when iam trying install apps through terminal
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: initramfs-tools 0.140ubuntu13.4
ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-33-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
AptOrdering:
fuse:amd64: Remove
fuse3:amd64: Install
gnome-remote-desktop:amd64: Install
gnome-control-center:amd64: Install
NULL: ConfigurePending
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
Date: Sun Oct 1 14:42:33 2023
DpkgHistoryLog:
Start-Date: 2023-10-01 14:42:29
Commandline: apt install gnome-control-center
Requested-By: avinash (1000)
Install: gnome-remote-desktop:amd64 (42.9-0ubuntu0.22.04.1, automatic),
fuse3:amd64 (3.10.5-1build1, automatic), gnome-control-center:amd64
(1:41.7-0ubuntu0.22.04.7)
Remove: fuse:amd64 (2.9.9-5ubuntu3)
ErrorMessage: subprocess installed post-installation script returned error
exit status 1
InstallationDate: Installed on 2023-09-17 (13 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
PackageArchitecture: all
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal,
3.10.6-1~22.04
PythonDetails: N/A
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.140ubuntu13.4 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2037879/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399945] Re: Settings, Preferences, ect. - All keyboard input is added twice
gtk package dropped in 1.5.5-10 Please re-open if seen in the qt package ** Changed in: winff (Ubuntu) Status: New => Fix Committed -- 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/1399945 Title: Settings, Preferences, ect. - All keyboard input is added twice Status in Winff: Unknown Status in ibus package in Ubuntu: New Status in winff package in Ubuntu: Fix Committed Bug description: Test Case: Open winff Try to edit or add something using keyboard. All characters are doubled Screen shows attempt to add /Videos to Output Folder box ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: winff 1.5.3-4ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.15-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Dec 6 10:32:03 2014 InstallationDate: Installed on 2014-11-16 (20 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141114) PackageArchitecture: all SourcePackage: winff UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/winff/+bug/1399945/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2028410] [NEW] Random Logout Bug
Public bug reported: While using my computer, since switching to Nouveou driver I get randomly logged out. I used to use the NVidia drivers, but a few months back I could no longer connect to my external monitor. The Nouveou driver works beautifully, except for this random logout bug. This other bug I filed https://bugs.launchpad.net/ubuntu/+source/linux- signed-lowlatency/+bug/2026652, may or may not be related. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-1007.7-lowlatency 6.2.12 Uname: Linux 6.2.0-1007-lowlatency x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 21 15:01:00 2023 DistUpgraded: 2023-04-26 12:00:46,209 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:3ffb] InstallationDate: Installed on 2021-12-18 (580 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE Device(8910) Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81T2 ProcEnviron: LANG=en_CA.UTF-8 LANGUAGE=en_CA:en PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1007-lowlatency root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash nouveau.debug=debug vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to lunar on 2023-04-26 (86 days ago) dmi.bios.date: 05/24/2022 dmi.bios.release: 1.45 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y545 PG0 dmi.ec.firmware.release: 1.45 dmi.modalias: dmi:bvnLENOVO:bvrBHCN45WW:bd05/24/2022:br1.45:efr1.45:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0: dmi.product.family: Legion Y545 PG0 dmi.product.name: 81T2 dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0 dmi.product.version: Legion Y545 PG0 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar 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/2028410 Title: Random Logout Bug Status in xorg package in Ubuntu: New Bug description: While using my computer, since switching to Nouveou driver I get randomly logged out. I used to use the NVidia drivers, but a few months back I could no longer connect to my external monitor. The Nouveou driver works beautifully, except for this random logout bug. This other bug I filed https://bugs.launchpad.net/ubuntu/+source/linux-signed- lowlatency/+bug/2026652, may or may not be related. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-1007.7-lowlatency 6.2.12 Uname: Linux 6.2.0-1007-lowlatency x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 21 15:01:00 2023 DistUpgraded: 2023-04-26 12:00:46,209 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Ma
[Touch-packages] [Bug 1980679] Re: Suspend on focal takes 30s.
It got fixed even before I rebooted; so installing that package changed config files, and indeed I see this: # /usr/lib/systemd/logind.conf.d/unattended-upgrades-logind-maxdelay.conf [Login] # delay InhibitDelayMaxSec=2 Not sure why it was set to 30s... -- 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/1980679 Title: Suspend on focal takes 30s. Status in systemd package in Ubuntu: Invalid Status in xfce4-power-manager package in Ubuntu: New Bug description: Just upgrades my NUC from Bionic to Focal and suspend went from immediate (within a couple seconds) to taking a whole 30 seconds. While suspend is happening, the machine is still usable, mouse moves, applications respond, all the way until the machine actually goes to sleep. I don't see anything strange in kern.log that would explain the slowness: Jul 4 08:44:55 domi kernel: [342379.045479] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:44:55 domi kernel: [342379.048878] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:44:55 domi kernel: [342379.049670] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:44:56 domi kernel: [342379.966129] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:44:56 domi kernel: [342379.971410] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:45:27 domi kernel: [342410.725869] PM: suspend entry (s2idle) Jul 4 08:45:32 domi kernel: [342410.749912] Filesystems sync: 0.024 seconds Jul 4 08:45:32 domi kernel: [342410.751470] Freezing user space processes ... (elapsed 0.002 seconds) done. Jul 4 08:45:32 domi kernel: [342410.753907] OOM killer disabled. Jul 4 08:45:32 domi kernel: [342410.753907] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jul 4 08:45:32 domi kernel: [342410.755259] printk: Suspending console(s) (use no_console_suspend to debug) Jul 4 08:45:32 domi kernel: [342410.755948] e1000e: EEE TX LPI TIMER: 0011 Jul 4 08:45:32 domi kernel: [342410.812587] sd 2:0:0:0: [sdb] Synchronizing SCSI cache Jul 4 08:45:32 domi kernel: [342410.812607] sd 1:0:0:0: [sda] Synchronizing SCSI cache Jul 4 08:45:32 domi kernel: [342410.812708] sd 2:0:0:0: [sdb] Stopping disk Jul 4 08:45:32 domi kernel: [342410.816870] sd 1:0:0:0: [sda] Stopping disk Jul 4 08:45:32 domi kernel: [342411.080056] ACPI: EC: interrupt blocked Jul 4 08:45:32 domi kernel: [342415.597918] ACPI: EC: interrupt unblocked There does look to be 30s between the last "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7" and "PM: suspend entry (s2idle)" This is mostly a frustration, but could be a security issue for some if they suspend the machine and walk away thinking it would be locked but is usable for another 30s. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-121-generic 5.4.0-121.137 ProcVersionSignature: Ubuntu 5.4.0-121.137-generic 5.4.189 Uname: Linux 5.4.0-121-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bbogart1033 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Jul 4 08:43:09 2022 InstallationDate: Installed on 2019-02-09 (1241 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Intel(R) Client Systems NUC8i3BEH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-121-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-121-generic N/A linux-backports-modules-5.4.0-121-generic N/A linux-firmware 1.187.31 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2022-06-30 (4 days ago) dmi.bios.date: 10/15/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0051.2018.1015.1513 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1980679/+subscriptions -- Mailing list: https://launchpad.n
[Touch-packages] [Bug 1980679] Re: Suspend on focal takes 30s.
This issue disappeared after installing linux-generic-hwe-20.04 due to another bug. -- 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/1980679 Title: Suspend on focal takes 30s. Status in systemd package in Ubuntu: Invalid Status in xfce4-power-manager package in Ubuntu: New Bug description: Just upgrades my NUC from Bionic to Focal and suspend went from immediate (within a couple seconds) to taking a whole 30 seconds. While suspend is happening, the machine is still usable, mouse moves, applications respond, all the way until the machine actually goes to sleep. I don't see anything strange in kern.log that would explain the slowness: Jul 4 08:44:55 domi kernel: [342379.045479] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:44:55 domi kernel: [342379.048878] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:44:55 domi kernel: [342379.049670] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:44:56 domi kernel: [342379.966129] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:44:56 domi kernel: [342379.971410] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:45:27 domi kernel: [342410.725869] PM: suspend entry (s2idle) Jul 4 08:45:32 domi kernel: [342410.749912] Filesystems sync: 0.024 seconds Jul 4 08:45:32 domi kernel: [342410.751470] Freezing user space processes ... (elapsed 0.002 seconds) done. Jul 4 08:45:32 domi kernel: [342410.753907] OOM killer disabled. Jul 4 08:45:32 domi kernel: [342410.753907] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jul 4 08:45:32 domi kernel: [342410.755259] printk: Suspending console(s) (use no_console_suspend to debug) Jul 4 08:45:32 domi kernel: [342410.755948] e1000e: EEE TX LPI TIMER: 0011 Jul 4 08:45:32 domi kernel: [342410.812587] sd 2:0:0:0: [sdb] Synchronizing SCSI cache Jul 4 08:45:32 domi kernel: [342410.812607] sd 1:0:0:0: [sda] Synchronizing SCSI cache Jul 4 08:45:32 domi kernel: [342410.812708] sd 2:0:0:0: [sdb] Stopping disk Jul 4 08:45:32 domi kernel: [342410.816870] sd 1:0:0:0: [sda] Stopping disk Jul 4 08:45:32 domi kernel: [342411.080056] ACPI: EC: interrupt blocked Jul 4 08:45:32 domi kernel: [342415.597918] ACPI: EC: interrupt unblocked There does look to be 30s between the last "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7" and "PM: suspend entry (s2idle)" This is mostly a frustration, but could be a security issue for some if they suspend the machine and walk away thinking it would be locked but is usable for another 30s. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-121-generic 5.4.0-121.137 ProcVersionSignature: Ubuntu 5.4.0-121.137-generic 5.4.189 Uname: Linux 5.4.0-121-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bbogart1033 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Jul 4 08:43:09 2022 InstallationDate: Installed on 2019-02-09 (1241 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Intel(R) Client Systems NUC8i3BEH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-121-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-121-generic N/A linux-backports-modules-5.4.0-121-generic N/A linux-firmware 1.187.31 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2022-06-30 (4 days ago) dmi.bios.date: 10/15/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0051.2018.1015.1513 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1980679/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799265] Re: avahi-daemon high cpu, unusable networking
Hi, I'm wondering if the fix for this is https://github.com/lathiat/avahi/pull/366 and whether or not that fix can be SRU'd into Jammy, which uses avahi 0.8-5ubuntu5.1 ? That patch was already pulled in to 0.8-6 (https://salsa.debian.org/utopia- team/avahi/-/commit/cf97e08b52cd2194c4f7a516c3929ea79d39696a) which is included in Kinetic+. Thanks for considering this :) -- 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/1799265 Title: avahi-daemon high cpu, unusable networking Status in Avahi: New Status in avahi package in Ubuntu: Triaged Bug description: Currently running Kubuntu 18.10, Dell XPS 13 9350 Since updating from Kubuntu 18.04 to 18.10, the avahi-daemon has been consistently hampering network performance and using CPU for long periods of time. When booting machine from off state, avahi-daemon uses an entire CPU at max load for approx 10 minutes. During this time, internet connectivity via wifi is essentially unusable. The wifi connection is good, but it seems that http transactions are cutoff mid-way so no webpage is able to load. When waking from sleep, the avahi-daemon causes similar symptoms, but with less than 1 full cpu usage, and with somewhat less degraded network performance, but still quite unusable. I have never had issues with avahi prior to the 18.10 upgrade, so I am fairly confident the issue is rooted in that change. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: avahi-daemon 0.7-4ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: KDE Date: Mon Oct 22 10:00:34 2018 InstallationDate: Installed on 2017-07-24 (455 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LD_PRELOAD= SHELL=/bin/bash SourcePackage: avahi UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/avahi/+bug/1799265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1980679] Re: Suspend on focal takes 30s.
** Attachment added: "systemd-inhibit output" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1980679/+attachment/5682590/+files/systemd-inhibit -- 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/1980679 Title: Suspend on focal takes 30s. Status in systemd package in Ubuntu: Incomplete Bug description: Just upgrades my NUC from Bionic to Focal and suspend went from immediate (within a couple seconds) to taking a whole 30 seconds. While suspend is happening, the machine is still usable, mouse moves, applications respond, all the way until the machine actually goes to sleep. I don't see anything strange in kern.log that would explain the slowness: Jul 4 08:44:55 domi kernel: [342379.045479] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:44:55 domi kernel: [342379.048878] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:44:55 domi kernel: [342379.049670] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:44:56 domi kernel: [342379.966129] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:44:56 domi kernel: [342379.971410] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:45:27 domi kernel: [342410.725869] PM: suspend entry (s2idle) Jul 4 08:45:32 domi kernel: [342410.749912] Filesystems sync: 0.024 seconds Jul 4 08:45:32 domi kernel: [342410.751470] Freezing user space processes ... (elapsed 0.002 seconds) done. Jul 4 08:45:32 domi kernel: [342410.753907] OOM killer disabled. Jul 4 08:45:32 domi kernel: [342410.753907] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jul 4 08:45:32 domi kernel: [342410.755259] printk: Suspending console(s) (use no_console_suspend to debug) Jul 4 08:45:32 domi kernel: [342410.755948] e1000e: EEE TX LPI TIMER: 0011 Jul 4 08:45:32 domi kernel: [342410.812587] sd 2:0:0:0: [sdb] Synchronizing SCSI cache Jul 4 08:45:32 domi kernel: [342410.812607] sd 1:0:0:0: [sda] Synchronizing SCSI cache Jul 4 08:45:32 domi kernel: [342410.812708] sd 2:0:0:0: [sdb] Stopping disk Jul 4 08:45:32 domi kernel: [342410.816870] sd 1:0:0:0: [sda] Stopping disk Jul 4 08:45:32 domi kernel: [342411.080056] ACPI: EC: interrupt blocked Jul 4 08:45:32 domi kernel: [342415.597918] ACPI: EC: interrupt unblocked There does look to be 30s between the last "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7" and "PM: suspend entry (s2idle)" This is mostly a frustration, but could be a security issue for some if they suspend the machine and walk away thinking it would be locked but is usable for another 30s. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-121-generic 5.4.0-121.137 ProcVersionSignature: Ubuntu 5.4.0-121.137-generic 5.4.189 Uname: Linux 5.4.0-121-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bbogart1033 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Jul 4 08:43:09 2022 InstallationDate: Installed on 2019-02-09 (1241 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Intel(R) Client Systems NUC8i3BEH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-121-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-121-generic N/A linux-backports-modules-5.4.0-121-generic N/A linux-firmware 1.187.31 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2022-06-30 (4 days ago) dmi.bios.date: 10/15/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0051.2018.1015.1513 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1980679/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launc
[Touch-packages] [Bug 1980679] Re: Suspend on focal takes 30s.
Related? # /usr/lib/systemd/logind.conf.d/unattended-upgrades-logind-maxdelay.conf [Login] # delay InhibitDelayMaxSec=30 -- 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/1980679 Title: Suspend on focal takes 30s. Status in systemd package in Ubuntu: Incomplete Bug description: Just upgrades my NUC from Bionic to Focal and suspend went from immediate (within a couple seconds) to taking a whole 30 seconds. While suspend is happening, the machine is still usable, mouse moves, applications respond, all the way until the machine actually goes to sleep. I don't see anything strange in kern.log that would explain the slowness: Jul 4 08:44:55 domi kernel: [342379.045479] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:44:55 domi kernel: [342379.048878] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:44:55 domi kernel: [342379.049670] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:44:56 domi kernel: [342379.966129] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:44:56 domi kernel: [342379.971410] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:45:27 domi kernel: [342410.725869] PM: suspend entry (s2idle) Jul 4 08:45:32 domi kernel: [342410.749912] Filesystems sync: 0.024 seconds Jul 4 08:45:32 domi kernel: [342410.751470] Freezing user space processes ... (elapsed 0.002 seconds) done. Jul 4 08:45:32 domi kernel: [342410.753907] OOM killer disabled. Jul 4 08:45:32 domi kernel: [342410.753907] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jul 4 08:45:32 domi kernel: [342410.755259] printk: Suspending console(s) (use no_console_suspend to debug) Jul 4 08:45:32 domi kernel: [342410.755948] e1000e: EEE TX LPI TIMER: 0011 Jul 4 08:45:32 domi kernel: [342410.812587] sd 2:0:0:0: [sdb] Synchronizing SCSI cache Jul 4 08:45:32 domi kernel: [342410.812607] sd 1:0:0:0: [sda] Synchronizing SCSI cache Jul 4 08:45:32 domi kernel: [342410.812708] sd 2:0:0:0: [sdb] Stopping disk Jul 4 08:45:32 domi kernel: [342410.816870] sd 1:0:0:0: [sda] Stopping disk Jul 4 08:45:32 domi kernel: [342411.080056] ACPI: EC: interrupt blocked Jul 4 08:45:32 domi kernel: [342415.597918] ACPI: EC: interrupt unblocked There does look to be 30s between the last "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7" and "PM: suspend entry (s2idle)" This is mostly a frustration, but could be a security issue for some if they suspend the machine and walk away thinking it would be locked but is usable for another 30s. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-121-generic 5.4.0-121.137 ProcVersionSignature: Ubuntu 5.4.0-121.137-generic 5.4.189 Uname: Linux 5.4.0-121-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bbogart1033 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Jul 4 08:43:09 2022 InstallationDate: Installed on 2019-02-09 (1241 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Intel(R) Client Systems NUC8i3BEH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-121-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-121-generic N/A linux-backports-modules-5.4.0-121-generic N/A linux-firmware 1.187.31 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2022-06-30 (4 days ago) dmi.bios.date: 10/15/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0051.2018.1015.1513 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1980679/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1980679] Re: Suspend on focal takes 30s.
Yes, there is still a delay of 32s between pressing "suspend" and the machine actually going into suspend. See attached systemd-analyze output. ** Attachment added: "Output of systemd-analyze cat-config systemd/logind.conf" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1980679/+attachment/5682587/+files/systemd-analyze -- 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/1980679 Title: Suspend on focal takes 30s. Status in systemd package in Ubuntu: Incomplete Bug description: Just upgrades my NUC from Bionic to Focal and suspend went from immediate (within a couple seconds) to taking a whole 30 seconds. While suspend is happening, the machine is still usable, mouse moves, applications respond, all the way until the machine actually goes to sleep. I don't see anything strange in kern.log that would explain the slowness: Jul 4 08:44:55 domi kernel: [342379.045479] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:44:55 domi kernel: [342379.048878] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:44:55 domi kernel: [342379.049670] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:44:56 domi kernel: [342379.966129] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:44:56 domi kernel: [342379.971410] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Jul 4 08:45:27 domi kernel: [342410.725869] PM: suspend entry (s2idle) Jul 4 08:45:32 domi kernel: [342410.749912] Filesystems sync: 0.024 seconds Jul 4 08:45:32 domi kernel: [342410.751470] Freezing user space processes ... (elapsed 0.002 seconds) done. Jul 4 08:45:32 domi kernel: [342410.753907] OOM killer disabled. Jul 4 08:45:32 domi kernel: [342410.753907] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jul 4 08:45:32 domi kernel: [342410.755259] printk: Suspending console(s) (use no_console_suspend to debug) Jul 4 08:45:32 domi kernel: [342410.755948] e1000e: EEE TX LPI TIMER: 0011 Jul 4 08:45:32 domi kernel: [342410.812587] sd 2:0:0:0: [sdb] Synchronizing SCSI cache Jul 4 08:45:32 domi kernel: [342410.812607] sd 1:0:0:0: [sda] Synchronizing SCSI cache Jul 4 08:45:32 domi kernel: [342410.812708] sd 2:0:0:0: [sdb] Stopping disk Jul 4 08:45:32 domi kernel: [342410.816870] sd 1:0:0:0: [sda] Stopping disk Jul 4 08:45:32 domi kernel: [342411.080056] ACPI: EC: interrupt blocked Jul 4 08:45:32 domi kernel: [342415.597918] ACPI: EC: interrupt unblocked There does look to be 30s between the last "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7" and "PM: suspend entry (s2idle)" This is mostly a frustration, but could be a security issue for some if they suspend the machine and walk away thinking it would be locked but is usable for another 30s. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-121-generic 5.4.0-121.137 ProcVersionSignature: Ubuntu 5.4.0-121.137-generic 5.4.189 Uname: Linux 5.4.0-121-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bbogart1033 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Jul 4 08:43:09 2022 InstallationDate: Installed on 2019-02-09 (1241 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Intel(R) Client Systems NUC8i3BEH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-121-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-121-generic N/A linux-backports-modules-5.4.0-121-generic N/A linux-firmware 1.187.31 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2022-06-30 (4 days ago) dmi.bios.date: 10/15/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0051.2018.1015.1513 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1980679/+subscriptions -- Mailin
[Touch-packages] [Bug 1922047]
> kept scrolling too long after releasing this is probably another thing in gtk, kinetic scrolling stops after you put a finger on the touchpad (zwp_pointer_gesture_hold_v1 event), but in firefox it doesn't, you have to wait -- 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/1922047 Title: Touchpad scrolling is too fast Status in Mozilla Firefox: Confirmed Status in GTK+: Fix Released Status in Mutter: New Status in firefox package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: This is an issue which has troubled me for a while. Anecdotally, scrolling feels way too fast in GNOME on Wayland compared to on X11. I finally tested it semi-scientifically, and it seems like GNOME on Wayland scrolls almost exactly 1.5x faster than GNOME on X11. I tested this by testing how many lines are scrolled from a full two- finger touchpad swipe from the bottom of my touchpad to the top of my touchpad, and logged a few attempts in both X and Wayland. I kept track of the results in this spreadsheet: https://docs.google.com/spreadsheets/d/17EaBM5Pgt7GdnnzcN2Vchk4kfT7IZ6i4qZ0zpVRGLhc/edit?usp=sharing I scrolled in one of my own GTK applications (https://github.com/mortie/lograt) because it lets me easily see how many lines I scrolled. Attach is a video of one full scroll on X11 and one full scroll on Wayland. This testing was performed on a Dell XPS 13 9343, but I've also used Ubuntu on a Dell XPS 9575 where GNOME Wayland scrolling also feels way too fast. I don't have other hardware to test on. This has been an issue on both Ubuntu 20.10 and Ubuntu 21.04. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 31 11:44:04 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-21 (495 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-16 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1922047/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922047]
GTK apps scroll the same as Epiphany, Firefox is much faster -- 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/1922047 Title: Touchpad scrolling is too fast Status in Mozilla Firefox: Confirmed Status in GTK+: Fix Released Status in Mutter: New Status in firefox package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: This is an issue which has troubled me for a while. Anecdotally, scrolling feels way too fast in GNOME on Wayland compared to on X11. I finally tested it semi-scientifically, and it seems like GNOME on Wayland scrolls almost exactly 1.5x faster than GNOME on X11. I tested this by testing how many lines are scrolled from a full two- finger touchpad swipe from the bottom of my touchpad to the top of my touchpad, and logged a few attempts in both X and Wayland. I kept track of the results in this spreadsheet: https://docs.google.com/spreadsheets/d/17EaBM5Pgt7GdnnzcN2Vchk4kfT7IZ6i4qZ0zpVRGLhc/edit?usp=sharing I scrolled in one of my own GTK applications (https://github.com/mortie/lograt) because it lets me easily see how many lines I scrolled. Attach is a video of one full scroll on X11 and one full scroll on Wayland. This testing was performed on a Dell XPS 13 9343, but I've also used Ubuntu on a Dell XPS 9575 where GNOME Wayland scrolling also feels way too fast. I don't have other hardware to test on. This has been an issue on both Ubuntu 20.10 and Ubuntu 21.04. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 31 11:44:04 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-21 (495 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-16 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1922047/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1982693] Re: USB-Audio device UMC204HD disappears after suspend
I tried an unbind/bind with the xhci_hcd driver as explained here: https://stackoverflow.com/questions/35605178/ubuntu-sound-network-usb- trouble-after-suspend-how-to-restart It didn't help. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1982693 Title: USB-Audio device UMC204HD disappears after suspend Status in alsa-driver package in Ubuntu: New Bug description: Coming back from sleep, Behringer UMC204HD is not in the list of devices in Settings > Sound. It comes back if I unplug and plug back in. I tried with/without a USB hub in between, I tried setting "usbcore.autosuspend=-1". No help. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 24 15:04:57 2022 InstallationDate: Installed on 2022-04-21 (93 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:U192k successful Symptom_Card: HD Webcam C525 - HD Webcam C525 Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [USB-Audio - UMC204HD 192k, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.H0 dmi.board.asset.tag: Default string dmi.board.name: H110M PRO-VH (MS-7996) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.H0:bd06/16/2018:br5.12:svnMSI:pnMS-7996:pvr1.0:rvnMSI:rnH110MPRO-VH(MS-7996):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7996 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1982693/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1952107] Re: Google Contacts API Deprecated
When will this fix be released also for Ubuntu 22.04 (Jammy Jellyfish)? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Fix Released Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution source package in Bionic: Triaged Status in evolution-data-server source package in Bionic: Triaged Status in evolution source package in Focal: Triaged Status in evolution-data-server source package in Focal: Triaged Status in evolution source package in Impish: Fix Released Status in evolution-data-server source package in Impish: Fix Released Bug description: * Impact The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown * Testcase - use evolution - add a google account - go the contacts section The contacts stored on the google account should be listed, no error should be displayed * Regression potential The patch changes the google contact backend so any potential issue is likely to be with contacts integration. I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1952107] Re: Google Contacts API Deprecated
Hi again Affred and thank you very much for trying to help me. So, firstly,
just to be sure that there is no confusion, the way I configured my google
account in Ubuntu 22.04 is not in Evolution, but in Ubuntu Settings -> Online
Accounts, then Evolution automatically uses that account. In Online Accounts I
ticked all possible things to sync for my google account (including Contacts).
Like I said, entering the app password in Online Accounts is not accepted by
Ubuntu. Then I did, as you said, open the Seahorse app. When I look into that
with the filter set to "Show any" (so that it doeas not filter any entries
out), I see no entry for Address Book. The only entry I see is named "GOA
google credentials for identity account_xx_y" and it has a poassword
field (can be edited after clicking right on the entry and choosing Properties)
like:
{'authorization_code':
<'a'>,
'access_token':
<''>,
'access_token_expires_at': , 'refresh_token':
<'ccc'>}
So there is no password or app password part in the above field. I even
tried to replace that field with {'password': <''>},
where ee...ee will be the app password, or directly with ee...eee, but
no luck.
Any other suggestions please? Thank you very much.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1952107
Title:
Google Contacts API Deprecated
Status in evolution-data-server:
Fix Released
Status in evolution package in Ubuntu:
Fix Released
Status in evolution-data-server package in Ubuntu:
Fix Released
Status in evolution source package in Bionic:
Triaged
Status in evolution-data-server source package in Bionic:
Triaged
Status in evolution source package in Focal:
Triaged
Status in evolution-data-server source package in Focal:
Triaged
Status in evolution source package in Impish:
Fix Released
Status in evolution-data-server source package in Impish:
Fix Released
Bug description:
* Impact
The google contacts integration with the GNOME component will stop working
since it relies on an API which is going to be shutdown
* Testcase
- use evolution
- add a google account
- go the contacts section
The contacts stored on the google account should be listed, no error
should be displayed
* Regression potential
The patch changes the google contact backend so any potential issue is likely
to be with contacts integration.
I opened Evolution today and a red banner appeared on top with the
following message:
> Failed to connect address book “ : Contacts”
> Invalid request URI or header, or unsupported nonstandard parameter:
Contacts API is being deprecated. Migrate to People API to retain
programmatic access to Google Contacts. See
https://developers.google.com/people/contacts-api-migration.
I found the upstream bug report for this[0], which references the commit[1]
that fixes it.
However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has
3.40.4-1. Is it possible to backport this commit so that Evolution will
continue to work properly?
[0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658
[1]:
https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1952107] Re: Google Contacts API Deprecated
Hi Alfred, I did create a app password in the Google account (I had to enable the 2-step veryfication before doing it), but Gnome, in its Online Contacts, does not accept my app password for the google account, instead only the real google account password. Any instructions please about how you configured Evolution (or Gnome) to use the app password? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Fix Released Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution source package in Bionic: Triaged Status in evolution-data-server source package in Bionic: Triaged Status in evolution source package in Focal: Triaged Status in evolution-data-server source package in Focal: Triaged Status in evolution source package in Impish: Fix Released Status in evolution-data-server source package in Impish: Fix Released Bug description: * Impact The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown * Testcase - use evolution - add a google account - go the contacts section The contacts stored on the google account should be listed, no error should be displayed * Regression potential The patch changes the google contact backend so any potential issue is likely to be with contacts integration. I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1952107] Re: Google Contacts API Deprecated
I am on Ubuntu 22.04 with the system up-to-date and Evolution is not retrieving any contacts from google. :( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1952107 Title: Google Contacts API Deprecated Status in evolution-data-server: Fix Released Status in evolution package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution source package in Bionic: Triaged Status in evolution-data-server source package in Bionic: Triaged Status in evolution source package in Focal: Triaged Status in evolution-data-server source package in Focal: Triaged Status in evolution source package in Impish: Fix Released Status in evolution-data-server source package in Impish: Fix Released Bug description: * Impact The google contacts integration with the GNOME component will stop working since it relies on an API which is going to be shutdown * Testcase - use evolution - add a google account - go the contacts section The contacts stored on the google account should be listed, no error should be displayed * Regression potential The patch changes the google contact backend so any potential issue is likely to be with contacts integration. I opened Evolution today and a red banner appeared on top with the following message: > Failed to connect address book “ : Contacts” > Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. I found the upstream bug report for this[0], which references the commit[1] that fixes it. However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 3.40.4-1. Is it possible to backport this commit so that Evolution will continue to work properly? [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658 [1]: https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1971538] Re: My machine as Wi-Fi Hotspot broken after upgrade to 22.04
I seem to be having similar issues. I could connect my android phone for a bit then it just kinda stopped. My Ipad has never been able to join the network. sometimes with an error saying the channel is too busy (fixed that by starting with nmcli and selecting another channel). Otherwise, the Ipad gives the error "unable to join network" (A nice helpful message, thanks apple) All devices can connect to other networks (android hotstpot and wifi router) I've attached my log file if it'll be any help This might be the wrong place to post, but it was the most recent relevant bug report. ** Attachment added: "My Journalctl log file" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+attachment/5601989/+files/log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1971538 Title: My machine as Wi-Fi Hotspot broken after upgrade to 22.04 Status in network-manager package in Ubuntu: Confirmed Bug description: * Impact The hotspot feature fails to forward the data to the clients * Test case - log into an Ubuntu or GNOME session - connect the machine to an eth cable for internet - go to gnome-control-center -> wifi - enable the hotspot from the menu in the headerbar - connect another device to the wifi created -> the client should connect and access to internet work correctly Upon updating to 22.04, none of my machines can use the connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916651] Re: asks about irc user home directory during upgrade
Received this while upgrading from 20.10 to 21.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-passwd in Ubuntu. https://bugs.launchpad.net/bugs/1916651 Title: asks about irc user home directory during upgrade Status in base-passwd package in Ubuntu: Confirmed Status in base-passwd source package in Hirsute: Confirmed Bug description: Upgrading from groovy to hirsuite, base-passwd asks if the `irc` user's home directory should be moved from `/var/run/ircd` to `/run/ircd`. Having no IRC server installed makes this very confusing, but appears harmless (https://askubuntu.com/questions/876975/user-irc-inside-of-default- ubuntu-16-04-server). Possibly caused by https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=946884, but can this not prompt the user for a decision? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: base-passwd 3.5.49 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Feb 23 12:02:59 2021 InstallationDate: Installed on 2019-08-17 (556 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RebootRequiredPkgs: libc6 libc6 libssl1.1 libssl1.1 SourcePackage: base-passwd UpgradeStatus: Upgraded to hirsute on 2021-02-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/1916651/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1173827] Re: Switch gdebi to pkexec
However as gksu is used, why keep policykit-1 as a dependency? Recommended should be enough. I use Devuan and I have to remove "policykit-1" each time, because it worlks perfectly well without. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1173827 Title: Switch gdebi to pkexec Status in gdebi package in Ubuntu: Won't Fix Bug description: Well gksu isn't default installed anymore & 64 bit users run into the su mode deal, gksu-polkit isn't suitable either So makes no sense to keep using gksu in gdebi. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gdebi (not installed) ProcVersionSignature: Ubuntu 3.9.0-0.1-generic 3.9.0-rc8 Uname: Linux 3.9.0-0-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sat Apr 27 22:50:03 2013 InstallationDate: Installed on 2013-04-24 (4 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1173827/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
No longer affects openlp 2.4.0 and 2.4.6, which OpenLP at GitLab has declared a WontFix. Awaiting 2.9.1 (unreleased as of 29 January 2021) for focal-proposed, groovy-proposed, and hirsute-proposed. I's able to get the EL1210-09 fully up by cherrypicking packages appropriate for nVIDIA 390.nn from the focal Repository, post-installation with nouveau. -- 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/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: In Progress Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. We have two changes that help address this: * The first one stops immediately configuring multi-arch siblings (e.g. libc6:i386 when it's configuring libc6:amd64). This was not necessary, and caused all the libc6:i386 failures here. * The second change sort of also supersedes the first one: It just ignores any errors from immediate configuration, relying on the fact that it's checked and rectified at a later point if there are unconfigured packages (which is what made all those failures happen spuriously after having successfully installed everything). [Test case] We have one test case in EIPP format in the Debian bug 973305 which was only helped by the second change, not the first one. Run /usr/lib/apt/planners < eipp.log and check there are no errors. TODO: It's unclear if the APT from proposed installed in the live session will fix the installer, needs investigation, but would make a useful test case. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
I confirm this problem still active in the latest Release ISO images for 20.04.1-LTS. Obviously a regression consistent with the ~vorlon observation(s) -- didn't happen in 19.04 or 19.10. Involves PluginInstall.py failing to find exact versions of several packages, although I's unable to screen-shot prior to Installer terminating. Even with the ~qd0t workaround, openlp crashes on open, which didn't happen on 18.04.4-LTS. Attempted clean install on four partitions: /boot (ext2), 4 GiB swap, /home (ext4), / (ext4) emachines/acer EL1210-09 (Acer DA078L) Advance Micro Devices Athlon 64 LE-1620 (P/N AD1620IAA5DH) nVIDIA nForce 780a MCP (C77 64-bit geForce GPU in northbridge) msi GT610-1GD3-LP (nVIDIA GF119 64-bit GPU, 1 GiB DDR3 VRAM) -- 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/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: In Progress Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. We have two changes that help address this: * The first one stops immediately configuring multi-arch siblings (e.g. libc6:i386 when it's configuring libc6:amd64). This was not necessary, and caused all the libc6:i386 failures here. * The second change sort of also supersedes the first one: It just ignores any errors from immediate configuration, relying on the fact that it's checked and rectified at a later point if there are unconfigured packages (which is what made all those failures happen spuriously after having successfully installed everything). [Test case] We have one test case in EIPP format in the Debian bug 973305 which was only helped by the second change, not the first one. Run /usr/lib/apt/planners < eipp.log and check there are no errors. TODO: It's unclear if the APT from proposed installed in the live session will fix the installer, needs investigation, but would make a useful test case. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find packa
[Touch-packages] [Bug 1773476] Re: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.img-4.8.0 when no corresponding vmlinuz present
Actually would have been a bug against either apt or dpkg, which failed to clean up /var after Kernel package removal. Since upgraded to ubuntu Focal, closing Bug. ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Invalid -- 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/1773476 Title: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.img-4.8.0 when no corresponding vmlinuz present Status in initramfs-tools package in Ubuntu: Invalid Bug description: With LinUX Images/-Extras 4.15.0-22-generic, 4.13.0-43-generic, 4.8.0-58-generic, 4.8.0-56-generic, and 4.4.0-127-generic installed, sudo dpkg-reconfigure linux-firmware returns the following to Console: update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic update-initramfs: Generating /boot/initrd.img-4.13.0-43-generic update-initramfs: Generating /boot/initrd.img-4.8.0-58-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.4.0-127-generic Same configuration report for "Setting up linux-firmware..." with sudo apt(-get) install (--reinstall) linux-firmware and sudo apt-get upgrade linux-firmware. Therefore: Reproducible: Always Steps to reproduce: sudo apt install (--reinstall) linux-firmware or sudo dpkg-reconfigure linux-firmware. Actual results, excepting actually installed Kernel Image packages: update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory Expected results, excepting actually installed Kernel Image packages: No attempt to generate /boot/initrd.img for missing kernels, thus no warnings, errors or fatals. UPDATE: Solved via sudo rm -rf /var/lib/initramfs-tools/4.8.0 && sudo rm -rf /var/lib/initramfs-tools/4.8.0-56. Recommend check for bug(s) in apt and dpkg of which this Bug may be a depend, as automatic housecleaning failed me in this specific case. --- ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: Unity Dependencies: DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-05-17 (373 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: linux-firmware 1.157.19 [origin: unknown] PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-22.24~16.04.1-generic 4.15.17 Tags: xenial third-party-packages Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lp
[Touch-packages] [Bug 1903329] Re: SRU the current 2.48.9 stable update
Hi Brian I've succesfully installed and tested the `librsvg2-*` v2.48.9-1ubuntu0.20.04.1 packages on focal and can confirm that they work as expected for me, meaning i.a. that the bug I suffered from in the previous v2.48.7 is fixed. I've used the CLI `rsvg-convert` as well as the R package rsvg[1] (which uses the C bindings provided by `librsvg2-dev`) to convert SVG images to PDF. Everything was fine, no regression as far as I can tell. Thank you very much, Oliver, Brian and everyone else involved for the SRU work! [1]: https://github.com/jeroen/rsvg#readme ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1903329 Title: SRU the current 2.48.9 stable update Status in librsvg package in Ubuntu: Fix Released Status in librsvg source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, which fixes a number of issues, including a regression[1] since librsvg 2.40.x which was shipped in Ubuntu 16.04. The NEWS file[2] summarizes the relevant changes between Ubuntu 20.04's current librsvg 2.48.7 (that version was also introduced by an SRU back in July[3]) and the current version 2.48.9. The complete list of changes is available on GNOME GitLab[4]. * Test case The update is part of GNOME stable updates[5]. Smoke testing by opening SVG images with eog or importing them with gimp can be performed to ensure there are no regressions. * Regression potential This is a bugfix-only stable micro-release, however librsvg is a core component with a number of reverse dependencies. A combination of autopkgtests and manual smoke testing to try and detect SVG rendering issues should be performed. * Notes about this report This is my first SRU request (and at the same time my first launchpad bug report). I'm not really familiar with the whole SRU process which is why I first asked about it on Ubuntu's official discourse forum[6]. Canonical's Sebastien Bacher encouraged me to open this ticket. I've copied over some parts of the last librsvg SRU ticket[3]. I hope this is fine. Thanks for considering this SRU. [1]: https://gitlab.gnome.org/GNOME/librsvg/-/issues/642 [2]: https://gitlab.gnome.org/GNOME/librsvg/-/blob/librsvg-2.48/NEWS [3]: https://bugs.launchpad.net/bugs/1884326 [4]: https://gitlab.gnome.org/GNOME/librsvg/-/compare/2.48.7...2.48.9 [5]: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [6]: https://discourse.ubuntu.com/t/most-straight-forward-way-to-get- librsvg2-microrelease-update-into-focal-updates/19238 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1903329/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1897369] Re: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)
On my system, I have a consistent Deny on cups-browsed --capable, one example from 281300Z November 2020 being: Nov 28 13:00:24 hotrodgpc-desktop kernel: [ 52.928672] audit: type=1400 audit(1606597224.111:54): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=1496 comm ="cups-browsed" capability=23 capname="sys_nice" I have set cups-browsed to complain mode in AppArmor pending the bugfix. --- ubuntu® 20.04.1-LTS AMD64 AuthenticAMD® Athlon64® 3500+ / 3.3 GiB memory AuthenticAMD® RS780 GPU GNOME 3.36.3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1897369 Title: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE) Status in cups package in Ubuntu: Confirmed Bug description: In Ubuntu 20.04.1 with *cups-browsed* 1.27.4-1, apparmor prevents `/usr/sbin/cups-browsed` to change its nice value. $ sudo dmesg | grep apparmor [541870.509461] audit: type=1400 audit(1600898428.089:60): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=62030 comm="cups-browsed" capability=23 capname="sys_nice" [628298.779668] audit: type=1400 audit(1600984854.115:61): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=66850 comm="cups-browsed" capability=23 capname="sys_nice" [714667.424963] audit: type=1400 audit(1601071220.527:62): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=76828 comm="cups-browsed" capability=23 capname="sys_nice" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1897369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854314] Re: Legacy directory /var/run in /lib/systemd/system/dbus.socket
Unresolved as of this date in Ubuntu 20.04/Mint 20. Regression: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. Manual fix still necessary to remove /var in: /lib/systemd/system/dbus.socket: [Unit] Description=D-Bus System Message Bus Socket [Socket] ListenStream=/run/dbus/system_bus_socket -- 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/1854314 Title: Legacy directory /var/run in /lib/systemd/system/dbus.socket Status in D-Bus: New Status in dbus package in Ubuntu: Fix Committed Status in dbus package in Debian: Fix Released Bug description: dbus/focal-proposed,now 1.12.16-2ubuntu1 amd64 Re(o)curring after each new upgrade of dbus, for quite some time and still... $ dmesg|grep accordingly systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. Originally: $cat /lib/systemd/system/dbus.socket [Unit] Description=D-Bus System Message Bus Socket [Socket] ListenStream=/var/run/dbus/system_bus_socket After change: $cat /lib/systemd/system/dbus.socket [Unit] Description=D-Bus System Message Bus Socket [Socket] ListenStream=/run/dbus/system_bus_socket To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1854314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903329] Re: SRU the current 2.48.9 stable update
** Description changed: * Impact That's the current GNOME stable update, which fixes a number of issues, including a regression[1] since librsvg 2.40.x which was shipped in Ubuntu 16.04. The NEWS file[2] summarizes the relevant changes between Ubuntu 20.04's current librsvg 2.48.7 (that version was also introduced by an SRU back in July[3]) and the current version 2.48.9. The complete list of changes is available on GNOME GitLab[4]. * Test case The update is part of GNOME stable updates[5]. Smoke testing by opening SVG images with eog or importing them with gimp can be performed to ensure there are no regressions. * Regression potential This is a bugfix-only stable micro-release, however librsvg is a core component with a number of reverse dependencies. A combination of autopkgtests and manual smoke testing to try and detect SVG rendering issues should be performed. * Notes about this report This is my first SRU request (and at the same time my first launchpad bug report). I'm not really familiar with the whole SRU process which is why I first asked about it on Ubuntu's official discourse forum[6]. Canonical's Sebastien Bacher encouraged me to open this ticket. I've copied over some parts of the last librsvg SRU ticket[3]. I hope this is fine. Thanks for considering this SRU. - [1]: https://gitlab.gnome.org/GNOME/librsvg/-/issues/642 [2]: https://gitlab.gnome.org/GNOME/librsvg/-/blob/librsvg-2.48/NEWS [3]: https://bugs.launchpad.net/bugs/1884326 [4]: https://gitlab.gnome.org/GNOME/librsvg/-/compare/2.48.7...2.48.9 [5]: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME + + [6]: https://discourse.ubuntu.com/t/most-straight-forward-way-to-get- + librsvg2-microrelease-update-into-focal-updates/19238 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1903329 Title: SRU the current 2.48.9 stable update Status in librsvg package in Ubuntu: Confirmed Bug description: * Impact That's the current GNOME stable update, which fixes a number of issues, including a regression[1] since librsvg 2.40.x which was shipped in Ubuntu 16.04. The NEWS file[2] summarizes the relevant changes between Ubuntu 20.04's current librsvg 2.48.7 (that version was also introduced by an SRU back in July[3]) and the current version 2.48.9. The complete list of changes is available on GNOME GitLab[4]. * Test case The update is part of GNOME stable updates[5]. Smoke testing by opening SVG images with eog or importing them with gimp can be performed to ensure there are no regressions. * Regression potential This is a bugfix-only stable micro-release, however librsvg is a core component with a number of reverse dependencies. A combination of autopkgtests and manual smoke testing to try and detect SVG rendering issues should be performed. * Notes about this report This is my first SRU request (and at the same time my first launchpad bug report). I'm not really familiar with the whole SRU process which is why I first asked about it on Ubuntu's official discourse forum[6]. Canonical's Sebastien Bacher encouraged me to open this ticket. I've copied over some parts of the last librsvg SRU ticket[3]. I hope this is fine. Thanks for considering this SRU. [1]: https://gitlab.gnome.org/GNOME/librsvg/-/issues/642 [2]: https://gitlab.gnome.org/GNOME/librsvg/-/blob/librsvg-2.48/NEWS [3]: https://bugs.launchpad.net/bugs/1884326 [4]: https://gitlab.gnome.org/GNOME/librsvg/-/compare/2.48.7...2.48.9 [5]: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [6]: https://discourse.ubuntu.com/t/most-straight-forward-way-to-get- librsvg2-microrelease-update-into-focal-updates/19238 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1903329/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903329] [NEW] SRU the current 2.48.9 stable update
Public bug reported: * Impact That's the current GNOME stable update, which fixes a number of issues, including a regression[1] since librsvg 2.40.x which was shipped in Ubuntu 16.04. The NEWS file[2] summarizes the relevant changes between Ubuntu 20.04's current librsvg 2.48.7 (that version was also introduced by an SRU back in July[3]) and the current version 2.48.9. The complete list of changes is available on GNOME GitLab[4]. * Test case The update is part of GNOME stable updates[5]. Smoke testing by opening SVG images with eog or importing them with gimp can be performed to ensure there are no regressions. * Regression potential This is a bugfix-only stable micro-release, however librsvg is a core component with a number of reverse dependencies. A combination of autopkgtests and manual smoke testing to try and detect SVG rendering issues should be performed. * Notes about this report This is my first SRU request (and at the same time my first launchpad bug report). I'm not really familiar with the whole SRU process which is why I first asked about it on Ubuntu's official discourse forum[6]. Canonical's Sebastien Bacher encouraged me to open this ticket. I've copied over some parts of the last librsvg SRU ticket[3]. I hope this is fine. Thanks for considering this SRU. [1]: https://gitlab.gnome.org/GNOME/librsvg/-/issues/642 [2]: https://gitlab.gnome.org/GNOME/librsvg/-/blob/librsvg-2.48/NEWS [3]: https://bugs.launchpad.net/bugs/1884326 [4]: https://gitlab.gnome.org/GNOME/librsvg/-/compare/2.48.7...2.48.9 [5]: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Affects: librsvg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1903329 Title: SRU the current 2.48.9 stable update Status in librsvg package in Ubuntu: New Bug description: * Impact That's the current GNOME stable update, which fixes a number of issues, including a regression[1] since librsvg 2.40.x which was shipped in Ubuntu 16.04. The NEWS file[2] summarizes the relevant changes between Ubuntu 20.04's current librsvg 2.48.7 (that version was also introduced by an SRU back in July[3]) and the current version 2.48.9. The complete list of changes is available on GNOME GitLab[4]. * Test case The update is part of GNOME stable updates[5]. Smoke testing by opening SVG images with eog or importing them with gimp can be performed to ensure there are no regressions. * Regression potential This is a bugfix-only stable micro-release, however librsvg is a core component with a number of reverse dependencies. A combination of autopkgtests and manual smoke testing to try and detect SVG rendering issues should be performed. * Notes about this report This is my first SRU request (and at the same time my first launchpad bug report). I'm not really familiar with the whole SRU process which is why I first asked about it on Ubuntu's official discourse forum[6]. Canonical's Sebastien Bacher encouraged me to open this ticket. I've copied over some parts of the last librsvg SRU ticket[3]. I hope this is fine. Thanks for considering this SRU. [1]: https://gitlab.gnome.org/GNOME/librsvg/-/issues/642 [2]: https://gitlab.gnome.org/GNOME/librsvg/-/blob/librsvg-2.48/NEWS [3]: https://bugs.launchpad.net/bugs/1884326 [4]: https://gitlab.gnome.org/GNOME/librsvg/-/compare/2.48.7...2.48.9 [5]: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1903329/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1644995] Re: specific SVG file breaks Ubuntu 16.04 desktop + nautilus
10100727: The recent upgrade of librsvg2-2:i386 and librsvg2-common:i386 (from 2.40.20-2 to (2.40.20-2ubuntu0.1) "broke" the display of card styles Anglo and Gnomeangelo, in the aisleriot "Klondike" solitaire game. By "broke", I mean that the card faces displayed only in part -- elements were missing. Reverting to the previous version solved the issue. ** Attachment added: "Klondike-librsvg.png" https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1644995/+attachment/5396751/+files/Klondike-librsvg.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1644995 Title: specific SVG file breaks Ubuntu 16.04 desktop + nautilus Status in librsvg: Expired Status in librsvg package in Ubuntu: Triaged Bug description: Saving following file on Desktop (Ubuntu 16.04.1) results in: 1. Wallpaper and all icons on the desktop disappear 2. Nautilus starts for ~1sec then breaks with "Floating point exception" I suspect it's related to librsvg. In syslog I have many records similar to this one: kernel: [ 20.076864] traps: nautilus[2270] trap divide error ip:7f63fbddf716 sp:7f63fad3f5b0 error:0 in librsvg-2.so.2.40.13[7f63fbdc9000+35000] Here is the file (I can't even attach it here with Firefox, because it makes it crash): http://www.w3.org/2000/svg"; xmlns:xlink="http://www.w3.org/1999/xlink"; xmlns:ev="http://www.w3.org/2001/xml-events";> https://encrypted-tbn2.gstatic.com/images?q=tbn:ANd9GcRiXhgkC523CD5DIdvfwFl3G_S1Hc3oHzh8NUTXPeRSfYv1i8rA"; result="pattern" width="4" height="4"/> To manage notifications about this bug go to: https://bugs.launchpad.net/librsvg/+bug/1644995/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1884535] [NEW] package network-manager 1.22.10-1ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi
Public bug reported: 20.04 LTS ProblemType: Package DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.3 AptOrdering: libnm0:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 22 13:46:13 2020 DuplicateSignature: package:network-manager:1.22.10-1ubuntu2.1 Setting up libnm0:amd64 (1.22.10-1ubuntu2.1) ... dpkg: error processing package network-manager (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-06-22 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.23 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: network-manager Title: package network-manager 1.22.10-1ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/3 VM6807780 8d657f17-f51d-480d-8ae2-241c4030a964 /org/freedesktop/NetworkManager/ActiveConnection/1 enp3s0 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1884535 Title: package network-manager 1.22.10-1ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in network-manager package in Ubuntu: New Bug description: 20.04 LTS ProblemType: Package DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.3 AptOrdering: libnm0:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 22 13:46:13 2020 DuplicateSignature: package:network-manager:1.22.10-1ubuntu2.1 Setting up libnm0:amd64 (1.22.10-1ubuntu2.1) ... dpkg: error processing package network-manager (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-06-22 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.23 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: network-manager Title: package network-manager 1.22.10-1ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEI
[Touch-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
The fix does not work for me: uname -r 5.4.0-33-generic ournalctl -b0 -u rtkit-daemon -- Logs begin at Wed 2020-04-29 18:57:09 EEST, end at Thu 2020-06-04 18:41:05 EEST. -- Jun 04 18:26:06 n552vw systemd[1]: Starting RealtimeKit Scheduling Policy Service... Jun 04 18:26:06 n552vw systemd[1]: Started RealtimeKit Scheduling Policy Service. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Successfully called chroot. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Successfully dropped privileges. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Successfully limited resources. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Running. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Canary thread running. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Watchdog thread running. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: Operation not permitted Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes of 1 users. Jun 04 18:26:49 n552vw
[Touch-packages] [Bug 1876562] Re: Upgrade to 20.04 LTS errors - mkinitramfs failure cpio
This fixed my problem: sudo apt purge linux-image-4.15.0-99-generic from: https://askubuntu.com/questions/1207958/error-24-write-error-cannot-write-compressed-block Usually if it's a freespace thing, I'll get a popup about /boot not having enough space. That happened during upgrade process, but I wasn't able to purge old space, and it hasn't happened since finishing the upgrade. There is usually enough space for the current and previous kernel in /boot as well. -- 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/1876562 Title: Upgrade to 20.04 LTS errors - mkinitramfs failure cpio Status in initramfs-tools package in Ubuntu: New Bug description: At the end of the upgrade process to 20.04 I got a message about mkinitramfs. It said I should consider submitting a bug. Now after a re-boot I get: $ sudo apt install -f Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up initramfs-tools (0.136ubuntu6) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.136ubuntu6) ... update-initramfs: Generating /boot/initrd.img-5.4.0-28-generic Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.4.0-28-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned erro r exit status 1 Errors were encountered while processing: initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 $ apt-cache policy initramfs-tools initramfs-tools: Installed: 0.136ubuntu6 Candidate: 0.136ubuntu6 Version table: *** 0.136ubuntu6 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 02:11:32 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-16 (1994 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: Upgraded to focal on 2020-05-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1876562/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876562] [NEW] Upgrade to 20.04 LTS errors - mkinitramfs failure cpio
Public bug reported: At the end of the upgrade process to 20.04 I got a message about mkinitramfs. It said I should consider submitting a bug. Now after a re-boot I get: $ sudo apt install -f Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up initramfs-tools (0.136ubuntu6) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.136ubuntu6) ... update-initramfs: Generating /boot/initrd.img-5.4.0-28-generic Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.4.0-28-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned erro r exit status 1 Errors were encountered while processing: initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) $ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 $ apt-cache policy initramfs-tools initramfs-tools: Installed: 0.136ubuntu6 Candidate: 0.136ubuntu6 Version table: *** 0.136ubuntu6 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 02:11:32 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-16 (1994 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: Upgraded to focal on 2020-05-03 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "screenshot of error I saw during upgrade process" https://bugs.launchpad.net/bugs/1876562/+attachment/5365616/+files/upgrade_error_screenshot.png -- 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/1876562 Title: Upgrade to 20.04 LTS errors - mkinitramfs failure cpio Status in initramfs-tools package in Ubuntu: New Bug description: At the end of the upgrade process to 20.04 I got a message about mkinitramfs. It said I should consider submitting a bug. Now after a re-boot I get: $ sudo apt install -f Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up initramfs-tools (0.136ubuntu6) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.136ubuntu6) ... update-initramfs: Generating /boot/initrd.img-5.4.0-28-generic Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.4.0-28-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned erro r exit status 1 Errors were encountered while processing: initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 $ apt-cache policy initramfs-tools initramfs-tools: Installed: 0.136ubuntu6 Candidate: 0.136ubuntu6 Version table: *** 0.136ubuntu6 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 02:11:32 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-16 (1994 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: Upgraded to focal on 2020-05-03 (0 days ago) To manage notificatio
Re: [Touch-packages] [Bug 774542] Re: [ICH4 - Intel ICH6, playback] No sound at all
Hi Marcus, this is no longer an issue. Those tablets have been retired. Not sure what I can do to clear/close this report. - Steven B. Reeves On Thu, Mar 5, 2020 at 8:30 PM Marcus Tomlinson < marcus.tomlin...@canonical.com> wrote: > This release of Ubuntu is no longer receiving maintenance updates. If > this is still an issue on a maintained version of Ubuntu please let us > know. > > ** Changed in: alsa-driver (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/774542 > > Title: > [ICH4 - Intel ICH6, playback] No sound at all > > Status in alsa-driver package in Ubuntu: > Incomplete > > Bug description: > Both 10.10 and 11.04 have no sound for LE1600 Tablet > > ProblemType: Bug > DistroRelease: Ubuntu 11.04 > Package: alsa-base 1.0.24+dfsg-0ubuntu1 > ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 > Uname: Linux 2.6.38-8-generic i686 > AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. > Architecture: i386 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: solarboy 1246 F pulseaudio > Card0.Amixer.info: >Card hw:0 'ICH6'/'Intel ICH6 with STAC9758,59 at irq 17' > Mixer name : 'SigmaTel STAC9758,59' > Components : 'AC97a:83847658' > Controls : 50 > Simple ctrls : 37 > CheckboxSubmission: 3fa4bb708fb73202cfcfe0c9bb22f401 > CheckboxSystem: c925ed66fbb6fb95ab27315f9d025b66 > Date: Sat Apr 30 16:44:48 2011 > InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release > i386 (20101007) > PackageArchitecture: all > ProcEnviron: >LANGUAGE=en_CA:en >LANG=en_CA.UTF-8 >SHELL=/bin/bash > SourcePackage: alsa-driver > Symptom: audio > Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH6 failed > Symptom_Card: Internal Audio - Intel ICH6 > Symptom_DevicesInUse: 1246 > Symptom_Type: No sound at all > Title: [ICH4 - Intel ICH6, playback] No sound at all > UpgradeStatus: Upgraded to natty on 2011-04-30 (0 days ago) > dmi.bios.date: 12/19/2006 > dmi.bios.vendor: Motion Computing - LE1600 > dmi.bios.version: A12 > dmi.board.name: Compal DX20 > dmi.board.vendor: Compal Computer Corporation > dmi.board.version: None > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: Compal Computer Corporation > dmi.chassis.version: N/A > dmi.modalias: > dmi:bvnMotionComputing-LE1600:bvrA12:bd12/19/2006:svnMotionComputing:pnLE1600:pvrA0:rvnCompalComputerCorporation:rnCompalDX20:rvrNone:cvnCompalComputerCorporation:ct10:cvrN/A: > dmi.product.name: LE1600 > dmi.product.version: A0 > dmi.sys.vendor: Motion Computing > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/774542/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/774542 Title: [ICH4 - Intel ICH6, playback] No sound at all Status in alsa-driver package in Ubuntu: Incomplete Bug description: Both 10.10 and 11.04 have no sound for LE1600 Tablet ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: alsa-base 1.0.24+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: solarboy 1246 F pulseaudio Card0.Amixer.info: Card hw:0 'ICH6'/'Intel ICH6 with STAC9758,59 at irq 17' Mixer name : 'SigmaTel STAC9758,59' Components : 'AC97a:83847658' Controls : 50 Simple ctrls : 37 CheckboxSubmission: 3fa4bb708fb73202cfcfe0c9bb22f401 CheckboxSystem: c925ed66fbb6fb95ab27315f9d025b66 Date: Sat Apr 30 16:44:48 2011 InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007) PackageArchitecture: all ProcEnviron: LANGUAGE=en_CA:en LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH6 failed Symptom_Card: Internal Audio - Intel ICH6 Symptom_DevicesInUse: 1246 Symptom_Type: No sound at all Title: [ICH4 - Intel ICH6, playback] No sound at all UpgradeStatus: Upgraded to natty on 2011-04-30 (0 days ago) dmi.bios.date: 12/19/2006 dmi.bios.vendor: Motion Computing - LE160
[Touch-packages] [Bug 1767302] Re: User is not added to kvm group when installing gnome-boxes
FYI: adduser kvm solves that problem nope. added myself and still no joy. -- 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/1767302 Title: User is not added to kvm group when installing gnome-boxes Status in gnome-boxes package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in gnome-boxes source package in Bionic: Triaged Status in qemu source package in Bionic: Won't Fix Status in systemd source package in Bionic: Invalid Status in gnome-boxes source package in Cosmic: Invalid Status in qemu source package in Cosmic: Invalid Status in systemd source package in Cosmic: Fix Released Status in gnome-boxes source package in Disco: Invalid Status in qemu source package in Disco: Invalid Status in systemd source package in Disco: Fix Released Bug description: Installing gnome-boxes does not add the user to the needed kvm group. This leads to the problem that it is impossible to start any system within gnome-boxes. Gnome-Boxes throwes the error: CPU mode 'custom' for x86_64 kvm domain on x86_64 host is not supported by hypervisor adduser kvm solves that problem but how should an average user know that. Gnome-Boxes is not usable as of now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-boxes/+bug/1767302/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676547] Re: No network connectivity (NIC unmanaged) after upgrade
Ubuntu Server 18.04.3 fresh install.
Ethernet Unmanaged in Network Manager.
SOLVED. FIXED, etc.
-
I created file /etc/netplan/01-network-manager-all.yaml
Within I entered:
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
--
I edited /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
Within I ensured it only say:
network: {config: disabled}
---
I edit /etc/netplan/01-network-manager-all.yaml (If you don't nave then create)
within it I entered:
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
rebooted
-
Wooho, It works!
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1676547
Title:
No network connectivity (NIC unmanaged) after upgrade
Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Yakkety:
Fix Released
Status in network-manager source package in Zesty:
Fix Released
Bug description:
Impact
--
When upgrading from Xenial (with all updates installed) to Yakkety/Zesty you
will boot to a system without networking - sad!
Test Case
-
1) Boot a xenial desktop system
2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is
installed
3) Upgrade to yakkety or zesty
3.5) Enable -proposed and download the new version of n-m "apt-get download
network-manager"
4) Reboot
5) Observe you have no network
If you install the version of network-manager from yakkety-proposed
and then reboot you should have a network connection.
1) Boot a xenial desktop system.
2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is
installed.
3) Install nplan, configure to set up static network on an ethernet device
using nplan.
4) Upgrade to yakkety or zesty
5) Reboot
6) Observe that your system is still being managed by networkd rather than
NetworkManager.
Regression Potential
Any failure to manage ethernet or wireless devices after upgrade, or
issues with the use of netplan in conjunction with NetworkManager
should be investigated as potential regressions. For example, if after
upgrading, ethernet devices are no longer managed, or if devices that
should be explicitly ignored by NetworkManager due to existing user
configuration are now managed, these would indicate a possible
regression caused by this update.
Original Description
nplan was installed during the upgrade process but I had no network
connectivity after upgrading. Apparently, no package wanted to manage
my ethernet connection.
ProblemType: BugDistroRelease: Ubuntu 16.10
Package: ubuntu-release-upgrader-core 1:16.10.10
ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
Uname: Linux 4.8.0-41-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Mon Mar 27 11:34:04 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-01-16 (1531 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
PackageArchitecture: allSourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago)
VarLogDistupgradeTermlog:
modified.conffile..etc.update-manager.meta-release: [modified]
mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676547/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method
*** This bug is a duplicate of bug 1676547 *** https://bugs.launchpad.net/bugs/1676547 I tried all these suggestion, no joy. Why won't dev fix? Please at least tell us what we're doing wrong. I may have to install Desktop version because KVM/QEMU isn't playing nice with seeing the network connection. Now what, reinstall every server manually that I use on my hosts so those KVMs work. I was hoping to avoid using VBox. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1638842 Title: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method Status in network-manager package in Ubuntu: Won't Fix Bug description: Hello, I installed Ubuntu 16.10 using a chroot. I use network-manager to manage connections. My system is up-to-date (so I use network-manager 1.2.4-0ubuntu1). Wifi works perfectly but I cannot connect to wired networks and using my phone's Bluetooth connection. Corresponding devices are said to be unmanaged by network-manager. nmcli dev outputs: DEVICETYPE STATE CONNECTION enp1s0ethernet unmanaged -- wlp2s0wifi disconnected -- 6C:9B:02:2C:EE:2C btunmanaged -- hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C gsm unmanaged -- loloopback unmanaged -- The following command has no effect: sudo nmcli dev set enp1s0 managed yes I can connect to a wired connection by doing: ifconfig enp1s0 up dhclient enp1s0 There is nothing in the file /etc/network/interfaces. Everything works perfectly if I downgrade network-manager to this version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb (http://packages.ubuntu.com/xenial-updates/amd64/network- manager/download). I had to install libreadline6 and downgrade nplan to meet dependencies. I don't know what to join to this bug report so please ask in case anything is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817424] Re: Unable to resolve local DNS names provided by router on bootup.
Looking at this issue again I noticed some others having issues with /etc/resolv.conf so I check and indeed the symlink was incorrect: /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf This was a fresh installation of bionic, so I'm not sure what package installed this incorrect symlink. The solution was to change the symlink: /etc/resolv.conf -> ../run/systemd/resolve/resolv.conf And now I don't need to flush caches for local names to be resolved. -- 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/1817424 Title: Unable to resolve local DNS names provided by router on bootup. Status in systemd package in Ubuntu: New Bug description: On boot, I can see systemd-resolve is configured properly; the router (192.168.1.254) is listed as a DNS server: $ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 3 (wlp0s20f3) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 2 (eno1) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.1.254 DNS Domain: telus Local names are not resolved: $ nslookup zf1 Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find zf1: SERVFAIL $ dig zf1 ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> zf1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 39908 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;zf1. IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Sat Feb 23 09:46:12 PST 2019 ;; MSG SIZE rcvd: 32 Restarting netplan and network-manager services make no difference. Restarting the systemd-resolved (or clearing systemd-resolved caches) solve the problem: $ sudo systemd-resolve --flush-caches OR $ sudo service systemd-resolved restart $ nslookup zf1 Server: 127.0.0.53 Address: 127.0.0.53#53 Non-authoritative answer: Name: zf1.telus Address: 192.168.1.71 ** server can't find zf1.telus: NXDOMAIN Dig still can't find server though: $ dig zf1 ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> zf1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 20375 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;zf1. IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Sat Feb 23 09:47:38 PST 2019 ;; MSG SIZE rcvd: 32 Unless I specify the server manually: $ dig @192.168.1.254 zf1 ;; Warning: Message parser reports malformed message packet. ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> @192.168.1.254 zf1 ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50811 ;; flags: qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ; COOKIE: 94b92f65104856d4 (echoed) ;; QUESTION SECTION: ;zf1. IN A ;; ADDITIONAL SECTION: zf1. 1 IN A 192.168.1.71 ;; Query time: 6 msec ;; SERVER: 192.168.1.254#53(192.168.1.254) ;; WHEN: Sat Feb 23 09:59:05 PST 2019 ;; MSG SIZE rcvd: 60 Once I get local names resolved, the systemd-resolve status remains the same: $ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr
[Touch-packages] [Bug 1838848] [NEW] Bluetooth device not detected after resume from suspend [Qualcomm Atheros AR9485]
Public bug reported: It's very familiar to Bug #1788807. I'm on 19.04. How can I help to solve it? 1) $lsb_release -rd Description:Ubuntu 19.04 Release:19.04 2) $ apt-cache policy bluez bluez: Установлен: 5.50-0ubuntu2 Кандидат: 5.50-0ubuntu2 Таблица версий: *** 5.50-0ubuntu2 500 500 http://ru.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status 3) Expectations: work as designed - no issues. 4) after resume from suspended state device is no longer available - if open gnome (UI) bluetooth manager in journal: 03 16:35:50 PC-Name tracker-miner-f[1357]: Could not process 'file:///home/user/%23534117': Error when getting information for file “/home/user/#534117”: Нет такого файла или каталога* *translation from russian: File or path does not exist $ lspci -nnk | grep -iA3 net; lsusb; rfkill list; uname -r; dmesg | egrep -i 'blue|firm' 01:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032] (rev 01) Subsystem: Hewlett-Packard Company AR9485 Wireless Network Adapter [103c:1785] Kernel driver in use: ath9k Kernel modules: ath9k 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL810xE PCI Express Fast Ethernet controller [10ec:8136] (rev 05) Subsystem: Hewlett-Packard Company RTL810xE PCI Express Fast Ethernet controller [103c:3566] Kernel driver in use: r8169 Kernel modules: r8169 03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader [10ec:5209] (rev 01) Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 002: ID 0e8f:0021 GreenAsia Inc. Multimedia Keyboard Controller Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 003: ID 05c8:021e Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 5.0.0-23-generic [0.177448] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [0.198830] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain [bus 00-3f] only partially covers this bridge [3.257474] [Firmware Bug]: Invalid critical threshold (0) [4.140519] usb 6-1: Product: Bluetooth USB Host Controller [6.610450] Bluetooth: Core ver 2.22 [6.610478] Bluetooth: HCI device and connection manager initialized [6.610485] Bluetooth: HCI socket layer initialized [6.610488] Bluetooth: L2CAP socket layer initialized [6.610494] Bluetooth: SCO socket layer initialized [ 16.795026] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 16.795029] Bluetooth: BNEP filters: protocol multicast [ 16.795036] Bluetooth: BNEP socket layer initialized ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 3 16:19:13 2019 InstallationDate: Installed on 2019-08-03 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: bnep btusb bluetooth MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=670d7b88-4792-45a0-a2d1-b026d4926c27 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.53 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3566 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.3A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.53:bd10/24/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr06921220461610100:rvnHewlett-Packard:rn3566:rvr21.3A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: A5Q13EA#ACB dmi.product.version: 06921220461610100 dmi.sys.vendor: Hewlett-Packard hciconfig: rfkill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https:
[Touch-packages] [Bug 1817424] Re: Unable to resolve local DNS names provided by router on bootup.
I noticed the following in my syslog recently: systemd-resolved[656]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. This may be a hint. Bug persists using systemd 237-3ubuntu10.24 -- 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/1817424 Title: Unable to resolve local DNS names provided by router on bootup. Status in systemd package in Ubuntu: New Bug description: On boot, I can see systemd-resolve is configured properly; the router (192.168.1.254) is listed as a DNS server: $ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 3 (wlp0s20f3) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 2 (eno1) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.1.254 DNS Domain: telus Local names are not resolved: $ nslookup zf1 Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find zf1: SERVFAIL $ dig zf1 ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> zf1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 39908 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;zf1. IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Sat Feb 23 09:46:12 PST 2019 ;; MSG SIZE rcvd: 32 Restarting netplan and network-manager services make no difference. Restarting the systemd-resolved (or clearing systemd-resolved caches) solve the problem: $ sudo systemd-resolve --flush-caches OR $ sudo service systemd-resolved restart $ nslookup zf1 Server: 127.0.0.53 Address: 127.0.0.53#53 Non-authoritative answer: Name: zf1.telus Address: 192.168.1.71 ** server can't find zf1.telus: NXDOMAIN Dig still can't find server though: $ dig zf1 ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> zf1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 20375 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;zf1. IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Sat Feb 23 09:47:38 PST 2019 ;; MSG SIZE rcvd: 32 Unless I specify the server manually: $ dig @192.168.1.254 zf1 ;; Warning: Message parser reports malformed message packet. ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> @192.168.1.254 zf1 ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50811 ;; flags: qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ; COOKIE: 94b92f65104856d4 (echoed) ;; QUESTION SECTION: ;zf1. IN A ;; ADDITIONAL SECTION: zf1. 1 IN A 192.168.1.71 ;; Query time: 6 msec ;; SERVER: 192.168.1.254#53(192.168.1.254) ;; WHEN: Sat Feb 23 09:59:05 PST 2019 ;; MSG SIZE rcvd: 60 Once I get local names resolved, the systemd-resolve status remains the same: $ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa
[Touch-packages] [Bug 1805543] Re: Packaged version of iptables doesn't provide --random-fully flag.
I found this thread because I ran into a problem with a brand-new installation of Kubernetes (K8s) running in AWS that was failing a large number of browser requests being serviced by the K8s cluster. There is a ton of detail about this problem at https://tech.xing.com/a-reason-for- unexplained-connection-timeouts-on-kubernetes-docker-abd041cf7e02. To make a very long story short, we need the 1.6.2+ version of iptables on Ubuntu because it supports the --random-fully flag. Without this, any K8s cluster created on Ubuntu is pretty useless if you use local DNS to resolve cluster services by name (e.g. http://my-backend-microservice), which is what we do to support namespaces for reverse proxies (nginx). I manually built iptables 1.6.2 using the instructions at http://www.linuxfromscratch.org/blfs/view/8.2/postlfs/iptables.html and my problem appears to be solved. It would be great if the change could be backported into bionic, but at the minimum getting this into the next LTS then that would be great. If it makes any difference, iptables in Debian buster is at 1.8.2-4. They have a planned release in, oh look at that, two days :-) As for test cases, in this particular instance it's sufficient that when using the --random-fully flag to set up a NAT masquerading rule that the NF_NAT_RANGE_PROTO_RANDOM_FULLY flag is set. I can't say what the regression potential is, but since it's a minor release then I'd expect it to be minimal. The diffs are at https://www.netfilter.org/projects/iptables/files/patch- iptables-1.6.1-1.6.2.bz2 Here are some details of my installation: ubuntu@kubernetes-master:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic ubuntu@kubernetes-master:~$ uname -a Linux kubernetes-master 4.15.0-1043-aws #45-Ubuntu SMP Mon Jun 24 14:07:03 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1805543 Title: Packaged version of iptables doesn't provide --random-fully flag. Status in iptables package in Ubuntu: Confirmed Bug description: Hello. This isn't strictly a bug, but more of an upgrade-request on the iptables package. Normally i wouldn't be inclined to submit such a bug report, but a user on the ubuntu-devel-discuss mailing list encouraged me to submit this anyway [1]. For our production systems, we're running into a kernel race condition bug, for which a workaround has been made available. The fix boils down to iptables having a new flag which it passes down to the kernel, to enable the workaround. However, the version of iptables in Ubuntu (v1.6.1) doesn't support that kernel feature yet. Specifically, it's introduced in this commit on the iptables codebase: https://git.netfilter.org/iptables/commit/?id=8b0da2130b8af3890ef20afb2305f11224bb39ec. The feature we need from that commit is part of the v1.6.2 and newer iptables releases, but it looks like the Bionic, Cosmic, and Disco releases of Ubuntu all include v1.6.1 without that patch, so for now we're going to have to build iptables from source on our production machines. That shouldn't pose any huge issues, but of course, we'd prefer to be able to use the package from package management, or perhaps a backported package from a newer Ubuntu release. So to summarise, this might be an invalid bug report, but consider it a vote to upgrade the packaged version of iptables. If this bug report is entirely inappropriate, then I apologise. 1. Link to thread on ubuntu-devel-discuss where I describe the problem and Nish suggests I file this bug report: https://lists.ubuntu.com/archives/ubuntu-devel- discuss/2018-November/018181.html Ubuntu version we're using: Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy iptables iptables: Installed: 1.6.1-2ubuntu2 Candidate: 1.6.1-2ubuntu2 Version table: *** 1.6.1-2ubuntu2 500 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Thanks for your time, Paul To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1805543/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726160] Re: On login, display rotates to wrong orientation [HP Pavilion]
Had this same problem on Acer Spin 1, with Intel Celeron CPU and Intel HD Graphics 500 (Broxton). Removing iio-sensor-proxy fixed it perfectly! Thank you! -- 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/1726160 Title: On login, display rotates to wrong orientation [HP Pavilion] Status in IIO Sensor Proxy: Fix Released Status in systemd: Fix Released Status in iio-sensor-proxy package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in iio-sensor-proxy source package in Bionic: Invalid Status in systemd source package in Bionic: Triaged Status in iio-sensor-proxy source package in Cosmic: Invalid Status in systemd source package in Cosmic: Triaged Status in iio-sensor-proxy source package in Disco: Invalid Status in systemd source package in Disco: Fix Released Bug description: I'm using a laptop, and on 17.04 the display always showed correctly, but after upgrading to 17.10, when I log in the display rotates to the right (portrait), and I have to open a terminal and run 'xrandr -o 1' to get it back to the correct (landscape) orientation. In previous versions 'xrandr -o 0' was landscape, and '1' was portrait the other way. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 15:15:08 2017 DistUpgraded: 2017-10-22 14:17:00,381 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed nvidia-340, 340.104, 4.10.0-37-generic, x86_64: installed nvidia-340, 340.104, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c] InstallationDate: Installed on 2017-01-11 (284 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file. MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago) dmi.bios.date: 10/05/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 363C dmi.board.vendor: Hewlett-Packard dmi.board.version: 32.25 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039D222412102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 039D222412102 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/iio-sensor-proxy/+bug/1726160/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800003] Re: evince crashes in FcConfigParseAndLoad
This bug https://gitlab.freedesktop.org/fontconfig/fontconfig/issues/71
suggests that substantial improvements have been made to the fontconfig
package against null pointer dereferences after version 2.13.0-5.
https://cgit.freedesktop.org/fontconfig/commit/?id=efac784b0108d3140d7ec51cf22cb8a4453bd566
https://cgit.freedesktop.org/fontconfig/commit/?id=b1762935c3db2bc611750c61ce9cb38b9008db6b
https://cgit.freedesktop.org/fontconfig/commit/?id=b047e299546ac3abb79cf0bac3c67f5c2dfc7fb6
https://cgit.freedesktop.org/fontconfig/commit/?id=f3981a8bcd97a0388bf150ea7c1b4a1015e5e358
Can fontconfig be updated?
** Bug watch added: gitlab.freedesktop.org/fontconfig/fontconfig/issues #71
https://gitlab.freedesktop.org/fontconfig/fontconfig/issues/71
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/183
Title:
evince crashes in FcConfigParseAndLoad
Status in fontconfig package in Ubuntu:
Confirmed
Bug description:
I have the following situation persistently on my system (Ubuntu
18.04.1 on Dell Latitude E6500):
Evince called with any pdf file crashes immediately with a
segmentation fault. From the crash dump, I see that the crash happens
in fontconfig's FcConfigParseAndLoad function, i.e. when the system
fonts.conf is read. I can reproduce the crash with the following
minimal example:
#include
const FcChar8* filename = "/home/mirkoh/fontconfig-test/fonts.conf";
FcConfig* config;
int main(){
FcConfigParseAndLoad(config, filename, FcTrue);
}
The fonts.conf file used here is also absolutely minimal:
(Get me right. It first happened with my system fonts.conf, which is
not empty. In order to find out whether a specific entry lead to the
crash, I deleted entry after entry, ultimately reaching the file
above, and always FcConfigParseAndLoad crashes.
I have no idea how to go on from here.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/183/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800003] Re: evince crashes in FcConfigParseAndLoad
Please re-open. I have the same bug.
$ /usr/bin/evince
(evince:2751): Gtk-WARNING **: 00:31:32.744: Attempting to read the recently
used resources file at '/home/user/.local/share/recently-used.xbel', but the
parser failed: Failed to open file
“/home/user/.local/share/recently-used.xbel”: Permission denied.
Segmentation fault (core dumped)
$ { echo run; echo thread apply all bt full; quit; } | gdb /usr/bin/evince
GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
[Touch-packages] [Bug 1800003] Re: evince crashes in FcConfigParseAndLoad
I can also reproduce the crash with the minimal test program provided in
the bug report (nice catch!). I am on Ubuntu 18.04.2.
** Changed in: fontconfig (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/183
Title:
evince crashes in FcConfigParseAndLoad
Status in fontconfig package in Ubuntu:
Confirmed
Bug description:
I have the following situation persistently on my system (Ubuntu
18.04.1 on Dell Latitude E6500):
Evince called with any pdf file crashes immediately with a
segmentation fault. From the crash dump, I see that the crash happens
in fontconfig's FcConfigParseAndLoad function, i.e. when the system
fonts.conf is read. I can reproduce the crash with the following
minimal example:
#include
const FcChar8* filename = "/home/mirkoh/fontconfig-test/fonts.conf";
FcConfig* config;
int main(){
FcConfigParseAndLoad(config, filename, FcTrue);
}
The fonts.conf file used here is also absolutely minimal:
(Get me right. It first happened with my system fonts.conf, which is
not empty. In order to find out whether a specific entry lead to the
crash, I deleted entry after entry, ultimately reaching the file
above, and always FcConfigParseAndLoad crashes.
I have no idea how to go on from here.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/183/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829533] [NEW] Doubled desktop icons
Public bug reported: I customized my icons by changing the folder image. That worked fine in Ubuntu 18.04. When I upgraded to 19.04 my customized icons no longer showed the new image, and to fix that I did... something. Install Nemo deskop, I think, but I can't find a configuration or uninstall option for it. Then the old icons with the customized images worked fine... but now the folders have a doubles that are "dummies" (not working -- not customized -- don't respond to being clicked). In the Gnome Tweak Took Desktop icons is "off" but the toggle for "Desktop Icons Switch" has an ! meaning can't be turned on or off. I'm moderately techy in Windows, but still pretty stupid about Linux, sorry. But I can probably run tests, find logs, paste commands into Terminal Window or whatever. THANKS!!! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 17 09:27:05 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T520 [17aa:21cf] Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4243AV5 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=a8ac701e-a37a-41b7-aa12-0816bd937e33 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET49WW (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 4243AV5 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:bvr8AET49WW(1.29):bd07/11/2011:svnLENOVO:pn4243AV5:pvrThinkPadT520:rvnLENOVO:rn4243AV5:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T520 dmi.product.name: 4243AV5 dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco 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/1829533 Title: Doubled desktop icons Status in xorg package in Ubuntu: New Bug description: I customized my icons by changing the folder image. That worked fine in Ubuntu 18.04. When I upgraded to 19.04 my customized icons no longer showed the new image, and to fix that I did... something. Install Nemo deskop, I think, but I can't find a configuration or uninstall option for it. Then the old icons with the customized images worked fine... but now the folders have a doubles that are "dummies" (not working -- not customized -- don't respond to being clicked). In the Gnome Tweak Took Desktop icons is "off" but the toggle for "Desktop Icons Switch" has an ! meaning can't be turned on or off. I'm moderately techy in Windows, but still pretty stupid about Linux, sorry. But I can probably run tests, find logs, paste commands into Terminal Window or whatever. THANKS!!! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu27 Architect
[Touch-packages] [Bug 1815987] Re: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS
I have reclaimed /var/lib with chown to root:root and now everything is working. Thank you so much for your help in chasing it down! I couldn't figure it out since it didn't point me all those levels up. Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1815987 Title: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS Status in systemd package in Ubuntu: New Bug description: I am using Ubuntu 18.04LTS, fresh install from the summer, and tmpfiles won't launch since November. $ sudo systemctl start systemd-tmpfiles-setup Job for systemd-tmpfiles-setup.service failed because the control process exited with error code. See "systemctl status systemd-tmpfiles-setup.service" and "journalctl -xe" for details. $ sudo systemctl status systemd-tmpfiles-setup ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2019-02-14 19:48:36 EST; 8s ago Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Process: 28934 ExecStart=/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE) Main PID: 28934 (code=exited, status=1/FAILURE) Feb 14 19:48:35 mythserver2018 systemd[1]: Starting Create Volatile Files and Directories... Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/colord/icc, refusing. Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing. Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Feb 14 19:48:36 mythserver2018 systemd[1]: Failed to start Create Volatile Files and Directories. Looking at /var/lib/colord/icc: kris@mythserver2018:/var/lib/colord/icc$ ls -a . .. kris@mythserver2018:/var/lib/colord/icc$ I have also deleted these directories and rebuilt them, just to be sure - they are NOT symlinked and have no permission issues: kris@mythserver2018:/var/lib/systemd$ ls -l total 28 drwxr-xr-x 2 root root 4096 Feb 9 16:04 catalog drwxr-xr-x 2 root root 4096 Dec 28 07:04 coredump drwxr-xr-x 2 root root 4096 Jul 8 2018 coredumpold drwxr-xr-x 20 root root 4096 Feb 9 16:08 deb-systemd-helper-enabled drwxr-xr-x 2 root root 4096 Nov 14 18:31 deb-systemd-helper-masked -rw--- 1 root root 512 Feb 9 17:34 random-seed drwxr-xr-x 2 root root 4096 Jul 10 2018 timers lrwxrwxrwx 1 root root 27 Jul 8 2018 timesync -> ../private/systemd/timesync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1815987/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815987] Re: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS
krisbee@mythserver2018:~$ sudo ls -la / total 120 drwxr-xr-x 25 root root 4096 Apr 11 18:41 . drwxr-xr-x 25 root root 4096 Apr 11 18:41 .. drwxr-xr-x 2 root root 4096 Apr 20 15:34 bin drwxr-xr-x 3 root root 4096 Apr 20 15:37 boot drwxrwxr-x 2 root root 4096 Jul 8 2018 cdrom drwxr-xr-x 21 root root 4580 Apr 25 07:32 dev drwxr-xr-x 157 root root 12288 Apr 20 15:37 etc drwxr-xr-x 5 root root 4096 Feb 1 21:37 home lrwxrwxrwx 1 root root33 Apr 7 16:19 initrd.img -> boot/initrd.img-4.15.0-47-generic lrwxrwxrwx 1 root root33 Apr 7 16:19 initrd.img.old -> boot/initrd.img-4.15.0-46-generic drwxr-xr-x 21 root root 4096 Sep 6 2018 lib drwxr-xr-x 2 root root 4096 Jul 29 2018 lib32 drwxr-xr-x 2 root root 4096 Apr 26 2018 lib64 drwx-- 2 root root 16384 Jul 8 2018 lost+found drwxr-xr-x 3 root root 4096 Jul 8 2018 media drwxr-xr-x 4 root root 4096 Jul 11 2018 mnt drwxr-xr-x 5 root root 4096 Mar 5 19:57 opt dr-xr-xr-x 294 root root 0 Apr 20 15:38 proc drwx-- 6 root root 4096 Nov 23 17:51 root drwxr-xr-x 33 root root 1120 Apr 25 06:30 run drwxr-xr-x 2 root root 12288 Apr 20 15:35 sbin drwxr-xr-x 2 root root 4096 Jul 8 2018 snap drwxr-xr-x 2 root root 4096 Apr 26 2018 srv dr-xr-xr-x 13 root root 0 Apr 25 22:40 sys drwxrwxrwt 22 root root 12288 Apr 25 22:39 tmp drwxr-xr-x 12 root root 4096 Jun 11 2010 usr drwxr-xr-x 15 root root 4096 May 23 2010 var lrwxrwxrwx 1 root root30 Apr 7 16:19 vmlinuz -> boot/vmlinuz-4.15.0-47-generic lrwxrwxrwx 1 root root30 Apr 7 16:19 vmlinuz.old -> boot/vmlinuz-4.15.0-46-generic krisbee@mythserver2018:~$ sudo ls -la /var/ total 60 drwxr-xr-x 15 rootroot 4096 May 23 2010 . drwxr-xr-x 25 rootroot 4096 Apr 11 18:41 .. drwxr-xr-x 2 rootroot 4096 Apr 21 00:06 backups drwxr-xr-x 20 rootroot 4096 Jul 27 2018 cache drwxrwsrwt 2 rootwhoopsie 4096 Apr 23 00:05 crash drwxr-xr-x 90 krisbee krisbee 4096 Apr 7 16:16 lib drwxrwsr-x 2 rootstaff4096 Apr 24 2018 local lrwxrwxrwx 1 rootroot9 Jul 8 2018 lock -> /run/lock drwxrwxr-x 18 rootsyslog 4096 Apr 25 00:06 log drwxrwsr-x 2 rootmail 4096 Apr 25 22:40 mail drwxrwsrwt 2 rootwhoopsie 4096 Apr 26 2018 metrics drwxr-xr-x 2 rootroot 4096 Apr 26 2018 opt lrwxrwxrwx 1 rootroot4 Jul 8 2018 run -> /run drwxr-xr-x 2 rootroot 4096 Apr 16 2018 snap drwxr-xr-x 10 rootroot 4096 Oct 20 2018 spool drwxrwxrwt 10 rootroot 4096 Apr 25 22:39 tmp drwxr-xr-x 3 rootroot 4096 Jul 10 2018 www krisbee@mythserver2018:~$ sudo ls -la /var/lib/ total 360 drwxr-xr-x 90 krisbee krisbee 4096 Apr 7 16:16 . drwxr-xr-x 15 root root 4096 May 23 2010 .. drwxr-xr-x 4 root root 4096 Apr 26 2018 AccountsService drwxr-xr-x 2 root root 4096 Apr 30 2013 acpi-support drwxr-xr-x 2 root root 4096 Apr 20 15:38 alsa drwxr-xr-x 5 root root 4096 Jul 10 2018 apache2 drwxr-xr-x 4 root root 4096 Apr 20 15:32 app-info drwxr-xr-x 5 root root 4096 Apr 20 15:34 apt drwxr-xr-x 2 root root 4096 Apr 23 00:10 apt-xapian-index drwxr-xr-x 2 root root 4096 Apr 26 2018 aspell drwxr-xr-x 2 avahi-autoipdavahi-autoipd 4096 Apr 26 2018 avahi-autoipd drwxr-xr-x 2 root root 4096 Apr 20 15:35 binfmts drwxr-xr-x 2 root root 4096 Feb 21 2018 bluetooth drwxr-xr-x 7 krisbee krisbee 4096 Jul 25 2018 cache drwxr-xr-x 4 colord colord4096 Dec 28 07:06 colord drwxr-xr-x 2 root root 4096 Apr 23 2018 command-not-found drwxr-xr-x 2 root root 4096 Jul 8 2018 dbus drwxr-xr-x 2 root root 4096 Apr 16 2018 dhcp drwxr-xr-x 4 root root 4096 Apr 26 2018 dictionaries-common drwxr-xr-x 7 root root 4096 Apr 20 15:37 dpkg drwxr-xr-x 3 root root 4096 Apr 26 2018 emacsen-common drwxr-xr-x 3 root root 4096 Apr 26 2018 fwupd drwxr-xr-x 2 root root 4096 Feb 14 2018 fwupdate drwxr-xr-x 5 root root 4096 Apr 26 2018 gconf drwxr-xr-x 3 root root 4096 Apr 26 2018 gems drwxr-xr-x 2 geoclue geoclue 4096 Jul 20 2017 geoclue drwxr-xr-x 4 root root 4096 Apr 26 2018 ghostscript drwxr-xr-x 2 root root 4096 May 31 2018 git drwxr-xr-x 3 root root 4096 Apr 7 16:16 grub drwxr-xr-x 2 root root 4096 Mar 7 2018 hp drwxr-xr-x 3 root root 4096 Apr 26 2018 ieee-data drwxr-xr-x 2 root root 4096 Apr 8 06:06 initramfs-tools drwxr-xr-x 2 ro
[Touch-packages] [Bug 1815987] Re: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS
Still nothing? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1815987 Title: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS Status in systemd package in Ubuntu: New Bug description: I am using Ubuntu 18.04LTS, fresh install from the summer, and tmpfiles won't launch since November. $ sudo systemctl start systemd-tmpfiles-setup Job for systemd-tmpfiles-setup.service failed because the control process exited with error code. See "systemctl status systemd-tmpfiles-setup.service" and "journalctl -xe" for details. $ sudo systemctl status systemd-tmpfiles-setup ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2019-02-14 19:48:36 EST; 8s ago Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Process: 28934 ExecStart=/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE) Main PID: 28934 (code=exited, status=1/FAILURE) Feb 14 19:48:35 mythserver2018 systemd[1]: Starting Create Volatile Files and Directories... Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/colord/icc, refusing. Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing. Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Feb 14 19:48:36 mythserver2018 systemd[1]: Failed to start Create Volatile Files and Directories. Looking at /var/lib/colord/icc: kris@mythserver2018:/var/lib/colord/icc$ ls -a . .. kris@mythserver2018:/var/lib/colord/icc$ I have also deleted these directories and rebuilt them, just to be sure - they are NOT symlinked and have no permission issues: kris@mythserver2018:/var/lib/systemd$ ls -l total 28 drwxr-xr-x 2 root root 4096 Feb 9 16:04 catalog drwxr-xr-x 2 root root 4096 Dec 28 07:04 coredump drwxr-xr-x 2 root root 4096 Jul 8 2018 coredumpold drwxr-xr-x 20 root root 4096 Feb 9 16:08 deb-systemd-helper-enabled drwxr-xr-x 2 root root 4096 Nov 14 18:31 deb-systemd-helper-masked -rw--- 1 root root 512 Feb 9 17:34 random-seed drwxr-xr-x 2 root root 4096 Jul 10 2018 timers lrwxrwxrwx 1 root root 27 Jul 8 2018 timesync -> ../private/systemd/timesync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1815987/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815987] Re: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS
Still no idea/help on this bug? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1815987 Title: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS Status in systemd package in Ubuntu: New Bug description: I am using Ubuntu 18.04LTS, fresh install from the summer, and tmpfiles won't launch since November. $ sudo systemctl start systemd-tmpfiles-setup Job for systemd-tmpfiles-setup.service failed because the control process exited with error code. See "systemctl status systemd-tmpfiles-setup.service" and "journalctl -xe" for details. $ sudo systemctl status systemd-tmpfiles-setup ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2019-02-14 19:48:36 EST; 8s ago Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Process: 28934 ExecStart=/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE) Main PID: 28934 (code=exited, status=1/FAILURE) Feb 14 19:48:35 mythserver2018 systemd[1]: Starting Create Volatile Files and Directories... Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/colord/icc, refusing. Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing. Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Feb 14 19:48:36 mythserver2018 systemd[1]: Failed to start Create Volatile Files and Directories. Looking at /var/lib/colord/icc: kris@mythserver2018:/var/lib/colord/icc$ ls -a . .. kris@mythserver2018:/var/lib/colord/icc$ I have also deleted these directories and rebuilt them, just to be sure - they are NOT symlinked and have no permission issues: kris@mythserver2018:/var/lib/systemd$ ls -l total 28 drwxr-xr-x 2 root root 4096 Feb 9 16:04 catalog drwxr-xr-x 2 root root 4096 Dec 28 07:04 coredump drwxr-xr-x 2 root root 4096 Jul 8 2018 coredumpold drwxr-xr-x 20 root root 4096 Feb 9 16:08 deb-systemd-helper-enabled drwxr-xr-x 2 root root 4096 Nov 14 18:31 deb-systemd-helper-masked -rw--- 1 root root 512 Feb 9 17:34 random-seed drwxr-xr-x 2 root root 4096 Jul 10 2018 timers lrwxrwxrwx 1 root root 27 Jul 8 2018 timesync -> ../private/systemd/timesync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1815987/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815987] Re: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS
Bump. Still up to date on all patches, still have this issue. kris@mythserver2018:/$ uname -a Linux mythserver2018 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux kris@mythserver2018:/$ sudo mount sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,nosuid,relatime,size=8109040k,nr_inodes=2027260,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1627864k,mode=755) /dev/sda1 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=19533) mqueue on /dev/mqueue type mqueue (rw,relatime) debugfs on /sys/kernel/debug type debugfs (rw,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M) configfs on /sys/kernel/config type configfs (rw,relatime) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) tracefs on /sys/kernel/debug/tracing type tracefs (rw,relatime) /dev/sdc1 on /mnt/backup_storage type xfs (rw,relatime,attr2,inode64,noquota) /dev/sdb1 on /mnt/storage type xfs (rw,relatime,attr2,inode64,noquota) /dev/sda6 on /home type ext4 (rw,relatime,data=ordered) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime) vmware-vmblock on /run/vmblock-fuse type fuse.vmware-vmblock (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other) tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1627860k,mode=700,uid=1000,gid=1000) kris@mythserver2018:/$ ls -l total 112 drwxr-xr-x 2 root root 4096 Apr 7 16:16 bin drwxr-xr-x 3 root root 4096 Apr 8 06:06 boot drwxrwxr-x 2 root root 4096 Jul 8 2018 cdrom drwxr-xr-x 21 root root 4500 Apr 11 07:35 dev drwxr-xr-x 157 root root 12288 Apr 11 18:50 etc drwxr-xr-x 5 root root 4096 Feb 1 21:37 home lrwxrwxrwx 1 root root33 Apr 7 16:19 initrd.img -> boot/initrd.img-4.15.0-47-generic lrwxrwxrwx 1 root root33 Apr 7 16:19 initrd.img.old -> boot/initrd.img-4.15.0-46-generic drwxr-xr-x 21 root root 4096 Sep 6 2018 lib drwxr-xr-x 2 root root 4096 Jul 29 2018 lib32 drwxr-xr-x 2 root root 4096 Apr 26 2018 lib64 drwx-- 2 root root 16384 Jul 8 2018 lost+found drwxr-xr-x 3 root root 4096 Jul 8 2018 media drwxr-xr-x 4 root root 4096 Jul 11 2018 mnt drwxr-xr-x 5 root root 4096 Mar 5 19:57 opt dr-xr-xr-x 291 root root 0 Apr 7 16:26 proc drwx-- 6 root root 4096 Nov 23 17:51 root drwxr-xr-x 34 root root 1040 Apr 11 18:47 run drwxr-xr-x 2 root root 12288 Apr 7 16:16 sbin drwxr-xr-x 2 root root 4096 Jul 8 2018 snap drwxr-xr-x 2 root root 4096 Apr 26 2018 srv dr-xr-xr-x 13 root root 0 Apr 11 18:48 sys drwxrwxrwt 7 root root 12288 Apr 11 18:51 tmp drwxr-xr-x 12 root root 4096 Jun 11 2010 usr drwxr-xr-x 15 root root 4096 May 23 2010 var lrwxrwxrwx 1 root root30 Apr 7 16:19 vmlinuz -> boot/vmlinuz-4.15.0-47-generic lrwxrwxrwx 1 root root30 Apr 7 16:19 vmlinuz.old -> boot/vmlinuz-4.15.0-46-generic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1815987 Title: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS S
[Touch-packages] [Bug 1823076] Re: Intel NUC (8I3BEH1) wakes up immediately after suspend if Bluetooth is still enabled
If I remove the bluez package there are no issues with suspend. ** Changed in: bluez (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1823076 Title: Intel NUC (8I3BEH1) wakes up immediately after suspend if Bluetooth is still enabled Status in bluez package in Ubuntu: New Bug description: After replacing my USB mouse with a BT mouse, I noticed my machine would no longer suspend without immediately waking up. i.e. I suspend and see the light go into the slow fade in and out for one cycle and then goes solid and the display wakes up again. If I disable BT (via blueman applet) suspend works fine. I've fixed this by shutting down the BT service before suspend, and starting it back up on wake, as indicated here: https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately- after-suspend Perhaps this script should be included in blueZ as suspend issues seem very hard to debug and the immediate wake after suspend could be caused many any number of things. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Apr 3 13:16:14 2019 InstallationDate: Installed on 2019-02-09 (53 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems NUC8i3BEH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0051.2018.1015.1513 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:BB:60:50:92:5D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1912660 acl:106009 sco:0 events:337 errors:0 TX bytes:12331 acl:74 sco:0 commands:204 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1823076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823076] Re: Intel NUC (8I3BEH1) wakes up immediately after suspend if Bluetooth is still enabled
So after some more investigation it's clear that the problem is inconsistent. Sometimes wake immediately follows suspend, sometimes not. Sometimes it takes a while to wake up, up to a few minutes, other times it's immediate. Occasionally, it seems to suspend fine; or maybe I'm not waiting long enough for the wake. I noticed also that I can't stop bluetoothd: $ ps aux | grep bluetoothd root 8305 0.0 0.0 36520 4388 ?Ss 11:35 0:00 /usr/lib/bluetooth/bluetoothd -d bbogart 8598 0.0 0.0 22000 1040 pts/2R+ 11:40 0:00 grep --color=auto bluetoothd $ sudo service bluetooth stop $ ps aux | grep bluetoothd root 8662 2.5 0.0 36520 4324 ?Ss 11:41 0:00 /usr/lib/bluetooth/bluetoothd -d bbogart 8670 0.0 0.0 22000 1088 pts/2S+ 11:41 0:00 grep --color=auto bluetoothd Why would bluetoothd restart after I've explicitly told it to stop? Now, if I put the stop and start service script in /lib/systemd/system- sleep/, then the NUC does not wake up after hours. The problem persists when: Mouse is switched off (before entering suspend) Mouse is changed to USB (not BT) mode Bluetooth is turned "off" (via blueman applet) Removing bluez may also solve the problem, I'm testing that now. -- 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/1823076 Title: Intel NUC (8I3BEH1) wakes up immediately after suspend if Bluetooth is still enabled Status in bluez package in Ubuntu: Incomplete Bug description: After replacing my USB mouse with a BT mouse, I noticed my machine would no longer suspend without immediately waking up. i.e. I suspend and see the light go into the slow fade in and out for one cycle and then goes solid and the display wakes up again. If I disable BT (via blueman applet) suspend works fine. I've fixed this by shutting down the BT service before suspend, and starting it back up on wake, as indicated here: https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately- after-suspend Perhaps this script should be included in blueZ as suspend issues seem very hard to debug and the immediate wake after suspend could be caused many any number of things. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Apr 3 13:16:14 2019 InstallationDate: Installed on 2019-02-09 (53 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems NUC8i3BEH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0051.2018.1015.1513 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:BB:60:50:92:5D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1912660 acl:106009 sco:0 events:337 errors:0 TX bytes:12331 acl:74 sco:0 commands:204 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1823076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823076] Re: Intel NUC (8I3BEH1) wakes up immediately after suspend if Bluetooth is still enabled
Scratch that; the first couple suspend operations did work, and then they stopped again. I'll do more testing and report back. I did rule out mouse movement by using the hardware power switch on the mouse. ** Changed in: bluez (Ubuntu) Status: Invalid => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1823076 Title: Intel NUC (8I3BEH1) wakes up immediately after suspend if Bluetooth is still enabled Status in bluez package in Ubuntu: Incomplete Bug description: After replacing my USB mouse with a BT mouse, I noticed my machine would no longer suspend without immediately waking up. i.e. I suspend and see the light go into the slow fade in and out for one cycle and then goes solid and the display wakes up again. If I disable BT (via blueman applet) suspend works fine. I've fixed this by shutting down the BT service before suspend, and starting it back up on wake, as indicated here: https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately- after-suspend Perhaps this script should be included in blueZ as suspend issues seem very hard to debug and the immediate wake after suspend could be caused many any number of things. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Apr 3 13:16:14 2019 InstallationDate: Installed on 2019-02-09 (53 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems NUC8i3BEH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0051.2018.1015.1513 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:BB:60:50:92:5D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1912660 acl:106009 sco:0 events:337 errors:0 TX bytes:12331 acl:74 sco:0 commands:204 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1823076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823076] Re: Intel NUC (8I3BEH1) wakes up immediately after suspend if Bluetooth is still enabled
I believe this issue was due to "legacy suspend" rather than "modern suspend" selected in UEFI. After a couple suspends I am no longer seeing the problem, but will reopen if it happens again. ** Changed in: bluez (Ubuntu) Status: Incomplete => Invalid -- 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/1823076 Title: Intel NUC (8I3BEH1) wakes up immediately after suspend if Bluetooth is still enabled Status in bluez package in Ubuntu: Invalid Bug description: After replacing my USB mouse with a BT mouse, I noticed my machine would no longer suspend without immediately waking up. i.e. I suspend and see the light go into the slow fade in and out for one cycle and then goes solid and the display wakes up again. If I disable BT (via blueman applet) suspend works fine. I've fixed this by shutting down the BT service before suspend, and starting it back up on wake, as indicated here: https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately- after-suspend Perhaps this script should be included in blueZ as suspend issues seem very hard to debug and the immediate wake after suspend could be caused many any number of things. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Apr 3 13:16:14 2019 InstallationDate: Installed on 2019-02-09 (53 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems NUC8i3BEH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0051.2018.1015.1513 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:BB:60:50:92:5D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1912660 acl:106009 sco:0 events:337 errors:0 TX bytes:12331 acl:74 sco:0 commands:204 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1823076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815987] Re: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS
Bump. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1815987 Title: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS Status in systemd package in Ubuntu: New Bug description: I am using Ubuntu 18.04LTS, fresh install from the summer, and tmpfiles won't launch since November. $ sudo systemctl start systemd-tmpfiles-setup Job for systemd-tmpfiles-setup.service failed because the control process exited with error code. See "systemctl status systemd-tmpfiles-setup.service" and "journalctl -xe" for details. $ sudo systemctl status systemd-tmpfiles-setup ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2019-02-14 19:48:36 EST; 8s ago Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Process: 28934 ExecStart=/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE) Main PID: 28934 (code=exited, status=1/FAILURE) Feb 14 19:48:35 mythserver2018 systemd[1]: Starting Create Volatile Files and Directories... Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/colord/icc, refusing. Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing. Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Feb 14 19:48:36 mythserver2018 systemd[1]: Failed to start Create Volatile Files and Directories. Looking at /var/lib/colord/icc: kris@mythserver2018:/var/lib/colord/icc$ ls -a . .. kris@mythserver2018:/var/lib/colord/icc$ I have also deleted these directories and rebuilt them, just to be sure - they are NOT symlinked and have no permission issues: kris@mythserver2018:/var/lib/systemd$ ls -l total 28 drwxr-xr-x 2 root root 4096 Feb 9 16:04 catalog drwxr-xr-x 2 root root 4096 Dec 28 07:04 coredump drwxr-xr-x 2 root root 4096 Jul 8 2018 coredumpold drwxr-xr-x 20 root root 4096 Feb 9 16:08 deb-systemd-helper-enabled drwxr-xr-x 2 root root 4096 Nov 14 18:31 deb-systemd-helper-masked -rw--- 1 root root 512 Feb 9 17:34 random-seed drwxr-xr-x 2 root root 4096 Jul 10 2018 timers lrwxrwxrwx 1 root root 27 Jul 8 2018 timesync -> ../private/systemd/timesync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1815987/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823076] [NEW] Intel NUC (8I3BEH1) wakes up immediately after suspend after installing BlueZ
Public bug reported: After replacing my USB mouse with a BT mouse, I noticed my machine would no longer suspend without immediately waking up. i.e. I suspend and see the light go into the slow fade in and out for one cycle and then goes solid and the display wakes up again. If I disable BT (via blueman applet) suspend works fine. I've fixed this by shutting down the BT service before suspend, and starting it back up on wake, as indicated here: https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately- after-suspend Perhaps this script should be included in blueZ as suspend issues seem very hard to debug and the immediate wake after suspend could be caused many any number of things. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Apr 3 13:16:14 2019 InstallationDate: Installed on 2019-02-09 (53 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems NUC8i3BEH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0051.2018.1015.1513 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0: Type: Primary Bus: USB BD Address: 00:BB:60:50:92:5D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1912660 acl:106009 sco:0 events:337 errors:0 TX bytes:12331 acl:74 sco:0 commands:204 errors:0 ** Affects: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1823076 Title: Intel NUC (8I3BEH1) wakes up immediately after suspend after installing BlueZ Status in bluez package in Ubuntu: New Bug description: After replacing my USB mouse with a BT mouse, I noticed my machine would no longer suspend without immediately waking up. i.e. I suspend and see the light go into the slow fade in and out for one cycle and then goes solid and the display wakes up again. If I disable BT (via blueman applet) suspend works fine. I've fixed this by shutting down the BT service before suspend, and starting it back up on wake, as indicated here: https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately- after-suspend Perhaps this script should be included in blueZ as suspend issues seem very hard to debug and the immediate wake after suspend could be caused many any number of things. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Apr 3 13:16:14 2019 InstallationDate: Installed on 2019-02-09 (53 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems NUC8i3BEH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0051.2018.1015.1513 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type:
[Touch-packages] [Bug 1815987] Re: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS
Ext4... the last two messages in that thread direct me to open a new bug, so I have. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1815987 Title: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS Status in systemd package in Ubuntu: New Bug description: I am using Ubuntu 18.04LTS, fresh install from the summer, and tmpfiles won't launch since November. $ sudo systemctl start systemd-tmpfiles-setup Job for systemd-tmpfiles-setup.service failed because the control process exited with error code. See "systemctl status systemd-tmpfiles-setup.service" and "journalctl -xe" for details. $ sudo systemctl status systemd-tmpfiles-setup ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2019-02-14 19:48:36 EST; 8s ago Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Process: 28934 ExecStart=/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE) Main PID: 28934 (code=exited, status=1/FAILURE) Feb 14 19:48:35 mythserver2018 systemd[1]: Starting Create Volatile Files and Directories... Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/colord/icc, refusing. Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing. Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Feb 14 19:48:36 mythserver2018 systemd[1]: Failed to start Create Volatile Files and Directories. Looking at /var/lib/colord/icc: kris@mythserver2018:/var/lib/colord/icc$ ls -a . .. kris@mythserver2018:/var/lib/colord/icc$ I have also deleted these directories and rebuilt them, just to be sure - they are NOT symlinked and have no permission issues: kris@mythserver2018:/var/lib/systemd$ ls -l total 28 drwxr-xr-x 2 root root 4096 Feb 9 16:04 catalog drwxr-xr-x 2 root root 4096 Dec 28 07:04 coredump drwxr-xr-x 2 root root 4096 Jul 8 2018 coredumpold drwxr-xr-x 20 root root 4096 Feb 9 16:08 deb-systemd-helper-enabled drwxr-xr-x 2 root root 4096 Nov 14 18:31 deb-systemd-helper-masked -rw--- 1 root root 512 Feb 9 17:34 random-seed drwxr-xr-x 2 root root 4096 Jul 10 2018 timers lrwxrwxrwx 1 root root 27 Jul 8 2018 timesync -> ../private/systemd/timesync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1815987/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815987] Re: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS
Bump. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1815987 Title: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS Status in systemd package in Ubuntu: New Bug description: I am using Ubuntu 18.04LTS, fresh install from the summer, and tmpfiles won't launch since November. $ sudo systemctl start systemd-tmpfiles-setup Job for systemd-tmpfiles-setup.service failed because the control process exited with error code. See "systemctl status systemd-tmpfiles-setup.service" and "journalctl -xe" for details. $ sudo systemctl status systemd-tmpfiles-setup ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2019-02-14 19:48:36 EST; 8s ago Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Process: 28934 ExecStart=/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE) Main PID: 28934 (code=exited, status=1/FAILURE) Feb 14 19:48:35 mythserver2018 systemd[1]: Starting Create Volatile Files and Directories... Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/colord/icc, refusing. Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing. Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Feb 14 19:48:36 mythserver2018 systemd[1]: Failed to start Create Volatile Files and Directories. Looking at /var/lib/colord/icc: kris@mythserver2018:/var/lib/colord/icc$ ls -a . .. kris@mythserver2018:/var/lib/colord/icc$ I have also deleted these directories and rebuilt them, just to be sure - they are NOT symlinked and have no permission issues: kris@mythserver2018:/var/lib/systemd$ ls -l total 28 drwxr-xr-x 2 root root 4096 Feb 9 16:04 catalog drwxr-xr-x 2 root root 4096 Dec 28 07:04 coredump drwxr-xr-x 2 root root 4096 Jul 8 2018 coredumpold drwxr-xr-x 20 root root 4096 Feb 9 16:08 deb-systemd-helper-enabled drwxr-xr-x 2 root root 4096 Nov 14 18:31 deb-systemd-helper-masked -rw--- 1 root root 512 Feb 9 17:34 random-seed drwxr-xr-x 2 root root 4096 Jul 10 2018 timers lrwxrwxrwx 1 root root 27 Jul 8 2018 timesync -> ../private/systemd/timesync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1815987/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815987] Re: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS
Bump. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1815987 Title: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS Status in systemd package in Ubuntu: New Bug description: I am using Ubuntu 18.04LTS, fresh install from the summer, and tmpfiles won't launch since November. $ sudo systemctl start systemd-tmpfiles-setup Job for systemd-tmpfiles-setup.service failed because the control process exited with error code. See "systemctl status systemd-tmpfiles-setup.service" and "journalctl -xe" for details. $ sudo systemctl status systemd-tmpfiles-setup ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2019-02-14 19:48:36 EST; 8s ago Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Process: 28934 ExecStart=/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE) Main PID: 28934 (code=exited, status=1/FAILURE) Feb 14 19:48:35 mythserver2018 systemd[1]: Starting Create Volatile Files and Directories... Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/colord/icc, refusing. Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing. Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Feb 14 19:48:36 mythserver2018 systemd[1]: Failed to start Create Volatile Files and Directories. Looking at /var/lib/colord/icc: kris@mythserver2018:/var/lib/colord/icc$ ls -a . .. kris@mythserver2018:/var/lib/colord/icc$ I have also deleted these directories and rebuilt them, just to be sure - they are NOT symlinked and have no permission issues: kris@mythserver2018:/var/lib/systemd$ ls -l total 28 drwxr-xr-x 2 root root 4096 Feb 9 16:04 catalog drwxr-xr-x 2 root root 4096 Dec 28 07:04 coredump drwxr-xr-x 2 root root 4096 Jul 8 2018 coredumpold drwxr-xr-x 20 root root 4096 Feb 9 16:08 deb-systemd-helper-enabled drwxr-xr-x 2 root root 4096 Nov 14 18:31 deb-systemd-helper-masked -rw--- 1 root root 512 Feb 9 17:34 random-seed drwxr-xr-x 2 root root 4096 Jul 10 2018 timers lrwxrwxrwx 1 root root 27 Jul 8 2018 timesync -> ../private/systemd/timesync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1815987/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817424] Re: Unable to resolve local DNS names provided by router on bootup.
Correction, service systemd-resolved restart does not solve the problem. Only systemd-resolve --flush-caches fixed the problem temporarily. -- 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/1817424 Title: Unable to resolve local DNS names provided by router on bootup. Status in systemd package in Ubuntu: New Bug description: On boot, I can see systemd-resolve is configured properly; the router (192.168.1.254) is listed as a DNS server: $ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 3 (wlp0s20f3) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 2 (eno1) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.1.254 DNS Domain: telus Local names are not resolved: $ nslookup zf1 Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find zf1: SERVFAIL $ dig zf1 ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> zf1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 39908 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;zf1. IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Sat Feb 23 09:46:12 PST 2019 ;; MSG SIZE rcvd: 32 Restarting netplan and network-manager services make no difference. Restarting the systemd-resolved (or clearing systemd-resolved caches) solve the problem: $ sudo systemd-resolve --flush-caches OR $ sudo service systemd-resolved restart $ nslookup zf1 Server: 127.0.0.53 Address: 127.0.0.53#53 Non-authoritative answer: Name: zf1.telus Address: 192.168.1.71 ** server can't find zf1.telus: NXDOMAIN Dig still can't find server though: $ dig zf1 ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> zf1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 20375 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;zf1. IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Sat Feb 23 09:47:38 PST 2019 ;; MSG SIZE rcvd: 32 Unless I specify the server manually: $ dig @192.168.1.254 zf1 ;; Warning: Message parser reports malformed message packet. ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> @192.168.1.254 zf1 ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50811 ;; flags: qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ; COOKIE: 94b92f65104856d4 (echoed) ;; QUESTION SECTION: ;zf1. IN A ;; ADDITIONAL SECTION: zf1. 1 IN A 192.168.1.71 ;; Query time: 6 msec ;; SERVER: 192.168.1.254#53(192.168.1.254) ;; WHEN: Sat Feb 23 09:59:05 PST 2019 ;; MSG SIZE rcvd: 60 Once I get local names resolved, the systemd-resolve status remains the same: $ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa
[Touch-packages] [Bug 1817424] [NEW] Unable to resolve local DNS names provided by router on bootup.
Public bug reported: On boot, I can see systemd-resolve is configured properly; the router (192.168.1.254) is listed as a DNS server: $ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 3 (wlp0s20f3) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 2 (eno1) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.1.254 DNS Domain: telus Local names are not resolved: $ nslookup zf1 Server: 127.0.0.53 Address:127.0.0.53#53 ** server can't find zf1: SERVFAIL $ dig zf1 ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> zf1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 39908 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;zf1. IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Sat Feb 23 09:46:12 PST 2019 ;; MSG SIZE rcvd: 32 Restarting netplan and network-manager services make no difference. Restarting the systemd-resolved (or clearing systemd-resolved caches) solve the problem: $ sudo systemd-resolve --flush-caches OR $ sudo service systemd-resolved restart $ nslookup zf1 Server: 127.0.0.53 Address:127.0.0.53#53 Non-authoritative answer: Name: zf1.telus Address: 192.168.1.71 ** server can't find zf1.telus: NXDOMAIN Dig still can't find server though: $ dig zf1 ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> zf1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 20375 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;zf1. IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Sat Feb 23 09:47:38 PST 2019 ;; MSG SIZE rcvd: 32 Unless I specify the server manually: $ dig @192.168.1.254 zf1 ;; Warning: Message parser reports malformed message packet. ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> @192.168.1.254 zf1 ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50811 ;; flags: qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ; COOKIE: 94b92f65104856d4 (echoed) ;; QUESTION SECTION: ;zf1. IN A ;; ADDITIONAL SECTION: zf1.1 IN A 192.168.1.71 ;; Query time: 6 msec ;; SERVER: 192.168.1.254#53(192.168.1.254) ;; WHEN: Sat Feb 23 09:59:05 PST 2019 ;; MSG SIZE rcvd: 60 Once I get local names resolved, the systemd-resolve status remains the same: $ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 3 (wlp0s20f3) Current Scopes: none
[Touch-packages] [Bug 1815987] [NEW] Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS
Public bug reported: I am using Ubuntu 18.04LTS, fresh install from the summer, and tmpfiles won't launch since November. $ sudo systemctl start systemd-tmpfiles-setup Job for systemd-tmpfiles-setup.service failed because the control process exited with error code. See "systemctl status systemd-tmpfiles-setup.service" and "journalctl -xe" for details. $ sudo systemctl status systemd-tmpfiles-setup ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2019-02-14 19:48:36 EST; 8s ago Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Process: 28934 ExecStart=/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE) Main PID: 28934 (code=exited, status=1/FAILURE) Feb 14 19:48:35 mythserver2018 systemd[1]: Starting Create Volatile Files and Directories... Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/colord/icc, refusing. Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing. Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Feb 14 19:48:36 mythserver2018 systemd[1]: Failed to start Create Volatile Files and Directories. Looking at /var/lib/colord/icc: kris@mythserver2018:/var/lib/colord/icc$ ls -a . .. kris@mythserver2018:/var/lib/colord/icc$ I have also deleted these directories and rebuilt them, just to be sure - they are NOT symlinked and have no permission issues: kris@mythserver2018:/var/lib/systemd$ ls -l total 28 drwxr-xr-x 2 root root 4096 Feb 9 16:04 catalog drwxr-xr-x 2 root root 4096 Dec 28 07:04 coredump drwxr-xr-x 2 root root 4096 Jul 8 2018 coredumpold drwxr-xr-x 20 root root 4096 Feb 9 16:08 deb-systemd-helper-enabled drwxr-xr-x 2 root root 4096 Nov 14 18:31 deb-systemd-helper-masked -rw--- 1 root root 512 Feb 9 17:34 random-seed drwxr-xr-x 2 root root 4096 Jul 10 2018 timers lrwxrwxrwx 1 root root 27 Jul 8 2018 timesync -> ../private/systemd/timesync ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1815987 Title: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS Status in systemd package in Ubuntu: New Bug description: I am using Ubuntu 18.04LTS, fresh install from the summer, and tmpfiles won't launch since November. $ sudo systemctl start systemd-tmpfiles-setup Job for systemd-tmpfiles-setup.service failed because the control process exited with error code. See "systemctl status systemd-tmpfiles-setup.service" and "journalctl -xe" for details. $ sudo systemctl status systemd-tmpfiles-setup ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2019-02-14 19:48:36 EST; 8s ago Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Process: 28934 ExecStart=/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE) Main PID: 28934 (code=exited, status=1/FAILURE) Feb 14 19:48:35 mythserver2018 systemd[1]: Starting Create Volatile Files and Directories... Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/colord/icc, refusing. Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing. Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Feb 14 19:48:36 mythserver2018 systemd[1]: Failed to start Create Volatile Files and Directories. Looking at /var/lib/colord/icc: kris@mythserver2018:/var/lib/colord/icc$ ls -a . .. kris@mythserver2018:/var/lib/colord/icc$ I have also deleted these directories and rebuilt them, just to be sure - they are NOT symlinked and have no permission issues: kris@mythserver2018:/var/lib/systemd$ ls -l total 28 drwxr-xr-x 2 root root 4096 Feb 9 16:04 catalog drwxr-xr-x 2 root root 4096 Dec 28 07:04 coredump drwxr-xr-x 2 root root 4096 Jul 8 2018 coredumpold drwxr-xr-x 20 root root 4096 Feb 9 16:08 deb-systemd-helper-enabled drwxr-xr-x 2 root root 4096 Nov 14 18:31 deb-systemd-helper-masked -rw--- 1 root root
[Touch-packages] [Bug 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
Jurit - I tried that months ago as documented in the forums. Didnt fix the issue. I also have run the sudo apt-get upgrade several times as well - still not fixed for me. I also see they did push a new kernel - still occurs. Not sure what else I can do... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] * Last security update introduced a regression on btrfs based systems, causing systemd-tmpfiles-setup.service to fail to start, resulting in degraded machines. * Cherrypick upstream fixes to resolve this. [Test Case] * Install VM using btrfs for / * Boot, check that systemd-tmpfiles-setup.service is started successfully with: $ systemctl status systemd-tmpfiles-setup.service [Regression Potential] * btrfs fd doesn't support the set of flags that systemd used, with this patch, a compat set of flags is set instead, thus resolving the introduced regression. The worst case scenario is that creating subvolumes/directories is still broken (as in, the current status quo). [Other Info] * Example bad output After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service fails with: Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and Directories... Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/var": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/home": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/srv": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files and Directories. This happens on btrfs root filesystems in real hardware and on our virtualized servers as well. 237-3ubuntu10.6 didnt show this errors and going back to 237-3ubuntu10 removes them as well. # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
Srill happening on 18.04LTS with ext4fs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] * Last security update introduced a regression on btrfs based systems, causing systemd-tmpfiles-setup.service to fail to start, resulting in degraded machines. * Cherrypick upstream fixes to resolve this. [Test Case] * Install VM using btrfs for / * Boot, check that systemd-tmpfiles-setup.service is started successfully with: $ systemctl status systemd-tmpfiles-setup.service [Regression Potential] * btrfs fd doesn't support the set of flags that systemd used, with this patch, a compat set of flags is set instead, thus resolving the introduced regression. The worst case scenario is that creating subvolumes/directories is still broken (as in, the current status quo). [Other Info] * Example bad output After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service fails with: Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and Directories... Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/var": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/home": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/srv": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files and Directories. This happens on btrfs root filesystems in real hardware and on our virtualized servers as well. 237-3ubuntu10.6 didnt show this errors and going back to 237-3ubuntu10 removes them as well. # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
Still happening for me on 18.04 LTS... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] * Last security update introduced a regression on btrfs based systems, causing systemd-tmpfiles-setup.service to fail to start, resulting in degraded machines. * Cherrypick upstream fixes to resolve this. [Test Case] * Install VM using btrfs for / * Boot, check that systemd-tmpfiles-setup.service is started successfully with: $ systemctl status systemd-tmpfiles-setup.service [Regression Potential] * btrfs fd doesn't support the set of flags that systemd used, with this patch, a compat set of flags is set instead, thus resolving the introduced regression. The worst case scenario is that creating subvolumes/directories is still broken (as in, the current status quo). [Other Info] * Example bad output After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service fails with: Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and Directories... Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/var": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/home": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/srv": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files and Directories. This happens on btrfs root filesystems in real hardware and on our virtualized servers as well. 237-3ubuntu10.6 didnt show this errors and going back to 237-3ubuntu10 removes them as well. # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
This bug made using emacs and IntelliJ Idea a nuisance. I found a simple workaround. 0 =1= You can verify how ALT and SHIFT are not being detected simultaneously by running $ xkbwatch Notice how the blinky lights change for ALT and for SHIFT but not for both at the same time. =2= $ setxkbmap -query rules: evdev model: pc105 layout: us,us,us variant:,intl, options:grp:alt_shift_toggle,grp_led:scroll THIS IS THE PROBLEM =3= We will now unset ALT-SHIFT toggle. $ setxkbmap -option -option grp_led:scroll ^^^ DELIBERATELY EMPTY The first empty -option erases all options, the second one just carries over an option we want to keep. Additional -option clauses can preserve other preexisting options. I can still change to next/previous input source with whatever is configured in Settings/Keyboard/Typing =4= Do step =2= again and notice how ALT and SHIFT now play together simultaneously. I am now a happy Emacs and IntelliJ user. This is a single command workaround. -- 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/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default Status in console-setup package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in console-setup source package in Bionic: Fix Released Status in gnome-control-center source package in Bionic: Invalid Bug description: [Impact] The keyboard-configuration package provides a tool for configuring the keyboard via /etc/default/keyboard. However, there are desktop GUIs which provide such tools as well, and in the case of gnome-control- center it has another idea of what /etc/default/keyboard should contain. In short: The different tools don't play well together. The proposed upload does not claim to fix all issues with this incompatibility. But one of the annoyances is that a pure upgrade of the keyboard-configuration package may result in a changed keyboard configuration without the user asking for it. The proposed upload does address that particular issue on desktop systems. [Test Case] 1. On an Ubuntu 18.04 system, make sure that the contents of /etc/default/keyboard is 'the g-c-c style', for instance: XKBLAYOUT=se,us BACKSPACE=guess XKBVARIANT=, 2. Reboot. 3. Upgrade to the version of the keyboard-configuration package in bionic-proposed. => Find that /etc/default/keyboard was not changed through the upgrade. 4. Run the command sudo dpkg-reconfigure keyboard-configuration => Find that you are now offered to change your keyboard configuration. [Regression Potential] As a result of this upload, and unlike before, no keyboard configuration will happen behind the scenes on a desktop system due to an upgrade of the keyboard-configuration package. This is the desired change, and I can't think of a case when a user would want the configuration to be changed without having asked for it. [Original description] Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in 18.04 Steps to reproduce: 1. Define two keyboard input methods in Settings -> Region & Language -> Input Sources 2. Open several applications 3. Observe that application windows can be iterated with Alt + Tab 4. Once application window iteration was begun with Alt + Tab, try to iterate backwards with Alt + Shift + Tab. 5. Try to change keyboard input method switching hotkeys in Settings -> Region & Language -> Input Sources -> Options. 6. Observe that Keyboard shortcut for "Alternative switch to next source" is set to "Alt + Shift" and that keyboard shortcuts can only be changed in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. 7. Observe that the shortcut for "Alternative switch to next source" is not available for configuration in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Actual state: * Performing step 4 does not select the previous app in application switcher but instead changes keyboard input method. Expected state: * The shortcut for "Alternative switch to next source" can be changed and / or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Notes: * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to next source" did not exist in that version of Gnome Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800329] Re: Ubnutu 18.04 LTS KDE Neon does not resolve local (or single name) queries through DHCP assigned DNS (cached) server on local network
I tried to find a reasonable solution and looks that there are different approaches. I wanted to stay at most within the distribution layout while keeping all business requirements fulfilled. This is what I tested: ```code # Install required package and reconfigure service plans (i.e. disable systemd-resolved, enable dnsmasq sudo apt-get install dnsmasq sudo systemctl disable systemd-resolved sudo systemctl stop systemd-resolved sudo systemctl enable dnsmasq # These two lines should work on most environments, but .. :-) # Just add or change 'dns=dnsmasq' to your NetworkManager.conf to the section [main] #sudo cp /etc/NetworkManager/NetworkManager.conf /etc/NetworkManager/NetworkManager.conf.backup #sudo bash -c 'cat /etc/NetworkManager/NetworkManager.conf.backup |sed -e "s/^dns=.*//"| sed -e "s/\[main\]/\[main\]\ndns=dnsmasq/" >/etc/NetworkManager/NetworkManager.conf' # Restart NetworkManager to make the change above applied sudo systemctl restart NetworkManager # This removes the systemd resolv.conf link only if it has NetworkManager replacement :-) ls /var/run/NetworkManager/resolv.conf && sudo rm /etc/resolv.conf # And add NetworkManager's resolv.conf available for the system resolver sudo ln -s /var/run/NetworkManager/resolv.conf /etc/resolv.conf ``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1800329 Title: Ubnutu 18.04 LTS KDE Neon does not resolve local (or single name) queries through DHCP assigned DNS (cached) server on local network Status in systemd package in Ubuntu: Confirmed Bug description: Ubnutu 18.04 KDE Neon does not resolve local (or single name) queries through DHCP assigned DNS (cached) server on local network. ** How to reproduce? ** 1. Let's have local network (e.g. 192.168.123.0/24) connected to the Internet through router called GATE 2. The GATE provides local DNS server cache (via Dnsmasq) and contains couple of local name translations (e.g. SuperCooolLocalServer pointing to 192.168.123.50). 3. Let's have fresh new Ubuntu 18.04 (KDE Neon) 4. Connect to the local network through WIFI (WPA2 encrypted, jsut enter password) ** What happens? ** Any desktop application trying to connect to SuperCooolLocalServer will fail when resolving the name to IP. When tested in terminal "host SuperCooolLocalServer" will return SERVFAIL. ** What is expected? ** The system should resolve the name SuperCooolLocalServer to 192.168.123.50 as it did until Ubuntu 16.04 LTS. ** Observation ** The system should do the resolution in the same logic as other home appliances running various operating systems (my iPhone, my wife's Galaxy, ours Ubuntu 16.04LTS, Windows 7, 8.1 10 and our other network components running various Linux based distributions.) I did quick test and the bug shows also on clean Ubuntu 18.04 (without the KDE Neon flavour). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1800329/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792820] [NEW] help you me
Public bug reported: I don#t know what i am doing. How can I help you? help you me ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Sep 16 22:33:39 2018 DistUpgraded: 2018-09-04 07:33:08,269 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8180] [1002:9839] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Kabini [Radeon HD 8180] [1043:141d] InstallationDate: Installed on 2016-10-16 (700 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X102BA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=UUID=b4b46cc3-3ea0-41d0-8266-15beb0306075 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-04 (12 days ago) dmi.bios.date: 12/31/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X102BA.219 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X102BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX102BA.219:bd12/31/2013:svnASUSTeKCOMPUTERINC.:pnX102BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX102BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X102BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Sep 3 23:15:32 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1792820 Title: help you me Status in xorg package in Ubuntu: New Bug description: I don#t know what i am doing. How can I help you? help you me ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Sep 16 22:33:39 2018 DistUpgraded: 2018-09-04 07:33:08,269 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8180] [1002:9839] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Kabini [Radeon HD 8180] [1043:141d] InstallationDate: Installed on 2016-10-16 (700 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X102BA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=UUID=b4b46cc3-3ea0-41d0-8266-15beb0306075 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-04 (12 days ago) dmi.bios.date: 12/31/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X102BA.219 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X102BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX102BA.219:bd12/31/2013:svnASUSTeKCOMPUTERINC.:pnX102BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX102BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X102BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libg
[Touch-packages] [Bug 1789516] [NEW] ubuntu-bug crashes when filing bug for usb storage when udisks2 is not installed.
Public bug reported: If udisks2 is not installed, the following actions cause ubuntu-bug to crash: 1. Run ubuntu-bug 2. Click on "External or internal storage devices" -> OK 3. Click on "Removable storage device is not mounted automatically" -> OK 4. Click Close 5. Connect offending device 6. Click Close Result: ERROR: symptom script /usr/share/apport/symptoms/storage.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/ui.py", line 108, in thread_collect_info package = symb['run'](report, ui) File "/usr/share/apport/symptoms/storage.py", line 29, in run return problem_removable(report, ui) File "/usr/share/apport/symptoms/storage.py", line 52, in problem_removable universal_newlines=True) File "/usr/lib/python3.6/subprocess.py", line 709, in __init__ restore_signals, start_new_session) File "/usr/lib/python3.6/subprocess.py", line 1344, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'udisksctl': 'udisksctl' Installing udisks2 solves the issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportLog: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CrashReports: 640:1000:134:5505230:2018-08-20 12:15:41.972497262 -0700:2018-08-20 12:15:29.675580645 -0700:/var/crash/_usr_bin_lyx.1000.crash 600:0:134:1189445:2018-08-20 17:04:50.652675440 -0700:2018-08-20 17:04:49.540680686 -0700:/var/crash/indicator-applet-session.0.crash 600:0:134:1058633:2018-08-20 13:12:02.353175760 -0700:2018-08-20 13:12:01.353169322 -0700:/var/crash/texlive-fonts-extra-doc.0.crash 640:0:134:2053111:2018-08-20 13:54:02.571655686 -0700:2018-08-20 13:53:55.195695778 -0700:/var/crash/_usr_sbin_synaptic.0.crash CurrentDesktop: XFCE Date: Tue Aug 28 16:37:24 2018 InstallationDate: Installed on 2010-11-05 (2853 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-08-16 (12 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-hook-error bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1789516 Title: ubuntu-bug crashes when filing bug for usb storage when udisks2 is not installed. Status in apport package in Ubuntu: New Bug description: If udisks2 is not installed, the following actions cause ubuntu-bug to crash: 1. Run ubuntu-bug 2. Click on "External or internal storage devices" -> OK 3. Click on "Removable storage device is not mounted automatically" -> OK 4. Click Close 5. Connect offending device 6. Click Close Result: ERROR: symptom script /usr/share/apport/symptoms/storage.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/ui.py", line 108, in thread_collect_info package = symb['run'](report, ui) File "/usr/share/apport/symptoms/storage.py", line 29, in run return problem_removable(report, ui) File "/usr/share/apport/symptoms/storage.py", line 52, in problem_removable universal_newlines=True) File "/usr/lib/python3.6/subprocess.py", line 709, in __init__ restore_signals, start_new_session) File "/usr/lib/python3.6/subprocess.py", line 1344, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'udisksctl': 'udisksctl' Installing udisks2 solves the issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportLog: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CrashReports: 640:1000:134:5505230:2018-08-20 12:15:41.972497262 -0700:2018-08-20 12:15:29.675580645 -0700:/var/crash/_usr_bin_lyx.1000.crash 600:0:134:1189445:2018-08-20 17:04:50.652675440 -0700:2018-08-20 17:04:49.540680686 -0700:/var/crash/indicator-applet-session.0.crash 600:0:134:1058633:2018-08-20 13:12:02.353175760 -0700:2018-08-20 13:12:01.353169322 -0700:/var/crash/texlive-fonts-extra-doc.0.crash 640:0:134:2053111:2018-08-20 13:54:02.571655686 -0700:2018-08-20 13:53:55.195695778 -0700:/var/crash/_usr_sbin_synaptic.0.crash CurrentDesktop: XFCE Date: Tue Aug 28 16:37:24 2018 InstallationDate: Installed on 2010-11-05 (2853 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-08-16 (12 days ago) To manage notifications about this bug go to: https://
[Touch-packages] [Bug 1784289] Re: package systemd 229-4ubuntu21.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to install/upgrade: subprocess installed pre-rem
Reinstalled mysql to fix the issue ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1784289 Title: package systemd 229-4ubuntu21.2 [modified: usr/share/dbus-1/system- services/org.freedesktop.systemd1.service] failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in systemd package in Ubuntu: Invalid Bug description: I had to completely remove mysql server after an upgrade to 16.04 which installed upstart. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu21.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon Jul 30 11:01:38 2018 DpkgTerminalLog: Removing systemd (229-4ubuntu21.2) ... systemd is the active init system, please switch to another before removing systemd. dpkg: error processing package systemd (--purge): subprocess installed pre-removal script returned error exit status 1 DuplicateSignature: package:systemd:229-4ubuntu21.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] Removing systemd (229-4ubuntu21.2) ... systemd is the active init system, please switch to another before removing systemd. dpkg: error processing package systemd (--purge): subprocess installed pre-removal script returned error exit status 1 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2018-05-29 (61 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Dell Inc. Latitude 3460 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=2f7bff7f-36fa-4631-b297-9ca03f7ed302 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: systemd Title: package systemd 229-4ubuntu21.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 09CGMV dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd01/23/2018:svnDellInc.:pnLatitude3460:pvr:rvnDellInc.:rn09CGMV:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3460 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1784289/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784289] [NEW] package systemd 229-4ubuntu21.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to install/upgrade: subprocess installed pre-r
Public bug reported: I had to completely remove mysql server after an upgrade to 16.04 which installed upstart. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu21.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon Jul 30 11:01:38 2018 DpkgTerminalLog: Removing systemd (229-4ubuntu21.2) ... systemd is the active init system, please switch to another before removing systemd. dpkg: error processing package systemd (--purge): subprocess installed pre-removal script returned error exit status 1 DuplicateSignature: package:systemd:229-4ubuntu21.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] Removing systemd (229-4ubuntu21.2) ... systemd is the active init system, please switch to another before removing systemd. dpkg: error processing package systemd (--purge): subprocess installed pre-removal script returned error exit status 1 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2018-05-29 (61 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Dell Inc. Latitude 3460 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=2f7bff7f-36fa-4631-b297-9ca03f7ed302 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: systemd Title: package systemd 229-4ubuntu21.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 09CGMV dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd01/23/2018:svnDellInc.:pnLatitude3460:pvr:rvnDellInc.:rn09CGMV:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3460 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1784289 Title: package systemd 229-4ubuntu21.2 [modified: usr/share/dbus-1/system- services/org.freedesktop.systemd1.service] failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: I had to completely remove mysql server after an upgrade to 16.04 which installed upstart. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu21.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon Jul 30 11:01:38 2018 DpkgTerminalLog: Removing systemd (229-4ubuntu21.2) ... systemd is the active init system, please switch to another before removing systemd. dpkg: error processing package systemd (--purge): subprocess installed pre-removal script returned error exit status 1 DuplicateSignature: package:systemd:229-4ubuntu21.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] Removing systemd (229-4ubuntu21.2) ... systemd is the active init system, please switch to another before removing systemd. dpkg: error processing package systemd (--purge): subprocess installed pre-removal script returned error exit status 1 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2018-05-29 (61 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Dell Inc. Latitude 3460 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=2f7bff7f-36fa-4631-b297-9ca03f7ed302 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: systemd Title: package systemd 229-4ubuntu21.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 09CGMV dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA
[Touch-packages] [Bug 1784161] Re: Mouse inoperative in other apps while Shotwell is uploading to Flickr
Adding some detail here: Switching back to xorg reproduces the bug 100%. I can click on the launcher, it seems to be the only thing that'll receive my clicks while the bug is active, but new apps launched while the bug is active are also unable to see mouse clicks. Kernel is 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:39:52 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux shotwell is 0.28.2 that came preinstalled, I've done nothing to it other than import a folder of photos and authenticate with Flickr for my upload key. -- 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/1784161 Title: Mouse inoperative in other apps while Shotwell is uploading to Flickr Status in xorg package in Ubuntu: New Bug description: I'm using Shotwell to Publish (ctrl+shift+P) photos to Flickr. Some of these uploads take quite a while, so I'd like to do other things while they're running. If I alt-tab over to Firefox or Slack or whatever, my mouse works normally, but if I alt-tab back to Shotwell to peek if the upload has completed yet, and then alt-tab over to another app again, now my mouse doesn't work. Pointer moves, yes. Doesn't produce mouse-over events, doesn't click, doesn't scroll. As soon as the upload completes in Shotwell, the mouse works normally again. I popped into freenode/#ubuntu IRC and they suggested trying Wayland. This behavior does not occur in Wayland, so it was suggested that I report it here under xorg. I'm running Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1784161/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784161] [NEW] Mouse inoperative in other apps while Shotwell is uploading to Flickr
Public bug reported: I'm using Shotwell to Publish (ctrl+shift+P) photos to Flickr. Some of these uploads take quite a while, so I'd like to do other things while they're running. If I alt-tab over to Firefox or Slack or whatever, my mouse works normally, but if I alt-tab back to Shotwell to peek if the upload has completed yet, and then alt-tab over to another app again, now my mouse doesn't work. Pointer moves, yes. Doesn't produce mouse-over events, doesn't click, doesn't scroll. As soon as the upload completes in Shotwell, the mouse works normally again. I popped into freenode/#ubuntu IRC and they suggested trying Wayland. This behavior does not occur in Wayland, so it was suggested that I report it here under xorg. I'm running Ubuntu 18.04 LTS. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- 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/1784161 Title: Mouse inoperative in other apps while Shotwell is uploading to Flickr Status in xorg package in Ubuntu: New Bug description: I'm using Shotwell to Publish (ctrl+shift+P) photos to Flickr. Some of these uploads take quite a while, so I'd like to do other things while they're running. If I alt-tab over to Firefox or Slack or whatever, my mouse works normally, but if I alt-tab back to Shotwell to peek if the upload has completed yet, and then alt-tab over to another app again, now my mouse doesn't work. Pointer moves, yes. Doesn't produce mouse-over events, doesn't click, doesn't scroll. As soon as the upload completes in Shotwell, the mouse works normally again. I popped into freenode/#ubuntu IRC and they suggested trying Wayland. This behavior does not occur in Wayland, so it was suggested that I report it here under xorg. I'm running Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1784161/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1729357]
All updates released.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1729357
Title:
unprivileged user can drop supplementary groups
Status in shadow package in Ubuntu:
Confirmed
Status in shadow package in openSUSE:
Fix Released
Bug description:
Distribution: Ubuntu 16.04.3 LTS
Kernel: 4.4.0-97-generic
uidmap package version: 1:4.2-3.1ubuntu5.3
The newgidmap setuid executable allows any user to write a single
mapping line to the gid_map of a process whose identity is the same as
the calling process, as long as that mapping line maps the process's
own GID outside of the user namespace to GID 0 inside the user
namespace.
Newgidmap will write the mapping regardless of the content of
/proc/$process_being_mapped/setgroups, which will initially contain
the string "allow". After this mapping is performed, and also after
the process' uid_map is written with newuidmap, the process in the
user namespace will be able to use the setgroups system call to drop
supplementary groups.
This is possible even if there is no entry for the user in
/etc/subgid, because no subordinate GIDs are actually being used.
This allows any user to circumvent the use of supplementary groups as
blacklists, e.g. for some file owned by root:blacklist with permission
bits 0604 (octal). Normally any process whose identity included the
group "blacklist" in its supplementary groups would not be able to
read that file. By performing this exploit using newgidmap, they can
drop all supplementary groups and read that file.
If newgidmap was not available, unprivileged users would not be able
to write a process's gid_map until writing "deny" to
/proc/$pid/setgroups. A fix for this might be for newgidmap to check
the content of /proc/$process_being_mapped/setgroups is "deny", but we
have not tried to patch this ourselves.
An example using 2 login shells for a user named "someone" on Ubuntu
Xenial, with the uidmap package installed:
Shell 1
someone@ubuntu-xenial:~$ id
uid=1001(someone) gid=1001(someone) groups=1001(someone),1002(restricted)
someone@ubuntu-xenial:~$ ls -al /tmp/should_restrict
-rwr-- 1 root restricted 8 Nov 1 12:23 /tmp/should_restrict
someone@ubuntu-xenial:~$ cat /tmp/should_restrict
cat: /tmp/should_restrict: Permission denied
someone@ubuntu-xenial:~$ unshare -U --setgroups allow #
/proc/self/setgroups already contains 'allow', but let's be explicit
nobody@ubuntu-xenial:~$ echo $$
1878
Shell 2
someone@ubuntu-xenial:~$ cat /etc/subuid
lxd:10:65536
root:10:65536
ubuntu:165536:65536
someone@ubuntu-xenial:~$ cat /etc/subgid
lxd:10:65536
root:10:65536
ubuntu:165536:65536
# There are no entries in /etc/sub{u,g}id for someone, but this
doesn't matter that much as subordinate IDs are not being requested.
someone@ubuntu-xenial:~$ newuidmap 1878 0 1001 1
someone@ubuntu-xenial:~$ newgidmap 1878 0 1001 1
Back to shell 1
nobody@ubuntu-xenial:~$ id
uid=0(root) gid=0(root) groups=0(root),65534(nogroup)
# The presence of the "nogroup" supplementary group indicates that
some unmapped GIDs are present as supplementary GIDs. The kernel knows
that this process still has "restricted" in its supplementary groups,
so it can't read the restricted file yet.
nobody@ubuntu-xenial:~$ cat /tmp/should_restrict
cat: /tmp/should_restrict: Permission denied
# The process has gained CAP_SETGID in its user namespace by becoming
UID 0. /proc/$pid/setgroups contains "allow", so it can call
setgroups(2). By su-ing to root (itself, in the user namespace), it
can drop the supplementary groups. It can't read /root/.bashrc as that
file is owned by UID 0 in the initial user namespace, which creates
some distracting error output but doesn't matter in this case.
nobody@ubuntu-xenial:~$ su root
su: Authentication failure
(Ignored)
bash: /root/.bashrc: Permission denied
# Supplementary groups have been dropped
root@ubuntu-xenial:~# id
uid=0(root) gid=0(root) groups=0(root)
# It can read the restricted file
root@ubuntu-xenial:~# cat /tmp/should_restrict
content
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1729357/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1656100] Re: Unable to remove signing keys using gnome-software-properties
I can confirm this. Also, specifying the -d flag upon executing this program through a terminal emulator returns no useful debug info to help us. -- 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/1656100 Title: Unable to remove signing keys using gnome-software-properties Status in Ubuntu GNOME: Invalid Status in software-properties package in Ubuntu: Confirmed Bug description: I have found that on Ubuntu GNOME 16.10 with GNOME 3.22 that I am unable to remove signing keys in the Authentication tab. If I select a key I wish to remove and click the Remove button, either nothing will happen, or it will ask me for authentication, upon giving it the correct password all that will happen is it will deselect the key I select, but at no point will it actually remove it, which is rather annoying. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: software-properties-gtk 0.96.24.7 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Jan 12 21:35:55 2017 InstallationDate: Installed on 2017-01-09 (3 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) 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-gnome/+bug/1656100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779240] [NEW] Unable to Remove Trusted Software Providers From Authentication Tab
Public bug reported: Affected Ubuntu Release: Ubuntu 18.04 LTS Installed Package Version: 0.96.24.32.3 Upon clicking on a trusted software provider in the Authentication tab, and then clicking "Remove" will prompt for a password and do absolutely nothing. I would expect this to remove a software provider from the trusted list. Specifying the -d or -m options for extra information when running the application from a terminal emulator returns no useful information. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-gtk 0.96.24.32.3 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu Jun 28 21:20:48 2018 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2018-06-19 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: N/A SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (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 software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1779240 Title: Unable to Remove Trusted Software Providers From Authentication Tab Status in software-properties package in Ubuntu: New Bug description: Affected Ubuntu Release: Ubuntu 18.04 LTS Installed Package Version: 0.96.24.32.3 Upon clicking on a trusted software provider in the Authentication tab, and then clicking "Remove" will prompt for a password and do absolutely nothing. I would expect this to remove a software provider from the trusted list. Specifying the -d or -m options for extra information when running the application from a terminal emulator returns no useful information. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-gtk 0.96.24.32.3 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu Jun 28 21:20:48 2018 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2018-06-19 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: N/A 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/1779240/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773476] Re: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.img-4.8.0 when no corresponding vmlinuz present
** Description changed: With LinUX Images/-Extras 4.15.0-22-generic, 4.13.0-43-generic, 4.8.0-58-generic, 4.8.0-56-generic, and 4.4.0-127-generic installed, sudo dpkg-reconfigure linux-firmware returns the following to Console: update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic update-initramfs: Generating /boot/initrd.img-4.13.0-43-generic update-initramfs: Generating /boot/initrd.img-4.8.0-58-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.4.0-127-generic Same configuration report for "Setting up linux-firmware..." with sudo apt(-get) install (--reinstall) linux-firmware and sudo apt-get upgrade linux-firmware. Therefore: Reproducible: Always Steps to reproduce: sudo apt install (--reinstall) linux-firmware or sudo dpkg-reconfigure linux-firmware. Actual results, excepting actually installed Kernel Image packages: update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory Expected results, excepting actually installed Kernel Image packages: No attempt to generate /boot/initrd.img for missing kernels, thus no warnings, errors or fatals. - UPDATE: Solved via sudo rm -rf /var/lib/initramfs-tools-4/8/0 && sudo + UPDATE: Solved via sudo rm -rf /var/lib/initramfs-tools-4.8.0 && sudo rm -rf /var/lib/initramfs-tools/4.8.0-56. Recommend check for bug(s) in apt and dpkg of which this Bug may be a depend, as automatic housecleaning failed me in this specific case. --- ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: Unity Dependencies: DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-05-17 (373 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: linux-firmware 1.157.19 [origin: unknown] PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-22.24~16.04.1-generic 4.15.17 Tags: xenial third-party-packages Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True ** Description changed: With LinUX Images/-Extras 4.15.0-22-generic, 4.13.0-43-generic, 4.8.0-58-generic, 4.8.0-56-generic, and 4.4.0-127-generic installed, sudo dpkg-reconfigure linux-firmware returns the following to Console: update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic update-initramfs: Generating /boot/initrd.img-4.13.0-43-generic update-initramfs: Generating /boot/initrd.img-4.8.0-58-generic update-initramfs: Generating /boot/initrd.img
[Touch-packages] [Bug 1773476] Re: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.img-4.8.0 when no corresponding vmlinuz present
SOLVED via sudo rm -rf /var/lib/initramfs-tools/4.8.0 && sudo rm -rf /var/lib/initramfs-tools/4.8.0-56! Recommend check for bug(s) in apt and dpkg, as automatic housecleaning faile me in this specific case. ** Description changed: With LinUX Images/-Extras 4.15.0-22-generic, 4.13.0-43-generic, 4.8.0-58-generic, 4.8.0-56-generic, and 4.4.0-127-generic installed, sudo dpkg-reconfigure linux-firmware returns the following to Console: update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic update-initramfs: Generating /boot/initrd.img-4.13.0-43-generic update-initramfs: Generating /boot/initrd.img-4.8.0-58-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.4.0-127-generic Same configuration report for "Setting up linux-firmware..." with sudo apt(-get) install (--reinstall) linux-firmware and sudo apt-get upgrade linux-firmware. Therefore: Reproducible: Always Steps to reproduce: sudo apt install (--reinstall) linux-firmware or sudo dpkg-reconfigure linux-firmware. Actual results, excepting actually installed Kernel Image packages: update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory Expected results, excepting actually installed Kernel Image packages: No attempt to generate /boot/initrd.img for missing kernels, thus no warnings, errors or fatals. + UPDATE: Solved via sudo rm -rf /var/lib/initramfs-tools-4/8/0 && sudo + rm -rf /var/lib/initramfs-tools/4.8.0-56. Recommend check for bug(s) in + apt and dpkg of which this Bug may be a depend, as automatic + housecleaning failed me in this specific case. + --- ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: Unity Dependencies: DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-05-17 (373 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: linux-firmware 1.157.19 [origin: unknown] PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-22.24~16.04.1-generic 4.15.17 Tags: xenial third-party-packages Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True -- 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/1773476 Title: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.img-4.8.0 when no corresponding vmlinuz present Status in i
[Touch-packages] [Bug 1773476] Re: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.img-4.8.0 when no corresponding vmlinuz present
VERIFIED. Found a /var/lib/initramfs-tools/4.8.0 and a /var/lib /initramfs-tools/4.8.0-56 that shoudn't be there. -- 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/1773476 Title: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.img-4.8.0 when no corresponding vmlinuz present Status in initramfs-tools package in Ubuntu: Confirmed Bug description: With LinUX Images/-Extras 4.15.0-22-generic, 4.13.0-43-generic, 4.8.0-58-generic, 4.8.0-56-generic, and 4.4.0-127-generic installed, sudo dpkg-reconfigure linux-firmware returns the following to Console: update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic update-initramfs: Generating /boot/initrd.img-4.13.0-43-generic update-initramfs: Generating /boot/initrd.img-4.8.0-58-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.4.0-127-generic Same configuration report for "Setting up linux-firmware..." with sudo apt(-get) install (--reinstall) linux-firmware and sudo apt-get upgrade linux-firmware. Therefore: Reproducible: Always Steps to reproduce: sudo apt install (--reinstall) linux-firmware or sudo dpkg-reconfigure linux-firmware. Actual results, excepting actually installed Kernel Image packages: update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory Expected results, excepting actually installed Kernel Image packages: No attempt to generate /boot/initrd.img for missing kernels, thus no warnings, errors or fatals. --- ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: Unity Dependencies: DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-05-17 (373 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: linux-firmware 1.157.19 [origin: unknown] PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-22.24~16.04.1-generic 4.15.17 Tags: xenial third-party-packages Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1773476/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/Li
[Touch-packages] [Bug 1638345] Re: avahi-daemon crashes multiple times an hour
Hi @lathiat, just want to confirm that for me the issue was solved by commenting out rlimit-data and rlimit-stack. I had solved it ages ago using this thread above, and had completely forgotten about it. I was reminded of the issue as my computer was updating (and asking about this conf file), so just wanted to report now. Thanks a lot - the issue had been causing me headaches for ages. As to the avahi-browse: I get 0 lines. -- 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/1638345 Title: avahi-daemon crashes multiple times an hour Status in avahi package in Ubuntu: Fix Released Bug description: Ever since upgrading to 16.10, avahi-daemon crashes multiple times an hour, leading to the prompt to report the issue to Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: avahi-daemon 0.6.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 1 10:48:35 2016 InstallationDate: Installed on 2016-07-08 (115 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: avahi UpgradeStatus: Upgraded to yakkety on 2016-10-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1638345/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1764614] Re: package libperl5.26 5.26.0-8ubuntu1 [modified: usr/share/doc/libperl5.26/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/l
Found a FIX! Just need to move/backup the shared doc file that was causing the problem and all is right again. ~| sudo mv /usr/share/doc/libperl5.26 /usr/share/doc/libperl5.26.barron ~| sudo apt --fix-broken install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: libperl5.26:i386 The following NEW packages will be installed: libperl5.26:i386 0 upgraded, 1 newly installed, 0 to remove and 20 not upgraded. 3 not fully installed or removed. Need to get 0 B/3,169 kB of archives. After this operation, 16.3 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 647255 files and directories currently installed.) Preparing to unpack .../libperl5.26_5.26.0-8ubuntu1.1_i386.deb ... Unpacking libperl5.26:i386 (5.26.0-8ubuntu1.1) ... Setting up perl-modules-5.26 (5.26.0-8ubuntu1.1) ... Processing triggers for libc-bin (2.26-0ubuntu2.1) ... Setting up libperl5.26:amd64 (5.26.0-8ubuntu1.1) ... Setting up libperl5.26:i386 (5.26.0-8ubuntu1.1) ... Processing triggers for man-db (2.7.6.1-2) ... Setting up perl (5.26.0-8ubuntu1.1) ... Processing triggers for libc-bin (2.26-0ubuntu2.1) ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1764614 Title: package libperl5.26 5.26.0-8ubuntu1 [modified: usr/share/doc/libperl5.26/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:amd64 Status in perl package in Ubuntu: Confirmed Bug description: Gestionnaire de mise à jour Echec de traitement du paquet l'installation ou la desinstallation du paquet a échoué ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libperl5.26 5.26.0-8ubuntu1 [modified: usr/share/doc/libperl5.26/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 Date: Tue Apr 17 04:25:22 2018 DuplicateSignature: package:libperl5.26:5.26.0-8ubuntu1 [modified: usr/share/doc/libperl5.26/changelog.Debian.gz] Unpacking libperl5.26:amd64 (5.26.0-8ubuntu1.1) over (5.26.0-8ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libperl5.26_5.26.0-8ubuntu1.1_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:amd64 ErrorMessage: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:amd64 InstallationDate: Installed on 2017-11-15 (152 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: perl Title: package libperl5.26 5.26.0-8ubuntu1 [modified: usr/share/doc/libperl5.26/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1764614/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1764614] Re: package libperl5.26 5.26.0-8ubuntu1 [modified: usr/share/doc/libperl5.26/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/l
Some additional attempts to fix failed for me - I'm stuck and cannot update or remove anything. ~| sudo apt install perl Reading package lists... Done Building dependency tree Reading state information... Done perl is already the newest version (5.26.0-8ubuntu1.1). You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libperl5.26 : Breaks: libperl5.26:i386 (!= 5.26.0-8ubuntu1) but 5.26.0-8ubuntu1.1 is to be installed libperl5.26:i386 : Breaks: libperl5.26 (!= 5.26.0-8ubuntu1.1) but 5.26.0-8ubuntu1 is to be installed perl : Depends: libperl5.26 (= 5.26.0-8ubuntu1.1) but 5.26.0-8ubuntu1 is to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ~| sudo apt --fix-broken install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: libperl5.26 The following packages will be upgraded: libperl5.26 1 upgraded, 0 newly installed, 0 to remove and 20 not upgraded. 3 not fully installed or removed. Need to get 0 B/3,544 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 647747 files and directories currently installed.) Preparing to unpack .../libperl5.26_5.26.0-8ubuntu1.1_amd64.deb ... Unpacking libperl5.26:amd64 (5.26.0-8ubuntu1.1) over (5.26.0-8ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libperl5.26_5.26.0-8ubuntu1.1_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:amd64 Errors were encountered while processing: /var/cache/apt/archives/libperl5.26_5.26.0-8ubuntu1.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1764614 Title: package libperl5.26 5.26.0-8ubuntu1 [modified: usr/share/doc/libperl5.26/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:amd64 Status in perl package in Ubuntu: Confirmed Bug description: Gestionnaire de mise à jour Echec de traitement du paquet l'installation ou la desinstallation du paquet a échoué ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libperl5.26 5.26.0-8ubuntu1 [modified: usr/share/doc/libperl5.26/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 Date: Tue Apr 17 04:25:22 2018 DuplicateSignature: package:libperl5.26:5.26.0-8ubuntu1 [modified: usr/share/doc/libperl5.26/changelog.Debian.gz] Unpacking libperl5.26:amd64 (5.26.0-8ubuntu1.1) over (5.26.0-8ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libperl5.26_5.26.0-8ubuntu1.1_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:amd64 ErrorMessage: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:amd64 InstallationDate: Installed on 2017-11-15 (152 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: perl Title: package libperl5.26 5.26.0-8ubuntu1 [modified: usr/share/doc/libperl5.26/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1764614/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1764896] [NEW] System will not display using displayport from AMD GPU
Public bug reported: There are 2 monitors connected to 1 GPU. The monitor connected via a digital connection always comes up correctly. The monitor connected via DISPLAYPORT does not come up, even though the machine is booting correctly. It's almost like the DP path isn't recognized by xorg. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Apr 17 18:02:09 2018 DistUpgraded: 2018-03-30 21:12:37,078 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-13-generic, x86_64: installed nvidia, 390.48, 4.15.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/580] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Ellesmere [Radeon RX 470/480/570/580] [1462:3417] InstallationDate: Installed on 2017-03-11 (402 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170222) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic root=UUID=68755ecb-0ee0-46a1-8a3e-c027d0cbac65 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-03-31 (17 days ago) dmi.bios.date: 12/13/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P7.20 dmi.board.name: Z170M Pro4S dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP7.20:bd12/13/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170MPro4S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1764896 Title: System will not display using displayport from AMD GPU Status in xorg package in Ubuntu: New Bug description: There are 2 monitors connected to 1 GPU. The monitor connected via a digital connection always comes up correctly. The monitor connected via DISPLAYPORT does not come up, even though the machine is booting correctly. It's almost like the DP path isn't recognized by xorg. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Apr 17 18:02:09 2018 DistUpgraded: 2018-03-30 21:12:37,078 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-13-generic, x86_64: installed nvidia, 390.48, 4.15.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/580] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Ellesmere [Radeon RX 470/480/570/580] [1462:3417] InstallationDate: Installed on 2017-03-11 (402 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170222) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic root=UUID=68755ecb-0ee0-46a1-8a3e-c027d0cbac65 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display
[Touch-packages] [Bug 1761861] [NEW] dh-python dependency removal changing behaviour of installing virtualenv
Public bug reported: root@6de0badbae8b:/# apt-get install --no-install-recommends virtualenv Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: ca-certificates libexpat1 libmpdec2 libpython3-stdlib libpython3.6-minimal libpython3.6-stdlib libssl1.1 mime-support openssl python-pip-whl python3 python3-minimal python3-pkg-resources python3-virtualenv python3.6 python3.6-minimal Suggested packages: python3-doc python3-tk python3-venv python3-setuptools python3.6-venv python3.6-doc binutils binfmt-support Recommended packages: bzip2 file xz-utils The following NEW packages will be installed: ca-certificates libexpat1 libmpdec2 libpython3-stdlib libpython3.6-minimal libpython3.6-stdlib libssl1.1 mime-support openssl python-pip-whl python3 python3-minimal python3-pkg-resources python3-virtualenv python3.6 python3.6-minimal virtualenv 0 upgraded, 17 newly installed, 0 to remove and 43 not upgraded. Need to get 7375 kB of archives. After this operation, 29.9 MB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://archive.ubuntu.com/ubuntu bionic/main amd64 libssl1.1 amd64 1.1.0g-2ubuntu3 [1128 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic/main amd64 libpython3.6-minimal amd64 3.6.5-3 [529 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic/main amd64 libexpat1 amd64 2.2.5-3 [80.2 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic/main amd64 python3.6-minimal amd64 3.6.5-3 [1425 kB] Get:5 http://archive.ubuntu.com/ubuntu bionic/main amd64 python3-minimal amd64 3.6.5-2 [23.9 kB] Get:6 http://archive.ubuntu.com/ubuntu bionic/main amd64 mime-support all 3.60ubuntu1 [30.1 kB] Get:7 http://archive.ubuntu.com/ubuntu bionic/main amd64 libmpdec2 amd64 2.4.2-1 [82.6 kB] Get:8 http://archive.ubuntu.com/ubuntu bionic/main amd64 libpython3.6-stdlib amd64 3.6.5-3 [1648 kB] Get:9 http://archive.ubuntu.com/ubuntu bionic/main amd64 python3.6 amd64 3.6.5-3 [186 kB] Get:10 http://archive.ubuntu.com/ubuntu bionic/main amd64 libpython3-stdlib amd64 3.6.5-2 [7372 B] Get:11 http://archive.ubuntu.com/ubuntu bionic/main amd64 python3 amd64 3.6.5-2 [8780 B] Get:12 http://archive.ubuntu.com/ubuntu bionic/main amd64 openssl amd64 1.1.0g-2ubuntu3 [532 kB] Get:13 http://archive.ubuntu.com/ubuntu bionic/main amd64 ca-certificates all 20170717 [167 kB] Get:14 http://archive.ubuntu.com/ubuntu bionic/universe amd64 python-pip-whl all 9.0.1-2 [1379 kB] Get:15 http://archive.ubuntu.com/ubuntu bionic/main amd64 python3-pkg-resources all 39.0.1-2 [98.8 kB] Get:16 http://archive.ubuntu.com/ubuntu bionic/universe amd64 python3-virtualenv all 15.1.0+ds-1 [43.2 kB] Get:17 http://archive.ubuntu.com/ubuntu bionic/universe amd64 virtualenv all 15.1.0+ds-1 [4376 B] Fetched 7375 kB in 14s (515 kB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package libssl1.1:amd64. (Reading database ... 4416 files and directories currently installed.) Preparing to unpack .../0-libssl1.1_1.1.0g-2ubuntu3_amd64.deb ... Unpacking libssl1.1:amd64 (1.1.0g-2ubuntu3) ... Selecting previously unselected package libpython3.6-minimal:amd64. Preparing to unpack .../1-libpython3.6-minimal_3.6.5-3_amd64.deb ... Unpacking libpython3.6-minimal:amd64 (3.6.5-3) ... Selecting previously unselected package libexpat1:amd64. Preparing to unpack .../2-libexpat1_2.2.5-3_amd64.deb ... Unpacking libexpat1:amd64 (2.2.5-3) ... Selecting previously unselected package python3.6-minimal. Preparing to unpack .../3-python3.6-minimal_3.6.5-3_amd64.deb ... Unpacking python3.6-minimal (3.6.5-3) ... Selecting previously unselected package python3-minimal. Preparing to unpack .../4-python3-minimal_3.6.5-2_amd64.deb ... Unpacking python3-minimal (3.6.5-2) ... Selecting previously unselected package mime-support. Preparing to unpack .../5-mime-support_3.60ubuntu1_all.deb ... Unpacking mime-support (3.60ubuntu1) ... Selecting previously unselected package libmpdec2:amd64. Preparing to unpack .../6-libmpdec2_2.4.2-1_amd64.deb ... Unpacking libmpdec2:amd64 (2.4.2-1) ... Selecting previously unselected package libpython3.6-stdlib:amd64. Preparing to unpack .../7-libpython3.6-stdlib_3.6.5-3_amd64.deb ... Unpacking libpython3.6-stdlib:amd64 (3.6.5-3) ... Selecting previously unselected package python3.6. Preparing to unpack .../8-python3.6_3.6.5-3_amd64.deb ... Unpacking python3.6 (3.6.5-3) ... Selecting previously unselected package libpython3-stdlib:amd64. Preparing to unpack .../9-libpython3-stdlib_3.6.5-2_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.6.5-2) ... Setting up libssl1.1:amd64 (1.1.0g-2ubuntu3) ... debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.) debconf: falling back to frontend: Readline debconf: unable to initialize frontend
[Touch-packages] [Bug 1761275] [NEW] Typo when running command for uninstalled applications
Public bug reported: I tried running nodejs on Ubuntu Mate 18.04. When I ran it, it asked me to install it, I didn't know where to report this or where it was referring so I guessed it was apt. The command 'nodejs' can be ""intsalled"" by typing: sudo apt install nodejs The typo is in double quotation marks. It says intsalled instead of installed. It should be corrected. Thanks! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6~beta1 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: MATE Date: Wed Apr 4 14:50:48 2018 InstallationDate: Installed on 2018-04-03 (1 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307.1) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- 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/1761275 Title: Typo when running command for uninstalled applications Status in apt package in Ubuntu: New Bug description: I tried running nodejs on Ubuntu Mate 18.04. When I ran it, it asked me to install it, I didn't know where to report this or where it was referring so I guessed it was apt. The command 'nodejs' can be ""intsalled"" by typing: sudo apt install nodejs The typo is in double quotation marks. It says intsalled instead of installed. It should be corrected. Thanks! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6~beta1 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: MATE Date: Wed Apr 4 14:50:48 2018 InstallationDate: Installed on 2018-04-03 (1 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307.1) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1761275/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1666432] Re: Internet drops every few minutes on wired and wireless connection
I am also having the same issue on my Thinkpad E460 under Ubuntu 17.10. It started a couple of week ago and got really annoying. Sometimes the connection is just gone for a few seconds up to 2 or 3 minutes and sometimes it seems turning the WiFi module off and on again helps. The same problem occurs via Ethernet too, but less frequently. sudo lshw -class network *-network description: Wireless interface product: Dual Band Wireless-AC 3165 Plus Bluetooth vendor: Intel Corporation physical id: 0 bus info: pci@:01:00.0 logical name: wlp1s0 version: 79 serial: e0:94:67:45:be:3d width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.13.0-37-generic firmware=29.610311.0 ip=192.168.0.25 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:130 memory:f120-f1201fff *-network description: Ethernet interface product: Ethernet Connection I219-V vendor: Intel Corporation physical id: 1f.6 bus info: pci@:00:1f.6 logical name: enp0s31f6 version: 21 serial: 50:7b:9d:78:29:4b capacity: 1Gbit/s width: 32 bits clock: 33MHz capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k firmware=0.13-4 latency=0 link=no multicast=yes port=twisted pair resources: irq:129 memory:f130-f131 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1666432 Title: Internet drops every few minutes on wired and wireless connection Status in network-manager package in Ubuntu: Confirmed Bug description: Internet drops every 1-30 minutes when connected via wired or wireless (i.e., this is a problem on both wired and wireless) even though connection icon indicates the computer is still connected. Disconnecting and reconnecting via the connection icon resets internet temporarily until the next time. Dropped internet is discovered with "The site can't be reached" screens in Chromium, or error messages when downloading/updating in Terminal, or missing connection in Ubuntu Software app, or stalled syncing in Insync application (occurred even without Insync). Internet drops more frequently on wireless than on wired. It seems to disconnect more frequently with heavier internet use (e.g., downloading multiple files, opening several webpages in quick succession). This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron 15 5567 (dual boot). It occurs when running Live CD as well though. Ethernet and wifi both work without randomly disconnecting in Windows 10 on the same machine, and ethernet and wifi work on other machines running Ubuntu and Windows with the same router, so it is not a hardware or router issue. Output from sudo lshw -class network *-network description: Wireless interface product: Wireless 3165 vendor: Intel Corporation physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 79 serial: 58:fb:84:55:21:52 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn resources: irq:283 memory:df10-df101fff *-network description: Ethernet interface product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 07 serial: 18:db:f2:3c:d5:37 size: 10Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 latency=0 link=no multicast=yes port=MII speed=10Mbit/s resources: irq:279 ioport:d000(size=256) memory:df00-df000fff memory:d030-d0303fff ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64
[Touch-packages] [Bug 8949] Re: Opening a deleted 'recent document' results in a new file.
I can confirm this issue no longer affects Ubuntu 18.04, as recently viewed items are removed upon deletion. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/8949 Title: Opening a deleted 'recent document' results in a new file. Status in GNOME Panel: Invalid Status in GTK+: Won't Fix Status in One Hundred Papercuts: Confirmed Status in gtk+2.0 package in Ubuntu: Confirmed Bug description: http://bugzilla.gnome.org/show_bug.cgi?id=143385 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-panel/+bug/8949/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1743114] [NEW] package systemd 235-3ubuntu3 failed to install/upgrade: Trigger bilden eine Schleife, aufgegeben
Public bug reported: Upgrade from 17.10 to 18.04. Bug shows up after first startup ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Sat Jan 13 14:31:57 2018 ErrorMessage: Trigger bilden eine Schleife, aufgegeben InstallationDate: Installed on 2016-08-24 (506 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Sony Corporation VGN-AW21S_B ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic root=UUID=eb84ecb3-94ad-4359-ae7a-1d094a3a7042 ro Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.4ubuntu1 apt 1.6~alpha5 SourcePackage: systemd Title: package systemd 235-3ubuntu3 failed to install/upgrade: Trigger bilden eine Schleife, aufgegeben UpgradeStatus: Upgraded to bionic on 2018-01-13 (0 days ago) dmi.bios.date: 09/23/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1054Y2 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1054Y2:bd09/23/2009:svnSonyCorporation:pnVGN-AW21S_B:pvrC6015CED:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: N/A dmi.product.name: VGN-AW21S_B dmi.product.version: C6015CED dmi.sys.vendor: Sony Corporation ** Affects: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1743114 Title: package systemd 235-3ubuntu3 failed to install/upgrade: Trigger bilden eine Schleife, aufgegeben Status in systemd package in Ubuntu: New Bug description: Upgrade from 17.10 to 18.04. Bug shows up after first startup ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Sat Jan 13 14:31:57 2018 ErrorMessage: Trigger bilden eine Schleife, aufgegeben InstallationDate: Installed on 2016-08-24 (506 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Sony Corporation VGN-AW21S_B ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic root=UUID=eb84ecb3-94ad-4359-ae7a-1d094a3a7042 ro Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.4ubuntu1 apt 1.6~alpha5 SourcePackage: systemd Title: package systemd 235-3ubuntu3 failed to install/upgrade: Trigger bilden eine Schleife, aufgegeben UpgradeStatus: Upgraded to bionic on 2018-01-13 (0 days ago) dmi.bios.date: 09/23/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1054Y2 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1054Y2:bd09/23/2009:svnSonyCorporation:pnVGN-AW21S_B:pvrC6015CED:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: N/A dmi.product.name: VGN-AW21S_B dmi.product.version: C6015CED dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1743114/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738925] Re: PCI/internal sound card not detected
Similar issue with kernel 4.13.0-19.22-generic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1738925 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Audio issue precipitated when linux kernel was updated to 4.13.0-19 from 4.13.0-17 in Ubuntu 17.10. Loading kernel 4.13.0-17 fixes the issue. Currently using alsa-base 1.0.25. I expected to have sound options for onboard audio, hdmi video card audio, and headphones, but a dummy output was listed instead. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon Dec 18 22:03:24 2017 InstallationDate: Installed on 2010-11-27 (2578 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to artful on 2017-10-22 (57 days ago) dmi.bios.date: 08/25/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A78 PLUS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd08/25/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-10-26T22:10:32.289419 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1738925/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667512] Re: update-initramfs hangs on upgrade, dpkg unusable, unbootable system
ms, virtualbox-guest-modules, zfs-dkms Depends: initramfs-tools | linux-initramfs-tool, kmod Recommends: grub-pc | grub-efi-amd64 | grub-efi-ia32 | grub | lilo Suggests: fdutils, linux-doc-4.4.0 | linux-source-4.4.0, linux-tools, linux-headers-4.4.0-63-generic There does seem to be a problem with linux-image- extra-4.4.0-63-generic. Trying to uninstall this triggers update- initramfs. $ sudo dpkg --status linux-image-extra-4.4.0-63-generic Package: linux-image-extra-4.4.0-63-generic Status: purge ok half-installed Priority: optional Section: kernel Installed-Size: 148939 Maintainer: Ubuntu Kernel Team Architecture: amd64 Source: linux Version: 4.4.0-63.84 Depends: linux-image-4.4.0-63-generic, crda | wireless-crda I've tried http://askubuntu.com/questions/650732/apt-fails-to-remove- partially-installed-kernel-and-cant-install-any-other-packa/651596 with no luck. At this point I'm not sure if a partially installed kernel is the problem, and I've run out of troubleshooting insight. User #2: https://ubuntuforums.org/showthread.php?t=2351895 User #3: https://ubuntuforums.org/showthread.php?t=2353606 User #4 (original question): When upgrading (apt-get upgrade) on 16.04 (ubuntu-mate) I get a hang (left from 9:50am til 16:00 or thereabouts) I tracked down as far as the call to /etc/kernel/postinst.d/initramfs- tools and added a -v option, the last relevant lines on the terminal when re-running `apt-get upgrade` are as follows: ... Adding binary /bin/date Adding binary /sbin/hwclock Adding binary /sbin/dumpe2fs Calling hook dmsetup Calling hook reiserfsprogs Building cpio /boot/initrd.img-4.4.0-24-generic.new initramfs ^CFailed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-4.4.0-24-generic.postinst line 1052. dpkg: error processing package linux-image-4.4.0-24-generic (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of linux-image-extra-4.4.0-24-generic: linux-image-extra-4.4.0-24-generic depends on linux-image-4.4.0-24-generic; however: Package linux-image-4.4.0-24-generic is not configured yet. Checking with `ps fax` before the interrupt, I get this tree - indicating a hang on `sync` task sudo dpkg --configure -a \_ dpkg --configure -a \_ /usr/bin/perl /var/lib/dpkg/info/linux-image-4.4.0-24-generic.postinst configure \_ run-parts --verbose --exit-on-error --arg=4.4.0-24-generic --arg=/boot/vmlinuz-4.4.0-24-generic /etc/kernel/postinst.d \_ /bin/sh -e /etc/kernel/postinst.d/initramfs-tools 4.4.0-24-generic /boot/vmlinuz-4.4.0-24-generic \_ /bin/sh /usr/sbin/update-initramfs -v -c -t -k 4.4.0-24-generic -b /boot \_ sync I tried moving the resulting initramfs img file in /boot so a new one would be created - a new one is indeed created, hang still occurs on `sync` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1667512/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738925] [NEW] PCI/internal sound card not detected
Public bug reported: Audio issue precipitated when linux kernel was updated to 4.13.0-19 from 4.13.0-17 in Ubuntu 17.10. Loading kernel 4.13.0-17 fixes the issue. Currently using alsa-base 1.0.25. I expected to have sound options for onboard audio, hdmi video card audio, and headphones, but a dummy output was listed instead. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon Dec 18 22:03:24 2017 InstallationDate: Installed on 2010-11-27 (2578 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to artful on 2017-10-22 (57 days ago) dmi.bios.date: 08/25/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A78 PLUS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd08/25/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-10-26T22:10:32.289419 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1738925 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Audio issue precipitated when linux kernel was updated to 4.13.0-19 from 4.13.0-17 in Ubuntu 17.10. Loading kernel 4.13.0-17 fixes the issue. Currently using alsa-base 1.0.25. I expected to have sound options for onboard audio, hdmi video card audio, and headphones, but a dummy output was listed instead. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon Dec 18 22:03:24 2017 InstallationDate: Installed on 2010-11-27 (2578 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to artful on 2017-10-22 (57 days ago) dmi.bios.date: 08/25/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A78 PLUS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd08/25/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-10-26T22:10:32.289419 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1738925/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1729900] [NEW] I used the tool
Public bug reported: I am using Ubuntu 16.04- 64 bits ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Nov 3 14:29:05 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Skylake Integrated Graphics [1462:7a15] InstallationDate: Installed on 2017-06-24 (131 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1a2c:0c23 China Resource Semico Co., Ltd Bus 001 Device 002: ID 0458:003a KYE Systems Corp. (Mouse Systems) NetScroll+ Mini Traveler / Genius NetScroll 120 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7A15 ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, no user) LANG=es_AR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic root=UUID=5361567f-1ada-452b-b7b9-c77c77242c7f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.50 dmi.board.asset.tag: Default string dmi.board.name: H110M PRO-VH PLUS (MS-7A15) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.50:bd12/16/2016:svnMSI:pnMS-7A15:pvr1.0:rvnMSI:rnH110MPRO-VHPLUS(MS-7A15):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7A15 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Nov 3 08:57:00 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.4 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1729900 Title: I used the tool Status in xorg package in Ubuntu: New Bug description: I am using Ubuntu 16.04- 64 bits ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Nov 3 14:29:05 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Skylake Integrated Graphics [1462:7a15] InstallationDate: Installed on 2017-06-24 (131 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1a2c:0c23 China Resource Semico Co., Ltd Bus 001 Device 002: ID 0458:003a KYE Systems Corp. (Mouse Systems) NetScroll+ Mini Traveler / Genius NetScroll 120 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7A15 ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, no user) LANG=es_AR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic root=UUID=5361567f-1ada-452b-b7b9-c77c77242c7f ro quiet spla
[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
Just downgrade network-manager to 1.2.2-0ubuntu0.16.04.4 until the issue is resolved. Pretty simple. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Triaged Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1713595] [NEW] gdebi-kde crash on app startup
Public bug reported:
Here is the back trace information:
Application: GDebi (gdebi-kde), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6 0x in ()
#7 0x7f018591ea3a in sip_api_get_cpp_ptr () at
/usr/lib/python3/dist-packages/sip.cpython-35m-x86_64-linux-gnu.so
#8 0x7f0185924b20 in () at
/usr/lib/python3/dist-packages/sip.cpython-35m-x86_64-linux-gnu.so
#9 0x7f0185926a70 in () at
/usr/lib/python3/dist-packages/sip.cpython-35m-x86_64-linux-gnu.so
#10 0x7f0185927293 in () at
/usr/lib/python3/dist-packages/sip.cpython-35m-x86_64-linux-gnu.so
#11 0x7f0185927500 in () at
/usr/lib/python3/dist-packages/sip.cpython-35m-x86_64-linux-gnu.so
#12 0x7f0184ceb7fa in () at
/usr/lib/python3/dist-packages/PyQt4/QtGui.cpython-35m-x86_64-linux-gnu.so
#13 0x5567a18d828f in PyCFunction_Call (func=, args=,
kwds=) at ../Objects/methodobject.c:109
#14 0x5567a188f1e9 in call_function (oparg=,
pp_stack=0x7fffe5613070) at ../Python/ceval.c:4720
#15 0x5567a188f1e9 in PyEval_EvalFrameEx (f=Frame 0x5567a3f15e48, for file
/usr/share/gdebi/GDebi/GDebiKDE.py, line 149, in __init__
(self=,
version_info_msg='', hboxlayout5=,
infoIcon=, det=, DetailsSize=,
DetailsVersion=, hboxlayout1=, tabWidget2=,
DetailsSectionLabel=, unauthenticated=0,
hboxlayout=, DecriptionEdit=, hboxlayout3=,
detailsButton=,
downloadButton=, hboxlayout2=, IncFilesEdit=, install=[], DetailsPriority=, argcount=, args=,
locals=, globals=, _co=) at
../Python/ceval.c:4033
#17 0x5567a1894b5f in PyEval_EvalCodeEx () at ../Python/ceval.c:4054
#18 0x5567a18da2cf in function_call.lto_priv (func=, arg=(, version_info_msg='', hboxlayout5=, infoIcon=, det=, DetailsSize=,
DetailsVersion=, hboxlayout1=, tabWidget2=,
DetailsSectionLabel=, unauthenticated=0,
hboxlayout=, DecriptionEdit=, hboxlayout3=,
detailsButton=,
downloadButton=, hboxlayout2=, IncFilesEdit=,
install=[], DetailsPriority=, PackageProgressBar=, textLabel1_3=, 'file': '',
'datadir': '/usr/share/gdebi'}) at ../Objects/funcobject.c:627
#19 0x5567a1916887 in PyObject_Call (func=, arg=, kw=) at
../Objects/abstract.c:2166
#20 0x5567a1838f3e in method_call.lto_priv (func=, arg=(, version_info_msg='', hboxlayout5=, infoIcon=, det=, DetailsSize=,
DetailsVersion=, hboxlayout1=, tabWidget2=,
DetailsSectionLabel=, unauthenticated=0,
hboxlayout=, DecriptionEdit=, hboxlayout3=,
detailsButton=,
downloadButton=, hboxlayout2=, IncFilesEdit=,
install=[], DetailsPriority=, PackageProgressBar=, textLabel1_3=, 'file': '',
'datadir': '/usr/share/gdebi'}) at ../Objects/classobject.c:330
#21 0x5567a1916887 in PyObject_Call (func=, arg=, kw=) at
../Objects/abstract.c:2166
#22 0x5567a18d10e9 in slot_tp_init (self=, version_info_msg='',
hboxlayout5=, infoIcon=, det=, DetailsSize=, DetailsVersion=,
hboxlayout1=, tabWidget2=, DetailsSectionLabel=,
unauthenticated=0, hboxlayout=,
DecriptionEdit=, hboxlayout3=, detailsButton=, downloadButton=,
hboxlayout2=, IncFilesEdit=, install=[], DetailsPriority=, PackageProgressBar=
, textLabel1_3=, 'file': '', 'datadir': '/usr/share/gdebi'}) at
../Objects/typeobject.c:6287
#23 0x5567a18df7d4 in type_call.lto_priv (type=, args=(),
kwds={'options': ,
'file': '', 'datadir': '/usr/share/gdebi'}) at ../Objects/typeobject.c:905
#24 0x5567a1916887 in PyObject_Call (func=, arg=, kw=) at
../Objects/abstract.c:2166
#25 0x5567a188f961 in do_call (nk=, na=0,
pp_stack=0x7fffe5613440, func=) at ../Python/ceval.c:4951
#26 0x5567a188f961 in call_function (oparg=,
pp_stack=0x7fffe5613440) at ../Python/ceval.c:4747
#27 0x5567a188f961 in PyEval_EvalFrameEx (f=Frame 0x5567a37765c8, for file
/usr/bin/gdebi-kde, line 87, in (), throwflag=0) at
../Python/ceval.c:3251
#28 0x5567a1893d16 in _PyEval_EvalCodeWithName (_co=, globals=, locals=,
args=, argcount=, kws=0x0, kwcount=0, defs=0x0,
defcount=0, kwdefs=0x0, closure=0x0, name=0x0, qualname=0x0) at
../Python/ceval.c:4033
#29 0x5567a1894a1f in PyEval_EvalCodeEx () at ../Python/ceval.c:4054
#30 0x5567a1894a1f in PyEval_EvalCode (co=,
globals=, locals=) at ../Python/ceval.c:777
#31 0x5567a1961b02 in run_mod (mod=, filename=, globals={'KCmdLineArgs': , 'description': ,
'OptionParsed': , '__name__': '__main__',
'options': , 'sys':
, 'KAboutData': , '__cached__': None, '__loader__':
, 'ki18n': , 'afile': '', 'KMessageBox': , 'parser': , dest='non_interactive', help=
'Run non-interactive (dangerous!)', action='store_true', type=None,
callback=None, choices=None, callback_args=None,...(truncated),
locals={'KCmdLineArgs': , 'description': ,
'OptionParsed': , '__name__': '__main__',
'options': , 'sys':
, 'KAboutData': , '__cached__': None, '__loader__':
, 'ki18n': , 'afile': '', 'KMessageBox': , 'parser': , dest='non_interactive', help='Run non-interactive
(dangerous!)', action='store_true', type=None, callback=None, choices=None,
[Touch-packages] [Bug 1708317] [NEW] package libxcb-dri3-0:i386 1.11.1-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi
Public bug reported: please give me solution as fast as posible ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libxcb-dri3-0:i386 1.11.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Aug 3 06:05:15 2017 DistUpgraded: 2017-08-03 06:16:08,813 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: zesty DistroVariant: ubuntu DuplicateSignature: package:libxcb-dri3-0:i386:1.11.1-1ubuntu1 Setting up dpkg-dev (1.18.10ubuntu2) ... dpkg: error processing package libxcb-dri3-0:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0662] Subsystem: Dell GeForce 820M [1028:0662] InstallationDate: Installed on 2017-06-12 (51 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Dell Inc. Vostro 3546 PackageArchitecture: i386 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic root=UUID=6540422f-1c28-43bf-9b86-c1a3c6dc7d55 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: libxcb Title: package libxcb-dri3-0:i386 1.11.1-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to zesty on 2017-08-03 (0 days ago) dmi.bios.date: 05/27/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 036DYM dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA03:bd05/27/2014:svnDellInc.:pnVostro3546:pvrNotSpecified:rvnDellInc.:rn036DYM:rvrA03:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3546 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: libxcb (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 ubuntu zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1708317 Title: package libxcb-dri3-0:i386 1.11.1-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libxcb package in Ubuntu: New Bug description: please give me solution as fast as posible ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libxcb-dri3-0:i386 1.11.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Aug 3 06:05:15 2017 DistUpgraded: 2017-08-03 06:16:08,813 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: zesty DistroVariant: ubuntu DuplicateSignature: package:libxcb-dri3-0:i386:1.11.1-1ubuntu1 Setting up dpkg-dev (1.18.10ubuntu2) ... dpkg: error processing package libxcb-dri3-0:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0662] Subsystem: Dell GeForce 820
[Touch-packages] [Bug 1568787] Re: resolvconf does not reliable receive nameserver information from NetworkManager
I first experience this issue with nm version 1.8.2-1ubuntu1 in an - as of writing fully updated - 17.04. Syslog will be attached, from that you can see that dnsmask gets the nameserver, networkmanager gets it too, but it doesn't make to resolv.conf, that will only have the stub resolver. /etc/resolv.conf is a link ending in /run/resolvconf/resolv.conf. Workaround is to manually add the nameserver to resolv conf and comment out "dns=dnsmasq" in /etc/NetworkManager/NetworkManager.conf which is really annoying on a laptop which you move around a lot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1568787 Title: resolvconf does not reliable receive nameserver information from NetworkManager Status in dbus package in Ubuntu: Confirmed Status in dnsmasq package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: resolvconf does not reliable receive nameserver information from NetworkManager. In the journal I see things like: Apr 11 11:13:52 ottawa dnsmasq[3122]: setting upstream servers from DBus Apr 11 11:13:52 ottawa dnsmasq[3122]: using nameserver fe80::1#53 Apr 11 11:13:52 ottawa dnsmasq[3122]: using nameserver 192.168.1.254#53 Apr 11 11:13:52 ottawa dbus[978]: [system] Rejected send message, 13 matched rules; type="method_return", sender=":1.99" (uid=0 pid=3122 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.8" (uid=0 pid=1017 comm="/usr/sbin/NetworkManager --no-daemon ") Apr 11 11:04:21 ottawa NetworkManager[1017]: DNS: starting dnsmasq... Apr 11 11:04:21 ottawa NetworkManager[1017]: dnsmasq not available on the bus, can't update servers. Apr 11 11:04:21 ottawa NetworkManager[1017]: [1460369061.825658] [dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name Doing this via dbus seems really odd, but I suspect messages between NetworkManager and the dnsmasq it spawns should not be rejected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dnsmasq-base 2.75-1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 11 11:17:34 2016 InstallationDate: Installed on 2016-01-26 (76 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160125) SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1568787/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700089] Re: package python3-click-package 0.4.46+16.10.20170607.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
holding the following packages at their respective versions resolves the error, for now. (apt-get install these packages with "apt-get install =" and then use "apt-mark hold =") ((posted for the new guys like me, who were slightly terrified when this error popped up)) python3-click-package=0.4.45.1+16.10.20160916-0ubuntu1 gir1.2-click-0.4=0.4.45.1+16.10.20160916-0ubuntu1 libclick-0.4-0=0.4.45.1+16.10.20160916-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1700089 Title: package python3-click-package 0.4.46+16.10.20170607.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in click package in Ubuntu: Confirmed Bug description: Not sure what happened, just had this pop up. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: python3-click-package 0.4.46+16.10.20170607.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-56.61-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.3 AptOrdering: click:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Jun 23 14:59:20 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-08-21 (305 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1.1 apt 1.3.5 SourcePackage: click Title: package python3-click-package 0.4.46+16.10.20170607.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to yakkety on 2016-10-19 (247 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1700089/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
