Re: [kde] File selectors
On 04/11/15 11:33, Hussam Al-Tayeb wrote: > On Wed, 2015-11-04 at 10:06 +, Duncan wrote: >> Same general answer here, but with a couple additional notes: >> >> * Firefox: There is an option, exposed by the configuration mania >> extension if you have it installed but what config mania does is >> simply >> provide a UI option to change options you'd otherwise have to change >> via >> about:config editor, so obviously it's an about:config option >> regardless >> of whether config mania is installed or not... >> >> Anyway, in configuration mania, the option is UI > Other > Bottom of >> the >> page > Use XUL file picker even if system file picker is available. >> Looking at about:config, I think the option there is >> ui.allow_platform_file_picker. >> > Thanks for the replies - at least I have been able to set the Firefox file picker to use the standard KDE dialog. I guess for the others I just need to "celebrate the diversity of the linux ecosystem"... Bogus Zaba -- Dr Bogumil N Zaba ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
[kde] File selectors
Is there any way of forcing just one file selector to be used by all applications working within the KDE Environment. I am using Slackware 14.1 with KDE 14.10.5 and currently I see at least three different selectors: oOne in native KDE applications (Gwenview, digikam etc) oOne in various non-KDE apps (GIMP, LibreOffice etc) oOne unique (I think) to Firefox I neither love nor hate any of them but would prefer it if I got the same selector every time I wanted to open or save a file. I appreciate that this is a rather basic question and I believe that it has been discussed previously but I have not found an answer through searching in past discussion. Thanks Bogus -- Dr Bogumil N Zaba ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] K-Menu - High-lighting a bit too subtle
On 11/08/14 05:45, Duncan wrote: Bogus Zaba posted on Sun, 10 Aug 2014 17:58:36 +0100 as excerpted: KDE 4.10.5 as supplied with Slackware 14.1. I sometimes need to use the K-Menu to find an application and when I do so, I find that the default way selected items are highlighted as you scroll along them with either mouse of keyboard is a bit subtle. I would prefer to be able to see more readily where my cursor is. This is especially true on my laptop where the screen needs to be a the right angle (and not too much sunlight interfering etc). Is there anywhere you can configure this setting? Perhaps a theme? K-Menu can mean several different things in kde4. What type of k-menu, classic, kickoff, other? ... If you're using the kickoff style kmenu, the behavior and configuration is totally different, as that's part of the plasma workspace, covered by its own settings and widget theme, not the standard kde color settings and widget styles. Why the chose to have two entirely different sets of widgets configured in two entirely different places using two entirely different rulesets I don't know, as all it does is confuse people, but it has been that way for all of kde4, and won't be changing in kde4 now. What kde frameworks5 and plasma5 are doing with it I don't know, but one could hope they've done /something/ about that situation. Anyway, yes, in that case the configuration is via theme -- there's no GUI for configuring specific settings and you may have to directly-edit the theme files if you can't find a theme that does what you want. The configuration, such as it is, is still kde system settings but in an entirely different location, under workspace appearance and behavior, workspace appearance, desktop theme. Other than changing the entire theme on the theme tab, you can switch to the details tab and customize by choosing among installed themes for each individual component. For instance, you can use the default oxygen theme for most components but use the air theme for just the kickoff menu, if you like. It was Kickoff I was talking about, so your advice (above) on this was relevant. The only problem is that although changing the theme (including changing it just for Kickoff using the details tab), changes various aspects of the display, the one thing that remains constant for all themes I have tried is the method of highlighting the items under the cursor. This is done by drawing two light grey lines above and below the item to be highlighted (on a white background). But as I said, beyond that, you pretty much have to manually edit the individual theme files directly. It can be done, but it's not easy unless you want to become a kde4 plasma themes expert, and it's a bit late for that as the first releases of kde frameworks5 and plasma5 are already out, and will likely be shipping in distros next year, if not later this year for some, so you'd only have a relatively short time to use that expert knowledge. If you can point me at the relevant config files I will have a quick look, but as you say this is not something that it is worth spending a huge effort on. Thanks for your help bogzab Dr Bogumil N Zaba ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] K-Menu - High-lighting a bit too subtle
On 11/08/14 13:27, Duncan wrote: Bogus Zaba posted on Mon, 11 Aug 2014 08:29:08 +0100 as excerpted: It was Kickoff I was talking about, so your advice (above) on this was relevant. The only problem is that although changing the theme (including changing it just for Kickoff using the details tab), changes various aspects of the display, the one thing that remains constant for all themes I have tried is the method of highlighting the items under the cursor. This is done by drawing two light grey lines above and below the item to be highlighted (on a white background). OK, now that I know it's kickoff you're looking at, I actually did some experimenting, and found out that it's actually only the kickoff frame that's affected by the plasma/workspace theme. The good news is that I found out what to change to change the kickoff menu highlighting. The bad news is that changing that changes some other things too, and at least here, some of those things I want light and some dark, which makes for a challenge, to say the least. The setting is actually in kde's main colors, found in kde system settings, common appearance and behavior, application appearance. Once there, I *STRONGLY* recommend reading the help text (also available, if installed, in khelpcenter, system settings modules, colors), because there's a two-dimensional color organization, sets vs roles, that definitely takes some reading and then a bit of experimentation to get the hang of, but without that reading, the stuff that changes with each config change will seem almost random and the result will be VERY quick frustration! I certainly see what you mean - having read through the help a couple of times I think I understand it very slightly better than before... Not sure if I could explain it to anybody else though. Once you've read the help text and at least have an idea of what color sets and roles are all about, then it's time to try to change this, without making something else too horribly wrong. First, if you've changed anything else from whatever color scheme you started with, you should probably save your changes to a new scheme that you can always reset to if you don't like how the changes ended up. If not, first just make sure you know what scheme you're on so again you can reset back to it. With that done... Switch to the colors tab. There are two ways to set the particular setting we're after. It's available as either common colors, selection background, or selection set, normal background. The kickoff menu background, meanwhile, is available as common colors, view background, or as view set, normal background. So yes, I can make some changes here and, as you suggest, if you make sure that the side-effects are not too drastic those changes could even be described as improvements. Played only with the desktop PC so far and the one on which they problem was most annoying was the laptop so I will move onto that tomorrow. So you have a selection set, normal background, set off on a view set, normal background. Change either one to contrast with the other, hit apply, and you should immediately see the effect on the kickoff menu. The problem is everything else that's affected as well. Major parts of most windows will be view background, so changing it changes a lot. Selection background should be a bit easier to change since it's only used in the less common selection context, but be sure to select some text in some window somewhere (the khelpcenter window is a good place, if you still have it open) and be sure the effect isn't worse than the one you're fixing in kickoff. Many thanks for your help on this. Doubt if I would have got there by clicking away at the System Settings menus. btw How come you've stopped providing your standard paragraph which we all came to enjoy over several years about System Settings being the wrong name for that KDE module?? Thanks again bogzab -- Dr Bogumil N Zaba ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
[kde] K-Menu - High-lighting a bit too subtle
KDE 4.10.5 as supplied with Slackware 14.1. I sometimes need to use the K-Menu to find an application and when I do so, I find that the default way selected items are highlighted as you scroll along them with either mouse of keyboard is a bit subtle. I would prefer to be able to see more readily where my cursor is. This is especially true on my laptop where the screen needs to be a the right angle (and not too much sunlight interfering etc). Is there anywhere you can configure this setting? Perhaps a theme? Thanks bogzab -- Dr Bogumil N Zaba ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] kdm multiple keyboard layouts
On 03/27/2013 10:18 AM, zoolook wrote: Hello, First, is there a kdm-users dedicated mailing list? Now my question. I'm learning Dvorak keyboard layout but I share this computer with my wife. She doesn't like the layout so I need kdm to default to latam layout and have dvorak as a option (either a keyboard shortcut or a menu option) so I don't have to remember two passwords. Is this possible? Thanks!! Norberto ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html. System settings Input Devices Keyboard Layouts. The settings form there allows you to add various keyboard layouts. Once these have been activated an icon in the notifications area of your panel tells you which keyboard layout is active at the time. I use this to switch between UK, UK-international and Polisk keyboard layouts. Just click the icon and you cycle through them, once you have set them up in System Settings. ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] kdm multiple keyboard layouts
On 03/27/2013 09:16 PM, zoolook wrote: On Wed, Mar 27, 2013 at 5:11 PM, Bogus Zaba bog...@bogzab.plus.com mailto:bog...@bogzab.plus.com wrote: On 03/27/2013 10:18 AM, zoolook wrote: Hello, First, is there a kdm-users dedicated mailing list? Now my question. I'm learning Dvorak keyboard layout but I share this computer with my wife. She doesn't like the layout so I need kdm to default to latam layout and have dvorak as a option (either a keyboard shortcut or a menu option) so I don't have to remember two passwords. Is this possible? Thanks!! Norberto ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html. System settings Input Devices Keyboard Layouts. The settings form there allows you to add various keyboard layouts. Once these have been activated an icon in the notifications area of your panel tells you which keyboard layout is active at the time. I use this to switch between UK, UK-international and Polisk keyboard layouts. Just click the icon and you cycle through them, once you have set them up in System Settings. I want kd_M_ (kde's display manager) to be mutiple-keyboard-layout aware :-) I want to be able to switch between 2 keyboard layouts in kdM. Or is there something I'm missing? I see no icon to switch layouts in kdM. Thanks! Sorry, I misread your original post. I think you are right there is no kdm option to change keyboard layouts - the thing I was describing comes after you have logged in using kdm. There may be options to achieve what you want by logging into your system in a plain text console rather than using a display manager login. You might then be able to set locale / keyboard map in the console and afterwards start your gui with startx? ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] KDE Desktop effects
On 09/18/2012 02:21 AM, Duncan wrote: Bogus Zaba posted on Mon, 17 Sep 2012 20:13:42 +0100 as excerpted: Did not work, but maybe there there is a clue here because this middle tab is... completely empty! There is a one-line text box into which you can type a search term and a much bigger box which presumably should contain a long list of effects which I should be able to play with. This is weird because the system clearly does know about available effects because on the first tab I have set (for example) : Effect for window switching to Box Switch from a pick-list. Wow! I'd say that probably has something to do with it, for sure! But it's totally out of the blue, for me. I've never seen or heard anything like it! Two possibilities and if those (and sdowdy's suggestions) don't pan out, hit bugzilla and see if there's anything close. I'd say file a bug if you don't find anything like it, but what they're working on now is one and a half to two years of development beyond the 4.6 you're running, so it's probably not worth even thinking about at this point, if there's nothing already there about it. Once the new Slackware's out and you're on 4.8.x, however, if the bug's still there, I'd file it. There are only two possibilities I can think of that would be anywhere /close/ to that. 1) Check to be sure, you're running kwin as the window manager, correct? Obviously if it somehow got replaced by compiz or the like, there'd be some dramatic loss of window manager configurability within kde, but I've never tried it, so I'm not sure what the symptoms would look like. Probably the easiest way to be sure kwin's your window manager is to run kwin --replace, from krunner or the like. You might also try from konsole or the like, and see if it spits out any useful information as errors, but if it's like most kde apps, devs apparently don't expect users to be watching STDOUT/STDERR at all, so they print out all kinds of alarming looking stuff even when things are working, for all one can tell. As a result, that output tends to be useless for troubleshooting unless you have another similarly configured system that's working to try it on as well, and can do a diff to eliminate all the normal noise. kwin --replace seemed to work just fine - everything looked exactly like it did prior to the command, plus I got the following valuable (?) output in konsole. It is clearly warning me that some effects are not supported, although it remains a mystery as to why. bogzab:~/Documents kwin --replace OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce 7300 SE/7200 GS/PCIe/SSE2/3DNOW! OpenGL version string: 2.1.2 NVIDIA 295.33 OpenGL shading language version string: 1.20 NVIDIA via Cg compiler Driver: NVIDIA Driver version: 295.33 GPU class: NV40/G70 OpenGL version: 2.1.2 GLSL version: 1.20 X server version: 1.9.5 Linux kernel version: 2.6.37 Direct rendering: yes Requires strict binding:no GLSL shaders: limited Texture NPOT support: yes kwin(1021) KWin::EffectsHandlerImpl::loadEffect: EffectsHandler::loadEffect : Effect kwin4_effect_blur is not supported kwin(1021) KWin::EffectsHandlerImpl::loadEffect: EffectsHandler::loadEffect : Effect kwin4_effect_flipswitch is not supported kwin(1021) KWin::EffectsHandlerImpl::loadEffect: EffectsHandler::loadEffect : Effect kwin4_effect_startupfeedback is not supported kwin(1021) KWin::EffectsHandlerImpl::loadEffect: EffectsHandler::loadEffect : Effect kwin4_effect_screenshot is not supported kwin(1021) KWin::EffectsHandlerImpl::loadEffect: EffectsHandler::loadEffect : Effect kwin4_effect_coverswitch is not supported ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] KDE Desktop effects
On 09/17/2012 03:16 AM, Duncan wrote: But writing all the above made me think of another troubleshooting suggestion. =:^) On the middle tab, try disabling ALL INDIVIDUAL effects (even the ones you don't want to do without, permanently, and that you believe should work). Hit apply. Now on the advanced tab see if with all/individual/ effects disabled, you can successfully switch to opengl. Hopefully that works. If so, you can try enabling individual effects one at a time and see what's killing it. But, be prepared to crash and to edit/rename/delete kwinrc to get back into kde, if necessary, because the one you just tried isn't working, and with kwin's all-or-nothing approach back then, there IS a fair chance that when you enable that one, you'll trigger a crash and won't be able to get back into kde until that bit of the config is removed. Did not work, but maybe there there is a clue here because this middle tab is... completely empty! There is a one-line text box into which you can type a search term and a much bigger box which presumably should contain a long list of effects which I should be able to play with. This is weird because the system clearly does know about available effects because on the first tab I have set (for example) : Effect for window switching to Box Switch from a pick-list. dE. wrote : On 09/17/2012 02:57 PM, dE . wrote: Did you try this out with a new user Yes and the result is all desktop effects are disable with a message on the main tab of the desktop effects module which says: Desktop effects are not available on this system due to the following technical issues: (Blank space below...) ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] KDE Desktop effects
On 09/15/2012 03:40 PM, Duncan wrote: Bogus Zaba posted on Fri, 14 Sep 2012 19:59:15 +0100 as excerpted: I am not desperate to have all possible eye-candy operating, but I know that my system is capable of reasonable performance with regard to stuff like box-switching etc because it has worked before. The system has an nvidia GeForce 7300 card and I am using the nvidia (proprietary) driver. The KDE is 4.5.5 under Slackware 13.37 which is the best I can run under Slack 13.37 without making some other significant system changes. Recently KDE allows me to use only the XRender compositing type which provides a jerky experience if desktop effects are turned on. If I try and switch to OpenGL I get Failed to activate desktop effects using the given config options and it reverts to jerky Xrender. I have re-installed the nvidia driver and am sure it is working OK because the nvidia Server settings utility does what is expected (provides a cursor shadow for example). This utility also reports all sorts of OpenGL parameters and so it looks like OpenGL should work OK. Why is KDE not playing nicely? What kernel version? What xorg-server version? Did you upgrade those since it worked properly? What about your nvidia driver? If the rest of your system is as old as the now two years old kde 4.5 (tho 4.5.5 isn't quite that old... November/December), but you tried upgrading either the kernel or the video driver (or xorg-server, but that's less likely to be upgraded on its own I'd guess), they're probably expecting something newer. Kernel is 2.6.37.6 - as supplied with Slackware 13.37. xorg-server seems to be 1.9.5 as supplied with Slackware 13.37. The nvidia driver is 295.33 as supplied by the semi-official Slackbuilds.org repository. So none of the above are very recent upgrades - all about 1 year old. As I was getting this information together I remembered that there was a published reliable way of upgrading to KDE 4.6.5 from 4.5.5 without making major changes to the system, so I went ahead and upgraded. All seems to have worked well - KDE reports that it is now at 4.6.5, but same message when I try and switch from Xrender to OpenGL for desktop effects. Of course if you upgrade your kernel, you need to rebuild your servantware drivers against the new kernel, but failing to do that usually results in not being able to get into X at all (or at least it did back shortly after the turn of the century when I last ran nVidia graphics, something I've stayed away from since due to their lack of cooperation with the FLOSS community), so /that/ shouldn't be the problem. Just to confirm. There's an app called glxgears. You can run it and see the gears still? If so, you have at least /minimal/ glx (glx = (open)gl-X). If not, your glx is broken. Check - this works fine and glxgears reports about 1700 fps. And on the same (third/advanced) tab of the desktop effects applet, IDR if kde 4.5 had it or if it was added later, but if you have a checkbox for opengl shaders, try unchecking that. Older hardware/software didn't work well with that. Here are the options on this tab (in KDE 4.6.5): * Disable functionality tests (right under the compositing type drop-down list. This is checked. * Keep window thumbnails (This is set to never) * Scale method (Set to crisp rather than smooth) * OpenGL mode (Set to Fallback rather than Texture from pixmap or shared memory * Enable direct rendering (Checked) * Use vsync (also checked) I have played randomly with many of these but no combination that I have tried has fixed the won't-switch-to-OpenGL problem. Also, along about the kde 4.5 era, kwin was blacklisting certain combinations of hardware and drivers due to problems they've since worked out. It's possible that whatever you're running is or was blacklisted. Check kwinrc (probably in ~/.kde/share/config/). You may wish to try renaming that file (with kde not running of course) and starting kde/kwin to have it recreated clean. I did try renaming kwinrc in kde 4.5.5. This did not help either, but I will try with the newer 4.6.5 later on today. Finally, what window decoration are you running? Some of those, particularly the customizations available on kdelook.org, etc. (as opposed to those shipped by kde), have been known to trigger various issues. KDE's native oxygen decoration is one of the more challenging of the native/shipped decorations, so you might try one of the others. (Personally, I've run the kde2 decoration since... well... kde2, without the issues I sometimes see others mentioning for other decorations. But it's also not quite as featureful. YMMV.) I was using Modern system. I switched to KDE2 but again this did not solve the problem. We are expecting a new Slackware version any day now which will ship with KDE 4.8. I am inclined to wait now until this is released after which I will upgrade or fresh-install. Could well be that the upgrade will cure the problem
[kde] KDE Desktop effects
I am not desperate to have all possible eye-candy operating, but I know that my system is capable of reasonable performance with regard to stuff like box-switching etc because it has worked before. The system has an nvidia GeForce 7300 card and I am using the nvidia (proprietary) driver. The KDE is 4.5.5 under Slackware 13.37 which is the best I can run under Slack 13.37 without making some other significant system changes. Recently KDE allows me to use only the XRender compositing type which provides a jerky experience if desktop effects are turned on. If I try and switch to OpenGL I get Failed to activate desktop effects using the given config options and it reverts to jerky Xrender. I have re-installed the nvidia driver and am sure it is working OK because the nvidia Server settings utility does what is expected (provides a cursor shadow for example). This utility also reports all sorts of OpenGL parameters and so it looks like OpenGL should work OK. Why is KDE not playing nicely? Thanks ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] Activity epiphany
On 10/13/2011 12:14 PM, Duncan wrote: Over the months and years since kde4 came out, I've read a lot about activities... and they always seemed nice in an abstract wow, it's nice they can do that kind of way, but not necessarily something I'd use a lot, personally, tho I couldn't really put my finger on why I wasn't as personally enamored with them as I might be. Today I figured it out. The trigger for my epiphany was reading yet another blurb about another article by Aaron Seigo on activities, as it happened, on his epiphany that lead to the ideas that have gradually evolved into activities as we know them in kde (and the new plasma-active). Here's the article: http://aseigo.blogspot.com/2011/10/activities.html Quoting the first couple paragraphs (combined) as they appeared in my feed reader: Several years ago now I had a minor epiphany while doing field research in the offices of friends and work associates on how people use their computers. The ideas led to the concept of Activities, which I originally called Projects (we changed the name because it was about more than just things we could call a project).The idea was fairly grand: you communicate to the computer what you are currently doing and it adapts to that. You would be able to teach it what it means to be doing that thing: I use these files, talk to these people, need this network connection, want these applications ... The teaching would happen over time as you engage in your activity, whatever it might be. As I said, I finally got it, I think, and why altho it's a great feature for general computer newbies, it's not all that impressive in actual practice for me personally, because my personal assumptions are that of a power user comfortable at the command line and with scripting. Basically, all activities are, from a computer power-user perspective, is an automated method to batch a bunch of apps with their content together, launching and shutting them down as a unit, potentially at the same time changing configuration options that affect that activity -- disabling screensavers and automatic display sleep cycles when activating a movie activity, for instance, then activating them again when switching to some other activity. For a relative computer novice, or one more accustomed to taking an adversarial position regarding their computer because they can never seem to get it to work the way they want, as opposed to a computer power user who appreciates the way computers work, and uses that to their advantage, to the point they don't even realize half the stuff they're doing any more as it's so intuitive to them now... to that non-power-user, activities have the potential to open up a whole new world of automation for them, one they never appreciated as existing, before. But, for the already computer power user, the story is far different. To them, if they want a bunch of things to startup together, including a few config changes, the intuitive answer is to write a script. This script starts the apps and loads the appropriate data; if the intent is to watch a movie, it runs xset and etc to turn the display sleep timeout off if; if necessary, apps are started with a different title or profile or whatever, using command line options, so the appropriate kwin window rules will apply and place and size the window appropriately for that activity, including the appropriate virtual desktop, always-on-top, etc, settings; the script will either launch everything and quit, or wait around to reset things when the user's done and shuts down the key app; if necessary, the script will sleep a few seconds and then launch wmctrl to reposition the windows; etc. FWIW, it can be noted that /exactly/ this sort of thing is what I do, routinely. When kde4 killed khotkey multi-key support, I grumbled quite a bit, then had the insight that I could accomplish the same thing by having an initial key launch a customized menu app, that took the second key and issued the appropriate command; a few hours later, I had exactly that sort of solution scripted and running. As part of that solution, I start a konsole session with a special profile, so kwin can detect that it's not a normal konsole window, and treat it differently using window rules. I routinely setup window rules as needed to get windows to go where I want and behave as I want. At one point, the window name was changing after launch and I couldn't get window rules to put it where I wanted without using force, which then wouldn't let me move it if desired, so I searched for, installed, and setup a wrapper script that handled it all for me. I have scripts that launch a whole series of commands in a particular order, waiting when necessary, etc. All this is now second nature to me, just part of using the computer. So activities don't actually do much for me that I couldn't do already, only with more control, because I setup the script/config/whatever to do exactly what I wanted, when I wanted
Re: [kde] Home Directory KDE config files [SOLVED]
On 10/26/2011 07:11 PM, Duncan wrote: Bogus Zaba posted on Wed, 26 Oct 2011 13:02:56 +0100 as excerpted: On 10/26/2011 11:38 AM, Bogus Zaba wrote: Slackware 13.37, KDE4.5.5. Is there another location (other than the .kde folder) where kde config files are kept? My standard way of recovering from kde won't start has failed me since this is based on restoring a previously good .kde folder in place of the existing one that is causing problems. Now I have a failure of startup of KDE (but other users and other window managers for the same user start up fine). Symptoms are: Spalsh screen shows, but no progress with the icons which should slowly appear. Dumped back to console where I see: startkde: Starting up... Connecting to deprecated signal QBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kded(3521): Communication problem with kded , it probably crashed. Error message was org.freedesktop.DBus.Error.ServiceUnknown : The name org.kde.kded was not provided by any .service files This all started when KDE crashed when I foolishly tried to add a Launcelot application launcher widget to my desktop. I already had a Quicklauncher widget, but on trying to configure the new widget, screen went black and I had to ctrl-alt-BS to close X and get back to a console. Thanks Possible further clue as top what has gone wrong: When I try to run a KDE app (dolphin, knoqueror etc) from within xfce, I get : Code: QGtkStyle was unable to detect the current GTK+ theme Bus error I think it is the Bus Error that is significant because if I do the same thing for as another user who has not got the broken kde, you still see the QGtkStyle error (and a whole lot more messages too) but then the dolphin window opens OK. You got the hang of kde's errors and how to debug them -- STDOUT/STDERR is so noisy the only effective way to get any reasonable debugging info out of it is to diff it against the output from a working setup. (I guess they don't expect actual users to run the app with STDERR/STDOUT open, only devs, for whom the info is probably useful.) FWIW, bus error would refer to dbus... Try the XDG_CONFIG_HOME and XDG_DATA_HOME dirs. If these vars aren't exported, the defaults are (IIRC) generally ~/.config and ~/.local . These are the standard freedesktop.org vars/locations (X Desktop Guide, maybe?), and as such, will likely get more use over time, as current apps are redone to comply with this fairly new standard. (I expect for kde, many things will stay where they are for kde4, but may well move for kde5.) For now, most kde stuff uses KDEHOME (with a default to ~/.kde upstream tho some distros make that ~/.kde4), so that's still the first/best assumption, but there's enough stuff starting to use the new locations that they're the #2 place to look, if KDEHOME doesn't do it. If it is dbus related, that's a freedesktop.org tech, so it'd make sense that the XDG_* locations would be used. Do note that especially the data dir often contains user data, mail, etc, as well, so don't just go blowing it away. Move it out of the way for testing, and selectively move stuff back (bisecting the problem) if that dir is found to be the problem. Again, this is very likely to become even more the case over time... Found the answer by doing what I should have done before contacting the list, I guess : Googling for the exact error message regarding kded having crashed. When I did that I pretty quickly found this on an Arch forum: https://bbs.archlinux.org/viewtopic.php?id=107086 The trick is to delete the directory : /var/tmp/kdecache-username I had never heard of this cache previously, but it looks as if at start up KDE looks here and if something is corrupt, it will fall over, regardless of what changes you make to the config files in the home directory. It had to be user-specific, but I was wrong to think that the problem therefore had to be located in the user directory. Thanks for the help here too - always informative. ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
[kde] Home Directory KDE config files
Slackware 13.37, KDE4.5.5. Is there another location (other than the .kde folder) where kde config files are kept? My standard way of recovering from kde won't start has failed me since this is based on restoring a previously good .kde folder in place of the existing one that is causing problems. Now I have a failure of startup of KDE (but other users and other window managers for the same user start up fine). Symptoms are: Spalsh screen shows, but no progress with the icons which should slowly appear. Dumped back to console where I see: startkde: Starting up... Connecting to deprecated signal QBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kded(3521): Communication problem with kded , it probably crashed. Error message was org.freedesktop.DBus.Error.ServiceUnknown : The name org.kde.kded was not provided by any .service files This all started when KDE crashed when I foolishly tried to add a Launcelot application launcher widget to my desktop. I already had a Quicklauncher widget, but on trying to configure the new widget, screen went black and I had to ctrl-alt-BS to close X and get back to a console. Thanks ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] Home Directory KDE config files
No, I see only the .kde folder - I guess this might be distro-specific. I did find one other file - .kderc which I renamed but I am still getting the same problem. On 10/26/2011 12:22 PM, GSC wrote: Is there .kde4 folder? 2011/10/26 Bogus Zaba bog...@bogzab.plus.com mailto:bog...@bogzab.plus.com Slackware 13.37, KDE4.5.5. Is there another location (other than the .kde folder) where kde config files are kept? My standard way of recovering from kde won't start has failed me since this is based on restoring a previously good .kde folder in place of the existing one that is causing problems. Now I have a failure of startup of KDE (but other users and other window managers for the same user start up fine). Symptoms are: Spalsh screen shows, but no progress with the icons which should slowly appear. Dumped back to console where I see: startkde: Starting up... Connecting to deprecated signal QBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kded(3521): Communication problem with kded , it probably crashed. Error message was org.freedesktop.DBus.Error.ServiceUnknown : The name org.kde.kded was not provided by any .service files This all started when KDE crashed when I foolishly tried to add a Launcelot application launcher widget to my desktop. I already had a Quicklauncher widget, but on trying to configure the new widget, screen went black and I had to ctrl-alt-BS to close X and get back to a console. Thanks ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html. ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html. ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] Home Directory KDE config files
On 10/26/2011 11:38 AM, Bogus Zaba wrote: Slackware 13.37, KDE4.5.5. Is there another location (other than the .kde folder) where kde config files are kept? My standard way of recovering from kde won't start has failed me since this is based on restoring a previously good .kde folder in place of the existing one that is causing problems. Now I have a failure of startup of KDE (but other users and other window managers for the same user start up fine). Symptoms are: Spalsh screen shows, but no progress with the icons which should slowly appear. Dumped back to console where I see: startkde: Starting up... Connecting to deprecated signal QBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kded(3521): Communication problem with kded , it probably crashed. Error message was org.freedesktop.DBus.Error.ServiceUnknown : The name org.kde.kded was not provided by any .service files This all started when KDE crashed when I foolishly tried to add a Launcelot application launcher widget to my desktop. I already had a Quicklauncher widget, but on trying to configure the new widget, screen went black and I had to ctrl-alt-BS to close X and get back to a console. Thanks Possible further clue as top what has gone wrong: When I try to run a KDE app (dolphin, knoqueror etc) from within xfce, I get : Code: QGtkStyle was unable to detect the current GTK+ theme Bus error I think it is the Bus Error that is significant because if I do the same thing for as another user who has not got the broken kde, you still see the QGtkStyle error (and a whole lot more messages too) but then the dolphin window opens OK. ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
Re: [kde] Home Directory KDE config files
On 10/26/2011 07:11 PM, Duncan wrote: Bogus Zaba posted on Wed, 26 Oct 2011 13:02:56 +0100 as excerpted: On 10/26/2011 11:38 AM, Bogus Zaba wrote: Slackware 13.37, KDE4.5.5. Is there another location (other than the .kde folder) where kde config files are kept? My standard way of recovering from kde won't start has failed me since this is based on restoring a previously good .kde folder in place of the existing one that is causing problems. Now I have a failure of startup of KDE (but other users and other window managers for the same user start up fine). Symptoms are: Spalsh screen shows, but no progress with the icons which should slowly appear. Dumped back to console where I see: startkde: Starting up... Connecting to deprecated signal QBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kded(3521): Communication problem with kded , it probably crashed. Error message was org.freedesktop.DBus.Error.ServiceUnknown : The name org.kde.kded was not provided by any .service files This all started when KDE crashed when I foolishly tried to add a Launcelot application launcher widget to my desktop. I already had a Quicklauncher widget, but on trying to configure the new widget, screen went black and I had to ctrl-alt-BS to close X and get back to a console. Thanks Possible further clue as top what has gone wrong: When I try to run a KDE app (dolphin, knoqueror etc) from within xfce, I get : Code: QGtkStyle was unable to detect the current GTK+ theme Bus error I think it is the Bus Error that is significant because if I do the same thing for as another user who has not got the broken kde, you still see the QGtkStyle error (and a whole lot more messages too) but then the dolphin window opens OK. You got the hang of kde's errors and how to debug them -- STDOUT/STDERR is so noisy the only effective way to get any reasonable debugging info out of it is to diff it against the output from a working setup. (I guess they don't expect actual users to run the app with STDERR/STDOUT open, only devs, for whom the info is probably useful.) FWIW, bus error would refer to dbus... Try the XDG_CONFIG_HOME and XDG_DATA_HOME dirs. If these vars aren't exported, the defaults are (IIRC) generally ~/.config and ~/.local . These are the standard freedesktop.org vars/locations (X Desktop Guide, maybe?), and as such, will likely get more use over time, as current apps are redone to comply with this fairly new standard. (I expect for kde, many things will stay where they are for kde4, but may well move for kde5.) For now, most kde stuff uses KDEHOME (with a default to ~/.kde upstream tho some distros make that ~/.kde4), so that's still the first/best assumption, but there's enough stuff starting to use the new locations that they're the #2 place to look, if KDEHOME doesn't do it. If it is dbus related, that's a freedesktop.org tech, so it'd make sense that the XDG_* locations would be used. Do note that especially the data dir often contains user data, mail, etc, as well, so don't just go blowing it away. Move it out of the way for testing, and selectively move stuff back (bisecting the problem) if that dir is found to be the problem. Again, this is very likely to become even more the case over time... Duncan Thanks for this. I think it may well be connected with XDG_CONFIG_HOME etc variables, but can you tell me where these are normally set up? Thanks ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
[kde] Re: KDM not starting after upgrade
On 05/21/2011 02:14 PM, Duncan wrote: It looks like so. You'd have only encountered problems when you tried the kwin --replace and/or plasma-desktop steps, since they use opengl, and likely only kwin, as plasma-desktop uses opengl, but not to the same degree. (FWIW, the comic-strip-plasmoid, of /all/ things, appears to use opengl accelerated drawing functionality that triggered an agp-only radeon drm kernel regression bug I had at one point. The rest of my plasma config worked fine, as long as I didn't have a comic strip configured!) Thanks for the update! Knowing how it was ultimately resolved... is both potentially helpful if others have the problem, and fills my own curiosity. I did try and run plasma and kwin from xfce thing and plasma worked, but kwin caused a lock-up. As I was running from the command line I saw the messages from kwin and basically there were just four lines which more or less said : 1. The GL vendor is NVIDIA Corporation 2. The GL renderer is my graphics card identifier 3. The GL version is 2.1.2 NVIDIA 270.41.06 4. The driver is nvidia version 270.41.06 After that : total lock-up. At that point I realised that in running nvidia driver version 270..., I had leap-frogged Slackware's (unofficially) packaged nvidia driver which was 260 I uninstalled the 270 version, installed the Slackware package and found that everything worked just fine from the outset, apart from the need to put back some desktop backgrounds and a quicklaunch widget. The moral is : don't try and be smarter than the guys building your distro. Thanks again for you interest Duncan. ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
[kde] KDM not starting after upgrade
I have upgraded my Slackware Installation from 13.1 to 13.37. This means that my KDE has gone from 4.4.3 to 4.5.5. The same process worked fine on two other PCs, but on this (my main Desktop machine) I cannot get KDE up and running for a regular user. KDE starts OK for root, but for myself and for a newly created user, I see the splash screen and then four of the five splash icons come into focus. The last one never gets there and disk activity eventually ceases (I have left it for more than 30 mins). I have tried renaming the .kde folder and the .kderc file, but this has not helped. I can only stop the failed KDE session with ctrl-alt-BS which returns me to the terminal from which I tried to launch KDE with the startx command. On that terminal I see various error messages from akonadi. If this is the cause of the trouble, what is the solution ? I notice that when KDE does launch successfully (for root) there is a progress bar displayed also connected with the akonadi server starting up - presumably successfully in that case. Any thoughts appreciated. Thanks ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
