Yes, merged yesterday: https://github.com/PackageKit/PackageKit/pull/508
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943189
Title:
"cannot refresh whilst network offline" bug
To manage
Uploaded fix in 2.2.3 bugfix release from upstream
** Changed in: studio-controls (Ubuntu)
Assignee: Len Ovens (len-ovenwerks) => Erich Eickmeyer (eeickmeyer)
** Changed in: studio-controls (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notifi
** Changed in: studio-controls (Ubuntu)
Importance: High => Critical
** Changed in: studio-controls (Ubuntu)
Status: New => Triaged
** Changed in: studio-controls (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
$ studio-controls
install path: /usr
Config file: /home/ubuntu-studio/.config/autojack/autojack.json
Traceback (most recent call last):
File "/usr/bin/studio-controls", line 1836, in
us = StudioControls()
File "/usr/bin/studio-controls", line 550, in __init__
Public bug reported:
Just a few weeks ago, I noticed the .deb version of Visual Studio Code
crashing upon launch. I also noticed Element (matrix client) also would
crash. The only thing these applications have in common is electron. I
was hoping this would get noticed by someone and that the
This is the incorrect package. Slack desktop (the chat/collaboration
app) is not in the repositories. Unfortunately, I'm going to have to
invalidate this bug report as Slack is unsupported. The slack package in
Ubuntu is a different application altogether.
That said, there is an issue affecting
** Patch added: "Fix for previous patch"
https://bugs.launchpad.net/ubuntu/impish/+source/packagekit/+bug/1943189/+attachment/5526756/+files/11-fix-network-online-patch.patch
** Changed in: packagekit (Ubuntu Impish)
Assignee: Erich Eickmeyer (eeickmeyer) => Julian
ess
** Changed in: packagekit (Ubuntu Impish)
Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer)
** Description changed:
- Impact]
+ [Impact]
In Ubuntu Impish, an issue has been noted in regards to refreshing
packages in Plasma Discover for upgrade or installation. An
Totally spaced this. Can confirm it works.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
This happens any time my system senses my audio interface as unplugged,
which can happen if there's a momentary loss in power to the device
(i.e. momentary power outage, etc.).
ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: zita-ajbridge 0.8.4-1
Public bug reported:
This seems to happen quite a bit, not sure why.
ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: kmail 4:21.08.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-16.16-lowlatency 5.13.13
Uname: Linux 5.13.0-16-lowlatency x86_64
NonfreeKernelModules: zfs zunicode zavl icp
** Description changed:
+ Impact]
+
In Ubuntu Impish, an issue has been noted in regards to refreshing
packages in Plasma Discover for upgrade or installation. An error
appears upon initialization of the Discover interface:
"cannot refresh whilst network offline"
This will happen
@Julian I can definitely convert this to an SRU. I haven't seen it in
Hirsute or Focal, but it's a decent safety net for when things get stuck
(gio or otherwise).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
This bug is ancient, but a recent upstream open bug exists:
https://github.com/Enselic/recordmydesktop/issues/23
** Bug watch added: github.com/Enselic/recordmydesktop/issues #23
https://github.com/Enselic/recordmydesktop/issues/23
--
You received this bug notification because you are a
The issue resolved itself with the apache ssl update shortly after I
filed this bug, but it still shouldn't fail as hard as it did.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943286
Title:
Public bug reported:
Happened while trying to sync a package. Looks like it definitely should
not fail like this.
ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: ubuntu-dev-tools 0.184
ProcVersionSignature: Ubuntu 5.13.0-14.14-lowlatency 5.13.1
Uname: Linux 5.13.0-14-lowlatency x86_64
Pull request has been merged.
https://github.com/PackageKit/PackageKit/pull/506
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943189
Title:
"cannot refresh whilst network offline" bug
To manage
The packagekit maintainer (Richard Hughes) has requested this patch as a
pull request, so this will be in packagekit upstream very, very soon.
https://github.com/PackageKit/PackageKit/issues/336#issuecomment-91713
** Bug watch added: github.com/PackageKit/PackageKit/issues #336
Public bug reported:
In Ubuntu Impish, an issue has been noted in regards to refreshing
packages in Plasma Discover for upgrade or installation. An error
appears upon initialization of the Discover interface:
"cannot refresh whilst network offline"
This will happen regardless of if a system is
Thank you for taking the time to report this bug. Unfortunately, it was
initially reported against the wrong package (ubuntu-release-upgrader vs
calamares) and is therefore missing the correct stacktrace and crash
retrace information. The screenshot is not helpful as the issue is not
always
** Package changed: ubuntu-release-upgrader (Ubuntu) => calamares
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943071
Title:
ubuntustudio 21.10 daily build installation error
To manage
Public bug reported:
Crash occurred while running lintian, was reproducible with every run.
ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: groff-base 1.22.4-6
ProcVersionSignature: Ubuntu 5.13.0-14.14-lowlatency 5.13.1
Uname: Linux 5.13.0-14-lowlatency x86_64
NonfreeKernelModules: zfs
Public bug reported:
Seemed to happen on login. I don't quite know why.
ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: osspd 1.3.2-12.2
ProcVersionSignature: Ubuntu 5.13.0-14.14-lowlatency 5.13.1
Uname: Linux 5.13.0-14-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
*** This bug is a duplicate of bug 1942636 ***
https://bugs.launchpad.net/bugs/1942636
** This bug has been marked a duplicate of bug 1942636
install ubuntu 21.04 is not responding
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Public bug reported:
This occurred while trying to launch Scribus in Ubuntu Impish.
ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: scribus 1.5.7+dfsg-1build1
ProcVersionSignature: Ubuntu 5.13.0-14.14-lowlatency 5.13.1
Uname: Linux 5.13.0-14-lowlatency x86_64
NonfreeKernelModules:
** Summary changed:
- discover is not removing unused kernels
+ Kernel updates marked as "manually installed", prevents old kernels cleanup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914278
*** This bug is a duplicate of bug 1914278 ***
https://bugs.launchpad.net/bugs/1914278
** This bug has been marked a duplicate of bug 1914278
discover is not removing unused kernels
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: carla (Ubuntu)
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/1941939
Title:
Carla doesn't work
To manage notifications about this bug go to:
Apparently this is a known issue with PackageKit, but hasn't been
addressed by the developers.
https://github.com/PackageKit/PackageKit/issues/450
** Bug watch added: github.com/PackageKit/PackageKit/issues #450
https://github.com/PackageKit/PackageKit/issues/450
** Changed in: discover
Actually, I failed to read that correctly the first time. Are you saying
"download", etc. was *not* checked?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1941620
Title:
System still install update
** Changed in: ubiquity (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1941620
Title:
System still install update packages even uncheck "Download
updates..."
Kent, please do not override a bug triage. This is not a bug with
ubiqity.
** Changed in: ubiquity (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1941620
Actually, since this is expected behavior, I'm closing this bug as
invalid. Please do not reopen.
** Changed in: ubiquity (Ubuntu)
Status: Fix Released => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
What you are describing is expected behavior.
Ubuntu 20.04.3 is due for release on August 26th with kernel 5.11.0.27
as the default kernel. Closing this as "Fix Released".
** Changed in: ubiquity (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1941003
When reporting bugs in the future please use apport by using 'ubuntu-
Lars, thanks for investigating.
I'm pretty sure the "resolved downstream" status is referring to this
bug being marked as "Won't Fix" by Herald above. The patching mentioned
is no longer there, so it's definitely not a Kubuntu issue.
Based on that, and that this bug was initially filed against
Thank you for taking the time to report this bug and make Ubuntu better.
The following lines were found in the log files you provided:
Aug 22 15:58:10 ubuntu grub-installer: Installing for x86_64-efi platform.
Aug 22 15:58:22 ubuntu grub-installer: grub-install: warning: Internal error.
Aug 22
My job is not to report every bug that lands here upstream, but to
direct those reporting the bug where to properly report it.
The package in this case is kde-runtime and can be found at
https://bugs.kde.org. However, I did notice that Herald Sitter
(apachelogger), who *is* a KDE dev, marked this
Uqbar,
Your tone is not welcome here. I'm a bug supervisor here, and have
determined it's an upstream bug. It's not a matter of changing it "to
the desk of other devs", but to make sure it's reported properly.
My logic here: there's no reason to believe this is an Ubuntu/Kubuntu-
only bug since
Rather than bash Kubuntu/Ubuntu, let's do something constructive.
Has this been reported upstream to KDE (https://bugs.kde.org/)? If not,
then that needs to be done. Until then, this bug is incomplete. Please
report back with the upstream bug report linked.
** Changed in: kde-runtime (Ubuntu)
IOhannes and José,
In the future, be sure to change the "verification-needed" and
"verification-neeeded-{release}" tags as "verification-done" when you've
confirmed the bug fix. Otherwise the system will not know to
automatically migrate from updates-proposed to updates after the 7-day
period.
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
** Package changed: obs-studio (Ubuntu) => qtbase-opensource-src
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876612
Title:
Corrupt window layout / no preview
To manage notifications
** Changed in: jackd2 (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937325
Title:
Jack clients have segmentation fault when trying to connect
Unfortunately, all of this comes down to the forced LTO. Disabling this
in d/rules, per upstream, fixes the problem. He had a few more notes as
well. It seems as though the Debian package is doing some unnecessary
gymnastics, so this is a decent divergence.
diff --git a/debian/rules
** Changed in: v4l2loopback (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936250
Title:
modprobe: ERROR: could not insert 'v4l2loopback':
Looks like this is fixed upstream. I'll put the commit into a patch and
upload. https://github.com/umlaeute/v4l2loopback/issues/439
** Bug watch added: github.com/umlaeute/v4l2loopback/issues #439
https://github.com/umlaeute/v4l2loopback/issues/439
** Changed in: v4l2loopback (Ubuntu)
With regard to Debian, the Request For Packaging process is described
here: https://wiki.debian.org/RFP
Please bear in mind, though, that nearly all packages are created by
volunteers which need to take time out of their day to do these.
Therefore, you're more likely to get an application
With regards to bug 105653, dvdstyler was in the archive at some point,
but was removed. Likely, it was introduced in Debian and auto-synced,
but then removed from Debian and subsequently removed from Ubuntu.
Have you done a request for packaging in Debian? If you did that, and
someone packages
New information: Rebuilds of 1.9.17 and builds of 1.9.18 in impish
result in the same issue, meaning there is likely a build-time
dependency incompatibility. Upstream has been notified.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Changed to critical as this is a blocking bug for Ubuntu Studio 21.10's
release.
** Changed in: jackd2 (Ubuntu)
Importance: High => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937325
** Changed in: jackd2 (Ubuntu)
Importance: Undecided => High
** Changed in: jackd2 (Ubuntu)
Status: Confirmed => Triaged
** Changed in: jackd2 (Ubuntu)
Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer)
--
You received this bug notification because you are
Reported upstream: https://github.com/jackaudio/jack2/issues/776
** Bug watch added: github.com/jackaudio/jack2/issues #776
https://github.com/jackaudio/jack2/issues/776
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
Steps to show this bug. Start jackd either as jackd or jackdbus (with
jack_control). run jack_lsp from the command line to show jackd's port.
Jack_lsp will segfault. Other jack clients will have similar problems.
- This is specific to jackd2 1.1.19, jackd 1.1.17 does
** Description changed:
Steps to show this bug. Start jackd either as jackd or jackdbus (with
jack_control). run jack_lsp from the command line to show jackd's port.
Jack_lsp will segfault. Other jack clients will have similar problems.
This is specific to jackd2 1.1.19, jackd 1.1.17 does
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please execute the following command only once, as it will
automatically gather debugging information, in a terminal:
apport-collect 1937087
When reporting bugs in the future please use apport by using 'ubuntu-
** Package changed: ubuntu => onboard (Ubuntu)
** Package changed: onboard (Ubuntu) => gdm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936703
Title:
screen keyboard doesn't work on
Thank you for taking the time to report this issue and helping to make
Ubuntu better. Examining the information you have given us, this does
not appear to be a bug report so we are closing it. We understand the
difficulties you are facing, but it is better to raise problems you are
having in a
After updating, there has been an error related to modprobe that I
reported as a new bug (LP: #1936250), however, this may be a regression
from the fixes presented in this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
This looks like it has to do with a recent version of the package.
A recent update to v4l2loopback has caused it to fail with the following
error message when modprobe is done:
modprobe: ERROR: could not insert 'v4l2loopback': Invalid argument
This may have to do with an
Public bug reported:
Happened when right-clicking on the desktop to change the wallpaper.
ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: plasma-workspace 4:5.22.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-lowlatency 5.11.21
Uname: Linux 5.11.0-20-lowlatency x86_64
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
Thank you for taking the time to request this package and helping to
make Ubuntu better. Unfortunately you have not provided enough
information for a developer to start packaging this application. Please
make sure this bug meets the guidelines at
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
** Also affects: ubuntustudio-menu (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: ubuntustudio-menu (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: ubuntustudio-menu (Ubuntu)
Status: New => Fix Released
--
You received this bug notification
Public bug reported:
This crash seems to happen every time I send an email via Kmail. Mail
Dispatcher Agent freezes. Only workaround is to 'pkill akonadi' and
restart akonadi from within Kmail, at which point the email sends.
ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: kdepim-runtime
Public bug reported:
[Impact]
* Users of Ubuntu Studio 20.04 LTS currently have a menu item that
takes them to the Freenode IRC web chat for the #ubuntustudio channel.
However, Ubuntu Studio's support channel no longer exists on Freenode.
* Following the move from Freenode to libera.chat,
Public bug reported:
Crash happened while using dolphin to do a file search. Reproducible.
ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: kinit 5.83.0-0ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-lowlatency 5.11.17
Uname: Linux 5.11.0-18-lowlatency x86_64
Public bug reported:
This problem seems to have just shown-up. Running Impish for testing
reasons (basically dogfooding).
Got a window:
Title: Virtualbox - Error in SUPR3HardenedMain
Effective UID is not root (euid=1000 egid=1000 uid=1000 gid=1000)
(rc=-10)
Please try reinstalling VirtualBox
Public bug reported:
Per https://github.com/free-
sm/geonkick/commit/0ec36f4ef9b37053e0feb60937112c247ca3b310 the code for
redkite is now included in geonkick, which is the only project that was
using it.
As such, since redkite was only used by geonkick, redkite now has no use
being a separate
Thank you for taking the time to report this issue and helping to make
Ubuntu better. Examining the information you have given us, this does
not appear to be a bug report so we are closing it. We understand the
difficulties you are facing, but it is better to raise problems you are
having in the
Public bug reported:
While retrieving SMS messages, kdeconnect threw a segfault. This seems
to happen if MMS messages are also involved.
ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: kdeconnect 21.04.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-lowlatency 5.11.17
Uname:
Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Go ahead with the remove. The package is utterly broken as it crashes
upon launch. It has basically been replaced functionally by Carla. No
objections.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for reporting this bug to Ubuntu.
Ubuntu Studio 18.04 (bionic) reached end-of-life on January 26, 2019.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it
*** This bug is a duplicate of bug 1931009 ***
https://bugs.launchpad.net/bugs/1931009
** This bug has been marked a duplicate of bug 1931009
This is a long standing bug, kindly resolve. Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: ubiquity (Ubuntu)
Status: New => Opinion
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931017
Title:
Enabled proposed for this file, does exactly what is described and
allows for CUDA library installation on Hirsute, Groovy, and Focal.
** Tags removed: verification-needed verification-needed-focal
verification-needed-groovy verification-needed-hirsute
** Tags added: verification-done
Verified fixes work in Groovy as well using the above method.
** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925685
Verified fixes work in Hirsute as well using above method.
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925685
** Changed in: ubiquity (Ubuntu)
Status: New => Opinion
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930223
Title:
** Summary changed:
- Please SRU nvidia-modprobe 465.24 and nvidia-settings 460.73
+ Please SRU nvidia-modprobe 465.24
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928146
Title:
Please SRU
** Changed in: nvidia-settings (Ubuntu Focal)
Status: Fix Committed => Fix Released
** Changed in: nvidia-settings (Ubuntu Groovy)
Status: Fix Committed => Fix Released
** Changed in: nvidia-settings (Ubuntu Hirsute)
Status: Fix Committed => Fix Released
--
You received
Pander: Until the fix lands in Ubuntu, it's still "Triaged". The fix
landing in Ubuntu depends on the new version, whenever the upstream
releases it, landing in the latest development branch. Please do not
change the status of this bug to reflect the upstream status.
** Changed in: pavucontrol
Installed and ran on systems containing issue. Kernel seemed to work
flawlessly. We are going to roll with this kernel and resume sales of
our systems.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a
Thank you for taking the time to report this bug.
Xubuntu 18.04 (Bionic Beaver) reached end-of-life (EOL) on April 30,
2021.
As such, any and all installations of Xubuntu 18.04 are unsupported. Due
to this lack of support, this bug report is invalid as it was reported
after the EOL date.
**
** Changed in: obs-studio (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898224
Title:
[FFe] Upgrade OBS Studio to version 26 in focal
To manage
** Changed in: nvidia-settings (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: nvidia-settings (Ubuntu Groovy)
Status: New => Fix Committed
** Changed in: nvidia-settings (Ubuntu Hirsute)
Status: New => Fix Committed
--
You received this bug notification because
** Changed in: nvidia-modprobe (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: nvidia-modprobe (Ubuntu Groovy)
Status: New => Fix Committed
** Changed in: nvidia-modprobe (Ubuntu Hirsute)
Status: New => Fix Committed
--
You received this bug notification because
** Description changed:
[Impact]
Users of the Nvidia CUDA libraries using Hirsute, Groovy, or Focal are
unable to install and/or upgrade to version 460.73 of the CUDA
libraries. This is because the new libraries have a versioned hard
dependency on nvidia-modprobe >= 460.73 and
This bug was fixed in the package nvidia-modprobe - 465.24.02-1
---
nvidia-modprobe (465.24.02-1) experimental; urgency=medium
* New upstream release. (Closes: #987744)
-- Luca Boccassi Thu, 29 Apr 2021 11:48:45 +0100
** Description changed:
[Impact]
Users of the
** Changed in: nvidia-modprobe (Ubuntu Impish)
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928146
Title:
Please SRU nvidia-modprobe and nvidia-settings 460.73
Public bug reported:
[Impact]
Users of the Nvidia CUDA libraries using Hirsute, Groovy, or Focal are
unable to install and/or upgrade to version 460.73 of the CUDA
libraries. This is because the new libraries have a versioned hard
dependency on nvidia-modprobe 460.73 and nvidia-settings 460.73.
This will happen if you try it. Never add the ubuntustudio-* packages
directly. If you wish to use the Ubuntu Studio packages on a regular
Ubuntu install, install "ubuntustudio-installer" first as this is the
supported method. The method you tried is unsupported, so I'm closing
this bug.
**
** Bug watch removed: Debian Bug tracker #947376
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947376
** Also affects: pavucontrol (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958178
Importance: Unknown
Status: Unknown
** Changed in: pavucontrol (Ubuntu)
** Changed in: libffado (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/649542
Title:
New firewire stack makes more FFADO XRUNs than old firewire stack.
To
** Changed in: libffado (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097308
Title:
Echo Audiofire 12 not working on Ubuntu 12.10
To manage
701 - 800 of 1654 matches
Mail list logo
