Re: Some problems with the last updates

[Arthur Marsh]

Diederik de Haas wrote on 06/11/16 10:29:

On zaterdag 5 november 2016 20:25:32 CET Andrey Rahmatullin wrote:

If so, that is/was your problem and you'll likely have various qt5 package
at  version 5.7.1~20161021+dfsg-N.
Downgrade those packages to their version in testing and there's a
reasonable  chance things start working again. See also
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843208#10


The current state is that it's highly likely that a bug in qtdeclarative-
opensource-src (source package) version 5.7.1~20161021-4 is the cause for the
issue various people are seeing.
One of the Debian Qt maintainers filed the following bug for it:
https://bugreports.qt.io/browse/QTBUG-56932

In Debian the following bugs have been reported which are likely all caused by
this issue:
https://bugs.debian.org/843250
https://bugs.debian.org/843332

and probably more will follow ...


I wonder if rebuilding some packages locally is easier than downgrading a
lot of packages? If yes, which ones?


No, that will not help you or anyone else, since the problem is in an
(important) part of qt5 5.7.1 itself.
As you (Andrey) already noticed and reported back, downgrading to the version
in testing works and I think that it is the only solution for now.
Aptitudes resolver should be able to help in downgrading all those packages.


I reported bug 843332, aptitude had issues that after thinking that I 
had downgrading all packages so that nothing was broken, there was still 
a conflict (which was different the two times I tried) that needed to be 
fixed by searching for the package name in aptitude and selecting the 
version from testing. After that, the downgrade went smoothly.


Is there any way to tell aptitude to downgrade all packages based off a 
given source package to the version in testing? That would have been 
less tedious than the manual process I used.


Thanks for all who suggested the fix.

Arthur.

Re: unicode / utf-8 characters displayed incorrectly in konsole

[Arthur Marsh]

Maximiliano Curia wrote on 30/06/16 16:16:

On Thursday, 30 June 2016 11:40:39 CEST Arthur Marsh wrote:

I've reported http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829002



Sometime yesterday due to upgrades or something happening when my
computer mouse behaved randomly for a minute or so, I've lost the
display of unicode/utf-8 characters in konsole, instead seeing the
diamond with a question mark in it. If I try to use mozc to input
Japanese text, the result displays as plain question marks.



Any suggestions on where to look/what to try?


Copy and pasting random japanese characters seem to work fine here. Could you
please check if konsole is using Unicode? (Right click set encoding),


It had been set to "default". I thought that the default encoding 
inherited from KDE would be Unicode/utf-8?


When I set each tab's encoding to Unicode/utf-8 characters displayed 
correctly.



also the
output of:
set | egrep -a '^(LC_|LANG)'

Could be of use.


That gives me:

LANG=en_AU.UTF-8



Also, it might be worth testing a different font. Dejavu Sans Mono is probably
the most complete font available, so start with that one. Other fonts rely on
the fontconfig fallbacks to produce the characters that are not defined.

Happy hacking,



Thanks very much for the help and suggestions.

I've also replaced the PS/2 mouse with a USB mouse that identifies 
itself as:


Bus 003 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse

having discovered some error messages about loss of synchronisation with 
the PS/2 mouse.


I'll update the bug report in a few minutes.

unicode / utf-8 characters displayed incorrectly in konsole

[Arthur Marsh]

I've reported http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829002

Sometime yesterday due to upgrades or something happening when my 
computer mouse behaved randomly for a minute or so, I've lost the 
display of unicode/utf-8 characters in konsole, instead seeing the 
diamond with a question mark in it. If I try to use mozc to input 
Japanese text, the result displays as plain question marks.


If I start an xterm session, that xterm session displays the characters 
correctly and I can input Japanese text find with mozc.


Any suggestions on where to look/what to try?

Arthur.

Re: kwin-x11 lock-ups

[Arthur Marsh]

Arthur Marsh wrote on 25/02/16 23:46:



So a problem still exists but it doesn't happen as often.

Arthur.


Triggered another bug today: https://bugs.kde.org/show_bug.cgi?id=359839

Arthur.

Re: kwin-x11 lock-ups

[Arthur Marsh]

Arthur Marsh wrote on 25/02/16 23:14:
...

it turned out that I had not applied this upgrade:

[UPGRADE] kwrited:amd64 4:5.4.3-1 -> 4:5.5.4-1



I gave this a try with using org.kde.breeze again after rebooting, then
set the window decoration back to Plastik and rebooted again, and
started fine.


After upgrading kwrited to 4:5.5.4-1 and logging out and logging back in 
again and starting iceweasel with Plastik window decoration, I again had 
a kwin_x11 lock-up again (no usable back-trace). I set the window 
decoration back to org.kde.breeze, rebooted and restarted iceweasel 
fine, then set the window decoration back to Plastik, rebooted and 
restarted iceweasel fine.


So a problem still exists but it doesn't happen as often.

Arthur.

Re: kwin-x11 lock-ups

[Arthur Marsh]

Reply accidentally sent to sender only instead of to list at first, 
resending to list:


Martin Steigerwald wrote on 25/02/16 21:40:
> Arthur,
>
> On Samstag, 20. Februar 2016 20:29:27 CET Arthur Marsh wrote:
>> After upgrading libc6 to 2.21-9, my lock-ups with kwin-x11 4:5.4.3-1.1
>> have gone, perhaps due to the fix of Debian bug #814958 in libc6.
>>
>> However, kwin-x11 4:5.5.4-2 locked up when starting iceweasel that
>> restored multiple windows.
>>
>> At least I have a working set-up, but was wondering if kwin_x11 should
>> have provided any more diagnostic information that could have helped
>> track down bugs like #814958?
>
> did you make sure you have installed all of kwin from experimental 
that you

> can get?
>
> For me kwin_x11 crashed repeatedly when using GLX + OpenGL 3.1 as 
compositor

> until I made sure libkwin4-effect-builtins1 is also at version 5.5.4-1.
>
> Also preferable do not enable DRI 3 at the moment in X.org 
configuration, at

> least not when using two Plasma sessions and switch between them.,

I think that was the clue that I needed - if it were easier to see what 
versions of packages I had installed that shared a common source package 
with kwin-x11 and plasma-desktop packages that may have helped me 
identify and upgrade the related packages.


I was using an on-board Radeon 3200HD (RS780) when I first encountered 
the problems and upgraded to a Radeon HD5450 (CEDAR) part way through.

Neither support OpenGL 3.1:

OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD CEDAR (DRM 2.43.0, LLVM 3.7.1)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.1.2
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 11.1.2
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 11.1.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:

Upgrades just performed:

[UPGRADE] kwrited:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] libkf5activitiesexperimentalstats1:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] libkf5sysguard-bin:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] libkf5sysguard-data:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] libkfontinst5:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] libkfontinstui5:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] libksgrd7:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] libksignalplotter7:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] libkwin4-effect-builtins1:amd64 4:5.4.3-1.1 -> 4:5.5.4-2
[UPGRADE] libkworkspace5-5:amd64 4:5.4.3-2 -> 4:5.5.4-1
[UPGRADE] liboxygenstyle5-5:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] liboxygenstyleconfig5-5:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] libpam-kwallet5:amd64 5.4.3-1 -> 5.5.4-1
[UPGRADE] libprocesscore7:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] libprocessui7:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] libtaskmanager5:amd64 4:5.4.3-2 -> 4:5.5.4-1
[UPGRADE] libweather-ion7:amd64 4:5.4.3-2 -> 4:5.5.4-1
[UPGRADE] milou:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] plasma-desktop:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] plasma-desktop-data:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] polkit-kde-agent-1:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] systemsettings:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] systemsettings-dbg:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] plasma-desktop:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] plasma-desktop-data:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] kwrited:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] libkf5activitiesexperimentalstats1:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] libkf5sysguard-bin:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] libkf5sysguard-data:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] libkfontinst5:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] libkfontinstui5:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] libksgrd7:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] libksignalplotter7:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] libkwin4-effect-builtins1:amd64 4:5.4.3-1.1 -> 4:5.5.4-2
[UPGRADE] libkworkspace5-5:amd64 4:5.4.3-2 -> 4:5.5.4-1
[UPGRADE] liboxygenstyle5-5:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] liboxygenstyleconfig5-5:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] libpam-kwallet5:amd64 5.4.3-1 -> 5.5.4-1
[UPGRADE] libprocesscore7:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] libprocessui7:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] libtaskmanager5:amd64 4:5.4.3-2 -> 4:5.5.4-1
[UPGRADE] libweather-ion7:amd64 4:5.4.3-2 -> 4:5.5.4-1
[UPGRADE] milou:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] plasma-desktop:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] plasma-desktop-data:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] polkit-kde-agent-1:amd64 4:5.4.3-1 -> 4:5.5.4-1
[UPGRADE] systemsettings:a

Re: kwin-x11 lock-ups

[Arthur Marsh]

Lisandro Damián Nicanor Pérez Meyer wrote on 25/02/16 12:11:

On Wednesday 24 February 2016 23:04:42 Arthur Marsh wrote:

Arthur Marsh wrote on 20/02/16 20:29:

After upgrading libc6 to 2.21-9, my lock-ups with kwin-x11 4:5.4.3-1.1
have gone, perhaps due to the fix of Debian bug #814958 in libc6.

However, kwin-x11 4:5.5.4-2 locked up when starting iceweasel that
restored multiple windows.

At least I have a working set-up, but was wondering if kwin_x11 should
have provided any more diagnostic information that could have helped
track down bugs like #814958?

Arthur.


Finally had a crash with a usable back-trace:

https://bugs.kde.org/show_bug.cgi?id=359749


Which was marked as solved with Qt 5.5.0. We do have 5.5.1.




Really weird then, I did more testing last night based on the comment:

https://bugs.kde.org/show_bug.cgi?id=352259#c1

"It's induced by the aurora decoration, so use the breeze engine (not 
plastik!, since that uses QML as well)"


Sure enough, using org.kde.breeze rather than Plastik in the window 
decorations avoids the problem, even though Qt 5.5.1 is running.


Arthur.

Re: kwin-x11 lock-ups

[Arthur Marsh]

Arthur Marsh wrote on 20/02/16 20:29:

After upgrading libc6 to 2.21-9, my lock-ups with kwin-x11 4:5.4.3-1.1
have gone, perhaps due to the fix of Debian bug #814958 in libc6.

However, kwin-x11 4:5.5.4-2 locked up when starting iceweasel that
restored multiple windows.

At least I have a working set-up, but was wondering if kwin_x11 should
have provided any more diagnostic information that could have helped
track down bugs like #814958?

Arthur.




Finally had a crash with a usable back-trace:

https://bugs.kde.org/show_bug.cgi?id=359749

Arthur.

kwin-x11 lock-ups

[Arthur Marsh]

After upgrading libc6 to 2.21-9, my lock-ups with kwin-x11 4:5.4.3-1.1 
have gone, perhaps due to the fix of Debian bug #814958 in libc6.


However, kwin-x11 4:5.5.4-2 locked up when starting iceweasel that 
restored multiple windows.


At least I have a working set-up, but was wondering if kwin_x11 should 
have provided any more diagnostic information that could have helped 
track down bugs like #814958?


Arthur.

Re: possible cause? Re: iceweasel locking up under KDE, fine under Xfce

[Arthur Marsh]

Arthur Marsh wrote on 16/01/16 02:29:

Carsten Pfeiffer wrote on 16/01/16 00:09:

On Friday 15 January 2016 23:00:13 Arthur Marsh wrote:


Is there any documentation on what configuration file(s) kwin_x11 uses?


You can try starting kwin with strace, like this (when it's not
running at the
moment):

strace -f -e open kwin_x11 2>&1 | grep config

Kudos to your persistence in finding the root cause of the bug!


There are still issues, when I was running through all the tests with 
moving configuration files out of the way and back again, the underlying 
libraries stayed the same.


What I've encountered is that the lock-ups are related to upgrades of 
underlying libraries. I use prelink after each upgrade of packages, and 
on re-reading the kdeinit5 manual page today, discovered the 
KDE_IS_PRELINKED environmental variable, which I've now set in the lxdm 
start-up script's call to start lxdm and run up iceweasel successfully 
under KDE plasma since then.


Arthur.

Re: possible cause? Re: iceweasel locking up under KDE, fine under Xfce

[Arthur Marsh]

Carsten Pfeiffer wrote on 16/01/16 00:09:

On Friday 15 January 2016 23:00:13 Arthur Marsh wrote:


Is there any documentation on what configuration file(s) kwin_x11 uses?


You can try starting kwin with strace, like this (when it's not running at the
moment):

strace -f -e open kwin_x11 2>&1 | grep config

Kudos to your persistence in finding the root cause of the bug!

Best wishes
Carsten


Thanks, I only thought of using strace after I noticed the lack of 
documentation on where kwin_x11 obtains configuration information.


(I've saved that command line for reference).

Way back I used to use the SVR4 truss command to find what files 
programs were accessing.

Re: possible cause? Re: iceweasel locking up under KDE, fine under Xfce

[Arthur Marsh]

Arthur Marsh wrote on 15/01/16 16:54:
...
My next step in debugging was to rename the ~/.config directory when 
logged out of KDE plasma, and then logging in and starting iceweasel.


That ran fine, so I reverted the ~/.config directory and moved the 16 
most recently modified files and directories under it out the way, and 
again logged into KDE plasma and started iceweasel, leading to a lock-up.


I then moved the next 16 most recently modified files and directories 
under ~/.config out the way and logged into KDE plasma and started 
iceweasel successfully.


That would suggest that one or more of the second group of 16 of files 
and directories under ~/.config were responsible for the lock-up.


However, after several cycles of logging out of of the KDE plasma 
desktop, moving the files and directories back a few at a time, and 
logging back in again, at no stage did I experience another lock-up.


I did find that kwin was not using the Plastik style that I had 
previously, (and some other window behaviours were also different from 
how I had set them) so I changed them under "Window Manager Settings" 
and was again able to log out of KDE plasma and back in again and run 
iceweasel without problems.


It appears that there was some configuration that kwin_x11 was reading 
that had lead to the lock-up on loading iceweasel, but I have no way of 
finding what that was now.


Is there any documentation on what configuration file(s) kwin_x11 uses?

If I had known specifically where to find settings and move them out the 
way for testing purposes, I could have saved some time in isolating the 
problem.


Arthur.

Re: possible cause? Re: iceweasel locking up under KDE, fine under Xfce

[Arthur Marsh]

Diederik de Haas wrote on 15/01/16 11:13:

On Friday 15 January 2016 11:02:45 Arthur Marsh wrote:

I've used a stock Debian kernel and removed oldstable packages and still
seeing the same thing happening.


I think your last report was way better then (all) your other reports.
I don't know whether that will give ppl with relevant knowledge enough to go
on, because so far it is unreproducable for others. It's working fine here.

Have you tried creating a new user and can you confirm whether the issue then
still occurs?



This is where it gets really mystifying.

I copied my iceweasel profile (~/.mozilla/firefox/profiles.ini and 
~/.mozilla/firefox/vl23iilx.default directory tree) to a new account, 
and started iceweasel in KDE plasma without issue.


I then went to my original account:

cd
cd .mozilla
ls -al

drwxr-xr-x   7 amarsh04 amarsh04   4096 Jan 15 16:34 .
drwxr-xr-x 342 amarsh04 amarsh04 204800 Jan 15 16:34 ..
-rw-r--r--   1 amarsh04 amarsh04335 Nov  9  2008 appreg
drwxr-xr-x   3 amarsh04 amarsh04   4096 Apr 10  2009 default
drwx--   3 amarsh04 amarsh04   4096 Sep 14  2009 extensions
drwxr-xr-x   5 amarsh04 amarsh04   4096 Apr  9  2015 firefox
drwxr-xr-x   3 amarsh04 amarsh04   4096 Apr 10  2009 fonts
drwxr-xr-x   3 amarsh04 amarsh04   4096 Apr 10  2009 iceweasel
-rw-r--r--   1 amarsh04 amarsh04   1375 Mar 20  2006 mozver.dat
-rw---   1 amarsh04 amarsh04   6526 Sep  4  2008 oldpluginreg.dat

I moved everything except the empty fonts directory and firefox 
directory out the way, then restarted iceweasel under KDE plasma without 
problems.


I then quit iceweasel, moved the old directories and mozver.dat and 
oldpluginreg.dat back and was able to start iceweasel under KDE plasma 
without problems.


Even if iceweasel had completely locked up, should it lock up the rest 
of the plasma desktop with it?


Arthur.

Re: possible cause? Re: iceweasel locking up under KDE, fine under Xfce

[Arthur Marsh]

Diederik de Haas wrote on 14/01/16 22:08:

On Thursday 14 January 2016 14:40:53 Arthur Marsh wrote:

This seems to narrow the problem down to package kinit (bug reported as
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806213 ), although I
wonder what kwin_x11 has to do with things.


I'm pretty sure your issue are caused by your own compiled kernel.
And having unstable through oldstable in your sources.list doesn't help
either.



I've used a stock Debian kernel and removed oldstable packages and still 
seeing the same thing happening.


If I kill -9 the kwin_x11 process after a lock-up, iceweasel continues 
loading to completion.


If I start plasma desktop, kill kwin_x11 and then start iceweasel, 
iceweasel successfully loads. kwin_x11 can then be resarted alright.


Arthur.

Re: possible cause? Re: iceweasel locking up under KDE, fine under Xfce

[Arthur Marsh]

Arthur Marsh wrote on 05/01/16 06:22:

Arthur Marsh wrote on 04/01/16 17:15:


PS, the problem listed at https://bugs.kde.org/show_bug.cgi?id=356580
also seems to apply to kinit 5.17.0-1 in the reported case. I don't know
if the kinit/kwin-x11 in Debian unstable have the same problem.

Arthur.


Applying the fix at https://git.reviewboard.kde.org/r/126361/
against the kwin 4:5.4.3-1.1 sources has at least enabled me to use KDE
again - iceweasel and other applications start up fine, although kwin
does give a crash indication and apparently restarts.


After finally discovering that if I killed kwin_x11 in plasma desktop, I 
could start iceweasel fine then restart kwin_x11, I also learned that 
using F2 could start an application using krunner (and that launced 
iceweasel successfully when kwin_x11 was running).


This seems to narrow the problem down to package kinit (bug reported as 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806213 ), although I 
wonder what kwin_x11 has to do with things.


Arthur.

Re: possible cause? Re: iceweasel locking up under KDE, fine under Xfce

[Arthur Marsh]

Arthur Marsh wrote on 04/01/16 17:15:


PS, the problem listed at https://bugs.kde.org/show_bug.cgi?id=356580
also seems to apply to kinit 5.17.0-1 in the reported case. I don't know
if the kinit/kwin-x11 in Debian unstable have the same problem.

Arthur.


Applying the fix at https://git.reviewboard.kde.org/r/126361/
against the kwin 4:5.4.3-1.1 sources has at least enabled me to use KDE 
again - iceweasel and other applications start up fine, although kwin 
does give a crash indication and apparently restarts.


Arthur.

Re: possible cause? Re: iceweasel locking up under KDE, fine under Xfce

[Arthur Marsh]

Martin Steigerwald wrote on 29/12/15 17:34:

Am Mittwoch, 23. Dezember 2015, 23:11:59 CET schrieb Arthur Marsh:



Do you have any specific suggestions for a plasma-specific forum, or
just kde.org?


There are kde related user mailing lists for different languages. And well the
forums. Both should be easy to find via the search engine provider of your
choice.



Apologies, I accidentally sent my reply off-list rather than to the list:

Thanks, I had a look on kde.org for mailing lists, for users there are 
kde and kde-linux and then was able to find them on gmane.org via 
searching for the lists' email address, but the traffic appears to be 
quite low. Apart from that I only found developer lists.


Considering that the possible fix I found was implemented in kwin 5.5.1, 
is Debian KDE likely to be moving beyond kwin/plasma packages with 
source version 5.4.3 any time soon?


PS, the problem listed at https://bugs.kde.org/show_bug.cgi?id=356580 
also seems to apply to kinit 5.17.0-1 in the reported case. I don't know 
if the kinit/kwin-x11 in Debian unstable have the same problem.


Arthur.

Re: possible cause? Re: iceweasel locking up under KDE, fine under Xfce

[Arthur Marsh]

Martin Steigerwald wrote on 23/12/15 20:54:

Hi Arthur,



I'm again having to run under lxdm/xfce - am I the only person having
this problem with KDE?


As I think I said I have no issues with iceweasel on Plasma 5 session. Self-
compiled KF5 and KDEPIM together with Plasma 5 packages from Debian Sid.

Also I do not think above bug is related, cause it refers to a wayland
session. I pretty much guess that you are not using a wayland session, but an
X11 one.


I am using an X11 session, but can't think of any closer problem at the 
moment. I've previously filed a bug against kinit, Debian bug #806213.




Also I often do not notice new mails to this thread, cause even with Full HD
resolution the thread moved out towards the right. On any account I suggest
you take this up with Plasma developers or more Plasma specific user forums as
here you appear mostly talking with yourself. It may even make sense to try to
ask on IRC.


Do you have any specific suggestions for a plasma-specific forum, or 
just kde.org?




Filing an own bug report with a consice and detailed summary of your issue +
all data may also help, but it may happen it takes a while till you receive a
response. Anyway, during Christmas time and otherwise as well I would be
gentle in requesting developer time, but I imagine that a dev may be
interested into actually solving the issue provided that you are willing to
take the time to gather all data necessary to do it as the developer requests
you to. I made this experience recently, Sandro asked me to attach gdb to the
kmail process do find the root cause for issues with displaying inline pgp
encrypted mails. We did. And he fixed the issue.

On any account I suggest you look broader than this forum as it appears to me
that you did not receive any helpful hints there recently and the cause for
this may just be that no one knows.

As to display manager: I do use sddm. As thats the one that upstream uses and
I expect it to be the best tested one with a Plasma session.


Thanks for the detailed comments.

I'm happy to try things including building packages from source, but am 
not a C/C++ programmer.


Arthur.

Re: possible cause? Re: iceweasel locking up under KDE, fine under Xfce

[Arthur Marsh]

Arthur Marsh wrote on 20/12/15 09:29:

Arthur Marsh wrote on 19/12/15 21:43:

Arthur Marsh wrote on 19/12/15 14:01:


I managed to run KDE another day with iceweasel fine, then the more
recent updates stopped it again.

The general symptom is that the iceweasel windows lock up at the stage
when multiple windows are being restored. Unless one kills the kdeinit
processes, things in the graphical session are locked up until kdm is
stopped.

I'm running both machines without systemd/libsystemd0, but would like to
get it so that I can have accelerated video playback without tearing
(Radeon 3200HD/RS780).

Arthur.


After trying a few more things without success, replacing kdm with lxdm
has resulted in iceweasel starting fine under KDE again.

Arthur.


This appears to be a likely candidate for the cause of the problem:

https://bugs.kde.org/show_bug.cgi?id=356580

Arthur.


I'm again having to run under lxdm/xfce - am I the only person having 
this problem with KDE?


Arthur.

possible cause? Re: iceweasel locking up under KDE, fine under Xfce

[Arthur Marsh]

Arthur Marsh wrote on 19/12/15 21:43:

Arthur Marsh wrote on 19/12/15 14:01:


I managed to run KDE another day with iceweasel fine, then the more
recent updates stopped it again.

The general symptom is that the iceweasel windows lock up at the stage
when multiple windows are being restored. Unless one kills the kdeinit
processes, things in the graphical session are locked up until kdm is
stopped.

I'm running both machines without systemd/libsystemd0, but would like to
get it so that I can have accelerated video playback without tearing
(Radeon 3200HD/RS780).

Arthur.


After trying a few more things without success, replacing kdm with lxdm
has resulted in iceweasel starting fine under KDE again.

Arthur.


This appears to be a likely candidate for the cause of the problem:

https://bugs.kde.org/show_bug.cgi?id=356580

Arthur.

Re: iceweasel locking up under KDE, fine under Xfce

[Arthur Marsh]

Arthur Marsh wrote on 19/12/15 14:01:


I managed to run KDE another day with iceweasel fine, then the more
recent updates stopped it again.

The general symptom is that the iceweasel windows lock up at the stage
when multiple windows are being restored. Unless one kills the kdeinit
processes, things in the graphical session are locked up until kdm is
stopped.

I'm running both machines without systemd/libsystemd0, but would like to
get it so that I can have accelerated video playback without tearing
(Radeon 3200HD/RS780).

Arthur.


After trying a few more things without success, replacing kdm with lxdm 
has resulted in iceweasel starting fine under KDE again.


Arthur.

Re: iceweasel locking up under KDE, fine under Xfce

[Arthur Marsh]

Jimmy Johnson wrote on 17/12/15 14:52:


Besides XFCE4 I'm also looking at the "Trinity Desktop" ported to
Debian, currently I have both Jessie and Stretch installed with Trinity,
but I'm taking it slow, it's still a longtime before Stretch goes
finial, but it has been disturbing me with all the auto-stuff that's
being installed and working in the background, but I'm sure there will
be a lot of people who will love their new system, but it just don't
fell like a Debian System to me.


I managed to run KDE another day with iceweasel fine, then the more 
recent updates stopped it again.


The general symptom is that the iceweasel windows lock up at the stage 
when multiple windows are being restored. Unless one kills the kdeinit 
processes, things in the graphical session are locked up until kdm is 
stopped.


I'm running both machines without systemd/libsystemd0, but would like to 
get it so that I can have accelerated video playback without tearing 
(Radeon 3200HD/RS780).


Arthur.

Re: iceweasel locking up under KDE, fine under Xfce

[Arthur Marsh]

Arthur Marsh wrote on 15/12/15 16:18:


and the problem seems to have gone away with the upgrade of packages
based on kde4libs from 4:4.14.14-1 to 4:4.14.14-1+b1

Arthur.


Back again with a vengeance, I can't even bring up iceweasel in gdb 
under KDE without it locking up.


I can run iceweasel xfce alright though.

Arthur.

Re: iceweasel locking up under KDE, fine under Xfce

[Arthur Marsh]

Arthur Marsh wrote on 15/12/15 08:27:


I'm again seeing the problem after the libxml2 and gtk2 updates to
unstable: iceweasel locks up when started from kdeinit (the start menu),
but starts fine from a konsole window inside kde.

The problem occurs at a time when numerous iceweasel windows are coming up.

Still using vdpau and Radeon 3200HD with Linus' git head kernel.


...and the problem seems to have gone away with the upgrade of packages 
based on kde4libs from 4:4.14.14-1 to 4:4.14.14-1+b1


Arthur.

Re: iceweasel locking up under KDE, fine under Xfce

[Arthur Marsh]

Jimmy Johnson wrote on 15/12/15 07:49:

On 12/14/2015 10:16 AM, Jimmy Johnson wrote:

On 12/12/2015 11:52 PM, Luc Castermans wrote:

...

Yes you are right it should have nothing to do with the driver you have
installed, but since testing plasma it has so far been the case, there
is a big difference if you have the 'Nouveau' or 'Nvidia' driver
installed with the Nouveau driver SDDM dose not lose focus and I do not
have to click in the box to enter my password, this I have tested on 2
Stretch and my other Sid system and loosing mouse focus has not been a
problem with SDDM, I have 4 upstream plasma systems. Currently I'm going
to keep the Nvidia Driver installed on the one Sid system because
outside of loosing focus on SDDM it other wise seems to be working, but
I need to spend more time with it.


I'm already back to using the nouveau driver..The Nvidia driver or the
Debian Nvidia driver do not work with the new kernel, on the plus side
SDDM is now working and not loosing focus.  Plasma still crashes for no
apparent reason.


I'm again seeing the problem after the libxml2 and gtk2 updates to 
unstable: iceweasel locks up when started from kdeinit (the start menu), 
but starts fine from a konsole window inside kde.


The problem occurs at a time when numerous iceweasel windows are coming up.

Still using vdpau and Radeon 3200HD with Linus' git head kernel.

Arthur.

Re: iceweasel locking up under KDE, fine under Xfce

[Arthur Marsh]

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.

Re: iceweasel locking up under KDE, fine under Xfce

[Arthur Marsh]

Arthur Marsh wrote on 26/11/15 23:10:

Martin Steigerwald wrote on 25/11/15 08:46:

Am Montag, 23. November 2015, 15:30:19 CET schrieb Arthur Marsh:

Arthur Marsh wrote on 19/11/15 16:26:

It appears that the fix applied to qt5base-opensource-src 5.5.1+dfsg-8
in relation to the bug: https://bugreports.qt.io/browse/QTBUG-46323
has improved things.


The new gcc-5 libraries seemed to have caused problems also.

Both iceweasel and chromium locking up today.


Both run stable here. With Intel Sandybridge graphics (still on UXA,
although
EXA might be fine again).



Thanks, I've been able to shut down slightly more gracefully by killing
the kdeinit5 processes after killing the browser processes.

I've only had one lock-up with chromium started from the KDE start menu
(kdeinit5) today, but iceweasel still needs to be started from a konsole
command line to avoid locking up.

Arthur.




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.

Re: iceweasel locking up under KDE, fine under Xfce

[Arthur Marsh]

Martin Steigerwald wrote on 25/11/15 08:46:

Am Montag, 23. November 2015, 15:30:19 CET schrieb Arthur Marsh:

Arthur Marsh wrote on 19/11/15 16:26:

It appears that the fix applied to qt5base-opensource-src 5.5.1+dfsg-8
in relation to the bug: https://bugreports.qt.io/browse/QTBUG-46323
has improved things.


The new gcc-5 libraries seemed to have caused problems also.

Both iceweasel and chromium locking up today.


Both run stable here. With Intel Sandybridge graphics (still on UXA, although
EXA might be fine again).



Thanks, I've been able to shut down slightly more gracefully by killing 
the kdeinit5 processes after killing the browser processes.


I've only had one lock-up with chromium started from the KDE start menu 
(kdeinit5) today, but iceweasel still needs to be started from a konsole 
command line to avoid locking up.


Arthur.

Re: Mayday : actually kde freeze always

[Arthur Marsh]

MERLIN Philippe wrote on 24/11/15 02:24:


Further to the last ones update Debian: gcc-5, libstdc kde jams
constantly, in the starting up with the only one the screen of starting
up and visible progress, black screen...


I had similar problems, so far my solution was to upgrade chromium to 
the version in experimental and go into single user mode or reboot to 
ensure that dbus had been shut down and restarted after any lock-up.


I'm running on an ASUS motherboard with onboard Radeon 3200HD graphics 
(RS780) with mesa-vdpau-drivers installed.


Arthur.

Re: iceweasel locking up under KDE, fine under Xfce

[Arthur Marsh]

Arthur Marsh wrote on 19/11/15 16:26:


It appears that the fix applied to qt5base-opensource-src 5.5.1+dfsg-8
in relation to the bug: https://bugreports.qt.io/browse/QTBUG-46323
has improved things.


The new gcc-5 libraries seemed to have caused problems also.

Both iceweasel and chromium locking up today.

Arthur.

Re: [Solved] Re: App Icons in Task Bar

[Arthur Marsh]

Brad Rogers wrote on 20/11/15 22:20:

On Fri, 20 Nov 2015 12:17:31 +0100
Holger Schramm  wrote:

Hello Holger,


I have the same problem but it changes after the reboot. After one
reboot they are gone with the next some are back again. It's like
roulette but with icons in the taskbar :-/


I was sent a solution (off-list).  Thanks to Chris Dow for this;

-8X-
I recently had this same problem with generic icons.  This can be fixed
with a setting in the task manager.  Right click on the task manager and
go to 'Task Manager Settings'.  Then, uncheck 'Use launcher icons for
running applications'.

-Chris

-8X-


Not working for me unfortunately (icons for iceweasel and chromium not 
consistently showing under either setting of 'Use launcher icons for 
running applications').


Arthur.

Re: iceweasel locking up under KDE, fine under Xfce

[Arthur Marsh]

Arthur Marsh wrote on 19/11/15 10:46:

Arthur Marsh wrote on 17/11/15 19:18:


Funnily enough, iceweasel runs alright under KDE if started from the
command line in a konsole window, with or without gdb, but it locks up
if started from the K menu.

Arthur.


latest "fun" with the qt5base-opensource-src 5.5.1+dfsg-8 based packages:

iceweasel run under gdb in a konsole window under KDE locks up the
entire KDE session, but iceweasel run from the command line in a console
window under KDE runs fine.


After re-running iceweasel under gdb under KDE I can no longer reproduce 
the problem.


It appears that the fix applied to qt5base-opensource-src 5.5.1+dfsg-8 
in relation to the bug: https://bugreports.qt.io/browse/QTBUG-46323

has improved things.

Re: iceweasel locking up under KDE, fine under Xfce

[Arthur Marsh]

Arthur Marsh wrote on 17/11/15 19:18:


Funnily enough, iceweasel runs alright under KDE if started from the
command line in a konsole window, with or without gdb, but it locks up
if started from the K menu.

Arthur.


latest "fun" with the qt5base-opensource-src 5.5.1+dfsg-8 based packages:

iceweasel run under gdb in a konsole window under KDE locks up the 
entire KDE session, but iceweasel run from the command line in a console 
window under KDE runs fine.


Arthur.

Re: iceweasel locking up under KDE, fine under Xfce

[Arthur Marsh]

I had one success running:

genkdmconf

to get things working after a downgrade, but after another upgrade then
downgrade even genkdmconf doesn't help me.

Arthur.


Funnily enough, iceweasel runs alright under KDE if started from the 
command line in a konsole window, with or without gdb, but it locks up 
if started from the K menu.


Arthur.

Re: iceweasel locking up under KDE, fine under Xfce

[Arthur Marsh]

Arthur Marsh wrote on 17/11/15 14:39:

Arthur Marsh wrote on 10/11/15 10:19:

Arthur Marsh wrote on 10/11/15 08:22:

Arthur Marsh wrote on 10/11/15 07:49:

For the second time I'm seeing this bug:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804060

some upgrade in the last few days did it, my local Debian mirror wasn't
updating and when I switched to an alternative had over 100 packages to
update.


I'm getting similar problems after upgrading packages based on
qtbase-opensource-src (lots of libqt5* packages) from -6 to -7.

Even after downgrading, I had to log in and out of KDE before being able
to run iceweasel successfully.

Arthur.


I had one success running:

genkdmconf

to get things working after a downgrade, but after another upgrade then 
downgrade even genkdmconf doesn't help me.


Arthur.

Re: iceweasel locking up under KDE, fine under Xfce

[Arthur Marsh]

Arthur Marsh wrote on 10/11/15 10:19:

Arthur Marsh wrote on 10/11/15 08:22:

Arthur Marsh wrote on 10/11/15 07:49:

For the second time I'm seeing this bug:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804060

some upgrade in the last few days did it, my local Debian mirror wasn't
updating and when I switched to an alternative had over 100 packages to
update.


I'm getting similar problems after upgrading packages based on 
qtbase-opensource-src (lots of libqt5* packages) from -6 to -7.


Even after downgrading, I had to log in and out of KDE before being able 
to run iceweasel successfully.


Arthur.

Re: iceweasel locking up under KDE, fine under Xfce

[Arthur Marsh]

Arthur Marsh wrote on 10/11/15 08:22:

Arthur Marsh wrote on 10/11/15 07:49:

For the second time I'm seeing this bug:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804060

some upgrade in the last few days did it, my local Debian mirror wasn't
updating and when I switched to an alternative had over 100 packages to
update.

The problem could be related to using a Radeon3200HD onboard graphics
chip / vdpau.

I'll try removing vdpau libraries and downgrading likely libraries and
am open to other suggesitons to try to isolate the cause.

The only error I get in dmesg is:

[  308.499736] kactivitymanage[4194]: segfault at 7f7a85b35cd0 ip
00302bc14291 sp 7ffce281db78 error 4 in
libQt5Sql.so.5.5.1[302bc0+3f000]
[ 1088.569088] kactivitymanage[4828]: segfault at 7fdfc616ecd0 ip
00302bc14291 sp 7fff3a3658d8 error 4 in
libQt5Sql.so.5.5.1[302bc0+3f000]

Arthur.




I moved the r600 vdpau libraries out the way and restarted X and kdm and
the problem did not occur, however I'd still like to pinpoint the cause.

Arthur.




After another try with no r600 vdpau library, KDE again locked up when 
starting iceweasel.


I had a look with gdb --pid on the pid's of iceweasel, kwin_x11 and 
plasmashell, which had the most cpu showing in top in a konsole window 
when the lockup occurred, and also for the Xorg process. All processes 
except iceweasel seemed to be stuck in poll or select.


iceweasel showed at the end of a bt full:

#60 0x7f1828971680 in  ()
#61 0x0581 in  ()
#62 0x7ffc63cdc970 in  ()
Python Exception  int too big to convert:
#63 0x in  ()#64 0x7f18273f6740 in 
js::jit::DoSetPropFallbackInfo () at /usr/lib/iceweasel/libxul.so

#65 0x7f180c951a60 in  ()
#66 0x7f1801c1a9fc in  ()
#67 0x0881 in  ()
#68 0x7ffc63cdc9d8 in  ()
#69 0x7f17f3e9e980 in  ()
---Type  to continue, or q  to quit---
Python Exception  int too big to convert:
Python Exception  int too big to convert:
Python Exception  int too big to convert:
Python Exception  int too big to convert:
Python Exception  int too big to convert:
Python Exception  int too big to convert:
#70 0x in  ()#71 0x in  ()#72 
0x in  ()#73 0x in  ()#74 
0x in  ()#75 0x in  ()#76 
0x in  ()


Any suggestions for further debugging welcome.

Arthur.

Re: iceweasel locking up under KDE, fine under Xfce

[Arthur Marsh]

Arthur Marsh wrote on 10/11/15 07:49:

For the second time I'm seeing this bug:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804060

some upgrade in the last few days did it, my local Debian mirror wasn't
updating and when I switched to an alternative had over 100 packages to
update.

The problem could be related to using a Radeon3200HD onboard graphics
chip / vdpau.

I'll try removing vdpau libraries and downgrading likely libraries and
am open to other suggesitons to try to isolate the cause.

The only error I get in dmesg is:

[  308.499736] kactivitymanage[4194]: segfault at 7f7a85b35cd0 ip
00302bc14291 sp 7ffce281db78 error 4 in
libQt5Sql.so.5.5.1[302bc0+3f000]
[ 1088.569088] kactivitymanage[4828]: segfault at 7fdfc616ecd0 ip
00302bc14291 sp 7fff3a3658d8 error 4 in
libQt5Sql.so.5.5.1[302bc0+3f000]

Arthur.




I moved the r600 vdpau libraries out the way and restarted X and kdm and 
the problem did not occur, however I'd still like to pinpoint the cause.


Arthur.

iceweasel locking up under KDE, fine under Xfce

[Arthur Marsh]

For the second time I'm seeing this bug:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804060

some upgrade in the last few days did it, my local Debian mirror wasn't 
updating and when I switched to an alternative had over 100 packages to 
update.


The problem could be related to using a Radeon3200HD onboard graphics 
chip / vdpau.


I'll try removing vdpau libraries and downgrading likely libraries and 
am open to other suggesitons to try to isolate the cause.


The only error I get in dmesg is:

[  308.499736] kactivitymanage[4194]: segfault at 7f7a85b35cd0 ip 
00302bc14291 sp 7ffce281db78 error 4 in 
libQt5Sql.so.5.5.1[302bc0+3f000]
[ 1088.569088] kactivitymanage[4828]: segfault at 7fdfc616ecd0 ip 
00302bc14291 sp 7fff3a3658d8 error 4 in 
libQt5Sql.so.5.5.1[302bc0+3f000]


Arthur.

Re: All dm's failing [SOLVED]

[Arthur Marsh]

Carlos Kosloff wrote on 08/11/15 03:29:

It was at the end of the thread, but anyway here it is again:
1) run genkdmconf as root.
2) cd /usr/share/kde4/apps/kdm/faces/
3) cp .default.face.icon .default.face
4) set kdm to start to plasma, instead of previous (default), so it will
not revert to broken, after that plasma should be default.
5) reboot a couple times, have your fingers crossed.


Thanks, I've sometimes done a plasma startup, then logged out having not 
started any applications under plasma, then logged in to plasma again to 
try to get things sane.


Arthur.

Re: All dm's failing [SOLVED]

[Arthur Marsh]

Carlos Kosloff wrote on 06/11/15 03:02:

On 11/03/2015 09:40 PM, Carlos Kosloff wrote:

After the botched upgrade involving libqt5x11extras5, my computer
cannot start normally.
The latest upgrades brought newer versions of sddm and
glx-alternative-*, which are now at 0.6.93.
sddm is also in the video group, in spite of all that sddm does not work
I purged and reinstalled kdm, no luck, it is broken with following error:
Cannot load /usr/share/kde4/apps/kdm/faces/.default.face: No such file
or directory
lightdm does not work either.
I am out of ideas.
Can somebody help?


What was the solution?

Arthur.

Re: sid KDE broken again - locks up when loading iceweasel

[Arthur Marsh]

Diederik de Haas wrote on 05/11/15 04:46:

On Thursday 05 November 2015 04:06:13 Arthur Marsh wrote:

I still get a lock-up with the stock Debian 4.2.0-1 kernel.
I hope that it isn't a sign of a GPU going bad...


Does the lockup also happen when you have your browser open but don't have a
tab with audio and/or video in it? I have had some weird issue with iceweasel
and that turned out to be caused by gstreamer.

It may be a long shot, but have you tried with a different init system, namely
with systemd? In the "Cannot shutown from plasma or sddm" it seemed to have
solved some weird issue ...



The problem has gone now, possibly due to a subsequent upgrade.

Thanks for all the suggestions!

Arthur.

Re: sid KDE broken again - locks up when loading iceweasel

[Arthur Marsh]

Arthur Marsh wrote on 04/11/15 23:44:

Diederik de Haas wrote on 04/11/15 22:52:

On Wednesday 04 November 2015 22:35:54 Arthur Marsh wrote:

Thanks, what I'm seeing is if I either upgrade the following packages to
the 5.5.1+dfsg-6 versions, or run a kernel later than 4.3.0 (or both), I
get the lock-up in KDE starting up iceweasel.
...
I could git-bisect the kernel if it would help provide clues.


I have the 5.5.1+dfsg-6 versions installed and I don't experience any
problems
with Iceweasel (I do always close the programs myself before logging
of/shutting down though).
I am running the 4.2.0-1-amd64 kernel though.

I did notice that logging out/shutting down takes a long(er) time then
it used
to be (>30 sec), but I don't know whether that's (in any way) relevant.



Thanks, I always shut down iceweasel and wait for the process to finish
before leaving KDE.

Xfce runs iceweasel fine with 5.5.1+dfsg-6 packges, but I experienced a
SIGPIPE when running iceweasel under KDE with gdb:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804060

That was under kernel 4.3.0 - I might try the stock Debian 4.2.0 kernel
later.

Arthur.




I still get a lock-up with the stock Debian 4.2.0-1 kernel.

I hope that it isn't a sign of a GPU going bad...

Arthur.

Re: sid KDE broken again - locks up when loading iceweasel

[Arthur Marsh]

Diederik de Haas wrote on 04/11/15 22:52:

On Wednesday 04 November 2015 22:35:54 Arthur Marsh wrote:

Thanks, what I'm seeing is if I either upgrade the following packages to
the 5.5.1+dfsg-6 versions, or run a kernel later than 4.3.0 (or both), I
get the lock-up in KDE starting up iceweasel.
...
I could git-bisect the kernel if it would help provide clues.


I have the 5.5.1+dfsg-6 versions installed and I don't experience any problems
with Iceweasel (I do always close the programs myself before logging
of/shutting down though).
I am running the 4.2.0-1-amd64 kernel though.

I did notice that logging out/shutting down takes a long(er) time then it used
to be (>30 sec), but I don't know whether that's (in any way) relevant.



Thanks, I always shut down iceweasel and wait for the process to finish 
before leaving KDE.


Xfce runs iceweasel fine with 5.5.1+dfsg-6 packges, but I experienced a 
SIGPIPE when running iceweasel under KDE with gdb:


http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804060

That was under kernel 4.3.0 - I might try the stock Debian 4.2.0 kernel 
later.


Arthur.

Re: sid KDE broken again - locks up when loading iceweasel

[Arthur Marsh]

Diederik de Haas wrote on 04/11/15 21:52:

On Wednesday 04 November 2015 21:30:30 Arthur Marsh wrote:

kactivitymanage[3999]: segfault at 7ff6c35c7cd0 ip 00302bc14291 sp
7ffc7b321ff8 error 4 in libQt5Sql.so.5.5.1[302bc0+3f000]


That is a known issue: https://bugs.debian.org/803451



Thanks, what I'm seeing is if I either upgrade the following packages to 
the 5.5.1+dfsg-6 versions, or run a kernel later than 4.3.0 (or both), I 
get the lock-up in KDE starting up iceweasel.


Setting up libqt5core5a:amd64 (5.5.1+dfsg-5) ...
Setting up qtbase5-dbg:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5concurrent5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5dbus5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5network5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5sql5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5sql5-sqlite:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5test5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5xml5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5xcbqpa5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5gui5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5widgets5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5opengl5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5printsupport5:amd64 (5.5.1+dfsg-5) ...

I could git-bisect the kernel if it would help provide clues.

Arthur.

sid KDE broken again - locks up when loading iceweasel

[Arthur Marsh]

Hi, I suspect that something broke for me as a result of this update 
process:


[UPGRADE] libqt5gui5:amd64 5.5.1+dfsg-5 -> 5.5.1+dfsg-6
[UPGRADE] libqt5network5:amd64 5.5.1+dfsg-5 -> 5.5.1+dfsg-6
[UPGRADE] libqt5opengl5:amd64 5.5.1+dfsg-5 -> 5.5.1+dfsg-6
[UPGRADE] libqt5printsupport5:amd64 5.5.1+dfsg-5 -> 5.5.1+dfsg-6
[UPGRADE] libqt5sql5:amd64 5.5.1+dfsg-5 -> 5.5.1+dfsg-6
[UPGRADE] libqt5sql5-sqlite:amd64 5.5.1+dfsg-5 -> 5.5.1+dfsg-6
[UPGRADE] libqt5test5:amd64 5.5.1+dfsg-5 -> 5.5.1+dfsg-6
[UPGRADE] libqt5widgets5:amd64 5.5.1+dfsg-5 -> 5.5.1+dfsg-6
[UPGRADE] libqt5xcbqpa5:amd64 5.5.1+dfsg-5 -> 5.5.1+dfsg-6
[UPGRADE] libqt5xml5:amd64 5.5.1+dfsg-5 -> 5.5.1+dfsg-6

the konsole window left open at log-out was not restored, and iceweasel 
would consume about 25 seconds of CPU time then the whole KDE session 
would lock up save for the graphical arrow cursor.


stopping kdm would result in the following error:

kactivitymanage[3999]: segfault at 7ff6c35c7cd0 ip 00302bc14291 sp 
7ffc7b321ff8 error 4 in libQt5Sql.so.5.5.1[302bc0+3f000]


iceweasel still ran fine in xfce

I downgraded the following packages:

Setting up libqt5core5a:amd64 (5.5.1+dfsg-5) ...
Setting up qtbase5-dbg:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5concurrent5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5dbus5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5network5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5sql5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5sql5-sqlite:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5test5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5xml5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5xcbqpa5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5gui5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5widgets5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5opengl5:amd64 (5.5.1+dfsg-5) ...
Setting up libqt5printsupport5:amd64 (5.5.1+dfsg-5) ...

and although konsole sessions would be restored, launching iceweasel 
would still result in a lock-up and shutting kdm would still result in a 
segfault in libQt5Sql.so.5.5.1.


Any suggestions for tracking this down further welcome.

Arthur.

Re: Help needed: watch up during sid updates/upgrades

[Arthur Marsh]

Robert van den Berg wrote on 25/10/15 16:50:

On Oct 25, 2015 6:08 AM, "Arthur Marsh" .


Still stuck as to what to do to restore being able to log into the

desktop.



If you just want to use a desktop, you can for instance install xfce as
backup. That helped me before.


Arthur.



Robert



Somehow between upgrading libdrm packages to 2.4.65-1, mesa to 11.0.4-1 
and a new kernel build with radeon updates, I can again use KDE from sid 
on x86-64.


Arthur.

Re: Help needed: watch up during sid updates/upgrades

[Arthur Marsh]

Arthur Marsh wrote on 25/10/15 14:40:

Lisandro Damián Nicanor Pérez Meyer wrote on 23/10/15 07:33:

As you might probably now we are currently under the Qtbase 5.5.1
transition
[tran]. It started yesterday and we are 50% done, so it's not going
bad at
all.

[tran]
<https://release.debian.org/transitions/html/qtbase-abi-5-5-1.html>

But there's a gotcha: now libqt5gui5 recommends libqt5xcbqpa5. Some
people are
having problems due to it not being installed. It reflects in the app
saying
that the xcb plugin is not present.


I've had further problems that persist after downgrading qtbase5-dev to
5.4.2+dfsg-9 and associated dependencies resulting in not being able to
login to a kwin session:

..xsession-errors:

Xsession: X session started for amarsh04 at Sunday 25 October  14:21:48
ACDT 2015
QCoreApplication::arguments: Please instantiate the QApplication object
first
QDBusConnection: session D-Bus connection created before
QCoreApplication. Application may misbehave.
This application failed to start because it could not find or load the
Qt platform plugin "xcb".

Available platform plugins are: eglfs, kms, linuxfb, minimal,
minimalegl, offscreen.

Reinstalling the application may fix this problem.

I'm not sure which application I'm supposed to reinstall.


After upgrading qtbase5-dev to 5.5.1+dfsg-4 and selecting kwin-x11 
4:5.4.2-1+b1 I get:


$ cat .xsession-errors
xprop:  unable to open display '192.168.1.100:0'
Xsession: X session started for amarsh04 at Sunday 25 October  14:48:02 
ACDT 2015
QCoreApplication::arguments: Please instantiate the QApplication object 
first
QDBusConnection: session D-Bus connection created before 
QCoreApplication. Application may misbehave.

QXcbConnection: Failed to initialize XRandr
The X11 connection broke: I/O error (code 1)
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
  after 6 requests (6 known processed) with 0 events remaining.

After switching to kwin-wayland 4:5.4.2-1+b1 I get:

$ cat .xsession-errors
xprop:  unable to open display '192.168.1.100:0'
Xsession: X session started for amarsh04 at Sunday 25 October  14:57:09 
ACDT 2015
QCoreApplication::arguments: Please instantiate the QApplication object 
first
QDBusConnection: session D-Bus connection created before 
QCoreApplication. Application may misbehave.

Qt: failed to retrieve the virtual modifier names from XKB
Qt: failed to retrieve the virtual modifier map from XKB
Qt: couldn't get core keyboard device info
libEGL warning: DRI2: xcb_connect failed
libEGL warning: DRI2: xcb_connect failed
No protocol specified
libEGL warning: DRI2: xcb_connect failed
No protocol specified
libEGL warning: DRI2: xcb_connect failed
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to 
'/tmp/runtime-amarsh04'

The X11 connection broke: I/O error (code 1)
XIO:  fatal IO error 2 (No such file or directory) on X server ":0"
  after 187 requests (187 known processed) with 0 events remaining.

Still stuck as to what to do to restore being able to log into the desktop.

Arthur.

Re: Help needed: watch up during sid updates/upgrades

[Arthur Marsh]

Lisandro Damián Nicanor Pérez Meyer wrote on 23/10/15 07:33:

As you might probably now we are currently under the Qtbase 5.5.1 transition
[tran]. It started yesterday and we are 50% done, so it's not going bad at
all.

[tran] 

But there's a gotcha: now libqt5gui5 recommends libqt5xcbqpa5. Some people are
having problems due to it not being installed. It reflects in the app saying
that the xcb plugin is not present.


I've had further problems that persist after downgrading qtbase5-dev to 
5.4.2+dfsg-9 and associated dependencies resulting in not being able to 
login to a kwin session:


.xsession-errors:

Xsession: X session started for amarsh04 at Sunday 25 October  14:21:48 
ACDT 2015
QCoreApplication::arguments: Please instantiate the QApplication object 
first
QDBusConnection: session D-Bus connection created before 
QCoreApplication. Application may misbehave.
This application failed to start because it could not find or load the 
Qt platform plugin "xcb".


Available platform plugins are: eglfs, kms, linuxfb, minimal, 
minimalegl, offscreen.


Reinstalling the application may fix this problem.

I'm not sure which application I'm supposed to reinstall.

Any suggestions welcome.

Arthur.

Re: friendly display of multiple timeones in plasma-desktop 4:5.4.0-2?

[Arthur Marsh]

Arthur Marsh wrote on 10/09/15 03:09:

In KDE 3.5.x and 4.x I could easily get a display of multiple timezones
in decent sized print with the name of the city next to them, but
despite adding multiple timezones to the current plasma-desktop only see
a few cryptic times (not as many as I picked and with the abbreviated
time-zone name rather than the city name).

How to I fix this under plasma-desktop 4:5.4.0-2?

Arthur.



OK, I found the city / time-zone name option but I still seem to be 
restricted to showing 5 different time-zones in a small font when I 
hover the mouse arrow over the clock.


What package should I report this problem against?

Arthur.

friendly display of multiple timeones in plasma-desktop 4:5.4.0-2?

[Arthur Marsh]

In KDE 3.5.x and 4.x I could easily get a display of multiple timezones 
in decent sized print with the name of the city next to them, but 
despite adding multiple timezones to the current plasma-desktop only see 
a few cryptic times (not as many as I picked and with the abbreviated 
time-zone name rather than the city name).


How to I fix this under plasma-desktop 4:5.4.0-2?

Arthur.

Re: help, lost the tops of windows in KDE 4.X

[Arthur Marsh]

Arthur Marsh wrote on 01/08/15 03:07:

Diederik de Haas wrote on 01/08/15 02:06:

On Saturday 01 August 2015 01:36:39 Arthur Marsh wrote:

[HOLD] plasma-desktop:amd64


Why are you holding plasma-desktop? It's pretty important.
Try installing qml-module-org-kde-kwindowsystem, which is also a
dependency of
plasma-desktop.



I'll try the previous upgrade with qml-module-org-kde-kwindowsystem as
well later today.

I'm trying to update things without having to install full systemd, just
libsystemd0 (and my other machine still runs KDE 3.5.9/10).

Arthur.




Installing qml-module-org-kwindowsystem then doing the upgrade:

kde-window-manager:amd64 4:4.11.13-2 -> 4:5.3.2-3

whilst leaving on hold:

[HOLD] kde-plasma-desktop:amd64
[HOLD] plasma-desktop:amd64

still left the tops of windows missing, even though kwin-x11 was 
automatically installed.


Arthur.


--
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/q2vt8c-uuj@ppp14-2-48-242.lns21.adl2.internode.on.net

Re: help, lost the tops of windows in KDE 4.X

[Arthur Marsh]

Diederik de Haas wrote on 01/08/15 02:06:

On Saturday 01 August 2015 01:36:39 Arthur Marsh wrote:

[HOLD] plasma-desktop:amd64


Why are you holding plasma-desktop? It's pretty important.
Try installing qml-module-org-kde-kwindowsystem, which is also a dependency of
plasma-desktop.



I'll try the previous upgrade with qml-module-org-kde-kwindowsystem as 
well later today.


I'm trying to update things without having to install full systemd, just 
libsystemd0 (and my other machine still runs KDE 3.5.9/10).


Arthur.


--
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/gbos8c-m9g@ppp14-2-48-242.lns21.adl2.internode.on.net

Re: help, lost the tops of windows in KDE 4.X

[Arthur Marsh]

Posting to Debian-kde as I'd accidentally replied to sender first instead:

Martin Steigerwald wrote on 22/07/15 01:28:
> Am Montag, 20. Juli 2015, 11:25:17 schrieb Arthur Marsh:
>> Hi, I've lost the tops of windows and hence the ability to move them,
>> and also the ability to switch tasks with alt-tab on my other machine
>> and wonder where I should go looking to fix this.
>
> Read the list.
>
> This is already becoming a FAQ.
>
> Install kwin-x11 package.
>
> Ciao,
>

I tried again with:

[INSTALL, DEPENDENCIES] kwin-common:amd64
[INSTALL, DEPENDENCIES] kwin-data:amd64
[INSTALL, DEPENDENCIES] kwin-x11:amd64
[INSTALL, DEPENDENCIES] libkdecorations2-5:amd64
[INSTALL, DEPENDENCIES] libkdecorations2private5:amd64
[INSTALL, DEPENDENCIES] libkf5waylandserver5:amd64
[INSTALL, DEPENDENCIES] libkwin4-effect-builtins1:amd64
[INSTALL, DEPENDENCIES] libkwineffects6:amd64
[INSTALL, DEPENDENCIES] libkwinglutils6:amd64
[INSTALL, DEPENDENCIES] libkwinxrenderutils6:amd64
[INSTALL, DEPENDENCIES] libqt5multimediaquick-p5:amd64
[INSTALL, DEPENDENCIES] libxcb-cursor0:amd64
[INSTALL, DEPENDENCIES] qml-module-qtmultimedia:amd64
[HOLD] kde-plasma-desktop:amd64
[HOLD] plasma-desktop:amd64
[UPGRADE] kde-window-manager:amd64 4:4.11.13-2 -> 4:5.3.2-3

and am still missing the tops of windows.

Downgrading as follows fixed things:

[REMOVE, NOT USED] kwin-common:amd64
[REMOVE, NOT USED] kwin-data:amd64
[REMOVE, NOT USED] kwin-x11:amd64
[REMOVE, NOT USED] libkdecorations2-5:amd64
[REMOVE, NOT USED] libkdecorations2private5:amd64
[REMOVE, NOT USED] libkf5waylandserver5:amd64
[REMOVE, NOT USED] libkwin4-effect-builtins1:amd64
[REMOVE, NOT USED] libkwineffects6:amd64
[REMOVE, NOT USED] libkwinglutils6:amd64
[REMOVE, NOT USED] libkwinxrenderutils6:amd64
[REMOVE, NOT USED] libqt5multimediaquick-p5:amd64
[REMOVE, NOT USED] libxcb-cursor0:amd64
[REMOVE, NOT USED] qml-module-qtmultimedia:amd64
[INSTALL, DEPENDENCIES] libkdecorations4abi2:amd64
[INSTALL, DEPENDENCIES] libkwineffects1abi5:amd64
[INSTALL, DEPENDENCIES] libkwinglesutils1:amd64
[INSTALL, DEPENDENCIES] libkwinglutils1abi2:amd64
[INSTALL, DEPENDENCIES] libxcb-xtest0:amd64
[DOWNGRADE] kde-window-manager:amd64 4:5.3.2-3 -> 4:4.11.13-2
[HOLD] kde-plasma-desktop:amd64
[HOLD] plasma-desktop:amd64


Arthur.



--
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/f1js8c-97c@ppp14-2-48-242.lns21.adl2.internode.on.net

Re: Help, lost vdpau and opengl output after accidentally starting chromium as root

[Arthur Marsh]

Arthur Marsh wrote on 27/07/15 13:36:

Somehow I tried to run chromium as root last night and now chromium
brings up a window, but with the window only showing the existing
background and not actually doing anything.

see: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793748

It is also difficult to quit chromium except by a kill -9 of the main
process.

A clue appeared when I was unable to run vlc (which uses vdpau by
default) or mpv (which uses opengl by default), getting the same
unresponsive windows.

Once I moved the vdpau libraries out of the way, mplayer ran ok using vx
and vlc ran ok (using xv?).

Where would I look for what was broken and what files might need to be
reinstalled?

KDE is mostly at 4:4.14-2-5 here.

I'm happy to supply any more information on request.


I pulled out the Radeon 3850HD video card and am now running with an 
onboard Radeon 3200HD video chip and the problem has disappearend.


Not sure if it was a hardware failure or an architectural difference 
that fixed things.


Arthur.


--
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/55b6fbb6.7090...@internode.on.net

Help, lost vdpau and opengl output after accidentally starting chromium as root

[Arthur Marsh]

Somehow I tried to run chromium as root last night and now chromium 
brings up a window, but with the window only showing the existing 
background and not actually doing anything.


see: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793748

It is also difficult to quit chromium except by a kill -9 of the main 
process.


A clue appeared when I was unable to run vlc (which uses vdpau by 
default) or mpv (which uses opengl by default), getting the same 
unresponsive windows.


Once I moved the vdpau libraries out of the way, mplayer ran ok using vx 
and vlc ran ok (using xv?).


Where would I look for what was broken and what files might need to be 
reinstalled?


KDE is mostly at 4:4.14-2-5 here.

I'm happy to supply any more information on request.

Arthur.


--
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/hang8c-im9@ppp14-2-48-242.lns21.adl2.internode.on.net

Re: help, lost the tops of windows in KDE 4.X

[Arthur Marsh]

Arthur Marsh wrote on 20/07/15 11:25:

Hi, I've lost the tops of windows and hence the ability to move them,
and also the ability to switch tasks with alt-tab on my other machine
and wonder where I should go looking to fix this.


Downgrading kde-window-manager to 4:4.11.13-2 fixed things for me.

I didn't want to go up to KDE 5 just yet.


--
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/55ac5ee0.7060...@internode.on.net

help, lost the tops of windows in KDE 4.X

[Arthur Marsh]

Hi, I've lost the tops of windows and hence the ability to move them, 
and also the ability to switch tasks with alt-tab on my other machine 
and wonder where I should go looking to fix this.	


Installed includes:

ii  kde-plasma-desktop5:77+deb7u1 
 amd64KDE Plasma Desktop and minimal set of 
applications
ii  kdm   4:4.11.13-2 
 amd64KDE Display Manager for X11
ii  plasma-desktop4:4.11.13-2 
 amd64KDE Plasma workspace for desktop and 
laptop computers


Some process of upgrading attempting to remove apparently un-needed 
packages lead to this situation and I've been experimenting, using the 
aptitude logs as a guide to re-installing things.


Any suggestions on what to check for or do to restore this functionality 
are welcome.


I'm happy to supply more details as needed.

Arthur.


--
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/511u7c-3n8@ppp14-2-48-242.lns21.adl2.internode.on.net

Re: Nepomuk always indexing at the beginning of every session

[Arthur Marsh]

Valerio Passini wrote, on 19/09/10 20:25:

Alle domenica 19 settembre 2010, Arthur Marsh ha scritto:

Thanks, but I'm not sure how I would do that since I am running the
following versions (in other words, I updated some components as much
as possible without removing what was needed to keep 3.5.X programs
such as Quanta running):

ii  kdebase-runtime  4:4.2.4-2

ii  kdebase-bin 4:3.5.10.dfsg.1-2core binaries
for the KDE base module
ii  kdebase-data 4:3.5.10.dfsg.1-2shared data
files for the KDE base module
ii  kdebase-doc 4:3.5.10.dfsg.1-2developer
documentation for the KDE base module
ii  kdebase-doc-html 4:3.5.10.dfsg.1-2KDE base
documentation in HTML format
ii  kdebase-kio-plugins 4:3.5.10.dfsg.1-2core I/O
slaves for KDE

Regards,

Arthur.


IMHO you are mixing different packages (indeeed KDE 4.2 and KDE 3.5) and
anyhow, nepomuk has been disabled in Debian until KDE 4.4 that is not
what you actually have. Prabably you should not worry about it. Bye

Valerio




For the benefit of the mailing list archives, I solved teh problem by 
editing:


~/.kde/share/config/nepomukserverrc

and setting:

autostart=false

Unfortunately, there were no manual pages for nepomuk related 
executables and it was not clear to me how to start nepomuk in a nice'd 
or ionice'd way.


Arthur.


--
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/kguhm7-7sj@ppp121-45-136-118.lns11.adl6.internode.on.net

Re: Nepomuk always indexing at the beginning of every session

[Arthur Marsh]

Valerio Passini wrote, on 19/09/10 09:30:

Alle domenica 19 settembre 2010, Arthur Marsh ha scritto:



How does one disable nepomuk from starting?

I don't like programs deciding that they can run automatically
without being nice'd.

Arthur.


 From system-settings ->  Desktop Search. Uncheck where you can find
Enable semantic desktop...

Vale



Thanks, but I'm not sure how I would do that since I am running the 
following versions (in other words, I updated some components as much as 
possible without removing what was needed to keep 3.5.X programs such as 
Quanta running):


ii  kdebase-runtime  4:4.2.4-2

ii  kdebase-bin 4:3.5.10.dfsg.1-2core binaries for 
the KDE base module
ii  kdebase-data 4:3.5.10.dfsg.1-2shared data files 
for the KDE base module
ii  kdebase-doc 4:3.5.10.dfsg.1-2developer 
documentation for the KDE base module
ii  kdebase-doc-html 4:3.5.10.dfsg.1-2KDE base 
documentation in HTML format
ii  kdebase-kio-plugins 4:3.5.10.dfsg.1-2core I/O 
slaves for KDE


Regards,

Arthur.


--
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/82ggm7-a8v@ppp121-45-136-118.lns11.adl6.internode.on.net

Re: Nepomuk always indexing at the beginning of every session

[Arthur Marsh]

Andreas Bourges wrote, on 17/09/10 17:56:

Hi,

...I observe the same behaviour. Every morning my Laptop goes nuts after
logging in. This takes about 10 minutes, then everything is normal again. I
saw the nepomuk process in the process-list, too...

Andy

On Friday 17 September 2010 10:23:54 Valerio Passini wrote:

Hello, I would like to know if Nepomuk is misbehaving and if this is
happening only to me. At every new session, nepomuk starts indexing the
configured folders, even if no change has been made in them and the
database has data inside (i.e. it's possible to do a search and retrieve
results). Considering that the indexing process is very heavy on CPU,
this is really boring and at least a complete waste of resources.
Should I purge the database and start a new one? Is this a design flow?
Should I do a bugreport to nepomuk?
At the moment I run Sid with the KDE 4.5.1 packages available in the
semi-official repository.


How does one disable nepomuk from starting?

I don't like programs deciding that they can run automatically without 
being nice'd.


Arthur.


--
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/tctfm7-t0p@ppp121-45-136-118.lns11.adl6.internode.on.net

Re: What needs to improve in KDE 4?

[Arthur Marsh]

Dotan Cohen wrote, on 19/05/10 00:00:
...

KSCD has lost functionality from the KDE3 version to the KDE4 version.

I haven't been able to try later than the KDE 4.2.4 version:

https://bugs.kde.org/show_bug.cgi?id=190194



Thanks, Arthur. That might be a dupe of bug #109402:
https://bugs.kde.org/show_bug.cgi?id=109402


Thanks, that bug report is similar, but this functionality (copying text 
from freedb.org look-ups) *IS WORKING* in KSCD 4:3.5.9-3.


For now I use the console mode abcde (a better cd encoder) to work with 
freedb.org entries for CD's.


Arthur.


--
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/81qac7-8tj@ppp121-45-136-118.lns11.adl6.internode.on.net

Re: What needs to improve in KDE 4?

[Arthur Marsh]

Dotan Cohen wrote, on 10/05/10 23:38:

Please tell us what problems, bugs, or issues KDE 4 that make it
difficult to use. Please be very specific so that bugs can be filed
and the software can be fixed. General statements such as "KDE4 sux"
are not welcome, as they do not give any indication as to what can be
fixed.

Comparisons to KDE 3 are welcome, but please do not simply state
"should be like KDE 3". Rather, please state how KDE 4 behaves, and
how you would prefer it to behave (even if that means describing in
detail KDE 3 behaviour).

My intention is to file issues and get bugs fixed, not to fight.
Nobody is ordered to participate in this thread, but all are welcome.




KSCD has lost functionality from the KDE3 version to the KDE4 version.

I haven't been able to try later than the KDE 4.2.4 version:

https://bugs.kde.org/show_bug.cgi?id=190194

Arthur.


--
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/fsp8c7-poi@ppp121-45-136-118.lns11.adl6.internode.on.net

Re: KDE Issues under "Squeeze"

[Arthur Marsh]

Adrian von Bidder wrote, on 25/04/10 23:22:

Hi,

On Sunday 25 April 2010 05.49:44 lrhorer wrote:

KDE is much more stable, but still has problems.


Hmm.

Using KDE 4 for months now; currently 4.4 from experimental.  If that's
what'll end up in squeeze I wouldn't say "it has problems" in general.  KDE
certainly is far from bug-free, but it's very usable as an everyday desktop.
( Sune&  Co: you can consider this a general reportbug --kudos :-)

lrhorer: I recommend you update to the packages that are currently in
experimental and check if the problems are still there.  I'm sure bug
reports are welcome.  If you can be bothered to do the necessary work and
separately report packaging issues to the Debian bts and KDE 4.4 issues to
the KDE bug reporting sysstem, then all the better..

cheers
-- vbi



Agreed, but where do I file a bug in Debian to say that instructions on 
how to report a bug upstream and how to mark the bug originally reported 
in Debian has been forwarded upstream are lacking?


I've just attempted to do this with icedove ( 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579095 ) but how does 
one do this for the general case?


I found the instructions on marking a Debian bug as forwarded upstream 
not via the Debian wiki or any package's instructions on reporting bugs 
with packages upstream, but by a Google search which lead to:

http://www.debian.org/Bugs/server-control

Many packages do *not* list the upstream site for the package or how to 
report bugs upstream anywhere within /usr/share/doc/ but 
ideally they should be listed:


- in the manual page for the programs/configuration files for that package

- in /usr/share/doc/

and in the reportbug script for that package.

I do appreciate all the work of the Debian developers/packagers/release 
people, but please help "fill in the gaps" or "connect the dots" on how 
to go about reporting bugs that may affect both Debian users and the 
upstream package.


Arthur.


--
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/ge0ea7-1d2@ppp121-45-136-118.lns11.adl6.internode.on.net

Re: command line saving session

[Arthur Marsh]

Kevin Krammer wrote, on 23/01/10 22:28:

On Friday, 2010-01-22, roberto wrote:

hello
i am searching for a command line way to save the kde session, since
i'd like to place it into a script along with the command to suspend
the pc

i've found this command:
dcop ksmserver ksmserver saveCurrentSession

do you think it is right ?


Yes, that looks right for KDE3, the KDE4 equivalent should be
qdbus org.kde.ksmserver /KSMServer 
org.kde.KSMServerInterface.saveCurrentSession


Cheers,
Kevin


Is there a line break or word split somewhere there? I'm not running 
kde4 yet but would like to have the command in a workable state for 
future reference.


Arthur.


--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: KDE crash when effects & OpenGL enabled

[Arthur Marsh]

Manolete, ese artista... wrote, on 2009-10-16 23:43:

If someone has this same problem perhaps is possible to get "old"
packages somewhere on the net (?) If not, take a look to your Debian
CDs/USBs/whatever not too old, perhaps you have on them the working
version.


Try snapshot.debian.net for old versions of Debian packages.

Arthur.


--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: kdebase-runtime upgrade problems

[Arthur Marsh]

Modestas Vainius wrote, on 2009-08-05 23:40:

Hello,

On trečiadienis 05 Rugpjūtis 2009 16:49:57 Michele Alberti wrote:

Hi all,
This morning I'm updating my system and this is what aptitude said:

Errors were encountered while processing:
 /var/cache/apt/archives/kdebase-runtime_4%3a4.3.0-1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
dpkg: dependency problems prevent configuration of
kdebase-runtime-bin-kde4: kdebase-runtime-bin-kde4 depends on
kdebase-runtime (>= 4:4.3.0); however: Version of kdebase-runtime on system
is 4:4.2.4-2.
dpkg: error processing kdebase-runtime-bin-kde4 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 kdebase-runtime-bin-kde4

How can I deal with it? Do you have any ideas?
Regards,


Wait 2-3 hours and upgrade again. Btw, why do you repeat yourself?



Thanks for the quick turnaround, but it leaves me with an interesting 
situation.


I run most packages from unstable, but have kept KDE at 3.5.9/3.5.10 as 
my reason for running KDE in the first place was Quanta, which is still 
at 4:3.5.9-3, and does not "see" cervisia versions later than 4:3.5.9-3 
and needs kdebase-kio-plugins 4:3.5.X also.


I have been able to run KDE 3.5.9/3.5.10 with some KDE 4.X packages 
(e.g. okular) where X <= 2.4.


With KDE 4.3.Y hitting unstable, I have had to hold packages like okular 
at version 4.2.4 to avoid upgrading to KDE 4.X as the base environment.


Is it possible to migrate to KDE 4.3.Z and leave enough KDE 3.5.whatever 
compatibility to run programs such as Quanta and Rosegarden which are a 
long way from being ported to KDE 4.x with full functionality?


Regards,

Arthur.


--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: multiple KDE3.5.10 sessions and XDMCP

[Arthur Marsh]

jedd wrote, on 13/05/09 06:19:

On Monday 04 May 2009, Arthur Marsh wrote:

I'd like to have 2 KDE sessions possible on each box, one on vt7 and
one on vt8, and to be able to access one machine from the other using
XDMCP (or anything else that does not have significant overhead on a
slow pc).


 Hi Arthur,

 Did you resolve this one?  I seem to recall some magic in
 some /etc/ config files, but nothing too spectacular was
 required.  My K | Switch User breaks, but if I do K | Lock Screen,
 I can then login as another user, which starts the second
 session just fine.

 Does this approach work for you?

 J.




Yes, using the KDE 3.5 K menu's "switch user" worked, at least on my old 
machine (PII-266 running unstable). The new machine has a dual core 
amd64 cpu.


Is there any way to set up a second kdm login on vt8 without having to 
run "switch user" first?


I can post existing configuration files for both machines if someone can 
let me know which are important for doing this. I would like to restrict 
the remote logins to the other machine only (assigned 192.168.1.100 to 
the old and 192.168.1.101 to the new) and *not* use encryption as this 
would slow the PII-266 machine too much.


Thanks for your suggestion and any further help.

Arthur.


--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

multiple KDE3.5.10 sessions and XDMCP

[Arthur Marsh]

Hi, I have 2 boxes (one slow, one fast) running KDE3.5.9/10 using Debian 
unstable but one monitor.


I'd like to have 2 KDE sessions possible on each box, one on vt7 and one 
on vt8, and to be able to access one machine from the other using XDMCP 
(or anything else that does not have significant overhead on a slow pc).


in /etc/kde3/kdm/kdmrc I've set:

ServerVTs=-7,-8
StaticServers=:0,:1

but don't get a second kdm session on vt8 )-:.

the two machines have ip addresses 192.168.1.100 and 192.168.101 - I'd 
like to only allow XDMCP access from each other rather than:


*   #any host can get a login window

in /etc/kde3/kdm/Xaccess.

Does anyone have a recently confirmed configuration for this?

Arthur.


--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: For AMD64, Synaptic wants to remove konqueror, kdebase

[Arthur Marsh]

Valerio Passini wrote, on 2009-04-23 19:01:


KDE4 is still developing and it's missing some feature you may need:
Bluetooth it's completely missing, NetworkManager and K3b are missing
too, but you can use the KDE3 version without problems, Printer
manager is present but it has less features than before. Said that,
KDE4 is faster is prettier and is going to have a lot of more
features than KDE3. Bye

Valerio



Although KDE4 may be faster than KDE3, I'm finding some applications 
slower and less feature complete than their KDE3 counterparts ( e.g. 
kscd https://bugs.kde.org/show_bug.cgi?id=190194 ).


It would be good to have a list of KDE4 applications that are confirmed 
to be feature-complete with their KDE3 counterparts, and a list of KDE4 
applications that are believed to be feature-complete with their KDE3 
counterparts and a list of KDE4 applications that are available but 
known to need more work to be feature-complete with their KDE3 counterparts.


For now, I'm running unstable but not upgrading anything to a 4:4.2.2 
version.


Regards,

Arthur.


--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Kuickshow replacement in KDE 4.2.2

[Arthur Marsh]

Benjamí Villoslada wrote, on 13/04/09 23:53:

On Dilluns 13 Abril 2009 13:43:04 Alejandro Exojo wrote:

Have you checked if is still possible to have it installed? I have a mixed
3.5/4.2 environment, and I found no conflict that forced me to remove it.


$ apt-cache policy kuickshow
kuickshow:
  Installed: (none)
  Candidate: (none)
  Version table:
 4:3.5.9-3 0
100 /var/lib/dpkg/status

$ grep -i kuickshow /var/log/aptitude
[Suprimeix, no utilitzat] kuickshow
(KDE 3.5 to KDE 4 upgrade)
[Instal·la] kuickshow
(manual install)
[Suprimeix] kuickshow
(dist-upgrade. kdebase-kio-plugins and kdeeject removed too)

$ dpkg -l kuickshow
rc kuickshow 4:3.5.9-3


Is Gwenview the solution?
http://wiki.kde.org/tiki-index.php?page=KDE+4+Application+Cleanup

IMHO, is not a equivalent replacement, Gwenview is a much bigger
application, but is an improvement over Gimp. Even Okular it's a possible
better alternative.


Yes, is a bigger application. I try with Okular, thanks Alex :)



I found okular to be very heavy with file activity on start-up (see 
Debian bug #514542).


On comparison, they seem roughly equally light/heavy on start-up:

amars...@victoria:/victoriac$ time gwenview
gwenview(1512): Attempt to use QAction "edit_redo" with KXMLGUIFactory!
gwenview(1512): Attempt to use QAction "edit_undo" with KXMLGUIFactory!
kdeinit4: preparing to launch

real0m29.099s
user0m6.528s
sys 0m0.768s
amars...@victoria:/victoriac$ time okular
okular(1834): Attempt to use QAction "bookmark_action_0" with 
KXMLGUIFactory!


real0m27.253s
user0m5.364s
sys 0m1.456s
amars...@victoria:/victoriac$

I then compared the logs of running okular and gwenview under strace:

amars...@victoria:~$ grep open okular2.log|wc -l
498
amars...@victoria:~$ grep open gwenview2.log|wc -l
519
amars...@victoria:~$ grep stat64 okular2.log|wc -l
2538
amars...@victoria:~$ grep stat64 gwenview2.log|wc -l
3782
amars...@victoria:~$ grep stat64 okular2.log|sort -u|wc -l
656
amars...@victoria:~$ grep stat64 gwenview2.log|sort -u|wc -l
1208

This was for start-up, then selecting file, quit.

Is it just me or are the numbers of calls to stat64 excessive?

Arthur.


--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Discussions with no sense

[Arthur Marsh]

Sune Vuorela wrote, on 2009-04-13 20:08:

On 2009-04-13, Cassiano Leal  wrote:

I might be able to help with that, if it means what I think it does --
getting debian bugs that are not packaging bugs and filing them upstream, is
that it?


Basically, yes. (or locate them in bugs.kde.org)
And then set them to "forwarded" in the debian bug tracking system

To mark a debian bug forwarded, send a mail to the control bot with the
following content:

forwarded n http://bugs.kde.org/show_bug.cgi?id=m
thanks

with nnn being the debian bug number and  being the kde bug number


If that's the case, I would be more than happy to help, even though I don't
have much spare time either.


If a handful of people does this with a handful of bugs each week, it
adds up quite fast.


So, the big "all of Debian" picture is that packages.debian.org / 
bugs.debian.org and reportbug need to give instructions on when and how 
to search for and if necessary report a bug upstream and how to indicate 
on the Debian bug tracker that the bug has been forwarded upstream?


In the Debian-KDE case, if the instructions for reporting a kde-related 
bug provided when using reportbug or bugs.debian.org included how to 
search for a bug report and if necessary report a new bug at 
bugs.kde.org and how to mark the Debian-KDE bug as forwarded, then it 
would be easier for the average non-developer Debian user to do this.


If the above suggestions should be reported as a bug (feature request or 
wish-list item) against bugs.debian.org, please let me know how I go 
about doing so using reportbug.





Also, I must have missed the e-mail with the graphs, as I have no idea what
you're talking about, so if you could point me to them and also to some
beginner tips, that would be great.


http://users.alioth.debian.org/~pusling-guest/pkg-kde-buggraphs/ < graphs

http://pkg-kde.alioth.debian.org/bugs.html

/Sune


Arthur.


--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Pin to keep kde3.5.9?

[Arthur Marsh]

Jan De Luyck wrote, on 2009-04-13 03:57:

Hello,

After several unsuccessful tries... does anyone know what I have to pin/hold 
to keep KDE 3.5.9 instead of 4.2.2 in unstable?


Kind regards,

Jan


PS, I also keep, stable and testing in my /etc/apt/sources.list in 
addition to unstable.


Arthur.


--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Pin to keep kde3.5.9?

[Arthur Marsh]

Jan De Luyck wrote, on 2009-04-13 03:57:

Hello,

After several unsuccessful tries... does anyone know what I have to pin/hold 
to keep KDE 3.5.9 instead of 4.2.2 in unstable?


Kind regards,

Jan


I have not used pinning, but I'm keeping KDE 3.5.9/3.5.10 in unstable.

kdebase is kept at 4:3.5.10.dfsg.1-2,
and kappfinder, kdebase-bin, kdebase-data,
kdepasswd, konqueror
and kdm are at the 3.5.X settings.

I've also kept applets like knemo, klipper, kweather, kmix at the 
versions corresponding to KDE 3.5.X.


Other applications that I've kept at KDE 3.5.X version although an 
apparently compatible with KDE 4.2.2 version exists include:


kystemlog, kuser, cervisia, kommander, kompare, kdewebdev, 
kimagemapeditor, kfilereplace, konsole, kmess, kppp, kxsldbg,

kfind, kfloppy, ksysguard[d], klinkstatus, kdemultimedia-kio-plugins.

Hope this helps.

Arthur.


--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

When to report bugs upstream [was Re: Lancelot locks accessing NTFS partition]

[Arthur Marsh]

Hi, I'd like to preface this reply with the statement that I have read 
this entire thread, and have appreciated the Debian KDE maintainers 
efforts in general and Mark Purcell in particular.


Mark Purcell wrote, on 09/04/09 18:53:

On Thursday 09 April 2009 11:14:26 Boyd Stephen Smith Jr. wrote:

Are you aware about how many Debian packagers has the Qt/KDE team? Do you
imagine how many time is needed to handle this? And not only the KDE
people, but other teams as well.

If Debian can't shoulder the burden of maintaining KDE, they shouldn't be
packaging it.  Debian maintainers should be ready to receive bug reports
from Debian users.  I should not have to run another distribution or
compile KDE from source before I file a bug.


Boyd,

You are going to start seeing a lot more messages like this one when you file 
a bug with a Debian package. I am the Debian maintainer for the hplip package:


! For end user support please "Ask a question" at the
! upstream hplip support site:
!   https://answers.launchpad.net/hplip/+addquestion
!
! If you know that the bug you want to report is in the "upstream"
! code then please file report in the upstream hplip bug tracking system:
!   https://launchpad.net/hplip/+filebug
!
! If you feel that the bug is one that other Debian users should
! know about then you are welcome to file a report in the Debian BTS
! as well.  Please keep in mind, however, that managing bug reports
! is part of the maintainers' workload.



Perhaps KDE packages in Debian that are ports of upstream packages 
rather than Debian-specific [meta-]packages should include a similar text?


By the way, I can only make this suggestion where it will reach Debian 
KDE maintainers because there is a Debian-KDE user mailing list, 
debian-kde@lists.debian.org (which I can access via gmane.org as 
newsgroup gmane.linux.debian.user.kde). It would not be very helpful if 
I made this suggestion as a bug report against each KDE package in 
Debian, and reportbug doesn't seem to have a means of reporting a bug 
against a class of packages like all Debian KDE packages. (I did file 
bug #523584 about this, but this part of the Debian bug tracking system 
- making the bug tracking system more efficient - seems to be lacking 
attention).


[As an aside, HPLIP *DOES NOT EVEN HAVE ANY MAILING LISTS* and this was 
a barrier against finding and reporting bugs upstream against HPLIP )-:.]


Why have I done this?  Because I am not able to keep on top of the bugs 
reports, let alone the packaging upstream releases and the like to maintain 
this and other packages.  Also a lot of bugs are just upstream bugs and in 
most (all) cases it would be a lot better if the end user were talking 
directly to upstream.


Sure if another 5 people wanted to come and help with the bugs then I wouldn't 
have to do this, but there aren't 5 people helping, so the users reporting the 
bugs can help and forward the bug to the place where they will get the fastest 
response to their issues.


In a lot of cases the Debian maintain is on the upstream bug tracking list as 
well and will comment directly there when/ if things are being reported that 
are directly specific to the Debian package.


You don't need to run a different distribution to report a bug upstream.  
Upstream will happily take reports from any users and will respond to your 
issues. 

However if you report another upstream bug to the BTS, the Debian maintainer 
may not be in a position to forward the bug upstream for many days/ weeks/ 
months if at all.  So the end user doesn't get any feedback on their bug 
either.


Users don't need a 'bug-day' to forward bugs upstream.  Anyone can do that at 
any time and at any stage of the project.  I hope you are contributing with 
every post you are making here to debian-kde and also forwarding a bug 
upstream.  Takes me about 3-6 minutes per bug. Because that is what Debian is 
about.  Lots of people, like you, doing a little bit of work when they have 
some spare time.


After forwarding bugs upstream to the ALSA project, HPLIP, KDE, each 
requiring registration/username/password one wonders how many upstream 
packages one can report to. I will report "show-stopper" bugs upstream, 
but without instructions in the Debian bug tracking system on how to do 
so (as reportbug provides for), the effort required crosses many users' 
threshold for bug reporting. I've been happy to change configuration 
settings, recompile software and even perform a kernel git bisection on 
a PII-266 to get a bug fixed (thanks to a couple of lines of 
encouragement from waldi in #debian-kernel), but having to report 
upstream and getting no response nor any clue as to where in the source 
code the problem lies (e.g. HPLIP not accepting hyphens in printer 
names) is discouraging.




So with your next spare 3 minutes, look at the BTS, check if a bug is still 
relevant, forward it upstream, and mark it as forwarded in the BTS.


Mark


If you can show me how to forwar

Re: keeping kde 3.5.X base whilst upgrading applications

[Arthur Marsh]

Sune Vuorela wrote, on 07/04/09 20:31:

On 2009-04-07, Arthur Marsh  wrote:
Hi, some applications that are the reason I installed KDE in the first 
place will not have KDE 4.X versions for quite a while (Quanta Plus, 
Rosegarden). I intend to stay on KDE 3.5.X until all KDE applications 
that I use have KDE 4.X versions or better equivalent applications.


Quanta currently looks dead, for some reason, we have missed rosegarden.

I'd appreciate it if users in a similar situation could explain what 
worked and didn't work for them in trying to carry out the same goal.


At this stage I've upgraded libraries that were at 4.2.1 version to the 
new 4.2.2 version, along with some applications, but I have not upgraded 
the core parts of KDE that are still at 3.5.9/3.5.10. The only running 
KDE 4 app that the upgrade process notified me of was nepomukservicestub.


Good luck. Note that you now have both kde3 and kde4 using .kde


Quanta 3.5.X will work under KDE 4.X as long as the kde3 libraries are 
installed, according to Eric Laffoon, the lead developer. He has also 
stated that Quanta 4 will be out in the second half of 2009.


The other application that I don't want breaking under KDE 4.2.2 is k3b.

I did a fresh install of Debian unstable on a machine with Asus M3A7A 
Pro motherboard (having fouled things up by not noting BIOS settings 
before performing a BIOS upgrade - I had to disable all ACPI-related 
features in the BIOS and also had set SATA to IDE mode rather than AHCI 
mode). With a little bit of care selecting packages, I was able to 
install KDE 3.5.9/3.5.10 and some newer applications, using an 
/etc/apt/sources.list that contained stable, unstable and testing.


Arthur.


--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

keeping kde 3.5.X base whilst upgrading applications

[Arthur Marsh]

Hi, some applications that are the reason I installed KDE in the first 
place will not have KDE 4.X versions for quite a while (Quanta Plus, 
Rosegarden). I intend to stay on KDE 3.5.X until all KDE applications 
that I use have KDE 4.X versions or better equivalent applications.


I'd appreciate it if users in a similar situation could explain what 
worked and didn't work for them in trying to carry out the same goal.


At this stage I've upgraded libraries that were at 4.2.1 version to the 
new 4.2.2 version, along with some applications, but I have not upgraded 
the core parts of KDE that are still at 3.5.9/3.5.10. The only running 
KDE 4 app that the upgrade process notified me of was nepomukservicestub.


Thanks to the Debian KDE developers/packagers for easing the transition 
to KDE 4.X.


Arthur.


--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: New plasma-widgets

[Arthur Marsh]

Manolete, ese artista... wrote, on 2009-03-29 02:48:

Kweather intrigues me a lot. According to its name we can suppose
whta's its utility, but I haven't been able even to launch it by any
means :-/. Does it really work? I guess the programmers and the
packagers of every distro did test it before publishing, no? But even
in the KDE forum nobody could give an answer, everybody suggested
weather plasmoids as alternatives but it seems nobody knows what's
the deal with Kweather for  KDE4. Dark misteries of computing...


I installed kweather in kde 3.5.x by apt-get / aptitude then in the 
panel menu, select add applet to panel, and kweather appeared as an 
option then I added Adelaide to get the weather.


I have no idea how it is supposed to be launched in kde 4.x.

Arthur.


--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: replacement for kpdf for kde 4.X?

[Arthur Marsh]

Alejandro Exojo wrote, on 2009-02-09 01:22:
...
I suggest that you use Okular, and report bugs that you find. Also note that 
the PDF you linked to is badly served (blame Microsoft's IIS), since it 
says "Content-Type: .PDF", instead of application/pdf.




Bug#514542: Acknowledgement (okular: runs open() and stat64() 632 times 
on certain files in home directory)


[quote]
In running okular from a directory other than my home directory, opening
the file open dialogue, letting it load, then selecting cancel then
quitting okular, (where my home directory has 616 files not starting
with "." and the other directory has 583 files not starting with "."), I
had open() called 878 times and stat64() called 88522 times.
[end quote]

Arthur.


--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: replacement for kpdf for kde 4.X?

[Arthur Marsh]

Alejandro Exojo wrote, on 09/02/09 01:22:

El Domingo, 8 de Febrero de 2009, Arthur Marsh escribió:

Anyway, I was lead to believe that kde 4.X would not be slower than kde
3.5.X.


You are comparing Okular with KDPF, aren't you? This doesn't have to do with 
comparing KDE 3.5 with KDE 4.x. Okular started with the KPDF codebase, but 
it's really different in many ways. For example, Okular uses libpoppler to 
render PDFs, but KPDF uses xpdf.



What is the best way to achieve a fast, fully-documented pdf reader for
kde 3.5.X under Debian?


That depends on what you mean with "for KDE 3.5.x". If you mean a PDF reader 
done with KDE 3 libraries, then it's KPDF. However, I strongly recommend 
Okular, as it's a better application in general. Even if it uses KDE 4 
libraries, it's perfectly usable on a KDE 3 desktop. I've been using it since 
a _lot_ time ago, and to me it's perfectly stable. Although I understand that 
if you found one important PDF for you that makes Okular choke, then you will 
have a bad impression.


I suggest that you use Okular, and report bugs that you find. Also note that 
the PDF you linked to is badly served (blame Microsoft's IIS), since it 
says "Content-Type: .PDF", instead of application/pdf.




Thanks, but I'm talking about a file that is already saved to a local 
disk, albeit on fat-32. With kpdf it takes 15 seconds to open the file 
open dialogue on one large directory, but okular takes over 40 seconds 
on the same directory, even if I had previously done a file open in 
okular on the same directory.


I like a file open dialogue to read the *names* of files and directories 
first, and let the user pick a file or directory without first insisting 
on reading the beginning of each file to determine the file type.


Regards,

Arthur.


--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: replacement for kpdf for kde 4.X?

[Arthur Marsh]

Arthur Marsh wrote, on 08/02/09 23:26:

Hi, I had problems with lack of working help tool-tips and information
about copying text from encrypted pdfs in kpdf 0.5.9 using kde 3.5.10 in
Debian unstable (bug #514238) and was told that nothing would be done as
"KPDF is frozen solid and no more KDE 3 releases are planned, so it
cannot be done. (And Okular - KPDF successor in KDE 4 - does that, 
anyway.)"


However, Okular (at least the version in unstable) is *way* too slow
compared with kpdf, and when I reinstalled it and attempted to load a 
pdf via the command line, it crashed (Debian bug #514526). It also 
crashed when I loaded the same pdf (found at 
http://www.acma.gov.au/webwr/_assets/main/lib310648/ecs_disc_paper.pdf ) 
by first loading Okular and then selecting the file from the okular file 
menu.


The fix to this problem was to run

kbuildsycoca4 --noincremental

as the user.



I did also report the bug as http://bugs.kde.org/show_bug.cgi?id=183407

Anyway, I was lead to believe that kde 4.X would not be slower than kde
3.5.X.

What is the best way to achieve a fast, fully-documented pdf reader for
kde 3.5.X under Debian?


Arthur.





--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

replacement for kpdf for kde 4.X?

[Arthur Marsh]

Hi, I had problems with lack of working help tool-tips and information
about copying text from encrypted pdfs in kpdf 0.5.9 using kde 3.5.10 in
Debian unstable (bug #514238) and was told that nothing would be done as
"KPDF is frozen solid and no more KDE 3 releases are planned, so it
cannot be done. (And Okular - KPDF successor in KDE 4 - does that, anyway.)"

However, Okular (at least the version in unstable) is *way* too slow
compared with kpdf, and when I reinstalled it and attempted to load a 
pdf via the command line, it crashed (Debian bug #514526). It also 
crashed when I loaded the same pdf (found at 
http://www.acma.gov.au/webwr/_assets/main/lib310648/ecs_disc_paper.pdf ) 
by first loading Okular and then selecting the file from the okular file 
menu.


I did also report the bug as http://bugs.kde.org/show_bug.cgi?id=183407

Anyway, I was lead to believe that kde 4.X would not be slower than kde
3.5.X.

What is the best way to achieve a fast, fully-documented pdf reader for
kde 3.5.X under Debian?


Arthur.


--
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

QSettings: failed to open file '/etc/qt3/qt_plugins_3.3rc'

[Arthur Marsh]

I filed Debian bug report 484037 against kweather for the above error as 
well as failing to provide the capability to let kweather be configured.


Part of the problem appeared to be the permissions on 
/etc/qt3/qt_plugins_3.3rc:


-rw-r-   1 root root 1051 2008-05-31 20:21 qt_plugins_3.3rc

What applications use this file and how should its permissions be set?

Running Debian unstable, KDE 3.5.9, kernel 2.6.25.

Arthur.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Kontact, K3B Amarok 2?

[Arthur Marsh]

Sune Vuorela wrote, on 2008-04-23 22:41:

On 2008-04-23, Walt L. Williams <[EMAIL PROTECTED]> wrote:

On Wednesday, 23 April 2008 2:19 am, Carlos Alvarez wrote:
Kontact 4.0.70, K3B 1.95 and Amarok 2 Alpha are available 
for Opensuse. Can we expect the same from Debian soon?


Cheers


Hold on, I have K3B on my Etch system. 


Yes. but that's not the kde4 version. k3b 1.9x are for kde4.

SuSE combined various 
items and called it Kontact. 


No. Kontact is a kde thing. not a suse thing.

Similarly to Kinternet is also a SuSE 
thing. As far as a music player is concerned I prefer XMMS over 
Amarok. The lack of it in SuSE 10.3 is one of many thing I found 
disappointing that version when I made the move to it. 


xmms has been removed from debian post etch.


Pardon the off topic post but I do run KDE under Debian unstable.

I filed a bug against audacious as I can't get it to avoid skipping 
under load. xmms correctly configured will avoid skipping except under 
the most extreme load conditions (manually built under Debian unstable, 
PII-266 / 256 MiB RAM).


Any suggestions for an "officially" supported audio player that won't 
skip under load on Debian unstable / KDE?


Arthur.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

sound muted by kmix after upgrading ALSA

[Arthur Marsh]

Hi, see http://bugs.debian.org for bug #448263: alsa-source: artsd fails 
to start with ALSA 1.0.15 and sound has to be unmuted in kde.


Apart from manually removing startup files for kmix, is there any way to 
avoid this problem?


Arthur.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: k3b problems

[Arthur Marsh]

Michael Thaler wrote, on 03/06/07 00:29:

Hello,

I have a problem with k3b. If I start k3b with a blank CD or DVD in the CD/DVD 
drive, k3b hangs when started and I get the following kernel message:


Jun  2 16:40:20 tessa kernel: cdrom: This disc doesn't have any tracks I 
recognize!

Jun  2 16:40:29 tessa kernel: hdd: DMA timeout retry
Jun  2 16:40:34 tessa kernel: hdc: lost interrupt
Jun  2 16:40:39 tessa kernel: hdd: status timeout: status=0xd8 { Busy }
Jun  2 16:40:39 tessa kernel: ide: failed opcode was: unknown

However, if I start k3b with no CD/DVD in the drives or with data CD/DVDs in 
the drives, everything works fine. I can insert a blank CD/DVD after k3b 
started and I can then burn them without problems. 


My system is Debian SID. I have the following version of k3b installed:


[snip]

Any suggestions what to do to not hang my computer when starting k3b with a 
blanl CD/DVD in the drives?


Greetings,
Michael




What drive do you have, and what is the output of:

lspci -v|grep -i ide

I had to disable DMA on my CD-RW drive for it to work correctly. To do 
this, I had the following in /etc/hdparm.conf:


/dev/hdc {
dma = off
}


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Is prelink still required?

[Arthur Marsh]

Ritesh Raj Sarraf wrote, on 2007-05-31 06:06:

Hi,

I noticed that KDE is now linked with DT_GNU_HASH optimizations.

[EMAIL PROTECTED]:~$ readelf -a /usr/bin/kmail| grep HASH
  [ 3] .hash HASH08048148 000148 00028c 04   A  5  
0  4
  [ 4] .gnu.hash GNU_HASH080483d4 0003d4 0001d8 04   A  5  
0  4

 0x0004 (HASH)   0x8048148
 0x6ef5 (GNU_HASH)   0x80483d4


But I also noticed that many other applications (non-KDE) aren't linked with
this option.

Are any of you using prelink currently ?


Yes.


If yes, what have your experiences been overall (in the past and now in
present) with prelinking libraries ?


When I first read about prelinking and kde (5 or more years ago), I 
thought that it would significantly help with desktop GNU/Linux becoming 
more widely used. After all, who wants a long wait every time that they 
want to run a particular program?


I am running Debian Unstable (with KDE 3.5.6) at present on a 1998 era 
machine (PII-266, 256 MiB RAM, Cirrus Logic graphics card), so the 
machine is more likely to be CPU-bound than many machines.


At present prelinking kde programs seem to take longer than non-kde 
programs, presumably due to their being coded in C++ and having a large 
number of shared components, but the effort does appear to be worthwhile 
if programs become CPU-bound on start-up.


I haven't noticed any particular difference between prelinking now and 
in the past.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

FIXED: /etc/X11/Xsession was incorrectly a symbolic link to /etc/kde3/kdm/Xsession Re: KDE 3.5.7 in unstable and yes, we're working in KDE 4!

[Arthur Marsh]

After all the problems I had, I found that /etc/X11/Xsession was somehow 
a symbolic link to /etc/kde3/kdm/Xsession, and reinstalling x11-common 
fixed things. I have no idea how this came about, as the link was dated 
some time in 2005, and I have been running kde most of the time.


Thanks to everyone who offered suggestions.

Arthur.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: KDE 3.5.7 in unstable and yes, we're working in KDE 4!

[Arthur Marsh]

Kevin Krammer wrote, on 2007-05-24 19:46:

On Thursday 24 May 2007, Arthur Marsh wrote:

John Schmidt wrote, on 2007-05-24 11:18:

On Wednesday 23 May 2007 19:36, Arthur Marsh wrote:

Please visit bugs.debian.org and enter 425526 for the details.

I am eager for any more suggestions to try.
How about try moving your .kde/ to .kde.orig and try logging in again. 
If that works, then some configuration files in your .kde are not happy

with the upgrade.  Or you can try creating another user and logging in
via that user and seeing if things work.  Then it is a matter of tracking
down the offending settings in your original .kde/

John

Hi, I tried that early on and just tried it again in the last hour and
there was no difference to the problem.


Try moving ~/.qt or check if there are any lock files in there (starting with 
a dot, so they are hidden) and remove them.


I remember a weird case where Qt was hanging on one of its own lock files.

Cheers,
Kevin


Thanks for the suggestion, but that didn't change things.

date
Fri May 25 01:08:42 CST 2007
[EMAIL PROTECTED]:~$ ls -alt .qt
total 56
drwxr-xr-x   2 amarsh04 amarsh04  4096 2007-05-25 01:05 .
-rw-r--r--   1 amarsh04 amarsh04  1039 2007-05-25 01:05 qtrc
drwxr-xr-x 131 amarsh04 amarsh04 28672 2007-05-25 01:05 ..
-rw---   1 amarsh04 amarsh04 0 2007-05-25 00:58 .kstylerc.lock
-rw---   1 amarsh04 amarsh04 0 2007-05-25 00:58 
.qt_plugins_3.3rc.lock

-rw---   1 amarsh04 amarsh04 0 2007-05-25 00:51 .qtrc.lock
-rw-r--r--   1 amarsh04 amarsh04  2209 2007-05-21 15:44 qt_plugins_3.3rc
-rw-r--r--   1 amarsh04 amarsh04  2699 2007-05-20 12:15 qjackctlrc
-rw-r--r--   1 amarsh04 amarsh0470 2007-05-07 17:41 unixodbcrc
-rw-r--r--   1 amarsh04 amarsh04   113 2006-01-18 19:22 kstylerc
-rw-r--r--   1 amarsh04 amarsh04   315 2004-07-07 02:23 qt_plugins_3.2rc

After manually starting kde 3.5.7 by

DISPLAY=":0.0";export display
nohup startkde &

at 1:05 I have the following processes running:

 ps -ef|grep kd|more
root25 2  0 May24 ?00:00:07 [kblockd/0]
root  3164 2  0 May24 ?00:00:00 [cifsoplockd]
root 12736 1  0 01:03 ?00:00:00 /usr/bin/kdm -config 
/var/run/kd

m/kdmrc
amarsh04 12783 12750 42 01:03 ?00:03:21 /bin/sh 
/etc/kde3/kdm/Xsession /

usr/bin/startkde
amarsh04 17173 15127  0 01:05 tty2 00:00:00 /bin/sh /usr/bin/startkde
root 17251 1  0 01:05 tty2 00:00:00 start_kdeinit 
--new-startup +kcm

init_startup
amarsh04 17264 1  0 01:05 ?00:00:00 kdeinit Running...

amarsh04 17271 1  0 01:05 ?00:00:00 dcopserver [kdeinit] --nosid

amarsh04 17275 17264  0 01:05 ?00:00:00 klauncher [kdeinit] 
--new-startu

p
amarsh04 17291 1  2 01:05 ?00:00:08 kded [kdeinit] --new-startup

amarsh04 17394 1  0 01:05 ?00:00:00 ksmserver [kdeinit]

amarsh04 17399 17264  0 01:05 ?00:00:02 kwin [kdeinit] -session 
10e1de6d

6f0001118226173032566_1180020494_24829
amarsh04 17431 1  0 01:05 ?00:00:01 kdesktop [kdeinit]

amarsh04 17453 1  3 01:05 ?00:00:12 kicker [kdeinit]

amarsh04 17591 1  0 01:05 ?00:00:00 kaccess [kdeinit]

amarsh04 17595 17264  1 01:05 ?00:00:04 konsole [kdeinit] 
-session 10e5d

bccd500011723930850045910008_1180020490_546375 -name Qt-subapplication
amarsh04 17615 1  0 01:05 ?00:00:02 kmix [kdeinit] -session 
10e5dbcc

d500011767749810049050027_1180020490_438613
amarsh04 17631 1  0 01:05 ?00:00:00 knotify [kdeinit]

amarsh04 17639 1  0 01:05 ?00:00:00 klipper [kdeinit]


Regards,

Arthur.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: KDE 3.5.7 in unstable and yes, we're working in KDE 4!

[Arthur Marsh]

John Schmidt wrote, on 2007-05-24 11:18:

On Wednesday 23 May 2007 19:36, Arthur Marsh wrote:



Please visit bugs.debian.org and enter 425526 for the details.

I am eager for any more suggestions to try.


How about try moving your .kde/ to .kde.orig and try logging in again.  If 
that works, then some configuration files in your .kde are not happy with the 
upgrade.  Or you can try creating another user and logging in via that user 
and seeing if things work.  Then it is a matter of tracking down the 
offending settings in your original .kde/


John




Hi, I tried that early on and just tried it again in the last hour and 
there was no difference to the problem.


I now have a kdm debug log (with changed passwords (-:) on 
bugs.debian.org under bug 425526 showing what happens when I log in.


Arthur.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: KDE 3.5.7 in unstable and yes, we're working in KDE 4!

[Arthur Marsh]

Arthur Marsh wrote, on 2007-05-23 14:14:

Ana Guerrero wrote, on 2007-05-22 22:13:

Hello,

KDE 3.5.7 is being released today and it is already available in 
unstable.

If you're using i386 the update should go fine, if you're using another
arch, like amd64, some packages will not be available for your arch yet.

If you update while you're using your desktop enviroment and you 
notice some strange behaviour, please restart your desktop enviroment.
At the same time we have been working in kde 3.5.7, we have started to 
work in packaging KDE 4, and we're aiming to publish packages for the 
next

official development snapshot.

If you want to know how to contribute, take a look at our website:
http://pkg-kde.alioth.debian.org/

Ana




I had major problems with my upgrade.

After rebooting having installed kde 3.5.7-1, I would get the graphical 
login screen, but once I logged in I was left with the blue background 
and nothing else. The mouse moved and I could use ctrl alt F1 .. F6 and 
ctrl alt backspace but I could not get the desktop loading.


I finally returned to the desktop by some difficult to reproduce method 
of copying the /var/run/xauth/* file to ~/.Xauthority attempting to 
login via VT7 and then in a console session setting DISPLAY to ":0.0" 
and running startkde.


I'm at a real loss on how to go about finding the actual problem and
fixing things properly. Any suggestions?

(I'm copying this into Debian bug #425526, where I reported this).


I'm still no better off after purging kdm, re-installing kdm and 
dependent kde packages at Etch level (normally I run Sid), reinstalling 
hal, dbus, pam and their associated libraries. I've also tried changing 
between 2.6.20, 2.6.21 and 2.6.22 kernels to no avail.


Doing a graphical login results in one or two processes of the form:


/bin/sh /etc/kde3/kdm/Xsession /usr/bin/startkde

but nothing else under my username until I login via a console session, 
set DISPLAY=":0.0", then run


nohup startkde &

which brings up a kde desktop session which sooner or later crashes.

Please visit bugs.debian.org and enter 425526 for the details.

I am eager for any more suggestions to try.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: KDE 3.5.7 in unstable and yes, we're working in KDE 4!

[Arthur Marsh]

Ana Guerrero wrote, on 2007-05-22 22:13:

Hello,

KDE 3.5.7 is being released today and it is already available in unstable.
If you're using i386 the update should go fine, if you're using another
arch, like amd64, some packages will not be available for your arch yet.

If you update while you're using your desktop enviroment and you notice 
some strange behaviour, please restart your desktop enviroment. 

At the same time we have been working in kde 3.5.7, we have started to work 
in packaging KDE 4, and we're aiming to publish packages for the next

official development snapshot.

If you want to know how to contribute, take a look at our website:
http://pkg-kde.alioth.debian.org/

Ana




I had major problems with my upgrade.

After rebooting having installed kde 3.5.7-1, I would get the graphical 
login screen, but once I logged in I was left with the blue background 
and nothing else. The mouse moved and I could use ctrl alt F1 .. F6 and 
ctrl alt backspace but I could not get the desktop loading.


I finally returned to the desktop by some difficult to reproduce method 
of copying the /var/run/xauth/* file to ~/.Xauthority attempting to 
login via VT7 and then in a console session setting DISPLAY to ":0.0" 
and running startkde.


I'm at a real loss on how to go about finding the actual problem and
fixing things properly. Any suggestions?

(I'm copying this into Debian bug #425526, where I reported this).

Arthur.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: bug #403133 - print from kpdf fails, add file name to command and it works

[Arthur Marsh]

Modestas Vainius wrote, On 10/01/07 20:40:

Hi,

2007 m. sausis 10 d., trečiadienis 06:53, Arthur Marsh rašė:

A print error occurred. Error message received from system:

Unable to start child print process. Check the command syntax:
cupsdoprint -P 'CANON' -J '' -H '/var/run/cups/cups.sock:631' -U
'amarsh04' -o ' MediaType=Plain copies=1 orientation-requested=3
page-bottom=46 page-left=11 page-right=9 page-top=10'

However, if I copy the print command from above, add the file name to
the end and print from the command line, it prints fine.

Try logging off & logging on again.


OK, thanks, I could do a test print from KDE control centre after 
logging off and logging back on.


Usually, I wouldn't want to log out and log back in to do printing from 
KDE. Does anyone have any ideas what is actually going on and whether a 
permanent fix can be found?


Regards,

Arthur.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

bug #403133 - print from kpdf fails, add file name to command and it works

[Arthur Marsh]

Hi, I've encountered problems printing from kpdf that seem to match 
Debian Bug #403103 (original error message given in French, so I'm 
guessing, but I've added my case to the existing bug).


I get a dialogue box like:

A print error occurred. Error message received from system:

Unable to start child print process. Check the command syntax: 
cupsdoprint -P 'CANON' -J '' -H '/var/run/cups/cups.sock:631' -U 
'amarsh04' -o ' MediaType=Plain copies=1 orientation-requested=3 
page-bottom=46 page-left=11 page-right=9 page-top=10'


However, if I copy the print command from above, add the file name to 
the end and print from the command line, it prints fine.


Attempting to print from the KDE control centre gives the same result:

A print error occurred. Error message received from system:

Unable to start child print process. Check the command syntax: 
cupsdoprint -P 'CANON' -J '' -H '/var/run/cups/cups.sock:631' -U 
'amarsh04' -o ' MediaType=Plain 
multiple-document-handling=separate-documents-uncollated-copies 
orientation-requested=3 page-bottom=46 page-left=11 page-right=9 
page-top=10'


Any suggestions?


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Condensed font instead of Sans Serif in KDE

[Arthur Marsh]

Cédric Boutillier wrote, On 29/12/06 01:34:

Dear List,

For about a week, I have the following problem with my KDE Desktop
(up-to-date sid i386): it seems that the systems selects Dejavu Sans
Condensed instead of DejaVuSans, when "Sans" is selected in Kcontrol.
It results in a very ugly desktop. I got already this problem in the
beginning of December. It was then a problem with fontconfig and
ttf-dejavu, that was fixed by an upgrade of the system. But then the
problem reappeared a few days ago, and I do not know how to fix it.

I tried to dpkg-reconfigure several packages : fontconfig,
fontconfig-config, defoma, ttf-deja-vu, to purge and reinstall them,
but nothing changed. The only solution I found was to remove the
Condensed fonts from /usr/share/fonts/truetype/ttf-dejavu, but it does
not seem to be a good way of doing things in the long term.

I was not able to find a bug report concerning this problem. Moreover,
I have two others machines (powerpc and amd64) who do not suffer from
this problem (they did not suffer either when the same problem occured
a few weeks ago, since the versions of fontconfig/ttf-dejavu causing
the problem were not installed).

Does anybody know how I could fix this problem more properly than just
removing the files ? Only KDE applications suffer from this problem :
texmaker and iceweasel are displayed correctly.

Thanks in advance,

Cedric




Is it anything to do with what I reported here:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=401924

Arthur.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: [sarge] Konqueror 3.3.2 crashes

[Arthur Marsh]

Nick Boyce wrote, On 13/11/06 12:42:

On Saturday 12 November 2006 03:26, Nick Boyce wrote:


Over the last couple of weeks I've experienced a series of Konqueror
crashes using my vanilla Sarge system while surfing the web.  A common
feature seems to be Slashdot.  In every case, I had Slashdot pages open,
and in 3 cases the crash occurred immediately on opening an article link in
a new tab.

The crash is not repeatable - usually Konqueror behaves fine if I just
restart it and go back to Slashdot.  


Well ... it's getting worse.  Tonight I couldn't view Slashdot at all for 
several minutes.  Something on the front page was killing Konqueror as soon 
as the page started loading.  At one point the crash couldn't even produce a 
backtrace - the crash handler displayed a message saying a stack corruption 
prevented a valid backtrace from being produced.


It's gone away again now.

I've hunted around at bugs.kde.org, and similar crashes abound in Konqueror 
3.3.2 - in which KJS seems to be a common feature.  e.g. :

http://bugs.kde.org/show_bug.cgi?id=94934
http://bugs.kde.org/show_bug.cgi?id=107400
http://bugs.kde.org/show_bug.cgi?id=102632
http://bugs.kde.org/show_bug.cgi?id=109964

From the comments by the bug handlers it seems nobody is going to want to look 
further into my problem - a common response is "upgrade to 3.5.2 and see 
whether the problem's still there".


Oh well.  Might have to switch to Firefox till Etch gets released :(

PS: some of the bug reports talk about needing backtraces with debug symbols, 
or using debug builds ... can anyone tell me how one might do that ?


Cheers
Nick Boyce
Bristol, UK


You may need the kdebase-dbg kdelibs-dbg packages - they provide the 
debugging symbols for the kdebase packages and kdelibs libraries.


Arthur.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: problems starting KDE after xorg update

[Arthur Marsh]

[replying to all as op said he wasn't subscribed]

Dan Keshet wrote, On 2006-11-12 16:35:

I did an apt-get upgrade, upgrading both xserver-xorg (7.0-7.1) and kde
(3.5.4 to 3.5.5).  Following this, I had trouble starting the xserver,
which was fixed by updating my xorg.conf to use the new
/usr/share/fonts/X11... directories.

Now, I can start X with twm and kdm works fine, but once I start my kde
session (from "startkde" or kdm), kde spends a *really* long time at
"initializing system services", then eventually loads what looks like a
kde desktop with kicker running and everything, but the kmenu doesn't
respond to clicks and right-clicking the desktop does nothing.

Any ideas?


I found a slow start-up being due to fc-cache not having been run since 
the last font installation/update.


Try running (as root):

fc-cache -v

I have no suggestions on kmenu and right-clicking on the desktop not 
working as they've always worked for me. I'm running sid, so I do lots 
of small (daily) updates and look for help if/when anything breaks.


Arthur.



Dan

PS. I'm not subscribed to the mailing list, but I'll be checking it
regularly.





--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Any KDE way of reencoding id3 tags?

[Arthur Marsh]

Christoph Burgmer wrote, On 2006-11-02 05:55:

Hi list,

I'm living in the 21st century and just can't understand why my 
favourite software isn't able to display the id3 tags given to my mp3s. 
Support of multiple languages is something not only nice to have but 
something obligatory. Long story short: I can't work with my mp3s 
encoded in gbk*. Amarok developers aren't willing to support a method of 
specifying the encoding, so I end up with nothing but a hint to use 
easytag to convert them manually. easytag though again is ranting about 
some buggy version of "id3lib" and I am not willing to apply a patch.

Is there any help for somebody in a situation like this?

Thanks for any hints
Christoph Burgmer


What is gbk* ?

Although it is GTK+ based, exfalso seemed to be the best tag editor I 
could find in Debian unstable. I haven't done batch conversions although 
they appear to be supported - my needs were more along the line of utf-8 
support.


Arthur.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: kwin 4:3.5.5-1 causes problems (window flicker/flashing)

[Arthur Marsh]

Christophe Prud'homme wrote, On 2006-10-11 00:15:

[ Friday 6 October 2006 14:06 ]
| I've reported this as Debian bug #391357.
|
| After several combinations of upgrades and downgrades, I've found that
| the 3.5.5-1 versions of KDE packages work alright, but that kwin
| 4:3.5.5-1 causes flickering / flashing of windows when a window is in
| focus.
confirmed.
though when using the 'click to focus' policy, it is allright with kwin 
4:3.5.5-1


cu
C.


I since reported this problem on bugs.kde.org:

[Bug 135250] desktop unusable due to flickering of windows if not "focus 
follows click"


and a patch that fixes the problem has been released. See details at 
http://bugs.kde.org/135250


and a replacement kwin 3.5.5 i386 .deb is available at:

http://mirror.pusling.com/kwin_3.5.5-1_i386.deb

Arthur.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

kwin 4:3.5.5-1 causes problems (window flicker/flashing)

[Arthur Marsh]

I've reported this as Debian bug #391357.

After several combinations of upgrades and downgrades, I've found that 
the 3.5.5-1 versions of KDE packages work alright, but that kwin 
4:3.5.5-1 causes flickering / flashing of windows when a window is in focus.


Holding kwin at 4:3.5.4-2+b1 (and hence also kdebase) and upgrading 
other Debian KDE packages to 3.5.5-1 seem to work alright.


Hope that this saves someone else a few hours.

Arthur.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]