Ah, I got confused because I had GCC 13 and now Software Updater said
GCC (actually gcc-14-base) was to be updated to 14.2.0. Not sure why
gcc-14-base is installed, I haven't installed gcc-14 packages, anyway it
seems a pretty empty package.
--
You received this bug notification because you are a
I am mildly surprised to see something as fundamental as gcc being
upgraded to a new major version in a Ubuntu stable release, and this on
a very obscure basis (at least for the open community). I see no
justification here in the bug report that matches anything at
https://canonical-sru-docs.readth
For slowness on MTP or network file systems, see also
https://github.com/mate-desktop/caja/issues/380
** Bug watch added: github.com/mate-desktop/caja/issues #380
https://github.com/mate-desktop/caja/issues/380
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
*** This bug is a duplicate of bug 2001624 ***
https://bugs.launchpad.net/bugs/2001624
** Summary changed:
- caja
+ caja slow when dealing with lots of files
** This bug has been marked a duplicate of bug 2001624
copying or deleting large amounts of files is very slow
--
You received th
** Summary changed:
- caja stopped working
+ caja will not launch after crash, even after reboot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2024528
Title:
caja will not launch after crash, even
Public bug reported:
This is seen on Ubuntu 24.04 and is a regression from Ubuntu 20.04.
When selecting a file in Caja, then pressing F2 to edit the filename,
(optionally adjusting the text selection with mouse or arrow keys), then
ctrl-C to copy:
- expected behaviour: The selected text goes int
** Attachment removed: "upt-man-2068805.png"
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2068805/+attachment/5825324/+files/upt-man-2068805.png
** Attachment added: "upd-man-2068805-2"
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2068805/+attachment/58253
The message "You need to enable Ubuntu Pro to install these updates." is
written exactly when the button disappears, or actually at any time that
no packages are selected any longer.
** Attachment added: "Screenshot"
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2068805/+attach
The screenshot shows the absence of the "Install Now" button.
$ lsb_release -c
No LSB modules are available.
Codename: noble
$
$ update-manager --version
WARNING:root:can not import unity GI Namespace Dbusmenu not available
update-manager: version 24.04.9
$
** Attachment added: "upt-man-20
This should be fixed in noble-proposed now, see bug #2041831.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2027941
Title:
Unchecking packages in update-manager causes SIGSEGV
To manage notificatio
Nathan, now that 2041831/2027941 has been fixed, I hope you can come
back to this and reproduce the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068805
Title:
"Install Now" button disappear
I installed 1:24.04.9 from noble-proposed and clicked on the selection
tick markers to toggle them on and off repeatedly. I had 5-6 updates in
the list, one from a PPA. One was in a group, so I tested both clicking
the group tick marker and the package tick marker. I also clicked
multiple times qui
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073673
Title:
pyalsa segfaults on loading alsaseq
To manage notifications about this bug go to:
https://bugs.launchpa
With original from noble (1.2.7-1build5):
$ python3 -c 'from pyalsa import alsaseq'
Segmentation fault (core dumped)
$
With noble-proposed package:
$ sudo dpkg -i ~/Downloads/python3-pyalsa_1.2.7-1ubuntu0.1_amd64.deb
(Reading database ... 382157 files and directories currently installed.)
Prepar
Thanks, Vladimir!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073673
Title:
pyalsa segfaults on loading alsaseq
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+s
** Summary changed:
- GDS force mitigation re-enabled in 6.10 causing crashes
+ GDS force mitigation re-enabled in 6.10 (and 6.11) causing crashes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077145
> Just waiting for the kernel team to make the source available in the
normal oracular git repo.
It is here:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/oracular/tree/debian.master/config/annotations?h=Ubuntu-6.11.0-4.4#n8189
Also -5.5 is affected and it on its way:
https:/
> Just waiting for the kernel team to make the source available in the
normal oracular git repo.
It is here:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/oracular/tree/debian.master/config/annotations?h=Ubuntu-6.11.0-4.4#n8189
Everybody running this kernel on an older Intel
Matthew, you can check this yourself. Just install the kernel and look
for CONFIG_MITIGATION_GDS_FORCE in /boot/config-*. You don't need to
install it either, you can just download the "modules" package that owns
the config file and unpack it with dpkg-deb and grep the config file.
--
You receive
Maybe I should point out that the upstream default is 'n' [1]. I don't
know why it has been set to 'y' in Ubuntu, maybe just because mitigation
sounds "safe".
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/x86/Kconfig?h=v6.10#n2615
--
You received this bug notif
Hi Philip,
There must be a misunderstanding. In your links I see:
+CONFIG_MITIGATION_GDS_FORCE policy<{'amd64': 'y'}>
So line 8134 has:
CONFIG_MITIGATION_GDS_FORCE policy<{'amd64': 'y'}>
and this is the problem. This setting should be 'n'.
Please see my
** Summary changed:
- failed to send h2c command
+ rtw_8821ce: failed to send h2c command
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077217
Title:
rtw_8821ce: failed to send h2c command
To man
** Summary changed:
- No signal for hdmi monitor
+ No signal for hdmi monitor (i915)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077218
Title:
No signal for hdmi monitor (i915)
To manage notifi
** Description changed:
The (supposedly unintended) re-enabling of GDS force migration in the
Ubuntu 6.10 kernels causes the AVX instruction to be disabled on older
CPUs which have no available microcode update. This causes various
programs to crash due to the unconditional use of AVX in l
** Description changed:
The (supposedly unintended) re-enabling of GDS force migration in the
- 6.10 kernels causes the AVX instruction to be disabled on older CPUs
- which have no available microcode update. This causes various programs
- to crash due to the unconditional use of AVX in libgnutl
** Description changed:
The (supposedly unintended) re-enabling of GDS force migration in the
6.10 kernels causes the AVX instruction to be disabled on older CPUs
which have no available microcode update. This causes various programs
to crash due to the unconditional use of AVX in libgnutl
Public bug reported:
The (supposedly unintended) re-enabling of GDS force migration in the
6.10 kernels causes the AVX instruction to be disabled on older CPUs
which have no available microcode update. This causes various programs
to crash due to the unconditional use of AVX in libgnutls.so, libxu
I am not awaiting your approval but to see 1.2.12 landing in Ubuntu
24.10. Thanks for clarifying about git-ubuntu and the SRU team.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073673
Title:
pyals
** Description changed:
Upstream bug https://github.com/alsa-project/alsa-python/issues/9
- SRU justification:
+ SRU rationale:
[ Impact ]
- * the alsaseq segfault prevents the use of this module in noble and
+ * the alsaseq segfault prevents the use of this module in noble and
th
I was not able to reproduce the other issue, so I made an SRU only
fixing the present bug.
Awaiting your sync before subscribing ubuntu-sponsors or SRU team.
I tried also make a LP git merge request for the SRU, but it so
confusing with that repo sometimes having patches applied and sometimes
not
** Patch added: "SRU for noble, adding upstream patch"
https://bugs.launchpad.net/ubuntu/+source/python-pyalsa/+bug/2073673/+attachment/5806140/+files/python-pyalsa_1.2.7-1ubuntu0.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
** Description changed:
+ Upstream bug https://github.com/alsa-project/alsa-python/issues/9
+
+ SRU justification:
+
+ [ Impact ]
+
+ * the alsaseq segfault prevents the use of this module in noble and
+ thus breaks application using it
+
+ * regression due to the upgrade to python 3.12
+
+
Maybe this applies? "it is also acceptable to upload new microreleases
with many bug fixes without individual Launchpad bugs for each of them".
There is only one other change in 1.2.12, "hcontrol,mixer: improve
callback GIL state handling", fixing https://github.com/alsa-
project/alsa-python/issues
Thanks Jeremy. Is it possible to SRU 1.2.12 into Ubuntu 24.04, or can
only fixes like this be cherry-picked?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073673
Title:
pyalsa segfaults on loading
Public bug reported:
Just a heads-up that Intel updated their 20240813 release [1], as of
writing 8 hours ago, by replacing the release files (and apparently
repushing the git commit! [2]) but without bumping the version. Whereas
the current Ubuntu release has the contents of the original release
Proposed debdiff for oracular.
** Patch added: "Add upstream commit cb75f5c"
https://bugs.launchpad.net/ubuntu/+source/python-pyalsa/+bug/2073673/+attachment/5798887/+files/python-pyalsa_1.2.7-1ubuntu1.debdiff
** Tags added: patch
--
You received this bug notification because you are a memb
Marking confirmed since the issue is known and fixed upstream.
** Changed in: python-pyalsa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073673
Title:
pya
** Summary changed:
- pyalsa segfaults on loading
+ pyalsa segfaults on loading alsaseq
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073673
Title:
pyalsa segfaults on loading alsaseq
To manage n
This is solved by adding commit cb75f5cd from upstream:
https://git.alsa-project.org/?p=alsa-python.git;a=commitdiff;h=cb75f5cdba0a29bdfa43eb56285da4917d2941a9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
After rebuilding the package locally (sudo apt build-dep python3-pyalsa;
apt source python3-pyalsa; cd python-pyalsa-1.2.7; debuild -b -us -uc;
sudo dpkg -i ../python3-pyalsa_1.2.7-1build5_amd64.deb) there is a
different error:
$ python3 -c 'from pyalsa import alsaseq'
Traceback (most recent call
In my case the segfault can be reproduced with simply:
$ python3 -c 'from pyalsa import alsaseq'
Segmentation fault (core dumped)
$
I am not sure this issue is actually the same as OP here or in the
Debian bug, so I have reported bug #2073673 instead.
--
You received this bug notification becau
Public bug reported:
Ubuntu 24.04 with python3-pyalsa 1.2.7-1build5. I noticed that solfege
(3.23.4-12) crashes with segmentation fault while launching, after
installing the python3-pyalsa package.
It can be reproduced by simply loading pyalsa and its alsaseq module:
$ python3 -c 'from pyalsa im
Also appears in Ubuntu 24.04 with python3-pyalsa 1.2.7-1build5. (Note
that the Debian bug was closed because it worked for the OP after
upgrade to python3-pyalsa 1.1.6-2+b2.)
solfege (3.23.4-12) crashes with segmentation fault while launching.
This is the stack trace:
(gdb) where
#0 __memset_eve
Apport didn't work for me either, so I ran gdb python manually. The
traceback is identical to the OP one in bug #2027941.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2041831
Title:
/usr/bin/update
I think you got segfaults because you hit bug #2027941 (or #2041831, the
"secret" report, dunno which one should be made duplicate). I guess you
used a mouse click to deselect :) If you use the spacebar to deselect,
you can probably reproduce this bug.
--
You received this bug notification becaus
** Description changed:
If one deselects all packages, the "Install Now" button disappears,
which makes sense (on another note it would make even more sense if it
was simply grayed out). However when one or more packages are then re-
selected, the button won't ever reappear, and update-man
Merge request:
https://code.launchpad.net/~tormodvolden/update-manager/+git/update-manager/+merge/467152
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068809
Title:
changelogs not listed for PPA pa
Public bug reported:
When clicking on a package from a PPA in update-manager, the "Changes
for XXX versions:" section will say:
"This update does not come from a source that supports changelogs."
and on the console it dumps:
ERROR:root:Unable to find a valid PPA candidate URL.
The reason is t
It happens if packages are deselected with a mouse click. If the
keyboard spacebar is used instead, it doesn't crash AFAICS.
Seen with update-manager 1:24.04.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
*** This bug is a duplicate of bug 2027941 ***
https://bugs.launchpad.net/bugs/2027941
** This bug has been marked a duplicate of bug 2027941
Unchecking packages in update-manager causes SIGSEGV
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
*** This bug is a duplicate of bug 2027941 ***
https://bugs.launchpad.net/bugs/2027941
** This bug has been marked a duplicate of bug 2027941
Unchecking packages in update-manager causes SIGSEGV
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
The master bug is probably #2041831.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2027941
Title:
Unchecking packages in update-manager causes SIGSEGV
To manage notifications about this bug go to:
A.k.a "Unchecking packages in update-manager causes SIGSEGV" #2027941
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2041831
Title:
/usr/bin/update-
manager:11:g_type_check_instance_is_fundamental
*** This bug is a duplicate of bug 2027941 ***
https://bugs.launchpad.net/bugs/2027941
This seems to be a duplicate of #2027941.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2028920
Title:
Upd
From your crash file:
Thread 1 (Thread 0x7fc072830040 (LWP 3292)):
#0 0x7fc0718b4c41 in g_type_check_instance_is_fundamentally_a () from
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Probably a duplicate of #2027941.
--
You received this bug notification because you are a member of Ubuntu
** Tags added: noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068805
Title:
"Install Now" button disappears for good if all packages unselected
To manage notifications about this bug go to:
h
Public bug reported:
If one deselects all packages, the "Install Now" button disappears,
which makes sense (on another note it would make even more sense if it
was simply grayed out). However when one or more packages are then re-
selected, the button won't ever reappear, and update-manager must b
** Summary changed:
- Update Manager crashes when unselecting any package in Ubuntu 23.04
+ Update Manager crashes when unselecting any package
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2028920
T
I noticed all the "gesture" functions in the call trace. Indeed, if I
only use the keyboard (tab to navigate, space to toggle packages or
groups) it doesn't crash.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
This is where it is crashing:
$ gdb --args python3 /usr/bin/update-manager --no-update
... snip ...
Thread 1 "python3" received signal SIGSEGV, Segmentation fault.
Downloading source file
/usr/src/glib2.0-2.80.0-6ubuntu3.1/debian/build/deb/../../../gobject/gtype.c
0x77137d59 in g_type_c
I have this in 24.04 as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2028920
Title:
Update Manager crashes when unselecting any package in Ubuntu 23.04
To manage notifications about this bug
Can be the same as this: https://github.com/getsolus/brisk-
menu/issues/56 ("After some time, Brisk Menu consumes a ton of memory")
** Bug watch added: github.com/getsolus/brisk-menu/issues #56
https://github.com/getsolus/brisk-menu/issues/56
--
You received this bug notification because you
Today's linux-libc-dev changelog was 4 lines. This freezes the
update-manager GUI (with 100% CPU) in Ubuntu 20.04 for very long.
My 10 year old patch above still applies.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
dfu-util 0.11 is fully backwards-compatible with 0.9 so it shouldn't be
a problem with firmware-tomu. Please also note that firmware-tomu
doesn't call anything from dfu-util itself, only their user instructions
tell the user to run dfu-util manually.
The feature changes since 0.9 (see also ChangeL
Upstream made a 1.10.3 release with only this fix. Once this gets in
Debian it'll be worth syncing it as an SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895252
Title:
help menu entry points t
** Description changed:
Due to maintainer MIA the current package 0.9 in Debian testing (and
- Ubuntu) is nearly 7 years old. I have salvaged the package in Debian,
- but this has been a long process, and the new 0.11-1 package is now
- sitting in the delayed queue until February 26. Since this
It is in unstable now:
http://deb.debian.org/debian/pool/main/d/dfu-util/dfu-util_0.11-1.dsc
** Description changed:
Due to maintainer MIA the current package 0.9 in Debian testing (and
Ubuntu) is nearly 7 years old. I have salvaged the package in Debian,
but this has been a long process, a
** Summary changed:
- [FFe] sync dfu-util 0.11-1 from Debian (now in DELAYED)
+ [FFe] sync dfu-util 0.11-1 from Debian unstable (was in DELAYED)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961635
** Changed in: xscreensaver (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961634
Title:
Please merge xscreensaver 6.02+dfsg1-1 from Debian
To manage notifi
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961634
Title:
Please merge xscreensaver 6.02+dfsg1-1 from Debian
To manage notifications about this bug go to:
https://bugs.launc
This was also test-built in my PPA:
https://launchpad.net/~tormodvolden/+archive/ubuntu/ppa/+build/23196149
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961634
Title:
Please merge xscreensaver 6.0
To simplify review, here is the new Ubuntu delta.
** Patch added: "Ubuntu delta"
https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1961634/+attachment/5563441/+files/xscreensaver_6.02+dfsg1-2ubuntu1.ubuntu-delta.debdiff
--
You received this bug notification because you are a member
** Patch added: "Full debdiff from xscreensaver_5.45+dfsg1-2ubuntu1"
https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1961634/+attachment/5563432/+files/xscreensaver_6.02+dfsg1-2ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Due to maintainer MIA the current package 0.9 in Debian testing (and
Ubuntu) is nearly 7 years old. I have salvaged the package in Debian,
but this has been a long process, and the new 0.11-1 package is now
sitting in the delayed queue until February 26. Since this will barely
Public bug reported:
@robert-ancell Are you going to merge this? I notice Jammy feature
freeze is coming up soon.
** Affects: xscreensaver (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
The wrong display of information in lsusb when plugged in a hub is a
known problem fixed in usbutils 013.
Anyway, rest assured that wrong information printed by lsusb has no
effect on the functionality of the device (unless some weird program
would be parsing lsusb output, very unlikely).
--
You
That the "HyperX Cloud Alpha S" value is repeated for several items is a
known problem that has been fixed in newer usbutils.
Note that lsusb nowadays collect data from the udev hwdb database and
not from the usb.ids file.
--
You received this bug notification because you are a member of Ubuntu
The package description was updated at some point, for sure included in
5.42 (in 20.04).
** Changed in: xscreensaver (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
In my experience, small issues like this will seldom be fixed in the old
release (20.04). It is a small enough fix, but there is enough
"paperwork" involved (SRU process) that nobody will take their time for
this.
I would recommend installing the 6.02 version from my PPA:
https://launchpad.net/~to
Closing since no further info from submitter.
** Changed in: xscreensaver (Ubuntu)
Status: Incomplete => Invalid
** Changed in: xscreensaver (Ubuntu)
Assignee: Tormod Volden (tormodvolden) => (unassigned)
--
You received this bug notification because you are a member of Ubunt
Closing since it couldn't be reproduced and no further info from
submitter.
** Changed in: xscreensaver (Ubuntu)
Status: Incomplete => Invalid
** Changed in: xscreensaver (Ubuntu)
Assignee: Tormod Volden (tormodvolden) => (unassigned)
--
You received this bug notificat
Note the correction I am suggesting was also applied upstream as part of
commit 3a36bf7b55ff3da09cf6ff181be27e9f9b7cd97b
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947359
Title:
[focal] ubuntu p
** Patch added: "debdiff for focal SRU"
https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1947359/+attachment/5533147/+files/marco_1.24.0-1ubuntu1.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Public bug reported:
marco 1.24.0-1ubuntu1 in Ubuntu 20.04 ships with the Ubuntu-specific
patch debian/0001_fix_segfaults.patch which includes this part:
+ else {
+g_warning ("Visible region is null");
}
+ }
Thanks to this (unnecessary) part of patch ~/.xsession-errors gets f
Fixed upstream in caja-rename 21.7.18.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877718
Title:
RuntimeError: object at 0x7f3f983de500 of type RenameMenu is not
initialized
To manage notifica
I filed an upstream pull request at https://github.com/tari01/caja-
rename/pull/4
Corresponding changes for other packages:
- https://bazaar.launchpad.net/~costales/folder-color/trunk/revision/283
- https://github.com/GSConnect/gnome-shell-extension-
gsconnect/commit/cb422ea85a95d8d71bfafb8a1d05
FWIW, the error message also appears after upgrading to caja 1.25.3 and
caja-rename 21.4.11 (checked out latest git of both), on top of Ubuntu
20.04.2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/187
Certain combinations of screensaver hacks, graphic drivers and cards
cause unexpectedly high CPU loads. In my PPA at
https://launchpad.net/~tormodvolden/+archive/ubuntu/ppa there is
xscreensaver 5.45 for focal, with an extra patch that displays a CPU
load summary for each hack in the verbose log. I
I had this error on Ubuntu Mate 20.04, also when running grub-install
chroot'ed to the failed installation. After converting the partition
table from MBR to GPT, grub-install worked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Certainly happening in xenial, which is still supported. Clicking on a
kernel package makes it hang for a long time. Still have to apply my
above patch.
** Changed in: update-manager (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ub
I think this xenial update (the change to dict) broke changelog display
- please see my patch in #1850208.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771914
Title:
release-upgrade-motd can't upd
** Summary changed:
- update-manager stop to load update descriptions
+ update-manager stop to load update descriptions / changelog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849004
Title:
upda
*** This bug is a duplicate of bug 1849004 ***
https://bugs.launchpad.net/bugs/1849004
** This bug has been marked a duplicate of bug 1849004
update-manager stop to load update descriptions
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Because urlsplit() is returning None instead of "" in the username
member the logic in MyCache.py falsely thinks the URI contains a
username.
Exception in thread Thread-4:
Traceback (most recent call last):
File "/usr/lib/python3.5/threading.py", line 914, in _bootstrap_in
About xserver-xorg-video-radeon: It is a binary package, one of many
built from the xserver-xorg-video-ati source package.
** Package changed: xserver-xorg-video-radeonhd (Ubuntu) => xserver-
xorg-video-ati (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Bug watch added: freedesktop.org Bugzilla #100423
https://bugs.freedesktop.org/show_bug.cgi?id=100423
** Also affects: nouveau via
https://bugs.freedesktop.org/show_bug.cgi?id=100423
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a me
When I have the OP's original issue, lost connection after resume and
only one network listed, simply running "sudo iw wlp3s0 scan" makes
everything work again, without having to reload the module.
I am sure I have seen the lost connection after resume without any
network listed too. I have not ye
There are possibly two independent issues here. In some cases the
connection is lost after resume, and the module must be reloaded (or
configured to be unloaded at suspend).
The other issue is that nm-applet shows no connection (or in my case it
shows a wired connection and no wifi bar or networks
Seeing the same as OP with "Intel Corporation Centrino Advanced-N 6235
(rev 24)" on 16.04.2 with 4.8.0-34-generic.
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
** Bug watch added: Red Hat Bugzilla #737424
https://bugzilla.redhat.com/show_bug.cgi?id=737424
--
You received
Other possible workarounds to try out:
https://bugzilla.redhat.com/show_bug.cgi?id=737424
https://ubuntuforums.org/showthread.php?t=2004690&page=4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590985
1 - 100 of 7332 matches
Mail list logo
