[dragonplayer] [Bug 481110] Unsupport hardware acceleration
https://bugs.kde.org/show_bug.cgi?id=481110 --- Comment #9 from Levi Marvin --- (In reply to Harald Sitter from comment #7) > Nothing obvious sticks out to me. Whatever the problem is likely is in > libvlc though, on x11 we simply tell libvlc to render onto a window, the > decoding choice is entirely up to libvlc. > > Does this work with vlc? Yes, It works with VLC. -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 481110] Unsupport hardware acceleration
https://bugs.kde.org/show_bug.cgi?id=481110 --- Comment #8 from Levi Marvin --- (In reply to Harald Sitter from comment #7) > Nothing obvious sticks out to me. Whatever the problem is likely is in > libvlc though, on x11 we simply tell libvlc to render onto a window, the > decoding choice is entirely up to libvlc. > > Does this work with vlc? No. VLC can correctly use the GPU for decoding. (The "Video" Bar is active in intel GPU status) -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 481110] Unsupport hardware acceleration
https://bugs.kde.org/show_bug.cgi?id=481110 --- Comment #6 from Levi Marvin --- Created attachment 165694 --> https://bugs.kde.org/attachment.cgi?id=165694=edit iHD driver (intel-media-va-driver-non-free) vdpauinfo output -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 481110] Unsupport hardware acceleration
https://bugs.kde.org/show_bug.cgi?id=481110 --- Comment #5 from Levi Marvin --- (In reply to Harald Sitter from comment #3) > Please run with the following command, play a video and then collect the > entire log output. Thanks. > > PHONON_DEBUG=5 PHONON_BACKEND_DEBUG=5 dragon I have attached the ouput file. -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 481110] Unsupport hardware acceleration
https://bugs.kde.org/show_bug.cgi?id=481110 --- Comment #4 from Levi Marvin --- Created attachment 165693 --> https://bugs.kde.org/attachment.cgi?id=165693=edit The console output. -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 481110] Unsupport hardware acceleration
https://bugs.kde.org/show_bug.cgi?id=481110 --- Comment #2 from Levi Marvin --- (In reply to Harald Sitter from comment #1) > Wayland or X11? X11 -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 481110] New: Unsupport hardware acceleration
https://bugs.kde.org/show_bug.cgi?id=481110 Bug ID: 481110 Summary: Unsupport hardware acceleration Classification: Applications Product: dragonplayer Version: 24.01.95 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: levimar...@icloud.com CC: myr...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Make sure the device is using intel iGPU and NVIDIA dGPU. 2. GPU mode is On-Demand. 3. Open dragon player and play vedio. OBSERVED RESULT There is no GPU be used for decode. (Check in intel_gpu_top and nvidia-smi) EXPECTED RESULT The video engine of GPU should be used for playing video. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION CPU: Intel Core i7 13700H GPU (In about system): Mesa Intel(R) Graphics GPU1: Intel Alderlake_p (Gen12) (RPL-P) [Intel Iris Xe Graphics] GPU2: NVIDIA GeForce RTX 4060 Laptop 8GB -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469643] digiKam 8.0 crashes when starting, as soon as the scanning completes
https://bugs.kde.org/show_bug.cgi?id=469643 Marvin changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #10 from Marvin --- Hi Gilles, Thank you for following up. And apologies for my disappearance from this issue. What happened was that I kept updating stable and beta versions, then started tracing the errors and deleting images that I believe were causing problems, but that took quite some time with the many decades of pictures that I've collected. At some point, when I start digiKam, I'd get an error: - You have insufficient privileges on the database. Following privileges are not assigned to you: ALTER TABLE Check your privileges on the database and restart digiKam. - The app still starts, and I can hit the OK button, then check for latest version, and initiate an upgrade. Installer would do uninstall of current version, then installs the latest, with no visible errors. As I never got through a full scan, I just decided to clean up completely, install the latest daily build 2023-10-14 I could find, create new database and let it scan all subdirectories. I'm back to this PC after several hours and I see that digiKam is still working, it has "No active process" and would like to think that the issue is gone. Thank you for your help! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469643] digiKam 8.0 crashes when starting, as soon as the scanning completes
https://bugs.kde.org/show_bug.cgi?id=469643 Marvin changed: What|Removed |Added Version|8.0.0 |8.1.0 --- Comment #6 from Marvin --- (In reply to caulier.gilles from comment #5) > Well the only way to catch the bug is to clean up the database and rescan > from scratch to try to reproduce the bug. > > the most simpler way can be to create a new user and start digiKam to > repopulate a database. As the collection of files is huge, the best way will > be to import step by step small part of files with debugview in background > to catch the problematic files. When identified, you can share the files > using cloud to investigate here and found the bug. > > Tip: on the new account, start digiKam without any files imported, go to > setup/misc/system and enable debug trace for debugview. After that, start > debugview, take a care that debug traces from digiKam are visible, and start > to import files in your database, until a crash appears. > > Best > > Gilles Caulier Hi Gilles, I did add my pic-RAW folder. I had removed it when I saw lots of exiftool.exe piled up in Win11 the Task Manager and it started crashing again. I also changed to the weekly betas and selected the Debug option. Now, after a few more start/crash/kill exiftool processes/start/crash/etc... it again completed to 100%... but it still crashed while I had left it in the background and wasn't interacting with digiKam for a bit. What are the exact instructions for v8.1-beta on Win11. The instructions at https://www.digikam.org/contribute/ under Windows Host state "If digiKam start properly, go to Setup/Misc/System dialog page..." I guess those are moved around and called something different now? Maybe Settings/Configure digiKam/Miscellaneous/System? "... and turn on the option to generate debug traces." That isn't there, either. I assume it's "Enable internal debug logging"? Also, when I exit digiKam, it appears to close normally. Yet, there are still many exiftool.exe that remain running. Assuming my guesses above were somewhat correct, I still don't get a log file under C:\Users\\AppData\Local\digikam What I do see in DebugView are errors like those but can't spot something that'd crash the app, as it goes to the next RAW file fine. And I had no RAW files initially when I reported the bug. --- [29904] digikam.metaengine: Check ExifTool availability: true [29904] digikam.metaengine: ExifTool "Load Chunks" "-TagsFromFile D:\\pics-RAW\\RAW\\2013\\IMG_7139 (1).CR2 -all:all -o -.exv" [29904] digikam.database: Scanning took 135 ms [29904] digikam.dbengine: Database is locked. Waited 0 [29904] digikam.metaengine: ExifToolProcess::readOutput(): ExifTool command completed [29904] digikam.metaengine: ExifTool complete command for action "Load Chunks" with elasped time (ms): 25 [29904] digikam.metaengine: EXV chunk size: 6855 [29904] digikam.metaengine: ExifTool parsed command for action "Load Chunks" 1 properties decoded [29904] digikam.metaengine: ExifTool complete "Load Chunks" for "D:/pics-RAW/RAW/2013/IMG_7139 (1).CR2" [29904] digikam.metaengine: Metadata chunk loaded with ExifTool [29904] digikam.metaengine: Loading metadata with "ExifTool" backend from "D:/pics-RAW/RAW/2013/IMG_7139 (1).CR2" [29904] digikam.general: Trying to get thumbnail from "D:/pics-RAW/RAW/2013/IMG_7139 (1).CR2" ( "image" ) [29904] digikam.general: Trying to get thumbnail with Exiv2 for "D:/pics-RAW/RAW/2013/IMG_7139 (1).CR2" [29904] digikam.general: Trying to get thumbnail with DImg preview for "D:/pics-RAW/RAW/2013/IMG_7139 (1).CR2" [29904] digikam.general: Trying to get thumbnail from Embedded preview with libraw for "D:/pics-RAW/RAW/2013/IMG_7139 (1).CR2" [29904] digikam.rawengine: LibRaw: loadEmbeddedPreview from "D:/pics-RAW/RAW/2013/IMG_7139 (1).CR2" [29904] digikam.rawengine: LibRaw: failed to run open_file: Unsupported file format or not RAW file [29904] digikam.rawengine: Failed to load embedded RAW preview [29904] digikam.general: Trying to get thumbnail from half preview with libraw for "D:/pics-RAW/RAW/2013/IMG_7139 (1).CR2" [29904] digikam.rawengine: Try to use reduced RAW picture extraction [29904] digikam.rawengine: LibRaw: failed to run open_file: Unsupported file format or not RAW file [29904] digikam.general: Trying to get thumbnail from Embedded preview with Exiv2 for "D:/pics-RAW/RAW/2013/IMG_7139 (1).CR2" [29904] digikam.metaengine: Exiv2 ( 2 ) : Directory Image, entry 0x0111: Strip 0 is outside of the data area; ignored. [29904] [29904] digikam.metaengine: Exiv2 ( 2 ) : Directory SubImage1 has an unexpected next pointer; ignored. [29904] [29904] d
[digikam] [Bug 469643] digiKam 8.0 crashes when starting, as soon as the scanning completes
https://bugs.kde.org/show_bug.cgi?id=469643 --- Comment #4 from Marvin --- (In reply to caulier.gilles from comment #3) > How many files do you have in your collection ? > > I don't know why crash course do not handle the exception. > > The debugview running in background will indicate where in scan process the > crash appear, typically which file is the cause of the exception. > > the HEIF format can be a source of dysfunction. > > Best > > Gilles Caulier Hi Gilles, d:\pics contains 126,437 Files, 919 Folders. After a couple of more days of crashes while scanning, killing all digiKam processes, and restarting, the "Find new items" now got to 100%!!! I'm going to reinstall the normal, not -debug, version. Unless you want me to try something so we can find the bug and devs will fix it for other users. Thanks, Marv -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469643] digiKam 8.0 crashes when starting, as soon as the scanning completes
https://bugs.kde.org/show_bug.cgi?id=469643 --- Comment #2 from Marvin --- (In reply to caulier.gilles from comment #1) > Hi Marvin, > > Please give us more details: > > - The database type that you use. > - The king of file format that you manage on your collection. > - The program trace captured with debugview and the crash course captured > with DrMinGW (see details here : https://www.digikam.org/contribute/) > > Thanks in advance > > Gilles Caulier Hi Gilles, I did install the -debug version and it keeps crashing. I was hoping to get a .log file or something easily readable to crawl and try to see what breaks. There are no .log files under C:\Users\\AppData\Local\digikam, just \cache and \facesengine. It's an old Picasa set of subfolders with pics taken by various Nexus and Pixel phones, both jpg and raw, also some I got from iphone users. It looks like it's crashing while scanning. If I kill all the digiKam processes and start it again the "Find new items" bar seems to be able to progress by another percent or so. I'm at 96% after many many mny restarts. The install was done with just clicking Next so internal SQLite, I guess. Apart from installing Sysinternals and DebugView, is there something simple I can review? Thanks, Marv -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469643] New: digiKam 8.0 crashes when starting, as soon as the scanning completes
https://bugs.kde.org/show_bug.cgi?id=469643 Bug ID: 469643 Summary: digiKam 8.0 crashes when starting, as soon as the scanning completes Classification: Applications Product: digikam Version: 8.0.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Database-Scan Assignee: digikam-bugs-n...@kde.org Reporter: cqzhg...@duck.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. install digiKam 8.0 on Windows 11 (upgraded from 7.10 in my case) 2. start digiKam 3. wait for the initial small window to scan from 0% until... it crashes. The splash screen came up a few times but it doesn't anymore. OBSERVED RESULT digiKam 8.0 on Win11 quietly crashes EXPECTED RESULT to get to the splash screen and then start working with my photos SOFTWARE/OS VERSIONS Windows: Windows 11 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Anything I can do to collect logs or install a debug version on Windows 11? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 462577] New: Window panel and Kickoff don't apply accent color
https://bugs.kde.org/show_bug.cgi?id=462577 Bug ID: 462577 Summary: Window panel and Kickoff don't apply accent color Classification: Plasma Product: Breeze Version: 5.26.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Color scheme Assignee: plasma-b...@kde.org Reporter: m...@marvinreuter.de Target Milestone: --- SUMMARY When changing accent color in System Settings > Appearance > Color, task panel and Kickoff application launcher do not apply that chosen color. STEPS TO REPRODUCE 1. Open System Settings > Appearance > Color 2. Change accent color 3. Edit color scheme (esp. Decoration (hover, mouseover)) OBSERVED RESULT Task panel and Kickoff stick to the old accent color. EXPECTED RESULT Task panel and Kickoff show some elements (e.g. active window) in the new accent color. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.15.78-1 KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 459167] New: Printer configuration dialog missing custom user Id text box with some ppds
https://bugs.kde.org/show_bug.cgi?id=459167 Bug ID: 459167 Summary: Printer configuration dialog missing custom user Id text box with some ppds Product: systemsettings Version: 5.25.5 Platform: unspecified OS: Linux Status: REPORTED Severity: major Priority: NOR Component: kcm_printer_manager Assignee: dantt...@gmail.com Reporter: marvin-dennis.n...@kit.edu CC: plasma-b...@kde.org Target Milestone: --- Created attachment 152079 --> https://bugs.kde.org/attachment.cgi?id=152079=edit printer ppd SUMMARY *** When using some ppd files, selecting 'custom user id' does not provide a way to enter such custom user id although this works on the CUPS web interface. *** STEPS TO REPRODUCE 1. Add a printer with ppd having a JCL in the printer options 2. Go to 'configure' -> 'Printer options' 3. Scroll to JCL and change 'User Id (Up to 8 alphanumeric characters)' to 'Custom UserID' OBSERVED RESULT There is no text box 'UserId' showing up where you can enter the custom user id EXPECTED RESULT Text box 'UserId' showing up where you can enter the custom user id. Just like it does on the CUPS web interface SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro 21.3.0 (available in About System) KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 453896] When saving a new transaction Kmymoney crashes each time without saving
https://bugs.kde.org/show_bug.cgi?id=453896 --- Comment #12 from Marvin Dickhaus --- Really nice find. Thanks for also following up in the GnuTLS Repo https://gitlab.com/gnutls/gnutls/-/issues/1367. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 453857] malloc() aborts during save
https://bugs.kde.org/show_bug.cgi?id=453857 Marvin Dickhaus changed: What|Removed |Added CC||gradavies...@fastmail.co.uk --- Comment #5 from Marvin Dickhaus --- *** Bug 453896 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 453896] When saving a new transaction Kmymoney crashes each time without saving
https://bugs.kde.org/show_bug.cgi?id=453896 Marvin Dickhaus changed: What|Removed |Added CC||account-kde@marvindickhaus. ||de Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #11 from Marvin Dickhaus --- *** This bug has been marked as a duplicate of bug 453857 *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 453857] malloc() aborts during save
https://bugs.kde.org/show_bug.cgi?id=453857 Marvin Dickhaus changed: What|Removed |Added CC||account-kde@marvindickhaus. ||de Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Marvin Dickhaus --- Same issue for me. Also on Arch Linux with the same version scheme. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 437955] New: Elisa sometimes crashes when scrolling through album
https://bugs.kde.org/show_bug.cgi?id=437955 Bug ID: 437955 Summary: Elisa sometimes crashes when scrolling through album Product: Elisa Version: 20.12.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: mhaeu...@posteo.de Target Milestone: --- Application: elisa (20.12.3) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.12.8-300.fc34.x86_64 x86_64 Windowing System: X11 Drkonqi Version: 5.21.5 Distribution: Fedora 34 (KDE Plasma) -- Information about the crash: - What I was doing when the application crashed: Scrolling through the song list of an album, Elisa unexpectdely crashed. I found no clear way to reproduce the issue, but it happens every once in a while. The crash can be reproduced sometimes. -- Backtrace: Application: Elisa (elisa), signal: Segmentation fault [KCrash Handler] #4 0x7fceada16189 in QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () at /lib64/libQt5Qml.so.5 #5 0x7fceada16fe2 in QQmlIncubationController::incubateFor(int) () at /lib64/libQt5Qml.so.5 #6 0x7fceac25b23e in QQuickWindowIncubationController::timerEvent(QTimerEvent*) () at /lib64/libQt5Quick.so.5 #7 0x7fcead51321f in QObject::event(QEvent*) (this=0x55b8ee6d2aa0, e=0x7fffe3095230) at kernel/qobject.cpp:1336 #8 0x7fceae47ce73 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x55b8ee6d2aa0, e=0x7fffe3095230) at kernel/qapplication.cpp:3632 #9 0x7fcead4ebf48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55b8ee6d2aa0, event=0x7fffe3095230) at kernel/qcoreapplication.cpp:1063 #10 0x7fcead5379e3 in QTimerInfoList::activateTimers() (this=0x55b8ee4d47c0) at kernel/qtimerinfo_unix.cpp:643 #11 0x7fcead5382ec in timerSourceDispatch(GSource*, GSourceFunc, gpointer) (source=) at kernel/qeventdispatcher_glib.cpp:183 #12 0x7fceab1da4cf in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #13 0x7fceab22e4e8 in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0 #14 0x7fceab1d7c03 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #15 0x7fcead5386f8 in QEventDispatcherGlib::processEvents(QFlags) (this=0x55b8ee4d3f00, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #16 0x7fcead4ea9b2 in QEventLoop::exec(QFlags) (this=this@entry=0x7fffe30954d0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #17 0x7fcead4f2544 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #18 0x55b8ed03a973 in main () [Inferior 1 (process 10817) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 437820] New: KDialog destination picker crashes when downloading a file
https://bugs.kde.org/show_bug.cgi?id=437820 Bug ID: 437820 Summary: KDialog destination picker crashes when downloading a file Product: kdialog Version: 20.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: br...@frogmouth.net Reporter: mhaeu...@posteo.de Target Milestone: --- SUMMARY Downloading a file from a Chromium-based browser, KDialog opens to choose the destination location and immediately crashes. STEPS TO REPRODUCE 1. Ensure the Chromium-based browser asks to choose the destination on download. 2. Attempt to download a file from within the Chromium-based browser. OBSERVED RESULT KDialog immediately crashes. EXPECTED RESULT KDialog should allow picking the destination without crashing. SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: Fedora 34 (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- Backtrace: Application: KDialog (kdialog), signal: Segmentation fault [KCrash Handler] #4 0x7f67bafd5766 in __memmove_avx_unaligned_erms () from /lib64/libc.so.6 #5 0x7f67bbae525f in memcpy (__len=46080, __src=0x7f67a2c8e000, __dest=) at /usr/include/bits/string_fortified.h:29 #6 QImage::copy (this=0x7ffde460bfc0, r=...) at image/qimage.cpp:1182 #7 0x7f67a91df60d in KIO::PreviewJobPrivate::slotThumbData(KIO::Job*, QByteArray const&) () from /lib64/libKF5KIOWidgets.so.5 #8 0x7f67bb50f4b0 in QtPrivate::QSlotObjectBase::call (a=0x7ffde460c110, r=, this=0x55dee1cda1b0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #9 doActivate (sender=0x55dee1bfec10, signal_index=25, argv=0x7ffde460c110) at kernel/qobject.cpp:3886 #10 0x7f67bc916c38 in KIO::TransferJob::data(KIO::Job*, QByteArray const&) () from /lib64/libKF5KIOCore.so.5 #11 0x7f67bb50f4b0 in QtPrivate::QSlotObjectBase::call (a=0x7ffde460c210, r=, this=0x55dee1992980) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #12 doActivate (sender=0x55dee1eb8ad0, signal_index=3, argv=0x7ffde460c210) at kernel/qobject.cpp:3886 #13 0x7f67bc8f8926 in KIO::SlaveInterface::data(QByteArray const&) () from /lib64/libKF5KIOCore.so.5 #14 0x7f67bc8f833a in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /lib64/libKF5KIOCore.so.5 #15 0x7f67bc8f060d in KIO::SlaveInterface::dispatch() () from /lib64/libKF5KIOCore.so.5 #16 0x7f67bc8f9c62 in KIO::Slave::gotInput() () from /lib64/libKF5KIOCore.so.5 #17 0x7f67bb50f4b0 in QtPrivate::QSlotObjectBase::call (a=0x7ffde460c430, r=, this=0x55dee1eb0bd0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #18 doActivate (sender=0x55dee198f2f0, signal_index=3, argv=0x7ffde460c430) at kernel/qobject.cpp:3886 #19 0x7f67bb506257 in QObject::event (this=0x55dee198f2f0, e=0x55dee1ecc600) at kernel/qobject.cpp:1314 #20 0x7f67bc0f5e73 in QApplicationPrivate::notify_helper (this=, receiver=0x55dee198f2f0, e=0x55dee1ecc600) at kernel/qapplication.cpp:3632 #21 0x7f67bb4def48 in QCoreApplication::notifyInternal2 (receiver=0x55dee198f2f0, event=0x55dee1ecc600) at kernel/qcoreapplication.cpp:1063 #22 0x7f67bb4e1c76 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55dee1776210) at kernel/qcoreapplication.cpp:1817 #23 0x7f67bb52bc57 in postEventSourceDispatch (s=0x55dee184dc20) at kernel/qeventdispatcher_glib.cpp:277 #24 0x7f67b9d034cf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #25 0x7f67b9d574e8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #26 0x7f67b9d00c03 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #27 0x7f67bb52b6f8 in QEventDispatcherGlib::processEvents (this=0x55dee1850cc0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #28 0x7f67bb4dd9b2 in QEventLoop::exec (this=this@entry=0x7ffde460c880, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #29 0x7f67bc2f4c87 in QDialog::exec (this=0x55dee18c8830) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #30 0x7f67bc2f4bc7 in QDialog::exec (this=0x7ffde460cb60) at dialogs/qdialog.cpp:597 #31 0x55dee0700484 in main () [Inferior 1 (process 5634) detached] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435180] Plasma crash when taking a screenshot
https://bugs.kde.org/show_bug.cgi?id=435180 --- Comment #5 from Marvin Häuser --- Okay, I realised the screenshot being unavailable was due to a configuration error of the clipboard manager, so not-a-bug. Sorry, I'm still getting used to how KDE and Linux work. :) So far, since today's update, even heavy provocation did not yield any of the previous symptoms. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435180] Plasma crash when taking a screenshot
https://bugs.kde.org/show_bug.cgi?id=435180 --- Comment #4 from Marvin Häuser --- I saw there just was a another update. I cannot easily verify whether this one fully resolved the issue because it only happens very rarely (I'd say once or twice a week?). I found no way to reliably reproduce this yet, sorry. On a different note, I assumed the screenshot not being available in clipboard was a consequence of the crash, but I think sometimes it is unavailable without any crash. It happens with a custom hotkey bound to 'spectacle -brc'. Quickly searching (I previously did not realise the default is to search only open tickets, sorry!) yields only fixed or Wayland-related (I am on X11) issues. Is there a ticket I should be aware of, or should I open a new one? Unfortunately I cannot reliably reproduce this issue either. Thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435180] Plasma crash when taking a screenshot
https://bugs.kde.org/show_bug.cgi?id=435180 --- Comment #2 from Marvin Häuser --- Good day Mr. Redondo, As I have written in my report, it is likely closely related to the bug you marked as duplicate, yet yesterday's update resolved the original symptoms, but not the ones described here. Did yesterday's update only include a partial fix? Thank you a lot! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435180] New: Plasma crash when taking a screenshot
https://bugs.kde.org/show_bug.cgi?id=435180 Bug ID: 435180 Summary: Plasma crash when taking a screenshot Product: plasmashell Version: 5.21.3 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mhaeu...@posteo.de CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.21.3) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.11.10-051110-generic x86_64 Windowing System: X11 Drkonqi Version: 5.21.3 Distribution: KDE neon User Edition 5.21 -- Information about the crash: - What I was doing when the application crashed: Took a screenshot for the second time (into clipboard), as the first time the screenshot was not available in clipboard for unknown reasons (this happens frequently, usually without a crash). - Unusual behavior I noticed: Plasmashell seems to have restarted, the screenshot thumbnail took very long to load. It seems to be mildly related to https://bugs.kde.org/show_bug.cgi?id=430862, yet yesterday's kio update fixed the described issue pattern, while this issue is (still) sometimes(!) reproducible with the new update. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f6b8d0078c0 (LWP 2181))] [New LWP 2194] [New LWP 2200] [New LWP 2216] [New LWP 2422] [New LWP 2665] [New LWP 2700] [New LWP 2701] [New LWP 2747] [New LWP 2795] [New LWP 2855] [New LWP 2912] [New LWP 2916] [New LWP 7584] [New LWP 7590] [New LWP 7591] [New LWP 7592] [New LWP 7642] [New LWP 7643] [New LWP 7644] [New LWP 7645] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f6b90dc0aff in __GI___poll (fds=fds@entry=0x7ffc60c64da8, nfds=nfds@entry=1, timeout=timeout@entry=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 Thread 21 (Thread 0x7f6b627fc700 (LWP 7645)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7f6b627fbca0, clockid=, expected=0, futex_word=0x7f6b0c1468d8) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7f6b627fbca0, clockid=, mutex=0x7f6b20001a60, cond=0x7f6b0c1468b0) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7f6b0c1468b0, mutex=0x7f6b20001a60, abstime=0x7f6b627fbca0) at pthread_cond_wait.c:656 #3 0x7f6b898cb192 in () at /lib/x86_64-linux-gnu/libnvidia-glcore.so.460.67 #4 0x7f6b896a3bbc in () at /lib/x86_64-linux-gnu/libnvidia-glcore.so.460.67 #5 0x7f6b898cd3ba in () at /lib/x86_64-linux-gnu/libnvidia-glcore.so.460.67 #6 0x7f6b901a4609 in start_thread (arg=) at pthread_create.c:477 #7 0x7f6b90dcd293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7f6b62ffd700 (LWP 7644)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55d033465224) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55d0334651d0, cond=0x55d0334651f8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55d0334651f8, mutex=0x55d0334651d0) at pthread_cond_wait.c:638 #3 0x7f6b91153d5b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x55d0334651d0) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=this@entry=0x55d030d07608, mutex=mutex@entry=0x55d030d07600, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f6b92eee814 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x55d030d075f8) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qdeadlinetimer.h:68 #6 QSGRenderThread::processEventsAndWaitForMore() (this=this@entry=0x55d030d07560) at scenegraph/qsgthreadedrenderloop.cpp:936 #7 0x7f6b92eeec89 in QSGRenderThread::run() (this=0x55d030d07560) at scenegraph/qsgthreadedrenderloop.cpp:1053 #8 0x7f6b9114dbec in QThreadPrivate::start(void*) (arg=0x55d030d07560) at thread/qthread_unix.cpp:329 #9 0x7f6b901a4609 in start_thread (arg=) at pthread_create.c:477 #10 0x7f6b90dcd293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f6b63fff700 (LWP 7643)): #0 0x7f6b90dc0aff in __GI___poll (fds=0x7f6b63ffe7a8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f6b898ce640 in () at /lib/x86_64-linux-gnu/libnvidia-glcore.so.460.67 #2 0x7f6b89993293 in () at /lib/x86_64-linux-gnu/libnvidia-glcore.so.460.67 #3 0x7f6b89993416 in () at /lib/x86_64-linux-gnu/libnvidia-glcore.so.460.67 #4 0x7f6b8ad02f07 in () at /lib/x86_64-linux-gnu/libGLX_nvidia.so.0 #5 0x7f6b8acbb2c0 in () at /lib/x86_64-linux-gnu/libGLX_nvidia.so.0 #6 0x7f6b898cc31c in () at
[kio-extras] [Bug 435015] kdeinit5 crashes, related to notifications
https://bugs.kde.org/show_bug.cgi?id=435015 --- Comment #3 from Marvin Häuser --- Thank you for linking the other ticket that I missed, so far it seems that yesterday's Neon updates to kio indeed fixed the issue. Thanks to everyone involved! -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 435015] New: kdeinit5 crashes, related to notifications
https://bugs.kde.org/show_bug.cgi?id=435015 Bug ID: 435015 Summary: kdeinit5 crashes, related to notifications Product: kio-extras Version: 20.12.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Thumbnails and previews Assignee: plasma-b...@kde.org Reporter: mhaeu...@posteo.de Target Milestone: --- SUMMARY kio-extra's kdeinit5 crashes in multiple occasions related to notifications and possibly screenshots (latter possibly just a side-effect of former). I believe the crashes are not always but often reproducible, yet currently kdeinit5 consistently crashes. STEPS TO REPRODUCE - Open the notification centre (often or always), OR - Receive a notification banner (often or always), OR - Take a screenshot with Spectacle (always, possibly related to above) OBSERVED RESULT kdeinit5 crashes. If a screenshot was taken, it is available on the clipboard for a brief moment, before it is not anymore (possibly due to the application crash flushing its data from the clipboard?). EXPECTED RESULT kdeinit5 should not crash, and screenshots should be persistent in the clipboard. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.21.3 KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Application: kdeinit5 (kdeinit5), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7faeddd0fcc0 (LWP 156913))] [New LWP 156914] [New LWP 156918] [New LWP 156919] [New LWP 156922] [New LWP 156923] [New LWP 156924] [New LWP 156925] [New LWP 156926] [New LWP 156927] [New LWP 156928] [New LWP 156929] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7faee11e3aff in __GI___poll (fds=fds@entry=0x7ffc0fca9d28, nfds=nfds@entry=1, timeout=timeout@entry=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 Thread 12 (Thread 0x7faec17fa700 (LWP 156929)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7faec17f9cd0, clockid=, expected=0, futex_word=0x562c8e678414) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7faec17f9cd0, clockid=, mutex=0x562c8e6783c0, cond=0x562c8e6783e8) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x562c8e6783e8, mutex=0x562c8e6783c0, abstime=0x7faec17f9cd0) at pthread_cond_wait.c:656 #3 0x7faee1393ce8 in QWaitConditionPrivate::wait_relative (this=0x562c8e6783c0, deadline=...) at thread/qwaitcondition_unix.cpp:136 #4 QWaitConditionPrivate::wait (deadline=..., this=0x562c8e6783c0) at thread/qwaitcondition_unix.cpp:144 #5 QWaitCondition::wait (this=this@entry=0x562c8e65ff10, mutex=mutex@entry=0x562c8e6656d8, deadline=...) at thread/qwaitcondition_unix.cpp:225 #6 0x7faee13911f1 in QThreadPoolThread::run (this=0x562c8e65ff00) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:270 #7 0x7faee138dbec in QThreadPrivate::start (arg=0x562c8e65ff00) at thread/qthread_unix.cpp:329 #8 0x7faee074c609 in start_thread (arg=) at pthread_create.c:477 #9 0x7faee11f0293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7faec1ffb700 (LWP 156928)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7faec1ffacd0, clockid=, expected=0, futex_word=0x562c8e677f74) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7faec1ffacd0, clockid=, mutex=0x562c8e677f20, cond=0x562c8e677f48) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x562c8e677f48, mutex=0x562c8e677f20, abstime=0x7faec1ffacd0) at pthread_cond_wait.c:656 #3 0x7faee1393ce8 in QWaitConditionPrivate::wait_relative (this=0x562c8e677f20, deadline=...) at thread/qwaitcondition_unix.cpp:136 #4 QWaitConditionPrivate::wait (deadline=..., this=0x562c8e677f20) at thread/qwaitcondition_unix.cpp:144 #5 QWaitCondition::wait (this=this@entry=0x562c8e650320, mutex=mutex@entry=0x562c8e6656d8, deadline=...) at thread/qwaitcondition_unix.cpp:225 #6 0x7faee13911f1 in QThreadPoolThread::run (this=0x562c8e650310) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:270 #7 0x7faee138dbec in QThreadPrivate::start (arg=0x562c8e650310) at thread/qthread_unix.cpp:329 #8 0x7faee074c609 in start_thread (arg=) at pthread_create.c:477 #9 0x7faee11f0293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7faec27fc700 (LWP 156927)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7faec27fbcd0, clockid=, expected=0, futex_word=0x562c8e677ad4) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7faec27fbcd0, clockid=, mutex=0x562c8e677a80, cond=0x562c8e677aa8) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x562c8e677aa8, mutex=0x562c8e677a80, abstime=0x7faec27fbcd0) at pthread_cond_wait.c:656 #3
[Spectacle] [Bug 409762] [wayland] Screenshots taken on displays with scaling lack resolution
https://bugs.kde.org/show_bug.cgi?id=409762 --- Comment #22 from Marvin Hagemeister --- As a user I'd expect screenshots to be always taken in the native resolution, regardless of whether I have multiple screens attached or not. I'd be confused if there is any downscaling happening behind the scenes. When doing a screenshot the point is to capture everything as is, and anything else seems to take away from that. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 418152] Floating indicator for windows on Wayland
https://bugs.kde.org/show_bug.cgi?id=418152 --- Comment #1 from Marvin Dickhaus --- Just found a really annoying one: When you enter a date on a transaction there is a popup indicating the day. On sway this is drawed as a new window which gets immediate focus. Because of the focus the popup closes and the cycle starts over, which gets you a nice blinky screen. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 418152] New: Floating indicator for windows on Wayland
https://bugs.kde.org/show_bug.cgi?id=418152 Bug ID: 418152 Summary: Floating indicator for windows on Wayland Product: kmymoney Version: 5.0.8 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: account-...@marvindickhaus.de Target Milestone: --- SUMMARY I noticed that many windows that were drawn as floating on X (using i3wm) do not appear in the foreground as floating on Wayland (sway). Especially I noticed the following for the online banking dialogue (update account): Pick start date (not floating) Executing Jobs (not floating) PIN Entry (not floating) Schedule found (floating) Import statistics (floating) Configure AqBanking (not floating) New Account (not floating) New Institution (not floating) Import from ... (not floating) Export to ... (not floating) STEPS TO REPRODUCE 1. Start kmymoney in wayland 2. Execute e.g. Online Banking Import or create a new institution 3. Observe floating indicator OBSERVED RESULT Windows are not floating EXPECTED RESULT Windows are floating in the foreground of kmymoney SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION wayland using sway -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412998] System Settings -> Display and Monitor -> Compositor crashes
https://bugs.kde.org/show_bug.cgi?id=412998 Marvin changed: What|Removed |Added CC||lopez.marv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412605] Closed accounts are not hidden when option is ticked
https://bugs.kde.org/show_bug.cgi?id=412605 Marvin Dickhaus changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #2 from Marvin Dickhaus --- (In reply to Jack from comment #1) > Please check whether you have "Show all accounts" checked. (under the > "View" menu.) That overrides the other setting. Thanks. That was the issue. Even when I restored default settings, this was apparently not cleared. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412605] New: Closed accounts are not hidden when option is ticked
https://bugs.kde.org/show_bug.cgi?id=412605 Bug ID: 412605 Summary: Closed accounts are not hidden when option is ticked Product: kmymoney Version: git (master) Platform: Compiled Sources OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: account-...@marvindickhaus.de Target Milestone: --- SUMMARY I have the Option "Do not show closed accounts" ticked in the Config -> General -> Filter options. The closed accounts are still shown in the "Accounts"-Tab as well as in the Ledger selection menu. STEPS TO REPRODUCE 1. Tick the option "Do not show closed accounts" 2. Go to the ledger and try to select a different account OBSERVED RESULT Closed accounts are not hidden EXPECTED RESULT Closed accounts should be hidden SOFTWARE/OS VERSIONS 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.
[kmymoney] [Bug 412577] Optical Tan Methods not working / no dialogue shown for tan
https://bugs.kde.org/show_bug.cgi?id=412577 Marvin Dickhaus changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #2 from Marvin Dickhaus --- I previously compiled against the 5.0.7 tarball. I recompiled against the latest master and now the optical TAN challenge works like a charm. I was able to import transactions again. Keep up the good work. :-) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412577] New: Optical Tan Methods not working / no dialogue shown for tan
https://bugs.kde.org/show_bug.cgi?id=412577 Bug ID: 412577 Summary: Optical Tan Methods not working / no dialogue shown for tan Product: kmymoney Version: 5.0.7 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: major Priority: NOR Component: onlinebanking Assignee: kmymoney-de...@kde.org Reporter: account-...@marvindickhaus.de Target Milestone: --- SUMMARY I compiled the latest aqbanking Versions: AqBanking-CLI: 5.99.38 Gwenhywfar : 4.99.20.0 AqBanking: 5.99.38.0 and kmymoney 5.0.7. It seems like the optical TAN methods (see https://www.aquamaniac.de/rdm/projects/aqbanking/wiki/ImplementTanMethods) are not implemented? When I try to connect to my account with comdirect Bank, (tan method photoTan) I'm unable to retrieve any values where a TAN input is required. aqhbci-tool4 getaccs lists a TAN so it looks like the account is working as far as aqbanking is concerned. HBCI: 0030 - TAN-Eingabe erforderlich. (S) Dialog not aborted, assuming PIN is ok 3:2019/10/03 21-54-11:aqhbci(39619):provider_tan.c: 112: ChallengeHHD is [0009696D6167652F706E670E8F89504E470D0A1A0A000D4948445200D600D6080600ADE37C2E0E564944415478DAED9DB16E145B16451D3874E00F7040E0F07D82030232C8F98527915A2224B54442404EEAD0129FE01489809080D0A10302C21AF 3:2019/10/03 21-54-11:aqhbci(39619):provider_tan.c: 120: Created challenge HHUD is: 3:2019/10/03 21-54-11:aqhbci(39619):String size is 3740 3:2019/10/03 21-54-11:aqhbci(39619):: 00 09 69 6d 61 67 65 2f 70 6e 67 0e 8f 89 50 4e ..image/png...PN 3:2019/10/03 21-54-11:aqhbci(39619):0010: 47 0d 0a 1a 0a 00 00 00 0d 49 48 44 52 00 00 00 GIHDR... STEPS TO REPRODUCE 1. Configure aqbanking with a HBCI bank that uses an optical TAN method 2. Try to list accounts 3. OBSERVED RESULT Dialogue aborts unexpected EXPECTED RESULT TAN dialogue is displayed with the optical image. ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 409762] [wayland] Screenshots are always a little blurry
https://bugs.kde.org/show_bug.cgi?id=409762 --- Comment #6 from Marvin Hagemeister --- Yup, I can confirm that the X11 screen is the proper screen resolution and that the wayland screenshot exactly half of that. The bug only occurs when the scaling setting in KDE's "Display Settings" page is set to something other than 1x. In my case that's 2x so spectacle seems to think it'd only need to use half the resolution. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 409762] [wayland] Screenshots are always a little blurry
https://bugs.kde.org/show_bug.cgi?id=409762 --- Comment #4 from Marvin Hagemeister --- @Nate Thanks a bunch for responding. I've added two screenshots with Konsole fully maximized on the left half of the screen. One thing I noticed is that they wayland screenshot has only half the resolution. That's why the file sizes are wildly different. That peaked my curiosity and I took another screenshot with display scaling set to 1x instead of the default 2x. Et voila spectacle takes a screenshot with the right resolution. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 409762] [wayland] Screenshots are always a little blurry
https://bugs.kde.org/show_bug.cgi?id=409762 --- Comment #3 from Marvin Hagemeister --- Created attachment 121540 --> https://bugs.kde.org/attachment.cgi?id=121540=edit Spectacle Wayland Screenshot taken with spectacle on wayland -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 409762] [wayland] Screenshots are always a little blurry
https://bugs.kde.org/show_bug.cgi?id=409762 --- Comment #2 from Marvin Hagemeister --- Created attachment 121539 --> https://bugs.kde.org/attachment.cgi?id=121539=edit Spectacle X11 Screenshot taken with spectacle on X11 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 409762] New: [wayland] Screenshots are always a little blurry
https://bugs.kde.org/show_bug.cgi?id=409762 Bug ID: 409762 Summary: [wayland] Screenshots are always a little blurry Product: Spectacle Version: 19.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: he...@marvinh.dev CC: k...@david-redondo.de Target Milestone: --- Created attachment 121489 --> https://bugs.kde.org/attachment.cgi?id=121489=edit Sample blurry screenshot taken by spectacle SUMMARY Whenever I take a screenshot with spectacle the resulting image is super blurry. I'm not sure if this is related to wayland or caused by a high-dpi screen or anti-aliasing. Please have a look at the attached screenshot which shows the problem STEPS TO REPRODUCE 1. Run a wayland session 2. Make a screenshot 3. Open created screenshot OBSERVED RESULT Screenshot is blurry EXPECTED RESULT Screenshot is crisp sharp SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION My laptop has a 4k screen (Dell XPS 9380) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 409608] [wayland] Screenshot an area of the screen
https://bugs.kde.org/show_bug.cgi?id=409608 --- Comment #2 from Marvin Hagemeister --- Sweet, thanks for the quick response! That's very exciting! -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 409608] New: [wayland] Screenshot an area of the screen
https://bugs.kde.org/show_bug.cgi?id=409608
Bug ID: 409608
Summary: [wayland] Screenshot an area of the screen
Product: Spectacle
Version: 19.04.2
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: General
Assignee: m...@baloneygeek.com
Reporter: he...@marvinh.dev
CC: k...@david-redondo.de
Target Milestone: ---
SUMMARY
I do a lot of web development and for that I find myself often in the situation
to only screenshot certain areas instead of a complete window or the full
screen.
Inside spectacle's main window there is a dropdown option for capture mode and
it only lists "Full Screen" or "Window Under Cursor" for me. So I guess this
issue is sort of a feature request to only capture parts of the screen.
STEPS TO REPRODUCE
1. Open spectacle
2. Click on the "Area" dropdown
3. Only 2 Options are available ("Full Screen" and "Window Under Cursor")
OBSERVED RESULT
When pressing the "print" button my cursor turns into a cross and I was
expecting that drawing a rectangle with the mouse would overlay a marquee and
screenshot only that area. Instead nothing happens and the full screen is
captured.
EXPECTED RESULT
Drawing a rectangle with the mouse would display an overlay with the selected
region and capture only that.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.16.2
KDE Frameworks Version: 5.59.0
Qt Version: 5.13.0
ADDITIONAL INFORMATION
I'm using wayland, not X.
--
You are receiving this mail because:
You are watching all bug changes.
[lattedock] [Bug 409105] [wayland] crash when application launcher is present and clicked twice
https://bugs.kde.org/show_bug.cgi?id=409105 --- Comment #6 from Marvin Hagemeister --- Tried getting a stack trace by running latte via gdb. I hope this is correct, as I'm not at all familiar with native development. This is the trace: Thread 15 "QSGRenderThread" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffad3db700 (LWP 25621)] 0x74c95e94 in wl_proxy_marshal_constructor () from /usr/lib/libwayland-client.so.0 (gdb) bt #0 0x74c95e94 in wl_proxy_marshal_constructor () at /usr/lib/libwayland-client.so.0 #1 0x709b319b in QtWaylandClient::QWaylandWindow::handleUpdate() () at /usr/lib/libQt5WaylandClient.so.5 #2 0x7fffedf33d78 in () at /usr/lib/qt/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so #3 0x76263142 in QOpenGLContext::swapBuffers(QSurface*) () at /usr/lib/libQt5Gui.so.5 #4 0x777fd82e in () at /usr/lib/libQt5Quick.so.5 #5 0x778016f8 in () at /usr/lib/libQt5Quick.so.5 #6 0x75b2ebf0 in () at /usr/lib/libQt5Core.so.5 #7 0x749b257f in start_thread () at /usr/lib/libpthread.so.0 #8 0x75660f13 in clone () at /usr/lib/libc.so.6 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 409104] Can't open "Export" context menu
https://bugs.kde.org/show_bug.cgi?id=409104 --- Comment #4 from Marvin Hagemeister --- Sorry, I forgot to fill out the OS section: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.16.1 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 I'll try to check with kwin-git later. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 409105] Latte-dock crashes when application launcher is present and clicked twice
https://bugs.kde.org/show_bug.cgi?id=409105 --- Comment #3 from Marvin Hagemeister --- That's good to now. Just checked against the git version and it crashes too. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 409105] Latte-dock crashes when application launcher is present and clicked twice
https://bugs.kde.org/show_bug.cgi?id=409105 Marvin Hagemeister changed: What|Removed |Added Version|0.8.8 |git (master) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 409105] New: Latte-dock crashes when application launcher is present and clicked twice
https://bugs.kde.org/show_bug.cgi?id=409105 Bug ID: 409105 Summary: Latte-dock crashes when application launcher is present and clicked twice Product: lattedock Version: 0.8.8 Platform: Other OS: Linux Status: REPORTED Keywords: wayland Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: he...@marvinh.dev Target Milestone: --- SUMMARY Lattedock crashes when the application launcher is present and the icon is clicked twice. Output of `latte-dock -d` ``` [debug 6:57:12.994994] - syncGeometry() ended... [warning 6:57:46.0505] - Non-toplevel surfaces can't request window states [warning 6:57:46.088088] - Delivering update request through fallback timer, may not be in sync with display [warning 6:57:46.205205] - Delivering update request through fallback timer, may not be in sync with display [warning 6:57:46.421421] - Non-toplevel surfaces can't request window states [warning 6:57:46.725725] - Non-toplevel surfaces can't request window states [warning 6:57:47.484484] - Wayland does not support QWindow::requestActivate() KCrash: Attempting to start /usr/bin/latte-dock directly KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = latte-dock path = /usr/bin pid = 7978 KCrash: Arguments: /usr/bin/latte-dock --replace -d KCrash: Attempting to start /usr/lib/drkonqi directly [warning 6:57:48.916916] - QSocketNotifier: Invalid socket 6 and type 'Read', disabling... [warning 6:57:48.916916] - QSocketNotifier: Invalid socket 23 and type 'Read', disabling... ``` STEPS TO REPRODUCE 1. Put default KDE Launcher in latte-dock 2. Click twice on the launcher icon 3. click anywhere outside like on the desktop 4. -> Crash OBSERVED RESULT latte-dock crashes and restarts EXPECTED RESULT latte-dock should not crash SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.16.1 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 409104] New: Can't open "Export" context menu
https://bugs.kde.org/show_bug.cgi?id=409104 Bug ID: 409104 Summary: Can't open "Export" context menu Product: Spectacle Version: 19.04.2 Platform: Other OS: Linux Status: REPORTED Keywords: wayland Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: mar...@marvinhagemeister.de CC: k...@david-redondo.de Target Milestone: --- SUMMARY Under wayland I can't open the export context menu. When this happens and spectacle is started from the terminal it prints this error message: ``` qt.qpa.wayland: Non-toplevel surfaces can't request window states ``` STEPS TO REPRODUCE 1. execute `spectacle` and take a screenshot 2. Export menu works 3. focus any other window 4. Now the Export menu won't shop up anymore OBSERVED RESULT Clicking the Export button does nothing EXPECTED RESULT Export context menu should open SOFTWARE/OS VERSIONS Windows: 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.
[kmymoney] [Bug 392684] New: Unable to remove Payee from transactions
https://bugs.kde.org/show_bug.cgi?id=392684 Bug ID: 392684 Summary: Unable to remove Payee from transactions Product: kmymoney Version: 5.0.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: account-...@marvindickhaus.de Target Milestone: --- Steps to reproduce 1. Open a ledger 2. Select a transaction for editing 3. Try to remove a wrongfully guessed payee in the "Pay To"/"From" field and leave it empty Expected outcome No payee is present in the "Pay To"/"From" field Actual outcome The previously removed payee is still present in the "Pay To"/"From" field. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 382586] New: Changing Year of Budget possible in Grid, but not accepted
https://bugs.kde.org/show_bug.cgi?id=382586 Bug ID: 382586 Summary: Changing Year of Budget possible in Grid, but not accepted Product: kmymoney4 Version: 4.8.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: bugtracker Assignee: kmymoney-de...@kde.org Reporter: m...@marvindickhaus.de Target Milestone: --- When I create a new budget, I'm able to rename it, and change the year in the grid. Renaming works as expected, but the new year won't stick. When I change tabs the year resets to the current fiscal year. When I right-click on the budget I can select to change the year of the budget, which works as expected. I suppose it shouldn't be possible at all to change the year in the grid, but only using the selector. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 368770] Kate uses default Qt File Dialog *not KDE file dialog* which breaks tons of features, including KIO
https://bugs.kde.org/show_bug.cgi?id=368770 --- Comment #14 from Marvin Jens <mj...@mit.edu> --- Okay, I gave up and switched to KDE neon. Now everything is perfect. It seems one should currently regard kubuntu/backports as broken? Thanks for your time anyway... -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 368770] Kate uses default Qt File Dialog *not KDE file dialog* which breaks tons of features, including KIO
https://bugs.kde.org/show_bug.cgi?id=368770 --- Comment #13 from Marvin Jens <mj...@mit.edu> --- this is still not working. please let me know how I can help. Thx -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 248420] Transaction templates with formulae
https://bugs.kde.org/show_bug.cgi?id=248420 Marvin Dickhaus <m...@marvindickhaus.de> changed: What|Removed |Added CC||m...@marvindickhaus.de --- Comment #6 from Marvin Dickhaus <m...@marvindickhaus.de> --- I +1 the Credit Card management part in a first step. Having some kind of formulaes within the scheduled transactions would be great. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 368770] Kate uses default Qt File Dialog *not KDE file dialog* which breaks tons of features, including KIO
https://bugs.kde.org/show_bug.cgi?id=368770 --- Comment #12 from Marvin Jens <mj...@mit.edu> --- But since there seems to be a lot of magic happening at runtime with Qt and the FileDialog, I am not even sure the problem is with kate itself (or its source code). However, I have no clue how to dissect this issue. The mechanisms under the hood are somewhat opaque to me. :( -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 368770] Kate uses default Qt File Dialog *not KDE file dialog* which breaks tons of features, including KIO
https://bugs.kde.org/show_bug.cgi?id=368770 --- Comment #11 from Marvin Jens <mj...@mit.edu> --- Yes, I am also on 64Bit kubuntu. But my kate is from the backports repo, not from source. Do you get the same plugins loaded as I do? Can I uninstall kate/backports and compile it from source easily? Is there a howto somewhere? I guess I'd need a lot of qt-dev and kde-dev packages, but I could try. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 368770] Kate uses default Qt File Dialog *not KDE file dialog* which breaks tons of features, including KIO
https://bugs.kde.org/show_bug.cgi?id=368770 --- Comment #9 from Marvin Jens <mj...@mit.edu> --- please let me know if there is anything I can do to provide useful debug output. This bug is really haunting me every day! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 368770] Kate uses default Qt File Dialog *not KDE file dialog* which breaks tons of features, including KIO
https://bugs.kde.org/show_bug.cgi?id=368770 Marvin Jens <mj...@mit.edu> changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #8 from Marvin Jens <mj...@mit.edu> --- all version info and an attempt of debugging the loaded Qt plugins have been added -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 368770] Kate uses default Qt File Dialog *not KDE file dialog* which breaks tons of features, including KIO
https://bugs.kde.org/show_bug.cgi?id=368770 --- Comment #7 from Marvin Jens <mj...@mit.edu> --- I ran kate (file->open), which shows the Qt File Dialog, and gwenview (file->open), which shows the KDE File Dialog, from command line after setting QT_DEBUG_PLUGINS=1. They both load KdePlatformThemePlugin (if that's the one I should be looking for?) grep className ~/kate_QT_DEBUG_PLUGINS.log | sort | uniq "className": "AppMenuPlatformThemePlugin", "className": "CloseExceptPluginFactory", "className": "EPSPlugin", "className": "EXRPlugin", "className": "KateBtBrowserFactory", "className": "KateBuildPluginFactory", "className": "KateCTagsPluginFactory", "className": "KateFileBrowserPluginFactory", "className": "KateFileTreeFactory", "className": "KateKonsolePluginFactory", "className": "KateOpenHeaderFactory", "className": "KatePluginGDBFactory", "className": "KatePluginSearchFactory", "className": "KatePluginSymbolViewerFactory", "className": "KateProjectPluginFactory", "className": "KateReplicodePluginFactory", "className": "KateSnippetsPluginFactory", "className": "KateSQLFactory", "className": "KdePlatformThemePlugin", "className": "KonsolePartFactory", "className": "KraPlugin", "className": "KTERustCompletionPluginFactory", "className": "KWaylandPlugin", "className": "LumenPluginFactory", "className": "OraPlugin", "className": "PCXPlugin", "className": "PluginKateXMLToolsFactory", "className": "PSDPlugin", "className": "QComposePlatformInputContextPlugin", "className": "QDDSPlugin", "className": "QEglFSIntegrationPlugin", "className": "QGifPlugin", "className": "QIbusPlatformInputContextPlugin", "className": "QICNSPlugin", "className": "QICOPlugin", "className": "QJp2Plugin", "className": "QJpegPlugin", "className": "QLinuxFbIntegrationPlugin", "className": "QMinimalEglIntegrationPlugin", "className": "QMinimalIntegrationPlugin", "className": "QMngPlugin", "className": "QOffscreenIntegrationPlugin", "className": "QSvgIconPlugin", "className": "QSvgPlugin", "className": "QTgaPlugin", "className": "QTiffPlugin", "className": "QWaylandIntegrationPlugin", "className": "QWbmpPlugin", "className": "QWebpPlugin", "className": "QXcbEglIntegrationPlugin", "className": "QXcbGlxIntegrationPlugin", "className": "QXcbIntegrationPlugin", "className": "RASPlugin", "className": "RGBPlugin", "className": "SoftimagePICPlugin", "className": "StylePlugin", "className": "TabSwitcherPluginFactory", "className": "TextFilterPluginFactory", "className": "TGAPlugin", "className": "WaylandPlugin", "className": "X11Plugin", "className": "XCFPlugin", grep className ~/gwenview_QT_DEBUG_PLUGINS.log | sort | uniq "className": "AppMenuPlatformThemePlugin", "className": "EPSPlugin", "className": "EXRPlugin", "className": "KdePlatformThemePlugin", "className": "KIOPluginForMetaData", "className": "KraPlugin", "className": "OraPlugin", "className": "PCXPlugin", "className": "PSDPlugin", "className": "QComposePlatformInputContextPlugin", "className": "QDDSPlugin", "className": "QEglFSIntegrationPlugin", "className": "QGifPlugin", "className": "QIbusPlatformInputContextPlugin", "className": "QICNSPlugin", "className": "QICOPlugin", "className": "QJp2Plugin", "className": "QJpegPlugin", "className": "QLinuxFbIntegrationPlugin", "className": "QMinimalEglIntegrationPlugin", "className": "QMinimalIntegrationPlugin", "className": "QMngPlugin", "className": "QOffscreenIntegrationPlugin", "className": "QSvgIconPlugin", "className": "QSvgPlugin", "className": "QTgaPlugin", "className": "QTiffPlugin", "className": "QWaylandIntegrationPlugin", "className": "QWbmpPlugin", "className": "QWebpPlugin", "className": "QXcbEglIntegrationPlugin", "className": "QXcbGlxIntegrationPlugin", "className": "QXcbIntegrationPlugin", "className": "RASPlugin", "className": "RGBPlugin", "className": "SoftimagePICPlugin", "className": "StylePlugin", "className": "TGAPlugin", "className": "XCFPlugin", -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 368770] Kate uses default Qt File Dialog *not KDE file dialog* which breaks tons of features, including KIO
https://bugs.kde.org/show_bug.cgi?id=368770 --- Comment #6 from Marvin Jens <mj...@mit.edu> --- Created attachment 101105 --> https://bugs.kde.org/attachment.cgi?id=101105=edit full stderr output after running gwenview with QT_DEBUG_PLUGINS=1 export QT_DEBUG_PLUGINS=1 gwenview 2> ~/gwenview_QT_DEBUG_PLUGINS.log -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 368770] Kate uses default Qt File Dialog *not KDE file dialog* which breaks tons of features, including KIO
https://bugs.kde.org/show_bug.cgi?id=368770 --- Comment #5 from Marvin Jens <mj...@mit.edu> --- Created attachment 101104 --> https://bugs.kde.org/attachment.cgi?id=101104=edit full stderr output after running kate with QT_DEBUG_PLUGINS=1 export QT_DEBUG_PLUGINS=1 kate 2> ~/kate_QT_DEBUG_PLUGINS.log -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 368770] Kate uses default Qt File Dialog *not KDE file dialog* which breaks tons of features, including KIO
https://bugs.kde.org/show_bug.cgi?id=368770 --- Comment #4 from Marvin Jens <mj...@mit.edu> --- Running Plasma desktop (5.6.5) here. Refraining from re-installing neon, though. I'd prefer staying on LTS. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 368770] New: Kate uses default Qt File Dialog *not KDE file dialog* which breaks tons of features, including KIO
https://bugs.kde.org/show_bug.cgi?id=368770 Bug ID: 368770 Summary: Kate uses default Qt File Dialog *not KDE file dialog* which breaks tons of features, including KIO Product: kate Version: 16.04.1 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: mj...@mit.edu packages from kubuntu 16.04.1 with backports Kate version 15.12.3 KDE Frameworks 5.23.0 Qt 5.5.1 (built against 5.5.1) Since upgrading KDE to KDE5 from kubuntu/backports a major showstopper was introduced. The File open/save dialogs are no longer the KDE dialogs but the ultra-simplistic standard QtFileDialog. This means: * no KIO/remote files * no copy or typing of a URL * no "places" * I was so far completely unable to debug the issue as I am not on top of all the Qt5/KDE framworks-plugin mechanism. But I am very willing to help track this down if I can get some help! Kwrite shows the same behaviour, while (strangely) Gwenview opens the proper KDE dialog. Please let me know how I can help! Reproducible: Always Steps to Reproduce: 1. open kate 2. click file-> open 3. Actual Results: Shows simplistic Qt File Dialog Expected Results: Shows KDE File Dialog with all bells and whistles Also happens with a newly created user account (so no stale KDE config files from before the move to KDE5) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 363887] New: Mouse hover notifications are yellow background with white font, completely unreadable. Can not find option to configure this.
https://bugs.kde.org/show_bug.cgi?id=363887 Bug ID: 363887 Summary: Mouse hover notifications are yellow background with white font, completely unreadable. Can not find option to configure this. Product: digikam Version: unspecified Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: digikam-de...@kde.org Reporter: marvin.zimmer...@gmx.net Neither handbook nor online help contain information on configuring notification popups. Using: Linux 3.16.0-4-amd64 x86_64 Debian Digikam Version 4.4.0 using KDE Development Platform 4.14.2 Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
