Since upgrade to KDE 4.7.4 desktop effects do not work anymore

2012-03-19 Thread Luc Castermans

Hi,

Till yesterdays upgrade of Debian Wheezy / KDE from 4.6.5 to 4.7.4 the desktop
effects on my PC worked.   Now they stopped working.

I've a NVIDIA card using propriatery nvidia-driver.

Please help!

Regards,

Luc
<>

Re: Since upgrade to KDE 4.7.4 desktop effects do not work anymore

2012-03-19 Thread Luc Castermans
Op 19 maart 2012 19:39 heeft Brad Rogers  het
volgende geschreven:
>
>
> Hello Luc,
>
>> Till yesterdays upgrade of Debian Wheezy / KDE from 4.6.5 to 4.7.4 the
>> desktop effects on my PC worked.   Now they stopped working.
>
> Like you, I have an nVidia card, and use their driver.  Unlike you,
> effects are working here.
>
> Try moving ~/.kde (after logging out), and see what happens.

Actually that is how I started,  To make the story complete:

1. I have 2 PC´s and a file-server (NFS), the 2 PC´s are on Wheezy.
Both PC´s have local install, so / and /home is on the file-server
2. I dist-upgraded on PC1 (did not check effects on this PC)
3. I dist-upgraded PC2; now I could NOT login to this PC:
I get the KDM screen, but between 3 and 5 icon (disk,, kde)
I was thrown into the KDM login screen again
4. so I went into local root and deleted .kde from the users home-dir
5. Next I could log in, had to redo my whole desktop settings again and
6. found out desktop effects not working

So: should I try again ?

Many thanks,

-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAPwJL9x8t-Pa-UrLgwWfVsGg_zV=k3r6begeua5gh9vit0l...@mail.gmail.com



Re: Since upgrade to KDE 4.7.4 desktop effects do not work anymore

2012-03-20 Thread Luc Castermans

Op 19-03-12 20:44, Marco Valli schreef:

In data lunedì 19 marzo 2012 20:27:25, Luc Castermans ha scritto:

should I try again ?

Try to use raster:
$ touch ~/.kde/env/qt-graphic.sh
$ echo "export QT_GRAPHICSSYSTEM=raster">  ~/.kde/env/qt-graphic.sh
$ chmod +x ~/.kde/env/qt-graphic.sh
then restart kde.



thanks for sharing guys, just booted PC2, fiddled around
with the desktop settings and now they work.

Luc
<>

Re: Since upgrade to KDE 4.7.4 desktop effects do not work anymore

2012-03-21 Thread Luc Castermans

Op 20-03-12 21:55, Luc Castermans schreef:

Op 19-03-12 20:44, Marco Valli schreef:

In data lunedì 19 marzo 2012 20:27:25, Luc Castermans ha scritto:

should I try again ?

Try to use raster:
$ touch ~/.kde/env/qt-graphic.sh
$ echo "export QT_GRAPHICSSYSTEM=raster">  ~/.kde/env/qt-graphic.sh
$ chmod +x ~/.kde/env/qt-graphic.sh
then restart kde.



thanks for sharing guys, just booted PC2, fiddled around
with the desktop settings and now they work.


and yes, today it doesn´t work again!  Very weird and non-consistant 
behaviour.

Luc


<>

Re: KDE Plasma Workspaces 4.8.3 available in qt-kde.debian.net

2012-05-17 Thread Luc Castermans

Op 16-05-12 23:06, Matthias Müller schreef:

Before the upgrade, have you manually installed from libattr1 and
libacl1 from sid? The wheezy version is to low

That's the problem, I am not very experienced in installing libs or even
programs without aptitude.
Could you please offer a step-by-step recipe how to manually install
these libs?


use:

apt-get install -t sid  libattr1   libacl1

(after adding sid to /etc/apt/sources.list + apt-get update)
<>

kmail -> akonadi does not run

2012-06-01 Thread Luc Castermans

Hi, after this weeks update of Wheezy, KMail does not start anymore.
It reports Akonadi is not running.  On its turn Akonadi reports:

root@canne:~# akonadictl
D-Bus session bus is not available!
"[
0: akonadictl() [0x412b54]
1: akonadictl() [0x412e92]
2: /lib/x86_64-linux-gnu/libc.so.6(+0x324f0) [0x7f10508bc4f0]
3: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35) [0x7f10508bc475]
4: /lib/x86_64-linux-gnu/libc.so.6(abort+0x180) [0x7f10508bf6f0]


So something is really wrong. Is this recognised ?

Regards,

Luc
<>

Re: kmail -> akonadi does not run

2012-06-03 Thread Luc Castermans

Op 02-06-12 17:04, Chris Hodge schreef:

The real question then, would appear to be "Why was the removal of both
akonadi-backend-mysql and mysql-server-core-5.1 required?"

It wasn't that I removed them, the removal occurred during the update process, 
presumably a missed dependency in the packaging.  My solution was to reinstall 
the packages.  Wish I could provide more detail, but I simply updated my system 
as I do every morning, not paying a lot of attention, rebooted, started KMail 
and it wouldn't run because the akonadi wouldn't start.  My systems are pretty 
much straight wheezy, no special repos other than multimedia


So gents,as original reporter I confirm also in my case installing akonadi-backend-mysql and mysql-server-core-5.5 fixed the 
problem. Like Chris I run dist-upgrade minimal weekly and did miss the effects of it.


Thanks for your help!

Luc
<>

KDE screen lock reports wrong password

2012-07-31 Thread Luc Castermans

Hi,

I run KDE (Wheezy) on ¨old HW¨: Dell D400.  It seems that if I lock
the screen I cannot unlock it as my password is reported as wrong.
Upon initial login it is Ok.

On other machines (AMD64) this phenomena is not present.

Any idea what could be wrong?

Regards,

Luc
<>

wheezy issues

2012-12-15 Thread Luc Castermans

Hi,

I always update Wheezy.   KDE is not stable:

1. I get to see DrKonki right after logging in as a normal user.
2. Desktop Cube (CTRL-F11) does not work; other effects work.
3. Logging out as user 1, logging in as user 2: I do not get
to see the users´ desktop, the user splash screen remains on the screen

I use a NVIDIA card, bought a new one today allowing to use the latest
driver.   Above 3 remain.

I am alone seeing these issues?

Luc
<>

Re: wheezy issues

2012-12-16 Thread Luc Castermans

Op 16-12-12 02:46, Julian schreef:

Hi, is this stock wheezy? (no pinning).


Yes, stock Wheezy.   Special on the setup, which I run
for years now, is that /home is NFS-mounted on a file server
and the file server is getting slow, VIA Eden 700MHz with Squeeze  on it.


Is this a brand new user?


The users are old, happens at various users.


More information please.

 I get a segfault in Kactivitymanagerd, crash info attached.
(hope this survices the mailing list)

Regards

Luc



Jules.
On 16/12/12 02:23, Luc Castermans wrote:

Hi,

I always update Wheezy.   KDE is not stable:

1. I get to see DrKonki right after logging in as a normal user.
2. Desktop Cube (CTRL-F11) does not work; other effects work.
3. Logging out as user 1, logging in as user 2: I do not get
to see the users´ desktop, the user splash screen remains on the screen

I use a NVIDIA card, bought a new one today allowing to use the latest
driver.   Above 3 remain.

I am alone seeing these issues?

Luc





Application: KDE-activiteitenbeheerder (kactivitymanagerd), signal: 
Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#5  0x7f79df0413b0 in ?? () from /usr/lib/libsopranoclient.so.1
#6  0x7f79df041034 in ?? () from /usr/lib/libsopranoclient.so.1
#7  0x7f79df0410f9 in ?? () from /usr/lib/libsopranoclient.so.1
#8  0x7f79e303cb00 in QThreadStorageData::set(void*) () from 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x7f79df03ea6f in ?? () from /usr/lib/libsopranoclient.so.1
#10 0x7f79df03ead9 in ?? () from /usr/lib/libsopranoclient.so.1
#11 0x7f79df03e04a in Soprano::Client::LocalSocketClient::connect(QString 
const&) () from /usr/lib/libsopranoclient.so.1
#12 0x7f79e37649bd in ?? () from /usr/lib/libnepomuk.so.4
#13 0x7f79e3760412 in Nepomuk::ResourceManager::init() () from 
/usr/lib/libnepomuk.so.4
#14 0x7f79e37625d5 in ?? () from /usr/lib/libnepomuk.so.4
#15 0x7f79e376274b in 
Nepomuk::ResourceManager::qt_metacall(QMetaObject::Call, int, void**) () from 
/usr/lib/libnepomuk.so.4
#16 0x7f79e34b5c13 in ?? () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4
#17 0x7f79e314ea2e in QObject::event(QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#18 0x7f79e24e370c in QApplicationPrivate::notify_helper(QObject*, QEvent*) 
() from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#19 0x7f79e24e7b8a in QApplication::notify(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#20 0x7f79e3c42886 in KApplication::notify(QObject*, QEvent*) () from 
/usr/lib/libkdeui.so.5
#21 0x7f79e3139b5e in QCoreApplication::notifyInternal(QObject*, QEvent*) 
() from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#22 0x7f79e313d9e1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, 
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#23 0x7f79e31680e3 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#24 0x7f79de72a355 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x7f79de72a688 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x7f79de72a744 in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x7f79e3168276 in 
QEventDispatcherGlib::processEvents(QFlags) () 
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#28 0x7f79e258483e in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#29 0x7f79e31388af in 
QEventLoop::processEvents(QFlags) () from 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#30 0x7f79e3138b38 in 
QEventLoop::exec(QFlags) () from 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#31 0x7f79e313dcf8 in QCoreApplication::exec() () from 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#32 0x00406495 in ?? ()
#33 0x7f79e1c93ead in __libc_start_main (main=, 
argc=, ubp_av=, init=, 
fini=, rtld_fini=, stack_end=0x7fff3d389088) at 
libc-start.c:228
#34 0x004064ed in _start ()
<>

Re: wheezy issues

2012-12-22 Thread Luc Castermans

Op 16-12-12 15:52, Lisandro Damián Nicanor Pérez Meyer schreef:

On Sun 16 Dec 2012 05:44:35 Luc Castermans escribió:

Op 16-12-12 02:46, Julian schreef:

Hi, is this stock wheezy? (no pinning).

Yes, stock Wheezy.   Special on the setup, which I run
for years now, is that /home is NFS-mounted on a file server
and the file server is getting slow, VIA Eden 700MHz with Squeeze  on it.


Is this a brand new user?

The users are old, happens at various users.


More information please.

   I get a segfault in Kactivitymanagerd, crash info attached.
(hope this survices the mailing list)

Please install libsoprano-dbg and re create the backtrace.




Done; and backtrace attached.

Luc

Application: KDE-activiteitenbeheerder (kactivitymanagerd), signal: 
Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#5  indexOf (from=0, t=@0x21adb18: 0x21ad9b0, this=0x21ad950) at 
/usr/include/qt4/QtCore/qlist.h:855
#6  QList::removeAll (this=0x21ad950, _t=@0x21adb18: 0x21ad9b0) at 
/usr/include/qt4/QtCore/qlist.h:772
#7  0x7f64adc34034 in Soprano::Client::SocketHandler::~SocketHandler 
(this=0x21adb00, __in_chrg=) at 
../../client/clientconnection.cpp:59
#8  0x7f64adc340f9 in Soprano::Client::SocketHandler::~SocketHandler 
(this=0x21adb00, __in_chrg=) at 
../../client/clientconnection.cpp:61
#9  0x7f64b1c2fb00 in QThreadStorageData::set(void*) () from 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#10 0x7f64adc31a6f in 
qThreadStorage_setLocalData (d=..., 
t=) at /usr/include/qt4/QtCore/qthreadstorage.h:92
#11 setLocalData (t=0x21be780, this=) at 
/usr/include/qt4/QtCore/qthreadstorage.h:155
#12 Soprano::Client::ClientConnection::socketForCurrentThread (this=0x21b06d0) 
at ../../client/clientconnection.cpp:95
#13 0x7f64adc31ad9 in 
Soprano::Client::ClientConnection::connectInCurrentThread (this=) at ../../client/clientconnection.cpp:800
#14 0x7f64adc3104a in Soprano::Client::LocalSocketClient::connect 
(this=0x21bb5b8, name=...) at ../../client/localsocketclient.cpp:141
#15 0x7f64b23579bd in ?? () from /usr/lib/libnepomuk.so.4
#16 0x7f64b2353412 in Nepomuk::ResourceManager::init() () from 
/usr/lib/libnepomuk.so.4
#17 0x7f64b23555d5 in ?? () from /usr/lib/libnepomuk.so.4
#18 0x7f64b235574b in 
Nepomuk::ResourceManager::qt_metacall(QMetaObject::Call, int, void**) () from 
/usr/lib/libnepomuk.so.4
#19 0x7f64b20a8c13 in ?? () from /usr/lib/x86_64-linux-gnu/libQtDBus.so.4
#20 0x7f64b1d41a2e in QObject::event(QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#21 0x7f64b10d670c in QApplicationPrivate::notify_helper(QObject*, QEvent*) 
() from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#22 0x7f64b10dab8a in QApplication::notify(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQtGui.so.4
#23 0x7f64b2835886 in KApplication::notify(QObject*, QEvent*) () from 
/usr/lib/libkdeui.so.5
#24 0x7f64b1d2cb5e in QCoreApplication::notifyInternal(QObject*, QEvent*) 
() from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#25 0x7f64b1d309e1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, 
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#26 0x7f64b1d5b0e3 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#27 0x7f64ad31d355 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x7f64ad31d688 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x7f64ad31d744 in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x7f64b1d5b276 in 
QEventDispatcherGlib::processEvents(QFlags) () 
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#31 0x7f64b117783e in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#32 0x7f64b1d2b8af in 
QEventLoop::processEvents(QFlags) () from 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#33 0x7f64b1d2bb38 in 
QEventLoop::exec(QFlags) () from 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#34 0x7f64b1d30cf8 in QCoreApplication::exec() () from 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#35 0x00406495 in ?? ()
#36 0x7f64b0886ead in __libc_start_main (main=, 
argc=, ubp_av=, init=, 
fini=, rtld_fini=, stack_end=0x7fff1fb98f28) at 
libc-start.c:228
#37 0x004064ed in _start ()
<>

Re: wheezy issues

2013-01-04 Thread Luc Castermans

Op 03-01-13 16:03, Lisandro Damián Nicanor Pérez Meyer schreef:

On Sat 22 Dec 2012 09:58:02 Luc Castermans escribió:

Op 16-12-12 15:52, Lisandro Damián Nicanor Pérez Meyer schreef:

[snip]

Done; and backtrace attached.

Sorry for the delay. Saddly I can't get any ideas from it :-/



Ok; bug is still active on my desktop. As mentioned before
my systems comprise of desktops and a server. The desktop´s /home
dir is NFS-mounted on the server, so incl. de user .kde-dirs. The server
was running Squeeze, upgraded to Wheezy yesterday.
Overall behaviour did not change.

Also before I mentioned the behaviour that the KDE splashscreen
(with the 5 icons) remains visible after logging out + in of the
same account. Processes seems normaly running except that I cannot
see the normal KDE desktop. Further notices KWIN is eating up to 80% CPU
in this "mode".

Maybe this triggers some thoughts...

Luc

<>

Fwd: QA during fosdem (was: Re: Debian Project News - January 21st, 2013)

2013-01-22 Thread Luc Castermans
Hi,

I will be visiting FOSDEM in Brussels next February. Apart from being
Debian user, contributer, etc. and
member of LibreOffice Dutch language team I represent a community of
Software Process Improvers (http://www.st-spider.nl/)
To learn from others this team regularly organises lectures and meetings.
For the autumn 2013 SPIDER plans
a couple of lectures about "Open Source". Themes around "software
development processes in the cloud",
"quality assurance",  "requirements gathering", "." and many others are
of interesest.

I am looking forward to meet those who could give a lecture during this
event. Dutch is no requirement, English is fine.

Anyway: I like to pre-discuss with those who would be interested to give a
lecture to SPIDER during FOSDEM.

Drop me a mail, many thanks!

-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


signature.asc
Description: PGP signature


Re: digikam upgrade issue

2013-04-06 Thread Luc Castermans

Op 06-04-13 09:14, Rainer Dorsch schreef:

Hello,

Am Friday 05 April 2013 schrieb Sune Vuorela:

Actual upgrade issues, like file overlaps and such - you are most
welcome to report those. But remember your backup.

not sure if this has the same root cause as the amarok upgrade issue I
reported in the previous post. If yes, please ignore:

blackbox:~# aptitude install -t experimental digikam
The following packages will be upgraded:
   digikam{b} digikam-data{b}
2 packages upgraded, 0 newly installed, 0 to remove and 667 not upgraded.
Need to get 19.8 MB of archives. After unpacking 3206 kB will be used.
The following packages have unmet dependencies:
  digikam : Conflicts: libkdcraw-data but 4:4.8.4-1 is installed.
Conflicts: libkdcraw20 but 4:4.8.4-1 is installed.
Conflicts: libkexiv2-10 but 4:4.8.4-1 is installed.
Conflicts: libkexiv2-data but 4:4.8.4-1 is installed and it is kept
back.
Conflicts: libkipi-data but 4:4.8.4-1 is installed and it is kept
back.
Conflicts: libkipi8 but 4:4.8.4-1 is installed.
Conflicts: libksane0 but 4:4.8.4-1 is installed.
  digikam-data : Conflicts: libkdcraw-data but 4:4.8.4-1 is installed.
 Conflicts: libkdcraw20 but 4:4.8.4-1 is installed.
 Conflicts: libkexiv2-10 but 4:4.8.4-1 is installed.
 Conflicts: libkexiv2-data but 4:4.8.4-1 is installed and it is
kept back.
 Conflicts: libkipi-data but 4:4.8.4-1 is installed and it is
kept back.
 Conflicts: libkipi8 but 4:4.8.4-1 is installed.
 Conflicts: libksane0 but 4:4.8.4-1 is installed.
The following actions will resolve these dependencies:

  Remove the following packages:
1) digikam
2) digikam-data
3) kipi-plugins



Accept this solution? [Y/n/q/?]

Thanks,
Rainer



Yes. I have exactly the same issue.

Luc

<>

Re: So I have a Plasma 5 desktop!

2015-07-09 Thread Luc Castermans
How to get it? Which sources.list is required?
Can you share via Debian wiki.

Luc

Op do 9 jul. 2015 12:09 schreef Marco Valli :

> In data giovedì 9 luglio 2015 09:28:53, Martin Steigerwald ha scritto:
> > One time Cc to Maxy (please remove on replies).
>
> Plasma 5 works great here. Tnx a lot to Suone, Maxy and the others Debian
> KDE
> guys.
>
> --
> Marco Valli
>
>
> --
> 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/22453286.TVuWHezW9c@debian
>
>


Re: Plasma/KF5 : Situation in testing

2015-07-28 Thread Luc Castermans
I did encounter the issue. Thanks a lot for your message. Great help to
understand the situation! Luc

Op di 28 jul. 2015 17:26 schreef Jeremy Lainé :

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


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

2015-08-16 Thread Luc Castermans
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

Op zo 16 aug. 2015 20:04 schreef Gary Dale :

> I'm hoping that losing the ability to drag edges and corners to resize
> windows is temporary and that the KDE designers aren't trying to be more
> like Gnome.
>
>


Re: Plasma past G++ transition

2015-09-02 Thread Luc Castermans
this is very nice news!

However I tried to make fresh install from Testing last weekend, and then
get many dependency conflicts as
soon as I issue a "aptitide install kde-full".   In summary: I installed a
fresh Testing (base system), then do "aptitude install kde-full".

Should I add unstable to sources.list, then do "aptitude install -t sid
kde-full", or even from experimental?

Regards

Luc

Op wo 2 sep. 2015 om 10:35 schreef Marco Valli :

> In data mercoledì 2 settembre 2015 10:26:29, Martin Steigerwald ha scritto:
> > Thanks to the Debian Qt/KDE team for this huge effort.
>
> +1
>
> --
> Marco Valli
>
>


Re: Plasma desktop unusable in stretch

2015-09-05 Thread Luc Castermans
Thanks for excellent overview. Indeed massive wirk going on. Big
compliments to you guys!

Luc

Op za 5 sep. 2015 11:27 schreef Martin Steigerwald :

> Accidentally send off list.
>
> Am Donnerstag, 3. September 2015, 16:24:40 schrieb Gary Dale:
> > On 03/09/15 03:42 PM, Andrey Rahmatullin wrote:
> > > On Thu, Sep 03, 2015 at 03:03:35PM -0400, Gary Dale wrote:
> > >> Sorry, but before releasing a major package to "testing", shouldn't
> it be
> > >> tested against the "testing" environment?
> > >
> > > No, we don't do this.
> >
> > Obviously, but the question was "shouldn't you?"
>
> Thing is:
>
> Many of the issues were *transitional*.
>
> And as far as I know the exact order in which packages appear in testing is
> basically unpredictable, it is also quite unpredictable what problems can
> appear in testing. It could also be problems, that didn´t appear in
> unstable
> at all due to a different order of appearance of packages in the archive.
>
> Also I am not sure whether RC bugs are really a good way to get a stable
> transition for testing user. I bet it is not, cause a RC bug only stops one
> package, and maybe its dependencies, but… KDE Frameworks 5 and Plasma 5 are
> several hundred packages.
>
> So what would be needed is to prepare the migration completely separated
> from
> unstable, say in some PPA, *without* hindering the other package uploads
> too
> much. And then find a way to put all of these new packages into unstable at
> once and then into testing at once.
>
> I do not think that such an infrastructure  for Debian is already in place.
> PPAs are being worked on, and they will likely come. But atomic
> transitions of
> several hundred packages from a PPA into unstable and then testing without
> messing things up? Probably a challenging task.
>
> And also that said: This g++ ABI transition is one of the biggest
> transition I
> have ever seen. A member of the Qt/KDE team said to me that the last
> transition that big he remembers, was about 10 years ago.
>
> So it is not that this is happing every year or so.
>
> The transition is challenging. From what I see the Debian Qt/KDE team does
> a
> *marvellous* job. I try to help with bug triaging here and there. And on
> DebConf 2015 I experienced myself the amount of work needed to fix up those
> symbol files in the packages for the transition. I did it manually and
> someone
> more experienced can likely do it much faster, but thing is: It is still
> work.
>
> So members of the Debian Qt/KDE team, I am now also one, work, usually in
> their free time, unpaid, on delivering a new Plasma version to all of you.
>
> They do a marvellous job and that in my eyes deserves a huge big "Thank
> you!"
> instead of bashing on them. I have met people of the team on DebConf and
> they
> work on the stuff with best intentions. Its not that they plan new creative
> ways on how to break the desktop experience for you.
>
> Thanks,
> --
> Martin
>
>


Re: Plasma past G++ transition

2015-09-06 Thread Luc Castermans

Op 05-09-15 om 12:21 schreef Martin Steigerwald:

Am Freitag, 4. September 2015, 03:43:44 schrieb Diederik de Haas:

I may go in and remove things like kde-full, and kde-workspace* (I
think that was renamed plasma-workspace*?).

I do think that kde-workspace has been 'retired'; it's not available on my
system. Doing 'aptitude markauto kde-workspace' seems like a good idea.
Wrt kde-full I read on IRC that work is underway to make that
installable/upgradable, but since it includes the whole kitchen it
naturally  takes to most time to get ready.

Here kde-full is done (amd64 sid). Maybe not all mirrors catched up yet?



Approx. 2 ago weeks KED was pushed back to "Debian Stable", today I did "apt-get -t 
sid kde-full"
and all was installed, with nice desktop as result, (architecture: amd64)

Thanks for great work!!!

Luc


<>

Re: Any idea when plasma desktop will be working?

2015-09-17 Thread Luc Castermans
And from Testing.

Op do 17 sep. 2015 18:37 schreef Luc Castermans :

> Also here. On at least 3 pc's.
>
> Op do 17 sep. 2015 18:10 schreef Andrey Rahmatullin :
>
>> On Thu, Sep 17, 2015 at 11:59:43AM -0400, Gary Dale wrote:
>> > It's been a couple of weeks now since it broke. I'm continuing to do
>> > upgrades daily and see some progress in other tools (e.g. aptitude is
>> back)
>> > but the plasma desktop remains unusable. Does anyone how fixing it is
>> > progressing?
>> It is usable here, what dou you mean?
>>
>> --
>> WBR, wRAR
>>
>


Re: Any idea when plasma desktop will be working?

2015-09-17 Thread Luc Castermans
Also here. On at least 3 pc's.

Op do 17 sep. 2015 18:10 schreef Andrey Rahmatullin :

> On Thu, Sep 17, 2015 at 11:59:43AM -0400, Gary Dale wrote:
> > It's been a couple of weeks now since it broke. I'm continuing to do
> > upgrades daily and see some progress in other tools (e.g. aptitude is
> back)
> > but the plasma desktop remains unusable. Does anyone how fixing it is
> > progressing?
> It is usable here, what dou you mean?
>
> --
> WBR, wRAR
>


Re: Digikam

2015-10-03 Thread Luc Castermans
I think to get it soon you can help. Nobody stops you doing this

Luc

Op za 3 okt. 2015 10:59 schreef MERLIN Philippe <
phil-deb1.mer...@laposte.net>:

> Le samedi 3 octobre 2015, 00:41:53 anxious...@gmail.com a écrit :
>
> > Does anyone have any experience of installing/running the tarball
> version on
>
> > Debian unstable?
>
> >
>
> I made it but unsuccessfully, references were always missing, not being
> an expert, I abandoned, hoping that the Digikam Debian team was going to
> bring out to us quite new Digikam. Be that anybody can give us an
> information about the possible date of the release of this new version?
>
> Philippe Merlin
>


Re: dolphin and previews

2015-10-27 Thread Luc Castermans
Normally Okular. Not sure which package this is.

Luc
Op 27 okt. 2015 2:59 p.m. schreef "Holger Schramm" :

> Hi,
>
> i am using kde5 on debian testing. Currently there are no pdf previews
> available in dolphin. Which package have i to install that this works
> again? It occurs only on pdfs. Images works flawlessly.
>
> --
> Holger
>
>


Re: plasma desktop broken again :(

2015-10-31 Thread Luc Castermans
Gents,

I enjoy KDE5 desktop (testing / unstable) since quite some weeks now.
Quite usable it is!  Thanks for your efforts, I will use it, thereby
helping to
mature it.

Many, many, thanks.

Luc

2015-10-31 14:38 GMT+01:00 Martin Steigerwald :

> Am Freitag, 30. Oktober 2015, 17:57:03 CET schrieb Matthias Bodenbinder:
> > Full acknowledge!
> >
> > I am not an early adopter. If I would be somebody who likes bleeding edge
> > software with all the risks I would be using sid.I am using debian
> testing
> > because it is supposed to be a good compromise.
> >
> > I am personally not in agreement with statements like "stuff happens".
> This
> > "love it or leave it" attitude is preventing any continuous improvement
> > discussion. And this is for sure: The release process "unstable ->
> testing"
> > has room for improvement.
>
> The *issues* are known.
>
> But a discussion done *here* isn´t going to change anything.
>
> A discussion about testing on debian-devel may lead to some changes,
> especially if you would propose a constructive alternative and also offer
> to
> help out to make it happen.
>
> If you do that, first refer to old discussions about always releaseable
> testing. This really is no new topic at all.
>
> Its a volunteer effort, so unless you volunteer to help, you can complain
> as
> much as you want, and it is your perfect right to do so, yet, whether
> someone
> else steps up to fix your complaints is *completely* out of your control.
> It
> is every contributor´s perfect right to choose how to allocate the time
> spend
> on Debian work. You have no moral right to decide on how others choose to
> spend their free time. And in my view when I complain I often find myself
> feeling miserable afterwards, cause I see that my complaining doesn´t
> facilitiate change.
>
> There are only a few people doing this packaging work in their free time.
> As
> to my knowledge about no one is being paid for this work. From my
> impressions
> at DebConf I surely got that they work to with best intentions and to the
> best
> of their abilities. You can even just monitor #debian-qt-kde IRC channel
> for a
> while to see what I mean. No one intends to break anything for anyone. Yet,
> its a complex matter and people do mistakes at times and due to the way
> migrations of packages into testing works the results at times are
> basically
> unpredictable.
>
> From what I gathered so far, I´d even basically recommend to use unstable
> for
> some time at the moment, at it seems to be far less affected and fixes
> seem to
> come through much quicker. Then settle back to testing at another time.
>
> And in general if testing/unstable is too bumpy for you, use *stable* until
> later.
>
> We are still in the development phase for next Debian stable. Debian
> packagers
> want to get in what they want to see in next Debian stable. Nothing has
> been
> frozen yet, so in case you want a slower ride: Wait longer after release of
> stable till you switch to testing or unstable.
>
> You can still use tried and tested KDE SC 4.14 if you want it. So if it is
> to
> bumpy to you, use *stable*.
>
> That said I may probably stop discussing here again as in the time I spend
> answering here I could have worked on helping the Qt/KDE team to move
> forward.
> I have been busy with lots of other stuff and I didn´t help much. But fully
> aware of that I also didn´t complain, cause I do understand that the
> current
> team works to the best of their abilities and I feel gratitude for that. So
> unless I see opportunities to help constructively I mostly remain quiet to
> let
> others do their work without urging them spend additional time with my not
> so
> constructive feedback.
>
>
> And yes, before I close: Testing/unstable has been bumby in the last
> months.
> But the libstcd++ ABI transitions was and still is one of the biggest
> transitions Debian ever had. One packager told me that the last time such a
> big transition happened for KDE/Plasma was about 10 years ago. Added to
> that
> it wasn´t / isn´t the only transition.
>
> Thanks,
> --
> Martin
>
>


-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


long time before Desktop/Taskmanager is ready

2015-12-02 Thread Luc Castermans

Dear,

I am running Plasma5 Testing/Sid since quite some months, as reported to this 
list.
I regularly (<= weekly) update my packages.

Since a few weeks after/during login it takes long time (approx. 1 min) before 
the desktop/taskmanager is ready.
The desktop does not react at all to mouse clicks. As soon as the timeout is 
over, everything is normal.
All user accounts behave the same and from same moment onwards.

Any ideas about the root-cause of this?

thx

Luc
<>

Re: long time before Desktop/Taskmanager is ready

2015-12-05 Thread Luc Castermans

Op 03-12-15 om 00:18 schreef Facundo Aguilera:

On Wed, Dec 2, 2015 at 7:08 PM, Lisandro Damián Nicanor Pérez
 wrote:

On Wednesday 02 December 2015 20:05:12 Luc Castermans wrote:

Dear,

I am running Plasma5 Testing/Sid since quite some months, as reported to
this list. I regularly (<= weekly) update my packages.

Since a few weeks after/during login it takes long time (approx. 1 min)
before the desktop/taskmanager is ready. The desktop does not react at all
to mouse clicks. As soon as the timeout is over, everything is normal. All
user accounts behave the same and from same moment onwards.

Any ideas about the root-cause of this?

All I can say is that *sometimes* I see this too, but never got to try to
debug it I'm afraid :-/


Maybe it is related to the bluetooth problem reported here:
https://bugs.kde.org/show_bug.cgi?id=354230



thanks. It is definitely a plasma issue.  If I assure e.g. Icedove is started 
after loging-in,
then icedove is working normal while the desktop/plasma is not.

I have only 2 BlueTooth related packages installe:


root@canne:~# dpkg -l | fgrep bluet
ii  libbluetooth-dev 5.36-1 amd64
Development files for using the BlueZ Linux Bluetooth library
ii  libbluetooth3:amd64 5.36-1 amd64
Library to use the BlueZ Linux Bluetooth stack
root@canne:~#


Regards



Luc

Luc
<>

Re: long time before Desktop/Taskmanager is ready

2015-12-07 Thread Luc Castermans

Op 07-12-15 om 18:09 schreef Josep Febrer:

El Dimecres, 2 de desembre de 2015, a les 20:05:12, Luc Castermans va
escriure:

Dear,

I am running Plasma5 Testing/Sid since quite some months, as reported to
this list. I regularly (<= weekly) update my packages.

Since a few weeks after/during login it takes long time (approx. 1 min)
before the desktop/taskmanager is ready. The desktop does not react at all
to mouse clicks. As soon as the timeout is over, everything is normal. All
user accounts behave the same and from same moment onwards.

Any ideas about the root-cause of this?

In my case upgrading plasma-nm (4:5.4.3-1) from sid fixed this issue.


Hi Josep,

plasma-nm arrived in testing today and indeed it solved the issue. Thanks!!

Luc

<>

Re: Safe to upgrade?

2015-12-09 Thread Luc Castermans
I run Plasma (testing/sid) on a desktop, so no suspend function needed.
I really like it and it is very, very usable.

Luc

2015-12-09 18:42 GMT+01:00 Chris Knadle :

> Marc Haber:
> > On Tue, Dec 08, 2015 at 06:56:45PM +, Chris Knadle wrote:
> >> Marc Haber:
> >>> On Tue, Dec 08, 2015 at 05:31:43PM +, Chris Knadle wrote:
> >>>> However just within the last couple of weeks there's been a lot of
> work on
> >>>> the KDE5 packages and Plasma 5 is now usable.
> >>>
> >>> I still regularly experience plasmashell taking 100 % CPU and needing
> >>> a kill + restart. This especially happens over night when the machine
> >>> is idling away in the lock screen.
> >>
> >> Hmmm!  I normally put my computer to sleep or hibernate for the night,
> so I
> >> haven't seen this -- ick.  I wouldn't like to find that.
> >
> > Actually, the current behavior is a 100 % improvement over August's
> > state of KDE plasma 5 when it was still a complete crash, needing a
> > remote login+ kill X to get the machine back after it was left idling
> > over night.
>
> Yeah, a couple of months ago I repeatedly had to break out to a text
> console
> with Ctrl-Alt-F2 to restart X when I tried Plasma 5.
>
> > I have not dared to suspend the machine since the KDE Plasma 5 update
> > since if the current system doesn't even survive a night of idling,
> > how could it possibly survive a suspend+resume cycle?
>
> Well I don't think suspend/resume should break because of Plasma 5 per se;
> each of these are supposed to resume to the same memory state and continue
> from there.  I'm able to both suspend and hibernate and get back right now;
> that's not to say that this works for everybody of course, it's just one
> data point.  Only way to know if it works for you is to try it.
>
> >>> I didn't report it yet since I use a locally compiled
> >>> plasma-widget-addons with the quick launch widget backported from
> >>> plasma 5.5.
> >>>
> >>> And the volume occasionally jumps up to 100 %, especially when one
> >>> clicks on "leave" or does things in System Settings. My neighbors
> >>> really love that.
> >>
> >> I have this "volume jumps to 100%" issue, but in my case it's a
> self-made
> >> thing -- in my ~/.bashrc I have this:
> >>
> >># Restore local ALSA mixer settings
> >>/usr/sbin/alsactl --file ~/.config/asound.state restore
> >
> > Not in my case.
>
> Yes, I assumed not.  The main reason I mentioned the above is a) it means
> if
> I've ever had the same thing happen the data is convoluted with the running
> of the alsactrl restore, b) just in case you might have done something
> similar and had forgotten (I didn't think this likely).
>
>-- Chris
>
> --
> Chris Knadle
> chris.kna...@coredump.us
>
>


-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


Re: iceweasel locking up under KDE, fine under Xfce

2015-12-12 Thread Luc Castermans

Op 12-12-15 om 01:09 schreef Jimmy Johnson:

On 12/11/2015 01:30 PM, Arthur Marsh wrote:

Arthur Marsh wrote on 03/12/15 23:23:


With an update to KDE from unstable, iceweasel from unstable locked up
every time until I upgraded iceweasel to experimental. Now iceweasel
runs fine under KDE.

As previously mentioned running with Radeon 3200HD (RS780) and vdpau
libraries installed.

Arthur.




I had one lock-up after installing the latest Linus' git head kernel
with some Radeon-specic updates but did not lock up on a second attempt.

This seems to be an issue related to the graphics card used.

Arthur.



Maybe, but I don't know how it all fits as I'm using Nvidia card and the free driver from the Debian repos..What happens to me is 
I get a Notice that plasma has crashed and sure enough the panel has crashed, I close the the Notice and go back to what I was 
doing and then it will crash again..If I don't acknowledge the Notice the system/computer will Freeze causing Plasma to be useless 
as a system and me doing a Hard-Shutdown..


I'm willing to do testing if someone wants to fix the problem..


I always had bad experience with the free nvidia drivers. I always used the 
drivers from nvidia.

Luc


<>

Re: KDE catastrophe after June 5 dist-upgrade

2016-06-05 Thread Luc Castermans
I did safe-upgrade yesterday, from sid. All works nicely. Many others
reported such also here. I suggest you carefully check if required packages
are installed.

Luc
Op 6 jun. 2016 04:59 schreef "Allen James" :

> Dear maintainers,
>
> I use Debian Testing. Before today, my previous dist-upgrade was on May
> 28, at
> which points all packages were up to date and KDE 5.4 was running smoothly.
> Today (June 5) I again dist-upgrade my laptop and now KDE is very broken.
>
> The following is a list of many of the KDE-related packages upgraded today
> (others not related to KDE/Qt/KF5/etc were removed to the best of my
> ability):
>
> kde-cli-tools kde-cli-tools-data kde-config-cron kde-config-sddm
> kde-style-oxygen-qt5 kded5 kdenetwork-filesharing kdesdk-scripts
> kdesdk-thumbnailers kdevelop kdevelop-data kdevplatform8-libs
> libreoffice-kde
> python-kde4 qml-module-org-kde-draganddrop
> qml-module-org-kde-extensionplugin
> qml-module-org-kde-games-core qml-module-org-kde-kcoreaddons
> qml-module-org-kde-kio qml-module-org-kde-kquickcontrols
> qml-module-org-kde-kquickcontrolsaddons qml-module-org-kde-kwindowsystem
> baloo-kf5  kdegames-card-data-kf5  libkf5activities5  libkf5baloo5
> libkf5balooengine5  libkf5baloowidgets-bin  libkf5baloowidgets5
> libkf5bookmarks-data  libkf5bookmarks5  libkf5completion-data
> libkf5completion5
> libkf5config-bin  libkf5config-data  libkf5configcore5  libkf5configgui5
> libkf5configwidgets-data  libkf5configwidgets5  libkf5declarative-data
> libkf5declarative5  libkf5emoticons-bin  libkf5emoticons-data
> libkf5emoticons5
> libkf5globalaccel-bin  libkf5globalaccel-data  libkf5globalaccel5
> libkf5globalaccelprivate5 libkf5iconthemes-bin libkf5iconthemes-data
> libkf5iconthemes5 libkf5kcmutils-data libkf5kcmutils5
> libkf5kdegamesprivate1
> libkf5kdelibs4support-data libkf5kdelibs4support5 libkf5khtml-bin
> libkf5khtml-data libkf5khtml5 libkf5kiocore5 libkf5kiofilewidgets5
> libkf5kiontlm5 libkf5kiowidgets5 libkf5krosscore5 libkf5krossui5
> libkf5newstuff-data libkf5newstuff5 libkf5notifications-data
> libkf5notifications5 libkf5notifyconfig-data libkf5notifyconfig5
> libkf5package-data libkf5package5 libkf5parts-data libkf5parts-plugins
> libkf5parts5 libkf5people-data libkf5people5 libkf5peoplebackend5
> libkf5peoplewidgets5 libkf5quickaddons5 libkf5service-bin
> libkf5service-data
> libkf5service5 libkf5style5 libkf5su-bin libkf5su-data libkf5su5
> libkf5sysguard-bin libkf5sysguard-data libkf5texteditor5
> libkf5textwidgets-data
> libkf5textwidgets5 libkf5wallet-bin libkf5wallet-data libkf5wallet5
> libkf5webkit5 libkf5xmlgui-bin libkf5xmlgui-data libkf5xmlgui5
> libkf5xmlrpcclient-data libkf5xmlrpcclient5 qtdeclarative5-kf5declarative
> plasma-pa libpoppler-qt4-4 libpoppler-qt5-1 libqt4-dbus libqt4-declarative
> libqt4-designer libqt4-help libqt4-network libqt4-opengl libqt4-qt3support
> libqt4-script libqt4-scripttools libqt4-sql libqt4-sql-mysql
> libqt4-sql-sqlite
> libqt4-svg libqt4-test libqt4-xml libqt4-xmlpatterns libqtcore4 libqtdbus4
> libqtgui4 python-qt4 python-qt4-dbus python-qt4-sql python3-pyqt4
> qtcore4-l10n
> frameworkintegration
>
> After the dist-upgrade I ran apt-get autoremove as I usually do. The
> following
> packages were listed. It seemed strange but I went ahead anyway:
>
> The following packages will be REMOVED:
> accountsservice bluedevil breeze breeze-cursor-theme breeze-icon-theme
> fonts-oxygen ieee-data kde-config-sddm kde-style-breeze
> kde-style-breeze-qt4
> kde-style-oxygen-qt5 kde-style-qtcurve-qt4 kde-style-qtcurve-qt5 khotkeys
> khotkeys-data kinfocenter kmenuedit kscreen ksysguard ksysguard-data
> ksysguardd
> kwin-style-breeze kwin-wayland kwin-wayland-backend-drm kwrited
> libaccountsservice0 libanalitza5abi1 libanalitzagui5abi1
> libanalitzaplot5abi1
> libappstreamqt1 libavcodec-ffmpeg56 libavformat-ffmpeg56
> libavresample-ffmpeg2
> libavutil-ffmpeg54 libcolamd2.9.1 libgif4
> libkf5activitiesexperimentalstats1
> libkf5bluezqt-data libkf5bluezqt6 libkf5emoticons-bin libkf5emoticons-data
> libkf5emoticons5 libkf5kdegames6 libkf5people-data libkf5people5
> libkf5peoplebackend5 libkf5peoplewidgets5 libkf5style5 libkf5sysguard-bin
> libkfontinst5 libkfontinstui5 libksignalplotter7 libokularcore6
> liboxygenstyle5-5 liboxygenstyleconfig5-5 libpackagekitqt5-0 libpoppler57
> libpostproc-ffmpeg53 libpowerdevilcore2 libpowerdevilui5 libqtcurve-utils2
> libquvi-scripts libquvi7 libsuitesparseconfig4.4.6 libswresample-ffmpeg1
> libswscale-ffmpeg3 libxcb-record0 muon-discover muon-notifier muon-updater
> oxygen-sounds plasma-desktop-data plasma-discover plasma-discover-common
> plasma-discover-private plasma-discover-updater powerdevil powerdevil-data
> python3-pycurl python3-pyqt5 python3-software-properties
> qml-module-org-kde-bluezqt qml-module-qt-labs-folderlistmodel
> qml-module-qt-labs-settings qml-module-qtquick-controls-styles-breeze
> qtdeclarative5-kf5declarative sni-qt software-properties-common
> software-properties-kde systemset

Re: KDE catastrophe after June 5 dist-upgrade

2016-06-05 Thread Luc Castermans
In your list I spotted sddm package to be removed. You better install this
first, as this provides the login manager. Luc
Op 6 jun. 2016 07:15 schreef "Luc Castermans" :

> I did safe-upgrade yesterday, from sid. All works nicely. Many others
> reported such also here. I suggest you carefully check if required packages
> are installed.
>
> Luc
> Op 6 jun. 2016 04:59 schreef "Allen James" :
>
>> Dear maintainers,
>>
>> I use Debian Testing. Before today, my previous dist-upgrade was on May
>> 28, at
>> which points all packages were up to date and KDE 5.4 was running
>> smoothly.
>> Today (June 5) I again dist-upgrade my laptop and now KDE is very broken.
>>
>> The following is a list of many of the KDE-related packages upgraded today
>> (others not related to KDE/Qt/KF5/etc were removed to the best of my
>> ability):
>>
>> kde-cli-tools kde-cli-tools-data kde-config-cron kde-config-sddm
>> kde-style-oxygen-qt5 kded5 kdenetwork-filesharing kdesdk-scripts
>> kdesdk-thumbnailers kdevelop kdevelop-data kdevplatform8-libs
>> libreoffice-kde
>> python-kde4 qml-module-org-kde-draganddrop
>> qml-module-org-kde-extensionplugin
>> qml-module-org-kde-games-core qml-module-org-kde-kcoreaddons
>> qml-module-org-kde-kio qml-module-org-kde-kquickcontrols
>> qml-module-org-kde-kquickcontrolsaddons qml-module-org-kde-kwindowsystem
>> baloo-kf5  kdegames-card-data-kf5  libkf5activities5  libkf5baloo5
>> libkf5balooengine5  libkf5baloowidgets-bin  libkf5baloowidgets5
>> libkf5bookmarks-data  libkf5bookmarks5  libkf5completion-data
>> libkf5completion5
>> libkf5config-bin  libkf5config-data  libkf5configcore5  libkf5configgui5
>> libkf5configwidgets-data  libkf5configwidgets5  libkf5declarative-data
>> libkf5declarative5  libkf5emoticons-bin  libkf5emoticons-data
>> libkf5emoticons5
>> libkf5globalaccel-bin  libkf5globalaccel-data  libkf5globalaccel5
>> libkf5globalaccelprivate5 libkf5iconthemes-bin libkf5iconthemes-data
>> libkf5iconthemes5 libkf5kcmutils-data libkf5kcmutils5
>> libkf5kdegamesprivate1
>> libkf5kdelibs4support-data libkf5kdelibs4support5 libkf5khtml-bin
>> libkf5khtml-data libkf5khtml5 libkf5kiocore5 libkf5kiofilewidgets5
>> libkf5kiontlm5 libkf5kiowidgets5 libkf5krosscore5 libkf5krossui5
>> libkf5newstuff-data libkf5newstuff5 libkf5notifications-data
>> libkf5notifications5 libkf5notifyconfig-data libkf5notifyconfig5
>> libkf5package-data libkf5package5 libkf5parts-data libkf5parts-plugins
>> libkf5parts5 libkf5people-data libkf5people5 libkf5peoplebackend5
>> libkf5peoplewidgets5 libkf5quickaddons5 libkf5service-bin
>> libkf5service-data
>> libkf5service5 libkf5style5 libkf5su-bin libkf5su-data libkf5su5
>> libkf5sysguard-bin libkf5sysguard-data libkf5texteditor5
>> libkf5textwidgets-data
>> libkf5textwidgets5 libkf5wallet-bin libkf5wallet-data libkf5wallet5
>> libkf5webkit5 libkf5xmlgui-bin libkf5xmlgui-data libkf5xmlgui5
>> libkf5xmlrpcclient-data libkf5xmlrpcclient5 qtdeclarative5-kf5declarative
>> plasma-pa libpoppler-qt4-4 libpoppler-qt5-1 libqt4-dbus libqt4-declarative
>> libqt4-designer libqt4-help libqt4-network libqt4-opengl libqt4-qt3support
>> libqt4-script libqt4-scripttools libqt4-sql libqt4-sql-mysql
>> libqt4-sql-sqlite
>> libqt4-svg libqt4-test libqt4-xml libqt4-xmlpatterns libqtcore4 libqtdbus4
>> libqtgui4 python-qt4 python-qt4-dbus python-qt4-sql python3-pyqt4
>> qtcore4-l10n
>> frameworkintegration
>>
>> After the dist-upgrade I ran apt-get autoremove as I usually do. The
>> following
>> packages were listed. It seemed strange but I went ahead anyway:
>>
>> The following packages will be REMOVED:
>> accountsservice bluedevil breeze breeze-cursor-theme breeze-icon-theme
>> fonts-oxygen ieee-data kde-config-sddm kde-style-breeze
>> kde-style-breeze-qt4
>> kde-style-oxygen-qt5 kde-style-qtcurve-qt4 kde-style-qtcurve-qt5 khotkeys
>> khotkeys-data kinfocenter kmenuedit kscreen ksysguard ksysguard-data
>> ksysguardd
>> kwin-style-breeze kwin-wayland kwin-wayland-backend-drm kwrited
>> libaccountsservice0 libanalitza5abi1 libanalitzagui5abi1
>> libanalitzaplot5abi1
>> libappstreamqt1 libavcodec-ffmpeg56 libavformat-ffmpeg56
>> libavresample-ffmpeg2
>> libavutil-ffmpeg54 libcolamd2.9.1 libgif4
>> libkf5activitiesexperimentalstats1
>> libkf5bluezqt-data libkf5bluezqt6 libkf5emoticons-bin libkf5emoticons-data
>> libkf5emoticons5 libkf5kdegames6 libkf5people-data libkf5people5
>> libkf5peoplebackend5 libkf5peoplewidgets5 libkf5style5 libkf5sysguard-bin
>> libkfontinst5 libkfontinstui5 libksig

kde 5.7

2016-07-06 Thread Luc Castermans

dear, how can I find out about plans to further absorb KDE release like 5.7?

This list or other media.


thx


Luc

<>

Re: kde 5.7

2016-07-08 Thread Luc Castermans
Great! I'll install once available. Luc

Op 8 jul. 2016 16:38 schreef "Martin Steigerwald" :

> Am Freitag, 8. Juli 2016, 16:23:19 CEST schrieb Martin Steigerwald:
> > Am Mittwoch, 6. Juli 2016, 19:07:02 CEST schrieb Luc Castermans:
> > > dear, how can I find out about plans to further absorb KDE release like
> > > 5.7?
> > I think I just saw that Maxy uploaded the first 5.7 package: ksshaskpass
>
> Yep, further packages coming. Maxy started uploading Plasma 5.7.
>
> --
> Martin
>
>


Re: Digikam 5 and video playback / video thumbnails

2016-08-11 Thread Luc Castermans
hi, how did you install it? I have testin/sid installed. When I try to
install it aptitude proposes to remove kde-full and few other packages.
I.e. dependencies appear to prevent installing.

thanks, Luc

Op do 11 aug. 2016 16:28 schreef Martin Steigerwald :

> Hello Pino, hello Steve, hello everyone,
>
> I installed digikam, kipi plugins from experimental. I added ffmpegthumbs
> for
> thumbnails. I also added mplayerthumbs later just in case.
>
> I was surprised at being greeted by the migration assistent, but then just
> went through it. (I read the mail you linked here in the other thread,
> Pino.)
>
> It basically appears to work.
>
> Yet I do not see video thumbnails. And clicking on a video does not produce
> any result.
>
> What may I be missing?
>
> I am willing to provide a bug report, but first want to check in whether
> someone has an idea about it.
>
> # apt-show-versions | egrep "digikam|kipi|thumbs|ffmpeg|^mplayer" | grep -v
> "i386"
> digikam:amd64/experimental 4:5.0.0-1 uptodate
> digikam-data:all/experimental 4:5.0.0-1 uptodate
> digikam-doc:all/sid 4:4.14.0-5 uptodate
> digikam-private-libs:amd64/experimental 4:5.0.0-1 uptodate
> ffmpeg:amd64/sid 7:3.1.2-1 uptodate
> ffmpegthumbnailer:amd64/sid 2.1.1-0.1+b2 uptodate
> ffmpegthumbs:amd64/sid 4:16.04.2-1 uptodate
> kipi-plugins:amd64/experimental 4:5.0.0-1 uptodate
> kipi-plugins-common:all/experimental 4:5.0.0-1 uptodate
> libffmpegthumbnailer4v5:amd64/sid 2.1.1-0.1+b2 uptodate
> libkf5kipi-bin:amd64/sid 16.04.0-2 uptodate
> libkf5kipi-data:all/sid 16.04.0-2 uptodate
> libkf5kipi31.0.0:amd64/sid 16.04.0-2 uptodate
> libxine2-ffmpeg:amd64/sid 1.2.6-1.1+b1 uptodate
> mplayer:amd64/sid 2:1.3.0-3 uptodate
> mplayerthumbs:amd64/sid 4:15.08.3-2 uptodate
>
> (Just upgrading digikam-doc now as well.)
>
> Thanks,
> --
> Martin
>
>


digikam 5: then ksnapshot is removed

2016-08-13 Thread Luc Castermans

Hi,

Indeed installing Digikam 5 forces to remove kdegraphics package. I think

I can miss a few, except for ksnapshot. Is this a wrong dependency?

So I better wait?

Luc


=

root@canne:~# aptitude install digikam -t sid
De volgende NIEUWE pakketten zullen worden geïnstalleerd:
  libkf5kipi-bin{a} libkf5kipi-data{ab} libkf5kipi31.0.0{a}
De volgende pakketten zullen worden VERWIJDERD:
  libpgf6{u} libsqlite0{u}
De volgende pakketten zullen worden opgewaardeerd:
  digikam digikam-data digikam-private-libs
3 pakketten opwaarderen, 3 nieuwe installeren, 2 verwijderen en 187 niet 
opwaarderen.
Heb 21,1 MB archieven nodig. Na uitpakken zal 10,5 MB worden gebruikt.
De volgende pakketten hebben niet-voldane vereisten:
 libkf5kipi-data : Breekt: libkipi-data maar 4:15.08.3-2 is geïnstalleerd
 kipi-plugins : Vereisten: digikam-private-libs (= 4:4.14.0-5+b1) maar 
4:5.1.0-1 zal geïnstalleerd worden
open: 44; gesloten: 837; uitgesteld: 20; conflicten: 39 ODe volgende acties 
zullen deze vereisten oplossen:

 Verwijder de volgende pakketten:
1) kde-full [5:90 (now, testing, unstable)]
2) kde-standard [5:90 (now, testing, unstable)]
3) kdegraphics [4:4.12+5.90 (now, testing, unstable)]
4) ksnapshot [4:15.08.0-1 (now, testing, unstable)]
5) libkipi-data [4:15.08.3-2 (now, testing, unstable)]
6) libkipi11 [4:15.08.3-2 (now, testing, unstable)]

 Doe opwaardering van volgende pakketten:
7) kipi-plugins [4:4.14.0-5+b1 (now, testing) -> 4:5.1.0-1 (unstable)]
8) kipi-plugins-common [4:4.14.0-5 (now, testing) -> 4:5.1.0-1 (unstable)]



Deze oplossing aanvaarden? [Y/n/q/?]

<>

Re: digikam 5: then ksnapshot is removed

2016-08-13 Thread Luc Castermans

Op 13-08-16 om 21:50 schreef Brad Rogers:

On Sat, 13 Aug 2016 21:08:08 +0200
Diederik de Haas  wrote:

Hello Diederik,


You can use kde-spectacle which is (apparently) the successor to
ksnapshot

It does appear more capable than KSnapShot.  For a start, it's aware of
the possibility that there may be more than one monitor, and that the
current desktop can span them all.



Great guys,

I installed Digikam 5. It works, incl. panorama making, which did not work 
anymore in 4.14 version.

As previously reported here, movie viewing does not work.

Also kde-spectacle is an improved over kshapshot.


Great,


Luc

<>

Re: digikam 5: then ksnapshot is removed

2016-08-13 Thread Luc Castermans

Op 14-08-16 om 08:19 schreef Luc Castermans:

Op 13-08-16 om 21:50 schreef Brad Rogers:

On Sat, 13 Aug 2016 21:08:08 +0200
Diederik de Haas  wrote:

Hello Diederik,


You can use kde-spectacle which is (apparently) the successor to
ksnapshot

It does appear more capable than KSnapShot.  For a start, it's aware of
the possibility that there may be more than one monitor, and that the
current desktop can span them all.



Great guys,

I installed Digikam 5. It works, incl. panorama making, which did not work 
anymore in 4.14 version.

As previously reported here, movie viewing does not work.

Also kde-spectacle is an improved over kshapshot.



 and I had to hand-install okular

(guess this was due to kde-graphics dependency)

Luc


<>

Re: Plasma 5.7.4 in unstable now installable

2016-08-31 Thread Luc Castermans
I updated last night from 'sid', all looks fine. Thanks!!
 (plasma 5.7.4, libkf5 5.25.0, kde 16.08)

Luc

2016-08-31 22:22 GMT+02:00 Martin Steigerwald :

> Am Mittwoch, 31. August 2016, 22:14:16 CEST schrieb Martin Steigerwald:
> […]
> > plasma-workspace + plasma-desktop at 5.7.4. New session startup splash
> > screen.
> >
> > All seems fine so far.
> >
> > Activitymanager restored that I had some windows on two activities on
> > session startup. I think previous versions never did this.
>
> systemsettings seems to have that new ordering into groups by Visual Design
> Group (VDG) I read about in several blog posts. A user on #debian-kde
> reported
> issues with missing libraries there. For me it appears to work.
>
> Thanks,
> --
> Martin
>
>


-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


KDE Frameworks 5.26.0 from SID installed

2016-10-02 Thread Luc Castermans

Hi,

Just to let you  know I installed succesfully from SID: KDE Frameworks 5.26.0


thx!!

<>

Re: KDE Frameworks 5.26.0 from SID installed

2016-10-06 Thread Luc Castermans
Hi Holger, next to coffee maybe also Plasma 5.8 :=)

2016-10-06 10:59 GMT+02:00 Holger Schramm :

> Am 03.10.2016 um 12:14 schrieb Martin Steigerwald:
> > Am Sonntag, 2. Oktober 2016, 11:17:43 CEST schrieb Luc Castermans:
> >> Hi,
> >>
> >> Just to let you  know I installed succesfully from SID: KDE Frameworks
> >> 5.26.0
> >
> > I did so as well.
> >
> > I don´t have any issues with it so far.
>
> Me too. No problems with multi montitors and sddm.
>
> @Martin: sry for the direct mail, I hit the wrong button :( Need more
> coffee.
> --
> Holger
>
>


-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


plasma 5.8 upgrade - white desktop i.s.o. sddm login

2016-10-09 Thread Luc Castermans
So I upgraded to plasma 5.0 before the uploads were completed.
This brought my setup into problems.

Problem: After boot the computer produces only a white screen.

>From another computer, using SSH, I can login in to the computer (as
'root').  I do not find error messages in /var/log. After  "startx" I get a
KDE desktop.

Using this shell login I did a full upgrade to plasma 5.8 (SID).

Could I still be missing packages? How to debug this?

thx for any pointers.

-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


Re: plasma 5.8 upgrade - white desktop i.s.o. sddm login

2016-10-09 Thread Luc Castermans
Hi,   I have:

root@canne:~# dpkg -l  | fgrep kwin
ii  kde-window-manager
4:5.8.0-1all  transitional package for
kwin-x11
ii  kwin-common
4:5.8.0-1amd64KDE window manager,
common files
ii  kwin-data
4:5.8.0-1all  KDE window manager data
files
ii  kwin-style-breeze
4:5.8.0-1amd64KWin Breeze Style
ii  kwin-style-qtcurve
1.8.14-3+b2  amd64QtCurve window decoration
for KWin
ii  kwin-x11
4:5.8.0-1amd64KDE window manager, X11
version
ii  libkwin4-effect-builtins1
4:5.8.0-1amd64KDE window manager effect
builtins library
ii  libkwineffects9
4:5.8.0-1amd64KDE window manager
effects library
ii  libkwinglutils9
4:5.8.0-1amd64KDE window manager gl
utils library
ii  libkwinxrenderutils9
4:5.8.0-1amd64KDE window manager render
utils library
ii  qml-module-org-kde-kwindowsystem:amd64
5.26.0-1 amd64provides integration of
QML and KDE frameworks - kwindowsystem
root@canne:~#

Don't think missing kwin is the problem. I notice an awfull lot, 1048
kworker processes running.
is this normal?

Luc


2016-10-09 17:08 GMT+02:00 Diederik de Haas :

> On zondag 9 oktober 2016 16:37:33 CEST Luc Castermans wrote:
> > Could I still be missing packages?
>
> At what version is kwin? That package had to go through NEW and was
> therefor
> added to the archives later then the others, but it is available now.
>
> If you didn't use 'aptitude safe-upgrade', you may want to do so in the
> future
> as it would've hold of upgrades which weren't ready ;-)




-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


Re: plasma 5.8 upgrade - white desktop i.s.o. sddm login

2016-10-09 Thread Luc Castermans
Hi, in addition.  When I stop sddm, the screen turns black, when I start
sddm the screen becomes white,
with below status message. Looks normal to me, but not as the screen shown
only white.

===

root@canne:~# service sddm start
root@canne:~# service sddm status
● sddm.service - Simple Desktop Display Manager
   Loaded: loaded (/lib/systemd/system/sddm.service; enabled; vendor
preset: enabled)
   Active: active (running) since zo 2016-10-09 21:54:39 CEST; 32s ago
 Docs: man:sddm(1)
   man:sddm.conf(5)
  Process: 4518 ExecStartPre=/bin/sh -c [ "$(cat
/etc/X11/default-display-manager 2>/dev/null)" = "/usr/bin/sddm" ]
(code=exited, status=0/SUCCESS)
 Main PID: 4522 (sddm)
Tasks: 4 (limit: 4915)
   CGroup: /system.slice/sddm.service
   ├─4522 /usr/bin/sddm
   └─4524 /usr/lib/xorg/Xorg -nolisten tcp -auth
/var/run/sddm/{5cf693b5-a283-442f-9e3a-f3fb7aefa22d} -background none
-noreset -displayfd 18 vt7

okt 09 21:54:39 canne sddm[4522]: Display server started.
okt 09 21:54:39 canne sddm[4522]: Socket server starting...
okt 09 21:54:39 canne sddm[4522]: Socket server started.
okt 09 21:54:39 canne sddm[4522]: Greeter starting...
okt 09 21:54:39 canne sddm[4522]: Adding cookie to
"/var/run/sddm/{5cf693b5-a283-442f-9e3a-f3fb7aefa22d}"
okt 09 21:54:39 canne sddm-helper[4530]: [PAM] Starting...
okt 09 21:54:39 canne sddm-helper[4530]: [PAM] Authenticating...
okt 09 21:54:39 canne sddm-helper[4530]: [PAM] returning.
okt 09 21:54:39 canne sddm[4522]: Greeter session started successfully
okt 09 21:54:40 canne sddm[4522]: Message received from greeter: Connect
root@canne:~#


2016-10-09 21:50 GMT+02:00 Luc Castermans :

> Hi,   I have:
>
> root@canne:~# dpkg -l  | fgrep kwin
> ii  kde-window-manager
> 4:5.8.0-1all  transitional package
> for kwin-x11
> ii  kwin-common
> 4:5.8.0-1amd64KDE window manager,
> common files
> ii  kwin-data
> 4:5.8.0-1all  KDE window manager data
> files
> ii  kwin-style-breeze
> 4:5.8.0-1amd64KWin Breeze Style
> ii  kwin-style-qtcurve
> 1.8.14-3+b2  amd64QtCurve window
> decoration for KWin
> ii  kwin-x11
> 4:5.8.0-1amd64KDE window manager, X11
> version
> ii  libkwin4-effect-builtins1
> 4:5.8.0-1amd64KDE window manager
> effect builtins library
> ii  libkwineffects9
> 4:5.8.0-1amd64KDE window manager
> effects library
> ii  libkwinglutils9
> 4:5.8.0-1amd64KDE window manager gl
> utils library
> ii  libkwinxrenderutils9
> 4:5.8.0-1amd64KDE window manager
> render utils library
> ii  qml-module-org-kde-kwindowsystem:amd64
> 5.26.0-1 amd64provides integration of
> QML and KDE frameworks - kwindowsystem
> root@canne:~#
>
> Don't think missing kwin is the problem. I notice an awfull lot, 1048
> kworker processes running.
> is this normal?
>
> Luc
>
>
> 2016-10-09 17:08 GMT+02:00 Diederik de Haas :
>
>> On zondag 9 oktober 2016 16:37:33 CEST Luc Castermans wrote:
>> > Could I still be missing packages?
>>
>> At what version is kwin? That package had to go through NEW and was
>> therefor
>> added to the archives later then the others, but it is available now.
>>
>> If you didn't use 'aptitude safe-upgrade', you may want to do so in the
>> future
>> as it would've hold of upgrades which weren't ready ;-)
>
>
>
>
> --
> Luc Castermans
> mailto:luc.casterm...@gmail.com
>



-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


Re: plasma 5.8 upgrade - white desktop i.s.o. sddm login

2016-10-09 Thread Luc Castermans

Op 09-10-16 om 21:59 schreef Diederik de Haas:

On zondag 9 oktober 2016 21:50:27 CEST Luc Castermans wrote:

Don't think missing kwin is the problem.

Agreed.


I notice an awfull lot, 1048 kworker processes running. is this normal?

I have 21, so 1048 seems (a bit) excessive.


yep.

But when I:

stop sddm   (via ssh PC2)

give ´startx´ (via ssh PC2), then I get the KDE desktop of root on PC1.

In this KDE desktop I do a ¨ log-out¨, then I get into to a bash shell on PC1.

Now I login as normal user and do a ´ startx´   and get nicely in my KDE 
desktop.


Something in the boot to X and/or kwin/sddm is wrong.


thx for any help.


Luc






<>

Re: plasma 5.8 upgrade - white desktop i.s.o. sddm login

2016-10-10 Thread Luc Castermans

Op 09-10-16 om 22:17 schreef Luc Castermans:

Op 09-10-16 om 21:59 schreef Diederik de Haas:

On zondag 9 oktober 2016 21:50:27 CEST Luc Castermans wrote:

Don't think missing kwin is the problem.

Agreed.


I notice an awfull lot, 1048 kworker processes running. is this normal?

I have 21, so 1048 seems (a bit) excessive.


yep.

But when I:

stop sddm   (via ssh PC2)

give ´startx´ (via ssh PC2), then I get the KDE desktop of root on PC1.

In this KDE desktop I do a ¨ log-out¨, then I get into to a bash shell on PC1.

Now I login as normal user and do a ´ startx´   and get nicely in my KDE 
desktop.


Something in the boot to X and/or kwin/sddm is wrong.



after an aptitude purge sddm, and installing several sddm-theme´s all is 
working again.
(Debian stretch/sid, plasma 5.8, KDE Frameworks 5.26.0)

thanks!!

Luc


<>

Re: KF 5.27 and Plasma 5.8.1 coming

2016-10-19 Thread Luc Castermans

Op 18-10-16 om 22:59 schreef Martin Steigerwald:

Am Dienstag, 18. Oktober 2016, 17:25:44 CEST schrieb inkbottle:

No problem here neither so far:
"Testing" box with, this time, additional debian-qt-kde sid packages with
version 5.8.1-1 or 5.27.0-1

Applications 16.08.2 now also coming in.


Indeed, just did ¨aptitude safe-upgrade -t sid¨; 79 packages  are in.

luc@canne:~$ dpkg -l | fgrep 16.08.2 | wc -l
79

Thanks



<>

Re: KF 5.27 and Plasma 5.8.1 coming

2016-10-19 Thread Luc Castermans
I love it !

2016-10-19 22:27 GMT+02:00 Martin Steigerwald :

> Am Mittwoch, 19. Oktober 2016, 18:55:35 CEST schrieb Luc Castermans:
> > Op 18-10-16 om 22:59 schreef Martin Steigerwald:
> > > Am Dienstag, 18. Oktober 2016, 17:25:44 CEST schrieb inkbottle:
> > >> No problem here neither so far:
> > >> "Testing" box with, this time, additional debian-qt-kde sid packages
> with
> > >> version 5.8.1-1 or 5.27.0-1
> > >
> > > Applications 16.08.2 now also coming in.
> >
> > Indeed, just did ¨aptitude safe-upgrade -t sid¨; 79 packages  are in.
> >
> > luc@canne:~$ dpkg -l | fgrep 16.08.2 | wc -l
> > 79
>
> Now Plasma 5.8.2.
>
> Maxy is uploading new packages almost faster than I can install them :)
>
> --
> Martin
>
>


-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


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

2016-11-07 Thread Luc Castermans

Dear,

Yesterday morning (Nov 6) my screen stayed close to black, I did not read this 
mail thread before.

I reverted by installing several Stretch packages.

I just now re-installed all from Sid.

All working fine.

Many thanks indeed for quick actions AND clear communication via this channel.

Luc


<>

KDE Frameworks 5.28.0

2016-11-20 Thread Luc Castermans

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

<>

Re: KDE Frameworks 5.28.0

2016-11-20 Thread Luc Castermans

Op 20-11-16 om 10:15 schreef Andrey Rahmatullin:

On Sun, Nov 20, 2016 at 11:11:12AM +0200, David Baron wrote:

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!

It's the same as `apt upgrade`.


in contrast to ¨ aptitude dist-upgrade; which will upgrade all

Luc

<>

libreoffice-kde package qt4 -> qt5

2017-02-27 Thread Luc Castermans
Dear,

The libreoffice-kde package is built upon qt4, but deserves a port to
qt5/plasma.
Can you advice how I can help to give it attention and support?

Thanks

-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


Re: Qt 5.7.1 => 5.9.1

2017-08-27 Thread Luc Castermans

Op 27-08-17 om 23:05 schreef laurent Trinques:

Le dimanche 27 août 2017, 23:11:17 CEST Boris Pek a écrit :

Hi,
  


Hello.

Qt 5.9.1 hits unstable.

Please be careful to wait till its complete.

  Even though
   and
  
  still says "partial", it appears those packages do exist for AMD64,
  and upgrade seems possible, as of right now...
  Chris


Except for some KDE stuff like akonadi, so depending on what you have
installed apt might want to remove stuff.

We are working on it.
  
Is there any progress with qtcreator package? This is the only obstacle to

updating my system now. But I have not found bug reports related to Qt
5.7.1 => 5.9.1 transition for it.
  
Best regards,

Boris
  

Hi,
for the moment I have installed upstream qtcreator package(is easy and
quickly) and updated to Qt 5.9.1.

Best regards,
Laurent

.



After upgrading I found the package libqt5clucene5   to be at version 5.7.1-1 
still.
Should this be upgraded as well?

And then yes of course  a correct version of qml-module-org-kde-analitza   
should become available.

thx

Luc


<>

Re: Qt 5.7.1 => 5.9.1

2017-08-28 Thread Luc Castermans
Thanks Martin, so I removed this package.

Regards, Luc

Op 28 aug. 2017 09:17 schreef "Martin Steigerwald" :

> Luc Castermans - 28.08.17, 08:40:
> > > Hi,
> > > for the moment I have installed upstream qtcreator package(is easy and
> > > quickly) and updated to Qt 5.9.1.
> […]
> > After upgrading I found the package libqt5clucene5   to be at version
> > 5.7.1-1 still. Should this be upgraded as well?
> >
> > And then yes of course  a correct version of qml-module-org-kde-analitza
> > should become available.
>
> I just removed it as nothing on my system depended on it.
>
> Additionally the package is not in unstable anymore, so I bet it is not
> needed
> anymore.
>
> Thanks,
> --
> Martin
>
>


Re: Plasma 5.10 and KF 5.37

2017-08-29 Thread Luc Castermans

Op 29-08-17 om 08:55 schreef Martin Steigerwald:

Hi Libor.

Libor Klepáč - 29.08.17, 08:39:

just upgrade to qt5.9, frameworks 5.37 and plasma 5.10,
upgrade was smooth, no problem.

Logged in again, everything seem to be ok so far.
Kde window manager is still in 5.8.7 version

Lol, thanks for feedback, Libor.

I feel tempted :)

Maybe I wait a day or two whether you encounter a show stopper.

Thanks,


I could not resist: aptitude install plasma-framework  -t experimental

All looks OK for me

Many thanks to the team !!!


Luc Castermans

<>

Re: Plasma 5.10 and KF 5.37

2017-08-29 Thread Luc Castermans

Op 29-08-17 om 09:57 schreef Martin Steigerwald:

Martin Steigerwald - 29.08.17, 08:55:

Libor Klepáč - 29.08.17, 08:39:

just upgrade to qt5.9, frameworks 5.37 and plasma 5.10,
upgrade was smooth, no problem.

Logged in again, everything seem to be ok so far.
Kde window manager is still in 5.8.7 version

Lol, thanks for feedback, Libor.

I feel tempted :)

Well… that was easy enough.

So far so good.

KF 5.37 + Plasma 5.10.5. For plasma also watch out for "5.8.5" and "5.8.6"
packages like plasma-nm.

aptitude install -t experimental  plasma-nm

yields:

root@canne:~# dpkg -l | fgrep plasma-nm
ii  plasma-nm 4:5.10.5-1   amd64    Plasma5 
networkmanager library.
root@canne:~#



<>

Re: Plasma 5.10 and KF 5.37

2017-08-29 Thread Luc Castermans

Op 29-08-17 om 17:48 schreef Martin Steigerwald:

Luc Castermans - 29.08.17, 10:02:

KF 5.37 + Plasma 5.10.5. For plasma also watch out for "5.8.5" and "5.8.6"
packages like plasma-nm.

aptitude install -t experimental  plasma-nm

yields:

root@canne:~# dpkg -l | fgrep plasma-nm
ii  plasma-nm 4:5.10.5-1   amd64Plasma5
networkmanager library. root@canne:~#

And actually quite some goodness like a revamped System settings module for
connections. :)

I may review the official release videos for new features. Or device to let
myself be surprised whenever I find something.

Thanks,


Thx for hint! So I now upgraded from experimental to below. Luc

luc@canne:~$ dpkg -l | fgrep plasma
ii  kde-plasma-desktop 5:92 amd64    KDE 
Plasma Desktop and minimal set of applications
ii  kdeplasma-addons-data 4:5.10.5-1   all  
locale files for kdeplasma-addons
ii  libkdeclarative5 4:4.14.35-1  amd64    
declarative library for plasma
ii  libkf5plasma5:amd64 5.37.0-1 amd64    
Plasma Runtime components
ii  libkf5plasmaquick5:amd64 5.37.0-1 amd64    
Plasma Runtime components
ii  libplasma-geolocation-interface5 4:5.10.5-1   amd64 
   Plasma Workspace for KF5 library
ii  libplasma3 4:4.14.35-1  amd64    Plasma Library 
for the KDE Platform
ii  plasma-dataengines-addons 4:5.10.5-1   amd64    
additional data engines for Plasma
ii  plasma-desktop 4:5.10.5-1   amd64    Tools and 
widgets for the desktop
ii  plasma-desktop-data 4:5.10.5-1   all  Tools 
and widgets for the desktop data files
ii  plasma-discover 5.10.5-1 amd64    Discover 
software management suite
ii  plasma-discover-common 5.10.5-1 all  
Discover software manager suite (common data files)
ii  plasma-framework 5.37.0-1 amd64    Plasma 
Runtime components
ii  plasma-integration 5.10.5-1 amd64    Qt 
Platform Theme integration plugins for KDE Plasma
ii  plasma-nm 4:5.10.5-1   amd64    Plasma5 
networkmanager library.
ii  plasma-pa 4:5.10.5-1   amd64    Plasma 5 Volume 
controller
ii  plasma-runners-addons 4:5.10.5-1   amd64    
additional runners for Plasma 5 and Krunner
ii  plasma-scriptengine-javascript 4:16.08.3-2  amd64   
 JavaScript script engine for Plasma
ii  plasma-wallpapers-addons 4:5.10.5-1   amd64    
additional wallpaper plugins for Plasma 5
ii  plasma-widgets-addons 4:5.10.5-1   amd64    
additional widgets for Plasma 5
ii  plasma-workspace 4:5.10.5-1   amd64    Plasma 
Workspace for KF5
luc@canne:~

<>

Re: Qt 5.7.1 => 5.9.1

2017-08-30 Thread Luc Castermans

Op 30-08-17 om 11:55 schreef Boris Pek:

Hi,
> Just did a safe-upgrade. Everything seems to be working ok (though something
> is a little slow with Chrome unstable). The only issue I've noticed is widget
> style is stuck on Breeze. Selecting any other styles seems to not be
> respected.
I may add that usage of XDG_CURRENT_DESKTOP environment variable is broken now
in KDE applications from Sid, and because of it they look very ugly when
launched outside plasmashell or via `ssh -X ..`.
I may add that usage of XDG_CURRENT_DESKTOP environment variable is broken
now in KDE applications from Sid, and because of it they look very ugly when
launched outside plasmashell or via `ssh -X ..`.
For example, dolphin lacks all file icons and icons at toolbar and menus.
Plus it uses some strange theme (not breeze).


Boris,

Dolpin looks normal in my install.

Luc
<>

Re: Plasma 5.10

2017-09-02 Thread Luc Castermans

Dear,

After but also before upgrading to Plasma 5.10 I mostly need to login 2 twice as after the first login I get windows without 
decorations. I think KWin is not running then ?

Anyway after 2nd login it is always ok.

I find below in my .xsession-errors file, does this reveal any issue, in which 
other log to look for
the root cause ?

Luc

===

luc@canne:~$ tail .xsession-errors
networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property 
"S390Subchannels"

modemmanager-qt: Failed enumerating MM objects: 
"org.freedesktop.DBus.Error.ServiceUnknown"
 "The name org.freedesktop.ModemManager1 was not provided by any .service files"
kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried 
("/home/luc/.local/share", "/usr/share", "/usr/local/share")
kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried 
("/home/luc/.local/share", "/usr/share", "/usr/local/share")
kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried 
("/home/luc/.local/share", "/usr/share", "/usr/local/share")
kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried 
("/home/luc/.local/share", "/usr/share", "/usr/local/share")

trying to show an empty dialog
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:147:19: QML Loader: Binding loop detected for 
property "height"
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:147:19: QML Loader: Binding loop detected for 
property "height"

luc@canne:~$ ls -l --si .xsession-errors
-rw--- 1 luc users 17G sep  2 15:40 .xsession-errors
luc@canne:~$
<>

Re: Plasma 5.10 in Testing?

2017-10-12 Thread Luc Castermans
Dear,

On " ...experiencing graphic glitches in Testing"
since a while I see irregular glitches on my screen indeed. I already
suspected by GPU or graphic driver,
but is it a KDE component?

Regards, Luc


2017-10-12 12:31 GMT+02:00 devfra :

> Hi!
>
> Can someone give us some update about the migration of Plasma 5.10 in
> Testing
> It started about a month ago but there are components still blocked in Sid,
> such as kwin [1] and plasma-workspace [2].
>
> Thank you!
>
> PS: Anyone experiencing graphic glitches in Testing since this migration
> started? I have to restart X at least once a day and it is becoming
> annoying.
>
> [1] https://packages.qa.debian.org/k/kwin.html
> [2] https://packages.qa.debian.org/p/plasma-workspace.html
>
>


-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


Re: Plasma 5.10 in Testing?

2017-10-12 Thread Luc Castermans

Dear Libor

After below I see little improvement, but issue is not solved fully.
I never enabled GPU accel in Firefox.

My GPU:
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Richland [Radeon HD 8670D]


Luc

Op 12-10-17 om 13:26 schreef Libor Klepáč:

Hi,
I see those sometimes, starting few minutes after resume.
It's fixable by `kquitapp plasmashell` & run it again from krunner.

I don't know when it started, i have to candidates:
1) after upgrading to Plasma 5.10
2) after enabling GPU accel in firefox

My GPU is
VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics
Controller (rev 0b)

BTW: is it safe to upgrade to latest MESA, pulling in libegl1? Last time i
tried, it broke GPU acceleration and also video acceleration. There are still
some bug reports opened againts MESA.

Libor



Dear,

On " ...experiencing graphic glitches in Testing"since a while I see
irregular glitches on my screen indeed. I already suspected by GPU or
graphic driver, but is it a KDE component?








2017-10-12 12:31 GMT+02:00 devfra :


Hi!

Can someone give us some update about the migration of Plasma 5.10 in
TestingIt started about a month ago but there are components still blocked
in Sid,such as kwin [1] and plasma-workspace [2].

Thank you!

PS: Anyone experiencing graphic glitches in Testing since this
migrationstarted? I have to restart X at least once a day and it is
becoming annoying.

[1] https://packages.qa.debian.org/k/kwin.html[2]
https://packages.qa.debian.org/p/plasma-workspace.html[3]



Luc Castermansmailto:luc.casterm...@gmail.com[4]




[1] mailto:devfra_...@inventati.org
[2] https://packages.qa.debian.org/k/kwin.html
[3] https://packages.qa.debian.org/p/plasma-workspace.html
[4] mailto:luc.casterm...@gmail.com



<>

Re: libreoffice-kde package qt4 -> qt5

2017-10-15 Thread Luc Castermans
what to do for the moment?  LibreOffice 5.4.x can only be installed without
libreoffice-kde. Looks ugly. Accept it, right?

Luc

Op 15 okt. 2017 16:04 schreef "Rene Engelhard" :

> Hi,
>
> On Thu, Oct 05, 2017 at 07:38:57PM +0100, Rik Mills wrote:
> > > The libreoffice-kde package is built upon qt4, but deserves a port to
> > > qt5/plasma.
>
> There is no -kde package anymore. (except in stable)
>
> > > Can you advice how I can help to give it attention and support?
> >
> > Porting branch for the VCL to Qt5/KF5 I believe
> >
> > https://cgit.freedesktop.org/libreoffice/core/log/?h=feature/kde5
>
> Jup, that's it. When it'll be ready - no idea. And then there is the
> possible
> "exists but is buggy or has subtle major problems"
> (like gtk3 was at the beginning.)
>
> For more details about what it involves:
>
> https://wiki.documentfoundation.org/Development/GSoC/Ideas#KDE5:_
> port_KDE4_plugin_to_KF5 and
> https://wiki.documentfoundation.org/Development/GSoC/Ideas#KDE4:_
> use_Qt4_widgets_and_abstraction_layer_for_painting_and_event_filtering
>
> Regards,
>
> Rene
>
>


Re: Plasma 5.10 in Testing?

2017-10-22 Thread Luc Castermans

Dear

Today I got rid of the glitches in the screen by selecting
Xrender as Compositor (Systemsettings -> Screen and Monitor) instead of OpenGL 
x.

Does that give a clue to what is wrong?

thx

Luc


Op 12-10-17 om 13:26 schreef Libor Klepáč:

Hi,
I see those sometimes, starting few minutes after resume.
It's fixable by `kquitapp plasmashell` & run it again from krunner.

I don't know when it started, i have to candidates:
1) after upgrading to Plasma 5.10
2) after enabling GPU accel in firefox

My GPU is
VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics
Controller (rev 0b)

BTW: is it safe to upgrade to latest MESA, pulling in libegl1? Last time i
tried, it broke GPU acceleration and also video acceleration. There are still
some bug reports opened againts MESA.

Libor



Dear,

On " ...experiencing graphic glitches in Testing"since a while I see
irregular glitches on my screen indeed. I already suspected by GPU or
graphic driver, but is it a KDE component?








2017-10-12 12:31 GMT+02:00 devfra :


Hi!

Can someone give us some update about the migration of Plasma 5.10 in
TestingIt started about a month ago but there are components still blocked
in Sid,such as kwin [1] and plasma-workspace [2].

Thank you!

PS: Anyone experiencing graphic glitches in Testing since this
migrationstarted? I have to restart X at least once a day and it is
becoming annoying.

[1] https://packages.qa.debian.org/k/kwin.html[2]
https://packages.qa.debian.org/p/plasma-workspace.html[3]



Luc Castermansmailto:luc.casterm...@gmail.com[4]




[1] mailto:devfra_...@inventati.org
[2] https://packages.qa.debian.org/k/kwin.html
[3] https://packages.qa.debian.org/p/plasma-workspace.html
[4] mailto:luc.casterm...@gmail.com



<>

Packaging resources

2020-02-17 Thread Luc Castermans
Hi,

I read many times "the Debian KDE"-packaging team to be short of resources.
Being a KDE-fan I am very much willing to help and started to lean about
Debian packaging.

While I am studying Debian packaging I like to understand why KDE packaging
needs so much effort. For example the LibreOffice package seems almost
instantly available as soon as an up-stream release became available. Does
LibreOffice need less Debian packaging effort?

I do not expect an e-mail thread about this, maybe I could meet with a
knowledgeable DD on this, either F2F (I live in South of Netherlands) or
virtual.

Regards

-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


Re: Packaging resources

2020-02-25 Thread Luc Castermans
Hi Sandro,

I started my question from pure engineering background and interest, as I
like to understand the situation.

Your answer triggered 2 questions/observations:
- ratio of #packages / #packagers
- what is KDE?

Answering the last: for me KDE is Qt, Frameworks and Plasma.Krita, etc.
I'd exclude from it.
But only Qt, Frameworks and Plasma consists of 300+ packages (I counted
using https://kdesrc-build.kde.org/ ) and
next indeed the ratio #packages / #packagers  compared to other packages
could show the effort involved
for KDE compared to other packages.

Give the above ratio for KDE I wonder if/how further automation could help
to reduce manual effort. Another alternative I could see is to change
upstream to release Debian packages straight away.  But I guess this idea
is not new.

Regards,

Luc




Op ma 24 feb. 2020 om 00:40 schreef Sandro Knauß :

> Hey,
>
> > >  While I am studying Debian packaging I like to understand why KDE
> > >  packaging needs so much effort. For example the LibreOffice
> package
> > >  seems almost instantly available as soon as an up-stream release
> > >  became
> > >  available. Does LibreOffice need less Debian packaging effort?
> > >
> > >Well, it depends. On one side I think kde stuff is composed of many
> > >more
> > >source packages.
> >
> > Yes, having only one source package helps for testbuilding and
> > -installing massively.
> >
> > >On the other side Rene, the LO maintainer, has been doing a
> wonderful
> > >job
> > >in keeping it up to date. Now that this does not means we in the
> Qt/KDE
> >
> > Which also involves following upstream and doing packaging changes as
> > they are needed so I can just prepare an upload when it's time to do so
> > (actcually in many cases for final releases days in advance and at'ed
> > for the release time.) and by following every alpha,beta,rc etc.
>
> Well please don't forget KDE has much more software to package, that have
> very
> different needs and dependency chains. E.g. calligra a complete office
> suite
> (like libreoffice), Kontact an email client (like thunderbird), krita a
> image
> manipulation program (gimp),...
> That's why it is not fair to compare on application against something more
> than 100 applications and the KDE team is round about 5 core people. So
> the
> maintainer/package ratio inside the KDE team is not great.
> Packaging KDE stuff is NOT harder than other packaging, but it is about
> the
> amount to package and the people doing this work that makes it slow.
>
> hefee



-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


Re: KDE Apps 20.04 (and Plasma) for Debian

2020-05-06 Thread Luc Castermans

I just did, no issues seen.

thanks,

Luc

Op 06-05-2020 om 20:40 schreef Marco Valli:

In data martedì 5 maggio 2020 11:37:05 CEST, Sedat Dilek ha scritto:

How is the state of the packages in experimental?

Install kde framework now, before it becomes an issue :-)

regards


--

m.vr.gr.

Luc Castermans
mailto:luc.casterm...@gmail.com



Re: KDE Apps 20.04 (and Plasma) for Debian

2020-05-20 Thread Luc Castermans
Hi Marco

I found at least libkf5akonadicontact5   in experimental. You migh consider
using "-t experimental"   as command.

Luc

Op wo 20 mei 2020 om 13:07 schreef Marco Valli :

> In data mercoledì 6 maggio 2020 19:41:49 CEST, Sandro Knauß ha scritto:
> > But it will become an issue soon, when the first package uses these
> > new versions and apt needs to update.
>
> I just upgraded kdepim from experimental - but this time i had to use
> aptitude, not apt.
>
> Everithing works fine (do you read me?) but kgpg is no more installable.
>
> root@debian:~# apt -t unstable install kgpg
> ---snip---
> I seguenti pacchetti hanno dipendenze non soddisfatte:
>  kgpg : Dipende: libkf5akonadicontact5-19.08
> Dipende: libkf5akonadicore5-19.08
> Dipende: libkf5contacts5-19.08
> E: Impossibile correggere i problemi, ci sono pacchetti danneggiati
> bloccati.
>
> Nice work, Sandro, thanks.
>
> Best regards
>
> --
> Marco Valli
>
>
>

-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


Re: Status of Plasma 5.18/5.19?

2020-06-29 Thread Luc Castermans
Hi,

Right Sander:

Knowing  nothing about the history of the frictions but knowing the needs
and acknowledging each other's skills I regret to read the thread.
Are we past the point of no return or is there an option to go to square
one and restart? What would be needed to do so?
At the same time I note that email is a bad medium for this type of
interaction, sorry for using this medium I am not aware of another one.

Regards

Luc


Op ma 29 jun. 2020 om 13:30 schreef Sander van Grieken <
san...@outrightsolutions.nl>:

> On zondag 28 juni 2020 12:53:15 CEST Martin Steigerwald wrote:
> > Dear Marco, dear Qt/KDE team, dear Norberg, dear community,
> >
> > Marco Valli - 28.06.20, 11:12:03 CEST:
> > > Do you remember debian multimedia of Marillat, another "very
> > > experienced DD"? No? well, even preining in a few years will no
> > > longer remember by anyone. Debian yes.
> >
> > I am not sure whether it makes sense to discuss this out to the end…
>
> Well I'm afraid this topic will keep coming back occasionally until it is
> resolved in one way or the other.
>
> > I really would have preferred for Debian/Kubuntu Qt/KDE team to work
> > together. But if that isn't the case that also is how it is. And it is
> > important to accept that. That does not make anyone who is involved
> > right or wrong either. It is just different approaches. None of them
> > inherently better or worse than the other.
>
> Personally, I find this situation hard to accept. The maintainer team is
> not just a collection of individuals, it's a body that is a gatekeeper of
> the K/Qt stack into Debian. This gatekeeper role doesn't just give its
> members significant power, it also assigns to the team a responsibility to
> keep enabling contributions and improvements to reach the user.
>
> No process can be made totally free of friction. But it is a matter of
> maturity how friction is handled.
>
> --
> Sander
>
>
>
>

-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


Re: Status of Plasma 5.18/5.19?

2020-06-29 Thread Luc Castermans
Yes, a verbal meeting would be good, Jitsi is fine I guess.  I sense that
all subscribe to the need to "get KDE updates as fast as possible into
Debian" . So the starting point is excellent!   Let's discuss if this is
correct during the meeting and depending on how that goes poll about ways
forward.   Normally I would offer you coffee, but this remains virtual for
the moment, :=).

Luc

Op ma 29 jun. 2020 om 14:23 schreef Martin Steigerwald :

> Hi Luc.
>
> Luc Castermans - 29.06.20, 13:52:39 CEST:
> > Are we past the point of no return or is there an option to go to
> > square one and restart? What would be needed to do so?
>
> I have no idea. Actually I do not really understand the conflict.
>
> However…
>
> > At the same time I note that email is a bad medium for this type of
> > interaction, sorry for using this medium I am not aware of another
> > one.
>
> I am willing to offer moderation to find a solution in case both parties
> would like to have a go at finding one. We could find a Jitsi or
> BigBlueButton instance to do this. I know several instances that could
> be used.
>
> Disclaimer: I worked with Debian/Kubuntu Qt/KDE team, on some bug
> triaging or regarding providing information here. And I have no
> intention to change that at the moment. So I may be biased and gladly
> let a less likely to be biased person offer to do the job. That written,
> I learned a lot about ways to communicate that can help to find
> resolutions to conflicts and allow everyone to feel accepted as a person.
>
> Best,
> --
> Martin
>
>
>

-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


Re: Status of Plasma 5.18/5.19?

2020-07-01 Thread Luc Castermans

hi Shmerl

When I asked similar a while ago my conclusion was the amount of work, 
hundreds of packages, on one side and the amount of packagers on the 
other side. And of course disagreements in this case make the effective 
packaging capacity even smaller.


Luc


Op 01-07-2020 om 22:03 schreef Shmerl:
> Debian Sid is still on Plasma 5.17, meanwhile 5.18 LTS and 5.19 have 
already

> been released with 5.20 around the corner
> ...
> What is the status on this now?

Did you actually find the answer to your question? From this whole 
thread, I still don't understand

why is Plasma still outdated in Debian testing / unstable.

All I got was that there was some disagreement and packaging help was 
rejected.
But that doesn't explain what the disagreement was and why Plasma 
wasn't updated in

such a long time either way.

There must be some blockers or issues obviously that prevent it. Can 
anyone please elaborate

on it for the benefit of those who are reading it?

Thanks!

Shmerl.


--

m.vr.gr.

Luc Castermans
mailto:luc.casterm...@gmail.com



Re: Status of Plasma 5.18/5.19?

2020-07-05 Thread Luc Castermans
Hi,

I am slowly learning Debian packaging myself.  Also I tried to compile KDE
myself, while this is not 100% successful it learned my how big KDE is.
>From the discussions in this thread, once I asked the question also, it
became clear to me that having a small team on one end and a huge amount of
packages on the other side will lead to long throughput times in bringing
upstream changes to Debian packages. Automation and working together are
key-words, (the only?) in shortening the throughput times.

I do not know what led to the frictions in the past. But make a plea to
look forward, grab help and focus on achieving shorter throughput times in
bringing KDE changes to Debian.  Let me know if/how I can help.

Regards

Luc


Op zo 5 jul. 2020 om 15:49 schreef Norbert Preining :

> Hi Dietz,
>
> > Would you mind announcing relevant changes from your side (changed
> repos,
> > discontinued development and so on) also oh debian-kde?
>
> I don't think this is welcome here, since also on the IRC channel I was
> told not to advertise my repositories.
>
> I suggest you to follow my blog, tag "KDE" to receive updates.
>
> Thanks
>
> Norbert
>
> --
> PREINING Norbert  https://www.preining.info
> Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
> GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
>
>

-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


Re: Status of Plasma 5.18/5.19?

2020-07-07 Thread Luc Castermans
Dear

I have no objections to this proposal.
At the same time I like to express my wish to find an opening to get out of
the current situation.

Regards,
Luc

Op di 7 jul. 2020 om 09:06 schreef Rainer Dorsch :

> Am Sonntag, 5. Juli 2020, 15:48:55 CEST schrieb Norbert Preining:
> > Hi Dietz,
> >
> > > Would you mind announcing relevant changes from your side (changed
> repos,
> > > discontinued development and so on) also oh debian-kde?
> >
> > I don't think this is welcome here, since also on the IRC channel I was
> > told not to advertise my repositories.
> >
>
> Since this is already speculation, can anybody who has concerns with
> announcements or user reports of Norbert's super uptodate KDE packages for
> Debian here on the list share them? I hope with an open minded and
> solution
> oriented discussion they can be addressed and resolved
>
> Thanks
> Rainer
>
> --
> Rainer Dorsch
> http://bokomoko.de/
>
>
>

-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


Re: Status of Plasma 5.18/5.19?

2020-07-07 Thread Luc Castermans

In response to remarks in this thread, I like to add two remarks:

"Open":  is for me the openness of mind: listening to others opinions, 
remarks, etc. And carefully digestion these, balancing them, before 
responding to them.


Secondly: I consider myself Debian-ist. Packages created outside the 
DFSG and not available from Debian servers are basically not okay for me.


Therfore I see Norberts packages as a temporary way to get access to 
latest and greatest KDE packages, but at the same time I see them as an 
option to speed up creating compliant Debian packages. I´d expect code, 
methods, automation can be re-used from Norbert´s work to accomplish 
this. Disclaimer: I can be wrong on the latter.


Regards,

Luc






Op 07-07-2020 om 16:19 schreef Martin Steigerwald:

Hi.

Luc Castermans - 07.07.20, 09:42:34 CEST:

I have no objections to this proposal.
At the same time I like to express my wish to find an opening to get
out of the current situation.

Just speaking for myself personally: I second this.

Best,


--

m.vr.gr.

Luc Castermans
mailto:luc.casterm...@gmail.com



Re: Status of Plasma 5.18/5.19?

2020-07-26 Thread Luc Castermans

Could I help ? Although I am just a humble non-Debian packager.

Luc

Op 26-07-2020 om 22:33 schreef Shmerl:

Om Tue, 07 Jul 2020 08:20:48 -0700 Scarlett Moore wrote:
> Again, help is gladly accepted as long as it is quality work
> and not just a changelog entry..
> Thanks, Scarlett

Hi Scarlett!

If I understand correctly, it's primarily you alone working now on 
updating Plasma packages
in Debian unstable / testing? If so, thanks for your work! Did you 
manage to use//Norbert's

submissions after all? He said his merge requests are still available.

It would be really great for KDE/Debian users if this could be 
resolved positively and in the
manner that's productive and allows collaboration. This really needs 
to move forward, there

are simply not enough resources not to share such efforts.

Best regards,
Shmerl.
//



--

m.vr.gr.

Luc Castermans
mailto:luc.casterm...@gmail.com



Re: Status of Plasma 5.18/5.19?

2020-07-27 Thread Luc Castermans
So now I learned about it:  https://en.wikipedia.org/wiki/Occam%27s_razor

Is there a simple explanation of the status of KDE in Debian?



Op ma 27 jul. 2020 om 11:54 schreef Marco Valli :

> In data lunedì 27 luglio 2020 10:22:06 CEST, Norbert Preining ha scritto:
> > Lines up well with the rest of his comments!
>
> I don't like wasting words unnecessarily!
>
> --
> Marco Valli
>
>
>

-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


Re: Re: Status of Plasma 5.18/5.19?

2020-07-28 Thread Luc Castermans
Just came across: https://build.opensuse.org/
The/a developper mentioned this to be a X-distro build system, so can/could
be used to create Debian packages.
Could such service help, if appropriate, to create momentum?

Luc

Op zo 26 jul. 2020 om 22:51 schreef Shmerl :

> Om Tue, 07 Jul 2020 08:20:48 -0700 Scarlett Moore wrote:
> > Again, help is gladly accepted as long as it is quality work
> > and not just a changelog entry..
> > Thanks, Scarlett
>
> Hi Scarlett!
>
> If I understand correctly, it's primarily you alone working now on
> updating Plasma packages
> in Debian unstable / testing? If so, thanks for your work! Did you manage
> to use Norbert's
> submissions after all? He said his merge requests are still available.
>
> It would be really great for KDE/Debian users if this could be resolved
> positively and in the
> manner that's productive and allows collaboration. This really needs to
> move forward, there
> are simply not enough resources not to share such efforts.
>
> Best regards,
> Shmerl.
>
>
>

-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


Re: Status of Plasma 5.18/5.19?

2020-09-18 Thread Luc Castermans
Hi,

I am happy to test as well!

Luc

Op vr 18 sep. 2020 om 15:49 schreef Marc Haber :

> On Fri, Sep 18, 2020 at 10:41:30PM +0900, Norbert Preining wrote:
> > we, that is Scarlett Moore and Patrick Franz and me, are working on
> > updating Plasma in Debian. For now we are uploading 5.19(.4) to
> > Debian/experimental, but this needs a few iterations due to NEW
> > processing, but hopefully it will be all done soon.
>
> That is really really good news, thanks for the update!
>
> I am especially glad that things are going forward as a team effort and
> that the team has at least one VERY experienced DD. Thank you all for
> doing this.
>
> Please keep people updated about your progress and especially the state
> of the experimental packages, I have a test notebook that I don't mind
> breaking occasionally, so I can do testing if the packages are in a
> state when trying them makes sense. I guess other people might
> be able to help with that as well.
>
> Greetings
> Marc
>
> --
>
> -
> Marc Haber | "I don't trust Computers. They | Mailadresse im Header
> Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
> Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421
>
>

-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


Re: BTW

2020-10-16 Thread Luc Castermans

thanks Norbert++ indeed!!

apt install plasma-framework -t experimental

Did the job.

Regards,  Luc



Op 16-10-2020 om 00:48 schreef Marco Valli:

Btw, kdepim 20.08 and kde framework 5.74 works flawlessy here.
Thanks for your work - and thanks also to norbert, who is also becoming nice
to me.

regards


--

m.vr.gr.

Luc Castermans
mailto:luc.casterm...@gmail.com



Re: BTW

2020-10-16 Thread Luc Castermans
Making jokes in mails is difficult as facial expressions and gestures are
missing.

I like to thank all who contributed in whatever way.

luc

Op vr 16 okt. 2020 om 14:57 schreef Marco Valli :

> In data venerdì 16 ottobre 2020 13:35:09 CEST, Luc Castermans ha scritto:
> > thanks Norbert++ indeed!!
>
> Mine was a joke, but in this way you seem to belittle the work of
> Scarlett,
> Frank, Sandro, Pino and, last but no least, Lisandro.
>
> --
> Marco Valli
>
>
>

-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


Re: Plasma 5.19.5 and Qt 5.15 in unstable

2020-11-07 Thread Luc Castermans
great news.

Thanks for all efforts to all involved!

Luc

Op za 7 nov. 2020 10:04 schreef Martin Steigerwald :

> Hi!
>
> Qt 5.15 is completely in unstable now and already also migrated to
> testing. kdevelop had to be uninstalled on my system, but I bet a fix
> will be coming soon enough as well.
>
> Now Plasma 5.19.5 is also coming.
>
> As always just wait till apt dist-upgrade is safe to do. If you
> previously used experimental packages, the updates should be seamless,
> but if you still use 5.17, better wait till everything is complete.
>
> I already have Qt 5.15 and Plasma 5.19.5 experimental packages installed
> and they are working just fine. There was an issue with window rules
> editing pane in System Settings not displaying, but this was just a
> missing dependency that should be fixed with the next upload. To fix
> manually install:
>
> qml-module-org-kde-kitemmodels
>
> Thanks to the effort of the Qt/KDE team the Qt/Plasma/KDE Applications
> stuff is quite up to date in Debian by now!
>
> Thanks to everyone involved. This has been quite a large feat to
> complete. Thank you also very much for the nice cooperation I am seeing
> these days! It really shows that together it is easier to achieve all of
> this.
>
> You can help, too: In case you experience bugs it is good to first check
> whether you have all packages updated. At least to some extent packages
> should be updated in lock step due to versioned dependencies, but this
> is challenging to get completely right. If unsure ask here first before
> you report a bug report that is just due to some version mix that will
> not appear this way in next Debian stable. Also in case a bug is clearly
> an upstream bug, you can help by also reporting it upstream and provide
> a link to the Debian bug report.
>
> Many thanks!
>
> Best,
> --
> Martin
>
>
>


Re: You can help: Test Plasma 5.20.4 and test applications 20.12

2020-12-14 Thread Luc Castermans
same for me.

Later today I will perform a login again.

Thanks for good work!!

Luc

Op ma 14 dec. 2020 om 12:46 schreef Libor Klepáč :

> Hi,
> i upgraded to Plasma 5.20.4 when it appeared in experimental.
> So far so good.
>
> Today I also upgraded qt5, without problems (but I have not logged in
> again, yet)
>
> Thanks to all packagers
>
> Libor
>
> On So, 2020-12-12 at 19:37 +0100, Martin Steigerwald wrote:
> > Hi!
> >
> > If you are feeling adventurous and are using Sid, then you can help
> > by
> > testing Plasma 5.20.4 from experimental. I installed it using
> >
> > apt install -t experimental plasma-base
> >
> > "plasma-base" is a new package to keep the versions of all Plasma
> > packages in lock step.
> >
> > But beware currently Qt 5.15.2 is entering into Sid. It may need a
> > day
> > or two to complete. Be extra careful during that time.
> >
> > Also you can help test new application 20.12 packages as they enter
> > unstable. Use them and report any issues you find with them.
> >
> > Please do this only if you feel up to it and are willing to keep the
> > pieces in case something breaks. Of course you can always ask for
> > help
> > here, but it would be good if you are willing to do your best to
> > resolve
> > and diagnose issues on your own first and then if need be report with
> > as
> > much detail as possible.
> >
> > If unsure whether it is really a Debian bug or you like to learn
> > about
> > which package to report the bug for, feel free to ask here first.
> >
> > So far I am very happy with Plasma 5.20.4 and those KDE application
> > packages I upgraded. I thank Norbert, Aurélien, Sandro who is in the
> > process to upgrade KDEPIM packages to 20.08.3, Dmitry and everyone
> > else
> > who is involved with upgrading the packages or helps testing them.
> >
> > Thank you,
>


-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


Re: You can help: Test Plasma 5.20.4 and test applications 20.12

2020-12-14 Thread Luc Castermans
on 20.12 packages as they enter
unstable. Use them and report any issues you find with them.

Please do this only if you feel up to it and are willing to keep the
pieces in case something breaks. Of course you can always ask for
help
here, but it would be good if you are willing to do your best to
resolve
and diagnose issues on your own first and then if need be report with
as
much detail as possible.

If unsure whether it is really a Debian bug or you like to learn
about
which package to report the bug for, feel free to ask here first.

So far I am very happy with Plasma 5.20.4 and those KDE application
packages I upgraded. I thank Norbert, Aurélien, Sandro who is in the
process to upgrade KDEPIM packages to 20.08.3, Dmitry and everyone
else
who is involved with upgrading the packages or helps testing them.

Thank you,


--

m.vr.gr.

Luc Castermans
mailto:luc.casterm...@gmail.com



Re: Wohooo! Plasma 5.20 and KF 5.77 coming to unstable

2020-12-22 Thread Luc Castermans

yep

I did "apt upgrade -t sid"   That worked.


Op 22-12-2020 om 11:41 schreef Andrey Rahmatullin:

I've just updated (the packages from experimental were installed before)
and so far it works perfectly.


--

m.vr.gr.

Luc Castermans
mailto:luc.casterm...@gmail.com



Re: Upgrade to KF v5.79.0 from Debian/experimental

2021-02-16 Thread Luc Castermans

Indeed below did the job:

dpkg -l | grep 5.78.0 | awk '/^ii/ {print $2}' | sort > ZZZ-KF-5-78-0
apt install -t experimental  `cat ZZZ-KF-5-78-0 `

THX!!!

Luc

Op 16-02-2021 om 11:22 schreef Norbert Preining:

Hi Sedat,

Thanks for the report, indeed, purpose isn't building because I missed to 
update one dependency (no idea why all others are updated, though?).

I'll fix it later tonight or tomorrow morning (JST).

Let us know if you are any other anomalies.

Best


--

m.vr.gr.

Luc Castermans
mailto:luc.casterm...@gmail.com



Re: Upgrade to KF v5.79.0 from Debian/experimental

2021-02-16 Thread Luc Castermans
Thanks indeed.   I completed the install from experimental, all required 
packages available from there.



Luc

Op 16-02-2021 om 14:33 schreef Sedat Dilek:

Hi Norbert,

I want to thank you and all involved Debian/KDE/Qt users and
developers and of course KDE and Qt upstream.

Right now, I have installed the missing 3 purpose version 5.79.0-2
packages from Debian/buildd-experimental.

Regards,
- Sedat -

On Tue, Feb 16, 2021 at 11:22 AM Norbert Preining  wrote:

Hi Sedat,

Thanks for the report, indeed, purpose isn't building because I missed to 
update one dependency (no idea why all others are updated, though?).

I'll fix it later tonight or tomorrow morning (JST).

Let us know if you are any other anomalies.

Best
--
PREINING Norbert  https://www.preining.info
Fujitsu Research Labs + IFMGA ProGuide + TU Wien + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13


Feb 16, 2021 17:30:26 Sedat Dilek :


Hi,

just wanna let you know I was able to upgrade KF version
5.78.0/unstable -> 5.79.0/experimental.
( More exactly build-experimental. )

[ Get list of installed KF v5.78.0 packages ]
root$ dpkg -l | grep 5.78.0 | awk '/^ii/ {print $2}' | sort > ZZZ-KF-5-78-0

[ Simulate upgrade to KF v5.79.0 ]
root# apt-get install -s -t buildd-experimental $( cat ZZZ-KF-5-78-0 )
| grep ^Inst | awk '{print $2}' | sort > ZZZ-KF-5-79-0-UPGRADABLE

[ Looks good? ]
root# LC_ALL=C wc -l ZZZ-KF-5-78-0 ZZZ-KF-5-79-0-UPGRADABLE
183 ZZZ-KF-5-78-0
180 ZZZ-KF-5-79-0-UPGRADABLE
363 total

Note: 3 packages missing for upgrade (see `git diff` below).

[ SWITCH TO VT-2 ]

[ Stop Login-Manager ]
systemctl stop sddm.service

[ Upgrade to KF v5.79.0 ]
apt-get install -y -t buildd-experimental $( cat ZZZ-KF-5-78-0 )

[ List installed KF v5.79.0 packages ]
root# dpkg -l | grep 5.79.0 | awk '/^ii/ {print $2}' | sort > ZZZ-KF-5-79-0

[ What's missing? ]
root# git diff ZZZ-KF-5-78-0 ZZZ-KF-5-79-0 | grep ^'-'
--- a/ZZZ-KF-5-78-0
-libkf5purpose5:amd64
-libkf5purpose-bin:amd64
-qml-module-org-kde-purpose:amd64

Note: Missing libkf5purpose5 packages.

LGTM.

[ Start Login-Manager ]
systemctl start sddm.service

Enjoy :-).

Thanks for the update.

Regards,
- Sedat -


--

m.vr.gr.

Luc Castermans
mailto:luc.casterm...@gmail.com



Re: Simulated upgrade to KDE/Plasma (KP) 5.21.0/experimental

2021-02-19 Thread Luc Castermans
can something be done to stop need for drinking thea ?

Op vr 19 feb. 2021 08:57 schreef Sedat Dilek :

> On Fri, Feb 19, 2021 at 8:17 AM Norbert Preining 
> wrote:
> >
> > > What does that mean for kwin in NEW... and the availability of its
> >
> > Wait and have lots of tea!
> >
>
> Yupp, drinking camomile tea...
>
> - sed@ -
>
>


Re: Simulated upgrade to KDE/Plasma (KP) 5.21.0/experimental

2021-02-21 Thread Luc Castermans
wow, no more tea drinking!

Op zo 21 feb. 2021 om 20:57 schreef Sedat Dilek :

> On Sat, Feb 20, 2021 at 1:21 PM Sedat Dilek  wrote:
> >
> > On Wed, Feb 17, 2021 at 9:14 PM Norbert Preining 
> wrote:
> > >
> > > On Wed, 17 Feb 2021, Sedat Dilek wrote:
> > > > An upgraded kwin version 4:5.21.0-1 is not available.
> > >
> > > Yes, kdecorations, kwin, plasma-discover need NEW processing.
> > >
> > > If you are in hurry, get the git repo, checkout experimental branch of
> > > the three, run
> > > uscan --rename --download-current-version
> > > dpkg-buildpackage -us -uc -rfakeroot -S -d
> > > and then build the binary package in your favorite way.
> > >
> >
> > LGTM:
> >
> > root# dpkg -l | egrep 'kwin|kdecoration|plasma-discover' | awk '/^ii/
> > {print $1 " " $2 " " $3}' | column -t
> > ii  kwin-common 4:5.21.0-1
> > ii  kwin-data   4:5.21.0-1
> > ii  kwin-style-breeze   4:5.21.0-1
> > ii  kwin-wayland4:5.21.0-1
> > ii  kwin-wayland-backend-drm4:5.21.0-1
> > ii  kwin-wayland-backend-wayland4:5.21.0-1
> > ii  kwin-wayland-backend-x114:5.21.0-1
> > ii  kwin-x114:5.21.0-1
> > ii  libkdecorations2-5v5:amd64  4:5.21.0-1
> > ii  libkdecorations2-dev:amd64  4:5.21.0-1
> > ii  libkdecorations2private7:amd64  4:5.20.5-1
> > ii  libkdecorations2private8:amd64  4:5.21.0-1
> > ii  libkf5windowsystem-dev  5.79.0-1
> > ii  libkwin4-effect-builtins1   4:5.21.0-1
> > ii  libkwineffects134:5.21.0-1
> > ii  libkwinglutils134:5.21.0-1
> > ii  libkwinxrenderutils13   4:5.21.0-1
> > ii  plasma-discover 5.21.0-1
> > ii  plasma-discover-common  5.21.0-1
> > ii  qml-module-org-kde-kwindowsystem:amd64  5.79.0-1
> >
> > Rest:
> >
> > root# dpkg -l | grep 5.20.5 | awk '/^ii/ {print $1 " " $2 " " $3}' |
> column -t
> > ii  kde-config-gtk-style:amd64  4:5.20.5-2
> > ii  libkdecorations2private7:amd64  4:5.20.5-1
> >
> > Note: kde-config-gtk-style depends on libkdecorations2private7
> >
>
> The 3 packages are now available in Debian/experimental.
>
> - Sedat -
>
>

-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


Re: Simulated upgrade to KDE/Plasma (KP) 5.21.0/experimental

2021-02-21 Thread Luc Castermans
Indeed thanks Sedat, Norbert, all I forget now. I upgrade from Experimental
like a charm!!


Besturingssysteem: Debian GNU/Linux
KDE Plasma-versie: 5.21.0
Versie van KDE-Frameworks: 5.79.0
Qt-versie: 5.15.2
Kernel-versie: 5.10.0-3-amd64
Type OS: 64-bit
Grafisch platform: X11
Processors: 4 × Intel® Core™ i5-4200U CPU @ 1.60GHz
Geheugen: 7,2 GiB RAM
Grafische processor: Mesa DRI Intel® HD Graphics 4400

Op zo 21 feb. 2021 om 21:23 schreef Sedat Dilek :

> On Sun, Feb 21, 2021 at 9:17 PM Luc Castermans 
> wrote:
> >
> > wow, no more tea drinking!
> >
>
> Here it is past 9p.m., so no more tea-time.
>
> I built kde-gtk-config and installed the missing...
>
> -ii  kde-config-gtk-style:amd64  4:5.20.5-2
> +ii  kde-config-gtk-style:amd64  4:5.21.0-1
> -ii  libkdecorations2private7:amd64  4:5.20.5-1
>
> ...and removed (now unneeded) libkdecorations2private7.
>
> Finally:
>
> root# dpkg -l | grep 5.20.5
> [ empty ]
>
> Means full KDE/Plasma 5.21.0 installed.
>
> - Sedat -
>
> > Op zo 21 feb. 2021 om 20:57 schreef Sedat Dilek :
> >>
> >> On Sat, Feb 20, 2021 at 1:21 PM Sedat Dilek 
> wrote:
> >> >
> >> > On Wed, Feb 17, 2021 at 9:14 PM Norbert Preining <
> norb...@preining.info> wrote:
> >> > >
> >> > > On Wed, 17 Feb 2021, Sedat Dilek wrote:
> >> > > > An upgraded kwin version 4:5.21.0-1 is not available.
> >> > >
> >> > > Yes, kdecorations, kwin, plasma-discover need NEW processing.
> >> > >
> >> > > If you are in hurry, get the git repo, checkout experimental branch
> of
> >> > > the three, run
> >> > > uscan --rename --download-current-version
> >> > > dpkg-buildpackage -us -uc -rfakeroot -S -d
> >> > > and then build the binary package in your favorite way.
> >> > >
> >> >
> >> > LGTM:
> >> >
> >> > root# dpkg -l | egrep 'kwin|kdecoration|plasma-discover' | awk '/^ii/
> >> > {print $1 " " $2 " " $3}' | column -t
> >> > ii  kwin-common 4:5.21.0-1
> >> > ii  kwin-data   4:5.21.0-1
> >> > ii  kwin-style-breeze   4:5.21.0-1
> >> > ii  kwin-wayland4:5.21.0-1
> >> > ii  kwin-wayland-backend-drm4:5.21.0-1
> >> > ii  kwin-wayland-backend-wayland4:5.21.0-1
> >> > ii  kwin-wayland-backend-x114:5.21.0-1
> >> > ii  kwin-x114:5.21.0-1
> >> > ii  libkdecorations2-5v5:amd64  4:5.21.0-1
> >> > ii  libkdecorations2-dev:amd64  4:5.21.0-1
> >> > ii  libkdecorations2private7:amd64  4:5.20.5-1
> >> > ii  libkdecorations2private8:amd64  4:5.21.0-1
> >> > ii  libkf5windowsystem-dev  5.79.0-1
> >> > ii  libkwin4-effect-builtins1   4:5.21.0-1
> >> > ii  libkwineffects134:5.21.0-1
> >> > ii  libkwinglutils134:5.21.0-1
> >> > ii  libkwinxrenderutils13   4:5.21.0-1
> >> > ii  plasma-discover 5.21.0-1
> >> > ii  plasma-discover-common  5.21.0-1
> >> > ii  qml-module-org-kde-kwindowsystem:amd64  5.79.0-1
> >> >
> >> > Rest:
> >> >
> >> > root# dpkg -l | grep 5.20.5 | awk '/^ii/ {print $1 " " $2 " " $3}' |
> column -t
> >> > ii  kde-config-gtk-style:amd64  4:5.20.5-2
> >> > ii  libkdecorations2private7:amd64  4:5.20.5-1
> >> >
> >> > Note: kde-config-gtk-style depends on libkdecorations2private7
> >> >
> >>
> >> The 3 packages are now available in Debian/experimental.
> >>
> >> - Sedat -
> >>
> >
> >
> > --
> > Luc Castermans
> > mailto:luc.casterm...@gmail.com
>


-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


Plasma 5.21.1 in Experimental

2021-02-26 Thread Luc Castermans
Upstream Plasma 5.21.1 was released Feb 23, yesterday I installed it from
Experimental.A big wow and even a bigger thanks to all who made this
possible. I am tempted to mention names, don´t do that in order not to
disappoint people. Thank you community!


Besturingssysteem: Debian GNU/Linux
KDE Plasma-versie: 5.21.1
Versie van KDE-Frameworks: 5.79.0
Qt-versie: 5.15.2
Kernel-versie: 5.10.0-3-amd64
Type OS: 64-bit
Grafisch platform: X11
Processors: 4 × Intel® Core™ i5-4200U CPU @ 1.60GHz
Geheugen: 7,2 GiB RAM
Grafische processor: Mesa DRI Intel® HD Graphics 4400



-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


Re: Plasma 5.21.1 in Experimental

2021-02-26 Thread Luc Castermans
Hi Martin

My answer below depends on the starting point at your PC.

I retrieved the list of installed plasma related packages using something
like:

dpkg -l | fgrep 5.2xy  | awk '{ print $2 }' > toupgrade
[As my PC was on 5.21.0 I could use 5.21.0  in the fgrep, if you're at 5.20
you should use that of course.]

and then

apt install -t experimental `cat toupgrade`

Regards,

Luc

Op vr 26 feb. 2021 om 12:30 schreef Martin Steigerwald :

> Hi Luc,
>
> Luc Castermans - 26.02.21, 12:12:48 CET:
> > Upstream Plasma 5.21.1 was released Feb 23, yesterday I installed it
> > from Experimental.A big wow and even a bigger thanks to all who
> > made this possible. I am tempted to mention names, don´t do that in
> > order not to disappoint people. Thank you community!
>
> Thanks for letting us know.
>
> What exact command did you use?
>
> I already installed KDE Frameworks 5.79 from Experimental on top of
> Devuan Ceres – which is basically very similar to Debian Sid, just
> without Systemd by default without having to deal with some…
> uncooperative Debian maintainers (none from the Debian Qt/KDE team, midn
> you).
>
> However… I am certainly do not like to use the approach Sedat used
> initially, which is:
>
> RELEASE="experimental" ; LC_ALL=C apt-get dist-upgrade -V -t $RELEASE
>
> Cause it would upgrade too much.
>
> I instead did so with meta packages for Plasma, yet it still pulled
> libglib from experimental and things did not work as expected, maybe due
> to a partial upgrade of Plasma packages. Back then I downgraded
> everything to 5.20 again and reverted all the other package upgrades to
> Debian experimental as well.
>
> So I would like to just install Plasma 5.21.1 from experimental, but
> that complete, without upgrading unrelated packages to experimental as
> well.
>
> Any aptitude / apt foo magic recommendation? Otherwise I try to come up
> with something myself.
>
> Best,
> --
> Martin
>
>
>

-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


Re: KDE Plasma v5.21.2

2021-03-04 Thread Luc Castermans
same, here. Easy upgrade :=)   Thanks!!

[image: afbeelding.png]


Op do 4 mrt. 2021 om 10:27 schreef Sedat Dilek :

> No comment, see attachment.
>
> - sed@ -
>


-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


Frameworks 5.80

2021-03-20 Thread Luc Castermans
Hi,

I just pulled KDE-Frameworks: 5.80.0  from Experimental.

Thanks for all hard work and keeping us in sync with up-stream!!

-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


Plasma 5.21.4 available in Experimental

2021-04-07 Thread Luc Castermans

Dear

I just installed Plasma 5.21.4 from Experimental.

Thank you very much!

--

m.vr.gr.

Luc Castermans
mailto:luc.casterm...@gmail.com



KDE Frameworks 5.81.0 available (Experimental)

2021-04-14 Thread Luc Castermans
My computer just pulled KDE Frameworks 5.81.0 from Experimental.

Thanks!

-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


Re: KDE Gear 21.04 coming to experimental

2021-04-24 Thread Luc Castermans

thanks!  I installed and use without issues

root@canne:~# dpkg -l | fgrep 21.04
ii  dolphin 4:21.04.0-1   amd64    file manager
ii  dolphin-plugins 4:21.04.0-1   amd64    
plugins for Dolphin

ii  gwenview 4:21.04.0-1   amd64    image viewer
ii  kate 4:21.04.0-1   amd64    powerful 
text editor
ii  kate5-data 4:21.04.0-1   all  shared 
data files for Kate text editor
ii  konsole 4:21.04.0-1   amd64    X 
terminal emulator
ii  konsole-kpart 4:21.04.0-1   amd64    
Konsole plugin for Qt applications
ii  libdolphinvcs5:amd64 4:21.04.0-1   
amd64    library to show version control in Dolphin
ii  libokular5core9 4:21.04.0-1   amd64    
libraries for the Okular document viewer
ii  okular 4:21.04.0-1   amd64    universal 
document viewer

root@canne:~#


Op 23-04-2021 om 09:11 schreef Martin Steigerwald:

Hi!

Norbert is uploading it currently.

I do not expect issues, but as always only use packages from
experimental if you are confident that you can fix apt / aptitude errors
and if you in case that you need help are willing to provide sufficient
information.

I suggest to report bugs here first as they may turn out to be caused by
partial updates, although I believe with KDE Gear – yeah, they changed
the name again – this is not too much of an issue.

Best,


--

m.vr.gr.

Luc Castermans
mailto:luc.casterm...@gmail.com



Re: KDE Frameworks 5.81.0 available (Experimental)

2021-05-03 Thread Luc Castermans
Hi Chris

I use Plasma etc. stuf from Experimental and plan to use it along the way,
until it arrives in Sid, testing, etc.  The default on my machines
is testing, I install stuf from Experimental only based on my interests,
KDE being one of them, so non-KDE packages are installed from testing or
sid if needed.

I install latest-and-greatest of Frameworks and Plasma, as they ought to go
together, just following the upstream releases. I am very satisfied with de
KDE packages in Debian as they are available after a couple of days of the
upstream release. This allows me to follow and interact with the upstream
communications on KDE while using a stable Debian environment.   I cannot
thank the team enough for this!

Regards,

Luc



Op za 1 mei 2021 om 16:22 schreef inkbottle :

> On Wednesday, April 14, 2021 11:03:32 PM CEST Luc Castermans wrote:
> > My computer just pulled KDE Frameworks 5.81.0 from Experimental.
>
> I've myself switched to "Plasma 5.21.4". Like, not planing to go back.
> It allows me to use kwin-wayland by fixing:
>
> https://bugs.kde.org/show_bug.cgi?id=404092
>
> I answer here because it seems the first post in that line.
>
> I'd be happy to hear about:
>
> How did you manage to install the binaries related to the source package,
> but
> only those that you need. Sort of.
>
> I've myself be guided to the line:
>
> `apt install -t experimental $(dpkg -l | grep 5.20.5 | awk '/^ii/ {print
> $2}')`
>
> And about pinning experimental with a low priority...
>
> And also:
>
> Do you feel that "Plasma 5.21.4" is working better when with "Frameworks
> 5.81.0"?
>
> Or that, if I'm satisfied with Plasma-5.21.4, I shouldn't bother with
> Framework-5.81.0?
>
> (Satisfied here is more a question of "how much" than of "yes or no".
> Certainly
> there are plenty of things that are not performing the way they should.
> But
> the feeling is that Wayland is more stable, more robust, faster: better in
> every way that really matter. And no, the bells and whistles are not there
> yet. And plenty of small things are crashing, but the desktop itself seems
> dependable. And if something is not working with Wayland, you can expect
> there'll be a fix someday.)
>
> Anyway:
>
> How do you manage installs and upgrades related to Experimental Framework
> and
> Plasma?
>
> What is you level of satisfaction about it?
>
> Are you planing to keep on using them, until they come to unstable in a
> distant future?
>
> I don't suppose you are usually using experimental as your regular debian
> source?
>
> Thanks,
> Chris
>
>
>
>
>
>

-- 
Luc Castermans
mailto:luc.casterm...@gmail.com


plasma 5.21.5 - Debian experimental

2021-05-08 Thread Luc Castermans

Dear,

Today I successfully installed the Plasma 5.21.5 bug-fix release from 
Experimental.


Thank you very much!

--

m.vr.gr.

Luc Castermans
mailto:luc.casterm...@gmail.com



Re: KDE Frameworks 5.82.0-1 available (Experimental)

2021-05-10 Thread Luc Castermans
hi,

I upgraded earlier today.  I observed no issues during and after upgrade.

Thanks!

Luc

Op ma 10 mei 2021 18:06 schreef inkbottle :

> Hi all,
>
> I've upgraded to Frameworks 5.82.0-1.
>
> Below an edited transcript of what went well and what didn't.
>
> Your suggestions about the right way to do it are welcome.
>
> Chris
>
>
>
>  5.82.0-1: apt update; apt -t unstable dist-upgrade; apt install -t
> experimental plasma-desktop plasma-framework
>  First run didn't work: plasmashell 100% cpu forever, had to reboot.
>  Second run seems okay.
>  Do you have mixed versions?
>  I'm not sure whether that upgraded all packages to 5.21.5 or 5.82
>  Assuming you have the latest Plasma 5.21.5 installed, make sure no
> 5.21.4 packages are left: `dpkg -l | grep 5.21.4`
>  Similarly for the frameworks.
>  dpkg -l | grep -F "5.21.4" | wc -l ==> 72; dpkg -l | grep -F
> "5.21.5"
> | wc -l ==> 13
>  What did I do wrong?
>  Upgrading one package to 5.21.5 does not automatically upgrade all
> others.
>  So you would recommend this sort of command? `apt install -t
> experimental $( dpkg -l | grep 5.20.5 | awk '/^ii/ {print $2}' )`
>  It's the easiest for me. When you run stable/testing/unstable, you
> don't
> have this problem, because we usually upload all packages at once and
> everything will then be upgraded.
>  First thing would then be: `apt install -t experimental $( dpkg -l
> |
> grep 5.21.4 | awk '/^ii/ {print $2}' )`
>  Running now the above line
>  dpkg -l | grep -F "5.21.4" | wc -l ==> 0
>  dpkg -l | grep -F "5.21" | grep -v -F "5.21.5"  ==> two packages
> with
> version numbers 5.212.0~alpha4-11 => unrelated
>  Sounds good.
>  Now verifying for framework
>  dpkg -l | grep -F "5.78" | wc -l ==> 119
>  dpkg -l | grep -F "5.78" | egrep -v 'libkf5|qml-mod' ==> it's all
> KDE
> stuff
>  apt install -t experimental $( dpkg -l | grep -F "5.78.0" | awk
> '/^ii/
> {print $2}' )
>  dpkg -l | egrep "5\.(78|79|80|81)" | wc -l ==> 0
>  I should reboot now.
>
>
>
>
>


Re: KDE Frameworks 5.82.0-1 available (Experimental)

2021-05-10 Thread Luc Castermans

so I used below, with XY the version installed at present:

apt install -t experimental `dpkg -l | fgrep 5.XY | awk '{print $2}'`

Regards,


Luc



Op 10-05-2021 om 21:14 schreef inkbottle:

On Monday, May 10, 2021 7:13:11 PM CEST Luc Castermans wrote:

hi,

I upgraded earlier today.  I observed no issues during and after upgrade.

Can you say what specific command line(s) you are using for the experimental
part of the upgrade.


Thanks!

Luc

Op ma 10 mei 2021 18:06 schreef inkbottle :

Hi all,

I've upgraded to Frameworks 5.82.0-1.

Below an edited transcript of what went well and what didn't.

Your suggestions about the right way to do it are welcome.

Chris



 5.82.0-1: apt update; apt -t unstable dist-upgrade; apt install -t
experimental plasma-desktop plasma-framework
 First run didn't work: plasmashell 100% cpu forever, had to
reboot.
 Second run seems okay.
 Do you have mixed versions?
 I'm not sure whether that upgraded all packages to 5.21.5 or 5.82
 Assuming you have the latest Plasma 5.21.5 installed, make sure no
5.21.4 packages are left: `dpkg -l | grep 5.21.4`
 Similarly for the frameworks.
 dpkg -l | grep -F "5.21.4" | wc -l ==> 72; dpkg -l | grep -F
"5.21.5"

| wc -l ==> 13

 What did I do wrong?
 Upgrading one package to 5.21.5 does not automatically upgrade all
others.
 So you would recommend this sort of command? `apt install -t
experimental $( dpkg -l | grep 5.20.5 | awk '/^ii/ {print $2}' )`
 It's the easiest for me. When you run stable/testing/unstable, you
don't
have this problem, because we usually upload all packages at once and
everything will then be upgraded.
 First thing would then be: `apt install -t experimental $( dpkg -l

grep 5.21.4 | awk '/^ii/ {print $2}' )`
 Running now the above line
 dpkg -l | grep -F "5.21.4" | wc -l ==> 0
 dpkg -l | grep -F "5.21" | grep -v -F "5.21.5"  ==> two packages
with
version numbers 5.212.0~alpha4-11 => unrelated
 Sounds good.
 Now verifying for framework
 dpkg -l | grep -F "5.78" | wc -l ==> 119
 dpkg -l | grep -F "5.78" | egrep -v 'libkf5|qml-mod' ==> it's all
KDE
stuff
 apt install -t experimental $( dpkg -l | grep -F "5.78.0" | awk
'/^ii/
{print $2}' )
 dpkg -l | egrep "5\.(78|79|80|81)" | wc -l ==> 0
 I should reboot now.





--

m.vr.gr.

Luc Castermans
mailto:luc.casterm...@gmail.com



Re: Plasma 5.23 25th Annivery Release coming to unstable

2021-10-14 Thread Luc Castermans
Great & Thanks!

Op do 14 okt. 2021 17:15 schreef Martin Steigerwald :

> Hi!
>
> Just that. Norbert uploaded it to unstable.
>
> As I learned in #debian-qt-kde IRC channel, KDecoration went to
> experimental, instead of unstable, so you may need to get it from there
> until Norbert or someone else uploads it to unstable.
>
> As usually take care with "apt dist-upgrade". Wait until the builds are
> complete.
>
> Best,
> --
> Martin
>
>
>


  1   2   >