[kontact] [Bug 405711] Kontact crash after chainging UI language
https://bugs.kde.org/show_bug.cgi?id=405711 Mathias Homann changed: What|Removed |Added Version|5.10.3 |5.21.1 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405711] Kontact crash after chainging UI language
https://bugs.kde.org/show_bug.cgi?id=405711 Mathias Homann changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #7 from Mathias Homann --- does not reproduce anymore. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 378513] kontact or akregator crash after close/restart
https://bugs.kde.org/show_bug.cgi?id=378513 Mathias Homann changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #48 from Mathias Homann --- 4 years old. this bug has disappeared and resurfaced many times since then, most likely different reasons each time. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 415634] kontact crash on opening settings
https://bugs.kde.org/show_bug.cgi?id=415634 Mathias Homann changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #20 from Mathias Homann --- Bugs like this one keep disappearing and reappearing. TWO years later this specific occurence is most likely long gone. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 416136] kontact crash on exit
https://bugs.kde.org/show_bug.cgi?id=416136 Mathias Homann changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #2 from Mathias Homann --- right now this does not reproduce. Operating System: openSUSE Tumbleweed 20221003 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 457958] New: crash on close
https://bugs.kde.org/show_bug.cgi?id=457958 Bug ID: 457958 Summary: crash on close Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- Application: kontact (5.20.3 (22.04.3)) Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.19.1-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: I closed knotact with ctrl-q and it crashed. Didn't see if it happens all the time. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #4 0x7face2b7d444 in QTabWidget::count() const (this=0x55b0692fced0) at widgets/qtabwidget.cpp:1212 #5 0x7fac5d60f56f in MessageList::Pane::PanePrivate::updateTabControls() () at /lib64/libKF5MessageList.so.5 #6 0x7face1d12e6f in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x77917340, r=0x55b066407c20, this=0x55b0665d04f0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #7 doActivate(QObject*, int, void**) (sender=0x55b0665ee7a0, signal_index=3, argv=0x77917340) at kernel/qobject.cpp:3886 #8 0x7face1896678 in KCoreConfigSkeleton::save() (this=0x55b0665ee7a0) at /usr/src/debug/kconfig-5.96.0-1.1.x86_64/src/core/kcoreconfigskeleton.cpp:1245 #9 0x7fac5d5bd058 in () at /lib64/libKF5MessageList.so.5 #10 0x7fac5d5bd516 in () at /lib64/libKF5MessageList.so.5 #11 0x7fac5d5e94e8 in () at /lib64/libKF5MessageList.so.5 #12 0x7fac5d617519 in MessageList::Widget::~Widget() () at /lib64/libKF5MessageList.so.5 #13 0x7face1d0532e in QObjectPrivate::deleteChildren() (this=this@entry=0x55b066345780) at kernel/qobject.cpp:2104 #14 0x7face29e2666 in QWidget::~QWidget() (this=0x55b0663d72d0, __in_chrg=) at kernel/qwidget.cpp:1522 #15 0x7face2b59f89 in QStackedWidget::~QStackedWidget() (this=0x55b0663d72d0, __in_chrg=) at widgets/qstackedwidget.cpp:147 #16 0x7face1d0532e in QObjectPrivate::deleteChildren() (this=this@entry=0x55b0664227f0) at kernel/qobject.cpp:2104 #17 0x7face29e2666 in QWidget::~QWidget() (this=0x55b066407c20, __in_chrg=) at kernel/qwidget.cpp:1522 #18 0x7fac5d97c6bd in CollectionPane::~CollectionPane() (this=0x55b066407c20, this=) at /usr/src/debug/kmail-22.04.3-1.1.x86_64/src/widgets/collectionpane.cpp:24 #19 CollectionPane::~CollectionPane() (this=0x55b066407c20, this=) at /usr/src/debug/kmail-22.04.3-1.1.x86_64/src/widgets/collectionpane.cpp:24 #20 0x7face1d0532e in QObjectPrivate::deleteChildren() (this=this@entry=0x55b066378410) at kernel/qobject.cpp:2104 #21 0x7face29e2666 in QWidget::~QWidget() (this=0x55b0666f9a90, __in_chrg=) at kernel/qwidget.cpp:1522 #22 0x7face2b55229 in QSplitter::~QSplitter() (this=0x55b0666f9a90, __in_chrg=) at widgets/qsplitter.cpp:979 #23 0x7face1d0532e in QObjectPrivate::deleteChildren() (this=this@entry=0x55b066698130) at kernel/qobject.cpp:2104 #24 0x7face29e2666 in QWidget::~QWidget() (this=0x55b0666f9a50, __in_chrg=) at kernel/qwidget.cpp:1522 #25 0x7face2b55229 in QSplitter::~QSplitter() (this=0x55b0666f9a50, __in_chrg=) at widgets/qsplitter.cpp:979 #26 0x7fac5d9c8cf3 in KMMainWidget::deleteWidgets() (this=this@entry=0x55b0663a07a0) at /usr/src/debug/kmail-22.04.3-1.1.x86_64/src/kmmainwidget.cpp:987 #27 0x7fac5d9cb9f6 in KMMainWidget::destruct() (this=0x55b0663a07a0) at /usr/src/debug/kmail-22.04.3-1.1.x86_64/src/kmmainwidget.cpp:395 #28 KMMainWidget::destruct() (this=0x55b0663a07a0) at /usr/src/debug/kmail-22.04.3-1.1.x86_64/src/kmmainwidget.cpp:384 #29 0x7facb8621c1f in KMailPart::~KMailPart() (this=0x55b0662d4640, this=) at /usr/src/debug/kmail-22.04.3-1.1.x86_64/src/kmail_part.cpp:89 #30 0x7facb8621d69 in KMailPart::~KMailPart() (this=0x55b0662d4640, this=) at /usr/src/debug/kmail-22.04.3-1.1.x86_64/src/kmail_part.cpp:92 #31 0x7face33468fe in KontactInterface::Plugin::~Plugin() (this=this@entry=0x55b0662d06b0, __vtt_parm=__vtt_parm@entry=0x7fac5dfa1b30 , this=, __vtt_parm=) at /usr/src/debug/kontactinterface-22.04.3-1.1.x86_64/src/plugin.cpp:74 #32 0x7fac5df8ed11 in KMailPlugin::~KMailPlugin() (this=0x55b0662d06b0, this=) at /usr/src/debug/kmail-22.04.3-1.1.x86_64/src/kontactplugin/kmail/kmail_plugin.cpp:145 #33 0x7fac5df8ed49 in KMailPlugin::~KMailPlugin() (this=0x55b0662d06b0, this=) at /usr/src/debug/kmail-22.04.3-1.1.x86_64/src/kontactplugin/kmail/kmail_plugin.cpp:145 #34 0x7face337b59e in qDeleteAll::const_iterator>(QList::const_iterator, QList::const_iterator) (end=..., begin=...) at /usr/include/qt5/QtCore/qalgorithms.h:320 #35 qDeleteAll >(QList
[kontact] [Bug 453037] New: on first start after log in, kmail starts all imap agents in "offline mode"
https://bugs.kde.org/show_bug.cgi?id=453037 Bug ID: 453037 Summary: on first start after log in, kmail starts all imap agents in "offline mode" Product: kontact Version: 5.19.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: mail Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. reboot or relogin to plasma 2. start kontact OBSERVED RESULT all imap connections are in offline mode EXPECTED RESULT I expect the imap ressources to be in online mode when the connection to the mailserver is available at startup time SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220424 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.2 Kernel Version: 5.17.4-1-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 449239] New: kmail treats background color of plaintext emails as html mail background
https://bugs.kde.org/show_bug.cgi?id=449239 Bug ID: 449239 Summary: kmail treats background color of plaintext emails as html mail background Product: kontact Version: 5.19.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: mail Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. configure kmails color settings as follows: [x] Eigene farben benutzen (use own colors) [X] Farbe der ursprünglichen HTML mail nicht ändern (don't change colors in html mails) 2. open a plaintext email OBSERVED RESULT The text is colord according to the customized colors but the background of a PLAINTEXT email is switched to white, making the whole mess unreadable in my case. EXPECTED RESULT I would expect kmail to change all colors, including the background, if the mail is plaintext only. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220125 KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.1-1-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics ADDITIONAL INFORMATION The problem here is using a Plasma-wide dark color scheme - you HAVE to have kmail adjust the colors, or mails will be unreadable. but there seems to be no working combination of these two options that works equally well with plaintext- and html emails. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 436256] New: kontact crashed on quit
https://bugs.kde.org/show_bug.cgi?id=436256 Bug ID: 436256 Summary: kontact crashed on quit Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- Application: kontact (5.17.0 (21.04.0)) Qt Version: 5.15.2 Frameworks Version: 5.81.0 Operating System: Linux 5.3.18-lp152.72-preempt x86_64 Windowing System: X11 Drkonqi Version: 5.21.4 Distribution: "openSUSE Leap 15.2" -- Information about the crash: - What I was doing when the application crashed: Kontact crashed as I closed the application - no error message of any kind, just crash. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #4 0x7f07661906f4 in QTabWidget::count() const (this=0x5572bd28ed30) at widgets/qtabwidget.cpp:1212 #5 0x7f06d175d9bf in MessageList::Pane::Private::updateTabControls() (this=0x5572bbb05510) at /usr/src/debug/messagelib-21.04.0-lp152.210.1.x86_64/messagelist/src/pane.cpp:846 #6 0x7f076505bb57 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffdb3314d10, r=0x5572bbba5890, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #7 doActivate(QObject*, int, void**) (sender=0x5572bb96cbb0, signal_index=3, argv=0x7ffdb3314d10) at kernel/qobject.cpp:3886 #8 0x7f0765055012 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x5572bb96cbb0, m=m@entry=0x7f0762909f20 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #9 0x7f07626bfc00 in KCoreConfigSkeleton::configChanged() (this=this@entry=0x5572bb96cbb0) at /usr/src/debug/kconfig-5.81.0-lp152.256.1.x86_64/build/src/core/KF5ConfigCore_autogen/EWIEGA46WW/moc_kcoreconfigskeleton.cpp:154 #10 0x7f07626e68ed in KCoreConfigSkeleton::save() (this=0x5572bb96cbb0) at /usr/src/debug/kconfig-5.81.0-lp152.256.1.x86_64/src/core/kcoreconfigskeleton.cpp:1244 #11 0x7f06d16f2668 in MessageList::Core::Manager::saveGlobalConfiguration() (this=0x5572bbc04360) at /usr/src/debug/messagelib-21.04.0-lp152.210.1.x86_64/messagelist/src/core/manager.cpp:943 #12 MessageList::Core::Manager::saveConfiguration() (this=this@entry=0x5572bbc04360) at /usr/src/debug/messagelib-21.04.0-lp152.210.1.x86_64/messagelist/src/core/manager.cpp:948 #13 0x7f06d16f2af7 in MessageList::Core::Manager::~Manager() (this=0x5572bbc04360, __in_chrg=) at /usr/src/debug/messagelib-21.04.0-lp152.210.1.x86_64/messagelist/src/core/manager.cpp:59 #14 0x7f06d16f2c09 in MessageList::Core::Manager::~Manager() (this=0x5572bbc04360, __in_chrg=) at /usr/src/debug/messagelib-21.04.0-lp152.210.1.x86_64/messagelist/src/core/manager.cpp:66 #15 0x7f06d16ee516 in MessageList::Core::Manager::unregisterWidget(MessageList::Core::Widget*) (pWidget=, pWidget@entry=0x5572bb9d3bd0) at /usr/src/debug/messagelib-21.04.0-lp152.210.1.x86_64/messagelist/src/core/manager.cpp:87 #16 0x7f06d173cd8d in MessageList::Core::Widget::~Widget() (this=0x5572bb9d3bd0, __in_chrg=) at /usr/src/debug/messagelib-21.04.0-lp152.210.1.x86_64/messagelist/src/core/widgetbase.cpp:152 #17 0x7f06d176aa39 in MessageList::Widget::~Widget() (this=0x5572bb9d3bd0, __in_chrg=) at /usr/src/debug/messagelib-21.04.0-lp152.210.1.x86_64/messagelist/src/widget.cpp:86 #18 0x7f076504edab in QObjectPrivate::deleteChildren() (this=this@entry=0x5572bb7f41c0) at kernel/qobject.cpp:2104 #19 0x7f0765fff576 in QWidget::~QWidget() (this=0x5572bbbaa730, __in_chrg=) at kernel/qwidget.cpp:1522 #20 0x7f076616dac9 in QStackedWidget::~QStackedWidget() (this=0x5572bbbaa730, __in_chrg=) at widgets/qstackedwidget.cpp:147 #21 0x7f076504edab in QObjectPrivate::deleteChildren() (this=this@entry=0x5572bbce6500) at kernel/qobject.cpp:2104 #22 0x7f0765fff576 in QWidget::~QWidget() (this=0x5572bbba5890, __in_chrg=) at kernel/qwidget.cpp:1522 #23 0x7f06d26b6d71 in CollectionPane::~CollectionPane() (this=0x5572bbba5890, __in_chrg=) at /usr/src/debug/kmail-21.04.0-lp152.185.1.x86_64/src/widgets/collectionpane.h:13 #24 CollectionPane::~CollectionPane() (this=0x5572bbba5890, __in_chrg=) at /usr/src/debug/kmail-21.04.0-lp152.185.1.x86_64/src/widgets/collectionpane.h:13 #25 0x7f076504edab in QObjectPrivate::deleteChildren() (this=this@entry=0x5572bbb80190) at kernel/qobject.cpp:2104 #26 0x7f0765fff576 in QWidget::~QWidget() (this=0x5572bbb643b0, __in_chrg=) at kernel/qwidget.cpp:1522 #27 0x7f076616ccb9 in QSplitter::~QSplitter() (this=0x5572bbb643b0, __in_chrg=) at widgets/qsplitter.cpp:979 #28 0x7f076504edab in QObjectPrivate::deleteChildren() (this=this@entry=0x5572bba7b1f0) at
[kontact] [Bug 435643] New: akonadi mail dispatcher agent fails to store the password for smtp auth permanently
https://bugs.kde.org/show_bug.cgi?id=435643 Bug ID: 435643 Summary: akonadi mail dispatcher agent fails to store the password for smtp auth permanently Product: kontact Version: 5.16.80 Platform: Other OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: mail Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY my mailaccounts all need smtp auth - kmail fails to remember the password, and then takes several minutes to time out and retry STEPS TO REPRODUCE 1. have a mail account that requires smtp auth 2. configure kmail accordingly 3. try to send mail OBSERVED RESULT kmail asks for the smtp password, then sits there for minutes doing nothing. Finally a pop up appears, saying "the remote has closed the connection", after that sending mail works fine until the next reboot. EXPECTED RESULT I would expect the checkbox "store password" to ... make kmail store the password. Also, I'd expect kmail to immediately retry the sending process, not after a timeout of several minutes. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.2 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Kernel Version: 5.3.18-lp152.69-default OS Type: 64-bit Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-4210U CPU @ 1.70GHz Memory: 15.6 GiB of RAM Graphics Processor: Mesa DRI Intel® Haswell Mobile ADDITIONAL INFORMATION - other email clients work fine with my server... thunderbird on windows or linux, android phones, k9mail on android, iphones, you name it, it works. Just kmail collapses on me. severity: grave because a mail client that can't send mail reliably is DEAD IN THE WATER. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 430652] New: Repeating tasks can't be created unless you put a start and due date in
https://bugs.kde.org/show_bug.cgi?id=430652 Bug ID: 430652 Summary: Repeating tasks can't be created unless you put a start and due date in Product: kontact Version: 5.16.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: calendar Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY I can't create a repeating task without a start and finish time and date STEPS TO REPRODUCE 1. create a task 2. do NOT specify a start and end time 3. try to set the task to repeat OBSERVED RESULT everything in the "repeats" tab is disabled EXPECTED RESULT I expect to be able to create a task that (for example) repeats every friday without giving it a start and end time. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.2 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 Kernel Version: 5.3.18-lp152.57-default OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4210U CPU @ 1.70GHz Memory: 15.6 GiB of RAM Graphics Processor: Mesa DRI Intel® Haswell Mobile ADDITIONAL INFORMATION calendar is stored in nextcloud -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 430651] New: Weekly repeating tasks can only be created on the weekday that they happen on
https://bugs.kde.org/show_bug.cgi?id=430651 Bug ID: 430651 Summary: Weekly repeating tasks can only be created on the weekday that they happen on Product: kontact Version: 5.16.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: calendar Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY Weekly repeating tasks can only be created on the day they repeat on STEPS TO REPRODUCE 1. create a task in kontact 2. Set start and due date to some day in the future 3. set it to repeat weekly OBSERVED RESULT The weekday that is "today" is always in the list of repetitions and can not be removed EXPECTED RESULT I expect to be able to create a task that repeats only on fridays on any day of the week, not just on fridays SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.2 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 Kernel Version: 5.3.18-lp152.57-default OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4210U CPU @ 1.70GHz Memory: 15.6 GiB of RAM Graphics Processor: Mesa DRI Intel® Haswell Mobile ADDITIONAL INFORMATION calendar is stored in nextcloud -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 377324] akonadi server crashed when trying to create a task in my calendar
https://bugs.kde.org/show_bug.cgi?id=377324 Mathias Homann changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #2 from Mathias Homann --- this has not happened anymore for a while... -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 403875] can't open https links
https://bugs.kde.org/show_bug.cgi?id=403875 Mathias Homann changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #5 from Mathias Homann --- I have akregator 5.15.3 here, and with some blogs, all links work and with some, http links don't... here's another test case: add this feed: http://seraphimsl.com/feed/atom/ and try out any links that point at urls like this: http://maps.secondlife.com/secondlife/Follys End/33/231/2001 those still don't work, I have to go the "log way around" and open the post and use the link from there. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 428714] New: kontact crash on exit
https://bugs.kde.org/show_bug.cgi?id=428714 Bug ID: 428714 Summary: kontact crash on exit Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- Application: kontact (5.15.2 (20.08.2)) Qt Version: 5.15.1 Frameworks Version: 5.75.0 Operating System: Linux 5.3.18-lp152.47-default x86_64 Windowing system: X11 Distribution: "openSUSE Leap 15.2" -- Information about the crash: - What I was doing when the application crashed: quitting kontact makes it crash - are my settings saved? ((I don't have anything else to say about it but I can't file the report unless this text is long enough which is weird.)) The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [New LWP 7637] [New LWP 7638] [New LWP 7645] [New LWP 7647] [New LWP 7653] [New LWP 7654] [New LWP 7655] [New LWP 7656] [New LWP 7657] [New LWP 7659] [New LWP 7660] [New LWP 7682] [New LWP 7684] [New LWP 7724] [New LWP 7726] [New LWP 8500] [New LWP 8501] [New LWP 8502] [New LWP 8503] [New LWP 8504] [New LWP 8505] [New LWP 8506] [New LWP 8507] [New LWP 8559] [New LWP 15423] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x7f7e03f206db in poll () from /lib64/libc.so.6 [Current thread is 1 (Thread 0x7f7e076bf480 (LWP 7631))] Thread 26 (Thread 0x7f7d13fff700 (LWP 15423)): #0 0x7f7df8b74bab in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f7dfd1d3f76 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x0d03 in () #3 0x098179f8 in () #4 0x0ce2 in () #5 0x098179f8 in () #6 0x in () Thread 25 (Thread 0x7f7d1bfff700 (LWP 8559)): #0 0x7f7df8b7487d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f7dfd1d3e8a in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x in () Thread 24 (Thread 0x7f7d36ffd700 (LWP 8507)): #0 0x7f7e03f25839 in syscall () at /lib64/libc.so.6 #1 0x7f7e046a38e4 in QtLinuxFutex::_q_futex(int*, int, int, unsigned long long, int*, int) (val3=0, addr2=0x0, val2=0, val=, op=0, addr=) at thread/qfutex_p.h:116 #2 0x7f7e046a38e4 in QtLinuxFutex::futexWait >(QBasicAtomicInteger&, QBasicAtomicInteger::Type) (expectedValue=, futex=...) at thread/qfutex_p.h:135 #3 0x7f7e046a38e4 in futexSemaphoreTryAcquire_loop(QBasicAtomicInteger&, unsigned long long, unsigned long long, int) (timeout=-1, nn=8589934593, curValue=, u=...) at thread/qsemaphore.cpp:219 #4 0x7f7e046a38e4 in futexSemaphoreTryAcquire(QBasicAtomicInteger&, int, int) (timeout=-1, n=, u=...) at thread/qsemaphore.cpp:262 #5 0x7f7e046a38e4 in QSemaphore::acquire(int) (this=0x7f7df9cc6900, n=) at thread/qsemaphore.cpp:326 #6 0x7f7df99ffa64 in () at /usr/lib64/libQt5Network.so.5 #7 0x7f7e046a14ac in QThreadPrivate::start(void*) (arg=0x7f7df9cc68e0) at thread/qthread_unix.cpp:329 #8 0x7f7df8b6e4f9 in start_thread () at /lib64/libpthread.so.0 #9 0x7f7e03f2afbf in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f7d377fe700 (LWP 8506)): #0 0x7f7df62afad4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f7df62641b1 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7f7df6264720 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f7df626488c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f7e048f9ddb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f7d48002de0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f7e04895eba in QEventLoop::exec(QFlags) (this=this@entry=0x7f7d377fdbb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:232 #6 0x7f7e0469ff97 in QThread::exec() (this=) at thread/qthread.cpp:547 #7 0x7f7e046a14ac in QThreadPrivate::start(void*) (arg=0x555fe9e7f8c0) at thread/qthread_unix.cpp:329 #8 0x7f7df8b6e4f9 in start_thread () at /lib64/libpthread.so.0 #9 0x7f7e03f2afbf in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f7d37fff700 (LWP 8505)): #0 0x7f7e03f206db in poll () at /lib64/libc.so.6 #1 0x7f7df6264779 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f7df626488c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f7e048f9ddb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f7d540031e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f7e04895eba in QEventLoop::exec(QFlags) (this=this@entry=0x7f7d37ffebb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:232 #5 0x7f7e0469ff97 in QThread::exec() (this=) at thread/qthread.cpp:547 #6 0x7f7e046a14ac in
[kontact] [Bug 428627] New: "Combined view" has stopped working
https://bugs.kde.org/show_bug.cgi?id=428627 Bug ID: 428627 Summary: "Combined view" has stopped working Product: kontact Version: 5.15.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: akregator Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY When I use "Combined view" for my feeds the window stays empty STEPS TO REPRODUCE 1. Set up akregator with many different feeds 2. Switch to "combined view" OBSERVED RESULT The view pane stays empty EXPECTED RESULT The view pane should display all new posts from one feed in one view SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.2 KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 Kernel Version: 5.3.18-lp152.47-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 31.3 GiB of RAM Graphics Processor: GeForce GTX 1050/PCIe/SSE2 ADDITIONAL INFORMATION Possible regression: it had happened one already almost a year ago, see #416114 which was never acted upon -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 427432] Weird message when sending mail
https://bugs.kde.org/show_bug.cgi?id=427432 --- Comment #6 from Mathias Homann --- ...it just got weird. I have two computers running plasma, on both kmail is configured the same way, on computer #2 i can't reproduce this. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 427432] Weird message when sending mail
https://bugs.kde.org/show_bug.cgi?id=427432 --- Comment #5 from Mathias Homann --- (In reply to stakanov.s from comment #4) > You said "TLS" so I suppose SSL/TLS on 587 as setting in Kmail as opposed to > STARTTLS? > > Just to avoid somebody else looses your time. ssl/tls on port 465. kmail autodetects it that way w/o problems. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 427432] Weird message when sending mail
https://bugs.kde.org/show_bug.cgi?id=427432 --- Comment #3 from Mathias Homann --- the mail server in question is my OWN mailserver, and I have not made any changes to it. The notification only showed up a few weeks ago after a huge KDE/Plasma upgrade. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 427432] Weird message when sending mail
https://bugs.kde.org/show_bug.cgi?id=427432 --- Comment #1 from Mathias Homann --- I found something to reproduce the weird "already authenticated" message. If I "fetch all mail" just before sending the message appears; If i don't, it doesnt (unless of course kmail had just now automatically fetched mail). -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 427432] New: Weird message when sending mail
https://bugs.kde.org/show_bug.cgi?id=427432 Bug ID: 427432 Summary: Weird message when sending mail Product: kontact Version: 5.15.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: mail Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY Every time I'm sending email I get a pop up that says: "5.5.1 Error: already authenticated", followed by another one that says "successfully sent" STEPS TO REPRODUCE 1. I don't know any other step than to send a mail... OBSERVED RESULT see above EXPECTED RESULT I'd expect EITHER sending to fail, OR to succeed, but not fail first, succeed right after... SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.2 KDE Plasma Version: 5.19.90 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 Kernel Version: 5.3.18-lp152.44-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 31.3 GiB of RAM Graphics Processor: GeForce GTX 1050/PCIe/SSE2 ADDITIONAL INFORMATION Email accounts are all IMAP, sending is smtp with TLS. No other mail client shows this weird behaviour, nothing on the server has been changed in years. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 422568] New: akonadiconsole crashes on exit
https://bugs.kde.org/show_bug.cgi?id=422568 Bug ID: 422568 Summary: akonadiconsole crashes on exit Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: akonadiconsole Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- Application: akonadiconsole (5.14.1 (20.04.0)) Qt Version: 5.15.0 Frameworks Version: 5.70.0 Operating System: Linux 4.12.14-lp151.28.48-default x86_64 Windowing system: X11 Distribution: "openSUSE Leap 15.1" -- Information about the crash: - What I was doing when the application crashed: when I quit akonadiconsole it crashes, so far this hs happened every time i tried. The crash can be reproduced every time. -- Backtrace: Application: Akonadi Console (akonadiconsole), signal: Segmentation fault [KCrash Handler] #4 0x7f56b4884d1c in qDeleteAll::const_iterator> (end=..., begin=...) at /usr/include/qt5/QtCore/qalgorithms.h:320 #5 qDeleteAll > (c=...) at /usr/include/qt5/QtCore/qalgorithms.h:328 #6 Breeze::ShadowHelper::~ShadowHelper (this=0x55867b817a40, __in_chrg=) at /usr/src/debug/breeze-5.18.90-lp151.291.3.x86_64/kstyle/breezeshadowhelper.cpp:105 #7 0x7f56b4884e49 in Breeze::ShadowHelper::~ShadowHelper (this=0x55867b817a40, __in_chrg=) at /usr/src/debug/breeze-5.18.90-lp151.291.3.x86_64/kstyle/breezeshadowhelper.cpp:106 #8 0x7f56b4893a16 in Breeze::Style::~Style (this=0x55867b815f10, __in_chrg=) at /usr/src/debug/breeze-5.18.90-lp151.291.3.x86_64/kstyle/breezestyle.cpp:200 #9 0x7f56b4893ad9 in Breeze::Style::~Style (this=0x55867b815f10, __in_chrg=) at /usr/src/debug/breeze-5.18.90-lp151.291.3.x86_64/kstyle/breezestyle.cpp:202 #10 0x7f56f6971c17 in QApplication::~QApplication (this=0x7ffc83f2cfb0, __in_chrg=) at kernel/qapplication.cpp:746 #11 0x55867a440172 in main (argc=, argv=) at /usr/src/debug/akonadiconsole-20.04.1-lp151.129.2.x86_64/src/main.cpp:39 [Inferior 1 (process 7650) detached] Possible duplicates by query: bug 422533, bug 422433, bug 422200, bug 422199, bug 422092. Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 420608] Unable to configure a default email format
https://bugs.kde.org/show_bug.cgi?id=420608 Mathias Homann changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED Ever confirmed|1 |0 --- Comment #14 from Mathias Homann --- user case: USer is using kmail for a work account and a private account, where the company policy dictates use of HTML in the .signature, but the user has plaintext inb the signature for his private account. now imagine these steps: - user sends a mail from his private account, switches to plaintext as the mail format - after this, user sends email from his work account, which due to the html signature hard enforces html format no matter what has been configured for the recipient in the contact entry - after this, user has to manually switch back to plaintext the next time he sends mail from the private account again. Can this be handled more intuitively? With less hassle for the user? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 420608] Unable to configure a default email format
https://bugs.kde.org/show_bug.cgi?id=420608 --- Comment #11 from Mathias Homann --- (In reply to Laurent Montel from comment #10) > wait info what info and from whom? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 420608] Unable to configure a default email format
https://bugs.kde.org/show_bug.cgi?id=420608 --- Comment #5 from Mathias Homann --- (In reply to xchain from comment #4) > Remembering rich text editing state per identity instead of globally sounds > like a good idea. that. > Whether or not this needs a checkbox in the identity settings dialog is a > different question. if it works reliably it would not need a checkbox at all... -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 420608] Unable to configure a default email format
https://bugs.kde.org/show_bug.cgi?id=420608 Mathias Homann changed: What|Removed |Added Resolution|NOT A BUG |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #2 from Mathias Homann --- unless you have HTML in your signature, in which case it goes quietly back to HTML. The setting should be remembered on a per identity basis, at least. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 420608] New: Unable to configure a default email format
https://bugs.kde.org/show_bug.cgi?id=420608 Bug ID: 420608 Summary: Unable to configure a default email format Product: kmail2 Version: 5.14.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY At some point in the past the default format for emails composed in kmail has changed to HTML, and I can NOT find any place to switch the default STEPS TO REPRODUCE 1. Open kmail preferences 2. Look at every single page in the settings dialog at least 15 times 3. Notice that there is no place to configure a default format for outgoing mails. There is one for displaying mails, though - just not for composing. OBSERVED RESULT See 3. above EXPECTED RESULT I would expect to find a checkbox on the "Editor preferences" page, or on the "create mails" page in the security area, to set the default for new mails to either HTML or plaintext. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.1 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 Kernel Version: 4.12.14-lp151.28.48-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 31,4 GiB ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 417907] New: Groupdav agent forgets password, or even all settings
https://bugs.kde.org/show_bug.cgi?id=417907 Bug ID: 417907 Summary: Groupdav agent forgets password, or even all settings Product: Akonadi Version: 5.13.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: DAV Resource Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY Sometimes the groupdav agent forgets all its configuration STEPS TO REPRODUCE 1. configure a groupdav agent, for example nextcloud 2. keep using it OBSERVED RESULT Eventually you might notice that calendar events or addressbook changes are not synced anymore. on closer inspection with akonadiconsole you will find the groupdav agent "stuck" at "0%", and when you configure it it has no password stored. BUT NO ERROR MESSAGES - JUST EXPECTED RESULT I'd expect the groupdav agent to either keep its settings tored reliably or TELL me when it needs something. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.1 KDE Plasma Version: 5.18.1 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 Kernel Version: 4.12.14-lp151.28.36-default OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4210U CPU @ 1.70GHz Memory: 15,6 GiB ADDITIONAL INFORMATION Actually putting the missing password in the settings des not even fix this: the only way to fix is to remove the agent and create a new one. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 416136] New: kontact crash on exit
https://bugs.kde.org/show_bug.cgi?id=416136 Bug ID: 416136 Summary: kontact crash on exit Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- Application: kontact (5.13.1 (19.12.1)) Qt Version: 5.14.0 Frameworks Version: 5.65.0 Operating System: Linux 4.12.14-lp151.28.36-default x86_64 Distribution: "openSUSE Leap 15.1" -- Information about the crash: - What I was doing when the application crashed: kontact crashed when I closed the application. No specific misbehaviour before that, other than the akregator issues I reported in https://bugs.kde.org/show_bug.cgi?id=416114 -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb37284ce40 (LWP 6103))] Thread 29 (Thread 0x7fb2c4d81700 (LWP 26976)): #0 0x7fb36ad65bdb in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb35fe106a6 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x0f55 in () #3 0x091d146f in () #4 0x0f34 in () #5 0x091d1857 in () #6 0x in () Thread 28 (Thread 0x7fb297fff700 (LWP 26478)): #0 0x7fb36ad65bdb in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb35fe106a6 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x0f55 in () #3 0x0c02401f in () #4 0x0f34 in () #5 0x0c024407 in () #6 0x in () Thread 27 (Thread 0x7fb2ad4cf700 (LWP 23264)): #0 0x7fb36ad65bdb in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb35fe106a6 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x0f55 in () #3 0x094a7e09 in () #4 0x0f34 in () #5 0x094a7e09 in () #6 0x in () Thread 26 (Thread 0x7fb2977fe700 (LWP 6579)): #0 0x7fb36ad658ad in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb35fe105ba in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x in () Thread 25 (Thread 0x7fb2a700 (LWP 6549)): #0 0x7fb36f033269 in syscall () at /lib64/libc.so.6 #1 0x7fb36f95ce94 in QSemaphore::acquire(int) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb36b48df74 in () at /usr/lib64/libQt5Network.so.5 #3 0x7fb36f95a93c in () at /usr/lib64/libQt5Core.so.5 #4 0x7fb36ad5f569 in start_thread () at /lib64/libpthread.so.0 #5 0x7fb36f0389ef in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7fb2b4c43700 (LWP 6548)): #0 0x7fb36f02e19b in poll () at /lib64/libc.so.6 #1 0x7fb36898f1a9 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb36898f2bc in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb36fba8a3b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fb36fb4803a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb36f959467 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fb36f95a93c in () at /usr/lib64/libQt5Core.so.5 #7 0x7fb36ad5f569 in start_thread () at /lib64/libpthread.so.0 #8 0x7fb36f0389ef in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7fb2b5444700 (LWP 6547)): #0 0x7fb36f029c98 in read () at /lib64/libc.so.6 #1 0x7fb3689d3ca0 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb36898ecb8 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb36898f150 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fb36898f2bc in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fb36fba8a3b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fb36fb4803a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fb36f959467 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7fb36f95a93c in () at /usr/lib64/libQt5Core.so.5 #9 0x7fb36ad5f569 in start_thread () at /lib64/libpthread.so.0 #10 0x7fb36f0389ef in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7fb2b5c45700 (LWP 6546)): #0 0x7fb36f029c98 in read () at /lib64/libc.so.6 #1 0x7fb3689d3ca0 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb36898ecb8 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb36898f150 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fb36898f2bc in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fb36fba8a3b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fb36fb4803a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fb36f959467 in QThread::exec() ()
[akregator] [Bug 416114] New: "Combined view" has stopped working
https://bugs.kde.org/show_bug.cgi?id=416114 Bug ID: 416114 Summary: "Combined view" has stopped working Product: akregator Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY The "combined view" is not working anymore STEPS TO REPRODUCE 1. use akregator with several rss feeds 2. switch to combined view OBSERVED RESULT The "View" stays blank EXPECTED RESULT The view should display all unread posts within the subtree of sources, as it used to SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.1 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0 Kernel Version: 4.12.14-lp151.28.36-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 31,4 GiB ADDITIONAL INFORMATION Plasma and apps are from opensuse build service, KDE: projects happens both with "standalone" akregator and with the kontact plugin. Also, akregator seems to have lost the feature to show unread entries only. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 416063] New: kontact does not take any mouse events inside the "client area" after start
https://bugs.kde.org/show_bug.cgi?id=416063 Bug ID: 416063 Summary: kontact does not take any mouse events inside the "client area" after start Product: kontact Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY I can't click on anything inside the kontact "shell" anymore STEPS TO REPRODUCE 1. start kontact 2. click on - for example - the mail icon in the vertical nav bar 3. nothing happens 4. use ctrl-2 on the keyboard 5. mail opens 6. press ctrl-1 to go back to the summary 7. now the stuff inside the "client area" is clickable OBSERVED RESULT see above EXPECTED RESULT kontact should work like it used to SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.1 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0 Kernel Version: 4.12.14-lp151.28.36-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 31,4 GiB ADDITIONAL INFORMATION KDE / Plasma from the opensuse build service KDE: repositories -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 415635] Kontact and all kdepim apps "look weird" and don't work right
https://bugs.kde.org/show_bug.cgi?id=415635 --- Comment #1 from Mathias Homann --- there's way more "weird behaviour": - akregator fails to load news sources - akregator fails to load the list of news sources - akregator UI buttons on the "main view" are not clickable, for example the "reload session" button that appears when you start akregator after an unclean quit -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 415634] kontact crash on opening settings
https://bugs.kde.org/show_bug.cgi?id=415634 --- Comment #1 from Mathias Homann --- the "other bug" I was referring to is #415635 -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 415635] New: Kontact and all kdepim apps "look weird" and don't work right
https://bugs.kde.org/show_bug.cgi?id=415635 Bug ID: 415635 Summary: Kontact and all kdepim apps "look weird" and don't work right Product: kdepim Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- Created attachment 124754 --> https://bugs.kde.org/attachment.cgi?id=124754=edit screenshot of kontact main screen next to system information window SUMMARY Kontact and all kdepim apps "look weird" and don't work right STEPS TO REPRODUCE Wish if I knew how to reproduce - my laptop has the same rpm packages installed and does not show the weird behaviours I'm seeing. OBSERVED RESULT kontact and the kdepim apps like kmail, korganizer, etc show several weird behaviours: - in kontact the vertical icon bar on the left is not working - in all kdepim apps the fonts are wrong (bigger, and not antialiased) - applications crash EXPECTED RESULT I'd expect the kdepim applications to "work normally" SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.1 KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0 Kernel Version: 4.12.14-lp151.28.36-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 31,4 GiB ADDITIONAL INFORMATION the computer where this is happening has a nvidia card with the nvidia blob driver, and ~/ on nfs - and kontact here takes several minutes to start the computer that works normally has intel onboard graphics with nvidia as secondary (optimus), and ~ on local ssd attached is a screenshot of kontact and the "about this system" popup to compare the fonts. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 415634] New: kontact crash on opening settings
https://bugs.kde.org/show_bug.cgi?id=415634 Bug ID: 415634 Summary: kontact crash on opening settings Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- Application: kontact (5.13.0 (19.12.0)) Qt Version: 5.14.0 Frameworks Version: 5.65.0 Operating System: Linux 4.12.14-lp151.28.36-default x86_64 Distribution: "openSUSE Leap 15.1" -- Information about the crash: - What I was doing when the application crashed: I was trying to find something in settings that would explain the weird kontact behaviour i'm experiencing, see other bug report (not filed yet). The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f90fb21fe40 (LWP 30428))] Thread 38 (Thread 0x7f900d7fa700 (LWP 31492)): #0 0x7f90f3739c66 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f90c6bd1714 in () at /usr/lib64/libnvidia-glcore.so.440.31 #2 0x7f90c69c46d0 in () at /usr/lib64/libnvidia-glcore.so.440.31 #3 0x7f90c69c5122 in () at /usr/lib64/libnvidia-glcore.so.440.31 #4 0x7f90c6bd08ec in () at /usr/lib64/libnvidia-glcore.so.440.31 #5 0x7f90f3733569 in start_thread () at /lib64/libpthread.so.0 #6 0x7f90f7a0c9ef in clone () at /lib64/libc.so.6 Thread 37 (Thread 0x7f900dffb700 (LWP 31491)): #0 0x7f90f3739c66 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f90c6bd1714 in () at /usr/lib64/libnvidia-glcore.so.440.31 #2 0x7f90c69c46d0 in () at /usr/lib64/libnvidia-glcore.so.440.31 #3 0x7f90c69c5122 in () at /usr/lib64/libnvidia-glcore.so.440.31 #4 0x7f90c6bd08ec in () at /usr/lib64/libnvidia-glcore.so.440.31 #5 0x7f90f3733569 in start_thread () at /lib64/libpthread.so.0 #6 0x7f90f7a0c9ef in clone () at /lib64/libc.so.6 Thread 36 (Thread 0x7f900e7fc700 (LWP 31490)): #0 0x7f90f3739c66 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f90c6bd1714 in () at /usr/lib64/libnvidia-glcore.so.440.31 #2 0x7f90c69c46d0 in () at /usr/lib64/libnvidia-glcore.so.440.31 #3 0x7f90c69c5122 in () at /usr/lib64/libnvidia-glcore.so.440.31 #4 0x7f90c6bd08ec in () at /usr/lib64/libnvidia-glcore.so.440.31 #5 0x7f90f3733569 in start_thread () at /lib64/libpthread.so.0 #6 0x7f90f7a0c9ef in clone () at /lib64/libc.so.6 Thread 35 (Thread 0x7f900effd700 (LWP 31489)): #0 0x7f90f3739c66 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f90c6bd1714 in () at /usr/lib64/libnvidia-glcore.so.440.31 #2 0x7f90c6c432ec in () at /usr/lib64/libnvidia-glcore.so.440.31 #3 0x7f90c69c51cd in () at /usr/lib64/libnvidia-glcore.so.440.31 #4 0x7f90c6bd08ec in () at /usr/lib64/libnvidia-glcore.so.440.31 #5 0x7f90f3733569 in start_thread () at /lib64/libpthread.so.0 #6 0x7f90f7a0c9ef in clone () at /lib64/libc.so.6 Thread 34 (Thread 0x7f900f7fe700 (LWP 31488)): #0 0x7f90f3739c66 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f90c6bd1714 in () at /usr/lib64/libnvidia-glcore.so.440.31 #2 0x7f90c69c46d0 in () at /usr/lib64/libnvidia-glcore.so.440.31 #3 0x7f90c69c5122 in () at /usr/lib64/libnvidia-glcore.so.440.31 #4 0x7f90c6bd08ec in () at /usr/lib64/libnvidia-glcore.so.440.31 #5 0x7f90f3733569 in start_thread () at /lib64/libpthread.so.0 #6 0x7f90f7a0c9ef in clone () at /lib64/libc.so.6 Thread 33 (Thread 0x7f900700 (LWP 31487)): #0 0x7f90f3739c66 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f90c6bd1714 in () at /usr/lib64/libnvidia-glcore.so.440.31 #2 0x7f90c69c46d0 in () at /usr/lib64/libnvidia-glcore.so.440.31 #3 0x7f90c69c5122 in () at /usr/lib64/libnvidia-glcore.so.440.31 #4 0x7f90c6bd08ec in () at /usr/lib64/libnvidia-glcore.so.440.31 #5 0x7f90f3733569 in start_thread () at /lib64/libpthread.so.0 #6 0x7f90f7a0c9ef in clone () at /lib64/libc.so.6 Thread 32 (Thread 0x7f9014c6e700 (LWP 31486)): #0 0x7f90f3739c66 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f90c6bd1714 in () at /usr/lib64/libnvidia-glcore.so.440.31 #2 0x7f90c69c46d0 in () at /usr/lib64/libnvidia-glcore.so.440.31 #3 0x7f90c69c5122 in () at /usr/lib64/libnvidia-glcore.so.440.31 #4 0x7f90c6bd08ec in () at /usr/lib64/libnvidia-glcore.so.440.31 #5 0x7f90f3733569 in start_thread () at /lib64/libpthread.so.0 #6 0x7f90f7a0c9ef in clone () at /lib64/libc.so.6 Thread 31 (Thread 0x7f901546f700 (LWP
[Akonadi] [Bug 414387] New: sometimes the akonadi dav ressource looses all configuration
https://bugs.kde.org/show_bug.cgi?id=414387 Bug ID: 414387 Summary: sometimes the akonadi dav ressource looses all configuration Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: DAV Resource Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. set up a dav ressource, i.e. a nextcloud account, for calendar and contacts 2. use it for some time 3. eventually you might notice that it is not syncing anymore 4. go to "configure natively" for that ressource in akonadiconsole OBSERVED RESULT the configuration is completely empty, no account information at all EXPECTED RESULT The account information should be persistent, and if it "disappears" there needs to be a message to the user. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.1 KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.1 Kernel Version: 4.12.14-lp151.28.32-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 31,4 GiB ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 403875] can't open https links
https://bugs.kde.org/show_bug.cgi?id=403875 --- Comment #2 from Mathias Homann --- now this is interesting. by now, https works, but http:// doesnt. for example, put this feed in akregator: http://blog.slinkstyle.com/feed/ in the latest post are two http: links pointing at yourtube, and one https: pointing at the gimp webpage. the gimp link works, the two videos don't. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405711] Kontact crash after chainging UI language
https://bugs.kde.org/show_bug.cgi?id=405711 Mathias Homann changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Mathias Homann --- yep, still reproduces with the latest kontact Version here now: Operating System: openSUSE Leap 15.0 KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 Kernel Version: 4.12.14-lp150.12.70-default OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4210U CPU @ 1.70GHz Memory: 15,6 GiB -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 411307] New: Akonadi agents can't properly handle file:/ urls
https://bugs.kde.org/show_bug.cgi?id=411307 Bug ID: 411307 Summary: Akonadi agents can't properly handle file:/ urls Product: Akonadi Version: 5.11.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libakonadi Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. set up a local notes ressource 2. create notes OBSERVED RESULT the local notes ressource seems to use the path ~/.local/share/notes/(id) but actually the notes are stored in this folder: /home/mathias/file:/home/mathias/.local/share/notes/kmUmffNWnL EXPECTED RESULT I expect the notes ressource to actually store the notes where it's configured to do so. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.0 KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 Kernel Version: 4.12.14-lp150.12.70-default OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4210U CPU @ 1.70GHz Memory: 15,6 GiB ADDITIONAL INFORMATION the mail agent for loca folders shows the same behaviour. also: it does not matter whether home is on NFS or local storage. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 411269] New: maildir ressource creates a folder named "file:" in my home
https://bugs.kde.org/show_bug.cgi?id=411269 Bug ID: 411269 Summary: maildir ressource creates a folder named "file:" in my home Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Maildir Resource Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. use kmail normally, i.e. send some mails OBSERVED RESULT you will find a folder named "file:" in your home which contains the full path to your local mail folders, for example "file:/users/lemmy/.local/share with "local-mail" and "local-mail.directory" in it. EXPECTED RESULT I would expect the maildir ressource to actually understand and handle a "file://" ressource properly SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.0 KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 Kernel Version: 4.12.14-lp150.12.70-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz Memory: 31,4 GiB ADDITIONAL INFORMATION - the "local notes" ressource does it too, so maybe it's a bug in a kio_ instead of the akonadi parts? -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 410752] korganizer should use "better" intervals for reminders
https://bugs.kde.org/show_bug.cgi?id=410752 --- Comment #6 from Mathias Homann --- (In reply to Laurent Montel from comment #5) > Do you think that it's ok for you to use same combobox in reminder dialog > box ? that would in my eyes be the perfect solution: why present the user with two different versions of the same question...? -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 410752] korganizer should use "better" intervals for reminders
https://bugs.kde.org/show_bug.cgi?id=410752 --- Comment #3 from Mathias Homann --- Created attachment 122040 --> https://bugs.kde.org/attachment.cgi?id=122040=edit screenshot of a reminder popup in kontact / korganizer notice how the only option for reminding again is to set it to wait a custom time. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 410752] korganizer should use "better" intervals for reminders
https://bugs.kde.org/show_bug.cgi?id=410752 --- Comment #2 from Mathias Homann --- Created attachment 122038 --> https://bugs.kde.org/attachment.cgi?id=122038=edit screenshot of a reminder popup in microsoft outlook see the choices for when to remind again of this appointment: there are two options that I would like to see in korganizer: "5 minutes before the appointment starts" and "0 hours before the appointment starts". -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 410752] New: korganizer should use "better" intervals for reminders
https://bugs.kde.org/show_bug.cgi?id=410752
Bug ID: 410752
Summary: korganizer should use "better" intervals for reminders
Product: korganizer
Version: 5.11.3
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: reminder daemon (korgac)
Assignee: kdepim-bugs@kde.org
Reporter: mathias.hom...@opensuse.org
Target Milestone: ---
SUMMARY
the current intervals for reminding you of appointments are less than useful
STEPS TO REPRODUCE
1. create a calendar entry with a reminder in the future
2. wait for the reminder
3. try to postpone the reminder to another point in the future
OBSERVED RESULT
you can choose reminders after any free time period which means you actually
have to do the math to figure out what to put in - also, to postpone a reminder
that was set to "15 minutes before the event" to "remind again in 48 hours" is
pretty crazy.
EXPECTED RESULT
I would prefer the same kind of reminder intervals that for example outlook
has:
"5 minutes before the event", "when the event starts", and the current free
form but not as "in X {minutes|hours|days}" but as " {minutes|hours|days}
before the event starts"
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Leap 15.0 X86_64
(available in About System)
KDE Plasma Version: 5.16.4
KDE Frameworks Version: 5.60.0
Qt Version: 5.13.0
--
You are receiving this mail because:
You are the assignee for the bug.
[Akonadi] [Bug 409853] akonadiserver runs dbinitializer even when db is already filled with data and dies
https://bugs.kde.org/show_bug.cgi?id=409853 Mathias Homann changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #4 from Mathias Homann --- yep, it's the same bug. *** This bug has been marked as a duplicate of bug 409753 *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409753] Duplicate column name 'version' QMYSQL
https://bugs.kde.org/show_bug.cgi?id=409753 Mathias Homann changed: What|Removed |Added CC||mathias.hom...@opensuse.org --- Comment #3 from Mathias Homann --- *** Bug 409853 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409853] akonadiserver runs dbinitializer even when db is already filled with data and dies
https://bugs.kde.org/show_bug.cgi?id=409853 --- Comment #1 from Mathias Homann --- this completely breaks all pim functionality for existing setups - I don't think this should be "normal" -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409853] New: akonadiserver runs dbinitializer even when db is already filled with data and dies
https://bugs.kde.org/show_bug.cgi?id=409853 Bug ID: 409853 Summary: akonadiserver runs dbinitializer even when db is already filled with data and dies Product: Akonadi Version: 5.11.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- on my desktop workstation, akonadi is configured to use a central mysql database on a database server (~ is on NFS, 'nuff said). Since 5.11.3 akonadi dies after the first setup, due to dbinitializer in this configuration not realizng that the DB is already initialized. STEPS TO REPRODUCE 1. do a fresh akonadi configuration using a mysql database on a different machine via tcp/ip, set up some akonadi agents as usual - imap, webdav calendar, google, etc 2. wait for akonadi to fill with data 3. log out (and maybe restart your desktop workstation to make sure all akonadi processes are stopped) 4. log back in OBSERVED RESULT akonadiserver is not running EXPECTED RESULT akonadiserver should be running SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION when running "akonadiserver --verbose" on a commandline: lemmy@kumiko:~> akonadiserver --verbose org.kde.pim.akonadiserver: Akonadi control process not found - aborting. org.kde.pim.akonadiserver: If you started akonadiserver manually, try 'akonadictl start' instead. org.kde.pim.akonadiserver: Starting up the Akonadi Server... org.kde.pim.akonadiserver: Found mysql_install_db: "/usr/bin/mysql_install_db" org.kde.pim.akonadiserver: Found mysqlcheck: "/usr/bin/mysqlcheck" org.kde.pim.akonadiserver: Using mysqld: "/usr/sbin/mysqld" org.kde.pim.akonadiserver: Database "lemmy_akonadi" opened using driver "QMYSQL" org.kde.pim.akonadiserver: Running DB initializer org.kde.pim.akonadiserver: checking table "SchemaVersionTable" org.kde.pim.akonadiserver: "ALTER TABLE SchemaVersionTable ADD COLUMN version INTEGER NOT NULL DEFAULT 0" org.kde.pim.akonadiserver: "\nSql error: Duplicate column name 'version' QMYSQL: Unable to execute query\nQuery: ALTER TABLE SchemaVersionTable ADD COLUMN version INTEGER NOT NULL DEFAULT 0" org.kde.pim.akonadiserver: Unable to initialize database. org.kde.pim.akonadiserver: terminating connection threads org.kde.pim.akonadiserver: terminating service threads org.kde.pim.akonadiserver: Shutting down "NotificationManager" ... org.kde.pim.akonadiserver: stopping db process lemmy@kumiko:~> akonadiserver --version akonadiserver 5.11.3 lemmy@kumiko:~> Observe the dbinitializer trying to add a column to a table where that column already exists. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405711] Kontact crash after chainging UI language
https://bugs.kde.org/show_bug.cgi?id=405711 --- Comment #1 from Mathias Homann --- switching to US english instead of UK english worked fine. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 405711] New: Kontact crash after chainging UI language
https://bugs.kde.org/show_bug.cgi?id=405711 Bug ID: 405711 Summary: Kontact crash after chainging UI language Product: kontact Version: 5.10.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- Application: kontact (5.10.3) Qt Version: 5.12.2 Frameworks Version: 5.56.0 Operating System: Linux 4.12.14-lp150.12.48-default x86_64 Distribution: "openSUSE Leap 15.0" -- Information about the crash: I changed the interface language for kontact from german (my desktop default) to english (UK), now it crashes on start. Can't even reset that switch. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7facf410a940 (LWP 16943))] Thread 17 (Thread 0x7fabdd05a700 (LWP 16971)): #0 0x7facec4f389d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7face15e23d9 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7face15e2e4c in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7face15e2edf in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7face159ea58 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7face15a1526 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7face15a18c4 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7face15e5311 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7facec4ed559 in start_thread () from /lib64/libpthread.so.0 #9 0x7facf09fb81f in clone () from /lib64/libc.so.6 Thread 16 (Thread 0x7fabdd85b700 (LWP 16970)): #0 0x7facf0a0897c in __lll_lock_wait_private () from /lib64/libc.so.6 #1 0x7facf0a0a6d4 in __fprintf_chk () from /lib64/libc.so.6 #2 0x7facd90d507d in event_logv_ () from /usr/lib64/libevent-2.1.so.6 #3 0x7facd90d5214 in event_warn () from /usr/lib64/libevent-2.1.so.6 #4 0x7facd90d6b3c in ?? () from /usr/lib64/libevent-2.1.so.6 #5 0x7facd90cc7e4 in event_base_loop () from /usr/lib64/libevent-2.1.so.6 #6 0x7face15e91a4 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7face157c38b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7face15b0368 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #9 0x7face15e5311 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #10 0x7facec4ed559 in start_thread () from /lib64/libpthread.so.0 #11 0x7facf09fb81f in clone () from /lib64/libc.so.6 Thread 15 (Thread 0x7fac5700 (LWP 16967)): #0 0x7facec4f389d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7facda2fd7a4 in ?? () from /usr/lib64/libQt5Script.so.5 #2 0x7facda2fd7e9 in ?? () from /usr/lib64/libQt5Script.so.5 #3 0x7facec4ed559 in start_thread () from /lib64/libpthread.so.0 #4 0x7facf09fb81f in clone () from /lib64/libc.so.6 Thread 14 (Thread 0x7fac9c8bb700 (LWP 16965)): #0 0x7facf09f107b in poll () from /lib64/libc.so.6 #1 0x7facb0142831 in ?? () from /usr/lib64/libpulse.so.0 #2 0x7facb01341f0 in pa_mainloop_poll () from /usr/lib64/libpulse.so.0 #3 0x7facb0134880 in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0 #4 0x7facb0134910 in pa_mainloop_run () from /usr/lib64/libpulse.so.0 #5 0x7facb0142779 in ?? () from /usr/lib64/libpulse.so.0 #6 0x7fac9d5ce438 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-11.1.so #7 0x7facec4ed559 in start_thread () from /lib64/libpthread.so.0 #8 0x7facf09fb81f in clone () from /lib64/libc.so.6 Thread 13 (Thread 0x7fac9d575700 (LWP 16964)): #0 0x7facf09ecc0b in write () from /lib64/libc.so.6 #1 0x7facf097e19d in _IO_file_write@@GLIBC_2.2.5 () from /lib64/libc.so.6 #2 0x7facf097d47f in new_do_write () from /lib64/libc.so.6 #3 0x7facf097e95e in __GI__IO_file_xsputn () from /lib64/libc.so.6 #4 0x7facf09548db in buffered_vfprintf () from /lib64/libc.so.6 #5 0x7facf0951b4e in vfprintf () from /lib64/libc.so.6 #6 0x7facf0a0a726 in __fprintf_chk () from /lib64/libc.so.6 #7 0x7facd90d507d in event_logv_ () from /usr/lib64/libevent-2.1.so.6 #8 0x7facd90d5214 in event_warn () from /usr/lib64/libevent-2.1.so.6 #9 0x7facd90d6b3c in ?? () from /usr/lib64/libevent-2.1.so.6 #10 0x7facd90cc7e4 in event_base_loop () from /usr/lib64/libevent-2.1.so.6 #11 0x7face15e9061 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #12 0x7face157c38b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #13 0x7face15b0368 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #14 0x7face15e5311 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #15 0x7facec4ed559 in start_thread () from /lib64/libpthread.so.0 #16
[akregator] [Bug 403875] New: can't open https links
https://bugs.kde.org/show_bug.cgi?id=403875 Bug ID: 403875 Summary: can't open https links Product: akregator Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: internal browser Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- SUMMARY https:// links in feed entries do not work, clicking them does not open the link STEPS TO REPRODUCE 1. have any blog or such in your feeds that has https:// links in the entries 2. click those links OBSERVED RESULT nothing happens EXPECTED RESULT web page should open in the configured browser SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Leap 15.0 KDE Plasma Version: 5.14.90 KDE Frameworks Version: 5.54.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION Clicking a https link with the **right** mousebutton and selecting either of the two options to open the link **does** work. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 368769] kontact crashes on exit
https://bugs.kde.org/show_bug.cgi?id=368769 Mathias Homann changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #2 from Mathias Homann --- (In reply to Erik Quaeghebeur from comment #1) > Is this still happening? not right now... closing, will reopen if it starts crashing again. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 399752] New: kontact crash while using akregator
https://bugs.kde.org/show_bug.cgi?id=399752 Bug ID: 399752 Summary: kontact crash while using akregator Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- Application: kontact (5.9.2) Qt Version: 5.11.2 Frameworks Version: 5.50.0 Operating System: Linux 4.12.14-lp150.12.19-default x86_64 Distribution: "openSUSE Leap 15.0" -- Information about the crash: - What I was doing when the application crashed: Looking at blog posts using akregator, specifically https://akashasternberg.wordpress.com/2018/10/13/news-and-updates-that-hopefully-will-not-scare-you-silly/ fetched from the RSS feed at http://iheartsl.com/ -- Backtrace: Application: Kontact (kontact), signal: Bus error Using host libthread_db library "/lib64/libthread_db.so.1". 184 return currentThreadData; [Current thread is 1 (Thread 0x7f3c911ec900 (LWP 26404))] Thread 45 (Thread 0x7f3ad6494700 (LWP 2933)): #0 0x7f3c89a99bcb in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3c7ecd25f7 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f3c7ecd3b57 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f3c7ecd3c42 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f3c7ecd8cc1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f3c7ecda05f in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f3c7ece4c61 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f3c89a93559 in start_thread () at /lib64/libpthread.so.0 #8 0x7f3c8db4982f in clone () at /lib64/libc.so.6 Thread 44 (Thread 0x7f3ad6c95700 (LWP 2928)): #0 0x7f3c89a99bcb in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3c7ecd25f7 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f3c7ecd3b57 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f3c7ecd3c42 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f3c7ecd8cc1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f3c7ecda05f in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f3c7ece4c61 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f3c89a93559 in start_thread () at /lib64/libpthread.so.0 #8 0x7f3c8db4982f in clone () at /lib64/libc.so.6 Thread 43 (Thread 0x7f3adcb5d700 (LWP 2927)): #0 0x7f3c89a99bcb in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3c7ecd25f7 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f3c7ecd3b57 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f3c7ecd3c42 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f3c7ecd8cc1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f3c7ecda249 in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f3c7ece4c61 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f3c89a93559 in start_thread () at /lib64/libpthread.so.0 #8 0x7f3c8db4982f in clone () at /lib64/libc.so.6 Thread 42 (Thread 0x7f3b2e115700 (LWP 2926)): #0 0x7f3c89a99bcb in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3c7ecd25f7 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f3c7ecd3b57 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f3c7ecd3c42 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f3c7ecd8cc1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f3c7ecda249 in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f3c7ece4c61 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f3c89a93559 in start_thread () at /lib64/libpthread.so.0 #8 0x7f3c8db4982f in clone () at /lib64/libc.so.6 Thread 41 (Thread 0x7f3adf3e3700 (LWP 2910)): #0 0x7f3c89a99bcb in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f3c7ecd25f7 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f3c7ecd3b57 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f3c7ecd3c42 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f3c7ecd8cc1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f3c7ecda249 in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f3c7ece4c61 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f3c89a93559 in start_thread () at /lib64/libpthread.so.0 #8 0x7f3c8db4982f in clone () at /lib64/libc.so.6 Thread 40 (Thread 0x7f3c3dffb700 (LWP 2296)): [KCrash Handler] #6 0x7f3c8dbab49e in __memmove_avx_unaligned_erms () at /lib64/libc.so.6 #7 0x7f3c7fa11ae5 in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f3c7fa4f704 in () at /usr/lib64/libQt5WebEngineCore.so.5 #9 0x7f3c7fa4ff6d in () at /usr/lib64/libQt5WebEngineCore.so.5 #10 0x7f3c7fa77004 in () at /usr/lib64/libQt5WebEngineCore.so.5 #11 0x7f3c7fa7c980 in
[kaddressbook] [Bug 397233] New: kaddressbook 5.8.80 beta1 presets the category filter with something unusable on start
https://bugs.kde.org/show_bug.cgi?id=397233 Bug ID: 397233 Summary: kaddressbook 5.8.80 beta1 presets the category filter with something unusable on start Product: kaddressbook Version: GIT Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org CC: to...@kde.org Target Milestone: --- When i start kontact or kaddressbook "standalone", the category filter always is preset to something that does not even exist as a category in my address book, therefor making the list of addresses appear empty. Workaround: click the "clear category filter" button, which sets the filter to "All". It seems that the list of categories got populated from the categories in my CALENDAR, it contains a lot og categories that I used in calendar entries, but never for addresses -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 394879] kontact: weird startup error
https://bugs.kde.org/show_bug.cgi?id=394879 --- Comment #9 from Mathias Homann --- ...am I the only one who thinks the current version number mess is less than useful? Plasma is ...what, 5.13 with the next release, the app framework is 18.4.2 withe the next release, the apps themselves are what, 5.8.2, or whaever else the developer picks -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 394879] kontact: weird startup error
https://bugs.kde.org/show_bug.cgi?id=394879 --- Comment #7 from Mathias Homann --- 5.8.2 of what... kontact? in KDE:Applications on openSUSE build service there is a kontact 18.04.1 ... -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 394879] kontact: weird startup error
https://bugs.kde.org/show_bug.cgi?id=394879 --- Comment #5 from Mathias Homann --- yep, it's QT 5.11 in there. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 394879] kontact: weird startup error
https://bugs.kde.org/show_bug.cgi?id=394879 --- Comment #4 from Mathias Homann --- no idea, actually, i guess whichever qt version is in KDE:Qt5 which according to the OBS docs is the one to use together with KDE:Frameworks5... gotta have a look. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 394879] kontact: weird startup error
https://bugs.kde.org/show_bug.cgi?id=394879 --- Comment #2 from Mathias Homann --- (In reply to Mathias Homann from comment #0) > Created attachment 112972 [details] > Screenshot of the popup in question > > Since the latest opensuse updates to clarify: I'm running openSUSE Leap 42.3, and Plasma 5 from the opensuse buildservice repositories (KDE:Qt5, KDE:Frameworks5, KDE:Applications). -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 394879] New: kontact: weird startup error
https://bugs.kde.org/show_bug.cgi?id=394879 Bug ID: 394879 Summary: kontact: weird startup error Product: kontact Version: 5.8.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- Created attachment 112972 --> https://bugs.kde.org/attachment.cgi?id=112972=edit Screenshot of the popup in question Since the latest opensuse updates I get a very weird popup every time I start kontact (see attachment). After I click "OK" on it, kontact works normally. Pasting the html from the popup directly into the address line of a webbrowser shows that the page that kontact wants to show me is some kind of first run welcome page (see attachment 2) -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 394879] kontact: weird startup error
https://bugs.kde.org/show_bug.cgi?id=394879 --- Comment #1 from Mathias Homann --- Created attachment 112973 --> https://bugs.kde.org/attachment.cgi?id=112973=edit scxreenshot of the interpreted html -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 174977] clicking on system tray icon doesn't open the relevant kontact part
https://bugs.kde.org/show_bug.cgi?id=174977 --- Comment #34 from Mathias Homann <mathias.hom...@opensuse.org> --- Still happens to me. The way I use kontact gives me a kmail icon in the tray, and a akregator icon. Clicking on either one when kontact is hidden brings it up with the kontact part active that was active when I minimized kontact. Kontact 5.5.2 from openSUSE rpms. Plasma is 5.10.2, Frameworks is 5.35.0. Whatever happened to "kde-config --version"? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 381015] kmail often fails to remove mails from folders when multiple mails are moved or deleted
https://bugs.kde.org/show_bug.cgi?id=381015 --- Comment #2 from Mathias Homann <mathias.hom...@opensuse.org> --- I'm not sure about that, this one is more like the total opposite, the message content disappears from the preview area but the list stays what it was. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 381015] New: kmail often fails to remove mails from folders when multiple mails are moved or deleted
https://bugs.kde.org/show_bug.cgi?id=381015 Bug ID: 381015 Summary: kmail often fails to remove mails from folders when multiple mails are moved or deleted Product: kmail2 Version: 5.5.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: commands and actions Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- Sometimes when I delete or move multiple emails from the same folder, kmail copies the mails into the destination, but does NOT remove them from the source folder... but when I look in the source folder with any other imap client (i.e. thunderbird) the mails are actually gone from the source folder, just not in kmail. workaround exists: quit kmail / kontact, restart the akonadi server, then run akonadictl fsck and akonadictl vacuum. and yes I DO CONSIDER THIS A GRAVE BUG. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 377324] New: akonadi server crashed when trying to create a task in my calendar
https://bugs.kde.org/show_bug.cgi?id=377324 Bug ID: 377324 Summary: akonadi server crashed when trying to create a task in my calendar Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- Application: akonadiserver (5.4.2) Qt Version: 5.8.0 Frameworks Version: 5.31.0 Operating System: Linux 4.4.49-16-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: I tried to create a task in my calendar. Akonadi server crashed as soon as the edit task window came up. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe9e4673780 (LWP 9800))] Thread 41 (Thread 0x7fe90f7fe700 (LWP 11710)): #0 0x7fe9e23f451d in read () from /lib64/libc.so.6 #1 0x7fe9dd436073 in ?? () from /usr/lib64/tls/libnvidia-tls.so.375.39 #2 0x7fe9df1b3670 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe9df172e49 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #4 0x7fe9df1732a8 in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x7fe9df17342c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #6 0x7fe9e2f088ab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7fe9e2eb86ab in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #8 0x7fe9e2d009aa in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #9 0x7fe9e2d05019 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #10 0x7fe9e1275734 in start_thread () from /lib64/libpthread.so.0 #11 0x7fe9e2400d3d in clone () from /lib64/libc.so.6 Thread 40 (Thread 0x7fe90700 (LWP 11678)): #0 0x7fe9e23f451d in read () from /lib64/libc.so.6 #1 0x7fe9dd436073 in ?? () from /usr/lib64/tls/libnvidia-tls.so.375.39 #2 0x7fe9df1b3670 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe9df172e49 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #4 0x7fe9df1732a8 in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x7fe9df17342c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #6 0x7fe9e2f088ab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7fe9e2eb86ab in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #8 0x7fe9e2d009aa in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #9 0x7fe9e2d05019 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #10 0x7fe9e1275734 in start_thread () from /lib64/libpthread.so.0 #11 0x7fe9e2400d3d in clone () from /lib64/libc.so.6 Thread 39 (Thread 0x7fe930ff9700 (LWP 11676)): #0 0x7fe9e127ca6c in __lll_lock_wait () from /lib64/libpthread.so.0 #1 0x7fe9e12777eb in pthread_mutex_lock () from /lib64/libpthread.so.0 #2 0x7fe9de22de7c in ?? () from /usr/X11R6/lib64/libGL.so.1 #3 0x7fe9de232db1 in ?? () from /usr/X11R6/lib64/libGL.so.1 #4 0x7fe9de23326b in ?? () from /usr/X11R6/lib64/libGL.so.1 #5 0x7fe9dd4360f1 in ?? () from /usr/lib64/tls/libnvidia-tls.so.375.39 #6 0x7fe9df1b3670 in ?? () from /usr/lib64/libglib-2.0.so.0 #7 0x7fe9df172e49 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #8 0x7fe9df1732a8 in ?? () from /usr/lib64/libglib-2.0.so.0 #9 0x7fe9df17342c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #10 0x7fe9e2f088ab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #11 0x7fe9e2eb86ab in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #12 0x7fe9e2d009aa in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #13 0x7fe9e2d05019 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #14 0x7fe9e1275734 in start_thread () from /lib64/libpthread.so.0 #15 0x7fe9e2400d3d in clone () from /lib64/libc.so.6 Thread 38 (Thread 0x7fe972ffd700 (LWP 11652)): #0 0x7fe9e127ca6c in __lll_lock_wait () from /lib64/libpthread.so.0 #1 0x7fe9e12777eb in pthread_mutex_lock () from /lib64/libpthread.so.0 #2 0x7fe9de22de7c in ?? () from /usr/X11R6/lib64/libGL.so.1 #3 0x7fe9de232db1 in ?? () from /usr/X11R6/lib64/libGL.so.1 #4 0x7fe9de23326b in ?? () from /usr/X11R6/lib64/libGL.so.1 #5 0x7fe9dd4360f1 in ?? () from /usr/lib64/tls/libnvidia-tls.so.375.39 #6 0x7fe9df1b3670 in ?? () from /usr/lib64/libglib-2.0.so.0 #7 0x7fe9df172e49 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #8 0x7fe9df1732a8 in ?? () from /usr/lib64/libglib-2.0.so.0 #9 0x7fe9df17342c in
[kontact] [Bug 372282] New: Kontact crash on start
https://bugs.kde.org/show_bug.cgi?id=372282 Bug ID: 372282 Summary: Kontact crash on start Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- Application: kontact (5.3.0 (QtWebEngine)) Qt Version: 5.6.2 Frameworks Version: 5.26.0 Operating System: Linux 4.1.34-33-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Sometimes kontact crashes when you start it and it's not the first time after login. The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fecd6624800 (LWP 19512))] Thread 51 (Thread 0x7feb79466700 (LWP 31251)): #0 0x7fecd306ebfd in poll () at /lib64/libc.so.6 #1 0x7fecce370e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fecce370f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fecd3b9719b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fecd3b44bbb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fecd397ff5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fecd3984a29 in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #7 0x7feccefb10a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7fecd307702d in clone () at /lib64/libc.so.6 Thread 50 (Thread 0x7feb79e9d700 (LWP 31249)): #0 0x7fecce36e213 in () at /usr/lib64/libglib-2.0.so.0 #1 0x7fecce37044b in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7fecce370d80 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fecce370f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fecd3b9719b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fecd3b44bbb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fecd397ff5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fecd3984a29 in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #8 0x7feccefb10a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fecd307702d in clone () at /lib64/libc.so.6 Thread 49 (Thread 0x7feb9abed700 (LWP 31246)): #0 0x7fecce3b2d14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fecce370d73 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fecce370f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fecd3b9719b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fecd3b44bbb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fecd397ff5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fecd3984a29 in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #7 0x7feccefb10a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7fecd307702d in clone () at /lib64/libc.so.6 Thread 48 (Thread 0x7febaaffd700 (LWP 31230)): #0 0x7fecd306ebfd in poll () at /lib64/libc.so.6 #1 0x7fecce370e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fecce370f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fecd3b9719b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fecd3b44bbb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fecd397ff5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fecd3984a29 in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #7 0x7feccefb10a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7fecd307702d in clone () at /lib64/libc.so.6 Thread 47 (Thread 0x7febab7fe700 (LWP 31223)): #0 0x7fecd306ebfd in poll () at /lib64/libc.so.6 #1 0x7fecce370e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fecce370f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fecd3b9719b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fecd3b44bbb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fecd397ff5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fecd3984a29 in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #7 0x7feccefb10a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7fecd307702d in clone () at /lib64/libc.so.6 Thread 46 (Thread 0x7febc22de700 (LWP 31222)): #0 0x7fecd3b970d5 in postEventSourcePrepare(_GSource*, int*) () at /usr/lib64/libQt5Core.so.5 #1 0x7fecce3704ad in g_main_context_prepare () at
[kontact] [Bug 368769] New: kontact crashes on exit
https://bugs.kde.org/show_bug.cgi?id=368769 Bug ID: 368769 Summary: kontact crashes on exit Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org Application: kontact (5.2.3) Qt Version: 5.7.0 Frameworks Version: 5.26.0 Operating System: Linux 4.1.31-30-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Quitting kontact with ctrl-q or via the menu A lot of times kontact crashes when I quit the app. I can't think of anything else special that I'm doing in such a case, other than quitting the app... The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f96d2d60800 (LWP 4991))] Thread 16 (Thread 0x7f95d17fa700 (LWP 5068)): #0 0x7f96c70b3d10 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f96c7071759 in g_main_context_query () at /usr/lib64/libglib-2.0.so.0 #2 0x7f96c7071dcf in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f96c7071f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f96d0546f7b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f95e0006d00, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f96d04f68cb in QEventLoop::exec(QFlags) (this=this@entry=0x7f95d17f9dd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #6 0x7f96d033d06a in QThread::exec() (this=) at thread/qthread.cpp:507 #7 0x7f96d0341899 in QThreadPrivate::start(void*) (arg=0x1576390) at thread/qthread_unix.cpp:344 #8 0x7f96c8d880a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f96cfa3302d in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7f95d27fc700 (LWP 5066)): #0 0x7f96cfa2abfd in poll () at /lib64/libc.so.6 #1 0x7f96c7071e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f96c7071f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f96d0546f7b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f95cc004c20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f96d04f68cb in QEventLoop::exec(QFlags) (this=this@entry=0x7f95d27fbdd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #5 0x7f96d033d06a in QThread::exec() (this=) at thread/qthread.cpp:507 #6 0x7f96d0341899 in QThreadPrivate::start(void*) (arg=0x1679d50) at thread/qthread_unix.cpp:344 #7 0x7f96c8d880a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f96cfa3302d in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7f95d2ffd700 (LWP 5065)): #0 0x7f96c70b3cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f96c70714b9 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f96c7071d80 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f96c7071f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f96d0546f7b in QEventDispatcherGlib::processEvents(QFlags) (this=0x14548a0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f96d04f68cb in QEventLoop::exec(QFlags) (this=this@entry=0x7f95d2ffcdd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #6 0x7f96d033d06a in QThread::exec() (this=) at thread/qthread.cpp:507 #7 0x7f96d0341899 in QThreadPrivate::start(void*) (arg=0x1425330) at thread/qthread_unix.cpp:344 #8 0x7f96c8d880a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f96cfa3302d in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7f95d37fe700 (LWP 5064)): #0 0x7f96cfa26ccd in read () at /lib64/libc.so.6 #1 0x7f96c70b2b60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f96c7071999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f96c7071df8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f96c7071f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f96d0546f7b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f95d8004820, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f96d04f68cb in QEventLoop::exec(QFlags) (this=this@entry=0x7f95d37fddd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #7 0x7f96d033d06a in QThread::exec() (this=) at thread/qthread.cpp:507 #8 0x7f96d0341899 in QThreadPrivate::start(void*) (arg=0x1425890) at thread/qthread_unix.cpp:344 #9 0x7f96c8d880a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f96cfa3302d in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7f95d3fff700 (LWP 5063)): #0 0x7f96cfa2abfd in poll () at /lib64/libc.so.6 #1 0x7f96c7071e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f96c7071f7c in
[Akonadi] [Bug 301182] Mail dispatcher agent stops working
https://bugs.kde.org/show_bug.cgi?id=301182 --- Comment #12 from Mathias Homann <mathias.hom...@opensuse.org> --- it didn't happen for quite some time, but what still happens is that mail is being sent but still keeps sitting in my local outbox after it has been sent. the only way to be sure is to look in the sent mail folder for the account. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[akregator] [Bug 305494] Akregator always claims it wasn't closed correctly
https://bugs.kde.org/show_bug.cgi?id=305494 --- Comment #9 from Mathias Homann mathias.hom...@opensuse.org --- same here - ever so often this comes back, sometimes with no discernible reason, sometimes because kontact crashed on exit which it does ever so often. please reopen. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 348365] New: imap ressource crashes on start
https://bugs.kde.org/show_bug.cgi?id=348365 Bug ID: 348365 Summary: imap ressource crashes on start Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: mathias.hom...@opensuse.org CC: kdepim-bugs@kde.org, vkra...@kde.org Application: akonadi_imap_resource (4.14) KDE Platform Version: 4.14.6 Qt Version: 4.8.6 Operating System: Linux 3.16.7-21-desktop x86_64 Distribution: openSUSE 13.2 (Harlequin) (x86_64) -- Information about the crash: - What I was doing when the application crashed: Doing nothing in particular, I had just logged into KDE and was getting ready to do things. Akonadi was starting up, strangely enough only this one instance crashed, the other imap ressources are working fine. - Unusual behavior I noticed: nothing unusual. The crash can be reproduced every time. -- Backtrace: Application: le...@megatokyo.de vom Typ IMAP-E-Mail-Server (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7fe4740867c0 (LWP 7098))] Thread 3 (Thread 0x7fe460ba4700 (LWP 7100)): #0 0x7fff2b911d18 in () #1 0x in () Thread 2 (Thread 0x7fe45bfff700 (LWP 7689)): #0 0x7fe46f9fac5d in poll () at /lib64/libc.so.6 #1 0x7fe46e982be4 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe46e982cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe4736dc0de in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () at /usr/lib64/libQtCore.so.4 #4 0x7fe4736ade6f in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () at /usr/lib64/libQtCore.so.4 #5 0x7fe4736ae165 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () at /usr/lib64/libQtCore.so.4 #6 0x7fe4735ab0bf in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x7fe4735ad79f in () at /usr/lib64/libQtCore.so.4 #8 0x7fe46f0670a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fe46fa0308d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fe4740867c0 (LWP 7098)): [KCrash Handler] #5 0x7fe47131764d in KIMAP::SearchJob::handleResponse(KIMAP::Message const) () at /usr/lib64/libkimap.so.4 #6 0x7fe471307ddc in KIMAP::SessionPrivate::responseReceived(KIMAP::Message const) () at /usr/lib64/libkimap.so.4 #7 0x7fe4736c759e in QObject::event(QEvent*) () at /usr/lib64/libQtCore.so.4 #8 0x7fe472a4876c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #9 0x7fe472a4ecad in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #10 0x7fe470b5ecea in KApplication::notify(QObject*, QEvent*) () at /usr/lib64/libkdeui.so.5 #11 0x7fe4736af2ad in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQtCore.so.4 #12 0x7fe4736b257d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQtCore.so.4 #13 0x7fe4736dc8fe in () at /usr/lib64/libQtCore.so.4 #14 0x7fe46e982a04 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #15 0x7fe46e982c48 in () at /usr/lib64/libglib-2.0.so.0 #16 0x7fe46e982cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #17 0x7fe4736dc0be in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () at /usr/lib64/libQtCore.so.4 #18 0x7fe472ae5676 in () at /usr/lib64/libQtGui.so.4 #19 0x7fe4736ade6f in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () at /usr/lib64/libQtCore.so.4 #20 0x7fe4736ae165 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () at /usr/lib64/libQtCore.so.4 #21 0x7fe4736b35b9 in QCoreApplication::exec() () at /usr/lib64/libQtCore.so.4 #22 0x7fe473b99283 in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () at /usr/lib64/libakonadi-kde.so.4 #23 0x00419f53 in _start () The reporter indicates this bug may be a duplicate of or related to bug 348319. Possible duplicates by query: bug 348319, bug 345748, bug 345229, bug 344828, bug 344805. Reported using DrKonqi -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 348365] imap ressource crashes on start
https://bugs.kde.org/show_bug.cgi?id=348365 --- Comment #1 from Mathias Homann mathias.hom...@opensuse.org --- Created attachment 92888 -- https://bugs.kde.org/attachment.cgi?id=92888action=edit New crash information added by DrKonqi akonadi_imap_resource (4.14) on KDE Platform 4.14.6 using Qt 4.8.6 the imap ressource keeps crashing, but it is the only one that does that. I have several other imap accounts in akonadi all on the same server that work fine. I have already run a reconstruct on the imap server, didn't help. -- Backtrace (Reduced): #5 0x7f276f1c564d in KIMAP::SearchJob::handleResponse(KIMAP::Message const) () at /usr/lib64/libkimap.so.4 #6 0x7f276f1b5ddc in KIMAP::SessionPrivate::responseReceived(KIMAP::Message const) () at /usr/lib64/libkimap.so.4 #7 0x7f277157559e in QObject::event(QEvent*) () at /usr/lib64/libQtCore.so.4 #8 0x7f27708f676c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #9 0x7f27708fccad in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 348365] imap ressource crashes on start
https://bugs.kde.org/show_bug.cgi?id=348365 Mathias Homann mathias.hom...@opensuse.org changed: What|Removed |Added CC||mathias.hom...@opensuse.org -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 310437] Wish for a ActiveSync resource in akonadi for full Exchange compatibility
https://bugs.kde.org/show_bug.cgi?id=310437 --- Comment #7 from Mathias Homann mathias.hom...@opensuse.org --- no, ActiveSync and MAPI are not the same. Mapi only lets you access email on an exchange server, ActiveSync actually synchronises mail, calendar, addressbook and tasklist between your device and the exchange server. For a reference implementation see the activesync part in android. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail] [Bug 139308] kmail sometimes doesnt recognize mailing list headers
https://bugs.kde.org/show_bug.cgi?id=139308 --- Comment #10 from Mathias Homann mathias.hom...@opensuse.org --- hm.. it still does not work for me here. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[akregator] [Bug 305494] Akregator always claims it wasn't closed correctly
https://bugs.kde.org/show_bug.cgi?id=305494 Mathias Homann mathias.hom...@opensuse.org changed: What|Removed |Added CC||mathias.hom...@opensuse.org --- Comment #6 from Mathias Homann mathias.hom...@opensuse.org --- appeared for me in KDE 4.11.1 after rebuilding my ~/.kde4 settings folder from scratch. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 310437] Wish for a ActiveSync resource in akonadi for full Exchange compatibility
https://bugs.kde.org/show_bug.cgi?id=310437 Mathias Homann mathias.hom...@opensuse.org changed: What|Removed |Added CC||mathias.hom...@opensuse.org --- Comment #1 from Mathias Homann mathias.hom...@opensuse.org --- seconded. Right now I'm in the process of switching my mail/calendar/addressbook to thunderbird with lightning and the SOGO connector, because guess what, my employer uses exchange. And I'd rather use one mail app, not two. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 310437] Wish for a ActiveSync resource in akonadi for full Exchange compatibility
https://bugs.kde.org/show_bug.cgi?id=310437 --- Comment #2 from Mathias Homann mathias.hom...@opensuse.org --- and speaking of thunderbird, there are two not all that large addons, that let TB access all that is under exchange... -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 318274] New: The german menu in kmail has a typo
https://bugs.kde.org/show_bug.cgi?id=318274 Bug ID: 318274 Summary: The german menu in kmail has a typo Classification: Unclassified Product: kmail2 Version: 4.10.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org The german menu in kmail has a typo: File - Empty all trash folders in german shows as Alle Papierkorb löschen but Papierkorb is singular.. the correct form would be Alle Papierkörbe löschen. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 311674] Cannot authorize google ressources with my google account
https://bugs.kde.org/show_bug.cgi?id=311674 --- Comment #2 from Mathias Homann mathias.hom...@opensuse.org --- works ok now -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 301182] Mail dispatcher agent stops working
https://bugs.kde.org/show_bug.cgi?id=301182 --- Comment #3 from Mathias Homann mathias.hom...@opensuse.org --- would be nice if this got some attention... still around in 4.10.1 :( -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 312927] New: kontact summary sorts events by some unknown order; should sort by time
https://bugs.kde.org/show_bug.cgi?id=312927 Bug ID: 312927 Summary: kontact summary sorts events by some unknown order; should sort by time Classification: Unclassified Product: kontact Version: 4.9.5 Hardware: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: summary Assignee: kdepim-bugs@kde.org Reporter: mathias.hom...@opensuse.org I have the contact summary show upcoming events, and it seems to sort them by calendar... I think the upcoming events piece should sort all events just by time. Reproducible: Always Steps to Reproduce: 1. use more than one calendar 2. make sure they all have more than one event for the same day 3. observe the weird sorting order in kontact summary Actual Results: events should simply be sorted by time Expected Results: events seem to be sorted by calendar first, and *then* by time -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 308122] After some weeks downtime, google calendar fetch fails. The requested minimum modification time lies too far in the past
https://bugs.kde.org/show_bug.cgi?id=308122 Mathias Homann mathias.hom...@opensuse.org changed: What|Removed |Added CC||mathias.hom...@opensuse.org --- Comment #1 from Mathias Homann mathias.hom...@opensuse.org --- I'm having the very same thing, whenever I use an account on my laptop that I only use once every few weeks. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 288605] Mail Dispatcher Agent went offline for unknown reason
https://bugs.kde.org/show_bug.cgi?id=288605 Mathias Homann mathias.hom...@opensuse.org changed: What|Removed |Added CC||mathias.hom...@opensuse.org --- Comment #1 from Mathias Homann mathias.hom...@opensuse.org --- I'm having the same issues in KDE 4.9.4 here. After a few hours of working with my computer the mail dispatcher simply stops working and needs to be restarted. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 311674] New: Cannot authorize google ressources with my google account
https://bugs.kde.org/show_bug.cgi?id=311674 Bug ID: 311674 Severity: major Version: 4.9 Priority: NOR CC: kdepim-bugs@kde.org Assignee: dvra...@redhat.com Summary: Cannot authorize google ressources with my google account Classification: Unclassified OS: Linux Reporter: mathias.hom...@opensuse.org Hardware: openSUSE RPMs Status: UNCONFIRMED Component: Google Resource Product: Akonadi When I try to create a new google ressource, i get to add a google account, so i get a window that lets me login on google... but then the Allow and Deny buttons are not clickable. Reproducible: Always Steps to Reproduce: 1. delete all google ressources 2. create a new one 3. remove all google accounts; add a new one Actual Results: impossible to authorize the ressource Expected Results: it should work -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 301182] Mail dispatcher agent stops working
https://bugs.kde.org/show_bug.cgi?id=301182 --- Comment #1 from Mathias Homann mathias.hom...@opensuse.org --- this bug is still present in 4.9.2 and annoys me to no end. possible duplicates: https://bugs.kde.org/show_bug.cgi?id=306203 https://bugs.kde.org/show_bug.cgi?id=288605 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 308064] New: Load external references setting on a folder is not completely evaluated
https://bugs.kde.org/show_bug.cgi?id=308064 Bug ID: 308064 Severity: normal Version: 4.9.2 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Load external references setting on a folder is not completely evaluated Classification: Unclassified OS: Linux Reporter: mathias.hom...@opensuse.org Hardware: Other Status: UNCONFIRMED Component: general Product: kmail2 I have one folder where I allow HTML mails, and external references. Therefor I set the flags for those two settings in the Folder menu accordingly. Since KDE 4.9.2, the HTML flag still works, but the load external references flag doesn't, I get mails displayed with placeholders. What's more, when I switch that flag off, and back on, I get to see the external images, but I still get the Click here to enable external references header displayed on top of the email. Reproducible: Always Steps to Reproduce: 1. Set up a folder for HTML mail with external refs 2. put somesuch mails in there 3. set the folder flags in the folder menu 4. open a mail in that folder, observe the external references not being loaded, or being loaded but in either case you always see the Click here to enable external references headerbox. Actual Results: see steps Expected Results: I would expect the click here to... to go away after I enable external references. I would also expect the feature to work right away after starting kontact. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 132090] the move message to folder dialog is too crowded
https://bugs.kde.org/show_bug.cgi?id=132090 Mathias Homann mathias.hom...@opensuse.org changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #14 from Mathias Homann mathias.hom...@opensuse.org --- nope, the move to dialog is fine in KMail 2 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 230443] spellchecker needs more options to ignore things
https://bugs.kde.org/show_bug.cgi?id=230443 --- Comment #3 from Mathias Homann mathias.hom...@opensuse.org --- can't really say anything about that, to me it seems that the spell check on *my kde installation here* does not work at all right now 0.o -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 259949] Kmail does not use all addressbooks for autocompletion
https://bugs.kde.org/show_bug.cgi?id=259949 Mathias Homann mathias.hom...@opensuse.org changed: What|Removed |Added CC||mathias.hom...@opensuse.org --- Comment #132 from Mathias Homann mathias.hom...@opensuse.org --- kde 4.8.4, bug still exists. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 301182] New: Mail dispatcher agent stops working
https://bugs.kde.org/show_bug.cgi?id=301182 Bug ID: 301182 Severity: major Version: unspecified Priority: NOR CC: vkra...@kde.org Assignee: kdepim-bugs@kde.org Summary: Mail dispatcher agent stops working Classification: Unclassified OS: Linux Reporter: mathias.hom...@opensuse.org Hardware: openSUSE RPMs Status: UNCONFIRMED Component: Mail Dispatcher Agent Product: Akonadi The mail dispatcher agent stops working after some random (longer) time, leading to mails sitting in the outbox until you restart the mail dispatcher in akonadiconsole. Reproducible: Always Steps to Reproduce: 1. log in to KDE 2. use your KDE session for several hours without relogging 3. try to send a mail Actual Results: mail sits in outbox until forever Expected Results: Mail should actually be sent -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 301182] Mail dispatcher agent stops working
https://bugs.kde.org/show_bug.cgi?id=301182 Mathias Homann mathias.hom...@opensuse.org changed: What|Removed |Added CC||mia.hom...@eregion.de -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 139308] kmail sometimes doesnt recognize mailing list headers
https://bugs.kde.org/show_bug.cgi?id=139308 Mathias Homann mathias.hom...@opensuse.org changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- --- Comment #3 from Mathias Homann mathias.hom...@opensuse.org --- I'm still experiencing this bug. Attached is an example mail. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 139308] kmail sometimes doesnt recognize mailing list headers
https://bugs.kde.org/show_bug.cgi?id=139308 --- Comment #4 from Mathias Homann mathias.hom...@opensuse.org --- Created attachment 71079 -- https://bugs.kde.org/attachment.cgi?id=71079action=edit one email in mbox format that does not get recognized as coming from a mailinglist -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 139308] kmail sometimes doesnt recognize mailing list headers
https://bugs.kde.org/show_bug.cgi?id=139308 --- Comment #5 from Mathias Homann mathias.hom...@opensuse.org --- I'm running KDE 4.8.3: @nb-20:~ kmail --version Qt: 4.8.1 KDE: 4.8.3 (4.8.3) release 503 KMail: 4.8.3 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 139308] kmail sometimes doesnt recognize mailing list headers
https://bugs.kde.org/show_bug.cgi?id=139308 --- Comment #7 from Mathias Homann mathias.hom...@opensuse.org --- My problem is, it does not always work, or not. It's erratic. I restart kmail, and it works with a list email that failed to get recognized before. The success rate is roughly 20% though, makes it a real pain when you have to setup kmail/kontact on a fresh kde setup. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 299482] groupdav calendar sync fails with unknown error code 0
https://bugs.kde.org/show_bug.cgi?id=299482 --- Comment #2 from Mathias Homann ad...@eregion.de --- I updated another computer to KDE 4.8.3, and I get the same popups. This is getting annoying. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 299482] groupdav calendar sync fails with unknown error code 0
https://bugs.kde.org/show_bug.cgi?id=299482 --- Comment #3 from Mathias Homann ad...@eregion.de --- I have build a kdepim runtime package with this changeset removed: https://projects.kde.org/projects/kde/kdepim-runtime/repository/revisions/77d63ae37d53a811785978a450e6f722dbb9655e/diff/resources/dav/protocols/carddavprotocol.cpp the error seems to be fixed with that. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 299482] groupdav calendar sync fails with unknown error code 0
https://bugs.kde.org/show_bug.cgi?id=299482 --- Comment #4 from Mathias Homann ad...@eregion.de --- (In reply to comment #3) I have build a kdepim runtime package with this changeset removed: https://projects.kde.org/projects/kde/kdepim-runtime/repository/revisions/ 77d63ae37d53a811785978a450e6f722dbb9655e/diff/resources/dav/protocols/ carddavprotocol.cpp the error seems to be fixed with that. After some trying out I can confirm that removing this changeset also removes the weird errors. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 299482] groupdav calendar sync fails with unknown error code 0
https://bugs.kde.org/show_bug.cgi?id=299482 --- Comment #5 from Mathias Homann ad...@eregion.de --- I have two user accounts on the same computer. User 1 is completely local, and akonadi operates on a per-user local mysql instance, and the bug happens. The interesting part is user 2, which uses a central mysql server for akonadi because its home directory is on nfs... and the bug does **not** happen. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 299482] New: groupdav calendar sync fails with unknown error code 0
https://bugs.kde.org/show_bug.cgi?id=299482 Bug ID: 299482 Severity: normal Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: groupdav calendar sync fails with unknown error code 0 Classification: Unclassified OS: Linux Reporter: ad...@eregion.de Hardware: openSUSE RPMs Status: UNCONFIRMED Component: DAV Resource Product: Akonadi every 5 minutes or so I get a popup from akonadi telling me that syncing from my owncloud calendar failed with unknown error code 0. Guys... return code 0 means it worked fine, not something went wrong... I looked at the debugger output in akonadiconsole, and there are no errors showing. prior to upgrading to kde 4.8.3 everything worked. Reproducible: Always Steps to Reproduce: 1. use akonadi with owncloud calendars -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
