[krita] [Bug 405717] Numpad numbers won't work even when numlock is on
https://bugs.kde.org/show_bug.cgi?id=405717 --- Comment #2 from Razvan Radulescu --- (In reply to Boudewijn Rempt from comment #1) > You can find the git hash in the about box, it's part of the version number. > As for the issue: are you typing in things like the opacity slider or the > size slider in toolbar, or in entry boxes in dockers or dialogs? It's the same everywhere - dockers/dialogs/toolbar sliders etc. but not just sliders, any input box really, like for example layer names, specific color entry boxes. Krita just ignores keypad number keys/numlock altogether. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 405731] Not able to remove or move widgets in panel
https://bugs.kde.org/show_bug.cgi?id=405731 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #1 from Michail Vourlakos --- Above maximum length, there is a new option called, Rearrange and configure your widgets -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 405552] Unable to print from KDE/QT5 Apps anymore
https://bugs.kde.org/show_bug.cgi?id=405552 --- Comment #4 from boospy --- > ...so would you be willing to test again once you get Qt 5.12.1? Yes i do, probably should not take long until this version also appears in neon. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 405612] ctrl+L or ctrl+shift+k does not clear /usr/bin/screen correctly
https://bugs.kde.org/show_bug.cgi?id=405612 Mariusz Glebocki changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||m...@arccos-1.net See Also||https://bugs.kde.org/show_b ||ug.cgi?id=384218 Ever confirmed|0 |1 --- Comment #3 from Mariusz Glebocki --- Ctrl+L/`clear`: described/reported in a bug from Egmont's post, so I'll remove it from the title, as the second part is more unique. I'll try to look at it this weekend, as it annoys me too. Ctrl+Shift+K: `screen` is kind of terminal emulator inside terminal emulator (Konsole in this case). Ctrl+Shift+K clears internal Konsole buffers and display buffer #1. `screen`, like e.g vim or nano, works on dedicated display buffer #2, where clearing buffers would be pointless, as "full-screen" applications assume the characters they put on display will be there until they change them. Even if it would be cleared, `screen` redraws everything exactly as it was in nearest opportunity (like screen change). The way to make it work is to detect the `screen` is running (easy, already done to display program name in tab title) and send clearing escape sequences to it. There could be configurable list of programs which can receive clearing sequences on display buffer #2 (with e.g. screen, tmux by default) somewhere is settings. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 384218] clear/^l shouldn't add empty lines to the scrollback buffer
https://bugs.kde.org/show_bug.cgi?id=384218 Mariusz Glebocki changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=405612 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 384218] clear/^l shouldn't add empty lines to the scrollback buffer
https://bugs.kde.org/show_bug.cgi?id=384218 Mariusz Glebocki changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 405731] Not able to remove or move widgets in panel
https://bugs.kde.org/show_bug.cgi?id=405731 --- Comment #2 from himanshu.sp...@gmail.com --- Ah got it. It's working. In my opinion this new option doesn't look like a button (by looking at this I had no idea what to do with it). May be a button or toggle would be better approach -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 405612] ctrl+L or ctrl+shift+k does not clear /usr/bin/screen correctly
https://bugs.kde.org/show_bug.cgi?id=405612 --- Comment #4 from Egmont Koblinger --- > detect the `screen` is running Sounds hackish to me, IMO the terminal's behavior shouldn't depend on the app running inside. > and send clearing escape sequences to it How would you do it (keeping in mind that its keybindings are configurable)? Maybe allow to configure in konsole the keycombo to send for each particular app? If you really wish to go this direction, maybe you could make it independent from clearing the screen, and instead allow to specify arbitrary remapping based on the running application (and perhaps other circumstances too)? E.g. if vim is running then Shift+Ctrl+W, instead of closing the tab, could emit `:qEnter`, or sure you can come up with other ideas along these lines. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 405744] New: endless browser launch
https://bugs.kde.org/show_bug.cgi?id=405744 Bug ID: 405744 Summary: endless browser launch Product: Falkon Version: 3.1.0 Platform: Other OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: evgeniy28121...@mail.ru Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 405745] New: endless browser launch
https://bugs.kde.org/show_bug.cgi?id=405745 Bug ID: 405745 Summary: endless browser launch Product: Falkon Version: unspecified Platform: Other OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: evgeniy28121...@mail.ru Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405746] New: Rename and reorganize some Create New Document's Custom Document names and options
https://bugs.kde.org/show_bug.cgi?id=405746 Bug ID: 405746 Summary: Rename and reorganize some Create New Document's Custom Document names and options Product: krita Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: tysont...@gmail.com Target Milestone: --- Right now Custom Document in Create New Document dialogue has quite a few confusing item arrangements. 1) Color space related stuff is under the Dimension tab. Suggestion: Make a new Color Space tab and put color space stuff there. 2) The "Color" string should be renamed to "Color Management" or "Color Space". 3) This "Color" string is being used in way too many different context: #. i18n: ectx: property (title), widget (QGroupBox, grpMode) #. i18n: ectx: property (text), widget (KColorButton, colorSelector) #. i18n: ectx: property (text), widget (KColorButton, colorFillSelector) #. i18n: ectx: property (text), item, widget (QComboBox, cmbFillType) #. i18n: ectx: property (title), widget (QGroupBox, groupBox_2) #: libs/pigment/compositeops/KoCompositeOps.h:190 #: libs/pigment/KoCompositeOp.cpp:31 libs/pigment/KoCompositeOpRegistry.cpp:105 #: libs/ui/dialogs/kis_dlg_preferences.cc:1177 #: libs/ui/forms/wdgnewimage.ui:66 libs/ui/forms/wdgstrokeselectionproperties.ui:150 #: libs/ui/forms/wdgstrokeselectionproperties.ui:188 #: libs/ui/kis_palette_view.cpp:102 libs/ui/kis_palette_view.cpp:328 #: libs/ui/layerstyles/WdgColorOverlay.ui:23 #: libs/ui/layerstyles/WdgStroke.ui:134 plugins/color/lcms2engine/compositeops/RgbCompositeOpColor.h:38 #: plugins/extensions/layersplit/layersplit.cpp:202 #: plugins/generators/solid/colorgenerator.h:53 #, kde-format But Color (pigments) is not really the same as Color (color management context). In Chinese we have two different words for each: 颜色/色彩. But now we are forced to use Color (pigment) in contexts of Color (Color management), which is not completely wrong but irritating for a translator to do nothing but allow a mistake. I suggest we make every Color string unique and do not reuse them in any another context, this will greatly increase the accuracy of translation. 3) Image Background Color and Opacity is for some reason defined in "Content" tab. Now these are the two options that SHOULD go under the name of "Color"...but under the current arrangement it really has no place to go. I suggest we: 1. Rename "Dimensions" tab to "Content" 2. Move all Layer count and Image Background settings under the current "Color" section 3. Move all color space related stuff to a new "Color Space" tab 4. Rename the current "Content" tab to "Metadata", it has only Name and Description now. 5. Same goes for Create from Clipboard. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405743] Customise Tool tab in editor
https://bugs.kde.org/show_bug.cgi?id=405743 caulier.gil...@gmail.com changed: What|Removed |Added Version|unspecified |6.0.0 CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- The Editor tool bar can be already full customized. There is no dedicated toolbar for editor tools only, but the main tool bar can be used in this way. Go to Settings/Configure toolbars dialog. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 405585] Somewhere between Kate 17.12.3 and 18.12.2 code folding changed
https://bugs.kde.org/show_bug.cgi?id=405585 --- Comment #4 from Nibaldo G. --- The problem occurs when using beginRegion+endRegion in the same rule. Ex: In this case, the string "hello" is part of the "region1" and "region2" regions simultaneously, which generates folding problems. The behavior you expect (and the ideal behavior) is that "hello" isn't part of "region1", but of "region2". I have checked and there are many XML files that use endRegion+beginRegion and in which there is an incorrect folding due to this bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405747] New: Samsung Notebook 9 Pro/Pen S Pen (By Wacom) Eraser Button Not Working When Pressed In Proximity
https://bugs.kde.org/show_bug.cgi?id=405747 Bug ID: 405747 Summary: Samsung Notebook 9 Pro/Pen S Pen (By Wacom) Eraser Button Not Working When Pressed In Proximity Product: krita Version: 4.1.7 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: opensystemlinuxdee...@gmail.com Target Milestone: --- STEPS TO REPRODUCE Hold S Pen's eraser side button while selecting tools or drawing. OBSERVED RESULT Still drawing while eraser button is pressed. EXPECTED RESULT Always changes to eraser. SOFTWARE/OS VERSIONS Krita Version: 4.1.7 Qt Version (compiled): 5.9.3 Version (loaded): 5.9.3 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.17763 Pretty Productname: Windows 10 (10.0) ADDITIONAL INFORMATION Samsung's PenS2Helper is based on WinTab, and is similar to this bug report: https://bugs.kde.org/show_bug.cgi?id=341899 Besides, according to Samsung's PenS2Helper.inf inside the driver for Samsung Notebook 9 Pen, it affects the following devices: ``` HID\VEN_WCOM&DEV_0032&Col02 HID\VEN_WCOM&DEV_0033&Col02 HID\VEN_WCOM&DEV_006C&Col01 HID\VEN_WCOM&DEV_006D&Col01 HID\VEN_WCOM&DEV_006E&Col01 ``` -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 405422] ksudoku live-git (commit 09814312d) small-game generation fails with "Unable to generate a puzzle of the chosen variant"
https://bugs.kde.org/show_bug.cgi?id=405422 --- Comment #10 from Duncan <1i5t5.dun...@cox.net> --- (In reply to Jeremy Whiting from comment #6) > Git commit 40e80d73866634c954dce212f2da43cd0fdce8d6 by Jeremy Whiting. > > Don't use KIO copy and QTemporaryFile to load xml definition files. Confirmed: With this on master now, all games seem to work again. Thanks. =:^) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 405748] New: discover crashes when clicking “view updates” in plasmoid
https://bugs.kde.org/show_bug.cgi?id=405748 Bug ID: 405748 Summary: discover crashes when clicking “view updates” in plasmoid Product: Discover Version: 5.15.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: flying-sh...@web.de CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.15.3) Qt Version: 5.12.2 Frameworks Version: 5.56.0 Operating System: Linux 5.0.2-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I updated my kernel manually and afterwards wanted to update the rest of my packages with discover. But when I clicked “view updates”, it reproducibly crashed. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f65c3ce8e00 (LWP 10432))] Thread 10 (Thread 0x7f65977fe700 (LWP 10453)): #0 0x7f65c7cbe4ed in syscall () at /usr/lib/libc.so.6 #1 0x7f65c7fd9c06 in QBasicMutex::lockInternal() () at /usr/lib/libQt5Core.so.5 #2 0x7f65c862c0fe in () at /usr/lib/libQt5Network.so.5 #3 0x7f65c862c8b5 in () at /usr/lib/libQt5Network.so.5 #4 0x7f65c860b7f9 in QSslSocket::startClientEncryption() () at /usr/lib/libQt5Network.so.5 #5 0x7f65c860ca31 in () at /usr/lib/libQt5Network.so.5 #6 0x7f65c8612e21 in () at /usr/lib/libQt5Network.so.5 #7 0x7f65c81c082c in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #8 0x7f65c85d653e in () at /usr/lib/libQt5Network.so.5 #9 0x7f65c85d9500 in () at /usr/lib/libQt5Network.so.5 #10 0x7f65c85e885d in () at /usr/lib/libQt5Network.so.5 #11 0x7f65c9577e24 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #12 0x7f65c957f5f1 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #13 0x7f65c8195df9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #14 0x7f65c81ec916 in () at /usr/lib/libQt5Core.so.5 #15 0x7f65c62a57bf in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #16 0x7f65c62a7739 in () at /usr/lib/libglib-2.0.so.0 #17 0x7f65c62a777e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #18 0x7f65c81ebcb4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #19 0x7f65c8194a8c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #20 0x7f65c7fd8569 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #21 0x7f65c7fd996c in () at /usr/lib/libQt5Core.so.5 #22 0x7f65c744fa9d in start_thread () at /usr/lib/libpthread.so.0 #23 0x7f65c7cc3b23 in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f6597fff700 (LWP 10441)): #0 0x7f65c7cb47a4 in read () at /usr/lib/libc.so.6 #1 0x7f65c6255961 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f65c62a5e40 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f65c62a7636 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f65c62a86d2 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0 #5 0x7f65ad247568 in () at /usr/lib/libgio-2.0.so.0 #6 0x7f65c6282c21 in () at /usr/lib/libglib-2.0.so.0 #7 0x7f65c744fa9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f65c7cc3b23 in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f65acfec700 (LWP 10440)): #0 0x7f65c7cb47a4 in read () at /usr/lib/libc.so.6 #1 0x7f65c6255961 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f65c62a5e40 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f65c62a7636 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f65c62a777e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f65c62a77d2 in () at /usr/lib/libglib-2.0.so.0 #6 0x7f65c6282c21 in () at /usr/lib/libglib-2.0.so.0 #7 0x7f65c744fa9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f65c7cc3b23 in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f65addec700 (LWP 10439)): #0 0x7f65c7455ef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f65c7fdfbc9 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f65c7fdfd08 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f65c7fddc2b in () at /usr/lib/libQt5Core.so.5 #4 0x7f65c7fd996c in () at /usr/lib/libQt5Core.so.5 #5 0x7f65c744fa9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f65c7cc3b23 in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f65ae5ed700 (LWP 10438)): #0 0x7f65c7cbe4ed in sy
[kdeconnect] [Bug 393030] Notification sync plugin no longer works from android app versions to 1.7+ to 1.8.2
https://bugs.kde.org/show_bug.cgi?id=393030 Andreas Kilgus changed: What|Removed |Added CC||k...@fuenfsieben.de --- Comment #3 from Andreas Kilgus --- Same here for kdeconnect 1.3.3 on desktop and KDE Connect 1.12.4 on Android. The phone is running LineageOS 15.1 (= Android 8.1). Notifications do not appear on desktop though all necessary rights are granted. Even if I grant "unlimited data access" (might be an option available in LineageOS only) to KDE Connect, notifications do not show up on desktop. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 405731] Not able to remove or move widgets in panel
https://bugs.kde.org/show_bug.cgi?id=405731 --- Comment #3 from Michail Vourlakos --- You will get used it, don't worry -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 405658] Gwenview doesn't properly shows images loaded from Opera
https://bugs.kde.org/show_bug.cgi?id=405658 --- Comment #4 from xpert45...@gmail.com --- (In reply to xpert45689 from comment #3) > (In reply to Nate Graham from comment #2) > > Can you attach the image itself? > > But the image is attached in attachments https://imgur.com/r6GGRMd -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 405731] Not able to remove or move widgets in panel
https://bugs.kde.org/show_bug.cgi?id=405731 --- Comment #4 from Michail Vourlakos --- will get used to it* -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 384331] Cannot use PAM modules which send text back to kscreenlocker_greet
https://bugs.kde.org/show_bug.cgi?id=384331 Benoit Schneider changed: What|Removed |Added CC||ton.ami.tot...@gmail.com --- Comment #1 from Benoit Schneider --- Hi, Same problem/ask here with a Kubuntu 18.04 I try with lightdm, but after the user lock is session, he can't logon to resume it. If any idear in waiting dev... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kholidays] [Bug 405749] New: Potential issue with holiday listing for Poland
https://bugs.kde.org/show_bug.cgi?id=405749 Bug ID: 405749 Summary: Potential issue with holiday listing for Poland Product: frameworks-kholidays Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: ke...@kde.org Target Milestone: --- This bug was reported via email through an anonymiser service to KDE Press Contacts: It came to our attention, that Calendar Holiday Plugin for KDE, that should contain holidays for Poland is written extremely sloppy and contains extreme and excessive number of days that are not holidays (they are not state holidays and are not days off- therefore calendar is useless and we cannot see which days are off and state celebrated by our Great Nation), but also the national holidays are written very sloppy and the names are not the official names of the holidays (eg. Święto Konstytucji- there's no such holiday in Poland its Konstytucji 3-ego Maja! its not "a holiday of some constitution", holiday has a specific name! Moreover its interwined with some non holiday "equinox", "grampa" and "beer" days. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kholidays] [Bug 405749] Potential issue with holiday listing for Poland
https://bugs.kde.org/show_bug.cgi?id=405749 --- Comment #1 from Christophe Giboudeaux --- After a quick look, the holiday file for Poland wasn't touched since 2015. It contains categories however. The holidays belong to one of these: public, religious, cultural and civil. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 370569] kde4breeze.upd ignores system distributor values from XDG_CONFIG_DIRS/kdeglobals
https://bugs.kde.org/show_bug.cgi?id=370569 Erik Quaeghebeur changed: What|Removed |Added CC||k...@equaeghe.nospammail.net --- Comment #1 from Erik Quaeghebeur --- (In reply to Rohan Garg from comment #0) > It seems like kde4breeze.upd completely ignores the values set in > $XDG_CONFIG_DIRS/kdeglobals by a system distributor causing the script to > override the configured values with Breeze. Is this still an issue? Do you have a ~/.kde4//share/config/kdeglobals? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405722] arm64 core dump support unimplemented
https://bugs.kde.org/show_bug.cgi?id=405722 Mark Wielaard changed: What|Removed |Added Ever confirmed|0 |1 CC||m...@klomp.org Status|REPORTED|CONFIRMED --- Comment #2 from Mark Wielaard --- Hi Sasha, I saw you have a new commit that also fills in the floating point structure. https://github.com/sasshka/valgrind/commit/8903bfd77791723a46505530b993118c7abf1755 Could you please attach (git format-patch HEAD^) the patch to this bug as you would like to commit it? That makes it easier to review. It looks like the only question is whether pstate is setup correctly. I am not sure myself. In other code (synth_ucontext in coregrind/m_sigframe/sigframe-arm64-linux.c) we don't even try... Maybe the vgdb code does, but I cannot find where. Now that you have a bug number could you also add it to your commit message and in the NEWS file? Could you run make regtests before and after your patch to check for tests that now pass (or fail)? Thanks, Mark -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kholidays] [Bug 405749] Potential issue with holiday listing for Poland
https://bugs.kde.org/show_bug.cgi?id=405749 Christophe Giboudeaux changed: What|Removed |Added Keywords||junior-jobs -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 405750] New: Why is .kde4/share/config/kdeglobals still being created?
https://bugs.kde.org/show_bug.cgi?id=405750 Bug ID: 405750 Summary: Why is .kde4/share/config/kdeglobals still being created? Product: kde Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: k...@equaeghe.nospammail.net Target Milestone: --- SUMMARY While I've been on ‘kde 5’ for a long time now, I still have a .kde4 directory in my home directory. The reason is that the file .kde4/share/config/kdeglobals is being recreated even if you delete it. There already is .config/kdeglobals. When I compare both files, it is clear that .kde4/share/config/kdeglobals is a slimmed-down version of .config/kdeglobals. OBSERVED RESULT .kde4/share/config/kdeglobals is recreated EXPECTED RESULT .kde4/share/config/kdeglobals is not recreated SOFTWARE/OS VERSIONS KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 ADDITIONAL INFORMATION https://forum.kde.org/viewtopic.php?f=289&t=143296 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405751] New: plasma shell crash when I clicked on [Leave] menu
https://bugs.kde.org/show_bug.cgi?id=405751 Bug ID: 405751 Summary: plasma shell crash when I clicked on [Leave] menu Product: plasmashell Version: 5.15.3 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ja...@ticctv.cn CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.15.3) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.18.0-16-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: - What I was doing when the application crashed: I setup a multi-seat system on my PC, but if I login on seat-1, plasma shell crash when I clicked on [Leave] menu The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd397f10880 (LWP 21353))] Thread 19 (Thread 0x7fd3080d9700 (LWP 21920)): #0 0x7fd391345bf9 in __GI___poll (fds=0x7fd36470, nfds=1, timeout=3208630) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fd38b1ac539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd38b1ac64c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd391c8815b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fd391c2964a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fd391a5141a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fd309305f77 in KCupsConnection::run() () from /usr/lib/x86_64-linux-gnu/libkcupslib.so #7 0x7fd391a52bc2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fd38e5676db in start_thread (arg=0x7fd3080d9700) at pthread_create.c:463 #9 0x7fd39135288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7fd347734700 (LWP 21533)): #0 0x7fd38e56d9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55fd91655940) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55fd916558f0, cond=0x55fd91655918) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55fd91655918, mutex=0x55fd916558f0) at pthread_cond_wait.c:655 #3 0x7fd36e36ae6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fd36e36ab97 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fd38e5676db in start_thread (arg=0x7fd347734700) at pthread_create.c:463 #6 0x7fd39135288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7fd35affd700 (LWP 21520)): #0 0x7fd391c87e6d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7fd38b1aba98 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd38b1ac46b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd38b1ac64c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fd391c8815b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fd391c2964a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fd391a5141a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fd395d0e1c6 in QQuickPixmapReader::run (this=0x55fd90a61c00) at util/qquickpixmapcache.cpp:949 #8 0x7fd391a52bc2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fd38e5676db in start_thread (arg=0x7fd35affd700) at pthread_create.c:463 #10 0x7fd39135288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7fd35b7fe700 (LWP 21434)): #0 0x7fd38e56d9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55fd90dffdb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55fd90dffd68, cond=0x55fd90dffd90) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55fd90dffd90, mutex=0x55fd90dffd68) at pthread_cond_wait.c:655 #3 0x7fd36e36ae6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fd36e36ab97 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fd38e5676db in start_thread (arg=0x7fd35b7fe700) at pthread_create.c:463 #6 0x7fd39135288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7fd3577fe700 (LWP 21431)): #0 0x7fd38e56d9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55fd90dffdb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55fd90dffd68, cond=0x55fd90dffd90) a
[plasmashell] [Bug 405751] plasma shell crash when I clicked on [Leave] menu
https://bugs.kde.org/show_bug.cgi?id=405751 --- Comment #1 from jacky lau --- I'm not using LightDM, I'm using sddm 0.17.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kholidays] [Bug 405749] Potential issue with holiday listing for Poland
https://bugs.kde.org/show_bug.cgi?id=405749 --- Comment #2 from Kenny Duffus --- (In reply to Christophe Giboudeaux from comment #1) > After a quick look, the holiday file for Poland wasn't touched since 2015. > > It contains categories however. The holidays belong to one of these: public, > religious, cultural and civil. Thanks for having a look -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399696] Forced close with Internal Error message in kis_shortcut_matcher.cpp, line 557 [USE_QT_XCB]
https://bugs.kde.org/show_bug.cgi?id=399696 --- Comment #14 from Tyson Tan --- (In reply to Dmitry Kazakov from comment #13) > Hi, Tyson! > > Could you check the very latest AppImage? It looks like older builds had > non-patched Qt in it, so the problem was not fixed completely. The latest > AppImage seem to have this problem solved: > > https://binary-factory.kde.org/job/Krita_Nightly_Appimage_Build/ > > > PS: > I should still try to fix this problem for the distribution builds, but it > is a separate task. Thanks Dmitry, it's not crashing anymore. Another one of those elusive upstream complications, huh? I hope it doesn't make your days too difficult! :) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 405752] New: Make Konsole search field longer, better if it fill all width of a Konsole window
https://bugs.kde.org/show_bug.cgi?id=405752 Bug ID: 405752 Summary: Make Konsole search field longer, better if it fill all width of a Konsole window Product: konsole Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: mambus.sk...@gmail.com Target Milestone: --- Hi! I think it fill be great if Konsole search field fill all width of Konsole window so we can see what we search, not only partly. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kholidays] [Bug 405749] Potential issue with holiday listing for Poland
https://bugs.kde.org/show_bug.cgi?id=405749 Christophe Giboudeaux changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 405016] Dock stays visible when moving mouse in and out quickly
https://bugs.kde.org/show_bug.cgi?id=405016 Mathias Tillman changed: What|Removed |Added CC||master.ho...@gmail.com --- Comment #4 from Mathias Tillman --- Having the same problem here. I have a theory that it's caused by the user leaving the MouseArea (for the window preview) before it's active, meaning the onContainsMouseChanged signal is never sent. However, I haven't done enough testing to verify this is the case. Unfortunately, it also happens quite rarely for me, so I haven't been able to find a way to reproduce it reliably. I will do some testing and report back what I find. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 405745] endless browser launch
https://bugs.kde.org/show_bug.cgi?id=405745 David Rosca changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from David Rosca --- Please elaborate, for now I am closing it. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 405744] endless browser launch
https://bugs.kde.org/show_bug.cgi?id=405744 David Rosca changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from David Rosca --- Please elaborate, for now I am closing it. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 214547] Kosole KPart needs an API to retrieve $PWD
https://bugs.kde.org/show_bug.cgi?id=214547 Mateusz Mikuła changed: What|Removed |Added CC||mati...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 400337] Pressing Tab key when focus is in search field of sidebar view does nothing
https://bugs.kde.org/show_bug.cgi?id=400337 Shlomi Fish changed: What|Removed |Added CC||shlo...@shlomifish.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405753] New: Several issues with onion skins due way they're composited.
https://bugs.kde.org/show_bug.cgi?id=405753 Bug ID: 405753 Summary: Several issues with onion skins due way they're composited. Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: griffinval...@gmail.com Target Milestone: --- SUMMARY I am going to pile these up here because I think they're all symptoms of the same issue, namely the way how onion skins are composited. -- 1. Grayscale animated layers have gray onion skins. -- STEPS TO REPRODUCE 1. Have an animated layer. 2. Show the onion skins, observe how colorful they are. 3. Convert the layer to grayscale. 4. Observe how onion skins are now gray. -- 2. Transform tool boundary takes onion skins into account. -- 1. Have an animated paint layer. 2. Try transforming a frame, observe the size of the bounding box. 3. Cancel transformation, turn on onion skins. 4. Try transforming the layer again, observe how the bounding box now is larger, large enough to encompass the frame and its onion skins. -- 3. Onion skins can be color picked -- 1. Have onion skins active on an animated layer. 2. Ctrl+click or whatever you have set 'pick color from merged image' to. 3. Observe you can pick colors from the onion skin. -- 4. Onion skins affect the fill-tool results -- 1. Have onion skins active on an animated layer. 2. Use the fill tool. 3. Observe how the onion skin is used by the fill tool as well. Just to clarify, these are my fill tool settings: Fast mode: No Threshold: 0px Grow selection: 1px Feathering radius: 0px Fill entire selection: No Limit to current layer: No Use pattern: No I will add more as I come across them(and they seem to be an issue with compositing) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kholidays] [Bug 405749] Potential issue with holiday listing for Poland
https://bugs.kde.org/show_bug.cgi?id=405749 Christophe Giboudeaux changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://cgit.kde.org/kholid ||ays.git/commit/?id=d1f6062a ||818cfab2adef6a3219ab8b9154b ||8c78a Resolution|--- |FIXED Version Fixed In||5.57 --- Comment #3 from Christophe Giboudeaux --- Strange the bug wasn't closed automatically. https://cgit.kde.org/kholidays.git/commit/?id=d1f6062a818cfab2adef6a3219ab8b9154b8c78a fixes the wrong name for the Constitution day, sorts the categories and I added english comments if anyone needs to touch the file in the future. I also tried loading the polish days in korganizer, the non-working days (categorized 'public') have a different color. Without a proper way to contact the mail author, that's the best we can do. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400764] Devices see each other, but kdeconnect-cli reports 0 devices found
https://bugs.kde.org/show_bug.cgi?id=400764 --- Comment #2 from Denis Kasak --- I'm still seeing this with kdeconnect-cli 1.3.3. When was this fixed? -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 404275] Crash on startup
https://bugs.kde.org/show_bug.cgi?id=404275 --- Comment #1 from Seijiro Moriyama --- Created attachment 118969 --> https://bugs.kde.org/attachment.cgi?id=118969&action=edit New crash information added by DrKonqi korganizer (5.10.3) using Qt 5.12.0 - What I was doing when the application crashed: Ran korganizer from console. Log shown below: seijirom@macmini:~$ korganizer org.kde.pim.kidentitymanagement: IdentityManager: There was no default identity. Marking first one as default. KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = korganizer path = /usr/bin pid = 5436 KCrash: Arguments: /usr/bin/korganizer KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 [1]+ Stopped korganizer seijirom@macmini:~$ -- Backtrace (Reduced): #6 std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x50) at /usr/include/c++/7/bits/atomic_base.h:396 #7 QAtomicOps::load (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:227 #8 QBasicAtomicInteger::load (this=0x50) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:103 [...] #10 QString::QString (other=..., this=0x7ffc3b8f9740) at ../../include/QtCore/../../src/corelib/tools/qstring.h:958 #11 QTimeZonePrivate::Data::Data (this=0x7ffc3b8f9740) at tools/qtimezoneprivate_p.h:81 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 404275] Crash on startup
https://bugs.kde.org/show_bug.cgi?id=404275 Seijiro Moriyama changed: What|Removed |Added CC||seijiro.moriy...@anagix.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kholidays] [Bug 405749] Potential issue with holiday listing for Poland
https://bugs.kde.org/show_bug.cgi?id=405749 --- Comment #4 from Kenny Duffus --- (In reply to Christophe Giboudeaux from comment #3) > Strange the bug wasn't closed automatically. > > https://cgit.kde.org/kholidays.git/commit/ > ?id=d1f6062a818cfab2adef6a3219ab8b9154b8c78a fixes the wrong name for the > Constitution day, sorts the categories and I added english comments if > anyone needs to touch the file in the future. > > I also tried loading the polish days in korganizer, the non-working days > (categorized 'public') have a different color. > > Without a proper way to contact the mail author, that's the best we can do. Thanks -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405754] New: Make pinned applications open inplace
https://bugs.kde.org/show_bug.cgi?id=405754 Bug ID: 405754 Summary: Make pinned applications open inplace Product: plasmashell Version: 5.13.5 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: t.soer...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Say you have Firefox pinned on the taskbar, all the way to the left in position 1, with shortcuts for switching between windows. If you press , and Firefox is closed, it will open, but regardless of taskbar sorting method it is not guaranteed that it will open at position 1 if there are other programs already open, and if so then you cannot switch to it using after it has been opened. I want pinned applications to open in place. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 391293] Frequent Crashing On Start
https://bugs.kde.org/show_bug.cgi?id=391293 Stijn changed: What|Removed |Added CC||valenst...@msn.com --- Comment #1 from Stijn --- falkon crashes even on startup: (in french): Plugin "KDEFrameworksIntegration.so" not found Falkon: 1 extensions loaded falkon: ../nouveau/pushbuf.c :723 : nouveau_pushbuf_data: l'assertion « kref » a échoué -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366632] Windows not resized to maximize area if initially too large
https://bugs.kde.org/show_bug.cgi?id=366632 --- Comment #9 from Patrick Silva --- This bug persists on neon dev unstable. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 405503] Text cut off on buttons in Dolphin's "Configure the menu" window (Brazilian Portuguese and possibly other languages affected)
https://bugs.kde.org/show_bug.cgi?id=405503 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #2 from Patrick Silva --- It's not fixed with Qt 5.13 beta1 on Arch Linux. Both Bug 400118 and Bug 397630 mentioned in the upstream bug are fixed. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 405736] falkon:start doesn't automatically focus search bar
https://bugs.kde.org/show_bug.cgi?id=405736 Prasenjit Kumar Shaw changed: What|Removed |Added CC||shawprasenji...@gmail.com --- Comment #1 from Prasenjit Kumar Shaw --- On setting falkon:start as new tab page, the falkon:start page loads up by default which itself has a search bar and that is in focus so you can directly write your query there. The page acts just like any other search engine page where on opening that page the search field is in focus. As such why do you want the address bar to be in focus? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 405503] Text cut off on buttons in Dolphin's "Configure the menu" window (Brazilian Portuguese and possibly other languages affected)
https://bugs.kde.org/show_bug.cgi?id=405503 --- Comment #3 from Patrick Silva --- duplicate of bug 403043 -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 405755] New: Problem when we change to new connect api when sender and receiver has default value
https://bugs.kde.org/show_bug.cgi?id=405755 Bug ID: 405755 Summary: Problem when we change to new connect api when sender and receiver has default value Product: clazy Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mon...@kde.org CC: smart...@kde.org Target Milestone: --- Bug when converting to new connect api. As reported by Albert and you can see phabricator review for this bug (in sddm) https://phabricator.kde.org/D19959 in sddm-kcm clazy converted: -connect(configUi->autoLogin, SIGNAL(clicked()), SIGNAL(changed())); +connect(configUi->autoLogin, &QGroupBox::clicked, this, &AdvanceConfig::changed); but signal AdvanceConfig::changed had a default value Q_SIGNALS: void changed(bool changed=true); and QGroupBox::clicked has default value == false => when we use new connect api it will emit: QGroupBox::clicked(value == false) => emit AdvanceConfig::changed(false) as we send value from clicked to changed => Prevously when we clicked on QGroupBox it emitted changed(true) as we didn't send "sender value" on reveiver. For me we mustn't change connect api when old api doesn't use argument and sender and receiver has a default argument. I don't know if we can detect it but it will -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 405755] Problem when we change to new connect api when sender and receiver has default value
https://bugs.kde.org/show_bug.cgi?id=405755 Laurent Montel changed: What|Removed |Added CC||aa...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 405736] falkon:start doesn't automatically focus search bar
https://bugs.kde.org/show_bug.cgi?id=405736 --- Comment #2 from a...@msgsafe.io --- (In reply to Prasenjit Kumar Shaw from comment #1) > On setting falkon:start as new tab page, the falkon:start page loads up by > default which itself has a search bar and that is in focus so you can > directly write your query there. The page acts just like any other search > engine page where on opening that page the search field is in focus. As such > why do you want the address bar to be in focus? The bug I'm reporting is that the search bar is NOT in focus when opening the new tab, nor the address bar. Sorry for not making that clear enough. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400461] Cursor doesn't change or fails to revert to pointer while using zoom effect (Firefox and Thunderbird)
https://bugs.kde.org/show_bug.cgi?id=400461 --- Comment #8 from petrk --- Created attachment 118970 --> https://bugs.kde.org/attachment.cgi?id=118970&action=edit demo Cursor was not captured when screen was zoomed out, that's just something to do with pipewire/obs/kwin. It's working as expected when zoomed out. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405756] New: Surface Studio Pen side button no longer brings up Circle menu correction
https://bugs.kde.org/show_bug.cgi?id=405756 Bug ID: 405756 Summary: Surface Studio Pen side button no longer brings up Circle menu correction Product: krita Version: 4.1.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Color Selectors Assignee: krita-bugs-n...@kde.org Reporter: ericj...@thejcrew.net Target Milestone: --- SUMMARY This started happening in the last couple of days. The only thing I have changed on my computer is that I installed Office 365 UWP, then Office 365 desktop STEPS TO REPRODUCE 1. Press side button on surface pen 2. Tap the screen OBSERVED RESULT Result: Circle menu appears, then disappears the moment the pen lifts off the screen. EXPECTED RESULT As of two days ago, this menu would stay active after lifting off the pen. SOFTWARE/OS VERSIONS Windows: Win10 build 18860 (prerelease) 190315-2228 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 405757] New: Discover hangs on attempt to remove or update plasmoid
https://bugs.kde.org/show_bug.cgi?id=405757 Bug ID: 405757 Summary: Discover hangs on attempt to remove or update plasmoid Product: Discover Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: soundbulle...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY For the past few weeks, there have been updates to several Plasmoids (Air Quality Widget, Media Controller Compact, Window Buttons Applet, Window Title Applet) that I downloaded from store.kde.org sitting in the update queue. Every time I attempt to update all, it hangs with 0% in the task bar and refuses to allow me to cancel any task. When I attempt to remove the Plasmoids through Discover it hangs at 0% and does not allow me to cancel the task. If I unclick the Plasmoids (it appears to be all of them) in order to update other packages as soon as I click "update all" they are re-enabled against my wishes and the process hangs at 0%. I've been just updating my system using apt in the meantime. STEPS TO REPRODUCE 1. Selectively attempt to update each of the 4 Plasmoids individually, as a whole, and attempts to uninstall 2. Observe task stuck at 0% OBSERVED RESULT System refuses to close or progress. "Logout cancelled by usr/bin/plasma-discover" EXPECTED RESULT Plasmoids should be able to be either updated, uninstalled, or at the very least ignored through Discover SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 18.10 KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION It appears to be related to but distinct from Bug 404358. (This is my first bug report, apologies if syntax is vague or incorrect) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405756] Surface Studio Pen side button no longer brings up Circle menu correction
https://bugs.kde.org/show_bug.cgi?id=405756 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Um... If you didn't change Krita, then this probably isn't a bug in krita, but a problem with something else that changed stuff on your system? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405756] Circle menu dissappears immediately when tab mode is active
https://bugs.kde.org/show_bug.cgi?id=405756 Eric Jorgensen changed: What|Removed |Added Summary|Surface Studio Pen side |Circle menu dissappears |button no longer brings up |immediately when tab mode |Circle menu correction |is active --- Comment #2 from Eric Jorgensen --- I have some more information: The bug only happens when I press Tab to enter full screen mode. When tab mode is active, the circle menu goes away immediate unless I do just a very tiny tap. When tab mode is off, -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405756] Circle menu dissappears immediately when tab mode is active
https://bugs.kde.org/show_bug.cgi?id=405756 --- Comment #3 from Eric Jorgensen --- … continuing: When the tab mode is off, the menu comes up and stays up every time, regardless of how I tap the screen -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 366475] Buttons in notifications
https://bugs.kde.org/show_bug.cgi?id=366475 --- Comment #5 from Nicolas Fella --- Git commit c2cd60773b5738537f099cb306382f6d039a564a by Nicolas Fella. Committed on 22/03/2019 at 16:07. Pushed by nicolasfella into branch 'master'. Send notification actions Summary: Store PendingIntents from notification actions. Send list of notifications to desktop and trigger Intent when matching packet arrives. Test Plan: Create test notification, trigger package is received correctly. Whether intent.send() is actually successful is NOT yet tested. Reviewers: #kde_connect, sredman Reviewed By: #kde_connect, sredman Subscribers: sredman, apol, MatMaul, kdeconnect, mtijink, #kde_connect Tags: #kde_connect Differential Revision: https://phabricator.kde.org/D12294 M +48 -3 src/org/kde/kdeconnect/Plugins/NotificationsPlugin/NotificationsPlugin.java https://invent.kde.org/kde/kdeconnect-android/commit/c2cd60773b5738537f099cb306382f6d039a564a -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 405755] Problem when we change to new connect api when sender and receiver has default value
https://bugs.kde.org/show_bug.cgi?id=405755 Sergio Martins changed: What|Removed |Added Assignee|unassigned-b...@kde.org |smart...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405230] Recent 4.2.0 pre-alpha appimages are disabling the Layers Docker
https://bugs.kde.org/show_bug.cgi?id=405230 Tymond changed: What|Removed |Added Latest Commit||https://commits.kde.org/kri ||ta/ad1f27076d5df97326f9b07e ||b70bd93e75902d1b Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Tymond --- Git commit ad1f27076d5df97326f9b07eb70bd93e75902d1b by Agata Cacko. Committed on 22/03/2019 at 15:47. Pushed by tymond into branch 'master'. Fix Background Color change after flattening Before this commit if you flatten the image using Layer -> Flatten Image, the resulting image had canvas background color set to transparent black. Now the resulting image has the same canvas color as before the flattening. M +1-3libs/image/kis_image.cc https://commits.kde.org/krita/ad1f27076d5df97326f9b07eb70bd93e75902d1b -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405356] PPC64, xvcvsxdsp, xvcvuxdsp are supposed to write the 32-bit result to the upper and lower 32-bits of the 64-bit result
https://bugs.kde.org/show_bug.cgi?id=405356 --- Comment #1 from Carl Love --- Created attachment 118971 --> https://bugs.kde.org/attachment.cgi?id=118971&action=edit fix for xvcvsxdsp and xvcvuxddp instructions The attached patch was committed to fix the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405754] Make pinned applications open inplace
https://bugs.kde.org/show_bug.cgi?id=405754 Eike Hein changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Eike Hein --- You can either switch the sort mode to "Manual" and disable "Keep launchers seperate", or switch to Icons-only Task Manager. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 405758] New: Kmail crash dopo blocco
https://bugs.kde.org/show_bug.cgi?id=405758 Bug ID: 405758 Summary: Kmail crash dopo blocco Product: kmail2 Version: 5.10.3 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: andrea.sora...@gmail.com Target Milestone: --- Application: kmail (5.10.3) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.15.0-46-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: Kmail è bloccato: non riceve la posta, non mi consente di cancellare le email, non applica i filtri. Dopo averlo chiuso, alla riapertura non ricompare l'icona nella tray area. Modificando le impostazioni per ripristinare l'icona nella tray area il prgramma crasha. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f31e1f41bc0 (LWP 5379))] Thread 9 (Thread 0x7f30f9ce9700 (LWP 6264)): #0 0x7f31def790b4 in __GI___libc_read (fd=30, buf=0x7f30f9ce881e, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f31b9723021 in pa_read () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #2 0x7f31c12fea2e in pa_mainloop_prepare () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f31c12ff4a0 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f31c12ff560 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f31c130d3c9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f31b9752318 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #7 0x7f31d47356db in start_thread (arg=0x7f30f9ce9700) at pthread_create.c:463 #8 0x7f31def8a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f31826a8700 (LWP 5572)): #0 0x7f31d473b9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f31c4c52fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7f31c4c52f68, cond=0x7f31c4c52f90) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7f31c4c52f90, mutex=0x7f31c4c52f68) at pthread_cond_wait.c:655 #3 0x7f31c495c844 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f31c495c889 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f31d47356db in start_thread (arg=0x7f31826a8700) at pthread_create.c:463 #6 0x7f31def8a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f3198ae3700 (LWP 5385)): #0 0x7f31def7dbf9 in __GI___poll (fds=0x7f318404aa00, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f31d2869539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f31d286964c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f31df8c015b in QEventDispatcherGlib::processEvents (this=0x7f3184000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f31df86164a in QEventLoop::exec (this=this@entry=0x7f3198ae29e0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f31df68941a in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7f31df68abc2 in QThreadPrivate::start (arg=0x560bd70181c0) at thread/qthread_unix.cpp:361 #7 0x7f31d47356db in start_thread (arg=0x7f3198ae3700) at pthread_create.c:463 #8 0x7f31def8a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f31992e4700 (LWP 5384)): #0 0x7f31d28694e6 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f31d286964c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f31df8c015b in QEventDispatcherGlib::processEvents (this=0x7f319b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #3 0x7f31df86164a in QEventLoop::exec (this=this@entry=0x7f31992e39e0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #4 0x7f31df68941a in QThread::exec (this=) at thread/qthread.cpp:531 #5 0x7f31df68abc2 in QThreadPrivate::start (arg=0x560bd6fbfa10) at thread/qthread_unix.cpp:361 #6 0x7f31d47356db in start_thread (arg=0x7f31992e4700) at pthread_create.c:463 #7 0x7f31def8a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f3199d29700 (LWP 5383)): #0 0x7f31d286644b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f31d28689d3 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f31d286946b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f31d286964c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0
[valgrind] [Bug 405362] PPC64, vmsummbm instruction doesn't handle overflow case correctly
https://bugs.kde.org/show_bug.cgi?id=405362 --- Comment #1 from Carl Love --- Created attachment 118972 --> https://bugs.kde.org/attachment.cgi?id=118972&action=edit fix for vmsummbm instruction The attached patch fixes the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405754] Make pinned applications open inplace
https://bugs.kde.org/show_bug.cgi?id=405754 --- Comment #2 from t.soer...@gmail.com --- Very much so. Thanks a bunch! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405363] PPC64, xvcvdpsxws, xvcvdpuxws, do not handle NaN arguments correctly.
https://bugs.kde.org/show_bug.cgi?id=405363 --- Comment #1 from Carl Love --- Created attachment 118973 --> https://bugs.kde.org/attachment.cgi?id=118973&action=edit fix for instructions xvcvdpsxws, xvcvdpuxws The patch was committed to fix the issue. commit d4686f635ec9d9ee9f5aa4c6675d486c89e2c7a6 Author: Carl Love Date: Fri Mar 22 12:26:00 2019 -0500 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 391671] Face recognition fails giving a lot of addition effort to correct the errors.
https://bugs.kde.org/show_bug.cgi?id=391671 --- Comment #3 from Bob Fearnley --- I have tried it but the results are inconclusive so I think I need to delete the recognition database - how can I do that? I had the options selected as in the attached image: Work on all processor cores Clear and rebuild training data Even doing that I had some very strange results. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405365] PPC64, function _get_maxmin_fp_NaN() doesn't handle QNaN, SNaN case correctly
https://bugs.kde.org/show_bug.cgi?id=405365 --- Comment #1 from Carl Love --- Created attachment 118974 --> https://bugs.kde.org/attachment.cgi?id=118974&action=edit fix the _get_maxmin_fp_NAN function The attached patch was committed to fix the issue. commit e9986500957ae53ef6374e86938188bca4d1c6df Author: Carl Love Date: Fri Mar 22 12:32:29 2019 -0500 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 391671] Face recognition fails giving a lot of addition effort to correct the errors.
https://bugs.kde.org/show_bug.cgi?id=391671 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #4 from caulier.gil...@gmail.com --- If you wan to be sure, remove the recognition.db sqlite file. It will be re-created automatically. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405733] PPC64, xvcvdpsp should write 32-bit result to upper and lower 32-bits of the 64-bit destination field.
https://bugs.kde.org/show_bug.cgi?id=405733 --- Comment #1 from Carl Love --- Created attachment 118975 --> https://bugs.kde.org/attachment.cgi?id=118975&action=edit fix for the xvcvdpsp instruction The attached patch was committed to fix the issue. commit 91bd56be4153cb5cf6d1fa80ade4b2432ff81ab0 Author: Carl Love Date: Fri Mar 22 12:39:32 2019 -0500 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 386088] Brushes are very laggy
https://bugs.kde.org/show_bug.cgi?id=386088 Shaikha changed: What|Removed |Added CC||shosho.za...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405733] PPC64, xvcvdpsp should write 32-bit result to upper and lower 32-bits of the 64-bit destination field.
https://bugs.kde.org/show_bug.cgi?id=405733 Carl Love changed: What|Removed |Added Attachment #118975|0 |1 is obsolete|| --- Comment #2 from Carl Love --- Created attachment 118976 --> https://bugs.kde.org/attachment.cgi?id=118976&action=edit version 2, a line got left out of the previous patch Updated patch, caught the missing line before pushing patch to mainline. commit 30a24515f09f9118c469ae11c9d574da729c97ed Author: Carl Love Date: Fri Mar 22 12:42:27 2019 -0500 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405759] New: my brushes are very laggy, they freeze then continue
https://bugs.kde.org/show_bug.cgi?id=405759 Bug ID: 405759 Summary: my brushes are very laggy, they freeze then continue Product: krita Version: unspecified Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: crash Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: shosho.za...@gmail.com Target Milestone: --- my brushes are very laggy, I just downloaded Krita and giving it a try but every time I try to draw the brush freezes then it continues, which makes me unable to draw properly -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405734] PPC64, vrlwnm, vrlwmi, vrldrm, vrldmi do not work properly when me < mb
https://bugs.kde.org/show_bug.cgi?id=405734 --- Comment #1 from Carl Love --- Created attachment 118977 --> https://bugs.kde.org/attachment.cgi?id=118977&action=edit Fix for vrlwnm, vrlwmi, vrldrm, vrldmi instructions The attached patch was committed to fix the issue. commit ed80ebfa1704682de3a9a5ddfe3ce4ffef1878da Author: Carl Love Date: Fri Mar 22 12:50:52 2019 -0500 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 405760] New: Dolphin crashed
https://bugs.kde.org/show_bug.cgi?id=405760 Bug ID: 405760 Summary: Dolphin crashed Product: dolphin Version: 18.12.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: govers...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (18.12.3) Qt Version: 5.12.2 Frameworks Version: 5.56.0 Operating System: Linux 5.0.2-1-ck-ivybridge x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: When I tried to paste a file from one tab to another. Using keyboard shortcuts. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f675dccfc80 (LWP 4217))] Thread 3 (Thread 0x7f674e146700 (LWP 4227)): #0 0x7f6765b23c21 in poll () at /usr/lib/libc.so.6 #1 0x7f676137c690 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f676137c77e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f6763c03cb4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f6763baca8c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f67639f0569 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f67639f196c in () at /usr/lib/libQt5Core.so.5 #7 0x7f67622c8a9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f6765b2eb23 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f6757ea5700 (LWP 4223)): #0 0x7f6765b23c21 in poll () at /usr/lib/libc.so.6 #1 0x7f676137c690 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f676137c77e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f6763c03cb4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f6763baca8c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f67639f0569 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f6763e77ba6 in () at /usr/lib/libQt5DBus.so.5 #7 0x7f67639f196c in () at /usr/lib/libQt5Core.so.5 #8 0x7f67622c8a9d in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f6765b2eb23 in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f675dccfc80 (LWP 4217)): [KCrash Handler] #6 0x7f6763bd2d2b in () at /usr/lib/libQt5Core.so.5 #7 0x7f6763bd3dfd in QMimeData::data(QString const&) const () at /usr/lib/libQt5Core.so.5 #8 0x7f6765643f04 in KIO::isClipboardDataCut(QMimeData const*) () at /usr/lib/libKF5KIOWidgets.so.5 #9 0x7f6765672f3d in () at /usr/lib/libKF5KIOWidgets.so.5 #10 0x7f67656732e1 in () at /usr/lib/libKF5KIOWidgets.so.5 #11 0x7f6763bd9102 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #12 0x7f6764607e24 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #13 0x7f676460f5f1 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #14 0x7f6763baddf9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #15 0x7f6763bb0ee8 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #16 0x7f6763c046c4 in () at /usr/lib/libQt5Core.so.5 #17 0x7f676137a7bf in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #18 0x7f676137c739 in () at /usr/lib/libglib-2.0.so.0 #19 0x7f676137c77e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #20 0x7f6763c03c99 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #21 0x7f6763baca8c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #22 0x7f6763bb4de6 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #23 0x7f6765c37617 in kdemain () at /usr/lib/libkdeinit5_dolphin.so #24 0x7f6765a57223 in __libc_start_main () at /usr/lib/libc.so.6 #25 0x55fdda76e05e in _start () [Inferior 1 (process 4217) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 366475] Buttons in notifications
https://bugs.kde.org/show_bug.cgi?id=366475 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405230] Recent 4.2.0 pre-alpha appimages are disabling the Layers Docker
https://bugs.kde.org/show_bug.cgi?id=405230 Tymond changed: What|Removed |Added Ever confirmed|1 |0 Resolution|FIXED |--- CC||tamtamy.tym...@gmail.com Status|RESOLVED|REPORTED --- Comment #3 from Tymond --- Looks like I closed a wrong bug :( Sorry! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405684] Flatten image with canvas background color gives non-transparent background in result
https://bugs.kde.org/show_bug.cgi?id=405684 Tymond changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Tymond --- This commit changes only the canvas color after the flattening: now it is the same as before the flattening. The change of behaviour of canvas color during flattening requires a discussion. - Git commit ad1f27076d5df97326f9b07eb70bd93e75902d1b by Agata Cacko. Committed on 22/03/2019 at 15:47. Pushed by tymond into branch 'master'. Fix Background Color change after flattening Before this commit if you flatten the image using Layer -> Flatten Image, the resulting image had canvas background color set to transparent black. Now the resulting image has the same canvas color as before the flattening. M +1-3libs/image/kis_image.cc https://commits.kde.org/krita/ad1f27076d5df97326f9b07eb70bd93e75902d1b -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405684] Flatten image with canvas background color gives non-transparent background in result
https://bugs.kde.org/show_bug.cgi?id=405684 Tymond changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |tamtamy.tym...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 405529] Add support for kio-gdrive (Google Drive)?
https://bugs.kde.org/show_bug.cgi?id=405529 Ivan Čukić changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #1 from Ivan Čukić --- Unfortunately, this is not possible because encryption backends require proper file-systems which GDrive KIO is not. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 405761] New: On Wakeup windows trigger desktop blackouts.
https://bugs.kde.org/show_bug.cgi?id=405761 Bug ID: 405761 Summary: On Wakeup windows trigger desktop blackouts. Product: frameworks-plasma Version: 5.44.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: libplasma Assignee: notm...@gmail.com Reporter: mcarpen...@smtcorp.com Target Milestone: --- SUMMARY When waking the desktop from being locked or sleep after some time, new windows or alerts create black boxes over a majority of the desktop, clicking to an existing window or on the desktop clears these boxes. Only thing I've attempted to remedy this is to do `kquitapp5 plasmashell` and then `kstart5 plasmashell` this doesn't seem to solve the issue. STEPS TO REPRODUCE 1. Lock or sleep the device 2. Wake the device and login 3. Create a new window or generate an alert OBSERVED RESULT Desktop gets covered by black boxes/artifacts. EXPECTED RESULT Desktop remains visible and no boxes are generated. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KUBUNTU 18.04 (available in About System) KDE Plasma Version: 5.12.7 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 405525] [DBUS] add newVault() and importVault() methods which take all needed parameters from DBUS call
https://bugs.kde.org/show_bug.cgi?id=405525 --- Comment #1 from Ivan Čukić --- This would be problematic since the backends have different options. What /could/ be possible is to have API that assumes all options have the default values - and only leaves device, mountPoint and backend. The password can not be passed in via dbus safely, so that part is definitely out :) Alternatively, there could be a plasma-vault-cli console app for doing this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400658] Impossible to walk through all apps or all windows of the current app on Wayland if numlock is enabled on login
https://bugs.kde.org/show_bug.cgi?id=400658 Oskar changed: What|Removed |Added CC||k...@kinomoto.me -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 405506] Needs specific instructions about how to build from source
https://bugs.kde.org/show_bug.cgi?id=405506 michael changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kdi ||ff3/0ee48eb4dc2cde71d2d5e04 ||c24de491f482ac133 Version Fixed In||1.8 Status|REPORTED|RESOLVED --- Comment #1 from michael --- Git commit 0ee48eb4dc2cde71d2d5e04c24de491f482ac133 by Michael Reeves. Committed on 22/03/2019 at 18:54. Pushed by mreeves into branch 'master'. Add install instruction FIXED-IN:1.8 M +49 -2INSTALL https://commits.kde.org/kdiff3/0ee48eb4dc2cde71d2d5e04c24de491f482ac133 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 376464] JPG clip rendered as white screen although preview works
https://bugs.kde.org/show_bug.cgi?id=376464 --- Comment #18 from emohr --- Solved in the refactoring version. Solved with the upcoming 18.12.3 Windows version. -- You are receiving this mail because: You are watching all bug changes.
[plasma-mediacenter] [Bug 405762] New: xesam:artist is not read as List
https://bugs.kde.org/show_bug.cgi?id=405762 Bug ID: 405762 Summary: xesam:artist is not read as List Product: plasma-mediacenter Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: MediaController Assignee: ksi...@gmail.com Reporter: 2...@web.de Target Milestone: --- The MPRIS specification defines the xesam:artist property as being a String Array, not a string, see https://www.freedesktop.org/wiki/Specifications/mpris-spec/metadata/#index6h4. However, the mediacontroller only shows the artist field when it is a plain string, which results in this error in the console when launching plasmawindowed org.kde.plasma.mediacontroller while a specification-conform MediaPlayer runs: file:///usr/share/plasma/plasmoids/org.kde.plasma.mediacontroller/contents/ui/main.qml:52:5: Unable to assign QStringList to QString And does not show any artist. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 402899] kate does not remember the cursor position of last view or edit
https://bugs.kde.org/show_bug.cgi?id=402899 Ahmad Samir changed: What|Removed |Added Ever confirmed|0 |1 CC||a.samir...@gmail.com Status|REPORTED|CONFIRMED --- Comment #1 from Ahmad Samir --- It seems this issue is caused by this commit: https://cgit.kde.org/kate.git/commit/?id=e3ece7bd45d2743b3c36ad856abd12ac9ba282d6 closeDocument(untitledDoc) isn't called, so this chain doesn't happen: KateDocManager::documentsDeleted -> KateViewManager::documentsDeleted -> KateViewManager::createView, the latter calls KTextEditor::View::readSessionConfig() to restore the cursor position. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 405591] Plasmoid's tool-tip information should be displayed on mouse hover
https://bugs.kde.org/show_bug.cgi?id=405591 Michail Vourlakos changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 405517] Inconsistent Scaling and Jagged Icon with hover on
https://bugs.kde.org/show_bug.cgi?id=405517 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 391293] Frequent Crashing On Start
https://bugs.kde.org/show_bug.cgi?id=391293 Juraj changed: What|Removed |Added CC||sgd.or...@gmail.com --- Comment #2 from Juraj --- @Stijn nouvaea is not supported, but is there is a workaround > BUG397389 -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 405687] latte panels go haywire with display on the left
https://bugs.kde.org/show_bug.cgi?id=405687 Michail Vourlakos changed: What|Removed |Added Latest Commit|https://commits.kde.org/lat |https://commits.kde.org/lat |te-dock/d8c04e805c3cf218436 |te-dock/b9aabb7b1c927320f34 |8cf8d915cd8a4af252fd2 |b5220d336e53de99a585b --- Comment #32 from Michail Vourlakos --- Git commit b9aabb7b1c927320f34b5220d336e53de99a585b by Michail Vourlakos. Committed on 22/03/2019 at 19:34. Pushed by mvourlakos into branch 'v0.8'. multi-screen: find view::screen id in better way --when monitor from an explicit screen was closed there were cases that docks were moved at another monitor from the window manager and that was preventing them to be delete properly. This patch fixes this by considering as valid explicit screen only the one provided by the view M +24 -6app/layout.cpp https://commits.kde.org/latte-dock/b9aabb7b1c927320f34b5220d336e53de99a585b -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 391293] Frequent Crashing On Start
https://bugs.kde.org/show_bug.cgi?id=391293 David Rosca changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from David Rosca --- The original reported issue was Flatpak specific and should be fixed in latest builds. -- You are receiving this mail because: You are watching all bug changes.
[knights] [Bug 405763] New: Segfault on 19.03.80
https://bugs.kde.org/show_bug.cgi?id=405763 Bug ID: 405763 Summary: Segfault on 19.03.80 Product: knights Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.se...@web.de Reporter: limburg...@gmail.com CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[knights] [Bug 405763] Segfault on 19.03.80
https://bugs.kde.org/show_bug.cgi?id=405763 --- Comment #1 from Gwyn Ciesla --- Created attachment 118978 --> https://bugs.kde.org/attachment.cgi?id=118978&action=edit Backtrace -- You are receiving this mail because: You are watching all bug changes.
[knights] [Bug 405763] Segfault on 19.03.80
https://bugs.kde.org/show_bug.cgi?id=405763 --- Comment #2 from Gwyn Ciesla --- Open. New. Choose Randomly (Black or White) Ok. segfault. On Fedora 29. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 404858] "Add Network Folder" tooltip icon does not show on Breeze, shows correctly on Breeze Dark
https://bugs.kde.org/show_bug.cgi?id=404858 --- Comment #14 from Patrick Silva --- Is this fix already available on neon dev unstable? Bug persists on such distribution. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386104] [Security] Integrate trash in the vault concept
https://bugs.kde.org/show_bug.cgi?id=386104 Ivan Čukić changed: What|Removed |Added Ever confirmed|0 |1 Assignee|ivan.cu...@kde.org |k...@davidedmundson.co.uk Status|REPORTED|ASSIGNED --- Comment #1 from Ivan Čukić --- Assigned and investigated. Almost fixed :) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405764] New: Albums disappear when "sshfs - transport endpoint is not connected".
https://bugs.kde.org/show_bug.cgi?id=405764 Bug ID: 405764 Summary: Albums disappear when "sshfs - transport endpoint is not connected". Product: digikam Version: 6.1.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Database-Albums Assignee: digikam-bugs-n...@kde.org Reporter: iwannaber...@gmail.com Target Milestone: --- SUMMARY This bug is related to bug #377849, which was been dealt with, but it only happens in one specific situation. I don't think it's Digikam's fault, but maybe something could be done to avoid losing a whole collection in the db. When a network share (containing the pictures) is connected through a sshfs mount, and the connection is lost at some point, the operating system sometimes is not aware of it. When you try to access that folder in a file browser, error messages similar to "sshfs - transport endpoint is not connected" are shown. Unmounting and mounting the network share usually solves the problem. Digikam (and any other software) also thinks that network share is still connected and accessible, so when it scans for new items, it sees that the path is still available (but it's not). However, it cannot access any of the pictures, so it decides to remove all the pictures in that collection, one by one. I found that the hard way the other day, when I found my database was empty due to that network error. This is likely a Linux-only problem, and the error should be corrected at the level of the OS (better detection of disconnected network folders), but maybe some mechanism could be implemented in Digikam to minimize situations like this. Like asking for a confirmation after several folders in a row couldn't be found, or just hiding but not deleting the files from the database, so they don't need to be rescanned the next time they are available. I don't know. STEPS TO REPRODUCE 1. Wait for a network interruption to "freeze" a sshfs mount point without unmounting it. 2. Tell digikam to scan for new folders/albums. OBSERVED RESULT Observe how the scan goes faster than usual, and at the end all albums have been removed from the database. EXPECTED RESULT Nothing should happen, as the picture library is not really available. Maybe mark those pictures as "not available". SOFTWARE/OS VERSIONS Ubuntu 18.04 and digikam-6.1.0-git-20190320T143140-x86-64.appimage ADDITIONAL INFORMATION I mount my network shares using the software called "autofs". -- You are receiving this mail because: You are watching all bug changes.
