Re: Options for kdepim using kde 4.7/unstable?
> > Current kde from unstable is a bad idea for a laptop imho, because for some > reason, plasma-desktop permanently pulls some % of cpu time, therefore > ruining battery life. > > regards > Dietz > -- > Dietz, I'm running KDE from unstable and I don't have that problem (I've had kwin/xorg using excessive CPU before but not plasma-desktop and not now). In fact, I'm currently getting about the lowest power usage I've ever had from my laptop with full KDE + compositing! Diggory
Re: Two questions: NVIDIA driver and Nepomuk priority.
Regarding the NVIDIA driver, I use it without many problems. I did have a problem with Oxygen at one point, but IIRC it was more to do with interaction with a specific type of widget within kdevelop. Try upgrading the NVIDIA driver to one from testing/sid/experimental (they've been released by NVIDIA, so usually they're fine). I don't remember which version, but one adds compatibility with the latest X-server ABI. On Wednesday, 4 January 2012, Iki Sham wrote: > Oh, never mind about Nepomuk. I've just looked at 'top' and virtuoso-t > already has a nice value of 19. So maybe it's just time for me to disable > it.
Re: Kubuntu Control center for debian
Do you mean the control centre of the Kubuntu extensions? Kubuntu uses the standard "system settings" application, but adds a few options to it, as far as I know. Cheers On 17 September 2011 17:52, Uwe Brauer wrote: > > Hello > > Is it possible to use the (non standard Mac OS like) Kde > Control center which is provided by Kubuntu use in debian? > Is this already ported? I have not found anything using > google. > > Thanks > > Uwe Brauer > > > -- > To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: http://lists.debian.org/87ty8bmaj5@mat.ucm.es > >
Re: kdebug defaults/build options
> > So, turning off everything in kdebugdialog didn't silence kwrite on the > comand > line? > No, it did. > > > Any more thoughts on how much debug output is reasonable? Obviously it > > makes some sense for errors and warnings to be reported, but a lot of the > > output is only "trace" type debug output which is often only useful to > > people debugging or optimising applications so IMO shouldn't be enabled > by > > default (although feel free to disagree if you have a use for such > > output). Of my current 16 line log file, 2600 lines are matched by > > 'egrep -i warn' and another 800 by 'egrep -i error'. > > Turn off everything. :) > That was the idea. You can see it didn't work.. maybe little KDE app bugs left the rest of those boring messages? > > > Where does that leave us? Put up with it as is? Rebuild without debugging > > output enabled? Just disable all entries in kdebugdialog by default (this > > solves my issues anyway)? Ask KDE devs what their intentions are (maybe > > there are some KDE devs on this list)? > > Debian should default to disabling all messages via kdebugdialog. > Sounds OK. But you're saying you can't actually use long KDE sessions? I restart my laptop once a week or so (although maybe 2/3 of that time it's suspended to RAM), running KDE with kontact, kdevelop and konqueror running most of the time. I don't have a problem any more (actually, it was only a few annoyances to start with), so maybe debian should simply disable everything in kdebugdialog by default as Bruce said? -Dig
Re: Can't find brazilian ABNT2 keyboard layout configuration in KDE4 - squeeze (SOLVED)
Glad to hear it worked. FYI, xorg.conf settings are now auto-detected or configured elsewhere, with the exception of video driver config. Keyboard configuration can be found in /etc/default/keyboard. - Diggory On 19 August 2011 18:03, Joao Roscoe wrote: > Your comment gave an idea: I took a look at another squeeze box I have > (I installed squeeze in this one myself). In this other machine, the > keyboard is working properly, ***and***: > > 1. Keyboard layouts is disabled in systemsettings; > 2. There's no xorg.conf at all. > > So I did a little more research and found a locale issue - my personal > profile was enforcing LANG=C, very old stuff. I removed that, and now, > with en_US.UTF-8, everything works (proper keymap both in X and in > console). > > Best regards, > João > > On Fri, Aug 19, 2011 at 5:31 AM, Diggory Hardy > wrote: > > By the way, keyboard layouts are configured by XKB in a desktop > independent > > manner, so this might be better addressed to an xserver list. > > > > On 18 August 2011 23:27, Joao Roscoe wrote: > >> > >> Looked at systemsettings, "General" tab, "Regional and Languages", > >> "Keyboard Layout" > >> > >> Am I missing something? > >> > >> Best regards, > >> João > >> > >> > >> -- > >> To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org > >> with a subject of "unsubscribe". Trouble? Contact > >> listmas...@lists.debian.org > >> Archive: > >> > http://lists.debian.org/cakaijp0f57denhtmbqw_p1iuexvjjschzungw+o9btqan5...@mail.gmail.com > >> > > > > > > > -- > To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: > http://lists.debian.org/CAKaijp2ycrefLRfJ0GQ6MGXTkPk8Ýjdweitwrzxz6-oas...@mail.gmail.com > >
Re: kdebug defaults/build options
> > [sorry for the late response] > > If the only symptom was the huge log file then it could be argued that: had > debug messages been disabled, there wouldn't have been a problem... :D That makes sense, but (a) I disabled everything in kdebugdialog and truncated .xsession-errors to 100kB a few days ago, and now it's 16MB so still some traffic (over half from kio_xxx). That size of log file isn't an issue (for me at least), though most of the entries appear pretty uninteresting (e.g. HTTP requests). (b) many debug options are active by default, so new users are going to keep coming across nuisance messages (either in terms of .xsession-errors size or output on command-line when running things like kwrite). Any more thoughts on how much debug output is reasonable? Obviously it makes some sense for errors and warnings to be reported, but a lot of the output is only "trace" type debug output which is often only useful to people debugging or optimising applications so IMO shouldn't be enabled by default (although feel free to disagree if you have a use for such output). Of my current 16 line log file, 2600 lines are matched by 'egrep -i warn' and another 800 by 'egrep -i error'. Where does that leave us? Put up with it as is? Rebuild without debugging output enabled? Just disable all entries in kdebugdialog by default (this solves my issues anyway)? Ask KDE devs what their intentions are (maybe there are some KDE devs on this list)? Cheers, Diggory
Re: kdebug defaults/build options
Nice to see someone agrees with me but I was kinda expecting some sort of response from one of the package maintainers. Is it best to file a bug or just wait till this catches someone else's attention? Cheers, Diggory
kdebug defaults/build options
Hi all Regarding default debug output in kde on debian: 1. A while ago I reported this: https://bugs.kde.org/show_bug.cgi?id=269882 Perhaps disabling logging kget's debug messages makes sense? Or perhaps this is occasionally useful less often a problem? I don't have a strong opinion on this really. 2. At times I've been annoyed by the number of *spam* messages kwrite/kate leave on the console when run that way. Looking into it, these messages are kDebug outputs. The kde techbase suggests [1] this output is intended to be disabled in releases. Would you have any objections to doing this in the future, with kwrite at least? There's not many programs I've had problems with, but I do wince when running kwrite from a console every so often. [1]: http://techbase.kde.org/Development/FAQs/Debugging_FAQ#Is_there_a_preferred_way_to_print_debug_output_on_stderr.3F Cheers, Diggory
