[digikam] [Bug 328321] Image orientation is not maintained when processing RAW image through BQM
https://bugs.kde.org/show_bug.cgi?id=328321 Marc changed: What|Removed |Added CC||erme...@gmail.com --- Comment #9 from Marc --- Hello, this report duplicate #369668 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 363224] Kwin crashes from time to time (this time using Virtual Machine Manager)
https://bugs.kde.org/show_bug.cgi?id=363224 --- Comment #22 from marc --- Yes, and it seems to be related to either 'APIC' option in VirtualBox, or Compositing enabled in KWin (doesn't seem to appear if it's disabled) . Need to do more tests to confirm, if time allows Dnia 2 listopada 2016 15:53:44 CET, "Martin Gräßlin" napisał(a): >https://bugs.kde.org/show_bug.cgi?id=363224 > >--- Comment #21 from Martin Gräßlin --- >Anyone still experiencing the problem with KWin 5.8? > >-- >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.
[kwin] [Bug 363224] Kwin crashes from time to time (this time using Virtual Machine Manager)
https://bugs.kde.org/show_bug.cgi?id=363224 --- Comment #23 from marc --- Dnia środa, 2 listopada 2016 14:53:44 CET piszesz: > https://bugs.kde.org/show_bug.cgi?id=363224 > > --- Comment #21 from Martin Gräßlin --- > Anyone still experiencing the problem with KWin 5.8? OK, I can confirm that it only happens with compositing turned "on" - no matter which engine is being used [OpenGL 2/3.1/XRender]. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 363224] Kwin crashes from time to time (this time using Virtual Machine Manager)
https://bugs.kde.org/show_bug.cgi?id=363224 --- Comment #24 from marc --- Dnia środa, 2 listopada 2016 14:53:44 CET piszesz: > https://bugs.kde.org/show_bug.cgi?id=363224 > > --- Comment #21 from Martin Gräßlin --- > Anyone still experiencing the problem with KWin 5.8? OK, some more useful info: This issue appears ONLY if "Enable 3D acceleration" is enabled on "Virtualbox > Display > Display" tab ... Hope this helps a bit to find the source of this issue. Seems like VBox tries to use some kind of 3D accel subsystem and turns it on in a wrong way, or whatever. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467596] New: Doesnt Play both audio tracks during playback
https://bugs.kde.org/show_bug.cgi?id=467596 Bug ID: 467596 Summary: Doesnt Play both audio tracks during playback Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: lil.m...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. record a clip with mic and desktop audio separated (captured on obs) 2. load in your clip that has 2 audio tracks 3. preview it, it only plays desktop audio. Note: this is only for previewing it, if the clip is in the timeline it will play both audio's correctly through the timeline playback. This if frustrating when trimming clips because some clips context comes through the mic audio. OBSERVED RESULT Only hearing desktop audio when previewing a clip EXPECTED RESULT Hearing both desktop and mic audio when previewing a clip SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 467596] Doesnt Play both audio tracks during playback
https://bugs.kde.org/show_bug.cgi?id=467596 Marc changed: What|Removed |Added Component|general |User Interface Product|kde |kdenlive Version|unspecified |22.08.1 Assignee|unassigned-b...@kde.org |j...@kdenlive.org -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 467596] Doesnt Play both audio tracks during playback
https://bugs.kde.org/show_bug.cgi?id=467596 Marc changed: What|Removed |Added Platform|Other |Microsoft Windows OS|Other |Microsoft Windows -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 467596] Doesnt Play both audio tracks during playback
https://bugs.kde.org/show_bug.cgi?id=467596 Marc changed: What|Removed |Added Version|22.08.1 |22.12.3 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 471072] New: Home view is blank
https://bugs.kde.org/show_bug.cgi?id=471072 Bug ID: 471072 Summary: Home view is blank Classification: Applications Product: kmymoney Version: 5.1.3 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: photosnaps...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS macOS: Ventura (13.4) (Mac silicon) Kmymoney ver 5.1.3-d7dd9f8dd ADDITIONAL INFORMATION Home View is blank. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481374] Graphics performance in QEMU/KVM guest with virGL is bad on Wayland
https://bugs.kde.org/show_bug.cgi?id=481374 --- Comment #7 from Marc --- Created attachment 170960 --> https://bugs.kde.org/attachment.cgi?id=170960&action=edit plasma-kwin_wayland service log There you go. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481374] Graphics performance in QEMU/KVM guest with virGL is bad on Wayland
https://bugs.kde.org/show_bug.cgi?id=481374
--- Comment #9 from Marc ---
(In reply to Zamundaaa from comment #8)
> Okay, KWin is using legacy modesetting, with XRGB as the buffer format.
> I can't think of any reason this would be slow, without Xorg also being slow
Note that if my mouse cursor is _not_ on the QEMU window, the system doesn't
experience slowdowns. It's only when I move the mouse that everything seems to
slow down. For example, navigating the 'start' menu is very jerky in the VM but
works fine on bare metal... very strange.
My QEMU configuration:
/usr/local/bin/qemu-system-x86_64 \
-enable-kvm \
-cpu host \
-drive if=pflash,format=raw,unit=0,readonly=on,file=/usr/share/ovmf/OVMF.fd
\
-drive file=$image_file,if=virtio,format=raw \
-device virtio-net-pci,netdev=net0 \
-device virtio-rng-pci \
-device virtio-vga-gl \
-display gtk,gl=on \
-m 8G,maxmem=16G \
-machine q35,accel=kvm \
-netdev user,id=net0,hostfwd=tcp::-:22,"${PORT_FWDS}" \
-boot d \
-drive
file=/home/marc/Downloads/neon-user-20240523-1335.iso,media=cdrom,readonly=on \
-smp 2
QEMU version: 9.0.0
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 487905] Launching Elisa pinned icon fails with notification error
https://bugs.kde.org/show_bug.cgi?id=487905 --- Comment #7 from Marc --- Yes, it shows up as >dbus-:1.2-org.kde.elisa@0.service under applications in system monitor when launched from the task manager. And launched from the app launcher it shows as >Elisa same behavior with both '24.02.2-1' and '24.05.0-1'. But I discovered: You can launch multiple instances of 'elisa-24.05.0-1' when launched from the app launcher. You can't do this with the older version. I looked through the source code of both versions with meld (but I am no programmer, I must admit, so yeah) and I found some new code for 'KDbusService' in 'elisaapplication.cpp', seems to be one of the biggest changes between versions, could this be part of the problem? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487905] Launching Elisa via GUI method (KRunner, Kickoff, Task Manager) fails with DBus error
https://bugs.kde.org/show_bug.cgi?id=487905 --- Comment #14 from Marc --- Thanks for your work! I built elisa from source (now version 24.0.7.70). I uninstalled the pacman version made an menu entry in the app launcher and pinned the kdesrc-build to my task manager and it seems to work as it should. I can now close and relaunch it from there. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 392501] Volume slider in Elisa does not work
https://bugs.kde.org/show_bug.cgi?id=392501 Marc changed: What|Removed |Added CC||marc.schle...@gmx.de --- Comment #13 from Marc --- I noticed the same issue after upgrading to Plasma 6. KDE Frameworks 6.0.0 Qt 6.6.2 Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474725] Screen randomly freezes for a second
https://bugs.kde.org/show_bug.cgi?id=474725 --- Comment #16 from Marc --- For me the issue has almost disappeared somewhere at the end of december/beginning of january. The last two weeks the screen only very rarely froze. Maybe once every other day or so, whereas before it occurred very frequently. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481374] Graphics performance in QEMU/KVM guest with virGL is bad on Wayland
https://bugs.kde.org/show_bug.cgi?id=481374 Marc changed: What|Removed |Added CC||marc.ferl...@sonatest.com --- Comment #5 from Marc --- I'm seeing something very similar here. I just booted the neon-user-20240523-1335.iso ISO in QEMU (I'm running Ubuntu 22.04 as the host system). Simply moving the mouse around gives me these messages in the system journal (journalctl | grep libinput): May 23 18:55:55 neon kwin_wayland[1104]: kwin_libinput: Libinput: event2 - VirtualPS/2 VMware VMMouse: client bug: event processing lagging behind by 29ms, your system is too slow May 23 18:55:56 neon kwin_wayland[1104]: kwin_libinput: Libinput: event2 - VirtualPS/2 VMware VMMouse: client bug: event processing lagging behind by 78ms, your system is too slow May 23 18:56:01 neon kwin_wayland[1104]: kwin_libinput: Libinput: event2 - VirtualPS/2 VMware VMMouse: client bug: event processing lagging behind by 28ms, your system is too slow May 23 18:56:05 neon kwin_wayland[1104]: kwin_libinput: Libinput: event2 - VirtualPS/2 VMware VMMouse: client bug: event processing lagging behind by 32ms, your system is too slow May 23 18:56:38 neon kwin_wayland[1104]: kwin_libinput: Libinput: event2 - VirtualPS/2 VMware VMMouse: client bug: event processing lagging behind by 32ms, your system is too slow May 23 18:56:38 neon kwin_wayland[1104]: kwin_libinput: Libinput: event2 - VirtualPS/2 VMware VMMouse: WARNING: log rate limit exceeded (5 msgs per 60min). Discarding future messages. >From what I undertand, kwin_libinput isn't able to keep up (dispatch) events fast enough and so libinput complains. I also have this exact same behaviour on a custom image (yocto based) running plasma mobile. Another thing to try is `sudo evtest`, select the first mouse (VirtualPS/2 VMware Mouse) and look at the events. The faster the mouse moves the 'jerkier' it gets. CPU usage for the kwin_wayland process also goes up substantially (~12%). Note: doesn't happen when running on mutter, with the same QEMU setup. kinfo: Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-35-generic (64-bit) Graphics Platform: Wayland Processors: 2 × AMD Ryzen 9 7900 12-Core Processor Memory: 7.7 GiB of RAM Graphics Processor: virgl -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 453358] New: [Feature Request/ Idea] Fingerprint reader from smartphone using KDE Connect
https://bugs.kde.org/show_bug.cgi?id=453358 Bug ID: 453358 Summary: [Feature Request/ Idea] Fingerprint reader from smartphone using KDE Connect Product: kdeconnect Version: unspecified Platform: unspecified OS: Unspecified Status: REPORTED Severity: wishlist Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: marc_altm...@live.de Target Milestone: --- Hey guys, I hope this is the right place to share my idea. If not, please tell me. I know many users already had similar ideas (for example Bug 398931 and the duplicates), so many people want this feature. I hope now is the right time for this, because earlier no dev seriously reacted to this idea. Idea: My idea is to use the fingerprint reader of the smartphone (or other another device with supported fingerprint reader like an laptop) for authentication using KDE Connect. When you need to enter your password, KDE Connect on PC sends a request to KDE Connect on your Smartphone, KDE on Smartphone asks for authentication using fingerprint reader, if authenticated KDE Connect sends an time-based OTP to KDE Connect on PC. If it matches, KDE enters password or authenticates you. Why: PC users usually don't have a fingerprint reader and there are just a few laptops with it (and even less fingerprint readers are supported by libfprint). Always entering your password is stressful and you maybe use a shorter (and weaker) password instead. Use cases: 1. Maybe for login into your DE (this will probably not work after booting, but maybe it can be implemented when you are re-logging in after locking or suspending your session). 2. Maybe it is possible to integrate it in sudo/polkit so you don't have to always enter your password when using it. 3. Maybe it is possible to authenticate directly through KDE Connect using an API or something if other applications implement this feature. In general it is useful for programs where you need to enter your password multiple times (for example KeePassXC). I know that KeePassXC is working on supporting fingerprint sensors. However, libfprint supports just a few fingerprint sensors and just a few people even have one. Maybe KeePassXC can also implement polkit authentication or even directly the KDE Connect api. Let me here your thoughts on my idea! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 453358] [Feature Request/ Idea] Fingerprint reader from smartphone using KDE Connect
https://bugs.kde.org/show_bug.cgi?id=453358 --- Comment #1 from Marc --- Also see my related Reddit post: https://www.reddit.com/r/kde/comments/uhnjmg/feature_request_idea_use_fingerprint_reader_from/ It has quite some upvotes, comments and over 2.5k views. I think this is a feature a lot of people wish! KDE Connect is a great piece of software! Especially over the last month came a lot new features and stability was largely improved! I also want to mention the ideas of the Reddit-User u/Cyber_Daddy: """ i also have a few suggestions: virtual game controller using gyro and touch buttons or physical phone buttons passing location services to the host so you can run navigation software on a big screen theft alarm. if you are on the go(not home coordinates) you get notified if the connection is lost (could have exceptions if there is a shutdown due to scheduled standby or empty battery) remote side loading remote taskmanager (useful if you somehow can no longer interact with kde eg: app stealing focus and grabbing inputs or a frozen ui or cache thrashing) technically more challenging: audio/call/camera/screencap source and sink pass through in both directions tethering remote desktop in both directions for each running application individually and displaying them on the task switcher on kde and app switcher on the phone respectively. usb pass through in both directions """ Maybe some of them are harder to implement, but maybe KDE Connect can make a roadmap and add some of these suggestions! I think these are the ideas that can make KDE Connect even better. Thank you very much. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 453519] New: Horizontal lines with fractional HiDPI scaling (regression) under Wayland
https://bugs.kde.org/show_bug.cgi?id=453519 Bug ID: 453519 Summary: Horizontal lines with fractional HiDPI scaling (regression) under Wayland Product: konsole Version: 21.12.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: marc_sm...@gmx.com Target Milestone: --- STEPS TO REPRODUCE 1. set scaling [with FullHD 1920x1080] to 115% via Display Manager, font DPI 96, WAYLAND 2. run Konsole and k9s or htop 3. move cursor keys up and down until artifacts [lines] appear in random places OBSERVED RESULT artifacts / lines in random places on Konsole screen EXPECTED RESULT normal view without any artifacts SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro/Plasma 5.24.4 (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Wayland. This bug is the same and exact as the one reported in the past - example: https://bugs.kde.org/show_bug.cgi?id=373232 Can't attach screenshot, as artifacts disappear once I try to create a screenshot of them. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 442319] New: Closing Amarok with playback volume set at 100% and then reopening has volume set at 0%
https://bugs.kde.org/show_bug.cgi?id=442319 Bug ID: 442319 Summary: Closing Amarok with playback volume set at 100% and then reopening has volume set at 0% Product: amarok Version: 2.9.71 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Playback Assignee: amarok-bugs-d...@kde.org Reporter: marcerick...@gmail.com Target Milestone: kf5 SUMMARY marcerick...@gmail.com Closing Amarok with playback volume set at 100% and then reopening has volume set at 0% STEPS TO REPRODUCE 1. Set playback volume at 100% 2. Exit Amarok 3. Open Amarok OBSERVED RESULT Playback volume is at 0% EXPECTED RESULT Playback volume is at 100% SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) Ubuntu 18.04.5 LTS Sever with xfce GUI KDE Plasma Version: Unknown KDE Frameworks Version: Unknown Qt Version: Unknown ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444410] New: Systemsetting break rendering under Wayland
https://bugs.kde.org/show_bug.cgi?id=10 Bug ID: 10 Summary: Systemsetting break rendering under Wayland Product: systemsettings Version: 5.23.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: marc.schle...@gmx.de Target Milestone: --- Created attachment 142895 --> https://bugs.kde.org/attachment.cgi?id=142895&action=edit Screenshot with broken rendering under Wayland SUMMARY Clicking an item in the system settings under a Wayland session inverts the rendering to upside down. STEPS TO REPRODUCE 1. Start Wayland Session 2. Open System Settings 3. Click an Icon OBSERVED RESULT Window contents (overview) get rendered upside down instead of navigating to the desired submenu. UI stops working all together. Clicking a setting in the inverted rendering doesnt do anything. EXPECTED RESULT Navigate to submenu and render correct SOFTWARE/OS VERSIONS Linux/KDE Plasma: Opensuse Tumbleweed KDE Plasma Version: 5.23 KDE Frameworks Version: 5.86 Qt Version: 5.15.2 ADDITIONAL INFORMATION NVidia GPU with Nvidia drivers -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 456746] New: Dolphin don't use fqdn for sharing smb network
https://bugs.kde.org/show_bug.cgi?id=456746 Bug ID: 456746 Summary: Dolphin don't use fqdn for sharing smb network Product: dolphin Version: 22.04.3 Platform: Debian unstable OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: m...@gallifrey-blr.fr CC: kfm-de...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** I have a home workgroup called Atlantis. The fqdn for my destop is : marc@Midgard:~$ hostname --fqdn Midgard.Atlantis The fqdn for my server is : marc@gallifrey:~$ hostname --fqdn gallifrey.Atlantis STEPS TO REPRODUCE 1. In the left panel of Dolphin click on "network" 2. Click on Shared Folder (SMB) 3. It show me all shared machine on my network (eg : Gallifrey, Kodi and Midgard) 4. Click on Gallifrey OBSERVED RESULT After step 4 Dolphin try to connect on gallifrey.local instead off gallifrey and an error message "Impossible to connect" If I enter smb://gallifrey in the address bar, that work. If I enter smb://gallifrey.atlantis no error message appears, but dolphin can't show any shared folder. EXPECTED RESULT Dolphin should search gallifrey.Atlantis instead of gallifrey.local and show shared folder SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Debian SID (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION Kernel : 5.18 Graphic : X11 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 456746] Dolphin don't use fqdn for sharing smb network
https://bugs.kde.org/show_bug.cgi?id=456746
--- Comment #2 from marc ---
Hi Harald,
"How did you set up your domain?"
On my desktop :
marc@Midgard:~$ cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 Midgard.AtlantisMidgard
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
marc@Midgard:~$ cat /etc/samba/smb.conf
# Sample configuration file for the Samba suite for Debian GNU/Linux.
[...]
[global]
## Browsing/Identification ###
# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = Atlantis
[...]
On my server :
marc@gallifrey:~$ cat /etc/hosts
127.0.0.1 localhost
127.0.0.1 gallifrey.Atlantis Gallifrey
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
marc@gallifrey:~$ cat /etc/samba/smb.conf
# Sample configuration file for the Samba suite for Debian GNU/Linux.
[...]
[global]
## Browsing/Identification ###
# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = Atlantis
[...]
The rest of the smb.conf are the default file from the Debian installation.
marc@Midgard:~$ export KDE_FORK_SLAVES=1
marc@Midgard:~$ export QT_MESSAGE_PATTERN='[%{time
process}](%{pid})/(%{category}) %{function}: %{message}'
marc@Midgard:~$ export QT_LOGGING_RULES='log_kio_smb=true'
marc@Midgard:~$ dolphin --new-window smb://gallifrey.local
[ 0.000](28419)/(kf.kio.core) unknown: "Impossible de se connecter à l'hôte
« smb://gallifrey.local/ »"
marc@Midgard:~$ dolphin --new-window smb://gallifrey.atlantis
marc@Midgard:~$ dolphin --new-window smb://gallifrey
dolphin --new-window smb://gallifrey.atlantis -> No error with this command,
but no shared folder found
dolphin --new-window smb://gallifrey -> Work perfectly
dolphin --new-window smb://gallifrey.local -> this is the folder, that dolphin
want to explore on the GUI by clicking on the network icon
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 456746] Dolphin don't use fqdn for sharing smb network
https://bugs.kde.org/show_bug.cgi?id=456746 --- Comment #3 from marc --- Created attachment 150648 --> https://bugs.kde.org/attachment.cgi?id=150648&action=edit First screenshoot -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 456746] Dolphin don't use fqdn for sharing smb network
https://bugs.kde.org/show_bug.cgi?id=456746 --- Comment #4 from marc --- Created attachment 150649 --> https://bugs.kde.org/attachment.cgi?id=150649&action=edit Second Screenshot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455999] Plasmashell suddenly starts eating up all the CPU
https://bugs.kde.org/show_bug.cgi?id=455999 Marc changed: What|Removed |Added CC||marc.schle...@gmx.de --- Comment #3 from Marc --- I am seeing this issue as well on a complete fresh install of OpenSuse Tumbleweed with KDE 5.25.1 (though home-directory was from previous installation). Will have a look how this evolves and try to provide some feedback. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455999] Plasmashell suddenly starts eating up all the CPU
https://bugs.kde.org/show_bug.cgi?id=455999 --- Comment #4 from Marc --- Did some more testing: it looks like any animation is causing the issue. I had two widgets in use (cpu- and network-usage). Removing both removes the load, adding one raises half again, adding the second the high load behaviour is back. I might add that due to a bug in the Nvidia driver for Opensuse, I currently have to run Nouveau. Maybe the issue is there. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 441281] New: Cannot start kdenlive because preview cannot be loaded.
https://bugs.kde.org/show_bug.cgi?id=441281
Bug ID: 441281
Summary: Cannot start kdenlive because preview cannot be
loaded.
Product: kdenlive
Version: 21.08.0
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Installation
Assignee: vpi...@kde.org
Reporter: marc.schle...@gmx.de
Target Milestone: ---
Created attachment 140906
--> https://bugs.kde.org/attachment.cgi?id=140906&action=edit
Crash-Report from KDE
For some reason I could not send the error with the crash-reporter, I am doing
it manually. Following is the content from the kcrash file.
Application: kdenlive (21.08.0)
Qt Version: 5.15.2
Frameworks Version: 5.85.0
Operating System: Linux 5.13.8-1-default x86_64
Windowing System: X11
Drkonqi Version: 5.22.4
Distribution: "openSUSE Tumbleweed"
-- Information about the crash:
- What I was doing when the application crashed: just start the application on
a fresh openSuse Tumbleweed installation
The application shows an error stating that the preview window cannot be
loaded, but no real cause is given. It is mentioning that it could be a driver
issue...I am running the NVIDIA driver.
The crash can be reproduced every time.
-- Backtrace:
Application: Kdenlive (kdenlive), signal: Segmentation fault
Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fe568ca7980
(LWP 5216))]
[KCrash Handler]
#6 0x7fe56cfe69ad in Mlt::Properties::set (this=0x0, name=0x562592df3059
"scrub_audio", value=0) at
/usr/src/debug/libmlt-7.0.1-2.1.x86_64/src/mlt++/MltProperties.cpp:178
#7 0x562592a8d653 in GLWidget::setProducer (this=0x562596a4f6b0,
producer=..., isActive=, position=) at
/usr/include/c++/11/bits/shared_ptr_base.h:1295
#8 0x562592ca11db in Monitor::setProducer (pos=0,
producer=std::shared_ptr (use count 2, weak count 0) = {...},
this=0x56259690d190) at
/usr/src/debug/kdenlive-21.08.0-1.1.x86_64/src/monitor/monitor.cpp:2392
#9 ProjectManager::updateTimeline(int, int) [clone .constprop.0]
(this=this@entry=0x5625949bec40, pos=pos@entry=0, scrollPos=-1) at
/usr/src/debug/kdenlive-21.08.0-1.1.x86_64/src/project/projectmanager.cpp:982
#10 0x562592ae719f in ProjectManager::newFile (this=0x5625949bec40,
profileName=..., showProjectSettings=) at
/usr/src/debug/kdenlive-21.08.0-1.1.x86_64/src/project/projectmanager.cpp:228
#11 0x562592ae76bf in ProjectManager::newFile (this=0x5625949bec40,
showProjectSettings=) at
/usr/src/debug/kdenlive-21.08.0-1.1.x86_64/src/project/projectmanager.cpp:139
#12 0x5625928b280d in ProjectManager::slotLoadOnOpen (this=0x5625949bec40)
at
/usr/src/debug/kdenlive-21.08.0-1.1.x86_64/src/project/projectmanager.cpp:109
#13 ProjectManager::qt_static_metacall (_o=0x5625949bec40, _id=,
_a=0x5625949dd108, _c=) at
/usr/src/debug/kdenlive-21.08.0-1.1.x86_64/build/src/kdenliveLib_autogen/QV7S676PVK/moc_projectmanager.cpp:223
#14 0x7fe56b678f5e in QObject::event (this=0x5625949bec40,
e=0x5625949dd0c0) at kernel/qobject.cpp:1314
#15 0x7fe56c897a7f in QApplicationPrivate::notify_helper (this=, receiver=0x5625949bec40, e=0x5625949dd0c0) at
kernel/qapplication.cpp:3632
#16 0x7fe56b64c96a in QCoreApplication::notifyInternal2
(receiver=0x5625949bec40, event=0x5625949dd0c0) at
kernel/qcoreapplication.cpp:1064
#17 0x7fe56b64f9b7 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x5625942870d0) at
kernel/qcoreapplication.cpp:1821
#18 0x7fe56b6a47d3 in postEventSourceDispatch (s=s@entry=0x56259438f760) at
kernel/qeventdispatcher_glib.cpp:277
#19 0x7fe56969880f in g_main_dispatch (context=0x7fe560005000) at
../glib/gmain.c:3337
#20 g_main_context_dispatch (context=0x7fe560005000) at ../glib/gmain.c:4055
#21 0x7fe569698b98 in g_main_context_iterate
(context=context@entry=0x7fe560005000, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4131
#22 0x7fe569698c4f in g_main_context_iteration (context=0x7fe560005000,
may_block=1) at ../glib/gmain.c:4196
#23 0x7fe56b6a3e54 in QEventDispatcherGlib::processEvents
(this=0x56259439c090, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#24 0x7fe56b64b36b in QEventLoop::exec (this=this@entry=0x7ffd1d298c60,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#25 0x7fe56b653650 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#26 0x7fe56c1391dc in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1867
#27 0x7fe56c8979f5 in QApplication::exec () at kernel/qapplication.cpp:2824
#28 0x5625928499eb in main (argc=, argv=0x7ffd1d299008) at
/usr/src/debug/kdenlive-21.08.0-1.1.x86_64/src/main.cpp:278
[Inferior 1 (process 5216) detached]
Possible duplicates by query: bug 430295, bug 430183, bug 419604, bug 419603.
An htt
[digikam] [Bug 440156] New: Cant get Google Import/export to authenticate with Google on Mint 20.2 Cinnamon
https://bugs.kde.org/show_bug.cgi?id=440156 Bug ID: 440156 Summary: Cant get Google Import/export to authenticate with Google on Mint 20.2 Cinnamon Product: digikam Version: 7.3.0 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plugin-WebService-Google Assignee: digikam-bugs-n...@kde.org Reporter: anon.smith+...@gmail.com Target Milestone: --- SUMMARY Cant get Google import/export to authenticate/work on Mint 20.2 Cinnamon I'm quite sure I got this to work on an older weekly 7.3.x snapshot STEPS TO REPRODUCE 1. install fresh mint 20.2 cinnamon 2. download 7.3.0 appimage, make executable 3. start, digikam, download face data 4. restart digikam, click on google import or export 5. import dialog comes up, no name, click on "Change Account", get warning of you will be logged off 6. continue (and nothing happens) Tried on multiple computers, multiple installations, also tried on 20.1 Cinnamon, that works. Also tried on 20.1 xfce, it does now work here, either. Although this seems to be a Mint issue, I'm having a hard time pinpointing what to report / do in able to fix this. Can you help? OBSERVED RESULT import dialog comes up, no authenticated user EXPECTED RESULT browser to come up with authentication to Google SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424952] ERR_CERT_AUTHORITY_INVALID on accessing many component from within digikam
https://bugs.kde.org/show_bug.cgi?id=424952 marc changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from marc --- just wanted to confirm this issue is not present on current 7.3.0/Mint 20.2 anymore -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440156] Cant get Google Import/export to authenticate with Google on Mint 20.2 Cinnamon
https://bugs.kde.org/show_bug.cgi?id=440156 --- Comment #1 from marc --- Created attachment 140338 --> https://bugs.kde.org/attachment.cgi?id=140338&action=edit tracefile -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424952] New: ERR_CERT_AUTHORITY_INVALID on accessing many component from within digikam
https://bugs.kde.org/show_bug.cgi?id=424952 Bug ID: 424952 Summary: ERR_CERT_AUTHORITY_INVALID on accessing many component from within digikam Product: digikam Version: 7.0.0 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Documentation Assignee: digikam-bugs-n...@kde.org Reporter: anon.smith+...@gmail.com Target Milestone: --- SUMMARY both on freshly installed linux mint 20 cinnamon, and on two frequently used mint 19.3 xfce when accessing ie. help/documentation, or export plugins or import plugins, they can not connect to internet adresses due to ERR_CERT_AUTHORITY_INVALID hence do not work. Accessing the internet adresses with browser outside of digikam works perfectly fine STEPS TO REPRODUCE 1. run digikam-7.0.0-x86-64.appimage 2. open Help menu 3. select Online Handbook... OBSERVED RESULT This site can’t be reachedThe webpage at https://docs.kde.org/?application=digikam might be temporarily down or it may have moved permanently to a new web address. ERR_CERT_AUTHORITY_INVALID EXPECTED RESULT accessing html normally on kde.org SOFTWARE/OS VERSIONS Windows: (testet on Windows 10 2004, no problem there) Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: 5.14.2 ADDITIONAL INFORMATION Tried to install digikam through normal repository in the hopes that any dependencies might be resolved. tried to install and change default browser to chrome. Note also: fixed with same way as bug ID 417008, just wanted to post this anyway so any possible updates to install notes could be filed? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474725] Screen randomly freezes for a second
https://bugs.kde.org/show_bug.cgi?id=474725 Marc changed: What|Removed |Added Ever confirmed|0 |1 Platform|Other |Archlinux CC||e...@hotmail.de Version|master |5.27.8 Status|REPORTED|CONFIRMED --- Comment #9 from Marc --- On my latop a Lenovo ThinkPad X1 Carbon Gen 10 this is a huge problem. These stutters occur every couple of minutes, sometimes even multiple times per minute and the complete system hangs for some 100ms or sometimes some seconds. When the stutter occurs it is often the case that the keypress is repeated tens to hundred of times. So I type, the stutter occurs and my input looks like this. It's beyond annoying and makes the laptop hardly usable on the STABLE KDE VERSION 5.27.8. So this is definitely not only a master issue for Plasma 6. So it's also affecting Qt5 (5.15.11 in my case). To me it seems like an issue in the graphics stack. Either the Intel driver itself or Qt. I have an Intel i7-1265U with Intel Graphics. I assume this issue is much more common than this bug reports suggests so far. I wasn't sure where the stutter comes from and didn't know where to report the bug to until I stumbled on this report. Maybe Arch users are particularly affected because they typically use the most up to date packages and kernels. So it could indeed be a regression in some area of the software stack. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449385] New: Systemsettings can't save changes for user
https://bugs.kde.org/show_bug.cgi?id=449385 Bug ID: 449385 Summary: Systemsettings can't save changes for user Product: systemsettings Version: 5.23.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_users Assignee: plasma-b...@kde.org Reporter: marc_altm...@live.de CC: uhh...@gmail.com Target Milestone: --- SUMMARY I am trying to change my avatar or email address in systemsettings --> users. For my avatar picture, I've tried a picture from my phone (.jpg) and also the standard avatars that are available. When I click apply the message "Could not get permission to save user xxx". I think this is the same message that appears, when I click cancel in the PolicyKit1 window, but the window doesn't open. When I try to change my sddm theme in systemsettings --> Startup and Shutdown --> Login Screen (SDDM) the PolicyKit1 window does show up and I can enter my password and everything just works fine. STEPS TO REPRODUCE 1. Open systemsettings --> users 2. Select different avatar or enter an email adrees 3. Click apply OBSERVED RESULT Error message "Could not get permission to save user xxx". EXPECTED RESULT PolicyKit1 window opens, I insert my password, no error message and avatar or email are set. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux; Kernel: 5.16.3-arch1-1 (64bit) (available in About System) KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I installed Arch freshly on this device where the bug happens so it never worked on this system (I already tried reinstalling all packages and I already reinstalled my system). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449385] Systemsettings can't save changes for user
https://bugs.kde.org/show_bug.cgi?id=449385 --- Comment #1 from Marc --- I have another laptop with Arch and KDE installed (pretty much the same setup on the laptop that has the bug), but the system on this one is not freshly installed. I tried changing my avatar or email and it worked. Afterwards I updated my system (using pacman) and it doens't work anymore. So this bug seems to be in a current version of the systemsettings or it's dependencies. (Unfortunately I didn't update this laptop very recently, because I just use it sometimes, so maybe this bug is a little bit older). I don't know how I can provide useful information for solving this problem, but I would like to help! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434385] New: Taskbar freezes regularly when Compositor is set to XRender
https://bugs.kde.org/show_bug.cgi?id=434385 Bug ID: 434385 Summary: Taskbar freezes regularly when Compositor is set to XRender Product: plasmashell Version: 5.21.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: e...@hotmail.de CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When the compositor is set to XRender, the taskbar freezes regularly and the system becomes unusable because of that. I have to reboot or restart the plasmashell to get it back working. The bug occurs after some time of usage. Sometimes after a couple of minutes, sometimes after a few hours. But it occurs multiple times a day and made me switch to Gnome for a while (I had this bug for at least year). While searching in forums, I found quite a number of people having a freezing taskbar problem. Only recently I noticed that this is dependent on the compositor backend. There is another bug report which mentions the compositor backends, but for me it's exactly the other way around as in Bug 425557. Both OpenGL backends do not seem to trigger the bug on my system (ThinkPad with Intel Graphics) I need to use XRender though because of another bug. Screencasts or TeamViewer/Anydesk sessions with the OpenGL backends result in flickering, where the desktop background behind a window appears in some frames. STEPS TO REPRODUCE 1. Just run plasma with XRender backend and work till the taskbar freezes OBSERVED RESULT The taskbar freezes completely and cannot be unfrozen. I need to restart the plasmashell. EXPECTED RESULT Not freezing ;-) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.21.1 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 279594] JUK copies actual meta tag when clicking new song to that song
https://bugs.kde.org/show_bug.cgi?id=279594 Marc changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #14 from Marc --- later versions do no longer show this behavior. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434385] Taskbar freezes regularly when Compositor is set to XRender
https://bugs.kde.org/show_bug.cgi?id=434385 --- Comment #2 from Marc --- No, the plasma shell seems to be completely frozen. No context menu and no krunner. But curiously KWin seems to still work fine. So I can continue working with existing application windows and even use ALT-Tab. That's why I often realize that Plasma is frozen after a couple of minutes. I have tried to track the issue down, but I was not able to find anything obvious in the logs. Thank you very much for looking into the issue. Get Outlook for Android<https://aka.ms/AAb9ysg> From: David Edmundson Sent: Sunday, March 14, 2021 1:53:57 PM To: e...@hotmail.de Subject: [plasmashell] [Bug 434385] Taskbar freezes regularly when Compositor is set to XRender https://bugs.kde.org/show_bug.cgi?id=434385 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from David Edmundson --- When frozen can you right click on the dekstop and get a context menu? -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasma-mobile] [Bug 492884] New: Missing sddm greeter theme
https://bugs.kde.org/show_bug.cgi?id=492884 Bug ID: 492884 Summary: Missing sddm greeter theme Classification: Plasma Product: plasma-mobile Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-mobile-bugs-n...@kde.org Reporter: marc.ferl...@sonatest.com CC: c...@carlschwan.eu Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY Commit 5b401d9e1c026f97da12bc8b60c89f90c9162492 in plasma-workspace removed the sddm theme (now only in plasma-desktop). This makes plasma-mobile fallback to the default embedded theme. When logging out of plasma-mobile, I now get: sddm[1731]: The configured theme "breeze" doesn't exist, using the embedded theme instead See: https://github.com/KDE/plasma-workspace/commit/5b401d9e1c026f97da12bc8b60c89f90c9162492 STEPS TO REPRODUCE 1. Login to plasma-mobile 2. Shutodwn --> logout OBSERVED RESULT The greeter theme is now the default embedded theme EXPECTED RESULT I would expect the 'breeze' theme when login out of plasma-mobile. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5 Qt Version: 6.7.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480779] Can not add Google to Online Accounts anymore
https://bugs.kde.org/show_bug.cgi?id=480779 Marc changed: What|Removed |Added CC||darkstar...@gmail.com --- Comment #17 from Marc --- (In reply to gabriel.rilling from comment #15) > (In reply to Szczepan Hołyszewski from comment #13) > > I just tripped on this, and here's a workaround that worked for me, combined > > from an earlier workaround posted in #485286 and my own experimentation: > > > > 1. I maximized the embedded browser window that displays the authentication > > page > > 2. I switched the language to Polish (my language) > > 3. As per the original workaround (which was insufficient on its own in my > > case), I clicked Next with mouse instead of using Enter > > > > No further problems encountered. > > This worked for me too, although I did not change the language. I've tried this a few times on two separate systems, I don't speak polish and even tried that part specifically but unable to reproduce today. All items give an error indicating that there is an issue with the browser used for sign or the app setup to allow sign-in. -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 485286] Online accounts (kio-gdrive) "Couldn’t sign you in". [SOLUTION]: Enter credentials with the keyboard and validate with the mouse
https://bugs.kde.org/show_bug.cgi?id=485286 Marc changed: What|Removed |Added CC||darkstar...@gmail.com --- Comment #3 from Marc --- (In reply to Szczepan Hołyszewski from comment #2) > This workaround alone didn't work for me, but here is exactly what I did, > and it worked: > > 1. I maximized the embedded browser window that displays the authentication > page > 2. I switched the language to Polish (my native language) > 3. I used mouse to click on the buttons, as per the workaround I tried this and was unable to reproduce. Tried multiple languages to verify and two separate devices. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 490584] kwallet GPG error was No secret key
https://bugs.kde.org/show_bug.cgi?id=490584 Marc changed: What|Removed |Added CC||marc.schle...@gmx.de --- Comment #2 from Marc --- I can confirm this behaviour. I've seen this a couple of weeks ago, but after a reboot the issue was gone. As of today on Suse Tumbleweed Snapshot 13.09.2024, I cannot open my Wallet. Looking into Kleopatra, there is no key. So I backup the key from my other machine and imported it again and after a successful import Kleopatra still shows NO certificates/keys. There seems to be something completely off with the backend. If I can provide more information, please let me know how. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 490584] kwallet GPG error was No secret key
https://bugs.kde.org/show_bug.cgi?id=490584 --- Comment #3 from Marc --- One more observation. When I try to create a new key using Kleopatra I receive the error "SQL library used wrong" during (or after) the curve generation. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 490584] kwallet GPG error was No secret key
https://bugs.kde.org/show_bug.cgi?id=490584 --- Comment #4 from Marc --- Running "gpg -k" showed that a lock is held by some process. After killing this one (forgot to check which one it was) KWallet started working again. After a reboot Kleopatra also showed all keys again. Maybe the error-handling should be improved to tell the user that something is blocking access. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 490584] kwallet GPG error was No secret key
https://bugs.kde.org/show_bug.cgi?id=490584 --- Comment #5 from Marc --- (In reply to Marc from comment #4) > Running "gpg -k" showed that a lock is held by some process. After killing > this one (forgot to check which one it was) KWallet started working again. > After a reboot Kleopatra also showed all keys again. > > Maybe the error-handling should be improved to tell the user that something > is blocking access. It happened again today. The process blocking is gvfsd-fuse. -- You are receiving this mail because: You are watching all bug changes.
[krecorder] [Bug 492649] New: A big white box is displayed when using the app on an HD display
https://bugs.kde.org/show_bug.cgi?id=492649 Bug ID: 492649 Summary: A big white box is displayed when using the app on an HD display Classification: Applications Product: krecorder Version: 24.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: espi...@gmail.com Reporter: marc.ferl...@sonatest.com Target Milestone: --- Created attachment 173320 --> https://bugs.kde.org/attachment.cgi?id=173320&action=edit Screenshot SUMMARY When using Krecorder on a HD screen, a big white box is displayed. See the attached screenshot. STEPS TO REPRODUCE 1. Opening the app on a display with HD resolution 2. 3. OBSERVED RESULT EXPECTED RESULT Krecorder should support HD displays. SOFTWARE/OS VERSIONS Linux: 6.1.68 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-mobile-settings] [Bug 492650] New: Sound profile drop down is broken
https://bugs.kde.org/show_bug.cgi?id=492650 Bug ID: 492650 Summary: Sound profile drop down is broken Classification: Applications Product: plasma-mobile-settings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: espi...@gmail.com Reporter: marc.ferl...@sonatest.com Target Milestone: --- Created attachment 173321 --> https://bugs.kde.org/attachment.cgi?id=173321&action=edit Sound profiles drop down SUMMARY When trying to list the available sound profiles, the displayed list is broken. See attached screenshot. STEPS TO REPRODUCE 1. Open the Settings app 2. Open the sound settings 3. Click on the sound profile drop down list OBSERVED RESULT The list is not correctly displayed. No profiles is shown. EXPECTED RESULT The full list of profiles is shown. This list should be the same as the one shown from the quick drawer settings. See attached screen shot. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.1.68 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-mobile-settings] [Bug 492650] Sound profile drop down is broken
https://bugs.kde.org/show_bug.cgi?id=492650 --- Comment #1 from Marc --- Created attachment 173322 --> https://bugs.kde.org/attachment.cgi?id=173322&action=edit Sound profiles from the quick drawer The list of profiles from the quick drawer is shown correctly. -- You are receiving this mail because: You are watching all bug changes.
[KClock] [Bug 492652] New: Broken application layout when adding a new timer
https://bugs.kde.org/show_bug.cgi?id=492652 Bug ID: 492652 Summary: Broken application layout when adding a new timer Classification: Applications Product: KClock Version: 24.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: espi...@gmail.com Reporter: marc.ferl...@sonatest.com CC: hanyo...@protonmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY The layout used when adding a new timer in KClock is broken (see attached screenshot). Note that I am using a resolution of 1920x1080. STEPS TO REPRODUCE 1. Open the KClock application 2. Click "New timer" OBSERVED RESULT It is as if the layout is shifted to the left. EXPECTED RESULT I would expect the same behavior as when we click on "Add Alarm". SOFTWARE/OS VERSIONS Linux: 6.1.68 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.3 -- You are receiving this mail because: You are watching all bug changes.
[KClock] [Bug 492652] Broken application layout when adding a new timer
https://bugs.kde.org/show_bug.cgi?id=492652 --- Comment #1 from Marc --- Created attachment 173323 --> https://bugs.kde.org/attachment.cgi?id=173323&action=edit New timer screenshot -- You are receiving this mail because: You are watching all bug changes.
[kirigami-addons] [Bug 490502] New: KStandardAction vs KStandardActions
https://bugs.kde.org/show_bug.cgi?id=490502 Bug ID: 490502 Summary: KStandardAction vs KStandardActions Classification: Frameworks and Libraries Product: kirigami-addons Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: marc.ferl...@sonatest.com CC: c...@carlschwan.eu Target Milestone: --- Trying to compile version 1.4.0 of kirigami-addons using KF6 v6.2.0 fails with: git/src/statefulapplication/kirigamiactioncollection.h:18:10: fatal error: KStandardActions: No such file or directory I think the correct include name is "KStandardAction" and not "KStandardActions" (note the 'S'). The exact revision I am using is: ea800d58f3ddc1ead8b1395a9f03e47f18efed7b Note: I got this error while upgrading the yocto recipe: https://github.com/KDE/yocto-meta-kde/blob/master/recipes-playground/kirigami-addons.inc Any help appreciated! -- You are receiving this mail because: You are watching all bug changes.
[kirigami-addons] [Bug 490502] KStandardAction vs KStandardActions
https://bugs.kde.org/show_bug.cgi?id=490502 --- Comment #1 from Marc --- Created attachment 171788 --> https://bugs.kde.org/attachment.cgi?id=171788&action=edit Configure log -- You are receiving this mail because: You are watching all bug changes.
[kirigami-addons] [Bug 490502] KStandardAction vs KStandardActions
https://bugs.kde.org/show_bug.cgi?id=490502 --- Comment #2 from Marc --- Created attachment 171790 --> https://bugs.kde.org/attachment.cgi?id=171790&action=edit Compile log -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404274] Windows not displayed
https://bugs.kde.org/show_bug.cgi?id=404274 --- Comment #15 from Marc --- started yesterday mpv and the windows was not displayed, i was able to heard the sound. restarted mpv and now i was able to see the software. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 410653] New: Enter Key for Keyboard Navigation in File Dialogs
https://bugs.kde.org/show_bug.cgi?id=410653 Bug ID: 410653 Summary: Enter Key for Keyboard Navigation in File Dialogs Product: frameworks-kio Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Open/save dialogs Assignee: fa...@kde.org Reporter: e...@hotmail.de CC: kdelibs-b...@kde.org Target Milestone: --- Pressing ENTER on a selected folder in a save dialog does not open the corresponding folder any more, but instead confirms current selection and closes the dialog. This is a major bug for all keyboard users (am I the only one?). STEPS TO REPRODUCE 1. Try to save a file e.g. in the web browser 2. Select a folder in the file dialog 3. Press ENTER OBSERVED RESULT Dialog is closed EXPECTED RESULT Dialog should switch to the selected folder SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.60.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION This bug exists for quite some time now -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422116] New: Access to Power Management Settings causes crash
https://bugs.kde.org/show_bug.cgi?id=422116 Bug ID: 422116 Summary: Access to Power Management Settings causes crash Product: systemsettings Version: 5.17.5 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: marc_fel...@yahoo.com Target Milestone: --- Application: systemsettings5 (5.17.5) Qt Version: 5.12.5 Frameworks Version: 5.62.0 Operating System: Linux 5.5.0-1parrot1-amd64 x86_64 Distribution: Parrot GNU/Linux 4.9 -- Information about the crash: - What I was doing when the application crashed: I was trying to access the Power Management settings and kept getting the following error : "Power Management service is not running, it cas be fixed from Startup and Shutdown settings". For some reason... crash of the application. After some research, I found out the script responsible for the launch of such service is found in the following file "/etc/xdg/autostart/powerdevil.desktop" declared in the "Exec" key. This key contained the following path : "/usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil". So in the "Startup and Shutdown" settings I added a the script so it would be executed on startup, I rebooted the system and tried to access the Power Management settings and got the same error then the application crashed. I really want to stop my screen from dimming after 5 minutes :(Please help... ! - Custom settings of the application: Application running on Linux parrot 5.5.0-1parrot1-amd64 #1 SMP Parrot 5.5.17-1parrot1 (2020-04-25) x86_64 GNU/Linux - Usefull link : https://bugzilla.redhat.com/show_bug.cgi?id=1584227 The crash can be reproduced every 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 0x7fabc4db3800 (LWP 1605))] Thread 13 (Thread 0x7fab5700 (LWP 1641)): #0 0x7fabc7be75e5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7fabc955e78f in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fabc955e879 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fabc8896f9a in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #4 0x7fabc88573bf in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #5 0x7fabc88594dc in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7fabc885a33d in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fabc885a4be in QQmlImports::addLibraryImport(QQmlImportDatabase*, QString const&, QString const&, int, int, QString const&, QString const&, bool, QList*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7fabc882416c in QQmlTypeLoader::Blob::addImport(QV4::CompiledData::Import const*, QList*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7fabc882586d in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7fabc88277cf in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #11 0x7fabc882043e in QQmlTypeLoader::setData(QQmlDataBlob*, QQmlDataBlob::SourceCodeData const&) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #12 0x7fabc8820d49 in QQmlTypeLoader::setData(QQmlDataBlob*, QString const&) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #13 0x7fabc8820e79 in QQmlTypeLoader::loadThread(QQmlDataBlob*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #14 0x7fabc882107d in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #15 0x7fabc8896b78 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #16 0x7fabc8897242 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #17 0x7fabca1adc32 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7fabca1b7190 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7fabc9717a52 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7fabc971a648 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7fabc976e183 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7fabc713a60d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7fabc713a890 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7fabc713a91f in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7fabc976d7c1 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7fabc97166db in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7fabc95576f1 in QThread::exec() () from /lib/x86_64-linux-
[OCS] [Bug 415899] New: Can't load a save file even with kde as saved file
https://bugs.kde.org/show_bug.cgi?id=415899 Bug ID: 415899 Summary: Can't load a save file even with kde as saved file Product: OCS Version: unspecified Platform: MS Windows OS: MS Windows Status: REPORTED Severity: crash Priority: NOR Component: General Assignee: lei...@leinir.dk Reporter: 2000toybon...@gmail.com Target Milestone: --- SESSION: 05 Jan 2020 01:44:13 -0700. Executing C:\Program Files\Krita (x64)\bin\krita.exe C:\Users\terla\OneDrive\Pictures\drawings\song cover.kra WARNING: This file contains information about your system and the images you have been working with. If you have problems with Krita, the Krita developers might ask you to share this file with them. The information in this file is not shared automatically with the Krita developers in any way. You can disable logging to this file in Krita's Configure Krita Dialog. Please review the contents of this file before sharing this file with anyone. Krita Version: 4.2.1 Languages: en_US Hidpi: true Qt Version (compiled): 5.12.3 Version (loaded): 5.12.3 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.18362 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 05 Jan 2020 01:44:21 -0700: Importing application/x-krita to application/x-krita. Location: C:/Users/terla/OneDrive/Pictures/drawings/song cover.kra. Real location: C:/Users/terla/OneDrive/Pictures/drawings/song cover.kra. Batchmode: 0 Hardware Information GPU Acceleration: auto Memory: 8124 Mb Number of Cores: 4 Swap Location: C:/Users/terla/AppData/Local/Temp 05 Jan 2020 01:44:24 -0700: Closing. OpenGL Info Vendor: "Google Inc." Renderer: "ANGLE (Intel(R) HD Graphics 4600 Direct3D11 vs_5_0 ps_5_0)" Version: "OpenGL ES 3.0 (ANGLE 2.1.0.57ea533f79a7)" Shading language: "OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0.57ea533f79a7)" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 3.0, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Version: 3.0 Supports deprecated functions false is OpenGL ES: true QPA OpenGL Detection Info supportsDesktopGL: true supportsAngleD3D11: true isQtPreferAngle: true == log == Supported renderers: QFlags(0x2|0x4) Surface format preference list: * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) QSurfaceFormat::OpenGLES * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) QSurfaceFormat::OpenGL * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 16, greenBufferSize 16, blueBufferSize 16, alphaBufferSize 16, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::scRGBColorSpace, profile QSurfaceFormat::CompatibilityProfile) QSurfaceFormat::OpenGLES * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 10, greenBufferSize 10, blueBufferSize 10, alphaBufferSize 2, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::bt2020PQColorSpace, profile QSurfaceFormat::CompatibilityProfile) QSurfaceFormat::OpenGLES * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 16, greenBufferSize 16, blueBufferSize 16, alphaBufferSize 16, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::scRGBColorSpace, profile QSurfaceFormat::CompatibilityProfile) QSurfaceF
[frameworks-kio] [Bug 417714] New: Keyboard Navigation in File Dialogs
https://bugs.kde.org/show_bug.cgi?id=417714 Bug ID: 417714 Summary: Keyboard Navigation in File Dialogs Product: frameworks-kio Version: 5.67.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Open/save dialogs Assignee: fa...@kde.org Reporter: e...@hotmail.de CC: kdelibs-b...@kde.org Target Milestone: --- This is a resubmission of bug 410653 (duplicate: 412737), which has been marked as resolved fixed, but it is still not working. Am I the only one who is using keyboard navigation in open/save dialogs? Bug description: Pressing ENTER on a selected folder in a save dialog does not open the corresponding folder any more, but instead confirms current selection and closes the dialog. This is a major bug for all keyboard users (am I the only one?). STEPS TO REPRODUCE 1. Try to save a file e.g. in the web browser 2. Select a folder in the file dialog 3. Press ENTER OBSERVED RESULT Dialog is closed EXPECTED RESULT Dialog should switch to the selected folder SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.60.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION This bug exists for quite some time now -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407068] Some views show badly rendered fonts when fractional display scale is used
https://bugs.kde.org/show_bug.cgi?id=407068 Marc changed: What|Removed |Added CC||marc.schle...@gmx.de --- Comment #18 from Marc --- Created attachment 128189 --> https://bugs.kde.org/attachment.cgi?id=128189&action=edit 19.12.3 - still weird fonts This is the first time I am using kdenlive and I am on a 4K display with 150% scaling. There is only this box (dont know what it is called) where the fonts look horrible (see screenshot). I am on 19.12.3 -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 370972] Scanned image is bad
https://bugs.kde.org/show_bug.cgi?id=370972 --- Comment #24 from Marc --- I still have the problem, I can provide you information you will ask tonigh -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 391734] New: Can't export to google photos: SSL Handshake failed
https://bugs.kde.org/show_bug.cgi?id=391734 Bug ID: 391734 Summary: Can't export to google photos: SSL Handshake failed Product: digikam Version: 5.8.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Export-Google Assignee: digikam-bugs-n...@kde.org Reporter: erme...@gmail.com Target Milestone: --- Created attachment 111330 --> https://bugs.kde.org/attachment.cgi?id=111330&action=edit Screenshot of the error displayed after copy paste the code provided by google Hi, I have this issue since I upgraded from 5.6 to 5.7. I'm now in 5.8, using the appimage. Before, I was able to export to google photos. Then I had to reconnect to my google account: - a webbrowser open a tab which tel me that kipi-plugins need some rights - from the webbrowser, I accept: google provide me a code - I past this code in the window in digikam but It failed with the following error: An error happen during authentication "SSL handshake failed (6)" See screenshot below. I'm not sure this is related to digikam or ubuntu because I upgrade also many times my ubuntu (16.04, 17.10), etc. But it reproduce each time now. When I launch digikam from a terminal and I reproduce this bug, no additional relevant information are displayed in the console. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 393382] New: Improve the documentation of the custom shell scripts
https://bugs.kde.org/show_bug.cgi?id=393382 Bug ID: 393382 Summary: Improve the documentation of the custom shell scripts Product: digikam Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: BatchQueueManager Assignee: digikam-bugs-n...@kde.org Reporter: erme...@gmail.com Target Milestone: --- Hi there, I was wondering how to use a custom shell script in the batchQueueManager but can"t find anything in the official documentation. Would you mind define this part in? Regards -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 393383] New: Be able to mass editing album categories in digikam
https://bugs.kde.org/show_bug.cgi?id=393383 Bug ID: 393383 Summary: Be able to mass editing album categories in digikam Product: digikam Version: 5.9.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Albums-MainView Assignee: digikam-bugs-n...@kde.org Reporter: erme...@gmail.com Target Milestone: --- Hi there, I'm not sure that "Album-MainViews" is the most appropriate component for this feature request. My pictures in my collection are managed in the following way: 2018 |_20180101 |_20180312 |_20180427 When we wants to define a category in a folder, we have to: - rick click on the folder - select a category - apply With more than 2000 folders, it will be a very long task. I was wondering if you could implements a way to set the category more quickly? my thoughts was that having an option "apply this category for this folder and the subfolders" or being able to select multiples folders in the directory tree would help me to reduce time to define this information. Regards -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 363224] Kwin crashes from time to time (this time using Virtual Machine Manager)
https://bugs.kde.org/show_bug.cgi?id=363224 --- Comment #38 from marc --- Guys [and girls], From what I have gathered so far, this is what happens: - it appears only with Intel on-chip card [HD graphics] - it only appears when compositor is enabled [desktop effects] - it only shows in VirtualBox - it doesn't matter which rendering method is selected - the issue does not appear on other DEs Maybe you will be able to reproduce the issue with similar configuration. It seems that the issue lies somewhere between QT under kwin and graphics subsystem, from what I can see. W dniu 22.01.2017 o 18:16, Martin Gräßlin pisze: > https://bugs.kde.org/show_bug.cgi?id=363224 > > --- Comment #37 from Martin Gräßlin --- > I'm sorry that you are not satisfied with our quality. We would love to fix > this issue. It's one of the most annoying bugs we currently have and we see > that many users are affected by it. > > The problem is: we developers are not able to reproduce the issue. If we try > the steps outlined in this bug and its many duplicates it just doesn't crash. > There is an important part of the puzzle still missing. Something is different > for our users and for us trying to investigate. > > We need your support to figure out what it is. Once we find the key it will be > easy to fix. That is the proper way forward. Ranting won't fix the issue but > just demotivates those working on it. Please remember that I and most KDE > developers are volunteers working in their free time on it. > -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389205] New: Crash plasmashell
https://bugs.kde.org/show_bug.cgi?id=389205 Bug ID: 389205 Summary: Crash plasmashell Product: plasmashell Version: 5.11.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: marc_van_deur...@hotmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.11.4) Qt Version: 5.9.3 Frameworks Version: 5.40.0 Operating System: Linux 4.14.6-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2fcf5c0e40 (LWP 12273))] Thread 11 (Thread 0x7f2eef608700 (LWP 12302)): #0 0x7f2fc95c54ad in () at /usr/lib64/libQt5Core.so.5 #1 0x7f2fc3c94b51 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2fc3c950f0 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2fc3c9525c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f2fc95c577b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2fc956dc5a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f2fc939d1ea in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f2ef1ed2f67 in KCupsConnection::run() () at /usr/lib64/libkcupslib.so #8 0x7f2fc93a1dde in () at /usr/lib64/libQt5Core.so.5 #9 0x7f2fc858 in start_thread () at /lib64/libpthread.so.0 #10 0x7f2fc8ca66df in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f2f02988700 (LWP 12287)): #0 0x7f2fc3c9501c in () at /usr/lib64/libglib-2.0.so.0 #1 0x7f2fc3c9525c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2fc95c577b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f2fc956dc5a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f2fc939d1ea in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #5 0x7f2fcd076772 in () at /usr/lib64/libQt5Quick.so.5 #6 0x7f2fc93a1dde in () at /usr/lib64/libQt5Core.so.5 #7 0x7f2fc858 in start_thread () at /lib64/libpthread.so.0 #8 0x7f2fc8ca66df in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f2f13fef700 (LWP 12285)): #0 0x7f2fc855b82d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2f9cd3006b in () at /usr/lib64/dri/r600_dri.so #2 0x7f2f9cd2ff87 in () at /usr/lib64/dri/r600_dri.so #3 0x7f2fc858 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2fc8ca66df in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f2f147f0700 (LWP 12284)): #0 0x7f2fc855b82d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2f9cd3006b in () at /usr/lib64/dri/r600_dri.so #2 0x7f2f9cd2ff87 in () at /usr/lib64/dri/r600_dri.so #3 0x7f2fc858 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2fc8ca66df in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f2f9f7c7700 (LWP 12283)): #0 0x7f2fc855b82d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2fced4f554 in () at /usr/lib64/libQt5Script.so.5 #2 0x7f2fced4f599 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f2fc858 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2fc8ca66df in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f2fa5519700 (LWP 12282)): #0 0x7f2fc3cda714 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f2fc3c94678 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2fc3c9507b in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2fc3c9525c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f2fc95c577b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2fc956dc5a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f2fc939d1ea in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f2fc93a1dde in () at /usr/lib64/libQt5Core.so.5 #8 0x7f2fc858 in start_thread () at /lib64/libpthread.so.0 #9 0x7f2fc8ca66df in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f2fa73b1700 (LWP 12281)): #0 0x7f2fc8c97a88 in read () at /lib64/libc.so.6 #1 0x7f2fc3cd93c0 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2fc3c94c2b in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2fc3c950f0 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f2fc3c9525c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f2fc95c577b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f2fc956dc5a in QEventLoop::exec(QFlags) () at /usr/lib
[kwin] [Bug 404274] Windows not displayed
https://bugs.kde.org/show_bug.cgi?id=404274 Marc changed: What|Removed |Added CC||marccollin7...@gmail.com --- Comment #3 from Marc --- (In reply to Vlad Zagorodniy from comment #1) > I'm not quite understand what the problem is, could you please re-clarify > bug description? I start an application on a screen. In this application I open a dialog box. This dialog box is not displayed anywhere... I see it only if I use alt-tab and it's imposible to switch to it -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404274] Windows not displayed
https://bugs.kde.org/show_bug.cgi?id=404274 --- Comment #5 from Marc --- yesterday that was happening with netbeans, firefox will try to open more modal, dialog box... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404274] Windows not displayed
https://bugs.kde.org/show_bug.cgi?id=404274 --- Comment #7 from Marc --- (In reply to Vlad Zagorodniy from comment #6) > Could you please provide a screenshot that shows the problem? ya no problem should not take too much time to see this issue again -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 393382] Improve the documentation of the custom shell scripts
https://bugs.kde.org/show_bug.cgi?id=393382 --- Comment #2 from Marc --- Hello Malk, Do you have a simple example to share? Regards -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 394544] New: Export to inaturalist
https://bugs.kde.org/show_bug.cgi?id=394544 Bug ID: 394544 Summary: Export to inaturalist Product: digikam Version: 5.9.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: erme...@gmail.com Target Milestone: --- Hi there, As a powerful digikam user and also a naturalist, I think that an export feature to inaturalist would be very helpful. background: inaturalist is a community website which allow to identify both plants and animals based upon pictures: we submit a picture, add geotag and a date if there are not embedded in the metadatas, suggest a species and the community will help us to define very precisely the species which have been shooted. main feature request: being able to export to inaturalist from digikam like the google photos export does (automatic login, save credentials, convert raw files into the supported formats by inaturalist). others useful features requests: - Being able to identify from digikam which files have been submitted and which not: it will avoid to being able to compare your submissions from inaturalist website and digikam, task which can be time consuming. - Having an option which doesn't allow submission of pictures which don't have embedded geotag: this is not a real problem in inaturalist to set afterward the geotag, but this is another time we'll have to contribute afterward in inaturalist: it should be done only in digikam, and inaturalist would be there only for identification. - being able to embed the taxonomy which have been defined in inaturalist in the pictures tags: taxnonomy is a very complex classification, and copy them in the pictures tags is a very long task if we do numerous submissions. >From my side, I copy all the taxonomy found in inaturalist in my pictures. Our exchanges on the mailing list highlight that not everyone copy all the taxonomy so perhaps being able to configure which part of the taxonomy should be copied would be useful. Take care: taxonomy is provided in differents languages. We should be able to configure in which lang the taxonomy would be embedded. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394555] New: Crash desktop
https://bugs.kde.org/show_bug.cgi?id=394555 Bug ID: 394555 Summary: Crash desktop Product: plasmashell Version: 5.12.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: marc_van_deur...@hotmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.5) Qt Version: 5.10.0 Frameworks Version: 5.46.0 Operating System: Linux 4.16.9-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: Trying to change the settings of the desktop: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb21abfd5c0 (LWP 1582))] Thread 10 (Thread 0x7fb12700 (LWP 3639)): [KCrash Handler] #6 0x7fb213f5b9eb in raise () at /lib64/libc.so.6 #7 0x7fb213f5cda1 in abort () at /lib64/libc.so.6 #8 0x7fb214376e83 in () at /usr/lib64/libstdc++.so.6 #9 0x7fb21437cdd8 in () at /usr/lib64/libstdc++.so.6 #10 0x7fb21437ce23 in () at /usr/lib64/libstdc++.so.6 #11 0x7fb21470be39 in () at /usr/lib64/libQt5Core.so.5 #12 0x7fb214725cd9 in () at /usr/lib64/libQt5Core.so.5 #13 0x7fb2138cb59b in start_thread () at /lib64/libpthread.so.0 #14 0x7fb21401ea1f in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7fb143f33700 (LWP 1601)): #0 0x7fb214014179 in poll () at /lib64/libc.so.6 #1 0x7fb20e61f429 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb20e61f53c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb214952a2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fb2148f995a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb214720baa in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fb146802887 in KCupsConnection::run() () at /usr/lib64/libkcupslib.so #7 0x7fb214725ba0 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fb2138cb59b in start_thread () at /lib64/libpthread.so.0 #9 0x7fb21401ea1f in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7fb15c9a1700 (LWP 1591)): #0 0x7fb2138d156c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb1edf88e4b in () at /usr/lib64/dri/r600_dri.so #2 0x7fb1edf88b77 in () at /usr/lib64/dri/r600_dri.so #3 0x7fb2138cb59b in start_thread () at /lib64/libpthread.so.0 #4 0x7fb21401ea1f in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7fb1ecc43700 (LWP 1590)): #0 0x7fb2138d156c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb1edf88e4b in () at /usr/lib64/dri/r600_dri.so #2 0x7fb1edf88b77 in () at /usr/lib64/dri/r600_dri.so #3 0x7fb2138cb59b in start_thread () at /lib64/libpthread.so.0 #4 0x7fb21401ea1f in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fb1f8aa6700 (LWP 1589)): #0 0x7fb2138d156c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb21a383614 in () at /usr/lib64/libQt5Script.so.5 #2 0x7fb21a383659 in () at /usr/lib64/libQt5Script.so.5 #3 0x7fb2138cb59b in start_thread () at /lib64/libpthread.so.0 #4 0x7fb21401ea1f in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fb1fa97a700 (LWP 1588)): #0 0x7fb20e664e29 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fb20e61ee4c in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb20e61f3d0 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb20e61f53c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fb214952a2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb2148f995a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fb214720baa in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fb217ffa115 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7fb214725ba0 in () at /usr/lib64/libQt5Core.so.5 #9 0x7fb2138cb59b in start_thread () at /lib64/libpthread.so.0 #10 0x7fb21401ea1f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fb1fbfff700 (LWP 1587)): #0 0x7fb214014179 in poll () at /lib64/libc.so.6 #1 0x7fb20e61f429 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb20e61f53c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb214952a2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fb2148f995a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb214720baa in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fb217ffa115 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fb214725ba0 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fb2138cb59b in start_thread () at /lib64/libpthread.so.0 #9 0x7fb21401ea1f
[digikam] [Bug 394588] New: Exports: being able to block an export if there is some missing tags
https://bugs.kde.org/show_bug.cgi?id=394588 Bug ID: 394588 Summary: Exports: being able to block an export if there is some missing tags Product: digikam Version: 5.9.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: erme...@gmail.com Target Milestone: --- Hi there, I share many photos in many websites. I would appreciate if we can block an export (and notify why) if there is some missing metadatas (such as geotags, copyright, etc). These required metadatas should I think be configurable. Kind regards Mat -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 394589] New: Feature request: being able to copy geotags from one picture to another from the main window
https://bugs.kde.org/show_bug.cgi?id=394589 Bug ID: 394589 Summary: Feature request: being able to copy geotags from one picture to another from the main window Product: digikam Version: 5.9.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Metadata-Gps Assignee: digikam-bugs-n...@kde.org Reporter: erme...@gmail.com Target Milestone: --- Hi there, I was wondering if it would be possible having this kind of feature? I mean, select a picture, choose copy geotags, then select the appropriate pictures where we wants to copy these metadatas. Kind regards Mat -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 394590] New: Feature request: being able to filter on all metadatas fields
https://bugs.kde.org/show_bug.cgi?id=394590 Bug ID: 394590 Summary: Feature request: being able to filter on all metadatas fields Product: digikam Version: 5.9.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Searches Assignee: digikam-bugs-n...@kde.org Reporter: erme...@gmail.com Target Milestone: --- Hi there, In my publication process, I often use exiftool to find a matching selection of files such as: - files which match a custom gps latitude ref - files which do not have embedded gps altitude ref - files which have a specific gps altitude ref - files coming from a custom model of body etc. I was wondering if it would be possible having a way to filter on all the existing metadatas and add them in the current filters? Kind regards Mat -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 394591] New: Feature request : being able to apply google elevation api on a list of pictures
https://bugs.kde.org/show_bug.cgi?id=394591 Bug ID: 394591 Summary: Feature request : being able to apply google elevation api on a list of pictures Product: digikam Version: 5.9.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Geolocation Assignee: digikam-bugs-n...@kde.org Reporter: erme...@gmail.com Target Milestone: --- Hi there, Some pictures coming from modern phones embedded only latitude et longitude information. Google elevation APi is able to fetch from a latitude and a longitude the related altitude. I would appreciate being able from a selection of pictures being able to select a option "import google elevation api" altitude and let digikam getting the altitude to set on these pictures. Kind regards Mat -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 394590] Feature request: being able to filter on all metadatas fields
https://bugs.kde.org/show_bug.cgi?id=394590 Marc changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #2 from Marc --- Hi Maik, I didn't knew this advanced search form. It seems that this feature request could be closed because it looks like I could reach my expectations with this form. regards -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376453] Labels, Comments and dates disappear when folder is not readable
https://bugs.kde.org/show_bug.cgi?id=376453 Marc changed: What|Removed |Added CC||erme...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376453] New: Labels, Comments and dates disappear when folder is not readable
https://bugs.kde.org/show_bug.cgi?id=376453 Bug ID: 376453 Summary: Labels, Comments and dates disappear when folder is not readable Product: digikam Version: 5.4.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: AlbumsView-Group Assignee: digikam-de...@kde.org Reporter: erme...@gmail.com Target Milestone: --- Hello, My pictures are stored in a remote folder access through NFS. Albums are configured as mountable folders. After setting wrong permissions in these folder, all the meta information stored on each folder in the album view (categories, comments, specified date, thumbnails) have disappeared. Restoring appropriate permissions does not restore these informations. Expected Results: Keep information even if files are not readable. digikam 5.4, Using: KDE Frameworks 5.18.0 Qt 5.5.1 (built against 5.5.1) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376453] Labels, Comments and dates disappear when folder is not readable
https://bugs.kde.org/show_bug.cgi?id=376453 --- Comment #2 from Marc --- Hello(In reply to caulier.gilles from comment #1) > Why do you assign this file to AlbumView-Group ? The title said the image > properties as Labels and comments are lost. > > Gilles Caulier Hello Gilles, Perhaps the selected category is wrong, I'm sorry: I'm talking about the left part of the main digikam interface which show the directory tree and album folder: properties are those one when we right click on one album. Regards -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376470] New: Title is not refreshed when read again metadata from file is launched
https://bugs.kde.org/show_bug.cgi?id=376470 Bug ID: 376470 Summary: Title is not refreshed when read again metadata from file is launched Product: digikam Version: 5.4.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Metadata Assignee: digikam-de...@kde.org Reporter: erme...@gmail.com Target Milestone: --- Hello, I think the title is not refreshed when we execute "Read again metadata from file" from the Item menu. Step to reproduce: - Open digikam, select a picture, open the right panel "caption" > "description". - Set the title 'title original" on this picture for the french locale using digikam. - Click Save metadata on files - Confirm that this title has been set in picture using an external tool, such as exiftool (exiftool -XMP:Title-FR-fr /path/to/picture.jpg). - Set a new value for this title using an external tool (by running exiftool -XMP:Title-FR-fr="new title" /path/to/picture.jpg) - Confirm that this title has really been set in this pictures metadata by using the previous command (exiftool -XMP:Title-FR-fr /path/to/picture.jpg) - Under digikam, select the picture and refresh its metadata from the menu Item > Read again metadata from file. - See that from the right panel / caption / title, title has not changed. Expected results: The title field should display "new title" -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376470] Title is not refreshed when read again metadata from file is launched
https://bugs.kde.org/show_bug.cgi?id=376470 Marc changed: What|Removed |Added CC||erme...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376473] New: Can"t set empty IPTC country code when using metadata templates
https://bugs.kde.org/show_bug.cgi?id=376473 Bug ID: 376473 Summary: Can"t set empty IPTC country code when using metadata templates Product: digikam Version: 5.4.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Metadata-Template Assignee: digikam-de...@kde.org Reporter: erme...@gmail.com Target Milestone: --- Created attachment 104026 --> https://bugs.kde.org/attachment.cgi?id=104026&action=edit Screenshot of the interface which allow to define metadata templates: we cannot set empty country code as Location Hello, The metadata templates are very usefull to set easily some metadata tags. But interface which allow to configure a template doesn't allow to configure an empty country (see screenshot). So if we don't want to manage location in template, we cannot: Aruba country code will be used. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 328321] Image orientation is not maintained when processing RAW image through BQM
https://bugs.kde.org/show_bug.cgi?id=328321 --- Comment #13 from Marc --- Created attachment 102793 --> https://bugs.kde.org/attachment.cgi?id=102793&action=edit Exifs tags differences between the original RAW file and the generated JPG coming from batch queue manager / convert into JPG process -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 328321] Image orientation is not maintained when processing RAW image through BQM
https://bugs.kde.org/show_bug.cgi?id=328321 --- Comment #14 from Marc --- Hello, I'm Still having this issue under digikam 5.3 coming from PPA under Ubuntu X64 distribution (Version 5.3, Using: KDE Frameworks 5.18.0 Qt 5.5.1 (built against 5.5.1) The xcb windowing system) exiftool -Orientation /home/marc/pictures/343A5594.CR2 Orientation : Rotate 90 CW process this raw file with batch processing / convert into JPG (JPG quality 100, 4.4.4) generate a 343A5594.JPG file exiftool -Orientation /home/marc/pictures/343A5594.jpg Orientation : Horizontal (normal) exifool /home/marc/pictures/343A5594.CR2 | sort > /tmp/cr2.txt exifool /home/marc/pictures/343A5594.jpg | sort > /tmp/jpg.txt diff /tmp/cr2.txt /tmp/jpg.txt --suppress-common-lines > /tmp/diff_exifs_tags_between_raw_and_generated_jpg.txt file has been attached to this post. -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 373678] New: Videos exported in google photos are not available (still processing state)
https://bugs.kde.org/show_bug.cgi?id=373678 Bug ID: 373678 Summary: Videos exported in google photos are not available (still processing state) Product: kipiplugins Version: 5.3.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: GoogleServices Assignee: kde-imag...@kde.org Reporter: erme...@gmail.com Target Milestone: --- Hello, When I try to export videos (MP4, MOV and AVI files) 95% of these videos are not available in google photos: they are in state still processing. Google photos support say that it can take up to 8 hours to process videos, but even if I wait for one day, they are still in state "still processing". If I upload in google photos these videos from the google photos upload form, they are available. To reproduce: - browse in digikam the directory tree. - filter directory tree to "Videos files". - select all videos files listed - click on them to validate they are readable > the file is playing - select all videos files listed - click on the export to google photos menu item - log in to your google account > google account is listed in google account field - select no folder in the folder destination - click on resize photo - select JPG quality: 72 - maximum dimensions: 2048 - Tag path behaviour: split tags - click start upload > after some time, all videos have disappeared from the list on the left panel - go to your google photos account with your favorite browser - videos are listed, but the are marked as "still processing" - -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 373678] Videos exported in google photos are not available (still processing state)
https://bugs.kde.org/show_bug.cgi?id=373678 Marc changed: What|Removed |Added CC||erme...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373682] New: geolocalisation filter does not take care of the videos geolocalisation tags
https://bugs.kde.org/show_bug.cgi?id=373682 Bug ID: 373682 Summary: geolocalisation filter does not take care of the videos geolocalisation tags Product: digikam Version: 5.3.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Filters Assignee: digikam-de...@kde.org Reporter: erme...@gmail.com Target Milestone: --- Hello, Context: Digikam 5.3, coming from ppa, Ubuntu 16.04 64bits, KDE Frameworks 5.18.0 Qt 5.5.1 (built against 5.5.1) The xcb windowing system. When a movie embed geo tags, they are not filtered in digikam when applying "files with geolocalisation" or "files without geolocalisation" filter. To reproduce: 1. select a video available in digikam folders (/home/marc/pictures/movie.mov). 2. check if this video already have exif geolocalisation tags. for example with exiftool: exiftool -n -GPSLatitude -GPSLongitude /home/marc/pictures/movie.mov 3. if this command does not display something, add some geolocalisation tag to this video: exiftool -GPSLatitude=48.858356 -GPSLongitude=2.294460 -GPSLatitudeRef=North -GPSLongitudeRef=East /home/marc/pictures/movie.mov 4. check that exif infos have really set on file: exiftool -n -GPSLatitude -GPSLongitude /home/marc/pictures/movie.mov => will display: GPS Latitude: 48 deg 51' 30.08" N GPS Longitude : 2 deg 17' 40.06" E GPS Latitude Ref: North GPS Longitude Ref : East 5. in digikam, select this movie and click on update metadata from file content. 6. in filters, select "display movies only" => movie must be listed 7. in filters, select "without geolocalisation" => movie will be displayed. it should not 8. in filters, select "with geolocalisation" => movie won't be displayed, it should. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373682] geolocalisation filter does not take care of the videos geolocalisation tags
https://bugs.kde.org/show_bug.cgi?id=373682 Marc changed: What|Removed |Added CC||erme...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 374293] New: Google albums reload button still display albums which have been removed from google photos
https://bugs.kde.org/show_bug.cgi?id=374293 Bug ID: 374293 Summary: Google albums reload button still display albums which have been removed from google photos Product: kipiplugins Version: 5.3.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: GoogleServices Assignee: kde-imag...@kde.org Reporter: erme...@gmail.com Target Milestone: --- Hello, I'm not sure if this is an issue in digikam or an issue in the google photos API. Here's the context: I share some pictures within digikam 5 (5.3 / ppa / ubuntu) in google photos from the menu Export > Export to google photos / Picasa. When I open this field, my google account is listed and my remote google photos albums are listed in the selectbox. If I remove one of this album from google photos with a web browser and I click on the reload button in digikam, this remote album is still displayed. I need to restart digikam to ensure this remote album is not visible anymore in the album selectbox. -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 374293] Google albums reload button still display albums which have been removed from google photos
https://bugs.kde.org/show_bug.cgi?id=374293 Marc changed: What|Removed |Added CC||erme...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 374294] New: Be able to import photos in the photos directory
https://bugs.kde.org/show_bug.cgi?id=374294 Bug ID: 374294 Summary: Be able to import photos in the photos directory Product: kipiplugins Version: 5.3.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: GoogleServices Assignee: kde-imag...@kde.org Reporter: erme...@gmail.com Target Milestone: --- Hello, Google photos manage a pool a photos. These photos can be organized in albums. When we export to google photos from the menu Exportation > Export to google photos / picasa, we must select an album. This is an issue because google photos albums allow only 2000 pictures. So if you select more than 2000 photos in digikam, export process will run but there will be some missing photos in the remote album. -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 374294] Be able to import photos in the photos directory
https://bugs.kde.org/show_bug.cgi?id=374294 Marc changed: What|Removed |Added CC||erme...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 374294] Be able to import photos in the photos pool
https://bugs.kde.org/show_bug.cgi?id=374294 Marc changed: What|Removed |Added Summary|Be able to import photos in |Be able to import photos in |the photos directory|the photos pool -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 374294] Be able to export photos from digikam to the google photos pool
https://bugs.kde.org/show_bug.cgi?id=374294 Marc changed: What|Removed |Added Summary|Be able to import photos in |Be able to export photos |the photos pool |from digikam to the google ||photos pool -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 384025] New: Kmail does not crypt automatically when responding to crypted mail
https://bugs.kde.org/show_bug.cgi?id=384025 Bug ID: 384025 Summary: Kmail does not crypt automatically when responding to crypted mail Product: kmail2 Version: 5.5.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: marc.derum...@free.fr Target Milestone: --- Hi, I installed new opensuse Leap 42.3 and unfortunately, I can't configure kmail to automatically crypt the message when I reply to someone that has crypted his message. And of course, I often forget to check before sending, so my message is sent uncrypted and even the quote message is uncrypted... It would be great if kmail could consider that if the incoming mail is crypted, the response should also be crypted to keep the whole discussion secured. I'm almost sure that on my old opensuse 13.2, kmail had this behavior by default and I could not find any check button in the config panel. The only options available are (translated from my french install) : - "always send crypted if possible" (in the identity config), but as it is not possible to decrypt on a smartphone via gmail, I rather send uncrypted unless content is sensitive ; - "ask when trying to send uncrypted message" (in the security panel), but that mean that I always have to click all day long on that window for all common uncrypted messages. Thanks for any advice if I could not find the right config, otherwise, I put that option on the wishlist ! Thanks for developing such a nice tool ! Marc -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 384025] Kmail does not crypt automatically when responding to crypted mail
https://bugs.kde.org/show_bug.cgi?id=384025 marc changed: What|Removed |Added CC||marc.derum...@free.fr -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374453] New: Display as Date the DateUTC metadata coming from MP4 files
https://bugs.kde.org/show_bug.cgi?id=374453 Bug ID: 374453 Summary: Display as Date the DateUTC metadata coming from MP4 files Product: digikam Version: 5.3.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Metadata Assignee: digikam-de...@kde.org Reporter: erme...@gmail.com Target Milestone: --- Created attachment 103142 --> https://bugs.kde.org/attachment.cgi?id=103142&action=edit Suprising displayed dates in metadata panel for video files Hello, Digikam allow to manage both pictures and movies files and metadata are displayed for both these 2 kind of files. But Date metadatas are displayed in a very uncommon way in the right panel which display the embedded metadata (see screenshot). It seems this is an issue in digikam: if I use an different software like exiftool to fetch metadata dates, they are displayed correctly: $: exiftool /home/marc/pictures/GOPR0022.MP4 | grep Date File Modification Date/Time : 2013:01:02 12:23:11+01:00 File Access Date/Time : 2017:01:01 19:52:08+01:00 File Inode Change Date/Time : 2017:01:01 19:45:55+01:00 Modify Date : 2013:01:02 18:23:11 Track Create Date : 2013:01:02 18:23:11 Track Modify Date : 2013:01:02 18:23:11 Media Create Date : 2013:01:02 18:23:11 Media Modify Date : 2013:01:02 18:23:11 Date/Time Original : 2013:01:02 12:23:11 Create Date : 2013:01:02 12:23:11 This issue seems related to #316882 which is marked as fixed, but I'm still encounter this problem with 5.3 coming from ppa. Regards -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374453] Display as Date the DateUTC metadata coming from MP4 files
https://bugs.kde.org/show_bug.cgi?id=374453 Marc changed: What|Removed |Added CC||erme...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374453] Extract right video date from MP4 files metadata
https://bugs.kde.org/show_bug.cgi?id=374453 --- Comment #2 from Marc --- Hello Gilles, First, thanks for your quick answer. I haven't the required knowledge to judge which is the better API to process metadata: exiftool example was just to identify which component is responsible of this display. I'll give you a feedback with the 5.4 version. Regards -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374516] New: Persons metadata are not updated after a tag removed
https://bugs.kde.org/show_bug.cgi?id=374516 Bug ID: 374516 Summary: Persons metadata are not updated after a tag removed Product: digikam Version: 5.3.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Metadata-Editor Assignee: digikam-de...@kde.org Reporter: erme...@gmail.com Target Milestone: --- Created attachment 103183 --> https://bugs.kde.org/attachment.cgi?id=103183&action=edit Exiftool output before removing unappropriate person tag Hello, My wife has changed her name and so, I try to rename all her embedded tags within digikam. First, I have tried to rename her tag in the metadata person tag. I was thinking it was ok. But after reloading metadata from files, I see that on some files, pictures have both her old and new person tag. So I try now to remove the old tag. Before applying update, I've collected exif metadata with exiftool (exiftool /home/marc/pictures/img_6654.cr2). File has been attached under before.txt. In digikam, in one picture which have both the new and old tag, I remove from the picture her old name. Then I click to "apply metadata in picture" from menu item. After applying tag, I have collected metadata with exiftool. File has been attached under afterupdate.txt. Under digikam, My wife is now known has her new name. But If I refresh metadata (under menu item > reload metadata from file), she still known under the two names. I was thinking of a permission issue, but file have rw for every one. -- You are receiving this mail because: You are watching all bug changes.
