https://bugzilla.novell.com/show_bug.cgi?id=764739 https://bugzilla.novell.com/show_bug.cgi?id=764739#c Wilfred van Velzen changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=764739 https://bugzilla.novell.com/show_bug.cgi?id=764739#c2 Wilfred van Velzen changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Minor |Major --- Comment #2 from Wilfred van Velzen 2012-11-15 22:10:05 UTC --- (In reply to comment #1)

what kde version?

4.7.2

does it still happen in 12.2?

I'm still on 12.1 so I don't know.

as nobody else cried I shall put it as minor...

An issue that only happens after 10 days in a "user" application, has a small chance of getting noticed. To me it's an important loss of function, and it's "my" bug, 'major' it is... To update my experience, because the symptoms have changed (I do regular updates): - I don't notice the high cpu usage of knotify anymore. - I still get reminders from my agenda after the 10 day period, at least for a while. - After the 10 day period my agenda is still gone from the KOrganizer Agenda application's left bottom window plane. And the items aren't visible on the days of the month, and I can't re-add the agenda. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=764739 https://bugzilla.novell.com/show_bug.cgi?id=764739#c4 --- Comment #4 from Wilfred van Velzen 2012-11-16 22:09:29 UTC --- (In reply to comment #3)

can you update kde?

I don't know, can I? It seems like a major operation, which might easaly break some other software... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=764739 https://bugzilla.novell.com/show_bug.cgi?id=764739#c6 Wilfred van Velzen changed: What |Removed |Added ---------------------------------------------------------------------------- Component|KDE4 Applications |KDE4 Applications Product|openSUSE 12.1 |openSUSE 12.3 --- Comment #6 from Wilfred van Velzen 2013-09-26 07:43:06 UTC --- On a freshly installed 12.3 x64, different (new) hardware, I'm still losing the agenda's after a number of days uptime. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=764739 https://bugzilla.novell.com/show_bug.cgi?id=764739#c8 --- Comment #8 from Wilfred van Velzen 2013-09-26 08:51:48 UTC --- (In reply to comment #7)

You should get your agenda back when you run "akonadictl restart" in Konsole. Does this help?

I'll try it when it happens again...

Just a thought: Akonadi uses mysql for its cache, and mysql drops the connection after a certain amount of idle time. Maybe that causes your problem? Have you configured Akonadi to use an external server?

Not that I'm aware off... The Akonadi config should be pretty default on my system, as far as I know I haven't made changes to it's config.

With the default settings, Akonadi starts its own private mysql instance with the timeout set to 365 days, so that should not happen then. But in this case please check the wait_timeout value in ~/.config/akonadi/mysql-local.conf, attach the file if you are not sure.

This file does not exist on my system. I see some refereces to mysql in ~/.config/akonadi/akonadiserverrc, but no timeout setting. There's also no wait_timeout in /etc/my.cnf ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=764739 https://bugzilla.novell.com/show_bug.cgi?id=764739#c10 --- Comment #10 from Wilfred van Velzen 2013-09-26 09:34:00 UTC --- ~/.local/share/akonadi/mysql.conf contains: # wait 365d before dropping the DB connection (default:8h) wait_timeout=31536000 So a disconnected mysql connection probably isn't the cause of this... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=764739 https://bugzilla.novell.com/show_bug.cgi?id=764739#c12 --- Comment #12 from Wolfgang Bauer 2013-10-02 04:40:10 UTC --- (In reply to comment #11)

So I did:

# akonadictl restart D-Bus session bus is not available! "[ 0: akonadictl(_Z11akBacktracev+0x34) [0x417c24] 1: akonadictl() [0x417f61] 2: /lib64/libc.so.6(+0x35450) [0x7fe4aa72f450] 3: /lib64/libc.so.6(gsignal+0x35) [0x7fe4aa72f3d5] 4: /lib64/libc.so.6(abort+0x148) [0x7fe4aa730858] 5: /usr/lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x74) [0x7fe4ab739c54] 6: akonadictl(_ZN15FileDebugStream9writeDataEPKcx+0x9b) [0x41716b] 7: /usr/lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb4) [0x7fe4ab7d32e4] 8: /usr/lib64/libQtCore.so.4(+0x11bf8f) [0x7fe4ab7ddf8f] 9: /usr/lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x3b) [0x7fe4ab7e658b] 10: akonadictl(_ZN13AkApplication4initEv+0xd7) [0x410107] 11: akonadictl(main+0x88) [0x40c138] 12: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7fe4aa71ba15] 13: akonadictl() [0x40dc91] ] " This looks like you tried to run "akonadictl restart" as root, right? You have to run it as your user, not root!

-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=764739 https://bugzilla.novell.com/show_bug.cgi?id=764739#c14 --- Comment #14 from Wolfgang Bauer 2013-10-03 08:12:47 UTC --- (In reply to comment #13)

akonadictl produced a lot of output (I saved it in case you think it's relevant to this bug?). Afterwards I got my agenda's back in korganizer. I still had to select them to make them visible, but that's probably a korganizer "feature".

I don't think the output would tell much, since your problem does not happen on akonadi startup but after ~10 days uptime. I gave that hint just that you don't have to reboot your system everytime that happens. I'm afraid I'm not really sure how to debug this further. (that it only happens after 10 days doesn't make it easier...) In what kind of resource do you have your Agenda stored? Is it a standard ical resource or something else? And if it is, where is the ical file stored (see the resources settings)? On your local system or somewhere else in the network/internet (then maybe it's temporarily not reachable and that causes the problem)? When it happens again, please have a look in akonadiconsole if the resource went offline for some reason (on the "Agents" tab). It should be enough to turn it back online in that case (right-click on it and choose "Toggle Online/Offline"). You could maybe enable debugging output in kdebugdialog and have a look in ~/.xsession-errors after it happened again. Or try if it happens for a new user. But actually I doubt that this is an openSUSE bug. I think you should better report it upstream at http://bugs.kde.org/. You would also reach the Akonadi/KDE PIM developers there, they might have better ideas how to find out what's wrong. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=764739 https://bugzilla.novell.com/show_bug.cgi?id=764739#c16 --- Comment #16 from Wilfred van Velzen 2013-10-03 09:06:09 UTC --- https://bugs.kde.org/show_bug.cgi?id=325577 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.