Re: Upgrade errors

On Mon, Sep 08, 2025 at 09:50:04PM +, Andy Smith wrote: > > Setting up gitweb (1:2.47.3-0+deb13u1) ... > > dpkg: error processing package gitweb (--configure): > > installed gitweb package post-installation script subprocess returned > > error exit status 1 > > You'd have to look in to why

Re: Firmware upgrade on a Mac Mini A1283 ... 2008.

>> (as well as upgraded its firmware to allow the use of the "full" 3GB >> of RAM that the hardware can control). [...] > Memory upgrade may require firmware upgrade. Firmware upgrade > requires MacOS; correct? I believe so, yes. > Linux has replaced MacOS

Re: No ssh service after upgrade from trixie Sid to forky Sid

On 2025-09-12 05:48:22 +0100, mick.crane wrote: > On 2025-09-11 22:00, Thomas Schmitt wrote: > > My usual way to upgrade was > > apt-get update > > apt-get dist-upgrade > Without doing that RTFM I don't know what is the difference between > "upgrade"

Firmware upgrade on a Mac Mini A1283 ... 2008.

From: Stefan Monnier Date: Tue, 15 Jul 2025 12:43:20 -0400 > (as well as upgraded its firmware to allow the use of the "full" 3GB > of RAM that the hardware can control). This mini has 2 x (1 GiB) cards. According to Wikipedia, it should work with 4 GiB; possibly 8.

Re: Upgrade errors

On Mon, Sep 08, 2025 at 10:50:05PM +, Andy Smith wrote: > You are thinking of "a2ensite". "a2enconf" is for configuration snippets > in /etc/apache2/conf-available/. The "gitwen" file in there would have > been shipped with the package. It was ... I moved it sideways and replaced that directo

Re: No ssh service after upgrade from trixie Sid to forky Sid

On 2025-09-12 12:18, Greg Wooledge wrote: On Fri, Sep 12, 2025 at 05:48:22 +0100, mick.crane wrote: On 2025-09-11 22:00, Thomas Schmitt wrote: > Hi, > My usual way to upgrade was > apt-get update > apt-get dist-upgrade Without doing that RTFM I don't know what is the d

Re: No ssh service after upgrade from trixie Sid to forky Sid

On 2025-09-16 09:09:56 +0200, Thomas Schmitt wrote: > Hi, > > Greg wrote: > > > The release notes say when upgrading from Bookworm to Trixie to perform: > > > apt upgrade --without-new-pkgs > > > followed by: > > > apt full-upgrade > > Vin

Upgrade errors

I ran 'apt update' which told me the following, so I ran 'apt upgrade': 107 packages can be upgraded. Run 'apt list --upgradable' to see them. Notice: Repository 'https://deb.debian.org/debian trixie InRelease' changed its 'Version' value f

Re: No ssh service after upgrade from trixie Sid to forky Sid

Hi, i wrote: > > The release notes for buster > > https://www.debian.org/releases/buster/amd64/release-notes.en.txt > > do not recommend > > apt upgrade --without-new-pkgs > > but rather > > apt-get upgrade > > without extra options. Vincent Lefe

Re: No ssh service after upgrade from trixie Sid to forky Sid

Hi, i quoted: > >https://www.debian.org/releases/lenny/amd64/release-notes.en.txt > > "Please note that using apt-get is not recommended for the upgrade > > from etch to lenny." Greg Wooledge wrote: > That's VERY old. Yeah. We all were much younger b

Re: No ssh service after upgrade from trixie Sid to forky Sid

On Wed, Sep 17, 2025 at 13:33:09 +0200, Thomas Schmitt wrote: > In > https://www.debian.org/releases/lenny/amd64/release-notes.en.txt > it says > "Please note that using apt-get is not recommended for the upgrade >from etch to lenny. If you do not have aptitu

Re: No ssh service after upgrade from trixie Sid to forky Sid

On 2025-09-15, Vincent Lefevre wrote: >> >> The release notes say when upgrading from Bookworm to Trixie to perform: >> >> apt upgrade --without-new-pkgs >> >> followed by: >> >> apt full-upgrade >> >> Of course, all this after ha

Re: No ssh service after upgrade from trixie Sid to forky Sid

On Tue, Sep 16, 2025 at 09:09:56 +0200, Thomas Schmitt wrote: > > Is there any reason? > > The release notes say that "apt upgrade" before "apt full-upgrade" > avoids problems with removal of large numbers of packages. I believe the question was "Why did

Re: No ssh service after upgrade from trixie Sid to forky Sid

Hi, Greg wrote: > > The release notes say when upgrading from Bookworm to Trixie to perform: > > apt upgrade --without-new-pkgs > > followed by: > > apt full-upgrade Vincent Lefevre wrote: > This is new compared to the previous upgrades. I have this sequence already

Re: No ssh service after upgrade from trixie Sid to forky Sid

On 2025-09-13 16:33:51 -, Greg wrote: > On 2025-09-12, Vincent Lefevre wrote: > >> > >> Here's a table: > >> > >> Command NewPkgs RmvPkgs KeepDebs > >> -----

Re: No ssh service after upgrade from trixie Sid to forky Sid

Hi, it seems the upgrade is stuck with this conflict --- dpkg: error processing archive /var/cache/apt/archives/gnome-themes-extra-data_3.28-4_all.deb (--unpack): trying to overwrite '/usr/share/themes/Adwaita/gtk-2.0/ap

Re: No ssh service after upgrade from trixie Sid to forky Sid

On 13/09/2025 19:50, Greg Wooledge wrote: On Sat, Sep 13, 2025 at 12:26:44 +0700, Max Nikulin wrote: Is checked KeepDebs for apt-get above a typo? No. It's right there in the changelog entry that you cited: My bad. I am sorry, Greg. I can not figured out why I decided that this row is inco

Re: No ssh service after upgrade from trixie Sid to forky Sid

list '~o'" output prior to upgrade may help to avoid the issue with file conflict. On 12/09/2025 04:00, Thomas Schmitt wrote: i suspect that upgrading a 2 year old early "trixie" Sid VM remains incomplete and has spoiled ssh access to the VM from its Debian 12 host system.

[Solved] Re: No ssh service after upgrade from trixie Sid to forky Sid

Hi, it seems that i achieved the goal that motivated me to upgrade my Sid. lsb_release -a now says Description:Debian GNU/Linux forky/sid In hindsight it would have been more civilized to run apt-get purge gnome-themes-standard-data instead of mutilating /var/lib/dpkg/info/ and

Re: No ssh service after upgrade from trixie Sid to forky Sid

On 2025-09-12, Vincent Lefevre wrote: >> >> Here's a table: >> >> Command NewPkgs RmvPkgs KeepDebs >> --- --- --- >> apt-get upgrade

Re: No ssh service after upgrade from trixie Sid to forky Sid

On Sat, Sep 13, 2025 at 12:26:44 +0700, Max Nikulin wrote: > Is checked KeepDebs for apt-get above a typo? No. It's right there in the changelog entry that you cited: > > Please note that the behavior of apt-get is unchanged. The > > downloaded debs will be kept in the cache directory after

Re: No ssh service after upgrade from trixie Sid to forky Sid

pps.rc $ apt-file search gnome-themes-standard-data $ --- The same is reported on the pre-trixie Sid from which the upgrade adventure began. But dpkg -l dpkg -l gnome-themes'*' reports on trixie among other lines ii gnome-themes-standard-data 3.22.3-1 all Adwaita GTK+ 2 the

Re: No ssh service after upgrade from trixie Sid to forky Sid

On 2025-09-12 07:18:49 -0400, Greg Wooledge wrote: Command NewPkgs RmvPkgs KeepDebs --- --- --- apt-get upgrade✓ apt-get upgrade --with-new-pkgs✓ ✓ apt upgrade

Re: No ssh service after upgrade from trixie Sid to forky Sid

t. It is the reason why I mentioned "apt remove" above. As to ssh and libssl, my guess is that at certain point of upgrade process available (or running) executable file was inconsistent with dynamically loaded libraries present in the file system.

Re: No ssh service after upgrade from trixie Sid to forky Sid

On Fri, Sep 12, 2025 at 3:25 PM Thomas Schmitt wrote: > > it seems the upgrade is stuck with this conflict > --- > dpkg: error processing archive > /var/cache/apt/archives/gnome-themes-extra-data_3.28-4_al

My Trixie upgrade experience - not great, not terrible (KDE segfault)

"Only" two major issues: First, a realtek dkms driver I installed from source blocked kernel update (this one is my fault obviously). Second, a Plasma 6 segfault/crash after upgrade and login. It was a half-crash because toolbars were gone but I could still launch programs

Re: No ssh service after upgrade from trixie Sid to forky Sid

Hi, the provident upgrade instructions mention my problem under https://www.debian.org/releases/trixie/release-notes/upgrading.en.html#file-conflicts But the proposed remedy dpkg -r --force-depends package_name does not help, because the package gnome-themes-extra-data is stuck in limbo

Re: No ssh service after upgrade from trixie Sid to forky Sid

On 2025-09-12 07:18:49 -0400, Greg Wooledge wrote: > "apt-get upgrade" will not install any new packages, nor will it remove > any packages, in order to satisfy the dependencies. The .deb files are > left in place. > > "apt-get upgrade --with-new-pkgs" will in

Re: No ssh service after upgrade from trixie Sid to forky Sid

On Fri, Sep 12, 2025 at 05:48:22 +0100, mick.crane wrote: > On 2025-09-11 22:00, Thomas Schmitt wrote: > > Hi, > > > My usual way to upgrade was > > apt-get update > > apt-get dist-upgrade > Without doing that RTFM I don't know what is the difference

Re: No ssh service after upgrade from trixie Sid to forky Sid

On 2025-09-11 22:00, Thomas Schmitt wrote: Hi, My usual way to upgrade was apt-get update apt-get dist-upgrade Without doing that RTFM I don't know what is the difference between "upgrade" and "dist-upgrade". I had assumed that "upgrade" does the so

Re: No ssh service after upgrade from trixie Sid to forky Sid

On 12/09/2025 04:00, Thomas Schmitt wrote: E: Unable to read /tmp/apt-dpkg-install-cvyXki - opendir (2: No such file or directory) I hope, you have checked for obvious issues like no free space on /tmp tmpfs. Any idea how to solve this "OpenSSL version mismatch" while the VM is still runni

No ssh service after upgrade from trixie Sid to forky Sid

is message: --- Sep 11 21:15:30 ts6-sid sshd[31635]: OpenSSL version mismatch. Built against 3090, you have 30500010 ------- Upgrade to unstabl

Re: Upgrade errors

Hi, On Mon, Sep 08, 2025 at 11:13:29PM +0100, alain williams wrote: > On Mon, Sep 08, 2025 at 09:50:04PM +, Andy Smith wrote: > > > > Setting up gitweb (1:2.47.3-0+deb13u1) ... > > > dpkg: error processing package gitweb (--configure): > > > installed gitweb package post-installation script

Re: Upgrade errors

Hi, On Mon, Sep 08, 2025 at 10:29:19PM +0100, alain williams wrote: > > > Setting up systemd (257.8-1~deb13u1) ... > /usr/lib/tmpfiles.d/legacy.conf:14: Duplicate line for path "/run/lock", > ignoring. > > Apparently intentional but Luca's communication skills as usual leave a lot to

Re: [tde-users] blocked upgrade over "missing newline" (corrupt text file in /var/lib/dpkg/info/)

songbird composed on 2025-09-03 18:02 (UTC-0400): > Felix Miata wrote: >> songbird composed on 2025-09-01 11:40 (UTC-0400): >>> Felix Miata wrote: >>> ... How should or could I have fixed this using the package management system? >>> download via snapshot a copy of that package file and

Re: [tde-users] blocked upgrade over "missing newline" (corrupt text file in /var/lib/dpkg/info/)

Felix Miata wrote: > songbird composed on 2025-09-01 11:40 (UTC-0400): > >> Felix Miata wrote: >> ... >>> How should or could I have fixed this using the package management system? > >> download via snapshot a copy of that package file and then use >> reinstall. > > You mean the following (that y

Re: [tde-users] blocked upgrade over "missing newline" (corrupt text file in /var/lib/dpkg/info/)

Felix Miata wrote: ... > How should or could I have fixed this using the package management system? download via snapshot a copy of that package file and then use reinstall. songbird

Re: [tde-users] blocked upgrade over "missing newline" (corrupt text file in /var/lib/dpkg/info/)

songbird composed on 2025-09-01 11:40 (UTC-0400): > Felix Miata wrote: > ... >> How should or could I have fixed this using the package management system? > download via snapshot a copy of that package file and then use > reinstall. You mean the following (that you snipped)?: [quote] apt-get r

[tde-users] blocked upgrade over "missing newline" (corrupt text file in /var/lib/dpkg/info/)

InRelease Hit:3 http://ftp.debian.org/debian bookworm InRelease Hit:4 http://tde-mirror.yosemite.net/trinity/deb/trinity-r14.1.x bookworm InRelease Hit:5 http://www.deb-multimedia.org bookworm InRelease Reading package lists... Done # apt-get upgrade Reading package lists... Done Building dependency

Firefox URL-bar & autocomplete in Plasma (Wayland), broken since Trixie upgrade

Hi Not sure if this is a bug, and what package is causing it. Ever since the upgrade to Trixie, Firefox's URL bar has been behaving erratically, only on Plasma (Wayland). - The URL bar closes and reopens / redraws with every single keystroke. - Autocomplete in the URL bar is b

Re: Trixie upgrade that did not change lsb_release to trixie

I used a fix I found online: sudo dpkg-divert --local --remove --no-rename --divert /etc/os-release.debootstrap /etc/os-release then:sudo apt install --reinstall base-files seems to have the desired effect. On Sat, Aug 30, 2025 at 4:12 PM Steven Stryker wrote: > I am affected by this on two ma

Re: Trixie upgrade that did not change lsb_release to trixie

I am affected by this on two machines. thought I borked the update. On Sat, Aug 30, 2025 at 2:04 PM Greg Wooledge wrote: > On Sat, Aug 30, 2025 at 14:40:24 -0400, Eddie wrote: > > Upgraded to trixie from bookworm. Trixie up and running but the > lsb_release > > did not change to trixie. > > Did

Re: Trixie upgrade that did not change lsb_release to trixie

nown issue with that: https://bugs.debian.org/039 The bookworm was installed from a live release. The trixie was a dist-upgrade. Thank you I understand it now.

Re: Trixie upgrade that did not change lsb_release to trixie

On Sat, Aug 30, 2025 at 14:40:24 -0400, Eddie wrote: > Upgraded to trixie from bookworm. Trixie up and running but the lsb_release > did not change to trixie. Did you install from a "Live" image instead of a normal installer? There's a known issue with that: https://bugs.debian.org/039

Trixie upgrade that did not change lsb_release to trixie

Upgraded to trixie from bookworm. Trixie up and running but the lsb_release did not change to trixie. Any ideas? Eddie

Re: GPT4All since upgrade to Trixie

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Geert. > Geert Stappers writes: > On Mon, Aug 18, 2025 at 04:22:29PM +0100, Sharon Kimble wrote: >> tuxi...@posteo.de writes: >> > On Monday, August 18, 2025 2:42:14 PM CEST Sharon Kimble wrote: >> >> [Debug] (Mon Aug 18 12:54:28 2025): Sing

Bookworm to Trixie: suld-driver2-1.00.39hp script post-removal blocks the upgrade

Hi, During the upgrade from Bookworm to Trixie (apt full-upgrade), I’m getting an error message that blocks the process. This seems to be related to a driver I had installed for a Samsung printer from the repository https://www.bchemnet.com/suldr. I tried without success to delete suld

Re: GPT4All since upgrade to Trixie

On Mon, Aug 18, 2025 at 04:22:29PM +0100, Sharon Kimble wrote: > tuxi...@posteo.de writes: > > On Monday, August 18, 2025 2:42:14 PM CEST Sharon Kimble wrote: > >> [Debug] (Mon Aug 18 12:54:28 2025): SingleApplication: Cannot communicate > >> with primary so assuming primar- > > Thanks for replyin

Re: UVR5 not working after upgrade to Debian 13

another person has the same question they will be able to read your solution. That makes this discussion useful and helpful for anyone who might read it in the archive in future. I'll try to explain it briefly. 1. Installing pyenv as root. # apt update; apt upgrade -y # apt install

Re: UVR5 not working after upgrade to Debian 13

nother person has the same question > > they will be able to read your solution. That makes this discussion useful > > and helpful for anyone who might read it in the archive in future. > > I'll try to explain it briefly. > > 1. Installing pyenv as root. > # apt u

Re: UVR5 not working after upgrade to Debian 13

this discussion useful and helpful for anyone who might read it in the archive in future. I'll try to explain it briefly. 1. Installing pyenv as root. # apt update; apt upgrade -y # apt install pyenv 2. Follow the instruction exactly https://github.com/pyenv/pyenv?tab=readme-ov-f

Re: UVR5 not working after upgrade to Debian 13

On Mon, 18 Aug 2025 at 00:37, Budi Janto wrote: > On 8/14/25 3:45 PM, David wrote: > > On Thu, 14 Aug 2025 at 02:03, Max Nikulin wrote: > >> On 14/08/2025 07:30, Greg Wooledge wrote: > >>> On Thu, Aug 14, 2025 at 05:57:27 +0700, Budi Janto wrote: > from tkinter import tix >

Re: UVR5 not working after upgrade to Debian 13

On 8/14/25 3:45 PM, David wrote: On Thu, 14 Aug 2025 at 02:03, Max Nikulin wrote: On 14/08/2025 07:30, Greg Wooledge wrote: On Thu, Aug 14, 2025 at 05:57:27 +0700, Budi Janto wrote: from tkinter import tix ImportError: cannot import name 'tix' from 'tkinter' (/usr/lib/python3.13/tki

Re: unattended-upgrade still tracking Bookworm after upgrading to Trixie

xie | DEBIAN_VERSION_FULL=13.0 | ID=debian | HOME_URL="https://www.debian.org/"; | SUPPORT_URL="https://www.debian.org/support"; | BUG_REPORT_URL="https://bugs.debian.org/"; ` And unattended-upgrades is now back to normal: , | $ sudo unattended-upgrade --dry-run --ap

Re: unattended-upgrade still tracking Bookworm after upgrading to Trixie

Jeffrey Walton writes: > On Thu, Aug 14, 2025 at 11:10 PM Xiyue Deng wrote: > >> Hi, >> >> So I have a laptop that recently upgraded from Bookworm to Trixie >> without issues. Only that, unlike my other box (which also upgraded >> from Bookworm to Trixie

Re: unattended-upgrade still tracking Bookworm after upgrading to Trixie

Greg writes: > On 2025-08-15, Xiyue Deng wrote: >> >> , >>| # apt update >>| # apt upgrade --without-new-pkgs >>| # apt dist-upgrade >> ` > > Actually the notes say: > > ... > apt *full-upgrade*. > Ah indeed. But see below.

Re: unattended-upgrade still tracking Bookworm after upgrading to Trixie

On Thu, Aug 14, 2025 at 11:10 PM Xiyue Deng wrote: > Hi, > > So I have a laptop that recently upgraded from Bookworm to Trixie > without issues. Only that, unlike my other box (which also upgraded > from Bookworm to Trixie and has a working unattended-upgrade), I found &g

Re: unattended-upgrade still tracking Bookworm after upgrading to Trixie

On 2025-08-15, Xiyue Deng wrote: > > , >| # apt update >| # apt upgrade --without-new-pkgs >| # apt dist-upgrade > ` Actually the notes say: ... apt *full-upgrade*. I don't know if there's any difference between the two. I'm thinkng probably not, mais sait-t-on jamais?.

Re: unattended-upgrade still tracking Bookworm after upgrading to Trixie

Could this be your problem? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=039

Re: unattended-upgrade still tracking Bookworm after upgrading to Trixie

nd has a working unattended-upgrade), I found >> that all recent security updates are not upgraded automatically here. >> It turns out that unattended-upgrade seems to still be tracking >> Bookworm. > > You've said nothing about /etc/apt. That is where the current version &

Re: unattended-upgrade still tracking Bookworm after upgrading to Trixie

er box (which also upgraded > > from Bookworm to Trixie and has a working unattended-upgrade), I found > > that all recent security updates are not upgraded automatically here. > > It turns out that unattended-upgrade seems to still be tracking > > Bookworm. > > You've

Re: unattended-upgrade still tracking Bookworm after upgrading to Trixie

On Thu, 14 Aug 2025 17:44:55 -0700 Xiyue Deng wrote: > So I have a laptop that recently upgraded from Bookworm to Trixie > without issues. Only that, unlike my other box (which also upgraded > from Bookworm to Trixie and has a working unattended-upgrade), I found > that all rec

Re: UVR5 not working after upgrade to Debian 13

On 8/14/25 7:44 PM, Nate Bargmann wrote: * On 2025 14 Aug 04:18 -0500, Budi Janto wrote: Yes, probably the best way, I have to install Debian 12 on another CPU just to use UVR. Thanks David. Or just install Bookworm to a virtual machine using QEMU and running the virtual machine when you want

unattended-upgrade still tracking Bookworm after upgrading to Trixie

Hi, So I have a laptop that recently upgraded from Bookworm to Trixie without issues. Only that, unlike my other box (which also upgraded from Bookworm to Trixie and has a working unattended-upgrade), I found that all recent security updates are not upgraded automatically here. It turns out that

Re: UVR5 not working after upgrade to Debian 13

Nate Bargmann writes: > Or just install Bookworm to a virtual machine using QEMU and running the > virtual machine when you want to run that program. At least do that > until upstream fixes the dependency, which may already be done. I would prefer Distrobox with a Bookworm container for seamles

Re: UVR5 not working after upgrade to Debian 13

* On 2025 14 Aug 04:18 -0500, Budi Janto wrote: > Yes, probably the best way, I have to install Debian 12 on another CPU just > to use UVR. Thanks David. Or just install Bookworm to a virtual machine using QEMU and running the virtual machine when you want to run that program. At least do that un

Re: UVR5 not working after upgrade to Debian 13

On Thu, Aug 14, 2025 at 08:45:18 +, David wrote: > The Python documentation "Whats New In Python 3.13" [1] says: > Remove the tkinter.tix module (deprecated in Python 3.6) > [1] https://docs.python.org/3/whatsnew/3.13.html Oh, I see. Additional web searches bring up, for example,

Re: UVR5 not working after upgrade to Debian 13

On 8/14/25 3:45 PM, David wrote: As we can see in the lines from Max Nikulin, Bookworm ships Python 3.11 and Trixie ships Python 3.13. The Python documentation "Whats New In Python 3.13" [1] says: Remove the tkinter.tix module (deprecated in Python 3.6) So if Python has removed the module fr

Re: UVR5 not working after upgrade to Debian 13

On Thu, 14 Aug 2025 at 02:03, Max Nikulin wrote: > On 14/08/2025 07:30, Greg Wooledge wrote: > > On Thu, Aug 14, 2025 at 05:57:27 +0700, Budi Janto wrote: > >>from tkinter import tix > >> ImportError: cannot import name 'tix' from 'tkinter' > >> (/usr/lib/python3.13/tkinter/__

Re: UVR5 not working after upgrade to Debian 13

On 14/08/2025 07:30, Greg Wooledge wrote: On Thu, Aug 14, 2025 at 05:57:27 +0700, Budi Janto wrote: from tkinter import tix ImportError: cannot import name 'tix' from 'tkinter' (/usr/lib/python3.13/tkinter/__init__.py) There is no clue of the package named tix. Try installing tix. S

Re: UVR5 not working after upgrade to Debian 13

On 14/8/25 10:30, Greg Wooledge wrote: On Thu, Aug 14, 2025 at 05:57:27 +0700, Budi Janto wrote: from tkinter import tix ImportError: cannot import name 'tix' from 'tkinter' (/usr/lib/python3.13/tkinter/__init__.py) There is no clue of the package named tix. Try installing tix. See i

Re: UVR5 not working after upgrade to Debian 13

On Thu, Aug 14, 2025 at 05:57:27 +0700, Budi Janto wrote: > > > > > from tkinter import tix > > > > > ImportError: cannot import name 'tix' from 'tkinter' > > > > > (/usr/lib/python3.13/tkinter/__init__.py) > There is no clue of the package named tix. Try installing tix. See if you still g

Re: UVR5 not working after upgrade to Debian 13

On 8/13/25 7:50 AM, Greg Wooledge wrote: On Wed, Aug 13, 2025 at 07:21:47 +0700, Budi Janto wrote: On 8/12/25 8:22 PM, Greg Wooledge wrote: On Tue, Aug 12, 2025 at 19:57:37 +0700, Budi Janto wrote: from tkinter import tix ImportError: cannot import name 'tix' from 'tkinter' (/usr/lib/pyt

Re: UVR5 not working after upgrade to Debian 13

On Wed, Aug 13, 2025 at 07:21:47 +0700, Budi Janto wrote: > On 8/12/25 8:22 PM, Greg Wooledge wrote: > > On Tue, Aug 12, 2025 at 19:57:37 +0700, Budi Janto wrote: > > > from tkinter import tix > > > ImportError: cannot import name 'tix' from 'tkinter' > > > (/usr/lib/python3.13/tkinter/__init_

Re: UVR5 not working after upgrade to Debian 13

On 8/12/25 8:22 PM, Greg Wooledge wrote: On Tue, Aug 12, 2025 at 19:57:37 +0700, Budi Janto wrote: Hi, I need help to run UVR5 (https://github.com/Anjok07/ultimatevocalremovergui/releases/tag/v5.6) always get stuck requirement py packages. $ ~/UVR5$ ./uvr-startup.sh Traceback (most recent call

Re: UVR5 not working after upgrade to Debian 13

On Tue, Aug 12, 2025 at 19:57:37 +0700, Budi Janto wrote: > Hi, > > I need help to run UVR5 > (https://github.com/Anjok07/ultimatevocalremovergui/releases/tag/v5.6) > always get stuck requirement py packages. > > $ ~/UVR5$ ./uvr-startup.sh > Traceback (most recent call last): > File "/home/user

UVR5 not working after upgrade to Debian 13

Hi, I need help to run UVR5 (https://github.com/Anjok07/ultimatevocalremovergui/releases/tag/v5.6) always get stuck requirement py packages. $ ~/UVR5$ ./uvr-startup.sh Traceback (most recent call last): File "/home/user1/UVR5/UVR.py", line 42, in from gui_data.tkinterdnd2 import Tkinte

Re: grub-install problem after trixie upgrade

On Mon, Aug 11, 2025 at 01:57:00AM +, Andy Smith wrote: > > So ... on sda I could delete partition 1 so that it starts at 2048, but > > there > > is not enough room as the start of partition 2 is closer to the start of > > disk, > > so I would need to make it smaller on sdb as well. Summary

Re: grub-install problem after trixie upgrade

On 11.08.2025 02:40 Uhr Alain D D Williams wrote: > The disks are DOS partition table format not GUID as the > hardware/BIOS does not understand GUID - I bought it in 2012. In 2012 EFI was very common and even an old BIOS won't care, as it only looks at the boot sector, which can be used with GPT

Re: grub-install problem after trixie upgrade

Hi, On Mon, Aug 11, 2025 at 02:13:42AM +0100, Alain D D Williams wrote: > I have a clue ... If I run on the 2 disks "fdisk -l" I see a difference in > layout that I had not noticed before. The start of partition 1 is not in the > same place. On sda it is at 64 (not 2048) which might be the "short

Re: grub-install problem after trixie upgrade

e BIOS is. > Is this a fresh installation, or an upgrade? Is the RAID freshly made, or an > old > one reused without repartitioning? It is an upgrade from bookworm so an old RAID. > In recent years, the maximum size MBR gap has commonly been 31 sectors, or > 15872 > bytes, so

Re: grub-install problem after trixie upgrade

On Mon, Aug 11, 2025 at 12:53:06AM +, Andy Smith wrote: > I suspect you have too few sectors between the beginning of the disk and > the start of sda1 for grub to fit its core.img in. Please show us the > output of: > > # fdisk -u -l /dev/sda > # fdisk -u -l /dev/sdb > > (both harmless / rea

Re: grub-install problem after trixie upgrade

On Mon, Aug 11, 2025 at 01:36:03AM +0100, Alain Williams wrote: > I get an error installing grub. I do not understand it let alone know how to > fix it. Note that the error happens for sda but not sdb: > grub-install: warning: You have a short MBR gap and use advanced > config. Please incr

Re: grub-install problem after trixie upgrade

e disks are DOS partition table format not GUID as the hardware/BIOS does > not > understand GUID - I bought it in 2012. GPT/UEFI booting predates 2012 by a number of years. Your BIOS could well understand it if you desired to use it. Is this a fresh installation, or an upgrade? Is the RAID f

Re: grub-install problem after trixie upgrade

Hi, On Mon, Aug 11, 2025 at 01:36:03AM +0100, Alain D D Williams wrote: > The main disk is 2 disks in a RAID-1 pair (mirroring). The boot partition is > /dev/md0 that is built thus: > > md0 : active raid1 sda1[0] sdb1[1] > 510976 blocks super 1.2 [2/2] [UU] > > I get an error installing gr

grub-install problem after trixie upgrade

I have just upgraded from bookworm to trixie. An AMD FX (64 bit) machine. The main disk is 2 disks in a RAID-1 pair (mirroring). The boot partition is /dev/md0 that is built thus: md0 : active raid1 sda1[0] sdb1[1] 510976 blocks super 1.2 [2/2] [UU] I get an error installing grub. I do not

Re: Boring upgrade report

On Wed, Jul 30, 2025 at 08:46:42PM +, Andrew M.A. Cater wrote: > On Wed, Jul 30, 2025 at 06:33:39AM +0200, to...@tuxteam.de wrote: > > On Tue, Jul 29, 2025 at 07:47:14PM -0400, Stefan Monnier wrote: > > > > [Debian on Raspi] > > > > > PS: I wish this or something similar were "integrated" int

Re: Boring upgrade report

On Wed, Jul 30, 2025 at 06:33:39AM +0200, to...@tuxteam.de wrote: > On Tue, Jul 29, 2025 at 07:47:14PM -0400, Stefan Monnier wrote: > > [Debian on Raspi] > > > PS: I wish this or something similar were "integrated" into the > > Debian project. > > Gunnar Wolf has been at it for a while [1] (actu

Re: Boring upgrade report

On Tue, Jul 29, 2025 at 07:47:14PM -0400, Stefan Monnier wrote: [Debian on Raspi] > PS: I wish this or something similar were "integrated" into the > Debian project. Gunnar Wolf has been at it for a while [1] (actually, his work was my starting point a while ago when I needed it). It seems that

Re: Boring upgrade report

> I would very much like to understand your method for upgrading > a Raspberry Pi. I asked in the RPI support forum and was pointed to > a web post that explicitly says "upgrading" is not supported. > The only method to upgrade is to build a new image. I tried a scripted >

Re: Boring upgrade report

arge... > > > > Anders, > > I would very much like to understand your method for upgrading a > Raspberry Pi. I asked in the RPI support forum and was pointed to a web > post that explicitly says "upgrading" is not supported. The only method > to upgrade is to buil

Re: Boring upgrade report

s not supported. The only method to upgrade is to build a new image. I tried a scripted upgrade one time and it failed. I'd be happy to take this off list. Good point and thanks for the reply. I run the Debian-derivative from the RPI imager. I will have to give the Debian version a try.

Re: Boring upgrade report

27;ve upgraded a Debian machine since basically Debian Sarge... Anders, I would very much like to understand your method for upgrading a Raspberry Pi. I asked in the RPI support forum and was pointed to a web post that explicitly says "upgrading" is not supported. The only method t

Re: Boring upgrade report

berry Pi. I asked in the RPI support forum and was pointed to a web post that explicitly says "upgrading" is not supported. The only method to upgrade is to build a new image. I tried a scripted upgrade one time and it failed. I'd be happy to take this off list. -- Regards, John Boxall

Boring upgrade report

Just upgraded my Raspberry Pi 2 from Bookworm to Trixie. Nothing eventful happened, like every time I've upgraded a Debian machine since basically Debian Sarge...

Re: dh_installsystemd: don't start on install, but do restart on upgrade - if used

Hi Thomas, I'll try my luck with the Debhelper Maintainers; thanks for the advice. Regarding debian-mentors: I am aware of that list, but my question does not concern any Debian upload. It rather concerns a private package, for private use. Thomas Schmitt schreef op 2025-07-24 17:41: Hi, W

Re: dh_installsystemd: don't start on install, but do restart on upgrade - if used

Hi, William David Edwards wrote: > I have a question about dh_installsystemd. Since you got no answer since two days and there seems to be no mailing list for package "debhelper", i dare to point to debian-ment...@lists.debian.org where you could ask for advise. It's actually for people who wan

dh_installsystemd: don't start on install, but do restart on upgrade - if used

x27;s dh_installsystemd to install a systemd unit. Here is the behaviour I'm after: - The unit *is not* started on install. - If the unit is used, it *is* restarted on upgrade. In this case, 'used' could mean one of two things, both of which are fine with me: - The unit is activated/sta

Re: Trixie xorg crash (was: Trixie hangs during boot after upgrade)

On Mon, Jun 23, 2025 at 23:59:11 +0200, Rainer Dorsch wrote: > It seems that symlinks have been missing: > > root@h370:/usr/lib/x86_64-linux-gnu# ln -s libGL.so libGL.so.1 > root@h370:/usr/lib/x86_64-linux-gnu# ln -s libEGL.so libEGL.so.1 > root@h370:/usr/lib/x86_64-linux-gnu# > > cures the i

Re: Trixie xorg crash (was: Trixie hangs during boot after upgrade)

gt; > > > Rainer Dorsch: > > > Hi, > > > > > > I upgraded to Trixie some weeks back and had no serious issues during > > > all > > > upgrades so far. After the upgrade today, I rebooted and the Trixie > > > system > > > failed

  1   2   3   4   5   6   7   8   9   10   >