Re: New KDE (3.5.4) will break mouting of removeable devices
> I send this as an info/warning to all who use the new version of KDE: > mounting > removeable devices such as an USB pen drive won't work anymore. There are > workarounds and an explicit bug report (#377689) already: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377689 > > You will have to add: > > > > > > > > to /etc/dbus-1/system.d/hal.conf - but there are other issues yet unsolved, > read the bug report for more details. Thanks for the heads-up. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: network configuration
> I think, one day, network manager will be the way to go. For now, I'll have > to rely on ifplugd and whereami. Whew. Linux for desktops and laptops has made enormous strides, but this is one area where it lags badly. The range of tools-- ifplugd, whereami, waproamd, wpasupplicant, network-manager, all of the wireless tools, and others that I can't even remember now-- and their interactions is simply baffling to me, and I'm a long-time Debian user with a moderate to high tolerance for complexity. There are things in Linux (like network servers) that I like to tinker with and get just right, and then there are things (like sound) that I don't care how they work, I just want them to work. WLAN association is in the latter category. I have to say that Microsoft has really done an excellent job with their taskbar applet for WLANs in XP SP2. It's easy to set up, and once it's set up it mostly just works without any intervention. Fortunately, looking at the current ferment in open source tools in this area, I predict that in about one year, we'll have a good set of easy-to-use tools for moving between WLANs with a laptop. Linux will catch up. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KPlayer for KDE 3.4.2
> Hello, > > okay, didn't take long, there it is again nicely packaged: > > deb ftp://ftp.nerim.net/debian-marillat/ sid main > > apt-get install kplayer=0.5.3-0.1 Thanks! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
does superkaramba suck?
Is it just me, or does superkaramba suck? All of the superkaramba propaganda talks about how great it is, so I decided to try it. I install the Debian package, and run the program. The little bomb appears. So far, so good. Problem #1: Every time I complete an action-- e.g. trying to open a theme, then cancelling when I don't find any themes stored locally; or closing the welcome screen-- superkaramba exits. I have to restart it. Problem #2: superkaramba comes packaged with exactly zero themes. When I go to download one, I get a .skz file, which superkaramba doesn't recognize. So okay, I figure out pretty easily that it's just a stupidly named zip archive. I _manually_ create a directory and unpack the contents there. Now superkaramba recognizes the .theme file. superkaramba can't do this work on its own? Problem #3: I decide to try liquid weather. It sounds cool, and is the _very first_ theme listed on the download page. I coax superkaramba to use it as I described above. But when I do, I get Call to initWidget failed Traceback (most recent call last): File "liquid_weather.py", line 2432, in initWidget initTranslation(widget) File "liquid_weather.py", line 420, in initTranslation lang = karamba.language(widget) AttributeError: 'module' object has no attribute 'language' So, here's the score so far: Time spent so far with superkaramba: 20 minutes. Amount of eye candy appearing on my desktop: zero. If I persist will I be rewarded, or will I just be throwing good time after bad? And, does superkaramba suck? A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
device: default can't be opened for playback (Device or resource busy)
I have a longstanding multiuser problem with aRts. It happens to me often that when another user on my host has been using an application that makes sound, my sound won't work. If I try to start an application (such as a movie player) that makes sound, sometimes it will block or hang, and sometimes it will start but not play movies, or will play movies but without sound. So I go to the Control Center to restart the sound server, and when I try, an error dialog pops up with the following message: Error while initializing the sound driver: device: default can't be opened for playback (Device or resource busy) The sound server will continue, using the null output device. In the old days I used to be able to find out which application had grabbed control of the sound device by running 'lsof /dev/dsp'. That doesn't work now with aRts, but I don't know what the corresponding device file or command is. I know that my other users are the source of the problem, because if I slay them all then eventually I get my sound server back. Sometimes I can get it back by just killing other sound-using applications, but sometimes I can't and have to slay the users. All users have "Auto-suspend if idle" turned on and set to 3 seconds. I'm using ALSA with kernel 2.6.10, a Turtle Beach Santa Cruz sound card (cs46xx driver), and a bt878 video capture card. Any help appreciated. Thanks, Andrew. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
device: default can't be opened for playback (Device or resource busy)
I have a longstanding multiuser problem with aRts. It happens to me often that when another user on my host has been using an application that makes sound, my sound won't work. If I try to start an application (such as a movie player) that makes sound, sometimes it will block or hang, and sometimes it will start but not play movies, or will play movies but without sound. So I go to the Control Center to restart the sound server, and when I try, an error dialog pops up with the following message: Error while initializing the sound driver: device: default can't be opened for playback (Device or resource busy) The sound server will continue, using the null output device. In the old days I used to be able to find out which application had grabbed control of the sound device by running 'lsof /dev/dsp'. That doesn't work now with aRts, but I don't know what the corresponding device file or command is. I know that my other users are the source of the problem, because if I slay them all then eventually I get my sound server back. Sometimes I can get it back by just killing other sound-using applications, but sometimes I can't and have to slay the users. All users have "Auto-suspend if idle" turned on and set to 3 seconds. I'm using ALSA with kernel 2.6.10, a Turtle Beach Santa Cruz sound card (cs46xx driver), and a bt878 video capture card. Any help appreciated. Thanks, Andrew. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kde 3.4.1
> Hi I install Debian sarge today and upgraded for unstable, but I > can't install kde 3.4.1 here. > > In my sources.list I added line: > > deb http://pkg-kde.alioth.debian.org/kde-3.4.1/ ./ > > and when I put aptitude update, I get one error: > > Ign http://pkg-kde.alioth.debian.org ./ Packages > > what I need to install? KDE 3.4.1 is in experimental, not unstable. Still, your deb line is correct and you should be able to get the packages. I suggest waiting a while and trying again. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: audiocd:/ and secondary drives
>>> Documentation for audiocd:/ is in the information center (like for all >>> KIO stuff) and it tells you something like: >>> audiocd:/?device=/dev/hdc >> >> Not if you're using KDE 3.4.1 from alioth, which seems to be missing the >> audiocd.docbook file. I'm filing a bug report about this. Meanwhile >> thanks for the tip. > > Yep, that'd be exactly why I couldn't find it in the docs. I knew it > should've > been there but when it didn't display anything I just assumed nothing had > been written, yet. Thank you both. :) If anyone wants to follow the bug report, it's http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=315533. I filed it against kdebase-kio-plugins, but it seems that it may be reassigned to kdemultimedia-kio-plugins. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: audiocd:/ and secondary drives
>> audiocd:/ always uses the first CD drive, but I'd like to be able to use >> the audiocd:/ protocol on my second CD drive aswell. Does anyone know a >> way to do that, or is it not possible? I can't find any doc that'll tell >> me. > > Documentation for audiocd:/ is in the information center (like for all KIO > stuff) and it tells you something like: > audiocd:/?device=/dev/hdc Not if you're using KDE 3.4.1 from alioth, which seems to be missing the audiocd.docbook file. I'm filing a bug report about this. Meanwhile thanks for the tip. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: audiocd:/ and secondary drives
> El Jueves, 23 de Junio de 2005 03:13, Brendon Lloyd Higgins escribió: >> audiocd:/ always uses the first CD drive, but I'd like to be able to use >> the audiocd:/ protocol on my second CD drive aswell. Does anyone know a >> way to do that, or is it not possible? I can't find any doc that'll tell >> me. > > This is configurable in the control center: > > Sounds & Multimedia -> Audio CD's ... for exactly one drive at a time. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KMail does not use kwallet anymore
>> my guess is that you killed kded or such a process and that kmail is >> living on the old kded and kwallet on a new one, or the reverse. and >> log out and in again should solve the problem. > > Yes, I've observed that every (I believe) dbus upgrade kills all kded > daemons. Okay, that makes sense. I also had the OP's problem, and kwalletmanager was acting strangely-- it wouldn't create new wallets. And I had upgraded dbus. By the time I was done trying different things (reinstall kwallet, downgrade kwallet, wipe config files...) I'd trashed my old wallet and had to start a new one, but anyway it works again now. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ksplash still freezes
> same problem for weeks now. > when deleting .kde/share/config/ksmserverrc it works > > did i miss something on the list or am i the only one still having > this problem? I still have it. My solution is to log in on another console and run 'pkill klauncher'. Then I dismiss the splash window and I'm logged in, although many of my autostart programs haven't started. (It seems to hang on kmail.) I filed a bug report with KDE about this: http://bugs.kde.org/show_bug.cgi?id=102046. Just recently the bug was marked RESOLVED because they asked me 6 weeks ago to trace the hang with gdb, and I still haven't done it. But if you have something to add to the report, please do. I've now updated to KE 3.4.1, and ksplash still hangs every time I log in. Andrew. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kde 3.4.1 packages
>> Preparing to replace kdelibs-data 4:3.3.2-6.1 (using >> .../kdelibs-data_4%3a3.4.1-1_all.deb) ... >> Unpacking replacement kdelibs-data ... >> Replacing files in old package konq-plugins ... >> dpkg: error processing >> /var/cache/apt/archives/kdelibs-data_4%3a3.4.1-1_all.deb (--unpack): >> trying to overwrite `/usr/share/services/mmst.protocol', which is also in >> package kplayer >> dpkg-deb: subprocess paste killed by signal (Broken pipe) > > Please inform of this to the provider of the kplayer package (which is > not in Debian). Workaround is to uninstall kplayer, after which kdelibs-data will finishing installing; then reinstall kplayer. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kalyxo.org gone under?
>> kalyxo.org hasn't been resolvable as a domain for several months, but >> archive.kalyxo.org was still available at 62.104.23.254. Now, it doesn't >> respond. Has kalyxo.org gone under for good? Thanks, A. > > I just used > > http://kalyxo-archive.mornfall.net/ > > a few minutes ago. Thanks, yes, it seems that they've moved there. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
kalyxo.org gone under?
kalyxo.org hasn't been resolvable as a domain for several months, but archive.kalyxo.org was still available at 62.104.23.254. Now, it doesn't respond. Has kalyxo.org gone under for good? Thanks, A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDM locks me out
> After installing KDE 3.4 and KDM 3.4.0-0pre3 specifically, I found to my > displeasure after restarting that KDM won't let me in. I can't type in > the password field and after each keypress the widgets in the login > window are locked. I can access the menu item for restart, but that's > about all I can do. I noticed, that the only two session types offered > are "default" and "failsafe", notably no "KDE". Without being able to > type, though, I can't login anyway. Also, I can't switch to another > virtual console. > > To get in, I had to boot in single user mode an disable KDM. Now, I > don't think this is a bug in KDM, rather some kind of misconfiguration > on my part. Any ideas what might be causing this behavior? No, but it is worth a try to wipe KDM's configuration and reinstall. I suggest apt-get --purge remove kdm, rm -rf /etc/kde3/kdm (careful here!), then apt-get install kdm. Good luck, Andrew. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: www.kalyxo.org not available anymore?
> there was an ip.adres mentioned on the > list earlier this month (which you can use in the mean time) In /etc/hosts I have: 62.104.23.254 archive.kalyxo.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: what happened to kalyxo.org?
> * Andrew Schulman [Mon, 04 Apr 2005 05:34:09 -0400]: > > I can't resolve kalyxo.org for several days now. Did their domain name > > expire? Or did they suddenly go under? Thanks, Andrew. > > I believe they're changing registrars, and some trouble did arise in > the middle. Perhaps this line in /etc/hosts will help you: > > 62.104.23.254 archive.kalyxo.org Thanks, yes, that takes care of it. Andrew. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: OpenPGP/Mime in KMail broken in Sarge
> The problem is magically gone, now, at next reboot we'll see how long ;) I hate those. Spend hours trying to identify the cause of the problem by process of elimination, until there's nothing left... because the problem has gone away. Damn. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
what happened to kalyxo.org?
I can't resolve kalyxo.org for several days now. Did their domain name expire? Or did they suddenly go under? Thanks, Andrew. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
right way to start ksysguardd?
I'm using the KDE 3.4 packages from aleroth. I want to put a ksysguard applet in my panel, as I had in KDE 3.3. But when I start it, it can't connect to ksysguardd, because ksysguardd isn't running. I don't remember ever having to start ksysguardd myself in 3.3, or ever wondering whether it had started or how to start it. I just ran ksysguard, and it worked. Apparently ksysguardd was already running. I'm not sure what's changed now, but for whatever reason, ksysguardd 3.4 doesn't start automatically. I've compared the 3.3.2 and 3.4.0 package files, and looked around in /etc/kde3, and I don't see any obvious differences. I also don't find ksysguardd in the Control Center, under Service Manager, where I would expect to find it. So, what's the right way to have ksysguardd start automatically at boot? Of course I could write my own boot script, but I don't want to do that-- surely there must be some existing way of enabling it. Is anyone else having this problem in 3.4? Thanks, Andrew. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Locking screen doesn't work
> On Mon, Mar 28, 2005 at 09:57:18AM -0500, Andrew Schulman wrote: > > > > Do you also use the kdebluetooth package from the external > > repository? > > > > If yes, purge and reinstall it. > > > > > > thanks, locking works now (and kdebluetooth still works ;) > > > > Yikes. What the hell kind of a solution is that? kdebluetooth is > > interfering with your desktop locking? And purging and reinstalling > > fixes the problem? Why, why? > > Previous versions of the kdebluetooth .deb came with kbluelock. It used > dpkg-divert to replace /usr/bin/kdesktop_lock. > The current package does not ship kbluelock anymore but an upgrade does > not remove the dpkg-divert entry. The package removal script, however, > does this. Sheesh... thanks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: crashes and hangs in KDE 3.4
> On Monday 28 March 2005 14:55, Andrew Schulman wrote: > > > Did you try using KDE 3.4 with a freshly created KDE configuration > > > (move .kde directory out of the way and let it create a new one)? What > > > Debian version do you use? I use mostly Sarge with some parts of Sid. > > > > Yes, indeed. I always do that with a new point release of KDE: move > > .kde out of the way, start fresh, and then start customizing. > > That is very dangerous. For instance, in the new versions of kmail I think > your mail is stored in here. If you delete it, you will delete all your > mail. > > Similarly, all your bookmarks are also stored in here. Delete it, and all > your cherished heirarchy of bookmarks disappears. [I know, I did it] I didn't say delete, I said move aside, as in 'mv .kde .kde.3.3' . Your point is well taken that there's valuable information in .kde, such as bookmarks, kopete contact lists, and so on. After starting fresh with an empty config and then recustomizing it, I then reimport the data I need one application at a time from .kde.3.3 into kde. It's tedious, but to me worth it in order to start with a clean slate. In the case of kmail, I moved my mail out of .kde into .mail, by modifying kmailrc-- can't remember the details now, but it's in the kmail FAQ. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: crashes and hangs in KDE 3.4
> On Monday 28 March 2005 15:55, Andrew Schulman wrote: > > > Did you try using KDE 3.4 with a freshly created KDE configuration > > > (move .kde directory out of the way and let it create a new one)? What > > > Debian version do you use? I use mostly Sarge with some parts of Sid. > > > > Yes, indeed. I always do that with a new point release of KDE: move > > .kde out of the way, start fresh, and then start customizing. > > That shouldn't be neccesary, is it? I don't know if it's necessary, but in my experience it's worth the trouble. In the past I've found that there were new features that I never saw until I started fresh with an empty configuration-- something about the config from the earlier release suppressed the new features. Another reason is to avoid compatibility problems between old and new releases that can lead to bad behavior, such as crashes :( > To me that sounds very similar to 'Just > reinstall' on another well known OS. :( -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Locking screen doesn't work
> > Do you also use the kdebluetooth package from the external repository? > > If yes, purge and reinstall it. > > thanks, locking works now (and kdebluetooth still works ;) Yikes. What the hell kind of a solution is that? kdebluetooth is interfering with your desktop locking? And purging and reinstalling fixes the problem? Why, why? This does not speak well for KDE stability. It's as if we'd learned by luck from a passing leprechaun that the solution was to sprinkle a certain kind of fairy dust. Don't get me wrong, I'm glad you found your answer. But as I struggle with my own KDE 3.4 hassles, reading about a solution like that just sets my teeth on edge. I wonder what model of fairy dust I'll need to solve my KDE problems. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: crashes and hangs in KDE 3.4
> Did you try using KDE 3.4 with a freshly created KDE configuration > (move .kde directory out of the way and let it create a new one)? What > Debian version do you use? I use mostly Sarge with some parts of Sid. Yes, indeed. I always do that with a new point release of KDE: move .kde out of the way, start fresh, and then start customizing. And I do customize a lot; I change a lot of settings in the Control Center. My login hang started during that process-- at some point I couldn't reliably log in again. This was before I configured any applications; just Control Center settings. I isolated a few that seemed to cause the trouble (e.g. turning off certain system sounds, setting up a kwallet), but it's not convincing; I think it's some interaction that causes the trouble. This is one of the frustrating things about it. Start clean, and you should get a clean result. I'm using the latest Debian packages from alioth. My system is also Sarge with some Sid. > I dont want to go back to KDE 3.3. I like 3.4 quite much. It crashes less > than KDE 3.3. The Kontact crash-on-exit behaviour that I had with 3.3 is > completely gone now for example. Well I'm glad to hear it, and it does seem that most other users aren't having all of the problems that I am. Andrew. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
crashes and hangs in KDE 3.4
I love KDE, and 3.4 is the best and nicest looking version yet. But I'm sick of my applications crashing all the time. kicker and kopete both crash every time I log out. k3b crashes every time I drag several files into a project list. juk crashes every time I select a certain playlist. I made the playlist, and later changed some of the file names. Now to get rid of it I'll have to either undo the file name changes, or else hack my juk config files. knode crashes randomly, about once a day. And, my login still hangs about 75% of the time as it restores the session. I have to log in on a different VT and pkill klauncher, after which login continues. Is this just me? Or are other people suffering from this too? It almost makes me want to go back to 3.3. Thanks, Andrew. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kde3.4.0 lock at startup
> when Konversation is launched automaticaly at login. > > I had to remove the konversation stuff in the ksmserverrc to be able > to use kde. I've filed a bug report against klauncher for this. See http://bugs.kde.org/show_bug.cgi?id=102046. I'm not sure if klauncher is the right app to file the bug against; maybe it should be ksmserver. But that's as well as I can figure it right now. Please add your information to the bug report. If more than one person reports it I think they'll be more inclined to pay attention. Thanks, Andrew. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE 3.4: multiple hangs at login
> I'm running KDE 3.4.0-0pre2 from the Debian packages at alioth.debian.org. > I'm having a problem that when I customize some of KDE's settings, both in > the control center and in some applications, the next time I log in the > login will hang towards the end, somewhere during the "Loading panel" > phase. The mouse pointer still moves, but the desktop is locked up hard. > I have to switch to a different VT and kill a bunch of processes to get > that VT back. I've filed a bug report about this, http://bugs.kde.org/show_bug.cgi?id=102046. I've also determined that klauncher is the process that's hanging. This is useful, because I don't have to kill my whole login session to get past the hang; I just kill klauncher. This means that not all of my previous session gets restored, but at least I can log in without having to rm -rf .kde; cp -a .kde.bak .kde every time. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kde3.4.0 lock at startup
> when Konversation is launched automaticaly at login. > > I had to remove the konversation stuff in the ksmserverrc to be able > to use kde. Sounds like the same problem I reported yesterday. See my message yesterday about "KDE 3.4: multiple hangs at log in". I'm going to open a bug report about this as soon as I have time. When I do I'll post the URL here. Please add your observations to it, so the developers will pay attention. I don't know anything about ksmserver or ksmserverrc, but looking at my ksmserverrc now, apparently it has the information about which apps to restart at login. This is good to know; maybe I can manipulate it make my logins easier. Also, this gets to the question of which KDE app I should file this bug report against. KWin? ksmserver? I have no idea. If I can find the right app to file the bug against, we'll get a faster response. Andrew. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
KDE 3.4: multiple hangs at login
I'm running KDE 3.4.0-0pre2 from the Debian packages at alioth.debian.org. I'm having a problem that when I customize some of KDE's settings, both in the control center and in some applications, the next time I log in the login will hang towards the end, somewhere during the "Loading panel" phase. The mouse pointer still moves, but the desktop is locked up hard. I have to switch to a different VT and kill a bunch of processes to get that VT back. When I installed KDE 3.4, I started fresh as I always do with a new release, by moving aside my .kde directory and reconfiguring everything from scratch. I import some files from .kde-old/share/apps and .kde-old/share/config as needed. Unfortunately, as I customize things more and more, at some point if I log out and then log back in again, the login hangs. There seem to be many settings that cause this behavior. I haven't been able to isolate them all, but I have definitely isolated two: (1) Turning off the annoying login music. In the Control Center this is Sound -> System notifications -> KDE System Notifications -> KDE is starting up. In .kde/share/config/knotify.eventsrc, turning off that sound changes "1" to "0" in the section [startkde] commandline= logfile= presentation=1 soundfile=KDE_Startup_1.ogg And indeed, I can now reliably turn the hang on and off (at least, with respect to this setting) just by changing that presentation setting from 1 to 0 and back again. When I set presentation=0, login hangs. When presentation=1, it doesn't. (2) As soon as I configure a kwallet, login will hang every time. Even removing .kde/share/config/kwalletrc and .kde/share/apps/kwallet doesn't solve the problem; I have to delete .kde and restore it from backup. I love my new 3.4 desktop, but this is turning into a real hassle. Every time I change any setting at all, I have to stop my work, log out and log in again, and see if the login hangs. If it does, I have to give up on that setting, kill all my processes, and restore my old settings. If it doesn't hang, then I have to make a new backup of .kde. And, besides that, I can't use my kwallet. This is not good. I've been looking around for other reports of this problem, but haven't seen any. I haven't filed a bug report with KDE yet but will probably do so soon. Does anyone have any ideas about causes or workarounds for this problem? Heard of the same problem anywhere else? KDE 3.4 is the most beautiful and functional KDE yet. I'm already hooked on my beautiful transparent red cursors. I don't want to go back to 3.3! Thanks, Andrew. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Where do i get 3.4?
> > Also, I haven't found i18n packages :\ > > Yes, we know it's pending. The person in charge for it will probably > prepare it "soon". Along this line... I don't wish to sound greedy, as I'm very pleased to see most of KDE 3.4 already available through aleroth. But... I'm dying to see the new "fast user switching" feature in kdm, as I participated in the bug report that led to its creation. The developer closed the bug report 6 months ago, saying that he'd implemented the feature... in KDE 3.4! So now the moment has finally arrived! but I don't see the new kdm on aleroth yet. Any idea how much longer we'll have to wait? Thanks, Andrew. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KMix and Krec
> 3) Non of this is mentioned in the help file The help file has almost no useful information in it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE 3.3.1 in Sarge
> If I start kate from konsole, I get tons of messages like:
> ASSERT: "!m_doc->wrapCursor()" in ../../../kate/part/katerenderer.cpp
> (626)
kate always throws out reams of failed assertions to the console. I got
sick of it and now use
function kate
{
/usr/bin/kate "$@" 2>/dev/null
}
--
To reply by email, replace "deadspam.com" by "alumni.utexas.net"
Re: DPMS doesn't work with KDE
> I have a valid XF86Config-4 file with DPMS enabled, and I can turn the > monitor off when I run a window manager different from KDE. > > However with KDE 3.3.1 I have set DPMS in the display settings of the > control center but it has no effect. The value I entered are here, but > the screen will never shut down. > > $ xset q > [...] > DPMS (Energy Star): > Standby: 300Suspend: 600Off: 900 > DPMS is Enabled > Monitor is On > [...] > > Under KDE the command "xset dpms force off" (off or whatever) will do > nothing. My monitor just sits there, as if I had never done anything. Hm, what I found was that under kdm, DPMS settings in XF86Config-4 had no effect, but settings in the KDE Control Center did work. But then again, sometimes they don't. If my screen won't shut off, I have to restart my X server, then DPMS works again... but maybe only for a while. :| -- To reply by email, replace "deadspam.com" by "alumni.utexas.net"
Re: Can we lose the 'KDE is cool' blurb, please
> I recently wondered what kooka was and entered 'apt-cache show kooka'. It > tells me how cool KDE is, but only at the end do I see what kooka is. Same > with all (most?) other KDE packages. > > Can we lose that 'KDE is cool' blurb in every package description, please > (except in the kde metapackage obviously and probably the kdebase/kdelibs > packages.) It doesn't add any relevant information and makes it harder to > locate the information which I actually want to see. I agree, it gets annoying to read that same little promo attached to every KDE package.
Re: krdc requires rdesktop 1.3.2, but only rdesktop 1.3.1 is available
> > Any of you know why version 1.3.2 is required? What are those outstanding > > features? (just kidding :P) > see bug 268896 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=268896) > and 269013 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=269013) Also 267434 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=267434). I find this extremely annoying. The krdc authors made it depend on a version of rdesktop that doesn't exist yet, so the Debian maintainers had to either fix it themselves, or else declare it in conflict will all existing versions of rdesktop. They did the latter. As a result, krdc is now unusable if you want to keep using rdesktop. krdc is a front end. Why should it conflict with all existing versions of the thing it's supposed to be a front end for? Stupid.
Re: Upgrading from 3.1.X to 3.2.2 : KDM not working anymore
> Le mercredi 28 Avril 2004 16:23, Andrew Schulman a écrit : > > > > Does this happen for all users, or just charles? > > It happens just for charles, for other users (for example root) it works. > > I've tried dpkg --purge kdm and reinstalling it to get clean configuration > files but it did not solve my problem. > > What is happening when I try to log with user charles is that the screen goes > black for a second and kdm resets itself. So I guess, that after the > authentification the X server crashes and resets itself. Charles, try removing your ~/.xsession, if you have one. I've been having the same trouble lately. I haven't finished figuring out why yet, but when I remove ~/.xsession it goes away.
Re: Upgrading from 3.1.X to 3.2.2 : KDM not working anymore
> KDM starts and I get the greeting screen but the login for a user fails and > bring back the greeting screen. I have to do a console login and startx to > launch KDE. Does this happen for all users, or just charles?
Re: X mysteriously slow, no clue why
> I have this REALLY weird problem right now. My whole X has suddenly > started to be really slow. KDE used to be really snappy and nice to > use, now it's really sluggish and slow to respond. Have you changed your firewall settings lately? This slowness happened to me once when, by mistake, I set the default policy in the iptables nat and mangle tables to DROP. That stopped all traffic on the loopback interface, which made my whole system (but especially KDE) slow to a crawl. Took me about a week to figure it out. You can check this easily. Run the following commands as root: # Allow all traffic to pass on the loopback interface iptables -A INPUT -i lo -j ACCEPT iptables -A OUTPUT -o lo -j ACCEPT # Set default ACCEPT policies on the nat and mangle tables iptables -t nat --policy PREROUTING ACCEPT iptables -t nat --policy POSTROUTING ACCEPT iptables -t nat --policy OUTPUT ACCEPT iptables -t mangle --policy PREROUTING ACCEPT iptables -t mangle --policy INPUT ACCEPT iptables -t mangle --policy FORWARD ACCEPT iptables -t mangle --policy OUTPUT ACCEPT iptables -t mangle --policy POSTROUTING ACCEPT Good luck, Andrew.
Re: 3.1 to 3.2 observations
> 1. Bookmarks disappeared. Specifically my konq bookmarks > located at ~/.kde/share/apps/konqueror/bookmarks.xml got overwritten > by an empty template. Most disconcerting. I'll be damned... same thing happened to me. That's ugly. -- To reply by email, replace "deadspam.com" by "alumni.utexas.net"
Re: WP8 for Linux is toast in KDE 3.2
Hey! AbiWord reads AND WRITES WordPerfect documents! I haven't given this feature heavy exercise yet. No doubt it has problems with complicated content, blah blah blah. But it works on my simple memos. Not to mention that it has a modern look and feel, and my mouse scroll wheel works. Way to go AbiWord!
Re: WordPerfect 8 still lives
> Andrew, if you have a Corel CD, you should have the package wp-full. > That is the name of the .deb package on the CD, to be precise, on my > old Corel Linux OS Deluxe CDs from 2000. No, I just checked and unfortunately there's no such package on my CD. Note that my CD doesn't say "Deluxe", just "Corel WordPerfect 8 for Linux". > Linux does its utmost to avoid the ".DLL hell" of Windows through its > conventions for naming and numbering libraries. Thus we should be able > to get by with the version provided by libXT6. I would have thought so, yes. But xlibs 4.3 conflicts with xlib6, and there has to be a reason for this. An API incompatibility between the new and old versions sounds like a likely reason to me. > By the way, the package that is causing the problem is "xlib6g". Not the > final "g". I found these details with "apt-cache show . No, because I don't have xlib6g installed. 'apt-cache show' shows me the following: $ apt-cache depends xlibs | grep xlib6 Conflicts: xlib6 Conflicts: xlib6g Conflicts: xlib6g-dev Replaces: xlib6 Replaces: xlib6g Replaces: xlib6g-dev So this is pretty straightforward. And in fact, when I upgraded to xlibs 4.3, it forced me to uninstall xlib6. When I first installed WP8 a year ago, I made notes about what I had to do to get it to run. My notes say that I needed to install the following packages: libc5, xlib6, and xpm4.7, all from oldlibs. Sorry to be such a downer, Bruce. I do appreciate your help. OTOH, at least some people are apparently running WP8 with xlibs 4.3. So I guess I have to find the right combination somehow. I wonder what's different about that wp-full .deb.
Re: WP8 for Linux is toast in KDE 3.2
> KDE 3.2 depends on xlibs 4.3.x, which conflicts with xlib6, which is > required for WP8 for Linux to run. Therefore, WP8 is toast. Following a suggestion from Hendrik Sattler, I unpacked the xlib6 package into its own directory: $ dpkg -x /var/cache/apt/archives/xlib6_3.3.6-44_i386.deb /opt/xlib6 and tried to start WP using those versions of the X libraries: $ LD_LIBRARY_PATH=/opt/xlib6/usr/i486-linuxlibc1/lib /opt/wp8/wpbin/xwp When I do this WP starts, and I see the initial splash screen. Then it segfaults. By comprarison, $ /opt/wp8/wpbin/xwp /opt/wp8/wpbin/xwp: can't load library 'libXt.so.6' So it seems that using the old libraries almost works, except that it doesn't. My guess is that the old xlib6 libraries are just incompatible with xlibs 4.3, in which case there's really no way to run WP8 in KDE 3.2. So my options for reading and writing WP documents in Linux are dwindling. I can run WP2K for Linux, or set up a virtual Windows machine just to run WP. I'll also look into AbiWord, although I need to be able to write WP documents, not just read them. Any other solutions, please let me know. Andrew. -- To reply by email, replace "deadspam.com" by "alumni.utexas.net"
Re: WordPerfect 8 still lives
> I alerted Daniel Stone to this issue in December; I also found > that the solution is to rewrite the file /var/lib/dpkg/status to > remove the dependency of the package wp-full to xlib6g. The > files previously in that package are now provided by another > package, and I have been running wp 8 this way for nearly 2 > months. I don't follow. First, I don't have a wp-full package, and I don't have a reference to one either. I installed WP8 from a Corel CD. Second, the problem I see is: - KDE 3.2 needs xlibs 4.3. - xlibs 4.3 conflicts with xlib6. - WP8 needs xlib6. In order to install KDE 3.2 I had to uninstall xlib6, and now when I try to run WP I get $ /opt/wp8/wpbin/xwp /opt/wp8/wpbin/xwp: can't load library 'libXt.so.6' Of course there are other versions of libXt.so.6 in my system, e.g. from xlibs. But it's the old version from xlib6 that WP needs. Hendrik Sattler pointed out to me in email that I should get around the package conflicts by manually installing the files from the xlib6 package somewhere else on my system, so that WP can use them. Then probably set LD_RUN_PATH to tell WP where to find them. I'll try this, and post the solution if I get it to work.
Re: Could not start Kdeinit. Check your installation
> Can anybody help me whit this problem? Try Google. There was a long thread with this same subject a few weeks back. Lots of possible solutions. Good luck, Andrew. -- To reply by email, replace "deadspam.com" by "alumni.utexas.net"
WP8 for Linux is toast in KDE 3.2
KDE 3.2 depends on xlibs 4.3.x, which conflicts with xlibs6, which is required for WP8 for Linux to run. Therefore, WP8 is toast. But we still need to run WP here. AFAICT, the only other option is WP2K4L. I'll consider buying a copy, but I want to be sure first that it will work with KDE 3.2. Is anyone else running this combination? How's it working for you? I looked into Star Office, which is supposed to have a read/write WP conversion filter. But it turns out that the WP filter isn't included in the Linux version. Are there other KDE 3.2 users who are reading and writing WP documents? What's your solution? Thanks, Andrew.
Re: kde 3.2 Woody screensaver does not work
> Hello, > Recently i migrate from Kde 3.1.4 to Kde 3.2. > I configure the screensaver with the kde configuration center, and very few > screensaver among all proposed works and can be tested. But the screensaver > does not work at all. Try installing xscreensaver and xscreensaver-gl. -- To reply by email, replace "deadspam.com" by "alumni.utexas.net"
Re: "Could not start kdeinit. Check your installation and try again."
> checking for Qt... configure: error: Qt (>= Qt 2.2.2) (library qt-mt) not > found. Please check your installation! This is a FAQ (or at least a FEP = frequently encountered problem). For help see http://wiki.debian.net/index.cgi?DebianKDE, question 4, and then follow the link to the "Qt trouble" document. For me, the short version is: install libqt3-mt-dev, libqt3-compat- headers, and kdelibs4-dev, then ./configure --with-qt=/usr/share/qt3 But the references above will give you more complete information. Good luck, Andrew. -- To reply by email, replace "deadspam.com" by "alumni.utexas.net"
Re: "Could not start kdeinit. Check your installation and try again."
>> Hello. I have KDE 3.2, under Debian testing/unstable. I wiped clean my >> previous installation of KDE 3.1 (apt-get --purge, rm -rf /etc/kde3) and >> reinstalled from the .deb's at download.kde.org. > > You do realize, don't you, that you installed woody backports of KDE 3.2 > which were built with gcc 2.95, and so are incompatible with your qt and > all other c++ packages from testing/unstable. > > This might be the cause of your problems. Thank you. I removed the packages for stable, and installed the packages for unstable. Most (though not quite all) of my KDE problems have been solved, including the dreaded "Could not start kdeinit." I just love my new KDE desktop.
Re: "Could not start kdeinit. Check your installation and try again."
>> Hello. I have KDE 3.2, under Debian testing/unstable. I wiped clean my >> previous installation of KDE 3.1 (apt-get --purge, rm -rf /etc/kde3) and >> reinstalled from the .deb's at download.kde.org. > > You do realize, don't you, that you installed woody backports of KDE 3.2 > which were built with gcc 2.95, and so are incompatible with your qt and > all other c++ packages from testing/unstable. > > This might be the cause of your problems. Er... hm. An excellent point.Let me check into that. While I'm doing that: right now I don't find any KDE 3.2 release .deb's for unstable. The closest I see is CVS from 2004-01-26, at http://rs.fuzz.nl muesli/686/kde_head/. Correct? Or am I missing something? Thanks, Andrew.
