[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email
https://bugs.kde.org/show_bug.cgi?id=374734 Andreas K. Huettel changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||dilfri...@gentoo.org Ever confirmed|0 |1 --- Comment #13 from Andreas K. Huettel --- Same phenomenon here as described by original submitter, here with Gentoo. * randomly, kmail does not delete an e-mail * when leaving kmail and then stopping akonadi, akonadi crashes. Backtrace: Application: akonadiserver (akonadiserver), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". pthread_cond_timedwait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 [Current thread is 1 (Thread 0x7f8b76e62780 (LWP 32690))] Thread 19 (Thread 0x7f8b6cfc5700 (LWP 32691)): #0 0x7f8b73242b79 in g_mutex_lock (mutex=mutex@entry=0x7f8b68000990) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gthread-posix.c:1336 #1 0x7f8b731fd6c2 in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f8b680210c0, timeout=-1, context=0x7f8b68000990) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:4223 #2 g_main_context_iterate (context=context@entry=0x7f8b68000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3924 #3 0x7f8b731fd7ec in g_main_context_iteration (context=0x7f8b68000990, may_block=1) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3990 #4 0x7f8b766f369c in QEventDispatcherGlib::processEvents (this=0x7f8b680008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #5 0x7f8b766a6d9a in QEventLoop::exec (this=this@entry=0x7f8b6cfc4e10, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f8b765001f4 in QThread::exec (this=this@entry=0x7f8b769a9b00 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:507 #7 0x7f8b7693b445 in QDBusConnectionManager::run (this=0x7f8b769a9b00 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #8 0x7f8b7650478c in QThreadPrivate::start (arg=0x7f8b769a9b00 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:368 #9 0x7f8b74c72454 in start_thread (arg=0x7f8b6cfc5700) at pthread_create.c:333 #10 0x7f8b75c3a5dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 18 (Thread 0x7f8b6768d700 (LWP 32700)): #0 0x7f8b75c314fd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f8b731fd6dc in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f8b60295560, timeout=3330855, context=0x7f8b6990) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:4228 #2 g_main_context_iterate (context=context@entry=0x7f8b6990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3924 #3 0x7f8b731fd7ec in g_main_context_iteration (context=0x7f8b6990, may_block=1) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3990 #4 0x7f8b766f369c in QEventDispatcherGlib::processEvents (this=0x7f8b68c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #5 0x7f8b766a6d9a in QEventLoop::exec (this=this@entry=0x7f8b6768ce40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f8b765001f4 in QThread::exec (this=) at thread/qthread.cpp:507 #7 0x7f8b7650478c in QThreadPrivate::start (arg=0x2010e80) at thread/qthread_unix.cpp:368 #8 0x7f8b74c72454 in start_thread (arg=0x7f8b6768d700) at pthread_create.c:333 #9 0x7f8b75c3a5dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 17 (Thread 0x7f8b66e8c700 (LWP 32713)): #0 0x7f8b75c314fd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f8b731fd6dc in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f8b58003020, timeout=3330881, context=0x7f8b58000990) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:4228 #2 g_main_context_iterate (context=context@entry=0x7f8b58000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3924 #3 0x7f8b731fd7ec in g_main_context_iteration (context=0x7f8b58000990, may_block=1) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3990 #4 0x7f8b766f369c in QEventDispatcherGlib::processEvents (this=0x7f8b580008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #5 0x7f8b766a6d9a in QEventLoop::exec (this=this@entry=0x7f8b66e8be40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f8b765001f4 in QThread::exec (this=) at thread/qthread.cp
[kmail2] [Bug 350219] Kmail can't create IMAP top level folders
https://bugs.kde.org/show_bug.cgi?id=350219 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org Platform|Kubuntu Packages|Gentoo Packages Version|5.1.3 |5.4.1 --- Comment #15 from Andreas K. Huettel --- Same effect on Gentoo, kmail 5.4.1 New top-level IMAP folders cannot be created in kmail / kontact. Creating one in akonadiconsole works fine. Updating the bug data to show it's still current / applicable -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.
https://bugs.kde.org/show_bug.cgi?id=341143 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org --- Comment #243 from Andreas K. Huettel --- Missing this feature as well. Please reconsider. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 356634] Kmail Randomly Hangs On Email Deletion
https://bugs.kde.org/show_bug.cgi?id=356634 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 350219] Kmail can't create IMAP top level folders
https://bugs.kde.org/show_bug.cgi?id=350219 Andreas K. Huettel changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #21 from Andreas K. Huettel --- Definitely not fixed in 17.04.2, symptoms remain exactly the same. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 419882] New: reproducible kontact (or akonadiconsole) crash when viewing one specific mail
https://bugs.kde.org/show_bug.cgi?id=419882 Bug ID: 419882 Summary: reproducible kontact (or akonadiconsole) crash when viewing one specific mail Product: kontact Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: dilfri...@gentoo.org Target Milestone: --- Application: kontact (5.13.3 (19.12.3)) Qt Version: 5.14.1 Frameworks Version: 5.67.0 Operating System: Linux 5.4.30-gentoo-ah1 x86_64 Distribution: "Gentoo Base System release 2.6" -- Information about the crash: - What I was doing when the application crashed: Opened a specific e-mail by clicking on it in the folder contents list. The same crash occurs when I click on the mail in akondadiconsole. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f680832e340 (LWP 30909))] Thread 42 (Thread 0x7f6733fff700 (LWP 31047)): #0 0x7f6818d64f2c in read () at /lib64/libc.so.6 #1 0x7f681756646f in g_wakeup_acknowledge () at /usr/lib64/libglib-2.0.so.0 #2 0x7f681751f83e in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f681751fcb2 in g_main_context_iterate.isra () at /usr/lib64/libglib-2.0.so.0 #4 0x7f681751fe2f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f6819390a6b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f681933b56b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f681919033e in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f681919136b in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #9 0x7f6817e72fa7 in start_thread () at /lib64/libpthread.so.0 #10 0x7f6818d73d3f in clone () at /lib64/libc.so.6 Thread 41 (Thread 0x7f6745dac700 (LWP 31016)): #0 0x7f6817e79635 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f681189a57c in base::ConditionVariable::Wait() () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x in () Thread 40 (Thread 0x7f67471eb700 (LWP 31010)): #0 0x7f6817e79635 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6805f44823 in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f6805f7 in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f6817e72fa7 in start_thread () at /lib64/libpthread.so.0 #4 0x7f6818d73d3f in clone () at /lib64/libc.so.6 Thread 39 (Thread 0x7f6747fff700 (LWP 30995)): #0 0x7f6817e79635 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6805f44823 in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f6805f7 in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f6817e72fa7 in start_thread () at /lib64/libpthread.so.0 #4 0x7f6818d73d3f in clone () at /lib64/libc.so.6 Thread 38 (Thread 0x7f675ccbd700 (LWP 30993)): #0 0x7f6817e79635 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6805f44823 in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f6805f7 in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f6817e72fa7 in start_thread () at /lib64/libpthread.so.0 #4 0x7f6818d73d3f in clone () at /lib64/libc.so.6 Thread 37 (Thread 0x7f675e187700 (LWP 30976)): #0 0x7f681751f27b in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #1 0x7f681751fc36 in g_main_context_iterate.isra () at /usr/lib64/libglib-2.0.so.0 #2 0x7f681751fe2f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f6819390a6b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f681933b56b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f681919033e in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f681919136b in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #7 0x7f6817e72fa7 in start_thread () at /lib64/libpthread.so.0 #8 0x7f6818d73d3f in clone () at /lib64/libc.so.6 Thread 36 (Thread 0x7f675ef44700 (LWP 30966)): #0 0x7f681756a904 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f681751fd03 in g_main_context_iterate.isra () at /usr/lib64/libglib-2.0.so.0 #2 0x7f681751fe2f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f6819390a6b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f681933b56b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f681919033e in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f681919136b in Q
[kdelibs] [Bug 180051] [KDE4] Need a way to have default printer settings
https://bugs.kde.org/show_bug.cgi?id=180051 Andreas K. Huettel changed: What|Removed |Added CC|dilfri...@gentoo.org| -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 397316] akonadi loses connection with IMAP server after suspend (but not only, DB error too)
https://bugs.kde.org/show_bug.cgi?id=397316 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.
https://bugs.kde.org/show_bug.cgi?id=341143 Andreas K. Huettel changed: What|Removed |Added CC|dilfri...@gentoo.org| -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 Andreas K. Huettel changed: What|Removed |Added CC|dilfri...@gentoo.org| -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 350219] Kmail can't create IMAP top level folders
https://bugs.kde.org/show_bug.cgi?id=350219 Andreas K. Huettel changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #21 from Andreas K. Huettel --- Definitely not fixed in 17.04.2, symptoms remain exactly the same. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 374734] Akonadiserver Crashes While Deleting Email
https://bugs.kde.org/show_bug.cgi?id=374734 Andreas K. Huettel changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||dilfri...@gentoo.org Ever confirmed|0 |1 --- Comment #13 from Andreas K. Huettel --- Same phenomenon here as described by original submitter, here with Gentoo. * randomly, kmail does not delete an e-mail * when leaving kmail and then stopping akonadi, akonadi crashes. Backtrace: Application: akonadiserver (akonadiserver), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". pthread_cond_timedwait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 [Current thread is 1 (Thread 0x7f8b76e62780 (LWP 32690))] Thread 19 (Thread 0x7f8b6cfc5700 (LWP 32691)): #0 0x7f8b73242b79 in g_mutex_lock (mutex=mutex@entry=0x7f8b68000990) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gthread-posix.c:1336 #1 0x7f8b731fd6c2 in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f8b680210c0, timeout=-1, context=0x7f8b68000990) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:4223 #2 g_main_context_iterate (context=context@entry=0x7f8b68000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3924 #3 0x7f8b731fd7ec in g_main_context_iteration (context=0x7f8b68000990, may_block=1) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3990 #4 0x7f8b766f369c in QEventDispatcherGlib::processEvents (this=0x7f8b680008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #5 0x7f8b766a6d9a in QEventLoop::exec (this=this@entry=0x7f8b6cfc4e10, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f8b765001f4 in QThread::exec (this=this@entry=0x7f8b769a9b00 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:507 #7 0x7f8b7693b445 in QDBusConnectionManager::run (this=0x7f8b769a9b00 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #8 0x7f8b7650478c in QThreadPrivate::start (arg=0x7f8b769a9b00 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:368 #9 0x7f8b74c72454 in start_thread (arg=0x7f8b6cfc5700) at pthread_create.c:333 #10 0x7f8b75c3a5dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 18 (Thread 0x7f8b6768d700 (LWP 32700)): #0 0x7f8b75c314fd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f8b731fd6dc in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f8b60295560, timeout=3330855, context=0x7f8b6990) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:4228 #2 g_main_context_iterate (context=context@entry=0x7f8b6990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3924 #3 0x7f8b731fd7ec in g_main_context_iteration (context=0x7f8b6990, may_block=1) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3990 #4 0x7f8b766f369c in QEventDispatcherGlib::processEvents (this=0x7f8b68c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #5 0x7f8b766a6d9a in QEventLoop::exec (this=this@entry=0x7f8b6768ce40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f8b765001f4 in QThread::exec (this=) at thread/qthread.cpp:507 #7 0x7f8b7650478c in QThreadPrivate::start (arg=0x2010e80) at thread/qthread_unix.cpp:368 #8 0x7f8b74c72454 in start_thread (arg=0x7f8b6768d700) at pthread_create.c:333 #9 0x7f8b75c3a5dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 17 (Thread 0x7f8b66e8c700 (LWP 32713)): #0 0x7f8b75c314fd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f8b731fd6dc in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f8b58003020, timeout=3330881, context=0x7f8b58000990) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:4228 #2 g_main_context_iterate (context=context@entry=0x7f8b58000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3924 #3 0x7f8b731fd7ec in g_main_context_iteration (context=0x7f8b58000990, may_block=1) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3990 #4 0x7f8b766f369c in QEventDispatcherGlib::processEvents (this=0x7f8b580008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #5 0x7f8b766a6d9a in QEventLoop::exec (this=this@entry=0x7f8b66e8be40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f8b765001f4 in QThread::exec (this=) at thread/qthread.cp
[kmail2] [Bug 350219] Kmail can't create IMAP top level folders
https://bugs.kde.org/show_bug.cgi?id=350219 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org Platform|Kubuntu Packages|Gentoo Packages Version|5.1.3 |5.4.1 --- Comment #15 from Andreas K. Huettel --- Same effect on Gentoo, kmail 5.4.1 New top-level IMAP folders cannot be created in kmail / kontact. Creating one in akonadiconsole works fine. Updating the bug data to show it's still current / applicable -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.
https://bugs.kde.org/show_bug.cgi?id=341143 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org --- Comment #243 from Andreas K. Huettel --- Missing this feature as well. Please reconsider. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 356634] Kmail Randomly Hangs On Email Deletion
https://bugs.kde.org/show_bug.cgi?id=356634 Andreas K. Huettel changed: What|Removed |Added CC||dilfri...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #51 from Andreas K. Huettel --- (In reply to Daniel Vrátil from comment #50) > The only fix for the "Multiple merge candidates" error is to run Akonadi > Console, go to "Browser" tab, right-click the broken folder and select > "Clear Akonadi cache". Then restart Akonadi and it will re-fetch content of > the broken folder from the IMAP server. Dan, if I've been working on the folder in the meantime locally, in particular moving e-mails into that folder, are these mails lost then? -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 362006] New: 3.0.0_beta1: tablet (Intuos 4) recognized by finder, but kcm says "nothing connected"
https://bugs.kde.org/show_bug.cgi?id=362006 Bug ID: 362006 Summary: 3.0.0_beta1: tablet (Intuos 4) recognized by finder, but kcm says "nothing connected" Product: wacomtablet Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: joerg.ehri...@gmx.de Reporter: dilfri...@gentoo.org Have an Intuos 4, worked fine until the upgrade from KDE4. I packaged wacomtablet-3.0.0_beta1 (I'm in the gentoo kde team), the tabletfinder recognizes the tablet OK, but the KCM always shows "no tablet connected". Please advise how to debug further. Feel free to ping me on IRC (dilfridge). TIA! Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 362006] 3.0.0_beta1: tablet (Intuos 4) recognized by finder, but kcm says "nothing connected"
https://bugs.kde.org/show_bug.cgi?id=362006 --- Comment #1 from Andreas K. Huettel --- Created attachment 98513 --> https://bugs.kde.org/attachment.cgi?id=98513&action=edit workaround to force-disable xcb-input usage Seems like the problem comes from the new xcb-input code. If I hard-disable it, the tablet is recognized fine (see attachment for workaround). -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 362006] 3.0.0_beta1: tablet (Intuos 4) recognized by finder, kcm says "nothing connected", xcb-input problem
https://bugs.kde.org/show_bug.cgi?id=362006 Andreas K. Huettel changed: What|Removed |Added Summary|3.0.0_beta1: tablet (Intuos |3.0.0_beta1: tablet (Intuos |4) recognized by finder,|4) recognized by finder, |but kcm says "nothing |kcm says "nothing |connected" |connected", xcb-input ||problem -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 362006] releng3.0 HEAD: tablet (Intuos 4) recognized by finder, kcm says "nothing connected", xcb-input problem
https://bugs.kde.org/show_bug.cgi?id=362006 Andreas K. Huettel changed: What|Removed |Added Summary|3.0.0_beta1: tablet (Intuos |releng3.0 HEAD: tablet |4) recognized by finder,|(Intuos 4) recognized by |kcm says "nothing |finder, kcm says "nothing |connected", xcb-input |connected", xcb-input |problem |problem --- Comment #2 from Andreas K. Huettel --- Hmm. The workaround works on releng3.0 head, seems like something changed since 3.0.0beta1. -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 362006] releng3.0 HEAD: tablet (Intuos 4) recognized by finder, kcm says "nothing connected", xcb-input problem
https://bugs.kde.org/show_bug.cgi?id=362006 --- Comment #3 from Andreas K. Huettel --- Turns out this was only of limited success, since now * the tablet is displayed in the KCM, and e.g. the mapping to screen can be configured * but while the cursor moves, no clicks or touches arrive at all :( -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #51 from Andreas K. Huettel --- (In reply to Daniel Vrátil from comment #50) > The only fix for the "Multiple merge candidates" error is to run Akonadi > Console, go to "Browser" tab, right-click the broken folder and select > "Clear Akonadi cache". Then restart Akonadi and it will re-fetch content of > the broken folder from the IMAP server. Dan, if I've been working on the folder in the meantime locally, in particular moving e-mails into that folder, are these mails lost then? -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 362006] New: 3.0.0_beta1: tablet (Intuos 4) recognized by finder, but kcm says "nothing connected"
https://bugs.kde.org/show_bug.cgi?id=362006 Bug ID: 362006 Summary: 3.0.0_beta1: tablet (Intuos 4) recognized by finder, but kcm says "nothing connected" Product: wacomtablet Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: joerg.ehri...@gmx.de Reporter: dilfri...@gentoo.org Have an Intuos 4, worked fine until the upgrade from KDE4. I packaged wacomtablet-3.0.0_beta1 (I'm in the gentoo kde team), the tabletfinder recognizes the tablet OK, but the KCM always shows "no tablet connected". Please advise how to debug further. Feel free to ping me on IRC (dilfridge). TIA! Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 362006] 3.0.0_beta1: tablet (Intuos 4) recognized by finder, but kcm says "nothing connected"
https://bugs.kde.org/show_bug.cgi?id=362006 --- Comment #1 from Andreas K. Huettel --- Created attachment 98513 --> https://bugs.kde.org/attachment.cgi?id=98513&action=edit workaround to force-disable xcb-input usage Seems like the problem comes from the new xcb-input code. If I hard-disable it, the tablet is recognized fine (see attachment for workaround). -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 362006] 3.0.0_beta1: tablet (Intuos 4) recognized by finder, kcm says "nothing connected", xcb-input problem
https://bugs.kde.org/show_bug.cgi?id=362006 Andreas K. Huettel changed: What|Removed |Added Summary|3.0.0_beta1: tablet (Intuos |3.0.0_beta1: tablet (Intuos |4) recognized by finder,|4) recognized by finder, |but kcm says "nothing |kcm says "nothing |connected" |connected", xcb-input ||problem -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 362006] releng3.0 HEAD: tablet (Intuos 4) recognized by finder, kcm says "nothing connected", xcb-input problem
https://bugs.kde.org/show_bug.cgi?id=362006 Andreas K. Huettel changed: What|Removed |Added Summary|3.0.0_beta1: tablet (Intuos |releng3.0 HEAD: tablet |4) recognized by finder,|(Intuos 4) recognized by |kcm says "nothing |finder, kcm says "nothing |connected", xcb-input |connected", xcb-input |problem |problem --- Comment #2 from Andreas K. Huettel --- Hmm. The workaround works on releng3.0 head, seems like something changed since 3.0.0beta1. -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 362006] releng3.0 HEAD: tablet (Intuos 4) recognized by finder, kcm says "nothing connected", xcb-input problem
https://bugs.kde.org/show_bug.cgi?id=362006 --- Comment #3 from Andreas K. Huettel --- Turns out this was only of limited success, since now * the tablet is displayed in the KCM, and e.g. the mapping to screen can be configured * but while the cursor moves, no clicks or touches arrive at all :( -- You are receiving this mail because: You are watching all bug changes.
