[Bug 1946525] Re: Removable media are not mounted automatically

2021-12-29 Thread Johan Tol
** Description changed: 1) Ubuntu Desktop amd 64 20211008.1 daily build - 2) udisks 2.9.4-1 + 2) udisks 2.9.4-1 3) Inserted disks, in this case the Ubuntu and VirtualBox Guest Additions disk images, should be mounted automatically 4) the automount feature seems to be gone or

[Bug 1773821] Re: Installation 18.04 fails

2018-05-28 Thread Johan Tol
*** This bug is a duplicate of bug 1771651 *** https://bugs.launchpad.net/bugs/1771651 ** This bug has been marked a duplicate of bug 1771651 The installation fails with a "GRUB installation failed" message. -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1773821] [NEW] Installation 18.04 fails

2018-05-28 Thread Johan Tol
Public bug reported: Message while installing 18.04: The 'grub-efi-amd64-signed' package failed to install into / target/. Without the GRUB boot loader, the installed system will not boot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14 ProcVersionSignature: Ubuntu

[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-01-11 Thread Johan Tol
The same for me today. After upgrading to 16.10 I had no connection via VPN. Deleting the line "dns=dnsmasq" from /etc/NetworkManager/Networkmanager.conf followed by 'sudo service NetworkManager restart" did the trick for me. The connection was very slow though, but I don't know if that is related

[Bug 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

2017-01-09 Thread Johan Tol
This fix doesn't work for me (Dell Latitude E6540, Ubuntu 16.04); /var/log/syslog mentions instead: Error calling EVIOCSKEYCODE on device node '/dev/input/event17' (scan code 0x100150, key code 190): Invalid argument -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1510970] Re: Intel driver crashes on Ubuntu 15.10

2016-07-02 Thread Johan Tol
The same for me. Today I rolled back the "uxa"-workaround by deleting the 20-intel.conf file from /etc/X11/xorg.conf.d (I didn't have one before the workaround). After a couple of hours I still haven't had a single crash. I guess 16.04 solved the problem. -- You received this bug notification

[Bug 1510998] Re: Xorg crashes with segfault on 15.10

2016-07-02 Thread Johan Tol
typo: 16.06 --> 16.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1510998 Title: Xorg crashes with segfault on 15.10 To manage notifications about this bug go to:

[Bug 1510998] Re: Xorg crashes with segfault on 15.10

2016-07-02 Thread Johan Tol
Shortly after its introduction I migrated to Ubuntu 16.04. Today I rolled back the "uxa"-workaround by deleting the 20-intel.conf file from /etc/X11/xorg.conf.d (I didn't have one before the workaround). After a couple of hours I still haven't had a single crash. I guess 16.06 solved the problem.

[Bug 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

2016-06-29 Thread Johan Tol
In /lib/udev/hwdb.d/60-keyboard.hwdb I see the following related to scan code 150: # Dell Latitude microphone mute evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnLatitude* # Dell Precision microphone mute evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*

[Bug 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

2016-06-29 Thread Johan Tol
I have exactly the same message for my Dell Latitude E6540. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1597415 Title: systemd-udevd: Error calling EVIOCSKEYCODE on device node

[Bug 1510970] Re: Intel driver crashes on Ubuntu 15.10

2015-12-04 Thread Johan Tol
Thank you Axel for pointing to the intel drivers. I installed the latest drivers and enabled SNA again. It looks as if it takes longer to crash now, but eventually it does. Prior to the update it was easy for me the reproduce a crash with LibreOffice Calc. That requires a bit more effort now. I

[Bug 1510970] Re: Intel driver crashes on Ubuntu 15.10

2015-11-14 Thread Johan Tol
Thank you Georgi for the workaround. Works for me! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1510970 Title: Intel driver crashes on Ubuntu 15.10 To manage notifications about this bug go to:

[Bug 1510998] Re: Xorg crashes with segfault on 15.10

2015-11-14 Thread Johan Tol
Thank you Anoop for referring to https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1510970 The workaround presented there works for me! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1510998] Re: Xorg crashes with segfault on 15.10

2015-11-04 Thread Johan Tol
Sorry for the delay, but I was able to generate a backtrace as described by Dirk Seidel in comment #7 and comment #8. The backtrace is attached. ** Attachment added: "gdb-X.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1510998/+attachment/4512905/+files/gdb-X.txt -- You received

[Bug 1510998] Re: Xorg crashes with segfault on 15.10

2015-10-31 Thread Johan Tol
Sorry, I can't generate a backtrace, same problem as Dirk: after executing "continue" in gdb my entire system freezes, so I can't get back to the X session. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1510998] Re: Xorg crashes with segfault on 15.10

2015-10-29 Thread Johan Tol
I have exactly the same problem since upgrading to 15.10. For me reproducable in LibreOffice 5.0.3.2 Calc by a right mouse click followed by selecting "Format Cells...". Xorg.0.log.old: [ 674.409] (EE) Backtrace: [ 674.409] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55d163d7262e] [