Bug#344871: kdm: changing Language option breaks keyboard input
On Thu, Dec 29, 2005 at 04:36:42PM -0500, Christopher Martin wrote: > On Tuesday 27 December 2005 00:51, Itai Seggev wrote: > > Package: kdm > > Version: 4:3.4.3-3 > > Severity: important > > Tags: l10n > > > KDM has 'issues' reading /etc/kde3/kdm/kdmrc configuration files from older > versions of kdm, so just to make sure that your problem isn't in this > category, it would be good to purge and reinstall KDM 3.4 (you can of > course backup the old kdmrc first). I started with the Debian pacakged kdmrc, then edited the file by hand. I tried using the KDE Control Center as you suggested, and that worked fine. Confused, I looked at the config file it generated, and saw that it set Lang to he rather than he_IL or he he_IL.UTF-8 (from the default en_US). I then restored my original kdmrc and put in he for Lang, and it also worked. Thus, it seems to be a bug (why does using he_IL rather than he break some of the functionality?), but perhaps not as serious as I originally thought. > Also, if you have any systems/chroots > where you're feeling daring, could you see if the problem occurs using KDM > 3.5 from experimental? No chroots handy, but it should be easy to test whether setting Lang to he_IL continues to be a problem in 3.5 as described above. Thanks, -- Itai Itai Seggev, University of Mississippi, Department of Physics and Astronomy In 1997 a group of programmers started writing a desktop environment to fix a travesty they didn't create. Their program promptly found its way onto un*x systems everywhere. Today, still opposed by a software monopolist, they survive as soldiers of fortune. If you share their vision, if you know you can help, and if you can connect to internet, maybe you can join... the K-Team. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#345388: libqt4-dev: qmake adds -L/usr/lib
On Fri, 30 Dec 2005, Brian Nelson wrote: qmake adds -L/usr/lib to (the beginning of) LIBS. This is unneeded, and actually causes many problems. I agree it's unneeded, but what problems does it cause? I was recompiling a package that contains both a library and a program. When linking the program, "-L/usr/lib" came before "-L../lib" and the linker tried to link the program against the old version of the library in /usr/lib. I believe that -L$QTDIR -lQt* should only appear at the end of LIBS (or close to the end), and -L$QTDIR only if it is needed; maybe even use /usr/lib/libQt*.so instead of -L/-l flags, but I am dreaming. At least I need to be able to add -L flags before -L$QTDIR (maybe that is possible and I and the author of the package just need to read the doc...). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#345486: konqueror crash browsing SMB directory
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: konqueror Version: 3.4.2 Browsing into a SMB remotely mounted tree Konqueror had crash: I can't give more details just because I haven't did nothing special, just opened a directory and rather immediately clicked on the back button. Now paste the backtrace printed by KDE Crash Handler: (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1232050496 (LWP 4736)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #3 0xb64a2cda in SpringLoadingManager::finished () from /usr/lib/kde3/konq_iconview.so #4 0xb64a2dae in SpringLoadingManager::qt_invoke () from /usr/lib/kde3/konq_iconview.so #5 0xb7269c5f in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #6 0xb726a743 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #7 0xb75fc2b5 in QTimer::timeout () from /usr/lib/libqt-mt.so.3 #8 0xb728f1a4 in QTimer::event () from /usr/lib/libqt-mt.so.3 #9 0xb71ff778 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #10 0xb71ff996 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #11 0xb78bd9fc in KApplication::notify () from /usr/lib/libkdecore.so.4 #12 0xb718f665 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3 #13 0xb71f0a44 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3 #14 0xb71a33f8 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #15 0xb7217ea2 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #16 0xb7217dcb in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #17 0xb71fe305 in QApplication::exec () from /usr/lib/libqt-mt.so.3 #18 0xb68562ac in kdemain () from /usr/lib/libkdeinit_konqueror.so #19 0xb689d530 in kdeinitmain () from /usr/lib/kde3/konqueror.so #20 0x0804decd in ?? () #21 0x0002 in ?? () #22 0x08072650 in ?? () #23 0xbf81a2d8 in ?? () #24 0x0804def1 in ?? () #25 0x in ?? () #26 0x in ?? () #27 0x in ?? () #28 0x in ?? () #29 0xbcf4 in ?? () #30 0x08072498 in ?? () #31 0x08072484 in ?? () #32 0x0002 in ?? () #33 0x in ?? () #34 0x in ?? () #35 0x in ?? () #36 0x0010 in ?? () #37 0xb7da9868 in __malloc_initialize_hook () from /lib/tls/libc.so.6 #38 0xb400 in ?? () #39 0x4006 in ?? () #40 0x in ?? () #41 0x in ?? () #42 0x in ?? () #43 0x in ?? () #44 0x0010 in ?? () #45 0xb7da9868 in __malloc_initialize_hook () from /lib/tls/libc.so.6 #46 0x in ?? () #47 0xb77315b0 in vtable for QGArray () from /usr/lib/libqt-mt.so.3 #48 0x in ?? () #49 0x in ?? () #50 0x in ?? () #51 0x08051400 in vtable for QCString () #52 0x08071cd0 in ?? () #53 0x08051400 in vtable for QCString () #54 0x08071c68 in ?? () #55 0x08051400 in vtable for QCString () #56 0x080727d8 in ?? () #57 0x08051400 in vtable for QCString () #58 0x080727d8 in ?? () #59 0x08051400 in vtable for QCString () #60 0x08072690 in ?? () #
Bug#337788: kmix volume splash screen stuck on Dell inspiron 8500
I have the same problem. It occours when I have the DVD drive in on my inspiron 600m. I am using Gentoo for the OS. The problem is with Milo. You can stop it in the KDE control panel, under services. This will fix the problem, but I am not sure what is causing Milo (Special key detection) to freak out, and think you are holding the volume knob down. I hope this helps, cause I would really like to be able to use special keys. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
