Any news on rolling back 418 to it's own branch ? There are updates to
the 418 branch that were never released by the ppa :
The PPA had the 418.56, while nVidia released the 418.88 version.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-
Any news on rolling back 418 to it's own branch ? There are updates to
the 418 branch that were never released by the ppa :
The PPA had the 418.56, while nVidia released the 418.88 version.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-418 in Ubuntu.
http
The problem comes from the 418 package being a transitional package to
430 in the PPA, maintainers not rolling back 418 package to actual
driver.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-418 in Ubuntu.
https://bugs.
It is false, transitional package are used even while the next branch
would make the user unable to use the GPU due to nVidia dropping support
for it.
Example with 418 and 430.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-driv
Kernel 5.3 officially released by Canonical does not work with 418.56 from this
PPA.
Branch 430 does not support my GPU.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-418 in Ubuntu.
https://bugs.launchpad.net/bugs/18279
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-418 in Ubuntu.
http
Check https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-418/+bug/1838875
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-418 in Ubuntu.
https://bugs.launchpad.net/bugs/1853758
Title:
Forcing incompatibl
There are, thankfully, seemingly no regressions in unrelated areas :-)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1776447
Title:
Xorg's Indirect GLX broken from upstream regression
T
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.
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
** Also affects: nvidia-settings (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-settings (Ubuntu Bionic)
Status: New => In Progress
** Changed in: nvidia-settings (Ubuntu Bionic)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: nvidi
I'm seeing this issue for the first time in Ubuntu 19.10 (eoan).
Both the screensaver and the power manager have preferences for locking.
I see this issue when both are enabled.
Under: Screensaver Preferences -> Lock Screen, I see:
Enable Lock Screen: Y/N
Lock Screen with Screensaver: Y/N
Lock
Stephen, do you use xfce4-screensaver? Is the other lock screen from
light-locker. You do not have to use both. Check your autostarts.
Purging light-locker changes power manager settings UI, but there is
still checkbox for locking.
--
You received this bug notification because you are a member of
Hello Alberto, or anyone else affected,
Accepted nvidia-graphics-drivers-340 into eoan-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-340/340.108-0ubuntu0.19.10.1 in a few hours,
and then in the -proposed repository.
Please h
Public bug reported:
Running up-to-date Ubuntu-18.04.3 with kernel 5.3.0-26 on a Dell
Optiplex 7060 with an i7-8700 CPU and Intel UHD Graphics 630 (Coffeelake
3x8 GT2).
I had chrome, slack and vmware-player running in Gnome. While doing some
git clone, screen+mouse+keyboard froze for 2 minutes af
Hello Alberto, or anyone else affected,
Accepted nvidia-graphics-drivers-340 into bionic-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-340/340.108-0ubuntu0.18.04.1 in a few hours,
and then in the -proposed repository.
Please
** Changed in: xorg-server
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1776447
Title:
Xorg's Indirect GLX broken from upstream regression
To manage
The eoan-proposed repository didn't work for me. This is what apt-cache
says:
mesa-opencl-icd:
Installed: 19.2.8-0ubuntu0~19.10.1
Candidate: 19.2.8-0ubuntu0~19.10.1
Version table:
*** 19.2.8-0ubuntu0~19.10.1 500
500 http://ca.archive.ubuntu.com/ubuntu eoan-proposed/universe amd64
P
Installed from the proposed repository the version 19.2.8-0ubuntu0~19.10.1
Works great on:
Operating System: Kubuntu 19.10
KDE Plasma Version: 5.16.5
KDE Frameworks Version: 5.62.0
Qt Version: 5.12.4
Kernel Version: 5.3.0-29-generic
OS Type: 64-bit
Processors: 4 × AMD A8-6500T APU with Radeon(tm) H
wrong package, this is not related to mesa
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libclc in Ubuntu.
https://bugs.launchpad.net/bugs/1860042
Title:
openCL application gives error after update
To manage notifications about this bug go
check libclc-amdgcn instead
in any case, this has been verified on eoan already, bionic needs to be
verified too
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libclc in Ubuntu.
https://bugs.launchpad.net/bugs/1860042
Title:
openCL applicati
Here's the prevboot.
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1861043/+attachment/5323859/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https:
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.debdif
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.
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
*
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]
I can't find any existing reports of that secondary crash, but ideally
it would not usually be part of the fix here...
I guess it's OK if the secondary crash was impossible without the first
fix. If it wasn't then ideally a new bug should be opened to describe
that and both bugs mentioned in the p
Thanks. Yes the messages about "Memory pressure relief" sound unusual.
I've never seen that before.
Don't worry about the inability to switch VTs. That's not part of the
bug, that's just because switching VTs is the responsibility of the
currently active display server. If Xorg has frozen then you
*** This bug is a duplicate of bug 1841718 ***
https://bugs.launchpad.net/bugs/1841718
was fixed for me with common Ubuntu updates related to bug #1841718.
** This bug has been marked a duplicate of bug 1841718
[radeon] Rendering of combo boxes and tooltips is broken
--
You received this
30 matches
Mail list logo