[Bug 1770965] Re: After upgrade and reboot, the lightdm display manager does not start

2018-06-02 Thread Simon Pepping
** Attachment added: "The upgrade log files as requested" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1770965/+attachment/5147869/+files/dist-upgrade.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1770965] Re: After upgrade and reboot, the lightdm display manager does not start

2018-05-14 Thread Simon Pepping
I will keep this bug open. It is a release critical bug since it causes the user to have an unusable system after upgrade. If the lightdm configuration has the lightdm-kde-greeter configured as the greeter and if the user lets the upgrade remove the now obsolete lightdm-kde-greeter, the lightdm

[Bug 1770965] Re: After upgrade and reboot, the lightdm display manager does not start

2018-05-13 Thread Simon Pepping
It turns out that the problem is caused by lightdm: When its configuration points to a not-installed greeter, it fails to load. It is unfortunate that this bug raises its head upon release upgrade, which obseletes the kde greeter. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New

[Bug 1770965] [NEW] After upgrade and reboot, the lightdm display manager does not start

2018-05-13 Thread Simon Pepping
Public bug reported: Upon the upgrade, lightdm-kde-greeter was removed as it has become obsolete. That leaves the user with a system that hangs. I rebooted using system-recovery, and installed lightdm-gtk-greeter using aptitude. However, this greeter was not enabled in lightdm.conf. Also, the

[Bug 1770965] Re: After upgrade and reboot, the lightdm display manager does not start

2018-05-13 Thread Simon Pepping
The 2nd paragraph should start as: "To fix the problem I rebooted... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770965 Title: After upgrade and reboot, the lightdm display manager does not

[Bug 1753144] Re: Booting kernel 4.4.0-116.140 fails

2018-03-07 Thread Simon Pepping
Installed: linux-image-4.4.120-0404120-generic, Linux kernel image for version 4.4.120 on 32 bit x86 SMP, and associated headers. Booting fine: simon:~$ uname -a Linux vuurvlinder 4.4.120-0404120-generic #201803040932 SMP Sun Mar 4 14:44:35 UTC 2018 i686 i686 i686 GNU/Linux -- You received

[Bug 1753144] Re: Booting kernel 4.4.0-116.140 fails

2018-03-06 Thread Simon Pepping
Installed: linux-image-4.16.0-041600rc4-generic, Linux kernel image for version 4.16.0 on 32 bit x86 SMP, and associated headers. Booting fine: simon:~$ uname -a Linux vuurvlinder 4.16.0-041600rc4-generic #201803041930 SMP Mon Mar 5 00:44:23 UTC 2018 i686 i686 i686 GNU/Linux I guess this

[Bug 1753144] Re: Booting kernel 4.4.0-116.140 fails

2018-03-06 Thread Simon Pepping
Yes, I am able to boot with the previous kernel 4.4.0-112. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1753144 Title: Booting kernel 4.4.0-116.140 fails To manage notifications about this bug go

[Bug 1753144] Re: Booting kernel 4.4.0-116.140 fails

2018-03-04 Thread Simon Pepping
No luck running apport-collect: simon:~$ apport-collect 1753144 ERROR: Could not import module, is a package upgrade in progress? Error: No module named PyQt5.QtCore I cannot fix this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1753144] [NEW] Booting kernel 4.4.0-116.140 fails

2018-03-03 Thread Simon Pepping
Public bug reported: Booting kernel 4.4.0-116.140 lands me in an ash shell with prompt 'initramfs'. keyboard and mouse USB fails, so that I can do nothing. Error messages from module hid: 'unknown symbol __x86_indirect_thunk_XXX err -22' and 'disagrees about version of __x86_indirect_thunk_XXX

[Bug 1460431] Re: Canon Powershot camera not working in Kubuntu 15.04, was working fine in Kubuntu 14.10

2015-06-01 Thread Simon Pepping
In digikam I can import from the camera, using 'Canon Inc. Canon Digital Camera (auto-detected)'. This means that it works, even though there is not device notification. I am closing the bug. ** Changed in: gvfs (Ubuntu) Status: New = Invalid -- You received this bug notification because

[Bug 1460431] [NEW] Canon Powershot camera not working in Kubuntu 15.04, was working fine in Kubuntu 14.10

2015-05-31 Thread Simon Pepping
Public bug reported: My Canon Powershot SX610 is not recognized as a device in in Kubuntu 15.04, while it was recognized in Kubuntu 14.10. It uses PTP. This is the same as bug 1295275, except that it occurs in 15.04. I applied the patch mentioned in that bug and did the following in

[Bug 1460431] Re: Canon Powershot camera not working in Kubuntu 15.04, was working fine in Kubuntu 14.10

2015-05-31 Thread Simon Pepping
With the unmodified udev rules file of the package I get the same output from udevadm: P: /devices/pci:00/:00:1d.0/usb2/2-1/2-1.4 N: bus/usb/002/003 E: BUSNUM=002 E: COLORD_DEVICE=1 E: COLORD_KIND=camera E: DEVNAME=/dev/bus/usb/002/003 E: DEVNUM=003 E: