[gwenview] [Bug 431321] New: Gwenview transparent content area in wayland session
https://bugs.kde.org/show_bug.cgi?id=431321 Bug ID: 431321 Summary: Gwenview transparent content area in wayland session Product: gwenview Version: 20.12.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: vlzvo...@ya.ru Target Milestone: --- Created attachment 134664 --> https://bugs.kde.org/attachment.cgi?id=134664&action=edit Bug example screenshot SUMMARY Transparent content area in wayland session. STEPS TO REPRODUCE 1. Login into plasma wayland session 2. Open any image with gwenview OBSERVED RESULT Content area of gwenview is transparent (shows the background located under the gwenview window) EXPECTED RESULT Show image in content area SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro 20.2.1 KDE KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION GPU: Intel HD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 431321] Gwenview transparent content area in wayland session
https://bugs.kde.org/show_bug.cgi?id=431321 Harry changed: What|Removed |Added Platform|Other |Manjaro -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 431321] Gwenview transparent content area in wayland session
https://bugs.kde.org/show_bug.cgi?id=431321 --- Comment #2 from Harry --- (In reply to Justin Zobel from comment #1) > I'm unable to reproduce this issue on 20.12.0 on my wayland laptop. > > Can you try in a new user to see if it is configuration file related? > > Also what settings are you using in Display and Monitor > Compositor? Indeed, the problem was resolved after creating a new user. So the problem was in the outdated configuration. Thanks, and I apologize for the issue. My compositor configuration is: - Scale method: Smooth - Rendering backend: OpenGL 3.1 - Tearing prevention: Automatic - Keep window thumbnails: Only for shown windows -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 426381] New: Can't login to google account
https://bugs.kde.org/show_bug.cgi?id=426381 Bug ID: 426381 Summary: Can't login to google account Product: KAccounts Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ad...@leinir.dk Reporter: myownmai...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Try to login to Google Account OBSERVED RESULT Blank window EXPECTED RESULT Logged in 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.
[KAccounts] [Bug 426381] Can't login to google account
https://bugs.kde.org/show_bug.cgi?id=426381 Harry changed: What|Removed |Added CC||myownmai...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433489] New: Memory leak in plasmashell when switching desktop
https://bugs.kde.org/show_bug.cgi?id=433489 Bug ID: 433489 Summary: Memory leak in plasmashell when switching desktop Product: plasmashell Version: 5.20.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: notm...@gmail.com Reporter: vlzvo...@ya.ru CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I have been experiencing this for a long time. I think about a year for sure. For a work session of 12 hours, plasmashell memory consumption can grow from ~100Mb to ~1GB. Memory consumption increases irrevocably when switching virtual desktops. Approximately 300-400Kb at a time. In the process of research I came across these closed reports with the same problem: - https://bugs.kde.org/show_bug.cgi?id=391063 - https://bugs.kde.org/show_bug.cgi?id=368838 but researching it didn't help me a lot. I have experienced this on at least two different machines. Also on different KDE desktop configurations, including on a fresh kde config for new user. I have already tried removing the system monitoring applets. It didn't help. STEPS TO REPRODUCE Switch between virtual desktop with opened windows on them should be enough. OBSERVED RESULT Memory usage of plasmashell process continuously increases EXPECTED RESULT Stable memory usage of plasmashell SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro 20.2.1 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.15-1 MANJARO ADDITIONAL INFORMATION GPU: Intel HD Graphics 620 Video with the bug: https://youtu.be/MrVhHLO14u8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433489] Memory leak in plasmashell when switching desktop
https://bugs.kde.org/show_bug.cgi?id=433489 --- Comment #2 from Harry --- Sorry for the late answer. Wallpaper settings: Layout: Folder view Wallpaper type: Image Positioning: Scaled and Cropped Plasmoids and customized panels: On the standard panel, i have some plasmoids: - Window buttons 0.8.1-2 https://github.com/psifidotos/applet-window-buttons - Window title 0.6.0-1 https://github.com/psifidotos/applet-window-title - Window app menu 0.6.0 https://github.com/psifidotos/applet-window-appmenu - System Load Viewer 0.8 (default) In the process of research the problem I tried to disable applets one by one from the list above, but ram consumption was still growing. Also default KDE plasmoids I use: - System tray - Digital clock Additional Panel is Latte Dock with just icons. Reproduce circumstances: It's truly hard to predict, when the problem actually appears. It happens, the problem appears just from system start. Sometimes after a while, but I can't tell you what trigger actually is. If I can do something to investigate it myself, I will, just show me the direction. Thanks for the quick reply. Sincerely. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433489] Memory leak in plasmashell when switching desktop
https://bugs.kde.org/show_bug.cgi?id=433489 --- Comment #4 from Harry --- Window buttons (https://github.com/psifidotos/applet-window-buttons) widget triggers this situation too. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433489] Memory leak in plasmashell when switching desktop
https://bugs.kde.org/show_bug.cgi?id=433489 --- Comment #3 from Harry --- Today I got an update, and now KDE version is 5.21.1 and it just got worse. Now memory usage is growing at minimize/maximize action. I've spend about 2 hours to investigate this situation, and now I'm about to sure, that the problem is in Global Menu widget. I've repeat the experiment with removing widgets one by one, and noticed that memory usage stops growing after I: 1. Remove global menu widget from panel 2. Close "Widget removed" notification It seems to me that notification is the key, why previous attempts was not successful. The experiment above I did and with standard "Global Menu" applet (it requires to add menu button to window title bar) and with third-party "Window app menu". Both has the same result, as described above. This is very frustrating for me. Global menu is my favorite widget (in related with the two others), I don't want to give it up. So for now I have no idea how it possible to bypass the situation, and just use plasmashell --replace & sudo swapoff -a && sudo swapon -a when memory consumption is too high. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433489] Memory leak in plasmashell when switching desktop
https://bugs.kde.org/show_bug.cgi?id=433489 Harry changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419135] On the fonts settings page, the Apply button is enabled, even if there were no changes
https://bugs.kde.org/show_bug.cgi?id=419135 Harry changed: What|Removed |Added CC||signa...@gmail.com --- Comment #3 from Harry --- Additional observations: This is occurs after you change any of the default fonts. Also I see in the system log when you navigate away from this setting page: Warning org.kde.fontinst Connecting to session bus Failed to register service! If you hit the defaults button at the bottom of the page, you would think this would go away after it resets the fonts to all the defaults. It does not, the issue persists. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 497485] Kdenlive crash ever in Windows 11
https://bugs.kde.org/show_bug.cgi?id=497485 --- Comment #6 from Harry --- That is possible, but every shot is made with the same settings.website https://dvnet.nl <https://digitalvisuals.nl> - @digitalvisuals op mastodon.nl -- Verzonden met Tuta, veel plezier met beveiligde en advertentievrije emails: 16 dec 2024, 17:58 van bugzilla_nore...@kde.org: > https://bugs.kde.org/show_bug.cgi?id=497485 > > Bernd changed: > > What|Removed |Added > > CC||bern...@yahoo.com > > --- Comment #5 from Bernd --- > Do any of the cource clips/files have a variable frame rate? > > -- > You are receiving this mail because: > You are on the CC list for the bug. > -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 497485] Kdenlive crash ever in Windows 11
https://bugs.kde.org/show_bug.cgi?id=497485 Harry changed: What|Removed |Added CC||digitalvisu...@tuta.com --- Comment #4 from Harry --- Well I had the same problems, its not possible to get a project finished, programm close without any error. If you start again and choose recover its close almost direcly again. The only thing you can do to start completly clean. But mostley after some time it closed again. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 497485] Kdenlive crash ever in Windows 11
https://bugs.kde.org/show_bug.cgi?id=497485 --- Comment #8 from Harry --- Thanks for answering, but I have changed to a another editor after these crashes., because I had a timeline. This editor was working very well with Win11 latest updates. Greetz. DigitalVisualswebsite https://dvnet.nl <https://digitalvisuals.nl> - @digitalvisuals op mastodon.nl -- Verzonden met Tuta, veel plezier met beveiligde en advertentievrije emails: 1 jan 2025, 21:56 van bugzilla_nore...@kde.org: > https://bugs.kde.org/show_bug.cgi?id=497485 > > emohr changed: > > What|Removed |Added > > Keywords||triaged > Priority|NOR |HI > Severity|critical|normal > CC||fritzib...@gmx.net > > --- Comment #7 from emohr --- > I imported the same Kdenlive project file twice (project file size 825KB). The > Job for converting started. Afterwards I pulled both project into the > timeline. > No crash. > > Does your project contain any special clips or effects? > > Can you upload here such a MLT or project file which crash on your side? > > -- > You are receiving this mail because: > You are on the CC list for the bug. > -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 462046] `Segmentation fault` when launching `dolphin --split` with more than two arguments
https://bugs.kde.org/show_bug.cgi?id=462046 Harry K changed: What|Removed |Added CC||hkco...@use.startmail.com --- Comment #1 from Harry K --- Created attachment 158483 --> https://bugs.kde.org/attachment.cgi?id=158483&action=edit kcrash file of the error This kcrash error is from Dolphin 23.03.00 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 462046] `Segmentation fault` when launching `dolphin --split` with more than two arguments
https://bugs.kde.org/show_bug.cgi?id=462046 --- Comment #2 from Harry K --- Forgot to add, the error happens intermittently. I've reproduced it in both Dolphin versions 23.03.00 and 23.07.70 (latest build). Haven't figured out how to reproduce every time. When dolphin works, it works by creating a split of the two folders and opening a separate tab for the third. -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 469105] New: Segmentation fault when quitting from the system tray.
https://bugs.kde.org/show_bug.cgi?id=469105 Bug ID: 469105 Summary: Segmentation fault when quitting from the system tray. Classification: Applications Product: juk Version: 23.04.0 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: whee...@kde.org Reporter: hkco...@use.startmail.com CC: mp...@kde.org Target Milestone: --- Application: juk (23.04.0) Qt Version: 5.15.9 Frameworks Version: 5.105.0 Operating System: Linux 6.2.12-1-default x86_64 Windowing System: X11 Distribution: openSUSE Tumbleweed DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: Juk crashed with a segmentation fault when I right clicked-> quit from the tray. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: JuK (juk), signal: Segmentation fault [KCrash Handler] #4 0x001e in () #5 0x559fd57dffd9 in PlaylistSearch::matchedItems() const (this=0x559fd7df3ec0) at /usr/src/debug/juk-23.04.0/playlistsearch.cpp:62 #6 0x559fd57e64bf in SearchPlaylist::updateItems() (this=0x559fd7be8230) at /usr/src/debug/juk-23.04.0/searchplaylist.cpp:63 #7 0x559fd57e66f5 in SearchPlaylist::~SearchPlaylist() (this=0x559fd7be8230, this=) at /usr/src/debug/juk-23.04.0/searchplaylist.cpp:43 #8 SearchPlaylist::~SearchPlaylist() (this=0x559fd7be8230, this=) at /usr/src/debug/juk-23.04.0/searchplaylist.cpp:44 #9 0x7f6657d167ee in QObjectPrivate::deleteChildren() (this=this@entry=0x559fd748b600) at kernel/qobject.cpp:2137 #10 0x7f66589e26b6 in QWidget::~QWidget() (this=0x559fd7662340, __in_chrg=) at kernel/qwidget.cpp:1524 #11 0x7f6658b59ad9 in QStackedWidget::~QStackedWidget() (this=0x559fd7662340, __in_chrg=) at widgets/qstackedwidget.cpp:147 #12 0x7f6657d167ee in QObjectPrivate::deleteChildren() (this=this@entry=0x559fd75f1b50) at kernel/qobject.cpp:2137 #13 0x7f66589e26b6 in QWidget::~QWidget() (this=0x559fd7661b10, __in_chrg=) at kernel/qwidget.cpp:1524 #14 0x7f66589e29e9 in QWidget::~QWidget() (this=0x559fd7661b10, __in_chrg=) at kernel/qwidget.cpp:1548 #15 0x7f6657d167ee in QObjectPrivate::deleteChildren() (this=this@entry=0x559fd76600e0) at kernel/qobject.cpp:2137 #16 0x7f66589e26b6 in QWidget::~QWidget() (this=0x559fd7660770, __in_chrg=) at kernel/qwidget.cpp:1524 #17 0x7f6658b54da9 in QSplitter::~QSplitter() (this=0x559fd7660770, __in_chrg=) at widgets/qsplitter.cpp:979 #18 0x7f6657d167ee in QObjectPrivate::deleteChildren() (this=this@entry=0x559fd71c3890) at kernel/qobject.cpp:2137 #19 0x7f66589e26b6 in QWidget::~QWidget() (this=0x559fd765e040, __in_chrg=) at kernel/qwidget.cpp:1524 #20 0x559fd57b17ac in PlaylistSplitter::~PlaylistSplitter() (this=0x559fd765e040, this=) at /usr/src/debug/juk-23.04.0/playlistsplitter.cpp:65 #21 JuK::slotQuit() (this=0x559fd6f9deb0) at /usr/src/debug/juk-23.04.0/juk.cpp:586 #22 0x7f6657d25232 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffe1d4bbd70, r=0x559fd6f9deb0, this=0x559fd787b3f0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #23 doActivate(QObject*, int, void**) (sender=0x559fd786c160, signal_index=4, argv=0x7ffe1d4bbd70) at kernel/qobject.cpp:3923 #24 0x7f6657d1de2f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x559fd786c160, m=m@entry=0x7f6658ebad20, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffe1d4bbd70) at kernel/qobject.cpp:3983 #25 0x7f665899e8c2 in QAction::triggered(bool) (this=this@entry=0x559fd786c160, _t1=) at .moc/moc_qaction.cpp:376 #26 0x7f66589a143f in QAction::activate(QAction::ActionEvent) (this=0x559fd786c160, event=) at kernel/qaction.cpp:1161 #27 0x7f6657d18c50 in QObject::event(QEvent*) (this=0x559fd786c160, e=0x7f660038f300) at kernel/qobject.cpp:1347 #28 0x7f66589a51ae in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x559fd786c160, e=0x7f660038f300) at kernel/qapplication.cpp:3640 #29 0x7f6657cec978 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x559fd786c160, event=0x7f660038f300) at kernel/qcoreapplication.cpp:1064 #30 0x7f6657ceff71 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x559fd6e29f50) at kernel/qcoreapplication.cpp:1821 #31 0x7f6657d46713 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x559fd6f0a640) at kernel/qeventdispatcher_glib.cpp:277 #32 0x7f6655f168d8 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #33 0x7f6655f16ce8 in () at /lib64/libglib-2.0.so.0 #34 0x7f6655f16d7c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #35 0x7f6657d45f26 in QEventDispatcherGlib::processEvents(QFlags) (this=0x559fd6f18810, flags=...) at kernel
[kasts] [Bug 468686] Feature request: adjustable seek times in Kasts
https://bugs.kde.org/show_bug.cgi?id=468686 Harry K changed: What|Removed |Added CC||hkco...@use.startmail.com -- You are receiving this mail because: You are watching all bug changes.
[Arianna] [Bug 469127] EPUB's do not open without Internet connection
https://bugs.kde.org/show_bug.cgi?id=469127 Harry K changed: What|Removed |Added CC||hkco...@use.startmail.com --- Comment #2 from Harry K --- Could not reproduce in latest build of Arianna. Epubs opened ok with or without internet connection. -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 466792] Ability to hide Played Episodes by default in most lists
https://bugs.kde.org/show_bug.cgi?id=466792 Harry K changed: What|Removed |Added CC||hkco...@use.startmail.com --- Comment #1 from Harry K --- Created attachment 158863 --> https://bugs.kde.org/attachment.cgi?id=158863&action=edit Filter option within search The filter option under "Search and Filter" achieves the desired functionality if we select "Unplayed Episodes". Maybe making the filter permanent via options would be a possible solution. If we were to go this way, we would need to alter the user interface to indicate that filters are active while viewing the episode list. -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 459885] Subscriptions section always shows numbers on the podcasts
https://bugs.kde.org/show_bug.cgi?id=459885 Harry K changed: What|Removed |Added CC||hkco...@use.startmail.com --- Comment #5 from Harry K --- I do agree with tobias that it's a bit confusing. I, too, had the impression that the number indicated new episodes. I speculate the reasons for the confusion are the following: 1. When a podcast refreshes and the number changes, that change indicates that new things have been added. The number in this case is not as important. If only an icon appeared with no numbers then - I think - most people would understand this as an addition of something new. 2. The blue background on the number indicator matches the "NEW" word on the episode list. Personally, it makes me perceive these items linked. Hope this perspective helps. Regarding a potential change, my suggestion is another layer/icon that says "NEW EPISODES" or something to that effect. This would not alienate current users who might already understand the current behaviour. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 460130] New: Crash on account creation wizard
https://bugs.kde.org/show_bug.cgi?id=460130 Bug ID: 460130 Summary: Crash on account creation wizard Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Account Wizard Assignee: kdepim-b...@kde.org Reporter: dn.al...@tuta.io Target Milestone: --- Application: accountwizard (0.2) Qt Version: 5.15.6 Frameworks Version: 5.98.0 Operating System: Linux 5.19.13-200.fc36.x86_64 x86_64 Windowing System: X11 Distribution: Fedora Linux 36 (Workstation Edition) DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: After entering the basic information into the account creation wizard (name, email address, etc.) and clicking the 'Next' button, the wizard just crashes. This happens no matter the state of the automatically find settings checkbox. The crash can be reproduced every time. -- Backtrace: Application: Account Assistant (accountwizard), signal: Segmentation fault [KCrash Handler] #4 0x555faf61ce4f in CryptoPage::enterPageNext() () #5 0x555faf61ffc0 in Dialog::slotNextOk() () #6 0x7fb80896c9a6 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #7 0x555faf61c520 in Dialog::next() () #8 0x7fb80896c9a6 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #9 0x7fb8094ea1c6 in QAbstractButton::clicked(bool) () at /lib64/libQt5Widgets.so.5 #10 0x7fb8094ea43e in QAbstractButtonPrivate::emitClicked() () at /lib64/libQt5Widgets.so.5 #11 0x7fb8094ec3f9 in QAbstractButton::click() () at /lib64/libQt5Widgets.so.5 #12 0x7fb80960619c in QDialog::keyPressEvent(QKeyEvent*) () at /lib64/libQt5Widgets.so.5 #13 0x7fb809439610 in QWidget::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #14 0x7fb8093f5d02 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #15 0x7fb8093fdcf7 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #16 0x7fb8089391c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #17 0x7fb809454f72 in QWidgetWindow::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #18 0x7fb8093f5d02 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #19 0x7fb8089391c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #20 0x7fb808d734fd in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () at /lib64/libQt5Gui.so.5 #21 0x7fb808d5602c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /lib64/libQt5Gui.so.5 #22 0x7fb7f4c2e8be in xcbSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5XcbQpa.so.5 #23 0x7fb8055cbfaf in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #24 0x7fb8056212c8 in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0 #25 0x7fb8055c9940 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #26 0x7fb80898a02a in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #27 0x7fb808937c1a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #28 0x7fb80893fce2 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #29 0x555faf60f447 in main () [Inferior 1 (process 4) detached] The reporter indicates this bug may be a duplicate of or related to bug 459308, bug 459236. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457041] Can't save Wireguard VPN settings
https://bugs.kde.org/show_bug.cgi?id=457041 Harry Phillips changed: What|Removed |Added CC||harryjamesphill...@gmail.co ||m --- Comment #7 from Harry Phillips --- This has been an issue for a while now so I thought I'd dig a little deeper - especially since this only happens on some of my WireGuard connections. This is the in all of my WireGuard connections that I can't modify using the GUI: [ipv6] address1=bla::bla/128 method=manual And this is in all of the configurations where I can: [ipv6] method=disabled So, disabling IPv6 for the connection and reloading NetworkManager causes the bug to disappear and the apply button works. The bug seems related to IPv6 settings. I hope this helps with solving the issue! -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 452489] New: What Is The Right Way To Leverage Cash App Direct Deposit Facility?
https://bugs.kde.org/show_bug.cgi?id=452489 Bug ID: 452489 Summary: What Is The Right Way To Leverage Cash App Direct Deposit Facility? Product: Akonadi Version: GIT (master) Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Contacts resource Assignee: kdepim-b...@kde.org Reporter: starkharry...@gmail.com Target Milestone: --- If you are one of those users who are looking to enable Cash App Direct Deposit, you must be a verified Cash App account holder. After that, you need to find out the bank name, routing number, and account number. By providing details, you will be able to get the direct deposit feature enabled on your account. https://www.digitalworldsupport.com/what-is-cash-app-bank-name-for-direct-deposit -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 452489] What Is The Right Way To Leverage Cash App Direct Deposit Facility?
https://bugs.kde.org/show_bug.cgi?id=452489 Harry Stark changed: What|Removed |Added URL||https://www.digitalworldsup ||port.com/what-is-cash-app-b ||ank-name-for-direct-deposit -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427861] Sometimes desktop loses its settings (wallpaper, widgets, icons settings) after re-login
https://bugs.kde.org/show_bug.cgi?id=427861 Harry Coin changed: What|Removed |Added CC||hgc...@gmail.com --- Comment #99 from Harry Coin --- Well, "Me too". Latest Ubuntu LTS, fresh install: custom image wallpaper reverts to default on one to two of 6 attached monitors, and usually not the 'primary' one after screen lock or reboot. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 443398] New: Spectacle exits without taking screenshot, upon-relaunch is in 'select rectangle' mode.
https://bugs.kde.org/show_bug.cgi?id=443398 Bug ID: 443398 Summary: Spectacle exits without taking screenshot, upon-relaunch is in 'select rectangle' mode. Product: Spectacle Version: 20.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: hgc...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY The spectacle app disappears from the screen as if it was never run just after the 'take a new screenshot' button is pressed, and 'rectangular region' was the mode. Then, when the spectacle app is re-launched, the screen goes into the mode of choosing a region (the app box itself does not appear). After a region is chosen normally, the menu box appears and operations are typical. STEPS TO REPRODUCE 1. Launch the app, specify a rectangular region. Choose take a screenshot 2. See the app disappear as if it was never launched at all. Totally normal appearance. 3. Launch the app again, the screen goes into 'select rectangle' mode and when selected normal spectacle ops continue. OBSERVED RESULT As above. The only difference I can think of is I have a multimonitor setup. EXPECTED RESULT SOFTWARE/OS VERSIONS Latest Ubuntu 'hirsute', all updates applied. 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.
[Spectacle] [Bug 443398] Spectacle exits without taking screenshot, upon-relaunch is in 'select rectangle' mode.
https://bugs.kde.org/show_bug.cgi?id=443398 --- Comment #2 from Harry Coin --- administrator@ceo1homenx:/tmp$ export $(dbus-launch) administrator@ceo1homenx:/tmp$ spectacle QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-administrator' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-administrator' QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.1' ... dialog appears, hangs after asking for a screenshot ^C administrator@ceo1homenx:/tmp$ spectacle QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-administrator' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-administrator' dialog does not appear ^C Sometimes the dialog appears, sometimes not. From the command line, it always hangs. From the launcher, the second run allows taking a screenshot. -- You are receiving this mail because: You are watching all bug changes.
[bomber] [Bug 443627] New: Will Cash App Refund Money If Scammed? What are tips for solutions?
https://bugs.kde.org/show_bug.cgi?id=443627 Bug ID: 443627 Summary: Will Cash App Refund Money If Scammed? What are tips for solutions? Product: bomber Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: harryporter2...@gmail.com CC: kde-games-b...@kde.org Target Milestone: --- People using the Cash app are struggling with queries such as Will Cash App Refund Money If Scammed. They should be attentive if any unknown Element approaches them and instructs them to invest in profits. Cash app never Suggests their users for such aspect, so before, taking any action, they must Once contact the cash app service team to find out the facts. https://www.contactmail-support.com/blog/will-cash-app-refund-money-if-scammed/ -- You are receiving this mail because: You are watching all bug changes.
[kmailtransport] [Bug 435354] Sending SMTP mail doesn't work
https://bugs.kde.org/show_bug.cgi?id=435354 Harry Sinclair changed: What|Removed |Added CC||shadw...@hls3.com --- Comment #2 from Harry Sinclair --- I am experiencing the same issue on Ubuntu 21.04 with KMAIL 20.12.3. The SMTP commands never attempt to authenticate after the ELHO and STARTTLS commands. Here is the ksmtp log file output. - S: 220 mail2.domain.com ESMTP Postfix C: EHLO pop-os.localnet S: 250-mail2.domain.com S: 250-PIPELINING S: 250-SIZE 15728640 S: 250-ETRN S: 250-STARTTLS S: 250-ENHANCEDSTATUSCODES S: 250-8BITMIME S: 250-DSN S: 250 SMTPUTF8 C: STARTTLS S: 220 2.0.0 Ready to start TLS C: EHLO pop-os.localnet S: 250-mail2.domain.com S: 250-PIPELINING S: 250-SIZE 15728640 S: 250-ETRN S: 250-AUTH PLAIN LOGIN S: 250-ENHANCEDSTATUSCODES S: 250-8BITMIME S: 250-DSN S: 250 SMTPUTF8 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 439572] New: Yakuake "Keep Window Open when it loses focus" pref deselection ignored in Wayland
https://bugs.kde.org/show_bug.cgi?id=439572 Bug ID: 439572 Summary: Yakuake "Keep Window Open when it loses focus" pref deselection ignored in Wayland Product: yakuake Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: h...@kde.org Reporter: ha...@lansmart.com Target Milestone: --- SUMMARY Using Yakuake 21.04.2 on Manjaro, Plasma 5.22.2 the "Keep window open when it loses focus" preference is ignored when deselected or the "pin" unstuck. When losing focus the Yakuake window remains open...it worked perfectly until I switched to Wayland STEPS TO REPRODUCE 1. Open Yakuake in a Wayland session 2. deselect the preference to "keep window open when it loses focus" 3. click on another app or background so Yakuake session loses focus (it does not close in my case) OBSERVED RESULT Yakuake session does not close when losing focus even if pref "keep window open when it loses focus" is deselected. EXPECTED RESULT Yakuake window to close when it loses focus SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.13.0-1-MANJARO-ARM (64bit) (available in About System) KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Using Wayland, worked properly in X ARM Processor 64bit, PineBook Pro Laptop Similar or same to bug 386358 but the opposite in my case, probably because I had this pref enabled when I switched to wayland...and now cannot change the behavior with prefs deselection. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444493] Wallpaper dissappears after restarting my machine
https://bugs.kde.org/show_bug.cgi?id=93 Harry Coin changed: What|Removed |Added CC||hgc...@gmail.com --- Comment #8 from Harry Coin --- This happens to me as well. I have a multimonitor setup. Every reboot it's anyone's bet whether the "Darkest Hour" image will be restored (as set on each monitor), or whether the monitor will be entirely black. Of some interest, when I launch "desktop folder settings -- Plasma" even on the monitors where the image is correct, you'd expect when I choose the current image the apply button would remain greyed out. It does not, it pops active even though the image I chose matched the one on the monitor already. Go figure. I can reset the background on each monitor, and it will remain until the next poweroff/reboot. Then, at least 2 monitors will be black. Which two seems to vary. Latest jammy, no pending updates as of 12/23/22. -- You are receiving this mail because: You are watching all bug changes.
[kig] [Bug 446714] New: Curiosity TV is a video streaming app offering entire episodes and short videos of TV shows, never-before-seen exclusive specials, award-winning documentaries, and thousands of
https://bugs.kde.org/show_bug.cgi?id=446714 Bug ID: 446714 Summary: Curiosity TV is a video streaming app offering entire episodes and short videos of TV shows, never-before-seen exclusive specials, award-winning documentaries, and thousands of short videos only on curiosity.tv/activate. Product: kig Version: 20.03.80 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: david.narv...@computer.org Reporter: harrydalfio...@gmail.com Target Milestone: --- Curiosity TV is a video streaming app offering entire episodes and short videos of TV shows, never-before-seen exclusive specials, award-winning documentaries, and thousands of short videos only on curiosity.tv/activate. -- You are receiving this mail because: You are watching all bug changes.
[kig] [Bug 446714] Curiosity TV is a video streaming app offering entire episodes and short videos of TV shows, never-before-seen exclusive specials, award-winning documentaries, and thousands of shor
https://bugs.kde.org/show_bug.cgi?id=446714 Harry Dalfio changed: What|Removed |Added URL||https://www.gadgetswhy.com/ ||curiosity-tv-activate/ -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457041] Can't save Wireguard VPN settings
https://bugs.kde.org/show_bug.cgi?id=457041 --- Comment #9 from Harry Phillips --- (In reply to sashok.olen from comment #8) > Still an issue on Plasma 6.1.2 > I want to disable automatic connection to the VPN profile on startup, but > there's no way to do it, and I can't figure out how to disable it via nmcli > either. Slightly off topic, but in case anyone else runs into this exact scenario (common as auto-connect is on by default), the command is: nmcli con mod [connection_name] connection.autoconnect false -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 412834] New: "Cannot refresh cache whilst offline" -- except I'm online.
https://bugs.kde.org/show_bug.cgi?id=412834 Bug ID: 412834 Summary: "Cannot refresh cache whilst offline" -- except I'm online. Product: Discover Version: 5.16.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: hgc...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY "Cannot refresh cache whilst offline" -- except I'm not offline, obviously since I'm filing this report. STEPS TO REPRODUCE 1. Click the icon indicating updates are available in the task bar 2. Click 'check for updates'. 3. Notice it gives an error message and does nothing of any use. System is the latest Ubuntu 'eoan', though this bug has been around for a long time. My system's network is configured via systemd/networkd as is indicated in /etc/netplan. I don't use the network manager for anything. This bug appears whether the disused network-manager is enabled or disabled in systemd, or is running or not running. 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.
[kdeconnect] [Bug 413259] New: Files >=512MB (movies) corrupted during transfer without warning
https://bugs.kde.org/show_bug.cgi?id=413259 Bug ID: 413259 Summary: Files >=512MB (movies) corrupted during transfer without warning Product: kdeconnect Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: hgc...@gmail.com Target Milestone: --- SUMMARY Phone videos are silently corrupted during transfer. STEPS TO REPRODUCE 1. Take a phone video >= 512MB. 2. Connect via KDEConnect's android app, open dolphin, surf to DCIM directory, select all, copy. 3. Surf to local directly, paste. 4. Wait. Normal termination reported. OBSERVED RESULT Movie files (larger) correctly match size, dates, names. However, the content is quite wrong. Proven by removing the memory chip from the phone, copying via direct connection, then comparing the files. Latest ubuntu eoan kdeconnect 1.3.5-0ubuntu1 Android kdeconnect version 1.13.2, Samsung galaxy s8 / verizon. 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.
[kdeconnect] [Bug 413259] Files >=512MB (movies) corrupted during transfer without warning
https://bugs.kde.org/show_bug.cgi?id=413259 Harry Coin changed: What|Removed |Added Version|unspecified |1.3.5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407138] New: Waiting for process to complete lasts forever and prevents saving or editing, causing work to be lost
https://bugs.kde.org/show_bug.cgi?id=407138 Bug ID: 407138 Summary: Waiting for process to complete lasts forever and prevents saving or editing, causing work to be lost Product: krita Version: 4.1.7 Platform: Windows CE OS: Windows CE Status: REPORTED Severity: major Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: harryarth...@outlook.com Target Milestone: --- SUMMARY Occasionally Krita will be stuck on a process perpetually but forces me to wait for the process to complete before I can save or continue painting, resulting in forced closure and loss of autosaves and often loss of work. Seems to happen randomly and so I don't know how to reproduce it. 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.
[kdeconnect] [Bug 336043] SFTP: Should be able to browse external SD cards via SFTP too
https://bugs.kde.org/show_bug.cgi?id=336043 --- Comment #88 from Harry Coin --- Confirmed on the s8 . The only failure appears to be listing the root directory of the so card. On March 6, 2019 5:56:20 PM CST, Rafael Linux User wrote: >https://bugs.kde.org/show_bug.cgi?id=336043 > >--- Comment #87 from Rafael Linux User >--- >> I'll just make a test tonight about this theory. > >I test and confirmed that permission to access SD Card are granted for >KDE >Connect in my Galaxy S7, but as we all know, there is no any moment in >which >KDE Connect let user try to access to the SD Card (as I said, that's >the >difference with other apps). >I can confirm too something someone wrote here. Once you access to SD >Card from >Dolphin, if you modify the path and add a existent subfolder, you have >READ >access to that subfolder!! > >Example: >My SD Card path thru KDEConnect is: >/run/user/1000/3511dfbdef1892ed/storage/0411-AFE2/ > >I know that I have a subfolder called "Music", so I put: >/run/user/1000/3511dfbdef1892ed/storage/0411-AFE2/Music >and mysteriously, I have read access to that folder. > >-- >You are receiving this mail because: >You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 336043] SFTP: Should be able to browse external SD cards via SFTP too
https://bugs.kde.org/show_bug.cgi?id=336043 --- Comment #96 from Harry Coin --- When will it be out there for android updates to see it? On 3/8/19 11:35 AM, bugzilla_nore...@kde.org wrote: > https://bugs.kde.org/show_bug.cgi?id=336043 > > --- Comment #95 from ham...@laposte.net --- > Awesome ! I confirm, it works ! > Thanks much, we were waiting since a long time to see a fix :) > -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 367070] Crash when saving tabs as a bookmark after splitting konsole
https://bugs.kde.org/show_bug.cgi?id=367070 --- Comment #3 from Harry Rostovtsev --- This bug can be closed. I have attempted the steps again in Kubuntu 18.10 (Konsole version 18.04.3, KDE Plasma 5.13.5, Kde Frameworks 5.50.0 Qt 5.11.1) and the crash no longer happens. Sorry for the slow response rate. -- You are receiving this mail because: You are watching all bug changes.
[katomic] [Bug 366396] KAtomic crashes upon Shift-Tab key combo
https://bugs.kde.org/show_bug.cgi?id=366396 Harry Altman changed: What|Removed |Added CC||sniff...@gmail.com --- Comment #2 from Harry Altman --- I just wanted to say, I'm having this issue as well. katomic 4.0, Linux Mint 18.3. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 336043] SFTP: Should be able to browse external SD cards via SFTP too
https://bugs.kde.org/show_bug.cgi?id=336043 Harry Coin changed: What|Removed |Added CC||hgc...@gmail.com --- Comment #81 from Harry Coin --- Add HTC M8 to the list. user:/run/user/1000/93928376705e8277$ ls -l ls: reading directory '.': Operation not permitted total 0 user:cd /sdcard user:/run/user/1000/93928376705e8277/sdcard$ ls -l total 148 -rw-rw-rw- 1 administrator admin 72245 Aug 19 2017 _deleted.vcf drwxrwxrwx 1 administrator admin 0 Jun 30 2017 Alarms -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 401591] New: Dolphin crashed when looking in trash bucket.
https://bugs.kde.org/show_bug.cgi?id=401591 Bug ID: 401591 Summary: Dolphin crashed when looking in trash bucket. Product: dolphin Version: 18.04.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: hgc...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (18.04.3) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.18.0-11-generic x86_64 Distribution: Ubuntu 18.10 -- Information about the crash: - What I was doing when the application crashed: Previously I had chosen 'empty trash'. some minutes later, I looked in the bucket to see nothing had been deleted. I chose a folder at random asking it to delete that. Then in crashed. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f17288eb800 (LWP 6168))] Thread 6 (Thread 0x7f170fc45700 (LWP 8744)): #0 __GI___libc_read (fd=22, buf=0x7f170fc44bde, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7f172c7431f1 in pa_read () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-12.2.so #2 0x7f172e36bdbe in pa_mainloop_prepare () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f172e36c820 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f172e36c8e0 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f172e37a8f9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f172c7726f8 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-12.2.so #7 0x7f172e3bd164 in start_thread (arg=) at pthread_create.c:486 #8 0x7f1732297def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f171cac1700 (LWP 6173)): #0 0x7f173228b6d9 in __GI___poll (fds=0x7f17080049b0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f172d21ae46 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f172d21af6c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f17301c115b in QEventDispatcherGlib::processEvents (this=0x7f1708000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f173016e16b in QEventLoop::exec (this=this@entry=0x7f171cac0da0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f172ffbd0b6 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f172ffc6c87 in QThreadPrivate::start (arg=0x5610f3f822e0) at thread/qthread_unix.cpp:367 #7 0x7f172e3bd164 in start_thread (arg=) at pthread_create.c:486 #8 0x7f1732297def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f171ee20700 (LWP 6172)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5610f3dfd028) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5610f3dfcfd8, cond=0x5610f3dfd000) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5610f3dfd000, mutex=0x5610f3dfcfd8) at pthread_cond_wait.c:655 #3 0x7f171f5df75b in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #4 0x7f171f5df4c7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #5 0x7f172e3bd164 in start_thread (arg=) at pthread_create.c:486 #6 0x7f1732297def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f1725cb6700 (LWP 6171)): #0 0x7f173228b6d9 in __GI___poll (fds=0x7f171801b200, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f172d21ae46 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f172d21af6c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f17301c115b in QEventDispatcherGlib::processEvents (this=0x7f1718000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f173016e16b in QEventLoop::exec (this=this@entry=0x7f1725cb5d70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f172ffbd0b6 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f173047a545 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f172ffc6c87 in QThreadPrivate::start (arg=0x7f17304f4d60) at thread/qthread_unix.cpp:367 #8 0x7f172e3bd164 in start_thread (arg=) at pthread_create.c:486 #9 0x7f1732297def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f1726e5a700 (LWP 6169)): #0 0x7f173228b6d9 in __GI___poll (fds=0x7f1726e59cb8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #81 from Harry ten Berge --- Yes, confirmed that with '--notransparency' the artifacts are gone. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 387153] libinput-backend touchpad KCM only used on Wayland
https://bugs.kde.org/show_bug.cgi?id=387153 Harry ten Berge changed: What|Removed |Added CC|htenbe...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416358] kcm_fonts: Cannot apply changes (button remains inactive)
https://bugs.kde.org/show_bug.cgi?id=416358 Harry ten Berge changed: What|Removed |Added CC||htenbe...@gmail.com --- Comment #33 from Harry ten Berge --- Confirmed on OpenSUSE Tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 Harry ten Berge changed: What|Removed |Added CC|htenbe...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 Harry ten Berge changed: What|Removed |Added CC||htenbe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 387153] libinput-backend touchpad KCM only used on Wayland
https://bugs.kde.org/show_bug.cgi?id=387153 Harry ten Berge changed: What|Removed |Added CC||htenbe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 368597] New: Failed to switch to any Fcitx input methods
https://bugs.kde.org/show_bug.cgi?id=368597 Bug ID: 368597 Summary: Failed to switch to any Fcitx input methods Product: amarok Version: 2.8.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Collection Browser Assignee: amarok-bugs-d...@kde.org Reporter: harry...@gmail.com In this version, there is no way to switch to any Chinese input methods within Fcitx. Reproducible: Always Steps to Reproduce: 1.Ctrl+F to open search collection 2.Use whatever way to switch to another language input method in Fcitx 3.try typing (in my case Chinese pinyin) Actual Results: No input method is triggered. Stuck in English Expected Results: Type in Chinese The input method works fine everywhere but Amarok -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 367070] New: Crash when saving tabs as a bookmark after splitting konsole
https://bugs.kde.org/show_bug.cgi?id=367070 Bug ID: 367070 Summary: Crash when saving tabs as a bookmark after splitting konsole Product: konsole Version: 15.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: rost0...@gmail.com Application: konsole (15.12.3) Qt Version: 5.5.1 Frameworks Version: 5.23.0 Operating System: Linux 4.4.0-34-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: Split the screen in Konsole several times and tried to save all tabs as a bookmark. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #6 QBasicAtomicOps<4>::ref (_q_value=@0x20: ) at ../../include/QtCore/../../src/corelib/arch/qatomic_x86.h:181 #7 QBasicAtomicInteger::ref (this=0x20) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:127 #8 QIcon::QIcon (this=0x7ffdd4c81140, other=...) at image/qicon.cpp:630 #9 0x7fb54d34756d in Konsole::ViewProperties::icon() const () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.15 #10 0x7fb54d2b8bf9 in Konsole::BookmarkHandler::iconForView(Konsole::ViewProperties*) const () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.15 #11 0x7fb54d2b8f6e in Konsole::BookmarkHandler::currentBookmarkList() const () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.15 #12 0x7fb54979b5cf in KBookmarkMenu::slotAddBookmarksList() () from /usr/lib/x86_64-linux-gnu/libKF5Bookmarks.so.5 #13 0x7fb54a23ce4f in QtPrivate::QSlotObjectBase::call (a=0x7ffdd4c813f0, r=0x15d9af0, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #14 QMetaObject::activate (sender=sender@entry=0x159f8e0, signalOffset=, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffdd4c813f0) at kernel/qobject.cpp:3698 #15 0x7fb54a23d7d7 in QMetaObject::activate (sender=sender@entry=0x159f8e0, m=m@entry=0x7fb54b002f00 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffdd4c813f0) at kernel/qobject.cpp:3578 #16 0x7fb54aaf7412 in QAction::triggered (this=this@entry=0x159f8e0, _t1=false) at .moc/moc_qaction.cpp:365 #17 0x7fb54aaf9898 in QAction::activate (this=0x159f8e0, event=) at kernel/qaction.cpp:1162 #18 0x7fb54ac7be22 in QMenuPrivate::activateCausedStack (this=this@entry=0x15af640, causedStack=..., action=action@entry=0x159f8e0, action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at widgets/qmenu.cpp:1130 #19 0x7fb54ac820bc in QMenuPrivate::activateAction (this=this@entry=0x15af640, action=action@entry=0x159f8e0, action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at widgets/qmenu.cpp:1207 #20 0x7fb54ac86030 in QMenu::mouseReleaseEvent (this=, e=0x7ffdd4c81a30) at widgets/qmenu.cpp:2540 #21 0x7fb54ab43f88 in QWidget::event (this=this@entry=0x15a2d00, event=event@entry=0x7ffdd4c81a30) at kernel/qwidget.cpp:9044 #22 0x7fb54ac86a83 in QMenu::event (this=0x15a2d00, e=0x7ffdd4c81a30) at widgets/qmenu.cpp:2654 #23 0x7fb54ab0105c in QApplicationPrivate::notify_helper (this=this@entry=0x151c8e0, receiver=receiver@entry=0x15a2d00, e=e@entry=0x7ffdd4c81a30) at kernel/qapplication.cpp:3716 #24 0x7fb54ab06c19 in QApplication::notify (this=, receiver=0x15a2d00, e=0x7ffdd4c81a30) at kernel/qapplication.cpp:3276 #25 0x7fb54a20e62b in QCoreApplication::notifyInternal (this=0x7ffdd4c822f0, receiver=receiver@entry=0x15a2d00, event=event@entry=0x7ffdd4c81a30) at kernel/qcoreapplication.cpp:965 #26 0x7fb54ab05b32 in QCoreApplication::sendSpontaneousEvent (event=0x7ffdd4c81a30, receiver=0x15a2d00) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:227 #27 QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x15a2d00, event=event@entry=0x7ffdd4c81a30, alienWidget=alienWidget@entry=0x0, nativeWidget=0x15a2d00, buttonDown=buttonDown@entry=0x7fb54b031b20 , lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:2770 #28 0x7fb54ab5e8dd in QWidgetWindow::handleMouseEvent (this=this@entry=0x196b330, event=event@entry=0x7ffdd4c81e40) at kernel/qwidgetwindow.cpp:452 #29 0x7fb54ab60b3b in QWidgetWindow::event (this=0x196b330, event=0x7ffdd4c81e40) at kernel/qwidgetwindow.cpp:210 #30 0x7fb54ab0105c in QApplicationPrivate::notify_helper (this=this@entry=0x151c8e0, receiver=receiver@entry=0x196b330, e=e@entry=0x7ffdd4c81e40) at kernel/qapplication.cpp:3716 #31 0x7fb54ab06516 in QApplication::notify (this=0x7ffdd4c822f0, receiver=0x196b330, e=0x7ffdd4c81e40) at kernel/qapplication.cpp:3499 #32 0x7fb54a20e62b in QCoreApplication::notifyInternal (this=0x7ffdd4c822f0, receiver=receiver@entry=0x196b330, event=event@entry=0x7ffdd
[kmymoney4] [Bug 349033] option to invert transaction amounts during import
https://bugs.kde.org/show_bug.cgi?id=349033 harry bennett changed: What|Removed |Added CC||kdeb...@saltyshells.com --- Comment #2 from harry bennett --- Created attachment 99382 --> https://bugs.kde.org/attachment.cgi?id=99382&action=edit sample csv of how data is provided by credit card company -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 349033] option to invert transaction amounts during import
https://bugs.kde.org/show_bug.cgi?id=349033 --- Comment #5 from harry bennett --- No, I did nothing but edit for the foo/bar due to privacy concerns. I'll have to do an import to check. I'll get back to you. The OP is from a year ago, maybe it got fixed? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 342401] allow splits on payees
https://bugs.kde.org/show_bug.cgi?id=342401 --- Comment #1 from harry bennett --- a year has gone by and this is still "unconfirmed"? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 342401] allow splits on payees
https://bugs.kde.org/show_bug.cgi?id=342401 --- Comment #3 from harry bennett --- Jack, thanks for the reply. Totally understand the time thing. To All, Just to be clear I wasn't really expecting it to be fixed, I generally take "confirmed" as "someone read this" and hopefully, put it on the todo list. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 342401] allow splits on payees
https://bugs.kde.org/show_bug.cgi?id=342401 --- Comment #5 from harry bennett --- Sure. Christian hands me a check for services ($500). Jack hands me a check for services ($1000). Both of these checks may land into the same category (1099 income, in my case). I walk into the bank and make a single combined deposit for $1500. This is what my deposit receipt and bank statement will show, and also how I would enter it in my checkbook ledger (KMM). If I enter it as 2 separate transactions, It becomes correct from the payee perspective, but I lose transaction "correctness" in the checkbook ledger. Whereas if I were to leave the payee field blank, and enter the deposit as a split transaction, the entry in the bank ledger would simply read "split transaction" (and it does, by the way) showing the summed total of the splits (as any other split would do), but I would have payee fields where I could assign respective amounts. I am unfamiliar with "proper" bookkeeping/accounting procedures. I am just a lay person that is self-employed trying to keep his books straight. It just seemed logical to me that if we can have splits, we should be able to do this as well. This was discovered when I tried reconciling payees against 1099's. I had one that was $600 high and one $600 low. I came to realize that I "credited" an entire deposit to a single payee (having forgotten that the deposit was actually 2 checks). My next thought was "oh, I should split that". And now here I am. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 342401] allow different payees on splits
https://bugs.kde.org/show_bug.cgi?id=342401 harry bennett changed: What|Removed |Added Summary|allow splits on payees |allow different payees on ||splits -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 342401] allow different payees on splits
https://bugs.kde.org/show_bug.cgi?id=342401 --- Comment #6 from harry bennett --- FYI: I changed the heading on the bug to better reflect what I mean -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 342401] allow different payees on splits
https://bugs.kde.org/show_bug.cgi?id=342401 --- Comment #10 from harry bennett --- Are you implying that it may be as simple as just 'enabling' it? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 357954] Sometimes get "unlocking failed" error when using yubikey with static password
https://bugs.kde.org/show_bug.cgi?id=357954 Harry Henry Gebel changed: What|Removed |Added CC||hhge...@gmail.com --- Comment #6 from Harry Henry Gebel --- I have the same problem on Funtoo Linux. I also got it to work 100% by running the greeter by itself with the '---testing' parameter. I have been able to temporarily work around it by setting the Yubikey to output the password slower (20ms extra delay between keypresses) but it would be nice to have this fixed so I could use it at full speed. -- You are receiving this mail because: You are watching all bug changes.
