[konqueror] [Bug 138872] frames are not positioned correctly
https://bugs.kde.org/show_bug.cgi?id=138872 --- Comment #6 from Richard Bos --- Thanks. Amazing old bug report ;) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 271751] Allow to export Advanced Slideshow rendering as a video file
https://bugs.kde.org/show_bug.cgi?id=271751 --- Comment #13 from Richard Bos --- Gilles, thanks. -- You are receiving this mail because: You are watching all bug changes.
[kmarkdownwebview] [Bug 385219] Support custom stylesheet
https://bugs.kde.org/show_bug.cgi?id=385219 Richard Bos changed: What|Removed |Added CC||richard@xs4all.nl --- Comment #1 from Richard Bos --- I would like to see this implemented as well. Notepad++ markdown plugin has this, and it is really nice. The Notepad++ markdown plugin, can export the file to an (html) file as well. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 360834] no mechanism to reattempt to store items without rid (just in db) into the resource
https://bugs.kde.org/show_bug.cgi?id=360834 --- Comment #14 from Richard Bos --- I use kmail more or less on weekly basis (every weekend), and the first I need to do is to clean up emails that I processed before (days or weeks). That are emails that then again retrieved and shown in kmail. It looks like email get stuck through filtering, but what it is I don't know. Some of those emails I can't delete normally. I delete with and deletes the email from kmail, but I don't know what the adverse might be. This behavior removes the fun of using kmail, cause every week I've to clean-up/reread email that I already processed. I really hope this can be taken care of. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 397622] Colorized versus monochrome icons
https://bugs.kde.org/show_bug.cgi?id=397622 Richard Bos changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Richard Bos --- I'm now used to monochrome colored icons. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 397620] kmail 18.08 total column width way too much in folderlist
https://bugs.kde.org/show_bug.cgi?id=397620 Richard Bos changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #5 from Richard Bos --- It seems okay now -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 374108] Akregator - clicking some links in articles has no effect
https://bugs.kde.org/show_bug.cgi?id=374108 Richard Bos changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Richard Bos --- Let's close it. I'm not aware of this kind of issues. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 395711] External images not loaded by default if message was opened in a separate window
https://bugs.kde.org/show_bug.cgi?id=395711 --- Comment #31 from Richard Bos --- One more thank you. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 397620] kmail 18.08 total column width way too much in folderlist
https://bugs.kde.org/show_bug.cgi?id=397620 --- Comment #2 from Richard Bos --- What do you (exactly) mean with: it needs to be setup correctly? When I move the right side of the total column to the left, it does not move. I tried a couple of times, and for longer periods, it does not move. At least to me it appears there is no difference, making it an endless movement When it would have move, no bug report would have been needed. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 395711] Since last Update kmail didn't load external images anymore
https://bugs.kde.org/show_bug.cgi?id=395711 --- Comment #4 from Richard Bos --- Funny, I just wanted to report this issue (again) ;) Because I installed the new KDE (18.08) on a virtual machine and in this virtual machine I have this issue. Not on my current KDE desktop. I've the "Configure Kmail" -> Security -> Allow messages to load external references, this enabled. Full story: Current desktop / kmail version: kmail-17.12.3 openSUSE Leap 15.0 In this version HTML emails are shown correctly (at least the way I want it to be). I created a virtual machine with openSUSE Leap 15.0 copied my .local/share .config and .kde4 directories to the virtual machine All worked as expected. Update KDE to 18.08 with kmail version: kmail-18.08.0 This version shows the issue. It's an issue (bug?) in the new kmail version. I heard more people about this, I hope that this gets fixed before the offical release. Is this ticket on the list with issues to be solved before release? -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 397622] New: Colorized versus monochrome icons
https://bugs.kde.org/show_bug.cgi?id=397622 Bug ID: 397622 Summary: Colorized versus monochrome icons Product: kontact Version: GIT (master) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: richard@xs4all.nl Target Milestone: --- Created attachment 114499 --> https://bugs.kde.org/attachment.cgi?id=114499&action=edit Screenshot comparing colored vs monochrome icons in kontact With the current new (18.08) kontact the nice colored icons are changed to boring monochrome icons. I would like to have the colorized icons in kontact. (Make it at least optional). How can I keep the colored icons? openSUSE Leap 15.0 kontact 5.9.0 rpm -q kontact kontact-18.08.0-lp150.60.1 KDE Frameworks 5.48.0 Qt 5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 397620] New: kmail 18.08 total column width way too much in folderlist
https://bugs.kde.org/show_bug.cgi?id=397620 Bug ID: 397620 Summary: kmail 18.08 total column width way too much in folderlist Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: folders Assignee: kdepim-b...@kde.org Reporter: richard@xs4all.nl Target Milestone: --- Created attachment 114495 --> https://bugs.kde.org/attachment.cgi?id=114495&action=edit Screenshot showing the much too wide total column Total column width way too much in folderlist. I hope that the attached screenshot makes it clear what is wrong. openSUSE Leap 15.0 kmail 5.9.0 # rpm -q kmail kmail-18.08.0-lp150.76.1 KDE Frameworks 5.48.0 Qt 5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 397580] New: Write / flush emails that are missing at disk
https://bugs.kde.org/show_bug.cgi?id=397580 Bug ID: 397580 Summary: Write / flush emails that are missing at disk Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: richard@xs4all.nl Target Milestone: --- Equip akonadi with the possibility to write emails to disk that akonadi knows about in its database and that are missing at disk. At the moment I've the following amount of emails at disk. But kmail reports for sent-mail 13292 and for trash 307 emails. unread totaal folder 0 53 inbox 0 0 outbox 0 13290 sent-mail 0302 trash In case of recovery and the akonadi database is to be restored from scratch, not all emails from sent-mail and trash will be restored (as these are not disk, but are only known in the akonadi database). The feature could be added to akonadictl, akonadiconsole or to e.g. kmail. https://phabricator.kde.org/T638 seems to be related. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 397330] akonactl fsck crashes
https://bugs.kde.org/show_bug.cgi?id=397330 Richard Bos changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #3 from Richard Bos --- akonadictl --fsck finishes okay now, although nothing changed. I think the data is changed, but what data Will close the bug report. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 397330] akonactl fsck crashes
https://bugs.kde.org/show_bug.cgi?id=397330 --- Comment #2 from Richard Bos --- The command output is (akonadictl --verbose fsck): # akonadictl --verbose fsck Looking for resources in the DB not matching a configured resource... Looking for collections not belonging to a valid resource... Checking collection tree consistency... Looking for items not belonging to a valid collection... Looking for item parts not belonging to a valid item... Looking for item flags not belonging to a valid item... Looking for overlapping external parts... Verifying external parts... Found 128 external files. Found 128 external parts. Found no unreferenced external files. Checking size treshold changes... Found 0 parts to be moved to external files Found 0 parts to be moved to database Looking for dirty objects... Collection "Search" (id: 1) has no RID. Collection "OpenInvitations" (id: 1416) has no RID. Collection "DeclinedInvitations" (id: 1417) has no RID. Found 3 collections without RID. Item "319051" has no RID. Item "328336" has no RID. Item "328379" has no RID. Item "328420" has no RID. Item "328422" has no RID. Item "328428" has no RID. Found 6 items without RID. Found 0 dirty items. Looking for rid-duplicates not matching the content mime-type of the parent collection Checking agenda folder-1 (editted by bug reporter) Checking agenda folder-N (editted by bug reporter) Checking akonadi_davgroupware_resource_6 Checking akonadi_vcarddir_resource_10 Checking akonadi_vcarddir_resource_11 Checking akonadi_vcarddir_resource_12 Checking akonadi_vcarddir_resource_8 Checking akonadi_vcarddir_resource_9 Checking DeclinedInvitations Checking OpenInvitations Checking mail folder-1 (editted by bug reporter) Checking mail folder-N (editted by bug reporter) Checking https://owncloud./remote.php/dav/addressbooks/users//default/ Checking https://owncloud./remote.php/dav/calendars//am/ Checking https://owncloud./remote.php/dav/calendars//contact_birthdays/ Checking https://owncloud./remote.php/dav/calendars//default calendar/ Migrating parts to new cache hierarchy... Most (if not all) item's without RID are agenda items -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 397330] akonactl fsck crashes
https://bugs.kde.org/show_bug.cgi?id=397330 --- Comment #1 from Richard Bos --- In thread 6 I see: #9 0x7f100f57706f in qt_message_print (message=..., context=..., msgType=QtFatalMsg) at global/qlogging.cpp:1656 #10 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, context=..., msg=msg@entry=0x7f100f8401f0 "ASSERT: \"%s\" in file %s, line %d", ap=ap@entry=0x7f0fff7fd298) at global/qlogging.cpp:281 #11 0x7f100f578869 in QMessageLogger::fatal (this=this@entry=0x7f0fff7fd370, msg=msg@entry=0x7f100f8401f0 "ASSERT: \"%s\" in file %s, line %d") at global/qlogging.cpp:793 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 392947] Configuration crash after parallel installation of openLeap42.2 to older version
https://bugs.kde.org/show_bug.cgi?id=392947 Richard Bos changed: What|Removed |Added CC||richard@xs4all.nl Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 397330] New: akonactl fsck crashes
https://bugs.kde.org/show_bug.cgi?id=397330 Bug ID: 397330 Summary: akonactl fsck crashes Product: Akonadi Version: 5.7.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: richard@xs4all.nl Target Milestone: --- Application: akonadiserver (5.7.3) Qt Version: 5.9.4 Frameworks Version: 5.45.0 Operating System: Linux 4.12.14-lp150.12.10-default x86_64 Distribution (Platform): openSUSE RPMs -- Information about the crash: - What I was doing when the application crashed: Executed the command: # akonadictl --verbose fsck I recently migrated from an older openSUSE version to openSUSE Leap 15. After the migration, the above command finished successfully. Now with kmail and akonadi sometime in use (1,5 weeks) the command does not finish succesfully. The crash can be reproduced every time. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1010fa98c0 (LWP 4904))] Thread 48 (Thread 0x7f0f68ff1700 (LWP 11476)): #0 0x7f100b7b96a9 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #1 0x7f100b7ba03b in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f100b7ba21c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f100f7b0c0b in QEventDispatcherGlib::processEvents (this=0x7f0fa000f5b0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f100f75909a in QEventLoop::exec (this=this@entry=0x7f0f68ff0d10, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f100f5884da in QThread::exec (this=) at thread/qthread.cpp:515 #6 0x7f100f58d0ce in QThreadPrivate::start (arg=0x7f0f8406f200) at thread/qthread_unix.cpp:368 #7 0x7f100da70559 in start_thread () from /lib64/libpthread.so.0 #8 0x7f100ec7582f in clone () from /lib64/libc.so.6 Thread 47 (Thread 0x7f0f69ff3700 (LWP 11151)): #0 0x7f100b7ff759 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f100b7b9b34 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #2 0x7f100b7ba0b0 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f100b7ba21c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f100f7b0c0b in QEventDispatcherGlib::processEvents (this=0x7f0f8c029bf0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f100f75909a in QEventLoop::exec (this=this@entry=0x7f0f69ff2d10, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f100f5884da in QThread::exec (this=) at thread/qthread.cpp:515 #7 0x7f100f58d0ce in QThreadPrivate::start (arg=0x5620b7ac24d0) at thread/qthread_unix.cpp:368 #8 0x7f100da70559 in start_thread () from /lib64/libpthread.so.0 #9 0x7f100ec7582f in clone () from /lib64/libc.so.6 Thread 46 (Thread 0x7f0f6a7f4700 (LWP 11149)): #0 0x7f100ec6b08b in poll () from /lib64/libc.so.6 #1 0x7f100b7ba109 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f100b7ba21c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f100f7b0c0b in QEventDispatcherGlib::processEvents (this=0x7f0f80029b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f100f75909a in QEventLoop::exec (this=this@entry=0x7f0f6a7f3d10, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f100f5884da in QThread::exec (this=) at thread/qthread.cpp:515 #6 0x7f100f58d0ce in QThreadPrivate::start (arg=0x7f0f84015f20) at thread/qthread_unix.cpp:368 #7 0x7f100da70559 in start_thread () from /lib64/libpthread.so.0 #8 0x7f100ec7582f in clone () from /lib64/libc.so.6 Thread 45 (Thread 0x7f0f6700 (LWP 11147)): #0 0x7f100b7ff339 in g_private_get () from /usr/lib64/libglib-2.0.so.0 #1 0x7f100b7e1ce0 in g_thread_self () from /usr/lib64/libglib-2.0.so.0 #2 0x7f100b7ba20d in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f100f7b0c0b in QEventDispatcherGlib::processEvents (this=0x7f0f84056ae0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f100f75909a in QEventLoop::exec (this=this@entry=0x7f0f6fffed10, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f100f5884da in QThread::exec (this=) at thread/qthread.cpp:515 #6 0x7f100f58d0ce in QThreadPrivate::start (arg=0x7f0f90020ab0) at thread/qthread_unix.cpp:368 #7 0x7f100da70559 in start_thread () from /lib64/libpthread.so.0 #8 0x7f100ec7582f in clone () from /lib64/libc.so.6 Thread 44 (Thread 0x7f0f6aff5700 (LWP 6292)): #0 0x7f100b7ff774 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f100b7b9aa8 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #2 0x7f100b7ba0b0 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f100b
[Akonadi] [Bug 360834] no mechanism to reattempt to store items without rid (just in db) into the resource
https://bugs.kde.org/show_bug.cgi?id=360834 Richard Bos changed: What|Removed |Added CC||richard@xs4all.nl --- Comment #10 from Richard Bos --- Any update on this? Like others suggestes, this should have high priority as it may result in loss of data. This one seems related: 362044 I'm encountering a akonadiserver crash when running akonadictl --fsck, but don't know why, are what to do about it. In file_lost+found I found this file: -rw-r--r-- 1 user users 4238 5 aug 07:58 922307_r0 It's an email, but to which (former) folder it belonged I've no idea. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 389607] akonadictl fsck: Show more helpful messages
https://bugs.kde.org/show_bug.cgi?id=389607 Richard Bos changed: What|Removed |Added CC||richard@xs4all.nl --- Comment #4 from Richard Bos --- I agree with this. In my case I get: # akonadictl --verbose fsck Looking for resources in the DB not matching a configured resource... Looking for collections not belonging to a valid resource... Checking collection tree consistency... Looking for items not belonging to a valid collection... Looking for item parts not belonging to a valid item... Looking for item flags not belonging to a valid item... Looking for overlapping external parts... Verifying external parts... Found 165 external files. Found 165 external parts. Found no unreferenced external files. Checking size treshold changes... Found 0 parts to be moved to external files Found 0 parts to be moved to database Looking for dirty objects... Collection "Search" (id: 1) has no RID. Collection "OpenInvitations" (id: 1416) has no RID. Collection "DeclinedInvitations" (id: 1417) has no RID. Found 3 collections without RID. Item "243448" has no RID. Item "243531" has no RID. Item "243813" has no RID. Item "243868" has no RID. Item "243869" has no RID. Item "243986" has no RID. Item "244023" has no RID. Item "244026" has no RID. Item "244111" has no RID. Item "244176" has no RID. Item "244379" has no RID. Item "244393" has no RID. Item "244399" has no RID. Item "319051" has no RID. Item "328336" has no RID. Item "328379" has no RID. Found 16 items without RID. Item "232461" has RID and is dirty. Item "239145" has RID and is dirty. Item "243363" has RID and is dirty. Item "328334" has RID and is dirty. Found 4 dirty items. Looking for rid-duplicates not matching the content mime-type of the parent collection Checking Notes Checking Notities Checking Search Checking akonadi_davgroupware_resource_1 Checking akonadi_vcarddir_resource_10 Checking akonadi_vcarddir_resource_11 Checking akonadi_vcarddir_resource_12 Checking akonadi_vcarddir_resource_8 Checking akonadi_vcarddir_resource_9 Checking DeclinedInvitations Checking OpenInvitations Checking https:///remote.php/caldav/calendars//contact_birthdays/ Checking https:///remote.php/caldav/calendars//default calendar/ Checking https:///remote.php/carddav/addressbooks//default/ ___checking of all folders___ Migrating parts to new cache hierarchy... CRASH of akonadi! This happens now everytime. It worked before. Now how to make akonadictl fsck work again???! BTW: creating a bug report (with stackback trace) does not work :( Would be nice / good to give this attention at Akademy -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 389607] akonadictl fsck: Show more helpful messages
https://bugs.kde.org/show_bug.cgi?id=389607 Richard Bos changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 396781] kmail no longer shows new mails
https://bugs.kde.org/show_bug.cgi?id=396781 --- Comment #2 from Richard Bos --- Rebuilding what? - The code? - Or the data? When data, how did you rebuild it? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 365162] after upgrading today, kmail folder list corrupted
https://bugs.kde.org/show_bug.cgi?id=365162 Richard Bos changed: What|Removed |Added CC|richard@xs4all.nl | -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 365162] after upgrading today, kmail folder list corrupted
https://bugs.kde.org/show_bug.cgi?id=365162 Richard Bos changed: What|Removed |Added CC||richard@xs4all.nl --- Comment #5 from Richard Bos --- Suggestion: close this bug report? -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 374108] Akregator - clicking some links in articles has no effect
https://bugs.kde.org/show_bug.cgi?id=374108 Richard Bos changed: What|Removed |Added CC||richard@xs4all.nl --- Comment #1 from Richard Bos --- Looks like this bug: https://bugreports.qt.io/browse/QTBUG-67870 As described at: https://blogs.kde.org/2018/07/24/2018-toulouse-pim-sprint-report (look for Investigated Qt 5.11 bug which broke clicking on links in KMail... fixed) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 395711] Since last Update kmail didn't load external images anymore
https://bugs.kde.org/show_bug.cgi?id=395711 Richard Bos changed: What|Removed |Added CC||richard@xs4all.nl --- Comment #2 from Richard Bos --- boospy: can you describe better where to find the "load external references"? For example with a screenshot. I ask because I can't find the setting you're referring to. Hmm, I found it now: it's the menu folder in the main menu (on top of kmail) and not on the folder itself. In my case "load external references" is grayed out. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 181986] Implement the "Set Selection End " action within context menu, as in KDE3 konsole
https://bugs.kde.org/show_bug.cgi?id=181986 --- Comment #9 from Richard Bos --- OK, thanks (a lot)! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 181986] Implement the "Set Selection End " action within context menu, as in KDE3 konsole
https://bugs.kde.org/show_bug.cgi?id=181986 Richard Bos changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 181986] Implement the "Set Selection End " action within context menu, as in KDE3 konsole
https://bugs.kde.org/show_bug.cgi?id=181986 Richard Bos changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WAITINGFORINFO |--- --- Comment #7 from Richard Bos --- For short text selections using the shift button is fine. The request is however for long (huge) text selections. In this case (long text selection), one just marks the beginning of the text, release the mouse, scroll down (many, many lines) and when the correct point is reach where the text selection should end, the "selection end" from the the console context menu is then used. Very convenient. Much more convenient then scrolling down, down, ,down (while scrolling down the mouse releases, and one has to start over again. Hence, the "selection end" is power users, and very much desired. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 386278] Need warning when zooming is initiated
https://bugs.kde.org/show_bug.cgi?id=386278 --- Comment #3 from Richard Bos --- That's too bad. In that case I've remove the key assignment: To prevent this from happening again, I removed the meta key combination; (kde) system settings -> accelerator keys -> global keys -> system settings -> zoom in Remove it from there. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 386278] Need warning when zooming is initiated
https://bugs.kde.org/show_bug.cgi?id=386278 --- Comment #1 from Richard Bos --- Perhaps it is possible to show something on the desktop that zooming has been activated, including a zoom back to normal button at the top of screen (for example). Even the user enabled "no longer show this popup message", show it again when the zooming functionality has not been used for a long time (1 year). One might not remember that zooming has been enabled and that it can be restored using for example +- I hope that usability issue gets a good followup. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 386278] New: Need warning when zooming is initiated
https://bugs.kde.org/show_bug.cgi?id=386278 Bug ID: 386278 Summary: Need warning when zooming is initiated Product: kwin Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: richard@xs4all.nl Target Milestone: --- By accident I just hit the key combination += and suddenly my screen is very very unpleasant to work; the KDE desktop was too big to fit in the monitor area! As this just occured after upgrading to KDE-5.39 I expected something was wrong in the new kde packages. After using different desktops (icewm, gnome), logging into other KDE user desktops none of them showed the issues. So it really seemed to be a KDE thing in my user environment. Spending some time, moving away files and putting them back one by one I was in the end able to restore the situation. Using the backup I have; in the end it appeared that the ~/.config/kwinrc contained the culprit. The setting InitialZoom was set to 1.2 [Effect-Zoom] InitialZoom=1.2 With help of https://forums.opensuse.org/showthread.php/527862-After-upate-KDE-screen-no-longer-fits-in-monitor-screen I'm now aware that is a zoom factor, and can be reverted using the combinatie +- May I asked for a popup window that shows up when those (type of) buttons are activated, at least when the +- is activated. The popup should inform the user, that the zooming can be undone using +- The popup should have the option "do you want to see this window next time". When it is not possible to tell the user how to undo the zooming as the unzoom combination is configurable, ask the user: "are you sure to zoom in? Do you want to continue?" Zooming can be undone with the correct key combination. I hope I get my message across. Make sure that users that are hitting this key combination by accident (in my case I was looking for another key combination), are informed what is going to happen, that it can be undone, and especially where to look for information about this feature (desktop zooming). I consider this a bug, although the software is working correctly, but it results in a desktop that is no longer useful and I had to use my backup to restore the old situation! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383646] Store facetag information in the photo file
https://bugs.kde.org/show_bug.cgi?id=383646 --- Comment #6 from Richard Bos --- Thanks. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383646] Store facetag information in the photo file
https://bugs.kde.org/show_bug.cgi?id=383646 --- Comment #4 from Richard Bos --- Thanks for the feedback. Where is it in the manual? I did not found it (just searched for it). > How you should know? > Well besides what you mentioned we have a manual - not sure what else you > would expect. Propose the setting before creating the database? Why is it not enabled by default? For archive purpose I put the following information here: I found the data that is written to the photo file. Region Name : Pers 1, Pers 2, Pers 3, Pers 4, Pers 5 Region Type : Face, Face, Face, Face, Face Region Area X : 0.58125, 0.771875, 0.865625, 0.191875, 0.26625 Region Area Y : 0.429167, 0.3175, 0.3225, 0.325, 0.628333 Region Area W : 0.09, 0.06875, 0.07875, 0.09125, 0.165 Region Area H : 0.151667, 0.111667, 0.138333, 0.14, 0.276667 Region Area Unit: normalized, normalized, normalized, normalized, normalized Region Rectangle: 0.53625, 0.35, 0.09, 0.151667, 0.7375, 0.261667, 0.06875, 0.111667, 0.82625, 0.25, 0.07875, 0.138333, 0.14625, 0.25, 0.09125, 0.14, 0.18375, 0.49, 0.165, 0.276667 Region Person Display Name : Pers 1, Pers 2, Pers 3, Pers 4, Pers 5 The data was not available, after I enabled the 'write face tag to photo file'. It was only available for the photo files after I made a dummy face tag update in the particular photo? The face tag information was also written to the photo file, with the function "write metadata to photo" (menu option: item -> "write metadata to photo"). Is there a possibility to automatically write only the face tag data to the photo files that were tagged before enabling "write facetag to photo file"? Is there a query possible to looks up which photo have face tags, and activate ""write metadata to photo" (via a dbus command)? (would that make sense)? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383646] Store facetag information in the photo file
https://bugs.kde.org/show_bug.cgi?id=383646 --- Comment #2 from Richard Bos --- That's wunderful! Where is more information about this? H ow should the user know, that this setting exist? PS: the user should just browse the settings tab is a unexpected answer, but not the one I'm looking for. Why is it not enabled by default? What about the facetags that I already populated, how can I get those written to the photo files? Is that taken care of automatically when the setting is enabled? How can I verify that the facetag has been written to the photo files for the photos that I already face tagged? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383646] New: Store facetag information in the photo file
https://bugs.kde.org/show_bug.cgi?id=383646 Bug ID: 383646 Summary: Store facetag information in the photo file Product: digikam Version: 5.7.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Faces-Maintenance Assignee: digikam-bugs-n...@kde.org Reporter: richard@xs4all.nl Target Milestone: --- Due to a database corruption, some photo's were not displayed anymore. The only way (known till this date) was to recreate the database. For a lot of information / tags that is fine, as the data is stored in the database as well as in the photo files. Recreating the database from the data in the photofiles takes some time, but after that most information is back. Most as the facetag information is missing. Like most other tag information, store the facetag information in the photo file, please. When this can be accomplished it is very, very, very valuable when the database must be recreated from scratch. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383552] New: Add filename when mimetype is processed when database is created for the first time
https://bugs.kde.org/show_bug.cgi?id=383552 Bug ID: 383552 Summary: Add filename when mimetype is processed when database is created for the first time Product: digikam Version: 5.7.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: richard@xs4all.nl Target Milestone: --- When there is no database and digikam is started for the first time, digikam starts to initialize all the photos in the collection. This takes a long time. Especially the part that is outputting: digikam.general: mimetype = "JPEG" ext = "JPG" digikam.metaengine: Orientation => Exif.Image.Orientation => 1 digikam.general: mimetype = "JPEG" ext = "JPG" digikam.metaengine: Orientation => Exif.Image.Orientation => 1 Takes a long time. As there is no indication what file is processed, the used does not have much about the above included information. Add the filename of the photo that is processed to the messages above, this would make it already more useful / informative. In the case digikam was started from the command line. I also missed a progress marker, but perhaps I overlooked it? I also missed a remark whether it is OK to interrupt this DB recreation process. May it be stopped and will it continue when digikam is restated next time. Anyway, it might be useful to add a remark about this at the DB configuration screen. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 344874] username/password not being sent in header
https://bugs.kde.org/show_bug.cgi?id=344874 Richard Bos changed: What|Removed |Added CC||richard@xs4all.nl --- Comment #14 from Richard Bos --- Is this big https://github.com/nextcloud/server/issues/5326 related? I opened the bug report at nextcloud, but they refer to KDE. The message I get in logfiles is: No 'Authorization: Basic' header found. Either the client didn't send one, or the server is misconfigured in logfile -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 271751] Allow to export Advanced Slideshow rendering as a video file
https://bugs.kde.org/show_bug.cgi?id=271751 --- Comment #10 from Richard Bos --- Gilles, well done. Looking forward to have it available (some day)... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 271751] Allow to export Advanced Slideshow rendering as a video file
https://bugs.kde.org/show_bug.cgi?id=271751 --- Comment #4 from Richard Bos --- Thanks for adding the requested functionality. Very nice :) -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 64603] Multiple overlapping events in agenda view are layed out wrong (overlapping, too wide, different widths, etc.)
https://bugs.kde.org/show_bug.cgi?id=64603 --- Comment #13 from Richard Bos --- Denis you're my hero. Thanks for looking into the KDE bug situation and for verying this problem. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 158921] recurring entries on Feb 29. missing in non leap years
https://bugs.kde.org/show_bug.cgi?id=158921 --- Comment #5 from Richard Bos --- Denis you're my hero. Thanks for looking into the KDE bug situation and for verying this problem. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 64603] Multiple overlapping events in agenda view are layed out wrong (overlapping, too wide, different widths, etc.)
https://bugs.kde.org/show_bug.cgi?id=64603 --- Comment #11 from Richard Bos --- Why propose to close this bug? Perhaps the people in this bug report are not yet running the KDE version you asked for. On the other hand the example in the attachment is rather clear how to reproduce the problem ( https://bugs.kde.org/show_bug.cgi?id=64603#attach_26967 ). In case you're running the required KDE version, just schedule 4 events and see for yourself if the problem is fixed or not. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 158921] recurring entries on Feb 29. missing in non leap years
https://bugs.kde.org/show_bug.cgi?id=158921 --- Comment #3 from Richard Bos --- I reported the bug. I'm running kontact at version 4.14, as such I can't test the way you requested. I assume that you're running KDE at version 5 or later. But this bug should be easily reproducible. Let me repeat it from initial problem description: How to reproduce, but updated for recent years: - Schedule an event without time associated on feb 29 2016 in korganizer ( - The event must recur each year on the 29 of February The solution might be a warning when the event is scheduled. Now check the event on the next years 2017, 2018, 2019 and 2020. In 2019-2019 it is not present neither on 1 march, on 29 feb 2020 it is back. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Workspace Wallpapers] [Bug 366470] Add unsplash wallpapers to KDE
https://bugs.kde.org/show_bug.cgi?id=366470 --- Comment #3 from Richard Bos --- Indeed Martin. My idea is not to include each and every wallpaper, but to offer the source via ( wallpaper ) plugin(s). Either by making it easily available to the user, or as a dynamic wallpaper. -- Richard ps: if the above correction make sense, change the status to inprogress. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Workspace Wallpapers] [Bug 366470] New: Add unsplash wallpapers to KDE
https://bugs.kde.org/show_bug.cgi?id=366470 Bug ID: 366470 Summary: Add unsplash wallpapers to KDE Product: Plasma Workspace Wallpapers Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: plasma-de...@kde.org Reporter: richard@xs4all.nl https://unsplash.com/ offer wallpapers for free. At https://unsplash.com/developers the API is explained. Have the wallpapers added to KDE, it seems to be nice library. Reproducible: Always Steps to Reproduce: Feature request -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 362441] Caption and Tags - use 4 digit year format instead of 2 digit year format (additionally add seconds)
https://bugs.kde.org/show_bug.cgi?id=362441 --- Comment #4 from Richard Bos --- Thanks for the quick fix! I hope that 5.0 becomes quickly available for openSUSE. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 362441] Use 4 digit year format instead of 2 digit year format ( additionally add seconds )
https://bugs.kde.org/show_bug.cgi?id=362441 --- Comment #1 from Richard Bos --- Created attachment 98670 --> https://bugs.kde.org/attachment.cgi?id=98670&action=edit Screenshot showing the menu and the date/time field -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 362441] New: Use 4 digit year format instead of 2 digit year format ( additionally add seconds )
https://bugs.kde.org/show_bug.cgi?id=362441 Bug ID: 362441 Summary: Use 4 digit year format instead of 2 digit year format ( additionally add seconds ) Product: digikam Version: 4.14.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Metadata-Editor Assignee: digikam-de...@kde.org Reporter: richard@xs4all.nl Date modification using menu "captions/tags" from the right side bar In this menu in tab "Description" there is the possibility to enter a date. The date format is dd/mm/yy hh:mm The date with the 2 digit format is sometimes changed from 1995 to 2095 unintentionally. This happens when e.g. the date set incorrectly to e.g. Assigned date: 01/07/1995, visible date 01/07/95 Assume 1 july ( 01/07 ) was wrong and should have been 14 july. So change 01/07/95 to 14/07/95. Looks OK, but at the same time the year was changed from 1995 to 2095! This is not wanted! Sect 2: please add seconds To make it possible to have photos displayed in the chronological order make it possible to add seconds in this time field. I use the utility 'exiftool' to have seconds added to the EXIF field in the photos. It's a pity that it is not possible via this GUI date/time filed. Reproducible: Always Steps to Reproduce: 1. Start Digikam 2. Open a photo with the date set to 01/07/1995 ( 1 July ) 3. Modify the day from 01 to e.g. 14 using the Date field in the "captions/tags" menu from the right side bar ( in the tab Description ) Sect 2: seconds 1. See the time field, it is not possible to enter seconds in the field Actual Results: Not only the day is changed from 01 to 14, but the year is also changed from 1995 to 2095 Sect 2: seconds 1. It is not possible to enter seconds in the time field Expected Results: The year information should remain unchanged. Sect 2: seconds 1. It is now possible to enter seconds in the time field besides hours:minutes ( thus hh:mm:ss ) Screenshot will be added -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361611] Plugin 'Advanced Slide Show' - "Print Caption" does not work
https://bugs.kde.org/show_bug.cgi?id=361611 --- Comment #2 from Richard Bos --- Impressive. Does this make it work in Gwenview too, or only in digikam and showfoto? I'm using Gwenview 4.18.x /me hoping to see this working in this version 4.y.x ... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361611] New: Plugin 'Advanced Slide Show' - "Print Caption" does not work
https://bugs.kde.org/show_bug.cgi?id=361611 Bug ID: 361611 Summary: Plugin 'Advanced Slide Show' - "Print Caption" does not work Product: digikam Version: 4.14.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Presentation Assignee: digikam-de...@kde.org Reporter: richard@xs4all.nl The Plugin 'Advanced Slide Show' - "Print Caption" does not work. I use the plugin from Gwenview. Reproducible: Always Steps to Reproduce: 1. Start gwenview to start the kipi plugin AdvancedSlideShow ( Gwenview -> Plugins -> > > Tools -> AdvancedSlideShow ) 2. There is an option to enable 'print caption' 3. This should display EXIF information from the photo, when the slide show is running Actual Results: Nothing is displayed ( at least not the caption ). The file name and progress marker are displayed. Expected Results: The caption ( EXIF ) should be displayed. Some information from GIlles: Op zondag 10 april 2016 11:11:42 schreef u: > Hi, > > The print caption show image comment passed from kipi host to the plugin > by libkipi. > > the kipi interface is reimplemented in kipi host. Each kipi host pass the > right information to populate caption in plugin. > > In digiKam, if Exif comment exist, it populate the database and pass this > information through kipi interface if a plugin need it. > > In other word, the problem is in the kipi host re-implementation. > > Best > > Gilles Caulier 2016-04-10 11:49 GMT+02:00: Hi Gilles, thanks for your response. The EXIF information exists in Digikam, but it is not displayed. Now how do I report this bug? I'm ( very ) familair with the KDE bug tracking system, but in this particular case, which component do I select to report the error for? ps: can you confirm that you see the same problem perhaps it is something local in my installation... -- Richard Op zondag 10 april 2016 21:59:48 schreef u: > yes, problem is reproducible. > > Please report it to digiKam component of KDE bugzilla, into Presentation > section. > > Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 357179] New: Email remains in inbox after moving it to a folder
https://bugs.kde.org/show_bug.cgi?id=357179 Bug ID: 357179 Summary: Email remains in inbox after moving it to a folder Product: kmail2 Version: 4.14.7 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: richard@xs4all.nl When an email is moved from inbox to another folder, it re-appears in inbox ( the copy in the other folder stays there btw ). Reproducible: Always Steps to Reproduce: 1. receive an email 2. move it from inbox to another folder 3. verify that the email has been moved to the other folder 4. go back to the inbox 5. the moved email appears again in the inbox This behavior is the same for messages moved manually as well as filtered emails Actual Results: The moved email re-appears in inbox Expected Results: The moved email should not re-appear in the inbox, as it has been copied to another folder. I'm using pop email. I recently updated from openSUSE_13.1 where emails moving and filtering worked just great ( as expected ). Currently running kmail-4.14.10. Looks a bit similar to bug report: 350059 But indeed also for me email filters are at the moment not usuable. Restarting akonadictl does not help. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 357067] New: kmail crashed when configuring appearance
https://bugs.kde.org/show_bug.cgi?id=357067 Bug ID: 357067 Summary: kmail crashed when configuring appearance Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: richard@xs4all.nl Application: kmail (4.14.10) KDE Platform Version: 4.14.10 Qt Version: 4.8.6 Operating System: Linux 4.1.13-5-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: start kmail setings configure kmail click at appearance crash Tried to launch kmail from other users desktops, it always crashed. While kmail for the other users are not crashing. Might it have something to do with the (kde4) theme? If so, how do I change it from kde5? The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5cd87ba840 (LWP 16995))] Thread 5 (Thread 0x7f5cb1167700 (LWP 16998)): #0 0x7f5cce58b05f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5cca964eb6 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQtWebKit.so.4 #2 0x7f5cca964ee9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x7f5cce5870a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f5cd5a4104d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f5c6bdd8700 (LWP 16999)): #0 0x7f5cce58b05f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5cca6d7b3d in JSC::BlockAllocator::blockFreeingThreadMain() () from /usr/lib64/libQtWebKit.so.4 #2 0x7f5cca98ca06 in WTF::wtfThreadEntryPoint(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x7f5cce5870a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f5cd5a4104d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f5c6b1d7700 (LWP 17002)): #0 0x7f5cd5a34ced in read () from /lib64/libc.so.6 #1 0x7f5cbdd6df45 in ?? () from /usr/lib64/tls/libnvidia-tls.so.340.93 #2 0x7f5ccd7acb60 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f5ccd76b999 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #4 0x7f5ccd76bdf8 in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x7f5ccd76bf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #6 0x7f5cd710bfde in QEventDispatcherGlib::processEvents (this=0x7f5c5c0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #7 0x7f5cd70ddd4f in QEventLoop::processEvents (this=this@entry=0x7f5c6b1d6da0, flags=...) at kernel/qeventloop.cpp:149 #8 0x7f5cd70de045 in QEventLoop::exec (this=this@entry=0x7f5c6b1d6da0, flags=...) at kernel/qeventloop.cpp:204 #9 0x7f5cd6fdb4df in QThread::exec (this=) at thread/qthread.cpp:538 #10 0x7f5cd6fddbbf in QThreadPrivate::start (arg=0x26876f0) at thread/qthread_unix.cpp:349 #11 0x7f5cce5870a4 in start_thread () from /lib64/libpthread.so.0 #12 0x7f5cd5a4104d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f5c69c0a700 (LWP 17005)): #0 0x7f5cce58b05f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5cbfe5b86b in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7f5cc0157ee0 ) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #2 0x7f5cbfe5b8a9 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #3 0x7f5cce5870a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f5cd5a4104d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f5cd87ba840 (LWP 16995)): [KCrash Handler] #6 data (this=0x8) at ../../src/corelib/tools/qscopedpointer.h:135 #7 qGetPtrHelper > (p=...) at ../../src/corelib/global/qglobal.h:2466 #8 d_func (this=0x0) at widgets/qabstractbutton.h:171 #9 QAbstractButton::setChecked (this=0x0, checked=true) at widgets/qabstractbutton.cpp:738 #10 0x7f5cd82cb7fd in load (this=0x2e11760) at /usr/src/debug/kdepim-4.14.10/kmail/configuredialog/configuredialog_p.cpp:82 #11 ConfigModuleWithTabs::load (this=0x2d9e050) at /usr/src/debug/kdepim-4.14.10/kmail/configuredialog/configuredialog_p.cpp:52 #12 0x7f5cd7bd1839 in KCModule::qt_static_metacall (_o=, _id=, _a=, _c=) at /usr/src/debug/kdelibs-4.14.10/build/kdeui/kcmodule.moc:65 #13 0x7f5cd70f749e in QObject::event (this=this@entry=0x2d9e050, e=e@entry=0x2c3d180) at kernel/qobject.cpp:1231 #14 0x7f5cd64c8cab in QWidget::event (this=0x2d9e050, event=0x2c3d180) at kernel/qwidget.cpp:8859 #15 0x7f5cd647979c in QApplicationPrivate::notify_helper (this=this@entry=0x1d92470, receiver=receiver@entry=0x2d9e050, e=e@entry=0x2c3d1
[Akonadi] [Bug 357064] New: Mail not accessible after migration
https://bugs.kde.org/show_bug.cgi?id=357064 Bug ID: 357064 Summary: Mail not accessible after migration Product: Akonadi Version: 4.13 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: Maildir Resource Assignee: kdepim-b...@kde.org Reporter: richard@xs4all.nl Mail not accessible after migration. The migration was done after updating from openSUSE_13.1 to openSUSE_leap kmail created a new resource called "Local Folders", but the old previous folders "Kmail folders" were not migrated to the new Local Folders. Very frustrating. After many attempts, using various ways, fortunately having backup arounds, I started kmail, from the command line. Kmail finished the migration, spitting the following line 10 times per second and never stopping: Resource id's don't match: "akonadi_maildir_resource_1" "akonadi_maildir_resource_0" Looking for this results in this bug report: https://bugs.kde.org/show_bug.cgi?id=255104 (Thus that report is still not solved)! The bugreport points to: https://forum.kde.org/viewtopic.php?f=215&t=120777#p308518 Which has the solution. At the bottom at states: https://forum.kde.org/viewtopic.php?f=215&t=120777#p347175 For me it was sufficient to remove the local trash folder: rm -rf .local/share/local-mail/trash/ Have this fixed please, because it takes a whole day to work out the problem, it is frustrating as it looks like old email is no longer accessible, etc. Reproducible: Always Steps to Reproduce: 1. See above 2. 3. Actual Results: Email is no longer accessible! very bad. Expected Results: Nice smooth migration, and emails always accessible -- You are receiving this mail because: You are watching all bug changes.
