[digikam] [Bug 377432] Crash on browsing images
https://bugs.kde.org/show_bug.cgi?id=377432 --- Comment #4 from Simon --- Thank you for all your reporting here and upstream on the exiv2 project! On 10/03/17 07:14, wildcowboy wrote: > https://bugs.kde.org/show_bug.cgi?id=377432 > > --- Comment #3 from wildcowboy --- > (In reply to caulier.gilles from comment #1) > Anyways, you might be correct. I have already had some issues with a metadata > created by my Pentax K-S1 and exiv2 called via API by darktable. > Posted. http://dev.exiv2.org/issues/1283 > Thanks for your help! > -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 373996] Crash when try to delete file from "Save as..." dialog
https://bugs.kde.org/show_bug.cgi?id=373996 --- Comment #5 from Oleg Koncevoy --- I will try to describe it step by step: 1) Create a new file in KDevelop 2) Save it with some name (test.cpp) 3) Press "Save As" and in appeared dialog try to delete this file (test.cpp) Those steps gave me a crash every time. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 370263] Gpx files open but nothing is displayed
https://bugs.kde.org/show_bug.cgi?id=370263 --- Comment #6 from Olivier Carton --- I have tried to zoom a lot and I do not see the track of the GPX file. However, I am not familiar with Marble. I may have missed something to make the track show up. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 370263] Gpx files open but nothing is displayed
https://bugs.kde.org/show_bug.cgi?id=370263 --- Comment #5 from Olivier Carton --- Created attachment 104486 --> https://bugs.kde.org/attachment.cgi?id=104486&action=edit Screenshot of Marble 2.1.0 (NOT) showing the track of the GPX file -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 370263] Gpx files open but nothing is displayed
https://bugs.kde.org/show_bug.cgi?id=370263 --- Comment #4 from Olivier Carton --- Created attachment 104485 --> https://bugs.kde.org/attachment.cgi?id=104485&action=edit Screenshot of Marble 1.9.2 showing GPX file -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 370263] Gpx files open but nothing is displayed
https://bugs.kde.org/show_bug.cgi?id=370263 --- Comment #3 from Olivier Carton --- Created attachment 104484 --> https://bugs.kde.org/attachment.cgi?id=104484&action=edit GPX file GPX file used for trials. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 377445] Dolphin Crashes
https://bugs.kde.org/show_bug.cgi?id=377445 --- Comment #1 from kde@gishpuppy.com --- Although not a programmer, developer, whatever; I noticed when looking at the backtrace output myself in the Crash Handler Window that certain things were in red, only a few of them, I am not familiar with the subject but I thought possibly them being in red was an error indicator. In the "Thread 1 (Thread 0x7f126e0cf7c0 (LWP 29624)): [KCrash Handler]" section the following things were in red. I noticed these red 0x0 in #11, #26, #27, #28, #29, #30, #31, #32, #33, #34, #39, and #40. I don't know if this will be helpful for debugging the problem or not. Hope this comment was helpful -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6
https://bugs.kde.org/show_bug.cgi?id=361236 Martin Gräßlin changed: What|Removed |Added CC||ebelc...@eacbelcher.net --- Comment #102 from Martin Gräßlin --- *** Bug 377440 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377432] Crash on browsing images
https://bugs.kde.org/show_bug.cgi?id=377432 --- Comment #3 from wildcowboy --- (In reply to caulier.gilles from comment #1) > Again a crash in Exiv2. > > Please look a little bit in backtrace. It's clear Exiv2 crash when Pentax > makernote tags parser is used. You can report this crash directly in Exiv2 > bugzilla. It's not a crash in digiKam as well. > > Sound like your PEntax image are not well liked by Exiv2. > > Try to identify the image file and report this problem to Exiv2 bugzilla as > UPSTREAM. > > Gilles Caulier Anyways, you might be correct. I have already had some issues with a metadata created by my Pentax K-S1 and exiv2 called via API by darktable. Posted. http://dev.exiv2.org/issues/1283 Thanks for your help! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377440] KWIN crashes when starting saved VBOX client with two screens.
https://bugs.kde.org/show_bug.cgi?id=377440 Martin Gräßlin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Martin Gräßlin --- As a workaround use the breeze window decoration. *** This bug has been marked as a duplicate of bug 361236 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kservice] [Bug 377446] New: KServiceGroupPrivate::entries return not all menu items
https://bugs.kde.org/show_bug.cgi?id=377446 Bug ID: 377446 Summary: KServiceGroupPrivate::entries return not all menu items Product: frameworks-kservice Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: pushi...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 104483 --> https://bugs.kde.org/attachment.cgi?id=104483&action=edit patch for fix this bug In KServiceGroupPrivate::entries use conversion nameStr = name.toLocal8Bit(). In my system has bug, QTextCodec::codecForLocale()->name() is "US-ASCII" , system locale ru_RU.UTF-8. Russian menu item Games and Office - "Игры" and "Офис" translate to identical strings "" and show only one menu item. In the attachment, the patch fixes this bug. Please help me to find settings location for QTextCodec::codecForLocale(). ps. In pure Qt application QTextCodec::codecForLocale()->name() is "System". -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377432] Crash on browsing images
https://bugs.kde.org/show_bug.cgi?id=377432 --- Comment #2 from wildcowboy --- (In reply to caulier.gilles from comment #1) > Again a crash in Exiv2. > > Please look a little bit in backtrace. It's clear Exiv2 crash when Pentax > makernote tags parser is used. You can report this crash directly in Exiv2 > bugzilla. It's not a crash in digiKam as well. > > Sound like your PEntax image are not well liked by Exiv2. > > Try to identify the image file and report this problem to Exiv2 bugzilla as > UPSTREAM. > > Gilles Caulier I see this: --- #1 0x0032d2b81dda in Exiv2::Internal::PentaxMakerNote::printShutterCount ( os=..., value=..., metadata=) at /b/ext_exiv2/ext_exiv2-prefix/src/ext_exiv2/src/pentaxmn.cpp:1157 --- But how do I determine whether it caused the crash or not? If you did not tell me I would never find out that "Exiv2 crash when Pentax makernote tags parser is used." What I am saying is it's not that clear when you don't have the knowledge. I am learning though... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377434] Crash on deleting items from Trash
https://bugs.kde.org/show_bug.cgi?id=377434 --- Comment #2 from wildcowboy --- (In reply to caulier.gilles from comment #1) > Another crash in Exiv2 shared library when JPEG parser is process the file. > > Please report also this crash as UPSTREAM to Exiv2 bungzilla. > > Note that Exiv2 0.26-svn is used in AppImage bundle. This version is not > yet released. Posted http://dev.exiv2.org/issues/1282 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377422] Main window got stuck in Full Screen mode
https://bugs.kde.org/show_bug.cgi?id=377422 --- Comment #1 from wildcowboy --- Ctrl+M does not work, I do see the toolbar but clicking on Full Screen button does nothing. Ctrl+Shift+F isn't working either. See short video (you won't see mouse pointer so just look at the Full Screen button) https://youtu.be/KFJ9sKPSv2E -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377418] Crash on saving metadata. Latest AppImage 5.5
https://bugs.kde.org/show_bug.cgi?id=377418 --- Comment #2 from wildcowboy --- (In reply to caulier.gilles from comment #1) > It's clear. It crash in Exiv2, XMP parser class, and finaly in Adobe XMP > SDK. Probably something from your image in XMP metadata is not well > interpreted by Exiv2. > > Reprot this problem as UPSTREAM to Exiv2 team with the image file for > investiguation (20161218_172327.jpg) > > Gilles Caulier Posted http://dev.exiv2.org/issues/1281 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 377445] New: Dolphin Crashes
https://bugs.kde.org/show_bug.cgi?id=377445 Bug ID: 377445 Summary: Dolphin Crashes Product: dolphin Version: 4.14.2 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: kde@gishpuppy.com Target Milestone: --- Application: dolphin (4.14.2) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 4.4.0-21-generic x86_64 Distribution: Linux Mint 17.3 Rosa -- Information about the crash: - What I was doing when the application crashed: I had just turned the computer back on after a lock-up of Linux Mint KDE 17.3, as usual the first thing I tried to do was open Dolphin. Dolphin crashed. It now crashes every time I try to open Dolphin. - Unusual behavior I noticed: For a long time now I have noticed that the computer's memory seems to be 'stolen' and used up as I leave the computer on, until eventually when you have too many programs open (relatively small amount, say 7 or 8 actual programs, maybe a couple more running 'in the background') the system locks up. You can't 'un-freeze' it, at least no way that I can find. You have to do a 'dangerous' shutdown holding down the power button. Had a 'lock-up' today and had to do this. When I rebooted, Dolphin crashed as soon as I tried to open it, and ever single time since then. Noticed my Volume Control icon and Update Manager icon were both missing from lower right on the taskbar. Tried to Restart Mint, wouldn't restart. Tried Shut Down and Mint KDE would not shut down. Had to do a hard power-off with the power button. Started up again, same thing happened, had to power-off with power button. While logging on again like the 3rd or 5th time or whatever, saw little 'Leave' icon on log-in screen. Clicked on it, then clicked restart. The system restarted, and I saw that my Update Manager & Volume Control Icons were both back. But Dolphin continues to crash immediately upon clicking on the icon. My guess is there are KDE/Plasma bugs or Mint bugs causing programs not to release all of their memory when you shut them down, leading to the eventual lock-up of the system. Have noticed KDE/Plasma specific problems with bluetooth, volume control, and other things with this install. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Bus error Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd71dcf17c0 (LWP 25744))] Thread 4 (Thread 0x7fd700c06700 (LWP 25752)): #0 0x7fd71484a61a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fd71484a979 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd714808699 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd714808f03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fd7148090ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fd7196207be in QEventDispatcherGlib::processEvents (this=0x7fd6fc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #6 0x7fd7195f20af in QEventLoop::processEvents (this=this@entry=0x7fd700c05de0, flags=...) at kernel/qeventloop.cpp:149 #7 0x7fd7195f23a5 in QEventLoop::exec (this=this@entry=0x7fd700c05de0, flags=...) at kernel/qeventloop.cpp:204 #8 0x7fd7194eec5f in QThread::exec (this=this@entry=0x12c2440) at thread/qthread.cpp:537 #9 0x7fd7195d3823 in QInotifyFileSystemWatcherEngine::run (this=0x12c2440) at io/qfilesystemwatcher_inotify.cpp:265 #10 0x7fd7194f132f in QThreadPrivate::start (arg=0x12c2440) at thread/qthread_unix.cpp:349 #11 0x7fd714ce8184 in start_thread (arg=0x7fd700c06700) at pthread_create.c:312 #12 0x7fd71d5bf37d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7fd6fbfff700 (LWP 25753)): #0 0x7fd714cea558 in __GI___pthread_mutex_lock (mutex=0x7fd6f4000a60) at ../nptl/pthread_mutex_lock.c:125 #1 0x7fd71484a981 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd714808699 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd714808f03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fd7148090ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fd7196207be in QEventDispatcherGlib::processEvents (this=0x7fd6f40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #6 0x7fd7195f20af in QEventLoop::processEvents (this=this@entry=0x7fd6fbffee20, flags=...) at kernel/qeventloop.cpp:149 #7 0x7fd7195f23a5 in QEventLoop::exec (this=this@entry=0x7fd6fbffee20, flags=...) at kernel/qeventloop.cpp:204 #8 0x7fd7194eec5f in QThread::exec (this=) at thread/qthread.cpp:537 #9 0x7fd
[digikam] [Bug 375651] Update 5.4.0 on Windows : no sound with all my videos
https://bugs.kde.org/show_bug.cgi?id=375651 --- Comment #27 from caulier.gil...@gmail.com --- The video sound playback under Linux is now fixed with AppImage. Look this report for details : https://bugs.kde.org/show_bug.cgi?id=376952 The same fix have been applied to Windows installer. I need a feedback please to validate this solution under Windows. The 5.5.0 Windows installer 32 and 64 bits is now up to date in usual GDrive repository : https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Thanks in advance for your feedback Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376952] AppImage Video playback issues - no sound
https://bugs.kde.org/show_bug.cgi?id=376952 caulier.gil...@gmail.com changed: What|Removed |Added Version|5.5.0 |5.4.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376952] AppImage Video playback issues - no sound
https://bugs.kde.org/show_bug.cgi?id=376952 caulier.gil...@gmail.com changed: What|Removed |Added Status|CONFIRMED |RESOLVED Version Fixed In||5.5.0 Resolution|--- |FIXED --- Comment #28 from caulier.gil...@gmail.com --- Great. Thanks for the feedback. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376951] Unexpected crash on rescan - Latest 5.5. AppImage
https://bugs.kde.org/show_bug.cgi?id=376951 --- Comment #6 from wildcowboy --- Posted http://dev.exiv2.org/issues/1280 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376952] AppImage Video playback issues - no sound
https://bugs.kde.org/show_bug.cgi?id=376952 --- Comment #27 from wildcowboy --- (In reply to caulier.gilles from comment #26) > wildcowboy, > > The new AppImage 64 bits is now available for testing : > > https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM > > Gilles Caulier AppImage's now working and the video preview's with the sound on! Woo-Hoo! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 377392] Select Folder on Going up (Feature Request)
https://bugs.kde.org/show_bug.cgi?id=377392 --- Comment #2 from Tsu Jan --- Added a patch here: https://git.reviewboard.kde.org/r/130002/diff/1/ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377444] C++ runtime error
https://bugs.kde.org/show_bug.cgi?id=377444 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- A C++ exception is generated at runtime. What's about to use pre-version 5.5.0 of digiKam installer available here : https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 377391] "under read" error
https://bugs.kde.org/show_bug.cgi?id=377391 Leslie Zhai changed: What|Removed |Added CC||xiangzha...@gmail.com --- Comment #2 from Leslie Zhai --- Hi uc, I am maintaining k3b for KF5 right now https://github.com/KDE/k3b it will be released as KDE Applications 17.04.0 soon! but v2.0.3 was not be maintained any more! Regards, Leslie Zhai -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 377385] Some icons are missing on Gnome
https://bugs.kde.org/show_bug.cgi?id=377385 Leslie Zhai changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/k3b ||/940dcdbdf32bfc7c338ba12fcd ||12ef0104c1938f --- Comment #3 from Leslie Zhai --- Git commit 940dcdbdf32bfc7c338ba12fcd12ef0104c1938f by Leslie Zhai. Committed on 10/03/2017 at 04:12. Pushed by lesliezhai into branch 'master'. Fix some icons are missing on GNOME issue M +10 -2src/option/k3boptiondialog.cpp https://commits.kde.org/k3b/940dcdbdf32bfc7c338ba12fcd12ef0104c1938f -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 377385] Some icons are missing on Gnome
https://bugs.kde.org/show_bug.cgi?id=377385 Leslie Zhai changed: What|Removed |Added CC||xiangzha...@gmail.com --- Comment #2 from Leslie Zhai --- (In reply to Dr. Chapatin from comment #0) > Created attachment 104458 [details] > screenshot > > I'm running k3b-git on Arch from AUR, I use the default Gnome icon theme > (Adwaita). Hi Dr.Chapatin, There is *NO* icon to express "Copy Medium", but KDE icon theme (breeze) has one: tools-media-optical-copy, so please ask GNOME icon theme designers to draw one ;-) Regards, Leslie Zhai -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377444] New: C++ runtime error
https://bugs.kde.org/show_bug.cgi?id=377444 Bug ID: 377444 Summary: C++ runtime error Product: digikam Version: 5.4.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: showfoto Assignee: digikam-de...@kde.org Reporter: huhug...@gmail.com Target Milestone: --- Created attachment 104482 --> https://bugs.kde.org/attachment.cgi?id=104482&action=edit Screen shot of Showfoto error Application crashed unexpected while running on Windows 10 64-bit machine. See attached. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370320] Cannot open Krita files by double clicking
https://bugs.kde.org/show_bug.cgi?id=370320 f.alavi2...@gmail.com changed: What|Removed |Added CC||f.alavi2...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 377443] New: "Could not find the Cantor Part."
https://bugs.kde.org/show_bug.cgi?id=377443 Bug ID: 377443 Summary: "Could not find the Cantor Part." Product: cantor Version: 16.12 Platform: Slackware Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: fil...@kde.org Reporter: ave...@email.arizona.edu CC: alexanderrie...@gmail.com Target Milestone: --- Starting Cantor, a dialog box pops up saying "Could not find the Cantor Part." I tried configuring a backend, too, but not will load. Here's what Cantor outputs: dir: "/usr/lib64/qt5/plugins/cantor/backends" Error while loading plugin: "." Error while loading plugin: ".." Creating MaximaBackend Creating NullBackend Creating PythonBackend Creating SageBackend Creating ScilabBackend dir: "/usr/bin/cantor/backends" I'm using Cantor 16.12.2. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365038] Copy large file (> 10 GB) => panel becomes unresponsive
https://bugs.kde.org/show_bug.cgi?id=365038
--- Comment #6 from Gregor Mi ---
Thanks for the hint. The suggested solution works for my internal HDD ("...
WriteCache=enabled ...") but an USB stick I tried yielded:
sudo hdparm -i /dev/sdb
/dev/sdb1:
SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 00 00 00 00 20 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
HDIO_GET_IDENTITY failed: Invalid argument
Detailed investigation would be part of another thread.
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 377363] Kirta 3.1.2. crashes upon opening new document
https://bugs.kde.org/show_bug.cgi?id=377363 --- Comment #3 from Karee James --- Created attachment 104481 --> https://bugs.kde.org/attachment.cgi?id=104481&action=edit Kirta Crash log Sure thing. I don't understand what's in the log myself. If it doesn't upload, please let me know and I'll just copy-paste it. Thank you mvowada. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355919] Some app return a large tray icon image with wide transparent border and result in an almost invisible statusitem icon
https://bugs.kde.org/show_bug.cgi?id=355919 Dr. Chapatin changed: What|Removed |Added CC||yy...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377442] Isolate layer not working properly on single layers and layer groups
https://bugs.kde.org/show_bug.cgi?id=377442 Karim changed: What|Removed |Added CC||lanaly...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376417] "Open original directory" opened with Gnome Files instead of Dolphin
https://bugs.kde.org/show_bug.cgi?id=376417 --- Comment #4 from Gregor Mi --- Created attachment 104480 --> https://bugs.kde.org/attachment.cgi?id=104480&action=edit Context menu of symlinked folder in Folder View Plasma 5.9.2 I added a screenshot. The option is gone now (upgraded from openSUSE Leap 42.1 with KDE repos to Tumbleweed with Plasma 5.9.2). It was a useful feature. Seems that it was removed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377442] New: Isolate layer not working properly on single layers and layer groups
https://bugs.kde.org/show_bug.cgi?id=377442 Bug ID: 377442 Summary: Isolate layer not working properly on single layers and layer groups Product: krita Version: 3.1.2 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: lanaly...@gmail.com Target Milestone: --- Hi! Krita 3.1.2 portable + Installed, Win 7 x64: 1- When isolating a layer: then clicking on another layer: result = the new selected layer becmes isolated: expected result: Isolation mode should be turned off. (this mode could be interesting as a separate feature) 2- As a result of 1: When isolating a Group of layers (folder of layers): Only layers of said group are shown, but selecting any layer will isolate that particular layer alone: be it inside the group or outside, and the isolate mode is not turned off.. - expected result of selecitng another layer in group: keeping the isolation mode only for the group of layers - Expected result for selecting any other layer outside the group of layers: turning off isolation mode. This bug happens also to someone else who is contributing to krita translation to french, I forgot his name, we chatted on IRC. Thanks for any help! Karim -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 336838] Isolate layer on group doesn't work correctly
https://bugs.kde.org/show_bug.cgi?id=336838 --- Comment #2 from Karim --- Hi! It is still not working properly for me: Krita 3.1.2 portable (instaler did the same) Win 7 x64: 1- When isolating a layer: then clicking on another layer: result = the new selected layer becmes isolated: expected result: Isolation mode should be turned off. (this mode could be interesting as a separate feature) 2- As a result of 1: When isolating a Group of layers (folder of layers): Only layers of said group are shown, but selecting any layer will isolate that particular layer alone: be it inside the group or outside, and the isolate mode is not turned off.. - expected result of selecitng another layer in group: keeping the isolation mode only for the group of layers - Expected result for selecting any other layer outside the group of layers: turning off isolation mode. This bug happens also to someone else who is contributing to krita translation to french, I forgot his name, we chatted on IRC. Should I create a new ticket or is this sufficient? First time reporting on here, thought that existing topic should be used instead of duplicates? :) Karim -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 336838] Isolate layer on group doesn't work correctly
https://bugs.kde.org/show_bug.cgi?id=336838 Karim changed: What|Removed |Added CC||lanaly...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 175414] Icons don't show that a folder is inaccessible
https://bugs.kde.org/show_bug.cgi?id=175414 --- Comment #9 from Don Nguyen --- Currently the lock emblem gets painted because KFileItem::overlays() returns "object-locked" for folders without read access. If we want to paint this lock for folders without execute access as well, we will have to consider if we want KFileItem to handle this or dolphin. eg Have KFileItem::overlays() return "object-locked" for folders without execute access vs adding logic to dolphin to paint the lock for folders without execute access. -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 350997] Panel does not autohide if a window gets closed
https://bugs.kde.org/show_bug.cgi?id=350997 Peter changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Peter --- In my case this only occured in netbook-mode. So I changed to desktop-mode and this behavior was gone. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377441] When hovering a file it does not unselect
https://bugs.kde.org/show_bug.cgi?id=377441 --- Comment #1 from Nicolas L. --- Created attachment 104479 --> https://bugs.kde.org/attachment.cgi?id=104479&action=edit Snapshot when hovering files -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377441] New: When hovering a file it does not unselect
https://bugs.kde.org/show_bug.cgi?id=377441 Bug ID: 377441 Summary: When hovering a file it does not unselect Product: plasmashell Version: 5.8.6 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: k...@nicolaslecureuil.fr CC: plasma-b...@kde.org Target Milestone: 1.0 Since Plasma 5.8.6 ( when using folderview ) the file is selected and hovering the second does not unselect the first one. Tested with Breeze and oxygen themes -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377440] New: KWIN crashes when starting saved VBOX client with two screens.
https://bugs.kde.org/show_bug.cgi?id=377440 Bug ID: 377440 Summary: KWIN crashes when starting saved VBOX client with two screens. Product: kwin Version: 5.8.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: ebelc...@eacbelcher.net Target Milestone: --- Application: kwin_x11 (5.8.3) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.49-16-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: Starting VBOX saved client from a shortcut on the desktop. VirtualBox Graphical User Interface Version 5.1.14 r112924 (Qt5.6.1) Symptom have only started occuring in the last few weeks after some OpenSUSE updates. Virtual Box version has been installed and stable since the release of this version. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f457c988940 (LWP 2474))] Thread 7 (Thread 0x7f44c0d65700 (LWP 2632)): #0 0x7f457c0fdb03 in select () at /lib64/libc.so.6 #1 0x7f45797d0849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f45797d20c3 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7f45797d2527 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f4579781fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f45795bcf1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f45741ae9c8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f45795c19e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f457c3c6734 in start_thread () at /lib64/libpthread.so.0 #9 0x7f457c104d3d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f4552ffe700 (LWP 2585)): #0 0x7f457c3cb0af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f457875793b in () at /usr/lib64/libQt5Script.so.5 #2 0x7f4578757969 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f457c3c6734 in start_thread () at /lib64/libpthread.so.0 #4 0x7f457c104d3d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f454179e700 (LWP 2584)): #0 0x7f457c3cb0af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4550ed7533 in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f4550ed6d57 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f457c3c6734 in start_thread () at /lib64/libpthread.so.0 #4 0x7f457c104d3d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f4553fff700 (LWP 2554)): #0 0x7f457c0fdb03 in select () at /lib64/libc.so.6 #1 0x7f45797d0849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f45797d20c3 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7f45797d2527 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f4579781fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f45795bcf1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f45741ae9c8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f45795c19e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f457c3c6734 in start_thread () at /lib64/libpthread.so.0 #9 0x7f457c104d3d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f4561864700 (LWP 2514)): #0 0x7f457c0fdb03 in select () at /lib64/libc.so.6 #1 0x7f45797d0849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f45797d20c3 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7f45797d2527 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f4579781fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f45795bcf1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f457338f1d5 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7f45795c19e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f457c3c6734 in start_thread () at /lib64/libpthread.so.0 #9 0x7f457c104d3d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f45630b7700 (LWP 2510)): #0 0x7f457c0fc49d in poll () at /lib64/libc.so.6 #1 0x7f457b2833e2 in () at /usr/lib64/libxcb.so.1 #2 0x7f457b284fcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f4563d67839 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f45795c19e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f457c3c6734 in start_thread () at /lib64/libpthread.so.0 #6 0x000
[valgrind] [Bug 376956] Memcheck crashes on access(NULL, F_OK) done by Free Pascal application
https://bugs.kde.org/show_bug.cgi?id=376956 --- Comment #3 from Daniel Glöckner --- Created attachment 104478 --> https://bugs.kde.org/attachment.cgi?id=104478&action=edit Log of UltraStar Deluxe -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 376956] Memcheck crashes on access(NULL, F_OK) done by Free Pascal application
https://bugs.kde.org/show_bug.cgi?id=376956
--- Comment #2 from Daniel Glöckner ---
Created attachment 104477
--> https://bugs.kde.org/attachment.cgi?id=104477&action=edit
Log of int main(){access(NULL,F_OK);return 0;}
--
You are receiving this mail because:
You are watching all bug changes.
[partitionmanager] [Bug 348740] Add truecrypt-like LUKS+ext4 functionality like Gnome Disk Utility
https://bugs.kde.org/show_bug.cgi?id=348740 --- Comment #3 from Andrius Štikonas --- Note that upcoming Plasma Vault can actually do this too with Tomb backend: http://cukic.co/2017/03/09/vault-for-the-privacy-of-your-data/ Probably better to use it there. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 377439] New: Konquerer crashed opening locally saved web page
https://bugs.kde.org/show_bug.cgi?id=377439 Bug ID: 377439 Summary: Konquerer crashed opening locally saved web page Product: konqueror Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: mnpmo...@gmail.com Target Milestone: --- Application: konqueror (4.14.25) KDE Platform Version: 4.14.25 Qt Version: 4.8.6 Operating System: Linux 4.4.49-16-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed:Opening a local page saved from a google drive page 2 years ago - kwrite highlight in red everything in the file after 1.25 in "@media screen and (min-resolution:1.25dppx),screen and (-o-min-device-pixel-ratio:5/4),screen and (-" (Firefox does open the page) The crash can be reproduced every time. -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0cd6782780 (LWP 21755))] Thread 7 (Thread 0x7f0c62131700 (LWP 21766)): #0 0x7f0cd3d4849d in poll () at /lib64/libc.so.6 #1 0x7f0cd0e55314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f0cd0e5564a in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0 #3 0x7f0c72fae386 in () at /usr/lib64/libgio-2.0.so.0 #4 0x7f0cd0e799a5 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7f0cd5055734 in start_thread () at /lib64/libpthread.so.0 #6 0x7f0cd3d50d3d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f0c62932700 (LWP 21765)): #0 0x7f0cd3d4849d in poll () at /lib64/libc.so.6 #1 0x7f0cd0e55314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f0cd0e5542c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f0cd0e55469 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f0cd0e799a5 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7f0cd5055734 in start_thread () at /lib64/libpthread.so.0 #6 0x7f0cd3d50d3d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f0c637a8700 (LWP 21764)): #0 0x7f0cd505a0af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f0c6ab0a533 in () at /usr/lib64/dri/r600_dri.so #2 0x7f0c6ab09d57 in () at /usr/lib64/dri/r600_dri.so #3 0x7f0cd5055734 in start_thread () at /lib64/libpthread.so.0 #4 0x7f0cd3d50d3d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f0c7ab43700 (LWP 21759)): #0 0x7f0cd505a0af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f0cc21b595d in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f0cc246a806 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4 #3 0x7f0cd5055734 in start_thread () at /lib64/libpthread.so.0 #4 0x7f0cd3d50d3d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f0c7bed4700 (LWP 21757)): #0 0x7ffec3bd3adc in clock_gettime () #1 0x7f0cd3d5d806 in clock_gettime () at /lib64/libc.so.6 #2 0x7f0cd5340057 in () at /usr/lib64/libQtCore.so.4 #3 0x7f0cd541b765 in () at /usr/lib64/libQtCore.so.4 #4 0x7f0cd5419e7c in () at /usr/lib64/libQtCore.so.4 #5 0x7f0cd5419f25 in () at /usr/lib64/libQtCore.so.4 #6 0x7f0cd0e5495d in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f0cd0e55230 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f0cd0e5542c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f0cd5419fce in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #10 0x7f0cd53ebd3f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #11 0x7f0cd53ec035 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #12 0x7f0cd52e949f in QThread::exec() () at /usr/lib64/libQtCore.so.4 #13 0x7f0cd52ebb7f in () at /usr/lib64/libQtCore.so.4 #14 0x7f0cd5055734 in start_thread () at /lib64/libpthread.so.0 #15 0x7f0cd3d50d3d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f0cbd421700 (LWP 21756)): #0 0x7f0cd505a0af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f0cc2442cb6 in WTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f0cc2442ce9 in () at /usr/lib64/libQtWebKit.so.4 #3 0x7f0cd5055734 in start_thread () at /lib64/libpthread.so.0 #4 0x7f0cd3d50d3d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f0cd6782780 (LWP 21755)): [KCrash Handler] #6 0x7f0c5afb26bf in gdk_display_open () at /usr/lib64/libgdk-x11-2.0.so.0 #7 0x7f0c5af835ad in gdk_display_open_default_libgtk_only () at /usr/lib64/libgdk-x11-2.0.so.0 #8 0x7f0c5b34b644 in gtk_init_check () at /usr/lib64/libgtk-x11-2.0.so.0 #9 0x7f0c5b34b669 in gtk_init () at /usr/lib64/libgtk
[frameworks-kdoctools] [Bug 377406] Fails to build on windows with linker error
https://bugs.kde.org/show_bug.cgi?id=377406 --- Comment #4 from brko...@gmail.com --- I can confirm this has been fixed. My craft is continuing its build. Thanks very much! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdoctools] [Bug 377406] Fails to build on windows with linker error
https://bugs.kde.org/show_bug.cgi?id=377406 Luigi Toscano changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kdo ||ctools/d2186e6786b3f717080a ||7b4b2264787a40f8d4a0 Status|UNCONFIRMED |RESOLVED --- Comment #3 from Luigi Toscano --- Git commit d2186e6786b3f717080a7b4b2264787a40f8d4a0 by Luigi Toscano. Committed on 09/03/2017 at 21:11. Pushed by ltoscano into branch 'master'. meinproc5: link to the files, not to the library The code worked with the GCC stack on GNU/Linux, but not with MSVC 19.0 (2015). Reviewed-by: Kevin Funk M +1-1src/CMakeLists.txt https://commits.kde.org/kdoctools/d2186e6786b3f717080a7b4b2264787a40f8d4a0 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 377401] KBibTeX fails to load zotero bibliography
https://bugs.kde.org/show_bug.cgi?id=377401 --- Comment #4 from Tobias Schula --- Created attachment 104476 --> https://bugs.kde.org/attachment.cgi?id=104476&action=edit output after applying the patch from comment 3 It doesn't crash anymore when double clicking the library. And this is the output I get after applying the patch. This seems to be the interesting part: > "Error downloading > https://api.zotero.org/users/2535537/tags?start=45&limit=45 - server replied: > Forbidden" -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 194722] Only sharpen one channel, e.g. the "value" channel of HSV
https://bugs.kde.org/show_bug.cgi?id=194722 Shaza changed: What|Removed |Added CC||shaza.ismai...@gmail.com --- Comment #1 from Shaza --- Currently an option for "Suppress color noise" is added to unsharp masking if the checkbox is selected the filter is applied on luminosity(value) channel only, is that sufficient? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376952] AppImage Video playback issues - no sound
https://bugs.kde.org/show_bug.cgi?id=376952 --- Comment #26 from caulier.gil...@gmail.com --- wildcowboy, The new AppImage 64 bits is now available for testing : https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376952] AppImage Video playback issues - no sound
https://bugs.kde.org/show_bug.cgi?id=376952 --- Comment #25 from caulier.gil...@gmail.com --- Maik, ok i will do it tomorrow morning. recompiling all digiKam will take one hour and it's late. Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376952] AppImage Video playback issues - no sound
https://bugs.kde.org/show_bug.cgi?id=376952 --- Comment #24 from caulier.gil...@gmail.com --- Git commit a1ea8082fdaf9cd4b9d70727ec892c0b7f4b4d2a by Gilles Caulier. Committed on 09/03/2017 at 21:47. Pushed by cgilles into branch 'master'. remove openal.so from linux bundle M +1-0project/bundles/appimage/04-build-appimage.sh https://commits.kde.org/digikam-software-compilation/a1ea8082fdaf9cd4b9d70727ec892c0b7f4b4d2a -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376952] AppImage Video playback issues - no sound
https://bugs.kde.org/show_bug.cgi?id=376952 --- Comment #23 from Maik Qualmann --- Gilles, I have a small try in the current master branch to fix Unity menu problem. Please create a AppImage from current master branch for testing. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376952] AppImage Video playback issues - no sound
https://bugs.kde.org/show_bug.cgi?id=376952 --- Comment #22 from caulier.gil...@gmail.com --- Confirmed. I extracted all bundle content in local, removed openal library, and now digiKAm start properly. sound is also played with video. I regenerate AppImage files now. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376952] AppImage Video playback issues - no sound
https://bugs.kde.org/show_bug.cgi?id=376952 --- Comment #21 from caulier.gil...@gmail.com --- Maik, The problem is reproducible under Mageia 5 (but not Mageia 6) : QtAV 1.11.0(Mar 9 2017, 11:27:18) Multimedia framework base on Qt and FFmpeg. Distributed under the terms of LGPLv2.1 or later. Shanghai University->S3 Graphics->Deepin, Shanghai, ChinaCopyright (C) 2012-2016 Wang Bin (aka. Lucas Wang) wbse...@gmail.com Donate: http://qtav.org/donate.html Source: https://github.com/wang-bin/QtAV Home page: http://qtav.org capi::version: 0.6.0 ALSA lib conf.c:3750:(snd_config_update_r) Cannot access file ././/share/alsa/alsa.conf ALSA lib control.c:954:(snd_ctl_open_noupdate) Invalid CTL hw:0 AL lib: alsa.c:257: control open (0): No such file or directory ALSA lib conf.c:3750:(snd_config_update_r) Cannot access file ././/share/alsa/alsa.conf ALSA lib control.c:954:(snd_ctl_open_noupdate) Invalid CTL hw:1 AL lib: alsa.c:257: control open (1): No such file or directory ALSA lib conf.c:3750:(snd_config_update_r) Cannot access file ././/share/alsa/alsa.conf ALSA lib control.c:954:(snd_ctl_open_noupdate) Invalid CTL hw:0 ALSA lib conf.c:3750:(snd_config_update_r) Cannot access file ././/share/alsa/alsa.conf ALSA lib control.c:954:(snd_ctl_open_noupdate) Invalid CTL hw:1 digikam: src/hostapi/alsa/pa_linux_alsa.c:1453: BuildDeviceList: Assertion `devIdx < numDeviceNames' failed. /tmp/.mount_9CD7mN/AppRun: line 73: 31049 Aborted digikam.wrapper $@ I suspect that libopenal.so must be dropped from the bundle in favor than system based library. Gilles -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376417] "Open original directory" opened with Gnome Files instead of Dolphin
https://bugs.kde.org/show_bug.cgi?id=376417 --- Comment #3 from Eike Hein --- Could you add a screenshot? I don't have that option. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377432] Crash on browsing images
https://bugs.kde.org/show_bug.cgi?id=377432 caulier.gil...@gmail.com changed: What|Removed |Added Component|AlbumsView |Metadata-Engine Resolution|--- |UPSTREAM CC||caulier.gil...@gmail.com Status|UNCONFIRMED |RESOLVED --- Comment #1 from caulier.gil...@gmail.com --- Again a crash in Exiv2. Please look a little bit in backtrace. It's clear Exiv2 crash when Pentax makernote tags parser is used. You can report this crash directly in Exiv2 bugzilla. It's not a crash in digiKam as well. Sound like your PEntax image are not well liked by Exiv2. Try to identify the image file and report this problem to Exiv2 bugzilla as UPSTREAM. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377434] Crash on deleting items from Trash
https://bugs.kde.org/show_bug.cgi?id=377434 caulier.gil...@gmail.com changed: What|Removed |Added Component|Bundle-AppImage |Metadata-Engine Resolution|--- |UPSTREAM CC||caulier.gil...@gmail.com Status|UNCONFIRMED |RESOLVED --- Comment #1 from caulier.gil...@gmail.com --- Another crash in Exiv2 shared library when JPEG parser is process the file. Please report also this crash as UPSTREAM to Exiv2 bungzilla. Note that Exiv2 0.26-svn is used in AppImage bundle. This version is not yet released. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 377438] New: Resize display visualization for scaled display
https://bugs.kde.org/show_bug.cgi?id=377438 Bug ID: 377438 Summary: Resize display visualization for scaled display Product: KScreen Version: 5.9.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: kcm Assignee: se...@kde.org Reporter: bugs-...@lagiewka.pl Target Milestone: --- When Plasma on Wayland implementation comes in with per-display DPI, one thing that could be a great addition to KCM is resizing the presentation according to scaling factors that were applied per each display. Example: http://imgur.com/a/ZT8iS The laptop screen is QHD+ and has 13.3" diagonal. The external displays are 27" and have QHD resolution. In real life the externals are much bigger and laptop screen takes about a quarter of each external display. In the visualization the laptop screen overwhelms the externals. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 377401] KBibTeX fails to load zotero bibliography
https://bugs.kde.org/show_bug.cgi?id=377401 --- Comment #3 from Thomas Fischer --- Created attachment 104475 --> https://bugs.kde.org/attachment.cgi?id=104475&action=edit More debug output before error dialog "KBibTeX failed to retrieve the bibliography from Zotero." -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 377401] KBibTeX fails to load zotero bibliography
https://bugs.kde.org/show_bug.cgi?id=377401 Thomas Fischer changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Thomas Fischer --- You are reporting two related but different problems. About the crash in comment #1: I think I have fixed this problem in commit 914cea6a733f900 (branch 'kbibtex/0.6'). I am not sure about the reason, but the problem is reproducible only with clang, but not gcc (in my test setup). About the error message in your original posting: The message box is shown if certain test, composed of various checks, fails. To trace the problem, please apply the patch I am going to attach on the latest code from branch 'kbibtex/0.6', compile it with full debug settings [1], install it in a temporary directory [1], and then launch KBibTeX from a console. I would like to see the complete output you get on the console when you try to access your Zotero bibliography. [1] https://userbase.kde.org/KBibTeX/Development -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 377437] New: clicking a link does not open the page
https://bugs.kde.org/show_bug.cgi?id=377437 Bug ID: 377437 Summary: clicking a link does not open the page Product: akregator Version: 5.3.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: internal browser Assignee: kdepim-b...@kde.org Reporter: kol...@aon.at Target Milestone: --- On openSuse 42.2 Often a simple left-click on a URL-link in an article (from the page of the full article) does simply nothing. Although I can right-click the link, and selecting "open link in new tab" then opens the link in a new tab. Eg. I read https://electrek.co/2017/03/09/tesla-model-s-screwed-vw-phaeton/ Then I click on the Twitter link to https://twitter.com/FredericLambert This does not work and nothing happens. But as said above, from the context menu I can open the twitter link. When I click another link, e.g. https://electrek.co/guides/tesla/ on the same page, this DOES open a new background tab with the clicked link. Can this be a problem with "cross site" links ? Left mouse click is set to "open in background tab" -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 323673] Marble should focus on .gpx file that is specified on the commandline
https://bugs.kde.org/show_bug.cgi?id=323673 Stefan Bauer changed: What|Removed |Added CC||stefan-a-ba...@gmx.net --- Comment #5 from Stefan Bauer --- Looks like there is a regression with this functionality, it is no longer working in Marble 2.1.0. Shall this bug be reopened or a new one created? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 377436] New: Non-integer scaling values are not properly propagated to force fonts DPI setting
https://bugs.kde.org/show_bug.cgi?id=377436 Bug ID: 377436 Summary: Non-integer scaling values are not properly propagated to force fonts DPI setting Product: KScreen Version: 5.9.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: se...@kde.org Reporter: bugs-...@lagiewka.pl Target Milestone: --- For the entire time that I've been using HiDPI display (not so long, since december) I thought that scaling by factors different than 2 was not working for the whole desktop. Yesterday I discovered that scaling by 1.6-1.9 can be easily achieved, but still does not work out of the box. One just needs to set desired scaling factor in Kscreen kcm and proceed to font settings kcm and use Force fonts DPI to Factor x 96 DPI. Why is it a bug? When scaling by 1.5, the force fonts DPI is automatically set to 144 (1.5 x 96). When scaling by 2, the force fonts DPI is automatically set to 192 (2 x 96). When scaling by anything between 1.6 and 1.9 (I suppose 1.1-1.4 as well), the force fonts DPI setting is not set at all, thus scaling is not complete. The common thing between all of them is the fact, that when 96 is multiplied by this factor we get non integer DPI value (i.e. 163.2), which is probably not accepted by whatever is behind font settings. Tested on X11 session. Reproducible: always. Possible solutions: Take the closest integer to the multiplied value (ceiling or floor) or if not every DPI (even integer) can be accepted (I see that arrow up/down in font settings change the value by 24 which is a quarter of 96 DPI) then the closest possible DPI value should be set. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 370263] Gpx files open but nothing is displayed
https://bugs.kde.org/show_bug.cgi?id=370263 Stefan Bauer changed: What|Removed |Added CC||stefan-a-ba...@gmx.net --- Comment #2 from Stefan Bauer --- Could you please check with a well-known GPX file that there is actually nothing displayed? (I.e. load a GPX file with a known track and zoom close the location of the track.) Tracks are currently drawn with a 1px wide white line which is easily overlooked. I was considering to file a bug about that fact, maybe this one is about the same issue. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 377231] Color of track not modifyable
https://bugs.kde.org/show_bug.cgi?id=377231 Stefan Bauer changed: What|Removed |Added CC||stefan-a-ba...@gmx.net --- Comment #1 from Stefan Bauer --- I can confirm this for Marble 2.1.0 on Arch Linux, x86_64. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 377431] Screen does not lock during compositor animations
https://bugs.kde.org/show_bug.cgi?id=377431 Martin Gräßlin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from Martin Gräßlin --- I'm sorry this is an old conceptional problem of the X11 windowing system. On wayland the problem is fixed. For X11 there is nothing we can do. The situation is for example explained in this blog post by yours truly: https://blog.martin-graesslin.com/blog/2014/05/screenlocker-architecture-in-plasma-next/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376536] virtual desktops on wayland
https://bugs.kde.org/show_bug.cgi?id=376536 Andrew Martens changed: What|Removed |Added CC||a.t.mart...@gmail.com --- Comment #1 from Andrew Martens --- I have the same problem. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377197] Customize grouping behaviour [patch]
https://bugs.kde.org/show_bug.cgi?id=377197 --- Comment #3 from Simon --- Yes, context menu is obviously broken. I tested all kinds of things but for unknown reasons never once did a right click. This code is also heavily duplicated between table and icon view, I am thus refactoring while fixing. On 08/03/17 20:21, Maik Qualmann wrote: > Simon, > > I think we do not need that much. A simple "use first image of grouped or use > all images" for all actions should be enough. Let's see what Gilles says when > he has time. I have also found some errors on the right mouse button context > menu: > > - Assign color label to a group, the dialog asks for each image > - Assign or remove tags no longer works > - Assign rating no longer works > - Assign flags no longer works > > Maik > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377433] Crash on opening settings
https://bugs.kde.org/show_bug.cgi?id=377433 Maik Qualmann changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||metzping...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 375809 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375809] digiKam froze on opening Settings
https://bugs.kde.org/show_bug.cgi?id=375809 --- Comment #24 from Maik Qualmann --- *** Bug 377433 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377435] New: crash of plasma after clicking on the Default widget
https://bugs.kde.org/show_bug.cgi?id=377435 Bug ID: 377435 Summary: crash of plasma after clicking on the Default widget Product: plasmashell Version: 5.9.3 Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: abdelh...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.3) Qt Version: 5.8.0 Frameworks Version: 5.31.0 Operating System: Linux 4.9.13-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: plasma get crashed every time when i click clicking on the Default widget Kernel: x86_64 Linux 4.9.13-1-MANJARO DE: KDE 5.31.0 / Plasma 5.9.3 The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f73c6e79800 (LWP 678))] Thread 18 (Thread 0x7f72b67fc700 (LWP 2582)): #0 0x7f73bfafc10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f73c0c2c58b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f72ff4fe1d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f72ff5029d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f72ff4fd263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f72ff502a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f72ff4fd263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f72ff500249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f73c0c2b6d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7f73bfaf6454 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f73c05407df in clone () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7f72b6ffd700 (LWP 2581)): #0 0x7f73bfafc10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f73c0c2c58b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f72ff4fe1d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f72ff5029d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f72ff4fd263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f72ff502a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f72ff4fd263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f72ff500249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f73c0c2b6d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7f73bfaf6454 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f73c05407df in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7f72b77fe700 (LWP 2580)): #0 0x7f73bfafc10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f73c0c2c58b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f72ff4fe1d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f72ff5029d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f72ff4fd263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f72ff502a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f72ff4fd263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f72ff502a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f72ff4fd263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f72ff502a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f72ff4fd263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f72ff502a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7f72ff4fd263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #13 0x7f72ff502a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #14 0x7f72ff4fd263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #15 0x7f72ff502a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #16 0x7f72ff4fd263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*,
[krita] [Bug 376597] Text created using Multiline text tool disappears when reopening .kra file and cuases Krita to crash
https://bugs.kde.org/show_bug.cgi?id=376597 --- Comment #6 from Lia Min --- Created attachment 104474 --> https://bugs.kde.org/attachment.cgi?id=104474&action=edit .shapelayer files within the defected .kra file I could not locate the .odg file in the layers folder. Instead, here are seven folders named "layer#.shapelayer" which I assume contains information about the vector layers. Among these seven, three were used for multiline texts -I am not sure which though, since the layer number doesn't correspond to that in krita. I know very little computer language, but from what I can figure out by comparing another file that does not have this error, the text that I typed in using the multiline text tool seem to have disappeared from the "contect.xml" just leaving an empty text box in its place. I hope this helps you debug. In the meantime, I will stick to using artistic text for all my text work instead. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377434] New: Crash on deleting items from Trash
https://bugs.kde.org/show_bug.cgi?id=377434 Bug ID: 377434 Summary: Crash on deleting items from Trash Product: digikam Version: 5.4.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Bundle-AppImage Assignee: digikam-de...@kde.org Reporter: aegor...@gmail.com Target Milestone: --- digikam.iojob: DELETING: "/media/data/FamilyPictures/.dtrash/info/20170201_181821_412.dtrashinfo" FILE EXISTS? true IS TO TRASH? false digikam.general: One job is done digikam.general: One job is done digikam.iojob: DELETING: "/media/data/FamilyPictures/.dtrash/info/20170201_181821_412.dtrashinfo" FILE EXISTS? false IS TO TRASH? false digikam.iojob: Thread Finished digikam.general: One job is done [Thread 0x7fff0bff7700 (LWP 6699) exited] [Switching to Thread 0x7fff1700 (LWP 6659)] Thread 123 "Thread (pooled)" hit Catchpoint 1 (exception thrown), 0x7fffee6b78bd in __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (gdb) bt #0 0x7fffee6b78bd in __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #1 0x0032d2b46b15 in Exiv2::JpegBase::readMetadata (this=) at /b/ext_exiv2/ext_exiv2-prefix/src/ext_exiv2/src/jpgimage.cpp:345 #2 0x76813bd6 in Digikam::MetaEngine::load (this=this@entry=0x7fff1fffe850, filePath=...) at /b/dktemp/digikam-master/core/libs/dmetadata/metaengine.cpp:280 #3 0x7685c816 in Digikam::DMetadata::load (this=this@entry=0x7fff1fffe850, filePath=...) at /b/dktemp/digikam-master/core/libs/dmetadata/dmetadata.cpp:96 #4 0x7685c892 in Digikam::DMetadata::DMetadata (this=0x7fff1fffe850, filePath=...) at /b/dktemp/digikam-master/core/libs/dmetadata/dmetadata.cpp:63 #5 0x768a65aa in Digikam::ThumbnailCreator::createThumbnail (this=this@entry=0xc96150, info=..., detailRect=...) at /b/dktemp/digikam-master/core/libs/threadimageio/thumbnailcreator.cpp:468 #6 0x768a9607 in Digikam::ThumbnailCreator::load (this=0xc96150, identifier=..., rect=..., pregenerate=pregenerate@entry=false) at /b/dktemp/digikam-master/core/libs/threadimageio/thumbnailcreator.cpp:264 #7 0x768a9e22 in Digikam::ThumbnailCreator::load (this=, identifier=...) at /b/dktemp/digikam-master/core/libs/threadimageio/thumbnailcreator.cpp:181 #8 0x768b4c8e in Digikam::ThumbnailLoadingTask::execute (this=0x3758dd0) at /b/dktemp/digikam-master/core/libs/threadimageio/thumbnailtask.cpp:166 #9 0x7688d372 in Digikam::LoadSaveThread::run (this=0xc96020) at /b/dktemp/digikam-master/core/libs/threadimageio/loadsavethread.cpp:133 #10 0x768cb88e in Digikam::DynamicThread::DynamicThreadPriv::run (this=0xc96090) at /b/dktemp/digikam-master/core/libs/threads/dynamicthread.cpp:183 #11 0x00306c6ac01d in ?? () from /tmp/.mount_BBXz35/usr/lib/libQt5Core.so.5 #12 0x00306c6aefc9 in ?? () from /tmp/.mount_BBXz35/usr/lib/libQt5Core.so.5 #13 0x75fd56ba in start_thread (arg=0x7fff1700) at pthread_create.c:333 #14 0x7fffede4882d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 (gdb) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377433] New: Crash on opening settings
https://bugs.kde.org/show_bug.cgi?id=377433 Bug ID: 377433 Summary: Crash on opening settings Product: digikam Version: 5.4.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Bundle-AppImage Assignee: digikam-de...@kde.org Reporter: aegor...@gmail.com Target Milestone: --- [New Thread 0x7fff395e4700 (LWP 6121)] [New Thread 0x7fff0b33a700 (LWP 6122)] [New Thread 0x7fff33fff700 (LWP 6123)] [New Thread 0x7fff3a4eb700 (LWP 6124)] digikam.general: Testing "mysql_install_db" ... digikam.general: Testing "mysqld" ... digikam.general: Testing "mysql_install_db" ... digikam.general: Testing "mysqld" ... digikam.general: Testing "././/bin/mysql_install_db" ... digikam.general: All Binaries Found : false digikam.general: Testing "././/bin/mysqld" ... digikam.general: All Binaries Found : false digikam.general: Testing "././/sbin/mysql_install_db" ... digikam.general: All Binaries Found : false digikam.general: Testing "././/sbin/mysqld" ... digikam.general: All Binaries Found : false Thread 1 "digikam" hit Catchpoint 1 (exception thrown), 0x7fffee6b78bd in __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (gdb) bt #0 0x7fffee6b78bd in __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #1 0x0032d2bb6992 in Exiv2::ExifKey::ExifKey (this=, ti=...) at /b/ext_exiv2/ext_exiv2-prefix/src/ext_exiv2/src/tags.cpp:3157 #2 0x76830d40 in Digikam::MetaEngine::getStdExifTagsList ( this=this@entry=0x7fffbac0) at /b/dktemp/digikam-master/core/libs/dmetadata/metaengine_exif.cpp:1087 #3 0x769a9814 in Digikam::MetadataPanel::slotTabChanged ( this=this@entry=0x3041fd0) at /b/dktemp/digikam-master/core/libs/widgets/metadata/metadatapanel.cpp:311 #4 0x769aa19d in Digikam::MetadataPanel::MetadataPanel ( this=0x3041fd0, tab=0x3040460) at /b/dktemp/digikam-master/core/libs/widgets/metadata/metadatapanel.cpp:232 #5 0x7768f07a in Digikam::SetupMetadata::SetupMetadata (this= 0x30052f0, parent=) at /b/dktemp/digikam-master/core/utilities/setup/metadata/setupmetadata.cpp:463 #6 0x776673ca in Digikam::Setup::Setup (this=this@entry=0x2969020, parent=parent@entry=0x2275a60) at /b/dktemp/digikam-master/core/utilities/setup/setup.cpp:186 #7 0x776691a5 in Digikam::Setup::execDialog (parent=0x2275a60, ---Type to continue, or q to quit--- page=Digikam::Setup::LastPageUsed) at /b/dktemp/digikam-master/core/utilities/setup/setup.cpp:362 #8 0x00306c8af146 in QMetaObject::activate(QObject*, int, int, void**) () from /tmp/.mount_4YlzjE/usr/lib/libQt5Core.so.5 #9 0x7fffef93f4e2 in QAction::triggered(bool) () from /tmp/.mount_4YlzjE/usr/lib/libQt5Widgets.so.5 #10 0x7fffef941ebd in QAction::activate(QAction::ActionEvent) () from /tmp/.mount_4YlzjE/usr/lib/libQt5Widgets.so.5 #11 0x7fffefaa8842 in ?? () from /tmp/.mount_4YlzjE/usr/lib/libQt5Widgets.so.5 #12 0x7fffefaad6c4 in ?? () from /tmp/.mount_4YlzjE/usr/lib/libQt5Widgets.so.5 #13 0x7fffefab16b6 in QMenu::mouseReleaseEvent(QMouseEvent*) () from /tmp/.mount_4YlzjE/usr/lib/libQt5Widgets.so.5 #14 0x7fffef98bbf8 in QWidget::event(QEvent*) () from /tmp/.mount_4YlzjE/usr/lib/libQt5Widgets.so.5 #15 0x7fffefab20db in QMenu::event(QEvent*) () from /tmp/.mount_4YlzjE/usr/lib/libQt5Widgets.so.5 #16 0x7fffef94623c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /tmp/.mount_4YlzjE/usr/lib/libQt5Widgets.so.5 #17 0x7fffef94da1b in QApplication::notify(QObject*, QEvent*) () from /tmp/.mount_4YlzjE/usr/lib/libQt5Widgets.so.5 #18 0x00306c887ad0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) ---Type to continue, or q to quit--- () from /tmp/.mount_4YlzjE/usr/lib/libQt5Core.so.5 #19 0x7fffef94c70e in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from /tmp/.mount_4YlzjE/usr/lib/libQt5Widgets.so.5 #20 0x7fffef9a76fb in ?? () from /tmp/.mount_4YlzjE/usr/lib/libQt5Widgets.so.5 #21 0x7fffef9a9613 in ?? () from /tmp/.mount_4YlzjE/usr/lib/libQt5Widgets.so.5 #22 0x7fffef94623c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /tmp/.mount_4YlzjE/usr/lib/libQt5Widgets.so.5 #23 0x7fffef94d148 in QApplication::notify(QObject*, QEvent*) () from /tmp/.mount_4YlzjE/usr/lib/libQt5Widgets.so.5 #24 0x00306c887ad0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /tmp/.mount_4YlzjE/usr/lib/libQt5Core.so.5 #25 0x7fffef36ffdd in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /tmp/.mount_4YlzjE/usr/lib/libQt5Gui.so.5 #26 0x7fffef371cf5 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::W
[krusader] [Bug 328944] Use Shift+Delete for delete or move selected files to trash
https://bugs.kde.org/show_bug.cgi?id=328944 Alex Bikadorov changed: What|Removed |Added Resolution|--- |FIXED CC||alex.bikado...@kdemail.net Status|UNCONFIRMED |RESOLVED --- Comment #2 from Alex Bikadorov --- Patch should be good enough. If not, please reopen. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377432] New: Crash on browsing images
https://bugs.kde.org/show_bug.cgi?id=377432 Bug ID: 377432 Summary: Crash on browsing images Product: digikam Version: 5.4.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: AlbumsView Assignee: digikam-de...@kde.org Reporter: aegor...@gmail.com Target Milestone: --- Thread 1 "digikam" received signal SIGSEGV, Segmentation fault. Exiv2::ExifData::findKey (this=, key=...) at /b/ext_exiv2/ext_exiv2-prefix/src/ext_exiv2/src/exif.cpp:583 583 /b/ext_exiv2/ext_exiv2-prefix/src/ext_exiv2/src/exif.cpp: No such file or directory. (gdb) bt #0 Exiv2::ExifData::findKey (this=, key=...) at /b/ext_exiv2/ext_exiv2-prefix/src/ext_exiv2/src/exif.cpp:583 #1 0x0032d2b81dda in Exiv2::Internal::PentaxMakerNote::printShutterCount ( os=..., value=..., metadata=) at /b/ext_exiv2/ext_exiv2-prefix/src/ext_exiv2/src/pentaxmn.cpp:1157 #2 0x7682ad4d in Exiv2::operator<< (md=..., os=...) at ././/include/exiv2/metadatum.hpp:305 #3 Digikam::MetaEngine::getExifTagsDataList (this=this@entry=0x7fffc7a0, exifKeysFilter=..., invertSelection=invertSelection@entry=false) at /b/dktemp/digikam-master/core/libs/dmetadata/metaengine_exif.cpp:194 #4 0x769abb65 in Digikam::ExifWidget::decodeMetadata (this=0xd03680) at /b/dktemp/digikam-master/core/libs/widgets/metadata/exifwidget.cpp:114 #5 0x769a4f35 in Digikam::MetadataWidget::setMetadata (this=0xd03680, data=...) at /b/dktemp/digikam-master/core/libs/widgets/metadata/metadatawidget.cpp:254 #6 0x76a02e43 in Digikam::ImagePropertiesMetaDataTab::setCurrentURL ( this=this@entry=0xd01860, url=...) at /b/dktemp/digikam-master/core/libs/imageproperties/imagepropertiesmetadatatab.cpp:192 #7 0x77644083 in Digikam::ImagePropertiesSideBarDB::slotChangedTab ( this=0xcc6760, tab=0xd01860) ---Type to continue, or q to quit--- db.cpp:288 #8 0x76a0dd10 in Digikam::ImagePropertiesSideBar::qt_static_metacall (_o=, _c=, _id=, _a=) at /b/dktemp/digikam-master/build/core/libs/imageproperties/moc_imagepropertiessidebar.cpp:97 #9 0x00306c8af146 in QMetaObject::activate(QObject*, int, int, void**) () from /tmp/.mount_6Lif4P/usr/lib/libQt5Core.so.5 #10 0x769d274f in Digikam::Sidebar::signalChangedTab (this=, _t1=0xd01860) at /b/dktemp/digikam-master/build/core/libs/widgets/moc_sidebar.cpp:536 #11 0x769d754b in Digikam::Sidebar::qt_static_metacall (_o=, _c=, _id=, _a=) at /b/dktemp/digikam-master/build/core/libs/widgets/moc_sidebar.cpp:458 #12 0x00306c8af146 in QMetaObject::activate(QObject*, int, int, void**) () from /tmp/.mount_6Lif4P/usr/lib/libQt5Core.so.5 #13 0x769d270e in Digikam::DMultiTabBarButton::clicked (this=, _t1=1) at /b/dktemp/digikam-master/build/core/libs/widgets/moc_sidebar.cpp:208 #14 0x00306c8af146 in QMetaObject::activate(QObject*, int, int, void**) () from /tmp/.mount_6Lif4P/usr/lib/libQt5Core.so.5 #15 0x7fffefa296c2 in QAbstractButton::clicked(bool) () from /tmp/.mount_6Lif4P/usr/lib/libQt5Widgets.so.5 #16 0x7fffefa298b5 in ?? () from /tmp/.mount_6Lif4P/usr/lib/libQt5Widgets.so.5 #17 0x7fffefa2ae84 in ?? () from /tmp/.mount_6Lif4P/usr/lib/libQt5Widgets.so.5 #18 0x7fffefa2b024 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /tmp/.mount_6Lif4P/usr/lib/libQt5Widgets.so.5 #19 0x7fffef98bbf8 in QWidget::event(QEvent*) () from /tmp/.mount_6Lif4P/usr/lib/libQt5Widgets.so.5 #20 0x7fffef94623c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /tmp/.mount_6Lif4P/usr/lib/libQt5Widgets.so.5 #21 0x7fffef94da1b in QApplication::notify(QObject*, QEvent*) () from /tmp/.mount_6Lif4P/usr/lib/libQt5Widgets.so.5 #22 0x00306c887ad0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /tmp/.mount_6Lif4P/usr/lib/libQt5Core.so.5 #23 0x7fffef94c70e in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from /tmp/.mount_6Lif4P/usr/lib/libQt5Widgets.so.5 #24 0x7fffef9a7156 in ?? () from /tmp/.mount_6Lif4P/usr/lib/libQt5Widgets.so.5 #25 0x7fffef9a9613 in ?? () from /tmp/.mount_6Lif4P/usr/lib/libQt5Widgets.so.5 #26 0x7fffef94623c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /tmp/.mount_6Lif4P/usr/lib/libQt5Widgets.so.5 #27 0x7fffef94d148 in QApplication::notify(QObject*, QEvent*) () from /tmp/.mount_6Lif4P/usr/lib/libQt5Widgets.so.5 #28 0x00306c887ad0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /tmp/.mount_6Lif4P/usr/lib/libQt5Core.so.5 #29 0x7fffef36ffdd in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /tmp/.mount_6Lif4P/usr/lib/libQt5Gui.so.5 #30 0x7fffef371cf5 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::Windo
[plasma4] [Bug 350997] Panel does not autohide if a window gets closed
https://bugs.kde.org/show_bug.cgi?id=350997 Andrew Martens changed: What|Removed |Added CC||a.t.mart...@gmail.com --- Comment #1 from Andrew Martens --- I don't know if this is the same problem, but whenever I open or close a program the panel gets un-hidden, as might be expected since a change occurs. However, I then have to mouse over the panel to make it hide again. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 377431] Screen does not lock during compositor animations
https://bugs.kde.org/show_bug.cgi?id=377431 Tobias Guggenmos changed: What|Removed |Added Severity|normal |major -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 377431] New: Screen does not lock during compositor animations
https://bugs.kde.org/show_bug.cgi?id=377431 Bug ID: 377431 Summary: Screen does not lock during compositor animations Product: kscreenlocker Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: slartibartfas...@gmail.com CC: bhus...@gmail.com, mgraess...@kde.org Target Milestone: --- Created attachment 104473 --> https://bugs.kde.org/attachment.cgi?id=104473&action=edit Screenshot When using some compositor animations such as the workspaces and windows overviews (see screenshot) the screen does not lock. Reproduce: 1) Enter some of those animated full screen window switchers (screenshot), for example by using one of the hot corners (move the mouse pointer to one of the upper screen corners (assuming a vanilla configuration)). The compositor has to be enabled for this. 2) Try to lock the screen (close the laptop lid, trigger the appropriate key combination, etc.) Expected: screen does lock Result: it doesn't Possible dangers of this bug: User closes laptop lid, expects the screen to be locked, goes away. -> Stranger/attacker has access to user account System used: fedora 25, plasma 5.8.6 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 377122] kwallet cannot ask for GPG password on wayland
https://bugs.kde.org/show_bug.cgi?id=377122 Guo Yunhe (郭云鹤) changed: What|Removed |Added CC||guoyunhebr...@gmail.com --- Comment #1 from Guo Yunhe (郭云鹤) --- Same issue here. When enter desktop, kwalletd keeps popping up a warning saying cannot open wallet with GPG. openSUSE Tumbleweed 20170308 64bit Plasma 5.9.2 Frameworks 5.31.0 Qt 5.7.1 Wayland Kernel 4.10.1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376952] AppImage Video playback issues - no sound
https://bugs.kde.org/show_bug.cgi?id=376952 --- Comment #20 from wildcowboy --- (In reply to Maik Qualmann from comment #19) > AppImage works here under openSUSE with sound. OpenAl is found as audio > backend. Wildcowboy please look where in your system is the alsa.conf file > is located (/usr/share/alsa/alsa.conf). > > Maik /usr/share/alsa -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 377430] Checksums SHA512
https://bugs.kde.org/show_bug.cgi?id=377430 Elvis Angelaccio changed: What|Removed |Added CC||elvis.angelac...@kde.org, ||kdelibs-b...@kde.org Product|dolphin |frameworks-kio Component|panels: information |general Assignee|dolphin-bugs-n...@kde.org |fa...@kde.org Version|unspecified |5.31.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 377430] New: Checksums SHA512
https://bugs.kde.org/show_bug.cgi?id=377430 Bug ID: 377430 Summary: Checksums SHA512 Product: dolphin Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: panels: information Assignee: dolphin-bugs-n...@kde.org Reporter: den...@gesker.com Target Milestone: --- Please add SHA512 to the Checksums tab of the File Properties window BTW, thanks for Dolphin. It's awesome. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 377430] Checksums SHA512
https://bugs.kde.org/show_bug.cgi?id=377430 Dennis Gesker changed: What|Removed |Added CC||den...@gesker.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376155] "Quick tile window to the left/right" de-maximizes the window without tiling as a first action since plasma 5.9.0
https://bugs.kde.org/show_bug.cgi?id=376155 mowalle@gmail.com changed: What|Removed |Added CC||mowalle@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377429] New: Plasman crashes when I pressed win button on keyboard
https://bugs.kde.org/show_bug.cgi?id=377429 Bug ID: 377429 Summary: Plasman crashes when I pressed win button on keyboard Product: plasmashell Version: 5.9.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: greengogo...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.3) Qt Version: 5.8.0 Frameworks Version: 5.31.0 Operating System: Linux 4.9.13-1-lts x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I installed plasma. Booted it using sddm and pressd win button. The mistake no longer showed up. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe3ead34800 (LWP 695))] Thread 6 (Thread 0x7fe335b9f700 (LWP 819)): #0 0x7fe3df234e64 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7fe3df1eec80 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7fe3df1ef6cb in () at /usr/lib/libglib-2.0.so.0 #3 0x7fe3df1ef8bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7fe3e4cf506b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fe3e4c9e89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fe3e4ac0a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7fe3e87adfd6 in () at /usr/lib/libQt5Quick.so.5 #8 0x7fe3e4ac56d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7fe3e3990454 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fe3e43da7df in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fe3b6d3a700 (LWP 818)): #0 0x7fe3e399610f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe3ea4a2234 in () at /usr/lib/libQt5Script.so.5 #2 0x7fe3ea4a2279 in () at /usr/lib/libQt5Script.so.5 #3 0x7fe3e3990454 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fe3e43da7df in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fe3c15f5700 (LWP 817)): #0 0x7fe3df234e64 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7fe3df1ef79a in () at /usr/lib/libglib-2.0.so.0 #2 0x7fe3df1ef8bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fe3e4cf506b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fe3e4c9e89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fe3e4ac0a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fe3e7bfa025 in () at /usr/lib/libQt5Qml.so.5 #7 0x7fe3e4ac56d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7fe3e3990454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fe3e43da7df in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fe3d0822700 (LWP 816)): #0 0x7fe3df1ec79e in () at /usr/lib/libglib-2.0.so.0 #1 0x7fe3df1eec2b in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7fe3df1ef6cb in () at /usr/lib/libglib-2.0.so.0 #3 0x7fe3df1ef8bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7fe3e4cf506b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fe3e4c9e89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fe3e4ac0a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7fe3e7bfa025 in () at /usr/lib/libQt5Qml.so.5 #8 0x7fe3e4ac56d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7fe3e3990454 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fe3e43da7df in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7fe3d226a700 (LWP 775)): #0 0x7fe3e43d148d in poll () at /usr/lib/libc.so.6 #1 0x7fe3df1ef7a6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fe3df1ef8bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fe3e4cf506b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fe3e4c9e89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fe3e4ac0a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fe3e510a125 in () at /usr/lib/libQt5DBus.so.5 #7 0x7fe3e4ac56d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7fe3e3990454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fe3e43da7df in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7fe3ead34800 (LWP 695)): [KCrash Handler] #6 0x7fe3e8858d16 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /usr/lib/libQt5Quick.so.5 #7 0x7fe3e8858dea in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /usr/lib/libQt5Quick.so.5 #8 0x7fe3e8858dea in QQuickItemPrivate::setEffec
[dolphin] [Bug 377411] Created Items Are Not Selected In Parent Folder
https://bugs.kde.org/show_bug.cgi?id=377411 --- Comment #4 from Tsu Jan --- Added the patch at https://git.reviewboard.kde.org/r/130001/ -- You are receiving this mail because: You are watching all bug changes.
[kde-windows] [Bug 234732] okular cannot open djvu files
https://bugs.kde.org/show_bug.cgi?id=234732 swds...@gmail.com changed: What|Removed |Added CC||swds...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 372411] MTP flickers with android
https://bugs.kde.org/show_bug.cgi?id=372411 --- Comment #1 from Olivier Churlaud --- Some debug showed that the problem is due to energy: if I connect the phone to the computer through a powered hub, it works correctly. (However it works fine even without the hub on Ubuntu with gnome) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375651] Update 5.4.0 on Windows : no sound with all my videos
https://bugs.kde.org/show_bug.cgi?id=375651 --- Comment #26 from caulier.gil...@gmail.com --- I try to fix the problem using current QtAv implementation in digiKam Windows installer. I just recompiled quickly the 32 bits bundle for testing. Please test and give me a feedback. File is at usual place : https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 377428] New: Indicate if Num Lock is active.
https://bugs.kde.org/show_bug.cgi?id=377428 Bug ID: 377428 Summary: Indicate if Num Lock is active. Product: kscreenlocker Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: breeze-theme Assignee: plasma-b...@kde.org Reporter: olaf.the.lost.vik...@gmail.com CC: bhus...@gmail.com, mgraess...@kde.org Target Milestone: --- (my current version is 5.9.3, which isn't selectable above) My TKL keyboard as well as my notebook keyboard map certain "normal" keys to number keys if Num Lock is active. Indicating this on the lockscreen just like with Caps Lock could be helpful. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 377311] a panel crash
https://bugs.kde.org/show_bug.cgi?id=377311 Marco Martin changed: What|Removed |Added Version|5.7.4 |5.26.0 Product|plasmashell |frameworks-baloo Component|general |general Assignee|k...@davidedmundson.co.uk|pinak.ah...@gmail.com CC||notm...@gmail.com Target Milestone|1.0 |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377301] Plasma crushing
https://bugs.kde.org/show_bug.cgi?id=377301 Marco Martin changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |BACKTRACE CC||notm...@gmail.com --- Comment #1 from Marco Martin --- can you install debug packages for plasma-workspace and plasma-framework? the backtrace doesn't say that much at the moment -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377298] plasma5 crash after detaching secondary screen
https://bugs.kde.org/show_bug.cgi?id=377298 --- Comment #3 from Marco Martin --- possible solution: https://phabricator.kde.org/D4991 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377210] Drag files from Dolphin to another programs causes plasma crash under Wayland
https://bugs.kde.org/show_bug.cgi?id=377210 --- Comment #2 from Dr. Chapatin --- I dont know enable debug symbols on Arch. Sorry. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376952] AppImage Video playback issues - no sound
https://bugs.kde.org/show_bug.cgi?id=376952 --- Comment #19 from Maik Qualmann --- AppImage works here under openSUSE with sound. OpenAl is found as audio backend. Wildcowboy please look where in your system is the alsa.conf file is located (/usr/share/alsa/alsa.conf). Maik -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 377421] Ark claims to delete file from APK while it didn't
https://bugs.kde.org/show_bug.cgi?id=377421 --- Comment #1 from Ragnar Thomsen --- I can't reproduce with a random apk archive from the internet. Tried with both cli7z and clizip plugins. Can you set: QT_LOGGING_RULES=ark.*.debug=true and then reproduce the problem and attach console output? Does it happen with all apk archives? If not, can you provide a link to the affected archive or upload it (if small)? What is your version of Ark? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 377427] New: PPC64, lxv instruction failing on odd destination register
https://bugs.kde.org/show_bug.cgi?id=377427 Bug ID: 377427 Summary: PPC64, lxv instruction failing on odd destination register Product: valgrind Version: 3.10 SVN Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: c...@us.ibm.com Target Milestone: --- The lxv instruction is failing on a Valgrind test of the register number being odd. This Valgrind test only applies to load/store functions that work on a register pair. This is not the case for the lxv instruction. -- You are receiving this mail because: You are watching all bug changes.
