[Touch-packages] [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output
Also getting these messages (trying to find useful information in syslog due to other issues, found these messages spamming). NVme as well. uname -a Linux computer 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux #journalctl -m | grep ureadahead | wc -l 30244 After cold boot: #journalctl -b | grep ureadahead | wc -l 892 @Khurshid Alam Does a workaround exist for getting rid of this on 18.04? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1579580 Title: ureadahead reports relative path errors in journalctl output Status in ureadahead package in Ubuntu: Confirmed Bug description: ureadahead reports relative path errors in my journalctl output. This is currently 4368 lines of useless annoyances in my logs. To see if you have this problem, run: journalctl -b | grep ureadahead | grep relative | wc -l Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ureadahead 0.100.0-19 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun May 8 15:55:18 2016 InstallationDate: Installed on 2016-04-04 (34 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ureadahead UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output
Thanks, workaround in #19 seem to have removed (thousands of) these messages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1579580 Title: ureadahead reports relative path errors in journalctl output Status in ureadahead package in Ubuntu: Confirmed Bug description: ureadahead reports relative path errors in my journalctl output. This is currently 4368 lines of useless annoyances in my logs. To see if you have this problem, run: journalctl -b | grep ureadahead | grep relative | wc -l Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ureadahead 0.100.0-19 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun May 8 15:55:18 2016 InstallationDate: Installed on 2016-04-04 (34 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ureadahead UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1724919] Re: Bluetooth headphones only use A2DP when connected manually
Lots of errors etc in syslog, added some notes on top of the obvious errors. Kernel keeps spamming syslog with these (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748565): kernel: [15621.044566] Bluetooth: hci0: last event is not cmd complete (0x0f) Note: this kernel message disappears when and if i get a bluetooth connection that works with AD2P. If HSP/HFP is set instead this message spams the log. 1) Ubuntu control panel, events when enabling bluetooth: systemd[1]: Starting Load/Save RF Kill Switch Status... systemd[1]: Started Load/Save RF Kill Switch Status. kernel: [15952.121703] usb 1-7: new full-speed USB device number 16 using xhci_hcd kernel: [15952.271062] usb 1-7: New USB device found, idVendor=8087, idProduct=0a2b kernel: [15952.271069] usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0 kernel: [15952.274564] Bluetooth: hci0: Bootloader revision 0.0 build 26 week 38 2015 kernel: [15952.275558] Bluetooth: hci0: Device revision is 16 kernel: [15952.275563] Bluetooth: hci0: Secure boot is enabled kernel: [15952.275566] Bluetooth: hci0: OTP lock is enabled kernel: [15952.275569] Bluetooth: hci0: API lock is enabled kernel: [15952.275572] Bluetooth: hci0: Debug lock is disabled kernel: [15952.275576] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 kernel: [15952.276189] Bluetooth: hci0: Found device firmware: intel/ibt-12-16.sfi systemd[1]: Reached target Bluetooth. upowerd[1560]: unhandled action 'bind' on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.1 upowerd[1560]: unhandled action 'bind' on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0 upowerd[1560]: unhandled action 'bind' on /sys/devices/pci:00/:00:14.0/usb1/1-7 kernel: [15952.453260] [UFW BLOCK] IN=wlp4s0 OUT= MAC= SRC=fe80::::XXX DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=807886 PROTO=UDP SPT=8612 DPT=8612 LEN=24 kernel: [15952.453273] [UFW BLOCK] IN=wlp4s0 OUT= MAC= SRC=fe80::::XXX DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=273955 PROTO=UDP SPT=8612 DPT=8610 LEN=24 kernel: [15952.463425] [UFW BLOCK] IN=wlp4s0 OUT= MAC= SRC=fe80::::XXX DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=807886 PROTO=UDP SPT=8612 DPT=8612 LEN=24 kernel: [15952.463447] [UFW BLOCK] IN=wlp4s0 OUT= MAC= SRC=fe80::::XXX DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=273955 PROTO=UDP SPT=8612 DPT=8610 LEN=24 kernel: [15953.936818] Bluetooth: hci0: Waiting for firmware download to complete kernel: [15953.937485] Bluetooth: hci0: Firmware loaded in 1625036 usecs kernel: [15953.937530] Bluetooth: hci0: Waiting for device to boot kernel: [15953.949542] Bluetooth: hci0: Device booted in 11737 usecs kernel: [15953.949684] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-12-16.ddc kernel: [15953.960521] Bluetooth: hci0: Applying Intel DDC parameters completed bluetoothd[8656]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98) bluetoothd[8656]: RFCOMM server failed for :1.68/Profile/HSPHSProfile/1108--1000-8000-00805f9b34fb: rfcomm_bind: Address already in use (98) NetworkManager[1222]: [1536298184.5852] bluez5: NAP: added interface 00:28:F8:28:45:F5 bluetoothd[8656]: Endpoint registered: sender=:1.68 path=/MediaEndpoint/A2DPSource bluetoothd[8656]: Endpoint registered: sender=:1.68 path=/MediaEndpoint/A2DPSink bluetoothd[8656]: Endpoint registered: sender=:1.39 path=/MediaEndpoint/A2DPSource bluetoothd[8656]: Endpoint registered: sender=:1.39 path=/MediaEndpoint/A2DPSink NetworkManager[1222]: [1536298184.6229] keyfile: add connection in-memory NetworkManager[1222]: [1536298184.6244] bluez: BT device Samsung Galaxy S7 edge added (NAP) NetworkManager[1222]: [1536298184.6252] manager: new Bluetooth device (/org/freedesktop/NetworkManager/Devices/15) NetworkManager[1222]: [1536298184.6258] device state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') NetworkManager[1222]: [1536298184.6507] device state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed') kernel: [15959.948617] Bluetooth: hci0: last event is not cmd complete (0x0f) 2) Ubuntu control panel, events when enabling Jabra Elite device: gnome-shell[2235]: g_source_remove: assertion 'tag > 0' failed kernel: [16375.892576] Bluetooth: hci0: last event is not cmd complete (0x0f) kernel: [16391.773520] Bluetooth: hci0: last event is not cmd complete (0x0f) bluetoothd[8656]: Unable to connect Headset Voice gateway: connect: Device or resource busy (16) bluetoothd[8656]: Connecting Headset Voice gateway failed: Input/output error obexd[2645]: CONNECT(0x0), (0xff) obexd[2645]: CONNECT(0x0), (0x0) obexd[2645]: SETPATH(0x5), (0xff) obexd[2645]: stat(/home/nn/phonebook/): No such file or directory
[Touch-packages] [Bug 1724919] Re: Bluetooth headphones only use A2DP when connected manually
Ubuntu 18.04.1. Jabra Elite Sport v2. Impossible to get A2DP to stick. Have to go through multiple jumps to get it to work. E.g., 1) Shut down and start bluetooth a few times after suspend or reboot. Sometimes i try to shutdown the Jabra device as well. 2) Then connect to the device, which always fails at minimum 3 times when using the slider for connecting, and then it might add a sound device or not. It takes a long time for this to happen in any situation after successful connect. Often the sound device is not even selected if it is added, which require a second user interaction to solve. However, this step works much better using blueman. I.e., the interface and bluetooth solution in Ubuntu is buggy to say the least. At least a few bugs must exist in the interface solution considered blueman works better. 3) If connection is working and a sound device is added then the A2DP is never selected. Using the Ubuntu drop down menu to change to A2DP is pointless, it will never work, and blueman cant change profile either. Thus going back to step one and and trying again is the only solution. This process takes up to 15 minutes or more to complete. By pure luck, the A2DP setting will stick until next suspend These errors have existed for at least 12 months in my case. -- 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/1724919 Title: Bluetooth headphones only use A2DP when connected manually Status in alsa-driver package in Ubuntu: Confirmed Bug description: Issue with Sony MDR-1ABT Bluetooth headphones: Once paired, the headphones will be connected automatically whenever they are switched on. However when connected this way, only the HSP/HFP profile will work and trying to change to A2DP in sound settings does nothing. If the headphones are then manually disconnected and reconnected from Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in sound settings will successfully make them use A2DP. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: neil 1443 F pulseaudio /dev/snd/pcmC0D0c: neil 1443 F...m pulseaudio /dev/snd/controlC0: neil 1443 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 19:12:59 2017 InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: MDR-1ABT Symptom_Type: None of the above Title: [MDR-1ABT, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: Z270N-WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z270N-WIFI dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1724919/+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 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm
Sorry, small adjustment. I use wayland as default since 17.10 with gdm (works well in general for me): loginctl show-session c1 -p Type Type=wayland -- 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/1715435 Title: Can't lock screen with keyboard shortcuts when using lightdm Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen. Additionally, if I wait a very long time the screen does not lock either. Switching from LightDM to GDM3 fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 6 09:17:35 2017 DisplayManager: lightdm InstallationDate: Installed on 2016-01-22 (592 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715435/+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 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm
Confirm (Super - L) not working on Ubuntu 18.04, switching keyboard language does not work either most of the time (Super + Space). Those I use the most. Extremely annoying after some time, especially when using dual screens (since the Gnome top bar is only on one monitor which is even more annoying: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1682542). Worked fine in Ubuntu 17.10 with Gnome and previous versions with Unity. -- 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/1715435 Title: Can't lock screen with keyboard shortcuts when using lightdm Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen. Additionally, if I wait a very long time the screen does not lock either. Switching from LightDM to GDM3 fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 6 09:17:35 2017 DisplayManager: lightdm InstallationDate: Installed on 2016-01-22 (592 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715435/+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 774071] Re: Indicator-datetime-service renders 100% CPU usage
The problem went away in 17.10. Cheers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/774071 Title: Indicator-datetime-service renders 100% CPU usage Status in Indicator Date and Time: Fix Released Status in Unity Foundations: Fix Released Status in indicator-datetime package in Ubuntu: Fix Released Bug description: Binary package hint: indicator-datetime On my laptop "indicator-datetime-service" occasionally make my CPU to use 100% of its resources. It does not happen every time I log in to Ubuntu, but when it happens, it stays hogging 100% of CPU until I kill the process. If it helps, I've noticed in "System Monitor" that there are two instances of "indicator-datetime-service" running, but only one of them is hogging recourses. So far I was unable to determine after what actions/events this bug pups up. I'm using Ubuntu 11.04 64-bit. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: indicator-datetime 0.2.3-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sat Apr 30 15:27:58 2011 ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) SourcePackage: indicator-datetime UpgradeStatus: Upgraded to natty on 2011-04-28 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/774071/+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 1731939] Re: Indicator-datetime-service renders 25% CPU usage and 100% RAM
*** This bug is a duplicate of bug 774071 *** https://bugs.launchpad.net/bugs/774071 The problem went away in 17.10. Cheers. ** This bug has been marked a duplicate of bug 774071 Indicator-datetime-service renders 100% CPU usage -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1731939 Title: Indicator-datetime-service renders 25% CPU usage and 100% RAM Status in indicator-datetime package in Ubuntu: New Bug description: Same as Bug #774071 but with 100% RAM instead. Collected info while the Indicator-datetime-service was acting up. I.e., writing this with a few hundred megabytes RAM available.. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: indicator-datetime 15.10+17.04.20170322-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Mon Nov 13 15:41:39 2017 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service InstallationDate: Installed on 2015-07-18 (848 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: indicator-datetime UpgradeStatus: Upgraded to zesty on 2017-06-13 (153 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1731939/+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 774071] Re: Indicator-datetime-service renders 100% CPU usage
Last work-around didn't stick. Don't think this bug or #1731939 is about indicator-datetime-service. It seems to be evolution calendar that is the problem. See comment below: https://bugs.launchpad.net/ubuntu/+source/indicator- datetime/+bug/1731939/comments/4 Will test 17.10 now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/774071 Title: Indicator-datetime-service renders 100% CPU usage Status in Indicator Date and Time: Fix Released Status in Unity Foundations: Fix Released Status in indicator-datetime package in Ubuntu: Fix Released Bug description: Binary package hint: indicator-datetime On my laptop "indicator-datetime-service" occasionally make my CPU to use 100% of its resources. It does not happen every time I log in to Ubuntu, but when it happens, it stays hogging 100% of CPU until I kill the process. If it helps, I've noticed in "System Monitor" that there are two instances of "indicator-datetime-service" running, but only one of them is hogging recourses. So far I was unable to determine after what actions/events this bug pups up. I'm using Ubuntu 11.04 64-bit. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: indicator-datetime 0.2.3-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sat Apr 30 15:27:58 2011 ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) SourcePackage: indicator-datetime UpgradeStatus: Upgraded to natty on 2011-04-28 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/774071/+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 1731939] Re: Indicator-datetime-service renders 25% CPU usage and 100% RAM
Last work-around didn't stick. Did some test and can reproduce the error now easily in 17.04. Ubuntu reports it is the Indicator-datetime-service that crashes when its the evolution calendar that is the problem. During the system overload the problem can be fixed by killing all evolution processes and sub-processes indirectly. Evolution is overloading the Indicator-datetime-service somehow with lots of (factory?) sub-processes. Attached screenshot of the processes active during the error. Resolved by killing the evolution processes in the screenshot. Also, this problem started after enabling Empathy on boot. However, after disabling Empathy completely at startup the problem persisted. Will update to 17.10 (KVM bug fixed) and see if the error is unresolved. ** Attachment added: "htop screenshot sorted by mem usage" https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1731939/+attachment/5010707/+files/Screenshot%20from%202017-11-17%2022-45-57.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1731939 Title: Indicator-datetime-service renders 25% CPU usage and 100% RAM Status in indicator-datetime package in Ubuntu: New Bug description: Same as Bug #774071 but with 100% RAM instead. Collected info while the Indicator-datetime-service was acting up. I.e., writing this with a few hundred megabytes RAM available.. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: indicator-datetime 15.10+17.04.20170322-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Mon Nov 13 15:41:39 2017 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service InstallationDate: Installed on 2015-07-18 (848 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: indicator-datetime UpgradeStatus: Upgraded to zesty on 2017-06-13 (153 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1731939/+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 774071] Re: Indicator-datetime-service renders 100% CPU usage
(#51 was a mistake) Sorry, wrote incorrect. Reported for 17.04 LTS above. Work-around (I cant upgrade to 17.10 due to KVM bug): Turn of the "Show a clock in the menu bar" in System Settings for Time & Date. Worked after cold reboot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/774071 Title: Indicator-datetime-service renders 100% CPU usage Status in Indicator Date and Time: Fix Released Status in Unity Foundations: Fix Released Status in indicator-datetime package in Ubuntu: Fix Released Bug description: Binary package hint: indicator-datetime On my laptop "indicator-datetime-service" occasionally make my CPU to use 100% of its resources. It does not happen every time I log in to Ubuntu, but when it happens, it stays hogging 100% of CPU until I kill the process. If it helps, I've noticed in "System Monitor" that there are two instances of "indicator-datetime-service" running, but only one of them is hogging recourses. So far I was unable to determine after what actions/events this bug pups up. I'm using Ubuntu 11.04 64-bit. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: indicator-datetime 0.2.3-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sat Apr 30 15:27:58 2011 ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) SourcePackage: indicator-datetime UpgradeStatus: Upgraded to natty on 2011-04-28 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/774071/+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 774071] Re: Indicator-datetime-service renders 100% CPU usage
Sorry, wrote incorrect. Reported for 17.04 LTS above. Work-around (I cant upgrade to 17.10 due to KVM bug): Turn of the t -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/774071 Title: Indicator-datetime-service renders 100% CPU usage Status in Indicator Date and Time: Fix Released Status in Unity Foundations: Fix Released Status in indicator-datetime package in Ubuntu: Fix Released Bug description: Binary package hint: indicator-datetime On my laptop "indicator-datetime-service" occasionally make my CPU to use 100% of its resources. It does not happen every time I log in to Ubuntu, but when it happens, it stays hogging 100% of CPU until I kill the process. If it helps, I've noticed in "System Monitor" that there are two instances of "indicator-datetime-service" running, but only one of them is hogging recourses. So far I was unable to determine after what actions/events this bug pups up. I'm using Ubuntu 11.04 64-bit. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: indicator-datetime 0.2.3-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sat Apr 30 15:27:58 2011 ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) SourcePackage: indicator-datetime UpgradeStatus: Upgraded to natty on 2011-04-28 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/774071/+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 1731939] Re: Indicator-datetime-service renders 25% CPU usage and 100% RAM
Work-around (I cant upgrade to 17.10 due to KVM bug): Turn of the "Show a clock in the menu bar" in System Settings for Time & Date. Worked after cold reboot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1731939 Title: Indicator-datetime-service renders 25% CPU usage and 100% RAM Status in indicator-datetime package in Ubuntu: New Bug description: Same as Bug #774071 but with 100% RAM instead. Collected info while the Indicator-datetime-service was acting up. I.e., writing this with a few hundred megabytes RAM available.. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: indicator-datetime 15.10+17.04.20170322-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Mon Nov 13 15:41:39 2017 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service InstallationDate: Installed on 2015-07-18 (848 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: indicator-datetime UpgradeStatus: Upgraded to zesty on 2017-06-13 (153 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1731939/+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 774071] Re: Indicator-datetime-service renders 100% CPU usage
Seeing this on 17.10 as well. Battery indicator says ("estimating,
100%) and indicator-datetime-service uses between 2.4 GiB and (mostly)
~14.5 GiB RAM. CPU usage stays at 25% all the time. The indicator-
datetime-service crashes after reaching all available RAM, then restarts
with new PID.
I reported, with debug info, about the relevant PID in Bug #1731939
(apport-collect didnt work during the bug event).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/774071
Title:
Indicator-datetime-service renders 100% CPU usage
Status in Indicator Date and Time:
Fix Released
Status in Unity Foundations:
Fix Released
Status in indicator-datetime package in Ubuntu:
Fix Released
Bug description:
Binary package hint: indicator-datetime
On my laptop "indicator-datetime-service" occasionally make my CPU to
use 100% of its resources. It does not happen every time I log in to
Ubuntu, but when it happens, it stays hogging 100% of CPU until I kill
the process. If it helps, I've noticed in "System Monitor" that there
are two instances of "indicator-datetime-service" running, but only
one of them is hogging recourses. So far I was unable to determine
after what actions/events this bug pups up.
I'm using Ubuntu 11.04 64-bit.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: indicator-datetime 0.2.3-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sat Apr 30 15:27:58 2011
ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
SourcePackage: indicator-datetime
UpgradeStatus: Upgraded to natty on 2011-04-28 (1 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/774071/+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 1731939] [NEW] Indicator-datetime-service renders 25% CPU usage and 100% RAM
Public bug reported: Same as Bug #774071 but with 100% RAM instead. Collected info while the Indicator-datetime-service was acting up. I.e., writing this with a few hundred megabytes RAM available.. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: indicator-datetime 15.10+17.04.20170322-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Mon Nov 13 15:41:39 2017 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service InstallationDate: Installed on 2015-07-18 (848 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: indicator-datetime UpgradeStatus: Upgraded to zesty on 2017-06-13 (153 days ago) ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1731939 Title: Indicator-datetime-service renders 25% CPU usage and 100% RAM Status in indicator-datetime package in Ubuntu: New Bug description: Same as Bug #774071 but with 100% RAM instead. Collected info while the Indicator-datetime-service was acting up. I.e., writing this with a few hundred megabytes RAM available.. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: indicator-datetime 15.10+17.04.20170322-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Mon Nov 13 15:41:39 2017 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service InstallationDate: Installed on 2015-07-18 (848 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: indicator-datetime UpgradeStatus: Upgraded to zesty on 2017-06-13 (153 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1731939/+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 1731939] Re: Indicator-datetime-service renders 25% CPU usage and 100% RAM
PID changes after crash when RAM is depleted. Sceenshoot of RAM usage attached. ** Attachment added: "Exampel of memory usage" https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1731939/+attachment/5008303/+files/Screenshot%20from%202017-11-13%2015-29-41.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1731939 Title: Indicator-datetime-service renders 25% CPU usage and 100% RAM Status in indicator-datetime package in Ubuntu: New Bug description: Same as Bug #774071 but with 100% RAM instead. Collected info while the Indicator-datetime-service was acting up. I.e., writing this with a few hundred megabytes RAM available.. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: indicator-datetime 15.10+17.04.20170322-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Mon Nov 13 15:41:39 2017 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service InstallationDate: Installed on 2015-07-18 (848 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: indicator-datetime UpgradeStatus: Upgraded to zesty on 2017-06-13 (153 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1731939/+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 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
This hits me constantly. Why is this bug present years on end and three major Ubuntu versions? The workaround is easy enough, still for many users it is rocket science and will break the update procedure (I two other persons that cant fix it themselves). I.e, thus is a critical problem. Make a test in the installation procedure and remove the oldest unused kernel, if disk space is low, before installing the new version. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space Status in initramfs-tools: Confirmed Status in initramfs-tools package in Ubuntu: In Progress Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 WORKAROUND: Remove unused kernels using computer janitor (not in repositories for 14.04 or later) or manually free space on your partition containing the /boot file system. See instructions here https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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 1542733] Re: Connect to Hidden Wi-Fi Network, "Connect" grayed out
Got this in 16.04 today, fully updated. Has happened in older releases as well. -- 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/1542733 Title: Connect to Hidden Wi-Fi Network, "Connect" grayed out Status in network-manager package in Ubuntu: Confirmed Bug description: Reproduce: 1. Create a static, connection to hidden Wi-Fi connection using nm-connection-editor 2. click nm-applet icon click "Connect to Hidden Wi-Fi Network" click pre-existing connection "Connect" is grayed out Work around is using terminal. nmcli c up id ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.0.4-0ubuntu9 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Feb 6 15:58:22 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-02-06 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160206) IpRoute: default via 192.168.0.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.55 metric 600 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 7c22db8e-2026-413b-86cd-0c796f177dd5 802-3-ethernet 1454790964 Sat 06 Feb 2016 02:36:04 PM CST yes 0 no/org/freedesktop/NetworkManager/Settings/1 no -- -- -- jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A d57103a5-d3d7-4fb0-a2a0-469894e184ab 802-11-wireless 1454795858 Sat 06 Feb 2016 03:57:38 PM CST yes 0 no/org/freedesktop/NetworkManager/Settings/0 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/4 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/1 jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A d57103a5-d3d7-4fb0-a2a0-469894e184ab /org/freedesktop/NetworkManager/ActiveConnection/4 enp1s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1542733/+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] Re: Lots of zeitgeist errors
Also getting lots of these (new installation). Sep 14 21:20:14 boll org.gnome.zeitgeist.Engine[1592]: message repeated 3 times: [ ** (zeitgeist-datahub:2095): WARNING **: zeitgeist-datahub.vala:212: Error during inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: interpretation, manifestation and actor are required] Sep 14 21:28:58 boll com.canonical.Unity.Scope.Music[1592]: (unity-music-daemon:9903): unity-music-daemon-WARNING **: rhythmbox-collection.vala:510: Unable to open album-art DB! Sep 14 21:28:58 boll com.canonical.Unity.Scope.Music[1592]: (unity-music-daemon:9903): unity-music-daemon-WARNING **: rhythmbox-collection.vala:574: Error while parsing rhythmbox DB: Error opening file: No such file or directory uname -a Linux boll 3.19.0-28-generic #30-Ubuntu SMP Mon Aug 31 15:52:51 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1486445 Title: Lots of zeitgeist errors Status in Unity: New Status in unity package in Ubuntu: Confirmed 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/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 1323772] Re: Unattended apt-get dist-upgrade -qq --force-yes on 14.04 fails on grub configuration.
*** This bug is a duplicate of bug 1485685 *** https://bugs.launchpad.net/bugs/1485685 That makes no sense since the workaround in this thread is useful for those searching for a solution to the problem (this year) and your description appears to be the duplicate since it was filed later :-) Secondly, this bug indicates that this is an bug with ties to older bugs, which can perhaps be of use. I.e., why is the bug not addressed properly, which is another issue to resolve. 11 people (at least) are affected as well which can give input instead of six. I have deployed the workaround during several Ubuntu releases. It still works! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1323772 Title: Unattended apt-get dist-upgrade -qq --force-yes on 14.04 fails on grub configuration. Status in apt package in Ubuntu: Confirmed Bug description: Unattended apt-get dist-upgrade -qq --force-yes on 14.04 fails on Grub configuration. Reproduce by using apt-get dist-upgrade -qq --force-yes on the latest Ubuntu 14.04 image (https://cloud- images.ubuntu.com/locator/ec2/). It will not select grub defaults (install the package maintainer's version) during upgrade. Setup will prompt the user for input. This is a new behavior (for me, since Ubuntu 6). It breaks automatic/scripted setup of servers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1323772/+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 1453912] Re: systemd does not unlock dm-crypt password
Don't think i can verify this on the other computer as stated. It seems to be a different problem. -- 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/1453912 Title: systemd does not unlock dm-crypt password Status in systemd package in Ubuntu: Incomplete Bug description: Since upgrading from version 14.10 to Kubuntu 15.04, my system does not boot normally any more. Maybe it's only a stupid oversight on my part, but not being a systemd pro, I'm currently at a loss of how to debug this any further. Hints and pointers to appropriate documentation are welcome! Kubuntu 15.04 quickly boots to a specific point where it seems to try to enable a dm-crypt partition which also carries /home, beside other data, and simply stalls. I'm not asked to enter my crytpdisk password and I also cannot enter it blindly without being asked. You can see the point where it stalls in the attached screenshot (photo of my screen). I can then press Ctrl+Alt+Del to cleanly restart the system but I could not find a way to get beyond this point with systemd. Using the alternative boot option with upstart works flawlessly. (Although booting with this boot option is really slow and it takes a while to reach the graphical login screen - it basically looks as if the system is waiting for some name resolving timeouts during boot, but that's a different issue, if've not debugged it further and maybe it's just gone once systemd works to boot my machine.) Further info about my setup: $ cat /etc/crypttab crypt /dev/mapper/main-cryptstore none luks,noearly,discard $ mount | egrep crypt /dev/mapper/crypt on /mnt/crypt type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /home type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /var/lib/mysql type ext4 (rw,relatime,data=ordered) Here the first entry is the actual mount point while the other mount points are bind mounts: $ cat /etc/fstab | egrep crypt /dev/mapper/crypt /mnt/crypt ext4defaults0 2 /mnt/crypt/home /home nonebind0 0 /mnt/crypt/var_lib_mysql/var/lib/mysql nonebind0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 11 20:28:18 2015 MachineType: Sony Corporation SVS13A3W9ES ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/main-root ro quiet init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service - /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 1 overridden configuration files found. UpgradeStatus: Upgraded to vivid on 2015-04-28 (13 days ago) dmi.bios.date: 03/13/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1021C8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS13A3W9ES:pvrC60BRBTW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVS13A3W9ES dmi.product.version: C60BRBTW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+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 1453912] Re: systemd does not unlock dm-crypt password
@Martin, Sorry for late reply. I spilled juice in my computer and it fried. Never gets old :-) I have a new computer so I cant do proper debugging anymore. I will check a friends computer since I think he has the exact same problem. On Wednesday next week that is (is in transit until then). ..will test the method in /usr/share/doc/systemd/README.Debian. Btw, could the problem be that I had two passwords. One for the full disk and one for the home folder? So the setup tried to use the same password for the disk as the home folder? I had a keyboard key that was included in the password once that broke and had to change the disk/boot password (was a pain to 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/1453912 Title: systemd does not unlock dm-crypt password Status in systemd package in Ubuntu: Incomplete Bug description: Since upgrading from version 14.10 to Kubuntu 15.04, my system does not boot normally any more. Maybe it's only a stupid oversight on my part, but not being a systemd pro, I'm currently at a loss of how to debug this any further. Hints and pointers to appropriate documentation are welcome! Kubuntu 15.04 quickly boots to a specific point where it seems to try to enable a dm-crypt partition which also carries /home, beside other data, and simply stalls. I'm not asked to enter my crytpdisk password and I also cannot enter it blindly without being asked. You can see the point where it stalls in the attached screenshot (photo of my screen). I can then press Ctrl+Alt+Del to cleanly restart the system but I could not find a way to get beyond this point with systemd. Using the alternative boot option with upstart works flawlessly. (Although booting with this boot option is really slow and it takes a while to reach the graphical login screen - it basically looks as if the system is waiting for some name resolving timeouts during boot, but that's a different issue, if've not debugged it further and maybe it's just gone once systemd works to boot my machine.) Further info about my setup: $ cat /etc/crypttab crypt /dev/mapper/main-cryptstore none luks,noearly,discard $ mount | egrep crypt /dev/mapper/crypt on /mnt/crypt type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /home type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /var/lib/mysql type ext4 (rw,relatime,data=ordered) Here the first entry is the actual mount point while the other mount points are bind mounts: $ cat /etc/fstab | egrep crypt /dev/mapper/crypt /mnt/crypt ext4defaults0 2 /mnt/crypt/home /home nonebind0 0 /mnt/crypt/var_lib_mysql/var/lib/mysql nonebind0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 11 20:28:18 2015 MachineType: Sony Corporation SVS13A3W9ES ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/main-root ro quiet init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service - /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 1 overridden configuration files found. UpgradeStatus: Upgraded to vivid on 2015-04-28 (13 days ago) dmi.bios.date: 03/13/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1021C8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS13A3W9ES:pvrC60BRBTW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVS13A3W9ES dmi.product.version: C60BRBTW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+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 1453912] Re: systemd does not allow to boot with /home on dm-crypt
Requested syslog attached (for real). ** Attachment added: Syslog for two consecutive boots (systemd,upstart) https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+attachment/4412564/+files/syslog -- 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/1453912 Title: systemd does not allow to boot with /home on dm-crypt Status in systemd package in Ubuntu: Incomplete Bug description: Since upgrading from version 14.10 to Kubuntu 15.04, my system does not boot normally any more. Maybe it's only a stupid oversight on my part, but not being a systemd pro, I'm currently at a loss of how to debug this any further. Hints and pointers to appropriate documentation are welcome! Kubuntu 15.04 quickly boots to a specific point where it seems to try to enable a dm-crypt partition which also carries /home, beside other data, and simply stalls. I'm not asked to enter my crytpdisk password and I also cannot enter it blindly without being asked. You can see the point where it stalls in the attached screenshot (photo of my screen). I can then press Ctrl+Alt+Del to cleanly restart the system but I could not find a way to get beyond this point with systemd. Using the alternative boot option with upstart works flawlessly. (Although booting with this boot option is really slow and it takes a while to reach the graphical login screen - it basically looks as if the system is waiting for some name resolving timeouts during boot, but that's a different issue, if've not debugged it further and maybe it's just gone once systemd works to boot my machine.) Further info about my setup: $ cat /etc/crypttab crypt /dev/mapper/main-cryptstore none luks,noearly,discard $ mount | egrep crypt /dev/mapper/crypt on /mnt/crypt type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /home type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /var/lib/mysql type ext4 (rw,relatime,data=ordered) Here the first entry is the actual mount point while the other mount points are bind mounts: $ cat /etc/fstab | egrep crypt /dev/mapper/crypt /mnt/crypt ext4defaults0 2 /mnt/crypt/home /home nonebind0 0 /mnt/crypt/var_lib_mysql/var/lib/mysql nonebind0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 11 20:28:18 2015 MachineType: Sony Corporation SVS13A3W9ES ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/main-root ro quiet init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service - /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 1 overridden configuration files found. UpgradeStatus: Upgraded to vivid on 2015-04-28 (13 days ago) dmi.bios.date: 03/13/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1021C8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS13A3W9ES:pvrC60BRBTW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVS13A3W9ES dmi.product.version: C60BRBTW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+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 1453912] Re: systemd does not allow to boot with /home on dm-crypt
Requested syslog attached. -- 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/1453912 Title: systemd does not allow to boot with /home on dm-crypt Status in systemd package in Ubuntu: Incomplete Bug description: Since upgrading from version 14.10 to Kubuntu 15.04, my system does not boot normally any more. Maybe it's only a stupid oversight on my part, but not being a systemd pro, I'm currently at a loss of how to debug this any further. Hints and pointers to appropriate documentation are welcome! Kubuntu 15.04 quickly boots to a specific point where it seems to try to enable a dm-crypt partition which also carries /home, beside other data, and simply stalls. I'm not asked to enter my crytpdisk password and I also cannot enter it blindly without being asked. You can see the point where it stalls in the attached screenshot (photo of my screen). I can then press Ctrl+Alt+Del to cleanly restart the system but I could not find a way to get beyond this point with systemd. Using the alternative boot option with upstart works flawlessly. (Although booting with this boot option is really slow and it takes a while to reach the graphical login screen - it basically looks as if the system is waiting for some name resolving timeouts during boot, but that's a different issue, if've not debugged it further and maybe it's just gone once systemd works to boot my machine.) Further info about my setup: $ cat /etc/crypttab crypt /dev/mapper/main-cryptstore none luks,noearly,discard $ mount | egrep crypt /dev/mapper/crypt on /mnt/crypt type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /home type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /var/lib/mysql type ext4 (rw,relatime,data=ordered) Here the first entry is the actual mount point while the other mount points are bind mounts: $ cat /etc/fstab | egrep crypt /dev/mapper/crypt /mnt/crypt ext4defaults0 2 /mnt/crypt/home /home nonebind0 0 /mnt/crypt/var_lib_mysql/var/lib/mysql nonebind0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 11 20:28:18 2015 MachineType: Sony Corporation SVS13A3W9ES ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/main-root ro quiet init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service - /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 1 overridden configuration files found. UpgradeStatus: Upgraded to vivid on 2015-04-28 (13 days ago) dmi.bios.date: 03/13/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1021C8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS13A3W9ES:pvrC60BRBTW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVS13A3W9ES dmi.product.version: C60BRBTW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+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 1453912] Re: systemd does not allow to boot with /home on dm-crypt
I have a very similar issue. Upstart works but systemd does not. Lucs encrypted logical volume on a work computer. It has worked flawless with boot for many versions of Ubuntu (even before upstart I think). I can produce the syslog with two boots tomorrow. Also have taken a picture of the actual error message during boot with systemd, which is attached. Upstart presents the password prompt, systemd does not. ** Attachment added: Picture of output during boot with systemd https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+attachment/4412269/+files/20150609_175942.jpg -- 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/1453912 Title: systemd does not allow to boot with /home on dm-crypt Status in systemd package in Ubuntu: Incomplete Bug description: Since upgrading from version 14.10 to Kubuntu 15.04, my system does not boot normally any more. Maybe it's only a stupid oversight on my part, but not being a systemd pro, I'm currently at a loss of how to debug this any further. Hints and pointers to appropriate documentation are welcome! Kubuntu 15.04 quickly boots to a specific point where it seems to try to enable a dm-crypt partition which also carries /home, beside other data, and simply stalls. I'm not asked to enter my crytpdisk password and I also cannot enter it blindly without being asked. You can see the point where it stalls in the attached screenshot (photo of my screen). I can then press Ctrl+Alt+Del to cleanly restart the system but I could not find a way to get beyond this point with systemd. Using the alternative boot option with upstart works flawlessly. (Although booting with this boot option is really slow and it takes a while to reach the graphical login screen - it basically looks as if the system is waiting for some name resolving timeouts during boot, but that's a different issue, if've not debugged it further and maybe it's just gone once systemd works to boot my machine.) Further info about my setup: $ cat /etc/crypttab crypt /dev/mapper/main-cryptstore none luks,noearly,discard $ mount | egrep crypt /dev/mapper/crypt on /mnt/crypt type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /home type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /var/lib/mysql type ext4 (rw,relatime,data=ordered) Here the first entry is the actual mount point while the other mount points are bind mounts: $ cat /etc/fstab | egrep crypt /dev/mapper/crypt /mnt/crypt ext4defaults0 2 /mnt/crypt/home /home nonebind0 0 /mnt/crypt/var_lib_mysql/var/lib/mysql nonebind0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 11 20:28:18 2015 MachineType: Sony Corporation SVS13A3W9ES ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/main-root ro quiet init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service - /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 1 overridden configuration files found. UpgradeStatus: Upgraded to vivid on 2015-04-28 (13 days ago) dmi.bios.date: 03/13/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1021C8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS13A3W9ES:pvrC60BRBTW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVS13A3W9ES dmi.product.version: C60BRBTW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+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 1453912] Re: systemd does not allow to boot with /home on dm-crypt
Some setup info as previous post: sda5_crypt UUID=acdea251-1e21-4612-afce-4101e364d6c6 none luks cryptswap1 /dev/dm-1 /dev/urandom swap,cipher=aes-cbc-essiv:sha256 mount -l with upstart sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,relatime,size=6130708k,nr_inodes=1532677,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1229448k,mode=755) /dev/mapper/lvm1-sysroot on / type ext4 (rw,relatime,errors=remount-ro,data=ordered) none on /sys/fs/cgroup type tmpfs (rw,relatime,size=4k,mode=755) none on /sys/fs/fuse/connections type fusectl (rw,relatime) none on /sys/kernel/debug type debugfs (rw,relatime) none on /sys/kernel/security type securityfs (rw,relatime) tmpfs on /tmp type tmpfs (rw,noatime) none on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) none on /run/shm type tmpfs (rw,nosuid,nodev,relatime) none on /run/user type tmpfs (rw,nosuid,nodev,noexec,relatime,size=102400k,mode=755) none on /sys/fs/pstore type pstore (rw,relatime) cgmfs on /run/cgmanager/fs type tmpfs (rw,relatime,size=100k,mode=755) /dev/mapper/lvm1-home on /home type ext4 (rw,relatime,data=ordered) /dev/sda1 on /boot type ext4 (rw,relatime,data=ordered) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime) rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw,relatime) tmpfs on /run/user/104 type tmpfs (rw,nosuid,nodev,relatime,size=1229448k,mode=700,uid=104,gid=111) tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1229448k,mode=700,uid=1000,gid=1000) /home/user1/.Private on /home/user1 type ecryptfs (rw,nosuid,nodev,relatime,ecryptfs_fnek_sig=9609cabaf4e75b54,ecryptfs_sig=825adaf5c17ffed8,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs) gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000) -- 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/1453912 Title: systemd does not allow to boot with /home on dm-crypt Status in systemd package in Ubuntu: Incomplete Bug description: Since upgrading from version 14.10 to Kubuntu 15.04, my system does not boot normally any more. Maybe it's only a stupid oversight on my part, but not being a systemd pro, I'm currently at a loss of how to debug this any further. Hints and pointers to appropriate documentation are welcome! Kubuntu 15.04 quickly boots to a specific point where it seems to try to enable a dm-crypt partition which also carries /home, beside other data, and simply stalls. I'm not asked to enter my crytpdisk password and I also cannot enter it blindly without being asked. You can see the point where it stalls in the attached screenshot (photo of my screen). I can then press Ctrl+Alt+Del to cleanly restart the system but I could not find a way to get beyond this point with systemd. Using the alternative boot option with upstart works flawlessly. (Although booting with this boot option is really slow and it takes a while to reach the graphical login screen - it basically looks as if the system is waiting for some name resolving timeouts during boot, but that's a different issue, if've not debugged it further and maybe it's just gone once systemd works to boot my machine.) Further info about my setup: $ cat /etc/crypttab crypt /dev/mapper/main-cryptstore none luks,noearly,discard $ mount | egrep crypt /dev/mapper/crypt on /mnt/crypt type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /home type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /var/lib/mysql type ext4 (rw,relatime,data=ordered) Here the first entry is the actual mount point while the other mount points are bind mounts: $ cat /etc/fstab | egrep crypt /dev/mapper/crypt /mnt/crypt ext4defaults0 2 /mnt/crypt/home /home nonebind0 0 /mnt/crypt/var_lib_mysql/var/lib/mysql nonebind0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 11 20:28:18 2015 MachineType: Sony Corporation SVS13A3W9ES ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/main-root ro quiet init=/sbin/upstart SourcePackage: systemd SystemdDelta:
[Touch-packages] [Bug 1323089] Re: wpa_supplicant writes to syslog every 2 minutes
Connectivity issues reported: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1323089/comments/17 Read the full thread with information before making claims. An I wrote and perhaps connectivity issues as well (which is not unlikely). Nuff said. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1323089 Title: wpa_supplicant writes to syslog every 2 minutes Status in “wpa” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04 LTS wpasupplicant 2.1-0ubuntu1 wpa_supplicant is writing to syslog every couple of minutes. Example output: May 25 19:57:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 19:57:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 19:59:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 19:59:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:00:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:01:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:01:24 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:03:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:03:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:05:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:05:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:05:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:07:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:07:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:09:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:09:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:10:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:13:18 ubuntu wpa_supplicant[1161]: message repeated 2 times: [ wlan0: CTRL-EVENT-SCAN-STARTED ] May 25 20:13:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 The message seems harmless as far as the network is concerned, meaning there is no problem with the wifi connection. But it's spamming the syslog, making it very difficult to find any other thing there, and it's generating constant writes to disk, and an unnecessarily large syslog file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1323089/+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 1323089] Re: wpa_supplicant writes to syslog every 2 minutes
Well, bug 57843 does not describe symptoms besides spamming of the syslog. This bug does describe spamming of syslog and perhaps connectivity issues for some users. However, the the upstream bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539915 you mention NoOp seems to be similar to this one. Perhaps this bug is more informative than 539915, with suggestions for solving the problem, that work in some cases, so just merge bug 539915 an 1323089 instead. In my view it is unclear if bug 57843 is related. ** Bug watch added: Debian Bug tracker #539915 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539915 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1323089 Title: wpa_supplicant writes to syslog every 2 minutes Status in “wpa” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04 LTS wpasupplicant 2.1-0ubuntu1 wpa_supplicant is writing to syslog every couple of minutes. Example output: May 25 19:57:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 19:57:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 19:59:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 19:59:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:00:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:01:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:01:24 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:03:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:03:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:05:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:05:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:05:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:07:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:07:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:09:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:09:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:10:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:13:18 ubuntu wpa_supplicant[1161]: message repeated 2 times: [ wlan0: CTRL-EVENT-SCAN-STARTED ] May 25 20:13:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 The message seems harmless as far as the network is concerned, meaning there is no problem with the wifi connection. But it's spamming the syslog, making it very difficult to find any other thing there, and it's generating constant writes to disk, and an unnecessarily large syslog file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1323089/+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 1323089] Re: wpa_supplicant writes to syslog every 2 minutes
Thank you ricklee! Worked on my setup too. Still, this message should only be visible with verbose debugging. Muted as default for consumers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1323089 Title: wpa_supplicant writes to syslog every 2 minutes Status in “wpa” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04 LTS wpasupplicant 2.1-0ubuntu1 wpa_supplicant is writing to syslog every couple of minutes. Example output: May 25 19:57:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 19:57:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 19:59:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 19:59:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:00:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:01:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:01:24 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:03:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:03:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:05:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:05:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:05:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:07:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:07:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:09:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:09:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:10:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:13:18 ubuntu wpa_supplicant[1161]: message repeated 2 times: [ wlan0: CTRL-EVENT-SCAN-STARTED ] May 25 20:13:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 The message seems harmless as far as the network is concerned, meaning there is no problem with the wifi connection. But it's spamming the syslog, making it very difficult to find any other thing there, and it's generating constant writes to disk, and an unnecessarily large syslog file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1323089/+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 1323089] Re: wpa_supplicant writes to syslog every 2 minutes
Any idea how this error message can be muted? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1323089 Title: wpa_supplicant writes to syslog every 2 minutes Status in “wpa” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04 LTS wpasupplicant 2.1-0ubuntu1 wpa_supplicant is writing to syslog every couple of minutes. Example output: May 25 19:57:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 19:57:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 19:59:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 19:59:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:00:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:01:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:01:24 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:03:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:03:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:05:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:05:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:05:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:07:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:07:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:09:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:09:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 May 25 20:10:58 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED May 25 20:13:18 ubuntu wpa_supplicant[1161]: message repeated 2 times: [ wlan0: CTRL-EVENT-SCAN-STARTED ] May 25 20:13:23 ubuntu wpa_supplicant[1161]: nl80211: send_and_recv-nl_recvmsgs failed: -33 The message seems harmless as far as the network is concerned, meaning there is no problem with the wifi connection. But it's spamming the syslog, making it very difficult to find any other thing there, and it's generating constant writes to disk, and an unnecessarily large syslog file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1323089/+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 1323772] Re: Unattended apt-get dist-upgrade -qq --force-yes on 14.04 fails on grub configuration.
Note that the bug https://bugs.launchpad.net/cloud-init/+bug/1309079 mentions that the work-around is not good enough. Will test myself today. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1323772 Title: Unattended apt-get dist-upgrade -qq --force-yes on 14.04 fails on grub configuration. Status in “apt” package in Ubuntu: Confirmed Bug description: Unattended apt-get dist-upgrade -qq --force-yes on 14.04 fails on Grub configuration. Reproduce by using apt-get dist-upgrade -qq --force-yes on the latest Ubuntu 14.04 image (https://cloud- images.ubuntu.com/locator/ec2/). It will not select grub defaults (install the package maintainer's version) during upgrade. Setup will prompt the user for input. This is a new behavior (for me, since Ubuntu 6). It breaks automatic/scripted setup of servers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1323772/+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 1323772] Re: Unattended apt-get dist-upgrade -qq --force-yes on 14.04 fails on grub configuration.
The work-around in https://bugs.launchpad.net/cloud- init/+bug/1309079/comments/5 did work as expected: sudo rm /boot/grub/menu.lst sudo update-grub-legacy-ec2 -y sudo apt-get dist-upgrade -qq --force-yes However, as I understand, the prompt will still appear when doing later upgrades. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1323772 Title: Unattended apt-get dist-upgrade -qq --force-yes on 14.04 fails on grub configuration. Status in “apt” package in Ubuntu: Confirmed Bug description: Unattended apt-get dist-upgrade -qq --force-yes on 14.04 fails on Grub configuration. Reproduce by using apt-get dist-upgrade -qq --force-yes on the latest Ubuntu 14.04 image (https://cloud- images.ubuntu.com/locator/ec2/). It will not select grub defaults (install the package maintainer's version) during upgrade. Setup will prompt the user for input. This is a new behavior (for me, since Ubuntu 6). It breaks automatic/scripted setup of servers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1323772/+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 1323772] Re: Unattended apt-get dist-upgrade -qq --force-yes on 14.04 fails on grub configuration.
Related bug marked as fixed: https://bugs.launchpad.net/ubuntu/+bug/1009294 Discussion of workarounds: http://askubuntu.com/questions/146921/how- do-i-apt-get-y-dist-upgrade-without-a-grub-config-prompt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1323772 Title: Unattended apt-get dist-upgrade -qq --force-yes on 14.04 fails on grub configuration. Status in “apt” package in Ubuntu: Confirmed Bug description: Unattended apt-get dist-upgrade -qq --force-yes on 14.04 fails on Grub configuration. Reproduce by using apt-get dist-upgrade -qq --force-yes on the latest Ubuntu 14.04 image (https://cloud- images.ubuntu.com/locator/ec2/). It will not select grub defaults (install the package maintainer's version) during upgrade. Setup will prompt the user for input. This is a new behavior (for me, since Ubuntu 6). It breaks automatic/scripted setup of servers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1323772/+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 1323772] Re: Unattended apt-get dist-upgrade -qq --force-yes on 14.04 fails on grub configuration.
Why is there no response to this bug? You keep pushing up releases with this bug for no good reason! Confirmed in the eu 14.04 ebs ami-cb4986bc version at https://cloud- images.ubuntu.com/locator/ec2/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1323772 Title: Unattended apt-get dist-upgrade -qq --force-yes on 14.04 fails on grub configuration. Status in “apt” package in Ubuntu: Confirmed Bug description: Unattended apt-get dist-upgrade -qq --force-yes on 14.04 fails on Grub configuration. Reproduce by using apt-get dist-upgrade -qq --force-yes on the latest Ubuntu 14.04 image (https://cloud- images.ubuntu.com/locator/ec2/). It will not select grub defaults (install the package maintainer's version) during upgrade. Setup will prompt the user for input. This is a new behavior (for me, since Ubuntu 6). It breaks automatic/scripted setup of servers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1323772/+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
