Re: webcam color profile calibration? - anyone?
Am Donnerstag, 16. Januar 2014, 02:04:59 schrieb chymian: > hey everybody, > > using my webcam with skype gives a too gray-in-gray picture. > > what is the recommended way, to calibrate the webcam-colors or tinker > colord-profiles, that a more realistic picture is possible. > > HW: laptop clevo 150er > webcam: > > usb 4-1.6: New USB device found, idVendor=5986, idProduct=0308 > usb 4-1.6: Product: BisonCam, NB Pro > usb 4-1.6: Manufacturer: BisonCam, NB Pro > uvcvideo: Found UVC 1.00 device BisonCam, NB Pro (5986:0308) > > debian: jessie > colord: 1.0.5-1 > icc-profiles 2.0.1-1 > icc-profiles-free 2.0.1+dfsg-1 > libicc2 2.12+argyll1.5.1-5+b1 > > TIA > guenter > > > -- 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/1889189.kiYTgYbics@hansa
webcam color profile calibration?
hey everybody, using my webcam with skype gives a too gray-in-gray picture. what is the recommended way, to calibrate the webcam-colors or tinker colord-profiles, that a more realistic picture is possible. HW: laptop clevo 150er webcam: usb 4-1.6: New USB device found, idVendor=5986, idProduct=0308 usb 4-1.6: Product: BisonCam, NB Pro usb 4-1.6: Manufacturer: BisonCam, NB Pro uvcvideo: Found UVC 1.00 device BisonCam, NB Pro (5986:0308) debian: jessie colord: 1.0.5-1 icc-profiles2.0.1-1 icc-profiles-free 2.0.1+dfsg-1 libicc2 2.12+argyll1.5.1-5+b1 TIA guenter -- 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/26756873.UfAQP6iaYL@hansa
Re: KDEPIM & Cal-/Card-DAV
Am 26.11.2012 16:48, schrieb john Culleton: > On Mon, 26 Nov 2012 23:39:16 +0800 > David Smith wrote: > >> On Mon, Nov 26, 2012 at 11:31 PM, Benjamin Eikel >> wrote: >>> Am Montag, 26. November 2012, 16:11:21 schrieb Kevin Krammer: >>>> On Monday, 2012-11-26, David Smith wrote: >>>>> On Sun, Nov 18, 2012 at 11:00 PM, chymian >>>>> wrote: >>>>>> at the moment I'm tied to icedove/thunderbird which is another >>>>>> sad story. >>>>>> >>>>>> tia >>>>>> günter >>>>> Yes, I agree the state of KMAIL in Wheezy is really bad.. It's >>>>> *VERY* easy to make it crash 10-15 times an hour with normal >>>>> operation of the program. I've also resorted to just removing >>>>> it and running ice dove which is easily 1000x better in features >>>>> and never crashes. >>>> Is this a different version than the one in Unstable? >>>> Because the one in Unstable does not show that kind of behavior. >>>> >>>> Here it is one the few applications that run at all times (I start >>>> it one of the first things when logging in and never quit it until >>>> I log out) and this laptop often sees uptimes of 60 days and more. >>>> >>>> I do run it as a component within Kontact, but I would be >>>> surprised if this is the important difference. >>> Same for me. KMail runs rock stable here, too (unstable, libkdepim4 >>> 4:4.4.11.1+l10n-3+b1, running inside Kontact). >>> But some of the features of newer KDEPIM (e.g. GroupDAV support) >>> would indeed be very nice. As far as I know the Debian KDE team >>> lacks manpower and therefore newer packages will takes some time. >> >> Looks to be the same version... >> >> I'm in mainland China which has artificial connectivity problems with >> google's mail servers. That *might* be the cause of my constant KMAIL >> crashes, but I never bothered to investigate further. Even when I'm >> not doing anything with KMAIL, and just have it running it in the >> background doing nothing, it will just crash all by itself and I have >> to regularly restart it. Again, that might just be because I have a >> lot of connectivity problems to the mail server that KMAIl is trying >> to use. I've tried doing everything in the book (deleting all of the >> user's config files, using a different user account on the PC, etc..) >> with no success.. I'm sure if I stop using google's mail servers from >> China, the problem will probably go away, but gmail's spam filter is >> the best I've ever seen so I keep using it anyway and just gave KMAIL >> the boot. >> >> The only reason I end up using IceDove or KMAIL is because gmail.com >> won't even load most of the time... At least with IceDove, I can write >> something up and queue it to send when it can.. KMAIL does that and >> then just crashes some time later, sometimes even losing my e-mail >> that I wrote without sending it :(. >> >> > I switched to claws-mail and never looked back. > > to go back to the main topic: does claws has card-/cal-dav support? does it integrate into KDE? i.e. can you sent file from dolphin per claws, etc. -- 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/50b39cd4.8070...@gmx.net
Re: KDEPIM & Cal-/Card-DAV
anyone? Am 18.11.2012 16:00, schrieb chymian: > hi, > is there any chance to connect kdepim/akonadi successful to either sogo, > or even better owncloud? > > all tries I made with kdepim 4.4.11 & kdepim-runtime 4.8/experimental > failed so far from my wheezy installation. > > how long to go, till we can test kdepim2 (>= 4.8.x.) > > at the moment I'm tied to icedove/thunderbird which is another sad story. > > tia > günter > > > > -- 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/50ab8980.9020...@gmx.net
KDEPIM & Cal-/Card-DAV
hi, is there any chance to connect kdepim/akonadi successful to either sogo, or even better owncloud? all tries I made with kdepim 4.4.11 & kdepim-runtime 4.8/experimental failed so far from my wheezy installation. how long to go, till we can test kdepim2 (>= 4.8.x.) at the moment I'm tied to icedove/thunderbird which is another sad story. tia günter -- 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/50a8f815.2060...@gmx.net
Re: [debian-kde] Re: plasma desktop hangs - BUG 303105 & 303106
Am 06.07.2012 10:02, schrieb David Jarvie: On Monday 02 July 2012 16:20:27 chymian wrote: I followed your advice and opened up a new thread: http://forum.kde.org/viewtopic.php?f=67&t=106640 Just a word of warning - many KDE developers do not read forums. Unless you know that the forum you posted to is read by developers, you should raise issues either on the appropriate KDE mailing list (see http://lists.kde.org) or if it's a bug, at https://bugs.kde.org. done, I've opend the two bugs: Bug 303105 <https://bugs.kde.org/show_bug.cgi?id=303105> - widget-SOHO: hangs plasma on lost network-connection against plasma. since there was no widget-soho component-entry, I opend it against general - correct? Bug 303106 <https://bugs.kde.org/show_bug.cgi?id=303106> - PLASMA corrupted ~/.kde/share/configplasma-desktop-appletsrc - System hangs against plasma-desktop. have a nice one günter
Re: plasma desktop hangs
hi miro, thx for answering. Am Mo, 2. Juli 2012, 00:44:40 schrieb Mirosław Zalewski: > On 01/07/2012 at 16:48, chymian wrote: > > BUT: the point here: > > >> plasma should definitly NOT freeze on a lost network connection. > > > > or even, if a plasmoid can't update it's content! > > This is probably caused by plasma design - i.e. all plasmoids run under > single process. So, if one plasmoid tries to connect, it virtually hangs > whole desktop for that time. > > This issue was discussed some time ago on planet KDE, but I can't find that > post right now. > > I have found that brainstorm discussion from few years back: > http://forum.kde.org/viewtopic.php?f=90&t=45255 > It seems that rationale was: plasmoid crash causes whole desktop to crash, > so we should run them in separate processes. But plasmoids don't crash > that often now, so we do not have to run them in separate processes. > > Your case shows that there is still pretty strong reason to run plasmoids > in separate processes (if only my suppositions are right). You should > definitely post your findings in KDE forums - either in linked thread, or > in new thread (which may get more attention). at the end of the long, dark valley, there is a house - made of paper - and it's starting to rain. > > But you should not post a bug report to Debian's BTS - there is really not > much that Debian's KDE packaging team can do about it. That's what I thought and why I'm asking. > > As for corrupted configplasma-desktop-appletsrc file - it would be nice if > you could provide step-by-step instructions how to reproduce that. I will > check on Arch Linux with KDE to ensure that this is Debian issue. As KDE > packaging team recently said on that mailing list, they prefer that KDE > bugs goes directly to KDE, not Debian BTS. Debian BTS is appropriate for > packaging issues and things that do not happen outside Debian. I followed your advice and opened up a new thread: http://forum.kde.org/viewtopic.php?f=67&t=106640 as you can read there as well, I don't now how to reproduce, other then doing the normal updates, which did scramble the desktop a couple of times in the last half year. there had been other people on the list, reporting that. (don't find the mails at the moment) for me, I start over with a empty .kde in the next days - again :( :( :( and will monitor more closely on the config files. if i find a misbehavior again, smashed config-files, etc. I will report. have a nice day. günter -- 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/201207021720.28077.chym...@gmx.net
BUG: plasma desktop hangs on corrupted configplasma-desktop-appletsrc
further update & workaround: 2 BUGs found. Am So, 1. Juli 2012, 16:48:13 schrieb chymian: > Hi again, > > Am So, 1. Juli 2012, 15:39:43 schrieb Kevin Krammer: > > On Sunday, 2012-07-01, chymian wrote: > > > hi everybody, > > it seems to be, as kevin wrote: > > Maybe it is a certain applet that triggers this behavior, e.g. something > > that gets data from a web service? > > I found the following appear every 5 min in my .xsession-errors > Failed to get chart. Updating... > Failed to get chart. Updating... > Failed to get chart. Updating... > Failed to get chart. Updating... > Failed to get chart. Updating... > Failed to get chart. Updating... > Failed to get chart. Updating... > Failed to get chart. Updating... > Failed to get chart. Updating... > Failed to get chart. Updating... > Failed to get chart. Updating... > Failed to get chart. Updating... > > which could come from my SOHO-plasmoids. > and is EXACT the time, when the desktop freezes for 3 minutes. > > BUT: the point here: > >> plasma should definitly NOT freeze on a lost network connection. > > or even, if a plasmoid can't update it's content! > > > I've never had any problem with dropping network connections, neither > > WLAN nor mobile broadband (where this happens a lot more often, e.g. > > when on a train). > > so, what's the difference? > mine freezes every 5 min because of a couple of plasmoids cannot update > it's self, even when I have a network-connection. aka. on a > web-server-pbl. they connect to? indeed, the soho-plasmoids could not connect to it's server. but even more strange: I removed all but one weather-plasmoid, which works flawlessly - and I still get the same error & behavior as before. errorlogs & desktop-freeze, but only 6 times in a row now. I checked the ~/.kde/share/configplasma-desktop-appletsrc and again, it was corrupted, which happend quite a few times in the last months. after I removed the aktiv soho-plasmoids, I found 6 leftovers in the config file. removing these in between KDE newstarts resolved the problem. corrupted config attached. do the KDE-maintainers want me to open 2 bugs on that, or do you take it from here? 1. plasma-desktop should not freeze on failed plasmoid aka: Failed to get chart. Updating... freezes plasma-desktop 2. ~/.kde/share/configplasma-desktop-appletsrc gets corrupted plasma-desktop 4:4.8.4-2 günter [ActionPlugins] LeftButton;NoModifier=applauncher MidButton;NoModifier=paste RightButton;NoModifier=contextmenu wheel:Vertical;NoModifier=switchdesktop [AppletGlobals][plasma_applet_pager] rows=2 [Containments][1] activity= activityId= desktop=-1 formfactor=2 geometry=0,-41,1600,35 immutability=1 lastDesktop=-1 lastScreen=0 location=4 plugin=panel screen=0 zvalue=0 [Containments][1][ActionPlugins] RightButton;NoModifier=contextmenu [Containments][1][Applets][15] geometry=0,3,32,32 immutability=2 plugin=simplelauncher zvalue=2 [Containments][1][Applets][15][LayoutInformation] Order=0 [Containments][1][Applets][15][Shortcuts] global= [Containments][1][Applets][3] geometry=144,3,32,32 immutability=2 plugin=org.kde.showActivityManager zvalue=0 [Containments][1][Applets][3][LayoutInformation] Order=4 [Containments][1][Applets][31] geometry=36,3,32,32 immutability=2 plugin=icon zvalue=1 [Containments][1][Applets][31][Configuration] Url=file:///usr/share/applications/iceweasel.desktop [Containments][1][Applets][31][LayoutInformation] Order=1 [Containments][1][Applets][32] geometry=108,3,32,32 immutability=2 plugin=icon zvalue=4 [Containments][1][Applets][32][Configuration] Url=file:///usr/share/applications/kde4/dolphin.desktop [Containments][1][Applets][32][LayoutInformation] Order=3 [Containments][1][Applets][4] geometry=180,3,231,32 immutability=2 plugin=pager zvalue=0 [Containments][1][Applets][4][Configuration] Share=false currentDesktopSelected=0 displayedText=2 showWindowIcons=false [Containments][1][Applets][4][LayoutInformation] Order=5 [Containments][1][Applets][5] geometry=415,3,831,32 immutability=1 plugin=tasks zvalue=1 [Containments][1][Applets][5][Configuration] Share=false forceRows=false groupWhenFull=true groupingStrategy=2 highlightWindows=false maxRows=2 showOnlyCurrentActivity=true showOnlyCurrentDesktop=false showOnlyCurrentScreen=false showOnlyMinimized=false showTooltip=true sortingStrategy=2 [Containments][1][Applets][5][Configuration][Launchers] Items=file:///usr/share/applications/virt-manager.desktop?wmClass=Virt-manager,file:///usr/share/applications/iceweasel.desktop?wmClass=Iceweasel,file:///usr/share/applications/kde4/basket.desktop?wmClass=Basket,file:///usr/share/applications/kde4/konsole.desktop?wmClass=Konsole [Containments][1][Applets][5][LayoutInformation] Order=6 [Containments][1][Applets][6] geometry=1250,3,258
Re: plasma desktop hangs
Hi again, Am So, 1. Juli 2012, 15:39:43 schrieb Kevin Krammer: > On Sunday, 2012-07-01, chymian wrote: > > hi everybody, > > it seems to be, as kevin wrote: > Maybe it is a certain applet that triggers this behavior, e.g. something > that gets data from a web service? I found the following appear every 5 min in my .xsession-errors Failed to get chart. Updating... Failed to get chart. Updating... Failed to get chart. Updating... Failed to get chart. Updating... Failed to get chart. Updating... Failed to get chart. Updating... Failed to get chart. Updating... Failed to get chart. Updating... Failed to get chart. Updating... Failed to get chart. Updating... Failed to get chart. Updating... Failed to get chart. Updating... which could come from my SOHO-plasmoids. and is EXACT the time, when the desktop freezes for 3 minutes. BUT: the point here: >> plasma should definitly NOT freeze on a lost network connection. or even, if a plasmoid can't update it's content! > I've never had any problem with dropping network connections, neither WLAN > nor mobile broadband (where this happens a lot more often, e.g. when on a > train). so, what's the difference? mine freezes every 5 min because of a couple of plasmoids cannot update it's self, even when I have a network-connection. aka. on a web-server-pbl. they connect to? > > Cheers, > Kevin cheers günter
plasma desktop hangs
hi everybody, since a while now (at least a year), KDE does have the following behavior: while the WLAN-connection is stable, every thing is good. moving my laptop (i.e. to the terrasse) where it often still has a 50% signal, the pbls. begin: while it rechecks/reconnect to the wlan, plasma hangs (menues, systray, etc all frozen, kwin still is responsable, can move windows) for a minute or 2! that happens on movment and also, while I don't move the box - just out of the sky on rechecking the connection. first, I used Network-Manager + plasmoid, which often was not able to reconnect. I had to manual stop the manager, sometimes reload the module & restart the manager, then wait till KDE realises, that there is network again. after it had lost the connection once, it's keeping me asking over and over for the WLAN-secret, which was already in kwallet and too often, the only way out was to complety remove the connection and configure it new. then I moved to WICD, (for the price of loosing my comfortable VPN's setup). WICD is MUCH more stable, never asks for the password but still hangs plasma now and then. but seems to be 80% more stable. since I swapped hardware 4 weeks ago, it dosen't look like a driver/module-pbl. to me. (b43 before, iwlwifi now). I also see this on some laptops of friends, all KDE 4.4 - 4.8, wheezy. and I checked it with three different WLAN-routers - all same behavior. so, even if it's a driver-/network-pbl. the basic line here: plasma should definitly NOT freeze on a lost network connection. running on KDE-SC 4.8.4, wheezy, wicd 1.7.2.4-2, wicd-kde 0.3.0-2 kernel 3.0 ... .3.5-rc2 (all show the same behavior) all I see in the syslog is: wlan dropped connection and is trying to reconnect for a while. any hint's, how to prevent KDE from freezing? anybody sees the same behavior? and who get's the bug-report? kde for freezing?, kernel for dropping, one (or both) of the network-managers? since I didn't got an answeer on debian-user for a week, I cross post it to the kde-list. sorry for that, but I think I should have done this in the first place. update: since plasma hangs on the described network-problem quit often, it also hangs sometimes after switching activities for a minute or so. any hint, how to hunt it down? cheers, günter log starts, with unpluging my ext. HDD before I move the laptop: Jun 26 14:28:41 merkaba acpid: input device has been disconnected, fd 12 Jun 26 14:28:45 merkaba kernel: [ 3982.161109] ata5: hard resetting link Jun 26 14:28:46 merkaba kernel: [ 3982.465661] ata5: SATA link down (SStatus 0 SControl 310) Jun 26 14:28:46 merkaba kernel: [ 3982.465672] ata5.00: disabled Jun 26 14:28:46 merkaba kernel: [ 3982.476617] ata5: EH complete Jun 26 14:28:46 merkaba kernel: [ 3982.476635] ata5.00: detaching (SCSI 4:0:0:0) Jun 26 14:28:46 merkaba kernel: [ 3982.477260] sd 4:0:0:0: [sdc] Synchronizing SCSI cache Jun 26 14:28:46 merkaba kernel: [ 3982.477336] sd 4:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK Jun 26 14:28:46 merkaba kernel: [ 3982.477347] sd 4:0:0:0: [sdc] Stopping disk Jun 26 14:28:46 merkaba kernel: [ 3982.477367] sd 4:0:0:0: [sdc] START_STOP FAILED Jun 26 14:28:46 merkaba kernel: [ 3982.477372] sd 4:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK Jun 26 14:29:44 merkaba anacron[20062]: Anacron 2.3 started on 2012-06-26 Jun 26 14:29:44 merkaba anacron[20062]: Normal exit (0 jobs run) Jun 26 14:30:07 merkaba init: Switching to runlevel: 5 Jun 26 14:30:07 merkaba acpid: client connected from 20382[0:0] Jun 26 14:30:07 merkaba acpid: 1 client rule loaded Jun 26 14:30:07 merkaba kdm_greet[20406]: Cannot set locale. Translations will not work. Jun 26 14:30:07 merkaba kdm_greet[20406]: Cannot load /usr/share/kde4/apps/kdm/faces/.default.face: No such file or directory Jun 26 14:33:05 merkaba kdm: :0[20520]: pam_ecryptfs: Passphrase file wrapped Jun 26 14:35:33 merkaba amd[3608]: No fs type specified (key = "/defaults", map = ""root"") Jun 26 14:35:33 merkaba amd[3608]: Unknown host: .Trash Jun 26 14:35:33 merkaba amd[3608]: No fs type specified (key = "/defaults", map = ""root"") Jun 26 14:35:33 merkaba amd[3608]: Unknown host: .Trash-1000 Jun 26 14:35:48 merkaba pulseaudio[21647]: [pulseaudio] pid.c: Daemon already running. Jun 26 14:35:48 merkaba pulseaudio[21654]: [pulseaudio] pid.c: Daemon already running. Jun 26 14:36:48 merkaba kernel: [ 4464.281193] cfg80211: Calling CRDA to update world regulatory domain Jun 26 14:36:51 merkaba dhclient: Internet Systems Consortium DHCP Client 4.2.2 Jun 26 14:36:51 merkaba dhclient: Copyright 2004-2011 Internet Systems Consortium. Jun 26 14:36:51 merkaba dhclient: All rights reserved. Jun 26 14:36:51 merkaba dhclient: For info, please visit https://www.isc.org/software/dhcp/ Jun 26 14:36:51 merkaba dhclient: Jun 26 14:36:52 merkaba dhclient: Listening on LPF/wlan0/88:53:2e:b4:9a:60 Jun 26 14:36:52 merkaba dhclient: Sendin
Re: kdepim-runtime 4.8.4 in experimental, call for testing
hi leo, > > I have tested it with Sogo and I have had a mixture of good result and bad > result. > > As good result, kaddressbook works perfectly with the several contacts list > that i have in my sogo server. I can create, copy and delete contacts > without any problem. The only thing is that I'm not been able to see it > when I create a new mail. I just seen my original resources. Any idea? > > As bad result, although I can see my calendars in korganizer, as I have > several calendars, I have not been able to create an event in one specific > . It seems as I have to have a global configuration for all the resource. > However, I think that I would need more test. as you get different results connecting to sogo, then I did, which versions are you running? my setup: sogo 1.3.16-1, Zentyal 2.2, ubuntu 10.4 cheers guenter -- 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/201206271334.52794.chym...@gmx.net
Re: kdepim-runtime 4.8.4 in experimental, call for testing
hi, glad to hear, that there is a chance to finally get xxxDAV :) thx a lot. Am Sonntag, 24. Juni 2012, 21:32:29 schrieb Modestas Vainius: > Hello, > > > * Test if kmail, korganizer, ktimetracker, address book and the whole > kontact work as expected. > * Test if maybe any of your pet bugs have been fixed. > * Test if any other features like e.g. ownCloud (hi > Diederik! [1]) or various groupware support started to work magically. > * Test if external akonadi resources like e.g. googledata work as expected. starting with a new install in a VM: akonadi-backend-sqlite: does not install in ~/.config/.akonadi/akonadiserverrc. (still mysql there)! connected PIM to my sogo-server: initial configuration ok. shows callender & addressbooks in resources. connect to sogo via https ok. in KONTACT: its shows the calender & the entries. cannot create an entry, which get synced back. and yes, the read-only-flag is unchecked. addressbooK: does show both addressbooks (system & user). does not show ANY entries in either addr-book. - stays complete empty. so, no luck here > > We need this information in order to determine if kdepim-runtime 4.8.4 is > worth a risk at all. in my opinion, there are a lot of use-cases which cannot be handled by kdepim-runtime 4.4.x. and any effort, to get 4.8.x in is higly appreceated. thx a lot guenter -- 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/201206261411.20957.chym...@gmx.net
KDE 4.6 constantly smashing my configs & data - nearly unusable....
hi guys, after a lot of problems with the squeezy/weezy versions of KDE, I updated to 4.6.1 from exerimental in the hope that the varios bugs and problems I was facing would go away... unfortunatley ther are evem more - so much that I think of leaving KDE I runing deb-testing on a MacBook 3.1 (intel core2Duo, 4G RAM) laptop screen LVDS1, 1280x800 and ext. monitor via DVI1 1680x1050 (my prim. screen) kernel 2.6.38-2 (experiemental) 1. after every reboot/restart/login of KDE, the settings from LVDS1 are back to 1024x768 - I have to manualy do the settings again and again. even if they seem to be correctly default-saved in .kde/share/config/startupconfig: krandrrc_display_startupcommands="xrandr --output \"LVDS1\" --pos 0x0 --mode 1280x800 --refresh 59.9095 xrandr --output \"DVI1\" --pos 1280x0 --mode 1680x1050 --refresh 59.8833 xrandr --noprimary" also, after reboot/restart of kde: 2. my dashboards-layout is always scrambled and often loss of configuration some of them are not started anymore, 3. since the update to 4.6.1, the toolbar does not resize correct. once it was smaler (due to screenconfig error) it does not resize to full width of the screen. only 1280 instead of 1680 aka LVDS1 instead of DVI1-width 4. after a shutdown/init level without KDE, it happend every 2nd/3rd time that: kmail is loosing mails, (last recieved mails are empty...) kmail is loosing configuration constantly: like filtersettings, view-setup, etc. but they are still in the config files!!! 5. bluetooth-monolith is started, but does not find any adapter, after each reboot. after manualy restarting bluetoothd deamon while KDE is running, it finds the adapter again. 6. my apple bluetoothmouse buttens do not working anymore (sinc 4.6). I can move the mouse/arrow, but that's all. 7. kwallet and other apps constantly losing ther config/data files 8. knetwork does not start automated connect and/or looses config-files... 9. comming back from suspend (lid close) funktion keys ar often not working. have to restart dbus & pommed helps most of the times. 10. can not set konqueror to use webkit. khtml only. ...and a lot minor problems more, which I even can't remeber at the moment all in all, since I installed 4.6 ca. 5 days ago, I have to repair my system every day, doing constant backups (1h) of my .kde-dir. and reply nearly at every start a couple of config files - what a mess. since the update from weezy smashed KDE completley, I moved .kde out of the way and started over from scratch (-> website: no help for a testing-update like that) I'm glad to help, provide any data etc. if someone jumps on these varios bugs... cheers chymian -- 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/201104121700.20721.chym...@gmx.net
