[Touch-packages] [Bug 1771204] Re: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

2018-05-30 Thread Thomas Diesenreiter
Hi there, I fear that I do not have the time to do such in-depth debugging atm. As I said, I used the latest kernel with my previous 17.10 install without this problem, and it occurred with the first kernel of the 18.04 release. I know that it would be easier for you to know the specific

[Touch-packages] [Bug 1771204] Re: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

2018-05-29 Thread Thomas Diesenreiter
Tested it with 4.17.0-041700rc6-generic, the bug still exists. ** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-4.17.0-041700rc6-generic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu.

[Touch-packages] [Bug 1771204] Re: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

2018-05-25 Thread Thomas Diesenreiter
Hi Christopher, ad 1: 17.10 ad 2: I cannot check that, sorry. My boot partition is so small (only 256mb, happened when I first installed ubuntu on this machine in 2013 for whatever reason), so i have to uninstall the older kernels immediately after updating in order to be able to install

[Touch-packages] [Bug 1771204] Re: Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

2018-05-14 Thread Thomas Diesenreiter
See photo of the screen attached. ** Attachment added: "IMG_20180514_224101.jpg" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771204/+attachment/5139476/+files/IMG_20180514_224101.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages,

[Touch-packages] [Bug 1771204] [NEW] Horizontal lines on Samsung Laptop np900x3f after Update to 18.04

2018-05-14 Thread Thomas Diesenreiter
Public bug reported: My laptop was running fine for years, but after the latest update to 18.04 and the reboot there were horizontal lines everywhere. It seems like its a regression of an older bug, because its the same bug with the same strange behaviour as listed here: