[systemsettings] [Bug 366186] "Scale Display" doesn't properly scale applications for specific scaling factor values
https://bugs.kde.org/show_bug.cgi?id=366186 Robert Lindgren <r...@x0.se> changed: What|Removed |Added CC||r...@x0.se --- Comment #1 from Robert Lindgren <r...@x0.se> --- Same problem in Neon 5.9.2. Dell 4k monitor. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376984] New: Special application settings, force color scheme, doesn't apply on restart
https://bugs.kde.org/show_bug.cgi?id=376984 Bug ID: 376984 Summary: Special application settings, force color scheme, doesn't apply on restart Product: plasmashell Version: 5.9.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Look & Feel package Assignee: plasma-b...@kde.org Reporter: r...@x0.se CC: plasma-b...@kde.org Target Milestone: 1.0 In Special application settings, forcing color scheme, doesn't apply on application restart. My test is setting Spotify to force Breeze Dark. Works first time, but fails on application restart. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 373395] Crash on exit after playing track silently
https://bugs.kde.org/show_bug.cgi?id=373395 --- Comment #4 from robert marshall <rob...@capuchin.co.uk> --- I've not seen it crash again so I guess the rescan fixed that bit, the silent problem is I guess pulse's problem. Close it! -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 376586] Kdevelop crashes during parsing on large PHP projects/files
https://bugs.kde.org/show_bug.cgi?id=376586 --- Comment #2 from robert <robert.buchin...@gmail.com> --- I will try without rebuilding my whole dev space. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 376586] Kdevelop crashes during parsing on large PHP projects/files
https://bugs.kde.org/show_bug.cgi?id=376586 robert <robert.buchin...@gmail.com> changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 376586] New: Kdevelop crashes during parsing on large PHP projects/files
https://bugs.kde.org/show_bug.cgi?id=376586 Bug ID: 376586 Summary: Kdevelop crashes during parsing on large PHP projects/files Product: kdevelop Version: 5.0.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: PHP Assignee: kdevelop-bugs-n...@kde.org Reporter: robert.buchin...@gmail.com Target Milestone: --- Created attachment 104074 --> https://bugs.kde.org/attachment.cgi?id=104074=edit crash log Application: kdevelop (5.0.3) Qt Version: 5.8.0 Frameworks Version: 5.31.0 Operating System: Linux 4.9.8-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Each time opening the session containing this project KDevelop crashes after some seconds OR when background parser is turned off KDevelop crashes a few seconds after the background parser is enabled Project contains about 7100 files (most of then PHP and JS), files up to 8 lines of code Background parser is set to: 9 Threads with 500ms delay Kdevelop-PHP 5.0.3/glibc 2.24 The crash can be reproduced every time. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 375944] New: Bug
https://bugs.kde.org/show_bug.cgi?id=375944 Bug ID: 375944 Summary: Bug Product: kmymoney4 Version: 4.8.0 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: bobfarm...@msn.com Target Milestone: --- kmymoney stops responding when loading QIF file. Have to close and restart then it's OK. But this happens all the time. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375775] New: plasma crash
https://bugs.kde.org/show_bug.cgi?id=375775 Bug ID: 375775 Summary: plasma crash Product: plasmashell Version: 5.8.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: r...@bugs.kde.pu.futz.org CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.5) Qt Version: 5.7.1 Frameworks Version: 5.29.0 Operating System: Linux 4.9.6-200.fc25.x86_64 x86_64 Distribution: "Fedora release 25 (Twenty Five)" -- Information about the crash: - What I was doing when the application crashed: setting show/hide config for items in sys-tray settings - Unusual behavior I noticed: lots of plasma lockups and crashes on my system The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f582d8d0940 (LWP 2775))] Thread 8 (Thread 0x7f57715cf700 (LWP 5635)): #0 0x7f58344d67f9 in g_mutex_lock () at /lib64/libglib-2.0.so.0 #1 0x7f58344901c4 in g_main_context_release () at /lib64/libglib-2.0.so.0 #2 0x7f583449110a in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x7f583449126c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7f583c4f073b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f583c4a173a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f583c2fe5f3 in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x7f583f56f4e5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #8 0x7f583c3029da in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7f583aa3f6ca in start_thread () at /lib64/libpthread.so.0 #10 0x7f583b6f5f7f in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f5774670700 (LWP 4004)): #0 0x7f583b6e5bed in read () at /lib64/libc.so.6 #1 0x7f58344d5450 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7f5834490c60 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f58344910f4 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7f583449126c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f583c4f073b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f583c4a173a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7f583c2fe5f3 in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7f5775f402c7 in KCupsConnection::run() () at /lib64/libkcupslib.so #9 0x7f583c3029da in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #10 0x7f583aa3f6ca in start_thread () at /lib64/libpthread.so.0 #11 0x7f583b6f5f7f in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f580700 (LWP 3883)): #0 0x7f583aa45460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5841daa2f4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7f5841daa339 in () at /lib64/libQt5Script.so.5 #3 0x7f583aa3f6ca in start_thread () at /lib64/libpthread.so.0 #4 0x7f583b6f5f7f in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f581a9b6700 (LWP 3744)): #0 0x7f583b6ea01d in poll () at /lib64/libc.so.6 #1 0x7f5834491156 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f583449126c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f583c4f073b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f583c4a173a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f583c2fe5f3 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f583f56f4e5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7f583c3029da in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f583aa3f6ca in start_thread () at /lib64/libpthread.so.0 #9 0x7f583b6f5f7f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f581bfff700 (LWP 3009)): #0 0x7f583448e1e7 in g_source_iter_next () at /lib64/libglib-2.0.so.0 #1 0x7f5834490ac4 in g_main_context_check () at /lib64/libglib-2.0.so.0 #2 0x7f58344910f4 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x7f583449126c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7f583c4f073b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f583c4a173a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f583c2fe5f3 in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x7f583f56f4e5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #8 0x7f583c3029da in QThreadPrivate::start(void*) () at
[krunner] [Bug 353547] krunner uses 726GiB (Gigabytes!) of virtual memory - mapped the baloo index ~3000 times
https://bugs.kde.org/show_bug.cgi?id=353547 Robert <r...@bugs.kde.pu.futz.org> changed: What|Removed |Added CC||r...@bugs.kde.pu.futz.org --- Comment #12 from Robert <r...@bugs.kde.pu.futz.org> --- another 'me too'.. Fedora 25, plasma 5.8.5, krunner using 257 G of memory. balooctl status Baloo File Indexer is running Indexer state: Idle Indexed 7 / 7 files Current size of index is 136.00 KiB -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 375434] New: Crash going to all settings on KDE Fedora 25
https://bugs.kde.org/show_bug.cgi?id=375434 Bug ID: 375434 Summary: Crash going to all settings on KDE Fedora 25 Product: systemsettings Version: 5.8.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: rstehw...@gmail.com Target Milestone: --- Application: systemsettings5 (5.8.5) Qt Version: 5.7.1 Frameworks Version: 5.29.0 Operating System: Linux 4.9.4-201.fc25.x86_64 x86_64 Distribution: "Fedora release 25 (Twenty Five)" -- Information about the crash: - What I was doing when the application crashed: Going back to all settings. Had just discarded some changes. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f83463016c0 (LWP 4429))] Thread 7 (Thread 0x7f82e700 (LWP 4504)): #0 0x7f8351ea001d in poll () from /lib64/libc.so.6 #1 0x7f834ad30156 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f834ad3026c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f8352ca673b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f8352c5773a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f8352ab45f3 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f83516784e5 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #7 0x7f8352ab89da in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f834ef766ca in start_thread () from /lib64/libpthread.so.0 #9 0x7f8351eabf7f in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f831ddd6700 (LWP 4470)): #0 0x7f8351e9bbed in read () from /lib64/libc.so.6 #1 0x7f834ad74450 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0 #2 0x7f834ad2fc60 in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x7f834ad300f4 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #4 0x7f834ad3026c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f8352ca673b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f8352c5773a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7f8352ab45f3 in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7f83516784e5 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #9 0x7f8352ab89da in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #10 0x7f834ef766ca in start_thread () from /lib64/libpthread.so.0 #11 0x7f8351eabf7f in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f831efe6700 (LWP 4469)): #0 0x7f834ad75814 in g_mutex_unlock () from /lib64/libglib-2.0.so.0 #1 0x7f834ad2f68c in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #2 0x7f834ad3007b in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7f834ad3026c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7f8352ca673b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f8352c5773a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f8352ab45f3 in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x7f83516784e5 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #8 0x7f8352ab89da in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7f834ef766ca in start_thread () from /lib64/libpthread.so.0 #10 0x7f8351eabf7f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f83274e2700 (LWP 4437)): #0 0x7f8351ea001d in poll () from /lib64/libc.so.6 #1 0x7f834ad30156 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f834ad3026c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f8352ca673b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f8352c5773a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f8352ab45f3 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f83516784e5 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #7 0x7f8352ab89da in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f834ef766ca in start_thread () from /lib64/libpthread.so.0 #9 0x7f8351eabf7f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f8332c09700 (LWP 4432)): #0 0x7f8351ea001d in poll () from /lib64/libc.so.6 #1 0x7f834ad30156 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f834ad3026c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f8352ca673b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f8352c5773a in QEventLoop::exec(QFlags) ()
[krita] [Bug 375285] Krita crashes every time saving or opening any .kra file
https://bugs.kde.org/show_bug.cgi?id=375285 --- Comment #4 from Robert <rgbe...@gmail.com> --- Thank you for the reply. On Thu, Jan 19, 2017 at 3:37 AM, Boudewijn Rempt <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=375285 > > --- Comment #3 from Boudewijn Rempt <b...@valdyas.org> --- > *** Bug 375214 has been marked as a duplicate of this bug. *** > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375285] Krita crashes every time saving or opening any .kra file
https://bugs.kde.org/show_bug.cgi?id=375285 --- Comment #1 from Robert <rgbe...@gmail.com> --- Created attachment 103522 --> https://bugs.kde.org/attachment.cgi?id=103522=edit gdb krita just in case the backtrace report was lacking information needed -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375285] New: Krita crashes every time saving or opening any .kra file
https://bugs.kde.org/show_bug.cgi?id=375285 Bug ID: 375285 Summary: Krita crashes every time saving or opening any .kra file Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: rgbe...@gmail.com Target Milestone: --- Created attachment 103521 --> https://bugs.kde.org/attachment.cgi?id=103521=edit Backtrace crash report when tried saving a new .kra file I have recently updated Krita to the newest git version 3.1.88 (git 57fe954), from the previous version, where there was no issues. But when I first started trying to make a new image I noticed that it took longer than it should have to open up. Then I started to draw and about the time when krita would autosave, every 5 min, it would crash; losing all the settings that I had had set with brushes and layouts. Then I tried to save the new file, I had just created, right away, but it would crash instantly. So I tried opening previously made .kra files and with same result it would crash again. But opening a .png or .jpg file there was no issue. Exporting the image as a .png it gives me an internal error but doesn't crash. Everything in the setting is default for the image, so I don't know why it is doing this. I can't even use Krita from the git version. The 3.1.1 snap package all works fine. I had no crashes with opening or saving files. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375214] New: Krita 3.1.88 git Crashing every time saving
https://bugs.kde.org/show_bug.cgi?id=375214 Bug ID: 375214 Summary: Krita 3.1.88 git Crashing every time saving Product: krita Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: rgbe...@gmail.com Target Milestone: --- Application: krita (3.1.88 (git 4df1b99)) (Compiled from sources) Qt Version: 5.7.1 Frameworks Version: 5.29.0 Operating System: Linux 4.9.4-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: Tried to save a .kra whether I drew on it or not. It would reset all the settings that I had changed. - Unusual behavior I noticed: Krita would crash evertime I was drawing for about 5 min. Then I tried to save the document before it crashed. - Custom settings of the application: I made the cavas bigger, 3508 X 2480 px @ 300 ppi But everything else was default. The crash can be reproduced every time. -- Backtrace: Application: Krita (krita), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4c68472780 (LWP 13775))] Thread 7 (Thread 0x7f4c66453700 (LWP 13776)): #0 0x7f4c70a214ad in poll () from /lib64/libc.so.6 #1 0x7f4c740b48f2 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f4c740b66df in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f4c6817e2a9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f4c715f072c in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7f4c6f479444 in start_thread () from /lib64/libpthread.so.0 #6 0x7f4c70a2a5ad in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f4c5b82c700 (LWP 13778)): #0 0x7f4c70a214ad in poll () from /lib64/libc.so.6 #1 0x7f4c6ca80fec in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f4c6ca810fc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f4c717e0e4c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f4c7179448a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f4c715ec194 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f4c7a42a445 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7f4c715f072c in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7f4c6f479444 in start_thread () from /lib64/libpthread.so.0 #9 0x7f4c70a2a5ad in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f4c0af72700 (LWP 13791)): #0 0x7f4c6f47f02f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4c715f0d9a in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x7f4c715eae7b in QSemaphore::acquire(int) () from /usr/lib64/libQt5Core.so.5 #3 0x7f4c78a355ce in KisTileDataPooler::waitForWork (this=0x7f4c78f16d00 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>) at /home/rbear/krita/src/libs/image/tiles3/kis_tile_data_pooler.cc:165 #4 0x7f4c78a35fb2 in KisTileDataPooler::run (this=0x7f4c78f16d00 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>) at /home/rbear/krita/src/libs/image/tiles3/kis_tile_data_pooler.cc:187 #5 0x7f4c715f072c in ?? () from /usr/lib64/libQt5Core.so.5 #6 0x7f4c6f479444 in start_thread () from /lib64/libpthread.so.0 #7 0x7f4c70a2a5ad in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f4c0a771700 (LWP 13792)): #0 0x7f4c6f47f02f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4c715f0d9a in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x7f4c715eb123 in QSemaphore::tryAcquire(int, int) () from /usr/lib64/libQt5Core.so.5 #3 0x7f4c78a50c93 in KisTileDataSwapper::waitForWork (this=) at /home/rbear/krita/src/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:86 #4 0x7f4c78a50e8a in KisTileDataSwapper::run (this=0x7f4c78f16d40 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder+64>) at /home/rbear/krita/src/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:92 #5 0x7f4c715f072c in ?? () from /usr/lib64/libQt5Core.so.5 #6 0x7f4c6f479444 in start_thread () from /lib64/libpthread.so.0 #7 0x7f4c70a2a5ad in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f4c09f70700 (LWP 13794)): #0 0x7f4c6f47f02f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4c715f0d9a in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x7f4c721ffa0a in ?? () from /usr/lib64/libQt5Widgets.so.5 #3 0x7f4c715f072c in ?? () from /usr/lib64/libQt5Core.so.5 #4 0x7f4c6f479444 in start_thread () from /lib64/libpthread.so.0 #5 0x7f4c70a2a5ad in clone () from /lib64/libc.so.6 Thread 2 (Thread
[trojita] [Bug 375179] Composer inserts hard line breaks to replies
https://bugs.kde.org/show_bug.cgi?id=375179 --- Comment #7 from Robert Kratky <kra...@rob.cz> --- Created attachment 103463 --> https://bugs.kde.org/attachment.cgi?id=103463=edit Composer without breaks -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 375179] Composer inserts hard line breaks to replies
https://bugs.kde.org/show_bug.cgi?id=375179 Robert Kratky <kra...@rob.cz> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #6 from Robert Kratky <kra...@rob.cz> --- (In reply to Jan Kundrát from comment #5) > Before we go further, could you please clarify what you expect to see and > why so? > > Trojita uses the format=flowed extension which affects the perceived line > breaks (and their on-the-wire form, too). If you reply to a flowed text, the > composer shows it with apparent line breaks because we have to somehow fit > the text into the composer window. The outgoing form is created using flowed > formatting once again, and will be re-flowed as needed. Maybe that is > confusing for you? That was indeed confusing to me. I didn't realize the message was then reflowed again. It's fine then. Just to clarify, I was expecting the composer to show the text as on the attached screenshot. It would seem more intuitive to me (I'm used to such behaviour from Kmail). -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 375179] Composer inserts hard line breaks to replies
https://bugs.kde.org/show_bug.cgi?id=375179 --- Comment #4 from Robert Kratky <kra...@rob.cz> --- Attached before and after screenshots. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 375179] Composer inserts hard line breaks to replies
https://bugs.kde.org/show_bug.cgi?id=375179 --- Comment #2 from Robert Kratky <kra...@rob.cz> --- Created attachment 103459 --> https://bugs.kde.org/attachment.cgi?id=103459=edit Message with no hard breaks -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 375179] Composer inserts hard line breaks to replies
https://bugs.kde.org/show_bug.cgi?id=375179 --- Comment #3 from Robert Kratky <kra...@rob.cz> --- Created attachment 103460 --> https://bugs.kde.org/attachment.cgi?id=103460=edit Quoted text in composer with hard breaks -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 375179] New: Composer inserts hard line breaks to replies
https://bugs.kde.org/show_bug.cgi?id=375179 Bug ID: 375179 Summary: Composer inserts hard line breaks to replies Product: trojita Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Message Composer Assignee: trojita-b...@kde.org Reporter: kra...@rob.cz Target Milestone: --- When replying to a message that had no hard line breaks, the composer inserts them into the quoted parts anyway. This should not be happening (or should be configurable -- whether the user wants the composer to always use hard breaks). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375172] New: kwin_x11 crash at system start
https://bugs.kde.org/show_bug.cgi?id=375172 Bug ID: 375172 Summary: kwin_x11 crash at system start Product: kwin Version: 5.8.5 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: s...@beotel.net Target Milestone: --- Application: kwin_x11 (5.8.5) Qt Version: 5.6.1 Frameworks Version: 5.28.0 Operating System: Linux 4.4.0-59-generic x86_64 Distribution: Linux Mint 18 Sarah -- Information about the crash: - What I was doing when the application crashed: Booting system. - Unusual behavior I noticed: Some startap applications behave oddly. Eg. Yakuake starts before plasma desktop itself and stays open until manualy closed ( hid). -- Backtrace: Application: К‑вин (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f904f2d3940 (LWP 2066))] Thread 4 (Thread 0x7f901bfff700 (LWP 2105)): #0 0x7ffc4e7f7caf in clock_gettime () #1 0x7f904ede8c86 in __GI___clock_gettime (clock_id=1, tp=0x7f901bffea10) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7f904cac56c6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f904cc40f09 in QTimerInfoList::updateCurrentTime() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f904cc4030b in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f904cc40b22 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f904cbebffa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f904ca149e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f9047c0b6b5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7f904ca19808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f9048aa86ba in start_thread (arg=0x7f901bfff700) at pthread_create.c:333 #11 0x7f904edda82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f9020b96700 (LWP 2104)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f902cc40213 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #2 0x7f902cc3f937 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r300_dri.so #3 0x7f9048aa86ba in start_thread (arg=0x7f9020b96700) at pthread_create.c:333 #4 0x7f904edda82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f9035a58700 (LWP 2068)): #0 0x7ffc4e7f7caf in clock_gettime () #1 0x7f904ede8c86 in __GI___clock_gettime (clock_id=1, tp=0x7f9035a57a00) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7f904cac56c6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f904cc40f09 in QTimerInfoList::updateCurrentTime() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f904cc4030b in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f904cc40b22 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f904cbebffa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f904ca149e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f904f3f7515 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7f904ca19808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f9048aa86ba in start_thread (arg=0x7f9035a58700) at pthread_create.c:333 #11 0x7f904edda82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f904f2d3940 (LWP 2066)): [KCrash Handler] #6 0x7f9047ba5984 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f9047ba3571 in QQmlMetaType::qmlSingletonTypes() () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f9047b7b6b1 in QQmlEngine::~QQmlEngine() () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7f9047b7b849 in QQmlEngine::~QQmlEngine() () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7f904ed0dff8 in __run_exit_handlers (status=1, listp=0x7f904f0975f8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82 #11 0x7f904ed0e045 in __GI_exit (status=) at exit.c:104 #12 0x7f9038208d18 in QXcbConnection::processXcbEvents() () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #13 0x7f904cc1b719 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f904d523afc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7f904d529036 in QApplication::notify(QObject*, QEvent*) () from
[trojita] [Bug 375034] State of 'Show Messages in Threads' not remembered
https://bugs.kde.org/show_bug.cgi?id=375034 --- Comment #1 from Robert Kratky <kra...@rob.cz> --- (In reply to Robert Kratky from comment #0) > The only thing that seems to be consistent is that the setting always stays > on in INBOX. Scratch that. That was a coincidence. I've now seen it forget the setting even in INBOX. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 375034] New: State of 'Show Messages in Threads' not remembered
https://bugs.kde.org/show_bug.cgi?id=375034 Bug ID: 375034 Summary: State of 'Show Messages in Threads' not remembered Product: trojita Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: kra...@rob.cz Target Milestone: --- The 'Show Messages in Threads' toggle option sometimes doesn't stay turned on. I haven't been able to find any pattern -- in some mailboxes, it stays on, in some, it doesn't. In some mailboxes, the setting is remembered even between sessions, in some, it doesn't survive mere switching between mailboxes. The only thing that seems to be consistent is that the setting always stays on in INBOX. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 374959] New: Error on 'Expunge': UnrecognizedResponseKind: -1
https://bugs.kde.org/show_bug.cgi?id=374959 Bug ID: 374959 Summary: Error on 'Expunge': UnrecognizedResponseKind: -1 Product: trojita Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP Assignee: trojita-b...@kde.org Reporter: kra...@rob.cz Target Milestone: --- Error message upon "Expunge": The IMAP server sent us a reply which we could not parse. This might either mean that there's a bug in Trojitá's code, or that the IMAP server you are connected to is broken. Please report this as a bug anyway. Here are the details: UnrecognizedResponseKind: -1 * -1 RECENT ^ here -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 374820] Keyboard shortcuts should be active without clicking on a message in a mailbox
https://bugs.kde.org/show_bug.cgi?id=374820 Robert Kratky <kra...@rob.cz> changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #2 from Robert Kratky <kra...@rob.cz> --- Right, I installed from source and can confirm it works as expected. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 374859] Local e-mail threading
https://bugs.kde.org/show_bug.cgi?id=374859 --- Comment #5 from Robert Kratky <kra...@rob.cz> --- The penultimate sentence was meant to be a question: Is Trojita featured on any of the open-source market place websites where I could set up a bounty for this? -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 374859] Local e-mail threading
https://bugs.kde.org/show_bug.cgi?id=374859 --- Comment #4 from Robert Kratky <kra...@rob.cz> --- (In reply to Jan Kundrát from comment #3) > (In reply to Robert Kratky from comment #2) > > Pardon my ignorance... what's a hamburger icon? > > Ah, that's probably a KDE-ism. Since you haven't said what version you're on > and because newer versions of Trojita merged the main into the toolbar by > default, you have to click an icon in the toolbar to get access to it. It's > on a lower left corner on this screenshot, > http://trojita.flaska.net/img/2016-03-22-trojita-home.png, and someone > suggested that it looks like a hamburger :]. Thanks. You were right, just THREAD=ORDEREDSUBJECT :-/ Speaking of newer versions -- can you set up nightly builds for Fedora 25, too? I now see that the 0.7 release that I use is not exactly new. > > > If you have suggestions on how to better reflect this state in the UI, > > > please propose them here. > > Not sure what you mean. If the client doesn't know about the threading, how > > could it be reflected in the GUI? > > You invested time by opening a bugreport which means that you were surprised > to see broken threading -- I understand that, that makes sense, and I > appreciate the feedback. So maybe there's something that we can do so that > we won't get a similar bugreport in future? (Apart from actually > implementing this :). ) > > Maybe a pop-up or a mouse-over text next to the action in the menu? > Something else? A color-coded icon showing the "level of suckiness" of the > IMAP server? I'm looking for suggestions. Ok, a popup that would warn of the inadequacies of the IMAP server (shown when a user clocks on the threading toggle) could help. > > The code that supports this surely exists somewhere. Other clients, incl. > > Kmail, support this threading. Wouldn't it be possible to reuse it? (I'm not > > a programmer, so I can't contribute code, unfortunately.) > > Yes, other projects have solved this, but taking code from an external > project or even simply using a well-maintained library needs integration > work. And because I don't really need this feature myself, I don't see me > investing my time to write this. Patch review and guidance, yes, writing > code, no. Is Trojita featured on any of the open-source market place websites where I could set up a bounty for this. As I said, I can't contribute code, but I'd be willing to contribute money. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 374798] Add "Save link as" to context menu in messages
https://bugs.kde.org/show_bug.cgi?id=374798 --- Comment #7 from Robert Kratky <kra...@rob.cz> --- (In reply to Jan Kundrát from comment #6) > (In reply to Robert Kratky from comment #5) > > The problem with the round trip through the browser is that I have my > > desktop environment configured in a way that only a certain limited subset > > of MIME types is opened through the browser when I click on them. For > > example, I use an image viewer to open images by default. So, when I click > > on a URL that points to an image in Trojita, the file is opened by the image > > viewer. > > > > Now, that particular helper app that's used to open a specific type of file > > may or may not have the functionality to save that file to a disk (for > > example, my GIF viewer isn't capable of doing that). So, I'm stuck with two > > options: > > > > * copy the URL from Trojita and use wget or similar > > * copy the URL from Trojita and open in a browser > > > > Both are possible but both are annoying and the 'round trip' has gotten a > > lot more complicated than just clicking on a link. > > The DE that I use (Plasma) has a switch which controls whether an URL is > always opened in a web browser, or whether the MIME type is guessed/checked > (I don't actually know, maybe it uses its generic network stack to download > or HTTP HEAD it first) and then an appropriate local application is used for > its handling. Perhaps you can use a similar feature as well? I use Plasma, too, but I actually like to open the individual types of files in their associated apps. Even from Trojita. But I'd like to have the opportunity to download the file instead of opening it when I choose so. Even if I decided that I only want to open the files from Trojita in a browser, it's not possible. (Unless I'm mistaken, there'no way to configure this behaviour on a per-app basis.) > I believe that it's the job of the "rest of the desktop environment" to > provide a wrapper which gets triggered when a user "just clicked a web link" > to ask what they intend to do. I don't want to manage filetype associations > within Trojita, either; these are bits which we simply delegate to the DE. That sounds reasonable, but I don't know of any DE that would implement this. Perhaps it would be possible to implement custom menu items as Thomas suggested? I'd gladly write a wrapper script myself then. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 374832] Auto trimming of replies should be configurable
https://bugs.kde.org/show_bug.cgi?id=374832 --- Comment #2 from Robert Kratky <kra...@rob.cz> --- My suggestion would be to either not to collapse by default (that seems to me to be a less intrusive default than collapsing by default), or to make it configurable. I.e. to include an option (in the 'View' menu?) that would toggle automatic collapsing. At the very least, It'd be nice to have the possibility to expand *all* collapsed parts with one click/shortcut. As it is now, if I want to view the whole message, I need to go through it, clicking along to show deeper and deeper levels. To me, that seems very inconvenient. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 374859] Threaded view not really threaded
https://bugs.kde.org/show_bug.cgi?id=374859 --- Comment #2 from Robert Kratky <kra...@rob.cz> --- (In reply to Jan Kundrát from comment #1) > This functionality depends on a server-side support ([1] and [2]) for e-mail > threads. Chances are that your IMAP server might only support > THREAD=ORDEREDSUBJECT which indeed sucks exactly like you described. You can > check the dialog under the hamburger icon -> IMAP -> Debugging -> IMAP > Server Information for a list of announced capabilities to confirm this. Pardon my ignorance... what's a hamburger icon? > We do not do client-side threading because doing that would require Trojita > to download a subset of header for each message in an entire mailbox. It is > a design decision -- we rely on IMAP features so that the server can do work > on our behalf and that we do not have to transfer data that we do not really > need. Unfortunately, this means that the end user experience is worse in > case their e-mail server leaves something to be desired. Right now for > example we won't do any threading on GMail because GMail servers have their > own proprietary extension for one-level-deep threading and because we don't > have code to work with this non-standard extension yet (patches welcome). Yeah, I read about this decision in Trojita a couple of years ago. Understandable. I just didn't know that this was a similar problem. For reference, the IMAP server I'm using is Zimbra. > If you have suggestions on how to better reflect this state in the UI, > please propose them here. Not sure what you mean. If the client doesn't know about the threading, how could it be reflected in the GUI? > If someone wants to contribute code which adds support for client-side > threading, I'll be happy to review the patches and to provide suggestions on > how to best approach the problem. However, I don't see myself actively > working on this. The code that supports this surely exists somewhere. Other clients, incl. Kmail, support this threading. Wouldn't it be possible to reuse it? (I'm not a programmer, so I can't contribute code, unfortunately.) > [1] https://tools.ietf.org/html/rfc5256 > [2] https://tools.ietf.org/html/draft-ietf-morg-inthread-01 -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 374859] New: Threaded view not really threaded
https://bugs.kde.org/show_bug.cgi?id=374859 Bug ID: 374859 Summary: Threaded view not really threaded Product: trojita Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: kra...@rob.cz Target Milestone: --- When the "Show messages in threads" option is checked, only one level of threads is shown. I.e. below the first message of a thread, the thread structure is flat. This would be correct only if all messages in the thread were replies to the first message. Now we have (regardless of the real structure): |-- |-- |-- |-- |-- |-- |-- A real thread usually looks something like the following: |-- |-- | |-- |-- |-- |-- -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 374832] New: Auto trimming of replies should be configurable
https://bugs.kde.org/show_bug.cgi?id=374832 Bug ID: 374832 Summary: Auto trimming of replies should be configurable Product: trojita Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: kra...@rob.cz Target Milestone: --- Currently, when I reply to a plain-text message that contains collapsed content (more than one level of replies within the body), the collapsed content isn't included in the reply. This should be configurable (or the display of messages should not be collapsed by default). Most of the times, I wish to include at least some of the thread's history in the reply, not just the immediately preceding message. In order to do that, I now need to manually expand the message by clicking on the 'ellipsis' buttons before I hit 'reply'. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 374831] New: Context menu on e-mail address should offer "Add to addressbook"
https://bugs.kde.org/show_bug.cgi?id=374831 Bug ID: 374831 Summary: Context menu on e-mail address should offer "Add to addressbook" Product: trojita Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: kra...@rob.cz Target Milestone: --- The context menu shown when right-clicking on an e-mail address in the header of a message should offer the option to add the address (and name, if available) to the addressbook. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 374830] New: Context menu on e-mail address should offer "Copy e-mail address"
https://bugs.kde.org/show_bug.cgi?id=374830 Bug ID: 374830 Summary: Context menu on e-mail address should offer "Copy e-mail address" Product: trojita Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: kra...@rob.cz Target Milestone: --- The context menu shown when right-clicking on an e-mail address in the header of a message should offer the option to copy the e-mail address to the clipboard. Right now, the menu only offers "Copy Link Location", which gets me the following (in this case unhelpful) URL: mailto:j...@example.com?X-Trojita-DisplayName=Joe It would be good if one could also copy just: j...@example.com -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 374822] Quick search filters messages "as you type"
https://bugs.kde.org/show_bug.cgi?id=374822 --- Comment #2 from Robert Kratky <kra...@rob.cz> --- (In reply to Thomas Lübking from comment #1) > you're aware that it's an online query and will cause quite some traffic? I wasn't aware of that. Perhaps it could be configurable? -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 374824] New: Configure moving in list of messages vs scrolling a selected message
https://bugs.kde.org/show_bug.cgi?id=374824 Bug ID: 374824 Summary: Configure moving in list of messages vs scrolling a selected message Product: trojita Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: kra...@rob.cz Target Milestone: --- It would be nice to have the possibility to configure what navigation keys (up, down, left, right, pgup, pgdown, home, end) do when a message is selected. Now, all of the navig. keys move in the list of messages within the mailbox. I.e. "up" selects the previous message, "home" jumps to the first message in the mailbox, etc. I'd like to be able to configure that these keys would instead affect the viewing of the body of the currently selected message (without having to click on the body of the message to manually select that view/frame). I.e. "pgdown" would scroll one page down in the selected message etc. Ideally, this would be configurable on a per-key basis. For example, I'm used to having the following setting: left - moves/selects one message up right - moves/selects one message down up, down, pgup, pgdown, home, end - all affect scrolling within the currently selected message -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 374822] New: Quick search filters messages "as you type"
https://bugs.kde.org/show_bug.cgi?id=374822 Bug ID: 374822 Summary: Quick search filters messages "as you type" Product: trojita Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: kra...@rob.cz Target Milestone: --- It would be nice if messages were automatically filtered as you type in the 'Quick Search' field (instead of having to press Enter to trigger the search). -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 374821] New: Previously selected message should be shown when a mailbox is opened
https://bugs.kde.org/show_bug.cgi?id=374821 Bug ID: 374821 Summary: Previously selected message should be shown when a mailbox is opened Product: trojita Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: kra...@rob.cz Target Milestone: --- When I click on a mailbox, and its list of messages is displayed, I would expect the last message that was selected (when I previously browsed that mailbox) to be automatically selected and open. If this is the first time I'm opening the mailbox (i.e. no previously selected message exists), then I would expect either the oldest unread message to be selected, or the current behaviour (i.e. no message gets selected). This is possibly connected to #374820 -- as in, if a message is automatically selected upon opening a mailbox, the linked bug would be taken care of. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 374820] New: Keyboard shortcuts should be active without clicking on a message in a mailbox
https://bugs.kde.org/show_bug.cgi?id=374820 Bug ID: 374820 Summary: Keyboard shortcuts should be active without clicking on a message in a mailbox Product: trojita Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: kra...@rob.cz Target Milestone: --- When I click on a mailbox that contains unread messages, and the list of its messages is displayed, it should be possible to start using navigation keyboard shortcuts (next/prev new message) immediately -- without having to click on/select a message within that mailbox. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 374819] New: When dragging a collapsed thread, all messages in the thread should be moved
https://bugs.kde.org/show_bug.cgi?id=374819 Bug ID: 374819 Summary: When dragging a collapsed thread, all messages in the thread should be moved Product: trojita Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: kra...@rob.cz Target Milestone: --- Currently, when I drag (& drop) a collapsed thread of messages, only the top message gets dragged. This is unintuitive (and it's different from the behaviour of other applications that use some sort of hierarchical collapsing). All messages in the collapsed thread should be moved. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 374798] Add "Save link as" to context menu in messages
https://bugs.kde.org/show_bug.cgi?id=374798 --- Comment #5 from Robert Kratky <kra...@rob.cz> --- (In reply to Jan Kundrát from comment #4) > > Right click on a URL, select 'Save link as', which opens a save-file dialog > > window that lets me choose where I want to save the file. > > That was sort of obvious :), but I wonder what do you want/use this for. > What's wrong with a roundtrip through your browser? Click a link -> your > browser asks you what to do -> the browser performs the required work. OK, I didn't understand before what you had in mind when you asked how I use this feature in other MUA. The problem with the round trip through the browser is that I have my desktop environment configured in a way that only a certain limited subset of MIME types is opened through the browser when I click on them. For example, I use an image viewer to open images by default. So, when I click on a URL that points to an image in Trojita, the file is opened by the image viewer. Now, that particular helper app that's used to open a specific type of file may or may not have the functionality to save that file to a disk (for example, my GIF viewer isn't capable of doing that). So, I'm stuck with two options: * copy the URL from Trojita and use wget or similar * copy the URL from Trojita and open in a browser Both are possible but both are annoying and the 'round trip' has gotten a lot more complicated than just clicking on a link. > As an anecdotal data point about my specific usage patterns: when a link > refers to something which is not a web page, it's very often something > which requires authentication anyway. Trojita won't know what to do in that > case. I don't see that many examples of this in my workflow, but wouldn't it be possible for Trojita to time out in such cases and report something like 'Unable to access'? I don't know how Trojita handles HTML content in messages, but the fact that it's capable of displaying it properly rendered means that it must be capable of downloading arbitrary stuff from the Internet, or not? > We also do not want to deal with showing a progress GUI of possibly N > concurrent downloads, to track their state, to make this list persistent > and to recover from OS/session restarts, etc. In short, as Thomas said, > Trojita is not a download manager. That's a good point, but couldn't this be hidden, for example, behind the systray icon? And I don't mean progress bars or something like that. Just a note that Trojita is trying to access so and so. Just an idea. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 374798] Add "Save link as" to context menu in messages
https://bugs.kde.org/show_bug.cgi?id=374798 --- Comment #3 from Robert Kratky <kra...@rob.cz> --- (In reply to Jan Kundrát from comment #1) > Can you please explain what use case do you have in mind? How do you usually > use this feature in another MUA? Right click on a URL, select 'Save link as', which opens a save-file dialog window that lets me choose where I want to save the file. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 374798] New: Add "Save link as" to context menu in messages
https://bugs.kde.org/show_bug.cgi?id=374798 Bug ID: 374798 Summary: Add "Save link as" to context menu in messages Product: trojita Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: kra...@rob.cz Target Milestone: --- Upon right-clicking on a link/URL in a message, it would be useful to have a "Save link as" option for easy downloading of linked files/content. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 374797] New: Tabbed interface for folders/mailboxes
https://bugs.kde.org/show_bug.cgi?id=374797 Bug ID: 374797 Summary: Tabbed interface for folders/mailboxes Product: trojita Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: kra...@rob.cz Target Milestone: --- It would be great if Trojita supported tabs for easy switching between several open mailboxes. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 321229] LDAP address book support
https://bugs.kde.org/show_bug.cgi?id=321229 Robert Kratky <kra...@rob.cz> changed: What|Removed |Added CC||kra...@rob.cz -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 321374] Multiple accounts
https://bugs.kde.org/show_bug.cgi?id=321374 Robert Kratky <kra...@rob.cz> changed: What|Removed |Added CC||kra...@rob.cz -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 321228] Kerberos authenticaton support
https://bugs.kde.org/show_bug.cgi?id=321228 Robert Kratky <kra...@rob.cz> changed: What|Removed |Added CC||kra...@rob.cz -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 336138] Do not use localized date
https://bugs.kde.org/show_bug.cgi?id=336138 Robert Kratky <kra...@rob.cz> changed: What|Removed |Added CC||kra...@rob.cz -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 321370] Automatically expand threads with new arrivals
https://bugs.kde.org/show_bug.cgi?id=321370 Robert Kratky <kra...@rob.cz> changed: What|Removed |Added CC||kra...@rob.cz -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 374492] New: The chat application crashes on paste onto the divide line
https://bugs.kde.org/show_bug.cgi?id=374492 Bug ID: 374492 Summary: The chat application crashes on paste onto the divide line Product: telepathy Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: text-ui Assignee: kde-telepathy-b...@kde.org Reporter: s...@szo.hu Target Milestone: Future Pasting with middle-click into the text window and into the text entry window works as expected, but it the mouse pointer is exactly on the line between the two when pressing middle-click, the application crashes. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 373395] Crash on exit after playing track silently
https://bugs.kde.org/show_bug.cgi?id=373395 --- Comment #2 from robert marshall <rob...@capuchin.co.uk> --- It seems to only happen when I get the audio playback in that broken state. I've done a rescan and am trying to get it to happen again. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 373395] New: Crash on exit after playing track silently
https://bugs.kde.org/show_bug.cgi?id=373395 Bug ID: 373395 Summary: Crash on exit after playing track silently Product: amarok Version: 2.8-git Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: rob...@capuchin.co.uk Target Milestone: 2.9 I use bluetooth headphones on a few occasions I take the laptop away from the headset and turn off the bluetooth device within plasma. I return and reconnect the device - which works and the volume control sees the device. But sometimes when I then play a track it appears to play but is silent (nothing on the headphones - or on the wired phone connection). If I then exit amarok to try to sort it out it crashes on exit with the following traceback Application: Amarok (amarok), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238 [Current thread is 1 (Thread 0x7f9dba84e800 (LWP 12783))] Thread 17 (Thread 0x7f9d82c7e700 (LWP 12787)): #0 0x7f9db744faed in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f9daf7b5ee4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9daf7b5ffc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9db7bdbd37 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7f9db7bab271 in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7f9db7bab5d5 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7f9db7a9fe99 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f9db7b8bac3 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7f9db7aa270f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7f9db653f0a4 in start_thread (arg=0x7f9d82c7e700) at pthread_create.c:309 #10 0x7f9db745862d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 16 (Thread 0x7f9d80e5d700 (LWP 12788)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238 #1 0x7f9db7aa2c44 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f9db9297a47 in AbstractDirectoryWatcher::run (this=0xf9d6d0) at /home/robertmarshall/devel/kde-build/amarok/src/scanner/AbstractDirectoryWatcher.cpp:65 #3 0x7f9db3dd7912 in ?? () from /usr/lib/libthreadweaver.so.4 #4 0x7f9db3dd7b28 in ThreadWeaver::Job::execute(ThreadWeaver::Thread*) () from /usr/lib/libthreadweaver.so.4 #5 0x7f9db3dd72cb in ThreadWeaver::Thread::run() () from /usr/lib/libthreadweaver.so.4 #6 0x7f9db7aa270f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f9db653f0a4 in start_thread (arg=0x7f9d80e5d700) at pthread_create.c:309 #8 0x7f9db745862d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 15 (Thread 0x7f9d7bfff700 (LWP 12789)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f9db7aa2c66 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f9db3dd586c in ?? () from /usr/lib/libthreadweaver.so.4 #3 0x7f9db3dd8743 in ?? () from /usr/lib/libthreadweaver.so.4 #4 0x7f9db3dd875c in ?? () from /usr/lib/libthreadweaver.so.4 #5 0x7f9db3dd875c in ?? () from /usr/lib/libthreadweaver.so.4 #6 0x7f9db3dd875c in ?? () from /usr/lib/libthreadweaver.so.4 #7 0x7f9db3dd875c in ?? () from /usr/lib/libthreadweaver.so.4 #8 0x7f9db3dd875c in ?? () from /usr/lib/libthreadweaver.so.4 #9 0x7f9db3dd722f in ThreadWeaver::Thread::run() () from /usr/lib/libthreadweaver.so.4 #10 0x7f9db7aa270f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #11 0x7f9db653f0a4 in start_thread (arg=0x7f9d7bfff700) at pthread_create.c:309 #12 0x7f9db745862d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 14 (Thread 0x7f9d7b7fe700 (LWP 12790)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f9db7aa2c66 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f9db3dd586c in ?? () from /usr/lib/libthreadweaver.so.4 #3 0x7f9db3dd8743 in ?? () from /usr/lib/libthreadweaver.so.4 #4 0x7f9db3dd875c in ?? () from /usr/lib/libthreadweaver.so.4 #5 0x7f9db3dd875c in ?? () from /usr/lib/libthreadweaver.so.4 #6 0x7f9db3dd875c in ?? () from /usr/lib/libthreadweaver.so.4 #7 0x7f9db3dd875c in ?? () from /usr/lib/libthreadweaver.so.4 #8
[kdev-python] [Bug 373349] KDevelop Crash on recent keywords (Python) [Python::PythonCodeCompletionContext::raiseItems, KDevelop::DUContext::findDeclarations]
https://bugs.kde.org/show_bug.cgi?id=373349
--- Comment #2 from robert <robert.buchin...@gmail.com> ---
Hi Sven
For example when i try to code this:
#a lot of code above
fieldvalues = {}
fieldtext = {}
try:
cur = dbcon.cursor()
cur.execute("select options from table where ID=%s",(fieldID,))
res = cur.fetchall()
except Exception as e:
print str(e)
#a lot of code below
it crashes immediately after entering the word "except"
this piece of code is part of a (closed source) project with about 900 lines of
code
After each crash, Kdevelop tries to recover the code, but fails with the same
result when recovering
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 373349] New: KDevelop Crash on recent keywords (Python)
https://bugs.kde.org/show_bug.cgi?id=373349 Bug ID: 373349 Summary: KDevelop Crash on recent keywords (Python) Product: kdevelop Version: 5.0.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: robert.buchin...@gmail.com Target Milestone: --- Application: kdevelop (5.0.3) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.8.11-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Kdevelop crashes when entered keywords like "raise" or "except" The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb43b045800 (LWP 7620))] Thread 14 (Thread 0x7fb3c37fe700 (LWP 7721)): #0 0x7fb43172a10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb429964ac4 in () at /usr/lib/libQt5Script.so.5 #2 0x7fb429964b09 in () at /usr/lib/libQt5Script.so.5 #3 0x7fb431724454 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fb437e587df in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7fb3e27fc700 (LWP 7699)): #0 0x7ffe525e1b02 in clock_gettime () #1 0x7fb437e656b6 in clock_gettime () at /usr/lib/libc.so.6 #2 0x7fb4385e81a1 in () at /usr/lib/libQt5Core.so.5 #3 0x7fb43876f3a9 in QTimerInfoList::updateCurrentTime() () at /usr/lib/libQt5Core.so.5 #4 0x7fb43876f955 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/libQt5Core.so.5 #5 0x7fb438770cfe in () at /usr/lib/libQt5Core.so.5 #6 0x7fb42f734c89 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #7 0x7fb42f7356ab in () at /usr/lib/libglib-2.0.so.0 #8 0x7fb42f73589c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #9 0x7fb43877172b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #10 0x7fb43871b23a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #11 0x7fb43853e0f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #12 0x7fb438542d78 in () at /usr/lib/libQt5Core.so.5 #13 0x7fb431724454 in start_thread () at /usr/lib/libpthread.so.0 #14 0x7fb437e587df in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7fb3e2ffd700 (LWP 7686)): #0 0x7fb43172a10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb438543c2b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fb42ce3e1c0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fb42ce42988 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fb42ce3d263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fb42ce429e2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fb42ce3d263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7fb42ce401f9 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7fb438542d78 in () at /usr/lib/libQt5Core.so.5 #9 0x7fb431724454 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fb437e587df in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7fb3e37fe700 (LWP 7685)): #0 0x7fb43172a10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb438543c2b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fb42ce3e1c0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fb42ce42988 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fb42ce3d263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fb42ce429e2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fb42ce3d263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7fb42ce401f9 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7fb438542d78 in () at /usr/lib/libQt5Core.so.5 #9 0x7fb431724454 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fb437e587df in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7fb3e3fff700 (LWP 7684)): #0 0x7fb43172a10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb438543c2b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fb42ce3e1c0 in
[skrooge] [Bug 373147] Dashboard/Scheduled operations typo
https://bugs.kde.org/show_bug.cgi?id=373147 --- Comment #4 from Robert Natkay <natkay.rob...@nrcode.com> --- I have attached the screenshots of the dashboard and my scheduled tr.list. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 373147] Dashboard/Scheduled operations typo
https://bugs.kde.org/show_bug.cgi?id=373147 --- Comment #3 from Robert Natkay <natkay.rob...@nrcode.com> --- Created attachment 102575 --> https://bugs.kde.org/attachment.cgi?id=102575=edit my scheduled transactions -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 373147] Dashboard/Scheduled operations typo
https://bugs.kde.org/show_bug.cgi?id=373147 --- Comment #2 from Robert Natkay <natkay.rob...@nrcode.com> --- Created attachment 102574 --> https://bugs.kde.org/attachment.cgi?id=102574=edit dashboard -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 373147] New: Dashboard/Scheduled operations typo
https://bugs.kde.org/show_bug.cgi?id=373147 Bug ID: 373147 Summary: Dashboard/Scheduled operations typo Product: skrooge Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: natkay.rob...@nrcode.com CC: steph...@mankowski.fr Target Milestone: --- Hello! I have added the scheduled operations to my dashboard and noticed, that the 1st character of the name of operation is missing. i have "oan" instead of "Loan", etc. Not a big deal, keep up the good work! Robert Skrooge version: v2.5.0 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 363298] Allow users to define custom stamp to use with the review functions.
https://bugs.kde.org/show_bug.cgi?id=363298 --- Comment #4 from Robert Cabane <rcab...@free.fr> --- As of Okular 0.24, it's really possible to create personal stamps, see here : https://wiki.ubuntuusers.de/Okular/ However, the exported PDF file doesn't show the personal stamps with any other viewer as Okular (tested with Evince and the pdf viewers included in FireFox or Chrome). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 159007] Personal gallery od stamps
https://bugs.kde.org/show_bug.cgi?id=159007 Robert Cabane <rcab...@free.fr> changed: What|Removed |Added CC||rcab...@free.fr --- Comment #9 from Robert Cabane <rcab...@free.fr> --- (In reply to kdebug from comment #8) > There is a way now to add a custom image (svg, png) to a stamp (description > here -> http://wiki.ubuntuusers.de/Okular) > With "Save as.." it is even possible to write annotations down to the > PDF-file. > > Unfortunately, those notifications are not shown by common PDF Viewers > (Adobe Reader, PDF-Master,...) Neither it is possible to print them to a new > PDf File (which seems to work just for text-annotations) I agree. Just the same with Okular 0.24 (under OpenSuSE) : the stamp is really included in the exported PDF file (whose size grows), but in a special manner, which isn't compatible with Adobe Reader. Hopefully one will find how to fix that ... -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 372343] New: search stops working after muon is first used to install a package
https://bugs.kde.org/show_bug.cgi?id=372343 Bug ID: 372343 Summary: search stops working after muon is first used to install a package Product: muon Version: 5.6 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: muon Assignee: echidna...@kubuntu.org Reporter: rjst...@talk21.com CC: silh...@gmail.com Target Milestone: --- The muon search bar works correctly when the application is first started but after something has been installed, all searches will return no results. Restarting the application fixes the problem. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 371460] ANDs get converted to ORs when editing the filter
https://bugs.kde.org/show_bug.cgi?id=371460 --- Comment #2 from robert marshall <rob...@capuchin.co.uk> --- As I said in irc I've not used OR much before so couldn't comment as to whether the problem is new - however after testing the the version of amarok that comes with 16.04 - 2.8.0 - I can replicate this problem there -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 368884] Kscreenlocker locks screen for ever! (a critical bug)
https://bugs.kde.org/show_bug.cgi?id=368884 --- Comment #14 from Robert Anderson <r...@sr.unh.edu> --- I do have an Nvidia card. I also attempted to get the debugging trace but failed. In order to get the trace I needed to install another rpm. That installed a few packages. After which everything worked again. So I can no longer reproduce the error. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 368884] Kscreenlocker locks screen for ever! (a critical bug)
https://bugs.kde.org/show_bug.cgi?id=368884 Robert Anderson <r...@sr.unh.edu> changed: What|Removed |Added CC||r...@sr.unh.edu --- Comment #11 from Robert Anderson <r...@sr.unh.edu> --- I before and last time an rpm update solved it. At this time I cannot use the lockscreen or logout correctly. Lockscreen just returns me to the lockscreen. Running with --testing yeilds an error as soon as I type my password. Logging into a virtual terminal and running the unlock-session does work. I have tried different themes but have not stumbled upon a working combination. [rea@q ~]$ /usr/libexec/kscreenlocker_greet --testing Locked at 1477515185 file:///usr/share/plasma/look-and-feel/org.fedoraproject.fedora.twenty.four/contents/components/InfoPane.qml:54:22: Unable to assign [undefined] to int file:///usr/share/plasma/look-and-feel/org.fedoraproject.fedora.twenty.four/contents/components/UserDelegate.qml:82:9: QML Image: Cannot open: file:///usr/share/plasma/look-and-feel/org.fedoraproject.fedora.twenty.four/contents/components/system-log-out file:///usr/share/plasma/look-and-feel/org.fedoraproject.fedora.twenty.four/contents/components/UserDelegate.qml:82:9: QML Image: Cannot open: file:///usr/share/plasma/look-and-feel/org.fedoraproject.fedora.twenty.four/contents/components/system-switch-user KCrash: Application 'kscreenlocker_greet' crashing... Segmentation fault (core dumped) [rea@q ~]$ rpm -qa | grep screenlocker kscreenlocker-5.7.5-1.fc24.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 371460] New: ANDs get converted to ORs when editing the filter
https://bugs.kde.org/show_bug.cgi?id=371460 Bug ID: 371460 Summary: ANDs get converted to ORs when editing the filter Product: amarok Version: 2.8-git Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Collection Browser Assignee: amarok-bugs-d...@kde.org Reporter: rob...@capuchin.co.uk Set up a filter containing (for example) artist:"Sol" AND genre:"Classic" OR genre:"Chamber" then click the edit filter button, the search filter displays correctly (at the foot of the dialog but the graphic buttons has two ANDs rather than AND and then OR, if without doing anything to amend the filter you select OK you get an edited filter artist:"Sol" AND genre:"Classic" AND genre:"Chamber" I didn't expect the filter to change. I tried to work around by adding brackets in case it was an operator precedence issue but that made no difference (as reported on #amarok on IRC with a slightly different example) Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 371459] New: System Settings > Display & Monitor: crash every time
https://bugs.kde.org/show_bug.cgi?id=371459 Bug ID: 371459 Summary: System Settings > Display & Monitor: crash every time Product: systemsettings Version: 5.6.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kde.bug.tracking.sys...@marksim.org Application: systemsettings5 (5.6.5) Qt Version: 5.5.1 Frameworks Version: 5.23.0 Operating System: Linux 4.8.3-040803-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: opened "System Settings" clicked on "Display & Monitor" - Custom settings of the application: no, but upgraded nvidia to 370 before (still not rebooted), The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9f9e4848c0 (LWP 1611))] Thread 3 (Thread 0x7f9f7c271700 (LWP 1650)): #0 0x7f9f9abb0e8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f9f978ca39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9f978ca4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9f9b4dda9b in QEventDispatcherGlib::processEvents (this=0x7f9f740008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f9f9b484dea in QEventLoop::exec (this=this@entry=0x7f9f7c270ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f9f9b2a18a4 in QThread::exec (this=this@entry=0x1f1be90) at thread/qthread.cpp:503 #6 0x7f9f99c1b3c5 in QQmlThreadPrivate::run (this=0x1f1be90) at qml/ftw/qqmlthread.cpp:141 #7 0x7f9f9b2a684e in QThreadPrivate::start (arg=0x1f1be90) at thread/qthread_unix.cpp:331 #8 0x7f9f97deb6fa in start_thread (arg=0x7f9f7c271700) at pthread_create.c:333 #9 0x7f9f9abbcb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f9f8da70700 (LWP 1621)): #0 0x7f9f9abb0e8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f9f98661c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f9f986638d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f9f903f4629 in QXcbEventReader::run (this=0x1b1aeb0) at qxcbconnection.cpp:1253 #4 0x7f9f9b2a684e in QThreadPrivate::start (arg=0x1b1aeb0) at thread/qthread_unix.cpp:331 #5 0x7f9f97deb6fa in start_thread (arg=0x7f9f8da70700) at pthread_create.c:333 #6 0x7f9f9abbcb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f9f9e4848c0 (LWP 1611)): [KCrash Handler] #6 0x7f9f9aaeb418 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f9f9aaed01a in __GI_abort () at abort.c:89 #8 0x7f9f9b293ff1 in qt_message_fatal (context=..., message=) at global/qlogging.cpp:1578 #9 QMessageLogger::fatal (this=this@entry=0x7fffce74cf20, msg=msg@entry=0x7f9f9a0572c5 "%s") at global/qlogging.cpp:781 #10 0x7f9f99ed3af1 in QSGRenderLoop::handleContextCreationFailure (this=this@entry=0x1f24820, window=0x1f20080, isEs=isEs@entry=false) at scenegraph/qsgrenderloop.cpp:244 #11 0x7f9f99edc332 in QSGThreadedRenderLoop::handleExposure (this=this@entry=0x1f24820, window=window@entry=0x1f20080) at scenegraph/qsgthreadedrenderloop.cpp:919 #12 0x7f9f99edc733 in QSGThreadedRenderLoop::exposureChanged (this=0x1f24820, window=0x1f20080) at scenegraph/qsgthreadedrenderloop.cpp:857 #13 0x7f9f9c3b82f5 in QWindow::event (this=this@entry=0x1f20080, ev=ev@entry=0x7fffce74d380) at kernel/qwindow.cpp:2060 #14 0x7f9f99f0f871 in QQuickWindow::event (this=0x1f20080, e=0x7fffce74d380) at items/qquickwindow.cpp:1413 #15 0x7f9f9c96005c in QApplicationPrivate::notify_helper (this=this@entry=0x1aff2e0, receiver=receiver@entry=0x1f20080, e=e@entry=0x7fffce74d380) at kernel/qapplication.cpp:3716 #16 0x7f9f9c965516 in QApplication::notify (this=0x7fffce74d760, receiver=0x1f20080, e=0x7fffce74d380) at kernel/qapplication.cpp:3499 #17 0x7f9f9b48762b in QCoreApplication::notifyInternal (this=0x7fffce74d760, receiver=receiver@entry=0x1f20080, event=event@entry=0x7fffce74d380) at kernel/qcoreapplication.cpp:965 #18 0x7f9f9c3b04ec in QCoreApplication::sendSpontaneousEvent (event=0x7fffce74d380, receiver=0x1f20080) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:227 #19 QGuiApplicationPrivate::processExposeEvent (e=0x20185d0) at kernel/qguiapplication.cpp:2663 #20 0x7f9f9c3b125d in QGuiApplicationPrivate::processWindowSystemEvent (e=e@entry=0x20185d0) at kernel/qguiapplication.cpp:1658 #21 0x7f9f9c394f38 in QWindowSystemInterface::sendWindowSystemEvents (flags=...) at
[dolphin] [Bug 371458] New: Dolphin - Changing View Properties
https://bugs.kde.org/show_bug.cgi?id=371458 Bug ID: 371458 Summary: Dolphin - Changing View Properties Product: dolphin Version: 16.08.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: agontec...@gmail.com Application: dolphin (16.08.2) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.8.2-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Changed view properties successfully, but when applied to sub-folders Dolphin quit. Repeated behavior when attempted again with same result The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5fe29187c0 (LWP 1024))] Thread 4 (Thread 0x7f5fc1ff9700 (LWP 1028)): #0 0x7f5fd58bdc12 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #1 0x7f5fd58be6ab in () at /usr/lib/libglib-2.0.so.0 #2 0x7f5fd58be89c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f5fdc3ca72b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f5fdc37423a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f5fdc1970f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f5fdc19bd78 in () at /usr/lib/libQt5Core.so.5 #7 0x7f5fd79fc454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f5fe22647df in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f5fc9f93700 (LWP 1027)): #0 0x7f5fd58bdc12 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #1 0x7f5fd58be6ab in () at /usr/lib/libglib-2.0.so.0 #2 0x7f5fd58be89c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f5fdc3ca72b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f5fdc37423a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f5fdc1970f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f5fdc7dbe55 in () at /usr/lib/libQt5DBus.so.5 #7 0x7f5fdc19bd78 in () at /usr/lib/libQt5Core.so.5 #8 0x7f5fd79fc454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f5fe22647df in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f5fcc169700 (LWP 1026)): #0 0x7f5fe225b48d in poll () at /usr/lib/libc.so.6 #1 0x7f5fd4ff58e0 in () at /usr/lib/libxcb.so.1 #2 0x7f5fd4ff7679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7f5fce6dd449 in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7f5fdc19bd78 in () at /usr/lib/libQt5Core.so.5 #5 0x7f5fd79fc454 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f5fe22647df in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f5fe29187c0 (LWP 1024)): [KCrash Handler] #6 0x7f5fb0be3b94 in () at /usr/lib/libQtGui.so.4 #7 0x7f5fe280c4fa in call_init.part () at /lib64/ld-linux-x86-64.so.2 #8 0x7f5fe280c60b in _dl_init () at /lib64/ld-linux-x86-64.so.2 #9 0x7f5fe2810b38 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2 #10 0x7f5fe280c3a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2 #11 0x7f5fe28102d9 in _dl_open () at /lib64/ld-linux-x86-64.so.2 #12 0x7f5fd5b87ee9 in () at /usr/lib/libdl.so.2 #13 0x7f5fe280c3a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2 #14 0x7f5fd5b88521 in () at /usr/lib/libdl.so.2 #15 0x7f5fd5b87f82 in dlopen () at /usr/lib/libdl.so.2 #16 0x7f5fc07eabb0 in () at /usr/lib/libvlccore.so.8 #17 0x7f5fc07ceebb in () at /usr/lib/libvlccore.so.8 #18 0x7f5fc07cf1e8 in () at /usr/lib/libvlccore.so.8 #19 0x7f5fc07cf144 in () at /usr/lib/libvlccore.so.8 #20 0x7f5fc07cf6c4 in () at /usr/lib/libvlccore.so.8 #21 0x7f5fc07cfcca in () at /usr/lib/libvlccore.so.8 #22 0x7f5fc0755eb1 in libvlc_InternalInit () at /usr/lib/libvlccore.so.8 #23 0x7f5fc0526cee in libvlc_new () at /usr/lib/libvlc.so.5 #24 0x7f5fc0a872c8 in () at /usr/lib/qt5/plugins/phonon4qt5_backend/phonon_vlc.so #25 0x7f5fc0a5c586 in () at /usr/lib/qt5/plugins/phonon4qt5_backend/phonon_vlc.so #26 0x7f5fc0a8b195 in qt_plugin_instance () at /usr/lib/qt5/plugins/phonon4qt5_backend/phonon_vlc.so #27 0x7f5fdc35ecdb in QPluginLoader::instance() () at /usr/lib/libQt5Core.so.5 #28 0x7f5fdda16180 in () at /usr/lib/libphonon4qt5.so.4 #29 0x7f5fdda18ada in () at /usr/lib/libphonon4qt5.so.4 #30 0x7f5fdda19179 in () at /usr/lib/libphonon4qt5.so.4 #31 0x7f5fdda19aa4 in Phonon::Factory::backend(bool) () at /usr/lib/libphonon4qt5.so.4 #32 0x7f5fdda1a339 in () at /usr/lib/libphonon4qt5.so.4 #33 0x7f5fdda0e031 in () at
[krita] [Bug 369480] Preset choosing bugs: stylus tip-presets don't switch properly, / key broken
https://bugs.kde.org/show_bug.cgi?id=369480 --- Comment #3 from Robert <rggor...@gmail.com> --- I am also experiencing this same bug with the git master build 3.0.90 I see the link Boudenwijn posted, but I have no idea how to apply it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369480] Preset choosing bugs: stylus tip-presets don't switch properly, / key broken
https://bugs.kde.org/show_bug.cgi?id=369480 Robert <rggor...@gmail.com> changed: What|Removed |Added CC||rggor...@gmail.com --- Comment #2 from Robert <rggor...@gmail.com> --- I am also experiencing this same bug with the git master build 3.0.90 I see the link Boudenwijn posted, but I have no idea how to apply it. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 370651] Dependency lines not shown correctly
https://bugs.kde.org/show_bug.cgi?id=370651 --- Comment #1 from Robert Hairgrove <c...@roberthairgrove.com> --- Now I see that this depends on the "Style" and "Use fill" properties. If I change the line color to black and uncheck "Use fill", the dotted line shows correctly. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 370651] New: Dependency lines not shown correctly
https://bugs.kde.org/show_bug.cgi?id=370651 Bug ID: 370651 Summary: Dependency lines not shown correctly Product: umbrello Version: 2.18.3 (KDE Applications 15.12.3) Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: c...@roberthairgrove.com When I draw a dependency in a class diagram, it should be shown as a dotted line and not a solid line. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 370607] How to add contents to packages in class diagram?
https://bugs.kde.org/show_bug.cgi?id=370607 --- Comment #6 from Robert Hairgrove <c...@roberthairgrove.com> --- Thank you, Ralf, for responding so quickly! Another thing: once I have a package, I can add a new class to it by setting the "Package path" property in the properties dialog of the new class. So ... it's not so difficult after all. :) However, it would be more intuitive if i could add existing classes to a package in the properties dialog of the package (at least to me). -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 370607] How to add contents to packages in class diagram?
https://bugs.kde.org/show_bug.cgi?id=370607 --- Comment #2 from Robert Hairgrove <c...@roberthairgrove.com> --- (In reply to Robert Hairgrove from comment #1) > In the meanwhile, I discovered that I can add classes to a package (AKA > namespace), but I cannot add an ordinary datatype to a package. Forgot to mention that I did this by dragging the class in the Tree View to the package. Doesn't seem to work that way in the class diagram itself. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 370607] How to add contents to packages in class diagram?
https://bugs.kde.org/show_bug.cgi?id=370607 --- Comment #1 from Robert Hairgrove <c...@roberthairgrove.com> --- In the meanwhile, I discovered that I can add classes to a package (AKA namespace), but I cannot add an ordinary datatype to a package. What I would like to do is to build a package for the STL types I am using ... there anren't very many of those, so I wouldn't have to have the entire STL imported into my project. But it would be useful for types such as std::vector, std::string, std::map, and perhaps a few more. Or is there a better way to do this? -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 370607] New: How to add contents to packages in class diagram?
https://bugs.kde.org/show_bug.cgi?id=370607 Bug ID: 370607 Summary: How to add contents to packages in class diagram? Product: umbrello Version: 2.18.3 (KDE Applications 15.12.3) Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: c...@roberthairgrove.com Using Umbrello version 2.18.3 on Ubuntu 16.04.x LTS. After adding a package in a C++ class diagram (with or without a stereotype <>), I cannot populate its "Contents" with classes or other types (datatypes, interfaces, etc.) There is no button "Add...", and right-clicking in the empty "Contents" box gives me no such option. It remains empty. The documentation offers no help whatsoever here. What good is a namespace if it has no classes? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 365752] crash during typing
https://bugs.kde.org/show_bug.cgi?id=365752 --- Comment #1 from Robert Ikanov <robert.ika...@gmail.com> --- Created attachment 101502 --> https://bugs.kde.org/attachment.cgi?id=101502=edit New crash information added by DrKonqi kdevelop (4.7.3) on KDE Platform 4.14.24 using Qt 4.8.7 - What I was doing when the application crashed: I tried to define a constructor by using initialization list and the software crashed right after typing ':' character. -- Backtrace (Reduced): #6 0x7fd4eb57f66c in KDevelop::AbstractType::indexed() const () at /usr/lib64/libkdevplatformlanguage.so.8 #7 0x7fd43c5b5538 in (anonymous namespace)::getDeclarationSignature(KDevelop::Declaration const*, KDevelop::DUContext const*, bool) (functionDecl=functionDecl@entry=0x4dc8270, functionCtxt=, includeDefaults=includeDefaults@entry=true) at /usr/src/debug/kdevelop-4.7.3/languages/cpp/codegen/adaptsignatureassistant.cpp:67 #8 0x7fd43c5b5e4f in Cpp::AdaptSignatureAssistant::textChanged(KTextEditor::View*, KTextEditor::Range const&, QString const&) (this=0x3aebcd0, view=, invocationRange=..., removedText=...) at /usr/src/debug/kdevelop-4.7.3/languages/cpp/codegen/adaptsignatureassistant.cpp:157 #9 0x7fd4eb47d891 in KDevelop::StaticAssistantsManager::Private::eventuallyStartAssistant() () at /usr/lib64/libkdevplatformlanguage.so.8 #10 0x7fd4eccef2f1 in QObject::event(QEvent*) () at /usr/lib64/libQtCore.so.4 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 365752] crash during typing
https://bugs.kde.org/show_bug.cgi?id=365752 Robert Ikanov <robert.ika...@gmail.com> changed: What|Removed |Added CC||robert.ika...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363487] brush lags behind when making quick or long strokes
https://bugs.kde.org/show_bug.cgi?id=363487 --- Comment #18 from Robert Showalter <show...@gmail.com> --- Thank you for checking Boudewijn. I did more tests and discovered it happens for some brushes, but not others. I suspect it's the brush spacing that reveals the bottleneck. When using the circle brush presets for example, a standard one like "Fill_circle" does not have discernible lag when 5 layers deep (a paint layer within 4 nested groups, that is). However, when I use another present like "ink_circle_10" the lag is significant when nested in groups, but non-existent outside of them. One of the main differences between the two is that the first one has spacing set to auto and the second's spacing is <1. Come to think of it, when I first noticed the problem I was using David Revoy's 8.1 brush presets (http://www.davidrevoy.com/article319/krita-brushkit-v8), many of which have brush spacing <1. Sure enough, when I set spacing to "auto" for "ink_circle_10," indeed the lag goes away (unfortunately, this alters the look for many brushes). This whole thing wouldn't be a problem, except that so many standard brushes have tight spacing and will not work well when nested. That is, if you can reproduce it with the same brush and it's not something with my setup. I'd be curious to know. I went a head and recorded my screen to show the problem (forgive me for using my phone, I wanted to be sure there's no question about screen recording taxing the system). https://drive.google.com/open?id=0BxKOKqLVyGC-QUR2OWZtVXp3RGs As you can see in the video, I'm using the circle brush preset, "ink_circle_10." It's a simple setup as I mentioned before; A 2k square image with 4 nested groups containing a paint layer, and one un-nested paint layer for comparison. Here's the file for safe measure: https://drive.google.com/open?id=0BxKOKqLVyGC-eXQwZGJ4Um44TEU -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363487] brush lags behind when making quick or long strokes
https://bugs.kde.org/show_bug.cgi?id=363487 --- Comment #16 from Robert Showalter <show...@gmail.com> --- (In reply to Boudewijn Rempt from comment #15) > Given that the original poster reported that it was a problem with his video > card driver, you're not having the same problem. Thank you for the response, Boudewijin. I was under the impression that the original poster had incorrectly assumed that it was the video card driver. (William Kensinger from comment #11) >It would appear that the driver update didn't solve the issue. I'm new to bug reporting and I didn't want to create a duplicate bug. Thank you, as well, for the information about the layer rendering. I was unaware of that bottleneck and that explains a lot. > Whether it's too slow to be usable or not depends on your system's > specifications. My machine has 32 gigs of ram, I'm using a GTX 970 with the latest driver, and I'm using a separate SSD for the swap file. Even in a blank file with just 4 groups, a simple brush becomes unusable (and yes, I've tried toggling off OpenGL and made sure instant preview mode is disabled). Now that I'm aware of this limitation, I no longer utilize nested groups. Krita is fantastic, and I'm really impressed with it, but that seemed like very unexpected behavior, which is why I wanted to join this community and mention what I thought was a bug. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 364924] Kdevelop crashes when editing code [Cpp::getMatchQuality, KDevelop::AbstractType::indexed]
https://bugs.kde.org/show_bug.cgi?id=364924 --- Comment #3 from Robert Ikanov <robert.ika...@gmail.com> --- Created attachment 101409 --> https://bugs.kde.org/attachment.cgi?id=101409=edit New crash information added by DrKonqi kdevelop (4.7.3) on KDE Platform 4.14.24 using Qt 4.8.7 - What I was doing when the application crashed: Typing a variable name and Kdevelop crashed right before offering completion. -- Backtrace (Reduced): #6 0x7f5841d1566c in KDevelop::AbstractType::indexed() const () at /usr/lib64/libkdevplatformlanguage.so.8 #7 0x7f578f301eff in Cpp::getMatchQuality(Cpp::CodeCompletionContext*, KDevelop::Declaration const*, KDevelop::TopDUContext*) (context=, decl=0x7f5771646220, top=0x7f577004b740) at /usr/src/debug/kdevelop-4.7.3/languages/cpp/codecompletion/item.cpp:114 #8 0x7f578f30307d in Cpp::NormalDeclarationCompletionItem::data(QModelIndex const&, int, KDevelop::CodeCompletionModel const*) const (this=0x7f57880569c0, index=..., role=, model=0x347e240) at /usr/src/debug/kdevelop-4.7.3/languages/cpp/codecompletion/item.cpp:538 #9 0x7f5841d6227d in KDevelop::CodeCompletionModel::data(QModelIndex const&, int) const () at /usr/lib64/libkdevplatformlanguage.so.8 #10 0x7f5796377ab9 in KateCompletionModel::contextMatchQuality(QPair<KTextEditor::CodeCompletionModel*, QModelIndex> const&) const () at /usr/lib64/libkatepartinterfaces.so.4 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 364924] Kdevelop crashes when editing code [Cpp::getMatchQuality, KDevelop::AbstractType::indexed]
https://bugs.kde.org/show_bug.cgi?id=364924 Robert Ikanov <robert.ika...@gmail.com> changed: What|Removed |Added CC||robert.ika...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363487] brush lags behind when making quick or long strokes
https://bugs.kde.org/show_bug.cgi?id=363487 Robert Showalter <show...@gmail.com> changed: What|Removed |Added CC||show...@gmail.com --- Comment #14 from Robert Showalter <show...@gmail.com> --- Is this issue considered to be resolved in 3.0.1? Because I can confirm this problem on windows 7 with Krita 3.0.1 On a 2048 x 2048 px image, if I create a new paint layer and draw with the brush, it's fine. However, if I create 4 nested groups with a paint layer within the last group when I make a brush stroke there's a severe lag. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365739] Layer name text deselects after one second when hiding, showing then renaming a layer
https://bugs.kde.org/show_bug.cgi?id=365739 Robert Showalter <show...@gmail.com> changed: What|Removed |Added CC||show...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 369641] Render time improperly displayed on Ubuntu 16.04
https://bugs.kde.org/show_bug.cgi?id=369641 --- Comment #4 from Robert Orzanna <orsch...@gmail.com> --- Yes, I did. orschiro@x230:~$ dpkg -l | grep breeze # grep deb package ii breeze-icon-theme4:5.18.0-0ubuntu1 amd64Default Plasma icon theme. ii kde-style-breeze 4:5.5.5-0ubuntu1 amd64Widget style for Qt and KDE Software ii kde-style-breeze-qt4 4:5.5.5-0ubuntu1 amd64Widget style for Qt 4 and KDE Software ii libreoffice-style-breeze 1:5.2.2-0ubuntu1~xenial0all office productivity suite -- Breeze symbol style ii qml-module-qtquick-controls-styles-breeze4:5.5.5-0ubuntu1 amd64QtQuick style for Qt and KDE Software -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 369641] Render time improperly displayed on Ubuntu 16.04
https://bugs.kde.org/show_bug.cgi?id=369641 --- Comment #2 from Robert Orzanna <orsch...@gmail.com> --- Hi, It's Ubuntu Unity 16.04. Please let me know if I can provide you with something else. Thanks! -Robert -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 369642] Feature request to replace a clip
https://bugs.kde.org/show_bug.cgi?id=369642 --- Comment #2 from Robert Orzanna <orsch...@gmail.com> --- Hi, In the timeline. I am sorry for the broken link! Please see this: http://i.imgur.com/J28fBSD.png -Robert -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 348194] kactivitymanager sometimes crashes on logout
https://bugs.kde.org/show_bug.cgi?id=348194 Robert G. Siebeck <kde.bugzilla.2...@r123.de> changed: What|Removed |Added CC||kde.bugzilla.2...@r123.de -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 351985] kactivitymanage segfault
https://bugs.kde.org/show_bug.cgi?id=351985 Robert G. Siebeck <kde.bugzilla.2...@r123.de> changed: What|Removed |Added CC||kde.bugzilla.2...@r123.de -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 369642] New: Feature request to replace a clip
https://bugs.kde.org/show_bug.cgi?id=369642 Bug ID: 369642 Summary: Feature request to replace a clip Product: kdenlive Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: orsch...@gmail.com Dear all, What do you think of a context menu entry to replace a clip with another one and thus keeping the current position and length of the previously replaced clip? Screenshot: blob:http://imgur.com/2d78a748-65f3-40aa-81da-ce0a3d9cf126 Thankfully, -Robert Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 369641] New: Render time improperly displayed on Ubuntu 16.04
https://bugs.kde.org/show_bug.cgi?id=369641 Bug ID: 369641 Summary: Render time improperly displayed on Ubuntu 16.04 Product: kdenlive Version: 16.08.1 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: orsch...@gmail.com Dear all, I noticed the following graphical bug regarding displaying render time. Screenshot: http://i.imgur.com/YUKZhG8.png Please let me know if I can provide you more information. Thankfully, -Robert Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 173896] Sent-to menu entry or send-via-email menu-entry
https://bugs.kde.org/show_bug.cgi?id=173896 Robert Kehl <robertk...@robertkehl.de> changed: What|Removed |Added CC|robertk...@robertkehl.de| --- Comment #25 from Robert Kehl <robertk...@robertkehl.de> --- Forget about the idea, nobody needs it apparantly, they are moving to other programs an "apps". -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364438] The preview screen is black when I give play
https://bugs.kde.org/show_bug.cgi?id=364438 --- Comment #5 from Robert <rgru...@gmail.com> --- I've updated the nvidia drivers and it fixed the problem, I guess that some modules may not work as intended after kernel update (the problem with black preview in kdenlive appeared after system upgrade using apt). Hope that my post will help someone experiencing similar issue. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 355441] DAV Resource 16.04.1: Broken state, The item was not deleted on the server.
https://bugs.kde.org/show_bug.cgi?id=355441 --- Comment #16 from Robert Schöftner <r...@unfoo.net> --- actually, RewriteRule ^(.*\.[iv]c[sf])/$ $1 [L,PT] or RewriteRule ^(.*\.ics)/$ $1 [L,PT] RewriteRule ^(.*\.vcf)/$ $1 [L,PT] would be better, as it is either .ics or .vcf -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 367449] Strange shadow in the up left of display when open Amarok
https://bugs.kde.org/show_bug.cgi?id=367449 robert marshall <rob...@capuchin.co.uk> changed: What|Removed |Added CC||rob...@capuchin.co.uk --- Comment #6 from robert marshall <rob...@capuchin.co.uk> --- This looks very like this issue https://bugs.kde.org/show_bug.cgi?id=277830 that I reported a few years back - which eventually went away for no clear reason (and I still no longer see it). I saw it with fluxbox as WM -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364438] The preview screen is black when I give play
https://bugs.kde.org/show_bug.cgi?id=364438 Robert <rgru...@gmail.com> changed: What|Removed |Added CC||rgru...@gmail.com --- Comment #4 from Robert <rgru...@gmail.com> --- Hi there, I have Kdenlive 16.04.3 installed on Kali linux (Linux (x86_64) release 4.6.0-kali1-amd64, nvidia graphic driver) and have same problem as described above. The playback screen is allways black, it does not depend on clip codecs etc. When started from console kdenlive, loaded previously working project with clip on timeline it does not throw any errors: roof@desktop:~$ kdenlive Removing cache at "/home/roof/.cache/kdenlive-thumbs.kcache" OpenGL vendor: "NVIDIA Corporation" OpenGL renderer: "GeForce GTS 450/PCIe/SSE2" OpenGL ARG_SYNC: true OpenGL OpenGLES: false OpenGL vendor: "NVIDIA Corporation" OpenGL renderer: "GeForce GTS 450/PCIe/SSE2" OpenGL ARG_SYNC: true OpenGL OpenGLES: false // / processing file open // / processing file open: validate Opening a document with version 0.94 / 0.94 // / processing file validate ok *** FOUND GUIDES: 0 ** "Creating audio thumbnails (1/2)" "Creating audio thumbnails (2/5)" "Creating audio thumbnails (3/5)" "Creating audio thumbnails (4/5)" "Creating audio thumbnails (5/5)" "Creating audio thumbnails (6/5)" The sound from clip is played properly, but the preview screen stays black no matter what. I've tried different configurations settings, resetting to defaults etc. If you have any questions feel free to ask. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 316107] big regression: kmail IMAP connection and message display problems
https://bugs.kde.org/show_bug.cgi?id=316107 Robert G. Siebeck <kde.bugzilla.2...@r123.de> changed: What|Removed |Added CC||kde.bugzilla.2...@r123.de -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 327513] IMAP server disconnect leads to failure in mail retrieval/corrupt akonadi cache
https://bugs.kde.org/show_bug.cgi?id=327513 Robert G. Siebeck <kde.bugzilla.2...@r123.de> changed: What|Removed |Added CC||kde.bugzilla.2...@r123.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366339] New: startkde interaction with NVIDIA DRIVERS
https://bugs.kde.org/show_bug.cgi?id=366339 Bug ID: 366339 Summary: startkde interaction with NVIDIA DRIVERS Product: plasmashell Version: 5.7.2 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ebou...@bellsouth.net CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.7.2) Qt Version: 5.6.1 Frameworks Version: 5.24.0 Operating System: Linux 4.6.4-201.fc23.x86_64 x86_64 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: - What I was doing when the application crashed Starting kde from a command line screen mode 3 boot. last couple of weeks after 4.6.4-201 kernel, nvidia and xorg updates kde crashes to a 1024x768 screen. xfce4, gnome and cinnamon work normally. Applying the updates on 8/1 the kde startup crashed and then restarted at full screen resolution. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6576996900 (LWP 11691))] Thread 10 (Thread 0x7f656c6fc700 (LWP 11696)): #0 0x7f6583e62b1d in poll () at /lib64/libc.so.6 #1 0x7f6588ecf272 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7f6588ed0ee7 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7f656fdc5039 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7f6584a6d00c in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f65831c061a in start_thread () at /lib64/libpthread.so.0 #6 0x7f6583e6e59d in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f656aeee700 (LWP 11697)): #0 0x7f657f5b9794 in g_mutex_unlock () at /lib64/libglib-2.0.so.0 #1 0x7f657f5750ae in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f657f57529c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f6584c57b5b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f6584c0825a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f6584a68bd4 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f6585351675 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #7 0x7f6584a6d00c in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f65831c061a in start_thread () at /lib64/libpthread.so.0 #9 0x7f6583e6e59d in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f65696b1700 (LWP 11731)): #0 0x7f657f5b9794 in g_mutex_unlock () at /lib64/libglib-2.0.so.0 #1 0x7f657f574bc9 in g_main_context_check () at /lib64/libglib-2.0.so.0 #2 0x7f657f575130 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x7f657f57529c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7f6584c57b5b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f6584c0825a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f6584a68bd4 in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x7f6587d7a7f5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #8 0x7f6584a6d00c in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7f65831c061a in start_thread () at /lib64/libpthread.so.0 #10 0x7f6583e6e59d in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f655bbb5700 (LWP 11859)): #0 0x7f6583e62b1d in poll () at /lib64/libc.so.6 #1 0x7f657f57518c in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f657f57529c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f6584c57b5b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f6584c0825a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f6584a68bd4 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f6587d7a7f5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7f6584a6d00c in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f65831c061a in start_thread () at /lib64/libpthread.so.0 #9 0x7f6583e6e59d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f6559604700 (LWP 11899)): #0 0x7f65831c5b20 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f658a59f2e4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7f658a59f329 in () at /lib64/libQt5Script.so.5 #3 0x7f65831c061a in start_thread () at /lib64/libpthread.so.0 #4 0x7f6583e6e59d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f64ce55d700 (LWP 12170)): #0 0x7f6583e5e70d in read () at /lib64/libc.so.6 #1 0x7f657f5b83f0 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7f657f574c84 in g_main_context_check () at
[krfb] [Bug 356782] krfb stops sending updates after the first frame
https://bugs.kde.org/show_bug.cgi?id=356782 Robert Hollencamp <rhollenc...@gmail.com> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #4 from Robert Hollencamp <rhollenc...@gmail.com> --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351399] Newly started application windows randomly positioned on primary or extended screen
https://bugs.kde.org/show_bug.cgi?id=351399 Robert Kaiser <ka...@kairo.at> changed: What|Removed |Added CC||ka...@kairo.at -- You are receiving this mail because: You are watching all bug changes.
