[plasmashell] [Bug 365970] Demanding attention tasks are not shown on all desktops
https://bugs.kde.org/show_bug.cgi?id=365970 Eike Hein changed: What|Removed |Added CC||kdde.rhn@porcupinefactory.o ||rg --- Comment #4 from Eike Hein --- *** Bug 360740 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360740] Multiple icons highlighted as the active window
https://bugs.kde.org/show_bug.cgi?id=360740 Eike Hein changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #6 from Eike Hein --- "Demands attention" and "active" are two different states, and the above is a separate bug - that was already fixed for 5.7.3 though. *** This bug has been marked as a duplicate of bug 365970 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366292] taskmanager launcher-icons sometimes disappear
https://bugs.kde.org/show_bug.cgi?id=366292 Eike Hein changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Eike Hein --- *** This bug has been marked as a duplicate of bug 365617 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365617] pinned chromium launcher disappears
https://bugs.kde.org/show_bug.cgi?id=365617 Eike Hein changed: What|Removed |Added CC||xapi...@gmx.net --- Comment #28 from Eike Hein --- *** Bug 366292 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356066] crash on exit
https://bugs.kde.org/show_bug.cgi?id=356066 Wegwerf changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #4 from Wegwerf --- Unfortunately, Kdenlive doesn't have the developer resources to support older Kdenlive versions than current stable, dev, and beta branches. At this time this is 16.04 and beta 16.7.90. We're sorry, but there is no more support for Kdenlive 0.9.10 or older. -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 366293] New: crash when deleting folder in krusader datamanager
https://bugs.kde.org/show_bug.cgi?id=366293 Bug ID: 366293 Summary: crash when deleting folder in krusader datamanager Product: Baloo Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Baloo File Daemon Assignee: pinak.ah...@gmail.com Reporter: tobias.teichm...@gmx.at nothing noticeable happened after the crash Reproducible: Sometimes Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #6 0x7fcf31761418 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7fcf3176301a in __GI_abort () at abort.c:89 #8 0x7fcf2ff53002 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #9 0x7fcf2ff486a5 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #10 0x7fcf2ff49863 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #11 0x7fcf2ff49ac9 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #12 0x7fcf2ff4b704 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #13 0x7fcf2ff4f857 in mdb_cursor_del () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #14 0x7fcf2ff50dc0 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #15 0x7fcf329097ae in Baloo::DocumentDataDB::del(unsigned long long) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #16 0x7fcf329231cf in Baloo::WriteTransaction::removeDocument(unsigned long long) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #17 0x00429632 in Baloo::MetadataMover::removeMetadata(Baloo::Transaction*, QString const&) () #18 0x004296cd in Baloo::MetadataMover::removeFileMetadata(QString const&) () #19 0x7fcf32448e4f in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x00432f05 in Baloo::PendingFileQueue::removeFileIndex(QString const&) () #21 0x00427856 in Baloo::PendingFileQueue::processCache() () #22 0x7fcf32448e4f in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7fcf32455878 in QTimer::timerEvent(QTimerEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7fcf32449e53 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7fcf3241a60c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7fcf3246f89d in QTimerInfoList::activateTimers() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7fcf3246fdd9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7fcf2e9be1a7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7fcf2e9be400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x7fcf2e9be4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x7fcf32470a7f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7fcf32417dea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7fcf3241fe8c in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x0041698c in main () -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 358223] Rotoscoping effect crashes kdenlive when played
https://bugs.kde.org/show_bug.cgi?id=358223 --- Comment #7 from Wegwerf --- Noticed that too, so we will keep this report open. Hopefully, the person who stepped forward is able to make progress. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 365839] Unable to open or save a project
https://bugs.kde.org/show_bug.cgi?id=365839 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #2 from Wegwerf --- Ian, not being able to load or save projects is a grave issue. However, this appears to me to be a downstream distro and packaging issue. Using recent git master I cannot reproduce, but then I'm on Kubuntu 16.04. Thus, I would like you to search/ask the Kdenlive and Manjaro forums for help, and maybe file a bug report with your Manjaro packaging of Kdenlive. I would thus also ask you to be so kind as to close this bug report, unless you have good reason as to this being a genuine Kdenlive bug and not a packaging issue. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 366119] git master: only subset of scalable icons installed
https://bugs.kde.org/show_bug.cgi?id=366119 Wegwerf changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #2 from Wegwerf --- Eating my own dog food I'm closing this bug report now, as most Kdenlive users would install into system icon locations anyway. I have found a workaround by copying the underlying Breeze icon theme over to my local icon branch, then copying the newer Kdenlive icons into this local Breeze theme, and finally removing my local icons.kcache (or so). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366294] New: Folderview Widget in Panel: "Create New" creates files/folders in top path, not in current location
https://bugs.kde.org/show_bug.cgi?id=366294 Bug ID: 366294 Summary: Folderview Widget in Panel: "Create New" creates files/folders in top path, not in current location Product: plasmashell Version: 5.7.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: stefanpro...@kolabnow.com CC: plasma-b...@kde.org When creating a new file/folder with folderview as a panel-widget, the new file/folder is created in the path that is set in the settings of the widget, not in the directory that I have navigated to. Reproducible: Always Steps to Reproduce: 1. Place folderview widget in panel with path /foo/ 2. Open folderview widget and navigate to /foo/bar/ 3. Click create new -> textfile -> dmy.txt Actual Results: File is created as /foo/dmy.txt Expected Results: File should be created as /foo/bar/dmy.txt -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 366274] Krunner fails to display & crashes
https://bugs.kde.org/show_bug.cgi?id=366274 --- Comment #2 from nickgnor...@gmail.com --- Yes, but idle. Audacious. The issue has only started in the last 2-3 days. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 365368] git master - opening a particular project (that was made with a past git master build) doesn't have track compositing.
https://bugs.kde.org/show_bug.cgi?id=365368 --- Comment #6 from Wegwerf --- Jesse, using my project Analyzer, I've found many of my projects to have issues with transparent track setup and audio mixing. Luckily, as Jean-Baptiste became aware of the size of this issue, he added to the recent beta 16.7.90 a new behind-the-scenes feature: the "timeline compositing" selector. You should see it in the timeline toolbar, otherwise add it manually. Then switch modes, and Kdenlive will rebuilt all its internally added track compositing transitions from ground up to a sane state. The old track-wise opacity is gone, as it was acting counter-intuitively when switching a track in between to opaque. Please see also here, scroll down to last section: http://thediveo-e.blogspot.de/2016/07/new-kdenlive-transition-composite-and.html If this feature also fixes the bug for you, I would like to ask you to be so kind as to close this report. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 365074] git master: not forcing Breeze Icon Theme causes inconsistent Breeze dark/light icons on Kubuntu
https://bugs.kde.org/show_bug.cgi?id=365074 Wegwerf changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #9 from Wegwerf --- This issue is caused by installing into a local icon branch, instead of system icon banches. This seems always to be a problem, especially as Kdenlive does not set up a new icon theme, but instead installs its own icons and also required thensystem theme, which then may take even precence. Most users will install into system locations anyway. Eating my own dog food, Im closing this report. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 349913] Kdenlive return wrong file name to gimp when you want to edit image clip
https://bugs.kde.org/show_bug.cgi?id=349913 Wegwerf changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||wegwerf-1-...@gmx.de Resolution|--- |FIXED --- Comment #1 from Wegwerf --- Cannot reproduce. Make sure that in "Configure Kdenlive", section "Environment" the image editing application is correctly set, and that your distribution has provided a correctly working wrapping script, if it does so. With recent Kdenlive beta 16.09.30 Gimp opens correctly the image clip from the project bin. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 351167] git master -08-10 clip in timeline not popping to foreground.
https://bugs.kde.org/show_bug.cgi?id=351167 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Wegwerf --- Evert, I cannot reproduce on recent Kdenlive beta 16.07.90. I now that there was some issue some time ago, as I noticed this myself. However in the current beta, clicking on a timeline clip correctly brings it to the front as expected. I'm thus closing this as resolved. If you happen to see this issue again on your system even with the most recent beta or git master, feel free to reopen this report. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 352601] Crash when changing Alpha Channel Operation under Region transition
https://bugs.kde.org/show_bug.cgi?id=352601 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Wegwerf --- Fahad, unfortunately, due to lack of developer resources, only the recent stable Kdenlive version is supported, as are current betas and development versions. Thus, we can't offer any support for Kdenlive other than 16.04.2 and soon 16.08.0. I'm thus closing this rather old bug report. If this bug has somehow crept into Kdenlive 16.04/16.08 please feel free to create a new report, with the usual additional information, such as example project, backtraces, et cetera. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 366274] Krunner fails to display & crashes
https://bugs.kde.org/show_bug.cgi?id=366274 --- Comment #3 from Kai Uwe Broulik --- Did you perhaps update Audacious? Does controlling it through the media controller (play icon next to the clock) crash Plasma? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 359827] 0.9.6 4.13.3, Kubuntu packages - RAM SATURATION WHILE RENDERING HDV VIDEO
https://bugs.kde.org/show_bug.cgi?id=359827 Wegwerf changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Wegwerf --- Unfortunately, Kdenlive versions other than current stable (16.04.2 at this time, soon 16.08.0), current beta, and development versions are no longer maintained due to a lack of developer resources. In case this issue still persists with a recent supported Kdenlive version, feel free to reopen this report with updated description, example project, et cetera. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364734] git-master 2016-06-25: Compiler warnings
https://bugs.kde.org/show_bug.cgi?id=364734 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 347217] KDEnlive 0.9.8 vs 0.9.10
https://bugs.kde.org/show_bug.cgi?id=347217 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de Status|UNCONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED --- Comment #8 from Wegwerf --- Unfortunately, Kdenlive versions other than current stable (16.04.2 at this time, soon 16.08.0), current beta, and development versions are no longer maintained due to a lack of developer resources. In case this issue still persists with a recent supported Kdenlive version, feel free to reopen this report with updated description, example project, et cetera. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 354493] Crash in an old file with Composite transition
https://bugs.kde.org/show_bug.cgi?id=354493 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #1 from Wegwerf --- Aslanex, can you please try with a recent stable version 16.04.2 of Kdenlive, as well as a recent MLT 6.2.0+? If the bug has been fixed, I would like to ask you to be so kind as to close this bug report. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 366282] I can't make a screen shot when spectacle window is opened
https://bugs.kde.org/show_bug.cgi?id=366282 Chao Feng changed: What|Removed |Added CC||chaofeng...@gmail.com --- Comment #1 from Chao Feng --- In PrintScreen method, the Capture mode is Full Screen. So maybe a new full screen is taking but nothing changed. Could you change your screen before step 2 and check if there is new screenshot taken? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 354550] Tracks shorten themselves upon re-opening the project
https://bugs.kde.org/show_bug.cgi?id=354550 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #1 from Wegwerf --- Chris, can you please try with a recent stable version 16.04.2 of Kdenlive, as well as a recent MLT 6.2.0+? If the bug has been fixed, I would like to ask you to be so kind as to close this bug report. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 347539] crashes when importing 1920x1080 clip that is over an hour long, MP4 29.97 fps
https://bugs.kde.org/show_bug.cgi?id=347539 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #2 from Wegwerf --- Shane, can you please try with a recent stable version 16.04.2 of Kdenlive, as well as a recent MLT 6.2.0+? If the bug has been fixed, I would like to ask you to be so kind as to close this bug report. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 348907] Crop, Scale and Position casts a shadow
https://bugs.kde.org/show_bug.cgi?id=348907 Wegwerf changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||wegwerf-1-...@gmx.de --- Comment #2 from Wegwerf --- Axel, can you please try with a recent stable version 16.04.2 of Kdenlive, as well as a recent MLT 6.2.0+? If the bug has been fixed, I would like to ask you to be so kind as to close this bug report. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 357111] Segfault if I set the name of a track and then click away without hitting enter
https://bugs.kde.org/show_bug.cgi?id=357111 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED --- Comment #3 from Wegwerf --- Unfortunately, due to lack of developer resources, only recent stable/beta/dev Kdenlive versions are supported. At the time of this writing, Kdenlive 16.04.2 is current, with beta 16.07.90 in the works. As I also cannot reproduce this bug with a recent beta, and the report is for an old unsupported version, I'm closing this report. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356022] crash at exit
https://bugs.kde.org/show_bug.cgi?id=356022 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #2 from Wegwerf --- Thomas, can you please test using the recent stable Kdenlive 16.04.2 version, with MLT 6.2.0+ at least? Does the bug still persists? If not, I would like to ask you to be so kind as to close this bug report. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 357151] Crashes when trying to render
https://bugs.kde.org/show_bug.cgi?id=357151 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #3 from Wegwerf --- Herve, can you please test using the recent stable Kdenlive 16.04.2 version, with MLT 6.2.0+ at least? Does the bug still persists? If not, I would like to ask you to be so kind as to close this bug report. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356162] .mxf (mpeg2) footage clips are not added completely
https://bugs.kde.org/show_bug.cgi?id=356162 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #8 from Wegwerf --- Thomas, can you please test using the recent stable Kdenlive 16.04.2 version, with MLT 6.2.0+ at least, and ffmpeg 3.0.0+? Does the bug still persists? If not, I would like to ask you to be so kind as to close this bug report. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 354940] Corrupted project after Video Profile change e.g. 1080p50 > 1080p25
https://bugs.kde.org/show_bug.cgi?id=354940 Wegwerf changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||wegwerf-1-...@gmx.de Ever confirmed|0 |1 --- Comment #5 from Wegwerf --- cstark, can you please test using the recent stable Kdenlive 16.04.2 version, with MLT 6.2.0+ at least? Does the bug still persists? If not, I would like to ask you to be so kind as to close this bug report. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 357326] 1326x888 resolution/aspect ratio cause faulty display of videos
https://bugs.kde.org/show_bug.cgi?id=357326 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #10 from Wegwerf --- Qubodup, is this bus still present, or has it been successfully fixed? If it's been fixed, I would like to ask you to be so kind as to close this bug report. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366294] Folderview Widget in Panel: "Create New" creates files/folders in top path, not in current location
https://bugs.kde.org/show_bug.cgi?id=366294 Eike Hein changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Eike Hein --- This is caused by AppletInterface::contextualActionsAboutToShow not firing for popups, so the call to update the location used by the new submenu doesn't run. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 357589] Duplicates video clips and changes durations of audio crossfades
https://bugs.kde.org/show_bug.cgi?id=357589 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Wegwerf --- Barade, unfortunately, due to lack of developer resources, only the current stable/beta/dev versions of Kdenlive are supported, that is, stable 16.04.2 at the time of this writing. Older Kdenlive versions are no longer supported. Can you please upgrade to Kdenlive 16.04.2 on KDE Frameworks 5? Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 357490] Razor cursor inaccurately looks like clip will be cut to right of scissors
https://bugs.kde.org/show_bug.cgi?id=357490 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 357322] Clip Properties: rounded frame rate, b/s vs kb/s, superfluous digit in audio bitrate
https://bugs.kde.org/show_bug.cgi?id=357322 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #6 from Wegwerf --- Qubodup, is this bug report still relevant, or can we close it? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 357855] Upgraded 0.9x project retains previous Project End point, even when clips are deleted.
https://bugs.kde.org/show_bug.cgi?id=357855 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #5 from Wegwerf --- Sam, is this bug still present with the recent stable 16.04.2? If not, can you please be so kind as to close this bug report? Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 357899] A Button that toggles all visual effects on/off
https://bugs.kde.org/show_bug.cgi?id=357899 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 357893] Applications shouldn't override user-specified desktop settings (style)
https://bugs.kde.org/show_bug.cgi?id=357893 Wegwerf changed: What|Removed |Added CC||wegwerf-1-...@gmx.de --- Comment #8 from Wegwerf --- RJVB, is this bug report still relevant? If not, I would like to ask you to be so kind as to close it. Thank you very much for your cooperation! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366294] Folderview Widget in Panel: "Create New" creates files/folders in top path, not in current location
https://bugs.kde.org/show_bug.cgi?id=366294 --- Comment #2 from Eike Hein --- Fix up for review https://git.reviewboard.kde.org/r/128562/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366295] New: Plasma crashed after boot
https://bugs.kde.org/show_bug.cgi?id=366295 Bug ID: 366295 Summary: Plasma crashed after boot Product: plasmashell Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: andrej.zu...@ya.ru CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.1.27-27-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: Plasma desktop crashes every time after boot The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f95789017c0 (LWP 2145))] Thread 7 (Thread 0x7f9560909700 (LWP 2146)): #0 0x7f9571e0cbfd in poll () at /lib64/libc.so.6 #1 0x7f9576d60422 in () at /usr/lib64/libxcb.so.1 #2 0x7f9576d6200f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f956308c3c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f957250732f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f95716160a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f9571e1502d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f955900e700 (LWP 2165)): #0 0x7f957161c79c in __lll_lock_wait () at /lib64/libpthread.so.0 #1 0x7f95716184a4 in _L_lock_986 () at /lib64/libpthread.so.0 #2 0x7f9571618306 in pthread_mutex_lock () at /lib64/libpthread.so.0 #3 0x7f956d908e90 in () at /usr/X11R6/lib64/libGL.so.1 #4 0x7f956d90c41e in () at /usr/X11R6/lib64/libGL.so.1 #5 0x7f956d90c81b in () at /usr/X11R6/lib64/libGL.so.1 #6 0x7f9569f9cfc0 in () at /usr/lib64/tls/libnvidia-tls.so.340.96 #7 0x7f956e52ab60 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f956e4e in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #9 0x7f956e4e9df8 in () at /usr/lib64/libglib-2.0.so.0 #10 0x7f956e4e9f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #11 0x7f9572739d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #12 0x7f95726e0d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #13 0x7f957250261a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #14 0x7f9575816e18 in () at /usr/lib64/libQt5Qml.so.5 #15 0x7f957250732f in () at /usr/lib64/libQt5Core.so.5 #16 0x7f95716160a4 in start_thread () at /lib64/libpthread.so.0 #17 0x7f9571e1502d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f954d6b5700 (LWP 2178)): #0 0x7f956e52bd14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f956e4e94a0 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f956e4e9d80 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f956e4e9f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f9572739d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f95726e0d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f957250261a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f9575816e18 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7f957250732f in () at /usr/lib64/libQt5Core.so.5 #9 0x7f95716160a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f9571e1502d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f9547da3700 (LWP 2179)): #0 0x7f9571e08ccd in read () at /lib64/libc.so.6 #1 0x7f9569f9cf45 in () at /usr/lib64/tls/libnvidia-tls.so.340.96 #2 0x7f956e52ab60 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f956e4e in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x7f956e4e9df8 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7f956e4e9f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7f9572739d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f95726e0d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7f957250261a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #9 0x7f9575816e18 in () at /usr/lib64/libQt5Qml.so.5 #10 0x7f957250732f in () at /usr/lib64/libQt5Core.so.5 #11 0x7f95716160a4 in start_thread () at /lib64/libpthread.so.0 #12 0x7f9571e1502d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f9546400700 (LWP 2181)): #0 0x7f957161a03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f9577fe586b in () at /usr/lib64/libQt5Script.so.5 #2 0x7f9577fe5899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f95716160a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f9571e1502d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f953f501700 (LWP 2192)): #0 0x
[kmymoney4] [Bug 365615] SQL syntax error reported opening MySQL database
https://bugs.kde.org/show_bug.cgi?id=365615 Christian David changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #3 from Christian David --- This bug is caused by mymoneydbdef.cpp, line 221. There I used “order” as column name. This is okay if the identifier is quoted. Unfortunately the way of quoting it is different between the databases (e.g. https://www.postgresql.org/docs/7.3/static/sql-syntax.html#SQL-SYNTAX-IDENTIFIERS vs https://dev.mysql.com/doc/refman/5.7/en/identifiers.html). I did not know that :( It should be safe to rename the identifier as we do not really use it, yet. Alternatively we could adopt our query creator to this. However, I think this is too much work for a minor benefit. There is another case of this issue in line 162. If someone is working an this bug, please assign it to yourself. -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 366296] New: Baloo file crash
https://bugs.kde.org/show_bug.cgi?id=366296 Bug ID: 366296 Summary: Baloo file crash Product: Baloo Version: unspecified Platform: Debian unstable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: pinak.ah...@gmail.com Reporter: tim.rueh...@gmx.de Application: baloo_file (5.23.0) Qt Version: 5.6.1 Frameworks Version: 5.23.0 Operating System: Linux 4.6.0-1-amd64 x86_64 Distribution: Debian GNU/Linux unstable (sid) -- Information about the crash: - What I was doing when the application crashed: Just start KDE. I always get this crash. Since a few months. No matter if the DB is inconsistent or whatever... there should be no crash, just an informative message that tells me what is wrong and how I can (manually) solve it. Regards, Tim The crash can be reproduced every time. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6fcec908c0 (LWP 3293))] Thread 3 (Thread 0x7f6fc28bf700 (LWP 3954)): [KCrash Handler] #6 0x7f6fcde4a2be in () at /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #7 0x7f6fcde77a3e in () at /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #8 0x7f6fcde76e9f in () at /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #9 0x7f6fcde5fb14 in Baloo::PositionDB::get(QByteArray const&) () at /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #10 0x7f6fcde7495c in Baloo::WriteTransaction::commit() () at /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #11 0x7f6fcde6b342 in Baloo::Transaction::commit() () at /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #12 0x0040fa65 in () #13 0x7f6fcd780c03 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f6fcd784808 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f6fcc416464 in start_thread (arg=0x7f6fc28bf700) at pthread_create.c:333 #16 0x7f6fccd9730d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f6fc3423700 (LWP 3301)): #0 0x7f6fccd8e19d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f6fc9f2b39c in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f6fbc003220, timeout=, context=0x7f6fbc000990) at /build/glib2.0-vjfO_h/glib2.0-2.48.1/./glib/gmain.c:4135 #2 0x7f6fc9f2b39c in g_main_context_iterate (context=context@entry=0x7f6fbc000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-vjfO_h/glib2.0-2.48.1/./glib/gmain.c:3835 #3 0x7f6fc9f2b4ac in g_main_context_iteration (context=0x7f6fbc000990, may_block=1) at /build/glib2.0-vjfO_h/glib2.0-2.48.1/./glib/gmain.c:3901 #4 0x7f6fcd9ae1cb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6fcd956e4a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6fcd77f9e4 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f6fcedad515 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7f6fcd784808 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f6fcc416464 in start_thread (arg=0x7f6fc3423700) at pthread_create.c:333 #10 0x7f6fccd9730d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f6fcec908c0 (LWP 3293)): #0 0x7f6fccd8a17d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f6fc9f6e740 in g_wakeup_acknowledge (__nbytes=16, __buf=0x7fff8ae9fbf0, __fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44 #2 0x7f6fc9f6e740 in g_wakeup_acknowledge (wakeup=0x1607330) at /build/glib2.0-vjfO_h/glib2.0-2.48.1/./glib/gwakeup.c:210 #3 0x7f6fc9f2ae84 in g_main_context_check (context=context@entry=0x161dfb0, max_priority=2147483647, fds=fds@entry=0x1643050, n_fds=n_fds@entry=3) at /build/glib2.0-vjfO_h/glib2.0-2.48.1/./glib/gmain.c:3632 #4 0x7f6fc9f2b340 in g_main_context_iterate (context=context@entry=0x161dfb0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-vjfO_h/glib2.0-2.48.1/./glib/gmain.c:3837 #5 0x7f6fc9f2b4ac in g_main_context_iteration (context=0x161dfb0, may_block=1) at /build/glib2.0-vjfO_h/glib2.0-2.48.1/./glib/gmain.c:3901 #6 0x7f6fcd9ae1af in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f6fcd956e4a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f6fcd95f50c in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x0040aa5c in () #10 0x7f6fcccd0730 in __libc_start_main (main=0x40a6e0, argc=1, argv=0x7fff8aea0178, init=, fini=, rtld_fini=, stack_end=0x7fff8aea0168) at ../csu/libc-start.c:291 #11 0x0040ac19 in _star
[plasmashell] [Bug 354015] Moving panels between different screens is not possible without many tries and crashes
https://bugs.kde.org/show_bug.cgi?id=354015 Björn Ruberg changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #8 from Björn Ruberg --- Closing this bug. If you still have an issue with plasma 5.7, please open a specific bug. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 354550] Tracks shorten themselves upon re-opening the project
https://bugs.kde.org/show_bug.cgi?id=354550 Chris changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Chris --- I did try this with the most recent stable version of kdenlive and it seems to me that the bug is now fixed. Could not reproduce this effect anymore. Thanks :) -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 360122] Password for a jabber account is never remembered
https://bugs.kde.org/show_bug.cgi?id=360122 --- Comment #2 from Björn Ruberg --- I solved this now be carefully deleting the account and recreating it. Saved it between and made sure, that the old account was really not existing before creating a new one. Although fixable, this stays a problem. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 362696] Poor rendering performance
https://bugs.kde.org/show_bug.cgi?id=362696 razrfal...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from razrfal...@gmail.com --- Was fixed in 15.12.3. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 244163] Dolphin doesn't refresh the folder list until I press F5
https://bugs.kde.org/show_bug.cgi?id=244163 Teoti Kalki Nathaniel changed: What|Removed |Added CC||teotihuacan...@gmail.com --- Comment #40 from Teoti Kalki Nathaniel --- Hey all. I'm a Gnome user who can't stand the Gnome file manager and have been using Dolphin full-time for years, even though I had to install hundreds of megs of KDE dependencies for it (which is annoying; I'd really like to see the true Linux philosophy embraced and have 'File Manager' be a modular component of ANY window manager... I truly love custom integrations, I just don't think that they should be straightjackets). ANYWAYS. I found this thread because I have the same issue with Dolphin. It usually comes up with qBittorrent putting files into its 'completed' directory and those files not being visible in Dolphin. For reference, I'm using the latest Debian Jessie with both Gnome and KDE installed; Dolphin was installed via apt and is whatever version the Debian repositories give me (not sure how to check its version number); I operate mostly in Gnome when I'm not in terminals; Dolphin has been my exclusive file manager since approximately day 2 of Gnome use (iirc it was the 'tooltip' that appeared at the bottom with the file name and size when you selected a file that drove me away... it covered the name of the last file in any directory (with more than a few files) and effectively rendered it 'inaccessible'. This feature could NOT be disabled. Aside from that it just looks/feels like it's the 'adolescent' file manager to Dolphin's 'undergraduate'... simplistic and almost childish?. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 365804] Print Dialog doesn't respect Printer Hierarchy / Order
https://bugs.kde.org/show_bug.cgi?id=365804 --- Comment #2 from Christoph Feck --- If you can provide the information requested in comment #1, please add it. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 366194] DIscover crashed on open
https://bugs.kde.org/show_bug.cgi?id=366194 Christoph Feck changed: What|Removed |Added Version|unspecified |5.7.1 Product|kde |Discover Component|general |discover Assignee|unassigned-b...@kde.org |aleix...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 366256] Plasma / Nvidia
https://bugs.kde.org/show_bug.cgi?id=366256 Christoph Feck changed: What|Removed |Added Version|unspecified |4.11.11 Product|kde |plasma4 Component|general |general Assignee|unassigned-b...@kde.org |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 366264] Was doing upgrade in Plasma DIscover
https://bugs.kde.org/show_bug.cgi?id=366264 Christoph Feck changed: What|Removed |Added Version|unspecified |5.7.2 Component|general |discover Assignee|unassigned-b...@kde.org |aleix...@kde.org Product|kde |Discover -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366234] Import from card readers starts automatically when digikam is started
https://bugs.kde.org/show_bug.cgi?id=366234 Wolfram Kroiss changed: What|Removed |Added Severity|normal |minor --- Comment #12 from Wolfram Kroiss --- After restarting the computer this phenomenon doesn't appear. Severity decreased to "minor". I would like to do some additional tests (e.g. what happens if a memory card was inserted, then ejected, then digikam). But I'll run them end of August when I'm not so busy. I hope we can keep this defect open until then. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 364939] KDENLIVE fechou inesperadamente - Executável: kdenlive PID: 16726 Sinal: Segmentation fault (11)
https://bugs.kde.org/show_bug.cgi?id=364939 Christoph Feck changed: What|Removed |Added Product|kde |kdenlive Component|general |User Interface Assignee|unassigned-b...@kde.org |j...@kdenlive.org Resolution|FIXED |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 366297] New: Z-index is not indepenent of layers.
https://bugs.kde.org/show_bug.cgi?id=366297 Bug ID: 366297 Summary: Z-index is not indepenent of layers. Product: karbon Version: 2.9.8 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: opendocument Assignee: ja...@gmx.net Reporter: j...@vandenoever.info Created attachment 100394 --> https://bugs.kde.org/attachment.cgi?id=100394&action=edit drawing with boxes with different z-index. The boxes should be stacked. In ODF, they layer to which a drawing object belongs should not affect the z-index. Nevertheless, the UI can modify the z-index for all object at once. Karbon does not respect the z-index of objects if they are in different layers when an ODG file with objects with different z-index per layer is loaded. -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 366297] Z-index is not indepenent of layers.
https://bugs.kde.org/show_bug.cgi?id=366297 --- Comment #1 from Jos van den Oever --- Created attachment 100395 --> https://bugs.kde.org/attachment.cgi?id=100395&action=edit Screenshot of how the boxes should look. Each box shows the name of the layer to which it belongs. -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 366297] Z-index is not indepenent of layers.
https://bugs.kde.org/show_bug.cgi?id=366297 --- Comment #2 from Jos van den Oever --- Created attachment 100396 --> https://bugs.kde.org/attachment.cgi?id=100396&action=edit screenshot of karbon with wrong ordering of boxes -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356066] crash on exit
https://bugs.kde.org/show_bug.cgi?id=356066 rouven changed: What|Removed |Added Resolution|WONTFIX |REMIND Status|RESOLVED|VERIFIED --- Comment #5 from rouven --- as you say? one last question about the project: the crashreport software stated that the information of the backtrace was/is useless. is it really useless? to me it seems that it exactly points to the line were the error occured. a second question about you: you set it to resolved: it is not resolved. as long as the bug is present nothing is resolved. who are you? thank you for your attention. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 366260] kate opens real file as blank
https://bugs.kde.org/show_bug.cgi?id=366260 --- Comment #4 from Kåre Särs --- Could it be that PACManFM does not provide the path properly? I installed PCmanFM in kubuntu 16.04 and it worked as expected... strange Are you able to determine the command used to by PCmanFM to launch kate? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366294] Folderview Widget in Panel: "Create New" creates files/folders in top path, not in current location
https://bugs.kde.org/show_bug.cgi?id=366294 Eike Hein changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/plas ||ma-framework/8665999ee70935 ||e18a1e5b2a4032697842334959 Resolution|--- |FIXED --- Comment #3 from Eike Hein --- Git commit 8665999ee70935e18a1e5b2a4032697842334959 by Eike Hein. Committed on 31/07/2016 at 12:12. Pushed by hein into branch 'master'. Emit contextualActionsAboutToShow before showing the applet's contextualActions menu. This is done by ContainmentInterface::mousePressEvent, but not in this code path, which is hit for applet panel popups. Folder View relies on this to update actions ahead of the menu being opened. M +1-0src/scriptengines/qml/plasmoid/appletinterface.cpp http://commits.kde.org/plasma-framework/8665999ee70935e18a1e5b2a4032697842334959 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 357151] Crashes when trying to render
https://bugs.kde.org/show_bug.cgi?id=357151 --- Comment #4 from HERVE MOENS --- Thank you so much. I'm using Version 16.04.3 now and I haven't any bug anymore. The bug report can be closed. Beste Regards, Hervé On 07/31/2016 11:10 AM, Wegwerf via KDE Bugzilla wrote: > https://bugs.kde.org/show_bug.cgi?id=357151 > > Wegwerf changed: > >What|Removed |Added > > CC||wegwerf-1-...@gmx.de > > --- Comment #3 from Wegwerf --- > Herve, can you please test using the recent stable Kdenlive 16.04.2 version, > with MLT 6.2.0+ at least? Does the bug still persists? If not, I would like to > ask you to be so kind as to close this bug report. Thank you very much for > your > cooperation! > -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366298] New: widgets remain locked after selecting the "unlock widgets" option from the desktop context menu
https://bugs.kde.org/show_bug.cgi?id=366298 Bug ID: 366298 Summary: widgets remain locked after selecting the "unlock widgets" option from the desktop context menu Product: plasmashell Version: 5.7.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: alexandre.skobin...@gmail.com I can't unlock the widgets: when I right-click the desktop or a panel and click "unlock widgets", the panels disappear, then come back, widgets still locked and marked as locked. reboot doesn't fix it. Reproducible: Always Steps to Reproduce: 1. right click on the desktop or panel(s) 2. select lock widgets 3. right click on the desktop or panel(s) again 4. select unlock widgets Actual Results: the widgets aren't unlocked and the three horizontal bars (hamburger menu?) on the panel don't show up Expected Results: The widgets and panels should have been unlocked and editable I only have one active panel with these widgets: * application launcher * icons-only task manager * lock/leave buttons * system tray * digital clock -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 336607] cursor is blinking (flashing) at insane rate
https://bugs.kde.org/show_bug.cgi?id=336607 --- Comment #8 from Arek Guzinski --- Bump! 2 Years later and still not fixed :( While there is still no way to easily turn off blinking in qt5 on linux (shame on that!), it can be done with qt5noblink (https://github.com/igogo/qt5noblink). While this works for other applications, okteta (0.17.0 here) still blinks insanely. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 357618] scrolling with xf86-input-libinput is unusable slow - only in dolphin
https://bugs.kde.org/show_bug.cgi?id=357618 --- Comment #19 from Larry --- (In reply to Lukasz from comment #9) > Use xf86-input-evdev until fixed. Finally removed xorg-x11-drv-libinput (dnf remove xorg-x11-drv-libinput) and all mouse-wheel scrolling issues are resolved. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kbookmarks] [Bug 358079] Bookmarks widget disappeared with the change to Plasma.
https://bugs.kde.org/show_bug.cgi?id=358079 Larry changed: What|Removed |Added Version|5.5.3 |5.24.0 Product|kdeplasma-addons|frameworks-kbookmarks Component|General |general -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kbookmarks] [Bug 358079] Bookmarks widget disappeared with the change to Plasma.
https://bugs.kde.org/show_bug.cgi?id=358079 --- Comment #5 from Larry --- I changed the product since no developers commented on the issue if it wasn't initially properly assigned. Hopefully, someone will either acknowledge it or assign it to the correct group. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 366299] New: System setting "Energy Saving" window is too large for a standard laptop screen
https://bugs.kde.org/show_bug.cgi?id=366299 Bug ID: 366299 Summary: System setting "Energy Saving" window is too large for a standard laptop screen Product: Powerdevil Version: 5.7.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-de...@kde.org Reporter: o...@geek.co.il I'm using a rather standard laptop with a 1600x900 resolution (what was used to be called HD+ and is higher than the resolution available on most laptops sold up until about a year ago), and on that screen the "Energy Saving" configuration window is so large that the OK/Cancel buttons are not visible (they mostly out of the screen and the rest is hidden behind the bottom panel). See screenshot This wasn't an issue before 5.7 (or 5.6 - i haven't used 5.6 much). From looking at the current setup, it looks like there's a lot of unnecessary empty space around elements, and it looks to me as if reducing some of that can get all the content to fit in 800px and a bit (to leave some room for a bottom panel) without moving anything to other tabs/sub dialogs. Reproducible: Always Steps to Reproduce: 1. Right click the battery icon in the notification tray and select "Configure Power Saving..." 2. Change something 3. Try to click "OK" Actual Results: The "OK" button is not visible and cannot be clicked. Also the window cannot be moved up by grabbing the window title bar or even by grabbing empty space (if this is configured under "Application Style" -> "Widget Style and Behavior" -> "Breeze" -> "Configure" -> "General" -> "Windows' drag mode:" -> "Drag from all empty areas"). Expected Results: The "OK" button should be visible and clickable. There is a workaround by grabbing the window with the "Windows action modifier key" (usually ALT), which does allow you to move the window so that the title bar is higher than the top of the screen (which the Breeze "drag mode" doesn't let you do) - but that "hack" is something you can't expect KDE newbies to be aware of. I'd set the severity to "minor", but because the workaround is so undiscoverable, I think "normal" is in order. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 366299] System setting "Energy Saving" window is too large for a standard laptop screen
https://bugs.kde.org/show_bug.cgi?id=366299 --- Comment #1 from Oded Arbel --- Created attachment 100398 --> https://bugs.kde.org/attachment.cgi?id=100398&action=edit attachment showing the problem -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 365596] Deleting Albums and renaming not possible
https://bugs.kde.org/show_bug.cgi?id=365596 Maik Qualmann changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||5.1.0 Resolution|--- |FIXED Latest Commit||http://commits.kde.org/digi ||kam/6ceab7bc027b8f0fa6b7da8 ||6e2f48f77728a52b2 --- Comment #4 from Maik Qualmann --- Git commit 6ceab7bc027b8f0fa6b7da86e2f48f77728a52b2 by Maik Qualmann. Committed on 31/07/2016 at 12:51. Pushed by mqualmann into branch 'master'. workaround for locked albums under Windows FIXED-IN: 5.1.0 M +2-1NEWS M +11 -0libs/album/albummanager.cpp M +2-0libs/album/albummanager.h M +19 -0libs/album/albumwatch.cpp M +2-0libs/album/albumwatch.h M +8-0libs/database/utils/dio.cpp http://commits.kde.org/digikam/6ceab7bc027b8f0fa6b7da86e2f48f77728a52b2 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 334080] kdeconnect,some sent photo are uncomplete
https://bugs.kde.org/show_bug.cgi?id=334080 ghost53...@gmail.com changed: What|Removed |Added CC||ghost53...@gmail.com --- Comment #36 from ghost53...@gmail.com --- I have a HTC ONE M9 android 6. Kdeconnect 0.9.g-3 arch linux packe. I sent a photo of 192KB , on the phone it appeared at 28 KB. Same happens with videos, and not just on one desktop on my other one as well. Seems after going to plasma 5.6+ that I have been getting this error -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 366260] kate opens real file as blank
https://bugs.kde.org/show_bug.cgi?id=366260 --- Comment #5 from Roman --- "Could it be that PACManFM does not provide the path properly?" But for leafpad it provides the path properly! How can I determine the command used to launch kate? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 366260] kate opens real file as blank
https://bugs.kde.org/show_bug.cgi?id=366260 --- Comment #6 from Roman --- $ ps -ax | grep kate 2152 ?Sl 0:01 kate -b file:///home/destructor/Dropbox/English.txt -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 366300] New: Reduce Pop Ups after Completing Operations
https://bugs.kde.org/show_bug.cgi?id=366300 Bug ID: 366300 Summary: Reduce Pop Ups after Completing Operations Product: dolphin Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: stefan...@posteo.de A nasty thing of KDE is the noise that's produces. I want a desktop to be quiet as possible. Examples: - Don't inform me by a Pop Up, that KDE has connected with a wireless network after I rebooted my laptop, because this is something I am expecting anyway. - Don't inform me by a Pop Up, that a file has been copied. Show the progress within Dolphin and disappear when the progress is completed. See Gnome 3.20+ as an example. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 366301] New: Moved a folder from one tab to another and Dolphin crashed
https://bugs.kde.org/show_bug.cgi?id=366301 Bug ID: 366301 Summary: Moved a folder from one tab to another and Dolphin crashed Product: dolphin Version: unspecified Platform: Debian testing OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: johnbugs...@gmail.com Application: dolphin (16.04.2) Qt Version: 5.6.1 Frameworks Version: 5.23.0 Operating System: Linux 4.6.0-1-amd64 x86_64 Distribution: Debian GNU/Linux testing (stretch) -- Information about the crash: - What I was doing when the application crashed: I dragged a folder from one tab and when I reached the other tab, I pressed shift and left the mouse (I did not pause on the tab long enough for it to change focus to that tab). And dolphin crashed. I moved that folder back and tried the exact same thing again, and dolphin did not crash. I do this kind of moving often, and about 2 times dolphin has crashed in the past 2 months. I don't remember the specifics of those crashes. But this has never happened when i used to use the dolphin inside debian jessie. The crash does not seem to be reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc777e6e940 (LWP 5254))] Thread 6 (Thread 0x7fc74b1e7700 (LWP 7119)): #0 0x7fc77788c19d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fc76e62c091 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7fc76e61d641 in pa_mainloop_poll () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7fc76e61dcde in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7fc76e61dd90 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7fc76e62bfd9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7fc76a930418 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-9.0.so #7 0x7fc76ea66464 in start_thread (arg=0x7fc74b1e7700) at pthread_create.c:333 #8 0x7fc77789530d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7fc751130700 (LWP 5258)): #0 0x7fc77788c19d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fc76ded939c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc76ded94ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc77257c1cb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc772524e4a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc77234d9e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc772352808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fc76ea66464 in start_thread (arg=0x7fc751130700) at pthread_create.c:333 #8 0x7fc77789530d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fc759614700 (LWP 5257)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fc75a769693 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #2 0x7fc75a768db7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #3 0x7fc76ea66464 in start_thread (arg=0x7fc759614700) at pthread_create.c:333 #4 0x7fc77789530d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fc75bfff700 (LWP 5256)): #0 0x7fc77788c19d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fc76ded939c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc76ded94ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc77257c1cb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc772524e4a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc77234d9e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc777f62515 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fc772352808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fc76ea66464 in start_thread (arg=0x7fc75bfff700) at pthread_create.c:333 #9 0x7fc77789530d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fc761c58700 (LWP 5255)): #0 0x7fc77788c19d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fc76be2b382 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fc76be2cff7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fc763153a89 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fc772352808 in ?? ()
[kaffeine] [Bug 366302] New: DVB-S tuning fails since 2.0 upgrade
https://bugs.kde.org/show_bug.cgi?id=366302 Bug ID: 366302 Summary: DVB-S tuning fails since 2.0 upgrade Product: kaffeine Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: mchehab+...@kernel.org Reporter: martin+...@linuxlounge.net Since the 2.0 upgrade I lost all channels and am unable to rescan for new ones. Kaffeine version is 2.0.4 (built from git) on ArchLinux with the following DVB-S device: 05:03.0 Multimedia controller: Twinhan Technology Co. Ltd Mantis DTV PCI Bridge Controller [Ver 1.0] (rev 01) [4.726834] DVB: registering new adapter (Mantis DVB adapter) [5.623837] Mantis :05:03.0: DVB: registering adapter 0 frontend 0 (STB0899 Multistandard)... Setup is a DiSEqC-Switch with LNB1: Astra 19.2E. 31-07-16 15:44:03.596 [Debug ] src/dvb/dvbscan.cpp#300: DvbScan::DvbScan(DvbDevice*, const QString&, const QList&, bool): Use other NIT is disabled 31-07-16 15:44:03.596 [Debug ] src/dvb/dvbscan.cpp#634: void DvbScan::updateState(): Transponder 0/1 31-07-16 15:44:03.597 [Debug ] src/dvb/dvbdevice_linux.cpp#918: virtual bool DvbLinuxDevice::satSetup(QString, int, int): Using LNBf type UNIVERSAL 31-07-16 15:44:03.597 [Debug ] src/dvb/dvbdevice_linux.cpp#932: virtual bool DvbLinuxDevice::tune(const DvbTransponder&): tune to: S 12551500 V 2200 5/6 31-07-16 15:44:05.345 [Debug ] src/dvb/dvbdevice.cpp#692: void DvbDevice::frontendEvent(): tuning failed on 12551.50 MHz 31-07-16 15:44:05.346 [Debug ] src/dvb/dvbscan.cpp#634: void DvbScan::updateState(): Transponder 1/1 Reproducible: Always Steps to Reproduce: 1. start channel scan Actual Results: Signal and SNR show '0%' then immediately go back to '-' Expected Results: Tuning should work and channels should start to appear. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 366216] Dropping into folder popup on KUrlNavigator changes folder
https://bugs.kde.org/show_bug.cgi?id=366216 --- Comment #1 from A. Bikadorov --- update. I think I tracked it down: in filewidgets/kurlnavigatormenu.cpp there is a signal emitted for every dropEvent AND mouseReleaseEvent: two signals for one mouse release. Question is why the mouseButtonClicked signal is emitted for mouse releases and not mouse clicks. And my new explanation why this does not happen in Dolphin: the dropEvent signal opens a popup menu by calling KIO::drop(). This menu catches the mouse release event. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366303] New: color picker sample radius setting has no effect
https://bugs.kde.org/show_bug.cgi?id=366303 Bug ID: 366303 Summary: color picker sample radius setting has no effect Product: krita Version: 3.0 Platform: Other OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: jdre...@web.de I tried to increase the sample radius of the color picker to get a mixed color when I cmd-click (mac) on a sharp border between two colors. It seems the sample radius setting does not increase no matter if set to 20px, 200px, 900px, not for the color picker tool nor the cmd - shortcut. The transition between the original colors stays very narrow. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 357151] Crashes when trying to render
https://bugs.kde.org/show_bug.cgi?id=357151 Wegwerf changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360219] Right Click opens files
https://bugs.kde.org/show_bug.cgi?id=360219 --- Comment #28 from Eike Hein --- Here's an updated patch for Qt 5.7 if you want to test: https://codereview.qt-project.org/#/c/166455/ -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 366304] New: kontact crashes
https://bugs.kde.org/show_bug.cgi?id=366304 Bug ID: 366304 Summary: kontact crashes Product: kontact Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: fr.teichm...@aon.at Application: kontact (5.1.3) Qt Version: 5.5.1 Operating System: Linux 4.4.0-31-generic i686 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: just after starting korganizer as well as by starting addressbook (att: after upgrading from Kubuntu 14.04 to 16.04 The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xab728840 (LWP 3956))] Thread 32 (Thread 0x923f7b40 (LWP 4056)): #0 0xb26a048d in g_mutex_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb265a0ed in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb265a244 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb6499b14 in QEventDispatcherGlib::processEvents (this=0xaa90aa28, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0xb643e953 in QEventLoop::processEvents (this=0x923f7194, flags=...) at kernel/qeventloop.cpp:128 #5 0xb643edaa in QEventLoop::exec (this=0x923f7194, flags=...) at kernel/qeventloop.cpp:204 #6 0xb6264f1d in QThread::exec (this=0xa677ed8) at thread/qthread.cpp:503 #7 0xb6264ff8 in QThread::run (this=0xa677ed8) at thread/qthread.cpp:570 #8 0xb626a43b in QThreadPrivate::start (arg=0xa677ed8) at thread/qthread_unix.cpp:331 #9 0xb27f62b5 in start_thread (arg=0x923f7b40) at pthread_create.c:333 #10 0xb5f7a16e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 31 (Thread 0x92bf8b40 (LWP 4054)): #0 0xb26a048d in g_mutex_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb2659adc in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb265a0a1 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb265a244 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb6499b14 in QEventDispatcherGlib::processEvents (this=0xa820c198, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0xb643e953 in QEventLoop::processEvents (this=0x92bf8194, flags=...) at kernel/qeventloop.cpp:128 #6 0xb643edaa in QEventLoop::exec (this=0x92bf8194, flags=...) at kernel/qeventloop.cpp:204 #7 0xb6264f1d in QThread::exec (this=0xa654580) at thread/qthread.cpp:503 #8 0xb6264ff8 in QThread::run (this=0xa654580) at thread/qthread.cpp:570 #9 0xb626a43b in QThreadPrivate::start (arg=0xa654580) at thread/qthread_unix.cpp:331 #10 0xb27f62b5 in start_thread (arg=0x92bf8b40) at pthread_create.c:333 #11 0xb5f7a16e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 30 (Thread 0x933f9b40 (LWP 4042)): #0 0xb26a048d in g_mutex_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb2659c68 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb265a179 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb265a244 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb6499b14 in QEventDispatcherGlib::processEvents (this=0xa7705e40, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0xb643e953 in QEventLoop::processEvents (this=0x933f9194, flags=...) at kernel/qeventloop.cpp:128 #6 0xb643edaa in QEventLoop::exec (this=0x933f9194, flags=...) at kernel/qeventloop.cpp:204 #7 0xb6264f1d in QThread::exec (this=0xa2fb120) at thread/qthread.cpp:503 #8 0xb6264ff8 in QThread::run (this=0xa2fb120) at thread/qthread.cpp:570 #9 0xb626a43b in QThreadPrivate::start (arg=0xa2fb120) at thread/qthread_unix.cpp:331 #10 0xb27f62b5 in start_thread (arg=0x933f9b40) at pthread_create.c:333 #11 0xb5f7a16e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 29 (Thread 0x93bfab40 (LWP 4040)): #0 0xb6308332 in qt_clock_gettime (ts=0x93bf9ee4, clock=) at tools/qelapsedtimer_unix.cpp:105 #1 do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:156 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:165 #3 0xb64973e2 in QTimerInfoList::updateCurrentTime (this=0xa65069c4) at kernel/qtimerinfo_unix.cpp:84 #4 0xb6497904 in QTimerInfoList::timerWait (this=0xa65069c4, tm=...) at kernel/qtimerinfo_unix.cpp:381 #5 0xb6498ec9 in timerSourcePrepareHelper (timeout=0x93bf9ff8, src=0xa6506990) at kernel/qeventdispatcher_glib.cpp:127 #6 timerSourcePrepare (source=0xa6506990, timeout=0x93bf9ff8) at kernel/qeventdispatcher_glib.cpp:160 #7 0xb26595cb in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0xb265a014 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0xb265a244 in g_main_context_iteration () from /lib
[digikam] [Bug 366305] New: Undo is disfunctional for complex operations
https://bugs.kde.org/show_bug.cgi?id=366305 Bug ID: 366305 Summary: Undo is disfunctional for complex operations Product: digikam Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: showfoto Assignee: digikam-de...@kde.org Reporter: kpho...@o2online.de for most operations the 'undo' function does not work. Reproducible: Always Steps to Reproduce: 1. Open image 2. Change color to BW or resize or ... 3. accept changes 4. Edit/undo last operation Actual Results: Modifications on the image persist. Expected Results: Modifications on the image should be undone This is on version 3.5.0 under ubuntu 14.04 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 359610] Kontact crashed after trying to add new category to calendar event, now calendar and addressbook crashes on start
https://bugs.kde.org/show_bug.cgi?id=359610 r...@alum.mit.edu changed: What|Removed |Added CC||r...@alum.mit.edu --- Comment #1 from r...@alum.mit.edu --- Reproduces for me too, using latest openSUSE RPMs. I've narrowed it down to use of QtCurve widget theme. I created a new user with default configuration; kontact works fine. If I change the widget theme to QtCurve it dies. Change it to fusion, no problem. This happens also when simply creating a new calendar entry. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366298] widgets remain locked after selecting the "unlock widgets" option from the desktop context menu
https://bugs.kde.org/show_bug.cgi?id=366298 alexandre.skobin...@gmail.com changed: What|Removed |Added CC||alexandre.skobinsky@gmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361585] Two-finger gesture to zoom on trackpad causes zoom-mode to be always on
https://bugs.kde.org/show_bug.cgi?id=361585 jdre...@web.de changed: What|Removed |Added CC||jdre...@web.de --- Comment #6 from jdre...@web.de --- I still have the same problem as mentioned above. When I try to zoom or pan with the trackpad (OSX 10.11.6) krita gets so unresponsive I have to close and reopen. Same with 3.0.1 alpha. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 359610] Kontact crashed after trying to add new category to calendar event, now calendar and addressbook crashes on start
https://bugs.kde.org/show_bug.cgi?id=359610 --- Comment #2 from r...@alum.mit.edu --- A bit more information: this worked up through about KDE Frameworks 5.5.5. It broke in 5.6. I'm using qtcurve 1.8.19~git20150303 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366305] Undo is disfunctional for complex operations
https://bugs.kde.org/show_bug.cgi?id=366305 Frank Steinmetzger changed: What|Removed |Added CC||war...@gmx.de --- Comment #1 from Frank Steinmetzger --- Same here, Digikam 5.0.0 on Plasma 5.7.2, Qt 5.6.1, Frameworks 5.24.0 on Gentoo Linux. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint
https://bugs.kde.org/show_bug.cgi?id=353960 Atle changed: What|Removed |Added CC||atle.peder...@gmail.com --- Comment #9 from Atle --- I had the same problem. gpg --full-gen-key doesn't work for me, but gpg2 --full-gen-key does. It seems my system (kubuntu 16.04) has both v1 and v2 of gpg, and gpg defaults to v1. After doing this I had to quit and restart the process requesting to use the wallet. Seems the "KDE Wallet System" creating a new wallet will not reload available keys after first loading them. So: 1. Cancel the dialog for creating a new wallet 2. Run gpg2 --full-gen-key and follow the instructions 3. Redo whatever triggered the request for a new wallet (for example connecting to wireless) (Optionally create the wallet using kwalletmanager5, for example 'kdewallet') -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366306] New: Click App Close activates Icon under the Close Button
https://bugs.kde.org/show_bug.cgi?id=366306 Bug ID: 366306 Summary: Click App Close activates Icon under the Close Button Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: s093x...@rogers.com CC: bhus...@gmail.com, plasma-b...@kde.org I am using KDE neon 5.7.2 which is up-to-date. The desktop theme is the default, Breeze. The icons are kumic-circle. A reminder app shows frequently on my desktop. The Close button is directly over an icon on the desktop. When I click the Close button, the underlying icon is usually activated and the associated app starts. Reproducible: Sometimes Steps to Reproduce: 1. Close an app with Close button over a desktop icon and do the click slowly 2. 3. Actual Results: Clicking the Close button activates the desktop icon which is under it Expected Results: The opened app should close with no other desktop activity OK, I think I know what is going on but I don't understand why it happens. If I click to Close an open app and the click is not quick enough then the click is 'carried' over to the desktop icon. I tried keeping the rodent button down after a click but the underlying icon is highlighted but not activated. If I click quickly then the desktop icon is unaffected. If I click longer then the desktop icon is activated. I tried this on a few open apps and different desktop icons and it shows the same results. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 366307] New: activity manager daemon crash
https://bugs.kde.org/show_bug.cgi?id=366307 Bug ID: 366307 Summary: activity manager daemon crash Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: g...@crowhealingnetwork.net Application: kactivitymanagerd (3.0) KDE Platform Version: 4.14.13 Qt Version: 4.8.6 Operating System: Linux 3.13.0-92-generic x86_64 Distribution: Ubuntu 14.04.4 LTS -- Information about the crash: - Unusual behavior I noticed: it crashes from time to time I have not noticed at what circumstance it crashes The crash can be reproduced sometimes. -- Backtrace: Application: KDE Activity Manager (kactivitymanagerd), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7efeda2e57c0 (LWP 3205))] Thread 6 (Thread 0x7efec93f1700 (LWP 3214)): #0 0x7efed6f827de in __pthread_mutex_unlock_usercnt (decr=1, mutex=0x7efec4000a60) at pthread_mutex_unlock.c:57 #1 __GI___pthread_mutex_unlock (mutex=0x7efec4000a60) at pthread_mutex_unlock.c:310 #2 0x7efed4c759b1 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7efed4c33680 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7efed4c33f03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7efed4c340ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7efed904e7be in QEventDispatcherGlib::processEvents (this=0x7efec40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #7 0x7efed90200af in QEventLoop::processEvents (this=this@entry=0x7efec93f0e10, flags=...) at kernel/qeventloop.cpp:149 #8 0x7efed90203a5 in QEventLoop::exec (this=this@entry=0x7efec93f0e10, flags=...) at kernel/qeventloop.cpp:204 #9 0x7efed8f1cc5f in QThread::exec (this=) at thread/qthread.cpp:537 #10 0x0040a06a in ?? () #11 0x7efed8f1f32f in QThreadPrivate::start (arg=0x9eb9b0) at thread/qthread_unix.cpp:349 #12 0x7efed6f7f184 in start_thread (arg=0x7efec93f1700) at pthread_create.c:312 #13 0x7efed7c2237d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 5 (Thread 0x7efec8bf0700 (LWP 3230)): #0 0x7efed6f827de in __pthread_mutex_unlock_usercnt (decr=1, mutex=0x7efeb8000a60) at pthread_mutex_unlock.c:57 #1 __GI___pthread_mutex_unlock (mutex=0x7efeb8000a60) at pthread_mutex_unlock.c:310 #2 0x7efed4c759b1 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7efed4c33a59 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7efed4c33f7b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7efed4c340ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7efed904e7be in QEventDispatcherGlib::processEvents (this=0x7efeb80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #7 0x7efed90200af in QEventLoop::processEvents (this=this@entry=0x7efec8befe10, flags=...) at kernel/qeventloop.cpp:149 #8 0x7efed90203a5 in QEventLoop::exec (this=this@entry=0x7efec8befe10, flags=...) at kernel/qeventloop.cpp:204 #9 0x7efed8f1cc5f in QThread::exec (this=) at thread/qthread.cpp:537 #10 0x0040a09a in ?? () #11 0x7efed8f1f32f in QThreadPrivate::start (arg=0xa41810) at thread/qthread_unix.cpp:349 #12 0x7efed6f7f184 in start_thread (arg=0x7efec8bf0700) at pthread_create.c:312 #13 0x7efed7c2237d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 4 (Thread 0x7efec3fff700 (LWP 3231)): #0 0x7efed4c759b1 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7efed4c330f0 in g_main_context_acquire () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7efed4c33ea5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7efed4c340ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7efed904e7be in QEventDispatcherGlib::processEvents (this=0x7efebc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #5 0x7efed90200af in QEventLoop::processEvents (this=this@entry=0x7efec3ffee10, flags=...) at kernel/qeventloop.cpp:149 #6 0x7efed90203a5 in QEventLoop::exec (this=this@entry=0x7efec3ffee10, flags=...) at kernel/qeventloop.cpp:204 #7 0x7efed8f1cc5f in QThread::exec (this=) at thread/qthread.cpp:537 #8 0x0040a0ca in ?? () #9 0x7efed8f1f32f in QThreadPrivate::start (arg=0x9f3d60) at thread/qthread_unix.cpp:349 #10 0x7efed6f7f184 in start_thread (arg=0x7efec3fff700) at pthread_create.c:312 #11 0x7efed7c2237d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7efec2cdf700 (LWP 3232)): #0 0x7efed4c7561a in ?? () from /lib/x86_64-linux-gnu/li
[i18n] [Bug 366308] New: l10n-kf5/tr/messages/pim/kdgantt2_qt.po@1465307 contains invalid text "(http: //www.transifex.com/projects/p/kdepim-k-tr/language/tr/)\n"
https://bugs.kde.org/show_bug.cgi?id=366308 Bug ID: 366308 Summary: l10n-kf5/tr/messages/pim/kdgantt2_qt.po@1465307 contains invalid text "(http: //www.transifex.com/projects/p/kdepim-k-tr/language/tr /)\n" Product: i18n Version: unspecified Platform: Other URL: https://websvn.kde.org/trunk/l10n-kf5/tr/messages/pim/ kdgantt2_qt.po?revision=1465307&view=markup OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: tr Assignee: gor...@gelecek.com.tr Reporter: devuran...@gmx.net At revision 1465307 (e.g. included in release 16.07.80) l10n-kf5/tr/messages/pim/kdgantt2_qt.po has the following text on line 20, which is not in the "key: value" format: "(http: //www.transifex.com/projects/p/kdepim-k-tr/language/tr/)\n" This generates invalid XML in the kdgantt2_qt.ts file, which will break the build. Deleting the line solves the problem. See-Also: https://bugs.gentoo.org/show_bug.cgi?id=589804 Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362531] Plasma panels are not transparent after login
https://bugs.kde.org/show_bug.cgi?id=362531 Dušan Dragić changed: What|Removed |Added CC||dragic.du...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kemoticons] [Bug 366309] New: Time not shown if no Time Zone is selected
https://bugs.kde.org/show_bug.cgi?id=366309 Bug ID: 366309 Summary: Time not shown if no Time Zone is selected Product: frameworks-kemoticons Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: alejandr...@openmailbox.org - Running GNU Parabola OS. (similar to archlinux) Time not shown if no Time Zone is selected. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366309] Time not shown if no Time Zone is selected
https://bugs.kde.org/show_bug.cgi?id=366309 Alejandro changed: What|Removed |Added Target Milestone|--- |1.0 Version|unspecified |master Product|frameworks-kemoticons |plasmashell Component|general |Digital Clock -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 366260] kate opens real file as blank
https://bugs.kde.org/show_bug.cgi?id=366260 Kåre Särs changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Version Fixed In||16.08 Status|NEEDSINFO |RESOLVED --- Comment #7 from Kåre Särs --- Thanks! That helped :) The root of the problem is a bug that has been fixed at the Randa meeting earlier this summer. The fix will be in 16.08. (I'm using master, that is why I couldn't reproduce) If you can get PCmanFM to remove the "file://" prefix of the file name, kate should work properly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366294] Folderview Widget in Panel: "Create New" creates files/folders in top path, not in current location
https://bugs.kde.org/show_bug.cgi?id=366294 --- Comment #4 from stefanpro...@kolabnow.com --- Thank you very much for the very quick fix! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366294] Folderview Widget in Panel: "Create New" creates files/folders in top path, not in current location
https://bugs.kde.org/show_bug.cgi?id=366294 --- Comment #5 from Eike Hein --- Thanks for the report and sorry for the trouble :-) -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 366277] klipper systray applet autostarts on non-plasma DE's
https://bugs.kde.org/show_bug.cgi?id=366277 Rex Dieter changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Rex Dieter --- In my opinion, the aforementioned commit should be reverted, until this can be fixed properly (and klipper be able to support non-plasma DE's via configuration to enable/disable autostart). That's probably what I'm going to do in fedora downstream patching for now. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366305] Undo is disfunctional for complex operations
https://bugs.kde.org/show_bug.cgi?id=366305 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- Strangely, this is absolutely not here to reproduce. All processing steps can undo. Possibly a problem with the undo cache. Please share the output of the console. Maik -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 347217] KDEnlive 0.9.8 vs 0.9.10
https://bugs.kde.org/show_bug.cgi?id=347217 Sandro changed: What|Removed |Added Version Fixed In||15.12.3 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 347217] KDEnlive 0.9.8 vs 0.9.10
https://bugs.kde.org/show_bug.cgi?id=347217 Sandro changed: What|Removed |Added Resolution|UNMAINTAINED|FIXED -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 366310] New: krusader pass wrong file names to kdiff3
https://bugs.kde.org/show_bug.cgi?id=366310 Bug ID: 366310 Summary: krusader pass wrong file names to kdiff3 Product: krusader Version: Git Platform: Gentoo Packages URL: http://i.imgur.com/f4nzb94.png OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: m...@fork.pl Reporter: reagen...@gmail.com File names like /foo/bar are passed as /foo/file:/foo/bar. Tested on latest git build of krusader (Qt5). Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
