Version: (using KDE 4.2.2) Installed from: Ubuntu Packages On 64-bit Kubuntu installations the Kaddressbook and Journal applications have no visible main window. 32 bit installations do not suffer from this issue. This bug was originally reported on the Ubuntu bugtracker and forwarded here at the devs' request: https://bugs.launchpad.net/ubuntu/+bug/364591
Created attachment 32991 [details] Screenshot illustrating problem
*** Bug 192648 has been marked as a duplicate of this bug. ***
AFAIK (in Bug 192648) - this has nothing to do with 32/64bit. Dotan, you reported my bug as duplicate of yours - either we have two separate bugs, or the bug description here is wrong: I have a 32bit system, and suffered from this bug. The error is in the rc file, as i stated. Please check this.
Yes, the description is wrong. I meant Korganizer, not Kaddressbook. The title reflects the correct application, as does the screenshot. I only noticed this issue on 64-bit Kubuntu installs, and not on 32-bit Kubuntu installs. But if you can confirm it on a 32-bit install then that is good to know. If you feel that inability to reproduce on 32-bit makes it a separate bug, then go ahead and reopen Bug 192648.
Hello, I have read bug report 192648 and therefore I removed ~/.kde/share/config/korganizerrc. (created by 4.2.2) Now calendar views (day/week) work for me (Jaunty/64bit). However I have meanwhile installed KDE 4.2.3 from deb http://ppa.launchpad.net/kubuntu-ppa/ppa/ubuntu jaunty main I attach a diff of the file.
Created attachment 33793 [details] Diff bad file <-> good file
I think I found the problem. I narrowed it down by changing values in the rc file until it didn't work any more. in the [Views] section just set "Separator AgendaView" to "0,0" - then KOrganizer shows the grey panel. I don't know how, but KOrganizer (maybe just in an earlier version, or an update?) had set this value to 0,0.
The development of the old KAddressBook will be discontinued for KDE 4.4. Since the new application has the same name, but a completly new code base we close all bug reports against the old version and ask the submitters to resend there reports against the new product.