Public bug reported:
I enable Auto-hide Launcher.
Launcher auto-hides.
Moving the mouse to the top left corner does not reveal the launcher,
even with reveal sensitivity slid to maximum.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1
There's actually a second patch that is recommended as per the libreelec
tree:
https://github.com/LibreELEC/LibreELEC.tv/blob/9012226b40baa26241069317fdce6174935ca71b/packages/x11/driver/xf86
-video-nvidia-legacy/patches/xf86-video-nvidia-legacy-02-fix-
linux-5.1.patch
I've combined both
The additional patch needed can be modeled off the one at
https://bugs.archlinux.org/task/62610 labeled as nvidia-340xx.patch
I've updated the patch to be additive on top of the
buildfix_kernel_5.0.patch
** Patch added: "buildfix_kernel_5.1.patch"
This is the patch from debian for this issue. The driver seems to
compile fine with it.
** Patch added: "kmem_cache_create_usercopy.patch"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1802622/+attachment/5264097/+files/kmem_cache_create_usercopy.patch
--
You
Is 340.107 working for anyone with kernel 5.2?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1830049
Title:
nvidia-graphics-drivers-340 340.107-0ubuntu3 ADT test
I fixed the workaround script mentioned above here:
https://gist.github.com/satmandu/2f2da70a7a6bbbacdba01ef8fb8c18f4
This "works" on my system.
(dbus-send doesn't get the right info to work unless you give it the
info of the logged in user, which "machinectl shell" can do.
** Description changed:
Running on arm64 eoan build with kernel from raspberry pi folks (
4.19.71-v8-g6de367fd7 ) on a rpi4.
lsb_release -rd
Description:Ubuntu Eoan Ermine (development branch)
Release:19.10
-
- With wpasupplicant 2.29, wifi comes up on boot, but then
Public bug reported:
Running on arm64 eoan build with kernel from raspberry pi folks (
4.19.71-v8-g6de367fd7 ) on a rpi4.
lsb_release -rd
Description:Ubuntu Eoan Ermine (development branch)
Release:19.10
With wpasupplicant 2.29, wifi comes up on boot, but then drops out shortly
I'm still seeing this issue on resume from sleep today on my updated
19.10 setup with gnome-shell 3.34.0-1ubuntu1.
For what it is worth I also see this in my dmesg at boot:
[ 19.404177] gnome-shell[3485]: segfault at 18 ip 7f82407d4924 sp
7ffeb4e50f08 error 4 in
Here is the wpa supplicant log, gathered as per:
https://gist.github.com/wch/8305204#gistcomment-2477237
https://paste.ubuntu.com/p/Nm7G6STc22/
Note there are 3 sections.
The first section starts with "wpa_supplicant v2.6"
When I upgrade to 2.9 you can see this start with "wpa_supplicant v2.9"
Public bug reported:
Error reported during build, but dkms reports successful build.
Dkms build appears to complete successfully despite error reports, so
maybe only a cosmetic error during the build process?
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: nvidia-340 340.107-0ubuntu7
Public bug reported:
Installed ubuntu 19.10 onto a zfs bpool/rpool.
Installed zsys.
Did a "zpool import" of my existing zfs pools.
Rebooted.
The previously imported zpools are not imported at boot!
I am currently using this hacky workaround:
https://gist.github.co
/boot/grub/grub.cfg on BOOT doesn't seem to get populated, but there was
a grub.cfg.new which I was able to copy over.
Upon boot initramfs and kernel load from BOOT, but rpool fails to mount
and initram drops to shell.
doing this at initramfs prompt lets me login:
zpool import -R /root -N
I'm only getting a grub.cfg.new with useful information when I move
/etc/grub.d/10_linux_zfs to /etc/grub.d/10_linux_zfs.old
Default grub.cfg generated:
https://paste.ubuntu.com/p/snQKzDh8Kg/
With
https://paste.ubuntu.com/p/m5w4mTrPVQ/
Looks like /etc/grub.d/10_linux_zfs is the culprit here.
This patch was added to the nvidia-340 package in 340.107-0ubuntu5 as
per http://changelogs.ubuntu.com/changelogs/pool/restricted/n/nvidia-
graphics-drivers-340/nvidia-graphics-drivers-
340_340.107-0ubuntu7/changelog so this bug can be marked as resolved.
--
You received this bug notification
Great work kelebek333!
Has anybody heard about any usable patches to make this work on 5.7?
./include/linux/cpumask.h:266:9: warning: comparison of integer expressions of
different signedness: ‘int’ and ‘unsigned int’ [-Wsign-compare]
266 | (cpu) < nr_cpu_ids;)
| ^
The other patches are needed! For instance, there is display corruption
after sleep without one of the other patches.
(That has returned after the other patches were removed.)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Dmesg: https://paste.ubuntu.com/p/jNCR2qTKWQ/
Also maybe seeing this error:
Sep 15 13:37:15 nocturne gnome-control-c[2021]: file
../panels/display/cc-display-config.c: line 452 (get_fractional_scaling_key):
should not be reached
** Also affects: gnome-control-center (Ubuntu)
Importance:
Public bug reported:
Setting Fractional Scaling in the X11 Gnome Session is working fine. I
can set the 3000x2000 screen to 150%.
In the Gnome-Wayland Session, the Fractional Scaling Toggle doesn't
stick, and I don't see any fractional scaling percentage options show
up.
(Running a slightly
*** This bug is a duplicate of bug 1894593 ***
https://bugs.launchpad.net/bugs/1894593
** This bug has been marked a duplicate of bug 1894593
Fractional scaling switch doesn't work
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Public bug reported:
Seeing this on groovy installs after an update.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.36.4-1ubuntu2~build1
Uname: Linux 5.8.3-050803-generic x86_64
ApportVersion: 2.20.11-0ubuntu44
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Aug 25
This problem went away once I stopped using groovy-proposed and
(painfully) removed libffi8ubuntu1 and all dependencies which used it.
** Also affects: libffi (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- gnome-shell crashing with Wayland
+ gnome-shell crashing
@vorlon it is in the graphic which shows up in the GUI surrounding the checkbox
to enable -proposed
here:
https://wiki.ubuntu.com/Testing/EnableProposed?action=AttachFile=get=devoptions_1604.png
Thank you @knox for the clarification. This was largely my fault for doing a
's/focal/groovy/g' in
Fully aware that proposed is not supported, and that this may cause
instability.
Just trying to be helpful as per
https://wiki.ubuntu.com/Testing/EnableProposed
"Proposed updates are only for testing updates and providing development
feedback. Enabling this may introduce instability."
This bug
Public bug reported:
dkms.conf can be changed to just use
PATCH[0]="kernel-5.7.patch"
PATCH[1]="buildfix_kernel_5.8.patch"
with patches from archlinux:
https://aur.archlinux.org/cgit/aur.git/tree/buildfix_kernel_5.8.patch?h=nvidia-340xx
and
Note also a patch for kernel 5.9 there:
https://aur.archlinux.org/cgit/aur.git/tree/0003-kernel-5.9.patch?h
=nvidia-340xx
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
And apt installs are so much snappier now!
** Changed in: zsys (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zsys in Ubuntu.
https://bugs.launchpad.net/bugs/1882090
Title:
"ERROR couldn't
Public bug reported:
Have "ERROR couldn't connect to zsys daemon: timed out waiting for
server handshake" error every single time I run apt upgrade.
Example:
Fetched 312 kB in 2s (136 kB/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state
Attaching the nvidia 340.108 patch for kernel 5.10 from the
aforementioned link.
** Patch added: "nvidia-340.108-fix-5.10-kernel-compile"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+attachment/5443469/+files/nvidia-340.108-fix-5.10-kernel-compile.patch
This isn't solved until the patches are added to the ubuntu package,
right?
Please unmark it as solved until debian's package is imported into
ubuntu?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in
@albertomilone the debian nvidia-legacy-340xx-kernel-dkms (340.108-10)
package builds and installs successfully with the ubuntu 5.10.0-9.10
bootstrap kernel on amd64.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
This was an issue with corruption via an attempted AMDGPU-PRO driver
install.
Cleaning that out fixed the issue.
** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
Status: New => Invalid
** Summary changed:
- No Acceleration w/ amdgpu driver, needs rebuild for newer xorg?
+ Trying to
Public bug reported:
I'm seeing this in the xorg log:
[ 429.296] (II) Loading /usr/lib/xorg/modules/drivers/amdgpu_drv.so
[ 429.296] (II) Module amdgpu: vendor="X.Org Foundation"
[ 429.297]compiled for 1.20.11, module version = 21.0.0
[ 429.297]Module class: X.Org Video Driver
[
@vanvugt would you be willing to open an issue about this at
https://github.com/raspberrypi/linux/issues since this does look like a kernel
issue?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
I'm also seeing this same issue with a 5.15-rc4 kernel built from
https://github.com/raspberrypi/linux/tree/rpi-5.15.y
[ 408.326395] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]]
*ERROR* [CRTC:77:crtc-3] flip_done timed out
[ 408.326477] [drm:drm_crtc_commit_wait [drm]] *ERROR*
@jawn-smith, I'm using this display:
https://www.waveshare.com/5.5inch-hdmi-amoled-with-case.htm
with this cmdline.txt:
console=tty1 root=LABEL=writable rootfstype=ext4 rootwait quiet splash
video=HDMI-A-1:1080x1920M@60,rotate=90,panel_orientation=right_side_up
You can use https://launchpad.net/~kelebek333/+archive/ubuntu/nvidia-
legacy for support on jammy, but why bother?
The legacy Nvidia driver doesn't support Wayland with mutter, so you're
probably better off just using the nouveau driver anyways.
--
You received this bug notification because you
Here is some info from the crash file. More is available upon request.
(I opened a separate bug for the failure to upload the crash file at
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1988870 )
Title: gnome-shell crashed with SIGABRT in
__pthread_kill_implementation()
SourcePackage:
Public bug reported:
ssh to a host forwarding X, and open geany on remote host.
The entire session crashes, and I get logged out.
I'm assuming this is a mutter issue?
I have always been able to forward geany over ssh before.
Both machines are running ubuntu 20.10/dev/kinetic, with kernel
vanvugt,
Thanks! That resolved the issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-appindicator in
Ubuntu.
https://bugs.launchpad.net/bugs/1988315
Title:
gnome-shell crashed with SIGABRT
I'm seeing this as well.
I have a Wayland session, from which I ssh to another host and run geany
(forwarded over ssh).
Gnome-shell immediately crashes.
Interestingly, forwarding xterm from the remote host does not cause a
crash.
--
You received this bug notification because you are a member
41 matches
Mail list logo
