[Falkon] [Bug 414302] Ecosia search engine doesn't work as default
https://bugs.kde.org/show_bug.cgi?id=414302 --- Comment #5 from Juraj --- 1. Preferences > Tabs > Address Bar Behaviour > Search with Default Engine [Check] If it is checked the default Search Engine is used. If it is NOT checked the selected Search Engine in search bar is used. 2. At first you wrote into the URL field only ecosia homepage without any parameter. (like that would work) Than you copied the right URL with required parameters but you still failed because of option mentioned in [1]. PS: Why to restart whole machine to change settings in web browser? This is not Internet Explorer. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 414541] cantor git master and maxima 5.43 crash
https://bugs.kde.org/show_bug.cgi?id=414541
--- Comment #5 from Alexander Semke ---
(In reply to nijso from comment #4)
> Hi, I have the most recent version of libspectre, 0.2.8. I re-compiled
> libspectre and cantor and it still crashes, also for the previous cantor
> version 19.08 (I thought that one worked, but unfortunately it doesn't work
> either. I tried cantor 18.04 but that one crashes when I load it).
I'm also on openSUSE and also observed this crash in the past. The crash
disappeared later and I never managed to look into this. Now it's crashing
permanently for me and I had a closer look into it.
The crash happens in glibc in the memcopy call (Cantor -> Spectre ->
GhostScript -> Little-CMS -> GNU C lib). Modern versions of glibc use the
AVX-optimized implementations where the propper AVX-instructions are
used/generated depending on the available CPU-features ("CPU-dispatching",
https://lwn.net/Articles/691932/). On my and on your computer the CPU has the
AVX extension and we go into the AVX-case where __memmove_avx_unaligned_erms is
used. But, this generates "somehow" an instruction which is not recognized by
the CPU(?) and the process crashes.
Recompiling glibc without AVX-optimization or patching the compiled library as
described in
https://stackoverflow.com/questions/42451492/disable-avx-optimized-functions-in-glibc-ld-hwcap-mask-etc-ld-so-nohwcap-for/44468494#44468494
will help here but is surely not an option for everybody.
I'm not sure how to deal with this now. This problem is clearly outside of
Cantor.
We introduced the support for Jupyter notebooks recently:
https://sirgienkogsoc2019.blogspot.com/2019/08/cantor-and-support-for-jupyter.html
Here, for the mathematical formulas embedded into the text we also use LaTeX to
generate the images. We use pdflatex to generate PDF and to render it to an
image via Poppler. For general latex entries in the worksheet we use latex as
the renderer and the path is tex->EPS->libspectre->image - this is where the
crash happens. Since we now require pdflatex anyway for the support of Jupyter
notebooks, we should maybe completely switch to pdflatex also for normal latex
entries in the worksheet. This will simplify the code a bit and also avoid this
crash in the AVX-optimized glibc on openSUSE and maybe on some other
distributions.
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 362946] keyboard kcm build too fat
https://bugs.kde.org/show_bug.cgi?id=362946 Harald Sitter changed: What|Removed |Added Latest Commit||https://commits.kde.org/pla ||sma-desktop/c7a1f606ca9669d ||3732786a4701bec8457cc8eeb Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from Harald Sitter --- Git commit c7a1f606ca9669d3732786a4701bec8457cc8eeb by Harald Sitter. Committed on 29/11/2019 at 07:53. Pushed by sitter into branch 'master'. replace bespoke xkb geometry parser with xkb Summary: the bespoke parser was a horrendous drain on the build time of plasma-desktop due to recursive templates. it's been replaced with a new standalone binary that previews any model/layout/variant/options combination as requested and a qtquick UI which simplifies the actual rendering substantially. the new code is better in that it: - builds in a fraction of the time with a fraction of the power use - renders complex models (such as the tm2020 or the kinesis) correctly - because it entirely relies on xkb to figure out keysyms belonging to a given key, it's layout representation is not only substantially more complete it also correctly obeys options like eurosign:2 - renders numlock and the like (not that this is in fact very useful ^^) - is following the system palette for coloring - the paint code should be easier to graps and more robust because xkb provides completely consistent geometry and layout data meaning we can model this verbatim in qtquick and then scale the entire keyboard to a useful size - this is now a standalone application so potential input method KCMs can opt to use it (e.g. fcitx) Test Plan: preview all the layouts and all the models Reviewers: #plasma Subscribers: davidre, ngraham, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D25191 M +5-34 kcms/keyboard/CMakeLists.txt M +0-2kcms/keyboard/config-keyboard.h.cmake M +8-18 kcms/keyboard/kcm_add_layout_dialog.cpp M +5-6kcms/keyboard/kcm_add_layout_dialog.h M +19 -24 kcms/keyboard/kcm_keyboard_widget.cpp M +0-2kcms/keyboard/kcm_keyboard_widget.h D +0-7kcms/keyboard/preview/TODO D +0-245 kcms/keyboard/preview/geometry_components.cpp D +0-362 kcms/keyboard/preview/geometry_components.h D +0-593 kcms/keyboard/preview/geometry_parser.cpp D +0-161 kcms/keyboard/preview/geometry_parser.h D +0-375 kcms/keyboard/preview/kbpreviewframe.cpp D +0-95 kcms/keyboard/preview/kbpreviewframe.h D +0-128 kcms/keyboard/preview/keyaliases.cpp D +0-36 kcms/keyboard/preview/keyaliases.h D +0-133 kcms/keyboard/preview/keyboardlayout.cpp D +0-115 kcms/keyboard/preview/keyboardlayout.h D +0-100 kcms/keyboard/preview/keyboardpainter.cpp D +0-51 kcms/keyboard/preview/keyboardpainter.h D +0-901 kcms/keyboard/preview/keysym2ucs.cpp D +0-27 kcms/keyboard/preview/keysym2ucs.h D +0-59 kcms/keyboard/preview/keysymbols.cpp D +0-36 kcms/keyboard/preview/keysymbols.h D +0-83 kcms/keyboard/preview/keysymhelper.cpp D +0-41 kcms/keyboard/preview/keysymhelper.h D +0-288 kcms/keyboard/preview/symbol_parser.cpp D +0-93 kcms/keyboard/preview/symbol_parser.h A +66 -0kcms/keyboard/tastenbrett.cpp [License: GPL (v2/3)] A +35 -0kcms/keyboard/tastenbrett.h [License: GPL (v2/3)] A +34 -0kcms/keyboard/tastenbrett/CMakeLists.txt A +8-0kcms/keyboard/tastenbrett/README.md A +36 -0kcms/keyboard/tastenbrett/application.cpp [License: GPL (v2/3)] A +43 -0kcms/keyboard/tastenbrett/application.h [License: GPL (v2/3)] A +93 -0kcms/keyboard/tastenbrett/doodad.cpp [License: GPL (v2/3)] A +156 -0kcms/keyboard/tastenbrett/doodad.h [License: GPL (v2/3)] A +45 -0kcms/keyboard/tastenbrett/geometry.cpp [License: GPL (v2/3)] A +45 -0kcms/keyboard/tastenbrett/geometry.h [License: GPL (v2/3)] A +257 -0kcms/keyboard/tastenbrett/key.cpp [License: GPL (v2/3)] A +94 -0kcms/keyboard/tastenbrett/key.h [License: GPL (v2/3)] A +151 -0kcms/keyboard/tastenbrett/main.cpp [License: GPL (v2/3)] A +34 -0kcms/keyboard/tastenbrett/outline.cpp [License: GPL (v2/3)] A +46 -0kcms/keyboard/tastenbrett/outline.h [License: GPL (v2/3)] A +12 -0kcms/keyboard/tastenbrett/qml.qrc A +26 -0kcms/keyboard/tastenbrett/qml/IndicatorDoodad.qml [License: GPL (v2/3)] A +85 -0kcms/keyboard/tastenbrett/qml/Key.qml [License: GPL (v2/3)] A +63 -0kcms/keyboard/tastenbrett/qml/KeyCap.qml [License: GPL (v2/3)] A +31 -0
[ktorrent] [Bug 401035] libktorrent linking KF5::Crash but not forcing it
https://bugs.kde.org/show_bug.cgi?id=401035 Harald Sitter changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Harald Sitter --- fixed in e7c4847d9bbdc5d7c7435039aa5088d276ca5bce -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414637] new option for search
https://bugs.kde.org/show_bug.cgi?id=414637 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #3 from Maik Qualmann --- This function already exists. Look in the head of the advanced search and open the "Options". Here you can negate your search. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414484] Cannot use Rawtherapee or Darktable for raw image import on Windows
https://bugs.kde.org/show_bug.cgi?id=414484 --- Comment #23 from caulier.gil...@gmail.com --- Windows bundles are under compilation and will be published in 1 hour at usual place Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414484] Cannot use Rawtherapee or Darktable for raw image import on Windows
https://bugs.kde.org/show_bug.cgi?id=414484 --- Comment #22 from tlteebken-...@outlook.com --- Ah you're right on the exposure control, my bad, sorry. I'm new-ish to Digikam UI. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 414617] video scrolling area in monitors
https://bugs.kde.org/show_bug.cgi?id=414617 --- Comment #1 from Jean-Baptiste Mardelle --- Git commit 45ebc3fe4c9021b00dd1628614f64491edba4f24 by Jean-Baptiste Mardelle. Committed on 29/11/2019 at 06:42. Pushed by mardelle into branch 'release/19.12'. Fix clip monitor audio overlay, make monitor ruler slightly larger M +1-1src/monitor/glwidget.cpp M +7-2src/monitor/view/MonitorRuler.qml M +2-2src/monitor/view/kdenliveclipmonitor.qml https://invent.kde.org/kde/kdenlive/commit/45ebc3fe4c9021b00dd1628614f64491edba4f24 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414648] Plasma (Wayland) crashed when watching video in full screen with mpv and a notification popped up
https://bugs.kde.org/show_bug.cgi?id=414648 --- Comment #1 from Benjamin Smith --- I suspect this is related to a crash I experienced a few days ago when I connected to a VPN, and a notification appeared to let me know it connected successfully. That was bug number 414552. I edited the original report's title to reflect the notification was to blame, not the connection to VPN through plasma-nm. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414552] Plasmashell crashed when a notification appeared from Plasma's notification system
https://bugs.kde.org/show_bug.cgi?id=414552 Benjamin Smith changed: What|Removed |Added Summary|Plasmashell crashed when I |Plasmashell crashed when a |connected to a VPN via |notification appeared from |plasma-nm. |Plasma's notification ||system --- Comment #1 from Benjamin Smith --- Well, I had another crash related to a notification that appeared. This one was in Plasma Wayland. I was watching a video in mpv full screen, and another notification from Plasma's native notification system caused plasmashell to crash. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414648] Plasma (Wayland) crashed when watching video in full screen with mpv and a notification popped up
https://bugs.kde.org/show_bug.cgi?id=414648 Benjamin Smith changed: What|Removed |Added Platform|unspecified |Manjaro -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414648] New: Plasma (Wayland) crashed when watching video in full screen with mpv and a notification popped up
https://bugs.kde.org/show_bug.cgi?id=414648 Bug ID: 414648 Summary: Plasma (Wayland) crashed when watching video in full screen with mpv and a notification popped up Product: plasmashell Version: 5.17.3 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bsmith7...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.3) Qt Version: 5.13.2 Frameworks Version: 5.64.0 Operating System: Linux 5.4.0-2-MANJARO x86_64 Distribution: Manjaro Linux -- Information about the crash: - What I was doing when the application crashed: I was watching a video in mpv in full screen with the wayland backend. A notification appeared from Plasmashell's notification system and caused Plasma to crash. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f62547d1c80 (LWP 14206))] Thread 11 (Thread 0x7f6215264700 (LWP 14554)): #0 0x7f62589209ef in poll () at /usr/lib/libc.so.6 #1 0x7f62571f8120 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f62571f81f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f6258ec7b2c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f6258e6e83c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f6258ca0305 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f6258ca1530 in () at /usr/lib/libQt5Core.so.5 #7 0x7f62581924cf in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f625892b2d3 in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f62167fc700 (LWP 14424)): #0 0x7f6258198c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f6258ca7610 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f6258ca7702 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f625a930e3d in () at /usr/lib/libQt5Quick.so.5 #4 0x7f625a9310ee in () at /usr/lib/libQt5Quick.so.5 #5 0x7f6258ca1530 in () at /usr/lib/libQt5Core.so.5 #6 0x7f62581924cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f625892b2d3 in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f62177fe700 (LWP 14422)): #0 0x7f6258198c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f6258ca7610 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f6258ca7702 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f625a930e3d in () at /usr/lib/libQt5Quick.so.5 #4 0x7f625a9310ee in () at /usr/lib/libQt5Quick.so.5 #5 0x7f6258ca1530 in () at /usr/lib/libQt5Core.so.5 #6 0x7f62581924cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f625892b2d3 in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f622cb29700 (LWP 14341)): #0 0x7f6258198c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f6258ca7610 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f6258ca7702 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f625a930e3d in () at /usr/lib/libQt5Quick.so.5 #4 0x7f625a9310ee in () at /usr/lib/libQt5Quick.so.5 #5 0x7f6258ca1530 in () at /usr/lib/libQt5Core.so.5 #6 0x7f62581924cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f625892b2d3 in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f622f556700 (LWP 14339)): #0 0x7f62589209ef in poll () at /usr/lib/libc.so.6 #1 0x7f62571f8120 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f62571f81f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f6258ec7b2c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f6258e6e83c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f6258ca0305 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f6258ca1530 in () at /usr/lib/libQt5Core.so.5 #7 0x7f62581924cf in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f625892b2d3 in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f623de75700 (LWP 14335)): #0 0x7f6258198c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f6258ca7610 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f6258ca7702 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f625a930e3d in () at /usr/lib/libQt5Quick.so.5 #4 0x7f625a9310ee in () at /usr/lib/libQt5Quick.so.5 #5 0x7f6258ca1530
[kwin] [Bug 414438] Application windows don't appear until KWin is restarted
https://bugs.kde.org/show_bug.cgi?id=414438 Mufeed Ali changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #10 from Mufeed Ali --- The issue was in my .xprofile apparently. Deleting it fixed it. Sorry for the inconvenience caused and thanks for trying to help anyway. :) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 414123] Drag and drop functionality unavailable
https://bugs.kde.org/show_bug.cgi?id=414123 --- Comment #2 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.
[lattedock] [Bug 413581] Latte opening animation is extremely slow
https://bugs.kde.org/show_bug.cgi?id=413581 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #16 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.
[kmahjongg] [Bug 413628] Matching Letters Not Working
https://bugs.kde.org/show_bug.cgi?id=413628 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- 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.
[ktorrent] [Bug 413613] torrents not starting automaticaly
https://bugs.kde.org/show_bug.cgi?id=413613 --- Comment #4 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.
[Heaptrack] [Bug 413108] Compilation/Syntax error: template specialization in different namespace
https://bugs.kde.org/show_bug.cgi?id=413108 --- Comment #2 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 408057] Areas transformed with the transform tool disappear
https://bugs.kde.org/show_bug.cgi?id=408057 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #10 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.
[krita] [Bug 413949] Docker Disappeared - Small Color Selector
https://bugs.kde.org/show_bug.cgi?id=413949 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #8 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.
[plasmashell] [Bug 373579] Battery label is cut off on small (hidpi) panels
https://bugs.kde.org/show_bug.cgi?id=373579 --- 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.
[plasmashell] [Bug 406213] Battery indicator randomly disappears from Systray
https://bugs.kde.org/show_bug.cgi?id=406213 --- Comment #4 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.
[plasmashell] [Bug 405286] Selecting ‘Configure Desktop’ when desktop configuration window is minimized has no effect
https://bugs.kde.org/show_bug.cgi?id=405286 --- Comment #6 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 414647] New: Grow / Shrink Selection only change the width of a selection
https://bugs.kde.org/show_bug.cgi?id=414647 Bug ID: 414647 Summary: Grow / Shrink Selection only change the width of a selection Product: krita Version: 4.2.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: tysont...@gmail.com Target Milestone: --- In Krita 4.2.8, it was reported to me that the Grow / Shrink Selection functions appear to be broken. They can only change the width of a selection. It's happening with both the Selection Tools and Fill Tool. Selection Tools: Right click menu -> Transform -> Grow Selection / Shrink Selectoion Fill tool: Tool Options -> Grow selection slider I can confirm this by: 1) Make a small circular selection 2) Grow the selection 3) It's now a oval selection -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 414646] Kdenlive in Windows crashes when opening a project created under a different Locale
https://bugs.kde.org/show_bug.cgi?id=414646 --- Comment #1 from Brett --- Relevant forum discussion: https://forum.kde.org/viewtopic.php?f=265=163455 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 414646] New: Kdenlive in Windows crashes when opening a project created under a different Locale
https://bugs.kde.org/show_bug.cgi?id=414646 Bug ID: 414646 Summary: Kdenlive in Windows crashes when opening a project created under a different Locale Product: kdenlive Version: 19.08.3 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: critical Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: daloo...@gmail.com Target Milestone: --- SUMMARY Kdenlive in Windows shows a visual C++ Runtime error and crashes when attempting to open a project that was created and saved under a different locale. The issue seems to be due to the fact that some locales use a comma instead of a period in their timestamps. STEPS TO REPRODUCE 1. Create a project with a machine using the locale fr_CA and save it. See http://txt.do/1oxnn for an example project. 2. Move to a machine running Windows and with the locale en_US. Attempt to open the previous project. OBSERVED RESULT Crash: Runtime Error! This program has requested yadda yadda yadda... EXPECTED RESULT Kdenlive gives a warning about the project being created in a different locale and offers to save it in the current locale. SOFTWARE/OS VERSIONS Windows: 8 macOS: Linux/KDE Plasma: Manjaro (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Here is a workaround: 1. Open the project in a text editor 2. Change LC_NUMERIC="fr_CA.UTF-8" to LC_NUMERIC="en_US" 3. Use find and replace to transform all of the commas into periods in the timestamps. For example: in the original file now becomes this: 4. The project will now open properly without crashing Kdenlive -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414645] New: Crash transform
https://bugs.kde.org/show_bug.cgi?id=414645 Bug ID: 414645 Summary: Crash transform Product: krita Version: 4.2.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Transform Assignee: krita-bugs-n...@kde.org Reporter: sebastianl...@hotmail.com Target Milestone: --- SUMMARY when i use the transform tool, krita crash and close STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 414644] New: Cannot reorder music tracks in the Play Queue
https://bugs.kde.org/show_bug.cgi?id=414644 Bug ID: 414644 Summary: Cannot reorder music tracks in the Play Queue Product: juk Version: 19.08.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: whee...@kde.org Reporter: lulosals...@gmail.com CC: mp...@kde.org Target Milestone: --- Created attachment 124174 --> https://bugs.kde.org/attachment.cgi?id=124174=edit Dragging a file in the Play Queue appears to work but does not SUMMARY Cannot reorder music tracks in the Play Queue although the functionality appears to be there to do so. Within the Play Queue, clicking and dragging a music track displays an arrow cursor with the + sign next to the cursor and you actually can see yourself dragging a track around, with an insertion bar showing where it will move to, but when you let go of the button, the music track doesn't actually move within the list. It's like all the UI functionality is there, but the action isn't being acted upon. STEPS TO REPRODUCE 1. From the Collection List, right-click on a music track, choose Add to Play Queue. Repeat 2 more times. 2. Go to the Play Queue with the 3 added tracks visible. 3. Click and drag on any of the music tracks and try to reorder them. They will drag around and appear to be moved, but in actuality nothing happens when the mouse button is released. SOFTWARE/OS VERSIONS Linux: 4.15.0-70 64-bit KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION This is actually Juk 19.08.3 (not 19.08.1) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414643] New: "Create From Clipboard" inserts image as an alpha mask when background is set to fill layer
https://bugs.kde.org/show_bug.cgi?id=414643 Bug ID: 414643 Summary: "Create From Clipboard" inserts image as an alpha mask when background is set to fill layer Product: krita Version: 4.2.8 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: jshortho...@protonmail.com Target Milestone: --- When using the "create from clipboard" functionality if the background type in the "Content" tab is set to "As fill layer" the clipboard image is inserted as an alpha mask to the background layer. I would have expected that when using this feature the clipboard image would be inserted on a raster layer above the background layer. I don't think the current behaviour is expected or useful, the resultant image does not resemble what was in the clipboard. The reason this is a problem is that I always use the fill layer background type when creating normal documents, and this preference is also applied when creating from clipboard. To work around this issue I would have to manually change the background type every time. I suggest that either a) the preferences for "custom document" and "create from clipboard" are split from each other so I can have one background type for one and one for the other, or b) the background type is ignored and a raster layer is always used or c) whenever "fill layer" is selected a new raster layer with the image is always inserted above the background. STEPS TO REPRODUCE 1. Go to File > New > Create from Clipboard 2. In the content tab set the background to "As fill layer" 3. Set layers to 2 4. Click create OBSERVED RESULT A fill background with the image as an alpha channel is created. The raster layer above is completely empty. The document does not resemble the clipboard image. EXPECTED RESULT A fill background layer is created with a raster layer containing the image above it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 414003] Systemsettings crashes in QQmlObjectCreator::createInstance() when I'm trying to open any icon a second time
https://bugs.kde.org/show_bug.cgi?id=414003 --- Comment #37 from Nate Graham --- This bug is already marked as fixed (in Kirigami 5.65). There is no need to add further information unless you are using the version of the code that supposedly contains the fix and you can still reproduce the issue. Otherwise just sit tight. :) -- You are receiving this mail because: You are watching all bug changes.
[kig] [Bug 414641] coordinate precision cannot be changed
https://bugs.kde.org/show_bug.cgi?id=414641 Kevin Kofler changed: What|Removed |Added Ever confirmed|0 |1 CC||kevin.kof...@chello.at Status|REPORTED|CONFIRMED --- Comment #1 from Kevin Kofler --- As I wrote in the downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1311513 I can confirm this. It is easily reproducible: the dialog has no OK button (nor a Cancel nor Close button for that matter), and closing it through the title bar's close button does not save the settings, so they are lost no matter what you do. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414642] New: Double clicking text to open text editor crashes krita
https://bugs.kde.org/show_bug.cgi?id=414642 Bug ID: 414642 Summary: Double clicking text to open text editor crashes krita Product: krita Version: nightly build (please specify the git hash!) Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Tool/Text Assignee: krita-bugs-n...@kde.org Reporter: acc4commissi...@gmail.com Target Milestone: --- SUMMARY 4.3.0-prealpha (git dea9c67) 1 Create a text shape, and double click it to open the text editor. 2 Crash. It doesn't happen in 4.2.8. SOFTWARE/OS VERSIONS Windows: Win7 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Error occurred on Friday, November 29, 2019 at 08:54:11. krita.exe caused an Access Violation at location 07FED73BDEC8 in module Qt5Core.dll Reading from location . AddrPC Params 07FED73BDEC8 000E 07FE0002 597FF500 Qt5Core.dll!0x22dec8 QObject::connect+0x188 07FED5C0D85E 59AD6C50 07FED8EBA5E4 0008 Qt5Widgets.dll!0x21d85e QAbstractItemView::setItemDelegate+0x15e 07FED5AE4254 07FED8ED2A23 07FED73E94B1 59D22040 Qt5Widgets.dll!0xf4254 QComboBox::setItemDelegate+0x54 07FED8EC29BB 0022B060 0022BC00 59AD4110 krita_tool_svgtext.dll!0x129bb KisFontFamilyComboBox::setInitialized+0xfb 07FED8EBC9B6 0020 004E 0018 krita_tool_svgtext.dll!0xc9b6 SvgTextEditor::setShape+0x196 07FED8EBED67 0048 0048 004E02C8 krita_tool_svgtext.dll!0xed67 SvgTextTool::showEditor+0x207 07FED8EBEFCB 0048 0022B360 0022B2F8 krita_tool_svgtext.dll!0xefcb SvgTextTool::mouseReleaseEvent+0x4b 07FED3DF2C60 0048 0022BC00 C0984C00 libkritaflake.dll!0x52c60 KoToolProxy::mouseReleaseEvent+0x60 07FED3DF2D05 40984B5A7165 4094E371A723 libkritaflake.dll!0x52d05 KoToolProxy::mousePressEvent+0x65 07FED3DF30C1 0001 libkritaflake.dll!0x530c1 KoToolProxy::mouseDoubleClickEvent+0x21 07FED3FD5033 1EBD2540 07FED424E8BB 3C4CE130 libkritaui.dll!0x15033 KisToolProxy::forwardEvent+0x233 07FED4243F3C 0022BC00 07FE0001 07FED4242A90 libkritaui.dll!0x283f3c KisToolInvocationAction::end+0x8c 07FED424FC8D 0028 210FA2C0 libkritaui.dll!0x28fc8d KisShortcutMatcher::tryRunReadyShortcut+0x1bd 07FED4251942 210FA2C0 0001 libkritaui.dll!0x291942 KisShortcutMatcher::buttonPressed+0x102 07FED423DEC0 24A05150 07FED7220DD0 0022B6E0 libkritaui.dll!0x27dec0 KisInputManager::eventFilterImpl+0x1c80 07FED738BBA0 0022FBB0 0001 210FA2C0 Qt5Core.dll!0x1fbba0 QCoreApplication::applicationVersionChanged+0x1a0 07FED59F7BB5 249F22D0 0003 02490248 Qt5Widgets.dll!0x7bb5 QApplicationPrivate::notify_helper+0x75 07FED59FFBEA 07FED71B212F Qt5Widgets.dll!0xfbea QApplication::notify+0x13aa 07FED4298936 3FF0 C0709000 libkritaui.dll!0x2d8936 KisApplication::notify+0x16 07FED738D298 3FF0 Qt5Core.dll!0x1fd298 QCoreApplication::sendSpontaneousEvent+0x1a8 07FED59FDFE8 035A0002 Qt5Widgets.dll!0xdfe8 QApplicationPrivate::sendMouseEvent+0x208 07FED5A4A84D 07A5A230 07FED738BAA1 00090008 Qt5Widgets.dll!0x5a84d QDesktopWidget::qt_metacall+0x26dd 07FED5A4D5B3 0022FBB0 024E8470 0001 Qt5Widgets.dll!0x5d5b3 QDesktopWidget::qt_metacall+0x5443 07FED59F7BDC 0068 0068 004E02E8 Qt5Widgets.dll!0x7bdc QApplicationPrivate::notify_helper+0x9c 07FED59FEBF3 025C8090 07FED71B212F 0022C150 Qt5Widgets.dll!0xebf3 QApplication::notify+0x3b3 07FED4298936 07FED5FAA524 0020 libkritaui.dll!0x2d8936 KisApplication::notify+0x16 07FED738D298 0022C1A8 210FA2C0 24A05150 Qt5Core.dll!0x1fd298 QCoreApplication::sendSpontaneousEvent+0x1a8 07FED5F96D12 0020 07FED7392F62 0001 Qt5Gui.dll!0x36d12 QGuiApplicationPrivate::processMouseEvent+0xa02 07FED5F97DA5 025BD630 024E8510 001E03A8 Qt5Gui.dll!0x37da5 QGuiApplicationPrivate::processWindowSystemEvent+0x105 07FED5F70E7C 7767B792 0203 Qt5Gui.dll!0x10e7c QWindowSystemInterface::sendWindowSystemEvents+0x44c 07FED73E7B1A
[frameworks-kirigami] [Bug 414003] Systemsettings crashes in QQmlObjectCreator::createInstance() when I'm trying to open any icon a second time
https://bugs.kde.org/show_bug.cgi?id=414003 john4deidre2...@xtra.co.nz changed: What|Removed |Added CC||john4deidre2...@xtra.co.nz -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 414003] Systemsettings crashes in QQmlObjectCreator::createInstance() when I'm trying to open any icon a second time
https://bugs.kde.org/show_bug.cgi?id=414003 --- Comment #36 from john4deidre2...@xtra.co.nz --- Created attachment 124173 --> https://bugs.kde.org/attachment.cgi?id=124173=edit New crash information added by DrKonqi kinfocenter (5.17.3) using Qt 5.13.1 - What I was doing when the application crashed: i selected file sync first. that took a very long time to respond. when it finally got to file sync, i then selected memory, it then crashed -- Backtrace (Reduced): #6 0x7f0ae301e60f in QObject::property (this=0x5576042eedc0, name=name@entry=0x7f0ac87b1264 "gridUnit") at kernel/qobject.cpp:3974 #7 0x7f0ac87921e0 in ColumnViewoperator() (__closure=) at /usr/src/debug/kirigami2-5.64.0-1.1.x86_64/src/columnview.cpp:45 #8 ColumnView::classBegin (this=0x5576046c5130) at /usr/src/debug/kirigami2-5.64.0-1.1.x86_64/src/columnview.cpp:1427 #9 0x7f0ae22cd85f in QQmlObjectCreator::createInstance (this=0x7ffcea49e850, index=38, parent=, isContextObject=) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-1.2.x86_64/src/qml/qml/qqmlobjectcreator.cpp:1280 #10 0x7f0ae22cbe6a in QQmlObjectCreator::setPropertyBinding (this=0x7ffcea49e850, bindingProperty=0x7f0ab80d7288, binding=0x7f0ac8b4de24) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-1.2.x86_64/src/qml/qml/qqmlobjectcreator.cpp:856 -- You are receiving this mail because: You are watching all bug changes.
[kig] [Bug 414641] New: coordinate precision cannot be changed
https://bugs.kde.org/show_bug.cgi?id=414641 Bug ID: 414641 Summary: coordinate precision cannot be changed Product: kig Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: david.narv...@computer.org Reporter: paol...@dmf.unicatt.it Target Milestone: --- Description of problem: the number of decimal digits displayed in labels cannot be changed Version-Release number of selected component (if applicable): latest Git source How reproducible: There is an input panel for changing the value, but it is missing an "OK" button! Steps to Reproduce: 1. Start kig 2. Open "Settings" menu 3. Chose "Set coordinate precision" Actual results: You can cange the number in the input field, but there is no way to accept the value (no "OK" button visible) -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 414640] New: Kaffeine not play digital tv after upgrade kernel 5
https://bugs.kde.org/show_bug.cgi?id=414640 Bug ID: 414640 Summary: Kaffeine not play digital tv after upgrade kernel 5 Product: kaffeine Version: 2.0.14 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mchehab+sams...@kernel.org Reporter: ale_sca...@yahoo.it Target Milestone: --- SUMMARY Kaffeine doesn't play dvb channels (remains black screen and without audio, the only thing shown is the channel's name ) on asus p7131 hybrid tv card after linux kernel upgrade to kernel 5.0.0-37-generic STEPS TO REPRODUCE 1. upgrade to kernel 5.0.0-37-generic 2. open kaffeine 3. select digital tv OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 18.04 (available in About System) KDE Plasma Version: 5.12.9 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399234] Compositing breaks system tray functionality in programs running under Wine Staging
https://bugs.kde.org/show_bug.cgi?id=399234 --- Comment #30 from Konrad Materka --- (In reply to Eliphas from comment #29) > I am using the wine-development from default stable LTS, when I tried to > install the winehq staging it wanted some dependency from another repo > (libfaudio0 from SDL I think) Oh, I remember! Yes, you need to install libfaudio0 first. Unfortunately Ubuntu 18.04 does not have it, I just installed deb packages manually, both i386 and amd64 are required. Anyway, I tested with wine-development, no difference on my computer so most probably it is not related to Wine version. The original report was for Wine Staging, but your problem is different. > > From logs I can see that clicks are sent... The coordinates are strange - is > > your monitor rotated? > > Oh sorry about that. Yes, I have a 1440x900 in normal mode (where the kde > taskbar/systray are) and a 900x1600 rotated on the right side. I was not able to reproduce, but maybe it is somehow related to multi-monitor setup? Click coordinates are: x:1156, y:1583 (where (0,0) is in the top-left corner). x:1156 seems fine, it is less than 1440. But y:1583 is weird, definitely more than 900 from the first screen, more likely it is a coordinate from the second screen. Is it possible that these two overlap? Can you share output from: "kscreen-doctor -o" command? Can you retest (with logs enabled) with second screen disabled, different panel locations etc? Just to get some use case when it is working and when not. This will probably mess with your setup and layout, sorry for that. To fix this I really need to reproduce it locally and without detailed information I can only guess. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 395497] Menubar - No text
https://bugs.kde.org/show_bug.cgi?id=395497 --- Comment #25 from Albert Astals Cid --- The big question is, anyone has any idea how you ended up with those corrupted shell.rc files in your .local ? Any of you did any kind of menu costumization that you remember either now or in the past? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356711] XembedSNIProxy prevents KWin from unredirecting fullscreen SDL2 apps
https://bugs.kde.org/show_bug.cgi?id=356711 Konrad Materka changed: What|Removed |Added CC||mate...@gmail.com --- Comment #5 from Konrad Materka --- Hi Danni H, This bug is quite old, but maybe you are still there and can answer few questions: 1. Are you still experiencing microstutters? 2. If yes, does it happens always when xembedsniproxy is running or only when it is rendering some icons? Dropbox no longer uses XEmbed, you need to test with different application, for example: xchat, tuxguitar, hexchat, liferea or any app via Wine. For each XEmbed system tray icon, xembedsniproxy creates new window. It should be always in the background, but if you saw black square that was probably it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399234] Compositing breaks system tray functionality in programs running under Wine Staging
https://bugs.kde.org/show_bug.cgi?id=399234 --- Comment #29 from Eliphas --- (In reply to Konrad Materka from comment #28) > Hi Eliphas, > > You are using very old Wine version, uninstall it and install from: > https://wiki.winehq.org/Ubuntu I am using the wine-development from default stable LTS, when I tried to install the winehq staging it wanted some dependency from another repo (libfaudio0 from SDL I think) and I wanted to stay "stable" if you may have wanted me to do more tests with this version because that bug looks like the same and affecting the mainstream LTS (with not-so-mainstream KDE from Neon Testing Edition). Will enable the repos and retest. > Can you explain what does it mean "I have the same problem"? I assume that > with compositor enabled clicks are not working and click are working with > compositor disabled? Yes, exactly. Turning composite off before a wine program launch makes the systray icon work. > From logs I can see that clicks are sent... The coordinates are strange - is > your monitor rotated? Oh sorry about that. Yes, I have a 1440x900 in normal mode (where the kde taskbar/systray are) and a 900x1600 rotated on the right side. > I will try to add one more fix in Plasma 5.17.4, can you retest then? Sure, will install wine-staging from winehq and will disable secondary monitor when testing. Can retest it in about 12hs on that machine (will refresh pkgs and reboot before the test). -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 414639] New: Fails to connect to x11vnc server unless logged on. SDDM
https://bugs.kde.org/show_bug.cgi?id=414639
Bug ID: 414639
Summary: Fails to connect to x11vnc server unless logged on.
SDDM
Product: kscreenlocker
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: archer_of_wis...@hotmail.com
CC: bhus...@gmail.com
Target Milestone: ---
SUMMARY
Fails to connect to x11vnc server after reboot unless logged on in the
specified user account.
STEPS TO REPRODUCE
1. Put *** /usr/bin/x11vnc -forever -auth /var/run/$(ps xau | grep -o
"sddm/{.*}" | head -n 1) -bg *** into /usr/share/sddm/scripts/Xsetup
2. Reboot and don't login.
3. Connect with VNC client - Fails
OBSERVED RESULT
Cannot connect to server. Only works when logged in. Not before being logged
in.
EXPECTED RESULT
After a reboot, SDDM starts vnc server. User can login remotely.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon 5.17.3
(available in About System)
KDE Plasma Version: 5.17.3
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 399234] Compositing breaks system tray functionality in programs running under Wine Staging
https://bugs.kde.org/show_bug.cgi?id=399234 Konrad Materka changed: What|Removed |Added Status|NEEDSINFO |REOPENED Resolution|WAITINGFORINFO |--- --- Comment #28 from Konrad Materka --- Hi Eliphas, You are using very old Wine version, uninstall it and install from: https://wiki.winehq.org/Ubuntu Can you explain what does it mean "I have the same problem"? I assume that with compositor enabled clicks are not working and click are working with compositor disabled? >From logs I can see that clicks are sent... The coordinates are strange - is your monitor rotated? I will try to add one more fix in Plasma 5.17.4, can you retest then? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399923] Segmentation fault during face detection
https://bugs.kde.org/show_bug.cgi?id=399923 --- Comment #274 from Maik Qualmann --- Git commit 62ab5314c3b32a83c0b765b67c251ee2bd810b37 by Maik Qualmann. Committed on 28/11/2019 at 21:53. Pushed by mqualmann into branch 'master'. add debug, we need the loading task status M +2-0core/libs/threadimageio/preview/previewtask.cpp https://invent.kde.org/kde/digikam/commit/62ab5314c3b32a83c0b765b67c251ee2bd810b37 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399923] Segmentation fault during face detection
https://bugs.kde.org/show_bug.cgi?id=399923 --- Comment #273 from Maik Qualmann --- However, I see no error message that the memory could not be requested. Another possibility is that the shared image data is changed by another thread at the same time. Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414638] New: transform tool near instantly crashes krita
https://bugs.kde.org/show_bug.cgi?id=414638 Bug ID: 414638 Summary: transform tool near instantly crashes krita Product: krita Version: 4.2.8 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Tools/Transform Assignee: krita-bugs-n...@kde.org Reporter: pineapplewitn...@gmail.com Target Milestone: --- SUMMARY when i press on the transorm tool or use ctrl+t, krita crashes. sometimes it works fine for a minute or two before crashing, in one case crashing because i switched from it to the brush tool. STEPS TO REPRODUCE 1. open krita 2. open or create a canvas 3. use the transform tool SOFTWARE/OS VERSIONS Linux (x86_64) release 5.3.13-arch1-1 KRITA DID NOT CLOSE CORRECTLY SESSION: 28 Nov 2019 13:49:07 -0600. Executing krita WARNING: This file contains information about your system and the images you have been working with. If you have problems with Krita, the Krita developers might ask you to share this file with them. The information in this file is not shared automatically with the Krita developers in any way. You can disable logging to this file in Krita's Configure Krita Dialog. Please review the contents of this file before sharing this file with anyone. Krita Version: 4.2.8 Languages: C Hidpi: true Qt Version (compiled): 5.13.2 Version (loaded): 5.13.2 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.3.13-arch1-1 Pretty Productname: Arch Linux Product Type: arch Product Version: unknown OpenGL Info Vendor: "X.Org" Renderer: "Radeon RX 560 Series (POLARIS11, DRM 3.33.0, 5.3.13-arch1-1, LLVM 9.0.0)" Version: "4.5 (Compatibility Profile) Mesa 19.2.6" Shading language: "4.50" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 4.5, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Version: 4.5 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsOpenGLES: true isQtPreferOpenGLES: false Hardware Information GPU Acceleration: auto Memory: 7892 Mb Number of Cores: 4 Swap Location: /tmp Current Settings Current Swap Location: /tmp Undo Enabled: 1 Undo Stack Limit: 30 Use OpenGL: 1 Use OpenGL Texture Buffer: 1 Use AMD Vectorization Workaround: 0 Canvas State: OPENGL_SUCCESS Autosave Interval: 900 Use Backup Files: 1 Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Use Win8 Pointer Input: 0 Use RightMiddleTabletButton Workaround: 0 Levels of Detail Enabled: 0 Use Zip64: 0 28 Nov 2019 13:49:24 -0600: CLOSING SESSION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399923] Segmentation fault during face detection
https://bugs.kde.org/show_bug.cgi?id=399923 --- Comment #272 from timo...@zoho.com --- Created attachment 124172 --> https://bugs.kde.org/attachment.cgi?id=124172=edit here's one additional trace taken during the last run -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 414302] Ecosia search engine doesn't work as default
https://bugs.kde.org/show_bug.cgi?id=414302 --- Comment #4 from luca.finizio.m...@hotmail.it --- I still have this problem on Linux Mint 19.2. I made a video where you can see the problem: https://youtu.be/Zc7tn8x_W4Q I also tried to set the default search engine and then restart the pc, but the problem is still there. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399923] Segmentation fault during face detection
https://bugs.kde.org/show_bug.cgi?id=399923 --- Comment #271 from Maik Qualmann --- The cause here might be that we did not get the requested memory as a block. Hmm, yes we have to check if we got the memory, but what if not? Just do not rotate? On the other hand, we have to look at where we lose memory somewhere, the memory consumption seems to me a bit too high. Maik -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 414593] Huge memory usage with some PDFs
https://bugs.kde.org/show_bug.cgi?id=414593 Albert Astals Cid changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #3 from Albert Astals Cid --- the pre-rendered images of the 1049 pages -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 412952] Dolphin seems to add extra quotes when deleting trailing quote
https://bugs.kde.org/show_bug.cgi?id=412952
Ismael Asensio changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED |RESOLVED
Latest Commit||https://commits.kde.org/dol
||phin/6776fbc94760188daeca0a
||b30e49f645f225f008
--- Comment #4 from Ismael Asensio ---
Git commit 6776fbc94760188daeca0ab30e49f645f225f008 by Ismael Asensio.
Committed on 28/11/2019 at 21:08.
Pushed by iasensio into branch 'release/19.12'.
fix(search): Fix baloo searchString parsing
Summary:
Fix the parsing of Baloo query `searchString` to represent its parameters
properly
in the search box:
# Baloo terms (`rating`, `modified`) are added to the user search text:
{F7575590}
# Extra quotes are added to the search text:
https://bugs.kde.org/show_bug.cgi?id=412952
This revision supersedes D24422, by making the fixes on the new dolphin query
model,
instead of directly on the UI.
FIXED IN: 19.11.90
Test Plan:
- `bin/dolphinquerytest` passes without `XFAIL`s
- Dolphin search box is not garbled by search terms or quotes
Reviewers: elvisangelaccio, bruns, ngraham, #dolphin
Reviewed By: elvisangelaccio
Subscribers: kfm-devel
Tags: #dolphin
Differential Revision: https://phabricator.kde.org/D25260
M +22 -4src/search/dolphinquery.cpp
M +0-18 src/tests/dolphinquerytest.cpp
https://commits.kde.org/dolphin/6776fbc94760188daeca0ab30e49f645f225f008
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 414593] Huge memory usage with some PDFs
https://bugs.kde.org/show_bug.cgi?id=414593 --- Comment #2 from Andrius --- But it should only use the memory to load the document, what else is there to take up so much space? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414621] I cannot press play to play the animation in krita to look it over. It will not play no matter how much I try.
https://bugs.kde.org/show_bug.cgi?id=414621 Ahab Greybeard changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||ahab.greybe...@hotmail.co.u ||k --- Comment #1 from Ahab Greybeard --- I've just run the 4.2.8 Windows portable 64-bit .zip package and opened an animation and played it with no problems. I also created a new animation and that played with no problems. Which version of Windows are you using? Did your animation play ok in a previous version of krita? Can you attach a full screenshot that includes the Layers docker, the Timeline docker and the Animation docker? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 414402] Dolphin service fails to spawn a new instance of Dolphin
https://bugs.kde.org/show_bug.cgi?id=414402 Elvis Angelaccio changed: What|Removed |Added Version Fixed In||19.12.0 Resolution|--- |FIXED Latest Commit||https://commits.kde.org/dol ||phin/089a05b4edfd7a70e50ed7 ||d8b158cbcc50538d36 Status|CONFIRMED |RESOLVED --- Comment #4 from Elvis Angelaccio --- Git commit 089a05b4edfd7a70e50ed7d8b158cbcc50538d36 by Elvis Angelaccio. Committed on 28/11/2019 at 20:52. Pushed by elvisangelaccio into branch 'release/19.12'. Force dbus introspection on the Dolphin_1 object Summary: QtDBus caches known interfaces when passing a non-empty interface name to the QDbusInterface constructor. This is an issue when calling the FileManager1 methods more than once, because `preferred` could be a valid interface from the cache, but it would later fail to call the `openFiles`/`openDirectories` methods on the main window. By passing an empty interface name, we prevent QtDBus from using the cache so that we always get an invalid interface when calling the FileManager1 methods on a daemonized dolphin process (that doesn't have the Dolphin_1 dbus object). FIXED-IN: 19.12.0 Test Plan: 1. dolphin --daemon 2. qdbus org.freedesktop.FileManager1 /org/freedesktop/FileManager1 ShowFolders "/tmp" "" 3. Close the dolphin window that was just opened. 4. Start a normal dolphin process 5. qdbus org.freedesktop.FileManager1 /org/freedesktop/FileManager1 ShowFolders "/tmp" "" 6. Close again the dolphin window 7. qdbus org.freedesktop.FileManager1 /org/freedesktop/FileManager1 ShowFolders "/tmp" "" Subscribers: kfm-devel Tags: #dolphin Differential Revision: https://phabricator.kde.org/D25510 M +1-1src/global.cpp https://commits.kde.org/dolphin/089a05b4edfd7a70e50ed7d8b158cbcc50538d36 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414484] Cannot use Rawtherapee or Darktable for raw image import on Windows
https://bugs.kde.org/show_bug.cgi?id=414484 --- Comment #21 from Maik Qualmann --- Ok, the image is displayed perfectly in digiKam, no bug ((:-)) You have the display of overexposure enabled in the image editor, bottom right, the 2 icons. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414484] Cannot use Rawtherapee or Darktable for raw image import on Windows
https://bugs.kde.org/show_bug.cgi?id=414484 --- Comment #20 from Maik Qualmann --- The modification of Comment 16 is not yet current bundle included, until tomorrow when Gilles builds a new one. Maik -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 414541] cantor git master and maxima 5.43 crash
https://bugs.kde.org/show_bug.cgi?id=414541 Alexander Semke changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 414541] cantor git master and maxima 5.43 crash
https://bugs.kde.org/show_bug.cgi?id=414541 Alexander Semke changed: What|Removed |Added Assignee|warqu...@gmail.com |alexander.se...@web.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 411690] QCH build fails with doxygen 1.8.16
https://bugs.kde.org/show_bug.cgi?id=411690 Antonio Rojas changed: What|Removed |Added CC||eugene.shalygin+bugzilla.kd ||e...@gmail.com --- Comment #5 from Antonio Rojas --- *** Bug 414634 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 414634] KDeclarative installation fails when building with qch
https://bugs.kde.org/show_bug.cgi?id=414634 Antonio Rojas changed: What|Removed |Added CC||aro...@archlinux.org Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Antonio Rojas --- *** This bug has been marked as a duplicate of bug 411690 *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 414636] New: MP4 different from kdenlive
https://bugs.kde.org/show_bug.cgi?id=414636 Bug ID: 414636 Summary: MP4 different from kdenlive Product: kdenlive Version: 19.08.3 Platform: Other OS: MS Windows Status: REPORTED Severity: major Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: isabiagio...@gmail.com Target Milestone: --- SUMMARY In the Kdenlive editor, my film runs smoothly but when exported in mp4 all the added images (with zoom effects) and all the transitions have randomly changed I can't export the film I see in Kdenlive to any other format. The only explanation I can find is the following : I have started editing with an older version. When my kdenlive upgraded, may it have corrupt the files somehow ? Should I reinstall an older version ??? Please help STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 414631] gwenview crashes with output "Floating point exception (core dumped)"
https://bugs.kde.org/show_bug.cgi?id=414631 --- Comment #1 from Julian --- The problem only occurs when the Thumbnail Bar is activated. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 414635] New: Very strange code at main.cpp
https://bugs.kde.org/show_bug.cgi?id=414635
Bug ID: 414635
Summary: Very strange code at main.cpp
Product: Spectacle
Version: 19.11.80
Platform: Debian stable
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: General
Assignee: m...@baloneygeek.com
Reporter: safinas...@mail.ru
CC: k...@david-redondo.de
Target Milestone: ---
I am attempting to understand how Spectacle works. So I read its code. I found
the following very strange code in Main.cpp in current master (
4370c5484972a02497bf4bb479f4cc1586b6924c ,
https://github.com/KDE/spectacle/blob/4370c5484972a02497bf4bb479f4cc1586b6924c/src/Main.cpp
):
} else if (lCmdLineParser.isSet(QStringLiteral("windowundercursor"))) {
lCaptureMode = Spectacle::CaptureMode::TransientWithParent;
} else if (lCmdLineParser.isSet(QStringLiteral("transientonly"))) {
lCaptureMode = Spectacle::CaptureMode::WindowUnderCursor;
This seems like a typo. It seems the following code should be:
} else if (lCmdLineParser.isSet(QStringLiteral("windowundercursor"))) {
lCaptureMode = Spectacle::CaptureMode::WindowUnderCursor;
} else if (lCmdLineParser.isSet(QStringLiteral("transientonly"))) {
lCaptureMode = Spectacle::CaptureMode::TransientWithParent;
Even if this is not typo, please add some comment, which will explain such
strange code. Or (better) rename something to help people, who read you code.
I am reading code of Spectacle, because I'm trying to capture video from screen
in my very unusual scenario, see https://bugs.kde.org/show_bug.cgi?id=412731 if
you are interested
--
You are receiving this mail because:
You are watching all bug changes.
[lattedock] [Bug 414620] Dock raises up on each focus of a modal window/menu
https://bugs.kde.org/show_bug.cgi?id=414620 --- Comment #5 from Michail Vourlakos --- All docks are setting Dodge Active as default visibility mode. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 414634] KDeclarative installation fails when building with qch
https://bugs.kde.org/show_bug.cgi?id=414634 --- Comment #1 from Eugene Shalygin --- Created attachment 124171 --> https://bugs.kde.org/attachment.cgi?id=124171=edit build.log -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 414634] New: KDeclarative installation fails when building with qch
https://bugs.kde.org/show_bug.cgi?id=414634 Bug ID: 414634 Summary: KDeclarative installation fails when building with qch Product: frameworks-kdeclarative Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: eugene.shalygin+bugzilla@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. cmake ... -DBUILD_QCH=yes 2. ninja 3. ninja install OBSERVED RESULT CMake Error at src/cmake_install.cmake:49 (file): file INSTALL cannot find "/var/portage/tmp/portage/kde-frameworks/kdeclarative-/work/kdeclarative-_build/src/KF5Declarative.qch". Call Stack (most recent call first): cmake_install.cmake:76 (include) SOFTWARE/OS VERSIONS Linux/KDE Plasma: git master KDE Plasma Version: git master KDE Frameworks Version: git master Qt Version: 5.14.0 beta 3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 414620] Dock raises up on each focus of a modal window/menu
https://bugs.kde.org/show_bug.cgi?id=414620 --- Comment #4 from Jazz --- That resolves this issue. It's a bit confusing though, since I would expect this mode to be the default, but ok... glad that it's resolved. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399923] Segmentation fault during face detection
https://bugs.kde.org/show_bug.cgi?id=399923 --- Comment #270 from timo...@zoho.com --- I was using exiv2 0.27.1. I've updated to 0.27.2, disabled color management (which was enabled in the other runs, since every run starts from a clean digikam with default configuration). With 105ccfd47cc8ac73037eac0d6873581a9e49c1aa: > digikam.general: Found 0 faces in "IMG_20180620_172836326_HDR.jpg" > QSize(4160, 3120) QSize(4160, 3120) > digikam.general: Removing old entries () > digikam.general: Cancel Main Thread > [Thread 0x7fff1affd700 (LWP 23850) exited] > digikam.general: One job is done > digikam.general: Cancel Main Thread > [Thread 0x7fff1a7fc700 (LWP 23851) exited] > digikam.general: Check for finish: 10 packages, 0 infos to filter, > hasFinished() false > digikam.general: Try to get preview from > "/tmp/tmp.PyUwvaBSNi/Pictures/p/something/IMG_20180621_105141093.jpg" > digikam.general: Preview quality: 1 > digikam.dimg: > "/tmp/tmp.PyUwvaBSNi/Pictures/p/something/IMG_20180621_105141093.jpg" : > "JPEG" file identified > digikam.metaengine: Exif color-space tag is sRGB. Using default sRGB ICC > profile. > digikam.facesengine: Good rect = QRect(248,151 32x42) , conf = 0.81234 > digikam.general: Found 1 faces in "IMG_20180620_215959940_HDR.jpg" > QSize(4160, 3120) QSize(4160, 3120) > digikam.general: Removing old entries () > digikam.general: Found 0 faces in "IMG_20180621_100509050.jpg" QSize(3120, > 4160) QSize(3120, 4160) > digikam.general: Removing old entries () > > Thread 1137 "Thread (pooled)" received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0x7fff5cf59700 (LWP 4434)] > Digikam::DImg::rotate (this=0x256ef48, angle=angle@entry=Digikam::DImg::ROT90) > at /tmp/tmp.PyUwvaBSNi/digikam/core/libs/dimg/dimg_transform.cpp:119 > 119 *to = *from++; > (gdb) bt > #0 Digikam::DImg::rotate (this=0x256ef48, > angle=angle@entry=Digikam::DImg::ROT90) at > /tmp/tmp.PyUwvaBSNi/digikam/core/libs/dimg/dimg_transform.cpp:119 > #1 0x778b4997 in Digikam::DImg::rotateAndFlip > (this=this@entry=0x256ef48, orientation=) at > /tmp/tmp.PyUwvaBSNi/digikam/core/libs/dimg/dimg_transform.cpp:450 > #2 0x778b4b8e in Digikam::DImg::exifRotate > (this=this@entry=0x256ef48, filePath=...) at > /tmp/tmp.PyUwvaBSNi/digikam/core/libs/dimg/dimg_transform.cpp:562 > #3 0x77967c74 in Digikam::PreviewLoadingTask::execute > (this=0x256ed60) at > /tmp/tmp.PyUwvaBSNi/digikam/core/libs/threadimageio/preview/previewtask.cpp:296 > #4 0x7797d84e in Digikam::LoadSaveThread::run (this=0x2525630) at > /tmp/tmp.PyUwvaBSNi/digikam/core/libs/threadimageio/fileio/loadsavethread.cpp:133 > #5 0x7799deae in Digikam::DynamicThread::Private::run > (this=0x2c4b4f0) at > /tmp/tmp.PyUwvaBSNi/digikam/core/libs/threads/dynamicthread.cpp:183 > #6 0x74b1b7d2 in ?? () from > /nix/store/683732s7dq6bxrl267lcadl5lvn6i4nh-qtbase-5.12.0/lib/libQt5Core.so.5 > #7 0x74b17062 in ?? () from > /nix/store/683732s7dq6bxrl267lcadl5lvn6i4nh-qtbase-5.12.0/lib/libQt5Core.so.5 > #8 0x744e2ef7 in start_thread () from > /nix/store/iykxb0bmfjmi7s53kfg6pjbfpd8jmza6-glibc-2.27/lib/libpthread.so.0 > #9 0x7441822f in clone () from > /nix/store/iykxb0bmfjmi7s53kfg6pjbfpd8jmza6-glibc-2.27/lib/libc.so.6 > (gdb) I don't think isolating a single image is going to work, since there is no failure that is deterministically triggered by a single image. Sometimes the scan succeeds without crash. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414484] Cannot use Rawtherapee or Darktable for raw image import on Windows
https://bugs.kde.org/show_bug.cgi?id=414484 --- Comment #19 from tlteebken-...@outlook.com --- Ok so I installed latest bits: no changes with regard to the issue. RT still works, DT will not even load. Next thing: the pictures that are round-tripped from RT are still rendering badly in Image Editor. They have artifacts or dark spots. This is true with roughly 3/4 of the images I tried. I've attached before and after pics, "before" is how it looks loaded in RT, "after" is returned to Image Editor. I circled in red the problem areas. This is just a representative example. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414484] Cannot use Rawtherapee or Darktable for raw image import on Windows
https://bugs.kde.org/show_bug.cgi?id=414484 --- Comment #18 from tlteebken-...@outlook.com --- Created attachment 124170 --> https://bugs.kde.org/attachment.cgi?id=124170=edit Image rendered in Image Editor after returning from RT No edits were made in RT -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414484] Cannot use Rawtherapee or Darktable for raw image import on Windows
https://bugs.kde.org/show_bug.cgi?id=414484 --- Comment #17 from tlteebken-...@outlook.com --- Created attachment 124169 --> https://bugs.kde.org/attachment.cgi?id=124169=edit Image rendered in RT after loading from Digikam -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413949] Docker Disappeared - Small Color Selector
https://bugs.kde.org/show_bug.cgi?id=413949 --- Comment #7 from keyth_qcfx2 --- But I already placed the attachments requested already. did I do something wrong on posting them? or they are not what was asked? -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 414633] New: [Wayland] cannot increase the volume level scrolling on the slider with a touchpad
https://bugs.kde.org/show_bug.cgi?id=414633 Bug ID: 414633 Summary: [Wayland] cannot increase the volume level scrolling on the slider with a touchpad Product: elisa Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: bugsefor...@gmx.com Target Milestone: --- SUMMARY I can't increase the volume level scrolling on the volume slider with a touchpad on Wayland. The volume decreases instead of increasing Such problem does not occur when I scroll using a mouse wheel on Wayland nor when I use the touchpad on X11. EXPECTED RESULT we can increase the volume level on Wayland scrolling on the slider with a touchpad. SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.17.80 KDE Frameworks Version: 5.65.0 Qt Version: 5.13.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414632] New: crash when I move a widget on desktop after changing plasma layout
https://bugs.kde.org/show_bug.cgi?id=414632 Bug ID: 414632 Summary: crash when I move a widget on desktop after changing plasma layout Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: 1.0 STEPS TO REPRODUCE 1. start Wayland session 2. add weather report widget to your desktop 3. right click on wallpaper, select "Configure desktop..." 4. change plasma layout setting and click on "Ok" button 5. do not minimize/close "Configure desktop..." window, drag and drop the weather report widget on your desktop. If plasma does not crash, drag and drop the widget a few times again. At some point probably plasma will crash. EXPECTED RESULT no crash SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.17.80 KDE Frameworks Version: 5.65.0 Qt Version: 5.13.2 Thread 21 (Thread 0x7fb9c127b700 (LWP 29182)): #0 0x7fba186609f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55f3d51d2374) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fba186609f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55f3d51d2320, cond=0x55f3d51d2348) at pthread_cond_wait.c:502 #2 0x7fba186609f3 in __pthread_cond_wait (cond=0x55f3d51d2348, mutex=0x55f3d51d2320) at pthread_cond_wait.c:655 #3 0x7fba1b730aeb in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x55f3d51d2320) at thread/qwaitcondition_unix.cpp:146 #4 0x7fba1b730aeb in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x55f3d51d4ce0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7fba1b730df9 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x55f3d51d4ce8, mutex=mutex@entry=0x55f3d51d4ce0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #6 0x7fba1f759ec8 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x55f3d51d4cd8) at scenegraph/qsgthreadedrenderloop.cpp:245 #7 0x7fba1f759ec8 in QSGRenderThread::processEventsAndWaitForMore() (this=this@entry= 0x55f3d51d4c60) at scenegraph/qsgthreadedrenderloop.cpp:710 #8 0x7fba1f75a2fa in QSGRenderThread::run() (this=0x55f3d51d4c60) at scenegraph/qsgthreadedrenderloop.cpp:739 #9 0x7fba1b729b52 in QThreadPrivate::start(void*) (arg=0x55f3d51d4c60) at thread/qthread_unix.cpp:360 #10 0x7fba1865a6db in start_thread (arg=0x7fb9c127b700) at pthread_create.c:463 #11 0x7fba1b02688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7fb99dd01700 (LWP 29180)): #0 0x7fba1b019bf9 in __GI___poll (fds=0x7fb990004230, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fba14f545c9 in g_main_context_poll (priority=, n_fds=1, fds=0x7fb990004230, timeout=, context=0x7fb99bf0) at ../../../../glib/gmain.c:4203 #2 0x7fba14f545c9 in g_main_context_iterate (context=context@entry=0x7fb99bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../../glib/gmain.c:3897 #3 0x7fba14f546dc in g_main_context_iteration (context=0x7fb99bf0, may_block=may_block@entry=1) at ../../../../glib/gmain.c:3963 #4 0x7fba1b96cb7f in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fb99b20, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #5 0x7fba1b90d06a in QEventLoop::exec(QFlags) (this=this@entry=0x7fb99dd00d80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7fba1b7283aa in QThread::exec() (this=this@entry=0x55f3d5028a00) at thread/qthread.cpp:531 #7 0x7fba1f201815 in QQmlThreadPrivate::run() (this=0x55f3d5028a00) at qml/ftw/qqmlthread.cpp:152 #8 0x7fba1b729b52 in QThreadPrivate::start(void*) (arg=0x55f3d5028a00) at thread/qthread_unix.cpp:360 #9 0x7fba1865a6db in start_thread (arg=0x7fb99dd01700) at pthread_create.c:463 #10 0x7fba1b02688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7fb9c1cff700 (LWP 29165)): #0 0x7fba186609f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55f3cadac9a0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fba186609f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55f3cadac950, cond=0x55f3cadac978) at pthread_cond_wait.c:502 #2 0x7fba186609f3 in __pthread_cond_wait (cond=0x55f3cadac978, mutex=0x55f3cadac950) at pthread_cond_wait.c:655 #3 0x7fba1b730aeb in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x55f3cadac950) at thread/qwaitcondition_unix.cpp:146 #4 0x7fba1b730aeb in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x55f3c3b89740, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7fba1b730df9 in
[lattedock] [Bug 414620] Dock raises up on each focus of a modal window/menu
https://bugs.kde.org/show_bug.cgi?id=414620 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #3 from Michail Vourlakos --- 1. For KCalc of course and it should go up. If you don't want to go up choose Dodge All Windows and NOT Dodge Active 2. For Application Launcher same thing applies with 1 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 414631] gwenview crashes with output "Floating point exception (core dumped)"
https://bugs.kde.org/show_bug.cgi?id=414631 Julian changed: What|Removed |Added CC||ju-0...@gmx.ch -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 414631] New: gwenview crashes with output "Floating point exception (core dumped)"
https://bugs.kde.org/show_bug.cgi?id=414631 Bug ID: 414631 Summary: gwenview crashes with output "Floating point exception (core dumped)" Product: gwenview Version: 19.08.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: ju-0...@gmx.ch Target Milestone: --- Created attachment 124168 --> https://bugs.kde.org/attachment.cgi?id=124168=edit image file with exif data leading to gwenview crash gwenview crashes with output "Floating point exception (core dumped)" The picture was exported from darktable. The problem must be related to the EXIF data embedded into the picture, as it does not crash if the exact same image is exported without EXIF infomration. STEPS TO REPRODUCE 1. open attached image in gwenview (better in terminal to see stdout): $ gwenview DSC00174_03.jpg 2. I have the Thumbnail Bar activated. The issue might be related to thumbnail loading... OBSERVED RESULT gwenview crashes with message "Floating point exception (core dumped)" printed to stdout. EXPECTED RESULT no crash SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2 Kernel Version: 4.19.85-1-MANJARO OS Type: 64-bit Processors: 4 × Intel® Core™ i7-7600U CPU @ 2.80GHz Memory: 19.5 GiB of RAM Many thanks for looking into this issue. Please let me know, if darktable is exporting a problematic / invalid EXIF tag which is causing the problem. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 414620] Dock raises up on each focus of a modal window/menu
https://bugs.kde.org/show_bug.cgi?id=414620 --- Comment #2 from Jazz --- I opened Kate editor. Latte Dock disappears, which is ok. Then I open Kcalc and place a focus on it, the Latte Dock goes up, which should NOT happen: https://i.imgur.com/bo4MIUW.png Then I just move my mouse and place a focus on Kate, the Latte Dock goes down again: https://i.imgur.com/7qobspC.png I close the KCalc window and click at the Application Launch widget, the Latte Dock goes up, which I believe is NOT what it should do: https://i.imgur.com/SgOLZXc.png For "Save as" dialogue windows the Latte Dock does not appear, which is ok: https://i.imgur.com/zC4yGnQ.png -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413223] Plasma Wayland session crashes immediately after login
https://bugs.kde.org/show_bug.cgi?id=413223 marco martinez changed: What|Removed |Added CC||mak...@gmail.com --- Comment #4 from marco martinez --- Created attachment 124167 --> https://bugs.kde.org/attachment.cgi?id=124167=edit wayland-session.log -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399234] Compositing breaks system tray functionality in programs running under Wine Staging
https://bugs.kde.org/show_bug.cgi?id=399234 Philipp Maierhöfer changed: What|Removed |Added CC|maiphi.pub...@gmx.net | -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 414624] FileSystem::sectorsUsed(): partitionmanager killed by SIGSEGV
https://bugs.kde.org/show_bug.cgi?id=414624 --- Comment #1 from Andrius Štikonas --- Unfortunately, I don't really know what causes craash in sectorsUsed. I have seen them myself from time to time and I had some bug reports but I was never able to reproduce them, they were just random crashes. And I can't see in the source what's wrong with sectorsUsed, there are already checks for non nullptr pointer... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399234] Compositing breaks system tray functionality in programs running under Wine Staging
https://bugs.kde.org/show_bug.cgi?id=399234 Eliphas changed: What|Removed |Added CC||k...@euodeio.net --- Comment #27 from Eliphas --- Hi, I came here because I have the same problem but maybe not same versions as the bug. As your last request for feedback has 20+ days, Maybe some feedback from my system can help you. KDE neon Testing Edition 18.04 fully updated wine-development 3.6-1 eliphas@T410:~$ QT_LOGGING_RULES="*kde*=true" xembedsniproxy kde.xembedsniproxy: starting kde.xembedsniproxy: Manager selection claimed org.kde.kwindowsystem: Loaded plugin "/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/org.kde.kwindowsystem.platforms/KF5WindowSystemX11Plugin.so" for platform "xcb" XXX Starting wine tflash.exe with compositing enabled, icon is round blue with an "F" kde.xembedsniproxy: trying to dock window 65011722 kde.xembedsniproxy: adding damage watch for 65011722 kde.xembedsniproxy: Received click 1 with passed x*y 1158 1582 kde.xembedsniproxy: Click point: QPoint(4,4) kde.xembedsniproxy: Received click 3 with passed x*y 1158 1582 kde.xembedsniproxy: Click point: QPoint(4,4) kde.xembedsniproxy: trying to undock window 65011722 XXX Ended wine with ^C, start again with compositing disabled, icon is only a square kde.xembedsniproxy: trying to dock window 65011720 kde.xembedsniproxy: adding damage watch for 65011720 kde.xembedsniproxy: Received click 1 with passed x*y 1156 1583 kde.xembedsniproxy: Received click 3 with passed x*y 1156 1583 kde.xembedsniproxy: Resizing window 65011720 "" from w*h QSize(-1, -1) kde.xembedsniproxy: Skip NULL image returned from xcb_image_get() for 65011720 "" kde.xembedsniproxy: No xembed icon for 65011720 "" kde.xembedsniproxy: trying to undock window 65011720 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 730, resource id: 65011720, major code: 25 (SendEvent), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 731, resource id: 65011720, major code: 12 (ConfigureWindow), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 152 (Unknown), sequence: 741, resource id: 33554441, major code: 143 (Unknown), minor code: 3 XXX Ended with right click context menu and exit -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414484] Cannot use Rawtherapee or Darktable for raw image import on Windows
https://bugs.kde.org/show_bug.cgi?id=414484 --- Comment #16 from Maik Qualmann --- Git commit 45d9a2fec09dcbad546ecd5d371b65be73931377 by Maik Qualmann. Committed on 28/11/2019 at 19:10. Pushed by mqualmann into branch 'master'. try reading the Windows registry to get paths M +8-1core/dplugins/rawimport/darktable/rawimportdarktableplugin.cpp M +8-4 core/dplugins/rawimport/rawtherapee/rawimportrawtherapeeplugin.cpp https://invent.kde.org/kde/digikam/commit/45d9a2fec09dcbad546ecd5d371b65be73931377 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 257566] Wobbly Windows effect with bi/trilinear filtering make windows' decorations flicker
https://bugs.kde.org/show_bug.cgi?id=257566 Vlad Zahorodnii changed: What|Removed |Added Assignee|kwin-bugs-n...@kde.org |vladz...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360549] Visible 1px space between window content and title bar when zooming
https://bugs.kde.org/show_bug.cgi?id=360549 Vlad Zahorodnii changed: What|Removed |Added Assignee|kwin-bugs-n...@kde.org |vladz...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 414593] Huge memory usage with some PDFs
https://bugs.kde.org/show_bug.cgi?id=414593 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #1 from Albert Astals Cid --- Okular will us as much memory as possible when set to Greedy, you can't complain it's doing that -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414603] pictures sort by freehand - drag & drop
https://bugs.kde.org/show_bug.cgi?id=414603 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||7.0.0 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 414620] Dock raises up on each focus of a modal window/menu
https://bugs.kde.org/show_bug.cgi?id=414620 --- Comment #1 from Michail Vourlakos --- I suppose you are referring to Dodge Active visibility... right? modal windows are those that are children windows, meaning in Libreoffice writer you open a Save dialog... KCalc is not a modal window and for application launcher I have no idea what you are referring as faulty behavior.. For each one case set full details how to reproduce in order for me to check out also if this is a bug or not... The libreoffice case works just fine... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414572] video stutter in fullscreen mode / slideshow
https://bugs.kde.org/show_bug.cgi?id=414572 --- Comment #3 from Maik Qualmann --- Git commit 40f4745254025487b8f2ee98f7dd2786b6e82791 by Maik Qualmann. Committed on 28/11/2019 at 18:17. Pushed by mqualmann into branch 'master'. cache the DInfoMap M +11 -8core/utilities/slideshow/slideproperties.cpp https://invent.kde.org/kde/digikam/commit/40f4745254025487b8f2ee98f7dd2786b6e82791 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 386384] installer quickly appears before plasma splash screen
https://bugs.kde.org/show_bug.cgi?id=386384 Patrick Silva changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #3 from Patrick Silva --- cannot reproduce with neon-user-20191128-1117.iso -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414629] New: SIGABRT if I open and close applets in systray after changing layout setting of plasma
https://bugs.kde.org/show_bug.cgi?id=414629 Bug ID: 414629 Summary: SIGABRT if I open and close applets in systray after changing layout setting of plasma Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: 1.0 STEPS TO REPRODUCE 1. start Wayland session 2. right click on wallpaper, select "Configure desktop..." 3. select another layout setting and click on "Ok" button 4. open and close the applets in systray and the calendar a few times OBSERVED RESULT at some point plasma crashes (and it's not restarted automatically) EXPECTED RESULT no crash SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.17.80 KDE Frameworks Version: 5.65.0 Qt Version: 5.13.2 Thread 20 (Thread 0x7fae40a70700 (LWP 18889)): #0 0x7faebca529f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x557912c35dc0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7faebca529f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x557912c35d70, cond=0x557912c35d98) at pthread_cond_wait.c:502 #2 0x7faebca529f3 in __pthread_cond_wait (cond=0x557912c35d98, mutex=0x557912c35d70) at pthread_cond_wait.c:655 #3 0x7faebfb22aeb in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x557912c35d70) at thread/qwaitcondition_unix.cpp:146 #4 0x7faebfb22aeb in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x55790f6fb020, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7faebfb22df9 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x55790f6fb028, mutex=mutex@entry=0x55790f6fb020, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #6 0x7faec3b4bec8 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x55790f6fb018) at scenegraph/qsgthreadedrenderloop.cpp:245 #7 0x7faec3b4bec8 in QSGRenderThread::processEventsAndWaitForMore() (this=this@entry= 0x55790f6fafa0) at scenegraph/qsgthreadedrenderloop.cpp:710 #8 0x7faec3b4c2fa in QSGRenderThread::run() (this=0x55790f6fafa0) at scenegraph/qsgthreadedrenderloop.cpp:739 #9 0x7faebfb1bb52 in QThreadPrivate::start(void*) (arg=0x55790f6fafa0) at thread/qthread_unix.cpp:360 #10 0x7faebca4c6db in start_thread (arg=0x7fae40a70700) at pthread_create.c:463 #11 0x7faebf41888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7fae41282700 (LWP 18858)): #0 0x7faebca529f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x557912c014a0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7faebca529f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x557912c01450, cond=0x557912c01478) at pthread_cond_wait.c:502 #2 0x7faebca529f3 in __pthread_cond_wait (cond=0x557912c01478, mutex=0x557912c01450) at pthread_cond_wait.c:655 #3 0x7faebfb22aeb in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x557912c01450) at thread/qwaitcondition_unix.cpp:146 #4 0x7faebfb22aeb in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x557912c64550, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7faebfb22df9 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x557912c64558, mutex=mutex@entry=0x557912c64550, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #6 0x7faec3b4bec8 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x557912c64548) at scenegraph/qsgthreadedrenderloop.cpp:245 #7 0x7faec3b4bec8 in QSGRenderThread::processEventsAndWaitForMore() (this=this@entry=0x557912c644d0) at scenegraph/qsgthreadedrenderloop.cpp:710 #8 0x7faec3b4c2fa in QSGRenderThread::run() (this=0x557912c644d0) at scenegraph/qsgthreadedrenderloop.cpp:739 #9 0x7faebfb1bb52 in QThreadPrivate::start(void*) (arg=0x557912c644d0) at thread/qthread_unix.cpp:360 #10 0x7faebca4c6db in start_thread (arg=0x7fae41282700) at pthread_create.c:463 #11 0x7faebf41888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7fae4332b700 (LWP 18793)): #0 0x7faebca529f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x557912d6ffb4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7faebca529f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x557912d6ff60, cond=0x557912d6ff88) at pthread_cond_wait.c:502 #2 0x7faebca529f3 in __pthread_cond_wait (cond=0x557912d6ff88, mutex=0x557912d6ff60) at pthread_cond_wait.c:655 #3 0x7faebfb22aeb in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x557912d6ff60) at thread/qwaitcondition_unix.cpp:146 #4 0x7faebfb22aeb in
[plasmashell] [Bug 399234] Compositing breaks system tray functionality in programs running under Wine Staging
https://bugs.kde.org/show_bug.cgi?id=399234 Konrad Materka changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REOPENED|NEEDSINFO --- Comment #26 from Konrad Materka --- Coty Ternes, can you provide answers to the questions from the comment above? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 414628] Add support for UTF8 Emoji characters in kate
https://bugs.kde.org/show_bug.cgi?id=414628 Kåre Särs changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||kare.s...@iki.fi Status|REPORTED|NEEDSINFO --- Comment #1 from Kåre Särs --- Have you also selected the Noto font in Kate? I'm using the Hack font in NEON (ubuntu 18.04 + latest KDE packages) and I can see the emoji... -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 414628] New: Add support for UTF8 Emoji characters in kate
https://bugs.kde.org/show_bug.cgi?id=414628 Bug ID: 414628 Summary: Add support for UTF8 Emoji characters in kate Product: kate Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: martin7...@gmail.com Target Milestone: --- Goal: Display Emoji UTF8 characters such as 鱗 in kate STEPS TO REPRODUCE 1. Install font for Emoji characters (Noto on my machine, from package fonts-noto-color-emoji) 2. Open a text file with Emoji UTF8 characters OBSERVED RESULT The characters are not displayed, there is a blank square instead. NOTES: The emojis are well displayed in the console (terminator) and in other editors (gedit). SOFTWARE/OS VERSIONS Linux Debian SID Kate: 4:19.08.2-1 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 414627] interface details
https://bugs.kde.org/show_bug.cgi?id=414627 --- Comment #1 from Anton --- Created attachment 124166 --> https://bugs.kde.org/attachment.cgi?id=124166=edit interface details Picture here -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 414627] New: interface details
https://bugs.kde.org/show_bug.cgi?id=414627 Bug ID: 414627 Summary: interface details Product: kdenlive Version: 19.08.3 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: agvozdez...@yandex.ru Target Milestone: --- SUMMARY See the picture STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 414624] FileSystem::sectorsUsed(): partitionmanager killed by SIGSEGV
https://bugs.kde.org/show_bug.cgi?id=414624 Diogo Gomes changed: What|Removed |Added CC||k...@diogogomes.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 414626] New: kwin_wayland on DisplayLink/udl turns screen off, and back on every frame
https://bugs.kde.org/show_bug.cgi?id=414626 Bug ID: 414626 Summary: kwin_wayland on DisplayLink/udl turns screen off, and back on every frame Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bluescreenaven...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE Need a Displaylink 2 device, (one that uses the UDL device start kwin_wayland on the displaylink device. I usually move the main integrated card0 into another seat, so that the DisplayLink card is the only dri device in seat0 start a simple application that doesn't change often, like xterm, or konsole. Press a key, or move the mouse. Observe the screen switch off, then back on OBSERVED RESULT Nothing interesting appears in the stdio/stderr log. I'm not sure the correct QT_LOGGING* variables to export... EXPECTED RESULT Weston runs on UDL, (the GL render works with a mesa patch workaround), but it runs with the --use-pixman flag, so I'd expect it to run like Weston. It needs a newer kernel (from past some 5.something version that I forget.) Nothing worked at ALL before on UDL SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 5.3.0 (Debian Buster (with the kernel from Debian Bullseye) KDE Plasma Version: Master KDE Frameworks Version: Master Qt Version: 5.14 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414625] New: Layer - Transform - Offset can't enter a value greater than 13887.50
https://bugs.kde.org/show_bug.cgi?id=414625 Bug ID: 414625 Summary: Layer - Transform - Offset can't enter a value greater than 13887.50 Product: krita Version: 4.2.8 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Transform Assignee: krita-bugs-n...@kde.org Reporter: dan.mclaugh...@gmail.com Target Milestone: --- Created attachment 124165 --> https://bugs.kde.org/attachment.cgi?id=124165=edit Simple project file showing the issue, try to move the selected layer over by 16384 pixels (or other large values) SUMMARY Layer - Transform - Offset can't enter a value greater than 13887.50. I have a large 4k file, first when the offset dialog comes up it keeps defaulting to 13887.50 for y and 2048 for x, instead of my previous used values which would be easier. Second when I try to change the y value to say 16384 it just pops back to the 13887.50 value, and there appears to be no way to offset a layer greater than that. STEPS TO REPRODUCE 1. Load attached file 2. In that layer select Layer - Transform - Offset 3. Try to enter 16384 and tab/click outside OBSERVED RESULT The value switches back EXPECTED RESULT My value SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 19.04 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401479] Feature request: add animations that follow the fingers when performing touchpad gestures
https://bugs.kde.org/show_bug.cgi?id=401479 Milos changed: What|Removed |Added CC||milos.braje...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 414624] New: FileSystem::sectorsUsed(): partitionmanager killed by SIGSEGV
https://bugs.kde.org/show_bug.cgi?id=414624 Bug ID: 414624 Summary: FileSystem::sectorsUsed(): partitionmanager killed by SIGSEGV Product: partitionmanager Version: 4.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: mattia.ve...@tiscali.it Target Milestone: --- A Fedora user reported a crash while creating a LUKS ext4 partition. Version-Release number of selected component: kde-partitionmanager-4.0.0-2.fc31 Additional info: reporter: libreport-2.11.3 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user@1000.service/gnome-shell-wayland.service cmdline:partitionmanager crash_function: FileSystem::sectorsUsed executable: /usr/bin/partitionmanager journald_cursor: s=72b73fcd08f54901b8af8bfd9f1cc603;i=7acbd;b=be349b3e97fb464aaf595be88aaeb259;m=5955cd21;t=5985c3d576f8a;x=f6d3484cfa751398 kernel: 5.3.12-300.fc31.x86_64 rootdir:/ runlevel: N 5 type: CCpp uid:1000 Truncated backtrace: Thread no. 1 (10 frames) #0 FileSystem::sectorsUsed at /usr/include/c++/9/bits/unique_ptr.h:352 #1 Partition::sectorsUsed at /usr/src/debug/kpmcore-4.0.1-1.fc31.x86_64/src/core/partition.h:187 #2 Partition::used at /usr/src/debug/kpmcore-4.0.1-1.fc31.x86_64/src/core/partition.h:154 #3 PartWidget::paintEvent at /usr/src/debug/kpmcore-4.0.1-1.fc31.x86_64/src/gui/partwidget.cpp:96 #4 QWidget::event at kernel/qwidget.cpp:8965 #5 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:3700 #6 QApplication::notify(QObject*, QEvent*) at kernel/qapplication.cpp:3446 #7 QCoreApplication::notifyInternal2 at kernel/qcoreapplication.cpp:1088 #8 QWidgetPrivate::sendPaintEvent at kernel/qwidget.cpp:5701 #9 QWidgetPrivate::drawWidget at kernel/qwidget.cpp:5641 The full backtrace is available at https://bugzilla.redhat.com/show_bug.cgi?id=1777607 -- You are receiving this mail because: You are watching all bug changes.
