[akregator] [Bug 389059] Deleting articles in Akregator causes graphics reset
https://bugs.kde.org/show_bug.cgi?id=389059 --- Comment #4 from Syam --- No. I can no longer reproduce this. I still have NVidia proprietary drivers but I no longer have this issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425522] Strange text in plasma-org.kde.plasma.desktop-appletsrc
https://bugs.kde.org/show_bug.cgi?id=425522 --- Comment #4 from numb3rl...@gmail.com --- I installed from .deb downloaded from the website. I am running current stable Debian. It also garbled the images of the widgets library if I right click and try to add a widget. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425522] Strange text in plasma-org.kde.plasma.desktop-appletsrc
https://bugs.kde.org/show_bug.cgi?id=425522 --- Comment #3 from numb3rl...@gmail.com --- Created attachment 131031 --> https://bugs.kde.org/attachment.cgi?id=131031=edit Pic of bug in action -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 408681] Repeated assert fail in baloo_file_extractor (master branch)
https://bugs.kde.org/show_bug.cgi?id=408681 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 Jason Cox changed: What|Removed |Added CC||d...@jasoncarloscox.com --- Comment #80 from Jason Cox --- Phone: Moto G7 Android Version: 10 SMS App: QKSMS 3.8.1 KDE Connect App Version: 1.14.2 OS: Arch Linux KDE Connect SMS Version: 1.4.0 I'm having this issue as well. I get notifications about new messages and can respond, but when I open the KDE Connect SMS app, it just spins and spins and never loads anything. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425575] New: Separate opacity curve for eraser.
https://bugs.kde.org/show_bug.cgi?id=425575 Bug ID: 425575 Summary: Separate opacity curve for eraser. Product: krita Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: i...@ralek.art Target Milestone: --- I have several 'sketch' brushes which have a curve that barely ever reaches 100% unless I push hard, and when I want the line to be thicker I do push harder. However when switching to eraser mode, it keeps the same curve and is thus nearly impossible for me to fully erase a line, since the eraser also almost never reaches 100% opacity. I have to push very hard to erase a line completely, and even go over it several times. I've started getting hand cramps from having to push so hard. "Separate opacity for brush and eraser" setting doesn't help, because I want the dynamic range of opacity available for my actual brush, while the eraser version either has a separate curve altogether, or simply ignores the pressure curve and goes by the opacity setting. (Maybe a toggle to ignore the curve?) -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 425546] Warn if file will be overwritten via "Save As"
https://bugs.kde.org/show_bug.cgi?id=425546 2wxsy5823...@opayq.com changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from 2wxsy5823...@opayq.com --- I can reproduce the bug. Other KDE apps such as Spectacle and KolourPaint work as expected and will warn if the file will be overwritten (e.g. by double-clicking the file). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425574] New: Konsole crashes when double-clicking and dragging a tab to reorder
https://bugs.kde.org/show_bug.cgi?id=425574 Bug ID: 425574 Summary: Konsole crashes when double-clicking and dragging a tab to reorder Product: konsole Version: 20.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: jappl...@redhat.com Target Milestone: --- Application: konsole (20.04.1) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.7.14-200.fc32.x86_64 x86_64 Windowing system: X11 Distribution: "Fedora release 32 (Thirty Two)" -- Information about the crash: What I was doing when the application crashed: - I had multiple tabs open in Konsole - which had been open for ~24 hours (locked computer overnight and returned to the consoles the next morning) - I was attempting to reorder the tabs and accidentally double-clicked while dragging a tab to re-order it. - Konsole crashed after that double-click action occurred. - I have not been able to reproduce this crash. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f686f3e30c0 (LWP 4764))] Thread 6 (Thread 0x7f684e29b700 (LWP 4771)): #0 0x7f687268ae92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f6859d2a59b in util_queue_thread_func () from /usr/lib64/dri/iris_dri.so #2 0x7f6859d2a06b in impl_thrd_routine () from /usr/lib64/dri/iris_dri.so #3 0x7f6872684432 in start_thread () from /lib64/libpthread.so.0 #4 0x7f6874e76913 in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f684ea9c700 (LWP 4770)): #0 0x7f687268ae92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f6859d2a59b in util_queue_thread_func () from /usr/lib64/dri/iris_dri.so #2 0x7f6859d2a06b in impl_thrd_routine () from /usr/lib64/dri/iris_dri.so #3 0x7f6872684432 in start_thread () from /lib64/libpthread.so.0 #4 0x7f6874e76913 in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f684f29d700 (LWP 4769)): #0 0x7f687268ae92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f6859d2a59b in util_queue_thread_func () from /usr/lib64/dri/iris_dri.so #2 0x7f6859d2a06b in impl_thrd_routine () from /usr/lib64/dri/iris_dri.so #3 0x7f6872684432 in start_thread () from /lib64/libpthread.so.0 #4 0x7f6874e76913 in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f6858da0700 (LWP 4768)): #0 0x7f687268ae92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f6859d2a59b in util_queue_thread_func () from /usr/lib64/dri/iris_dri.so #2 0x7f6859d2a06b in impl_thrd_routine () from /usr/lib64/dri/iris_dri.so #3 0x7f6872684432 in start_thread () from /lib64/libpthread.so.0 #4 0x7f6874e76913 in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f686098c700 (LWP 4767)): #0 0x7f6874e6baaf in poll () from /lib64/libc.so.6 #1 0x7f6871d91aae in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #2 0x7f6871d91be3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f68737a1b8b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f687375491b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f68735c0427 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f6872dab51b in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #7 0x7f68735c1690 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f6872684432 in start_thread () from /lib64/libpthread.so.0 #9 0x7f6874e76913 in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f686f3e30c0 (LWP 4764)): [KCrash Handler] #4 0x7f6874d0e7af in Konsole::ViewManager::sessionFinished() () from /lib64/libkonsoleprivate.so.20 #5 0x7f6873784f76 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #6 0x7f6874cdb2ae in Konsole::Session::closeInNormalWay() () from /lib64/libkonsoleprivate.so.20 #7 0x7f6874cdecd9 in Konsole::SessionController::closeSession() () from /lib64/libkonsoleprivate.so.20 #8 0x7f6874d07a04 in Konsole::TabbedViewContainer::closeTerminalTab(int) () from /lib64/libkonsoleprivate.so.20 #9 0x7f6873784f76 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #10 0x7f68742a22f5 in QTabBar::tabCloseRequested(int) () from /lib64/libQt5Widgets.so.5 #11 0x7f6873784fb0 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #12 0x7f68741e1fd6 in QAbstractButton::clicked(bool) () from /lib64/libQt5Widgets.so.5 #13 0x7f68741e299e in QAbstractButtonPrivate::emitClicked() () from /lib64/libQt5Widgets.so.5 #14 0x7f68741e4253 in
[Breeze] [Bug 399680] Graphical glitch/corruption in certain menus when transparency effect is enabled
https://bugs.kde.org/show_bug.cgi?id=399680 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #28 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/breeze/-/merge_requests/21 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 425573] New: Spectacle does not save Rectangular Selection
https://bugs.kde.org/show_bug.cgi?id=425573 Bug ID: 425573 Summary: Spectacle does not save Rectangular Selection Product: Spectacle Version: 20.08.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: thebillywa...@gmail.com CC: k...@david-redondo.de Target Milestone: --- Created attachment 131030 --> https://bugs.kde.org/attachment.cgi?id=131030=edit screenshot of configuration SUMMARY Spectacle is configured to a) Capture a Rectangular Selection upon hotkey press. b) auto-save the rectangular selection to a predefined location. c) copy the image to the clipboard. The previous version of Spectacle worked as expected. STEPS TO REPRODUCE 1. Configure Spectacle as described above. 2. Press hotkey. 3. Browse autosave location and witness no new file has been saved. OBSERVED RESULT Rectangular Selection is copied to the clipboard, but the image is not saved to the default location. EXPECTED RESULT Rectangular Selection is copied to the clipboard AND the Rectangular Selection is saved to default location. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 5.8.1 / Plasma 5.19.4 (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION I love KDE! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425572] when loading up the program it begins to flash very fast, going from black to the normal screen, cannot use it at all.
https://bugs.kde.org/show_bug.cgi?id=425572 Emmet O'Neill changed: What|Removed |Added CC||emmetoneill@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Emmet O'Neill --- Hi Lidia, sorry you've been having trouble with Krita. In order for us to figure out what's going wrong, it would help if you could give us more information about your computer, including your operating system (Windows, MacOSX, Linux), as well as what version of Krita you're running. (If you aren't sure, you can find out this information with the `Help > Report Bug` option on the top bar.) If you're on Windows something that you also may want to try is switching to the "ANGLE" renderer. You can do this by going to `Settings > Configure Krita > Display > Canvas Acceleration > Preferred Renderer`, setting it to "ANGLE" and restarting Krita. Please let us know if setting your renderer to ANGLE doesn't fix the problem or if you need more help. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425572] New: when loading up the program it begins to flash very fast, going from black to the normal screen, cannot use it at all.
https://bugs.kde.org/show_bug.cgi?id=425572 Bug ID: 425572 Summary: when loading up the program it begins to flash very fast, going from black to the normal screen, cannot use it at all. Product: krita Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: critical Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: pirate.ale...@gmail.com Target Milestone: --- SUMMARY when i load up the program it is fine until i try to draw. it begins to flash very fast, going from black to the normal screen, i cannot use it at all STEPS TO REPRODUCE 1. everything 2. 3. OBSERVED RESULT none EXPECTED RESULT i'd like to use this to draw please. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION i really like what i have seen so far, but i cannot even draw a line so i cannot say much. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424311] Severe Rendering Issues on Latest Nvidia Driver (450.57) (Arch)
https://bugs.kde.org/show_bug.cgi?id=424311 --- Comment #31 from Arix --- (In reply to Erik Kurzinger from comment #30) I've downgraded and re-upgraded on a couple different occasions to verify that it is the driver. No other packages were changed, and it has consistently been fine on 440 and broken on 450. As I beleive I mentioned above as well, I've noticed issues in another compositor, Picom, when using GLX but again only on the 450 driver. So it's not just a KDE/kwin thing. This is again something that works with no issues on 440, all other packages untouched. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 409995] Scan for Faces in video files is not yet supported
https://bugs.kde.org/show_bug.cgi?id=409995 Minh Nghia Duong changed: What|Removed |Added CC||minhnghiaduong...@gmail.com --- Comment #3 from Minh Nghia Duong --- Real-time face detection and recognition on video are possible. However, if you wish to extract all the faces appear in the video, it is possible that too many faces are returned, depend on the number of frames. If you wish to return only distinct faces in the video, face clustering is needed. In both ways, video analyse like this, as Gilles said, is time-consuming. But if this feature is still in need, I could try to implement it -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425571] New: Panel is animated twice when shown
https://bugs.kde.org/show_bug.cgi?id=425571 Bug ID: 425571 Summary: Panel is animated twice when shown Product: plasmashell Version: 5.19.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: carlon.l...@gmail.com Target Milestone: 1.0 Created attachment 131029 --> https://bugs.kde.org/attachment.cgi?id=131029=edit Show the problem and how to reproduce. SUMMARY When system tray (panel) is set to auto hide, the animation showing it is played twice in some cases. I attach a video to show the issue. STEPS TO REPRODUCE 1. Move the cursor to the border of the screen to show the panel. 2. Leave the cursor on the border, do not move it during the animation. OBSERVED RESULT Show animation is played twice. EXPECTED RESULT Show animation should only be played once. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION I've seen this issue also in Kubuntu. Please note that I'm working on a highdpi display. Not sure if this also happens in a regular display. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 424828] Render crashes
https://bugs.kde.org/show_bug.cgi?id=424828 --- Comment #2 from eldieguis...@gmail.com --- (In reply to emohr from comment #1) > Please try with the Kdenlive_Nightly_Appimage > https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/ > lastSuccessfulBuild/artifact/ > > WARNING: This version has a new project type that is not backwards > compatible... so you won't be able to use older versions to open new files. Works! I tried it with my original project on the same machine, and I can verify it is not crashing. It now does generate the final mp4 file. I do see some compatibilities issues with older project versions, but I guess that's outside the scope of this thread. When will this version be pushed to distribution repos (dnf for Fedora ;))? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425570] New: Long folder names create too much padding in breadcrumb
https://bugs.kde.org/show_bug.cgi?id=425570 Bug ID: 425570 Summary: Long folder names create too much padding in breadcrumb Product: dolphin Version: 20.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: bars: location Assignee: dolphin-bugs-n...@kde.org Reporter: squeakypanca...@disroot.org CC: kfm-de...@kde.org Target Milestone: --- Created attachment 131027 --> https://bugs.kde.org/attachment.cgi?id=131027=edit too much padding SUMMARY The padding in the breadcrumb menu around folders with long names is way to big. STEPS TO REPRODUCE 1. Create a folder with a long name 2. Go into folder 3. profit OBSERVED RESULT EXPECTED RESULT Operating System: Artix Linux KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 Kernel Version: 5.4.54-1-lts OS Type: 64-bit Processors: 4 × Intel® Core™ i5-3210M CPU @ 2.50GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425570] Long folder names create too much padding in breadcrumb
https://bugs.kde.org/show_bug.cgi?id=425570 --- Comment #1 from Squeaky Pancakes --- Created attachment 131028 --> https://bugs.kde.org/attachment.cgi?id=131028=edit normal amount of padding -- You are receiving this mail because: You are watching all bug changes.
[frameworks-purpose] [Bug 419170] Dolphin 19.12.3 crach using TX with bluetooth
https://bugs.kde.org/show_bug.cgi?id=419170 Nicolas Fella changed: What|Removed |Added CC||mobul...@gmail.com --- Comment #4 from Nicolas Fella --- *** Bug 425565 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425565] Dolphin crashed when send 2nd time a random file in KDE Connect to phone
https://bugs.kde.org/show_bug.cgi?id=425565 Nicolas Fella changed: What|Removed |Added Resolution|--- |DUPLICATE CC||nicolas.fe...@gmx.de Status|REPORTED|RESOLVED --- Comment #1 from Nicolas Fella --- *** This bug has been marked as a duplicate of bug 419170 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423014] kwin_x11 black screen with Depth 30 and compositing (intel and amdgpu)
https://bugs.kde.org/show_bug.cgi?id=423014 Han Prower changed: What|Removed |Added CC||mafr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425560] Horizontal margins and scroll/paint artefact regression
https://bugs.kde.org/show_bug.cgi?id=425560 --- Comment #9 from RJVB --- (Posted too quickly, because speaking of flaws:) I *could* see myself use this kind of feature if it had a quick, easily accessible toggle, with long-running jobs in background tabs or windows. But in its currently implementation it will probably not be of any help because bringing the window or tab to the foreground will almost certainly remove the highlighting from the output that you hadn't seen yet. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 411042] try to edit channel in kaffeine 2.0.17 gives a crash
https://bugs.kde.org/show_bug.cgi?id=411042 peter.sch...@web.de changed: What|Removed |Added CC||peter.sch...@web.de --- Comment #1 from peter.sch...@web.de --- kaffeine 2.0.18 has still the same error. It seems that the channel editor can't handle channels who don't have an audio pid (like sat-transponders with test-channels), so in /src/dvb/dvbchanneldialog.cpp starting at line 960: const QPair = pmtParser.audioPids.at(0); QString text = QString::number(it.first); a crash is inevitable, because in this case "it" is NULL. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425560] Horizontal margins and scroll/paint artefact regression
https://bugs.kde.org/show_bug.cgi?id=425560 --- Comment #8 from RJVB --- I'll repeat myself once more, new features should only be enabled by default if they're truly useful for most users and/or if similar applications also do that. A showcase mechanism would remove the justification of enabling things just to throw them in the users' faces so they don't miss them. My guess is that terminal users are a conservative bunch who for the most part aren't interested in fancy new bells and whistles at all, but rather in continuity - who prefer to discover features when they discover a need for one. BTW, the feature that got on my wrong side is flawed in its concept of what new lines are. I haven't check if the highlight on the last set of lines disappears if you wait long enough before you cause the next scroll, but if there is such a timeout it'd be too long for me. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 423113] Deleted Faces still serve as information to Facial Recognition
https://bugs.kde.org/show_bug.cgi?id=423113 --- Comment #6 from Minh Nghia Duong --- (In reply to Kartik from comment #5) > Hi Nghia, > > The Top Level Connections for the Deleting button are done in > DigikamItemView. The Delete Button forms part of a FaceRejectionOverlay, and > the signal for pressing the delete button is set here: > https://invent.kde.org/graphics/digikam/-/blob/master/core/app/items/views/ > digikamitemview.cpp#L342. > > The > removeFaces(https://invent.kde.org/graphics/digikam/-/blob/master/core/app/ > items/views/digikamitemview.cpp#L411) method then delegates deletion to a > FacePipeline. I think you might be familiar with FacePipeline functionality. > DatabaseWriter works with the FacePipeline and picks up the package (when > its time for being processed arrives), and then calls the FaceUtils method > for actual removal of the Image-Tag association: > > See this connection for DatabaseWriter with FaceUtils: > https://invent.kde.org/graphics/digikam/-/blob/master/core/utilities/ > facemanagement/workers/databasewriter.cpp#L142. > > There's multithreaded implementations that lead to DatabaseWriter picking up > the package sent via FacePipeline, however it isn't necessary to worry about > that in my opinion. > > Kartik Thanks, As I see it, FaceUtils only manage face tag and retrieve identity, and FacePipelineFaceTagsIface doesn't hold the information of the registered face embedding. Therefore in order to delete the face embedding in the database, we have to add an additional association between face item and face embedding. If I do it now, it will add up more conflicts to our projects. Therefore I will find a way to do it after the 2 projects merged. Nghia -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425483] Plasma crash after Laravel throw exception
https://bugs.kde.org/show_bug.cgi?id=425483 --- Comment #6 from Feathers And Down --- Just to add: if you say "emoji" related problem, should be something like this: https://bugs.kde.org/attachment.cgi?id=131026 ? Seems is where point your advice. Thanks in advance -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425483] Plasma crash after Laravel throw exception
https://bugs.kde.org/show_bug.cgi?id=425483 --- Comment #5 from Feathers And Down --- Created attachment 131026 --> https://bugs.kde.org/attachment.cgi?id=131026=edit Emoji at taskbar Emoji at task bar beside favicon -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 416007] Crash on startup
https://bugs.kde.org/show_bug.cgi?id=416007 Francis Herne changed: What|Removed |Added CC||m...@flherne.uk Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Francis Herne --- This report doesn't provide enough information to identify the problem. Good that it seems to have been fixed. For future reference: Often removing ~/.cache/kdevduchain/ resolves crash-on-start issues (there should be a dialog asking to do that when starting after a crash). Otherwise there may be a file in your project or its dependencies that triggers some parser bug. There's unlikely to be an AppImage with debug symbols, but KDevelop has quite conservative dependencies - you should always be able to compile KDevelop using the system library versions found the latest release of Ubuntu LTS or of most other distros. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425483] Plasma crash after Laravel throw exception
https://bugs.kde.org/show_bug.cgi?id=425483 --- Comment #4 from Feathers And Down --- Oh, thanks for reply. I've commented this: https://bugs.kde.org/show_bug.cgi?id=425483#c2 related to a buggy (for me) kernel version. Currently I got same issue with a previous 5.3.18-lp152.26. So if is an emoji the culprit Is there a way to mitigate? my all day opensuse work station stuck my job :-(. Thanks in advance. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418922] On large document, merging down a layer results in different layer getting selected after the merge
https://bugs.kde.org/show_bug.cgi?id=418922 Dmitry Kazakov changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/8fd316da1 |hics/krita/commit/87d27964b |1d6ec5c8a129bc88dd042fb0bcd |5893f67c95deb03d73198a8acb6 |c659|849a --- Comment #3 from Dmitry Kazakov --- Git commit 87d27964b5893f67c95deb03d73198a8acb6849a by Dmitry Kazakov. Committed on 19/08/2020 at 22:09. Pushed by dkazakov into branch 'master'. Fix temporary wrongly selected layer when merging down huge layers The problem happened because of our workaround for Qt's removed item avoidance algorithm. On element removal, Qt selects an item above that, but we need a reverse, below it. The previous implementation just tried to fix Qt's behavior after the removal, but that didn't seem to work correctly in case of merge down. Therefore, this patch implements a special signal that is fired *before* beginRemoveRows(), that fixes the selection before Qt can lay its hands on it. Related: bug 345601 M +15 -0libs/ui/kis_node_filter_proxy_model.cpp M +4-0libs/ui/kis_node_filter_proxy_model.h M +1-0libs/ui/kis_node_model.cpp M +1-0libs/ui/kis_node_model.h M +9-9plugins/dockers/layerdocker/LayerBox.cpp M +1-1plugins/dockers/layerdocker/LayerBox.h https://invent.kde.org/graphics/krita/commit/87d27964b5893f67c95deb03d73198a8acb6849a -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418922] On large document, merging down a layer results in different layer getting selected after the merge
https://bugs.kde.org/show_bug.cgi?id=418922 Dmitry Kazakov changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/8fd316da1 ||1d6ec5c8a129bc88dd042fb0bcd ||c659 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #2 from Dmitry Kazakov --- Git commit 8fd316da11d6ec5c8a129bc88dd042fb0bcdc659 by Dmitry Kazakov. Committed on 19/08/2020 at 22:08. Pushed by dkazakov into branch 'krita/4.3'. Fix temporary wrongly selected layer when merging down huge layers The problem happened because of our workaround for Qt's removed item avoidance algorithm. On element removal, Qt selects an item above that, but we need a reverse, below it. The previous implementation just tried to fix Qt's behavior after the removal, but that didn't seem to work correctly in case of merge down. Therefore, this patch implements a special signal that is fired *before* beginRemoveRows(), that fixes the selection before Qt can lay its hands on it. Related: bug 345601 M +15 -0libs/ui/kis_node_filter_proxy_model.cpp M +4-0libs/ui/kis_node_filter_proxy_model.h M +1-0libs/ui/kis_node_model.cpp M +1-0libs/ui/kis_node_model.h M +9-9plugins/dockers/layerdocker/LayerBox.cpp M +1-1plugins/dockers/layerdocker/LayerBox.h https://invent.kde.org/graphics/krita/commit/8fd316da11d6ec5c8a129bc88dd042fb0bcdc659 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 345601] On deleting a layer, the layer under the deleted layer should be selected, not the one above
https://bugs.kde.org/show_bug.cgi?id=345601 --- Comment #4 from Dmitry Kazakov --- Git commit 8fd316da11d6ec5c8a129bc88dd042fb0bcdc659 by Dmitry Kazakov. Committed on 19/08/2020 at 22:08. Pushed by dkazakov into branch 'krita/4.3'. Fix temporary wrongly selected layer when merging down huge layers The problem happened because of our workaround for Qt's removed item avoidance algorithm. On element removal, Qt selects an item above that, but we need a reverse, below it. The previous implementation just tried to fix Qt's behavior after the removal, but that didn't seem to work correctly in case of merge down. Therefore, this patch implements a special signal that is fired *before* beginRemoveRows(), that fixes the selection before Qt can lay its hands on it. Related: bug 418922 M +15 -0libs/ui/kis_node_filter_proxy_model.cpp M +4-0libs/ui/kis_node_filter_proxy_model.h M +1-0libs/ui/kis_node_model.cpp M +1-0libs/ui/kis_node_model.h M +9-9plugins/dockers/layerdocker/LayerBox.cpp M +1-1plugins/dockers/layerdocker/LayerBox.h https://invent.kde.org/graphics/krita/commit/8fd316da11d6ec5c8a129bc88dd042fb0bcdc659 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 345601] On deleting a layer, the layer under the deleted layer should be selected, not the one above
https://bugs.kde.org/show_bug.cgi?id=345601 --- Comment #5 from Dmitry Kazakov --- Git commit 87d27964b5893f67c95deb03d73198a8acb6849a by Dmitry Kazakov. Committed on 19/08/2020 at 22:09. Pushed by dkazakov into branch 'master'. Fix temporary wrongly selected layer when merging down huge layers The problem happened because of our workaround for Qt's removed item avoidance algorithm. On element removal, Qt selects an item above that, but we need a reverse, below it. The previous implementation just tried to fix Qt's behavior after the removal, but that didn't seem to work correctly in case of merge down. Therefore, this patch implements a special signal that is fired *before* beginRemoveRows(), that fixes the selection before Qt can lay its hands on it. Related: bug 418922 M +15 -0libs/ui/kis_node_filter_proxy_model.cpp M +4-0libs/ui/kis_node_filter_proxy_model.h M +1-0libs/ui/kis_node_model.cpp M +1-0libs/ui/kis_node_model.h M +9-9plugins/dockers/layerdocker/LayerBox.cpp M +1-1plugins/dockers/layerdocker/LayerBox.h https://invent.kde.org/graphics/krita/commit/87d27964b5893f67c95deb03d73198a8acb6849a -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424311] Severe Rendering Issues on Latest Nvidia Driver (450.57) (Arch)
https://bugs.kde.org/show_bug.cgi?id=424311 --- Comment #30 from Erik Kurzinger --- Are you certain this is a regression in the 450.57 driver? We've reproduced the issue internally at NVIDIA, but also observe similar corruption with a 440 series driver. It is possible the regression was actually caused by another package that just happened to be updated around the same time? One of KDE's components, Qt, or the kernel might be suspects. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 416007] Crash on startup
https://bugs.kde.org/show_bug.cgi?id=416007 --- Comment #1 from Ian H --- seems to be fixed in the latest 5.5.80 beta -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 411956] Fails to build against Python 3.8
https://bugs.kde.org/show_bug.cgi?id=411956 --- Comment #7 from Francis Herne --- Those files should not be byte-compiled. They are never intended to be executed; kdev-python parses them as-is to provide information about the relevant modules. Compiling or executing them in any other way will not do anything useful and may cause problems. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 425569] New: Ekos: HA limit interferes with meridian flip
https://bugs.kde.org/show_bug.cgi?id=425569 Bug ID: 425569 Summary: Ekos: HA limit interferes with meridian flip Product: kstars Version: git Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: co...@mimas.ru Target Milestone: --- Created attachment 131025 --> https://bugs.kde.org/attachment.cgi?id=131025=edit Ekos log SUMMARY Enabled HA limit may throw Ekos off in the middle of meridian flip. See the log after 2020-08-16T00:49:54.064 Mount is Celestron AVX. I have RA tracking limit set there to 20 degrees, which should be bigger than Ekos HA limit and flip tolerance. STEPS TO REPRODUCE 1. Have HA limit set to 1h. 2. Have meridian flip enabled at 0.5h. 3. Run a job that crosses the meridian. OBSERVED RESULT While the mount is moving for flip, the HA limit warning is raised and the mount is stopped in the middle. Ekos proceeds as if the mount moved where it is supposed to. Moreover, Ekos seemigly changes its desired target coordinates to where the mount was stopped. So, it that successfully aligns to wrong coordinates and happily starts capturing. EXPECTED RESULT Align module should not change its target in the middle of a job for any reason! HA limits should not restrain the meridian flip if everything was OK just before the flip started. Perhaps, disable it entirely for the duration of the flip slew. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 20.04 amd64 (available in About System) KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION kstars-bleeding from PPA -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 425568] New: Kmail: New settings will be not shown directly after creation
https://bugs.kde.org/show_bug.cgi?id=425568 Bug ID: 425568 Summary: Kmail: New settings will be not shown directly after creation Product: kmail2 Version: 5.14.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: config dialog Assignee: kdepim-b...@kde.org Reporter: e605.male...@gmail.com Target Milestone: --- SUMMARY Settings for identity, receiving and sending will be not displayed after creation directly. They will be shown after log off and relog in as user. STEPS TO REPRODUCE 1. kmail -> call menue settings -> entries -> identity or receiving or sending 2. create a new identity for example and confirm all entries by the ok button 3. select the new identity and press the modify button 4. every data field is empty or has a standard value but shows not what was filled in by creation. 5. quit kmail and log off 6. relog in and start kmail OBSERVED RESULT 7. in the settings the data of the new identity will be shown. EXPECTED RESULT After new identity is created it is to shown at once under the modify button. No quitting of Kmail and no log off with relog in. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.3.18-lp152.33 (openSuSe Leap 15.2) (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.
[kstars] [Bug 425567] New: Guiding calibration failure after meridian flip leaves Ekos idle
https://bugs.kde.org/show_bug.cgi?id=425567 Bug ID: 425567 Summary: Guiding calibration failure after meridian flip leaves Ekos idle Product: kstars Version: git Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: co...@mimas.ru Target Milestone: --- Created attachment 131024 --> https://bugs.kde.org/attachment.cgi?id=131024=edit Ekos log SUMMARY After meridian flip, if guiding calibration fails, Ekos just sits idle and does not retry anything. See the log after 2020-08-15T00:54:47.275. STEPS TO REPRODUCE 1. Have a job with track+focus+align+guide that crosses the meridian. Meridian flip is enabled. 2. Wait until transit. 3. Guider loses the guide star while in the 'DEC drifting reverse...' stage. OBSERVED RESULT Nothing happens. After 2 minutes I clicked the Guide button and it picked up from there and continued running the schedule. EXPECTED RESULT It should retry the guiding or step back and restart the whole job. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 20.04 amd64 (available in About System) KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION kstars-bleeding from PPA -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422426] Implement Wayland Primary Selection Protocol bridge with XWayland
https://bugs.kde.org/show_bug.cgi?id=422426 --- Comment #7 from David Edmundson --- Both. Bridge as you say is simple just missing but I have a pending rewrite of the brige to get rid of the internal connection, so I want to finish that first. Then it should be just a few lines. I had spoken to someone from the GTK team about implementing it. Paraphrasing the response it was "we should eventually, patches welcome" >So it should not be too hard to support the legacy version, or is it? Not hard, but it'd take about as much effort as just patching GTK ourselves, so it's where I'd rather see time spent. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 425566] New: Ekos flat frame automatic ADU algorithm is erroneous
https://bugs.kde.org/show_bug.cgi?id=425566 Bug ID: 425566 Summary: Ekos flat frame automatic ADU algorithm is erroneous Product: kstars Version: git Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: co...@mimas.ru Target Milestone: --- Created attachment 131023 --> https://bugs.kde.org/attachment.cgi?id=131023=edit Ekos log SUMMARY Exposure time estimator jumps up and down in the range of 1000x. I set the start time a bit too early and it was getting brighter quickly while Ekos was trying to figure out the exposure time. STEPS TO REPRODUCE 1. Set exposure duration to 1s, type Flat, ADU target 4, tolerance 5000, 64 frames. 2. Add sequence to the schedule, starting about an hour before dawn. 3. Start the scheduler. OBSERVED RESULT See the log after 2020-08-16T05:14:59.738. It starts the job normally, but jumps in its estimation of a good exposure time between ~0.1s and ~100s. Occasionally it settles and makes a good number of exposures. EXPECTED RESULT As Sun goes up and ADU goes over tolerable 45000, it should make little adjustments in the right direction. I expect one or two trial frames before it finds new good exposure time. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 20.04 amd64 (available in About System) KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION kstars-bleeding from PPA -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 419290] Fails to build against Python 3.9
https://bugs.kde.org/show_bug.cgi?id=419290 Francis Herne changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kdev ||elop/kdev-python/commit/05e ||95cac74b0bb3595a6d97da07a12 ||b907385be5 Status|CONFIRMED |RESOLVED --- Comment #3 from Francis Herne --- Git commit 05e95cac74b0bb3595a6d97da07a12b907385be5 by Francis Herne. Committed on 19/08/2020 at 20:36. Pushed by flherne into branch '5.6'. Initial support for CPython 3.9 This reformats our AST to match that introduced upstream by https://bugs.python.org/issue34822 and adjusts the conversion from older Python versions' AST to match. ExtendedSliceAst is removed, in favour of a TupleAst containing SliceAsts and/or other expressions. IndexAst is removed, instead non-slice index expressions are direct children of SubscriptAst. SliceAst and EllipsisAst are now subclasses of ExpressionAst. In the latter case I don't understand how it wasn't broken before. --- The stdlib docfiles are not updated. There aren't many changes to builtins in 3.9, but we do need a system to re-generate these - perhaps based on Typeshed. In CPython 3.8 and 3.9 there are several changes to the parser that could be useful to us -- particularly end_lineno and end_col_offset. This patch doesn't attempt to take advantage of them. M +2-2CMakeLists.txt M +2-2duchain/declarationbuilder.cpp M +2-2duchain/expressionvisitor.cpp M +2-17 parser/ast.cpp M +3-24 parser/ast.h M +0-10 parser/astdefaultvisitor.cpp M +0-4parser/astdefaultvisitor.h M +0-2parser/astvisitor.cpp M +0-2parser/astvisitor.h M +2-0parser/conversionGenerator.py M +22 -5parser/generated.h R +4-3parser/python39.sdef [from: parser/python38.sdef - 096% similarity] https://invent.kde.org/kdevelop/kdev-python/commit/05e95cac74b0bb3595a6d97da07a12b907385be5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425483] Plasma crash after Laravel throw exception
https://bugs.kde.org/show_bug.cgi?id=425483 David Edmundson changed: What|Removed |Added Assignee|k...@davidedmundson.co.uk|plasma-b...@kde.org Component|general |generic-crash --- Comment #3 from David Edmundson --- ?Thread 8 (Thread 0x7f6d9dc6c700 (LWP 12006)): [KCrash Handler] #4 std::__atomic_base::operator++ (this=0x15bd) at /usr/include/c++/7/bits/atomic_base.h:296 #5 QAtomicOps::ref (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:265 #6 QBasicAtomicInteger::ref (this=0x15bd) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:114 #7 QRawFontPrivate::setFontEngine (engine=0x15b1, this=0x7f6d9818a900) at text/qrawfont_p.h:128 #8 glyphRunWithInfo (fontEngine=0x15b1, glyphLayout=..., pos=..., flags=..., selectionX=..., selectionWidth=..., glyphsStart=0, glyphsEnd=0, logClusters=, textPosition=0, textLength=35) at text/qtextlayout.cpp:2230 #9 0x7f6df70b9250 in QTextLine::glyphRuns (this=this@entry=0x7f6d9dc694d0, from=from@entry=0, length=) at text/qtextlayout.cpp:2413 #10 0x7f6dfa8ec81c in QQuickTextNodeEngine::addGlyphsInRange (this=this@entry=0x7f6d9dc69470, rangeStart=rangeStart@entry=0, rangeLength=rangeLength@entry=35, color=..., backgroundColor=..., selectionStart=selectionStart@entry=-1, selectionEnd=-1) at /usr/src/debug/libqt5-qtdeclarative-5.12.7-lp152.2.2.x86_64/src/quick/items/qquicktextnodeengine.cpp:593 #11 0x7f6dfa8ecda7 in QQuickTextNodeEngine::addGlyphsForRanges (this=this@entry=0x7f6d9dc69470, ranges=..., start=start@entry=0, end=35, selectionStart=selectionStart@entry=-1, selectionEnd=selectionEnd@entry=-1) at /usr/src/debug/libqt5-qtdeclarative-5.12.7-lp152.2.2.x86_64/src/quick/items/qquicktextnodeengine.cpp:565 We have a known crash in Qt if rendering a QQuickText item with an emoji/UTF-8 in it, from the trace it's similar. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425560] Horizontal margins and scroll/paint artefact regression
https://bugs.kde.org/show_bug.cgi?id=425560 --- Comment #7 from tcanabr...@kde.org --- We are thinking in adding for next version the information of what changed on first run, so this will not happen again, I mean, things will be implemented, and enabled by default - but we will showcase them before the app runs, with luck this is approved. On Wed, 19 Aug 2020 at 20:52 RJVB wrote: > https://bugs.kde.org/show_bug.cgi?id=425560 > > > > --- Comment #6 from RJVB --- > > That's called change blindness and it's a real thing, but apparently not so > > much in terminal emulators. I've been trying a whole bunch of those > recently > > and if they offer the feature it's off by default. Not too surprising > either, > > because change blindness usually occurs only when you do not induce change > > yourself, as with scrolling. > > > > Turning new features on by default is a good idea if they're not intrusive > and > > likely to be useful for a majority of the user population and don't look > like a > > weird bug. How would you feel if someone added a "reset to default" > feature to > > the profile settings dialog and turned that on by default because it's > useful > > to review your settings during an upgrade ... or would you prefer to get a > > suggestion to do so (as I think vlc still does after an upgrade)? > > > > -- > > You are receiving this mail because: > > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425565] New: Dolphin crashed when send 2nd time a random file in KDE Connect to phone
https://bugs.kde.org/show_bug.cgi?id=425565 Bug ID: 425565 Summary: Dolphin crashed when send 2nd time a random file in KDE Connect to phone Product: dolphin Version: 20.08.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: mobul...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.08.0) Qt Version: 5.14.2 Frameworks Version: 5.73.0 Operating System: Linux 5.4.0-42-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.19 -- Information about the crash: - What I was doing when the application crashed: Try to send the next choosed file in Dolphin with KDE Connect to phone. (right click -> Share -> Send To Device -> Choose a device to send to: -> my phone) The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7f79fea5e907 in QQmlData::wasDeleted (object=0x55871d0165d0) at ../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/qml/qqmldata_p.h:338 #5 QV4::QObjectWrapper::wrap (object=0x55871d0165d0, engine=0x55871c31fdb0) at jsruntime/qv4qobjectwrapper_p.h:213 #6 loadProperty (v4=0x55871c31fdb0, object=0x55871cb07390, property=...) at jsruntime/qv4qobjectwrapper.cpp:139 #7 0x7f79fea7fec7 in QV4::Moth::VME::interpret (frame=0x7ffcca89f280, engine=0x55871c31fdb0, code=0x7f79f01d12c2 ":\n:\v\030\006\002") at jsruntime/qv4vme_moth.cpp:638 #8 0x7f79fea853ef in QV4::Moth::VME::exec (frame=frame@entry=0x7ffcca89f280, engine=engine@entry=0x55871c31fdb0) at jsruntime/qv4vme_moth.cpp:463 #9 0x7f79fea14dcd in QV4::Function::call (this=this@entry=0x55871cff5090, thisObject=, argv=argv@entry=0x7f79e7023500, argc=, context=) at jsruntime/qv4function.cpp:69 #10 0x7f79feba3b47 in QQmlJavaScriptExpression::evaluate (this=this@entry=0x55871ccaab50, callData=callData@entry=0x7f79e70234d0, isUndefined=isUndefined@entry=0x7ffcca89f47f) at ../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/jsruntime/qv4value_p.h:343 #11 0x7f79feba99a3 in QQmlBinding::evaluate (this=this@entry=0x55871ccaab50, isUndefined=isUndefined@entry=0x7ffcca89f47f) at ../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/jsruntime/qv4jscall_p.h:95 #12 0x7f79febade3d in QQmlNonbindingBinding::doUpdate (this=0x55871ccaab50, watcher=..., flags=..., scope=...) at qml/qqmlbinding.cpp:246 #13 0x7f79febaac52 in QQmlBinding::update (this=0x55871ccaab50, flags=...) at qml/qqmlbinding.cpp:186 #14 0x7f79feb46efe in QQmlContextData::refreshExpressionsRecursive (this=, expression=0x55871ccaab50) at qml/qqmlcontext.cpp:722 #15 0x7f79feb46ee9 in QQmlContextData::refreshExpressionsRecursive (this=, expression=0x55871d3f4490) at qml/qqmlcontext.cpp:719 #16 0x7f79feb46ee9 in QQmlContextData::refreshExpressionsRecursive (this=this@entry=0x55871c8c1e30, expression=0x55871d3f45f0) at qml/qqmlcontext.cpp:719 #17 0x7f79feb4739a in QQmlContextData::refreshExpressionsRecursive (this=0x55871c8c1e30, isGlobal=false) at qml/qqmlcontext.cpp:751 #18 0x7f79feb4749f in QQmlContextData::refreshExpressionsRecursive (this=0x55871c8c1d70, isGlobal=) at qml/qqmlcontext.cpp:741 #19 0x7f79feb47438 in QQmlContextData::refreshExpressionsRecursive (this=0x55871cff58c0, isGlobal=) at qml/qqmlcontext.cpp:761 #20 0x7f79feb4761f in QQmlContextData::refreshExpressions (this=this@entry=0x55871cdca730) at qml/qqmlcontext.cpp:788 #21 0x7f79feb2afe8 in QQmlEngine::retranslate (this=) at qml/qqmlengine.cpp:1434 #22 0x7f79fff002a9 in QObject::event (this=0x55871cac3910, e=0x7f79e01c3310) at kernel/qobject.cpp:1339 #23 0x7f7a00abfcc3 in QApplicationPrivate::notify_helper (this=this@entry=0x55871be456a0, receiver=receiver@entry=0x55871cac3910, e=e@entry=0x7f79e01c3310) at kernel/qapplication.cpp:3685 #24 0x7f7a00ac8f40 in QApplication::notify (this=0x7ffcca89fda0, receiver=0x55871cac3910, e=0x7f79e01c3310) at kernel/qapplication.cpp:3431 #25 0x7f79ffed278a in QCoreApplication::notifyInternal2 (receiver=0x55871cac3910, event=0x7f79e01c3310) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:153 #26 0x7f79ffed4f74 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55871be3ac70) at kernel/qcoreapplication.cpp:1815 #27 0x7f79fff2bb87 in postEventSourceDispatch (s=0x55871bea9410) at kernel/qeventdispatcher_glib.cpp:277 #28 0x7f79fdcfdfbd in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7f79fdcfe240 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x7f79fdcfe2e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x7f79fff2b1e2 in
[kwin] [Bug 424550] Pinning window to all desktops should hold window steady when switching
https://bugs.kde.org/show_bug.cgi?id=424550 Nate Graham changed: What|Removed |Added Version Fixed In||5.20 Resolution|NOT A BUG |FIXED Latest Commit||https://invent.kde.org/plas ||ma/kwin/commit/ed0b0ee925e4 ||d1be38606480c27e04257f44786 ||6 --- Comment #5 from Nate Graham --- Git commit ed0b0ee925e4d1be38606480c27e04257f447866 by Nate Graham. Committed on 19/08/2020 at 19:31. Pushed by ngraham into branch 'master'. [effects/cubeslide] Keep sticky windows on top of the cube by default This simply looks much better. FIXED-IN: 5.20 M +1-1effects/cubeslide/cubeslide.kcfg https://invent.kde.org/plasma/kwin/commit/ed0b0ee925e4d1be38606480c27e04257f447866 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425560] Horizontal margins and scroll/paint artefact regression
https://bugs.kde.org/show_bug.cgi?id=425560 --- Comment #6 from RJVB --- That's called change blindness and it's a real thing, but apparently not so much in terminal emulators. I've been trying a whole bunch of those recently and if they offer the feature it's off by default. Not too surprising either, because change blindness usually occurs only when you do not induce change yourself, as with scrolling. Turning new features on by default is a good idea if they're not intrusive and likely to be useful for a majority of the user population and don't look like a weird bug. How would you feel if someone added a "reset to default" feature to the profile settings dialog and turned that on by default because it's useful to review your settings during an upgrade ... or would you prefer to get a suggestion to do so (as I think vlc still does after an upgrade)? -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 425563] should treat \r in lyrics as new line
https://bugs.kde.org/show_bug.cgi?id=425563 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #5 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/multimedia/elisa/-/merge_requests/148 -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 425563] should treat \r in lyrics as new line
https://bugs.kde.org/show_bug.cgi?id=425563 --- Comment #4 from Nate Graham --- In fact I do! MR incoming. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 425563] should treat \r in lyrics as new line
https://bugs.kde.org/show_bug.cgi?id=425563 Nate Graham changed: What|Removed |Added Assignee|matthieu_gall...@yahoo.fr |n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 425563] should treat \r in lyrics as new line
https://bugs.kde.org/show_bug.cgi?id=425563 Nate Graham changed: What|Removed |Added CC||gagor...@gmail.com --- Comment #3 from Nate Graham --- *** Bug 418072 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 418072] Lyrics display sometimes doesn't show newlines
https://bugs.kde.org/show_bug.cgi?id=418072 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #8 from Nate Graham --- I'm 99% sure this has the same root cause as Bug 425563 after working on a patch to fix that for the reporter and finding that it fixes all the cases of this happening to my own music. *** This bug has been marked as a duplicate of bug 425563 *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 416403] During account wizard using @protonmail.com, get "Kmail could not convert value of setting 'Authentication' to required type"
https://bugs.kde.org/show_bug.cgi?id=416403 ryantg changed: What|Removed |Added CC||grat...@fastmail.com --- Comment #24 from ryantg --- I used to experience this bug, but I just tried kmail again and it did not occur (using fastmail). Is it resolved? -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 425563] should treat \r in lyrics as new line
https://bugs.kde.org/show_bug.cgi?id=425563 Nate Graham changed: What|Removed |Added CC||n...@kde.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from Nate Graham --- I probably some of these myself, having used iTunes in macOS 9 to add lyrics to some of my songs when I was a kid. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424550] Pinning window to all desktops should hold window steady when switching
https://bugs.kde.org/show_bug.cgi?id=424550 --- Comment #4 from Nate Graham --- You're right, that probably should be set by default. It looks much nicer. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 406810] Dolphin and Konqueror consume a lot of CPU when Plasma Vault or encfs directory is open for a while
https://bugs.kde.org/show_bug.cgi?id=406810 --- Comment #30 from Henning --- Created attachment 131021 --> https://bugs.kde.org/attachment.cgi?id=131021=edit CPU-flags compared between i7-3930K, i5-4200U and Virtualbox VM on i5-4200U as announced in comment 29 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425564] New: SEGFAULT occurs in plasma when a certificate is untrusted
https://bugs.kde.org/show_bug.cgi?id=425564
Bug ID: 425564
Summary: SEGFAULT occurs in plasma when a certificate is
untrusted
Product: plasmashell
Version: 5.18.5
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: k...@davidedmundson.co.uk
Reporter: aleprez...@pm.me
CC: plasma-b...@kde.org
Target Milestone: 1.0
Application: plasmashell (5.18.5)
Qt Version: 5.13.2
Frameworks Version: 5.70.0
Operating System: Linux 5.7.15-100.fc31.x86_64 x86_64
Windowing system: X11
Distribution: Fedora 31 (KDE Plasma)
-- Information about the crash:
In this case I was just using Firefox and plasma had a segmentation fault,
something that I've already experienced, I suppose due to the same problem.
It also happens that when I share a URL between applications(like a web link
from konsole or kdeconnect) and the cert is untrusted, Kio complains about it
("The issuer certificate of a locally looked up certificate could not be
found"), somethimes even plasma chrashes.
Please note that in this case, no link has been shared between apps, just
firefox running.
The crash can be reproduced sometimes.
-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe04f5cf680 (LWP 5361))]
Thread 36 (Thread 0x7fdfa0a8f700 (LWP 40987)):
#0 0x7fe001b3fb38 in pa_mainloop_dispatch () from /lib64/libpulse.so.0
#1 0x7fe001b3fea2 in pa_mainloop_iterate () from /lib64/libpulse.so.0
#2 0x7fe001b3ff40 in pa_mainloop_run () from /lib64/libpulse.so.0
#3 0x7fe001b4e0ed in thread () from /lib64/libpulse.so.0
#4 0x7fe001ae1dac in internal_thread_func () from
/usr/lib64/pulseaudio/libpulsecommon-13.99.so
#5 0x7fe04cf994e2 in start_thread () from /lib64/libpthread.so.0
#6 0x7fe04d7916c3 in clone () from /lib64/libc.so.6
Thread 35 (Thread 0x7fdfa17fa700 (LWP 36337)):
#0 0x7fe04cf9fd45 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1 0x7fe04db26943 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/lib64/libQt5Core.so.5
#2 0x7fe04db269d1 in QWaitCondition::wait(QMutex*, unsigned long) () from
/lib64/libQt5Core.so.5
#3 0x7fe0025ffab0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /lib64/libKF5ThreadWeaver.so.5
#4 0x7fe00260373e in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) ()
from /lib64/libKF5ThreadWeaver.so.5
#5 0x7fe0025fec82 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/lib64/libKF5ThreadWeaver.so.5
#6 0x7fe002603799 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) ()
from /lib64/libKF5ThreadWeaver.so.5
#7 0x7fe0025fec82 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/lib64/libKF5ThreadWeaver.so.5
#8 0x7fe002603799 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) ()
from /lib64/libKF5ThreadWeaver.so.5
#9 0x7fe0025fec82 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/lib64/libKF5ThreadWeaver.so.5
#10 0x7fe002601713 in ThreadWeaver::Thread::run() () from
/lib64/libKF5ThreadWeaver.so.5
#11 0x7fe04db20e26 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#12 0x7fe04cf994e2 in start_thread () from /lib64/libpthread.so.0
#13 0x7fe04d7916c3 in clone () from /lib64/libc.so.6
Thread 34 (Thread 0x7fdfa1ffb700 (LWP 36336)):
#0 0x7fe04cf9fd45 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1 0x7fe04db26943 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/lib64/libQt5Core.so.5
#2 0x7fe04db269d1 in QWaitCondition::wait(QMutex*, unsigned long) () from
/lib64/libQt5Core.so.5
#3 0x7fe0025ffab0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /lib64/libKF5ThreadWeaver.so.5
#4 0x7fe00260373e in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) ()
from /lib64/libKF5ThreadWeaver.so.5
#5 0x7fe0025fec82 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/lib64/libKF5ThreadWeaver.so.5
#6 0x7fe002601713 in ThreadWeaver::Thread::run() () from
/lib64/libKF5ThreadWeaver.so.5
#7 0x7fe04db20e26 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8 0x7fe04cf994e2 in start_thread () from /lib64/libpthread.so.0
#9 0x7fe04d7916c3 in clone () from /lib64/libc.so.6
Thread 33 (Thread 0x7fdfa27fc700 (LWP 36335)):
#0 0x7fe04cf9fd45 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1 0x7fe04db26943 in QWaitCondition::wait(QMutex*,
[frameworks-kio] [Bug 406810] Dolphin and Konqueror consume a lot of CPU when Plasma Vault or encfs directory is open for a while
https://bugs.kde.org/show_bug.cgi?id=406810 --- Comment #29 from Henning --- Assuming that the Dolphin+EncFS-problem is a result of the CPU/CPU-flags in conjunction with the compiler/compiler-flags I also did some further investigations. Out of habit I used "Oracle VM Virtualbox" with host-extensions installed for USB support. (No guest-extensions installed by me; Virtualbox 6.1) The results: i5-4200U host: Kubuntu 20.04.1 works fine with Dolphin+EncFS VM on that i5-4200U host: Kubuntu 20.04.1 shows the Dolphin+EncFS-problem i7-3930K host: Kubuntu 20.04.1 shows the Dolphin+EncFS-problem Therefore I took a look at the CPU-flags by comparing the output of /proc/cpuinfo. If I can attach the LO-calc-file, I will do so. But from my point of view, these flags are the most interesting: Flag only on the two systems where the problem appears (VM@4200U and 3930K): x2apic Flags missing on the two systems where the problem appears but available on the working system (4200U): bmi1, bmi2, cpuid_fault, ept_ad, erms, f16c, fma, sdbg, smep, tsc_adjust. There are a lot flags missing only in the VM and some others are missing on the 3930K only. Hence I listed all flags that are common on the systems where the Dolphin+EncFS-problem appears. Since I don't really know much about CPU- or compiler-flags, I also played around with CPU-microcode and patches on the native 3930K. Booting without any microcode loaded to the CPU by Kubuntu does not solve the Dolphin+EncFS-problem just as adding "mitigations=off" to grub. Does anyone have an old ISO-image of Neon with Plasma 5.18? Testing Dolphin+EncFS there inside a VM would be quite interesting! P.S.: A Kubuntu 20.04.1-VM on the i5-4200U running Win10 as host OS also shows the Dolphin+EncFS-problem. -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 423428] WARNING: Could not lex literal_block as "cmake"
https://bugs.kde.org/show_bug.cgi?id=423428 ratijas changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from ratijas --- Fixed by https://invent.kde.org/frameworks/extra-cmake-modules/-/commit/ada528dc4b71cb5cc16902aea2b9e16b3f4b53f2?merge_request_iid=16 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425359] First face tag moves intermittently
https://bugs.kde.org/show_bug.cgi?id=425359 --- Comment #8 from Tom Cunningham --- Another data point, although just anecdotal: after performing edits and returning to the preview screen, just before tagging if I click on another thumbnail and then return to the original, I can tag and the problem does not appear. If I tag immediately after the edits, the problem more often than not recurs. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 425563] should treat \r in lyrics as new line
https://bugs.kde.org/show_bug.cgi?id=425563 --- Comment #1 from ratijas --- Created attachment 131020 --> https://bugs.kde.org/attachment.cgi?id=131020=edit track with \r in lyrics tag -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 425563] New: should treat \r in lyrics as new line
https://bugs.kde.org/show_bug.cgi?id=425563 Bug ID: 425563 Summary: should treat \r in lyrics as new line Product: elisa Version: 20.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: gm...@ratijas.tk Target Milestone: --- SUMMARY Not exactly sure about standardization of this feature, but I recall my iPod used to render all my media library's lyrics correctly, even so many of them apparently have always been containing \r instead of proper \n line breaks. I could submit my copy of Red Hot Chili Peppers - Dani California to the attachment as an evidence, but I'm not sure about legal aspect of such action. STEPS TO REPRODUCE 1. Get an audio file with \r line breaks in lyrics; 2. Enjoy huge one-liner. OBSERVED RESULT All lyrics text squashed in one logical line, split into multiple physical only at 'word' boundaries as usual. EXPECTED RESULT Normal verses, just as if using \n for line breaks. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Not relevant (available in About System) KDE Plasma Version: Not relevant KDE Frameworks Version: Not relevant Qt Version: 5.15.0-4 ADDITIONAL INFORMATION I took the audio file of '1-01 Dani California.m4a' with python's mutagen library, and found there a '©lyr' tag containing lyrics with '\r' characters — just as i suspected. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 425535] Project (20.04.1) fails to load
https://bugs.kde.org/show_bug.cgi?id=425535 Arno Rog changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Assignee|j...@kdenlive.org |arno@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425560] Horizontal margins and scroll/paint artefact regression
https://bugs.kde.org/show_bug.cgi?id=425560 --- Comment #5 from tcanabr...@kde.org --- Well, I don't use this while developing konsole, but to scroll trough compilation errors or log files when I'm reading. sometimes the text is too similar and it's hard to keep track what scrolled, so this helps me. The enabled on by default is to encourage people to test the features, as most of the features - if off bu default - will not be visible to users. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-krunner] [Bug 423003] krunner crashes as soon as I start typing when PIM Contact Search plugin is enabled
https://bugs.kde.org/show_bug.cgi?id=423003 Benjamin Buch changed: What|Removed |Added CC||benni.b...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-krunner] [Bug 423003] krunner crashes as soon as I start typing when PIM Contact Search plugin is enabled
https://bugs.kde.org/show_bug.cgi?id=423003 tomas nackaerts changed: What|Removed |Added CC||tomas.nackae...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425557] Plasma freezes when Compositor set to use OpenGL, both 2.1 or 3.0. No freeze with Xrender
https://bugs.kde.org/show_bug.cgi?id=425557 --- Comment #2 from MichaelOF --- yes, that's my "rescue path" to systemctl isolate multi-user.target and systemctl isolate graphical.target to get my machine back to a working state, avoiding hard reboots. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425560] Horizontal margins and scroll/paint artefact regression
https://bugs.kde.org/show_bug.cgi?id=425560 --- Comment #4 from RJVB --- I was wondering if this wasn't a feature. Thing is, I don't see what it is useful for except for Konsole devs, so why turn it on automatically? Turning off the feature also got rid of the margin issue, thank goodness. FWIW: adding a timer so the bar disappears even without a viewport refresh would make it clear that this is a feature. As it is it can disappear for no apparent reason (for more casual users) esp. when focus-follows-mouse is on. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425253] systemd related commit breaks exporting env vars
https://bugs.kde.org/show_bug.cgi?id=425253 --- Comment #17 from Ahmad Samir --- Friendly ping. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 425503] QGIS3.10.4 installs on Kubuntu 20.04 but not KDE Neon 20.04
https://bugs.kde.org/show_bug.cgi?id=425503 --- Comment #1 from Peter Wibberley --- N.B. Andrew-63 was having a similar problem with KDE Neon 18.04 - https://gis.stackexchange.com/questions/351962/problem-installing-qgis-3-12-on-linux-kde-neon . -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 415339] Akonadi IMAP crashed on waking up from sleep
https://bugs.kde.org/show_bug.cgi?id=415339 Ahmad Samir changed: What|Removed |Added CC||devuran...@gmx.net --- Comment #12 from Ahmad Samir --- *** Bug 418599 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 418599] Crash when moving emails from one IMAP server to another
https://bugs.kde.org/show_bug.cgi?id=418599 Ahmad Samir changed: What|Removed |Added CC||a.samir...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Ahmad Samir --- *** This bug has been marked as a duplicate of bug 415339 *** -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 425518] Can't run English Title Case
https://bugs.kde.org/show_bug.cgi?id=425518 --- Comment #3 from Urs Fleisch --- Using the binary package kid3-3.8.3-Linux.tgz or the flatpak may work, but it will not solve the problem. Linux Mint is based on Ubuntu and on my Ubuntu installation it is working. Maybe there are some dependencies missing. Could you check if you have the following packages installed or try to install them using sudo apt install libqt5quick5 libqt5qml5 qml-module-qtquick-layouts qml-module-qtquick2 If this still does not help, check if "ldd /usr/lib/kid3/plugins/libqmlcommand.so" reports some "not found" libraries. If this still does not help, you could start kid3 with strace and check if it tries to load some files or libraries which are missing. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 424963] Search doesn't recieve focus
https://bugs.kde.org/show_bug.cgi?id=424963 --- Comment #7 from Leon De Andrade --- hmm can there still be something done? Some further information I can provide? -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 421589] Help button doesn't bring up the Klipper help page in Help Center
https://bugs.kde.org/show_bug.cgi?id=421589 aaronxn changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=425562 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 425562] New: Edit Identity > Help Button = Wrong URL
https://bugs.kde.org/show_bug.cgi?id=425562 Bug ID: 425562 Summary: Edit Identity > Help Button = Wrong URL Product: kontact Version: 5.13.3 Platform: unspecified URL: https://docs.kde.org/stable5/en/pim/kontact//kmail2/co nfigure-identity.html OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: aa...@abmlab.net Target Milestone: --- SUMMARY Wrong html link for help button at Settings > Configure KMail > Accounts > Edit Identity STEPS TO REPRODUCE Help button opens https://docs.kde.org/stable5/en/pim/kontact//kmail2/configure-identity.html OBSERVED RESULT Help button URL has a typo and when fixed it does not load or redirect to any help info pages. EXPECTED RESULT Help button should have the correct link. SOFTWARE/OS VERSIONS Not Applicable -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 421589] Help button doesn't bring up the Klipper help page in Help Center
https://bugs.kde.org/show_bug.cgi?id=421589 aaronxn changed: What|Removed |Added CC||aa...@abmlab.net -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 425561] New: kwallet should support Freedesktop Secret Service standard.
https://bugs.kde.org/show_bug.cgi?id=425561 Bug ID: 425561 Summary: kwallet should support Freedesktop Secret Service standard. Product: frameworks-kwallet Version: 5.73.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: va...@kde.org Reporter: deced...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- There are a few programs that need to access the desktop environment password manager and they do it using the Freedesktop Secret Service standard (https://specifications.freedesktop.org/secret-service/latest/) but KDE does not have any implementation for this. For example: "$ ayatana-webmail 2020-08-19 19:36:06,347: Ayatana Webmail: CRITICAL: The name org.freedesktop.secrets was not provided by any .service files" -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 425559] Add icon for KeePass 2 database format
https://bugs.kde.org/show_bug.cgi?id=425559 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/breeze-icons/-/merge_requests/37 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425560] Horizontal margins and scroll/paint artefact regression
https://bugs.kde.org/show_bug.cgi?id=425560 tcanabr...@kde.org changed: What|Removed |Added CC||tcanabr...@kde.org --- Comment #3 from tcanabr...@kde.org --- Configure Profile -> Scrolling -> Unmark "Highligth lines comming into view", but be assured that the new behavior with the blue line comming to view is really userful, and not a bug but intended behavior. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425560] Horizontal margins and scroll/paint artefact regression
https://bugs.kde.org/show_bug.cgi?id=425560 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Christoph Feck --- See bug 425408 comment 3 for the commit. *** This bug has been marked as a duplicate of bug 425408 *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425408] Vertical blue line appears at the left side of window when scrolling in Konsole 20.08.
https://bugs.kde.org/show_bug.cgi?id=425408 Christoph Feck changed: What|Removed |Added CC||rjvber...@gmail.com --- Comment #7 from Christoph Feck --- *** Bug 425560 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425560] Horizontal margins and scroll/paint artefact regression
https://bugs.kde.org/show_bug.cgi?id=425560 --- Comment #1 from RJVB --- I'd appreciate knowing which commits are responsible for this new behaviour so I can look into a fix or even a local workaround. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425560] New: Horizontal margins and scroll/paint artefact regression
https://bugs.kde.org/show_bug.cgi?id=425560
Bug ID: 425560
Summary: Horizontal margins and scroll/paint artefact
regression
Product: konsole
Version: master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: konsole-de...@kde.org
Reporter: rjvber...@gmail.com
Target Milestone: ---
Created attachment 131018
--> https://bugs.kde.org/attachment.cgi?id=131018=edit
screenshot showing the older konsole window on top of the newer version. The 2
windows should be identical.
SUMMARY
Somewhere between commits 473941dc96415e735afdf307f1f5b900af3c7d27
("18.11.70.88") and 4cf41db6336184e4ea217bec67c6bc3066c7ca46 ("20.11.70.5")
change was made that introduces what I consider a regression in the horizontal
margins used in the terminal view proper, as well as a painting artefact in new
regions that replace older content that was scrolled upwards in the view.
STEPS TO REPRODUCE
0. Install 473941dc96415e735afdf307f1f5b900af3c7d27 from git and open a konsole
window using that version.
1. Install 4cf41db6336184e4ea217bec67c6bc3066c7ca46 from git
2. Open a new konsole window
3. scroll down the prompt by hitting enter repeatedly or by executing a command
that generates enough output to provoke viewport scrolling.
OBSERVED RESULT
Note how the newer version has slightly larger horizontal margins inside the
window, leading to a 1 char. shorter linewidth (with Ubuntu Mono 11pt,
antialiased). Also note the bar (blueish in my case) that appears to the left
in newly painted content (and disappears in content that's scrolled upwards).
The margins do NOT correspond to the margins setting in the current profile;
they remain there when I set that parameter to 0. The parameter also doesn't
influence the artefact bar.
EXPECTED RESULT
Text should touch the viewport edges when the margins parameter is 0. No
artefacts should be visible.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: 5.6.19
(available in About System)
KDE Plasma Version: NA
KDE Frameworks Version: 5.60.0
Qt Version: 5.12.6 (as well as 5.9.8 after a single trivial revert)
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 424550] Pinning window to all desktops should hold window steady when switching
https://bugs.kde.org/show_bug.cgi?id=424550 --- Comment #3 from Aaron Wolf --- (In reply to Aaron Wolf from comment #2) > Oh, there's already an option existing! "Do not animate window on all > desktops" in the settings for the Cube effect, and this works correctly for > slide. So nevermind! It would be good if the cube animation had that option set by default, but whatever. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 425559] Add icon for KeePass 2 database format
https://bugs.kde.org/show_bug.cgi?id=425559 Carson Black changed: What|Removed |Added CC||uhh...@gmail.com Assignee|visual-des...@kde.org |uhh...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424550] Pinning window to all desktops should hold window steady when switching
https://bugs.kde.org/show_bug.cgi?id=424550 Aaron Wolf changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |NOT A BUG --- Comment #2 from Aaron Wolf --- Oh, there's already an option existing! "Do not animate window on all desktops" in the settings for the Cube effect, and this works correctly for slide. So nevermind! -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 409762] [wayland] Screenshots taken on displays with scaling lack resolution
https://bugs.kde.org/show_bug.cgi?id=409762 --- Comment #23 from Christoph Feck --- It would help if snapshots were saved with DPI information. A viewer could then decide if the images need to be scaled. -- You are receiving this mail because: You are watching all bug changes.
[kdenetwork-filesharing] [Bug 425203] If guest access to Samba shares is globally disabled, either warn the user ahead of time or prompt to turn it on
https://bugs.kde.org/show_bug.cgi?id=425203 --- Comment #4 from Nate Graham --- Thanks! However I'll admit I'm having trouble following your examples. This seems like an extraordinarily complicated permissions system. I don't think regular users will have a prayer of a chance of understanding this unless we abstract away most of that complication and present a subset of the features/permissions that can actually make sense and won't conflict with one another. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 409762] [wayland] Screenshots taken on displays with scaling lack resolution
https://bugs.kde.org/show_bug.cgi?id=409762 --- Comment #22 from Marvin Hagemeister --- As a user I'd expect screenshots to be always taken in the native resolution, regardless of whether I have multiple screens attached or not. I'd be confused if there is any downscaling happening behind the scenes. When doing a screenshot the point is to capture everything as is, and anything else seems to take away from that. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425520] Drop-downs in PDF form do not work
https://bugs.kde.org/show_bug.cgi?id=425520 Albert Astals Cid changed: What|Removed |Added Status|REPORTED|RESOLVED CC||aa...@kde.org Resolution|--- |UPSTREAM --- Comment #1 from Albert Astals Cid --- It's a bug of either the file, Adobe Reader/Chrome, or the PDF spec https://gitlab.freedesktop.org/poppler/poppler/-/merge_requests/613 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-krunner] [Bug 423003] krunner crashes as soon as I start typing when PIM Contact Search plugin is enabled
https://bugs.kde.org/show_bug.cgi?id=423003 Christoph Feck changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #46 from Christoph Feck --- Multiple reports show that the issue is not fixed in KF 5.73.0; reopening. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425525] Brush Settings options (size, ratio, etc.) don't remember which sensor you were looking at in certain cases
https://bugs.kde.org/show_bug.cgi?id=425525 Ahab Greybeard changed: What|Removed |Added CC||ahab.greybe...@hotmail.co.u ||k Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Ahab Greybeard --- I can confirm this for the 4.2.0 appimage and the latest Aug18 4.4.0 alpha (git c6ac82b) appimages. There is a pattern to the behaviour, with interesting exceptions (which may be stylus capability related) and an exception to the exceptions. I'm not going to bother describing them. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 425559] New: Add icon for KeePass 2 database format
https://bugs.kde.org/show_bug.cgi?id=425559 Bug ID: 425559 Summary: Add icon for KeePass 2 database format Product: Breeze Version: unspecified Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: ongun.ka...@gmail.com CC: kain...@gmail.com Target Milestone: --- The MIME type is defined as application/x-keepass2 by KeepassXC. https://github.com/keepassxreboot/keepassxc/blob/develop/share/linux/keepassxc.xml KeepassXC installs this icon: https://github.com/keepassxreboot/keepassxc/blob/develop/share/icons/application/scalable/mimetypes/application-x-keepassxc.svg -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 424963] Search doesn't recieve focus
https://bugs.kde.org/show_bug.cgi?id=424963 --- Comment #6 from Albert Astals Cid --- Can't reproduce. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 425387] Location bar autosuggestion broken
https://bugs.kde.org/show_bug.cgi?id=425387 --- Comment #2 from andydecle...@gmail.com --- Please do check over the conversation Nate linked. While this is broken, I've put kio-append-slash in the AUR, and I recommend to change your completion mode to "Dropdown List" (right click editable location bar). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420966] After tab-completing to a path (or typing a trailing slash) and hitting enter, Dolphin instead navigates to the first suggested subdirectory of that path
https://bugs.kde.org/show_bug.cgi?id=420966
--- Comment #18 from andydecle...@gmail.com ---
Additionally, with the default completion mode, the problematic behavior in the
title persists ("...or typing a trailing slash...").
While I would never want that, it is unclear to me if is intentional behavior.
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 425558] Option to not show a bell icon on the tab bar, it's distracting
https://bugs.kde.org/show_bug.cgi?id=425558 Albert Astals Cid changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Albert Astals Cid --- On the other hand, if i want ls/cd not to produce a bell, i can configure them not to actually produce a bell, so i guess that's the real fix. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403686] Add the ability to change application UI style like Kdenlive under KDE Plasma
https://bugs.kde.org/show_bug.cgi?id=403686 --- Comment #4 from Tyson Tan --- Yes, it can! I totally forgot about reporting this one. Thank you for telling me, and Thank Scott for making it work! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425407] Plasma dialogs not using Sliding Popups effect overlap an auto-hidden panel when it's visible
https://bugs.kde.org/show_bug.cgi?id=425407 twinshadows...@gmail.com changed: What|Removed |Added Assignee|twinshadows...@gmail.com|plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
