[digikam] [Bug 405347] selecting by aspect ratio: abs function in sqlite lowercase, in mariadb uppercase
https://bugs.kde.org/show_bug.cgi?id=405347 --- Comment #3 from Jürgen Blumenschein --- Thanks a lot, I patched and compiled the 6.0.0 and all worked fine. Jürgen Zitat von Maik Qualmann : > https://bugs.kde.org/show_bug.cgi?id=405347 > > Maik Qualmann changed: > > What |Removed |Added > > Status|REPORTED |RESOLVED > Version Fixed In| |6.1.0 > Latest Commit| |https://commits.kde.org/dig > | |ikam/b3a3598a28c0e744920bf8 > | |31296109af3338d3c8 > Resolution|--- |FIXED > > --- Comment #2 from Maik Qualmann --- > Git commit b3a3598a28c0e744920bf831296109af3338d3c8 by Maik Qualmann. > Committed on 11/03/2019 at 19:04. > Pushed by mqualmann into branch 'master'. > > fix unknown data type REAL for MySQL in the CAST function > testet with SQLite and MariaDB-10.2.22 > FIXED-IN: 6.1.0 > > M +2 -1 NEWS > M +6 -6 core/libs/database/item/query/itemquerybuilder.cpp > https://commits.kde.org/digikam/b3a3598a28c0e744920bf831296109af3338d3c8 Jürgen Blumenschein, eMail: blumensch...@dokom.net Homepage: http://members.dokom.net/blumenschein Am Quartus 17 D-44149 Dortmund Tel.: +49 231 7217321, Handy: +49 176 5591 4562 public key: http://members.dokom.net/blumenscheinJuergen_Blumenschein_(0xC9358EBB)_public_key.asc -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 404518] System Settings crashed when added another preferred language in Regional Settings
https://bugs.kde.org/show_bug.cgi?id=404518 hung0966609...@gmail.com changed: What|Removed |Added Platform|Ubuntu Packages |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 404518] System Settings crashed when added another preferred language in Regional Settings
https://bugs.kde.org/show_bug.cgi?id=404518 --- Comment #4 from hung0966609...@gmail.com --- I'm switching to Manjaro KDE 18.0.3 and still encounter this issue. But I found out what happened, it doesn't apply to any specific languages, it just that it automatically crashes when you add the third language, no matter what is that. I tried multiple language and got the same problem when adding the third one. You can only add 2 languages there. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 405381] New: Mouse pointer gets fixed to a move symbol just after drag and drop media from the clip monitor to timeline
https://bugs.kde.org/show_bug.cgi?id=405381 Bug ID: 405381 Summary: Mouse pointer gets fixed to a move symbol just after drag and drop media from the clip monitor to timeline Product: kdenlive Version: 18.12.1 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: minor Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: ksy20...@chollian.net Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Import a movie clip for source media into Kdenlive 2. Select the movie clip from within the project bin 3. Optional: Set in/out point of the clip using the clip monitor 4. Drag the clip monitor and drop the media on the timeline OBSERVED RESULT Mouse pointer gets changed to a move symbol. Further editing gets very hard with fixed mouse pointer because mouse pointer does not indicate that the position is correct for trim/fade/transition any more. The only way to overcome this situation so far is that to click status bar once, then mouse cursor gets unfixed. EXPECTED RESULT Mouse pointer should never affected by drag'n'drop action. SOFTWARE/OS VERSIONS Windows: Both Windows 7 Ultimate K and Windows 10 Professional MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 405311] latte-dock icons not showing up
https://bugs.kde.org/show_bug.cgi?id=405311 --- Comment #5 from Michail Vourlakos --- No, this isn't what I asked for... 1. Close Latte 2. Right click on the desktop->Panels->Add default panel 3. Open some windows 4. Take a screenshot with the panel that was added with [2] -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405333] Unexpected connections between fast, short, close brush strokes.
https://bugs.kde.org/show_bug.cgi?id=405333 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404793] The program keeps crashing in the middle of drawing, or when attempting to open a recent file
https://bugs.kde.org/show_bug.cgi?id=404793 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404653] Kwin Crash
https://bugs.kde.org/show_bug.cgi?id=404653 --- Comment #6 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404710] Segmentation fault at KWin::ModifierOnlyShortcuts::keyEvent
https://bugs.kde.org/show_bug.cgi?id=404710 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 405380] New: Apt Updates fail to load in Discover
https://bugs.kde.org/show_bug.cgi?id=405380 Bug ID: 405380 Summary: Apt Updates fail to load in Discover Product: Discover Version: 5.15.2 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Updater Assignee: lei...@leinir.dk Reporter: leftcr...@tutanota.com CC: aleix...@kde.org Target Milestone: --- The update plasmoid show a number of packages, but when you click view updates, you don't see any apt updates in Discover. However, if you disable and then enable ANY apt source, the updates will appear. So every time I want to update I have to go to sources, then toggle a random apt repo on and off. Operating System: Kubuntu 18.10 KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.1 Kernel Version: 4.18.0-16-generic OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 399355] Add callgrind_diff
https://bugs.kde.org/show_bug.cgi?id=399355 --- Comment #13 from Nick Nethercote --- I haven't looked into the problems reported in comment 6. I don't see why this shouldn't be able to work, but the Callgrind format does have a lot of bells and whistles that the Cachegrind format does not, so they have to all be handled appropriately. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 382599] Progress bar does not work correctly during files extraction
https://bugs.kde.org/show_bug.cgi?id=382599 Andrew Crouthamel changed: What|Removed |Added CC||andrew.crouthamel@kdemail.n ||et Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 366159] [unarchiver] Race condition when opening header-encrypted archives
https://bugs.kde.org/show_bug.cgi?id=366159 Andrew Crouthamel changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #4 from Andrew Crouthamel --- Nevermind, I retract that statement. I can get it reproducing now. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 366159] [unarchiver] Race condition when opening header-encrypted archives
https://bugs.kde.org/show_bug.cgi?id=366159 Andrew Crouthamel changed: What|Removed |Added Keywords||investigated, triaged --- Comment #3 from Andrew Crouthamel --- I'm unable to reproduce this on 18.12.3, I tried probably 50 times as fast as possible. Elvis, can you test again? -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 366159] [unarchiver] Race condition when opening header-encrypted archives
https://bugs.kde.org/show_bug.cgi?id=366159 Andrew Crouthamel changed: What|Removed |Added CC||andrew.crouthamel@kdemail.n ||et -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 400018] When installed as a standalone program, Ark fails: Unable to find Ark's KPart Component, please check your installer
https://bugs.kde.org/show_bug.cgi?id=400018 Andrew Crouthamel changed: What|Removed |Added CC||andrew.crouthamel@kdemail.n ||et Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #9 from Andrew Crouthamel --- Yuri, could you please follow up? -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 377887] Crash when opening file from archive
https://bugs.kde.org/show_bug.cgi?id=377887 Andrew Crouthamel changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||andrew.crouthamel@kdemail.n ||et --- Comment #17 from Andrew Crouthamel --- I cannot reproduce either, could you please re-test and/or provide an archive that causes the failure? -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 375681] Not correctly handle binary numbers
https://bugs.kde.org/show_bug.cgi?id=375681 Andrew Crouthamel changed: What|Removed |Added Ever confirmed|0 |1 Keywords||investigated, triaged CC||andrew.crouthamel@kdemail.n ||et Status|REPORTED|CONFIRMED --- Comment #6 from Andrew Crouthamel --- Marking this confirmed, I can reproduce and agree at least an option should be present. As a network engineer, I would expect it to behave in binary, and assume leading zeros. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392556] After updating Fedora-27 to plasma-5.12, login takes >30s
https://bugs.kde.org/show_bug.cgi?id=392556 --- Comment #29 from Darin Miller --- Created attachment 118734 --> https://bugs.kde.org/attachment.cgi?id=118734&action=edit with Splash and auto login disabled Boots quickly to desktop when auto login is not enabled. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392556] After updating Fedora-27 to plasma-5.12, login takes >30s
https://bugs.kde.org/show_bug.cgi?id=392556 --- Comment #28 from Darin Miller --- Kubuntu 18.10/19.04 are also suffering from splash screen delaying desktop display. Attached boot chart with and without splash enabled. BTW, charts captured on a single screen laptop (Dell 7559 booting with Intel video). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392556] After updating Fedora-27 to plasma-5.12, login takes >30s
https://bugs.kde.org/show_bug.cgi?id=392556 Darin Miller changed: What|Removed |Added CC||darinsmil...@gmail.com --- Comment #26 from Darin Miller --- Created attachment 118732 --> https://bugs.kde.org/attachment.cgi?id=118732&action=edit With Splash Slow boot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392556] After updating Fedora-27 to plasma-5.12, login takes >30s
https://bugs.kde.org/show_bug.cgi?id=392556 --- Comment #27 from Darin Miller --- Created attachment 118733 --> https://bugs.kde.org/attachment.cgi?id=118733&action=edit Without Splash fast boot -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 384792] Unwanted row height changes
https://bugs.kde.org/show_bug.cgi?id=384792 --- Comment #4 from Eugene --- Created attachment 118731 --> https://bugs.kde.org/attachment.cgi?id=118731&action=edit cmdline contents -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 384792] Unwanted row height changes
https://bugs.kde.org/show_bug.cgi?id=384792 --- Comment #3 from Eugene --- (In reply to Richard Llom from comment #2) > I cannot reproduce this (also using firefox) on v 5.15. > > Does this still happen to you? Although this does not seem to happen with current Firefox anymore, it still can be reproduced with Firefox v55. Here is a cmdline dump for convenience. To reproduce, for example: $ kwrite `cat firefox-cmdline` -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 405278] [feature request] EPG from xmltv
https://bugs.kde.org/show_bug.cgi?id=405278 --- Comment #6 from higuita --- Created attachment 118730 --> https://bugs.kde.org/attachment.cgi?id=118730&action=edit kaffeine channel list To start, thank you very much for implementing this! :D > Kaffeine's EPG data is stored using channel name, as it was discovered from > MPEG-TS tables. Do you know if the display-name is identical to the channel > name that Kaffeine displays? many are the same, but most of then have little differences, that are enough to break the parser :) Some have H instead of HD, others drop the SD, others simplify the name (RADICAL -> R or Food Network -> TFN ), others change case (SkyNews -> SKY News) I pulled the git and tested, it worked on the names that match (23 from 62 channels i have available in my local DVB-T) Doing the command below and attaching the list echo 'select name from Channels;' | sqlite3 sqlite.db > /tmp/channels.txt But i think it is a lost battle trying to always automatically match all the feeds and channels, we do never know what is out there. Some automatic rules like the current are good to help the initial setup, but in the end one should be able to map the xmltv name to the channel when needed. So i suggest adding a extra rule to also try to match names without the SD and HD if not matched already, as usually the channel and data is the same, only change the resolution. Also always match names with case insensitive After that, in the channels config, add a extra column (may be optional) for epg that show the EPG/xmltv name (or * if same name). This will allow to quickly find out what channels are without EPG and fix then Finally, editing the channel, we would have a new drop down list with the EPG/xmltv name, so one can manually choose the correct feed source for the channel. Of course, this also requires a new field in the database to store this map -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405379] New: Wayland session crashed while I dragged a CSD gtk window
https://bugs.kde.org/show_bug.cgi?id=405379 Bug ID: 405379 Summary: Wayland session crashed while I dragged a CSD gtk window Product: kwin Version: 5.15.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- I was dragging a CSD gtk window (pamac package manager), Wayland session froze and after a few seconds my system went to login screen. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.1 Thread 3 (Thread 0x7f63af624700 (LWP 21246)): #0 0x7f63b7d98c21 in poll () at /usr/lib/libc.so.6 #1 0x7f63b3ce5690 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f63b3ce577e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f63b82cdd04 in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f63a8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f63b8276b2c in QEventLoop::exec(QFlags) (this=this@entry=0x7f63af623cb0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f63b80ba569 in QThread::exec() (this=this@entry=0x7f63b7a6f080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f63b79f3ba6 in QDBusConnectionManager::run() (this=0x7f63b7a6f080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #7 0x7f63b80bb96c in QThreadPrivate::start(void*) (arg=0x7f63b7a6f080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361 #8 0x7f63b6127a9d in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f63b7da3b23 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f63a6521700 (LWP 21248)): #0 0x7f63b612dafc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f63a6b2ec94 in () at /usr/lib/dri/i965_dri.so #2 0x7f63a6b2e9b8 in () at /usr/lib/dri/i965_dri.so #3 0x7f63b6127a9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f63b7da3b23 in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f63b09a4280 (LWP 21245)): #0 0x7f63b7cdfd7f in raise () at /usr/lib/libc.so.6 #1 0x7f63b6513bcf in KCrash::defaultCrashHandler(int) () at /usr/lib/libKF5Crash.so.5 #2 0x7f63b7cdfe00 in () at /usr/lib/libc.so.6 #3 0x7f63b131ce50 in () at /usr/lib/liblmdb.so #4 0x7f63b13208e8 in () at /usr/lib/liblmdb.so #5 0x7f63b131ee69 in mdb_cursor_get () at /usr/lib/liblmdb.so #6 0x7f63b337fdff in Baloo::PostingDB::fetchTermsStartingWith(QByteArray const&) () at /usr/lib/libKF5BalooEngine.so.5 #7 0x7f63b33862d2 in Baloo::Transaction::fetchTermsStartingWith(QByteArray const&) const () at /usr/lib/libKF5BalooEngine.so.5 #8 0x7f63b6b3bb79 in Baloo::TagListJob::start() () at /usr/lib/libKF5Baloo.so.5 #9 0x7f63b85d8cf1 in KJob::exec() () at /usr/lib/libKF5CoreAddons.so.5 #10 0x7f63b9c7 in Gwenview::BalooSemanticInfoBackend::refreshAllTags() () at /usr/lib/libgwenviewlib.so.5 #11 0x7f63b9c71053 in Gwenview::BalooSemanticInfoBackend::allTags() const () at /usr/lib/libgwenviewlib.so.5 #12 0x7f63b9c6d614 in Gwenview::TagModel::createAllTagsModel(QObject*, Gwenview::AbstractSemanticInfoBackEnd*) () at /usr/lib/libgwenviewlib.so.5 #13 0x563291ca219e in () #14 0x7f63b8e8eb68 in QWidget::event(QEvent*) (this=this@entry=0x563292068f50, event=event@entry=0x7fff3ec4a1f0) at kernel/qwidget.cpp:8935 #15 0x7f63b8f3636f in QFrame::event(QEvent*) (this=0x563292068f50, e=0x7fff3ec4a1f0) at widgets/qframe.cpp:550 #16 0x7f63b8e4de24 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x563291d41750, receiver=receiver@entry=0x563292068f50, e=e@entry=0x7fff3ec4a1f0) at kernel/qapplication.cpp:3753 #17 0x7f63b8e556e1 in QApplication::notify(QObject*, QEvent*) (this=0x7fff3ec4a800, receiver=0x563292068f50, e=0x7fff3ec4a1f0) at kernel/qapplication.cpp:3500 #18 0x7f63b8277e99 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x563292068f50, event=0x7fff3ec4a1f0) at ../../include/QtCore/5.12.1/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:322 #19 0x7f63b8e8b3e8 in QWidgetPrivate::show_helper() (this=0x56329204a710) at kernel/qwidget.cpp:8055 #20 0x7f63b8e8b215 in QWidgetPrivate::show_recursive() (this=) at kernel/qwidget.cpp:7926 #21 0x7f63b8e8b34c in QWidgetPrivate::showChildren(bool) (this=this@entry=0x563291e70900, spontaneous=spontaneous@entry=false) at ../../include/QtCore/../../src/corelib/global/qglobal.h:1038 #22 0x7f63b8e8b3c2 in QWidgetPrivate::show_helper() (this=this@entry=0x563291e70900) at ke
[ark] [Bug 368851] Cannot add new files to a specific RAR archive
https://bugs.kde.org/show_bug.cgi?id=368851 Andrew Crouthamel changed: What|Removed |Added Keywords||investigated, triaged CC||andrew.crouthamel@kdemail.n ||et Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #7 from Andrew Crouthamel --- I don't see an error code in 18.12.3 but it indeed does not add the file, so there should be some sort of UI function to reflect the archive is read-only. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 403146] Extracting suggests replacement file with info of destination file
https://bugs.kde.org/show_bug.cgi?id=403146 Andrew Crouthamel changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||andrew.crouthamel@kdemail.n ||et Keywords||investigated, triaged Ever confirmed|0 |1 --- Comment #2 from Andrew Crouthamel --- Confirming based on Patrick's investigation. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 405189] If you take a screenshot, copy it to clipboard and close Spectacle, it's impossible to paste the screenshot into a photo editor
https://bugs.kde.org/show_bug.cgi?id=405189 Andrew Crouthamel changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||andrew.crouthamel@kdemail.n ||et Keywords||investigated, triaged Ever confirmed|0 |1 --- Comment #2 from Andrew Crouthamel --- I can confirm this on 18.12.3 on Neon. The clipboard is cleared upon exit of Spectacle. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 405214] Freezing to try to make a screenshot of configuring screen
https://bugs.kde.org/show_bug.cgi?id=405214 Andrew Crouthamel changed: What|Removed |Added Keywords||investigated, triaged CC||andrew.crouthamel@kdemail.n ||et --- Comment #1 from Andrew Crouthamel --- I'm unable to reproduce this on 18.12.3 on Neon. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 400865] Option "Divide CPU usage by number of CPUs" does not affect the darker histogram in cpu usage field
https://bugs.kde.org/show_bug.cgi?id=400865 --- Comment #3 from Massimiliano --- With reference to the picture in comment 2, you can see four applications running with full CPU usage. Under the number representing the usage percentage, there are two histograms, a light blue one and a dark blue one. As far as I understand, they indicate the instantaneous and time average cpu usage, or some variation of these. The point is that since the cpu is running at constant load, they should overlap. If I toggle "Divide CPU usage by number of CPUs" then the lighter one is resized to 1/4 of its height and kinda overlaps with the darker one. My understanding is that the same should happen even if I toggle the same option again, and both histograms should cover the whole area and overlap. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 400865] Option "Divide CPU usage by number of CPUs" does not affect the darker histogram in cpu usage field
https://bugs.kde.org/show_bug.cgi?id=400865 --- Comment #2 from Massimiliano --- Created attachment 118729 --> https://bugs.kde.org/attachment.cgi?id=118729&action=edit Screenshot of issue -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405378] New: Missing libz.dll on launch
https://bugs.kde.org/show_bug.cgi?id=405378 Bug ID: 405378 Summary: Missing libz.dll on launch Product: digikam Version: 6.1.0 Platform: Other OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Bundle-Windows Assignee: digikam-bugs-n...@kde.org Reporter: bg+k...@cyclos.com Target Milestone: --- SUMMARY With digiKam-6.1.0-git-20190310T212601-Win64.exe, a system dialog stating "The program can't start because libz.dll is missing from your computer." occurs on every launch. This did not occur with the 20190308 build. STEPS TO REPRODUCE 1. Launch digiKam OBSERVED RESULT A system dialog stating "The program can't start because libz.dll is missing from your computer." occurs on every launch. This did not occur with the 20190308 build. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: Windows 7 ADDITIONAL INFORMATION The Program Files directory for digiKam does not contain a libz.dll file. There is a zlib1.dll. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405377] New: Handle new Linux kernel feature: Restartable Sequences ("rseq")
https://bugs.kde.org/show_bug.cgi?id=405377
Bug ID: 405377
Summary: Handle new Linux kernel feature: Restartable Sequences
("rseq")
Product: valgrind
Version: unspecified
Platform: unspecified
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: derek.bruen...@gmail.com
Target Milestone: ---
The Linux kernel has introduced a new feature called "Restartable Sequences"
or "rseq". This raises multiple problems for dynamic binary instrumentation,
including loss of control due to the kernel redirecting the PC and incorrect
application behavior due to failing to preserve the semantics of these
code sequences.
DynamoRIO has looked at and tried to solve these issues for an earlier
version of rseq. The new version of rseq, the one that went into the
official linux kernel, is more difficult to handle and may require
establishing conventions among software developers who use rseq. Given that,
it may make sense to collaboratively come up with a solution that works for
all dynamic instrumentation frameworks.
See Kevin's post to the valgrind-developers list:
https://sourceforge.net/p/valgrind/mailman/valgrind-developers/thread/CAB%3DH8NUgjS9Ee7r_VWoBXafAZVYzW1%2BeHPzmA3j-Qeo2n22nmg%40mail.gmail.com/#msg36584233
See a writeup with further details of rseq and ideas for how to handle it here:
https://github.com/DynamoRIO/dynamorio/wiki/Restartable-Sequences
The kernel commit adding rseq:
https://github.com/torvalds/linux/commit/d82991a8688ad128b46db1b42d5d84396487a508
--
You are receiving this mail because:
You are watching all bug changes.
[kstars] [Bug 404639] Shrunk "View Start Profile" window
https://bugs.kde.org/show_bug.cgi?id=404639 --- Comment #7 from Rob --- Yep, you were quite right. When I made the revisions before 3.1.0 to fix the issues with the star profile viewer appearing, I put the changes into an existing if statement if(mode == FITS_NORMAL || mode == FITS_ALIGN) So the fix did not apply to Guide and Focus views. I just sent a revision to Jasem with the code a bit rearranged so that the fix is now outside the if statement so it works for all star profile views. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 405305] Tooltip has unnecessary line break
https://bugs.kde.org/show_bug.cgi?id=405305 Andrew Crouthamel changed: What|Removed |Added Status|REPORTED|CONFIRMED Severity|normal |minor Keywords||investigated, triaged CC||andrew.crouthamel@kdemail.n ||et Ever confirmed|0 |1 --- Comment #1 from Andrew Crouthamel --- Confirmed on 18.12.3. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 405374] Send to... menu results in error message (Kmail/Evolution)
https://bugs.kde.org/show_bug.cgi?id=405374 --- Comment #1 from David --- Found a solution here: https://ubuntuforums.org/showthread.php?t=2338516 sudo apt-get install --reinstall plasma-workspace Should still be investigated maybe? -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 405376] New: Simple Simon no longer autodrops
https://bugs.kde.org/show_bug.cgi?id=405376 Bug ID: 405376 Summary: Simple Simon no longer autodrops Product: kpat Version: 3.6 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: co...@kde.org Reporter: q@rsn-tech.co.uk CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY When you complete a column, Simple Simon no longer automatically moves it to a top pile STEPS TO REPRODUCE 1. Play Simple Simon with autodrop enabled 2. Complete a suit column OBSERVED RESULT Nothing happens EXPECTED RESULT The column should automatically move to an empty pile slot SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: Linux (x86_64) release 4.20.14-200.fc29.x86_64 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 405375] New: Crash in kdiff3
https://bugs.kde.org/show_bug.cgi?id=405375 Bug ID: 405375 Summary: Crash in kdiff3 Product: kdiff3 Version: 1.7.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: reeves...@gmail.com Reporter: flor...@loitsch.com Target Milestone: --- Created attachment 118728 --> https://bugs.kde.org/attachment.cgi?id=118728&action=edit tar of the 3 files that make kdiff3 crash. (Also contains a shell script to launch kdiff3 with the correct arguments). SUMMARY When comparing the attached files, kdiff3 crashes with """ Severe internal error Data loss error: If it is reproducible please contact the author. """ STEPS TO REPRODUCE 1. run: ``` diff3 --auto -o Changelog ./Changelog_BASE_12356 ./Changelog_LOCAL_12356 ./Changelog_REMOTE_12356 ``` OBSERVED RESULT Crash EXPECTED RESULT Merging of files. SOFTWARE/OS VERSIONS Windows: - MacOS: - Linux/KDE Plasma: Linux, Archlinux (available in About System) KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.1 ADDITIONAL INFORMATION Kdiff3 Version 1.7.95 (64 bit) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405017] baloo_file_extractor crash, in Exiv2::DataValue::toLong in kfilemetadata_exiv2extractor
https://bugs.kde.org/show_bug.cgi?id=405017 --- Comment #5 from skierpage --- Created attachment 118727 --> https://bugs.kde.org/attachment.cgi?id=118727&action=edit New crash information added by DrKonqi baloo_file_extractor (5.55.0) using Qt 5.11.3 - What I was doing when the application crashed: On restart I guess baloo tried to index a problem file again, and it reported a crash. The backtrace includes Exiv2Extractor:fetchGpsAltitude. `exiv2 print -p a`reports pretty similar GPSAltitude info in the problem file compared to a working panorama, so maybe it isn't the value but the structure or size of the image and its metadata. -- Backtrace (Reduced): #8 0x7f1620856278 in std::__replacement_assert (__file=__file@entry=0x7f162096ff08 "/usr/include/c++/8/bits/stl_vector.h", __line=__line@entry=950, __function=__function@entry=0x7f16209cc740 >::operator[](unsigned long) const::__PRETTY_FUNCTION__> "std::vector<_Tp, _Alloc>::const_reference std::vector<_Tp, _Alloc>::operator[](std::vector<_Tp, _Alloc>::size_type) const [with _Tp = unsigned char; _Alloc = std::allocator; std::vector"..., __condition=__condition@entry=0x7f162096fed8 "__builtin_expect(__n < this->size(), true)") at /usr/include/c++/8/x86_64-redhat-linux/bits/c++config.h:2389 #9 0x7f162090dc85 in std::vector >::operator[] (__n=, this=) at /usr/src/debug/exiv2-0.26-12.fc29.x86_64/src/value.cpp:229 #10 Exiv2::DataValue::write (os=..., this=) at /usr/src/debug/exiv2-0.26-12.fc29.x86_64/src/value.cpp:233 #11 0x7f162090dcb9 in Exiv2::DataValue::toLong (this=, n=) at /usr/include/c++/8/bits/stl_vector.h:948 #12 0x7f1620fcb56c in KFileMetaData::Exiv2Extractor::fetchGpsAltitude (this=, data=...) at /usr/include/c++/8/ext/aligned_buffer.h:74 -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 398275] Incorrect tab index on Login into the KDE Bug Tracking System page
https://bugs.kde.org/show_bug.cgi?id=398275 --- Comment #2 from Patrick Silva --- also confirmed on Arch Linux, plasma 5.15.2. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 405374] New: Send to... menu results in error message (Kmail/Evolution)
https://bugs.kde.org/show_bug.cgi?id=405374 Bug ID: 405374 Summary: Send to... menu results in error message (Kmail/Evolution) Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: kaig...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Use LibreOffice or any other program's internal menu to attach a file to your email program (if it's not KMail). Send to... results in "Could not find the program 'kmailservice'" (which makes sense because it's not installed, I'm using Evolution which has been working just fine up to the recent installation of kframework 5.56!) EXPECTED RESULT Send to... results in Evolution being opened and the file attached to a new email. Operating System: KDE neon 5.15 KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.0 Kernel Version: 4.15.0-46-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4300U CPU @ 1.90GHz Memory: 11,6 GiB of RAM ADDITIONAL INFORMATION This has just recently happend with the latetest update to Frameworks 5.56. Before that it worked just fine. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 398275] Incorrect tab index on Login into the KDE Bug Tracking System page
https://bugs.kde.org/show_bug.cgi?id=398275 skierpage changed: What|Removed |Added Ever confirmed|0 |1 CC||skierp...@gmail.com Status|REPORTED|CONFIRMED --- Comment #1 from skierpage --- Still true in version 5.14.5 on Fedora. The Password field seems to be the first tab index even though it's below the Username field. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 405373] New: KInfoCenter is now following the current Click behavior
https://bugs.kde.org/show_bug.cgi?id=405373 Bug ID: 405373 Summary: KInfoCenter is now following the current Click behavior Product: kinfocenter Version: 5.15.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: hubn...@gmail.com Reporter: thunder...@verizon.net Target Milestone: --- SUMMARY When selecting each of the sections on the left, you are now required to double-click the item if you have the Click behavior set for double-click to open files and folders (single click to select). This seems inappropriate for this program, single click does nothing and makes it look like the program doesn't work (which can confuse users). STEPS TO REPRODUCE 1. System Settings/Workspace/Desktop Behavior/Click behavior, set for Double-click 2. Set KInfoCenter 3. Select (single-click) any section, nothing happens. 4. Double-click any section, and the section is shown. OBSERVED RESULT Selecting a section does nothing. EXPECTED RESULT The section should be shown. SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: KDE Neon 5.15 User Edition (available in About System) KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION Works as expected when Click behavior is set for Single-click to open files and folders. The issue was probably introduced by Bug ID 399962. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 405372] New: merge open windows into tabs in a single window
https://bugs.kde.org/show_bug.cgi?id=405372 Bug ID: 405372 Summary: merge open windows into tabs in a single window Product: konsole Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: tabbar Assignee: konsole-de...@kde.org Reporter: m.j.gri...@gmail.com Target Milestone: --- SUMMARY merge open konsole windows into tabs in a single window SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372487] BQM says there are unprocessed items even though it completed successfully and all images were processed
https://bugs.kde.org/show_bug.cgi?id=372487 caulier.gil...@gmail.com changed: What|Removed |Added Version|5.3.0 |6.1.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372487] BQM says there are unprocessed items even though it completed successfully and all images were processed
https://bugs.kde.org/show_bug.cgi?id=372487 --- Comment #6 from Geoff King --- Tested. Still the same with 6.1.0 pre-release as when originally reported. I think all that is needed when removing a queue is a text change to something like this: "There are still XX items in queue "#Y". "Are you sure you want to remove this queue?" -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 405371] New: [wayland] Crash when resuming from suspend
https://bugs.kde.org/show_bug.cgi?id=405371 Bug ID: 405371 Summary: [wayland] Crash when resuming from suspend Product: kdevelop Version: 5.3.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: frmdst...@protonmail.com Target Milestone: --- Application: kdevelop (5.3.2) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.15.0-46-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: - What I was doing when the application crashed: It crashed immediately when my laptop resumed from suspend. I have a second monitor plugged in if that matters. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f97f1b8abc0 (LWP 15724))] Thread 15 (Thread 0x7f978214c700 (LWP 15919)): #0 0x7f97e4cfe43b in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f97e4d009d3 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f97e4d0146b in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f97e4d0164c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f97eeaaa15b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f9774013930, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7f97eea4b64a in QEventLoop::exec(QFlags) (this=this@entry=0x7f978214b910, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7f97ee87341a in QThread::exec() (this=this@entry=0x5571b024ad50) at thread/qthread.cpp:531 #7 0x7f97ecf7af0f in KDevelop::CompletionWorkerThread::run() (this=0x5571b024ad50) at ./kdevplatform/language/codecompletion/codecompletionmodel.cpp:79 #8 0x7f97ee874bc2 in QThreadPrivate::start(void*) (arg=0x5571b024ad50) at thread/qthread_unix.cpp:361 #9 0x7f97e6e9d6db in start_thread (arg=0x7f978214c700) at pthread_create.c:463 #10 0x7f97ee17488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7f9778a65700 (LWP 15908)): #0 0x7f97e6ea39f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5571869d06c4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f97e6ea39f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5571869d0670, cond=0x5571869d0698) at pthread_cond_wait.c:502 #2 0x7f97e6ea39f3 in __pthread_cond_wait (cond=0x5571869d0698, mutex=0x5571869d0670) at pthread_cond_wait.c:655 #3 0x7f97ee87bb4b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x5571869d0670) at thread/qwaitcondition_unix.cpp:146 #4 0x7f97ee87bb4b in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x5571869e1f30, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f97ee87be59 in QWaitCondition::wait(QMutex*, unsigned long) (this=0x5571869e1e98, mutex=0x5571869e1f30, time=) at thread/qwaitcondition_unix.cpp:208 #6 0x7f97e4a9f935 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f97e4aa37e8 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f97e4a9ebfd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f97e4aa16ab in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7f97ee874bc2 in QThreadPrivate::start(void*) (arg=0x5571b1070de0) at thread/qthread_unix.cpp:361 #11 0x7f97e6e9d6db in start_thread (arg=0x7f9778a65700) at pthread_create.c:463 #12 0x7f97ee17488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7f9779266700 (LWP 15907)): #0 0x7f97e6ea39f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5571869d06c4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f97e6ea39f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5571869d0670, cond=0x5571869d0698) at pthread_cond_wait.c:502 #2 0x7f97e6ea39f3 in __pthread_cond_wait (cond=0x5571869d0698, mutex=0x5571869d0670) at pthread_cond_wait.c:655 #3 0x7f97ee87bb4b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x5571869d0670) at thread/qwaitcondition_unix.cpp:146 #4 0x7f97ee87bb4b in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x5571869e1f30, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f97ee87be59 in QWaitCondition::wait(QMutex*, unsigned long) (this=0x5571869e1e98, mutex=0x5571869e1f30, time=) at thread/qwaitcondition_unix.cpp:208 #6 0x7f97e4a9f935 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Th
[digikam] [Bug 365263] Dragging a image to an Album cannot see which album easily
https://bugs.kde.org/show_bug.cgi?id=365263 caulier.gil...@gmail.com changed: What|Removed |Added Version|5.0.0 |6.1.0 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #130 from Rafael Kitover --- I switched to Geary, it's beautiful and modern and works perfectly with gmail. It's GTK but it works perfectly in KDE :D -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 365263] Dragging a image to an Album cannot see which album easily
https://bugs.kde.org/show_bug.cgi?id=365263 --- Comment #2 from Geoff King --- Tested. I see no changes in the way it works with the 6.1.0 pre-release. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 405370] New: gwenview crashed immediately when I tried to start it via the apps launcher
https://bugs.kde.org/show_bug.cgi?id=405370 Bug ID: 405370 Summary: gwenview crashed immediately when I tried to start it via the apps launcher Product: gwenview Version: 18.12.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- I tried to open gwenview via the apps launcher (kickoff) and plasma immediately shown a crash notification. So I opened gwenview without any problem by double-clicking a picture in Dolphin. I was able to reproduce the crash a few times, now gwenview is working as expected. Operating System: Arch Linux KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.1 Thread 3 (Thread 0x7f63af624700 (LWP 21246)): #0 0x7f63b7d98c21 in poll () at /usr/lib/libc.so.6 #1 0x7f63b3ce5690 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f63b3ce577e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f63b82cdd04 in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f63a8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f63b8276b2c in QEventLoop::exec(QFlags) (this=this@entry=0x7f63af623cb0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f63b80ba569 in QThread::exec() (this=this@entry=0x7f63b7a6f080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f63b79f3ba6 in QDBusConnectionManager::run() (this=0x7f63b7a6f080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #7 0x7f63b80bb96c in QThreadPrivate::start(void*) (arg=0x7f63b7a6f080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361 #8 0x7f63b6127a9d in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f63b7da3b23 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f63a6521700 (LWP 21248)): #0 0x7f63b612dafc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f63a6b2ec94 in () at /usr/lib/dri/i965_dri.so #2 0x7f63a6b2e9b8 in () at /usr/lib/dri/i965_dri.so #3 0x7f63b6127a9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f63b7da3b23 in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f63b09a4280 (LWP 21245)): #0 0x7f63b7cdfd7f in raise () at /usr/lib/libc.so.6 #1 0x7f63b6513bcf in KCrash::defaultCrashHandler(int) () at /usr/lib/libKF5Crash.so.5 #2 0x7f63b7cdfe00 in () at /usr/lib/libc.so.6 #3 0x7f63b131ce50 in () at /usr/lib/liblmdb.so #4 0x7f63b13208e8 in () at /usr/lib/liblmdb.so #5 0x7f63b131ee69 in mdb_cursor_get () at /usr/lib/liblmdb.so #6 0x7f63b337fdff in Baloo::PostingDB::fetchTermsStartingWith(QByteArray const&) () at /usr/lib/libKF5BalooEngine.so.5 #7 0x7f63b33862d2 in Baloo::Transaction::fetchTermsStartingWith(QByteArray const&) const () at /usr/lib/libKF5BalooEngine.so.5 #8 0x7f63b6b3bb79 in Baloo::TagListJob::start() () at /usr/lib/libKF5Baloo.so.5 #9 0x7f63b85d8cf1 in KJob::exec() () at /usr/lib/libKF5CoreAddons.so.5 #10 0x7f63b9c7 in Gwenview::BalooSemanticInfoBackend::refreshAllTags() () at /usr/lib/libgwenviewlib.so.5 #11 0x7f63b9c71053 in Gwenview::BalooSemanticInfoBackend::allTags() const () at /usr/lib/libgwenviewlib.so.5 #12 0x7f63b9c6d614 in Gwenview::TagModel::createAllTagsModel(QObject*, Gwenview::AbstractSemanticInfoBackEnd*) () at /usr/lib/libgwenviewlib.so.5 #13 0x563291ca219e in () #14 0x7f63b8e8eb68 in QWidget::event(QEvent*) (this=this@entry=0x563292068f50, event=event@entry=0x7fff3ec4a1f0) at kernel/qwidget.cpp:8935 #15 0x7f63b8f3636f in QFrame::event(QEvent*) (this=0x563292068f50, e=0x7fff3ec4a1f0) at widgets/qframe.cpp:550 #16 0x7f63b8e4de24 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x563291d41750, receiver=receiver@entry=0x563292068f50, e=e@entry=0x7fff3ec4a1f0) at kernel/qapplication.cpp:3753 #17 0x7f63b8e556e1 in QApplication::notify(QObject*, QEvent*) (this=0x7fff3ec4a800, receiver=0x563292068f50, e=0x7fff3ec4a1f0) at kernel/qapplication.cpp:3500 #18 0x7f63b8277e99 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x563292068f50, event=0x7fff3ec4a1f0) at ../../include/QtCore/5.12.1/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:322 #19 0x7f63b8e8b3e8 in QWidgetPrivate::show_helper() (this=0x56329204a710) at kernel/qwidget.cpp:8055 #20 0x7f63b8e8b215 in QWidgetPrivate::show_recursive() (this=) at kernel/qwidget.cpp:7926 #21 0x7f63b8e8b34c in QWidgetPrivate::showChildren(bool) (this=this@entry=0x563291e70900, spontaneous=spontaneous@entry=false) at ../../include/QtC
[latte-dock] [Bug 405311] latte-dock icons not showing up
https://bugs.kde.org/show_bug.cgi?id=405311 --- Comment #4 from Tycho Grouwstra --- Created attachment 118726 --> https://bugs.kde.org/attachment.cgi?id=118726&action=edit ksysguard showing icons, latte-dock not showing them Hi, I hope this screenshot is as you intended. In it, the icons can be seen in ksysguard, though not in latte-dock. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 405313] kalarm freezes in gnome
https://bugs.kde.org/show_bug.cgi?id=405313 --- Comment #2 from David Jarvie --- This looks similar to bug 392357. The culprit is likely to be Akonadi. There is a goal to replace the use of Akonadi for KAlarm, but this will take some time yet. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 405323] Suggestion & question: Backups
https://bugs.kde.org/show_bug.cgi?id=405323 --- Comment #1 from David Jarvie --- You should check the location of KAlarm's calendar files as follows. In the menu, use View -> Show Calendars. Hover the mouse over each calendar shown there, and it will display the location of the file used to store that calendar. You can use the pull-down selector to show Archived Alarms and Alarm Templates in addition to the default Active Alarms, to show other alarm calendars (if you use them). These files are probably in ~/.local/share/kalarm, which is the directory you mention. To back up KAlarm, save those calendar files, and also save the file 'kalarmc' which is probably in the directory ~/.config . Note that in order to restore the files, you need to ensure that KAlarm is not running, and also that Akonadi is not running. Use the Quit option in the KAlarm menu to exit KAlarm, and then, in a terminal window, type the command akonadictl stop and press Enter. Allow a few seconds for Akonadi to stop, and then restore the files. After that, run KAlarm. KAlarm should not crash when copying or restoring files. When did KAlarm crash? Can you please attach a crash report which you should be prompted to get if it crashes. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 403803] Memory leak in Kaffeine when using deinterlacing
https://bugs.kde.org/show_bug.cgi?id=403803 --- Comment #4 from Mauro Carvalho Chehab --- (In reply to Petr Kovács from comment #3) > Mauro, I'm not sure if we understand each other. The problem occurs when you > set deinterlacing method to "discard". When you disable deinterlacing or use > another method than discard, everything is fine. > > When discard is selected, Kaffeine's memory consumption grows by 23 MiB each > time TOP refreshes (which is every 3 seconds on my computer). At this rate, > you are out of memory in a few minutes (depending on your RAM size of > course). Wow! I can't reproduce this behaviour here. Anyway, it is libvlc with handles de-interlacing. Here, I'm using version 3.0.6, with is the latest stable one while playing a *.mp4 file. No memory consumption increase on such rate (it has a small increase at the beggining, while libVlc is doing some buffering). With DVB, memory consumption may grow with time, due to EPG data. > > I'm using nouveau graphics driver on GeForce GTX460. I will try to install > the proprietary nvidia drivers and check if that helps. I would rely a lot more on nouveau than with nvidia proprietary driver. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405051] Linear gradient from Inkscape not displayed correctly
https://bugs.kde.org/show_bug.cgi?id=405051 roxy-kde...@ritzke.net changed: What|Removed |Added CC||roxy-kde...@ritzke.net --- Comment #1 from roxy-kde...@ritzke.net --- Failed to reproduce, gradients were rendered the same. Running Arch Linux with MATE desktop environment Inkscape ver. 0.92.4 Krita ver. 4.1.8 -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 403874] Kaffeine scanlist channels lost
https://bugs.kde.org/show_bug.cgi?id=403874 --- Comment #11 from Mauro Carvalho Chehab --- And run it from the git tree, instead of installing, with: $ src/kaffeine (you may also install, if you want - install instructions are also at the README.md file) -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 403874] Kaffeine scanlist channels lost
https://bugs.kde.org/show_bug.cgi?id=403874 --- Comment #10 from Mauro Carvalho Chehab --- (In reply to compi-killer from comment #9) > (In reply to Mauro Carvalho Chehab from comment #8) > > > rights where ok, but only the first channels added to channle list where > > > inside. > > > After trying repait without success, I killed kaffeine plus killed > > > database. > > > After re-install all seemed fine...till i closed kaffeine and restarted. > > > Then again scan could only find a few channels. > > > > Channels are saved at mySql database when Kaffeine quits without errors. I > > found a few issues on Kaffeine's exit code that got fixed after 2.0.16. > > > > Basically, using the (x) button of Kaffeine was doing something different > > than Ctrl-Q or "File" -> "Exit". This could explain the issues you're > > facing. > > > > Could you please test it from git tree, where such issue got solved? > > > Yes I know the problem with (x), so I quit over programme exit or rightclick > at symbol in task bar, selecting quit to exit. > > So this is not my problem. > > And no...both my linux and my english knowledge are not good enough to > exactly understand what you mean with git tree solving I mean: $ git clone git://anongit.kde.org/kaffeine Then following the build instructions at https://cgit.kde.org/kaffeine.git/tree/README.md And run it with: -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 404119] 100% CPU Core Usage In KSysGuard And CPU Widget, But 2% In Top And HTop And /Proc/Stat
https://bugs.kde.org/show_bug.cgi?id=404119 --- Comment #3 from naroyce --- That reply would've been more helpful sooner rather than over 1 month. I ended up updating my system which also required a reboot and I haven't had the issue. That was the ONLY time I've ever noticed the issue which is why time was important in getting it debugged to figure out the cause. I don't recall if I had done the "new tab" in ksysmon, but given that the sensor widget also reflected the same issue, I'm led to believe the issue lay with whatever data source they got their information from... and THAT is what I'd like to know. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 405278] [feature request] EPG from xmltv
https://bugs.kde.org/show_bug.cgi?id=405278 --- Comment #5 from Mauro Carvalho Chehab --- (In reply to Mauro Carvalho Chehab from comment #3) > On a quick look, I guess that the main challenge is how to map the channel > ID provided by xmltv into the channel data stored at the mysql tables used > by Kaffeine, at epgdata.dvb file. > > From the file you posted, xmltv stores channels like: > > > Bloomberg > ... > > Blaze HD > > > Kaffeine's EPG data is stored using channel name, as it was discovered from > MPEG-TS tables. Do you know if the display-name is identical to the channel > name that Kaffeine displays? > > On a quick look, it doesn't sound hard to parse the tables > > One challenge is how to handle languages. Instead of ISO639 3-letter code, > as found at MPEG-TS tables, it uses ISO 639 2-letter codes, but the DTD file > says: > > Many of the details have a 'lang' attribute so that you can > store them in multiple languages or have mixed languages in a single > listing. This 'lang' should be the two-letter code such as 'en' or > 'fr_FR'. Or you can just leave it out and let your reader take a > guess. > > Adding support for 2-letter codes is easy, but converting 'fr_FR', 'pt_BR', > ... formats to ISO 639 3-letter codes could be a little tricky. I can't find > an easy way of doing that. It is easier to just ignore the Country > information and use just the 2 letter code. > > Could you please record ~60 seconds of a channel and place on GoogleDrive > (or something similar) from one channel that has EPG data? I need the record > of the entire transponder, in order to have all MPEG tables there, and be > able to test some code that would map xmltv data into Kaffeine's EPG > internal representation. > > In order to get it, you should use dvbv5-zap. Instructions about how to use > it are at: > > https://linuxtv.org/wiki/index.php/Dvbv5- > zap#Recording_the_full_MPEG_stream_on_a_transponder No need anymore. Some of the channels on the xmltv file you provided are identical to the channel names I have here. So, I was able to test it. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 405278] [feature request] EPG from xmltv
https://bugs.kde.org/show_bug.cgi?id=405278 Mauro Carvalho Chehab changed: What|Removed |Added Latest Commit||https://commits.kde.org/kaf ||feine/2380ab25da84c999ea14c ||d6bb34e0328e9c67059 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Mauro Carvalho Chehab --- Git commit 2380ab25da84c999ea14cd6bb34e0328e9c67059 by Mauro Carvalho Chehab. Committed on 11/03/2019 at 21:38. Pushed by mauroc into branch 'master'. xmltv: add a parser for XMLTV EPG data files This parser handles XMLTV format files as specified at: http://wiki.xmltv.org/index.php/Main_Page The way the parser was written, once a file is added to the parser, it keeps monitoring it for file changes. When a file change is detected, it will reload the file and parse it, adding entries to the EPG guide. Signed-off-by: Mauro Carvalho Chehab M +2-1src/CMakeLists.txt M +7-0src/dvb/dvbchannel.cpp M +1-0src/dvb/dvbchannel.h M +44 -15 src/dvb/dvbconfigdialog.cpp M +2-0src/dvb/dvbconfigdialog.h M +20 -0src/dvb/dvbmanager.cpp M +4-0src/dvb/dvbmanager.h A +261 -0src/dvb/xmltv.cpp [License: GPL (v2+)] A +56 -0src/dvb/xmltv.h [License: GPL (v2+)] https://commits.kde.org/kaffeine/2380ab25da84c999ea14cd6bb34e0328e9c67059 -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 403304] Can't figure out how to plot data against second y-axis
https://bugs.kde.org/show_bug.cgi?id=403304 --- Comment #3 from Justin --- As an addition to this, it would be really helpful to scale the data against the given axis. I would like to be able to have one set of data plotted linearly and the other logarithmic. Right now all log(y) seems to do is change the tic spacing. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 403304] Can't figure out how to plot data against second y-axis
https://bugs.kde.org/show_bug.cgi?id=403304 Justin changed: What|Removed |Added CC||jr...@cornell.edu --- Comment #2 from Justin --- Created attachment 118725 --> https://bugs.kde.org/attachment.cgi?id=118725&action=edit Dual scale graph -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405369] New: Cursor preferences no longer respected
https://bugs.kde.org/show_bug.cgi?id=405369 Bug ID: 405369 Summary: Cursor preferences no longer respected Product: krita Version: nightly build (please specify the git hash!) Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: bee...@bitmessage.ch Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Go to settings and set cursor shape to show no cursor. 2. Draw or paint something; cursor isn't shown; just the outline or whatever other option is set under outline shape. 3. Move the cursor outside of the canvas area and select something else like a layer. 4. Move the cursor back to the canvas. OBSERVED RESULT The cursor is displayed along with the outline shape. EXPECTED RESULT The cursor continues not to be displayed; only the outline shape. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch, kernel 5.0.0 (available in About System) KDE Plasma Version: N/A, using i3wm KDE Frameworks Version: 5.55.0 Qt Version: 5.12.1 ADDITIONAL INFORMATION Only occurs in 4.1.8, doesn't happen in 4.1.7. git hash 4d9ed8e2e78a -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 405368] New: [wayland] Crash when clicking job status during parsing
https://bugs.kde.org/show_bug.cgi?id=405368 Bug ID: 405368 Summary: [wayland] Crash when clicking job status during parsing Product: kdevelop Version: 5.3.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: frmdst...@protonmail.com Target Milestone: --- Application: kdevelop (5.3.2) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.15.0-46-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: - What I was doing when the application crashed: Just opened KDevelop, clicked the parse job status (bottom right) when it was at about 6% and it crashed (very large project). -- Backtrace: Application: KDevelop (kdevelop), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". __lll_lock_wait_private () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95 [Current thread is 1 (Thread 0x7f7d074a5bc0 (LWP 14094))] Thread 17 (Thread 0x7f7c7df28700 (LWP 14458)): #0 0x7f7d03a82bf9 in __GI___poll (fds=0x7f7c70115820, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f7cfa61c539 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7cfa61c64c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7d043c515b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f7c700418d0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f7d0436664a in QEventLoop::exec(QFlags) (this=this@entry=0x7f7c7df27910, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f7d0418e41a in QThread::exec() (this=this@entry=0x5640f8043da0) at thread/qthread.cpp:531 #6 0x7f7d02895f0f in KDevelop::CompletionWorkerThread::run() (this=0x5640f8043da0) at ./kdevplatform/language/codecompletion/codecompletionmodel.cpp:79 #7 0x7f7d0418fbc2 in QThreadPrivate::start(void*) (arg=0x5640f8043da0) at thread/qthread_unix.cpp:361 #8 0x7f7cfc7b86db in start_thread (arg=0x7f7c7df28700) at pthread_create.c:463 #9 0x7f7d03a8f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7f7c5bfff700 (LWP 14287)): #0 0x7f7cfc7be9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5640c7bdc5d4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f7cfc7be9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5640c7bdc580, cond=0x5640c7bdc5a8) at pthread_cond_wait.c:502 #2 0x7f7cfc7be9f3 in __pthread_cond_wait (cond=0x5640c7bdc5a8, mutex=0x5640c7bdc580) at pthread_cond_wait.c:655 #3 0x7f7d04196b4b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x5640c7bdc580) at thread/qwaitcondition_unix.cpp:146 #4 0x7f7d04196b4b in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x5640c7c798e0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f7d04196e59 in QWaitCondition::wait(QMutex*, unsigned long) (this=0x5640c7c79848, mutex=0x5640c7c798e0, time=) at thread/qwaitcondition_unix.cpp:208 #6 0x7f7cfa3ba935 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f7cfa3be7e8 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f7cfa3b9bfd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f7cfa3bc6ab in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7f7d0418fbc2 in QThreadPrivate::start(void*) (arg=0x7f7c600025e0) at thread/qthread_unix.cpp:361 #11 0x7f7cfc7b86db in start_thread (arg=0x7f7c5bfff700) at pthread_create.c:463 #12 0x7f7d03a8f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7f7c74a8d700 (LWP 14286)): #0 0x7f7cfc7be9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5640c7bdc5d4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f7cfc7be9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5640c7bdc580, cond=0x5640c7bdc5a8) at pthread_cond_wait.c:502 #2 0x7f7cfc7be9f3 in __pthread_cond_wait (cond=0x5640c7bdc5a8, mutex=0x5640c7bdc580) at pthread_cond_wait.c:655 #3 0x7f7d04196b4b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x5640c7bdc580) at thread/qwaitcondition_unix.cpp:146 #4 0x7f7d04196b4b in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x5640c7c798e0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f7d04196e59 in QWaitCondition::wait(QMutex*, unsigned long) (this=0x5640c7c79848, mutex=0x5640c7c798e0, time=) at thread/qwaitcondition_unix.cpp:208 #6 0x7f7cfa3ba935 in ThreadWeav
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #129 from Søren Holm --- I don't think that *anyone* knows what the problem is. This "mail in database"-system should never have been done in the first place. I still use kmail/kontact but tt has been functioning suboptimal all the years. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 405351] Plasma crashes with frameworks-plasma 5.56.0
https://bugs.kde.org/show_bug.cgi?id=405351 David Faure changed: What|Removed |Added CC||fa...@kde.org Assignee|notm...@gmail.com |mon...@kde.org --- Comment #9 from David Faure --- Looks like a missing null check before using sourceModel(), in roleNames(). -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 405325] Meridian flip if HA>
https://bugs.kde.org/show_bug.cgi?id=405325 --- Comment #4 from Jean-Claude --- Wolfgang, I will repeat again the test to-morrow morning to provide a clear answer. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 404965] Scrollbar arrows don't work properly in System Settings sidebar view
https://bugs.kde.org/show_bug.cgi?id=404965 Nate Graham changed: What|Removed |Added Component|sidebarview |general Version|5.15.2 |5.56.0 Product|systemsettings |frameworks-kirigami Summary|Scrollbar arrows doesn't|Scrollbar arrows don't work |work in side bar|properly in System Settings ||sidebar view Target Milestone|--- |Not decided -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 405325] Meridian flip if HA>
https://bugs.kde.org/show_bug.cgi?id=405325 --- Comment #3 from Wolfgang Reissenberger --- Jean-Claude, could you please be a little more specific, what the problem is? Here some background how it is built: the meridian flip is controlled by the Mount module. At the same time, in a capture schedule considering a meridian flip can be defined. When values are set in a capture schedule, the values are transferred to the Mount tab as soon as the capture plan has been startet - but not immediately when defining the values in the capture schedule. When a capture schedule is executed, the Mount module takes into account whether a capture is running a soon as the meridian flip limit has been reached. If this is the case, it waits until the next frame has been captured - that's why it signals "Meridian flip waiting ..." So in case you see this message, it behaves as planned - as long as a capture is running. Or wasn't this the case? The only thing what seems to be a bug are the different increments in the two models. Wolfgang -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 403803] Memory leak in Kaffeine when using deinterlacing
https://bugs.kde.org/show_bug.cgi?id=403803 --- Comment #3 from Petr Kovács --- Mauro, I'm not sure if we understand each other. The problem occurs when you set deinterlacing method to "discard". When you disable deinterlacing or use another method than discard, everything is fine. When discard is selected, Kaffeine's memory consumption grows by 23 MiB each time TOP refreshes (which is every 3 seconds on my computer). At this rate, you are out of memory in a few minutes (depending on your RAM size of course). I'm using nouveau graphics driver on GeForce GTX460. I will try to install the proprietary nvidia drivers and check if that helps. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 405280] Wish: Dropping text on the line number border should insert at the beginning of that line.
https://bugs.kde.org/show_bug.cgi?id=405280 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405333] Unexpected connections between fast, short, close brush strokes.
https://bugs.kde.org/show_bug.cgi?id=405333 --- Comment #3 from acc4commissi...@gmail.com --- Driver is 6.3.32-4. But the bug is not specific to this version. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 383534] Folder open dialog: clicking on Places panel entry should expand its tree in the main view
https://bugs.kde.org/show_bug.cgi?id=383534 --- Comment #4 from David Palacio --- Git commit 51ba55f2c5cc598eea79d2e4d99c21f4baae179a by David Palacio. Committed on 11/03/2019 at 20:26. Pushed by davidp into branch 'master'. Remove URLs being fetched when listing job is completed Remove the discard URL logic from _k_slotNewItems and move it to a new slot _k_slotCompleted so that KDirModel can process as many batches as needed until its job is finished. Reviewed By: dfaure Differential Revision: https://phabricator.kde.org/D19586 M +11 -2src/widgets/kdirmodel.cpp https://commits.kde.org/kio/51ba55f2c5cc598eea79d2e4d99c21f4baae179a -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405333] Unexpected connections between fast, short, close brush strokes.
https://bugs.kde.org/show_bug.cgi?id=405333 --- Comment #2 from acc4commissi...@gmail.com --- (In reply to Boudewijn Rempt from comment #1) > What tablet and tablet driver are you using? Wacom intuos pro medium. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 405359] “Default applications” should provide clearer options for “Web browser”
https://bugs.kde.org/show_bug.cgi?id=405359 --- Comment #1 from ariasuni --- I meant KDE Plasma Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 405355] Bypass of password login in kscreenlocker after resuming screens from energy save mode.
https://bugs.kde.org/show_bug.cgi?id=405355 Oskar Roesler changed: What|Removed |Added Summary|Bypass of password login in |Bypass of password login in |klockscreen after resuming |kscreenlocker after |screens from energy save|resuming screens from |mode. |energy save mode. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405367] New: Dnd from Wayland to X fails assert
https://bugs.kde.org/show_bug.cgi?id=405367 Bug ID: 405367 Summary: Dnd from Wayland to X fails assert Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: subd...@gmail.com Target Milestone: --- This happened to me once since the XWayland DND patches were merged. I started a drag in Dolphin and it directly failed the assert that there must not be any other Wayland drag at the same time. I.e. some time before a previous Wayland native drag must have happened and not have been cleaned up correctly. Maybe it got aborted? Backtrace: #0 0x7f7617c92e97 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x7f7617c948db in __GI_abort () at abort.c:100 #2 0x7f7618679e7b in qErrnoWarning(char const*, ...) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f7618679671 in qt_assert_x(char const*, char const*, char const*, int) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x558809ad8826 in KWin::Xwl::Dnd::startDrag() (this=0x55880b4d9ac0) at /home/roman/dev/kde/src/kde/workspace/kwin/xwl/dnd.cpp:198 #5 0x558809adb276 in QtPrivate::FunctorCall, QtPrivate::List<>, void, void (KWin::Xwl::Dnd::*)()>::call(void (KWin::Xwl::Dnd::*)(), KWin::Xwl::Dnd*, void**) (f=(void (KWin::Xwl::Dnd::*)(KWin::Xwl::Dnd * const)) 0x558809ad879a , o=0x55880b4d9ac0, arg=0x7ffe595d4d00) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:152 #6 0x558809adae84 in QtPrivate::FunctionPointer::call, void>(void (KWin::Xwl::Dnd::*)(), KWin::Xwl::Dnd*, void**) (f=(void (KWin::Xwl::Dnd::*)(KWin::Xwl::Dnd * const)) 0x558809ad879a , o=0x55880b4d9ac0, arg=0x7ffe595d4d00) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:185 #7 0x558809ada09c in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0x55880b041a40, r=0x55880b4d9ac0, a=0x7ffe595d4d00, ret=0x0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:414 #8 0x7f76188a5f3f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f761a09e4df in KWayland::Server::SeatInterface::dragStarted() (this=0x55880ae39dc0) at /home/roman/dev/kde/build/frameworks/kwayland/src/server/KF5WaylandServer_autogen/EWIEGA46WW/moc_seat_interface.cpp:505 #10 0x7f761a036a39 in KWayland::Server::SeatInterface::Privateoperator()(void) const (__closure=0x55880c4a2f00) at /home/roman/dev/kde/src/frameworks/kwayland/src/server/seat_interface.cpp:341 #11 0x7f761a04150f in QtPrivate::FunctorCall, QtPrivate::List<>, void, KWayland::Server::SeatInterface::Private::registerDataDevice(KWayland::Server::DataDeviceInterface*):: >::call(KWayland::Server::SeatInterface::Private:: &, void **) (f=..., arg=0x7ffe595d4f50) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:146 #12 0x7f761a040ecb in QtPrivate::Functor, 0>::call, void>(KWayland::Server::SeatInterface::Private:: &, void *, void **) (f=..., arg=0x7ffe595d4f50) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:256 #13 0x7f761a03fdd1 in QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=1, this_=0x55880c4a2ef0, r=0x55880ae39dc0, a=0x7ffe595d4f50, ret=0x0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:439 #14 0x7f76188a5f3f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f761a09250b in KWayland::Server::DataDeviceInterface::dragStarted() (this=0x55880c51b720) at /home/roman/dev/kde/build/frameworks/kwayland/src/server/KF5WaylandServer_autogen/EWIEGA46WW/moc_datadevice_interface.cpp:155 #16 0x7f7619fdc49c in KWayland::Server::DataDeviceInterface::Private::startDrag(KWayland::Server::DataSourceInterface*, KWayland::Server::SurfaceInterface*, KWayland::Server::SurfaceInterface*, unsigned int) (this=0x55880be9f970, dataSource=0x55880c4d1e10, origin=0x55880be31600, i=0x55880c371e20, serial=24931) at /home/roman/dev/kde/src/frameworks/kwayland/src/server/datadevice_interface.cpp:127 #17 0x7f7619fdc2eb in KWayland::Server::DataDeviceInterface::Private::startDragCallback(wl_client*, wl_resource*, wl_resource*, wl_resource*, wl_resource*, unsigned int) (client=0x55880bfb2820, resource=0x55880c558e50, source=0x55880c52b390, origin=0x55880c0110f0, icon=0x55880af9ec70, serial=24931) at /home/roman/dev/kde/src/frameworks/kwayland/src/server/datadevice_interface.cpp:99 #18 0x7f760a466dae in ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #19 0x7f760a46671f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #20 0x7f761089de74 in wl_closure_invoke (closure=closure@entry=
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #128 from davidblunkett --- Its back - this went away for a few months but its back and its so annoying - akonadi restarts 5 times today - akonadi just hangs. anyone got a simple way to restart the imap part I can us in a script? it would be so helpful. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405366] New: Flatten image with alpha inheritance in python results in a blank image.
https://bugs.kde.org/show_bug.cgi?id=405366 Bug ID: 405366 Summary: Flatten image with alpha inheritance in python results in a blank image. Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Scripting Assignee: krita-bugs-n...@kde.org Reporter: griffinval...@gmail.com Target Milestone: --- SUMMARY While alpha inheritance merging using layer->flatten image now works, it doesn't work with document.flatten(). STEPS TO REPRODUCE Run this python script, open a file with alpha ineheritance in its layer stack: -- from krita import * from PyQt5.QtWidgets import QFileDialog # Open a file, flatten it, add a view to the krita instance. filename = QFileDialog.getOpenFileName(caption="Open File", filter="Krita files (*.kra)")[0] doc = Application.openDocument(filename) doc.waitForDone() # Now we'll add a new view. Application.activeWindow().addView(doc) # Now we'll flatten doc.flatten() doc.waitForDone() -- OBSERVED RESULT Everything is blank EXPECTED RESULT Image, but flattened to a single layer. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 405180] Latex doesn't work
https://bugs.kde.org/show_bug.cgi?id=405180 Alexander Semke changed: What|Removed |Added Resolution|WORKSFORME |FIXED --- Comment #13 from Alexander Semke --- (In reply to rogier.delporte from comment #12) > Maybe add these packages to the recommended/suggested packages? Thanks. I just added the information about the required packages to our INSTALL file: https://cgit.kde.org/labplot.git/commit/?id=893cd8d84404948a6be94ee2fdccd157805f0ff4 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405365] New: PPC64, function _get_maxmin_fp_NaN() doesn't handle QNaN, SNaN case correctly
https://bugs.kde.org/show_bug.cgi?id=405365 Bug ID: 405365 Summary: PPC64, function _get_maxmin_fp_NaN() doesn't handle QNaN, SNaN case correctly Product: valgrind Version: 3.15 SVN Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: c...@us.ibm.com Target Milestone: --- The _get_maxmin_fp_NaN() function is used in instructions xvmaxsp, xvminsp, xvmindp, xvmaxdp. The case where srcA is QNaN and src is SNaN returns SNaN. However, in this case the HW sets the result to QNaN. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405364] New: Krita puts files which are opened but not added to the view into the recent documents list.
https://bugs.kde.org/show_bug.cgi?id=405364 Bug ID: 405364 Summary: Krita puts files which are opened but not added to the view into the recent documents list. Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: griffinval...@gmail.com Target Milestone: --- SUMMARY When opening a file from python but not adding a view, Krita still adds it to the recent documents list. A week ago this behaviour was not present. git 52ee93a This behaviour is rather annoying when batch processing files like the comics project management tools do... -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 405187] Solver for Freecell is very slow
https://bugs.kde.org/show_bug.cgi?id=405187 --- Comment #14 from Shlomi Fish --- (In reply to Clifford Snow from comment #13) > I don't know if this will help, but some games in work just fine. For me, > the following games work without problem, spider, grandfather's clock, and > yukon. None of these use libfreecell-solver (see https://fc-solve.shlomifish.org/ ). > > These two cause slow downs and may need force quitting - Freecell and > klondike. Please try using freecell after building with my patch to kpat. klondike does not use fc-solve either. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405363] New: PPC64, xvcvdpsxws, xvcvdpuxws, do not handle NaN arguments correctly.
https://bugs.kde.org/show_bug.cgi?id=405363 Bug ID: 405363 Summary: PPC64, xvcvdpsxws, xvcvdpuxws, do not handle NaN arguments correctly. Product: valgrind Version: 3.15 SVN Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: c...@us.ibm.com Target Milestone: --- PPC64, the current implementation for the xvcvdpsxws, xvcvdpuxws instructions do not check and handle the NaN, overflow, underflow cases correctly. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 405281] Falkon cannot move tabs between its separated windows
https://bugs.kde.org/show_bug.cgi?id=405281 --- Comment #4 from Andras --- Created attachment 118724 --> https://bugs.kde.org/attachment.cgi?id=118724&action=edit attempt LD_DEBUG for falkon with tab transferring issue (In reply to comment #3) SDDM with X11. It's KDE neon so I just did run away from gdm3 quikcly, I don't really want to deal with usable gnome environment setup becasue KDE neon sources are very edgy. Sorry I didn't recorded the very same issue there however I assure you it is also happening on gdm3 in the very same way. Sorry for the long video but I tried to point out that the browser is acepting tabs only after you touched the right or left edge of the tab line while you hold given tab with your mouse. Also I tried to create a backtrace, I don't know if any of this info would be helpful enough so I understand if more info should be provided. Le me know whenever you guys have time for this to proceed, I mean no rush. I also thought it can be caused by something else for example some windows management misbehaving however I already tried to turn off compositor and the issue presists without desktop effects too. https://drive.google.com/open?id=19tiLld_ubeq8ReaAI5XcvQXv39bSZH64 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405347] selecting by aspect ratio: abs function in sqlite lowercase, in mariadb uppercase
https://bugs.kde.org/show_bug.cgi?id=405347 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||6.1.0 Latest Commit||https://commits.kde.org/dig ||ikam/b3a3598a28c0e744920bf8 ||31296109af3338d3c8 Resolution|--- |FIXED --- Comment #2 from Maik Qualmann --- Git commit b3a3598a28c0e744920bf831296109af3338d3c8 by Maik Qualmann. Committed on 11/03/2019 at 19:04. Pushed by mqualmann into branch 'master'. fix unknown data type REAL for MySQL in the CAST function testet with SQLite and MariaDB-10.2.22 FIXED-IN: 6.1.0 M +2-1NEWS M +6-6core/libs/database/item/query/itemquerybuilder.cpp https://commits.kde.org/digikam/b3a3598a28c0e744920bf831296109af3338d3c8 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405362] New: PPC64, vmsummbm instruction doesn't handle overflow case correctly
https://bugs.kde.org/show_bug.cgi?id=405362 Bug ID: 405362 Summary: PPC64, vmsummbm instruction doesn't handle overflow case correctly Product: valgrind Version: 3.15 SVN Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: c...@us.ibm.com Target Milestone: --- The vmsummbm instruction needs to chop the results to 32-bits. Currently implementation is not doing this correctly. The result is errors in the adjacent 32-bit fields. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405358] Kwin crashed when login back from suspend
https://bugs.kde.org/show_bug.cgi?id=405358 Vlad Zagorodniy changed: What|Removed |Added Resolution|--- |BACKTRACE Status|REPORTED|NEEDSINFO --- Comment #1 from Vlad Zagorodniy --- Unfortunately the backtrace lacks debug symbols. Could you please install kwin debug packages and submit a new backtrace? -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 405361] Can't log in with drkonqi to report a crash
https://bugs.kde.org/show_bug.cgi?id=405361 Remi Rampin changed: What|Removed |Added CC||remiram...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 405361] New: Can't log in with drkonqi to report a crash
https://bugs.kde.org/show_bug.cgi?id=405361 Bug ID: 405361 Summary: Can't log in with drkonqi to report a crash Product: drkonqi Version: 5.12.7 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: remiram...@gmail.com Target Milestone: --- Created attachment 118723 --> https://bugs.kde.org/attachment.cgi?id=118723&action=edit Screenshot of the wizard page SUMMARY STEPS TO REPRODUCE 1. An app crash, drkonqi pops up to report bug 2. Check that you can provide "what I was doing when the application "Plasma" crashed" 3. Enter KDE BTS username and password OBSERVED RESULT The "next", "finish", and "login" button are all disabled, preventing me from reporting the crash. EXPECTED RESULT I can report a crash with the crash reporting assistant. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 18.04 KDE Plasma Version: 5.12.7 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION Plasma crashed when I clicked "disconnect" next to my WiFi connection, which is what triggered drkonqi in the first place. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 405187] Solver for Freecell is very slow
https://bugs.kde.org/show_bug.cgi?id=405187 --- Comment #13 from Clifford Snow --- I don't know if this will help, but some games in work just fine. For me, the following games work without problem, spider, grandfather's clock, and yukon. These two cause slow downs and may need force quitting - Freecell and klondike. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 375631] UX "Monitor Remote Machine" should always be available in File Menu
https://bugs.kde.org/show_bug.cgi?id=375631 Richard Llom changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #4 from Richard Llom --- Issue is still in v 5.15 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 262333] Extend systemmonitor with a downloadable view of CUDA stress
https://bugs.kde.org/show_bug.cgi?id=262333 Richard Llom changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||richard.l...@gmail.com --- Comment #6 from Richard Llom --- Per comment #5 setting to NEEDSINFO The easiest way would probably be if NVIDIA would provide those informations via sysfs. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 405360] New: When copy/move to FAT32 file system fails because file size limit, an error message mentions the mount point of the destination instead of name of the file that Dolp
https://bugs.kde.org/show_bug.cgi?id=405360 Bug ID: 405360 Summary: When copy/move to FAT32 file system fails because file size limit, an error message mentions the mount point of the destination instead of name of the file that Dolphin can not copy/move Product: frameworks-kio Version: git master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: bugsefor...@gmx.com CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 118722 --> https://bugs.kde.org/attachment.cgi?id=118722&action=edit screenshot I tried to copy a file larger than 4GiB named videos.tar.gz to a pen drive formatted with FAT32 file system. Now, thanks a recent improvement, Dolphin shows an error message about the file size limit before start to copy: "Cannot transfer file:///... because it is too large..." However, as we can see in my screenshot, the "file" mentioned by the error message is the mount point of the destination. STEPS TO REPRODUCE 1. try to copy/move a file larger than 4 GiB to a partition formatted with FAT32 file system OBSERVED RESULT Already explained above. EXPECTED RESULT the error menssage mentions the name of the file larger than 4 GiB SOFTWARE/OS VERSIONS Operating System: KDE neon Developer Edition KDE Plasma Version: 5.15.80 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.0 -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 405354] I can find no way to insert space-plasmoids between elements in Latte-dock
https://bugs.kde.org/show_bug.cgi?id=405354 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 405354] I can find no way to insert space-plasmoids between elements in Latte-dock
https://bugs.kde.org/show_bug.cgi?id=405354 --- Comment #2 from PK --- Thanks... -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 321872] CPU Load Column Sort is backwards
https://bugs.kde.org/show_bug.cgi?id=321872 Richard Llom changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED CC||richard.l...@gmail.com --- Comment #10 from Richard Llom --- The Arrow (sort order indicator) correctly display the sorting in v 5.15. Closing as FIXED -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 384792] Unwanted row height changes
https://bugs.kde.org/show_bug.cgi?id=384792 Richard Llom changed: What|Removed |Added CC||richard.l...@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Richard Llom --- I cannot reproduce this (also using firefox) on v 5.15. Does this still happen to you? -- You are receiving this mail because: You are watching all bug changes.
