[Ubuntu-x-swat] [Bug 2020604] Re: After mesa upgrades, Chrome won't show graphics
While it's obviously not a real fix, As I don't use chrome as my primary browser, simply regenerating my ~/.config/google-chrome/ directory resolved this issue. Others may not have this option. Question 1 : What is it about the Mesa upgrade that kills chrome but not Firefox? Question 2 : Is there a less nuclear fix than wiping the Chrome settings? e.g. Deleting just the ShaderCache or GrShaderCache directories? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2020604 Title: After mesa upgrades, Chrome won't show graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2020604/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1803885] Re: Lenovo R60 screen corrupt immediately after install
For future reference (probably my own), if anyone else has this issue. Although the problem doesn't entirely go away. There is still some strange artifacting and ocassionally black foreground in windows. Most likely memory corruption, as a reboot cures it. In /etc/gdm3/custom.conf change the line [daemon] WaylandEnable=true to WaylandEnable=false -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1803885 Title: Lenovo R60 screen corrupt immediately after install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1803885/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1803885] Re: Lenovo R60 screen corrupt immediately after install
Anybody got a solution for this? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1803885 Title: Lenovo R60 screen corrupt immediately after install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1803885/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1803885] [NEW] Lenovo R60 screen corrupt immediately after install
Public bug reported: Version : Ubuntu 18.04.1 LTS Immediately after the install completes. The computer restarts to a corrupt login screen. Hardware : Lenovo R60 Video : 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV515/M54 [Mobility Radeon X1400] Xorg.log AMD Radeon HD 6900M Series, Mobility Radeon HD 6000 Series, BARTS, AMD Radeon HD 6800 Series, AMD Radeon HD 6700 Series, TURKS, CAICOS, ARUBA, TAHITI, PITCAIRN, VERDE, OLAND, HAINAN, BONAIRE, KABINI, MULLINS, KAVERI, HAWAII [13.133] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [13.133] (II) FBDEV: driver for framebuffer: fbdev [13.133] (II) VESA: driver for VESA chipsets: vesa [13.135] (II) [KMS] drm report modesetting isn't supported. [13.135] (EE) open /dev/dri/card0: No such file or directory [13.135] (WW) Falling back to old probe method for modesetting [13.135] (EE) open /dev/dri/card0: No such file or directory [13.135] (II) Loading sub module "fbdevhw" [13.135] (II) LoadModule: "fbdevhw" [13.136] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so [13.137] (II) Module fbdevhw: vendor="X.Org Foundation" [13.137]compiled for 1.19.6, module version = 0.0.2 [13.137]ABI class: X.Org Video Driver, version 23.0 [13.137] (**) FBDEV(2): claimed PCI slot 1@0:0:0 [13.137] (II) FBDEV(2): using default device [13.137] (WW) Falling back to old probe method for vesa [13.137] (EE) Screen 0 deleted because of no matching config section. [13.137] (II) UnloadModule: "radeon" [13.137] (EE) Screen 0 deleted because of no matching config section. [13.137] (II) UnloadModule: "modesetting" [13.138] (II) FBDEV(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [13.138] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32 After some digging, on another computer, adding nomodeset to the kernal startup parameters helps. Edited /etc/default/grub GRUB_CMDLINE_LINUX="nomodeset" $update-grub provides a usable but degraded session. The screen resolution is 1400x1050. ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1803885 Title: Lenovo R60 screen corrupt immediately after install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1803885/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 366937] Re: firefox segmentation fault in kde4.2 jaunty on maximizing flash video
I've been fighting this same problem since upgrading from Intrepid. I looks like X does not load all the dependencies for glx... here's my xorg.conf which works for my radeon 9600 dual monitor setup. (xorg- xserver-ati-video), This appears to have solved the problem for me. I can't be sure without some more testing though. Section Module LoadGLcore Loadglx Loadi2c Loadbitmap Loadddc Loadextmod Loadint10 Loadvbe Loaddri Loaddbe Loadv4l EndSection Section Monitor Identifier Configured Monitor EndSection Section Screen Identifier Default Screen Monitor Configured Monitor Device Configured Video Device SubSection Display Virtual 2560 1024 EndSubSection EndSection Section Device Identifier Configured Video Device Option AccelMethod EXA Option AddARGBGLXVisuals true Option RenderAccel true Option AllowGLXWithComposite true EndSection Section DRI Mode0666 EndSection Section Extensions Option Composite Enable EndSection -- firefox segmentation fault in kde4.2 jaunty on maximizing flash video https://bugs.launchpad.net/bugs/366937 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 366937] Re: firefox segmentation fault in kde4.2 jaunty on maximizing flash video
I forgot to mention I also had to do the following. sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri xserver-xorg-core -- firefox segmentation fault in kde4.2 jaunty on maximizing flash video https://bugs.launchpad.net/bugs/366937 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
