[Desktop-packages] [Bug 1876219] Re: iris driver for old cpu
Whiskey Lake is also affected, guess it is gen8? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1876219 Title: iris driver for old cpu Status in mesa package in Ubuntu: Confirmed Bug description: I am not completely sure where I should file the bug. I am using Lubuntu 20.04 with lxqt, and since the upgrade to 20.04 iris is the default graphics driver, which results in crashes in multiple apps including guvcview and calibre. Setting MESA_LOADER_DRIVER_OVERRIDE=i965 fixed the problem. I am not sure but is it true that iris does not support older generations of Intel CPUs? If it is the case would it be possible to revert to i965 in those circumstances? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1876219/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877879] [NEW] segfault in iris_dri.so
Public bug reported: As of Ubuntu 20.04, on intel graphics with intel driver (not modesetting), I got segfault whenever anything tries to use GL. This happens unless I export MESA_LOADER_DRIVER_OVERRIDE=i965. One says that it does not happen with modesetting driver. (gdb) run Starting program: /usr/bin/glxgears [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x717cf700 (LWP 97070)] [New Thread 0x7fffebfff700 (LWP 97071)] [New Thread 0x70fce700 (LWP 97072)] [New Thread 0x7fffeb7fe700 (LWP 97073)] Thread 1 "glxgears" received signal SIGSEGV, Segmentation fault. 0x76a7e1d4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (gdb) where #0 0x76a7e1d4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #1 0x76c42de4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #2 0x76a59e5d in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #3 0x76a5aa95 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x76099774 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x711e in ?? () #6 0x6c88 in ?? () #7 0x77ace0b3 in __libc_start_main (main=0x6410, argc=1, argv=0x7fffe698, init=, fini=, rtld_fini=, stack_end=0x7fffe688) at ../csu/libc-start.c:308 #8 0x6f0a in ?? () (gdb) I believe, this is a bug in mesa tracked here: https://gitlab.freedesktop.org/mesa/mesa/issues/1358 packages versions: libgl1-mesa-dri:amd64 20.0.4-2ubuntu1 amd64 xserver-xorg-video-intel 2:2.99.917+git20200226-1amd64 xserver-xorg-core 2:1.20.8-2ubuntu2 amd64 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1877879 Title: segfault in iris_dri.so Status in mesa package in Ubuntu: New Bug description: As of Ubuntu 20.04, on intel graphics with intel driver (not modesetting), I got segfault whenever anything tries to use GL. This happens unless I export MESA_LOADER_DRIVER_OVERRIDE=i965. One says that it does not happen with modesetting driver. (gdb) run Starting program: /usr/bin/glxgears [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x717cf700 (LWP 97070)] [New Thread 0x7fffebfff700 (LWP 97071)] [New Thread 0x70fce700 (LWP 97072)] [New Thread 0x7fffeb7fe700 (LWP 97073)] Thread 1 "glxgears" received signal SIGSEGV, Segmentation fault. 0x76a7e1d4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (gdb) where #0 0x76a7e1d4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #1 0x76c42de4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #2 0x76a59e5d in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #3 0x76a5aa95 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x76099774 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x711e in ?? () #6 0x6c88 in ?? () #7 0x77ace0b3 in __libc_start_main (main=0x6410, argc=1, argv=0x7fffe698, init=, fini=, rtld_fini=, stack_end=0x7fffe688) at ../csu/libc-start.c:308 #8 0x6f0a in ?? () (gdb) I believe, this is a bug in mesa tracked here: https://gitlab.freedesktop.org/mesa/mesa/issues/1358 packages versions: libgl1-mesa-dri:amd64 20.0.4-2ubuntu1 amd64 xserver-xorg-video-intel 2:2.99.917+git20200226-1 amd64 xserver-xorg-core 2:1.20.8-2ubuntu2 amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1877879/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1751776] Re: google-chrome crashes in i965_dri.so
solved by system reinstall. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1751776 Title: google-chrome crashes in i965_dri.so Status in mesa package in Ubuntu: Incomplete Bug description: Google-chrome crashes in i965_dri.so. Lib GL mesa is version 18.0.0~rc4-1ubuntu1. Google-chrome is version 64.0.3282.186 (Official Build) (64-bit). It creates core dump files and it chrome complains about: Log Messages GpuProcessHostUIShim: The GPU process crashed! GpuProcessHostUIShim: The GPU process crashed! GpuProcessHostUIShim: The GPU process crashed! (gdb) where #0 0x7f781b626b78 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #1 0x0001 in ?? () #2 0x55d0d3597fff in ?? () #3 0x in ?? () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1751776/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1751776] [NEW] google-chrome crashes in i965_dri.so
Public bug reported: Google-chrome crashes in i965_dri.so. Lib GL mesa is version 18.0.0~rc4-1ubuntu1. Google-chrome is version 64.0.3282.186 (Official Build) (64-bit). It creates core dump files and it chrome complains about: Log Messages GpuProcessHostUIShim: The GPU process crashed! GpuProcessHostUIShim: The GPU process crashed! GpuProcessHostUIShim: The GPU process crashed! (gdb) where #0 0x7f781b626b78 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #1 0x0001 in ?? () #2 0x55d0d3597fff in ?? () #3 0x in ?? () ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1751776 Title: google-chrome crashes in i965_dri.so Status in mesa package in Ubuntu: New Bug description: Google-chrome crashes in i965_dri.so. Lib GL mesa is version 18.0.0~rc4-1ubuntu1. Google-chrome is version 64.0.3282.186 (Official Build) (64-bit). It creates core dump files and it chrome complains about: Log Messages GpuProcessHostUIShim: The GPU process crashed! GpuProcessHostUIShim: The GPU process crashed! GpuProcessHostUIShim: The GPU process crashed! (gdb) where #0 0x7f781b626b78 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #1 0x0001 in ?? () #2 0x55d0d3597fff in ?? () #3 0x in ?? () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1751776/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 994739] Re: wireless takes several seconds longer to connect from standby
I can confirm that the patch fix_driver_wext_for_broadcom_wl.patch is broken, supplicant stopped working with iwlwifi driver resulting with: ioctl[SIOCGIWSCAN]: Argument list too long ioctl[SIOCGIWSCAN]: Argument list too long ioctl[SIOCGIWSCAN]: Argument list too long ioctl[SIOCGIWSCAN]: Argument list too long ioctl[SIOCGIWSCAN]: Argument list too long ioctl[SIOCGIWSCAN]: Argument list too long -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/994739 Title: wireless takes several seconds longer to connect from standby Status in “network-manager” package in Ubuntu: Invalid Status in “wpasupplicant” package in Ubuntu: In Progress Status in “network-manager” source package in Precise: Invalid Status in “wpasupplicant” source package in Precise: Triaged Bug description: My observation is that network-manager is taking longer to connect to my wireless access point than 11.10. I trust the rest of the attached info will reveal all necessary system data. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic-pae 3.2.16 Uname: Linux 3.2.0-24-generic-pae i686 NonfreeKernelModules: wl nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Fri May 4 12:47:28 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) IpRoute: default via 192.168.1.1 dev eth1 proto static 169.254.0.0/16 dev eth1 scope link metric 1000 192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.116 metric 2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1264165e3-74f6-4750-8198-6e8b6d3632cf 802-3-ethernet1336133356 Fri 04 May 2012 07:09:16 AM CDTyes no /org/freedesktop/NetworkManager/Settings/1 2.4GHzWPA29afe3092-8693-4b03-92cd-fd179af0fca8 802-11-wireless 1336153624 Fri 04 May 2012 12:47:04 PM CDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/994739/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1022100] [NEW] evince does not store settings
Public bug reported: Hi, I use XFCE environment and evince. On evince start, I get message: ** (evince:14863): WARNING **: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files Maybe it is related to the main problem, evince does not preserve any setting I made (e.g., non continuous viewing). At each new start, I have to again turn off continuous viewing. Also zoom level nor window size is not preserved. Either for old pdf files or new ones. I use ubuntu quantal (but this bug is present also in 12.04). I use evince-gtk package, version 3.5.3-0ubuntu5 amd64. -- Lukas Hejtmanek ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1022100 Title: evince does not store settings Status in “evince” package in Ubuntu: New Bug description: Hi, I use XFCE environment and evince. On evince start, I get message: ** (evince:14863): WARNING **: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files Maybe it is related to the main problem, evince does not preserve any setting I made (e.g., non continuous viewing). At each new start, I have to again turn off continuous viewing. Also zoom level nor window size is not preserved. Either for old pdf files or new ones. I use ubuntu quantal (but this bug is present also in 12.04). I use evince-gtk package, version 3.5.3-0ubuntu5 amd64. -- Lukas Hejtmanek To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1022100/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
