[kwin] [Bug 464196] Drag and drop in GTK apps: 'drag-motion' is triggered when GTK window regains focus
https://bugs.kde.org/show_bug.cgi?id=464196 --- Comment #5 from sedrubal --- Same for me. This one is really annoying. The only solution I found is to close and reopen the application that gets those spurious DnD events, which is most of the time Firefox. Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Graphics Platform: Wayland Gtk: 3.24.38 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464196] Drag and drop in GTK apps: 'drag-motion' is triggered when GTK window regains focus
https://bugs.kde.org/show_bug.cgi?id=464196 sedrubal changed: What|Removed |Added CC||k...@sedrubal.de -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 445487] Feature: qrcode support in captured image
https://bugs.kde.org/show_bug.cgi?id=445487 sedrubal changed: What|Removed |Added CC||k...@sedrubal.de -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 458718] Only first word of Metadata is written to file
https://bugs.kde.org/show_bug.cgi?id=458718 sedrubal changed: What|Removed |Added CC||k...@sedrubal.de --- Comment #4 from sedrubal --- Thank you very much! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 458718] New: Only first word of Metadata is written to file
https://bugs.kde.org/show_bug.cgi?id=458718 Bug ID: 458718 Summary: Only first word of Metadata is written to file Product: kdenlive Version: 22.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: k...@sedrubal.de Target Milestone: --- SUMMARY When you render a project and enable "Export metadata" (after ticking "More options" in the "Rendering" dialogue and if your project title consists of multiple words separated by a space, only the first word will be written to the metadata of the file. STEPS TO REPRODUCE 1. Create a project with the title "Example title" 2. When you render the project click on "More options" > "Export metadata" 3. I'm not sure if it is important but I'm using a custom preset using mp4 container and libx264 4. Render the project 5. Inspect the rendered file with exiftool OBSERVED RESULT The title will be "Example" EXPECTED RESULT The title should be "Example title" SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION Most likely the generated command should quote the project title. The generated command looks like this: > [...] meta.attr.title.markup=Example title I assume it might be fixed if it looks like this: > [...] meta.attr.title.markup='Example title' -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 450211] New: Add option to copy target of symlink when copying to filesystem that does not support symlinks
https://bugs.kde.org/show_bug.cgi?id=450211 Bug ID: 450211 Summary: Add option to copy target of symlink when copying to filesystem that does not support symlinks Product: dolphin Version: 21.12.2 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: k...@sedrubal.de CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When you try to copy a symlink to a filesystem that does not support symlinks (e.g., FAT), a information message appears "Could not create symlink "". The destination filesystem (FAT) doesn't support symlinks. You can choose between "Skip"*, "Skip All"* and "Cancel" (* skip of course only in bulk copy mode). It would be helpful to add an option "Copy symlink target" or "Make hard copy" or something like that, to resolve the symlink and copy the target of it to the file system. In my scenario, I'm copying files to an external portable USB stick. A symlink makes no sense there and the message is indeed correct of course. However, I want to use the stick to plug it into a printer and print the files (i.e. the files the symlinks are pointing to). STEPS TO REPRODUCE 1. Create a partition with e.g. FAT32 / FAT16 / vfat / ... 2. Create a local symlink to any other file on the local file system 3. Mount the FAT/... partition 4. Try to copy the symlink (via drag and drop) to the FAT/... partition OBSERVED RESULT The (correct) information message appears. EXPECTED RESULT I did expect that, but I'd like to have an option to resolve the symlinks and copy the target files to the external partition. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 449898] "setFcc: collection invalid" after answering an e-mail
https://bugs.kde.org/show_bug.cgi?id=449898 sedrubal changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #6 from sedrubal --- Yes, the update also fixes it for me. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 449898] "setFcc: collection invalid" after answering an e-mail
https://bugs.kde.org/show_bug.cgi?id=449898 sedrubal changed: What|Removed |Added Summary|"setFcc: collection |"setFcc: collection |invalid" after composing|invalid" after answering an |new e-mail |e-mail -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 449898] "setFcc: collection invalid" after composing new e-mail
https://bugs.kde.org/show_bug.cgi?id=449898 --- Comment #3 from sedrubal --- (In reply to Hauke from comment #2) > But for me answering any mails (not only mail with an mail-adress in the > message body) causes this crash. Can confirm, that this bug is caused by answering any mail. > Removing all files in ~./local/share/kmail2/autosave/ solved the startup > issue and KMail starts normally. Answering a mail results in a crash again. Can confirm that, too. Thanks for the "fix". -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 449898] "setFcc: collection invalid" after composing new e-mail
https://bugs.kde.org/show_bug.cgi?id=449898 sedrubal changed: What|Removed |Added Summary|"setFcc: collection |"setFcc: collection |invalid" after clicking on |invalid" after composing |mail address in e-mail |new e-mail |message body| -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 449898] "setFcc: collection invalid" after clicking on mail address in e-mail message body
https://bugs.kde.org/show_bug.cgi?id=449898 sedrubal changed: What|Removed |Added CC||k...@sedrubal.de --- Comment #1 from sedrubal --- The original crash is described in Bug 449891. This bug is about the corrupt data. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 449891] kmail crashes on startup
https://bugs.kde.org/show_bug.cgi?id=449891 --- Comment #1 from sedrubal --- Created attachment 146507 --> https://bugs.kde.org/attachment.cgi?id=146507=edit New crash information added by DrKonqi kmail (5.19.2 (21.12.2)) using Qt 5.15.2 - What I was doing when the application crashed: This issue seems to be the cause of the crash described in Bug 449898, which results in corrupt data. -- Backtrace (Reduced): #4 std::__atomic_base::load(std::memory_order) const (__m=std::memory_order_relaxed, this=0x8) at /usr/include/qt/QtCore/qrefcount.h:54 #5 QAtomicOps::loadRelaxed(std::atomic const&) (_q_value=...) at /usr/include/qt/QtCore/qatomic_cxx11.h:239 #6 QBasicAtomicInteger::loadRelaxed() const (this=0x8) at /usr/include/qt/QtCore/qbasicatomic.h:107 [...] #8 QString::QString(QString const&) (this=0x7ffd48a7db20, other=..., this=, other=) at /usr/include/qt/QtCore/qstring.h:1094 #9 0x7fcde918eb86 in std::_Head_base<3ul, QString, false>::_Head_base(QString const&) (__h=..., this=0x7ffd48a7db20, this=, __h=) at /usr/include/c++/11.1.0/tuple:182 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 449891] kmail crashes on startup
https://bugs.kde.org/show_bug.cgi?id=449891 sedrubal changed: What|Removed |Added CC||k...@sedrubal.de -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 449898] New: "setFcc: collection invalid" after clicking on mail address in e-mail message body
https://bugs.kde.org/show_bug.cgi?id=449898 Bug ID: 449898 Summary: "setFcc: collection invalid" after clicking on mail address in e-mail message body Product: kmail2 Version: 5.19.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: k...@sedrubal.de Target Milestone: --- SUMMARY kmail crashes when I click on a mail address in the body of an email. Unfortunately it seems, that some data gets corrupt during the crash and I am not able to start kmail again. I manually deleted some kmail / akonadi related files without success. But I could create a backup using PIM Data Exporter. After deleting everything I found in ~/.local/share and ~/.config/ and restored the backup, it worked again. STEPS TO REPRODUCE 1. Open a mail with an email address in the message body 2. click on the email address OBSERVED RESULT kmail freezes / crashes. When I close it, it does not start again. Instead it is crashing with the message EXPECTED RESULT I want to write a new email to the address, I clicked on. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.24 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This is the log when I try to start kmail: $ kmail Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed org.kde.pim.kmail: setFcc: collection invalid "" *** KMail got signal 11 (Exiting) *** Dead letters dumped. 19 -- exe=/usr/bin/kmail 13 -- platform=xcb 11 -- display=:1 14 -- appname=kmail 17 -- apppath=/usr/bin 10 -- signal=11 11 -- pid=183353 28 -- appversion=5.19.2 (21.12.2) 18 -- programname=KMail 31 -- bugaddress=sub...@bugs.kde.org 12 -- startupid=0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449541] Quick tile action via shortcut de-maximizes the window without tiling as a first action
https://bugs.kde.org/show_bug.cgi?id=449541 sedrubal changed: What|Removed |Added CC||k...@sedrubal.de -- You are receiving this mail because: You are watching all bug changes.
[parley] [Bug 448922] New: Crash when opening word list editor
https://bugs.kde.org/show_bug.cgi?id=448922 Bug ID: 448922 Summary: Crash when opening word list editor Product: parley Version: 21.12.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: editor Assignee: parley-bugs-n...@kde.org Reporter: k...@sedrubal.de Target Milestone: --- SUMMARY Parley crashes as soon as a word collection is opened (I think in the editor). It crashes because of a segfault. Unfortunately I can't provide a backtrace. STEPS TO REPRODUCE 1. Open Parley 2. Open a recent word collection (File -> Open Recent) Or 1. Create a new collection: File -> New 2. Ok 3. Edit Languages -> Ok OBSERVED RESULT A segfault is happening. EXPECTED RESULT I think, the word editor should open. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 443223] Use bit/s instead of Byte/s for data rates
https://bugs.kde.org/show_bug.cgi?id=443223 sedrubal changed: What|Removed |Added CC||k...@sedrubal.de --- Comment #3 from sedrubal --- In my use case, I wanted to know the utilization of the link. When I know, that there is a 1 Gbit/s link, it's hard to estimate the utilization if all graphs show values in bytes/s. In my opinion this is the default use case of such graphs but I could be wrong. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 398890] Add monitor brightness to system settings
https://bugs.kde.org/show_bug.cgi?id=398890 sedrubal changed: What|Removed |Added CC||k...@sedrubal.de -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 353032] Add ability to set screen brightness for non-laptop displays so I can adjust to the room's lighting
https://bugs.kde.org/show_bug.cgi?id=353032 sedrubal changed: What|Removed |Added CC||k...@sedrubal.de -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 443223] New: Use bit/s instead of Byte/s for data rates
https://bugs.kde.org/show_bug.cgi?id=443223 Bug ID: 443223 Summary: Use bit/s instead of Byte/s for data rates Product: plasma-systemmonitor Version: 5.22.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: k...@sedrubal.de CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY Currently data rates are displayed in MiB/s, KiB/s and so on. Usually you use bit/s (kbit/s, Mbit/s, ...) for data rates, I guess. STEPS TO REPRODUCE 1. Create a graph and add the sensor like "Network" > "Interfaces" > $device > Receiver / Transmitter > Data Rate OBSERVED RESULT The values are displayed using KiB/s (e.g. 300 KiB/s) EXPECTED RESULT The values should be displayed in bit/s (e.g. 2.4 Mbit/s) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 441175] New: Turn off monitor after actively locking the screen
https://bugs.kde.org/show_bug.cgi?id=441175 Bug ID: 441175 Summary: Turn off monitor after actively locking the screen Product: kscreenlocker Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: k...@sedrubal.de CC: bhus...@gmail.com Target Milestone: --- SUMMARY It would be great, if you add a config to turn off the monitor immediately after the screen was actively locked. Most of the time the computer won't be used soon after the screen was locked (e.g. by using a keyboard shortcut). Energy can be saved if the screen turns off immediately instead of after the default timeout. I think, this behavior can be configured on Mac books (but I'm not sure). OBSERVED RESULT After locking the screen using a keyboard shortcut, the screen keeps turned on for the default duration, that is configured in the energy settings. EXPECTED RESULT It was great if the screen turns off much earlier. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 434321] Lock screen doesn't clear the password entered, when left idle.
https://bugs.kde.org/show_bug.cgi?id=434321 sedrubal changed: What|Removed |Added CC||k...@sedrubal.de -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 387418] Password field allows deleted password to be restored with Ctrl+z
https://bugs.kde.org/show_bug.cgi?id=387418 sedrubal changed: What|Removed |Added CC||k...@sedrubal.de -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 432262] Sometimes screen is not locked upon hibernation
https://bugs.kde.org/show_bug.cgi?id=432262 sedrubal changed: What|Removed |Added CC||k...@sedrubal.de -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 441032] Switching Screen 100% CPU
https://bugs.kde.org/show_bug.cgi?id=441032 sedrubal changed: What|Removed |Added CC||k...@sedrubal.de --- Comment #1 from sedrubal --- When I wrote `korganizer` I meant `kontact`. Sorry... -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 441032] New: Switching Screen 100% CPU
https://bugs.kde.org/show_bug.cgi?id=441032 Bug ID: 441032 Summary: Switching Screen 100% CPU Product: korganizer Version: 5.18.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: reminder daemon (korgac) Assignee: kdepim-b...@kde.org Reporter: k...@sedrubal.de Target Milestone: --- SUMMARY When I switch my screen (from internal laptop screen to external screen or other way round) under wayland korganizer freezes often and korgac runs at 100% CPU load. STEPS TO REPRODUCE 1. Use wayland session 2. Run kmail in korganizer 3. Switch screen to external monitor or to laptop monitor OBSERVED RESULT kmail / korganizer freezes; korgac utilises 100% CPU load EXPECTED RESULT The applications should not break when you change the screen. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Grpahics Platform: Wayland Graphics Processor: Mesa Intel HD Graphics 530 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414786] Plasmashell crashes when you move a file to the last desktop on pager
https://bugs.kde.org/show_bug.cgi?id=414786 sedrubal changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME CC||k...@sedrubal.de Status|NEEDSINFO |RESOLVED --- Comment #2 from sedrubal --- Yes it looks like this is fixed. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 438833] Everything jerks when changing laptop brightness and external screen is enabled
https://bugs.kde.org/show_bug.cgi?id=438833 --- Comment #1 from sedrubal --- To add some more info: Sometimes jerking does not end but can be resolved, when I active my internal laptop display additionally to an external screen, that is already activated. Actually I want to switch to the second screen and disable the laptop screen. This is the output of `kscreen-doctor --outputs --info` Environment: * KSCREEN_BACKEND : [not set] * KSCREEN_BACKEND_INPROCESS : [not set] * KSCREEN_LOGGING : [not set] Logging to: [logging disabled] Preferred KScreen backend : KSC_XRandR.so Available KScreen backends: * KSC_Fake.so: /usr/lib/qt/plugins/kf5/kscreen/KSC_Fake.so * KSC_KWayland.so: /usr/lib/qt/plugins/kf5/kscreen/KSC_KWayland.so * KSC_QScreen.so: /usr/lib/qt/plugins/kf5/kscreen/KSC_QScreen.so * KSC_XRandR.so: /usr/lib/qt/plugins/kf5/kscreen/KSC_XRandR.so * KSC_XRandR11.so: /usr/lib/qt/plugins/kf5/kscreen/KSC_XRandR11.so Output: 67 eDP1 enabled connected Panel Modes: 504:1920x1080@60 505:1680x1050@60 506:1400x1050@60 507:1600x900@60 508:1600x900@60 509:1600x900@60 510:1280x1024@60 511:1400x900@60 512:1400x900@60 513:1280x960@60 514:1368x768@60 515:1368x768@60 516:1368x768@60 517:1280x800@60 518:1280x800@60 519:1280x720@60 520:1280x720@60 521:1280x720@60 522:1024x768@60 523:1024x576@60 524:1024x576@60 525:1024x576@60 526:960x540@60 527:960x540@60 528:960x540@60 529:800x600@60 530:800x600@56 531:864x486@60 532:864x486@60 533:864x486@60 534:640x480@60 535:720x405@60 536:720x405@60 537:720x405@59 538:640x360@60 539:640x360@59 540:640x360@60 70:1920x1080@60*! Geometry: 0,1080 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable Output: 68 VIRTUAL1 disabled disconnected Unknown Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable Output: 203 DP-1-1 disabled disconnected DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable Output: 204 DP-1-2 enabled connected primary DisplayPort Modes: 505:1680x1050@60 510:1280x1024@60 513:1280x960@60 522:1024x768@60 529:800x600@60 530:800x600@56 534:640x480@60 910:1920x1080@60*! 911:1920x1080@50 912:1920x1080@60 913:1920x1080@60 914:1920x1080@50 915:1920x1080@60 916:1280x1024@75 917:1440x900@60 918:1280x720@60 919:1280x720@50 920:1280x720@60 921:1024x768@75 922:1024x768@70 923:832x624@75 924:800x600@72 925:800x600@75 926:720x576@50 927:720x480@60 928:720x480@60 929:640x480@75 930:640x480@73 931:640x480@67 932:640x480@60 933:720x400@70 Geometry: 0,0 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable primary Output: 205 DP-1-3 disabled disconnected DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 438833] Everything jerks when changing laptop brightness and external screen is enabled
https://bugs.kde.org/show_bug.cgi?id=438833 sedrubal changed: What|Removed |Added CC||k...@sedrubal.de -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 438833] New: Everything jerks when changing laptop brightness and external screen is enabled
https://bugs.kde.org/show_bug.cgi?id=438833 Bug ID: 438833 Summary: Everything jerks when changing laptop brightness and external screen is enabled Product: KScreen Version: 5.18.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: k...@sedrubal.de Target Milestone: --- SUMMARY When I plug in an external monitor and change my laptop display brightness or lock my screen, everything (graphics, music, cursor) jerks for about one minute and then it works again. STEPS TO REPRODUCE 0. Use plasma desktop with X11 1. Plug in an external monitor 2. Extend screen to that monitor 3. Change display brightness or lock screen OBSERVED RESULT Everything jerks and CPU fan turns up for about one minute. Then everything works again. EXPECTED RESULT Graphics and music should stay fluent. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.22.1 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Kernel 5.10.44 Graphics Platform: X11 in journal this lines are showing up multiple times in that time span: kscreen_backend_launcher[1033]: kscreen.xcb.helper: State (newValue, Deleted): 0 kscreen_backend_launcher[1033]: kscreen.xcb.helper: Property: BACKLIGHT kscreen_backend_launcher[1033]: kscreen.xcb.helper: Output: 67 kscreen_backend_launcher[1033]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413822] Option to not change layout by scrolling
https://bugs.kde.org/show_bug.cgi?id=413822 sedrubal changed: What|Removed |Added CC||k...@sedrubal.de --- Comment #8 from sedrubal --- Yes it behaves similar under wayland. In the meantime the issue is less worse as there are tiles used instead of a list for the items in the tray and you don't have to scroll all the time to see all items. -- You are receiving this mail because: You are watching all bug changes.
[phonon-backend-gstreamer] [Bug 354873] Stops playing music when trying to play a deleted track
https://bugs.kde.org/show_bug.cgi?id=354873 sedrubal changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #6 from sedrubal --- I don't use Amarok anymore so I'm not sure, if the problem still exists. -- You are receiving this mail because: You are watching all bug changes.
[storageservicemanager] [Bug 355655] Not informative error message: Actions failed - Upload File returns an error: Connection closed
https://bugs.kde.org/show_bug.cgi?id=355655 sedrubal changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME CC||k...@sedrubal.de -- You are receiving this mail because: You are watching all bug changes.
[storageservicemanager] [Bug 355656] Cancel button does nothing after a action failed
https://bugs.kde.org/show_bug.cgi?id=355656 sedrubal changed: What|Removed |Added CC||k...@sedrubal.de Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from sedrubal --- I don't know the issue anymore. -- You are receiving this mail because: You are watching all bug changes.
[storageservicemanager] [Bug 355654] Progress notification not working with multiple uploads
https://bugs.kde.org/show_bug.cgi?id=355654 sedrubal changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME CC||k...@sedrubal.de --- Comment #2 from sedrubal --- I don't know the issue anymore. -- You are receiving this mail because: You are watching all bug changes.
[storageservicemanager] [Bug 355658] Error on cancelling authentication
https://bugs.kde.org/show_bug.cgi?id=355658 sedrubal changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #5 from sedrubal --- I can't remember the issue anymore. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433338] New: Allow to set custom icon for bluetooth devices
https://bugs.kde.org/show_bug.cgi?id=48 Bug ID: 48 Summary: Allow to set custom icon for bluetooth devices Product: systemsettings Version: 5.21.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_bluetooth Assignee: now...@gmail.com Reporter: k...@sedrubal.de CC: plasma-b...@kde.org Target Milestone: --- SUMMARY When you did connect to multiple Bluetooth devices the list of devices might be a bit confusing. You can set custom names to devices but the icon, that is displayed is automatically chosen. It would be great if you can set the icon of each Bluetooth device on your own. In my case a headphones symbol is chosen for a stationary Bluetooth device and I think this is quite confusing. STEPS TO REPRODUCE 1. Connect to a Bluetooth device 2. Show on the list of known Bluetooth devices OBSERVED RESULT The icon is chosen automatically and cannot be changed (the name can be changed) EXPECTED RESULT The icon can be chosen using the "Select icon" dialog, that is used for other components of plasma, too. SOFTWARE/OS VERSIONS Linux/KDE Plasma: arch Linux KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 399848] Closing neovim in terminal crashes konsole
https://bugs.kde.org/show_bug.cgi?id=399848 sedrubal changed: What|Removed |Added CC||k...@sedrubal.de Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #4 from sedrubal --- Yes it looks like this is fixed. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 381328] Okular crashes when editing forms in a PDF that's located inside an archive
https://bugs.kde.org/show_bug.cgi?id=381328 sedrubal changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #13 from sedrubal --- Yes this should be fixed now. There is also an alert, that you can't save the document and you have to save it under another location. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 429385] New: Control Audio Volume of Android Device on Desktop
https://bugs.kde.org/show_bug.cgi?id=429385 Bug ID: 429385 Summary: Control Audio Volume of Android Device on Desktop Product: kdeconnect Version: 1.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: k...@sedrubal.de Target Milestone: --- SUMMARY Add a volume slider to the kde-connect widget on desktop to control the volume of a remote (android) device SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION Currently it is possible to write custom scripts / assign keyboard shortcuts using dbus: decrease volume: qdbus org.kde.kdeconnect /modules/kdeconnect/devices//mprisremote org.freedesktop.DBus.Properties.Set "" volume $(($(qdbus org.kde.kdeconnect /modules/kdeconnect/devices//mprisremote org.kde.kdeconnect.device.mprisremote.volume) - 10)) increase volume: qdbus org.kde.kdeconnect /modules/kdeconnect/devices//mprisremote org.freedesktop.DBus.Properties.Set "" volume $(($(qdbus org.kde.kdeconnect /modules/kdeconnect/devices//mprisremote org.kde.kdeconnect.device.mprisremote.volume) + 10)) -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 429343] New: Wrong incidence in the preview of the reminder
https://bugs.kde.org/show_bug.cgi?id=429343 Bug ID: 429343 Summary: Wrong incidence in the preview of the reminder Product: korganizer Version: 5.15.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: reminder daemon (korgac) Assignee: kdepim-b...@kde.org Reporter: k...@sedrubal.de Target Milestone: --- SUMMARY When reminders of multiple incidences pop up at the same time (e.g. after waking up the suspended notebook) it happens sometimes, that one item is selected in the list at the top, but another one is displayed in the preview. STEPS TO REPRODUCE 1. Wake up your notebook 2. Multiple incidences trigger a reminder at the same time OBSERVED RESULT One incidence is selected above. EXPECTED RESULT Another one is displayed in the preview below. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 365268] Kmail2 crashed while deleting items rapidly
https://bugs.kde.org/show_bug.cgi?id=365268 sedrubal changed: What|Removed |Added CC||k...@sedrubal.de -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 427817] Unified Folders don't work
https://bugs.kde.org/show_bug.cgi?id=427817 sedrubal changed: What|Removed |Added CC||k...@sedrubal.de Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from sedrubal --- This seems to be a duplicate of Bug 403770 *** This bug has been marked as a duplicate of bug 403770 *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 403770] unified mailbox (folder) not update sometimes
https://bugs.kde.org/show_bug.cgi?id=403770 sedrubal changed: What|Removed |Added CC||soporte@gmail.com --- Comment #5 from sedrubal --- *** Bug 427817 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421100] New: Plasmashell crashes right after start
https://bugs.kde.org/show_bug.cgi?id=421100 Bug ID: 421100 Summary: Plasmashell crashes right after start Product: plasmashell Version: 5.18.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: k...@sedrubal.de CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.3) Qt Version: 5.13.2 Frameworks Version: 5.68.0 Operating System: Linux 5.6.8-300.fc32.x86_64 x86_64 Windowing system: X11 Distribution: Fedora 32 (Thirty Two) -- Information about the crash: - What I was doing when the application crashed: I think, as soon as a notification comes in, plasmashell / plasmaworkspace crashes. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbf33935580 (LWP 9938))] Thread 12 (Thread 0x7fbee2570700 (LWP 9991)): [KCrash Handler] #6 std::__atomic_base::operator++ (this=0x1296) at /usr/include/c++/10/bits/atomic_base.h:325 #7 QAtomicOps::ref (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:265 #8 QBasicAtomicInteger::ref (this=0x1296) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:114 #9 QRawFontPrivate::setFontEngine (engine=0x128a, this=0x7fbed40e5550) at text/qrawfont_p.h:128 #10 glyphRunWithInfo (fontEngine=0x128a, glyphLayout=..., pos=..., flags=..., selectionX=..., selectionWidth=..., glyphsStart=28, glyphsEnd=28, logClusters=, textPosition=0, textLength=44) at text/qtextlayout.cpp:2239 #11 0x7fbf37ba219e in QTextLine::glyphRuns (this=this@entry=0x7fbee256d5c0, from=from@entry=0, length=, length@entry=44) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:211 #12 0x7fbf390d2090 in QQuickTextNodeEngine::addGlyphsInRange (this=this@entry=0x7fbee256d560, rangeStart=rangeStart@entry=0, rangeLength=rangeLength@entry=44, color=..., backgroundColor=..., selectionStart=selectionStart@entry=-1, selectionEnd=-1) at items/qquicktextnodeengine.cpp:593 #13 0x7fbf390d26d4 in QQuickTextNodeEngine::addGlyphsForRanges (this=this@entry=0x7fbee256d560, ranges=..., start=start@entry=0, end=44, selectionStart=selectionStart@entry=-1, selectionEnd=selectionEnd@entry=-1) at /usr/include/qt5/QtGui/qcolor.h:290 #14 0x7fbf390d0fcb in QQuickTextNode::addTextLayout (this=this@entry=0x7fbed457cde0, position=..., textLayout=0x561d908a65d0, color=..., style=QQuickText::Normal, styleColor=..., anchorColor=..., selectionColor=..., selectedTextColor=..., selectionStart=-1, selectionEnd=-1, lineStart=0, lineCount=1) at items/qquicktextnode.cpp:268 #15 0x7fbf390cf7e1 in QQuickText::updatePaintNode (this=0x561d8d3b7580, oldNode=, data=) at /usr/include/qt5/QtCore/qpoint.h:287 #16 0x7fbf39085778 in QQuickWindowPrivate::updateDirtyNode (this=0x561d8b3d44f0, item=0x561d8d3b7580) at items/qquickwindow.cpp:3532 #17 0x7fbf3908600b in QQuickWindowPrivate::updateDirtyNodes (this=this@entry=0x561d8b3d44f0) at items/qquickwindow.cpp:3277 #18 0x7fbf390876d6 in QQuickWindowPrivate::syncSceneGraph (this=this@entry=0x561d8b3d44f0) at items/qquickwindow.cpp:437 #19 0x7fbf3902d962 in QSGRenderThread::sync (this=this@entry=0x561d8d3ff480, inExpose=inExpose@entry=false) at scenegraph/qsgthreadedrenderloop.cpp:563 #20 0x7fbf3902ef14 in QSGRenderThread::syncAndRender (this=this@entry=0x561d8d3ff480) at scenegraph/qsgthreadedrenderloop.cpp:610 #21 0x7fbf3902f3b8 in QSGRenderThread::run (this=0x561d8d3ff480) at scenegraph/qsgthreadedrenderloop.cpp:730 #22 0x7fbf3759b846 in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:360 #23 0x7fbf36aeb432 in start_thread () from /lib64/libpthread.so.0 #24 0x7fbf372229d3 in clone () from /lib64/libc.so.6 Thread 11 (Thread 0x7fbee886c700 (LWP 9983)): #0 0x7fbf35e99c2d in g_source_unref_internal () from /lib64/libglib-2.0.so.0 #1 0x7fbf35e9b985 in g_source_iter_next () from /lib64/libglib-2.0.so.0 #2 0x7fbf35e9cf23 in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #3 0x7fbf35e9da1b in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #4 0x7fbf35e9dc23 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7fbf37772c23 in QEventDispatcherGlib::processEvents (this=0x7fbedc000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7fbf3772621b in QEventLoop::exec (this=this@entry=0x7fbee886bd60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7fbf3759a577 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7fbee8d8d66c in KCupsConnection::run() () from /lib64/libkcupslib.so #9
[kdeconnect] [Bug 420447] Clipboard Sync broken since Android App 1.14.1
https://bugs.kde.org/show_bug.cgi?id=420447 sedrubal changed: What|Removed |Added Resolution|--- |FIXED CC||k...@sedrubal.de Status|REPORTED|RESOLVED --- Comment #1 from sedrubal --- Updating to 1.14.2 fixed the problem. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 420447] New: Clipboard Sync broken since Android App 1.14.1
https://bugs.kde.org/show_bug.cgi?id=420447 Bug ID: 420447 Summary: Clipboard Sync broken since Android App 1.14.1 Product: kdeconnect Version: unspecified Platform: Android OS: Android 9.x Status: REPORTED Severity: major Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: k...@sedrubal.de Target Milestone: --- SUMMARY Since I upgraded to the android app 1.14.1, the clipboard sync seems to be broken. STEPS TO REPRODUCE 1. Install 1.14.1, connect to laptop 2. Copy something on your laptop 3. try to paste it on the smartphone OBSERVED RESULT The content that was in the smartphones clipboard before will be pasted. EXPECTED RESULT The content you copied on your laptop should be pasted. SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: Fedora 32 KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.13.2 Android: 9 kdeconnect Android App Version: 1.14.1 ADDITIONAL INFORMATION - Uninstalling KDE connect, installing 1.13.7 and reconnecting to laptop solves the issue - I'm using the android app from f-droid -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 410700] kmail no longer allows addition of gmail account
https://bugs.kde.org/show_bug.cgi?id=410700 sedrubal changed: What|Removed |Added CC||k...@sedrubal.de -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414713] Crash when clicking on multimedia
https://bugs.kde.org/show_bug.cgi?id=414713 sedrubal changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED CC||k...@sedrubal.de --- Comment #2 from sedrubal --- I can't reproduce it, because it did not happen on my PC. Most likely that person upgraded to plasma 5.17 already. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 415802] New: Don't try to retrieve mails if there is not internet connectivity
https://bugs.kde.org/show_bug.cgi?id=415802 Bug ID: 415802 Summary: Don't try to retrieve mails if there is not internet connectivity Product: kmail2 Version: 5.11.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: k...@sedrubal.de Target Milestone: --- Created attachment 124854 --> https://bugs.kde.org/attachment.cgi?id=124854=edit Error message box SUMMARY Sometimes right after starting KDE when there is not yet an internet connection, kmail shows many error messages (one per IMAP account), that it can't connect to IMAP servers. STEPS TO REPRODUCE 1. Configure kmail / kontact as autostart app 2. Start KDE plasma OBSERVED RESULT The attached message box pops up and a bit later the internet connectivity is established. EXPECTED RESULT kontact / kmail should wait until there is a internet connectivity SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 31 KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.64.0 Qt Version: 5.12.5 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 80406] KOorganizer should use KNotify for lots of messages
https://bugs.kde.org/show_bug.cgi?id=80406 sedrubal changed: What|Removed |Added CC||k...@sedrubal.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414786] New: Plasmashell crashes when you move a file to the last desktop on pager
https://bugs.kde.org/show_bug.cgi?id=414786 Bug ID: 414786 Summary: Plasmashell crashes when you move a file to the last desktop on pager Product: plasmashell Version: 5.16.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Pager Assignee: h...@kde.org Reporter: k...@sedrubal.de CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 124290 --> https://bugs.kde.org/attachment.cgi?id=124290=edit An incomplete backtrace SUMMARY When you move a file to the last desktop on the pager widget, plasmashell crashes. STEPS TO REPRODUCE 0. Add the pager widget to your taskbar 1. Add or remove a desktop (I'm not sure, if this step is required) 2. Open dolphin 3. Drag a file to the last desktop on the pager and wait a bit OBSERVED RESULT After some milliseconds you usually would change to that desktop. But instead it crashes. EXPECTED RESULT You should automatically change to the last desktop. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 31, plasma 5.16.5 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.12.5 ADDITIONAL INFORMATION When you hover other desktops there seems to be an off-by-one error and you sometimes change to the wrong desktop, too. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414713] New: Crash when clicking on multimedia
https://bugs.kde.org/show_bug.cgi?id=414713 Bug ID: 414713 Summary: Crash when clicking on multimedia Product: systemsettings Version: 5.16.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: k...@sedrubal.de Target Milestone: --- Application: systemsettings5 (5.16.5) Qt Version: 5.12.5 Frameworks Version: 5.61.0 Operating System: Linux 5.3.12-300.fc31.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I searched for audio in systemsettings and found multimedia. It crashed, when I clicked on multimedia. The crash can be reproduced every time. -- Backtrace: Application: Systemeinstellungen (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1a3c332840 (LWP 2854))] Thread 6 (Thread 0x7f1a1b5ef700 (LWP 2860)): #0 0x7f1a3e7e7a08 in g_mutex_unlock () from /lib64/libglib-2.0.so.0 #1 0x7f1a3e79ad0d in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #2 0x7f1a3e79b6cb in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7f1a3e79b8d3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7f1a40b0bcd3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f1a40ab5ceb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f1a4090e395 in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x7f1a3fbed119 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #8 0x7f1a4090f4e6 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7f1a3f0ec4e2 in start_thread () from /lib64/libpthread.so.0 #10 0x7f1a40590693 in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f1a25d91700 (LWP 2859)): #0 0x7f1a4058144c in read () from /lib64/libc.so.6 #1 0x7f1a3e7e34cf in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0 #2 0x7f1a3e79b2e7 in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x7f1a3e79b742 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #4 0x7f1a3e79b8d3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f1a40b0bcd3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f1a40ab5ceb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7f1a4090e395 in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7f1a3fbed119 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #9 0x7f1a4090f4e6 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #10 0x7f1a3f0ec4e2 in start_thread () from /lib64/libpthread.so.0 #11 0x7f1a40590693 in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f1a2c8cc700 (LWP 2857)): #0 0x7f1a3f0f2d45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f1a277db14b in util_queue_thread_func () from /usr/lib64/dri/i965_dri.so #2 0x7f1a277dad5b in impl_thrd_routine () from /usr/lib64/dri/i965_dri.so #3 0x7f1a3f0ec4e2 in start_thread () from /lib64/libpthread.so.0 #4 0x7f1a40590693 in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f1a2e036700 (LWP 2856)): #0 0x7f1a420fcd75 in _dl_update_slotinfo () from /lib64/ld-linux-x86-64.so.2 #1 0x7f1a420fcddc in update_get_addr () from /lib64/ld-linux-x86-64.so.2 #2 0x7f1a42101fbc in __tls_get_addr () from /lib64/ld-linux-x86-64.so.2 #3 0x7f1a4090ea8a in QThreadData::current(bool) () from /lib64/libQt5Core.so.5 #4 0x7f1a40b0bb8e in postEventSourcePrepare(_GSource*, int*) () from /lib64/libQt5Core.so.5 #5 0x7f1a3e79ad1a in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #6 0x7f1a3e79b6cb in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #7 0x7f1a3e79b8d3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #8 0x7f1a40b0bcd3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #9 0x7f1a40ab5ceb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #10 0x7f1a4090e395 in QThread::exec() () from /lib64/libQt5Core.so.5 #11 0x7f1a40d87f4a in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #12 0x7f1a4090f4e6 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #13 0x7f1a3f0ec4e2 in start_thread () from /lib64/libpthread.so.0 #14 0x7f1a40590693 in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f1a2f036700 (LWP 2855)): #0 0x7f1a40585a6f in poll () from /lib64/libc.so.6 #1 0x7f1a3f0ab38a in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x7f1a3f0acfea in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f1a2f213ac8 in QXcbEventQueue::run() () from
[kxkb] [Bug 413822] New: Keyboard Layout indicator: Do not change layout by scrolling
https://bugs.kde.org/show_bug.cgi?id=413822 Bug ID: 413822 Summary: Keyboard Layout indicator: Do not change layout by scrolling Product: kxkb Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: k...@sedrubal.de Target Milestone: --- Created attachment 123726 --> https://bugs.kde.org/attachment.cgi?id=123726=edit Screen record of scrolling over keyboard layout switching indicator by mistake SUMMARY When you scroll over the kayboard layout switcher in the system tray the keyboard layout changes automatically even if it is not intended. STEPS TO REPRODUCE 1. Configure more than one keyboard layout 2. Configure the keyboard indicator to be hidden in system tray 3. Have enough elements in the system tray in order you are able to scroll the collapsed list 4. Scroll over the keyboard indicator OBSERVED RESULT The layout switches EXPECTED RESULT The layout should not be switched if it is not inteded. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 31 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.12.5 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 179678] KIO needs PolicyKit-kde integration
https://bugs.kde.org/show_bug.cgi?id=179678 sedrubal changed: What|Removed |Added CC|k...@sedrubal.de | -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 392341] Zooming not possible in neovim when guicursor enabled
https://bugs.kde.org/show_bug.cgi?id=392341 sedrubal changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||k...@sedrubal.de --- Comment #2 from sedrubal --- I'm not able to reproduce it neither any more. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 411728] New: Messageid is leaking hostname
https://bugs.kde.org/show_bug.cgi?id=411728 Bug ID: 411728 Summary: Messageid is leaking hostname Product: kmail2 Version: 5.11.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: k...@sedrubal.de Target Milestone: --- SUMMARY kmail generates message IDs using a random string and @. There may be cases where you don't want to tell your hostname. STEPS TO REPRODUCE 1. Write an E-Mail 2. Send it 3. Inspect its sources OBSERVED RESULT The Message-ID is something like <$random@$hostname> EXPECTED RESULT There should be at least an option to make the message id anonymous. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 30 KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION Additionally it would be great to hide the following headers: - X-KMail-Identity - X-KMail-Transport - X-KMail-Fcc - X-KMail-Identity-Name - X-KMail-Transport-Name -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411308] Application Dashboard not opens on primary display
https://bugs.kde.org/show_bug.cgi?id=411308 --- Comment #6 from sedrubal --- Created attachment 122366 --> https://bugs.kde.org/attachment.cgi?id=122366=edit Screenshot of the current setup without the application dashboard -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411308] Application Dashboard not opens on primary display
https://bugs.kde.org/show_bug.cgi?id=411308 --- Comment #5 from sedrubal --- Created attachment 122365 --> https://bugs.kde.org/attachment.cgi?id=122365=edit Screenshot of the current setup The primary monitor is below the secondary. Its resolution is 1920x1080. The second monitor has a higher resolution, but this should not change the behaviour. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411308] Application Dashboard not opens on primary display
https://bugs.kde.org/show_bug.cgi?id=411308 --- Comment #4 from sedrubal --- Created attachment 122364 --> https://bugs.kde.org/attachment.cgi?id=122364=edit xwininfo if the application dashboard -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411308] Application Dashboard not opens on primary display
https://bugs.kde.org/show_bug.cgi?id=411308 --- Comment #3 from sedrubal --- Created attachment 122363 --> https://bugs.kde.org/attachment.cgi?id=122363=edit xrandr -q -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411308] Application Dashboard not opens on primary display
https://bugs.kde.org/show_bug.cgi?id=411308 sedrubal changed: What|Removed |Added CC||k...@sedrubal.de --- Comment #2 from sedrubal --- Created attachment 122362 --> https://bugs.kde.org/attachment.cgi?id=122362=edit xprop of the application dashboard -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411308] New: Application Dashboard not opens on primary display
https://bugs.kde.org/show_bug.cgi?id=411308 Bug ID: 411308 Summary: Application Dashboard not opens on primary display Product: plasmashell Version: 5.15.5 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: k...@sedrubal.de CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY The Application Dashboard always opens on the most left and most upper screen / display and not on the primary display or that display, where the cursor is currently placed. STEPS TO REPRODUCE 1. Connect an external monitor 2. Align it above or left of the primary display 3. Configure plasmashell to use the application dashboard instead of the application launcher 4. Move the cursor to the primary screen and focus a window there 5. Hit the Super key / Windows key or Alt+F1 or click on the dashboard launch icon OBSERVED RESULT It opens on the secondary most left / most upper display. EXPECTED RESULT It should open on the primary screen or on that screen, where the cursor is currently placed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 30 - Kernel 5.2.9-200.fc30.x86_64 KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 403770] unified mailbox (folder) not update sometimes
https://bugs.kde.org/show_bug.cgi?id=403770 sedrubal changed: What|Removed |Added CC||k...@sedrubal.de -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 403574] Suddenly crashed while clicking through IMAP folders in kmail
https://bugs.kde.org/show_bug.cgi?id=403574 sedrubal changed: What|Removed |Added CC||k...@sedrubal.de --- Comment #2 from sedrubal --- Unfortunately I could not reproduce it but I installed the debug symbols and will report back, when it happens again. Otherwise you can close this bug. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 403574] New: Suddenly crashed while clicking through IMAP folders in kmail
https://bugs.kde.org/show_bug.cgi?id=403574 Bug ID: 403574 Summary: Suddenly crashed while clicking through IMAP folders in kmail Product: kontact Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: k...@sedrubal.de Target Milestone: --- Application: kontact (5.9.3) Qt Version: 5.11.3 Frameworks Version: 5.53.0 Operating System: Linux 4.20.3-200.fc29.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I clicked through the folders of one IMAP account in kmail and suddenly kontact crashed. The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbae1c84380 (LWP 3329))] Thread 35 (Thread 0x7fb990c5e700 (LWP 12835)): #0 0x7fbae5c3fb28 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbae85d7607 in () at /lib64/libQt5WebEngineCore.so.5 #2 0x7fbae85d92ca in () at /lib64/libQt5WebEngineCore.so.5 #3 0x7fbae85d93b2 in () at /lib64/libQt5WebEngineCore.so.5 #4 0x7fbae85de171 in () at /lib64/libQt5WebEngineCore.so.5 #5 0x7fbae85df651 in () at /lib64/libQt5WebEngineCore.so.5 #6 0x7fbae85e9a81 in () at /lib64/libQt5WebEngineCore.so.5 #7 0x7fbae5c3958e in start_thread () at /lib64/libpthread.so.0 #8 0x7fbaed39e6a3 in clone () at /lib64/libc.so.6 Thread 34 (Thread 0x7fb973fff700 (LWP 12832)): #0 0x7fbae5c3fb28 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbae85d7607 in () at /lib64/libQt5WebEngineCore.so.5 #2 0x7fbae85d92ca in () at /lib64/libQt5WebEngineCore.so.5 #3 0x7fbae85d93b2 in () at /lib64/libQt5WebEngineCore.so.5 #4 0x7fbae85de171 in () at /lib64/libQt5WebEngineCore.so.5 #5 0x7fbae85df651 in () at /lib64/libQt5WebEngineCore.so.5 #6 0x7fbae85e9a81 in () at /lib64/libQt5WebEngineCore.so.5 #7 0x7fbae5c3958e in start_thread () at /lib64/libpthread.so.0 #8 0x7fbaed39e6a3 in clone () at /lib64/libc.so.6 Thread 33 (Thread 0x7fb9a97bd700 (LWP 12584)): #0 0x7fbaed393421 in poll () at /lib64/libc.so.6 #1 0x7fbae34243a6 in () at /lib64/libglib-2.0.so.0 #2 0x7fbae34244d0 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fbaeda405ab in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fbaed9eee0b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fbaed856e86 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fbaed8602fb in () at /lib64/libQt5Core.so.5 #7 0x7fbae5c3958e in start_thread () at /lib64/libpthread.so.0 #8 0x7fbaed39e6a3 in clone () at /lib64/libc.so.6 Thread 32 (Thread 0x7fb992b85700 (LWP 12030)): #0 0x7fbaed393421 in poll () at /lib64/libc.so.6 #1 0x7fbae34243a6 in () at /lib64/libglib-2.0.so.0 #2 0x7fbae34244d0 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fbaeda405ab in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fbaed9eee0b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fbaed856e86 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fbaed8602fb in () at /lib64/libQt5Core.so.5 #7 0x7fbae5c3958e in start_thread () at /lib64/libpthread.so.0 #8 0x7fbaed39e6a3 in clone () at /lib64/libc.so.6 Thread 31 (Thread 0x7fbab37fe700 (LWP 30783)): #0 0x7fbac43cbf61 in pa_pstream_unref () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #1 0x7fbac43cc4ad in srb_callback () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #2 0x7fbac43ccd3a in srbchannel_rwloop () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #3 0x7fbac4431fd8 in pa_mainloop_dispatch () at /lib64/libpulse.so.0 #4 0x7fbac44322b0 in pa_mainloop_iterate () at /lib64/libpulse.so.0 #5 0x7fbac4432350 in pa_mainloop_run () at /lib64/libpulse.so.0 #6 0x7fbac44405bd in thread () at /lib64/libpulse.so.0 #7 0x7fbac43dd06c in internal_thread_func () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #8 0x7fbae5c3958e in start_thread () at /lib64/libpthread.so.0 #9 0x7fbaed39e6a3 in clone () at /lib64/libc.so.6 Thread 30 (Thread 0x7fb9a8bfa700 (LWP 4419)): #0 0x7fbaed393421 in poll () at /lib64/libc.so.6 #1 0x7fbae34243a6 in () at /lib64/libglib-2.0.so.0 #2 0x7fbae34244d0 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fbaeda405ab in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fbaed9eee0b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5
[kontact] [Bug 377115] Disabling journal turns To-do List into calendar
https://bugs.kde.org/show_bug.cgi?id=377115 --- Comment #4 from sedrubal --- I'm on 5.9.3, too. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 363570] Save login information never stored
https://bugs.kde.org/show_bug.cgi?id=363570 sedrubal changed: What|Removed |Added CC||k...@sedrubal.de -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 402129] New: Crash after closing kmail
https://bugs.kde.org/show_bug.cgi?id=402129 Bug ID: 402129 Summary: Crash after closing kmail Product: kontact Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: k...@sedrubal.de Target Milestone: --- Application: kontact (5.9.3) Qt Version: 5.11.1 Frameworks Version: 5.52.0 Operating System: Linux 4.19.8-300.fc29.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: I closed kmail and got the notification, that it crashed. The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2938ec7340 (LWP 26095))] Thread 36 (Thread 0x7f27e6bfc700 (LWP 30698)): #0 0x7f293ce82b68 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f293f80ace7 in () at /lib64/libQt5WebEngineCore.so.5 #2 0x7f293f80c9ba in () at /lib64/libQt5WebEngineCore.so.5 #3 0x7f293f80caa2 in () at /lib64/libQt5WebEngineCore.so.5 #4 0x7f293f811861 in () at /lib64/libQt5WebEngineCore.so.5 #5 0x7f293f812d41 in () at /lib64/libQt5WebEngineCore.so.5 #6 0x7f293f81d171 in () at /lib64/libQt5WebEngineCore.so.5 #7 0x7f293ce7c58e in start_thread () at /lib64/libpthread.so.0 #8 0x7f2944a3 in clone () at /lib64/libc.so.6 Thread 35 (Thread 0x7f28fbfff700 (LWP 30013)): #0 0x7f294465b421 in poll () at /lib64/libc.so.6 #1 0x7f2920681675 in poll_func () at /lib64/libpulse.so.0 #2 0x7f2920672c58 in pa_mainloop_poll () at /lib64/libpulse.so.0 #3 0x7f29206732a2 in pa_mainloop_iterate () at /lib64/libpulse.so.0 #4 0x7f2920673350 in pa_mainloop_run () at /lib64/libpulse.so.0 #5 0x7f29206815bd in thread () at /lib64/libpulse.so.0 #6 0x7f292061e06c in internal_thread_func () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #7 0x7f293ce7c58e in start_thread () at /lib64/libpthread.so.0 #8 0x7f2944a3 in clone () at /lib64/libc.so.6 Thread 34 (Thread 0x7f27e63fb700 (LWP 29906)): #0 0x7f2944656f84 in read () at /lib64/libc.so.6 #1 0x7f293a6a6aa0 in () at /lib64/libglib-2.0.so.0 #2 0x7f293a66009b in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f293a660550 in () at /lib64/libglib-2.0.so.0 #4 0x7f293a6606d0 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f2944d0882b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f2944cb717b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7f2944b1f046 in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7f2944b284bb in () at /lib64/libQt5Core.so.5 #9 0x7f293ce7c58e in start_thread () at /lib64/libpthread.so.0 #10 0x7f2944a3 in clone () at /lib64/libc.so.6 Thread 33 (Thread 0x7f290d7fa700 (LWP 29904)): #0 0x7ffef51829b7 in () #1 0x7ffef5182bbc in clock_gettime () #2 0x7f2944674692 in clock_gettime () at /lib64/libc.so.6 #3 0x7f2944d08035 in () at /lib64/libQt5Core.so.5 #4 0x7f2944d06b1d in QTimerInfoList::updateCurrentTime() () at /lib64/libQt5Core.so.5 #5 0x7f2944d06f29 in QTimerInfoList::timerWait(timespec&) () at /lib64/libQt5Core.so.5 #6 0x7f2944d084e4 in () at /lib64/libQt5Core.so.5 #7 0x7f2944d08592 in () at /lib64/libQt5Core.so.5 #8 0x7f293a65fae9 in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #9 0x7f293a6604db in () at /lib64/libglib-2.0.so.0 #10 0x7f293a6606d0 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #11 0x7f2944d0882b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #12 0x7f2944cb717b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #13 0x7f2944b1f046 in QThread::exec() () at /lib64/libQt5Core.so.5 #14 0x7f2944b284bb in () at /lib64/libQt5Core.so.5 #15 0x7f293ce7c58e in start_thread () at /lib64/libpthread.so.0 #16 0x7f2944a3 in clone () at /lib64/libc.so.6 Thread 32 (Thread 0x7f280bcec700 (LWP 28494)): #0 0x7f293a6a7ebd in g_mutex_lock () at /lib64/libglib-2.0.so.0 #1 0x7f293a66058c in () at /lib64/libglib-2.0.so.0 #2 0x7f293a6606d0 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f2944d0882b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f2944cb717b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f2944b1f046 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f2944b284bb in () at /lib64/libQt5Core.so.5 #7 0x7f293ce7c58e in start_thread () at /lib64/libpthread.so.0 #8 0x7f2944a3 in clone () at /lib64/libc.so.6 Thread 31 (Thread 0x7f290cff9700 (LWP 28449)): #0
[kontact] [Bug 402127] New: Crash after clicking on feeds after disabling and enabling it
https://bugs.kde.org/show_bug.cgi?id=402127 Bug ID: 402127 Summary: Crash after clicking on feeds after disabling and enabling it Product: kontact Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: k...@sedrubal.de Target Milestone: --- Application: kontact (5.9.3) Qt Version: 5.11.1 Frameworks Version: 5.52.0 Operating System: Linux 4.19.8-300.fc29.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I disabled the feeds app in kontact settings and enabled it afterwards. When I click on the icon in the left side bar in kontact, kontact crashes. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f01c95cc340 (LWP 19584))] Thread 33 (Thread 0x7f01957fa700 (LWP 25608)): #0 0x7f01cd587b68 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f01cff0fce7 in () at /lib64/libQt5WebEngineCore.so.5 #2 0x7f01cff119ba in () at /lib64/libQt5WebEngineCore.so.5 #3 0x7f01cff11aa2 in () at /lib64/libQt5WebEngineCore.so.5 #4 0x7f01cff16861 in () at /lib64/libQt5WebEngineCore.so.5 #5 0x7f01cff17d41 in () at /lib64/libQt5WebEngineCore.so.5 #6 0x7f01cff22171 in () at /lib64/libQt5WebEngineCore.so.5 #7 0x7f01cd58158e in start_thread () at /lib64/libpthread.so.0 #8 0x7f01d4d6b6a3 in clone () at /lib64/libc.so.6 Thread 32 (Thread 0x7f0196ffd700 (LWP 23218)): #0 0x7f01d4d60421 in poll () at /lib64/libc.so.6 #1 0x7f01cad655a6 in () at /lib64/libglib-2.0.so.0 #2 0x7f01cad656d0 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f01d540d82b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f01d53bc17b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f01d5224046 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f01d522d4bb in () at /lib64/libQt5Core.so.5 #7 0x7f01cd58158e in start_thread () at /lib64/libpthread.so.0 #8 0x7f01d4d6b6a3 in clone () at /lib64/libc.so.6 Thread 31 (Thread 0x7f0099bcb700 (LWP 21976)): #0 0x7f01b059a7ee in pa_mainloop_prepare () at /lib64/libpulse.so.0 #1 0x7f01b059b294 in pa_mainloop_iterate () at /lib64/libpulse.so.0 #2 0x7f01b059b350 in pa_mainloop_run () at /lib64/libpulse.so.0 #3 0x7f01b05a95bd in thread () at /lib64/libpulse.so.0 #4 0x7f01b054606c in internal_thread_func () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #5 0x7f01cd58158e in start_thread () at /lib64/libpthread.so.0 #6 0x7f01d4d6b6a3 in clone () at /lib64/libc.so.6 Thread 30 (Thread 0x7f00850ba700 (LWP 19729)): #0 0x7f01d4d5bf84 in read () at /lib64/libc.so.6 #1 0x7f01cadabaa0 in () at /lib64/libglib-2.0.so.0 #2 0x7f01cad6509b in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f01cad65550 in () at /lib64/libglib-2.0.so.0 #4 0x7f01cad656d0 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f01d540d82b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f01d53bc17b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7f01d5224046 in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7f01d522d4bb in () at /lib64/libQt5Core.so.5 #9 0x7f01cd58158e in start_thread () at /lib64/libpthread.so.0 #10 0x7f01d4d6b6a3 in clone () at /lib64/libc.so.6 Thread 29 (Thread 0x7f00858bb700 (LWP 19726)): #0 0x7f01d4d60421 in poll () at /lib64/libc.so.6 #1 0x7f01cad655a6 in () at /lib64/libglib-2.0.so.0 #2 0x7f01cad656d0 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f01d540d82b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f01d53bc17b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f01d5224046 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f01d522d4bb in () at /lib64/libQt5Core.so.5 #7 0x7f01cd58158e in start_thread () at /lib64/libpthread.so.0 #8 0x7f01d4d6b6a3 in clone () at /lib64/libc.so.6 Thread 28 (Thread 0x7f009ae49700 (LWP 19697)): #0 0x7f01cd587b68 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f01cff0fce7 in () at /lib64/libQt5WebEngineCore.so.5 #2 0x7f01cff119ba in () at /lib64/libQt5WebEngineCore.so.5 #3 0x7f01cff11aa2 in () at /lib64/libQt5WebEngineCore.so.5 #4 0x7f01cff16861 in () at /lib64/libQt5WebEngineCore.so.5 #5 0x7f01cff17d41 in () at /lib64/libQt5WebEngineCore.so.5 #6 0x7f01cff22171 in () at
[kontact] [Bug 377115] Disabling journal turns To-do List into calendar
https://bugs.kde.org/show_bug.cgi?id=377115 sedrubal changed: What|Removed |Added Version|5.4.1 |5.9.2 --- Comment #1 from sedrubal --- Can anyone reproduce this? It still affects me. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 402125] New: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
https://bugs.kde.org/show_bug.cgi?id=402125 Bug ID: 402125 Summary: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString, QString,QString) Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: k...@sedrubal.de Target Milestone: --- SUMMARY When I start akonadi (akonadictl restart) I see the warning: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) It also appears in some error log files like ~/.local/share/akonadi/akonadi_control.error STEPS TO REPRODUCE 1. akonadictl stop 2. akonadictl start OBSERVED RESULT The warning will be printed. EXPECTED RESULT No deprecated signals should be used, I think. SOFTWARE/OS VERSIONS Akonadi version: 5.9.3 Linux: Fedora 29 KDE Plasma Version: 5.14.4 KDE Frameworks Version: ? Qt Version: 5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 401736] New: Crash, when closing program in konsole
https://bugs.kde.org/show_bug.cgi?id=401736 Bug ID: 401736 Summary: Crash, when closing program in konsole Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: k...@sedrubal.de Target Milestone: --- Application: kdeinit5 (18.08.1) Qt Version: 5.11.1 Frameworks Version: 5.52.0 Operating System: Linux 4.19.5-300.fc29.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I ran neovim in the konsole (without an intermediate shell like bash or zsh) and close neovim using :q. This happens, when you create a launcher and check the checkbox "Run in terminal". The crash can be reproduced every time. -- Backtrace: Application: Konsole (kdeinit5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f74cddb5940 (LWP 10122))] Thread 4 (Thread 0x7f74b6bc5700 (LWP 10126)): #0 0x7f74d05de77c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f74b787f8c3 in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7f74b787f61b in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7f74d05d858e in start_thread () from /lib64/libpthread.so.0 #4 0x7f74d07ab6a3 in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f74bdc9e700 (LWP 10125)): #0 0x7f74d07a0516 in ppoll () from /lib64/libc.so.6 #1 0x7f74d0e4bbf5 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /lib64/libQt5Core.so.5 #2 0x7f74d0e4cd49 in QEventDispatcherUNIX::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #3 0x7f74d0dfe17b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f74d0c66046 in QThread::exec() () from /lib64/libQt5Core.so.5 #5 0x7f74d1dcef89 in ?? () from /lib64/libQt5DBus.so.5 #6 0x7f74d0c6f4bb in ?? () from /lib64/libQt5Core.so.5 #7 0x7f74d05d858e in start_thread () from /lib64/libpthread.so.0 #8 0x7f74d07ab6a3 in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f74bf25b700 (LWP 10124)): #0 0x7f74d07a0421 in poll () from /lib64/libc.so.6 #1 0x7f74d1c5439f in ?? () from /lib64/libxcb.so.1 #2 0x7f74d1c5601a in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f74bf3cada9 in ?? () from /lib64/libQt5XcbQpa.so.5 #4 0x7f74d0c6f4bb in ?? () from /lib64/libQt5Core.so.5 #5 0x7f74d05d858e in start_thread () from /lib64/libpthread.so.0 #6 0x7f74d07ab6a3 in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f74cddb5940 (LWP 10122)): [KCrash Handler] #6 0x7f74c0bdd324 in QHash::findNode (this=this@entry=0x10, akey=@0x7e7cc1e0: Konsole::Profile::Font, ahp=ahp@entry=0x0) at /usr/include/qt5/QtCore/qhash.h:926 #7 0x7f74c0c30572 in QHash::contains (akey=@0x7e7cc1e0: Konsole::Profile::Font, this=0x10) at /usr/include/qt5/QtCore/qhash.h:904 #8 Konsole::Profile::property (p=, this=) at /usr/src/debug/konsole5-18.08.1-1.fc29.x86_64/src/Profile.h:670 #9 Konsole::Profile::property (p=Konsole::Profile::Font, this=) at /usr/src/debug/konsole5-18.08.1-1.fc29.x86_64/src/Profile.h:664 #10 Konsole::Profile::font (this=) at /usr/src/debug/konsole5-18.08.1-1.fc29.x86_64/src/Profile.h:443 #11 Konsole::SessionManager::sessionProfileCommandReceived (this=0x7f74c0cbed20 <(anonymous namespace)::Q_QGS_theSessionManager::innerFunction()::holder>, text=...) at /usr/src/debug/konsole5-18.08.1-1.fc29.x86_64/src/SessionManager.cpp:293 #12 0x7f74d0e27513 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #13 0x7f74c0c64a79 in Konsole::Session::profileChangeCommandReceived (this=this@entry=0x55f1dc8db8b0, _t1=...) at /usr/src/debug/konsole5-18.08.1-1.fc29.x86_64/x86_64-redhat-linux-gnu/src/konsoleprivate_autogen/EWIEGA46WW/moc_Session.cpp:774 #14 0x7f74c0c1525f in Konsole::Session::setSessionAttribute (this=0x55f1dc8db8b0, what=50, caption=...) at /usr/src/debug/konsole5-18.08.1-1.fc29.x86_64/src/Session.cpp:572 #15 0x7f74d0e27513 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #16 0x7f74c0c63a3a in Konsole::Emulation::sessionAttributeChanged (this=this@entry=0x55f1dc903920, _t1=, _t1@entry=50, _t2=...) at /usr/src/debug/konsole5-18.08.1-1.fc29.x86_64/x86_64-redhat-linux-gnu/src/konsoleprivate_autogen/EWIEGA46WW/moc_Emulation.cpp:532 #17 0x7f74c0c5ebe9 in Konsole::Vt102Emulation::updateSessionAttributes (this=0x55f1dc903920) at /usr/include/qt5/QtCore/qhash.h:158 #18 0x7f74d0e27513 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #19 0x7f74d0e331bb in QTimer::timeout(QTimer::QPrivateSignal) () from /lib64/libQt5Core.so.5 #20 0x7f74d0e280ab in QObject::event(QEvent*)
[Oxygen] [Bug 299736] dolphin crashes on file copying
https://bugs.kde.org/show_bug.cgi?id=299736 sedrubal changed: What|Removed |Added CC|k...@sedrubal.de | -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 399848] New: Closing neovim in terminal crashes konsole
https://bugs.kde.org/show_bug.cgi?id=399848 Bug ID: 399848 Summary: Closing neovim in terminal crashes konsole Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: k...@sedrubal.de Target Milestone: --- Application: kdeinit5 (18.08.1) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.18.12-300.fc29.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I have neovim installed which installs a .desktop file with `Terminal=true`. Clicking on that desktop icon opens nvim in a konsole terminal window. When I close neovim (with :q), konsole sometimes closes normally but sometimes it crashes. The crash can be reproduced sometimes. -- Backtrace: Application: Konsole (kdeinit5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7eff56282940 (LWP 8867))] Thread 4 (Thread 0x7eff3f494700 (LWP 8872)): #0 0x7eff58aa567c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7eff3f8efa43 in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7eff3f8ef79b in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7eff58a9f58e in start_thread () from /lib64/libpthread.so.0 #4 0x7eff58c71513 in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7eff46406700 (LWP 8871)): #0 0x7eff58c663f6 in ppoll () from /lib64/libc.so.6 #1 0x7eff59311e85 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /lib64/libQt5Core.so.5 #2 0x7eff59312fd9 in QEventDispatcherUNIX::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #3 0x7eff592c439b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7eff5912bf16 in QThread::exec() () from /lib64/libQt5Core.so.5 #5 0x7eff5a29ec89 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #6 0x7eff591353ab in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7eff58a9f58e in start_thread () from /lib64/libpthread.so.0 #8 0x7eff58c71513 in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7eff479b8700 (LWP 8870)): #0 0x7eff58c66301 in poll () from /lib64/libc.so.6 #1 0x7eff5a12639f in ?? () from /lib64/libxcb.so.1 #2 0x7eff5a12801a in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7eff47b23b79 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x7eff591353ab in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7eff58a9f58e in start_thread () from /lib64/libpthread.so.0 #6 0x7eff58c71513 in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7eff56282940 (LWP 8867)): [KCrash Handler] #6 0x7eff49321324 in QHash::findNode (this=this@entry=0x10, akey=@0x7ffed8baae20: Konsole::Profile::Font, ahp=ahp@entry=0x0) at /usr/include/qt5/QtCore/qhash.h:926 #7 0x7eff49374572 in QHash::contains (akey=@0x7ffed8baae20: Konsole::Profile::Font, this=0x10) at /usr/include/qt5/QtCore/qhash.h:904 #8 Konsole::Profile::property (p=, this=) at /usr/src/debug/konsole5-18.08.1-1.fc29.x86_64/src/Profile.h:670 #9 Konsole::Profile::property (p=Konsole::Profile::Font, this=) at /usr/src/debug/konsole5-18.08.1-1.fc29.x86_64/src/Profile.h:664 #10 Konsole::Profile::font (this=) at /usr/src/debug/konsole5-18.08.1-1.fc29.x86_64/src/Profile.h:443 #11 Konsole::SessionManager::sessionProfileCommandReceived (this=0x7eff49402d20 <(anonymous namespace)::Q_QGS_theSessionManager::innerFunction()::holder>, text=...) at /usr/src/debug/konsole5-18.08.1-1.fc29.x86_64/src/SessionManager.cpp:293 #12 0x7eff592ed763 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #13 0x7eff493a8a79 in Konsole::Session::profileChangeCommandReceived (this=this@entry=0x55e52ffda130, _t1=...) at /usr/src/debug/konsole5-18.08.1-1.fc29.x86_64/x86_64-redhat-linux-gnu/src/konsoleprivate_autogen/EWIEGA46WW/moc_Session.cpp:774 #14 0x7eff4935925f in Konsole::Session::setSessionAttribute (this=0x55e52ffda130, what=50, caption=...) at /usr/src/debug/konsole5-18.08.1-1.fc29.x86_64/src/Session.cpp:572 #15 0x7eff592ed763 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #16 0x7eff493a7a3a in Konsole::Emulation::sessionAttributeChanged (this=this@entry=0x55e530006340, _t1=, _t1@entry=50, _t2=...) at /usr/src/debug/konsole5-18.08.1-1.fc29.x86_64/x86_64-redhat-linux-gnu/src/konsoleprivate_autogen/EWIEGA46WW/moc_Emulation.cpp:532 #17 0x7eff493a2be9 in Konsole::Vt102Emulation::updateSessionAttributes (this=0x55e530006340) at /usr/include/qt5/QtCore/qhash.h:158 #18 0x7eff592ed763 in QMetaObject::activate(QObject*, int, int, void**) () from
[frameworks-kio] [Bug 355662] Wrong error message: Access denied to .../Trash/...
https://bugs.kde.org/show_bug.cgi?id=355662 sedrubal changed: What|Removed |Added CC||k...@sedrubal.de --- Comment #2 from sedrubal --- I'm running fedora 28 which packages plasma 5.13.4 right now (afaik). Here this bug is still present. You should be able to reproduce the issue yourself by executing the 3 steps I posted above. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377840] [Wayland] Shows windows from all activities and desktops, doesn't respect settings that should disable this functionality
https://bugs.kde.org/show_bug.cgi?id=377840 sedrubal changed: What|Removed |Added Version|5.9.3 |5.12.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377840] [Wayland] Shows windows from all activities and desktops, doesn't respect settings that should disable this functionality
https://bugs.kde.org/show_bug.cgi?id=377840 sedrubal changed: What|Removed |Added CC||k...@sedrubal.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395228] New: Crash when adding widget in wayland session
https://bugs.kde.org/show_bug.cgi?id=395228 Bug ID: 395228 Summary: Crash when adding widget in wayland session Product: plasmashell Version: 5.12.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: k...@sedrubal.de CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.5) Qt Version: 5.10.1 Frameworks Version: 5.46.0 Operating System: Linux 4.16.14-300.fc28.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I tried to add a Widget in a wayland session, but as soon as the widget menu should open (right click on desktop, "Add widgets...", or Alt+D, A), plasmashell crashes. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2864768940 (LWP 1786))] Thread 18 (Thread 0x7f276bfff700 (LWP 3400)): #0 0x7f286ff6952c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f28718ea83b in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f287570f4e9 in QSGRenderThread::processEventsAndWaitForMore() () at /lib64/libQt5Quick.so.5 #3 0x7f287570f952 in QSGRenderThread::run() () at /lib64/libQt5Quick.so.5 #4 0x7f28718ea11d in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f286ff63594 in start_thread () at /lib64/libpthread.so.0 #6 0x7f2870c2700f in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7f27813b3700 (LWP 3387)): #0 0x7f286ff6952c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f28718ea83b in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f287570f4e9 in QSGRenderThread::processEventsAndWaitForMore() () at /lib64/libQt5Quick.so.5 #3 0x7f287570f952 in QSGRenderThread::run() () at /lib64/libQt5Quick.so.5 #4 0x7f28718ea11d in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f286ff63594 in start_thread () at /lib64/libpthread.so.0 #6 0x7f2870c2700f in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7f276affd700 (LWP 3386)): #0 0x7f286951448d in g_mutex_lock () at /lib64/libglib-2.0.so.0 #1 0x7f28694cdbae in () at /lib64/libglib-2.0.so.0 #2 0x7f28694cdd10 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f2871ae8c2b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f2871a9712b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f28718e59c6 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f2874cbf339 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7f28718ea11d in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f286ff63594 in start_thread () at /lib64/libpthread.so.0 #9 0x7f2870c2700f in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7f276b7fe700 (LWP 3380)): #0 0x7f286ff6952c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f28718ea83b in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f287570f4e9 in QSGRenderThread::processEventsAndWaitForMore() () at /lib64/libQt5Quick.so.5 #3 0x7f287570f952 in QSGRenderThread::run() () at /lib64/libQt5Quick.so.5 #4 0x7f28718ea11d in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f286ff63594 in start_thread () at /lib64/libpthread.so.0 #6 0x7f2870c2700f in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7f2768ff9700 (LWP 3348)): #0 0x7f286ff6952c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f28718ea83b in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f287570f4e9 in QSGRenderThread::processEventsAndWaitForMore() () at /lib64/libQt5Quick.so.5 #3 0x7f287570f952 in QSGRenderThread::run() () at /lib64/libQt5Quick.so.5 #4 0x7f28718ea11d in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f286ff63594 in start_thread () at /lib64/libpthread.so.0 #6 0x7f2870c2700f in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7f27697fa700 (LWP 3235)): #0 0x7f286ff6952c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f28718ea83b in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f287570f4e9 in QSGRenderThread::processEventsAndWaitForMore() () at /lib64/libQt5Quick.so.5 #3 0x7f287570f952 in QSGRenderThread::run() () at /lib64/libQt5Quick.so.5 #4 0x7f28718ea11d in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f286ff63594 in
[kmail2] [Bug 394740] Folder list columns visibility not persistent
https://bugs.kde.org/show_bug.cgi?id=394740 sedrubal <k...@sedrubal.de> changed: What|Removed |Added CC||k...@sedrubal.de --- Comment #1 from sedrubal <k...@sedrubal.de> --- Created attachment 112904 --> https://bugs.kde.org/attachment.cgi?id=112904=edit The folder list in its default(?) configuration - imho quite useless -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 394740] New: Folder list columns visibility not persistent
https://bugs.kde.org/show_bug.cgi?id=394740 Bug ID: 394740 Summary: Folder list columns visibility not persistent Product: kmail2 Version: 5.7.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: k...@sedrubal.de Target Milestone: --- Created attachment 112903 --> https://bugs.kde.org/attachment.cgi?id=112903=edit The column configuration drop down Since about a month the configuration, which columns should be displayed in the folder (and account) list (on the left) is not beeing restored after quitting and starting kmail. After every start I configure to no show the "Unread", "Total" and "Size" column in the dropdown (see attachment), but they appear on the next start again. It seems that kmail had a similar issue the other way round: Bug 190838 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 391675] Discover crashes after click on non existent app
https://bugs.kde.org/show_bug.cgi?id=391675 --- Comment #4 from sedrubal <k...@sedrubal.de> --- I was on fedora 28 alpha and it was a confirmed bug. I found no way to easily reproduce it so I think, I can't provide a useful backtrace. As this seems to happen only under special circumstances, you can close this issue, if you want. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 392816] New: Crash when changing Login Manager Background image
https://bugs.kde.org/show_bug.cgi?id=392816 Bug ID: 392816 Summary: Crash when changing Login Manager Background image Product: systemsettings Version: 5.12.4 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: k...@sedrubal.de Target Milestone: --- Application: systemsettings5 (5.12.4) Qt Version: 5.10.1 Frameworks Version: 5.44.0 Operating System: Linux 4.16.0-0.rc7.git0.1.fc28.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I changed the background image of the login manager (sddm) using systemsettings5. After clicking on apply I entered my password and then it crashed. The crash can be reproduced sometimes. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcdfbe78940 (LWP 17628))] Thread 8 (Thread 0x7fcdbd303700 (LWP 17961)): #0 0x7fcdfec4b9b0 in g_source_iter_next () at /lib64/libglib-2.0.so.0 #1 0x7fcdfec4df93 in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #2 0x7fcdfec4ea4b in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x7fcdfec4ec40 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7fce07060c2b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fcdb8012710, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7fce0700f12b in QEventLoop::exec(QFlags) (this=0x7fcdbd302c40, flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:71 #6 0x7fce06e5d9c6 in QThread::exec() (this=) at thread/qthread.cpp:522 #7 0x7fce0535d339 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #8 0x7fce06e6211d in QThreadPrivate::start(void*) (arg=0x55f1b16c9ba0) at thread/qthread_unix.cpp:376 #9 0x7fce03972564 in start_thread () at /lib64/libpthread.so.0 #10 0x7fce0619f31f in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7fcdcc9a1700 (LWP 17956)): #0 0x7fce06194929 in poll () at /lib64/libc.so.6 #1 0x7fcdfec4eb16 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fcdfec4eed2 in g_main_loop_run () at /lib64/libglib-2.0.so.0 #3 0x7fcdbfb2b66a in gdbus_shared_thread_func () at /lib64/libgio-2.0.so.0 #4 0x7fcdfec76cda in g_thread_proxy () at /lib64/libglib-2.0.so.0 #5 0x7fce03972564 in start_thread () at /lib64/libpthread.so.0 #6 0x7fce0619f31f in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fcdcdbe4700 (LWP 17955)): #0 0x7fce06190374 in read () at /lib64/libc.so.6 #1 0x7fcdfec93df0 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7fcdfec4e60b in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7fcdfec4eac0 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7fcdfec4ec40 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7fcdfec4ec91 in glib_worker_main () at /lib64/libglib-2.0.so.0 #6 0x7fcdfec76cda in g_thread_proxy () at /lib64/libglib-2.0.so.0 #7 0x7fce03972564 in start_thread () at /lib64/libpthread.so.0 #8 0x7fce0619f31f in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fcdcfde1700 (LWP 17634)): #0 0x7fce06194929 in poll () at /lib64/libc.so.6 #1 0x7fcdfec4eb16 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fcdfec4ec40 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fce07060c2b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fcdc8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fce0700f12b in QEventLoop::exec(QFlags) (this=0x7fcdcfde0c40, flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:71 #5 0x7fce06e5d9c6 in QThread::exec() (this=) at thread/qthread.cpp:522 #6 0x7fce0535d339 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7fce06e6211d in QThreadPrivate::start(void*) (arg=0x55f1ae7e3df0) at thread/qthread_unix.cpp:376 #8 0x7fce03972564 in start_thread () at /lib64/libpthread.so.0 #9 0x7fce0619f31f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fcdd66f6700 (LWP 17633)): #0 0x7fce06194929 in poll () at /lib64/libc.so.6 #1 0x7fcdfec4eb16 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fcdfec4ec40 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fce07060c2b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fcddb20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fce0700f12b in QEventLoop::exec(QFlags) (this=0x7fcdd66f5c40, flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:71 #5 0x7fce06e5d9c6 in QThread::exec() (this=) at thread/qthread.cpp:522 #6
[dolphin] [Bug 392633] New: Crash when copying from FTP and connection gets lost
https://bugs.kde.org/show_bug.cgi?id=392633 Bug ID: 392633 Summary: Crash when copying from FTP and connection gets lost Product: dolphin Version: 17.12.2 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: k...@sedrubal.de CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (17.12.2) Qt Version: 5.10.1 Frameworks Version: 5.44.0 Operating System: Linux 4.16.0-0.rc7.git0.1.fc28.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I downloaded some files from a FTP server, then there was an error (don't know why) and before I clicked retry the FTP server turned down. Then there was a crash. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f33d2de92c0 (LWP 19112))] Thread 3 (Thread 0x7f33b379b700 (LWP 19116)): #0 0x7f33df9d2374 in read () from /lib64/libc.so.6 #1 0x7f33d809cdf0 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0 #2 0x7f33d805760b in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x7f33d8057ac0 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #4 0x7f33d8057c40 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f33e08a2c2b in QEventDispatcherGlib::processEvents (this=0x7f33ac000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f33e085112b in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:71 #7 0x7f33e069f9c6 in QThread::exec() () at thread/qthread.cpp:522 #8 0x7f33e06a411d in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:376 #9 0x7f33dcbbc564 in start_thread () from /lib64/libpthread.so.0 #10 0x7f33df9e131f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f33c27cc700 (LWP 19115)): #0 0x7f33df9d6929 in poll () from /lib64/libc.so.6 #1 0x7f33d8057b16 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f33d8057c40 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f33e08a2c2b in QEventDispatcherGlib::processEvents (this=0x7f33b4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f33e085112b in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:71 #5 0x7f33e069f9c6 in QThread::exec() () at thread/qthread.cpp:522 #6 0x7f33e20fb299 in QDBusConnectionManager::run (this=0x7f33e2172060 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #7 0x7f33e06a411d in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:376 #8 0x7f33dcbbc564 in start_thread () from /lib64/libpthread.so.0 #9 0x7f33df9e131f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f33d2de92c0 (LWP 19112)): [KCrash Handler] #6 0x7f33e3074098 in KIO::Slave::deref() () from /lib64/libKF5KIOCore.so.5 #7 0x7f33e307456d in KIO::Slave::gotInput() () from /lib64/libKF5KIOCore.so.5 #8 0x7f33e310acb5 in KIO::Slave::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /lib64/libKF5KIOCore.so.5 #9 0x7f33e087acbe in QMetaObject::activate(QObject*, int, int, void**) () at kernel/qobject.cpp:3767 #10 0x7f33e30026e3 in KIO::ConnectionPrivate::dequeue() [clone .part.20] () from /lib64/libKF5KIOCore.so.5 #11 0x7f33e087ba26 in QObject::event(QEvent*) () at kernel/qobject.cpp:1247 #12 0x7f33e15dce95 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #13 0x7f33e15e483a in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #14 0x7f33e0852376 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at kernel/qcoreapplication.cpp:1050 #15 0x7f33e085509b in QCoreApplication::sendEvent (event=0x555d318712a0, receiver=0x1) at kernel/qcoreapplication.h:234 #16 QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at kernel/qcoreapplication.cpp:1740 #17 0x7f33e08554ec in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1594 #18 0x7f33e08a2ec7 in postEventSourceDispatch (s=0x555d31276ed0) at kernel/qeventdispatcher_glib.cpp:276 #19 0x7f33d80577dd in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #20 0x7f33d8057ba8 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #21 0x7f33d8057c40 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #22 0x7f33e08a2c13 in QEventDispatcherGlib::processEvents (this=0x555d31219030, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #23
[kmail2] [Bug 376286] Add a "Mark as read" button in the new mail notification
https://bugs.kde.org/show_bug.cgi?id=376286 --- Comment #2 from sedrubal <k...@sedrubal.de> --- +1. I'd also suggest an additional "Delete" button, for arriving spam. These buttons in notifications are one of my favourite features in k9 mail. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 376286] Add a "Mark as read" button in the new mail notification
https://bugs.kde.org/show_bug.cgi?id=376286 sedrubal <k...@sedrubal.de> changed: What|Removed |Added CC||k...@sedrubal.de -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 391675] Discover crashes after click on non existent app
https://bugs.kde.org/show_bug.cgi?id=391675 sedrubal <k...@sedrubal.de> changed: What|Removed |Added CC||k...@sedrubal.de --- Comment #2 from sedrubal <k...@sedrubal.de> --- I'm sorry, I think I can't provide a better backtrace, as drkonqi and gdb are crashing all the time. I could reproduce it sometimes when I added a typo in the metalink URL in one of the enabled repos in /etc/yum.repos.d/ (in order that an error must be thrown when some programm uses it), starting discover and clicking on a package, that was available in this repository. Discover seems to remove all the apps from this repo but when you click on one of them before discover removes it, it crashes... -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392243] Notifications for new mails not click-able anymore
https://bugs.kde.org/show_bug.cgi?id=392243 --- Comment #4 from sedrubal <k...@sedrubal.de> --- Yes, that would be like notifications of other applications are working (e.g. Firefox). Is there any chance that this will be changed? Otherwise you can close this issue. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392243] Notifications for new mails not click-able anymore
https://bugs.kde.org/show_bug.cgi?id=392243 sedrubal <k...@sedrubal.de> changed: What|Removed |Added CC||k...@sedrubal.de --- Comment #2 from sedrubal <k...@sedrubal.de> --- Oops thanks. I'd suggest to enable this by default. Or is there any disadvantage in showing these buttons? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 392341] New: Zooming not possible in neovim when guicursor enabled
https://bugs.kde.org/show_bug.cgi?id=392341 Bug ID: 392341 Summary: Zooming not possible in neovim when guicursor enabled Product: konsole Version: 17.12.2 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: k...@sedrubal.de Target Milestone: --- When neovim is opened in konsole and guicursor is set (to `guicursor=n-v-c-sm:block,i-ci-ve:ver25,r-cr-o:hor20,a:blinkon0` which is default) it is not possible to zoom any more using Ctrl + mouse wheel as the zoom level jumps back to the original level all the time. `:set guicursor=` fixes the problem, but then the cursor remains a block all the time (nvim usually sets the cursor to a beam when it is in insert mode). I think this bug may be related to Bug 347323 but I'm not sure. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 347323] Add support for changing cursor shape with extended DECSCUSR escape sequences
https://bugs.kde.org/show_bug.cgi?id=347323 sedrubal <k...@sedrubal.de> changed: What|Removed |Added CC||k...@sedrubal.de -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392243] New: Notifications for new mails not click-able anymore
https://bugs.kde.org/show_bug.cgi?id=392243 Bug ID: 392243 Summary: Notifications for new mails not click-able anymore Product: kmail2 Version: 5.7.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: k...@sedrubal.de Target Milestone: --- Since some time it seems like you can't open new mails when they arrive by clicking on their notification. I think formerly there was a button which opened the mail directly (see Bug 374917). (plasmashell 5.12.3) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 391675] New: Discover crashes after click on non existent app
https://bugs.kde.org/show_bug.cgi?id=391675 Bug ID: 391675 Summary: Discover crashes after click on non existent app Product: Discover Version: 5.12.2 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: k...@sedrubal.de Target Milestone: --- Application: plasma-discover (5.12.2) Qt Version: 5.10.1 Frameworks Version: 5.44.0 Operating System: Linux 4.16.0-0.rc3.git0.1.fc28.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - Unusual behavior I noticed: Discover tried to update packae info from a repository that is currently broken (according to the alert). Then Discover does not have any package info and does not show any application in the "Applications" section. Most of the apps disappear on the start page after that. - What I was doing when the application crashed: ...but not all apps disappear (~5 apps remain there). When you click on one of them, discover crashes. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa7beb33300 (LWP 21348))] Thread 13 (Thread 0x7fa765a3d700 (LWP 21395)): #0 0x7fa7b99df949 in poll () from /lib64/libc.so.6 #1 0x7fa7b2a79ab6 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7fa7b2a79be0 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7fa7ba8abc2b in QEventDispatcherGlib::processEvents (this=0x7fa75c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fa7ba85a12b in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:71 #5 0x7fa7ba6a89c6 in QThread::exec() () at thread/qthread.cpp:522 #6 0x7fa7ba6ad11d in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:376 #7 0x7fa7b79c6564 in start_thread () from /lib64/libpthread.so.0 #8 0x7fa7b99ea33f in clone () from /lib64/libc.so.6 Thread 12 (Thread 0x7fa766308700 (LWP 21394)): #0 0x7fa7b99db394 in read () from /lib64/libc.so.6 #1 0x7fa7b2abf000 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0 #2 0x7fa7b2a795ab in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x7fa7b2a79a60 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #4 0x7fa7b2a79be0 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7fa7ba8abc2b in QEventDispatcherGlib::processEvents (this=0x7fa758000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7fa7ba85a12b in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:71 #7 0x7fa7ba6a89c6 in QThread::exec() () at thread/qthread.cpp:522 #8 0x7fa7ba6ad11d in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:376 #9 0x7fa7b79c6564 in start_thread () from /lib64/libpthread.so.0 #10 0x7fa7b99ea33f in clone () from /lib64/libc.so.6 Thread 11 (Thread 0x7fa766d5a700 (LWP 21360)): #0 0x7fa7b2ac041d in g_mutex_lock () from /lib64/libglib-2.0.so.0 #1 0x7fa7b2a79bcc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #2 0x7fa7ba8abc2b in QEventDispatcherGlib::processEvents (this=0x7fa76b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #3 0x7fa7ba85a12b in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:71 #4 0x7fa7ba6a89c6 in QThread::exec() () at thread/qthread.cpp:522 #5 0x7fa7ba6ad11d in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:376 #6 0x7fa7b79c6564 in start_thread () from /lib64/libpthread.so.0 #7 0x7fa7b99ea33f in clone () from /lib64/libc.so.6 Thread 10 (Thread 0x7fa77cae2700 (LWP 21358)): #0 0x7fa7b79cc8e8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa7ba6ad736 in QWaitConditionPrivate::wait_relative (time=3, this=0x7fa768005910) at thread/qwaitcondition_unix.cpp:133 #2 QWaitConditionPrivate::wait (time=3, this=0x7fa768005910) at thread/qwaitcondition_unix.cpp:141 #3 QWaitCondition::wait (this=this@entry=0x7fa7680056d0, mutex=mutex@entry=0x7fa768005450, time=3) at thread/qwaitcondition_unix.cpp:215 #4 0x7fa7ba6aa662 in QThreadPoolThread::run() () at ../../include/QtCore/../../src/corelib/thread/qmutex.h:240 #5 0x7fa7ba6ad11d in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:376 #6 0x7fa7b79c6564 in start_thread () from /lib64/libpthread.so.0 #7 0x7fa7b99ea33f in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7fa77d2e3700 (LWP 21357)): #0 0x7fa7b2ac041d in g_mutex_lock () from /lib64/libglib-2.0.so.0 #1 0x7fa7b2a7964a in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #2
[knetworkmanager] [Bug 276378] 802.1X GUI doesn't allow to specify the server name
https://bugs.kde.org/show_bug.cgi?id=276378 sedrubal <k...@sedrubal.de> changed: What|Removed |Added CC||k...@sedrubal.de -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 386689] New: Add option "Domain" for "802.1x Security"
https://bugs.kde.org/show_bug.cgi?id=386689 Bug ID: 386689 Summary: Add option "Domain" for "802.1x Security" Product: plasma-nm Version: 5.10.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: editor Assignee: jgrul...@redhat.com Reporter: k...@sedrubal.de Target Milestone: --- Bug 276378 says it was implemented in 2011 but I can't find the option to specify the server name (CN) of the 802.1X server certificate. Network Manager, nm-connection-editor, Windows, MaxOS and Android >7 all support this feature, but plasma-nm and the gnome front end do not. Without this verification there is (almost) no security for 802.1X. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 385967] New: Increase maximum value for "Size in Bytes" in search
https://bugs.kde.org/show_bug.cgi?id=385967 Bug ID: 385967 Summary: Increase maximum value for "Size in Bytes" in search Product: kmail2 Version: 5.5.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: search Assignee: kdepim-b...@kde.org Reporter: k...@sedrubal.de Target Milestone: --- Currently you can not select a value greater than 99.99kB in the search field "Size in Bytes" in the search dialog. The maximum value should be at least 1TB (like in thunderbird). Example use case: Your quota is reached and you have to delete the biggest mails. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 356517] Message window displays no content for multipart HTML emails with empty text/plain section when HTML is not preferred over "text-only"
https://bugs.kde.org/show_bug.cgi?id=356517 --- Comment #2 from sedrubal <k...@sedrubal.de> --- Another problem is, that one html mime part with global style can also change an other mime part (even if it is a text/plain mime part). Use case: mailman sends plain text emails to ask list admins for approval and attaches the original email. If this is a malicious html email, it can manipulate the mailman mail. May using iframes for every mime part be a solution? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 356517] Message window displays no content for multipart HTML emails with empty text/plain section when HTML is not preferred over "text-only"
https://bugs.kde.org/show_bug.cgi?id=356517 sedrubal <k...@sedrubal.de> changed: What|Removed |Added CC||k...@sedrubal.de -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 384929] New: Detect captive portals
https://bugs.kde.org/show_bug.cgi?id=384929 Bug ID: 384929 Summary: Detect captive portals Product: Akonadi Version: 5.5.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: DAV Resource Assignee: kdepim-b...@kde.org Reporter: k...@sedrubal.de Target Milestone: --- Created attachment 107933 --> https://bugs.kde.org/attachment.cgi?id=107933=edit The certificate warning Akonadi should not try to sync with external servers (in my case the DAV resource) when the device is connected to a captive portal. If you configured to use a TLS secured connection, you'll receive many (!) certificate warnings if the captive portal web site is also available on a TLS connection and if your requests will be redirected to the captive portal website. Maybe you can use NetworkManager to determine if you are in an captive portal: $ nmcli networking connectivity check -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 353855] Media controls should be shown on lock screen.
https://bugs.kde.org/show_bug.cgi?id=353855 --- Comment #4 from sedrubal <k...@sedrubal.de> --- Yes, it was implemented with Plasma 5.10: https://www.kde.org/announcements/plasma-5.10.0.php So this one can be closed now. -- You are receiving this mail because: You are watching all bug changes.
