[kwin] [Bug 403722] New: KDE openGL crash at startup, but after login-logout it will work fine until the next reboot.
https://bugs.kde.org/show_bug.cgi?id=403722 Bug ID: 403722 Summary: KDE openGL crash at startup, but after login-logout it will work fine until the next reboot. Product: kwin Version: 5.14.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: andythe_gr...@pm.me Target Milestone: --- Created attachment 117711 --> https://bugs.kde.org/attachment.cgi?id=117711=edit Screenshot of broken compositor When I boot my PC, the windows would either have no border, no compositing, or having a after image of the past windows as shown in the attached image. But when I re-login, it is back to normal and did not crash at all after that, until next reboot. I tried change between openGL 2.0 and 3.1 no difference. I don't have externel graphic card. I attached output of journalctl -u display-manager.service and less /var/log/Xorg.0.log in root privilege. My system is: Operating System: openSUSE Tumbleweed 20190125 KDE Plasma Version: 5.14.5 Qt Version: 5.12.0 KDE Frameworks Version: 5.54.0 Kernel Version: 4.20.2-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz Memory: 7.5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 390550] Can't resize windows due to no borders
https://bugs.kde.org/show_bug.cgi?id=390550 Rik Mills changed: What|Removed |Added CC||arco...@gmail.com --- Comment #4 from Rik Mills --- *** Bug 403696 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403696] Borderless GTK windows do not show resize handles and cannot be resized
https://bugs.kde.org/show_bug.cgi?id=403696 Rik Mills changed: What|Removed |Added Status|REPORTED|RESOLVED CC||rikmi...@kubuntu.org Resolution|--- |DUPLICATE --- Comment #1 from Rik Mills --- *** This bug has been marked as a duplicate of bug 390550 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 403456] Export to Dropbox: New Album in Dropbox not visible
https://bugs.kde.org/show_bug.cgi?id=403456 --- Comment #11 from Maik Qualmann --- New bundles for Windows from 28.01.2019 are now available. Can you check whether all folders in the list are available from the Dropbox tool? https://files.kde.org/digikam/ Maik -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 403706] RKWard crashes on startup
https://bugs.kde.org/show_bug.cgi?id=403706 --- Comment #2 from gri...@yandex.com --- (In reply to m.eik michalke from comment #1) > you need RKWard >= 0.7.0 for R 3.5, and it must be compiled for the R > version you're actually running. please see > https://rkward.kde.org/Binaries_and_Build_Scripts for more detailed > information on this. Thank you very much for the reply. I have used the package that is at: https://cran.r-project.org/bin/linux/debian/stretch-cran35/rkward_0.6.5-1~stretchcran.0_amd64.deb Therefore, I infer that the repository package of https://cran.r-project.org/bin/linux/debian/stretch-cran35/ is incorrect and the bug is r-sig-debian@ r-project.org. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 403688] make it easier to find "Save workflow" command
https://bugs.kde.org/show_bug.cgi?id=403688 caulier.gil...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||6.0.0 Resolution|--- |FIXED CC||caulier.gil...@gmail.com --- Comment #3 from caulier.gil...@gmail.com --- No problem Chris, you welcome... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 403688] make it easier to find "Save workflow" command
https://bugs.kde.org/show_bug.cgi?id=403688 --- Comment #2 from Chris --- ouch... how did I NOT see that? I swear I repeatedly opened / scanne through all available menus. Sorry, I suggest to close the issue immediately. Sorry for all the hot air. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 341589] Cannot assign tag to a split
https://bugs.kde.org/show_bug.cgi?id=341589 --- Comment #4 from Thomas Baumgart --- I use ccmake to turn it on. Or you run cmake -DENABLE_UNFINISHEDFEATURES=ON. You will have a new view at the bottom of the left pane called 'New ledger'. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 403721] New: Crashes when right-clicking in thumbnail area
https://bugs.kde.org/show_bug.cgi?id=403721 Bug ID: 403721 Summary: Crashes when right-clicking in thumbnail area Product: kphotoalbum Version: 5.4 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Thumbnail Viewer Assignee: kpab...@willden.org Reporter: robert.spo...@gmail.com Target Milestone: --- SUMMARY Application crashes when right-clicking in the thumbnail viewing area STEPS TO REPRODUCE 1. Browse images 2. Scroll down to most recent 3. right click on area where there are no thumbnails OBSERVED RESULT Program crashes EXPECTED RESULT popup menu SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: gentoo (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: 5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 403715] Dual or Two Person Control for Certificate encryption and storage
https://bugs.kde.org/show_bug.cgi?id=403715 --- Comment #1 from Andre Heinecke --- For such requirements wouldn't it be best to have a two person setup using a hardware token (e.g. an OpenPGP Smartcard) where one person has access to the token and the second person knows the PIN? Anyhow just to clarify: - You only want to have the second passphrase applied on the export. But don't want to need to enter two passphrases every time you use a key? --> In this case I would suggest to symmetrically encrypt the export with a second passphrase. So you would need both when the key should be imported somewhere. We cannot really implement technical "export" restrictions (without a hardware token where export is impossible by design) because to use the key we need to be able to unlock it and you can always just copy the encrypted key material from the local storage. -- You are receiving this mail because: You are watching all bug changes.
[flatpak-platform-plugin] [Bug 403713] QWebEngine in KDE flatpak runtime cannot play h.264 videos?
https://bugs.kde.org/show_bug.cgi?id=403713 Jan Grulich changed: What|Removed |Added CC||aleix...@kde.org, ||jgrul...@redhat.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 403720] New: Baloo crashes at KDE session start.
https://bugs.kde.org/show_bug.cgi?id=403720 Bug ID: 403720 Summary: Baloo crashes at KDE session start. Product: frameworks-baloo Version: 5.45.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: k.ohl...@gmail.com Target Milestone: --- Application: baloo_file (5.45.0) Qt Version: 5.9.4 Frameworks Version: 5.45.0 Operating System: Linux 4.12.14-lp150.12.45-default x86_64 Distribution: "openSUSE Leap 15.0" -- Information about the crash: - What I was doing when the application crashed: The crash happens immediately after I logged in to my KDE session. The crash can be reproduced every time. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe671559100 (LWP 2205))] Thread 3 (Thread 0x7fe666179700 (LWP 3389)): [KCrash Handler] #6 0x7fe66efde58c in __memmove_avx_unaligned_erms () from /lib64/libc.so.6 #7 0x7fe670562a93 in memcpy (__len=2051, __src=, __dest=) at /usr/include/bits/string_fortified.h:34 #8 Baloo::PostingCodec::decode (this=this@entry=0x7fe666178997, arr=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/codecs/postingcodec.cpp:42 #9 0x7fe670553f64 in Baloo::PostingDB::get (this=this@entry=0x7fe666178a80, term=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/postingdb.cpp:100 #10 0x7fe670560180 in Baloo::WriteTransaction::commit (this=0x5602767038e0) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/writetransaction.cpp:259 #11 0x7fe6705594c2 in Baloo::Transaction::commit (this=this@entry=0x7fe666178b90) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/transaction.cpp:262 #12 0x560274ecd6cd in Baloo::NewFileIndexer::run (this=0x5602766cfa90) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/file/newfileindexer.cpp:75 #13 0x7fe66f9c6372 in QThreadPoolThread::run (this=0x5602765d4980) at thread/qthreadpool.cpp:99 #14 0x7fe66f9c90ce in QThreadPrivate::start (arg=0x5602765d4980) at thread/qthread_unix.cpp:368 #15 0x7fe66dfd3559 in start_thread () from /lib64/libpthread.so.0 #16 0x7fe66ef7c81f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fe666c7c700 (LWP 2209)): #0 0x7fe66ef7207b in poll () from /lib64/libc.so.6 #1 0x7fe66b6591c9 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe66b6592dc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe66fbecc0b in QEventDispatcherGlib::processEvents (this=0x7fe66b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fe66fb9509a in QEventLoop::exec (this=this@entry=0x7fe666c7bca0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fe66f9c44da in QThread::exec (this=) at thread/qthread.cpp:515 #6 0x7fe670e09985 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7fe66f9c90ce in QThreadPrivate::start (arg=0x7fe671079d60) at thread/qthread_unix.cpp:368 #8 0x7fe66dfd3559 in start_thread () from /lib64/libpthread.so.0 #9 0x7fe66ef7c81f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fe671559100 (LWP 2205)): #0 0x7fe66ef7207b in poll () from /lib64/libc.so.6 #1 0x7fe66b6591c9 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe66b6592dc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe66fbecbef in QEventDispatcherGlib::processEvents (this=0x560276578d60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #4 0x7fe66fb9509a in QEventLoop::exec (this=this@entry=0x7fff34679740, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7fe66fb9d9e4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1289 #6 0x560274ec521c in main (argc=, argv=) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/file/main.cpp:104 [Inferior 1 (process 2205) detached] The reporter indicates this bug may be a duplicate of or related to bug 403483. Possible duplicates by query: bug 403483, bug 403310, bug 403282, bug 403205, bug 402787. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #303 from michel --- Hi all, "the process of scoping out" seems to hibernate. let's hope, that he can remember us, when he wakes up... ...and informs us a little about it's status. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 397313] False positive on long double "uninitialised bytes"
https://bugs.kde.org/show_bug.cgi?id=397313
--- Comment #3 from Daniel Fahlgren ---
Just to clarify. The following example shows that long double ld1 =
does not work as you normally expect an assignment to work.
#include
#include
void func1(void)
{
long double a;
memset(, 0xFF, sizeof a);
}
void func2(void)
{
long double a = 0;
char *p = (char *)
for (int i = 0; i < sizeof a; i++)
printf("%d: 0x%02x\n", i, p[i] & 0xff);
}
int main(int argc, char *argv[])
{
func1()
func2();
return 0;
}
--
You are receiving this mail because:
You are watching all bug changes.
[Falkon] [Bug 403719] New: A page on walletinvestor.com crashes the tab
https://bugs.kde.org/show_bug.cgi?id=403719 Bug ID: 403719 Summary: A page on walletinvestor.com crashes the tab Product: Falkon Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: now...@gmail.com Reporter: dgunc...@gmail.com Target Milestone: --- SUMMARY Opening https://walletinvestor.com/magazine/announcing-walletinvestors-historical-index-coins-listed-on-our-statistics-page-receive-a-rating-according-to-market-data/ works initially, but if one scrolls down (or just wait a little) the tab crashes. STEPS TO REPRODUCE 1. Open the web page 2. Wait a while or scroll down OBSERVED RESULT Failed loading page Something went wrong while loading this page. Try reloading the page or closing some tabs to make more memory available. EXPECTED RESULT SOFTWARE/OS VERSIONS Application version 3.0.1 KDE Plasma Version: 5.54.0 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 (built against 5.11.3) ADDITIONAL INFORMATION I managed to open Chromium and it displayed the page (along with 10 other tabs), so I have memory (16G). -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 401495] CTRL+Q should only close current window, not all windows
https://bugs.kde.org/show_bug.cgi?id=401495 Doncho N. Gunchev changed: What|Removed |Added CC||dgunc...@gmail.com --- Comment #10 from Doncho N. Gunchev --- I for one like and use the current behavior. I close everything with Ctrl+Q (tabs and widndows) and next time when I start Falkon it will bring back all windows and tabs. During the day I open tabs and sometimes windows with information I want to check later. I close everything, get back home and I read and close what I can one by one. I was thinking of a global KDE setting to select the behavior, but it looks like Ctrl+F4 is global shortcut and Ctrl+Q is application specific one... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 403702] Triggering "radio switch" with Fn+Home causes Meta-Key not to trigger Application Launcher
https://bugs.kde.org/show_bug.cgi?id=403702 --- Comment #2 from Martin Flöser --- X11 or Wayland -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 403718] New: The default value of the Hover action should be PreviewWindows
https://bugs.kde.org/show_bug.cgi?id=403718 Bug ID: 403718 Summary: The default value of the Hover action should be PreviewWindows Product: latte-dock Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: tr...@yandex.com Target Milestone: --- That make it consistent with Plasma panel's behavior. And that was the previous behavior of Latte too, some users have been familiar with it. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395998] can't add clips
https://bugs.kde.org/show_bug.cgi?id=395998 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 381543] Mount slewing during exposure
https://bugs.kde.org/show_bug.cgi?id=381543 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #9 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 380937] Exporting a DB with Images into csv provides an unstructured file
https://bugs.kde.org/show_bug.cgi?id=380937 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #10 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395938] Typing and erasing 3d in effects search crashes flatpak Kdenlive 18.04.2
https://bugs.kde.org/show_bug.cgi?id=395938 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 382836] Equirectangular projection
https://bugs.kde.org/show_bug.cgi?id=382836 --- Comment #6 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 382123] star hopper
https://bugs.kde.org/show_bug.cgi?id=382123 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|FIXED |WORKSFORME --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 397600] KDEnlive Settings are not persisted after re-opening app
https://bugs.kde.org/show_bug.cgi?id=397600 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 403203] akonadi server crashes on system start
https://bugs.kde.org/show_bug.cgi?id=403203 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 403188] At login, previous session restores before some other services
https://bugs.kde.org/show_bug.cgi?id=403188 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 403717] New: When multiple instances are running, render progress is not handled consistently
https://bugs.kde.org/show_bug.cgi?id=403717 Bug ID: 403717 Summary: When multiple instances are running, render progress is not handled consistently Product: kdenlive Version: 18.12.1 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: minor Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: c6kargn...@liamekaens.com Target Milestone: --- SUMMARY If multiple instances of kdenlive are running, then when you start a render job, there is a possibility that a different instance will "attach" to the job. In the instance where you started the job, the job appears in the Job Queue tab with the text "Waiting...", and the job also appears in the Job Queue tab of the other instance, and that is where the progress is actually displayed. If an instance of kdenlive is already running and rendering a job, and then a new instance of kdenlive is started, its Job Queue will not show the job from the first instance. The code appears to attach to jobs in a manner that excludes other instances. STEPS TO REPRODUCE 1. Start a render job in a kdenlive instance. 2. Start a second instance. The job from the first instance does not appear in the second instance's Job Queue. 3. Start a render job in the second instance. The job appears in the first instance's Job Queue with progress updates, and the second instance shows the job but fails to attach to it, simply displaying "Waiting..." OBSERVED RESULT Only one instance can attach to a job, and sometimes it is the wrong one. EXPECTED RESULT All instances should show all jobs and be able to receive progress information in tandem. SOFTWARE/OS VERSIONS Windows: Windows 10 1809 MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I do not have ready access to platforms other than Windows to say if the behaviour is the same or different there. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 399584] Support macOS Mojave (10.14)
https://bugs.kde.org/show_bug.cgi?id=399584 --- Comment #9 from Rhys Kidd --- (In reply to i.am.qix from comment #8) > Rhys, have you gotten a chance to look at the diff? This is blocking a lot > of our development on MacOS unfortunately, and build/dist from source isn't > a viable option for us at the moment. Hi - I have a slightly more updated work-in-progress commit here [0]. Please note, this remains *very* alpha quality. I am still not happy with the number of failing Valgrind unit tests on Mojave, so you should be very cautious before actioning a report from Valgrind on Mojave in your own code. There is the potential for many false positives and false negatives. I'll make the plea as well. If your employer or organization is reliant upon Valgrind on macOS, please consider how you could support this critically under-resourced open source project on which you are building. This is more than financial, there are a number of different ways to support important open source communities. [0] https://github.com/Echelon9/valgrind/commit/742cf660a9b6a933eec60b5791fd342325018395 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 403716] New: Spectacle
https://bugs.kde.org/show_bug.cgi?id=403716 Bug ID: 403716 Summary: Spectacle Product: Spectacle Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: ben.sim...@uts.edu.au Target Milestone: --- Application: spectacle (18.08.3 - A Dearth of Dank Memes) (Compiled from sources) Qt Version: 5.11.3 Frameworks Version: 5.52.0 Operating System: Linux 4.9.76-gentoo-r1 x86_64 Distribution: "Gentoo Base System release 2.6" -- Information about the crash: - What I was doing when the application crashed: Selected the type of screen capture to be: select rectangular area. There's 2 x 4K screens. Spectacle window was on (primary) LHS screen. Selection was about to be made on RHS second 4K screen. Crashed before the screen usually goes dim to allow dragged-rectangular selection to be made. gentoo linux Linux west.da.uts.edu.au 4.9.76-gentoo-r1 #1 SMP Tue Jan 30 18:27:33 AEDT 2018 x86_64 Intel(R) Core(TM) i5-4690 CPU @ 3.50GHz GenuineIntel GNU/Linux kde-apps/spectacle-18.08.3:5 -- Backtrace: Application: Spectacle (spectacle), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0f1f8d2780 (LWP 13059))] Thread 4 (Thread 0x7f0efb5c4700 (LWP 13158)): #0 0x7f0f19c8eb6e in socketNotifierSourceCheck (source=0x7f0ef4004820) at kernel/qeventdispatcher_glib.cpp:75 #1 0x7f0f12f79ad1 in g_main_context_check (context=context@entry=0x7f0ef4000bf0, max_priority=2147483647, fds=fds@entry=0x7f0ef4004a00, n_fds=n_fds@entry=1) at /usr/src/debug/dev-libs/glib-2.56.4/glib-2.56.4/glib/gmain.c:3735 #2 0x7f0f12f7a060 in g_main_context_iterate (context=context@entry=0x7f0ef4000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /usr/src/debug/dev-libs/glib-2.56.4/glib-2.56.4/glib/gmain.c:3899 #3 0x7f0f12f7a1cc in g_main_context_iteration (context=0x7f0ef4000bf0, may_block=may_block@entry=1) at /usr/src/debug/dev-libs/glib-2.56.4/glib-2.56.4/glib/gmain.c:3963 #4 0x7f0f19c8e51b in QEventDispatcherGlib::processEvents (this=0x7f0ef4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7f0f19c30fab in QEventLoop::exec (this=this@entry=0x7f0efb5c3e00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #6 0x7f0f19a76d7a in QThread::exec (this=) at thread/qthread.cpp:525 #7 0x7f0f1dc2e2e5 in ?? () from /usr/lib64/libQt5Qml.so.5 #8 0x7f0f19a82566 in QThreadPrivate::start (arg=0x55e0f5485750) at thread/qthread_unix.cpp:367 #9 0x7f0f1641896a in start_thread () from /lib64/libpthread.so.0 #10 0x7f0f1930891f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f0f08c00700 (LWP 13069)): #0 QMutex::unlock (this=0x55e0f5384010) at thread/qmutex.cpp:337 #1 0x7f0f19c8e416 in QMutexLocker::unlock (this=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:219 #2 QMutexLocker::~QMutexLocker (this=, __in_chrg=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:213 #3 QThreadData::canWaitLocked (this=) at ../../include/QtCore/5.11.3/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:254 #4 postEventSourcePrepare (s=0x7f0efc004ba0, timeout=timeout@entry=0x7f0f08bffc24) at kernel/qeventdispatcher_glib.cpp:259 #5 0x7f0f12f79618 in g_main_context_prepare (context=context@entry=0x7f0efc000bf0, priority=priority@entry=0x7f0f08bffcb0) at /usr/src/debug/dev-libs/glib-2.56.4/glib-2.56.4/glib/gmain.c:3474 #6 0x7f0f12f79feb in g_main_context_iterate (context=context@entry=0x7f0efc000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /usr/src/debug/dev-libs/glib-2.56.4/glib-2.56.4/glib/gmain.c:3882 #7 0x7f0f12f7a1cc in g_main_context_iteration (context=0x7f0efc000bf0, may_block=may_block@entry=1) at /usr/src/debug/dev-libs/glib-2.56.4/glib-2.56.4/glib/gmain.c:3963 #8 0x7f0f19c8e51b in QEventDispatcherGlib::processEvents (this=0x7f0efc000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #9 0x7f0f19c30fab in QEventLoop::exec (this=this@entry=0x7f0f08bffdf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #10 0x7f0f19a76d7a in QThread::exec (this=) at thread/qthread.cpp:525 #11 0x7f0f1a333de5 in ?? () from /usr/lib64/libQt5DBus.so.5 #12 0x7f0f19a82566 in QThreadPrivate::start (arg=0x7f0f1a5abd60) at thread/qthread_unix.cpp:367 #13 0x7f0f1641896a in start_thread () from /lib64/libpthread.so.0 #14 0x7f0f1930891f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f0f0c63e700 (LWP 13064)): #0 0x7f0f192fcd43 in poll () from /lib64/libc.so.6 #1 0x7f0f1d09e7f7 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f0f1d0a042a in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f0f0e7c27a9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4
[konqueror] [Bug 104338] Need to limit memory usage
https://bugs.kde.org/show_bug.cgi?id=104338 Lisa Eli Croft changed: What|Removed |Added CC||lisaelima...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 399584] Support macOS Mojave (10.14)
https://bugs.kde.org/show_bug.cgi?id=399584 i.am@gmail.com changed: What|Removed |Added CC||i.am@gmail.com --- Comment #8 from i.am@gmail.com --- Rhys, have you gotten a chance to look at the diff? This is blocking a lot of our development on MacOS unfortunately, and build/dist from source isn't a viable option for us at the moment. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 403706] RKWard crashes on startup
https://bugs.kde.org/show_bug.cgi?id=403706 m.eik michalke changed: What|Removed |Added Status|REPORTED|RESOLVED CC||bugs.kde.org@ad.geldunterga ||ng.biz Resolution|--- |NOT A BUG --- Comment #1 from m.eik michalke --- you need RKWard >= 0.7.0 for R 3.5, and it must be compiled for the R version you're actually running. please see https://rkward.kde.org/Binaries_and_Build_Scripts for more detailed information on this. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 401184] Latte Dock - Global Keyboard Shortcuts Stop Working / Multiple Entries Created
https://bugs.kde.org/show_bug.cgi?id=401184 --- Comment #13 from scum.filter+...@gmail.com --- (In reply to Michail Vourlakos from comment #12) > Dont worry I merged it for 0.8.6 so you could test when it is released Figured things out and got 0.8.75 installed - everything is working well so far. Thanks much for all your help and work! -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 377911] [Wayland] RDP doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=377911 --- Comment #11 from Andrius Štikonas --- Created attachment 117710 --> https://bugs.kde.org/attachment.cgi?id=117710=edit wayland.patch Perhaps something like this to start with. It still doesn't embed window on Wayland but at least it shows it in the external window. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 397313] False positive on long double "uninitialised bytes"
https://bugs.kde.org/show_bug.cgi?id=397313 Daniel Fahlgren changed: What|Removed |Added CC||dan...@fahlgren.se --- Comment #2 from Daniel Fahlgren --- When running with --track-origins=yes you can see where the uninitialised bytes originated from: ==7624== Uninitialised value was created by a stack allocation ==7624==at 0x10881A: main (test.c:11) which indicates a local variable in main is to blame. The problem is that the FPU stack is 80 bits wide even if sizeof(long double) returns 16. After the assignment only the first 10 bytes are initialised since floating point instructions has been used. Valgrind correctly reports the last 6 bytes as being uninitialised. If you do a memset followed by an assignment the warning will go away, like: memset(, 0, sizeof ld1); ld1 = 1.2345e+80; -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 403715] New: Dual or Two Person Control for Certificate encryption and storage
https://bugs.kde.org/show_bug.cgi?id=403715 Bug ID: 403715 Summary: Dual or Two Person Control for Certificate encryption and storage Product: kleopatra Version: 3.1.1 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: aheine...@intevation.de Reporter: robsumsi...@gmail.com CC: kdepim-b...@kde.org, m...@kde.org Target Milestone: --- SUMMARY With the increase in the requirement to meet PCI DSS and NIST and ISO 27001 and others, we have been increasingly required to store PGP Keys, SSH keys and X509 certificates with two person control. This requires at least 2 people to be involved before the private keys can be exported. I would love using Kleopatra to be able to allow 1-n control setting on certificates when stored, and if set to 2 for example, it firstly must have a 2nd person go in and set a 2nd passphrase on the certificate etc. Then when exporting, it could go into a state of Export-first approval, and then 2nd approver must put password into get the export done? Be amazing improvement? SOFTWARE/OS VERSIONS Windows: We are windows shop KDE Plasma Version: 3.1.1 KDE Frameworks Version: 5.43 Qt Version: 5.10.1 ADDITIONAL INFORMATION IF there is a way to already to this that would be great thanks? -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 377911] [Wayland] RDP doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=377911 Andrius Štikonas changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 377911] [Wayland] RDP doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=377911 Andrius Štikonas changed: What|Removed |Added CC||stiko...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403542] Login Screen, the keyboard layout displays “us” whatever the current layout until a key is pressed
https://bugs.kde.org/show_bug.cgi?id=403542 --- Comment #4 from 21na...@gmail.com --- I wrote to Debian’s bug tracking system with the tag “upstream”, I hope it is sufficient: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920483 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 341589] Cannot assign tag to a split
https://bugs.kde.org/show_bug.cgi?id=341589 --- Comment #3 from bren...@coupeware.com --- Thomas, How do you turn a feature like this on? I assume it's done as part of the cmake command but what is the correct syntax? How do you confirm that the feature is active in your new build? Thanks, Brendan Coupe On Sun, Jan 27, 2019 at 10:37 AM Thomas Baumgart wrote: > https://bugs.kde.org/show_bug.cgi?id=341589 > > Thomas Baumgart changed: > >What|Removed |Added > > >Severity|minor |wishlist > > --- Comment #2 from Thomas Baumgart --- > Work is underway. If you compile yourself, want to be a bit adventurous > and set > the ENABLE_UNFINISHEDFEATURES build variable to ON, then you can check out > a > new ledger view and a new transaction editor which among other new features > allows setting the tag per split. It is not finished and not ready for > production use yet. You can find this on the master branch of the > development. > > -- > You are receiving this mail because: > You are the assignee for the bug. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 403477] Dolphin Hangs and is Unkillble when opening folders
https://bugs.kde.org/show_bug.cgi?id=403477 --- Comment #3 from accounts+...@moochermedia.co --- These are local folders. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 403450] Sending multiple files via Bluetooth does not work
https://bugs.kde.org/show_bug.cgi?id=403450 Elvis Angelaccio changed: What|Removed |Added Product|dolphin |Bluedevil Component|general |kio-bt Assignee|dolphin-bugs-n...@kde.org |now...@gmail.com --- Comment #2 from Elvis Angelaccio --- Moving to bluedevil. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 403450] Sending multiple files via Bluetooth does not work
https://bugs.kde.org/show_bug.cgi?id=403450 Elvis Angelaccio changed: What|Removed |Added Version|unspecified |5.14.5 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 403477] Dolphin Hangs and is Unkillble when opening folders
https://bugs.kde.org/show_bug.cgi?id=403477 --- Comment #2 from Elvis Angelaccio --- Are those network or local folders? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 368287] Dolphin crashed while moving files to directory on NTFS/FAT file system owned by another user [KIO::FileCopyJob::slotResult]
https://bugs.kde.org/show_bug.cgi?id=368287 Elvis Angelaccio changed: What|Removed |Added CC||abelnicolas1...@gmail.com --- Comment #27 from Elvis Angelaccio --- *** Bug 403603 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 403603] Dolphin crashea cuando mueve archivos hacia una partición NTFS
https://bugs.kde.org/show_bug.cgi?id=403603 Elvis Angelaccio changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Elvis Angelaccio --- *** This bug has been marked as a duplicate of bug 368287 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 403690] new tab should be opened after the current tab in tab list, not at the end
https://bugs.kde.org/show_bug.cgi?id=403690 Elvis Angelaccio changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 403691] Crash when expanding and removing folders & files
https://bugs.kde.org/show_bug.cgi?id=403691 Elvis Angelaccio changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Elvis Angelaccio --- *** This bug has been marked as a duplicate of bug 380201 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 380201] Dolphin Crash when renaming and moving folders into folders.
https://bugs.kde.org/show_bug.cgi?id=380201 Elvis Angelaccio changed: What|Removed |Added CC||jeanmichael.celerier@gmail. ||com --- Comment #6 from Elvis Angelaccio --- *** Bug 403691 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 403658] Latte freezes when switching the type of application menu
https://bugs.kde.org/show_bug.cgi?id=403658 --- Comment #4 from Viorel-Cătălin Răpițeanu --- (In reply to Michail Vourlakos from comment #3) > > I wondered what the Latte dock would do > > since it locks itself right after you select an option. Wait for the launcer > > to be replaced (if that's the implementation), then lock itself up? > > Latte does not lock itself, I dont know what you are describing Really bad wording from my part. Sorry about that. What I meant is the behaviour when the panel exits 'The Dock/Panel Settings' phase. After you select 'Alternatives', the panel will exit the configuration mode even if this pop-up is still up. > > I admit however, I wasn't expecting a freeze for this case. > > > > you probably did not understand me. In my system Latte Alternative option > works fine at all cases. I can not reproduce this in my system. Please try > with different layouts and options to check if this is happening always in > your system. I've attached a video for this issue, testing with a default plasma panel and with Latte. Also, I think I've tried almost all possible configurations and this issue still reproduces. https://drive.google.com/open?id=1uj-k8twB1nUJ5KsOjIfK02yL4wpi-BVT -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 403714] Preview Pane Constantly Flashes (WebEngine issue)
https://bugs.kde.org/show_bug.cgi?id=403714 Dan changed: What|Removed |Added CC||dan.f.k...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 403714] New: Preview Pane Constantly Flashes (WebEngine issue)
https://bugs.kde.org/show_bug.cgi?id=403714 Bug ID: 403714 Summary: Preview Pane Constantly Flashes (WebEngine issue) Product: kmail2 Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: dan.f.k...@gmail.com Target Milestone: --- Application: kmail (5.10.1) Qt Version: 5.12.0 Frameworks Version: 5.54.0 Operating System: Linux 4.20.4-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: I open kmail. The preview pane flashes constantly, and is unable to preview any emails. This appears to be a bug in qt5-webengine. I can reproduce this by browsing to any URL in Konqueror when WebEngine is used, but things show fine when using KHTML. If I attempt to close Kmail when the preview pane is flashing, I get this crash. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcdfdebfb40 (LWP 3647))] Thread 26 (Thread 0x7fccf2350700 (LWP 3738)): #0 0x7fce15384ef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fce0eafc447 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #2 0x7fce0eafd16a in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #3 0x7fce0eafd252 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #4 0x7fce0eabc301 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #5 0x7fce0eabe4d7 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #6 0x7fce0eabeac4 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #7 0x7fce0eaff361 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #8 0x7fce1537ea9d in start_thread () from /usr/lib/libpthread.so.0 #9 0x7fce179bfb23 in clone () from /usr/lib/libc.so.6 Thread 25 (Thread 0x7fcdceffd700 (LWP 3737)): #0 0x7fce15384ef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fce0eafc447 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #2 0x7fce0eafd16a in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #3 0x7fce0eafd252 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #4 0x7fce0eabc301 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #5 0x7fce0eabe806 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #6 0x7fce0eabeac4 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #7 0x7fce0eaff361 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #8 0x7fce1537ea9d in start_thread () from /usr/lib/libpthread.so.0 #9 0x7fce179bfb23 in clone () from /usr/lib/libc.so.6 Thread 24 (Thread 0x7fcd796ee700 (LWP 3704)): #0 0x7fce15384afc in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fce0b9b728c in ?? () from /usr/lib/libQt5Script.so.5 #2 0x7fce0b9b72a9 in ?? () from /usr/lib/libQt5Script.so.5 #3 0x7fce1537ea9d in start_thread () from /usr/lib/libpthread.so.0 #4 0x7fce179bfb23 in clone () from /usr/lib/libc.so.6 Thread 23 (Thread 0x7fcda0ad3700 (LWP 3691)): #0 0x7fce14465424 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0 #1 0x7fce144b5faa in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #2 0x7fce144b74e6 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7fce144b762e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7fce17ee75c4 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fce17e9058c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7fce17cd45c9 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #7 0x7fce17cd59cc in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7fce1537ea9d in start_thread () from /usr/lib/libpthread.so.0 #9 0x7fce179bfb23 in clone () from /usr/lib/libc.so.6 Thread 22 (Thread 0x7fcda1da4700 (LWP 3688)): #0 0x7fce15384afc in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fce0eafc379 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #2 0x7fce0eafd178 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #3 0x7fce0eafd20f in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #4 0x7fce0eabc318 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #5 0x7fce0eabe806 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #6 0x7fce0eabeb44 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #7 0x7fce0eaff361 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #8 0x7fce1537ea9d in start_thread () from /usr/lib/libpthread.so.0 #9 0x7fce179bfb23 in clone () from /usr/lib/libc.so.6 Thread 21 (Thread 0x7fcda27fc700 (LWP 3682)): #0 0x7fce15384e5b in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fce14f56ea4 in ?? () from /usr/lib/nvidia/libGL.so.1 #2 0x7fce09bca522 in ?? () from
[flatpak-platform-plugin] [Bug 403713] New: QWebEngine in KDE flatpak runtime cannot play h.264 videos?
https://bugs.kde.org/show_bug.cgi?id=403713 Bug ID: 403713 Summary: QWebEngine in KDE flatpak runtime cannot play h.264 videos? Product: flatpak-platform-plugin Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: cos@gmail.com Target Milestone: --- SUMMARY The QWebEngine in KDE runtime can't play H.264 videos on the Internet. It seems that the support for proprietary codecs in QWebEngine is not enabled. Is it possible to enable it? See https://doc.qt.io/qt-5/qtwebengine-features.html Or if there is a license problem, is it OK to make it as a runtime plugin or as a BaseApp? STEPS TO REPRODUCE 1. Use QWebEngine in Flatpak runtime to open a website with H.264 videos OBSERVED RESULT Video cannot be played EXPECTED RESULT Video should be played SOFTWARE/OS VERSIONS Linux/KDE Plasma: LinuxMint 19.1 Mate Qt Version: 5.12 ADDITIONAL INFORMATION Flatpak runtime version: org.kde.Platform//5.12 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 403247] Markdown backend: hyperlinks across multiple lines don't work
https://bugs.kde.org/show_bug.cgi?id=403247 Albert Astals Cid changed: What|Removed |Added Latest Commit||https://commits.kde.org/oku ||lar/27b76ee7c035b9f16452c56 ||aa3ab997948ecfc7e Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Albert Astals Cid --- Git commit 27b76ee7c035b9f16452c56aa3ab997948ecfc7e by Albert Astals Cid. Committed on 28/01/2019 at 21:09. Pushed by aacid into branch 'master'. TextDocumentGenerator: Support links that span more than one line Summary: If a link spans more than one line we need one rect for each of the lines Subscribers: okular-devel Tags: #okular Differential Revision: https://phabricator.kde.org/D18303 M +13 -0core/area.cpp M +11 -0core/area.h M +16 -7core/textdocumentgenerator.cpp M +61 -0core/textdocumentgenerator_p.h https://commits.kde.org/okular/27b76ee7c035b9f16452c56aa3ab997948ecfc7e -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 403712] Update all annotations after its setting (e.g. color) has changed
https://bugs.kde.org/show_bug.cgi?id=403712 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #1 from Albert Astals Cid --- This is by design. Just think that you're using a different pen, the annotations done with the old pen won't change because of that. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 403710] baloo_file_Extractor crash at startup
https://bugs.kde.org/show_bug.cgi?id=403710 --- Comment #1 from Bruno Friedmann --- Created attachment 117708 --> https://bugs.kde.org/attachment.cgi?id=117708=edit New crash information added by DrKonqi baloo_file_extractor (5.54.0) using Qt 5.12.0 Second reboot after last Tumbleweed snapshot 20190125 same crash This time also plamashell didn't finished its startup (no desktop wallpaper plugin running) -- Backtrace (Reduced): #6 0x7ff185acabba in KFileMetaData::TagLibExtractor::extract (this=, result=0x7ffecc9725a0) at /usr/src/debug/kfilemetadata5-5.54.0-1.1.x86_64/src/extractors/taglibextractor.cpp:857 #7 0x55cff6deae6b in Baloo::App::index (this=this@entry=0x7ffecc972d10, tr=0x55cff80d3940, url=..., id=id@entry=1433818997194801) at /usr/src/debug/baloo5-5.54.0-1.1.x86_64/src/file/extractor/app.cpp:191 #8 0x55cff6decd07 in Baloo::App::processNextFile (this=0x7ffecc972d10) at /usr/src/debug/baloo5-5.54.0-1.1.x86_64/src/file/extractor/app.cpp:111 #9 0x7ff195a18ea6 in QtPrivate::QSlotObjectBase::call (a=0x7ffecc9726f0, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #10 QSingleShotTimer::timerEvent (this=0x55cff81e6bd0) at kernel/qtimer.cpp:318 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 403710] baloo_file_Extractor crash at startup
https://bugs.kde.org/show_bug.cgi?id=403710 Bruno Friedmann changed: What|Removed |Added CC||br...@ioda-net.ch -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 403712] Update all annotations after its setting (e.g. color) has changed
https://bugs.kde.org/show_bug.cgi?id=403712 alex...@gmx.net changed: What|Removed |Added CC||alex...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 403712] New: Update all annotations after its setting (e.g. color) has changed
https://bugs.kde.org/show_bug.cgi?id=403712 Bug ID: 403712 Summary: Update all annotations after its setting (e.g. color) has changed Product: okular Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: alex...@gmx.net Target Milestone: --- SUMMARY Changing the setting of an annotation tool (e.g. the notes or the marker) does not apply to earlier annotations. STEPS TO REPRODUCE Choose a specific annotation, e.g.: 1. Color an area with a rectangle in yellow 2. Change the color of this annotation tool to green 3. Color something else with this annotation tool OBSERVED RESULT The first annotation stays yellow, while the second annotation is green. EXPECTED RESULT There should be a dialogue to ask the user if all annotations by this tool shall change the color to the new setting. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.12.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 403702] Triggering "radio switch" with Fn+Home causes Meta-Key not to trigger Application Launcher
https://bugs.kde.org/show_bug.cgi?id=403702 --- Comment #1 from Matt --- (In reply to Matt from comment #0) > SUMMARY > On my Dell XPS 9370, the radio kill button is paired with the home button, > right next to my F12 key. 90% of the time, when I use that key (Fn+Home), it > kills my Meta key until I relog. > > STEPS TO REPRODUCE > 1. Hold Fn key > 2. Tap Home key > > OBSERVED RESULT > Meta key fails to trigger application launcher. Alt+F1 still works, and > other Meta assignments work too. > > > EXPECTED RESULT > Application launcher opens > > SOFTWARE/OS VERSIONS > Linux/KDE Plasma: Arch Linux 4.20.0-arch1-1-ARCH > (available in About System) > KDE Plasma Version: 5.14.5 > KDE Frameworks Version: 5.53.0 > Qt Version: 5.12.0 > > ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 403711] New: Navigation by keyboard not always works
https://bugs.kde.org/show_bug.cgi?id=403711 Bug ID: 403711 Summary: Navigation by keyboard not always works Product: Discover Version: 5.14.90 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: notux...@gmail.com Target Milestone: --- STEPS TO REPRODUCE For example: 1. Start Discover. 2. Press up/down arrows (featured apps are navigating by keyboard). 3. Select some app. 4. Press up/down arrows. OBSERVED RESULT Middle featured apps list isn't navigating by keyboard. Also after Enter key press the currently selected app page isn't showing. SOFTWARE/OS VERSIONS Operating System: KDE neon Developer Edition KDE Plasma Version: 5.15.80 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.2 Kernel Version: 4.15.0-42-generic -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 394494] support right-click on touchscreen
https://bugs.kde.org/show_bug.cgi?id=394494 Christoph Feck changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 403675] App crashes with segfault after second import
https://bugs.kde.org/show_bug.cgi?id=403675 Stephane MANKOWSKI changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/skr ||ooge/39d8b2f9b82507863a0d45 ||eeeae0bd2fe1dc3ebd Resolution|--- |FIXED --- Comment #1 from Stephane MANKOWSKI --- Git commit 39d8b2f9b82507863a0d45eeeae0bd2fe1dc3ebd by Stephane MANKOWSKI. Committed on 28/01/2019 at 20:05. Pushed by smankowski into branch 'master'. App crashes with segfault after second import M +1-0CHANGELOG M +16 -17 plugins/generic/skg_monthly/skgmonthlyplugin.cpp M +1-1skgbasegui/skgmainpanel.cpp https://commits.kde.org/skrooge/39d8b2f9b82507863a0d45eeeae0bd2fe1dc3ebd -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 403710] New: baloo_file_Extractor crash at startup
https://bugs.kde.org/show_bug.cgi?id=403710 Bug ID: 403710 Summary: baloo_file_Extractor crash at startup Product: frameworks-baloo Version: 5.54.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: br...@ioda-net.ch Target Milestone: --- Application: baloo_file_extractor (5.54.0) Qt Version: 5.12.0 Frameworks Version: 5.54.0 Operating System: Linux 4.20.2-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: the desktop was loading (autologin used here) at the same time plasma was finising it's statup (systray applet there) the crash debug was already there The crash can be reproduced sometimes. -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe518cb3940 (LWP 2854))] Thread 2 (Thread 0x7fe50b249700 (LWP 2888)): #0 g_mutex_unlock (mutex=0x7fe504000bf0) at gthread-posix.c:1355 #1 0x7fe519c544a1 in g_main_context_prepare (context=context@entry=0x7fe504000bf0, priority=priority@entry=0x7fe50b248ae0) at gmain.c:3560 #2 0x7fe519c54eeb in g_main_context_iterate (context=context@entry=0x7fe504000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3900 #3 0x7fe519c550dc in g_main_context_iteration (context=0x7fe504000bf0, may_block=may_block@entry=1) at gmain.c:3981 #4 0x7fe51bc4188b in QEventDispatcherGlib::processEvents (this=0x7fe504000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7fe51bbec02b in QEventLoop::exec (this=this@entry=0x7fe50b248c30, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7fe51ba363b6 in QThread::exec (this=this@entry=0x7fe51cc5dd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7fe51cbe3565 in QDBusConnectionManager::run (this=0x7fe51cc5dd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #8 0x7fe51ba37702 in QThreadPrivate::start (arg=0x7fe51cc5dd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361 #9 0x7fe51aef6554 in start_thread (arg=) at pthread_create.c:463 #10 0x7fe51b51bccf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fe518cb3940 (LWP 2854)): [KCrash Handler] #6 0x7fe50bcd3bba in KFileMetaData::TagLibExtractor::extract (this=, result=0x7ffdbe677d90) at /usr/src/debug/kfilemetadata5-5.54.0-1.1.x86_64/src/extractors/taglibextractor.cpp:857 #7 0x56055bea7e6b in Baloo::App::index (this=this@entry=0x7ffdbe678500, tr=0x56055d6195b0, url=..., id=id@entry=1433818997194801) at /usr/src/debug/baloo5-5.54.0-1.1.x86_64/src/file/extractor/app.cpp:191 #8 0x56055bea9d07 in Baloo::App::processNextFile (this=0x7ffdbe678500) at /usr/src/debug/baloo5-5.54.0-1.1.x86_64/src/file/extractor/app.cpp:111 #9 0x7fe51bc22ea6 in QtPrivate::QSlotObjectBase::call (a=0x7ffdbe677ee0, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #10 QSingleShotTimer::timerEvent (this=0x56055d7f3a90) at kernel/qtimer.cpp:318 #11 0x7fe51bc1791b in QObject::event (this=0x56055d7f3a90, e=) at kernel/qobject.cpp:1230 #12 0x7fe51c5de591 in QApplicationPrivate::notify_helper (this=this@entry=0x56055d4d7b90, receiver=receiver@entry=0x56055d7f3a90, e=e@entry=0x7ffdbe678200) at kernel/qapplication.cpp:3753 #13 0x7fe51c5e5b50 in QApplication::notify (this=0x7ffdbe6784f0, receiver=0x56055d7f3a90, e=0x7ffdbe678200) at kernel/qapplication.cpp:3500 #14 0x7fe51bbed359 in QCoreApplication::notifyInternal2 (receiver=0x56055d7f3a90, event=0x7ffdbe678200) at ../../include/QtCore/5.12.0/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:322 #15 0x7fe51bc40c83 in QTimerInfoList::activateTimers (this=0x56055d58b700) at kernel/qtimerinfo_unix.cpp:643 #16 0x7fe51bc4150c in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:182 #17 idleTimerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:229 #18 0x7fe519c54c85 in g_main_dispatch (context=0x7fe510004ff0) at gmain.c:3182 #19 g_main_context_dispatch (context=context@entry=0x7fe510004ff0) at gmain.c:3847 #20 0x7fe519c55048 in g_main_context_iterate (context=context@entry=0x7fe510004ff0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3920 #21 0x7fe519c550dc in g_main_context_iteration (context=0x7fe510004ff0, may_block=may_block@entry=1) at gmain.c:3981 #22 0x7fe51bc41873 in QEventDispatcherGlib::processEvents
[Discover] [Bug 403709] New: Ratings aren't synchronized with reviews' ratings
https://bugs.kde.org/show_bug.cgi?id=403709 Bug ID: 403709 Summary: Ratings aren't synchronized with reviews' ratings Product: Discover Version: 5.14.90 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: notux...@gmail.com Target Milestone: --- Created attachment 117707 --> https://bugs.kde.org/attachment.cgi?id=117707=edit No rating from review in kmag app STEPS TO REPRODUCE 1. Open 'Applications' page. 2. Open 'Accessibility' page. 3. Open for example gXNeur or kmag app page. OBSERVED RESULT 'No ratings yet' text is displayed below app name - but there is rating in the review of the app. EXPECTED RESULT Rating from reviews is displayed below app name. SOFTWARE/OS VERSIONS Operating System: KDE neon Developer Edition KDE Plasma Version: 5.15.80 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.2 Kernel Version: 4.15.0-42-generic -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403703] Slideshow - display the list of images that will be shown
https://bugs.kde.org/show_bug.cgi?id=403703 --- Comment #10 from Filip F. --- (In reply to David Redondo from comment #9) > I had in my mind some sort of icon on each image that you could click on to > exclude an image but didn't include it in the mockup because I didn't find a > suitable one (a vague idea was open/closed eye). As I wrote in the bug > description flipwise suggested checkboxes (apparently like Windows 7 does) Yes, something like this: http://cdn.nirmaltv.com/images/changewallpaper.png -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 403708] KDE connect sometimes does not find the media player and custom commands
https://bugs.kde.org/show_bug.cgi?id=403708 --- Comment #1 from Ville Aakko --- Just after adding this report, I got behaviour where the media player is not found while the custom commands are found, and moreover: restarting the android application does not recover the media controls (as it often does). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403703] Slideshow - display the list of images that will be shown
https://bugs.kde.org/show_bug.cgi?id=403703 --- Comment #9 from David Redondo --- I had in my mind some sort of icon on each image that you could click on to exclude an image but didn't include it in the mockup because I didn't find a suitable one (a vague idea was open/closed eye). As I wrote in the bug description flipwise suggested checkboxes (apparently like Windows 7 does) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 403708] New: KDE connect sometimes does not find the media player and custom commands
https://bugs.kde.org/show_bug.cgi?id=403708 Bug ID: 403708 Summary: KDE connect sometimes does not find the media player and custom commands Product: kdeconnect Version: 1.3.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: ville.aa...@gmail.com Target Milestone: --- Sometimes KDE connect (the Android application) does not find the media player anymore or some custom commands I've set up (both seem to disappear at the same time if they appear; it is never one missing while the other works). These entries are just empty on the Android application (or; "no custom commands" or "no media player detected" or something is displayed; don't remember exactly what is displayed in the UI). Other functionality is still there; seems notifications get through, I can "ping!" either way, use as a remote (mouse/touchscreen) etc. Seems like some kind of synchronization issue (the android app forgets the media player and commands). Force closing the android applications populates the features again - but this is annoying and needs to be done very now and then. Choosing component as "common" since I am not sure which end is causing this. STEPS TO REPRODUCE 1. Pair KDE connect with an Android phone as intented 2. Create custom commands on the computter and/or set up a media player 3. Use KDE connect for a while (hours/days) (not sure how to trigger) OBSERVED RESULT Sometimes media player control and custom command just disappear from the android app. EXPECTED RESULT Media player controls and custom commands should not disappear. In case these bugs / problems can not be eliminated, there should be an easy way to refresh the android application. One workaround is to force-close the application via Android OS system. SOFTWARE/OS VERSIONS Arch Linux KDE Plasma Version: 5.14.5 Qt Version: 5.12.0 KDE Frameworks Version: 5.54.0 Kernel: 4.20.4-zen1-1-zen -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 403707] New: Add more apps into Featured apps' list from all categories
https://bugs.kde.org/show_bug.cgi?id=403707 Bug ID: 403707 Summary: Add more apps into Featured apps' list from all categories Product: Discover Version: 5.14.90 Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: notux...@gmail.com Target Milestone: --- SOFTWARE/OS VERSIONS Operating System: KDE neon Developer Edition KDE Plasma Version: 5.15.80 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.2 Kernel Version: 4.15.0-42-generic -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 403706] New: RKWard crashes on startup
https://bugs.kde.org/show_bug.cgi?id=403706 Bug ID: 403706 Summary: RKWard crashes on startup Product: rkward Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: rkward-de...@kde.org Reporter: gri...@yandex.com Target Milestone: --- Application: rkward (0.6.5) KDE Platform Version: 4.14.26 Qt Version: 4.8.7 Operating System: Linux 4.9.0-8-amd64 x86_64 Distribution: Debian GNU/Linux 9.7 (stretch) -- Information about the crash: - What I was doing when the application crashed: Opening rkward I have updated to version 3.5 by following the instructions here: https://cran.r-project.org/bin/linux/debian/stretch-cran34/ Then I have updated as root the R from inside with: update.packages(.libPaths()[1], ask = F, checkBuilt=TRUE, dependencies = F, repos = "http://mirror.ibcp.fr/pub/CRAN/;) When finalizing the update of the R, I execute RKWard and I get the error: "unable to initialize the JIT" The crash can be reproduced every time. -- Backtrace: Application: RKWard (rkward), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f14f26e8900 (LWP 7583))] Thread 3 (Thread 0x7f14d7341700 (LWP 7593)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f14f104d61a in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #2 0x7f14f104d649 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #3 0x7f14eb219494 in start_thread (arg=0x7f14d7341700) at pthread_create.c:333 #4 0x7f14ec718acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 2 (Thread 0x7f14dd419700 (LWP 7586)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #7 0x7f14ec66442a in __GI_abort () at abort.c:89 #8 0x7f14ecf7b0ad in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #9 0x7f14ecf79066 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #10 0x7f14ecf790b1 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #11 0x7f14ecf79b8f in __cxa_pure_virtual () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #12 0x55e545967334 in RKROutputBuffer::handleOutput (this=this@entry=0x55e545f9e050, output=..., buf_length=3869583, output_type=ROutput::Warning, allow_blocking=allow_blocking@entry=true) at ./rkward/rbackend/rkrbackendprotocol_shared.cpp:107 #13 0x55e545968a13 in RKFrontendTransmitter::requestReceived (this=0x55e545f9df90, request=0x7f14d8005e60) at ./rkward/rbackend/rkfrontendtransmitter.cpp:155 #14 0x55e54596c3d1 in RKAbstractTransmitter::fetchTransmission (this=0x55e545f9df90) at ./rkward/rbackend/rktransmitter.cpp:245 #15 0x7f14ee63f660 in QMetaObject::activate (sender=0x7f14d8010cc0, m=, local_signal_index=, argv=) at kernel/qobject.cpp:3567 #16 0x7f14ee63f660 in QMetaObject::activate (sender=sender@entry=0x7f14d800eaf8, m=m@entry=0x7f14ee98e9c0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3567 #17 0x7f14ee68e840 in QIODevice::readyRead (this=this@entry=0x7f14d800eaf8) at .moc/release-shared/moc_qiodevice.cpp:104 #18 0x7f14f0c30ace in QAbstractSocketPrivate::canReadNotification (this=0x7f14d800f1e0) at socket/qabstractsocket.cpp:654 #19 0x7f14f0c3a04d in QReadNotifier::event (this=, e=) at socket/qnativesocketengine.cpp:1151 #20 0x7f14ed43054c in QApplicationPrivate::notify_helper (this=this@entry=0x55e545df5390, receiver=receiver@entry=0x7f14d8011120, e=e@entry=0x7f14dd418970) at kernel/qapplication.cpp:4570 #21 0x7f14ed43752c in QApplication::notify (this=0x7ffc1692c950, receiver=0x7f14d8011120, e=0x7f14dd418970) at kernel/qapplication.cpp:4356 #22 0x7f14ef0dac5a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #23 0x7f14ee62af1d in QCoreApplication::notifyInternal (this=0x7ffc1692c950, receiver=0x7f14d8011120, event=event@entry=0x7f14dd418970) at kernel/qcoreapplication.cpp:955 #24 0x7f14ee65be12 in QCoreApplication::sendEvent (event=0x7f14dd418970, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #25 socketNotifierSourceDispatch (source=0x7f14d8003000) at kernel/qeventdispatcher_glib.cpp:110 #26 0x7f14e8c707f7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7f14e8c70a60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7f14e8c70b0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7f14ee65b854 in QEventDispatcherGlib::processEvents (this=0x7f14d80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #30 0x7f14ee6297ef in QEventLoop::processEvents
[plasmashell] [Bug 403703] Slideshow - display the list of images that will be shown
https://bugs.kde.org/show_bug.cgi?id=403703 --- Comment #8 from David Edmundson --- >I think the improvement is that the user sees what images are added to the >slideshow So the problem was that in order to verify what was added you currently have to sit through a million hours watching it cycle. I'm fully on board with that. >Also if you have some pictures you would like in your slideshow and in the >same folder you have pictures you don't want to add you have to create a new >folder and move them around. How would that change with the preview list? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403703] Slideshow - display the list of images that will be shown
https://bugs.kde.org/show_bug.cgi?id=403703 --- Comment #7 from David Redondo --- I think the improvement is that the user sees what images are added to the slideshow. Right now you have to know which images are in which folders because you are adding them blind. Also if you have some pictures you would like in your slideshow and in the same folder you have pictures you don't want to add you have to create a new folder and move them around. Apart from that I think the settings should be visually redesigned because they don't look good in my opinion. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403703] Slideshow - display the list of images that will be shown
https://bugs.kde.org/show_bug.cgi?id=403703 --- Comment #6 from Nate Graham --- I can answer that for my use cases at least. The problem is that there's no clear way to see which wallpapers will be a part of the slideshow. You only see a list of the folders that contain the wallpapers that will be a part of the slideshow, not the actual wallpapers themselves. You need to remember which images are in those folders. That's why I think the right pane should show the union of all wallpapers in all folders: then it would be answering the question of "which images will be included in the slideshow?" If it only showed the images in the selected folders, it wouldn't be answering that question anymore. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 403705] New: 'Add a new Flatpak repository' popup sometimes isn't appearing from the first time after clicking 'Add Source...' button in Wayland
https://bugs.kde.org/show_bug.cgi?id=403705 Bug ID: 403705 Summary: 'Add a new Flatpak repository' popup sometimes isn't appearing from the first time after clicking 'Add Source...' button in Wayland Product: Discover Version: 5.14.90 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Flatpak Backend Assignee: aleix...@kde.org Reporter: notux...@gmail.com CC: jgrul...@redhat.com Target Milestone: --- STEPS TO REPRODUCE 1. Open ''About' page. 2. Open 'Sources' page. 3. Click 'Add Source...' button. OBSERVED RESULT 1. The popup shows and hides immediately. 2. Second and subsequent 'Add Source...' button presses shows the popup. SOFTWARE/OS VERSIONS Operating System: KDE neon Developer Edition KDE Plasma Version: 5.15.80 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.2 Kernel Version: 4.15.0-42-generic -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403703] Slideshow - display the list of images that will be shown
https://bugs.kde.org/show_bug.cgi?id=403703 --- Comment #5 from David Edmundson --- >I'm not sure there's much value to showing per-folder wallpapers in the right >pane; that would get confusing. It depends, one thing I'd like to do is back up to the question we should have started with. What problems does David Redondo have with configuring the slideshow wallpaper right now that we're trying to solve? -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 403704] Opening server context menu makes File menu actions apply to wrong server
https://bugs.kde.org/show_bug.cgi?id=403704 --- Comment #1 from Nicolás Alvarez --- nicolas17: m_contextServer is only set when showViewContextMenu is called on a ChatWindow::Status it doesn't seem to get cleared until a showViewContextMenu is called on something other than a status window Indeed, it looks like right-clicking a *channel* tab also fixes this without needing to restart Konversation. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 403704] New: Opening server context menu makes File menu actions apply to wrong server
https://bugs.kde.org/show_bug.cgi?id=403704
Bug ID: 403704
Summary: Opening server context menu makes File menu actions
apply to wrong server
Product: konversation
Version: 1.7.5
Platform: Debian testing
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: konversation-de...@kde.org
Reporter: nicolas.alva...@gmail.com
Target Milestone: ---
SUMMARY
If I open the context menu of a server tab, Konversation gets into a broken
state where the File->Reconnect and File->Disconnect menu items will apply to
that server, regardless of what tab is currently selected.
STEPS TO REPRODUCE
1. Connect to two or more servers.
2. Try File->Reconnect or File->Disconnect actions. They work as expected,
applying to the currently selected server.
3. Right-click server tab 1; the context menu appears. Select any menu item, or
dismiss the context menu without selecting any menu item; it makes no
difference.
4. Select server tab 2, and run File->Reconnect. Now Konversation incorrectly
reconnects server tab 1.
Now every time you run File->{Disconnect,Reconnect,Join channel}, it will apply
to server tab 1 regardless of the current tab, until Konversation is restarted
(goes back to sane behavior) or you right-click a different server (makes that
the server where actions always apply).
SOFTWARE/OS VERSIONS
Debian testing
Konversation 1.7.5
(available in About System)
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3
--
You are receiving this mail because:
You are watching all bug changes.
[kactivitymanagerd] [Bug 398069] Can't assign shortcut to activities
https://bugs.kde.org/show_bug.cgi?id=398069 Lukas Leitner changed: What|Removed |Added Version|5.12.6 |5.13.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403703] Slideshow - display the list of images that will be shown
https://bugs.kde.org/show_bug.cgi?id=403703 Filip F. changed: What|Removed |Added CC||tyx...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 398069] Can't assign shortcut to activities
https://bugs.kde.org/show_bug.cgi?id=398069 Lukas Leitner changed: What|Removed |Added CC||lukasleitne...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403703] Slideshow - display the list of images that will be shown
https://bugs.kde.org/show_bug.cgi?id=403703 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||n...@kde.org --- Comment #4 from Nate Graham --- I love it! What makes sense to me is that the right pane shows all wallpapers from all folders in the left pane, and the items in the left folder pane are not selectable (just deletable). I'm not sure there's much value to showing per-folder wallpapers in the right pane; that would get confusing. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 400247] Kdenlive displays sound icon near its task when no sound is playing from it
https://bugs.kde.org/show_bug.cgi?id=400247 emohr changed: What|Removed |Added Flags||Brainstorm+ Severity|normal |wishlist CC||fritzib...@gmx.net --- Comment #1 from emohr --- If you don't mind i change it to wishlist. I'm not sure if the dev can change the code of Kdenlive in a manner to change the Task Manager settings. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403703] Slideshow - display the list of images that will be shown
https://bugs.kde.org/show_bug.cgi?id=403703 --- Comment #3 from David Redondo --- My idea was that it shows what's in the selected folder. dermauch in the vdg room/telegram had the idead to have an option to show the images from all folders -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403703] Slideshow - display the list of images that will be shown
https://bugs.kde.org/show_bug.cgi?id=403703 David Edmundson changed: What|Removed |Added Summary|Redesign slideshow settings |Slideshow - display the ||list of images that will be ||shown Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403703] Redesign slideshow settings
https://bugs.kde.org/show_bug.cgi?id=403703 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #2 from David Edmundson --- That's quite a good idea. In your head, is the preview list on the right showing the total from /all/ the folders, or showing you what's in the selected folder? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403703] Redesign slideshow settings
https://bugs.kde.org/show_bug.cgi?id=403703 David Redondo changed: What|Removed |Added CC||k...@david-redondo.de --- Comment #1 from David Redondo --- Created attachment 117706 --> https://bugs.kde.org/attachment.cgi?id=117706=edit Current settings -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403703] New: Redesign slideshow settings
https://bugs.kde.org/show_bug.cgi?id=403703 Bug ID: 403703 Summary: Redesign slideshow settings Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Image Wallpaper Assignee: notm...@gmail.com Reporter: k...@david-redondo.de CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 117705 --> https://bugs.kde.org/attachment.cgi?id=117705=edit Mockup of the idea Current slideshow settings don't look good and the only functionality is adding a whole folder to the slideshow. My idea is to have a list of folders on the left and an area where the images in the currently selected folder are shown with the possibility to exclude images. For this flipwise proposed checkboxes (missing on the attached image). Another idea from dermauch is to have an option/list item to show all images from all folders or a checkbox list. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 403702] Triggering "radio switch" with Fn+Home causes Meta-Key not to trigger Application Launcher
https://bugs.kde.org/show_bug.cgi?id=403702 Matt changed: What|Removed |Added CC||mat...@matteog.xyz -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 403702] New: Triggering "radio switch" with Fn+Home causes Meta-Key not to trigger Application Launcher
https://bugs.kde.org/show_bug.cgi?id=403702 Bug ID: 403702 Summary: Triggering "radio switch" with Fn+Home causes Meta-Key not to trigger Application Launcher Product: kwin Version: 5.14.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: appmenu Assignee: kwin-bugs-n...@kde.org Reporter: mat...@matteog.xyz Target Milestone: --- SUMMARY On my Dell XPS 9370, the radio kill button is paired with the home button, right next to my F12 key. 90% of the time, when I use that key (Fn+Home), it kills my Meta key until I relog. STEPS TO REPRODUCE 1. Hold Fn key 2. Tap Home key OBSERVED RESULT Meta key fails to trigger application launcher. Alt+F1 still works, and other Meta assignments work too. 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.
[kde] [Bug 403701] New: Displays KCM crashes every time after log into system with external monitor connected
https://bugs.kde.org/show_bug.cgi?id=403701 Bug ID: 403701 Summary: Displays KCM crashes every time after log into system with external monitor connected Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: notux...@gmail.com Target Milestone: --- Application: kcmshell5 (5.15.80) Qt Version: 5.11.2 Frameworks Version: 5.54.0 Operating System: Linux 4.15.0-42-generic x86_64 Distribution: KDE neon Developer Edition -- Information about the crash: - What I was doing when the application crashed: Started system with ext monitor connected and tried to launch Displays KCM, previously there ware log outs/ins with configuring displays in the KCM The crash can be reproduced every time. -- Backtrace: Application: System Settings Module (kcmshell5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3cfd6aa380 (LWP 12583))] Thread 2 (Thread 0x7f3ce1a14700 (LWP 12585)): #0 0x7ffe21d80aa3 in clock_gettime () #1 0x7f3cfd006ea6 in __GI___clock_gettime (clock_id=clock_id@entry=1, tp=tp@entry=0x7f3ce1a13aa0) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7f3cf9fdcff1 in qt_clock_gettime (ts=0x7f3ce1a13aa0, clock=) at kernel/qelapsedtimer_unix.cpp:111 #3 do_gettime (frac=, sec=) at kernel/qelapsedtimer_unix.cpp:166 #4 qt_gettime () at kernel/qelapsedtimer_unix.cpp:175 #5 0x7f3cf9fdb829 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7f3cdc004cf0) at kernel/qtimerinfo_unix.cpp:91 #6 0x7f3cf9fdbe05 in QTimerInfoList::timerWait (this=0x7f3cdc004cf0, tm=...) at kernel/qtimerinfo_unix.cpp:388 #7 0x7f3cf9fdd44e in timerSourcePrepareHelper (timeout=0x7f3ce1a13b64, src=) at kernel/qeventdispatcher_glib.cpp:132 #8 timerSourcePrepare (source=, timeout=0x7f3ce1a13b64) at kernel/qeventdispatcher_glib.cpp:165 #9 0x7f3cf3d6fa98 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f3cf3d7046b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f3cf3d7064c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f3cf9fdd6eb in QEventDispatcherGlib::processEvents (this=0x7f3cdc000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #13 0x7f3cf9f819aa in QEventLoop::exec (this=this@entry=0x7f3ce1a13d30, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #14 0x7f3cf9dad25a in QThread::exec (this=this@entry=0x7f3cfbb31d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:525 #15 0x7f3cfb8b9e45 in QDBusConnectionManager::run (this=0x7f3cfbb31d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #16 0x7f3cf9db817b in QThreadPrivate::start (arg=0x7f3cfbb31d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:367 #17 0x7f3cf68046db in start_thread (arg=0x7f3ce1a14700) at pthread_create.c:463 #18 0x7f3cfcff788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f3cfd6aa380 (LWP 12583)): [KCrash Handler] #5 KScreen::GetConfigOperation::start (this=0x5640990d2130) at ./src/getconfigoperation.cpp:174 #6 0x7f3cf9fb3282 in QObject::event (this=0x5640990d2130, e=) at kernel/qobject.cpp:1251 #7 0x7f3cfad10e1c in QApplicationPrivate::notify_helper (this=this@entry=0x564098fe0620, receiver=receiver@entry=0x5640990d2130, e=e@entry=0x7f3ce40066e0) at kernel/qapplication.cpp:3727 #8 0x7f3cfad183ef in QApplication::notify (this=0x7ffe21d42f00, receiver=0x5640990d2130, e=0x7f3ce40066e0) at kernel/qapplication.cpp:3486 #9 0x7f3cf9f83688 in QCoreApplication::notifyInternal2 (receiver=0x5640990d2130, event=event@entry=0x7f3ce40066e0) at kernel/qcoreapplication.cpp:1048 #10 0x7f3cf9f861cd in QCoreApplication::sendEvent (event=0x7f3ce40066e0, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:234 #11 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x564098fd7210) at kernel/qcoreapplication.cpp:1745 #12 0x7f3cf9f86788 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1599 #13 0x7f3cf9fde093 in postEventSourceDispatch (s=0x564099037190) at kernel/qeventdispatcher_glib.cpp:276 #14 0x7f3cf3d70387 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7f3cf3d705c0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7f3cf3d7064c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #17
[kdenlive] [Bug 403024] Refactoring timeline git 2019-02-09 - proxy clip on stabilized .mlt file not working
https://bugs.kde.org/show_bug.cgi?id=403024 emohr changed: What|Removed |Added CC||fritzib...@gmx.net Status|REPORTED|CONFIRMED Flags||Brainstorm+ Ever confirmed|0 |1 --- Comment #1 from emohr --- Yes the VidStab2 is an issue because this effect is deprecated https://sourceforge.net/p/mlt/bugs/252/ and we should use vidstab instead: https://www.mltframework.org/plugins/FilterVidstab/ . I add this Bug to issue: https://invent.kde.org/kde/kdenlive/issues/22 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 403688] make it easier to find "Save workflow" command
https://bugs.kde.org/show_bug.cgi?id=403688 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- There is also the menu item for saving the workflow in the first menu "Queues". Maik -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 403190] Actions Breaks The Chroma Key
https://bugs.kde.org/show_bug.cgi?id=403190 emohr changed: What|Removed |Added CC||fritzib...@gmx.net Flags||timeline_corruption+ --- Comment #1 from emohr --- I have done the following steps in Kdenlive Windows 18.12.1: - Drag a clip onto the timeline. - Drag the effect Chroma Key on that clip. - Select with the drop a color by draw up a square. - Clip gets a proper alpha. - On the timeline Set Zone Out somewhere within the clip then only the bar on top of the timeline gets shorter/longer. - The clip remains the same with the effect on it with the alpha still visible. What I’m doing different to you? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 403327] Preview Mode creates strange display when Transform effect (but not only) is applied ...
https://bugs.kde.org/show_bug.cgi?id=403327 emohr changed: What|Removed |Added Flags||timeline_corruption+ CC||fritzib...@gmx.net --- Comment #1 from emohr --- Do you have ticked „Distort“ in the transform effect? Be careful with switching the Track Compositing. See here: https://kdenlive.org/en/project/timeline-track-compositing/ -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 403700] New: Updater system tray entry should be removed after removing of Discover
https://bugs.kde.org/show_bug.cgi?id=403700 Bug ID: 403700 Summary: Updater system tray entry should be removed after removing of Discover Product: Discover Version: 5.14.90 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Updater Assignee: aleix...@kde.org Reporter: notux...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Remove Discover. 2. Right click on Updater systray icon. 3. Select 'Refresh' or 'Open Software Center...' item in the menu. OBSERVED RESULT "Could not find the program 'plasma-discover'" popup window is showed. EXPECTED RESULT Updater tray icon is removed from the tray right after Discover uninstallation. SOFTWARE/OS VERSIONS Operating System: KDE neon Developer Edition KDE Plasma Version: 5.15.80 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.2 Kernel Version: 4.15.0-42-generic -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 403650] Effect Compressor (avfilter) explodes when attributes changed
https://bugs.kde.org/show_bug.cgi?id=403650 emohr changed: What|Removed |Added CC||fritzib...@gmx.net Flags||Brainstorm+, ||timeline_corruption+ --- Comment #1 from emohr --- Tested with the AppImage 18.12.1b in a Virtual Machine on Win7. I cannot reproduce it when setting back the value to default (middle mouse click). Only when I move the gain to, let’s say 3 then the distortion begins. This must be a LADSPA effect as this effect is not on the Windows version available. I have point and not comma as decimal. Does all effect as commas? I saw such issue with effects under the Kdenlive Windows version. Change the keyboard to English and the decimal separator to point and try again. -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 403699] Karbon crashed while opening an .svg archive
https://bugs.kde.org/show_bug.cgi?id=403699 Pedro Herrero García changed: What|Removed |Added CC||pe...@pedroherrero.eu -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 403699] New: Karbon crashed while opening an .svg archive
https://bugs.kde.org/show_bug.cgi?id=403699 Bug ID: 403699 Summary: Karbon crashed while opening an .svg archive Product: karbon Version: unspecified Platform: Slackware Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ja...@gmx.net Reporter: pe...@pedroherrero.eu Target Milestone: --- Application: karbon (2.9.11) KDE Platform Version: 4.14.38 Qt Version: 4.8.7 Operating System: Linux 4.19.16 x86_64 Distribution (Platform): Slackware Packages -- Information about the crash: - What I was doing when the application crashed: Just clicked on the archive and instead of starting, Karbon crashed -- Backtrace: Application: Karbon (karbon), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #6 0x7f0fab6e57a6 in () at /usr/lib64/libflake.so.14 #7 0x7f0fab6f33df in KoShapeManager::addShape(KoShape*, KoShapeManager::Repaint) () at /usr/lib64/libflake.so.14 #8 0x7f0fab6f3b35 in KoShapeManager::setShapes(QList const&, KoShapeManager::Repaint) () at /usr/lib64/libflake.so.14 #9 0x7f0fabdda315 in () at /usr/lib64/libkarbonui.so.14 #10 0x7f0fabdcadd3 in KarbonView::KarbonView(KarbonPart*, KarbonDocument*, QWidget*) () at /usr/lib64/libkarbonui.so.14 #11 0x7f0fabdc427d in KarbonPart::createViewInstance(KoDocument*, QWidget*) () at /usr/lib64/libkarbonui.so.14 #12 0x7f0fabd533b3 in KoPart::createView(KoDocument*, QWidget*) () at /usr/lib64/libkomain.so.14 #13 0x7f0fabd083a7 in KoMainWindow::setRootDocument(KoDocument*, KoPart*, bool) () at /usr/lib64/libkomain.so.14 #14 0x7f0fabd09ec2 in KoMainWindow::slotLoadCompleted() () at /usr/lib64/libkomain.so.14 #15 0x7f0fabd183fd in () at /usr/lib64/libkomain.so.14 #16 0x7f0fbb6f0070 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/libQtCore.so.4 #17 0x7f0fabd02975 in KoDocument::openUrlInternal(KUrl const&) () at /usr/lib64/libkomain.so.14 #18 0x7f0fabd03130 in KoDocument::openUrl(KUrl const&) () at /usr/lib64/libkomain.so.14 #19 0x7f0fabd08b9c in KoMainWindow::openDocumentInternal(KUrl const&, KoPart*, KoDocument*) () at /usr/lib64/libkomain.so.14 #20 0x7f0fabd09039 in KoMainWindow::openDocument(KoPart*, KUrl const&) () at /usr/lib64/libkomain.so.14 #21 0x7f0fabcedf22 in KoApplication::start() () at /usr/lib64/libkomain.so.14 #22 0x7f0fb6fbb398 in kdemain () at /usr/lib64/libkdeinit4_karbon.so #23 0x0040842d in () #24 0x0040990e in () #25 0x0040a133 in () #26 0x0040598f in () #27 0x7f0fba46a0ab in __libc_start_main () at /lib64/libc.so.6 #28 0x0040676a in _start () [Inferior 1 (process 2432) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
