Re: KDE Frameworks 5.103.0 and KDE Plasma 5.27

[Timothy M Butterworth]

On Tue, Feb 21, 2023 at 6:35 PM Patrick Franz  wrote:

> Hej,
>
> Am Dienstag, 21. Februar 2023, 20:09:13 CET schrieb Timothy M
> Butterworth:
> > Is Bookworm going to get Frameworks 5.103.0 and is there any estimated
> > time when Bookworm will get Plasma 5.27?
>
> Bookworm already has Plasma 5.27 beta (it's officially called 5.26.90),
> but both the Frameworks 5.103 and Plasma 5.27.0 have been uploaded to
> unstable and will be available in bookworm unless something weird
> happens.
>
> The Frameworks 5.103 will migrate to bookworm towards the end of the
> week, while Plasma 5.27.0 will migrate in the middle of next week.
>

Thanks Patrick


> We hope we can get Plasma 5.27.2 in before the next freeze.


> --
> Med vänliga hälsningar
>
> Patrick Franz
>
>
>

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

Re: KDE Frameworks 5.103.0 and KDE Plasma 5.27

[Patrick Franz]

Hej,

Am Dienstag, 21. Februar 2023, 20:09:13 CET schrieb Timothy M 
Butterworth:
> Is Bookworm going to get Frameworks 5.103.0 and is there any estimated
> time when Bookworm will get Plasma 5.27?

Bookworm already has Plasma 5.27 beta (it's officially called 5.26.90), 
but both the Frameworks 5.103 and Plasma 5.27.0 have been uploaded to 
unstable and will be available in bookworm unless something weird 
happens.

The Frameworks 5.103 will migrate to bookworm towards the end of the 
week, while Plasma 5.27.0 will migrate in the middle of next week.

We hope we can get Plasma 5.27.2 in before the next freeze.


-- 
Med vänliga hälsningar

Patrick Franz

Re: Kde: Dolphin file manager doesn't show comment content in the Details view mode?

[local10]

Jul 21, 2022, 11:46 by timothy.m.butterwo...@gmail.com:

> I tested it on Debian 11 and I am able to go to Properties/Details and add a 
> comment. The comment is then displayed. It looks like it might be a 
> regression. Are you running Bookworm or Sid?
>

Bookworm. Thanks

Re: Kde: Dolphin file manager doesn't show comment content in the Details view mode?

[tomas]

On Thu, Jul 21, 2022 at 01:18:38PM +0200, local10 wrote:
> Hi,
> 
> Tried adding comments to files (a useful feature in some cases) and the 
> comments are added and saved. A file comment can be seen by selecting the 
> file, doing a RMB click > Properties > Details > Comment. The comment is 
> there.
> 
> However, the Dolphin File Manager doesn't show the comment content in the 
> Details View Mode even though it shows the (empty) comment column. Am using 
> ext4.

File Comments aren't a standard OS feature; each file manager will
do its own thing [1] . Which file manager/desktop environment did
you use to add those comments?

Cheers

[1] And it's not as trivial as it looks at a first glance. I once
   fell into that rabbit hole trying to "fix" Gnome file emblems
   for somebody and I still carry the scars to show. Boy, am I
   glad for the command line ;-)

-- 
t


signature.asc
Description: PGP signature

Re: Kde: Dolphin file manager doesn't show comment content in the Details view mode?

[Timothy M Butterworth]

On Thu, Jul 21, 2022 at 7:19 AM local10  wrote:

> Hi,
>
> Tried adding comments to files (a useful feature in some cases) and the
> comments are added and saved. A file comment can be seen by selecting the
> file, doing a RMB click > Properties > Details > Comment. The comment is
> there.
>
> However, the Dolphin File Manager doesn't show the comment content in the
> Details View Mode even though it shows the (empty) comment column. Am using
> ext4.
>
> Any ideas? Thanks
>
> I tested it on Debian 11 and I am able to go to Properties/Details and add
a comment. The comment is then displayed. It looks like it might be a
regression. Are you running Bookworm or Sid?


> # cat /etc/debian_version && uname -a
> bookworm/sid
> Linux tst 5.18.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 5.18.5-1
> (2022-06-16) x86_64 GNU/Linux
>
>
>
>

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

Re: KDE Plasma - Arrastrar y soltar entre escritorios virtuales

[Camaleón]

El 2022-03-25 a las 12:45 -0300, JavierDebian escribió:

> El 25/3/22 a las 12:11, Camaleón escribió:
> > El 2022-03-25 a las 11:23 -0300, JavierDebian escribió:
> > > Utilizo KDE como escritorio para trabajar hace ya más de una década, con
> > > varios escritorios virtuales (EV).
> > > 
> > > Por ejemplo, en el EV1 tengo abierto un Dolphin, y en el EV4 Thunderbird.
> > > Siempre pude hacer lo siguiente: "capturar" con el ratón un archivo desde
> > > Dolphin, arrastrarlo a la barra del gestor de tareas donde están los EV,
> > > seleccionar el 4, se abre ese escritorio, y suelto en Thunderbird el 
> > > archivo
> > > en cuestión para que vaya como adjunto.
> > > 
> > > Bueno, ya desde hace un tiempo, no puedo hacer eso, el Escritorio Virtual 
> > > no
> > > cambia.
> > > 
> > > https://anonfiles.com/39l6Q0Qaxe/Arrastre2_mp4
> > > 
> > > ¿Alguno sabe de configuraciones o dónde meter los dedos para que esto 
> > > vuelva
> > > a ser lo que era?
> > > Tener que andar desde Thunderbird buceando en los árboles de directorio
> > > buscando el archivo a adjuntar hace perder mucho tiempo.
> > 
> > Cosas que probaría:

(...)

> > 5. Revisar la configuración de los escritorios virtuales, que en KDE
> > intuyo estará lleno de ajustes y opciones (Ajustes → comportamiento de
> > los espacios de trabajo...).
> Justamente, no encuentro nada para ajustar que habilite o impida eso.

En XFCE hay dos sitios donde mirar, quizá en KDE/Plasma también:

1. Configuración → ajustes del gestor de ventanas → áreas de trabajo
2. Botón derecho sobre el applet → configuración

Pero si antes funcionaba y ahora no... es raro que hayan eliminado la 
funcionalidad de manera premeditada y también que sea un bug porque 
la versión de KDE en Debian está bastante actualizada (5.x). 

> Esto empezó con Plasma, por lo que creo que es algo que se quedó colgado
> entre KDE 4 y KDE Plasma 5.

A ver si alguien que use Plasma te puede confimar si le pasa lo mismo.

Saludos,

-- 
Camaleón 

Re: KDE Plasma - Arrastrar y soltar entre escritorios virtuales

[JavierDebian]

El 25/3/22 a las 12:11, Camaleón escribió:

El 2022-03-25 a las 11:23 -0300, JavierDebian escribió:


Utilizo KDE como escritorio para trabajar hace ya más de una década, con
varios escritorios virtuales (EV).

Por ejemplo, en el EV1 tengo abierto un Dolphin, y en el EV4 Thunderbird.
Siempre pude hacer lo siguiente: "capturar" con el ratón un archivo desde
Dolphin, arrastrarlo a la barra del gestor de tareas donde están los EV,
seleccionar el 4, se abre ese escritorio, y suelto en Thunderbird el archivo
en cuestión para que vaya como adjunto.

Bueno, ya desde hace un tiempo, no puedo hacer eso, el Escritorio Virtual no
cambia.

https://anonfiles.com/39l6Q0Qaxe/Arrastre2_mp4

¿Alguno sabe de configuraciones o dónde meter los dedos para que esto vuelva
a ser lo que era?
Tener que andar desde Thunderbird buceando en los árboles de directorio
buscando el archivo a adjuntar hace perder mucho tiempo.


Cosas que probaría:

1. Crear un un usuario/perfil nuevo en KDE para ver si le pasa lo mismo,
y descartar así problemas con la basura acumulada en la caché del
usuario actual.

Hecho. El problema persiste.



2. Descartar que se trate de una funcionalidad no habilitada (p. ej.,
si usas Wayland en lugar de Xorg quizá no lo hayan implementado aún en
la versión que tengas de Plasma).

No uso Wayland hasta que no quede otra opción.



3. Comprobar si te funciona con otro tipo de archivo, es decir, prueba
a arrastrar/soltar una aplicación que tengas abierta.
No funciona con ninguna otra aplicación que esté en otro escritorio; 
sólo si está en el mismo escritorio.




4. Comrpobar si funciona con otra aplicación que no sea Thunderbird,
que es un poco tiquismiquis con los entornos de escritorio en Linux.

No, tampoco, cuando son escritorios distintos.



5. Revisar la configuración de los escritorios virtuales, que en KDE
intuyo estará lleno de ajustes y opciones (Ajustes → comportamiento de
los espacios de trabajo...).

Justamente, no encuentro nada para ajustar que habilite o impida eso.



Saludos,



Esto empezó con Plasma, por lo que creo que es algo que se quedó colgado 
entre KDE 4 y KDE Plasma 5.


JAP

Re: KDE Plasma - Arrastrar y soltar entre escritorios virtuales

[Camaleón]

El 2022-03-25 a las 11:23 -0300, JavierDebian escribió:

> Utilizo KDE como escritorio para trabajar hace ya más de una década, con
> varios escritorios virtuales (EV).
> 
> Por ejemplo, en el EV1 tengo abierto un Dolphin, y en el EV4 Thunderbird.
> Siempre pude hacer lo siguiente: "capturar" con el ratón un archivo desde
> Dolphin, arrastrarlo a la barra del gestor de tareas donde están los EV,
> seleccionar el 4, se abre ese escritorio, y suelto en Thunderbird el archivo
> en cuestión para que vaya como adjunto.
> 
> Bueno, ya desde hace un tiempo, no puedo hacer eso, el Escritorio Virtual no
> cambia.
> 
> https://anonfiles.com/39l6Q0Qaxe/Arrastre2_mp4
> 
> ¿Alguno sabe de configuraciones o dónde meter los dedos para que esto vuelva
> a ser lo que era?
> Tener que andar desde Thunderbird buceando en los árboles de directorio
> buscando el archivo a adjuntar hace perder mucho tiempo.

Cosas que probaría:

1. Crear un un usuario/perfil nuevo en KDE para ver si le pasa lo mismo,
y descartar así problemas con la basura acumulada en la caché del 
usuario actual.

2. Descartar que se trate de una funcionalidad no habilitada (p. ej., 
si usas Wayland en lugar de Xorg quizá no lo hayan implementado aún en 
la versión que tengas de Plasma). 

3. Comprobar si te funciona con otro tipo de archivo, es decir, prueba 
a arrastrar/soltar una aplicación que tengas abierta.

4. Comrpobar si funciona con otra aplicación que no sea Thunderbird, 
que es un poco tiquismiquis con los entornos de escritorio en Linux.

5. Revisar la configuración de los escritorios virtuales, que en KDE 
intuyo estará lleno de ajustes y opciones (Ajustes → comportamiento de 
los espacios de trabajo...).

Saludos,

-- 
Camaleón 

[SOLVED] Re: KDE: widget settings location

[local10]

Mar 7, 2022, 16:00 by loca...@tutanota.com:

> 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?
>

The KDE Digital Clock widget config settings are stored in the 
"~/.config/plasma-org.kde.plasma.desktop-appletsrc" file.

Thanks to everyone who responded.

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: 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

Re: KDE Icon query

[Peter Hillier-Brook]

On 28/01/2022 21:38, Hans wrote:

Am Freitag, 28. Januar 2022, 18:51:21 CET schrieb Peter Hillier-Brook:
Hi Peter,

the icons should be below /usr/share/icons/ and then within thwe required
themefolder.

If dolphin and the other apps are in the menus, but got no icon, try another
icon theme in the settings menu.

If then there is an icon, revert to the former theme and check, if dolphin and
the ones got now an icon.

Please note, that not all plasma themes got icons for ever application!

I am using i.e. oxygen where nightshift icon is missing, but in breeze is is
existent.

(Still could not discover, how to add a missing icon for an application in a
theme.)

Hope this helps.

Best

Hans


Hello All,

can anyone identify the file that holds the following KDE icons:
Application Launcher, Dolphin and Konsole?

I recently re-booted an already up-to-date bullseye system and they have
visually disappeared from the Panel, although the launchers themselves
are still present and functional.

Peter HB


Many thanks for your hints: I recovered them all by re-selecting 
"Breeze" as my theme. Why they disappeared during a re-boot is for 
another day.


Peter HB

Re: KDE Icon query

[Hans]

Am Freitag, 28. Januar 2022, 18:51:21 CET schrieb Peter Hillier-Brook:
Hi Peter,

the icons should be below /usr/share/icons/ and then within thwe required 
themefolder.

If dolphin and the other apps are in the menus, but got no icon, try another 
icon theme in the settings menu.

If then there is an icon, revert to the former theme and check, if dolphin and 
the ones got now an icon.

Please note, that not all plasma themes got icons for ever application!

I am using i.e. oxygen where nightshift icon is missing, but in breeze is is 
existent. 

(Still could not discover, how to add a missing icon for an application in a 
theme.)

Hope this helps.

Best

Hans  

> Hello All,
> 
> can anyone identify the file that holds the following KDE icons:
> Application Launcher, Dolphin and Konsole?
> 
> I recently re-booted an already up-to-date bullseye system and they have
> visually disappeared from the Panel, although the launchers themselves
> are still present and functional.
> 
> Peter HB

Re: KDE qui ne se lance plus correctement

[Erwan David]

Le 19/01/2022 à 20:24, didier gaumet a écrit :


Le mercredi 19 janvier 2022 à 18:54 +0100, BERTRAND Joël a écrit :
[...]

 Concernant KDE, je ne trouve rien dans les logs. J'ai tenté
une
réinstallation avec apt install --reintall, même résultat. Je ne
connais
pas KDE, j'ai installé ce gestionnaire de bureau pour configurer
facilement les sorties son. Où chercher ?

Je réponds à côté mais ça peut t'intéresser au cas où:

- Si ton environnement perso utilise Pulseaudio (cas de presque tous
les DE, je pense) tu peux installer Pavucontrol qui devrait te
permettre de choisr ce que tu veux en sortie son. Ceci sous n'importe
quel DE/WM du moment que Pulseaudio est lancé.

- Si ton environnement utilises encore Alsa directyement (me souviens
plus: t'es pas sous WindowMaker, ça doit utiliser Alsa, je crois), un
utiloitaire graphique style Alsamixergui devrait aussi convenir (sais
pas, ça fait tellement longtemps que je l'ai utilisé)?



SOus KDE, on peut aussi utiliser pavucontrol-qt, c'ets pavucontrol mais 
avec les même libs graphiques que KDE (donc tire moins de nouvelles 
dépendances)

Re: KDE qui ne se lance plus correctement

[didier gaumet]

Le mercredi 19 janvier 2022 à 18:54 +0100, BERTRAND Joël a écrit :
[...]
> Concernant KDE, je ne trouve rien dans les logs. J'ai tenté
> une
> réinstallation avec apt install --reintall, même résultat. Je ne
> connais
> pas KDE, j'ai installé ce gestionnaire de bureau pour configurer
> facilement les sorties son. Où chercher ?

Je réponds à côté mais ça peut t'intéresser au cas où:

- Si ton environnement perso utilise Pulseaudio (cas de presque tous
les DE, je pense) tu peux installer Pavucontrol qui devrait te
permettre de choisr ce que tu veux en sortie son. Ceci sous n'importe
quel DE/WM du moment que Pulseaudio est lancé.

- Si ton environnement utilises encore Alsa directyement (me souviens
plus: t'es pas sous WindowMaker, ça doit utiliser Alsa, je crois), un
utiloitaire graphique style Alsamixergui devrait aussi convenir (sais
pas, ça fait tellement longtemps que je l'ai utilisé)?

Re: KDE qui ne se lance plus correctement

[didier gaumet]

Le mercredi 19 janvier 2022 à 18:58 +0100, BERTRAND Joël a écrit :
> BERTRAND Joël a écrit :
> > [ 3065.757921] xs_tcp_setup_socket: connect returned unhandled
> > error -107
> > [ 3068.782698] xs_tcp_setup_socket: connect returned unhandled
> > error -107
> > [ 3155.938708] xs_tcp_setup_socket: connect returned unhandled
> > error -107
> > [ 3185.765546] xs_tcp_setup_socket: connect returned unhandled
> > error -107
> > [ 3234.173970] xs_tcp_setup_socket: connect returned unhandled
> > error -107
> > [ 3245.766629] xs_tcp_setup_socket: connect returned unhandled
> > error -107
> > [ 3248.790693] xs_tcp_setup_socket: connect returned unhandled
> > error -107
> > [ 3305.773160] xs_tcp_setup_socket: connect returned unhandled
> > error -107
> > [ 3305.821121] xs_tcp_setup_socket: connect returned unhandled
> > error -107
> > [ 3308.785220] xs_tcp_setup_socket: connect returned unhandled
> > error -107
> 
> Je constate aussi que ces erreurs apparaissent avec plusieurs
> instances
> de systemd-udev qui tournent simultanément et qui semble lancées par
> KDE.
> 
> 
tout ça plane bien au-dessus de mes compétences. Je constate seulement
qu'une recherche internet amène certains contenus réservés à du support
payant corporate (RedHat, Oracle) et que ça a l'air surtout en raport
avec NFS ou FTP (ton bouzin utlise NFS?).
Y a une question de ce genre ici:
https://access.redhat.com/discussions/3434091
Moi je ne saurais pas en tirer quelque chose d'utlie mais toi ça te
mettre peut-être sur la piste

Re: KDE qui ne se lance plus correctement

[BERTRAND Joël]

BERTRAND Joël a écrit :
> [ 3065.757921] xs_tcp_setup_socket: connect returned unhandled error -107
> [ 3068.782698] xs_tcp_setup_socket: connect returned unhandled error -107
> [ 3155.938708] xs_tcp_setup_socket: connect returned unhandled error -107
> [ 3185.765546] xs_tcp_setup_socket: connect returned unhandled error -107
> [ 3234.173970] xs_tcp_setup_socket: connect returned unhandled error -107
> [ 3245.766629] xs_tcp_setup_socket: connect returned unhandled error -107
> [ 3248.790693] xs_tcp_setup_socket: connect returned unhandled error -107
> [ 3305.773160] xs_tcp_setup_socket: connect returned unhandled error -107
> [ 3305.821121] xs_tcp_setup_socket: connect returned unhandled error -107
> [ 3308.785220] xs_tcp_setup_socket: connect returned unhandled error -107

Je constate aussi que ces erreurs apparaissent avec plusieurs instances
de systemd-udev qui tournent simultanément et qui semble lancées par KDE.

Re: Re : KDE Plasma - fenêtre toujours active dans la barre de tâches

[steve]

Le 26-10-2021, à 00:54:01 +0200, k6dedi...@free.fr a écrit :


Bonjour Steve,
Tu parles d'une application, mais laquelle ?


pixinsight


Certaines applis peuvent avoir des droits particuliers.


Rien trouvé dans les préférences de l'application en question.

Merci

Re : KDE Plasma - fenêtre toujours active dans la barre de tâches

[k6dedijon]

Bonjour Steve,
Tu parles d'une application, mais laquelle ?
Certaines applis peuvent avoir des droits particuliers.

Cassis




- Mail d'origine -
De: steve 
À: duf 
Envoyé: Sun, 24 Oct 2021 09:52:19 +0200 (CEST)
Objet: KDE Plasma - fenêtre toujours active dans la barre de tâches

Bonjour,

Je suis sous Bullseye à jour avec kde plasma.

J'ai un petit souci qui m'embête et que je n'arrive pas à résoudre par
moi-même.

J'ai configuré la barre de tâches pour qu'elle se masque automatiquement
après x secondes afin d'avoir un plus grand espace de travail. Mais une
application prend la main constamment sur les autres (elle est en
surimpression dans la barre de tâches) ce qui fait que la barre des
tâches ne disparaît jamais. 

J'ai désactivé les notifications, parcouru sans succès les différents
panneaux de configuration et je ne vois vraiment pas où modifier ce
comportement.

Toute aide serait la bienvenue !

Merci

Enc: Re: KDE Plasma não inicia após atualização

[Cráudio]

> Bom dia, Antônio!
>
> Obrigado pela resposta.
>
> Ontem continuei pesquisando e trata-se de uma incompatibilidade de versão do 
> libkdecorations2.so.5.23.0
>
> Veja só: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996670
>
> Fiz um downgrade neste pacote com o aptitude, preservando suas dependências, 
> e o Plasma voltou.
>
> Segundo consta nesse bug o pessoal está trabalhando nisso e devem liberar 
> alguma correção via atualização.
>
> Novamente, agradeço pela sua atenção!
>
> Abraços!
>
> Cráudio
>
> Sent with ProtonMail Secure Email.
>
> ‐‐‐ Original Message ‐‐‐
>
> Em quarta-feira, 20 de outubro de 2021 às 09:06, Antonio Terceiro 
> terce...@debian.org escreveu:
>
> > On Tue, Oct 19, 2021 at 10:26:42PM +, Cráudio wrote:
> >
> > > Olá, pessoal!
> > >
> > > Após simplesmente uma atualização de pacotes, o KDE Plasma passou a 
> > > congelar após efetuar o login no início do sistema, no modo gráfico.
> >
> > Qual a versão do Debian? A atualização foi de qual versão para qual
> >
> > outra?
> >
> > > O log em anexo foi produzido por meio do comando: grep erro 
> > > /var/log/syslog
> > >
> > > Alguém conseguiria me indicar algum caminho?
> > >
> > > Agradeço desde já pela atenção.
> > >
> > > Cráudio (vulgo Cláudio Brandão)
> > >
> > > Sent with ProtonMail Secure Email.
> >
> > > aa5720 error:0 in libkdecorations2.so.5.23.0[7fd9245f7000+f000]
> > >
> > > Oct 17 21:05:09 debian-xps sddm[2219]: Authentication error: "Process 
> > > crashed"
> > >
> > > Oct 17 21:05:09 debian-xps sddm[2219]: Authentication error: "Process 
> > > crashed"
> > >
> > > Oct 17 21:05:09 debian-xps kactivitymanagerd[4406]: The X11 connection 
> > > broke (error 1). Did the X11 server die?
> > >
> > > Oct 17 21:05:09 debian-xps kglobalaccel5[4412]: The X11 connection broke 
> > > (error 1). Did the X11 server die?
> >
> > Isso aqui diz que o sddm deu crash. veja os logs do sddm.service
> >
> > (jourcalctl -u sddm.service) e compartilhe aqui.

Re: KDE Plasma não inicia após atualização

[Antonio Terceiro]

On Tue, Oct 19, 2021 at 10:26:42PM +, Cráudio wrote:
> Olá, pessoal!
> 
> Após simplesmente uma atualização de pacotes, o KDE Plasma passou a congelar 
> após efetuar o login no início do sistema, no modo gráfico.

Qual a versão do Debian? A atualização foi de qual versão para qual
outra?

> O log em anexo foi produzido por meio do comando: grep erro /var/log/syslog
> 
> Alguém conseguiria me indicar algum caminho?
> 
> Agradeço desde já pela atenção.
> 
> Cráudio (vulgo Cláudio Brandão)
> 
> Sent with [ProtonMail](https://protonmail.com/) Secure Email.

> aa5720 error:0 in libkdecorations2.so.5.23.0[7fd9245f7000+f000]
> Oct 17 21:05:09 debian-xps sddm[2219]: Authentication error: "Process crashed"
> Oct 17 21:05:09 debian-xps sddm[2219]: Authentication error: "Process crashed"
> Oct 17 21:05:09 debian-xps kactivitymanagerd[4406]: The X11 connection broke 
> (error 1). Did the X11 server die?
> Oct 17 21:05:09 debian-xps kglobalaccel5[4412]: The X11 connection broke 
> (error 1). Did the X11 server die?

Isso aqui diz que o sddm deu crash. veja os logs do sddm.service
(jourcalctl -u sddm.service) e compartilhe aqui.


signature.asc
Description: PGP signature

Re: KDE and Pulseaudio; swapping users

[deloptes]

James Allsopp wrote:

> Hi,
> Does anyone have a solution for the problem that when I switch users, to
> have any sound as the new user, I have to su to root to kill the other
> users Pulseaudio. If I don't do this I'm left with a dummy sound card.

>From what I read recently but couldn't test because of time constrains is
that ConsoleKit/PolicyKit should manage this

Re : Kde inutilisable

[k6dedijon]

Bonjour à tous,
Voici un bon exemple qui me fait m'organiser en découpant mes partitions ainsi :
/ racine système 1
/ racine système 2
/ racine système 3
/ racine système 4
/boot (750 mo car il y a plusieurs systèmes)
/home système 1
/home système 2
/home système 3
/home système 4
/home/moi/mes_données

Je sors "mes données" sur une partition que je peux monter avec n'importe le 
quel des systèmes que j'essaye.
Je ne mets pas la pagaille dans /home car j'ai un répertoire /home par système.
Selon mes tentatives les répertoires racines sont de 5 à 20 Go
Les répertoires /home sont 2,5 à 8 Go (voire 10 à 15 si vous utilisez 
thunderbird et que vous conservez longtemps vos archives)

En espérant vous donner des idées.
Cassis



- Mail d'origine -
De: Francois Mescam 
À: debian-user-french@lists.debian.org
Envoyé: Sun, 27 Dec 2020 11:59:29 +0100 (CET)
Objet: Kde inutilisable

je suis en testing et ce matin j'ai fait la mise à jour de kde sauf 4 
paquets que j'ai gelé pour cause de dépendances non satisfaites.

Résultat lors du début d'une session mes diverses applis se lancent bien 
mais le tour des fenres ne s'affiche pas et donc pas possible de changer 
de fenêtre donc kde est à ce stade inutilisable.

je verrai demain s'il y a du nouveau.

Pour l'instant je me suis rabattu sur xfce.

-- 
Francois Mescam

Re: Kde inutilisable

[Erwan David]

Le 28/12/2020 à 11:00, Francois Mescam a écrit :
Je viens de faire la mise à jour d'aujourd'hui et maintenant c'est 
rentré dans l'ordre pour kde.


Francois Mescam

Le 27/12/2020 à 21:01, Jérôme a écrit :

Le Sun, 27 Dec 2020 11:59:29 +0100,
Francois Mescam  a écrit :


je suis en testing et ce matin j'ai fait la mise à jour de kde sauf 4
paquets que j'ai gelé pour cause de dépendances non satisfaites.

Résultat lors du début d'une session mes diverses applis se lancent
bien mais le tour des fenres ne s'affiche pas et donc pas possible de
changer de fenêtre donc kde est à ce stade inutilisable.

je verrai demain s'il y a du nouveau.

C'est pour ce genre d'ennui que j'aime bien aptitude, surtout en
testing/sid : je fais toujours un safe-upgrade et s'il y a des problème
de dépendances soit je diffère, soit j'y vais prudemment paquet par
paquet. En plus aptitude fournis quand même pas mal de solutions par
lui-même. En tout cas je n'upgrade jamais de force ni ne fige de
paquets, ça devient vite ingérable.

Pour la même raison je fais aussi du pinning avec Sid en backup, ça
permet la plupart du teps de ne pas rester coincé sur un paquet en
testing qui peut rester parfois longtemps avant de résoudre un problème:
C'est normal, il s'agit d'intégration pour construire une stable et
pas d'une version de production... Sid est plus souple et réactive à ce
niveau.






Merci, j'ai pas osé, car j'ai encore une petite 30aines de paquets qui 
ne passent pas en safe-upgrade

Re: Kde inutilisable

[Francois Mescam]

Je viens de faire la mise à jour d'aujourd'hui et maintenant c'est 
rentré dans l'ordre pour kde.


Francois Mescam

Le 27/12/2020 à 21:01, Jérôme a écrit :

Le Sun, 27 Dec 2020 11:59:29 +0100,
Francois Mescam  a écrit :


je suis en testing et ce matin j'ai fait la mise à jour de kde sauf 4
paquets que j'ai gelé pour cause de dépendances non satisfaites.

Résultat lors du début d'une session mes diverses applis se lancent
bien mais le tour des fenres ne s'affiche pas et donc pas possible de
changer de fenêtre donc kde est à ce stade inutilisable.

je verrai demain s'il y a du nouveau.

C'est pour ce genre d'ennui que j'aime bien aptitude, surtout en
testing/sid : je fais toujours un safe-upgrade et s'il y a des problème
de dépendances soit je diffère, soit j'y vais prudemment paquet par
paquet. En plus aptitude fournis quand même pas mal de solutions par
lui-même. En tout cas je n'upgrade jamais de force ni ne fige de
paquets, ça devient vite ingérable.

Pour la même raison je fais aussi du pinning avec Sid en backup, ça
permet la plupart du teps de ne pas rester coincé sur un paquet en
testing qui peut rester parfois longtemps avant de résoudre un problème:
C'est normal, il s'agit d'intégration pour construire une stable et
pas d'une version de production... Sid est plus souple et réactive à ce
niveau.

Re: Kde inutilisable

[Jérôme]

Le Sun, 27 Dec 2020 11:59:29 +0100,
Francois Mescam  a écrit :

> je suis en testing et ce matin j'ai fait la mise à jour de kde sauf 4 
> paquets que j'ai gelé pour cause de dépendances non satisfaites.
> 
> Résultat lors du début d'une session mes diverses applis se lancent
> bien mais le tour des fenres ne s'affiche pas et donc pas possible de
> changer de fenêtre donc kde est à ce stade inutilisable.
> 
> je verrai demain s'il y a du nouveau.

C'est pour ce genre d'ennui que j'aime bien aptitude, surtout en
testing/sid : je fais toujours un safe-upgrade et s'il y a des problème
de dépendances soit je diffère, soit j'y vais prudemment paquet par
paquet. En plus aptitude fournis quand même pas mal de solutions par
lui-même. En tout cas je n'upgrade jamais de force ni ne fige de
paquets, ça devient vite ingérable.

Pour la même raison je fais aussi du pinning avec Sid en backup, ça
permet la plupart du teps de ne pas rester coincé sur un paquet en
testing qui peut rester parfois longtemps avant de résoudre un problème:
C'est normal, il s'agit d'intégration pour construire une stable et
pas d'une version de production... Sid est plus souple et réactive à ce
niveau.

Re: Kde inutilisable

[Erwan David]

Le 27/12/2020 à 11:59, Francois Mescam a écrit :
> je suis en testing et ce matin j'ai fait la mise à jour de kde sauf 4
> paquets que j'ai gelé pour cause de dépendances non satisfaites.
>
> Résultat lors du début d'une session mes diverses applis se lancent
> bien mais le tour des fenres ne s'affiche pas et donc pas possible de
> changer de fenêtre donc kde est à ce stade inutilisable.
>
> je verrai demain s'il y a du nouveau.
>
> Pour l'instant je me suis rabattu sur xfce.
>

Merci de prévenir, j'ai failli me faire avoir... Je vais attendre un peu.

Re: KDE run Dolphin as root?

[Andrei POPESCU]

On Vi, 19 iun 20, 09:58:40, to...@tuxteam.de wrote:
> On Fri, Jun 19, 2020 at 05:54:38AM +0300, Andrei POPESCU wrote:
> > On Mi, 17 iun 20, 10:55:55, to...@tuxteam.de wrote:
> > > 
> > > Making things user friendly (something we *gotta* do) means sometimes
> > > taking decisions for the user. Where's the limit? Where's too much
> > > (authoritarian software)? Where's too litle (RTFM software)? You'll
> > > be wrong most of the time for some users, and some of the time for
> > > most users.
> > 
> > In my opinion Chrome OS (and I assume Chromium OS as well) gets many 
> > things right, Debian could learn a lot from it.
> 
> That's the point. In Sally's opinion it's Mac. In Betty's, it's Windows
> (but not after '95). In Sue's, OTOH...
> 
> (BTW. for all I've seen of Chrome OS, I'd either run away screaming or
> scrub it from the computer, depending on my momentary mood).

Chrome OS itself is definitely not something for the typical debian-user 
subscriber, as it is "just enough OS to run Chrome" ;)

What would be interesting to at least consider for Debian (in my, not so 
humble, opinion):


By default it is using secured boot (signed kernel, etc.) with the user 
data partition fully encrypted and no root access whatsoever. It can be 
switched to "developer mode" with full root access by a special 
(documented) boot procedure, which involves full erasure of all user 
data (for privacy reasons).


Robust and user friendly auto-update mechanism. There is just one 
notification informing you to reboot to upgrade. On the next reboot you 
are running the upgrade, not additional waiting time involved.

As far as I know it uses two "boot" (system?) partitions. The upgrade is 
written to the "other" partition and marked to be booted from next time.  
The "current" partition is kept as backup with an automatic fall-back 
mechanism (never seen it trigger as far as I could tell).

During the lifetime of my Acer Chromebook R13 I've had countless 
updates, including a "firmware" upgrade (u-boot?) and a filesystem 
change (to ext4 I think, don't recall what it had before), all without a 
glitch. These did involve some (one?) additional confirmation and the 
filesystem change did take a while (unavoidable).

For a while I was also running the "beta" channel, similar to Debian's 
testing, no issues with the upgrades.


Too many apps installed? Some things appear to now work properly? Are 
you selling / giving away the Chromebook? No problem. Just use 
"Powerwash" (something like a "factory reset") to restore the OS to its 
basic state (with all updates applied) and erase all user data.

Sounds quite similar to what was recently discussed here on the list.


As I wrote above, it's not for the typical debian-user subscriber. It is 
however a really good option for the kind of users that spend 95% of the 
time in a browser. The other 5% are most likely covered by Chrome and 
Android Apps, if the user is willing to ignore / doesn't care about the 
privacy issues.

Building something similar with just Debian is mostly doable, though by 
far not easy.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: KDE run Dolphin as root?

[tomas]

On Fri, Jun 19, 2020 at 05:54:38AM +0300, Andrei POPESCU wrote:
> On Mi, 17 iun 20, 10:55:55, to...@tuxteam.de wrote:
> > 
> > Making things user friendly (something we *gotta* do) means sometimes
> > taking decisions for the user. Where's the limit? Where's too much
> > (authoritarian software)? Where's too litle (RTFM software)? You'll
> > be wrong most of the time for some users, and some of the time for
> > most users.
> 
> In my opinion Chrome OS (and I assume Chromium OS as well) gets many 
> things right, Debian could learn a lot from it.

That's the point. In Sally's opinion it's Mac. In Betty's, it's Windows
(but not after '95). In Sue's, OTOH...

(BTW. for all I've seen of Chrome OS, I'd either run away screaming or
scrub it from the computer, depending on my momentary mood).

How to cater to all of those? And, more importantly: how to enable (or
better: seduce) all of those to tinker away, if they wish to do so?

After all, that last point is the "mission statement" of free software.
There was a meme around one of the first free smartphones, the OpenMoko:

  "WARRANTY VOID WHEN NOT OPENED" [1] [2]

I think in these days, where the attacks on freedom come sometimes in
the guise of convenience rather than constraint (in some privileged
parts of the world, at least!), this point becomes ever more important.

Cheers

[1] https://www.vanille.de/blog/openmoko-10-years-after-mickeys-story/
[2] http://fidzu.com/fidzu/openmoko

-- tomás


signature.asc
Description: Digital signature

Re: KDE run Dolphin as root?

[Andrei POPESCU]

On Mi, 17 iun 20, 10:55:55, to...@tuxteam.de wrote:
> 
> Making things user friendly (something we *gotta* do) means sometimes
> taking decisions for the user. Where's the limit? Where's too much
> (authoritarian software)? Where's too litle (RTFM software)? You'll
> be wrong most of the time for some users, and some of the time for
> most users.

In my opinion Chrome OS (and I assume Chromium OS as well) gets many 
things right, Debian could learn a lot from it.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: KDE run Dolphin as root?

[tomas]

On Tue, Jun 16, 2020 at 04:51:39PM -0700, Gary L. Roach wrote:

[...]

> Miacopa

All is well, and sorry if my tone was... rough.

> I think I was venting. I am so frustrated with this whole Dolphin
> mess that I may have gone overboard [...]

I feel your pain. Not from KDE land, but I think it's a basic problem.

We are being torn apart by the attempt to democratize free software
(which is something we *must* attempt!).

Making things user friendly (something we *gotta* do) means sometimes
taking decisions for the user. Where's the limit? Where's too much
(authoritarian software)? Where's too litle (RTFM software)? You'll
be wrong most of the time for some users, and some of the time for
most users.

As an example: yesterday, I got a laptop from a customer. Doesn't
boot. Thinkpad something something, with Ubuntu on it. Now I think
it's so awesome that a psychotherapist runs Ubuntu for his business.
He gets a special price.

What was the problem? Basically a b0rked kernel upgrade[1], where
the corresponding Intel CPU firmware was missing. The two youngest
kernels in the Grub menu didn't boot, the third oldest did (though
I found about that in a somewhat roundabout way: it seems at least
80% of our profession consists of barking up the wrong tree, but
I disgress).

Back to our topic: this customer has auto-upgrade running. While
his box was up and running, it did two (!) kernel updates without
the owner even noticing[2]. This is an incredible luxury, but in
this case the effect was that after the next shutdown the box didn't
boot, with no obvious reason for him.

What is "the right" degree of automation? Finding an adequate answer
to this will be our job for the next ~20 years. I don't expect a
scalar number as answer :-)

Cheers

[1] https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1882890
[2] "But there was this notification saying the box needs a reboot, blah,
   blah" you'll say. Yeah, right.

-- tomás


signature.asc
Description: Digital signature

Re: KDE run Dolphin as root?

[didier . gaumet]

Le mercredi 17 juin 2020 01:40:05 UTC+2, Gary L. Roach a écrit :
[...] 
> I now have to start communications with the Elmerfem people who have 
> religated their GUI Qt4 problems from a bug to an inhancement. I have 
> gotten warnings from several different sources that Debian is dropping 
> Qt4 because of maintenance problems up line. One of these days I may get 
> a working physics modeling setup.
> 
> Regards
> 
> Gary R.

Debian is droping Qt4:
 https://wiki.debian.org/Qt4Removal

QT4 is not facing maintenance problems upstream, it is unsupported upstream 
since 2015:
 https://en.wikipedia.org/wiki/Qt_version_history#Qt_4

Re: KDE run Dolphin as root?

[didier . gaumet]

(Apologies if this link have been given before) 

You will find a thread there on a KDE forum detailing why running Dolphin as 
root is discouraged and how to bypass this measure:
 https://forum.kde.org/viewtopic.php?t=141836

Re: KDE run Dolphin as root?

[Gary L. Roach]

On 6/16/20 12:26 AM, to...@tuxteam.de wrote:

On Tue, Jun 16, 2020 at 09:21:24AM +0200, Marco Möller wrote:

On 15.06.20 21:47, Gary L. Roach wrote:

Someone in the Debian hierarchy decided that root Dolphin was too
much of a security risk. So the problem has propagated to at least
a half dozen other distros (Ubuntu,Kubuntu, Mint) to name a
couple.

To my knowledge, this is not true!

You're too polite ;-D

To my perception, this is borderline... conspiracy theory.

Cheers
-- t


Miacopa

I think I was venting. I am so frustrated with this whole Dolphin mess 
that I may have gone overboard. Dolphin is probably the most used 
package on my systems. I do a lot of compiling from source code and 
complicated computer modeling and the frustration this has caused is 
very very unfortunate. *So who is responsible for messing around with my 
head*. My last post did include an apology  to anyone I maligned.


Gary R

Re: KDE run Dolphin as root?

[Gary L. Roach]

On 6/15/20 1:05 PM, Andrei POPESCU wrote:

On Lu, 15 iun 20, 12:47:59, Gary L. Roach wrote:

I assume that with respect to the original message that it should be obvious
that the root user problem stems from the underlying Debian OS. Someone in
the Debian hierarchy decided that root Dolphin was too much of a security
risk. So the problem has propagated to at least a half dozen other distros
(Ubuntu,Kubuntu, Mint) to name a couple.

Do you have any source for this claim?

Debian tends to do little if any customization to such big software
packages like KDE (there simply aren't enough resources for it), with
the obvious exception of integrating it with the rest of the system.

Kind regards,
Andrei


Hi all,

Andrei, after thinking about your question for a while I realized that I 
use KDE5 for just about everything. I'm even using Kubuntu for my Ubuntu 
installation. I really don't care for Ubuntu's Gnome desktop. Personal 
preference. That may have to change. I just loaded up the latest Kubuntu 
version (20.04) and now, not only is Dolphin completely locked out as a  
root user, they have now locked out everything. I can't even read a root 
directory. Everything is grayed out. So to hell with Dolphin. I loaded 
in Nemo and took the memory hit from all of the Gnome support packages. 
With two one terabyte drives and 16 GB of ram. who cares. Apologies for 
slandering Debian but if they want to keep using KDE as their desktop 
they had better bring the hammer down on someone in the KDE hierarchy . 
I now have to start communications with the Elmerfem people who have 
religated their GUI Qt4 problems from a bug to an inhancement. I have 
gotten warnings from several different sources that Debian is dropping 
Qt4 because of maintenance problems up line. One of these days I may get 
a working physics modeling setup.


Regards

Gary R.

Re: KDE run Dolphin as root?

[tomas]

On Tue, Jun 16, 2020 at 09:21:24AM +0200, Marco Möller wrote:
> On 15.06.20 21:47, Gary L. Roach wrote:
> >Someone in the Debian hierarchy decided that root Dolphin was too
> >much of a security risk. So the problem has propagated to at least
> >a half dozen other distros (Ubuntu,Kubuntu, Mint) to name a
> >couple.
> 
> To my knowledge, this is not true!

You're too polite ;-D

To my perception, this is borderline... conspiracy theory.

Cheers
-- t


signature.asc
Description: Digital signature

Re: KDE run Dolphin as root?

[tomas]

On Tue, Jun 16, 2020 at 08:33:29AM +1000, Keith bainbridge wrote:

[...]

> Here, hear i say. It is my computer.

You own it, you do the work. Complaining ain't working ;-D

> Now, i just tested both caja and nemo and both run as sudo and su
> -c. caja could not connect to ibus. (Default file managers for Mate
> & Cinnamon)

> I am sure I have had other file managers run as sudo.

This might just be because the others don't care as much about
your security. Who knows.

> I reckon the problem is dolphin specific. Having said that, I can't
> check in another environment, other than debian, mint - oh I could
> download and run an ISO in vbox. Am I that desperate to prove the
> point - not yet.

As long as there is a way to change the defaults all seems wellm no?

Cheers
-- t


signature.asc
Description: Digital signature

Re: KDE run Dolphin as root?

[Marco Möller]

On 15.06.20 21:47, Gary L. Roach wrote:
Someone in the Debian hierarchy decided that root Dolphin was too much 
of a security risk. So the problem has propagated to at least a half 
dozen other distros (Ubuntu,Kubuntu, Mint) to name a couple.


To my knowledge, this is not true!
It is the Dolphin upstream team which implements the blocking mechanism. 
In some of the many threads on this issue flooding the internet there 
are given instructions how to compile your personal version of Dolphin 
after having changed (removed) the respective code in the Dolphin source 
code, in order to finally make it run as user root again.


Best regards, Marco.

Re: KDE run Dolphin as root?

[Keith bainbridge]

On 16/6/20 6:19 am, to...@tuxteam.de wrote:

On Mon, Jun 15, 2020 at 11:05:32PM +0300, Andrei POPESCU wrote:

On Lu, 15 iun 20, 12:47:59, Gary L. Roach wrote:


I assume that with respect to the original message that it should be obvious
that the root user problem stems from the underlying Debian OS. Someone in
the Debian hierarchy decided that root Dolphin was too much of a security
risk. So the problem has propagated to at least a half dozen other distros
(Ubuntu,Kubuntu, Mint) to name a couple.


Do you have any source for this claim?

Debian tends to do little if any customization to such big software
packages like KDE (there simply aren't enough resources for it), with
the obvious exception of integrating it with the rest of the system.


No, no. The secret Debian Hierarchy is out to get us! Run!

;-)

Now more seriously, Gary: I think the default policy to disable root
for such huge GUI programs is sensible: there is no way in hell one
could make them secure.

As a default, it seems to make sense.

OTOH it is *your* computer, so there should be a way to override that
default behaviour. And it seems there is. All is well?

Software shouldn't *force* you to do something.

Cheers
-- t





Here, hear i say. It is my computer.


Now, i just tested both caja and nemo and both run as sudo and su -c. 
caja could not connect to ibus. (Default file managers for Mate & Cinnamon)


I am sure I have had other file managers run as sudo.


I reckon the problem is dolphin specific. Having said that, I can't 
check in another environment, other than debian, mint - oh I could 
download and run an ISO in vbox. Am I that desperate to prove the point 
- not yet.


--

Keith Bainbridge

keithr...@gmail.com

0447 667468

Re: KDE run Dolphin as root?

[tomas]

On Mon, Jun 15, 2020 at 11:05:32PM +0300, Andrei POPESCU wrote:
> On Lu, 15 iun 20, 12:47:59, Gary L. Roach wrote:
> > 
> > I assume that with respect to the original message that it should be obvious
> > that the root user problem stems from the underlying Debian OS. Someone in
> > the Debian hierarchy decided that root Dolphin was too much of a security
> > risk. So the problem has propagated to at least a half dozen other distros
> > (Ubuntu,Kubuntu, Mint) to name a couple.
> 
> Do you have any source for this claim?
> 
> Debian tends to do little if any customization to such big software 
> packages like KDE (there simply aren't enough resources for it), with 
> the obvious exception of integrating it with the rest of the system.

No, no. The secret Debian Hierarchy is out to get us! Run!

;-)

Now more seriously, Gary: I think the default policy to disable root
for such huge GUI programs is sensible: there is no way in hell one
could make them secure.

As a default, it seems to make sense.

OTOH it is *your* computer, so there should be a way to override that
default behaviour. And it seems there is. All is well?

Software shouldn't *force* you to do something.

Cheers
-- t


signature.asc
Description: Digital signature

Re: KDE run Dolphin as root?

[Andrei POPESCU]

On Lu, 15 iun 20, 12:47:59, Gary L. Roach wrote:
> 
> I assume that with respect to the original message that it should be obvious
> that the root user problem stems from the underlying Debian OS. Someone in
> the Debian hierarchy decided that root Dolphin was too much of a security
> risk. So the problem has propagated to at least a half dozen other distros
> (Ubuntu,Kubuntu, Mint) to name a couple.

Do you have any source for this claim?

Debian tends to do little if any customization to such big software 
packages like KDE (there simply aren't enough resources for it), with 
the obvious exception of integrating it with the rest of the system.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: KDE run Dolphin as root?

[Gary L. Roach]

On 6/14/20 1:22 PM, Default User wrote:

On Wed, Jun 10, 2020 at 4:12 AM Marco Möller
 wrote:

On 09.06.20 23:55, Default User wrote:

(...)
Now, a final note.

When I did my main install, it was a day or two before the release of
Buster 10.0.  I immediately upgraded to Unstable.  But it is still
originally based upon Stretch.  It was set up with both root and user
passwords. And I use good quality, long passwords.
: )

Here's the point:
I can do everything requiring elevated privileges just by using the
user password, and sudo in a terminal as needed. Never need to use the
root password.

Well, when I did an alternate Buster Stable install on a spare drive,
I was surprised (not happily) that when running from that setup,
various programs demand the root password, and will not accept the
user password.  So, now I have to remember not one, but two "good"
passwords.  And try to determine which one is being asked for.  And
re-remember both every time they are changed.

I am guessing this has to do with a change made for Buster.  Perhaps
it is a "security thing".


Others might correct me, I am still learning and might be confused about
things, but this is how I understand the situation be now:
In the past I thought that upgrading from release to release would be
all what someone good desire, especially when the upgrade process is
well designed and not breaking things. The Debian team is really doing
an excellent job to care for the release upgrade not being likely to
break things.
I then noticed that a release upgrade brings in more than simply
upgrading many packages and renewing version numbers, the latter being
what the in-release upgrades already do. Worth noting is that in a new
release additionally old concepts are deprecated or substituted, and new
concepts become introduced! Besides you having mentioned systemd already
here giving you another example: remember the (in 2015 ?) announced
changes in the use of the root directory structure concerning the
philosophy on which data is supposed to land in which directory
("filesystem hierarchy standard"). For now there are introduced symbolic
links from the old directory locations to the new locations, so that
software will not break right away if still not updated to respect the
new concept. If you would for long time roll from release to release,
then I imagine that conceptual changes like this will not become visible
in your system, and some time in the future the backward compatibility
to old concepts might need to be cut. You coming from a Debian/stretch
installation and having rolled upgrades via Debian/buster to
Debian/bullseye might still not find these changes cleanly applied.
Therefore, in order to keep up also with the conceptional changes, it is
worth to consider a fresh installation as the alternative to a release
upgrade. This is why many of us maintain detailed notes on package
installations and system configurations, in order to be able to
re-install quickly and thus also being well prepared for a new release
installation instead of a rolling upgrade.
(You are more then welcome to correct me if I misunderstood things ;-) !)
Best wishes, Marco.



On Jun 10, 2020, 2:36 AM Andrei POPESCU,  wrote:

You are making some claims above without providing even one example.


Well,  . . . yes.

There might be simple explanations and / or solutions for what you
experience...


Perhaps.  Problems can seem so simple, once they are solved.


On Jun 10, 2020, 4:12 AM, Marco Möller
 wrote:

Others might correct me, I am still learning and might be confused about
things, but this is how I understand the situation be now:
In the past I thought that upgrading from release to release would be
all what someone good desire, especially when the upgrade process is
well designed and not breaking things. The Debian team is really doing
an excellent job to care for the release upgrade not being likely to
break things.
I then noticed that a release upgrade brings in more than simply
upgrading many packages and renewing version numbers, the latter being
what the in-release upgrades already do. Worth noting is that in a new
release additionally old concepts are deprecated or substituted, and new
concepts become introduced! Besides you having mentioned systemd already
here giving you another example: remember the (in 2015 ?) announced
changes in the use of the root directory structure concerning the
philosophy on which data is supposed to land in which directory
("filesystem hierarchy standard"). For now there are introduced symbolic
links from the old directory locations to the new locations, so that
software will not break right away if still not updated to respect the
new concept. If you would for long time roll from release to release,
then I imagine that conceptual changes like this will not become visible
in your system, and some time in the future the backward compatibility
to old concepts might need to be cut. You coming from a Debian/stretch
installation and 

Re: KDE run Dolphin as root?

[Default User]

On Wed, Jun 10, 2020 at 4:12 AM Marco Möller
 wrote:
>
> On 09.06.20 23:55, Default User wrote:
> > (...)
> > Now, a final note.
> >
> > When I did my main install, it was a day or two before the release of
> > Buster 10.0.  I immediately upgraded to Unstable.  But it is still
> > originally based upon Stretch.  It was set up with both root and user
> > passwords. And I use good quality, long passwords.
> > : )
> >
> > Here's the point:
> > I can do everything requiring elevated privileges just by using the
> > user password, and sudo in a terminal as needed. Never need to use the
> > root password.
> >
> > Well, when I did an alternate Buster Stable install on a spare drive,
> > I was surprised (not happily) that when running from that setup,
> > various programs demand the root password, and will not accept the
> > user password.  So, now I have to remember not one, but two "good"
> > passwords.  And try to determine which one is being asked for.  And
> > re-remember both every time they are changed.
> >
> > I am guessing this has to do with a change made for Buster.  Perhaps
> > it is a "security thing".
>
>
> Others might correct me, I am still learning and might be confused about
> things, but this is how I understand the situation be now:
> In the past I thought that upgrading from release to release would be
> all what someone good desire, especially when the upgrade process is
> well designed and not breaking things. The Debian team is really doing
> an excellent job to care for the release upgrade not being likely to
> break things.
> I then noticed that a release upgrade brings in more than simply
> upgrading many packages and renewing version numbers, the latter being
> what the in-release upgrades already do. Worth noting is that in a new
> release additionally old concepts are deprecated or substituted, and new
> concepts become introduced! Besides you having mentioned systemd already
> here giving you another example: remember the (in 2015 ?) announced
> changes in the use of the root directory structure concerning the
> philosophy on which data is supposed to land in which directory
> ("filesystem hierarchy standard"). For now there are introduced symbolic
> links from the old directory locations to the new locations, so that
> software will not break right away if still not updated to respect the
> new concept. If you would for long time roll from release to release,
> then I imagine that conceptual changes like this will not become visible
> in your system, and some time in the future the backward compatibility
> to old concepts might need to be cut. You coming from a Debian/stretch
> installation and having rolled upgrades via Debian/buster to
> Debian/bullseye might still not find these changes cleanly applied.
> Therefore, in order to keep up also with the conceptional changes, it is
> worth to consider a fresh installation as the alternative to a release
> upgrade. This is why many of us maintain detailed notes on package
> installations and system configurations, in order to be able to
> re-install quickly and thus also being well prepared for a new release
> installation instead of a rolling upgrade.
> (You are more then welcome to correct me if I misunderstood things ;-) !)
> Best wishes, Marco.



On Jun 10, 2020, 2:36 AM Andrei POPESCU,  wrote:
> You are making some claims above without providing even one example.
>
Well,  . . . yes.
>
>There might be simple explanations and / or solutions for what you
>experience...
>
Perhaps.  Problems can seem so simple, once they are solved.


On Jun 10, 2020, 4:12 AM, Marco Möller
 wrote:
> Others might correct me, I am still learning and might be confused about
> things, but this is how I understand the situation be now:
> In the past I thought that upgrading from release to release would be
> all what someone good desire, especially when the upgrade process is
> well designed and not breaking things. The Debian team is really doing
> an excellent job to care for the release upgrade not being likely to
> break things.
> I then noticed that a release upgrade brings in more than simply
> upgrading many packages and renewing version numbers, the latter being
> what the in-release upgrades already do. Worth noting is that in a new
> release additionally old concepts are deprecated or substituted, and new
> concepts become introduced! Besides you having mentioned systemd already
> here giving you another example: remember the (in 2015 ?) announced
> changes in the use of the root directory structure concerning the
> philosophy on which data is supposed to land in which directory
> ("filesystem hierarchy standard"). For now there are introduced symbolic
> links from the old directory locations to the new locations, so that
> software will not break right away if still not updated to respect the
> new concept. If you would for long time roll from release to release,
> then I imagine that conceptual changes like this will not become visible
> in 

Re: KDE run Dolphin as root?

[Marco Möller]

On 09.06.20 23:55, Default User wrote:

(...)
Now, a final note.

When I did my main install, it was a day or two before the release of
Buster 10.0.  I immediately upgraded to Unstable.  But it is still
originally based upon Stretch.  It was set up with both root and user
passwords. And I use good quality, long passwords.
: )

Here's the point:
I can do everything requiring elevated privileges just by using the
user password, and sudo in a terminal as needed. Never need to use the
root password.

Well, when I did an alternate Buster Stable install on a spare drive,
I was surprised (not happily) that when running from that setup,
various programs demand the root password, and will not accept the
user password.  So, now I have to remember not one, but two "good"
passwords.  And try to determine which one is being asked for.  And
re-remember both every time they are changed.

I am guessing this has to do with a change made for Buster.  Perhaps
it is a "security thing".



Others might correct me, I am still learning and might be confused about 
things, but this is how I understand the situation be now:
In the past I thought that upgrading from release to release would be 
all what someone good desire, especially when the upgrade process is 
well designed and not breaking things. The Debian team is really doing 
an excellent job to care for the release upgrade not being likely to 
break things.
I then noticed that a release upgrade brings in more than simply 
upgrading many packages and renewing version numbers, the latter being 
what the in-release upgrades already do. Worth noting is that in a new 
release additionally old concepts are deprecated or substituted, and new 
concepts become introduced! Besides you having mentioned systemd already 
here giving you another example: remember the (in 2015 ?) announced 
changes in the use of the root directory structure concerning the 
philosophy on which data is supposed to land in which directory 
("filesystem hierarchy standard"). For now there are introduced symbolic 
links from the old directory locations to the new locations, so that 
software will not break right away if still not updated to respect the 
new concept. If you would for long time roll from release to release, 
then I imagine that conceptual changes like this will not become visible 
in your system, and some time in the future the backward compatibility 
to old concepts might need to be cut. You coming from a Debian/stretch 
installation and having rolled upgrades via Debian/buster to 
Debian/bullseye might still not find these changes cleanly applied. 
Therefore, in order to keep up also with the conceptional changes, it is 
worth to consider a fresh installation as the alternative to a release 
upgrade. This is why many of us maintain detailed notes on package 
installations and system configurations, in order to be able to 
re-install quickly and thus also being well prepared for a new release 
installation instead of a rolling upgrade.

(You are more then welcome to correct me if I misunderstood things ;-) !)
Best wishes, Marco.

Re: KDE run Dolphin as root?

[Andrei POPESCU]

On Ma, 09 iun 20, 17:55:07, Default User wrote:
> 
> Well, when I did an alternate Buster Stable install on a spare drive,
> I was surprised (not happily) that when running from that setup,
> various programs demand the root password, and will not accept the
> user password.  So, now I have to remember not one, but two "good"
> passwords.  And try to determine which one is being asked for.  And
> re-remember both every time they are changed.
> 
> I am guessing this has to do with a change made for Buster.  Perhaps
> it is a "security thing".
> 
> Maybe I am lazy, but I quite prefer to only have to remember and use
> one password.  And this feels like another step backward to me.
> 
> Oh, well . . .  I guess it's for my own good.  After all, I'm sure
> Debian developers know what is best for me, better than I do.  After
> all, these are the same people who actually thought systemd was a good
> idea.  And shouted down those who didn't.

You are making some claims above without providing even one example.

There might be simple explanations and / or solutions for what you 
experience...

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: KDE run Dolphin as root?

[Default User]

On Sunday, Jun 7, 2020, at 12:11, Kushal Kumaran  wrote:
>
>Running
>
>  sudo sh -c 'unset SUDO_USER; KDE_FULL_SESSION=true
> dolphin'
>
> from a shell gets a dolphin window.

Thanks, Kushal. That does work. For Dolphin, anyway.

> There is some advice at
> https://forum.kde.org/viewtopic.php?f=223=161021#p425888 that
> can arrange things so that you get an action on the right-click context
> menu.

Could not figure out how to get this to work.  Whatever.

> Sounds like you have your needs properly met with cinnamon and
> nemo, and they seem to be available in debian.  Is there a particular
> reason you need to solve this problem with dolphin?  I assume you
> could have just installed nemo and used it even while using the plasma
> shell as the desktop.

Yes, I have been getting along fine with nemo on Cinnamon.  Much
better than the crippled nautilus that Gnome makes these days.  I was
just looking around, to see if there was anything better. I have heard
people praise dolphin (and kde) lately.  And dolphin does seem to be a
little more configurable than nemo.

Nemo does work from within kde:
nemo as user
sudo nemo for elevated privileges.

Since I am the system administrator for my computer, I find myself
having to do a lot of things as root. I can enter the snippet you
provided, to run dolphin with elevated privileges.  Or nemo.  But it
really does bother me the arrogant attitude of one or more kde
developers: deliberately working to prevent users from deciding for
themselves how to use their own systems, even after considerable user
complaints.  And that they apparently promised users they would change
this, over a year ago! Sounds like "tell them whatever they want to
hear, then ignore them until they get too tired to complain any more."


On Jun 7, 2020, at 1:55 PM , Marco Möller wrote:
> For me the task to handle files as root is not frequently coming up. If
> so, then I simply use sudo and CLI commands. Besides on the CLI running
> nano, cp, mv and rm, I figured out that many times using chown helps a
> lot: if needing to manipulate many files as user root, then this is
> usually caused because a bunch of files was received from a backup
> storage directory or files on external storage devices come marked to be
> owned as root, but if I am pretty sure (this is of course important)
> that it will not do any harm to change the owner of those files or
> directories to the group and name of a normal user then chown is fast to
> do and afterwards I can continue to work with Dolphin as a normal user.
>
. . .
>
> Reminding on the question of the OP:
> If in need to handle files with root permissions, I simply use sudo and
> CLI commands. Remember the above mentioned comfort option to invoke a
> root terminal by command 'sudo su -'. Then, besides on the CLI running
> nano, cp, rm and mv, maybe having available mc, using the command chown
> should be considered as well. If I am pretty sure (this is of course
> important) that it will not do any harm to change the ownership of files
> or directories to the group and name of my normal user, then chown is
> fast to do and afterwards I can continue to work with Dolphin as my
> normal user.

Thanks for the explanation.

-

Now, a final note.

When I did my main install, it was a day or two before the release of
Buster 10.0.  I immediately upgraded to Unstable.  But it is still
originally based upon Stretch.  It was set up with both root and user
passwords. And I use good quality, long passwords.
: )

Here's the point:
I can do everything requiring elevated privileges just by using the
user password, and sudo in a terminal as needed. Never need to use the
root password.

Well, when I did an alternate Buster Stable install on a spare drive,
I was surprised (not happily) that when running from that setup,
various programs demand the root password, and will not accept the
user password.  So, now I have to remember not one, but two "good"
passwords.  And try to determine which one is being asked for.  And
re-remember both every time they are changed.

I am guessing this has to do with a change made for Buster.  Perhaps
it is a "security thing".

Maybe I am lazy, but I quite prefer to only have to remember and use
one password.  And this feels like another step backward to me.

Oh, well . . .  I guess it's for my own good.  After all, I'm sure
Debian developers know what is best for me, better than I do.  After
all, these are the same people who actually thought systemd was a good
idea.  And shouted down those who didn't.

Have a nice day!
: )

Re: KDE run Dolphin as root?

[Greg Wooledge]

On Mon, Jun 08, 2020 at 09:07:58AM +0300, Andrei POPESCU wrote:
> In Debian's default configuration members of group 'sudo' have sudo 
> access, so all you need is:
> 
> adduser my_user_name sudo

(and then log out and back in)

> As far as I know the installer does the equivalent of that.

If you enter an empty root password, yes, I've been told that it does.
If you enter a non-empty root password, then it doesn't.

Re: KDE run Dolphin as root?

[Andrei POPESCU]

On Du, 07 iun 20, 21:21:07, Marco Möller wrote:
> 
> Yes, design options exist. However, I never tried out if the user root could
> be blocked by the graphical session manager only, in the case of KDE usually
> sddm is in use. But I know that the login of user root can be blocked in
> general: when nowadays installing Debian, then there is offered to keep the
> root account deactivated, which is achieved by simply not assigning it a
> password but to leave the root's password empty and then activating the sudo
> mechanism for the during installation created normal user. Then the login as
> user root is disabled in general, not applying only to GUI login but also to
> text terminal login. As a consequence it is always required to log in as a
> normal user and using the command sudo would be the way to run commands with
> root permissions. The deactivation of the root account could also be
> achieved later on, any time, not only during installation of the system, by
> changing the password of user root to an empty string.

Careful, an empty password is not the same as a disabled password (see 
'man shadow'). The command 'passwd' will not even accept to change a 
password to an empty one.

To lock the password for an account use 'passwd -l'.

> But I am afraid that
> you then will have to care yourself to set up sudo properly when still
> possible to do so as user root.

In Debian's default configuration members of group 'sudo' have sudo 
access, so all you need is:

adduser my_user_name sudo

As far as I know the installer does the equivalent of that.

> Interestingly, although having disabled the root account during installation
> and having sudo automatically configured during installation, it by default
> appears to still be allowed to run command "sudo su -", which still lets you
> run a root terminal once you have been logged in as the normal user and
> knowing the user's password needed to use sudo! 

Warning, useless use of 'sudo su -' :)

There is no need for that, use 'sudo -i' ;)

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: KDE run Dolphin as root?

[Marco Möller]

On 07.06.20 02:42, Keith bainbridge wrote:

On 7/6/20 8:30 am, Marco Möller wrote:



I would easily agree with you concerning not to log into a graphical 
session as the user root. But Dolphin is also not running with sudo 
prepended.




And here I was thinking that the dolphin issue ran here for several 
days, just a few weeks ago.


And yes - not good idea to log into any GUI. My experience is I can't - 
I guess by design




Yes, design options exist. However, I never tried out if the user root 
could be blocked by the graphical session manager only, in the case of 
KDE usually sddm is in use. But I know that the login of user root can 
be blocked in general: when nowadays installing Debian, then there is 
offered to keep the root account deactivated, which is achieved by 
simply not assigning it a password but to leave the root's password 
empty and then activating the sudo mechanism for the during installation 
created normal user. Then the login as user root is disabled in general, 
not applying only to GUI login but also to text terminal login. As a 
consequence it is always required to log in as a normal user and using 
the command sudo would be the way to run commands with root permissions. 
The deactivation of the root account could also be achieved later on, 
any time, not only during installation of the system, by changing the 
password of user root to an empty string. But I am afraid that you then 
will have to care yourself to set up sudo properly when still possible 
to do so as user root.


Interestingly, although having disabled the root account during 
installation and having sudo automatically configured during 
installation, it by default appears to still be allowed to run command 
"sudo su -", which still lets you run a root terminal once you have been 
logged in as the normal user and knowing the user's password needed to 
use sudo! So, for repetitive work requiring root permissions it at least 
is not necessary to prepend sudo to all root commands again and again - 
but this is still not reaching the comfort like running Dolphin with 
root permissions would do, and Dolphin also resists to start up when 
called from such root xterminal running in the normal user session.


Reminding on the question of the OP:
If in need to handle files with root permissions, I simply use sudo and 
CLI commands. Remember the above mentioned comfort option to invoke a 
root terminal by command 'sudo su -'. Then, besides on the CLI running 
nano, cp, rm and mv, maybe having available mc, using the command chown 
should be considered as well. If I am pretty sure (this is of course 
important) that it will not do any harm to change the ownership of files 
or directories to the group and name of my normal user, then chown is 
fast to do and afterwards I can continue to work with Dolphin as my 
normal user.

Re: KDE run Dolphin as root?

[Keith bainbridge]

On 7/6/20 12:56 pm, Default User wrote:


So I guess I just got spoiled, using the nemo file manager in Cinnamon. 
Just right click the Cinnamon desktop, select "Open as root", then use 
nemo with temporarily elevated privileges.  Then close nemo, and I am 
back to the desktop as a regular user again. Easy.





Have you tried nemo (cinnamon's file mgr) in KDE?  It'll likely bring in 
a bit of gtk stuff, but that shouldn't hurt anything.


--

Keith Bainbridge

keithr...@gmail.com

0447 667468

Re: KDE run Dolphin as root?

[David Wright]

On Sat 06 Jun 2020 at 18:10:10 (-0700), Kushal Kumaran wrote:
> Default User  writes:
> >
> > As an experiment, I just installed Debian 10.4 Stable on a spare drive, and
> > installed kde on it.
> >
> > I have not tried kde in many years, so am not really familiar with it.
> > Perhaps I am overlooking something obvious, but I can not seem to run
> > Dolphin or Konqueror as root.
> >
> > Searching online, I was astounded to see many references to this problem,
> > saying that this is not a bug, but a feature - that kde developers are
> > deliberately working to prevent users from using some programs, including
> > Dolphin as root, as a "security measure".

> I have no idea what the unfixable security vulnerabilities are.

Perhaps the attack claimed here will answer that:

https://blog.martin-graesslin.com/blog/2017/02/editing-files-as-root/

> You might be overestimating the number of people who need to do file
> management as root with a graphical tool.

Yes, I've certainly never done that. Even using mc requires some care
in selecting its configuration options.

Cheers,
David.

Re: KDE run Dolphin as root?

[Kushal Kumaran]

Default User  writes:

> On Sat, Jun 6, 2020, 21:19 Kushal Kumaran  wrote:
>
>> Default User  writes:
>>
>> > Hi, all.
>> >
>> > As an experiment, I just installed Debian 10.4 Stable on a spare drive,
>> and
>> > installed kde on it.
>> >
>> > I have not tried kde in many years, so am not really familiar with it.
>> > Perhaps I am overlooking something obvious, but I can not seem to run
>> > Dolphin or Konqueror as root.
>> >
>> > Searching online, I was astounded to see many references to this problem,
>> > saying that this is not a bug, but a feature - that kde developers are
>> > deliberately working to prevent users from using some programs, including
>> > Dolphin as root, as a "security measure".
>> >
>> > So, can the current version of Dolphin in Debian Stable be run as root
>> > (without re-compiling, etc)?
>> >
>>
>> Dolphin is just checking the SUDO_USER environment variable.  Just unset
>> the variable before starting dolphin.  Ref:
>>
>> https://codesearch.debian.net/search?q=Executing+Dolphin+with+sudo+is+not+possible+due+to+unfixable+security+vulnerabilities=1
>>
>> I have no idea what the unfixable security vulnerabilities are.
>>
>> > And, if not, how (and why) would anyone use kde at all?
>>
>> You might be overestimating the number of people who need to do file
>> management as root with a graphical tool.  I, for one, use plasma as my
>> primary desktop environment, but almost all file management activity is
>> through emacs (with tramp for root stuff), or just a shell.  Until I saw
>> your post, I had no idea dolphin would refuse to run as root.
>>
>> --
>> regards,
>> kushal
>>
>
>
>
>
> First, to Keith:
>
> Yes, I vaguely remember that thread.  I did briefly look through the list
> archive but could not find it.
>
> Perhaps there is a search function for the list archive, but I am unaware
> of it.
>
>
> Second, to Kushal:
>
> I did look at the code you referenced. Interesting. But I am not a
> programmer.
>
> I did try to under the SUDO_USER environment variable as you suggested.
> Maybe I didn't do it correctly, but it did not resolve the problem. Dolphin
> refuses to run with elevated privileges.
>

Running

  sudo sh -c 'unset SUDO_USER; KDE_FULL_SESSION=true dolphin'

from a shell gets a dolphin window.

There is some advice at
https://forum.kde.org/viewtopic.php?f=223=161021#p425888 that can
arrange things so that you get an action on the right-click context
menu.

> Anyway, for now, I can use Midnight Commander, either as sudo or as root,
> to do file management of root folders and files. But it is somewhat
> "clunky" to do so.
>
> And just to note: I do a lot of management of files and directories
> requiring root privileges.
>
> So I guess I just got spoiled, using the nemo file manager in Cinnamon.
> Just right click the Cinnamon desktop, select "Open as root", then use nemo
> with temporarily elevated privileges.  Then close nemo, and I am back to
> the desktop as a regular user again. Easy.

Sounds like you have your needs properly met with cinnamon and nemo, and
they seem to be available in debian.  Is there a particular reason you
need to solve this problem with dolphin?  I assume you could have just
installed nemo and used it even while using the plasma shell as the
desktop.

-- 
regards,
kushal

Re: KDE run Dolphin as root?

[Default User]

On Sat, Jun 6, 2020, 21:19 Kushal Kumaran  wrote:

> Default User  writes:
>
> > Hi, all.
> >
> > As an experiment, I just installed Debian 10.4 Stable on a spare drive,
> and
> > installed kde on it.
> >
> > I have not tried kde in many years, so am not really familiar with it.
> > Perhaps I am overlooking something obvious, but I can not seem to run
> > Dolphin or Konqueror as root.
> >
> > Searching online, I was astounded to see many references to this problem,
> > saying that this is not a bug, but a feature - that kde developers are
> > deliberately working to prevent users from using some programs, including
> > Dolphin as root, as a "security measure".
> >
> > So, can the current version of Dolphin in Debian Stable be run as root
> > (without re-compiling, etc)?
> >
>
> Dolphin is just checking the SUDO_USER environment variable.  Just unset
> the variable before starting dolphin.  Ref:
>
> https://codesearch.debian.net/search?q=Executing+Dolphin+with+sudo+is+not+possible+due+to+unfixable+security+vulnerabilities=1
>
> I have no idea what the unfixable security vulnerabilities are.
>
> > And, if not, how (and why) would anyone use kde at all?
>
> You might be overestimating the number of people who need to do file
> management as root with a graphical tool.  I, for one, use plasma as my
> primary desktop environment, but almost all file management activity is
> through emacs (with tramp for root stuff), or just a shell.  Until I saw
> your post, I had no idea dolphin would refuse to run as root.
>
> --
> regards,
> kushal
>




First, to Keith:

Yes, I vaguely remember that thread.  I did briefly look through the list
archive but could not find it.

Perhaps there is a search function for the list archive, but I am unaware
of it.


Second, to Kushal:

I did look at the code you referenced. Interesting. But I am not a
programmer.

I did try to under the SUDO_USER environment variable as you suggested.
Maybe I didn't do it correctly, but it did not resolve the problem. Dolphin
refuses to run with elevated privileges.

Anyway, for now, I can use Midnight Commander, either as sudo or as root,
to do file management of root folders and files. But it is somewhat
"clunky" to do so.

And just to note: I do a lot of management of files and directories
requiring root privileges.

So I guess I just got spoiled, using the nemo file manager in Cinnamon.
Just right click the Cinnamon desktop, select "Open as root", then use nemo
with temporarily elevated privileges.  Then close nemo, and I am back to
the desktop as a regular user again. Easy.

Re: KDE run Dolphin as root?

[Kushal Kumaran]

Default User  writes:

> Hi, all.
>
> As an experiment, I just installed Debian 10.4 Stable on a spare drive, and
> installed kde on it.
>
> I have not tried kde in many years, so am not really familiar with it.
> Perhaps I am overlooking something obvious, but I can not seem to run
> Dolphin or Konqueror as root.
>
> Searching online, I was astounded to see many references to this problem,
> saying that this is not a bug, but a feature - that kde developers are
> deliberately working to prevent users from using some programs, including
> Dolphin as root, as a "security measure".
>
> So, can the current version of Dolphin in Debian Stable be run as root
> (without re-compiling, etc)?
>

Dolphin is just checking the SUDO_USER environment variable.  Just unset
the variable before starting dolphin.  Ref:
https://codesearch.debian.net/search?q=Executing+Dolphin+with+sudo+is+not+possible+due+to+unfixable+security+vulnerabilities=1

I have no idea what the unfixable security vulnerabilities are.

> And, if not, how (and why) would anyone use kde at all?

You might be overestimating the number of people who need to do file
management as root with a graphical tool.  I, for one, use plasma as my
primary desktop environment, but almost all file management activity is
through emacs (with tramp for root stuff), or just a shell.  Until I saw
your post, I had no idea dolphin would refuse to run as root.

-- 
regards,
kushal

Re: KDE run Dolphin as root?

[Keith bainbridge]

On 7/6/20 8:30 am, Marco Möller wrote:



I would easily agree with you concerning not to log into a graphical 
session as the user root. But Dolphin is also not running with sudo 
prepended.




And here I was thinking that the dolphin issue ran here for several 
days, just a few weeks ago.


And yes - not good idea to log into any GUI. My experience is I can't - 
I guess by design


--

Keith Bainbridge

keithr...@gmail.com

0447 667468

Re: KDE run Dolphin as root?

[Marco Möller]

On 06.06.20 23:37, Paul Johnson wrote:



On Sat, Jun 6, 2020 at 4:20 PM Default User > wrote:



On Fri, Jun 5, 2020, 16:55 Default User mailto:hunguponcont...@gmail.com>> wrote:

Hi, all.

As an experiment, I just installed Debian 10.4 Stable on a spare
drive, and installed kde on it.

I have not tried kde in many years, so am not really familiar
with it. Perhaps I am overlooking something obvious, but I can
not seem to run Dolphin or Konqueror as root.

Searching online, I was astounded to see many references to this
problem, saying that this is not a bug, but a feature - that kde
developers are deliberately working to prevent users from using
some programs, including Dolphin as root, as a "security measure".

So, can the current version of Dolphin in Debian Stable be run
as root (without re-compiling, etc)?

And, if not, how (and why) would anyone use kde at all?


So . . .  no one here using kde?
Hmmm . . . 



I think it's less "nobody running KDE" so much as "who logs in to KDE as 
root?"



I would easily agree with you concerning not to log into a graphical 
session as the user root. But Dolphin is also not running with sudo 
prepended.

Marco.

Re: KDE run Dolphin as root?

[Marco Möller]

On 06.06.20 23:20, Default User wrote:


On Fri, Jun 5, 2020, 16:55 Default User > wrote:


Hi, all.

As an experiment, I just installed Debian 10.4 Stable on a spare
drive, and installed kde on it.

I have not tried kde in many years, so am not really familiar with
it. Perhaps I am overlooking something obvious, but I can not seem
to run Dolphin or Konqueror as root.

Searching online, I was astounded to see many references to this
problem, saying that this is not a bug, but a feature - that kde
developers are deliberately working to prevent users from using some
programs, including Dolphin as root, as a "security measure".

So, can the current version of Dolphin in Debian Stable be run as
root (without re-compiling, etc)?

And, if not, how (and why) would anyone use kde at all?





So . . .  no one here using kde?
Hmmm . . .

: )




To my knowledge it for years is not possible to run Dolphin in KDE with 
root permissions, so also not in Buster. I never tried to use Dolphin 
outside of KDE and therefore cannot state on that situation.


IMHO, the nice thing of KDE over GNOME is that in KDE usually I am 
offered high control on the appearance and interactive control of my 
desktop. GNOME instead appears to copy an Android cellphone, not only 
that its appearance remind on it but also that you either like it or you 
have to make yourself to accept it as it is. Changes on some of its 
desktop elements have been quite restricted when I seriously would have 
needed a change. This was what forced me to change. On my quite old 
hardware I then went for LXQt until I noticed that running it with kwin 
was greatest. Well, anyway running kwin I then tried out KDE and found 
that its footprint is not significant higher than the one of LXQt and 
that its responsiveness is excellent if staying with KDE Plasma and a 
selection of helpful tools but sparing out its akonadi dependent apps. 
Actually, both LXQt and KDE fro me run much better than GNOME on my 
hardware - and today I am a quite satisfied KDE user.
But concerning Dolphin and the infantilizing amputation to not allow it 
to run with root permissions, here KDE completely fails to keep up with 
its fame.


Sorry for the bad news. Marco.

Re: KDE run Dolphin as root?

[Paul Johnson]

On Sat, Jun 6, 2020 at 4:20 PM Default User 
wrote:

>
> On Fri, Jun 5, 2020, 16:55 Default User  wrote:
>
>> Hi, all.
>>
>> As an experiment, I just installed Debian 10.4 Stable on a spare drive,
>> and installed kde on it.
>>
>> I have not tried kde in many years, so am not really familiar with it.
>> Perhaps I am overlooking something obvious, but I can not seem to run
>> Dolphin or Konqueror as root.
>>
>> Searching online, I was astounded to see many references to this problem,
>> saying that this is not a bug, but a feature - that kde developers are
>> deliberately working to prevent users from using some programs, including
>> Dolphin as root, as a "security measure".
>>
>> So, can the current version of Dolphin in Debian Stable be run as root
>> (without re-compiling, etc)?
>>
>> And, if not, how (and why) would anyone use kde at all?
>>
>
> So . . .  no one here using kde?
> Hmmm . . .
>

I think it's less "nobody running KDE" so much as "who logs in to KDE as
root?"

Re: KDE run Dolphin as root?

[Default User]

On Fri, Jun 5, 2020, 16:55 Default User  wrote:

> Hi, all.
>
> As an experiment, I just installed Debian 10.4 Stable on a spare drive,
> and installed kde on it.
>
> I have not tried kde in many years, so am not really familiar with it.
> Perhaps I am overlooking something obvious, but I can not seem to run
> Dolphin or Konqueror as root.
>
> Searching online, I was astounded to see many references to this problem,
> saying that this is not a bug, but a feature - that kde developers are
> deliberately working to prevent users from using some programs, including
> Dolphin as root, as a "security measure".
>
> So, can the current version of Dolphin in Debian Stable be run as root
> (without re-compiling, etc)?
>
> And, if not, how (and why) would anyone use kde at all?
>




So . . .  no one here using kde?
Hmmm . . .

: )

Re: kde, localization and keyboards

[Eduardo M KALINOWSKI]

On 08/03/2020 06:15, Graham Seaman wrote:
> I've previously used either Gnome or Enlightenment as my main
> environment; I just installed Debian on an old laptop and decided to
> give KDE a go instead. I often want to switch keyboard briefly to do a
> bit of text editing with non-english characters (pt, de, ru). I don't
> ever want to change localization away from GB English. In Gnome I
> could do this: switching keyboard had no effect on localization. In
> KDE I get randomly switch between localizations: for example, I just
> ran apt install, and the first half of the messages were in
> Portuguese, then it suddenly switched to German, with no input from
> me. The only localizations I get match the keyboards I've set up
> (though I'm not switching keyboard). I've removed all languages except
> British English from Settings->language->configure plasma translations.
>
I configure layouts via System settings->Input
Devices->Keyboard->Layouts and switch them using the tray icon or the
keyboard shortcut, and only the keyboard is changed - not the full
system locale.


-- 
Eduardo M KALINOWSKI
edua...@kalinowski.com.br

Re: KDE file dialog in Libreoffice

[Rainer Dorsch]

On Samstag, 18. Januar 2020 21:00:04 CET Rene Engelhard wrote:
> On Sat, Jan 18, 2020 at 06:49:23PM +0100, Rainer Dorsch wrote:
> > is there a way to get the KDE file dialog in libreoffice
> > (buster-backports) ?
> 
> > Installing libreoffice-kde does not seem to be sufficient for me...
> 
> libreoffice-kde5?
> 
> $ rmadison libreoffice-kde
> libreoffice-kde | 1:4.3.3-2+deb8u11| oldoldstable   |
> amd64, armel, armhf, i386 libreoffice-kde | 1:5.2.7-1+deb9u10|
> oldstable  | amd64, arm64, armel, armhf, i386, mips,
> mips64el, mipsel, ppc64el, s390x libreoffice-kde | 1:5.2.7-1+deb9u11   
> | oldstable-proposed-updates | amd64, arm64, armel, armhf, i386, mips,
> mips64el, mipsel, ppc64el, s390x libreoffice-kde | 1:6.1.5-3+deb10u4~bpo9+1
> | stretch-backports  | all libreoffice-kde | 1:6.1.5-3+deb10u5 
>   | stable | all $ rmadison libreoffice-kde5
> libreoffice-kde5 | 1:6.1.5-3+deb10u4~bpo9+1  | stretch-backports | amd64,
> arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> libreoffice-kde5 | 1:6.1.5-3+deb10u5 | stable| amd64,
> arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> libreoffice-kde5 | 1:6.3.4-2~bpo10+1 | buster-backports  | amd64,
> arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
> libreoffice-kde5 | 1:6.3.4-2 | testing   | amd64,
> arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
> libreoffice-kde5 | 1:6.3.4-2 | unstable  | arm64
> libreoffice-kde5 | 1:6.4.0~beta1-0reprotest1 | experimental  | arm64,
> armel, armhf, mips64el, mipsel libreoffice-kde5 | 1:6.4.0~beta1-4  
> | experimental  | amd64, i386, ppc64el, s390x libreoffice-kde5 |
> 1:6.4.0~rc2-2 | unstable  | amd64, armel, armhf, i386,
> mips64el, mipsel, ppc64el, s390x $
> 
> libreoffice-kde is a noop just depending on -kde5 (and not present in
> buster-backports since it was just in buster for stretch->buster updates).
> 

Hi Rene,

thanks for the quick reply. I think the issue is more subtle.

rd@nanette:~$ apt-cache policy libreoffice-kde5 
libreoffice-kde5:
  Installiert:   1:6.3.4-2~bpo10+1
  Installationskandidat: 1:6.3.4-2~bpo10+1
  Versionstabelle:
 *** 1:6.3.4-2~bpo10+1 100
100 http://ftp.de.debian.org/debian buster-backports/main amd64 
Packages
100 /var/lib/dpkg/status
 1:6.1.5-3+deb10u5 500
500 http://ftp.de.debian.org/debian buster/main amd64 Packages
 1:6.1.5-3+deb10u4 500
500 http://security.debian.org buster/updates/main amd64 Packages
rd@nanette:~$ 

was installed, it was a typo on my side, libreoffice-kde was not installed.

And checking carefully, I think it is even the KDE file picker, here they are 
next to each other from kate (KDE editor) and libreoffice

http://scw.bokomoko.de/~rd/file_picker.png

I was looking Ablage in the Section Fremdgerät in the libreoffice file picker 
and 
this not find it. Since I had it on the other KDE apps, I concluded that it is 
another file picker.

Ablage is an sftp:// address. I am wondering, are these not supported by 
libreoffice?

Thanks
Rainer

Thanks
Rainer

Re: KDE file dialog in Libreoffice

[Rene Engelhard]

On Sat, Jan 18, 2020 at 06:49:23PM +0100, Rainer Dorsch wrote:
> is there a way to get the KDE file dialog in libreoffice (buster-backports) ?

> 
> Installing libreoffice-kde does not seem to be sufficient for me...

libreoffice-kde5?

$ rmadison libreoffice-kde
libreoffice-kde | 1:4.3.3-2+deb8u11| oldoldstable   | 
amd64, armel, armhf, i386
libreoffice-kde | 1:5.2.7-1+deb9u10| oldstable  | 
amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
libreoffice-kde | 1:5.2.7-1+deb9u11| oldstable-proposed-updates | 
amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
libreoffice-kde | 1:6.1.5-3+deb10u4~bpo9+1 | stretch-backports  | all
libreoffice-kde | 1:6.1.5-3+deb10u5| stable | all
$ rmadison libreoffice-kde5
libreoffice-kde5 | 1:6.1.5-3+deb10u4~bpo9+1  | stretch-backports | amd64, 
arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
libreoffice-kde5 | 1:6.1.5-3+deb10u5 | stable| amd64, 
arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
libreoffice-kde5 | 1:6.3.4-2~bpo10+1 | buster-backports  | amd64, 
arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
libreoffice-kde5 | 1:6.3.4-2 | testing   | amd64, 
arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
libreoffice-kde5 | 1:6.3.4-2 | unstable  | arm64
libreoffice-kde5 | 1:6.4.0~beta1-0reprotest1 | experimental  | arm64, 
armel, armhf, mips64el, mipsel
libreoffice-kde5 | 1:6.4.0~beta1-4   | experimental  | amd64, i386, 
ppc64el, s390x
libreoffice-kde5 | 1:6.4.0~rc2-2 | unstable  | amd64, 
armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
$

libreoffice-kde is a noop just depending on -kde5 (and not present in 
buster-backports since it was
just in buster for stretch->buster updates).

Regards,

Rene

Re: KDE Connect no deixa editar arxius dona error.

[Antoni Villalonga]

Hola Jordi,

Pots adjuntar un fitxer d'exemple abans d'enviarlo a la tablet i una copia del
mateix fitxer recuperat des de la tablet?

Entenc que el fitxer no s'ha d'alterar en el procés.

Pee cert, el KDEConnect, l'he estat provant entre PC i mobil i entre dos
mobils. M'agrada tot i que trobo a faltar algunes funcionalitats.

Salut!

On Mon, Dec 23, 2019 at 03:37:17PM +0100, Jordi Boixader wrote:
> Hola,
> 
> M'he comprat una tauleta Samsung Galaxy Tab S6 amb 256 Gb de d'espai i
> voldria fer-la servir com a disc dur. Per exemple des del PC Sobretaula amb
> Debian KDE accedir als documents, editar-los i guardar-los dins ta tauleta.
> 
> Ho faig amb KDE Connect, és com entrar dins un USB extraible però és la
> tauleta amb wifi. Fins aquí tot bé, puc copiar, enganxar i esborrar arxius.
> (a part d'altres coses que no venen al cas).
> 
> Però depèn del tipus d'arxiu no el puc editar, diu que s'ha corromput. Per
> exemple els arxius del gimp .xcf només de copiarlos a la tauleta ja no és
> poden editar encara que els torni a copiar al PC. Això també passa amb
> altres tipus d'arxiu.
> 
> Que creieu que pot passar?
> 
> 
> Salut i bones festes!
> 
> Correu enviat des del mòbil, perdoneu la brevetat.

-- 
Antoni Villalonga
http://friki.cat/

Re: KDE Connect no deixa editar arxius dona error.

[Narcis Garcia]

Jo m'he trobat amb això en compartir carpetes simultànciament per a
clients GNU/Linux i clients Windows, i em sembla que té a veure amb els
permisos (umask) amb els quals es creen els fitxers.

Si REALMENT necessites fer-ho per xarxa, et suggereixo que li posis un
servidor SSH a la tauleta i facis totes les connexions per SFTP/SSH.


__
I'm using this express-made address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.
El 23/12/19 a les 15:37, Jordi Boixader ha escrit:
> Hola,
> 
> M'he comprat una tauleta Samsung Galaxy Tab S6 amb 256 Gb de d'espai i
> voldria fer-la servir com a disc dur. Per exemple des del PC Sobretaula
> amb Debian KDE accedir als documents, editar-los i guardar-los dins ta
> tauleta.
> 
> Ho faig amb KDE Connect, és com entrar dins un USB extraible però és la
> tauleta amb wifi. Fins aquí tot bé, puc copiar, enganxar i esborrar
> arxius. (a part d'altres coses que no venen al cas).
> 
> Però depèn del tipus d'arxiu no el puc editar, diu que s'ha corromput.
> Per exemple els arxius del gimp .xcf només de copiarlos a la tauleta ja
> no és poden editar encara que els torni a copiar al PC. Això també passa
> amb altres tipus d'arxiu. 
> 
> Que creieu que pot passar? 
> 
> 
> Salut i bones festes! 
> 
> Correu enviat des del mòbil, perdoneu la brevetat.

Re: KDE madness again

[deloptes]

Gene Heskett wrote:

> +100 deloptes, but we are the choir you are preaching to.  So many of us
> who liked the original kde, and have been using it since about 1.2 are
> now running TDE which is a fork of kde at about the 3.5 level, with
> hundreds of bugs fixed, but few new features. No changes of note  in the
> eye candy. Generally, it just works.

Amen and please open another thread for your crawler issue :) or continue in
the one that you already opened.

regards

Re: KDE madness again

[Gene Heskett]

On Sunday 03 November 2019 06:07:18 deloptes wrote:

> Reco wrote:
> > On Sun, Nov 03, 2019 at 09:47:50AM +0100, deloptes wrote:
> >> Reco wrote:
> >> > # apt install qttools5-dev-tools -y
> >>
> >> tried several times without success - perhaps because qt4 was
> >> installed before.
> >
> > QT4 has no future, and will be probably removed in bullseye.
>
> true, so I removed everything KDE/Qt4 and KDE/Qt5 then installed the
> KDE/Qt5 again - interestingly both qt4/5 is in the same package.
>
> $ ls -al /usr/lib/x86_64-linux-gnu/qtchooser/
> total 132
> drwxr-xr-x   2 root root   4096 Nov  3 09:44 .
> drwxr-xr-x 101 root root 126976 Nov  3 09:44 ..
> lrwxrwxrwx   1 root root 50 May  3  2019
> 4.conf -> ../../../share/qtchooser/qt4-x86_64-linux-gnu.conf
> lrwxrwxrwx   1 root root 50 May  3  2019
> 5.conf -> ../../../share/qtchooser/qt5-x86_64-linux-gnu.conf
> lrwxrwxrwx   1 root root 50 May  3  2019
> qt4.conf -> ../../../share/qtchooser/qt4-x86_64-linux-gnu.conf
> lrwxrwxrwx   1 root root 50 May  3  2019
> qt5.conf -> ../../../share/qtchooser/qt5-x86_64-linux-gnu.conf
>
> And the crap is broken
>
> $ dpkg -S /usr/share/qtchooser/qt4-x86_64-linux-gnu.conf
> qtchooser: /usr/share/qtchooser/qt4-x86_64-linux-gnu.conf
>
> >> > $ /usr/lib/x86_64-linux-gnu/qt5/bin/qdbusviewer
> >> >
> >> > Works for me.
> >>
> >> you should try starting qdbusviewer not from the full path. Does it
> >> work? $ /usr/bin/qdbusviewer
> >> qdbusviewer: could not find a Qt installation of ''
> >
> > No. And that's a bug in qtchooser. Some variation of #928315,
> > probably.
> >
> > I don't use QT programs that much, so I won't comment on whichever
> > is broken there. Presumably it's some user configuration file which
> > should point at /usr/lib/x86_64-linux-gnu/qt5.
> >
> > Personally I see no problem at creating a suitable shell alias.
>
> No customizations at this level - cause later you forget and wonder
> again why something does not work. MY solution was great customization
> :) use independent and recent Qt5.12
>
> >> A simple proof that after 11 years since they (KDE) promised things
> >> will work - it is still the same BS.
> >
> > I lost faith in KDE back in "KDE4.0 != KDE4" days.
>
> yes same - ridiculous and 11y later it is still crap. I tend to think
> this is a big problem for Free Open Source Software. In the profit
> driven market, you source inefficiency and stupidity out. But in FOSS
> there is no way to control ideology and SystemD/KDE expolit the
> freedom.
>
> There is no way to bring them to consciousness. The lack of ability to
> participate in normal argumentative communication, to make conclusions
> and correct the own stand point is ridiculous.
>
> regards

+100 deloptes, but we are the choir you are preaching to.  So many of us 
who liked the original kde, and have been using it since about 1.2 are 
now running TDE which is a fork of kde at about the 3.5 level, with 
hundreds of bugs fixed, but few new features. No changes of note  in the 
eye candy. Generally, it just works.

Todays question is how do you control webcrawler bots that ignore 
robot.txt, download the whole site using up your upload bandwidth, and 
repeat from the top when they have accomplished an image of the site. 
I've taken the view that I'll note their address from the httpd logs and 
have added it in CIDR/24 format to my hosts.deny. Thats a bit of a 
cylinder bored shotgun I guess as I have a potential user in Sweden 
reporting a blank page right now for

http:// http://geneslinuxbox.net:6309/gene/lathe-stf/linuxcnc4rpi4

Which should show a directory list of 9 or so files, and clicking on one 
of them should offer to download it. But its all for armhf on an rpi4b.
But these damned bots that ignore your robot.txt are using up all my 
upload bandwidth if I let them.  Screw em, and the camel that rode in on 
them.  And just now yandex has figured a way around my blocks and so has 
semrush.com/bots and my upload bandwidth of around 300 kbaud is being 
used up. And sucking everything in a new directory I just created Friday 
to hold those downloads. Around 3.5GB total. This is as far as I'm 
concerned a DDOS being done by about 5 of the webcrawlers extant, 
bingbot is in the block list as is googlbot. But the logs are currently 
showing a private copy of FF-60 in that directory, so perhaps the Swede 
will get what he needs. I don't show any of those bots ever reading 
robots.txt. Shame on them. If the swede would give me his ipv4, I'd put 
him in my hosts.allow. But I guess I'd better restart apache2 and 
interrupt this party so I can upload this reply. Done.


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: KDE madness again

[deloptes]

Kumar Appaiah wrote:

> I am currently running most packages on testing. On my system,
> qdbusviewer seems to be:
> 
> # ls -l /usr/bin/qdbusviewer
> lrwxrwxrwx 1 root root 9 May  3  2019 /usr/bin/qdbusviewer -> qtchooser
> 
> qdbusviewer itself seems to be in qttools5-dev-tools, and I seem to be
> able to run it as:
> 
> # /usr/lib/x86_64-linux-gnu/qt5/bin/qdbusviewer
> 
> Please let mke know if some version information from my side would
> help.

Hi,
I do not use KDE. I use only qdbusviewer and some libraries linked to other
applications - for example teamviewer requires qt.

I seem to have been using the qt4 version with stretch. Two days ago I
upgraded to buster and today I found out that this is not working.

Expected is that it set up itself during installation and works seamlessly.
I also deliberately avoid using software that causes problems, because I
want to do my work and not debug or fix something.

I do not know why it does not setup automatically. I uninstalled everything
old and installed from scratch.

To me it is a sign that KDE is still a BS, because of the philosophy behind.

Never mind - as mentioned I had a copy of Qt5 for other project. I do not
need any KDE - just the qdbusviewer and Qt5 libraries.

When things start working seamlessly like it was at the end of KDE3 - just
let me know. I'll give it a try.

regards

Re: KDE madness again

[deloptes]

Reco wrote:

> On Sun, Nov 03, 2019 at 09:47:50AM +0100, deloptes wrote:
>> Reco wrote:
>> 
>> > # apt install qttools5-dev-tools -y
>> 
>> tried several times without success - perhaps because qt4 was installed
>> before.
> 
> QT4 has no future, and will be probably removed in bullseye.
> 
> 

true, so I removed everything KDE/Qt4 and KDE/Qt5 then installed the KDE/Qt5
again - interestingly both qt4/5 is in the same package.

$ ls -al /usr/lib/x86_64-linux-gnu/qtchooser/
total 132
drwxr-xr-x   2 root root   4096 Nov  3 09:44 .
drwxr-xr-x 101 root root 126976 Nov  3 09:44 ..
lrwxrwxrwx   1 root root 50 May  3  2019
4.conf -> ../../../share/qtchooser/qt4-x86_64-linux-gnu.conf
lrwxrwxrwx   1 root root 50 May  3  2019
5.conf -> ../../../share/qtchooser/qt5-x86_64-linux-gnu.conf
lrwxrwxrwx   1 root root 50 May  3  2019
qt4.conf -> ../../../share/qtchooser/qt4-x86_64-linux-gnu.conf
lrwxrwxrwx   1 root root 50 May  3  2019
qt5.conf -> ../../../share/qtchooser/qt5-x86_64-linux-gnu.conf

And the crap is broken

$ dpkg -S /usr/share/qtchooser/qt4-x86_64-linux-gnu.conf
qtchooser: /usr/share/qtchooser/qt4-x86_64-linux-gnu.conf


>> > $ /usr/lib/x86_64-linux-gnu/qt5/bin/qdbusviewer
>> > 
>> > Works for me.
>> 
>> you should try starting qdbusviewer not from the full path. Does it work?
>> $ /usr/bin/qdbusviewer
>> qdbusviewer: could not find a Qt installation of ''
> 
> No. And that's a bug in qtchooser. Some variation of #928315, probably.
> 
> I don't use QT programs that much, so I won't comment on whichever is
> broken there. Presumably it's some user configuration file which should
> point at /usr/lib/x86_64-linux-gnu/qt5.
> 
> Personally I see no problem at creating a suitable shell alias.

No customizations at this level - cause later you forget and wonder again
why something does not work. MY solution was great customization :) use
independent and recent Qt5.12

>> A simple proof that after 11 years since they (KDE) promised things will
>> work - it is still the same BS.
> 
> I lost faith in KDE back in "KDE4.0 != KDE4" days.

yes same - ridiculous and 11y later it is still crap. I tend to think this
is a big problem for Free Open Source Software. In the profit driven
market, you source inefficiency and stupidity out. But in FOSS there is no
way to control ideology and SystemD/KDE expolit the freedom.

There is no way to bring them to consciousness. The lack of ability to
participate in normal argumentative communication, to make conclusions and
correct the own stand point is ridiculous.

regards

Re: KDE madness again

[Kumar Appaiah]

On Sun, Nov 03, 2019 at 08:45:49AM +0100, deloptes wrote:
> 
> Long time ago I stopped using KDE, because they started going insane.
> 
> Two days ago upgraded to Buster and now wanted to check if all works fine.
> 
> One of the things I need to use is qdbusviewer - unfortunately there is no
> acceptable alternative. Now I spend already one hour because of the
> stupidity and madness of the way KDE decided to do configuration
> 
> $ qdbusviewer
> qdbusviewer: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/qdbusviewer':
> No such file or directory

I am currently running most packages on testing. On my system,
qdbusviewer seems to be:

# ls -l /usr/bin/qdbusviewer
lrwxrwxrwx 1 root root 9 May  3  2019 /usr/bin/qdbusviewer -> qtchooser

qdbusviewer itself seems to be in qttools5-dev-tools, and I seem to be
able to run it as:

# /usr/lib/x86_64-linux-gnu/qt5/bin/qdbusviewer

Please let mke know if some version information from my side would
help.

Thanks.

Kumar
-- 
Computers are not intelligent.  They only think they are.

Re: KDE madness again

[deloptes]

Reco wrote:

> # apt install qttools5-dev-tools -y

tried several times without success - perhaps because qt4 was installed
before.

> $ /usr/lib/x86_64-linux-gnu/qt5/bin/qdbusviewer
> 
> Works for me.

you should try starting qdbusviewer not from the full path. Does it work?

$ which qdbusviewer
/usr/bin/qdbusviewer

$ ls -al /usr/bin/qdbusviewer
lrwxrwxrwx 1 root root 9 May  3  2019 /usr/bin/qdbusviewer -> qtchooser

$ /usr/bin/qdbusviewer
qdbusviewer: could not find a Qt installation of ''

in the other terminal
$ which qdbusviewer
/opt/custom_x64/qt5.12/5.12.2/gcc_64/bin/qdbusviewer

$ qdbusviewer
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)

A simple proof that after 11 years since they (KDE) promised things will
work - it is still the same BS.

regards

Re: KDE madness again

[Reco]

Hi.

On Sun, Nov 03, 2019 at 08:45:49AM +0100, deloptes wrote:
> 
> Long time ago I stopped using KDE, because they started going insane.
> 
> Two days ago upgraded to Buster and now wanted to check if all works fine.
> 
> One of the things I need to use is qdbusviewer - unfortunately there is no
> acceptable alternative. Now I spend already one hour because of the
> stupidity and madness of the way KDE decided to do configuration

# apt install qttools5-dev-tools -y
$ /usr/lib/x86_64-linux-gnu/qt5/bin/qdbusviewer

Works for me.

Reco

Re: KDE madness again

[Reco]

On Sun, Nov 03, 2019 at 09:47:50AM +0100, deloptes wrote:
> Reco wrote:
> 
> > # apt install qttools5-dev-tools -y
> 
> tried several times without success - perhaps because qt4 was installed
> before.

QT4 has no future, and will be probably removed in bullseye.


> > $ /usr/lib/x86_64-linux-gnu/qt5/bin/qdbusviewer
> > 
> > Works for me.
> 
> you should try starting qdbusviewer not from the full path. Does it work?
> $ /usr/bin/qdbusviewer
> qdbusviewer: could not find a Qt installation of ''

No. And that's a bug in qtchooser. Some variation of #928315, probably.

I don't use QT programs that much, so I won't comment on whichever is
broken there. Presumably it's some user configuration file which should
point at /usr/lib/x86_64-linux-gnu/qt5.

Personally I see no problem at creating a suitable shell alias.


> A simple proof that after 11 years since they (KDE) promised things will
> work - it is still the same BS.

I lost faith in KDE back in "KDE4.0 != KDE4" days.

Reco

Re: KDE desktop not accessible after installation

[Kenward Vaughan]

On 11/2/19 9:06 PM, Jude DaShiell wrote:

I don't know the full details on how kde starts, but have been
researching jovie to my limited capacity.  If spdconf has been run and
had a voice configured it may be possible to hit alt+f2 then type jovie
 or kmouth  and maybe have speech come up and talk.  Me
with no kde experienced sighted assistance let alone any sighted
assistance tried to get Kaos-linux going earlier today and that was a
total failure.
A way exists to install enough xorg packages so you could log in as a
console user and then run startx to bring up kde but I don't have full
details on that one in my notes.  If you did that, you'd be able to run
spdconf in console mode and get it set up and working before your next
attempt at kde.  Good luck, also there is an kde-accessibil...@kde.org
email list for what passes for kde accessibility support.

On Sat, 2 Nov 2019, Kenward Vaughan wrote:


Date: Sat, 2 Nov 2019 14:42:45
From: Kenward Vaughan 
To: debian-user@lists.debian.org
Subject: KDE desktop not accessible after installation
Resent-Date: Sun,  3 Nov 2019 01:43:04 + (UTC)
Resent-From: debian-user@lists.debian.org

Hello,

I have been using XFCE for quit some time, but wanted to play with several
other desktop environments, so I installed Cinnamon, Mate, and KDE.

The KDE choice does not show up in sddm's or lightdm's menu.?? I see no
startkde (has that disappeared?), and I have no .xsession* file.

Anyone know what I am missing to get this to work?

I am running an up-to-date testing system...


Thanks,


Kenward



I'll look for that (spdconf).?? Thanks!


Kenward

Re: KDE desktop not accessible after installation

[Kenward Vaughan]

On 11/2/19 8:42 PM, Keith Bainbridge wrote:

On 3/11/19 5:42 am, Kenward Vaughan wrote:

Hello,

I have been using XFCE for quit some time, but wanted to play with 
several other desktop environments, so I installed Cinnamon, Mate, 
and KDE.??


The KDE choice does not show up in sddm's or lightdm's menu.?? I see 
no startkde (has that disappeared?), and I have no .xsession* file.??


Anyone know what I am missing to get this to work?

I am running an up-to-date testing system...


Thanks,


Kenward


G'day Kenward


Is there a plasma option?

No.?? I have everything else (XFCE, Cinnamon, and Mate) as well as the 
default.



LightDM shows the same.

I wonder if the package lacks the appropriate config script for X 
managers??? (However this is done--I'm not a programmer/maintainer.)



Kenward

Re: KDE desktop not accessible after installation

[Felix Miata]

Kenward Vaughan composed on 2019-11-02 11:42 (UTC-0700):

> I have been using XFCE for quit some time, but wanted to play with 
> several other desktop environments, so I installed Cinnamon, Mate, and KDE.

> The KDE choice does not show up in sddm's or lightdm's menu.?? I see no 
> startkde (has that disappeared?), and I have no .xsession* file.

> Anyone know what I am missing to get this to work?

> I am running an up-to-date testing system...

NAICT, upstream changed the name from startkde to startplasma-x11 and
startplasma-wayland. Testing apparently picked this up this change incompletely,
as in not yet packaged a matching xsession file.
-- 
Evolution as taught in public schools is religion, not science.

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

Felix Miata  ***  http://fm.no-ip.com/

Re: KDE desktop not accessible after installation

[Jude DaShiell]

I don't know the full details on how kde starts, but have been
researching jovie to my limited capacity.  If spdconf has been run and
had a voice configured it may be possible to hit alt+f2 then type jovie
 or kmouth  and maybe have speech come up and talk.  Me
with no kde experienced sighted assistance let alone any sighted
assistance tried to get Kaos-linux going earlier today and that was a
total failure.
A way exists to install enough xorg packages so you could log in as a
console user and then run startx to bring up kde but I don't have full
details on that one in my notes.  If you did that, you'd be able to run
spdconf in console mode and get it set up and working before your next
attempt at kde.  Good luck, also there is an kde-accessibil...@kde.org
email list for what passes for kde accessibility support.

On Sat, 2 Nov 2019, Kenward Vaughan wrote:

> Date: Sat, 2 Nov 2019 14:42:45
> From: Kenward Vaughan 
> To: debian-user@lists.debian.org
> Subject: KDE desktop not accessible after installation
> Resent-Date: Sun,  3 Nov 2019 01:43:04 + (UTC)
> Resent-From: debian-user@lists.debian.org
>
> Hello,
>
> I have been using XFCE for quit some time, but wanted to play with several
> other desktop environments, so I installed Cinnamon, Mate, and KDE.
>
> The KDE choice does not show up in sddm's or lightdm's menu.?? I see no
> startkde (has that disappeared?), and I have no .xsession* file.
>
> Anyone know what I am missing to get this to work?
>
> I am running an up-to-date testing system...
>
>
> Thanks,
>
>
> Kenward
>
>
>

-- 

Re: KDE desktop not accessible after installation

[Keith Bainbridge]

On 3/11/19 5:42 am, Kenward Vaughan wrote:

Hello,

I have been using XFCE for quit some time, but wanted to play with 
several other desktop environments, so I installed Cinnamon, Mate, and 
KDE.??


The KDE choice does not show up in sddm's or lightdm's menu.?? I see no 
startkde (has that disappeared?), and I have no .xsession* file.??


Anyone know what I am missing to get this to work?

I am running an up-to-date testing system...


Thanks,


Kenward


G'day Kenward


Is there a plasma option?

--
Keith Bainbridge

ke1th3...@gmail.com
+61 (0)447 667 468

Re: KDE program 'klipper' is missing from Jessie to Stretch

[Keith Christian]

On Thu, Aug 15, 2019 at 11:39 AM Bob Weber  wrote:

> On 8/15/19 9:49 AM, Keith Christian wrote:
>
> Bob,
>
> Thank you.
>
> I assume the clipboard application that installs by default on stretch can
> be removed and replaced with the (far superior, IMHO) klipper app?
>
> Or can (or should?) the two clipboard applications coexist?
>
> Keith
>
>
>
> On Wed, Aug 14, 2019 at 4:48 PM Bob Weber  wrote:
>
>> On 8/14/19 6:27 PM, Keith Christian wrote:
>>
>> klipper was a feature-rich clipboard manager but I can't find it in Stretch.
>>
>> This is all I see:
>>
>> $ apt-cache search klipper
>> cairo-dock-clipper-plug-in - Clipper plug-in for Cairo-dock
>>
>> cairo-dock-clipper-plug-in claims to be a clone of klipper but the
>> features seem to be hidden.
>>
>> Anyone know if 'klipper' is deprecated or simply not in Debian?  Not
>> much found on web searches even targeting mail.kde.org mailing lists.
>>
>>
>> Its in plasma-workspace now.  Latest update:
>>
>> [2019-02-24] plasma-workspace 4:5.14.5.1-1 MIGRATED to testing
>>
>> It should have been installed with kde/plasma. "apt-file search klipper"
>> finds it.
>>
>>
>>
> I would be careful trying to remove klipper.  The other files in
> plasma-workspace are very important.
>
> apt-file list plasma-workspace:
>
> plasma-workspace: /usr/bin/gmenudbusmenuproxy
> plasma-workspace: /usr/bin/kcheckrunning
> plasma-workspace: /usr/bin/kcminit
> plasma-workspace: /usr/bin/kcminit_startup
> plasma-workspace: /usr/bin/kdostartupconfig5
> plasma-workspace: /usr/bin/klipper
> plasma-workspace: /usr/bin/krunner
> plasma-workspace: /usr/bin/ksmserver
> plasma-workspace: /usr/bin/ksplashqml
> plasma-workspace: /usr/bin/kstartupconfig5
> plasma-workspace: /usr/bin/kuiserver5
> plasma-workspace: /usr/bin/plasma_waitforname
> plasma-workspace: /usr/bin/plasmashell
> plasma-workspace: /usr/bin/plasmawindowed
> plasma-workspace: /usr/bin/startkde
> plasma-workspace: /usr/bin/systemmonitor
> plasma-workspace: /usr/bin/xembedsniproxy
>
> These are just the ones in /usr/bin.  If you try to remove
> plasma-workspace then kde would be gone.
>
> The new klipper seems to have plenty of options.  I use Alt-C -- Open
> klipper at mouse position  a lot (not sure if that is the default).  Makes
> it very easy to see and change what will be pasted.  I run testing here and
> didn't notice the change to the new klipper.  I see the older klipper
> package was removed back in 2015 as part of kde-workspace.
>
>
> --
>>
>>
>> *...Bob*
>>
>
> --
>
>
> *...Bob*
>


Bob,

Thanks for the extra information.

I could not see “klipper” in the process list so I assumed that was not
running.  But now I see that it actually is klipper itself.

It looks like the options are not set for full expression of klipper’s
capability, so I thought it was a clone.

Appreciate the feedback.

Keith


>

Re: KDE program 'klipper' is missing from Jessie to Stretch

[Bob Weber]

On 8/15/19 9:49 AM, Keith Christian wrote:

Bob,

Thank you.

I assume the clipboard application that installs by default on stretch can be 
removed and replaced with the (far superior, IMHO) klipper app?


Or can (or should?) the two clipboard applications coexist?

Keith



On Wed, Aug 14, 2019 at 4:48 PM Bob Weber > wrote:


On 8/14/19 6:27 PM, Keith Christian wrote:

klipper was a feature-rich clipboard manager but I can't find it in Stretch.

This is all I see:

$ apt-cache search klipper
cairo-dock-clipper-plug-in - Clipper plug-in for Cairo-dock

cairo-dock-clipper-plug-in claims to be a clone of klipper but the
features seem to be hidden.

Anyone know if 'klipper' is deprecated or simply not in Debian?  Not
much found on web searches even targetingmail.kde.org  
  mailing lists.


Its in plasma-workspace now.  Latest update:

[2019-02-24] plasma-workspace 4:5.14.5.1-1 MIGRATED to testing

It should have been installed with kde/plasma. "apt-file search klipper"
finds it.


I would be careful trying to remove klipper.  The other files in 
plasma-workspace are very important.


apt-file list plasma-workspace:

plasma-workspace: /usr/bin/gmenudbusmenuproxy
plasma-workspace: /usr/bin/kcheckrunning
plasma-workspace: /usr/bin/kcminit
plasma-workspace: /usr/bin/kcminit_startup
plasma-workspace: /usr/bin/kdostartupconfig5
plasma-workspace: /usr/bin/klipper
plasma-workspace: /usr/bin/krunner
plasma-workspace: /usr/bin/ksmserver
plasma-workspace: /usr/bin/ksplashqml
plasma-workspace: /usr/bin/kstartupconfig5
plasma-workspace: /usr/bin/kuiserver5
plasma-workspace: /usr/bin/plasma_waitforname
plasma-workspace: /usr/bin/plasmashell
plasma-workspace: /usr/bin/plasmawindowed
plasma-workspace: /usr/bin/startkde
plasma-workspace: /usr/bin/systemmonitor
plasma-workspace: /usr/bin/xembedsniproxy

These are just the ones in /usr/bin.  If you try to remove plasma-workspace then 
kde would be gone.


The new klipper seems to have plenty of options.  I use Alt-C -- Open klipper at 
mouse position  a lot (not sure if that is the default).  Makes it very easy to 
see and change what will be pasted.  I run testing here and didn't notice the 
change to the new klipper.  I see the older klipper package was removed back in 
2015 as part of kde-workspace.


-- 



*...Bob*



--


*...Bob*

Re: KDE program 'klipper' is missing from Jessie to Stretch

[Brad Rogers]

On Thu, 15 Aug 2019 07:49:12 -0600
Keith Christian  wrote:

Hello Keith,

>Or can (or should?) the two clipboard applications coexist?

IIRC (from when I installed klipper, a long, lng time ago), they
won't co-exist.  IOW, installation of klipper will require the removal
of it predecessor.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
Well you tried it just the once and found it alright for kicks
Orgasm Addict - Buzzcocks


pgpBbHYOFoWjP.pgp
Description: OpenPGP digital signature

Re: KDE program 'klipper' is missing from Jessie to Stretch

[Keith Christian]

Bob,

Thank you.

I assume the clipboard application that installs by default on stretch can
be removed and replaced with the (far superior, IMHO) klipper app?

Or can (or should?) the two clipboard applications coexist?

Keith



On Wed, Aug 14, 2019 at 4:48 PM Bob Weber  wrote:

> On 8/14/19 6:27 PM, Keith Christian wrote:
>
> klipper was a feature-rich clipboard manager but I can't find it in Stretch.
>
> This is all I see:
>
> $ apt-cache search klipper
> cairo-dock-clipper-plug-in - Clipper plug-in for Cairo-dock
>
> cairo-dock-clipper-plug-in claims to be a clone of klipper but the
> features seem to be hidden.
>
> Anyone know if 'klipper' is deprecated or simply not in Debian?  Not
> much found on web searches even targeting mail.kde.org mailing lists.
>
>
> Its in plasma-workspace now.  Latest update:
>
> [2019-02-24] plasma-workspace 4:5.14.5.1-1 MIGRATED to testing
>
> It should have been installed with kde/plasma. "apt-file search klipper"
> finds it.
>
>
> --
>
>
> *...Bob*
>

Re: KDE program 'klipper' is missing from Jessie to Stretch

[Bob Weber]

On 8/14/19 6:27 PM, Keith Christian wrote:

klipper was a feature-rich clipboard manager but I can't find it in Stretch.

This is all I see:

$ apt-cache search klipper
cairo-dock-clipper-plug-in - Clipper plug-in for Cairo-dock

cairo-dock-clipper-plug-in claims to be a clone of klipper but the
features seem to be hidden.

Anyone know if 'klipper' is deprecated or simply not in Debian?  Not
much found on web searches even targeting mail.kde.org mailing lists.


Its in plasma-workspace now.  Latest update:

[2019-02-24] plasma-workspace 4:5.14.5.1-1 MIGRATED to testing

It should have been installed with kde/plasma. "apt-file search klipper" finds 
it.

--


*...Bob*

Re: kde kmail to much email Unable to fetch item from backend

[Curt]

On 2019-07-04, Thomas  wrote:
> Hello,
> I have an Gmail Mail account and lots of email.
> Iam not able to open this folder succesfull anymore.
> After some time I get this message.

> Unable to fetch item from backend (collection -1) Unable to retrieve item 
> from 
> resource.
>
> Whats the problem and how solve it.
>
> Thanks Thomas
>
>

Maybe this bug (but no solution there):

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900895

-- 
"These findings demonstrate that under appropriate conditions the isolated,
intact large mammalian brain possesses an underappreciated capacity for
restoration of microcirculation and molecular and cellular activity after a
prolonged post-mortem interval." From a recent article in *Nature*. Holy shit.

Re: kde kmail to much email Unable to fetch item from backend

[Keith Christian]

I have no suggestions for your Kmail problem, you might try Thunderbird and
see if that does the job or else email the KDE team.

Keith

On Thu, Jul 4, 2019 at 10:56 AM Thomas  wrote:

> Hello,
> I have an Gmail Mail account and lots of email.
> Iam not able to open this folder succesfull anymore.
> After some time I get this message.
>
> Unable to fetch item from backend (collection -1) Unable to retrieve item
> from
> resource.
>
> Whats the problem and how solve it.
>
> Thanks Thomas
>
>

Re: KDE Bluedevil

[David Wright]

On Wed 22 Aug 2018 at 22:58:00 (-0400), Timothy M Butterworth wrote:
> On 8/21/18, David Wright  wrote:
> > On Mon 20 Aug 2018 at 20:12:57 (-0400), Timothy M Butterworth wrote:
> >> In Debian 9.5 KDE Bluedevil is unable to add devices. Is their any fix
> >> for this other then using GNOME Blueman tool.
> >
> > In the absence of other replies, can you explain what you mean by
> > "add devices".
> >
> > I use bluetooth, bluez, bluez-tools and bluez-obexd for what I do,
> > but that might not be all you and others do.

> When I try to pair a new device it fails with Bluedevil. I tried to
> pair multiple devices. I installed GNOME Blueman and was able to pair
> the devices. Now that the devices have been paired I can connect to
> and disconnect from them with Bluedevil.

I don't use GUIs to pair, but run bluetoothctl to pair a new device
in an xterm. Here's a typical conversation:

$ bluetoothctl
[NEW] Controller 0C:xx:xx:xx:xx:xx wren [default]
[NEW] Device 50:xx:xx:xx:xx:xx already
[NEW] Device 0B:xx:xx:xx:xx:xx paired
[NEW] Device 00:xx:xx:xx:xx:xx devices
[bluetooth]# agent on
Agent registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# pairable on
Changing pairable on succeeded
[bluetooth]# discoverable on
Changing discoverable on succeeded
[CHG] Controller 0C:xx:xx:xx:xx:xx Discoverable: yes ← pair after this line 
received
[NEW] Device F8:xx:xx:xx:xx:xx F8-xx-xx-xx-xx-xx
[CHG] Device F8:xx:xx:xx:xx:xx 
[CHG] Device F8:xx:xx:xx:xx:xx ServicesResolved: yes
[CHG] Device F8:xx:xx:xx:xx:xx Paired: yes
[CHG] Device F8:xx:xx:xx:xx:xx ServicesResolved: no
[CHG] Device F8:xx:xx:xx:xx:xx Connected: no
[bluetooth]# quit
Agent unregistered
[DEL] Controller 0C:xx:xx:xx:xx:xx wren [default]
$ 

The main use I have is transfer of files (photos, music, etc) back and
forth. I always have a command running (started in ~/.xsession):
$ yes | bt-obex -s /tmp/
The idea is that I don't have to intervene on the PC to transfer a
file to it (or even be in the same room necessarily).
I should point out that the /tmp/ argument is ignored in stretch;
files arrive in ~/.cache/obexd/ regardless.

To send files from the PC, I use the command
$ bt-obex -p galaxy path/to/file
where galaxy is the bluetooth name of the device. In this case, I
obviously have to remember to turn bluetooth on in the device.
(Leaving bluetooth on will discharge the battery more quickly.)

I haven't had much success with  bt-obex -f  (ie the FTP service)
so I don't bother with that.

One wrinkle when pairing: to get the bluetooth name of the device sent
to the PC, the device should be paired while it is visible to other
devices (rather than hidden). Otherwise it will still pair, but
without setting a name, so to send files to the device you have to
use its MAC (long and unmemorable) rather than its name (memorable
and short).

And finally, this method does not work (on an older laptop) in jessie:
it refuses to make itself discoverable. It still works with wheezy,
which runs using the older method, bluetooth-agent.

Cheers,
David.

Re: KDE Bluedevil

[Timothy M Butterworth]

David,

When I try to pair a new device it fails with Bluedevil. I tried to
pair multiple devices. I installed GNOME Blueman and was able to pair
the devices. Now that the devices have been paired I can connect to
and disconnect from them with Bluedevil.

Tim

On 8/21/18, David Wright  wrote:
> On Mon 20 Aug 2018 at 20:12:57 (-0400), Timothy M Butterworth wrote:
>> In Debian 9.5 KDE Bluedevil is unable to add devices. Is their any fix
>> for this other then using GNOME Blueman tool.
>
> In the absence of other replies, can you explain what you mean by
> "add devices".
>
> I use bluetooth, bluez, bluez-tools and bluez-obexd for what I do,
> but that might not be all you and others do.
>
> Cheers,
> David.
>
>

Re: KDE Bluedevil

[David Wright]

On Mon 20 Aug 2018 at 20:12:57 (-0400), Timothy M Butterworth wrote:
> In Debian 9.5 KDE Bluedevil is unable to add devices. Is their any fix
> for this other then using GNOME Blueman tool.

In the absence of other replies, can you explain what you mean by
"add devices".

I use bluetooth, bluez, bluez-tools and bluez-obexd for what I do,
but that might not be all you and others do.

Cheers,
David.

Re: KDE 4.4.3 in unstable

[Martin Steigerwald]

Am Donnerstag 06 Mai 2010 schrieb Boyd Stephen Smith Jr.:
> > However, whether to ship akonadi trunk/beta/final of the next version
> > is another question which is still open. In my opinion, Akonadi
> > itself is
> >
> >  pretty mature so it might be doable.
> 
> I didn't complain well.  This is the true crux of my complaint.  I
> don't  think stable users want an Akonadi that only supports one
> backend.  If nothing else, it makes bugs harder to work around, and I
> find staying with stable generally requires working around a non-RC
> bug or two during its lifetime.
> 
> Virtuoso, PostgreSQL, or SQLite -- any one of those as an option would
> satisfy  me, and I can't really speak for others.

SQLite or Virtuoso might be interesting to reduce resource footprint.

And it would be nice if Akonadi works via NFS, where at least regarding 
the wiki MySQL's inno db tables might be a problem. I asked on kde-pim and 
kdepim-users mailing lists. And got quite some feedback. Apparently it 
might just work if only one Akonadi is running and the network environment 
and nfs servers are stable. Fair enough for now. KMail never worked in 
mutiple instances.

And one user pointed out that its possible to use a central MySQL server 
with local filesystem for Akonadi stuff.

Well let's see.

-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7


signature.asc
Description: This is a digitally signed message part.

Re: Kde 3.5 ...

[deloptes]

Martin Steigerwald wrote:

> I think mainly Akonadi, Nepomuk, Plasma, a bit also Phonon needs
> quite some more stabilization and performance work.

After 10years - those basic applications still cause problems ... and you
call it "more stabilization and performance work" ... come on - jokes.

The problem as I understood it is fundamental disagreement between stability
and functionality. 
New KDE missed the target in my opinion, but as free software, it has always
another chance. It missed the target, because they promised to deliver and
delivered never in the past 10y.
Same story with systemd - only mess and problems - and it seems it will stay
like this.
So I stick to the old 3.5 which is now trinity 14 and for a desktop it is
great. Indeed there are still some bugs here and there, but nothing you
could call criticall.
For mobile devices - meego and mer are again the better choice. However a
friend uses KDE5 and it looks much better, works much better and is more
promising ... but again with issues.
If they finally manage to deliver now - it will be great and I will be
glad - after 10y.
>From code perspective (design etc) new KDE looks great, compared to old KDE
it is much easier to work with the code, but I guess there are still some
fundamental misunderstandings.

Just my 5cent.

regards

Re: Kde 3.5 ...

[Martin Steigerwald]

Am Donnerstag 06 Mai 2010 schrieb Sune Vuorela:
> On 2010-05-06, Curt Howland  wrote:
> > On Thursday 06 May 2010, Ana Guerrero was heard to say:
> >> On Thu, May 06, 2010 at 03:17:43AM -0300, Jorge Gonçalves wrote:
> >> > Maybe use dummy packages, or rename the packages so that KDE 3.5
> >> > could remain installed, and not be forced to upgrade to Kde4.
> >> 
> >> No, there is not sane way and there is nobody interested on it.
> > 
> > While the former is certainly true, the latter is demonstrably false.
> 
> Where is your code?
> 
> I will repeat "No one is interested in doing it".

That does not seem to be entirely true as was mentioned elsewhere in this 
thread:

http://trinity.pearsoncomputing.net/

However this seems far away from the man-power behind KDE 3 until 3.5.10. 
To truly get forward with this one it appears to me that way more 
developers are needed. Who then would have less or no time to work on 
improving KDE 4.

I will stick with KDE 4 - as long as it - as a whole - does get better 
from release to release. It already got better. It already takes longer 
than with KDE 3 to get as stable and nice to work with as KDE 3.5.10, but 
with help of everyone it eventually will get there. And KDE 3.5.10 had 
issues as well. Especially with KMail that Boyd is so interested in. KMail 
as of KDE 4.3 *and* 4.4 appears to be way more stable to me regarding that 
annoying index handling issues. And it has been improved a lot by Thomas 
McGuire and others. Okular is fine, Dolphin is fine, KWrite, Kate are fine, 
Dragon player is quite fine, Amarok is quite fine lots of other apps are 
fine. I think mainly Akonadi, Nepomuk, Plasma, a bit also Phonon needs 
quite some more stabilization and performance work.

-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7


signature.asc
Description: This is a digitally signed message part.

Re: KDE 4.4.3 in unstable

[Martin Steigerwald]

Am Donnerstag 06 Mai 2010 schrieb Modestas Vainius:
> Hello,
> 
> On ketvirtadienis 06 Gegužė 2010 23:48:43 Boyd Stephen Smith Jr. wrote:
[...]
> > >  YOU assume that your truth is an ultimate one.
> > 
> > Not really.  I made objective statement about KMail based on
> > observable facts. I also voiced an opinion that I based on that
> > statement.
> 
> What facts? That kdepim/kmail needs akonadi? That's hardly news.
> Akonadi integration is not stable enough? There is still time to
> improve it. That's what Ana's blog was about.
> 
> > >  If YOU have so
> > >  many problems with particular piece of software, look for better
> > >  options or read the first part of this mail again.
> > 
> > I have problems with a very narrow selection of selection of the
> > software. Specifically, I don't want to need MySQL installed in
> > order to use KMail effectively in Debian stable.
> 
> It is not like every mail client on the market suddenly needs MySQL.
> Actually, kmail is probably unique in this area.

Again. AFAIK KMail doesn't use Akonadi at all. Its the new KAddressBook 
that based on Akonadi. And since KMail uses it for address completion...

For the user it looks as if KMail uses Akonadi, but to the best of my 
knowledge it doesn't - at least not directly. Otherwise there wouldn't be 
much point in the akonadi- / nepomuk-based rewrite of KMail as KMail 2.

> > There are a number of solutions to this.  Newer Akonadi should run on
> > non- MySQL data stores.  Older KMail doesn't talk to Akonadi. 
> > Patches could be applied to either.  Stable could include software
> > from multiple KDE releases, as has been done before.
> 
> What I tried to say to you all this time, if Akonadi renders Kmail
> unusable to you, switch the client! Akonadi by itself is not a bug, it
> is not going away! Take it or switch to something else, simple as
> that.

And I want to add: It does not render it unusable for everyone.

Even when Akonadi does not start up cleanly, which happens on first start 
of Kontact for example as I reported already, I still *can* use KMail. Its 
just that the address book function do not work properly then. Although I 
didn't even verify this. Cause even when I get the Akonadi startup errors, 
KAddressBook shows the list of the people in my address book, its just 
ghosted out and not clickable. So maybe address completion would still 
work. But even if it doesn't, KMail as a whole actually does still work 
then.

Anyway, most important is to file and an all bugs with Akonadi in KDEPIM 
upstream ASAP. And that is where I suggest that people - including you 
Boyd - put their energy now.

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7


signature.asc
Description: This is a digitally signed message part.

Re: kde in stretch is very usable

[Roberto C . Sánchez]

On Sun, Dec 10, 2017 at 10:15:17AM +0100, deloptes wrote:
> bw wrote:
> 
> > I won't chime in on the main topic, there has been way too much already,
> > but this is really undeserved.  The plasma implementation the debian
> > maintainers put together for stretch is really pretty nice.
> > 
> > No, it's not perfect, but I'm really good, so it's close. ;->
> 
> I recently had a look at KDE5 and it looked really good.
> However still not perfect and KDE promised 2008 that it will soon be
> usable :)
> 
And in 1991 Linus urged only hobbyists to look at his new project, since
GNU Hurd was nearly ready and that was were serious developers would
want to look :-)

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: kde in stretch is very usable

[deloptes]

bw wrote:

> I won't chime in on the main topic, there has been way too much already,
> but this is really undeserved.  The plasma implementation the debian
> maintainers put together for stretch is really pretty nice.
> 
> No, it's not perfect, but I'm really good, so it's close. ;->

I recently had a look at KDE5 and it looked really good.
However still not perfect and KDE promised 2008 that it will soon be
usable :)

regards

Re: KDE startup instabiel in debian 9.2

[Eric Meijer]

On 11/16/2017 09:08 AM, Jeroen Mathon wrote:

Heb je KDE geïnstalleerd via de Live DVD(KDE) of heb je dit vanuit een
minimal installatie gedaan?

Een update van Jessie.
Eric

Re: KDE startup instabiel in debian 9.2

[Eric]

On 11/16/2017 12:34 AM, Sjoerd Hiemstra wrote:

Eric:

Ik gebruik KDE als mijn desktop-omgeving.  Sinds ik debian stretch
geïnstalleerd heb is de startup van KDE instabiel.

Soms krijg ik alleen een zwarte achtergrond met de kde "throbber" in het
wit en gebeurt er verder niets

Soms krijg ik een zwarte achtergrond en thunderbird (die ik automatisch
opstart), zonder decoraties, zonder taakbalk.

Soms krijg ik een redelijk normaal ogende desktop, maar hebben windows
geen decoraties.

Ik heb iets dergelijks ook wel eens gezien. Sommige pakketten, die KDE
nodig heeft, zijn dan niet geïnstalleerd. Bijvoorbeeld kwin, dat zorgt voor
de windowdecoraties.
Lijkt me niet het probleem. Uiteindelijk werkt alles, dus alle pakketten 
die nodig zijn, zijn aanwezig.

Eric

Ik zou zeggen, voer dit commando uit, dan is alles weer compleet:

# apt-get install kde-full

Re: KDE startup instabiel in debian 9.2

[Sjoerd Hiemstra]

Jeroen Mathon:
> Ik raad zelf de KDE live image aan, die komt met een hoop extra
> configuraties waardoor die optimaal werkt.
> 
> Had zelf ook problemen met de Minimale installatie.

Met de door mij genoemde simpele methode om alles wat ontbreekt, alsnog toe
te voegen, draait KDE nu probleemloos op Stretch.
Geen idee wat je met die 'extra configuraties' bedoelt. Ik heb het complete
KDE met alle mogelijke configuraties.

KDE vind ik trouwens leuk om er ook bij te hebben, maar voor het meeste
werk vind ik Openbox of WindowMaker toch wel erg handig.

Re: KDE startup instabiel in debian 9.2

[Jeroen Mathon]

Ik raad zelf de KDE live image aan, die komt met een hoop extra
configuraties waardoor die optimaal werkt.

Had zelf ook problemen met de Minimale installatie.


On 11/16/2017 12:50 PM, Sjoerd Hiemstra wrote:
> Jeroen Mathon:
>> Sjoerd:
>>> Eric:
 Ik gebruik KDE als mijn desktop-omgeving.  Sinds ik debian stretch 
 geïnstalleerd heb is de startup van KDE instabiel.

 Soms krijg ik alleen een zwarte achtergrond met de kde "throbber" in
 het wit en gebeurt er verder niets

 Soms krijg ik een zwarte achtergrond en thunderbird (die ik
 automatisch opstart), zonder decoraties, zonder taakbalk.

 Soms krijg ik een redelijk normaal ogende desktop, maar hebben
 windows geen decoraties.
>>> Ik heb iets dergelijks ook wel eens gezien. Sommige pakketten, die KDE
>>> nodig heeft, zijn dan niet geïnstalleerd. Bijvoorbeeld kwin, dat zorgt
>>> voor de windowdecoraties.
>>>
>>> Ik zou zeggen, voer dit commando uit, dan is alles weer compleet:
>>>
>>> # apt-get install kde-full
>> Heb je KDE geïnstalleerd via de Live DVD(KDE) of heb je dit vanuit een
>> minimal installatie gedaan?
> Vanuit een minimal installatie, een net-installatie. Als die eenmaal
> draait, dan vraagt de installer wat je verder nog wilt installeren. Daar
> heb ik o.a. KDE aangevinkt, dat wordt daarna nog gedownload.
> Maar dat is al lang geleden, in Etch of zo.
> Siondsdien is er bij KDE nogal wat veranderd, zoals die Plasma desktop en
> de overgang van QT4 naar QT5. Blijkbaar heeft men de boel niet helemaal bij
> elkaar weten te houden, om het maar zo te zeggen. Maar dat verbaast me
> eigenlijk niet.
>
> Maar met het installeren van kde-full is het volgens mij eenvoudig te
> verhelpen. Het is een soort meta-package dat ervoor zorgt dat alle nodige
> onderdelen van KDE weer aanwezig zijn.
>