[Bug 1881701] Re: NVIDIA cards should have set AllowExternalGpus in /usr/share/X11/xorg.conf.d/10-nvidia.conf
** Tags added: hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881701 Title: NVIDIA cards should have set AllowExternalGpus in /usr/share/X11/xorg.conf.d/10-nvidia.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1881701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
** Tags added: hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835630] Re: Relax dependency on specific version of libnvidia-compute-NNN
** Tags added: disco eoan groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835630 Title: Relax dependency on specific version of libnvidia-compute-NNN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvtop/+bug/1835630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835630] Re: Relax dependency on specific version of libnvidia-compute-NNN
** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835630 Title: Relax dependency on specific version of libnvidia-compute-NNN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvtop/+bug/1835630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835630] Re: Relax dependency on specific version of libnvidia-compute-NNN
This is fixed in hirsute hippo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835630 Title: Relax dependency on specific version of libnvidia-compute-NNN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvtop/+bug/1835630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773174] Re: Dutch lowercase translation warnings
** Changed in: snapd (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773174 Title: Dutch lowercase translation warnings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1773174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820074] Re: Running glxgears with Indirect GLX crashes Xorg
Also affects Disco ** Tags added: disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820074 Title: Running glxgears with Indirect GLX crashes Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1820074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1633319] Re: memory leak in indicator-datetime
This affects Eoan if you install Ubuntu proper, add accounts to "Online Accounts", then switch into an Ubuntu Mate session (installed via Apt on top of the same system - apt install ubuntu-mate-desktop^) ** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1633319 Title: memory leak in indicator-datetime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1633319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776447] Re: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/issues #211 https://gitlab.freedesktop.org/xorg/xserver/issues/211 ** Changed in: xorg-server Importance: Medium => Unknown ** Changed in: xorg-server Remote watch: freedesktop.org Bugzilla #99555 => gitlab.freedesktop.org/xorg/xserver/issues #211 ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776447] Re: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash
** Tags added: disco eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776447] Re: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash
A fix has now landed upstream. I think this could be a candidate for an SRU cherry-pick for every supported release back to Xenial. The upstream commit is https://gitlab.freedesktop.org/xorg/xserver/commit/e1fa3beb2fe2519e69f859f0acdc68e5a770de27. It's a very simple one-line change and is merely a revert of a prior upstream commit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776447] Re: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash
This is the upstream patch. It changes the return from __glXDRIcontextWait from hardcoded -1 to noClientException which will either be -1 or nothing. This is the pre-2016 behaviour that is being restored. ** Patch added: "xorg-server-iglx.diff" https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323631/+files/xorg-server-iglx.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776447] Re: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash
** Description changed: + [Impact] + + * IGLX is a way for an opengl application sending the 3D drawing GLX + commands to the Xorg server for rendering instead of using the DRI + infrastructure it is commonplace for High Performance Compute and + Scientific institutions to use this feature of the Xorg server. (ref: + https://www.phoronix.com/scan.php?page=news_item&px=Xorg-IGLX-Potential- + Bye-Bye) + + * The feature is completely broken, currently, and any attempt to use + it will cause the Xorg server to crash. This feature has been broken + since a commit upstream in 2016. + + * The attached patch is from the revert commit entered into the + upstream repository on 28 Jan 2020 following a git bisect of the bug + discovering the offending commit. + + [Test Case] + + * Create a new file at /etc/X11/xorg.conf.d/99-IGLX.conf with the + following contents: + + ``` + Section "ServerFlags" + Option "IndirectGLX" "on" + EndSection + ``` + + * Log out of your Xorg session + * Switch to a VT (Ctrl+Alt+F2) and login + * Run `sudo systemctl restart gdm` to restart Xorg + * Login to the graphical session + * If you do not have mesa-utils installed, then install it with the terminal command `sudo apt install mesa-utils` + * Open a terminal and execute `LIBGL_ALWAYS_INDIRECT=1 glxgears` + * If the fix is successful then glxgears should start and remain active without the Xorg server or glxgears crashing/segfaulting + + [Regression Potential] + + * This change is within DRI-related functionality and so might break + all 3D accelerated applications. + + * There is a potential that the change is insufficient to fix the IGLX + feature and so attempts to use it may still have undesirable and + undefined results. + + * Upstream has run the patch through their CI system, which passed with no errors. This does not necessarily mean the patch will achieve the desired results, but at least indicates that the code does compile cleanly and can start an Xvfb headless instance. + + [Other Info] + + Original Bug Report Follows + There's already an upstream bug report here: https://bugs.freedesktop.org/show_bug.cgi?id=99555 Basically, with Option "IndirectGLX" "True" and LIBGL_ALWAYS_INDIRECT=1 I get immediate crashes e.g. with glxgear: - steved@xubuntu:~$ LIBGL_ALWAYS_INDIRECT=true glxgears + steved@xubuntu:~$ LIBGL_ALWAYS_INDIRECT=true glxgears Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. X Error of failed request: 255 - Major opcode of failed request: 155 (GLX) - Minor opcode of failed request: 1 (X_GLXRender) - Serial number of failed request: 42 - Current serial number in output stream: 936 + Major opcode of failed request: 155 (GLX) + Minor opcode of failed request: 1 (X_GLXRender) + Serial number of failed request: 42 + Current serial number in output stream: 936 I am trying to run what is effectively a traditional X Terminal, but as the hardware I am using has a 3D accelerated chipset it seems sensible to try to use it.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Tue Jun 12 10:09:30 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: - rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-22-generic, x86_64: installed - rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-23-generic, x86_64: installed + rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-22-generic, x86_64: installed + rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller]) -Subsystem: Intel Corporation Device [8086:2212] + Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller]) + Subsystem: Intel Corporation Device [8086:2212] InstallationDate: Installed on 2018-05-31 (11 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: AZW S I ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_GB.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_GB.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=/dev/mapper/xubuntu--vg-root ro noresume SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 00.12 dmi.board.asset.tag: Default string dmi.board.name: AB1 dmi.board.vendor: IP3 Tech dmi.board.version:
[Bug 1776447] Re: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash
** Patch added: "debdiff for focal" https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323645/+files/xorg-server_1.20.6-1ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776447] Re: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash
** Patch removed: "debdiff for focal" https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323645/+files/xorg-server_1.20.6-1ubuntu2.debdiff ** Patch added: "re-rolled debdiff for focal" https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323646/+files/xorg-server_1.20.6-1ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776447] Re: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash
** Attachment added: "debdiff for eoan" https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323647/+files/xorg-server_1.20.5+git20191008-0ubuntu1.dsc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776447] Re: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash
** Attachment removed: "debdiff for eoan" https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323647/+files/xorg-server_1.20.5+git20191008-0ubuntu1.dsc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776447] Re: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash
** Patch added: "debdiff for eoan" https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323650/+files/xorg-server_1.20.5+git20191008-0ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776447] Re: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash
** Patch removed: "re-rolled debdiff for focal" https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323646/+files/xorg-server_1.20.6-1ubuntu2.debdiff ** Description changed: [Impact] * IGLX is a way for an opengl application sending the 3D drawing GLX commands to the Xorg server for rendering instead of using the DRI infrastructure it is commonplace for High Performance Compute and Scientific institutions to use this feature of the Xorg server. (ref: https://www.phoronix.com/scan.php?page=news_item&px=Xorg-IGLX-Potential- Bye-Bye) * The feature is completely broken, currently, and any attempt to use it will cause the Xorg server to crash. This feature has been broken since a commit upstream in 2016. * The attached patch is from the revert commit entered into the upstream repository on 28 Jan 2020 following a git bisect of the bug discovering the offending commit. [Test Case] * Create a new file at /etc/X11/xorg.conf.d/99-IGLX.conf with the following contents: ``` Section "ServerFlags" Option "IndirectGLX" "on" EndSection ``` * Log out of your Xorg session * Switch to a VT (Ctrl+Alt+F2) and login * Run `sudo systemctl restart gdm` to restart Xorg * Login to the graphical session * If you do not have mesa-utils installed, then install it with the terminal command `sudo apt install mesa-utils` * Open a terminal and execute `LIBGL_ALWAYS_INDIRECT=1 glxgears` * If the fix is successful then glxgears should start and remain active without the Xorg server or glxgears crashing/segfaulting [Regression Potential] * This change is within DRI-related functionality and so might break all 3D accelerated applications. * There is a potential that the change is insufficient to fix the IGLX feature and so attempts to use it may still have undesirable and undefined results. * Upstream has run the patch through their CI system, which passed with no errors. This does not necessarily mean the patch will achieve the desired results, but at least indicates that the code does compile cleanly and can start an Xvfb headless instance. [Other Info] - * This bug affects Ubuntu releases all the way back to, and including, - Xenial 16.04. + * This bug affects Ubuntu releases all the way back to, and including, + Bionic 18.04. Original Bug Report Follows There's already an upstream bug report here: https://bugs.freedesktop.org/show_bug.cgi?id=99555 Basically, with Option "IndirectGLX" "True" and LIBGL_ALWAYS_INDIRECT=1 I get immediate crashes e.g. with glxgear: steved@xubuntu:~$ LIBGL_ALWAYS_INDIRECT=true glxgears Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. X Error of failed request: 255 Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 1 (X_GLXRender) Serial number of failed request: 42 Current serial number in output stream: 936 I am trying to run what is effectively a traditional X Terminal, but as the hardware I am using has a 3D accelerated chipset it seems sensible to try to use it.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Tue Jun 12 10:09:30 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-22-generic, x86_64: installed rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2212] InstallationDate: Installed on 2018-05-31 (11 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: AZW S I ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=/dev/mapper/xubuntu--vg-root ro noresume SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 00.12 dmi.board.asset.tag: Default string dmi.board.name: AB1 dmi.board.vendor: IP3 Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr00.12:bd12/18/2017:svnAZW:pnSI:pvrDefaultstring:rvnIP3Tech:rnAB1:rvrDefaultst
[Bug 1776447] Re: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash
** Patch added: "debdiff for focal" https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323651/+files/xorg-server_1.20.6-1ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression
** Summary changed: - Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash + Xorg's Indirect GLX broken from upstream regression -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Xorg's Indirect GLX broken from upstream regression To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression
I've built this locally and tested it. While it improves matters, it is still incomplete to get IGLX working fully - there is a new crash at the point you close the IGLX-using application instead of immediately upon starting it. This fix is still warranted, however, because it does improve things. I'm going to go back to bisecting Xorg upstream to see if I can identify the new crash. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Xorg's Indirect GLX broken from upstream regression To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression
There are, thankfully, seemingly no regressions in unrelated areas :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Xorg's Indirect GLX broken from upstream regression To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression
The new crash backtrace: (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x7fb60370c899 in __GI_abort () at abort.c:79 #2 0x560aacd068c0 in OsAbort () at ../../../../os/utils.c:1351 #3 0x560aacd0c4f9 in AbortServer () at ../../../../os/log.c:879 #4 0x560aacd0d35a in FatalError (f=f@entry=0x560aacd40230 "Caught signal %d (%s). Server aborting\n") at ../../../../os/log.c:1017 #5 0x560aacd03c09 in OsSigHandler (unused=, sip=0x7ffd89b28470, signo=11) at ../../../../os/osinit.c:156 #6 OsSigHandler (signo=11, sip=0x7ffd89b28470, unused=) at ../../../../os/osinit.c:110 #7 0x7fb6038ef540 in () at /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x560aacd02cf3 in ResetCurrentRequest (client=client@entry=0x560aae67f0c0) at ../../../../os/io.c:560 #9 0x560aacccfa66 in DRI2WaitSwap (client=0x560aae67f0c0, pDrawable=) at ../../../../../../hw/xfree86/dri2/dri2.c:1082 #10 0x7fb6033fa5f1 in __glXDRIcontextWait (baseContext=, cl=0x560aae67f1d8, error=0x7ffd89b28aa8) at ../../../../glx/glxdri2.c:291 #11 0x7fb6033f29c7 in __glXForceCurrent (cl=0x560aae67f1d8, tag=tag@entry=1, error=error@entry=0x7ffd89b28aa8) at ../../../../glx/glxext.c:621 #12 0x7fb6033ee900 in xorgGlxMakeCurrent (client=0x560aae67f0c0, tag=1, drawId=, readId=0, contextId=, newContextTag=0) at ../../../../glx/glxcmds.c:616 #13 0x560aaccd378a in GlxFreeClientData (client=0x560aae67f0c0) at ../../../../glx/vndext.c:168 #14 0x560aacba838c in _CallCallbacks (pcbl=pcbl@entry=0x560aacdb2538 , call_data=call_data@entry=0x7ffd89b28b50) at ../../../../dix/dixutils.c:743 #15 0x560aacba2273 in CallCallbacks (call_data=0x7ffd89b28b50, pcbl=0x560aacdb2538 ) at ../../../../include/callback.h:83 #16 CloseDownClient (client=0x560aae67f0c0) at ../../../../dix/dispatch.c:3473 #17 0x560aacd045f1 in ospoll_wait (ospoll=0x560aad403a10, timeout=) at ../../../../os/ospoll.c:651 #18 0x560aaccfd3b3 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #19 0x560aacba2ca7 in Dispatch () at ../../../../include/list.h:220 #20 0x560aacba6f94 in dix_main (argc=12, argv=0x7ffd89b299b8, envp=) at ../../../../dix/main.c:276 #21 0x7fb60370e1e3 in __libc_start_main (main=0x560aacb90a00 , argc=12, argv=0x7ffd89b299b8, init=, fini=, rtld_fini=, stack_end=0x7ffd89b299a8) at ../csu/libc-start.c:308 #22 0x560aacb90a3e in _start () -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Xorg's Indirect GLX broken from upstream regression To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression
The refreshed patches fix both crashes. The first change is upstream commit e1fa3be [1] and the second change is from upstream PR 388 [2]. @Sponsors, this is now good to go from my point of view. [1] https://gitlab.freedesktop.org/xorg/xserver/commit/e1fa3beb2fe2519e69f859f0acdc68e5a770de27 [2] https://gitlab.freedesktop.org/xorg/xserver/merge_requests/388 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Xorg's Indirect GLX broken from upstream regression To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression
This debdiff for Bionic fixes the follow-on crash (on client close) that was unearthed by fixing the first crash (on client start). ** Patch added: "refreshed debdiff for bionic" https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323931/+files/xorg-server_1.19.6-1ubuntu4.4.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Xorg's Indirect GLX broken from upstream regression To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression
This debdiff for Focal fixes the follow-on crash (on client close) that was unearthed by fixing the first crash (on client start). ** Patch added: "refreshed debdiff for focal" https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323933/+files/xorg-server_1.20.6-1ubuntu2.debdiff ** Patch removed: "xorg-server-iglx.diff" https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323631/+files/xorg-server-iglx.diff ** Patch removed: "debdiff for bionic" https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323649/+files/xorg-server_1.19.6-1ubuntu4.4.debdiff ** Patch removed: "debdiff for eoan" https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323650/+files/xorg-server_1.20.5+git20191008-0ubuntu2.debdiff ** Patch removed: "debdiff for focal" https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323651/+files/xorg-server_1.20.6-1ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Xorg's Indirect GLX broken from upstream regression To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression
This debdiff for Eoan fixes the follow-on crash (on client close) that was unearthed by fixing the first crash (on client start). ** Patch added: "refreshed debdiff for eoan" https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323932/+files/xorg-server_1.20.5+git20191008-0ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Xorg's Indirect GLX broken from upstream regression To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression
The secondary crash doesn't occur without the first fix. You cannot reach it until the first fix is applied. However, I suppose it is in a different bit of code, but it is only reached when you use indirect GLX and prevents you using indirect GLX which is what this issue is attempting to fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Xorg's Indirect GLX broken from upstream regression To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression
both changes are now in upstream Xorg's repository, as PR388 was merged a few hours ago. So the changes in this debdiff are a backport of those to Bionic, Eoan and Focal (although if Focal were to sync with the upstream code then the delta won't be necessary going forward). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776447 Title: Xorg's Indirect GLX broken from upstream regression To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869475] Re: Window shrinks and menu disappears when other app is opened/closed to the dock
** Tags added: champagne -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869475 Title: Window shrinks and menu disappears when other app is opened/closed to the dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1869475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869747] [NEW] Recent changes have caused Xorg to fail to start. Possibly nvidia driver related.
Public bug reported: I am unsure where the problem stems, but changes since the 25th have caused my system to fail to initialise the Xorg display. The console remains operational for debugging. I am currently using ZFS snapshots to use the system as it was on the 25th of March 2020 because that is the last snapshot before this issue. This bug was captured using ubuntu-bug when booted into the broken (i.e. not working) latest snapshot of my filesystem. The versions of packages from the not broken (i.e. correctly working) earlier snapshot of my filesystem are: libnvidia-cfg1-440:amd64 440.64-0ubuntu2 libnvidia-common-440 440.64-0ubuntu2 libnvidia-compute-440:amd64 440.64-0ubuntu2 libnvidia-compute-440:i386 440.64-0ubuntu2 libnvidia-decode-440:amd64 440.64-0ubuntu2 libnvidia-decode-440:i386440.64-0ubuntu2 libnvidia-encode-440:amd64 440.64-0ubuntu2 libnvidia-encode-440:i386440.64-0ubuntu2 libnvidia-fbc1-440:amd64 440.64-0ubuntu2 libnvidia-fbc1-440:i386 440.64-0ubuntu2 libnvidia-gl-440:amd64 440.64-0ubuntu2 libnvidia-gl-440:i386440.64-0ubuntu2 libnvidia-ifr1-440:amd64 440.64-0ubuntu2 libnvidia-ifr1-440:i386 440.64-0ubuntu2 nvidia-compute-utils-440 440.64-0ubuntu2 nvidia-dkms-440 440.64-0ubuntu2 nvidia-driver-440440.64-0ubuntu2 nvidia-kernel-common-440 440.64-0ubuntu2 nvidia-kernel-source-440 440.64-0ubuntu2 nvidia-prime 0.8.14 nvidia-settings 440.64-0ubuntu1 nvidia-utils-440 440.64-0ubuntu2 xserver-xorg-video-nvidia-440440.64-0ubuntu2 $ lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-3ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 Date: Mon Mar 30 15:49:12 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes InstallationDate: Installed on 2020-03-03 (26 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 TH ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_7176ku@/vmlinuz-5.4.0-18-generic root=ZFS=rpool/ROOT/ubuntu_7176ku ro quiet splash intel_iommu=on vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22g dmi.board.asset.tag: Default string dmi.board.name: Z170X-UD5 TH-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22g:bd03/09/2018:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5TH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5TH-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z170X-UD5 TH dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug champagne focal nvidia regression reproducible ubuntu ** Tags added: champagne ** Tags added: nvidia -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869747 Title: Recent chan
[Bug 1869747] Re: Recent changes have caused Xorg to fail to start. Possibly nvidia driver related.
I've submitted it as bug #1869882 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869747 Title: Recent changes have caused Xorg to fail to start. Possibly nvidia driver related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1869747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869747] Re: Recent changes have caused Xorg to fail to start. Possibly nvidia driver related.
It looks like the stacktrace mentions AMDGPU related functions. For the record, I have three graphics devices in this box currently, one from each vendor to allow easily testing apps on each: nVidia, AMD, and Intel. The displays are currently only connected to the nVidia card's outputs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869747 Title: Recent changes have caused Xorg to fail to start. Possibly nvidia driver related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1869747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869747] Re: Recent changes have caused Xorg to fail to start. Possibly nvidia driver related.
Possible smoking gun: removing `intel_iommu=on` from the grub commandline successfully brings up gui desktop on boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869747 Title: Recent changes have caused Xorg to fail to start. Possibly nvidia driver related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1869747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869747] Re: Recent changes have caused Xorg to fail to start. Possibly nvidia driver related.
it's the correct reference, but I don't know whether it contains sensitive info or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869747 Title: Recent changes have caused Xorg to fail to start. Possibly nvidia driver related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1869747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869747] Re: Recent changes have caused Xorg to fail to start. Possibly nvidia driver related.
There are two whoopsies that my system has submitted, too: https://errors.ubuntu.com/oops/51e0231a-7138-11ea-98c4-fa163e102db1 https://errors.ubuntu.com/oops/5f9c714a-7352-11ea-aaf5-fa163e983629 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869747 Title: Recent changes have caused Xorg to fail to start. Possibly nvidia driver related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1869747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869882] Re: Xorg crashed with SIGABRT in __GI_raise()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869882 Title: Xorg crashed with SIGABRT in __GI_raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1869882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869747] Re: Recent changes have caused Xorg to fail to start. Possibly nvidia driver related.
OK, I've flipped it public. I had a browse through the attachments and my untrained eye can't see anything glaringly secret, so have at it :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869747 Title: Recent changes have caused Xorg to fail to start. Possibly nvidia driver related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1869747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870600] [NEW] permissions pane only shows currently-connected snap interfaces
Public bug reported: The applications applet in Gnome Control Center shows permissions that can be toggled on and off for installed applications and snap packages. When viewing a Snap package, only permissions that are currently enabled (interface is connected in Snap terms). Viewing the same Snap package's permissions in Gnome Software or the Snap Store Snap you can see that there are more permissions that can be enabled which are not currently. I have uploaded an example of both views to highlight the discrepency in a screenshot at: https://www.dropbox.com/s/zqr35hll94d37yg/photo_2020-04-03_19-49-06.jpg?dl=0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 3 19:48:07 2020 InstallationDate: Installed on 2020-03-03 (30 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug champagne focal ** Tags added: champagne -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870600 Title: permissions pane only shows currently-connected snap interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767428] [NEW] Selecting "mutiny" layout has caused the panel to gain a large margin
Public bug reported: Fresh install of Ubuntu Mate 18.04. Chose "mutiny" layout from mate- tweak (so this might be a mate-tweak but not mate-panel) and the panel is now correctly placed, but with a large right-hand margin making it appear too wide/twice the correct width. Screenshot: https://cloud.bowlhat.net/index.php/s/Tg7qSwpE2LE39Ht ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mate-panel 1.20.1-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Fri Apr 27 16:28:52 2018 InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mate-panel UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mate-panel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: - Fresh install of 18.04. Chose "mutiny" layout from mate-tweak (so this - might be a mate-tweak but not mate-panel) and the panel is now correctly - placed, but with a large right-hand margin making it appear too - wide/twice the correct width. + Fresh install of Ubuntu Mate 18.04. Chose "mutiny" layout from mate- + tweak (so this might be a mate-tweak but not mate-panel) and the panel + is now correctly placed, but with a large right-hand margin making it + appear too wide/twice the correct width. Screenshot: https://cloud.bowlhat.net/index.php/s/Tg7qSwpE2LE39Ht ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mate-panel 1.20.1-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Fri Apr 27 16:28:52 2018 InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mate-panel UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767428 Title: Selecting "mutiny" layout has caused the panel to gain a large margin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1767428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767428] Re: Selecting "mutiny" layout has caused the panel to gain a large margin
I've managed to get to the correct state by variously switching between hidpi/lodpi and cycling through a few different panel configurations, with the last one before it became unbroken being cupertino. I can't now reproduce the problem again to find a causal scenario. Sorry :-( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767428 Title: Selecting "mutiny" layout has caused the panel to gain a large margin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1767428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748678] Re: Intel graphics timeout, possibly caused wifi network to fail
I've tentatively marked it as fixed upstream, but as the bug occurs sporadically I might not have tested long enough to recreate the conditions which trigger the bug. I don't have reliable reproduction steps (read: any steps) so I will continue testing the upstream kernel in case I do hit it. ** Tags added: kernel-fixed-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748678 Title: Intel graphics timeout, possibly caused wifi network to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748678] Re: Intel graphics timeout, possibly caused wifi network to fail
Further, I've managed to cause two system lock-ups, which I do not have logs for because the lock-ups were so severe that the logging system didn't record the kernel logs before death. I therefore cannot attribute those two lockups to this issue for now. I've set-up netconsole now to try to gather logs from these lock-ups so that I can definitively attribute or rule them out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748678 Title: Intel graphics timeout, possibly caused wifi network to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752574] Re: Thunderbolt NULL pointer dereference in linux 4.15
Yes, this appears to be either a Firmware or Hardware issue. I have managed to get everything working via a process of removing other PCIe devices until it worked in Windows and running a firmware update at that point before putting all the other devices back. It's working correctly now. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752574 Title: Thunderbolt NULL pointer dereference in linux 4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768296] [NEW] Mate Terminal sets TERM to `xterm` thereby disabling vim color support
Public bug reported: Steps to reproduce: open mate-terminal $ sudo apt install vim $ vim test.txt Note that vim is in black and white only. $ export TERM=xterm-256color $ vim test.txt Now vim is in glorious technicolor :-) It seems that the TERM environment is set to a non-color mode by mate- terminal. -- Note: I use the `dracula` theme for vim - my dotfiles are at github.com/diddledan/dotfiles if you want to duplicate my setup. I use vcsh and there are submodules for my vim plugins and theme so: $ vcsh clone https://github.com/diddledan/dotfiles.git $ vcsh dotfiles submodule init $ vcsh dotfiles submodule update -- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mate-terminal 1.20.0-4 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Tue May 1 17:15:53 2018 InstallationDate: Installed on 2018-04-27 (3 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mate-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768296 Title: Mate Terminal sets TERM to `xterm` thereby disabling vim color support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-terminal/+bug/1768296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748678] Re: Intel graphics timeout, possibly caused wifi network to fail
** Tags removed: kernel-fixed-upstream ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748678 Title: Intel graphics timeout, possibly caused wifi network to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748678] Re: Intel graphics timeout, possibly caused wifi network to fail
I think the bug is still present upstream following more thorough usage. It seems sensitive to ambient light levels; using the computer in a darkened room (night) causes more intense and regular symptoms. It seems related to a bug I swear I filed a few years ago but didn't get any traction with, but I can't find any references to it. I recorded a video showing the screen flickering back then which I shared to show the physical manifestation - it's the same machine with similar behaviour but not as pronounced: https://youtu.be/zSP2EIAkkJg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748678 Title: Intel graphics timeout, possibly caused wifi network to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811444] [NEW] out-of-the-box monodoc-http fails to show documentation
Public bug reported: The out-of-the-box configuration for monodoc-http, which is pulled by installing mono-complete, does not find any documentation. It is configured to look for documentation at /mono/lib/monodoc-ios/ and reports an HTTP 500 error when trying to navigate to http://localhost:8084/monodoc. System.ArgumentException basedir Parameter name: Base documentation directory at '/mono/lib/monodoc-ios/' doesn't exist Description: HTTP 500.Error processing request. Details: Non-web exception. Exception origin (name of application or object): monodoc. Exception stack trace: at Monodoc.RootTree.LoadTree (System.String basedir, System.Boolean includeExternal) [0x00031] in <496c0b0510da4601a8fa1704154167ef>:0 at Mono.Website.Global.Application_Start () [0x0002d] in :0 at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (System.Reflection.MonoMethod,object,object[],System.Exception&) at System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00038] in <8f2c484307284b51944a1a13a14c0266>:0 Should the documentation path be changed? what to? Should we change monodoc-http to ensure it depends upon an appropriate documentation package to provide the path that the server is configured to serve? Or should we do both? ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: monodoc-http 4.2-2.2 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 11 17:06:25 2019 InstallationDate: Installed on 2018-12-13 (28 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: mono-tools UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mono-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811444 Title: out-of-the-box monodoc-http fails to show documentation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mono-tools/+bug/1811444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811444] Re: out-of-the-box monodoc-http fails to show documentation
Also affects xenial, though mono-complete does not install the monodoc- http package as a dependency. I needed to manually install monodoc-http after mono-complete to test whether it failed. ** Tags added: xenial ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811444 Title: out-of-the-box monodoc-http fails to show documentation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mono-tools/+bug/1811444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811444] Re: out-of-the-box monodoc-http fails to show documentation
Also affects bionic. Unlike xenial mono-complete DOES pull monodoc-http by default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811444 Title: out-of-the-box monodoc-http fails to show documentation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mono-tools/+bug/1811444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811444] Re: out-of-the-box monodoc-http fails to show documentation
Also affects disco. mono-complete DOES pull monodoc-http by default here, too. ** Tags added: disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811444 Title: out-of-the-box monodoc-http fails to show documentation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mono-tools/+bug/1811444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811444] Re: out-of-the-box monodoc-http fails to show documentation
** Bug watch added: Debian Bug tracker #919018 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919018 ** Also affects: mono-tools (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919018 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811444 Title: out-of-the-box monodoc-http fails to show documentation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mono-tools/+bug/1811444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916881] Re: Thunderbird unable to access external pgp keys
** Tags added: hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916881 Title: Thunderbird unable to access external pgp keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1916881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916881] Re: Thunderbird unable to access external pgp keys
** Tags added: champagne -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916881 Title: Thunderbird unable to access external pgp keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1916881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914825] [NEW] Impossible to override search paths in snap
Public bug reported: The snap configuration specifies `GLADE_CATALOG_SEARCH_PATH` and `GLADE_MODULE_SEARCH_PATH`. That prevents the user from adding their own entries into the search paths by setting the environment variable before executing the snap. apps: glade: command: usr/bin/glade extensions: [gnome-3-34] environment: GLADE_CATALOG_SEARCH_PATH: "$SNAP/usr/share/glade/catalogs" GLADE_MODULE_SEARCH_PATH: "$SNAP/usr/lib/$SNAPCRAFT_ARCH_TRIPLET/glade/modules" GLADE_PIXMAP_DIR: "$SNAP/usr/share/glade/pixmaps" ** Affects: glade (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914825 Title: Impossible to override search paths in snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glade/+bug/1914825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714941] Re: mounts should hint ignore
** Also affects: snapd Importance: Undecided Status: New ** Package changed: snapcraft (Ubuntu) => snapd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714941 Title: mounts should hint ignore To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1714941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921267] [NEW] Nextcloud Desktop requires login every time it starts
Public bug reported: Nextcloud Desktop does not save the user credential. Instead every time you launch the app it requires you to login again. Steps to reproduce: 1. Install nextcloud-desktop 2. Launch and login to your nextcloud instance 3. Close the app 4. Relaunch the app and notice you need to login again 5. Repeat steps 3 and 4 ad infinitum ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nextcloud-desktop 3.1.1-1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 24 20:38:04 2021 InstallationDate: Installed on 2020-07-16 (251 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nextcloud-desktop UpgradeStatus: Upgraded to hirsute on 2021-02-21 (31 days ago) ** Affects: nextcloud-desktop (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug champagne hirsute third-party-packages ** Tags added: champagne -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921267 Title: Nextcloud Desktop requires login every time it starts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1921267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921267] Re: Nextcloud Desktop requires login every time it starts
This might be specific to the Nextcloud server Snap package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921267 Title: Nextcloud Desktop requires login every time it starts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1921267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921267] Re: Nextcloud Desktop requires login every time it starts
I've had at least one report that indicates that this might be specific to my installation, and not a bug here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921267 Title: Nextcloud Desktop requires login every time it starts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1921267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871644] [NEW] Top corners of Firefox windows have weird black protrusions from the rounded edges
Public bug reported: Image to illustrate the problem is attached. All firefox windows on Wayland have a weird black protrusion from the top-left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug champagne focal wayland-session ** Attachment added: "top-right corner of a Firefox window on Wayland" https://bugs.launchpad.net/bugs/1871644/+attachment/5349674/+files/ffbug.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1871644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871644] Re: Top corners of Firefox windows have weird black protrusions from the rounded edges
I'm also seeing the pattern when logged-into X11 (note there is a difference in the image because in Wayland I have the monitor set to 200% scaling while in X11 it is set to 100%, so the images have different numbers of pixies for the bug) ** Attachment added: "top-right corner of a Firefox window on X11" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1871644/+attachment/5349685/+files/ffbug-x11.png ** Description changed: Image to illustrate the problem is attached. All firefox windows on Wayland have a weird black protrusion from the top-left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). + + EDIT: I have now checked X11 on my system and I see the same behaviour + as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Image to illustrate the problem is attached. All firefox windows on - Wayland have a weird black protrusion from the top-left and top-right - corners where yaru has curved the window corners, but something from - Firefox appears to not be being clipped by the theme. I need to double - check whether this appears on X11, but for now consider it Wayland only - until I report back, although oSoMoN has checked their system and they - don't see the behaviour (on X11). + Wayland (EDIT: and X11) have a weird black protrusion from the top-left + and top-right corners where yaru has curved the window corners, but + something from Firefox appears to not be being clipped by the theme. I + need to double check whether this appears on X11, but for now consider + it Wayland only until I report back, although oSoMoN has checked their + system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1871644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871644] Re: Top corners of Firefox windows have weird black protrusions from the rounded edges
** Attachment added: "with separate menu bar" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1871644/+attachment/5349702/+files/firefox-csdbug-separate-menubar.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871644] Re: Top corners of Firefox windows have weird black protrusions from the rounded edges
This is specific to the unification of the menu-bar into the title-bar through client-side decorations. I am about to attach two more screenshots that show the difference when the unification is disabled vs the default. ** Attachment added: "with menubar in title bar" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1871644/+attachment/5349701/+files/firefox-csdbug-unified-menubar.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871148] Re: services start before apparmor profiles are loaded
** Attachment added: "1871148-vm-no-varlib-mount_diddledan.svg" https://bugs.launchpad.net/apparmor/+bug/1871148/+attachment/5350256/+files/1871148-vm-no-varlib-mount_diddledan.svg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871148 Title: services start before apparmor profiles are loaded To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873565] [NEW] issue with TLS 1.2 session ticket handling as client during resumption
Public bug reported: Known upstream bug, that has been fixed upstream. There is an issue with session ticket handling in GnuTLS during session resumption. The issue is intermittent, but can eventually be reproduced by running: gnutls-cli --resume api.twitter.com 443 This is breaking the Cawbird Snap package based on Bionic/Core18. The issue affects both Bionic and Eoan. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnutls-bin 3.6.9-5ubuntu1.1 ProcVersionSignature: User Name 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Sat Apr 18 15:05:04 2020 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnutls28 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnutls Importance: Unknown Status: Unknown ** Affects: gnutls28 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic eoan uec-images ** Bug watch added: gitlab.com/gnutls/gnutls/issues #841 https://gitlab.com/gnutls/gnutls/issues/841 ** Also affects: gnutls via https://gitlab.com/gnutls/gnutls/issues/841 Importance: Unknown Status: Unknown ** Description changed: - Known upstream bug. There is an issue with session ticket handling in - GnuTLS during session resumption. + Known upstream bug, that has been fixed upstream. There is an issue with + session ticket handling in GnuTLS during session resumption. The issue is intermittent, but can eventually be reproduced by running: gnutls-cli --resume api.twitter.com 443 This is breaking the Cawbird Snap package based on Bionic/Core18. The issue affects both Bionic and Eoan. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnutls-bin 3.6.9-5ubuntu1.1 ProcVersionSignature: User Name 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Sat Apr 18 15:05:04 2020 ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=C.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash SourcePackage: gnutls28 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873565 Title: issue with TLS 1.2 session ticket handling as client during resumption To manage notifications about this bug go to: https://bugs.launchpad.net/gnutls/+bug/1873565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873565] Re: issue with TLS 1.2 session ticket handling as client during resumption
** Patch added: "The upstream diff from MR1087 fixing the issue." https://bugs.launchpad.net/gnutls/+bug/1873565/+attachment/5356468/+files/1087.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873565 Title: issue with TLS 1.2 session ticket handling as client during resumption To manage notifications about this bug go to: https://bugs.launchpad.net/gnutls/+bug/1873565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873565] Re: issue with TLS 1.2 session ticket handling as client during resumption
** Description changed: Known upstream bug, that has been fixed upstream. There is an issue with session ticket handling in GnuTLS during session resumption. The issue is intermittent, but can eventually be reproduced by running: gnutls-cli --resume api.twitter.com 443 + + When you trigger the bug the output will finish with the following two + lines: + + *** Fatal error: An unexpected TLS packet was received. + *** handshake has failed: An unexpected TLS packet was received. This is breaking the Cawbird Snap package based on Bionic/Core18. The issue affects both Bionic and Eoan. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnutls-bin 3.6.9-5ubuntu1.1 ProcVersionSignature: User Name 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Sat Apr 18 15:05:04 2020 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnutls28 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873565 Title: issue with TLS 1.2 session ticket handling as client during resumption To manage notifications about this bug go to: https://bugs.launchpad.net/gnutls/+bug/1873565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873804] Re: Website in debian packaging no longer valid, directing to dodgy site
Also affects - Xenial - Bionic - Disco - Eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873804 Title: Website in debian packaging no longer valid, directing to dodgy site To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wallch/+bug/1873804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873804] Re: Website in debian packaging no longer valid, directing to dodgy site
I confirm this is pointing at a domain holding page showing random links. The correct URL could be https://sourceforge.net/projects/wall- changer/ ** Changed in: wallch (Ubuntu) Status: New => Confirmed ** Tags added: bionic disco eoan xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873804 Title: Website in debian packaging no longer valid, directing to dodgy site To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wallch/+bug/1873804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838129] Re: Firefox crashreporter crashed with SIGSEGV in memcpy() when opening links from Visual Studio Code snap
Set back to confirmed. While there have been changes to VSCode, that isn't "Firefox (Ubuntu)". The Ubuntu codebase for Firefox has not received any commits to fix this. The likely outcome of this issue is that we set Firefox (Ubuntu) to invalid because it is a bug in VSCode, not Firefox on Ubuntu. ** Changed in: firefox (Ubuntu) Status: Fix Committed => Confirmed ** Bug watch added: github.com/microsoft/vscode/issues #85344 https://github.com/microsoft/vscode/issues/85344 ** Also affects: firefox via https://github.com/microsoft/vscode/issues/85344 Importance: Unknown Status: Unknown ** No longer affects: firefox ** Also affects: vscode via https://github.com/microsoft/vscode/issues/85344 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838129 Title: Firefox crashreporter crashed with SIGSEGV in memcpy() when opening links from Visual Studio Code snap To manage notifications about this bug go to: https://bugs.launchpad.net/vscode/+bug/1838129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820074] Re: Running glxgears with Indirect GLX crashes Xorg
The crash is in XorgLogOld.txt, and the backtrace reproduced here: [ 9027.274] (EE) Backtrace: [ 9027.274] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55b9210ba229] [ 9027.275] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7fdf6dcc4e1f] [ 9027.275] (EE) 2: /usr/lib/xorg/Xorg (ResetCurrentRequest+0xb) [0x55b9210b92ab] [ 9027.275] (EE) 3: /usr/lib/xorg/Xorg (DRI2WaitSwap+0x56) [0x55b921086716] [ 9027.275] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 9027.275] (EE) 4: /usr/lib/xorg/modules/extensions/libglx.so (?+0x0) [0x7fdf6c7faa20] [ 9027.276] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 9027.276] (EE) 5: /usr/lib/xorg/modules/extensions/libglx.so (?+0x0) [0x7fdf6c7f3010] [ 9027.276] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 9027.276] (EE) 6: /usr/lib/xorg/modules/extensions/libglx.so (?+0x0) [0x7fdf6c7eefd0] [ 9027.276] (EE) 7: /usr/lib/xorg/Xorg (dri3_send_open_reply+0xe2a) [0x55b92108b12a] [ 9027.277] (EE) 8: /usr/lib/xorg/Xorg (_CallCallbacks+0x34) [0x55b920f60be4] [ 9027.277] (EE) 9: /usr/lib/xorg/Xorg (CloseDownClient+0x5f) [0x55b920f5acbf] [ 9027.277] (EE) 10: /usr/lib/xorg/Xorg (OsCleanup+0x591) [0x55b9210bb021] [ 9027.277] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x1c3) [0x55b9210b3b93] [ 9027.277] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x10c) [0x55b920f5b72c] [ 9027.277] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3b6) [0x55b920f5f906] [ 9027.278] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7fdf6daea09b] [ 9027.278] (EE) 15: /usr/lib/xorg/Xorg (_start+0x2a) [0x55b920f4967a] [ 9027.278] (EE) [ 9027.278] (EE) Segmentation fault at address 0x8 [ 9027.278] (EE) Fatal server error: [ 9027.278] (EE) Caught signal 11 (Segmentation fault). Server aborting -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820074 Title: Running glxgears with Indirect GLX crashes Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1820074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820074] [NEW] Running glxgears with Indirect GLX crashes Xorg
Public bug reported: Replication Steps - sudo mv /usr/bin/Xorg /usr/bin/Xorg.real echo
[Bug 1820074] Re: Running glxgears with Indirect GLX crashes Xorg
Also crashes with nVidia using nouveau drivers (see attached log) ** Attachment added: "Xorg.0.log.old" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1820074/+attachment/5246195/+files/Xorg.0.log.old -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820074 Title: Running glxgears with Indirect GLX crashes Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1820074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826887] [NEW] Trousers cannot start when more than one file matches /dev/tpm*
Public bug reported: The init script in /etc/init.d/trousers includes the following test on line 32: if [ ! -e /dev/tpm* ] This will fail whenever the wildcard expansion of /dev/tpm* returns more than one result with a message similar to `/etc/init.d/trousers: 32: [: /dev/tpm0: unexpected operator`. On my Surface book I have two files which match /dev/tpm0 and /dev/tpmrm0. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: trousers 0.3.14+fixed1-1build1 Uname: Linux 5.0.9-surface-linux-surface x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 15:17:49 2019 InstallationDate: Installed on 2019-04-29 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: trousers UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.tcsd.conf: [inaccessible: [Errno 13] Permission denied: '/etc/tcsd.conf'] --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-29 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: trousers 0.3.14+fixed1-1build1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash Tags: disco Uname: Linux 5.0.9-surface-linux-surface x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True ** Affects: trousers (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-collected disco ** Tags added: apport-collected ** Description changed: The init script in /etc/init.d/trousers includes the following test on line 32: if [ ! -e /dev/tpm* ] This will fail whenever the wildcard expansion of /dev/tpm* returns more than one result with a message similar to `/etc/init.d/trousers: 32: [: /dev/tpm0: unexpected operator`. On my Surface book I have two files which match /dev/tpm0 and /dev/tpmrm0. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: trousers 0.3.14+fixed1-1build1 Uname: Linux 5.0.9-surface-linux-surface x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 15:17:49 2019 InstallationDate: Installed on 2019-04-29 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: trousers UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.tcsd.conf: [inaccessible: [Errno 13] Permission denied: '/etc/tcsd.conf'] + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu27 + Architecture: amd64 + DistroRelease: Ubuntu 19.04 + InstallationDate: Installed on 2019-04-29 (0 days ago) + InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) + Package: trousers 0.3.14+fixed1-1build1 + PackageArchitecture: amd64 + ProcEnviron: + LANGUAGE=en_GB:en + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_GB.UTF-8 + SHELL=/bin/bash + Tags: disco + Uname: Linux 5.0.9-surface-linux-surface x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826887 Title: Trousers cannot start when more than one file matches /dev/tpm* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/trousers/+bug/1826887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826887] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1826887/+attachment/5259990/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826887 Title: Trousers cannot start when more than one file matches /dev/tpm* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/trousers/+bug/1826887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826887] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1826887/+attachment/5259989/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826887 Title: Trousers cannot start when more than one file matches /dev/tpm* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/trousers/+bug/1826887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828500] Re: snapd fails always in Optimised Ubuntu Desktop images available in Microsoft Hyper-V gallery
@chipaca: seed.yaml from the 18.04.2 image in the Hyper-V Gallery $ cat /var/lib/snapd/seed/seed.yaml snaps: - name: core channel: stable file: core_6673.snap - name: gnome-3-26-1604 channel: stable/ubuntu-18.04 file: gnome-3-26-1604_82.snap - name: gnome-calculator channel: stable/ubuntu-18.04 file: gnome-calculator_352.snap - name: gnome-characters channel: stable/ubuntu-18.04 file: gnome-characters_206.snap - name: gnome-logs channel: stable/ubuntu-18.04 file: gnome-logs_57.snap - name: gnome-system-monitor channel: stable/ubuntu-18.04 file: gnome-system-monitor_70.snap - name: gtk-common-themes channel: stable/ubuntu-18.04 file: gtk-common-themes_1198.snap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828500 Title: snapd fails always in Optimised Ubuntu Desktop images available in Microsoft Hyper-V gallery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1828500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828500] Re: snapd fails always in Optimised Ubuntu Desktop images available in Microsoft Hyper-V gallery
followup: $ sudo snap info --verbose /var/lib/snapd/seed/snaps/*.snap | grep base: [sudo] password for dllewellyn: base: core18 base: core18 base: core18 base: core18 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828500 Title: snapd fails always in Optimised Ubuntu Desktop images available in Microsoft Hyper-V gallery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1828500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752307] Re: incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf
** Description changed: - Ubuntu 18.04. After xorg and nvidia proprietary drivers upgrades. + Ubuntu 18.04. After xorg and nvidia proprietary drivers upgrades. I rebooted and i get a black screen before the login screen I am unable to login. Thanks. + + -- + Added by diddledan: + -- + From the log file: + Parse error on line 5 of section OutputClass in file /usr/share/X11/xorg.conf.d/nvidia-drm-outputclass-ubuntu.conf + "Option" is not a valid keyword in this section. + + Commenting out this line proceeds to alert about the next line which is + also an "Option" line, and commenting that out moves the alert onto the + final line before EndSection. Commenting all three offending lines fixes + this particular issue. + + On diddledan's system, which may be an anomaly, Xorg then complains that libGL.so.1 is missing while loading /usr/lib/xorg/modules/extensions/libglx.so. + -- + End added by diddledan + -- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.25 Wed Jan 24 20:02:43 PST 2018 - GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.25 Wed Jan 24 20:02:43 PST 2018 + GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1) ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Wed Feb 28 04:47:12 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.25, 4.15.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: - NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. GM107 [GeForce GTX 750 Ti] [1043:84bb] + NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. GM107 [GeForce GTX 750 Ti] [1043:84bb] MachineType: Hewlett-Packard h8-1559 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=e7617605-fdbe-4cb6-9e67-00f9c8f45de2 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2012 dmi.bios.vendor: AMI dmi.bios.version: v8.10 dmi.board.name: 2AC8 dmi.board.vendor: Gigabyte dmi.board.version: 1.2 dmi.chassis.asset.tag: MXX30503QF dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvrv8.10:bd12/03/2012:svnHewlett-Packard:pnh8-1559:pvr:rvnGigabyte:rn2AC8:rvr1.2:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: h8-1559 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Description changed: Ubuntu 18.04. After xorg and nvidia proprietary drivers upgrades. I rebooted and i get a black screen before the login screen I am unable to login. Thanks. -- Added by diddledan: -- From the log file: Parse error on line 5 of section OutputClass in file /usr/share/X11/xorg.conf.d/nvidia-drm-outputclass-ubuntu.conf - "Option" is not a valid keyword in this section. + "Option" is not a valid keyword in this section. Commenting out this line proceeds to alert about the next line which is also an "Option" line, and commenting that out moves the alert onto the - final line before EndSection. Commenting all three offending lines fixes - this particular issue. + final line, "ModulePath", before EndSection. Commenting all three + offending lines fixes this particular issue. On diddledan's system, which may be an anomaly, Xorg then complains that libGL.so.1 is missing while loading /usr/lib/xorg/modules/extensions/libglx.so. -- End added by diddledan -- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: nvidia_
[Bug 1752307] Re: incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf
** Summary changed: - xorg + incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752307 Title: incompatible configuration in default nvidia-drm-outputclass- ubuntu.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1752307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752574] [NEW] Thunderbolt NULL pointer dereference in linux 4.15
Public bug reported: [0.994565] thunderbolt :09:00.0: enabling device ( -> 0002) [0.994957] thunderbolt :09:00.0: NHI initialized, starting thunderbolt [0.994961] thunderbolt :09:00.0: allocating TX ring 0 of size 10 [0.994983] thunderbolt :09:00.0: allocating RX ring 0 of size 10 [0.994999] thunderbolt :09:00.0: control channel created [0.994999] thunderbolt :09:00.0: control channel starting... [0.995000] thunderbolt :09:00.0: starting TX ring 0 [0.995018] thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) [0.995018] thunderbolt :09:00.0: starting RX ring 0 [0.995033] thunderbolt :09:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) [0.995046] thunderbolt :09:00.0: starting ICM firmware [0.995060] BUG: unable to handle kernel NULL pointer dereference at 0980 [0.995065] IP: pci_write_config_dword+0x5/0x30 [0.995066] PGD 0 P4D 0 [0.995068] Oops: [#1] SMP PTI [0.995069] Modules linked in: thunderbolt(+) ahci(+) ipmi_devintf libahci ipmi_msghandler video fjes(-) [0.995074] CPU: 6 PID: 214 Comm: systemd-udevd Not tainted 4.15.0-10-generic #11-Ubuntu [0.995075] Hardware name: Gigabyte Technology Co., Ltd. Z170X-UD5 TH/Z170X-UD5 TH-CF, BIOS F22d 12/01/2017 [0.995077] RIP: 0010:pci_write_config_dword+0x5/0x30 [0.995078] RSP: 0018:9e58839779e0 EFLAGS: 00010296 [0.995079] RAX: 4126 RBX: RCX: 0050 [0.995080] RDX: 0200 RSI: 0034 RDI: [0.995081] RBP: 9e5883977a18 R08: 0200 R09: 0330 [0.995082] R10: 2000 R11: R12: [0.995083] R13: 0050 R14: 92354e146f28 R15: [0.995084] FS: 7f86f2204440() GS:92357ed8() knlGS: [0.995085] CS: 0010 DS: ES: CR0: 80050033 [0.995086] CR2: 0980 CR3: 00080d1ce004 CR4: 003606e0 [0.995087] DR0: DR1: DR2: [0.995088] DR3: DR6: fffe0ff0 DR7: 0400 [0.995089] Call Trace: [0.995094] ? pcie2cio_write+0x40/0x80 [thunderbolt] [0.995098] icm_driver_ready+0x178/0x270 [thunderbolt] [0.995101] ? tb_ctl_start+0x50/0x90 [thunderbolt] [0.995105] tb_domain_add+0x79/0x100 [thunderbolt] [0.995108] nhi_probe+0x186/0x300 [thunderbolt] [0.995110] local_pci_probe+0x47/0xa0 [0.995111] pci_device_probe+0x145/0x1b0 [0.995114] driver_probe_device+0x31e/0x490 [0.995116] __driver_attach+0xa7/0xf0 [0.995118] ? driver_probe_device+0x490/0x490 [0.995119] bus_for_each_dev+0x70/0xc0 [0.995121] driver_attach+0x1e/0x20 [0.995123] bus_add_driver+0x1c7/0x270 [0.995124] ? 0xc03a9000 [0.995125] driver_register+0x60/0xe0 [0.995126] ? 0xc03a9000 [0.995128] __pci_register_driver+0x5a/0x60 [0.995131] nhi_init+0x2d/0x1000 [thunderbolt] [0.995133] do_one_initcall+0x52/0x1a0 [0.995135] ? _cond_resched+0x19/0x40 [0.995138] ? kmem_cache_alloc_trace+0xa6/0x1b0 [0.995140] ? do_init_module+0x27/0x209 [0.995141] do_init_module+0x5f/0x209 [0.995143] load_module+0x191e/0x1f10 [0.995146] ? ima_post_read_file+0x96/0xa0 [0.995148] SYSC_finit_module+0xfc/0x120 [0.995149] ? SYSC_finit_module+0xfc/0x120 [0.995151] SyS_finit_module+0xe/0x10 [0.995152] do_syscall_64+0x76/0x130 [0.995154] entry_SYSCALL_64_after_hwframe+0x21/0x86 [0.995155] RIP: 0033:0x7f86f1af3a49 [0.995156] RSP: 002b:7ffdedfa4478 EFLAGS: 0246 ORIG_RAX: 0139 [0.995157] RAX: ffda RBX: 559d3ffde790 RCX: 7f86f1af3a49 [0.995158] RDX: RSI: 7f86f17df0e5 RDI: 0005 [0.995159] RBP: 7f86f17df0e5 R08: R09: 7ffdedfa4590 [0.995160] R10: 0005 R11: 0246 R12: [0.995161] R13: 559d3ffedbf0 R14: 0002 R15: 559d3ffde790 [0.995162] Code: 87 c0 00 00 00 b9 04 00 00 00 48 89 e5 48 8b 40 20 e8 d0 45 72 00 5d c3 b8 87 00 00 00 c3 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 <48> 8b 8f 80 09 00 00 83 e1 01 75 0b 55 48 89 e5 e8 a6 ff ff ff [0.995182] RIP: pci_write_config_dword+0x5/0x30 RSP: 9e58839779e0 [0.995182] CR2: 0980 [0.995184] ---[ end trace 501c09dbb95a731e ]--- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC4D0', '/dev/snd/pcmC4D9p', '/dev
[Bug 1752111] Re: Xorg on Bionic doesn't start anymore
*** This bug is a duplicate of bug 1752307 *** https://bugs.launchpad.net/bugs/1752307 ** This bug has been marked a duplicate of bug 1752307 incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752111 Title: Xorg on Bionic doesn't start anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1752111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752307] Re: incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf
** Tags removed: single-occurrence -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752307 Title: incompatible configuration in default nvidia-drm-outputclass- ubuntu.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1752307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752307] Re: incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf
*** This bug is a duplicate of bug 1752053 *** https://bugs.launchpad.net/bugs/1752053 ** This bug has been marked a duplicate of bug 1752053 nvidia-390 fails to boot graphical display -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752307 Title: incompatible configuration in default nvidia-drm-outputclass- ubuntu.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1752307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752111] Re: Xorg on Bionic doesn't start anymore
*** This bug is a duplicate of bug 1752053 *** https://bugs.launchpad.net/bugs/1752053 ** This bug is no longer a duplicate of bug 1752307 incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf ** This bug has been marked a duplicate of bug 1752053 nvidia-390 fails to boot graphical display -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752111 Title: Xorg on Bionic doesn't start anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1752111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747281] Re: 18.04 nvidia driver installation failure
Likely duplicate of #1752053 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747281 Title: 18.04 nvidia driver installation failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1747281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752863] [NEW] libgl1 and libgl1-mesa-glx both provide libGL.so.1
Public bug reported: TJ in #ubuntu+1 suggested filing this as a bug. libgl1 from source package libglvnd and libgl1-mesa-glx from source package mesa both provide /usr/lib//libGL.so.1 root@u1804:~# apt-file list libgl1 libgl1: /usr/lib/x86_64-linux-gnu/libGL.so.1 libgl1: /usr/lib/x86_64-linux-gnu/libGL.so.1.0.0 libgl1: /usr/share/bug/libgl1/control libgl1: /usr/share/doc/libgl1/changelog.Debian.gz libgl1: /usr/share/doc/libgl1/copyright root@u1804:~# apt-file list libgl1-mesa-glx libgl1-mesa-glx: /usr/lib/x86_64-linux-gnu/mesa/ld.so.conf libgl1-mesa-glx: /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 libgl1-mesa-glx: /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1.2.0 libgl1-mesa-glx: /usr/share/bug/libgl1-mesa-glx/control libgl1-mesa-glx: /usr/share/bug/libgl1-mesa-glx/script libgl1-mesa-glx: /usr/share/doc/libgl1-mesa-glx/changelog.Debian.gz libgl1-mesa-glx: /usr/share/doc/libgl1-mesa-glx/copyright libgl1-mesa-glx: /usr/share/lintian/overrides/libgl1-mesa-glx ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgl1 (not installed) ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 2 12:54:46 2018 InstallationDate: Installed on 2017-12-01 (91 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: libglvnd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libglvnd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752863 Title: libgl1 and libgl1-mesa-glx both provide libGL.so.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1752863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 312722] Re: Connect to FTP with Login > Error "The file is not a directory"
This is a really old bug and the versions of Ubuntu it references are out of support now. Can you verify whether this is still a problem on Xenial (16.04) or Artful (17.10) and reset the bug to "confirmed" if you can recreate the issue. ** Changed in: nautilus (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/312722 Title: Connect to FTP with Login > Error "The file is not a directory" To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/312722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 708546] Re: USB keys freeze the computer
This is a really old bug and the versions of Ubuntu it references are out of support now. Can you verify whether this is still a problem on Xenial (16.04) or Artful (17.10) and reset the bug to "confirmed" if you can recreate the issue. ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/708546 Title: USB keys freeze the computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/708546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 716280] Re: gvfsd-metadata process pegs CPU while nautilus waits
This is a really old bug and the versions of Ubuntu it references are out of support now. Can you verify whether this is still a problem on Xenial (16.04) or Artful (17.10) and reset the bug to "confirmed" if you can recreate the issue. ** Changed in: nautilus (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/716280 Title: gvfsd-metadata process pegs CPU while nautilus waits To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/716280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 826283] Re: size of internal HDDs differs/wrong
This is a really old bug and the versions of Ubuntu it references are out of support now. Can you verify whether this is still a problem on Xenial (16.04) or Artful (17.10) and reset the bug to "confirmed" if you can recreate the issue. I've marked "Ubuntu Translations" as invalid because I do not believe it is related to the text translations. ** Changed in: nautilus (Ubuntu) Status: Confirmed => Incomplete ** Changed in: ubuntu-translations Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/826283 Title: size of internal HDDs differs/wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/826283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 874471] Re: Pendrive/USB drive cannot be open in folder
This is a really old bug and the versions of Ubuntu it references are out of support now. Can you verify whether this is still a problem on Xenial (16.04) or Artful (17.10) and reset the bug to "confirmed" if you can recreate the issue. ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/874471 Title: Pendrive/USB drive cannot be open in folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/874471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 823168] Re: gvfs webdav to common name
This is a really old bug and things may be different now. Can you verify whether this is still a problem on Xenial (16.04) or Artful (17.10) and reset the bug to "confirmed" if you can recreate the issue? ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/823168 Title: gvfs webdav to common name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/823168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1590831] Re: having prefix='' by default is non standard and confusing
Same problem snapping Corebird. I have no further information to evolve the discussion though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1590831 Title: having prefix='' by default is non standard and confusing To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1590831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721647] [NEW] qtCreator does not appear to have correct appstream data
Public bug reported: The gnome-software app does not show QTCreator in the Development Tools category, which suggests that the appstream data included in the QTCreator package is incorrect or missing? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: qtcreator 4.3.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 5 22:35:50 2017 InstallationDate: Installed on 2017-07-27 (70 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: qtcreator UpgradeStatus: Upgraded to artful on 2017-10-03 (2 days ago) ** Affects: qtcreator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session ** Description changed: The gnome-software app does not show QTCreator in the Development Tools - category, which suggests that the appstream data included in the package - is incorrect or missing? + category, which suggests that the appstream data included in the + QTCreator package is incorrect or missing? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: qtcreator 4.3.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 5 22:35:50 2017 InstallationDate: Installed on 2017-07-27 (70 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: qtcreator UpgradeStatus: Upgraded to artful on 2017-10-03 (2 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721647 Title: qtCreator does not appear to have correct appstream data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtcreator/+bug/1721647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748678] [NEW] Intel graphics timeout, possibly caused wifi network to fail
Public bug reported: My wifi network device stopped responding, unable to list any local wifi networks, which required turning off the adapter in settings and back-on again. while investigating I found the following in the dmesg output from the time the network device stopped responding. This is the only relevant message in recent history so I'm working on the assumption that somehow the intel gfx timeout knocked-onto the wifi device or the pci bus. === lcpsi of wifi card === 03:00.0 Network controller: Broadcom Limited BCM4331 802.11a/b/g/n (rev 02) Subsystem: Apple Inc. AirPort Extreme Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: wl Kernel modules: bcma, wl === lspci of gfx === 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 === relevant dmesg output === [ 7450.338278] pipe A vblank wait timed out [ 7450.338321] [ cut here ] [ 7450.338380] WARNING: CPU: 2 PID: 29153 at /build/linux-UKCsxy/linux-4.13.0/drivers/gpu/drm/i915/intel_display.c:12848 intel_atomic_commit_tail+0xf7d/0xf90 [i915] [ 7450.338380] Modules linked in: rfcomm scsi_transport_iscsi binfmt_misc veth ebtable_filter ebtables ip6t_MASQUERADE nf_nat_masquerade_ipv6 ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 xt_CHECKSUM xt_comment xt_tcpudp iptable_mangle unix_diag ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack libcrc32c l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel pppox mmc_block cmac bnep joydev applesmc input_polldev snd_hda_codec_hdmi snd_hda_codec_cirrus snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_seq_midi snd_seq_midi_event snd_rawmidi bcm5974 kvm_intel [ 7450.338405] btusb btrtl uvcvideo btbcm btintel kvm bluetooth irqbypass videobuf2_vmalloc videobuf2_memops snd_seq ecdh_generic videobuf2_v4l2 videobuf2_core videodev intel_cstate intel_rapl_perf media wl(POE) input_leds snd_seq_device snd_timer mei_me lpc_ich cfg80211 mei snd soundcore thunderbolt sbs shpchp sbshc apple_gmux acpi_als kfifo_buf industrialio apple_bl mac_hid iptable_filter ip6table_filter ip6_tables br_netfilter bridge stp llc arp_tables parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs xor raid6_pq algif_skcipher af_alg hid_generic hid_apple usbhid hid dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 sdhci_pci ahci aesni_intel libahci sdhci i2c_algo_bit aes_x86_64 drm_kms_helper crypto_simd glue_helper syscopyarea cryptd sysfillrect sysimgblt fb_sys_fops [ 7450.338442] drm video [ 7450.338445] CPU: 2 PID: 29153 Comm: kworker/u8:6 Tainted: P OE 4.13.0-32-generic #35-Ubuntu [ 7450.338446] Hardware name: Apple Inc. MacBookPro10,2/Mac-AFD8A9D944EA4843, BIOS MBP102.88Z.010B.B00.1708080805 08/08/2017 [ 7450.338478] Workqueue: events_unbound intel_atomic_commit_work [i915] [ 7450.338479] task: 9873194445c0 task.stack: b24909028000 [ 7450.338506] RIP: 0010:intel_atomic_commit_tail+0xf7d/0xf90 [i915] [ 7450.338507] RSP: 0018:b2490902bd90 EFLAGS: 00010286 [ 7450.338508] RAX: 001c RBX: RCX: [ 7450.338509] RDX: RSI: 98732f316578 RDI: 98732f316578 [ 7450.338509] RBP: b2490902be48 R08: 0001 R09: 04b1 [ 7450.338510] R10: b2490902bd90 R11: R12: 00066ddd [ 7450.338511] R13: 98731ab2 R14: 98731a7ea000 R15: 0001 [ 7450.338512] FS: () GS:98732f30() knlGS: [ 7450.338512] CS: 0010 DS: ES: CR0: 80050033 [ 7450.338513] CR2: 07ee6fce1000 CR3: 0001e440a006 CR4: 001606e0 [ 7450.338514] Call Trace: [ 7450.338519] ? dequeue_task_fair+0x49f/0x640 [ 7450.338521] ? wait_woken+0x80/0x80 [ 7450.338545] intel_atomic_commit_work+0x12/0x20 [i915] [ 7450.338547] process_one_work+0x1e7/0x410 [ 7450.338550] worker_thread+0x4b/0x420 [ 7450.338553] kthread+0x125/0x140 [ 7450.338554] ? process_one_work+0x410/0x410 [ 7450.338556] ? kthread_create_on_node+0x70/0x70 [ 7450.338558] ret_from_fork+0x1f/0x30 [ 7450.338560] Code: ff ff ff 48 83 c7 08 e8 52 f0 67 e0 4c 8b 85 70 ff ff ff 4d 85 c0 0f 85 7b fa ff ff
[Bug 1748678] Re: Intel graphics timeout, possibly caused wifi network to fail
** Description changed: My wifi network device stopped responding, unable to list any local wifi networks, which required turning off the adapter in settings and back-on again. while investigating I found the following in the dmesg output from the time the network device stopped responding. This is the only relevant message in recent history so I'm working on the assumption that somehow the intel gfx timeout knocked-onto the wifi device or the pci bus. === lcpsi of wifi card === 03:00.0 Network controller: Broadcom Limited BCM4331 802.11a/b/g/n (rev 02) - Subsystem: Apple Inc. AirPort Extreme - Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- - Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- - Kernel driver in use: wl - Kernel modules: bcma, wl + Subsystem: Apple Inc. AirPort Extreme + Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- + Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- + Kernel driver in use: wl + Kernel modules: bcma, wl === lspci of gfx === 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) - Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller - Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ - Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- - Kernel driver in use: i915 - Kernel modules: i915 + Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller + Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ + Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- + Kernel driver in use: i915 + Kernel modules: i915 - === relevant dmesg output === + === relevant dmesg output === [ 7450.338278] pipe A vblank wait timed out [ 7450.338321] [ cut here ] [ 7450.338380] WARNING: CPU: 2 PID: 29153 at /build/linux-UKCsxy/linux-4.13.0/drivers/gpu/drm/i915/intel_display.c:12848 intel_atomic_commit_tail+0xf7d/0xf90 [i915] [ 7450.338380] Modules linked in: rfcomm scsi_transport_iscsi binfmt_misc veth ebtable_filter ebtables ip6t_MASQUERADE nf_nat_masquerade_ipv6 ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 xt_CHECKSUM xt_comment xt_tcpudp iptable_mangle unix_diag ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack libcrc32c l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel pppox mmc_block cmac bnep joydev applesmc input_polldev snd_hda_codec_hdmi snd_hda_codec_cirrus snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_seq_midi snd_seq_midi_event snd_rawmidi bcm5974 kvm_intel [ 7450.338405] btusb btrtl uvcvideo btbcm btintel kvm bluetooth irqbypass videobuf2_vmalloc videobuf2_memops snd_seq ecdh_generic videobuf2_v4l2 videobuf2_core videodev intel_cstate intel_rapl_perf media wl(POE) input_leds snd_seq_device snd_timer mei_me lpc_ich cfg80211 mei snd soundcore thunderbolt sbs shpchp sbshc apple_gmux acpi_als kfifo_buf industrialio apple_bl mac_hid iptable_filter ip6table_filter ip6_tables br_netfilter bridge stp llc arp_tables parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs xor raid6_pq algif_skcipher af_alg hid_generic hid_apple usbhid hid dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 sdhci_pci ahci aesni_intel libahci sdhci i2c_algo_bit aes_x86_64 drm_kms_helper crypto_simd glue_helper syscopyarea cryptd sysfillrect sysimgblt fb_sys_fops [ 7450.338442] drm video [ 7450.338445] CPU: 2 PID: 29153 Comm: kworker/u8:6 Tainted: P OE 4.13.0-32-generic #35-Ubuntu [ 7450.338446] Hardware name: Apple Inc. MacBookPro10,2/Mac-AFD8A9D944EA4843, BIOS MBP102.88Z.010B.B00.1708080805 08/08/2017 [ 7450.338478] Workqueue: events_unbound intel_atomic_commit_work [i915] [ 7450.338479] task: 9873194445c0 task.stack: b24909028000 [ 7450.338506] RIP: 0010:intel_atomic_commit_tail+0xf7d/0xf90 [i915] [ 7450.338507] RSP: 0018:b2490902bd90 EFLAGS: 00010286 [ 7450.338508] RAX: 001c RBX: RCX: [ 7450.338509] RDX: RSI: 98732f316578 RDI: 98732f316578 [ 7450.338509] RBP: b2490902be48 R08: 0001 R09: 04b1 [ 7450.338510] R10: b2490902bd90 R11: R12: 00066ddd [ 7450.338511] R13: 98731ab2 R14: 98731a7ea000 R15: 0001 [ 7450.338512] FS: () GS:98732f30() knlGS:
[Bug 1746777] [NEW] Topicons extension's icons are not square
Public bug reported: The topicons extension showing apps using the appindicator library displays icons stretched vertically. The icons are the correct width but too tall. This leads to non-square icons and a distorted image. screenshot: https://imgur.com/a/caWli ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell-extension-appindicator 17.10.3 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 1 09:49:54 2018 Dependencies: InstallationDate: Installed on 2017-12-27 (35 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746777 Title: Topicons extension's icons are not square To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1746777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1252826] Re: Not compatible with the Django 1.6 default JSON_SESSION_SERIALIZER
one potential fix is to follow https://github.com/openid/python- openid/blob/master/openid/consumer/consumer.py#L90 which suggests that it can work in stateless mode by passing `None` to the `Consumer` constructor instead of the django session. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1252826 Title: Not compatible with the Django 1.6 default JSON_SESSION_SERIALIZER To manage notifications about this bug go to: https://bugs.launchpad.net/django-openid-auth/+bug/1252826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
