Re: KDE audio long broken.
On Fri, Sep 06, 2024 at 04:40:14PM +0100, Andy Wood wrote: > > > Can anybody point me towards a solution to this long standing Debian KDE > > > problem, which started around the time of the t64 transition upheaval. > > > Up-to-date Debian testing system. > > > Audio works with the VLC media player (via Pipewire to ALSA). > > > The Audio Volume Plasma Widget says "No output or input devices found". > > > > I expect the outcome to be the same, but still. Can you install > > pavucontrol and see what it shows? > > pavucontrol says it cannot connect to pulseaudio. I am guessing this is > because wireplumber > pipewire is now in control; pulseaudio has been removed > and replaced with pipewire-pulse? Yes, seamlessly. So do you have pipewire-pulse *running*? -- WBR, wRAR signature.asc Description: PGP signature
Re: KDE audio long broken.
On Thu, Sep 05, 2024 at 10:45:16AM +0100, Andy Wood wrote: > Hi, > > Can anybody point me towards a solution to this long standing Debian KDE > problem, which started around the time of the t64 transition upheaval. > > Up-to-date Debian testing system. > > Audio works with the VLC media player (via Pipewire to ALSA). > > The Audio Volume Plasma Widget says "No output or input devices found". I expect the outcome to be the same, but still. Can you install pavucontrol and see what it shows? -- WBR, wRAR signature.asc Description: PGP signature
Re: Carbon copy? (was: Re: Unstable stable KDE)
On Wed, Aug 28, 2024 at 03:31:05PM -0700, Soren Stoutner wrote: > In my experience, people usually include the author when replying on Debian > mailing lists, which is why I say it is the default. In my experience this is thankfully rare. -- WBR, wRAR signature.asc Description: PGP signature
Re: Unstable stable KDE (was: Fwd: too late to the party?)
This definitely belongs on debian-user@. -- WBR, wRAR signature.asc Description: PGP signature
Re: [OT] initramfstools 0.144 safe to use?
On Fri, Aug 23, 2024 at 01:56:56PM -0700, Soren Stoutner wrote: > On Thursday, August 22, 2024 10:25:02 AM MST Sedat Dilek wrote: > > TIPP: So, you should always have a 2nd linux-image installed for RESCUE > cases. > > Agreed. Although, if you have forgot to do so, you can always boot into the > Debian installer in rescue mode and fix your problem that way. Alternatively, keep a flash drive with GRML. -- WBR, wRAR signature.asc Description: PGP signature
Re: kwallet6 in testing
On Fri, Aug 23, 2024 at 05:45:13PM +0200, Erwan David wrote: > Upgrading my testing, I am proposed to install kwallet6 (and dependencies) > instead of kwallet5* Is it safe or should I wait for the whole Kde/Plasma 6 > to arrive in Testing ? TIL I have kwallet6 on sid. I haven't noticed any difference. -- WBR, wRAR signature.asc Description: PGP signature
Re: DO NOT UPGRADE KMOD to 33+20240816-1
On Wed, Aug 21, 2024 at 06:13:18PM +0200, Helge Reimer wrote: > Am Mittwoch, 21. August 2024, 18:02:13 CEST schrieb Andrey Rakhmatullin: > > > Consider installing apt-listbugs, it will not only tell you what these > > emails do but also tell you when the bug is fixed. > > apt-listbugs has been installed for a long time and didn't show anything > today. In general this means that either the bug has been fixed or you pinned the package and it's still pinned (and it will be no longer pinned after the apt-listbugs cronjob finds that the bug has been fixed). In this case the bug was indeed fixed (it's also always a good idea to double-check the bug itself if you are worried whether it's actually safe to upgrade. -- WBR, wRAR signature.asc Description: PGP signature
Re: DO NOT UPGRADE KMOD to 33+20240816-1
On Wed, Aug 21, 2024 at 05:41:34PM +0200, Helge Reimer wrote: > Am Montag, 19. August 2024, 16:58:15 CEST schrieb Sedat Dilek: > > dracut-install package needs to be rebuilt against latest libkmod2. > > Yesterday, apt dist-upgrade was supposed to remove dracut-install among other > things on my Sid. > > Today's apt upgrade installed kmod 33+20240816-2 and dist-upgrade was > supposed > to remove nothing. So I also did dist-upgrade. > > I restarted sddm and so far everything is working except for the black icon > for Dolphin. > > Xanmod Kernel was also updated and initramfs-tools ran smoothly. > dracut-install version is 103-1.1 > > Will my Sid boot or should I wait with a reboot? Consider installing apt-listbugs, it will not only tell you what these emails do but also tell you when the bug is fixed. -- WBR, wRAR signature.asc Description: PGP signature
Re: Qt upgrade
On Thu, May 23, 2024 at 09:44:10AM +0200, Martin Steigerwald wrote: > The new apt 2.9 and later makes it really obvious, so maybe warnings like > this are no longer needed? It was always obvious *shrug* -- WBR, wRAR signature.asc Description: PGP signature
Re: time_t 64 and KDE
On Mon, Mar 11, 2024 at 01:38:52PM +0100, Miguel A. Vallejo wrote: > plasma-workspace : Depends: gdb-minimal but it is not going to be installed > or > gdb > E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused > by held packages. > > > The interesting thing is GDB is installed: Sure, it means that apt wanted to remove it. > Is there anything I can do? Waiting for another pair of weeks? You can try upgrading packages that can be upgraded without removing others one by one. Or wait, or roll back to the usable version of your system. -- WBR, wRAR signature.asc Description: PGP signature
Re: Plasmashell crash: debugging symbols
Back to this, as I just hit the same problem I googled it and found https://bugs.kde.org/show_bug.cgi?id=454063 So it looks like it should only work (in stable and later, which have gdb >= 12) only if WITH_GDB12 is set at the drkonqi build time. https://salsa.debian.org/qt-kde-team/kde/drkonqi/-/blob/master/debian/rules doesn't set it, so I think this needs to be changed.
Re: Re: Is there a concept of related packages migration between unstable and testing that can be used for KDE Plasma?
On Thu, Nov 02, 2023 at 01:17:55PM -0400, Shmerl wrote: > > Yes, by setting versioned dependencies. > So is there a reason it's not done for Debian unstable → testing migration? Is there a reason it should be done, as you say later it's purely about version numbers? > It would help I think. Help what exactly? > > But I guess "an inconsistent mix" may mean something else? > > I simply mean versions mismatch like above.
Re: Is there a concept of related packages migration between unstable and testing that can be used for KDE Plasma?
On Thu, Nov 02, 2023 at 02:53:02AM -0400, Shmerl wrote: > Can maintainers set a group of packages as required to be migrated at the > same time for consistency? Yes, by setting versioned dependencies. > KDE Plasma in particular is versioning a bunch of related packages as a > group (versions 5.27.8, 5.27.9, etc.). > > But I noticed that they migrate from unstable to testing in chunks, some > earlier some later due to various hiccups for some of them. > > That can create an inconsistent mix for users of testing who upgrade that > without noticing. If this causes incompatible package sets, versioned deps should be added. But I guess "an inconsistent mix" may mean something else?
Re: Plasmashell crash: debugging symbols
On Tue, Oct 24, 2023 at 12:16:18PM +0100, piorunz wrote: > Why there are two ways to obtain debugging symbols? The -dbgsym packages is the official method since its introduction, debuginfod is newer and has some downsides, e.g. it's easier to pre-install all -dbgsym you could need and not worry about downloading symbols on demand. > I already have export DEBUGINFOD_URLS="https://debuginfod.debian.net";, > and this failed to resolve all problems in debugger, it seems. If > debuginfod works only partially, then it should not be recommended Sure, but unless someone else knows what is the cause of this problem it looks like you need to investigate it yourself.
Re: Plasmashell crash: debugging symbols
On Mon, Oct 23, 2023 at 07:51:54PM +0100, Brad Rogers wrote: > However, looking at the Debian packages web site indicates that debugsym > packages are only ever in unstable This is definitely not true.
Re: Plasmashell crash: debugging symbols
On Mon, Oct 23, 2023 at 08:08:56PM +0100, piorunz wrote: > > In general, assuming you use KDE packages from official Debian archives, > > you can use either debuginfod, or plain old debug packages. Have a look > > at the Wiki: HowToGetABacktrace[1]. It includes some hints on how to > > obtain the needed debug package names. Let us know if you'll have > > further issues or if there's something to improve in that Wiki text. > > > > [1]: https://wiki.debian.org/HowToGetABacktrace > > > > Hi Grzegorz, > > I already have debuginfod configured, It doesn't look like it worked then. > "or plain old debug packages" > > Where I can find those? The wiki page linked covers that too, in the "Installing the debugging symbols" section.
