[kstars] [Bug 404868] Scheduler delays subsequent jobs when hitting a restriction violation
https://bugs.kde.org/show_bug.cgi?id=404868 TallFurryMan changed: What|Removed |Added Assignee|mutla...@ikarustech.com |eric.dejouha...@gmail.com --- Comment #1 from TallFurryMan --- Will take over this one. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 404868] New: Scheduler delays subsequent jobs when hitting a restriction violation
https://bugs.kde.org/show_bug.cgi?id=404868 Bug ID: 404868 Summary: Scheduler delays subsequent jobs when hitting a restriction violation Product: kstars Version: 3.0.1 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: eric.dejouha...@gmail.com Target Milestone: --- SUMMARY Scheduler properly reschedules a job that crossed its altitude limit to the next acceptable startup time and waits for its rescheduled startup time. However, this prevents further jobs in the list from executing at that moment: following the ordering rule, they are rescheduled after the restricted job. This can be worked around by automatically reordering jobs each time the list is evaluated, but that feature is often disregarded because it doesn't (yet) address obstructed horizon. STEPS TO REPRODUCE 1. Schedule two asap jobs, first of which has an altitude restriction, second of which has none (warning: there is a minimal altitude limit hard-coded whatever the value of the restriction box). 2. Execute the plan so that while running, the first job violates the altitude restriction, but not the second job. 3. Observe behavior OBSERVED RESULT First job is aborted, and rescheduled hours later when the altitude restriction can be complied with. Second job is shifted to start after first job, often on the next night and doesn't execute right now although no restriction would prevent that. If happening on the beginning of the night, this wastes the whole night. EXPECTED RESULT The behavior is compliant with the algorithm. However, it would seem more natural that the violating job is aborted, and the next is processed. SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: Ubuntu 18.04 - KStars 2019-02-21T21:29:33Z built from git state ~3h before that time. (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION This is not a bug, this is how the algorithm was designed. Changing the behavior to address this issue would be an improvement. First, if currently running, Scheduler could avoid updating the current schedule of subsequent jobs after such violation, unless there are no jobs left to run. Scheduler would then continue with the next job that is ready to run. What is the job that is ready to run? Restriction violations are detected while scheduling and marked with a warning icon in the list, so the end-user is aware of possible issues in that case. Violations may also appear because of a runtime delay (customizing how long accessory steps take is not implemented as of now). Well, in order to manage those two situations, when running, Scheduler should decide to abort subsequent jobs that are too late based on their startup time (this is already in the code), without changing the schedule (this is not). To relax the situation (but this is a further improvement, not needed right now) and avoid delaying the whole schedule too much, Scheduler could abort jobs which have less than 50% of their duration remaining based on their startup time. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 404867] New: System settings crash on launch feedback page
https://bugs.kde.org/show_bug.cgi?id=404867 Bug ID: 404867 Summary: System settings crash on launch feedback page Product: systemsettings Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: kcm_launch Assignee: unassigned-b...@kde.org Reporter: sunxuanmail...@163.com Target Milestone: --- SUMMARY System settings crash on launch feedback page everytime. STEPS TO REPRODUCE 1. Open system settings 2. Go to Applications->Launch Feedback 3. OBSERVED RESULT The window title flashed between "Launch Feedback*-System settings" and "Launch Feedback-System settings" even when doing nothing, a few seconds later it crashed. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: Kubuntu 18.10 (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.
[krita] [Bug 404852] Crash upon saving due something with the mirror config. [gdb backtrace]
https://bugs.kde.org/show_bug.cgi?id=404852 --- Comment #2 from wolthera --- No, it seems random. Regardless, can we not deduce from the situation what might be causing it? -- You are receiving this mail because: You are watching all bug changes.
[libalkimia] [Bug 404202] library alkimia does not load translations
https://bugs.kde.org/show_bug.cgi?id=404202 Ralf Habacker changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||8.0.1 Resolution|--- |FIXED --- Comment #4 from Ralf Habacker --- Issue has been fixed in 8.0 and master branch. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 388729] Timeline refactoring - Duplicate clip with speed change not doing slowmotion
https://bugs.kde.org/show_bug.cgi?id=388729 Evert Vorster changed: What|Removed |Added Version|17.12.0 |unspecified Summary|17.12 - Duplicate clip with |Timeline refactoring - |speed change not doing |Duplicate clip with speed |slowmotion |change not doing slowmotion --- Comment #4 from Evert Vorster --- Hi there. I tested again with the timeline refactoring branch, and there it is back to it's old behavior. This means clips play at 100% speed when percentages lower than 100 is applied, with the extra frames just padded with the last frame. When applying percentages larger than 100%, the clip job works properly. I have changed the version of kdenlive for this bug, as it is obviously fixed in the stable branches. Hopefully it rings a bell with our developers as to how it was fixed last time. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 369562] Wrong highlight on MustacheJS template engine.
https://bugs.kde.org/show_bug.cgi?id=369562 Nibaldo G. changed: What|Removed |Added CC||nibg...@gmail.com Version Fixed In||5.56.0 --- Comment #2 from Nibaldo G. --- I corrected the Mustache highlighter. Also, the support to template files is added, commonly with *.mustache extension (in the menu: Markup -> Mustache/Handlebars (HTML)). Patch: https://phabricator.kde.org/D19328 -- You are receiving this mail because: You are watching all bug changes.
[user-manager] [Bug 404866] New: Users gone in User Manager
https://bugs.kde.org/show_bug.cgi?id=404866 Bug ID: 404866 Summary: Users gone in User Manager Product: user-manager Version: 5.14.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcontrol module Assignee: j...@jriddell.org Reporter: f4tm...@web.de Target Milestone: --- Created attachment 118397 --> https://bugs.kde.org/attachment.cgi?id=118397=edit Screenshot User Manager After having troubles with an update (Solus Plasma) I was forced to set up a new user. Now I got two accounts but neither is showing any users in User Manager. Maybe because they got the same name?! User1: user name: carl name: Michael Carl User2: user name: mcarl name: Michael Carl STEPS TO REPRODUCE 1. open user manager 2. add second user 3. OBSERVED RESULT Both accounts don't show any users in the User Manager EXPECTED RESULT Each account should show 2 users. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Solus 3. (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404684] Notifications only with text at the top left of the screen
https://bugs.kde.org/show_bug.cgi?id=404684 --- Comment #11 from Thomas --- I found out that I can solve the problem when I modify the yakuake autostart with Exec=sh -c 'sleep 3; yakuake' The question remains: why latte can't register the notifications service? Hint: yakuake shows a notification on start. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404852] Crash upon saving due something with the mirror config. [gdb backtrace]
https://bugs.kde.org/show_bug.cgi?id=404852 Anna Medonosova changed: What|Removed |Added CC||anna.medonos...@gmail.com --- Comment #1 from Anna Medonosova --- I am sorry, I cannot reproduce it. Are there specific steps to trigger the crash? Can you provide the file that causes it? Do you have a core file? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 147094] The "--geometry" option does not work for Konsole
https://bugs.kde.org/show_bug.cgi?id=147094 --- Comment #23 from George R. Goffe --- Hi, I think I reported this "kind" of bug some time ago... I'm currently using konsole5-18.12.2-1.fc30.x86_64... a Fedora 30 (rawhide) system. It appears to work from the command line of another konsole instance. I thank Mr. Wu for pointing out that the unit of measure is PIXELS and not the "normal" X11 way of specifying geometry. Why would someone choose to implement geometry is beyond me. Sorry. konsole -geometry 01210x610+011+011 produced a knosole near the top left side of the desktop (kde that is). Does the above mean that geometry is supported? George... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387313] Subsurfaces are not clipped
https://bugs.kde.org/show_bug.cgi?id=387313 --- Comment #61 from Martin Flöser --- To add: scene was pretty much the first part of KWin adjusted for Wayland. This part was ported before sub surface protocol was added. Unfortunately sub surfaces change the assumption. Vlad: an idea for a quick hack: trigger fullscreen repaints whenever there's a subsurface involved. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404865] New: Plasma 5.15.0, 5.15.1, 5.15.2 Task Manager Sequence & Thumbnail bugs.
https://bugs.kde.org/show_bug.cgi?id=404865 Bug ID: 404865 Summary: Plasma 5.15.0, 5.15.1, 5.15.2 Task Manager Sequence & Thumbnail bugs. Product: plasmashell Version: 5.15.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: kdem...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Plasma 5.15.0, 5.15.1, 5.15.2 Task Manager Sequence & Thumbnail bugs: Popup thumbnails have lost their VD#, & for VD-1 to VD-n, any windows using VD-n show first not last in Task Manager sequence. STEPS TO REPRODUCE 1. Upgrade Plasma to at least 5.15.0. 2. Activate Plasma Panel's Task Manager [TM], configured to arrange in Desktop sequence, Ungrouped. 3. Activate at least two Virtual Desktops [VD]. The following example uses 9 VDs, & the malfunction is confirmed also with 4 VDs [so i expect probably any number will suffice]. 4. Open random program / document windows distributed across multiple VDs, except NOT the final VD [ie, use 1 - 8]. 5. Inspect the TM & note that all its iconised windows correctly appear in the expected sequence. 6. Open another window, but now in VD9 [or alternatively drag an existing one there]. Reinspect the TM. OBSERVED RESULT 1. VD9’s window/s appear NOT last in the TM, but incorrectly at the start [LHS-end if panel is horizontal] of the TM… ie, before even the genuinely VD1 windows. 2. TM no longer identifies the VD# in the popup thumbnails [this is unrelated to VD9 being occupied or not]. EXPECTED RESULT 1. VD9’s window/s should appear last in the TM sequence [which was true for Plasma <5.15.0]. 2. TM window popup thumbnail should continue indicating VD# [which was true for Plasma <5.15.0]. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.15.1 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.1 Kernel Version: 4.20.12-1-MANJARO OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4790 CPU @ 3.60GHz Memory: 30.8 GiB of RAM ADDITIONAL INFORMATION 1. See my thread in Manjaro forum https://forum.manjaro.org/t/plasma-5-15-x-task-manager-bug/77238?u=kdemeoz for more information & pictures. 2. These bugs were NOT present in 5.14.5. 3. These bugs [when Plasma >= 5.15.0] occur in [at least] Manjaro [all three branches], KaOS, & openSUSE Tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 400594] "Invalid protocol" when clicking on a tag
https://bugs.kde.org/show_bug.cgi?id=400594 --- Comment #4 from Jamie Smith --- The bug was referenced in the commit because the commit removed the ability to access the slave with an additional /, preventing manifestation of the reported undefined behaviour. The commit did not solve the undefined behaviour allowing to access the slave with an additional /, therefore the bug is not 'fixed'. The bug is 'not a bug', because of host handling expectations in dolphin, kio and elsewhere, accessing the slave with // causes undefined behaviour. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 147094] The "--geometry" option does not work for Konsole
https://bugs.kde.org/show_bug.cgi?id=147094 andydecle...@gmail.com changed: What|Removed |Added CC||andydecle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 386744] Arabic–Indic numerals not recognized as valid numbers
https://bugs.kde.org/show_bug.cgi?id=386744 --- 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 403663] colors are darker upon returning to the virtual desktop
https://bugs.kde.org/show_bug.cgi?id=403663 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 357860] Launcher is on white background when all other launchers are on black
https://bugs.kde.org/show_bug.cgi?id=357860 --- 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.
[dragonplayer] [Bug 381673] problems with changing to full-screen mode and returning back to normal mode.
https://bugs.kde.org/show_bug.cgi?id=381673 --- Comment #3 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.
[korganizer] [Bug 404679] Korganizer crashes on startup
https://bugs.kde.org/show_bug.cgi?id=404679 --- Comment #1 from Kishore Gopalakrishnan --- With debug symbols for qt5 -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7ba6b77200 (LWP 31206))] Thread 5 (Thread 0x7f7b9edee700 (LWP 31220)): #0 0x7f7bae84c7a4 in read () from /usr/lib/libc.so.6 #1 0x7f7baa409971 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f7baa45a0b0 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7f7baa45b4e6 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7f7baa45b62e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7f7baed9fd04 in QEventDispatcherGlib::processEvents (this=0x7f7b8c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f7baed48b2c in QEventLoop::exec (this=this@entry=0x7f7b9ededd60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7f7baeb8c569 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7f7baeb8d96c in QThreadPrivate::start (arg=0x558b3fc35710) at thread/qthread_unix.cpp:361 #9 0x7f7baca57a9d in start_thread () from /usr/lib/libpthread.so.0 #10 0x7f7bae85bb23 in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7f7b9f5ef700 (LWP 31213)): #0 0x7f7bae850c21 in poll () from /usr/lib/libc.so.6 #1 0x7f7baa45b540 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f7baa45b62e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f7baed9fd04 in QEventDispatcherGlib::processEvents (this=0x7f7b94000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f7baed48b2c in QEventLoop::exec (this=this@entry=0x7f7b9f5eed60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f7baeb8c569 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f7baeb8d96c in QThreadPrivate::start (arg=0x558b3fbb4d20) at thread/qthread_unix.cpp:361 #7 0x7f7baca57a9d in start_thread () from /usr/lib/libpthread.so.0 #8 0x7f7bae85bb23 in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7f7ba4995700 (LWP 31208)): #0 0x7f7bae84c7a4 in read () from /usr/lib/libc.so.6 #1 0x7f7baa409971 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f7baa45a0b0 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7f7baa45b4e6 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7f7baa45b62e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7f7baed9fd04 in QEventDispatcherGlib::processEvents (this=0x7f7b98000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f7baed48b2c in QEventLoop::exec (this=this@entry=0x7f7ba4994d30, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7f7baeb8c569 in QThread::exec (this=this@entry=0x7f7bae541080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7f7bae4c5ba6 in QDBusConnectionManager::run (this=0x7f7bae541080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #9 0x7f7baeb8d96c in QThreadPrivate::start (arg=0x7f7bae541080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361 #10 0x7f7baca57a9d in start_thread () from /usr/lib/libpthread.so.0 #11 0x7f7bae85bb23 in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f7ba5b5c700 (LWP 31207)): #0 0x7f7bae850c21 in poll () from /usr/lib/libc.so.6 #1 0x7f7baa3d0630 in ?? () from /usr/lib/libxcb.so.1 #2 0x7f7baa3d22db in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7f7ba6711949 in QXcbEventQueue::run (this=0x558b3fae4a60) at qxcbeventqueue.cpp:228 #4 0x7f7baeb8d96c in QThreadPrivate::start (arg=0x558b3fae4a60) at thread/qthread_unix.cpp:361 #5 0x7f7baca57a9d in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f7bae85bb23 in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f7ba6b77200 (LWP 31206)): [KCrash Handler] #6 std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x51) at /usr/include/c++/8.2.1/bits/atomic_base.h:390 #7 QAtomicOps::load (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:227 #8 QBasicAtomicInteger::load (this=0x51) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:103 #9 QtPrivate::RefCount::ref (this=0x51) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:55 #10 QString::QString (other=..., this=0x7fffd9d9ce90) at ../../include/QtCore/../../src/corelib/tools/qstring.h:958 #11 QTimeZonePrivate::Data::Data (this=0x7fffd9d9ce90) at tools/qtimezoneprivate_p.h:81 #12 QTzTimeZonePrivate::previousTransition (this=0x558b3fc4ad90, beforeMSecsSinceEpoch=2879) at
[dolphin] [Bug 404858] "Add Network Folder" tooltip icon does not show on Breeze, shows correctly on Breeze Dark
https://bugs.kde.org/show_bug.cgi?id=404858 Nate Graham changed: What|Removed |Added Assignee|visual-des...@kde.org |dolphin-bugs-n...@kde.org Component|Theme - Breeze |view-engine: tooltip Version|master |unspecified Product|plasmashell |dolphin CC||n...@kde.org Ever confirmed|0 |1 Target Milestone|1.0 |--- Status|REPORTED|CONFIRMED --- Comment #3 from Nate Graham --- The icon itself (folder-new) is fully capable of changing its color, so the problem here must be that Dolphin's tooltip isn't invoking that behavior properly. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 404821] Presentation offset from full screen when OpenGL transitions selected.
https://bugs.kde.org/show_bug.cgi?id=404821 --- Comment #4 from caulier.gil...@gmail.com --- I will start the build today morning Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 400594] "Invalid protocol" when clicking on a tag
https://bugs.kde.org/show_bug.cgi?id=400594 --- Comment #3 from Nate Graham --- If this is NOT A BUG, why did you use the `BUG:` keyword in https://cgit.kde.org/baloo.git/commit/?id=f4dd3f7bab790734b47a31c70fbb68297d4d3062? That keyword means "this commit fixes such-and-such bug." -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 404864] New: Strange behavior with default browser setting
https://bugs.kde.org/show_bug.cgi?id=404864
Bug ID: 404864
Summary: Strange behavior with default browser setting
Product: konqueror
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: konq-b...@kde.org
Reporter: andronon...@gmail.com
Target Milestone: ---
Created attachment 118396
--> https://bugs.kde.org/attachment.cgi?id=118396=edit
Infinite message boxes
I don't know if it's Konqueror bug or KIO KRun component bug, but it only
happens when Konqueror is installed.
STEPS TO REPRODUCE
1. Install Konqueror
2. Go to System settings -> Default Applications -> Web Browser
3. Set 'with the following command' and *intentionally* set the wrong one
('abcdef' for example)
4. Launch some link from Konsole (or from some app that calls external web
browser for links)
5. Get infinine 'Command not found' message boxes.
The main point here is that if the command can't be found, default one will be
lauched, which is Konqueror. If I delete Konqueror nothing like this happens. I
had Firefox, Chromium and Konqueror installed when this happened.
See attached video for example.
Plasma 5.15.1 / Frameworks 5.55.0
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 404572] Sorting by desktop not working
https://bugs.kde.org/show_bug.cgi?id=404572 --- Comment #7 from Eike Hein --- Please give the updated patch another try now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404861] Configure systemtray crashes plasma desktop and looks wonky
https://bugs.kde.org/show_bug.cgi?id=404861 --- Comment #3 from Texstar --- Yes. All settings are set to Breeze. On another older installation (updated) with the exact same settings does not crash the desktop and the settings look normal. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404861] Configure systemtray crashes plasma desktop and looks wonky
https://bugs.kde.org/show_bug.cgi?id=404861 --- Comment #2 from Texstar --- Created attachment 118395 --> https://bugs.kde.org/attachment.cgi?id=118395=edit normal looking settings on other KDE installation. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 404863] New: KMail should use UTF-8 as default encoding
https://bugs.kde.org/show_bug.cgi?id=404863 Bug ID: 404863 Summary: KMail should use UTF-8 as default encoding Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: aurelien.mur...@net-c.be Target Milestone: --- Unless you manually change the encoding settings, KMail will send messages using US-ASCII if possible, then ISO-8859-1 and will only use UTF-8 when using ISO-8859-1 is not possible. Since UTF-8 has been a de facto standard for years, the use of ISO-8859-1 sometimes causes a few problems. For example, I regularly send messages to a mailing list. The list server automatically adds a few lines of text at the bottom of my messages, using UTF-8 encoding. The result is that those added lines appear broken, because their encoding does not match the one of my messages, which is ISO-8859-1. I cannot see why it would be better to keep using ISO-8859-1 instead of UTF-8, so I think KMail should now default to UTF-8. This is what most other mail clients do. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 400594] "Invalid protocol" when clicking on a tag
https://bugs.kde.org/show_bug.cgi?id=400594 Jamie Smith changed: What|Removed |Added Resolution|FIXED |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404861] Configure systemtray crashes plasma desktop and looks wonky
https://bugs.kde.org/show_bug.cgi?id=404861 David Edmundson changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||k...@davidedmundson.co.uk Resolution|--- |WAITINGFORINFO --- Comment #1 from David Edmundson --- Does this happen with the default breeze theme? -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 403751] very slow filtering of bibliography
https://bugs.kde.org/show_bug.cgi?id=403751 Gandalf Lechner changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Gandalf Lechner --- that commit has fixed it for me, thanks! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 404862] New: Kate freezes on completion
https://bugs.kde.org/show_bug.cgi?id=404862 Bug ID: 404862 Summary: Kate freezes on completion Product: kate Version: 18.12.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: part Assignee: kwrite-bugs-n...@kde.org Reporter: rootki...@yahoo.it Target Milestone: --- SUMMARY Kate freezes after completing a keyword STEPS TO REPRODUCE 1. open the attached file 2. write "config" at the end of the file OBSERVED RESULT it freezes EXPECTED RESULT guess what? SOFTWARE/OS VERSIONS Linux kernel: 4.20.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 ADDITIONAL INFORMATION clicking "recover data" after a crash freezes it again -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404861] New: Configure systemtray crashes plasma desktop and looks wonky
https://bugs.kde.org/show_bug.cgi?id=404861 Bug ID: 404861 Summary: Configure systemtray crashes plasma desktop and looks wonky Product: plasmashell Version: 5.15.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: texs...@gmail.com Target Milestone: 1.0 Created attachment 118394 --> https://bugs.kde.org/attachment.cgi?id=118394=edit picture of wonky settings page SUMMARY Configure systemtray will randomly crash the plasma desktop. The settings page has large checkmarks all over the place. See attached photo STEPS TO REPRODUCE 1. Select to configure systemtray OBSERVED RESULT Plasma crash and wonky settings page. EXPECTED RESULT No crash and correct setting page. SOFTWARE/OS VERSIONS Linux/KDE Plasma: PCLinuxOS (available in About System) KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.55 Qt Version: 5.12.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 404833] KDE's platform file dialog embedding
https://bugs.kde.org/show_bug.cgi?id=404833
--- Comment #14 from RJVB ---
(In reply to RJVB from comment #13)
> fDialog->setProperty("QFileDialogInstance", variant);
Doh, that has to be
setProperty("QFileDialogInstance", variant);
of course. That property *is* accessible from the plugin. And then the other
property becomes pointless.
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 404549] Printing N copies results in N^2 copies printed instead
https://bugs.kde.org/show_bug.cgi?id=404549 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #8 from Albert Astals Cid --- Data asked was provided, back to reported -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 400594] "Invalid protocol" when clicking on a tag
https://bugs.kde.org/show_bug.cgi?id=400594 Nate Graham changed: What|Removed |Added Resolution|NOT A BUG |FIXED CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 404821] Presentation offset from full screen when OpenGL transitions selected.
https://bugs.kde.org/show_bug.cgi?id=404821 --- Comment #3 from Tim --- Thanks Gilles and Maik. The build from Gilles link (digiKam-6.1.0-git-20190224T141538-Win64.exe) still has the bug. Is there a build with Maik's fix for me to test? Tim. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 404859] Using Batch Queue Manager to make a JPG copy of the images on completion the "arw" images are no longer visible in the originating album
https://bugs.kde.org/show_bug.cgi?id=404859 --- Comment #3 from Steven Tyrer --- Hi Malk Thanks for your help in solving my problem pleased that it was not a bug, have been using digikam for a long time and it indispensable. Steven Steven's Photo's On Tuesday, 26 February 2019, 22:07:05 GMT, Maik Qualmann wrote: https://bugs.kde.org/show_bug.cgi?id=404859 Maik Qualmann changed: What |Removed |Added CC| |metzping...@gmail.com --- Comment #2 from Maik Qualmann --- You have activated versioning. If you do not want to hide the original image, activate the option "Show always original image" in digiKam Setup-> Image Editor-> Versioning. Maik -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 404805] Add support for major version related pot files
https://bugs.kde.org/show_bug.cgi?id=404805 Luigi Toscano changed: What|Removed |Added CC||luigi.tosc...@tiscali.it Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #3 from Luigi Toscano --- The branch specific code is handled inside each branch (branches/stable/l10n-kf5, trunk/l10n-kf5, branches/stable/l10n-kde4). Right now alkimia translations (which would be the only user of this) are extracted only into the kf5 branches. Even if alkimia can be compiled against both Qt4 and Qt5, the translations can be extracted only inside kf5 branch and shipped together in the tarball. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404860] Tablet pressure not working in hidpi
https://bugs.kde.org/show_bug.cgi?id=404860 --- Comment #5 from Davide Baldo --- screen #0: dimensions:3840x2160 pixels (391x220 millimeters) resolution:249x249 dots per inch depths (7):24, 1, 4, 8, 15, 16, 32 root window id:0x24e depth of root window:24 planes number of colormaps:minimum 1, maximum 1 default colormap:0xb0 default number of colormap cells:256 preallocated pixels:black 0, white 16777215 options:backing-store WHEN MAPPED, save-unders NO largest cursor:64x64 current input event mask:0xfa8031 KeyPressMask EnterWindowMask LeaveWindowMask ExposureMask StructureNotifyMask SubstructureNotifyMask SubstructureRedirectMask FocusChangeMask PropertyChangeMask ColormapChangeMask number of visuals:132 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404860] Tablet pressure not working in hidpi
https://bugs.kde.org/show_bug.cgi?id=404860 --- Comment #4 from Davide Baldo --- just to be as complete as possible name of display::0 version number:11.0 vendor string:The X.Org Foundation vendor release number:12003000 X.Org version: 1.20.3 maximum request size: 16777212 bytes motion buffer size: 256 bitmap unit, bit order, padding:32, LSBFirst, 32 image byte order:LSBFirst number of supported pixmap formats:7 supported pixmap formats: depth 1, bits_per_pixel 1, scanline_pad 32 depth 4, bits_per_pixel 8, scanline_pad 32 depth 8, bits_per_pixel 8, scanline_pad 32 depth 15, bits_per_pixel 16, scanline_pad 32 depth 16, bits_per_pixel 16, scanline_pad 32 depth 24, bits_per_pixel 32, scanline_pad 32 depth 32, bits_per_pixel 32, scanline_pad 32 keycode range:minimum 8, maximum 255 focus: window 0x287, revert to PointerRoot number of extensions:28 BIG-REQUESTS Composite DAMAGE DOUBLE-BUFFER DPMS DRI2 GLX Generic Event Extension MIT-SCREEN-SAVER MIT-SHM NV-CONTROL NV-GLX Present RANDR RECORD RENDER SHAPE SYNC X-Resource XC-MISC XFIXES XFree86-DGA XFree86-VidModeExtension XINERAMA XInputExtension XKEYBOARD XTEST XVideo default screen number:0 number of screens:1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404860] Tablet pressure not working in hidpi
https://bugs.kde.org/show_bug.cgi?id=404860 --- Comment #3 from Davide Baldo --- > * What happens if you use Krita's internal switch to enable hidpi (in the > settings dialog) instead of the old environment variables? QT_AUTO_SCREEN_SCALE_FACTOR="" QT_SCREEN_SCALE_FACTORS="" ./krita-4.2.0-pre-alpha-7d4289d-x86_64.appimage scales correctly but no pen pressure > * Does this also happen with the nightly build appimage? Yes, downloaded krita-4.2.0-pre-alpha-7d4289d-x86_64.appimage scales correctly but no pen pressure I also noticed that sometime the pen doesn't work anymore (at all, can't draw anything not only pressure) randomly, has something to do with focus and sometimes happens when i press tab, workaround is to move cursor outside krita and back inside. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 403751] very slow filtering of bibliography
https://bugs.kde.org/show_bug.cgi?id=403751 Thomas Fischer changed: What|Removed |Added Latest Commit||defbd6867137ca1669911601594 ||5e81fcad99b2c Status|CONFIRMED |ASSIGNED --- Comment #2 from Thomas Fischer --- Please check if the problem has been fixed in commit defbd6867137ca available here: https://commits.kde.org/clones/kbibtex/thomasfischer/kbibtex/defbd6867137ca16699116015945e81fcad99b2c To test the code, have a look at the "Quick Start" instructions: https://userbase.kde.org/KBibTeX/Development#Quick_Start_to_Run_KBibTeX_from_Git Run script run-kbibtex.sh as follows: bash run-kbibtex.sh "https://anongit.kde.org/clones/kbibtex/thomasfischer/kbibtex.git; "bugs/kde403751" Please test and confirm if that commit fixes your performance issues. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 404859] Using Batch Queue Manager to make a JPG copy of the images on completion the "arw" images are no longer visible in the originating album
https://bugs.kde.org/show_bug.cgi?id=404859 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- You have activated versioning. If you do not want to hide the original image, activate the option "Show always original image" in digiKam Setup-> Image Editor-> Versioning. Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404860] Tablet pressure not working in hidpi
https://bugs.kde.org/show_bug.cgi?id=404860 --- Comment #2 from Boudewijn Rempt --- * What happens if you use Krita's internal switch to enable hidpi (in the settings dialog) instead of the old environment variables? * Does this also happen with the nightly build appimage? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404860] Tablet pressure not working in hidpi
https://bugs.kde.org/show_bug.cgi?id=404860 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Severity|major |normal -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404860] Tablet pressure not working in hidpi
https://bugs.kde.org/show_bug.cgi?id=404860 --- Comment #1 from Davide Baldo --- my screen is a 15" 4k -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 403285] Pressing CTRL while scrolling, but not using the touchpad causes zoom
https://bugs.kde.org/show_bug.cgi?id=403285 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com --- Comment #3 from Thiago Sueto --- Can confirm that this occurs on Konsole. This also currently occurs on Firefox, Dolphin, WPSOffice and SoftmakerOffice, just some examples I tested. An easy way to reproduce this on Dolphin is navigating to /etc with maximum zoom and testing with scrolling downwards. Nate also once mentioned that this occurs due to an X11 synaptics driver issue here on this Okular bug report: https://bugs.kde.org/show_bug.cgi?id=353330#c1 Should I submit a bug report for Dolphin as well? To me it seems a bit redundant having the same bug report across several KDE applications (Okular, Kate, Konsole, Dolphin) that is seemingly caused by an upstream issue, but this would need at least a temporary fix on KDE applications until libinput is fully implemented, I think. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404860] New: Tablet pressure not working in hidpi
https://bugs.kde.org/show_bug.cgi?id=404860 Bug ID: 404860 Summary: Tablet pressure not working in hidpi Product: krita Version: 4.1.7 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: dav...@baldo.me Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. QT_AUTO_SCREEN_SCALE_FACTOR="" ~/Downloads/krita-4.1.7-x86_64.appimage 2. krita opens and it's sized correctly :) 3. draw with pressure sensitive brush: pressure is IGNORED 1. QT_AUTO_SCREEN_SCALE_FACTOR="0" ~/Downloads/krita-4.1.7-x86_64.appimage 2. krita opens and it's really small :( 3. draw with pressure sensitive brush: pressure is CORRECT with hidpi(QT_AUTO_SCREEN_SCALE_FACTOR="") sometime under unknown condition the pressure works. without hidpi(QT_AUTO_SCREEN_SCALE_FACTOR="0") krita pressure always work. This happens with both USB and BLUETOOTH wacom intous 2018 (top 4 buttons in a raw without eraser). This also happen with native krita (4.1.7-r1) SOFTWARE/OS VERSIONS Linux/KDE Plasma: gentoo/kernel 4.14.61 KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 960M/PCIe/SSE2 OpenGL core profile version string: 4.5.0 NVIDIA 415.27 OpenGL core profile shading language version string: 4.50 NVIDIA $ lsusb -v Bus 001 Device 009: ID 056a:0376 Wacom Co., Ltd Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x056a Wacom Co., Ltd idProduct 0x0376 bcdDevice1.07 iManufacturer 1 Wacom Co.,Ltd. iProduct2 Intuos BT S iSerial 3 XXX bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.10 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 759 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Device Status: 0x (Bus Powered) $ set | grep QT_ QT_AUTO_SCREEN_SCALE_FACTOR=0 QT_GRAPHICSSYSTEM=native QT_IM_MODULE=fcitx QT_SCREEN_SCALE_FACTORS='eDP-1=2.6;DP-1=2.6;HDMI-1=2.6;DP-2=2.6;' $ ldd /usr/bin/krita linux-vdso.so.1 (0x7ffefe773000) libkritaui.so.17 => /usr/lib64/libkritaui.so.17 (0x7f7127a2b000) libKF5Crash.so.5 => /usr/lib64/libKF5Crash.so.5 (0x7f7127823000) libkritawidgetutils.so.17 => /usr/lib64/libkritawidgetutils.so.17 (0x7f71274e) libkritaglobal.so.17 => /usr/lib64/libkritaglobal.so.17 (0x7f71272aa000) libKF5I18n.so.5 => /usr/lib64/libKF5I18n.so.5 (0x7f7127059000) libQt5Widgets.so.5 => /usr/lib64/libQt5Widgets.so.5 (0x7f7126803000) libQt5Gui.so.5 => /usr/lib64/libQt5Gui.so.5 (0x7f7126116000) libQt5Core.so.5 => /usr/lib64/libQt5Core.so.5 (0x7f7125a69000) libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/libstdc++.so.6 (0x7f7125662000) libgcc_s.so.1 => /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/libgcc_s.so.1 (0x7f712544a000) libc.so.6 => /lib64/libc.so.6 (0x7f7125084000) libQt5Network.so.5 => /usr/lib64/libQt5Network.so.5 (0x7f7124cf2000) libkritaimpex.so.17 => /usr/lib64/libkritaimpex.so.17 (0x7f7124ad6000) libkritacolor.so.17 => /usr/lib64/libkritacolor.so.17 (0x7f71248d2000) libkritalibbrush.so.17 => /usr/lib64/libkritalibbrush.so.17 (0x7f7124676000) libpng16.so.16 => /usr/lib64/libpng16.so.16 (0x7f712444)
[digikam] [Bug 404859] Using Batch Queue Manager to make a JPG copy of the images on completion the "arw" images are no longer visible in the originating album
https://bugs.kde.org/show_bug.cgi?id=404859 --- Comment #1 from Steven Tyrer --- Tried saving the JPG's to a new folder but original "arw" images still disappear from Digikam but are still visible in the Ubuntu file system. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 379637] breeze-gtk should draw shadows for client-side-decorated windows
https://bugs.kde.org/show_bug.cgi?id=379637 --- Comment #32 from Gianluca Pettinello --- (In reply to David Edmundson from comment #31) > How? If we use the DialogShadows.cpp code and apply it to each Window that has _GTK_FRAME_EXTENTS enabled (we can trap it in kwin events.cpp)? Too naif? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 404859] Using Batch Queue Manager to make a JPG copy of the images on completion the "arw" images are no longer visible in the originating album
https://bugs.kde.org/show_bug.cgi?id=404859 Steven Tyrer changed: What|Removed |Added CC||tyrer.ste...@yahoo.co.uk Platform|Other |Ubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 404859] New: Using Batch Queue Manager to make a JPG copy of the images on completion the "arw" images are no longer visible in the originating album
https://bugs.kde.org/show_bug.cgi?id=404859 Bug ID: 404859 Summary: Using Batch Queue Manager to make a JPG copy of the images on completion the "arw" images are no longer visible in the originating album Product: digikam Version: 6.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: BatchQueueManager-RAWProcessing Assignee: digikam-bugs-n...@kde.org Reporter: tyrer.ste...@yahoo.co.uk Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Ubuntu 18.04.02 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.
[Discover] [Bug 402491] Unclear behavior when internet connection is interrupted during an update
https://bugs.kde.org/show_bug.cgi?id=402491 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 404714] Kamoso's right drawer handle icon is invisible
https://bugs.kde.org/show_bug.cgi?id=404714 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 404848] Crash on "Enter Next Transcation"
https://bugs.kde.org/show_bug.cgi?id=404848 --- Comment #2 from Robert Blackwell --- Using build 306 (kmymoney-master-306-windows-msvc2017_64-cl.exe) as a means of testing; It fails at; a) the ledger for the account containing the scheduled transaction b) the schedule view It fails shortly after I click on the menu item that reads "Enter Next Transaction". No error messages occur. The Busy icon displays for a few seconds then the program closes abruptly. It seems to fail at the point where the transaction window would normally open. It _DOES NOT_ fail on the Home Screen. I am able to enter a scheduled transaction from the home screen by clicking on the "Enter Schedule" button. When I do, the transaction window opens. I'm then able to "Enter" the transaction without the program stopping. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 404804] Power management KCM suggests to solve problem by starting a service not listed in "Startup and Shutdown" KCM
https://bugs.kde.org/show_bug.cgi?id=404804 Daniel Zeiter changed: What|Removed |Added CC||dunas...@gmx.ch -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 395596] [OpenVPN] qt version of network manager gui does not work with openvpn >= 2.4 configuration
https://bugs.kde.org/show_bug.cgi?id=395596 Pascal changed: What|Removed |Added Version|5.12.5 |5.15.2 Platform|Kubuntu Packages|Archlinux Packages CC||pascalarg...@gmx.ch --- Comment #5 from Pascal --- Same problem here. Looks like it's not solved yet. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404858] "Add Network Folder" tooltip icon does not show on Breeze, shows correctly on Breeze Dark
https://bugs.kde.org/show_bug.cgi?id=404858 --- Comment #2 from Thiago Sueto --- Created attachment 118392 --> https://bugs.kde.org/attachment.cgi?id=118392=edit "Add Network Folder" tooltip icon on Breeze Dark. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404858] "Add Network Folder" tooltip icon does not show on Breeze, shows correctly on Breeze Dark
https://bugs.kde.org/show_bug.cgi?id=404858 --- Comment #1 from Thiago Sueto --- Created attachment 118391 --> https://bugs.kde.org/attachment.cgi?id=118391=edit "Add Network Folder" tooltip icon on Breeze. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404858] New: "Add Network Folder" tooltip icon does not show on Breeze, shows correctly on Breeze Dark
https://bugs.kde.org/show_bug.cgi?id=404858 Bug ID: 404858 Summary: "Add Network Folder" tooltip icon does not show on Breeze, shows correctly on Breeze Dark Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Theme - Breeze Assignee: visual-des...@kde.org Reporter: herzensch...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY The tooltip that appears on mouse hover at "Add Network Folder" does not show its icon on Breeze, but shows correctly on Breeze Dark. My first guess is that the tooltip icon tries to follow its folder icon variant, but since the tooltip icon shows on a dark background, unlike the folder icon, which shows on Dolphin's white background, there's a mismatch. Please see the attachments. OBSERVED RESULT Tooltip for Add Network Folder shows no apparent icon. EXPECTED RESULT Tooltip for Add Network Folder should show its icon correctly. SOFTWARE/OS VERSIONS Operating System: KDE neon Developer Edition (Git Unstable) KDE Plasma Version: 5.15.80 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.0 Kernel Version: 4.15.0-45-generic OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 404833] KDE's platform file dialog embedding
https://bugs.kde.org/show_bug.cgi?id=404833
--- Comment #13 from RJVB ---
Created attachment 118390
--> https://bugs.kde.org/attachment.cgi?id=118390=edit
testing mod
So this works on Linux too, see the attached patch.
I've been testing this with an application that does
auto fDialog = new QFileDialog(this, tr("Pick a font file"), startDir);
auto variant = QVariant(QVariant::UserType);
variant.setValue(fDialog);
fDialog->setProperty("QFileDialogInstance", variant);
fDialog->setProperty("QFileDialogParentClass",
metaObject()->className());
qWarning() << "\t" << fDialog <<
fDialog->property("QFileDialogInstance")
<< fDialog->property("QFileDialogParentClass");
if (fDialog->exec() && !fDialog->selectedFiles().isEmpty()) {
}
This prints
QFileDialog(0x1749cc0) QVariant(QFileDialog*, QFileDialog(0x1749cc0))
QVariant(QString, "Dialog")
virtual bool KDEPlatformFileDialogHelper::show(Qt::WindowFlags,
Qt::WindowModality, QWindow *) KDEPlatformFileDialogHelper(0x16e5530)
KDEPlatformFileDialog(0x170ba10) QWidgetWindow(0x16ba7f0,
name="DialogClassWindow") Dialog(0x7fff972af318)
QVariant(Invalid) QVariant(Invalid)
(QFileDialog(0x1749cc0))
Here the 1st line comes from the application, the other 3 lines from
KDEPlatformFileDialogHelper::show().
As you can see, the properties are set correctly but for some reason they
cannot be read from the integration plugin. Maybe after a dynamic_cast to
QFileDialog?
However, findChildren() is promising and could be the solution if we can assume
that there are never multiple QFileDialog instances that share the same parent
(or if we can distinguish them somehow).
FWIW, I've even seen "(ScFileWidget(0x2fa45b0))" when opening a native
filedialog in Scribus, so findChildren() also works on classes that inherit
QFileDialog.
Now, how do you think we could use this information to embed the
KDEPlatformFileDialog into the parent of the instance we just retrieved?
--
You are receiving this mail because:
You are watching all bug changes.
[Spectacle] [Bug 404839] Under Gnome, application is not operational
https://bugs.kde.org/show_bug.cgi?id=404839
--- Comment #2 from Ricky Tigg ---
$ loginctl show-session `loginctl | sed -n '2p' | awk '{print $1}'` -p Type
Type=wayland
--
You are receiving this mail because:
You are watching all bug changes.
[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case
https://bugs.kde.org/show_bug.cgi?id=222878 boris.big...@hotmail.com changed: What|Removed |Added CC||boris.big...@hotmail.com --- Comment #40 from boris.big...@hotmail.com --- Still happens with kontact 5.10.2 using kde frameworks 5.55.0. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 404820] default construction SyntaxHighlighter() crashes
https://bugs.kde.org/show_bug.cgi?id=404820 Dominik Haumann changed: What|Removed |Added URL||https://codereview.qt-proje ||ct.org/#/c/254448/ --- Comment #3 from Dominik Haumann --- Proposed upstream patch for Qt 5.12: https://codereview.qt-project.org/#/c/254448/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404857] Application Menu keeps focus on quick virtual desktop change
https://bugs.kde.org/show_bug.cgi?id=404857 --- Comment #1 from veggero --- Created attachment 118389 --> https://bugs.kde.org/attachment.cgi?id=118389=edit Example to reproduce the bug -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 403936] Defish effect not working after adding clips
https://bugs.kde.org/show_bug.cgi?id=403936 --- Comment #12 from CzAndrew --- Created attachment 118388 --> https://bugs.kde.org/attachment.cgi?id=118388=edit kdenlive project with eng keyboard The kdenlive project which was made with english keyboard settings has been attached! Result: The defish effect still not working. (First I closed kdenlive completely with unlocker because dbus-daemon.exe process was still open from the last start. Changed the keyboard from hungarian to english. Started kdenlive 18.12.1, added title, clip, effect...) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404857] New: Application Menu keeps focus on quick virtual desktop change
https://bugs.kde.org/show_bug.cgi?id=404857 Bug ID: 404857 Summary: Application Menu keeps focus on quick virtual desktop change Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Global Menu Assignee: k...@privat.broulik.de Reporter: niccolo.venera...@gmail.com CC: mvourla...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. Add a Global Menu 2. Add some Virtual Desktops 3. Set a easy to press key to switch Virtual Desktops, e.g.: meta+left, meta+right 4. Open a window in a Virtual Desktop 5. Switch to the Virtual Desktop near said window 6. Switch to the Virtual Desktop with the window, but quickly get back to the empty Virtual Desktop OBSERVED RESULT The Global Menu of the application is still shown. EXPECTED RESULT The Global Menu is hidden as no application has focus in this Virtual Desktop. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.15.1 (available in About System) KDE Frameworks Version: 5.55.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION Please note that this happens often to me simply going from a busy Virtual Desktop one to a empty one, but this is the easiest way to reproduce. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 403936] Defish effect not working after adding clips
https://bugs.kde.org/show_bug.cgi?id=403936 emohr changed: What|Removed |Added Status|REPORTED|CONFIRMED Flags||Brainstorm+ Ever confirmed|0 |1 --- Comment #11 from emohr --- Thank you for uploading the file. There is a type-/characterset conflict with “comma” where a “point” is expected. As soon as you have a title-clip and you type some text this happen. This is why clip only work. Can you test the following: change your keyboard language to English and test again. I open issue https://invent.kde.org/kde/kdenlive/issues/78 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374575] "Shortcut for switching to this activity" has no effect when set from the Activities KCM
https://bugs.kde.org/show_bug.cgi?id=374575 Yuze Jiang changed: What|Removed |Added CC||fortissi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404856] New: [Wayland] Right click on desktop stops working after desktop grid effect
https://bugs.kde.org/show_bug.cgi?id=404856 Bug ID: 404856 Summary: [Wayland] Right click on desktop stops working after desktop grid effect Product: plasmashell Version: 5.15.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: 1.0 SUMMARY Only reproducible on Wayland. Both Arch Linux and neon dev unstable are affected. STEPS TO REPRODUCE 1. minimize all windows 2. activate desktop grid effect (default shortcut is ctrl+f8) 3. leave desktop grid effect by clicking some desktop or by pressing the same shortcut 4. right click on desktop OBSERVED RESULT nothing happens. Right click works again after you click on toolbox (icon in the upper right corner). EXPECTED RESULT right click on desktop always works. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.1 Operating System: KDE neon Developer Edition KDE Plasma Version: 5.15.80 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 383179] KDE desktop compositing occasionally causes flickering and frozen window contents
https://bugs.kde.org/show_bug.cgi?id=383179 blaueshawaiih...@gmx.de changed: What|Removed |Added CC||blaueshawaiih...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 404849] Icon Request: switch all applications' sounds to an audio device
https://bugs.kde.org/show_bug.cgi?id=404849 Nate Graham changed: What|Removed |Added CC||n...@kde.org Severity|normal |wishlist Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations
https://bugs.kde.org/show_bug.cgi?id=361154 blaueshawaiih...@gmx.de changed: What|Removed |Added CC||blaueshawaiih...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384660] Part of the screen(s) "often" flickers when showing windows
https://bugs.kde.org/show_bug.cgi?id=384660 blaueshawaiih...@gmx.de changed: What|Removed |Added CC||blaueshawaiih...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404855] New: Crash and visual update issue with transform tool
https://bugs.kde.org/show_bug.cgi?id=404855 Bug ID: 404855 Summary: Crash and visual update issue with transform tool Product: krita Version: git master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Transform Assignee: krita-bugs-n...@kde.org Reporter: rjquira...@gmail.com Target Milestone: --- Created attachment 118387 --> https://bugs.kde.org/attachment.cgi?id=118387=edit GDB text SUMMARY The transformation tool options "cage" and "warp" have no visual updates of the changes, can't tell what's been transformed until a few moments later when the full modification takes places (see video, last part of it demonstrates). Applying the transformations changes will most of the time crash Krita. The other options seems to have no issues. STEPS TO REPRODUCE 1. Make a new file (or open existent) and select transformation tool. 2. Select either the Cage or Warp transformations and try to transform any shape. 3. Apply changes. https://drive.google.com/file/d/1v4zuS-vlg2ewo04lCPCBnRcLpaY5_smQ/view?usp=sharing (I keep moving mouse to indicate that video is still recording :) ) OBSERVED RESULT While trying to transform, there would be no visual feedback/update of what is been changed. Applying the final changes (once the canvas updates) it will most likely crash Krita. EXPECTED RESULT Been able to see what is been changed (normal behaviour). Krita Version: 4.2.0-pre-alpha (git d7c5312) Qt Version (compiled): 5.12.0 Version (loaded): 5.12.1 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 4.20.12-arch1-1-ARCH Pretty Productname: Arch Linux Product Type: arch Product Version: unknown OpenGL Info Vendor: NVIDIA Corporation Renderer: "GeForce GT 430/PCIe/SSE2" Version: "4.6.0 NVIDIA 390.116" Shading language: 4.60 NVIDIA Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 4.6, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 0, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Version: 4.6 Supports deprecated functions true is OpenGL ES: false Hardware Information Memory: 15 Gb Cores: 6 Swap: /tmp -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 395107] Spell check does not work + missing language
https://bugs.kde.org/show_bug.cgi?id=395107 --- Comment #8 from Rigo Wenning --- I installed from http://download.opensuse.org/repositories/KDE:Unstable:Extra/openSUSE_Tumbleweed/ I've uninstalled kile and kile-lang first, added the repo with priority 102 and installed kile5. It works like a charm. But I assume they will soon integrate kile5 into Tumbleweed anyway. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387313] Subsurfaces are not clipped
https://bugs.kde.org/show_bug.cgi?id=387313 --- Comment #60 from Rainer Finke --- Yes, desktop effects like wobbling windows, magic lamp and desktop cube clearly show that the Wayland applications like systemsettings, Kmail and Firefox are not rendered correctly, so the flickering probably is just most obvious to a normal user. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402971] Suggestion to improve multibrush tool
https://bugs.kde.org/show_bug.cgi?id=402971 Scott Petrovic changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Scott Petrovic --- This feature has been added and will be available in Krita 4.2. Closing this ticket as this ticket was about adding the feature. The current UI that was added is a bit confusing. There is a separate discussion going with how to improve the UI/UX for the multi-brush tool. https://phabricator.kde.org/T10534 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 404848] Crash on "Enter Next Transcation"
https://bugs.kde.org/show_bug.cgi?id=404848 Thomas Baumgart changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Thomas Baumgart --- I am a bit confused by "1. Open Scheduled Transaction Account". Do you mean a) open the ledger for the account containing the scheduled transaction b) open the schedule view There is a third spot that can start the entry of a scheduled transaction which is the home view showing scheduled transactions. So my questions are: 1) Where does it fail for you and 2) Does it also fail using the other two methods? -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 404739] Upload file dialog doesn't allow selection of multiple files
https://bugs.kde.org/show_bug.cgi?id=404739 Nate Graham changed: What|Removed |Added Version Fixed In||5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 404777] KIO::CopyJob::setDefaultPermissions does not work
https://bugs.kde.org/show_bug.cgi?id=404777 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #1 from Nate Graham --- Would you like to submit patch? :) -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 404724] Google file id changed when move file to other folder via kio-gdrive
https://bugs.kde.org/show_bug.cgi?id=404724 Murz changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Murz --- Seems this issue is fixed in some recent updates, now files moved correctly. -- You are receiving this mail because: You are watching all bug changes.
[user-manager] [Bug 400060] State of brightness and bluetooth are not respected on user switching
https://bugs.kde.org/show_bug.cgi?id=400060 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- I can't reproduce the problem with screen brightness as least. I have no bluetooth device to test. Operating System: KDE neon Developer Edition KDE Plasma Version: 5.15.80 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.0 Kernel Version: 4.15.0-45-generic -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404643] Launching a second instance of single-instance application doesn't give focus to the running instance at Low or higher focus stealing prevention level
https://bugs.kde.org/show_bug.cgi?id=404643 --- Comment #5 from Martin Flöser --- I recommend using existing libraries like KRun in combination with KWindowsystem to achieve this. Way better solution than trying to reinvent the wheel. Also I recommend to remove everything where you try to activate or raise. That's where the window manager kicks in. If you get the startup notification done the window manager will ensure the window has focus and it's raised. That's his damn job. If you try to raise or active the window manager recognizes an attempt to steal focus and prevent it - that's also his damn job. Also ensure your user time stamps are up to date. That helps a lot. -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 404854] New: kdialog - suggested wrong filetype and wrong layout
https://bugs.kde.org/show_bug.cgi?id=404854 Bug ID: 404854 Summary: kdialog - suggested wrong filetype and wrong layout Product: kdialog Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: br...@frogmouth.net Reporter: pigeonskil...@libero.it Target Milestone: --- Created attachment 118386 --> https://bugs.kde.org/attachment.cgi?id=118386=edit kdialog - suggested wrong filetype and wrong layout SUMMARY Using latest version of Manjaro KDE and Slimjet 21.0.8.0 as web browser. When trying to 'save a page with filename' kdialog always shows a wrong filetype (xhtml instead of html) and doesn't show the checkbox at the bottom of the window... STEPS TO REPRODUCE 1. Use Slimjet 21.0.8.0 2. Try to save a page with a file name choosen by you OBSERVED RESULT Note the suggested wrong filetype and wrong layout of kdialog EXPECTED RESULT - SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE rolling release kernel 4.20.12 KDE Plasma Version: 5.15.1 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.1 ADDITIONAL INFORMATION Investigating if the bug is due to Slimjet... -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 404680] timeline refactor 2019-02-21_Composition effect issues.
https://bugs.kde.org/show_bug.cgi?id=404680 --- Comment #10 from emohr --- Hi Evert. Thanks for the feedback. -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 404833] KDE's platform file dialog embedding
https://bugs.kde.org/show_bug.cgi?id=404833 --- Comment #12 from RJVB --- I know you said "without use of private APIs" ... but it seems that - the parent received in KDEPlatformFileDialogHelper::show() is a QWidgetWindow - QWidgetWindow::widget() should give us the widget instance used in the application I couldn't get the code to build when trying QWidgetWindow::widget(), but there's an easier, non-private way: QWidget *parentWidget = parent ? QWidget::find(parent->winId()) : nullptr; This works on Mac, e.g. "QWidgetWindow(0x7fcd05b97fd0, name="KIconDialogClassWindow")" becomes "KIconDialog(0x7fff586d1ba8)" (in kicondialogtest from the KIconThemes tests; KIconDialog is used as a parent for QFileDialog). If it also works on Linux: - the application could call QFileDialog::setProperty() to communicate relevant information (the QFileDialog instance?) - the KDEPlatformFileDialogHelper could also use setProperty() on the widget obtained, e.g. to signal that the KDE dialog is in use. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 404853] New: digikam-6.0.0 FTBFS on ppc64le arch
https://bugs.kde.org/show_bug.cgi?id=404853
Bug ID: 404853
Summary: digikam-6.0.0 FTBFS on ppc64le arch
Product: digikam
Version: 6.0.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Faces-Engine
Assignee: digikam-bugs-n...@kde.org
Reporter: rdie...@gmail.com
Target Milestone: ---
On fedora 30 using gcc9,
../core/libs/facesengine/recognition/dlib-dnn/dnnface/dnn_face.h:175:88:
required from here
../core/libs/facesengine/recognition/dlib-dnn/dnnface/image_transforms/interpolation.h:1088:22:
error: conversion from 'const double' to 'const simd4f' is ambiguous
1088 | const simd4f _tb_frac = tb_frac;
| ^~~~
In file included from
../core/libs/facesengine/recognition/dlib-dnn/dnnface/image_transforms/interpolation.h:46,
from ../core/libs/facesengine/facedb/facedb.cpp:44:
../core/libs/facesengine/recognition/dlib-dnn/dnnface/dnn_base/simd4f.h:128:16:
note: candidate: 'simd4f::simd4f(float)'
128 | inline simd4f(float f) : x{f,f,f,f} { }
|^~
../core/libs/facesengine/recognition/dlib-dnn/dnnface/dnn_base/simd4f.h:121:16:
note: candidate: 'simd4f::simd4f(int)'
121 | inline simd4f(const vector float& v) : x{v} { }
|^~
In file included from ../core/libs/facesengine/facedb/facedb.cpp:44:
../core/libs/facesengine/recognition/dlib-dnn/dnnface/image_transforms/interpolation.h:1089:22:
error: conversion from 'double' to 'const simd4f' is ambiguous
1089 | const simd4f _inv_tb_frac = 1-tb_frac;
| ^~~~
In file included from
../core/libs/facesengine/recognition/dlib-dnn/dnnface/image_transforms/interpolation.h:46,
from ../core/libs/facesengine/facedb/facedb.cpp:44:
../core/libs/facesengine/recognition/dlib-dnn/dnnface/dnn_base/simd4f.h:128:16:
note: candidate: 'simd4f::simd4f(float)'
128 | inline simd4f(float f) : x{f,f,f,f} { }
|^~
../core/libs/facesengine/recognition/dlib-dnn/dnnface/dnn_base/simd4f.h:121:16:
note: candidate: 'simd4f::simd4f(int)'
121 | inline simd4f(const vector float& v) : x{v} { }
|^~
In file included from ../core/libs/facesengine/facedb/facedb.cpp:44:
../core/libs/facesengine/recognition/dlib-dnn/dnnface/image_transforms/interpolation.h:1090:22:
error: conversion from 'double' to 'const simd4f' is ambiguous
1090 | const simd4f _x_scale = 4*x_scale;
| ^~~~
In file included from
../core/libs/facesengine/recognition/dlib-dnn/dnnface/image_transforms/interpolation.h:46,
from ../core/libs/facesengine/facedb/facedb.cpp:44:
../core/libs/facesengine/recognition/dlib-dnn/dnnface/dnn_base/simd4f.h:128:16:
note: candidate: 'simd4f::simd4f(float)'
128 | inline simd4f(float f) : x{f,f,f,f} { }
|^~
../core/libs/facesengine/recognition/dlib-dnn/dnnface/dnn_base/simd4f.h:121:16:
note: candidate: 'simd4f::simd4f(int)'
121 | inline simd4f(const vector float& v) : x{v} { }
|^~
Full logs,
https://koji.fedoraproject.org/koji/taskinfo?taskID=33066535
(interesting piece is build.log link)
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 404852] New: Crash upon saving due something with the mirror config. [gdb backtrace]
https://bugs.kde.org/show_bug.cgi?id=404852 Bug ID: 404852 Summary: Crash upon saving due something with the mirror config. [gdb backtrace] Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: griffinval...@gmail.com Target Milestone: --- Got this crash while saving: Thread 1 "krita" received signal SIGSEGV, Segmentation fault. 0x766bb109 in KisMirrorAxisConfig::Private::operator== (this=0x696a7e70, rhs=...) at /home/wolthera/krita/src/libs/ui/canvas/KisMirrorAxisConfig.cpp:40 40 return mirrorHorizontal == rhs.mirrorHorizontal && (gdb) thread apply all backtrace Thread 642 (Thread 0x7fff7b7fe700 (LWP 13270)): #0 0x7fffebfbaed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fff7b7fdbc0, expected=0, futex_word=0x73f539a0) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fff7b7fdc80, mutex=0x73f53950, cond=0x73f53978) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x73f53978, mutex=0x73f53950, abstime=0x7fff7b7fdc80) at pthread_cond_wait.c:667 #3 0x73141ac6 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x73141e25 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7313f5dd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7313abc2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fffebfb46db in start_thread (arg=0x7fff7b7fe700) at pthread_create.c:463 #8 0x7282288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7fff97fff700 (LWP 31457)): #0 0x72815bf9 in __GI___poll (fds=0x7fff8c004ee0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fffea6b8539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fffea6b864c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7337015b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7331164a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7313941a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7313abc2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fffebfb46db in start_thread (arg=0x7fff97fff700) at pthread_create.c:463 #8 0x7282288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7fff9c84e700 (LWP 31448)): #0 0x72815bf9 in __GI___poll (fds=0x7fff900052a0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fffea6b8539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fffea6b864c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7337013f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7331164a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7313941a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fffd66e81c6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7313abc2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fffebfb46db in start_thread (arg=0x7fff9c84e700) at pthread_create.c:463 #9 0x7282288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 ---Type to continue, or q to quit--- Thread 14 (Thread 0x7fffaae1d700 (LWP 31439)): #0 0x72815bf9 in __GI___poll (fds=0x7fff98004990, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fffea6b8539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fffea6b864c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7337013f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7331164a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7313941a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fffd62232e5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7313abc2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fffebfb46db in start_thread (arg=0x7fffaae1d700) at pthread_create.c:463 #9 0x7282288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7fffaa61c700 (LWP 31406)): #0 0x727e59d0 in __GI___nanosleep
[kdenlive] [Bug 404851] New: Don't switch to Non-Fullscreen
https://bugs.kde.org/show_bug.cgi?id=404851 Bug ID: 404851 Summary: Don't switch to Non-Fullscreen Product: kdenlive Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: volker.h...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. CTRL+Shift+F 2. Screen don't change to Non Full Screen 3. Don't switch back to Fullscreen only the bottom right corner change. OBSERVED RESULT the frame will be smaller again but can't switch to a small screen. EXPECTED RESULT switch between Fullscreen and Non full Screen SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: Mint 18.3 Sylvia Cinnamon KDE Plasma Version: KDE Frameworks Version: Qt Version: 5.5.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 40236] keyboard shortcut to switch konsole to fullscreen
https://bugs.kde.org/show_bug.cgi?id=40236 weakbit changed: What|Removed |Added CC||volker.h...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 403373] Disabling touchpad breaks touchpad configuration
https://bugs.kde.org/show_bug.cgi?id=403373 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #2 from Patrick Silva --- I can't confirm. Touchpad settings are applied as expected while a usb mouse is plugged in and the touchpad is disabled. Operating System: KDE neon Developer Edition KDE Plasma Version: 5.15.80 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.0 Kernel Version: 4.15.0-45-generic -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 399570] Akregator crashes after clicking on link in an open tab
https://bugs.kde.org/show_bug.cgi?id=399570 Wolfgang Bauer changed: What|Removed |Added CC||philippe.roub...@free.fr --- Comment #4 from Wolfgang Bauer --- *** Bug 404765 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 404765] left click on a link => kontact-akregator crash
https://bugs.kde.org/show_bug.cgi?id=404765 Wolfgang Bauer changed: What|Removed |Added Status|REPORTED|RESOLVED CC||wba...@tmo.at Resolution|--- |DUPLICATE --- Comment #1 from Wolfgang Bauer --- Same backtrace as bug#399570: (In reply to Philippe ROUBACH from comment #0) > Thread 1 (Thread 0x7fc20fd95900 (LWP 8015)): > [KCrash Handler] > #6 QString::isNull (this=0x68) at /usr/include/qt5/QtCore/qstring.h:822 > #7 QtWebEngineCore::ProfileAdapter::httpUserAgent (this=0x0) at > /usr/src/debug/libqt5-qtwebengine-5.12.1-lp150.3.1.x86_64/src/core/ > profile_adapter.cpp:287 > #8 0x7fc1fb87ddd8 in QtWebEngineCore::WebContentsAdapter::initialize > (this=this@entry=0x5562d519e930, site=site@entry=0x0) at > /usr/src/debug/libqt5-qtwebengine-5.12.1-lp150.3.1.x86_64/src/core/ > web_contents_adapter.cpp:470 > #9 0x7fc1fb87e62c in QtWebEngineCore::WebContentsAdapter::loadDefault > (this=this@entry=0x5562d519e930) at > /usr/src/debug/libqt5-qtwebengine-5.12.1-lp150.3.1.x86_64/src/core/ > web_contents_adapter.cpp:568 *** This bug has been marked as a duplicate of bug 399570 *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 404850] New: Archiving of mails in kmail folders doesn't work - collection does not exist
https://bugs.kde.org/show_bug.cgi?id=404850 Bug ID: 404850 Summary: Archiving of mails in kmail folders doesn't work - collection does not exist Product: kmail2 Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-b...@kde.org Reporter: piedro.kul...@gmail.com Target Milestone: --- SUMMARY The attempt to archive even a single mail does result in a "collection does not exist" error. STEPS TO REPRODUCE 1. create a fresh user account with default settings 2. add an standard email account (also apllies to gmail accounts) 3. right click on any message in any folder and chose archive (make sure you've set an accessible archive folder before!) OBSERVED RESULT you get a notification saying "Collection can't be fetched. collection doesn't exist." EXPECTED RESULT Obviously: move mail to designated archive folder SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: Arch linux, fully updated (available in About System) KDE Plasma Version: Plasma 5.15.1 KDE Frameworks Version: KDE 18.12.1 Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 402328] Discover crashes on launch in AbstractResource::reportNewState() due to some Fwupd issue
https://bugs.kde.org/show_bug.cgi?id=402328 Nate Graham changed: What|Removed |Added Status|REOPENED|RESOLVED Version Fixed In|5.14.5.1|5.14.5.1, 5.15.1, 5.16.0 Resolution|--- |FIXED --- Comment #62 from Nate Graham --- Urgh, you're right, it's in 5.15.1. Derp. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 126348] (rdpmc) vex x86->IR: unhandled instruction bytes: 0xF 0x33 0x89 0x45
https://bugs.kde.org/show_bug.cgi?id=126348 --- Comment #8 from Vince Weaver --- (In reply to Vince Weaver from comment #7) > If you want some tests to test this out sorry about that, hit enter at the wrong location in the browser. If you want tests to test this out, see: https://github.com/deater/perf_event_tests in the tests/rdpmc directory specifically rdpmc_validation and rdpmc_invalid -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 126348] (rdpmc) vex x86->IR: unhandled instruction bytes: 0xF 0x33 0x89 0x45
https://bugs.kde.org/show_bug.cgi?id=126348 --- Comment #7 from Vince Weaver --- If you want some tests to test this out -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 404358] Cancelled installation of a Snap package (VSCode) made Discovery lock up with a 0% task in the tube.
https://bugs.kde.org/show_bug.cgi?id=404358 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
