[kmymoney4] [Bug 371055] New: crash while attempting to update account / download bank transactions
https://bugs.kde.org/show_bug.cgi?id=371055 Bug ID: 371055 Summary: crash while attempting to update account / download bank transactions Product: kmymoney4 Version: 4.8.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: b...@mroczka.com Application: kmymoney (4.8.0) KDE Platform Version: 4.14.22 Qt Version: 4.8.7 Operating System: Linux 4.8.0-22-generic x86_64 Distribution: Ubuntu 16.10 -- Information about the crash: - What I was doing when the application crashed: >From ledger view attempting to update account crashes kmymoney. This issue is only happening for one credit card account and it crashes every time in the same place. After closing the dialog after authenticating with bank. The crash can be reproduced every time. -- Backtrace: Application: KMyMoney (kmymoney), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0272c0b900 (LWP 5207))] Thread 2 (Thread 0x7f0257511700 (LWP 5209)): #0 0x7f02684d186d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f02684d1aec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f026df5b22e in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #3 0x7f026df2912f in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7f026df29495 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7f026de18549 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7f026df091c3 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f026de1ae3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7f02689ba70a in start_thread (arg=0x7f0257511700) at pthread_create.c:333 #9 0x7f026cd700af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 1 (Thread 0x7f0272c0b900 (LWP 5207)): [KCrash Handler] #6 QBasicAtomicInt::ref (this=0xf8) at /usr/include/qt4/QtCore/qatomic_x86_64.h:121 #7 QMap::QMap (other=..., this=0x7ffc453cede0) at /usr/include/qt4/QtCore/qmap.h:184 #8 MyMoneyAccount::MyMoneyAccount (this=0x7ffc453ced60) at /build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/mymoney/mymoneyaccount.h:81 #9 0x7f0255507991 in KMyMoneyBanking::importAccountInfo (this=0x55fff6cfa220, ai=0x55fff6a16a00) at /build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/plugins/kbanking/mymoneybanking.cpp:1437 #10 0x7f0255511a7b in AB_Banking::importContext (this=0x55fff6cfa220, ctx=0x55fff5c3d3d0, flags=0) at /build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/plugins/kbanking/banking.cpp:199 #11 0x7f025550a8c6 in KBankingPlugin::executeQueue (this=this@entry=0x55fff6d28070) at /build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/plugins/kbanking/mymoneybanking.cpp:571 #12 0x7f025550a99d in KBankingPlugin::executeQueue (this=0x55fff6d28070) at /build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/plugins/kbanking/mymoneybanking.cpp:566 #13 0x7f025550aaa8 in KBankingPlugin::updateAccount (this=, acc=..., moreAccounts=) at /build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/plugins/kbanking/mymoneybanking.cpp:559 #14 0x55fff3783416 in KMyMoneyApp::slotAccountUpdateOnline (this=this@entry=0x55fff5657810) at /build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/kmymoney.cpp:7576 #15 0x55fff37cbfb5 in KMyMoneyApp::qt_static_metacall (_o=0x55fff5657810, _c=, _id=, _a=0x7ffc453cf580) at /build/kmymoney-8ALMks/kmymoney-4.8.0/obj-x86_64-linux-gnu/kmymoney/moc_kmymoney.cpp:531 #16 0x7f026df3ef70 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #17 0x7f026e931dc2 in QAction::triggered(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #18 0x7f026e933113 in QAction::activate(QAction::ActionEvent) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #19 0x7f026e93366c in QAction::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #20 0x7f026f5b3c12 in KAction::event(QEvent*) () from /usr/lib/libkdeui.so.5 #21 0x7f026e93803c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #22 0x7f026e93ef76 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #23 0x7f026f69e4ba in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #24 0x7f026df2a8ad in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #25 0x7f026e96ef78 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #26 0x7f026e96f167 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #27 0x7f026e940
[kmymoney4] [Bug 371055] crash while attempting to update account / download bank transactions
https://bugs.kde.org/show_bug.cgi?id=371055 b...@mroczka.com changed: What|Removed |Added Component|general |onlinebanking -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 371055] crash while attempting to update account / download bank transactions
https://bugs.kde.org/show_bug.cgi?id=371055 --- Comment #3 from b...@mroczka.com --- I am using QIF. I attempted to unmap and map the troubled account and a download worked once but then crashed thereafter. I also attemtped to create a new credit card account to the same bank account to see if I could at least download the transactions and then move them to my existing credit card account. In the process of different things it is working now but everytime I click to update the account it always asks me to which account I want to assign the downloaded transactions to. As long as I don't get a crash I happy to reselect the account everytime. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 371055] crash while attempting to update account / download bank transactions
https://bugs.kde.org/show_bug.cgi?id=371055 --- Comment #4 from b...@mroczka.com --- Correction. I could be wrong but I don't believe my bank is sending QIF behind the scenes. I believe the format is actually OFX. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display.
https://bugs.kde.org/show_bug.cgi?id=353975 b...@mroczka.com changed: What|Removed |Added CC||b...@mroczka.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365240] kde.systemtray floods .xsession-errors with messages if Thunderbird is running
https://bugs.kde.org/show_bug.cgi?id=365240 b...@mroczka.com changed: What|Removed |Added CC||b...@mroczka.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 465693] New: New File Setup dialog wording wrong
https://bugs.kde.org/show_bug.cgi?id=465693 Bug ID: 465693 Summary: New File Setup dialog wording wrong Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: ux-ui Assignee: kmymoney-de...@kde.org Reporter: kmymoney@dfgh.net Target Milestone: --- Created attachment 156214 --> https://bugs.kde.org/attachment.cgi?id=156214&action=edit picture of dialog box SUMMARY *** The New File Setup dialog wording states 'click Next' but there is no 'Next' button to push. *** STEPS TO REPRODUCE 1. launch a new install of KMyMoney 2. Go thru configuration 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.
[kmymoney] [Bug 465695] New: Incomplete transaction type list for Mutual Funds
https://bugs.kde.org/show_bug.cgi?id=465695 Bug ID: 465695 Summary: Incomplete transaction type list for Mutual Funds Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: kmymoney@dfgh.net Target Milestone: --- SUMMARY *** Mutual Funds commonly have Long Term (LT) Capital Gains and Short Term (ST) Capital Gains distributions and offer the possibilities of Reinvesting those moneys. Currently only Dividends and Reinvest Dividends are listed as choices of Fund disbursements. These transactions are important to differentiate as their tax handling is different. *** STEPS TO REPRODUCE 1. Characterize the transaction type for mutual funds 2. 3. OBSERVED RESULT transaction type list missing: -Long Term (LT) Capital Gains -Short Term (ST) Capital Gains -Reinvest Long Term (LT) Capital Gains -Reinvest Short Term (ST) Capital Gains EXPECTED RESULT transaction type list includes the missing 4 types 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.
[plasmashell] [Bug 464996] Resurrection of bug 422111
https://bugs.kde.org/show_bug.cgi?id=464996 Bob changed: What|Removed |Added CC||bobfun...@gmail.com --- Comment #1 from Bob --- Created attachment 156215 --> https://bugs.kde.org/attachment.cgi?id=156215&action=edit Screenshot of the failed condition This is when the bug has occurred. The brightness icon is here instead of the battery, and the tool tip reports batteries are unavailable. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464996] Resurrection of bug 422111
https://bugs.kde.org/show_bug.cgi?id=464996 --- Comment #2 from Bob --- Created attachment 156216 --> https://bugs.kde.org/attachment.cgi?id=156216&action=edit Screenshot of the failed condition This one has the tooltip -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464996] Resurrection of bug 422111
https://bugs.kde.org/show_bug.cgi?id=464996 --- Comment #3 from Bob --- I'm seeing the same thing on my system so I thought I would try to add my findings here... SUMMARY I am also seeing the missing battery applet bug described here and in 422111 on the latest version of plasmashell (5.26.5). The bug is very sporadic/random in nature but can be recurrently triggered with enough attempts. STEPS TO REPRODUCE Start a desktop session from a tty (i.e. with the startplasma-x11 xinit script). If the battery applet shows up normally, log out back to tty and launch the x11 session again until it occurs. The bug also shows up when starting the session from a display manager like sddm. I just used the tty method because it was quicker to repeatedly launch sessions. Note: The bug only triggers on new session startups. Simply restarting plasmashell in an already running session will not cause it. Note that it is highly random to trigger. I have observed up to 24 attempts until it triggers the bug. Other times it takes less attempts. OBSERVED RESULT Battery icon is missing from the system tray. It is replaced by the brightness icon and the tool tip reports "No Batteries Available". This is shown in the screenshots. EXPECTED RESULT The battery level should always be reported since this is a battery powered laptop. SOFTWARE/OS VERSIONS Operating System: Slackware Live 15.0 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.11 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 Manufacturer: Dell Inc. Product Name: XPS 13 9350 ADDITIONAL INFORMATION UPower and solid-hardware5 both report the battery is present in any case. It is just the icon in plasmashell that is incorrect. When the battery icon is missing, running 'org_kde_powerdevil --replace' has no effect. When powerdevil restarts, the icon disappears and reappears as the brightness icon and still reports batteries are not available. Only restarting plasmashell returns it to normal. This bug seems related to UPower. Slackware is still packaging UPower 0.99.13 and the bug is not present with the combination of UPower 0.99.13 and Plasma 5.26.5. I've tested newer UPower versions (0.99.14 up to 0.99.20) and the bug can be triggered on all newer versions with enough login attempts. I'm not sure what happened between 0.99.13 to 0.99.14 that might cause this to trigger but it seemed related and worth mentioning. I hope this information is helpful. I can try to provide more debug output if needed but I am not experienced with the inner workings of upower, powerdevil, and plasmashell. - Bob -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 465698] New: Better handling of transaction type naming in imports
https://bugs.kde.org/show_bug.cgi?id=465698 Bug ID: 465698 Summary: Better handling of transaction type naming in imports Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: importer Assignee: kmymoney-de...@kde.org Reporter: kmymoney@dfgh.net Target Milestone: --- SUMMARY *** It's annoying that apparently the phrasing of transactions must be matched exactly when manually importing a CSV file. 'Dividend Reinvestment' is not the same as 'Reinvest Dividend' and thus import fails requiring a manual editing of every transaction in the import file. It would be great if a popup could be implemented that would allow the user to specify/select what the transaction type is from the KMM display list and then remember that for the duration of the import or perhaps longer. Given the decision not to support cash in an investment account which is contrary to almost all investment accounts I have, intelligent importing of mixed transactions from those accounts would be very nice to support. Since the program knows of the association of investment and brokerage accounts from when they were created, give the importer the ability to direct a line item to either the investment or brokerage account. *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT import fails EXPECTED RESULT user can map the import file transaction types to what the program has defined, greatly decreasing user frustration with the import process 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.
[kmymoney] [Bug 465695] Incomplete transaction type list for Mutual Funds
https://bugs.kde.org/show_bug.cgi?id=465695 --- Comment #2 from Bob --- (In reply to Jack from comment #1) > You can use different categories for long and short term cap gains (and I > even have another set for tax deferred accounts.) I think the transactions > don't need different inherent types - you get a dividend of some sort and > you either get the cash or use it to buy additional shares. The dividend > could be interest, dividends, long or short term capital gains > distributions. Using different Categories is sufficient to allow you to > prepare the reports you need to prepare your taxes. > Separately, it is known that Investments needs a major overhaul, but that is > not high on the current priority list. Right now the basics of capital > gains are not really handled by KMM. I'm actually working on accumulating > all the various things that need to be dealt with, which are now not really > addressed. I'll add all this to the list, but nothing is likely to happen > in the near future. Thanks for the feedback on the submission and roadmap expectations. While I agree that a high level category of distributions can include dividends, special dividends, stocks/company spin outs and the various capital gains would obviously be preferred. As a brand new user, I guess I am highlighting the obvious. As I get deeper into it, I certainly agree that Investments needs to be better, I have some other feedback as I struggle getting my data into the program, should I write those up as individual bug/wishlist items - what is preferred? Some are usability, others are feature support - futures and options categories, etc. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464996] Resurrection of bug 422111
https://bugs.kde.org/show_bug.cgi?id=464996 --- Comment #4 from Bob --- I updated to the latest plasma release and can still trigger this battery applet bug after enough login/logout cycles. Here's the "About" copy paste, for the record: Operating System: Slackware Live 15.0 KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.12 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 Manufacturer: Dell Inc. Product Name: XPS 13 9350 The bug is the same: A random chance that upon login, the battery applet thinks there's no battery and only shows the icon and controls for screen brightness/keyboard brightness instead. The tooltip over the "battery applet" in this state reports "No Batteries Available". This would seem that batterymonitor thinks there's no batteries, even though UPower reports 'IsPresent' as true, along with solid-hardware5 reporting "Battery.present = true (bool)" when looking at the details of my battery. Somehow there is a very small chance the applet gets the wrong information at session startup and stays that way until plasmashell is restarted. Seems like a timing issue but I dont understand enough about how the applet gets its data to make a proper guess. If there's anything else I can supply please let me know. Everything seems to report a present and functional battery except the applet. Upower and soild reports arn't anything to look at because they report a present battery and charge status as normal. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 466051] New: focus lost when typing in Indicator boxes when creating import profile
https://bugs.kde.org/show_bug.cgi?id=466051 Bug ID: 466051 Summary: focus lost when typing in Indicator boxes when creating import profile Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: ux-ui Assignee: kmymoney-de...@kde.org Reporter: kmymoney@dfgh.net Target Milestone: --- Created attachment 156475 --> https://bugs.kde.org/attachment.cgi?id=156475&action=edit screenshot of issue SUMMARY *** When configuring a new CSV Profile, Focus is lost when typing in the 'Indicator for Credit/Debit' boxes after typing each character. Cursor moves to the top left field of the input file and typed characters replace that content. *** STEPS TO REPRODUCE 1. create a new input profile for a CSV file 2. start typing a new keyword in the 'Indicator for Credit' or 'Indicator for Debit' entry boxes (noticed in the Amount tab) OBSERVED RESULT notice that the first character is correctly displayed and further characters appear in the row 1 column 1 input file EXPECTED RESULT all characters typed show up in the box in which they are typed SOFTWARE/OS VERSIONS Windows: 10 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.
[kmymoney] [Bug 466052] New: Define global configurable default formatting settings for such things as dates, thousands and decimal separators, etc.
https://bugs.kde.org/show_bug.cgi?id=466052 Bug ID: 466052 Summary: Define global configurable default formatting settings for such things as dates, thousands and decimal separators, etc. Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: ux-ui Assignee: kmymoney-de...@kde.org Reporter: kmymoney@dfgh.net Target Milestone: --- SUMMARY *** It is annoying to always get an error when creating new import profile when the typical US date format of M-D-Y in CSV files is at odds with the program default Y-M-D Can the format settings that are typically region dependent be added to the Settings/Configure KMM dialog someplace? Keeping the ability to override the default is fine, but it would be much friendlier to have a programmable default. *** 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.
[plasmashell] [Bug 464996] Resurrection of bug 422111
https://bugs.kde.org/show_bug.cgi?id=464996 --- Comment #5 from Bob --- In regular use I have a non-systemd system and plasmashell and powerdevil get started via their /etc/kde/xdg/autostart/ scripts. They are not always started in the same order on my system. Sometimes they are closer together, sometimes further apart, sometimes in reverse order. It would seem that on some of these occasions there is a timing that hits this bug. With that in mind, I managed to reproduce this bug from a running plasma session by opening konsole and running the following as my test user: # /usr/lib64/libexec/org_kde_powerdevil --replace & /usr/bin/plasmashell --replace Most of the time the two will restart as normal. However on rare occasion it will start with the bugged batterymonitor applet where it fails to report about my laptop's battery. Racing the two programs this way seems to trigger it as well, although only on rare occasion. The plasmashell console spew after the --replace command was is same everytime when the battery applet is working normally. When the applet gets bugged, the only difference is that plasmashell console will output the following: file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/ui/CompactRepresentation.qml:61:17: Unable to assign [undefined] to int This line gets emitted when clicking on the icon in the system tray when the battery icon that should be there is bugged and replaced with the display brightness icon instead. I am not a kde/plasma expert so its hard to know what to look into next here. Any insight on what to try next from a dev would be appreciated. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464996] Resurrection of bug 422111
https://bugs.kde.org/show_bug.cgi?id=464996 --- Comment #6 from Bob --- As an addon to my last comment, that line: file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/ui/CompactRepresentation.qml:61:17: Unable to assign [undefined] to int Also gets emitted periodically from plasmashell while the battery applet is bugged, probably due to periodic battery discharge updates in the backend somewhere. Seems like battery information is being sent to the applet, but once its in the bugged state it will not update otherwise. The only thing that clears it is a restart of plasmashell so the applet reloads to get the proper data. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451481] Unable to delete cached webdavs credentials, potentially causing disabled accounts
https://bugs.kde.org/show_bug.cgi?id=451481 bob changed: What|Removed |Added CC||b...@labhost.nohost.me --- Comment #2 from bob --- Same issue here, no idea where the credential are stored. Another thing to add, accessing a webdav on the same server with a different username don't work. Dolpin uses the same cached username. No way of removing or editing cached credential. Please help! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441904] KWin 5.22.5 regression on NVIDIA: Black screen when putting on/taking off full screen a previously maximized window.
https://bugs.kde.org/show_bug.cgi?id=441904 Bob changed: What|Removed |Added CC||bobfun...@gmail.com --- Comment #22 from Bob --- I'm seeing this same bug on my Linux system with NVIDIA graphics. Selecting either of the OpenGL compositor backends causes a fullscreen youtube video to become a black screen. It only happens when switching from an already maximized browser window into fullscreen mode. I also tested reverting the code from this commit as other users here have mentioned: https://invent.kde.org/plasma/kwin/-/commit/f432ba7821cea2302d040c8bfc7e3cb7d9540874 After rebuilding kwin-5.22.5, the problem is gone. I am not familiar with kwin's coding so its difficult to offer a suggestion for fixing this other than reverting that change. Operating System: Slackware Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 Kernel Version: 5.14.11 Graphics Platform: X11 Processors: 8 x Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz Memory: 16GB Graphics Processor: NVIDIA GeForce GTX 1660 SUPER -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441904] KWin 5.22.5 regression on NVIDIA: Black screen when putting on/taking off full screen a previously maximized window.
https://bugs.kde.org/show_bug.cgi?id=441904 --- Comment #23 from Bob --- (In reply to Bob from comment #22) > I'm seeing this same bug on my Linux system with NVIDIA graphics. Selecting > either of the OpenGL compositor backends causes a fullscreen youtube video > to become a black screen. It only happens when switching from an already > maximized browser window into fullscreen mode. > > I also tested reverting the code from this commit as other users here have > mentioned: > https://invent.kde.org/plasma/kwin/-/commit/ > f432ba7821cea2302d040c8bfc7e3cb7d9540874 > > After rebuilding kwin-5.22.5, the problem is gone. I am not familiar with > kwin's coding so its difficult to offer a suggestion for fixing this other > than reverting that change. > > Operating System: Slackware Linux > KDE Plasma Version: 5.22.5 > KDE Frameworks Version: 5.87.0 > Qt Version: 5.15.3 > Kernel Version: 5.14.11 > Graphics Platform: X11 > Processors: 8 x Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz > Memory: 16GB > Graphics Processor: NVIDIA GeForce GTX 1660 SUPER I just tried out the newly released plasma version 5.23.0 and do not have this bug anymore (using OpenGL 2.0). Going to be sticking to that version now. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 430324] Support for libinput backend missing, touch feature tweaks and mapping not good on xf86-input-wacom
https://bugs.kde.org/show_bug.cgi?id=430324 Bob changed: What|Removed |Added CC||arkon...@yahoo.com --- Comment #1 from Bob --- Best approach is to split handling of the tablet. Touch will be handled by libinput, stylus by xf86-wacom: Create a file named /etc/X11/xorg.conf.d/90-libinput-wacom.conf with the following contents, and then reboot: ``` Section "InputClass" Identifier "libinput Wacom touchpad override class" MatchUSBID "056a:*" MatchDevicePath "/dev/input/event*" MatchIsTouchpad "true" Driver "libinput" EndSection ``` Source: https://github.com/linuxwacom/xf86-input-wacom/issues/28#issuecomment-420737038 There is one issue, if you have a libinput touchpad, that will be replaced in KDE settings with the Wacom Touchpad (I'm about to create a bug report for that). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414315] Touchpad select dropdown is disabled even if more than one touchpad is present
https://bugs.kde.org/show_bug.cgi?id=414315 Bob changed: What|Removed |Added CC||arkon...@yahoo.com --- Comment #7 from Bob --- Same for me: Touchpad 'Devices' drop-down disabled with multiple libinput touch devices in X using libinput driver. STEPS TO REPRODUCE 1. Plug >1 libinput touch devices 2. Open System Settings -> Input Devices -> Touchpad 3. Attempt to select alternative device using 'Device' drop-down OBSERVED RESULT 'Device' drop-down is disabled / greyed out. EXPECTED RESULT All compatible devices listed and selectable. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Also reported here: https://forum.kde.org/viewtopic.php?f=17&t=166738&p=442399#p442399 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439941] New: Plasmashell crash - theme related?
https://bugs.kde.org/show_bug.cgi?id=439941 Bug ID: 439941 Summary: Plasmashell crash - theme related? Product: plasmashell Version: 5.12.9 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bobboer1...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.9) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 5.4.0-77-generic x86_64 Distribution: Ubuntu 18.04.5 LTS -- Information about the crash: - Custom settings of the application: On Kubuntu 20.04.2 LTS with Ubuntu 18.04 (Bionic) Workspace theme: ant-dark. I suspect the different workspace theme might be the culprit? The crash can be reproduced every time. -- 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 0x7fe817f61d80 (LWP 2777))] Thread 19 (Thread 0x7fe728995700 (LWP 3526)): [KCrash Handler] #6 0x7fe815998640 in QSGSimpleTextureNode::texture() const () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fe74c997963 in () at /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kquickcontrolsaddons/libkquickcontrolsaddonsplugin.so #8 0x7fe811e5166f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fe815a1aa30 in QQuickWindowPrivate::renderSceneGraph(QSize const&) () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7fe8159c5bbc in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x7fe8159caac8 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x7fe811c4417d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fe810dc56db in start_thread (arg=0x7fe728995700) at pthread_create.c:463 #14 0x7fe81153f71f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7fe70efc9700 (LWP 3121)): #0 0x7fe810dcbad3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5636ddd5fcd4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fe810dcbad3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5636ddd5fc80, cond=0x5636ddd5fca8) at pthread_cond_wait.c:502 #2 0x7fe810dcbad3 in __pthread_cond_wait (cond=0x5636ddd5fca8, mutex=0x5636ddd5fc80) at pthread_cond_wait.c:655 #3 0x7fe811c455ab in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe8159ca6a8 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7fe8159cab0a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fe811c4417d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fe810dc56db in start_thread (arg=0x7fe70efc9700) at pthread_create.c:463 #8 0x7fe81153f71f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7fe70f7fe700 (LWP 3095)): #0 0x7fe810dcbad3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fe7fc00c034) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fe810dcbad3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7fe7fc00bfe0, cond=0x7fe7fc00c008) at pthread_cond_wait.c:502 #2 0x7fe810dcbad3 in __pthread_cond_wait (cond=0x7fe7fc00c008, mutex=0x7fe7fc00bfe0) at pthread_cond_wait.c:655 #3 0x7fe811c455ab in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe8159ca6a8 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7fe8159cab0a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fe811c4417d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fe810dc56db in start_thread (arg=0x7fe70f7fe700) at pthread_create.c:463 #8 0x7fe81153f71f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7fe70700 (LWP 3063)): #0 0x7fe810dcbad3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5636da65b540) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fe810dcbad3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5636da65b4f0, cond=0x5636da65b518) at pthread_cond_wait.c:502 #2 0x7fe810dcbad3 in __pthread_cond_wait (cond=0x5636da65b518, mutex=0x5636da65b4f0) at pthread_cond_wait.c:655 #3 0x7fe811c455ab in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe8159ca6a8 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7fe8159cab0a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fe811c4417d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fe810dc56db in start_thread (arg=0x7fe70700) at pthread_create.c:463 #8 0x7fe81153f71f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thre
[digikam] [Bug 412894] Import window causes digiKam to hang in macOS
https://bugs.kde.org/show_bug.cgi?id=412894 --- Comment #10 from Bob --- It will be several weeks before I can update and test this release, as requested in todays email from Gilles/bugzilla. I’m in Covid retreat in a place with very weak internet service until late fall. Thanks for all the work that you did in the new release. On Tue, Dec 31, 2019 at 3:19 PM Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=412894 > > --- Comment #6 from Maik Qualmann --- > The Import tool was designed to display images from cameras or memory > cards. So > for a few thousand images. But not for hard drives with tens of thousands > of > images. The thumbnail model cannot process this large number of images > without > a database and is getting slower and slower. > > Maik > > -- > 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.
[colord-kde] [Bug 417157] Colord-kde not working on KDE Neon and Kubuntu 20.04LTS
https://bugs.kde.org/show_bug.cgi?id=417157 Bob changed: What|Removed |Added CC||bob.caut...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473083] New: Appimage has no titlebar under Wayland
https://bugs.kde.org/show_bug.cgi?id=473083 Bug ID: 473083 Summary: Appimage has no titlebar under Wayland Classification: Applications Product: digikam Version: 8.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Portability-Interroperability Assignee: digikam-bugs-n...@kde.org Reporter: arkon...@yahoo.com Target Milestone: --- SUMMARY *** The 8.1.0 appimage has no titlebar under Wayland. *** STEPS TO REPRODUCE 1. I tried launching with: QT_QPA_PLATFORM=wayland ./Applications/digiKam-8.1.0-x86-64.appimage In the log output I see the messages 'unknown: EGL not available' and 'unknown: Unhandled container to remove : Digikam::DigikamApp' 2. I then tried launching with: QT_QPA_PLATFORM=wayland-egl ./Applications/digiKam-8.1.0-x86-64.appimage Digikam failed to launch. 3. I then tried: QT_QPA_PLATFORM=xcb ./Applications/digiKam-8.1.0-x86-64.appimage Digikam launched normally, with a titlebar. OBSERVED RESULT When run without amendment the appimage creates a window without a titlebar. EXPECTED RESULT The appimage should run without modification under Wayland and create a window with a titlebar. SOFTWARE/OS VERSIONS Ubuntu 23.04 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473083] Appimage has no titlebar under Wayland
https://bugs.kde.org/show_bug.cgi?id=473083 --- Comment #2 from Bob --- Thanks for the response. I am running a Wayland session. I am running other appimages without issue: BambuStudio_ubuntu-v01.07.02.51-20230804223010.AppImage kdenlive-23.04.3-x86_64.AppImage UltiMaker-Cura-5.4.0-linux-modern.AppImage Bob -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 348104] Remove all tags from selected image(s)
https://bugs.kde.org/show_bug.cgi?id=348104 Bob changed: What|Removed |Added CC||arkon...@yahoo.com --- Comment #6 from Bob --- Is there any way to call this new function in the app? I am running the 8.1.0 appimage but haven't been able to find one yet. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 348104] Remove all tags from selected image(s)
https://bugs.kde.org/show_bug.cgi?id=348104 --- Comment #7 from Bob --- Nevermind, I hadn't checked the code thoroughly enough, found it! Thanks :-) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473083] Appimage has no titlebar under Wayland
https://bugs.kde.org/show_bug.cgi?id=473083 --- Comment #4 from Bob --- It's a good thought and the same occurred to me, but having tried all the shortcut combinations I could think of and resetting the Digikam config files, I haven't been able to find any setting that's hiding the titlebar. I installed KDE system settings to see if there was anything there, but the dialogue is all but empty as I have no KDE components installed. Also, I have since concluded that it couldn't be this: 1. I've never had KDE/Plasma installed on this system. 2. The app has a titlebar when launched with QT_QPA_PLATFORM=xcb I think (2) strongly suggests that this isn't a misconfiguration on my system. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473083] Appimage has no title-bar under Wayland: add Qt plugin wayland-decoration-client.
https://bugs.kde.org/show_bug.cgi?id=473083 --- Comment #6 from Bob --- Yes I'm using Gnome on Wayland. That does sound like it might be the issue. I was aware there are some differences in the way Window decorations are handled under Wayland but didn't know the details, thanks for the explanation. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 388935] Unable to import investment account transaction with .csv
https://bugs.kde.org/show_bug.cgi?id=388935 b...@mroczka.com changed: What|Removed |Added CC||b...@mroczka.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473083] Appimage has no title-bar under Wayland: add Qt plugin wayland-decoration-client.
https://bugs.kde.org/show_bug.cgi?id=473083 --- Comment #8 from Bob --- I've just tried the linked 8.2 appimage, it still launches without a titlebar I'm afraid. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473083] Appimage has no title-bar under Wayland: add Qt plugin wayland-decoration-client.
https://bugs.kde.org/show_bug.cgi?id=473083 --- Comment #10 from Bob --- Inconclusive, that one doesn't even want to start on Ubuntu (23.10) I'm afraid: ``` ./digikam-master-381-linux-gcc-x86_64.AppImage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. --to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. -- Detected host Linux ubuntu-64-23.10 -- AppImage mounted directory: /tmp/.mount_digikaHnSI0k Check library libudev.so.0 Check library libxcb-dri3.so.0 Check library libcrypto.so.1.1 Check library libssl.so.1.1 Check library libnss3.so Check library libnssutil3.so Check library libsmime3.so Check library libpango-1.0.so.0 Check library libpangocairo-1.0.so.0 Check library libgmodule-2.0.so.0 -- Preloading shared libs: :/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0:/usr/lib/x86_64-linux-gnu/libnss3.so:/usr/lib/x86_64-linux-gnu/libnssutil3.so:/usr/lib/x86_64-linux-gnu/libsmime3.so:/usr/lib/x86_64-linux-gnu/libpango-1.0.so.0:/usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0:/usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 digikam: symbol lookup error: /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0: undefined symbol: g_string_free_and_steal Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. QSocketNotifier: Can only be used with threads started with QThread /tmp/.mount_digikaHnSI0k/AppRun.wrapped: symbol lookup error: /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_proxy_marshal_flags ``` -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 441324] Ease the process of closing an investment brokerage account.
https://bugs.kde.org/show_bug.cgi?id=441324 b...@mroczka.com changed: What|Removed |Added CC||b...@mroczka.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 462558] Wish: I wish for smaller configurable vertical line spacing in Kate
https://bugs.kde.org/show_bug.cgi?id=462558 --- Comment #3 from Bob --- (In reply to Waqar Ahmed from comment #2) > This is a won't fix. 1.0 is the default value that the underlying font gives > us. If you want less, then you should change the font to behave that way. If > the editor provides a way to do this, it will just wreck the UI. Understood. Thanks for looking into this, Waqar. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 461291] New: Keyboard shortcuts definitions using the Numeric Keypad keys are not possible
https://bugs.kde.org/show_bug.cgi?id=461291 Bug ID: 461291 Summary: Keyboard shortcuts definitions using the Numeric Keypad keys are not possible Classification: I don't know Product: kde Version: unspecified Platform: OpenSUSE OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: grim.der.rea...@gmail.com Target Milestone: --- I would like to bind single keys from the numpad as shortcuts, which was possible with opensuse15.1 (and not anymore since 15.2) STEPS TO REPRODUCE: Example with Dolphin version 22.08.2 – set a keyboard shortcut to duplicate a file (or any other action): Duplicate file set to «NumPad + 7» doesn't work. Duplicate file set to «Shift + NumPad + 7» doesn't work. Duplicate file set to «Crtl + NumPad + 7» doesn't work. Duplicate file set to «Crtl + Shift + NumPad + 7» doesn't work. Duplicate file set to «Crtl + Ü» does work. Duplicate file set to «Crtl + 7» does work – (Keyboard “7” – not NumPad “7”). OBSERVED RESULT Currently, KDE Plasma will not allow shortcuts definitions using the Numeric Keypad keys. EXPECTED RESULT Use a shortcut with a single key from the numeric keypad without adding a 'Crtl +' or 'Shift +' SOFTWARE/OS VERSIONS NAME="openSUSE Tumbleweed" # VERSION="20221030" -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 421686] Skrooge Homebrew formula build error
https://bugs.kde.org/show_bug.cgi?id=421686 --- Comment #3 from Bob --- I'm afraid I didn't - please see my updates here: https://www.reddit.com/r/kde/comments/gldjml/skrooge_formula_for_homebrew/ Currently I'm working around this by running Skrooge in a Docker image, with connection through a browser using XPRA. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 267277] configurable delay for autohide/show of panels
https://bugs.kde.org/show_bug.cgi?id=267277 Bob changed: What|Removed |Added CC||arkon...@yahoo.com --- Comment #64 from Bob --- This is also an issue when using Barrier KVM. If a panel resides on an edge between 2 adjacent screens, it always unhides whenever moving from one screen to the other. For reasons unknown this causes the cursor to jump halfway across the destination screen every few times. The only solution atm is to move the panel to a different screen edge. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 371055] crash while attempting to update account / download bank transactions
https://bugs.kde.org/show_bug.cgi?id=371055 --- Comment #8 from b...@mroczka.com --- Please close the ticket. I am no longer seeing this issue. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 462251] New: kdesrc-build kde-pim throws DBUS error inside kdepim-docker instance
https://bugs.kde.org/show_bug.cgi?id=462251 Bug ID: 462251 Summary: kdesrc-build kde-pim throws DBUS error inside kdepim-docker instance Classification: Developer tools Product: kdesrc-build Version: Git Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mp...@kde.org Reporter: kdebugs.20.gordo...@spamgourmet.com Target Milestone: --- SUMMARY kdesrc-build kde-pim throws DBUS error inside kdepim-docker instance STEPS TO REPRODUCE 1. Download kubuntu latest iso and install into a new VirtualBox VM instance 2. Follow steps from https://community.kde.org/KDE_PIM/Docker 3. Finally execute most critical step (from section "Running the Docker container"): run.sh $HOME/kdepim-dev OBSERVED RESULT bob029345@bob029345-VirtualBox:~/kdepim-docker$ ./run.sh $HOME/kdepim-dev dbus at unix:abstract=/tmp/dbus-gXoBJ4oY8w,guid=282d241d1cd3b89b30ee8ac66381124a dbus at 27 dbus killed, starting again started dbus neon@367a8b8badc3:~$ sudo apt update Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease Hit:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:3 http://archive.ubuntu.com/ubuntu jammy-backports InRelease Hit:4 http://security.ubuntu.com/ubuntu jammy-security InRelease Get:5 http://archive.neon.kde.org/unstable jammy InRelease [173 kB] Hit:6 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy InRelease Fetched 173 kB in 1s (127 kB/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. W: http://archive.neon.kde.org/unstable/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details. neon@367a8b8badc3:~$ sudo apt full-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. neon@367a8b8badc3:~$ kdesrc-build kde-pim ~/kdesrc-build ~ The signatures feature is experimental at /home/neon/kdesrc-build/modules/ksb/Util/LoggedSubprocess.pm line 139. The signatures feature is experimental at /home/neon/kdesrc-build/modules/ksb/Util/LoggedSubprocess.pm line 165. The signatures feature is experimental at /home/neon/kdesrc-build/modules/ksb/Util/LoggedSubprocess.pm line 189. The signatures feature is experimental at /home/neon/kdesrc-build/modules/ksb/Util/LoggedSubprocess.pm line 200. The signatures feature is experimental at /home/neon/kdesrc-build/modules/ksb/Util/LoggedSubprocess.pm line 217. The global configuration file is stored in the old location. It will still be processed correctly, however, it's recommended to move it to the new location. Please move ~/.kdesrc-buildrc to ~/kdepim/home/config/kdesrc-buildrc The global data file is stored in the old location. It will still be processed correctly, however, it's recommended to move it to the new location. Please move ~/.kdesrc-build-data to ~/.local/state/kdesrc-build-data Cloning sysadmin-repo-metadata Encountered an error in the execution of the script. --> org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory Please submit a bug against kdesrc-build on https://bugs.kde.org/ Your logs are saved in file:///home/neon/kdepim/logs/2022-11-25-01 ~ neon@367a8b8badc3:~$ EXPECTED RESULT The kde run.sh script should execute without any issue as this is done in a Docker container SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.10 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.0-23-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-2500K CPU @ 3.30GHz Memory: 7.8 GiB of RAM Graphics Processor: llvmpipe Manufacturer: innotek GmbH Product Name: VirtualBox System Version: 1.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 489856] New: collection scanner fails/no files displayed
https://bugs.kde.org/show_bug.cgi?id=489856 Bug ID: 489856 Summary: collection scanner fails/no files displayed Classification: Applications Product: amarok Version: 3.0.1 Platform: Ubuntu OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Collections/Local Assignee: amarok-bugs-d...@kde.org Reporter: b...@mroczka.com CC: ralf-eng...@gmx.de Target Milestone: kf5 SUMMARY When I attempt to scan my local audio files the scanner completes but no files are shown in the local music browser. I attempted to run the scanner from command line with same options and it finishes successfully so it is not clear what the underlying issue is. STEPS TO REPRODUCE 1. add folder to scan 2. 3. OBSERVED RESULT No audio files displayed EXPECTED RESULT The scanner to allow searching of local audio file collection. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 22.04.4 LTS Amarok Version 3.0.1-git KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 462558] New: Wish: I wish for smaller configurable vertical line spacing in Kate
https://bugs.kde.org/show_bug.cgi?id=462558 Bug ID: 462558 Summary: Wish: I wish for smaller configurable vertical line spacing in Kate Classification: Applications Product: kate Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: bob872...@hotmail.com Target Milestone: --- Created attachment 154238 --> https://bugs.kde.org/attachment.cgi?id=154238&action=edit Comparison of vertical line spacing of Kate vs Textpad SUMMARY For me, there is too much vertical whitespace between lines for the same TTF font Courier New (as a simple comparison font) I would like the option to set a vertical whitespace less than the current minimum value of "1.0" in Configure Kate I have shown the differences in attached image: KateNeon_vs_TextpadWin7.png Background context: This might be more general for linux font rendering which always seems to prefer lots of whitespace which I am not pleased about. This could be Konsole, text editors, Konquerer or KDE titlebars and tool bars. KDE and Linux always seems to have a lot of vertical whitespace used for: title bar area, application menu, application toolbar, statusbar etc. Again, this is so apparent in my attachment as the "title bar area, application menu, application toolbar" vertical size for Kate vs Textpad is about double for Kate. In an era when non-casual users are desktop/laptop users with 16:10 or 16:9 aspect screens, it's annoying. I get that you want to support touch control on mobile, but I don't want a mobile OS for use on my desktop. I have a mouse, a keyboard, a high DPI screen and I would prefer to use all of that precious vertical space to the maximum effect when programming, reading documentation etc. STEPS TO REPRODUCE 1. Navigate to Kate -> Settings Menu -> Configure Kate -> Appearance Tab -> Line Height Multiplier 2. Click the down arrow as much as possible for "Line Height Multiplier" setting 3. You cannot go below a multiplier of 1.0 OBSERVED RESULT "1.0" is the arbitrary minimum value EXPECTED RESULT I want to go lower than 1.0. I would experiment and check results, but I want to get rid of most of the vertical whitespace area in between lines in the editor regardless of font choice. For this, I would suggest a minimum of zero? SOFTWARE/OS VERSIONS Windows: 7 Professional SP1 Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.26.80 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 5.15.0-53-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-2500K CPU @ 3.30GHz Memory: 7.8 GiB of RAM Graphics Processor: SVGA3D; build: RELEASE; LLVM; Manufacturer: innotek GmbH Product Name: VirtualBox System Version: 1.2 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 462558] Wish: I wish for smaller configurable vertical line spacing in Kate
https://bugs.kde.org/show_bug.cgi?id=462558 Bob changed: What|Removed |Added Attachment #154238|0 |1 is obsolete|| --- Comment #1 from Bob --- Created attachment 154239 --> https://bugs.kde.org/attachment.cgi?id=154239&action=edit Comparison of vertical line spacing of Kate vs Textpad -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 400353] New: All channels pixelData is Blue channel
https://bugs.kde.org/show_bug.cgi?id=400353
Bug ID: 400353
Summary: All channels pixelData is Blue channel
Product: krita
Version: 4.1.5
Platform: MS Windows
OS: MS Windows
Status: REPORTED
Severity: normal
Priority: NOR
Component: Scripting
Assignee: krita-bugs-n...@kde.org
Reporter: chockablock...@outlook.com
Target Milestone: ---
Can only read and write to Blue channel from Node::channels() list, no matter
which channel is accessed (Channel::name() works correctly however).
STEPS TO REPRODUCE
1. Create new document (something small, say 2x2 pixels)
2. Fill with yellow (255, 255, 0)
3. Run the following script:
from krita import *
from PyQt5.QtCore import QByteArray, QRect
doc = Krita.instance().activeDocument()
layers = doc.rootNode().childNodes()
channels = layers[0].channels()
greenChan = channels[1]
print(greenChan.name()) # Prints 'Green'
rect = greenChan.bounds()
# Print out 1
for chan in channels:
print("Channel: " + chan.name())
px = chan.pixelData(rect)
print(px)
val = int(128)
pxData = greenChan.pixelData(rect)
pxData.fill(val.to_bytes(1, byteorder='little'))
greenChan.setPixelData(pxData, rect)
# Print out 2
for chan in channels:
print("Channel: " + chan.name())
px = chan.pixelData(rect)
print(px)
doc.refreshProjection()
OBSERVED RESULT
Print out 1 in above script prints all \x00s for all channels
Print out 2 in above script prints all \x80s for all channels
Image is pale yellow (255, 255, 128)
EXPECTED RESULT
Print out 1 should print \x00 for Blue channel and \xFF for other channels
Print out 2 should print \x00 for Blue, \x80 for Green and \xFF for Red/Alpha
Image should be orange (255, 128, 0)
SOFTWARE VERSIONS
(available in About System)
Krita
Version: 4.1.5
Qt
Version (compiled): 5.9.3
Version (loaded): 5.9.3
OS Information
Build ABI: x86_64-little_endian-llp64
Build CPU: x86_64
CPU: x86_64
Kernel Type: winnt
Kernel Version: 6.1.7601
Pretty Productname: Windows 7 SP 1 (6.1)
Product Type: windows
Product Version: 7sp1
OpenGL Info
**OpenGL not initialized**
ADDITIONAL INFORMATION
Same behaviour occurs in Krita 4.1.3.
Same behaviour occurs no matter which channel is accessed
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 407949] New: Group By Time uses groups by minute not second
https://bugs.kde.org/show_bug.cgi?id=407949 Bug ID: 407949 Summary: Group By Time uses groups by minute not second Product: digikam Version: 6.1.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Albums-Group Assignee: digikam-bugs-n...@kde.org Reporter: arkon...@yahoo.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Select 2 photos with Date Taken timestamp a second apart 2. Choose Group -> Group By Time 3. OBSERVED RESULT 2 images with timestamps 2016:03:18 15:52:15 2016:03:18 15:52:16 get grouped together. 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 407949] Group By Time uses groups by minute not second
https://bugs.kde.org/show_bug.cgi?id=407949 --- Comment #2 from Bob --- Apologies, rushed that post - additional details below. SUMMARY Digikam Group By Time groups images by nearest minute, not nearest second. STEPS TO REPRODUCE 1. Select 2 photos with Date Taken timestamp a second apart 2. Choose Group -> Group By Time 3. OBSERVED RESULT 2 images with timestamps 2016:03:18 15:52:15 2016:03:18 15:52:16 get grouped together. EXPECTED RESULT Images a second or more apart should not be grouped SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 19.04 (5.0.0-15-generic SMP x86_64) KDE Plasma Version: Plasma 5.15.5 from Kubuntu backports KDE Frameworks Version: 5.57.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407949] Group By Time uses groups by minute not second
https://bugs.kde.org/show_bug.cgi?id=407949 --- Comment #3 from Bob --- Apologies again, didn't expect/realise someone had already replied thanks for the quick response! I had read elsewhere that only images where only grouped within a second of each other. If it's 2 seconds, is there a way for the user to reduce that? My use-case: I only want photos with identical timestamps grouped (RAW & JPEG of the same shot). With grouping as it is I get different shots taken manually in quick succession or burst shots grouped together. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407949] Group By Time uses groups by minute not second
https://bugs.kde.org/show_bug.cgi?id=407949 --- Comment #5 from Bob --- If that is the intended behaviour then it is also working on my system, the images are less than 2 seconds apart. That was a misunderstanding on my part. The bug can be closed, I may put in a feature request instead for some level of adjustment to the group time range in settings. Thanks again for the help. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407949] Group By Time uses groups by minute not second
https://bugs.kde.org/show_bug.cgi?id=407949 Bob changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 400353] All channels pixelData is Blue channel
https://bugs.kde.org/show_bug.cgi?id=400353 --- Comment #4 from Bob --- I've downloaded the nightly build that contains the above commits, and while it works for the provided example, it fails on others, especially on straight copying one channel to another. Channel pixelData now appears to be four times longer than needed (A 2x2 image will now return a QByteArray with 16 bytes rather than 4). Channel data for non-blue channels seems to be offsets of blue channel as well: A 2x2 image will print out (for each channel) Blue: b'\x00\x00\x00\xYY\x00\x00\x00\xYY\x00\x00\x00\xYY\x00\x00\x00\xYY' Green: b'\x00\x00\x00\xYY+1\x00\x00\x00\xYY+1\x00\x00\x00\xYY+1\x00\x00\x00\xYY+1' Red: b'\x00\x00\x00\xYY+2\x00\x00\x00\xYY+2\x00\x00\x00\xYY+2\x00\x00\x00\xYY+2' Alpha: b'\x00\x00\x00\xYY+3\x00\x00\x00\xYY+3\x00\x00\x00\xYY+3\x00\x00\x00\xYY+3' where YY+Z can overflow into the byte before it. e.g., If the image has xFF blue, the alpha channel will be four copies of \x00\x00\x01\x02 This overflowing also affects the filling. If we have a white 2x2 image, and just simply copy the blue channel to the red with rect = QRect(0,0,doc.width(),doc.height()) channels[2].setPixelData(channels[0].pixelData(rect), rect) the image should stay white but becomes three teal pixels and a white pixel. It also appears can't retrieve channel data for any channel but blue. Also, while I believe it's just a manifestation of the above overflowing, copying the blue channel into another channel on a larger image causes an odd stretching and wrapping effect (see attachments) --- Comment #5 from Bob --- Created attachment 116176 --> https://bugs.kde.org/attachment.cgi?id=116176&action=edit Copying blue channel from this image -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 400353] All channels pixelData is Blue channel
https://bugs.kde.org/show_bug.cgi?id=400353 --- Comment #4 from Bob --- I've downloaded the nightly build that contains the above commits, and while it works for the provided example, it fails on others, especially on straight copying one channel to another. Channel pixelData now appears to be four times longer than needed (A 2x2 image will now return a QByteArray with 16 bytes rather than 4). Channel data for non-blue channels seems to be offsets of blue channel as well: A 2x2 image will print out (for each channel) Blue: b'\x00\x00\x00\xYY\x00\x00\x00\xYY\x00\x00\x00\xYY\x00\x00\x00\xYY' Green: b'\x00\x00\x00\xYY+1\x00\x00\x00\xYY+1\x00\x00\x00\xYY+1\x00\x00\x00\xYY+1' Red: b'\x00\x00\x00\xYY+2\x00\x00\x00\xYY+2\x00\x00\x00\xYY+2\x00\x00\x00\xYY+2' Alpha: b'\x00\x00\x00\xYY+3\x00\x00\x00\xYY+3\x00\x00\x00\xYY+3\x00\x00\x00\xYY+3' where YY+Z can overflow into the byte before it. e.g., If the image has xFF blue, the alpha channel will be four copies of \x00\x00\x01\x02 This overflowing also affects the filling. If we have a white 2x2 image, and just simply copy the blue channel to the red with rect = QRect(0,0,doc.width(),doc.height()) channels[2].setPixelData(channels[0].pixelData(rect), rect) the image should stay white but becomes three teal pixels and a white pixel. It also appears can't retrieve channel data for any channel but blue. Also, while I believe it's just a manifestation of the above overflowing, copying the blue channel into another channel on a larger image causes an odd stretching and wrapping effect (see attachments) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412894] Import window causes digiKam to hang in macOS
https://bugs.kde.org/show_bug.cgi?id=412894 Bob changed: What|Removed |Added CC||jenne...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412894] Import window causes digiKam to hang in macOS
https://bugs.kde.org/show_bug.cgi?id=412894 --- Comment #3 from Bob --- I've also had this bug consistently over the last 2 versions of Digikam and MacOS. I let it try to comp[lete for 2 days, and no progress. After the 2-day test, my OS was corrupted, Safari and Apple App Store (and possibly other apps) caused system exceptions (attempt to execute invalid instruction). Reinstall of MaxOS fixed Safari and App Store, but Digikam, and Digikam after reinstall failed as before. This is my first bug report, but I'll try to attach Activity force quit reports. I have also consistently filed reports with Apple when offered. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412894] Import window causes digiKam to hang in macOS
https://bugs.kde.org/show_bug.cgi?id=412894 --- Comment #4 from Bob --- Activity Monitor reports create apparently garbage pdf files which are too big to attach. I'll pursue this one with Apple, hopefully in parallel with Digikam fix process. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412894] Import window causes digiKam to hang in macOS
https://bugs.kde.org/show_bug.cgi?id=412894 --- Comment #5 from Bob --- Created attachment 124791 --> https://bugs.kde.org/attachment.cgi?id=124791&action=edit text report from force quit of hung import DigiKam not responding -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412894] Import window causes digiKam to hang in macOS
https://bugs.kde.org/show_bug.cgi?id=412894 --- Comment #7 from Bob --- OK, I can understand that. Could it be a little more defensive? Maybe: Check the size of the target and if too big ask for a folder? Or just come back with a “too big” dialog? There may actually be a bug there, too. Please consider the following: 1. When I let it run for 3 days, it apparently corrupted the OS. Safari and Apple App Store started crashing with “invalid instruction codes. 2. On my system, it seems to generate multiple identities for mounted disks remembered from previous instances. Most of the phantom disks show “fail to connect” dialog. The phantoms don’t seem to agree exactly with information I see in finder or disk utility. Could there be a file system interface issue that’s making it worse? On Tue, Dec 31, 2019 at 3:19 PM Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=412894 > > --- Comment #6 from Maik Qualmann --- > The Import tool was designed to display images from cameras or memory > cards. So > for a few thousand images. But not for hard drives with tens of thousands > of > images. The thumbnail model cannot process this large number of images > without > a database and is getting slower and slower. > > Maik > > -- > 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.
[skrooge] [Bug 421686] New: Skrooge Homebrew formula build error
https://bugs.kde.org/show_bug.cgi?id=421686
Bug ID: 421686
Summary: Skrooge Homebrew formula build error
Product: skrooge
Version: 2.20.0
Platform: Homebrew (macOS)
OS: macOS
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: guillaume.deb...@gmail.com
Reporter: arkon...@yahoo.com
CC: steph...@mankowski.fr
Target Milestone: ---
SUMMARY
I am trying to create a Homebrew formula for Skrooge on Mac. The Macports
version is out of date and Macports itself seems to be in decline. However the
build currently fails.
STEPS TO REPRODUCE
1. Install homebrew on Mac.
2. Add the following local formula
desc "Skrooge is a personal finance manager powered by KDE that aims to be
simple and intuitive. Skrooge allows you to keep track of your expenses and
income, categorize them, and build reports of them."
homepage "https://skrooge.org/";
url "https://download.kde.org/stable/skrooge/skrooge-2.20.0.tar.xz";
sha256 "3c58c54ad048b03608fde0b794de0cd3a83d0b5bd43c1d033c5dc8739f755365"
head "git://anongit.kde.org/skrooge.git"
depends_on "cmake" => :build
depends_on "kf5-extra-cmake-modules" => :build
depends_on "ninja" => :build
depends_on "qt"
depends_on "KDE-mac/kde/kf5-breeze-icons"
depends_on "KDE-mac/kde/kf5-kdesignerplugin"
depends_on "KDE-mac/kde/kf5-knewstuff"
depends_on "KDE-mac/kde/kf5-knotifyconfig"
depends_on "sqlcipher"
depends_on "pkg-config"
depends_on "qca"
depends_on "grantlee"
depends_on "libofx"
depends_on "KDE-mac/kde/kf5-kross" => :optional
def install
args = std_cmake_args
args << "-DBUILD_TESTING=OFF"
args << "-DKDE_INSTALL_QMLDIR=lib/qt5/qml"
args << "-DKDE_INSTALL_PLUGINDIR=lib/qt5/plugins"
args << "-DCMAKE_INSTALL_BUNDLEDIR=#{bin}"
args << "-DSKG_WEBENGINE=ON"
mkdir "build" do
system "cmake", "-G", "Ninja", "..", *args
system "ninja"
system "ninja", "install"
prefix.install "install_manifest.txt"
end
# Extract Qt plugin path
qtpp = `#{Formula["qt"].bin}/qtpaths --plugin-dir`.chomp
system "/usr/libexec/PlistBuddy",
"-c", "Add :LSEnvironment:QT_PLUGIN_PATH string
\"#{qtpp}\:#{HOMEBREW_PREFIX}/lib/qt5/plugins\"",
"#{bin}/skrooge.app/Contents/Info.plist"
end
def post_install
system HOMEBREW_PREFIX/"bin/update-mime-database",
HOMEBREW_PREFIX/"share/mime"
mkdir_p HOMEBREW_PREFIX/"share/skrooge"
ln_sf HOMEBREW_PREFIX/"share/icons/breeze/breeze-icons.rcc",
HOMEBREW_PREFIX/"share/skrooge/icontheme.rcc"
end
def caveats
<<~EOS
You need to take some manual steps in order to make this formula work:
"$(brew --repo kde-mac/kde)/tools/do-caveats.sh"
EOS
end
test do
assert `"#{bin}/skrooge.app/Contents/MacOS/skrooge" --help | grep --
--help` =~ /--help/
end
end
3. Install the formula with 'brew install skrooge'
OBSERVED RESULT
==> Downloading https://download.kde.org/stable/skrooge/skrooge-2.20.0.tar.xz
Already downloaded:
/Users/bob/Library/Caches/Homebrew/downloads/3326bdb6158519a6a569fd3ff6e43a4ae34309244126d4d91ebb3de6be4fb86e--skrooge-2.20.0.tar.xz
==> cmake -G Ninja .. -DBUILD_TESTING=OFF -DKDE_INSTALL_QMLDIR=lib/qt5/qml
-DKDE_INSTALL_PLUGINDIR=lib/qt5/plugins
-DCMAKE_INSTALL_BUNDLEDIR=/usr/local/Cellar/skrooge/2.20.0/bin
==> ninja
Last 15 lines from /Users/bob/Library/Logs/Homebrew/skrooge/02.ninja:
class QMetaProperty;
^
../plugins/generic/skg_monthly/grantlee_filters/skgdocumentfilter.cpp:142:67:
error: calling 'property' with incomplete return type 'QMetaProperty'
table += QStringLiteral("") %
metaObject->property(i).name() % "" % val.toString() % "";
^~~
/usr/local/opt/qt/include/QtCore/qobjectdefs.h:373:19: note: 'property'
declared here
QMetaProperty property(int index) const;
^
/usr/local/opt/qt/include/QtCore/qobjectdefs.h:285:7: note: forward declaration
of 'QMetaProperty'
class QMetaProperty;
^
2 errors generated.
[193/725] Automatic MOC for target skg_statistic
[194/725] Building CXX object
plugins/generic/skg_monthly/grantlee_filters/CMakeFiles/grantlee_skgfilters.dir/skgobjectfilter.cpp.o
ninja: build stopped: subcommand failed.
EXPECTED RESULT
Skrooge built and installed.
SOFTWARE/OS VERSIONS
macOS: 10.15.1
KDE Plasma (homebrew-kde):
KDE Plasma Version: 5.70.0
KDE Frameworks Version: 5.70.0
Qt Version: 5.14.2
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 374686] HTML Gallery tool must support modern HTML5 tags
https://bugs.kde.org/show_bug.cgi?id=374686 Bob changed: What|Removed |Added CC||bobsons...@yahoo.co.uk --- Comment #3 from Bob --- Hello, Chris. I've just created a new HTML gallery theme which generates pages using HTML5, CSS3, and UTF-8. Gilles has included this new theme in the digiKam 7.0.0 project, but in the meantime you can download it and use it with digiKam 6.x.y by visiting my project page on GitLab: https://gitlab.com/Bobulous/digikam-html5-gallery-theme Let me know what you think. (And for any problems or suggestions relating to this gallery theme, please use the Issue page within GitLab.) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388476] Missing image metadata in gallery.xml
https://bugs.kde.org/show_bug.cgi?id=388476 Bob changed: What|Removed |Added CC||bobsons...@yahoo.co.uk --- Comment #1 from Bob --- I agree that it would be good to see the gallery.xml file generated with the descriptive image title (if one has been set) rather than repeating the original filename within the `collections/collection/image/title` XML element. (Would still be good to keep a dedicated element for the original filename too, though.) I hadn't spotted that the datetime was adjusted, but I agree that a new element containing the original value should be available. And, while we're on the subject of data which would be desirable when creating HTML gallery themes, I'd like to see an XML element which contains child elements holding the tags applied to each image, so that this could optionally be used in an HTML gallery. So gallery.xml would, within each image element, contain something like this: located/United-Kingdom/London/City-Of-London organised/Wiki-Loves-Monuments-2018 released/Creative-Commons_Attribution-ShareAlike-4.0-International warning/Time-Is-GMT -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 92462] Add a new option to limit amount of thumbnails per index page
https://bugs.kde.org/show_bug.cgi?id=92462 Bob changed: What|Removed |Added CC||bobsons...@yahoo.co.uk --- Comment #4 from Bob --- The current version of the HTML gallery tool does make it possible for a theme to offer the user the option to specify the number of thumbnails per index page. Whether or not this possibility is exploited depends upon the specific gallery theme, and no core change to digiKam could automatically alter this behaviour in a theme which does not support this. But there are already themes which do allow the user to specify the number of thumbnails per index page, such as the "Elegant" "Simple Rounded", and "Vanilla" themes which already come with digiKam 6.4.0, and also the new "HTML5 Responsive" theme which will be included in digiKam 7.0.0 and can in the meantime be downloaded from here: https://gitlab.com/Bobulous/digikam-html5-gallery-theme Given that this request is theme-specific and not something which can be fixed in digiKam core, can this request now be marked as resolved? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 334680] Allow to limit exported files by type-mime in html gallery
https://bugs.kde.org/show_bug.cgi?id=334680 Bob changed: What|Removed |Added CC||bobsons...@yahoo.co.uk --- Comment #1 from Bob --- In digiKam 6.4.0 (and earlier versions) you can use the "Search" tab (on the left navigation column) to create a search for a particular Album (file directory) and/or matching specific tags, and selected file type (see within the "Picture Properties" section of the search form, and where it says "File Format" click on "Any" and then change it by selecting just the file types you want to see included in the gallery). Once you've crafted a search which shows only the images of interest, type a name into the box labelled "Save Current Search" (in the Search pane on the left) and then click the diskette icon to save. Your named search will now appear within the "Searches" list, and anything within this list can be selected when you create an HTML gallery. (Select "Albums" on the very first page of the gallery tool, then select the the "Searches" tab and tick/check as many of your saved searches as you want to include in your gallery.) Using saved searches allows you very fine control over what images to include in an HTML gallery. Does this resolve your request? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388476] Missing image metadata in gallery.xml
https://bugs.kde.org/show_bug.cgi?id=388476 Bob changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 147768] Allow to include more metadata in gallery.xml
https://bugs.kde.org/show_bug.cgi?id=147768 Bob changed: What|Removed |Added CC||b...@dotcommie.net --- Comment #2 from Bob --- *** Bug 388476 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388476] Missing image metadata in gallery.xml
https://bugs.kde.org/show_bug.cgi?id=388476 Bob changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Bob --- This request actually duplicates an earlier request for additional image/collection metadata. See bug 147768. *** This bug has been marked as a duplicate of bug 147768 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 147768] Allow to include more metadata in gallery.xml
https://bugs.kde.org/show_bug.cgi?id=147768 Bob changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||bobsons...@yahoo.co.uk Ever confirmed|0 |1 --- Comment #3 from Bob --- Yes, this request is still valid even in the latest plugin (as of digiKam 6.4.0). See also bug 388476 which duplicates the request for additional image and collection metadata, but also asks for a title element which reflects the descriptive title of an image (if one has been defined). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 114216] Add a new option to export and merge more than one album in html gallery
https://bugs.kde.org/show_bug.cgi?id=114216 Bob changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED CC||bobsons...@yahoo.co.uk --- Comment #5 from Bob --- In digiKam 6.4.0 (and earlier versions) if you create a saved search which finds all images of interest to you (based on the album location/s, file types, camera models, tags, etc) then you can tell the HTML gallery tool to create a gallery based on that saved search, and each named search will go into one gallery album. This way you can collate images from multiple folders, tags, whatever, and have them all rendered as a single gallery album using the tool. I believe this should resolve the original request. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 129648] Add new option to show Exif tags in html gallery
https://bugs.kde.org/show_bug.cgi?id=129648 Bob changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||bobsons...@yahoo.co.uk Resolution|--- |WAITINGFORINFO --- Comment #2 from Bob --- As of digiKam 6.4.0 the HTML gallery plugin does write the following Exif data within the gallery.xml file made available to each theme: Canon Canon EOS R top, left 350 350 inch 28/09/2019 12:59 Centered 1/80 s F4 unavailable 160 1/83 s F4 19.0 mm 51.360615 -0.215532 71.300 (Note that where any piece of data is not defined for a particular image, the value `unavailable` will be shown within the corresponding XML element.) Does this resolve your request? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 305167] Add back filenames in html gallery
https://bugs.kde.org/show_bug.cgi?id=305167 Bob changed: What|Removed |Added CC||bobsons...@yahoo.co.uk Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Bob --- Hello, Jaan. As of digiKam 6.4.0 (and earlier versions) the HTML gallery plugin does create a gallery.xml file which contains the original filename (with extension) for each image: JO2A2472.JPG Interior of Lumley Chapel, Cheam 2019-09-28T12:44:42 This means that a gallery theme does have the option to display the filename below the thumbnails on the image list pages, and it's up to each theme designer (and style within a theme) to decide whether or not to label the thumbnails this way. Of the HTML gallery themes which come with digiKam 6.4.0, the "Classic", "Frames", "Matrix", "Simple", and "Snow" themes do show the filename (with extension) below each thumbnail. Whilst the "Floating Cards" theme shows the image caption underneath each thumbnail (which looks good for short descriptions but might be a bit awkward for lengthy captions). I find that the filenames are usually not helpful/appealing as a visual element (because my files are all named by the camera; I don't rename them with a descriptive label, because I use the caption metadata field in digiKam for that). But if you want to see filenames without extensions appear below thumbnails then the only way you're likely to achieve this is to create your own theme and generate HTML and styling to make it look exactly how you need. See this very useful how-to guide for advice on customising your own theme: https://cgit.kde.org/digikam.git/tree/core/dplugins/generic/tools/htmlgallery/themes/THEME_HOWTO I'm going to mark this as resolved because gallery appearance is specific to each theme and style, and for any visual style or structure not yet available the possibility exists to create your own. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 181107] Add tooltip for the "X-HTML Parameter" in themes
https://bugs.kde.org/show_bug.cgi?id=181107 Bob changed: What|Removed |Added Ever confirmed|0 |1 CC||bobsons...@yahoo.co.uk Status|REPORTED|CONFIRMED --- Comment #3 from Bob --- Yes, this request is still valid as of the HTML gallery plugin included with digiKam 6.4.0. At the moment there is no way for a theme author to convey useful information about a gallery parameter. A tooltip would be nice, but better would be a dedicated frame/box within the gallery parameters dialog, which shows informative text for the currently focused parameter field. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 136389] Add new option to show image date and time in html gallery
https://bugs.kde.org/show_bug.cgi?id=136389 Bob changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||bobsons...@yahoo.co.uk --- Comment #3 from Bob --- The HTML gallery plugin which comes with digiKam 6.4.0 (and earlier versions) already makes it possible for a gallery theme to generate HTML which includes the digiKam datetime for the image, and/or the Exif datetime (if defined for the image). Whether or not the datetime is displayed below the thumbnails is dependent upon the gallery and applied visual style. Most themes do not choose to display this information below thumbnails, but some themes do. For example, I've just created a new "HTML5 Responsive" theme which comes with four styles, and the "Feed" style does show the digiKam datetime below each thumbnail. (It takes the value from the image element, not from the exif elements. But the two values always appear to be synchronised in the examples I've seen.) If you want to see a gallery generated using a different structure, layout, or visual style, then your best bet is to create your own gallery theme by following this how-to guide: https://cgit.kde.org/digikam.git/tree/core/dplugins/generic/tools/htmlgallery/themes/THEME_HOWTO Given that the digiKam HTML gallery plugin does now support this ability, I'm marking this request as resolved. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 88323] Add new option to show file info in html gallery
https://bugs.kde.org/show_bug.cgi?id=88323 Bob changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO CC||bobsons...@yahoo.co.uk Resolution|--- |WAITINGFORINFO --- Comment #3 from Bob --- Hello, Ferdinand. As of digiKam 6.3.0 there does not appear to be a "File Info" window, only a "File Properties" pane within the "Properties" tab. The "File Properties" contains only filename, folder path, modification date, file size, and (in Linux) file owner and file permissions. The filename is already made available to the HTML gallery themes, and the other data wouldn't really apply to the generated HTML gallery (because the file paths would have changed, the file sizes would differ for the thumbnails and large images, and the file owner/permissions would not really apply). Can you clarify what additional information you are hoping to see made available to HTML gallery themes? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 130107] Add watermark to photos in html gallery
https://bugs.kde.org/show_bug.cgi?id=130107
Bob changed:
What|Removed |Added
CC||bobsons...@yahoo.co.uk
Status|REPORTED|CONFIRMED
Ever confirmed|0 |1
--- Comment #1 from Bob ---
The HTML gallery plugin does not currently offer a way to watermark the
thumbnails and/or large images it produces for the gallery.
As a workaround, you can use digiKam to add all of the images you want in the
gallery to a new queue ("Item" menu, then "Add to New Queue"). Then
double-click the "Add Watermark" tool and adjust its settings to suit, then in
the "Target" tab (bottom-left pane of the queue window) untick "Use Original
Album", and choose an empty folder (ideally create a new folder with the "New
Album" button and call it something like "BatchQueueOutput"). Then run the
queue and you'll get a folder with watermarked images which you can select for
use with the HTML gallery tool.
But this is not ideal because it's quite a few additional steps, and because it
would make it harder to create multi-album galleries without a fair bit of
extra work.
So adding a watermark option to the HTML gallery plugin would be a better
solution.
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 147768] Allow to include more metadata in gallery.xml
https://bugs.kde.org/show_bug.cgi?id=147768 Bob changed: What|Removed |Added CC||frederico.pf...@gmail.com --- Comment #4 from Bob --- *** Bug 136682 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 136682] Add tags as comment for each photo in html gallery
https://bugs.kde.org/show_bug.cgi?id=136682 Bob changed: What|Removed |Added Status|REPORTED|RESOLVED CC||bobsons...@yahoo.co.uk Resolution|--- |DUPLICATE --- Comment #7 from Bob --- As of digiKam 6.3.0 it is still the case that the HTML gallery tool does not add write any data about digiKam tags to the gallery.xml file. This improvement, plus a request for additional metadata, is also seen in bug 147768, so I'm marking this as a duplicate. *** This bug has been marked as a duplicate of bug 147768 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 181112] Add "X-HTML Parameter" file to select an item in html gallery
https://bugs.kde.org/show_bug.cgi?id=181112 Bob changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||bobsons...@yahoo.co.uk --- Comment #2 from Bob --- As of digiKam 6.3.0 the HTML gallery plugin does not offer the ability to define a file-select parameter type within the themeName.desktop file. However, it would need to be decided whether adding this ability would make sense. Giving a user the option to select a custom CSS file would be interesting until the user needs to make custom image resources available, and then it's not clear how the HTML gallery parameters interface would make that possible (because the gallery interface would have no idea how many files would be needed, so it wouldn't be able to offer parameter fields would be needed). If a user wishes to see custom CSS in their generated galleries, it's probably better that they read the how-to guide: https://cgit.kde.org/digikam.git/tree/core/dplugins/generic/tools/htmlgallery/themes/THEME_HOWTO and create their own custom theme or style. (Once they've created a custom theme in their home directory, it will continue to be available to them in future runs of the digiKam HTML gallery tool, and will be a lot easier to apply then specifying file paths for stylesheets and image resources.) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 137626] Add more controls to generate html gallery
https://bugs.kde.org/show_bug.cgi?id=137626
Bob changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED|CONFIRMED
CC||bobsons...@yahoo.co.uk
--- Comment #6 from Bob ---
I believe that Beat's request could now be considered resolved, as the current
HTML gallery plugin (as of digiKam 6.3.0) offers many more themes and styles,
most of which offer customisation options.
Christian's request in Comment 1 is still unresolved because even though the
HTML gallery tool does generate a gallery.xml file containing the captions
("comments") and capture datetime, it does not yet write the image tags. This
enhancement has been requested in bug 147768.
Michael's requests could be considered resolved from a core code point of view
because the HTML gallery tool does make it possible to keep the
up/previous/next links visible at the top of the page. (And JavaScript
libraries already allow image zooming.) But at the moment none of the available
themes actually do make the up/previous/next bar remain visible.
Michael, I've just created a new theme which comes with four visual styles.
Currently none of them make the up/previous/next bar stay in view, but give the
new theme a try:
https://gitlab.com/Bobulous/digikam-html5-gallery-theme
and if you like any of the four visual styles which come with this theme let me
know and I'll see whether it's viable to make the nav bar stick to the top of
the window. (Please raise any suggestions/problems on that GitLab site
directly.)
If none of these styles appeals to you, then the best bet for you is to read
the how-to guide:
https://cgit.kde.org/digikam.git/tree/core/dplugins/generic/tools/htmlgallery/themes/THEME_HOWTO
and create your own theme.
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 92462] Add a new option to limit amount of thumbnails per index page
https://bugs.kde.org/show_bug.cgi?id=92462 Bob changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #5 from Bob --- Marking as resolved, as this has been fixed for some time, and I realise that the original reporter is no longer in the CC list for this bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 334680] Allow to limit exported files by type-mime in html gallery
https://bugs.kde.org/show_bug.cgi?id=334680 Bob changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Bob --- Marking this as resolved because digiKam has supported this for some time, and because I see that the original reporter is no longer in the CC list. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 205406] Add Javascript to scaling images in html gallery [patch]
https://bugs.kde.org/show_bug.cgi?id=205406 Bob changed: What|Removed |Added Status|REPORTED|RESOLVED CC||bobsons...@yahoo.co.uk Resolution|--- |FIXED --- Comment #6 from Bob --- Several of the themes available with the HTML gallery tool (as of digiKam 6.3.0) already support JavaScript widgets which display the large image so that it is scaled to fit the screen. Additionally, I've just created a new theme "HTML5 Responsive" which uses responsive HTML5 and CSS3 styling so that neither the thumbnails nor the large images will exceed the width of the screen, making it suitable for use on desktop and mobile devices. Take a look: https://gitlab.com/Bobulous/digikam-html5-gallery-theme For these reasons I'm marking this request as resolved. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 395793] New: qif export date range ignored
https://bugs.kde.org/show_bug.cgi?id=395793 Bug ID: 395793 Summary: qif export date range ignored Product: kmymoney Version: 5.0.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: exporter Assignee: kmymoney-de...@kde.org Reporter: b...@mroczka.com Target Milestone: --- The export to qif file is not working as expected. When attempting to specify a date range the resulting output file contains all account transactions instead of those that fall within the specified date range. I have found that it sometimes works if I type in a new file that does not already exist. If the output file does exist there is no prompt to overwrite and the output always contains all transactions in the account. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 395793] qif export date range ignored
https://bugs.kde.org/show_bug.cgi?id=395793 --- Comment #1 from b...@mroczka.com --- Created attachment 113539 --> https://bugs.kde.org/attachment.cgi?id=113539&action=edit QIF Export dialog -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 395793] qif export date range ignored
https://bugs.kde.org/show_bug.cgi?id=395793 --- Comment #2 from b...@mroczka.com --- Comment on attachment 113539 --> https://bugs.kde.org/attachment.cgi?id=113539 QIF Export dialog Not sure is this is related to the issue but the "Account to export" dialog has a very large number of duplicate entries. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 330356] Panel auto-hide stops working after using desktop for a while.
https://bugs.kde.org/show_bug.cgi?id=330356 b...@mroczka.com changed: What|Removed |Added CC||b...@mroczka.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 350948] git master 2015-08-04 - changing project framerate does not update number of frames in source clips
https://bugs.kde.org/show_bug.cgi?id=350948 Bob changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|FIXED |--- CC||arkon...@yahoo.com --- Comment #14 from Bob --- There seems to be a regression of this bug in v17 (17.12.0). I created a 1080p @ 29fps project into which I imported clips of 720p @ 59fps. Having created a lengthy edit, I then changed the project settings to 720p @ 59fps to match the clips. This caused all the edit in/out points to shift to completely different points in the clips. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 375391] New: Kmymoney crashes after attempting to create new account
https://bugs.kde.org/show_bug.cgi?id=375391 Bug ID: 375391 Summary: Kmymoney crashes after attempting to create new account Product: kmymoney4 Version: 4.8.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: b...@mroczka.com Target Milestone: --- Application: kmymoney (4.8.0) KDE Platform Version: 4.14.22 Qt Version: 4.8.7 Operating System: Linux 4.8.0-32-generic x86_64 Distribution: Ubuntu 16.10 -- Information about the crash: I tried creating a new credit card account but after clicking OK after its shows the account summary the application crashes. Same thing occurs if I try to create a checking account. The crash can be reproduced every time. -- Backtrace: Application: KMyMoney (kmymoney), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f63b034a900 (LWP 4279))] Thread 2 (Thread 0x7f6394c6a700 (LWP 4280)): #0 0x7f63aa49fc8d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f63a5c55c60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f63a5c11485 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f63a5c11974 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f63a5c11aec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f63ab69b22e in QEventDispatcherGlib::processEvents (this=0x7f6398c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #6 0x7f63ab66912f in QEventLoop::processEvents (this=this@entry=0x7f6394c69c80, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f63ab669495 in QEventLoop::exec (this=this@entry=0x7f6394c69c80, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f63ab558549 in QThread::exec (this=this@entry=0x55f593264c50) at thread/qthread.cpp:538 #9 0x7f63ab6491c3 in QInotifyFileSystemWatcherEngine::run (this=0x55f593264c50) at io/qfilesystemwatcher_inotify.cpp:265 #10 0x7f63ab55ae3c in QThreadPrivate::start (arg=0x55f593264c50) at thread/qthread_unix.cpp:352 #11 0x7f63a60fa6ca in start_thread (arg=0x7f6394c6a700) at pthread_create.c:333 #12 0x7f63aa4b00af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 1 (Thread 0x7f63b034a900 (LWP 4279)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58 #7 0x7f63aa3df3ea in __GI_abort () at abort.c:89 #8 0x7f63aa3d5bb7 in __assert_fail_base (fmt=, assertion=assertion@entry=0x7f638e9dd385 "buffer", file=file@entry=0x7f638e9c156b "buffer.c", line=line@entry=1017, function=function@entry=0x7f638e9bdb00 "GWEN_Buffer_AppendString") at assert.c:92 #9 0x7f63aa3d5c62 in __GI___assert_fail (assertion=0x7f638e9dd385 "buffer", file=0x7f638e9c156b "buffer.c", line=1017, function=0x7f638e9bdb00 "GWEN_Buffer_AppendString") at assert.c:101 #10 0x7f638e921cdf in GWEN_Buffer_AppendString () from /usr/lib/libgwenhywfar.so.60 #11 0x7f638e26de41 in ?? () from /usr/lib/libaqbanking.so.35 #12 0x7f638ec2572e in KBankingPlugin::availableJobs (this=0x55f5941b0040, accountId=...) at /build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/plugins/kbanking/mymoneybanking.cpp:632 #13 0x7f63ae6bfc7b in onlineJobAdministration::canSendCreditTransfer (this=0x7f63ae92d380 ) at /build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/mymoney/onlinejobadministration.cpp:311 #14 0x55f5919299d0 in KMyMoneyApp::slotUpdateActions (this=this@entry=0x55f592addc40) at /build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/kmymoney.cpp:6407 #15 0x55f59192f03e in KMyMoneyApp::slotSelectAccount (this=this@entry=0x55f592addc40, obj=...) at /build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/kmymoney.cpp:6923 #16 0x55f59197855a in KMyMoneyApp::qt_static_metacall (_o=0x55f592addc40, _c=, _id=, _a=0x7ffc05acc7c0) at /build/kmymoney-8ALMks/kmymoney-4.8.0/obj-x86_64-linux-gnu/kmymoney/moc_kmymoney.cpp:605 #17 0x7f63ab67ef70 in QMetaObject::activate (sender=sender@entry=0x55f593063880, m=m@entry=0x55f592195e40 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc05acc7c0) at kernel/qobject.cpp:3567 #18 0x55f5919dfcb2 in KAccountsView::selectObject (this=this@entry=0x55f593063880, _t1=...) at /build/kmymoney-8ALMks/kmymoney-4.8.0/obj-x86_64-linux-gnu/kmymoney/views/moc_kaccountsview.cpp:161 #19 0x55f5919e9500 in KAccountsView::slotTabCurrentChanged (this=this@entry=0x55f593063880, index=) at /build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/views/kaccountsview.cpp:198 #20 0x55f5919ea918 in KAccountsView::slotLoadAccounts (this=this@entry=0x55f593063880) at /build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/views/kaccountsview.cpp:168 #21 0x55f5919e0e68 in KAccountsView::qt_static_metacall (_o=0x55f593063880,
[kmymoney4] [Bug 375391] Kmymoney crashes after attempting to create new account
https://bugs.kde.org/show_bug.cgi?id=375391 --- Comment #1 from b...@mroczka.com --- Here is an alternate stack dump showing a bit more debug symbols. Application: KMyMoney (kmymoney), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f986f7cf900 (LWP 9987))] Thread 2 (Thread 0x7f98540ef700 (LWP 10017)): #0 0x7f9865096992 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f9865096aec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f986ab2022e in QEventDispatcherGlib::processEvents (this=0x7f984c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #3 0x7f986aaee12f in QEventLoop::processEvents (this=this@entry=0x7f98540eec80, flags=...) at kernel/qeventloop.cpp:149 #4 0x7f986aaee495 in QEventLoop::exec (this=this@entry=0x7f98540eec80, flags=...) at kernel/qeventloop.cpp:204 #5 0x7f986a9dd549 in QThread::exec (this=this@entry=0x5583d7f31f50) at thread/qthread.cpp:538 #6 0x7f986aace1c3 in QInotifyFileSystemWatcherEngine::run (this=0x5583d7f31f50) at io/qfilesystemwatcher_inotify.cpp:265 #7 0x7f986a9dfe3c in QThreadPrivate::start (arg=0x5583d7f31f50) at thread/qthread_unix.cpp:352 #8 0x7f986557f6ca in start_thread (arg=0x7f98540ef700) at pthread_create.c:333 #9 0x7f98699350af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 1 (Thread 0x7f986f7cf900 (LWP 9987)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58 #7 0x7f98698643ea in __GI_abort () at abort.c:89 #8 0x7f986985abb7 in __assert_fail_base (fmt=, assertion=assertion@entry=0x7f9851e99385 "buffer", file=file@entry=0x7f9851e7d56b "buffer.c", line=line@entry=1017, function=function@entry=0x7f9851e79b00 "GWEN_Buffer_AppendString") at assert.c:92 #9 0x7f986985ac62 in __GI___assert_fail (assertion=0x7f9851e99385 "buffer", file=0x7f9851e7d56b "buffer.c", line=1017, function=0x7f9851e79b00 "GWEN_Buffer_AppendString") at assert.c:101 #10 0x7f9851dddcdf in GWEN_Buffer_AppendString () from /usr/lib/libgwenhywfar.so.60 #11 0x7f9851729e41 in AB_Job_new (jt=jt@entry=AB_Job_TypeTransfer, a=a@entry=0x5583d8e7d4c0) at job.c:85 #12 0x7f985173223d in AB_JobSingleTransfer_new (a=a@entry=0x5583d8e7d4c0) at jobsingletransfer.c:28 #13 0x7f98520e172e in KBankingPlugin::availableJobs (this=0x5583d8e7d830, accountId=...) at /build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/plugins/kbanking/mymoneybanking.cpp:632 #14 0x7f986db44c7b in onlineJobAdministration::canSendCreditTransfer (this=0x7f986ddb2380 ) at /build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/mymoney/onlinejobadministration.cpp:311 #15 0x5583d4ecc9d0 in KMyMoneyApp::slotUpdateActions (this=this@entry=0x5583d77aa980) at /build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/kmymoney.cpp:6407 #16 0x5583d4ed203e in KMyMoneyApp::slotSelectAccount (this=this@entry=0x5583d77aa980, obj=...) at /build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/kmymoney.cpp:6923 #17 0x5583d4f1b55a in KMyMoneyApp::qt_static_metacall (_o=0x5583d77aa980, _c=, _id=, _a=0x7ffdf66a8640) at /build/kmymoney-8ALMks/kmymoney-4.8.0/obj-x86_64-linux-gnu/kmymoney/moc_kmymoney.cpp:605 #18 0x7f986ab03f70 in QMetaObject::activate (sender=sender@entry=0x5583d7d30ff0, m=m@entry=0x5583d5738e40 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffdf66a8640) at kernel/qobject.cpp:3567 #19 0x5583d4f82cb2 in KAccountsView::selectObject (this=this@entry=0x5583d7d30ff0, _t1=...) at /build/kmymoney-8ALMks/kmymoney-4.8.0/obj-x86_64-linux-gnu/kmymoney/views/moc_kaccountsview.cpp:161 #20 0x5583d4f8c500 in KAccountsView::slotTabCurrentChanged (this=this@entry=0x5583d7d30ff0, index=) at /build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/views/kaccountsview.cpp:198 #21 0x5583d4f8d918 in KAccountsView::slotLoadAccounts (this=this@entry=0x5583d7d30ff0) at /build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/views/kaccountsview.cpp:168 #22 0x5583d4f83e68 in KAccountsView::qt_static_metacall (_o=0x5583d7d30ff0, _c=, _id=4, _a=0x7ffdf66a8b40) at /build/kmymoney-8ALMks/kmymoney-4.8.0/obj-x86_64-linux-gnu/kmymoney/views/moc_kaccountsview.cpp:94 #23 0x7f986ab03f70 in QMetaObject::activate (sender=sender@entry=0x7f986ddb1c80 , m=m@entry=0x7f986ddaf960 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3567 #24 0x7f986db49b00 in MyMoneyFile::dataChanged (this=this@entry=0x7f986ddb1c80 ) at /build/kmymoney-8ALMks/kmymoney-4.8.0/obj-x86_64-linux-gnu/kmymoney/mymoney/moc_mymoneyfile.cpp:112 #25 0x7f986dac8b2c in MyMoneyFile::commitTransaction (this=this@entry=0x7f986ddb1c80 ) at /build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/mymoney/mymoneyfile.cpp:446 #26 0x7f986dac8cc5 in MyMoneyFileTransaction::commit (this=this@entry=0x7ffdf66a8c20) at /build/kmymoney-8ALMks/kmymoney-4.8.0/kmymoney/mymoney/mymoneyfile.cpp:3227 #27 0x5583d4ee33d2 in KMyM
[kmymoney4] [Bug 375391] Kmymoney crashes after attempting to create new account
https://bugs.kde.org/show_bug.cgi?id=375391
--- Comment #2 from b...@mroczka.com ---
I found the issue. Apparently aqbanking saved an account uid file that did not
contain values or even keys for attributes such as accountNumber and bankCode
that it expects to be always there. After removing the incomplete file at
./settings/accounts/uid%3a%3a0005.conf the issue was fixed.
The incomplete file looked like this:
char provider="aqofxconnect"
int uniqueId="103421"
int accountType="0"
char country="AL"
data {
backend {
int maxPurposeLines="1"
int debitAllowed="0"
} #backend
} #data
If anyone else has this problem look for one of these files and move it out of
the .aqbanking folder to see if it resolves the issue. Hopefully this will
help others with the same issue.
--
You are receiving this mail because:
You are watching all bug changes.
[kmymoney4] [Bug 372996] KMyMoney
https://bugs.kde.org/show_bug.cgi?id=372996 b...@mroczka.com changed: What|Removed |Added CC||b...@mroczka.com --- Comment #3 from b...@mroczka.com --- Please see if the information at https://bugs.kde.org/show_bug.cgi?id=375391 helps you. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 328230] Cover fetching only works from last.fm since 2.8
https://bugs.kde.org/show_bug.cgi?id=328230 b...@mroczka.com changed: What|Removed |Added CC||b...@mroczka.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 403399] New: Konsole crashed during boot
https://bugs.kde.org/show_bug.cgi?id=403399 Bug ID: 403399 Summary: Konsole crashed during boot Product: konsole Version: 17.04.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: jrpryo...@gmail.com Target Milestone: --- Application: konsole (17.04.2) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.4.165-81-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: - What I was doing when the application crashed: boot stopped at OS select screen - grub? only 42.3 and 42.3 xen and their snapshots selectable cursor up/down not working enter booted 42.3 Konsole crashed message - Unusual behavior I noticed: other taskbar windows seem normal extra kate window as usual normally 2 konsole windows, none here packages zypper updated within last 4 days -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f818fc368c0 (LWP 3174))] Thread 3 (Thread 0x7f81789a9700 (LWP 3188)): #0 0x7f818f56330d in poll () from /lib64/libc.so.6 #1 0x7f8186f94314 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f8186f9442c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f818bb7716b in QEventDispatcherGlib::processEvents (this=0x7f816c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7f818bb24bbb in QEventLoop::exec (this=this@entry=0x7f81789a8ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:206 #5 0x7f818b95ff1a in QThread::exec (this=) at thread/qthread.cpp:500 #6 0x7f8189d24285 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7f818b9649e9 in QThreadPrivate::start (arg=0x7f8189f8cce0) at thread/qthread_unix.cpp:365 #8 0x7f81874b1724 in start_thread () from /lib64/libpthread.so.0 #9 0x7f818f56be8d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f817ad43700 (LWP 3184)): #0 0x7f818f56330d in poll () from /lib64/libc.so.6 #1 0x7f81878d43c2 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f81878d5faf in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f817d29e149 in QXcbEventReader::run (this=0xf15270) at qxcbconnection.cpp:1332 #4 0x7f818b9649e9 in QThreadPrivate::start (arg=0xf15270) at thread/qthread_unix.cpp:365 #5 0x7f81874b1724 in start_thread () from /lib64/libpthread.so.0 #6 0x7f818f56be8d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f818fc368c0 (LWP 3174)): [KCrash Handler] #6 0x7f81874bb5e0 in __lll_unlock_elision () from /lib64/libpthread.so.0 #7 0x7f818bfd712b in KSharedDataCache::Private::unlock (this=0xf769c0) at /usr/src/debug/kcoreaddons-5.32.0/src/lib/caching/kshareddatacache.cpp:1226 #8 KSharedDataCache::Private::CacheLocker::~CacheLocker (this=, __in_chrg=) at /usr/src/debug/kcoreaddons-5.32.0/src/lib/caching/kshareddatacache.cpp:1298 #9 KSharedDataCache::find (this=0xf71600, key=..., destination=destination@entry=0x7ffe2743f1f0) at /usr/src/debug/kcoreaddons-5.32.0/src/lib/caching/kshareddatacache.cpp:1580 #10 0x7f818e4e4c18 in KIconLoaderPrivate::findCachedPixmapWithPath (this=0xf75f30, key=..., data=..., path=...) at /usr/src/debug/kiconthemes-5.32.0/src/kiconloader.cpp:995 #11 0x7f818e4e5b20 in KIconLoader::loadIcon (this=0x7f818e6fcce0 <(anonymous namespace)::Q_QGS_globalIconLoader::innerFunction()::holder>, _name=..., group=group@entry=KIconLoader::Desktop, size=32, state=0, overlays=..., path_store=path_store@entry=0x0, canReturnNull=canReturnNull@entry=false) at /usr/src/debug/kiconthemes-5.32.0/src/kiconloader.cpp:1288 #12 0x7f818e4dcd60 in KIconEngine::pixmap (this=, size=..., mode=, state=) at /usr/src/debug/kiconthemes-5.32.0/src/kiconengine.cpp:100 #13 0x7f818c37ca2e in QIcon::pixmap (this=this@entry=0x7ffe2743f6c0, window=window@entry=0x0, size=..., mode=mode@entry=QIcon::Normal, state=state@entry=QIcon::Off) at image/qicon.cpp:839 #14 0x7f818c37cada in QIcon::pixmap (this=this@entry=0x7ffe2743f6c0, size=..., mode=mode@entry=QIcon::Normal, state=state@entry=QIcon::Off) at image/qicon.cpp:775 #15 0x7f817d2b62db in QXcbWindow::setWindowIcon (this=0x104bd20, icon=...) at qxcbwindow.cpp:1585 #16 0x7f818c30b333 in QWindow::setIcon (this=this@entry=0x107b950, icon=...) at kernel/qwindow.cpp:865 #17 0x7f818cadca92 in QWidgetPrivate::setWindowIcon_sys (this=this@entry=0xf76e00) at kernel/qwidget.cpp:6225 #18 0x7f818cae8587 in QWidget::setWindowIcon (this=this@entry=0xf62690, icon=...) at kernel/qwidget.cpp:6215 #19 0x7f818f83fdc9 in Konsole::MainWindow::updateWindowIcon (this=this@entry=0xf62690) at /usr/src/debug/konsole-17.04.2/src/MainWindow.cpp:277 #20 0x7f818f842e1b in Konsole::MainWindow::activeViewChang
[plasmashell] [Bug 401868] New: Plasmashell crash changing desktop icon
https://bugs.kde.org/show_bug.cgi?id=401868 Bug ID: 401868 Summary: Plasmashell crash changing desktop icon Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: sleepingspy...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. change desktop icon 2. click on other icons 3. OBSERVED RESULT plasmashell crash 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.
[plasmashell] [Bug 401868] Plasmashell crash changing desktop icon
https://bugs.kde.org/show_bug.cgi?id=401868 --- Comment #1 from Bob --- Created attachment 116738 --> https://bugs.kde.org/attachment.cgi?id=116738&action=edit Crash report Crash report -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401868] Plasmashell crash changing desktop icon
https://bugs.kde.org/show_bug.cgi?id=401868 Bob changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REPORTED --- Comment #5 from Bob --- Depends: libkf5iconthemes5 (=5.28.0-2) but 5.51.0-1 is to be installed error trying to install debug synbols breeze dark theme -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 377227] New: new install with bugs
https://bugs.kde.org/show_bug.cgi?id=377227 Bug ID: 377227 Summary: new install with bugs Product: systemsettings Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: yousuckyoujack...@gmail.com Target Milestone: --- Application: systemsettings5 (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.8.0-36-generic x86_64 Distribution: Ubuntu 16.04.2 LTS -- Information about the crash: - Unusual behavior I noticed: Well first off, this is about the 3rd time i had to install this OS. When I try to install with the OEM install. I can get in fine, run updates. But then when I run the ship to customer? so that it will have me get out of OEM mode, it would totally bonk the install. After the splash screen would apear, it would totally halt.. This is a new install where i just did live usb and installed from inside live usb and its has its problems also. - Custom settings of the application: none yet as i havent even really started using the OS. Bugs out the box. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fba6e13f8c0 (LWP 1723))] Thread 6 (Thread 0x7fba3f5f3700 (LWP 1948)): #0 0x7fba6a853b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fba677a438c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fba677a449c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fba6b1807eb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fba6b127b4a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fba6af44834 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fba698c33c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fba6af497be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fba67cc56ba in start_thread (arg=0x7fba3f5f3700) at pthread_create.c:333 #9 0x7fba6a85f82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7fba44b69700 (LWP 1947)): #0 0x7fba677a3b7b in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fba677a4307 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fba677a449c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fba6b1807eb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fba6b127b4a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fba6af44834 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fba698c33c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fba6af497be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fba67cc56ba in start_thread (arg=0x7fba44b69700) at pthread_create.c:333 #9 0x7fba6a85f82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fba48761700 (LWP 1928)): #0 0x7fba6a853b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fba677a438c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fba677a449c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fba6b1807eb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fba6b127b4a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fba6af44834 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fba698c33c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fba6af497be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fba67cc56ba in start_thread (arg=0x7fba48761700) at pthread_create.c:333 #9 0x7fba6a85f82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fba4cbd9700 (LWP 1727)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fba50b200f3 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #2 0x7fba50b1f817 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #3 0x7fba67cc56ba in start_thread (arg=0x7fba4cbd9700) at pthread_create.c:333 #4 0x7fba6a85f82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fba5c99e700 (LWP 1724)): #0 0x7fba6a853b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fba6853bc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fba6853d8d7 in xcb_wait_for_event ()
[Discover] [Bug 386015] New: Discover constant crashing when searching
https://bugs.kde.org/show_bug.cgi?id=386015 Bug ID: 386015 Summary: Discover constant crashing when searching Product: Discover Version: 5.10.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: spamhate...@gmail.com Target Milestone: --- Application: plasma-discover (5.10.5) Qt Version: 5.9.1 Frameworks Version: 5.38.0 Operating System: Linux 4.10.0-33-generic x86_64 Distribution: Ubuntu 17.10 -- Information about the crash: Main behaviour causing crash - crashed 3 times in a row searching for new programs. search terms used win ff, sound konvertor, flac. strange behaviour of empty window on right side popping up while scrolling though list with cursor. Secondary comments, Discover very unstable on my system, often crashing while updating or searching. Added artful Kubuntu Backports in sources The crash can be reproduced sometimes. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f090dd455c0 (LWP 3625))] Thread 11 (Thread 0x7f08b7bbc700 (LWP 3639)): #0 0x7f0909474901 in __GI___poll (fds=0x7f08ac002de0, nfds=1, timeout=34232) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f0903e21169 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0903e2127c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0909db449b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0909d59e3a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0909b793ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0909b7e29d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0905ce97fc in start_thread (arg=0x7f08b7bbc700) at pthread_create.c:465 #8 0x7f0909480b0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f08c5190700 (LWP 3637)): #0 0x7f0909474901 in __GI___poll (fds=0x7f08bc022840, nfds=1, timeout=19231) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f0903e21169 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0903e2127c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0909db449b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0909d59e3a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0909b793ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0909b7e29d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0905ce97fc in start_thread (arg=0x7f08c5190700) at pthread_create.c:465 #8 0x7f0909480b0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f08c66dc700 (LWP 3636)): #0 0x7f0909474901 in __GI___poll (fds=0x7f08b8002de0, nfds=1, timeout=9231) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f0903e21169 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0903e2127c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0909db449b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0909d59e3a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0909b793ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0909b7e29d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0905ce97fc in start_thread (arg=0x7f08c66dc700) at pthread_create.c:465 #8 0x7f0909480b0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f08c7fff700 (LWP 3633)): #0 0x7f0909474901 in __GI___poll (fds=0x559805c00210, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f0903e21169 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0903e21502 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f08cde65b26 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7f0903e48645 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f0905ce97fc in start_thread (arg=0x7f08c7fff700) at pthread_create.c:465 #6 0x7f0909480b0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f08cc803700 (LWP 3632)): #0 0x7f0909474901 in __GI___poll (fds=0x559805bd7a50, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f0903e21169 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0903e2127c in g_main_context_iteration () from /lib/x86_64-linux-gnu/li
[gwenview] [Bug 373405] New: Gwenview 16.08.2 fails to honor BlackListedExtensions in gwenviewrc
https://bugs.kde.org/show_bug.cgi?id=373405 Bug ID: 373405 Summary: Gwenview 16.08.2 fails to honor BlackListedExtensions in gwenviewrc Product: gwenview Version: Other (add details in bug description) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: kde.coral...@xoxy.net CC: myr...@kde.org Target Milestone: --- Gwenview 16.08.2 KDE Frameworks 5.27.0 Qt 5.6.1 xcb windowing system Problem: When browsing images, Gwenview includes .NEF files in the browse list, even when $HOME/.kde/share/config/gwenviewrc contains the following configuration: [General] HistoryEnabled=true BlackListedExtensions=NEF,new According to this page of KDE documentation: /userbase.kde.org/Gwenview/Hidden_Configuration_Options Gwenview will ignore *.NEF files when browsing a file directory. Unfortunately, that isn't happening. I have a directory full of .JPG and .NEF files and Gwenview is loading both the .JPG and .NEF files when only the .JPG files should be loaded into the list of images to view. This results in browsing twice as many photos as expected, with redundancy. Please advise if this is due to a configuration error on my part. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 342186] Global shortcuts do not work to control activity switching
https://bugs.kde.org/show_bug.cgi?id=342186 b...@mroczka.com changed: What|Removed |Added CC||b...@mroczka.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374575] "Shortcut for switching to this activity" has no effect
https://bugs.kde.org/show_bug.cgi?id=374575 b...@mroczka.com changed: What|Removed |Added CC||b...@mroczka.com -- You are receiving this mail because: You are watching all bug changes.
