[Touch-packages] [Bug 2017317] Re: Ubuntu: upon reboot, forever waiting for encrypted swapfile ...
I've initially reported this bug there https://gitlab.com/cryptsetup/cryptsetup/-/issues/811#note_1361818938 But got recommended posting it here instead. There, Milan Broz added following: "My guess here is that /etc/crypttab is missing something about cryptswap device, but we cannot do anything with these problems in the upstream cryptsetup project (also, Debian/Ubuntu specific cryptsetup tools are not even maintained upstream." -- 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/2017317 Title: Ubuntu: upon reboot, forever waiting for encrypted swapfile ... Status in systemd package in Ubuntu: New Bug description: ### Issue description When restarting my machine, cryptsetup waits forever. Waiting for the swapfile. Unable to start Ubuntu at all. Error message is: ``` cryptsetup: Waiting for encrypted source device /swapfile... ``` ### Steps for reproducing the issue 1. Do a fresh installation of Ubuntu, unencrypted. 2. Later, due to restrictions at work, encrypt Ubuntu POST installation accordingly to this article: https://jumpcloud.com/blog/how-to-encrypt-ubuntu-20-04-desktop-post-installation 3. Reboot, all works fine, but ... 4. Later, after a couple of months, install a new Linux kernel and then ... 5. Upon boot cryptsetup gets stuck, waits forever. See attached photo. ### Additional info I've found a temporary, painful workaround by rebooting in recovery mode and running this command every time: ``` sudo update-initramfs -u -k all ``` Then I can boot again. But I have to do this every time. Why? ### Debug log Hard to say but here's the output of this command `journalctl | grep crypt`, not sure if you can find anything interesting about it: ``` Apr 21 13:48:28 M1 audit[179547]: AVC apparmor="DENIED" operation="getattr" class="file" info="Failed name lookup - disconnected path" error=-13 profile="/usr/bin/evince-thumbnailer" name="home/.ecryptfs/michael-heuberger/.Private/ECRYPTFS_FNEK_ENCRYPTED.FWaKkF5ZO-vAFETGnoPriOb55KN8iA.SprD0W8LFNkfXu75b-QusjTdAA---/ECRYPTFS_FNEK_ENCRYPTED.FXaKkF5ZO-vAFETGnoPriOb55KN8iA.SprD0JjExLlqv3Fk6x4GGYcQdjXda2554lHGsMAmCwjYZWGA-" pid=179547 comm="evince-thumbnai" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Apr 21 17:01:49 M1 gdm-password][219451]: pam_ecryptfs: pam_sm_authenticate: /home/michael-heuberger is already mounted Apr 21 17:26:59 M1 systemd[1]: Requested transaction contradicts existing jobs: Transaction for plymouth-quit.service/start is destructive (dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dPLAIN\x2dcryptswap1.swap has 'stop' job queued, but 'start' is included in transaction). Apr 21 17:26:59 M1 systemd[1]: gdm.service: Failed to enqueue OnFailure= job, ignoring: Transaction for plymouth-quit.service/start is destructive (dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dPLAIN\x2dcryptswap1.swap has 'stop' job queued, but 'start' is included in transaction). Apr 21 17:26:59 M1 systemd[3094]: Stopping GnuPG cryptographic agent and passphrase cache... Apr 21 17:27:00 M1 systemd[3094]: Stopped GnuPG cryptographic agent and passphrase cache. Apr 21 17:27:07 M1 systemd[1]: Stopped target Local Encrypted Volumes. Apr 21 17:27:08 M1 umount.ecryptfs[231225]: Failed to find key with sig [2bda85c181b04823]: Required key not available Apr 21 17:27:08 M1 umount.ecryptfs[231225]: Failed to find key with sig [96c111e5680ecc45]: Required key not available Apr 21 17:27:09 M1 systemd[1]: Deactivating swap /dev/disk/by-id/dm-name-cryptswap1... Apr 21 17:27:09 M1 systemd[1]: dev-disk-by\x2dlabel-cryptswap1.swap: Deactivated successfully. Apr 21 17:27:09 M1 systemd[1]: Deactivated swap /dev/disk/by-label/cryptswap1. ``` Do you have any tips, advice please, how to fix this, how can I reboot my machine without running `update-initramfs` every time? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2017317/+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 2017317] [NEW] Ubuntu: upon reboot, forever waiting for encrypted swapfile ...
Public bug reported: ### Issue description When restarting my machine, cryptsetup waits forever. Waiting for the swapfile. Unable to start Ubuntu at all. Error message is: ``` cryptsetup: Waiting for encrypted source device /swapfile... ``` ### Steps for reproducing the issue 1. Do a fresh installation of Ubuntu, unencrypted. 2. Later, due to restrictions at work, encrypt Ubuntu POST installation accordingly to this article: https://jumpcloud.com/blog/how-to-encrypt-ubuntu-20-04-desktop-post-installation 3. Reboot, all works fine, but ... 4. Later, after a couple of months, install a new Linux kernel and then ... 5. Upon boot cryptsetup gets stuck, waits forever. See attached photo. ### Additional info I've found a temporary, painful workaround by rebooting in recovery mode and running this command every time: ``` sudo update-initramfs -u -k all ``` Then I can boot again. But I have to do this every time. Why? ### Debug log Hard to say but here's the output of this command `journalctl | grep crypt`, not sure if you can find anything interesting about it: ``` Apr 21 13:48:28 M1 audit[179547]: AVC apparmor="DENIED" operation="getattr" class="file" info="Failed name lookup - disconnected path" error=-13 profile="/usr/bin/evince-thumbnailer" name="home/.ecryptfs/michael-heuberger/.Private/ECRYPTFS_FNEK_ENCRYPTED.FWaKkF5ZO-vAFETGnoPriOb55KN8iA.SprD0W8LFNkfXu75b-QusjTdAA---/ECRYPTFS_FNEK_ENCRYPTED.FXaKkF5ZO-vAFETGnoPriOb55KN8iA.SprD0JjExLlqv3Fk6x4GGYcQdjXda2554lHGsMAmCwjYZWGA-" pid=179547 comm="evince-thumbnai" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Apr 21 17:01:49 M1 gdm-password][219451]: pam_ecryptfs: pam_sm_authenticate: /home/michael-heuberger is already mounted Apr 21 17:26:59 M1 systemd[1]: Requested transaction contradicts existing jobs: Transaction for plymouth-quit.service/start is destructive (dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dPLAIN\x2dcryptswap1.swap has 'stop' job queued, but 'start' is included in transaction). Apr 21 17:26:59 M1 systemd[1]: gdm.service: Failed to enqueue OnFailure= job, ignoring: Transaction for plymouth-quit.service/start is destructive (dev-disk-by\x2did-dm\x2duuid\x2dCRYPT\x2dPLAIN\x2dcryptswap1.swap has 'stop' job queued, but 'start' is included in transaction). Apr 21 17:26:59 M1 systemd[3094]: Stopping GnuPG cryptographic agent and passphrase cache... Apr 21 17:27:00 M1 systemd[3094]: Stopped GnuPG cryptographic agent and passphrase cache. Apr 21 17:27:07 M1 systemd[1]: Stopped target Local Encrypted Volumes. Apr 21 17:27:08 M1 umount.ecryptfs[231225]: Failed to find key with sig [2bda85c181b04823]: Required key not available Apr 21 17:27:08 M1 umount.ecryptfs[231225]: Failed to find key with sig [96c111e5680ecc45]: Required key not available Apr 21 17:27:09 M1 systemd[1]: Deactivating swap /dev/disk/by-id/dm-name-cryptswap1... Apr 21 17:27:09 M1 systemd[1]: dev-disk-by\x2dlabel-cryptswap1.swap: Deactivated successfully. Apr 21 17:27:09 M1 systemd[1]: Deactivated swap /dev/disk/by-label/cryptswap1. ``` Do you have any tips, advice please, how to fix this, how can I reboot my machine without running `update-initramfs` every time? Thanks! ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot of error message upon boot" https://bugs.launchpad.net/bugs/2017317/+attachment/5666561/+files/IMG_2291.jpg ** Bug watch added: gitlab.com/cryptsetup/cryptsetup/-/issues #811 https://gitlab.com/cryptsetup/cryptsetup/-/issues/811 -- 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/2017317 Title: Ubuntu: upon reboot, forever waiting for encrypted swapfile ... Status in systemd package in Ubuntu: New Bug description: ### Issue description When restarting my machine, cryptsetup waits forever. Waiting for the swapfile. Unable to start Ubuntu at all. Error message is: ``` cryptsetup: Waiting for encrypted source device /swapfile... ``` ### Steps for reproducing the issue 1. Do a fresh installation of Ubuntu, unencrypted. 2. Later, due to restrictions at work, encrypt Ubuntu POST installation accordingly to this article: https://jumpcloud.com/blog/how-to-encrypt-ubuntu-20-04-desktop-post-installation 3. Reboot, all works fine, but ... 4. Later, after a couple of months, install a new Linux kernel and then ... 5. Upon boot cryptsetup gets stuck, waits forever. See attached photo. ### Additional info I've found a temporary, painful workaround by rebooting in recovery mode and running this command every time: ``` sudo update-initramfs -u -k all ``` Then I can boot again. But I have to do this every time. Why? ### Debug log Hard to say but here'
[Touch-packages] [Bug 1757577] [NEW] Unclaimed AR5416 Wireless Network Adapter
Public bug reported: On my latest Ubuntu 17.10 I am unable to use my WiFi, only Ethernet. Didn't happen before I upgraded from 16.10. The `sudo lshw -C network` command tells me the AR5416 Wireless Network Adapter is UNCLAIMED: ``` └─❱❱❱ sudo lshw -C network *-network description: Ethernet interface product: 88E8056 PCI-E Gigabit Ethernet Controller vendor: Marvell Technology Group Ltd. physical id: 0 bus info: pci@:05:00.0 logical name: eth0 version: 12 serial: f4:6d:04:00:dc:74 size: 100Mbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm vpd msi pciexpress bus_master cap_list rom ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 duplex=full ip=192.168.2.10 latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s resources: irq:35 memory:fbdfc000-fbdf ioport:d800(size=256) memory:fbdc-fbdd *-network UNCLAIMED description: Network controller product: AR5416 Wireless Network Adapter [AR5008 802.11(a)bgn] vendor: Qualcomm Atheros physical id: 1 bus info: pci@:07:01.0 version: 01 width: 32 bits clock: 66MHz capabilities: cap_list configuration: latency=168 ``` Here few more useful info from other commands ``` └─❱❱❱ iwconfig lono wireless extensions. eth0 no wireless extensions. └─❱❱❱ lspci -vnn | grep Network 07:01.0 Network controller [0280]: Qualcomm Atheros AR5416 Wireless Network Adapter [AR5008 802.11(a)bgn] [168c:0023] (rev 01) Subsystem: Qualcomm Atheros AR5416 Wireless Network Adapter [AR5008 802.11(a)bgn] [168c:3071] ``` and yes, dmesg tells me initialisation of that device failed during startup: ``` └─❱❱❱ dmesg | grep ath ... [ 25.700597] ath: phy0: address test failed addr: 0x8000 - wr:0x != rd:0x0100 [ 25.758375] ath: phy0: Unable to initialize hardware; initialization status: -19 [ 25.814677] ath9k :07:01.0: Failed to initialize device [ .517258] ath9k: ath9k: Driver unloaded ``` Any clues what this could be? Any hints very much appreciated! Thanks guys ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1757577 Title: Unclaimed AR5416 Wireless Network Adapter Status in network-manager package in Ubuntu: New Bug description: On my latest Ubuntu 17.10 I am unable to use my WiFi, only Ethernet. Didn't happen before I upgraded from 16.10. The `sudo lshw -C network` command tells me the AR5416 Wireless Network Adapter is UNCLAIMED: ``` └─❱❱❱ sudo lshw -C network *-network description: Ethernet interface product: 88E8056 PCI-E Gigabit Ethernet Controller vendor: Marvell Technology Group Ltd. physical id: 0 bus info: pci@:05:00.0 logical name: eth0 version: 12 serial: f4:6d:04:00:dc:74 size: 100Mbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm vpd msi pciexpress bus_master cap_list rom ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 duplex=full ip=192.168.2.10 latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s resources: irq:35 memory:fbdfc000-fbdf ioport:d800(size=256) memory:fbdc-fbdd *-network UNCLAIMED description: Network controller product: AR5416 Wireless Network Adapter [AR5008 802.11(a)bgn] vendor: Qualcomm Atheros physical id: 1 bus info: pci@:07:01.0 version: 01 width: 32 bits clock: 66MHz capabilities: cap_list configuration: latency=168 ``` Here few more useful info from other commands ``` └─❱❱❱ iwconfig lono wireless extensions. eth0 no wireless extensions. └─❱❱❱ lspci -vnn | grep Network 07:01.0 Network controller [0280]: Qualcomm Atheros AR5416 Wireless Network Adapter [AR5008 802.11(a)bgn] [168c:0023] (rev 01) Subsystem: Qualcomm Atheros AR5416 Wireless Network Adapter [AR5008 802.11(a)bgn] [168c:3071] ``` and yes, dmesg tells me initialisation of that device failed during startup: ``` └─❱❱❱ dmesg | grep ath ... [ 25.700597] ath: phy0: address test failed addr: 0x8000 - wr:0x != rd:0x0100 [ 25.758375] ath: phy0: Unable to initialize hardware; initialization status: -19 [ 25.814677] ath9k :07:01.0: Failed to initialize device [ .517
[Touch-packages] [Bug 1504659] Re: Duplicate line for path "/var/log" warning is shown when rsyslog is installed
still happening on ubuntu 17 :( ... what's the official fix? -- 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/1504659 Title: Duplicate line for path "/var/log" warning is shown when rsyslog is installed Status in systemd package in Ubuntu: Opinion Bug description: On an snappy 15.04 stable system I see in the logs: systemd-tmpfiles[958]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Bug 1434295 mentions this, but reports that systemd fails to start. This bug is about preventing systemd from displaying this in the logs. Looking at the snappy system, I'm not sure why it is doing that: $ cat /usr/lib/tmpfiles.d/var.conf # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. # See tmpfiles.d(5) for details d /var 0755 - - - L /var/run - - - - ../run d /var/log 0755 - - - f /var/log/wtmp 0664 root utmp - f /var/log/btmp 0600 root utmp - d /var/cache 0755 - - - d /var/lib 0755 - - - v /var/lib/machines 0700 - - - d /var/spool 0755 - - - Perhaps this is a bug in systemd? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1504659/+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 1556713] Re: systemd-tmpfiles [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
*** This bug is a duplicate of bug 1484027 *** https://bugs.launchpad.net/bugs/1484027 Still happening here on Ubuntu 17 -- 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/1556713 Title: systemd-tmpfiles [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Status in systemd package in Ubuntu: New Bug description: In /var/log/syslog systemd-tmpfiles [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-2ubuntu1 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sun Mar 13 21:07:01 2016 InstallationDate: Installed on 2014-03-23 (721 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140318) MachineType: Dell Inc. Inspiron N7010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic root=UUID=9f1341c7-2522-4643-86be-b9c020215429 ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to xenial on 2016-03-03 (10 days ago) dmi.bios.date: 09/13/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 08VFX1 dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd09/13/2010:svnDellInc.:pnInspironN7010:pvrA07:rvnDellInc.:rn08VFX1:rvrA07:cvnDellInc.:ct8:cvrA07: dmi.product.name: Inspiron N7010 dmi.product.version: A07 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1556713/+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 1574897] [NEW] Upgrading to 16.04 disables Python3?
Public bug reported: Since I ran a do-release-upgrade last week from 15.10 to 16.04, starting Vim now produces this warning I haven't seen before: ~/D/abc ❯❯❯ vim develop ✭ You need vim compiled with Python 2.6, 2.7 or 3.2 and later support for Powerline to work. Please consult the documentation for more details. Press ENTER or type command to continue Then had a look at the included features of Vim: /e/alternatives ❯❯❯ vim --version VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Apr 08 2016 11:38:28) Included patches: 1-1689 Modified by pkg-vim-maintain...@lists.alioth.debian.org Compiled by pkg-vim-maintain...@lists.alioth.debian.org Huge version without GUI. Features included (+) or not (-): +acl +farsi +mouse_netterm +tag_binary +arabic +file_in_path+mouse_sgr +tag_old_static +autocmd +find_in_path-mouse_sysmouse -tag_any_white -balloon_eval+float +mouse_urxvt -tcl -browse +folding +mouse_xterm +terminfo ++builtin_terms -footer +multi_byte +termresponse +byte_offset +fork() +multi_lang +textobjects +channel +gettext -mzscheme+timers +cindent -hangul_input+netbeans_intg +title -clientserver+iconv +packages-toolbar -clipboard +insert_expand +path_extra +user_commands +cmdline_compl +job -perl+vertsplit +cmdline_hist+jumplist+persistent_undo +virtualedit +cmdline_info+keymap +postscript +visual +comments+langmap +printer +visualextra +conceal +libcall +profile +viminfo +cryptv +linebreak -python +vreplace +cscope +lispindent -python3 +wildignore +cursorbind +listcmds+quickfix+wildmenu +cursorshape +localmap+reltime +windows +dialog_con -lua +rightleft +writebackup +diff+menu-ruby-X11 +digraphs+mksession +scrollbind -xfontset -dnd +modify_fname+signs -xim -ebcdic +mouse +smartindent -xsmp +emacs_tags -mouseshape +startuptime -xterm_clipboard +eval+mouse_dec +statusline -xterm_save +ex_extra+mouse_gpm -sun_workshop-xpm +extra_search-mouse_jsbterm +syntax system vimrc file: "$VIM/vimrc" user vimrc file: "$HOME/.vimrc" 2nd user vimrc file: "~/.vim/vimrc" user exrc file: "$HOME/.exrc" fall-back for $VIM: "/usr/share/vim" Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -Wdate-time -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 Linking: gcc -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o vim-lm -ltinfo -lnsl -lselinux -lacl -lattr -lgpm -ldl I see, there is -python and -python3 But all news and documentation say the Vim in Xenial 16.04 comes with Python3 enabled. I am confused? A bug? ** Affects: vim (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1574897 Title: Upgrading to 16.04 disables Python3? Status in vim package in Ubuntu: New Bug description: Since I ran a do-release-upgrade last week from 15.10 to 16.04, starting Vim now produces this warning I haven't seen before: ~/D/abc ❯❯❯ vim develop ✭ You need vim compiled with Python 2.6, 2.7 or 3.2 and later support for Powerline to work. Please consult the documentation for more details. Press ENTER or type command to continue Then had a look at the included features of Vim: /e/alternatives ❯❯❯ vim --version VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Apr 08 2016 11:38:28) Included patches: 1-1689 Modified by pkg-vim-maintain...@lists.alioth.debian.org Compiled by pkg-vim-maintain...@lists.alioth.debian.org Huge version without GUI. Features included (+) or not (-): +acl +farsi +mouse_netterm +tag_binary +arabic +file_in_path+mouse_sgr +tag_old_static +autocmd +find_in_path-mouse_sysmouse -tag_any_white -balloon_eval+float +mouse_urxvt -tcl -browse +folding +mouse_xterm +terminfo ++builtin_terms -footer +multi_byte +termresponse +byte_offset +fork() +multi_lang +textobjects +channel +gettext -mzscheme+timers +cindent -hangul_input+netbeans_intg +title -clientserver+iconv +packag
[Touch-packages] [Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2
Can I apt-get upgrade this anytime soon instead? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1442050 Title: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 Status in colord package in Ubuntu: Confirmed Bug description: Get that error logged into journalctl (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Thu Apr 9 11:57:02 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1442050/+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 1510998] Re: Xorg crashes with segfault on 15.10
Had this issue five times today. Bad for my job :( -- 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/1510998 Title: Xorg crashes with segfault on 15.10 Status in xorg package in Ubuntu: Confirmed Bug description: I updated my system from 15.04 to 15.10 yesterday. Since then the X server has already crashed 5 times, which renders the system close to unusable for me. The corresponding messages in Xorg.0.log.old are: [ 12125.023] (EE) [ 12125.023] (EE) Backtrace: [ 12125.023] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55953d82762e] [ 12125.023] (EE) 1: /usr/bin/X (0x55953d673000+0x1b8999) [0x55953d82b999] [ 12125.023] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f7c10e7b000+0x352f0) [0x7f7c10eb02f0] [ 12125.023] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f7c0d252000+0x24edc) [0x7f7c0d276edc] [ 12125.023] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f7c0d252000+0x26157) [0x7f7c0d278157] [ 12125.023] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f7c0d252000+0x4a1e8) [0x7f7c0d29c1e8] [ 12125.023] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f7c0d252000+0x4a7ec) [0x7f7c0d29c7ec] [ 12125.023] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f7c0d252000+0x59103) [0x7f7c0d2ab103] [ 12125.023] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f7c0d252000+0x593aa) [0x7f7c0d2ab3aa] [ 12125.023] (EE) 9: /usr/bin/X (0x55953d673000+0x13fb73) [0x55953d7b2b73] [ 12125.023] (EE) 10: /usr/bin/X (0x55953d673000+0x54ce3) [0x55953d6c7ce3] [ 12125.023] (EE) 11: /usr/bin/X (0x55953d673000+0x5818f) [0x55953d6cb18f] [ 12125.023] (EE) 12: /usr/bin/X (0x55953d673000+0x5c34b) [0x55953d6cf34b] [ 12125.023] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7f7c10e9ba40] [ 12125.023] (EE) 14: /usr/bin/X (_start+0x29) [0x55953d6b96c9] [ 12125.023] (EE) [ 12125.023] (EE) Segmentation fault at address 0x7f7e141995e0 [ 12125.023] (EE) Fatal server error: [ 12125.023] (EE) Caught signal 11 (Segmentation fault). Server aborting I have attached the syslog file. The relevant messages for the three crashes from today can be found at: Oct 28 15:56:36 Oct 28 12:06:58 Oct 28 09:08:51 Unfortunately I have no clue how to reproduce the segfault. The last crash happened while I was reading some document and I did not push any button, moved the mouse or anything... ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Wed Oct 28 16:30:43 2015 DistUpgraded: 2015-10-27 11:46:32,614 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: kubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-31-generic, x86_64: installed bbswitch, 0.7, 4.2.0-16-generic, x86_64: installed nvidia-304, 304.128, 3.19.0-31-generic, x86_64: installed nvidia-304, 304.128, 4.2.0-16-generic, x86_64: installed vboxhost, 4.3.26, 3.19.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:091c] InstallationDate: Installed on 2015-01-20 (281 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) LightdmGreeterLog: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei oder Verzeichnis nicht gefunden QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon LightdmGreeterLogOld: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei oder Verzeichnis nicht gefunden QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon MachineType: Acer Aspire VN7-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=5ebd3c26-8bee-44ee-a832-0dbfb0ee72f4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to wily on 2015-10-27 (1 days ago) dmi.bios.date: 01/08/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.14 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-571G dmi.board.vendor: Acer dmi.board.version: V1.14 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.14 dmi.modal
[Touch-packages] [Bug 1488344] Re: dbus rejected send messages
great, thanks. about time! :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1488344 Title: dbus rejected send messages Status in GLib: Fix Released Status in accountsservice package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Triaged Bug description: Seeing these log entries in the syslog Aug 24 18:26:36 M1 dbus[783]: [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.5" (uid=0 pid=733 comm="/usr/lib/accountsservice/accounts-daemon ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.59" (uid=1000 pid=4326 comm="/usr/lib/x86_64-linux-gnu/indicator-messages/indic") Hope the attached info helps locating the issue? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dbus 1.8.12-1ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 Date: Tue Aug 25 18:30:51 2015 InstallationDate: Installed on 2014-10-31 (298 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1488344/+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 1524963] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1524963/+attachment/4532791/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1524963 Title: Could not grab port (tty/ttyS4): 'Cannot add port 'tty/ttyS4', unhandled serial type' Status in modemmanager package in Ubuntu: New Bug description: I see these warnings in the journalctl after every boot, on Ubuntu 15.10: ``` Dec 11 09:18:08 M2 ModemManager[816]: Could not grab port (tty/ttyS4): 'Cannot add port 'tty/ttyS4', unhandled serial type' Dec 11 09:18:08 M2 ModemManager[816]: Couldn't create modem for device at '/sys/devices/pci:00/:00:16.3': Failed to find primary AT port Dec 11 09:18:08 M2 ModemManager[816]: Modem couldn't be initialized: Couldn't check unlock status: SIM not inserted ``` Any clues what this could be and why modem can't be initialized? --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 InstallationDate: Installed on 2015-05-22 (202 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Package: modemmanager 1.4.10-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Tags: wily Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: Upgraded to wily on 2015-11-15 (24 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1524963/+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 1524963] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1524963/+attachment/4532789/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1524963 Title: Could not grab port (tty/ttyS4): 'Cannot add port 'tty/ttyS4', unhandled serial type' Status in modemmanager package in Ubuntu: New Bug description: I see these warnings in the journalctl after every boot, on Ubuntu 15.10: ``` Dec 11 09:18:08 M2 ModemManager[816]: Could not grab port (tty/ttyS4): 'Cannot add port 'tty/ttyS4', unhandled serial type' Dec 11 09:18:08 M2 ModemManager[816]: Couldn't create modem for device at '/sys/devices/pci:00/:00:16.3': Failed to find primary AT port Dec 11 09:18:08 M2 ModemManager[816]: Modem couldn't be initialized: Couldn't check unlock status: SIM not inserted ``` Any clues what this could be and why modem can't be initialized? --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 InstallationDate: Installed on 2015-05-22 (202 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Package: modemmanager 1.4.10-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Tags: wily Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: Upgraded to wily on 2015-11-15 (24 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1524963/+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 1524963] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1524963/+attachment/4532790/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1524963 Title: Could not grab port (tty/ttyS4): 'Cannot add port 'tty/ttyS4', unhandled serial type' Status in modemmanager package in Ubuntu: New Bug description: I see these warnings in the journalctl after every boot, on Ubuntu 15.10: ``` Dec 11 09:18:08 M2 ModemManager[816]: Could not grab port (tty/ttyS4): 'Cannot add port 'tty/ttyS4', unhandled serial type' Dec 11 09:18:08 M2 ModemManager[816]: Couldn't create modem for device at '/sys/devices/pci:00/:00:16.3': Failed to find primary AT port Dec 11 09:18:08 M2 ModemManager[816]: Modem couldn't be initialized: Couldn't check unlock status: SIM not inserted ``` Any clues what this could be and why modem can't be initialized? --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 InstallationDate: Installed on 2015-05-22 (202 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Package: modemmanager 1.4.10-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Tags: wily Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: Upgraded to wily on 2015-11-15 (24 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1524963/+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 1524963] [NEW] Could not grab port (tty/ttyS4): 'Cannot add port 'tty/ttyS4', unhandled serial type'
Public bug reported: I see these warnings in the journalctl after every boot, on Ubuntu 15.10: ``` Dec 11 09:18:08 M2 ModemManager[816]: Could not grab port (tty/ttyS4): 'Cannot add port 'tty/ttyS4', unhandled serial type' Dec 11 09:18:08 M2 ModemManager[816]: Couldn't create modem for device at '/sys/devices/pci:00/:00:16.3': Failed to find primary AT port Dec 11 09:18:08 M2 ModemManager[816]: Modem couldn't be initialized: Couldn't check unlock status: SIM not inserted ``` Any clues what this could be and why modem can't be initialized? --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 InstallationDate: Installed on 2015-05-22 (202 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Package: modemmanager 1.4.10-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Tags: wily Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: Upgraded to wily on 2015-11-15 (24 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected wily ** Tags added: apport-collected wily ** Description changed: I see these warnings in the journalctl after every boot, on Ubuntu 15.10: ``` Dec 11 09:18:08 M2 ModemManager[816]: Could not grab port (tty/ttyS4): 'Cannot add port 'tty/ttyS4', unhandled serial type' Dec 11 09:18:08 M2 ModemManager[816]: Couldn't create modem for device at '/sys/devices/pci:00/:00:16.3': Failed to find primary AT port Dec 11 09:18:08 M2 ModemManager[816]: Modem couldn't be initialized: Couldn't check unlock status: SIM not inserted ``` Any clues what this could be and why modem can't be initialized? + --- + ApportVersion: 2.19.1-0ubuntu5 + Architecture: amd64 + CurrentDesktop: Unity + DistroRelease: Ubuntu 15.10 + InstallationDate: Installed on 2015-05-22 (202 days ago) + InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) + Package: modemmanager 1.4.10-1ubuntu2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 + Tags: wily + Uname: Linux 4.2.0-19-generic x86_64 + UpgradeStatus: Upgraded to wily on 2015-11-15 (24 days ago) + UserGroups: adm cdrom dip docker 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 modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1524963 Title: Could not grab port (tty/ttyS4): 'Cannot add port 'tty/ttyS4', unhandled serial type' Status in modemmanager package in Ubuntu: New Bug description: I see these warnings in the journalctl after every boot, on Ubuntu 15.10: ``` Dec 11 09:18:08 M2 ModemManager[816]: Could not grab port (tty/ttyS4): 'Cannot add port 'tty/ttyS4', unhandled serial type' Dec 11 09:18:08 M2 ModemManager[816]: Couldn't create modem for device at '/sys/devices/pci:00/:00:16.3': Failed to find primary AT port Dec 11 09:18:08 M2 ModemManager[816]: Modem couldn't be initialized: Couldn't check unlock status: SIM not inserted ``` Any clues what this could be and why modem can't be initialized? --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 InstallationDate: Installed on 2015-05-22 (202 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Package: modemmanager 1.4.10-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Tags: wily Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: Upgraded to wily on 2015-11-15 (24 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1524963/+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 1369216] Re: gpu-manager: /etc/modprobe.d is not a file
Well, I am on Willy and do not have a Nvidia graphic card but still see the same error: Dec 01 09:20:52 M2 gpu-manager[892]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1369216 Title: gpu-manager: /etc/modprobe.d is not a file Status in upstart package in Ubuntu: Confirmed Bug description: Get these lines logged into gpu-manager.log, on that fresh stock installation /etc/modprobe.d is not a file update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2 Uname: Linux 3.16.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Sep 14 08:42:45 2014 ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.default.whoopsie: [modified] modified.conffile..etc.gdm.Init.Default: [modified] mtime.conffile..etc.default.whoopsie: 2014-08-29T19:12:47.435075 mtime.conffile..etc.gdm.Init.Default: 2014-09-07T17:01:23.246055 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1369216/+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 1488344] [NEW] dbus rejected send messages
Public bug reported: Seeing these log entries in the syslog Aug 24 18:26:36 M1 dbus[783]: [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.5" (uid=0 pid=733 comm="/usr/lib/accountsservice/accounts-daemon ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.59" (uid=1000 pid=4326 comm="/usr/lib/x86_64-linux-gnu/indicator-messages/indic") Hope the attached info helps locating the issue? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dbus 1.8.12-1ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 Date: Tue Aug 25 18:30:51 2015 InstallationDate: Installed on 2014-10-31 (298 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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/1488344 Title: dbus rejected send messages Status in dbus package in Ubuntu: New Bug description: Seeing these log entries in the syslog Aug 24 18:26:36 M1 dbus[783]: [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.5" (uid=0 pid=733 comm="/usr/lib/accountsservice/accounts-daemon ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.59" (uid=1000 pid=4326 comm="/usr/lib/x86_64-linux-gnu/indicator-messages/indic") Hope the attached info helps locating the issue? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dbus 1.8.12-1ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 Date: Tue Aug 25 18:30:51 2015 InstallationDate: Installed on 2014-10-31 (298 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1488344/+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 1488343] [NEW] colord failed to get session
Public bug reported: Seeing this in the syslog Aug 24 18:24:26 M1 colord[865]: (colord:865): Cd-WARNING **: failed to get session [pid 751]: Unknown error -2 Maybe the attached info helps locating the issue? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: colord 1.2.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 Date: Tue Aug 25 18:28:52 2015 InstallationDate: Installed on 2014-10-31 (298 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: colord UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: colord (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1488343 Title: colord failed to get session Status in colord package in Ubuntu: New Bug description: Seeing this in the syslog Aug 24 18:24:26 M1 colord[865]: (colord:865): Cd-WARNING **: failed to get session [pid 751]: Unknown error -2 Maybe the attached info helps locating the issue? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: colord 1.2.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 Date: Tue Aug 25 18:28:52 2015 InstallationDate: Installed on 2014-10-31 (298 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: colord UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1488343/+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 1488056] [NEW] Rejected send message, 10 matched rules; type="method_return", sender=":1.84"
Public bug reported: Seeing lots of those log entries. Here an example Aug 24 20:14:36 M1 NetworkManager[748]: [1440404076.494991] [dns-manager/nm-dns-dnsmasq.c:398] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name Aug 24 20:14:36 M1 dbus[792]: [system] Rejected send message, 10 matched rules; type="method_return", sender=":1.84" (uid=0 pid=3300 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.7" (uid=0 pid=748 comm="/usr/sbin/NetworkManager --no-daemon ") Attached info might help locating the issue. Thanks for any clues. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dnsmasq 2.72-3ubuntu0.1 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 Date: Mon Aug 24 23:08:37 2015 InstallationDate: Installed on 2014-10-31 (297 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dnsmasq (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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/1488056 Title: Rejected send message, 10 matched rules; type="method_return", sender=":1.84" Status in dnsmasq package in Ubuntu: New Bug description: Seeing lots of those log entries. Here an example Aug 24 20:14:36 M1 NetworkManager[748]: [1440404076.494991] [dns-manager/nm-dns-dnsmasq.c:398] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name Aug 24 20:14:36 M1 dbus[792]: [system] Rejected send message, 10 matched rules; type="method_return", sender=":1.84" (uid=0 pid=3300 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.7" (uid=0 pid=748 comm="/usr/sbin/NetworkManager --no-daemon ") Attached info might help locating the issue. Thanks for any clues. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dnsmasq 2.72-3ubuntu0.1 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 Date: Mon Aug 24 23:08:37 2015 InstallationDate: Installed on 2014-10-31 (297 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1488056/+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 1487983] Re: No rules and cannot mount USB
thanks heaps! somehow the command `sudo ubuntu-bug storage` brought back
the usb stick and it works now.
--
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/1487983
Title:
No rules and cannot mount USB
Status in systemd package in Ubuntu:
Invalid
Bug description:
After upgrading to vivid, I seem to have lost all udev rules and
cannot mount any USB sticks anymore.
All I have is this:
# michael-heuberger at M1 in /etc/udev/rules.d [19:12:41]
$ l
total 12K
drwxr-xr-x 2 root root 4.0K Oct 31 2014 .
drwxr-xr-x 4 root root 4.0K Aug 24 18:53 ..
-rw-r--r-- 1 root root 628 Oct 31 2014 70-persistent-net.rules
The contents of this one rules file is simple
$ cat 70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
# PCI device 0x11ab:0x4364 (sky2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="f4:6d:04:00:dc:74", ATTR{dev_id}=="0x0", ATTR{type}=="1",
KERNEL=="eth*", NAME="eth0"
# PCI device 0x168c:0x0023 (ath9k)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:25:86:d0:bc:17", ATTR{dev_id}=="0x0", ATTR{type}=="1",
KERNEL=="wlan*", NAME="wlan0"
But what else is missing?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1487983/+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 1487983] [NEW] No rules and cannot mount USB
Public bug reported:
After upgrading to vivid, I seem to have lost all udev rules and cannot
mount any USB sticks anymore.
All I have is this:
# michael-heuberger at M1 in /etc/udev/rules.d [19:12:41]
$ l
total 12K
drwxr-xr-x 2 root root 4.0K Oct 31 2014 .
drwxr-xr-x 4 root root 4.0K Aug 24 18:53 ..
-rw-r--r-- 1 root root 628 Oct 31 2014 70-persistent-net.rules
The contents of this one rules file is simple
$ cat 70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
# PCI device 0x11ab:0x4364 (sky2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="f4:6d:04:00:dc:74", ATTR{dev_id}=="0x0", ATTR{type}=="1",
KERNEL=="eth*", NAME="eth0"
# PCI device 0x168c:0x0023 (ath9k)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:25:86:d0:bc:17", ATTR{dev_id}=="0x0", ATTR{type}=="1",
KERNEL=="wlan*", NAME="wlan0"
But what else is missing?
** 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/1487983
Title:
No rules and cannot mount USB
Status in systemd package in Ubuntu:
New
Bug description:
After upgrading to vivid, I seem to have lost all udev rules and
cannot mount any USB sticks anymore.
All I have is this:
# michael-heuberger at M1 in /etc/udev/rules.d [19:12:41]
$ l
total 12K
drwxr-xr-x 2 root root 4.0K Oct 31 2014 .
drwxr-xr-x 4 root root 4.0K Aug 24 18:53 ..
-rw-r--r-- 1 root root 628 Oct 31 2014 70-persistent-net.rules
The contents of this one rules file is simple
$ cat 70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
# PCI device 0x11ab:0x4364 (sky2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="f4:6d:04:00:dc:74", ATTR{dev_id}=="0x0", ATTR{type}=="1",
KERNEL=="eth*", NAME="eth0"
# PCI device 0x168c:0x0023 (ath9k)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:25:86:d0:bc:17", ATTR{dev_id}=="0x0", ATTR{type}=="1",
KERNEL=="wlan*", NAME="wlan0"
But what else is missing?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1487983/+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 1486445] [NEW] Lots of zeitgeist errors
Public bug reported: $ cat /var/log/syslog shows me lots of zeitgeist-related errors. My system is behaving weird lately since the upgrade from Ubuntu 14.10 to 15.04 so I am guessing this might be related. Alright, here the relevant log entries: Aug 19 19:31:49 M1 org.gnome.zeitgeist.Engine[25838]: ** (zeitgeist-datahub:26262): WARNING **: zeitgeist-datahub.vala:212: Error during inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: interpretation, manifestation and actor are required ... Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** (zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: Desktop file for "file:///home/michael-heuberger/.config/sublime-text-3/Projects/seeflow_live.sublime-project" was not found, exec: sublime_text, mime_type: application/octet-stream Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** (zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: Desktop file for "file:///home/michael-heuberger/binarykitchen/code/videomail.io/etc/ssl-certs/local/fake.crt" was not found, exec: google-chrome-stable, mime_type: application/pkix-cert Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** (zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: Desktop file for "file:///home/michael-heuberger/binarykitchen/code/webcamjs/demos/flash.html" was not found, exec: google-chrome-stable, mime_type: application/x-extension-html ... Aug 19 20:34:30 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: ** (zeitgeist-fts:26260): WARNING **: Unable to get info on application://gnome-terminal-server.desktop Aug 19 20:37:47 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: message repeated 2 times: [ ** (zeitgeist-fts:26260): WARNING **: Unable to get info on application://gnome-terminal-server.desktop] ... Aug 19 20:38:52 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: ** (zeitgeist-fts:26260): WARNING **: Unable to get info on application://gnome-terminal-server.desktop Any clues how to fix all that? ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1486445 Title: Lots of zeitgeist errors Status in unity package in Ubuntu: New Bug description: $ cat /var/log/syslog shows me lots of zeitgeist-related errors. My system is behaving weird lately since the upgrade from Ubuntu 14.10 to 15.04 so I am guessing this might be related. Alright, here the relevant log entries: Aug 19 19:31:49 M1 org.gnome.zeitgeist.Engine[25838]: ** (zeitgeist-datahub:26262): WARNING **: zeitgeist-datahub.vala:212: Error during inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: interpretation, manifestation and actor are required ... Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** (zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: Desktop file for "file:///home/michael-heuberger/.config/sublime-text-3/Projects/seeflow_live.sublime-project" was not found, exec: sublime_text, mime_type: application/octet-stream Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** (zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: Desktop file for "file:///home/michael-heuberger/binarykitchen/code/videomail.io/etc/ssl-certs/local/fake.crt" was not found, exec: google-chrome-stable, mime_type: application/pkix-cert Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** (zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: Desktop file for "file:///home/michael-heuberger/binarykitchen/code/webcamjs/demos/flash.html" was not found, exec: google-chrome-stable, mime_type: application/x-extension-html ... Aug 19 20:34:30 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: ** (zeitgeist-fts:26260): WARNING **: Unable to get info on application://gnome-terminal-server.desktop Aug 19 20:37:47 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: message repeated 2 times: [ ** (zeitgeist-fts:26260): WARNING **: Unable to get info on application://gnome-terminal-server.desktop] ... Aug 19 20:38:52 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: ** (zeitgeist-fts:26260): WARNING **: Unable to get info on application://gnome-terminal-server.desktop Any clues how to fix all that? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1486445/+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 1466314] Re: boot hangs on missing swap partition
Hmmm, after a recent apt-get dist-upgrade this problem seems to be gone. Unable to reproduce this at the moment ... -- 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/1466314 Title: boot hangs on missing swap partition Status in systemd package in Ubuntu: Incomplete Bug description: With the recent kernel update for Ubuntu 15.04 the boot process takes so long. At this line I have to wait 1:30 min until it gets over with it: > UPDATE UTMP System Boot/Shutdown ... (progress bar here) How can we disable this? And why has the latest kernel introduced this? My system: $ uname -a Linux M2 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 18:31:11 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1466314/+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 1466314] Re: boot hangs on missing swap partition
$ grep -v '^#' /etc/fstab UUID=b2f035dd-f14c-4a64-8834-5116d2df7864 / ext4 errors=remount-ro 0 1 UUID=bb8b6759-8fdb-4e4b-879b-7701cb217d2a noneswapsw 0 0 -- 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/1466314 Title: boot hangs on missing swap partition Status in systemd package in Ubuntu: Incomplete Bug description: With the recent kernel update for Ubuntu 15.04 the boot process takes so long. At this line I have to wait 1:30 min until it gets over with it: > UPDATE UTMP System Boot/Shutdown ... (progress bar here) How can we disable this? And why has the latest kernel introduced this? My system: $ uname -a Linux M2 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 18:31:11 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1466314/+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 1466314] Re: boot hangs on missing swap partition
yes, looks like i have no working swap. but when i open the disk app, i see an active 8.2 GB swap partition on /dev/sda2 ... ?? -- 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/1466314 Title: boot hangs on missing swap partition Status in systemd package in Ubuntu: Incomplete Bug description: With the recent kernel update for Ubuntu 15.04 the boot process takes so long. At this line I have to wait 1:30 min until it gets over with it: > UPDATE UTMP System Boot/Shutdown ... (progress bar here) How can we disable this? And why has the latest kernel introduced this? My system: $ uname -a Linux M2 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 18:31:11 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1466314/+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 1466314] Re: boot hangs on missing swap partition
$ sudo blkid /dev/sda1: UUID="b2f035dd-f14c-4a64-8834-5116d2df7864" TYPE="ext4" PARTUUID="1173afaf-01" /dev/sda2: UUID="bb8b6759-8fdb-4e4b-879b-7701cb217d2a" TYPE="swap" PARTUUID="1173afaf-02" -- 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/1466314 Title: boot hangs on missing swap partition Status in systemd package in Ubuntu: Incomplete Bug description: With the recent kernel update for Ubuntu 15.04 the boot process takes so long. At this line I have to wait 1:30 min until it gets over with it: > UPDATE UTMP System Boot/Shutdown ... (progress bar here) How can we disable this? And why has the latest kernel introduced this? My system: $ uname -a Linux M2 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 18:31:11 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1466314/+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 1466314] Re: boot hangs on missing swap partition
$ ls -lR /dev/disk/by-uuid/ /dev/disk/by-uuid/: total 0 lrwxrwxrwx 1 root root 10 Jul 6 09:54 b2f035dd-f14c-4a64-8834-5116d2df7864 -> ../../sda1 lrwxrwxrwx 1 root root 10 Jul 6 09:54 bb8b6759-8fdb-4e4b-879b-7701cb217d2a -> ../../sda2 -- 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/1466314 Title: boot hangs on missing swap partition Status in systemd package in Ubuntu: Incomplete Bug description: With the recent kernel update for Ubuntu 15.04 the boot process takes so long. At this line I have to wait 1:30 min until it gets over with it: > UPDATE UTMP System Boot/Shutdown ... (progress bar here) How can we disable this? And why has the latest kernel introduced this? My system: $ uname -a Linux M2 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 18:31:11 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1466314/+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 1469922] [NEW] Rotated daily but has keyword weekly
Public bug reported:
I have this logroate config in /etc/logrotate.d which has the 'weekly'
keyword but I still get it every day. It's triggered via a daily cron
but still, I expect logrotate to be smart here:
/var/log/nginx/error.log
/var/log/nginx/production.videomail.io/error.log {
sharedscripts
create 0644 www-data adm
weekly
rotate 12
mail michael.heuber...@binarykitchen.com
notifempty
mailfirst
prerotate
if [ -d /etc/logrotate.d/httpd-prerotate ]; then \
run-parts /etc/logrotate.d/httpd-prerotate; \
fi \
endscript
postrotate
[ -s /run/nginx.pid ] && kill -USR1 `cat /run/nginx.pid`
endscript
}
Version info:
$ logrotate -v
logrotate 3.8.7 - Copyright (C) 1995-2001 Red Hat, Inc.
This may be freely redistributed under the terms of the GNU Public License
Let me know if it's a bug or if my above config is wrong.
Thanks!
** Affects: logrotate (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1469922
Title:
Rotated daily but has keyword weekly
Status in logrotate package in Ubuntu:
New
Bug description:
I have this logroate config in /etc/logrotate.d which has the 'weekly'
keyword but I still get it every day. It's triggered via a daily cron
but still, I expect logrotate to be smart here:
/var/log/nginx/error.log
/var/log/nginx/production.videomail.io/error.log {
sharedscripts
create 0644 www-data adm
weekly
rotate 12
mail michael.heuber...@binarykitchen.com
notifempty
mailfirst
prerotate
if [ -d /etc/logrotate.d/httpd-prerotate ]; then \
run-parts /etc/logrotate.d/httpd-prerotate; \
fi \
endscript
postrotate
[ -s /run/nginx.pid ] && kill -USR1 `cat /run/nginx.pid`
endscript
}
Version info:
$ logrotate -v
logrotate 3.8.7 - Copyright (C) 1995-2001 Red Hat, Inc.
This may be freely redistributed under the terms of the GNU Public License
Let me know if it's a bug or if my above config is wrong.
Thanks!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1469922/+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 1469892] [NEW] failed to get session
Public bug reported: I spotted this warning in my journal. What does it mean? A bug? Jun 30 09:07:31 M2 colord[799]: (colord:799): Cd-WARNING **: failed to get session [pid 750]: Unknown error -2 ** Affects: colord (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1469892 Title: failed to get session Status in colord package in Ubuntu: New Bug description: I spotted this warning in my journal. What does it mean? A bug? Jun 30 09:07:31 M2 colord[799]: (colord:799): Cd-WARNING **: failed to get session [pid 750]: Unknown error -2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1469892/+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 1466314] Re: UTMP Update makes booting 1:30min longer
@pitti I don't know how to add "systemd.log_level=debug" via command- line or grub-customzier2 - can you help? -- 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/1466314 Title: UTMP Update makes booting 1:30min longer Status in systemd package in Ubuntu: Incomplete Bug description: With the recent kernel update for Ubuntu 15.04 the boot process takes so long. At this line I have to wait 1:30 min until it gets over with it: > UPDATE UTMP System Boot/Shutdown ... (progress bar here) How can we disable this? And why has the latest kernel introduced this? My system: $ uname -a Linux M2 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 18:31:11 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1466314/+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 1469890] [NEW] Could not get the Network Manager state
Public bug reported: During boot my laptop behaves weird. Sometimes there are no network connection for the first 60 seconds after desktop is loaded. But on some days, they come quickly, connections are build before desktop is loaded. Had a look in the journal and found these lines interesting: Jun 30 09:07:31 M2 whoopsie[756]: [09:07:31] Could not get the Network Manager state: Jun 30 09:07:31 M2 whoopsie[756]: [09:07:31] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files Any clues? ** Affects: whoopsie (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1469890 Title: Could not get the Network Manager state Status in whoopsie package in Ubuntu: New Bug description: During boot my laptop behaves weird. Sometimes there are no network connection for the first 60 seconds after desktop is loaded. But on some days, they come quickly, connections are build before desktop is loaded. Had a look in the journal and found these lines interesting: Jun 30 09:07:31 M2 whoopsie[756]: [09:07:31] Could not get the Network Manager state: Jun 30 09:07:31 M2 whoopsie[756]: [09:07:31] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files Any clues? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1469890/+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 1466314] Re: UTMP Update makes booting 1:30min longer
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1466314/+attachment/4422093/+files/journal.txt -- 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/1466314 Title: UTMP Update makes booting 1:30min longer Status in systemd package in Ubuntu: Incomplete Bug description: With the recent kernel update for Ubuntu 15.04 the boot process takes so long. At this line I have to wait 1:30 min until it gets over with it: > UPDATE UTMP System Boot/Shutdown ... (progress bar here) How can we disable this? And why has the latest kernel introduced this? My system: $ uname -a Linux M2 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 18:31:11 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1466314/+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 1466314] Re: UTMP Update makes booting 1:30min longer
``` $ sudo systemctl status -l systemd-update-utmp.service develop ● systemd-update-utmp.service - Update UTMP about System Boot/Shutdown Loaded: loaded (/lib/systemd/system/systemd-update-utmp.service; static; vendor preset: enabled) Active: active (exited) since Tue 2015-06-30 09:06:02 NZST; 34min ago Docs: man:systemd-update-utmp.service(8) man:utmp(5) Main PID: 571 (code=exited, status=0/SUCCESS) CGroup: /system.slice/systemd-update-utmp.service Jun 30 09:06:02 M2 systemd[1]: Starting Update UTMP about System Boot/Shutdown... Jun 30 09:06:02 M2 systemd[1]: Started Update UTMP about System Boot/Shutdown. ``` -- 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/1466314 Title: UTMP Update makes booting 1:30min longer Status in systemd package in Ubuntu: Incomplete Bug description: With the recent kernel update for Ubuntu 15.04 the boot process takes so long. At this line I have to wait 1:30 min until it gets over with it: > UPDATE UTMP System Boot/Shutdown ... (progress bar here) How can we disable this? And why has the latest kernel introduced this? My system: $ uname -a Linux M2 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 18:31:11 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1466314/+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 1466314] Re: UTMP Update makes booting 1:30min longer
$ uname -a Linux M2 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 18:31:11 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ lscpu Architecture: x86_64 CPU op-mode(s):32-bit, 64-bit Byte Order:Little Endian CPU(s):4 On-line CPU(s) list: 0-3 Thread(s) per core:2 Core(s) per socket:2 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family:6 Model: 69 Model name:Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz Stepping: 1 CPU MHz: 3047.835 CPU max MHz: 3300. CPU min MHz: 800. BogoMIPS: 5387.47 Virtualisation:VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 4096K NUMA node0 CPU(s): 0-3 -- 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/1466314 Title: UTMP Update makes booting 1:30min longer Status in systemd package in Ubuntu: New Bug description: With the recent kernel update for Ubuntu 15.04 the boot process takes so long. At this line I have to wait 1:30 min until it gets over with it: > UPDATE UTMP System Boot/Shutdown ... (progress bar here) How can we disable this? And why has the latest kernel introduced this? My system: $ uname -a Linux M2 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 18:31:11 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1466314/+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 1466314] Re: UTMP Update makes booting 1:30min longer
$ systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @1min 39.801s └─multi-user.target @1min 39.801s └─virtualbox.service @1min 39.770s +30ms └─network-online.target @1min 39.769s └─network.target @1min 30.565s └─NetworkManager.service @1min 30.291s +269ms └─basic.target @1min 30.264s └─sockets.target @1min 30.263s └─dbus.socket @1min 30.262s └─sysinit.target @1min 30.235s └─systemd-update-utmp.service @1.914s +27ms └─systemd-tmpfiles-setup.service @1.842s +69ms └─systemd-journal-flush.service @1.805s +24ms └─systemd-remount-fs.service @1.799s +4ms └─systemd-fsck-root.service @1.785s +13ms └─systemd-fsckd.socket @153ms └─-.slice @91ms -- 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/1466314 Title: UTMP Update makes booting 1:30min longer Status in systemd package in Ubuntu: New Bug description: With the recent kernel update for Ubuntu 15.04 the boot process takes so long. At this line I have to wait 1:30 min until it gets over with it: > UPDATE UTMP System Boot/Shutdown ... (progress bar here) How can we disable this? And why has the latest kernel introduced this? My system: $ uname -a Linux M2 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 18:31:11 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1466314/+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 1466314] Re: UTMP Update makes booting 1:30min longer
Hello, any news? This is bugging me ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1466314 Title: UTMP Update makes booting 1:30min longer Status in systemd package in Ubuntu: New Bug description: With the recent kernel update for Ubuntu 15.04 the boot process takes so long. At this line I have to wait 1:30 min until it gets over with it: > UPDATE UTMP System Boot/Shutdown ... (progress bar here) How can we disable this? And why has the latest kernel introduced this? My system: $ uname -a Linux M2 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 18:31:11 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1466314/+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 1466314] [NEW] UTMP Update makes booting 1:30min longer
Public bug reported: With the recent kernel update for Ubuntu 15.04 the boot process takes so long. At this line I have to wait 1:30 min until it gets over with it: > UPDATE UTMP System Boot/Shutdown ... (progress bar here) How can we disable this? And why has the latest kernel introduced this? My system: $ uname -a Linux M2 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 18:31:11 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux ** 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/1466314 Title: UTMP Update makes booting 1:30min longer Status in systemd package in Ubuntu: New Bug description: With the recent kernel update for Ubuntu 15.04 the boot process takes so long. At this line I have to wait 1:30 min until it gets over with it: > UPDATE UTMP System Boot/Shutdown ... (progress bar here) How can we disable this? And why has the latest kernel introduced this? My system: $ uname -a Linux M2 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 18:31:11 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1466314/+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 1389201] Re: [keymap Microsoft Natural Ergonomic Keyboard 4000] Error calling EVIOCSKEYCODE on device node: Invalid argument
Thanks man! I didn't modify '/lib/udev/hwdb.d/60-keyboard.hwdb' yet but had a look at the 'dmesg' output and spotted, the warning is already gone. No idea why. Probably a recent apt-get upgrade already solved it. This ticket is quite old. But give me a couple of weeks to observe and confirm this 100%. By the way, I installed the evtest and tested the Zoom in/out keys. Nothing happens, no event is fired for these keys. Looks like these aren't mapped anymore. ** Changed in: systemd (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1389201 Title: [keymap Microsoft Natural Ergonomic Keyboard 4000] Error calling EVIOCSKEYCODE on device node: Invalid argument Status in systemd package in Ubuntu: Confirmed Bug description: In dmesg I can see these two error lines [7.375599] systemd-udevd[508]: Error calling EVIOCSKEYCODE on device node '/dev/input/event10' (scan code 0xc022d, key code 418): Invalid argument [7.375605] systemd-udevd[508]: Error calling EVIOCSKEYCODE on device node '/dev/input/event10' (scan code 0xc022e, key code 419): Invalid argument res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1 (device error) No idea what these two mean and how we can fix this. Any clues? ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-24-generic 3.16.0-24.32 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: michael-heuberger 2178 F pulseaudio /dev/snd/controlC2: michael-heuberger 2178 F pulseaudio /dev/snd/controlC0: michael-heuberger 2178 F pulseaudio CurrentDesktop: Unity Date: Wed Nov 5 00:55:34 2014 HibernationDevice: RESUME=UUID=b0b47183-895a-4f27-bb25-40bd23028028 InstallationDate: Installed on 2014-10-31 (4 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=b5b38333-3694-4441-8a13-50bf4dbf2f41 ro quiet RelatedPackageVersions: linux-restricted-modules-3.16.0-24-generic N/A linux-backports-modules-3.16.0-24-generic N/A linux-firmware 1.138 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6X58D-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd08/06/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6X58D-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1389201/+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 1359439] Re: [ 7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service
when will this be fixed??? -- 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/1359439 Title: [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service Status in systemd-shim package in Ubuntu: In Progress Status in systemd-shim package in Debian: New Bug description: [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service [7.287677] systemd-logind[1057]: Failed to start user service: Unknown unit: user@126.service [7.293871] systemd-logind[1057]: New session c1 of user lightdm. [7.293902] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/126/X11-display. [7.363706] ip_tables: (C) 2000-2006 Netfilter Core Team [7.421846] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [7.484529] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready [9.903052] wlan0: authenticate with c8:d7:19:22:21:ec [9.912429] wlan0: send auth to c8:d7:19:22:21:ec (try 1/3) [9.920181] wlan0: authenticated [9.924352] wlan0: associate with c8:d7:19:22:21:ec (try 1/3) [9.925709] wlan0: RX AssocResp from c8:d7:19:22:21:ec (capab=0x11 status=0 aid=2) [9.927753] wlan0: associated [9.927800] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 12.677104] systemd-logind[1057]: Failed to abandon scope session-c1.scope [ 12.677122] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc1_2escope [ 12.683902] systemd-logind[1057]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 12.683912] systemd-logind[1057]: Failed to start user service: Unknown unit: user@1000.service [ 12.685157] systemd-logind[1057]: New session c2 of user caravena. [ 12.685190] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. [ 234.494462] systemd-logind[1057]: Failed to abandon scope session-c2.scope [ 234.494478] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc2_2escope [ 235.514349] systemd-logind[1057]: New session c3 of user lightdm. [ 244.245908] systemd-logind[1057]: Failed to abandon scope session-c3.scope [ 244.245923] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc3_2escope ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd 208-7ubuntu4 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Aug 20 18:26:06 2014 InstallationDate: Installed on 2014-04-27 (115 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1359439/+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 1359439] Re: [ 7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service
The problem is still here, fix hasn't landed on my machine yet ... -- 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/1359439 Title: [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service Status in systemd-shim package in Ubuntu: In Progress Status in systemd-shim package in Debian: New Bug description: [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service [7.287677] systemd-logind[1057]: Failed to start user service: Unknown unit: user@126.service [7.293871] systemd-logind[1057]: New session c1 of user lightdm. [7.293902] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/126/X11-display. [7.363706] ip_tables: (C) 2000-2006 Netfilter Core Team [7.421846] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [7.484529] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready [9.903052] wlan0: authenticate with c8:d7:19:22:21:ec [9.912429] wlan0: send auth to c8:d7:19:22:21:ec (try 1/3) [9.920181] wlan0: authenticated [9.924352] wlan0: associate with c8:d7:19:22:21:ec (try 1/3) [9.925709] wlan0: RX AssocResp from c8:d7:19:22:21:ec (capab=0x11 status=0 aid=2) [9.927753] wlan0: associated [9.927800] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 12.677104] systemd-logind[1057]: Failed to abandon scope session-c1.scope [ 12.677122] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc1_2escope [ 12.683902] systemd-logind[1057]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 12.683912] systemd-logind[1057]: Failed to start user service: Unknown unit: user@1000.service [ 12.685157] systemd-logind[1057]: New session c2 of user caravena. [ 12.685190] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. [ 234.494462] systemd-logind[1057]: Failed to abandon scope session-c2.scope [ 234.494478] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc2_2escope [ 235.514349] systemd-logind[1057]: New session c3 of user lightdm. [ 244.245908] systemd-logind[1057]: Failed to abandon scope session-c3.scope [ 244.245923] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc3_2escope ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd 208-7ubuntu4 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Aug 20 18:26:06 2014 InstallationDate: Installed on 2014-04-27 (115 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1359439/+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 1389657] [NEW] Libpixman segfaults when searching
Public bug reported: [ 2810.133252] pool[8519]: segfault at bc ip 7f966bdabb71 sp 7f962bfed040 error 4 in libpixman-1.so.0.32.4[7f966bd55000+a3000] Compiz crashed and I saw the above line in the dmesg output. Happens EVERY time I pressed "d" on the ubuntu button for file search (dash, icon on top in the sidebar). Furthermore .xsession-errors has logged this as well: upstart: unity7 main process (1925) killed by SEGV signal upstart: unity7 main process ended, respawning Pretty serious I'd say ... ** Affects: pixman (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pixman in Ubuntu. https://bugs.launchpad.net/bugs/1389657 Title: Libpixman segfaults when searching Status in “pixman” package in Ubuntu: New Bug description: [ 2810.133252] pool[8519]: segfault at bc ip 7f966bdabb71 sp 7f962bfed040 error 4 in libpixman-1.so.0.32.4[7f966bd55000+a3000] Compiz crashed and I saw the above line in the dmesg output. Happens EVERY time I pressed "d" on the ubuntu button for file search (dash, icon on top in the sidebar). Furthermore .xsession-errors has logged this as well: upstart: unity7 main process (1925) killed by SEGV signal upstart: unity7 main process ended, respawning Pretty serious I'd say ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pixman/+bug/1389657/+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 1389201] Re: Error calling EVIOCSKEYCODE on device node: Invalid argument
Why incomplete? -- 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/1389201 Title: Error calling EVIOCSKEYCODE on device node: Invalid argument Status in “systemd” package in Ubuntu: Incomplete Bug description: In dmesg I can see these two error lines [7.375599] systemd-udevd[508]: Error calling EVIOCSKEYCODE on device node '/dev/input/event10' (scan code 0xc022d, key code 418): Invalid argument [7.375605] systemd-udevd[508]: Error calling EVIOCSKEYCODE on device node '/dev/input/event10' (scan code 0xc022e, key code 419): Invalid argument res 51/04:fe:00:00:00/00:00:00:00:00/40 Emask 0x1 (device error) No idea what these two mean and how we can fix this. Any clues? ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-24-generic 3.16.0-24.32 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michael-heuberger 2178 F pulseaudio /dev/snd/controlC2: michael-heuberger 2178 F pulseaudio /dev/snd/controlC0: michael-heuberger 2178 F pulseaudio CurrentDesktop: Unity Date: Wed Nov 5 00:55:34 2014 HibernationDevice: RESUME=UUID=b0b47183-895a-4f27-bb25-40bd23028028 InstallationDate: Installed on 2014-10-31 (4 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=b5b38333-3694-4441-8a13-50bf4dbf2f41 ro quiet RelatedPackageVersions: linux-restricted-modules-3.16.0-24-generic N/A linux-backports-modules-3.16.0-24-generic N/A linux-firmware 1.138 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6X58D-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd08/06/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6X58D-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1389201/+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 1359439] Re: [ 7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service
Just updated to Ubuntu 14.10 and got a similar error: [ 14.070781] systemd-logind[969]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 14.070789] systemd-logind[969]: Failed to start user service: Unknown unit: user@1000.service -- 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/1359439 Title: [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service Status in “systemd-shim” package in Ubuntu: Triaged Status in “systemd-shim” package in Debian: Incomplete Bug description: [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service [7.287677] systemd-logind[1057]: Failed to start user service: Unknown unit: user@126.service [7.293871] systemd-logind[1057]: New session c1 of user lightdm. [7.293902] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/126/X11-display. [7.363706] ip_tables: (C) 2000-2006 Netfilter Core Team [7.421846] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [7.484529] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready [9.903052] wlan0: authenticate with c8:d7:19:22:21:ec [9.912429] wlan0: send auth to c8:d7:19:22:21:ec (try 1/3) [9.920181] wlan0: authenticated [9.924352] wlan0: associate with c8:d7:19:22:21:ec (try 1/3) [9.925709] wlan0: RX AssocResp from c8:d7:19:22:21:ec (capab=0x11 status=0 aid=2) [9.927753] wlan0: associated [9.927800] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 12.677104] systemd-logind[1057]: Failed to abandon scope session-c1.scope [ 12.677122] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc1_2escope [ 12.683902] systemd-logind[1057]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 12.683912] systemd-logind[1057]: Failed to start user service: Unknown unit: user@1000.service [ 12.685157] systemd-logind[1057]: New session c2 of user caravena. [ 12.685190] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. [ 234.494462] systemd-logind[1057]: Failed to abandon scope session-c2.scope [ 234.494478] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc2_2escope [ 235.514349] systemd-logind[1057]: New session c3 of user lightdm. [ 244.245908] systemd-logind[1057]: Failed to abandon scope session-c3.scope [ 244.245923] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc3_2escope ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd 208-7ubuntu4 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Aug 20 18:26:06 2014 InstallationDate: Installed on 2014-04-27 (115 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1359439/+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 1302264] Re: systemd-logind assert failure: error.c:319: Assertion failed in nih_error_get: context_stack != NULL
Not sure if my problem is related to this one. At the moment I experience issues installing/updating libpam-systemd:amd64. Then I followed the installation scripts and saw that /sys/fs/cgroup/systemd is missing and I wasn't able to create that manually or using the script. Looks like /sys/fs/cgroup is missing. Sorry if this is off-topic but I am desperate to fix it. Here a log from sudo apt-get install libpam-systemd: ... Setting up libpam-systemd:amd64 (204-5ubuntu20.4) ... start: Job failed to start invoke-rc.d: initscript systemd-logind, action "start" failed. dpkg: error processing package libpam-systemd:amd64 (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: libpam-systemd:amd64 -- 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/1302264 Title: systemd-logind assert failure: error.c:319: Assertion failed in nih_error_get: context_stack != NULL Status in “systemd” package in Ubuntu: Fix Released Bug description: Initially presents as a 'hang' during bootup. Checking the upstart logs it looks like systemd-logind is failing. I tried a few different approaches - and eventually found that installing cgmanager allowed the system to reach a x11 login checking into the logs now I continue to see errors: Removed session c1. cgmanager: cgm_remove for controller=blkio, cgroup_path=user/115.user/c1.session, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=cpu, cgroup_path=user/115.user/c1.session, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=cpuacct, cgroup_path=user/115.user/c1.session, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=cpuset, cgroup_path=user/115.user/c1.session, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=devices, cgroup_path=user/115.user/c1.session, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=freezer, cgroup_path=user/115.user/c1.session, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=hugetlb, cgroup_path=user/115.user/c1.session, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=memory, cgroup_path=user/115.user/c1.session, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=perf_event, cgroup_path=user/115.user/c1.session, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=systemd, cgroup_path=user/115.user/c1.session, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=blkio, cgroup_path=user/115.user, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=cpu, cgroup_path=user/115.user, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=cpuacct, cgroup_path=user/115.user, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=cpuset, cgroup_path=user/115.user, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=devices, cgroup_path=user/115.user, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=freezer, cgroup_path=user/115.user, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=hugetlb, cgroup_path=user/115.user, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=memory, cgroup_path=user/115.user, recursive=1 failed: invalid request cgmanager: cgm_remove for controller=perf_event, cgroup_path=user/115.user, recursive=1 failed: invalid request Failed to issue method call: Unknown unit: autovt@tty2.service but the system seems to working now. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: systemd-services 204-5ubuntu16 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 AssertionMessage: error.c:319: Assertion failed in nih_error_get: context_stack != NULL Date: Thu Apr 3 18:18:23 2014 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2014-03-24 (10 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140323) ProcCmdline: /lib/systemd/systemd-logind ProcEnviron: PATH=(custom, no user) TERM=linux Signal: 6 SourcePackage: systemd StacktraceTop: nih_error_get () from /lib/x86_64-linux-gnu/libnih.so.1 ?? () ?? () ?? () ?? () Title: systemd-logind assert failure: error.c:319: Assertion failed in nih_error_get: context_stack != NULL UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1302264/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-pack
[Touch-packages] [Bug 1295521] Re: Installing i386 and amd64 PAM stacks causes shutdown/logout/etc. to break
Not sure if my problem is related to this one. At the moment I experience issues installing/updating libpam-systemd:amd64. Then I followed the installation scripts and saw that /sys/fs/cgroup/systemd is missing and I wasn't able to create that manually or using the script. Looks like /sys/fs/cgroup is missing. Sorry if this is off-topic but I am desperate to fix it. Here a log from sudo apt-get install libpam-systemd: ... Setting up libpam-systemd:amd64 (204-5ubuntu20.4) ... start: Job failed to start invoke-rc.d: initscript systemd-logind, action "start" failed. dpkg: error processing package libpam-systemd:amd64 (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: libpam-systemd:amd64 -- 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/1295521 Title: Installing i386 and amd64 PAM stacks causes shutdown/logout/etc. to break Status in Light Display Manager: Invalid Status in “systemd” package in Ubuntu: Incomplete Bug description: Hi, After I upgraded to Ubuntu Trusty, I've seen that it is no longer possible to suspend/shutdown/restart my system from the GUI. In other words within lightdm buttons to do so are grayed out, and within KDE it is the same. I had the same bug in Saucy beta and the culprit was the login component, and after its upgrade the issue was fixed. My system : Kubuntu 14.04 LTS AMD64 AMD Phenom 9850 8 GB RAM NVidia GeForce 660 Ti w/ NVidia 331 driver ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: login 1:4.1.5.1-1ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Fri Mar 21 07:21:52 2014 ProcEnviron: LANGUAGE=fr_FR TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: shadow UpgradeStatus: Upgraded to trusty on 2014-03-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1295521/+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 1325309] Re: User can't suspend laptop/control wireless via dbus/systemd-logind if cgroups are disabled in kernel
Not sure if my problem is related to this one. At the moment I experience issues installing/updating libpam-systemd:amd64. Then I followed the installation scripts and saw that /sys/fs/cgroup/systemd is missing and I wasn't able to create that manually or using the script. Looks like /sys/fs/cgroup is missing. Sorry if this is off-topic but I am desperate to fix it. -- 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/1325309 Title: User can't suspend laptop/control wireless via dbus/systemd-logind if cgroups are disabled in kernel Status in “systemd” package in Ubuntu: Invalid Bug description: This is kind of a long chain, but I think this is where it ends. I custom compile my kernel for battery savings, as I spend lots of time flying. I recently went back to BFS in 3.14 as my scheduler, but immediately ran into lots of problems (it used to give me 15 more minutes on average). The most interesting, that I can't work around is this: I disable cgroups because BFS doesn't use them at all. and when I did, even with the ubuntu linux-source package, I suddenly couldn't put my laptop to sleep, and I couldn't control my network connections anymore. Investigating lead me to discover that "start systemd-logind" was failing. So, here's my relevant config: rob@kubuntu4:~$ grep CGROUP /boot/config-`uname -r`; sudo start systemd-logind; dmesg |tail -1; ls /sys/fs/cgroup # CONFIG_CGROUPS is not set start: Job failed to start [ 1450.848491] init: systemd-logind pre-start process (10865) terminated with status 32 ls: cannot access /sys/fs/cgroup: No such file or directory the /sys/fs/cgroup folder doesn't exist because CONFIG_CGROUPS isn't set in the kernel. So what is "status 32" from the pre-script for systemd-logind ? the problem seems to be in the mount statements in the systemd-logind prestart script: grep mount /etc/init/systemd-logind.conf # this is being done by systemd or mountall usually, but not during if ! mountpoint -q /sys/fs/cgroup; then mount -t tmpfs -o uid=0,gid=0,mode=0755,size=1024 none /sys/fs/cgroup # mounting the cgroup does not work in LXC, there it uses cgmanager if [ ! -e /run/container_type ] && ! mountpoint -q /sys/fs/cgroup/systemd; then mount -t cgroup -o nosuid,noexec,nodev,none,name=systemd systemd /sys/fs/cgroup/systemd Testing: sudo mount -t tmpfs -o uid=0,gid=0,mode=0755,size=1024 none /sys/fs/cgroup; echo $? [sudo] password for rob: mount: mount point /sys/fs/cgroup does not exist 32 Rebooting into the stock ubuntu kernel, and I can put my laptop to sleep again, albeit at the cost of a bunch of battery life. I don't understand why cgroups are required for dbus and PolicyKit to be able to allow me to put my laptop to sleep, so I'm filing this as a bug. the systemd pre-script doesn't bother to check if the /sys/fs/cgroup folder even exists, so there's definitely a "defensive programming" bug in systemd not handling this situation better. currently "sudo pm_suspend" is an easy workaround for the sleep issue, but my wireless access issue has no workaround. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1325309/+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 1295909] Re: Unity spread trigger ruins windows and freezes desktop
I am having this problem too. Thanks for the workaround Hendrik but I would like to get the windows spread feature back (as soon as possible when this bug is fixed). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1295909 Title: Unity spread trigger ruins windows and freezes desktop Status in Compiz: Triaged Status in Unity: Confirmed Status in “compiz” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: The latest update disabled window spreading and when triggered crashes the desktop. Everything freezes and windows cannot be switched. The only way to close an application is to shut down. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140320.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 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 CurrentDesktop: Unity Date: Fri Mar 21 20:59:17 2014 DistUpgraded: 2014-03-19 22:45:03,298 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.8, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.8, 3.13.0-18-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fa20] InstallationDate: Installed on 2014-01-03 (77 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: TOSHIBA Satellite C55-A ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-18-generic root=UUID=6b37c83b-b64c-42fc-89d3-3db46a397734 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-20 (1 days ago) dmi.bios.date: 04/12/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.10 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.10:bd04/12/2013:svnTOSHIBA:pnSatelliteC55-A:pvrPSCF6U-01Y00C:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite C55-A dmi.product.version: PSCF6U-01Y00C dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.11+14.04.20140320.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 10.0.0-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Mar 21 18:56:33 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17223 vendor SDC xserver.version: 2:1.15.0-1ubuntu7 --- .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 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 CurrentDesktop: Unity DistUpgraded: 2014-03-19 22:45:03,298 DEBUG enabling apt cron job DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.8, 3.13.0-18-generic, x86_64: installed vboxhost, 4.3.8, 3.13.0-19-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fa20] InstallationDate: Installed on 2014-01-03 (83 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: TOSHIBA Satellite C55-A Package: unity PackageArchitecture: all ProcKernelCmdLine: B
[Touch-packages] [Bug 1325142] Re: failure to update libpam-systemd in 14.04 due to missing logind init script
I have this issue, not sure if it's related: Setting up libpam-systemd:amd64 (204-5ubuntu20.4) ... start: Job failed to start invoke-rc.d: initscript systemd-logind, action "start" failed. dpkg: error processing package libpam-systemd:amd64 (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: libpam-systemd:amd64 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1325142 Title: failure to update libpam-systemd in 14.04 due to missing logind init script Status in “systemd” package in Ubuntu: Fix Released Status in “systemd” source package in Trusty: Triaged Status in “systemd” source package in Utopic: Fix Released Bug description: Hi, while running inside an i386 lubuntu 14.04 chroot, upgrading libpam- systemd to version 204-5ubuntu20.2 fails leaving dpkg in a broken state. 'apt-get -f install' from within the chroot will not fix it, but if the build is made bootable and put into a iso/VM you can recover that way in a live session. the problem seems to be the /var/lib/dpkg/info/libpam-systemd:i386.prerm script failing to bring down the logind daemon with 'invoke-rc.d systemd-logind stop', because invoke-rd.d is only looking for the /etc/init.d/ script (doesn't exist) and not /etc/init/systemd-logind.conf (does exist). ? Reading package lists... Building dependency tree... Reading state information... The following packages will be upgraded: libpam-systemd 1 upgraded, 0 newly installed, 0 to remove and 113 not upgraded. 3 not fully installed or removed. Need to get 0 B/25.2 kB of archives. After this operation, 1024 B of additional disk space will be used. (Reading database ... 113986 files and directories currently installed.) Preparing to unpack .../libpam-systemd_204-5ubuntu20.2_i386.deb ... invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found. dpkg: warning: subprocess old pre-removal script returned error exit status 100 dpkg: trying script from the new package instead ... invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found. dpkg: error processing archive /var/cache/apt/archives/libpam-systemd_204-5ubuntu20.2_i386.deb (--unpack): subprocess new pre-removal script returned error exit status 100 invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found. dpkg: error while cleaning up: subprocess installed post-installation script returned error exit status 100 Errors were encountered while processing: /var/cache/apt/archives/libpam-systemd_204-5ubuntu20.2_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Our build logs available upon request, but the scripts to setup the chroot to recreate it are here: https://trac.osgeo.org/osgeo/browser/livedvd/gisvm/trunk/bin/build_chroot_nightly.sh https://trac.osgeo.org/osgeo/browser/livedvd/gisvm/trunk/bin/inchroot_nightly.sh In a web-search I notice a few others running into the same bug, chatter on irc at [18:10], http://irclogs.ubuntu.com/2013/05/28 /%23ubuntu-devel.txt someone else's build log: https://launchpad.net/~qutim/+archive/qutim/+build/6039800 launchpad bug #1323575 seems to be a duplicate of this one. perhaps related to older launchpad bug #1305395 ? note we are also suffering from a failure with update-initramfs, not sure of the root cause of that one but I thought I'd mention it in case they were related, since they both started happening about the same time, a couple weeks ago. (launchpad bug #1317602) It all worked ok after the inital releases of 14.04, so something to do with a package update since then. thanks, Hamish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1325142/+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 1308262] Re: libpam-systemd postinstall stuck on upgrade
I have this issue, not sure if it's related: Setting up libpam-systemd:amd64 (204-5ubuntu20.4) ... start: Job failed to start invoke-rc.d: initscript systemd-logind, action "start" failed. dpkg: error processing package libpam-systemd:amd64 (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: libpam-systemd:amd64 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1308262 Title: libpam-systemd postinstall stuck on upgrade Status in “systemd” package in Ubuntu: Fix Released Bug description: Just did an "apt-get update && apt-get dist-upgrade" on my trusty laptop. It's been stuck in the libpam-systemd postinst for 15-20 minutes: Recent output from dist-upgrade: Unpacking xpra (0.12.3+dfsg-1ubuntu1) over (0.12.2+dfsg-1ubuntu1) ... Processing triggers for man-db (2.6.7.1-1) ... Processing triggers for ureadahead (0.100.0-16) ... ureadahead will be reprofiled on next reboot Processing triggers for gnome-menus (3.10.1-0ubuntu2) ... Processing triggers for desktop-file-utils (0.22-1ubuntu1) ... Processing triggers for mime-support (3.54ubuntu1) ... Processing triggers for hicolor-icon-theme (0.13-1) ... Setting up libcgmanager0:i386 (0.24-0ubuntu5) ... Setting up libcgmanager0:amd64 (0.24-0ubuntu5) ... Setting up libudev1:amd64 (204-5ubuntu20) ... Setting up libudev1:i386 (204-5ubuntu20) ... Setting up udev (204-5ubuntu20) ... udev stop/waiting udev start/running, process 30898 Removing 'diversion of /bin/udevadm to /bin/udevadm.upgrade by fake-udev' update-initramfs: deferring update (trigger activated) Setting up libsystemd-daemon0:amd64 (204-5ubuntu20) ... Setting up systemd-services (204-5ubuntu20) ... Setting up libpam-systemd:amd64 (204-5ubuntu20) ... Installing new version of config file /etc/init/systemd-logind.conf ... [stuck here] Relevant processes running: | | | | |-bash---sudo---apt-get---dpkg ---libpam-systemd:---invoke-rc.d---start root 28517 17005 0 16:14 pts/26 00:00:00 sudo apt-get dist-upgrade root 28579 28517 3 16:14 pts/26 00:00:56 apt-get dist-upgrade root 30803 28579 0 16:15 pts/28 00:00:00 /usr/bin/dpkg --status-fd 69 --configure libcgmanager0:i386 libcgmanager0:amd64 libudev1:amd64 libudev1:i386 udev:amd64 libsystemd-daemon0:amd64 systemd-services:amd64 libpam-systemd:amd64 libsystemd-login0:amd64 chromium-codecs-ffmpeg-extra:amd64 chromium-browser:amd64 chromium-browser-l10n:all libgudev-1.0-0:amd64 cgmanager:amd64 liblxc1:amd64 python3-lxc:amd64 lxc:amd64 lxc-templates:amd64 libva1:amd64 libva-x11-1:amd64 libsystemd-journal0:amd64 ubuntu-minimal:amd64 gir1.2-gudev-1.0:amd64 libxenstore3.0:amd64 libxen-4.4:amd64 python-qt4:amd64 python-qt4-dbus:amd64 xpra:amd64 root 30928 30803 0 16:15 pts/28 00:00:00 /bin/sh /var/lib/dpkg/info/libpam-systemd:amd64.postinst configure 204-5ubuntu19 root 30942 30928 0 16:15 pts/28 00:00:00 /bin/sh /usr/sbin/invoke-rc.d systemd-logind start root 30984 30942 0 16:15 pts/28 00:00:00 start systemd-logind System info: Description:Ubuntu 14.04 LTS Release:14.04 libpam-systemd: Installed: 204-5ubuntu20 Candidate: 204-5ubuntu20 Version table: *** 204-5ubuntu20 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1308262/+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 1222356] Re: ** (apport-gtk:3020): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a r
I have this issue too. It occured when I ran the command `apport-collect 1353913`, see below: $ apport-collect 1353913 ** (apport-gtk:7970): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. dpkg-query: no packages found matching linux How can I fix this? -- 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/1222356 Title: ** (apport-gtk:3020): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Status in “apport” package in Ubuntu: Confirmed Bug description: The following warnings/errors appear after calling ubuntu-bug ** (apport-gtk:3020): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (process:4192): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: apport-gtk 2.12.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Sun Sep 8 10:54:01 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-09-01 (371 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MarkForUpload: True PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to saucy on 2013-09-05 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1222356/+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 1353907] [NEW] hda-codec: out of range cmd on Ubuntu 14
Public bug reported: In the `dmesg` output I see this: [ 18.722470] hda-codec: out of range cmd 2:5:707:ffbf No idea what caused this. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- 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/1353907 Title: hda-codec: out of range cmd on Ubuntu 14 Status in “alsa-driver” package in Ubuntu: New Bug description: In the `dmesg` output I see this: [ 18.722470] hda-codec: out of range cmd 2:5:707:ffbf No idea what caused this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1353907/+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 1345296] Re: Unable to load entry point in libxpathselect
Thanks so much guys, your comments help me a lot. Will follow that guide next time it's happening. By the way, I removed my old NVIDIA driver and installed a much newer one. Looks like my system is behaving much better now. There were no hints at all that my NVIDIA driver was outdated. You should add some notification in the OS to tell me to update the graphic drivers! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1345296 Title: Unable to load entry point in libxpathselect Status in Unity: In Progress Status in “unity” package in Ubuntu: Triaged Bug description: Hello When restarting unity I get this error message and it looks like it's related to lightdm. At the moment I cannot select my windows at all and can only use the command line :( ERROR 2014-07-20 13:19:20 unity.debug.interface DebugDBusInterface.cpp:216 Unable to load entry point in libxpathselect: libxpathselect.so.1.4: cannot open shared object file: No such file or directory I did a very recent apt-get update && apt-get upgrade with the latest Ubuntu 14 kernel/ To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1345296/+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 1345296] Re: Unable to load entry point in libxpathselect
I really have no idea. The compiz log is weird. And Unity, LightDM + Compiz all together behave weird sometimes. Diffcult to say. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1345296 Title: Unable to load entry point in libxpathselect Status in “unity” package in Ubuntu: New Bug description: Hello When restarting unity I get this error message and it looks like it's related to lightdm. At the moment I cannot select my windows at all and can only use the command line :( ERROR 2014-07-20 13:19:20 unity.debug.interface DebugDBusInterface.cpp:216 Unable to load entry point in libxpathselect: libxpathselect.so.1.4: cannot open shared object file: No such file or directory I did a very recent apt-get update && apt-get upgrade with the latest Ubuntu 14 kernel/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1345296/+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 1345296] Re: Unable to load entry point in libxpathselect
Here you go: # michael.heuberger at M1 in ~ [19:31:24] $ dpkg -l | grep libxpathselect # michael.heuberger at M1 in ~ [19:31:28] Looks like I didn't have one installed at all. So I installed it manually with `$ sudo apt-get install libxpathselect1.4` ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1345296 Title: Unable to load entry point in libxpathselect Status in “lightdm” package in Ubuntu: Incomplete Bug description: Hello When restarting unity I get this error message and it looks like it's related to lightdm. At the moment I cannot select my windows at all and can only use the command line :( ERROR 2014-07-20 13:19:20 unity.debug.interface DebugDBusInterface.cpp:216 Unable to load entry point in libxpathselect: libxpathselect.so.1.4: cannot open shared object file: No such file or directory I did a very recent apt-get update && apt-get upgrade with the latest Ubuntu 14 kernel/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1345296/+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 1345296] [NEW] Unable to load entry point in libxpathselect
Public bug reported: Hello When restarting unity I get this error message and it looks like it's related to lightdm. At the moment I cannot select my windows at all and can only use the command line :( ERROR 2014-07-20 13:19:20 unity.debug.interface DebugDBusInterface.cpp:216 Unable to load entry point in libxpathselect: libxpathselect.so.1.4: cannot open shared object file: No such file or directory I did a very recent apt-get update && apt-get upgrade with the latest Ubuntu 14 kernel/ ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1345296 Title: Unable to load entry point in libxpathselect Status in “lightdm” package in Ubuntu: New Bug description: Hello When restarting unity I get this error message and it looks like it's related to lightdm. At the moment I cannot select my windows at all and can only use the command line :( ERROR 2014-07-20 13:19:20 unity.debug.interface DebugDBusInterface.cpp:216 Unable to load entry point in libxpathselect: libxpathselect.so.1.4: cannot open shared object file: No such file or directory I did a very recent apt-get update && apt-get upgrade with the latest Ubuntu 14 kernel/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1345296/+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
