Re: Launch a minimal MATE DE

[tomas]

On Tue, Mar 08, 2022 at 01:54:11PM +1300, Richard Hector wrote:

[...]

> Just to solve the infinite recursion problem:
> 
> richard@zircon:~$ apt-file search bin/apt-file
> apt-file: /usr/bin/apt-file
> 
> so install the apt-file package :-)

Oh, a recursive fishing rod :-)

-- 
t


signature.asc
Description: PGP signature

Hardware Acceleration on Chromium 99

[Kevin Exton]

Hi all,

I'm running chromium 99 on Bullseye:

Version 99.0.4844.51 (Official Build) built on Debian 11.2, running on
Debian 11.2 (64-bit)

And I can't get hardware acceleration working. I've followed the
instructions here:

https://wiki.debian.org/Chromium#Video_acceleration

As well as a variety of other online sources of increasingly dubious
quality, so I've decided to come to the mailing lists and plea for help.

I'm running an Intel i5-5300U processor (so quite old I suppose):
- Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz

with Intel Integrated graphics:
- Intel(R) HD Graphics 5500 (BDW GT2)

I've tried running it both with and without vulkan drivers enabled.

I'm runnin Vulkan Instance:
Vulkan Instance Version: 1.2.162

and some of the errors logs I'm getting particularly at startup look like
this:

*** stack smashing detected ***: terminated
[32829:32829:0100/00.428969:ERROR:sandbox_linux.cc(377)]
InitializeSandbox() called with multiple threads in process gpu-process.
[32829:32829:0100/00.432878:ERROR:vulkan_device_queue.cc(227)] Vulkan:
Intel(R) HD Graphics 5500 (BDW GT2)

I'm checking to see if hardware accelerated video decoding is working by
viewing this video in 1080p HD:
https://www.youtube.com/watch?v=HmZKgaHa3Fg

and looking at the output of intel_gpu_top, where the row for Video/0 stays
at 0%.

Anyone got any ideas?

- Kevin

Re: linux kernel and nvidia - never ending story

[Felix Miata]

Stefan Monnier composed on 2022-03-07 18:25 (UTC-0500):

> I've heard several reports that Nouveau installations can
> be impacted by the installation of the proprietary Nvidia driver.

I believe this happens due to incomplete purging of all effects of having
attempted to install, or succeeding to install, then "removing", NVidia's
proprietary drivers. I have a bunch of old NVidia cards, 8 years old and older.
All are running purely on FOSS:

1-the nouveau kernel device driver/module

2-the modesetting DIX display device driver (usually; optionally: nouveau DDX)

#2 is the upstream default for AMD, Intel and NVidia GPUs. Unlike the
reverse-engineered, old, "experimental" and optional nouveau DDX display driver
from package xserver-xorg-video-nouveau, the modesetting DIX is newer 
technology,
and less dependent on device specifications NVidia withholds from FOSS 
developers.

Other than for the issue reported at:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006907
the FOSS drivers nouveau (module)/modesetting (DIX)/nouveau (DDX) provided by
Debian are fully suited to the needs of all my NVidia GPUs.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

Re: system lock up, not sure if related to "your system is too slow"

[songbird]

Vincent Lefevre wrote:
> On 2022-03-06 07:12:10 -0500, songbird wrote:
>> when i search for this kind of problem on the internet i come
>> up with:
>> 
>> https://itectec.com/ubuntu/ubuntu-why-am-i-getting-event-processing-lagging-behind-msg-in-ubuntu-20-10/
>> 
>> which says ignore it
>> 
>> while the following two give me the hope that it is some
>> kind of bug that might get fixed.
>> 
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968093
>> 
>> https://gitlab.freedesktop.org/xorg/driver/xf86-input-libinput/-/issues/46
>
> My opinion is that the behavior is normal and that the bug is the
> message itself, i.e. libinput misdetects a potential issue. No-one
> knows the cause yet, possibly a buggy timestamp. AFAIK, users
> (including me) who see this message haven't notice any slowness
> issue.
>
> Well, only if you get something like more than 100ms, perhaps you
> need to worry. But even 100ms, that's a fraction of second, thus
> not related to a lock up.

  thanks for the reply,  :)

  ok, any ideas how to get a crash instead of a lockup so i can
figure out where the problem might be?

  right now it locks solid and i can't get a core file at all.
all my log files are not giving me any clues either the Xorg
one is the only one that's telling me anything relating to
what is happening (some kind of IO issue).

  it happens when i'm typing, not at other times.  it might
only be typing in the browser (firefox).  i'm not sure if the
issue is the keyboard driver, the USB subsystems or xorg stuff
or the browser and i'm not sure how to get it isolated.  any
tips would be greatly appreciated.  :)

  all my drives are SSD and they seem to not be having trouble
recovering from the lockups when i restart the machine but it
would be nice to have some more detailed logs of what is going
on and those would need to be sync'd to make sure i'm catching
them completely, but that's better than the nothing i'm coming
up with now for figuring this out.  :)


  songbird

Re: system lock up, not sure if related to "your system is too slow"

[songbird]

Johann Klammer wrote:
...
> xserver-xorg-video-intel
> update that one. if that doesn't help, 

  already at the most current version in unstable.  i can
reinstall it without any problem.  all done.


> try 
> xserver-xorg-video-fbdev

  same as above.


> and as alast try
> xserver-xorg-video-vesa

  same as above.


> (you may have to edit /etc/X11/xorg.conf and possibly mess with kernel 
> modesetting, initrd and bootime parameters to get an acceptable resolution)
> you'll lose all `acceleration' as usual.
> but it might run more stable.
> no internet or video but ok for text processing(mcedit/pico/nano/vim but not 
> openoffice)

  it hasn't been terribly unstable, just a once in a while hard
lock up.  i'd like to figure out which part is the problem and
not wonder which it might be.

  one reason i run testing is to find issues before they go into
stable.  unfortunately, i'm not as well versed in this sort of
debugging as i'd like to be so i get to learn some new things.  :)

  if i have to get source code and compile it locally with certain
flags for debugging or whatever that is ok with me just so long
as it gets me further along in figuring out what this specific
problem is and what chunk of code it is coming from.


  songbird

Re: Launch a minimal MATE DE

[Richard Hector]

On 6/03/22 22:20, to...@tuxteam.de wrote:

On Sun, Mar 06, 2022 at 09:34:36AM +0100, Christian Britz wrote:



On 2022-03-06 09:30 UTC+0100, Richard Owlett wrote:

>> apt-get --no-install-recommends install mate-desktop-environment
> When I attempted to run startx I received the message
>> startx: command not found

Hi Richard,

I can't tell you anything about the dependencies but you could try to
install xinit package. This contains the startx command.


(Thanks, Christian, for the fish. Now I'll try to sell the rod ;-)

Reminder (paste this on a sticky note on your workshop wall :)

   apt-file search startx


Just to solve the infinite recursion problem:

richard@zircon:~$ apt-file search bin/apt-file
apt-file: /usr/bin/apt-file

so install the apt-file package :-)

Cheers,
Richard

cups/avahi-daemon - worrying logs

[Richard Hector]

Hi all,

I've recently set up a small box to run cups, to provide network access 
to a USB-only printer. It's a 32-bit machine running bullseye.


I'm seeing log messages like these:


Mar  7 15:47:47 whio avahi-daemon[310]: Record 
[Brother\032HL-2140\032\064\032whio._ipps._tcp.local#011IN#011SRV 0 0 631 
whio.local ; ttl=120] not fitting in legacy unicast packet, dropping.
Mar  7 15:47:47 whio avahi-daemon[310]: Record [whio.local#011IN#011 
fe80::3e4a:92ff:fed3:9e16 ; ttl=120] not fitting in legacy unicast packet, 
dropping.
Mar  7 15:47:48 whio avahi-daemon[310]: Record 
[Brother\032HL-2140\032\064\032whio._ipp._tcp.local#011IN#011SRV 0 0 631 
whio.local ; ttl=120] not fitting in legacy unicast packet, dropping.
Mar  7 15:47:48 whio avahi-daemon[310]: Record [whio.local#011IN#011 
fe80::3e4a:92ff:fed3:9e16 ; ttl=120] not fitting in legacy unicast packet, 
dropping.


Those link-local IPv6 addresses belong to the machine itself. It 
currently has no other IPv6 address(es) (other than loopback), but I 
should probably set that up.


Any hints as to what's going on?

Most of the hits I get from a web search are full of 'me too' with no 
answers.


Cheers,
Richard

Re: linux kernel and nvidia - never ending story

[Alexander V. Makartsev]

On 07.03.2022 23:49, Hans wrote:

Dear list,

how find the correct words, without being upset or stepping on someones feet.
But I believe, debian hates Nvidia, and debian does not want, to use Nvidia.

I am now for a long time using debian and also using nvidia graphic cards for
almost the same long time.

But whenever debian ships a new kernel version, the proprietrary nvidia kernel
modules can not be built. If lucky, there is a patch for it after months.

Yes, modern Nvidia cards are supported, but using an older notebook you can
not change the graphics card.
...
I have several older notebooks, that my customers use. They worked perfectly
with the proprietrary driver from Nvidia. But after update to bullseye, it was
hardly get them running again. And why? They have an old graphics card in
their notebooks, and they use Nvidia cards, specially the legacy 340xx.
Out of curiosity, can you name a model of nvidia GPU(-s) you have 
trouble with?
Are you sure you need legacy 340xx driver specifically? That version is 
for hardware that was released in 2009-2010 and older.

I think there is a chance you can install legacy 390xx version instead.
You can use 'nvidia-detect' program to check your hardware and get a 
driver version recommendation.



--
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄

Re: linux kernel and nvidia - never ending story

[Hans]

Am Montag, 7. März 2022, 20:46:40 CET schrieb Christian Britz:
Hi Christian, 

I feel to answer your post and have to correct some of your essays.
> Hello Hans,
> 
> I understand your frustration, I was also frustrated sometimes back when
> I used nVidia, but IMO Debian is not to blame here, the situation is
> completely the responsibility of nVidia.
> 
> 0. After reading your post again, I realize that sections 1 to 4 of my
> reply do not really apply to your situation. I leave them in my text
> though, because in my opionion they describe the general problem with
> nvidia quite well.
> 

Yes, good idea.

> 1. You are probably not talking about Debian stable and the kernel that
> ships with it. I have not checked, but the binary nVidia packages almost
> certainly have not disappeared from Debian stable non-free within a
> release cycle. Nothing should have broken with the latest dot kernel
> update. If you have problems, please specify further. Testing/unstable
> may break at any time, you have to deal with that, especially when using
> non-free software, which can only be fixed to a certain amount by the
> maintainers.

No, I DO talk about debian/stable! And when I mean stable, I talk about 
bullseye. I expect bullseye to work.
> 
> 2. If you are talking about kernels newer than the one in Debian stable,
> the problem is a problem by design that can and will happen with every
> Linux distribution. The reason is simply that the kernel interfaces
> which nVidia uses are not stable and were never intended to be used by
> non-free software. Eventually, nVidia will adapt their interface module
> and release a new driver package. Eventually, this will be integrated in
> Debian non-free. It is a race between the kernel developers and the
> nvidia developers, which nvidia never can win. If at all, you can blame
> Linus and the developers for not providing a stable interface for
> proprietary non-free software. I fear they will laugh at you, at best.
> Some kernel developers even have the opinion that it is a GPL violation
> what nvidia does.

Oh, no, this I see not this way. When there is a new kernel shipped, I expect 
that this does not break the system! I expect that at least the code, that is 
already existent, builds. This is not too much expected! Why is it called 
stable???


> 
> 3. If you are not satisfied how fast updated nvidia drivers are
> integrated into testing/unstable, you could always install the drivers
> manually from the website of nvidia. It is not very hard to do if you
> are used to Linux.
> 

This does NOT work., as I told. The drivers from the nvidia site do no more 
build with a new kernel version. Who is then to blame? Those, who change the 
kernel or those who do not change the drivers?  It is the kernel that changed, 
who breaks the system, not the driver, who has NOT chenged!

> 4. Given the circumstances, I feel the nvidia integration in Debian
> quite smooth, on stable it works almost out of the box (if your card is
> not too new, but that is a general issue with the stable concept of Debian).
Agreed! If you get the driver compiled, then it is working very well, if you 
get it compiled. 

> 
> 5. I only now realize that your card is actually too OLD, sorry. What
> should I say, the latest release of the 340 branch from nvidia is dating
> back to 2019.12.23. If they dont support their older products anymore
> themselves, do you expect Debian to hack their closed source driver?
> 

And what? 3 years is too old??? I do not expect the drivers to be improved, 
but I expect, that the drivers can be used further on! This is not to few to 
be expected, isn't it?

> 6. If nvidia would only be a little bit more cooperative, nouveau would
> be in a much better state. I found it usable for older cards, although
> the prorietary driver is of course much better in terms of performance
> and power saving.
> 

As I wrote, please read it again: The nouveau driver does not work for this 
card, X is totally unstable and so often freezing, that it can not be used. 
Did I tell, it is debian/stable? 

> 7. Intel (what I use these days) and AMD support Linux in a much cleaner
> way, avoiding many of the problems with the nvidia blob.
> 
Yes, may be, but who cares. As I wrote, it is not possible, to change the 
graphics card in noterbooks.

> 8. If you buy a system with the goal to use it over many years, I can
> only reccomend to choose hardware components wich can be well supported
> by free drivers. Please support companies that support Linux well, like
> Intel and AMD.
> 

Why shhould one? Shall I tell all customers, "Hey, throw away your 5 or 8 year 
old stuff!", which yesterday worked well and today, after an upgrade does no 
more, because a simple driver can not be compiled? No, that is the wrong way!

The whole story with Nvidia-modules is shit, and even when I no come into the 
doghouse, IMO it is NOT the fault of Nvidia, how the developers always try to 
tell! Someone ist just closing the 

Suggestion

[I - FSBR]

Hello, my name is iramar and I like Ubuntu a lot since the beginning,,,
unfortunately I don't know how to program but I even like to develop some
things and being so on social networks especially in the late g+ of Google
I really liked giving ideas to programmers and developers and even
companies anyway and so it came to the canonical owner of Ubuntu that I
really like to talk about and say that the Windows XP code that was leaked
on github WAS BECAUSE OF ME I was asking for this code or Windows 7 code
for a long time to solve the problem. question of standard linux hardware
drivers and nd windows games and programs on linux so,, the owner
of the code someone there at Microsoft in possession of the code granted my
request because it also achieved my vision for fix and complete linux on
the other hand i believe microsoft made windows 11 based on reports i sent
from my windows years ago my windows 7 ultimate 64bits was kind of all they
had available at the time hollow any program or game just install and it
works perfectly even with the limiting factor of RAM memory ddr2 8000 4Gb
runs perfectly and without any installation error the bed was ready
anyway. So what I want to ask for canonical that is the front of Linux
let's say as a representative of the Linux distribution is USE THE
WINDOWS XP CODE WHICH WAS DONATED IN GITHUB WITHOUT FEAR AND WITHOUT Pity
IT WAS DONATED BY THE OWNER IT COULD ONLY LEAK HE WHO WAS THE OWNER
UNDERSTAND, thus being in possession of this code let's get down to
business recently sudo Apt-get has been individually updated recently,,
Linus promised to update the next kernel to c11 or higher,, has a developer
working alone on optimizing Linux dependencies and repositories to update
modernize and optimize help him ,,, supports the all-in-one printers mainly
arrived hp and epson,, already has the USB and wireless video game
controller with the x360ce excellent USB video game control controller and
wireless I used it a lot on Windows, and Android arrived on Linux too,
so all you need to do is solve games and drivers and with the Windows XP
code you can do that, program all the peripheral hardware drivers of
the Windows updating the lines of code from Windows XP drivers updating to
Windows 7 updating the code and unifying with the Linux drivers code making
a single standard without failure type Windows peripheral driver A  Linux
peripheral driver B  unifying are standard AB peripheral driver without
failure recognition of any peripheral hardware on the market, you can use
both Linux and Windows without any problems, peripheral hardware, for
example an HP Epson Cannon Xerox Lexmark multifunction printer that is
installed on Windows,,, with the unification of the driver Windows XP new
standard *Windows 7 for Linux driver unified standard AB the same USB or
wireless all-in-one printer is also plugged into Linux and automatically
recognized by the new unified driver and it is the same with any peripheral
hardware to be used thanks to the new unified drivers with the help of the
XP source code that was donated on github question of Windows games and
programs and the Windows market we can program a compatibility layer
restricted to only files and DLLs that the software and games will use to
be able to be installed and work, nothing else matters, so do the
compatibility layer by improving wine or play on linux so that they create
this bed of files and folders necessary for windows software and windows
computer games understand that it is being installed on windows and will
only need the DLLs specific folders and some files and few APIs make this
compatibility bed updated and the story is dead GAMES AND WHAT INTERESTS IS
YOU WILL NOT NEED TO ESOERAR LEAVE THE NATIVE LINUX VERSION OR INSTALL THE
FU GAME NCI ONOU QUIETLY BE A FILE IN WINDOWS OR LINUX,,, and with the
Android emulator anbox or waydroid do the same thing the compatibility box
inserted in Linux so that I install the apk without needing any other
shortcut I just click install and Linux already has the compatibility bed
opens the wheel installs and creates the icon in the icon tray I click open
and use it simple like the same thing with Windows games and programs...
AND SO COMPLETE LINUX ONE TIME ,, LET'S GO TO HEAVY PROGRAMMING AND
EVERYTHING WILL WORK PERFECTLY AND LINUX CHANGES FOREVER!

  Remembering that you will need all the directX all the net-framework all
the visual c+++ all the DRM.DLL unifying with vulkan and opengl will be
top Besides Proton!


  HERE IS MY CONTENT ABOUT LINUX learn to get by on Linux, Linux office
with Android office +PDF pc print on any computer here

  https://www.facebook.com/17949318439/posts/3113785452229735/?app=fbl

You already have the Windows code that was donated on github now it becomes
a Linux configuration like the virtual box software, updates Windows XP
installs all directX all net-framework all visual c +++ updates HTML5 and
Java scr

Re: Pulseaudio goes into an uninterruptible sleep upon start

[Jude DaShiell]

Three things to do:
1) pulseaudio --cleanup-shm
reboot and see if you get any better results.
2) if 1 fails in the user directory rm -fr ~/.config/pulseaudio then
reboot and check for better results.
3) if 2 fails, remove pulseaudio from the machine and think about
installing and running pipewire if alsa really needs that much management.
Ways exist to run firefox without pulseaudio.  If memory serves pulseaudio
firefox may do this as a single command.


On Mon, 7 Mar 2022, Daniel Fishman wrote:

> Hello,
>
> I have an up-to-date Debian stable machine where pulseaudio becomes stuck
> as soon as it is started (goes into an uninterruptible sleep). I couldn't
> understand what is the cause for this behavior - maybe somebody can provide
> an idea?
>
> Initially, pulse worked as expected - the machine doesn't have any fixed
> output devices, sound was used via bluetooth headphones. Then one day I added
> a USB sound card dongle to the machine: this dongle worked immediately after
> it was
> plugged in, but after the first reboot the problem had occurred. It continued
> to occur even after I removed this USB dongle, removed ~/.config/pulse
> directory and rebooted the machine (and then done those actions many times
> with various variations - for example, to make sure that pulse doesn't create
> config dir between the time it removed & the machine is rebooted I rename
> pulseaudio executable, reboot, remove pulse's config dir, restore the exe and
> reboot again - doesn't help).
>
> Attached pulse's log created when it becomes stuck. From the log it seems to
> me that the problem starts when pulse fails to open a device pcmC0D0p, though
> it is not clear why it tries to open this device, since there is indeed no
> such device: /dev/snd contains the following:
>
> drwxr-xr-x  2 root root   60 Mar  7 19:55 by-path
> crw-rw+ 1 root audio 116,  6 Mar  7 19:55 controlC0
> crw-rw+ 1 root audio 116,  5 Mar  7 19:55 hwC0D2
> crw-rw+ 1 root audio 116,  2 Mar  7 19:55 pcmC0D1p
> crw-rw+ 1 root audio 116,  3 Mar  7 19:55 pcmC0D2p
> crw-rw+ 1 root audio 116,  4 Mar  7 19:57 pcmC0D3p
> crw-rw+ 1 root audio 116,  1 Mar  7 19:55 seq
> crw-rw+ 1 root audio 116, 33 Mar  7 19:55 timer
>
> output from 'aplay -lL':
>
> null
> Discard all samples (playback) or generate zero samples (capture)
> lavrate
> Rate Converter Plugin Using Libav/FFmpeg Library
> samplerate
> Rate Converter Plugin Using Samplerate Library
> speexrate
> Rate Converter Plugin Using Speex Resampler
> jack
> JACK Audio Connection Kit
> oss
> Open Sound System
> pulse
> PulseAudio Sound Server
> upmix
> Plugin for channel upmix (4,6,8)
> vdownmix
> Plugin for channel downmix (stereo) with a simple spacialization
> hw:CARD=sofhdadsp,DEV=1
> sof-hda-dsp,
> Direct hardware device without any conversions
> hw:CARD=sofhdadsp,DEV=2
> sof-hda-dsp,
> Direct hardware device without any conversions
> hw:CARD=sofhdadsp,DEV=3
> sof-hda-dsp,
> Direct hardware device without any conversions
> plughw:CARD=sofhdadsp,DEV=1
> sof-hda-dsp,
> Hardware device with all software conversions
> plughw:CARD=sofhdadsp,DEV=2
> sof-hda-dsp,
> Hardware device with all software conversions
> plughw:CARD=sofhdadsp,DEV=3
> sof-hda-dsp,
> Hardware device with all software conversions
> dmix:CARD=sofhdadsp,DEV=1
> sof-hda-dsp,
> Direct sample mixing device
> dmix:CARD=sofhdadsp,DEV=2
> sof-hda-dsp,
> Direct sample mixing device
> dmix:CARD=sofhdadsp,DEV=3
> sof-hda-dsp,
> Direct sample mixing device
> usbstream:CARD=sofhdadsp
> sof-hda-dsp
> USB Stream Output
>  List of PLAYBACK Hardware Devices 
> card 0: sofhdadsp [sof-hda-dsp], device 1: HDMI1 (*) []
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> card 0: sofhdadsp [sof-hda-dsp], device 2: HDMI2 (*) []
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI3 (*) []
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
>
>
> output for lspci:
>
> 00:0e.0 Multimedia audio controller: Intel Corporation Celeron/Pentium Silver
> Processor High Definition Audio (rev 06)
> Subsystem: Realtek Semiconductor Co., Ltd. Celeron/Pentium Silver
> Processor High Definition Audio
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B- DisINTx+
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> SERR-  Latency: 0, Cache Line Size: 64 bytes
> Interrupt: pin A routed to IRQ 133
> IOMMU group: 2
> Region 0: Memory at 70 (64-bit, non-prefetchable) [size=16K]
> Region 4: Memory at 7fffe0 (64-bit, non-prefetchable) [size=1M]
> Capabilities: [50] Power Management version 3
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA
> PME(D0+,D1-,D2-,D3hot+,D3cold+)
> Status: D

Re: linux kernel and nvidia - never ending story

[Christian Britz]

Hello Hans,

I understand your frustration, I was also frustrated sometimes back when
I used nVidia, but IMO Debian is not to blame here, the situation is
completely the responsibility of nVidia.

0. After reading your post again, I realize that sections 1 to 4 of my
reply do not really apply to your situation. I leave them in my text
though, because in my opionion they describe the general problem with
nvidia quite well.

1. You are probably not talking about Debian stable and the kernel that
ships with it. I have not checked, but the binary nVidia packages almost
certainly have not disappeared from Debian stable non-free within a
release cycle. Nothing should have broken with the latest dot kernel
update. If you have problems, please specify further. Testing/unstable
may break at any time, you have to deal with that, especially when using
non-free software, which can only be fixed to a certain amount by the
maintainers.

2. If you are talking about kernels newer than the one in Debian stable,
the problem is a problem by design that can and will happen with every
Linux distribution. The reason is simply that the kernel interfaces
which nVidia uses are not stable and were never intended to be used by
non-free software. Eventually, nVidia will adapt their interface module
and release a new driver package. Eventually, this will be integrated in
Debian non-free. It is a race between the kernel developers and the
nvidia developers, which nvidia never can win. If at all, you can blame
Linus and the developers for not providing a stable interface for
proprietary non-free software. I fear they will laugh at you, at best.
Some kernel developers even have the opinion that it is a GPL violation
what nvidia does.

3. If you are not satisfied how fast updated nvidia drivers are
integrated into testing/unstable, you could always install the drivers
manually from the website of nvidia. It is not very hard to do if you
are used to Linux.

4. Given the circumstances, I feel the nvidia integration in Debian
quite smooth, on stable it works almost out of the box (if your card is
not too new, but that is a general issue with the stable concept of Debian).

5. I only now realize that your card is actually too OLD, sorry. What
should I say, the latest release of the 340 branch from nvidia is dating
back to 2019.12.23. If they dont support their older products anymore
themselves, do you expect Debian to hack their closed source driver?

6. If nvidia would only be a little bit more cooperative, nouveau would
be in a much better state. I found it usable for older cards, although
the prorietary driver is of course much better in terms of performance
and power saving.

7. Intel (what I use these days) and AMD support Linux in a much cleaner
way, avoiding many of the problems with the nvidia blob.

8. If you buy a system with the goal to use it over many years, I can
only reccomend to choose hardware components wich can be well supported
by free drivers. Please support companies that support Linux well, like
Intel and AMD.

Best Regards,
Christian



On 2022-03-07 19:49 UTC+0100, Hans wrote:
> Dear list,
> 
> how find the correct words, without being upset or stepping on someones feet.
> But I believe, debian hates Nvidia, and debian does not want, to use Nvidia.
> 
> I am now for a long time using debian and also using nvidia graphic cards for 
> almost the same long time. 
> 
> But whenever debian ships a new kernel version, the proprietrary nvidia 
> kernel 
> modules can not be built. If lucky, there is a patch for it after months.
> 
> Yes, modern Nvidia cards are supported, but using an older notebook you can 
> not change the graphics card. 
> 
> But this is not a problem of Nvidia, not IMO it is a problem with the kernel 
> developers. Suddenly, with a  kernel the gcc was updated, oh, now the kernel 
> module does not want it any more. Wtf? Or, with the new kernel, the kernel 
> module crashes during building, but builds perfectly at the older kernel.
> 
> And suddenly the kernel modul of nvidia disappears completely from the repo, 
> problems solved? Get lost, you foolish users with old hardware, buy new 
> hardware! What???
> 
> Oh, and when someone says: Hey, use the nouveau driver, then tell him, 
> nouveau 
> is not working.
> 
> I have several older notebooks, that my customers use. They worked perfectly 
> with the proprietrary driver from Nvidia. But after update to bullseye, it 
> was 
> hardly get them running again. And why? They have an old graphics card in 
> their notebooks, and they use Nvidia cards, specially the legacy 340xx.
> 
> But: 
> 
> 1. no problem, Install nvidia kernel 340xx, oh no, it is no more in the repo, 
> but 
> 
> 2. no problem, hey, use nouveau, oh no, nouveau crashes and freezes X, but
> 
> 3. no problem, build just the downloaded 340xx from buster, oh no, does not 
> build, wrong gcc installed, gcc to new, but
> 
> 4. no problem, just downgrade gcc to the old one, oh no, many other packag

linux kernel and nvidia - never ending story

[Hans]

Dear list,

how find the correct words, without being upset or stepping on someones feet.
But I believe, debian hates Nvidia, and debian does not want, to use Nvidia.

I am now for a long time using debian and also using nvidia graphic cards for 
almost the same long time. 

But whenever debian ships a new kernel version, the proprietrary nvidia kernel 
modules can not be built. If lucky, there is a patch for it after months.

Yes, modern Nvidia cards are supported, but using an older notebook you can 
not change the graphics card. 

But this is not a problem of Nvidia, not IMO it is a problem with the kernel 
developers. Suddenly, with a  kernel the gcc was updated, oh, now the kernel 
module does not want it any more. Wtf? Or, with the new kernel, the kernel 
module crashes during building, but builds perfectly at the older kernel.

And suddenly the kernel modul of nvidia disappears completely from the repo, 
problems solved? Get lost, you foolish users with old hardware, buy new 
hardware! What???

Oh, and when someone says: Hey, use the nouveau driver, then tell him, nouveau 
is not working.

I have several older notebooks, that my customers use. They worked perfectly 
with the proprietrary driver from Nvidia. But after update to bullseye, it was 
hardly get them running again. And why? They have an old graphics card in 
their notebooks, and they use Nvidia cards, specially the legacy 340xx.

But: 

1. no problem, Install nvidia kernel 340xx, oh no, it is no more in the repo, 
but 

2. no problem, hey, use nouveau, oh no, nouveau crashes and freezes X, but

3. no problem, build just the downloaded 340xx from buster, oh no, does not 
build, wrong gcc installed, gcc to new, but

4. no problem, just downgrade gcc to the old one, oh no, many other packages 
need to be deinstalled, too, but

5. no problem, just do it, oh no, does not build with the latest kernel, but 

6. no problem, just downgrade the kernel, too, oh no, no kernel from bullseye 
is working, but 

7. no problem, just reactivate buster and install latest kernel from buster, 
and oh yes, 

8. old kernel from buster let build 340xx, but oh no, kernel old...

Well, I and these procedures are now accompanies me since years. New kernel, 
and building fails. Youu feel lost, you feel anger, can you believe me?

In earlier times, debian potato and so, there were always prebuild kernel 
modules for graphic cards, Nvidia or AMD or whatever. Today these are gone, 
and people with older cards are lost. IMO here debian lost a lots of its 
quality. 

I thought a long time, if I should write this, and maybe I have not found the 
correct words. I do not want to harsh anyone or attack anyone, you know what I 
mean. 

But I felt in my heart, I had to say it.

Please apologize, if someone is feeling agry about me now, this was not 
intended. And thanks for reading this.

Best regards

Hans

 

 

Re: XFCE: ALT-F1 shows the wrong menu on Debian 11

[Daniel Fishman]

This is the following issue:

https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/201

On 3/4/22 00:39, José Luis González wrote:

On Wed, 2 Mar 2022 17:30:38 +0500
"Alexander V. Makartsev"  wrote:


On 28.02.2022 02:32, José Luis González wrote:

Hi,


Hi Alexander,


Upon upgrading to Debian 11, the ALT+F1 key, which is assigned as a
shortcut to xfce4-popup-applicationsmenu, according to XFCE's settings,
no longer shows the applications menu and instead the app menu button
on my panel appears pressed without the menu unfolded. A second key
press shows the CTRL-ESC (xfdesktop --menu) menu, not the app menu.

What's going on? I'm suffering from the same in both machines I have
with Debian 11.

It looks like "xfce4-popup-applicationsmenu" is a simple wrapper Bash
script.
All it does is trying to execute "xfce4-panel" with a long line of
parameters and if that fails, fallback to execute "xfdesktop --menu"
instead.
Man page for "xfce4-panel" doesn't explain anything about
"--plugin-event" parameter, so it looks like it was reworked somehow.
The problem is that "xfce4-panel" never fails to execute with that
undocumented parameter, so fallback option doesn't work.
You can file a bug report about this, or change a command, assigned to
'Alt+F1' key combination, to
      "/usr/bin/xfce4-panel --plugin-event=applicationsmenu:popup"


The replacement command you propose doesn't work any better for me. I'm
going to file a bug report.

Best,
José Luis

Pulseaudio goes into an uninterruptible sleep upon start

[Daniel Fishman]

Hello,

I have an up-to-date Debian stable machine where pulseaudio becomes stuck
as soon as it is started (goes into an uninterruptible sleep). I couldn't
understand what is the cause for this behavior - maybe somebody can provide
an idea?

Initially, pulse worked as expected - the machine doesn't have any fixed
output devices, sound was used via bluetooth headphones. Then one day I added
a USB sound card dongle to the machine: this dongle worked immediately after it 
was
plugged in, but after the first reboot the problem had occurred. It continued
to occur even after I removed this USB dongle, removed ~/.config/pulse
directory and rebooted the machine (and then done those actions many times
with various variations - for example, to make sure that pulse doesn't create
config dir between the time it removed & the machine is rebooted I rename
pulseaudio executable, reboot, remove pulse's config dir, restore the exe and
reboot again - doesn't help).

Attached pulse's log created when it becomes stuck. From the log it seems to
me that the problem starts when pulse fails to open a device pcmC0D0p, though
it is not clear why it tries to open this device, since there is indeed no
such device: /dev/snd contains the following:

drwxr-xr-x  2 root root   60 Mar  7 19:55 by-path
crw-rw+ 1 root audio 116,  6 Mar  7 19:55 controlC0
crw-rw+ 1 root audio 116,  5 Mar  7 19:55 hwC0D2
crw-rw+ 1 root audio 116,  2 Mar  7 19:55 pcmC0D1p
crw-rw+ 1 root audio 116,  3 Mar  7 19:55 pcmC0D2p
crw-rw+ 1 root audio 116,  4 Mar  7 19:57 pcmC0D3p
crw-rw+ 1 root audio 116,  1 Mar  7 19:55 seq
crw-rw+ 1 root audio 116, 33 Mar  7 19:55 timer

output from 'aplay -lL':

null
Discard all samples (playback) or generate zero samples (capture)
lavrate
Rate Converter Plugin Using Libav/FFmpeg Library
samplerate
Rate Converter Plugin Using Samplerate Library
speexrate
Rate Converter Plugin Using Speex Resampler
jack
JACK Audio Connection Kit
oss
Open Sound System
pulse
PulseAudio Sound Server
upmix
Plugin for channel upmix (4,6,8)
vdownmix
Plugin for channel downmix (stereo) with a simple spacialization
hw:CARD=sofhdadsp,DEV=1
sof-hda-dsp,
Direct hardware device without any conversions
hw:CARD=sofhdadsp,DEV=2
sof-hda-dsp,
Direct hardware device without any conversions
hw:CARD=sofhdadsp,DEV=3
sof-hda-dsp,
Direct hardware device without any conversions
plughw:CARD=sofhdadsp,DEV=1
sof-hda-dsp,
Hardware device with all software conversions
plughw:CARD=sofhdadsp,DEV=2
sof-hda-dsp,
Hardware device with all software conversions
plughw:CARD=sofhdadsp,DEV=3
sof-hda-dsp,
Hardware device with all software conversions
dmix:CARD=sofhdadsp,DEV=1
sof-hda-dsp,
Direct sample mixing device
dmix:CARD=sofhdadsp,DEV=2
sof-hda-dsp,
Direct sample mixing device
dmix:CARD=sofhdadsp,DEV=3
sof-hda-dsp,
Direct sample mixing device
usbstream:CARD=sofhdadsp
sof-hda-dsp
USB Stream Output
 List of PLAYBACK Hardware Devices 
card 0: sofhdadsp [sof-hda-dsp], device 1: HDMI1 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofhdadsp [sof-hda-dsp], device 2: HDMI2 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI3 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0


output for lspci:

00:0e.0 Multimedia audio controller: Intel Corporation Celeron/Pentium Silver 
Processor High Definition Audio (rev 06)
Subsystem: Realtek Semiconductor Co., Ltd. Celeron/Pentium Silver 
Processor High Definition Audio
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: fee00478  Data: 
Capabilities: [70] Express (v1) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE- FLReset+
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+ FLReset-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ 
TransPend-
Kernel driver in use: sof-audio-pci
Kernel modules: snd_hda_intel, snd_soc_skl, snd_sof_pciI: [pulseaudio.orig] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted
I: [pulseaudio.orig] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted
D: [pulseaudio.orig] core-rtclock.c: Timer slack is set to 50 us.
I: [pulseaudio.orig] core-util.c: Failed to acquire high-priority scheduling: Permission denied
I: [pulseaudio.orig] main.c: This is PulseAudio 14.2
D: [pulseaudio.orig] main.c: Compilation CFLAGS: -g -O2 -ffile-prefix-map=/bu

Re: system lock up, not sure if related to "your system is too slow"

[Johann Klammer]

On 03/06/2022 09:10 PM, songbird wrote:
> Johann Klammer wrote:
> ...
>> Likely the xorg video driver.
>> Try installing the alternatives possible for your hardware.
>> avoid the closed source nvidias.
>> They've had the hard lock ups since about 2000.
>> nouveau and framebuffer ones will probably work.
> 
> 
>   hi, thanks for the hints, i just have the built in GPU for the CPU:
> 
> 
> # lscpu
> Architecture:x86_64
>   CPU op-mode(s):32-bit, 64-bit
>   Address sizes: 39 bits physical, 48 bits virtual
>   Byte Order:Little Endian
> CPU(s):  8
>   On-line CPU(s) list:   0-7
> Vendor ID:   GenuineIntel
>   BIOS Vendor ID:Intel(R) Corporation
>   Model name:Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz
> BIOS Model name: Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz
> CPU family:  6
> Model:   158
> Thread(s) per core:  1
> Core(s) per socket:  8
> Socket(s):   1
> Stepping:13
> CPU max MHz: 4900.
> CPU min MHz: 800.
> BogoMIPS:7200.00
> Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
> mc
>  a cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 
> ss 
>  ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc 
> art
>   arch_perfmon pebs bts rep_good nopl xtopology 
> nonstop_
>  tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor 
> ds_cp
>  l vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid 
> ss
>  e4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer 
> aes 
>  xsave avx f16c rdrand lahf_lm abm 3dnowprefetch 
> cpuid_f
>  ault invpcid_single ssbd ibrs ibpb stibp 
> ibrs_enhanced 
>  tpr_shadow vnmi flexpriority ept vpid ept_ad 
> fsgsbase t
>  sc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx 
> rdseed a
>  dx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 
> xsa
>  ves dtherm ida arat pln pts hwp hwp_notify 
> hwp_act_wind
>  ow hwp_epp md_clear flush_l1d arch_capabilities
> Virtualization features: 
>   Virtualization:VT-x
> Caches (sum of all): 
>   L1d:   256 KiB (8 instances)
>   L1i:   256 KiB (8 instances)
>   L2:2 MiB (8 instances)
>   L3:12 MiB (1 instance)
> NUMA:
>   NUMA node(s):  1
>   NUMA node0 CPU(s): 0-7
> 
> 
>   the following shows installed:
> 
> 
> # dpkg -l | grep video-intel
> 
> ii  xserver-xorg-video-intel 2:2.99.917+git20210115-1   
> amd64X.Org X server -- Intel i8xx, i9xx display driver
> 
> 
> # uname -a
> Linux rant 5.16.0-3-amd64 #1 SMP PREEMPT Debian 5.16.11-1 (2022-02-25) x86_64 
> GNU/Linux
> 
> 
> songbird
> 
xserver-xorg-video-intel
update that one. if that doesn't help, 
try 
xserver-xorg-video-fbdev
and as alast try
xserver-xorg-video-vesa
(you may have to edit /etc/X11/xorg.conf and possibly mess with kernel 
modesetting, initrd and bootime parameters to get an acceptable resolution)
you'll lose all `acceleration' as usual.
but it might run more stable.
no internet or video but ok for text processing(mcedit/pico/nano/vim but not 
openoffice)

Re: how many W a PSU for non-gaming Debian?

[Linux-Fan]

Emanuel Berg writes:


Linux-Fan wrote:

> It does, see
> https://www.techporn.ph/wp-content/uploads/ASUS-ROG-Strix-B450-F-Gaming-
Benchmark-1.jpg
> which is from your reference iv and explicitly shows an AMD R5
> 2600X processor being used.

I'll subtract 65W from it then ...

> * CPU power doubled to account for short-time bursts.

Double it, that something one should do?


In Intel world, yes :) In AMD world it seems to be slightly better, cf.:
https://images.anandtech.com/graphs/graph16220/119126.png

The TDP is given in the labels whereas the actual max power consumption
observed is in the diagram. It seems that for AMD systems, the most extreme
factor observed there is 143.22/105 = 1.364, so you might take that or round
up to 1.5 rather than factor 2 for AMD systems.


  Default TDP
  65W
  AMD Configurable TDP (cTDP)
  45-65W
  

> * RAM upped to 10W and SSD upped to 5W (depending on the
>   actual components, you might want to revert that but
>   computing an SSD with 3W makes your entire calculation
>   dependent on that specific model and if you upgrade that
>   later you'd have to take it into account).

I got these digits from
https://www.buildcomputers.net/power-consumption-of-pc-components.html
which is one of the first Google hits so I trust them for
now ...


The figures on that page for CPUs are misleading (they specify TDP range
which is not much related to actual power draw anymore, see linked figure
above).

The remainder of the figures seems sensible. Some GPUs are also known to
draw extreme peak loads (though usually that's only the "large" ones).

SSD highly depends on the model. No need to argue for one general figure
over the other. I think my SSD is specified 14W, but it is large and not the
"newest" :)

For RAM it seems that my figure is just a little too high and that your 3W
are more correct in modern times. Nice to know :)


As for upgrading that will be easy in this regard since I'll
read how many Watts on the box of whatever I get :)

device  model/category max W   note   ref
  -
  CPU AMD middle end, 4 cores 65 exact  [i]
  fans 80 mm (3K RPM)  9 3*3W =  9W[ii]
  120 mm (2K RPM) 12 2*6W = 12W[ii]
  GPU geforce-gt-710  19 exact[iii]
  mb  Asus ROG Strix B450-F Gaming AM4   166.2   exact, incl CPU   [iv]
  RAM DDR3 (1.5V)  3 actually, a DDR4  [ii]
  SSD  2.8 [ii]
  -

total:
  (ceiling (+ 65 (* 3 3) (* 2 6) 19 (- 166.2 65) 3 2.8))  ; 212 W

with +30% wiggle room:
  (ceiling (* 1.3 (+ 65 (* 3 3) (* 2 6) 19 (- 166.2 65) 3 2.8)))  ; 276 W


IMHO this is too low a figure for the system being planned. I am pretty sure
it _will_ run on a 300W PSU, BUT probably not stable for a long time and
under high loads.

HTH
Linux-Fan


  [i] https://www.amd.com/en/products/apu/amd-ryzen-3-3200g
 [ii] https://www.buildcomputers.net/power-consumption-of-pc-components.html
[iii] https://www.techpowerup.com/gpu-specs/geforce-gt-710.c1990
 [iv] 
https://www.techporn.ph/review-asus-rog-strix-b450-f-gaming-am4-motherboard/
  
https://www.techporn.ph/wp-content/uploads/ASUS-ROG-Strix-B450-F-Gaming-Benchmark-1.jpg


[...]


pgpJwCQrGCL_L.pgp
Description: PGP signature

Re: Which flavour for a 2GB RAM laptop?

[Andrew M.A. Cater]

On Mon, Mar 07, 2022 at 04:06:01PM +0900, 황병희 wrote:
> Ottavio Caruso  writes:
> 
> > One of my memory slot has died, so I am running a Thinkpad with 2GB
> > ram only. I have been told that, even if I put a 4GB ram module in, it
> > won't be as fast as 2x2GB ram (true? Stop me here if I am
> > wrong). Never mind put an 8GB stick; it might not even work.
> >
> > At the moment I'm running a heavily hacked LMDE4 (Buster) with a lot
> > of Mint customisations off. What flavour of Debian should I replace my 
> > LMDE4 with? And does it make any difference? My memory hogs are
> > Chromium and Firefox, the rest is ok.
> 
> Hi, grazie!
> 
> My 1st chromebook(codename: alex)[0] have only 2GB ram. At that time
> (in 2016), i did install Ubuntu 12.04 LTS via Crouton[1] at there the
> chromebook. It was not bad.
> 
> So if you want Debian, Jessie (stable)[2] seems proper to you, i guess. 
> (also it would be good to try xfce ho ho ho ^^^)
> 

XFCE / Mate or Cinnamon all work on my Lenovo Ideapad with 32G disk and 2G RAM.
Web browsing may be a little slower using Firefox - don't open too many tabs.
This with Bullseye (Debian 11).

Please don't use Jessie at this point: it's almost entirely out of support by
anybody. Consider using something completely up to date.

With every good wish, as ever,

Andy Cater


> REFERENCE: [0-2]
> [0]
> 
> [1] 
> [2] 
> 
> Sincerely, Linux fan Byung-Hee
> 
> -- 
> ^고맙습니다 _地平天成_ 감사합니다_^))//
> 

Re: system lock up, not sure if related to "your system is too slow"

[Vincent Lefevre]

On 2022-03-06 07:12:10 -0500, songbird wrote:
> when i search for this kind of problem on the internet i come
> up with:
> 
> https://itectec.com/ubuntu/ubuntu-why-am-i-getting-event-processing-lagging-behind-msg-in-ubuntu-20-10/
> 
> which says ignore it
> 
> while the following two give me the hope that it is some
> kind of bug that might get fixed.
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968093
> 
> https://gitlab.freedesktop.org/xorg/driver/xf86-input-libinput/-/issues/46

My opinion is that the behavior is normal and that the bug is the
message itself, i.e. libinput misdetects a potential issue. No-one
knows the cause yet, possibly a buggy timestamp. AFAIK, users
(including me) who see this message haven't notice any slowness
issue.

Well, only if you get something like more than 100ms, perhaps you
need to worry. But even 100ms, that's a fraction of second, thus
not related to a lock up.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: KDE: widget settings location

[Brad Rogers]

On Mon, 7 Mar 2022 17:00:07 +0100 (CET)
local10  wrote:

Hello local10,

>Perhaps I need to clarify that I'm looking for my Digital Clock widget
>*user* settings.

I realise that.  I'd hoped that there would be some pointers in the file
& url I sent.  It appears not.  I only had a cursory glance, TBH.

-- 
 Regards  _
 / )  "The blindingly obvious is never immediately apparent"
/ _)rad   "Is it only me that has a working delete key?"
You're so pretty, not to talk to you would be a crime
Baby Baby - The Vibrators


pgpi6Lbx_18Ap.pgp
Description: OpenPGP digital signature

Re: Google smtp and pop

[Eric S Fraga]

On Sunday,  6 Mar 2022 at 15:41, Brian wrote:
> I came across Disroot (disroot.org) the other day. Looks interesting
> and worth considering.

I've been using disroot for some time now for personal email (work is
Exchange unfortunately with 2FA which I access by using davmail).
Disroot works very well for me and comes with nextcloud as well which is
useful.

-- 
Eric S Fraga with org 9.5.2 in Emacs 29.0.50 on Debian 11.2

Re: KDE: widget settings location

[local10]

Mar 7, 2022, 15:37 by b...@fineby.me.uk:

> After a bit of DDG'ing, I found this folder;
>
> /usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/
>
> from the discussion at;
>

Perhaps I need to clarify that I'm looking for my Digital Clock widget *user* 
settings. When one goes into the "Configure Digital Clock" window and selects 
different options (for example, "Show date", "Time display format", "Date 
format", etc) where are they stored?

Thanks,

Re: KDE: widget settings location

[Brad Rogers]

On Mon, 7 Mar 2022 16:12:55 +0100 (CET)
local10  wrote:

Hello local10,

>That file seems to contain the list of widgets installed on the panel.
>Am looking for a place where "org.kde.plasma.digitalclock" settings are
>kept.

After a bit of DDG'ing, I found this folder;

/usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/

from the discussion at;



-- 
 Regards  _
 / )  "The blindingly obvious is never immediately apparent"
/ _)rad   "Is it only me that has a working delete key?"
You criticize us, you say we're sh*t, but we're up here doin' it
We're The League - Anti-Nowhere League


pgpwNuhLXNyu_.pgp
Description: OpenPGP digital signature

Re: KDE: widget settings location

[local10]

Mar 7, 2022, 15:01 by b...@fineby.me.uk:

> Right click on the clock widget brings up (amongst other things)
> 'Configure Digital Clock'.  That is to say, it does here.
>

Tried that but it doesn't work right.


> However, all I can find is;
> ~/.config/plasma-org.kde.plasma.desktop-appletsrc and search within for
> 'clock'
>

That file seems to contain the list of widgets installed on the panel. Am 
looking for a place where "org.kde.plasma.digitalclock" settings are kept.

Thanks

Re: KDE: widget settings location

[Brad Rogers]

On Mon, 7 Mar 2022 15:43:43 +0100 (CET)
local10  wrote:

Hello local10,

>Digital Clock widget and I can't find any way to fix it so maybe
>removing the clock

Right click on the clock widget brings up (amongst other things)
'Configure Digital Clock'.  That is to say, it does here.

However, all I can find is;
~/.config/plasma-org.kde.plasma.desktop-appletsrc and search within for
'clock'

I include my relevant section as an example, but note that I never
altered the config from the default:

[Containments][2][Applets][27]
immutability=1
plugin=org.kde.plasma.digitalclock


Also, I could be completely wrong about that being the correct settings
file.

-- 
 Regards  _
 / )  "The blindingly obvious is never immediately apparent"
/ _)rad   "Is it only me that has a working delete key?"
Let them go, set them free, let them be who they wanna be
Lovers Of Outrage - Penetration


pgpsB837q1rdu.pgp
Description: OpenPGP digital signature

KDE: widget settings location

[local10]

Hi,

Any ideas where KDE keeps its widget settings? Something got screwed up with 
the KDE Digital Clock widget and I can't find any way to fix it so maybe 
removing the clock settings file may help.

Thanks,

# cat /etc/debian_version && uname -a
11.2
Linux test 5.10.0-11-amd64 #1 SMP Debian 5.10.92-2 (2022-02-28) x86_64 GNU/Linux