[krita] [Bug 397231] Unable to move/close certain dockers
https://bugs.kde.org/show_bug.cgi?id=397231 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- those are not dockers, but toolbars, and you can hide them in the settings/toolbars menu. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397232] Krita was suddenly closed.
https://bugs.kde.org/show_bug.cgi?id=397232 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Severity|normal |crash Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Boudewijn Rempt --- Please update to the latest version, 4.1.1. If you experience problems and want us to figure out what is going on, we need way more information than you're giving in this report. There is no way we can guess what caused the problems on your system without a crash log and a full set of instructions on how to reproduce the crash. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393358] Web Extensions support
https://bugs.kde.org/show_bug.cgi?id=393358 --- Comment #5 from Volga --- (In reply to trmdi from comment #4) > Yes, supporting the lots of existing webextensions is much better than > waiting for someone to create new Falkon extensions. And several bundled extensions in Falkon could also be convert to WebExtension. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 397040] crash when save a QImage to the eps format file
https://bugs.kde.org/show_bug.cgi?id=397040 Pino Toscano changed: What|Removed |Added CC||p...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 397040] crash when save a QImage to the eps format file
https://bugs.kde.org/show_bug.cgi?id=397040 --- Comment #4 from Pino Toscano --- (In reply to zccrs from comment #3) > Created attachment 114347 [details] > This is a stack list This shows that the issue is not in the EPS handler, which is called for some reasons during the application destruction. The problem is the deepin stuff, including its usage of an internal part of Qt (the Qt5XcbQpa library). Try the test case of comment 2 without any deepin stuff installed. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397229] Facetags are not well displayed in the facetag list for one person
https://bugs.kde.org/show_bug.cgi?id=397229 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #3 from Maik Qualmann --- The problem will be hard for us to reproduce. Can you always reproduce the problem? Maybe then a step by step guide. Was the face rectangle created manually? Was the image rotated before or after? Maik -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 397233] New: kaddressbook 5.8.80 beta1 presets the category filter with something unusable on start
https://bugs.kde.org/show_bug.cgi?id=397233 Bug ID: 397233 Summary: kaddressbook 5.8.80 beta1 presets the category filter with something unusable on start Product: kaddressbook Version: GIT Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: mathias.hom...@opensuse.org CC: to...@kde.org Target Milestone: --- When i start kontact or kaddressbook "standalone", the category filter always is preset to something that does not even exist as a category in my address book, therefor making the list of addresses appear empty. Workaround: click the "clear category filter" button, which sets the filter to "All". It seems that the list of categories got populated from the categories in my CALENDAR, it contains a lot og categories that I used in calendar entries, but never for addresses -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397194] Face tags are not well rendered when coming from Portrait DNG files
https://bugs.kde.org/show_bug.cgi?id=397194 --- Comment #4 from Maik Qualmann --- You can set the preview mode in the digiKam settings (embedded JPEG image, full view, etc.). You currently use half RAW preview. If you change these settings, the position of the face rectangle shifts? Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397219] Visual Studio Code crashed
https://bugs.kde.org/show_bug.cgi?id=397219 --- Comment #2 from Shadab Faiz --- (In reply to Martin Flöser from comment #1) > Crash happens in the Intel driver. Please report to Mesa developers. This is my first time posting any bugs here. So i have not idea who are Mesa developer and how to report to them. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397232] New: Krita was suddenly closed.
https://bugs.kde.org/show_bug.cgi?id=397232 Bug ID: 397232 Summary: Krita was suddenly closed. Product: krita Version: 4.0.4 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: dfyhu1...@gmail.com Target Milestone: --- When I drawing important graph, Kirta was suddenly closed. so, my data was gone. but I had a save file. but It is two times ago. So I must work again. I want to ask to your company's creaters. How can I do for this situation? Is there anything patch file for this bug? I Want to know your group's explanation or answer plz tell me your answer in E-mail. Thank you so much. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 359243] Krita suddenly closes while drawing
https://bugs.kde.org/show_bug.cgi?id=359243 YOUNG UK LEE changed: What|Removed |Added CC||dfyhu1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397231] New: Unable to move/close certain dockers
https://bugs.kde.org/show_bug.cgi?id=397231 Bug ID: 397231 Summary: Unable to move/close certain dockers Product: krita Version: 4.1.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: buffaloba...@earthlink.net Target Milestone: --- Created attachment 114349 --> https://bugs.kde.org/attachment.cgi?id=114349&action=edit A screenshot of my current workspace setup This is more just a minor annoyance to my personal workspace, but seeing as it doesn't appear to be the intended behavior for this program, I decided to submit a bug report anyways. Two dockers in my workspace aren't moving at all, and they aren't listed in the Settings > Dockers menu, so I can't close them. In the default workspace configuration in 4.1.1, they are the ones at the very top, just below all the menus. I made this specific workspace in version 4.1.0, and at that point I was able to move them around from the default position as long as I didn't put them anywhere else along the canvas edges. Essentially, once I moved them, they were stuck. To reproduce the issue (note that this only works in version 4.1.0, as these specific dockers are completely immobile on 4.1.1): Take the default workspace configuration, drag the docker with the eraser button, and place it in the far left side of the workspace. That's it. Once it's there, it's stuck. I only have one display active (my tablet) at any given moment. I'm using a Huion Kamvas GT-191 tablet. This problem persists on any and all canvas resolutions, sizes, etc. Here's my hardware info: Krita Version: 4.1.1 OS Information Build ABI: i386-little_endian-ilp32 Build CPU: i386 CPU: i386 Kernel Type: winnt Kernel Version: 6.3.9600 Pretty Productname: Windows 8.1 (6.3) Product Type: windows Product Version: 8.1 OpenGL Info **OpenGL not initialized** -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 397184] Amarok corrupts ogg files
https://bugs.kde.org/show_bug.cgi?id=397184 --- Comment #10 from Heiko Becker --- (In reply to jeromecmoi from comment #9) > @Heiko Becker: Did you try the ogginfo command? > Here is the output of my ogginfo with both the original and corrupted files > Did you tick the box to sync metadata with file? Yes and ogginfo looks sane: "Processing file "/home/heiko/Musik/test-file.ogg"... New logical stream (#1, serial: e1a36eda): type vorbis Vorbis headers parsed for stream 1, information follows... Version: 0 Vendor: Xiph.Org libVorbis I 20070622 (1.2.0) Channels: 2 Rate: 44100 Nominal bitrate: 128.00 kb/s Upper bitrate not set Lower bitrate not set User comments section follows ..." -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397230] New: Plasma restarts constantly in a loop
https://bugs.kde.org/show_bug.cgi?id=397230 Bug ID: 397230 Summary: Plasma restarts constantly in a loop Product: plasmashell Version: 5.12.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: s...@satel-sa.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.5) Qt Version: 5.9.4 Frameworks Version: 5.45.0 Operating System: Linux 4.12.14-lp150.12.7-default x86_64 Distribution: "openSUSE Leap 15.0" -- Information about the crash: - Unusual behavior I noticed: Occurs when entering the desk, plasma begins to restart every 2 or 3 seconds. I do not perform any other action The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f86c9e4c100 (LWP 6277))] Thread 19 (Thread 0x7f85829fd700 (LWP 6762)): #0 0x7f86c2ad289d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f86c391f3eb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f86c7691398 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f86c76917ca in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f86c391e0ce in () at /usr/lib64/libQt5Core.so.5 #5 0x7f86c2acc559 in start_thread () at /lib64/libpthread.so.0 #6 0x7f86c321d82f in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7f85837fe700 (LWP 6759)): #0 0x7f86c2ad289d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f86c391f3eb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f86c7691398 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f86c76917ca in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f86c391e0ce in () at /usr/lib64/libQt5Core.so.5 #5 0x7f86c2acc559 in start_thread () at /lib64/libpthread.so.0 #6 0x7f86c321d82f in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7f859226e700 (LWP 6681)): #0 0x7f86c2ad289d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f86c391f3eb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f86c7691398 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f86c76917ca in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f86c391e0ce in () at /usr/lib64/libQt5Core.so.5 #5 0x7f86c2acc559 in start_thread () at /lib64/libpthread.so.0 #6 0x7f86c321d82f in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7f8592cdf700 (LWP 6678)): #0 0x7f86c2ad289d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f86c391f3eb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f86c7691398 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f86c76917ca in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f86c391e0ce in () at /usr/lib64/libQt5Core.so.5 #5 0x7f86c2acc559 in start_thread () at /lib64/libpthread.so.0 #6 0x7f86c321d82f in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7f8593be1700 (LWP 6664)): #0 0x7f86c2ad289d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f86c391f3eb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f86c7691398 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f86c76917ca in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f86c391e0ce in () at /usr/lib64/libQt5Core.so.5 #5 0x7f86c2acc559 in start_thread () at /lib64/libpthread.so.0 #6 0x7f86c321d82f in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7f85a2ffd700 (LWP 6653)): #0 0x7f86c322b11c in clock_gettime () at /lib64/libc.so.6 #1 0x7f86c3b41621 in () at /usr/lib64/libQt5Core.so.5 #2 0x7f86c3b3fef9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #3 0x7f86c3b40475 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #4 0x7f86c3b419be in () at /usr/lib64/libQt5Core.so.5 #5 0x7f86bdb02668 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #6 0x7f86bdb0303b in () at /usr/lib64/libglib-2.0.so.0 #7 0x7f86bdb0321c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #8 0x7f86c3b41c0b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #9 0x7f86c3aea09a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f86c39194da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #11 0x7f86c391e0ce in () at /usr/lib64/libQt5Core.so.5 #12 0x7f86c2acc559 in start_thread () at /lib64/libpthread.so.0 #13 0x7f86c321d82f in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7f85a37fe700 (LWP 6652)): #0 0x7ffc892e3ad5 in clo
[kmymoney] [Bug 397024] Wrong date choice when a schedule transaction is recognised
https://bugs.kde.org/show_bug.cgi?id=397024 --- Comment #7 from Thomas Baumgart --- Created attachment 114348 --> https://bugs.kde.org/attachment.cgi?id=114348&action=edit Testfile Attached a sample file. It has a single account (named Current) and contains two transactions. One is matched (Test1, 200 EUR) and the button shows 'Unmatch' if it is selected, the other one (Test2, 300 EUR) the button shows 'Match' (though disabled but that is OK) if selected in the ledger. Does the problem persist using this sample file? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397229] Facetags are not well displayed in the facetag list for one person
https://bugs.kde.org/show_bug.cgi?id=397229 --- Comment #2 from Mat --- The problem exist also with DNG files in portrait orientation. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 397040] crash when save a QImage to the eps format file
https://bugs.kde.org/show_bug.cgi?id=397040 zccrs changed: What|Removed |Added CC||zc...@live.com --- Comment #3 from zccrs --- Created attachment 114347 --> https://bugs.kde.org/attachment.cgi?id=114347&action=edit This is a stack list -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 397040] crash when save a QImage to the eps format file
https://bugs.kde.org/show_bug.cgi?id=397040
zccrs changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolution|INVALID |---
--- Comment #2 from zccrs ---
(In reply to David Faure from comment #1)
> Yes, so construct a QCoreApplication, as it says ;-)
>
> This isn't a bug.
This is a bug. If not construct QGuiApplication, the "image.save" should be
return false, not thorw a abort and crash.
The above list the code is just a simple example to highlight the problem. The
following is a normal code, but it still exits abnormally.
#include
#include
#include
#include
int main(int argc, char *argv[])
{
QGuiApplication app(argc, argv);
QPixmap pixmap(100, 100);
app.clipboard()->setPixmap(pixmap);
return 0;
}
Qt=5.10.1
kimageformat-plugins=5.46.0-1
On Debian sid
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 397229] Facetags are not well displayed in the facetag list for one person
https://bugs.kde.org/show_bug.cgi?id=397229 --- Comment #1 from Mat --- Created attachment 114346 --> https://bugs.kde.org/attachment.cgi?id=114346&action=edit Screenshot of the facetag: facetags related to the wrong display really match a face -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397229] New: Facetags are not well displayed in the facetag list for one person
https://bugs.kde.org/show_bug.cgi?id=397229 Bug ID: 397229 Summary: Facetags are not well displayed in the facetag list for one person Product: digikam Version: 5.9.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Faces-Detection Assignee: digikam-bugs-n...@kde.org Reporter: erme...@gmail.com Target Milestone: --- Created attachment 114345 --> https://bugs.kde.org/attachment.cgi?id=114345&action=edit Screenhof of the problem: facetag is not well displayed in the facetag list Hi there, To reproduce: - From the left side, click person - select a person from the person list - browse pictures: some of them are not well displayed (screenshot pb_facetags_facetag_not_well_displayed_in_facetag_list.png) - click on a thumbnail where face is not well displayed - see that the face is correctly rounded on the picture (screenshot pb_facetag_facetag_well_displayed_when_displaying_the_picture.png) reproductible: sometimes. Seems happen only when picture orientation is portrait (with Canon CR2 raw files from EOS 5D Mark III and EOS 7D) Regards -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 397024] Wrong date choice when a schedule transaction is recognised
https://bugs.kde.org/show_bug.cgi?id=397024 Simon Depiets changed: What|Removed |Added CC||sdepi...@gmail.com --- Comment #6 from Simon Depiets --- I've amended the translation to "Ne correspond pas" I hope it will be short enough, the shorter alternatives "associer/dissocier/apparier/etc." are less accurate and for some of them already used (for associated accounts). https://phabricator.kde.org/R883:1522012 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397206] Kicker: submenus are too wide after opening Recent Documents containing long filename
https://bugs.kde.org/show_bug.cgi?id=397206 --- Comment #4 from Albert Astals Cid --- No, that's not what I understand we agreed. I understood you wanted to minimize jumps in width while visiting the menu. If it did what you are suggesting now it would jump in width continuously when you switch between Recent Documents and Administration. So what it does is stick to the minimum size for the menus you've visited until now. If you don't like that and prefer the width to jump for every menu you visit that is fine, it is actually what i wanted but I thought it was clear it was not what you wanted. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 397201] Show current version of package in Discover Update available list
https://bugs.kde.org/show_bug.cgi?id=397201 Aleix Pol changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/dis ||cover/4b1c55098170ea23a2ef8 ||47c40b306486edcaa22 Resolution|--- |FIXED --- Comment #1 from Aleix Pol --- Git commit 4b1c55098170ea23a2ef847c40b306486edcaa22 by Aleix Pol. Committed on 06/08/2018 at 23:36. Pushed by apol into branch 'master'. PK: Improve changelog for appstream applications It seems like expecting developers to offer a proper changelog is a lot to ask. At least show something so the user isn't on his own to see what's happening. M +2-2libdiscover/backends/PackageKitBackend/AppPackageKitResource.cpp M +1-1libdiscover/backends/PackageKitBackend/AppPackageKitResource.h M +1-1libdiscover/backends/PackageKitBackend/PackageKitResource.cpp M +2-0libdiscover/backends/PackageKitBackend/PackageKitResource.h https://commits.kde.org/discover/4b1c55098170ea23a2ef847c40b306486edcaa22 -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 397193] Latte fails to show window thumbnails with multiple application windows
https://bugs.kde.org/show_bug.cgi?id=397193 --- Comment #4 from Ben Daines --- Seems fixed to me. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 397228] kcm_keyboard crash
https://bugs.kde.org/show_bug.cgi?id=397228 Mau changed: What|Removed |Added Platform|unspecified |Debian testing -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 397228] New: kcm_keyboard crash
https://bugs.kde.org/show_bug.cgi?id=397228 Bug ID: 397228 Summary: kcm_keyboard crash Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mav...@gmail.com Target Milestone: --- Application: kdeinit5 (5.13.1) Qt Version: 5.10.1 Frameworks Version: 5.47.0 Operating System: Linux 4.17.0-12.slh.1-aptosid-amd64 x86_64 Distribution: Debian GNU/Linux testing (buster) -- Information about the crash: - What I was doing when the application crashed: closing with "OK" the kcm module after deselecting "spare mappings" (4 mappings set: Italian, Russian, Croatian and Serbian). I also noticed that after applying some change the process "kcmshell5 [kdeinit5] --args=--tab=layouts kcm_keyboard" didn't exit and prevented opening the kcm module again, therefore I killed it manually. -- Backtrace: Application: Modulo delle impostazioni di sistema (kdeinit5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa8a82a4780 (LWP 3096))] Thread 3 (Thread 0x7fa890f1b700 (LWP 3102)): [KCrash Handler] #5 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #6 0x7fa8af6b72f1 in __GI_abort () at abort.c:79 #7 0x7fa8af6f8867 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fa8af802273 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 #8 0x7fa8af6fee0a in malloc_printerr (str=str@entry=0x7fa8af803b30 "malloc_consolidate(): invalid chunk size") at malloc.c:5350 #9 0x7fa8af6ff10e in malloc_consolidate (av=av@entry=0x7fa88020) at malloc.c:4441 #10 0x7fa8af701dad in _int_malloc (av=av@entry=0x7fa88020, bytes=bytes@entry=2032) at malloc.c:3703 #11 0x7fa8af704321 in __libc_calloc (n=, elem_size=) at malloc.c:3436 #12 0x7fa8ac3d23e3 in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-tls.so.390.77 #13 0x7fa8aca468b1 in g_malloc0 () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fa8aca5ee1d in g_slice_free1 () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fa8ae1e6058 in __nptl_deallocate_tsd () at pthread_create.c:300 #16 0x7fa8ae1e707c in __nptl_deallocate_tsd () at ../sysdeps/nptl/futex-internal.h:200 #17 start_thread (arg=0x7fa890f1b700) at pthread_create.c:473 #18 0x7fa8af777edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fa893fff700 (LWP 3098)): #0 0x7fa8af76d739 in __GI___poll (fds=0x7fa88c0029e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fa8aca41439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa8aca4154c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa8afb2e1bb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa8afad1b6a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa8af8e77ea in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa8a69b1df5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fa8af8ecb4f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fa8ae1e6f2a in start_thread (arg=0x7fa893fff700) at pthread_create.c:463 #9 0x7fa8af777edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fa8a82a4780 (LWP 3096)): [KCrash Handler] #6 0x7fa8aa3c3310 in XextRemoveDisplay () from /usr/lib/x86_64-linux-gnu/libXext.so.6 #7 0x7fa8adf27884 in ?? () from /usr/lib/x86_64-linux-gnu/libGL.so.1 #8 0x7fa8b0b6e3d2 in XCloseDisplay () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #9 0x7fa89d8dcc14 in QXcbConnection::~QXcbConnection() () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #10 0x7fa89d8dccb9 in QXcbConnection::~QXcbConnection() () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #11 0x7fa89d8de956 in QXcbIntegration::~QXcbIntegration() () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #12 0x7fa89d8dea59 in QXcbIntegration::~QXcbIntegration() () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #13 0x7fa8b00375ad in QGuiApplicationPrivate::~QGuiApplicationPrivate() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #14 0x7fa8ae55bf89 in QApplicationPrivate::~QApplicationPrivate() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7fa8afb0a693 in QObject::~QObject() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7fa8afad5e96 in QCoreApplication::~QCoreApplication() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7fa8ae55e129 in QApplication::~QApplication() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7fa89f7d5f7f in kdemain () from /usr/lib/x86_6
[kstars] [Bug 397227] New: PHD2 stopped guiding not recognized
https://bugs.kde.org/show_bug.cgi?id=397227 Bug ID: 397227 Summary: PHD2 stopped guiding not recognized Product: kstars Version: 2.9.7 Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: wreis...@gmx.de Target Milestone: --- When guiding with PHD2 fails during a schedule, it causes a capture failure marking the capture as "Aborted". But when the scheduler tries to recover, the PHD2 guide adaptor returns the wrong value: guideInterface->call(QDBus::AutoDetect, "getStatus") returns "no error" despite PHD has stopped guiding. As a consequence, the scheduler simply executes the next capture sequence and does not restarts guiding. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 385846] Baloo file indexer crashes on login
https://bugs.kde.org/show_bug.cgi?id=385846 --- Comment #4 from Bob Wildfong --- Created attachment 114344 --> https://bugs.kde.org/attachment.cgi?id=114344&action=edit New crash information added by DrKonqi baloo_file_extractor (5.47.0) using Qt 5.9.6 - What I was doing when the application crashed: logged into plasma after a fresh boot, crash appeared instantly. Happens nearly every login, except one time very recently Baloo did not crash but gradually consumed all memory. That time, I rebooted, and it crashed on first login as usual. -- Backtrace (Reduced): #6 0x7fece6ca248b in Baloo::IdFilenameDB::get(unsigned long long) () from /lib64/libKF5BalooEngine.so.5 #7 0x7fece6c9bdaf in Baloo::DocumentUrlDB::get(unsigned long long) const () from /lib64/libKF5BalooEngine.so.5 #8 0x7fece6cac7c4 in Baloo::Transaction::documentUrl(unsigned long long) const () from /lib64/libKF5BalooEngine.so.5 #9 0x5591e2ab1bd8 in Baloo::App::processNextFile() () #10 0x7fece4bc9a24 in QSingleShotTimer::timerEvent(QTimerEvent*) () from /lib64/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 385846] Baloo file indexer crashes on login
https://bugs.kde.org/show_bug.cgi?id=385846 Bob Wildfong changed: What|Removed |Added CC||b...@seeds.ca -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 397226] New: Action icons are missing
https://bugs.kde.org/show_bug.cgi?id=397226 Bug ID: 397226 Summary: Action icons are missing Product: kmymoney Version: 5.0.0 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: aba...@free.fr Target Milestone: --- Created attachment 114343 --> https://bugs.kde.org/attachment.cgi?id=114343&action=edit Welcome window without action icons I have installed kmymoney from the application manager on my Linux Mint 19 (Tara) distro. Action Icons for KMyMoney 5 are missing. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396934] Halftone filter renders to white in MacOS
https://bugs.kde.org/show_bug.cgi?id=396934 L. E. Segovia changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #3 from L. E. Segovia --- As of 2d24e9a09f796466e3001510ce24944785192c95 it is working again. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5
https://bugs.kde.org/show_bug.cgi?id=347772 --- Comment #25 from Gianni --- Created attachment 114342 --> https://bugs.kde.org/attachment.cgi?id=114342&action=edit qdbus org.kde.KWin /KWin supportInformation macmini mid 2007 -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 397193] Latte fails to show window thumbnails with multiple application windows
https://bugs.kde.org/show_bug.cgi?id=397193 Michail Vourlakos changed: What|Removed |Added Latest Commit|https://commits.kde.org/lat |https://commits.kde.org/lat |te-dock/b4a7b1ac844f2ced04f |te-dock/176d7200cdc7c90cb1b |63b8c5e5d7c2d6619b7cb |239751f56da1134d822a0 --- Comment #3 from Michail Vourlakos --- Git commit 176d7200cdc7c90cb1b239751f56da1134d822a0 by Michail Vourlakos. Committed on 06/08/2018 at 22:05. Pushed by mvourlakos into branch 'v0.8'. restructure windows previews to plasma design --previews showed some strange behavior by re-introducing faulty or empty previews under X11. Best way to approach this is to follow up plasma design idea in order for the code to be comparable. The code was updated and the introduced issue shows to be fixed but this wants users feedback. FIXED-IN: 0.8.1 (cherry picked from commit b4a7b1ac844f2ced04f63b8c5e5d7c2d6619b7cb) M +1-1plasmoid/package/contents/ui/MouseHandler.qml M +81 -85 plasmoid/package/contents/ui/ToolTipDelegate2.qml M +17 -17 plasmoid/package/contents/ui/ToolTipInstance.qml M +2-3plasmoid/package/contents/ui/ToolTipWindowMouseArea.qml M +2-8plasmoid/package/contents/ui/main.qml M +1-1plasmoid/package/contents/ui/task/TaskDelegate.qml https://commits.kde.org/latte-dock/176d7200cdc7c90cb1b239751f56da1134d822a0 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5
https://bugs.kde.org/show_bug.cgi?id=347772 Gianni changed: What|Removed |Added CC||gianni_2...@hotmail.it --- Comment #24 from Gianni --- I am experiencing this bug on plasma 5.13.5 using intel integrated graphics. Whenever the screen locks kscreenlocker_greet starts eating cpu with consequent fan spin. This is very annoying and destroys the concept of energy saving. Since I'm not using nvidia graphics I doubt it's related to that specific driver, unless there is more than one bug (if someone thinks this is the case, I'll promptly file another bug). I'm appending output of "qdbus org.kde.KWin /KWin supportInformation" for my system (a mid 2007 macmini). -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 397193] Latte fails to show window thumbnails with multiple application windows
https://bugs.kde.org/show_bug.cgi?id=397193 Michail Vourlakos changed: What|Removed |Added Version Fixed In||0.8.1 Resolution|--- |FIXED Latest Commit||https://commits.kde.org/lat ||te-dock/b4a7b1ac844f2ced04f ||63b8c5e5d7c2d6619b7cb Status|CONFIRMED |RESOLVED --- Comment #2 from Michail Vourlakos --- Git commit b4a7b1ac844f2ced04f63b8c5e5d7c2d6619b7cb by Michail Vourlakos. Committed on 06/08/2018 at 22:04. Pushed by mvourlakos into branch 'master'. restructure windows previews to plasma design --previews showed some strange behavior by re-introducing faulty or empty previews under X11. Best way to approach this is to follow up plasma design idea in order for the code to be comparable. The code was updated and the introduced issue shows to be fixed but this wants users feedback. FIXED-IN: 0.8.1 M +1-1plasmoid/package/contents/ui/MouseHandler.qml M +81 -85 plasmoid/package/contents/ui/ToolTipDelegate2.qml M +17 -17 plasmoid/package/contents/ui/ToolTipInstance.qml M +2-3plasmoid/package/contents/ui/ToolTipWindowMouseArea.qml M +2-8plasmoid/package/contents/ui/main.qml M +1-1plasmoid/package/contents/ui/task/TaskDelegate.qml https://commits.kde.org/latte-dock/b4a7b1ac844f2ced04f63b8c5e5d7c2d6619b7cb -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 397204] Latte-Dock does not always respect Opacity Settings
https://bugs.kde.org/show_bug.cgi?id=397204 --- Comment #2 from Michail Vourlakos --- Probably some screenshots showing the issue and the settings in Appearance to understand what is the issue -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 397225] New: newly generated gpg key not shown in kmail
https://bugs.kde.org/show_bug.cgi?id=397225 Bug ID: 397225 Summary: newly generated gpg key not shown in kmail Product: kmail2 Version: 5.8.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-b...@kde.org Reporter: robby.engelm...@igfs-ev.de Target Milestone: --- I generated a new key in kleopatra, but in kmail it is not shown, when I want to set it to an identity. However, generating a new key (only with kind of standard settings) directly in kmail works. The key is also shown in kleopatra with no obviously different properties (expect for no expiration and only 2024bit instead of 4048bit). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397221] Tracking
https://bugs.kde.org/show_bug.cgi?id=397221 --- Comment #3 from Boudewijn Rempt --- If you have the latest version (next time, give the version number, please, "latest" doesn't say much) of Wacom's driver, something _has_ changed, you must have updated the driver. The latest wacom tablet driver is known to have a bug causing offsets when drawing, so you probabl should downgrade until the problem is fixed in the driver. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397221] Tracking
https://bugs.kde.org/show_bug.cgi?id=397221 --- Comment #2 from bakabakatou...@outlook.fr --- What tablet? Intuos CTH490 What driver version? i have the last version, even after an update the bug remains the same What changed "a few months" ago on your system? I did not touch anything -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 397104] isbndb search broken
https://bugs.kde.org/show_bug.cgi?id=397104 --- Comment #5 from Volker Fröhlich --- Anyway, I can see that you already disabled it in May. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 397105] "plasmawindowed org.kde.plasma.networkmanagement" can't be closed correctly
https://bugs.kde.org/show_bug.cgi?id=397105 --- Comment #5 from Lucas Willems --- Thank you for the work! and details :) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397194] Face tags are not well rendered when coming from Portrait DNG files
https://bugs.kde.org/show_bug.cgi?id=397194 --- Comment #3 from Mat --- Hello Maik, How can I confirm that? Kind regards -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 394960] Kirigami.Theme.highlightColor changes depending on whether the window is selected
https://bugs.kde.org/show_bug.cgi?id=394960 --- Comment #11 from Matthew Trescott --- Sorry, I realized that we're talking about different things. I'm talking specifically about the word "Graphics" in the header turning black when the window is defocused. I don't have any problem with the interactive widgets switching to a lighter shade of blue. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 397104] isbndb search broken
https://bugs.kde.org/show_bug.cgi?id=397104 --- Comment #4 from Volker Fröhlich --- Hm? I didn't say 0.4 anywhere. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 394960] Kirigami.Theme.highlightColor changes depending on whether the window is selected
https://bugs.kde.org/show_bug.cgi?id=394960 Matthew Trescott changed: What|Removed |Added Ever confirmed|1 |0 Resolution|INVALID |--- Status|RESOLVED|UNCONFIRMED --- Comment #10 from Matthew Trescott --- Those are all interactive widgets, not non-interactive text. Imagine if the word "Startup" in your last screenshot turned green when Dolphin's config windows was un-focused. It wouldn't make any sense. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397207] Too many open files, when reverse geocoding many images
https://bugs.kde.org/show_bug.cgi?id=397207 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||6.0.0 Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/dig ||ikam/f0cb9459229d84c6c96158 ||a9fb8e5016ae36b3c7 --- Comment #2 from Maik Qualmann --- Git commit f0cb9459229d84c6c96158a9fb8e5016ae36b3c7 by Maik Qualmann. Committed on 06/08/2018 at 20:24. Pushed by mqualmann into branch 'master'. fix use of QNetworkAccessManager FIXED-IN: 6.0.0 M +2-1NEWS M +16 -18 core/utilities/geolocation/editor/backends/backend-geonames-rg.cpp M +16 -20 core/utilities/geolocation/editor/backends/backend-geonamesUS-rg.cpp M +14 -17 core/utilities/geolocation/editor/backends/backend-osm-rg.cpp M +13 -15 core/utilities/geolocation/editor/searches/searchbackend.cpp M +14 -13 core/utilities/geolocation/geoiface/lookup/lookupaltitudegeonames.cpp https://commits.kde.org/digikam/f0cb9459229d84c6c96158a9fb8e5016ae36b3c7 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397206] Kicker: submenus are too wide after opening Recent Documents containing long filename
https://bugs.kde.org/show_bug.cgi?id=397206 --- Comment #3 from Eike Hein --- According to the user bug report, a wide menu now raises some floor that it never dips below again. I don't think that's what I requested :). Wasn't it supposed to expand if needed, but stick to the default size when it can? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 397108] GPU crash when setting the needle
https://bugs.kde.org/show_bug.cgi?id=397108 --- Comment #2 from Mateus Seenem Tavares --- hm, gonna tried that, but after disabling gpu aceleration(moovit) it comes back normal. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 396050] Move away from SHA-1 to SHA-2
https://bugs.kde.org/show_bug.cgi?id=396050 rugk <7429c...@opayq.com> changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #2 from rugk <7429c...@opayq.com> --- Okay, that's good to hear, but anyway, that's still a thing to move away from. Also HTTPS certificates signed by CAs must not use SHA-1 anymore. They have reasons to do so. :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397224] Tranform layer tool crashes krita
https://bugs.kde.org/show_bug.cgi?id=397224 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Boudewijn Rempt --- Please update to 4.1.1: that has this issue fixed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397224] New: Tranform layer tool crashes krita
https://bugs.kde.org/show_bug.cgi?id=397224 Bug ID: 397224 Summary: Tranform layer tool crashes krita Product: krita Version: 4.1.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: hxkh...@gmail.com Target Milestone: --- Application: krita (4.1.0) Qt Version: 5.9.6 Frameworks Version: 5.47.0 Operating System: Linux 4.17.11-100.fc27.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: Every time transform layer tool is clicked or ctrl+T is used krita produces segmentation fault The crash can be reproduced every time. -- Backtrace: Application: Krita (krita), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1cee19d940 (LWP 11937))] Thread 7 (Thread 0x7f1c9bd3a700 (LWP 11990)): #0 0x7f1ce0691472 in g_poll () at /lib64/libglib-2.0.so.0 #1 0x7f1ce0681eb9 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f1ce0681fcc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f1ce36fcd3b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f1ce36aaa3a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f1ce34fba1a in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f1ca4f09576 in QQuickPixmapReader::run() () at /lib64/libQt5Quick.so.5 #7 0x7f1ce34fff32 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f1ce169d50b in start_thread () at /lib64/libpthread.so.0 #9 0x7f1ce28b016f in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f1ca47e1700 (LWP 11989)): #0 0x7f1ce28a1738 in read () at /lib64/libc.so.6 #1 0x7f1ce06c6160 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7f1ce06819c8 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f1ce0681e60 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7f1ce0681fcc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f1ce36fcd3b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f1ce36aaa3a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7f1ce34fba1a in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7f1ca4ac4565 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #9 0x7f1ce34fff32 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #10 0x7f1ce169d50b in start_thread () at /lib64/libpthread.so.0 #11 0x7f1ce28b016f in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f1ca3fe0700 (LWP 11986)): #0 0x7f1ce16a382d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1ce350068b in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f1ce34fa6df in QSemaphore::tryAcquire(int, int) () at /lib64/libQt5Core.so.5 #3 0x7f1cebee8c6a in KisTileDataSwapper::run() () at /lib64/libkritaimage.so.17 #4 0x7f1ce34fff32 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f1ce169d50b in start_thread () at /lib64/libpthread.so.0 #6 0x7f1ce28b016f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f1cb700 (LWP 11943)): #0 0x7f1ce28a5c6b in poll () at /lib64/libc.so.6 #1 0x7f1ce0681eb9 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f1ce0682252 in g_main_loop_run () at /lib64/libglib-2.0.so.0 #3 0x7f1ccc593c86 in gdbus_shared_thread_func () at /lib64/libgio-2.0.so.0 #4 0x7f1ce06a9546 in g_thread_proxy () at /lib64/libglib-2.0.so.0 #5 0x7f1ce169d50b in start_thread () at /lib64/libpthread.so.0 #6 0x7f1ce28b016f in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f1cc4a86700 (LWP 11942)): #0 0x7f1ce28a1738 in read () at /lib64/libc.so.6 #1 0x7f1ce06c6160 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7f1ce06819c8 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f1ce0681e60 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7f1ce0681fcc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f1ce0682011 in glib_worker_main () at /lib64/libglib-2.0.so.0 #6 0x7f1ce06a9546 in g_thread_proxy () at /lib64/libglib-2.0.so.0 #7 0x7f1ce169d50b in start_thread () at /lib64/libpthread.so.0 #8 0x7f1ce28b016f in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f1cc58fc700 (LWP 11940)): #0 0x7f1ce34fef22 in QThreadData::current(bool) () at /lib64/libQt5Core.so.5 #1 0x7f1ce36fcc2a in postEventSourcePrepare(_GSource*, int*) () at /lib64/libQt5Core.so.5 #2 0x7f1ce0681419 in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #3 0x7f1ce0681deb in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x00
[systemsettings] [Bug 397223] New: system settings crashes on close under Wayland
https://bugs.kde.org/show_bug.cgi?id=397223 Bug ID: 397223 Summary: system settings crashes on close under Wayland Product: systemsettings Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Application: systemsettings5 (5.13.80) Qt Version: 5.11.1 Frameworks Version: 5.49.0 Operating System: Linux 4.15.0-29-generic x86_64 Distribution: KDE neon Developer Edition -- Information about the crash: - What I was doing when the application crashed: open system settings (I use the icon view) open "shortcuts", click every section on the left side from the top to bottom back to all settings click "startup and shutdown" and click every section on the left side from the top to bottom again when you to reach the kcm to configure the boot screen, close the system settings window plasma shows a crash notification The crash can be reproduced every time. -- Backtrace: Application: Configurações do Sistema (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4ac754c940 (LWP 21789))] Thread 5 (Thread 0x7f4a8b91c700 (LWP 21802)): #0 0x7f4abc309a94 in g_mutex_unlock (mutex=0x7f4a84000990) at /build/glib2.0-b4FPyK/glib2.0-2.48.2/./glib/gthread-posix.c:1347 #1 0x7f4abc2c4f2a in g_main_context_dispatch (context=context@entry=0x7f4a84000990) at /build/glib2.0-b4FPyK/glib2.0-2.48.2/./glib/gmain.c:3772 #2 0x7f4abc2c53f0 in g_main_context_iterate (context=context@entry=0x7f4a84000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-b4FPyK/glib2.0-2.48.2/./glib/gmain.c:3840 #3 0x7f4abc2c549c in g_main_context_iteration (context=0x7f4a84000990, may_block=may_block@entry=1) at /build/glib2.0-b4FPyK/glib2.0-2.48.2/./glib/gmain.c:3901 #4 0x7f4ac34bb0bb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f4a840008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f4ac34625ba in QEventLoop::exec(QFlags) (this=this@entry=0x7f4a8b91bc50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #6 0x7f4ac32975e4 in QThread::exec() (this=) at thread/qthread.cpp:525 #7 0x7f4ac0faf195 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f4ac32a2727 in QThreadPrivate::start(void*) (arg=0x696e690) at thread/qthread_unix.cpp:367 #9 0x7f4abe3476ba in start_thread (arg=0x7f4a8b91c700) at pthread_create.c:333 #10 0x7f4ac2baf41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f4a9dd4f700 (LWP 21799)): #0 0x7f4ac2ba374d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f4abc2c538c in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f4a900010c0, timeout=, context=0x23676e0) at /build/glib2.0-b4FPyK/glib2.0-2.48.2/./glib/gmain.c:4135 #2 0x7f4abc2c538c in g_main_context_iterate (context=0x23676e0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-b4FPyK/glib2.0-2.48.2/./glib/gmain.c:3835 #3 0x7f4abc2c5712 in g_main_loop_run (loop=0x2250470) at /build/glib2.0-b4FPyK/glib2.0-2.48.2/./glib/gmain.c:4034 #4 0x7f4a9e8399d6 in gdbus_shared_thread_func (user_data=0x22504b0) at /build/glib2.0-b4FPyK/glib2.0-2.48.2/./gio/gdbusprivate.c:246 #5 0x7f4abc2ebbb5 in g_thread_proxy (data=0x22304a0) at /build/glib2.0-b4FPyK/glib2.0-2.48.2/./glib/gthread.c:780 #6 0x7f4abe3476ba in start_thread (arg=0x7f4a9dd4f700) at pthread_create.c:333 #7 0x7f4ac2baf41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f4a9e550700 (LWP 21798)): #0 0x7f4ac2ba374d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f4abc2c538c in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f4a980008c0, timeout=, context=0x23299d0) at /build/glib2.0-b4FPyK/glib2.0-2.48.2/./glib/gmain.c:4135 #2 0x7f4abc2c538c in g_main_context_iterate (context=context@entry=0x23299d0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-b4FPyK/glib2.0-2.48.2/./glib/gmain.c:3835 #3 0x7f4abc2c549c in g_main_context_iteration (context=0x23299d0, may_block=may_block@entry=1) at /build/glib2.0-b4FPyK/glib2.0-2.48.2/./glib/gmain.c:3901 #4 0x7f4abc2c54d9 in glib_worker_main (data=) at /build/glib2.0-b4FPyK/glib2.0-2.48.2/./glib/gmain.c:5672 #5 0x7f4abc2ebbb5 in g_thread_proxy (data=0x2230450) at /build/glib2.0-b4FPyK/glib2.0-2.48.2/./glib/gthread.c:780 #6 0x7f4abe3476ba in start_thread (arg=0x7f4a9e550700) at pthread_create.c:333 #7 0x7f4ac2baf41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f4ab099d700 (LWP 21791)): #0 0x7f4abc309a94 in g_mutex_unlock
[plasmashell] [Bug 387901] Task manager loses windows with multi monitor
https://bugs.kde.org/show_bug.cgi?id=387901 Luiz Angelo De Luca changed: What|Removed |Added Status|NEEDSINFO |REOPENED Resolution|WAITINGFORINFO |--- CC||luizl...@gmail.com Ever confirmed|0 |1 --- Comment #2 from Luiz Angelo De Luca --- Hello, I'm having something like this problem. I use task manager configured to show only windows in the current monitor. I'm using 5.13.3 (openSUSE Tumbleweed) My second screen sometimes does not recovery nicely from sleep/hibernate or from power save mode. The screen becomes either off (but KDE still detects it as on) or shows garbage. My workaround is to turn it off and on again: xrandr --output DisplayPort-0 --off xrandr --output DisplayPort-0 --auto xrandr --output DisplayPort-0 --rotate left --left-of DisplayPort-1 xrandr --output DisplayPort-1 --primary --pos 900x131 When I do that, plasma task manager losses the association of windows-screen on the primary screen, showing no window at all. The secondary screen does work as expected. If I create a new task manager, I can see the correct list of windows. If I uncheck the "show only windows from current monitor", I can see all windows, including from the primary screen. However, if I mark it again, I return to the problematic state. If I restart plasma, everything is back to normal. Is there any info to get while the problem is happening? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 396309] Clip Ebtry
https://bugs.kde.org/show_bug.cgi?id=396309 fritzib...@gmx.net changed: What|Removed |Added CC||fritzib...@gmx.net --- Comment #1 from fritzib...@gmx.net --- Does the clip play in VLC (for example)? If not download the clip again from: granjow.net/uploads/kdenlive/manual/kdenlive-tutorial-videos-2011-avi.tar.bz2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397221] Tracking
https://bugs.kde.org/show_bug.cgi?id=397221 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Boudewijn Rempt --- What tablet? What driver version? What changed "a few months" ago on your system? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397206] Kicker: submenus are too wide after opening Recent Documents containing long filename
https://bugs.kde.org/show_bug.cgi?id=397206 --- Comment #2 from Albert Astals Cid --- You said you didn't want the width to jump when changing menus, that's what i did. So that would be a "no bug"? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 397222] Move an annotation over page border makes it inaccessible
https://bugs.kde.org/show_bug.cgi?id=397222 Oliver Sander changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||oliver.san...@tu-dresden.de Ever confirmed|0 |1 --- Comment #1 from Oliver Sander --- I can confirm this. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 397184] Amarok corrupts ogg files
https://bugs.kde.org/show_bug.cgi?id=397184 --- Comment #9 from jeromec...@laposte.net --- Created attachment 114341 --> https://bugs.kde.org/attachment.cgi?id=114341&action=edit Ogginfo files for original and corrupted music 2.8.0 isn't supported anymore… but it is the most recent from Debian Stable repo… (and no 2.9.0 backport) So, I'm sorry but I can't do what you ask without upgrading my whole Debian :/ If any of you guys can try to reproduce the problem… @Heiko Becker: Did you try the ogginfo command? Here is the output of my ogginfo with both the original and corrupted files Did you tick the box to sync metadata with file? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcmutils] [Bug 389585] Window is too small when KCMs are opened standalone (e.g. using `kcmshell5), and contents get cut off
https://bugs.kde.org/show_bug.cgi?id=389585 Valeriy Malov changed: What|Removed |Added CC||jazzv...@gmail.com --- Comment #20 from Valeriy Malov --- There seem to be multiple problems First, there seems to be a problem with QDialog + QScrollArea having some kind of implicit preferred maximum size, after which dialog stops growing to fit content. For example, all kcmshell5 dialogs open at 637x518 max for me no matter what's the size of the widget inside. Second, some widgets that have QML contents report incorrect size hint because QML content takes time to initialize. This is why KScreen KCM has size hint explicitly set, and it stops it from opening as extremely tiny window, but issue 1 stops it from opening as a large enough window to fit all contents. Third, few widgets already seem to have scrollable content (e.g. opengl kcm) and they probably just need manual minimum size set. First problem is the biggest issue I suppose, since it affects all KCMs with large content and network manager KCM in particular, but I don't know where this preferred size comes from so I don't know how to fix it yet :/ -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 397222] New: Move an annotation over page border makes it inaccessible
https://bugs.kde.org/show_bug.cgi?id=397222 Bug ID: 397222 Summary: Move an annotation over page border makes it inaccessible Product: okular Version: 1.4.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: codestr...@posteo.org Target Milestone: --- Reproduce: 1. Have a two page PDF file and open it with Okular 2. Create an annotation on page 2 3. Move the annotation to page 1 4. The annotation disappears. It can now only be accessed from the "Reviews" tree view where it can be edited and deleted but not moved to make it visible again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397219] Visual Studio Code crashed
https://bugs.kde.org/show_bug.cgi?id=397219 Martin Flöser changed: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #1 from Martin Flöser --- Crash happens in the Intel driver. Please report to Mesa developers. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397221] New: Tracking
https://bugs.kde.org/show_bug.cgi?id=397221 Bug ID: 397221 Summary: Tracking Product: krita Version: 4.1.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: bakabakatou...@outlook.fr Target Milestone: --- Created attachment 114340 --> https://bugs.kde.org/attachment.cgi?id=114340&action=edit Bug tracker Hello, since a few months I have a problem with the stylus tracker it is completely decline I can not draw anything -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 389713] AAC navigation/seeking - Kdenlive plays the wrong part of the file
https://bugs.kde.org/show_bug.cgi?id=389713 fritzib...@gmx.net changed: What|Removed |Added CC||fritzib...@gmx.net --- Comment #1 from fritzib...@gmx.net --- Some play bugs in Windows are known. Try the following: press CTRL+space (start from begin) and then click with the mouse into the timeline. Is it playing now as you expecting? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 397220] Thumbnails/previews in systemsettings gone
https://bugs.kde.org/show_bug.cgi?id=397220 maxthon...@outlook.com changed: What|Removed |Added CC||maxthon...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 397220] New: Thumbnails/previews in systemsettings gone
https://bugs.kde.org/show_bug.cgi?id=397220 Bug ID: 397220 Summary: Thumbnails/previews in systemsettings gone Product: systemsettings Version: 5.13.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: maxthon...@outlook.com Target Milestone: --- Created attachment 114339 --> https://bugs.kde.org/attachment.cgi?id=114339&action=edit Image of look and feel I am experiencing an issue that all the preview thumbnails for look an feel, dekstop theme, cursor, the loading screen after sddm and for the icon theme are gone in the system settings. The same thing also applies to desktop wallpaper, strangely the preview for the windows titles works fine. I have booted two different snapshots from before the problem occured and the problem still existed there so it should not have anything to do with any updates. I am on 5.13.4 now and the updates didn't change it either. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 386281] Video on timeline does not display
https://bugs.kde.org/show_bug.cgi?id=386281 fritzib...@gmx.net changed: What|Removed |Added CC||fritzib...@gmx.net --- Comment #4 from fritzib...@gmx.net --- 1) You close the bin view only. The bin still exists in the background it’s just hidden. What do you want perform with closing the bin? 2) Problem is known for all Kdenlive Windows versions. Root cause not found so far. Work around: hit space and the arrow key right. If Kdenlive seems blocked as you descript hit CTR+Space. Now the play heat starts from beginning and you can click with the mouse into the timeline to play from there. Ones Kdenlive crashes with clicking into the timeline please post the error message from the event viewer: windows+r -> eventvwr -> check the error messages with Kdenlive. -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 303483] 4.10 tracking bug
https://bugs.kde.org/show_bug.cgi?id=303483 bakabakatou...@outlook.fr changed: What|Removed |Added CC||bakabakatou...@outlook.fr -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 397024] Wrong date choice when a schedule transaction is recognised
https://bugs.kde.org/show_bug.cgi?id=397024 --- Comment #5 from Thomas Baumgart --- I took a look at the french translation: #: kmymoney/kmymoney.cpp:702 kmymoney/views/kgloballedgerview.cpp:262 #: kmymoney/views/kgloballedgerview.cpp:1700 #, kde-format msgctxt "Button text for match transaction" msgid "Match" msgstr "Correspond" #: kmymoney/views/kgloballedgerview.cpp:332 #, kde-format msgctxt "Button text for unmatch transaction" msgid "Unmatch" msgstr "Supprimer la mise en correspondance" Maybe that text "Supprimer la mise en correspondance" is too long and does not get applied to the button so that it stays with "Correspond". In the original version it switches between Match and Unmatch. The problem seems to be with the button text, but that is a translation issue I don't have under control. The logic is working. Could be, that the same applies to German. There is also a long text, but I have not checked. #: kmymoney/views/kgloballedgerview.cpp:332 #, kde-format msgctxt "Button text for unmatch transaction" msgid "Unmatch" msgstr "Zuordnung rückgängig machen" -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 388064] cl...@idig.za.net
https://bugs.kde.org/show_bug.cgi?id=388064 fritzib...@gmx.net changed: What|Removed |Added CC||fritzib...@gmx.net --- Comment #1 from fritzib...@gmx.net --- Problem is known for all Kdenlive Windows versions. Root cause not found so far. Work around: hit space and the arrow key right. If Kdenlive seems blocked as you descript hit CTR+Space. Now the play heat starts from beginning and you can click with the mouse into the timeline to play from there. Ones Kdenlive crashes with clicking into the timeline please post the error message from the event viewer: windows+r -> eventvwr -> check the error messages with Kdenlive. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397215] Visual bug around the maximize/unmaximize button
https://bugs.kde.org/show_bug.cgi?id=397215 --- Comment #3 from Dr. Chapatin --- X11. I have never seen this bug under Wayland. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 397184] Amarok corrupts ogg files
https://bugs.kde.org/show_bug.cgi?id=397184 Heiko Becker changed: What|Removed |Added Status|REOPENED|NEEDSINFO CC||heire...@exherbo.org Resolution|--- |WAITINGFORINFO --- Comment #8 from Heiko Becker --- I can't reproduce the problem with the attached file and the VLC Phonon backend. Additionally 2.8.0 isn't supported anymore. Can you please try to update to 2.9.0 and see if the problem persists? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 389831] DIVIDE AUDIO AND VIDEO
https://bugs.kde.org/show_bug.cgi?id=389831 fritzib...@gmx.net changed: What|Removed |Added CC||fritzib...@gmx.net --- Comment #1 from fritzib...@gmx.net --- Click on the green light in the track to switch of the target (you set the target to video 1 and Audio 1). Try again. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 389988] When rendering I get audio but no video
https://bugs.kde.org/show_bug.cgi?id=389988 fritzib...@gmx.net changed: What|Removed |Added CC||fritzib...@gmx.net --- Comment #1 from fritzib...@gmx.net --- Do you have enabled the video track before rendering? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 391493] falta botones de reproducción en panel clip de texto en kdenlive 17.12 español
https://bugs.kde.org/show_bug.cgi?id=391493 fritzib...@gmx.net changed: What|Removed |Added CC||fritzib...@gmx.net --- Comment #1 from fritzib...@gmx.net --- 1) Can you click on this text? If not something is wrong. 2) Problem is known for all Kdenlive Windows versions. Root cause not found so far. Work around: hit space and the arrow key right. If Kdenlive seems blocked as you descript hit CTR+Space. Now the play heat starts from beginning and you can click with the mouse into the timeline to play from there. Ones Kdenlive crashes with clicking into the timeline please post the error message from the event viewer: windows+r -> eventvwr -> check the error messages with Kdenlive. (com Google) 1)¿Puedes hacer clic en este texto? Si no, algo está mal. 2) El problema es conocido para todas las versiones de Kdenlive Windows. Causa raíz no encontrada hasta ahora. Solución: pulse el espacio y la tecla de flecha derecha. Si Kdenlive parece estar bloqueado mientras escribes, presiona CTR + Espacio. Ahora el calor de juego comienza desde el principio y puede hacer clic con el mouse en la línea de tiempo para jugar desde allí. Ones Kdenlive se bloquea al hacer clic en la línea de tiempo, publique el mensaje de error del visor de eventos: windows + r -> eventvwr -> verifique los mensajes de error con Kdenlive. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 380271] Text in input fields are hard to see on BreezeDark and other dark themes
https://bugs.kde.org/show_bug.cgi?id=380271 fritzib...@gmx.net changed: What|Removed |Added CC||fritzib...@gmx.net --- Comment #2 from fritzib...@gmx.net --- Try the “Breeze High Contrast” design. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 394123] Problems with the work of some options
https://bugs.kde.org/show_bug.cgi?id=394123 fritzib...@gmx.net changed: What|Removed |Added CC||fritzib...@gmx.net --- Comment #1 from fritzib...@gmx.net --- Number 1: strange. Has something to do with access rights. From where (drive, path) do you run Kdenlive? Number 2: Problem is known for all Kdenlive Windows versions. Root cause not found so far. Work around: hit space and the arrow key right. If Kdenlive seems blocked as you descript hit CTR+Space. Now the play heat starts from beginning and you can click with the mouse into the timeline to play from there. Ones Kdenlive crashes with clicking into the timeline please post the error message from the event viewer: windows+r -> eventvwr -> check the error messages with Kdenlive. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 384151] Kdenlive in Windows: playback hangs until I click on the timeline
https://bugs.kde.org/show_bug.cgi?id=384151 fritzib...@gmx.net changed: What|Removed |Added CC||fritzib...@gmx.net --- Comment #3 from fritzib...@gmx.net --- Problem is known for all Kdenlive Windows version. Root cause not found so far. Work around: hit space and the arrow key right. If Kdenlive seems blocked as you descript hit CTR+Space. Now the play heat starts from beginning and you can click with the mouse into the timeline to play from there. Ones Kdenlive crashes with clicking into the timeline please post the error message from the event viewer: windows+r -> eventvwr -> check the error messages with Kdenlive. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 393836] 3 application processes are persist in memory after closing main kdenlive window
https://bugs.kde.org/show_bug.cgi?id=393836 fritzib...@gmx.net changed: What|Removed |Added CC||fritzib...@gmx.net --- Comment #1 from fritzib...@gmx.net --- Created attachment 114338 --> https://bugs.kde.org/attachment.cgi?id=114338&action=edit Kdenlive-kill Bug known. Solution (root cause) unknown. Workaround: Run attached batch file before you start Kdenlive or after you close it. This will kill all running instances. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395014] Downloaded videos do not show
https://bugs.kde.org/show_bug.cgi?id=395014 fritzib...@gmx.net changed: What|Removed |Added CC||fritzib...@gmx.net --- Comment #1 from fritzib...@gmx.net --- Which video file type you put into the time line? You have to drag and drop the video first to the bin and from there to the timeline. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 394300] Kdenlive stops responding after playing a clip (windows - 18-04-1)
https://bugs.kde.org/show_bug.cgi?id=394300 fritzib...@gmx.net changed: What|Removed |Added CC||fritzib...@gmx.net --- Comment #1 from fritzib...@gmx.net --- Problem is known for all Kdenlive Windows version. Root cause not found so far. Work around: hit space and the arrow key right. If Kdenlive seems blocked as you descript hit CTR+Space. Now the play heat starts from beginning and you can click with the mouse into the timeline to play from there. Ones Kdenlive crashes with clicking into the timeline please post the error message from the event viewer: windows+r -> eventvwr -> check the error messages with Kdenlive. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 397184] Amarok corrupts ogg files
https://bugs.kde.org/show_bug.cgi?id=397184 --- Comment #7 from Nate Graham --- Thanks Tristan. You are correct, but they are somewhat related (GStreamer is now more tolerant and can read the corrupted files). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397219] New: Visual Studio Code crashed
https://bugs.kde.org/show_bug.cgi?id=397219 Bug ID: 397219 Summary: Visual Studio Code crashed Product: kwin Version: 5.13.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: shadabfaiz...@gmail.com Target Milestone: --- Application: kwin_x11 (5.13.3) Qt Version: 5.10.1 Frameworks Version: 5.48.0 Operating System: Linux 4.17.11-200.fc28.x86_64 x86_64 Distribution: "Fedora release 28 (Twenty Eight)" -- Information about the crash: - What I was doing when the application crashed: I had two instance of vscode opened. One ws running angular and another one was running node server. Addionally, a MySql Workbench, Chrome, Postman were opened. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5e6c8cf940 (LWP 1674))] Thread 7 (Thread 0x7f5e3f3dd700 (LWP 5427)): #0 0x7ffde2d52b49 in clock_gettime () #1 0x7f5e62c39cb6 in clock_gettime () from /lib64/libc.so.6 #2 0x7f5e63aed455 in qt_gettime() () from /lib64/libQt5Core.so.5 #3 0x7f5e63aebf2d in QTimerInfoList::updateCurrentTime() () from /lib64/libQt5Core.so.5 #4 0x7f5e63aec339 in QTimerInfoList::timerWait(timespec&) () from /lib64/libQt5Core.so.5 #5 0x7f5e63aeb374 in QEventDispatcherUNIX::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f5e63a9c12b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7f5e638ea9c6 in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7f5e6aaab3a9 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #9 0x7f5e638ef11d in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #10 0x7f5e65db2594 in start_thread () from /lib64/libpthread.so.0 #11 0x7f5e62c2c0df in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f5e26e23700 (LWP 3649)): #0 0x7f5e62c21756 in ppoll () from /lib64/libc.so.6 #1 0x7f5e63ae9e55 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /lib64/libQt5Core.so.5 #2 0x7f5e63aeb159 in QEventDispatcherUNIX::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #3 0x7f5e63a9c12b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f5e638ea9c6 in QThread::exec() () from /lib64/libQt5Core.so.5 #5 0x7f5e6aaab3a9 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #6 0x7f5e638ef11d in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7f5e65db2594 in start_thread () from /lib64/libpthread.so.0 #8 0x7f5e62c2c0df in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f5e265e2700 (LWP 1950)): #0 0x7f5e65db852c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5e6bb219f8 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from /lib64/libQt5Script.so.5 #2 0x7f5e6bb21a63 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /lib64/libQt5Script.so.5 #3 0x7f5e65db2594 in start_thread () from /lib64/libpthread.so.0 #4 0x7f5e62c2c0df in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f5e3e61f700 (LWP 1848)): #0 0x7f5e62c21756 in ppoll () from /lib64/libc.so.6 #1 0x7f5e63ae9e55 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /lib64/libQt5Core.so.5 #2 0x7f5e63aeb159 in QEventDispatcherUNIX::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #3 0x7f5e63a9c12b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f5e638ea9c6 in QThread::exec() () from /lib64/libQt5Core.so.5 #5 0x7f5e6aaab3a9 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #6 0x7f5e638ef11d in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7f5e65db2594 in start_thread () from /lib64/libpthread.so.0 #8 0x7f5e62c2c0df in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f5e45666700 (LWP 1699)): #0 0x7f5e62c21756 in ppoll () from /lib64/libc.so.6 #1 0x7f5e63ae9e55 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /lib64/libQt5Core.so.5 #2 0x7f5e63aeb159 in QEventDispatcherUNIX::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #3 0x7f5e63a9c12b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f5e638ea9c6 in QThread::exec() () from /lib64/libQt5Core.so.5 #5 0x7f5e6c98f299 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #6 0x7f5e638ef11d in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7f5e65db2594 in start_thread () from /lib64/libpthread.so.0 #8 0x7f5e62c2c0df in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f5e470e6700 (LWP 1680)): #0 0x7f5e62c21659 in poll () from /lib64/libc.so.6 #1 0x7f5e652a304f in _xcb_conn_wait () from /lib64/libxcb.so.1 #2
[amarok] [Bug 397184] Amarok corrupts ogg files
https://bugs.kde.org/show_bug.cgi?id=397184 Tristan Miller changed: What|Removed |Added CC||psychon...@nothingisreal.co ||m --- Comment #6 from Tristan Miller --- (In reply to Nate Graham from comment #2) > This is a bug in GStreamer that was fixed in a 1.12.x bugfix release. see > https://bugzilla.gnome.org/show_bug.cgi?id=784530 > > If Debian's version is older than that, you might ask them to backport the > fix. I am the reporter of the GStreamer bug. This Amarok bug is not the same. As far as I know, the GStreamer bug only affects how Vorbis files are read. This bug is about Amarok corrupting files (i.e., writing to them) when they are played. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 394408] crash after editing a title and coming back to timeline
https://bugs.kde.org/show_bug.cgi?id=394408 fritzib...@gmx.net changed: What|Removed |Added CC||fritzib...@gmx.net --- Comment #1 from fritzib...@gmx.net --- When the crash occurs again please run event viewer: windows+r -> eventvwr -> check the error field and post the error related with Kdenlive. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397218] inaccurate Layer -> Transform -> Offset when canvas size is 2048x2048. I input X:64px offset to a 64x64 content, it made 63px offset instead of 64px. When input is X:65px, it made
https://bugs.kde.org/show_bug.cgi?id=397218 bryanlong...@gmail.com changed: What|Removed |Added Summary|inaccurate Layer -> Offset |inaccurate Layer -> |when canvas size is |Transform -> Offset when |2048x2048. I input X:64px |canvas size is 2048x2048. I |offset to a 64x64 content, |input X:64px offset to a |it made 63px offset instead |64x64 content, it made 63px |of 64px. When input is |offset instead of 64px. |X:65px, it made 65px|When input is X:65px, it |offset. There is no way to |made 65px offset. There is |make accurate 64px offset. |no way to make accurate ||64px offset. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397218] New: inaccurate Layer -> Offset when canvas size is 2048x2048. I input X:64px offset to a 64x64 content, it made 63px offset instead of 64px. When input is X:65px, it made 65px of
https://bugs.kde.org/show_bug.cgi?id=397218 Bug ID: 397218 Summary: inaccurate Layer -> Offset when canvas size is 2048x2048. I input X:64px offset to a 64x64 content, it made 63px offset instead of 64px. When input is X:65px, it made 65px offset. There is no way to make accurate 64px offset. Product: krita Version: 4.1.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: critical Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: bryanlong...@gmail.com Target Milestone: --- Created attachment 114337 --> https://bugs.kde.org/attachment.cgi?id=114337&action=edit This is a youtube video link which reproduces the described bug To reproduce this bug. Follow the steps done in the attached youtube video. For smaller canvas size, it works. However, for 2048x2048, it has this problem. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 397010] Context menu hides after ~1 second in some cases (e.g. on objects below horizon)
https://bugs.kde.org/show_bug.cgi?id=397010 Jasem Mutlaq changed: What|Removed |Added Version Fixed In||2.9.8 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 397184] Amarok corrupts ogg files
https://bugs.kde.org/show_bug.cgi?id=397184 Nate Graham changed: What|Removed |Added Priority|NOR |VHI Severity|grave |critical -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 397184] Amarok corrupts ogg files
https://bugs.kde.org/show_bug.cgi?id=397184 Nate Graham changed: What|Removed |Added Resolution|UPSTREAM|--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 397214] Context info vanishes after a second if drawn above location
https://bugs.kde.org/show_bug.cgi?id=397214 Jasem Mutlaq changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||2.9.8 --- Comment #1 from Jasem Mutlaq --- This is fixed in the next release. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 387849] Display and Monitor: Scale Display should also apply to Gtk apps
https://bugs.kde.org/show_bug.cgi?id=387849 Nate Graham changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- Assignee|plasma-b...@kde.org |se...@kde.org Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 387849] Display and Monitor: Scale Display should also apply to Gtk apps
https://bugs.kde.org/show_bug.cgi?id=387849 --- Comment #12 from Nate Graham --- *** Bug 397217 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 397217] Do whatever's necessary to make scaling apply to GTK apps too
https://bugs.kde.org/show_bug.cgi?id=397217 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Nate Graham --- Actually this was silly. There's no reason to open a new bug when I can just re-open Bug 387849. *** This bug has been marked as a duplicate of bug 387849 *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 387849] Display and Monitor: Scale Display should also apply to Gtk apps
https://bugs.kde.org/show_bug.cgi?id=387849 --- Comment #11 from Nate Graham --- Peter, sadly this broke some people and had to be reverted in Bug 389523. Since GDK_SCALE only supports integers, perhaps we could only conditionally set GDK_SCALE and GDK_DPI_SCALE if $kdeglobals_kscreen_scalefactor is also an integer. What do you think? -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 397184] Amarok corrupts ogg files
https://bugs.kde.org/show_bug.cgi?id=397184 --- Comment #5 from jeromec...@laposte.net --- I confirm it is the same issue ;) And I am formal: Amarok corrupts the headers. The GStreamer issue you linked only solves the question "how to play corrupted files?" but it does not solve the source issue which is "Why does Amarok corrupt ogg files?". So, maybe we should re-open this bug case? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389523] GDK_DPI_SCALE seems to have changed with the latest updates to 0.571429. Firefox, Chromium and Thunderbird now have tiny fonts on a hidpi screen despite existing settings to
https://bugs.kde.org/show_bug.cgi?id=389523 --- Comment #7 from Nate Graham --- Let's give this another go in Bug 397217. One final note: the Force Fonts DPI setting is not intended to be used as a systemwide scale factor system. Using that in conjunction with the Scaling in the Display & Monitor KCM is asking for trouble. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397215] Visual bug around the maximize/unmaximize button
https://bugs.kde.org/show_bug.cgi?id=397215 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #2 from David Edmundson --- Both look pretty broken X or wayland? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 397217] Do whatever's necessary to make scaling apply to GTK apps too
https://bugs.kde.org/show_bug.cgi?id=397217 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=389523 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389523] GDK_DPI_SCALE seems to have changed with the latest updates to 0.571429. Firefox, Chromium and Thunderbird now have tiny fonts on a hidpi screen despite existing settings to
https://bugs.kde.org/show_bug.cgi?id=389523 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=397217 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 397217] Do whatever's necessary to make scaling apply to GTK apps too
https://bugs.kde.org/show_bug.cgi?id=397217 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=387849 -- You are receiving this mail because: You are watching all bug changes.
