Bug#495506: [ksysguard] ksysguard crashes with "ProcessTable.sgrd does not contain valid XML"
Good morning Xavier, On Thu, Aug 21, 2008 at 04:11:44PM +0200, Xavier Vello wrote: > > > Can't reproduce the bug on 4:4.1.0-2. > > > Try removing ~/.kde4/share/apps/ksysguard/SystemLoad.sgrd , it may have > > > gotten corrupt. > > > > if I remove this file, I still get message, that the > > ProcessTable.sgrd file does not contain valid XML. But if I remove > > that file as well, I get ksysguard started. Though there is no > > possibility to scroll neither to active an entry to kill it via UI > Then try removing ~/.kde4/share/apps/ksysguard/* and > ~/.kde4/share/config/ksysguardrc for a fresh start. O.K. ... After I have done this, ksysguard starts as normal. > > > You can also try removing and reinstalling the ksysguard package if > > > it doesn't work. > > Yes, I know ... ;) Although I have not done it yet ... :( But why on > > earth leads an update to an non-functional prog? > Hard disks aren't perfect, think of bad sectors :) That may be, but the only problem I have is with ksysguard and nothing else ... And that old is neither my HD nor my PC at all (although there are some older disks attached to this PC ... ;) ). > dpkg has a md5 checksum check builtin, but it may have been corrupted > afterwards. Even if it's low probability, it's good to try it. As I am using apt-get to update my system, I have never tried to update my system via dpkg. And as I am short of time atm (and maybe the next months ... :( ), I am not able to read the dpkg documentation/man page and to test it, sorry ... :( As ksysguard works for me again, this bug could be closed as "worksforme", although I find it astonishing, that an system update via apt-get leads to an unfunctional program ... :( > > Thanks for your answer anyway and I hope it is OK, that I have > > answered your mail privately ... > You should always CC [EMAIL PROTECTED] when adding information, so > that it's archived on our BTS and easilly available for everyone. Sorry, I have not seen the [EMAIL PROTECTED] address in the reply, so I answered you instead of both ... :( Have a nice day Thomas. -- Gnagloot, n.: A person who leaves all his ski passes on his jacket just to impress people. -- Rich Hall, "Sniglets" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#495506: marked as done ([ksysguard] ksysguard crashes with "ProcessTable.sgrd does not contain valid XML")
Your message dated Fri, 22 Aug 2008 13:19:17 +0200 with message-id <[EMAIL PROTECTED]> and subject line close 495506 has caused the Debian Bug report #495506, regarding [ksysguard] ksysguard crashes with "ProcessTable.sgrd does not contain valid XML" to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 495506: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495506 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: ksysguard Version: 4:4.1.0-2 Severity: normal --- Please enter the report below this line. --- Hello all, after an experimental upgrade yesterday ksysguard opens the above mentioned message box, if I try to start it ... :( If I click the OK button (or hit enter) the next dialog tells me, that SystemLoad.sgrd does as well not contain valid XML. After that, the KDE Crash Handler appears to tell the user, that ksysguard has crashed ... :( It is reading the files from ~/.kde4/share/apps/ksysguard, if this is important ... HTH Thomas. --- System information. --- Architecture: amd64 Kernel: Linux 2.6.26-1-openvz-amd64 Debian Release: lenny/sid 990 unstablewww.debian- multimedia.org 990 unstablemirror.noreply.org 990 unstablekmuto.jp 990 unstableftp.debian-unofficial.org 990 unstableftp.de.debian.org 990 unstableemacs.orebokech.com 990 unstabledebian.wgdd.de 990 unstabledebian.hug.cx 990 unstabledebian.alphagemini.org 990 unstabledeb.opera.com 600 experimentalwww.debian- multimedia.org 600 experimentalftp.de.debian.org 600 experimentaldebian.wgdd.de 500 testing security.debian.org 500 stable dl.google.com 500 kernel-dists-sid kernel- archive.buildserver.net 500 experimental-0.2.0.x-sid mirror.noreply.org --- Package information. --- Depends (Version) | Installed ==-+- = kdebase-runtime (>= 4:4.1.0) | 4:4.1.0-2 kdebase-workspace-libs4+5 | 4:4.1.0-2 kdelibs5 (>= 4:4.1.0) | 4:4.1.0-2 libc6 (>= 2.7-1) | 2.8+20080809-1 libplasma2 | 4:4.1.0-2 libqt4-dbus (>= 4.4.0) | 4.4.1-1 libqt4-xml (>= 4.4.0) | 4.4.1-1 libqtcore4 (>= 4.4.0) | 4.4.1-1 libqtgui4 (>= 4.4.0) | 4.4.1-1 libstdc++6 (>= 4.1.1) | 4.3.1-9 -- love, n.: Love ties in a knot in the end of the rope. --- End Message --- --- Begin Message --- Not a packaging error. Bug closed. --- End Message ---
Bug#452602: kdebase-bin: Screen lock password check fails
Package: kdebase-bin Version: 4:3.5.9.dfsg.1-5 Followup-For: Bug #452602 I think I'm seeing the same problem. It started to happen after recent dist-upgrade which besides other things upgraded PAM libraries. It seems that at least in my case the fix is downgrading libpam-modules package to 0.99.7.1-7 version (I had 1.0.1-2 after upgrade). -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22-2-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=ru_RU.UTF8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kdebase-bin depends on: ii kdebase-bin-kde34:3.5.9.dfsg.1-5 core binaries for the KDE base mod ii kdelibs4c2a 4:3.5.9.dfsg.1-6 core libraries and binaries for al ii libc6 2.7-13 GNU C Library: Shared libraries ii libgcc1 1:4.3.1-2GCC support library ii libpam-runtime 1.0.1-2 Runtime support for the PAM librar ii libpam0g1.0.1-2 Pluggable Authentication Modules l ii libqt3-mt 3:3.3.8b-5 Qt GUI Library (Threaded runtime v ii libstdc++6 4.3.1-2 The GNU Standard C++ Library v3 ii libx11-62:1.1.4-2X11 client-side library ii libxcursor1 1:1.1.9-1X cursor management library ii libxkbfile1 1:1.0.5-1X11 keyboard file manipulation lib ii libxtst62:1.0.3-1X11 Testing -- Resource extension kdebase-bin recommends no packages. Versions of packages kdebase-bin suggests: ii gdb6.8-3 The GNU Debugger ii khelpcente 4:4.0.0.really.3.5.9.dfsg.1-5 help center for KDE -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#495474: [kmid] kmid doesn't play any sound
On Friday 22 August 2008 08:17:27 Valerio Passini wrote: > Alle venerdì 22 agosto 2008, Lisandro Damián Nicanor Pérez Meyer ha scritto: > > What about using timidity in the console with the same file? > >Lisandro Damián Nicanor Pérez Meyer > > Timidity plays well every file. I want to underscore here that this issue I > have with kmid presents with every file I've tried (sampling from the > archive I have), while timidity works. Ciao > > Valerio I just tested with kernel 2.6.26-1-686 (I do not have a 2.6.26.2 available as you seem to do), with a midi file with silence at the beggining and with another without them and both of them worked flawlessly. Could you please send me: /etc/timidity/timidity.cfg /etc/default/timidity ~/.kde/share/config/kmidrc ~/.kde4/share/config/kmidrc if you are running KDE 4 Regards, Lisandro. -- "One World, One web, One program" - Microsoft Promo ad. "Ein Volk, Ein Reich, Ein Führer" - Adolf Hitler Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Processed: bug report
Processing commands for [EMAIL PROTECTED]: > forwarded 493820 http://bugs.kde.org/show_bug.cgi?id=151638 Bug#493820: Msn http method does not work Noted your statement that Bug has been forwarded to http://bugs.kde.org/show_bug.cgi?id=151638. > Tags 493820 upstream Bug#493820: Msn http method does not work There were no tags set. Tags added: upstream > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#496110: kdeprint: Wrong initscript name (cupsys instead of cups)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: kdeprint Severity: important Hi, when clicking on "Restart server" in the kde printer dialog (the one you get when issuing "kcmshell printers" in a console) in the "Printer Server" menu, kdeprint refuses to restart cups because the package is looking for /etc/init.d/cupsys instead of /etc/init.d/cups. Greetings, Christian -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkiu/uMACgkQa8N5v3G+vWIk8wCeJ/VROLioHkJmT+wAH6KG4HOZ 1ygAn3491kREoNcZJPKvJHm+7K1p+2PU =WveD -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#496118: [kommander] Experimental kommander can't launch scripts
Package: kommander Version: 4:4.1.0-1 Severity: normal --- Please enter the report below this line. --- When trying to launch a script with the experimental kommander, it complains about missing libkommanderwidgets: kommander(19280) KommanderFactory::loadPlugins: KommanderFactory::loadPlugins - Can't load Kommander plugin library "libkommanderwidgets" Symlinking /usr/lib/libkommanderwidgets.so.4 to /usr/lib/libkommanderwidgets.so solves the problem. Yannick --- System information. --- Architecture: amd64 Kernel: Linux 2.6.26-preempt Debian Release: lenny/sid 500 unstableftp.fr.debian.org 1 experimentalftp.fr.debian.org --- Package information. --- Depends (Version) | Installed ==-+-= kdebase-runtime (>= 4:4.1.0) | 4:4.1.0-2 kdelibs5 (>= 4:4.1.0) | 4:4.1.0-2 libc6 (>= 2.7-1) | 2.7-13 libqt4-dbus (>= 4.4.0) | 4.4.1-1 libqt4-qt3support (>= 4.4.0) | 4.4.1-1 libqt4-xml (>= 4.4.0) | 4.4.1-1 libqtcore4 (>= 4.4.0) | 4.4.1-1 libqtgui4 (>= 4.4.0) | 4.4.1-1 libstdc++6 (>= 4.2.1) | 4.3.1-9 zlib1g(>= 1:1.1.4) | 1:1.2.3.3.dfsg-12 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
xdg-open does not exit if the called applications has been closed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: xdg-utils
Version: 1.0.2-6
Severity: normal
Hello,
I noticed that all xdg-open processes do not exit if the called
application dies/has been closed.
This is easy to reproduce:
[EMAIL PROTECTED]:~$ /bin/sh /usr/bin/xdg-open http://www.debian.org
kfmclient(5959) ClientApp::doIt: Creating ClientApp
(5961)/ ClientApp::doIt: Creating ClientApp
kioclient(5961) ClientApp::kde_open: KUrl("http://www.debian.org";)
If I close now iceweasel, the process runs as long until I kill it.
After some longer X11 session, this appears in a few hundred "useless"
processes ;)
I setted up iceweasel as default browser in KDE 4.1.
While I never saw this behaviour in the past I think this bug is more
kdebase-runtime dependend (Version: 4:4.1.0-2) - but now I just habe KDE
4.1 desktops and can't test it with other enviroments, so please feel
free to test and reassign it!
So on I also CC the debian-qt-kde list.
Thanks in advance.
- --
/*
Mit freundlichem Gruß / With kind regards,
Patrick Matthäi
E-Mail: [EMAIL PROTECTED]
Comment:
Always if we think we are right,
we were maybe wrong.
*/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkivM/UACgkQ2XA5inpabMd8HwCgp3bxnZCtcpU//C7g9/68J/0d
YE4AnAhfdsGjxGACipM6fLB4z0eGTglB
=BbW/
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#491879: Contact Mr.Thomas Hillary
Your mail account have been picked as a winner of a lump sum pay out of £891,934.00 pounds sterlings) Contact Mr.Thomas Hillary via email ( [EMAIL PROTECTED] )with the following information Names,Address,Age,Occupation,Phon Numbers,Sex,Nationality -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
