Re: [Touch-packages] [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output
Be aware the messages will come back next time you boot after upgrading a package that touches something in /etc, which will trigger another scan by ureadahead. Better is the workaround I gave back in #9, but really what I recommend is just purge ureadahead. ureadahead only ever can help the second (and subsequent) time one boots after updating the system, and these days I never reboot unless I have updated, since suspend works for desktops/laptops and who reboots servers if you don't have to? Rich On Sat, Sep 22, 2018 at 8:54 AM Anders Hall wrote: > > Thanks, workaround in #19 seem to have removed (thousands of) these > messages. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1579580 > > Title: > ureadahead reports relative path errors in journalctl output > > Status in ureadahead package in Ubuntu: > Confirmed > > Bug description: > ureadahead reports relative path errors in my journalctl output. > > This is currently 4368 lines of useless annoyances in my logs. > > To see if you have this problem, run: journalctl -b | grep ureadahead > | grep relative | wc -l > > Thanks > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: ureadahead 0.100.0-19 > ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 > Uname: Linux 4.4.0-22-generic x86_64 > NonfreeKernelModules: zfs zunicode zcommon znvpair zavl > ApportVersion: 2.20.1-0ubuntu2 > Architecture: amd64 > Date: Sun May 8 15:55:18 2016 > InstallationDate: Installed on 2016-04-04 (34 days ago) > InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 > (20160325) > ProcEnviron: >TERM=linux >PATH=(custom, no user) >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: ureadahead > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1579580 Title: ureadahead reports relative path errors in journalctl output Status in ureadahead package in Ubuntu: Confirmed Bug description: ureadahead reports relative path errors in my journalctl output. This is currently 4368 lines of useless annoyances in my logs. To see if you have this problem, run: journalctl -b | grep ureadahead | grep relative | wc -l Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ureadahead 0.100.0-19 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun May 8 15:55:18 2016 InstallationDate: Installed on 2016-04-04 (34 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ureadahead UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 219057] Re: Bluetooth does not coexist with WiFi
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- 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/219057 Title: Bluetooth does not coexist with WiFi Status in bluez package in Ubuntu: Expired Bug description: On my system bluetooth and wifi are unusable together. I have a built- in CSR-based bluetooth module in my laptop, and an Atheros wifi. Wifi transfers slow to a halt whenever there is BT traffic. For example, if I play a music file from another machine through the network using a BT headset, only the first few seconds of the file will play until the player runs out of buffered data. No further data is downloaded. Web pages also do not download, and I even lose connection to AP from time to time. At the same time, it looks like AFH is trying to work. If I monitor the value returned by 'hcitool afh', it changes. But this seems to have little effect on connection quality. Is this a problem with my hardware, or the AFH implementation? Is there a way to force bluetooth to not use the channels in use by WiFi? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/219057/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1731699] Re: Unable to transfer files via bluetooth to paired android phone
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- 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/1731699 Title: Unable to transfer files via bluetooth to paired android phone Status in bluez package in Ubuntu: Expired Bug description: I'm trying to transfer files to my phone (Nexus 6P - Android 8.0) from Ubuntu 17.10, but when I pair the laptop and phone, I don't think it's pairing in a way which permits file transfers. When I pair, my phone gives me a checkbox "Allow xx to access your contacts and call history", but there is no option to allow file transfers. Then, when I attempt to transfer a file via Bluetooth from Ubuntu the transfer fails and I get the message "There was an error". My phone doesn't seem to recognise there's been any attempt to send a file. Discussed at https://ubuntuforums.org/showthread.php?t=2377286 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731699/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()
-- 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/1792745 Title: NetworkManager crashed with SIGSEGV in _int_malloc() Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: New Bug description: I’m seeing NetworkManager crash several times on startup and on resume from suspend. Apport doesn’t catch those for some reason, but this happened when I tried to reproduce by manually running NetworkManager --debug. (Different crash from bug 1792743? Also apport-retrace didn’t seem to like that one.) ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: network-manager 1.12.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Date: Sat Sep 15 14:04:50 2018 EcryptfsInUse: Yes ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system. Do not edit. InstallationDate: Installed on 2016-02-19 (939 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false ProcCmdline: NetworkManager --debug SegvAnalysis: Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp %rcx,0x18(%rdx) PC (0x7f79966ea378) ok source "%rcx" ok destination "0x18(%rdx)" (0x0018) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: network-manager StacktraceTop: _int_malloc (av=av@entry=0x7f799683ac40 , bytes=bytes@entry=4096) at malloc.c:4014 __libc_calloc (n=, elem_size=) at malloc.c:3420 g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314 _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88 Title: NetworkManager crashed with SIGSEGV in _int_malloc() UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago) UserGroups: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 8: Error: NetworkManager is not running. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 8: Error: NetworkManager is not running. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1792745/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()
** Patch added: "debdiff adding upstream patch" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1792745/+attachment/5191867/+files/network-manager_1.12.2-0ubuntu4_lp1792745.debdiff -- 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/1792745 Title: NetworkManager crashed with SIGSEGV in _int_malloc() Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: New Bug description: I’m seeing NetworkManager crash several times on startup and on resume from suspend. Apport doesn’t catch those for some reason, but this happened when I tried to reproduce by manually running NetworkManager --debug. (Different crash from bug 1792743? Also apport-retrace didn’t seem to like that one.) ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: network-manager 1.12.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Date: Sat Sep 15 14:04:50 2018 EcryptfsInUse: Yes ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system. Do not edit. InstallationDate: Installed on 2016-02-19 (939 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false ProcCmdline: NetworkManager --debug SegvAnalysis: Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp %rcx,0x18(%rdx) PC (0x7f79966ea378) ok source "%rcx" ok destination "0x18(%rdx)" (0x0018) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: network-manager StacktraceTop: _int_malloc (av=av@entry=0x7f799683ac40 , bytes=bytes@entry=4096) at malloc.c:4014 __libc_calloc (n=, elem_size=) at malloc.c:3420 g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314 _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88 Title: NetworkManager crashed with SIGSEGV in _int_malloc() UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago) UserGroups: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 8: Error: NetworkManager is not running. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 8: Error: NetworkManager is not running. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1792745/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754777] Re: bionic casper nfsboot not reaching desktop env, failure to mount various kernel filesystems and /tmp
*** This bug is a duplicate of bug 1755863 *** https://bugs.launchpad.net/bugs/1755863 ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released -- 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/1754777 Title: bionic casper nfsboot not reaching desktop env, failure to mount various kernel filesystems and /tmp Status in casper package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Bug description: 1st of all, i am successfully using casper netboot with this distros: menu label Ubuntu 13.10 "Saucy Salamander" - Release i386 menu label Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 menu label Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 menu label Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 but not with menu label Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 boot process gets to the point of running this services dev-hugepages.mount dev-mqueue.mount sys-fs-fuse-connections.mount sys-kernel-config.mount sys-kernel-debug.mount tmp.mount and it stops in emergency console. Too run further to gnome session i've need to do #systemctl mask dev-hugepages.mount #systemctl mask dev-mqueue.mount #systemctl mask sys-fs-fuse-connections.mount #systemctl mask sys-kernel-config.mount #systemctl mask sys-kernel-debug.mount #systemctl mask tmp.mount #ctrl-d after this i get normal live session except wrong dns setting, which is fixed by setting my router's dns as resolver #echo "nameserver 192.168.1.1" > /etc/resolv.conf Please fix boot process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1754777/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
@Timo: This seems to be a reason to upgrade xkeyboard-config in Debian (and then Ubuntu) to 2.24. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) Status in xkeyboard-config package in Ubuntu: New Bug description: Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793920] [NEW] software-properties-gtk prompts me to install the nVidia proprietary drivers on a system using Xen, leading to no video on the next boot
Public bug reported: nVidia's proprietary drivers don't work when the kernel is running under the Xen hypervisor; nVidia knows this and has chosen not to implement Xen support. However, I did not know this. On my Ubuntu Xen dom0 system, I went into Ubuntu's "Software & Updates", on the "Additional Drivers" tab, and selected "Using NVIDIA driver metapackage from nvidia-driver-390" as my GPU driver. The driver was available, with no warning associated with it, and it seemed to install correctly. However, upon rebooting, I had no video output. I had to mess about in Grub to boot the system without Xen, and now I'm going to have to uninstall the nVidia proprietary drivers. The "Additional Drivers" UI should not present the option to install the proprietary nVidia drivers if the system is running under Xen, because doing so renders the system unusable in that configuration until the drivers are removed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-gtk 0.96.24.32.5 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 22 15:09:38 2018 InstallationDate: Installed on 2017-08-06 (412 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to bionic on 2018-05-29 (116 days ago) ** 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/1793920 Title: software-properties-gtk prompts me to install the nVidia proprietary drivers on a system using Xen, leading to no video on the next boot Status in software-properties package in Ubuntu: New Bug description: nVidia's proprietary drivers don't work when the kernel is running under the Xen hypervisor; nVidia knows this and has chosen not to implement Xen support. However, I did not know this. On my Ubuntu Xen dom0 system, I went into Ubuntu's "Software & Updates", on the "Additional Drivers" tab, and selected "Using NVIDIA driver metapackage from nvidia-driver-390" as my GPU driver. The driver was available, with no warning associated with it, and it seemed to install correctly. However, upon rebooting, I had no video output. I had to mess about in Grub to boot the system without Xen, and now I'm going to have to uninstall the nVidia proprietary drivers. The "Additional Drivers" UI should not present the option to install the proprietary nVidia drivers if the system is running under Xen, because doing so renders the system unusable in that configuration until the drivers are removed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-gtk 0.96.24.32.5 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 22 15:09:38 2018 InstallationDate: Installed on 2017-08-06 (412 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to bionic on 2018-05-29 (116 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1793920/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
Following upstream suggestion ** Package changed: gnome-settings-daemon (Ubuntu) => xkeyboard-config (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) Status in xkeyboard-config package in Ubuntu: New Bug description: Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1791367] [NEW] Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
You have been subscribed to a public bug: Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xkeyboard-config (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic has-workaround reproducible ubuntu wayland-session -- Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) https://bugs.launchpad.net/bugs/1791367 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
Just upgraded today from 16.04 to 18.04 and I got the same issue. The systemd-shim package was still installed, the only way I had to uninstall it was to force remove systemd, then I was able to purge systemd-shim and reinstall systemd I made sure that xenial was up2date before starting the update (using update-manager) to 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/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Confirmed Status in systemd-shim package in Ubuntu: Incomplete Status in systemd source package in Bionic: Confirmed Status in systemd-shim source package in Bionic: Confirmed Bug description: $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 63 files and directories currently installed.) Removing systemd-shim (9-1bzr4ubuntu1) ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed dpkg: error processing package systemd-shim (--remove): subprocess installed post-removal script returned error exit status 2 Errors were encountered while processing: systemd-shim E: Sub-process /usr/bin/dpkg returned an error code (1) Commenting out the dpkg-divert in systemd-shim's postrm solved this for me and I was about to continue the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1571147] Re: package systemd-shim 9-1bzr2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 2
*** This bug is a duplicate of bug 1773859 *** https://bugs.launchpad.net/bugs/1773859 ** This bug has been marked a duplicate of bug 1641324 package systemd-shim 9-1bzr4ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 ** This bug is no longer a duplicate of bug 1641324 package systemd-shim 9-1bzr4ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 ** This bug has been marked a duplicate of bug 1773859 upgrades to 18.04 fail -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1571147 Title: package systemd-shim 9-1bzr2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 2 Status in systemd-shim package in Ubuntu: Confirmed Bug description: No apport report written because the error message indicates its a followup error from a previous failure. Errors were encountered while processing: samba-common grub-pc samba-common-bin E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 15.10 Package: systemd-shim 9-1bzr2 ProcVersionSignature: Ubuntu 3.19.0-58.64-generic 3.19.8-ckt16 Uname: Linux 3.19.0-58-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 Date: Sat Apr 16 09:15:28 2016 DuplicateSignature: package:systemd-shim:9-1bzr2:subprocess new pre-installation script returned error exit status 2 ErrorMessage: subprocess new pre-installation script returned error exit status 2 InstallationDate: Installed on 2016-04-12 (3 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1.1 apt 1.0.9.7ubuntu4.2 SourcePackage: systemd-shim Title: package systemd-shim 9-1bzr2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 2 UpgradeStatus: Upgraded to wily on 2016-04-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1571147/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641438] Re: package systemd-shim 9-1bzr4ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2
*** This bug is a duplicate of bug 1773859 *** https://bugs.launchpad.net/bugs/1773859 ** This bug is no longer a duplicate of bug 1641324 package systemd-shim 9-1bzr4ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 ** This bug has been marked a duplicate of bug 1773859 upgrades to 18.04 fail -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1641438 Title: package systemd-shim 9-1bzr4ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 Status in systemd-shim package in Ubuntu: New Bug description: while installing this was shown ProblemType: Package DistroRelease: Ubuntu 16.10 Package: systemd-shim 9-1bzr4ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 Date: Sun Nov 13 23:15:13 2016 ErrorMessage: subprocess installed post-removal script returned error exit status 2 InstallationDate: Installed on 2016-11-12 (1 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.2.12~ubuntu16.04.1 SourcePackage: systemd-shim Title: package systemd-shim 9-1bzr4ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 UpgradeStatus: Upgraded to yakkety on 2016-11-13 (0 days ago) mtime.conffile..etc.dbus-1.system.d.org.freedesktop.systemd1.conf: 2016-10-26T16:41:33 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1641438/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641324] Re: package systemd-shim 9-1bzr4ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2
*** This bug is a duplicate of bug 1773859 *** https://bugs.launchpad.net/bugs/1773859 ** Changed in: systemd-shim (Ubuntu) Importance: High => Critical ** This bug has been marked a duplicate of bug 1773859 upgrades to 18.04 fail -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1641324 Title: package systemd-shim 9-1bzr4ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 Status in systemd-shim package in Ubuntu: Confirmed Bug description: Restoring Xubuntu Xenial to manifest list of contents ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-shim 9-1bzr4ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Nov 12 11:19:26 2016 ErrorMessage: subprocess installed post-removal script returned error exit status 2 InstallationDate: Installed on 2014-03-19 (969 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: systemd-shim Title: package systemd-shim 9-1bzr4ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-11-11 (0 days ago) mtime.conffile..etc.dbus-1.system.d.org.freedesktop.systemd1.conf: 2016-10-26T09:04:44 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1641324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793916] [NEW] package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2
Public bug reported: During upgrade received following errors: 1. installed systemd-shim package post-removal script subprocess returned error exit status 2 2. could not install '/var/cache/apt/archives/systemd-sysv_237-3ubuntu10.3_amd64.deb 3. Could not install upgrades - The upgrade has aborted your system could be in an unusable state. A recovery will run now (dpkg -configure -a) 4. The upgrade has completed but there were errors during the upgrade process 5. lsb_release -a resulted in Ubuntu 18.04.1 LTS Then no GUI when boot So did: sudo apt purge gdm gdm3 sudo apt install gdm3 ubuntu-desktop systemctl restart gdm And received: The system is runnin in low graphics mode. But still no GUI Then did: sudo apt-get install lightdm sudo dpkg-reconfigure lightdm And then got a working GUI. Then followed errors and request for bug report ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Sat Sep 22 11:19:55 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2013-04-01 (1999 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: systemd Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-09-22 (0 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1793916 Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 Status in systemd package in Ubuntu: New Bug description: During upgrade received following errors: 1. installed systemd-shim package post-removal script subprocess returned error exit status 2 2. could not install '/var/cache/apt/archives/systemd-sysv_237-3ubuntu10.3_amd64.deb 3. Could not install upgrades - The upgrade has aborted your system could be in an unusable state. A recovery will run now (dpkg -configure -a) 4. The upgrade has completed but there were errors during the upgrade process 5. lsb_release -a resulted in Ubuntu 18.04.1 LTS Then no GUI when boot So did: sudo apt purge gdm gdm3 sudo apt install gdm3 ubuntu-desktop systemctl restart gdm And received: The system is runnin in low graphics mode. But still no GUI Then did: sudo apt-get install lightdm sudo dpkg-reconfigure lightdm And then got a working GUI. Then followed errors and request for bug report ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Sat Sep 22 11:19:55 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2013-04-01 (1999 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: systemd Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-09-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1793916/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793907] [NEW] package console-setup 1.178ubuntu2.7 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert
Public bug reported: Somehow I was directed to this page. Unfortunately I domn't have any further information ProblemType: Package DistroRelease: Ubuntu 18.04 Package: console-setup 1.178ubuntu2.7 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: libqt5opengl5:amd64: Install virtualbox-5.2:amd64: Install libsdl-ttf2.0-0:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Sep 17 20:47:48 2018 ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: console-setup Title: package console-setup 1.178ubuntu2.7 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: console-setup (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 console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1793907 Title: package console-setup 1.178ubuntu2.7 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert Status in console-setup package in Ubuntu: New Bug description: Somehow I was directed to this page. Unfortunately I domn't have any further information ProblemType: Package DistroRelease: Ubuntu 18.04 Package: console-setup 1.178ubuntu2.7 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: libqt5opengl5:amd64: Install virtualbox-5.2:amd64: Install libsdl-ttf2.0-0:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Sep 17 20:47:48 2018 ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: console-setup Title: package console-setup 1.178ubuntu2.7 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1793907/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :
** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubiquity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1755863 Title: netbooting the bionic live CD over NFS goes straight to maintenance mode : Status in casper package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: netbooting the bionic live CD[1] over NFS goes straight to maintenance mode : [1] http://cdimage.ubuntu.com/daily-live/current/ # casper.log Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' (uid=999 pid=569 comm="" label="unconfined") dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 'org.gtk.vfs.Daemon' dbus-daemon[568]: [session uid=999 pid=568] Activating service name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=569 comm="" label="unconfined") fuse: device not found, try 'modprobe fuse' first dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 'org.gtk.vfs.Metadata' (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed A connection to the bus can't be made done. Begin: Setting up init... ... done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1755863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754777] Re: bionic casper nfsboot not reaching desktop env, failure to mount various kernel filesystems and /tmp
*** This bug is a duplicate of bug 1755863 *** https://bugs.launchpad.net/bugs/1755863 ** This bug has been marked a duplicate of bug 1755863 netbooting the bionic live CD over NFS goes straight to maintenance mode : -- 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/1754777 Title: bionic casper nfsboot not reaching desktop env, failure to mount various kernel filesystems and /tmp Status in casper package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: 1st of all, i am successfully using casper netboot with this distros: menu label Ubuntu 13.10 "Saucy Salamander" - Release i386 menu label Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 menu label Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 menu label Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 but not with menu label Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 boot process gets to the point of running this services dev-hugepages.mount dev-mqueue.mount sys-fs-fuse-connections.mount sys-kernel-config.mount sys-kernel-debug.mount tmp.mount and it stops in emergency console. Too run further to gnome session i've need to do #systemctl mask dev-hugepages.mount #systemctl mask dev-mqueue.mount #systemctl mask sys-fs-fuse-connections.mount #systemctl mask sys-kernel-config.mount #systemctl mask sys-kernel-debug.mount #systemctl mask tmp.mount #ctrl-d after this i get normal live session except wrong dns setting, which is fixed by setting my router's dns as resolver #echo "nameserver 192.168.1.1" > /etc/resolv.conf Please fix boot process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1754777/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754828] Re: Ubuntu 18.04 LTS fails to PXE boot
*** This bug is a duplicate of bug 1755863 *** https://bugs.launchpad.net/bugs/1755863 ** Also affects: casper (Ubuntu) Importance: Undecided Status: New ** Also 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/1754828 Title: Ubuntu 18.04 LTS fails to PXE boot Status in casper package in Ubuntu: New Status in systemd package in Ubuntu: New Status in ubiquity package in Ubuntu: Confirmed Bug description: i just downloaded the daily-live image from: http://cdimage.ubuntu.com/daily-live/current/bionic-desktop-amd64.iso and added it to my PXE server project (for more information see: https://github.com/beta-tester/RPi-PXE-Server/tree/testing). when i try to PXE boot the PC or VirtualBox from that ISO daily-live image, i run into the emergency mode console. earlier ISO images of Ubuntu (16.04.04, 17.10.1) are PXE booting this way correctly to the UI on both, PC and VirtualBox. when i burm the ISO of Ubuntu 18.04 LTS daily-live to a media and boot from it, it boots correctly. this are the PXE boot menu parameters: LABEL Ubuntu x64 Daily-Live KERNEL /nfs/ubuntu-daily-x64/casper/vmlinuz.efi APPEND initrd=/nfs/ubuntu-daily-x64/casper/initrd.lz netboot=nfs nfsroot=192.168.1.1:/srv/nfs/ubuntu-daily-x64 ro file=/cdrom/preseed/ubuntu.seed boot=casper -- TEXT HELP Boot to Ubuntu x64 Daily-Live User: ubuntu ENDTEXT this is the log i could grab from the emergency mode console: see attached log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1754828/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773045] Re: Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-builder.css
Just remove the line (73) in /usr/share/themes/Radiance/gtk-3.20/gtk-
main.css, it's useless & not in ambiance..
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1773045
Title:
Radiance/gtk-3.20/gtk-main.css attempts to import nonexistent gnome-
builder.css
Status in Ubuntu theme:
Confirmed
Status in ubuntu-themes package in Ubuntu:
Confirmed
Bug description:
The file /usr/share/themes/Radiance/gtk-3.20/gtk-main.css contains the
line
@import url("apps/gnome-builder.css");
But this file does not exist in this package or any other, as far as I
can tell from apt-file. This triggers an annoying warning when
running various applications (e.g. evince):
(evince:12714): Gtk-WARNING **: 18:41:45.136: Theme parsing error:
gtk-main.css:73:38: Failed to import: Error opening file
/usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such
file or directory
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: light-themes 16.10+18.04.20180421.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed May 23 18:58:41 2018
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: Upgraded to bionic on 2018-05-23 (1 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1773045/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793900] [NEW] NO HDMI Sound Working ! but not after Suspend! Help
Public bug reported: upload=true=true= !! !!ALSA Information Script v 0.4.64 !! !!Script ran on: Sun Sep 16 13:13:04 UTC 2018 !!Linux Distribution !!-- Ubuntu 18.04.1 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=bionic !!DMI Information !!--- Manufacturer: HP Product Name: OMEN X by HP Laptop 17-ap0xx Product Version: Firmware Version: F.18 Board Vendor: HP Board Name:83A5 !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ACPI0003:00/status 15 /sys/bus/acpi/devices/ACPI000C:00/status 15 /sys/bus/acpi/devices/HPIC0003:00/status 15 /sys/bus/acpi/devices/HPIC0004:00/status 15 /sys/bus/acpi/devices/HPQ6007:00/status 15 /sys/bus/acpi/devices/HPQ8001:00/status 15 /sys/bus/acpi/devices/INT33A1:00/status 15 /sys/bus/acpi/devices/INT3400:00/status 15 /sys/bus/acpi/devices/INT3403:00/status 15 /sys/bus/acpi/devices/INT3403:01/status 15 /sys/bus/acpi/devices/INT3403:02/status 15 /sys/bus/acpi/devices/INT3403:03/status 15 /sys/bus/acpi/devices/INT340E:00/status 15 /sys/bus/acpi/devices/INT345D:00/status 15 /sys/bus/acpi/devices/INT3F0D:00/status 15 /sys/bus/acpi/devices/LNXPOWER:00/status 1 /sys/bus/acpi/devices/PNP0103:00/status 15 /sys/bus/acpi/devices/PNP0C02:01/status 15 /sys/bus/acpi/devices/PNP0C02:03/status 3 /sys/bus/acpi/devices/PNP0C02:05/status 3 /sys/bus/acpi/devices/PNP0C04:00/status 31 /sys/bus/acpi/devices/PNP0C09:00/status 15 /sys/bus/acpi/devices/PNP0C0A:00/status 31 /sys/bus/acpi/devices/PNP0C0C:00/status 15 /sys/bus/acpi/devices/PNP0C0F:00/status 9 /sys/bus/acpi/devices/PNP0C0F:01/status 9 /sys/bus/acpi/devices/PNP0C0F:02/status 9 /sys/bus/acpi/devices/PNP0C0F:03/status 9 /sys/bus/acpi/devices/PNP0C0F:04/status 9 /sys/bus/acpi/devices/PNP0C0F:05/status 9 /sys/bus/acpi/devices/PNP0C0F:06/status 9 /sys/bus/acpi/devices/PNP0C0F:07/status 9 /sys/bus/acpi/devices/SYN3265:00/status 15 /sys/bus/acpi/devices/device:11/status 15 /sys/bus/acpi/devices/device:72/status 15 /sys/bus/acpi/devices/device:81/status 11 !!Kernel Information !!-- Kernel release:4.15.0-35-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k4.15.0-35-generic Library version:1.1.3 Utilities version: 1.1.3 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xdc628000 irq 137 !!PCI Soundcards installed in the system !!-- 00:1f.3 Audio device: Intel Corporation CM238 HD Audio Controller (rev 31) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0403: 8086:a171 (rev 31) (prog-if 80) Subsystem: 103c:83a5 !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 !!Loaded sound module options !!--- !!Module: snd_hda_intel align_buffer_size : -1 bdl_pos_adj : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) index :
[Touch-packages] [Bug 1793893] [NEW] Tracking module not included
Public bug reported: The tracking module from opencv_contrib is omitted in packaging. Actually it is commented out in the .install file. ** Affects: opencv (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opencv in Ubuntu. https://bugs.launchpad.net/bugs/1793893 Title: Tracking module not included Status in opencv package in Ubuntu: New Bug description: The tracking module from opencv_contrib is omitted in packaging. Actually it is commented out in the .install file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1793893/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output
Thanks, workaround in #19 seem to have removed (thousands of) these messages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1579580 Title: ureadahead reports relative path errors in journalctl output Status in ureadahead package in Ubuntu: Confirmed Bug description: ureadahead reports relative path errors in my journalctl output. This is currently 4368 lines of useless annoyances in my logs. To see if you have this problem, run: journalctl -b | grep ureadahead | grep relative | wc -l Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ureadahead 0.100.0-19 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun May 8 15:55:18 2016 InstallationDate: Installed on 2016-04-04 (34 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ureadahead UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793876] Re: software-properties-qt/kde does not show in menus
** Tags added: patch -- 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/1793876 Title: software-properties-qt/kde does not show in menus Status in software-properties package in Ubuntu: New Bug description: Cosmic and Bionic Desktop file sets: NoDisplay=true resulting in no software sources menu entry in KDE menu. This was probably just about ok when Plasma Discover was able to launch this via a menu item in its options, but at least for Plasma 5.13 this is currently broken, and Discover's built-in source selection has further issues. Plus many users decide not to use Discover at all, and even uninstall it altogether. Not withstanding all that, it is just desirable that someone can just type "software" or "sources" in to the search box in Plasma's main menu and find the menu item/launcher for this and use software- properties without having to go a more complicated path. Solution is simply removing the "NoDisplay=true" line from the .desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1793876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793876] Re: software-properties-qt/kde does not show in menus
Debdiff to solve this. ** Patch added: "software-properties_0.96.28_v1.debdiff" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1793876/+attachment/5191717/+files/software-properties_0.96.28_v1.debdiff -- 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/1793876 Title: software-properties-qt/kde does not show in menus Status in software-properties package in Ubuntu: New Bug description: Cosmic and Bionic Desktop file sets: NoDisplay=true resulting in no software sources menu entry in KDE menu. This was probably just about ok when Plasma Discover was able to launch this via a menu item in its options, but at least for Plasma 5.13 this is currently broken, and Discover's built-in source selection has further issues. Plus many users decide not to use Discover at all, and even uninstall it altogether. Not withstanding all that, it is just desirable that someone can just type "software" or "sources" in to the search box in Plasma's main menu and find the menu item/launcher for this and use software- properties without having to go a more complicated path. Solution is simply removing the "NoDisplay=true" line from the .desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1793876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793876] Re: software-properties-qt/kde does not show in menus
** Description changed: Cosmic and Bionic Desktop file sets: NoDisplay=true resulting in no software sources menu entry in KDE menu. This was probably just about ok when Plasma Discover was able to launch - this via a menu item in it's options, but at least for Plasma 5.13 this - is currently broken, and Disover's built-in source selection has further - issues. Plus many users decide not to use Discover at all, and even - uninstall it altogether. + this via a menu item in its options, but at least for Plasma 5.13 this + is currently broken, and Discover's built-in source selection has + further issues. Plus many users decide not to use Discover at all, and + even uninstall it altogether. Not withstanding all that, it is just desirable that someone can just type "software" or "sources" in to the search box in Plasma's main menu and find the menu item/launcher for this and use software-properties without having to go a more complicated path. Solution is simply removing the "NoDisplay=true" line from the .desktop file -- 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/1793876 Title: software-properties-qt/kde does not show in menus Status in software-properties package in Ubuntu: New Bug description: Cosmic and Bionic Desktop file sets: NoDisplay=true resulting in no software sources menu entry in KDE menu. This was probably just about ok when Plasma Discover was able to launch this via a menu item in its options, but at least for Plasma 5.13 this is currently broken, and Discover's built-in source selection has further issues. Plus many users decide not to use Discover at all, and even uninstall it altogether. Not withstanding all that, it is just desirable that someone can just type "software" or "sources" in to the search box in Plasma's main menu and find the menu item/launcher for this and use software- properties without having to go a more complicated path. Solution is simply removing the "NoDisplay=true" line from the .desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1793876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793876] [NEW] software-properties-qt/kde does not show in menus
Public bug reported: Cosmic and Bionic Desktop file sets: NoDisplay=true resulting in no software sources menu entry in KDE menu. This was probably just about ok when Plasma Discover was able to launch this via a menu item in its options, but at least for Plasma 5.13 this is currently broken, and Discover's built-in source selection has further issues. Plus many users decide not to use Discover at all, and even uninstall it altogether. Not withstanding all that, it is just desirable that someone can just type "software" or "sources" in to the search box in Plasma's main menu and find the menu item/launcher for this and use software-properties without having to go a more complicated path. Solution is simply removing the "NoDisplay=true" line from the .desktop file ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- 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/1793876 Title: software-properties-qt/kde does not show in menus Status in software-properties package in Ubuntu: New Bug description: Cosmic and Bionic Desktop file sets: NoDisplay=true resulting in no software sources menu entry in KDE menu. This was probably just about ok when Plasma Discover was able to launch this via a menu item in its options, but at least for Plasma 5.13 this is currently broken, and Discover's built-in source selection has further issues. Plus many users decide not to use Discover at all, and even uninstall it altogether. Not withstanding all that, it is just desirable that someone can just type "software" or "sources" in to the search box in Plasma's main menu and find the menu item/launcher for this and use software- properties without having to go a more complicated path. Solution is simply removing the "NoDisplay=true" line from the .desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1793876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793851] Re: packagekitd crashed with SIGABRT
*** This bug is a duplicate of bug 1788099 *** https://bugs.launchpad.net/bugs/1788099 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1788099, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1793851/+attachment/5191629/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1793851/+attachment/5191631/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1793851/+attachment/5191635/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1793851/+attachment/5191636/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1793851/+attachment/5191637/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1793851/+attachment/5191638/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1793851/+attachment/5191639/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1788099 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1793851 Title: packagekitd crashed with SIGABRT Status in packagekit package in Ubuntu: New Bug description: Error happened in backround, while installing packages from Software Center ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: packagekit 1.1.10-1ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 Date: Sat Sep 22 09:59:39 2018 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2018-09-14 (7 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180913) ProcCmdline: /usr/lib/packagekit/packagekitd Signal: 6 SourcePackage: packagekit StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: packagekitd crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1793851/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
