[krita] [Bug 404284] Krita closes when told to save the document
https://bugs.kde.org/show_bug.cgi?id=404284 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 404310] Maximize Minimize Expand buttons dissapear when maximize any windows even chrome which is gtk I think very weird this
https://bugs.kde.org/show_bug.cgi?id=404310 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.
[konsole] [Bug 398706] Arrow keys: down disabling touchpad, up does not cycle through history
https://bugs.kde.org/show_bug.cgi?id=398706 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 397791] crash and won't open file
https://bugs.kde.org/show_bug.cgi?id=397791 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404224] krita crashes, bug #1, please fix. windows. please fix. 2019
https://bugs.kde.org/show_bug.cgi?id=404224 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 405506] New: Needs specific instructions about how to build from source
https://bugs.kde.org/show_bug.cgi?id=405506 Bug ID: 405506 Summary: Needs specific instructions about how to build from source Product: kdiff3 Version: 1.8.x Platform: unspecified OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: reeves...@gmail.com Reporter: ross.boy...@ucsf.edu Target Milestone: --- SUMMARY Please describe specifically how to build the package from source on Windows or *nix. Ideally this would go in INSTALL; alternately it could go in the README. This would start with a list of prerequisite software, where to obtain it, and whether source or binary versions were necessary. It would then describe environment setup and build steps. DETAILS The current source code (git://anongit.kde.org/kdiff3.git) does not explain in any specific way how to build the package on either Windows (my current concern) or *nix. INSTALL is simply a pointer to the README, which has some general remarks about requirements at the top. The old, specific, instructions were deleted as obsolete, but they haven't been replaced by anything. It doesn't even indicate which specific KF5 frameworks are required. Maybe this is all obvious to those familiar with cmake or KF5, but it's not obvious to me. The old INSTALL recipe of configure; make; make install was "obvious" to those familiar with it, but it was still documented in INSTALL. I'm hoping for something similar. https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source/Windows has been only marginally helpful. Having followed the steps, I'm not even sure if I've completed them properly or not (the last thing was the message Execute: C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\python.exe c:\Users\rdboylan\Documents\src\CraftRoot\craft-master\bin\craft.py craft Please ensure that you have installed the C++ component ). And it was also unclear to me from those instructions whether it would suffice to download the Qt binaries. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 362857] Background transparency not applied when restoring session
https://bugs.kde.org/show_bug.cgi?id=362857 --- Comment #18 from Joe --- So - the idea then would be to let konsole startup/restore (without transparency), and pole (or some other mechanism) kwin and when its ready, restore transparency? Seems reasonable enough, to be honest, as long as the enabling of transparency isn't too jarring. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 404695] Icy Cast metadata received from stream doesn't updates the author correctly
https://bugs.kde.org/show_bug.cgi?id=404695 Myriam Schweingruber changed: What|Removed |Added Version|unspecified |2.9.0 --- Comment #6 from Myriam Schweingruber --- (In reply to Fernando from comment #3) > (In reply to Myriam Schweingruber from comment #1) > > Please update your Amarok version, 2.8.0 is really obsolete. Is this > > reproducible with version 2.9.0? > > Hi Myriam, > > At Debian Buster is not available yet so I installed Kubuntu in VirtualBox, > with same issue. > > I was required to install gstreamer1.0-plugins-bad to be able to listen this > stream ... Could be this library the issue? Most likely not, the plugin is required to actually listen to mp3. I was wondering: did the stream behavior change compared to an earlier version or is this happening only in this particular stream? can it be reproduced with other streams (which would then clearly point to Amarok or one of its dependencies) or is this behavior specific to this stream? Some streams just don't update the metadata correctly, and sadly this happens very often. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 380171] KMail crash on first start
https://bugs.kde.org/show_bug.cgi?id=380171 --- Comment #4 from Rik Mills --- Reproducible here on debian sid/buster. Requires a pristine install with NO config files or db created yet OR after stopping akonadi and doing rm -fr ~/.local/share/akonadi* ~/.cache/akonadi* ~/.config/akonadi* ~/.config/specialmailcollectionsrc then trying. removing ~/.config/specialmailcollectionsrc (which would not exist in pristine install) seems crucial. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 403054] GeoIP.dat.gz
https://bugs.kde.org/show_bug.cgi?id=403054 --- Comment #6 from Glenn McCorkle --- Question: Is anyone @ KDE working to resolve this issue by modifying ktorrent to access the new database instead of the discontinued one ? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380495] Freezes during login process
https://bugs.kde.org/show_bug.cgi?id=380495 --- Comment #7 from George R. Goffe --- I forgot to indicate "my" level of ksplashqml... so here it is: plasma-workspace-5.15.3-1.fc31.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 311045] Search strings should be parsable from the command-line
https://bugs.kde.org/show_bug.cgi?id=311045 Albert Astals Cid changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||aa...@kde.org Resolution|--- |DUPLICATE --- Comment #3 from Albert Astals Cid --- Yes *** This bug has been marked as a duplicate of bug 362038 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 362038] feature request for "find" functionality from console startup (CLI)
https://bugs.kde.org/show_bug.cgi?id=362038 Albert Astals Cid changed: What|Removed |Added CC||comenius...@gmail.com --- Comment #15 from Albert Astals Cid --- *** Bug 311045 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 402397] Okular crashes while trying to re-open already deleted document at startup
https://bugs.kde.org/show_bug.cgi?id=402397 Albert Astals Cid changed: What|Removed |Added CC||k...@equaeghe.nospammail.net --- Comment #1 from Albert Astals Cid --- *** Bug 405502 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 405502] Okular crashes when trying to reopen document on unmounted filesystem
https://bugs.kde.org/show_bug.cgi?id=405502 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Albert Astals Cid --- *** This bug has been marked as a duplicate of bug 402397 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404823] Issue with tty
https://bugs.kde.org/show_bug.cgi?id=404823 Christoph Feck changed: What|Removed |Added Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdemultimedia] [Bug 404897] kdeinit5 crashes all the time
https://bugs.kde.org/show_bug.cgi?id=404897 Christoph Feck changed: What|Removed |Added Latest Commit||https://commits.kde.org/ffm ||pegthumbs/caf68da418658d99f ||a8e48db99b9733ef6697fa3 Resolution|--- |FIXED Version Fixed In||18.12.3 Status|REPORTED|RESOLVED --- Comment #8 from Christoph Feck --- Fixed by Kai Uwe Broulik with commit caf68da418658d99fa8e48db99b9733ef6697fa3 https://commits.kde.org/ffmpegthumbs/caf68da418658d99fa8e48db99b9733ef6697fa3 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 405491] KMail (in Kontact) crashing upon start or shortly after
https://bugs.kde.org/show_bug.cgi?id=405491 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #5 from Christoph Feck --- Crash is in nouveau_dri.so OpenGL driver. Please report this issue directly to nouveau developers. See also https://nouveau.freedesktop.org/wiki/Bugs/ -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 405422] ksudoku live-git (commit 09814312d) small-game generation fails with "Unable to generate a puzzle of the chosen variant"
https://bugs.kde.org/show_bug.cgi?id=405422 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #4 from Albert Astals Cid --- I can generate any game just fine using the current git version of ksudoku + Qt 5.12.1 + KF5 5.56 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 405505] Titlebars of shaded maximized windows are indistinguishable from titlebars of maximized windows underneath them
https://bugs.kde.org/show_bug.cgi?id=405505 Christoph Feck changed: What|Removed |Added Product|kwin|Breeze Component|general |window decoration Version|git master |5.15.3 Assignee|kwin-bugs-n...@kde.org |unassigned-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380495] Freezes during login process
https://bugs.kde.org/show_bug.cgi?id=380495 George R. Goffe changed: What|Removed |Added CC||grgo...@yahoo.com --- Comment #6 from George R. Goffe --- Created attachment 118832 --> https://bugs.kde.org/attachment.cgi?id=118832=edit gzip'd file containing the execution of startkde from my .xinitrc file. Hi, I think I have this same problem with a Fedora Core 31 (rawhide) system. The system is freshly installed and has several rounds of "normal" package upgrades. I have my run level set to 3, a text mode login. After login I issue a startx command which uses my .xinitrc config file which contains " /usr/bin/bash -xv /usr/bin/startkde". Startkde just never ends. I have included output of this .xinitrc script. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 404936] A4 double sided printing of a .pdf doc produces wrong size "images" on even/odd paper.
https://bugs.kde.org/show_bug.cgi?id=404936 Christoph Feck changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #12 from Christoph Feck --- New information was provided; changing status for inspection. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405096] Media Player plasmoid jump +/- 19 second
https://bugs.kde.org/show_bug.cgi?id=405096 --- Comment #5 from Christoph Feck --- New information was provided; changing status for inspection. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405081] Windows contents are not fully rendered when moving to corner
https://bugs.kde.org/show_bug.cgi?id=405081 Christoph Feck changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Christoph Feck --- Information was provided with comment #2; changing status for inspection. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401788] "Scale Image to New Size" - Nearest Neighbor filter generates wrong results while downsampling image
https://bugs.kde.org/show_bug.cgi?id=401788 Curtis Wiseman changed: What|Removed |Added CC||can0bicc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405505] Titlebars of shaded maximized windows are indistinguishable from titlebars of maximized windows underneath them
https://bugs.kde.org/show_bug.cgi?id=405505 --- Comment #1 from Noah Davis --- Created attachment 118831 --> https://bugs.kde.org/attachment.cgi?id=118831=edit Shaded unmaximized Konsole window on top of a maximized Firefox window This is how I think shaded maximized windows should look. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 399282] Random freezes when capturing an area running multiple gpu's
https://bugs.kde.org/show_bug.cgi?id=399282 Christoph Feck changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Christoph Feck --- Thanks for the update; changing status. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405505] New: Titlebars of shaded maximized windows are indistinguishable from titlebars of maximized windows underneath them
https://bugs.kde.org/show_bug.cgi?id=405505 Bug ID: 405505 Summary: Titlebars of shaded maximized windows are indistinguishable from titlebars of maximized windows underneath them Product: kwin Version: git master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: noaha...@gmail.com Target Milestone: --- Created attachment 118830 --> https://bugs.kde.org/attachment.cgi?id=118830=edit Shaded maximized Konsole window on top of a maximized Firefox window SUMMARY There is no visible difference between a shaded maximized window and the titlebar of the maximized window behind it. If all shaded windows were made to cast a shadow, the problem would be fixed. STEPS TO REPRODUCE 1. Put one maximized window in front of another maximized window 2. Shade the top maximized window OBSERVED RESULT The tilebar of the shaded window in front is indistinguishable from the window behind it. EXPECTED RESULT There should be a visible difference between the titlebar of the shaded window and the titlebar of the window behind it. SOFTWARE/OS VERSIONS Linux Distribution: openSUSE Tumbleweed 20190314 KDE Plasma/KWin Version: 5.15.80 (git master) KDE Frameworks Version: 5.57 (git master) Qt Version: 5.12.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399923] Segmentation fault during face detection
https://bugs.kde.org/show_bug.cgi?id=399923 --- Comment #146 from Maik Qualmann --- Git commit abdf66b5c6ba7fc37fec0853db0e08a45b6a3ad3 by Maik Qualmann. Committed on 15/03/2019 at 22:29. Pushed by mqualmann into branch 'master'. Revert "fix big memory allocation failure if rotate DImg" Sorry for noise M +4-4core/libs/dimg/dimg.cpp https://commits.kde.org/digikam/abdf66b5c6ba7fc37fec0853db0e08a45b6a3ad3 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 385189] Save dialog: Return key only bound to Save button when text field has focus
https://bugs.kde.org/show_bug.cgi?id=385189 --- Comment #4 from Patrick Silva --- Bug is still reproducible here. Operating System: Arch Linux KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 405504] New: "st" string in text field is converted to Unicode ligature
https://bugs.kde.org/show_bug.cgi?id=405504
Bug ID: 405504
Summary: "st" string in text field is converted to Unicode
ligature
Product: KBibTeX
Version: 0.8.2
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: User interface
Assignee: fisc...@unix-ag.uni-kl.de
Reporter: glyphi...@gmail.com
Target Milestone: ---
SUMMARY
After entering text containing 1 or more instances of the string "st" into a
field, each instance is converted into the Unicode ligature character 'st'
(U+FB06, decimal 64262,
https://www.fileformat.info/info/unicode/char/fb06/index.htm). For example,
after entering text containing "justice", it appears as "justice", and the
element doesn't appear when filtering on "justice".
STEPS TO REPRODUCE
1. Add a new element, or edit an existing element.
2. Enter the string "st" into any text field.
3. Click on a different tab, or click OK, or change the pulldown menu to
"Source Code" and back to "Plain Text".
OBSERVED RESULT
Each "st" string appears as the Unicode ligature character 'st'. The element
doesn't appear when filtering for "st".
EXPECTED RESULT
Each "st" string appears as "st". The element appears when filtering for "st".
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version: 5.54.0
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3
ADDITIONAL INFORMATION
If you enter "justice" into a text field, then change the dropdown from "Plain
Text" to "Source Code", it appears as "{justice}". That is, there's no
ligature. Possibly "st" is stored correctly, but displayed incorrectly?
Although searching for "st" still fails.
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 399923] Segmentation fault during face detection
https://bugs.kde.org/show_bug.cgi?id=399923 --- Comment #145 from Maik Qualmann --- Git commit e31d8c418b9b334d9aa31d4835e34a0c781ae6f4 by Maik Qualmann. Committed on 15/03/2019 at 22:13. Pushed by mqualmann into branch 'master'. fix big memory allocation failure if rotate DImg M +4-4core/libs/dimg/dimg.cpp https://commits.kde.org/digikam/e31d8c418b9b334d9aa31d4835e34a0c781ae6f4 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 405492] Unable to clear the cache
https://bugs.kde.org/show_bug.cgi?id=405492 --- Comment #1 from Juraj --- SO it turns out Falkon truly is unable to clear its own cache, In the request in dev tools it says > Status Code: 200 (from ServiceWorker) Where can I check / browse things stored in ServiceWorker ? Will Falkon be able to delete ServiceWorker cache soon ? -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 405446] ksplashqml hits its hard timeout of 30 seconds because setStage(6) is needed twice
https://bugs.kde.org/show_bug.cgi?id=405446 Bernhard Übelacker changed: What|Removed |Added Attachment #118782|0 |1 is obsolete|| --- Comment #8 from Bernhard Übelacker --- Comment on attachment 118782 --> https://bugs.kde.org/attachment.cgi?id=118782 ksplashqml: Quit on first call to setStage with stage == 6. Moving the assignment is not correct as there are really 7 stages. -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 405446] ksplashqml hits its hard timeout of 30 seconds because setStage(6) is needed twice
https://bugs.kde.org/show_bug.cgi?id=405446 --- Comment #7 from Bernhard Übelacker --- Hello Kai Uwe Broulik, with the patch from #405444 I now receive that missing "kcminit" stage. Maybe that stage "kcminit" arrives even before the "kinit" and got lost because of the not yet up dbus interface. So this issue might be just closed. Still adding that stage "kcminit" to the comment in splashapp.cpp might be an improvement. Kind regards, Bernhard -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 405446] ksplashqml hits its hard timeout of 30 seconds because setStage(6) is needed twice
https://bugs.kde.org/show_bug.cgi?id=405446 Bernhard Übelacker changed: What|Removed |Added Attachment #118783|0 |1 is obsolete|| --- Comment #6 from Bernhard Übelacker --- Comment on attachment 118783 --> https://bugs.kde.org/attachment.cgi?id=118783 ksplashqml: Add some logging to get details when stages were reached. Better version added to #405444. -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 405444] ksplashqml hits its hard timeout of 30 seconds because of failing qdbus call kinit
https://bugs.kde.org/show_bug.cgi?id=405444 --- Comment #4 from Bernhard Übelacker --- Created attachment 118829 --> https://bugs.kde.org/attachment.cgi?id=118829=edit ksplashqml: Add some logging to get details when stages were reached. -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 405444] ksplashqml hits its hard timeout of 30 seconds because of failing qdbus call kinit
https://bugs.kde.org/show_bug.cgi?id=405444
--- Comment #3 from Bernhard Übelacker ---
Hello Kai Uwe Broulik,
> > Can you give the patch https://phabricator.kde.org/D19753 a try?
> I will rebuild a package with just that change and report back.
I build the package with D19753 applied and the first some boots did not
show these "Cannot find 'org.kde.KSplash.setStage' ..." messages anymore.
Additional I had modified my logging patch and now I also get the
"kcminit" stage even before the "kinit".
Might the "kcminit" also just got lost because the
dbus interface was not yet up?
Kind regards,
Bernhard
2019-03-15 22:34:12.728 SplashApp::setStage("initial")
2019-03-15 22:34:12.728 SplashApp::setStage("initial"): m_stages.count==1
2019-03-15 22:34:12.728 SplashApp::setStage(1), m_stage==0
2019-03-15 22:34:12.803 SplashApp::setStage("kcminit")
2019-03-15 22:34:12.803 SplashApp::setStage("kcminit"): m_stages.count==2
2019-03-15 22:34:12.803 SplashApp::setStage(2), m_stage==1
2019-03-15 22:34:12.811 SplashApp::setStage("kinit")
2019-03-15 22:34:12.811 SplashApp::setStage("kinit"): m_stages.count==3
2019-03-15 22:34:12.811 SplashApp::setStage(3), m_stage==2
2019-03-15 22:34:12.891 SplashApp::setStage("ksmserver")
2019-03-15 22:34:12.891 SplashApp::setStage("ksmserver"): m_stages.count==4
2019-03-15 22:34:12.891 SplashApp::setStage(4), m_stage==3
2019-03-15 22:34:13.119 SplashApp::setStage("ready")
2019-03-15 22:34:13.119 SplashApp::setStage("ready"): m_stages.count==5
2019-03-15 22:34:13.119 SplashApp::setStage(5), m_stage==4
2019-03-15 22:34:13.440 SplashApp::setStage("wm")
2019-03-15 22:34:13.440 SplashApp::setStage("wm"): m_stages.count==6
2019-03-15 22:34:13.440 SplashApp::setStage(6), m_stage==5
2019-03-15 22:34:15.841 SplashApp::setStage("desktop")
2019-03-15 22:34:15.841 SplashApp::setStage("desktop"): m_stages.count==7
2019-03-15 22:34:15.841 SplashApp::setStage(7), m_stage==6
2019-03-15 22:34:15.841 SplashApp::setStage() before exit
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 405503] New: Text cut off on buttons in Dolphin's "Configure the menu" window (Brazilian Portuguese and possibly other languages affected)
https://bugs.kde.org/show_bug.cgi?id=405503 Bug ID: 405503 Summary: Text cut off on buttons in Dolphin's "Configure the menu" window (Brazilian Portuguese and possibly other languages affected) Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: guimarcalsi...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Created attachment 118828 --> https://bugs.kde.org/attachment.cgi?id=118828=edit Cut off text screenshot SUMMARY STEPS TO REPRODUCE 1. Open Dolphin when using pt_BR locale 2. Click on the bottom right corner (where it says the amount of free space left) 3. Click "Configure..." (Configurar...). OBSERVED RESULT Text is cut off on the buttons because the text is either too big or the buttons are too small. (see attached screenshot) EXPECTED RESULT Text should fit perfectly SOFTWARE/OS VERSIONS Operating System: KDE neon Developer Edition KDE Plasma Version: 5.15.80 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.0 Kernel Version: 4.18.0-16-generic OS Type: 64-bit Processors: 2 × Intel® Core™ i5-6200U CPU @ 2.30GHz Memory: 3,9 GiB -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 405502] New: Okular crashes when trying to reopen document on unmounted filesystem
https://bugs.kde.org/show_bug.cgi?id=405502 Bug ID: 405502 Summary: Okular crashes when trying to reopen document on unmounted filesystem Product: okular Version: 1.5.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: k...@equaeghe.nospammail.net Target Milestone: --- Application: okular (1.5.3) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.27-gentoo-r1 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: The desktop environment was restarting. Previously, some pdfs were open in Okular. Before the restart, the filesystem on which those files were located was unmounted, so they were not there anymore. I guess Okular should just report that the file is not present instead of crashing because of it. -- Backtrace: Application: Okular (okular), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f51be01a180 (LWP 7009))] Thread 3 (Thread 0x7f5195145700 (LWP 7101)): #0 0x7f51b701056c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f51958901eb in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7f519588ff17 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7f51b700996a in start_thread () from /lib64/libpthread.so.0 #4 0x7f51b9daa92f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f51a0c03700 (LWP 7026)): #0 0x7f51b9d9ed63 in poll () from /lib64/libc.so.6 #1 0x7f51b4a100b9 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f51b4a101cc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f51ba70965b in QEventDispatcherGlib::processEvents (this=0x7f519c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f51ba6b985b in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f51ba5326c6 in QThread::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f51bab52de5 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7f51ba53b69b in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:367 #8 0x7f51b700996a in start_thread () from /lib64/libpthread.so.0 #9 0x7f51b9daa92f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f51be01a180 (LWP 7009)): [KCrash Handler] #6 0x7f51bc2099c3 in QMapData::findNode (this=0x20, akey=...) at /usr/include/qt5/QtCore/qmap.h:284 #7 0x7f51bc20ecab in QMap::constFind (akey=..., this=0x55a50872c5f0) at /usr/include/qt5/QtCore/qmap.h:869 #8 QMap::find (akey=..., this=0x55a50872c5f0) at /usr/include/qt5/QtCore/qmap.h:876 #9 KEntryMap::findEntry (this=this@entry=0x55a50872c5f0, group=..., key=..., flags=..., flags@entry=...) at /var/tmp/portage/kde-frameworks/kconfig-5.54.0-r1/work/kconfig-5.54.0/src/core/kconfigdata.cpp:74 #10 0x7f51bc2032f7 in KConfigPrivate::lookupData (this=this@entry=0x55a50872c5d0, group=..., key=key@entry=0x55a507f8bb42 "ActiveTab", flags=..., flags@entry=...) at /var/tmp/portage/kde-frameworks/kconfig-5.54.0-r1/work/kconfig-5.54.0/src/core/kconfig.cpp:1024 #11 0x7f51bc2187dc in KConfigGroup::readEntry (this=this@entry=0x7fff51f7c0f0, key=key@entry=0x55a507f8bb42 "ActiveTab", aDefault=...) at /var/tmp/portage/kde-frameworks/kconfig-5.54.0-r1/work/kconfig-5.54.0/src/core/kconfiggroup.cpp:725 #12 0x55a507f84de3 in KConfigGroup::readEntry (defaultValue=@0x7fff51f7c03c: 0, key=0x55a507f8bb42 "ActiveTab", this=0x7fff51f7c0f0) at /usr/include/KF5/KConfigCore/kconfiggroup.h:723 #13 Shell::readProperties (this=0x55a5084aea90, group=...) at /var/tmp/portage/kde-apps/okular-18.08.3/work/okular-18.08.3/shell/shell.cpp:392 #14 0x7f51bd191858 in KMainWindow::readPropertiesInternal (this=this@entry=0x55a5084aea90, config=0x55a5084b7720, number=number@entry=1) at /var/tmp/portage/kde-frameworks/kxmlgui-5.54.0-r1/work/kxmlgui-5.54.0/src/kmainwindow.cpp:652 #15 0x7f51bd1918a2 in KMainWindow::restore (this=0x55a5084aea90, number=1, show=) at /var/tmp/portage/kde-frameworks/kxmlgui-5.54.0-r1/work/kxmlgui-5.54.0/src/kmainwindow.cpp:473 #16 0x55a507f800db in kRestoreMainWindows () at /usr/include/KF5/KXmlGui/kmainwindow.h:719 #17 0x55a507f7d822 in main (argc=, argv=) at /var/tmp/portage/kde-apps/okular-18.08.3/work/okular-18.08.3/shell/main.cpp:64 The reporter indicates this bug may be a duplicate of or related to bug 402397. Possible duplicates by query: bug 402397, bug 395913, bug 395869, bug 395779, bug 395613. Reported using DrKonqi -- 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 --- Comment #16 from Wolfgang Reissenberger --- Bug fix posted here: https://phabricator.kde.org/D19794 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 308243] Inconsistent reset behaviour within curve tools
https://bugs.kde.org/show_bug.cgi?id=308243 Sambhav Dusad changed: What|Removed |Added Resolution|--- |DUPLICATE CC||sambhavdusa...@gmail.com Status|REPORTED|RESOLVED --- Comment #3 from Sambhav Dusad --- *** This bug has been marked as a duplicate of bug 277040 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 277040] Incomplete Reset of Functions for Curves widget [patch]
https://bugs.kde.org/show_bug.cgi?id=277040 --- Comment #12 from Sambhav Dusad --- *** Bug 308243 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 405386] RKWard Version 0.7.0z+0.7.1+devel1 can't preview Markdown
https://bugs.kde.org/show_bug.cgi?id=405386 --- Comment #13 from Adley --- I uploaded my whole process to youtube. https://www.youtube.com/watch?v=vRoZGoIAnkQ Thanks -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401306] digikam-git r41326 doesn't compile with Opencv 4
https://bugs.kde.org/show_bug.cgi?id=401306 --- Comment #23 from caulier.gil...@gmail.com --- Git commit 08423e488df2dc0346d9e18fd84c528354fe27bd by Gilles Caulier. Committed on 15/03/2019 at 20:37. Pushed by cgilles into branch 'master'. fix broken compilation with OpenCV 3 M +4-0core/app/utils/digikam_opencv.h.cmake.in https://commits.kde.org/digikam/08423e488df2dc0346d9e18fd84c528354fe27bd -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389549] "Clear all faces on this image" Does Not Remove All People Tags
https://bugs.kde.org/show_bug.cgi?id=389549 caulier.gil...@gmail.com changed: What|Removed |Added Version|5.8.0 |6.1.0 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 404881] Kontact crashes when closing Akregator from tray icon
https://bugs.kde.org/show_bug.cgi?id=404881 John Scott changed: What|Removed |Added Component|general |akregator -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 385189] Save dialog: Return key only bound to Save button when text field has focus
https://bugs.kde.org/show_bug.cgi?id=385189 Méven Car changed: What|Removed |Added CC||meve...@gmail.com --- Comment #3 from Méven Car --- I tried to reproduce this bug, it seems to me it is fixed. Can someone confirm ? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400658] Impossible to walk through all apps or all windows of the current app on Wayland
https://bugs.kde.org/show_bug.cgi?id=400658 Luca Weiss changed: What|Removed |Added CC||l...@z3ntu.xyz --- Comment #9 from Luca Weiss --- I have this problem on Arch in a Wayland session with Plasma 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 347326] Usability regression: resizing widgets in plasma 5
https://bugs.kde.org/show_bug.cgi?id=347326 Méven Car changed: What|Removed |Added CC||meve...@gmail.com --- Comment #4 from Méven Car --- I would suggest instead having a different background color for the handle. Something like a lighter gray or invert the color of the handle completely including the buttons. It would remove the need for a separation line altogether. I believe this would be more visually appealing. -- 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 Luca Weiss changed: What|Removed |Added CC||l...@z3ntu.xyz -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405286] Selecting ‘Configure Desktop’ when desktop configuration window is minimized has no effect
https://bugs.kde.org/show_bug.cgi?id=405286 --- Comment #3 from Karl Ove Hufthammer --- No, I’m on X.org, not Wayland. And I can reproduce the bug even when not using ‘Show Desktop’. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402608] Screen occasionally goes black for a second or two before coming back
https://bugs.kde.org/show_bug.cgi?id=402608 --- Comment #5 from DeKay --- (In reply to Christoph Feck from comment #4) > That could be a cable problem. Definitely not a cable problem. The time the screen is black is always the same (somewhere around a second or two), indicative of something crashing and restarting. The monitor OSD shows no indication that the hardware has lost its connection. Never happens in Windows. And I can't see getting the errors I'm getting if it was the cable. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389549] "Clear all faces on this image" Does Not Remove All People Tags
https://bugs.kde.org/show_bug.cgi?id=389549 --- Comment #12 from hardy.pub...@gmail.com --- Created attachment 118827 --> https://bugs.kde.org/attachment.cgi?id=118827=edit Not OK Metadata -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389549] "Clear all faces on this image" Does Not Remove All People Tags
https://bugs.kde.org/show_bug.cgi?id=389549 --- Comment #11 from hardy.pub...@gmail.com --- Created attachment 118826 --> https://bugs.kde.org/attachment.cgi?id=118826=edit OK Metadata Yet more info: Also confirmed this is not a database problem because I confirmed the XMP metadata is definitely present using another tool. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 222470] Switch to temporarily disable all notifications ("Do not disturb" mode)
https://bugs.kde.org/show_bug.cgi?id=222470 jat...@gmail.com changed: What|Removed |Added CC||jat...@gmail.com --- Comment #4 from jat...@gmail.com --- Anyone have an idea on how to go about implementing something like this? Would it need a big change on the notification backend, or is there a flag somewhere that could be changed with a nice little checkbox? As Daniele mentioned, nearly every other DE (windows and mac included) have something like this, and this is a serious usability issue for Plasma. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389549] "Clear all faces on this image" Does Not Remove All People Tags
https://bugs.kde.org/show_bug.cgi?id=389549 --- Comment #10 from hardy.pub...@gmail.com --- More info: I did the same trial with the same images but in a local collection. Again 3/10 images had lingering Test6 tag. So I guess this eliminates NAS collections as a causal factor. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405234] Refresh does no work
https://bugs.kde.org/show_bug.cgi?id=405234 --- Comment #21 from Maik Qualmann --- To change the rating externally, the Metadata option "Reread metadata if the files were changed" should be activated. We monitor the directory, which means the new / no longer existing files, changed name and file size is detected. If the file already had a rating, there is no resizing and digiKam will not be notified. Monitoring all files would consume the system resources. It would be possible to monitor only the currently active album completely. We would not notice changes in other albums. But actually you should change the rating in digiKam. :-) If the refresh with F5 takes too long because thumbnails are also rebuilt, try Album-> Reread Metadata from files. Maik -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 404695] Icy Cast metadata received from stream doesn't updates the author correctly
https://bugs.kde.org/show_bug.cgi?id=404695 Fernando changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #5 from Fernando --- Changing status. Required information given. Hope it helps ;) -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards
https://bugs.kde.org/show_bug.cgi?id=405437 --- Comment #35 from Rob --- Actually the question is not what changed, the question is what didn't change. Basically EVERYTHING changed from 3.0.0 to 3.1.0. We were forced to abandon the old method we were using to build KStars entirely. The script we built over about 2 years no longer worked for us because qt stopped supporting OS 10.11 entirely. The old script would build using a combination of craft and homebrew. It was fairly complicated, sort of like a patchwork quilt, but it worked pretty well. With the old script, since we were using homebrew, we had to build kstars on the minimum system we wanted to support. Homebrew does not support building software for older systems. So if we wanted to support 10.11, 10.12, 10.13, and 10.14, we had to build on a 10.11 system. If we built on a 10.14 system, it will ONLY work on 10.14. I had been planning for months to get some craft recipes together so that we could build kstars using only craft and not having to install anything using macports or homebrew to /usr/local at all. Then we can build for older OSes I had actually written most of the recipes already over the last few months. But then our old script broke VERY suddenly, with no warning, with a QT update. So I very quickly wrote up a new build script based entirely on craft (well almost entirely). 3.1.0 was the first one we released with the new script. It actually worked almost completely. There were just a couple of mistakes in 3.1.0 that I corrected in 3.1.1. In fact 3.1.0 did NOT plate solve correctly because I misnamed the internal python executable. It needed to be called python2.7. I found that naming that python made it look in /usr/local for python instead of using the bundled one. But naming it python2.7 made it use the correct python. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 405501] plasma-nm is not compatible with NetworkManager 1.16's native WireGuard support
https://bugs.kde.org/show_bug.cgi?id=405501 Jan Grulich changed: What|Removed |Added CC||banderson19...@san.rr.com, ||jgrul...@redhat.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 405501] plasma-nm is not compatible with NetworkManager 1.16's native WireGuard support
https://bugs.kde.org/show_bug.cgi?id=405501 K900 changed: What|Removed |Added Platform|Other |Archlinux Packages CC||m...@0upti.me -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 405501] New: plasma-nm is not compatible with NetworkManager 1.16's native WireGuard support
https://bugs.kde.org/show_bug.cgi?id=405501 Bug ID: 405501 Summary: plasma-nm is not compatible with NetworkManager 1.16's native WireGuard support Product: plasma-nm Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: m...@0upti.me Target Milestone: --- SUMMARY The WireGuard connections are shown as wired connections, and are brought up automatically on login. STEPS TO REPRODUCE 1. Install NetworkManager 1.16 2. nmcli connection import type wireguard file my-wg-conf.conf 3. Open plasma-nm OBSERVED RESULT WireGuard connection is treated as an Ethernet connection EXPECTED RESULT WireGuard connection should be treated as a WireGuard connection -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389549] "Clear all faces on this image" Does Not Remove All People Tags
https://bugs.kde.org/show_bug.cgi?id=389549 --- Comment #9 from hardy.pub...@gmail.com --- Created attachment 118825 --> https://bugs.kde.org/attachment.cgi?id=118825=edit Video showing problem. The problem still there unfortunately. I attach a video with ten 10 identical images and "clear faces" on each in turn. Image 5.jpg and 7.jpg have a lingering tag so it's a problem about 20% of the time. Sometimes it's more often. Sometimes it's less. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 405500] New: Kontact Crashes Opening Settings
https://bugs.kde.org/show_bug.cgi?id=405500 Bug ID: 405500 Summary: Kontact Crashes Opening Settings Product: kontact Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: lnx...@westlot.net Target Milestone: --- Application: kontact (5.10.1) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.15.0-46-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: Kontact crashes when Settings->Configure Kontact is clicked. from within any module. Other configuration menu items withion Settings works without crashing. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f15b75dcbc0 (LWP 15343))] Thread 23 (Thread 0x7f14466f3700 (LWP 15757)): #0 0x7f15af807ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f14466f2710, expected=0, futex_word=0x7f14466f28f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f15af807ed9 in __pthread_cond_wait_common (abstime=0x7f14466f27b0, mutex=0x7f14466f28a8, cond=0x7f14466f28d0) at pthread_cond_wait.c:533 #2 0x7f15af807ed9 in __pthread_cond_timedwait (cond=0x7f14466f28d0, mutex=0x7f14466f28a8, abstime=0x7f14466f27b0) at pthread_cond_wait.c:667 #3 0x7f15a4e67177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f15a4e67ada in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f15a4e67bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f15a4e25851 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f15a4e28387 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f15a4e28974 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f15a4e69cd1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f15af8016db in start_thread (arg=0x7f14466f3700) at pthread_create.c:463 #11 0x7f15b3f0b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7f146bfff700 (LWP 15529)): #0 0x7f15af807ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f146bffe710, expected=0, futex_word=0x7f146bffe8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f15af807ed9 in __pthread_cond_wait_common (abstime=0x7f146bffe7b0, mutex=0x7f146bffe8a8, cond=0x7f146bffe8d0) at pthread_cond_wait.c:533 #2 0x7f15af807ed9 in __pthread_cond_timedwait (cond=0x7f146bffe8d0, mutex=0x7f146bffe8a8, abstime=0x7f146bffe7b0) at pthread_cond_wait.c:667 #3 0x7f15a4e67177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f15a4e67ada in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f15a4e67bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f15a4e25851 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f15a4e286b6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f15a4e28974 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f15a4e69cd1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f15af8016db in start_thread (arg=0x7f146bfff700) at pthread_create.c:463 #11 0x7f15b3f0b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7f144fbff700 (LWP 15452)): #0 0x7f15b3efebf9 in __GI___poll (fds=0x7f1448003ce0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f15ad935539 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f15ad93564c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f15b4a5915b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f15b49fa64a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f15b482241a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f15b4823bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f15af8016db in start_thread (arg=0x7f144fbff700) at pthread_create.c:463 #8 0x7f15b3f0b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7f1471c26700 (LWP 15431)): #0 0x7f15ad97b049 in g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f15ad934905 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f15ad93546b in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f15ad93564c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f15b4a5915b in
[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards
https://bugs.kde.org/show_bug.cgi?id=405437 --- Comment #34 from Andre Kovacs --- Just to let you know, I tested KStars versions and the plate solver worked fine up to version 3.0.0. The issue started with version 3.1.0. The question is, what changed in plate solving from version 3.0.0 to 3.1.0? -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 405476] Saving the Ekos settings
https://bugs.kde.org/show_bug.cgi?id=405476 --- Comment #5 from Jean-Claude --- The same applies to the Focus settings in the Focuser Module : The focus settings are saved only if an Autofocus has been executed except (Focuser/Steps) and (CCD & Filter Wheel/FW) -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 403814] Messages moved to trash from trash icon in message window disappear.
https://bugs.kde.org/show_bug.cgi?id=403814 lnx...@westlot.net changed: What|Removed |Added Version|5.7.3 |5.10.3 --- Comment #1 from lnx...@westlot.net --- Several versions later and this is still a problem. Is anyone listening? Email disappearing unexpectedly is a major problem. The only workaround for this if you don't want the message preview pane visible is to close the email and move it to the trash from the message view window. This creates an extra step that becomes annoying after just a couple of messages. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 397782] Position and zoom keyframe get lost if you move/ extend / whatever
https://bugs.kde.org/show_bug.cgi?id=397782 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405496] Installation of KDE5 immovable
https://bugs.kde.org/show_bug.cgi?id=405496 --- Comment #3 from lsmod --- Then please move this problem to the correct "product". Thanks. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405232] digiKam crashes in Slideshow and Presentation
https://bugs.kde.org/show_bug.cgi?id=405232 --- Comment #12 from harald.a...@web.de --- Created attachment 118824 --> https://bugs.kde.org/attachment.cgi?id=118824=edit Screenshot of Task Manager while running digiKam Ok, the predictability (Slideshow always crashes after first image) I have to take back; it just ran through a slideshow of 5 images without crashing. Without knowing the details, the logs attached before seem to indicate a memory problem on my machine. However, to me, this doesn't seem to be the case. In the attached screenshot, the interesting part (i.e. where digiKam is running) is the right half. Idle; digiKam starts; slideshow with 5 images without crash; new slideshow with crash. At any rate, the memory available seems to be more than sufficient. At least it was to what I was running before starting digiKam, as can be seen in the left half. Best regards, Harald -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401306] digikam-git r41326 doesn't compile with Opencv 4
https://bugs.kde.org/show_bug.cgi?id=401306 --- Comment #22 from maderios --- Fixed for me -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405232] digiKam crashes in Slideshow and Presentation
https://bugs.kde.org/show_bug.cgi?id=405232 --- Comment #11 from harald.a...@web.de --- Created attachment 118823 --> https://bugs.kde.org/attachment.cgi?id=118823=edit Log for "Presentation" with transition "None" -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405232] digiKam crashes in Slideshow and Presentation
https://bugs.kde.org/show_bug.cgi?id=405232 --- Comment #9 from caulier.gil...@gmail.com --- It's clear, there is a memory allocation error : digikam.dimg: Failed to allocate chunk of memory of size 64131072 std::bad_alloc Do you found the crash backtrace file ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405232] digiKam crashes in Slideshow and Presentation
https://bugs.kde.org/show_bug.cgi?id=405232 --- Comment #10 from harald.a...@web.de --- Created attachment 118822 --> https://bugs.kde.org/attachment.cgi?id=118822=edit Log for "Presentation" with OpenGL transition Behavior was different from the one described before. It did not show just white screens, but alternating the first image and a white screen. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405232] digiKam crashes in Slideshow and Presentation
https://bugs.kde.org/show_bug.cgi?id=405232 --- Comment #8 from harald.a...@web.de --- Created attachment 118821 --> https://bugs.kde.org/attachment.cgi?id=118821=edit Log for "Slideshow" -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 161266] Network speed monitor not displays or speed value doubles
https://bugs.kde.org/show_bug.cgi?id=161266 Richard Llom changed: What|Removed |Added CC||richard.l...@gmail.com See Also||https://bugs.kde.org/show_b ||ug.cgi?id=354350 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 354350] ksysguard sums all network interfaces even though virtual interfaces are already counted
https://bugs.kde.org/show_bug.cgi?id=354350 Richard Llom changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=161266 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405232] digiKam crashes in Slideshow and Presentation
https://bugs.kde.org/show_bug.cgi?id=405232 --- Comment #7 from caulier.gil...@gmail.com --- If it crash, you must see a crash backtrace file generated by DrMinGW in your home directory : C:\Users\_user_name_\AppData\Local\digikam_crash.log Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 405375] Crash in kdiff3
https://bugs.kde.org/show_bug.cgi?id=405375 --- Comment #1 from michael --- Git commit d25cb3a405b9ba93a5cd6c63df82ac70bcacc001 by Michael Reeves. Committed on 15/03/2019 at 14:01. Pushed by mreeves into branch 'master'. use std::list not QList std::list is close to QLinkedList behavoir wise. In particular it matches rules about what operations invalidate iterators. FIXED-IN:1.8 M +2-2src/diff.cpp M +3-1src/diff.h https://commits.kde.org/kdiff3/d25cb3a405b9ba93a5cd6c63df82ac70bcacc001 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405232] digiKam crashes in Slideshow and Presentation
https://bugs.kde.org/show_bug.cgi?id=405232 --- Comment #6 from harald.a...@web.de --- Gilles, The following is for digiKam-6.1.0-git-20190315T074305-Win32. - No error message at startup anymore. - Slideshow: Crashes. However, it now seems to consistently show the first picture and crash when transitioning to the second. - Presentation, standard transition "None": Screen remains black; always crashes sooner or later. Can't say if behavior has changed or not. - Presentation, OpenGL transition "Fade": Same behavior as before. Doesn't crash but only shows white screen instead of pictures fading in and out. Kind regards, Harald -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 405499] New: Content area does not change when clicking on tree entries
https://bugs.kde.org/show_bug.cgi?id=405499 Bug ID: 405499 Summary: Content area does not change when clicking on tree entries Product: kinfocenter Version: 5.15.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: hubn...@gmail.com Reporter: sascha.gas...@gmx.de Target Milestone: --- SUMMARY The right side (main content area) does not change when I click on a tree entry. When I select an entry and hit enter, the according content is shown. STEPS TO REPRODUCE 1. Open kinfocenter 2. Klick on an entry of the tree (e.g. X-Server) OBSERVED RESULT The right side does not change. EXPECTED RESULT The right side should show the X-Server informations. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Plasmashell 5.15.2 (also in 5.15.1) (available in About System) KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION I tried it only with Wayland. Distribution: OpenSUSE Tumbleweed -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385942] Applications with URLs constructed with spaces can't be pinned and/or jump around
https://bugs.kde.org/show_bug.cgi?id=385942 michael changed: What|Removed |Added Status|RESOLVED|REPORTED CC||reeves...@gmail.com Version Fixed In|1.8 | Latest Commit|https://commits.kde.org/kdi | |ff3/d25cb3a405b9ba93a5cd6c6 | |3df82ac70bcacc001 | Resolution|FIXED |--- --- Comment #28 from michael --- Closed wrong bug -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405234] Refresh does no work
https://bugs.kde.org/show_bug.cgi?id=405234 --- Comment #20 from harald.a...@web.de --- Regarding load time, My machine is an 11-year-old laptop without SSD. It runs perfectly, but it is still an 11-year-old laptop without SSD. And digiKam is not exactly small, so I wouldn't expect miracles. Nonetheless, it normally loads in less than 10 seconds. Only immediately after installation it seems to take significantly longer. Kind regards, Harald -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401306] digikam-git r41326 doesn't compile with Opencv 4
https://bugs.kde.org/show_bug.cgi?id=401306 --- Comment #21 from caulier.gil...@gmail.com --- Git commit 7a5af66d8fc7ab8e78f05016eaf3e94de66951b3 by Gilles Caulier. Committed on 15/03/2019 at 16:16. Pushed by cgilles into branch 'master'. fix broken compilation with OpenCV4 in Test::FaceEngine M +7-1core/tests/facesengine/preprocess.cpp https://commits.kde.org/digikam/7a5af66d8fc7ab8e78f05016eaf3e94de66951b3 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405234] Refresh does no work
https://bugs.kde.org/show_bug.cgi?id=405234 --- Comment #19 from harald.a...@web.de --- Maik, The following is for digiKam-6.1.0-git-20190315T074305-Win32. - Automatic monitoring now works :-) As you wrote, new files are discovered after 1 second or so; changes in tags (rating) are not discovered. - Triggering Refresh manually now works and also discovers tag changes. However, it's extremely slow (8 minutes (yes) for a database of just 360 pictures), so I'd say its practical use is limited... - Doing Tools/Maintenance/Scan still works and takes only 1 second. Best regards, Harald -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405498] Can't render animation to PNG sequence
https://bugs.kde.org/show_bug.cgi?id=405498 --- Comment #3 from Konstantin Dmitriev --- Note: the same can be reproduced by rendering animation via CLI: ``` konstantin@master:~$ /home/konstantin/0-work/tools/apps/krita-4.2.0-pre-alpha-bb0edcc-x86_64.appimage --export-sequence '/home/konstantin/0-work/morevna/ep03/118-5/118-5-storyboard-54-7-bug2.kra' --export-filename /tmp/file.png krita.general: Failed to load "paintoppresets/11_Clone_brush.kpp" from bundle "/home/konstantin/.local/share/krita/bundles/rads.bundle" krita.general: Failed to load "paintoppresets/14_Brush_Textured.kpp" from bundle "/home/konstantin/.local/share/krita/bundles/rads.bundle" Entering "KisAsyncAnimationRenderDialogBase::Result KisAsyncAnimationRenderDialogBase::regenerateRange()" numWorkers = 4 numThreadsPerWorker = 2 Entering "KisAsyncAnimationRenderDialogBase::Result KisAsyncAnimationRenderDialogBase::regenerateRange()" Copying done in 34 Entering "KisAsyncAnimationRenderDialogBase::Result KisAsyncAnimationRenderDialogBase::regenerateRange()" Full regeneration done in 9965 krita.general: "Failed to render animation frames!" krita.general: Warning: some tiles have leaked: krita.general: Tiles in memory: 11082 Total tiles: 11082 konstantin@master:~$ ``` -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405498] Can't render animation to PNG sequence
https://bugs.kde.org/show_bug.cgi?id=405498 --- Comment #2 from Konstantin Dmitriev --- This is almost the same file. It is after re-saving in Linux + some minor edits (layers renamed to English). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405498] Can't render animation to PNG sequence
https://bugs.kde.org/show_bug.cgi?id=405498 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Just checking: is this the file we discussed earlier? And before or after re-saving on Linux? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405498] Can't render animation to PNG sequence
https://bugs.kde.org/show_bug.cgi?id=405498 Konstantin Dmitriev changed: What|Removed |Added Summary|Cant' render animation to |Can't render animation to |PNG sequence|PNG sequence -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405498] New: Cant' render animation to PNG sequence
https://bugs.kde.org/show_bug.cgi?id=405498 Bug ID: 405498 Summary: Cant' render animation to PNG sequence Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: ksee.zelga...@gmail.com Target Milestone: --- SUMMARY Krita fails to render animation from this file - https://downloads.morevnaproject.org/public/118-5-storyboard-54-7-bug2.kra Rendering starts, but after rendering 5-8 frames (count of frames is different every time) it fails. Tested on Krita nightly appimage, commit id bb0edcc. STEPS TO REPRODUCE 1. Open file https://downloads.morevnaproject.org/public/118-5-storyboard-54-7-bug2.kra 2. Choose File -> Render Animation 3. In "Render Animation" window select "Image sequence" option. Make sure "File format" is set to "PNG image", "frame range" from 0 to 100. 4. Click OK. 5. Rendering starts. 6. After some time render stops, showing "Failed to render animation frames!" in the top-left corner of canvas. OBSERVED RESULT Examine output dir to see that not all frames are rendered. EXPECTED RESULT Frames from 0 to 100 should be rendered. SOFTWARE/OS VERSIONS Linux: Linux Mint 19 Mate edition ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 22540] Creating/Editing Symlinks
https://bugs.kde.org/show_bug.cgi?id=22540 Lucas Willems changed: What|Removed |Added CC||lcswill...@gmail.com --- Comment #12 from Lucas Willems --- I don't understand how we can create or edit symlinks... It seems like it is not implemented. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 405224] KMail/Kontact mail list refreshed on (de)activation
https://bugs.kde.org/show_bug.cgi?id=405224 Mykola Krachkovsky changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Mykola Krachkovsky --- This looks like solved with 5.10.3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405497] Cannot charge Android phone when device notifier appear
https://bugs.kde.org/show_bug.cgi?id=405497 Guo Yunhe changed: What|Removed |Added Version|5.15.3 |5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405497] New: Cannot charge Android phone when device notifier appear
https://bugs.kde.org/show_bug.cgi?id=405497 Bug ID: 405497 Summary: Cannot charge Android phone when device notifier appear Product: plasmashell Version: 5.15.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Device Notifier Assignee: plasma-b...@kde.org Reporter: i...@guoyunhe.me Target Milestone: 1.0 SUMMARY When I want to charge my phone through computer, Device Notifier always prevents charging. I think most users connect their phone to computer for charging other than read files in the storage. STEPS TO REPRODUCE 1. Have an Android phone and a KDE PC. 2. Connect phone to PC with USB cable. 3. Check the charging status in the phone and Device Notifier in the PC. OBSERVED RESULT Phone charges only a short time. Then Device Notifier tray icon appears and charging immediately stopped. EXPECTED RESULT Phone should be charged. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20190310 KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.0 Kernel Version: 4.20.13-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 31.2 GiB ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401306] digikam-git r41326 doesn't compile with Opencv 4
https://bugs.kde.org/show_bug.cgi?id=401306 caulier.gil...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/dig ||ikam/a38c26bbc57291172404b8 ||4e05ac2b82c6db9808 --- Comment #20 from caulier.gil...@gmail.com --- Git commit a38c26bbc57291172404b84e05ac2b82c6db9808 by Gilles Caulier. Committed on 15/03/2019 at 14:52. Pushed by cgilles into branch 'master'. This header is deprecated with openCV4 M +0-1core/app/utils/digikam_opencv.h.cmake.in https://commits.kde.org/digikam/a38c26bbc57291172404b84e05ac2b82c6db9808 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405403] s390x disassembler cannot be used on x86
https://bugs.kde.org/show_bug.cgi?id=405403 Andreas Arnez changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #6 from Andreas Arnez --- Pushed as commit #7e9113cb7a249e0fae2a365462c6b0164de11566. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405496] Installation of KDE5 immovable
https://bugs.kde.org/show_bug.cgi?id=405496 --- Comment #2 from Vlad Zagorodniy --- kwin has nothing to do with it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405496] Installation of KDE5 immovable
https://bugs.kde.org/show_bug.cgi?id=405496 --- Comment #1 from lsmod --- Created attachment 118820 --> https://bugs.kde.org/attachment.cgi?id=118820=edit KDE 4 version -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405496] New: Installation of KDE5 immovable
https://bugs.kde.org/show_bug.cgi?id=405496 Bug ID: 405496 Summary: Installation of KDE5 immovable Product: kwin Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: forum+...@home.decotrain.de Target Milestone: --- Created attachment 118819 --> https://bugs.kde.org/attachment.cgi?id=118819=edit KDE 5 version Up to KDE 4 it was no problem to configure a complete distribution of Linux on an PC, make an tar.gz of it and deploy this installation to other PC's. This was working very comfortable and stable. Now in KDE 5 this seems not possible any more! In 3 cases after the unpacking i ended in an black empty screen with only the mouse cursor that can be moved on it. I have no idea why the rest is missing and how to debug this? The last fatal try was to move an running installation on my PC from the hard-disk to the SSD on the same PC. Booting from SSD is working, but after the login there is only the blank black screen. STEPS TO REPRODUCE 1. Boot an Knoppix or another Linux 2. Pack / Backup the running installation in the mounted partition with tar cvfz. 3. Unpack the tar.gz on another hardisk or PC 4. Make the needed adjustment of the fstab to the new UUID, and grub.cfg etc. 5. Boot and start the copied installation OBSERVED RESULT Vopied installation ends up with an blank black screen only the mouse working. EXPECTED RESULT Copy is working perfect without limits. SOFTWARE/OS VERSIONS See the screenshots of the last KDE 4 (Debian 8 jessie) and KDE 5 (Debian 9 stretch) Info -- You are receiving this mail because: You are watching all bug changes.
