[plasmashell] [Bug 425576] New: Plasma crashes when i add spacer to panel.
https://bugs.kde.org/show_bug.cgi?id=425576 Bug ID: 425576 Summary: Plasma crashes when i add spacer to panel. Product: plasmashell Version: 5.19.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: anisimovkost...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.19.4) Qt Version: 5.15.0 Frameworks Version: 5.73.0 Operating System: Linux 5.8.0-1-pae i686 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Im clicked to Edit panel, the to add spacer and palsma crashed. Sorry for my english. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #5 QScopedPointer >::operator->() const (this=0x14) at /usr/include/qt5/QtCore/qscopedpointer.h:116 #6 qGetPtrHelper > const>(QScopedPointer > const&) (ptr=...) at /usr/include/qt5/QtCore/qglobal.h:1133 #7 QObject::d_func() const (this=0x10) at /usr/include/qt5/QtCore/qobject.h:132 #8 QObjectPrivate::get(QObject const*) (o=0x10) at /usr/include/qt5/QtCore/5.15.0/QtCore/private/qobject_p.h:341 #9 QQmlData::wasDeleted(QObject const*) (object=0x10) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.2.i386/include/QtQml/5.15.0/QtQml/private/../../../../../src/qml/qml/qqmldata_p.h:337 #10 QV4::QObjectWrapper::wrap(QV4::ExecutionEngine*, QObject*) (object=0x10, engine=0xc8e970) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.2.i386/src/qml/jsruntime/qv4qobjectwrapper_p.h:213 #11 loadProperty (property=..., object=0xcb17b0, v4=0xc8e970) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.2.i386/src/qml/jsruntime/qv4qobjectwrapper.cpp:139 #12 QV4::QObjectWrapper::getProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData*) (engine=0xc8e970, object=0xcb17b0, property=0x326b900) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.2.i386/src/qml/jsruntime/qv4qobjectwrapper.cpp:268 #14 QV4::QObjectWrapper::lookupGetter(QV4::Lookup*, QV4::ExecutionEngine*, QV4::Value const&) (lookup=0x332b908, engine=0xc8e970, object=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.2.i386/src/qml/jsruntime/qv4qobjectwrapper.cpp:895 #15 0xb72b0c99 in QV4::QObjectWrapper::virtualResolveLookupGetter(QV4::Object const*, QV4::ExecutionEngine*, QV4::Lookup*) (object=0xae4c16a0, engine=0xc8e970, lookup=0x332b908) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.2.i386/src/qml/jsruntime/qv4qobjectwrapper.cpp:883 #16 0xb723cf29 in QV4::Lookup::getterGeneric(QV4::Lookup*, QV4::ExecutionEngine*, QV4::Value const&) (l=0x332b908, engine=0xc8e970, object=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.2.i386/src/qml/jsruntime/qv4lookup.cpp:143 #17 0xb72d1874 in QV4::Moth::VME::interpret(QV4::CppStackFrame*, QV4::ExecutionEngine*, char const*) (frame=0xbfb9b4c8, engine=0xc8e970, code=0xc8e970 "\310\264\271\277") at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.2.i386/src/qml/jsruntime/qv4vme_moth.cpp:638 #18 0xb72d68e5 in QV4::Moth::VME::exec(QV4::CppStackFrame*, QV4::ExecutionEngine*) (frame=0xbfb9b4c8, engine=0xc8e970) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.2.i386/src/qml/jsruntime/qv4vme_moth.cpp:463 #19 0xb72666fa in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) (this=0x3251be0, thisObject=0xae4c1678, argv=0xae4c1690, argc=0, context=0xa03add48) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.2.i386/src/qml/jsruntime/qv4function.cpp:69 #20 0xb73fb9ed in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) (this=0x3160fe0, callData=0xae4c1660, isUndefined=0xbfb9b643) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.2.i386/include/QtQml/5.15.0/QtQml/private/../../../../../src/qml/jsruntime/qv4value_p.h:343 #21 0xb7400e4c in QQmlBinding::evaluate(bool*) (this=0x3160fe0, isUndefined=0xbfb9b643) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.2.i386/include/QtQml/5.15.0/QtQml/private/../../../../../src/qml/jsruntime/qv4jscall_p.h:95 #22 0xb7404dea in QQmlNonbindingBinding::doUpdate(QQmlJavaScriptExpression::DeleteWatcher const&, QFlags, QV4::Scope&) (this=0x3160fe0, watcher=..., flags=..., scope=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.2.i386/src/qml/qml/qqmlbinding.cpp:254 #23 0xb7402a32 in QQmlBinding::update(QFlags) (this=0x3160fe0, flags=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.2.i386/src/qml/qml/qqmlbinding.cpp:194 #24 0xb7402c0d in QQmlBinding::setEnabled(bool, QFlags) (this=0x3160fe0, e=true, flags=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.2.i386/src/qml/qml/qqmlbinding.cpp:566 #25 0xb738b4ca in QQmlData::flushPendingBindingImpl(QQmlPropertyIndex) (this=0x253a250, index=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.2.i386/src/qml/
[kmymoney] [Bug 424402] When entering a check/account statement number using the numeric keypad, insert '.' instead of ','
https://bugs.kde.org/show_bug.cgi?id=424402 --- Comment #4 from Thomas Baumgart --- Created attachment 131033 --> https://bugs.kde.org/attachment.cgi?id=131033&action=edit Numeric keypad delete behavior The numeric keypad delete button has a different meaning in different locales. No mentioning of locales here, so it is hard to give advice. For KF5 (don't know about KDE4) please take a look at the advanced keyboard settings (see attachment) and report back if any of that solves your problem or provide more details. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 424402] When entering a check/account statement number using the numeric keypad, insert '.' instead of ','
https://bugs.kde.org/show_bug.cgi?id=424402 Thomas Baumgart changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #5 from Thomas Baumgart --- Update state -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 Philipp Reichmuth changed: What|Removed |Added CC||philipp.reichm...@gmail.com --- Comment #343 from Philipp Reichmuth --- Is #357195 a duplicate of this? -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 425337] The sql query and custom DateTime format are not saved in Import dialog
https://bugs.kde.org/show_bug.cgi?id=425337 --- Comment #3 from Rok --- I forgot to state that custom DateTime format is not saved. If I choose predefined format it is saved, But if I write following format "-MM-ddThh:mm:ss.zzz" - note T in the middle then the DateTime is parsed correctly for this import, but when I reopen import dialog the combo box is cleared. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 425111] UHD Resolution on HDMI / On TV's with ~ 43" or more
https://bugs.kde.org/show_bug.cgi?id=425111 --- Comment #10 from blackcrack --- Created attachment 131034 --> https://bugs.kde.org/attachment.cgi?id=131034&action=edit WebOS TV Open Source, This could give Hardware-Info over HDMI https://github.com/topics/webos-tv https://github.com/danjohnson95/LGTV-node with Java https://github.com/Kvanrooyen/WebOS-Remote over Phython application therewith could normally kscreen read out all technical information over WebOS Webos is Open Source, by start of Kscreen could it test if Web0S connectibal and if yes, read out all technical informations and the possible resolutions. Also could it be possible over Plasma/KDE use Webos-application if a WebOS connected over HDMI if is possible ofver a connectable API for Webos in Plasma this could be great possible for plasma, include a programming remote control in Plasma for Web0S ;) -- 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 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #2 from Boudewijn Rempt --- There's also help->system information for bug reports. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422591] Add "logout" option after inactivity period
https://bugs.kde.org/show_bug.cgi?id=422591 --- Comment #4 from David Edmundson --- Git commit 72b1e92e115168512bb01f3df56b2ab1a7887c01 by David Edmundson. Committed on 20/08/2020 at 07:39. Pushed by davidedmundson into branch 'master'. Update logind's SetLockedHint SetLockedHint exists so that an external system can determine if a session is locked or not without having to access the user's session bus. We support logind's requesting us to lock/unlock so it makes sense to support this also. M +2-0ksldapp.cpp M +20 -4logind.cpp M +9-0logind.h https://invent.kde.org/plasma/kscreenlocker/commit/72b1e92e115168512bb01f3df56b2ab1a7887c01 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 423151] android app periodically looses connection with the host
https://bugs.kde.org/show_bug.cgi?id=423151 --- Comment #1 from l...@royal.net --- Seems that one of the causes of this issue is the PC reboot. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422591] Add "logout" option after inactivity period
https://bugs.kde.org/show_bug.cgi?id=422591 David Edmundson changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #5 from David Edmundson --- >Are these idle sessions screen locked? Assuming this was true: The commit above adds support for easily querying locked state for another user making it easier to externally script. This should allow > Being able to poll the activity status of those users would be good already > as I could write a cronjob that would do the rest. --- Marking as needsinfo so you can reply if anything is missing. -- 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 #10 from tcanabr...@kde.org --- "new features should only be enabled by default if they're truly useful for most users and/or if similar applications also do that" - That really depends, most tools just follows the status quo and don't really inovate, and for inovation to happen we need to show what we are doing. This specific feature has been showcased on the kde app release news, my blogpost about changes in konsole and nate's "kde weekly blogpost", so it's not really a surprise. Also, it can be quickly disabled as stated. Now, for some real implementation issues: The konsole settings is currently a mess, a lot of things that should not be settings are settings, things that should be profile are in settings, things that should be settings are in profile. We are aware of those but currently we have one developer looking for code inconsistencies and one developer trying to implement new ideas, that's not much. My next iteration of changes are going to be: Toolbar for access to toogable options (ease of discoverability, better usability) Future-proofiness of the codebase. If you would like to help I'd be grateful as we don't have too many developers on konsole. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 425577] New: Crash when using razor tool on grouped clips
https://bugs.kde.org/show_bug.cgi?id=425577 Bug ID: 425577 Summary: Crash when using razor tool on grouped clips Product: kdenlive Version: 20.08.0 Platform: Appimage OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: vr...@syllogic.in Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. group some video clips on track 2. use razor tool to cut 3. app crashes OBSERVED RESULT crash EXPECTED RESULT ungroup and cut SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424311] Severe Rendering Issues on Latest Nvidia Driver (450.57) (Arch)
https://bugs.kde.org/show_bug.cgi?id=424311 --- Comment #32 from br1ghtc...@gmail.com --- (In reply to Erik Kurzinger from comment #30) > 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. I have the same experience with Arix. I've tested downgrade to 440 without any issues. It also seem to points solely to the compositors since issues with kscreenlocker, at least in my system, seem to have been resolved. Since its the compositor, it looks like an issue with the GLX in the 450 driver. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425578] New: Variation selectors don't change column widths of preceding characters correctly
https://bugs.kde.org/show_bug.cgi?id=425578 Bug ID: 425578 Summary: Variation selectors don't change column widths of preceding characters correctly Product: konsole Version: 20.08.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: font Assignee: konsole-de...@kde.org Reporter: frederick...@tsundere.moe Target Milestone: --- Created attachment 131035 --> https://bugs.kde.org/attachment.cgi?id=131035&action=edit Up: Konsole, Below: Kitty SUMMARY Variation selectors (U+FE0E, U+FE0F) should be able to enforce column width on some preceding characters, e.g. U+270F ✏. However they have no effects in Konsole. STEPS TO REPRODUCE 1. Launch Konsole 2. echo -e '\U270F XX\nABCD' 3. echo -e '\U270F\UFE0E XX\nABCD' 4. echo -e '\U270F\UFE0F XX\nABCD' OBSERVED RESULT U+270F always occupies one column. EXPECTED RESULT The third command should cause U+270F to occupy 2 columns. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 Kernel Version: 5.8.1-zen1-1-zen OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 425579] New: Bug of Ktorrent 5.1.2 from message hôte geolite.maxmind.com: Hôte introuvable inconnu
https://bugs.kde.org/show_bug.cgi?id=425579 Bug ID: 425579 Summary: Bug of Ktorrent 5.1.2 from message hôte geolite.maxmind.com: Hôte introuvable inconnu Product: ktorrent Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: lpa...@free.fr Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. When I open Ktorrent, a pop-up message tell me : hôte geolite.maxmind.com: Hôte introuvable inconnu 2. I close Ktorrent and then it is impossible to open Ktorrent : i must reboot de Virtual Machine of OpenSuse 15.2 3. I tried to resolve the problem by installing the package from YAst : geolite2legacy : No result the bug is steel the same. OBSERVED RESULT : I can't re-open Ktorrent. I've read https://bugs.kde.org/show_bug.cgi?id=403054 but I don't understand how to use this messages for OpenSuse 15.2 EXPECTED RESULT : Have a package I could install from YAst, or from the Konsole via zypper, or a package .rpm to resolve this problem ? SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: OpenSuse 15.2 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.71.0 Qt Version: 5.12.7 ADDITIONAL INFORMATION Type de système d'exploitation 64-bit Opensuse 15.2 est installé sur une Machine Virtuelle : VirtualBox 6.1.12 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425141] Setting startup folder to "state from last time" makes .zshrc not load
https://bugs.kde.org/show_bug.cgi?id=425141 Evan changed: What|Removed |Added CC||e...@evanjt.com --- Comment #3 from Evan --- I can confirm this affects me too and just started happening after the update to 20.08.0. The workaround of setting the home folder in "Show on startup:" in Dolphin's startup preferences fixes the problem. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 402017] Cannot save PDF when loaded file has been deleted
https://bugs.kde.org/show_bug.cgi?id=402017 Phil changed: What|Removed |Added CC||pv.bugzi...@gmail.com --- Comment #52 from Phil --- 0. To ensure we have properly diagnosed the problem: 1. This error is easily reproduced, 2. Open the same file twice (simultaneously). Make changes in both copies, and save one. 3. It is not surprising that okular refuses to save over the changed file. 4. It IS surprising that the file cannot be saved at all. 5. In my test case, okular uses 40MB to view an 0.8MB file. It would be at most a 5% increase in RAM to keep the whole file in memory. Perhaps do that for small files? 6. In the meantime, perhaps a change to the error message to clarify (3&4) above: CURRENT VERSION: There are unsaved changes, and the file 'file.pdf' has been modified by another program. Your changes will be lost, because the file can no longer be saved. Do you want to continue reloading the file? PROPOSED VERSION: There are unsaved changes, and the file 'file.pdf' has been modified by another program. Your past *and future changes* will be lost, because the file can no longer be saved, *not even to a new file*. Do you want to continue reloading the file? OPTIONAL SUGGESTION: (Consider manually copying over your changes to a freshly opened copy of the file.) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425529] Document name missing from window title
https://bugs.kde.org/show_bug.cgi?id=425529 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #2 from Boudewijn Rempt --- I actually restored this behaviour in the krita/4.3 and master branch, but that shows why I changed it in the first place: now it shows the filename twice if krita is in subwindow mode. -- 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 #5 from Harald Sitter --- (In reply to Nate Graham from comment #4) > 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. Yep. I have been saying a simple "share this" wizard would be nicer for most people. But until someone makes one I'd kick out the guest option out (since it isn't enabled by default upstream anyway) and make fullaccess the default for Everyone. Full access effectively does what a full on "share this" wizard would do, it takes the share permissions out of the equation. With everyone:fullaccess the rule of thumb is: give your directory and files the permissions so the people you want to have access can have access, shares need no special set up. -- 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 #11 from RJVB --- (In reply to tcanabrava from comment #10) > This specific feature has been showcased on the kde app release news, my > blogpost about changes in konsole and nate's "kde weekly blogpost", so it's > not really a surprise. Does it come as a surprise that most users who rely on their systems to be productive on other things than the system itself don't have time to follow those things - if they are even aware that they exist?! I'd say that if you really want to look into implementing new ideas in something as basic and crucial as a terminal emulator, do it in a branch or fork that people/distributions can provide as an alternative, a konsole-ng or something similar that will pop up when using command completion (cf. iTerm and iTerm2). Now *that* would incite even me to go see what that's all about, while not obliging me to waste time figuring out what and why the heck something was changed in my user experience (my main workspace has consisted of 2 side-by-side, vertically maximised terminal windows for the past 30+ years). A toolbar with toggle buttons might sound like a good idea, but I wouldn't want to waste space on it, so make sure you use kxmlgui or something of the sort so one can assign actions to menus too. As to helping: KDE's move away first from ReviewBoard (ideal for me) and now from Phabricator to a service that doesn't match my way of working at all has made me much less inclined to make the smallish here-and-there contributions I've been making the past few years. As long as Microsoft don't drive me off github I'll be staying there and off gitlab (but even that wouldn't change much because my main gripe is with having to jump through the PR circus). NB: the flaws I pointed out have nothing to do with the settings interface. No matter how much of a mess those are, it's one I'm used to (and thank goodness the dialog still looks like one you'd expect on a desktop). -- 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 Albert Astals Cid changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #8 from Albert Astals Cid --- You could answer my original question "are you using Plasma?" also a new question "Are you using any custom style? i.e. anything that isn't Breeze" -- 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 Christoph Feck changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 420528 *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 420528] Gwenview SaveAs overwrites file without asking for confirmation
https://bugs.kde.org/show_bug.cgi?id=420528 Christoph Feck changed: What|Removed |Added CC||pos...@posteo.eu --- Comment #9 from Christoph Feck --- *** Bug 425546 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 #12 from tcanabr...@kde.org --- Hey man, There's no need to be so assertive, we are usually on eachothers backs. I don't understand a few points on your reply, so if you have time to explain them I would be grateful: > Does it come as a surprise that most users who rely on their systems to be > productive on other things than the system itself don't have time to follow > those things - if they are even aware that they exist?! Yes, it does come as a surprise for me, as those blogs are federated on the planet, and they usually appear on phoronix and other linux outlets. If they don't follow, I don't see a problem - new features are a sign that applications are evolving and a quick check on news will give you the answer if it's a bug or a feature. > I'd say that if you really want to look into implementing new ideas in > something as basic and crucial as a terminal emulator, do it in a branch or > fork that people/distributions can provide as an alternative, a konsole-ng that exists in the form of git-branches, This specific one has been in test for almost six months with discussions and input from the visual design group, users and testers. Now, you can say that you where not part of the testing, and this is true. But it's a feature that we are experimenting since phabricator so we can't blame gitlab here. The majority consensus is that this feature is a nice addition and if users don't like they can simply deactivate, no harm done. > Now *that* would incite even me to go see what that's all about, while not > obliging me to waste time figuring out what and why the heck something was > changed in my user experience (my main workspace has consisted of 2 side-by- > side, vertically maximised terminal windows for the past 30+ years). But we are not in the 80's anymore. If you want a terminal that mimics what we have in the 80's I ask you to test xterm or urxvt. with konsole you will have increased changes over time (since I'm driving those) and I don't plan to stop. you can test the new features and disable if you don't like, which is fine. Having new things disabled by default is a really good way to make sure nobody will use them. Things like Image Thumbnail, the `copy full path` and this slim line on the side for new lines on the scroll history are welcome change by the majority of people that tested konsole, for more than six months, before we launched the app. > A toolbar with toggle buttons might sound like a good idea, but I wouldn't > want to waste space on it, so make sure you use kxmlgui or something of the > > > sort so one can assign actions to menus too. XMLGui is being used. but I'd argue that 22pxs is not really a waste of space. I'm also experimenting with a new feature that you migth fancy, since you like to use two vertical terminals. What would you say about having an hability to say "This terminal on the right is the continuation of this terminal on the left", having double the scrollback lines visible? > As to helping: KDE's move away first from ReviewBoard (ideal for me) and now > from Phabricator to a service that doesn't match my way of working at all has > > made me much less inclined to make the smallish here-and-there > contributions > I've been making the past few years. That's sad, I quite enjoy your contributions. tooling is just tooling and we need to adapt to what projects that we like use. Gitlab is already helping KDE on the developers front as it's what newcomers used to github knows how to use. > As long as Microsoft don't drive me off github I'll be staying there and off > gitlab (but even that wouldn't change much because my main gripe is with > having to jump through the PR circus). I don't understand this, as you don't need a new account and gitlab quite similar to github, and does not askss you to use a different and unconventional tooling (like arcanist) > NB: the flaws I pointed out have nothing to do with the settings interface. > No > matter how much of a mess those are, it's one I'm used to (and thank goodness > the dialog still looks like one you'd expect on a desktop). And they will continue to look like a sane dekstop settings - I just want to reorganize them. -- 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 #5 from Nicolas Fella --- I don't see how the two things could be related. What graphics driver are you running? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424780] Wayland session crash upon login
https://bugs.kde.org/show_bug.cgi?id=424780 Stephan Diestelhorst changed: What|Removed |Added CC||stephan.diestelhorst@gmail. ||com --- Comment #5 from Stephan Diestelhorst --- Does this need any tagging as a packaging bug for KDE Neon User? Or a way to expedite the backport? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 424784] System hangs when Dolphin is opened
https://bugs.kde.org/show_bug.cgi?id=424784 --- Comment #11 from Ann_Rose --- Thanks for your reply On Wed, 19 Aug, 2020, 2:41 pm Julian Schraner, wrote: > https://bugs.kde.org/show_bug.cgi?id=424784 > > Julian Schraner changed: > >What|Removed |Added > > > Resolution|--- |WAITINGFORINFO > Status|REOPENED|NEEDSINFO > > --- Comment #10 from Julian Schraner --- > Right, this was only recently changed, in your version it was still called > only > file search. You haven't said if that helped or not, but I assume it > didn't. Is > that correct? > > Regarding startup: you can uninstall Akonadi, but this will also remove > KMail, > KOrganizer and a few other PIM applications. If you don't use these, that > would > be a good option. The other applications are essential and shouldn't be > removed > unless you really know what you are doing. > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425529] Document name missing from window title
https://bugs.kde.org/show_bug.cgi?id=425529 Boudewijn Rempt changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/304e72bbe ||53685e48c479a8175a6685da7ab ||10c6 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Boudewijn Rempt --- Git commit 304e72bbe53685e48c479a8175a6685da7ab10c6 by Boudewijn Rempt. Committed on 20/08/2020 at 10:11. Pushed by rempt into branch 'master'. Try once more to fix the window captions The problem is that QMDiArea messes with the mainwindow's title and that cannot be changed without hacking Qt; it will always add the current mdi document to the window title. M +18 -23 libs/ui/KisMainWindow.cpp M +0-6libs/ui/KisMainWindow.h https://invent.kde.org/graphics/krita/commit/304e72bbe53685e48c479a8175a6685da7ab10c6 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425529] Document name missing from window title
https://bugs.kde.org/show_bug.cgi?id=425529 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/304e72bbe |hics/krita/commit/191a104cd |53685e48c479a8175a6685da7ab |38566205319dd14f7a7f23dc9df |10c6|b238 --- Comment #4 from Boudewijn Rempt --- Git commit 191a104cd38566205319dd14f7a7f23dc9dfb238 by Boudewijn Rempt. Committed on 20/08/2020 at 10:13. Pushed by rempt into branch 'krita/4.3'. Try once more to fix the window captions The problem is that QMDiArea messes with the mainwindow's title and that cannot be changed without hacking Qt; it will always add the current mdi document to the window title. (cherry picked from commit 304e72bbe53685e48c479a8175a6685da7ab10c6) M +18 -19 libs/ui/KisMainWindow.cpp M +0-5libs/ui/KisMainWindow.h https://invent.kde.org/graphics/krita/commit/191a104cd38566205319dd14f7a7f23dc9dfb238 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425580] New: Plasmashell crashed on adding and modifying weather report widget
https://bugs.kde.org/show_bug.cgi?id=425580 Bug ID: 425580 Summary: Plasmashell crashed on adding and modifying weather report widget Product: plasmashell Version: 5.18.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: willyant...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.5) 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 32 (KDE Plasma) - unusual behaviors on startup before crash: 1. home and trash icon suddenly appears on desktop 2. widgets disappear -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc539b253c0 (LWP 1043))] Thread 26 (Thread 0x7fc4ee150700 (LWP 1557)): #0 0x7fc53cf62e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fc53dab7dab in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib64/libQt5Core.so.5 #2 0x7fc53f5cebc2 in QSGRenderThread::processEventsAndWaitForMore() () from /lib64/libQt5Quick.so.5 #3 0x7fc53f5d1109 in QSGRenderThread::run() () from /lib64/libQt5Quick.so.5 #4 0x7fc53dab2690 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7fc53cf5c432 in start_thread () from /lib64/libpthread.so.0 #6 0x7fc53d731913 in clone () from /lib64/libc.so.6 Thread 25 (Thread 0x7fc4a26e5700 (LWP 1556)): #0 0x7fc53d726aaf in poll () from /lib64/libc.so.6 #1 0x7fc53c30aaae in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #2 0x7fc53c30abe3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7fc53dc92b8b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7fc53dc4591b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7fc53dab1427 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7fc53f2721e9 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #7 0x7fc53dab2690 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7fc53cf5c432 in start_thread () from /lib64/libpthread.so.0 #9 0x7fc53d731913 in clone () from /lib64/libc.so.6 Thread 24 (Thread 0x7fc4a337e700 (LWP 1553)): #0 0x7fc53c35938d in g_mutex_lock () from /lib64/libglib-2.0.so.0 #1 0x7fc53c30a9b0 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #2 0x7fc53c30abe3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7fc53dc92b8b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7fc53dc4591b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7fc53dab1427 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7fc53dab2690 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7fc53cf5c432 in start_thread () from /lib64/libpthread.so.0 #8 0x7fc53d731913 in clone () from /lib64/libc.so.6 Thread 23 (Thread 0x7fc4a3fff700 (LWP 1547)): #0 0x7fc53cf62e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fc53dab7dab in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib64/libQt5Core.so.5 #2 0x7fc53f5cebc2 in QSGRenderThread::processEventsAndWaitForMore() () from /lib64/libQt5Quick.so.5 #3 0x7fc53f5d1109 in QSGRenderThread::run() () from /lib64/libQt5Quick.so.5 #4 0x7fc53dab2690 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7fc53cf5c432 in start_thread () from /lib64/libpthread.so.0 #6 0x7fc53d731913 in clone () from /lib64/libc.so.6 Thread 22 (Thread 0x7fc4bd6fa700 (LWP 1546)): #0 0x7fc53c35938d in g_mutex_lock () from /lib64/libglib-2.0.so.0 #1 0x7fc53c309fcf in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #2 0x7fc53c30a9db in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #3 0x7fc53c30abe3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7fc53dc92b8b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7fc53dc4591b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7fc53dab1427 in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x7fc53f51ffda in QQuickPixmapReader::run() () from /lib64/libQt5Quick.so.5 #8 0x7fc53dab2690 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7fc53cf5c432 in start_thread () from /lib64/libpthread.so.0 #10 0x7fc53d731913 in clone () from /lib64/libc.so.6 Thread 21 (Thread 0x7fc4bdffb700 (LWP 1534)): #0 0x7fc53cf62e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x000
[plasmashell] [Bug 425580] Plasmashell crashed on adding and modifying weather report widget
https://bugs.kde.org/show_bug.cgi?id=425580 David Edmundson changed: What|Removed |Added Assignee|k...@davidedmundson.co.uk|plasma-b...@kde.org Component|general |generic-crash -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 424680] Krusader crashs after the command F6 (move files)
https://bugs.kde.org/show_bug.cgi?id=424680 --- Comment #5 from Davide Gianforte --- You should copy the output from the "Developer Information" tab from the first screenshot; if it says it is not useful, you should use the debug packages, as said in the second screen. Follow this guide up to 1.3 : https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Also, do you have preview active on tabs (source or destination)? View - Show Preview; if yes, can you try with this option disabled? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 415293] Incorrect call-graph tracking due to new _dl_runtime_resolve_xsave* functions
https://bugs.kde.org/show_bug.cgi?id=415293 Mark Wielaard changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #8 from Mark Wielaard --- (In reply to Mark Wielaard from comment #6) > Created attachment 130439 [details] > Patch to search/check all possible dl_runtime_resolve variants So this approach seems to work as intended and I would like to push it to git. Any comments/reviews before I do that? -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 404590] ksysguard plot legends do not work well in small windows
https://bugs.kde.org/show_bug.cgi?id=404590 Dennis Schridde changed: What|Removed |Added CC||devuran...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 425581] New: Kmail crash on starup
https://bugs.kde.org/show_bug.cgi?id=425581 Bug ID: 425581 Summary: Kmail crash on starup Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: pando...@gmail.com Target Milestone: --- SUMMARY Kmail crash startup STEPS TO REPRODUCE 1. Open kmail 2. 3. OBSERVED RESULT Cannot initialize model with data QJsonObject() . missing: QJsonValue(string, "urls") org.kde.pim.akonadicore: Failed SpecialCollectionsRequestJob::slotResult "Recupero della collezione di risorse non riuscito." org.kde.pim.mailcommon: "L'esecuzione del programma di posta verrà terminata a causa di un problema.\nL'errore è stato:\nRecupero della collezione di risorse non riuscito." org.kde.pim.akonadicore: Failed SpecialCollectionsRequestJob::slotResult "Recupero della collezione di risorse non riuscito." org.kde.pim.mailcommon: "L'esecuzione del programma di posta verrà terminata a causa di un problema.\nL'errore è stato:\nRecupero della collezione di risorse non riuscito." org.kde.pim.akonadicore: Failed to request resource "akonadi_maildir_resource_0" : "Recupero della collezione di risorse non riuscito." org.kde.pim.akonadicore: Failed SpecialCollectionsRequestJob::slotResult "Recupero della collezione di risorse non riuscito." org.kde.pim.mailcommon: "L'esecuzione del programma di posta verrà terminata a causa di un problema.\nL'errore è stato:\nRecupero della collezione di risorse non riuscito." org.kde.pim.akonadicore: Failed to request resource "akonadi_maildir_resource_0" : "Recupero della collezione di risorse non riuscito." org.kde.pim.akonadicore: Failed SpecialCollectionsRequestJob::slotResult "Recupero della collezione di risorse non riuscito." org.kde.pim.mailcommon: "L'esecuzione del programma di posta verrà terminata a causa di un problema.\nL'errore è stato:\nRecupero della collezione di risorse non riuscito." org.kde.pim.akonadicore: Failed to request resource "akonadi_maildir_resource_0" : "Recupero della collezione di risorse non riuscito." org.kde.pim.akonadicore: Failed SpecialCollectionsRequestJob::slotResult "Recupero della collezione di risorse non riuscito." org.kde.pim.mailcommon: "L'esecuzione del programma di posta verrà terminata a causa di un problema.\nL'errore è stato:\nRecupero della collezione di risorse non riuscito." org.kde.pim.akonadicore: Failed to request resource "akonadi_maildir_resource_0" : "Recupero della collezione di risorse non riuscito." org.kde.pim.akonadicore: Failed SpecialCollectionsRequestJob::slotResult "Recupero della collezione di risorse non riuscito." org.kde.pim.mailcommon: "L'esecuzione del programma di posta verrà terminata a causa di un problema.\nL'errore è stato:\nRecupero della collezione di risorse non riuscito." org.kde.pim.akonadicore: Failed to request resource "akonadi_maildir_resource_0" : "Recupero della collezione di risorse non riuscito." EXPECTED RESULT I can add email account Operating System: void KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 Kernel Version: 5.8.2_1 OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 425581] Kmail crash on starup
https://bugs.kde.org/show_bug.cgi?id=425581 kdedom changed: What|Removed |Added CC||pando...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 425582] New: Use separate scales for values of different units
https://bugs.kde.org/show_bug.cgi?id=425582 Bug ID: 425582 Summary: Use separate scales for values of different units Product: ksysguard Version: 5.19.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plasmoid / Applet Assignee: ksysguard-b...@kde.org Reporter: devuran...@gmx.net CC: plasma-b...@kde.org Target Milestone: --- OBSERVED RESULT I would like to plot CPU temperature in °C and CPU clock frequency in MHz in the same graph. Since both use the same scale, the clock frequency (>1000) dominates the temperature (<100) and the resulting graph does no longer have high enough resolution to be useful. EXPECTED RESULT Using separate scales and min/max values for sources of different units (°C and MHz) would alleviate my problem. SOFTWARE/OS VERSIONS Operating System: Gentoo Linux KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 Kernel Version: 5.8.1 OS Type: 64-bit Processors: 8 × AMD Ryzen 5 2400G with Radeon Vega Graphics Memory: 13,5 GiB of RAM Graphics Processor: AMD RAVEN -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 425583] New: Ability to customise sensor names in legend
https://bugs.kde.org/show_bug.cgi?id=425583 Bug ID: 425583 Summary: Ability to customise sensor names in legend Product: ksysguard Version: 5.19.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plasmoid / Applet Assignee: ksysguard-b...@kde.org Reporter: devuran...@gmx.net CC: plasma-b...@kde.org Target Milestone: --- OBSERVED RESULT I would like to display temperature sensor data. Several sensors in my system use the name "edge" or "Tdie" or generic names like "Sensor 1". EXPECTED RESULT In the legend on the graph I would like to customise the names to e.g. "CPU" or "dGPU" or "iGPU" or "SSD". SOFTWARE/OS VERSIONS Operating System: Gentoo Linux KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 Kernel Version: 5.8.1 OS Type: 64-bit Processors: 8 × AMD Ryzen 5 2400G with Radeon Vega Graphics Memory: 13,5 GiB of RAM Graphics Processor: AMD RAVEN -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425498] The calender widget is extremely large
https://bugs.kde.org/show_bug.cgi?id=425498 --- Comment #3 from John van Spaandonk --- On 8/18/20 2:39 PM, John van Spaandonk wrote: > https://bugs.kde.org/show_bug.cgi?id=425498 > > --- Comment #2 from John van Spaandonk --- > Forgot to mention: the calendar widget increased it's size after upgrading > from > neon 18.04 to neon 20.04 today. > I played a bit with the settings of the clock, changing it to various types (analog etc). After this the problem was gone, but also my week numbers did not show anymore since that setting was reset. I am surprised that by playing with the clock's appearance, you can reset settings of the calendar. This appears to be a bug to me, just let me know if I should file a separate report for that. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 423326] Files view doesn't show the SVG icon of a .desktop file
https://bugs.kde.org/show_bug.cgi?id=423326 --- Comment #7 from Patrick Silva --- yes, it exists. I can open the icon file indicated in "Icon=" line of the .desktop file with Gwenview. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 -- 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 Julian Steinmann changed: What|Removed |Added Version|20.04.3 |20.08.0 CC||m...@xyquadrat.ch Ever confirmed|0 |1 Status|REPORTED|CONFIRMED Severity|normal |minor --- Comment #2 from Julian Steinmann --- Can confirm this behavior with Dolphin 20.11.70. Not sure why this padding is even dependant on the length of the folder name. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425431] Doesn't execute python scripts, opens them instead.
https://bugs.kde.org/show_bug.cgi?id=425431 Julian Steinmann changed: What|Removed |Added CC||m...@xyquadrat.ch Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Julian Steinmann --- Can confirm this behavior with Dolphin 20.11.70 on KDE Neon Unstable. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425455] Dolphin crashes, then i try to create a new link to a folder for the page entry
https://bugs.kde.org/show_bug.cgi?id=425455 Julian Steinmann changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||m...@xyquadrat.ch --- Comment #1 from Julian Steinmann --- Hi, what do you mean by "page entry"? When I create a new "Link to Location", I cannot get Dolphin to crash (using Dolphin 20.11.70). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425584] New: Can't stack saving|exporting operations
https://bugs.kde.org/show_bug.cgi?id=425584 Bug ID: 425584 Summary: Can't stack saving|exporting operations Product: krita Version: 4.3.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- Export a file while it is being saved and didn't finish yet, the export is ignored. STEPS TO REPRODUCE 1. Save a big file that takes at least a few seconds so you can finish the export form while the file is STILL saving. 2. Fill the export popup form and use another format so you can make sure which save command has been done and which has been ignored. OBSERVED RESULT Only the save operation has happened. If you invert things (you export, then you save while still exporting, then only the export will happen) EXPECTED RESULT Both save and export and whatever third, forth operation have been executed SOFTWARE/OS VERSIONS macOS: 10.15.5 (19F101) ADDITIONAL INFORMATION: This is an old problem, I've been noticing it since maybe 2 years ? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425259] Dolphin crashed when emptying trash
https://bugs.kde.org/show_bug.cgi?id=425259 Julian Steinmann changed: What|Removed |Added Resolution|--- |UNMAINTAINED CC||m...@xyquadrat.ch Status|REPORTED|RESOLVED --- Comment #1 from Julian Steinmann --- You are using a very old version of Dolphin (3 years old in a few months). It is very likely that your bug has been fixed since then. Additionally, the backtrace indicates that this crash isn't actually happening in Dolphin, but in the system notification. Consider updating your system to Ubuntu 20.04. If the issue persists, please reopen this report and attach a new, complete backtrace. Thanks :) -- You are receiving this mail because: You are watching all bug changes.
[kdenetwork-filesharing] [Bug 422554] permission order in usershare_acl
https://bugs.kde.org/show_bug.cgi?id=422554 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #6 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/network/kdenetwork-filesharing/-/merge_requests/5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425585] New: Take layer state into account in the undo history
https://bugs.kde.org/show_bug.cgi?id=425585 Bug ID: 425585 Summary: Take layer state into account in the undo history Product: krita Version: 4.3.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: wishlist Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: mangate...@gmail.com Target Milestone: --- Making a layer visible or not is not taken into account in the undo history. You can not open a file, disable a rough layer, or enable a missing layer and save. You need to make a "dummy" operation for a * to appear next to the file name. Also sometimes when undoing, if layers are not set back in place as they were, you can have a hard time with your history. What about giving the ability to take layer visibility into account in undos.? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425390] Dolphin crashes upon moving to second monitor
https://bugs.kde.org/show_bug.cgi?id=425390 Julian Steinmann changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED CC||m...@xyquadrat.ch --- Comment #1 from Julian Steinmann --- This appears to be a crash in QtWayland, not Dolphin itself. Please report the bug there if the issue persists. Thanks :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425585] Take layer state into account in the undo history
https://bugs.kde.org/show_bug.cgi?id=425585 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com --- Comment #1 from Dmitry Kazakov --- Perhaps we should recover undo for layer properties, but make it compressible? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425343] [Wayland] Keyboard Layout applet doesn't follow actual layout switching
https://bugs.kde.org/show_bug.cgi?id=425343 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/plasma/kwin/-/merge_requests/203 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425542] Dolphin "Free space information" bug
https://bugs.kde.org/show_bug.cgi?id=425542 Julian Steinmann changed: What|Removed |Added CC||m...@xyquadrat.ch Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Severity|normal |minor --- Comment #1 from Julian Steinmann --- Can confirm this with Dolphin 20.11.70 on KDE Neon Unstable. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425585] Take layer state into account in the undo history
https://bugs.kde.org/show_bug.cgi?id=425585 --- Comment #2 from Dmitry Kazakov --- Hi, Manga! Could you start a discussion for it on krita-artists? I remember that not having undo for layer properties was an explicit painter's wish. Perhaps they changed their opinion on that? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425586] New: [Wayland] KDE does not detect a second monitor
https://bugs.kde.org/show_bug.cgi?id=425586 Bug ID: 425586 Summary: [Wayland] KDE does not detect a second monitor Product: kwin Version: 5.19.4 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: thunderstormpol...@o2.pl Target Milestone: --- Created attachment 131037 --> https://bugs.kde.org/attachment.cgi?id=131037&action=edit Screenshot Unfortunately, I don't know what logs are needed. KDE (Wayland) does not detect the second screen that is connected. Maybe it's because the screen is connected to the second graphics card (dedicated). Not only KDE has a problem with this, but also Enlightenment. Sway (wdisplays) and Gnome support. On Xorg works (But I have Xorg issues, so I prefer using Wayland) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425585] Take layer state into account in the undo history
https://bugs.kde.org/show_bug.cgi?id=425585 --- Comment #3 from Manga Tengu --- 1 I thought of something but I found it overkill: having an undo that ignores layer state and having one which doesn't 2 Yes let's do that ! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425586] [Wayland] KDE does not detect a second monitor
https://bugs.kde.org/show_bug.cgi?id=425586 Fervi changed: What|Removed |Added Platform|Other |Archlinux Packages OS|Other |Linux -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425586] [Wayland] KDE does not detect a second monitor
https://bugs.kde.org/show_bug.cgi?id=425586 Fervi changed: What|Removed |Added Platform|Archlinux Packages |Manjaro -- 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 #13 from RJVB --- (In reply to tcanabrava from comment #12) > on eachothers backs. Are you sure that's what you wanted to say? > Yes, it does come as a surprise for me, as those blogs are federated on the > planet, and they usually appear on phoronix and other linux outlets. I did say people who's productivity is not aimed at but simply based on Linux? As a cheek-in-tongue example of something you're bound to use: how actively do you follow the federated blogs and what-have-you that are surely written by toilet designers or cleaning product developers? > applications are evolving and a quick check on news will give you the answer > if it's a bug or a feature. You still have to know what to search for, and if the behaviour ressembles what's being described in QTBUG-78963 that you had already been following the idea it might be a feature doesn't spring to mind immediately. I had noticed the "highlight new lines" setting, but this implementation only highlights new canvas that has never been painted before. > The majority consensus is > that this feature is a nice addition and if users don't like they can simply > deactivate, no harm done. The big question here is how big and representative the tester population is. As long as branches are feature-specific and/or aren't well advertised so pre-built preview binaries become available to a large audience the testing population will remain small, and probably not very representative. > But we are not in the 80's anymore. If you want a terminal that mimics what > we have in the 80's I ask you to test xterm or urxvt. There are a handful of things that are missing from those, but I'm not obliged to keep updating konsole nor forbidden from hacking out things I really can't stand - and I will be taking a look at QTerminal or whatever other Qt-based terminals there are. > XMLGui is being used. but I'd argue that 22pxs is not really a waste of > space. That must be (almost) 2 lines of text for me, and for something that gets to be used only occasionally that's a waste in my book, even on my larger screens. > you like to use two vertical terminals. What would you say about having an > hability to say "This terminal on the right is the continuation of this > terminal on the left", having double the scrollback lines visible? I'd say that might interest me as a feature in Kate or a GUI equivalent of `less`, but not in a terminal. I'm also pretty certain that curses-based implementations of this must exist but I've never had need for those. The practice of using multiple on-screen windows that can be positioned freely so each shows something relevant and allows to do things based on what is being shown here and there seems to become an increasingly lost art. That's visible also in websites that assume everyone maximises their browser window. It took me a long time to adjust to MDI IDE designs and I only did that because there are no IDEs anymore that can be used as a loose collection of related windows. > That's sad, I quite enjoy your contributions. tooling is just tooling and we > need to adapt to what projects that we like use. No, we don't. Call it voting with your wallet if you want. > I don't understand this, as you don't need a new account and gitlab quite > similar to github, and does not askss you to use a different and > unconventional tooling (like arcanist) Arcanist was a bit weird but it still allowed me to put up diffs for review without having to commit them in a local branch of a forked repo. I don't care if that's not the fashionable industry way of doing things, it's what's most convenient for me and doesn't oblige me to waste disk space or time. I too contribute because I feel like it and not because I'm paid and/or ordered to do so. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425585] Take layer state into account in the undo history
https://bugs.kde.org/show_bug.cgi?id=425585 --- Comment #4 from Manga Tengu --- here is the topic: https://krita-artists.org/t/take-layer-state-into-account-in-the-undo-history/11040 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407383] Krita hangs calculating the result of a layer stack with 10 clone layers and 10 transform masks
https://bugs.kde.org/show_bug.cgi?id=407383 --- Comment #2 from Dmitry Kazakov --- Hi, Boud! I cannot reproduce the problem anymore. Perhaps the document was just too large and the recalculation took too long? I've attached a document that I created for testing the problem. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407383] Krita hangs calculating the result of a layer stack with 10 clone layers and 10 transform masks
https://bugs.kde.org/show_bug.cgi?id=407383 --- Comment #3 from Dmitry Kazakov --- Created attachment 131038 --> https://bugs.kde.org/attachment.cgi?id=131038&action=edit Testing document -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407383] Krita hangs calculating the result of a layer stack with 10 clone layers and 10 transform masks
https://bugs.kde.org/show_bug.cgi?id=407383 Dmitry Kazakov changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|ASSIGNED|NEEDSINFO --- Comment #4 from Dmitry Kazakov --- Since I cannot reproduce the bug anymore, I'll mark the bug as needsinfo -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 420409] Mnemonics in chinese (and possibly others) shouldn't take symbols
https://bugs.kde.org/show_bug.cgi?id=420409 Marco Martin changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/fram ||eworks/kirigami/commit/6dda ||5f1d3782b2c8aeb385fdade6e94 ||87c29f571 Status|ASSIGNED|RESOLVED --- Comment #6 from Marco Martin --- Git commit 6dda5f1d3782b2c8aeb385fdade6e9487c29f571 by Marco Martin. Committed on 20/08/2020 at 12:26. Pushed by mart into branch 'master'. new logic to remove acceleration marks Logic to remove acceleration marks borrowed from KWidgetAddons https://phabricator.kde.org/D7964 This should handle as wel CJK text. M +89 -3src/mnemonicattached.cpp https://invent.kde.org/frameworks/kirigami/commit/6dda5f1d3782b2c8aeb385fdade6e9487c29f571 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425455] Dolphin crashes, then i try to create a new link to a folder for the page entry
https://bugs.kde.org/show_bug.cgi?id=425455 --- Comment #2 from Sammy --- (In reply to Julian Steinmann from comment #1) > Hi, what do you mean by "page entry"? When I create a new "Link to > Location", I cannot get Dolphin to crash (using Dolphin 20.11.70). Hi, on the left side there are different links to folders like main directory, downloads etc. if i try to add another entry now it crashes. interestingly enough, it worked when i reinstalled the program. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 352837] Single Layer EXR with RGB and Alpha channels behaves erroneously
https://bugs.kde.org/show_bug.cgi?id=352837 Dmitry Kazakov changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 352837] Single Layer EXR with RGB and Alpha channels behaves erroneously
https://bugs.kde.org/show_bug.cgi?id=352837 Dmitry Kazakov changed: What|Removed |Added Status|CONFIRMED |ASSIGNED CC||dimul...@gmail.com --- Comment #8 from Dmitry Kazakov --- I can reproduce this bug on CandleGlass.exr. I'll check what we can do with it -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 353204] 32 bit float composite ops overflow: Layer Blending Mode Over Gradients result in strange patterns
https://bugs.kde.org/show_bug.cgi?id=353204 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425455] Dolphin crashes, then i try to create a new link to a folder for the page entry
https://bugs.kde.org/show_bug.cgi?id=425455 Julian Steinmann changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #3 from Julian Steinmann --- Hi, thank you for your quick response. I now understand what you mean - but I have still not been able to reproduce your crash. Given that it works fine for you now if I understood that correctly, I'll close this report. Feel free to reopen it if the crash occurs again. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 425587] New: K3b crashed unexpectedly
https://bugs.kde.org/show_bug.cgi?id=425587 Bug ID: 425587 Summary: K3b crashed unexpectedly Product: k3b Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Burning/Hardware Assignee: k...@kde.org Reporter: reinhardau...@gmx.at CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- Created attachment 131039 --> https://bugs.kde.org/attachment.cgi?id=131039&action=edit Backtrace of k3b SUMMARY STEPS TO REPRODUCE 1. Try to burn a DVD 2. K3b crashes 3. OBSERVED RESULT K3b crashed EXPECTED RESULT Burnt DVD SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.3.18-lp152.33-default / 5.18.5 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.71.0 Qt Version: 5.12.7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 425587] K3b crashed unexpectedly
https://bugs.kde.org/show_bug.cgi?id=425587 Reinhard Auner changed: What|Removed |Added CC||reinhardau...@gmx.at -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425588] When opening EXR the background in not set to black automatically anymore
https://bugs.kde.org/show_bug.cgi?id=425588 Dmitry Kazakov changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425588] New: When opening EXR the background in not set to black automatically anymore
https://bugs.kde.org/show_bug.cgi?id=425588 Bug ID: 425588 Summary: When opening EXR the background in not set to black automatically anymore Product: krita Version: nightly build (please specify the git hash!) Platform: Microsoft Windows OS: Other Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: dimul...@gmail.com Target Milestone: --- When loading EXR image we used to set the background to "Black" to display CandleGrass.exr-like images correctly. For some reason it doesn't work anymore. Krita loads EXRs with fully transparent background The bug is reproducible in krita/4.3 branch af77ed57599cab0e65a3b5470af666513f7f7bf0 -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 425589] New: No CAS Worksheet in menubar on KDE Neon
https://bugs.kde.org/show_bug.cgi?id=425589
Bug ID: 425589
Summary: No CAS Worksheet in menubar on KDE Neon
Product: LabPlot2
Version: 2.7.0
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: frontend
Assignee: alexander.se...@web.de
Reporter: samcas...@gmail.com
Target Milestone: ---
SUMMARY
With multiple Labplot2 CAS worksheet backends installed (Maxima, Lau, Python2),
there is no CAS worksheet button in the menu. Compared with a version on
windows 7 & the snap package (Labplot 2.6 c.f. Labplot 2.7 on Neon), which did
not have CAS backends installed, but did show the CAS worksheet button, albeit
grayed out.
STEPS TO REPRODUCE
1. pkcon install labplot2 {i.e. install from KDE Neon packages}
OBSERVED RESULT
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Neon 5.19
(available in About System)
KDE Plasma Version: 5.19.4
KDE Frameworks Version: 5.73.0
Qt Version: 5.14.2
ADDITIONAL INFORMATION
I am aware there is a similar issue here, but that one seems to be largely
about flatpack?
Happy to wait til 2.8 :)
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 425590] New: no OSD indication when switching keyboard layout with Application Policy
https://bugs.kde.org/show_bug.cgi?id=425590 Bug ID: 425590 Summary: no OSD indication when switching keyboard layout with Application Policy Product: kwin Version: git master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: butir...@gmail.com Target Milestone: --- SUMMARY Happens in some cases as described below. STEPS TO REPRODUCE 1. Set Application Policy for keyboard layout switching in Keyboard Settings. Make sure there are at least 2 layouts. 2. Switch layout in one app, not OSD notification pop up on the switching. 3. Focus another app. 4. Switch layout there (using hotkey or clicking Keyboard Layout applet in the systray). OBSERVED RESULT No OSD notification on the layout change. EXPECTED RESULT OSD should always popup on actual layout switching SOFTWARE/OS VERSIONS Operating System: Ubuntu 20.04 KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 414512] Firefox KDE Plasma Integration sets window.Audio.prototype to undefined
https://bugs.kde.org/show_bug.cgi?id=414512 si...@brulhart.me changed: What|Removed |Added CC||si...@brulhart.me -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424538] The Window rules dialog does not show
https://bugs.kde.org/show_bug.cgi?id=424538 Ismael Asensio changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #6 from Ismael Asensio --- (In reply to Ezike Ebuka from comment #5) > (In reply to Ismael Asensio from comment #4) > > You are right, sorry I missed the video. > > It is very clear and this is indeed a different bug from the one I > > mentioned. > > > > Could you please launch `kcmshell5 kwinrules` from a terminal and paste here > > the output? Specially after trying to edit a rule you have or adding a new > > one. > > > > Thanks! > > sorry i kinda reinstalled manjaro kde and it started working Nice! I guess this was due to some Qt goodies it uses from later releases not being completely updated. I'm closing the bug. Feel free to re-open if you experience it again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425343] [Wayland] Keyboard Layout applet doesn't follow actual layout switching
https://bugs.kde.org/show_bug.cgi?id=425343 Andrey changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=425590 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425590] no OSD indication when switching keyboard layout with Application Policy
https://bugs.kde.org/show_bug.cgi?id=425590 Andrey changed: What|Removed |Added CC||bugsefor...@gmx.com See Also||https://bugs.kde.org/show_b ||ug.cgi?id=425343 --- Comment #1 from Andrey --- Would be gratitude for the confirmation (hope the description is clear). -- You are receiving this mail because: You are watching all bug changes.
[kdenetwork-filesharing] [Bug 425591] New: share tab bricked in master
https://bugs.kde.org/show_bug.cgi?id=425591 Bug ID: 425591 Summary: share tab bricked in master Product: kdenetwork-filesharing Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: n...@kde.org Reporter: sit...@kde.org Target Milestone: --- trying to edit shares more than once falls over with current master because the qml types are registered as singleton types. that falls over impressively when opening multiple properties tabs as any after the first will fall over the now nullptr'd singletons. needs reshuffling to contextProperty() on the engine. super invasive though, so pending mrs need landing first -- You are receiving this mail because: You are watching all bug changes.
[kdenetwork-filesharing] [Bug 425591] share tab bricked in master
https://bugs.kde.org/show_bug.cgi?id=425591 Harald Sitter changed: What|Removed |Added Assignee|n...@kde.org|sit...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kdenetwork-filesharing] [Bug 425591] share tab bricked in master
https://bugs.kde.org/show_bug.cgi?id=425591 Harald Sitter changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 352837] Single Layer EXR with RGB and Alpha channels behaves erroneously
https://bugs.kde.org/show_bug.cgi?id=352837 --- Comment #9 from Dmitry Kazakov --- Okay, the problem happens because all the selections in Krita are 8-bit. Therefore one cannot split alpha from a 16-bit EXR image without precision loss. I don't think it is fixable without implementing high-bitdepth selections. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425590] no OSD indication when switching keyboard layout with Application Policy
https://bugs.kde.org/show_bug.cgi?id=425590 Andrey changed: What|Removed |Added Assignee|kwin-bugs-n...@kde.org |butir...@gmail.com -- 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 #6 from Harald Sitter --- o turns out ksambashare already has all the code, the qwidget ui just didn't use it properly :O -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425590] no OSD indication when switching keyboard layout with Application Policy
https://bugs.kde.org/show_bug.cgi?id=425590 Andrey changed: What|Removed |Added Flags||Wayland+ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 352837] Split-alpha on 16-bit EXR images destroys alpha channel (needs high bitdepth selections)
https://bugs.kde.org/show_bug.cgi?id=352837 Dmitry Kazakov changed: What|Removed |Added Summary|Single Layer EXR with RGB |Split-alpha on 16-bit EXR |and Alpha channels behaves |images destroys alpha |erroneously |channel (needs high ||bitdepth selections) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 352837] Split-alpha on 16-bit EXR images destroys alpha channel (needs high bitdepth selections)
https://bugs.kde.org/show_bug.cgi?id=352837 Dmitry Kazakov changed: What|Removed |Added Assignee|dimul...@gmail.com |krita-bugs-n...@kde.org Status|ASSIGNED|CONFIRMED Severity|normal |wishlist --- Comment #10 from Dmitry Kazakov --- I will downgrade this bug to a wishlist, because it needs high bitdepth selections, which is not in our roadmap currently. Perhaps we should provide some other algorithm for working with alpha channel in high bitdepth images. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 398465] Tray of optical device closes itself when a disc is ejected
https://bugs.kde.org/show_bug.cgi?id=398465 --- Comment #18 from prote...@hotmail.it --- (In reply to Patrick Silva from comment #17) > I have reverted the workaround mentioned in comment 6 to test again with > newer KDE software. > > My settings in "Removable devices" kcm when auto-mounting is enabled: > "Enable automatic mounting of removable media", "Automatically mount all > removable media at login" > and "Automatically mount all removable media when attached" options are > checked. > "Only automatically mount removable media that have been manually mounted > before" is unchcked. > > If auto-mounting is enabled, this behavior is reproducible when: > the optical disc is ejected via device notifier; > the optical disc is ejected via the "Eject" option of the context menu > that opens when we right-click on the optical device under "Removable > devices" section of places panel of Dolphin; > I run "eject" commnand in Konsole. > > However, if auto-mounting is enabled this behavior is NOT reproducible when > I eject the disc by pressing the physical "eject" button of the optical > device. > > If auto-mounting is disabled, this behavior is reproducible when: > I press the physical "eject" button of the optical device; > the optical disc is ejected via the "Eject" option of the context menu > that opens when we right-click on the optical device under "Removable > devices" section of places panel of Dolphin; > I run "eject" commnand in Konsole. > > It's impossible to eject a disc via device notifier when auto-mounting is > disabled. > We only can mount the disc. > > Operating System: Arch Linux > KDE Plasma Version: 5.18.90 > KDE Frameworks Version: 5.70.0 > Qt Version: 5.15.0 rc2 > Kernel Version: 5.6.13-arch1-1 Is there or not a solution to this wrong behavior? The solution is SIMPLE. The developers have to separate the unmount function from the EJECT FUNCTION otherwise the system doesn't distinguish between the two operations. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425592] New: In solus Linux with default dark theme, the file and folder backgrounds remains white with grey and barely visible text while the UI is using the apropriate dark theme colo
https://bugs.kde.org/show_bug.cgi?id=425592 Bug ID: 425592 Summary: In solus Linux with default dark theme, the file and folder backgrounds remains white with grey and barely visible text while the UI is using the apropriate dark theme colour. Product: dolphin Version: 20.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: thesli...@free.fr CC: kfm-de...@kde.org Target Milestone: --- SUMMARY In solus Linux with default dark theme, the file and folder backgrounds remains white with grey and barely visible text while the UI is using the appropriate dark theme colours. STEPS TO REPRODUCE 1. Run Dolphin in the default Solus environment. 2. 3. OBSERVED RESULT Appropriate dark theme usage in the UI but not in the file and folder view pane which has only appropriate text colour but with white background. EXPECTED RESULT A darker shade of dark grey used as the background colour for the files and folders view pane similar to the File program provided by default with Solus. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 374538] Logout/shutdown/reboot from KDE session hangs system
https://bugs.kde.org/show_bug.cgi?id=374538 Patrick Dubois changed: What|Removed |Added Platform|Kubuntu Packages|Ubuntu Packages CC||p...@pdubois.com --- Comment #3 from Patrick Dubois --- I have seen this problem in the Fedora packages as well. The effects on user experience are quite severe rendering KDE not usable in a lab environment as an example. What can be done to get someone @ KDE to look at this ? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425141] Setting startup folder to "state from last time" makes .zshrc not load
https://bugs.kde.org/show_bug.cgi?id=425141 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Keywords||regression Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 424189] Krusader file copy failing for larger files in Ubuntu 20.04
https://bugs.kde.org/show_bug.cgi?id=424189 Harald Sitter changed: What|Removed |Added Assignee|plasma-b...@kde.org |kio-bugs-n...@kde.org Product|kio-extras |frameworks-kio Version|19.12 |unspecified Component|Samba |general CC||kdelibs-b...@kde.org, ||sit...@kde.org --- Comment #4 from Harald Sitter --- Moving bug to KIO. kio-extras don't play into this since the share is accessed through gvfs (i.e. that's file->file from a KIO point of view). -- 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 #24 from Méven Car --- (In reply to Marvin Hagemeister from comment #22) > 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. So I have opposite opinions, a setting/option seems to be necessary. It will be wayland only, not-native by default (current screen is always native now so it will be a fast path). (In reply to Christoph Feck from comment #23) > It would help if snapshots were saved with DPI information. A viewer could > then decide if the images need to be scaled. That's not really possible for multiple screens with multiple scale factors... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407383] Krita hangs calculating the result of a layer stack with 10 clone layers and 10 transform masks
https://bugs.kde.org/show_bug.cgi?id=407383 Boudewijn Rempt changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #5 from Boudewijn Rempt --- We've done a bunch of work in this area, so let's just close. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399688] layer's blending mode is not saved when alpha inheritance is on with ora files
https://bugs.kde.org/show_bug.cgi?id=399688 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 423818] KDirWatch's useFam loops indefinitely (actual fam, not gamin)
https://bugs.kde.org/show_bug.cgi?id=423818 Harald Sitter changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/kcoreaddons/commit/8 ||599c4d58b82ad0096d59a4a23e5 ||4d75b5c7f558 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Version Fixed In||5.74 --- Comment #14 from Harald Sitter --- Git commit 8599c4d58b82ad0096d59a4a23e54d75b5c7f558 by Harald Sitter. Committed on 20/08/2020 at 13:59. Pushed by sitter into branch 'master'. do not wait for fam events indefinitely when famEventReceived encountered trouble with getting events it'll disable FAM entirely and instead register another fallback system. this means we'll have to check if FAM has been disabled every iteration and if it has break out of the loop. otherwise we'd loop indefinitely. we'll now also cap the amount of time (or rather iterations) we'll wait for the event to arrive. this acts as a safety net against further infinity loops. what's more, since this will get called from the main thread the GUI is blocked by us, so, 4s is already a lot all things considered. FIXED-IN: 5.74 M +33 -19 src/lib/io/kdirwatch.cpp M +1-0src/lib/io/kdirwatch_p.h https://invent.kde.org/frameworks/kcoreaddons/commit/8599c4d58b82ad0096d59a4a23e54d75b5c7f558 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425588] When opening EXR the background in not set to black automatically anymore
https://bugs.kde.org/show_bug.cgi?id=425588 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- I actually think you're going to need to do some archaeology here, because I remember seeing this change after a commit of yours that had, I think, to do with premultiplied alpha. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418089] Blend mode "Addition" replaced by "Normal" after save/load to Krita (`kra`) file.
https://bugs.kde.org/show_bug.cgi?id=418089 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422919] brushes Blending modes's shortcutes are not work.
https://bugs.kde.org/show_bug.cgi?id=422919 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422919] brushes Blending modes's shortcutes are not work.
https://bugs.kde.org/show_bug.cgi?id=422919 Dmitry Kazakov changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425593] New: presentation window resized and moved to top left corner by touch gesture
https://bugs.kde.org/show_bug.cgi?id=425593 Bug ID: 425593 Summary: presentation window resized and moved to top left corner by touch gesture Product: okular Version: 1.11.0 Platform: Flatpak OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: keschur...@gmail.com Target Milestone: --- Created attachment 131040 --> https://bugs.kde.org/attachment.cgi?id=131040&action=edit screen shot of presentation window in corner of screen SUMMARY In presentation mode on a 2-in-1 laptop, a downward stroke on the touchscreen from the top edge of the screen causes the presentation window to be resized and moved to the top left corner of the screen. STEPS TO REPRODUCE 1. View PDF in presentation mode 2. Using any number of fingers, swipe down from the top edge of the screen OBSERVED RESULT The presentation window is resized and moved to the top left corner of the screen. EXPECTED RESULT Nothing. (Would be nice if this gesture revealed the annotations toolbar, though.) SOFTWARE/OS VERSIONS Pop!_OS 20.04 Gnome 3.36 ADDITIONAL INFORMATION I see the same result when I use a one-, two-, or three-finger touch gesture from the top of the screen. A four-finger downward stroke causes the same change to the presentation window and simultaneously switches the workspace. The workspace switching is the expected behavior in Gnome. The other gestures are not assigned. I cannot recreate the behavior with a click-and-drag. I thought maybe the touch gesture is grabbing the edge of an invisible title bar that I cannot reach with the touchpad. I see the same result when I turn on/off the "double click window titlebar toggles maximize" setting in Gnome Tweaks. -- You are receiving this mail because: You are watching all bug changes.
