Nepomuk file indexing stuck in a loop
With the recent upgrade to KDE 4.10 in unstable, Nepomuk file indexing has become somewhat troubled on my system. As far as I can tell, indexing is stuck in a loop through about 10 files, in different folders. The progress display is rather quick, but it seems that all these files are PDFs and undamaged. After the upgrade, I deleted the Nepomuk repository and by now I have rebooted several times. In ~/.xsession-errors, the only messages that seem vaguely relevant are about 5 of the form akonadi_nepomuk_feeder(6556) ItemQueue::fetchJobResult: Not all items were fetched: 2 3 I've already run nepomukcleaner, but with no effect. Does anyone have an idea what might be going wrong and how to diagnose it? Michael -- Michael Schuerig mailto:mich...@schuerig.de http://www.schuerig.de/michael/ -- 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/7369215.BFaCeBe5Cs@fuchsia
akonadi failing to connect to database
I was trying to get kmail working since my upgrade to 4.10. I never got it working in 4.8.4 either, with similar errors. I looked online, but akonadi troubleshooting tips are all over the board. I found some for 4.3, and on the KDE wiki has one troubleshooting tip for "Can't read any details of some messages or big delays to read it" so I thought I would ask here. When I opened kmail, it tried to transition to 4.10, and the first step was to start akonadi. It failed after a few minutes. Tests 1, 2, and 6 passed, tests 3, 4, and 5 (the mysql stuff) were untested. Test 7: ERROR Akonadi control process not registered at D-Bus. Details: The Akonadi control process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup. Test 8: ERROR Akonadi server process not registered at D-Bus. Details: The Akonadi server process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup. Test 9: ERROR Nepomuk search service not registered at D-Bus. Details: The Nepomuk search service is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup. Test 10: SKIP Protocol version check not possible. Details: Without a connection to the server it is not possible to check if the protocol version meets the requirements. Test 11: ERROR No resource agents found. Details: No resource agents have been found, Akonadi is not usable without at least one. This usually means that no resource agents are installed or that there is a setup problem. The following paths have been searched: '/usr/share/akonadi/agents'. The XDG_DATA_DIRS environment variable is set to '/usr/share:/usr/share:/usr/local/share'; make sure this includes all paths where Akonadi agents are installed. Directory listing of '/usr/share/akonadi/agents': akonadinepomukfeederagent.desktop akonotesresource.desktop archivemailagent.desktop birthdaysresource.desktop contactsresource.desktop davgroupwareresource.desktop icaldirresource.desktop icalresource.desktop imapresource.desktop invitationsagent.desktop kabcresource.desktop kalarmdirresource.desktop kalarmresource.desktop kcalresource.desktop kdeaccountsresource.desktop knutresource.desktop localbookmarksresource.desktop maildirresource.desktop maildispatcheragent.desktop mailfilteragent.desktop mboxresource.desktop microblog.desktop mixedmaildirresource.desktop mtdummyresource.desktop nepomuktagresource.desktop nntpresource.desktop notesresource.desktop openxchangeresource.desktop pop3resource.desktop vcarddirresource.desktop vcardresource.desktop Environment variable XDG_DATA_DIRS is set to '/usr/share:/usr/share:/usr/local/share' Test 12: ERROR Current Akonadi server error log found. Details: The Akonadi server reported errors during its current startup. The log can be found in /home/storm/.local/share/akonadi/akonadiserver.error. File '/home/storm/.local/share/akonadi/akonadiserver.error' could not be opened Test 13: ERROR Previous Akonadi server error log found. Details: The Akonadi server reported errors during its previous startup. The log can be found in /home/storm/.local/share/akonadi/akonadiserver.error.old. File '/home/storm/.local/share/akonadi/akonadiserver.error.old' could not be opened Test 14: SUCCESS No current Akonadi control error log found. Details: The Akonadi control process did not report any errors during its current startup. Test 15: SUCCESS No previous Akonadi control error log found. Details: The Akonadi control process did not report any errors during its previous startup. Now in the error log, I see lines like Database error: Cannot open database. Last driver error: "QMYSQL: Unable to connect" Last database error: "Can't connect to local MySQL server through socket '/home/storm/.local/share/akonadi/socket-defiant/mysql.socket' (2)" Unable to open database "Can't connect to local MySQL server through socket '/home/storm/.local/share/akonadi/socket-defiant/mysql.socket' (2) QMYSQL: Unable to connect" "[ 0: akonadiserver() [0x418114] 1: akonadiserver() [0x418541] 2: /lib/x86_64-linux-gnu/libc.so.6(+0x35260) [0x7f8236c4f260] 3: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35) [0x7f8236c4f1e5] 4: /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7f8236c52398] 5: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x102) [0x7f82386f8912] 6: akonadiserver() [0x41a3eb] 7: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7f8238793190] 8: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x11858d) [0x7f82387a058d] 9: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x33) [0x7f82387a9173] 10: akonadiserver() [0x41d2cd] 11: akonadiserver() [0x41e487] 12: akonadiserver() [0x411f43] 13: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f8236c3b995] 14: akonadiserver() [0x41
PDF annotations with okular
I wonder why saving pdf annotations are not enabled in okular 0.16.5. I am using the last kde 4.10.5 from sid 4.10.5 and have installed the last libpoppler. I don't know if I'm missing some package or some configuration. Thanks! http://okular.kde.org/faq.php#addedannotationsinpdf -- 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/CAPYB0AABszkqTGSohRKzdAX7AH+hpk7Dw=91wyv4n38hmuk...@mail.gmail.com
Re: akonadi failing to connect to database
My akonadi works ... until it doesn't Had few if any problems with 4.8 4.10 from the beginning, kmail is quite flakey. Messages will sort of dissappear, the number in the folder will show but no message. Until I restart kmail. After a while, "mail resources broken, on line." Must restart kde to get off that one.
Screen locker not disabled by VLC
Among the casualties caused by the upgrade to KDE 4.10 is, on my system, that the screen saver is not disabled anymore by media players, in particular VLC. So, when I watch a movie now, I have to hit a key or move the mouse every now and then in order to avoid the screen from being locked. I'm using the "Simple locker", although I'd prefer to use the "normal" screen saver with a blank screen. However, the latter doesn't appear to work. I get a blank screen for a very short time, but then the "simple locker" kicks in. One time, after logging out and in again, session management restored about 50 black screen saver windows. Any ideas what's going wrong? Michael -- Michael Schuerig mailto:mich...@schuerig.de http://www.schuerig.de/michael/ -- 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/2313853.CnWo2nRUWl@fuchsia
Re: Screen locker not disabled by VLC
So this is slightly off topic, but I don't think I've run into a single person who's been happy with the new system locker. I'm now using xscreensvaer for all my screen saving and screen locking needs. The steps I took to get this working * Install xscreensaver and all the bells and whistles that come with it * chmod 000 /usr/lib/kde4/libexec/kscreenlocker_greet * Go into the KDE screen saver settings and uncheck "start automatically" * Add /usr/bin/xscreensaver -nosplash to start up with your user session however you want that to happen * run xscreensaver-demo (it'll complain about the daemon not running, start it) and setup your options * echo this script into /etc/pm/sleep.d/xscreensaver.hook http://paste.debian.net/16904/ (remember to throw in your own user or write up some logic to deal with detecting which user is currently logged in and running xscreensaver). * Delete/remove whatever shortcut keys you've got setup to "lock the screen" and create a new one to simply run xscreensaver-commend -lock There's another way to do this out there on the internet I've found to be pretty failtastic, which is replace /usr/lib/kde4/libexec/kscreenlocker_greet with a script that runs xscreensaver-command -lock. The problem with this methoid is that it's really good about not not wanting to lock the screen on suspsend till after your computer has woken up, or worse yet, just not allowing the machine to suspend. I haven't had any issues with the screensaver starting up during a full screen play with VLC, but I don't know if I have any other trickery going on with making that happen. -- Rubin ru...@starset.net signature.asc Description: OpenPGP digital signature
KMail 2: problems after recent changes in unstable
The recent update of KMail/KDE to 4.10 has resulted in several changes for the worse on my system. * Sometimes messages selected in the message list are not shown. The message frame keeps showing "Retrieving Folder Contents. Please wait...". If this happens, all folders and accounts are affected. Restarting Akonadi seems to help. * IMAP: Messages in threads marked as "ignored" or "watched" are not properly marked as read. After migrating to KMail 2, there were thousands of purportedly unread messages, all of them in threads marked either as "ignored" or "watched". Making these messages unread only persistently(!) worked after I removed the "ignored" and "watched" markings. This is not just a migrating issue, I see the same behavior with newly started threads. * After starting KMail, I get a notification that doesn't make sense: "Resource Local is broken. This resource is now online" (sic). Akonadi Console shows the resource having status "Online, Idle" with status message "Ready". * Every now and then I get an error message Conflict Resolution - Local of type KMail Mail Folder Two updates conflict with each other. Please choose which update(s) to apply. If I keep both messages, I can see that they have the same date, so presumably this is indeed an update conflict. However, as there is no other process touching ~/Mail, I have no idea why KMail brings this upon itself. * I have several rules for handling messages marked as spam. They are marked as read and then moved into a Spam folder. The moving works, but the messages show up twice in the Spam folder. One copy is marked as spam and read, the other is unmarked and unread. As far as I can tell, only IMAP accounts are affected. What makes these issues particularly unfortunate is that from a *user's* point of view I see no improvements that might balance them. Michael -- Michael Schuerig mailto:mich...@schuerig.de http://www.schuerig.de/michael/ -- 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/8817081.tx3B3A8NLD@fuchsia
Re: akonadi failing to connect to database
On Thursday, 2013-07-18, Brad Alexander wrote: > Is there a config file that I should get rid of and just let it configure > from defaults? I tried dpkg-reconfigure akonadi-backend-sqlite > akonadi-server akonadiconsole but it had the same behavior after doing so. The package doesn't change any user level configuration. You probably have to install akonadi-backend-mysql or change the config $HOME/.config/akonadi/akonadiserverrc so that it uses QSQLITE3 instead of QMYSQL as the driver. Cheers, Kevin signature.asc Description: This is a digitally signed message part.
