Re: ssh-agent not running on Plasma 6 Wayland session

[Erwan David]

On Tue, Aug 27, 2024 at 04:43:39PM CEST, Martin Steigerwald 
 said:
> Sedat Dilek - 27.08.24, 16:22:08 CEST:
> > Do you miss ksshaskpass package?
> 
> No. It is installed.
> 
> On X11 ssh-agent is running, on Wayland not.
> 

On plasma5 ssh-agent is startted (by default) by /etc/X11/Xsession (see
/etc/X11/Xsession.d/90x11-common-use-ssh, thats the latest step on my
investigation why emacs.service does not have the right environment for using
ssh-agent)
Might be totally different on plasma6.

Is the user service ssh-agent.service activated ?

-- 
Erwan David

kwallet6 in testing

[Erwan David]

Upgrading my testing, I am proposed to install kwallet6 (and 
dependencies) instead of kwallet5* Is it safe or should I wait for the 
whole Kde/Plasma 6 to arrive in Testing ?


(Yes I know in testing you may have broken packages, that's why I ask 
before upgrading)

Screen Numbering in Plasma 5

[Erwan David]

I have 3 screens. I can set which one is middle, left or right. However, 
I cannot  find how to select which one is number 1, 2 or 3 for the "move 
to screen" menu, (or 0,1,2 for the keyboard shortcuts).


Does someone have a hint at this (Plasma 5 in testing or stable).

Re: How to not update package list through plasma discover ?

[Erwan David]

Le 12/06/2024 à 12:57, Geoff a écrit :

Erwan David wrote:

Le 12/06/2024 à 10:25, yaros a écrit :

Dnia środa, 12 czerwca 2024 10:14:42 CEST Erwan David pisze:
Le 12/06/2024 à 10:05, yaros a écrit :

Dnia wtorek, 11 czerwca 2024 17:55:50 CEST Erwan David pisze:
I'll be temporarily with a bad connexion. During this time I'd like
plasma-discover to not update the package list. How can I do this ?

There is no option in discover for this. I can remove the package but
that would be a bit harsh



Open Plasma discover go to Settings -> Software sources -> Updates 
-> uncheck position Check for updates.




I do not have this in debian testing. I only have a list of all 
sources,

If I uncheck a source there, it is commented in /etc/apt/sources.list.d
thus preventing me to manualy update


I have Debian testing too and I have this option. Maybe my 
translation is not accurate, because I'm using not english interface 
but:
when I go to Settings/Configuration in Plasma Discover i see 
settings for Flatpak, Firmware updates, Snap and
Debian GNU/Linux trixie/sid (this appears after some time after 
click settings). To the right is text Default sorces and more right 
is clickable text Software sources. When i click it new window 
appears (root password needed) and in Updates tab I can uncheck 
option Check for updates.







Alas I do not have this, I can only select le different sources (and 
it changes the /etc/apt/sources.list.d) I'll try purging and 
reinstalling plasma-discover






What about System Settings -> Software Update?



Did not work either...


But It seems that masking packagekit.service does the job, with some 
small drawbacks (eg I get warning when doing a manual apt update). A 
clear option to disable it but keeping the notification (or a separate 
notifier that there are availabe updates, eg after a apt-daily.timer 
trigger) would be handy.

Re: How to not update package list through plasma discover ?

[Erwan David]

Le 12/06/2024 à 10:25, yaros a écrit :

Dnia środa, 12 czerwca 2024 10:14:42 CEST Erwan David pisze:
Le 12/06/2024 à 10:05, yaros a écrit :

Dnia wtorek, 11 czerwca 2024 17:55:50 CEST Erwan David pisze:
I'll be temporarily with a bad connexion. During this time I'd like
plasma-discover to not update the package list. How can I do this ?

There is no option in discover for this. I can remove the package but
that would be a bit harsh



Open Plasma discover go to Settings -> Software sources -> Updates -> uncheck 
position Check for updates.




I do not have this in debian testing. I only have a list of all sources,
If I uncheck a source there, it is commented in /etc/apt/sources.list.d
thus preventing me to manualy update


I have Debian testing too and I have this option. Maybe my translation is not 
accurate, because I'm using not english interface but:
when I go to Settings/Configuration in Plasma Discover i see settings for 
Flatpak, Firmware updates, Snap and
Debian GNU/Linux trixie/sid (this appears after some time after click 
settings). To the right is text Default sorces and more right is clickable text 
Software sources. When i click it new window appears (root password needed) and 
in Updates tab I can uncheck option Check for updates.






Alas I do not have this, I can only select le different sources (and it 
changes the /etc/apt/sources.list.d) I'll try purging and reinstalling 
plasma-discover




--
Erwan David

Re: How to not update package list through plasma discover ?

[Erwan David]

Le 12/06/2024 à 10:05, yaros a écrit :

Dnia wtorek, 11 czerwca 2024 17:55:50 CEST Erwan David pisze:
I'll be temporarily with a bad connexion. During this time I'd like
plasma-discover to not update the package list. How can I do this ?

There is no option in discover for this. I can remove the package but
that would be a bit harsh



Open Plasma discover go to Settings -> Software sources -> Updates -> uncheck 
position Check for updates.



I do not have this in debian testing. I only have a list of all sources, 
If I uncheck a source there, it is commented in /etc/apt/sources.list.d 
thus preventing me to manualy update


--
Erwan David

How to not update package list through plasma discover ?

[Erwan David]

I'll be temporarily with a bad connexion. During this time I'd like 
plasma-discover to not update the package list. How can I do this ?


There is no option in discover for this. I can remove the package but 
that would be a bit harsh

Re: Package management tool

[David Hill]

On 2023-12-27 7:32 a.m., Luc Castermans wrote:

hi

mini howto would be nice. I use "apt" too, never was aware e.g. 
Firefox is not seen be Discover although enabled in sources.list


Luc


Sedat Dilek  schreef op 27 december 2023 
13:16:50 UTC:


On Tue, Dec 26, 2023 at 11:27 PM Marc Haber
 wrote:

Hi, on my new notebook I am trying to do more administrative
tasks in graphical tools to be able to answer beginners'
questions in the unix user group. That also means package
management, which I usually do with apt on the command line.
KDE Discover seems to not quite the package management tool I
am looking for. It only says that my Debian unstable offers
like 2000 packages for installation (the notebook alone has
2400 packages installed), it says that the installation only
has 240 packages installed. And it cannot find the firefox
browser. (1) Am I holding KDE Discover wrong? 


Hi Marc, there is some work to be done to get KDE/discover run
properly and update all the software catalogues while recognizing
your sources.list. This resulted in more MB to be downloaded for
all my repository-information - when using/checked with apt. But I
never installed software via KDE/discover - just displayed what
software is available. Maybe, I can share my mini-howto when I am
in front of my Debian system. IIRC apt-config-xxx and packagekit
needs to be adapted. When I was using mobile network connection I
disabled some settings in apt-config-xxx to reduce the amount of
(repository) data which is required by KDE/discover to build the
software-catalogues.

(2) If KDE Discover is not what I am looking for, what is the
recommended way to do package management, install, deinstall,
configure, purge Debian packages from the Debian archive on a
KDE system? 


/me relies on good old apt for software-upgrades. BR, -Sedat-

I use too use apt, but there is Apper. It is not as "shiny and bright" 
as Discover but does provide a KDE GUI to package management and seems 
to include all packages in sources.list. It's very basic - it does not 
seem provide for purging or autoremove for example.

No transparencies ?

[Erwan David]

Today's "minor" upgrade in testing added transparences in menus where 
there waher non. How can I set that I do nit want transparent 
background. It makes difficult to read lenus (at least for me).

Re: sddm 0.20.0-1 : kdm not starting on tty7

[Erwan DAVID]

Le 30 juin 2023 13:27:44 Andy Wood - BAS  a écrit :


Hi,

On Debian testing, after the recent update of sddm from 0.19.0-5 to 0.20.0-1
all previous expected tty usage seems to have gone out of the window (if you
pardon the pun).
kdm seems to be on tty2, tty3/4/5/6 all provide a text login and nothing is
starting on tty7?

I am confused.  Are others seeing this?
Andy.


This email and any attachments are intended solely for the use of the named 
recipients. If you are not the intended recipient you must not use, 
disclose, copy or distribute this email or any of its attachments and 
should notify the sender immediately and delete this email from your 
system. UK Research and Innovation (UKRI) has taken every reasonable 
precaution to minimise risk of this email or any attachments containing 
viruses or malware but the recipient should carry out its own virus and 
malware checks before opening the attachments. UKRI does not accept any 
liability for any losses or damages which the recipient may sustain due to 
presence of any viruses.



I did not check but that was in changelog for sddm package (upgrade yesterday)


* Drop patch 03_vt7-minimum-vt.diff and switch back to upstream default of
  spawning greeter on VT1.

--
Erwan David

Re: plasmashell crashes

[Erwan David]

Le 08/01/2023 à 12:53, Martin Steigerwald a écrit :

piorunz - 08.01.23, 12:46:35 CET:

On 08/01/2023 11:43, Martin Steigerwald wrote:

piorunz - 08.01.23, 12:33:06 CET:

Debian Testing is experiencing high volume of plasmashell and kded5
crashes. Just caught clean crash of plasmashell with full
backtrace, I was clicking nothing on the desktop with focus on
another program, and plasmashell just crashed. But this time it
restarted itself and desktop was usable again immediately, so I
didn't wasted my work. X11, Radeon card, AMD64 machine with ECC
RAM and RAID1 storage. Bug report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028197

No crashes here on Unstable.

ThinkPad T14 AMD Gen 1 with integrated AMD Renoir Vega 7 graphics.

Don't have Apper installed.

I have apper installed. "KDE package management tool using
PackageKit". What is it for, can I uninstall it without consequence?
I don't use Discover or other KDE tools too much to install software,
and can live without it, if it comes to that.

>From what I read from this whole thread, I'd recommend to remove it.

Apper is somewhat similar to Discover, but I am not sure whether it is
even maintained by upstream anymore.

However it is apper which used to display in systray when upgrades or 
security upgrades were available.

Re: kded5 crashes

[Erwan David]

Le 06/01/2023 à 00:54, Miguel A. Vallejo a écrit :

Hello!

Once I removed apper, plasmashell goes to 100% after login for about
30 seconds and then, everything goes ok, no extra CPU usage and
everything seems to work.

I guess it is ok for now.

Thank you!




So a bug should be open against apper ?

Re: kded5 crashes

[Erwan David]

Le 05/01/2023 à 20:11, Miguel A. Vallejo a écrit :

I'm still experiencing constant kded5 crashes, but after a few days of
googling I didn't find anything relevant... Is it a Debian Unstable
only issue?

Greetings




On testing it crashes when apper sees upgrades are available and it's 
icon has to be switch on in systray.


It wa	s already said here, I do not know whether it is a kded5 or a 
apper bug.

Krunner : how to choose order of plugins

[Erwan David]

Hello

In krunner I get the folers/files before the applications. But I use it 
moire pften to start an apllication than to look for a file. I did not 
find a way to specify I want the applications before he files in kruner 
menu. Is it possible ?


--
Erwan

kwin_x11 loses connexion to X server

[Erwan David]

Hello

From time to time, I lose kwin_x11

I have this kind of errors in the log

déc. 13 16:06:36 ot-port-145 kwin_x11[73305]: The X11 connection broke: 
I/O error (code 1)
déc. 13 16:06:36 ot-port-145 kwin_x11[73305]: X connection to :0 broken 
(explicit kill or server shutdown).
déc. 13 16:06:37 ot-port-145 kwin_x11[73305]: 
Application::crashHandler() called with signal 11; recent crashes: 1
déc. 13 16:06:37 ot-port-145 systemd[1670]: plasma-kwin_x11.service: 
Consumed 9min 49.960s CPU time.


No other X client loises the connection, what could be the cause ?


(Debian testing, up to date)


Thanks


--
Erwan

Almost nothing in .xsession-errors

[Erwan David]

Hello,

I am running testing with plasma 5.26

Today I got a crash of plasma, and I tried to look in .xsession-errors : 
there is almost nothing


For each session, only

Xsession: X session started for edavid at Fri Nov  4 12:31:19 CET 2022
dbus-update-activation-environment: setting 
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus

dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting 
XAUTHORITY=/home/edavid/.Xauthority

localuser:edavid being added to access control list
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1

Is it the new normal ? Or should I configure something to get more 
versose informations in .xsession-errors ?


Thanks

Any chance of getting the fix for autocompletion or kmail addresses failure into Debian?

[David Goodenough]

https://bugs.kde.org/show_bug.cgi?id=458042[1]

It would appear that there is a fix, and this is a regression 
from the previous release.  It would be nice not to have to 
wait for the next full release.


[1] https://bugs.kde.org/show_bug.cgi?id=458042

Re: Managing 3 screens

[Erwan David]

Le 15/04/2022 à 13:44, Xavier Brochard a écrit :
In display settings, check "record properties for this screen 
arrangement" (or something like that). Then create a second screen 
arrangement and record settings again.


It it doesn't switch automaticaly between home and work (based on 
display identifiers), you will have to choose the right one manualy.




It was set to "save for any display arrangement", I put it to "For only 
this specific display arrangement".


I'll let you know once I get back at work, then back at home.

Managing 3 screens

[Erwan David]

Hello

On same laptop, I have at work 3 desktops (from left to right laptop, 
external 1, external 2) External 2 is primary


At home same setting (but external screens are obviously different). 
External 2 being declared primary in the system settings, no problem 
with it, however laptop screen and external 1 exchange their widgets 
between home and work.


What would be the right hing to do to keep widgets on the choosen screen ?

--
Erwan

Re: Plasma 5.24 coming to Bookworm/testing

[Erwan David]

Le 05/03/2022 à 18:01, Diederik de Haas a écrit :

Hi,

On the 14h apt update 'round' I noticed the following packages became
available:
bluedevil drkonqi kactivitymanagerd kde-config-sddm kgamma5 kinfocenter
kmenuedit konsole konsole-kpart kscreen ksshaskpass kwayland-integration
kwrited layer-shell-qt libkf5baloowidgets-bin libkf5baloowidgets5
libkf5screen-bin libkf5screen7 liblayershellqtinterface5 libokular5core9
libpam-kwallet-common libpam-kwallet5 libssh2-1 milou okular okular-extra-
backends plasma-disks plasma-nm plasma-pa polkit-kde-agent-1 yakuake

Which is ~ 30 packages, but the whole of 5.24 is 100+ IIRC, so only a part has
transitioned to testing now. So doing an (full-)upgrade *now* is probably not
a good idea. Wait a few days or when it looks like all packages are available
to prevent getting a version mismatch and any problems that may arise from it.

Unless you know how to deal with potential problems and want to see if you can
potentially help improve things, then now could be a good time to break your
installation and help figuring out how to fix it ;-)

Cheers,Zahony
   Diederik


I saw same thing. Similarly some KDE porgrams (eg okular) have a 
possible upgrade from 21.08 to 21.12 I prefered to keep them until all 
is avaiblable.

Re: Plasma 5.24 coming to unstable

[Erwan David]

Le 27/02/2022 à 16:41, Patrick Franz a écrit :

Hi,


Thanks for the advice, but too late for me: my KDE is broken now.
You should ideally warn one or two days before packages are uploaded.

I'm sorry about the mistake I made in plasma-workspace, but it's fixed
and Plasma 5.24 installs cleanly now.

As for the advice, we've stated this multiple times to not mix versions.
Plasma is quite the dependency hell and it's incredibly difficult to
both get it right and prevent unintended consequences at the same time.

I disagree with having to give a warning 2 days in advance. If you run
unstable, you should read mailing-lists, hang around in IRC and/or
install apt-listbugs.


I use testing, but should be careful also (some pacakges do not go into 
testing as soon as the others). My question is always the same : How do 
I know wether all plasma packages will upgrade or not ?


For the framework, I wait until I get the upgrade of plasma-framework 
package. But I do not know how to check that the upgrade will upgrade 
all installed plasma packages. Does someone have a trick for this ?

Disabling/enabling touch pad on keyboard

[Erwan David]

Hi,

I use debian testing. Sometime, by walking on the keyboard my cat 
disables the touchpad of my Lenovo T590. I used to be able to get it 
back by disabling and reenabling it in the system settings (or with the 
systrau "touchpad" icon), but it does not do anything anymore .


Do someone have a solution to reenabe it without logging out ?

Thanks

Activités

[Erwan David]

Hello,

I am looking for' explations, docs tutorials about activities in Plasma 5.
All I find is either for plasma 4 with menu entries which do not exist 
anymore or "you certainly know activities".


My questions are : how does this articulate with virtual desktops and 
multi-screen ?
Are windows/applications linked to a particular activity or can they be 
present on al activities ?

How do we configure this ?

Please if you know of such a documentation or tutorial, send the link

Thanks

Testing : is it OK to upgrade ?

[Erwan David]

Hi,

For quite some time I see no new KDE package arrivi,g in testing. 
However I have ~ 40 packages only as upgrade candidates, but 96 on 
version 5.21 or 4:5.21 Is it OK to upgrade now or not ?

Re: 5.23 starting move to testing

[Erwan David]

Le 19/10/2021 à 21:52, Shai Berger a écrit :
> On Tue, 19 Oct 2021 16:37:14 +0200 (CEST)
> Borden  wrote:
>
>> 17 Oct 2021, 07:16 by b...@fineby.me.uk:
>>> Taking note of the thread regarding updating to 5.23 in Sid, I'll be
>>> holding off for a few days until migration to testing is complete.
>>>  
>> I'm sure this has been answered before, but this seems to be a
>> perennial issue wherever there's a major upgrade. Since Testing is
>> supposed to be free of known system-breaking errors, why can't the
>> packages be held back until the it's all ready?
>>
> This not only has been answered before in general -- it has been
> effectively discussed on this very list, only last week.
>
> As a user, you can use "apt upgrade" or "aptitude safe-upgrade". With
> either of these, you will not get half-system updates. If the whole
> upgrade is ready, you'll get it; if it isn't, you will get suggestions
> to either keep older versions of packages with updates, or drop the
> not-yet-updated packages. Then, you should choose what to do according
> to your taste and the selection of not-yet-updated packages.
>
> Asking for any non-stable flavor to act like stable is making the
> packagers' work harder, and IMO as a grateful user who is not involved
> in packaging, that is completely uncalled for.
>
> Hope this helps,
>   Shai.
>
>
With apt upgrade on testing, you often get partial non working upgrade.
I was recently told to "only do complete upgarde", but when I asked how
to know the upgrade is compelte, I got no answer.

Tonight apt list --upgradable lists me

bluedevil/testing,unstable 4:5.23.0-1 amd64 [upgradable from: 4:5.21.5-2]
drkonqi/testing,unstable 5.23.0-1 amd64 [upgradable from: 5.21.5-2]
kactivitymanagerd/testing,unstable 5.23.0-1 amd64 [upgradable from:
5.21.5-2]
kgamma5/testing,unstable 5.23.0-1 amd64 [upgradable from: 5.21.5-2]
kinfocenter/testing,unstable 4:5.23.0-1 amd64 [upgradable from: 4:5.21.5-2]
kmenuedit/testing,unstable 4:5.23.0-1 amd64 [upgradable from: 4:5.21.5-2]
kscreen/testing,unstable 4:5.23.0-1 amd64 [upgradable from: 4:5.21.5-2]
ksshaskpass/testing,unstable 4:5.23.0-1 amd64 [upgradable from: 4:5.21.5-2]
kwayland-integration/testing,unstable 5.23.0-1 amd64 [upgradable from:
5.21.5-2]
libkdecorations2-5v5/testing 4:5.23.0-2 amd64 [upgradable from: 4:5.21.5-2]
libkf5screen-bin/testing,unstable 4:5.23.0-1 amd64 [upgradable from:
4:5.21.5-2]
libkf5screen7/testing,unstable 4:5.23.0-1 amd64 [upgradable from:
4:5.21.5-2]
libpam-kwallet-common/testing,unstable 5.23.0-1 all [upgradable from:
5.21.5-2]
libpam-kwallet5/testing,unstable 5.23.0-1 amd64 [upgradable from: 5.21.5-2]
plymouth-theme-breeze/testing,unstable 5.23.0-1 amd64 [upgradable from:
5.21.5-2]

and apt upgrade would upgrade them giving a mix of 5.21 and 5.23

Re: KDE/Plasma/Wayland v5.23 and SDDM delay on reboot/restart

[David Palacio]

On Sat, Oct 16, 2021, at 2:40 AM, Sedat Dilek wrote:
> Hi,
>
> I switched to KDE/Plasma v5.23 from Debian/unstable - mostly as
> middle-mouse-paste is now supported.
>
> On reboot and restart I get a 90 seconds delay when SDDM service is shutdown.
>
> Debian ships SDDM version 0.19 and upcoming 0.20 shall have Wayland
> support (see [1]).
>
> Is there a workaround I do not know?
>
> I might change DefaultTimeoutStopSec:
>
> root# grep DefaultTimeout /etc/systemd/system.conf
> 44:#DefaultTimeoutStartSec=90s
> 45:#DefaultTimeoutStopSec=90s
> 46:#DefaultTimeoutAbortSec=
>
> Alternatively, use a different GUI login-manager which supports
> Wayland properly?
>
> Thanks in advance.
>
> Regards,
> - Sedat -
>
>
>
> [1] https://wiki.archlinux.org/title/SDDM

Hi,

Does uninstalling kdeconnect, if it is installed, remove the delay?

Regards,
David

Re: Bug#992760: ksystemtray: cannot be started, wrong version

[Erwan David]

De : Norbert Preining [mailto:norb...@preining.info]
Envoyé : lundi 23 août 2021 à 11:24 UTC+2
Pour : Erwan David , 992...@bugs.debian.org
Cc : Debian Kde 
Objet : Bug#992760: ksystemtray: cannot be started, wrong version


Hi Erwan,


kf.plasma.core: 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/applets/org.kde.plasma.systemtray.so"
 : this plugin is compiled against incompatible Plasma version 348928 This build is 
compatible with 5 .0.0 ( 327680 ) to 5.78.0 ( 347708 )
kf.plasma.core: Applet "org.kde.plasma.systemtray" could not be loaded.



ii  libkf5plasma5 5.78.0-3


The problem is that this packages (and several others) from the
frameworks are not updated.

I guess we have to introduce a breaks somewhere ... this incompatibility
is somehow surprising, because it is not documented in the CMakeList
files - at least as far I see...


So better wait for a newer version...


No, wait for all frameworks being updated ...

Best

Norbert


Thanks, everything is OK now. Now, I just have to close the bug I opened.

Re: Testing : do not upgrade to 5.21 (yet)

[Erwan David]

De : Lisandro Damián Nicanor Pérez Meyer [mailto:perezme...@gmail.com]


Hi!

On Mon, 23 Aug 2021 at 07:23, Luigi Toscano  wrote:


Erwan David ha scritto:

Le 23/08/2021 à 11:25, Luigi Toscano a écrit :
u have a mix of Frameworks packages from 5.78 and 5.83:


ii  libkf5plasma5 5.78.0-3
ii  libkf5plasmaquick55.78.0-3
ii  libkf5prison5 5.83.0-2

Make sure you fully get all Frameworks 5.83 (which should be upgraded as a
single block).



And what would be the best way to be sure ?
Given I have some libkf5* packages with another numbering scheme :
eg libkf5cddb5 : 4:20.12.0-1


Those are not the Frameworks product, they are shipped with a different cycle.



There are alos many packages in the framework, what would be the best tool to
be sure we upgrade the framework as a whole ?


There is surely some dependency that needs to be tighten. I have just
run into the same issue.



Upgrading this morning, it now works...

Re: Testing : do not upgrade to 5.21 (yet)

[Erwan David]

Le 23/08/2021 à 11:25, Luigi Toscano a écrit :
u have a mix of Frameworks packages from 5.78 and 5.83:


ii  libkf5plasma5 5.78.0-3
ii  libkf5plasmaquick55.78.0-3
ii  libkf5prison5 5.83.0-2

Make sure you fully get all Frameworks 5.83 (which should be upgraded as a
single block).



And what would be the best way to be sure ?
Given I have some libkf5* packages with another numbering scheme :
eg libkf5cddb5 : 4:20.12.0-1

There are alos many packages in the framework, what would be the best 
tool to be sure we upgrade the framework as a whole ?

Re: Bug#992760: ksystemtray: cannot be started, wrong version

[Erwan David]

De : Norbert Preining [mailto:norb...@preining.info]


Hi Erwan,


kf.plasma.core: 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/applets/org.kde.plasma.systemtray.so"
 : this plugin is compiled against incompatible Plasma version 348928 This build is 
compatible with 5 .0.0 ( 327680 ) to 5.78.0 ( 347708 )
kf.plasma.core: Applet "org.kde.plasma.systemtray" could not be loaded.



ii  libkf5plasma5 5.78.0-3


The problem is that this packages (and several others) from the
frameworks are not updated.

I guess we have to introduce a breaks somewhere ... this incompatibility
is somehow surprising, because it is not documented in the CMakeList
files - at least as far I see...


So better wait for a newer version...


No, wait for all frameworks being updated ...

Best

Norbert


I know it is a big work, but with ~ 400 package upgrades, it is 
difficult to check everything will be updated. And version naming does 
not help either (it would be a big work to change, I know).


I am on testing, so I am OK with minor inconveniences like this (by the 
way the plasmoid to get network, CPU or RAM load does not start either).

But I wanted to warn people of this (obviously transient) problem.

Re: Testing : do not upgrade to 5.21 (yet)

[Erwan David]

 Message d'origine 
De : Luigi Toscano [mailto:luigi.tosc...@tiscali.it]
Envoyé : lundi 23 août 2021 à 10:50 UTC+2
Pour : Erwan David , Debian Kde 


Objet : Testing : do not upgrade to 5.21 (yet)


Erwan David ha scritto:

After upgrade to 5.21 this morning (plasma-workspace 4:5.21.5-3), I get

kf.plasma.core:
"/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/applets/org.kde.plasma.systemtray.so"
: this plugin is compiled against incompatible Plasma version 348928 This
build is compatible with 5 .0.0 ( 327680 ) to 5.78.0 ( 347708 )
kf.plasma.core: Applet "org.kde.plasma.systemtray" could not be loaded.

So better wait for a newer version...



plasma-workspace alone is not Plasma. You need all the packages which makes up
Plasma, those are the upstream sources
https://download.kde.org/stable/plasma/5.21.5/

Please also consider that Frameworks is only partially migrated to testing,
which means other stuff may not work for different reasons than not having all
Plasma bits.



I know; There were more than 400 packages, however error message is
kf.plasma.core: 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/applets/org.kde.plasma.systemtray.so" 
: this plugin is compiled against incompatible Plasma version 348928 
This build is compatible with 5 .0.0 ( 327680 ) to 5.78.0 ( 347708 )


and according to apt-file  org.kde.plasma.systemtray.so comes in 
plasma-workspace package.


See bug #992760

Testing : do not upgrade to 5.21 (yet)

[Erwan David]

After upgrade to 5.21 this morning (plasma-workspace 4:5.21.5-3), I get

kf.plasma.core: 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/applets/org.kde.plasma.systemtray.so" 
: this plugin is compiled against incompatible Plasma version 348928 
This build is compatible with 5 .0.0 ( 327680 ) to 5.78.0 ( 347708 )

kf.plasma.core: Applet "org.kde.plasma.systemtray" could not be loaded.

So better wait for a newer version...

Re: Locale Issue in bullseye

[Erwan David]

Le 03/01/2021 à 19:41, Rainer Dorsch a écrit :

Hi,

I installed a new bullseye system. I added some accounts and changed the
locale (regional settings) to German. Worked well for

- System settings
- Application starter menu
- Non-KDE Applications (e.g. firefox and libreoffice)

Did not work for
- control panel
- all KDE Applications, e.g.
-- kate
-- kmail
-- konsole
-- ...

Is this a bug or did I miss something?

Any advice or hint is welcome.

Thanks
Rainer



In KDE System's settings are your regional settings at "No Change" ? If 
not, KDE will setup environment variables according to those settings 
and they will be used for KDE applications.

Re: Taskbar and Plasma 5.20.4

[Erwan David]

Le 29/12/2020 à 13:49, Erwan David a écrit :
> Le 29/12/2020 à 13:39, MERLIN Philippe a écrit :
>> Hello,
>> My system is an AMD64 Sid, since the Plasma migration to 5.20.4 I have 
>> problems with my taskbar, for example if I click on the Firefox icon I no 
>> longer see the window showing all the sessions Firefox open, it must be 
>> recognized that I often have more than 10 sessions open simultaneously, now 
>> to 
>> access a particular session I have to click on the Firefox icon and I see 
>> all 
>> the sessions scrolling. Another oddity some sessions are no longer visible 
>> only the title appears, impossible to see these sessions. This problem does 
>> not only concern Firefox, Dolphin, Konsole ...
>> I would like to go back to normal operation, is there a way out?
>> Cheers.
>> Philippe Merlin
>>
>>
>>
> Same here : clicking on an icon opens the next corresponding window.
>
>
Ok found it : you get former behaviour by right clicking on the taskbar,
Configure Task Manager, Behavior, ans set 'clicking grouped task' to
"shows textual list"

Re: Taskbar and Plasma 5.20.4

[Erwan David]

Le 29/12/2020 à 13:39, MERLIN Philippe a écrit :
> Hello,
> My system is an AMD64 Sid, since the Plasma migration to 5.20.4 I have 
> problems with my taskbar, for example if I click on the Firefox icon I no 
> longer see the window showing all the sessions Firefox open, it must be 
> recognized that I often have more than 10 sessions open simultaneously, now 
> to 
> access a particular session I have to click on the Firefox icon and I see all 
> the sessions scrolling. Another oddity some sessions are no longer visible 
> only the title appears, impossible to see these sessions. This problem does 
> not only concern Firefox, Dolphin, Konsole ...
> I would like to go back to normal operation, is there a way out?
> Cheers.
> Philippe Merlin
>
>
>
Same here : clicking on an icon opens the next corresponding window.

Re: No more file opening dialogs, which package should I open the bug ?

[Erwan David]

Le 25/12/2020 à 19:55, Erwan DAVID a écrit :
>
> Le 24 décembre 2020 19:37:29 Brad Rogers  a écrit :
>
>> On Thu, 24 Dec 2020 18:30:12 +0100
>> Erwan David  wrote:
>>
>> Hello Erwan,
>>
>>> I got some kde upgrades, since then, applications opening a file opening
>>> dialog completely block (tried with vlc, dragon player or okular). Which
>>
>> All fine here.
>>
>> Did you log out and back in again?  Sometimes this is required to get
>> things talking to each other properly.
>>
>> -- 
>>  Regards  _
>>          / )           "The blindingly obvious is
>>         / _)rad        never immediately apparent"
>> My body's an oasis to drink from as you please
>> Mirage - Siouxsie & The Banshees
> Yes, I even restarted
>
> -- 
> Erwan David


Ok, I found the bug : I have autmount units, and I am at a location
where the mounting is not possible. That's what blocks the dialog. I do
not see why not being able to do the automount should block this, thus
I'd still like to fill a bug, but more precise.

Maybe it is a QT package, and not a KDE one ?

Re: No more file opening dialogs, which package should I open the bug ?

[Erwan DAVID]

Le 24 décembre 2020 19:37:29 Brad Rogers  a écrit :


On Thu, 24 Dec 2020 18:30:12 +0100
Erwan David  wrote:

Hello Erwan,


I got some kde upgrades, since then, applications opening a file opening
dialog completely block (tried with vlc, dragon player or okular). Which


All fine here.

Did you log out and back in again?  Sometimes this is required to get
things talking to each other properly.

--
Regards  _
/ )   "The blindingly obvious is
   / _)radnever immediately apparent"
My body's an oasis to drink from as you please
Mirage - Siouxsie & The Banshees


Yes, I even restarted

--
Erwan David

Re: No more file opening dialogs, which package should I open the bug ?

[Erwan David]

Le 24/12/2020 à 18:30, Erwan David a écrit :
> I got some kde upgrades, since then, applications opening a file opening
> dialog completely block (tried with vlc, dragon player or okular). Which
> package should I open a bu against ?
>
>
>
Precision : I am on testing, and got some upgrades today and yesterday.

No more file opening dialogs, which package should I open the bug ?

[Erwan David]

I got some kde upgrades, since then, applications opening a file opening
dialog completely block (tried with vlc, dragon player or okular). Which
package should I open a bu against ?

KDE PIM version for testing

[David Jarvie]

Is it the intention to update the KDE PIM version in testing to at least 
20.08.3 before Bullseye is released as the stable version? The reason I ask is 
that there is a very serious bug in the current version of KAlarm in testing, 
which is fixed in 20.08.3 (see https://bugs.kde.org/show_bug.cgi?id=427722). If 
it's going to be updated, there is no need for me to raise a bug report.

Thanks,
-- 
David Jarvie.
KDE developer, KAlarm author.

Re: Upgrade partially some packages (Plasma 5.19. 5 - 3) on testing broke plasma.

[Erwan David]

Le 09/11/2020 à 11:06, Erwan David a écrit :
> Le 09/11/2020 à 10:04, Andy G Wood a écrit :
>> I had the same problem this morning with testing.
>> My fix was to simply to back out the new libkdecorations2-5v5 :
>>
>> debsnap -d . --binary -a amd64 libkdecorations2-5v5 4:5.17.5-2
>> sudo dpkg -i libkdecorations2-5v5_5.17.5-2_amd64.deb
>> dpkg --get-selections \* | grep -P '^libkdecorations2-5v5' \
>>    | sed -e 's/install/hold/' > libkdecorations2-5v5.hold
>> sudo dpkg --set-selections < libkdecorations2-5v5.hold
>>
>> That was good enough to get things working for today!
>> Andy.
>
> Could you please elaborate :
> I install debsnap and get "fatal error at line 270
> Unable to retrieve information for libkdecorations2-5v5 from
> https://snapshot.debian.org/mr/package/libkdecorations2-5v5/
>
>
Sorry, I missed the --binary while copying the command (not easy without
a graphical env).

Thanks for the tip.

Re: Upgrade partially some packages (Plasma 5.19. 5 - 3) on testing broke plasma.

[Erwan David]

Le 09/11/2020 à 10:04, Andy G Wood a écrit :

I had the same problem this morning with testing.
My fix was to simply to back out the new libkdecorations2-5v5 :

debsnap -d . --binary -a amd64 libkdecorations2-5v5 4:5.17.5-2
sudo dpkg -i libkdecorations2-5v5_5.17.5-2_amd64.deb
dpkg --get-selections \* | grep -P '^libkdecorations2-5v5' \
   | sed -e 's/install/hold/' > libkdecorations2-5v5.hold
sudo dpkg --set-selections < libkdecorations2-5v5.hold

That was good enough to get things working for today!
Andy.


Could you please elaborate :
I install debsnap and get "fatal error at line 270
Unable to retrieve information for libkdecorations2-5v5 from 
https://snapshot.debian.org/mr/package/libkdecorations2-5v5/

Re: Kate 19.08

[David Goodenough]

On Thursday, 26 September 2019 19:29:32 BST Martin Steigerwald wrote:

> Hi David.

>

> Please do not send HTML mails to this list.

>

> David Goodenough - 26.09.19, 19:30:51 CEST:

> > On Thursday, 26 September 2019 08:26:13 BST Martin Steigerwald wrote:

> […]

>

> > > Pino uploaded Kate 19.08. Pino is working on updating application

> > > packages since quite a while. Also like KMyMoney and others.

> > > Looking forward to the enhancements from kate 18.08 => 19.08.

> >

> > Any chance of adding LSP support by building with:-

> >

> > -DENABLE_LSPCLIENT=ON

> >

> > Apparently it is not yet enabled by default.

>

> Good idea.

>

> Please file a bug report with "reportbug kate"

>

> Thanks,

Sorry about the HTML, KMail forgot the setting for this folder.



Bug submitted.



David

Re: Kate 19.08

[David Goodenough]

On Thursday, 26 September 2019 08:26:13 BST Martin Steigerwald wrote:

> Hi!

>

> Pino uploaded Kate 19.08. Pino is working on updating application

> packages since quite a while. Also like KMyMoney and others.

>

> Looking forward to the enhancements from kate 18.08 => 19.08.

>

> Thanks,

Any chance of adding LSP support by building with:-



-DENABLE_LSPCLIENT=ON



Apparently it is not yet enabled by default.



Thank you



David

Change of behaviour for Konsole in Bullseye

[Erwan David]

Hi,

I use bullseye, and I found that konsole has changed behaviour regarding
Views and tabd.

The old behaviour when you asked for a plit view was to have a second
frame with the tabs of the window in each frame. Now, when I split the
view, current tab is kep on left, other tabs are hidden, a new terminal
is started in right frame.

Is there a way to get back the old behaviour ?


Thanks.

Re: Back to Amarok

[Erwan David]

Le 21/08/2019 à 13:34, Martin Steigerwald a écrit :
> Hi!
>
> I used qmmp in the meanwhile, but since in Debian Sid it is possible to 
> install Amarok again (since 2.9.0-2 of package version), I am back to 
> Amarok.
>
> What was I missing in Qmmp:
>
> - Play/Pause is one button. Qmmp with libqsui.so simple gui plugin has 
> three buttons Start, Stop, Pause which I find confusing.
>
> - I found no way to have a collection or file browser beneath the play 
> list so I can easily drag and drop files from there to the playlist.
>
> And yes, I know, unless there will be a KF5/Qt5 port of Amarok in time 
> Amarok will go away as soon at Qt 4 and the remainder of KDE SC 4.14 
> libraries is removed.
>
> Thanks,

I got notified that some bug I had opened against amarok was closed due
to amarok being retired. I had already switched to cantata since buster
install...

Re: krunner and systemtray broken in testing

[Erwan David]

On Mon, Aug 27, 2018 at 09:25:21PM CEST, Erwan David  said:
> Since latest upgrade, krunner does not find anything outside the latest
> documents (and cannot execute command lines), sametime system tray
> cannot start anymore (and this on 2 different machines)
> 
> Do someone have a hint on what happens ?
> 
> (or is there a workaround) ?

Thanks to verybody who answered, I now have a working desktop.

-- 
Erwan

Re: krunner and systemtray broken in testing

[Erwan David]

Le 08/27/18 à 22:46, Luigi Toscano a écrit :
> Erwan David ha scritto:
>> Le 08/27/18 à 21:51, Luigi Toscano a écrit :
>>> yaros ha scritto:
>>>> Dnia poniedziałek, 27 sierpnia 2018 21:25:21 CEST Erwan David pisze:
>>>>> Since latest upgrade, krunner does not find anything outside the
>>>>> latest
>>>>> documents (and cannot execute command lines), sametime system tray
>>>>> cannot start anymore (and this on 2 different machines)
>>>>>
>>>>> Do someone have a hint on what happens ?
>>>>>
>>>>> (or is there a workaround) ?
>>>>>
>>>>>
>>>>>
>>>> Look at the topic "[Debian/buster] Problems after Upgrade 4:5.13.1-1
>>>> to 4:5.13.4-1"
>>>> And https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907262
>>>>
>>>>
>>>
>>> Namely this email:
>>> https://lists.debian.org/debian-kde/2018/08/msg00030.html
>>>
>> Thanks. So what would be the safest way to get only the needed packages
>> from unstable and not keep getting them from unstable in the future ?
>
> Discussed in the same thread:
>
> https://lists.debian.org/debian-kde/2018/08/msg00032.html
>
My past tries whith this kind of commands lead to always using unstable
after such an install. I do not want to run unstable if avoidable.

Re: krunner and systemtray broken in testing

[Erwan David]

Le 08/27/18 à 22:14, Kai Michael Hamich a écrit :
> Just build the package 'plasma-workspace' via deb-src and install only this 
> package afterwards. This will fix the problem!
>
> Am Montag, 27. August 2018, 22:05:12 CEST schrieb Erwan David:
>> Le 08/27/18 à 21:51, Luigi Toscano a écrit :
>>> yaros ha scritto:
>>>> Dnia poniedziałek, 27 sierpnia 2018 21:25:21 CEST Erwan David pisze:
>>>>> Since latest upgrade, krunner does not find anything outside the latest
>>>>> documents (and cannot execute command lines), sametime system tray
>>>>> cannot start anymore (and this on 2 different machines)
>>>>>
>>>>> Do someone have a hint on what happens ?
>>>>>
>>>>> (or is there a workaround) ?
>>>> Look at the topic "[Debian/buster] Problems after Upgrade 4:5.13.1-1
>>>> to 4:5.13.4-1"
>>>> And https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907262
>>> Namely this email:
>>> https://lists.debian.org/debian-kde/2018/08/msg00030.html
>> Thanks. So what would be the safest way to get only the needed packages
>> from unstable and not keep getting them from unstable in the future ?
>>
>> My tests with soucre policies in the past lead to catastrophs because
>> once a package was installed from unstable it was marked in some way and
>> always came from unstable after that.
>
>
>
>
Sorry I wouldn't know how to do this, is there somewhere a tutorial ?

Re: krunner and systemtray broken in testing

[Erwan David]

Le 08/27/18 à 22:05, Erwan David a écrit :
> Le 08/27/18 à 21:51, Luigi Toscano a écrit :
>> yaros ha scritto:
>>> Dnia poniedziałek, 27 sierpnia 2018 21:25:21 CEST Erwan David pisze:
>>>> Since latest upgrade, krunner does not find anything outside the latest
>>>> documents (and cannot execute command lines), sametime system tray
>>>> cannot start anymore (and this on 2 different machines)
>>>>
>>>> Do someone have a hint on what happens ?
>>>>
>>>> (or is there a workaround) ?
>>>>
>>>>
>>>>
>>> Look at the topic "[Debian/buster] Problems after Upgrade 4:5.13.1-1
>>> to 4:5.13.4-1"
>>> And https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907262
>>>
>>>
>> Namely this email:
>> https://lists.debian.org/debian-kde/2018/08/msg00030.html
>>
> Thanks. So what would be the safest way to get only the needed packages
> from unstable and not keep getting them from unstable in the future ?
>
> My tests with soucre policies in the past lead to catastrophs because
> once a package was installed from unstable it was marked in some way and
> always came from unstable after that.
>
>
ANd another question : how to know the list of packages to upgrade ?
There are many of them for kde, with several naming schemes (plasma*,
kde*, kf* at least).

Re: krunner and systemtray broken in testing

[Erwan David]

Le 08/27/18 à 21:51, Luigi Toscano a écrit :
> yaros ha scritto:
>> Dnia poniedziałek, 27 sierpnia 2018 21:25:21 CEST Erwan David pisze:
>>> Since latest upgrade, krunner does not find anything outside the latest
>>> documents (and cannot execute command lines), sametime system tray
>>> cannot start anymore (and this on 2 different machines)
>>>
>>> Do someone have a hint on what happens ?
>>>
>>> (or is there a workaround) ?
>>>
>>>
>>>
>> Look at the topic "[Debian/buster] Problems after Upgrade 4:5.13.1-1
>> to 4:5.13.4-1"
>> And https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907262
>>
>>
>
> Namely this email:
> https://lists.debian.org/debian-kde/2018/08/msg00030.html
>
Thanks. So what would be the safest way to get only the needed packages
from unstable and not keep getting them from unstable in the future ?

My tests with soucre policies in the past lead to catastrophs because
once a package was installed from unstable it was marked in some way and
always came from unstable after that.

krunner and systemtray broken in testing

[Erwan David]

Since latest upgrade, krunner does not find anything outside the latest
documents (and cannot execute command lines), sametime system tray
cannot start anymore (and this on 2 different machines)

Do someone have a hint on what happens ?

(or is there a workaround) ?

Re: Why won't KDE start with overcommit disabled?

[Erwan David]

Le 06/06/18 à 04:27, Borden Rhodes a écrit :
> I have a problem with web browsers going rogue and locking up my
> computer such that I have to hard restart. I want to set
> vm.overcommit_memory=2 to try to invoke the OOM killer before a
> browser locks up my computer. When I do, though, SDDM will start
> normally, I'll log in but it'll freeze up whilst plasmashell is
> loading. I have 4GB of RAM and 4GB of swap. Is it not possible to set
> vm.overcommit _memory on a KDE system?
>
>
When I look at my processes, I see that baloo allocates (or is it an
mmap ?) 256 GB of memory. That could explain. But Why is baloo
allocating so much ?

Re: KDEPIM 17.12: pane that show message structure missing?

[David Goodenough]

On Thursday, 12 April 2018 08:33:43 BST Martin Steigerwald wrote:
> Hello.
> 
> With KDEPIM prior 17.12 I always had a pane that shows the message
> structure where I could select which part of the message to view in the
> message content display area. So with messages that are both available
> as text and HTML I could select which one to view.
> 
> This is gone since KDEPIM 17.12 and I found no way to enable it again. I
> remember there was an option but I digged through all menus and
> configuration options three times without finding it.
> 
> Any idea?
> 
> Thanks,
Try Folder->Message Default Format

David

Re: Some KDE applications still outdated

[Erwan David]

Le 11/28/17 à 12:45, Martin Steigerwald a écrit :
> Hello.
>
> There are still some KDE Applications not at 17.08.
>
> For example kdenetwork including Kopete which is still at a version that uses 
> KDE SC 4.14.
>
> I bet you are aware of it… if not, then after reading this you are.
>
> Yes, I am not in the position to request anything without offering to help. 
> It 
> just would be nice to have kdenetwork at 17.08 as well.
>
> kdegraphics and kdemultimedia metapackages are not yet up to date, but it 
> appears some of their more popular dependencies are.
>
> Thanks,

Hi,

I see references to those versions of KDE applications. Is there a
specific repository to get something more advanced than the partial KDE
of stable ?


Thank you.

Stable : how can I configure akonadi/Pim ?

[Erwan David]

I'd like to subscribe to a caldav calendar to get it in the digital
Clack/Calendar widget.

However I cannot find any way to configure akonadi, be it the server or
the accounts.

Where is the configuration ?


Thank you.

Re: Kmail often stuck at "Retrieving folder contents..."

[David Goodenough]

On Wednesday, 1 March 2017 12:53:20 GMT David Baron wrote:
> On יום רביעי, 1 במרץ 2017 11:17:56 IST Martin Steigerwald wrote:
> > Hello Tim.
> > 
> > Am Mittwoch, 1. März 2017, 10:56:45 CET schrieb Tim Ruehsen:
> > > Please wait...
> > > 
> > > No matter how long I wait, KMail is stuck.
> > > I have to restart KMail.
> > > 
> > > My impression: It happens regular when changing folders too fast.
> > > 
> > > Of course I tried akonadictl (fsck + vacuum + restart) with no success.
> > > 
> > > Any idea where to look at or what to do ?
> > 
> > This topic has been discussed just recently on kdepim-users mailing list.
> > It appears to be a known issue.
> > 
> > Please review
> > 
> > "Retrieving Folders..." hang and a possible solution
> > 
> > thread there.
> > 
> > https://mail.kde.org/mailman/listinfo/kdepim-users
> > 
> > Thanks,
> 
> Select the option to download for off-line use. Once the stuff is there,
> problem will not recur.
I get it all the time on local folders, and all my IMAP connections are 
already set to disconnected mode (i.e. download for off-line).

Usually stopping kmail and akonadi and then starting kmail again
fixes it.
> 
> I was under the impression there were problems on GMail servers but
> apparently more widespread.
I have never had problems with any of the actual servers, only the local
folders.

I had read somewhere on one of the KDE forums that this was supposed
to be fixed in 16.08, but I do not remember details.

David

Re: Kmail often stuck at "Retrieving folder contents..."

[David Baron]

On יום רביעי, 1 במרץ 2017 11:17:56 IST Martin Steigerwald wrote:
> Hello Tim.
> 
> Am Mittwoch, 1. März 2017, 10:56:45 CET schrieb Tim Ruehsen:
> > Please wait...
> > 
> > No matter how long I wait, KMail is stuck.
> > I have to restart KMail.
> > 
> > My impression: It happens regular when changing folders too fast.
> > 
> > Of course I tried akonadictl (fsck + vacuum + restart) with no success.
> > 
> > Any idea where to look at or what to do ?
> 
> This topic has been discussed just recently on kdepim-users mailing list. It
> appears to be a known issue.
> 
> Please review
> 
> "Retrieving Folders..." hang and a possible solution
> 
> thread there.
> 
> https://mail.kde.org/mailman/listinfo/kdepim-users
> 
> Thanks,

Select the option to download for off-line use. Once the stuff is there, 
problem will not recur.

I was under the impression there were problems on GMail servers but apparently 
more widespread.

Re: linux-image-4.9.0-1-amd64 + nvidia-legacy-304xx-driver + xserver-xorg-video-nouveau

[David Baron]

On יום שלישי, 24 בינואר 2017 14:35:18 IST Jimmy Johnson wrote:
> On 01/23/2017 11:54 PM, David Baron wrote:
> > On יום שני, 23 בינואר 2017 21:14:58 IST Jimmy Johnson wrote:
> >> On 01/14/2017 02:26 PM, Jimmy Johnson wrote:
> >> 
> >> I'm happy to report linux-image-4.9.0-1-amd64 +
> >> nvidia-legacy-304xx-driver are currently working swell together.
> > 
> > I just updated, rebooted. See no change. Window decorations still missing,
> > both in openGL and Xrender.
> 
> Yes, Plasma defaults to OpenGL 2.0 and it's not good that it's not
> working, you have to use XRender, but compositing is working.  Once you
> switch to XRender you need to logout/login to see the change.

I am on Xrender. I do not enable compositor on startup as I had hangups when 
doing that. I still see no change.

Re: linux-image-4.9.0-1-amd64 + nvidia-legacy-304xx-driver + xserver-xorg-video-nouveau

[David Baron]

On יום שני, 23 בינואר 2017 21:14:58 IST Jimmy Johnson wrote:
> On 01/14/2017 02:26 PM, Jimmy Johnson wrote:
> >  And it still works.
> > I updated Sid/testing a couple days ago and retested current drivers,
> > "nouveau" is working with sddm okay but froze with plasma(colorful
> > lighting bolts).  Current nvidia-legacy-304xx is working with XRender
> > and compositing enabled and I'm good with that, tested on Stretch too,
> > now I can do clean upgrades and I'm happy. Thank you Debian!
> > 
> > linux-image-4.9.0-1-amd64 is behaving like image-4.8 used to behave
> > nouveau froze with plasma(colorful lighting bolts).  Debian's
> > nvidia-legacy-304xx-driver is freezing with plasma start.
> > 
> > On first boot plasma loaded the vga driver giving me the wrong screen
> > size and did not load the installed nvidia driver at all. Booting
> > linux-image-4.9.0-1-amd64 and reinstalling nvidia-legacy-304xx-driver
> > crashed plasma and so did nouveau. I'm back to using
> > nvidia-legacy-304xx-driver and linux-image-4.8.0-2-amd64 with XRender
> > and compositing enabled.
> 
> I'm happy to report linux-image-4.9.0-1-amd64 +
> nvidia-legacy-304xx-driver are currently working swell together.
> 
> Thank you Debian!

I just updated, rebooted. See no change. Window decorations still missing, 
both in openGL and Xrender.

Re: linux-image-4.9.0-1-amd64 + nvidia-legacy-304xx-driver + xserver-xorg-video-nouveau

[David Baron]

On יום שבת, 14 בינואר 2017 14:26:53 IST Jimmy Johnson wrote:
>  And it still works.
> I updated Sid/testing a couple days ago and retested current drivers,
> "nouveau" is working with sddm okay but froze with plasma(colorful
> lighting bolts).  Current nvidia-legacy-304xx is working with XRender
> and compositing enabled and I'm good with that, tested on Stretch too,
> now I can do clean upgrades and I'm happy. Thank you Debian!
> 
> linux-image-4.9.0-1-amd64 is behaving like image-4.8 used to behave
> nouveau froze with plasma(colorful lighting bolts).  Debian's
> nvidia-legacy-304xx-driver is freezing with plasma start.
> 
> On first boot plasma loaded the vga driver giving me the wrong screen
> size and did not load the installed nvidia driver at all. Booting
> linux-image-4.9.0-1-amd64 and reinstalling nvidia-legacy-304xx-driver
> crashed plasma and so did nouveau. I'm back to using
> nvidia-legacy-304xx-driver and linux-image-4.8.0-2-amd64 with XRender
> and compositing enabled.

I just tried the 4.9.0-1-amd64. Worked for me the same as the 4.8. No better 
with XRender.

Re: Compositing Problem

[David Baron]

On יום שבת, 7 בינואר 2017 4:36:59 IST Jimmy Johnson wrote:
> On 10/19/2016 11:33 PM, Jimmy Johnson wrote:
> > On 10/12/2016 12:10 PM, David Baron wrote:
> >> Running must recent kwin, etc., with Sid nvidia-legacy-304xx driver.
> >> 
> >> Window decorations slow or do not show on non-KDE windows. If they do not
> >> show, one can pretend they are there and do everything.
> >> 
> >> Effects all compositing options.
> >> 
> >> Where to file bug?
> >> Quick fix?
> > 
> > Quick fix, force install all your 'nvidia' and 'glx' installed packages
> > back to 'Jessie-backports' and then 'lock-them' works, maybe 20-24
> > packages that you will be locking, varies a little with my installs,
> > some I had not upgraded and I only had to lock the packages.  I used
> > synaptic while in xfce4 and all your kde apps work from xfce4 too as a
> > side note.  Note no problem with upgrades and those files being locked,
> > at this time anyways. hehe
> > 
> > There's a lot noise out there about fix's, I found nothing works for me.
> > 
> >  I came up with this fix and it works.  While gtk works with the
> > 
> > upgrade, plasma don't, it's a problem with plasma, you can't blame
> > nvidia and say they are not doing their part, this is a problem debian
> > plasma, I'm sure they are working on it. Seems to affect only
> > 'legacy-304' and could be a simple code error.
> > 
> > With the Debian-nvidia driver: Plasma is unable to start as it could not
> > correctly use OpenGL2.  Note dialog is working, sound is working, no
> > plasma.
> > 
> > With the Debian-free driver, computer freeze with colorful squiggly
> > lines and I have to push the power button and repair the file system.
> > 
> > David, do you have a better fix than down-grading the packages?  And I
> > may not need to down grade as many packages as I do, but it works.
> 
> I updated Sid/testing a couple days ago and retested current drivers,
> "nouveau" is working with sddm okay but froze with plasma(colorful
> lighting bolts).  Current nvidia-legacy-304xx is working with XRender
> and compositing enabled and I'm good with that, tested on Stretch too,
> now I can do clean upgrades and I'm happy. Thank you Debian!

Mine does NOT work with xrender

Re: Searching in dolphin

[David McPearson]

On 2017-01-06 18:31, Rainer Dorsch wrote:


On Friday 06 January 2017 08:08:14 David McPearson wrote:






On 2017-01-05 22:15, Brad Rogers wrote:



On Thu, 05 Jan 2017 21:02:00 +0100



solitone  wrote:







Hello solitone,







What package is needed in order to use the search functionality in



Dolphin? At the moment I get an "invalid protocol" error.







Nothing:






Run System Settings, then go to Workspace -> Search -> File Search 
and



turn *off* Enable File Search. That is, untick/uncheck it. Now apply,



and then the Find file function will work in Dolphin.







Hi Guys,







Same error here on Debian Jessie/KDE 4.14.2/Dolphin 4.14.1. When I run



System Settings I do not see an option "Search option"







According to the System Setting Manual there should be a "Desktop


Search" module under System Settings > Workspace Appearance and 
Behavior



- but it is not there. I assume this is what is meant by "File Search"



above. Am I correct?







Any hints/instructions about how to get Dolphin's Find to work (given



the above)?







Please note I turned file indexing off when I first installed Jessie.


I can at least confirm that desktop search works for me in Jessie, my 
dataset is about 60 GB in about half a million files.


There is "Desktop Search" and "Desktop Search Advanced" in "System 
Settings". In "Desktop Search Advanced" I specified which paths to 
exclude and which to include in the desktop search. I have enabled 
"Desktop search" and "File indexer"


##
##
I found (at least part of) the problem here:
https://www.ryananddebi.com/2015/07/13/linux-getting-find-working-in-dolphin-on-kde-linux-mint-and-kubuntu/
You have to have baloo4 installed for these items to appear in System 
Settings. Checking my software I have most of the baloo libraries 
installed but not the baloo4 base application.

##
##



There is one glitch I noticed: dolphin searches from the current 
working directory. If the current working directory is a symbolic link, 
the search does not find anything. It seems baloo stores the physical 
paths and is not able to map symbolic paths to physical paths.


##
##
...ouch...!
The whole point (for me, anyway) is to quickly search from the current 
working directory. If I want anything else I use kfind.

##
##



I hope that helps...

Rainer

--

Rainer Dorsch

http://bokomoko.de/


Also, from the comments to the post I linked above, it seems that (from 
Aug/Sept 2016 anyway) that you can have searching from Dolphin or 
searching from Krunner - but not both.


At the moment I'll put up with it. Looking around on the web it seems 
that the guys over at KDE have been struggling with semantic search for 
a while. It seems it is very difficult to get this right. And I prefer 
to take the (perceived) "performance hit" when I (infrequently) search, 
rather than all the time.


The biggest problem for me is that I (try to) use the Dolphin find 
functionality so rarely I forget it's broken. So I click the button, 
enter the search term(s) then swear and curse etc.


Thanks very much for taking the time to respond. With any luck the link 
above might help someone.


Cheers,
Dave.

Re: Searching in dolphin

[David McPearson]

On 2017-01-05 22:15, Brad Rogers wrote:

On Thu, 05 Jan 2017 21:02:00 +0100
solitone  wrote:

Hello solitone,


What package is needed in order to use the search functionality in
Dolphin? At the moment I get an "invalid protocol" error.


Nothing:

Run System Settings, then go to Workspace -> Search -> File Search and
turn *off* Enable File Search.  That is, untick/uncheck it.  Now apply,
and then the Find file function will work in Dolphin.


Hi Guys,

Same error here on Debian Jessie/KDE 4.14.2/Dolphin 4.14.1. When I run 
System Settings I do not see an option "Search option"


According to the System Setting Manual there should be a "Desktop 
Search" module under System Settings > Workspace Appearance and Behavior 
- but it is not there. I assume this is what is meant by "File Search" 
above. Am I correct?


Any hints/instructions about how to get Dolphin's Find to work (given 
the above)?


Please note I turned file indexing off when I first installed Jessie.

Many thanks,
Dave.

Kontact Calendars and Mail folders disappearing - exim update issue??

[David McPearson]

Hi Guys,

I'm having a bit of an issue with Kontact at present. The timing 
suggests it may be connected with the latest exim update.


First thing I noticed was the To-Dos and Calendar were not displaying. I 
could get the Calendar to display by chenging the folder settings (ie. 
path to calendar files), then changing them back. This was not 
persistent and had to be repeatded when Kontact was restarted.


I did the same thing in the Akonadai settings, logged out and logged 
back in (force Akonadia apps to restart) and the calender info is 
present. Pls note I'm pretty sure I put everything in Akonadai back the 
way it was - but am not completely certain.


After the logout/in Kontact/Kmail reported that the folders I had 
deleted were associated with my mail account (I do not remember the 
exact wording - apologies for that).

Pls note I have not deleted any files or directories,

E-mail messages still appear to be in ~/.local/share/local-mail.
All the settings I've found to date (Kontact > KMail settings dialogs 
and Akonadai dialogs from System Settings) point to  
~/.local/share/local-mail


A new directory  ~/.local/share/.local-mail.didrectory has appeared with 
a Date stamp consistent with the start of this issue. It has the same 
subdirectory structure as  ~/.local/share/local-mail but all the 
directories are empty.


My current working assumption is an issue with the recent exim update. 
Fundamentally I'm asking for help to confirm/deny/troubleshoot that. If 
it's more likely that this is a KDE issue I'll post over there. (Did a 
quick search, found nothing but my search skills suck)


Also - is anyone else seeing this? If not it's probably my system (read 
on...)


Some not so recent history which may be relevant:
https://lists.debian.org/debian-kde/2016/11/msg00036.html
Bottom line of that is I created /var/lib and deleted it when the fix to 
the mysql update was released. This broke apr so I put /var/lib back and 
am still getting some fallout from that error. Not trying to fix this 
one at present, but mention it in case it's relevant.


Sorry for the length, hope it's clear.

Thanks for reading this far,
DMcP.

Re: KDE Frameworks 5.28.0

[David Baron]

On יום ראשון, 20 בנובמבר 2016 9:30:10 IST Luc Castermans wrote:
> Hi,
> 
> Just to let you know ´ aptitude -t sid safe-upgrade´  resulted in KDE
> Frameworks 5.28.0
> 
> and other stuf.  All works nicely. Thanks !!

"Safe-upgrade?" First time I have heard of this. Next time, try it this way!

Latest mysql upgrade (5.5.53-0+deb8u1) causes Akonadi to fail to start

[David McPearson]

Hi All,

This is not a cry for help - more of a heads up and getting the issue 
and a solution documented here.
(I did a quick search of the list and found nothing - apologies if I'm 
duplicating earlier posts)


Short version:
sudo mkdir /var/lib/mysql-files

See https://forum.kde.org/viewtopic.php?f=215&t=135957#p366374

= = = = =

Long version:

After the recent mysql upgrade to 5.5.53-0+deb8u1 Kontact failed to 
display mails, tasks etc. and whinged about akonadi not starting. Poking 
around my system I found a clue in 
~/.local/share/akonadi/akonadiserver.error


stderr: "/usr/sbin/mysqld: Error on realpath() on '/var/lib/mysql-files' 
(Error 2)


Checking /var revealed that /var/lib did not exist.

However, the obvious solution was too obvious for me...
I did some trawling on the net, found various and recent reports of the 
same issue on various distros. Tried various solutions that worked for 
others, but proved ineffective and unnecessary for me, including mods to 
~/.local/share/akonadi/mysql.conf.


Finally at the above URL I found what was staring me in the face -viola, 
'sall good.


From my perspective it would be nice if the missing dir was created as 
part of the update (I'm a doze drone - I expect everything to be done 
for me..) Feedback on whether that is possible and/or generally 
desirable will be welcomed. Who knows, I might learn something.


Cheers.

Re: Warning: Please delay dist-upgrade to Debian Sid (qtdeclarative, sddm, Plasma) (fix coming soon)

[David Baron]

On יום שני, 7 בנובמבר 2016 10:33:37 IST MERLIN Philippe wrote:
> Le lundi 7 novembre 2016, 08:02:47 CET Valerio Passini a écrit :
> > On domenica 6 novembre 2016 19:23:22 CET Ferdinand Thommes wrote:
> > > ---
> > > Moin,
> > > 
> > > 
> > > 
> > > 
> > > greetz
> > > Ferdinand
> > > 
> > > Am 06.11.2016 18:42 schrieb Martin Steigerwald:
> > > > Am Sonntag, 6. November 2016, 17:43:58 CET schrieben Sie:
> > > >> On יום ראשון, 6 בנובמבר 2016 15:56:20 IST Martin Steigerwald wrote:
> > > >> > Am Sonntag, 6. November 2016, 11:14:04 CET schrieb Martin
> 
> Steigerwald:
> > > >> > > Am Sonntag, 6. November 2016, 00:59:07 CET schrieb Diederik de
> 
> Haas:
> > > >> > > > On zaterdag 5 november 2016 20:25:32 CET Andrey Rahmatullin
> 
> wrote:
> > > >> > > > > > If so, that is/was your problem and you'll likely have
> > > >> > > > > > various
> > > >> > > > > > qt5
> > > >> > > > > > package
> > > >> > > > > > at  version 5.7.1~20161021+dfsg-N.
> > > >> > > > > > Downgrade those packages to their version in testing and
> > > >> > > > > > there's a
> > > >> > > > > > reasonable  chance things start working again. See also
> > > >> > > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843208#10
> > > >> > > > 
> > > >> > > > The current state is that it's highly likely that a bug in
> > > >> > > > qtdeclarative-
> > > >> > > > opensource-src (source package) version 5.7.1~20161021-4 is the
> > > >> > > > cause
> > > >> > > > for
> > > >> > > > the  issue various people are seeing.
> > > >> > > > One of the Debian Qt maintainers filed the following bug for
> > > >> > > > it:
> > > >> > > > https://bugreports.qt.io/browse/QTBUG-56932
> > > >> > > > 
> > > >> > > > In Debian the following bugs have been reported which are
> > > >> > > > likely
> > > >> > > > all
> > > >> > > > caused
> > > >> > > > by  this issue:
> > > >> > > > https://bugs.debian.org/843250
> > > >> > > > https://bugs.debian.org/843332
> > > >> > > > 
> > > >> > > > and probably more will follow ...
> > > >> > > 
> > > >> > > More indeed followed already, so:
> > > >> > > 
> > > >> > > 1) Please delay updates to Debian Sid.
> > > >> > 
> > > >> > Dmitry (aka Mitya57) gave us updated Qt Declarative packages for
> > > >> > testing
> > > >> > and they fix the issue. So a fix should be available soon.
> > > >> > 
> > > >> > So I am on Qt 5.7.1 now without any instabilities. But
> > > >> > 
> > > >> > quasselclient currently crashes, see:
> > > >> > 
> > > >> > Bug#843416: libqt5widgets5: quasselclient segfaults with version
> > > >> > 5.7.1~20161021+dfsg-5 of libqt5widgets5
> > > >> > 
> > > >> > binNMU to fix that is scheduled.
> > > > 
> > > > […]
> > > > 
> > > >> Good news!
> > > >> Maybe let us know when to go ahead and upgrade.
> > > >> Thanx.
> > > > 
> > > > To have sddm and plasma session QML stuff work correctly:
> > > > 
> > > > qtdeclarative-opensource-src 5.7.1~20161021-5
> > > > 
> > > > for the fix you need at least libqt5qml5 and libqt5quick5
> > > > 5.7.1~20161021-5.
> > > > 
> > > > So wait till apt-cache policy shows the required versions for these
> > > > *and* you
> > > > can safely apt dist-upgrade without removing a ton of packages.
> > > > 
> > > > 
> > > > To fix quassel:
> > > > 
> > > > plasma-integration_5.8.2-1+b1_amd64
> > > > 
> > > > which Dmitry aka mitya57 also just uploaded.
> > > > 
> > > > 
> > > > I´d say tomorrow, maybe even earlier, depending on buildd speeds.
> > > > 
> > > > 
> > > > I suggest you monitor #debian-qt-kde IRC channel. Can have benefits as
> > > > mitya
> > > > provides links to packages he built there, so on my system Quassel
> > > > client is
> > > > also already fixed.
> > > > 
> > > > Ciao,
> > > 
> > > All neccessary packages are already in incoming.
> > > So they will be in Sid with the next mirror sync in ~ 3.5 hours
> > 
> > Hi,
> > 
> > Today KDE is back again. Thanks for being so fast in fixing this bug
> > 
> > Valerio
> 
> +1
> Philippe Merlin

Thanks for the warnings (saved a lot of heart-ache).
Thanks for the fixes.

Re: Warning: Please delay dist-upgrade to Debian Sid (qtdeclarative, sddm, Plasma)

[David Baron]

On יום ראשון, 6 בנובמבר 2016 15:56:20 IST Martin Steigerwald wrote:
> Am Sonntag, 6. November 2016, 11:14:04 CET schrieb Martin Steigerwald:
> > Am Sonntag, 6. November 2016, 00:59:07 CET schrieb Diederik de Haas:
> > > On zaterdag 5 november 2016 20:25:32 CET Andrey Rahmatullin wrote:
> > > > > If so, that is/was your problem and you'll likely have various qt5
> > > > > package
> > > > > at  version 5.7.1~20161021+dfsg-N.
> > > > > Downgrade those packages to their version in testing and there's a
> > > > > reasonable  chance things start working again. See also
> > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843208#10
> > > 
> > > The current state is that it's highly likely that a bug in
> > > qtdeclarative-
> > > opensource-src (source package) version 5.7.1~20161021-4 is the cause
> > > for
> > > the  issue various people are seeing.
> > > One of the Debian Qt maintainers filed the following bug for it:
> > > https://bugreports.qt.io/browse/QTBUG-56932
> > > 
> > > In Debian the following bugs have been reported which are likely all
> > > caused
> > > by  this issue:
> > > https://bugs.debian.org/843250
> > > https://bugs.debian.org/843332
> > > 
> > > and probably more will follow ...
> > 
> > More indeed followed already, so:
> > 
> > 1) Please delay updates to Debian Sid.
> 
> Dmitry (aka Mitya57) gave us updated Qt Declarative packages for testing and
> they fix the issue. So a fix should be available soon.
> 
> So I am on Qt 5.7.1 now without any instabilities. But
> 
> quasselclient currently crashes, see:
> 
> Bug#843416: libqt5widgets5: quasselclient segfaults with version
> 5.7.1~20161021+dfsg-5 of libqt5widgets5
> 
> binNMU to fix that is scheduled.
> 
> Ciao,

Good news!
Maybe let us know when to go ahead and upgrade.
Thanx.

Re: Compositing Problem

[David Baron]

On יום שבת, 22 באוקטובר 2016 21:54:34 IDT Brad Rogers wrote:
> On Sat, 22 Oct 2016 22:22:22 +0300
> David Baron  wrote:
> 
> Hello David,
> 
> >Dkms will build it against my kernels.
> 
> True, but that still doesn't restart X using the new drivers & modules.
> 
Obviously. If I can downgrade, dkms will run. Then I reboot.

> >As I said, maybe time to get plasma to play with Nouveau, get it out of
> >Nvidia's hands.
> 
> Maybe.

Re: Compositing Problem

[David Baron]

Dkms will build it against my kernels.
I have to get the needed packages first and this does not work.

As I said, maybe time to get plasma to play with Nouveau, get it out of 
Nvidia's hands.

> On Sat, 22 Oct 2016 21:16:42 +0300
> David Baron  wrote:
> 
> Hello David,
> 
> >Did not succede in downgrading (using synaptic, force version).
> >Same problem as downgrading to testing. Broken packages.
> 
> Just downgrading isn't enough.  There's the whole "build against the
> correct kernel" issue to consider, then you have to restart the X server.

Re: Compositing Problem

[David Baron]

Did not succede in downgrading (using synaptic, force version).
Same problem as downgrading to testing. Broken packages.

> Control: tag -1 + help
> 
> ¡Hola NVIDIA Maintainers!
> 
> It seems that the new plasma version has some kind of incompatibility with
> the nvidia-legacy-304xx packages in sid. The following mail reports that
> using the nvidia packages from backports works as expected.
> 
> In the kde team we are not using nvidia cards, so we can't reproduce/test
> this. And frankly, this might be way out of our league. :( Thus the request
> for help.
> 
> Is this issue known to you?
> Should this bug be reassigned to the nvidia packages?
> Can you reproduce it? If so, can you point us to what the problem might be?
> 
> Happy hacking,
> 
> El 2016-10-19 a las 23:33 -0700, Jimmy Johnson escribió:
> > On 10/12/2016 12:10 PM, David Baron wrote:
> >> Running must recent kwin, etc., with Sid nvidia-legacy-304xx driver.
> >> 
> >> Window decorations slow or do not show on non-KDE windows. If they do not
> >> show, one can pretend they are there and do everything.
> >> 
> >> Effects all compositing options.
> >> 
> >> Where to file bug?
> >> Quick fix?
> > 
> > Quick fix, force install all your 'nvidia' and 'glx' installed
> > packages back to 'Jessie-backports' and then 'lock-them' works, maybe
> > 20-24 packages that you will be locking, varies a little with my
> > installs, some I had not upgraded and I only had to lock the packages.
> > I used synaptic while in xfce4 and all your kde apps work from xfce4
> > too as a side note.  Note no problem with upgrades and those files
> > being locked, at this time anyways. hehe
> > 
> > There's a lot noise out there about fix's, I found nothing works for
> > me.  I came up with this fix and it works.  While gtk works with the
> > upgrade, plasma don't, it's a problem with plasma, you can't blame
> > nvidia and say they are not doing their part, this is a problem debian
> > plasma, I'm sure they are working on it. Seems to affect only
> > 'legacy-304' and could be a simple code error.
> > 
> > With the Debian-nvidia driver: Plasma is unable to start as it could
> > not correctly use OpenGL2.  Note dialog is working, sound is working,
> > no plasma.
> > 
> > With the Debian-free driver, computer freeze with colorful squiggly
> > lines and I have to push the power button and repair the file system.
> > 
> > David, do you have a better fix than down-grading the packages?  And I
> > may not need to down grade as many packages as I do, but it works.

Re: Compositing Problem

[David Baron]

Just maybe it be time that plasma worked correctly with Nouveau. Nouveau is 
beautiful for everything else.

At least, Debian folks are maintaining that, not dependent on Nvidia to 
maintain for legacy devices they would rather forget.

> Control: tag -1 + help
> 
> ¡Hola NVIDIA Maintainers!
> 
> It seems that the new plasma version has some kind of incompatibility with
> the nvidia-legacy-304xx packages in sid. The following mail reports that
> using the nvidia packages from backports works as expected.
> 
> In the kde team we are not using nvidia cards, so we can't reproduce/test
> this. And frankly, this might be way out of our league. :( Thus the request
> for help.
> 
> Is this issue known to you?
> Should this bug be reassigned to the nvidia packages?
> Can you reproduce it? If so, can you point us to what the problem might be?
> 
> Happy hacking,
> 
> El 2016-10-19 a las 23:33 -0700, Jimmy Johnson escribió:
> > On 10/12/2016 12:10 PM, David Baron wrote:
> >> Running must recent kwin, etc., with Sid nvidia-legacy-304xx driver.
> >> 
> >> Window decorations slow or do not show on non-KDE windows. If they do not
> >> show, one can pretend they are there and do everything.
> >> 
> >> Effects all compositing options.
> >> 
> >> Where to file bug?
> >> Quick fix?
> > 
> > Quick fix, force install all your 'nvidia' and 'glx' installed
> > packages back to 'Jessie-backports' and then 'lock-them' works, maybe
> > 20-24 packages that you will be locking, varies a little with my
> > installs, some I had not upgraded and I only had to lock the packages.
> > I used synaptic while in xfce4 and all your kde apps work from xfce4
> > too as a side note.  Note no problem with upgrades and those files
> > being locked, at this time anyways. hehe
> > 
> > There's a lot noise out there about fix's, I found nothing works for
> > me.  I came up with this fix and it works.  While gtk works with the
> > upgrade, plasma don't, it's a problem with plasma, you can't blame
> > nvidia and say they are not doing their part, this is a problem debian
> > plasma, I'm sure they are working on it. Seems to affect only
> > 'legacy-304' and could be a simple code error.
> > 
> > With the Debian-nvidia driver: Plasma is unable to start as it could
> > not correctly use OpenGL2.  Note dialog is working, sound is working,
> > no plasma.
> > 
> > With the Debian-free driver, computer freeze with colorful squiggly
> > lines and I have to push the power button and repair the file system.
> > 
> > David, do you have a better fix than down-grading the packages?  And I
> > may not need to down grade as many packages as I do, but it works.

Re: Compositing Problem

[David Baron]

On יום חמישי, 20 באוקטובר 2016 9:22:29 IDT Maximiliano Curia wrote:
> Control: tag -1 + help
> 
> ¡Hola NVIDIA Maintainers!
> 
> It seems that the new plasma version has some kind of incompatibility with
> the nvidia-legacy-304xx packages in sid. The following mail reports that
> using the nvidia packages from backports works as expected.
> 
> In the kde team we are not using nvidia cards, so we can't reproduce/test
> this. And frankly, this might be way out of our league. :( Thus the request
> for help.
> 
> Is this issue known to you?
> Should this bug be reassigned to the nvidia packages?
> Can you reproduce it? If so, can you point us to what the problem might be?
> 
> Happy hacking,
> 
> El 2016-10-19 a las 23:33 -0700, Jimmy Johnson escribió:
> > On 10/12/2016 12:10 PM, David Baron wrote:
> >> Running must recent kwin, etc., with Sid nvidia-legacy-304xx driver.
> >> 
> >> Window decorations slow or do not show on non-KDE windows. If they do not
> >> show, one can pretend they are there and do everything.
> >> 
> >> Effects all compositing options.
> >> 
> >> Where to file bug?
> >> Quick fix?
> > 
> > Quick fix, force install all your 'nvidia' and 'glx' installed
> > packages back to 'Jessie-backports' and then 'lock-them' works, maybe
> > 20-24 packages that you will be locking, varies a little with my
> > installs, some I had not upgraded and I only had to lock the packages.
> > I used synaptic while in xfce4 and all your kde apps work from xfce4
> > too as a side note.  Note no problem with upgrades and those files
> > being locked, at this time anyways. hehe
> > 
> > There's a lot noise out there about fix's, I found nothing works for
> > me.  I came up with this fix and it works.  While gtk works with the
> > upgrade, plasma don't, it's a problem with plasma, you can't blame
> > nvidia and say they are not doing their part, this is a problem debian
> > plasma, I'm sure they are working on it. Seems to affect only
> > 'legacy-304' and could be a simple code error.
> > 
> > With the Debian-nvidia driver: Plasma is unable to start as it could
> > not correctly use OpenGL2.  Note dialog is working, sound is working,
> > no plasma.
> > 
> > With the Debian-free driver, computer freeze with colorful squiggly
> > lines and I have to push the power button and repair the file system.
> > 
> > David, do you have a better fix than down-grading the packages?  And I
> > may not need to down grade as many packages as I do, but it works.

1. Previous bug reassigned to 304xx of AceofPeguins Freecell game failing to 
start apparently healed itself, no new 304xx so maybe something else!

2. For 841242 (I filed this one as well as starting this thread beforehand), 
Plasma does start. What will not work is starting compositing on start, had to 
hand edit that out of the rc file.

3. Toggling compisitor choices will restore the title bar decorations for the 
current session. This might seem to contra-indicate 304xx being the source of 
the problem. If this assessment is not correct, maybe do reassign.

4. If downgrading 304xx be the only way now, please give me step by step how 
to do this since testing packages are broken. Using dkms.

Compositing Problem

[David Baron]

Running must recent kwin, etc., with Sid nvidia-legacy-304xx driver.

Window decorations slow or do not show on non-KDE windows. If they do not 
show, one can pretend they are there and do everything.

Effects all compositing options.

Where to file bug?
Quick fix?

Plasma 5.8 Woes

[David Baron]

Came about with the demise of legacy nvidia drivers, testing versions gone 
forever it seems. Unstable version are really that.

Back to Nouveau. Now I like Nouveau, but newer Plasma does not.

So now the thing crashes every few minutes, restarts fine. Nothing lost since 
whatever window I have opened stays there through the mess. But still ...

Up-to-date Sid. What to do about this?

Re: *arg* "Personal Contacts" (KAddressBook) empty after upgrading to 5.7

[David Baron]

On יום רביעי, 7 בספטמבר 2016 5:57:28 IDT rhkra...@gmail.com wrote:
> On Wednesday, September 07, 2016 05:21:23 AM Tim Ruehsen wrote:
> > Anyways, I searched for *.vcf in ~/.kde and voila:
> > /usr/oms/.kde/share/apps/kabc/std.vcf
> > seems to hold all my contacts.
> 
> Not to be nit-picky but, for the reference of future readers, I presume you
> really meant /home (vs /usr), or, slightly generically:
> 
> /home//.kde/share/apps/kabc/std.vcf
> 
> > kaddressbook's 'import' function from the menu worked like a charm :-)
> > 
> > Thanks for your help - your mail inspired me to search for *.vcf.
> 
> Of course, that is an even better generic suggestion. ;-)

Or best still:
file->new ->addressbook
Can get to vcf and google contacts  from here.
End of story :-)

Re: Latest and Greatest: Dropbox Disappears

[David Baron]

On יום שבת, 27 באוגוסט 2016 21:45:26 IDT Alex DEKKER wrote:
> On 27/08/16 21:14, David Baron wrote:
> > Running up-to-date Sid.
> > 
> > Plasma desktop come up, the Dropbox icon (actually NOT, but a folder icon)
> > appears on the system bar. After a while, it is gone.
> > 
> > The daemon is still running.
> 
> Does it reappear if you run xembedsniproxy?
> 
> alexd

That was previous kde/plasma, now deprecated I believe.
Correct icon showed up this morning. See if it lasts.

Latest and Greatest: Dropbox Disappears

[David Baron]

Running up-to-date Sid.

Plasma desktop come up, the Dropbox icon (actually NOT, but a folder icon) 
appears on the system bar. After a while, it is gone.

The daemon is still running.

Re: Need help regarding experimental KDEPIM/Kmail

[David Goodenough]

On Friday 08 July 2016 16:42:35 Martin Steigerwald wrote:
> Am Freitag, 8. Juli 2016, 16:17:37 CEST schrieb Martin Steigerwald:
> > Hello Klaus.
> > 
> > Akonadi continues to work just fine on my mixed Sid/Experimental setup.
> > 
> > Am Freitag, 8. Juli 2016, 13:10:28 CEST schrieb Klaus Becker:
> > > Test 14:  ERROR
> > > 
> > > 
> > > Current Akonadi server error log found.
> > > Details: The Akonadi server reported errors during its current startup.
> > > The
> > > log can be found in  > > href='/home/klaus/.local/share/akonadi/akonadiserver.error'>/home/klaus/
> > > .l
> > > oc al/share/akonadi/akonadiserver.error.
> > > 
> > > File content of '/home/klaus/.local/share/akonadi/akonadiserver.error':
> > > Did not find MySQL server default configuration (mysql-global.conf)
> > > Failed to remove Unix socket
> > > Failed to remove runtime connection config file
> > 
> > I think it is this.
> > 
> > Resource agents AFAIK are used to access IMAP and POP3 accounts, calender
> > resources etc.
> > 
> > It might be due to inconsistent package versions.
> > 
> > Please post the mentioned logfile somewhere.
> > 
> > Please also check your package versions:
> > 
> > martin@merkaba:~> dpkg -l | grep akonadi | cut -c1-72
> > ii  akonadi-backend-mysql 4:16.04.2-3
> > ii  akonadi-server4:16.04.2-3
> > ii  akonadiconsole4:16.04.2-1
> > ii  libkf5akonadi-dev 4:16.04.2-3
> > ii  libkf5akonadiagentbase5:amd64 4:16.04.2-3
> > ii  libkf5akonadicalendar5:amd64  16.04.2-2
> > ii  libkf5akonadicontact5:amd64   4:16.04.2-2
> > ii  libkf5akonadicore-bin 4:16.04.2-3
> > ii  libkf5akonadicore5:amd64  4:16.04.2-3
> > ii  libkf5akonadimime5:amd64  4:16.04.2-2
> > ii  libkf5akonadinotes5:amd64 4:16.04.2-2
> > ii  libkf5akonadiprivate5 4:16.04.2-3
> > ii  libkf5akonadisearchdebug5:amd64   16.04.2-2
> > ii  libkf5akonadisearchpim5:amd64 16.04.2-2
> > ii  libkf5akonadiserver-dev   4:16.04.2-3
> > ii  libkf5akonadiwidgets5:amd64   4:16.04.2-3
> > ii  libkf5akonadixml5:amd64   4:16.04.2-3
> > 
> > Absolutely make sure that all of them are at 16.04!
> 
> It maybe also be that KDEPIM already packages are at wrong version. KDEPIM
> upstream developers splitted KDEPIM into different frameworks, for there are
> libkf5 kdepim related packages. I don´t know an easy filter for these. But
> I think resource agents might be in a KDEPIM related package. Yep:
> 
> martin@merkaba:~> dpkg -S /usr/bin/akonadi_maildir_resource
> kdepim-runtime: /usr/bin/akonadi_maildir_resource
> 
> martin@merkaba:~> LANG=C apt-cache policy kdepim-runtime
> kdepim-runtime:
>   Installed: 4:16.04.2-2
>   Candidate: 4:16.04.2-2
>   Version table:
>  *** 4:16.04.2-2 500
> 500 http://ftp.de.debian.org/debian sid/main amd64 Packages
> 100 /var/lib/dpkg/status
> 
> You absolutely need to have kdepim-runtime and related packages at 16.04.
> 
> Do not upgrade until you can get both Akonadi + KDEPIM at 16.04!
> 
> In case you already did: Either wait for KDEPIM 16.04 to appear or try to
> downgrade Akonadi.
> 
> Its important you need to upgrade KDEPIM and Akonadi in lockstep this time
> due to incompatible changes upstream introduced in Qt5 based Akonadi.
The odd thing is that the dependancies in the packages don't enforce that
Akonadi and KdePIM are in lockstep.

David
> 
> Thanks,

Re: Need help regarding experimental KDEPIM/Kmail

[David Baron]

With today's Sid upgrades.
1. Akonadi worked.
2. KMail repeatedly timed out looking for a lock, BUT ...
Individual account setups remained and enabled configuration to proceed.
3. After logout, login to KDE, FINALLY can use KMail once again.

Re: Upcoming KDEPIM changes in unstable (KMail, Kontact, KOrganizer, etc)

[David Goodenough]

On Saturday 02 July 2016 21:46:48 Lisandro Damián Nicanor Pérez Meyer wrote:
> Currently the latest version of kdepim is available in experimental.
> According to our limited tests it's working way better than kdepim 4.14
> (more stable, more performant, less bugs). However migrating from one to
> the other is not a trivial process (distribution wise, hopefully not for
> our users).
> 
> If you are still reading, please check the full text in [link].
> 
> [link]
> <http://perezmeyer.blogspot.com.ar/2016/07/upcoming-kdepim-changes-in-unsta
> ble.html>
> 
> Happy hacking!
Is there a migration guide so that we know what to expect (and when to panic)?

David

Re: plasma-systray-legacy replacement?

[David Baron]

On Thursday 09 June 2016 08:32:51 Thomas Fjellstrom wrote:
> Hi,
> 
> I've been monitoring the "big upgrade" thats been rolling out, and the only
> thing that seems to be blocking it on my desktop is a missing
> plasma-systray- legacy package. Is that going to make it to the new kde
> packages? or is it being discontinued?
> 
> I find it very useful as there are still plenty of irreplaceable apps that
> still use the old systray interface.
> 
> thanks!

Likely, no longer needed. The icons for which I installed it show just fine 
now without it.

Re: [solved] Re: trouble after upgrading to kdepim/experimental

[David Goodenough]

On Thursday 09 June 2016 15:48:37 Diederik de Haas wrote:
> On Thursday 09 June 2016 15:19:32 a...@bourges.de wrote:
> > I missed to upgrade akonadi-server - which seems to be quite important for
> > kdepim :))
> > 
> > Sorry for the noise,
> 
> I wouldn't call that noise at all as that may very well be the reason it
> wasn't working for me
If this is a general problem, sounds like a dependancy problem.

David

Re: kdepim 16.04 from experimental (UPDATE)

[David Goodenough]

On Wednesday 08 June 2016 22:33:18 Martin Steigerwald wrote:
> Hi David,
> 
> On Mittwoch, 8. Juni 2016 17:05:36 CEST David Goodenough wrote:
> > On Wednesday 08 June 2016 17:34:51 Martin Steigerwald wrote:
> > > On Mittwoch, 8. Juni 2016 17:20:38 CEST Martin Steigerwald wrote:
> > > > Hi!
> > > > 
> > > > In case you want to try it, also install the package kdepim-addons,
> > > > otherwise mails are displayed without header and you cannot select a
> > > > header
> > > > template in "View / Headers"
> > > > 
> > > > I will rebort bug.
> > > > 
> > > > Otherwise it works really nicely for me. Diederik has issues tough.
> > > > 
> > > > Of course, if you want to wait till it receives some further testing,
> > > > then
> > > > wait till its updated to unstable or migrates to testing.
> > > 
> > > OK, beware. Diederik just told me it doesn´t work at all for him. So if
> > > you
> > > depend on it, better wait!
> > > 
> > > Cause: Going back to KDEPIM 4 without a backup is not supported. It will
> > > *change* the Akonadi database + file database layout (for better
> > > performance).
> > 
> > As a matter of interest, is there a list of what needs to be backed up? 
> > BTW saying that we should use the Export Data -> Backup menu option only
> > works if you are using mysql, if you are using any of the other database
> > options it will feil because it aways uses msqldump whatever the
> > database.
> Well
> 
> 1. ~/.local/share/akonadi contains db if it was started by Akonadi (no
> external db) and file_db_data
> 
> 2. ~/.config/akonadi
> 
> 3. ~/.kde/share/config/akonadi*
> 
> 4. I´d also make sure to have a copy ~/.local/share/local-mail or wherever
> your local mail has been stored and all other primary data for your calender
> and addressbook resources. Where resources store primary data you see in
> the config files I mentioned in 3.
> 
> But scratch all that:
> 
> Make a complete backup of your home directory, just in case. You backup it
> anyway, don´t you? Still above information may help you in case you need to
> restore your old KDEPIM without wanting to restore your complete home
> directory.
I back my home directory, the question is what to restore in case the upgrade
has problems.
> 
> 
> I suggest the following approach:
> 
> - Don´t use export/import. As from many reports I think I don´t think it
> will work reliably and if so, will take ages.
> 
> - You can try whether automatic migration works.
> 
> 
> If automatic migration does not work:
> 
> 1. Make sure your maildirs are in ~/.local/share/local-mail, if its still in
> ~/.kde/share/something I´d move the folder to the new location
They are in .local
> 
> 2. Make sure your calendar and addressbook are in default locations (dunno
> whether these changed for Akonadi/KMail 16.04, I bet they still store them
> in ~/.kde/share, but you can still look at ~/.config/akonadi* akonadi
> configuration files (that is the new location of these, see 3 above)
don't really use these, and they are on CalDav andCardDav servers anyway.
> 
> 3. Rename ~/.local/share/akonadi and  ~/.config/akonadi
will do
> 
> 4. Let Akonadi reindex all resources from scratch.
> 
> Yet there is a slight risk that your current Akonadi still has some mails
> you moved around recently in file_db_data or the database itself and you
> would loose these.
> 
> 
> In case you just use IMAP accounts I suggest the following: Wipe all old
> Akonadi stuff and restart from scratch.
I only have disconnected IMAP, so none of the data remains on the server,
but I then filter them all into local folders. 
> 
> 
> I know this can be rough. I migrated from KDEPIM SC 4 and Akonadi 1 to
> KDEPIM 5 and Akonadi "2" quite some time ago as I compiled both from git
> master myself. I do think the automatic migration kind of worked, but it
> may have also been that I did the second approach and recreated the
> configuration and database from scratch letting Akonadi reindex all
> resources then.
> 
> I suggest to refrain from creating bugs with the Debian bug tracker related
> to the migration from KDEPIM SC 4 and Akonadi 1 to KDEPIM and Akonadi 16.04
> as any those issues are very likely upstream issues and I bet the Qt/KDE
> Debian team lacks the time to do much about it. Also KDEPIM SC 4 and
> Akonadi 1 are unmaintained, so…
> 
> This is a rough overview of what I know.
> 
> Thanks,
Thank you for your help.

David

Re: kdepim 16.04 from experimental (UPDATE)

[David Goodenough]

On Wednesday 08 June 2016 17:34:51 Martin Steigerwald wrote:
> On Mittwoch, 8. Juni 2016 17:20:38 CEST Martin Steigerwald wrote:
> > Hi!
> > 
> > In case you want to try it, also install the package kdepim-addons,
> > otherwise mails are displayed without header and you cannot select a
> > header
> > template in "View / Headers"
> > 
> > I will rebort bug.
> > 
> > Otherwise it works really nicely for me. Diederik has issues tough.
> > 
> > Of course, if you want to wait till it receives some further testing, then
> > wait till its updated to unstable or migrates to testing.
> 
> OK, beware. Diederik just told me it doesn´t work at all for him. So if you
> depend on it, better wait!
> 
> Cause: Going back to KDEPIM 4 without a backup is not supported. It will
> *change* the Akonadi database + file database layout (for better
> performance).
As a matter of interest, is there a list of what needs to be backed up?  BTW
saying that we should use the Export Data -> Backup menu option only works
if you are using mysql, if you are using any of the other database options
it will feil because it aways uses msqldump whatever the database.

David
> 
> So better wait.
> 
> That written it works just fine for me.
> 
> Thanks,

Upgrade with new kactivity module

[David Baron]

Works quite well. Please fix dependencies in plasma-desktop so that this one 
gets pulled in as well rather than having to do this manually. Legacy panel is 
no longer needed, it seems.

Plasma-containments-addons is listed as no longer needed, in autoremove list. 
Old 4.14 stuff.

Re: Unstale: Recommendation to wait with an dist-upgrade

[David Goodenough]

On Wednesday 01 June 2016 14:52:44 Martin Steigerwald wrote:
> Hi!
> 
> In case you want to avoid an after about 10 minutes crashing plasma session
> due to ksmserver not finding a symbol in a window manager related library, I
> recommend you to wait till you can get plasma-workspace, kscreen, kwin
> related packages from unstable. Otherwise you need to install some kscreen
> + kwin packages from experimental temporarily to get back a working
> session.
> 
> You can also wait for plasma-desktop as well, Maxy just uploaded it.
> 
> Akonadi 16.04 seems to work fine, but is not yet fully completely at 16.04,
> and KDEPIM packages are still to come for 16.04.
> 
> Thanks,
With a large transition like this it would REALY helpful to people who 
follow sid (which I guess is many of the people on this list) if there was
an email saying that such an upgrade had started (there was one 
where someone noted it had started this time) and then one saying
when it had finished.  Especially when the list of packages making up 
KDE has changed it is really had to know when everything is in place 
and therefore we can restart regular dist-upgrades.

David

Re: Kmail / Akonadi hanging, more

[David Baron]

Other error states demanding re-login:

Ineffective move or removal of message. Simple stays in its folder. No marking 
as read. Nada.

Re: Kmail / Akonadi hanging

[David Baron]

On Wednesday 13 April 2016 15:13:24 Tim Ruehsen wrote:
> Since a while (few months) akonadi 'hangs' from time to time.
> This happens when reading or removing emails from my folders.
> When it happens, Kmail shows me a nice gfx saying "Retrieving Folder
> Contents" and "Please wait ..."
> 
> No matter how long I wait... Kmail does not recover.
> Then, I open a console and do 'akonadictl restart', sometimes 'akonadictl
> fsck'. Kmail starts working again for a while...
> BTW, restarting Kmail does not help at all.
>.

Sometimes, killing it and restarting will get it back on track.
Logging out and re-logging in most reliable.

Re: Dassault Users

[Erwan David]

Le 13/04/2016 18:19, Keian Rao Eng Haau a écrit :
> I was not aware that spammers existed in Debian mailing lists xD
>
> 
>   Virus-free. www.avast.com
> 
>
>

Debian MLs are open, that's the drawback. But there are also advantages.

Re: Plasmashell is eating too much CPU sometimes

[David Baron]

On Thursday 03 March 2016 11:32:56 C. Mourad Jaber wrote:
> Hi,
> 
> I'm currently experimenting an issue with plasmashell
> (plasma-framework:5.16.0-1).
> 
> For an unknown reason plasmashell process start to eat 1 CPU at 100% and it
> stay stuck to consume all that power...
> 
> It seem to be linked to suspend-resume cycle.
> 
> Is there any possibility to have some logs or to analyse that issue ?
> 
> As workaround, when it happen, I kill and restart plasmashell :
> $ killall plasmashell ; kstart plasmashell
> 
> And Cpu consumption goes down normally...
> 
> Regards
> 
> Mourad

I had previously posted: When I start a new session (old session still 
running), the older session's plasmashell CPU is way up, sometimes bogging the 
system! If I unlock the old session's desktop, that problem subsides, though 
its plasmashell can still sometimes eat a lot of CPU, but not crippling.

What is the difference between "kstart plasmashell" and (simply) "plasmashell" 
to restart it?

Re: how to remove widgets from panel on plasma desktop?

[Erwan David]

Le 17/09/2015 20:39, Gary Dale a écrit :
> Now that I'm finally back using KDE, an old problem has become front
> and centre again. Namely how to remove widgets from the bottom panel?
> I've got some that I don't want that just take up space but there
> doesn't seem to be any way to remove them.
>
> And no, the widgets aren't locked.
>
> Any ideas?
>
>

in KDE 4 : right click, panel options -> panel settings then you can go
over a widget and there is a small tag with the name and a cross
click on this cross it will remove the widget from the panel

Re: Plasma past G++ transition

[David Baron]

On Tuesday 08 September 2015 14:17:54 Martin Steigerwald wrote:
> On Monday, 7 September 2015 09:17:54 CEST Marc Haber wrote:
> > On Wed, Sep 02, 2015 at 10:26:29AM +0200, Martin Steigerwald wrote:
> > > I am now past G++ transition on my system (full dist-upgrade) as I
> > > wrote.
> > > And tomorrow I was able to install kdepim again, in a newer upstream
> > > version to 4.4.10. It works nicely so far.
> > 
> > in testing or unstable?
> 
> unstable.
> 
> For testing I suggest to wait another week or so, maybe longer.
> 
> Thanks,

Working now, more or less the same as before.

Plasmashell Balky -- Workaround

[David Baron]

More than occasionally, plasmashell fails to paint the screen. Remains black 
with a cursor. Various functions and notifications do occur.

Formerly had to restart kdm (and have it still do this) or reboot ...

Workaround:
Have Yakuake part of active session startup. This will still operate.
Hit F12
Kill errant Plasmashell, i.e killall or kill -9 pid of this plasmashell.
Now re-run Plasmashell&

Home screen will now come up.

Re: Any idea when KDE will be working properly in Stretch?

[Erwan David]

On Mon, Aug 17, 2015 at 07:33:48AM CEST, Luc Castermans 
 said:
> It is not lost. First you have to select the resize option in the menu you get
> right-clicking on the upper left window corner
> 
> Luc

Why, oh why make those very frequent oprations more and more difficult to do ?

Is the anti-user design so trendy ?

Re: sddm versus kdm

[Erwan David]

On Tue, Aug 04, 2015 at 08:39:08AM CEST, Sune Vuorela  said:
> On 2015-08-02, Jimmy Johnson <420.christian.sin...@gmail.com> wrote:
> > Sune that's the second time you have posted that, I don't view it as 
> > being helpful.  It seems to me that KDM is only missing a systemsetting 
> > module/plugin in order to work properly with plasma 5.
> 
> I'm pretty sure that kdm will also be gone from debian before christmas,
> if not already next month, so staying with kdm is not really an option.
> 

Given taht kde 5 is far from complete, taht many programs still do not
work with it, it would be a bit harsh. (I've seen on the list problems
with hp-systray, kdeconnect, and the fact that sddm does not get the
user environment correctly)




-- 
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150804075415.gq31...@rail.eu.org

Re: sddm versus kdm

[David Baron]

On Sunday 02 August 2015 13:48:57 Jimmy Johnson wrote:
> On 08/02/2015 12:18 PM, Sune Vuorela wrote:
> > On 2015-08-02, Gary Dale  wrote:
> >> For a KDE user, what do people think are the strengths and weaknesses of
> >> the two managers?
> > 
> > KDM is dead upstream, SDDM is alive.
> > 
> > I think that's the simplest way of summing it up.
> > 
> > /Sune
> 
> Sune that's the second time you have posted that, I don't view it as
> being helpful.  It seems to me that KDM is only missing a systemsetting
> module/plugin in order to work properly with plasma 5.

and it works just fine without one


-- 
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5948852.0GboLoxPUq@dovidhalevi

Re: Plasma/KF5 : Situation in testing

[Erwan David]

Le 28/07/2015 17:19, Jeremy Lainé a écrit :
> Dear Debian/KDE users,
>
> We are aware that the current situation in testing is very unfortunate, with 
> two main issues:
>
> a/ systemsettings transitioned to testing before the corresponding KDE 
> Control Modules.
> The result is that systemsettings displays an empty screen. This is tracked 
> in the
> following bug:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790703
>
> b/ plasmoids such as plasma-nm transitioned to testing before plasma-desktop 
> 5. The result
> is that the plasmoid are no longer displayed in the system tray.
>
> We are working on getting plasma-desktop to transition to testing as soon as 
> possible
> (hopefully in 2 days time), which will resolve both those issues. In the 
> meantime, it
> might be best to refrain from updating your boxes running testing.
>
> We appreciate that the transition to KF5 is much rougher than we would have 
> liked, and
> would like apologise to all those impacted. In the meantime, please continue 
> to help us
> with your helpful bug reports, and do take the time to check whether a bug 
> has already
> been reported before filing a new one.
>
> For the Qt/KDE team,
> Jeremy
>
>
I may have open bugs which were duplicate. Just downgraded everything to
kde 4 and waiting for 5 to be ok for instal in testing.




signature.asc
Description: OpenPGP digital signature

How not to break a testing

[Erwan David]

Small parts of kde 5 arrive to testing, ibnstamlmling through
upgrade a bcompletely breaking the environemnt (eg sytem
setting cannot set anything more), etc. How can we detect that a
package is kde5 in order to NOT upgrade or install it until a complete
kde 5 is available in testing ?

Current upgrade path is best way to make users refuse the change,
because just doing the upgrades actually breaks everything.

And kde pacakges are NOT recognizable by name.



-- 
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150728124826.gj31...@rail.eu.org