[kstars] [Bug 392807] New: Kstars crashes on Mac OSX on startup
https://bugs.kde.org/show_bug.cgi?id=392807 Bug ID: 392807 Summary: Kstars crashes on Mac OSX on startup Product: kstars Version: 2.9.3 Platform: Mac OS X Disk Images OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: guy.b.william...@gmail.com Target Milestone: --- Kstars was working fine until I added the Tycho2 star catalogue from the Data menu. Since then it crashes with 'Kstars quit unexpectedly'. I've uninstalled Kstars from Application folder, reinstalled and get the same error. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 408018] New: Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted
https://bugs.kde.org/show_bug.cgi?id=408018 Bug ID: 408018 Summary: Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted Product: frameworks-baloo Version: 5.58.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: guy.car...@gmail.com Target Milestone: --- SUMMARY every time I boot up my Fedora30 I'm getting an error that Baloo File Extractor Crashed STEPS TO REPRODUCE 1. boot up Fedora30 SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora30 KDE plasma (available in About System) KDE Plasma Version: plasm a-workspace-common-5.15.5-1.fc30.x86_64 KDE Frameworks Version: kde-settings-30.0-1.fc30.noarch Qt Version: qt5 ADDITIONAL INFORMATION Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f289c4bf800 (LWP 2472))] Thread 3 (Thread 0x7f288e9b6700 (LWP 2493)): #0 0x7f289e350dde in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #1 0x7f289e351270 in ?? () from /lib64/libglib-2.0.so.0 #2 0x7f289e351313 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f289f782413 in QEventDispatcherGlib::processEvents (this=0x7f288b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f289f72c2bb in QEventLoop::exec (this=this@entry=0x7f288e9b5d70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f289f585675 in QThread::exec (this=this@entry=0x7f28a074d060 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f28a06c9f4a in QDBusConnectionManager::run (this=0x7f28a074d060 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #7 0x7f289f5867c6 in QThreadPrivate::start (arg=0x7f28a074d060 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361 #8 0x7f289ec7f5a2 in start_thread () from /lib64/libpthread.so.0 #9 0x7f289f203163 in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f288f1cd700 (LWP 2488)): #0 0x7f289f1f83f7 in poll () from /lib64/libc.so.6 #1 0x7f289e2d738a in ?? () from /lib64/libxcb.so.1 #2 0x7f289e2d8ffa in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f288f3c8908 in QXcbEventQueue::run (this=0x55a0d4df65f0) at qxcbeventqueue.cpp:228 #4 0x7f289f5867c6 in QThreadPrivate::start (arg=0x55a0d4df65f0) at thread/qthread_unix.cpp:361 #5 0x7f289ec7f5a2 in start_thread () from /lib64/libpthread.so.0 #6 0x7f289f203163 in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f289c4bf800 (LWP 2472)): [KCrash Handler] #6 0x7f289f13feb5 in raise () from /lib64/libc.so.6 #7 0x7f289f12a895 in abort () from /lib64/libc.so.6 #8 0x7f289ee46ca3 in mdb_assert_fail (env=0x55a0d4f0b830, expr_txt=expr_txt@entry=0x7f289ee4902f "rc == 0", func=func@entry=0x7f289ee49978 <__func__.7120> "mdb_page_dirty", line=line@entry=2127, file=0x7f289ee49010 "mdb.c") at mdb.c:1542 #9 0x7f289ee3b9c5 in mdb_page_dirty (mp=, txn=0x55a0d4f0d3b0) at mdb.c:2114 #10 mdb_page_dirty (txn=0x55a0d4f0d3b0, mp=) at mdb.c:2114 #11 0x7f289ee3cc56 in mdb_page_alloc (num=num@entry=1, mp=mp@entry=0x7ffdf65aa558, mc=) at mdb.c:2308 #12 0x7f289ee3ce93 in mdb_page_touch (mc=mc@entry=0x7ffdf650) at mdb.c:2495 #13 0x7f289ee3ead7 in mdb_cursor_touch (mc=mc@entry=0x7ffdf650) at mdb.c:6523 #14 0x7f289ee41bed in mdb_cursor_put (mc=mc@entry=0x7ffdf650, key=key@entry=0x7ffdf65aae80, data=data@entry=0x7ffdf65aae90, flags=flags@entry=0) at mdb.c:6657 #15 0x7f289ee449f8 in mdb_put (txn=0x55a0d4f0d3b0, dbi=7, key=0x7ffdf65aae80, data=0x7ffdf65aae90, flags=0) at mdb.c:9022 #16 0x7f28a07873b8 in Baloo::IdTreeDB::put(unsigned long long, QVector) () from /lib64/libKF5BalooEngine.so.5 #17 0x7f28a07ac1d0 in Baloo::WriteTransaction::removeDocument(unsigned long long) () from /lib64/libKF5BalooEngine.so.5 #18 0x7f28a079e657 in Baloo::Transaction::removeDocument(unsigned long long) () from /lib64/libKF5BalooEngine.so.5 #19 0x55a0d3ef599a in Baloo::App::processNextFile (this=0x7ffdf65ab7e0) at /usr/src/debug/kf5-baloo-5.58.0-1.fc30.x86_64/src/file/extractor/app.cpp:106 #20 0x7f289f763dc6 in QtPrivate::QSlotObjectBase::call (a=0x7ffdf65ab1e0, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #21 QSingleShotTimer::timerEvent (this=0x55a0d5753220) at kernel/qtimer.cpp:318 #22 0x7f289f7583c5 in QObject::event (this=0x55a0d5753220, e=) at kernel/qobject.cpp:1282 #23 0x7f28a0086ad6 in QApplicationPrivate::notify_helper (this=this@entry=0x55a0d4dd6100,
[frameworks-kwayland] [Bug 373907] Implement Wayland Primary Selection Protocol (middle-click paste)
https://bugs.kde.org/show_bug.cgi?id=373907 guy changed: What|Removed |Added CC||guy.car...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 434892] konsole crash when open
https://bugs.kde.org/show_bug.cgi?id=434892 --- Comment #2 from guy --- Application: Konsole (konsole), signal: Aborted [KCrash Handler] #4 0x7f6766bdd292 in raise () from /lib64/libc.so.6 #5 0x7f6766bc68a4 in abort () from /lib64/libc.so.6 #6 0x7f6766a9ec78 in std::__replacement_assert (__file=, __line=, __function=, __condition=) at /usr/include/c++/11/x86_64-redhat-linux/bits/c++config.h:2648 #7 0x7f6766b4148f in std::piecewise_linear_distribution::param_type::_M_initialize (this=0x7ffeb57cf8d0) at /usr/include/c++/11/bits/random.tcc:3055 #8 0x7f6766b485af in std::piecewise_linear_distribution::piecewise_linear_distribution > (__fw=..., __bl=..., this=0x7ffeb57cf8d0) at /usr/include/c++/11/bits/random.h:5867 #9 Konsole::ColorScheme::colorEntry (this=0x7ffeb57cf8d0, index=, randomSeed=3044866064) at /usr/src/debug/konsole5-20.12.2-1.fc34.x86_64/src/colorscheme/ColorScheme.cpp:322 #10 0x7f6766afaa29 in Konsole::ColorScheme::getColorTable (randomSeed=9989121, table=0x7ffeb57d0d90, this=0x55ad84378d20) at /usr/src/debug/konsole5-20.12.2-1.fc34.x86_64/src/colorscheme/ColorScheme.cpp:339 #11 Konsole::TerminalDisplay::applyProfile (this=0x55ad84092220, profile=...) at /usr/src/debug/konsole5-20.12.2-1.fc34.x86_64/src/terminalDisplay/TerminalDisplay.cpp:3118 #12 0x7f6766ab233b in Konsole::ViewManager::applyProfileToView (this=0x55ad83ff1c90, view=0x55ad84092220, profile=...) at /usr/src/debug/konsole5-20.12.2-1.fc34.x86_64/src/ViewManager.cpp:832 #13 0x7f6766aba84b in Konsole::ViewManager::createView (this=0x55ad83ff1c90, session=session@entry=0x55ad83f80130) at /usr/src/debug/konsole5-20.12.2-1.fc34.x86_64/src/ViewManager.cpp:675 #14 0x7f676737982e in Konsole::MainWindow::createSession (this=this@entry=0x55ad83f71a60, profile=..., directory=...) at /usr/src/debug/konsole5-20.12.2-1.fc34.x86_64/src/MainWindow.cpp:512 #15 0x7f676737fa64 in Konsole::Application::newInstance (this=0x7ffeb57d1370) at /usr/src/debug/konsole5-20.12.2-1.fc34.x86_64/src/Application.cpp:235 #16 0x7f676738a918 in kdemain (argc=, argv=) at /usr/src/debug/konsole5-20.12.2-1.fc34.x86_64/src/main.cpp:235 #17 0x7f6766bc7b75 in __libc_start_main () from /lib64/libc.so.6 #18 0x55ad8234136e in _start () [Inferior 1 (process 9755) detached] -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 434892] konsole crash when open
https://bugs.kde.org/show_bug.cgi?id=434892 guy changed: What|Removed |Added CC||guy.car...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 434892] New: konsole crash when open
https://bugs.kde.org/show_bug.cgi?id=434892 Bug ID: 434892 Summary: konsole crash when open Product: konsole Version: 20.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: guy.car...@gmail.com Target Milestone: --- Application: konsole (20.12.2) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.11.8-300.fc34.x86_64 x86_64 Windowing System: X11 Drkonqi Version: 5.21.3 Distribution: Fedora 34 (KDE Plasma Prerelease) -- Information about the crash: - What I was doing when the application crashed: After I've upgrade frm F33 to F34 beta consloe crash when try to start it. The crash can be reproduced every time. -- Backtrace: Application: Konsole (konsole), signal: Aborted [KCrash Handler] #4 0x7f12bba2e292 in raise () from /lib64/libc.so.6 #5 0x7f12bba178a4 in abort () from /lib64/libc.so.6 #6 0x7f12bb8efc78 in std::__replacement_assert(char const*, int, char const*, char const*) () from /lib64/libkonsoleprivate.so.20 #7 0x7f12bb99248f in std::piecewise_linear_distribution::param_type::_M_initialize() () from /lib64/libkonsoleprivate.so.20 #8 0x7f12bb9995af in Konsole::ColorScheme::colorEntry(int, unsigned int) const () from /lib64/libkonsoleprivate.so.20 #9 0x7f12bb94ba29 in Konsole::TerminalDisplay::applyProfile(QExplicitlySharedDataPointer const&) () from /lib64/libkonsoleprivate.so.20 #10 0x7f12bb90333b in Konsole::ViewManager::applyProfileToView(Konsole::TerminalDisplay*, QExplicitlySharedDataPointer const&) () from /lib64/libkonsoleprivate.so.20 #11 0x7f12bb90b84b in Konsole::ViewManager::createView(Konsole::Session*) () from /lib64/libkonsoleprivate.so.20 #12 0x7f12bc1ca82e in Konsole::MainWindow::createSession(QExplicitlySharedDataPointer, QString const&) () from /lib64/libkdeinit5_konsole.so #13 0x7f12bc1d0a64 in Konsole::Application::newInstance() () from /lib64/libkdeinit5_konsole.so #14 0x7f12bc1db918 in kdemain () from /lib64/libkdeinit5_konsole.so #15 0x7f12bba18b75 in __libc_start_main () from /lib64/libc.so.6 #16 0x55a270f2936e in _start () [Inferior 1 (process 4727) detached] Possible duplicates by query: bug 399035. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 441668] Please make middle-click pasting optional
https://bugs.kde.org/show_bug.cgi?id=441668 Guy changed: What|Removed |Added CC||guyc1...@gmail.com Platform|Other |Fedora RPMs -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 464055] crash when entering a portfogllio transaction
https://bugs.kde.org/show_bug.cgi?id=464055 --- Comment #9 from Guy --- You got it right on the BTC /CHF brokerage account. It crashes when I try to type something into the amount box. It also crashes if I leave 0. I entered all previous buy transactions the same way, with the difference that an amount around in CHF was always proposed, never zero. I just had to adjust such amount. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 464055] crash when entering a portfogllio transaction
https://bugs.kde.org/show_bug.cgi?id=464055 --- Comment #2 from Guy --- Hello, I'm entering a buy transaction. It crashes when I try to input a value to replace the 0. The account is a placement account for Bitcoin and the currency is BTC. My main currency is the Swiss francs CHF Not sure I understand your asking about backtrack and debug though. Guy Le lun. 9 janv. 2023, 18:57, Jack a écrit : > https://bugs.kde.org/show_bug.cgi?id=464055 > > Jack changed: > >What|Removed |Added > > > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO >Platform|unspecified |Ubuntu > > --- Comment #1 from Jack --- > Please provide some additional information. You say you enter BTC and are > asked to confirm the amount of Swiss Francs (with 0 proposed) but you > don't say > what action you are trying to take (entering a buy transaction?) and what > type > of account, including the specified currency of that account and your base > currency. Also, what actually triggers the crash? Trying to save the > transaction? Just entering a value for Swiss Francs? Accepting the > currency > conversion dialog (is that where you are asked to confirm the value?) > Note - I do see a divide by 0 in the backtrace - are you accepting the 0 > value > for Swiss Francs? That clearly could cause a divide by 0. > Also, it might also help if you could get the backtrace with debug symbols > enabled, as I only see two reverences to kmm libraries in the backtrace, > but > the other information would be a good start. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 464055] New: crash when entering a portfogllio transaction
https://bugs.kde.org/show_bug.cgi?id=464055 Bug ID: 464055 Summary: crash when entering a portfogllio transaction Classification: Applications Product: kmymoney Version: 5.1.3 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: gmalacr...@gmail.com Target Milestone: --- Application: kmymoney (5.1.3) Qt Version: 5.15.6 Frameworks Version: 5.98.0 Operating System: Linux 5.19.0-28-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.10 DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: I enter the BTC and the pop up ask me to confirm the FIAT equivalent (in my case Swiss francs) but with 0 proposed as an amount. Usually it proposes something +/- equivalent to the rates downloaded with the Tools menu The crash can be reproduced every time. -- Backtrace: Application: KMyMoney (kmymoney), signal: Floating point exception [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=8, threadid=) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=8, threadid=) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=, signo=signo@entry=8) at ./nptl/pthread_kill.c:89 #7 0x7fa07443bc46 in __GI_raise (sig=8) at ../sysdeps/posix/raise.c:26 #8 0x7fa0752b399d in __gmp_exception () from /lib/x86_64-linux-gnu/libgmp.so.10 #9 0x7fa0752b39e4 in __gmp_divide_by_zero () from /lib/x86_64-linux-gnu/libgmp.so.10 #10 0x7fa0752d33bd in __gmpq_div () from /lib/x86_64-linux-gnu/libgmp.so.10 #11 0x7fa07994c226 in AlkValue::operator/(AlkValue const&) const () from /lib/x86_64-linux-gnu/libalkimia5.so.7 #12 0x7fa076b2d780 in MyMoneyMoney::operator/(MyMoneyMoney const&) const () from /lib/x86_64-linux-gnu/libkmm_mymoney.so.5 #13 0x55a882ba0eb7 in ?? () #14 0x7fa074ef36ff in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7fa0760b5656 in QLineEdit::textChanged(QString const&) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7fa074ef372c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7fa0760bce69 in QWidgetLineControl::textChanged(QString const&) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7fa0760c0590 in QWidgetLineControl::finishChange(int, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7fa0760c32c4 in QWidgetLineControl::processKeyEvent(QKeyEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7fa0760b5843 in QLineEdit::keyPressEvent(QKeyEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7fa079cd05bb in AmountEdit::keyPressEvent(QKeyEvent*) () from /lib/x86_64-linux-gnu/libkmm_widgets.so.5 #22 0x7fa075faf94a in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7fa075f6bf32 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7fa075f73f37 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7fa074ebae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7fa075fcb4e2 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x7fa075f6bf32 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x7fa074ebae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7fa07573e41d in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #30 0x7fa07571663c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #31 0x7fa06ead578e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #32 0x7fa072b9c4f9 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #33 0x7fa072bf1228 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #34 0x7fa072b99cb0 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #35 0x7fa074f14aea in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #36 0x7fa074eb97cb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #37 0x7fa07617b497 in QDialog::exec() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #38 0x55a882b9d3db in ?? () #39 0x55a882c001f7 in ?? () #40 0x55a882b9e3ba in ?? () #41 0x55a882beab41 in ?? () #42 0x55a882ace1f5 in ?? () #43 0x7fa074ef36ff in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #44 0x7fa075f65536 in QAction::triggered(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #45 0x7fa075f681f3 in QAction::activate(QAction::ActionEvent) () from
[kmymoney] [Bug 464055] crash when entering a portfogllio transaction
https://bugs.kde.org/show_bug.cgi?id=464055 --- Comment #5 from Guy --- Yes, exactly as you said -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 464055] crash when entering a portfogllio transaction
https://bugs.kde.org/show_bug.cgi?id=464055 --- Comment #7 from Guy --- I am using CHF from my bank account to buy BTC. CHF is my main currency and everything is converted into CHF. In my case I invested CHF 60 to buy 0.003773 BTC I enclose a printscreen of the situation. You can see the box where I usually put the countervalue in CHF (although it was never 0 before). As soon as I enter a number the program crashes. BTW I am not a developer, very sorry for my total lack of the conventions. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 464055] crash when entering a portfollio transaction
https://bugs.kde.org/show_bug.cgi?id=464055 --- Comment #12 from Guy --- I'll have to figure out how to create that small .kmy file. Looks to me a currency issue. I enclose a snapshot of the same kind of transaction in November that went OK (kmymonneyNoCrash.png). You can see that exchange rates are proposed whereby none are proposed in the new transaction that crashes the programme (see kmymonneyCrash.png). One was in EUR and the last in CHF though... Le mar. 17 janv. 2023 à 16:37, Jack a écrit : > > https://bugs.kde.org/show_bug.cgi?id=464055 > > Jack changed: > >What|Removed |Added > > Summary|crash when entering a |crash when entering a >|portfogllio transaction |portfollio transaction > > --- Comment #11 from Jack --- > I need to find time to make another attempt to reproduce this. If you can > create a small .kmy file which demonstrated the error (with exact instructions > on how to trigger it) that would be helpful. I'll leave the status for now, > so > we get reminded if nothing happens for too long. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 464055] crash when entering a portfogllio transaction
https://bugs.kde.org/show_bug.cgi?id=464055 --- Comment #10 from Guy --- Hello Jack, Any news? Anything I could/should do? thanks guy Guy Malacrida 33 ch. des Tuileries 1293 Bellevue/GE (Suisse) +41 78 603 7077 gmalacr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 464055] crash when entering a portfollio transaction
https://bugs.kde.org/show_bug.cgi?id=464055 --- Comment #14 from Guy --- Hello Jack, I found a way to solve the issue thanks to a thread in KDE.org, i.e. https://forum.kde.org/viewtopic.php?f=69=173354 I think I'm basically did not setup Bitcoin properly although it worked quite well since 2019 . Anyway, I followed the advice from the people in that thread and created a security BTC, an investment a/c "Investement in BTC" and a brokerage a/c "Investment in BTC (brokerage)". It works, differently though as I need to input the BTC CHF rate (i.e. 19'988) instead of the c/v in CHF (i.e. CHF 60). Thanks for your help and have a good day. Guy Le mar. 17 janv. 2023 à 18:43, Guy Malacrida a écrit : > > I'll have to figure out how to create that small .kmy file. > Looks to me a currency issue. I enclose a snapshot of the same kind of > transaction in November that went OK (kmymonneyNoCrash.png). You can > see that exchange rates are proposed whereby none are proposed in the > new transaction that crashes the programme (see kmymonneyCrash.png). > One was in EUR and the last in CHF though... > > > > Le mar. 17 janv. 2023 à 16:37, Jack a écrit : > > > > https://bugs.kde.org/show_bug.cgi?id=464055 > > > > Jack changed: > > > >What|Removed |Added > > > > Summary|crash when entering a |crash when entering a > >|portfogllio transaction |portfollio transaction > > > > --- Comment #11 from Jack --- > > I need to find time to make another attempt to reproduce this. If you can > > create a small .kmy file which demonstrated the error (with exact > > instructions > > on how to trigger it) that would be helpful. I'll leave the status for > > now, so > > we get reminded if nothing happens for too long. > > > > -- > > You are receiving this mail because: > > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468191] Backup hanging
https://bugs.kde.org/show_bug.cgi?id=468191 --- Comment #4 from Guy --- Thanks Jack. Let me update and I'll keep you posted. Guy On Fri, Apr 14, 2023, 5:02 PM Jack wrote: > https://bugs.kde.org/show_bug.cgi?id=468191 > > --- Comment #3 from Jack --- > Guy, > > Please do let us know if the current version (5.1.3) works ok or if we > still > have some digging to do on Windows. Particularly - without ticking the > "mount" > checkbox. > > Thanks. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468191] Backup hanging
https://bugs.kde.org/show_bug.cgi?id=468191 --- Comment #5 from Guy --- I installed the latest and it seems to have backed up the data. Thanks, Guy On Sat, Apr 15, 2023 at 10:12 AM Guy Clements wrote: > Thanks Jack. Let me update and I'll keep you posted. > > Guy > > On Fri, Apr 14, 2023, 5:02 PM Jack wrote: > >> https://bugs.kde.org/show_bug.cgi?id=468191 >> >> --- Comment #3 from Jack --- >> Guy, >> >> Please do let us know if the current version (5.1.3) works ok or if we >> still >> have some digging to do on Windows. Particularly - without ticking the >> "mount" >> checkbox. >> >> Thanks. >> >> -- >> You are receiving this mail because: >> You reported the bug. > > -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468191] New: Backup hanging
https://bugs.kde.org/show_bug.cgi?id=468191 Bug ID: 468191 Summary: Backup hanging Classification: Applications Product: kmymoney Version: 5.0.6 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: guy.cleme...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. File >> Backup 2. Select directory and check mount dir checkbox. 3. Click OK and mounting just hangs so backup never starts. OBSERVED RESULT Mounting hangs and backup never happens EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 11 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I manually backed up my *.kmy file but noit sure that's sufficient. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468191] Backup hanging
https://bugs.kde.org/show_bug.cgi?id=468191 --- Comment #2 from Guy --- That's cool.thanks for the feedback, if backing up manually works, I can deal with that. I'll check for an update and see if it Corrects the problem but to answer your question, I'm just saving to a local drive - either the same filesystem or another physical drive in the same chassis. Appreciate the rapid response . Guy On Wed, Apr 5, 2023, 10:15 PM Jack wrote: > https://bugs.kde.org/show_bug.cgi?id=468191 > > Jack changed: > >What|Removed |Added > > > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO > > --- Comment #1 from Jack --- > First, 5.0.6 is really old. Please try a more recent version - 5.1.3 is > current. > For your problem, what happens if you do not tick the box to mount the > backup > directory? Where are you trying to back up the file? To a local > directory or > a network share? > For your last question, yes, simply making a copy of the .kmy file is all a > backup does, so that is sufficient - but you should use some naming > convention > so each backup does not simply overwrite the previous one. > Let us know if any of this helps. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
please Help me with this bug
https://bugs.kde.org/show_bug.cgi?id=366213 I've been waiting for a very long time to get ANY help with my problem, PLEASE HELP. guy lapointe www.crowhealingnetwork.net "No country and no people can be free and ignorant at the same time." - Thomas Jefferson
[krusader] [Bug 380094] New: Krusader as Root opens with blank screen
https://bugs.kde.org/show_bug.cgi?id=380094 Bug ID: 380094 Summary: Krusader as Root opens with blank screen Product: krusader Version: 2.4.0-beta3 "Single Step" Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: m...@fork.pl Reporter: supp...@heviitech.com Target Milestone: --- I cannot run Krusader as Root whether I start from within Krusader (which appears to work flawlessly), from the Plasma menu (Fedora 25) or from the terminal with: su -l -c "export DISPLAY=:0 && dbus-launch krusader" A window opens but is completely devoid of icons and menus. Right-clicking has no effect. The following error is reported and repeated in the terminal window: X Error: BadShmSeg (invalid shared segment parameter) 128 Extension:130 (MIT-SHM) Minor opcode: 3 (X_ShmPutImage) Resource id: 0x6a0002f I am running: KDE Plasma 5.9.5 KDE Frameworks %.33.0 QT Version: 5.7.1 Fedora 25 with Kernel Version: 4.10.15-200.fc25.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 380094] Krusader as Root opens with blank screen
https://bugs.kde.org/show_bug.cgi?id=380094 --- Comment #2 from Hevii Guy <supp...@heviitech.com> --- Sorry Alex, we won't know why krusader 2.4.0-beta3 is sick; I obliterated all traces of it from my system! Instead of struggling, I compiled 2.6. After creating a couple of directories and a symlink to kdesu, I know have a healthy krusader :-) Any idea why Fedora packages an ancient beta version? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 207613] memcheck fails to handle paths with spaces on Mac; line numbers lost as result
https://bugs.kde.org/show_bug.cgi?id=207613 Guy Harris <g...@alum.mit.edu> changed: What|Removed |Added CC||g...@alum.mit.edu --- Comment #1 from Guy Harris <g...@alum.mit.edu> --- Duplicate of 205093? Or, at least, related to 205093? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 207613] memcheck fails to handle paths with spaces on Mac; line numbers lost as result
https://bugs.kde.org/show_bug.cgi?id=207613 --- Comment #3 from Guy Harris <g...@alum.mit.edu> --- $ valgrind --version valgrind-3.13.0 $ valgrind --leak-check=full /tmp/foo\ bar/foo\ bar ==98088== Memcheck, a memory error detector ==98088== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==98088== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==98088== Command: /tmp/foo\ bar/foo\ bar ==98088== --98088-- run: /usr/bin/dsymutil "/tmp/foo bar/foo bar" ... ==98088== 2,048 bytes in 1 blocks are definitely lost in loss record 37 of 42 ==98088==at 0x100096861: malloc (vg_replace_malloc.c:302) ==98088==by 0x10F6A: main (in /tmp/foo bar/foo bar) (deliberately leaked in my small test program). -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 354209] Taskbar "Show only task from the current screen" option Shows only the windows in the other screen
https://bugs.kde.org/show_bug.cgi?id=354209 Guy Sheffer changed: What|Removed |Added Resolution|UNMAINTAINED|FIXED --- Comment #5 from Guy Sheffer --- Heu, Just tested on KDE Plasma 5.12.4 and its indeed resolved. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398319] New: Start G'MIC Qt update error (incomplete alert)
https://bugs.kde.org/show_bug.cgi?id=398319 Bug ID: 398319 Summary: Start G'MIC Qt update error (incomplete alert) Product: krita Version: 4.1.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: G'Mic for Krita Assignee: krita-bugs-n...@kde.org Reporter: alomphega+kde@gmail.com Target Milestone: --- Created attachment 114809 --> https://bugs.kde.org/attachment.cgi?id=114809=edit Screen capture of the alert Just opening the "Start G'MIC Qt" Krita menu, we get an incomplete alert "Download error of" -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 341918] the source for udev is not correct
https://bugs.kde.org/show_bug.cgi?id=341918 Guy Maurel <guy.mau...@kde.org> changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[grantlee] [Bug 337945] a better info in CMakeLists.txt
https://bugs.kde.org/show_bug.cgi?id=337945 Guy Maurel <guy.mau...@kde.org> changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401837] Button Caption transcription error in french
https://bugs.kde.org/show_bug.cgi?id=401837 --- Comment #5 from Guy B --- Created attachment 116850 --> https://bugs.kde.org/attachment.cgi?id=116850=edit Button Caption transcription error in french: Apply --> Appliquer -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401837] Button Caption transcription error in french
https://bugs.kde.org/show_bug.cgi?id=401837 --- Comment #6 from Guy B --- Created attachment 116851 --> https://bugs.kde.org/attachment.cgi?id=116851=edit Button Caption transcription error in french: Defaults--->Défauts -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401837] Button Caption transcription error in french
https://bugs.kde.org/show_bug.cgi?id=401837 --- Comment #2 from Guy B --- Created attachment 116847 --> https://bugs.kde.org/attachment.cgi?id=116847=edit Button Caption transcription error in french: Cancel --> Annuler -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401837] Button Caption transcription error in french
https://bugs.kde.org/show_bug.cgi?id=401837 --- Comment #7 from Guy B --- Created attachment 116852 --> https://bugs.kde.org/attachment.cgi?id=116852=edit Button Caption transcription error in french: Close-->Fermer -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401837] Button Caption transcription error in french
https://bugs.kde.org/show_bug.cgi?id=401837 --- Comment #3 from Guy B --- Created attachment 116848 --> https://bugs.kde.org/attachment.cgi?id=116848=edit Button Caption transcription error in french: Help-->Aide -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401837] Button Caption transcription error in french
https://bugs.kde.org/show_bug.cgi?id=401837 --- Comment #4 from Guy B --- Created attachment 116849 --> https://bugs.kde.org/attachment.cgi?id=116849=edit Button Caption transcription error in french: Yes/No --> Oui/Non -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401837] New: Button Caption transcription error in french
https://bugs.kde.org/show_bug.cgi?id=401837 Bug ID: 401837 Summary: Button Caption transcription error in french Product: digikam Version: 5.9.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tags-Captions Assignee: digikam-bugs-n...@kde.org Reporter: guybeller...@videotron.ca Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Using any dialog box 2. 3. OBSERVED RESULT The button caption are not translate in french Cancel --> Annuler Defaults --> Défauts Close --> Fermer Help --> Aide Appy --> Appliquer Yes --> Oui No --> Non EXPECTED RESULT See the translation upward 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.
[digikam] [Bug 401834] New: The "Scanning Faces" dialog box is too large and can't be resized in french language
https://bugs.kde.org/show_bug.cgi?id=401834 Bug ID: 401834 Summary: The "Scanning Faces" dialog box is too large and can't be resized in french language Product: digikam Version: 5.9.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Maintenance Assignee: digikam-bugs-n...@kde.org Reporter: guybeller...@videotron.ca 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.
[digikam] [Bug 401849] New: Cannot Save Current Search
https://bugs.kde.org/show_bug.cgi?id=401849 Bug ID: 401849 Summary: Cannot Save Current Search Product: digikam Version: 5.9.0 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Searches Assignee: digikam-bugs-n...@kde.org Reporter: guybeller...@videotron.ca Target Milestone: --- SUMMARY When I try to save a search critera to use later, nothing appens STEPS TO REPRODUCE 1. Open search view 2. Enter search critera 3. Enter a nave for the search 4. Click on save icon OBSERVED RESULT There search do not appear in the search list 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.
[korganizer] [Bug 110288] Termine verschwinden KDE Update
https://bugs.kde.org/show_bug.cgi?id=110288 guy mathez changed: What|Removed |Added CC||guy.mat...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422504] All tagged images does not show in display when names starts with number.
https://bugs.kde.org/show_bug.cgi?id=422504 --- Comment #1 from Guy Dupont --- Created attachment 129087 --> https://bugs.kde.org/attachment.cgi?id=129087=edit Snapshot example -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422504] New: All tagged images does not show in display when names starts with number.
https://bugs.kde.org/show_bug.cgi?id=422504 Bug ID: 422504 Summary: All tagged images does not show in display when names starts with number. Product: digikam Version: 6.4.0 Platform: Appimage OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Tags-Engine Assignee: digikam-bugs-n...@kde.org Reporter: dupont...@gmail.com Target Milestone: --- Created attachment 129086 --> https://bugs.kde.org/attachment.cgi?id=129086=edit Digikam traces SUMMARY STEPS TO REPRODUCE 1. Original Organisation Folder 1: 20200305_scan600dpi_test.scanned22 – 2 images 1952+T_Papa18ans+1001.jpg 1953-juil+T_Papa19ans_Chevaux+Z_Papa_en_cheval+1002.jpg Folder 2: AlbumLouise3000_test.scanned22 – a single image All of three are TAGged NetB – because they are White and Black... 2. Going under Tags -> Type -> NetB This will display all 3 images - 2 from Folder 1 and the single one in folder 2. 3. Renaming the image in Folder 2. Raname the from directly from Digikan by removing the first letter from the file name. OBSERVED RESULT One of the images from Folder 1 does not show anymore. EXPECTED RESULT I should continue to see all 3 images. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: About: -- Professional Photo Management with the Power of Open Source - A KDE Family Project IRC: irc.freenode.net - #digikam Feedback: digikam-u...@kde.org Build date: Oct 30 2019 (target: RelWithDebInfo) Rev.: d4189399d3b9a70e172e2e4c619548c5dd933280 (c) 2002-2019, digiKam developers team https://www.digikam.org Libraries: -- KDE Frameworks 5.61.0 Qt 5.13.1 (built against 5.13.1) The xcb windowing system ADDITIONAL INFORMATION I will include an open office document with snapshot... I'm also adding the digikam traces. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422504] All tagged images does not show in display when names starts with number.
https://bugs.kde.org/show_bug.cgi?id=422504 --- Comment #3 from Guy Dupont --- Hello Mark, I was not able to reproduce the problem with the RC version provided, even on a larger scale. I will continue to do some more testings and keep you posted. Thank you very much, Guy -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 439045] New: Problème avec avec les signets de KATE qui ne s'enregistrent plus!
https://bugs.kde.org/show_bug.cgi?id=439045 Bug ID: 439045 Summary: Problème avec avec les signets de KATE qui ne s'enregistrent plus! Product: kate Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: guyyves.mich...@gmail.com Target Milestone: --- SUMMARY Bonjour, venant d'installer Debian GNU/Linux 10 (buster) KDE plasmashell 5.14.5, j'ai des problèmes jusqu'à présent inexistant sur les version précédente du KDE, avec les signets de KATE! Les signets ne s'enregistre plus?! Comment faire? Par avance merci. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.14.5 (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 ADDITIONAL INFORMATION Système d'exploitation : Debian GNU/Linux 10 Version de noyau : 4.19.0-17-amd64 Type de système d'exploitation : 64-bit Processeurs : 4 × Intel® Core™ i5-3230M CPU @ 2.60GHz Mémoire : 3,7 Gio de mémoire vive -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 439045] Problème avec avec les signets de KATE qui ne s'enregistrent plus!
https://bugs.kde.org/show_bug.cgi?id=439045 --- Comment #2 from Guy-Yves --- (In reply to Paul Worrall from comment #1) > Bonjour Guy-Yves > > Quelle version de Kate utilisez-vous (Aide=>À propos de Kate) ? Je ne vois > pas de problème avec 21.04.2. > > Je pense que les signets de Kate sont enregistrés dans > ~/.config/katemetainfos. Ce fichier existe-t-il et est-il accessible en > écriture ? > > Système d'exploitation : KDE néon 5.22 > Version KDE Plasma : 5.22.1 > Version des frameworks KDE : 5.83.0 > Version Qt : 5.15.3 > Version du noyau : 5.8.0-59-générique (64 bits) > Plateforme graphique : X11 > Processeurs : 2 × APU AMD A6-6400K avec carte graphique HD Radeon(tm) > Mémoire : 7,7 Gio de RAM > Processeur graphique : AMD CEDAR Bonjour et merci pour votre réponse rapide. Il s'agit de Kate Version 18.08.0, oui le fichier katemetainfos et bien enregistrés dans ~/.config/katemetainfos avec la variable "Bookmarks=" alors que jai mis des signets! Par avance merci. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 439045] Problème avec avec les signets de KATE qui ne s'enregistrent plus!
https://bugs.kde.org/show_bug.cgi?id=439045 --- Comment #3 from Guy-Yves --- (In reply to Paul Worrall from comment #1) > Bonjour Guy-Yves > > Quelle version de Kate utilisez-vous (Aide=>À propos de Kate) ? Je ne vois > pas de problème avec 21.04.2. > > Je pense que les signets de Kate sont enregistrés dans > ~/.config/katemetainfos. Ce fichier existe-t-il et est-il accessible en > écriture ? > > Système d'exploitation : KDE néon 5.22 > Version KDE Plasma : 5.22.1 > Version des frameworks KDE : 5.83.0 > Version Qt : 5.15.3 > Version du noyau : 5.8.0-59-générique (64 bits) > Plateforme graphique : X11 > Processeurs : 2 × APU AMD A6-6400K avec carte graphique HD Radeon(tm) > Mémoire : 7,7 Gio de RAM > Processeur graphique : AMD CEDAR Aussi j'ai le même problème identique avec KWrite 18.08.0 aucun signet ne s'enregistre!!! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 433437] FreeBSD support, part 1
https://bugs.kde.org/show_bug.cgi?id=433437 Guy Harris changed: What|Removed |Added CC||ghar...@sonic.net --- Comment #2 from Guy Harris --- (In reply to Paul Floyd from comment #0) > Created attachment 136050 [details] > diff in vex directory > > Primarily these changes concern the nature of alignment generated signals. > On Linux, these produce SIGSEGV and n FreeBSD they produce SIGBUS. On most if not all *BSDs they produce SIGBUS. That *might* be the case on Solaris as well. (I remember it being the case on SunOS on Sun-2, where 16-bit and wider quantities had to be aligned on 16-bit boundaries, and on SPARC; that probably carried over to SunOS 5.) Personally, I think that's how it *should* be, but -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 448107] Pointer for the Edit Shapes tool is a small rectangle of broken lines
https://bugs.kde.org/show_bug.cgi?id=448107 Guy Bonneau changed: What|Removed |Added CC||guy.bonn...@videotron.ca --- Comment #5 from Guy Bonneau --- I have the same issue with an LG 5K monitor. If I switch to an HD monitor the issue is gone. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 377928] kwallet fails to build under macOS
https://bugs.kde.org/show_bug.cgi?id=377928 --- Comment #5 from Guy Sheffer --- On ubuntu runing: sudo apt-get install libgpgme-dev solves the issue. its not set as a build-dep for some reason. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 377928] kwallet fails to build under macOS
https://bugs.kde.org/show_bug.cgi?id=377928 Guy Sheffer changed: What|Removed |Added CC||guys...@gmail.com --- Comment #4 from Guy Sheffer --- Hey, I have the same issue in 2022, ubuntu 21.10 ``` # kdesrc-build running: 'gmake' '-j' '4' # from directory: /home/guy/kde/build/kwallet [ 2%] Built target docs-kwallet-query-kwallet-query-1 [ 2%] Automatic MOC for target kwalletbackend5 [ 2%] Automatic MOC for target KF5Wallet [ 2%] Built target KF5Wallet_autogen [ 2%] Built target kwalletbackend5_autogen gmake[2]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libgpgme.so', needed by 'bin/libkwalletbackend5.so.5.93.0'. Stop. gmake[1]: *** [CMakeFiles/Makefile2:677: src/runtime/kwalletd/backend/CMakeFiles/kwalletbackend5.dir/all] Error 2 gmake[1]: *** Waiting for unfinished jobs [ 8%] Built target KF5Wallet gmake: *** [Makefile:160: all] Error 2 ``` Any idea what can be done? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 473829] Let users pick the type of device they've connected
https://bugs.kde.org/show_bug.cgi?id=473829 Scary Guy changed: What|Removed |Added CC|scary_...@tuta.io | -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 473829] New: Let users pick the type of device they've connected
https://bugs.kde.org/show_bug.cgi?id=473829 Bug ID: 473829 Summary: Let users pick the type of device they've connected Classification: Applications Product: kdeconnect Version: unspecified Platform: postmarketOS OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: scary_...@tuta.io CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY Getting SMS messages to work properly is an exercise in futility. I'm not sure where the stopgap is but one issue I've found is that it doesn't see my Pinephone as an actual phone but rather as just a generic Linux device. I connected to an Android phone and I saw that there are a few more options available. STEPS TO REPRODUCE 1. Connect phone 2. Open KDE Connect SMS OBSERVED RESULT "No Devices Available" EXPECTED RESULT Device is seen and connects. It should be noted that I'm not a developer and I don't know how to code. I only know how to complain and point out problems/make suggestions. I tried to tell the PostmarketOS guys in the Matrix and they told me to come to you guys, so I made an account and have done so. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 473829] Let users pick the type of device they've connected
https://bugs.kde.org/show_bug.cgi?id=473829 Scary Guy changed: What|Removed |Added CC||scary_...@tuta.io -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 453743] New: Admin password request is hidden by 'scanning devices' window
https://bugs.kde.org/show_bug.cgi?id=453743 Bug ID: 453743 Summary: Admin password request is hidden by 'scanning devices' window Product: partitionmanager Version: 21.12.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: ericgreenwood...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open KDE partition manager as normal user OBSERVED RESULT Under wayland: The main window opens; the admin password request flashes on screen; then the 'scanning devices' window appears, pushing the main window (it's parent window) into focus and leaving the password request window in the background Under X.org: Almost the same, except the 'scanning devices' window does not pull the main window into focus, but does still open on top of the password request window. EXPECTED RESULT The password request window would be in focus after opening so the password can be entered without needing to look for the window, For example: The partition manager would wait for admin permissions before it starts to scan devices, therefore leaving the password request window in focus, and opening the 'scanning devices' window after the password request was successful and that window has closed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE plasma KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Graphics Platform: Wayland/X.org -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 453743] Admin password request is hidden by 'scanning devices' window
https://bugs.kde.org/show_bug.cgi?id=453743 Random Guy changed: What|Removed |Added CC||ericgreenwood...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 458246] New: Scroll wheel tilt (scrolling left and right) behaves the same as scrolling up and down.
https://bugs.kde.org/show_bug.cgi?id=458246 Bug ID: 458246 Summary: Scroll wheel tilt (scrolling left and right) behaves the same as scrolling up and down. Product: gwenview Version: 22.04.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: ericgreenwood...@gmail.com Target Milestone: --- SUMMARY Scroll wheel tilt (scrolling left and right) behaves the same as scrolling up and down. STEPS TO REPRODUCE 1. open gwenview 2. load an image in view mode or fullscreen view mode 3. scroll horizontally - using tilt on scroll wheel, and probably any other horizontal scrolling input feature, such as some touchpads, but I have only tested the horizontal scroll from my scroll wheel. OBSERVED RESULT Scrolling left zooms in (as if I scrolled up), and scrolling right zooms out (as if I scrolled down). EXPECTED RESULT There are options to set 'scrolling' to browse or to zoom, however, when an input device has a horizontal scroll feature it would be useful to be able to set 'vertical scrolling' and 'horizontal scrolling' seperately (I always think more options are better), or just make it so that they invert, and if 'scrolling' is set to zoom then horizontal scroll will browse, or visa versa. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux DE: KDE Plasma KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Graphics Platform: Wayland Processor: AMD Ryzen 5 5600X 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 343108] The 'memo' field in the 'kmmTransactions' table is not updated for duplicated transactions
https://bugs.kde.org/show_bug.cgi?id=343108 --- Comment #2 from Guy Germeaux --- Hello Justin, I am currently not working with the latest version, so I will have to countercheck. In previous versions, the reported error was easily reproducible (just choosing “duplicate” for an existing transaction and the memo field was always blank). Regards, Guy > On 17 Oct 2022, at 02:40, Justin Zobel wrote: > > https://bugs.kde.org/show_bug.cgi?id=343108 > > Justin Zobel changed: > > What|Removed |Added > > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Justin Zobel --- > Thank you for reporting this bug in KDE software. As it has been a while since > this issue was reported, can we please ask you to see if you can reproduce the > issue with a recent software version? > > If you can reproduce the issue, please change the status to "CONFIRMED" when > replying. Thank you! > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448778] Unplugging an external monitor leads to a crash
https://bugs.kde.org/show_bug.cgi?id=448778 --- Comment #15 from Random Guy --- (In reply to Zamundaaa from comment #14) > Please open a new bug report for that issue, it doesn't sound related at a > first glance; KWin crashing does not make your monitors hang The monitors are not actually hanging, I can use ctrl+alt+fX and login on another tty. I think it might actually be a bug within wayland itself so I may make a report there. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448778] Unplugging an external monitor leads to a crash
https://bugs.kde.org/show_bug.cgi?id=448778 Random Guy changed: What|Removed |Added CC||ericgreenwood...@gmail.com --- Comment #13 from Random Guy --- I believe I am having this same issue, in KDE version 5.25 on Wayland. I have a PC with 2 monitors connected, and I have a projector on which I watch films/TV shows. When I turn off the monitors and connect the projector the display sometimes freezes without the rest of the system crashing - music remains playing indefinitely in the background. The same crash also occasionally happens when waking from sleep. I presume the fix mentioned in this thread is enough for most use cases, however I have one old monitor and one new monitor so my main setup is 1680*1050 @ 60hz on DVI and a gaming monitor using 1920*1050 @ up to 144hz (with AMD freesync) on HDMI so I think it is testing this fix quite hard (along with many other parts of the system - it took me a while to get it working at all). It is not a dealbreaker as I can restart and retry when it breaks which is about 1 in 3 attempts, however I wanted to log the fact that this is still an issue. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 461264] If Dolphin is already open, it is not brought to foreground when opened via link
https://bugs.kde.org/show_bug.cgi?id=461264 --- Comment #2 from Random Guy --- Ah great, sorry I did not find those when searching prior to making my report :) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 461264] New: If Dolphin is already open, it is not brought to foreground when opened via link
https://bugs.kde.org/show_bug.cgi?id=461264 Bug ID: 461264 Summary: If Dolphin is already open, it is not brought to foreground when opened via link Classification: Applications Product: dolphin Version: 22.08.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ericgreenwood...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY NOTE: I am using Wayland. When dolphin is already open in the background and is then opened via a link (e.g. clicking 'mount and open in file manager' in the removable devices popup) a new tab is added and the window remains in the background. If 'Open new folders in tabs' is deselected then it opens a new window in the foreground, however I would expect it to open in a new tab and bring the whole window to the foreground. STEPS TO REPRODUCE (with Dolphin configured to use tabs) 1. Open Dolphin 2. Open another window on top. 3. Open Dolphin via a link (e.g. 'open in file manager' from the removable devices dialog) OBSERVED RESULT Dolphin opens a new tab and the icon is highlighted in orange on the window switcher, but it remains in the background EXPECTED RESULT Either 1: A new tab would be opened and the whole window would be brought to the foreground, or 2: There would be a toggle to switch between the two outcomes in the settings. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE Plasma KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Renderer: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 477173] "Close Document" warning shows twice
https://bugs.kde.org/show_bug.cgi?id=477173 Kwok Guy changed: What|Removed |Added OS|Other |Microsoft Windows -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 477173] New: "Close Document" warning shows twice
https://bugs.kde.org/show_bug.cgi?id=477173 Bug ID: 477173 Summary: "Close Document" warning shows twice Classification: Applications Product: kate Version: 23.08.3 Platform: Microsoft Windows OS: Other Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: kwok...@163.com Target Milestone: --- SUMMARY "Close Document" warning shows twice if the user is going to exit Kate. STEPS TO REPRODUCE 1. Open Kate. 2. Input anything. 3. Exit Kate. 4. For the first "Close Document" warning dialog, select "Cancel". OBSERVED RESULT "Close Document" warning shows again. EXPECTED RESULT "Close Document" warning should not appear for the second time. SOFTWARE/OS VERSIONS Windows: 10 22H2 19045.3693 ADDITIONAL INFORMATION By the way, if there are more than one documents, when kate is being closed, it will ask separately for all documents, and if the user selects "Cancel", it will then show a "Save documents" dialog. Maybe we only need the "Save documents" dialog? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 477173] "Close Document" warning shows twice
https://bugs.kde.org/show_bug.cgi?id=477173 --- Comment #1 from Kwok Guy --- Created attachment 163257 --> https://bugs.kde.org/attachment.cgi?id=163257=edit "Close Document" warning shows twice -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 189254] No support for transparent background with wallpaper only
https://bugs.kde.org/show_bug.cgi?id=189254 --- Comment #14 from Guy Sheffer --- Created attachment 167839 --> https://bugs.kde.org/attachment.cgi?id=167839=edit ubuntu 23.10 with trsnaparrent window, with another window visible underneeth (In reply to Kurt Hindenburg from comment #13) > Any recent versions should have want you requested. Hey, Thanks for getting back on this after such a long time! Just tested in Ubuntu 23.10 and this still does not exist there. You can make either the konsole window transparent but you can see the windows below. Or you can set a wallpaper that would be stretched and tiled independent to the background of the desktop. Attaching a photo. I will note though that I am not really using that feature at the moment, so its not urgent for me. However I thought is worth documenting. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 189254] No support for transparent background with wallpaper only
https://bugs.kde.org/show_bug.cgi?id=189254 --- Comment #16 from Guy Sheffer --- (In reply to Kurt Hindenburg from comment #15) > (In reply to Guy Sheffer from comment #14) > > Created attachment 167839 [details] > > ubuntu 23.10 with trsnaparrent window, with another window visible > > underneeth > > > > (In reply to Kurt Hindenburg from comment #13) > > > Any recent versions should have want you requested. > > > > Hey, Thanks for getting back on this after such a long time! > > > > Just tested in Ubuntu 23.10 and this still does not exist there. You can > > make either the konsole window transparent but you can see the windows > > below. > > > > Or you can set a wallpaper that would be stretched and tiled independent to > > the background of the desktop. > > > > Attaching a photo. > > > > I will note though that I am not really using that feature at the moment, so > > its not urgent for me. However I thought is worth documenting. > > Interesting I didn't realize KDE4/konsole had this feature. You want the > transparency to ignore everything but the desktop background. Its from KDE 3, there is a screenshot attached of KDE 3 with the feature, and my very messy desktop :) . And the report was after upgrading to 4. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 365125] Win64 version cannot start
https://bugs.kde.org/show_bug.cgi?id=365125 Guy <guyrutenb...@gmail.com> changed: What|Removed |Added CC||guyrutenb...@gmail.com --- Comment #38 from Guy <guyrutenb...@gmail.com> --- Created attachment 99952 --> https://bugs.kde.org/attachment.cgi?id=99952=edit Dependency Walker log Dependency Walker log detailing missing DLLs. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415233] New: Plasma panel crasshes while using Google Chrome.
https://bugs.kde.org/show_bug.cgi?id=415233 Bug ID: 415233 Summary: Plasma panel crasshes while using Google Chrome. Product: plasmashell Version: 5.17.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: elementalgu...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.4) Qt Version: 5.13.2 Frameworks Version: 5.65.0 Operating System: Linux 5.0.0-37-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: I was watching a video in YouTube in the current google-chrome-stable build. - Unusual behavior I noticed: The Plasma panel randomly disappeared and reappeared. The crash does not seem to be reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5bfc4dee40 (LWP 1304))] Thread 25 (Thread 0x7f5b02ffd700 (LWP 4872)): #0 0x7f5bf32349f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55d180951dd4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f5bf32349f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55d180951d80, cond=0x55d180951da8) at pthread_cond_wait.c:502 #2 0x7f5bf32349f3 in __pthread_cond_wait (cond=0x55d180951da8, mutex=0x55d180951d80) at pthread_cond_wait.c:655 #3 0x7f5bf6304aeb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f5bf6304df9 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f5bbb77b845 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f5bbb77f6f8 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f5bbb77ab0d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f5bbb77d5bb in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f5bf62fdb52 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f5bf322e6db in start_thread (arg=0x7f5b02ffd700) at pthread_create.c:463 #11 0x7f5bf5bfa88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7f5b037fe700 (LWP 4871)): #0 0x7f5bf32349f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55d180951dd4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f5bf32349f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55d180951d80, cond=0x55d180951da8) at pthread_cond_wait.c:502 #2 0x7f5bf32349f3 in __pthread_cond_wait (cond=0x55d180951da8, mutex=0x55d180951d80) at pthread_cond_wait.c:655 #3 0x7f5bf6304aeb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f5bf6304df9 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f5bbb77b845 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f5bbb77f6f8 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f5bbb77ab0d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f5bbb77d5bb in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f5bf62fdb52 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f5bf322e6db in start_thread (arg=0x7f5b037fe700) at pthread_create.c:463 #11 0x7f5bf5bfa88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7f5b03fff700 (LWP 4870)): #0 0x7f5bf32349f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55d180951dd4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f5bf32349f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55d180951d80, cond=0x55d180951da8) at pthread_cond_wait.c:502 #2 0x7f5bf32349f3 in __pthread_cond_wait (cond=0x55d180951da8, mutex=0x55d180951d80) at pthread_cond_wait.c:655 #3 0x7f5bf6304aeb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f5bf6304df9 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f5bbb77b845 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6
[okular] [Bug 437185] New: Tabs appear to be misbehaving.
https://bugs.kde.org/show_bug.cgi?id=437185 Bug ID: 437185 Summary: Tabs appear to be misbehaving. Product: okular Version: 21.04.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: ben2t...@yahoo.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Open a document with Okular 2. Open other documents in new tabs. 3. Try to view two documents side by side. OBSERVED RESULT Unable to find the option to 1. tear off a tab to create a new window or 2. Move a tab to a new window or 3. Split window to view two or more tabs side by side or as a 4x4 grid. These options would appear to be a 'standard' for desktop apps - though some do not behave. EXPECTED RESULT Operating System: Manjaro Linux KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Kernel Version: 5.12.1-2-MANJARO OS Type: 64-bit Graphics Platform: X11 Processors: 4 × Intel® Core™ i3-4130 CPU @ 3.40GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4400 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 458450] New: New subscriptions marked as played...
https://bugs.kde.org/show_bug.cgi?id=458450 Bug ID: 458450 Summary: New subscriptions marked as played... Product: kasts Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: b...@mogwai.be Reporter: ben2t...@yahoo.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Subscribe to a new Podcast previously not listened. 2. Go to Subscriptions, select podcast. OBSERVED RESULT All items in the list have a tick, the word 'played' and the date the episode was aired (not played). EXPECTED RESULT All podcasts should not be marked played until after they have been played. Linux/KDE Plasma: KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 462615] Use KActionCollection::setDefaultShortcut(s) instead
https://bugs.kde.org/show_bug.cgi?id=462615 Ben Guy-Williams changed: What|Removed |Added CC||ben2t...@yahoo.com --- Comment #2 from Ben Guy-Williams --- ``` Dec 27 18:08:42 konsole[1947]: kf.xmlgui: Shortcut for action "" "Show Quick Commands" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. Dec 27 18:08:42 konsole[1947]: kf.xmlgui: Shortcut for action "" "Show SSH Manager" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. ``` -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 428762] Akonadi is asking for gmail authentication every 10ish minutes?
https://bugs.kde.org/show_bug.cgi?id=428762 Ben Guy-Williams changed: What|Removed |Added CC||ben2t...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[KClock] [Bug 467093] Only major cities are available in the city list
https://bugs.kde.org/show_bug.cgi?id=467093 --- Comment #3 from Ben Guy-Williams --- Haha ok. This does work, indeed, but the search is quite limited. I searched New Zealand and get to it that way on the plasmoid 'Digital Clock 3.0'. Certainly Kidderminster is not available there also, but the flexibility of searching by country on that Plasma by Martin Klapetek is interesting. Sent from Mailspring (https://link.getmailspring.com/link/7b2fcdea-4f4f-417f-9221-8c66a37f0...@getmailspring.com/0?redirect=https%3A%2F%2Fgetmailspring.com%2F=YnVnLWNvbnRyb2xAa2RlLm9yZw%3D%3D), the best free email app for work On Mar 14 2023, at 2:38 am, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=467093 > > Nate Graham changed: > What |Removed |Added > > CC| |n...@kde.org > Summary|Cannot add locations for |Only major cities are > |clocks in KClock... |available in the city list > Ever confirmed|0 |1 > Severity|normal |minor > Status|REPORTED |CONFIRMED > Keywords| |usability > > --- Comment #2 from Nate Graham --- > "Auckland" is present, but "Aukland (a misspelling)" is not. "kidderminster" > is > too small to be included in the city list. Try London. > > We could probably improve the error message here to say something like "Check > the spelling or try searching for the nearest major city." > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[KClock] [Bug 467093] New: Cannot add locations for clocks in KClock...
https://bugs.kde.org/show_bug.cgi?id=467093 Bug ID: 467093 Summary: Cannot add locations for clocks in KClock... Classification: Applications Product: KClock Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: espi...@gmail.com Reporter: ben2t...@yahoo.com CC: hanyo...@protonmail.com Target Milestone: --- SUMMARY *** Unable to add specific clock. *** STEPS TO REPRODUCE 1. Select `+ Add` 2. Try to set a clock for New Zealand, Aukland. Try to search for `kidderminster` (UK town). 3. No results appear - unable to add clock for New Zealand. 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.
[Arianna] [Bug 469037] New: No option to manage library.
https://bugs.kde.org/show_bug.cgi?id=469037 Bug ID: 469037 Summary: No option to manage library. Classification: Applications Product: Arianna Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: c...@carlschwan.eu Reporter: ben2t...@yahoo.com Target Milestone: --- Starting up Arianna brings a list of items in local directories which I did not want automatically add. Calibre has a total of 1676 listed which I want to be able to open in Arianna, but I only want Arianna to remember selected books on the front page. STEPS TO REPRODUCE 1. Install Flatpak Arianna (as version 1.01 crashes with` "KF5KirigamiAddons" that is compatible with requested version "0.8". ` error) 2. Nothing else required - it opens and has no menu until you find the oddly located settings button. 3. No option to edit colours (see Foliate for an example) and apparently no option to modify the font. With Foliate, these are easily accessed via hidden menu options). OBSERVED RESULT Options limited and instantly forgotten upon restart. EXPECTED RESULT Experience approaching that of Foliate. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.12-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD Radeon Graphics Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I will test again with the next release. With the AUR installation around 605 kb vs the Flathub version at 172,600 kB I will wait until it will build from AUR. Further comments - finding a chapter (Ctrl_T) was absent, as were context menu options once a book was loaded). -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 462931] "No metadata URIs for vendor directory" error seen in Discover for disabled fwupd repo
https://bugs.kde.org/show_bug.cgi?id=462931 Ben Guy-Williams changed: What|Removed |Added CC||ben2t...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 471278] New: Discover fails update doe to contents of /tmp
https://bugs.kde.org/show_bug.cgi?id=471278 Bug ID: 471278 Summary: Discover fails update doe to contents of /tmp Classification: Applications Product: Discover Version: 5.27.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: ben2t...@yahoo.com CC: aleix...@kde.org Target Milestone: --- SUMMARY *** Failed Update *** Initial messages: ``` Unsupported question: This file already exists on disk (possibly due to an earlier failed download attempt). Continuing means overwriting it. Do you wish to overwrite the existing file? '/home/ben/.local/share/color-schemes/Neither2.colors' ``` STEPS TO REPRODUCE 1. Open Discover - see 16 updates. 2. Choose to 'Install Updates' 3. Delete 'Neither2.colors' 4. Refresh and update 5. Attempt to deselect ALL update items and select only one (Advanced Radio Player) 6. Refresh and update Operating System: Manjaro Linux KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.3.5-2-MANJARO (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD Radeon Graphics Product Name: B550M Steel Legend ADDITIONAL INFORMATION Even when everything is de-selected, the Advanced Radio Player simply does not update (no error appears). ** Deleting contents of /tmp removes the issue. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 469690] New: Kate and Kwrite - Close Document warning dialog returns after completion.
https://bugs.kde.org/show_bug.cgi?id=469690 Bug ID: 469690 Summary: Kate and Kwrite - Close Document warning dialog returns after completion. Classification: Applications Product: kate Version: 23.04.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: ben2t...@yahoo.com Target Milestone: --- SUMMARY *** Warning dialogue recurs after cancelling *** STEPS TO REPRODUCE 1. Create a file 'Kate' or 'Kwrite' and enter text 'this is a text'. 2. Save the file. 3. Type some more. 4. Quit the application 5. Click Cancel ONE TIME. OBSERVED RESULT Dialog returns, very slightly altered in shape - but with identical text and options. EXPECTED RESULT After clicking Cancel, the dialog should not re-appear. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.3.0-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD Radeon Graphics Product Name: B550M Steel Legend -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 469690] Kate and Kwrite - Close Document warning dialog returns after completion.
https://bugs.kde.org/show_bug.cgi?id=469690 --- Comment #1 from Ben Guy-Williams --- Created attachment 158903 --> https://bugs.kde.org/attachment.cgi?id=158903=edit Kate-Kwrite dialog in question file:///home/ben/Desktop/Kate-Kwrite-Bug.png -- You are receiving this mail because: You are watching all bug changes.
[Keysmith] [Bug 481355] New: Keysmith is asking for a password before I used it.
https://bugs.kde.org/show_bug.cgi?id=481355 Bug ID: 481355 Summary: Keysmith is asking for a password before I used it. Classification: Applications Product: Keysmith Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: bhus...@gmail.com Reporter: ben2t...@yahoo.com Target Milestone: --- SUMMARY *** After installation, Keysmith asks me for a password to unlock accounts. I have no idea what that should be, I haven't made a password for this application before. *** STEPS TO REPRODUCE 1. Install 2. Launch OBSERVED RESULT Undefined password requested. EXPECTED RESULT Request to enter a password on first run. SOFTWARE/OS VERSIONS Linux/KDE Plasma: plasma 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482418] Desktop Grid Layout Preference to Ignore the Pager layout possible in Plasma 6?
https://bugs.kde.org/show_bug.cgi?id=482418 Ben Guy-Williams changed: What|Removed |Added CC||ben2t...@yahoo.com --- Comment #4 from Ben Guy-Williams --- I made the discovery that, if you open your Virtual Desktop settings and set, let's go for 4 desktops (works nicely in the Grid, right?) If you then set 4 ROWS. Then you have 4 vertical desktops... which display (IMO) nicely in Overview (but suck in Grid). The vertical desktop arrangement here is actually nicer for navigation for me. If you set 1 ROW, then you have 4 Horizontal desktops... which display worse still in GRID, and not much better in Overview. So we have a Hobsons Choice here. I would suggest 1. Fix the Grid, and make Overview flexible in lining up whatever desktops we have or 2. Fix the Overview and make GRID more flexible. Desktops have names/numbers, so an option to display this - if we assume that mixing up layouts would be in some way 'confusing'. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475077] Show non-linear virtual desktop arrangements again
https://bugs.kde.org/show_bug.cgi?id=475077 Ben Guy-Williams changed: What|Removed |Added CC||ben2t...@yahoo.com --- Comment #27 from Ben Guy-Williams --- (In reply to Rafael Lima from comment #14) > (In reply to Niccolò Venerandi from comment #8) > > You can press the Overview shortcut again to switch to the grid mode and > > easily move applications between desktops > > Unfortunately this is not a nice experience. The current implementation in > 5.27 is so much better. > > (In reply to postix from comment #13) > > To further decrease any confusion about a different layout some users may > > have due the linearization I'd suggest to add a row indicator to the VD > > preview bar. Please see the mockup. I believe this makes it pretty obvious > > and clear. :) > > TBH I think the indicators are not needed... they clutter the interface. It > would be better to simply revert to what we had in 5.27. > > If a user sets a 2x2 = 4 workspaces, they won't find it weird to see a row > with 4 workspaces when they open the overview. Now, if the user sees nothing > at the top bar when the Overview is started, then this will be weird. When pressing 'Meta+W' to get overview, pressing it again simply enters 'W' in the search. I'm having a lot of trouble understanding this, my rectangular screen zooms 4 desktops in a lovely grid with good resolution on a FHD monitor - why can't I just see 4 in a row in Overview? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484555] Enhance with “Create folder from selected files”
https://bugs.kde.org/show_bug.cgi?id=484555 Ben Guy-Williams changed: What|Removed |Added CC||ben2t...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377162] Window shading not supported for Wayland windows
https://bugs.kde.org/show_bug.cgi?id=377162 Ben Guy-Williams changed: What|Removed |Added CC||ben2t...@yahoo.com --- Comment #28 from Ben Guy-Williams --- (In reply to Alan Prescott from comment #27) > This is an annoying bug in Wayland - I've just gotten so used to setting > mouse wheel to shade/unshade and the upgrade to Plasma6 & Wayland without > this means I've lost a major plus feature. > > Operating System: openSUSE Tumbleweed 20240319 > KDE Plasma Version: 6.0.2 > KDE Frameworks Version: 6.0.0 > Qt Version: 6.6.2 > Kernel Version: 6.8.1-1-default (64-bit) > Graphics Platform: Wayland Aha. I used Mouse Gestures heavily in the past - to manage my windows mostly - as well as occasionally shading a window here and there... Now that we're moving to Wayland, and leaving (at least for now...) the likes of 'Easystroke' and hoping for development on the likes of 'Mouse Actions' then this redundant (visible, but not working) feature is rather a nasty tease. -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 483439] File browser crashing Strawberry and similar programs
https://bugs.kde.org/show_bug.cgi?id=483439 Ben Guy-Williams changed: What|Removed |Added CC||ben2t...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484362] New: Column navigation with arrow keys...
https://bugs.kde.org/show_bug.cgi?id=484362 Bug ID: 484362 Summary: Column navigation with arrow keys... Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: plasma-b...@kde.org Reporter: ben2t...@yahoo.com Target Milestone: 1.0 Created attachment 167684 --> https://bugs.kde.org/attachment.cgi?id=167684=edit Search in menu - result in Documents pane/column. SUMMARY With Plasma 5, I was able to start typing (e.g. to pull up `Record.ods`) and see this in the THIRD column (Documents) and then right arrow would navigate between columns. Now it appears that this is not working. STEPS TO REPRODUCE 1. Choose an indexed document to launch. 2. Type incomplete name until document appears in Document column. 3. Press Arrow key to navigate to the right across columns OBSERVED RESULT Cannot navigate to other columns without the mouse. EXPECTED RESULT Can navigate to other columns without the mouse. 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.
