[kmymoney] [Bug 492110] No visible difference between entered and scheduled transactions in ledgers view under Gnome 46
https://bugs.kde.org/show_bug.cgi?id=492110 Ian Neal changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Ian Neal --- Using in .bashrc or .profile the following: export QT_QPA_PLATFORMTHEME=gnome seems to fix this issue. Should some sort of note be added about this? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 492111] New: Using enter key does not operate highlighted action in a dialog on Gnome
https://bugs.kde.org/show_bug.cgi?id=492111 Bug ID: 492111 Summary: Using enter key does not operate highlighted action in a dialog on Gnome Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ux-ui Assignee: kmymoney-de...@kde.org Reporter: iann_bugzi...@blueyonder.co.uk Target Milestone: --- SUMMARY When a dialog comes up, one of the buttons is highlighted. Pressing the enter key should carry out that action but doesn't. STEPS TO REPRODUCE 1. Use kmymoney on Gnome 2. Enter a transaction into an account that pops up the Exchange rate dialog 3. Note that the OK button appears to be highlighted 4. Press enter / CR key on keyboard OBSERVED RESULT Nothing happens EXPECTED RESULT Enter / CR key activates OK button SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.5-200.fc40.x86_64 (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION If you use the tab key to cycle round field / buttons until it reaches the OK button again and press enter/CR key, it does carry out the OK button's action. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 492110] New: No visible difference between entered and scheduled transactions in ledgers view under Gnome 46
https://bugs.kde.org/show_bug.cgi?id=492110 Bug ID: 492110 Summary: No visible difference between entered and scheduled transactions in ledgers view under Gnome 46 Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ux-ui Assignee: kmymoney-de...@kde.org Reporter: iann_bugzi...@blueyonder.co.uk Target Milestone: --- SUMMARY >From the ledgers view entered and scheduled transactions look the same when using Gnome 46 STEPS TO REPRODUCE 1. Use Gnome as desktop environment in Fedora 40 2. Start kmymoney and create some transactions and some scheduled transactions against an account 3. View ledger for that account OBSERVED RESULT Both entered and scheduled transactions look the same EXPECTED RESULT Scheduled transactions should be a different light colour font than the entered transactions SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.5-200.fc40.x86_64 (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION Was fine with Gnome on Fedora 38 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 419897] Error when accessing filesystem. sshfs finished with exit code 1
https://bugs.kde.org/show_bug.cgi?id=419897 --- Comment #44 from Ian Proudler --- I've just had an update to the mobile app. It now works. Thanks to whoever fixed it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 491877] New: Krita crashes after ctrl+v
https://bugs.kde.org/show_bug.cgi?id=491877 Bug ID: 491877 Summary: Krita crashes after ctrl+v Classification: Applications Product: krita Version: 5.2.3 Platform: Compiled Sources OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: zooo...@gmail.com Target Milestone: --- Created attachment 172738 --> https://bugs.kde.org/attachment.cgi?id=172738&action=edit error log *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY I opened a few files (13 to be precise), one of the files has many layers, the rest are just a single-layer image. The task was to copy some of the layers from many-layered file to other files. Noting extraordinary, and I did this many times on my PC, but on my laptop Krita crashes constantly. STEPS TO REPRODUCE 1. Open file with many layers and several files with a single layer 2. Copy one of the layers from the many-layered file 3. Paste to one of the single-layered files ??? OBSERVED RESULT Krita crashes! EXPECTED RESULT Krita doesn't crash and I succesfully paste what I've copied SOFTWARE/OS VERSIONS Windows: 10 home macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I attached a log in txt file -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 490698] Discover crash on application search
https://bugs.kde.org/show_bug.cgi?id=490698 Ian Newton changed: What|Removed |Added Version|6.0.5 |6.1.3 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 490698] Discover crash on application search
https://bugs.kde.org/show_bug.cgi?id=490698 Ian Newton changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|UNMAINTAINED|--- Ever confirmed|0 |1 --- Comment #3 from Ian Newton --- Crash persists for latest version available discover-6.1.3-1 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 490698] New: Discover crash on application search
https://bugs.kde.org/show_bug.cgi?id=490698 Bug ID: 490698 Summary: Discover crash on application search Classification: Applications Product: Discover Version: 6.0.5 Platform: Manjaro OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: i.new...@c-org.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (6.0.5) Qt Version: 6.7.2 Frameworks Version: 6.3.0 Operating System: Linux 6.10.0-3-MANJARO x86_64 Windowing System: X11 Distribution: Manjaro Linux DrKonqi: 6.0.5 [CoredumpBackend] -- Information about the crash: Discover loads OK, then searching for an installed application shows the application then crashes. The crash can be reproduced every time. -- Backtrace (Reduced): #4 0x72a1efecd224 in ??? () at /usr/lib/libKF6Attica.so.6 #5 0x72a22678c00f in QObject::event (this=0x5ad5a058e7f0, e=0x5ad59f943550) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobject.cpp:1452 #6 0x72a2288fc51c in QApplicationPrivate::notify_helper (this=, receiver=0x5ad5a058e7f0, e=0x5ad59f943550) at /usr/src/debug/qt6-base/qtbase/src/widgets/kernel/qapplication.cpp:3287 #7 0x72a226744d28 in QCoreApplication::notifyInternal2 (receiver=0x5ad5a058e7f0, event=event@entry=0x5ad59f943550) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qcoreapplication.cpp:1142 #8 0x72a2267450eb in QCoreApplication::sendEvent (receiver=, event=0x5ad59f943550) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qcoreapplication.cpp:1583 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 490698] Discover crash on application search
https://bugs.kde.org/show_bug.cgi?id=490698 --- Comment #1 from Ian Newton --- Created attachment 171927 --> https://bugs.kde.org/attachment.cgi?id=171927&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 419897] Error when accessing filesystem. sshfs finished with exit code 1
https://bugs.kde.org/show_bug.cgi?id=419897 --- Comment #36 from Ian Proudler --- In case it helps. I am still able to access my SMS messages from my PC. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 463636] After sleep, KDE Connect complains about dBus service files
https://bugs.kde.org/show_bug.cgi?id=463636 --- Comment #3 from Ian H. Chamberlain --- To add onto my previous comment: I reproduced again today, and I realized that actually the `dbus-daemon` process was still running, but `kdeconnectd` was not! During normal operation I see 3 processes - `kdeconnectd`, `kdeconnect-indicator`, and `dbus-daemon`, but when the issue occurred I only saw `kdeconnect-indicator` and `dbus-daemon`. Perhaps there is something wrong with the launch daemon configuration that prevents it from restarting after sleep... I'll keep digging in and see if I can find any other clues. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425758] Edge detection pushback based on wrong monitor in overlapping setups
https://bugs.kde.org/show_bug.cgi?id=425758 --- Comment #8 from Ian Silvester --- I confirm that this behaviour is no longer reproducible at all under Plasma 6.1. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 419897] Error when accessing filesystem. sshfs finished with exit code 1
https://bugs.kde.org/show_bug.cgi?id=419897 --- Comment #30 from Ian Proudler --- Just discovered that I can 'push' a file from the smartphone to the PC. It seem it's the 'pull' that's the issue. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 419897] Error when accessing filesystem. sshfs finished with exit code 1
https://bugs.kde.org/show_bug.cgi?id=419897 Ian Proudler changed: What|Removed |Added CC||i.proud...@oxon.org --- Comment #29 from Ian Proudler --- I've been using KDE Connect quite happily for years but suddenly it is now producing this error. 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-113-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 27.3 GiB of RAM Graphics Processor: RENOIR Samsung Galaxy A20e Android 11 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 487681] Consider changing the setting to drag windows from any empty view area to only do this for the Tools Area
https://bugs.kde.org/show_bug.cgi?id=487681 --- Comment #3 from Ian Newton --- (In reply to Nate Graham from comment #2) > This is a Breeze setting. You're welcome to turn it off in System Settings > > Colors & Themes > Application Style > Click the pencil icon on "Breeze" > > Windows' drag mode> Set it to a different value from what it's currently set > to. > > We can consider changing the default value, as this does seem to accumulate > a lot of complaints, particularly from Kdenlive users. > > I bet if we changed this to only allow dragging from the Tools Area > (Titlebar, menubar, and toolbar), nobody would complain. Let's consider it. Having a play with the settings in Kdenlive it is possible to select Breeze as window style which now has "windows drag mode" set for header only. Most other windows only have minor irritations like the scroll bar becoming the drag item for the window. I have used QTcurve style for some time as it has many config options as my default. It still works well in Plasma 6 though the configure panel no longer appears. Editing the config file allows adjustments though a fresh config may be hard work. Maybe I can get the developer to fix this and ensure Plasma 6 compatability. It probably does not have a setting for this at the moment. Alternatively a global setting for drag behaviour would make sense for all styles? -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 477478] Preview of running apps on taskbar are "empty"
https://bugs.kde.org/show_bug.cgi?id=477478 --- Comment #22 from ian karlsson --- Correction to the above, bug #473703 is what I was referring to. -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 477478] Preview of running apps on taskbar are "empty"
https://bugs.kde.org/show_bug.cgi?id=477478 ian karlsson changed: What|Removed |Added CC||themvru...@gmail.com --- Comment #21 from ian karlsson --- I have noticed this as well, but only with one application Brave (web browser). To me, it started happening after I locked the desktop and left the computer idle overnight. All other applications had thumbnails rendering OK and restarting Brave would temporarily fix the issue. The error I saw in the journalctl output is similar to what has been reported by others: plasmashell[66949]: kpipewire_logging: PipeWire remote error: -2 unknown resource 8 op:4 I also noticed bug #477478 which seems to be duplicate. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 487681] Clicking and holding any item in KCM panel list or the scroll bar results in the whole window moving (Plasma 6)
https://bugs.kde.org/show_bug.cgi?id=487681 --- Comment #1 from Ian Newton --- This behaviour also affects some other applications such as Kdenlive where clicking and holding the video timeline selects window move in the same way. This makes editing almost impossible. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 487681] Clicking and holding any item in KCM panel list or the scroll bar results in the whole window moving (Plasma 6)
https://bugs.kde.org/show_bug.cgi?id=487681 Ian Newton changed: What|Removed |Added Summary|Clicking and holding any|Clicking and holding any |item in KCM panel list or |item in KCM panel list or |the scroll bar results in |the scroll bar results in |the whole window moving |the whole window moving ||(Plasma 6) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 487681] New: Clicking and holding any item in KCM panel list or the scroll bar results in the whole window moving
https://bugs.kde.org/show_bug.cgi?id=487681 Bug ID: 487681 Summary: Clicking and holding any item in KCM panel list or the scroll bar results in the whole window moving Classification: Applications Product: systemsettings Version: 6.0.4 Platform: Manjaro OS: Linux Status: REPORTED Keywords: accessibility, reproducible, usability Severity: normal Priority: NOR Component: kcmshell Assignee: plasma-b...@kde.org Reporter: i.new...@c-org.com Target Milestone: --- SUMMARY Clicking and holding any item in KCM panel list or the scroll bar results in the whole window moving STEPS TO REPRODUCE 1. Clicking and holding any item in panel list or the scroll bar results in the whole window moving 2. 3. OBSERVED RESULT results in the whole window moving EXPECTED RESULT The item should be selected or the scroll bar should work as expected (drag up or down) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.9.0-1-MANJARO (64-bit) (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 487325] Mouse select moves whole window under KDE plasma 6
https://bugs.kde.org/show_bug.cgi?id=487325 --- Comment #2 from Ian Newton --- Created attachment 169870 --> https://bugs.kde.org/attachment.cgi?id=169870&action=edit Screenshot of window settings -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 487325] Mouse select moves whole window under KDE plasma 6
https://bugs.kde.org/show_bug.cgi?id=487325 --- Comment #1 from Ian Newton --- As a work-around, I have set the application window rules (KDE plasma window frame) for the main window position to "Force". This means the window cannot be moved once Kdenlive is open. So I set an optimal size and position before adding these settings. Resizing is allowed after the initial size is set so F11 full-screen still works. Not ideal but workable! Looks like there is some work to do around the select and drag of the timeline to prevent this behaviour? See the attached snap of the KDE Plasma window settings. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 487325] Mouse select moves whole window under KDE plasma 6
https://bugs.kde.org/show_bug.cgi?id=487325 Ian Newton changed: What|Removed |Added Platform|Other |Manjaro CC||i.new...@c-org.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 487325] New: Mouse select moves whole window under KDE plasma 6
https://bugs.kde.org/show_bug.cgi?id=487325 Bug ID: 487325 Summary: Mouse select moves whole window under KDE plasma 6 Classification: Applications Product: kdenlive Version: 24.04.90 Platform: Other OS: Linux Status: REPORTED Keywords: regression, reproducible, usability Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: i.new...@c-org.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY With a clip in the timeline selecting the clip to perform any edit action reverts to the global window select to move the window. It seems that this is implemented for all native applications like Kate and Dolphin under Plasma 6 where any nonactive surface (frame border etc) as well as the expected header shows mouse select pointer. Any edit or display area (lists etc) do not. As it is the user has less than a second to make any drag action before the whole window moves with the mouse. Not a great user experience? I don't remember having this behavior in Plasma 5 before upgrading. STEPS TO REPRODUCE 1. Select item in timeline with mouse 2. Within 1-2 seconds the window grab appears 3. OBSERVED RESULT The whole window moves with the mouse EXPECTED RESULT Drag/resize operations should work with the clip or item SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.9.0-1-MANJARO (64-bit) (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 429584] growisofs crashes @ 99%
https://bugs.kde.org/show_bug.cgi?id=429584 --- Comment #6 from Ian Proudler --- Re. "independent of file size" - Which file sizes have you tried? I'm sorry it's been a long time since I first raised this issue and I don't remember what sizes I tried. I imagine I made sure that the file would fit. I've just tried to burn a 2.5GiB .iso (in simulate mode) and it failed (see below). Note I have been using k3b with my 'new' optical drive without any trouble for the past three years so it seems to be an issue with the drive itself. It is an old drive and I don't use it to write any more so I wonder if we should just close this issue. If you want more information I'm happy to help. Note my system has changed since the last time I tried using the 'old' drive. - 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-97-generic (64-bit) Graphics Platform: X11 Processor: 1 × Intel® Core™ i7-4770 CPU @ 3.40GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4600 --- Burned media --- DVD-R Sequential Devices --- TSSTcorp CDDVDW SH-S223F SB00 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump] [%7] System --- K3b Version: 21.12.3 KDE Version: 5.91.0 Qt Version: 5.15.3 Kernel: 5.15.0-97-generic Used versions --- growisofs: 7.1 growisofs --- Executing 'builtin_dd if=/dev/fd/0 of=/dev/sr0 obs=32k seek=0' /dev/sr0: engaging DVD-R DAO upon user request... /dev/sr0: reserving 1289054 blocks /dev/sr0: "Current Write Speed" is 8.2x1352KBps. 655360/2639982592 ( 0.0%) @0.0x, remaining 469:51 RBU 100.0% UBU 4.8% 655360/2639982592 ( 0.0%) @0.0x, remaining 671:12 RBU 100.0% UBU 100.0% 655360/2639982592 ( 0.0%) @0.0x, remaining 872:34 RBU 100.0% UBU 100.0% 655360/2639982592 ( 0.0%) @0.0x, remaining 1141:03 RBU 100.0% UBU 100.0% 655360/2639982592 ( 0.0%) @0.0x, remaining 1342:25 RBU 100.0% UBU 100.0% 655360/2639982592 ( 0.0%) @0.0x, remaining 1543:47 RBU 100.0% UBU 100.0% 8749056/2639982592 ( 0.3%) @1.8x, remaining 135:20 RBU 100.0% UBU 100.0% 36503552/2639982592 ( 1.4%) @6.0x, remaining 35:39 RBU 100.0% UBU 100.0% 64258048/2639982592 ( 2.4%) @6.0x, remaining 22:02 RBU 100.0% UBU 100.0% 85098496/2639982592 ( 3.2%) @4.5x, remaining 18:30 RBU 100.0% UBU 100.0% ... 2448588800/2639982592 (92.8%) @8.0x, remaining 0:24 RBU 100.0% UBU 99.9% 2484469760/2639982592 (94.1%) @7.8x, remaining 0:19 RBU 100.0% UBU 99.9% 2513338368/2639982592 (95.2%) @6.3x, remaining 0:15 RBU 100.0% UBU 99.9% 2550366208/2639982592 (96.6%) @8.0x, remaining 0:11 RBU 12.1% UBU 99.9% 2556788736/2639982592 (96.8%) @1.4x, remaining 0:10 RBU 100.0% UBU 99.9% 2593783808/2639982592 (98.3%) @8.0x, remaining 0:05 RBU 100.0% UBU 99.9% :-[ WRITE@LBA=13ab50h failed with SK=5h/ASC=21h/ACQ=04h]: Invalid argument :-( write failed: Invalid argument /dev/sr0: flushing cache growisofs command: --- /usr/bin/growisofs -Z /dev/sr0=/dev/fd/0 -use-the-force-luke=notray -use-the-force-luke=tty -use-the-force-luke=4gms -use-the-force-luke=tracksize:1289054 -use-the-force-luke=dummy -use-the-force-luke=dao:1289054 -dvd-compat -speed=8 -use-the-force-luke=bufsize:32m -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 481356] New: Unable to transition when video file contains multiple Audio tracks
https://bugs.kde.org/show_bug.cgi?id=481356 Bug ID: 481356 Summary: Unable to transition when video file contains multiple Audio tracks Classification: Applications Product: kdenlive Version: 23.08.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: id012c3...@blueyonder.co.uk Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Normally, a video file contains 1 video track and 1 audio track. To edit you drag the video onto the timeline and it goes into tracks V1 and A1. If you then want to cut out part you might want to transition from the first part to the second and you would drag the second piece of video to V2 and the corresponding audio would go to A2 - and you can then overlap the two clips and make whatever transitions you want. I have a video file which contains 1 video track and 2 audio tracks. When I drag that onto the timeline it occupies tracks V1, A1 and A2. If I cut out a piece and than drag V1 to V2, the audio shifts to A2 and A3. The 'new A2' buts up against the 'old A2' and therefore I cannot overlap the two clips. I cannot find a way to implement transitions. STEPS TO REPRODUCE 1. Import (or create) a clip with video and 2 Audio tracks 2. Cut and attempt to transition from 1st part to 2nd part 3. OBSERVED RESULT Audio tracks 'collide' EXPECTED RESULT There should be a way to do it - maybe allow that the original clip utilises tracks V1, A1 and A3 - then the shifted clip could utilise tracks V2, A2 and A4 SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 458072] Ctrl+. broken as a keybind
https://bugs.kde.org/show_bug.cgi?id=458072 --- Comment #14 from Ian H --- I have found the issue with this (it's not in anything kdevelop or kde, so this can be closed). Ubuntu seems to set the emoji keybind for the operating system to 'ctrl+.' and 'ctrl+;'. This can be removed by running ibus-setup and going to the emoji section. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 477356] Saving a file takes ten seconds before anything happens
https://bugs.kde.org/show_bug.cgi?id=477356 --- Comment #3 from Ian --- Apologies for taking so long to get back to this. It seems to be no longer happening, so it may have been a Thonny problem. Update(s) have been applied to Thonny since the problem was happening, and it seems to have gone away now. Apologies for wasting your time. -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 356183] JuK doesn't remember settings
https://bugs.kde.org/show_bug.cgi?id=356183 Ian Darwin changed: What|Removed |Added CC||i...@darwinsys.com --- Comment #2 from Ian Darwin --- Still a problem, at least for the "Player->Random Play" setting, presumably the others too. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 477356] New: Saving a file takes ten seconds before anything happens
https://bugs.kde.org/show_bug.cgi?id=477356 Bug ID: 477356 Summary: Saving a file takes ten seconds before anything happens Classification: Plasma Product: xdg-desktop-portal-kde Version: 5.27.9 Platform: Flatpak OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mogpl...@tpg.com.au CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org Target Milestone: --- Application: xdg-desktop-portal-kde (5.27.9) Qt Version: 5.15.11 Frameworks Version: 5.112.0 Operating System: Linux 6.5.4-1-default x86_64 Windowing System: X11 Distribution: openSUSE Tumbleweed DrKonqi: 5.27.9 [CoredumpBackend] -- Information about the crash: I was using Thonny (micropython editor), but the same thing happened every other time I tried to save a file. A button with KDE logo appears on the panel and the tumbler tumbles for maybe ten seconds. then the save dialog appears. Clicking a library causes the same th ing, KDE panel item and wait for ten seconds. The last time the portal actually crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Portal (xdg-desktop-portal-kde), signal: Segmentation fault PID: 4472 (xdg-desktop-por) UID: 1000 (ian) GID: 1000 (ian) Signal: 11 (SEGV) Timestamp: Wed 2023-11-22 19:54:13 AEDT (43s ago) Command Line: /usr/libexec/xdg-desktop-portal-kde Executable: /usr/libexec/xdg-desktop-portal-kde Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-xdg-desktop-portal-kde.service Unit: user@1000.service User Unit: plasma-xdg-desktop-portal-kde.service Slice: user-1000.slice Owner UID: 1000 (ian) Boot ID: 1f31a4839bc0416693324c2eda70b9a8 Machine ID: 29535661e97b4ebea7baeee4f9d533e9 Hostname: opensusian Storage: /var/lib/systemd/coredump/core.xdg-desktop-por.1000.1f31a4839bc0416693324c2eda70b9a8.4472.170064325300.zst (present) Size on Disk: 3.4M Message: Process 4472 (xdg-desktop-por) of user 1000 dumped core. Stack trace of thread 5847: #0 0x7f99d8491dec __pthread_kill_implementation (libc.so.6 + 0x91dec) #1 0x7f99d843f0c6 raise (libc.so.6 + 0x3f0c6) #2 0x7f99d9940d9a _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x7d9a) #3 0x7f99d843f190 __restore_rt (libc.so.6 + 0x3f190) #4 0x7f99d8491dec __pthread_kill_implementation (libc.so.6 + 0x91dec) #5 0x7f99d843f0c6 raise (libc.so.6 + 0x3f0c6) #6 0x7f99d843f190 __restore_rt (libc.so.6 + 0x3f190) #7 0x7f99d8514e11 pselect (libc.so.6 + 0x114e11) #8 0x7f99d64b6b37 n/a (libusbmuxd-2.0.so.6 + 0x4b37) #9 0x7f99d64b77a3 n/a (libusbmuxd-2.0.so.6 + 0x57a3) #10 0x7f99d848ff44 start_thread (libc.so.6 + 0x8ff44) #11 0x7f99d85184cc __clone3 (libc.so.6 + 0x1184cc) Stack trace of thread 4512: #0 0x7f99d848c4ee __futex_abstimed_wait_common (libc.so.6 + 0x8c4ee) #1 0x7f99d848f230 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x8f230) #2 0x7f99d02d1feb n/a (iris_dri.so + 0xd1feb) #3 0x7f99d031b8e7 n/a (iris_dri.so + 0x11b8e7) #4 0x7f99d848ff44 start_thread (libc.so.6 + 0x8ff44) #5 0x7f99d85184cc __clone3 (libc.so.6 + 0x1184cc) Stack trace of thread 4472: #0 0x7f99d8509d7f __poll (libc.so.6 + 0x109d7f) #1 0x7f99d9940198 n/a (libKF5Crash.so.5 + 0x7198) #2 0x7f99d9940d3d _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x7d3d) #3 0x7f99d843f190 __restore_rt (libc.so.6 + 0x3f190) #4 0x7f99d9381cf0 _ZNK7QWindow15transientParentEv (libQt5Gui.so.5 + 0x181cf0) #5 0x7f99d9381daa _ZNK7QWindow12isAncestorOfEPKS_NS_12AncestorModeE (libQt5Gui.so.5 + 0x181daa) #6 0x7f99da7a4354 _ZNK19QApplicationPrivate15isWindowBlockedEP7QWindowPS1_ (libQt5Widgets.so.5 + 0x1a4354) #7 0x7f99d93751d6 _ZN22QGuiApplicationPrivate15showModalWindowEP7QWindow (libQt5Gui.so.5 + 0x1751d6) #8 0x7f99d9388018 _ZN14QWindowPrivate10setVisibleEb (libQt5Gui.so.5 + 0x188018) #9 0x7f99da7dacd1 _ZN14QWidgetPrivate8show_sysEv (libQt5Widgets.so.5 + 0x1dacd1) #10 0x7f99da7e38bb _ZN14QWidgetPrivate11show_helperEv (libQt5Widgets.so.5 + 0x1e38bb) #11 0x7f99da7e6803 _ZN14QWidgetPrivate10setVisibleEb (libQt5Widgets.so
[plasmashell] [Bug 476637] New: Plasma crashes reriodically when running Hunyango plugin for Desktop Wallpaper settings.
https://bugs.kde.org/show_bug.cgi?id=476637 Bug ID: 476637 Summary: Plasma crashes reriodically when running Hunyango plugin for Desktop Wallpaper settings. Classification: Plasma Product: plasmashell Version: 5.27.9 Platform: Debian testing OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: i...@ossher.ca CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.9) Qt Version: 5.15.10 Frameworks Version: 5.107.0 Operating System: Linux 6.5.0-3-amd64 x86_64 Windowing System: Wayland Distribution: Debian GNU/Linux trixie/sid DrKonqi: 5.27.9 [CoredumpBackend] -- Information about the crash: With Wallpaper type set to Hunyango, Plasma would crash perodically, probably after each wallpper colour change. Was using Firefox at the time, not sure if this is related as well. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted PID: 1138 (plasmashell) UID: 1000 (iossher) GID: 1000 (iossher) Signal: 6 (ABRT) Timestamp: Mon 2023-11-06 13:17:37 EST (35s ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (iossher) Boot ID: 795b1536ad8f41e79fea012ca587dba7 Machine ID: 31028c578155476fa266dc0dd0e85f92 Hostname: debian-mac Storage: /var/lib/systemd/coredump/core.plasmashell.1000.795b1536ad8f41e79fea012ca587dba7.1138.169929465700.zst (present) Size on Disk: 42.9M Message: Process 1138 (plasmashell) of user 1000 dumped core. Module libarchive.so.13 from deb libarchive-3.7.2-1.amd64 Module libsystemd.so.0 from deb systemd-254.5-1.amd64 Module libzstd.so.1 from deb libzstd-1.5.5+dfsg2-2.amd64 Module libudev.so.1 from deb systemd-254.5-1.amd64 Stack trace of thread 1138: #0 0x7f57de2a80fc n/a (libc.so.6 + 0x8a0fc) #1 0x7f57de25a472 raise (libc.so.6 + 0x3c472) #2 0x7f57e0cc6b46 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b46) #3 0x7f57de25a510 n/a (libc.so.6 + 0x3c510) #4 0x7f57de2a80fc n/a (libc.so.6 + 0x8a0fc) #5 0x7f57de25a472 raise (libc.so.6 + 0x3c472) #6 0x7f57de25a510 n/a (libc.so.6 + 0x3c510) #7 0x7f57de2a3154 n/a (libc.so.6 + 0x85154) #8 0x7f57de2a5818 pthread_cond_wait (libc.so.6 + 0x87818) #9 0x7f57de8e0cab _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xe0cab) #10 0x7f57e080c508 n/a (libQt5Quick.so.5 + 0x20c508) #11 0x7f57e08799b0 _ZN12QQuickWindow5eventEP6QEvent (libQt5Quick.so.5 + 0x2799b0) #12 0x7f57df762f32 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162f32) #13 0x7f57deacc7b8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2cc7b8) #14 0x7f57def2e23c _ZN15QPlatformWindow20deliverUpdateRequestEv (libQt5Gui.so.5 + 0x12e23c) #15 0x7f57deaf99b0 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2f99b0) #16 0x7f57df762f32 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162f32) #17 0x7f57deacc7b8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2cc7b8) #18 0x7f57deacfec1 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2cfec1) #19 0x7f57deb28707 n/a (libQt5Core.so.5 + 0x328707) #20 0x7f57dd43c1b4 n/a (libglib-2.0.so.0 + 0x571b4) #21 0x7f57dd43f2d7 n/a (libglib-2.0.so.0 + 0x5a2d7) #22 0x7f57dd43f8f0 g_main_context_iteration (libglib-2.0.so.0 + 0x5a8f0) #23 0x7f57deb27dba _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x327dba) #24 0x7f57deacb16b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2cb16b) #25 0x7f57dead3914 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2d3914) #26 0x5604ffe2ddb4 n/a (plasmashell + 0x26db4) #27 0x7f57de2456ca n/a (libc.so.6 + 0x276ca) #28 0x
[konsole] [Bug 476136] New: konsole website has broken link to handbook
https://bugs.kde.org/show_bug.cgi?id=476136 Bug ID: 476136 Summary: konsole website has broken link to handbook Classification: Applications Product: konsole Version: unspecified Platform: unspecified OS: All Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: i...@iankelling.org Target Milestone: --- https://konsole.kde.org/ links to "user support" https://konsole.kde.org/users.html at the top of the page that links to "Konsole Handbook" https://docs.kde.org/trunk5/en/konsole/konsole/index.html that is 404. I see that https://docs.kde.org/index.php?language=en&package=konsole has a working link to a manual. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475180] Plasma Panel displays when its visibility is configured as "auto hide"
https://bugs.kde.org/show_bug.cgi?id=475180 --- Comment #5 from Ian --- Created attachment 162264 --> https://bugs.kde.org/attachment.cgi?id=162264&action=edit Screenshot of my desktop I've only got a standard 1920x1080 screen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475180] Plasma Panel displays when its visibility is configured as "auto hide"
https://bugs.kde.org/show_bug.cgi?id=475180 --- Comment #3 from Ian --- Hi Nate, thanks for your answer. (In reply to Nate Graham from comment #2) > Some questions: > - Is this panel on an edge between two screens? Nop > - Did you disable the "hide utility windows for inactive applications" > setting in System Settings > Window Behavior? Nop. I just tried disabling and enablig it and didn't see any effect. > - Are there any other Panels on vertical screen edges? Nop. > - Have you turned on the "Switch desktop on edge > Always enabled" setting? Nop. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471315] Plasma always crashes in TaskGroupingProxyModel::Private::sourceRowsInserted() when clicking on apps in task panel
https://bugs.kde.org/show_bug.cgi?id=471315 --- Comment #15 from Ian Newton --- (In reply to Jf from comment #10) > Seems to be something with widgets. I added the same widges, cpu cores and > power, and the issue came back. I remove them and it seems to be gone. I reported this problem as Bug 474726 now marked as a duplicate. I can confirm that removing Power widget from the task bar and upgrading back to latest plasma-desktop-5.27.8-2 from v 5.27.5 seems to solve this problem. Restarting the desktop remains stable minimising any window or switching activities. For some reason re-adding this power widget to the desktop also remains stable. Does the re-write of the widget config correct the desktop config? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475180] Plasma Panel displays when its visibility is configured as "auto hide"
https://bugs.kde.org/show_bug.cgi?id=475180 Ian changed: What|Removed |Added Summary|Plasma Panel doesn't|Plasma Panel displays when |display when its visibility |its visibility is |is configured as "auto |configured as "auto hide" |hide" | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475180] Plasma Panel doesn't display when its visibility is configured as "auto hide"
https://bugs.kde.org/show_bug.cgi?id=475180 --- Comment #1 from Ian --- Created attachment 162055 --> https://bugs.kde.org/attachment.cgi?id=162055&action=edit Visual example -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475180] New: Plasma Panel doesn't display when its visibility is configured as "auto hide"
https://bugs.kde.org/show_bug.cgi?id=475180 Bug ID: 475180 Summary: Plasma Panel doesn't display when its visibility is configured as "auto hide" Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: cisnerosalen...@protonmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 162054 --> https://bugs.kde.org/attachment.cgi?id=162054&action=edit Visual example SUMMARY The same as the title. STEPS TO REPRODUCE 1. Configure the Plasma panel with Auto hide visibility. OBSERVED RESULT The panel still shows but it isn't clickable. EXPECTED RESULT The panel should hide. SOFTWARE/OS VERSIONS Arch Linux KDE Plasma (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION I attached a video showing the problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474726] plasma-desktop crash for versions 5.27.6/5.27.7/5.27.8
https://bugs.kde.org/show_bug.cgi?id=474726 --- Comment #5 from Ian Newton --- Created attachment 161783 --> https://bugs.kde.org/attachment.cgi?id=161783&action=edit Backtrace with debug symbol applications installed I hope this is of some use? It looks like a problem is in /usr/lib/libQt5Core.so.5 or dependencies. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474726] plasma-desktop crash for versions 5.27.6/5.27.7/5.27.8
https://bugs.kde.org/show_bug.cgi?id=474726 --- Comment #3 from Ian Newton --- Created attachment 161760 --> https://bugs.kde.org/attachment.cgi?id=161760&action=edit coredumpctl log following guide instructions It seems the trigger to cause the crash was minimizing any open window. It is not related to the system tray other than some applications are minimized there. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474726] plasma-desktop crash for versions 5.27.6/5.27.7/5.27.8
https://bugs.kde.org/show_bug.cgi?id=474726 Ian Newton changed: What|Removed |Added CC||i.new...@c-org.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474726] plasma-desktop crash for versions 5.27.6/5.27.7/5.27.8
https://bugs.kde.org/show_bug.cgi?id=474726 --- Comment #1 from Ian Newton --- Created attachment 161743 --> https://bugs.kde.org/attachment.cgi?id=161743&action=edit coredumpctl log -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474726] New: plasma-desktop crash for versions 5.27.6/5.27.7/5.27.8
https://bugs.kde.org/show_bug.cgi?id=474726 Bug ID: 474726 Summary: plasma-desktop crash for versions 5.27.6/5.27.7/5.27.8 Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: Manjaro OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: i.new...@c-org.com Target Milestone: 1.0 Created attachment 161742 --> https://bugs.kde.org/attachment.cgi?id=161742&action=edit Section of journal log showing restart of plasma and crash/core dump. 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. Upgrade from plasma-desktop 5.27.5 to 5.27.8 2. Restart plasma desktop 3. Mouse select program icon in system tray. QT based programs seem the most vulnerable like keepassxc. There is no such problem under plasma-desktop 5.27.5. OBSERVED RESULT plasma-desktop crashes "core-dump" in system log. EXPECTED RESULT Program opens as normal as in 5.27.5 SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Linux 6.5.3-1-MANJARO x86_64 (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 474099] New: kscreen doesn't save config when upower is not installed
https://bugs.kde.org/show_bug.cgi?id=474099 Bug ID: 474099 Summary: kscreen doesn't save config when upower is not installed Classification: Plasma Product: KScreen Version: 5.27.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: arequip...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Uninstall upower 2. Log out of Plasma 3. Remove any existing kscreen configuration in ~/.local/share/kscreen 4. Log in to Plasma OBSERVED RESULT kscreen configuration is not written to ~/.local/share/kscreen. Any changes to the configuration are lost when logging out. EXPECTED RESULT Configuration should be saved to ~/.local/share/kscreen. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: Fedora 38 (kernel 6.4.12) (available in About System) KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION A similar issue is described here. https://rainerkeller.de/2018-KDE-does-not-load-screen-settings.html The patch from that blog post appears to fix this issue as well. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 391624] Add support for screen sharing
https://bugs.kde.org/show_bug.cgi?id=391624 Ian changed: What|Removed |Added CC||ian.sch...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 472296] New: Crashed when opening an item in discover
https://bugs.kde.org/show_bug.cgi?id=472296 Bug ID: 472296 Summary: Crashed when opening an item in discover Classification: Applications Product: Discover Version: 5.24.7 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: ian.sch...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.24.7) Qt Version: 5.15.3 Frameworks Version: 5.92.0 Operating System: Linux 5.15.0-76-generic x86_64 Windowing System: Wayland Distribution: Linux Mint 21.1 DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Double-clicked on tuxracer to get more information about the program. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139670658741824) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=139670658741824) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=139670658741824, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7f07f63ea476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f07f63d07f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x7f07f688aba3 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f07f2246e45 in () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #11 0x7f07f22565dd in QtWaylandClient::QWaylandDisplay::dispatchQueueWhile(wl_event_queue*, std::function, int) () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #12 0x7f07f225c63b in QtWaylandClient::QWaylandWindow::waitForFrameSync(int) () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #13 0x7f07eb463bf2 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so #14 0x7f07f85f761c in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #15 0x7f07f85f7e07 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #16 0x7f07f68c6ca1 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f07f643cb43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #18 0x7f07f64cea00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 15 (Thread 0x7f07c8c6d640 (LWP 38281) "plasma-d:gdrv0"): #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x55dfcd02d8e0) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x55dfcd02d8e0, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x7f07f643bac1 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55dfcd02d890, cond=0x55dfcd02d8b8) at ./nptl/pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x55dfcd02d8b8, mutex=0x55dfcd02d890) at ./nptl/pthread_cond_wait.c:627 #5 0x7f07e9a9fced in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #6 0x7f07e9a5335b in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #7 0x7f07e9a9fc1b in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #8 0x7f07f643cb43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #9 0x7f07f64cea00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 14 (Thread 0x7f07c946e640 (LWP 38280) "plasma-d:gdrv0"): #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x55dfccf899f4) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x55dfccf899f4, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x7f07f643bac1 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55dfccf899a0, cond=0x55dfccf899c8) at ./nptl/pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x55dfccf899c8, mutex=0x55dfccf899a0) at ./nptl/pthread_cond_wait.c:627 #5 0x7f07e9a9fced in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #6 0x7f07e9a5335b in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #7 0x7f07e9a9fc1b in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #8 0x7f07f643cb43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #9 0x7f07f64cea00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 13 (Thread 0x7f07ca66d640 (LWP 38273) "dconf worker"): #1 0x7f07f54011f6 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f07f53a93e3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f07d011d33d in () at /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so #4 0
[neon] [Bug 464830] [Request] Update kdevelop snap to latest (22.12.1)
https://bugs.kde.org/show_bug.cgi?id=464830 Ian H changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #3 from Ian H --- installed: 23.04.1(64) 812MB classic throws errors when building/running qt projects. my guess is it is loading up an incompatible lib during build/run. /Qt/5.15.12/gcc_64/bin/repc: symbol lookup error: /Qt/5.15.12/gcc_64/bin/repc: undefined symbol: _ZdlPvm, version Qt_5 installed: 23.04.2(66) 812MB classic crashes at kdevelop launch snap run kdevelop Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. Segmentation fault (core dumped) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460570] Face Recognition fails (process stuck at 0%)
https://bugs.kde.org/show_bug.cgi?id=460570 Ian Davey changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #16 from Ian Davey --- My issue has been resolved. -- You are receiving this mail because: You are watching all bug changes.
[palapeli] [Bug 466360] it does not load a jpg file
https://bugs.kde.org/show_bug.cgi?id=466360 Ian Wadham changed: What|Removed |Added CC||iandw...@gmail.com --- Comment #8 from Ian Wadham --- (In reply to Albert Astals Cid from comment #4) > Works fine for me. > > Can you attach a screenshot of the error you get? @aacid - The error Albert Debney gets is "Puzzle cannot be created: The file you selected is not an image." and he asserts that it is a regular JPG file. The lines of code from 103 to 130 in file palapeli/src/creator/puzzlecreator.cpp are essentially unchanged since KDE4 days, except for the message types changing from Sorry to Error. They involve the use of quite a bit of heavy KDE machinery and do not provide messages for every possible failure. Could it be that the other Albert's installed versions of Linux and KF/Qt simply fail to find or retrieve the file and then conclude that it is "not an image" file? -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 465676] New: KSysguard fails to build with kdesrcbuild
https://bugs.kde.org/show_bug.cgi?id=465676 Bug ID: 465676 Summary: KSysguard fails to build with kdesrcbuild Classification: Applications Product: ksysguard Version: master Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: master.ha...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 156196 --> https://bugs.kde.org/attachment.cgi?id=156196&action=edit build log SUMMARY *** Does not build with kdesrcbuild. *** STEPS TO REPRODUCE 1. kdesrc-build libksysguard --verbose --debug OBSERVED RESULT gmake[2]: *** [processui/CMakeFiles/processui.dir/build.make:282: bin/libprocessui.so.5.27.80] Error 1 gmake[1]: *** [CMakeFiles/Makefile2:1123: processui/CMakeFiles/processui.dir/all] Error 2 gmake: *** [Makefile:146: all] Error 2 libksysguard command logged to /home/user/kde/src/log/2023-02-13-04/libksysguard/build.log gave non-zero exit: 512 run_logged_p(): libksysguard build complete: 512 Logfile for libksysguard is build.log libksysguard didn't build, stopping here. Removing 0 out of 3 old log directories... Message is FAILED TO BUILD for libksysguard <<< PACKAGES FAILED TO BUILD >>> EXPECTED RESULT should compile successfully SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 22.04 Qt Version: 5.15.12 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 465562] Crash in kdevelop possibly due to old llvm being used in snap
https://bugs.kde.org/show_bug.cgi?id=465562 --- Comment #1 from Ian H --- up until now i've been unsuccessful at creating a simple project that causes this. it only seems to happen in a very large project. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 465562] New: Crash in kdevelop possibly due to old llvm being used in snap
https://bugs.kde.org/show_bug.cgi?id=465562 Bug ID: 465562 Summary: Crash in kdevelop possibly due to old llvm being used in snap Classification: KDE Neon Product: neon Version: unspecified Platform: Ubuntu OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Snaps Assignee: sgmo...@kde.org Reporter: master.ha...@gmail.com CC: neon-b...@kde.org Target Milestone: --- SUMMARY *** Kdevelop crashes when a pointer is deleted. according to the dev team, it's likely that it's crashing because the llvm version being used in the snap is very old (llvm11). Is it possible for the snap to be updated with a newer version of llvm? *** STEPS TO REPRODUCE 1. add code to a c++ file: if() delete 2. crash OBSERVED RESULT crashes consistently when the parser reads any 'delete' line. EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: ubuntu 22.04 ADDITIONAL INFORMATION (gdb) thread apply all bt Thread 57 (LWP 1895369 "Queue(0x55af300"): #0 0x7fec0e08d45c in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #1 0x7fec0dea2d0e in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #2 0x7fec0e3e03ba in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #3 0x7fec0e3e0ae5 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #4 0x7fec0e3e0ae5 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #5 0x7fec0e3dfcf0 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #6 0x7fec0e3d7789 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #7 0x7fec0e3d744d in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #8 0x7fec0e3d7b56 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #9 0x7fec0ec36131 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #10 0x7fec0ec32bfd in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #11 0x7fec0e2f7ed8 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #12 0x7fec0e291b9c in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #13 0x7fec0e2968b4 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #14 0x7fec0de6a9d6 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #15 0x7fec036c9a8d in llvm::CrashRecoveryContext::RunSafely(llvm::function_ref) () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libLLVM-11.so.1 #16 0x7fec036c9ba4 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libLLVM-11.so.1 #17 0x7fec03783e0a in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libLLVM-11.so.1 #18 0x7fec90d9f609 in start_thread () from /snap/core20/current/lib/x86_64-linux-gnu/libpthread.so.0 #19 0x7fec9475f133 in clone () from /snap/core20/current/lib/x86_64-linux-gnu/libc.so.6 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 464747] Crash when adding code to delete a pointer in c++
https://bugs.kde.org/show_bug.cgi?id=464747 --- Comment #12 from Ian H --- yea. i suspect that since noone else is seeing this that it is simply because the version of llvm the snap is using is super old. unfortunately convincing anyone to keep the snap or appImage up to date is almost impossible. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 396710] Subclassing interface adds '=0' to header file
https://bugs.kde.org/show_bug.cgi?id=396710 Ian H changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- --- Comment #4 from Ian H --- this is still an issue as far as i know. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 464747] Crash when adding code to delete a pointer in c++
https://bugs.kde.org/show_bug.cgi?id=464747 --- Comment #9 from Ian H --- Found a case that literally crashes every boot... but i still cant simplify it to a test project. doing ` if(m_ldap) ldap_destroy(m_ldap)` doesnt crash, but instantly when i switch the ldap_destroy to delete m_ldap, it gets stuck in a crash loop. you guys mentioned that it could be caused by the old version of LLVM. is there any chance someone from the neon team could update the snap so that it uses a more recent version of llvm? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460570] Face Recognition fails (process stuck at 0%)
https://bugs.kde.org/show_bug.cgi?id=460570 --- Comment #11 from Ian Davey --- As requested I have installed 7.10.0, selected People module, Skip images already scanned. Unfortunately process remains at 0%. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 453640] Home page Copy an amount no longer works
https://bugs.kde.org/show_bug.cgi?id=453640 Ian Neal changed: What|Removed |Added CC||iann_bugzi...@blueyonder.co ||.uk --- Comment #14 from Ian Neal --- (In reply to Pete from comment #5) > This problem also affects Fedora 36. Out of interest what window manager are you using? KDE, Gnome or something else? I see the same issue using Gnome on Fedora 36. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 465078] New: Progress bar stays at 0%
https://bugs.kde.org/show_bug.cgi?id=465078 Bug ID: 465078 Summary: Progress bar stays at 0% Classification: Applications Product: digikam Version: 7.9.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Faces-Detection Assignee: digikam-bugs-n...@kde.org Reporter: idave...@gmail.com Target Milestone: --- SUMMARY Progress bar stays at 0% following "Scan collection for faces" with "skip images ..." selected STEPS TO REPRODUCE 1. Click on Scan Collection for faces OBSERVED RESULT Progress stays at 0%. Faces scanning greyed out. EXPECTED RESULT Progress bar activity SOFTWARE/OS VERSIONS Windows: 10 19045.2486 64bit 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.
[neon] [Bug 464830] New: [Request] Update kdevelop snap to latest (22.12.1)
https://bugs.kde.org/show_bug.cgi?id=464830 Bug ID: 464830 Summary: [Request] Update kdevelop snap to latest (22.12.1) Classification: KDE Neon Product: neon Version: unspecified Platform: Snap OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Snaps Assignee: sgmo...@kde.org Reporter: master.ha...@gmail.com CC: neon-b...@kde.org Target Milestone: --- Any chance we could get an update on the kdevelop snap? Also i ran into an issue with kdevelop and the devs there said the current snap is using a really old version of clang (libclang11). i dont know if it's possible to change this? i think the latest libclang is 14. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 464747] Crash when adding code to delete a pointer in c++
https://bugs.kde.org/show_bug.cgi?id=464747 --- Comment #8 from Ian H --- Must be related to something else going on. it also creashes when using make_unique sometimes. Thread 78 (LWP 1983138 "Queue(0x56339ff"): #0 0x7f51b5967125 in clone () from /snap/core20/current/lib/x86_64-linux-gnu/libc.so.6 #1 0x7f51b1fa7530 in ?? () from /snap/core20/current/lib/x86_64-linux-gnu/libpthread.so.0 #2 0x7f50da7fc700 in ?? () #3 0x in ?? () Thread 77 (LWP 1983135 "KDevelop::Compl"): #0 0x7f51b595a99f in poll () from /snap/core20/current/lib/x86_64-linux-gnu/libc.so.6 #1 0x7f51b14de36e in ?? () from /snap/core20/current/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f51b14de4a3 in g_main_context_iteration () from /snap/core20/current/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f51b5f2b5e2 in QEventDispatcherGlib::processEvents(QFlags) () from /snap/kdevelop/37/usr/bin/../lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f51b5ecf76b in QEventLoop::exec(QFlags) () from /snap/kdevelop/37/usr/bin/../lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f51b5ce9372 in QThread::exec() () from /snap/kdevelop/37/usr/bin/../lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f51b3f589f0 in KDevelop::CompletionWorkerThread::run() () from /snap/kdevelop/37/usr/bin/../lib/x86_64-linux-gnu/libKDevPlatformLanguage.so.59 #7 0x7f51b5cea553 in ?? () from /snap/kdevelop/37/usr/bin/../lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f51b1fa7609 in start_thread () from /snap/core20/current/lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f51b5967133 in clone () from /snap/core20/current/lib/x86_64-linux-gnu/libc.so.6 Thread 67 (LWP 1983120 "Queue(0x56339ff"): #0 0x7f512e3a98e9 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #1 0x7f512e3aaac0 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #2 0x7f512e05c3f6 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #3 0x7f512e05cae5 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #4 0x7f512e05bcf0 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #5 0x7f512e053789 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #6 0x7f512e05344d in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #7 0x7f512e053b56 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #8 0x7f512e8b2131 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #9 0x7f512e8aebfd in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #10 0x7f512df73ed8 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #11 0x7f512df0db9c in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #12 0x7f512df11547 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #13 0x7f512df12254 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #14 0x7f512dae5539 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #15 0x7f51236c9a8d in llvm::CrashRecoveryContext::RunSafely(llvm::function_ref) () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libLLVM-11.so.1 --Type for more, q to quit, c to continue without paging--c #16 0x7f51236c9ba4 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libLLVM-11.so.1 #17 0x7f5123783e0a in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libLLVM-11.so.1 #18 0x7f51b1fa7609 in start_thread () from /snap/core20/current/lib/x86_64-linux-gnu/libpthread.so.0 #19 0x7f51b5967133 in clone () from /snap/core20/current/lib/x86_64-linux-gnu/libc.so.6 Thread 50 (LWP 1983103 "Queue(0x56339ff"): #0 0x7f512e670600 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #1 0x7f512e66d947 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #2 0x7f512e66e718 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #3 0x7f512e66ec14
[kdevelop] [Bug 464747] Crash when adding code to delete a pointer in c++
https://bugs.kde.org/show_bug.cgi?id=464747 --- Comment #7 from Ian H --- (In reply to Igor Kushnir from comment #6) > (In reply to Sven Brauch from comment #5) > > The code in question is so trivial that it's very unlikely to be related to > > that code. This snippet occurs in pretty much every C++ file in every > > project. > The snippet should not occur in every C++ file. Not only does it use raw > delete, which is discouraged in modern C++. It also redundantly checks for > null as deleting nullptr is a no-op. > > That said, I agree that the snippet in itself is unlikely to cause a crash > in any released libclang or KDevelop version. that may be the case, but it happens quite often for me when i do that exact line of code. i noticed this because i was purposely trying to crash my program to test a crash handler and it crashed kdevelop when i added the delete. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 464747] Crash when adding code to delete a pointer in c++
https://bugs.kde.org/show_bug.cgi?id=464747 --- Comment #4 from Ian H --- Just tested on a blank project and it doesnt seem to crash... so i guess it might be project related. that makes this way more annoying. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 464747] Crash when adding code to delete a pointer in c++
https://bugs.kde.org/show_bug.cgi?id=464747 --- Comment #2 from Ian H --- pretty sure I'm using the clang that comes in the snap. does that mean this needs to get assigned to the snap team? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 464747] New: Crash when adding code to delete a pointer in c++
https://bugs.kde.org/show_bug.cgi?id=464747 Bug ID: 464747 Summary: Crash when adding code to delete a pointer in c++ Classification: Applications Product: kdevelop Version: 5.9.220801 Platform: Snap OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: master.ha...@gmail.com Target Milestone: --- SUMMARY *** Crash when adding code to delete a pointer *** STEPS TO REPRODUCE 1. add code to a c++ file: if() delete 2. crash OBSERVED RESULT seems to crash every time you add that code. it does not crash on subsequent loads after the code is added EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: ubuntu 22.04 ADDITIONAL INFORMATION (gdb) thread apply all bt Thread 57 (LWP 1895369 "Queue(0x55af300"): #0 0x7fec0e08d45c in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #1 0x7fec0dea2d0e in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #2 0x7fec0e3e03ba in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #3 0x7fec0e3e0ae5 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #4 0x7fec0e3e0ae5 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #5 0x7fec0e3dfcf0 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #6 0x7fec0e3d7789 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #7 0x7fec0e3d744d in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #8 0x7fec0e3d7b56 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #9 0x7fec0ec36131 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #10 0x7fec0ec32bfd in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #11 0x7fec0e2f7ed8 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #12 0x7fec0e291b9c in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #13 0x7fec0e2968b4 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #14 0x7fec0de6a9d6 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libclang-11.so.1 #15 0x7fec036c9a8d in llvm::CrashRecoveryContext::RunSafely(llvm::function_ref) () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libLLVM-11.so.1 #16 0x7fec036c9ba4 in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libLLVM-11.so.1 #17 0x7fec03783e0a in ?? () from /snap/kdevelop/37/usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/37/../../../../libLLVM-11.so.1 #18 0x7fec90d9f609 in start_thread () from /snap/core20/current/lib/x86_64-linux-gnu/libpthread.so.0 #19 0x7fec9475f133 in clone () from /snap/core20/current/lib/x86_64-linux-gnu/libc.so.6 --Type for more, q to quit, c to continue without paging-- Thread 51 (LWP 1895358 "Thread (pooled)"): #0 0x7fec90da67d1 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /snap/core20/current/lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7fec94ae8588 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /snap/kdevelop/37/usr/bin/../lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fec94ae5aa1 in ?? () from /snap/kdevelop/37/usr/bin/../lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fec94ae2553 in ?? () from /snap/kdevelop/37/usr/bin/../lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fec90d9f609 in start_thread () from /snap/core20/current/lib/x86_64-linux-gnu/libpthread.so.0 #5 0x7fec9475f133 in clone () from /snap/core20/current/lib/x86_64-linux-gnu/libc.so.6 Thread 50 (LWP 1895357 "Thread (pooled)"): #0 0x7fec90da67d1 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /snap/core20/current/lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7fec94ae8588 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /snap/kdevelop/37/usr/bin/../lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fec94ae5aa1 in ?? () from /snap/kdevelop/37/usr/bin/../lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fec94ae2553 in ?? () from /snap/kdevelop/37/usr/bin/../lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fec90d9f609
[kpat] [Bug 464481] Cannot download new themes - must do manual install
https://bugs.kde.org/show_bug.cgi?id=464481 --- Comment #5 from Ian Wadham --- I seem to remember that the card decks reside in a library. KPat is not the only card game… See https://invent.kde.org/games/libkdegames/-/blob/master/src/carddecks/README > On 19 Jan 2023, at 10:44 pm, Ron Nascimento wrote: > > https://bugs.kde.org/show_bug.cgi?id=464481 > > --- Comment #4 from Ron Nascimento --- > Looking at source code: > > 1. https://invent.kde.org/games/kpat/-/blob/master/src/renderer.cpp#L67 - > shows > where it looks for themes > 2. > https://invent.kde.org/games/kpat/-/blob/master/src/libkcardgame/kcardtheme.cpp#L58 > - appears to be looking in `~/.local/share/carddecks` but need to read > further... > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 464017] Cannot shrink an ext2/3/4 filesystem
https://bugs.kde.org/show_bug.cgi?id=464017 --- Comment #4 from Ian Turner --- I was trying to reduce it by 60 gibibytes (to 892428 mebibytes). While I was playing around with it I reduced it by a much smaller amount (< 1GB) and then reduced it a second time to the desired size, and that worked. So possible there is some mathy issue. I suppose that one possible step forward would be to change some of these types to unsigned, or to add asserts. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 464017] Cannot shrink an ext2/3/4 filesystem
https://bugs.kde.org/show_bug.cgi?id=464017 Ian Turner changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 464017] Cannot shrink an ext2/3/4 filesystem
https://bugs.kde.org/show_bug.cgi?id=464017 --- Comment #2 from Ian Turner --- Actually, looking more closely at the resize2fs documentation, I think the problem is that we are passing a negative number at all. And unfortunately, I'm now unable to reproduce this issue. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 464017] Cannot shrink an ext2/3/4 filesystem
https://bugs.kde.org/show_bug.cgi?id=464017 --- Comment #1 from Ian Turner --- I think the bug is right here: https://github.com/KDE/kpmcore/blob/ce39e149040bce9782b91e532d041ca0c7548a77/src/fs/ext2.cpp#L181 There should be an extra "--" as the first parameter. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 464017] New: Cannot shrink an ext2/3/4 filesystem
https://bugs.kde.org/show_bug.cgi?id=464017 Bug ID: 464017 Summary: Cannot shrink an ext2/3/4 filesystem Classification: Applications Product: partitionmanager Version: 20.12.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: vec...@vectro.org Target Milestone: --- SUMMARY Attempting to shrink an ext2/3/4 filesystem fails with an error because kpmcore does not pass the correct arguments to resize2fs. STEPS TO REPRODUCE 1. Mark an ext2/3/4 for resizing. Specify a smaller size 2. Execute the operatior OBSERVED RESULT Job: Resize file system on partition ‘/dev/sdc1’ to 1,827,692,544 sectors Resizing file system from 1,953,523,119 to 1,827,692,544 sectors. Command: resize2fs /dev/mapper/luks-edfeab04-9935-4f0c-b019-805ceb4f8df8 -125830575s Resizing encrypted file system on partition ‘/dev/sdc1’ failed. Resize file system on partition ‘/dev/sdc1’ to 1,827,692,544 sectors: Error EXPECTED RESULT Operation would succeed SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian 11 "Bullseye" (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Running the resize2fs command in the output reveals the actual problem: $ sudo resize2fs /dev/mapper/luks-edfeab04-9935-4f0c-b019-805ceb4f8df8 -125830575s [sudo] password for vectro: resize2fs 1.46.2 (28-Feb-2021) resize2fs: invalid option -- '1' Usage: resize2fs [-d debug_flags] [-f] [-F] [-M] [-P] [-p] device [-b|-s|new_size] [-S RAID-stride] [-z undo_file] Annoyingly, it is necessary to quote the negative number so that it is not interpreted as a flag. The command line should be: resize2fs /dev/mapper/luks-edfeab04-9935-4f0c-b019-805ceb4f8df8 -- -125830575s (note the extra --) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 437323] Move Copy menu no mouse hover wayland
https://bugs.kde.org/show_bug.cgi?id=437323 --- Comment #2 from Ian Snow --- (In reply to Laurent Montel from comment #1) > Still valid ? Yes, and its now KMail 5.22.0 and latest versions of the software stack as its Arch -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 463532] Account info page can be pushed multiple times
https://bugs.kde.org/show_bug.cgi?id=463532 Ian Kidd changed: What|Removed |Added Version|unspecified |23.01.0 Platform|Other |Flatpak CC||ik...@protonmail.com --- Comment #1 from Ian Kidd --- In fact it just rolls back to the start of the account wizard which makes you think there was an error, and so you do it all over again and end up with 3 or 4 of the same account in the Account list under settings. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432263] Shift- and Alt-Modifier keys do not change the drag and drop behaviour
https://bugs.kde.org/show_bug.cgi?id=432263 Ian Petts changed: What|Removed |Added CC||ipe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 463523] Text is not visible in dark model
https://bugs.kde.org/show_bug.cgi?id=463523 --- Comment #3 from Ian Gutierrez --- (In reply to Carl Schwan from comment #1) > Could you add a screenshot? Sure! Added to the ticket. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 463523] Text is not visible in dark model
https://bugs.kde.org/show_bug.cgi?id=463523 Ian Gutierrez changed: What|Removed |Added CC||ian.gutier...@protonmail.co ||m --- Comment #2 from Ian Gutierrez --- Created attachment 154850 --> https://bugs.kde.org/attachment.cgi?id=154850&action=edit Screenshot of text (I attempted to write "I can't read any text" into the toot box) Screenshot of text (I attempted to write "I can't read any text" into the toot box) -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 463523] New: Text is not visible in dark model
https://bugs.kde.org/show_bug.cgi?id=463523 Bug ID: 463523 Summary: Text is not visible in dark model Classification: Applications Product: Tokodon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ian.gutier...@protonmail.com CC: c...@carlschwan.eu Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Set up Pop!_OS 22.04 in Dark Mode under Desktop > Appearance 2. Install Tokodon 22.11.2 OBSERVED RESULT Text unreadable (black text on black box) EXPECTED RESULT White text on black box SOFTWARE/OS VERSIONS Linux/KDE Plasma: Pop!_OS 22.04 ADDITIONAL INFORMATION Tokodon 22.11.2 KDE Frameworks 5.101.0 The xcb windowing system Qt 5.15.7 (built against 5.15.7) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 463107] New: Window rule does not apply automatically after restarting a Wine application
https://bugs.kde.org/show_bug.cgi?id=463107 Bug ID: 463107 Summary: Window rule does not apply automatically after restarting a Wine application Classification: Plasma Product: kwin Version: 5.26.4 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: rules Assignee: kwin-bugs-n...@kde.org Reporter: themvru...@gmail.com CC: isma...@gmail.com Target Milestone: --- SUMMARY This happens when I run the application GraphicsGale v2.08.24 (https://graphicsgale.com/us/) in Wine. I have tried a few other applications, both Wine and native but couldn't reproduce. This application appears to create an invisible window when starting, clicking it in the taskbar does nothing. The actual window has the property "Skip taskbar" automatically set. I created a rule to force "Skip taskbar" to "No", however when the application is restarted, the rule does not apply, unless I first set it to "Yes" and then "No" again. The invisible window might be a separate issue, I'm not sure exactly where it should be filed. This report concerns the issue where the window rules are not reapplied after the restart. STEPS TO REPRODUCE 1. Open GraphicsGale 2. Right click icon in window title bar, select More actions -> Configure Special Window Settings 3. Add a property "Skip taskbar", "Force", "No" 4. Another window icon will appear in the taskbar 5. Close and restart GraphicsGale 6. Minimize OBSERVED RESULT A second window icon that appears can be clicked to restore the window EXPECTED RESULT The second window icon does not appear, clicking the existing icon does nothing. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: EndeavourOS (available in About System) KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 462827] Crash when editing splits in a transaction
https://bugs.kde.org/show_bug.cgi?id=462827 --- Comment #7 from Ian Neal --- (In reply to Jack from comment #6) > Just for clarification, is this when editing splits in a transaction in the > ledger, or when editing splits in a scheduled transaction? I have checked, it crashes both for a scheduled transaction and a transaction that is already in the ledger. I have tested editing a scheduled transaction both in the ledger view and the scheduled transactions view - it crashes in both. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 462827] Crash when editing splits in a transaction
https://bugs.kde.org/show_bug.cgi?id=462827 --- Comment #4 from Ian Neal --- Tested using kmymoney-5.1-327-linux-gcc-x86_64.AppImage - that also crashes -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 462827] Crash when editing splits in a transaction
https://bugs.kde.org/show_bug.cgi?id=462827 --- Comment #3 from Ian Neal --- Easier STR: 1. Create a scheduled transaction with splits 2. Edit the scheduled transaction 3. On one of the splits alter the amount then hit CR and Enter at the same time (easier than trying to do it twice quickly). -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 462827] Crash when editing splits in a transaction
https://bugs.kde.org/show_bug.cgi?id=462827 --- Comment #2 from Ian Neal --- *** Bug 462026 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 462026] Crash whilst editing split
https://bugs.kde.org/show_bug.cgi?id=462026 Ian Neal changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Ian Neal --- *** This bug has been marked as a duplicate of bug 462827 *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 462827] Crash when editing splits in a transaction
https://bugs.kde.org/show_bug.cgi?id=462827 Ian Neal changed: What|Removed |Added Summary|Crash when entering |Crash when editing splits |multiple splits in a|in a transaction |transaction | --- Comment #1 from Ian Neal --- STR 1. Create a scheduled transaction with splits 2. Edit the scheduled transaction 3. On one of the splits alter the amount then hit CR twice very quickly 4. When prompted go back to editing the split 5. Loop back to step 3 for around 15-20 times. Expected result 1. Popup entitled "Enter Split" with message "You need to assign a category to this split before it can be entered." which, when acknowledge, goes back to split transaction screen. Actual result 1. Popup entitled "Enter Split" with message "You need to assign a category to this split before it can be entered." which, when acknowledge, crashes / hangs KMyMoney. I'm not sure if this is due to the number of times the field is being edited or how quickly the enter/CR key is hit. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 462827] New: Crash when entering multiple splits in a transaction
https://bugs.kde.org/show_bug.cgi?id=462827 Bug ID: 462827 Summary: Crash when entering multiple splits in a transaction Classification: Applications Product: kmymoney Version: 5.1.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: iann_bugzi...@blueyonder.co.uk Target Milestone: --- Application: kmymoney (5.1.2) Qt Version: 5.15.7 Frameworks Version: 5.100.0 Operating System: Linux 6.0.10-200.fc36.x86_64 x86_64 Windowing System: X11 Distribution: "Fedora release 36 (Thirty Six)" DrKonqi: 5.26.3 [KCrashBackend] -- Information about the crash: Creating a new transaction with splits across multiple categories, each new split gets slower and slower to create until it eventually crashes. The crash can be reproduced sometimes. -- Backtrace: Application: KMyMoney (kmymoney), signal: Segmentation fault [KCrash Handler] #4 0x7f1fdb5eb750 in QWidget::setFocus(Qt::FocusReason) () at /lib64/libQt5Widgets.so.5 #5 0x55671ba799e9 in KMyMoneySplitTable::endEdit(bool, bool) () #6 0x7f1fd7ad2ec4 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #7 0x7f1fdb69e522 in QFrame::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #8 0x7f1fdb5aed12 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #9 0x7f1fd7aa8278 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #10 0x7f1fd7aab5e4 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5 #11 0x7f1fd7af9897 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #12 0x7f1fd4bc9faf in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #13 0x7f1fd4c1f2c8 in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0 #14 0x7f1fd4bc7940 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #15 0x7f1fd7af938a in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #16 0x7f1fd7aa6cca in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #17 0x7f1fdb7bf787 in QDialog::exec() () at /lib64/libQt5Widgets.so.5 #18 0x55671ba955c2 in KSplitTransactionDlg::exec() () #19 0x55671baa8559 in StdTransactionEditor::slotEditSplits() () #20 0x7f1fd7adbc26 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #21 0x7f1fdb6a31d6 in QAbstractButton::clicked(bool) () at /lib64/libQt5Widgets.so.5 #22 0x7f1fdb6a344e in QAbstractButtonPrivate::emitClicked() () at /lib64/libQt5Widgets.so.5 #23 0x7f1fdb6a508c in QAbstractButtonPrivate::click() () at /lib64/libQt5Widgets.so.5 #24 0x7f1fdb6a52ab in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () at /lib64/libQt5Widgets.so.5 #25 0x7f1fdb5f1818 in QWidget::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #26 0x7f1fdb5aed12 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #27 0x7f1fdb5b7382 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #28 0x7f1fd7aa8278 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #29 0x7f1fdb5b5482 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /lib64/libQt5Widgets.so.5 #30 0x7f1fdb60ab7c in QWidgetWindow::handleMouseEvent(QMouseEvent*) () at /lib64/libQt5Widgets.so.5 #31 0x7f1fdb60df40 in QWidgetWindow::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #32 0x7f1fdb5aed12 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #33 0x7f1fd7aa8278 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #34 0x7f1fd7f6ae7d in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /lib64/libQt5Gui.so.5 #35 0x7f1fd7f4a02c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /lib64/libQt5Gui.so.5 #36 0x7f1fc3f178de in xcbSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5XcbQpa.so.5 #37 0x7f1fd4bc9faf in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #38 0x7f1fd4c1f2c8 in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0 #39 0x7f1fd4bc7940 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #40 0x7f1fd7af938a in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #41 0x7f1fd7aa6cca in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #42 0x7f1fd7aaed92 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #43 0x55671b936b4a in main () [Inferior 1 (process 5156) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 389659] Please wait while the message is transferred
https://bugs.kde.org/show_bug.cgi?id=389659 --- Comment #15 from Ian --- I think this old bug has now mostly gone away. I still get it occasionally, at which point I exit Kmail, open a terminal session, restart akonadi, and exit the terminal session. That seems to fix it. I am now on a different machine to when I reported this back in 2018. Thanks, Ian -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 389662] clearing cache removes messages from message list
https://bugs.kde.org/show_bug.cgi?id=389662 Ian changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Ian --- This is nearly 5 years old, I think it is fixed. Thinks, Ian -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 462026] New: Crash whilst editing split
https://bugs.kde.org/show_bug.cgi?id=462026 Bug ID: 462026 Summary: Crash whilst editing split Classification: Applications Product: kmymoney Version: 5.1.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: iann_bugzi...@blueyonder.co.uk Target Milestone: --- Application: kmymoney (5.1.2) Qt Version: 5.15.6 Frameworks Version: 5.99.0 Operating System: Linux 6.0.5-200.fc36.x86_64 x86_64 Windowing System: X11 Distribution: "Fedora release 36 (Thirty Six)" DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: I was editing a transaction which had multiple splits The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KMyMoney (kmymoney), signal: Segmentation fault [KCrash Handler] #4 0x7f5b67feb740 in QWidget::setFocus(Qt::FocusReason) () at /lib64/libQt5Widgets.so.5 #5 0x55c73f4839e9 in KMyMoneySplitTable::endEdit(bool, bool) () #6 0x7f5b644d2c44 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #7 0x7f5b6809e512 in QFrame::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #8 0x7f5b67faed02 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #9 0x7f5b644a81c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #10 0x7f5b644ab534 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5 #11 0x7f5b644f9537 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #12 0x7f5b61619faf in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #13 0x7f5b6166f2c8 in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0 #14 0x7f5b61617940 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #15 0x7f5b644f902a in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #16 0x7f5b644a6c1a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #17 0x7f5b681bf5e7 in QDialog::exec() () at /lib64/libQt5Widgets.so.5 #18 0x55c73f49f5c2 in KSplitTransactionDlg::exec() () #19 0x55c73f4b2559 in StdTransactionEditor::slotEditSplits() () #20 0x55c73f38d5fe in KGlobalLedgerView::slotEditSplits() () #21 0x7f5b644db9a6 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #22 0x7f5b67fa82e6 in QAction::triggered(bool) () at /lib64/libQt5Widgets.so.5 #23 0x7f5b67faafa3 in QAction::activate(QAction::ActionEvent) () at /lib64/libQt5Widgets.so.5 #24 0x7f5b68134f32 in QMenuPrivate::activateCausedStack(QVector > const&, QAction*, QAction::ActionEvent, bool) () at /lib64/libQt5Widgets.so.5 #25 0x7f5b6813ce0c in QMenuPrivate::activateAction(QAction*, QAction::ActionEvent, bool) () at /lib64/libQt5Widgets.so.5 #26 0x7f5b67ff1808 in QWidget::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #27 0x7f5b67faed02 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #28 0x7f5b67fb7372 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #29 0x7f5b644a81c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #30 0x7f5b67fb5472 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /lib64/libQt5Widgets.so.5 #31 0x7f5b6800afc5 in QWidgetWindow::handleMouseEvent(QMouseEvent*) () at /lib64/libQt5Widgets.so.5 #32 0x7f5b6800df30 in QWidgetWindow::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #33 0x7f5b67faed02 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #34 0x7f5b644a81c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #35 0x7f5b6496ae7d in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /lib64/libQt5Gui.so.5 #36 0x7f5b6494a02c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /lib64/libQt5Gui.so.5 #37 0x7f5b509178be in xcbSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5XcbQpa.so.5 #38 0x7f5b61619faf in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #39 0x7f5b6166f2c8 in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0 #40 0x7f5b61617940 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #41 0x7f5b644f902a in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #42 0x7f5b644a6c1a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #43 0x7f5b6813a763 in QMenuPrivate::exec(QPoint const&, QAction*, std::function) () at /lib64/libQt5Widgets.so.5 #44 0x7f5b6813a883 in QMenu::exec(QPoint const&, QAction*) () at /lib64/libQt5Widgets.so.5 #45 0x0
[ksudoku] [Bug 384546] Generated killer sudoku puzzle with multiple valid solutions (ksudoku 1.3)
https://bugs.kde.org/show_bug.cgi?id=384546 --- Comment #6 from Ian Wadham --- Not at all, Steve. No worries. I enjoyed the challenge! I was also a little worried that I might have left a time-limit in the algorithm that checks that the solution is unique. It runs until all possibilities are exhausted, which could take some time at Unlimited difficulty-level on the machines of 10 years ago. I keyed in your puzzle and KSudoku duly reported a unique solution. So all is OK. -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 384546] Generated killer sudoku puzzle with multiple valid solutions (ksudoku 1.3)
https://bugs.kde.org/show_bug.cgi?id=384546 Ian Wadham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #4 from Ian Wadham --- @Steve: I am the author of the puzzle generators and solvers in KSudoku. My congratulations to you on reaching Unlimited level in Killer KSudoku, but I am sorry, this is not a bug: the puzzle you show in your screenshot does indeed have a unique solution. The Notes you show are correct for normal constraints on rows, columns and 3x3 boxes and they can make cages add up correctly, BUT you have missed one further constraint, which applies to Killer KSudoku cages but not Mathdoku cages. All the digits in a Killer cage must be unique. In the cage with total 23 at top center, there is already a 1, so you cannot have a 1 in the bottom-right cell of that cage. It must be a 2. That forces the cell to its left to be a 7 and then the cage with total 18 must have unique contents. There is only one place its 7 can go. Thanks for the interesting case! -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 384546] Generated killer sudoku puzzle with multiple valid solutions (ksudoku 1.3)
https://bugs.kde.org/show_bug.cgi?id=384546 --- Comment #3 from Ian Wadham --- (In reply to Steve Soule from comment #2) > Your demand that I reproduce the bug is not reasonable, since that would > require a random number generator to produce precisely the same values as it > did before. @Steve: Not quite true. You can re-enter the cages and the initial clues, using the Enter In A Puzzle and Check buttons on the main-menu screen. A message comes up to tell you how to do that - see also the KSudoku Handbook. https://docs.kde.org/trunk5/en/ksudoku/ksudoku/interface.html#welcome-screen -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 429584] growisofs crashes @ 99%
https://bugs.kde.org/show_bug.cgi?id=429584 Ian Proudler changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Ian Proudler --- As requested, I tried burning a DVD-R again. The processes failed again (see below). Note that this time I asked k3b to only simulate the burning process (I was curious to see what it did in this mode and possibly avoid destroying a DVD-R). I am happy to try to burn a DVD-R for real if requested. The software on my system has been updated since my last post but the hardware is the same: Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-52-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™2 Quad CPU Q8200 @ 2.33GHz Memory: 3.8 GiB of RAM Graphics Processor: Mesa Intel® G41 Optical Drive: TSSTcorp CDDVDW SH-S223F k3B Error Message: Burned media --- DVD-R Sequential Devices --- TSSTcorp CDDVDW SH-S223F SB00 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump] [%7] System --- K3b Version: 21.12.3 KDE Version: 5.91.0 Qt Version: 5.15.3 Kernel: 5.15.0-52-generic Used versions --- growisofs: 7.1 growisofs --- Executing 'builtin_dd if=/dev/fd/0 of=/dev/sr0 obs=32k seek=0' /dev/sr0: engaging DVD-R DAO upon user request... /dev/sr0: reserving 1358065 blocks /dev/sr0: "Current Write Speed" is 18.4x1352KBps. 655360/2781317120 ( 0.0%) @0.0x, remaining 424:17 RBU 100.0% UBU 4.8% 655360/2781317120 ( 0.0%) @0.0x, remaining 707:09 RBU 100.0% UBU 100.0% 655360/2781317120 ( 0.0%) @0.0x, remaining 919:18 RBU 100.0% UBU 100.0% 655360/2781317120 ( 0.0%) @0.0x, remaining 1131:27 RBU 100.0% UBU 100.0% .. 2547220480/2781317120 (91.6%) @12.6x, remaining 0:17 RBU 100.0% UBU 96.4% 2613772288/2781317120 (94.0%) @14.4x, remaining 0:12 RBU 97.5% UBU 97.9% 2680979456/2781317120 (96.4%) @14.6x, remaining 0:07 RBU 100.0% UBU 97.6% :-[ WRITE@LBA=14b8f0h failed with SK=5h/ASC=21h/ACQ=04h]: Invalid argument :-( write failed: Invalid argument /dev/sr0: flushing cache growisofs command: --- /usr/bin/growisofs -Z /dev/sr0=/dev/fd/0 -use-the-force-luke=notray -use-the-force-luke=tty -use-the-force-luke=4gms -use-the-force-luke=tracksize:1358065 -use-the-force-luke=dummy -use-the-force-luke=dao:1358065 -dvd-compat -speed=18 -use-the-force-luke=bufsize:32m -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 461610] New: Crash while launching System setting > Appearance > Application style
https://bugs.kde.org/show_bug.cgi?id=461610
Bug ID: 461610
Summary: Crash while launching System setting > Appearance >
Application style
Classification: Applications
Product: systemsettings
Version: 5.26.3
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: r...@etik.com
Target Milestone: ---
Application: systemsettings (5.26.3)
Qt Version: 5.15.7
Frameworks Version: 5.99.0
Operating System: Linux 6.0.7-zen1-1-zen x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.26.3 [KCrashBackend]
-- Information about the crash:
Application: systemsettings (5.26.3)
Operating System: Arch Linux
KDE Plasma Version: 5.26.3
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.7
Kernel Version: 6.0.7-zen1-1-zen (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 4800U with Radeon Graphics
Memory: 15.0 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: LENOVO
Product Name: 82DM
-- Information about the crash:
System settings crashes when try to open Application Style menu in Appearance
menu. Other appearance menus work fine.
The crash can be produced every time both on x11 and wayland.
The crash can be reproduced every time.
-- Backtrace:
Application: 系统设置 (systemsettings), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#7 0x7f336f8a16b3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#8 0x7f336f851958 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#9 0x7f336f83b53d in __GI_abort () at abort.c:79
#10 0x7f336fe9fede in qt_message_fatal (message=...,
context=) at global/qlogging.cpp:1914
#11 QMessageLogger::fatal(char const*, ...) const (this=,
msg=) at global/qlogging.cpp:893
#12 0x7f336febdb93 in
QObjectPrivate::checkForIncompatibleLibraryVersion(int) const (this=, version=) at kernel/qobject_p.h:438
#13 QObjectPrivate::checkForIncompatibleLibraryVersion(int) const
(version=, this=) at kernel/qobject_p.h:430
#14 QObjectPrivate::QObjectPrivate(int) (this=,
version=, this=, version=) at
kernel/qobject.cpp:191
#15 0x7f33296bdca4 in () at /usr/lib/qt/plugins/styles/libqgtk2style.so
#16 0x7f3370de7634 in qLoadPlugin(QFactoryLoader
const*, QString const&) (key=..., loader=0x7f33712b93a0 <(anonymous
namespace)::Q_QGS_loader::innerFunction()::holder>) at
../../include/QtCore/5.15.7/QtCore/private/../../../../../src/corelib/plugin/qfactoryloader_p.h:108
#17 QStyleFactory::create(QString const&) (key=...) at
styles/qstylefactory.cpp:105
#18 0x7f3329c85e39 in PreviewItem::reload() (this=0x5632fe432560) at
/usr/src/debug/plasma-workspace/plasma-workspace-5.26.3/kcms/style/previewitem.cpp:106
#19 0x7f336dea4691 in
QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) (this=0x5632fd7441a0,
interrupt=...) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmlobjectcreator.cpp:1413
#20 0x7f336de4abef in
QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&)
(this=this@entry=0x5632ff4b7050, i=...) at
/usr/include/qt/QtCore/qscopedpointer.h:116
#21 0x7f336de4b596 in QQmlEnginePrivate::incubate(QQmlIncubator&,
QQmlContextData*) (this=0x5632fdbb24e0, i=,
forContext=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmlincubator.cpp:89
#22 0x7f336b329896 in
QQmlDelegateModelPrivate::object(QQmlListCompositor::Group, int,
QQmlIncubator::IncubationMode) (this=0x5632fe7ed470, group=,
index=6, incubationMode=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qmlmodels/qqmldelegatemodel.cpp:1324
#23 0x7f336e4f6f49 in QQuickItemViewPrivate::createItem(int,
QQmlIncubator::IncubationMode) (this=0x5632fdbf7200, modelIndex=6,
incubationMode=QQmlIncubator::AsynchronousIfNested) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquickitemview.cpp:2351
#24 0x7f336e4e54e2 in QQuickGridViewPrivate::addVisibleItems(double,
double, double, double, bool) (this=0x5632fdbf7200, fillFrom=-0, fillTo=1342,
bufferFrom=, bufferTo=, doBuffer=false) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquickgridview.cpp:520
#25 0x7f336e4f6657 in QQuickItemViewPrivate::refill(double, double)
(this=0x5632fdbf7200, from=-0, to=1342) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquickitemview.cpp:1801
#26 0x7f336e4fb1cd in QQuickItemViewPrivate::regenerate(bool)
(this=0x5632fdbf7200, orientationChanged=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquickitemview.cpp:1848
#27 0x7f336e4fb472 in QQuickItemViewPrivate::regenerate(bool)
(orientationChanged=false, this=0x5632fdbf7200) at
../../include/QtQmlModels/5.
[kdevelop] [Bug 375304] Documentation helper shifted
https://bugs.kde.org/show_bug.cgi?id=375304 Ian H changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 375543] Rename variable helper does not work in a few situations
https://bugs.kde.org/show_bug.cgi?id=375543 Ian H changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 369194] Background parser does not reparse other open files after changes
https://bugs.kde.org/show_bug.cgi?id=369194 Ian H changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368108] Adapt signature helper doesnt keep virtual
https://bugs.kde.org/show_bug.cgi?id=368108 Ian H changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Ian H --- Still broken in 22.04 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368107] Declaration helper/autocomplete not working
https://bugs.kde.org/show_bug.cgi?id=368107 Ian H changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 375304] Documentation helper shifted
https://bugs.kde.org/show_bug.cgi?id=375304 Ian H changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #2 from Ian H --- Seems fixed in latest -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 375156] Variable information popup closes too quickly
https://bugs.kde.org/show_bug.cgi?id=375156 Ian H changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Ian H --- This is still an issue -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 375543] Rename variable helper does not work in a few situations
https://bugs.kde.org/show_bug.cgi?id=375543 Ian H changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #2 from Ian H --- Seems to be fixed in latest -- You are receiving this mail because: You are watching all bug changes.
