Does this need to get refiled against libgweather in order to get this
issue fixed? I can confirm that building local
libgweather_3.36.1-2~ubuntu20.04.1 packages with the four patches
referenced in comment 6 eliminates this bug.
--
You received this bug notification because you are a member of Ub
Patch to set APBS_PSIZE_LOCATION and APBS_PDB2PQR_LOCATION to the
locations used in the ubuntu pdb2pqr package for psize.py and pdb2pqr.py
scripts required by the APBS Tools 2.1 plugin.
** Patch added: "apbs_path_fix.diff"
https://bugs.launchpad.net/ubuntu/+source/pymol/+bug/1760449/+attachmen
To clarify, the steps to reproduce the functionality of the patched
pymol, the correct steps are described for Example 1 at
https://pymolwiki.org/index.php/Apbsplugin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Public bug reported:
The current pymol 1.8.4.0+dfsg-1build1 packaging fails to set the
APBS_PSIZE_LOCATION and APBS_PDB2PQR_LOCATION variables in
modules/pmg_tk/startup/apbs_tools.py which breaks the ability to perform
electrostatic surface calculations in the APBS Tools 2.1 plugin. The fix
is to
Public bug reported:
The nvidia-graphics-drivers-340 is essential to many users. For example,
on my MacPro 3,1 equipped with an EVGA GTX-680 Mac version graphic card,
the nvidia 360, 390 and 396 drivers all fail due to issues with the new
nvidia_drm module resulting in no video output on DVI and H
I believe that I have identified why the newer nvidia drivers which
depend on the new nvidia_drm kernel module fail on Mac hardware. That
new module depends on the ipmi modules. On Mac hardware, unsurprisingly,
the ipmi_si module fails to load and the ipmi device is not created.
Motherboards with i
Public bug reported:
When enabling the proprietary packages option on the Ubuntu installation
of xenial, bionic or cosmic x86_64 on a machine with both a wireless
card requiring the bcmwl-kernel-source package and an additional Nvidia
card present, the installation of the bcmwl-kernel-source packa
Public bug reported:
The bionic 18.04 installer used the grub-efi-amd64 package for grub on a
MacPro 3,1, however the cosmic 18.10 installer on the same machine
installs grub-pc instead (despite this being an EFI-64 machine).
** Affects: ubuntu
Importance: Undecided
Status: New
--
I am seeing the same problem with current cosmic 18.10. The stock
nouveau drivers work fine but using 'sudo ubuntu-drivers autoinstall' to
install either the nvidia-390 or nvidia-396 drivers produces a black
screen (backlighting completely off) after the ubuntu splash screen has
been displayed on r
** Summary changed:
- nvidia-340 installation issues need to be resolved and the package marked as
'tested'
+ nvidia-440 installation issues need to be resolved and the package marked as
'tested'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I can confirm, on a 2008 MacPro with Apple ROMed GTX680, that the nvidia
440 drivers bundled with the 20.04 beta release show the same behavior.
The Apple Cinema HD display LED comes on (indicating that the driver
loses contact with the display) as nvidia drivers are loaded and nvidia-
modeset exec
Public bug reported:
The current bionic installer is incorrectly installing snap versions of
gnome-calculator, gnome-characters and gnome-system-monitor from the
Gnome 3.26 release rather than the newer 3.28 normal deb packages
present in the bionic repo.
** Affects: ubuntu
Importance: Undec
Public bug reported:
The sysprof in eoan is still based on 3.32.0. Since the improvements to
sysprof are considered one of the significant improvements in gnome
3.34.0, it should be upgraded to the matching new version.
** Affects: sysprof (Ubuntu)
Importance: Undecided
Status: New
Note that the Gnome press release specifically mentions the sysprof
improvements.
https://www.gnome.org/press/2019/09/gnome-3-34-released/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845979
Title:
I was able to suppress these fatal crashes in plymouth that launched the
bug reporter on that package under current 18.10 Cosmic by building and
installing the 0.9.3-1ubuntu12 release on launchpad
https://launchpad.net/ubuntu/+source/plymouth
from the disco dingo proposed updates. There are no ob
I've seen the same issue with focal and System76 Stable PPA's
460.32.03-1pop0~1611601564~20.04~11a4029~dev nvidia packaging. All text
was corrupted after waking from suspend but it has only occurred once so
far.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
The installation of the new 3.8.2-0ubuntu2 update in Ubuntu 20.04
produces a series of warning...
Setting up python3 (3.8.2-0ubuntu2) ...
running python rtupdate hooks for python3.8...
/usr/share/hplip/base/utils.py:2060: SyntaxWarning: "is" with a literal. Did
you mean "=="
I ran into this problem under Ubuntu 20.04 Beta on my 2008 MacPro while
attempting to have the boot loader installed on the same drive as the
linux installation rather than the drive with my macOS installation.
Using the Custom Partitioning option to install / on /dev/sde2 (ext4)
and the device for
Public bug reported:
The current pymol package for 2.3.0+dfsg-1build1 has upstream's code to
disable shader support on nouveau drivers in /usr/lib/python3/dist-
packages/pymol/__init__.py. This causes pymol to render very slowly
compared to the non-free nvidia drivers. Disabling this code...
#
Note that this issue is always fixed in pymol trunk with...
https://github.com/schrodinger/pymol-open-
source/commit/af8c2e09c3ff45eaaeaac76a9fb89b9359340336
** Patch added: "do not blacklist "nouveau" driver"
https://bugs.launchpad.net/ubuntu/+source/pymol/+bug/1872109/+attachment/5351641/+
I can also confirm that the nvidia-340 package in 20.04 builds usable
kernel modules and works fine on the same 2008 MacPro with Mac rom'd
GTX680.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797791
I checked with pymol upstream and the 2.4.0 release, which will contain
the removal of the nouveau blacklisting, is slated for a May release.
This change isn't associated with any fixes in pymol but just a
recognition that recent nouveau now has usable shader support.
--
You received this bug not
diff --git a/modules/pymol/__init__.py b/modules/pymol/__init__.py
index fe299fbff..aaf978ade 100644
--- a/modules/pymol/__init__.py
+++ b/modules/pymol/__init__.py
@@ -332,8 +332,7 @@ def adapt_to_hardware(self):
print(" Disabling shaders for Intel Express graphics")
Public bug reported:
The most recent kernel updates resulted in...
ii linux-image-5.4.0-24-generic 5.4.0-24.28
amd64Signed kernel image generic
ii linux-image-generic5.4.0.24.29
amd64
Public bug reported:
The 1.0.0.61-2ubuntu3 steam package installs a steam which creates
generic icons on the Desktop for games. These Desktop game icons open in
gedit rather than launching when double clicked. One has to explicitly
right-click on the icon and select 'Allow Launching' for the Deskt
20.04 RC shows the same problem with the nvidia-340 drivers on a MacPro
3,1 with Mac ROM'd GTX680. The autologin is ignored and the greeter is
shown instead. While the login works fine at the point, restarting then
causes the system to hang rather than completing the restart.
--
You received this
Confirmed that setting 'WaylandEnable=false' in /etc/gdm3/custom.conf
under 20.04 has no impact on the autologin bug with nvidia-340.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845801
Title:
[nv
This bug is definitely triggered by the built kernel image loading the
nvidia drivers. The autologin failures and associated hangs on restarts
can be suppressed as follows...
1) Edit /etc/config/grub to remove 'splash' from GRUB_CMDLINE_LINUX_DEFAULT
2) Regenerate /boot/grub/grub.cfg with 'sudo up
Couldn't the nvidia packages all be modified to prune 'splash' from
/boot/grub/grub.cfg prior to rebuilding its kernel modules and thus
regenerating the initrd.img files?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Public bug reported:
Currently the Nvidia driver packages break the autologin feature of gdm3
whenever the 'splash' option is present on GRUB_CMDLINE_LINUX_DEFAULT in
/etc/config/grub.
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1845801
This breakage can be avoided by removing '
Public bug reported:
Steps to reproduce this bug...
1) Install the current nvidia-340 340.108-0ubuntu2 package.
2) Reboot to confirm nvidia graphics drivers are functional.
3) Reboot and edit the default kernel options to have 'single' before 'quiet
splash'
4) Boot the edited kernel options
The
Public bug reported:
On a 2008 MacPro with GTX680 under Ubuntu 20.04, selecting the recovery
mode from grub hangs on loading of the ramdisk with the Recovery Menu
dialog never appearing. This problem doesn't exist for a fresh install
of Ubuntu 18.04 updated to the current package updates. In that
If I remove 'nomodeset' from the grub kernel options for the recovery
kernel under 20.04, the hang in booting at loading the ramdisk is
eliminated. The recovery dialog appears as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Interestingly, installing the mainline Ubuntu 5.4.25 generic kernel
packages on Ubuntu 18.04 produces the same bug of nomodeset preventing
the recovery dialog from appearing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Oddly, so far I have not found a Ubuntu mainline kernel build that
doesn't show the problem.
5.3.18-050318-generic
5.4.0-050400-generic
5.4.25-050425-generic
5.4.28-050428-generic
5.6.6-050606-generic
all produce the hang at loading the ramdisk when booting the recovery
kernel with the default us
This problem doesn't exist for current Ubuntu 19.10 under its
5.3.0-46-generic kernel. The recovery mode boots fine on the same
hardware.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873965
Title:
This bug doesn't exist on the same hardware (a 2008 MacPro with Mac
ROM'd GTX680) under current Ubuntu 19.10 with the nvidia-340 package
installed. In that case, booting the default 5.3.0-46-generic kernel in
single user mode produces the expected prompt.
--
You received this bug notification bec
I have been able to eliminate the focal 5.4.0-26-generic kernel packages
as the origin of this bug. Manually installing those onto an
installation of Ubuntu 19.10, produced a fully functional boot. More
importantly the recovery mode boot from grub worked fine. So the problem
under 20.04 would appea
This issue extends to the daily desktop cd image for focal. When booted
from a usb memory stick and the safe graphics (which uses nomodeset) is
selected from grub, the screen remains black and never completes
booting. This issue doesn't exist with the current 19.10 cd images which
boot without issu
This offending package for bug is proving very difficult to pin down. I
have tried to sequentially regress all the packages that the recovery
kernel boot are likely to use back to their eoan versions on a 20.04
installation. In each case, I reinstalled the kernels afterwards to
insure that the init
I noticed that one of the changes in accountsservice
0.6.55-0ubuntu12~20.04.1 is...
* Add patch to not crash in the library when the daemon goes away
(Closes: #948228) (LP: #1843982)
Does this imply that the existing accountsservice 0.6.55-0ubuntu11
package in 20.04 will crash during upgrade
Public bug reported:
When updating Ubuntu 20.04 to the current proposed updates with the
accountsservice 0.6.55-0ubuntu12~20.04.1 update, the current gnome
session crashes out reproducibly into the the gdm3 greeter. At that
point, when you try to log back in, only the background color is
displayed
Done. I forget to note that I do have autologin set.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878611
Title:
accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into greeter
To manage not
I am seeing crashes back into the greeter when updating the current
accountsservice 0.6.55-0ubuntu11 package to the accountsservice
0.6.55-0ubuntu12~20.04.1 update in the focal proposed-updates. An
autologin is currently set for this machine. Since the changes describe
this fix as...
* Add patch
I can also confirm that if I disable autologin, reboot and then update
to the current packages in focal-proposed updates that the installation
of accountsservice 0.6.55-0ubuntu12~20.04.1 from the current
accountsservice 0.6.55-0ubuntu11 package completes normally.
--
You received this bug notific
I can also confirm that if I disable autologin, reboot and then update
to the current packages in focal-proposed updates that the installation
of accountsservice 0.6.55-0ubuntu12~20.04.1 from the current
accountsservice 0.6.55-0ubuntu11 package completes normally.
--
You received this bug notific
Looking at the syslog for the failed upgrade to accountsservice
0.6.55-0ubuntu12~20.04.1 with autologin enabled, I find that the first
failure appears at...
May 13 17:04:50 howarth-MacPro systemd[1]: Stopping Accounts Service...
May 13 17:04:50 howarth-MacPro systemd[1]: accounts-daemon.service: S
My experience with focal-proposed and accountsservice
0.6.55-0ubuntu12~20.04.1 has been that the update causes the currently
executing 'sudo apt-get update' to prematurely abort when the gnome
shell crashes. In my case, this left the linux-kerrnel packages only
half configured. My understanding is
The 33_fix_relative_paths_in_example_scripts.patch has to be regenerated
to cope with context changes in the pymol 2.1.0 sources.
** Patch added: "33_fix_relative_paths_in_example_scripts.patch"
https://bugs.launchpad.net/ubuntu/+source/pymol/+bug/1763992/+attachment/5115692/+files/33_fix_rela
The PyQt GUI for pymol appears as shown in the attached screen shot
under 18.04.
** Attachment added: "Screenshot from 2018-04-14 15-09-08.png"
https://bugs.launchpad.net/ubuntu/+source/pymol/+bug/1763992/+attachment/5115694/+files/Screenshot%20from%202018-04-14%2015-09-08.png
--
You receive
The 22_fix_pymol_import.patch has to be regenerated to cope with context
changes in the pymol 2.1.0 sources.
** Patch added: "22_fix_pymol_import.patch"
https://bugs.launchpad.net/ubuntu/+source/pymol/+bug/1763992/+attachment/5115691/+files/22_fix_pymol_import.patch
--
You received this bug
Public bug reported:
It is trivial to update the current pymol packaging in 18.04 to the
newest pymol 2.1.0 tarball at available on
https://sourceforge.net/projects/pymol/files/pymol/2/. The 2.1.0 release
now runs under a PyQt when present so the control file for the deb build
only needs...
The 02_test-suite.patch has to be regenerated to cope with context
changes in the pymol 2.1.0 sources.
** Patch added: "02_test-suite.patch"
https://bugs.launchpad.net/ubuntu/+source/pymol/+bug/1763992/+attachment/5115690/+files/02_test-suite.patch
--
You received this bug notification becau
Add additional 40_fix_apbstools_search_path.patch should be added to
solve the long standing issue of the apbstools plugin not being able to
find the required psize.py and pdb2pqr.py files from the pdb2pqr package
in ubuntu. Trivial to fix.
** Patch added: "40_fix_apbstools_search_path.patch"
Just to be clear, the changes required to the existing packaging are...
--- pymol-1.8.4.0+dfsg/debian/control 2016-10-20 11:33:21.0 -0400
+++ pymol-2.1.0+dfsg/debian/control 2018-04-14 13:57:37.0 -0400
@@ -24,6 +24,8 @@
Package: pymol
Architecture: any
Depends: python-nump
Public bug reported:
The nautilus handling of removable media capable of automated insertion
is flawed. On a MacPro 3,1, running bionic for instance, the first use
of the eject key on the keyboard ejects the SuperDrive DVD tray but the
second use of the eject key doesn't cause the tray to auto-ins
Public bug reported:
Description of problem: Currently the existing Ubuntu Live installers can't
boot from a USB key on legacy Apple hardware like a MacBook Pro 2,1 which lacks
EFI-64 firmware with only EFI-32 firmware. The next Ubuntu release should adopt
the same mixed-mode multi-arch install
Public bug reported:
Currently when the ubuntu-software program offers the user OS Updates
which promise security and performance improvements, it is completely
opaque about what these will encompass. Is it a minor system utility or
a full kernel upgrade? There needs to be a tab to click on that p
I have crafted a update-efi-booter script which automates the booting
approach described in
http://courses.cms.caltech.edu/cs171/materials/pdfs/How_to_Dual-
Boot_OSX_and_Ubuntu.pdf where the /boot/efi partition on Macs are kept
as HFS+ so that the boot selector can be made aware of the bootable
boo
I have successfully installed Debian Jessie using the multi-arch netinst
iso
https://cdimage.debian.org/debian-cd/current/multi-arch/iso-
cd/debian-8.6.0-amd64-i386-netinst.iso
which leverages the new mixed mode support described in
https://wiki.debian.org/UEFI
Support for mixed-mode systems: 64
I would also strongly suggest that we add code similar to that posted on
pastebin for journal_disable.c at http://pastebin.com/7rvxR38d to the
mactel-boot package as well as this script so we can add the additional
lines...
# make sure HFS+ Journaling is disabled
disable_journal `cat /proc/mounts
Tested on a fresh install of Ubuntu 16.10 x86_64 by...
gcc -o disable_journal disable_journal.c
chmod ugo+x update-efi-booter
install disable_journal update-efi-booter /usr/local/bin
identify the device that the /boot/efi partition is mounted on, umount
it and then use gdisk to delete that parti
*** This bug is a duplicate of bug 1595765 ***
https://bugs.launchpad.net/bugs/1595765
I can confirm that the instructions at
http://wiki.beyondlogic.org/index.php?title=TPLINK_Archer_T4U_RTL8812au_Linux_Drivers
produce a usable rtl8812au.ko under both the 4.8.0-22-generic and
4.8.0-32-generic
Public bug reported:
The libomp5 and libomp-dev packages available in arty for installation
against the release clang-5.0 package are still based on the 4.0.1-4
packaging. The libomp5 and libomp-dev packages need to be kept in sync
with the latest official release of llvm (5.0.0) in order to be fu
Public bug reported:
The Ubuntu tomcat8 server fails to properly serve the MetaboAnalyst
server application when installed as described upstream at
http://www.metaboanalyst.ca/faces/docs/Resources.xhtml. A manual
installation of a glassfish4 4.1.2 server has no problems serving the
same MetaboAnal
The logs from a bzip2 tar archive of the /var/lib/tomcat8/logs directory
contents after the tomcat8 and MetaboAnalyst installation to run as
tomcat8. The logs show the messages logged from tomcat8 when the failed
connection attempt at the URL...
http://localhost:8080/MetaboAnalyst/
...produces th
Public bug reported:
On a MacPro 3,1 with a stock installation of Ubuntu 16.10 amd64 from
ubuntu-16.10-desktop-amd64.iso , the mounted volumes on the Dock of the
Desktop are incorrect. The machine has three SATA drives installed. Two
of these are formatted as RAID-1 slices of an AppleRAID Journal
Why is ubuntu bothering to duplicate the virtualbox packaging when
Oracle appears to be both more current and supporting all of the Ubuntu
releases in their own repo?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
I see the same problem on Ubuntu 16.10 but using the Oracle
virtualbox-5.1 packaging for 5.1.10 works perfectly after installing the
dkms package and running /sbin/vboxconfig to generate the kernel
modules.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Public bug reported:
While looking at the various Linux distributions as a replacement OS on
a MacBook Pro 2,1 with EFI-32, I was pleasantly surprised that Fedora 24
could produce a bootable system on an internal disk which was
partitioned as MBR with just a single spare partition of empty space.
Why not take the path of least resistance here? Just make the system-
config-samba have an dependency on the installation of the libuser
package and the problem goes away, no? It certainly worked for me
tonight with a fresh installation of 16.10.
Note from...
http://packages.ubuntu.com/yakkety/sy
Public bug reported:
I consider this bug extremely insidious as it can ruin the performance
of linux while virtualbox is running. While setting up Oracle's
virtualbox-5.1 on my MacPro 3,1 under Ubuntu 16.10, I was puzzled by the
extremely bad system performance that I was seeing. Finally I realize
FYI, I strongly urge the interested Ubuntu developers to carefully read
the following thread in the fedora-devel mailing list where the Fedora
developers discuss the specific changes made and known behaviors of
booting on EFI-32 with Fedora 25...
https://lists.fedoraproject.org/archives/list/de...
After struggling this for the better part of a week, the best solution I
have found is to abandon the Ubuntu 16.10 installers entirely and use
debian-8.6.0-amd64-i386-netinst.iso which works perfectly on a MacBook
Pro 3,1. A workable approach I believe is to do as bare-bones an
installation as poss
err, that should have been MacBook Pro 2,1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647184
Title:
Ubuntu should install mach_kernel and System directory in boot/EFI
like Fedora 24 and fallba
I finally got this to work. The only real requirement for this to work
is the the a boot partition that is FAT32 was exist for the Mac EFI
firmware to see and that this partition must contain the fake
mach_kernel file and a System/Library/CoreServices/SystemVersion.plist
file containing...
Public bug reported:
Under both current 22.04.4 and 23.10, the command 'sudo do-release-
upgrade -d' is non-functional and can't upgrade a system to the current
24.04 development release. I've never witnessed this behavior in the
past and assume that the development release has been hidden from th
Public bug reported:
The linux-signatures-nvidia-6.8.0-22-generic package only contains
nvidia drivers as new as nvidia-driver-450 despite the current
additional drivers in Software & Updates having nvidia-driver-550 as the
tested topmost choice.
** Affects: linux-restricted-signatures (Ubuntu)
Public bug reported:
The python 3.12 in use on noble causes pymol in the pymol
2.5.0+dfsg-1build6 to fail on the command line with the error...
Traceback (most recent call last):
File "", line 189, in _run_module_as_main
File "", line 112, in _get_module_details
File "/usr/lib/python3/dist-
I am a bit confused as to why simply commenting out the import of imp
works as find_module() should be removed in python 3.12 under Ubuntu
24.04. There doesn't appear to be any fixes yet upstream in Debian Sid
which uses the same 22_fix_pymol_import.patch. Debian doesn't have a bug
report yet again
It appears that the following does find the pymol module when executed
within python3.12.
% python3.12
Python 3.12.2 (main, Feb 10 2024, 11:33:20) [Clang 15.0.0 (clang-1500.1.0.2.5)]
on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from importlib.util import fi
Public bug reported:
While I am unclear which package update impacted the video drivers
detected by ubuntu-drivers, the nvidia 545 and nvidia 550 video drivers
are no longer shown as an option on NVIDIA GeForce GTX 1050 video card.
I can understand the removal of the nvidia 545 drivers as the curr
Public bug reported:
Often when logging back into after workstation sleeping, the dropbox
icon in the top menu bar is replaced with three dots instead of its
normal dropbox icon.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nautilus-dropbox 2019.02.14-1ubuntu1
ProcVersionSignature: Ubunt
** Attachment added: "screen shot of the three dot icon instead of the expected
dropbox one."
https://bugs.launchpad.net/ubuntu/+source/nautilus-dropbox/+bug/1971558/+attachment/5586601/+files/Screenshot%20from%202022-05-04%2006-01-59.png
--
You received this bug notification because you are
** Attachment added: "screen shot of the three dot icon instead of the expected
dropbox one."
https://bugs.launchpad.net/ubuntu/+source/nautilus-dropbox/+bug/1971558/+attachment/5586602/+files/Screenshot%20from%202022-05-04%2006-01-59.png
--
You received this bug notification because you are
The changes made to linux-firmware 1.201.1 on impish has destablized use
of a Gigabyte GC-WB867D-I REV Bluetooth 4.0/Wireless AC/B/G/N Band Dual
Frequency 2.4Ghz/5.8Ghz Expansion Card. Under the new linux-firmware
1.201.1, no wifi is available under Gnome in about 80-90% of the boots.
Under the pri
So this isn't a single bug but multiple points of failure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969243
Title:
gdm 42.0-1ubuntu4 no longer shows Wayland option
To manage notifications abou
gdm3 42.0-1ubuntu6 is in proposed and Wayland is apparently going to be
unavailable for the 22.04 LTS release. Cnet is going to have to rewrite
its review.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Looks like Fedora 36 won't have this problem with Wayland on Nvidia
because their associated rpmfusion packaging for xorg-x11-drv-nvidia
adds a nvidia-power-management.conf with the following contents into
/etc/modprobe.d...
#
# Save and restore all video memory allocations.
options nvidia NVreg_P
What is Ubuntu's definition of a 'stable release update' in this case
regarding Nvidia driver support for Wayland? Does this imply, as I fear,
an update only after the fix has been deployed in another full Ubuntu
release? If so, this would imply that we won't have Nvidia Wayland
support until 22.10
"gdm3 (42.0-1ubuntu6) jammy; urgency=medium
* Fix Wayland no longer being available for everyone
- Fix by adding a separate revert patch instead of trying to
rebase the cherry-picked patches (LP: #1969243)
* Please note that Wayland is not currently available for
systems using th
As importantly, how can we even know whether the Nvidia power
mananagement support is broken or working if the Ubuntu Nvidia packaging
never starts nvidia-hibernate.service, nvidia-powerd.service, nvidia-
resume.service and nvidia-suspend.service like rpmfusion on Fedora. Of
course, we would need a
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969243
Title:
gdm 42.0-1ubuntu4 no longer shows Wayland option
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/
How can we even know whether the Nvidia power mananagement support is
broken or working if the Ubuntu Nvidia packaging never starts nvidia-
hibernate.service, nvidia-powerd.service, nvidia-resume.service and
nvidia-suspend.service like rpmfusion on Fedora? Of course, we would
need a /etc/modprobe.d
Public bug reported:
The current /lib/udev/rules.d/61-gdm.rules has a broken rule for
detecting the presence of NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1.
This issue can be seen by adding a file /etc/modprobe.d/nvidia-power-
management.conf containing the line...
options nvidia NVreg_PreserveVi
I am wondering if the use of escaped quotes in the failing rule of
/lib/udev/rules.d/61-gdm.rules is really being honored. There don't seem
to be any other examples of deployed udev rules which actually use such
escaped quotes.
--
You received this bug notification because you are a member of Ubu
I have found that current /lib/udev/rules.d/61-gdm.rules can be fixed by
swapping the order of the single and escaped double quotes from...
IMPORT{program}="/bin/sh -c \"sed -e 's/: /=/g' -e
's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e 's/[[:lower:]]/\U&/g' -e
's/^/NVIDIA_/' /proc/driver/nvidia/
Note that I stumbled onto the above fix after noticing the example shown
for the udev escaped quoting support showed an example with double
quotes surrounded by single quotes which in turn surrounded escaped
double quotes...
https://git.alternativebit.fr/NinjaTrappeur/Systemd/commit/7e760b79ad143b
Daniel, I disagree. This bug is actually about the fact that the test
crafted in /lib/udev/rules.d/61-gdm.rules doesn't parse as expected in
udev. We also should probably file a bug report against upstream udev as
the changes added to support escaped quotes in #6890 aren't robust
enough.
--
You r
Public bug reported:
The cheese application produces a corrupted display under Ubuntu 22.04
with a Logitech C525 webcam. When started from the command line, cheese
produces repeated warnings of the form...
(cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being
dropped.: ../li
1 - 100 of 122 matches
Mail list logo
