[kontact] [Bug 393558] New: sync with gmail address book
https://bugs.kde.org/show_bug.cgi?id=393558 Bug ID: 393558 Summary: sync with gmail address book Product: kontact Version: 5.7.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: contacts Assignee: to...@kde.org Reporter: emil.gazaz...@scitoday.org CC: kdepim-b...@kde.org Target Milestone: --- Daar Developers, Kontact sync with gmail address book only first time but after same time cannot sync with gmail address book. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 393559] New: sync with gmail
https://bugs.kde.org/show_bug.cgi?id=393559 Bug ID: 393559 Summary: sync with gmail Product: kontact Version: 5.7.2 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: calendar Assignee: kdepim-b...@kde.org Reporter: emil.gazaz...@scitoday.org Target Milestone: --- Daar Developers, Kontact sync with gmail calendar only first time but after same time cannot sync with gmail caendar. -- You are receiving this mail because: You are watching all bug changes.
[kmail] [Bug 31360] kmail does not delete mail, spontaneously recovers deleted mail
https://bugs.kde.org/show_bug.cgi?id=31360 Emil changed: What|Removed |Added CC||emil.gazaz...@scitoday.org -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 393560] New: delete e-mail
https://bugs.kde.org/show_bug.cgi?id=393560 Bug ID: 393560 Summary: delete e-mail Product: kontact Version: 5.7.2 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: emil.gazaz...@scitoday.org Target Milestone: --- Dear Developers, I use filters to sort an email. sorted e-mail I redirect to the sub-folder. and in subfolder. I unnecessary e-mails was erase but some e-mail are not erased. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 393561] New: mail spend to much time for open e-mail
https://bugs.kde.org/show_bug.cgi?id=393561 Bug ID: 393561 Summary: mail spend to much time for open e-mail Product: kontact Version: 5.7.2 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: emil.gazaz...@scitoday.org Target Milestone: --- Dear Developers, kontact spend more time for open email and for this period of show me "please wait while the message is transferred". Connection is carried out according to the protocol of pop -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 393597] New: sync with google
https://bugs.kde.org/show_bug.cgi?id=393597 Bug ID: 393597 Summary: sync with google Product: kontact Version: 5.7.2 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: summary Assignee: kdepim-b...@kde.org Reporter: emil.gazaz...@scitoday.org Target Milestone: --- Dear Developers, PIM KMAIL after the first synchronization it is not synchronized The problem is solved only after the deletion (address book and calendars) and reconnect. Kubuntu 18.04 LTS Kontact 5.7.3 Linux (x86_64) release 4.15.0-20-generic -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 394039] New: Krita closes immediately when trying to change font
https://bugs.kde.org/show_bug.cgi?id=394039 Bug ID: 394039 Summary: Krita closes immediately when trying to change font Product: krita Version: 3.1.1 Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tool/Text Assignee: krita-bugs-n...@kde.org Reporter: emilko...@gmx.com Target Milestone: --- I was editing a painting in Krita and I added some text. Then I erased all default text and tried to change font. When I clicked next to the dropdown for fonts (the empty area) Krita closed immediately without any prompts. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433957] New: system monitor widget horizontal bars only work correctly for CPU load and frequency
https://bugs.kde.org/show_bug.cgi?id=433957 Bug ID: 433957 Summary: system monitor widget horizontal bars only work correctly for CPU load and frequency Product: plasmashell Version: 5.21.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: emil.vanh...@gmail.com CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 Created attachment 136368 --> https://bugs.kde.org/attachment.cgi?id=136368&action=edit video file of the horizontal bars not scaling SUMMARY The system monitor widget horizontal bars only work correctly for CPU load and frequency, other stats (temp, fan, download rate, upload rate, ...) always show full bars. See attached video. STEPS TO REPRODUCE 1. Add system monitor widget 2. Change display style to "Horizontal Bars" 3. Add some sensors OBSERVED RESULT Only the CPU load and frequency sensor bars will correctly scale with the sensor values, all the others are always 100% full. EXPECTED RESULT All bars scale with sensor values. 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.
[plasmashell] [Bug 433957] system monitor widget horizontal bars only work correctly for CPU load and frequency
https://bugs.kde.org/show_bug.cgi?id=433957 --- Comment #2 from Emil --- Why? What's the difference with vertical bars? I would put in a manual maximum value, but the setting seem to be missing for horizontal bars -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420927] New: quick tile is very hard to trigger on multi monitor middle edge
https://bugs.kde.org/show_bug.cgi?id=420927 Bug ID: 420927 Summary: quick tile is very hard to trigger on multi monitor middle edge Product: kwin Version: 5.18.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: multihead Assignee: kwin-bugs-n...@kde.org Reporter: emil.vanh...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. have a multi monitor setup 2. Drag a window to the edge between the two screens for quick tile OBSERVED RESULT You need to be very slow and very precise to be able to tile the window. EXPECTED RESULT It should be easy to quick tile a window. Maybe make the trigger come earlier on the edge in the middle? 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.
[kwin] [Bug 420927] quick tile is very hard to trigger on multi monitor middle edge
https://bugs.kde.org/show_bug.cgi?id=420927 Emil changed: What|Removed |Added Ever confirmed|0 |1 Resolution|UNMAINTAINED|--- Version|5.18.4 |5.27.10 Status|RESOLVED|REOPENED --- Comment #3 from Emil --- Still the same on 5.27.10 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433354] New: Network speed monitor legend spacing jumps around
https://bugs.kde.org/show_bug.cgi?id=433354 Bug ID: 433354 Summary: Network speed monitor legend spacing jumps around Product: plasmashell Version: 5.21.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: emil.vanh...@gmail.com CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 Created attachment 135988 --> https://bugs.kde.org/attachment.cgi?id=135988&action=edit video file of the network speed legend spacing jumping around SUMMARY Network speed monitor download/upload rate jumps around (see attached video) STEPS TO REPRODUCE 1. Add Network speed widget 2. Increase the width of the widget, just under the size that it would show a 2 column legend. 3. introduce a bit of network traffic OBSERVED RESULT The legend text with "Download Rate" and "Upload Rate" jumps around. EXPECTED RESULT The text spacing stays the same, preferably with "Download Rate" aligned left and the "XX B/KiB/MiB/s" aligned to the right. 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.
[plasmashell] [Bug 433355] New: Cannot change or (un)hide title system monitor widget
https://bugs.kde.org/show_bug.cgi?id=433355 Bug ID: 433355 Summary: Cannot change or (un)hide title system monitor widget Product: plasmashell Version: 5.21.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: emil.vanh...@gmail.com CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 SUMMARY Cannot change or (un)hide the title of system monitor widgets after first configuration. STEPS TO REPRODUCE 1. Add any system monitor widget (Disk Usage, Individual Core Usage, System Monitor Sensor, Network speed, ...) 2. Open the widget configuration, changing the title / hide unhide the title works. 3. Close the configuration. 4. Re-open widget configuration, changing the title / hide unhide the title has no effect anymore. OBSERVED RESULT Changing the title / hide unhide the title has no effect anymore. EXPECTED RESULT Changing the title / hide unhide the title works. 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.
[plasmashell] [Bug 433375] New: system monitor widget doesn't remember unit and si prefix when using manual y data range
https://bugs.kde.org/show_bug.cgi?id=433375 Bug ID: 433375 Summary: system monitor widget doesn't remember unit and si prefix when using manual y data range Product: plasmashell Version: 5.21.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: emil.vanh...@gmail.com CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 Created attachment 136007 --> https://bugs.kde.org/attachment.cgi?id=136007&action=edit screenshot of unit and si prefix missing SUMMARY system monitor widget doesn't remember unit when using manual y data range, see attached image. Left is with an automatic y range and right is with a manual y range, the unit and si prefix are missing. STEPS TO REPRODUCE 1. Add any system monitor widget that uses line chart or bar chart chart (Disk Usage, Individual Core Usage, System Monitor Sensor, Network speed, ...) 2. Open the widget configuration and disable "Automatic Y Data Range" 3. logout and login again. OBSERVED RESULT Y axis units are gone EXPECTED RESULT Y axis units are show and it's possible to select Si prefix (K/Ki/Mi/G/Gi ...) for the data range. 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.
[plasmashell] [Bug 433450] New: system monitor widget text-only sensors are not shown when graph legend is hidden
https://bugs.kde.org/show_bug.cgi?id=433450 Bug ID: 433450 Summary: system monitor widget text-only sensors are not shown when graph legend is hidden Product: plasmashell Version: 5.21.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: emil.vanh...@gmail.com CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 SUMMARY Text-only sensors are not shown when sensor graph legend is hidden. STEPS TO REPRODUCE 1. Add any system monitor widget (Disk Usage, Individual Core Usage, System Monitor Sensor, Network speed, ...) 2. Open the widget configuration, add a text-only sensors 3. Disable "Show Sensor Legend" OBSERVED RESULT The text-only sensor is not shown. EXPECTED RESULT Text-only sensors should be shown even when the graph legend is hidden. 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.
[plasmashell] [Bug 433375] system monitor widget doesn't remember unit and si prefix when using manual y data range
https://bugs.kde.org/show_bug.cgi?id=433375 Emil changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- Ever confirmed|0 |1 --- Comment #2 from Emil --- Not only the prefix but also the units on the y axis are gone. %, °C, Hz etc are not shown. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433375] system monitor widget doesn't remember unit and si prefix when using manual y data range
https://bugs.kde.org/show_bug.cgi?id=433375 --- Comment #3 from Emil --- Created attachment 136195 --> https://bugs.kde.org/attachment.cgi?id=136195&action=edit % missing Units are missing too -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433375] system monitor widget doesn't remember unit and si prefix when using manual y data range
https://bugs.kde.org/show_bug.cgi?id=433375 --- Comment #5 from Emil --- Created attachment 136198 --> https://bugs.kde.org/attachment.cgi?id=136198&action=edit plasmashell log Anything useful in here? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433375] system monitor widget doesn't remember unit and si prefix when using manual y data range
https://bugs.kde.org/show_bug.cgi?id=433375 --- Comment #6 from Emil --- I can reproduce the issue consistently on 2 different machines. Plasmashell needs to be restarted for the problem to occur. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420927] quick tile is very hard to trigger on multi monitor middle edge
https://bugs.kde.org/show_bug.cgi?id=420927 --- Comment #5 from Emil --- Great! This is indeed what I wanted. Is there a way to have this behavior only during window dragging? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490018] New: plasmashell crashes after unlock screen
https://bugs.kde.org/show_bug.cgi?id=490018 Bug ID: 490018 Summary: plasmashell crashes after unlock screen Classification: Plasma Product: plasmashell Version: 6.1.1 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: emil.vanh...@gmail.com Target Milestone: 1.0 Application: plasmashell (6.1.1) Qt Version: 6.7.2 Frameworks Version: 6.3.0 Operating System: Linux 6.9.7-arch1-1 x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 6.1.1 [CoredumpBackend] -- Information about the crash: The plasmashell crashed sometimes after I unlock my screen. It seems to only happen after several minutes or hours of inactivity, not when I lock and unlock immediately. I have a few crash reports, hopefully they are useful. The crash can be reproduced sometimes. -- Backtrace (Reduced): #5 QtWaylandClient::QWaylandWindow::waylandScreen (this=0x5e1d1b750b40) at /usr/src/debug/qt6-wayland/qtwayland/src/client/qwaylandwindow.cpp:956 #6 QtWaylandClient::QWaylandWindow::devicePixelRatio (this=0x5e1d1b750b40) at /usr/src/debug/qt6-wayland/qtwayland/src/client/qwaylandwindow.cpp:1519 #7 0x79aafa4e9f0c in QtWaylandClient::QWaylandEglWindow::updateSurface (this=0x5e1d1b750b40, create=true) at /usr/src/debug/qt6-wayland/qtwayland/src/hardwareintegration/client/wayland-egl/qwaylandeglwindow.cpp:70 #8 0x79aafa4ea905 in QtWaylandClient::QWaylandGLContext::makeCurrent (this=this@entry=0x79a9f0002210, surface=) at /usr/src/debug/qt6-wayland/qtwayland/src/hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:318 #9 0x79ab016adc28 in QOpenGLContext::makeCurrent (this=0x79a9f0001f60, surface=0x5e1d1b752f50) at /usr/src/debug/qt6-base/qtbase/src/gui/kernel/qopenglcontext.cpp:664 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490018] plasmashell crashes after unlock screen
https://bugs.kde.org/show_bug.cgi?id=490018 --- Comment #1 from Emil --- Created attachment 171532 --> https://bugs.kde.org/attachment.cgi?id=171532&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490018] plasmashell crashes after unlock screen
https://bugs.kde.org/show_bug.cgi?id=490018 --- Comment #2 from Emil --- Created attachment 171533 --> https://bugs.kde.org/attachment.cgi?id=171533&action=edit crash information -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490018] plasmashell crashes after unlock screen
https://bugs.kde.org/show_bug.cgi?id=490018 Emil changed: What|Removed |Added Attachment #171533|crash information |crash information description||20240706-231330 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490018] plasmashell crashes after unlock screen
https://bugs.kde.org/show_bug.cgi?id=490018 --- Comment #3 from Emil --- Created attachment 171534 --> https://bugs.kde.org/attachment.cgi?id=171534&action=edit crash information 20240705-134303 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490018] plasmashell crashes after unlock screen
https://bugs.kde.org/show_bug.cgi?id=490018 --- Comment #4 from Emil --- Created attachment 171535 --> https://bugs.kde.org/attachment.cgi?id=171535&action=edit crash information 20240704-220148. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490018] plasmashell crashes after unlock screen
https://bugs.kde.org/show_bug.cgi?id=490018 --- Comment #5 from Emil --- Created attachment 171536 --> https://bugs.kde.org/attachment.cgi?id=171536&action=edit crash information 20240704-091122 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 490120] plasma-browser-integration-host repeatedly crashing in Firefox 128
https://bugs.kde.org/show_bug.cgi?id=490120 Emil changed: What|Removed |Added CC||emil.vanh...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487118] The Power Management applet displays incorrect description of effects of org.freedesktop.portal.Inhibit
https://bugs.kde.org/show_bug.cgi?id=487118 Emil changed: What|Removed |Added CC||emil.vanh...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487118] The Power Management applet displays incorrect description of effects of org.freedesktop.portal.Inhibit
https://bugs.kde.org/show_bug.cgi?id=487118 --- Comment #1 from Emil --- Is this not a bug in kscreenlocker? If I'm not mistaken the logic which correctly detects the inhibition in the battery monitor is here: https://invent.kde.org/plasma/powerdevil/-/blob/master/applets/batterymonitor/plugin/powermanagementcontrol.cpp But kscreensaver fails to detect that the screen has to be locked: https://invent.kde.org/plasma/kscreenlocker/-/blob/master/powermanagement_inhibition.cpp -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487118] The Power Management applet displays incorrect description of effects of org.freedesktop.portal.Inhibit
https://bugs.kde.org/show_bug.cgi?id=487118
--- Comment #2 from Emil ---
If org.freedesktop.portal.Inhibit is used with Firefox in Flatpak I see this
with dbus-monitor
>signal time=1722369868.405491 sender=org.freedesktop.DBus ->
>destination=:1.1401 serial=4294967295 path=/org/freedesktop/DBus;
>interface=org.freedesktop.DBus; member=NameAcquired
> string ":1.1401"
>signal time=1722369868.405515 sender=org.freedesktop.DBus ->
>destination=:1.1401 serial=4294967295 path=/org/freedesktop/DBus;
>interface=org.freedesktop.DBus; member=NameLost
> string ":1.1401"
>method call time=1722369869.908031 sender=:1.544 ->
>destination=org.kde.Solid.PowerManagement serial=13724
>path=/org/kde/Solid/PowerManagement/PolicyAgent;
>interface=org.kde.Solid.PowerManagement.PolicyAgent; member=AddInhibition
> uint32 1
> string "org.mozilla.firefox"
> string "video-playing"
>signal time=1722369874.825363 sender=:1.545 -> destination=(null destination)
>serial=9434 path=/org/kde/Solid/PowerManagement/PolicyAgent;
>interface=org.kde.Solid.PowerManagement.PolicyAgent; member=InhibitionsChanged
> array [
> struct {
> string "org.mozilla.firefox"
> string "video-playing"
> }
> ]
> array [
> ]
>method call time=1722369874.825737 sender=:1.515 ->
>destination=org.kde.Solid.PowerManagement.PolicyAgent serial=4342
>path=/org/kde/Solid/PowerManagement/PolicyAgent;
>interface=org.kde.Solid.PowerManagement.PolicyAgent; member=HasInhibition
> uint32 4
>method call time=1722369874.827273 sender=:1.535 ->
>destination=org.kde.Solid.PowerManagement serial=304963
>path=/org/kde/Solid/PowerManagement/PolicyAgent;
>interface=org.kde.Solid.PowerManagement.PolicyAgent; member=ListInhibitions
>method call time=1722369874.827313 sender=:1.535 ->
>destination=org.kde.Solid.PowerManagement serial=304964
>path=/org/kde/Solid/PowerManagement/PolicyAgent;
>interface=org.kde.Solid.PowerManagement.PolicyAgent; member=ListInhibitions
>method call time=1722369877.280859 sender=:1.544 ->
>destination=org.kde.Solid.PowerManagement serial=13727
>path=/org/kde/Solid/PowerManagement/PolicyAgent;
>interface=org.kde.Solid.PowerManagement.PolicyAgent; member=ReleaseInhibition
> uint32 920
>signal time=1722369877.281258 sender=:1.545 -> destination=(null destination)
>serial=9439 path=/org/kde/Solid/PowerManagement/PolicyAgent;
>interface=org.kde.Solid.PowerManagement.PolicyAgent; member=InhibitionsChanged
> array [
> ]
> array [
> string "org.mozilla.firefox"
> ]
>method call time=1722369877.281461 sender=:1.515 ->
>destination=org.kde.Solid.PowerManagement.PolicyAgent serial=4343
>path=/org/kde/Solid/PowerManagement/PolicyAgent;
>interface=org.kde.Solid.PowerManagement.PolicyAgent; member=HasInhibition
> uint32 4
>method call time=1722369877.281671 sender=:1.535 ->
>destination=org.kde.Solid.PowerManagement serial=304966
>path=/org/kde/Solid/PowerManagement/PolicyAgent;
>interface=org.kde.Solid.PowerManagement.PolicyAgent; member=ListInhibitions
>method call time=1722369877.281676 sender=:1.535 ->
>destination=org.kde.Solid.PowerManagement serial=304967
>path=/org/kde/Solid/PowerManagement/PolicyAgent;
>interface=org.kde.Solid.PowerManagement.PolicyAgent; member=ListInhibitions
In the case of Firefox without Flatpak (using org.freedesktop.ScreenSaver it
seems) I see this:
>>signal time=1722370014.376410 sender=org.freedesktop.DBus ->
>>destination=:1.1405 serial=4294967295 path=/org/freedesktop/DBus;
>>interface=org.freedesktop.DBus; member=NameAcquired
> string ":1.1405"
>signal time=1722370014.376428 sender=org.freedesktop.DBus ->
>destination=:1.1405 serial=4294967295 path=/org/freedesktop/DBus;
>interface=org.freedesktop.DBus; member=NameLost
> string ":1.1405"
>method call time=1722370017.317112 sender=:1.515 ->
>destination=org.kde.Solid.PowerManagement.PolicyAgent serial=4408
>path=/org/kde/Solid/PowerManagement/PolicyAgent;
>interface=org.kde.Solid.PowerManagement.PolicyAgent; member=AddInhibition
> uint32 4
> string "firefox"
> string "video-playing"
>signal time=1722370022.072171 sender=:1.545 -> destination=(null destination)
>serial=9486 path=/org/kde/Solid/PowerManagement/PolicyAgent;
>interface=org.kde.Solid.PowerManagement.PolicyAgent; member=InhibitionsChanged
> array [
> struct {
> string "firefox"
> string "video-playing"
> }
> ]
> array [
> ]
>method call time=1722370022.072447 sender=:1.515 ->
>destination=org.kde.Solid.
[plasmashell] [Bug 487118] The Power Management applet displays incorrect description of effects of org.freedesktop.portal.Inhibit
https://bugs.kde.org/show_bug.cgi?id=487118 --- Comment #4 from Emil --- (In reply to Wyatt Childers from comment #3) > (In reply to Emil from comment #1) > > Is this not a bug in kscreenlocker? > > > > If I'm not mistaken the logic which correctly detects the inhibition in the > > battery monitor is here: > > > > https://invent.kde.org/plasma/powerdevil/-/blob/master/applets/ > > batterymonitor/plugin/powermanagementcontrol.cpp > > > > But kscreensaver fails to detect that the screen has to be locked: > > > > https://invent.kde.org/plasma/kscreenlocker/-/blob/master/ > > powermanagement_inhibition.cpp > > Does the applet depend on kscreenlocker somehow? No, but if I understand the bug report correctly (and how I experience it) the applet does correctly indicate that screen locking *should* be blocked. Which means it's a bug in kscreenlocker that should also block with org.freedesktop.portal.Inhibit -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 244163] Dolphin doesn't refresh the folder list until I press F5
https://bugs.kde.org/show_bug.cgi?id=244163 Emil changed: What|Removed |Added CC||emil.vanh...@gmail.com --- Comment #43 from Emil --- Yes, still happens. (I think) it was gone for years, but recently it's happening again. Dolphin Version 21.04.0. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399705] New: cannot copy coordinates from map
https://bugs.kde.org/show_bug.cgi?id=399705 Bug ID: 399705 Summary: cannot copy coordinates from map Product: digikam Version: 5.9.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Geolocation-Editor Assignee: digikam-bugs-n...@kde.org Reporter: emil.w...@online.de Target Milestone: --- SUMMARY cannot copy coordinates from map STEPS TO REPRODUCE see digikam documentation 5.1.2 Edit Coordinates The coordinates can be set manually in the Details tab (see screenshot above). The location can be found and fixed iteratively with the displayed map. Move the mouse cursor to the region of interest, zoom in, adjust location, zoom in again, and so on until sufficient accuracy is achieved. Note that the zoom center will always be at the cursor position. Eventually you click with the right mouse button at the desired position and choose Copy Coordinates. Now you can go to the list of images below the map, select one or more images, click with the right mouse button on them and choose Paste Coordinates. The coordinates will then be displayed in the Latitude and Longitude fields to the right of the map. To save your changes you click the Apply button right under the DOP field. The coordinates can be set manually in the Details tab (see screenshot above). The location can be found and fixed iteratively with the displayed map. Move the mouse cursor to the region of interest, zoom in, adjust location, zoom in again, and so on until sufficient accuracy is achieved. Note that the zoom center will always be at the cursor position. Eventually you click with the right mouse button at the desired position and choose Copy Coordinates. Now you can go to the list of images below the map, select one or more images, click with the right mouse button on them and choose Paste Coordinates. The coordinates will then be displayed in the Latitude and Longitude fields to the right of the map. To save your changes you click the Apply button right under the DOP field. OBSERVED RESULT EXPECTED RESULT this works in 5.6.0 on KDE software opensuse 42.3 as below SOFTWARE VERSIONS on opensuse leap 42.3 (available in About System) KDE Plasma Version: 5.8.7 KDE Frameworks Version: 5.32.0 Qt Version: 5.6.2 ADDITIONAL INFORMATION same problem on opensuse leap 15.0 KDE Plasma Version: 5.12.5 KDE Frameworks Version: 5.45.0 Qt Version: 5.9.4 I've seen this problem many years ago. then it was fixed till now. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 393558] New: sync with gmail address book
https://bugs.kde.org/show_bug.cgi?id=393558 Bug ID: 393558 Summary: sync with gmail address book Product: kontact Version: 5.7.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: contacts Assignee: to...@kde.org Reporter: emil.gazaz...@scitoday.org CC: kdepim-b...@kde.org Target Milestone: --- Daar Developers, Kontact sync with gmail address book only first time but after same time cannot sync with gmail address book. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 393559] New: sync with gmail
https://bugs.kde.org/show_bug.cgi?id=393559 Bug ID: 393559 Summary: sync with gmail Product: kontact Version: 5.7.2 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: calendar Assignee: kdepim-b...@kde.org Reporter: emil.gazaz...@scitoday.org Target Milestone: --- Daar Developers, Kontact sync with gmail calendar only first time but after same time cannot sync with gmail caendar. -- You are receiving this mail because: You are watching all bug changes.
[kmail] [Bug 31360] kmail does not delete mail, spontaneously recovers deleted mail
https://bugs.kde.org/show_bug.cgi?id=31360 Emil changed: What|Removed |Added CC||emil.gazaz...@scitoday.org -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 393560] New: delete e-mail
https://bugs.kde.org/show_bug.cgi?id=393560 Bug ID: 393560 Summary: delete e-mail Product: kontact Version: 5.7.2 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: emil.gazaz...@scitoday.org Target Milestone: --- Dear Developers, I use filters to sort an email. sorted e-mail I redirect to the sub-folder. and in subfolder. I unnecessary e-mails was erase but some e-mail are not erased. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 393561] New: mail spend to much time for open e-mail
https://bugs.kde.org/show_bug.cgi?id=393561 Bug ID: 393561 Summary: mail spend to much time for open e-mail Product: kontact Version: 5.7.2 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: emil.gazaz...@scitoday.org Target Milestone: --- Dear Developers, kontact spend more time for open email and for this period of show me "please wait while the message is transferred". Connection is carried out according to the protocol of pop -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 393597] New: sync with google
https://bugs.kde.org/show_bug.cgi?id=393597 Bug ID: 393597 Summary: sync with google Product: kontact Version: 5.7.2 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: summary Assignee: kdepim-b...@kde.org Reporter: emil.gazaz...@scitoday.org Target Milestone: --- Dear Developers, PIM KMAIL after the first synchronization it is not synchronized The problem is solved only after the deletion (address book and calendars) and reconnect. Kubuntu 18.04 LTS Kontact 5.7.3 Linux (x86_64) release 4.15.0-20-generic -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 394039] New: Krita closes immediately when trying to change font
https://bugs.kde.org/show_bug.cgi?id=394039 Bug ID: 394039 Summary: Krita closes immediately when trying to change font Product: krita Version: 3.1.1 Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tool/Text Assignee: krita-bugs-n...@kde.org Reporter: emilko...@gmx.com Target Milestone: --- I was editing a painting in Krita and I added some text. Then I erased all default text and tried to change font. When I clicked next to the dropdown for fonts (the empty area) Krita closed immediately without any prompts. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 375148] New: KDE Neon does't include mtp-tools by default
https://bugs.kde.org/show_bug.cgi?id=375148 Bug ID: 375148 Summary: KDE Neon does't include mtp-tools by default Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: debiankondo...@hotmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Today I tried to copy files to my Samsung Galaxy Trend via USB cabel and mtp. But filesystem on phone was read-only. I googled for half an hour and found, that I must install mtp-tools and it solved my problem. Please include that package in distro. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 375148] KDE Neon does not include mtp-tools by default
https://bugs.kde.org/show_bug.cgi?id=375148 Emil Alasgarov changed: What|Removed |Added Summary|KDE Neon does't include |KDE Neon does not include |mtp-tools by default|mtp-tools by default -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395477] regression: folder view widget in panel = file list popup is too tiny
https://bugs.kde.org/show_bug.cgi?id=395477 Emil Sedgh changed: What|Removed |Added CC||emilse...@kde.org --- Comment #11 from Emil Sedgh --- Can confirm on 5.13.1 on Debian. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395477] regression: folder view widget in panel = file list popup is too tiny
https://bugs.kde.org/show_bug.cgi?id=395477 --- Comment #27 from Emil Sedgh --- Thank you Eike. Really appreciate the quick fix. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 386370] kwin randomly crashes when switching desktops
https://bugs.kde.org/show_bug.cgi?id=386370 Emil Jacobs changed: What|Removed |Added CC||emiljac...@gmail.com Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|DOWNSTREAM |--- --- Comment #10 from Emil Jacobs --- I'd like to confirm this bug in an updated instance of Fedora 27. The bug is intermittent and therefore not easily reproducible. Workaround so far is to not use virtual desktops... If logging is required, please request specific logging as I'm not a developer and can't easily judge what is and isn't relevant. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 395550] New: Extending "hints" with user provided url hints
https://bugs.kde.org/show_bug.cgi?id=395550
Bug ID: 395550
Summary: Extending "hints" with user provided url hints
Product: konsole
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: wishlist
Priority: NOR
Component: general
Assignee: konsole-de...@kde.org
Reporter: emilse...@kde.org
Target Milestone: ---
Konsole already has this amazing "URL Hints" feature. You wouldn't have to use
your mouse to open the URL's.
The idea is extending the same feature to it supports "hints" for any regular
expressions.
For example, I personally have to deal with a lot of uuid's during the day.
They generally look like this:
7b6436b2-005d-11e7-b9c2-f23c91b0d077
The idea is that I'd give this regular expression to Konsole:
/^[0-9a-f]{8}-[0-9a-f]{4}-[1-5][0-9a-f]{3}-[89AB][0-9a-f]{3}-[0-9a-f]{12}$/i
Then, every time I hold the "hint" keyboard shortcut, it would detect those
strings as well, and offer them to me to open them.
And instead of opening them in the browser, it would just copy them to the
clipboard.
Konsole can then provide a list of widely known regular expressions by default.
For example:
UUID
Hex Colors
ISO Date's
...
That'd make Konsole much much more keyboard friendly.
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 395550] Extending "hints" with user provided regular expressions
https://bugs.kde.org/show_bug.cgi?id=395550 Emil Sedgh changed: What|Removed |Added Summary|Extending "hints" with user |Extending "hints" with user |provided url hints |provided regular ||expressions -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 395550] Extending "hints" with user provided regular expressions
https://bugs.kde.org/show_bug.cgi?id=395550 --- Comment #1 from Emil Sedgh --- I actually looked into Konsole's source code. It seems that the basis for executing this feature is almost already there through filter chain. There is already an extendable Filter Chain which can take in classes for processing. I think the majority of the work is just adding the UI to manage the list of regular expressions. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 395550] Extending "hints" with user provided regular expressions
https://bugs.kde.org/show_bug.cgi?id=395550 --- Comment #3 from Emil Sedgh --- I have not done any cpp programming in many years, so I'd be struggling about it. However, I can try. But I'm not sure if I'll be successful at it. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 395550] Extending "hints" with user provided regular expressions
https://bugs.kde.org/show_bug.cgi?id=395550 --- Comment #5 from Emil Sedgh --- I will give it a try, but I probably am gonna fail ;) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 423790] New: Interface freezes when zooming in on the timeline
https://bugs.kde.org/show_bug.cgi?id=423790 Bug ID: 423790 Summary: Interface freezes when zooming in on the timeline Product: kdenlive Version: 20.04.1 Platform: unspecified OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: emil.wihlan...@outlook.com Target Milestone: --- SUMMARY When I zoom in on the timeline the application starts freezing and I see the spinning wheel cursor for a couple of seconds. If I try to do anything while zoomed in it freezes again and again until I zoom out. STEPS TO REPRODUCE 1. Open a project 2. Zoom in as far as possible om the timeline OBSERVED RESULT Application freezes for a couple of seconds EXPECTED RESULT It should perform equal regardless of zoom level of the timeline. SOFTWARE/OS VERSIONS Windows: 10.0.18363 Build 18363 (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.
[konsole] [Bug 407447] Global shortcut for toggling visibility of Konsole
https://bugs.kde.org/show_bug.cgi?id=407447 Emil Sedgh changed: What|Removed |Added CC||emilse...@kde.org --- Comment #2 from Emil Sedgh --- You can right-click on title bar and go to "More Actions" -> "Special Application Settings" -> "Arrangement & Access" -> "Shortcut". You can set any shortcut you want, like "F9". -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 407447] Global shortcut for toggling visibility of Konsole
https://bugs.kde.org/show_bug.cgi?id=407447 --- Comment #12 from Emil Sedgh --- Just as a side note, you _can_ have F9 as the shortcut for the app. You would have to type in F9 in the Shortcut window manually. I was a heavy user of Yakuake as well up to a few years ago. Everybody loves Yakuake and Quake style terminals. I realized the reason I love Yakuake is not because it opens from top-to-bottom with a nice animation. It's because I can assign it a quick global shortcut and my mind can remember it. So I used KWin's Special Application to give all popular apps their own dedicated shortcuts: F1 is Chrome F2 is Dolphin F3 is Kate F4 is Telegram F6 is KMail F7 is Slack F9 is Konsole ... After a few years of using this setup, I'm pretty much sure that it's the most productive workflow possible. All apps are always full screen and 1 key away. And that key is saved into my subconscious that I don't even have to think about it anymore. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491201] New: Plasma crash everytime after Nobara 40 update
https://bugs.kde.org/show_bug.cgi?id=491201 Bug ID: 491201 Summary: Plasma crash everytime after Nobara 40 update Classification: Plasma Product: plasmashell Version: 6.1.3 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: emil.pane...@gmail.com Target Milestone: 1.0 Application: plasmashell (6.1.3) Qt Version: 6.7.2 Frameworks Version: 6.4.0 Operating System: Linux 6.10.2-201.fsync.fc40.x86_64 x86_64 Windowing System: Wayland Distribution: Nobara Linux 40 (KDE Plasma) DrKonqi: 6.1.3 [CoredumpBackend] -- Information about the crash: Nobara 40 update, there is a loadins screan and on about 70% screen freezes and then windows plasmashell - Crash handler apears. The crash can be reproduced every time. -- Backtrace (Reduced): #5 QQmlRefPointer::QQmlRefPointer (this=0x7faf8d5fe578, other=...) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/qml/qml/ftw/qqmlrefcount_p.h:184 #6 QQmlType::QQmlType (this=this@entry=0x7faf8d5fe578) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/qml/qml/qqmltype.cpp:98 #7 0x7fafc760f9d5 in QV4::ResolvedTypeReference::type (this=) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/qml/jsruntime/qv4resolvedtypereference_p.h:46 #8 QQmlPropertyCacheCreator::propertyCacheForObject (this=this@entry=0x7faf8d5fe990, obj=obj@entry=0x7faf48297ac8, context=..., error=error@entry=0x7faf8d5fe660) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/qml/qml/qqmlpropertycachecreator_p.h:365 #9 0x7fafc761f109 in QQmlPropertyCacheCreator::buildMetaObjectRecursively (this=this@entry=0x7faf8d5fe990, objectIndex=1, context=..., isVMERequired=isVMERequired@entry=QQmlPropertyCacheCreator::VMEMetaObjectIsRequired::Maybe) at /usr/src/debug/qt6-qtdeclarative-6.7.2-2.fc40.x86_64/src/qml/qml/qqmlpropertycachecreator_p.h:279 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491201] Plasma crash everytime after Nobara 40 update
https://bugs.kde.org/show_bug.cgi?id=491201 --- Comment #1 from Emil Panecki --- Created attachment 172237 --> https://bugs.kde.org/attachment.cgi?id=172237&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399604] New: Discover chrashed when opening chrome-.deb.
https://bugs.kde.org/show_bug.cgi?id=399604 Bug ID: 399604 Summary: Discover chrashed when opening chrome-.deb. Product: Discover Version: 5.14.0 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: m...@emilharder.dk Target Milestone: --- Application: plasma-discover (5.14.0) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.15.0-36-generic x86_64 Distribution: KDE neon User Edition 5.14 -- Information about the crash: - Openened .deb for the Chrome browser, downloaded from firefox. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f94b82a5c80 (LWP 31538))] Thread 11 (Thread 0x7f94652d7700 (LWP 31559)): #0 0x7f94b383e839 in syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f94b3f40564 in QSemaphore::acquire(int) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f94b4147d70 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f94b171121b in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #4 0x7f94b17ab0fd in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #5 0x7f94b4147ad5 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f94b1706e59 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #7 0x7f94b17076f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #8 0x7f94b4147ad5 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f94b17a4d2f in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #10 0x7f94b17a1850 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #11 0x7f94b17a1be5 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #12 0x7f94b17862e1 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #13 0x7f94b4147ad5 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f94b174eb73 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #15 0x7f94b174ec24 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #16 0x7f94b17624e1 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #17 0x7f94b572fe8c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f94b573745f in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f94b4118ab8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f94b41736dd in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f94adda6287 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7f94adda64c0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7f94adda654c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7f94b4172a9b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f94b4116dea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f94b3f41b8a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7f94b3f4caab in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7f94aff426db in start_thread (arg=0x7f94652d7700) at pthread_create.c:463 #29 0x7f94b384488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f947d773700 (LWP 31550)): #0 0x7f94aff48ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f947d772c30, expected=0, futex_word=0x7f9468005554) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f94aff48ed9 in __pthread_cond_wait_common (abstime=0x7f947d772d00, mutex=0x7f9468005500, cond=0x7f9468005528) at pthread_cond_wait.c:533 #2 0x7f94aff48ed9 in __pthread_cond_timedwait (cond=0x7f9468005528, mutex=0x7f9468005500, abstime=0x7f947d772d00) at pthread_cond_wait.c:667 #3 0x7f94b3f4d850 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f94b3f4425d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f94b3f4caab in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f94aff426db in start_thread (arg=0x7f947d773700) at pthread_create.c:463 #7 0x7f94b384488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f947df74700 (LWP 31549)): #0 0x7f94b3837bf9 in __GI___poll (fds=0x7f946800abb0, nfds=1, timeout=14796) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f94adda6439 in () at /usr/lib/x
[kmenuedit] [Bug 400522] New: Menu editor crashes when changing icon source for submenu
https://bugs.kde.org/show_bug.cgi?id=400522 Bug ID: 400522 Summary: Menu editor crashes when changing icon source for submenu Product: kmenuedit Version: 5.14.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: m...@emilharder.dk Target Milestone: --- Application: kmenuedit (5.14.2) Qt Version: 5.11.2 Frameworks Version: 5.51.0 Operating System: Linux 4.15.0-38-generic x86_64 Distribution: KDE neon User Edition 5.14 -- Information about the crash: - What I was doing when the application crashed: Opened the drop down menu, to change icon source from Applications to something else. The crash can be reproduced every time. -- Backtrace: Application: KDE Menu Editor (kmenuedit), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8fa0c54cc0 (LWP 24931))] Thread 3 (Thread 0x7f8f8561c700 (LWP 24933)): #0 0x7f8fa055b0b4 in __GI___libc_read (fd=7, buf=0x7f8f8561bb20, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f8f95c87a00 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8f95c42f27 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8f95c433e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f8f95c4354c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f8f9c41304b in QEventDispatcherGlib::processEvents (this=0x7f8f8b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f8f9c3b730a in QEventLoop::exec (this=this@entry=0x7f8f8561bd30, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #7 0x7f8f9c1e2bba in QThread::exec (this=) at thread/qthread.cpp:525 #8 0x7f8f9dae8e45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7f8f9c1edadb in QThreadPrivate::start (arg=0x7f8f9dd60d60) at thread/qthread_unix.cpp:367 #10 0x7f8f97dde6db in start_thread (arg=0x7f8f8561c700) at pthread_create.c:463 #11 0x7f8fa056c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f8f8cef3700 (LWP 24932)): #0 0x7f8fa055fbf9 in __GI___poll (fds=0x7f8f8cef2c68, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f8f94d1d747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f8f94d1f36a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f8f8f889ed9 in QXcbEventReader::run (this=0x56327c16e400) at qxcbconnection.cpp:1391 #4 0x7f8f9c1edadb in QThreadPrivate::start (arg=0x56327c16e400) at thread/qthread_unix.cpp:367 #5 0x7f8f97dde6db in start_thread (arg=0x7f8f8cef3700) at pthread_create.c:463 #6 0x7f8fa056c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f8fa0c54cc0 (LWP 24931)): [KCrash Handler] #6 QString::mid (this=this@entry=0x56327ebbb4a8, position=38, n=n@entry=-1) at tools/qstring.cpp:4769 #7 0x7f8f9f7698d9 in sortByFileName (path1=..., path2=...) at ./src/kicondialog.cpp:419 #8 0x7f8f9f76d041 in __gnu_cxx::__ops::_Val_comp_iter::operator()::iterator> (__it=..., __val=..., this=) at /usr/include/c++/7/bits/predefined_ops.h:215 #9 std::__unguarded_linear_insert::iterator, __gnu_cxx::__ops::_Val_comp_iter > (__last=..., __comp=__comp@entry=...) at /usr/include/c++/7/bits/stl_algo.h:1828 #10 0x7f8f9f76b8be in std::__unguarded_insertion_sort::iterator, __gnu_cxx::__ops::_Iter_comp_iter > (__comp=..., __last=..., __first=...) at /usr/include/c++/7/bits/stl_algo.h:1867 #11 std::__final_insertion_sort::iterator, __gnu_cxx::__ops::_Iter_comp_iter > (__comp=..., __last=..., __first=...) at /usr/include/c++/7/bits/stl_algo.h:1886 #12 std::__sort::iterator, __gnu_cxx::__ops::_Iter_comp_iter > (__comp=..., __last=..., __first=...) at /usr/include/c++/7/bits/stl_algo.h:1971 #13 std::sort::iterator, bool (*)(QString const&, QString const&)> (__comp=0x7f8f9f769860 , __last=..., __first=...) at /usr/include/c++/7/bits/stl_algo.h:4868 #14 KIconDialog::KIconDialogPrivate::showIcons (this=0x56327c5288d0) at ./src/kicondialog.cpp:447 #15 0x7f8f9c3e8075 in QMetaObject::activate (sender=sender@entry=0x56327c529bc0, signalOffset=, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffdeb0ff9d0) at kernel/qobject.cpp:3771 #16 0x7f8f9c3e8747 in QMetaObject::activate (sender=sender@entry=0x56327c529bc0, m=m@entry=0x7f8f9d818020 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffdeb0ff9d0) at kernel/qobject.cpp:3633 #17 0x7f8f9d23dfb1 in QComboBox::activated (this=this@entry=0x56327c529bc0, _t1=) at .moc/moc_qcombobox.cpp:477 #18 0x7f8f9d23fe4e in QComboBoxPrivate::emitActivated (this=this@entry=0x56327c529ed0, ind
[plasmashell] [Bug 395477] regression: folder view widget in panel = file list popup is too tiny
https://bugs.kde.org/show_bug.cgi?id=395477 Emil Sedgh changed: What|Removed |Added CC||emilse...@kde.org --- Comment #11 from Emil Sedgh --- Can confirm on 5.13.1 on Debian. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395477] regression: folder view widget in panel = file list popup is too tiny
https://bugs.kde.org/show_bug.cgi?id=395477 --- Comment #27 from Emil Sedgh --- Thank you Eike. Really appreciate the quick fix. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 386370] kwin randomly crashes when switching desktops
https://bugs.kde.org/show_bug.cgi?id=386370 Emil Jacobs changed: What|Removed |Added CC||emiljac...@gmail.com Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|DOWNSTREAM |--- --- Comment #10 from Emil Jacobs --- I'd like to confirm this bug in an updated instance of Fedora 27. The bug is intermittent and therefore not easily reproducible. Workaround so far is to not use virtual desktops... If logging is required, please request specific logging as I'm not a developer and can't easily judge what is and isn't relevant. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 395550] New: Extending "hints" with user provided url hints
https://bugs.kde.org/show_bug.cgi?id=395550
Bug ID: 395550
Summary: Extending "hints" with user provided url hints
Product: konsole
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: wishlist
Priority: NOR
Component: general
Assignee: konsole-de...@kde.org
Reporter: emilse...@kde.org
Target Milestone: ---
Konsole already has this amazing "URL Hints" feature. You wouldn't have to use
your mouse to open the URL's.
The idea is extending the same feature to it supports "hints" for any regular
expressions.
For example, I personally have to deal with a lot of uuid's during the day.
They generally look like this:
7b6436b2-005d-11e7-b9c2-f23c91b0d077
The idea is that I'd give this regular expression to Konsole:
/^[0-9a-f]{8}-[0-9a-f]{4}-[1-5][0-9a-f]{3}-[89AB][0-9a-f]{3}-[0-9a-f]{12}$/i
Then, every time I hold the "hint" keyboard shortcut, it would detect those
strings as well, and offer them to me to open them.
And instead of opening them in the browser, it would just copy them to the
clipboard.
Konsole can then provide a list of widely known regular expressions by default.
For example:
UUID
Hex Colors
ISO Date's
...
That'd make Konsole much much more keyboard friendly.
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 395550] Extending "hints" with user provided regular expressions
https://bugs.kde.org/show_bug.cgi?id=395550 Emil Sedgh changed: What|Removed |Added Summary|Extending "hints" with user |Extending "hints" with user |provided url hints |provided regular ||expressions -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 395550] Extending "hints" with user provided regular expressions
https://bugs.kde.org/show_bug.cgi?id=395550 --- Comment #1 from Emil Sedgh --- I actually looked into Konsole's source code. It seems that the basis for executing this feature is almost already there through filter chain. There is already an extendable Filter Chain which can take in classes for processing. I think the majority of the work is just adding the UI to manage the list of regular expressions. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 395550] Extending "hints" with user provided regular expressions
https://bugs.kde.org/show_bug.cgi?id=395550 --- Comment #3 from Emil Sedgh --- I have not done any cpp programming in many years, so I'd be struggling about it. However, I can try. But I'm not sure if I'll be successful at it. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 395550] Extending "hints" with user provided regular expressions
https://bugs.kde.org/show_bug.cgi?id=395550 --- Comment #5 from Emil Sedgh --- I will give it a try, but I probably am gonna fail ;) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 375148] New: KDE Neon does't include mtp-tools by default
https://bugs.kde.org/show_bug.cgi?id=375148 Bug ID: 375148 Summary: KDE Neon does't include mtp-tools by default Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: debiankondo...@hotmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Today I tried to copy files to my Samsung Galaxy Trend via USB cabel and mtp. But filesystem on phone was read-only. I googled for half an hour and found, that I must install mtp-tools and it solved my problem. Please include that package in distro. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 375148] KDE Neon does not include mtp-tools by default
https://bugs.kde.org/show_bug.cgi?id=375148 Emil Alasgarov changed: What|Removed |Added Summary|KDE Neon does't include |KDE Neon does not include |mtp-tools by default|mtp-tools by default -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363284] [XP-PEN][UGEE] Krita connects strokes with previous ones
https://bugs.kde.org/show_bug.cgi?id=363284 Emil Lehmann Friis changed: What|Removed |Added CC||emillehmannfr...@hotmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416646] New: Inconsistency between display of 24h and 12h format.
https://bugs.kde.org/show_bug.cgi?id=416646 Bug ID: 416646 Summary: Inconsistency between display of 24h and 12h format. Product: plasmashell Version: 5.17.5 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: emiltangkristen...@gmail.com Target Milestone: 1.0 Created attachment 125326 --> https://bugs.kde.org/attachment.cgi?id=125326&action=edit Comparison between 12h and 24 format. SUMMARY The 12 hour clock display format was clearly made to include a little bit of spacing on both the right and left side to avoid the text being too close to the panel edge or other panel elements. Apparently there is no such thing for 24h format, which creates problems with readability and is overall inconsistent. STEPS TO REPRODUCE 1. Add the Digital Clock Applet and lock panel. 2. Right clock applet and select configure. 3. Switch the time displat to 12h. 4. Take a screenshot. 5. Do the same for the 24h format. 6. Compare results. OBSERVED RESULT The 12h format has a nice spacing on both the left and right side of the clock text. The 24h format has 0 spacing on the right and left side. EXPECTED RESULT Both format should have the same spacing. SOFTWARE/OS VERSIONS OS: Arch Linux KDE Plasma Version: 5.17.5 Qt Version: 5.14.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416646] Inconsistency between spacing in 24h and 12h format.
https://bugs.kde.org/show_bug.cgi?id=416646 Emil Tang Kristensen changed: What|Removed |Added Summary|Inconsistency between |Inconsistency between |display of 24h and 12h |spacing in 24h and 12h |format. |format. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416646] Inconsistency between spacing in 24h and 12h format.
https://bugs.kde.org/show_bug.cgi?id=416646 --- Comment #2 from Emil Tang Kristensen --- Cheers, thanks for all the hard work :). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363284] [XP-PEN][UGEE] Krita connects strokes with previous ones
https://bugs.kde.org/show_bug.cgi?id=363284 Emil Lehmann Friis changed: What|Removed |Added CC||emillehmannfr...@hotmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 347474] bottom of lines with Chinese characters are not displayed correctly.
https://bugs.kde.org/show_bug.cgi?id=347474 --- Comment #2 from Emil --- The problem also seems to only occur with monospaced fonts. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 347474] bottom of lines with Chinese characters are not displayed correctly.
https://bugs.kde.org/show_bug.cgi?id=347474 --- Comment #2 from Emil --- The problem also seems to only occur with monospaced fonts. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 289609] KMail doesnt know an email has been downloaded
https://bugs.kde.org/show_bug.cgi?id=289609 Emil Sedgh changed: What|Removed |Added Resolution|WAITINGFORINFO |INVALID Status|NEEDSINFO |RESOLVED --- Comment #2 from Emil Sedgh --- Hi Denis. I'm the original reported and I haven't seen this happen for a while now. I think its safe to close it. I'm marking it as INVALID. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 363362] New: crash when using configuration
https://bugs.kde.org/show_bug.cgi?id=363362 Bug ID: 363362 Summary: crash when using configuration Product: digikam Version: 4.4.0 Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: setup Assignee: digikam-de...@kde.org Reporter: n...@nobswolf.info After choosing menu "configure digikam" the dialog starts up and looks ok, but after the first clicks, the entire application freezes. Reproducible: Always Steps to Reproduce: 1. start digikam 2. click menu-entry "configure digikam" 3. click something in the dialog-box Actual Results: application freezes, sometimes shows a single reaction after a minute or so, but never recovers Expected Results: normal operations and ability to use the configuration dialog standard Debian stable application 64 Bit multi-core Intel system MariaDB XFCE Desktop this happens on the console: Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QString) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QString) Got bus address: "unix:abstract=/tmp/dbus-QWhAl5MZWw,guid=b930101fe7404a1657f64adb5730b810" Connected to accessibility bus at: "unix:abstract=/tmp/dbus-QWhAl5MZWw,guid=b930101fe7404a1657f64adb5730b810" Registered DEC: true Registered event listener change listener: true QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" FIXME: handle dialog end. QSpiAccessible::accessibleEvent not handled: "6" obj: KMenu(0x2b67d40, name = "settings") "settings" QSpiAccessible::accessibleEvent not handled: "7" obj: KMenu(0x2b67d40, name = "settings") "settings" QLayout: Cannot add null widget to QVBoxLayout/ QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" FIXME: handle dialog start. QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 363362] crash when using configuration
https://bugs.kde.org/show_bug.cgi?id=363362 --- Comment #2 from Emil Obermayr --- Can you tell me a Debian Repository where I can get the 4.14? GDB Backtrace after the dialog hangs: [Thread 0x7fffab7fc700 (LWP 22106) exited] [Thread 0x7fff48ff9700 (LWP 22133) exited] [Thread 0x7fffb8bc9700 (LWP 22104) exited] [Thread 0x7fff437fe700 (LWP 22134) exited] ^C Program received signal SIGINT, Interrupt. 0x71d86e53 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 (gdb) bt #0 0x71d86e53 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #1 0x71d6ec3a in QObjectPrivate::~QObjectPrivate() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x71d709e4 in QObject::~QObject() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #3 0x71d74a09 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x71d6fce3 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7277548c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #6 0x7277bfa8 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #7 0x734ed1aa in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #8 0x71d5671d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x71d8838b in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x71d853c1 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #11 0x7fffe935ec5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7fffe935ef48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7fffe935effc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x71d85d1d in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #15 0x72819f96 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #16 0x71d55271 in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #17 0x71d555d5 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #18 0x72c4ae7c in QDialog::exec() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #19 0x004e10c5 in ?? () #20 0x005bc326 in ?? () #21 0x71d6b71c in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #22 0x7276ece2 in QAction::triggered(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #23 0x72770867 in QAction::activate(QAction::ActionEvent) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #24 0x72bc569d in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #25 0x72bca069 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #26 0x735b5013 in KMenu::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libkdeui.so.5 #27 0x727c8748 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #28 0x72bce04b in QMenu::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #29 0x7277548c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #30 0x7277c10f in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #31 0x734ed1aa in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #32 0x71d5671d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #33 0x7277b76f in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #34 0x727f27ca in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #35 0x727f0e2c in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #36 0x72819ed2 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #37 0x7fffe935ec5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #38 0x7fffe935ef48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #39 0x7fffe935effc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #40 0x71d85d1d in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #41 0x72819f96 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #42 0x71d55271 in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #43 0x71d555d5 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #44 0x71d5b059 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #45 0x00495be6 in ?? () #46 0x70da7b45 in __libc_start_main (main=0x494aa0, argc=1,
[digikam] [Bug 363362] crash when using configuration
https://bugs.kde.org/show_bug.cgi?id=363362 --- Comment #4 from Emil Obermayr --- I got 4.14 from the Jessie Backports. Configuration works now. Thanks for the hint. I will use the debug package when I find the next bug ;-) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 367953] New: Global shortcuts not working on modified keys
https://bugs.kde.org/show_bug.cgi?id=367953 Bug ID: 367953 Summary: Global shortcuts not working on modified keys Product: frameworks-kglobalaccel Version: unspecified Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mgraess...@kde.org Reporter: emilse...@kde.org CC: kdelibs-b...@kde.org In KDE4, I used to make 'Caps Lock' act like Numlock. Then numlock was set to enable a global shortcut key. This doesn't work in Plasma 5 anymore. Reproducible: Always Steps to Reproduce: 1. Open up System Settings -> Input Devices -> Keyboard -> Advanced -> Caps Lock Key behavior 2. Open it up and enable 'Make Caps Lock key an additional Num Lock 3. Now go to any app and define a global shortcut. Press Caps Lock as the shortcut key. Num Lock is properly defined. 4. Save it 5. Press Caps Lock to trigger the shortcut Actual Results: Nothing happens Expected Results: The caps lock key, which is acting like a numlock, should trigger the action. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 367953] Global shortcuts not working on modified keys
https://bugs.kde.org/show_bug.cgi?id=367953 --- Comment #2 from Emil Sedgh --- Hey Martin. I'm using Debian packages. Qt 5.6.1 kglobalacces 5.23.0 I used to build KDE manually until a few months ago and this issue was always there (beginning from KF5 times) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 367953] Global shortcuts not working on modified keys
https://bugs.kde.org/show_bug.cgi?id=367953 --- Comment #4 from Emil Sedgh --- Killing kglobalaccel5 and restarting it does fix the issue. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 351198] 'Numlock' is not trigger-able
https://bugs.kde.org/show_bug.cgi?id=351198 --- Comment #19 from Emil Sedgh --- *** Bug 367953 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 367953] Global shortcuts not working on modified keys
https://bugs.kde.org/show_bug.cgi?id=367953 Emil Sedgh changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #6 from Emil Sedgh --- I'm such a fool. I had this reported already (#351198) exactly one year ago. And that was marked as a duplicate of #350816 which is the bug you are referring to. Thanks again and sorry for the time you had to waste on this. *** This bug has been marked as a duplicate of bug 351198 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 363362] New: crash when using configuration
https://bugs.kde.org/show_bug.cgi?id=363362 Bug ID: 363362 Summary: crash when using configuration Product: digikam Version: 4.4.0 Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: setup Assignee: digikam-de...@kde.org Reporter: n...@nobswolf.info After choosing menu "configure digikam" the dialog starts up and looks ok, but after the first clicks, the entire application freezes. Reproducible: Always Steps to Reproduce: 1. start digikam 2. click menu-entry "configure digikam" 3. click something in the dialog-box Actual Results: application freezes, sometimes shows a single reaction after a minute or so, but never recovers Expected Results: normal operations and ability to use the configuration dialog standard Debian stable application 64 Bit multi-core Intel system MariaDB XFCE Desktop this happens on the console: Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QString) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QString) Got bus address: "unix:abstract=/tmp/dbus-QWhAl5MZWw,guid=b930101fe7404a1657f64adb5730b810" Connected to accessibility bus at: "unix:abstract=/tmp/dbus-QWhAl5MZWw,guid=b930101fe7404a1657f64adb5730b810" Registered DEC: true Registered event listener change listener: true QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" FIXME: handle dialog end. QSpiAccessible::accessibleEvent not handled: "6" obj: KMenu(0x2b67d40, name = "settings") "settings" QSpiAccessible::accessibleEvent not handled: "7" obj: KMenu(0x2b67d40, name = "settings") "settings" QLayout: Cannot add null widget to QVBoxLayout/ QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" FIXME: handle dialog start. QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 363362] crash when using configuration
https://bugs.kde.org/show_bug.cgi?id=363362 --- Comment #2 from Emil Obermayr --- Can you tell me a Debian Repository where I can get the 4.14? GDB Backtrace after the dialog hangs: [Thread 0x7fffab7fc700 (LWP 22106) exited] [Thread 0x7fff48ff9700 (LWP 22133) exited] [Thread 0x7fffb8bc9700 (LWP 22104) exited] [Thread 0x7fff437fe700 (LWP 22134) exited] ^C Program received signal SIGINT, Interrupt. 0x71d86e53 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 (gdb) bt #0 0x71d86e53 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #1 0x71d6ec3a in QObjectPrivate::~QObjectPrivate() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x71d709e4 in QObject::~QObject() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #3 0x71d74a09 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x71d6fce3 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7277548c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #6 0x7277bfa8 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #7 0x734ed1aa in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #8 0x71d5671d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x71d8838b in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x71d853c1 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #11 0x7fffe935ec5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7fffe935ef48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7fffe935effc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x71d85d1d in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #15 0x72819f96 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #16 0x71d55271 in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #17 0x71d555d5 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #18 0x72c4ae7c in QDialog::exec() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #19 0x004e10c5 in ?? () #20 0x005bc326 in ?? () #21 0x71d6b71c in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #22 0x7276ece2 in QAction::triggered(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #23 0x72770867 in QAction::activate(QAction::ActionEvent) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #24 0x72bc569d in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #25 0x72bca069 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #26 0x735b5013 in KMenu::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libkdeui.so.5 #27 0x727c8748 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #28 0x72bce04b in QMenu::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #29 0x7277548c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #30 0x7277c10f in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #31 0x734ed1aa in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #32 0x71d5671d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #33 0x7277b76f in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #34 0x727f27ca in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #35 0x727f0e2c in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #36 0x72819ed2 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #37 0x7fffe935ec5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #38 0x7fffe935ef48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #39 0x7fffe935effc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #40 0x71d85d1d in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #41 0x72819f96 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #42 0x71d55271 in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #43 0x71d555d5 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #44 0x71d5b059 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #45 0x00495be6 in ?? () #46 0x70da7b45 in __libc_start_main (main=0x494aa0, argc=1,
[digikam] [Bug 363362] crash when using configuration
https://bugs.kde.org/show_bug.cgi?id=363362 --- Comment #4 from Emil Obermayr --- I got 4.14 from the Jessie Backports. Configuration works now. Thanks for the hint. I will use the debug package when I find the next bug ;-) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 289609] KMail doesnt know an email has been downloaded
https://bugs.kde.org/show_bug.cgi?id=289609 Emil Sedgh changed: What|Removed |Added Resolution|WAITINGFORINFO |INVALID Status|NEEDSINFO |RESOLVED --- Comment #2 from Emil Sedgh --- Hi Denis. I'm the original reported and I haven't seen this happen for a while now. I think its safe to close it. I'm marking it as INVALID. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 367953] New: Global shortcuts not working on modified keys
https://bugs.kde.org/show_bug.cgi?id=367953 Bug ID: 367953 Summary: Global shortcuts not working on modified keys Product: frameworks-kglobalaccel Version: unspecified Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mgraess...@kde.org Reporter: emilse...@kde.org CC: kdelibs-b...@kde.org In KDE4, I used to make 'Caps Lock' act like Numlock. Then numlock was set to enable a global shortcut key. This doesn't work in Plasma 5 anymore. Reproducible: Always Steps to Reproduce: 1. Open up System Settings -> Input Devices -> Keyboard -> Advanced -> Caps Lock Key behavior 2. Open it up and enable 'Make Caps Lock key an additional Num Lock 3. Now go to any app and define a global shortcut. Press Caps Lock as the shortcut key. Num Lock is properly defined. 4. Save it 5. Press Caps Lock to trigger the shortcut Actual Results: Nothing happens Expected Results: The caps lock key, which is acting like a numlock, should trigger the action. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 367953] Global shortcuts not working on modified keys
https://bugs.kde.org/show_bug.cgi?id=367953 --- Comment #2 from Emil Sedgh --- Hey Martin. I'm using Debian packages. Qt 5.6.1 kglobalacces 5.23.0 I used to build KDE manually until a few months ago and this issue was always there (beginning from KF5 times) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 367953] Global shortcuts not working on modified keys
https://bugs.kde.org/show_bug.cgi?id=367953 --- Comment #4 from Emil Sedgh --- Killing kglobalaccel5 and restarting it does fix the issue. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 351198] 'Numlock' is not trigger-able
https://bugs.kde.org/show_bug.cgi?id=351198 --- Comment #19 from Emil Sedgh --- *** Bug 367953 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 367953] Global shortcuts not working on modified keys
https://bugs.kde.org/show_bug.cgi?id=367953 Emil Sedgh changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #6 from Emil Sedgh --- I'm such a fool. I had this reported already (#351198) exactly one year ago. And that was marked as a duplicate of #350816 which is the bug you are referring to. Thanks again and sorry for the time you had to waste on this. *** This bug has been marked as a duplicate of bug 351198 *** -- You are receiving this mail because: You are watching all bug changes.
