[kde] [Bug 483670] New: Using the shortcut to change keyboard layout loses focus of the current window
https://bugs.kde.org/show_bug.cgi?id=483670 Bug ID: 483670 Summary: Using the shortcut to change keyboard layout loses focus of the current window Classification: I don't know Product: kde Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bgu...@gmail.com Target Milestone: --- SUMMARY When typing in an input and then pressing the shortcut to switch keyboard language, the window will lose focus. STEPS TO REPRODUCE 1. Setup two keyboard layout with a shortcut to switch between layout 2. Start typing in an input 3. Press the shortcut to switch between layout OBSERVED RESULT The window and input will lose focus, and you have to click it again to resume typing EXPECTED RESULT The window and input stays focused, and you can keep typing with the new keyboard layout SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.7.9-arch1-1 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 501552] New: Video thumbnails are broken
https://bugs.kde.org/show_bug.cgi?id=501552 Bug ID: 501552 Summary: Video thumbnails are broken Classification: Applications Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: pinchon.guilla...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When viewing video files in Dolphin, thumbnails are broken. Tested with OpenSUSE SlowRoll and Fedora 41. The Flatpak version works (but seems abandonned) if that helps... When running Dolphin through the console, I get the following errors when hovering over a video file. > [swscaler @ 0x557cca67cf40] bad src image pointers > kf.kio.core.connection: Socket not connected QLocalSocket::PeerClosedError > kf.kio.core: An error occurred during write. The worker terminates now. > QThreadStorage: Thread 0x557cc9564010 exited after QThreadStorage 2 destroyed > QThreadStorage: Thread 0x557cc9564010 exited after QThreadStorage 1 destroyed STEPS TO REPRODUCE 1. Open Dolphin 2. Navigate to a folder containing video files OBSERVED RESULT When hovering over video files the thumbnails are scrambled. Side panel video preview is blank. EXPECTED RESULT Video thumbnails should be displayed and cycle through video preview when hovered. The side panel should allow to play the video preview. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 41 KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.2 Kernel Version: 6.13.6-200.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840HS with Radeon 780M Graphics Memory: 27.1 Gio of RAM Graphics Processor: AMD Radeon 780M Manufacturer: LENOVO Product Name: 82Y8 System Version: Yoga Pro 7 14APH8 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 501552] Video thumbnails are broken
https://bugs.kde.org/show_bug.cgi?id=501552 Guillaume changed: What|Removed |Added Platform|Other |Fedora RPMs Component|panels: folders |general Version|unspecified |24.12.3 -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 421457] Browser Integration won't work through Firefox Flatpak
https://bugs.kde.org/show_bug.cgi?id=421457 Guillaume changed: What|Removed |Added Resolution|UPSTREAM|--- CC||pinchon.guilla...@gmail.com Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #4 from Guillaume --- Is there any news on this issue ? This is still an issue in 2025 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372220] New: Usage of a template aliases are not hightlighted
https://bugs.kde.org/show_bug.cgi?id=372220 Bug ID: 372220 Summary: Usage of a template aliases are not hightlighted Product: kdevelop Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: gufi...@gmail.com Target Milestone: --- Kdevelop seems to ignore highlighting and inspecting usage of template alisases. Here's a minimal code to reproduce the error. template using my_vec = std::vector; my_vec doStuff(); Inside the using declaration, my_vec is highlighted properly, but not when it is used (eg. in the function declaration) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449918] New: plasma-workspace-5.24.0 sets Xft.dpi to 0 in Xresources
https://bugs.kde.org/show_bug.cgi?id=449918 Bug ID: 449918 Summary: plasma-workspace-5.24.0 sets Xft.dpi to 0 in Xresources Product: plasmashell Version: 5.24.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: casta+...@xwing.info CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Since upgrade to plasma-workspace-5.24.0, my plasma X11 session opens with Xft.dpi: 0. This messes especially webkit-gtk applications (in my case, Evolution mail, but tested epiphany browser too). I see there was change in this area, especially https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1012/diffs#96a3553f6e69e17f575e2ced2f36e16c755d5e6a_0_22 If I’m not mistaken, if fontDpiKey is present, it’s value is dumped to xrdb, even if it’s 0? In my case, it’s present in configuration (forcing dpi is disabled in fonts kcm) and the value is 0 indeed in configuration file. xrdb right after opening session: $ xrdb -query Xcursor.size: 24 Xcursor.theme: breeze_cursors Xft.antialias: 1 Xft.dpi:0 Xft.hinting:1 Xft.hintstyle: hintslight Xft.rgba: rgb kcm font config file: $ cat .config/kcmfonts [General] dontChangeAASettings=true forceFontDPI=0 STEPS TO REPRODUCE 1. upgrade to plasma-wokspace-5.24.0 2. restart session 3. OBSERVED RESULT Xft.dpi is set to 0 EXPECTED RESULT Xft.dpi should not be set in my case (I have no scaling) just like it was before SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo linux (available in About System) KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 450541] New: [event summary] The value associated to the "Calendar :" field is prefixed arbitrarily.
https://bugs.kde.org/show_bug.cgi?id=450541
Bug ID: 450541
Summary: [event summary] The value associated to the "Calendar
:" field is prefixed arbitrarily.
Product: korganizer
Version: 5.19.1
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: otherviews
Assignee: kdepim-b...@kde.org
Reporter: guillaume.l...@illoc.net
Target Milestone: ---
SUMMARY
In the event summary in the main window, the calendar name is always
automatically altered. If the calendar is named "foo", the summary displays
"Calendar: My foo", i.e., the calendar name is prefixed with "My".
(see for instance https://cdn.kde.org/screenshots/korganizer/korganizer.png)
=> This is forced on the user.
=> This brings no readability improvement, and easily breaks (for instance if
naming a calendar after one's child).
=> It is even worse in languages where there is a pronominal distinction
between singular and plural or between genders. For instance in French ("My" =>
"Mon / Ma / Mes") and German ("My" => "Mein / Meine"). That is borderline
unreadable.
STEPS TO REPRODUCE
1. Create any event in the "foo" calendar.
2. Select it.
OBSERVED RESULT
"Calendar: My foo"
EXPECTED RESULT
"Calendar: foo"
SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 449709] Print Color Mode: not possible to print in black-white
https://bugs.kde.org/show_bug.cgi?id=449709 Guillaume Zin changed: What|Removed |Added CC||guillaume@gmail.com --- Comment #4 from Guillaume Zin --- Created attachment 156547 --> https://bugs.kde.org/attachment.cgi?id=156547&action=edit Print to PDF as grayscale I confirm this bug for: - Okular 22.08.3 - KDE Frameworks 5.102.0 - Qt 5.15.6 When "Mono" printing is selected via the "Properties" printer configuration dialog, output is in color anyways (Brother printer). The bug is present if you print to a PDF file too and you select grayscale in "Options", cf. OkularPrintPdfGrayscale.png attached file. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 464590] kded5 crashes in KScreen::Config::setOutputPriority() after monitor wakes from sleep
https://bugs.kde.org/show_bug.cgi?id=464590 --- Comment #10 from Guillaume Castagnino --- Indeed, looking at git history, it seems it missed 5.27 and is for 5.27.1. I had to patch manually over 5.27. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466095] Plasma crashes in DesktopView::screenToFollow() on screen wake up when KScreen service is active and high refresh rate monitor is connected and AdaptivSync is enabled
https://bugs.kde.org/show_bug.cgi?id=466095 Guillaume Castagnino changed: What|Removed |Added CC||casta+...@xwing.info --- Comment #13 from Guillaume Castagnino --- Hi, I have the same backtrace with a quite different use case. using x11, not wayland, and one standard low frequency monitor (60Hz) connected through mDP and a videoprojector connected through HDMI. Operating System: Gentoo Linux 2.13 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.8-gentoo (64-bit) Graphics Platform: X11 Processors: 12 × 12th Gen Intel® Core™ i5-12500 Memory: 31.1 Gio of RAM Graphics Processor: Mesa Intel® UHD Graphics 770 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B660I AORUS PRO DDR4 System Version: -CF Monitors: 2 0: +*DP-1 2560/597x1440/336+0+0 DP-1 1: +HDMI-1 1920/508x1080/286+2560+0 HDMI-1 Use case, quite simple: - Start the HDMI video projector - shut-down the main DP screen - put back the main DP screen on - plasmashell crashes Nota: it seems that I get this crash only since my main screen is using DP (it was before connected through HDMI too, without issues). But this assumption is just a guess, since I cannot connect it any more using HDMI (motherboard changed) The backtrace follows -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466095] Plasma crashes in DesktopView::screenToFollow() on screen wake up when KScreen service is active and high refresh rate monitor is connected and AdaptivSync is enabled
https://bugs.kde.org/show_bug.cgi?id=466095 --- Comment #14 from Guillaume Castagnino --- Created attachment 157561 --> https://bugs.kde.org/attachment.cgi?id=157561&action=edit plasmashell backtrace -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466095] Plasma crashes in DesktopView::screenToFollow() on screen wake up when KScreen service is active and high refresh rate monitor is connected and AdaptivSync is enabled
https://bugs.kde.org/show_bug.cgi?id=466095 --- Comment #15 from Guillaume Castagnino --- And for completeness, no crash if plasmashell is built with -DNDEBUG, so this a workaround. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 459670] Cursor theme changes to Adwaita when interacting with GTK applications
https://bugs.kde.org/show_bug.cgi?id=459670 Guillaume Castagnino changed: What|Removed |Added CC||casta+...@xwing.info -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 468069] New: broken kwallet auto-openning with SDDM autologin
https://bugs.kde.org/show_bug.cgi?id=468069 Bug ID: 468069 Summary: broken kwallet auto-openning with SDDM autologin Classification: Frameworks and Libraries Product: kwallet-pam Version: git-stable-Plasma/5.27 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: casta+...@xwing.info Target Milestone: --- SUMMARY Here is the use case. I know it’s not secure at all, but it’s for my elders, not familiar with computer sciences… - The system is « single-user » - kwallet is setup without password (because of next point) - sddm is set to autologin, so PAM is not fed with credentials - kwallet-pam is auto-opening the wallet at login. This was working because the wallet has no password. This commit: https://invent.kde.org/plasma/kwallet-pam/-/merge_requests/12/diffs?commit_id=09659874cc6cc3ab21314dc3b24a2db1bc77c46c or it’s cherry-pick on 5.27 branch: https://invent.kde.org/plasma/kwallet-pam/-/commit/d1910a2280d0394525bed903af16db4bd238e3e7 breaks my use case. It prevents opening the wallet without password. Even if not secure, this use case seems legitimate to me. So for me, this commit should be reverted. Thank’s! Operating System: Gentoo Linux 2.13 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.8-gentoo (64-bit) Graphics Platform: X11 Processors: 12 × 12th Gen Intel® Core™ i5-12500 Memory: 31.1 Gio of RAM Graphics Processor: Mesa Intel® UHD Graphics 770 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B660I AORUS PRO DDR4 System Version: -CF -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 468098] New: Function ''Mean'' does not function (in SpreadSheet) with numbers of more 5 figures
https://bugs.kde.org/show_bug.cgi?id=468098 Bug ID: 468098 Summary: Function ''Mean'' does not function (in SpreadSheet) with numbers of more 5 figures Classification: Applications Product: LabPlot2 Version: 2.10.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.se...@web.de Reporter: guellis_1...@hotmail.com Target Milestone: --- Created attachment 157803 --> https://bugs.kde.org/attachment.cgi?id=157803&action=edit PrintScreen 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. Function ''Mean'' does not function (in SpreadSheet) with numbers of more 5 figures 2. ex. 15000, 14000, 13000 3. OBSERVED RESULT Does not function. EXPECTED RESULT Does not function. SOFTWARE/OS VERSIONS Windows: 10 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.
[plasmashell] [Bug 468430] Plasmashell X11 crashes in DesktopView::screenToFollow() when removing a screen from a multimonitor setup
https://bugs.kde.org/show_bug.cgi?id=468430 Guillaume Castagnino changed: What|Removed |Added CC||casta+...@xwing.info -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468430] Plasmashell X11 crashes in DesktopView::screenToFollow() when adding or removing a screen from a multimonitor setup
https://bugs.kde.org/show_bug.cgi?id=468430 --- Comment #9 from Guillaume Castagnino --- Confirmed fixed for me with both https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2841 AND https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2842 The first MR made the initial backtrace disappear, but there was a second one behind, fixed by the second MR. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470661] New: [aarch64] plasmashell crashes on 1st start on aarch64
https://bugs.kde.org/show_bug.cgi?id=470661 Bug ID: 470661 Summary: [aarch64] plasmashell crashes on 1st start on aarch64 Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: guillaume.gar...@free.fr Target Milestone: 1.0 Reported first on openSUSE bugzilla: https://bugzilla.opensuse.org/show_bug.cgi?id=1211628 I bring this bug upstream to reach people knowing more on plasma. SUMMARY plasmashell crashes on 1st start on (unreleased) openSUSE Tumbleweed aarch64 with the following trace from coredumpctl gdb. #0 0x98f66618 in __pthread_kill_implementation () from /lib64/libc.so.6 #1 0x98f1e8c0 in raise () from /lib64/libc.so.6 #2 0x9b8e79d8 in KCrash::defaultCrashHandler(int) () from /lib64/libKF5Crash.so.5 #3 #4 0x98f66618 in __pthread_kill_implementation () from /lib64/libc.so.6 #5 0x98f1e8c0 in raise () from /lib64/libc.so.6 #6 #7 0x98fc6090 in poll () from /lib64/libc.so.6 #8 0x97c125b0 in ?? () from /lib64/libglib-2.0.so.0 #9 0x97c126e8 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #10 0x9963f968 in QEventDispatcherGlib::processEvents (this=0x5b70, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #11 0x995d4a30 in QEventLoop::exec (this=this@entry=0x7c94e658, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #12 0x993cb3d0 in QThread::exec (this=this@entry=0xf56b5f10) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #13 0x9af60554 in QQmlThreadPrivate::run (this=0xf56b5f10) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.9+kde25/src/qml/qml/ftw/qqmlthread.cpp:155 #14 0x993ccba4 in operator() (__closure=) at thread/qthread_unix.cpp:350 #15 (anonymous namespace)::terminate_on_exception > (t=...) at thread/qthread_unix.cpp:287 #16 QThreadPrivate::start (arg=0xf56b5f10) at thread/qthread_unix.cpp:310 #17 0x98f649e4 in start_thread () from /lib64/libc.so.6 #18 0x98fd085c in thread_start () from /lib64/libc.so.6 After this crash, plasmashell is reloaded automatically, but part of the default openSUSE theme is not applied, namely the bottom bar which is missing icons/applets and is smaller than expected. This started zhen ze updated from 5.27.4 to 5.27.5 and it happens in X11 only. STEPS TO REPRODUCE Install unreleased openSUSE Tumbleweed for aarch64. X11 only. OBSERVED RESULT Theme is not applied properly and we get traces in journal. EXPECTED RESULT Theme should be applied properly and no crash should happen. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470661] [aarch64] plasmashell crashes on 1st start on aarch64
https://bugs.kde.org/show_bug.cgi?id=470661 --- Comment #2 from Guillaume GARDET --- (In reply to Nate Graham from comment #1) > Backtrace does not contain any evidence of KDE code. Possibly a Qt issue or > a setup/packaging issue. You said you're using "(unreleased) openSUSE > Tumbleweed aarch64"; can you describe the hardware and software setup a bit > more? The problem is under qemu. The screenshot showing the issue can be seen here: https://openqa.opensuse.org/tests/3337754#step/opensuse_welcome/4 and can be compared to https://openqa.opensuse.org/tests/3279201#step/opensuse_welcome/4 I wrote unreleased, because QA is blocking the updates delivered to users due to this bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470661] [aarch64] plasmashell crashes on 1st start on aarch64
https://bugs.kde.org/show_bug.cgi?id=470661 --- Comment #3 from Guillaume GARDET --- And the journal shows: May 23 02:13:20.779784 ip-10-0-2-15.eu-west-1.compute.internal plasmashell[1539]: 25 -- exe=/usr/bin/plasmashell May 23 02:13:20.790901 ip-10-0-2-15.eu-west-1.compute.internal plasmashell[1539]: 13 -- platform=xcb May 23 02:13:20.791043 ip-10-0-2-15.eu-west-1.compute.internal plasmashell[1539]: 11 -- display=:0 May 23 02:13:20.791106 ip-10-0-2-15.eu-west-1.compute.internal plasmashell[1539]: 20 -- appname=plasmashell May 23 02:13:20.791166 ip-10-0-2-15.eu-west-1.compute.internal plasmashell[1539]: 17 -- apppath=/usr/bin May 23 02:13:20.791216 ip-10-0-2-15.eu-west-1.compute.internal plasmashell[1539]: 10 -- signal=11 May 23 02:13:20.791279 ip-10-0-2-15.eu-west-1.compute.internal plasmashell[1539]: 9 -- pid=1539 May 23 02:13:20.791336 ip-10-0-2-15.eu-west-1.compute.internal plasmashell[1539]: 18 -- appversion=5.27.5 May 23 02:13:20.791394 ip-10-0-2-15.eu-west-1.compute.internal plasmashell[1539]: 19 -- programname=Plasma May 23 02:13:20.791450 ip-10-0-2-15.eu-west-1.compute.internal plasmashell[1539]: 31 -- bugaddress=sub...@bugs.kde.org May 23 02:13:20.791511 ip-10-0-2-15.eu-west-1.compute.internal plasmashell[1539]: KCrash: Application 'plasmashell' crashing... May 23 02:13:20.826815 ip-10-0-2-15.eu-west-1.compute.internal plasmashell[1539]: KCrash: Attempting to start /usr/libexec/drkonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470661] [aarch64] plasmashell crashes on 1st start on aarch64
https://bugs.kde.org/show_bug.cgi?id=470661 Guillaume GARDET changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #5 from Guillaume GARDET --- So, this is this Qt issue: https://bugreports.qt.io/browse/QTBUG-111935 And the (tested) fix is: https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=15ec024152a1d1d99a4934f7b2408e7af7b2552a Which should have been pushed to 5.15 branch, but is not in yet apparently. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470990] New: Dolphin information panel not displaying preview properly
https://bugs.kde.org/show_bug.cgi?id=470990 Bug ID: 470990 Summary: Dolphin information panel not displaying preview properly Classification: Applications Product: dolphin Version: 21.12.3 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: information Assignee: dolphin-bugs-n...@kde.org Reporter: p...@imc.lc CC: kfm-de...@kde.org Target Milestone: --- Created attachment 159640 --> https://bugs.kde.org/attachment.cgi?id=159640&action=edit Shows the Dolphin window with preview of a pdf document SUMMARY Since upgrading to Kubuntu 22.04, I have previews in the Dolphin information panel like I used to, but the image resolution is poor. I used to be able to read the contents of a pdf file preview, so I did not have to open the file, which was great when searching several documents. This is no longer possible. The preview image is smaller than before and it looks like there is no way to increase the size. Photos shot in high resolution display clearly, so it seems like this is a problem with displaying text in a pdf or plain text file. I'm attaching a screenshot which hopefully should illustrate the problem. I'm not sure how to attach a second screenshot, but I also have one showing the same Dolphin window, showing preview display of a photo, which fills more of the information pane with a clear preview. Please let me know if there is any information I can share that will help solve the problem. STEPS TO REPRODUCE Select a pdf or text file in the dolphin window. OBSERVED RESULT The information panel does not use all of the space available to display a preview, and the image resolution in the panel is low, so text is not easy to read EXPECTED RESULT Previously I was able to read text in the preview of a pdf file, which made it easy to choose the correct file from a folder by viewing the preview instead of opening the file to check it's contents. SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-73-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz Memory: 23.1 GiB of RAM Graphics Processor: Mesa Intel® Iris® Plus Graphics ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470990] Dolphin information panel not displaying preview properly
https://bugs.kde.org/show_bug.cgi?id=470990 Paul Guillaume changed: What|Removed |Added CC||p...@imc.lc -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 457793] Powerdevil restart loop on startup on kernels 5.18+
https://bugs.kde.org/show_bug.cgi?id=457793 Guillaume Ausset changed: What|Removed |Added CC||guillaume+...@ausset.me --- Comment #3 from Guillaume Ausset --- I can confirm I encounter the same bug with a caveat: only on my laptop. Desktop is fine. On the laptop the problem doesn't manifest if I'm hooked to a dock. I checked that it's not due to power/no-power by using a charger. It seems, interestingly, that powerdevil goes in a restart loop if I don't have networking via ethernet. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 459670] Cursor theme changes to Adwaita when interacting with GTK applications
https://bugs.kde.org/show_bug.cgi?id=459670 --- Comment #4 from Guillaume Castagnino --- (In reply to jamesxmcintosh from comment #2) > (In reply to Paul from comment #1) > > Does anyone have a workable temporary fix for this until the issue is > > resolved? > > Try editing/creating: /usr/share/icons/default/index.theme > > Add this: > [Icon Theme] > Inherits=Oxygen_White Indeed, this workaround is working. Thank’s a lot. It looks like it’s a recent regression since very few times. Maybe since kde frameworks 5.98. But not really sure about this. This is my best guess considering my upgrade history Currently still having the issue with: Operating System: Gentoo Linux 2.9 KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.5 Kernel Version: 6.0.2-gentoo (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463024] Plasma doesn't respect Sub-pixel rendering for system tray and desktop
https://bugs.kde.org/show_bug.cgi?id=463024 Guillaume Castagnino changed: What|Removed |Added CC||casta+...@xwing.info -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 464590] kded5 crashes in KScreen::Config::setOutputPriority() after monitor wakes from sleep
https://bugs.kde.org/show_bug.cgi?id=464590 Guillaume Castagnino changed: What|Removed |Added CC||casta+...@xwing.info -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 464590] kded5 crashes in KScreen::Config::setOutputPriority() after monitor wakes from sleep
https://bugs.kde.org/show_bug.cgi?id=464590 --- Comment #1 from Guillaume Castagnino --- I can report the same crash here with kf 5.102 and plasma 5.26.90. The crash did not occur with plasma 5.26.5 Only one monitor connected using DP, the crash can be triggered simply by powering off/on the monitor. It seems to crash when powering back on the screen. I did not manage to get a stacktrace yet. Nothing special in log files when powering on the screen as you can see: janv. 29 11:11:26 dagobah kded5[836]: colord: Setting X atom (id: 0 ) "_ICC_PROFILE" on output: "DP-1" janv. 29 11:11:26 dagobah dbus-daemon[539]: [session uid=1000 pid=539] Activating via systemd: service name='org.kde.kscreen.osdService' unit='plasma-kscreen-osd.service' requested by ':1.12' (uid=1000 pid=836 comm="/usr/bin/kded5") janv. 29 11:11:26 dagobah systemd[504]: Starting plasma-kscreen-osd.service... janv. 29 11:11:26 dagobah dbus-daemon[539]: [session uid=1000 pid=539] Successfully activated service 'org.kde.kscreen.osdService' janv. 29 11:11:26 dagobah systemd[504]: Started plasma-kscreen-osd.service. janv. 29 11:11:27 dagobah kscreen_backend_launcher[1037]: kscreen.xrandr: Emitting configChanged() janv. 29 11:11:27 dagobah kded5[836]: KCrash: Attempting to start /usr/bin/kded5 janv. 29 11:11:27 dagobah kded5[836]: KCrash: crashing... crashRecursionCounter = 2 janv. 29 11:11:27 dagobah kded5[836]: KCrash: Application Name = kded5 path = /usr/bin pid = 836 janv. 29 11:11:27 dagobah kded5[836]: KCrash: Arguments: /usr/bin/kded5 janv. 29 11:11:27 dagobah ksmserver[1330]: 11:11:27.832 WARN unknown env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP janv. 29 11:11:27 dagobah keepassxc[1023]: kf.notifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP janv. 29 11:11:27 dagobah fookb[1154]: kf.notifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP janv. 29 11:11:27 dagobah systemd[504]: plasma-kded.service: Main process exited, code=dumped, status=11/SEGV janv. 29 11:11:27 dagobah systemd[504]: plasma-kded.service: Failed with result 'core-dump'. janv. 29 11:11:36 dagobah plasmashell[898]: trying to show an empty dialog -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 464590] kded5 crashes in KScreen::Config::setOutputPriority() after monitor wakes from sleep
https://bugs.kde.org/show_bug.cgi?id=464590 --- Comment #2 from Guillaume Castagnino --- Created attachment 155820 --> https://bugs.kde.org/attachment.cgi?id=155820&action=edit libkscreen-crash.patch This is probably not the correct fix, but this small patch in libkscreen fixes the issue for me. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 464590] kded5 crashes in KScreen::Config::setOutputPriority() after monitor wakes from sleep
https://bugs.kde.org/show_bug.cgi?id=464590 --- Comment #4 from Guillaume Castagnino --- (In reply to Fushan Wen from comment #3) > The patch looks sane, would you like to create a merge request? Honestly, I do not think that’s the correct fix. It hides the crash, but I assume there is some flaw before this somewhere in the logic. In this case, we may fall under the case where the monitor is already primary but still disabled (here: https://invent.kde.org/plasma/libkscreen/-/blob/master/src/setconfigoperation.cpp#L175) . But is this not a race condition? Shouldn’t the screen be already woken-up when entering this code? With my patch, you may end with no primary at all, or multiple primary when exiting fixPrimaryOutput(). So I think there is something better to do than this patch that is just hiding things. The only purpose of this patch was in fact to narrow down the crash location and workaround until we get a proper fix :) -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 486771] Extremely slow UI with some driver/compositor combinations
https://bugs.kde.org/show_bug.cgi?id=486771 Guillaume Castagnino changed: What|Removed |Added CC||casta+...@xwing.info --- Comment #5 from Guillaume Castagnino --- I can report the same issue here. I never take time to report it, but I have the problem since the first time I use skanpage (23.04, 23.08, 24.05). UI is damn slow for every action, but scan speed is not affected. It’s a pain to select a scan zone, or even to save the document. skanlite is NOT affected on the same machine. Setup: - Plasma 5 under X11 (for the oldest versions) - Plasma 6 under X11 or wayland - Scanner : Canon LIDE 400 (PIXMA backend too, USB only) - Computer is a recent intel-based iGPU (i5-12500) -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 486771] Extremely slow UI with some driver/compositor combinations
https://bugs.kde.org/show_bug.cgi?id=486771 --- Comment #6 from Guillaume Castagnino --- Using strace I saw suspicious USBDEVFS_REAPURBNDELAY ioctl loops even while not using the scanner, only browsing the interface. So I check ksanecore and guess what: the bad behaviour is fixed by : https://invent.kde.org/libraries/ksanecore/-/merge_requests/19 The MR speak about *remote* PIXMA scanner, but this bug can be definitively linked, even for local USB PIXMA scanner :) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 473127] Discover should prefer the backend for the installed version of an app when navigating to its page
https://bugs.kde.org/show_bug.cgi?id=473127 Guillaume Zin changed: What|Removed |Added CC||guillaume@gmail.com --- Comment #2 from Guillaume Zin --- Hello, Kubuntu 24.04 with Plasma 5.27.11 here. I would like to add that sometimes it is strange: for instance I installed Floorp from their ppa. I installed Flatpak backend afterwards. Now Discover proposes to install Floorp as it was not installed, as described before. But for other applications, only Flatpak is proposed (Brave for instance), even if there is at lease a snap alternative. And for others (Falkon for instance), I can choose source from Flathub, Ubuntu or Snap... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445717] Overlapping notifications
https://bugs.kde.org/show_bug.cgi?id=445717 Guillaume Castagnino changed: What|Removed |Added CC||casta+...@xwing.info -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 446639] New: Breeze GTK: Regression in various GTK assets since commit c18f2a472a654b648fb9e056f4c7c66d5e1bf786
https://bugs.kde.org/show_bug.cgi?id=446639 Bug ID: 446639 Summary: Breeze GTK: Regression in various GTK assets since commit c18f2a472a654b648fb9e056f4c7c66d5e1bf786 Product: Breeze Version: 5.23.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: gtk theme Assignee: uhh...@gmail.com Reporter: casta+...@xwing.info CC: plasma-b...@kde.org Target Milestone: --- Created attachment 144321 --> https://bugs.kde.org/attachment.cgi?id=144321&action=edit 0001-gtk3-custom-GTK-properties-are-case-sensitive.patch GTK 3 specific CSS properties are case sensitive. Prettier in commit c18f2a472a654b648fb9e056f4c7c66d5e1bf786 made those properties lower case, thus breaking things. For example, scrollbars steppers. Find attached a patch to apply on top of breeze-gtk sources that fixes this issue (I wanted to open a MR, but I’m no allowed to do it) Thank’s! -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 446639] Breeze GTK: Regression in various GTK assets since commit c18f2a472a654b648fb9e056f4c7c66d5e1bf786
https://bugs.kde.org/show_bug.cgi?id=446639 --- Comment #2 from Guillaume Castagnino --- Ok I did not see the fork button, and my MR by mail was rejected. Should be ok now: https://invent.kde.org/plasma/breeze-gtk/-/merge_requests/34 -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 452800] New: Ability to set manual snapshots from signal
https://bugs.kde.org/show_bug.cgi?id=452800 Bug ID: 452800 Summary: Ability to set manual snapshots from signal Product: Heaptrack Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: m...@milianw.de Reporter: gdesm...@gnome.org Target Milestone: --- The DATA segment of my application keeps growing when I do some tasks. Ideally I'd like to be able to do something like this to help me debug it: - Send a signal (such as `SIGUSR1`) to trigger a snapshot from heaptrack. - Interact with my app to reproduce the problem. - Send another signal to trigger a second snapshot. - Be able somehow to see the memory which have been allocated (and not freed) between these two snapshots. Does this make sense? I implemented something similar in GStreamer's leaks tracer (see https://gitlab.freedesktop.org/gstreamer/gstreamer/-/blob/main/subprojects/gstreamer/plugins/tracers/gstleaks.c#L810 ) and it's been quite useful. -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 452800] Ability to set manual snapshots from signal
https://bugs.kde.org/show_bug.cgi?id=452800 Guillaume Desmottes changed: What|Removed |Added CC||gdesm...@gnome.org -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 452800] Ability to set manual snapshots from signal
https://bugs.kde.org/show_bug.cgi?id=452800 --- Comment #2 from Guillaume Desmottes --- > heaptrack now allows filtering on the time axis of the charts. So is there a way to filter to only display the allocated and not freed memory in a specific time interval? I didn't find any way to do that in heaptrack_gui. > I think adding custom markers there to better allow figuring out where to > filter is a great idea! I'm not so fond though of writing to different files > or such to create different snapshots. Agreed, I think custom markers would be enough then. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 458595] New: VIM keybindings starting with numeric precursor should be implemented.
https://bugs.kde.org/show_bug.cgi?id=458595 Bug ID: 458595 Summary: VIM keybindings starting with numeric precursor should be implemented. Product: kdevelop Version: 5.8.220403 Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: All editors Assignee: kdevelop-bugs-n...@kde.org Reporter: guillaume.frogn...@laposte.net Target Milestone: --- SUMMARY VIM keybindings starting with numeric precursor should be implemented. For instance typing "3dd" do not delete 3 lines but only one. STEPS TO REPRODUCE 1. select vi input mode: Edit -> input modes -> vi-mode 2. type a command starting with a numeric precursor: for instance "2x" to delete two characters. OBSERVED RESULT The numeric precursor is ignored. For instance "2x" delete only one characters. EXPECTED RESULT The numeric precursor should not be ignored. For instance "2x" should delete two characters. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.15.60-1-MANJARO (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 458595] VIM keybindings starting with numeric precursor should be implemented.
https://bugs.kde.org/show_bug.cgi?id=458595 Guillaume Frognier changed: What|Removed |Added CC||guillaume.frognier@laposte. ||net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450119] Plasma slow/freezes on resume - possible memory leak?
https://bugs.kde.org/show_bug.cgi?id=450119 Guillaume Zin changed: What|Removed |Added CC||guillaume@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444385] Right-click on GTK icon in systray leads to fast random mouse clicks events
https://bugs.kde.org/show_bug.cgi?id=444385 Guillaume Castagnino changed: What|Removed |Added CC||casta+...@xwing.info -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 362493] quoting with blockquote
https://bugs.kde.org/show_bug.cgi?id=362493 Guillaume Castagnino changed: What|Removed |Added CC||casta+...@xwing.info -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 419978] KMail missing line break in blockquote when showing as HTML mail
https://bugs.kde.org/show_bug.cgi?id=419978 Guillaume Castagnino changed: What|Removed |Added CC||casta+...@xwing.info -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 439252] New: Kde config and discover crash
https://bugs.kde.org/show_bug.cgi?id=439252 Bug ID: 439252 Summary: Kde config and discover crash Product: Discover Version: 5.21.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: g...@free.fr CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.21.5) Qt Version: 5.15.2 Frameworks Version: 5.83.0 Operating System: Linux 5.12.11-300.fc34.x86_64 x86_64 Windowing System: X11 Drkonqi Version: 5.22.2 Distribution: Fedora 34 (Workstation Edition) -- Information about the crash: - What I was doing when the application crashed: I was by mistake installing a radeon driver on a computer equiped by nvdia (equiped) :[[[? - Unusual behavior I noticed: Can only navigate and run program : The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x7fbf8f1a2c65 in chameleon::ChameleonStyle::drawControl(QStyle::ControlElement, QStyleOption const*, QPainter*, QWidget const*) const () from /usr/lib64/qt5/plugins/styles/libchameleon.so #5 0x7fbf8f1ad721 in chameleon::ChameleonStyle::drawComplexControl(QStyle::ComplexControl, QStyleOptionComplex const*, QPainter*, QWidget const*) const () from /usr/lib64/qt5/plugins/styles/libchameleon.so #6 0x7fbf840d6bd8 in KQuickStyleItem::updatePolish() () from /usr/lib64/qt5/qml/org/kde/qqc2desktopstyle/private/libqqc2desktopstyleplugin.so #7 0x7fbfa48cb75c in QQuickWindowPrivate::polishItems() () from /lib64/libQt5Quick.so.5 #8 0x7fbfa48645e0 in QSGGuiThreadRenderLoop::renderWindow(QQuickWindow*) () from /lib64/libQt5Quick.so.5 #9 0x7fbfa4865843 in QSGGuiThreadRenderLoop::exposureChanged(QQuickWindow*) () from /lib64/libQt5Quick.so.5 #10 0x7fbfa3225ed5 in QWindow::event(QEvent*) () from /lib64/libQt5Gui.so.5 #11 0x7fbfa3d21e73 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #12 0x7fbfa2ddff48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #13 0x7fbfa321bff5 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () from /lib64/libQt5Gui.so.5 #14 0x7fbfa31fc4fc in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib64/libQt5Gui.so.5 #15 0x7fbf909074ce in xcbSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5XcbQpa.so.5 #16 0x7fbfa13b24cf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #17 0x7fbfa14064e8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #18 0x7fbfa13afc03 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #19 0x7fbfa2e2c6f8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #20 0x7fbfa2dde9b2 in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #21 0x7fbfa2de6544 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #22 0x5582598cd6cb in main () [Inferior 1 (process 5608) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 323382] syntax highliting messed up when section content starts with "{"
https://bugs.kde.org/show_bug.cgi?id=323382
Guillaume Lang changed:
What|Removed |Added
CC||guillaume.l...@illoc.net
Version|2.9.60 |2.9.93
--- Comment #5 from Guillaume Lang ---
Bug still present in 2.9.93.
MWE with variations:
"""""""
\documentclass{article}
\begin{document}
\section{Wrong}
{\small BOLD HIGHLIGHTING}
\section{Wrong}
%
{\small BOLD HIGHLIGHTING}
\section{Wrong}%
{\small BOLD HIGHLIGHTING}
\section{OK}
\textit{NOT BOLD}
{\small NOT BOLD}
\section{OK}
NOT BOLD
{\small NOT BOLD}
\end{document}
"""
Reproducible: Always
Steps to Reproduce:
code similar to the above
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-baloo] [Bug 389848] baloo_file crashes in mdb_put() in LMDB
https://bugs.kde.org/show_bug.cgi?id=389848 Guillaume B. changed: What|Removed |Added CC||geex+mag...@geex.ovh --- Comment #183 from Guillaume B. --- I had an issue similar to this recently, tell me if you need more traces coredumpctl dump PID: 1495228 (baloo_file) UID: 1000 (geex) GID: 1000 (geex) Signal: 6 (ABRT) Timestamp: Thu 2024-01-11 01:46:59 CET (14h ago) Command Line: /usr/libexec/kf6/baloo_file Executable: /usr/libexec/kf6/baloo_file Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-baloo_file-1495228.scope Unit: user@1000.service User Unit: app-gnome-baloo_file-1495228.scope Slice: user-1000.slice Owner UID: 1000 (geex) Boot ID: 52ca0d584d194ccbbaa6db5f7762a1d6 Machine ID: 0d084b96342343d6b1e021c0813ecb22 Hostname: x2.local Storage: /var/lib/systemd/coredump/core.baloo_file.1000.52ca0d584d194ccbbaa6db5f7762a1d6.1495228.170493401900.zst (present) Size on Disk: 711.9K Message: Process 1495228 (baloo_file) of user 1000 dumped core. Stack trace of thread 1495501: #0 0x7f4d460b33cc __pthread_kill_implementation (libc.so.6 + 0x853cc) #1 0x7f4d460648b2 raise (libc.so.6 + 0x368b2) #2 0x7f4d46f31967 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x5967) #3 0x7f4d46064960 __restore_rt (libc.so.6 + 0x36960) #4 0x7f4d460b33cc __pthread_kill_implementation (libc.so.6 + 0x853cc) #5 0x7f4d460648b2 raise (libc.so.6 + 0x368b2) #6 0x7f4d46050464 abort (libc.so.6 + 0x22464) #7 0x7f4d454ee15a mdb_assert_fail.constprop.0 (liblmdb.so.0.0.0 + 0x415a) #8 0x7f4d454ee1b7 mdb_page_dirty.cold (liblmdb.so.0.0.0 + 0x41b7) #9 0x7f4d454f2b76 mdb_page_alloc.isra.0 (liblmdb.so.0.0.0 + 0x8b76) #10 0x7f4d454f2d9b mdb_page_touch (liblmdb.so.0.0.0 + 0x8d9b) #11 0x7f4d454f4634 mdb_cursor_touch (liblmdb.so.0.0.0 + 0xa634) #12 0x7f4d454f7ac0 mdb_cursor_put (liblmdb.so.0.0.0 + 0xdac0) #13 0x7f4d454fa49f mdb_put (liblmdb.so.0.0.0 + 0x1049f) #14 0x7f4d46d3bf5d _ZN5Baloo10DocumentDB3putEyRK5QListI10QByteArrayE (libKF6BalooEngine.so.6 + 0xff5d) #15 0x7f4d46d55bd5 _ZN5Baloo16WriteTransaction15replaceDocumentERKNS_8DocumentE6QFlagsINS_17DocumentOperationEE (libKF6BalooEngine.so.6 + 0x29bd5) #16 0x00416c93 _ZN5Baloo20UnindexedFileIndexer3runEv (baloo_file + 0x16c93) #17 0x7f4d468dee45 _ZN17QThreadPoolThread3runEv (libQt6Core.so.6 + 0x2dee45) #18 0x7f4d468da337 _ZN14QThreadPrivate5startEPv (libQt6Core.so.6 + 0x2da337) #19 0x7f4d460b18da start_thread (libc.so.6 + 0x838da) #20 0x7f4d4612d48c __clone3 (libc.so.6 + 0xff48c) Stack trace of thread 1495228: #0 0x7f4d4612051f __poll (libc.so.6 + 0xf251f) #1 0x7f4d453ad7af g_main_context_iterate_unlocked.constprop.0 (libglib-2.0.so.0 + 0x587af) #2 0x7f4d453adeac g_main_context_iteration (libglib-2.0.so.0 + 0x58eac) #3 0x7f4d469dfddc _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3dfddc) #4 0x7f4d46781833 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x181833) #5 0x7f4d4677e1d4 _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x17e1d4) #6 0x0040c0e2 main (baloo_file + 0xc0e2) #7 0x7f4d460516b7 __libc_start_call_main (libc.so.6 + 0x236b7) #8 0x7f4d46051775 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x23775) #9 0x0040c201 _start (baloo_file + 0xc201) Stack trace of thread 1495328: #0 0x7f4d4612051f __poll (libc.so.6 + 0xf251f) #1 0x7f4d453ad7af g_main_context_iterate_unlocked.constprop.0 (libglib-2.0.so.0 + 0x587af) #2 0x7f4d453adeac g_main_context_iteration (libglib-2.0.so.0 + 0x58eac) #3 0x7f4d469dfddc _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3dfddc) #4 0x7f4d46781833 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x181833) #5 0x7f4d46874efc _ZN7QThread4execEv (libQt6Core.so.6 + 0x274efc) #6 0x7f4d46c9b4ea _ZN22QDBusConnectionManager3runEv (libQt6DBus.so.6 + 0x354ea) #7
[KSystemLog] [Bug 227793] ksystemlog starting as root causing problems
https://bugs.kde.org/show_bug.cgi?id=227793 Guillaume Frognier changed: What|Removed |Added CC||guillaume.frognier@laposte. ||net --- Comment #4 from Guillaume Frognier --- I confirm this. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 472106] New: [Feature Request] Add a variable "Executable name" for filename variables
https://bugs.kde.org/show_bug.cgi?id=472106 Bug ID: 472106 Summary: [Feature Request] Add a variable "Executable name" for filename variables Classification: Applications Product: Spectacle Version: 23.04.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: a...@teri-chan.net CC: k...@david-redondo.de Target Milestone: --- Hello. This is a mere feature request and I don't know if it's possible. I know there is %T for window title, but sometimes the window title can be pretty long, like when you're taking a screenshot of your firefox browser window for example. I come from the ShareX app on Windows and I'm very happy with what Spectacle offers, but I think a new variable like %A containing the app's process name would be nice in order to better sort screenshots in a folder. Thanks in advance. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 490508] New: Power management daemon crash on screen locking
https://bugs.kde.org/show_bug.cgi?id=490508
Bug ID: 490508
Summary: Power management daemon crash on screen locking
Classification: Plasma
Product: Powerdevil
Version: 6.1.3
Platform: Arch Linux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: gufi...@gmail.com
CC: m...@ratijas.tk, natalie_clar...@yahoo.de
Target Milestone: ---
Application: org_kde_powerdevil (6.1.3)
Qt Version: 6.7.2
Frameworks Version: 6.4.0
Operating System: Linux 6.9.10-arch1-1 x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 6.1.3 [CoredumpBackend]
-- Information about the crash:
Everytime my desktop locks after inactivity, a crash window about Power
management crashing is present.
The crash can be reproduced every time.
-- Backtrace:
Application: KDE Power Management System (org_kde_powerdevil), signal:
Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
Downloading separate debug info for /usr/lib/org_kde_powerdevil...
[New LWP 26396]
[New LWP 26398]
[New LWP 26397]
[New LWP 26404]
[New LWP 26406]
[New LWP 26524]
[New LWP 26403]
[New LWP 26405]
[New LWP 26465]
[New LWP 26401]
[New LWP 26467]
[New LWP 26400]
[New LWP 26466]
[New LWP 26399]
Downloading separate debug info for /usr/lib/libKF6Crash.so.6...
Downloading separate debug info for /usr/lib/libpowerdevilcore.so.2...
Downloading separate debug info for /usr/lib/libKF6DBusAddons.so.6...
Downloading separate debug info for /usr/lib/libKF6XmlGui.so.6...
Downloading separate debug info for /usr/lib/libKF6GlobalAccel.so.6...
Downloading separate debug info for /usr/lib/libKF6CoreAddons.so.6...
Downloading separate debug info for /usr/lib/libKF6I18n.so.6...
Downloading separate debug info for /usr/lib/libQt6DBus.so.6...
Downloading separate debug info for /usr/lib/libQt6Gui.so.6...
Downloading separate debug info for /usr/lib/libQt6Core.so.6...
Downloading separate debug info for /usr/lib/libc.so.6...
Downloading separate debug info for /usr/lib/libX11.so.6...
Downloading separate debug info for /usr/lib/libPlasmaActivities.so.6...
Downloading separate debug info for /usr/lib/libkworkspace6.so.6...
Downloading separate debug info for /usr/lib/libKF6AuthCore.so.6...
Downloading separate debug info for /usr/lib/libKF6Solid.so.6...
Downloading separate debug info for /usr/lib/libKF6IdleTime.so.6...
Downloading separate debug info for /usr/lib/libKF6Screen.so.8...
Downloading separate debug info for /usr/lib/libKF6Notifications.so.6...
Downloading separate debug info for /usr/lib/libKirigamiPlatform.so.6...
Downloading separate debug info for /usr/lib/libudev.so.1...
Downloading separate debug info for /usr/lib/libxcb.so.1...
Downloading separate debug info for /usr/lib/libddcutil.so.5...
Downloading separate debug info for /usr/lib/libKF6ConfigGui.so.6...
Downloading separate debug info for /usr/lib/libKF6ConfigCore.so.6...
Downloading separate debug info for /usr/lib/libm.so.6...
Downloading separate debug info for /usr/lib/libQt6Xml.so.6...
Downloading separate debug info for /usr/lib/libQt6Network.so.6...
Downloading separate debug info for /usr/lib/libQt6PrintSupport.so.6...
Downloading separate debug info for /usr/lib/libKF6ItemViews.so.6...
Downloading separate debug info for /usr/lib/libKF6IconWidgets.so.6...
Downloading separate debug info for /usr/lib/libKF6ConfigWidgets.so.6...
Downloading separate debug info for /usr/lib/libKF6WidgetsAddons.so.6...
Downloading separate debug info for /usr/lib/libQt6Widgets.so.6...
Downloading separate debug info for /usr/lib/libKF6IconThemes.so.6...
Downloading separate debug info for /usr/lib/libKF6ColorScheme.so.6...
Downloading separate debug info for /usr/lib/libKF6GuiAddons.so.6...
Downloading separate debug info for /usr/lib/libdbus-1.so.3...
Downloading separate debug info for /usr/lib/libEGL.so.1...
Downloading separate debug info for /usr/lib/libfontconfig.so.1...
Downloading separate debug info for /usr/lib/libglib-2.0.so.0...
Downloading separate debug info for /usr/lib/libxkbcommon.so.0...
Downloading separate debug info for /usr/lib/libGLX.so.0...
Downloading separate debug info for /usr/lib/libOpenGL.so.0...
Downloading separate debug info for /usr/lib/libpng16.so.16...
Downloading separate debug info for /usr/lib/libharfbuzz.so.0...
Downloading separate debug info for /usr/lib/libmd4c.so.0...
Downloading separate debug info for /usr/lib/libfreetype.so.6...
Downloading separate debug info for /usr/lib/libz.so.1...
Downloading separate debug info for /usr/lib/libicui18n.so.75...
Downloading separate debug info for /usr/lib/libicuuc.so.75...
Downloading separate debug info for /usr/lib/libsystemd.so.0...
Downloading separate debug info for /usr/lib/libdouble-conversion.so.3...
Downloading separate debug info for /usr/lib/libb2.so.1.
[kwin] [Bug 457847] kwin becomes unresponsive, need to restart session
https://bugs.kde.org/show_bug.cgi?id=457847 Guillaume Castagnino changed: What|Removed |Added CC||casta+...@xwing.info --- Comment #22 from Guillaume Castagnino --- Hello, I seems I face the same bug. At least I have the same symptoms. After digging, I found this: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7674 affecting mesa 22.2 After reverting the 2 involved commits, it looks this crash does not occur any more. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462315] New: kwin_x11: erratic windows resize when switching screen OFF then ON
https://bugs.kde.org/show_bug.cgi?id=462315 Bug ID: 462315 Summary: kwin_x11: erratic windows resize when switching screen OFF then ON Classification: Plasma Product: kwin Version: 5.26.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-x11-standalone Assignee: kwin-bugs-n...@kde.org Reporter: casta+...@xwing.info Target Milestone: --- Created attachment 154083 --> https://bugs.kde.org/attachment.cgi?id=154083&action=edit video showing window resize when powering on the screen SUMMARY Use case: when not in front of my desktop, I usually shut down the screen. So X11 is left without screen. When restarting the screen, I see strange windows resize. For some applications (mostly GTK), it leads to application freeze with this message: Gtk-WARNING **: infinite surface size not supported On screen powering _on_, I get this that seems interesting: nov. 27 14:45:31 dagobah kscreen_backend_launcher[1044]: kscreen.xrandr: Requested screen size is QSize(0, 0) nov. 27 14:45:31 dagobah kscreen_backend_launcher[1044]: kscreen.xrandr: Requested screen size is QSize(2560, 1440) I also have this : $ journalctl --user --identifier kwin_x11 nov. 27 14:45:30 dagobah kwin_x11[153806]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3283, resource id: 71941410, major code: 3 (GetWindowAttributes), minor code: 0 nov. 27 14:45:30 dagobah kwin_x11[153806]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 3284, resource id: 71941410, major code: 14 (GetGeometry), minor code: 0 nov. 27 14:45:31 dagobah kwin_x11[153806]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3525, resource id: 71941430, major code: 3 (GetWindowAttributes), minor code: 0 nov. 27 14:45:31 dagobah kwin_x11[153806]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 3526, resource id: 71941430, major code: 14 (GetGeometry), minor code: 0 nov. 27 14:45:31 dagobah kwin_x11[153806]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3663, resource id: 71941442, major code: 3 (GetWindowAttributes), minor code: 0 nov. 27 14:45:31 dagobah kwin_x11[153806]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 3664, resource id: 71941442, major code: 14 (GetGeometry), minor code: 0 nov. 27 14:45:32 dagobah kwin_x11[153806]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3738, resource id: 100663300, major code: 18 (ChangeProperty), minor code: 0 nov. 27 14:45:32 dagobah kwin_x11[153806]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3750, resource id: 100663307, major code: 18 (ChangeProperty), minor code: 0 nov. 27 14:45:32 dagobah kwin_x11[153806]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3820, resource id: 71941455, major code: 3 (GetWindowAttributes), minor code: 0 nov. 27 14:45:32 dagobah kwin_x11[153806]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 3821, resource id: 71941455, major code: 14 (GetGeometry), minor code: 0 STEPS TO REPRODUCE 1. Shut down screen and restart it. OBSERVED RESULT Strange windows resize, maximized one or not. sometime with application freeze. EXPECTED RESULT Windows are not resized. SOFTWARE/OS VERSIONS Operating System: Gentoo Linux 2.9 KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.5 Kernel Version: 6.0.9-gentoo (64-bit) Graphics Platform: X11 Processors: 12 × 12th Gen Intel® Core™ i5-12500 Memory: 31.1 Gio of RAM Graphics Processor: Mesa Intel® UHD Graphics 770 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B660I AORUS PRO DDR4 System Version: -CF ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462315] kwin_x11: erratic windows resize when switching screen OFF then ON
https://bugs.kde.org/show_bug.cgi?id=462315 --- Comment #1 from Guillaume Castagnino --- For completeness on this : I did not have it with my previous computer (same installation, I moved the hard drive to a new hardware) Previous hardware not having issue: intel i5 4960 GPU (haswell generation) New hardware having the issue, as shown in my previous post: intel i5 12500 GPU (alderlake-S generation) So it could be a driver/xorg issue, not kwin. I workarounded the issue by adding this in my xorg configuration instead of relying on auto-configuration. Since I added, this, no more erratic windows resize when switching the monitor off/on # cat /etc/X11/xorg.conf.d/10-monitor.conf Section "Monitor" Identifier "DP-1" Option "PreferredMode" "2560x1440" EndSection Section "Device" Identifier "Intel" Driver "modesetting" Option "Monitor-DP-1" "DP-1" EndSection -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462315] kwin_x11: erratic windows resize when switching screen OFF then ON
https://bugs.kde.org/show_bug.cgi?id=462315 Guillaume Castagnino changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Guillaume Castagnino --- I close it now. It seems that upgrade to 5.26.4 fixes this. I cannot reproduce any more. Maybe related to this commit about screen modes ? https://invent.kde.org/plasma/kwin/-/commit/bb99fb8aa4dd5c1ce0630081e424f1038c6b3dae Because it really looked like a race condition while reading the DDC modes when screen going back on. Anyway, fixed for me, thank’s! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462316] Black background after monitors were in standby
https://bugs.kde.org/show_bug.cgi?id=462316 Guillaume Castagnino changed: What|Removed |Added CC||casta+...@xwing.info -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421441] Calendar widget highlights yesterday instead of today
https://bugs.kde.org/show_bug.cgi?id=421441 Guillaume Castagnino changed: What|Removed |Added CC||casta+...@xwing.info -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 340871] Applications open in background when opened from system tray
https://bugs.kde.org/show_bug.cgi?id=340871 Guillaume Castagnino changed: What|Removed |Added CC||casta+...@xwing.info --- Comment #14 from Guillaume Castagnino --- I can confirm this behaviour with applications opening from systray Some examples all Qt applications: - nextcloud - keepassxc - strawberry - tel.red sky (well, this one is proprietary and damn buggy, so we may ignore it) Set focus stealing prevention to Low. Behaviour may change depending on the application, since click on systray icon leads to different behaviour Example 1, with strawberry: - For example open firefox and dolphin. Give the focus to dolphin - the first time I click the strawberry systray icon, the application is opened, but it stay below dolphin, but above firefox. Does not get the focus. - second click on the icon, the window comes on top and get the focus - third click, the window is closed, focus is back on dolphin - fourth click, this time, strawberry opens directly on top, with focus (correct behaviour) - fifth click, it closes - sixth click is the same as the fourth, etc… But if I click again inside dolphin, I’m back to the initial behaviour Example 2 with sky: - For example open firefox and dolphin. Give the focus to dolphin - the first time I click the tel.red sky systray icon, the application is opened, but it stay below dolphin, but above firefox. Does not get the focus - second click close the window - third click open again, but this time on top and with focus (correct behaviour) - same as for strawberry, the behaviour is OK until I click on dolphin, in such case I’m back to the begining With nextcloud on keepassxc, It seems more random, or at least I did not get the clue. Sometime it behaves correctly, and sometime it opens without focus just behind the topmost window. If I disable the focus stealing prevention, all four apps behave correctly. But this is not a very good workaround as in such case, some popups get the focus when it’s not desirable. Currently using plasma/kwin 5.18.4.1 under Gentoo, but this was the same with 5.17 or below. -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 370940] DPI field shows: 300 DPI (I18N_EXCESS_ARGUMENTS_SUPPLIED)
https://bugs.kde.org/show_bug.cgi?id=370940 Guillaume Castagnino changed: What|Removed |Added CC||casta+...@xwing.info -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394772] Some GTK apps temporarily lose scroll focus while desktop notification are shown
https://bugs.kde.org/show_bug.cgi?id=394772 Guillaume Castagnino changed: What|Removed |Added CC||casta+...@xwing.info -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 397045] New: Kdevelop crashes when parsing starts
https://bugs.kde.org/show_bug.cgi?id=397045 Bug ID: 397045 Summary: Kdevelop crashes when parsing starts Product: kdevelop Version: 5.2.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: gufi...@gmail.com Target Milestone: --- Application: kdevelop (5.2.3) Qt Version: 5.11.1 Frameworks Version: 5.48.0 Operating System: Linux 4.17.10-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I opened a project. The background parser started then crashes the IDE. It happen every time I open that particular project. This make KDevelop completely unusable for that project (cash on startup) Some investigation showed me that it happen when the cursor kind is CXCursor_FunctionTemplate and it seem it happen when it's a member function. I tried debugging it but it was inconclusive. Copying the preprocessed file in another project did not reproduced the crash. I Also tried deleting the .kdev and the .kdev folder and I tried emptying the cache. - Custom settings of the application: I enabled C++17. It didn't seemed related for this bug however. It happen both with the master branch and the v5.2.3 tag The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8c3e2b0940 (LWP 6785))] Thread 20 (Thread 0x7f8bba7fc700 (LWP 7028)): #0 0x7f8c2fc9d3f6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f8c36a7e1dd in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f8c36a75c04 in () at /usr/lib/libQt5Core.so.5 #3 0x7f8c36a7db45 in () at /usr/lib/libQt5Core.so.5 #4 0x7f8c2fc97075 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f8c35dc053f in clone () at /usr/lib/libc.so.6 Thread 19 (Thread 0x7f8bb8ff9700 (LWP 6841)): #0 0x7f8c35db5ea9 in poll () at /usr/lib/libc.so.6 #1 0x7f8c2d58f523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f8c2d58f63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f8c36c7f054 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f8c36c2a94c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f8c36a73a99 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f8bcab26cea in () at /usr/lib/qt/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so #7 0x7f8c36a7db45 in () at /usr/lib/libQt5Core.so.5 #8 0x7f8c2fc97075 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f8c35dc053f in clone () at /usr/lib/libc.so.6 Thread 18 (Thread 0x7f8bb97fa700 (LWP 6837)): #0 0x7f8c2fc9cffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f8c36a7e2fc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f8c32e82139 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f8c32e86009 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f8c32e811fd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f8c32e84059 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f8c36a7db45 in () at /usr/lib/libQt5Core.so.5 #7 0x7f8c2fc97075 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f8c35dc053f in clone () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7f8bb9ffb700 (LWP 6836)): [KCrash Handler] #6 0x7f8be43c1450 in clang::Decl::setInvalidDecl(bool) () at /usr/lib/../lib/libclangAST.so.6 #7 0x7f8be43c149c in clang::Decl::setInvalidDecl(bool) () at /usr/lib/../lib/libclangAST.so.6 #8 0x7f8bd55dfbc8 in clang::ASTDeclReader::VisitDecl(clang::Decl*) () at /usr/lib/../lib/../lib/libclangSerialization.so.6 #9 0x7f8bd55e0482 in clang::ASTDeclReader::VisitNamedDecl(clang::NamedDecl*) () at /usr/lib/../lib/../lib/libclangSerialization.so.6 #10 0x7f8bd55e0982 in clang::ASTDeclReader::VisitValueDecl(clang::ValueDecl*) () at /usr/lib/../lib/../lib/libclangSerialization.so.6 #11 0x7f8bd55e09f6 in clang::ASTDeclReader::VisitDeclaratorDecl(clang::DeclaratorDecl*) () at /usr/lib/../lib/../lib/libclangSerialization.so.6 #12 0x7f8bd55ed7fe in clang::ASTDeclReader::VisitVarDeclImpl(clang::VarDecl*) () at /usr/lib/../lib/../lib/libclangSerialization.so.6 #13 0x7f8bd55ee6d4 in clang::ASTDeclReader::VisitDecompositionDecl(clang::DecompositionDecl*) () at /usr/lib/../lib/../lib/libclangSerialization.so.6 #14 0x7f8bd55f4916 in clang::ASTDeclReader::Visit(clang::Decl*)
[kdevelop] [Bug 397045] Kdevelop crashes when parsing starts
https://bugs.kde.org/show_bug.cgi?id=397045 Guillaume Racicot changed: What|Removed |Added Platform|Archlinux Packages |Compiled Sources -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 397045] Kdevelop crashes when parsing starts
https://bugs.kde.org/show_bug.cgi?id=397045 --- Comment #1 from Guillaume Racicot --- I tried opening the project in QtCreator, and it cannot parse the project correctly. I get in the console "Clang Code Model: Error: The clangbackend process has finished unexpectedly and was restarted." So it seems to be an error in the clang library. But instead of outputting an error like QtCreator, kdevelop crashes. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372220] Usage of a template aliases are not hightlighted
https://bugs.kde.org/show_bug.cgi?id=372220 --- Comment #2 from Guillaume Racicot --- I think this problem has been resolved in KDevelop 5.2 -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 391495] Configure menu entry does not open any window
https://bugs.kde.org/show_bug.cgi?id=391495 Guillaume Racicot changed: What|Removed |Added Platform|Other |Compiled Sources -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 391495] New: Configure menu entry does not open any window
https://bugs.kde.org/show_bug.cgi?id=391495 Bug ID: 391495 Summary: Configure menu entry does not open any window Product: elisa Version: 0.0.81 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: gufi...@gmail.com Target Milestone: --- Step to reproduce: 1. Press the hamburger menu 2. Click on "Configure Elisa" 3. ... Actual behavior: - No configuration window is open Expected behavior: - A configuration window is opened -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 391496] New: Crash when spamming the "Configure Elisa" action through hotkeys
https://bugs.kde.org/show_bug.cgi?id=391496 Bug ID: 391496 Summary: Crash when spamming the "Configure Elisa" action through hotkeys Product: elisa Version: 0.0.81 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: gufi...@gmail.com Target Milestone: --- Application: elisa (0.0.81) Qt Version: 5.10.1 Frameworks Version: 5.43.0 Operating System: Linux 4.15.6-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I pressed a large number of times Ctrl+Shift+, rapidly - Unusual behavior I noticed: The configure window don't open for me, so spamming the hotkey was easy The crash can be reproduced every time. -- Backtrace: Application: Elisa (elisa), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9bcc8d1200 (LWP 14977))] Thread 13 (Thread 0x7f9b6bc2e700 (LWP 15128)): #0 0x7f9bc17aeee8 in () at /usr/lib/libglib-2.0.so.0 #1 0x7f9bc17af10e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #2 0x7f9bc8915314 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f9bc88b73db in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f9bc86c67ae in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f9bc9c34379 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f9bc86cbb4d in () at /usr/lib/libQt5Core.so.5 #7 0x7f9bc3f5608c in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f9bc7fd3e7f in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7f9b79769700 (LWP 14990)): #0 0x7f9bc3f5c3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f9bc86cd02c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f9bc6a1041a in () at /usr/lib/libQt5Quick.so.5 #3 0x7f9bc6a108a4 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f9bc86cbb4d in () at /usr/lib/libQt5Core.so.5 #5 0x7f9bc3f5608c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f9bc7fd3e7f in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f9b7a17c700 (LWP 14989)): #0 0x7f9bc3f5c6fd in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f9bc86ccee1 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f9bc86c8db1 in () at /usr/lib/libQt5Core.so.5 #3 0x7f9bc86cbb4d in () at /usr/lib/libQt5Core.so.5 #4 0x7f9bc3f5608c in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f9bc7fd3e7f in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f9b7a97d700 (LWP 14988)): #0 0x7f9bc7fc997b in poll () at /usr/lib/libc.so.6 #1 0x7f9bc17aeff3 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f9bc17af10e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f9bc8915314 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f9bc88b73db in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f9bc86c67ae in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f9bc86cbb4d in () at /usr/lib/libQt5Core.so.5 #7 0x7f9bc3f5608c in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f9bc7fd3e7f in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f9b7b17e700 (LWP 14987)): #0 0x7f9bc17f5b94 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7f9bc17aeb8b in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #2 0x7f9bc17af081 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f9bc17af10e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f9bc8915314 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f9bc88b73db in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f9bc86c67ae in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f9bc86cbb4d in () at /usr/lib/libQt5Core.so.5 #8 0x7f9bc3f5608c in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f9bc7fd3e7f in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f9b98f28700 (LWP 14986)): #0 0x7f9bc17f5b94 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7f9bc17ade7c in g_main_context_acquire () at /usr/lib/libglib-2.0.so.0 #2 0x7f9bc17aeea7 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f9bc17af10e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f9bc8915314 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f9bc88b73db in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f9bc86c67ae in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f9bc86cbb4d in () at /usr/lib/libQt5Co
[kdevelop] [Bug 391775] New: Crash when right click on the toolbar
https://bugs.kde.org/show_bug.cgi?id=391775 Bug ID: 391775 Summary: Crash when right click on the toolbar Product: kdevelop Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: gufi...@gmail.com Target Milestone: --- Application: kdevelop (5.2.40) Qt Version: 5.10.1 Frameworks Version: 5.43.0 Operating System: Linux 4.15.7-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: 1. Compile project 2. While compiling, right click on a button in the toolbar The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f04a640 (LWP 5178))] Thread 18 (Thread 0x7f0407fff700 (LWP 5311)): #0 0x7f049bfa33bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f04a0ec102c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f04a7d7e42f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f04a7d83479 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f04a7d7d924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f04a7d80c83 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f04a0ebfb4d in () at /usr/lib/libQt5Core.so.5 #7 0x7f049bf9d08c in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f04a0264e7f in clone () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7f04297fa700 (LWP 5309)): #0 0x7f049bfa33bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f04a0ec102c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f04a7d7e42f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f04a7d83479 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f04a7d7d924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f04a7d834d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f04a7d7d924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f04a7d834d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f04a7d7d924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f04a7d834d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f04a7d7d924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f04a7d834d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7f04a7d7d924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #13 0x7f04a7d834d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #14 0x7f04a7d7d924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #15 0x7f04a7d834d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #16 0x7f04a7d7d924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #17 0x7f04a7d834d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #18 0x7f04a7d7d924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #19 0x7f04a7d834d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #20 0x7f04a7d7d924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #21 0x7f04a7d834d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #22 0x7f04a7d7d924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #23 0x7f04a7d834d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #24 0x7f04a7d7d924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #25 0x7f04a7d834d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #26 0x7f04a7d7d924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #27 0x7f04a7d80c83 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #28 0x7f04a0ebfb4d in () at /usr/lib/libQt5Core.so.5 #29 0x7f049bf9d08c in start_thread () at /usr/lib/libpthread.so.0 #30 0x7f04a0264e7f in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7f0429ffb700 (LWP 5308)): #0
[kdevelop] [Bug 387994] New: All variable in body and parameter in a global lambda hightlighted as global variables
https://bugs.kde.org/show_bug.cgi?id=387994 Bug ID: 387994 Summary: All variable in body and parameter in a global lambda hightlighted as global variables Product: kdevelop Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: gufi...@gmail.com Target Milestone: --- Created attachment 109431 --> https://bugs.kde.org/attachment.cgi?id=109431&action=edit Acual result of hightlighting When declaring a global lambda, or sending a lambda into a function inside the global scope, all parameters of the lambda and variables in the body of the lambda are hightlighed light pink, as of they were all in the global scope. Expected result: All variables and parameter to be hightlighted in different colors. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387994] All variable in body and parameter in a global lambda hightlighted as global variables
https://bugs.kde.org/show_bug.cgi?id=387994 --- Comment #1 from Guillaume Racicot --- Created attachment 109432 --> https://bugs.kde.org/attachment.cgi?id=109432&action=edit Expected result of hightlighting -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387994] All variable in body and parameter in a global lambda hightlighted as global variables
https://bugs.kde.org/show_bug.cgi?id=387994 --- Comment #2 from Guillaume Racicot --- Created attachment 109433 --> https://bugs.kde.org/attachment.cgi?id=109433&action=edit Expected result of hightlighting (fixed) Please refer to this one, the previous edited screenshot contained errors -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387994] All variable in body and parameter in a global lambda hightlighted as global variables
https://bugs.kde.org/show_bug.cgi?id=387994 --- Comment #4 from Guillaume Racicot --- The fixed version of my screenshot simply removed the colored highlighting for the lambda names, since they are global themselves. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387994] All variable in body and parameter in a global lambda hightlighted as global variables
https://bugs.kde.org/show_bug.cgi?id=387994 --- Comment #6 from Guillaume Racicot --- Ah! I simply enclosed all lambda in a function, took a screenshot and edited out the function in gimp. I didn't found a magic workaround for that unfortunately :) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 392859] New: Discovers crashes
https://bugs.kde.org/show_bug.cgi?id=392859 Bug ID: 392859 Summary: Discovers crashes Product: Discover Version: 5.12.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: guillaume2.fay...@wanadoo.fr Target Milestone: --- Application: plasma-discover (5.12.4) Qt Version: 5.9.4 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-13-generic x86_64 Distribution: Ubuntu Bionic Beaver (development branch) -- Information about the crash: - What I was doing when the application crashed: Discovers crashes when clicking on Settings. This happens every time. It happens on a fresh install of Kubuntu 18.04 Beta 2. The crash can be reproduced every time. -- Backtrace: Application: Découvrir (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc2059c6f40 (LWP 1817))] Thread 9 (Thread 0x7fc1bec9f700 (LWP 1825)): #0 0x7fc1fb9a0360 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fc1fb9a28d3 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc1fb9a336b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc1fb9a354c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc201a004fb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc2019a561a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc2017c422a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fc2017c916d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fc1fd8c86db in start_thread (arg=0x7fc1bec9f700) at pthread_create.c:463 #9 0x7fc2010c188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fc1ce29c700 (LWP 1824)): #0 0x7fc1fd8ceed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fc1ce29bc40, expected=0, futex_word=0x7fc1c0006df4) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fc1ce29bd00, mutex=0x7fc1c0006da0, cond=0x7fc1c0006dc8) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7fc1c0006dc8, mutex=0x7fc1c0006da0, abstime=0x7fc1ce29bd00) at pthread_cond_wait.c:667 #3 0x7fc2017ca458 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc2017c652d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc2017c916d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc1fd8c86db in start_thread (arg=0x7fc1ce29c700) at pthread_create.c:463 #7 0x7fc2010c188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fc1cea9d700 (LWP 1823)): #0 0x7fc2010b4bf9 in __GI___poll (fds=0x557c902d7030, nfds=1, timeout=120106) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fc1fb9a3439 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc1fb9a354c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc201a004fb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc2019a561a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc2017c422a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc2017c916d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fc1fd8c86db in start_thread (arg=0x7fc1cea9d700) at pthread_create.c:463 #8 0x7fc2010c188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fc1d001e700 (LWP 1822)): #0 0x7fc1fb9a33ee in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fc1fb9a354c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc201a004fb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fc2019a561a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc2017c422a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc2017c916d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc1fd8c86db in start_thread (arg=0x7fc1d001e700) at pthread_create.c:463 #7 0x7fc2010c188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fc1d9729700 (LWP 1821)): #0 0x7fc1fb9e8cf4 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fc1fb9a2930 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc1fb9a336b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3
[Discover] [Bug 392859] Discovers crashes
https://bugs.kde.org/show_bug.cgi?id=392859 --- Comment #2 from Guillaume Fayard --- Maybe I was on Plasma using Wayland, cannot remember. (I don't know if this could be related to the bug.) Anyway, now it's not happening anymore (after updates). -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 269067] Massif Diff Script
https://bugs.kde.org/show_bug.cgi?id=269067 Guillaume Desmottes changed: What|Removed |Added CC||gdesm...@gnome.org --- Comment #1 from Guillaume Desmottes --- Hi, This script is exactly what I'm looking for but unfortunately it doesn't seem to work with recent version of Valgrind (3.14.0). Do you have an updated version by any chance? Such script would be a great addition to the valgrind tests suite. Any chance to consider including it? -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 339871] The process kio_file is using approximately 3.2 GB of memory.
https://bugs.kde.org/show_bug.cgi?id=339871 --- Comment #15 from Guillaume Debray --- This bug is solved in the 18.04 version (Kubuntu x64) Thanks -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 397045] Kdevelop crashes when parsing starts [clang::Decl::setInvalidDecl]
https://bugs.kde.org/show_bug.cgi?id=397045 --- Comment #6 from Guillaume Racicot --- The crash still happens with clang 7. The backtrace when opening my project is similar: #0 0x7fffb27107b0 in clang::Decl::setInvalidDecl(bool) () at /usr/lib/../lib/libclangAST.so.7 #1 0x7fffb27107fc in clang::Decl::setInvalidDecl(bool) () at /usr/lib/../lib/libclangAST.so.7 #2 0x7fffb10e9c18 in clang::ASTDeclReader::VisitDecl(clang::Decl*) () at /usr/lib/../lib/../lib/libclangSerialization.so.7 #3 0x7fffb10ea4e2 in clang::ASTDeclReader::VisitNamedDecl(clang::NamedDecl*) () at /usr/lib/../lib/../lib/libclangSerialization.so.7 #4 0x7fffb10eaa02 in clang::ASTDeclReader::VisitValueDecl(clang::ValueDecl*) () at /usr/lib/../lib/../lib/libclangSerialization.so.7 #5 0x7fffb10eaa96 in clang::ASTDeclReader::VisitDeclaratorDecl(clang::DeclaratorDecl*) () at /usr/lib/../lib/../lib/libclangSerialization.so.7 #6 0x7fffb10f913e in clang::ASTDeclReader::VisitVarDeclImpl(clang::VarDecl*) () at /usr/lib/../lib/../lib/libclangSerialization.so.7 #7 0x7fffb10fa044 in clang::ASTDeclReader::VisitDecompositionDecl(clang::DecompositionDecl*) () at /usr/lib/../lib/../lib/libclangSerialization.so.7 #8 0x7fffb1100346 in clang::ASTDeclReader::Visit(clang::Decl*) () at /usr/lib/../lib/../lib/libclangSerialization.so.7 #9 0x7fffb1100ae0 in clang::ASTReader::ReadDeclRecord(unsigned int) () at /usr/lib/../lib/../lib/libclangSerialization.so.7 #10 0x7fffb10b75a6 in clang::ASTReader::GetDecl(unsigned int) () at /usr/lib/../lib/../lib/libclangSerialization.so.7 #11 0x7fffb1102563 in clang::ASTStmtReader::VisitDeclStmt(clang::DeclStmt*) () at /usr/lib/../lib/../lib/libclangSerialization.so.7 #12 0x7fffb1117885 in clang::ASTReader::ReadStmtFromStream(clang::serialization::ModuleFile&) () at /usr/lib/../lib/../lib/libclangSerialization.so.7 #13 0x7fffb10bd6c3 in clang::ASTReader::GetExternalDeclStmt(unsigned long) () at /usr/lib/../lib/../lib/libclangSerialization.so.7 #14 0x7fffb270806c in clang::FunctionDecl::getBody(clang::FunctionDecl const*&) const () at /usr/lib/../lib/libclangAST.so.7 #15 0x7fffb2939c6c in clang_getCursorDefinition () at /usr/lib/libclang.so.7 #16 0x7fffb2939fcb in clang_isCursorDefinition () at /usr/lib/libclang.so.7 #17 0x7fffb2a7bd3d in (anonymous namespace)::Visitor::dispatchCursor<(CXCursorKind)30, (Decision)0, (Decision)2> (cursor=..., this=0x7fff82ffc170, parent=...) at /home/master/prog/kdevelop/plugins/clang/duchain/builder.cpp:919 #18 0x7fffb2a7bd3d in (anonymous namespace)::Visitor::dispatchCursor<(CXCursorKind)30> (parent=..., cursor=..., this=0x7fff82ffc170) at /home/master/prog/kdevelop/plugins/clang/duchain/builder.cpp:912 #19 0x7fffb2a7bd3d in (anonymous namespace)::visitCursor(CXCursor, CXCursor, CXClientData) (cursor=..., parent=..., data=0x7fff82ffc170) at /home/master/prog/kdevelop/plugins/clang/duchain/builder.cpp:1541 #20 0x7fffb2941025 in () at /usr/lib/libclang.so.7 #21 0x7fffb294306e in () at /usr/lib/libclang.so.7 #22 0x7fffb294316c in () at /usr/lib/libclang.so.7 #23 0x7fffb2940b03 in () at /usr/lib/libclang.so.7 #24 0x7fffb2948c81 in clang_visitChildren () at /usr/lib/libclang.so.7 #25 0x7fffb2a670e1 in (anonymous namespace)::Visitor::buildDeclaration<(CXCursorKind)2, KDevelop::ClassDeclaration, true> (cursor=..., this=0x7fff82ffc170) at /usr/include/c++/8.2.1/bits/move.h:99 #26 0x7fffb2a670e1 in (anonymous namespace)::Visitor::dispatchCursor<(CXCursorKind)2, (Decision)0, (Decision)0> (parent=..., cursor=..., this=0x7fff82ffc170) at /home/master/prog/kdevelop/plugins/clang/duchain/builder.cpp:950 #27 0x7fffb2a670e1 in (anonymous namespace)::Visitor::dispatchCursor<(CXCursorKind)2, (Decision)0, (Decision)2>(CXCursor, CXCursor) (this=0x7fff82ffc170, cursor=..., parent=...) at /home/master/prog/kdevelop/plugins/clang/duchain/builder.cpp:924 #28 0x7fffb2a7e551 in (anonymous namespace)::Visitor::dispatchCursor<(CXCursorKind)2> (parent=..., cursor=..., this=0x7fff82ffc170) at /home/master/prog/kdevelop/plugins/clang/duchain/builder.cpp:448 #29 0x7fffb2a7e551 in (anonymous namespace)::visitCursor(CXCursor, CXCursor, CXClientData) (cursor=..., parent=..., data=0x7fff82ffc170) at /home/master/prog/kdevelop/plugins/clang/duchain/builder.cpp:1522 #30 0x7fffb2941025 in () at /usr/lib/libclang.so.7 #31 0x7fffb294306e in () at /usr/lib/libclang.so.7 #32 0x7fffb294316c in () at /usr/lib/libclang.so.7 #33 0x7fffb2940b03 in () at /usr/lib/libclang.so.7 #34 0x7fffb2948c81 in clang_visitChildren () at /usr/lib/libclang.so.7 #35 0x7fffb2a6c4c1 in (anonymous namespace)::Visitor::buildDeclaration<(CXCursorKind)22, KDevelop::Declaration, true>(CXCursor) (this=this@entry=0x7fff82ffc170, cursor=...) at /usr/include/c++/8.2.1/bits/move.h:99 #36 0x7fffb2a7a536 in (anonymous namespace)::Visitor::dispatchCursor<(CXCu
[kdevelop] [Bug 397205] Lambda capture with initializers and structured binding declaration not parsed
https://bugs.kde.org/show_bug.cgi?id=397205 Guillaume Racicot changed: What|Removed |Added CC||gufi...@gmail.com --- Comment #1 from Guillaume Racicot --- Created attachment 115585 --> https://bugs.kde.org/attachment.cgi?id=115585&action=edit Highligted operator== with two unhighlighted variables As with lambda capture, structured binding seems to behave as if the type of the variable is indeed recognized, but not the declaration. I added a screenshot that demonstrates that two unhighlighted variables (created from structured bindings) actually yield to highlighted expressions when it uses other entities. I analyzed what libclang output as information, and it seems to skip declaration of such variable (structured bindings and lambda capture with initializers) but later uses those as if they were declared. This breaks the KDevelop DUChain, since the usages cannot be linked to a declaration. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 397045] Kdevelop crashes when parsing starts [clang::Decl::setInvalidDecl]
https://bugs.kde.org/show_bug.cgi?id=397045 --- Comment #7 from Guillaume Racicot --- It seems the crash now has a workaround. When opening the crashing project, I click the "Stop All" button as soon as the initial parsing starts. Then, everything seems to work at that point. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 394055] New: Crash when autocomplete with is_detected
https://bugs.kde.org/show_bug.cgi?id=394055
Bug ID: 394055
Summary: Crash when autocomplete with is_detected
Product: kdevelop
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Keywords: drkonqi
Severity: normal
Priority: NOR
Component: general
Assignee: kdevelop-bugs-n...@kde.org
Reporter: gufi...@gmail.com
Target Milestone: ---
Application: kdevelop (5.2.40)
Qt Version: 5.10.1
Frameworks Version: 5.45.0
Operating System: Linux 4.16.6-1-ARCH x86_64
Distribution: "Arch Linux"
-- Information about the crash:
- What I was doing when the application crashed:
Typing a character, invoking autocompletion.
It doesn't happen for any templates, but when using a particular set of
templates it crashes every time.
I implemented the `is_detected` idiom and it triggered the bug.
This code makes it crash for me:
#include
template
struct voider {
using type = void;
};
template
using void_t = typename voider::type;
namespace detail {
template
class Op, typename... Args>
struct detector {
using value_t = std::false_type;
using type = Default;
};
template class Op, typename...
Args>
struct detector>, Op, Args...> {
using value_t = std::true_type;
using type = Op;
};
} // namespace detail
// <--- there
When tying a character just before the comment saying `there`, kdevelop
crashes. I use the current master branch
The crash can be reproduced every time.
-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7a9f46a1c0 (LWP 11302))]
Thread 19 (Thread 0x7f7a09ffb700 (LWP 11426)):
#0 0x7f7a9197b07c in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1 0x7f7a96881f9c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2 0x7f7a9d85752f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3 0x7f7a9d85b719 in () at /usr/lib/libKF5ThreadWeaver.so.5
#4 0x7f7a9d8566fd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5 0x7f7a9d85b772 in () at /usr/lib/libKF5ThreadWeaver.so.5
#6 0x7f7a9d8566fd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7 0x7f7a9d85b772 in () at /usr/lib/libKF5ThreadWeaver.so.5
#8 0x7f7a9d8566fd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#9 0x7f7a9d85b772 in () at /usr/lib/libKF5ThreadWeaver.so.5
#10 0x7f7a9d8566fd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#11 0x7f7a9d85b772 in () at /usr/lib/libKF5ThreadWeaver.so.5
#12 0x7f7a9d8566fd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#13 0x7f7a9d85b772 in () at /usr/lib/libKF5ThreadWeaver.so.5
#14 0x7f7a9d8566fd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#15 0x7f7a9d85b772 in () at /usr/lib/libKF5ThreadWeaver.so.5
#16 0x7f7a9d8566fd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#17 0x7f7a9d85b772 in () at /usr/lib/libKF5ThreadWeaver.so.5
#18 0x7f7a9d8566fd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#19 0x7f7a9d85b772 in () at /usr/lib/libKF5ThreadWeaver.so.5
#20 0x7f7a9d8566fd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#21 0x7f7a9d85b772 in () at /usr/lib/libKF5ThreadWeaver.so.5
#22 0x7f7a9d8566fd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#23 0x7f7a9d85b772 in () at /usr/lib/libKF5ThreadWeaver.so.5
#24 0x7f7a9d8566fd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#25 0x7f7a9d85b772 in () at /usr/lib/libKF5ThreadWeaver.so.5
#26 0x7f7a9d8566fd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#27 0x7f7a9d85b772 in () at /usr/lib/libKF5ThreadWeaver.so.5
#28 0x7f7a9d8566fd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#29 0x7f7a9d85b772 in () at /usr/lib/libKF5ThreadWeaver.so.5
#30 0x7f7a9d8566fd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#31 0x7f7a9d8
[elisa] [Bug 391496] Crash when spamming the "Configure Elisa" action through hotkeys
https://bugs.kde.org/show_bug.cgi?id=391496 --- Comment #2 from Guillaume Racicot --- Yes it fixed the crash, thank you! -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 394055] Crash when autocomplete with is_detected
https://bugs.kde.org/show_bug.cgi?id=394055 Guillaume Racicot changed: What|Removed |Added Version|unspecified |git master Component|general |Code completion -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 394055] Crash when autocomplete with is_detected
https://bugs.kde.org/show_bug.cgi?id=394055 Guillaume Racicot changed: What|Removed |Added Platform|Archlinux Packages |Compiled Sources -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 316557] wrong image size (always square) and video (only image) lagging
https://bugs.kde.org/show_bug.cgi?id=316557 Guillaume GAUTIER changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 297390] When wide characters appear on a line, Konsole cuts off half a letter
https://bugs.kde.org/show_bug.cgi?id=297390 Guillaume BINET changed: What|Removed |Added CC||g...@gootz.net --- Comment #24 from Guillaume BINET --- Reported: 2012-04-03, it feels like the other one is the duplicate ! :) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 376604] New: Kdenlive crash when opening video source
https://bugs.kde.org/show_bug.cgi?id=376604 Bug ID: 376604 Summary: Kdenlive crash when opening video source Product: kdenlive Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: yog...@wanadoo.fr Target Milestone: --- When I enter in my video folder to open a mkv file, the window freeze. gstreamer1.0-libav version 1.8.3-1 Kdenlive 16.12.2 from the kdenlive ppa:kdenlive/kdenlive-stable Kubuntu 16.10 x64 Here the backtrace: ERROR: Caught a segmentation fault while loading plugin file: /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstlibav.so Please either: - remove it and restart. - run with --gst-disable-segtrap --gst-disable-registry-fork and debug. (kdenlive:19032): GStreamer-WARNING **: Trying to join task 0x55b2b0735dd0 from its thread would deadlock. You cannot change the state of an element from its streaming thread. Use g_idle_add() or post a GstMessage on the bus to schedule the state change from the main thread. KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kdenlive path = /usr/bin pid = 19032 KCrash: Arguments: /usr/bin/kdenlive KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 The X11 connection broke: I/O error (code 1) XIO: fatal IO error 88 (Opération de type socket sur un type non socket) on X server ":0" after 36 requests (36 known processed) with 0 events remaining. QSocketNotifier: Socket notifiers cannot be enabled or disabled from another thread QThreadStorage: Thread 0x7f6be4075820 exited after QThreadStorage 15 destroyed [1]+ Arrêtékdenlive -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 376604] Kdenlive crash when opening video source
https://bugs.kde.org/show_bug.cgi?id=376604 Guillaume Debray changed: What|Removed |Added CC||yog...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 376604] Kdenlive crash when opening video source
https://bugs.kde.org/show_bug.cgi?id=376604 --- Comment #2 from Guillaume Debray --- (In reply to Wegwerf from comment #1) > Can you play your mkv file using ffplay, and melt? Yes, ffplay and melt can play the video. Duration: 00:14:48.06, start: 0.00, bitrate: 1070 kb/s Stream #0:0: Video: hevc (Main), yuv420p(tv), 1920x832, SAR 1:1 DAR 30:13, 24 fps, 24 tbr, 1k tbn, 1k tbc (default) Stream #0:1: Audio: aac (LC), 48000 Hz, stereo, fltp (default) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 376604] Kdenlive crash when opening video source
https://bugs.kde.org/show_bug.cgi?id=376604 --- Comment #4 from Guillaume Debray --- The video is easy to find: https://durian.blender.org/download/ I have downloaded the 720p mkv file (600MB) In my home folder, a new folder is created and only this video is in this folder. When I go to this folder and want to select this video, kdenlive crashes. With another video (not mkv but mp4 for example), no crash. It's the presence of mkv file in the folder I think. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 376604] Kdenlive crash when opening video source
https://bugs.kde.org/show_bug.cgi?id=376604 --- Comment #5 from Guillaume Debray --- An other thing: With the -i flag, no problem to load the video. kdenlive -i /home/guillaume/essai_kden/Sintel.2010.720p.mkv -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368331] To display the eraser mode
https://bugs.kde.org/show_bug.cgi?id=368331 Guillaume Audirac changed: What|Removed |Added CC||guillaume.audi...@gmail.com --- Comment #3 from Guillaume Audirac --- I would also be in favor of such a feature. Identifying from the cursor appearance that the brush eraser mode is enabled would make it more comfortable. Even more with large screens and "Show Canvas Only" mode. Changing its shape would NOT be ideal as all brushes has their own shape, but simply filling the cursor shape with a plain color, the same as the outline color basically, and only when the stylus tip is not pressed (so when the brush is not drawing). With this behavior, it might even not be necessary to add an additional configuration entry to enable/disable this feature. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 384574] New: Error on import with backends
https://bugs.kde.org/show_bug.cgi?id=384574 Bug ID: 384574 Summary: Error on import with backends Product: skrooge Version: 2.9.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: guillaume.st...@gmail.com CC: steph...@mankowski.fr Target Milestone: --- I'm trying the "import with backends" feature; But whatever the date display option set in skrooge, I've git the skrooge error: [ERR-5] Date format not supported When I'm using command line with boobank everything looks good... boobank> list Account BalanceComing --+--+-- #1 (ing)ING Direct Vie (Multi supxxx.xx #2 (ing)Compte Courant xxx.xx --+--+-- Total (EUR).xx 0.00 boobank> history 2 Date Category Label Amount ++---+--- 2017-09-06 Transfer ipeca prevoyance 6.90 2017-09-07 Orderamaline assurances : fr09zzz543921 ++001ac13000375 -4.90 -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 384574] Error on import with backends
https://bugs.kde.org/show_bug.cgi?id=384574 --- Comment #2 from Guillaume Stamm --- Created attachment 107787 --> https://bugs.kde.org/attachment.cgi?id=107787&action=edit snapshot of boobank commands The issue comes from, the account list. Look at the snapshot, the "list" command does not give the same result if it is done inside boobank or directly from command line. Then the command: boobank -q -f csv history 2 -s rdate,type,raw,label,amount returns: Error(ing): Account not found and the command: boobank -q -f csv history CC-4167961@ing -s rdate,type,raw,label,amount rdate;type;raw;label;amount returns: 2017-09-06;1;virement sepa recu ipeca prevoyance;ipeca prevoyance;6.90 ... -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 384574] Error on import with backends
https://bugs.kde.org/show_bug.cgi?id=384574
--- Comment #4 from Guillaume Stamm ---
by looking at the trace:
Skrooge execute this:
boobank ls -q -f csv -s id,balance | grep -E "id|"
with result this: (some "xxx" has been added by myself)
id;balance
00020031401@creditmutuel;xxx5.81
00020293601@creditmutuel;xxx5.55
00033550540@creditmutuel;xxx9.02
00033550560@creditmutuel;xxx5.16
00033550565@creditmutuel;xxx55.56
00037869560@creditmutuel;xxx5.87
102780303400033550502@creditmutuel;xxx19.00
57419614@ing;xxx6.00
CC-4167961@ing;xxx32.34
LEO-10001356004@ing;xxx29.17
TITRE-77800057098@ing;xxx11.97
then skrooge executes these commands (and some others)
boobank -q -f csv history "CC-4167961@ing" -s
rdate,type,raw,label,amount --condition "rdate>2000-01-01 OR date>2000-01-01 OR
rdate>2000-01-01 00:00:00 OR date>2000-01-01 00:00:00" -n 9
boobank -q -f csv history "LEO-10001356004@ing" -s
rdate,type,raw,label,amount --condition "rdate>2000-01-01 OR date>2000-01-01 OR
rdate>2000-01-01 00:00:00 OR date>2000-01-01 00:00:00" -n 9
boobank -q -f csv history "TITRE-77800057098@ing" -s
rdate,type,raw,label,amount --condition "rdate>2000-01-01 OR date>2000-01-01 OR
rdate>2000-01-01 00:00:00 OR date>2000-01-01 00:00:00" -n 9
I think that my issue is linked to the nature of the last account that is a
"stock"
If I execute directly the boobank commands:
boobank -q -f csv history "CC-4167961@ing" -s
rdate,type,raw,label,amount --condition "rdate>2000-01-01 OR date>2000-01-01 OR
rdate>2000-01-01 00:00:00 OR date>2000-01-01 00:00:00" -n 3
=>
rdate;type;raw;label;amount
2017-09-06;1;virement sepa recu ipeca prevoyance;ipeca prevoyance;6.90
2017-09-07;2;prlv sepa amaline assurances : fr09zzz543921
++001ac13000375 de amaline assurances : ++001ac13000375 fr09zzz543921;amaline
assurances : fr09zzz543921 ++001ac13000375 de amaline assurances :
++001ac13000375 fr09zzz543921;-4.90
2017-09-07;2;prlv sepa maif 79038 niort cedex : fr70zzz000884
0013511673r de maif 79038 niort cedex : 0013511673r fr70zzz000884;maif
79038 niort cedex : fr70zzz000884 0013511673r de maif 79038 niort cedex :
0013511673r fr70zzz000884;-173.33
this result looks good, but now
boobank -q -f csv history "TITRE-77800057098@ing" -s
rdate,type,raw,label,amount --condition "rdate>2000-01-01 OR date>2000-01-01 OR
rdate>2000-01-01 00:00:00 OR date>2000-01-01 00:00:00" -n 3
=>
Not available;0;CISCO SYSTEMS COUPONS;CISCO SYSTEMS COUPONS;10.24
Not available;0;ADVINI COUPONS;ADVINI COUPONS;24.26
Not available;0;IBM COUPONS;IBM COUPONS;10.72
here the date is a problème
Hence the issue does not come from Skrooge, neither from weboob/boobank, but
from the bank itself
But to not block end user, I see 2 options:
1- add a feature allowing to select witch account, from a bank, you are
interested in
2- when the date can not be read, put a date in the futur or date of the day
in any case it is sad that actually all accounts of the import are "rollback"
for information the trace of the error is:
##Input parameter [iSqlOrder]=[ANALYZE]
##Input filename=file:///tmp/skrooge-GL8ofY/titre-77800057...@ing.csv
##Input local filename=/tmp/skrooge-GL8ofY/titre-77800057...@ing.csv
## [36m>virtual SKGError SKGImportPluginCsv::importFile()[39m
##[37m>virtual SKGError SKGDocument::beginTransaction(const
QString&, int, const QDateTime&, bool)[39m
##Input parameter [name]=[#INTERNAL#Import CSV file] [nb step]=[3]
[refresh]=[Y]
##[37mvirtual SKGError SKGDocument::sendMessage(const QString&,
SKGDocument::MessageType, const QString&)[39m
## [31m>virtual int SKGDocument::getCurrentTransaction()
const[39m
## [31mvirtual SKGError SKGObjectBase::save(bool, bool)[39m
## Input parameter [iSqlOrder]=[INSERT INTO doctransactionmsg
('t_type','rd_doctransaction_id','t_message') VALUES ('I','17649','Mapping
used: date|mode|comment|payee|amount')]
##[32m>virtual SKGError SKGObjectBase::load()[39m
##[32mvirtual int SKGImportPluginCsv::getCSVHeaderIndex()[39m
##[37mvirtual QChar SKGImportPluginCsv::getCSVSeparator()[39m
##[37mstatic QString SKGServices::getDateFormat(const
QStringList&)[39m
##[37mvirtual SKGError SKGDocument::endTransaction(bool)[39m
## [31m>virtual int SKGDocument::getCurrentTransaction()
const[39m
## [31mvirtual SKGError
SKGImportExportManager::setDefaultAccount(SKGAccountObject*)[39m
##[33mvirtual SKG
[skrooge] [Bug 384574] Error on import with backends
https://bugs.kde.org/show_bug.cgi?id=384574 --- Comment #6 from Guillaume Stamm --- (In reply to Stephane MANKOWSKI from comment #5) > Proposal 1 is available in backend settings. > I am closing this incident. Reopen it if needed. Selecting accounts in backend settings works perfectly, sorry for having missed this. For information, I checked the "date/rdate/vdate" on the account generating the error, and only the "date" is valuated correctly, the two others returns "Not loaded" -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 384659] New: Weboob / Boobank date condition
https://bugs.kde.org/show_bug.cgi?id=384659 Bug ID: 384659 Summary: Weboob / Boobank date condition Product: skrooge Version: 2.9.0 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: guillaume.st...@gmail.com CC: steph...@mankowski.fr Target Milestone: --- Hello, I have a small feature request on boobank import. When skrooge looks for operations with boobank the date condition is set to ">2000-01-01" This date condition does not change from time to time, at each import. It would be nice to either: 1- automatically set this date to the last_download_date_for_this_account or 2- add a parameter, on weboob backend settings to be able to set this date. Why I am requesting this?? On some bank the number of imported operation could be huge! lots more than 1000. There is an import performance issue (this is limited: I tested on command line ">2000-01-01" and ">2017-07-01" with only 20% improvement) But my real need, is not performances, it is on the old operations (many of them), previously imported by .qif, .ofx... (since years), for these operations boobank/skrooge import them again, and I have no other choice than to delete them… but at next boobank import they come again !! :-( Remark: it is not the case for operations, already imported by boobank, I think that scrooge stores an operation identification number to avoid import duplicates. I hope, I was clear enough!! Thanks Guillaume -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 384659] Weboob / Boobank date condition
https://bugs.kde.org/show_bug.cgi?id=384659
--- Comment #1 from Guillaume Stamm ---
I found this part of code: skgimportpluginbackend.cpp
if (currentList != lastList || !lastDownload.isValid()) {
nbToDownload = 9;
fromDate = QStringLiteral("2000-01-01");
} else {
nbToDownload = qMax(lastDownload.daysTo(QDate::currentDate()) * 10,
qint64(20));
fromDate = SKGServices::dateToSqlString(lastDownload.addDays(-4));
}
but I do not know why I am not in the second case, using "lastDownload"
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 378789] New: Crash when restarting kwin after suspend wakeup
https://bugs.kde.org/show_bug.cgi?id=378789 Bug ID: 378789 Summary: Crash when restarting kwin after suspend wakeup Product: kwin Version: 5.9.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: gufi...@gmail.com Target Milestone: --- Application: kwin_x11 (5.9.4) Qt Version: 5.8.0 Frameworks Version: 5.32.0 Operating System: Linux 4.10.9-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: "kwin_x11 --replace" in krunner - Unusual behavior I noticed: The whole screen was flikering with distorted texture of window, even in the lock screen. The only way to make my computer useable again was to restart kwin The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7685aaf840 (LWP 635))] Thread 6 (Thread 0x7f764e209700 (LWP 1055)): #0 0x7f76854fe76b in ppoll () at /usr/lib/libc.so.6 #1 0x7f7682b822f9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f7682b8396a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f7682b3089a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f7682952a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f76829576d8 in () at /usr/lib/libQt5Core.so.5 #6 0x7f767e7442e7 in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f768550854f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f764da08700 (LWP 749)): #0 0x7f767e74a756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7681ac1234 in () at /usr/lib/libQt5Script.so.5 #2 0x7f7681ac1279 in () at /usr/lib/libQt5Script.so.5 #3 0x7f767e7442e7 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f768550854f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f7661651700 (LWP 729)): #0 0x7f767e74aca6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7661909e44 in () at /usr/lib/libGLX_nvidia.so.0 #2 0x7f764efd5394 in () at /usr/lib/libnvidia-glcore.so.378.13 #3 0x7f766190912c in () at /usr/lib/libGLX_nvidia.so.0 #4 0x7f767e7442e7 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f768550854f in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f766a0fc700 (LWP 686)): #0 0x7f76854fe76b in ppoll () at /usr/lib/libc.so.6 #1 0x7f7682b822f9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f7682b8396a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f7682b3089a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f7682952a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f767c615125 in () at /usr/lib/libQt5DBus.so.5 #6 0x7f76829576d8 in () at /usr/lib/libQt5Core.so.5 #7 0x7f767e7442e7 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f768550854f in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f766c24c700 (LWP 663)): #0 0x7f76854fe67d in poll () at /usr/lib/libc.so.6 #1 0x7f76846178e0 in () at /usr/lib/libxcb.so.1 #2 0x7f7684619679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7f766d328239 in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7f76829576d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f767e7442e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f768550854f in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f7685aaf840 (LWP 635)): [KCrash Handler] #6 0x7f768544fa10 in raise () at /usr/lib/libc.so.6 #7 0x7f768545113a in abort () at /usr/lib/libc.so.6 #8 0x7f768293de21 in () at /usr/lib/libQt5Core.so.5 #9 0x7f7682951d04 in QThread::~QThread() () at /usr/lib/libQt5Core.so.5 #10 0x7f7682951df9 in QThread::~QThread() () at /usr/lib/libQt5Core.so.5 #11 0x7f7682b5c411 in QObjectPrivate::deleteChildren() () at /usr/lib/libQt5Core.so.5 #12 0x7f7682b65d6f in QObject::~QObject() () at /usr/lib/libQt5Core.so.5 #13 0x7f76696d8c69 in KWin::X11StandalonePlatform::~X11StandalonePlatform() () at /usr/lib/qt/plugins/org.kde.kwin.platforms/KWinX11Platform.so #14 0x7f7682b5c411 in QObjectPrivate::deleteChildren() () at /usr/lib/libQt5Core.so.5 #15 0x7f7682b65d6f in QObject::~QObject() () at /usr/lib/libQt5Core.so.5 #16 0x7f7682b33f56 in QCoreApplication::~QCoreApplication() () at /usr/lib/libQt5Core.so.5 #17 0x7f7683814dc1 in QApplication::~QApplication() () at /usr/lib/libQt5Widgets.so.5 #18 0x7f76857c7834 in () at /usr/lib/libkdeinit5_kwin_x11.so #19 0x7f76857c93e0 in kdemain
[kwin] [Bug 378789] Crash when restarting kwin after suspend wakeup
https://bugs.kde.org/show_bug.cgi?id=378789 --- Comment #2 from Guillaume Racicot --- Indeed. I'll try to build kwin with debugging symbols and reproduce the bug. As additional info, the flickering is not always there, but the crash is. -- You are receiving this mail because: You are watching all bug changes.
