[kmymoney] [Bug 413764] Cell not correctly displaying content with Arabic numerals in text
https://bugs.kde.org/show_bug.cgi?id=413764 Hamidreza Jafari changed: What|Removed |Added Summary|Cell not displaying content |Cell not correctly |with Hindi numerals in text |displaying content with ||Arabic numerals in text -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411651] New tool to export photos to Canon Irista
https://bugs.kde.org/show_bug.cgi?id=411651 --- Comment #6 from Maik Qualmann --- Canon closes its cloud service on January 31, 2020. There's nothing for us here to do... Maik -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 413461] Latte-dock is badly positioned on Debian Wayland
https://bugs.kde.org/show_bug.cgi?id=413461 --- Comment #23 from Michail Vourlakos --- (In reply to prog-amateur from comment #22) > Any other Edge is offset (too much on the right, or down, etc.) I believe that this is just the wayland way of doing this. In wayland environment the windows can not position themselves without communicating with the wm running. Latte has achieved this for Plasma/KWin combo. In the past there were some articles that there will be a protocol that even sway would use in order to achieve this. For Gnome I don't even know if there is a way for external docks/panels to place themselves on their own. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413867] Allow battery monitor to be shown when fullly charged and plugged in
https://bugs.kde.org/show_bug.cgi?id=413867 g...@gabeappleton.me changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from g...@gabeappleton.me --- I was stupid and missed an option in the system tray. Sorry for the trouble. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413867] New: Allow battery monitor to be shown when fullly charged and plugged in
https://bugs.kde.org/show_bug.cgi?id=413867 Bug ID: 413867 Summary: Allow battery monitor to be shown when fullly charged and plugged in Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Battery Monitor Assignee: k...@privat.broulik.de Reporter: g...@gabeappleton.me CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY In some desktop managers (like Gnome) you can configure the battery monitor such that it is shown even when the device is both fully charged and plugged in. On plasmashell there is no obvious way to do so. It would be nice if this toggle could be added. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 30/kernel 5.3.7-200 (available in About System) KDE Plasma Version: 5.15.15 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 413866] New: Konqueror crashed when dragging window
https://bugs.kde.org/show_bug.cgi?id=413866 Bug ID: 413866 Summary: Konqueror crashed when dragging window Product: konqueror Version: 5.0.97 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: buo.ren@gmail.com Target Milestone: --- Application: konqueror (5.0.97) Qt Version: 5.9.5 Frameworks Version: 5.47.0 Operating System: Linux 5.3.0-18-generic x86_64 Distribution: Ubuntu 18.04.3 LTS -- Information about the crash: - What I was doing when the application crashed: I try to drag window from a screen to another, then the window disappeared and the crash prompt surfaced. -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3ad9e58840 (LWP 31020))] Thread 7 (Thread 0x7f3aa700 (LWP 31027)): #0 0x7f3acee009f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55db18913e98) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55db18913e48, cond=0x55db18913e70) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55db18913e70, mutex=0x55db18913e48) at pthread_cond_wait.c:655 #3 0x7f3abac1decb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f3abac1dab7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f3acedfa6db in start_thread (arg=0x7f3aa700) at pthread_create.c:463 #6 0x7f3ad96b288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f3ab88c8700 (LWP 31026)): #0 0x7f3acee009f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55db18913e98) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55db18913e48, cond=0x55db18913e70) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55db18913e70, mutex=0x55db18913e48) at pthread_cond_wait.c:655 #3 0x7f3abac1decb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f3abac1dab7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f3acedfa6db in start_thread (arg=0x7f3ab88c8700) at pthread_create.c:463 #6 0x7f3ad96b288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f3ab90c9700 (LWP 31025)): #0 0x7f3acee009f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55db18913e98) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55db18913e48, cond=0x55db18913e70) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55db18913e70, mutex=0x55db18913e48) at pthread_cond_wait.c:655 #3 0x7f3abac1decb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f3abac1dab7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f3acedfa6db in start_thread (arg=0x7f3ab90c9700) at pthread_create.c:463 #6 0x7f3ad96b288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f3ab98ca700 (LWP 31024)): #0 0x7f3acee009f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55db18913e98) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55db18913e48, cond=0x55db18913e70) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55db18913e70, mutex=0x55db18913e48) at pthread_cond_wait.c:655 #3 0x7f3abac1decb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f3abac1dab7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f3acedfa6db in start_thread (arg=0x7f3ab98ca700) at pthread_create.c:463 #6 0x7f3ad96b288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f3ac10f2700 (LWP 31023)): #0 0x7f3ad96a5bf9 in __GI___poll (fds=0x7f3ab4013bb0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f3accecf5c9 in g_main_context_poll (priority=, n_fds=1, fds=0x7f3ab4013bb0, timeout=, context=0x7f3ab4000bf0) at ../../../../glib/gmain.c:4203 #2 g_main_context_iterate (context=context@entry=0x7f3ab4000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../../glib/gmain.c:3897 #3 0x7f3accecf6dc in g_main_context_iteration (context=0x7f3ab4000bf0, may_block=may_block@entry=1) at ../../../../glib/gmain.c:3963 #4 0x7f3ad3f8f99b in QEventDispatcherGlib::processEvents (this=0x7f3ab4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f3ad3f349fa in QEventLoop::exec (this=this@entry=0x7f3ac10f1d30, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f3ad3d5323a in QThread::exec (this=this@entry=0x7f3ad5cccd60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
[Active Window Control] [Bug 413865] New: Dynamic widget width
https://bugs.kde.org/show_bug.cgi?id=413865 Bug ID: 413865 Summary: Dynamic widget width Product: Active Window Control Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: s4ng...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Could it be possible to make this widget adjust its width dynamically to take up space only needed to display current window icon and title string? Because now this widget only has an option to set fixed width and it would be nice if the widget could automatically adjust its width according to the current application icon and/or title. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413118] Scrollbar mouse down/click on background zone not registered.
https://bugs.kde.org/show_bug.cgi?id=413118 --- Comment #3 from Martín Lucas Golini --- Created attachment 123746 --> https://bugs.kde.org/attachment.cgi?id=123746=edit Correct patch to fix the scrollbar behavior. I just want to mention that the proposed patch is not correct, since the behavior is still broken for the slider click although is visually correct. I uploaded a patch that simply reverts the changes that actually caused this bug (linked in my first post): removed the scrollbar margin, and restored the transparent border to the scrollbar slider. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413864] New: Window > New View does not open new view
https://bugs.kde.org/show_bug.cgi?id=413864 Bug ID: 413864 Summary: Window > New View does not open new view Product: krita Version: 4.2.7.1 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: i...@ivywong.dev Target Milestone: --- SUMMARY I'd like to open a new view for a project. I have subwindows enabled, but when I click Window > New View > [project title], no new view opens. I've tried this with multiple files, e.g. a new unnamed document, a .kra file, and a .jpg file. I've also tried this with and without a Cintiq 13HD connected. I've reproduced this with Krita 4.2.2 as well as 4.2.7.1b. STEPS TO REPRODUCE 1. Open project file 2. Click on Window > New View > [project title] 3. Wait for new view to appear. OBSERVED RESULT Nothing happens. EXPECTED RESULT A new view opens showing the same document. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 16.04.6 LTS Linux (x86_64) release 4.15.0-66-generic (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: 5.12.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 413863] New: Graphs don't correct vertical scale after changing "Stack the beams on top of each other"
https://bugs.kde.org/show_bug.cgi?id=413863 Bug ID: 413863 Summary: Graphs don't correct vertical scale after changing "Stack the beams on top of each other" Product: ksysguard Version: 5.16.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: jman012...@gmail.com Target Milestone: --- SUMMARY Creating a custom plot and selecting "Stack the beams on top of each other" in the plot properties causes the vertical scale to be set too high while the ksysguard window is open. Closing and reopening the window resets the scale correctly. STEPS TO REPRODUCE 1. Create a custom plot, e.g. CPU temperatures 2. Select more than one sensor 3. Right click on the plot and select "Stack the beams on top of each other" in the plot properties 4. Click Apply 5. Deselect "Stack the beams on top of each other" and click apply OBSERVED RESULT Vertical axis scale adjusts to stack beams, but doesn't adjust when this operation is undone EXPECTED RESULT Vertical axis scale should adjust when this option is deselected SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 31 (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.12.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 412329] It says thar can not connect to internet
https://bugs.kde.org/show_bug.cgi?id=412329 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413525] I don't know what is going on, or if I am doin this correctly, but, something is wrong with the color wheel, everything is all neon, and the blending is all messed up. This is my
https://bugs.kde.org/show_bug.cgi?id=413525 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 412443] software update notification doesn't have away of clearing the entries
https://bugs.kde.org/show_bug.cgi?id=412443 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 412246] Cannot find file in kdeconnect
https://bugs.kde.org/show_bug.cgi?id=412246 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412458] Make the preview line from the assistant tool invisible when snapping to it is disabled
https://bugs.kde.org/show_bug.cgi?id=412458 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412548] Gui to whitelist/blacklist applications for global menu export (workaround for broken applications)
https://bugs.kde.org/show_bug.cgi?id=412548 --- Comment #7 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412656] Cintiq 24 inch can't use Pen after eraser side hits digital display.
https://bugs.kde.org/show_bug.cgi?id=412656 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 353481] Preset loses curve settings after resizing
https://bugs.kde.org/show_bug.cgi?id=353481 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 413620] The font in annotations (e.g. pop-up notes, highlights) can not be increased.
https://bugs.kde.org/show_bug.cgi?id=413620 Sodre changed: What|Removed |Added Status|NEEDSINFO |REOPENED Resolution|WAITINGFORINFO |--- --- Comment #6 from Sodre --- I re-open the thread as I provide the screenshot(https://postimg.cc/Lqth0dKJ). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 413449] Baloo file Extractor crash directly at KDE start
https://bugs.kde.org/show_bug.cgi?id=413449 Some1 changed: What|Removed |Added CC||newus...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 413449] Baloo file Extractor crash directly at KDE start
https://bugs.kde.org/show_bug.cgi?id=413449 --- Comment #2 from Some1 --- Created attachment 123745 --> https://bugs.kde.org/attachment.cgi?id=123745=edit New crash information added by DrKonqi baloo_file_extractor (5.63.0) using Qt 5.13.1 - What I was doing when the application crashed: Just started KDE neon and it crashed. It happend multiple times now. Not really sure why -- Backtrace (Reduced): #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #7 0x7f1bc0deb801 in __GI_abort () at abort.c:79 [...] #10 0x7f1bc00d3e8a in mdb_cursor_del () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 [...] #12 0x7f1bc3873af6 in Baloo::PositionDB::del (this=this@entry=0x7ffdee34e280, term=...) at ./src/engine/positiondb.cpp:119 #13 0x7f1bc3885816 in Baloo::WriteTransaction::commit (this=0x562e0c10bd10) at ./src/engine/writetransaction.cpp:335 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401634] Brush Disappears from Presets Filtered by a Tag After Override Brush
https://bugs.kde.org/show_bug.cgi?id=401634 vanyossi changed: What|Removed |Added CC||i...@ralek.art --- Comment #10 from vanyossi --- *** Bug 413860 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413860] Overwriting brush preset removes it from your assigned tags
https://bugs.kde.org/show_bug.cgi?id=413860 vanyossi changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||ghe...@gmail.com --- Comment #1 from vanyossi --- Resource issue, very smiliar (or same as) to 401634. Marking as duplicate *** This bug has been marked as a duplicate of bug 401634 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 413829] Discover does not start with Qt 5.12
https://bugs.kde.org/show_bug.cgi?id=413829 Aleix Pol changed: What|Removed |Added Product|Discover|frameworks-kirigami Target Milestone|--- |Not decided Version|5.17.2 |5.63.0 Component|discover|general Assignee|lei...@leinir.dk|notm...@gmail.com --- Comment #2 from Aleix Pol --- It would be great if you could confirm that the patch fixes the issue so we can close the bug. -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 413862] New: App task bar will not go into auto hide mode
https://bugs.kde.org/show_bug.cgi?id=413862 Bug ID: 413862 Summary: App task bar will not go into auto hide mode Product: kded-appmenu Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: top menubar Assignee: plasma-b...@kde.org Reporter: devguy...@gmail.com Target Milestone: --- Created attachment 123744 --> https://bugs.kde.org/attachment.cgi?id=123744=edit App bar top edge will not hide and covers windows SUMMARY This happens randomly, the App task(menu) bar will stop going into hide mode and remain stuck visible while covering over application windows. STEPS TO REPRODUCE 1. Set menu bar to auto hide. 2. Do stuff OBSERVED RESULT App bar becomes visible and will not auto hide for some reason. EXPECTED RESULT Should auto hide SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSuse Tumbleweed 20191101 KDE Plasma Version: 5.17.2 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 413861] attempting to install scripts does nothing
https://bugs.kde.org/show_bug.cgi?id=413861 --- Comment #1 from sirenji...@gmail.com --- Amarok version 2.9.70 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 413861] New: attempting to install scripts does nothing
https://bugs.kde.org/show_bug.cgi?id=413861 Bug ID: 413861 Summary: attempting to install scripts does nothing Product: amarok Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Script Manager Assignee: amarok-bugs-d...@kde.org Reporter: sirenji...@gmail.com CC: darthco...@gmail.com Target Milestone: kf5 SUMMARY STEPS TO REPRODUCE 1. open amarok settings > scripts 2. open manage scripts 3. install a script OBSERVED RESULT no scripts show up in the window, and do not appear to work EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro 18.10 (available in About System) KDE Plasma Version: 5.17.2 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413858] Settings crashes when opening "Startup and Shutdown"
https://bugs.kde.org/show_bug.cgi?id=413858 Finian Wright changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #2 from Finian Wright --- I'm not sure what caused it, but the sddm-kcm directory in .local/share/ was missing. I reinstalled kde-config-sddm and it fixed it. I'm guessing it just got removed accidentally at some point. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413859] Pre-cached frames don't save current frame.
https://bugs.kde.org/show_bug.cgi?id=413859 Aaron Lavarnway changed: What|Removed |Added Platform|Other |MS Windows OS|Linux |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413860] New: Overwriting brush preset removes it from your assigned tags
https://bugs.kde.org/show_bug.cgi?id=413860 Bug ID: 413860 Summary: Overwriting brush preset removes it from your assigned tags Product: krita Version: nightly build (please specify the git hash!) Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Tagging Assignee: krita-bugs-n...@kde.org Reporter: i...@ralek.art Target Milestone: --- Not sure if intentional. Any time I edit a brush and want to permanently save it, I click 'overwrite brush' and it removes it from all the tags I had put it under. So I then have to go find it in the long master list of brushes, and re-add it to my tags. Krita Version: 4.3.0-prealpha (git 2c21a4c) Qt Version (compiled): 5.12.5 Version (loaded): 5.12.5 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.17134 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413525] I don't know what is going on, or if I am doin this correctly, but, something is wrong with the color wheel, everything is all neon, and the blending is all messed up. This is my
https://bugs.kde.org/show_bug.cgi?id=413525 --- Comment #2 from AJ --- On Sun, Oct 27, 2019, 2:50 PM Boudewijn Rempt wrote: > https://bugs.kde.org/show_bug.cgi?id=413525 > > Boudewijn Rempt changed: > >What|Removed |Added > > > CC||b...@valdyas.org > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Boudewijn Rempt --- > Please attach a screenshot showing the problem; include the full Krita > window > including statusbar annd everything. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413859] New: Pre-cached frames don't save current frame.
https://bugs.kde.org/show_bug.cgi?id=413859 Bug ID: 413859 Summary: Pre-cached frames don't save current frame. Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: i...@ralek.art Target Milestone: --- Created attachment 123742 --> https://bugs.kde.org/attachment.cgi?id=123742=edit uncached frame SUMMARY If the current frame is frame 2, and Krita caches frames in the background, it fails to cache the current viewed frame. When drag scrubbing through frames afterwards, the failed frame does not show up unless explicitly clicked on. STEPS TO REPRODUCE -Make an animation with several frames each with their own keyframe -force a background re-cache by setting caching to on-disk or on-memory -observe which frames were cached and which weren't -scrubbing through the frames by dragging fails to show the uncached frame, or re-cache it Krita Version: 4.3.0-prealpha (git 2c21a4c) Qt Version (compiled): 5.12.5 Version (loaded): 5.12.5 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.17134 Pretty Productname: Windows 10 (10.0) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413858] Settings crashes when opening "Startup and Shutdown"
https://bugs.kde.org/show_bug.cgi?id=413858 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- Could you install debug symbols for /usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_sddm.so -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412637] Panel resets upon restarting Plasma
https://bugs.kde.org/show_bug.cgi?id=412637 --- Comment #5 from Christoph Feck --- Did comment #4 help to resolve this issue? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 413799] Screen settings panel: Presence of available inactive screens is hard to determine
https://bugs.kde.org/show_bug.cgi?id=413799 --- Comment #8 from ci3...@gmail.com --- (In reply to David Edmundson from comment #7) > >If you as the user haven't specifically disabled a screen, it shouldn't be > >disabled. When you plug in a screen, it should be enabled by default (if you > >didn't want it enabled, you wouldn't have plugged it in). > > We should restore the state we were last in when we had that set of monitors > plugged in. That's all within the KDED rather than the KCM and AFAIK that is > completely unchanged. Yes, this is the behaviour I experienced. Especially on my laptop, which I have connected to several beamers/TVs/screens, the last configuration for that specific device is restored. Afaik, also a quick setup is shown, when a new screen (never connected before) is plugged it. However, my concern is about a setup where a screen is not permanently active but activated only when needed (one of my screens for example is a TV that is off and deactivated most of the times). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413858] New: Settings crashes when opening "Startup and Shutdown"
https://bugs.kde.org/show_bug.cgi?id=413858 Bug ID: 413858 Summary: Settings crashes when opening "Startup and Shutdown" Product: systemsettings Version: 5.12.8 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: finianwri...@gmail.com Target Milestone: --- Application: systemsettings5 (5.12.8) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-65-generic x86_64 Distribution: Ubuntu 18.04.3 LTS -- Information about the crash: - What I was doing when the application crashed: Opening the "Startup and Shutdown" category in KDE System Settings. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9e10139c80 (LWP 2876))] Thread 9 (Thread 0x7f9dcf1d5700 (LWP 2888)): #0 0x7f9e0b99dbf9 in __GI___poll (fds=0x7f9dc40020a0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f9e058005c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9e058006dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9e0c2e699b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f9e0c28b9fa in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f9e0c0aa23a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f9e097dc6f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f9e0c0af17d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f9e0b46d6db in start_thread (arg=0x7f9dcf1d5700) at pthread_create.c:463 #9 0x7f9e0b9aa88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f9dcfbe4700 (LWP 2887)): #0 0x7f9e0b9990b4 in __GI___libc_read (fd=21, buf=0x7f9dcfbe3cd0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f9e058452d0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9e058000b7 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9e05800570 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f9e05800962 in g_main_loop_run () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f9dd0d820e6 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x7f9e05828195 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f9e0b46d6db in start_thread (arg=0x7f9dcfbe4700) at pthread_create.c:463 #8 0x7f9e0b9aa88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f9dd03e5700 (LWP 2886)): #0 0x7f9e0b99dbf9 in __GI___poll (fds=0x5616c9bf93f0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f9e058005c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9e058006dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9e05800721 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f9e05828195 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f9e0b46d6db in start_thread (arg=0x7f9dd03e5700) at pthread_create.c:463 #6 0x7f9e0b9aa88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f9ddcad3700 (LWP 2884)): #0 0x7f9e0c0a69ae in QMutex::lock() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f9e0c2e68bd in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f9e057ffb28 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9e058004fb in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f9e058006dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f9e0c2e699b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f9e0c28b9fa in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f9e0c0aa23a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f9e097dc6f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7f9e0c0af17d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f9e0b46d6db in start_thread (arg=0x7f9ddcad3700) at pthread_create.c:463 #11 0x7f9e0b9aa88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f9de4b01700 (LWP 2883)): #0 0x7f9e0b99dbf9 in __GI___poll (fds=0x7f9dd8004a00, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f9e058005c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9e058006dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3
[plasma-pk-updates] [Bug 413856] option missing: check 'x' minutes after start-up
https://bugs.kde.org/show_bug.cgi?id=413856 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #3 from Nate Graham --- Sweet, glad that works for you! -- You are receiving this mail because: You are watching all bug changes.
[plasma-pk-updates] [Bug 413856] option missing: check 'x' minutes after start-up
https://bugs.kde.org/show_bug.cgi?id=413856 --- Comment #2 from James Th --- Ooh! I had no idea that I could even do that! :) thank you! On Tue, Nov 5, 2019 at 9:44 PM +, "Nate Graham" wrote: https://bugs.kde.org/show_bug.cgi?id=413856 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Nate Graham --- > manually via the CLI (which is my preferred way of doing updates) Why not just uninstall plasma-pk updates, then? If you're not going to use it, just delete it. :) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 413810] QUESTION: scrollbar margin
https://bugs.kde.org/show_bug.cgi?id=413810 --- Comment #3 from Nate Graham --- Can you check the following: System Settings > Application Style > Window Decorations > Breeze > click the inline edit button that looks like a pencil > Allow resizing maximized windows from window edges If that's checked, uncheck it and see if that helps. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 413810] QUESTION: scrollbar margin
https://bugs.kde.org/show_bug.cgi?id=413810 --- Comment #2 from pierrescal...@gmail.com --- Thanks for your fast answer. I am using the kde-arc theme. When I try the Breeze theme, it is worse, click drag gets okular to enter window drag mode. By configuring the breeze application style drag mode from "Drag windows from all empty area" to "Drag windows from title bar only" the same behavior happens as in the kde-arc theme. I also tested with different Windows border size. Nothing, I cannot select the scrollbar. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408847] Plasma crashes when I click the button to open the apps launcher a few times in sequence
https://bugs.kde.org/show_bug.cgi?id=408847 --- Comment #20 from David Edmundson --- Fix is not in 5.13.1 git tag --contains 5d43a686fc3d5f13087a61e8ef216ecbbae0d15e v5.12.5 v5.13.2 v5.14.0-alpha1 v5.14.0-beta1 v5.14.0-beta2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 413826] Can't pick default application from list after typing text in search box
https://bugs.kde.org/show_bug.cgi?id=413826 Nate Graham changed: What|Removed |Added Component|general |general Product|frameworks-kwidgetsaddons |frameworks-kio Assignee|cf...@kde.org |fa...@kde.org --- Comment #2 from Nate Graham --- My bad, I forgot that KOpenWithDialog lives in KIO. Moving it there. As far as I can tell, there are two problems here: 1. Clicking on the OK button returns the text in the KHistoryCombobox, not the currently-selected item in the list below it. 2. Using a KHistoryCombobox in the first place is inappropriate, since it's being abused as a search/filter field to narrow the list of apps below it, but the field's own history/autocomplete features interfere with this. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 413826] Can't pick default application from list after typing text in search box
https://bugs.kde.org/show_bug.cgi?id=413826 --- Comment #1 from Christoph Feck --- How came investigation to the conclusion that the bug is in KWidgetsAddons? Does KOpenWithDialog use a widget from KWidgetsAddon that shows the issue? >From quickly checking, it uses KHistoryComboBox from KCompletion framework, but I didn't investigate if the bug is there or in KOpenWithDialog. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 413106] problem confiuring 3 monitors kde neon 5.16 worked fine 5.17 not work
https://bugs.kde.org/show_bug.cgi?id=413106 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #4 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 413627 *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 413627] screen positions of dual monitor setup does not get applied with one screen rotated
https://bugs.kde.org/show_bug.cgi?id=413627 Christoph Feck changed: What|Removed |Added CC||shipt...@zipmail.com.br --- Comment #11 from Christoph Feck --- *** Bug 413106 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408847] Plasma crashes when I click the button to open the apps launcher a few times in sequence
https://bugs.kde.org/show_bug.cgi?id=408847 --- Comment #19 from Christoph Feck --- We still get many duplicates, even with Qt 5.13.1. https://bugs.kde.org/buglist.cgi?bug_severity=crash=QtWaylandClient%3A%3AQWaylandWindow%3A%3AhandleUpdate%205.13.1_type=allwordssubstr_format=advanced=180d_id=1678744 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 413819] highlight annotation not carried over to pdfjs
https://bugs.kde.org/show_bug.cgi?id=413819 Tobias Deiminger changed: What|Removed |Added CC||haxti...@posteo.de --- Comment #1 from Tobias Deiminger --- >From your description I'm quite sure this is the same as already explained in bug 410642 comment 9. You may want to attach document snapshots here from before and after the "magic" repair operation by Foxit. I'd assume Foxit added an AP entry, which is kind of pregenerated graphics representing the note, unburdening PDF.js from generating it at their side. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 413820] Page jumps by a about a line when search bar is opened or closed
https://bugs.kde.org/show_bug.cgi?id=413820 Nate Graham changed: What|Removed |Added CC||n...@kde.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 413819] highlight annotation not carried over to pdfjs
https://bugs.kde.org/show_bug.cgi?id=413819 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 413826] Can't pick default application from list after typing text in search box
https://bugs.kde.org/show_bug.cgi?id=413826 Nate Graham changed: What|Removed |Added CC||kdelibs-b...@kde.org, ||n...@kde.org Assignee|unassigned-b...@kde.org |cf...@kde.org Product|systemsettings |frameworks-kwidgetsaddons Summary|Can't pick default |Can't pick default |application from list |application from list after ||typing text in search box Version|5.17.1 |5.63.0 Component|kcm_componentchooser|general Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413857] New: Separate Image > Output to color produces incorrect channels with higher bit depth documents
https://bugs.kde.org/show_bug.cgi?id=413857 Bug ID: 413857 Summary: Separate Image > Output to color produces incorrect channels with higher bit depth documents Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: manuel.snudl.zeid...@gmail.com Target Milestone: --- SUMMARY Using Image > Separate Image... with the enabled option "Output to color, not grayscale" confuses the separated channels if the image uses anything else than 8-bit per channel. All color models I tested (RGB, LAB, CMYK) produced the issue. STEPS TO REPRODUCE 1. Open an image that uses 16 or 32-bit per channel 2. Use Image > Separate Image... and enable the Output to color checkbox 3. Hide the original layer(s), inspect the separated layers OBSERVED RESULT Channel layers can be swapped or empty, so the full color image cannot be assembled correctly. EXPECTED RESULT Correctly split channels, same as with 8-bit depth. SOFTWARE/OS VERSIONS Tested in master (git 179649c) and 4.2.7.1 from distro repos, both showing the same issue. ADDITIONAL INFORMATION Small usability gripe - Using the new "Activate the current channel" option that's present in master will give all channel layers the Inherit Alpha property, so they can't be seen unless there is a solid layer behind them. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 413820] Page jumps by a about a line when search bar is opened or closed
https://bugs.kde.org/show_bug.cgi?id=413820 Nate Graham changed: What|Removed |Added Severity|normal |minor -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413843] "In an application based on the contents of the URL" setting causes HTTP links in to produce a KIO error pop-up saying "file or folder http://X does not exist" when click
https://bugs.kde.org/show_bug.cgi?id=413843 Nate Graham changed: What|Removed |Added CC||n...@kde.org Summary|Clicking on HTTP links in |"In an application based on |applications causes KIO |the contents of the URL" |error pop-up - "file or |setting causes HTTP links |folder http://X does not|in to produce a KIO error |exist" |pop-up saying "file or ||folder http://X does not ||exist" when clicked Component|general |kcm_componentchooser Product|kde |systemsettings -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413849] Area screenshot on Wayland not intuitive
https://bugs.kde.org/show_bug.cgi?id=413849 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasma-pk-updates] [Bug 413856] option missing: check 'x' minutes after start-up
https://bugs.kde.org/show_bug.cgi?id=413856 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Nate Graham --- > manually via the CLI (which is my preferred way of doing updates) Why not just uninstall plasma-pk updates, then? If you're not going to use it, just delete it. :) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 413461] Latte-dock is badly positioned on Debian Wayland
https://bugs.kde.org/show_bug.cgi?id=413461 --- Comment #22 from prog-amat...@tutamail.com --- Any other Edge is offset (too much on the right, or down, etc.) -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 395376] Multi-line result support
https://bugs.kde.org/show_bug.cgi?id=395376 Mark Smith changed: What|Removed |Added CC||anon...@openmailbox.org -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 412910] special character shown in warning dialog
https://bugs.kde.org/show_bug.cgi?id=412910 --- Comment #1 from Christoph Feck --- Interesting. The dialog is a simple QMessageBox, but when I write a testcase, I never see the '\n' text; only a new line is started. I also use Qt 5.13.1. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pk-updates] [Bug 413856] New: option missing: check 'x' minutes after start-up
https://bugs.kde.org/show_bug.cgi?id=413856 Bug ID: 413856 Summary: option missing: check 'x' minutes after start-up Product: plasma-pk-updates Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: ja...@thornber.io Target Milestone: --- SUMMARY currently as soon as I boot up my linux box within seconds of the network connection becoming available, then the system software update runs. I'd like the option to be able to delay this action by 'x' minutes, this would give me the time to run it manually via the CLI (which is my preferred way of doing updates). Would something like this be possible, please? OBSERVED RESULT System software update runs automatically a few seconds after startup/network connection becoming available. EXPECTED RESULT I should be able to delay the default action by 'x' minutes after startup if possible, please. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.17.2 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 411647] regression: adding a new imap account prompts no error but no directory tree is created
https://bugs.kde.org/show_bug.cgi?id=411647 --- Comment #4 from avlas --- (In reply to keitalbame from comment #3) > You are right. > When I read "directory tree is not created", remembered about the bug I > mentioned because when I first saw the issue, the folders where not being > created in the filesystem. I found out later that they where created on a > different (incorrect) path. I see. It might still be the same underlying issue, but it's not obvious. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 411647] regression: adding a new imap account prompts no error but no directory tree is created
https://bugs.kde.org/show_bug.cgi?id=411647 --- Comment #3 from keitalbame --- You are right. When I read "directory tree is not created", remembered about the bug I mentioned because when I first saw the issue, the folders where not being created in the filesystem. I found out later that they where created on a different (incorrect) path. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 413799] Screen settings panel: Presence of available inactive screens is hard to determine
https://bugs.kde.org/show_bug.cgi?id=413799 --- Comment #7 from David Edmundson --- >If you as the user haven't specifically disabled a screen, it shouldn't be >disabled. When you plug in a screen, it should be enabled by default (if you >didn't want it enabled, you wouldn't have plugged it in). We should restore the state we were last in when we had that set of monitors plugged in. That's all within the KDED rather than the KCM and AFAIK that is completely unchanged. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 263042] XFA Forms are not supported
https://bugs.kde.org/show_bug.cgi?id=263042 --- Comment #9 from Albert Astals Cid --- Just a reality check, XFA forms are 99.98% never going to be supported unless you come by a few hundred thousands euros. XFA is also deprecated in PDF 2.0 so whoever is giving you those kind of files, you should tell them to stop producing them. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 tosziro changed: What|Removed |Added Component|android-application |messaging-application Platform|Other |Manjaro CC||piotr.kusnierz@protonmail.c ||om --- Comment #26 from tosziro --- Sms,contacts and history sms not visible in sms window. Anyway messages can be send. Huawei Mate 20 Pro and Manjaro Linux. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 411647] regression: adding a new imap account prompts no error but no directory tree is created
https://bugs.kde.org/show_bug.cgi?id=411647 --- Comment #2 from avlas --- It doesn't seem related, as this one doesn't have anything to do with local mail, but not sure. At some point I found an alternative way to add an email account in Kmail that did work. This was some months ago, so I don't totally recall. But for the case other users suffer this, they could explore alternative ways to create the account, as it seems based on my experience that one is troublesome and the other is not. -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 413151] cmake crashes when trying to compile a KDE package
https://bugs.kde.org/show_bug.cgi?id=413151 Christoph Feck changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Christoph Feck --- If cmake crashes, please report this issue directly to cmake developers via https://gitlab.kitware.com/cmake/cmake/issues -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 411647] regression: adding a new imap account prompts no error but no directory tree is created
https://bugs.kde.org/show_bug.cgi?id=411647 keitalbame changed: What|Removed |Added CC||keitalb...@posteo.net --- Comment #1 from keitalbame --- Related with bug 408354. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412883] kwin crashing when waking up from supend
https://bugs.kde.org/show_bug.cgi?id=412883 Christoph Feck changed: What|Removed |Added Resolution|BACKTRACE |--- Status|NEEDSINFO |REPORTED --- Comment #8 from Christoph Feck --- New backtrace was added with comment #7; changing status for inspection. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 413799] Screen settings panel: Presence of available inactive screens is hard to determine
https://bugs.kde.org/show_bug.cgi?id=413799 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #6 from Nate Graham --- Perhaps we could show disabled screens in the visualization with low opacity and the text "Disabled" appended to its label. But I think the greater problem is that screens show up as disabled far too often in the new KCM. If you as the user haven't specifically disabled a screen, it shouldn't be disabled. When you plug in a screen, it should be enabled by default (if you didn't want it enabled, you wouldn't have plugged it in). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413011] Reactivating a display then opening taskbar configuration
https://bugs.kde.org/show_bug.cgi?id=413011 Christoph Feck changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #2 from Christoph Feck --- Crash is in libGLX_nvidia.so.0 which is NVIDIA's OpenGL driver bridge for X11. If this is reproducible, please report this issue directly to NVIDIA developers via https://devtalk.nvidia.com/default/topic/522835/linux/if-you-have-a-problem-please-read-this-first/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364410] large padding in vertical panel
https://bugs.kde.org/show_bug.cgi?id=364410 Nate Graham changed: What|Removed |Added Resolution|DUPLICATE |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #5 from Nate Graham --- Oops, my mistake. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 413689] Move the page number info to the toolbar and hide the status bar by default
https://bugs.kde.org/show_bug.cgi?id=413689 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #8 from Nate Graham --- (In reply to David Hurka from comment #7) > In the latter option, we also should remove the toolbar buttons, because the > toolbar widget of the page bar already has these buttons. Yes, I've submitted an MR that does just this: https://invent.kde.org/kde/okular/merge_requests/61 > Concerning the page size: Would it make sense to put page-related > information directly into the grey background of PageView? The page number > itself could also be shown there, so it is obvious which page is which. Hmm, that might be a bit weird. In general I don't like when pop-ups or messages permanently cover content. > I would also like annotation comment windows sticked to the grey background, > instead of floating on the view. Currently you have to close all comment > windows manually when you scroll to another page. Unrelated to this issue. :) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 299816] Support XFA form
https://bugs.kde.org/show_bug.cgi?id=299816 Nate Graham changed: What|Removed |Added Resolution|UPSTREAM|DUPLICATE CC||n...@kde.org --- Comment #3 from Nate Graham --- *** This bug has been marked as a duplicate of bug 263042 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 413852] Supporting XFA forms
https://bugs.kde.org/show_bug.cgi?id=413852 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||n...@kde.org --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 263042 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 263042] XFA Forms are not supported
https://bugs.kde.org/show_bug.cgi?id=263042 Nate Graham changed: What|Removed |Added CC||newbee...@nativobject.net --- Comment #7 from Nate Graham --- *** Bug 299816 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413855] Digikam crashes when deleting a letter in the login window
https://bugs.kde.org/show_bug.cgi?id=413855 --- Comment #2 from Maik Qualmann --- Yes, it crashes in the depths of Webkit (WebCore). Maik -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 263042] XFA Forms are not supported
https://bugs.kde.org/show_bug.cgi?id=263042 --- Comment #8 from Nate Graham --- *** Bug 413852 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 263042] XFA Forms are not supported
https://bugs.kde.org/show_bug.cgi?id=263042 Nate Graham changed: What|Removed |Added URL||https://gitlab.freedesktop. ||org/poppler/poppler/issues/ ||530 Status|REOPENED|CONFIRMED --- Comment #6 from Nate Graham --- Bug trackers track actionable work. If 100% of the required work is in Poppler such that Okular will gain the feature for free, then there is no work required in Okular and hence this bug report does not track anything and should be closed. If on the other hand Okular will need some work to adopt the feature once it's implemented in Poppler, then it's appropriate to keep this bug open to track that work. I suppose technically once XFA support is added to Poppler, at the minimum we'll need to remove the banner that warns you that XFA forms are unsupported, so we can keep this open to track that. But to reiterate, the bulk of the work needs to be done in Poppler, not in Okular. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 413433] QtQuick dialog: header is empty
https://bugs.kde.org/show_bug.cgi?id=413433 Dan Leinir Turthra Jensen changed: What|Removed |Added Latest Commit||https://commits.kde.org/kne ||wstuff/4d56727cc7d76c18742f ||97782ebf3ab6d44391be Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Dan Leinir Turthra Jensen --- Git commit 4d56727cc7d76c18742f97782ebf3ab6d44391be by Dan Leinir Turthra Jensen. Committed on 05/11/2019 at 20:43. Pushed by leinir into branch 'master'. Fix the header layouts for EntryDetails and Page components Summary: This ensures that the header is the correct width, and further that the text does not disappear when there is no space for the text (so that it elides as intended). Related: bug 413440 Test Plan: Without patch: Resize a dialog to make the text not fit, and it disappears With patch: Resize dialog, text is elided as one would expect, and the header row takes up the correct amount of space Reviewers: ngraham, #knewstuff, #frameworks, #plasma Reviewed By: ngraham Subscribers: ahiemstra, kde-frameworks-devel Tags: #frameworks Differential Revision: https://phabricator.kde.org/D25067 M +30 -46 src/qtquick/qml/EntryDetails.qml M +1-7src/qtquick/qml/Page.qml https://commits.kde.org/knewstuff/4d56727cc7d76c18742f97782ebf3ab6d44391be -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 413440] QtQuick dialog: header label on item detail page probably needs Layout.fillWidth: true set on it
https://bugs.kde.org/show_bug.cgi?id=413440 Dan Leinir Turthra Jensen changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/kne ||wstuff/4d56727cc7d76c18742f ||97782ebf3ab6d44391be Resolution|--- |FIXED --- Comment #1 from Dan Leinir Turthra Jensen --- Git commit 4d56727cc7d76c18742f97782ebf3ab6d44391be by Dan Leinir Turthra Jensen. Committed on 05/11/2019 at 20:43. Pushed by leinir into branch 'master'. Fix the header layouts for EntryDetails and Page components Summary: This ensures that the header is the correct width, and further that the text does not disappear when there is no space for the text (so that it elides as intended). Related: bug 413433 Test Plan: Without patch: Resize a dialog to make the text not fit, and it disappears With patch: Resize dialog, text is elided as one would expect, and the header row takes up the correct amount of space Reviewers: ngraham, #knewstuff, #frameworks, #plasma Reviewed By: ngraham Subscribers: ahiemstra, kde-frameworks-devel Tags: #frameworks Differential Revision: https://phabricator.kde.org/D25067 M +30 -46 src/qtquick/qml/EntryDetails.qml M +1-7src/qtquick/qml/Page.qml https://commits.kde.org/knewstuff/4d56727cc7d76c18742f97782ebf3ab6d44391be -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413855] Digikam crashes when deleting a letter in the login window
https://bugs.kde.org/show_bug.cgi?id=413855 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Can you create a better backtrace? Compiled here with QWebEngine I can not reproduce an error. The AppImage uses the older WebKit. Even though WebKit is currently being actively developed, I still think that it does not get along well with modern websites. Maik -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 413854] Dolphin crashes repeatedly right after login to SMB server
https://bugs.kde.org/show_bug.cgi?id=413854 Andreas Sittinger changed: What|Removed |Added CC||a...@andreassittinger.de -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384110] Shift-drag brush size change doesn't work in the smart patch tool
https://bugs.kde.org/show_bug.cgi?id=384110 kjellem changed: What|Removed |Added CC||sendtonulldev...@gmail.com --- Comment #5 from kjellem --- Same as this? https://bugs.kde.org/show_bug.cgi?id=383640#c6 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 413854] Dolphin crashes repeatedly right after login to SMB server
https://bugs.kde.org/show_bug.cgi?id=413854 --- Comment #2 from Andreas Sittinger --- Created attachment 123740 --> https://bugs.kde.org/attachment.cgi?id=123740=edit New crash information added by DrKonqi dolphin (18.12.3) using Qt 5.9.7 - What I was doing when the application crashed: starting fresh after login entered address line as smb://ds411 filled pop-up for user name and password Dolphin crashes the core dump will not happen if SMB connection has been stablished successfully before by running smbclient new backtrace with some more kio-*-debuginfo added -- Backtrace (Reduced): #8 0x7f64975c164f in QtPrivate::QSlotObjectBase::call (a=0x7ffc65834590, r=0x7f649be7b360, this=0x55b6a0b56940) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:101 [...] #11 0x7f6498f75d8c in KJob::result (this=this@entry=0x55b6a0a16490, _t1=, _t1@entry=0x55b6a0a16490, _t2=...) at /usr/src/debug/kcoreaddons-5.55.0-lp151.1.2.x86_64/build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:569 #12 0x7f6498f768c1 in KJob::finishJob (this=0x55b6a0a16490, emitResult=) at /usr/src/debug/kcoreaddons-5.55.0-lp151.1.2.x86_64/src/lib/jobs/kjob.cpp:109 #13 0x7f649bbc3658 in KIO::SimpleJob::slotFinished() () from /usr/lib64/libKF5KIOCore.so.5 #14 0x7f649bbb7fab in KIO::ListJob::slotFinished() () from /usr/lib64/libKF5KIOCore.so.5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 383640] Unable to change the size of the Smart Patch Tool
https://bugs.kde.org/show_bug.cgi?id=383640 --- Comment #6 from kjellem --- (Still, It seems) occurs for me on 4.2.7.1 on Win10 x64... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 383640] Unable to change the size of the Smart Patch Tool
https://bugs.kde.org/show_bug.cgi?id=383640 kjellem changed: What|Removed |Added CC||sendtonulldev...@gmail.com --- Comment #5 from kjellem --- Occurs for me on 4.2.7.1 on Win10 x64... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413855] New: Digikam crashes when deleting a letter in the login window
https://bugs.kde.org/show_bug.cgi?id=413855 Bug ID: 413855 Summary: Digikam crashes when deleting a letter in the login window Product: digikam Version: 6.4.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plugin-WebService-OneDrive Assignee: digikam-bugs-n...@kde.org Reporter: nic...@tuxfamily.org Target Milestone: --- STEPS TO REPRODUCE 1. Call Export To Onedrive plugin 2. A window opens where you can enter you login (Microsoft account, usually hotmail or outlook e-mail) 3. Enter your login and delete a letter of it (using 'delete' or 'backspace' key) OBSERVED RESULT Digikam crashes In terminal: /tmp/.mount_digika8YzzZy/AppRun: line 151: 6890 Segmentation fault (core dumped) digikam $@ SOFTWARE/OS VERSIONS Digikam 6.4 (Appimage) on Fedora 30 ADDITIONAL INFORMATION Reproduceable also on Digikam 6.3 (Appimage) but not with 6.1 (Appimage and rpm) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 413799] Screen settings panel: Presence of available inactive screens is hard to determine
https://bugs.kde.org/show_bug.cgi?id=413799 David Edmundson changed: What|Removed |Added Flags||Usability+ Resolution|WAITINGFORINFO |--- Summary|Screen settings panel: |Screen settings panel: |Please bring the gray |Presence of available |monitor back|inactive screens is hard to ||determine Status|NEEDSINFO |REPORTED --- Comment #5 from David Edmundson --- It's interesting that you had 3 screens. The case of going between 1 and 2 screens is more obvious because a whole combo box and page indicator appear, but 2 -> 3 wouldn't have that. Reopening for UX discussion on what we do next. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 413853] kpmcore testmsart hangs
https://bugs.kde.org/show_bug.cgi?id=413853 --- Comment #1 from Andrius Štikonas --- Test smart is known to be broken. It tries to call df command which helper is not allowed to run. Possibly it makes sense to remove this test... -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 413854] Dolphin crashes repeatedly right after login to SMB server
https://bugs.kde.org/show_bug.cgi?id=413854 Elvis Angelaccio changed: What|Removed |Added Assignee|dolphin-bugs-n...@kde.org |plasma-b...@kde.org CC||elvis.angelac...@kde.org Status|REPORTED|NEEDSINFO Component|general |Samba Product|dolphin |kio-extras Resolution|--- |BACKTRACE --- Comment #1 from Elvis Angelaccio --- Please install debug symbols for KIO and then post another backtrace. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 413689] Move the page number info to the toolbar and hide the status bar by default
https://bugs.kde.org/show_bug.cgi?id=413689 --- Comment #7 from David Hurka --- (In reply to Nate Graham from comment #6) > Yeah right now there's redundancy in that there are two sets of > next/previous buttons. I guess the question is whether this should be fixed > by removing the toolbar buttons and keeping the status bar, or putting the > navigation controls from the status bar into the toolbar and hiding the > status bar. > > The latter option makes more sense to me IMO. In the latter option, we also should remove the toolbar buttons, because the toolbar widget of the page bar already has these buttons. Concerning the page size: Would it make sense to put page-related information directly into the grey background of PageView? The page number itself could also be shown there, so it is obvious which page is which. I would also like annotation comment windows sticked to the grey background, instead of floating on the view. Currently you have to close all comment windows manually when you scroll to another page. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375501] Selection color should become lighter if folder view loses focus
https://bugs.kde.org/show_bug.cgi?id=375501
Nate Graham changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED |RESOLVED
Version Fixed In||5.18.0
Latest Commit||https://commits.kde.org/pla
||sma-desktop/596f979d45c5f1b
||61042d8278efdaef364c6bdc6
--- Comment #3 from Nate Graham ---
Git commit 596f979d45c5f1b61042d8278efdaef364c6bdc6 by Nate Graham.
Committed on 05/11/2019 at 20:14.
Pushed by ngraham into branch 'master'.
[Folder View] Use an inactive highlight effect when something else has focus
Summary:
The theme SVG doesn't have a concept of "inactive selection highlight", so we
need to
manufacture our own by reducing the opacity of the selection highlight.
Thanks to @broulik for suggesting the necessary code changes in the bug report.
FIXED-IN: 5.18.0
Test Plan: {F7743147}
Reviewers: #plasma, #vdg, davidedmundson
Reviewed By: #plasma, davidedmundson
Subscribers: broulik, plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D25160
M +4-0containments/desktop/package/contents/ui/FolderItemDelegate.qml
https://commits.kde.org/plasma-desktop/596f979d45c5f1b61042d8278efdaef364c6bdc6
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 413854] New: Dolphin crashes repeatedly right after login to SMB server
https://bugs.kde.org/show_bug.cgi?id=413854 Bug ID: 413854 Summary: Dolphin crashes repeatedly right after login to SMB server Product: dolphin Version: 18.12.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: a...@andreassittinger.de CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (18.12.3) Qt Version: 5.9.7 Frameworks Version: 5.55.0 Operating System: Linux 4.12.14-lp151.28.20-default x86_64 Distribution: "openSUSE Leap 15.1" -- Information about the crash: - What I was doing when the application crashed: entered address line as smb://ds411 filled pop-up for user name and password Dolphin crashes this particular problem seems to be around for 12 months or more, I have seen it in my configuration for a long time; it was also found in OpenSuse Leap 42.3, and very likely any older versions I used; same for Ubuntu 18.04.3 LTS (all plain vanilla out of the box) the server access in general works fine, like using smbclient; please note this server has 10 shares and a total capacity of 6TB The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2b5c452900 (LWP 30621))] Thread 6 (Thread 0x7f2b23fff700 (LWP 30626)): #0 0x7f2b5bce119b in poll () from /lib64/libc.so.6 #1 0x7f2b4e6d51a9 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f2b4e6d52bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f2b55e7196b in QEventDispatcherGlib::processEvents (this=0x7f2b1c000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f2b55e1690a in QEventLoop::exec (this=this@entry=0x7f2b23ffecb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f2b55c34daa in QThread::exec (this=) at thread/qthread.cpp:515 #6 0x7f2b55c39ced in QThreadPrivate::start (arg=0x562cfc3c92f0) at thread/qthread_unix.cpp:368 #7 0x7f2b50b16569 in start_thread () from /lib64/libpthread.so.0 #8 0x7f2b5bceb9ef in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f2b3180a700 (LWP 30625)): #0 0x7f2b50b1c8ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f2b36d7f88b in ?? () from /usr/lib64/dri/r600_dri.so #2 0x7f2b36d7f597 in ?? () from /usr/lib64/dri/r600_dri.so #3 0x7f2b50b16569 in start_thread () from /lib64/libpthread.so.0 #4 0x7f2b5bceb9ef in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f2b3200b700 (LWP 30624)): #0 0x7f2b50b1c8ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f2b36d7f88b in ?? () from /usr/lib64/dri/r600_dri.so #2 0x7f2b36d7f597 in ?? () from /usr/lib64/dri/r600_dri.so #3 0x7f2b50b16569 in start_thread () from /lib64/libpthread.so.0 #4 0x7f2b5bceb9ef in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f2b3e093700 (LWP 30623)): #0 0x7f2b5bce119b in poll () from /lib64/libc.so.6 #1 0x7f2b4e6d51a9 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f2b4e6d52bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f2b55e7196b in QEventDispatcherGlib::processEvents (this=0x7f2b38000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f2b55e1690a in QEventLoop::exec (this=this@entry=0x7f2b3e092c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f2b55c34daa in QThread::exec (this=) at thread/qthread.cpp:515 #6 0x7f2b562f19e5 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7f2b55c39ced in QThreadPrivate::start (arg=0x7f2b56564d60) at thread/qthread_unix.cpp:368 #8 0x7f2b50b16569 in start_thread () from /lib64/libpthread.so.0 #9 0x7f2b5bceb9ef in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f2b448f0700 (LWP 30622)): #0 0x7f2b5bce119b in poll () from /lib64/libc.so.6 #1 0x7f2b4d40a307 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f2b4d40bf3a in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f2b476a8939 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f2b55c39ced in QThreadPrivate::start (arg=0x562cfbd2f7e0) at thread/qthread_unix.cpp:368 #5 0x7f2b50b16569 in start_thread () from /lib64/libpthread.so.0 #6 0x7f2b5bceb9ef in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f2b5c452900 (LWP 30621)): [KCrash Handler] #6 0x7f2b5a49e8f0 in ?? () from /usr/lib64/libKF5KIOCore.so.5 #7 0x7f2b5a497e42 in ?? () from /usr/lib64/libKF5KIOCore.so.5 #8 0x7f2b55e4764f in QtPrivate::QSlotObjectBase::call (a=0x7ffe8ed3ef30, r=0x7f2b5a701360, this=0x562cfc2fd200) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:101 #9 QMetaObject::activate
[partitionmanager] [Bug 413853] New: kpmcore testmsart hangs
https://bugs.kde.org/show_bug.cgi?id=413853 Bug ID: 413853 Summary: kpmcore testmsart hangs Product: partitionmanager Version: 4.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: h.goe...@crazy-compilers.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Build kpmcore 2. Apply https://phabricator.kde.org/D25161 to make test run 3. Run testsmart OBSERVED RESULT Test hangs: $ ../build/bin/testsmart Loaded backend plugin: "pmsfdiskbackendplugin" "Connection \":1.219\" is not allowed to own the service \"org.kde.kpmcore.applicationinterface\" due to security policies in the configuration file" QDBusArgument: read from a write-only object QDBusArgument: read from a write-only object QDBusArgument: read from a write-only object kf5.kauth: Tried to start an invalid action ^C EXPECTED RESULT Test terminates. SOFTWARE/OS VERSIONS Linux KDE Frameworks Version: 5.63 Qt Version: 5.12 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 413827] KActionMenu sticky/delayed wrong behavior
https://bugs.kde.org/show_bug.cgi?id=413827
--- Comment #1 from David Hurka ---
I also find this weird, thanks for opening the bug.
I think providing a setPopupMode(QToolButton::ToolButtonPopupMode) would be
just fine.
>From kactionmenu.cpp:
In private class definition:
>bool m_delayed = true;
>bool m_stickyMenu = true;
In createWidget():
>if (delayed()) {
>button->setPopupMode(QToolButton::DelayedPopup);
>} else if (stickyMenu()) {
>button->setPopupMode(QToolButton::InstantPopup);
>} else {
>button->setPopupMode(QToolButton::MenuButtonPopup);
>}
In toggleactionmenu.cpp (D21971) I go the reverse way:
> if ( popupMode == QToolButton::DelayedPopup )
> {
> setDelayed( true );
> }
> else if ( popupMode == QToolButton::InstantPopup )
> {
> setDelayed( false );
> setStickyMenu( true );
> }
> else
> {
> setDelayed( false );
> setStickyMenu( false );
> }
--
You are receiving this mail because:
You are watching all bug changes.
[skrooge] [Bug 413747] Many Entries & Previous Reconciliations Disappear
https://bugs.kde.org/show_bug.cgi?id=413747 Stephane MANKOWSKI changed: What|Removed |Added Assignee|guillaume.deb...@gmail.com |steph...@mankowski.fr --- Comment #1 from Stephane MANKOWSKI --- Hi, I never had this kind of issue. Are you sure you didn't do something to come back on a previous version? Example: - CTRL+Z to undo modifications - Replace the file by a old one (synchronization with on cloud can produce this) - Forget to save the file after modification - ... You can have a look on the history to see what happen in your document. Anyway, without detailed scenario to reproduce the issue, I can fix it. Regards. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 413799] Screen settings panel: Please bring the gray monitor back
https://bugs.kde.org/show_bug.cgi?id=413799 --- Comment #4 from ci3...@gmail.com --- Created attachment 123739 --> https://bugs.kde.org/attachment.cgi?id=123739=edit monitor.png (In reply to David Edmundson from comment #3) > What is the issue caused by not showing the disabled screens in the > arrangement area. Users are unable to see that other monitors are present (recognized by the system) or are not able to select it in a fast way. I marked the visual indicators for other monitors in the screenshot. Previewing the inactive display is a much bigger indicator that other screens are present. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 263042] XFA Forms are not supported
https://bugs.kde.org/show_bug.cgi?id=263042 Archisman Panigrahi changed: What|Removed |Added Resolution|UPSTREAM|--- Status|RESOLVED|REOPENED CC||apanda...@gmail.com --- Comment #5 from Archisman Panigrahi --- I believe this should not be marked as resolved until this feature is implemented in poppler, and Okular supports it. Lots of passport/government applications require one to fill up XFA forms. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 413840] Burger Menu in sidebar resizes unexpectedly
https://bugs.kde.org/show_bug.cgi?id=413840 Sam Dyer changed: What|Removed |Added CC||samdyer...@outlook.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Sam Dyer --- Could you please add you operating system version. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 413841] Text in toolbar jitters when sidebar collapses
https://bugs.kde.org/show_bug.cgi?id=413841 Sam Dyer changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||samdyer...@outlook.com --- Comment #1 from Sam Dyer --- Could you add your operating system version. -- You are receiving this mail because: You are watching all bug changes.
