[krita] [Bug 408199] If I use my pen to draw a line and then hover over the screen, the pen would continue to draw.
https://bugs.kde.org/show_bug.cgi?id=408199 tus...@vista.aero changed: What|Removed |Added Component|Brush engines |tablet support CC||tus...@vista.aero --- Comment #1 from tus...@vista.aero --- Cannot reproduce this on Surface Pro 4. Probably a tablet-related issue. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 408203] New: «Konqueror crashing on start of Plasma Desktop»
https://bugs.kde.org/show_bug.cgi?id=408203 Bug ID: 408203 Summary: «Konqueror crashing on start of Plasma Desktop» Product: konqueror Version: 5.0.97 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: cescp...@gmail.com Target Milestone: --- Application: konqueror (5.0.97) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-50-generic x86_64 Distribution: Ubuntu 18.04.2 LTS -- Information about the crash: Application: konqueror (5.0.97) Qt Version: 5.9.1 Frameworks Version: 5.37.0 Operating System: Linux 4.4.0-94-generic x86_64 Distribution: KDE neon User Edition 5.10 -- Information about the crash: - What I was doing when the application crashed: Just turned the computer on. The crash occured during start of Plasma Desktop. -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7f89f17940 (LWP 2255))] Thread 20 (Thread 0x7f7f2b7fe700 (LWP 2353)): #0 0x7f7f8b5645aa in pa_fdsem_before_poll () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so #1 0x7f7f8b57b027 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so #2 0x7f7f8c2f80b7 in pa_mainloop_dispatch () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f7f8c2f84bc in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f7f8c2f8560 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f7f8c3067a9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f7f8b58b078 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so #7 0x7f7f936a46ba in start_thread (arg=0x7f7f2b7fe700) at pthread_create.c:333 #8 0x7f7f9c5083dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 19 (Thread 0x7f7f2bfff700 (LWP 2352)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7f7f6c823d22 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #2 0x7f7f6c7ec284 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #3 0x7f7f6c7c7218 in base::MessagePumpDefault::Run(base::MessagePump::Delegate*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f7f6c7c3225 in base::MessageLoop::RunHandler() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f7f6c7dfefa in base::RunLoop::Run() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f7f6c7f7d96 in base::Thread::ThreadMain() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f7f6c7f3f3d in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f7f936a46ba in start_thread (arg=0x7f7f2bfff700) at pthread_create.c:333 #9 0x7f7f9c5083dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 18 (Thread 0x7f7f44ff9700 (LWP 2351)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f7f6cf629dd in cc::SingleThreadTaskGraphRunner::Run() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #2 0x7f7f6c7f78d0 in base::SimpleThread::ThreadMain() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #3 0x7f7f6c7f3f3d in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f7f936a46ba in start_thread (arg=0x7f7f44ff9700) at pthread_create.c:333 #5 0x7f7f9c5083dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 17 (Thread 0x7f7f457fa700 (LWP 2350)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f7f6c7f636f in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #2 0x7f7f6c7f6b07 in base::SequencedWorkerPool::Worker::Run() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #3 0x7f7f6c7f78d0 in base::SimpleThread::ThreadMain() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f7f6c7f3f3d in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f7f936a46ba in start_thread (arg=0x7f7f457fa700) at pthread_create.c:333 #6 0x7f7f9c5083dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 16 (Thread 0x7f7f45ffb700 (LWP 2349)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1
[digikam] [Bug 378364] Sequence number options need date-aware modifier
https://bugs.kde.org/show_bug.cgi?id=378364 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||6.2.0 CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408164] Krita is closed suddenly
https://bugs.kde.org/show_bug.cgi?id=408164 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #5 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.
[kmymoney] [Bug 407644] Wish to export/import scheduled transactions
https://bugs.kde.org/show_bug.cgi?id=407644 --- 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.
[kate] [Bug 374792] Crash on multiple closing docs, via close button on a toolbar
https://bugs.kde.org/show_bug.cgi?id=374792 --- 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.
[konsole] [Bug 408161] UP ARROW doesn't work in konsole 19.04.1
https://bugs.kde.org/show_bug.cgi?id=408161 Nate Graham changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #7 from Nate Graham --- Thanks, glad you got it figured out and working again. :) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408161] UP ARROW doesn't work in konsole 19.04.1
https://bugs.kde.org/show_bug.cgi?id=408161 --- Comment #6 from Yuriy Vidineev --- On liveusb it works for me. If I remove all konsole settings - it works as well mv ~/.local/share/konsole/ ~/.local/share/konsole_bkp Looks like I see what's wrong - for some reason ARROW UP was set as a key to switch profiles in konsole. I'll try to dig deeper why it happened. Thanks for checking, guys! And sorry for false (most possible) alarm -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 408202] New: Feature Request: Custom color: Auto-pick color after creation
https://bugs.kde.org/show_bug.cgi?id=408202 Bug ID: 408202 Summary: Feature Request: Custom color: Auto-pick color after creation Product: kolourpaint Version: 19.04 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: notebook22...@gmail.com Target Milestone: --- SUMMARY After creating a new custom color, the color is added to the palette of 22 colors in the bottom. But it is not selected as the current active color. I think people who create a custom color are only doing this, because they are going to use that color right after creation. STEPS TO REPRODUCE 1. Doubleclick on one of the 22 colors in the bottom. 2. "Select Color" window opens. 3. Set up any color. 4. Click OK OBSERVED RESULT Created color is not the active color. EXPECTED RESULT Created color is the current active color. SOFTWARE/OS VERSIONS XUbuntu 18.04 LTS @ snap install -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 408201] New: Enhancement: Text tool: Allow marking of text
https://bugs.kde.org/show_bug.cgi?id=408201 Bug ID: 408201 Summary: Enhancement: Text tool: Allow marking of text Product: kolourpaint Version: 19.04 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: notebook22...@gmail.com Target Milestone: --- SUMMARY Currently it's not possible to mark text while editing it. STEPS TO REPRODUCE 1. Select Text tool. 2. Create new text. Write some random content. 3. Press shift+arrow keys OBSERVED RESULT Nothing happens. EXPECTED RESULT Text gets marked. SOFTWARE/OS VERSIONS XUbuntu 18.04 @ snap install ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 407494] Stock price updating slow
https://bugs.kde.org/show_bug.cgi?id=407494 Michael Carpino changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #21 from Michael Carpino --- I have tested downloading stock prices using other Linux OS which included OpenSuse and Ubuntu. Both of these OS performed the updating of stock prices within KMM as it should. I looked at the trace and it is performed with the use of TLS v2. Because this is not a KMM bug or problem I felt that it to be appropriate to close this issue. This appears to be specifcally within how Fedora handles the connection of TLS v3. I expect someday in the future Fedora/Redhat will provide a fix to efficient and proper handling of v3. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408193] i cant render my aniamtion
https://bugs.kde.org/show_bug.cgi?id=408193 Ahab Greybeard changed: What|Removed |Added CC||ahab.greybe...@hotmail.co.u ||k --- Comment #1 from Ahab Greybeard --- The best place to discuss this is the General Help forum: https://forum.kde.org/viewforum.php?f=139 This bug report contains no information that would help to solve your problem and is probably not a fault in krita itself. Please post in the General Help forum where you can have a discussion in more detail. -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 408200] New: Enhancement: Unselect selection, if clicked outside the canvas (in the grey area)
https://bugs.kde.org/show_bug.cgi?id=408200 Bug ID: 408200 Summary: Enhancement: Unselect selection, if clicked outside the canvas (in the grey area) Product: kolourpaint Version: 19.04 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: notebook22...@gmail.com Target Milestone: --- SUMMARY If you click outside the canvas area, the current selection does not get removed. STEPS TO REPRODUCE 1. Select selection tool. 2. Select a random area. 3. Click on the grey area outside the canvas. OBSERVED RESULT Selection stays. EXPECTED RESULT Selection disappears. SOFTWARE/OS VERSIONS Ubuntu 18.04 LTS Install: snap installation ADDITIONAL INFORMATION This comes into play, when the canvas is bigger, than the screen size. E.g extremely large images or zoomed images. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408182] Scaling with the transform tool deletes the selection
https://bugs.kde.org/show_bug.cgi?id=408182 Ahab Greybeard changed: What|Removed |Added CC||ahab.greybe...@hotmail.co.u ||k --- Comment #1 from Ahab Greybeard --- I don't see this on the 4.2.0 appimage for a variety of selection methods and a variety of transforms. Windows Only? Krita Version: 4.2.0 Languages: en_GB, en Hidpi: true Qt Version (compiled): 5.12.2 Version (loaded): 5.12.2 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 4.9.0-9-amd64 Pretty Productname: Debian GNU/Linux 9 (stretch) Product Type: debian Product Version: 9 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408199] New: If I use my pen to draw a line and then hover over the screen, the pen would continue to draw.
https://bugs.kde.org/show_bug.cgi?id=408199 Bug ID: 408199 Summary: If I use my pen to draw a line and then hover over the screen, the pen would continue to draw. Product: krita Version: 4.2.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: critical Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: jiaqingli...@gmail.com Target Milestone: --- SUMMARY This is for Lenovo Windows 2 in 1 tablet. If I use my pen to draw a line and then hover over the screen, the pen would continue to draw. There is no pressure either. Note: this did not happen in the previous version. STEPS TO REPRODUCE 1. Open Krita with a canvas, on a Lenovo Flex 14. 2. Draw some lines and then lift and hover the pen on top of the screen. 3. OBSERVED RESULT The hovering pen would still continue to draw wherever you move the pen. EXPECTED RESULT The hovering pen would still continue to draw wherever you move the pen. SOFTWARE/OS VERSIONS Windows: 10 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.
[krita] [Bug 408169] Transparent pattern fill layer renders incorrect on load
https://bugs.kde.org/show_bug.cgi?id=408169 Ahab Greybeard changed: What|Removed |Added CC||ahab.greybe...@hotmail.co.u ||k --- Comment #1 from Ahab Greybeard --- This bug seems related: https://bugs.kde.org/show_bug.cgi?id=402978 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 398324] Dophin has ambiguous shortcuts
https://bugs.kde.org/show_bug.cgi?id=398324 Nate Graham changed: What|Removed |Added CC||irishni...@gmail.com --- Comment #7 from Nate Graham --- *** Bug 408132 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 408132] kget: open destination, launching dolphin, gives error "ambiguous shortcuts", alt+tab
https://bugs.kde.org/show_bug.cgi?id=408132 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |DUPLICATE Platform|Debian testing |Debian stable Status|REPORTED|RESOLVED Version|19.04.1 |18.08.0 --- Comment #2 from Nate Graham --- Debian Buster currently has 18.08.0, per: https://packages.debian.org/buster/allpackages?format=txt.gz Bug 398324 was fixed in 18.08.2. It seems weird to me that they would ship with the initial release of 18.08 rather than its latest bugfix release. *** This bug has been marked as a duplicate of bug 398324 *** -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 408139] Overall assessment wrong
https://bugs.kde.org/show_bug.cgi?id=408139 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 408141] High CPU usage when copying files
https://bugs.kde.org/show_bug.cgi?id=408141 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||n...@kde.org Resolution|--- |WAITINGFORINFO --- Comment #1 from Nate Graham --- What process was using all the CPU? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408161] UP ARROW doesn't work in konsole 19.04.1
https://bugs.kde.org/show_bug.cgi?id=408161 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #5 from Nate Graham --- Yeah works for me too. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408102] After every Plasma update the toolbar configuration is lost
https://bugs.kde.org/show_bug.cgi?id=408102 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #1 from Nate Graham --- This seems impossible, or at least something must be very wrong. Plasma updates shouldn't touch app configurations. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 408110] Move "Window decorations" to "Plasma addons" category
https://bugs.kde.org/show_bug.cgi?id=408110 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/dis ||cover/b17de8cbf88ce32a5fec6 ||38ac6c5b3ada0f996a6 Version Fixed In||5.16.0 --- Comment #1 from Nate Graham --- Git commit b17de8cbf88ce32a5fec638ac6c5b3ada0f996a6 by Nate Graham. Committed on 02/06/2019 at 02:59. Pushed by ngraham into branch 'Plasma/5.16'. Make sure "Window Decorations" shows up in "Plasma Addons" The Aurorae ones are already there; let's move this one there too FIXED-IN: 5.16.0 M +1-1libdiscover/backends/KNSBackend/KNSBackend.cpp https://commits.kde.org/discover/b17de8cbf88ce32a5fec638ac6c5b3ada0f996a6 -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 408111] Update Manager does not make updates
https://bugs.kde.org/show_bug.cgi?id=408111 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- Kubuntu 14.04 is using Plasma 4 and Qt4 software, and both are quite old and unsupported anymore. I strongly recommend upgrading to Kubuntu 18.04 or 19.04. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408198] New: Export Image Sequence First Frame stuck on 60
https://bugs.kde.org/show_bug.cgi?id=408198 Bug ID: 408198 Summary: Export Image Sequence First Frame stuck on 60 Product: krita Version: 4.2.0-beta Platform: unspecified OS: Windows CE Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: jeremy6321...@gmail.com Target Milestone: --- Created attachment 120491 --> https://bugs.kde.org/attachment.cgi?id=120491=edit Start Value cant go lower than 60 despite having animation from 0 to 130 SUMMARY I made a animation sequence from 0 to 130 frames. when I tried to export the image sequence I could only export 60 to 130. I am not sure how well it is possible to reproduce this bug. STEPS TO REPRODUCE 1. make animation with 0 to 130 frames 2. export image sequence 3. Try to export the full sequence OBSERVED RESULT export from 60 to 130 frames EXPECTED RESULT export from 0 to 130 frames 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.
[konsole] [Bug 408161] UP ARROW doesn't work in konsole 19.04.1
https://bugs.kde.org/show_bug.cgi?id=408161 --- Comment #4 from Yuriy Vidineev --- Thanks, Kurt. It's weird. I'll check in liveusb -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408197] New: Cannot Preview Audio & Video Resources
https://bugs.kde.org/show_bug.cgi?id=408197 Bug ID: 408197 Summary: Cannot Preview Audio & Video Resources Product: kdenlive Version: Appimage - Refactoring Platform: Appimage OS: Linux Status: REPORTED Severity: major Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: jimj_...@yahoo.ca Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Select Online Resources from the menu list 2. Select Freesound Audio Library or Archive.org Video Library 3. Select an audio or video file 4. Press "Preview" button to listen or watch clip before downloading it. OBSERVED RESULT Pressing the Preview button has no effect. User must download Audio or Video clip onto their workstation. User ends up "guessing" which clip to use, rather than listening to the remote copy. EXPECTED RESULT Preview would allow a user to listen or watch a clip before downloading to see if it would be useful to use in their project or not. 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.
[kdenlive] [Bug 407987] Constantly crash when trimming video
https://bugs.kde.org/show_bug.cgi?id=407987 --- Comment #3 from Christophorus Ardi Nugraha --- Ok Thanks. I'm waiting the updates. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408170] Layer properties window draws on top of other application windows
https://bugs.kde.org/show_bug.cgi?id=408170 --- Comment #2 from Carl Olsson --- Added patch to fix this here: https://phabricator.kde.org/D21530 -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 318267] Kile frequently overwrites closing curly brackets / braces when an additional character of the same type is added
https://bugs.kde.org/show_bug.cgi?id=318267 Kevin changed: What|Removed |Added CC||kjs...@gmail.com --- Comment #3 from Kevin --- This bug still occurs on Kile, Kwrite, and Kate and now might be a duplicate of a bug introduced in the initial fix to this issue: https://bugs.kde.org/show_bug.cgi?id=368580 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 407822] subsequent ZModem upload failed to launch if cancel file dialog
https://bugs.kde.org/show_bug.cgi?id=407822 Kurt Hindenburg changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://commits.kde.org/kon |konsole/commit/9685e23e2efe |sole/9685e23e2efe07a0763c7c |07a0763c7c7716eb805cc2228df |7716eb805cc2228dfa |a | --- Comment #5 from Kurt Hindenburg --- Git commit 9685e23e2efe07a0763c7c7716eb805cc2228dfa by Kurt Hindenburg. Committed on 02/06/2019 at 00:23. Pushed by scmsync into branch 'master'. Remove unneeded setZModemBusy(true) _zmodemBusy is set to true in startZModem() so there's no need to set it before. FIXED-IN: 19.08.00 M +0-1src/SessionController.cpp https://commits.kde.org/konsole/9685e23e2efe07a0763c7c7716eb805cc2228dfa -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 407822] subsequent ZModem upload failed to launch if cancel file dialog
https://bugs.kde.org/show_bug.cgi?id=407822 Kurt Hindenburg changed: What|Removed |Added Latest Commit|https://commits.kde.org/kon |https://invent.kde.org/kde/ |sole/0509982a7cd178ac774a75 |konsole/commit/9685e23e2efe |a000af82ebf2688855 |07a0763c7c7716eb805cc2228df ||a --- Comment #4 from Kurt Hindenburg --- Git commit 9685e23e2efe07a0763c7c7716eb805cc2228dfa by Kurt Hindenburg. Committed on 02/06/2019 at 00:23. Pushed by hindenburg into branch 'master'. Remove unneeded setZModemBusy(true) _zmodemBusy is set to true in startZModem() so there's no need to set it before. FIXED-IN: 19.08.00 M +0-1src/SessionController.cpp https://invent.kde.org/kde/konsole/commit/9685e23e2efe07a0763c7c7716eb805cc2228dfa -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 368580] Auto Brackets forgets about multiple levels of brackets when overtyping closing bracket
https://bugs.kde.org/show_bug.cgi?id=368580 Kevin changed: What|Removed |Added CC||kjs...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408196] Generators Submenu Duplicates
https://bugs.kde.org/show_bug.cgi?id=408196 --- Comment #1 from James A. Jaworski --- Version 19.4.1c AppImage. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408196] New: Generators Submenu Duplicates
https://bugs.kde.org/show_bug.cgi?id=408196 Bug ID: 408196 Summary: Generators Submenu Duplicates Product: kdenlive Version: Appimage - Refactoring Platform: Appimage OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: jimj_...@yahoo.ca Target Milestone: --- Created attachment 120490 --> https://bugs.kde.org/attachment.cgi?id=120490=edit Generators Submenu SUMMARY STEPS TO REPRODUCE 1. Open up Generators menu OBSERVED RESULT Generators submenu appears twice as: Counter Color Bars White Noise Counter Color Bars White Noise EXPECTED RESULT Generators submenu items appear once as: Counter Color Bars White Noise SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Window Maker & GNOME 3.26 (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.
[kdenlive] [Bug 408142] Improve workflow when removing empty space in timeline
https://bugs.kde.org/show_bug.cgi?id=408142 Grzegorz Nowakowski changed: What|Removed |Added Summary|Improve workflow when |Improve workflow when |remove empty space in |removing empty space in |timeline|timeline -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 374485] Modified Icon Should Act as "Quick Save" or Add Save Button
https://bugs.kde.org/show_bug.cgi?id=374485 Ben Opp changed: What|Removed |Added CC||ben@eml.cc --- Comment #6 from Ben Opp --- I think the save icon should be a save button. I like that it shows up only after modifying the file, and it's in a convenient place for a save button, it should just do that. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 Fabian Lesniak changed: What|Removed |Added CC||fab...@lesniak-it.de --- Comment #98 from Fabian Lesniak --- (In reply to Wolfgang Bauer from comment #96) > What you are seeing is bug#402415 that should be fixed in konsole 19.04.0, > but you are using 18.12.3 that still has this problem. I still have this problem with Konsole 19.04.1, scaling set to 1.2. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408194] Cannot See Whole Titler Window
https://bugs.kde.org/show_bug.cgi?id=408194 James A. Jaworski changed: What|Removed |Added Summary|Cannot See Whole Title |Cannot See Whole Titler |Window |Window -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408195] unrendered pdf regions with trim margins and facing pages on 4k screen
https://bugs.kde.org/show_bug.cgi?id=408195 Kevin changed: What|Removed |Added CC||kjs...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408194] Cannot See Whole Titler Window
https://bugs.kde.org/show_bug.cgi?id=408194 --- Comment #1 from James A. Jaworski --- Previous versions of kdenlive don't have this issue. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408194] Cannot See Whole Title Window
https://bugs.kde.org/show_bug.cgi?id=408194 James A. Jaworski changed: What|Removed |Added Summary|Cannot See Whole Title |Cannot See Whole Title ||Window -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408194] New: Cannot See Whole Title
https://bugs.kde.org/show_bug.cgi?id=408194 Bug ID: 408194 Summary: Cannot See Whole Title Product: kdenlive Version: Appimage - Refactoring Platform: Appimage OS: Linux Status: REPORTED Severity: major Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: jimj_...@yahoo.ca Target Milestone: --- Created attachment 120488 --> https://bugs.kde.org/attachment.cgi?id=120488=edit Titler window SUMMARY STEPS TO REPRODUCE 1. Open Kdenlive 19.04.1 (AppImage). 2. Go to menu and select Add Title 3. OBSERVED RESULT Only the lower part of the titler window is visible. The rest is "above the screen" and I cannot reposition the window to make it visible. EXPECTED RESULT The entire Titler window is visible and I can click on any buttons to change any settings for a title or its background. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Window Maker & GNOME 3.26 (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.
[okular] [Bug 408195] New: unrendered pdf regions with trim margins and facing pages on 4k screen
https://bugs.kde.org/show_bug.cgi?id=408195 Bug ID: 408195 Summary: unrendered pdf regions with trim margins and facing pages on 4k screen Product: okular Version: 1.7.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: kjs...@gmail.com Target Milestone: --- Created attachment 120489 --> https://bugs.kde.org/attachment.cgi?id=120489=edit screenshot SUMMARY When I view certain pdfs with okular using the trim margin and facing pages feature, some regions of the pdf don't render and just appear white. See attached screenshot of this pdf: https://docs.kde.org/trunk5/en/applications/fundamentals/fundamentals.pdf This seems to only occur when the okular window is at least ~3000 pixels wide; eg, a fullscreen okular window has this issue on my 4k screen. STEPS TO REPRODUCE 1. Open https://docs.kde.org/trunk5/en/applications/fundamentals/fundamentals.pdf 2. Make okular window at least ~3000 pixels wide. 3. Enable trim margin 4. Use facing pages OBSERVED RESULT Large unrendered region, as seen in screenshot. EXPECTED RESULT Everything should be rendered. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.1.5 (available in About System) KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408193] New: i cant render my aniamtion
https://bugs.kde.org/show_bug.cgi?id=408193 Bug ID: 408193 Summary: i cant render my aniamtion Product: krita Version: 4.1.7 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: demonblack...@gmail.com Target Milestone: --- SUMMARY 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.
[krita] [Bug 408166] Rectangular grid spacing limits incorrect after resizing canvas
https://bugs.kde.org/show_bug.cgi?id=408166 --- Comment #1 from Carl Olsson --- Added patch to fix this here: https://phabricator.kde.org/D21528 -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 408179] Alternative initialisation? The properly patched Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend still hungs forever
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #28 from Nikita Sirgienko ---
I had reproduced the issue, in some sense.
1. Build Cantor with my Julia v1.0.0
2. Then, without 'make clean', rerun cmake with JULIA_EXECUTABLE points to
julia v1.1.0 (or remove julia v1.0.0 and install julia v1.1.0)
3. Build Cantor (it's not actually full rebuild, so it passes quickly)
4. Install
Now we have corrupted Julia backend: cantor_juliaserver will crash on any Julia
error and Cantor will never finish evaluation on entry with error code.
Second moment, it's a GR julia module, which Cantor uses for embedded graphic.
Important, that Cantor don't check GR precense and just import GR module,
which, if GR module not installed, cause *julia error*. Often is not a problem,
we just got an error, handle it and continue to work.
Important, that Cantor does this import *before* running user code from first
user code entry.
As can be seen, synergy of this two problems cause unending login (Cantor done
login, send import code, server crashs and Cantor never finish computing first
user code entry), that you describe in this bug report.
There is a easy way to check, if I am right about your problem: you need go to
Julia settings and disable 'Integrate Plots in Worksheet' checkbox.
If after this you could login in julia (for example, with code `print("Hello
world!")`), then we successfully localized your problem.
--
You are receiving this mail because:
You are watching all bug changes.
[krunner] [Bug 406384] AppStream runner reduces KRunner performance and causes calculator runner to not show any results approximately 60% of the time
https://bugs.kde.org/show_bug.cgi?id=406384 romulu...@gmail.com changed: What|Removed |Added CC||romulu...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408164] Krita is closed suddenly
https://bugs.kde.org/show_bug.cgi?id=408164 --- Comment #4 from Antonio Bezerra --- When I open krita's site it suggests me to install 4.2.0 version. I did it. But when i tried to open krita didn't work, not opened. So I install 4.1.5 version, but when I'm working krita closed. My OS is Windows 10. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 385520] Kate's tabs don't respect the theme and look like they came from Adwaita
https://bugs.kde.org/show_bug.cgi?id=385520 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=408192 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 408192] Inactive window effects do not apply to tab bar
https://bugs.kde.org/show_bug.cgi?id=408192 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=385520 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 408192] New: Inactive window effects do not apply to tab bar
https://bugs.kde.org/show_bug.cgi?id=408192 Bug ID: 408192 Summary: Inactive window effects do not apply to tab bar Product: kate Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: n...@kde.org Target Milestone: --- Created attachment 120487 --> https://bugs.kde.org/attachment.cgi?id=120487=edit Tab bar text does not fade along with everything else STEPS TO REPRODUCE 1. Go to System Settings > Colors 2. Edit the current color scheme 3. Check "Apply Inactive window effects" 4. Go to the "inactive" tab, change "Contrast" to "Fade" and move the slider a ways to the right 5. Open Kate with multiple tabs 6. Make the window inactive OBSERVED RESULT The tabs' text does not fade when the window becomes inactive EXPECTED RESULT The text should fade ADDITIONAL INFORMATION Discovered while working on https://phabricator.kde.org/T10201 SOFTWARE/OS VERSIONS Everything from git master -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 408191] Sidebar text is always considered "inactive" from the perspective of applying inactive window effects
https://bugs.kde.org/show_bug.cgi?id=408191 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=408187 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 408187] Sidebar text is always considered "inactive" from the perspective of applying inactive window effects
https://bugs.kde.org/show_bug.cgi?id=408187 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=408191 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 408191] New: Sidebar text is always considered "inactive" from the perspective of applying inactive window effects
https://bugs.kde.org/show_bug.cgi?id=408191 Bug ID: 408191 Summary: Sidebar text is always considered "inactive" from the perspective of applying inactive window effects Product: Discover Version: 5.15.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: n...@kde.org CC: aleix...@kde.org Target Milestone: --- Created attachment 120486 --> https://bugs.kde.org/attachment.cgi?id=120486=edit Always-faded sidebar text STEPS TO REPRODUCE 1. Go to System Settings > Colors 2. Edit the current color scheme 3. Check "Apply Inactive window effects" 4. Go to the "inactive" tab, change "Contrast" to "Fade" and move the slider a ways to the right 5. Open Discover OBSERVED RESULT The sidebar text is always faded no matter if the window is inactive or not EXPECTED RESULT The text should only be faded when the window is inactive ADDITIONAL INFORMATION Found while working on https://phabricator.kde.org/T10201 System Settings has the same problem: Bug 408187 SOFTWARE/OS VERSIONS Everything from git master -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 408179] Alternative initialisation? The properly patched Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend still hungs forever
https://bugs.kde.org/show_bug.cgi?id=408179 --- Comment #27 from Nikita Sirgienko --- What about cantor_juliaserver process? Is he alive, when Cantor starts hanging on "Calculation"? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408190] New: Inactive window effects do not apply to side toolbar
https://bugs.kde.org/show_bug.cgi?id=408190 Bug ID: 408190 Summary: Inactive window effects do not apply to side toolbar Product: okular Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: n...@kde.org Target Milestone: --- Created attachment 120485 --> https://bugs.kde.org/attachment.cgi?id=120485=edit Side toolbar text does not fade STEPS TO REPRODUCE 1. Go to System Settings > Colors 2. Edit the current color scheme 3. Check "Apply Inactive window effects" 4. Go to the "inactive" tab, change "Contrast" to "Fade" and move the slider a ways to the right 5. Open Okular and then make the window inactive OBSERVED RESULT The left side toolbar's text does not fade when the window becomes inactive EXPECTED RESULT The text should fade ADDITIONAL INFORMATION Discovered while working on https://phabricator.kde.org/T10201 SOFTWARE/OS VERSIONS Everything from git master -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407704] [sddm-theme] There is no spacing between action button labels
https://bugs.kde.org/show_bug.cgi?id=407704 Filip Fila changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://cgit.kde.org/plasma ||-workspace.git/commit/?id=a ||4bcb11bc2f1d12dfb016cd00ab3 ||18fc4b85ca2f -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408189] New: Inactive window effects do not apply to tab text
https://bugs.kde.org/show_bug.cgi?id=408189 Bug ID: 408189 Summary: Inactive window effects do not apply to tab text Product: konsole Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: font Assignee: konsole-de...@kde.org Reporter: n...@kde.org Target Milestone: --- Created attachment 120484 --> https://bugs.kde.org/attachment.cgi?id=120484=edit Tab bar text not fading STEPS TO REPRODUCE 1. Go to System Settings > Colors 2. Edit the current color scheme 3. Check "Apply Inactive window effects" 4. Go to the "inactive" tab, change "Contrast" to "Fade" and move the slider a ways to the right 5. Open Konsole and add more tabs OBSERVED RESULT The tabs' text does not fade when the window becomes inactive EXPECTED RESULT The text should fade ADDITIONAL INFORMATION This is a blocker for https://phabricator.kde.org/T10201 The fading effect works with standard Qt tab bars in Dolphin and Okular, so I think it's an issue specific to Konsole rather than a generic issue with applying the effect to a QTabBar. SOFTWARE/OS VERSIONS Everything from git master -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 408179] Alternative initialisation? The properly patched Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend still hungs forever
https://bugs.kde.org/show_bug.cgi?id=408179 --- Comment #26 from Nikita Sirgienko --- Well, looks the problem appears after login in first expression evaluation. Intresting. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 408188] New: Make it easier to resize a window via mouse / Usability
https://bugs.kde.org/show_bug.cgi?id=408188 Bug ID: 408188 Summary: Make it easier to resize a window via mouse / Usability Product: frameworks-kwindowsystem Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: off...@mikemitterer.at Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Try to resize a window without using a cryptic key-combination - use just the mouse 2. 3. OBSERVED RESULT Very hard - you need to fiddle around the window border to find the invisible, one pixel line that lets you grab the border to resize the windows EXPECTED RESULT Set the tolerance for the "grab"-Area higher SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.15 ADDITIONAL INFORMATION I think you have a strong focus on usability. This problem should be really on top of your list. It should not be necessary to know the keyboard shortcut to resize a window Thanks -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 408187] New: Sidebar text is always considered "inactive" from the perspective of applying inactive window effects
https://bugs.kde.org/show_bug.cgi?id=408187 Bug ID: 408187 Summary: Sidebar text is always considered "inactive" from the perspective of applying inactive window effects Product: systemsettings Version: 5.14.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: sidebarview Assignee: notm...@gmail.com Reporter: n...@kde.org Target Milestone: --- Created attachment 120483 --> https://bugs.kde.org/attachment.cgi?id=120483=edit System Settings sidebar faded text when the window is active STEPS TO REPRODUCE 1. Go to System Settings > Colors 2. Edit the current color scheme 3. Check "Apply Inactive window effects" 4. Go to the "inactive" tab, change "Contrast" to "Fade" and move the slider a ways to the right 5. Open System Settings OBSERVED RESULT The sidebar text is always faded no matter if the window is inactive or not EXPECTED RESULT The text should only be faded when the window is inactive SOFTWARE/OS VERSIONS Everything from git master -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 408179] Alternative initialisation? The properly patched Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend still hungs forever
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #25 from vialav ---
Your suggestion was timely:
My system has exported:
QT_LOGGING_RULES=*.debug=false
But that was meant essentially to preserve the only debug output. It puzzles me
what the 'debug' output was that or it wasn't.
Unsetting QT_LOGGING_RULES started to produce the desired [non-debug?] output:
─── Output/messages
───
Invalid Context= "stock" line for icon theme:
"/usr/share/icons/ubuntu-mono-dark/stock/16/"
Invalid Context= "stock" line for icon theme:
"/usr/share/icons/ubuntu-mono-dark/stock/22/"
Invalid Context= "stock" line for icon theme:
"/usr/share/icons/ubuntu-mono-dark/stock/24/"
Invalid Context= "stock" line for icon theme:
"/usr/share/icons/ubuntu-mono-dark/stock/32/"
Invalid Context= "stock" line for icon theme:
"/usr/share/icons/ubuntu-mono-dark/stock/48/"
Invalid Context= "stock" line for icon theme:
"/usr/share/icons/ubuntu-mono-dark/stock/64/"
Invalid Context= "stock" line for icon theme:
"/usr/share/icons/ubuntu-mono-dark/stock/128/"
dir: "/usr/lib/x86_64-linux-gnu/qt5/plugins/cantor/backends"
Creating MaximaBackend
Creating NullBackend
Creating PythonBackend
Creating PythonBackend
Creating RBackend
Creating SageBackend
Creating ScilabBackend
dir: "/usr/bin/cantor/backends"
"Julia" true true
"KAlgebra" true true
"Lua" true true
"Maxima" true true
"nullbackend" false true
"Octave" true true
"Python 2" true true
"Python 3" true true
"Qalculate" true true
"R" true true
"Sage" true true
"Scilab" true true
Backend "Julia" offers extensions: ("VariableManagementExtension",
"PackagingExtension", "PlotExtension", "ScriptExtension",
"LinearAlgebraExtension")
JuliaSession(0x4abe20) Cantor::VariableManagementExtension(0x95f800, name =
"VariableManagementExtension")
new worksheetaccess interface
loading assistants...
dir: "/usr/lib/x86_64-linux-gnu/qt5/plugins/cantor/assistants"
plugin "AdvancedPlot" is not supported by "Julia"
plugin "Create Matrix" is supported by "Julia" , requires extensions
("LinearAlgebraExtension")
plugin "Differentiate" is not supported by "Julia"
plugin "Eigenvalues" is not supported by "Julia"
plugin "Eigenvectors" is not supported by "Julia"
plugin "Import Package" is supported by "Julia" , requires extensions
("PackagingExtension")
plugin "Integrate" is not supported by "Julia"
plugin "Invert Matrix" is not supported by "Julia"
plugin "Plot2d" is supported by "Julia" , requires extensions
("PlotExtension")
plugin "Plot3d" is supported by "Julia" , requires extensions
("PlotExtension")
plugin "QalculatePlot" is not supported by "Julia"
plugin "RunScript" is supported by "Julia" , requires extensions
("ScriptExtension")
plugin "Solve" is not supported by "Julia"
dir: "/usr/bin/cantor/assistants"
loading panel plugins for session of type "Julia"
dir: "/usr/lib/x86_64-linux-gnu/qt5/plugins/cantor/panels"
plugin "Help" is supported, requires extensions ("")
plugin "Variable Manager" is supported, requires extensions
("VariableManagementExtension")
dir: "/usr/bin/cantor/panels"
Entry Appended
adding panel for "Help"
adding panel for "Variable Manager" # here I've entered 1+1 and pressed
Shift+Enter -->
ShortcutOverride 16777220 QFlags(ShiftModifier)
[Detaching after fork from child process 24404]
wsStatusChange 1
login to julia 1.2.0-rc1 done
wsStatusChange 0
# (process is hanging on "Calculating…"; next I click File -> Exit):
Thread 1 "cantor" received signal SIGSEGV, Segmentation fault.
0x in ?? ()
─── Assembly
──
Cannot access memory at address 0x0
─── Expressions
───
─── History
───
─── Memory
─── Registers
─
rax 0xrbx 0x00e1d1c0rcx 0x7fffbe20
rdx 0x7774f440rsi 0x7fffbe70rdi 0x0050e600
[KXStitch] [Bug 407875] Save/load file in KXStitch is not working properly.
https://bugs.kde.org/show_bug.cgi?id=407875 --- Comment #4 from Milan Steklý --- So how to solve the problem as a regular user: -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 408155] Workflow improvement : simply drag & drop pictures from Thumbnail to Map area
https://bugs.kde.org/show_bug.cgi?id=408155 IWBR changed: What|Removed |Added CC||iwannaber...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 408179] Alternative initialisation? The properly patched Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend still hungs forever
https://bugs.kde.org/show_bug.cgi?id=408179 --- Comment #24 from vialav --- ok, thanks for a hint As a sidenote: No, it is not the way I've got the source. Following the standard procedure of 'git-cloning' (with no merging), and compiling with clang-9 in this last case (with full debug on), then File -> Exit after the Julia session hangs up, all with gdb and debug symbols (and full absence of the Qt-debug output): ─── Output/messages ─── Invalid Context= "stock" line for icon theme: "/usr/share/icons/ubuntu-mono-dark/stock/16/" Invalid Context= "stock" line for icon theme: "/usr/share/icons/ubuntu-mono-dark/stock/22/" Invalid Context= "stock" line for icon theme: "/usr/share/icons/ubuntu-mono-dark/stock/24/" Invalid Context= "stock" line for icon theme: "/usr/share/icons/ubuntu-mono-dark/stock/32/" Invalid Context= "stock" line for icon theme: "/usr/share/icons/ubuntu-mono-dark/stock/48/" Invalid Context= "stock" line for icon theme: "/usr/share/icons/ubuntu-mono-dark/stock/64/" Invalid Context= "stock" line for icon theme: "/usr/share/icons/ubuntu-mono-dark/stock/128/" [Detaching after fork from child process 21264] Thread 1 "cantor" received signal SIGSEGV, Segmentation fault. 0x in ?? () ─── Assembly ── Cannot access memory at address 0x0 ─── Expressions ─── ─── History ─── ─── Memory ─── Registers ─ rax 0xrbx 0x00e24eb0rcx 0x7fffbdf0 rdx 0x7774f440rsi 0x7fffbe40rdi 0x005f7380 rbp 0x7fffbde0rsp 0x7fffbce8 r8 0x r9 0x0006r10 0x r11 0x0004r12 0x005f7380r13 0x00e00a70 r14 0x00c4aaf0r15 0x767cc360 rip 0x eflags [ IF RF ] cs 0x0033 ss 0x002b ds 0x es 0x fs 0x gs 0x ─── Source ─── Stack ─ [0] from 0x (no arguments) [1] from 0x7633b77f in QMetaObject::activate(QObject*, int, int, void**) (no arguments) [+] ─── Threads ─── [6] id 21260 name cantor:disk$0 from 0x75c7a3bb in futex_wait_cancelable+27 at ../sysdeps/unix/sysv/linux/futex-internal.h:88 [5] id 21257 name QDBusConnection from 0x75da3ba9 in __GI___poll+73 at ../sysdeps/unix/sysv/linux/poll.c:29 [4] id 21256 name gdbus from 0x75da3ba9 in __GI___poll+73 at ../sysdeps/unix/sysv/linux/poll.c:29 [3] id 21255 name gmain from 0x75da3ba9 in __GI___poll+73 at ../sysdeps/unix/sysv/linux/poll.c:29 [2] id 21251 name QXcbEventReader from 0x75da3ba9 in __GI___poll+73 at ../sysdeps/unix/sysv/linux/poll.c:29 [1] id 21244 name cantor from 0x ─── >>> >>> bt #0 0x in () #1 0x7633b77f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x77c863f5 in KParts::Part::setStatusBarText(QString
[cantor] [Bug 408179] Alternative initialisation? The properly patched Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend still hungs forever
https://bugs.kde.org/show_bug.cgi?id=408179 --- Comment #23 from Nikita Sirgienko --- Arg, I remembered, that a few years ago, I need to change system qt policy, because Debian (and Ubuntu too) had starts suppress qt debug messages. See https://bugzilla.redhat.com/show_bug.cgi?id=1227295, I think Cantor is actually builded in debug mode, but OS supress all debug messages. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 408179] Alternative initialisation? The properly patched Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend still hungs forever
https://bugs.kde.org/show_bug.cgi?id=408179 --- Comment #22 from vialav --- So, it is, likely, how I've got a source?… with clang-9: #0 0x in () #1 0x7633b77f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x77c863f5 in KParts::Part::setStatusBarText(QString const&) () at /usr/lib/x86_64-linux-gnu/libKF5Parts.so.5 #3 0x7fffc659717f in CantorPart::setStatusMessage(QString const&) (this=0xcabc50, message=...) at ./src/cantor_part.cpp:947 #4 0x7fffc659717f in CantorPart::worksheetStatusChanged(Cantor::Session::Status) (this=0xcabc50, status=) at ./src/cantor_part.cpp:595 #5 0x7fffc6587497 in CantorPart::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x5b4a20, _c=, _id=, _a=0x7fffbdf0) at ./obj-x86_64-linux-gnu/src/cantorpart_autogen/EWIEGA46WW/moc_cantor_part.cpp:209 #6 0x7633b665 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x77cf7dfc in Cantor::Session::statusChanged(Cantor::Session::Status) (this=0x5b4a20, _t1=) at ./obj-x86_64-linux-gnu/src/lib/cantorlibs_autogen/EWIEGA46WW/moc_session.cpp:164 #8 0x7fffdb2602b7 in JuliaSession::interrupt() (this=0xc882f0) at ./src/backends/julia/juliasession.cpp:158 #9 0x7fffdb25ffad in JuliaSession::logout() (this=0xc882f0) at ./src/backends/julia/juliasession.cpp:133 #10 0x7fffc659cf11 in Worksheet::~Worksheet() (this=0xca6cf0) at ./src/worksheet.cpp:107 #11 0x7fffc659d069 in Worksheet::~Worksheet() (this=0xca6cf0) at ./src/worksheet.cpp:101 #12 0x7633924b in QObjectPrivate::deleteChildren() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x770c4d5c in QWidget::~QWidget() () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x770c4f99 in QWidget::~QWidget() () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7633924b in QObjectPrivate::deleteChildren() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x770c4d5c in QWidget::~QWidget() () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x772343b9 in QStackedWidget::~QStackedWidget() () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7633924b in QObjectPrivate::deleteChildren() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x770c4d5c in QWidget::~QWidget() () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x772552a9 in QTabWidget::~QTabWidget() () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7633924b in QObjectPrivate::deleteChildren() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x770c4d5c in QWidget::~QWidget() () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x77b4ea14 in KMainWindow::~KMainWindow() () at /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #24 0x0040d710 in CantorShell::~CantorShell() (this=0x5b4a20) at ./obj-x86_64-linux-gnu/src/cantor_autogen/EWIEGA46WW/../../../../src/cantor.h:56 #25 0x0040d710 in CantorShell::~CantorShell() (this=0x5b4a20) at ./obj-x86_64-linux-gnu/src/cantor_autogen/EWIEGA46WW/../../../../src/cantor.h:56 #26 0x7633c1f0 in QObject::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x770c975b in QWidget::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x771dcc6b in QMainWindow::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #29 0x77b50feb in KMainWindow::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #30 0x77b9d147 in KXmlGuiWindow::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #31 0x7708a83c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #32 0x77092104 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #33 0x7630c9e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x7630f15d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #35 0x76366373 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #36 0x72d20417 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #37 0x72d20650 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #38 0x72d206dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #39 0x7636599f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #40 0x7630aa1a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #41 0x76313ac4 in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #42 0x0040fb02 in main(int, char**) (argc=, argv=) at ./src/main.cpp:156 -- You are receiving this mail because: You
[plasmashell] [Bug 407654] Text in Gtk apps is not antialiased on wayland
https://bugs.kde.org/show_bug.cgi?id=407654 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #5 from David Edmundson --- >Installing 'gnome-settings-daemon' and its dependencies solves this issue for >me. That's crucial info, please take this to the gnome tracker with that. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 408179] Alternative initialisation? The properly patched Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend still hungs forever
https://bugs.kde.org/show_bug.cgi?id=408179
--- Comment #21 from vialav ---
Might it be a compiler (gcc-9 in my case, I may try it with clang)? I turned
off all the optimizations, hardening, and explicitly requested
export DEB_BUILD_MAINT_OPTIONS = noopt
… -DCMAKE_BUILD_TYPE=debug
Running Cantor with gdb and debug symbols {all compiled with commented out the
line "add_definitions(-DQT_NO_DEBUG_OUTPUT)"} did not change the output.
Clicking File -> Exit after trying to start Julia session (hanged in the air),
I've caught up, possibly unrelated, a SIGSEGV:
─── Output/messages
───
Invalid Context= "stock" line for icon theme:
"/usr/share/icons/ubuntu-mono-dark/stock/16/"
Invalid Context= "stock" line for icon theme:
"/usr/share/icons/ubuntu-mono-dark/stock/22/"
Invalid Context= "stock" line for icon theme:
"/usr/share/icons/ubuntu-mono-dark/stock/24/"
Invalid Context= "stock" line for icon theme:
"/usr/share/icons/ubuntu-mono-dark/stock/32/"
Invalid Context= "stock" line for icon theme:
"/usr/share/icons/ubuntu-mono-dark/stock/48/"
Invalid Context= "stock" line for icon theme:
"/usr/share/icons/ubuntu-mono-dark/stock/64/"
Invalid Context= "stock" line for icon theme:
"/usr/share/icons/ubuntu-mono-dark/stock/128/"
[Detaching after fork from child process 5601]
Thread 1 "cantor" received signal SIGSEGV, Segmentation fault.
0x in ?? ()
─── Assembly
──
Cannot access memory at address 0x0
─── Expressions
───
─── History
───
─── Memory
─── Registers
─
rax 0xrbx 0x55f77fd0rcx 0x7fffbca0
rdx 0x7774d440rsi 0x7fffbcd8rdi 0x556f3dd0
rbp 0x7fffbc90rsp 0x7fffbb98
r8 0x r9 0x0004r10 0x
r11 0x0004r12 0x556f3dd0r13 0x55f63460
r14 0x55da8b50r15 0x767ca160
rip 0x eflags [ IF RF ] cs 0x0033
ss 0x002b ds 0x es 0x
fs 0x gs 0x
─── Source
─── Stack
─
[0] from 0x
(no arguments)
[1] from 0x7633977f in QMetaObject::activate(QObject*, int, int,
void**)
(no arguments)
[+]
─── Threads
───
[6] id 5591 name cantor:disk$0 from 0x75c783bb in
futex_wait_cancelable+27 at ../sysdeps/unix/sysv/linux/futex-internal.h:88
[5] id 5589 name QDBusConnection from 0x75da1ba9 in __GI___poll+73 at
../sysdeps/unix/sysv/linux/poll.c:29
[4] id 5588 name gdbus from 0x75da1ba9 in __GI___poll+73 at
../sysdeps/unix/sysv/linux/poll.c:29
[3] id 5587 name gmain from 0x75da1ba9 in __GI___poll+73 at
../sysdeps/unix/sysv/linux/poll.c:29
[2] id 5586 name QXcbEventReader from 0x75da1ba9 in __GI___poll+73 at
../sysdeps/unix/sysv/linux/poll.c:29
[1] id 5581 name cantor from 0x
───
>>> backtrace
#0 0x in ()
#1 0x7633977f in
[kstars] [Bug 405325] Meridian flip if HA>
https://bugs.kde.org/show_bug.cgi?id=405325 Wolfgang Reissenberger changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #19 from Wolfgang Reissenberger --- Yepp, the fix is part of the 3.2.0 release. So maybe you are facing another problem. Please report your problem to the INDI forum https://indilib.org/forum/ - Wolfgang -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 405325] Meridian flip if HA>
https://bugs.kde.org/show_bug.cgi?id=405325 Jean-Claude changed: What|Removed |Added Version|3.1.0 |3.2.3 OS|Linux |macOS --- Comment #18 from Jean-Claude --- Wolfgang, did you correct that bug ? I'm running v.3.2.3 and my mount Celestron CGE Pro doesn't flip when the target crosses the meridian. My mount uses a Nexstar+ hand control; I tried all possible settings in the Meridian menu to no avail. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 378364] Sequence number options need date-aware modifier
https://bugs.kde.org/show_bug.cgi?id=378364 Tom Cunningham changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #6 from Tom Cunningham --- I'm closing this out because, based on my 2019-02 comment and my discovery of a "Date Folder" option on my most recent camera, it appears that digiKam is performing correctly. After switching to Date Folders on the camera, digiKam is creating corresponding folders on the host and resetting the sequence numbers in each one, as expected. In my camera's normal folder mode, the camera would put all pictures, regardless of date, into one folder. DigiKam would then break these out into date-based folders on the host, but would not reset the sequence number, since the input folder was the same for all photos. I now realize that folder-aware numbering is associated with input file renaming, whereas date-based folder creation is associated with sub-album creation; I had the two conflated somehow. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 408031] Plasma 5.16 Notifications - Button hover tooltip shows erroneous ampersand
https://bugs.kde.org/show_bug.cgi?id=408031 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |DUPLICATE CC||k...@privat.broulik.de Status|REPORTED|RESOLVED --- Comment #1 from Kai Uwe Broulik --- *** This bug has been marked as a duplicate of bug 407853 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407853] Extra ampersand in tooltip text on 'configure' button in Notifications plasmoid
https://bugs.kde.org/show_bug.cgi?id=407853 Kai Uwe Broulik changed: What|Removed |Added CC||esa1...@gmail.com --- Comment #2 from Kai Uwe Broulik --- *** Bug 408031 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 407372] Need help-donate-[currency] icons
https://bugs.kde.org/show_bug.cgi?id=407372 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408180] Support additional org.freedesktop.Notifications capabilities
https://bugs.kde.org/show_bug.cgi?id=408180 --- Comment #2 from Thaodan --- I understand but the spec is used also by apps that are not from us. At least the sound part seems pretty easy. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 390550] Can't resize windows due to no borders
https://bugs.kde.org/show_bug.cgi?id=390550 Felix Miata changed: What|Removed |Added CC||mrma...@earthlink.net -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 408179] Alternative initialisation? The properly patched Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend still hungs forever
https://bugs.kde.org/show_bug.cgi?id=408179 --- Comment #20 from vialav --- Ok, because compiling with the only flag: # see FEATURE AREAS in dpkg-buildflags(1) export DEB_BUILD_MAINT_OPTIONS = hardening=+all …I've got essentially the same results, again, then it must me the main suspect. Removing it, and re-compiling, again. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 408179] Alternative initialisation? The properly patched Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend still hungs forever
https://bugs.kde.org/show_bug.cgi?id=408179 --- Comment #19 from vialav --- I'm turning all the optimization off, commenting out, and will post the result. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 408179] Alternative initialisation? The properly patched Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend still hungs forever
https://bugs.kde.org/show_bug.cgi?id=408179 --- Comment #18 from Nikita Sirgienko --- (In reply to vialav from comment #16) > #(so, CMAKE_BUILD_TYPE only once and Debug, but what the heck where is the > output…) Strange, I recommend go to CMakeLists.txt, found the line "add_definitions(-DQT_NO_DEBUG_OUTPUT)" and comment it. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 408179] Alternative initialisation? The properly patched Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend still hungs forever
https://bugs.kde.org/show_bug.cgi?id=408179 --- Comment #17 from Nikita Sirgienko --- (In reply to vialav from comment #16) > Ok, that 'None' did come from Debian 'automagic', I didn't set it on > purpose. However, the second (for me the only one) -DCMAKE_BUILD_TYPE=debug > shadows (rewrites anew) ehm… the CMAKE_BUILD_TYPE, so, it shall be the Debug > build in the result (even *debug.cmake hints on this). I had tested that happends, if cmake got two CMAKE_BUILD_TYPE (even second is 'debug'). With two definitions Cantor don't produced debug output. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408149] Selection Transformation not available via Selection Tool.
https://bugs.kde.org/show_bug.cgi?id=408149 --- Comment #11 from Boudewijn Rempt --- I agree with Scott. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 408186] New: Extracting archive into directory with 'tab' in the name.
https://bugs.kde.org/show_bug.cgi?id=408186 Bug ID: 408186 Summary: Extracting archive into directory with 'tab' in the name. Product: dolphin Version: 19.04.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: o...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- By 'tab' I mean \t. E.g. 'ddd ccc' Extracting archive into directory with \t in its name by submenu 'Extract to' - extracts into the directory with archive. Extracting by drug-and-drop into a dir with \t in its name - archive gets extracted into ~/ SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux lom 5.1.4-arch1-1-ARCH x86_64 GNU/Linux KDE Frameworks Version: 5.58.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 408179] Alternative initialisation? The properly patched Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend still hungs forever
https://bugs.kde.org/show_bug.cgi?id=408179 --- Comment #16 from vialav --- Ok, that 'None' did come from Debian 'automagic', I didn't set it on purpose. However, the second (for me the only one) -DCMAKE_BUILD_TYPE=debug shadows (rewrites anew) ehm… the CMAKE_BUILD_TYPE, so, it shall be the Debug build in the result (even *debug.cmake hints on this). And here is how I've got the source : git clone --recurse-submodules git://anongit.kde.org/cantor.git git checkout origin/Applications/19.04 git merge master # resolve a trivial merge conflict in CMakeLists.txt (set a version) # build as in the attached log #my **naive** debian/rules universal template: #!/usr/bin/make -f # see FEATURE AREAS in dpkg-buildflags(1) export DEB_BUILD_MAINT_OPTIONS = hardening=+all export DEB_CFLAGS_MAINT_APPEND := -fopenmp -mtune=native -O3 -fPIC -flto=jobserver -flto-compression-level=9 -funroll-loops -DMKL_LP64 -DM_PI=3.1415926535897932384 -I/usr/include/mkl export DEB_CXXFLAGS_MAINT_APPEND := $(DEB_CFLAGS_MAINT_APPEND) export DEB_CPPFLAGS_MAINT_APPEND := $(DEB_CFLAGS_MAINT_APPEND) export DEB_FFLAGS_MAINT_APPEND := -fopenmp -mtune=native -O3 -fPIC -ffree-line-length-0 export DEB_FCFLAGS_MAINT_APPEND = $(DEB_FFLAGS_MAINT_APPEND) export DEB_LDFLAGS_MAINT_APPEND := -fPIC -Wl,--start-group -lmkl_gf_lp64 -lmkl_gnu_thread -lmkl_core -Wl,--end-group -lgomp -lpthread -lm -ldl # the last line is for compiling with IntelMKL override_dh_auto_configure: $(overridden_command) -- -DBUILD_TESTING=OFF -DJULIA_EXECUTABLE=/usr/bin/julia -DCMAKE_BUILD_TYPE=debug #(so, CMAKE_BUILD_TYPE only once and Debug, but what the heck where is the output…) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 407822] subsequent ZModem upload failed to launch if cancel file dialog
https://bugs.kde.org/show_bug.cgi?id=407822 --- Comment #3 from Kurt Hindenburg --- Well this was committed to a branch and I didn't realize it would close this. It will be committed to master shortly -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 407822] subsequent ZModem upload failed to launch if cancel file dialog
https://bugs.kde.org/show_bug.cgi?id=407822 Kurt Hindenburg changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/kde/ ||konsole/commit/0509982a7cd1 ||78ac774a75a000af82ebf268885 ||5 Version Fixed In||19.08.00 --- Comment #1 from Kurt Hindenburg --- Git commit 0509982a7cd178ac774a75a000af82ebf2688855 by Kurt Hindenburg. Committed on 01/06/2019 at 18:50. Pushed by hindenburg into branch 'BR407822'. Remove unneeded setZModemBusy(true) _zmodemBusy is set to true in startZModem() so there's no need to set it before. FIXED-IN: 19.08.00 M +0-1src/SessionController.cpp https://invent.kde.org/kde/konsole/commit/0509982a7cd178ac774a75a000af82ebf2688855 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 407822] subsequent ZModem upload failed to launch if cancel file dialog
https://bugs.kde.org/show_bug.cgi?id=407822 Kurt Hindenburg changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://commits.kde.org/kon |konsole/commit/0509982a7cd1 |sole/0509982a7cd178ac774a75 |78ac774a75a000af82ebf268885 |a000af82ebf2688855 |5 | --- Comment #2 from Kurt Hindenburg --- Git commit 0509982a7cd178ac774a75a000af82ebf2688855 by Kurt Hindenburg. Committed on 01/06/2019 at 18:50. Pushed by scmsync into branch 'BR407822'. Remove unneeded setZModemBusy(true) _zmodemBusy is set to true in startZModem() so there's no need to set it before. FIXED-IN: 19.08.00 M +0-1src/SessionController.cpp https://commits.kde.org/konsole/0509982a7cd178ac774a75a000af82ebf2688855 -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 408179] Alternative initialisation? The properly patched Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend still hungs forever
https://bugs.kde.org/show_bug.cgi?id=408179 --- Comment #15 from Nikita Sirgienko --- (In reply to vialav from comment #14) > There is nothing useful in the output, when I log in into julia (btw, what > 'log in' means in this context? I simply [tried to] started the julia > session, which produced no output there): Your cmake command (below) set CMAKE_BUILD_TYPE twice (first as None) so Cantor not builded in debug mode. When Cantor will builded in debug mode, you should see a lot of output in console. Could you please rebuild Cantor? cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_BUILD_TYPE=Debian -DCMAKE_INSTALL_SYSCONFDIR=/etc -DKDE_INSTALL_USE_QT_SYS_PATHS=ON -DBUILD_TESTING=OFF -DJULIA_EXECUTABLE=/usr/bin/julia -DCMAKE_BUILD_TYPE=debug .. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408164] Krita is closed suddenly
https://bugs.kde.org/show_bug.cgi?id=408164 --- Comment #3 from Boudewijn Rempt --- So, please add the information I asked for. Right now, it's impossible to know whether there's something broken on your system, or in krita. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 408185] New: While closing one of two samba windows opened, the backmost crashed
https://bugs.kde.org/show_bug.cgi?id=408185 Bug ID: 408185 Summary: While closing one of two samba windows opened, the backmost crashed Product: dolphin Version: 17.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: s.fos...@protonmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (17.12.3) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.18.0-20-generic x86_64 Distribution: Ubuntu 18.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: I was exploring one single password protected samba share with two windows opened in different folders. Before, the two windows was minimized and hovering the folder icon in the bottom bar showed me the grayed preview selection of the two. Hovering one of the two windows, the red close options showed. Clicking on the red x to close one dolphin crashed -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff26170f6c0 (LWP 26255))] Thread 2 (Thread 0x7ff243df5700 (LWP 26257)): #0 0x7ff260f92bf9 in __GI___poll (fds=0x7ff23c01a740, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7ff253eed5c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff253eed6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff25b1a69bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7ff25b14ba1a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff25af6a23a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ff25b623d45 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7ff25af6f17d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ff25605f6db in start_thread (arg=0x7ff243df5700) at pthread_create.c:463 #9 0x7ff260f9f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7ff26170f6c0 (LWP 26255)): [KCrash Handler] #6 0x55a8adbc0200 in () #7 0x7ff25cff0606 in () at /usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5 #8 0x7ff25cff06a9 in () at /usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5 #9 0x7ff25b17a24b in QObjectPrivate::deleteChildren() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7ff25b183a7b in QObject::~QObject() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7ff25cfca579 in () at /usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5 #12 0x7ff260ec1041 in __run_exit_handlers (status=0, listp=0x7ff261269718 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108 #13 0x7ff260ec113a in __GI_exit (status=) at exit.c:139 #14 0x7ff260e9fb9e in __libc_start_main (main=0x55a8ac2ed730, argc=2, argv=0x7ffdf1559e88, init=, fini=, rtld_fini=, stack_end=0x7ffdf1559e78) at ../csu/libc-start.c:344 #15 0x55a8ac2ed76a in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408180] Support additional org.freedesktop.Notifications capabilities
https://bugs.kde.org/show_bug.cgi?id=408180 Kai Uwe Broulik changed: What|Removed |Added Severity|normal |wishlist --- Comment #1 from Kai Uwe Broulik --- For persistence we have status notifier items and for sound we typically have the app play it. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 408179] Alternative initialisation? The properly patched Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend still hungs forever
https://bugs.kde.org/show_bug.cgi?id=408179 --- Comment #14 from vialav --- I did everything as being told, and there is no difference in the end result… Usually I don't need to set JULIA_EXECUTABLE, as it is in the default path: -DJULIA_EXECUTABLE=/usr/bin/julia > Also, it's helpfull, if you will build debug cantor version and post Cantor > debug output here, when your tried to login into julia. There is nothing useful in the output, when I log in into julia (btw, what 'log in' means in this context? I simply [tried to] started the julia session, which produced no output there): $ cantor Invalid Context= "stock" line for icon theme: "/usr/share/icons/ubuntu-mono-dark/stock/16/" Invalid Context= "stock" line for icon theme: "/usr/share/icons/ubuntu-mono-dark/stock/22/" Invalid Context= "stock" line for icon theme: "/usr/share/icons/ubuntu-mono-dark/stock/24/" Invalid Context= "stock" line for icon theme: "/usr/share/icons/ubuntu-mono-dark/stock/32/" Invalid Context= "stock" line for icon theme: "/usr/share/icons/ubuntu-mono-dark/stock/48/" Invalid Context= "stock" line for icon theme: "/usr/share/icons/ubuntu-mono-dark/stock/64/" Invalid Context= "stock" line for icon theme: "/usr/share/icons/ubuntu-mono-dark/stock/128/" That it was indeed, the debug version, is that I've got the CantorTargets-debug.cmake file instead of CantorTargets-debin.cmake -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407077] Composite and transform parameters (and also geometry) are taken from other clip.
https://bugs.kde.org/show_bug.cgi?id=407077 emohr changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |WORKSFORME --- Comment #10 from emohr --- I think this confuses other users as well. I track this bug with a similar issue: https://bugs.kde.org/show_bug.cgi?id=408081 We close this bug. If it still appears in the latest version, please feel free to re-open it and update the affected version number. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 408179] Alternative initialisation? The properly patched Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend still hungs forever
https://bugs.kde.org/show_bug.cgi?id=408179 --- Comment #13 from vialav --- Created attachment 120482 --> https://bugs.kde.org/attachment.cgi?id=120482=edit build log -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 408179] Alternative initialisation? The properly patched Julia v1.1.0/v1.1.1/v1.2.0-rc1 backend still hungs forever
https://bugs.kde.org/show_bug.cgi?id=408179 --- Comment #12 from vialav --- Created attachment 120481 --> https://bugs.kde.org/attachment.cgi?id=120481=edit Calculating… -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408184] New: Bad scaling Krita GUI on Windows 10
https://bugs.kde.org/show_bug.cgi?id=408184 Bug ID: 408184 Summary: Bad scaling Krita GUI on Windows 10 Product: krita Version: 4.2.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: major Priority: NOR Component: OpenGL Canvas Assignee: krita-bugs-n...@kde.org Reporter: kamin...@konto.pl Target Milestone: --- Created attachment 120480 --> https://bugs.kde.org/attachment.cgi?id=120480=edit broken scaling visible on colour whell and icons SUMMARY STEPS TO REPRODUCE 1. open krita 4.20 and make new document 2. look at colour wheel, icons in GUI and layer previews (after mouseover) OBSERVED RESULT Visible, big. problems with scaling GUI. Jagged edges. Problem occurs in windows 10. I use a laptop Acer Aspire 17'' that has a built-in Intel 630 graphics card and Nvidia 1050. it does not matter which graphics processor i use the effect is the same. It might be important, that scaling on my screen is set to 125%. Maybe it is a reason. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: windows 10 ADDITIONAL INFORMATION I do not know if it is connected, but 4.20 drawing with brushes is two times slower than in Krita 4.17. I returned to version 4.17, unfortunately the new is not usable. -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 408183] New: Audio feedback when volume changes
https://bugs.kde.org/show_bug.cgi?id=408183 Bug ID: 408183 Summary: Audio feedback when volume changes Product: kmix Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: KMix Panel Docking Assignee: es...@kde.org Reporter: jan.muss...@gmail.com Target Milestone: --- Created attachment 120479 --> https://bugs.kde.org/attachment.cgi?id=120479=edit Audio volume settings window SUMMARY When I right-click the loudspeaker icon in the panel and choose Configure audio volume, I can choose to have or not to have audio feedback when the volume changes. The text next to the item says however: Provide visual feedback. STEPS TO REPRODUCE 1. See above 2. See attachment Audio volume settings volume picture 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro Linux KDE edition (available in About System) KDE Plasma Version: 5.16.80 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 407822] subsequent ZModem upload failed to launch if cancel file dialog
https://bugs.kde.org/show_bug.cgi?id=407822 Kurt Hindenburg changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 398456] latte-dock takes a lot % of CPU
https://bugs.kde.org/show_bug.cgi?id=398456 Michail Vourlakos changed: What|Removed |Added Resolution|--- |LATER Status|REPORTED|RESOLVED --- Comment #4 from Michail Vourlakos --- this is a wishlist with no metrics and not patches to improve the situation... in the current form is just with no reason. Latte is trying always to reduce its CPU cycles... -- You are receiving this mail because: You are watching all bug changes.
