[krita] [Bug 467257] New: File layers do not get scaled when scaling document
https://bugs.kde.org/show_bug.cgi?id=467257 Bug ID: 467257 Summary: File layers do not get scaled when scaling document Classification: Applications Product: krita Version: 5.1.5 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Resize/Scale Image/Layer Assignee: krita-bugs-n...@kde.org Reporter: zoomula...@gmail.com Target Milestone: --- Created attachment 157224 --> https://bugs.kde.org/attachment.cgi?id=157224&action=edit A test image + a series of 3 images showing the unexpected behavior SUMMARY Using file layers in a document and scaling the image either by "image -> scale image to new size" or via the "file -> export advanced" will result in the file-layers being cropped to the new size instead of scaled. STEPS TO REPRODUCE 1. Add a File Layer to a Krita document. I imported PNG files. 2. Scale the image to a new size, like 50% 3. The image's dimensions are changed but the file layer is just cropped instead of scaled. OBSERVED RESULT The file layer is not scaled with the rest of the image EXPECTED RESULT The contents of the file layer should match the new scale of the image SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION This is possibly related to an old bug 349821 where transforming file layers seems out of the question at first but is later marked as resolved fixed. -- You are receiving this mail because: You are watching all bug changes.
[kwordquiz] [Bug 467585] New: The Question & Answer quiz should be case-insensitive.
https://bugs.kde.org/show_bug.cgi?id=467585 Bug ID: 467585 Summary: The Question & Answer quiz should be case-insensitive. Classification: Applications Product: kwordquiz Version: 21.12.1 Platform: Slackware OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: pe...@peterandlinda.com Reporter: kimaya.ch...@gmail.com CC: aa...@kde.org Target Milestone: --- The Question & Answer quiz marks an answer as 'wrong' when the answer is in a different case as it is in the Editor. STEPS TO REPRODUCE 1. Type something in Column 1 and Column 2. 2. Select Question & Answer. 3. Type the answer in with at least one character different case than it was entered in the Editor. OBSERVED RESULT It marks the answer as 'wrong'. EXPECTED RESULT I expected the answer to be correct, as the answer should not be case-sensitive. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.23.5 (available in About System) KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I would like an option, such as a checkbox, to specify whether I want the answer to be case-sensitive or not. -- You are receiving this mail because: You are watching all bug changes.
[kwordquiz] [Bug 467585] The Question & Answer quiz should be case-insensitive.
https://bugs.kde.org/show_bug.cgi?id=467585 --- Comment #2 from Kim --- (In reply to Albert Astals Cid from comment #1) > Where do you think that option makes sense? > > As an new column where you can set it per each of the rows? > > Or as a configure option in the Settings -> Configure -> Quiz section? > > I'm thinking more on the second. Yes, the second option sounds better. -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 481103] flatpak installation on Ubuntu - after loading files from directory, cannot save.
https://bugs.kde.org/show_bug.cgi?id=481103 --- Comment #5 from Kim --- SOLVED I used flatseal to add host file permissions and now it works as expected, so no problem with kgeotag, just another system to learn. Can also use "sudo flatpak override [app id] --filesystem=host" Thanks for the tips -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 481103] New: flatpak installation on Ubuntu - after loading files from directory, cannot save.
https://bugs.kde.org/show_bug.cgi?id=481103
Bug ID: 481103
Summary: flatpak installation on Ubuntu - after loading files
from directory, cannot save.
Classification: Applications
Product: kgeotag
Version: 1.5.0
Platform: Ubuntu
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: General
Assignee: t...@stonemx.de
Reporter: kit...@gmail.com
Target Milestone: ---
SUMMARY
Using the flatpak v1.5.0 on Ubuntu, and loading files from directory
("file->Add all images and tracks from a folder") it will load all files, but
after tagging, cannot save them.
Using kgeotag v1.4.0 ubuntu .deb from repository for ubuntu 23.10, all works as
expected
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
STEPS TO REPRODUCE
1.
2.
3.
OBSERVED RESULT
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[kgeotag] [Bug 481103] flatpak installation on Ubuntu - after loading files from directory, cannot save.
https://bugs.kde.org/show_bug.cgi?id=481103 --- Comment #1 from Kim --- flatpak installation on ubuntu 22.04 read all files from directory reads OK, from /run/user/1000/doc/70be0a1a/Photos/IMG_20170827_132616.jpg (eg) tries to write back to /run/flatpak/doc/70be0a1a/Photos/IMG_20160921_143850.jpg.orig which does not exist installation of version 1.4.0 from ubuntu repositories on 23.10 works perfectly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448420] Autohide panel shown in tablet mode when rotated
https://bugs.kde.org/show_bug.cgi?id=448420 --- Comment #5 from kim --- It seen this bug came back in 5.24 - it is present i Fedora 35 packages -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 444654] New: segfault upon exit/save
https://bugs.kde.org/show_bug.cgi?id=444654 Bug ID: 444654 Summary: segfault upon exit/save Product: kdiff3 Version: 1.9.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: reeves...@gmail.com Reporter: kim-kde...@roedderne.dk Target Milestone: --- Application: kdiff3 (1.9.3 (64 bit)) Qt Version: 5.15.2 Frameworks Version: 5.87.0 Operating System: Linux 5.14.14-300.fc35.x86_64 x86_64 Windowing System: X11 Drkonqi Version: 5.22.5 Distribution: "Fedora release 35 (Thirty Five)" -- Information about the crash: - What I was doing when the application crashed: I use kdiff3 as merger for rpmconf,and upon exiting / saveing kdiff3 it segfaults - seeming before saving. Used to work in Fedora 34. The crash can be reproduced every time. -- Backtrace: Application: KDiff3 (kdiff3), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7ff0b32695c0 (LWP 54475))] [KCrash Handler] #6 0x556b44fa3af7 in KDiff3App::slotUpdateAvailabilities (this=0x556b45a1f5d0) at /usr/src/debug/kdiff3-1.9.3-1.fc35.x86_64/src/pdiff.cpp:2094 #7 0x7ff0b78dd3a9 in QtPrivate::QSlotObjectBase::call (a=0x7ffc53a011e0, r=, this=0x556b45cf7530) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #8 doActivate (sender=0x7ffc53a01a80, signal_index=22, argv=0x7ffc53a011e0) at kernel/qobject.cpp:3886 #9 0x7ff0b78d8327 in QMetaObject::activate (sender=, m=m@entry=0x7ff0b88a64c0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc53a011e0) at kernel/qobject.cpp:3946 #10 0x7ff0b837ec3f in QApplication::focusChanged (this=, _t1=, _t2=) at .moc/moc_qapplication.cpp:244 #11 0x7ff0b8384ddf in QApplication::setActiveWindow (act=act@entry=0x0) at kernel/qapplication.cpp:2043 #12 0x7ff0b83a97ff in QWidgetPrivate::deactivateWidgetCleanup (this=this@entry=0x556b45ac56b0) at kernel/qwidget.cpp:2298 #13 0x7ff0b83b6cc9 in QWidgetPrivate::hide_sys (this=this@entry=0x556b45ac56b0) at kernel/qwidget.cpp:7994 #14 0x7ff0b83bdca8 in QWidgetPrivate::hide_helper (this=this@entry=0x556b45ac56b0) at kernel/qwidget.cpp:7937 #15 0x7ff0b83c2b78 in QWidgetPrivate::setVisible (this=0x556b45ac56b0, visible=) at kernel/qwidget.cpp:8133 #16 0x7ff0b83c2c56 in QWidget::setVisible (this=this@entry=0x556b459f12c0, visible=visible@entry=false) at kernel/qwidget.cpp:8044 #17 0x7ff0b859130e in QDialog::setVisible (this=0x556b459f12c0, visible=) at dialogs/qdialog.cpp:849 #18 0x7ff0b858ee15 in QDialog::~QDialog (this=0x556b459f12c0, __in_chrg=) at dialogs/qdialog.cpp:422 #19 0x556b44f707e9 in ProgressDialog::~ProgressDialog (this=, this=) at /usr/src/debug/kdiff3-1.9.3-1.fc35.x86_64/redhat-linux-build/src/kdiff3_autogen/EWIEGA46WW/../../../../src/progress.h:24 #20 ProgressDialog::~ProgressDialog (this=, this=) at /usr/src/debug/kdiff3-1.9.3-1.fc35.x86_64/redhat-linux-build/src/kdiff3_autogen/EWIEGA46WW/../../../../src/progress.h:24 #21 0x7ff0b78d278a in QObjectPrivate::deleteChildren (this=this@entry=0x556b45b13850) at kernel/qobject.cpp:2104 #22 0x7ff0b83be556 in QWidget::~QWidget (this=0x556b45a1f5d0, __in_chrg=) at kernel/qwidget.cpp:1522 #23 0x556b44f7de9d in KDiff3App::~KDiff3App (this=, this=) at /usr/src/debug/kdiff3-1.9.3-1.fc35.x86_64/src/kdiff3.cpp:532 #24 0x7ff0b8ed30b7 in KParts::Part::~Part (this=, __vtt_parm=, this=, __vtt_parm=) at /usr/src/debug/kf5-kparts-5.87.0-1.fc35.x86_64/src/part.cpp:58 #25 0x556b44f74e77 in KDiff3Part::~KDiff3Part (this=, this=) at /usr/src/debug/kdiff3-1.9.3-1.fc35.x86_64/src/kdiff3_part.cpp:84 #26 0x556b44f74ecd in KDiff3Part::~KDiff3Part (this=, this=) at /usr/src/debug/kdiff3-1.9.3-1.fc35.x86_64/src/kdiff3_part.cpp:84 #27 0x7ff0b78d278a in QObjectPrivate::deleteChildren (this=this@entry=0x556b4581c8f0) at kernel/qobject.cpp:2104 #28 0x7ff0b83be556 in QWidget::~QWidget (this=0x556b4590a750, __in_chrg=) at kernel/qwidget.cpp:1522 #29 0x556b44f719b7 in KDiff3Shell::~KDiff3Shell (this=, this=) at /usr/src/debug/kdiff3-1.9.3-1.fc35.x86_64/src/kdiff3_shell.cpp:83 #30 KDiff3Shell::~KDiff3Shell (this=, this=) at /usr/src/debug/kdiff3-1.9.3-1.fc35.x86_64/src/kdiff3_shell.cpp:83 #31 0x7ff0b78d3d31 in QObject::event (this=0x556b4590a750, e=0x556b45e710c0) at kernel/qobject.cpp:1301 #32 0x7ff0b8d04cbd in KXmlGuiWindow::event (this=0x556b4590a750, ev=0x556b45e710c0) at /usr/src/debug/kf5-kxmlgui-5.87.0-1.fc35.x86_64/src/kxmlguiwindow.cpp:219 #33 0x7ff0b8380443 in QApplicationPrivate::notify_helper (this=, receiver=0x556b4590a750, e=0x556b45e710c0) at kernel/qapplication.cpp:3632 #34 0x7ff0b78a9798 in QCoreApplication::notifyInternal2 (receiver=0x556b4590a750, event=0x556b45e710c0) at kernel/qcoreapplication.cpp:1064 #35 0x7ff0b78acd06 in QCoreApplicationPrivate::sendPo
[kscreenlocker] [Bug 461326] New: Cannot login with SDDM after locking screen (unlock failed, user unknown in logs)
https://bugs.kde.org/show_bug.cgi?id=461326 Bug ID: 461326 Summary: Cannot login with SDDM after locking screen (unlock failed, user unknown in logs) Classification: Plasma Product: kscreenlocker Version: 5.26.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: greeter Assignee: plasma-b...@kde.org Reporter: stylinsonne...@gmail.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY When I start my laptop and log in, everything is fine. When I lock manually (meta + L) or my screen locks automatically, I can't log back to system. All I get is Unlock failed. When I switch to another tty I'm able to log in in root and my user. Journalctl gives me 'check pass; user unknown' when I try to unlock screen with sddm. But, when I try to unlock my screen with KDE Connect on iOS, it unlocks. It started as a random appearing problem, but now I am able to reproduce it any time i lock the screen. STEPS TO REPRODUCE 1. Lock screen by using shortcut/menu/automatically (after a period of time) 2. Try to unlock the screen with correct password to user 3. Unlocking failed with correct password 4. After several retries, I get faillock OBSERVED RESULT I get Unlock failed every time. Also, after 3 retries i get pam faillock. Unlocking with KDE Connect is working correctly, I am able to use my system. EXPECTED RESULT I can unlock my screen with SDDM. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7 Kernel Version: 6.0.6-arch1-1 (64-bit) KDE Connect for iOS version: 0.2.1 (2) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 461326] Cannot unlock after locking screen (unlock failed, user unknown in logs)
https://bugs.kde.org/show_bug.cgi?id=461326 --- Comment #2 from kim --- (In reply to Nate Graham from comment #1) > Some questions: > 1. How many screens do you have? > 2. Are you using fingerprint auth? > 3. Are you using any unusual or non-default PAM settings/configs/etc? 1. Only 1 screen (laptop) 2. No, only password (I have built-in fingerprint scanner but I haven't configured it) 3. No, I haven't touched these configs, they're default. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 461326] Cannot unlock after locking screen (unlock failed, user unknown in logs)
https://bugs.kde.org/show_bug.cgi?id=461326 --- Comment #3 from kim --- Also, this happens for me even when I try kscreenlocker_greet --testing -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 461326] Cannot unlock after locking screen (unlock failed, user unknown in logs)
https://bugs.kde.org/show_bug.cgi?id=461326 --- Comment #5 from kim --- (In reply to Nate Graham from comment #4) > Oh dear, that's bad. > > Can you paste the output in your terminal window when you click on the > "Unlock" button while running kscreenlocker_greet? That would be helpful, > thanks! i get this in terminal. tried with my theme (materia) and with setting default breeze theme, it has nothing to do with theme (i hope) $ /usr/lib/kscreenlocker_greet --testing file:///usr/share/plasma/look-and-feel/com.github.varlesh.materia-dark/contents/components/VirtualKeyboard.qml:20:1: module "QtQuick.VirtualKeyboard" is not installed Locked at 1667417697 qt.gui.icc: fromIccProfile: failed minimal tag size sanity -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 461326] Cannot unlock after locking screen (unlock failed, user unknown in logs)
https://bugs.kde.org/show_bug.cgi?id=461326
--- Comment #7 from kim ---
(In reply to Nate Graham from comment #6)
> Thanks. Does it help to install the Qt Virtual Keyboard module package, or
> does it make no difference?
No, still Unlock failed.
Locked at 1667579030
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
qt.virtualkeyboard.hunspell: Hunspell dictionary is missing for "en_US" .
Search paths ("/usr/share/qt/qtvirtualkeyboard/hunspell",
"/usr/share/hunspell", "/usr/share/myspell/dicts")
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 448420] Autohide panel shown in tablet mode when rotated
https://bugs.kde.org/show_bug.cgi?id=448420 kim changed: What|Removed |Added CC||kim-kde...@roedderne.dk --- Comment #2 from kim --- The same happens also: * after lockscreen ends. * energy save ends I would guess that it has to do with multi-screen discovery, but it is annoying with only one screen. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411014] Thumbnail Support for AFPHOTO files
https://bugs.kde.org/show_bug.cgi?id=411014 Kim changed: What|Removed |Added CC||s...@email.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425886] New: DigiKam Crashes immediately after hitting the search button for Images, both on regular and advanced search tool
https://bugs.kde.org/show_bug.cgi?id=425886 Bug ID: 425886 Summary: DigiKam Crashes immediately after hitting the search button for Images, both on regular and advanced search tool Product: digikam Version: 7.3.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Searches-Advanced Assignee: digikam-bugs-n...@kde.org Reporter: s...@email.com Target Milestone: --- Created attachment 131225 --> https://bugs.kde.org/attachment.cgi?id=131225&action=edit eventvwr files of crashes SUMMARY DigiKam Crashes immediately after hitting the search button for Images, both on regular and advanced search tool STEPS TO REPRODUCE 1. open up digikam on windows 10 2. >tools/search or /advanced search type in a date range 3. hit ok or start search. OBSERVED RESULT Digicam crashes almost instantaneously with error message "digikam.exe has stopped working" A problem caused the program to stop working correctly. please close the program. EXPECTED RESULT Find the images within the date range specified SOFTWARE/OS VERSIONS Windows: 10 pro macOS: - Linux/KDE Plasma: -- (available in About System) KDE Plasma Version: (can't find this anywhere) KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 (built against 5.14.2) ADDITIONAL INFORMATION Computer info. Ryzen 3950x Radeon VII 32gb ram 1TB gen4. pcie m.2 windows eventvwr files are attached -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425886] DigiKam Crashes immediately after hitting the search button for Images, both on regular and advanced search tool
https://bugs.kde.org/show_bug.cgi?id=425886 Kim changed: What|Removed |Added Attachment #131225|0 |1 is obsolete|| --- Comment #3 from Kim --- Created attachment 131316 --> https://bugs.kde.org/attachment.cgi?id=131316&action=edit Screenshot from DbgView.exe thank you for your reply, this is the best I could do, Dbgview.exe keeps crashing every time I try to save out the log file. so I had to do a screenshot of it. I the command line thing, but I could not get it to work. but I'm no programer/developer. but I will continue to try and figure that out. and if I do, I will send you that report as well. thank you for your help. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425886] DigiKam Crashes immediately after hitting the search button for Images, both on regular and advanced search tool
https://bugs.kde.org/show_bug.cgi?id=425886 --- Comment #5 from Kim --- Created attachment 131320 --> https://bugs.kde.org/attachment.cgi?id=131320&action=edit Dbgview.exe file Hi Gilles Caulier, thank you again for taking the time to try and help me. I would have been lost without your guidance. I'm probably still am. I hope I did it right, and that this helps in figuring this out. best regards Kim -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425886] DigiKam Crashes immediately after hitting the search button for Images, both on regular and advanced search tool
https://bugs.kde.org/show_bug.cgi?id=425886 --- Comment #8 from Kim --- Gilles, Here it is, Do do not really have permission to share this, I took it for the City in the picture. but I will make an exception since this can help digikam. I do not think that it would be abused! but I have to say it. the image in the link below is copyrighted and, no usage without prior written agreement. Thank you again. https://mega.nz/file/wzBWRK4Q#885H9rHqFTntcEatHgJfppzNgZFA9gu1c4V3XjD6-A4 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425886] DigiKam Crashes immediately after hitting the search button for Images, both on regular and advanced search tool
https://bugs.kde.org/show_bug.cgi?id=425886 --- Comment #10 from Kim --- Hi Maik Qualmann, If your comment is meant for me? I'm afraid I have no idea what you are saying. I would need it in with a spoon. (I'm not a Programer/developer) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425886] DigiKam Crashes immediately after hitting the search button for Images, both on regular and advanced search tool
https://bugs.kde.org/show_bug.cgi?id=425886 --- Comment #14 from Kim --- Thank you. It's pretty big, it's a wall banner size. let me know if I need to do something else. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425886] DigiKam Crashes immediately after hitting the search button for Images, both on regular and advanced search tool
https://bugs.kde.org/show_bug.cgi?id=425886 --- Comment #15 from Kim --- Hi Caulier, I have one more question for you. How do I know if "you" DigiKam fixed the problem? I cant seem to find any buttons that says look for updates, or something along those lines in the Program itself. Thank you for all your awesome work! best regards Kim -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 461326] Cannot unlock after locking screen (unlock failed, user unknown in logs)
https://bugs.kde.org/show_bug.cgi?id=461326 --- Comment #11 from kim --- trying to fix this for around 3 months, i tried removing kde and sddm configs, creating new users, removing everything related to kde connect, installing it again, chmod to chkpwd sudo and su, reinstalled plasma, sddm and applications and nothing. everything that works is unlocking with loginctl and kde connect. tried switching to lightdm and then understood that the problem is in the kscreenlocker. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398028] New: Assertion `csfi_fits` failing in simple C program with embedded Julia code.
https://bugs.kde.org/show_bug.cgi?id=398028
Bug ID: 398028
Summary: Assertion `csfi_fits` failing in simple C program with
embedded Julia code.
Product: valgrind
Version: 3.14 SVN
Platform: unspecified
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: lo...@schmider.kim
Target Milestone: ---
Julia (https://julialang.org) is a scripting language that can be embedded into
C. For reproduction, version 1.0 can be installed on Arch with `pacman -S
julia`.
This simple program that only initializes Julia and sends an exit message to
the garbage collector, cannot be inspected with Valgrind, as the error
> valgrind: m_debuginfo/debuginfo.c:737 (check_CFSI_related_invariants):
> Assertion 'cfsi_fits' failed.
is encountered:
#include
int main() {
jl_init();
jl_atexit_hook(0);
}
It can be compiled with
$ gcc -c -DJULIA_ENABLE_THREADING=1 -fPIC src.c && gcc src.o -ljulia -o testing
I was unable to find out what CFSI stands for, so I can give no further
details.
I have opened an issue at the Julia repository, but was informed that it is a
Valgrind issue. The Docs for Julia
(https://docs.julialang.org/en/stable/devdocs/valgrind/) advise certain steps
to use Valgrind with Julia, but none of them have helped and I believe that
those are only for free-standing Julia scripts, not C programs.
Here is the entire log: https://pastebin.com/raw/QtHtfvkb
My OS is Linux 4.18.5-arch1-1-ARCH x86_64 GNU/Linux
Thank you for your help!
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 398028] Assertion `csfi_fits` failing in simple C program with embedded Julia code.
https://bugs.kde.org/show_bug.cgi?id=398028 --- Comment #2 from Kim --- Hm, I'm trying for an hour and I just get > valgrind: failed to start tool 'memcheck' for platform 'amd64-linux': No such > file or directory changing the install prefix didn't help, even though there exists > /usr/lib/valgrind/memcheck-amd64-linux -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398028] Assertion `csfi_fits` failing in simple C program with embedded Julia code.
https://bugs.kde.org/show_bug.cgi?id=398028 --- Comment #4 from Kim --- Okay, I redownloaded and followed your steps for a successful build. The cfsi_fits assertion failure still persists, though. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 385699] New: Major lag cannot use Krita
https://bugs.kde.org/show_bug.cgi?id=385699 Bug ID: 385699 Summary: Major lag cannot use Krita Product: krita Version: 3.3.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: major Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: kimberlyd...@gmail.com Target Milestone: --- Hello, Krita was working great until last night. Then when trying to paint strokes with any brush on canvas it just lags (sits there really) and is not usable. I can click on file and the action I was attempting works,and go back to canvas, but this is impossible to use Krita this way, still a huge lag. Any thoughts? Thanks Kim -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 386129] New: Wrong brush painting on canvas
https://bugs.kde.org/show_bug.cgi?id=386129 Bug ID: 386129 Summary: Wrong brush painting on canvas Product: krita Version: 3.2.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: kimberlyd...@gmail.com Target Milestone: --- I imported tree brushes .gbr and the water brush is painting for each tree brush I try to use. The trees will not show up. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363284] [UGEE] Krita connects strokes with previous ones
https://bugs.kde.org/show_bug.cgi?id=363284 Kim changed: What|Removed |Added CC||kmbr...@yahoo.com --- Comment #38 from Kim --- Purchased a Ugee 19" art tablet. My daughter loves your program, and previously used it successfully on her old Wacom, but it is connecting strokes together on the Ugee. When lifting the pen, it ignores and connects to the next brush stroke. Please advise. I've read that there are other people having this same issue. Thank you, Kim -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 385034] New: Cannot click on brush preset ondocker
https://bugs.kde.org/show_bug.cgi?id=385034 Bug ID: 385034 Summary: Cannot click on brush preset ondocker Product: krita Version: 3.3.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: major Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: kimberlyd...@gmail.com Target Milestone: --- Created attachment 107998 --> https://bugs.kde.org/attachment.cgi?id=107998&action=edit screen shot of error When I go to Settings, Docker, then brush presets it is greyed out and I cannot select it. I even reinstalled Krita and did not work. I also can no longer install brushes. I have had the program about a week and loved using it. Please help. Thanks Kim -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 502048] save tiff to tiff make corrupt output file
https://bugs.kde.org/show_bug.cgi?id=502048 Kim changed: What|Removed |Added Summary|11 |save tiff to tiff make ||corrupt output file -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 502048] New: 11
https://bugs.kde.org/show_bug.cgi?id=502048 Bug ID: 502048 Summary: 11 Classification: Applications Product: digikam Version: 8.6.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: critical Priority: NOR Component: Showfoto-Save Assignee: digikam-bugs-n...@kde.org Reporter: crap...@gmail.com Target Milestone: --- Windows 11, and try on ubuntu to, its the same outcome. SUMMARY STEPS TO REPRODUCE 1. scan an image with epson in tiff 16bit 600dpi, app xsane 0.999 2. open file in showfoto 3. save file as new file (ctrl+shift+s) 4. now convert to jpg with First the one xsane made from the scan, the file raw_scan_001.tiff we open in showfoto and save: arkiv@Arkiv-PC5:~$ convert "/home/arkiv/Billeder/OCR/raw_scan_001.tiff" -quality 85 "/home/arkiv/Billeder/OCR/raw_scan_001.jpg" arkiv@Arkiv-PC5:~$ All good, now the one from xsane scan saved with ShowFoto, and its the same with the editor in Digcam, both linux on ubuntu and win 11 raw_scan_001_save1.tiff arkiv@Arkiv-PC5:~$ convert "/home/arkiv/Billeder/OCR/raw_scan_001_save1.tiff" -quality 85 "/home/arkiv/Billeder/OCR/raw_scan_001_save1.jpg" Afbrudt (SIGABRT) (smed kerne) OBSERVED RESULT no output of the jpg file it fails. i try to clean meta but then got other error, i then try to generate new file, and now i can make jpg but still with error Here i try to fiddel with it together with chatgpt i just try this it gives an output jpg but its still gives the error but now i get an jpg file, just not sure if its ok or not, so it looks like its some meta and some other stuff and now this one is left C5:~$ convert /home/arkiv/Billeder/OCR/raw_scan_001_save1.tiff -depth 16 -compress none /home/arkiv/Billeder/OCR/b0001_clean.tiff Afbrudt (SIGABRT) (smed kerne) arkiv@Arkiv-PC5:~$ exiftool -all= -overwrite_original "/home/arkiv/Billeder/OCR/raw_scan_001_save1.tiff" Warning: [minor] Can't delete IFD0 from TIFF - /home/arkiv/Billeder/OCR/raw_scan_001_save1.tiff 1 image files updated arkiv@Arkiv-PC5:~$ convert /home/arkiv/Billeder/OCR/raw_scan_001_save1.tiff -depth 16 -compress none /home/arkiv/Billeder/OCR/b0001_clean.tiff convert-im6.q16: Unknown field with tag 11 (0xb) encountered. TIFFReadDirectory' @ warning/tiff.c/TIFFWarnings/905. EXPECTED RESULT an output of my jpg file SOFTWARE/OS VERSIONS Windows: 11 ADDITIONAL INFORMATION i all so found out that in ubuntu its best to start the app with QT_QPA_PLATFORM=xcb showfoto else its really unstable and the editor window is laggy and some time app crash but its better when start with the command abow. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 505120] Dolphin stopped remembering the previous folders that were open since KDE 6.4 beta 1
https://bugs.kde.org/show_bug.cgi?id=505120 --- Comment #2 from Kim --- Thanks, now I've looked closer at the "Kubuntu Beta Builds" PPA and Dolphin isn't included. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 505120] New: Dolphin stopped remembering the previous folders that were open since KDE 6.4 beta 1
https://bugs.kde.org/show_bug.cgi?id=505120 Bug ID: 505120 Summary: Dolphin stopped remembering the previous folders that were open since KDE 6.4 beta 1 Classification: Applications Product: dolphin Version First 24.12.3 Reported In: Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: kim.bother...@djdvant.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Dolphin stopped remembering the previous folders that were open since KDE 6.4 beta 1 STEPS TO REPRODUCE 1. Open Dolphin 2. Open a folder other than /home/ 3. Close Dolphin 4. Open Dolphin 5. Dolphin has returned to the users home dir OBSERVED RESULT Dolphin is always opening in the home dir EXPECTED RESULT Dolphin should open with "Folders, Tabs, and window state from last time" as per the option in the "Interface" > "Folders & Tabs" page in the Dolphin config SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.4 beta 1 and beta 2 KDE Plasma Version: 6.3.91 KDE Frameworks Version: 6.14.0 Qt Version: 6.8.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 454589] New: kate crashes when I click Settings > Configure Kate
https://bugs.kde.org/show_bug.cgi?id=454589 Bug ID: 454589 Summary: kate crashes when I click Settings > Configure Kate Product: kate Version: 22.04.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: gnuykeat@gmail.com Target Milestone: --- Application: kate (22.04.1) Qt Version: 5.15.2 Frameworks Version: 5.94.0 Operating System: Linux 5.17.9-1-default x86_64 Windowing System: X11 Distribution: openSUSE Tumbleweed DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: TSIA. I have no previous config files at all (clean install). In order to be sure, I removed ~/.config/kate and retried, but no differences. The crash can be reproduced every time. -- Backtrace: Application: Kate (kate), signal: Segmentation fault [KCrash Handler] #4 0x7f275022768a in QMapData::root (this=0x30) at /usr/include/qt5/QtCore/qmap.h:208 #5 QMapData::findNode (this=0x30, akey=...) at /usr/include/qt5/QtCore/qmap.h:287 #6 0x7f275024da66 in QMap::constFind (akey=..., this=0x563828009d10) at /usr/include/qt5/QtCore/qmap.h:852 #7 KEntryMap::constFindEntry(QByteArray const&, QByteArray const&, QFlags) const [clone .isra.0] (this=this@entry=0x563828009d10, key=..., flags=..., flags@entry=..., group=...) at /usr/src/debug/kconfig-5.94.0-1.1.x86_64/src/core/kconfigdata.cpp:60 #8 0x7f27502270ee in KEntryMap::getEntry (group=..., expand=0x7ffcc9a7db47, flags=..., defaultValue=..., key=..., this=0x563828009d10) at /usr/src/debug/kconfig-5.94.0-1.1.x86_64/src/core/kconfigdata.cpp:217 #9 KConfigPrivate::lookupData (this=0x563828009cf0, group=..., key=, flags=..., expand=0x7ffcc9a7db47) at /usr/src/debug/kconfig-5.94.0-1.1.x86_64/src/core/kconfig.cpp:1061 #10 0x7f27502337a1 in KConfigGroup::readEntry (this=this@entry=0x563826c21930, key=key@entry=0x7f274964bf7b "View Style", aDefault=...) at /usr/src/debug/kconfig-5.94.0-1.1.x86_64/src/core/kconfiggroup.cpp:674 #11 0x7f27502339bb in KConfigGroup::readEntry (this=this@entry=0x563826c21930, key=key@entry=0x7f274964bf7b "View Style", aDefault=aDefault@entry=0x7f274964bf70 "DetailTree") at /usr/src/debug/kconfig-5.94.0-1.1.x86_64/src/core/kconfiggroup.cpp:659 #12 0x7f27495e5d5e in KDirOperator::readConfig (this=0x5638284a91c0, configGroup=...) at /usr/src/debug/kio-5.94.0-1.1.x86_64/src/filewidgets/kdiroperator.cpp:2436 #13 0x7f2748013300 in KateFileBrowser::readSessionConfig (this=0x563828496ff0, cg=...) at /usr/src/debug/kate-22.04.1-1.1.x86_64/addons/filebrowser/katefilebrowser.cpp:160 #14 0x7f2748016a98 in KateFileBrowserPluginView::createFileBrowser (this=0x563826e39640, visible=) at /usr/include/c++/12/bits/unique_ptr.h:191 #15 0x7f2748017655 in KateFileBrowserPluginView::createFileBrowser (visible=true, this=) at /usr/include/qt5/QtCore/qlist.h:117 #16 KateFileBrowserPlugin::configPage (this=0x563826aef2d0, number=, parent=0x563827da85d0) at /usr/src/debug/kate-22.04.1-1.1.x86_64/addons/filebrowser/katefilebrowserplugin.cpp:56 #17 0x563825ee754f in KateConfigDialog::addPluginPage (this=0x563827da85d0, plugin=0x563826aef2d0) at /usr/src/debug/kate-22.04.1-1.1.x86_64/kate/kateconfigdialog.cpp:306 #18 0x563825ea4622 in KateConfigDialog::addPluginPages (this=0x563827da85d0) at /usr/src/debug/kate-22.04.1-1.1.x86_64/kate/kateconfigdialog.cpp:286 #19 KateConfigDialog::KateConfigDialog (parent=, this=) at /usr/src/debug/kate-22.04.1-1.1.x86_64/kate/kateconfigdialog.cpp:63 #20 KateMainWindow::showPluginConfigPage (this=, configpageinterface=, id=) at /usr/src/debug/kate-22.04.1-1.1.x86_64/kate/katemainwindow.cpp:905 #21 0x7f274ecf1e1c in doActivate (sender=0x563826f0a050, signal_index=4, argv=0x7ffcc9a7e0c0) at kernel/qobject.cpp:3898 #22 0x7f274eceb0cf in QMetaObject::activate (sender=sender@entry=0x563826f0a050, m=m@entry=0x7f274fdb6d40, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffcc9a7e0c0) at kernel/qobject.cpp:3946 #23 0x7f274f89bb62 in QAction::triggered (this=this@entry=0x563826f0a050, _t1=) at .moc/moc_qaction.cpp:376 #24 0x7f274f89e7ab in QAction::activate (this=0x563826f0a050, event=) at kernel/qaction.cpp:1161 #25 0x7f274fa22612 in QMenuPrivate::activateCausedStack (this=this@entry=0x563826ce99a0, causedStack=..., action=action@entry=0x563826f0a050, action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at widgets/qmenu.cpp:1384 #26 0x7f274fa2a6e4 in QMenuPrivate::activateAction (this=0x563826ce99a0, action=0x563826f0a050, action_e=QAction::Trigger, self=) at widgets/qmenu.cpp:1461 #27 0x7f274f8e3f48 in QWidget::event (this=0x563826d2abb0, event=0x7ffcc9a7e6a0) at kernel/qwidget.cpp:9020 #28 0x7f274f8a237e in QApplicationPrivate::notify_helper (this=this
[dolphin] [Bug 466423] Directory listing goes to the right when going from details view -> compact -> details
https://bugs.kde.org/show_bug.cgi?id=466423 Kim Zedali changed: What|Removed |Added CC||qou43...@nezid.com --- Comment #2 from Kim Zedali --- I can confirm this also happens on Arch Linux, regardless of the theme. This bug basically forces users to re-open dolphin to make things work again, because all the entries and icons disappear. More information: dolphin 22.12.2-1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466423] Directory listing goes to the right when going from details view -> compact -> details
https://bugs.kde.org/show_bug.cgi?id=466423 Kim Zedali changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466423] Dolphin stops showing icons and entries, making it unusable
https://bugs.kde.org/show_bug.cgi?id=466423 Kim Zedali changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478556] With NVIDIA or AMD GPUs on X11, sometimes left or right clicking on windows of JetBrains apps or a Plasma panel instead interacts with Plasma desktop
https://bugs.kde.org/show_bug.cgi?id=478556 --- Comment #26 from Kim Andersen --- Will you please delete that clip, it was a wrong one I uploaded. On 12/04/2024 21.20, Oded Arbel wrote: > https://bugs.kde.org/show_bug.cgi?id=478556 > > Oded Arbel changed: > > What|Removed |Added > > Attachment #168426|1 |0 > is patch|| > Attachment #168426|text/plain |video/mp4 >mime type|| > -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478556] With NVIDIA or AMD GPUs on X11, sometimes left or right clicking on windows of JetBrains apps or a Plasma panel instead interacts with Plasma desktop
https://bugs.kde.org/show_bug.cgi?id=478556 --- Comment #23 from Kim Andersen --- Created attachment 168426 --> https://bugs.kde.org/attachment.cgi?id=168426&action=edit Wayland window layer bug This is another video showing how interacting with the window on top, affects the window beneath -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478556] With NVIDIA or AMD GPUs on X11, sometimes left or right clicking on windows of JetBrains apps or a Plasma panel instead interacts with Plasma desktop
https://bugs.kde.org/show_bug.cgi?id=478556 Kim Andersen changed: What|Removed |Added CC||k...@knas-webdesign.dk Attachment #168426|video/mp4 |text/plain mime type|| Attachment #168426|0 |1 is patch|| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478556] With NVIDIA or AMD GPUs on X11, sometimes left or right clicking on windows of JetBrains apps or a Plasma panel instead interacts with Plasma desktop
https://bugs.kde.org/show_bug.cgi?id=478556 --- Comment #24 from Kim Andersen --- Comment on attachment 168426 --> https://bugs.kde.org/attachment.cgi?id=168426 Wayland window layer bug > -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478556] With NVIDIA or AMD GPUs on X11, sometimes left or right clicking on windows of JetBrains apps or a Plasma panel instead interacts with Plasma desktop
https://bugs.kde.org/show_bug.cgi?id=478556 --- Comment #25 from Kim Andersen --- Comment on attachment 168426 --> https://bugs.kde.org/attachment.cgi?id=168426 Wayland window layer bug > ftypisomisomiso2avc1mp41moovlmvhdè!V@ötrak\tkhd!H@T$edtselst!Hnmdia mdhd2ªUÄ- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 430401] cmake searches unused dependency
https://bugs.kde.org/show_bug.cgi?id=430401 Kitae Kim changed: What|Removed |Added Resolution|--- |FIXED CC||devel...@gmail.com Status|REPORTED|RESOLVED --- Comment #1 from Kitae Kim --- This issue is fixed on commit 00f2dc1d888d7d09f0767eaeedfbcf01dec62786. Changing status to resolved. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435113] certain mouse settings resets after restart/resume from suspend/dock/undock
https://bugs.kde.org/show_bug.cgi?id=435113 Jeongu Kim changed: What|Removed |Added CC||souldominat...@gmail.com --- Comment #61 from Jeongu Kim --- I have the same issue but in Manjaro. In my case, `sudo udevadm trigger -s input` reproduces the bug. I use Logitech G304. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.17.3-1-MANJARO OS Type: 64-bit Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: RAM 31.3 GiB Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431226] plugins/extensions/pykrita/kritarunner: Missing dependency on ui_info.h and ui_manager.h
https://bugs.kde.org/show_bug.cgi?id=431226 --- Comment #6 from Kim Lindberger --- Okay, great! Thanks! On Thu, 2021-01-07 at 10:17 +, Halla Rempt wrote: > https://bugs.kde.org/show_bug.cgi?id=431226 > > --- Comment #5 from Halla Rempt --- > I'll also merge it to the stable and the release branches. > -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431226] plugins/extensions/pykrita/kritarunner: Missing dependency on ui_info.h and ui_manager.h
https://bugs.kde.org/show_bug.cgi?id=431226 --- Comment #10 from Kim Lindberger --- I think you applied the wrong patch to master and the stable branches, unless you wanted to go with yours instead. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431226] plugins/extensions/pykrita/kritarunner: Missing dependency on ui_info.h and ui_manager.h
https://bugs.kde.org/show_bug.cgi?id=431226 --- Comment #13 from Kim Lindberger --- Yeah, looks good! Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438330] New: Latte dock weird behaviour
https://bugs.kde.org/show_bug.cgi?id=438330 Bug ID: 438330 Summary: Latte dock weird behaviour Product: plasmashell Version: 5.22.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kwj69...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.22.0) Qt Version: 5.15.3 Frameworks Version: 5.82.0 Operating System: Linux 5.4.0-74-generic x86_64 Windowing System: Wayland Drkonqi Version: 5.22.0 Distribution: KDE neon User Edition 5.22 -- Information about the crash: - What I was doing when the application crashed: Login - Unusual behavior I noticed: Latte dock and widget not work properly - Custom settings of the application: added windows button widget, transparent when no window is maximized on latte The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [New LWP 17668] [New LWP 17718] [New LWP 17719] [New LWP 17720] [New LWP 17721] [New LWP 17738] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7ff33d56caff in __GI___poll (fds=0x7ffe58748f68, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7ff33979e8c0 (LWP 17634))] Thread 7 (Thread 0x7ff328ffb700 (LWP 17738)): #0 0x7ff33bdd7a0f in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7ff33bdd829b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff33bdd84a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff33db3ab3b in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7ff33dadedcb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff33d8f8bb2 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ff33f0f9559 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7ff33d8f9d4c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ff33c80a609 in start_thread (arg=) at pthread_create.c:477 #9 0x7ff33d579293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7ff32a45e700 (LWP 17721)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55c48a208f98) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55c48a208f48, cond=0x55c48a208f70) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55c48a208f70, mutex=0x55c48a208f48) at pthread_cond_wait.c:638 #3 0x7ff330b51b5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7ff330b5175b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7ff33c80a609 in start_thread (arg=) at pthread_create.c:477 #6 0x7ff33d579293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7ff32ac5f700 (LWP 17720)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55c48a208f98) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55c48a208f48, cond=0x55c48a208f70) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55c48a208f70, mutex=0x55c48a208f48) at pthread_cond_wait.c:638 #3 0x7ff330b51b5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7ff330b5175b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7ff33c80a609 in start_thread (arg=) at pthread_create.c:477 #6 0x7ff33d579293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7ff323fff700 (LWP 17719)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55c48a208f98) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55c48a208f48, cond=0x55c48a208f70) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55c48a208f70, mutex=0x55c48a208f48) at pthread_cond_wait.c:638 #3 0x7ff330b51b5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7ff330b5175b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7ff33c80a609 in start_thread (arg=) at pthread_create.c:477 #6 0x7ff33d579293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7ff32b460700 (LWP 17718)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55c48a208f98) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55c48a208f48, cond=0x55c48a208f70) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55c48a208f70, mutex=0x55c48a208f48) at pthread_cond_wait.c:638 #3 0x7ff330b51b5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #
[krita] [Bug 431226] New: plugins/extensions/pykrita/kritarunner: Missing dependency on ui_info.h and ui_manager.h
https://bugs.kde.org/show_bug.cgi?id=431226 Bug ID: 431226 Summary: plugins/extensions/pykrita/kritarunner: Missing dependency on ui_info.h and ui_manager.h Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: kim.lindber...@gmail.com Target Milestone: --- The pykrita/plugin target generates two required ui header files, ui_info.h and ui_manager.h, using the ki18n_wrap_ui macro. The source files are independently used by the pykrita/kritarunner target, which however doesn't generate the required header files. This means that when built in parallel, sometimes the pykrita/kritarunner target is built before the pykrita/plugin target and compilation fails with > /build/krita-4.1.8/plugins/extensions/pykrita/plugin/pyqtpluginsettings.cpp:19:10: > fatal error: ui_manager.h: No such file or directory > #include "ui_manager.h" > ^~ A full build output can be found here: https://gist.githubusercontent.com/worldofpeace/c8248ff92b0ced199124bdcfdb59420f/raw/b0b26769b6369146b6c7a110eaa3e230f81515be/krita.log When building Krita for NixOS, we're currently disabling building in parallel to avoid this, but that makes the builds extremely lengthy. This was also reported in https://bugs.kde.org/show_bug.cgi?id=407591. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431226] plugins/extensions/pykrita/kritarunner: Missing dependency on ui_info.h and ui_manager.h
https://bugs.kde.org/show_bug.cgi?id=431226 --- Comment #2 from Kim Lindberger --- That should work, but I opened a PR with a different solution at https://invent.kde.org/graphics/krita/-/merge_requests/640. I think that should be better in the long run, it should be easier to maintain and make it less likely that a similar issue occurs again (in kritarunner, that is). -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 408869] New: Akregator krash at starup on remote X session
https://bugs.kde.org/show_bug.cgi?id=408869 Bug ID: 408869 Summary: Akregator krash at starup on remote X session Product: akregator Version: 5.11.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: k...@itr.no Target Milestone: --- Application: akregator (5.11.2) Qt Version: 5.12.3 Frameworks Version: 5.59.0 Operating System: Linux 4.18.0-21-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: Trying to start Akregator over ssh -X session running akregator results in crash trying kstart and dbus-launch same result deleteting all akregtor related setups / caches / db etc , same result The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f588e8e7bc0 (LWP 31988))] Thread 22 (Thread 0x7f575ed7b700 (LWP 32041)): #0 0x7f587df38ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f575ed7a710, expected=0, futex_word=0x7f575ed7a8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f587df38ed9 in __pthread_cond_wait_common (abstime=0x7f575ed7a7b0, mutex=0x7f575ed7a8a8, cond=0x7f575ed7a8d0) at pthread_cond_wait.c:533 #2 0x7f587df38ed9 in __pthread_cond_timedwait (cond=0x7f575ed7a8d0, mutex=0x7f575ed7a8a8, abstime=0x7f575ed7a7b0) at pthread_cond_wait.c:667 #3 0x7f5884233b17 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f588423446a in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f5884234552 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f58841f4fb1 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f58841f74c7 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f58841f7ab4 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f5884236561 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f587df326db in start_thread (arg=0x7f575ed7b700) at pthread_create.c:463 #11 0x7f588a68488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7f575f7fe700 (LWP 32027)): #0 0x7f587df389f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f575f7fd908) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f587df389f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f575f7fd8b8, cond=0x7f575f7fd8e0) at pthread_cond_wait.c:502 #2 0x7f587df389f3 in __pthread_cond_wait (cond=0x7f575f7fd8e0, mutex=0x7f575f7fd8b8) at pthread_cond_wait.c:655 #3 0x7f5884233a49 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f5884234478 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f588423450f in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f58841f4fc8 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f58841f77f6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f58841f7b34 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f5884236561 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f587df326db in start_thread (arg=0x7f575f7fe700) at pthread_create.c:463 #11 0x7f588a68488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7f575700 (LWP 32026)): #0 0x7f588a6936ac in __lll_lock_wait_private () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95 #1 0x7f588a695474 in ___fprintf_chk (fp=0x7f588a9508b0 <_IO_stdfile_2_lock>, flag=1, format=0x7f58765756a8 "[%s] %s\n") at fprintf_chk.c:30 #2 0x7f587655d9ad in event_logv_ () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #3 0x7f587655db44 in event_warn () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #4 0x7f587655f46c in () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #5 0x7f5876555114 in event_base_loop () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #6 0x7f5884239c79 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f58841d42db in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f5884206311 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f5884236561 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f587df326db in start_thread (arg=0x7f575700) at pthread_create.c:463 #11 0x7f588a68488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f57f8a31700 (LWP 32025)): #0 0x7f587df38ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f57f8a30710, expected=0, futex_word=0x7f57f8a308f8) a
[kmail2] [Bug 389675] Filters work only when a message arrives
https://bugs.kde.org/show_bug.cgi?id=389675 Kim Lilliestierna changed: What|Removed |Added CC||k...@itr.no --- Comment #1 from Kim Lilliestierna --- Same behaviour here, my spam filter action is a shellscript runing crm114, adding some logging to it shows that the filter is run, the mail is marked, but kmail is not reading back the output of the filter. same for both imap and pop. distro: ubuntu 17.10 Kmail: 5.5.3 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 399815] New: Unable to disssable delte confirmation
https://bugs.kde.org/show_bug.cgi?id=399815 Bug ID: 399815 Summary: Unable to disssable delte confirmation Product: kmail2 Version: 5.9.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-b...@kde.org Reporter: k...@itr.no Target Milestone: --- SUMMARY No option for disabling delete message confirmation popup the "Delete Item" command previously silently deleted a message without annoying "Are you sure..." poppups, this is no longer the case and there seems to be no options in setting to turn off this irritating behaviour. STEPS TO REPRODUCE 1. Add "Delete Item" to menu 2. Press the above "Delete Item" or press 3. The confirmation pop up appears. OBSERVED RESULT The confirmation pop up appears. EXPECTED RESULT The message should silently be deleted. SOFTWARE VERSIONS Kmail version 5.9.1 Neon: KDE neon 5.13 KDE Plasma: 5.13.5 KDE Framevork 5.50.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 399815] Unable to disssable delete confirmation
https://bugs.kde.org/show_bug.cgi?id=399815 Kim Lilliestierna changed: What|Removed |Added Summary|Unable to disssable delte |Unable to disssable delete |confirmation|confirmation -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 380387] New: Crash on marking feed read
https://bugs.kde.org/show_bug.cgi?id=380387 Bug ID: 380387 Summary: Crash on marking feed read Product: kontact Version: 5.2.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: k...@itr.no Target Milestone: --- Application: kontact (5.2.3) Qt Version: 5.6.1 Frameworks Version: 5.33.0 Operating System: Linux 4.4.0-78-generic x86_64 Distribution: Ubuntu 16.04.2 LTS -- Information about the crash: Crashes semi consitently when wrying to mark a feed read. Usually ends up with several cash entries corrupted. Not allways the same feed. The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc7c57d5940 (LWP 28431))] Thread 40 (Thread 0x7fc6a8bfc700 (LWP 31581)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7fc6fa3a5cbc in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #2 0x7fc6fa06674d in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #3 0x7fc6fa3a5a88 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #4 0x7fc6fa3a5abe in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #5 0x7fc6fa3a5b20 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #6 0x7fc7d5abb6ba in start_thread (arg=0x7fc6a8bfc700) at pthread_create.c:333 #7 0x7fc7dbb3182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 39 (Thread 0x7fc6a93fd700 (LWP 31580)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7fc6fa3a5cbc in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #2 0x7fc6fa06674d in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #3 0x7fc6fa3a5a88 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #4 0x7fc6fa3a5abe in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #5 0x7fc6fa3a5b20 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #6 0x7fc7d5abb6ba in start_thread (arg=0x7fc6a93fd700) at pthread_create.c:333 #7 0x7fc7dbb3182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 38 (Thread 0x7fc6aa20a700 (LWP 31579)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7fc6fa3a5cbc in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #2 0x7fc6fa06674d in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #3 0x7fc6fa3a5a88 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #4 0x7fc6fa3a5abe in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #5 0x7fc6fa3a5b20 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #6 0x7fc7d5abb6ba in start_thread (arg=0x7fc6aa20a700) at pthread_create.c:333 #7 0x7fc7dbb3182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 37 (Thread 0x7fc6aaa0b700 (LWP 31578)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7fc6fa3a5cbc in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #2 0x7fc6fa06674d in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #3 0x7fc6fa3a5a88 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #4 0x7fc6fa3a5abe in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #5 0x7fc6fa3a5b20 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #6 0x7fc7d5abb6ba in start_thread (arg=0x7fc6aaa0b700) at pthread_create.c:333 #7 0x7fc7dbb3182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 36 (Thread 0x7fc6ab4fe700 (LWP 31573)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fc6fa3a5cfc in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #2 0x7fc6fa15e93c in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #3 0x7fc6fa3a5a88 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #4 0x7fc6fa3a5abe in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #5 0x7fc6fa3a5b20 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #6 0x7fc7d5abb6ba in start_thread (arg=0x7fc6ab4fe700) at pthread_create.c:333 #7 0x7fc7dbb3182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 35 (Thread 0x7fc6abcff700 (LWP 31572)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fc6fa3a5cfc in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #2 0x7fc6fa15e93c in ?? () from /usr/lib/adobe-flashplug
[kmail2] [Bug 394886] New: "Pipe Through" not piping
https://bugs.kde.org/show_bug.cgi?id=394886 Bug ID: 394886 Summary: "Pipe Through" not piping Product: kmail2 Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-b...@kde.org Reporter: k...@itr.no Target Milestone: --- The "Pipe Through" filter action does not pipe the email to the external program, not even on manual filtering. It is ofc intermittent and hard to reproduce reliably. I have the following script for running crm114 #!/bin/bash TIME=$(date +"%d/%m/%Y %H:%M:%S") LOG=~/logs/crmlog mkdir ~/logs &>/dev/null touch $LOG echo $TIME >>$LOG cp /dev/null ~/logs/copy exec crm -u $HOME/.crm114 mailreaver.crm | tee ~/logs/copy 2>> $LOG This will enter a time stamp in the log file and copy any data from the pipe into the "copy" file. When Kmail starts failing the filtering, the logs shows that the action was run, but the "copy" file only contains the crm114 header message indicating that the pipe was empty. there seems to be 3 workarounds none that work reliably all the time.. 1. remake the filter rule, its enough to edit the rule and resave. 2. stop and start akonadi, making sure the filter agent is restarted. 3. log out from the kde session or reboot One would think that rebooting would fix it, but have had cases where the filtering fails on a fresh reboot / login first time kmail session, where resaving the rule fixed it... -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 386348] New: XML format not recognized
https://bugs.kde.org/show_bug.cgi?id=386348 Bug ID: 386348 Summary: XML format not recognized Product: akregator Version: 5.4.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: feed parser Assignee: kdepim-b...@kde.org Reporter: k...@itr.no Target Milestone: --- The rss feed from webtoons,com does not seem to be recognized as valid url: http://www.webtoons.com/en/sf/dents/rss?title_no=671 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 386348] XML format not recognized
https://bugs.kde.org/show_bug.cgi?id=386348 --- Comment #2 from Kim Lilliestierna --- Created attachment 108654 --> https://bugs.kde.org/attachment.cgi?id=108654&action=edit dent xml rss aquired by curl http://www.webtoons.com/en/sf/dents/rss?title_no=671 > dents -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 374250] New: Article list empty
https://bugs.kde.org/show_bug.cgi?id=374250 Bug ID: 374250 Summary: Article list empty Product: akregator Version: 5.2.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: k...@itr.no Target Milestone: --- No articles are shown in the article list, even though the feed lists as having several, this is true for all feeds. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 384842] New: Reporting for VEX IR semantic bugs
https://bugs.kde.org/show_bug.cgi?id=384842 Bug ID: 384842 Summary: Reporting for VEX IR semantic bugs Product: valgrind Version: unspecified Platform: unspecified OS: unspecified Status: UNCONFIRMED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: soom...@kaist.ac.kr Target Milestone: --- Dear Valgrind team, Here at KAIST, Korea, we are doing a research project on testing the correctness of binary lifters. The system is named MeanDiff, which systematically finds semantic bugs by differential testing the lifted output of thousands generated x86 and x86-64 instructions. We will be presenting a paper on our system called "Testing Intermediate Representations for Binary Analysis" at ASE 2017. Valgrind's VEX lifter was included in our experiments and in result we have some bugs we would like to report. In our attempt of making the bug reports as concise as possible, we have made issues on your behalf on our Github page below: https://github.com/SoftSec-KAIST/MeanDiff/issues Here the different binary lifters, including yours, are labeled by name. In summary we found 4 unique bugs in VEX lifter. If you have any questions feel free to write us or comment on the Github issues. Best regards, Soomin Kim & Markus Faerevaag & Sang Kil Cha -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 384842] Reporting for VEX IR semantic bugs
https://bugs.kde.org/show_bug.cgi?id=384842 Soomin Kim changed: What|Removed |Added CC||soom...@kaist.ac.kr -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 381816] New: Crash on closing tab in feed reader
https://bugs.kde.org/show_bug.cgi?id=381816 Bug ID: 381816 Summary: Crash on closing tab in feed reader Product: kontact Version: 5.2.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: k...@itr.no Target Milestone: --- Application: kontact (5.2.3) Qt Version: 5.6.1 Frameworks Version: 5.34.0 Operating System: Linux 4.4.0-78-generic x86_64 Distribution: Ubuntu 16.04.2 LTS -- Information about the crash: Closed a tab in feed ( Akregator). Hapens with increasing frequency. not allways on the same feed, clearing out the corupted cash file sometimes helps for some time. The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd84bd2a940 (LWP 25556))] Thread 30 (Thread 0x7fd7737fe700 (LWP 26258)): #0 0x7fd86207db5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fd85b7e938c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd85b7e949c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd862bbb37b in QEventDispatcherGlib::processEvents (this=0x7fd7640008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7fd862b63ffa in QEventLoop::exec (this=this@entry=0x7fd7737fdc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fd86298c9e4 in QThread::exec (this=) at thread/qthread.cpp:500 #6 0x7fd862991808 in QThreadPrivate::start (arg=0x4b4fe80) at thread/qthread_unix.cpp:341 #7 0x7fd85c0136ba in start_thread (arg=0x7fd7737fe700) at pthread_create.c:333 #8 0x7fd86208982d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 29 (Thread 0x7fd773fff700 (LWP 26256)): #0 0x7fd864d24ab8 in update_get_addr (ti=0x7fd862daf748) at dl-tls.c:805 #1 0x7fd862990706 in get_thread_data () at thread/qthread_unix.cpp:184 #2 QThreadData::current (createIfNecessary=createIfNecessary@entry=true) at thread/qthread_unix.cpp:215 #3 0x7fd862bba9da in postEventSourcePrepare (s=0x7fd76c0012d0, timeout=0x7fd773ffeab4) at kernel/qeventdispatcher_glib.cpp:246 #4 0x7fd85b7e891d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fd85b7e92bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fd85b7e949c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fd862bbb37b in QEventDispatcherGlib::processEvents (this=0x7fd76c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #8 0x7fd862b63ffa in QEventLoop::exec (this=this@entry=0x7fd773ffec80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #9 0x7fd86298c9e4 in QThread::exec (this=) at thread/qthread.cpp:500 #10 0x7fd862991808 in QThreadPrivate::start (arg=0x4968840) at thread/qthread_unix.cpp:341 #11 0x7fd85c0136ba in start_thread (arg=0x7fd773fff700) at pthread_create.c:333 #12 0x7fd86208982d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 28 (Thread 0x7fd780fe4700 (LWP 26254)): #0 0x7fd86207db5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fd85b7e938c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd85b7e949c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd862bbb37b in QEventDispatcherGlib::processEvents (this=0x7fd7780008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7fd862b63ffa in QEventLoop::exec (this=this@entry=0x7fd780fe3c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fd86298c9e4 in QThread::exec (this=) at thread/qthread.cpp:500 #6 0x7fd862991808 in QThreadPrivate::start (arg=0x49b5930) at thread/qthread_unix.cpp:341 #7 0x7fd85c0136ba in start_thread (arg=0x7fd780fe4700) at pthread_create.c:333 #8 0x7fd86208982d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 27 (Thread 0x7fd7834ed700 (LWP 25786)): #0 0x7fd86207db5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fd85b7e938c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd85b7e949c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd862bbb37b in QEventDispatcherGlib::processEvents (this=0x7fd7740008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7fd862b63ffa in QEventLoop::exec (this=this@entry=0x7fd7834ecc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fd86298c9e4 in QThread::exec (this=) at thread/qthread.cpp:500 #6 0x7fd862991808 in QThreadPrivate::start (arg=0x45e7390) at thread/qthread_unix.cpp:341 #7 0x7fd85c0136ba in start_thread (arg=0x7fd7834ed700) at pth
[Akonadi] [Bug 504550] New: Kmail imap resource crashes when used outside of KDE
https://bugs.kde.org/show_bug.cgi?id=504550
Bug ID: 504550
Summary: Kmail imap resource crashes when used outside of KDE
Classification: Frameworks and Libraries
Product: Akonadi
Version First unspecified
Reported In:
Platform: openSUSE
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: IMAP resource
Assignee: kdepim-b...@kde.org
Reporter: redbird...@gmail.com
CC: c...@carlschwan.eu
Target Milestone: ---
Application: akonadi_imap_resource (6.4.1 (25.04.1))
ApplicationNotResponding [ANR]: false
Qt Version: 6.9.0
Frameworks Version: 6.14.0
Operating System: Linux 6.14.6-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 6.3.5 [CoredumpBackend]
-- Information about the crash:
Kmail 6.4.1 crashes outside KDE when trying to connect to the IMAP server. As I
understand it tries to get the password from the KWallet, but fails for some
reason.
KWallet is installed and is configured to start in my standalone WM
environment. Google Mail provider successfully gets its password from KWallet.
When I use Kmail from KDE IMAP resource doesn't crash and works normally.
The crash can be reproduced every time.
-- Backtrace:
Application: akonadi_imap_resource_6 (akonadi_imap_resource), signal:
Segmentation fault
warning: Can't open file
/fontconfig/93d69c8b359a0071e6d6913be98342f8-x86_64.cache-9 during file-backed
mapping note processing
[New LWP 33420]
[New LWP 33421]
[New LWP 33423]
[New LWP 33422]
[New LWP 33433]
[New LWP 33430]
[New LWP 33431]
[New LWP 33434]
[New LWP 33435]
[New LWP 33436]
[New LWP 33439]
[New LWP 33445]
[New LWP 33524]
[New LWP 33438]
[New LWP 33440]
[New LWP 33437]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/akonadi_imap_resource --identifier
akonadi_imap_resource_6'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x7f1c2f29b37c in __pthread_kill_implementation () from
/lib64/libc.so.6
[Current thread is 1 (Thread 0x7f1c29609cc0 (LWP 33420))]
Function(s) ^std::(move|forward|as_const|(__)?addressof) will be skipped when
stepping.
Function(s) ^std::(shared|unique)_ptr<.*>::(get|operator) will be skipped when
stepping.
Function(s)
^std::(basic_string|vector|array|deque|(forward_)?list|(unordered_|flat_)?(multi)?(map|set)|span)<.*>::(c?r?(begin|end)|front|back|data|size|empty)
will be skipped when stepping.
Function(s) ^std::(basic_string|vector|array|deque|span)<.*>::operator.] will
be skipped when stepping.
python sentry-sdk not installed :(
Cannot QML trace cores :(
/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py:547: DeprecationWarning:
datetime.datetime.utcfromtimestamp() is deprecated and scheduled for removal in
a future version. Use timezone-aware objects to represent datetimes in UTC:
datetime.datetime.fromtimestamp(timestamp, datetime.UTC).
boot_time =
datetime.utcfromtimestamp(psutil.boot_time()).strftime('%Y-%m-%dT%H:%M:%S')
/usr/share/drkonqi/gdb/python/gdb_preamble/preamble.py:564: DeprecationWarning:
datetime.datetime.utcnow() is deprecated and scheduled for removal in a future
version. Use timezone-aware objects to represent datetimes in UTC:
datetime.datetime.now(datetime.UTC).
'timestamp': datetime.utcnow().isoformat(),
[Current thread is 1 (Thread 0x7f1c29609cc0 (LWP 33420))]
Thread 16 (Thread 0x7f1c0a7fc6c0 (LWP 33437)):
#0 0x7f1c2f2a1c32 in __syscall_cancel_arch () at /lib64/libc.so.6
#1 0x7f1c2f29581c in __internal_syscall_cancel () at /lib64/libc.so.6
#2 0x7f1c2f295fec in __futex_abstimed_wait_common () at /lib64/libc.so.6
#3 0x7f1c2f298c55 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libc.so.6
#4 0x7f1c2fd37345 in QWaitConditionPrivate::wait_relative (this=, deadline=...) at
/usr/src/debug/qtbase-everywhere-src-6.9.0/src/corelib/thread/qwaitcondition_unix.cpp:57
#5 QWaitConditionPrivate::wait (this=0x55f1c8bbf9e0, deadline=...) at
/usr/src/debug/qtbase-everywhere-src-6.9.0/src/corelib/thread/qwaitcondition_unix.cpp:65
#6 QWaitCondition::wait (this=, mutex=0x55f1c8785b88,
deadline=...) at
/usr/src/debug/qtbase-everywhere-src-6.9.0/src/corelib/thread/qwaitcondition_unix.cpp:145
#7 0x7f1c2fd31dcc in QThreadPoolThread::run (this=0x55f1c8f96920) at
/usr/src/debug/qtbase-everywhere-src-6.9.0/src/corelib/thread/qthreadpool.cpp:119
#8 0x7f1c2fd2c22a in operator() (__closure=) at
/usr/src/debug/qtbase-everywhere-src-6.9.0/src/corelib/thread/qthread_unix.cpp:433
#9 (anonymous
namespace)::terminate_on_exception >
(t=) at
/usr/src/debug/qtbase-everywhere-src-6.9.0/src/corelib/thread/qthread_unix.cpp:365
#10 QThreadPrivate::start (arg=0x55f1c8f96920) at
/usr/src/debug/qtbase-everywhere-src-6.9.0/src/corelib/thread/qthread_unix.cpp:393
#11 0x7f1c2f299546 in start_thread () at /lib64/li
[kwin] [Bug 507804] New: Kwin crash when starting a game with proton
https://bugs.kde.org/show_bug.cgi?id=507804
Bug ID: 507804
Summary: Kwin crash when starting a game with proton
Classification: Plasma
Product: kwin
Version First 6.4.3
Reported In:
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kwin-bugs-n...@kde.org
Reporter: k...@hatch.dk
Target Milestone: ---
Application: kwin_x11 (6.4.3)
ApplicationNotResponding [ANR]: false
Qt Version: 6.9.1
Frameworks Version: 6.16.0
Operating System: Linux 6.15.8-200.fc42.x86_64 x86_64
Windowing System: X11
Distribution: "Fedora Linux 42 (KDE Plasma Desktop Edition)"
DrKonqi: 6.4.3 [CoredumpBackend]
-- Information about the crash:
Whenever i start a game in lutris using the proton (or wine) runner kwin
crashes when the application starts.
The game starts fine, but if i alt-tab back out and into the game again, kwin
crashes again and sometimes it can be difficult to get back in the game because
it seems like kwin restarting after crashing pulls focus so it kinda flickers
back and forth.
The crash can be reproduced every time.
-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
Downloading separate debug info for /usr/bin/kwin_x11...
warning: Can't open file /memfd:JSGCHeap:QtQml (deleted) during file-backed
mapping note processing
warning: Can't open file /memfd:JSVMStack:QtQml (deleted) during file-backed
mapping note processing
warning: Can't open file /memfd:/.nvidia_drv.XX (deleted) during
file-backed mapping note processing
warning: Can't open file /memfd:unknown-usage:QtQml (deleted) during
file-backed mapping note processing
warning: Can't open file /memfd:/.glXX (deleted) during file-backed mapping
note processing
[New LWP 17027]
[New LWP 17037]
[New LWP 17038]
[New LWP 17074]
[New LWP 17303]
[New LWP 19041]
[New LWP 19040]
[New LWP 19042]
[New LWP 19043]
Downloading 3.80 M separate debug info for /lib64/libm.so.6...
Downloading 6.65 M separate debug info for /lib64/libc.so.6...
Downloading 254.88 K separate debug info for /lib64/libresolv.so.2...
Downloading separate debug info for /lib64/libdl.so.2...
Downloading separate debug info for /lib64/libpthread.so.0...
Downloading separate debug info for /lib64/librt.so.1...
Downloading 53.38 K separate debug info for system-supplied DSO at
0x7f1d7c0ee000...
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/kwin_x11 --replace'.
Program terminated with signal SIGSEGV, Segmentation fault.
Downloading source file
/usr/src/debug/glibc-2.41-9.fc42.x86_64/nptl/pthread_kill.c...
#0 __pthread_kill_implementation (threadid=,
signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44
44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO
(ret) : 0;
[Current thread is 1 (Thread 0x7f1d7267fdc0 (LWP 17027))]
Cannot QML trace cores :(
Downloading source file
/usr/src/debug/glibc-2.41-9.fc42.x86_64/misc/../sysdeps/unix/sysv/linux/x86_64/clone3.S...
Downloading source file
/usr/src/debug/glibc-2.41-9.fc42.x86_64/nptl/pthread_create.c...
Downloading 23.50 K source file
/usr/src/debug/glibc-2.41-9.fc42.x86_64/nptl/pthread_cond_wait.c...
Downloading source file
/usr/src/debug/glibc-2.41-9.fc42.x86_64/nptl/futex-internal.c...
Downloading source file
/usr/src/debug/glibc-2.41-9.fc42.x86_64/nptl/cancellation.c...
Downloading source file
/usr/src/debug/glibc-2.41-9.fc42.x86_64/nptl/../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S...
Downloading 1.41 K source file
/usr/src/debug/glibc-2.41-9.fc42.x86_64/io/../sysdeps/unix/sysv/linux/poll.c...
Downloading source file
/usr/src/debug/glibc-2.41-9.fc42.x86_64/io/../sysdeps/unix/sysv/linux/ppoll.c...
[Current thread is 1 (Thread 0x7f1d7267fdc0 (LWP 17027))]
Thread 9 (Thread 0x7f1d2e66a6c0 (LWP 19043)):
#0 __syscall_cancel_arch () at
../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
#1 0x7f1d7807b9da in __internal_syscall_cancel (a1=,
a2=, a3=a3@entry=1, a4=, a5=a5@entry=0,
a6=a6@entry=4294967295, nr=202) at cancellation.c:49
#2 0x7f1d7807c04c in __futex_abstimed_wait_common64 (private=0,
futex_word=0x562a3057583c, expected=1, op=,
abstime=0x7f1d2e6696d0, cancel=true) at futex-internal.c:57
#3 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x562a3057583c,
expected=expected@entry=1, clockid=clockid@entry=1,
abstime=abstime@entry=0x7f1d2e6696d0, private=private@entry=0,
cancel=cancel@entry=true) at futex-internal.c:87
#4 0x7f1d7807c0af in __GI___futex_abstimed_wait_cancelable64
(futex_word=futex_word@entry=0x562a3057583c, expected=expected@entry=1,
clockid=clockid@entry=1, abstime=abstime@entry=0x7f1d2e6696d0,
private=private@entry=0) at futex-internal.c:139
#5 0x7f1d7807e928 in __
[krita] [Bug 468601] New: Segmentation fault when starting up
https://bugs.kde.org/show_bug.cgi?id=468601 Bug ID: 468601 Summary: Segmentation fault when starting up Classification: Applications Product: krita Version: 5.1.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: kimt...@gmail.com Target Milestone: --- SUMMARY Krita crashes on startup, right after moving the mouse within the window. STEPS TO REPRODUCE 1. Start program 2. Move the mouse to click "new file" 3. Program crashes before even clicking anything OBSERVED RESULT Segfault EXPECTED RESULT Usability SOFTWARE/OS VERSIONS Arch Linux ADDITIONAL INFORMATION (gdb) bt #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x754a0953 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #2 0x75451ea8 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x7543b53d in __GI_abort () at abort.c:79 #4 0x7543c29e in __libc_message (fmt=fmt@entry=0x755b377e "%s\n") at ../sysdeps/posix/libc_fatal.c:150 #5 0x754aa657 in malloc_printerr (str=str@entry=0x755b11d9 "corrupted size vs. prev_size") at malloc.c:5651 #6 0x754ab15e in unlink_chunk (p=p@entry=0x7fff4c066c40, av=0x7fff4c30) at malloc.c:1605 #7 0x754ac66b in _int_free (av=0x7fff4c30, p=0x7fff4c065eb0, have_lock=, have_lock@entry=0) at malloc.c:4602 #8 0x754aee63 in __GI___libc_free (mem=) at malloc.c:3367 #9 0x7fffe04c86c5 in _TIFFfreeExt (tif=0x7fff4c064050, p=) at /usr/src/debug/libtiff/tiff-4.5.0/libtiff/tif_open.c:162 #10 TIFFFreeDirectory (tif=0x7fff4c064050) at /usr/src/debug/libtiff/tiff-4.5.0/libtiff/tif_dir.c:1647 #11 0x7fffe04c8758 in TIFFCleanup (tif=0x7fff4c064050) at /usr/src/debug/libtiff/tiff-4.5.0/libtiff/tif_close.c:52 #12 0x7fffc0ae97c4 in std::__uniq_ptr_impl::reset(tiff*) (__p=0x0, this=) at /usr/include/c++/12.2.1/bits/unique_ptr.h:198 #13 std::unique_ptr::reset(tiff*) (__p=0x0, this=) at /usr/include/c++/12.2.1/bits/unique_ptr.h:501 #14 KisTIFFImport::convert(KisDocument*, QIODevice*, KisPinnedSharedPtr) (this=0x7fff4c063ad0, document=0x7fff4c0018a0) at /usr/src/debug/krita/krita-5.1.5/plugins/impex/tiff/kis_tiff_import.cc:1834 #15 0x77c46ac4 in KisImportExportManager::doImport(QString const&, QSharedPointer) (this=this@entry=0x7fff4c002ce0, location=..., filter=...) at /usr/src/debug/krita/krita-5.1.5/libs/ui/KisImportExportManager.cpp:667 #16 0x77c48afd in KisImportExportManager::convert(KisImportExportManager::Direction, QString const&, QString const&, QString const&, bool, KisPinnedSharedPtr, bool, bool) (this=0x7fff4c002ce0, direction=direction@entry=KisImportExportManager::Import, location=, realLocation=, mimeType=, showWarnings=, exportConfiguration=..., isAsync=, isAdvancedExporting=) at /usr/src/debug/krita/krita-5.1.5/libs/ui/KisImportExportManager.cpp:376 #17 0x77c49bef in KisImportExportManager::importDocument(QString const&, QString const&) (this=, location=, mimeType=) at /usr/src/debug/krita/krita-5.1.5/libs/global/kis_shared_ptr.h:206 #18 0x77c30112 in KisDocument::openFile() (this=0x7fff4c0018a0) at /usr/src/debug/krita/krita-5.1.5/libs/ui/KisDocument.cpp:1874 #19 0x77c3dd78 in KisDocument::openPathInternal(QString const&) (this=0x7fff4c0018a0, path=) at /usr/src/debug/krita/krita-5.1.5/libs/ui/KisDocument.cpp:2414 #20 0x77c3688d in KisDocument::openPath(QString const&, QFlags) (this=0x7fff4c0018a0, _path=..., flags=...) at /usr/src/debug/krita/krita-5.1.5/libs/ui/KisDocument.cpp:1810 #21 0x77baaffe in KisFileIconCreator::createFileIcon(QString, QIcon&, double, QSize) (this=this@entry=0x7fff8e294bf8, path=..., icon=..., devicePixelRatioF=devicePixelRatioF@entry=1, iconSize=...) at /usr/include/qt/QtCore/qflags.h:121 #22 0x77bab444 in (anonymous namespace)::getFileIcon((anonymous namespace)::GetFileIconParameters) (gfip=...) at /usr/src/debug/krita/krita-5.1.5/libs/ui/utils/KisRecentFileIconCache.cpp:51 #23 0x77ba4f46 in QtConcurrent::StoredFunctorCall1<(anonymous namespace)::IconFetchResult, (anonymous namespace)::IconFetchResult (*)((anonymous namespace)::GetFileIconParameters), (anonymous namespace)::GetFileIconParameters>::runFunctor (this=0x5cd2b640) at /usr/include/qt/QtConcurrent/qtconcurrentstoredfunctioncall.h:422 #24 QtConcurrent::RunFunctionTask<(anonymous namespace)::IconFetchResult>::run() (this=0x5cd2b640) at /usr/include/qt/QtConcurrent/qtconcurrentrunbase.h:108 #25 0x75ae8711 in QThreadPoolThread::run() (this=0x5a32a9a0) at thread/qthreadpool.cpp:100 #26 0x75ae424a in operator() (__closure=) at thread/qthread_unix.cpp:350 #27 (anonymous namespace)::terminate_on_exception
[krita] [Bug 468601] Segmentation fault when starting up
https://bugs.kde.org/show_bug.cgi?id=468601 --- Comment #2 from Kim Tore Jensen --- (In reply to Dmitry Kazakov from comment #1) > From the backtrace it seems like the problem is related to the custom build > of Arch Linux package... Hi Dmitry, Reporting to the Arch Linux community revealed that Krita had a TIFF file in the recent history that was causing trouble. I have identified the file in question, it is a 56MB file from NASA's infrared camera satellite. What would you like me to do? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468601] Segmentation fault when starting up
https://bugs.kde.org/show_bug.cgi?id=468601 Kim Tore Jensen changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #5 from Kim Tore Jensen --- Hello Dmitry, (In reply to Dmitry Kazakov from comment #4) > Could you please test if the same crash happens with the official AppImage > version of Krita: I'm unable to reproduce the crash with the official AppImage. > And, of course, it would be helpful if you shared the link to that NASA > image. It took some searching around, but I finally found the links: https://webbtelescope.org/contents/media/images/2022/031/01G780WF1VRADDSD5MDNDRKAGY?news=true https://stsci-opo.org/STScI-01G8GY7CZNNQH69BJG1ZGQ4D5B.tif -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 439470] KFontView is unable to open or install a font on Wayland
https://bugs.kde.org/show_bug.cgi?id=439470 Doan Kim Huy changed: What|Removed |Added CC||doankimhuy...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 439470] KFontView is unable to open or install a font on Wayland
https://bugs.kde.org/show_bug.cgi?id=439470 --- Comment #3 from Doan Kim Huy --- Any updates on this bug? It is still here in Plasma 5.23.4, KDE Frameworks 5.89, Qt 5.15.2. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 431728] New: 4.4.3-alpha (git 36584ff)
https://bugs.kde.org/show_bug.cgi?id=431728 Bug ID: 431728 Summary: 4.4.3-alpha (git 36584ff) Product: yakuake Version: Git (KDE Platform 4) Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: h...@kde.org Reporter: khsim...@gmail.com Target Milestone: --- Created attachment 134963 --> https://bugs.kde.org/attachment.cgi?id=134963&action=edit Krita Version: 4.4.3-alpha (git 36584ff) Languages: da, en_US, en, da, en_US, en, da, en_US, en, da, en_US, en, en_US, en Hidpi: true QtVersion (compiled): 5.12.9 Version (loaded): 5.12.9 SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Krita Version: 4.4.3-alpha (git 36584ff) Languages: da, en_US, en, da, en_US, en, da, en_US, en, da, en_US, en, en_US, en Hidpi: true Qt Version (compiled): 5.12.9 Version (loaded): 5.12.9 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.19042 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 164234] Krita crashes when opening anything
https://bugs.kde.org/show_bug.cgi?id=164234 kim <30020...@cityofglacol.ac.uk> changed: What|Removed |Added CC||30020...@cityofglacol.ac.uk -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369398] New: The program crashes when loading.
https://bugs.kde.org/show_bug.cgi?id=369398 Bug ID: 369398 Summary: The program crashes when loading. Product: krita Version: 3.0.1 Platform: Windows CE OS: other Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: 30020...@cityofglacol.ac.uk When I load the program, it takes minutes to load and then crashes. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 361066] [Feature Request] GTK+ 3.20 support
https://bugs.kde.org/show_bug.cgi?id=361066 Kim changed: What|Removed |Added CC||jiak...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 354056] Deleted emails stay, but greyed out
https://bugs.kde.org/show_bug.cgi?id=354056 --- Comment #38 from Kim Lilliestierna --- This has been resolved in the latest kmail version (5.1.3) and kde framework (5.18.0) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 356457] valgrind: m_mallocfree.c:2042 (vgPlain_arena_free): Assertion 'blockSane(a, b)' failed.
https://bugs.kde.org/show_bug.cgi?id=356457 Kim Rosberg changed: What|Removed |Added CC||kim.rosb...@ericsson.com --- Comment #4 from Kim Rosberg --- I'm experience exactly the same behavior. But the interval is between +-4 days and I'm running multiple servers 24h. ==247219== Memcheck, a memory error detector ==247219== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==247219== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info ==247219== Command: some test.elf ==247219== Parent PID: 247218 ==247219== blockSane: fail -- redzone-hi valgrind: m_mallocfree.c:2047 (vgPlain_arena_free): Assertion 'blockSane(a, b)' failed. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 356457] valgrind: m_mallocfree.c:2042 (vgPlain_arena_free): Assertion 'blockSane(a, b)' failed.
https://bugs.kde.org/show_bug.cgi?id=356457 --- Comment #7 from Kim Rosberg --- I'm sorry, assertion was from 2047 in Valgrind 3.10.0 and 2042 in 3.11.0 (I copy pasted and changed the version number from the error code). I'm mainly running on Red Hat 6 with custom Valgrind (almost default config). I cannot inform you about the libraries. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 363308] New: Unable to use Navigation and OsmPlacemarkData classes
https://bugs.kde.org/show_bug.cgi?id=363308 Bug ID: 363308 Summary: Unable to use Navigation and OsmPlacemarkData classes Product: marble Version: 1.14 (KDE Applications 16.04) Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: kimt...@gmail.com The "Navigation.h" and "OsmPlacemarkData.h" header files (and possibly others) are not installed into /usr/include/marble upon running "make install". Thus, it seems to me that it is not possible to use these classes in a custom application. Reproducible: Always Steps to Reproduce: 1. Build Marble 16.04 by configuring with: cmake -DCMAKE_BUILD_TYPE=Release -DWITH_KF5=FALSE -DCMAKE_INSTALL_PREFIX=/usr -DQTONLY=ON -DBUILD_MARBLE_APPS=NO -DWITH_DESIGNER_PLUGIN=NO -DBUILD_MARBLE_TESTS=NO /path/to/marble 2. Try to compile a C++ program with #include or #include Actual Results: Compilation is failing. Expected Results: Compiled successfully. -- You are receiving this mail because: You are watching all bug changes.
