Debian version 3.0.1-1 (experimental) doesn't build on Ubuntu, so I'm adding a
debdiff. I've confirmed that it builds in pbuilder and works when installed.
Also added an epoch (since it was present in earlier Ubuntu releases, so
we'll probably have to carry it forever).
** Patch added:
Debian version 3.0.1-1 (experimental) doesn't build on Ubuntu, so I'm
adding a debdiff. I've confirmed that it builds in pbuilder and works
when installed.
** Patch added: "amarok_3.0.1-1ubuntu1.debdiff"
Amarok 3.0.1 has been uploaded to Debian experimental:
https://tracker.debian.org/pkg/amarok
Worth syncing into Oracular, maybe?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933737
Title:
Please
To reproduce under Noble:
1. sudo apt install s3cmd
2. s3cmd --configure, input credentials for any S3 bucket you own (a local
Minio installation with Docker would do)
3. s3cmd ls s3://bucket-name
With the broken version 2.3.0-1:
TypeError: sequence item 1: expected str instance, bytes found
Public bug reported:
Under Noble, s3cmd 2.3.0 is completely broken because of an
incompatibility with Python 3.12, producing the exception:
https://github.com/s3tools/s3cmd/issues/1343
All operations fail with the error message:
TypeError: sequence item 1: expected str instance, bytes found
I also don't want ubuntu-pro-client to be a hard dependency of ubuntu-
minimal. Move it to recommends if you have to, but give the user an
option to delete it without touching the rest of the system.
I'm running Ubuntu as an open source OS on a production server and don't
want to hear about any
Thanks Christoph!
debdiff v3, incorporating this fix:
** Patch added: "quodlibet_4.6.0-1ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/quodlibet/+bug/2056101/+attachment/5756879/+files/quodlibet_4.6.0-1ubuntu1.debdiff
--
You received this bug notification because you are a
Corrected version of the debdiff, with Origin: upstream, and XSBC-
Original-Maintainer in debian/control.
** Patch added: "debdiff v2"
https://bugs.launchpad.net/ubuntu/+source/quodlibet/+bug/2056101/+attachment/5756877/+files/quodlibet_4.6.0-1ubuntu1.debdiff
--
You received this bug
That's the upstream fix, Alexander, you're right! I didn't realize
luk1337 committed it upstream and not just to Void Linux.
If you wish, you can change "Origin: vendor" in the patch header to
"Origin: upstream" with a link to that commit.
The fix should make it into the next upstream release.
Subscribed ubuntu-sponsors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056101
Title:
[noble] Quod Libet doesn't start: ModuleNotFoundError: No module named
'senf'
To manage notifications
)
-- Maia Everett Tue, 05 Mar 2024 01:52:29 +0200
Please review and sponsor the upload!
** Patch added: "quodlibet_4.6.0-1ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/quodlibet/+bug/2056101/+attachment/5752613/+files/quodlibet_4.6.0-1ubuntu1.debdiff
--
You receive
Public bug reported:
In Noble, with Python 3.12, Quod Libet refuses to start:
$ quodlibet
Traceback (most recent call last):
File "/usr/bin/quodlibet", line 11, in
from quodlibet.main import main
File "/usr/lib/python3/dist-packages/quodlibet/__init__.py", line 21, in
from
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964791
Title:
[SRU] Quod Libet fails to start with python 3.10, the
*** This bug is a duplicate of bug 1964791 ***
https://bugs.launchpad.net/bugs/1964791
Duplicate of bug #1964791.
** This bug has been marked a duplicate of bug 1964791
[SRU] Quod Libet fails to start with python 3.10, the default for Jammy
--
You received this bug notification because
** Summary changed:
- [SRU] Please sync quodlibet 4.5.0-1 from Debian unstable into jammy (was:
Quod Libet fails to start with python 3.10, the default for Jammy)
+ [SRU] Quod Libet fails to start with python 3.10, the default for Jammy
--
You received this bug notification because you are a
Attaching debdiff with a minimal fix. Verified to fix the bug on my
machine and to build correctly in pbuilder against current jammy.
In kinetic, 4.5.0-1, containing the fix, has been auto-synced from
Debian, so nothing needs to be done there.
** Patch added: "quodlibet_4.4.0-2ubuntu0.1.debdiff"
[Impact]
With Python 3.10 as default, Quod Libet 4.4.0 is completely broken for
Ubuntu 22.04 users. It fails to start with the following error:
E: 0.321: errorreport.main.errorhook: collection.py:27:: ImportError:
cannot import name 'Iterable' from 'collections'
** Summary changed:
- Quod Libet fails to start with python 3.10, the default for Jammy
+ [SRU] Please sync quodlibet 4.5.0-1 from Debian unstable into jammy (was:
Quod Libet fails to start with python 3.10, the default for Jammy)
--
You received this bug notification because you are a member
Public bug reported:
After the 5.8 kernel update, my Ubuntu 20.04.1 installation stopped
seeing any networks, either wireless or USB tethering from my phone. The
ifconfig command only showed the loopback interface.
I rolled back to 5.4.0-59-generic, and it works fine.
The offending package is
>From this thread
https://www.reddit.com/r/firefox/comments/brjj82/firefox_67_thinks_its_an_old_version_and_wont/?ref=readnext
"From looking at the compatibility.ini for the old profile vs the new
one it looks like the long version number for the newer Ubuntu is
slightly smaller.
18.04 profile:
Public bug reported:
Today I installed the Firefox 67 update on Ubuntu 18.04, then updated to
Ubuntu 18.10. After this, launching Firefox gave me a "Using an older
version of Firefox" message with only two options: create a new profile
or quit.
Apparently the Firefox 67 build for 18.10 thinks
Works for me and fixes the problem with rar archives on 16.10, even
without unrar installed. I would like it SRU'd 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/1636655
Title:
[SRU] Ark no
Public bug reported:
On vivid, calligrawords refuses to start:
$ calligrawords
calligrawords: error while loading shared libraries:
libkdeinit4_calligrawords.so: cannot open shared object file: No such file or
directory
** Affects: calligra (Ubuntu)
Importance: Undecided
Status:
Seems to be fixed by installing 2.9.0-0ubuntu2 from vivid-proposed.
** Summary changed:
- [vivid] libkdeinit4_calligrawords.so: cannot open shared object file: No such
file or directory
+ [vivid] libkdeinit4_calligrawords.so: cannot open shared object file: No such
file or directory
I can confirm this on Kubuntu Vivid with Plasma 5.
** Changed in: transmission (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/1212839
Title:
transmission-qt:
Reopening, it occurs for me too. And it *is* a qtcurve bug. It ignores
the font set in .gtkrc-2.0 and KDE GTK settings.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to gtk2-engines-qtcurve in Ubuntu.
https://bugs.launchpad.net/bugs/1078446
It also ignores the font set in KDE font settings (not for GTK). The
only way I could make it use the KDE system font is by commenting out
lines in kdeglobals, as outlined in the first post.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
27 matches
Mail list logo
