Bug#595558: kgpg editor does not support non-Latin characters
Package: kgpg Version: 4:4.4.5-1 Severity: normal Open editor and enter for example "тест" (Russian "test"), then press "Sign/Verify" and you have all non-Latin characters changed to '?': -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkyC9iAACgkQQ2KBgKEPWL/J2wCfX6fh7R737CxSsCYTIrfCH13N kXgAnj3y8YBKZOdPLpBF5Bys4oEaRoS+ =D110 -END PGP SIGNATURE- This problem also exist for "Sign/Verify clipboard" command. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (800, 'testing'), (800, 'stable'), (200, 'unstable'), (65, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kgpg depends on: ii kdebase-runtime 4:4.4.5-1 runtime components from the offici ii kdepim-runtime4:4.4.4-1 Runtime components for akonadi-kde ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libkabc4 4:4.4.5-1 library for handling address book ii libkdecore5 4:4.4.5-1 the KDE Platform Core Library ii libkdeui5 4:4.4.5-1 the KDE Platform User Interface Li ii libkio5 4:4.4.5-1 the Network-enabled File Managemen ii libkpimutils4 4:4.4.5-1 library for dealing with email add ii libqt4-dbus 4:4.6.3-1 Qt 4 D-Bus module ii libqtcore44:4.6.3-1 Qt 4 core module ii libqtgui4 4:4.6.3-1 Qt 4 GUI module ii libsolid4 4:4.4.5-1 Solid Library for KDE Platform ii libstdc++64.4.4-8The GNU Standard C++ Library v3 kgpg recommends no packages. kgpg suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100905015254.5004.24379.report...@home.progtech.ru
Fwd: [Kde-pim] kdepim 4.4.6?
Hi Debian Qt/KDE developer team, are you aware of this? Thanks, Martin -- Weitergeleitete Nachricht -- Subject: [Kde-pim] kdepim 4.4.6? Date: Samstag 04 September 2010 From: Allen Winter To: KDE release coordination , KDE PIM Howdy, Laurent has been putting quite a number of fixes into the 4.4 kdepim branch and the distro packagers have noticed :) Since we are delaying kdepim 4.5 so long, some distros will be skipping kdepim 4.5 completely. so...a kdepim 4.4.6 (not a full KDE SC 4.4.6) makes sense to me. Does anyone object to such a thing? I can do the work of making the tag, unless Dirk wants to do that. Maybe tag it on .. oh.. say 9 September (next Thursday)? Laurent, would that be a good date for you? -Allen -- Allen Winter | al...@kdab.net | Software Engineer KDAB (USA), LLC, a KDAB Group company Tel. USA +1-866-777-KDAB(5322), Sweden (HQ) +46-563-540090 KDAB - Qt Experts - Platform-independent software solutions ___ KDE PIM mailing list kde-...@kde.org https://mail.kde.org/mailman/listinfo/kde-pim KDE PIM home page at http://pim.kde.org/ --- -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 signature.asc Description: This is a digitally signed message part.
Bug#595532: [python-kde4] python-kde4 depends on python2.5
Package: python-kde4 Version: 4:4.4.5-2 Severity: serious This packages still depends on python2.5. The new standard version for the next stable release will be python2.6, so that package should not need python2.5 anymore. --- System information. --- Architecture: i386 Kernel: Linux 2.6.34-0.slh.11-sidux-686 Debian Release: squeeze/sid 500 unstablewww.debian-multimedia.org 500 unstablesidux.com 500 unstablelinux.wuertz.org 500 unstableftp.debian.org 500 unstabledeb.opera.com 500 testing ftp5.gwdg.de 400 unstablefrickelplatz.de 1 experimentalftp5.gwdg.de --- Package information. --- Depends (Version) | Installed ==-+-= kdebase-runtime| 4:4.4.5-1 kdepim-runtime | 4:4.4.5-1 libakonadi-kde4 (>= 4:4.4.0) | 4:4.4.5-1 libakonadi-kmime4 (>= 4:4.4.0) | 4:4.4.5-1 libc6 (>= 2.1.3) | 2.11.2-2 libkdecore5(>= 4:4.4.4-2~) | 4:4.4.5-1 libkdeui5 (>= 4:4.4.0) | 4:4.4.5-1 libkdnssd4 (>= 4:4.4) | 4:4.4.5-1 libkfile4 (>= 4:4.4.0) | 4:4.4.5-1 libkhtml5 (>= 4:4.4.0) | 4:4.4.5-1 libkio5 (>= 4:4.4.0) | 4:4.4.5-1 libknewstuff2-4 (>= 4:4.4.0) | 4:4.4.5-1 libknewstuff3-4 (>= 4:4.4.0) | 4:4.4.5-1 libkparts4(>= 4:4.4.1) | 4:4.4.5-1 libkpty4(>= 4:4.4) | 4:4.4.5-1 libktexteditor4 (>= 4:4.4) | 4:4.4.5-1 libkutils4(>= 4:4.4.0) | 4:4.4.5-1 libnepomuk4 (>= 4:4.4.0) | 4:4.4.5-1 libnepomukquery4a (>= 4:4.4.0) | 4:4.4.5-1 libphonon4(>= 4:4.6.0really4.3.80) | 4:4.6.0really4.4.2-1 libplasma3 (>= 4:4.4.4-2~) | 4:4.4.5-1 libpython2.6 (>= 2.6) | 2.6.6-2 libqt4-network(>= 4:4.5.3) | 4:4.6.3-1 libqt4-svg(>= 4:4.5.3) | 4:4.6.3-1 libqt4-xml(>= 4:4.5.3) | 4:4.6.3-1 libqtcore4(>= 4:4.6.1) | 4:4.6.3-1 libqtgui4 (>= 4:4.6.1) | 4:4.6.3-1 libsolid4 (>= 4:4.4.0) | 4:4.4.5-1 libsoprano4 (>= 2.4.0.1) | 2.5.0+dfsg.1-1 libstdc++6 (>= 4.1.1) | 4.4.4-11 phonon | 4:4.6.0really4.4.2-1 python2.5 (>= 2.5) | 2.5.5-6 python(<< 2.7) | 2.6.5-13 python(>= 2.5) | 2.6.5-13 python-support (>= 0.90.0) | 1.0.9 python-qt4 | 4.7.3-1+b1 sip-api-7.1| python-sip | 4.10.2-1 Package's Recommends field is empty. Package's Suggests field is empty. signature.asc Description: This is a digitally signed message part.
Bug#595483: kde: KDE4 Crashes system
> -Original Message- > From: George Kiagiadakis [mailto:kiagiadakis.geo...@gmail.com] > Sent: Saturday, September 04, 2010 7:48 AM > To: Leslie Rhorer > Cc: 595...@bugs.debian.org > Subject: Re: Bug#595483: kde: KDE4 Crashes system > > On Sat, Sep 4, 2010 at 3:32 PM, Leslie Rhorer > wrote: > > A "normal" severity for a bug that causes the system to be > > completely unusable when the package is in use? That locks up the > system > > like Fort Knox? That causes data loss if any files are still open? I'm > > hard pressed to think of a more severe problem. > > It is a serious problem, but it is not related to the 'kde' package > where you reported it. The 'kde' package is a metapackage from lenny > and does not even exist in squeeze. The most likely cause of the bug > is the kernel, so this bug should eventually be reasigned there and > have its severity raised, however I cannot do that until the problem > has been fully identified. OK. > > There are no proprietary gpu drivers, and please re-read the > post. > > One of the systems is Intel. Both systems were upgraded from Debian > "Lenny" > > with no problems whatsoever running KDE3. Neither has any problem > running > > gnome. KDE4 was so unusable on the Pentium system I wiped the drive and > > installed fresh from the "Squeeze" installer. It didn't help. Both use > the > > graphics processors embedded on the motherboard, with plain-vanilla > Debian > > installations straight from the Debian install CD. The Pentium system > is an > > old Dell Optiplex GX-1 system, which is about as Plain Jane Intel as it > > gets. The AMD is over a year old. All of the software on both machines > - > > other than that I have written myself - is straight from the Debian > > repositories. > > An intel system can have an amd graphics card, this is not uncommon. I As I said, neither has a graphics card, and I certainly have never seen an Intel motherboard with an AMD GPU. I would think the execs at Intel would rather have their nards shredded than use an AMD product on one of their motherboards. Come to think of it, however, would the GPU or its drivers even have any effect on XDMCP? I'm not an expert on X11, but I don't think X11 makes use of any local GPU resources - hardware or software - when the X-server is remote, does it? That, along with the fact the GPUs are as different as can be would seem to tend to eliminate the GPUs or their drivers as the source of the issue. That said, on a note related to the Intel GPU, I did have to disable the i915 modeset in /etc/modeprobe.d/i915-kms.conf on the Pentium system or else it would not boot without a monitor. As I recall, the video driver installed by Debian is xserver-xorg-video-intel. (Oh, BTW, I mis-spoke a bit: It's a GX-260, not a GX-1.) On what I don't think is a related note - but could be - KDM does not come up on the console of the AMD machine. The console never switches to the graphical interface. I'm not sure why, but since I never use the console, I really haven't worried about it. I don't recall exactly when this broke. I don't think it was during the upgrade to "Squeeze" / KDE4, but I could be mistaken. It definitely worked under "Lenny", however. > still believe the problem is in graphics drivers, though. Even if > these are the free intel or radeon drivers. Radeon drivers are known > to lock up if their non-free firmware is missing, perhaps you should > make sure to install firmware-linux-nonfree and I'm not sure about the I don't follow. The embedded controller on the Asus MB is a Radeon HD 3200, though. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-qt-kde
Bug#595483: kde: KDE4 Crashes system
On Sat, Sep 4, 2010 at 3:32 PM, Leslie Rhorer wrote: > A "normal" severity for a bug that causes the system to be > completely unusable when the package is in use? That locks up the system > like Fort Knox? That causes data loss if any files are still open? I'm > hard pressed to think of a more severe problem. It is a serious problem, but it is not related to the 'kde' package where you reported it. The 'kde' package is a metapackage from lenny and does not even exist in squeeze. The most likely cause of the bug is the kernel, so this bug should eventually be reasigned there and have its severity raised, however I cannot do that until the problem has been fully identified. > There are no proprietary gpu drivers, and please re-read the post. > One of the systems is Intel. Both systems were upgraded from Debian "Lenny" > with no problems whatsoever running KDE3. Neither has any problem running > gnome. KDE4 was so unusable on the Pentium system I wiped the drive and > installed fresh from the "Squeeze" installer. It didn't help. Both use the > graphics processors embedded on the motherboard, with plain-vanilla Debian > installations straight from the Debian install CD. The Pentium system is an > old Dell Optiplex GX-1 system, which is about as Plain Jane Intel as it > gets. The AMD is over a year old. All of the software on both machines - > other than that I have written myself - is straight from the Debian > repositories. An intel system can have an amd graphics card, this is not uncommon. I still believe the problem is in graphics drivers, though. Even if these are the free intel or radeon drivers. Radeon drivers are known to lock up if their non-free firmware is missing, perhaps you should make sure to install firmware-linux-nonfree and I'm not sure about the intel drivers (never had one of those). Anyway, the kernel upgrade may help, since the -5- version of this kernel has all the graphics drivers backported from 2.6.33. PS: Do not keep cont...@bugs.debian.org in CC, it will just send you back an email full of errors, since you are not following its syntax in the email (it is a bot). -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlkti=ukosbfc000yq5rog8wxtspqu+qphe_m0qu...@mail.gmail.com
Bug#595483: kde: KDE4 Crashes system
> -Original Message- > From: George Kiagiadakis [mailto:kiagiadakis.geo...@gmail.com] > Sent: Saturday, September 04, 2010 7:06 AM > To: lrhorer; 595...@bugs.debian.org > Cc: cont...@bugs.debian.org > Subject: Re: Bug#595483: kde: KDE4 Crashes system > > severity 595483 normal > thanks > > On Sat, Sep 4, 2010 at 2:46 PM, lrhorer wrote: > > Package: kde > > Version: KDE4 > > Severity: critical > > Justification: breaks the whole system > > > > KDE4 invariably crashes the system. This system is running on an AMD > Athlon 64 > > x 2 processer under Debian "Squeeze" and kernel 2.6.32-3-amd64. The > same > > symptoms (only worse) are also observed on a Pentium IV system running > > 2.6.32-trunk-686. One can log in via kdm and bring up KDE4, but sooner > or > > later - usually within an hour or two, the system will crash hard. One > then > > cannot reach the system via telnet, XDMCP, or from the console. Often, > it will > > not even reply to pings. The only option is to hit the power switch. > If no > > KDE session is active, both machines are 100% stable, up continuously > for > > months at a time without issues. If a KDE4 session is active, then > after > > between 30 minutes and 24 hours, the system will crash. No activity is > > required on the KDE session for the failure to occur, but it seems that > > changing window foocus often triggers an event. > > > > This is most likely due to a faulty gpu driver. I guess you are using > amd's proprietary fglrx driver? I have seen such issues in the past > with this driver. KDE has no way to lock the system, if a system lock > happens this is a problem deep in the kernel or some of its modules. > > Btw, both of these kernels that you are using are out-of-date. The > latest squeeze kernel is 2.6.32-5-amd64. I advise you to upgrade to > this kernel and uninstall any proprietary graphics drivers. A "normal" severity for a bug that causes the system to be completely unusable when the package is in use? That locks up the system like Fort Knox? That causes data loss if any files are still open? I'm hard pressed to think of a more severe problem. There are no proprietary gpu drivers, and please re-read the post. One of the systems is Intel. Both systems were upgraded from Debian "Lenny" with no problems whatsoever running KDE3. Neither has any problem running gnome. KDE4 was so unusable on the Pentium system I wiped the drive and installed fresh from the "Squeeze" installer. It didn't help. Both use the graphics processors embedded on the motherboard, with plain-vanilla Debian installations straight from the Debian install CD. The Pentium system is an old Dell Optiplex GX-1 system, which is about as Plain Jane Intel as it gets. The AMD is over a year old. All of the software on both machines - other than that I have written myself - is straight from the Debian repositories. I'll try upgrading the kernel on the AMD system. The Pentium is not local to me, and an upgrade failure would probably be unrecoverable. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-qt-kde
Processed: Re: Bug#595483: kde: KDE4 Crashes system
Processing commands for cont...@bugs.debian.org: > severity 595483 normal Bug #595483 [kde] kde: KDE4 Crashes system Severity set to 'normal' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 595483: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.128360196832380.transcr...@bugs.debian.org
Processed (with 5 errors): Akregator is unusable crash at each start
Processing commands for cont...@bugs.debian.org: > severity 590147 serious Bug #590147 [akregator] akregator crashes at start Severity set to 'serious' from 'important' > forwarded 590147 https://bugs.kde.org/show_bug.cgi?id=250162 Bug #590147 [akregator] akregator crashes at start Set Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=250162'. > I get a backtrace and forwarded to upstream. Akregator is unusable so Unknown command or malformed arguments to command. > increase to serious. Unknown command or malformed arguments to command. > Application: Akregator (akregator), signal: Segmentation fault Unknown command or malformed arguments to command. > The current source language is "auto; currently asm". Unknown command or malformed arguments to command. > [KCrash Handler] Unknown command or malformed arguments to command. Too many unknown commands, stopping here. Please contact me if you need assistance. -- 590147: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590147 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.128360195332259.transcr...@bugs.debian.org
Bug#590147: Akregator is unusable crash at each start
severity 590147 serious forwarded 590147 https://bugs.kde.org/show_bug.cgi?id=250162 I get a backtrace and forwarded to upstream. Akregator is unusable so increase to serious. Application: Akregator (akregator), signal: Segmentation fault The current source language is "auto; currently asm". [KCrash Handler] #5 memcpy () at ../sysdeps/x86_64/memcpy.S:397 #6 0x7f131945bd04 in c4_String::Init (this=0x7fff150e81a0, p=, n=1230779) at ../../../../akregator/plugins/mk4storage/metakit/src/string.cpp:195 #7 0x7f1319453812 in c4_String (this=0x2032a30, ptr_=0x7fff150e8270, selfDesc_=) at ../../../../akregator/plugins/mk4storage/metakit/include/mk4str.inl:209 #8 c4_HandlerSeq::Prepare (this=0x2032a30, ptr_=0x7fff150e8270, selfDesc_=) at ../../../../akregator/plugins/mk4storage/metakit/src/handler.cpp:305 #9 0x7f1319456e5d in c4_Persist::LoadAll (this=0x202ffc0) at ../../../../akregator/plugins/mk4storage/metakit/src/persist.cpp:1026 #10 0x7f1319467479 in Akregator::Backend::StorageMK4Impl::open (this=0x1ec4c00, autoCommit=true) at ../../../../akregator/plugins/mk4storage/storagemk4impl.cpp:134 #11 0x7f131b125989 in Part (this=0x1ee83b0, parentWidget=, parent=, __in_chrg=, __vtt_parm=) at ../../../akregator/src/akregator_part.cpp:222 #12 0x7f131b1286cf in QObject* KPluginFactory::createPartInstance(QWidget*, QObject*, QList const&) () from /usr/lib/kde4/akregatorpart.so #13 0x7f132cfd563c in KPluginFactory::create (this=0x1ef6880, iface=0x7f132e2b6580 "KParts::ReadOnlyPart", parentWidget=, parent=0x1d9e0c0, args=..., keyword=) at ../../kdecore/util/kpluginfactory.cpp:191 #14 0x0040b014 in KPluginFactory::create (this=0x1d9e0c0) at /usr/include/KDE/../kpluginfactory.h:491 #15 Akregator::MainWindow::loadPart (this=0x1d9e0c0) at ../../../akregator/src/mainwindow.cpp:109 #16 0x0040b3a8 in Akregator::MainWindow::readProperties (this=0x1d9e0c0, config=...) at ../../../akregator/src/mainwindow.cpp:152 #17 0x0040a829 in Akregator::MainWindow::autoReadProperties (this=0x1d9e0c0) at ../../../akregator/src/mainwindow.cpp:266 #18 0x0040aae8 in MainWindow (this=0x1d9e0c0, parent=, f=, __in_chrg=, __vtt_parm=) at ../../../akregator/src/mainwindow.cpp:89 #19 0x00408c7a in Akregator::Application::newInstance (this=0x7fff150e9db0) at ../../../akregator/src/main.cpp:58 #20 0x7f132d4a3666 in KUniqueApplicationAdaptor::newInstance (this=0x1e68ab0, asn_id=, args=...) at ../../kdeui/kernel/kuniqueapplication.cpp:454 #21 0x7f132d4a3ca6 in KUniqueApplicationAdaptor::qt_metacall (this=0x1e68ab0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fff150e8e20) at ./kuniqueapplication_p.moc:81 #22 0x7f132c6e6421 in QDBusConnectionPrivate::deliverCall (this=, object=, msg=, metaTypes=..., slotIdx=) at qdbusintegrator.cpp:904 #23 0x7f132c6e762f in QDBusConnectionPrivate::activateCall (this=, object=0x1e68ab0, flags=337, msg=...) at qdbusintegrator.cpp:809 #24 0x7f132c6e810d in QDBusConnectionPrivate::activateObject (this=, node=, msg=..., pathStartPos=) at qdbusintegrator.cpp:1364 #25 0x7f132c6e83a8 in QDBusActivateObjectEvent::placeMetaCall (this=0x1e7b290) at qdbusintegrator.cpp:1477 #26 0x7f132cac3e89 in QObject::event (this=0x7fff150e9db0, e=0x1e7b290) at kernel/qobject.cpp:1248 #27 0x7f132bbdd69d in QApplication::event (this=0x7fff150e9db0, e=0x1e7b290) at kernel/qapplication.cpp:2355 #28 0x7f132bbd932c in QApplicationPrivate::notify_helper (this=0x1dac400, receiver=0x7fff150e9db0, e=0x1e7b290) at kernel/qapplication.cpp:4302 #29 0x7f132bbdf80b in QApplication::notify (this=0x7fff150e9db0, receiver=0x7fff150e9db0, e=0x1e7b290) at kernel/qapplication.cpp:4185 #30 0x7f132d49c836 in KApplication::notify (this=0x7fff150e9db0, receiver=0x7fff150e9db0, event=0x1e7b290) at ../../kdeui/kernel/kapplication.cpp:302 #31 0x7f132cab415c in QCoreApplication::notifyInternal (this=0x7fff150e9db0, receiver=0x7fff150e9db0, event=0x1e7b290) at kernel/qcoreapplication.cpp:726 #32 0x7f132cab7804 in QCoreApplication::sendEvent (receiver=0x0, event_type=, data=0x1d7eec0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #33 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=, data=0x1d7eec0) at kernel/qcoreapplication.cpp:1367 #34 0x7f132caddbd3 in QCoreApplication::sendPostedEvents (s=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220 #35 postEventSourceDispatch (s=) at kernel/qeventdispatcher_glib.cpp:276 #36 0x7f13254f46c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #37 0x7f13254f8538 in ?? () from /lib/libglib-2.0.so.0 #38 0x7f13254f86ec in g_main_context_iteration () from /lib/libglib-2.0.so.0 #39 0x7f132cadd713 in QEventDispatcherGlib::processEvents (this=0x1d7e630, flags=) at kernel/qeventdispatcher_glib.cpp:412 #40 0x7f132bc8914e in QGuiEventDispatcherGlib::processEvents (this=0x7f131931af96, flags=) at kernel/qguieventd
Bug#595483: kde: KDE4 Crashes system
severity 595483 normal thanks On Sat, Sep 4, 2010 at 2:46 PM, lrhorer wrote: > Package: kde > Version: KDE4 > Severity: critical > Justification: breaks the whole system > > KDE4 invariably crashes the system. This system is running on an AMD Athlon > 64 > x 2 processer under Debian "Squeeze" and kernel 2.6.32-3-amd64. The same > symptoms (only worse) are also observed on a Pentium IV system running > 2.6.32-trunk-686. One can log in via kdm and bring up KDE4, but sooner or > later - usually within an hour or two, the system will crash hard. One then > cannot reach the system via telnet, XDMCP, or from the console. Often, it > will > not even reply to pings. The only option is to hit the power switch. If no > KDE session is active, both machines are 100% stable, up continuously for > months at a time without issues. If a KDE4 session is active, then after > between 30 minutes and 24 hours, the system will crash. No activity is > required on the KDE session for the failure to occur, but it seems that > changing window foocus often triggers an event. > This is most likely due to a faulty gpu driver. I guess you are using amd's proprietary fglrx driver? I have seen such issues in the past with this driver. KDE has no way to lock the system, if a system lock happens this is a problem deep in the kernel or some of its modules. Btw, both of these kernels that you are using are out-of-date. The latest squeeze kernel is 2.6.32-5-amd64. I advise you to upgrade to this kernel and uninstall any proprietary graphics drivers. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimcthx2ny0ga79v=flp8vab8njne=++2=lmp...@mail.gmail.com
Bug#595483: kde: KDE4 Crashes system
Package: kde Version: KDE4 Severity: critical Justification: breaks the whole system KDE4 invariably crashes the system. This system is running on an AMD Athlon 64 x 2 processer under Debian "Squeeze" and kernel 2.6.32-3-amd64. The same symptoms (only worse) are also observed on a Pentium IV system running 2.6.32-trunk-686. One can log in via kdm and bring up KDE4, but sooner or later - usually within an hour or two, the system will crash hard. One then cannot reach the system via telnet, XDMCP, or from the console. Often, it will not even reply to pings. The only option is to hit the power switch. If no KDE session is active, both machines are 100% stable, up continuously for months at a time without issues. If a KDE4 session is active, then after between 30 minutes and 24 hours, the system will crash. No activity is required on the KDE session for the failure to occur, but it seems that changing window foocus often triggers an event. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kde depends on: pn kde-core (no description available) pn kdeaccessibility (no description available) pn kdeaddons (no description available) pn kdeadmin (no description available) pn kdeartwork (no description available) pn kdeedu (no description available) pn kdegames (no description available) pn kdegraphics(no description available) pn kdemultimedia (no description available) pn kdenetwork (no description available) pn kdepim (no description available) pn kdetoys(no description available) pn kdeutils (no description available) pn kdewebdev (no description available) kde recommends no packages. Versions of packages kde suggests: pn kde-i18n (no description available) pn x-window-system-core (no description available) -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100904114608.16298.52210.report...@backup
Processed: bug 595283 is forwarded to https://bugs.kde.org/show_bug.cgi?id=182073
Processing commands for cont...@bugs.debian.org: > forwarded 595283 https://bugs.kde.org/show_bug.cgi?id=182073 Bug #595283 [krfb] krfb: shift key not working from remote keyboard Set Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=182073'. > thanks Stopping processing here. Please contact me if you need assistance. -- 595283: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595283 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.128359569321854.transcr...@bugs.debian.org
