[Kamera] [Bug 487824] New: Error "I/O busy" ("E/S en cours" in French) the second time a Kamera is tested with systemsettings
https://bugs.kde.org/show_bug.cgi?id=487824
Bug ID: 487824
Summary: Error "I/O busy" ("E/S en cours" in French) the second
time a Kamera is tested with systemsettings
Classification: Applications
Product: Kamera
Version: 24.02.2
Platform: openSUSE
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: General
Assignee: kdelibs-b...@kde.org
Reporter: pas...@orange.fr
Target Milestone: ---
SUMMARY
At first the camera is accessible without any issue and all the buttons in
kcm_kamera work. But, if I close systemsettings and open it again, I get error
"I/O busy" ("E/S en cours" in French). I need to restart the physical camera so
that I can access it again.
STEPS TO REPRODUCE
1. Switch camera on
2. Open kcm_kamera in systemsettings
3. Test camera
4. Close systemsettings
5. Open kcm_kamera in systemsettings
6. Test camera
OBSERVED RESULT
At step 3. test works, but at step 6., it does not and we get error "I/O busy"
("E/S en cours" in French)
EXPECTED RESULT
Test should work everytime
SOFTWARE/OS VERSIONS
Distribution: openSUSE Tumbleweed 20240517
Linux: 6.8.9-1-default (64-bit)
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0
gPhoto: 2.5.28
ADDITIONAL INFORMATION
Camera: Nikon Coolpix S5100
--
You are receiving this mail because:
You are watching all bug changes.
[ksysguard] [Bug 473052] System monitor grid style widget doesn't apply configured update interval to sensors
https://bugs.kde.org/show_bug.cgi?id=473052 Pascal Pollet changed: What|Removed |Added Version|5.27.7 |6.0.1 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 473052] System monitor grid style widget doesn't apply configured update interval to sensors
https://bugs.kde.org/show_bug.cgi?id=473052 Pascal Pollet changed: What|Removed |Added CC||pascal.pol...@mailbox.org --- Comment #1 from Pascal Pollet --- I can confirm this bug still exists. The short refresh interval causes a really high CPU usage, too high to use the grid layout in a plasmoid on a notebook. Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462093] Add support for clipboard sharing (copy-paste) under Wayland + KVM/QEMU + Spice
https://bugs.kde.org/show_bug.cgi?id=462093 Pascal changed: What|Removed |Added CC||co...@gmx.de --- Comment #4 from Pascal --- Plasma Version: 5.27.7 Frameworks Version: 5.108.0 Qt Version: 5.15.8 Graphics Platform: X11 (and Wayland), both experience the issue of the clipboard sharing between host and VM not being available, even with the spice-vdagent confirmed operating. Now, this was tested on a Kubuntu machine but also showed the same results on Debian's (12) default Plasma implementation. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 472374] File System Browser plugin search doesn't work
https://bugs.kde.org/show_bug.cgi?id=472374 --- Comment #6 from Pascal --- Interesting background and suggestion, Friedrich. Thanks for that. I see that you are on this issue for some time already. Since I'm new to this system, I'm not sure if your wish regarding the move addressed me or Waqar Ahmed, although I would assume the latter. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 472374] File System Browser plugin search doesn't work
https://bugs.kde.org/show_bug.cgi?id=472374 --- Comment #4 from Pascal --- Thanks for the tip and info. Much appreciated. I never tried that workaround but it's fine, once you know it. Regarding KIO, I'm assuming this means "KDE input/output" and that's where the fix has to happen? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 472374] File System Browser plugin search doesn't work
https://bugs.kde.org/show_bug.cgi?id=472374 --- Comment #2 from Pascal --- Even after being on the backports ppa in terms of timely updates (and possible fixes), the problem persists on current and freshly installed machines and is not present on older Kate builds. Strangely enough, I couldn't find any other reports about it. Additional input and/or confirmation welcome. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470861] Segmentation fault in Plasmashell when using xrandr
https://bugs.kde.org/show_bug.cgi?id=470861 Pascal changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from Pascal --- Problem resolved since 525.125.06 NVidia driver... -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 472374] File System Browser plugin search doesn't work
https://bugs.kde.org/show_bug.cgi?id=472374 --- Comment #1 from Pascal --- Adding: Searching terms within documents works fine. It's just the File System Browser's search that's affected. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 472374] New: File System Browser plugin search doesn't work
https://bugs.kde.org/show_bug.cgi?id=472374 Bug ID: 472374 Summary: File System Browser plugin search doesn't work Classification: Applications Product: kate Version: 23.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: co...@gmx.de Target Milestone: --- This may be present since a few versions but I ran into it just now, with 23.04.3 and corresponding plugins: The File System Browser's search feature doesn't really find files any more. STEPS TO REPRODUCE 1. Install 23.04.3 version of Kate plus corresponding plugins 2. Enable File System Browser plugin 3. Browse to folder with documents, try to search them and see if they show up OBSERVED RESULT Even when entering a proper search term (=string is included in file names), nothing shows up as result. EXPECTED RESULT With files named "Text File copy.txt" being present, a search for "Text" or "text" or even "tex" should show them. SOFTWARE/OS VERSIONS (happens on production system and freshly installed VM) Linux/KDE Plasma: Kubuntu 23.04 (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION (Screenshots) Files being present - trying to search them - results: zero [url=https://abload.de/image.php?img=kate3pddi3.png][img]https://abload.de/thumb/kate3pddi3.png[/img][/url] [url=https://abload.de/image.php?img=kate2r0efm.png][img]https://abload.de/thumb/kate2r0efm.png[/img][/url] [url=https://abload.de/image.php?img=kate1uycr5.png][img]https://abload.de/thumb/kate1uycr5.png[/img][/url] I've tried this on an older version of Kate and it worked as intended. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470861] Segmentation fault in Plasmashell when using xrandr
https://bugs.kde.org/show_bug.cgi?id=470861 --- Comment #2 from Pascal --- The reporter is unsure if this crash is reproducible. => the crash appears every time -- You are receiving this mail because: You are watching all bug changes.
[KClock] [Bug 471815] "Timer has completed" - Unable to stop the alarm sound and "completed" status once a timer ran out
https://bugs.kde.org/show_bug.cgi?id=471815 --- Comment #6 from Pascal --- Checked on the Kubuntu 23.04 VM: The "X" button usage on the system notification popup does not end the alarm sound, it just makes the system notification popup go away. When clicking on the system notification text however, the feature works as intended as the alarm sound stops and the Clock app ends the "Timer has finished" popup. -- You are receiving this mail because: You are watching all bug changes.
[KClock] [Bug 471815] "Timer has completed" - Unable to stop the alarm sound and "completed" status once a timer ran out
https://bugs.kde.org/show_bug.cgi?id=471815 Pascal changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #4 from Pascal --- You are very helpful indeed. I've just check different themes and it turns out that my (default) "Breeze Dark" theme is somehow broken when it comes to the colour of items like the "Dismiss" button. I've installed a fresh VM and there the dark and light themes do apply a proper colour to the button's text, to make it stand out from the background. Just my main machine doesn't and only when using this one theme. So, to recap: - The button was hardly visible, but that seems to be a problem caused by the theme on my machine - The notification can also be used to dismiss the alarm, but only when not closing it (notification) with "X" but just by click on the notification's text for example That leaves the author(s) of this app with no fault or bug at all. I shall remain grateful for your help displayed. :-) -- You are receiving this mail because: You are watching all bug changes.
[KClock] [Bug 471815] "Timer has completed" - Unable to stop the alarm sound and "completed" status once a timer ran out
https://bugs.kde.org/show_bug.cgi?id=471815 --- Comment #2 from Pascal --- Ha, thanks for your reply, I found the "dismiss" button thanks to your tip since it's invisible and it seems I've clicked everywhere, just not there. But... to correct myself, it's only almost(!) invisible and I can now spot it, even on my screenshot posted. Guess my theme (which is standard though) makes the text very light. So I have to admit, I might actually to dumb to just hit that button. The closing of the system notification did not succeed in stopping the alarm. That is, if one closes the system notification with the "X" like I did. If one just clicks on the notification itself, you are correct. Again, user error in some sense. Anyhow, here's the terminal output, in case it's still needed: flatpak run org.kde.kclock file:///usr/lib/qml/org/kde/kirigami.2/templates/InlineMessage.qml:265:13: QML SelectableLabel: Binding loop detected for property "implicitWidth" file:///usr/lib/qml/org/kde/kirigami.2/templates/InlineMessage.qml:265:13: QML SelectableLabel: Binding loop detected for property "implicitWidth" qrc:/qml/components/Sidebar.qml:13:1: QML Sidebar: Binding loop detected for property "contentHeight" QDBusConnection: name 'org.kde.kclockd' had owner '' but we thought it was ':1.307' file:///usr/lib/qml/org/kde/kirigami.2/ContextDrawer.qml:135:9: QML ListView: Binding loop detected for property "topMargin" file:///usr/lib/qml/org/kde/kirigami.2/Dialog.qml:335:9: QML ScrollView: Binding loop detected for property "calculatedImplicitHeight" file:///usr/lib/qml/org/kde/kirigami.2/Dialog.qml:335:9: QML ScrollView: Binding loop detected for property "calculatedImplicitHeight" qrc:/qml/components/DialogComboBox.qml:23:5: QML Dialog: Binding loop detected for property "implicitHeight" qrc:/qml/settings/SettingsPage.qml:33:9: QML FormLayout: Binding loop detected for property "implicitHeight" -- You are receiving this mail because: You are watching all bug changes.
[KClock] [Bug 471815] New: "Timer has completed" - Unable to stop the alarm sound and "completed" status once a timer ran out
https://bugs.kde.org/show_bug.cgi?id=471815 Bug ID: 471815 Summary: "Timer has completed" - Unable to stop the alarm sound and "completed" status once a timer ran out Classification: Applications Product: KClock Version: 23.04.2 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: espi...@gmail.com Reporter: co...@gmx.de CC: hanyo...@protonmail.com Target Milestone: --- SUMMARY Once a timer has completed, it sounds the alarm and opens the "Timer has finished" popup but there's no way to acknowledge the status, end the sound and get rid of the popup within the app. Screen: https://abload.de/img/time9iejd.png STEPS TO REPRODUCE 1. Set up timer 2. Let it run out 3. See the notification and hear the alarm sound but now try to stop it with a click or other commands OBSERVED RESULT The system-wide(!) notification about the timer having ended can be dismissed, one can even close "Clock" itself but the alarm sound and status of "Timer has completed" won't go away. Reopening the app presents the old status (see screenshot above). EXPECTED RESULT Timer runs out, sound and popup come up and can be dismissed with a click. The sound would then stop and you'd be able to set up a new timer or check other features of the app. SOFTWARE/OS VERSIONS Operating System: Kubuntu 23.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.0-24-generic (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION I didn't run into this for a long time since I've always ended timers before they ran out. Currently, the only way to make the sound go away and use this nice and helpful app for other timers is to kill the process, which resets the status. I will happily accept the fact that I seem to be the most inept person alive for not figuring out how one is supposed to dismiss an expired timer. :-) Eager to learn. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 470474] new nvidia beta driver (535 series) not showing statistics
https://bugs.kde.org/show_bug.cgi?id=470474 --- Comment #15 from Pascal --- In the name of us newbies, thanks for that explanation and work. Always fun to learn new things. :-) -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 470474] new nvidia beta driver (535 series) not showing statistics
https://bugs.kde.org/show_bug.cgi?id=470474 Pascal changed: What|Removed |Added CC||pasjo...@gmail.com Status|ASSIGNED|CONFIRMED --- Comment #11 from Pascal --- NVIDIA Driver Version (out of beta now): 535.54.03 on 2080 Super. Kubuntu. KDE Plasma: 5.27.4. KDE Frameworks Version: 5.104.0 Same problem here but it seems that Mangohud is unaffected and can read the info just fine, like it did with the previous 530 driver and there wasn't an update to Mangohud in between. It also doesn't help to change sensor definitions to "all GPUs" for testing since the data fields (I'm mainly monitoring temperatures and VRAM usage) remain at zero all the time no matter what. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470861] Segmentation fault in Plasmashell when using xrandr
https://bugs.kde.org/show_bug.cgi?id=470861 --- Comment #1 from Pascal --- it's the same error if I use nvidia-setting to add my tv screen... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470861] New: Segmentation fault in Plasmashell when using xrandr
https://bugs.kde.org/show_bug.cgi?id=470861 Bug ID: 470861 Summary: Segmentation fault in Plasmashell when using xrandr Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Debian unstable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: pascal.ra...@yahoo.fr CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-9-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: Hello I use xrandr to add my TV, which systematically causes fault segmentation, both when adding this screen and when removing it. here's the xrandr command to add my tv screen: xrandr --output DP-0 --mode 2560x1440 --scale 1x1 --output HDMI-0 --mode 3840x2160 --scale 0.x0. --same-as DP-0 and the reverse command : xrandr --output DP-0 --mode "2560x1440" --scale 1x1 --output HDMI-0 --off The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault PID: 4596 (plasmashell) UID: 1000 (nous) GID: 1000 (nous) Signal: 11 (SEGV) Timestamp: Sat 2023-06-10 10:32:00 CEST (3min 51s 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 (nous) Boot ID: d6f5cf5699544b319fc20fa350800fcd Machine ID: 6183a1b8d8a04da280211d5fd9e6bb95 Hostname: corto-maltese Storage: /var/lib/systemd/coredump/core.plasmashell.1000.d6f5cf5699544b319fc20fa350800fcd.4596.168638592000.zst (present) Size on Disk: 24.1M Message: Process 4596 (plasmashell) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.6-1.amd64 Module libudev.so.1 from deb systemd-252.6-1.amd64 Stack trace of thread 4596: #0 0x7f2afc6aebb4 pthread_sigmask (libc.so.6 + 0x8fbb4) #1 0x7f2afc65b179 sigprocmask (libc.so.6 + 0x3c179) #2 0x7f2afecb4e9b _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x4e9b) #3 0x7f2afecb5b3e _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b3e) #4 0x7f2afc65af90 n/a (libc.so.6 + 0x3bf90) #5 0x7f2afe86ad01 _ZNK12QQuickWindow16mouseGrabberItemEv (libQt5Quick.so.5 + 0x26ad01) #6 0x7f2afe86d53a _ZN19QQuickWindowPrivate13removeGrabberEP10QQuickItembb (libQt5Quick.so.5 + 0x26d53a) #7 0x7f2afe84d61e _ZN17QQuickItemPrivate24setEffectiveVisibleRecurEb (libQt5Quick.so.5 + 0x24d61e) #8 0x7f2afe84d651 _ZN17QQuickItemPrivate24setEffectiveVisibleRecurEb (libQt5Quick.so.5 + 0x24d651) #9 0x7f2afe84d651 _ZN17QQuickItemPrivate24setEffectiveVisibleRecurEb (libQt5Quick.so.5 + 0x24d651) #10 0x7f2afe84d651 _ZN17QQuickItemPrivate24setEffectiveVisibleRecurEb (libQt5Quick.so.5 + 0x24d651) #11 0x7f2afe84d651 _ZN17QQuickItemPrivate24setEffectiveVisibleRecurEb (libQt5Quick.so.5 + 0x24d651) #12 0x7f2afe84d651 _ZN17QQuickItemPrivate24setEffectiveVisibleRecurEb (libQt5Quick.so.5 + 0x24d651) #13 0x7f2afe84d651 _ZN17QQuickItemPrivate24setEffectiveVisibleRecurEb (libQt5Quick.so.5 + 0x24d651) #14 0x7f2afe84d651 _ZN17QQuickItemPrivate24setEffectiveVisibleRecurEb (libQt5Quick.so.5 + 0x24d651) #15 0x7f2afe84d651 _ZN17QQuickItemPrivate24setEffectiveVisibleRecurEb (libQt5Quick.so.5 + 0x24d651) #16 0x7f2afe84d783 _ZN17QQuickItemPrivate10setVisibleEb (libQt5Quick.so.5 + 0x24d783) #17 0x7f2afe85a983 _ZN10QQuickItem11qt_metacallEN11QMetaObject4CallEiPPv (libQt5Quick.so.5 + 0x25a983) #18 0x7f2aff13bb25 _ZN11PlasmaQuick15AppletQuickItem11qt_metacallEN11QMetaObject4CallEiPPv (libKF5PlasmaQuick.so.5 + 0x23b25) #19 0x7f2af4e81ec5 n/a (plasma_appletscript_declarative.so + 0x19ec5) #20 0x7f2af4e8f2c5 n/a (plasma_appletscript_declarative.so + 0x272c5) #21 0x7f2afe2822c1 _ZN19QQmlPropertyPrivate5writeEP7QObjectRK16QQmlPropertyDataRK8QVariantP15QQmlContextData6QFlagsINS2_9WriteFlagEE (libQt5Qml.so.5 + 0x2822c1) #22 0x7f2afe1a68ba
[kdenlive] [Bug 462596] kdenlive does not exit properly, and hangs indefinitely in other operations
https://bugs.kde.org/show_bug.cgi?id=462596 --- Comment #6 from Pascal Niklaus --- Created attachment 155367 --> https://bugs.kde.org/attachment.cgi?id=155367=edit backtrace after interruption during stuck quit operation backtrace, kdenlive compiled from latest master branch: Version 23.03.70 (rev. 230736067) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 462596] kdenlive does not exit properly, and hangs indefinitely in other operations
https://bugs.kde.org/show_bug.cgi?id=462596 --- Comment #5 from Pascal Niklaus --- (In reply to erjiang from comment #4) > Thanks for the very helpful backtrace. Looks like something weird is > happening when the MLT consumer is stopped when the clip/project monitor is > closed during application exit. I'm guessing this hang will never happen if > you close Kdenlive when the project is empty? It did also with the empty project. > Is there anything different about the desktop environments, GPU drivers, or > GPU driver versions between your two computers? Not that I would know of. The one with the problem just is an older, slower machine. > There were some bugs related to MLT multiprocessing that were fixed in > 22.12. If you can still reproduce this problem with Kdenlive 22.12, can you > try also getting a backtrace with additional debugging symbols? > > You should be able to do something like: > > $ export DEBUGINFOD_URLS="https://debuginfod.ubuntu.com; > $ gdb path/to/kdenlive > > It should ask you "Enable debuginfod for this session?" which should > additionally add symbols to your backtrace for the libraries you installed > via apt. (Instructions from: > https://ubuntu.com/server/docs/service-debuginfod ) I just did, and it seems that kdenlive still sometimes hangs when exiting. Just now, for example, I got this output: (gdb) run Starting program: /usr/local/bin/kdenlive [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x701fd640 (LWP 27603)] [New Thread 0x7fffef893640 (LWP 27604)] [New Thread 0x7fffed14d640 (LWP 27606)] [New Thread 0x7fffec918640 (LWP 27607)] Could not detect package type, probably default? App dir is "/usr/local/bin" profilePath from KdenliveSetting::mltPath: "/usr/share/mlt-7/profiles" meltPath from KdenliveSetting::rendererPath: "/usr/bin/melt-7" [New Thread 0x7fffc9f47640 (LWP 27608)] Empty metadata for "audiochannels" Empty metadata for "audioconvert" Empty metadata for "imageconvert" Empty metadata for "avcolour_space" Empty metadata for "avcolor_space" Empty metadata for "avdeinterlace" Empty metadata for "swscale" Empty metadata for "swresample" Empty metadata for "glsl.manager" Empty metadata for "movit.convert" Empty metadata for "movit.crop" Empty metadata for "movit.resample" Empty metadata for "movit.resize" Empty metadata for "telecide" Empty metadata for "deinterlace" plugin not available: "avfilter.acompressor" plugin not available: "avfilter.aecho" plugin not available: "avfilter.agate" plugin not available: "avfilter.atadenoise" plugin not available: "avfilter.bwdif" plugin not available: "avfilter.deblock" plugin not available: "avfilter.dedot" plugin not available: "avfilter.deflate" plugin not available: "avfilter.derain" plugin not available: "avfilter.doubleweave" plugin not available: "avfilter.field" plugin not available: "avfilter.framestep" plugin not available: "avfilter.fspp" plugin not available: "avfilter.graphmonitor" plugin not available: "avfilter.hqdn3d" plugin not available: "avfilter.inflate" plugin not available: "avfilter.lagfun" plugin not available: "avfilter.loudnorm" plugin not available: "avfilter.random" plugin not available: "avfilter.removegrain" plugin not available: "avfilter.separatefields" plugin not available: "avfilter.shuffleplanes" plugin not available: "avfilter.sr" plugin not available: "avfilter.tmix" plugin not available: "avfilter.w3fdif" plugin not available: "avfilter.weave" plugin not available: "avfilter.yadif" plugin not available: "frei0r.baltan" plugin not available: "frei0r.bgsubtract0r" plugin not available: "frei0r.bigsh0t_eq_mask" plugin not available: "frei0r.bigsh0t_eq_to_rect" plugin not available: "frei0r.bigsh0t_eq_to_stereo" plugin not available: "frei0r.bigsh0t_hemi_to_eq" plugin not available: "frei0r.bigsh0t_rect_to_eq" plugin not available: "frei0r.bigsh0t_stabilize_360" plugin not available: "frei0r.bigsh0t_transform_360" plugin not available: "frei0r.delay0r" plugin not available: "frei0r.delaygrab" plugin not available: "frei0r.facebl0r" plugin not available: "frei0r.facedetect" plugin not available: "frei0r.lightgraffiti" plugin not available: "frei0r.lightgraffiti" plugin not available: "frei0r.tehRoxx0r&qu
[kdenlive] [Bug 462596] kdenlive does not exit properly, and hangs indefinitely in other operations
https://bugs.kde.org/show_bug.cgi?id=462596 --- Comment #3 from Pascal Niklaus --- Created attachment 154304 --> https://bugs.kde.org/attachment.cgi?id=154304=edit gdb backtrace, kdenlive compiled from master branch with debug symbols -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 462596] kdenlive does not exit properly, and hangs indefinitely in other operations
https://bugs.kde.org/show_bug.cgi?id=462596 --- Comment #2 from Pascal Niklaus --- I now compiled kdenlive (master branch with debug symbols). The program sometimes terminates normally, but sometimes hangs, as did the version from the Ubuntu PPA. I attach the gdb backtrace to this update. Let me know if I can help with further tests/information. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 462596] kdenlive does not exit properly, and hangs indefinitely in other operations
https://bugs.kde.org/show_bug.cgi?id=462596 --- Comment #1 from Pascal Niklaus --- Addition: the problem also does not always occur. When playing around, I sometimes (but rarely) was able to quit kdenlive without it hanging. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 462596] New: kdenlive does not exit properly, and hangs indefinitely in other operations
https://bugs.kde.org/show_bug.cgi?id=462596 Bug ID: 462596 Summary: kdenlive does not exit properly, and hangs indefinitely in other operations Classification: Applications Product: kdenlive Version: 22.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: pascal+...@niklaus.org Target Milestone: --- Created attachment 154278 --> https://bugs.kde.org/attachment.cgi?id=154278=edit backtrace after interruption of application SUMMARY kdenlive hangs forever on 'quit' STEPS TO REPRODUCE 1. start kdenlive 2. quit the application OBSERVED RESULT Application never finishes EXPECTED RESULT Application should terminate SOFTWARE/OS VERSIONS Kdenlive: 22.08.3 Package Type: Unknown/Default MLT: 7.12.0 Qt: 5.15.3 (built against 5.15.3 x86_64-little_endian-lp64) Frameworks: 5.92.0 System: Ubuntu 22.04.1 LTS Kernel: linux 5.15.0-30-generic CPU: x86_64 Windowing System: xcb Movit (GPU): disabled Track Compositing: frei0r.cairoblend ADDITIONAL INFORMATION The problem occurs both with the AppImage as well as the Ubuntu PPA version. However, it only occurs on one of my computers. I observe a similar (?) problem when performing other operations within kdenlive. For example, when loading an existing project, "loading clips" never completes (the status stops at "99%"). I did look for debug symbols to run kdenlive from dbg, but these were not available in the ubuntu ppa. Nevertheless, running kdenlive from gdb, I get: (No debugging symbols found in kdenlive) (gdb) run Starting program: /usr/bin/kdenlive [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x70209640 (LWP 15984)] [New Thread 0x7fffef89f640 (LWP 15985)] [New Thread 0x7fffed15a640 (LWP 15987)] [New Thread 0x7fffec925640 (LWP 15988)] Could not detect package type, probably default? App dir is "/usr/bin" === /// CANNOT ACCESS SPEECH DICTIONARIES FOLDER profilePath from KdenliveSetting::mltPath: "/usr/share/mlt-7/profiles" meltPath from KdenliveSetting::rendererPath: "/usr/bin/melt-7" [New Thread 0x7fffc9f0a640 (LWP 15989)] Empty metadata for "audiochannels" Empty metadata for "audioconvert" Empty metadata for "imageconvert" Empty metadata for "avcolour_space" Empty metadata for "avcolor_space" Empty metadata for "avdeinterlace" Empty metadata for "swscale" Empty metadata for "swresample" Empty metadata for "glsl.manager" Empty metadata for "movit.convert" Empty metadata for "movit.crop" Empty metadata for "movit.resample" Empty metadata for "movit.resize" Empty metadata for "telecide" Empty metadata for "deinterlace" plugin not available: "avfilter.acompressor" plugin not available: "avfilter.aecho" plugin not available: "avfilter.agate" plugin not available: "avfilter.atadenoise" plugin not available: "avfilter.bwdif" plugin not available: "avfilter.deblock" plugin not available: "avfilter.dedot" plugin not available: "avfilter.deflate" plugin not available: "avfilter.derain" plugin not available: "avfilter.doubleweave" plugin not available: "avfilter.field" plugin not available: "avfilter.framestep" plugin not available: "avfilter.fspp" plugin not available: "avfilter.graphmonitor" plugin not available: "avfilter.hqdn3d" plugin not available: "avfilter.inflate" plugin not available: "avfilter.lagfun" plugin not available: "avfilter.loudnorm" plugin not available: "avfilter.random" plugin not available: "avfilter.removegrain" plugin not available: "avfilter.separatefields" plugin not available: "avfilter.shuffleplanes" plugin not available: "avfilter.sr" plugin not available: "avfilter.tmix" plugin not available: "avfilter.w3fdif" plugin not available: "avfilter.weave" plugin not available: "avfilter.yadif" plugin not available: "frei0r.baltan" plugin not available: "frei0r.bgsubtract0r" plugin not available: "frei0r.bigsh0t_eq_mask" plugin not available: "frei0r.bigsh0t_eq_to_rect" plugin not available: "frei0r.bigsh0t_eq_to_stereo" plugin not available: "frei0r.bigsh0t_hemi_to_eq" plugin not available: "frei0r.bigsh0t_rect_to_eq" plugin not available: "frei0r.bigsh0t_stabilize_360" plugin not available: "frei0r.bigsh0t_transform_360&qu
[kdenlive] [Bug 446838] edge cropping and transformation: different result in preview and rendered video
https://bugs.kde.org/show_bug.cgi?id=446838 --- Comment #1 from Pascal Niklaus --- Created attachment 144454 --> https://bugs.kde.org/attachment.cgi?id=144454=edit Preview in UI, and transformations applied This differs from the rendered content (other attachment) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 446838] New: edge cropping and transformation: different result in preview and rendered video
https://bugs.kde.org/show_bug.cgi?id=446838 Bug ID: 446838 Summary: edge cropping and transformation: different result in preview and rendered video Product: kdenlive Version: 21.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: pascal+...@niklaus.org Target Milestone: --- Created attachment 144453 --> https://bugs.kde.org/attachment.cgi?id=144453=edit rendered video SUMMARY *** When I combine edge cropping and a shift (transformation with X offset), the preview does not show what is rendered. *** STEPS TO REPRODUCE 1. Insert a clip 2. add transformation and edge crop operations (order does not matter) 3. compare rendered output and project (pre)view. See attachments for an example of the preview and settings, and what is rendered. OBSERVED RESULT Preview and rendered position of video are different. Notice that the blue "X" at the left is clipped in the rendered file, but not in the preview. EXPECTED RESULT The preview should correspond to what is rendered SOFTWARE/OS VERSIONS Kdenlive: 21.08.3 MLT: 7.2.0 Qt: 5.12.8 (built against 5.12.8 x86_64-little_endian-lp64) Frameworks: 5.68.0 System: Ubuntu 20.04.3 LTS Kernel: linux 5.4.0-91-generic CPU: x86_64 Windowing System: xcb Movit (GPU): disabled ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437232] Activities and desktop configuration lost after rebooting
https://bugs.kde.org/show_bug.cgi?id=437232 --- Comment #4 from Pascal Niklaus --- The problem did not occur in the past 2 weeks so that I can't provide additional info. I will do so when I encounter this situation again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437232] Activities and desktop configuration lost after rebooting
https://bugs.kde.org/show_bug.cgi?id=437232 --- Comment #2 from Pascal Niklaus --- Ok, now it happened again, but I doubt that I see the crashes that caused the problem. In the morning, all was fine despite these dumps. Upon booting in the afternoon, all activities and desktop settings disappeared again. I wonder whether this is related to restoring open applications. $ coredumpctl TIMEPID UID GID SIG COREFILE EXE Wed 2021-05-19 08:03:48 CEST 1154 124 133 31 error /lib/systemd/systemd-timesyncd Wed 2021-05-19 08:03:48 CEST 1190 124 133 31 error /lib/systemd/systemd-timesyncd Wed 2021-05-19 08:03:48 CEST 1199 124 133 31 error /lib/systemd/systemd-timesyncd Wed 2021-05-19 08:03:48 CEST 1208 124 133 31 error /lib/systemd/systemd-timesyncd Wed 2021-05-19 08:03:48 CEST 1217 124 133 31 error /lib/systemd/systemd-timesyncd Wed 2021-05-19 17:44:30 CEST 1158 124 133 31 error /lib/systemd/systemd-timesyncd Wed 2021-05-19 17:44:30 CEST 1190 124 133 31 error /lib/systemd/systemd-timesyncd Wed 2021-05-19 17:44:30 CEST 1201 124 133 31 error /lib/systemd/systemd-timesyncd Wed 2021-05-19 17:44:30 CEST 1210 124 133 31 error /lib/systemd/systemd-timesyncd Wed 2021-05-19 17:44:30 CEST 1219 124 133 31 error /lib/systemd/systemd-timesyncd $ sudo coredumpctl gdb 1219 PID: 1219 (systemd-timesyn) UID: 124 (systemd-timesync) GID: 133 (systemd-timesync) Signal: 31 (SYS) Timestamp: Wed 2021-05-19 17:44:30 CEST (17min ago) Command Line: /lib/systemd/systemd-timesyncd Executable: /lib/systemd/systemd-timesyncd Control Group: /system.slice/systemd-timesyncd.service Unit: systemd-timesyncd.service Slice: system.slice Boot ID: bb2da3ff86ca4d0e8e4e5ab4e4a7433a Machine ID: ee39478c6fbf4a679a3f0795d320f25c Hostname: Storage: /var/lib/systemd/coredump/core.systemd-timesyn.124.bb2da3ff86ca4d0e8e4e5ab4e4a7433a.1219.1621439070.lz4 Message: Process 1219 (systemd-timesyn) of user 124 dumped core. Stack trace of thread 1219: #0 0xf7f29e3b n/a (/lib/i386-linux-gnu/ld-2.31.so + 0x1be3b) #1 0xf7f28855 n/a (/lib/i386-linux-gnu/ld-2.31.so + 0x1a855) #2 0xf7f0ffc5 n/a (/lib/i386-linux-gnu/ld-2.31.so + 0x1fc5) #3 0xf7f0f12b n/a (/lib/i386-linux-gnu/ld-2.31.so + 0x112b) GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2 Copyright (C) 2020 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /lib/systemd/systemd-timesyncd... (No debugging symbols found in /lib/systemd/systemd-timesyncd) [New LWP 1219] Core was generated by `/lib/systemd/systemd-timesyncd'. Program terminated with signal SIGSYS, Bad system call. #0 0xf7f29e3b in ?? () (gdb) bt #0 0xf7f29e3b in ?? () #1 0x56627a10 in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) (gdb) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 437232] New: Activities and desktop configuration lost after rebooting
https://bugs.kde.org/show_bug.cgi?id=437232 Bug ID: 437232 Summary: Activities and desktop configuration lost after rebooting Product: dolphin Version: 20.04.2 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: pascal+...@niklaus.org CC: kfm-de...@kde.org Target Milestone: --- SUMMARY This is a problem that started to occur only recently. After rebooting, the activities I have defined (three of them) no longer appear (at least the activity pager widget is not there). Also, the desktop is plain black and no desktop widgets are present anymore. Logging out and in again at least helped for the pager to re-appear, but the desktop settings (e.g. background) were not restored. I needed to re-configure these. STEPS TO REPRODUCE This is difficult to tell, but the problem occurs with a certain regularity (but not always). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04.2 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 248310] Msn Plug in HACKER theme issue while message is received from others when they using black font colour
https://bugs.kde.org/show_bug.cgi?id=248310 Gautier Pascal changed: What|Removed |Added CC||christophedragu...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 316515] Hacking attempt
https://bugs.kde.org/show_bug.cgi?id=316515 --- Comment #1 from Gautier Pascal --- hello my name is gautier pascal and i don t speak english but i am a big problem with the ISLAMIST hacker they control all the system window,LINUX AND ONLY THE PHONE IN FRENCH AND THE ALL COUNTRY PLEASE CONTACT ME BECAUSE I AM VIDEOS TO explication control and explication hacking system . I think it is thery important because this Islamist is very BAD and they don t have control system informatiques internationnal pascal gautier && rue arsene orillaerd 86000 Poitiers France . tel0981601644 or tel 0760448123it is not a joke they are big importance for security all the men in the word... -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 316515] Hacking attempt
https://bugs.kde.org/show_bug.cgi?id=316515 Gautier Pascal changed: What|Removed |Added CC||christophedragu...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 123186] Impossible to create a new project (tested with C simple Hello world and C++ simple Hello world)
https://bugs.kde.org/show_bug.cgi?id=123186 Gautier Pascal changed: What|Removed |Added CC||christophedragu...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 430038] New: PDF page rendered white
https://bugs.kde.org/show_bug.cgi?id=430038 Bug ID: 430038 Summary: PDF page rendered white Product: okular Version: 1.9.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: pascal+...@niklaus.org Target Milestone: --- Created attachment 133886 --> https://bugs.kde.org/attachment.cgi?id=133886=edit shows as blank white page In several pdf documents, entire pages are displayed as blank white surface. This is not the case when I open the same PDFs using other tools, e.g. Firefox. pdfinfo does not report any problems. The attached page demonstrates one such problem. I do not attach other documents because they are copyrighted. However, I am happy to provide these files directly to developers. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 429490] New: Highly visible "Pointer Tool" for presentations
https://bugs.kde.org/show_bug.cgi?id=429490 Bug ID: 429490 Summary: Highly visible "Pointer Tool" for presentations Product: okular Version: 1.9.3 Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: pascal+...@niklaus.org Target Milestone: --- I regularly use okular for presentations. What I miss is a highly visible pointer cursor. The cursors for the various tools are not well visible in video conferences. This could, for example, be implemented as an additional tool (Pointer). I also use okular outside presentation mode (by streaming a section of my desktop, for example); for me it would be important to have this pointer cursor available also outside presentation mode. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 426055] New: Crash upon replying to SMS
https://bugs.kde.org/show_bug.cgi?id=426055 Bug ID: 426055 Summary: Crash upon replying to SMS Product: kdeconnect Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: pas...@dhermilly.dk Target Milestone: --- Application: kdeconnectd (1.4.0) Qt Version: 5.14.2 Frameworks Version: 5.73.0 Operating System: Linux 5.4.0-42-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.19 -- Information about the crash: - What I was doing when the application crashed: It crashed after I clicked Send to a SMS message that I had typed in after clicking Reply to an incoming SMS. BTW. My kdeconnect connection seems kind of flaky due some different wifis. Perhaps an assumption of the connection being up. -- Backtrace: Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault [KCrash Handler] #4 QHash::findNode (ahp=0x0, akey=..., this=0x56170e2f5120) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:944 #5 QHash::contains (akey=..., this=0x56170e2f5120) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:924 #6 QSet::contains (value=..., this=0x56170e2f5120) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qset.h:97 #7 KdeConnectPlugin::sendPacket (this=0x56170e22d820, np=...) at ./core/kdeconnectplugin.cpp:73 #8 0x7ff27df426b4 in NotificationsDbusInterface::sendReply (this=0x56170e319320, replyId=..., message=...) at ./plugins/notifications/notificationsdbusinterface.cpp:178 #9 0x7ff28ae3451e in QtPrivate::QSlotObjectBase::call (a=0x7ffdd5712a00, r=0x56170e319320, this=0x56170e7c0e10) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #10 doActivate (sender=0x56170e228ce0, signal_index=10, argv=0x7ffdd5712a00) at kernel/qobject.cpp:3870 #11 0x7ff28ae2eaf7 in QMetaObject::activate (sender=sender@entry=0x56170e228ce0, m=m@entry=0x7ff27df50b20 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffdd5712a00) at kernel/qobject.cpp:3930 #12 0x7ff27df3377b in SendReplyDialog::sendReply (this=this@entry=0x56170e228ce0, _t1=..., _t2=...) at ./obj-x86_64-linux-gnu/plugins/notifications/kdeconnect_notifications_autogen/EWIEGA46WW/moc_sendreplydialog.cpp:142 #13 0x7ff27df48fa0 in SendReplyDialog::sendButtonClicked (this=0x56170e228ce0) at ./plugins/notifications/sendreplydialog.cpp:53 #14 0x7ff28ae3451e in QtPrivate::QSlotObjectBase::call (a=0x7ffdd5712af0, r=0x56170e228ce0, this=0x56170e1e6470) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #15 doActivate (sender=0x56170e228ce0, signal_index=8, argv=0x7ffdd5712af0) at kernel/qobject.cpp:3870 #16 0x7ff28ae2eaf7 in QMetaObject::activate (sender=sender@entry=0x56170e228ce0, m=m@entry=0x7ff28becf880 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3930 #17 0x7ff28bbb5847 in QDialog::accepted (this=this@entry=0x56170e228ce0) at .moc/moc_qdialog.cpp:236 #18 0x7ff28bbb5ca8 in QDialogPrivate::finalize (this=, resultCode=1, dialogCode=) at dialogs/qdialog.cpp:176 #19 0x7ff28ae34550 in doActivate (sender=0x56170e4792e0, signal_index=8, argv=0x7ffdd5712bf0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395 #20 0x7ff28ae2eaf7 in QMetaObject::activate (sender=sender@entry=0x56170e4792e0, m=m@entry=0x7ff28bec8820 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3930 #21 0x7ff28bb4c2d7 in QDialogButtonBox::accepted (this=this@entry=0x56170e4792e0) at .moc/moc_qdialogbuttonbox.cpp:287 #22 0x7ff28bb4cb36 in QDialogButtonBoxPrivate::_q_handleButtonClicked (this=) at widgets/qdialogbuttonbox.cpp:878 #23 0x7ff28ae34550 in doActivate (sender=0x56170e496eb0, signal_index=9, argv=0x7ffdd5712d60) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395 #24 0x7ff28ae2eaf7 in QMetaObject::activate (sender=sender@entry=0x56170e496eb0, m=m@entry=0x7ff28bebf700 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffdd5712d60) at kernel/qobject.cpp:3930 #25 0x7ff28baa4c36 in QAbstractButton::clicked (this=this@entry=0x56170e496eb0, _t1=) at .moc/moc_qabstractbutton.cpp:313 #26 0x7ff28baa4e5e in QAbstractButtonPrivate::emitClicked (this=0x56170e492b70) at widgets/qabstractbutton.cpp:415 #27 0x7ff28baa5bc9 in QAbstractButton::click (this=0x56170e496eb0) at widgets/qabstractbutton.cpp:872 #28 QAbstractButton::click (this=0x56170e496eb0) at widgets/qabstractbutton.cpp:858 #29 0x7ff28ae3451e in QtPrivate::QSlotObjectBase::call (a=0x7ffdd5712e70, r=0x56170e496eb0, this=0x56170e65d1e0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #30 doActivate (sender=0x56170e400b60, signal_index=3, argv=0x7ffdd5712e70) at
[ksysguard] [Bug 381198] show combined memory usage when in tree view for e.g. Google chrome
https://bugs.kde.org/show_bug.cgi?id=381198 --- Comment #2 from Pascal d'Hermilly --- Hey yeah. I almost made a dupe of this which I apparently reported 3 years ago. Do people not know how to report wishes or is Patrick and I the only ones who want this? How else can I see total consumption? -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 381198] show combined memory usage when in tree view for e.g. Google chrome
https://bugs.kde.org/show_bug.cgi?id=381198 Pascal d'Hermilly changed: What|Removed |Added Version|5.10.1 |5.19.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 418283] Kdenlive crashes after not being able to save automatically
https://bugs.kde.org/show_bug.cgi?id=418283 --- Comment #2 from Pascal --- Hello Jean-Baptiste! Thank you for the answer. There's written I should replace FILENAME_MAX with NAME_MAX to solve the problem, but it is not stated in which file that should happen. E.g. In the kdenlive project file I do not find these expressions. Also down the page, I don't know what is meant by src/lib/io/kautosavefile.cpp, as there is no directory "src" in my root directory and I could not locate a file named kautosavefile.cpp. I also don't use kde, but Cinnamon. If you could give me a hint in what file to paste the patch, I would be very thankful! Best regards Pascal Schneider Am 28.02.20 um 11:44 schrieb Jean-Baptiste Mardelle: > https://bugs.kde.org/show_bug.cgi?id=418283 > > Jean-Baptiste Mardelle changed: > > What|Removed |Added > > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Jean-Baptiste Mardelle --- > This error was unfortunately related to a bug in KDE Frameworks < 5.66 > See this for reference and possible workaround: > https://bugs.kde.org/show_bug.cgi?id=412519 > -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 418283] New: Kdenlive crashes after not being able to save automatically
https://bugs.kde.org/show_bug.cgi?id=418283 Bug ID: 418283 Summary: Kdenlive crashes after not being able to save automatically Product: kdenlive Version: 19.12.2 Platform: Mint (Debian based) OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: p...@pascalschneider.eu Target Milestone: --- Created attachment 126474 --> https://bugs.kde.org/attachment.cgi?id=126474=edit The crash happens some seconds after the red error message appears. SUMMARY STEPS TO REPRODUCE 1. Start kdenlive, import files 2. put files in timeline 3. kdenlive wants to autosave, but cannot create autosave-files 4. kdenlive crashes OBSERVED RESULT crash after minor changes in project, working with kdenlive is impossible EXPECTED RESULT no crash SOFTWARE/OS VERSIONS Linux: Mint 19.3 Cinnamon / flatpack version ADDITIONAL INFORMATION It is possible to save the file after changes, so that the project can be opened again. But automatic saving seems to cause the issue. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417864] New: Crashed when unplugging power/hdmi/usb
https://bugs.kde.org/show_bug.cgi?id=417864 Bug ID: 417864 Summary: Crashed when unplugging power/hdmi/usb Product: systemsettings Version: 5.18.0 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: pas...@dhermilly.dk Target Milestone: --- Application: systemsettings5 (5.18.0) Qt Version: 5.13.2 Frameworks Version: 5.67.0 Operating System: Linux 5.3.0-40-generic x86_64 Windowing system: Wayland Distribution: KDE neon User Edition 5.18 -- Information about the crash: - What I was doing when the application crashed: I unplugged the power/hdmi/usb cable at the same time. KDED and and the power-manager died at the same time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6411926800 (LWP 7501))] Thread 7 (Thread 0x7f63d3de5700 (LWP 7516)): #0 0x7f640ce6dbf9 in __GI___poll (fds=0x7f63cc004db0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f640651c5c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f640651c6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f640d7c0acb in QEventDispatcherGlib::processEvents (this=0x7f63cc000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f640d760f9a in QEventLoop::exec (this=this@entry=0x7f63d3de4da0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f640d57c3aa in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7f640d57db52 in QThreadPrivate::start (arg=0x560bd4d96bd0) at thread/qthread_unix.cpp:360 #7 0x7f64088db6db in start_thread (arg=0x7f63d3de5700) at pthread_create.c:463 #8 0x7f640ce7a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f63d981f700 (LWP 7514)): #0 0x7f640ce690b4 in __GI___libc_read (fd=27, buf=0x7f63d981eb70, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f64065612d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f640651c0b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f640651c570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f640651c6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f640d7c0acb in QEventDispatcherGlib::processEvents (this=0x7f63d4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f640d760f9a in QEventLoop::exec (this=this@entry=0x7f63d981ed80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f640d57c3aa in QThread::exec (this=this@entry=0x560bcf332230) at thread/qthread.cpp:531 #8 0x7f640b101815 in QQmlThreadPrivate::run (this=0x560bcf332230) at qml/ftw/qqmlthread.cpp:152 #9 0x7f640d57db52 in QThreadPrivate::start (arg=0x560bcf332230) at thread/qthread_unix.cpp:360 #10 0x7f64088db6db in start_thread (arg=0x7f63d981f700) at pthread_create.c:463 #11 0x7f640ce7a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f63ea42e700 (LWP 7511)): #0 0x7f640ce690b4 in __GI___libc_read (fd=17, buf=0x7f63ea42db70, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f64065612d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f640651c0b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f640651c570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f640651c6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f640d7c0acb in QEventDispatcherGlib::processEvents (this=0x7f63eb20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f640d760f9a in QEventLoop::exec (this=this@entry=0x7f63ea42dd80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f640d57c3aa in QThread::exec (this=this@entry=0x560bc9723e50) at thread/qthread.cpp:531 #8 0x7f640b101815 in QQmlThreadPrivate::run (this=0x560bc9723e50) at qml/ftw/qqmlthread.cpp:152 #9 0x7f640d57db52 in QThreadPrivate::start (arg=0x560bc9723e50) at thread/qthread_unix.cpp:360 #10 0x7f64088db6db in start_thread (arg=0x7f63ea42e700) at pthread_create.c:463 #11 0x7f640ce7a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f63f2ca1700 (LWP 7509)): #0 0x7f640ce690b4 in __GI___libc_read (fd=20, buf=0x7f63f2ca0b70, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f64065612d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f640651c0b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f640651c570 in ?? () from
[frameworks-kwayland] [Bug 417177] Closing notebook lid / suspend to RAM causes powerdevil to crash in KWayland::Client::OutputDevice::enabled()
https://bugs.kde.org/show_bug.cgi?id=417177 --- Comment #2 from Pascal d'Hermilly --- Created attachment 126154 --> https://bugs.kde.org/attachment.cgi?id=126154=edit New crash information added by DrKonqi org_kde_powerdevil (2.0.0) using Qt 5.13.2 - What I was doing when the application crashed: in wayland. Unplugged the power, hdmi and usb keyboard at same time. KDED and systemsetings (looking at displays) also died. -- Backtrace (Reduced): #6 0x7fb0cca38564 in KWayland::Client::OutputDevice::enabled (this=0x563fb836cfb0) at ./src/client/outputdevice.cpp:535 #7 0x7fb0cc3bd566 in KScreen::WaylandOutput::updateKScreenOutput (this=this@entry=0x563fb8359dc0, output=...) at ./backends/kwayland/waylandoutput.cpp:102 #8 0x7fb0cc3be7fc in KScreen::WaylandOutput::toKScreenOutput (this=0x563fb8359dc0) at ./backends/kwayland/waylandoutput.cpp:94 #9 0x7fb0cc3b5e0e in KScreen::WaylandConfig::currentConfig (this=0x563fb82e4db0) at ./backends/kwayland/waylandconfig.cpp:294 #10 0x7fb0cc3b3cb3 in KScreen::WaylandBackendoperator() (__closure=) at ./backends/kwayland/waylandbackend.cpp:45 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 417177] Closing notebook lid / suspend to RAM causes powerdevil to crash in KWayland::Client::OutputDevice::enabled()
https://bugs.kde.org/show_bug.cgi?id=417177 Pascal d'Hermilly changed: What|Removed |Added CC||pas...@dhermilly.dk -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417482] New: Lock screen does not react on enter button if mistyped once
https://bugs.kde.org/show_bug.cgi?id=417482 Bug ID: 417482 Summary: Lock screen does not react on enter button if mistyped once Product: kwin Version: 5.18.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: pas...@dhermilly.dk Target Milestone: --- If you mistype your password then the lockscreen does react on pressing enter the second time (after reentering the password). This is ONLY for the main enter button - NOT for the Num-pad enter button which continues to work. STEPS TO REPRODUCE 1. Lock screen 2. Mistype password and press enter 3. enter new password and press enter again OBSERVED RESULT No reaction/submit from pressing enter button second time. EXPECTED RESULT Submit like first time enter was pressed. The login can still be done by clicking with mouse or pressing the numpad enter button. This regression appeared in Kwin 5.17, but I thought someone would quickly find and fix it ;-) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 397948] Animation stops working in presentation mode
https://bugs.kde.org/show_bug.cgi?id=397948 Pascal Niklaus changed: What|Removed |Added CC||pascal+...@niklaus.org --- Comment #7 from Pascal Niklaus --- Since this bug report is over a year old, I'd like to confirm that I experience the very same problem. In a LaTeX-beamer presentations, embedded videos play as expected, but they show up in the regular window instead of the presentation screen (I can switch back the regular window with alt-TAB and see the videos playing there). This thus seems not to be a problem with the video file itself or its embedding, bit with it being rendered at the wrong place. This occurs with okular 1.3.3 as distributed with Ubuntu 18.04.3 LTS. This problem did not occur with earlier versions of okular/KDE/???. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411369] New: Does not trigger lock screen if right click menu is shown
https://bugs.kde.org/show_bug.cgi?id=411369 Bug ID: 411369 Summary: Does not trigger lock screen if right click menu is shown Product: kwin Version: 5.16.4 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: pas...@dhermilly.dk Target Milestone: --- SUMMARY If you have a right click context menu open, the screen lock will not activate. Regardless. closing the lid sends the laptop to sleep and it wakes up without a lock screen. also triggering the lockscreen with a keyboard shortcut doesnt work. STEPS TO REPRODUCE 1. right click somewhere here on the browser 2. Trigger the lock screen. Meta+L or close laptop lid. OBSERVED RESULT No lock screen EXPECTED RESULT Locked screen requiring password SOFTWARE/OS VERSIONS Operating System: KDE neon 5.16 KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.61.0 Qt Version: 5.12.3 Kernel Version: 5.0.0-25-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 7,6 GiB of RAM ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdemultimedia] [Bug 368883] When Bluetooth autoconnect the audio device is not added
https://bugs.kde.org/show_bug.cgi?id=368883 Pascal d'Hermilly changed: What|Removed |Added CC||pas...@dhermilly.dk --- Comment #2 from Pascal d'Hermilly --- Yeah I confirm this - it's very annoying. I've had this for a year - hoping it goes away by it self. Using Sony WH-1000XM3 headset. Same behaviour as you describe: - When I turn on my headset it autoconnects, but the audio device is not added in the Audio systray icon- although the bluetooth systray icon has it registered as an "audio device". - If I click Disconnect and Connect in the bluetooth systray icon it will register the audio device in the audio system. >From KinfoCenter: Operating System: KDE neon 5.16 KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 Kernel Version: 4.15.0-54-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-5300U CPU @ 2.30GHz Memory: 7,7 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372576] Present Windows lags when closing window
https://bugs.kde.org/show_bug.cgi?id=372576 --- Comment #41 from Pascal d'Hermilly --- @michael Just to be clear. it's not enough just to hover on and off over the close icon - you have to trigger window enlarge/shrink effect(mouse hover in/out of window) to get the lag. I didn't mess with the themes: it's Breeze on Intel graphics. Enabling the FPS desktop effect shows me a drop from 60FPS to 1FPS during the lag. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372576] Present Windows lags when closing window
https://bugs.kde.org/show_bug.cgi?id=372576 --- Comment #38 from Pascal d'Hermilly --- Mostly gone. You can still trigger it by moving the mouse in and out over the close icon of the window. It almost feels like it's some bad connection between the animation of the close icon and the enlarge window under mouse animation. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 395596] [OpenVPN] qt version of network manager gui does not work with openvpn >= 2.4 configuration
https://bugs.kde.org/show_bug.cgi?id=395596 Pascal changed: What|Removed |Added Version|5.12.5 |5.15.2 Platform|Kubuntu Packages|Archlinux Packages CC||pascalarg...@gmx.ch --- Comment #5 from Pascal --- Same problem here. Looks like it's not solved yet. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401763] New: kpat fige plasma
https://bugs.kde.org/show_bug.cgi?id=401763 Bug ID: 401763 Summary: kpat fige plasma Product: plasmashell Version: 5.14.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: pascal.bial...@yahoo.fr CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.14.3) Qt Version: 5.11.2 Frameworks Version: 5.52.0 Operating System: Linux 4.19.5-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Using KPatience. The application often freezes, and causes overflows of memory, to saturate the swap. This weakens the system that struggles to recover. I have seen several versions of "kpat", plasma and linux for six months, and kpat works poorly. KPatience Version 3.6 Operating system: openSUSE Tumbleweed 20181203 KDE Plasma Version: 5.14.3 Qt version: 5.11.2 KDE Frameworks Version: 5.52.0 Core version: 4.19.5-1-default Operating system type: 64-bit Processors: 4 × AMD Phenom (TM) II X4 955 Processor Memory: 9.8 GB of RAM linux-4tv3 4.19.5-1-default #1 SMP PREEMPT Tue Nov 27 19:56:09 UTC 2018 (6210279) x86_64 x86_64 x86_64 GNU/Linux - Unusual behavior I noticed: The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f978eece4c0 (LWP 2735))] Thread 9 (Thread 0x7f975b39c700 (LWP 3386)): #0 0x7f9793b66b2c in QMutex::lock() () at /usr/lib64/libQt5Core.so.5 #1 0x7f9793d6da2f in () at /usr/lib64/libQt5Core.so.5 #2 0x7f9790e9b499 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #3 0x7f9790e9be7b in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f9790e9c06c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f9793d6db1b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f9793d1aafb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f9793b69de6 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f9795749396 in () at /usr/lib64/libQt5Quick.so.5 #9 0x7f9793b739b7 in () at /usr/lib64/libQt5Core.so.5 #10 0x7f979246e554 in start_thread () at /lib64/libpthread.so.0 #11 0x7f9793652ccf in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f976f7fe700 (LWP 3379)): #0 0x7f9792475808 in pthread_getspecific () at /lib64/libpthread.so.0 #1 0x7f9790ec4950 in g_thread_self () at /usr/lib64/libglib-2.0.so.0 #2 0x7f9790e9af9e in g_main_context_acquire () at /usr/lib64/libglib-2.0.so.0 #3 0x7f9790e9be05 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f9790e9c06c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f9793d6db1b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f9793d1aafb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f9793b69de6 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f976d2fc8b7 in KCupsConnection::run() () at /usr/lib64/libkcupslib.so #9 0x7f9793b739b7 in () at /usr/lib64/libQt5Core.so.5 #10 0x7f979246e554 in start_thread () at /lib64/libpthread.so.0 #11 0x7f9793652ccf in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f9774e9e700 (LWP 2952)): #0 0x7f9790ee2d89 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f9790e9c058 in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #2 0x7f9793d6db1b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f9793d1aafb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f9793b69de6 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #5 0x7f9793b739b7 in () at /usr/lib64/libQt5Core.so.5 #6 0x7f979246e554 in start_thread () at /lib64/libpthread.so.0 #7 0x7f9793652ccf in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f976700 (LWP 2878)): #0 0x7f97924744dc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f977b60ca2b in () at /usr/lib64/dri/r600_dri.so #2 0x7f977b60c757 in () at /usr/lib64/dri/r600_dri.so #3 0x7f979246e554 in start_thread () at /lib64/libpthread.so.0 #4 0x7f9793652ccf in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f9777c50700 (LWP 2877)): #0 0x7f97924744dc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f977b60ca2b in () at /usr/lib64/dri/r600_dri.so #2 0x7f977b60c757 in () at /usr/lib64/dri/r600_dri.so #3 0x7f979246e554 in start_thread () at /lib64/libpthread.so.0 #4 0x7f9793652ccf in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f9789f9b700 (LWP 2799)): #0
[kmail2] [Bug 393421] No ability to hide the HTML Message Status Bar
https://bugs.kde.org/show_bug.cgi?id=393421 Pascal Patry changed: What|Removed |Added CC||i...@invalidip.com --- Comment #31 from Pascal Patry --- This commit should definitely be reverted. Not only it removes a setting that we are used to set, it creates a flicker on the message pane. Whenever I switch folder, the bar disappears and it seems to appear again only once the content is displayed. So, the text in the email jump left then right every time I switch folder. In order to have a working Kmail again, I've reverted the patch and rebuild the latest FC28 RPMs. The message lib is freely available here: https://services.spectrumdt.com/RPMS/messagelib/ No bump in version were executed, so if you are running FC28, simply ensure that you have the latest version and then reinstall that RPM. # dnf update messagelib # rpm -vh --reinstall kf5-messagelib-18.04.3-1.fc28.x86_64.rpm -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397189] digikam is crashing when adding this photo
https://bugs.kde.org/show_bug.cgi?id=397189 --- Comment #5 from Pascal Megert --- Wow you guys are fast! I did an additional test by removing the makernote because of the Warning : [minor] Bad offset for MakerNotes tag 0x0060 in the exiftool log exiftool -makernotes= 20160821035715.jpg and it works with digikam! I've no clue which software or probably hardware created the Makernote. I guess it's an error in the Samsung Hardware. Any comments from you? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397189] digikam is crashing when adding this photo
https://bugs.kde.org/show_bug.cgi?id=397189 Pascal Megert changed: What|Removed |Added URL||https://www.dropbox.com/s/v ||5b2qm2ne1odzo1/201608210357 ||15.zip?dl=0 CC||pascal.meg...@gmx.ch --- Comment #1 from Pascal Megert --- The phot is bigger than 4000 KB. You can download it from my dropbox. https://www.dropbox.com/s/v5b2qm2ne1odzo1/20160821035715.zip?dl=0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397189] New: digikam is crashing when adding this photo
https://bugs.kde.org/show_bug.cgi?id=397189 Bug ID: 397189 Summary: digikam is crashing when adding this photo Product: digikam Version: 5.9.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Database-Albums Assignee: digikam-bugs-n...@kde.org Reporter: pascal.meg...@gmx.ch Target Milestone: --- Hi I've tried to add my extended photo collection to digikam. Unfortunately digikam was crashing all the time. So I tried to figure out the problem and to isolate one of the photos that crashes the software. The problem appears on MySQL and on SQLite database too. The attachment contains the photo. Kind regards Pascal -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 366342] System Load Viewer Plasmoid shows only used memory including cache
https://bugs.kde.org/show_bug.cgi?id=366342 Pascal d'Hermilly <pas...@dhermilly.dk> changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #5 from Pascal d'Hermilly <pas...@dhermilly.dk> --- Any chance to get this fixed before Plasma 5.13? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 394573] New: Revers geodata from open street map does not work
https://bugs.kde.org/show_bug.cgi?id=394573 Bug ID: 394573 Summary: Revers geodata from open street map does not work Product: digikam Version: 6.0.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Geolocation-ReverseGeoCoding Assignee: digikam-bugs-n...@kde.org Reporter: kikouca...@gmail.com Target Milestone: --- Revers geodata from Open Street Map does not works, Revers geodata from Geonames is ok. digikam-6.0.0-git-20180515T100301-x86-64.appimage now On older version where geodata on Open Street Map was working, it does not works any more. Perhaps some changes occur from Open Street Map side now? BRGDS -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 366342] System Load Viewer Plasmoid shows only used memory including cache
https://bugs.kde.org/show_bug.cgi?id=366342 --- Comment #4 from Pascal d'Hermilly <pas...@dhermilly.dk> --- > The disk cache is included in used memory. To clarify my point: misrepresented in the visualization of used memory. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 366342] System Load Viewer Plasmoid shows only used memory including cache
https://bugs.kde.org/show_bug.cgi?id=366342 Pascal d'Hermilly <pas...@dhermilly.dk> changed: What|Removed |Added CC||pas...@dhermilly.dk --- Comment #3 from Pascal d'Hermilly <pas...@dhermilly.dk> --- Created attachment 112373 --> https://bugs.kde.org/attachment.cgi?id=112373=edit Screenshot - load viewer plasmoid includes disk cache in used memory This is apparently an issue again. The disk cache is included in used memory. See attached screenshot. Please reopen. Plasma version 5.12.4 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 369676] White lockscreen text's readability depends on background
https://bugs.kde.org/show_bug.cgi?id=369676 --- Comment #27 from Pascal d'Hermilly <pas...@dhermilly.dk> --- Looks good. You can read the text with a white background, right? I'm having trouble imagining the whole thing from the explanation. Den 22. april 2018 16.41.19 CEST, Marco Martin <bugzilla_nore...@kde.org> skrev: >https://bugs.kde.org/show_bug.cgi?id=369676 > >Marco Martin <notm...@gmail.com> changed: > > What|Removed |Added > > Status|CONFIRMED |RESOLVED > Resolution|--- |FIXED > Latest Commit||https://commits.kde.org/pla > ||sma-workspace/448455c3c937c > ||ebc1358dc417b280b0008a4c196 > Version Fixed In||5.13 > >--- Comment #26 from Marco Martin <notm...@gmail.com> --- >Git commit 448455c3c937cebc1358dc417b280b0008a4c196 by Marco Martin. >Committed on 22/04/2018 at 14:41. >Pushed by mart into branch 'master'. > >fade to blur when the login box appears > >Summary: >for both lockscreen and login screen: > >* display the wallpaper and the clock with a shadow by default >* at the first mouse or keyboard input, make the input fields appear >* the actual controls appear pretty fast >* the wallpaper starts to blur, desaturate and fade to darker >* after 10 seconds make the controls disappear again > >* as soon as anything is written in the password field never fade out >the >controls >* if the virtual keyboard is open, never fade out the controls >* if anything is pushed on the stack, like "switch user", never fade >the >controls >* Esc clears the field and makes controls disappear (closing keyboard >if >needed) > >the fade won't happen if the background is a simple color >Related: bug 388622 >FIXED-IN: 5.13 > >Depends on D12314 > >Recommended D11309 and D11308 to change the default wallpaper to plasma >wallpaper > >Test Plan: tested the behavior of all the above points > >Reviewers: #plasma, #vdg, ngraham > >Reviewed By: #vdg, ngraham > >Subscribers: zzag, abetts, davidedmundson, ngraham, plasma-devel > >Tags: #plasma > >Differential Revision: https://phabricator.kde.org/D11928 > >M +4-2lookandfeel/contents/components/Clock.qml >M +0-1 >lookandfeel/contents/components/SessionManagementScreen.qml >A +182 -0lookandfeel/contents/components/WallpaperFader.qml >[License: >GPL (v2)] >M +81 -13 lookandfeel/contents/lockscreen/LockScreenUi.qml >M +2-0sddm-theme/Login.qml >M +308 -236 sddm-theme/Main.qml > >https://commits.kde.org/plasma-workspace/448455c3c937cebc1358dc417b280b0008a4c196 > >-- >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.
[plasmashell] [Bug 383828] Crash in QV4::QObjectWrapper::getProperty
https://bugs.kde.org/show_bug.cgi?id=383828 Pascal d'Hermilly <pas...@dhermilly.dk> changed: What|Removed |Added CC|pas...@dhermilly.dk | -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 393226] New: crash using EQAscom and Ekos on Kstars
https://bugs.kde.org/show_bug.cgi?id=393226 Bug ID: 393226 Summary: crash using EQAscom and Ekos on Kstars Product: kstars Version: 2.9.4 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: pascal.m...@laposte.net Target Milestone: --- Created attachment 112074 --> https://bugs.kde.org/attachment.cgi?id=112074=edit screen shot from the crash Hello, first, thank you for your work, Kstars is a very promising software. I tried to control my telescope with it but I encountered some problems. I use the Windows version, with the Indy server for Windows, all seems to be ok (Indy started, telescope connected and responding with the Ekos windows open) until I click on the sky to move the scope on an object for example. Kstars crash each time I click on the sky (single click) and I have no time to anything. I use EQAscom, I have the same problem with the EQascom simulator but not with others simulators. I think it is a bug but may be from EQAscom ... do you have an idea? Thanks. Regards. Pascal -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392922] digikam-6.0.0 fail to start
https://bugs.kde.org/show_bug.cgi?id=392922 --- Comment #4 from pascal lacroix <kikouca...@gmail.com> --- digikam-6.0.0-git-20180409T120742-x86-64.appimage with mysql start fine. Pascal LACROIX -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392922] New: digikam-6.0.0 fail to start
https://bugs.kde.org/show_bug.cgi?id=392922 Bug ID: 392922 Summary: digikam-6.0.0 fail to start Product: digikam Version: 6.0.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Bundle-AppImage Assignee: digikam-bugs-n...@kde.org Reporter: kikouca...@gmail.com Target Milestone: --- On linux Mint with mysql ./digikam-6.0.0-git-20180408T074316-x86-64.appimage fail to start with error: -- Use 'help' as CLI argument to know all available options for digiKam application /tmp/.mount_digikaqn0sjT/AppRun: ligne 35: erreur de syntaxe près du symbole inattendu « fi » /tmp/.mount_digikaqn0sjT/AppRun: ligne 35: `fi' ./digikam-6.0.0-git-20180407T123747-x86-64.appimage is working fine -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392123] Device notifier "eject" icon not updated
https://bugs.kde.org/show_bug.cgi?id=392123 --- Comment #2 from Pascal Niklaus <pascal+...@niklaus.org> --- I'm sorry, it actually works. I realized this only when preparing a screen cast. The reason I did not see that is that at least on my machine it takes several seconds for the icon to change. It seems that by then I always had left the notifier window and closed it by continuing to work in another area of the desktop, which had closed the notifier window. Some kind of more immediate visual feedback would be great that animates that the device actually is being mounted. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 392123] New: Device notifier "eject" icon not updated
https://bugs.kde.org/show_bug.cgi?id=392123 Bug ID: 392123 Summary: Device notifier "eject" icon not updated Product: frameworks-plasma Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: components Assignee: notm...@gmail.com Reporter: pascal+...@niklaus.org Target Milestone: --- After connecting an USB drive, the device notifier pops up. It is possible to mount the device by clicking on the downward triangle on the right of the device's name. It then is mounted. However, this icon does not change to the "mounted" state (which would be the icon to eject the device). There thus is no visual feedback and the indicated state is wrong. The opposite works: When a drive is ejected the icon changes to the "unmounted" state. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 390284] New: no such file errors
https://bugs.kde.org/show_bug.cgi?id=390284 Bug ID: 390284 Summary: no such file errors Product: okular Version: 1.1.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: EPub backend Assignee: okular-de...@kde.org Reporter: pascal+...@niklaus.org Target Milestone: --- When opening a .epub file, I get many errors like the one shown below printed to the terminal: libepub (II): OEBPS/html/030_c15.html#c15 - No such file Unzipping the .epub file shows that the file 'OEBPS/html/030_c15.html' exists. Is it the anchor (#c15) that is not stripped off? I cannot attach the file .epub file because it is copyright protected. I am happy to send it by separate mail to confirm the error. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 390162] Digikam-5.9.0 appimage fail to start
https://bugs.kde.org/show_bug.cgi?id=390162 --- Comment #4 from pascal lacroix <kikouca...@gmail.com> --- As you said, some users report a missing OpenAL shared lib to include in the bundle: I try with alsoft-conf and libopenal-dev installed and now, ./digikam-5.9.0-20180209T014824-x86-64.appimage start now properly on my system Pascal LACROIX -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 390162] Digikam-5.9.0 appimage fail to start
https://bugs.kde.org/show_bug.cgi?id=390162 --- Comment #3 from pascal lacroix <kikouca...@gmail.com> --- My system is Linux Mint 18.3 "Sylvia", Cinnamon 64-bits Pascal LACROIX -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 390162] New: Digikam-5.9.0 appimage fail to start
https://bugs.kde.org/show_bug.cgi?id=390162 Bug ID: 390162 Summary: Digikam-5.9.0 appimage fail to start Product: digikam Version: 5.9.0 Platform: Mint (Debian based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Bundle-AppImage Assignee: digikam-bugs-n...@kde.org Reporter: kikouca...@gmail.com Target Milestone: --- $ ./digikam-5.9.0-20180209T014824-x86-64.appimage -- digiKam AppImage Bundle ... capi::version: 0.6.0 ALSA lib conf.c:3750:(snd_config_update_r) Cannot access file ././/share/alsa/alsa.conf ALSA lib control.c:954:(snd_ctl_open_noupdate) Invalid CTL hw:0 AL lib: alsa.c:257: control open (0): Aucun fichier ou dossier de ce type ALSA lib conf.c:3750:(snd_config_update_r) Cannot access file ././/share/alsa/alsa.conf ALSA lib control.c:954:(snd_ctl_open_noupdate) Invalid CTL hw:0 digikam: src/hostapi/alsa/pa_linux_alsa.c :1454 : BuildDeviceList: l'assertion « devIdx < numDeviceNames » a échoué. /tmp/.mount_digikasdTlHs/AppRun : ligne 73 : 23514 Abandon digikam $@ $ ./digikam-5.9.0-20180201T052342-x86-64.appimage start fine -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 386048] Discover is not associated with flatpakref files on neon dev unstable
https://bugs.kde.org/show_bug.cgi?id=386048 Pascal d'Hermilly <pas...@dhermilly.dk> changed: What|Removed |Added CC||pas...@dhermilly.dk --- Comment #2 from Pascal d'Hermilly <pas...@dhermilly.dk> --- Tried to install latest libreoffice through a .flatpakref file - it just opens as a text file. Could be nice if the system knew how to open it. Tried a ton of variations, including plasma-discover --local-filename org.libreoffice.LibreOffice.flatpakref I couldn't make it work... Using KDE Neon user edition -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389769] New: crashes consistently when changing system tray entry to always show.
https://bugs.kde.org/show_bug.cgi?id=389769 Bug ID: 389769 Summary: crashes consistently when changing system tray entry to always show. Product: plasmashell Version: 5.11.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: pas...@dhermilly.dk Target Milestone: 1.0 Plasmashell crashes reliably when I change the system tray settings in whether to show or not show an entry (tested with Owncloud, Nextcloud and "Audio volume" across two laptops - one with a brand new profile). Steps to reproduce: 1) Go into System tray settings => entries 2) change Audio Volume to "hidden" or "shown" and click "OK" (not apply) (if it was on auto it does not crash now, only if changed from hidden or show) 3)Open settings again and change it to the opposite (hidden/shown) Here is a crash report which I'm told is low quality by the crash handler, but it might provide a hint. (It installed all the debug packages that the crash handler wanted ). Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f309c2f08c0 (LWP 5375))] Thread 11 (Thread 0x7f2fab7fe700 (LWP 16140)): #0 0x7f30960ae5c0 in QThreadData::current (createIfNecessary=createIfNecessary@entry=true) at thread/qthread_unix.cpp:245 #1 0x7f30962d95ba in postEventSourcePrepare (s=0x7f2f9c009d90, timeout=0x7f2fab7fdb14) at kernel/qeventdispatcher_glib.cpp:252 #2 0x7f309087491d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f30908752bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f309087549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f30962d96cb in QEventDispatcherGlib::processEvents (this=0x7f2f9c01b910, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f3096281e2a in QEventLoop::exec (this=this@entry=0x7f2fab7fdce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #7 0x7f30960aa8f4 in QThread::exec (this=this@entry=0x79e8cf0) at thread/qthread.cpp:515 #8 0x7f3099201d25 in QQmlThreadPrivate::run (this=0x79e8cf0) at qml/ftw/qqmlthread.cpp:147 #9 0x7f30960af709 in QThreadPrivate::start (arg=0x79e8cf0) at thread/qthread_unix.cpp:368 #10 0x7f3094f566ba in start_thread (arg=0x7f2fab7fe700) at pthread_create.c:333 #11 0x7f30959be41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 10 (Thread 0x7f2fb73fe700 (LWP 10723)): #0 0x7f30959b274d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f308a5d0861 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7f308a5c1e11 in pa_mainloop_poll () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f308a5c24ae in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f308a5c2560 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f308a5d07a9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f3089858078 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so #7 0x7f3094f566ba in start_thread (arg=0x7f2fb73fe700) at pthread_create.c:333 #8 0x7f30959be41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7f2fc1455700 (LWP 10722)): #0 0x7f30908b9a79 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f3090874929 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f30908752bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f309087549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f30962d96cb in QEventDispatcherGlib::processEvents (this=0x7f2fbc0013d0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f3096281e2a in QEventLoop::exec (this=this@entry=0x7f2fc1454ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f30960aa8f4 in QThread::exec (this=this@entry=0x155b1d0) at thread/qthread.cpp:515 #7 0x7f3099201d25 in QQmlThreadPrivate::run (this=0x155b1d0) at qml/ftw/qqmlthread.cpp:147 #8 0x7f30960af709 in QThreadPrivate::start (arg=0x155b1d0) at thread/qthread_unix.cpp:368 #9 0x7f3094f566ba in start_thread (arg=0x7f2fc1455700) at pthread_create.c:333 #10 0x7f30959be41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7f2fccd63700 (LWP 5594)): #0 0x7f30959ae27d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f30908b86f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3090874e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3090875330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4
[korganizer] [Bug 374761] Event/To-do/Journal editor fails to populate calendar combo box
https://bugs.kde.org/show_bug.cgi?id=374761 Pascal Raton <p@orange.fr> changed: What|Removed |Added CC||p@orange.fr --- Comment #4 from Pascal Raton <p@orange.fr> --- I've been having excatly the same problem for a while now Debian SID and korganiser v5.6.3 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 389062] New: After suspend: Does not discover external screen disconnect
https://bugs.kde.org/show_bug.cgi?id=389062 Bug ID: 389062 Summary: After suspend: Does not discover external screen disconnect Product: KScreen Version: 5.11.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kded Assignee: se...@kde.org Reporter: pas...@dhermilly.dk Target Milestone: --- An update in Plasma workspace 5.11.5 has meant that after I close the laptop connected to an external at work and open it at home my laptop displayt is off and thus black. Changing to another TTY works turns on the screen. Also typing password in the blind with the display off and pressing projector + function key will turn on the screen. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 196998] Konsole should reflow the text when resizing
https://bugs.kde.org/show_bug.cgi?id=196998 Pascal d'Hermilly <pas...@dhermilly.dk> changed: What|Removed |Added CC||pas...@dhermilly.dk -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 387364] makeUpdates 8 to 9 Failure executing query
https://bugs.kde.org/show_bug.cgi?id=387364 --- Comment #6 from pascal lacroix <kikouca...@gmail.com> --- Face DB update error fixed on ./digikam-5.8.0-20171212T132305-x86-64.appimage ... digikam.general: Camera XML data: "/home/pascalou/.local/share/digikam/cameras.xml" digikam.facedb: FaceDB SelectFaceSetting val ret = 0 digikam.facedb: FaceDB SelectFaceSetting val ret = 0 digikam.facedb: Face database: have a structure version "2" digikam.facesengine: Face database ready for use digikam.general: Face PipeLine: add database writer digikam.general: Face PipeLine: add faces trainer digikam.facesengine: Face database ready for use digikam.general: Face PipeLine: add database writer digikam.general: Face PipeLine: add faces trainer digikam.geoiface: "setting backend marble" QtAV 1.12.0(Jul 20 2017, 17:39:32) Multimedia framework base on Qt and FFmpeg. ... Bravo !!! Pascal -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 387364] makeUpdates 8 to 9 Failure executing query
https://bugs.kde.org/show_bug.cgi?id=387364 --- Comment #4 from pascal lacroix <kikouca...@gmail.com> --- DB update error almost fixed with pre-release : ./digikam-5.8.0-20171207T053823-x86-64.appimage ... digikam.database: Database Parameters: Type: "QMYSQL" DB Core Name: "digikamcore" DB Thumbs Name: "digikamthumbs" DB Face Name: "digikamface" Connect Options: "" Host Name:"127.0.0.1" Host port:3306 Internal Server: false Internal Server Path: "" Internal Server Serv Cmd: "" Internal Server Init Cmd: "" Username: "pascalou" Password: "" digikam.dbengine: Failure executing query: "" Error messages: "QMYSQL: Unable to execute query" "Table 'digikamcore.Albums' doesn't exist" 1146 2 Bound values: () digikam.dbengine: Error while executing DBAction [ "Migrate_Cleanup_Prepare" ] Statement [ "\nALTER TABLE Albums DROP FOREIGN KEY Albums_Images;\n" ] digikam.coredb: Core database: running schema update digikam.coredb: Core database: no database file available digikam.coredb: Core database: trying to copy contents from DB with ActionName: [ "Migrate_Read_AlbumRoots" ] to DB with ActionName [ "Migrate_Write_AlbumRoots" ] digikam.coredb: Core database: driver doesn't support query size. We try to go to the last row and back to the current. digikam.coredb: Core database: result size: [ 0 ] digikam.coredb: Core database: query isOnValidRow [ true ] isActive [ true ] result size: [ -1 ] digikam.coredb: Core database: column: [ "id" ] value [ QVariant(qlonglong, 1) ] digikam.coredb: Core database: column: [ "label" ] value [ QVariant(QString, "Images") ] digikam.coredb: Core database: column: [ "status" ] value [ QVariant(qlonglong, 0) ] digikam.coredb: Core database: column: [ "type" ] value [ QVariant(qlonglong, 1) ] digikam.coredb: Core database: column: [ "identifier" ] value [ QVariant(QString, "volumeid:?uuid=b077f6de-7757-4f4d-8869-0dbb54691b2c") ] digikam.coredb: Core database: column: [ "specificPath" ] value [ QVariant(QString, "/home/pascalou/Images") ] digikam.coredb: Core database: trying to copy contents from DB with ActionName: [ "Migrate_Read_Albums" ] to DB with ActionName [ "Migrate_Write_Albums" ] digikam.coredb: Core database: driver doesn't support query size. We try to go to the last row and back to the current. digikam.coredb: Core database: result size: [ 674 ] digikam.coredb: Core database: query isOnValidRow [ true ] isActive [ true ] result size: [ -1 ] digikam.coredb: Core database: column: [ "id" ] value [ QVariant(qlonglong, 1) ] digikam.coredb: Core database: column: [ "albumRoot" ] value [ QVariant(qlonglong, 1) ] digikam.coredb: Core database: column: [ "relativePath" ] value [ QVariant(QString, "/") ] digikam.coredb: Core database: column: [ "date" ] value [ QVariant(QString, "2017-12-03") ] digikam.coredb: Core database: column: [ "caption" ] value [ QVariant(QString, "") ] digikam.coredb: Core database: column: [ "collection" ] value [ QVariant(QString, "") ] digikam.coredb: Core database: query isOnValidRow [ true ] isActive [ true ] result size: [ -1 ] digikam.coredb: Core database: column: [ "id" ] value [ QVariant(qlonglong, 2) ] . After restart face database error : -- digiKam AppImage Bundle -- Use 'help' as CLI argument to know all available options QApplication: invalid style override passed, ignoring it. digikam.widgets: Breeze icons ressource file found digikam.general: AlbumWatch use QFileSystemWatcher digikam.general: Database Parameters: Type: "QMYSQL" DB Core Name: "digikamcore" DB Thumbs Name: "digikamthumbs" DB Face Name: "digikamface" Connect Options: "" Host Name:"127.0.0.1" Host port:3306 Internal Server: false Internal Server Path: "" Internal Server Serv Cmd: "" Internal Server Init Cmd: "" Username: "pascalou" Password: "" digikam.dbengine: Loading SQL code from config file "/tmp/.mount_sZUGaK/usr/share/digikam/database/dbconfig.xml" digikam.dbengine: Checking XML version ID => expected: 3 found: 3 digikam.coredb: Core database: running schema update digikam.coredb: Core database: have a structure version 9 digikam.coredb: C
[digikam] [Bug 387364] makeUpdates 8 to 9 Failure executing query
https://bugs.kde.org/show_bug.cgi?id=387364 --- Comment #3 from pascal lacroix <kikouca...@gmail.com> --- I will proceed this DB update soon as possible this WE and revert Pascal -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 387364] New: makeUpdates 8 to 9 Failure executing query
https://bugs.kde.org/show_bug.cgi?id=387364 Bug ID: 387364 Summary: makeUpdates 8 to 9 Failure executing query Product: digikam Version: 5.8.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Database-Mysql Assignee: digikam-bugs-n...@kde.org Reporter: kikouca...@gmail.com Target Milestone: --- Schema update to v9 failled Version du serveur : 10.2.10-MariaDB-10.2.10 ./digikam-5.8.0-20171126T055526-x86-64.appimage ... digikam.dbengine: Loading SQL code from config file "/tmp/.mount_yEHrA3/usr/share/digikam/database/dbconfig.xml" digikam.dbengine: Checking XML version ID => expected: 3 found: 3 digikam.coredb: Core database: running schema update digikam.coredb: Core database: have a structure version 8 digikam.coredb: Core database: makeUpdates 8 to 9 digikam.dbengine: Failure executing query: "" Error messages: "QMYSQL: Unable to execute query" "Cannot delete rows from table which is parent in a foreign key constraint 'ImageTagProperties_Tags' of table 'ImageTagProperties'" 1834 2 Bound values: () digikam.dbengine: Error while executing DBAction [ "UpdateSchemaFromV8ToV9" ] Statement [ "ALTER TABLE Tags MODIFY COLUMN name LONGTEXT CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL;" ] digikam.coredb: Core database: schema update to V 9 failed! digikam.coredb: Core database: cannot process schema initialization -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 385610] Lockscreen: don't time block password entry - only login attempts.
https://bugs.kde.org/show_bug.cgi?id=385610 --- Comment #4 from Pascal d'Hermilly <pas...@dhermilly.dk> --- ok. Thanks for listening :-) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 385610] Lockscreen: don't time block password entry - only login attempts.
https://bugs.kde.org/show_bug.cgi?id=385610 --- Comment #2 from Pascal d'Hermilly <pas...@dhermilly.dk> --- Right. But could it wait with the annoying part until after 3 failed attempts? 3 attempts isn't exactly "brute force". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385610] New: Lockscreen: don't time block password entry - only login attempts.
https://bugs.kde.org/show_bug.cgi?id=385610 Bug ID: 385610 Summary: Lockscreen: don't time block password entry - only login attempts. Product: kwin Version: 5.11.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: pas...@dhermilly.dk Target Milestone: --- If I mistype my password on the lock screen I have to wait ca. 3-5 seconds to reenter it. I could have spent the time to reenter the password. It should in my opinion only time block the login attempts. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 71870] Suggestions about task "Preload next image"
https://bugs.kde.org/show_bug.cgi?id=71870 Pascal d'Hermilly <pas...@dhermilly.dk> changed: What|Removed |Added CC||pas...@dhermilly.dk --- Comment #21 from Pascal d'Hermilly <pas...@dhermilly.dk> --- Jep. At least for network shares - E.g. try to view some images over webdav (e.g. an Owncloud/Nextcloud share). Each time you click next you have to wait for Gwenview to fetch the image from the server with a loading symbol. If Gwenview had already loaded the next file it would be instant unless you are flipping through faster than your disk/network access. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378010] Generic High CPU Usage Rendering
https://bugs.kde.org/show_bug.cgi?id=378010 Pascal d'Hermilly <pas...@dhermilly.dk> changed: What|Removed |Added CC|pas...@dhermilly.dk | -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 196998] Konsole should reflow the text when resizing
https://bugs.kde.org/show_bug.cgi?id=196998 Pascal d'Hermilly <pas...@dhermilly.dk> changed: What|Removed |Added CC|pas...@dhermilly.dk | -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 339752] enable max protocol SMB3
https://bugs.kde.org/show_bug.cgi?id=339752 --- Comment #3 from Pascal d'Hermilly <pas...@dhermilly.dk> --- (In reply to Pascal d'Hermilly from comment #2) > Microsoft says disable all SMBv1 [...] Just to be clear. What I mean is that Dolphin only hooking up to smbv1 is/will become like not having smb. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 339752] enable max protocol SMB3
https://bugs.kde.org/show_bug.cgi?id=339752 --- Comment #2 from Pascal d'Hermilly <pas...@dhermilly.dk> --- Microsoft says disable all SMBv1 after wannacry and petaya and just announced new flaw. https://www.onmsft.com/news/microsoft-wont-patch-20-yr-old-smbv1-vulnerability-you-should-just-turn-the-service-off -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 368454] Easily enable automatic security/all updates
https://bugs.kde.org/show_bug.cgi?id=368454 --- Comment #6 from Pascal d'Hermilly <pas...@dhermilly.dk> --- I my view this is Neon packaging/plumbing. There is an LTS - it should be easy to tell it to just keep the system up to date. In Kubuntu it was ticking a checkbox and it took care of things. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 382088] New: power on battery: Does not consider mutiple batteries
https://bugs.kde.org/show_bug.cgi?id=382088 Bug ID: 382088 Summary: power on battery: Does not consider mutiple batteries Product: Powerdevil Version: 5.10.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-de...@kde.org Reporter: pas...@dhermilly.dk Target Milestone: --- The time left on battery seem to only consider one of the batteries. Powertop estimate the double time left on battery. I have 2 batteries in my Thinkpad - a removable and an internal. Actually - I see now that kinfocenter shows a consumption rate of 17 W versus powertop saying 8 W. It could also be this that is influencing the estimates... -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 299517] Skanlite should support scan to pdf.
https://bugs.kde.org/show_bug.cgi?id=299517 Pascal d'Hermilly <pas...@dhermilly.dk> changed: What|Removed |Added CC||pas...@dhermilly.dk --- Comment #15 from Pascal d'Hermilly <pas...@dhermilly.dk> --- is it wontfix? -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 381198] New: show combined memory usage when in tree view for e.g. Google chrome
https://bugs.kde.org/show_bug.cgi?id=381198 Bug ID: 381198 Summary: show combined memory usage when in tree view for e.g. Google chrome Product: ksysguard Version: 5.10.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: pas...@dhermilly.dk Target Milestone: --- It would be nice too see how much memory for example Google Chrome uses. right now it's not possible due to being spread on many processes. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 381063] New: Plantage de Krunner
https://bugs.kde.org/show_bug.cgi?id=381063 Bug ID: 381063 Summary: Plantage de Krunner Product: krunner Version: 5.10.0 Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: athu...@hotmail.com Target Milestone: --- Application: krunner (5.10.0) Qt Version: 5.9.0 Frameworks Version: 5.34.0 Operating System: Linux 4.10.9-1 x86_64 Distribution: "KaOS" -- Information about the crash: - What I was doing when the application crashed: le desktop était completement vide, je tape par erreur quelques caracteres ce qui a pour effet de lancer krunner, je vois les caracteres s'afficher dans la fenetre d'entree, j'appuie alors sur ECHAP pour sortir de krunner et un rapport de plantage apparait The crash can be reproduced sometimes. -- Backtrace: Application: krunner (krunner), signal: Segmentation fault Using host libthread_db library "/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f23f7def840 (LWP 20367))] Thread 14 (Thread 0x7f23b37fe700 (LWP 20380)): #0 0x7f2404e845cf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0 #1 0x7f24073993bb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f23ddebb57f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f23ddebf838 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f23ddeba71f in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f23ddebf882 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f23ddeba71f in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f23ddebd00f in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f240739858a in () at /usr/lib/libQt5Core.so.5 #9 0x7f2404e7e494 in start_thread () at /lib/libpthread.so.0 #10 0x7f2406cb86ff in clone () at /lib/libc.so.6 Thread 13 (Thread 0x7f23b3fff700 (LWP 20379)): #0 0x7f2404e845cf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0 #1 0x7f24073993bb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f23ddebb57f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f23ddebf838 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f23ddeba71f in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f23ddebd00f in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f240739858a in () at /usr/lib/libQt5Core.so.5 #7 0x7f2404e7e494 in start_thread () at /lib/libpthread.so.0 #8 0x7f2406cb86ff in clone () at /lib/libc.so.6 Thread 12 (Thread 0x7f23c8ec5700 (LWP 20378)): #0 0x7f2404e845cf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0 #1 0x7f24073993bb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f23ddebb57f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f23ddebf838 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f23ddeba71f in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f23ddebf882 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f23ddeba71f in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f23ddebd00f in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f240739858a in () at /usr/lib/libQt5Core.so.5 #9 0x7f2404e7e494 in start_thread () at /lib/libpthread.so.0 #10 0x7f2406cb86ff in clone () at /lib/libc.so.6 Thread 11 (Thread 0x7f23c96c6700 (LWP 20377)): [KCrash Handler] #5 0x7f2406c53ff4 in __memmove_sse2_unaligned_erms () at /lib/libc.so.6 #6 0x7f23d674fbec in () at /usr/lib/libKF5BalooEngine.so.5 #7 0x7f23d6738056 in Baloo::PostingDB::iter(QByteArray const&) () at /usr/lib/libKF5BalooEngine.so.5 #8 0x7f23d6743a1a in Baloo::Transaction::postingIterator(Baloo::EngineQuery const&) const () at /usr/lib/libKF5BalooEngine.so.5 #9 0x7f23d6ba1da6 in () at /usr/lib/libKF5Baloo.so.5 #10 0x7f23d6ba1f19 in () at /usr/lib/libKF5Baloo.so.5 #11 0x7f23d6ba3180 in () at /usr/lib/libKF5Baloo.so.5 #12 0x7f23d6b8f54f in Baloo::Query::exec() () at /usr/lib/libKF5Baloo.so.5 #13 0x7f23d6ddd579 in () at /usr/lib/qt5/plugins/krunner_baloosearchrunner.so #14 0x7f23d6dde6e9 in () at
[Powerdevil] [Bug 378498] Power settings missing scrollbar
https://bugs.kde.org/show_bug.cgi?id=378498 --- Comment #3 from Pascal d'Hermilly <pas...@dhermilly.dk> --- Confirmed happening in kcmshell5 5.10.1 -- You are receiving this mail because: You are watching all bug changes.
[user-manager] [Bug 380230] User manager: UID 1001 can see all users. UID 1000 cannot see user he created
https://bugs.kde.org/show_bug.cgi?id=380230 --- Comment #2 from Pascal d'Hermilly <pas...@dhermilly.dk> --- There is no qdbus-qt5 on my system. I'm guessing that qdbus is the same... pascal@nts-ThinkPad-T450:~$ qdbus --system org.freedesktop.Accounts / /org /org/freedesktop /org/freedesktop/Accounts /org/freedesktop/Accounts/User1001 /org/freedesktop/Accounts/User1000 I'm getting exactly same result on the nts user which is not showing the pascal account. BTW. I noticed there is something installed called qdbusviewer that is failing with some missing QT4. pascal@nts-ThinkPad-T450:~$ qdbusviewer qdbusviewer: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/qdbusviewer': No such file or directory My OS is KDE neon user edtion installed a month ago with extra programs. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 380230] New: User manager: UID 1001 can see all users. UID 1000 cannot see user he created
https://bugs.kde.org/show_bug.cgi?id=380230 Bug ID: 380230 Summary: User manager: UID 1001 can see all users. UID 1000 cannot see user he created Product: systemsettings Version: 5.9.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: pas...@dhermilly.dk Target Milestone: --- I created a user, pascal(1001), from user nts(1000) using user manager. The user works great - logged in and everything. But it's not listed in nts's user managers list. Strange thing is that nts is listed in the user manager for pascal. User manager: - nts only sees nts - pascal sees both nts and pascal. Adding a third (now non-administrative) user: - nts sees nts and test user - pascal sees nts, pascal and test user Adding a third user, it is listed both in /etc/passwd: nts:x:1000:1000:nts,,,:/home/nts:/bin/bash pascal:x:1001:1001:Pascal d'Hermilly:/home/pascal:/bin/bash test:x:1002:1002:test,,,:/home/test:/bin/bash -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 380180] New: Add option to user manager: encrypt home dir
https://bugs.kde.org/show_bug.cgi?id=380180 Bug ID: 380180 Summary: Add option to user manager: encrypt home dir Product: systemsettings Version: 5.9.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: pas...@dhermilly.dk Target Milestone: --- like a checkbox for administrator, it would be very nice to have "encrypt the home folder". background: My home dir is encrypted, but after creating another user, I saw that it is not encrypted like my original account created during installation. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 380079] New: Cannot get to apply button with display resolution 1366x768
https://bugs.kde.org/show_bug.cgi?id=380079 Bug ID: 380079 Summary: Cannot get to apply button with display resolution 1366x768 Product: systemsettings Version: 5.9.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcmshell Assignee: kdelibs-b...@kde.org Reporter: pas...@dhermilly.dk Target Milestone: --- There is no scrollbar for large settings pages directly invoked. E.g. I clicked opened the power settings via the power manager applet in the systray. When opened directly there is no scroll bar and I cannot get to the apply button. When opened through system settings there is a scroll bar and everything works great. My display resolution is 1366x768 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 371722] Let crash handler install debug packages
https://bugs.kde.org/show_bug.cgi?id=371722
--- Comment #10 from Pascal d'Hermilly <pas...@dhermilly.dk> ---
(In reply to Harald Sitter from comment #9)
> if you could run the installer manually on a terminal and paste the output
> here that'd be very handy
>
> drkonqi-pk-debug-installer /usr/bin/plasmashell
It seems to work flawlessly. It asks me for a password.
I've not filled it because I want to see it work for when I actually have a
crash.
output in case you can still use it:
drkonqi-pk-debug-installer /usr/bin/plasmashell
PackageKit::Transaction(0xf42b80)
FileResolver(0xf45450) found
"plasma-workspace;4:5.9.5.1-0neon+16.04+build75;amd64;installed:neon-xenial-main"
candidates ("plasma-workspace-dbgsym", "plasma-workspace-dbg")
DebugResolver(0xf463e0) dbgfound
"plasma-workspace-dbg;4:5.5.5.2-0ubuntu1;i386;ubuntu-xenial-universe" ()
DebugResolver(0xf463e0) 1
DebugResolver(0xf463e0) dbgfound
"plasma-workspace-dbg;4:5.9.5.1-0neon+16.04+build75;amd64;neon-xenial-main"
("plasma-workspace-dbg;4:5.5.5.2-0ubuntu1;i386;ubuntu-xenial-universe")
DebugResolver(0xf463e0) 2
FileResolver(0xf45450) ++ packages for
"plasma-workspace;4:5.9.5.1-0neon+16.04+build75;amd64;installed:neon-xenial-main"
("plasma-workspace-dbg;4:5.9.5.1-0neon+16.04+build75;amd64;neon-xenial-main")
"plasma-workspace;4:5.9.5.1-0neon+16.04+build75;amd64;installed:neon-xenial-main"
("plasma-workspace-dbg;4:5.9.5.1-0neon+16.04+build75;amd64;neon-xenial-main")
QSet(FileResolver(0xf45450)) FileResolver(0xf45450)
DO INSTALL
QSet("plasma-workspace-dbg;4:5.9.5.1-0neon+16.04+build75;amd64;neon-xenial-main")
2
--
You are receiving this mail because:
You are watching all bug changes.
[neon] [Bug 371722] Let crash handler install debug packages
https://bugs.kde.org/show_bug.cgi?id=371722 --- Comment #7 from Pascal d'Hermilly <pas...@dhermilly.dk> --- (In reply to Harald Sitter from comment #6) > Nope it's installing after you've authenticated. But it didn't ask me to authenticate - even check for hidden windows in the taskbar. Eventually I clicked cancel and drkonqi crashed and also wanted to install debug packages for it. From there it could have been an endless loop, it seems ;-) -- You are receiving this mail because: You are watching all bug changes.
