[kdeconnect] [Bug 456515] Ring my phone not working
https://bugs.kde.org/show_bug.cgi?id=456515 --- Comment #3 from Joost --- Maybe not so weird. Looking at logcat above and the source code here: https://github.com/KDE/kdeconnect-android/blob/master/src/org/kde/kdeconnect/Plugins/FindMyPhonePlugin/FindMyPhonePlugin.java what I think is happening: The onCreate function (line 68) obtains a content-uri to the default ringtone. Then the uri is opened by the mediaplayer, but it does not simply point to a file, but to a resource within ringtonemanager.java that is trying to obtain the ringtone data and it does not have the permission to do that. Perhaps there is a more compatible way to play the default ringtone. For example the second answer here: https://stackoverflow.com/questions/22503189/how-to-get-current-ringtone-in-android quote: >Uri defaultRintoneUri = >RingtoneManager.getActualDefaultRingtoneUri(getApplicationContext(), >RingtoneManager.TYPE_RINGTONE); >Ringtone defaultRingtone = >RingtoneManager.getRingtone(getApplicationContext(), defaultRintoneUri); >defaultRingtone.play(); Maybe when I have time I'll play around with that and see if it works on my phone. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410644] krita stops drawing after a while
https://bugs.kde.org/show_bug.cgi?id=410644 --- Comment #20 from joost --- (In reply to Dmitry Kazakov from comment #19) > Hi, joost! > > Please check if this bug still appears in the newly released Krita 4.2.6. I > think I have fixed it in August: > > https://krita.org/en/item/krita-4-2-6-released/ > > If the bug still persists for you, then reopen the report :) > > *** This bug has been marked as a duplicate of bug 410797 *** It doesn't the bug seemingly has been resolved -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410644] New: krita stops drawing after a while
https://bugs.kde.org/show_bug.cgi?id=410644 Bug ID: 410644 Summary: krita stops drawing after a while Product: krita Version: 4.2.5 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: crash Priority: NOR Component: Brush Engine/Shape Assignee: krita-bugs-n...@kde.org Reporter: joostlensv...@gmail.com Target Milestone: --- SUMMARY Krita stops drawing after 2 minutes while I am still drawing. And if I save the drawing it tries to complete an edit in the canvas even if the canvas is empty and I haven't drawn anything yet. STEPS TO REPRODUCE 1. I have no idea how to reproduce the bug. My friend drew some scribbles on it and then it stopped drawing. 2. 3. OBSERVED RESULT My pen stops drawing. EXPECTED RESULT I can keep on drawing SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION My drawing tablet is a wacom cintiq -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410644] krita stops drawing after a while
https://bugs.kde.org/show_bug.cgi?id=410644 --- Comment #2 from joost --- Created attachment 121957 --> https://bugs.kde.org/attachment.cgi?id=121957&action=edit possible crash repport It is the first time i posted a bug -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410644] krita stops drawing after a while
https://bugs.kde.org/show_bug.cgi?id=410644 --- Comment #3 from joost --- Created attachment 121958 --> https://bugs.kde.org/attachment.cgi?id=121958&action=edit possible crash repport -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410644] krita stops drawing after a while
https://bugs.kde.org/show_bug.cgi?id=410644 --- Comment #5 from joost --- Created attachment 121960 --> https://bugs.kde.org/attachment.cgi?id=121960&action=edit possible crash repport possible crash repport -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410644] krita stops drawing after a while
https://bugs.kde.org/show_bug.cgi?id=410644 --- Comment #4 from joost --- Created attachment 121959 --> https://bugs.kde.org/attachment.cgi?id=121959&action=edit possible crash repport possible crash repport -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410644] krita stops drawing after a while
https://bugs.kde.org/show_bug.cgi?id=410644 --- Comment #6 from joost --- Created attachment 121961 --> https://bugs.kde.org/attachment.cgi?id=121961&action=edit possible crash repport -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410644] krita stops drawing after a while
https://bugs.kde.org/show_bug.cgi?id=410644 --- Comment #7 from joost --- Created attachment 121962 --> https://bugs.kde.org/attachment.cgi?id=121962&action=edit possible crash repport -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410644] krita stops drawing after a while
https://bugs.kde.org/show_bug.cgi?id=410644 --- Comment #8 from joost --- Created attachment 121963 --> https://bugs.kde.org/attachment.cgi?id=121963&action=edit possible crash repport -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410644] krita stops drawing after a while
https://bugs.kde.org/show_bug.cgi?id=410644 --- Comment #9 from joost --- Created attachment 121964 --> https://bugs.kde.org/attachment.cgi?id=121964&action=edit possible crash repport -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410644] krita stops drawing after a while
https://bugs.kde.org/show_bug.cgi?id=410644 --- Comment #10 from joost --- Created attachment 121965 --> https://bugs.kde.org/attachment.cgi?id=121965&action=edit possible crash repport -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410644] krita stops drawing after a while
https://bugs.kde.org/show_bug.cgi?id=410644 --- Comment #11 from joost --- I posted all the files i had in the %LOCALAPPDATA%. I think it isn't a crash and I chose it by mistake -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410644] krita stops drawing after a while
https://bugs.kde.org/show_bug.cgi?id=410644 joost changed: What|Removed |Added Attachment #121957|0 |1 is obsolete|| Attachment #121958|0 |1 is obsolete|| Attachment #121959|0 |1 is obsolete|| Attachment #121960|0 |1 is obsolete|| Attachment #121961|0 |1 is obsolete|| Attachment #121962|0 |1 is obsolete|| Attachment #121963|0 |1 is obsolete|| Attachment #121964|0 |1 is obsolete|| Attachment #121965|0 |1 is obsolete|| --- Comment #13 from joost --- Created attachment 121966 --> https://bugs.kde.org/attachment.cgi?id=121966&action=edit There is no crash I made a mistake. here is the log there is no crash repport so it isn't a crash. here is the log. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411016] New: krita stops drawing and gives me a message when i save
https://bugs.kde.org/show_bug.cgi?id=411016 Bug ID: 411016 Summary: krita stops drawing and gives me a message when i save Product: krita Version: 4.2.5 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: joostlensv...@gmail.com Target Milestone: --- Created attachment 122202 --> https://bugs.kde.org/attachment.cgi?id=122202&action=edit image of the message krita gives me SUMMARY Krita stops drawing after switching between the drawing function of my tablet pen and eareser function. and if I try to save my drawing then I am hit with the message "wait untill the completion of the editing of the image" STEPS TO REPRODUCE 1. keep switching between the draw function and earaser function 2. 3. OBSERVED RESULT krita stops drawing and if I try to save I get a odd message EXPECTED RESULT krita keeps on drawing and I am able to save without a message. SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411016] krita stops drawing and gives me a message when i save
https://bugs.kde.org/show_bug.cgi?id=411016 --- Comment #2 from joost --- (In reply to wolthera from comment #1) > Hi, this should be fixed in the last Krita: Next (And Krita: Stable), can > you check? Do you mean wich version I am using? It is version 4.2.5 . If that isn't what you meant what should I check. You are a bit vague -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411016] krita stops drawing and gives me a message when i save
https://bugs.kde.org/show_bug.cgi?id=411016 --- Comment #4 from joost --- (In reply to wolthera from comment #3) > There's 'krita:next' and 'krita:stable' entries on the download section of > Krita.org, these are our nightly builds for the master and bugfix branches > respectively, so the code is newer than 4.2.5. > > Could you check if the fix that went in a few days ago and thus is in one of > these two builds works to solve your bug? Because otherwise you have a > different bug and we need to figure out why it is different :) I didn't download krita from krita.org I bought it from steam -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411016] krita stops drawing and gives me a message when i save
https://bugs.kde.org/show_bug.cgi?id=411016 --- Comment #7 from joost --- (In reply to Tymond from comment #6) > Just for the record, this person on reddit: > https://www.reddit.com/r/krita/comments/cp9num/ > waiting_for_image_operation_to_complete/ex7raue/?context=3 > says that they had this issue and in Krita Plus package from today (August > 17th, 2019, either g1a1ba08147 or the previous one) they didn't have those > issues, so it looks to be fixed for them (not that they tested for a long > time or anything... it's like three hours between my comment and theirs ;) ) thanks for the tip and help. I was planning on drawing all day tomorrow so if the isseu still persits I will contact you. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411016] krita stops drawing and gives me a message when i save
https://bugs.kde.org/show_bug.cgi?id=411016 --- Comment #10 from joost --- This is the result after about 7 hours of straight drawing using Krita. The newer version did indeed solve my problem. I was able to draw until i litterly dropped. so at least it is solved at my part. I like to thank the people who helped me with the bug. you guys are awesome -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411016] krita stops drawing and gives me a message when i save
https://bugs.kde.org/show_bug.cgi?id=411016 joost changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410644] krita stops drawing after a while
https://bugs.kde.org/show_bug.cgi?id=410644 --- Comment #16 from joost --- I am willing to help by testing krita. I am not that savvy with krita so tell me what I can do to help. I have a job so I am only able to repply during workdays after 17:00 give or take. with kind regards Joost Lensvelt -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410644] krita stops drawing after a while
https://bugs.kde.org/show_bug.cgi?id=410644 --- Comment #17 from joost --- by the way do you know people that can help me draw. I am an experienced amateur and need some drawing advice. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 466307] New: Okular crashes after, and sometimes when, opening signed PDF files
https://bugs.kde.org/show_bug.cgi?id=466307
Bug ID: 466307
Summary: Okular crashes after, and sometimes when, opening
signed PDF files
Classification: Applications
Product: okular
Version: 22.12.2
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: okular-de...@kde.org
Reporter: jo...@cassee.net
Target Milestone: ---
Application: okular (22.12.2)
Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.12-arch1-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.27.1 [KCrashBackend]
-- Information about the crash:
I opened a signed PDF document, and when I closed it, Okular crashed. A signed
document from the same series caused Okular to crash while opening it.
Unfortunately, I cannot include the documents because they contain personal
information.
The crash can be reproduced every time.
-- Backtrace:
Application: Okular (okular), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 __memcmp_evex_movbe () at
../sysdeps/x86_64/multiarch/memcmp-evex-movbe.S:164
#7 0x7f43640111a4 in SECITEM_CompareItem_Util (a=,
b=) at ../../lib/util/secitem.c:202
#8 0x7f4364160326 in CERT_CompareCerts (c1=, c2=) at ../../lib/certdb/certdb.c:1829
#9 0x7f43641bf7c2 in pkix_pl_Cert_Equals (firstObject=0x5639aa26f2d8,
secondObject=0x5639aa2fc238, pResult=0x7ffd7edd1a68, plContext=0x5639aa13cc50)
at ../../lib/libpkix/pkix_pl_nss/pki/pkix_pl_cert.c:1292
#10 0x7f43641d2ef4 in PKIX_PL_Object_Equals (firstObject=0x5639aa26f2d8,
secondObject=0x5639aa2fc238, pResult=0x7ffd7edd1a68, plContext=0x5639aa13cc50)
at ../../lib/libpkix/pkix_pl_nss/system/pkix_pl_object.c:996
#11 0x7f43641a09ab in pkix_List_Equals (first=first@entry=0x5639a9f272c8,
second=0x5639a9fd3978, pResult=pResult@entry=0x7ffd7edd1b34,
plContext=plContext@entry=0x5639aa13cc50) at
../../lib/libpkix/pkix/util/pkix_list.c:347
#12 0x7f43641d4c0d in pkix_pl_PrimHashTable_Lookup
(plContext=0x5639aa13cc50, pResult=, keyComp=0x7f43641a0710
, hashCode=1541928911, key=0x5639a9f272c8, ht=) at ../../lib/libpkix/pkix_pl_nss/system/pkix_pl_primhash.c:400
#13 PKIX_PL_HashTable_Lookup (ht=0x5639aa052648, key=0x5639a9f272c8,
pResult=0x7ffd7edd1dc0, plContext=0x5639aa13cc50) at
../../lib/libpkix/pkix_pl_nss/system/pkix_pl_hashtable.c:364
#14 0x7f43641e0bb1 in pkix_CacheCertChain_Lookup (plContext=0x5639aa13cc50,
pBuildResult=0x7ffd7edd1d90, pFound=,
testDate=0x5639aa3c49f8, anchors=0x5639aaec5c08, targetCert=0x5639aa26f2d8) at
../../lib/libpkix/pkix/util/pkix_tools.c:601
#15 pkix_Build_CheckInCache (plContext=0x5639aa13cc50,
pNBIOContext=0x7ffd7edd1d58, pBuildResult=0x7ffd7edd1d70, state=0x5639a9fcac38)
at ../../lib/libpkix/pkix/top/pkix_build.c:2948
#16 pkix_Build_InitiateBuildChain.constprop.0 (procParams=,
pNBIOContext=pNBIOContext@entry=0x7ffd7edd1f30,
pState=pState@entry=0x7ffd7edd1f40,
pBuildResult=pBuildResult@entry=0x7ffd7edd1f38, pVerifyNode=0x7ffd7edd20b0,
plContext=plContext@entry=0x5639aa13cc50) at
../../lib/libpkix/pkix/top/pkix_build.c:3495
#17 0x7f43641ab421 in PKIX_BuildChain (procParams=,
pNBIOContext=0x7ffd7edd20c8, pState=0x7ffd7edd20c0,
pBuildResult=0x7ffd7edd20d0, pVerifyNode=,
plContext=0x5639aa13cc50) at ../../lib/libpkix/pkix/top/pkix_build.c:3704
#18 0x7f4364122ce5 in CERT_PKIXVerifyCert (cert=0x5639aae1a890,
usages=, paramsIn=, paramsOut=,
wincx=) at ../../lib/certhigh/certvfypkix.c:2164
#19 0x7f434c6748fa in SignatureHandler::validateCertificate
(this=0x7ffd7edd22e0, validation_time=-1, ocspRevocationCheck=,
useAIACertFetch=) at
/usr/src/debug/poppler/poppler-23.02.0/poppler/SignatureHandler.cc:1036
#20 0x7f434c54d8b7 in FormFieldSignature::validateSignature
(this=0x5639a9fa0510, doVerifyCert=,
forceRevalidation=, validationTime=-1,
ocspRevocationCheck=, enableAIA=) at
/usr/src/debug/poppler/poppler-23.02.0/poppler/Form.cc:2405
#21 0x7f43643c38e3 in Poppler::FormFieldSignature::validate
(this=, opt=1, validationTime=...) at
/usr/src/debug/poppler/poppler-23.02.0/qt5/src/poppler-form.cc:1017
#22 0x7f43643c3da5 in Poppler::FormFieldSignature::validate
(this=0x5639aa405830,
opt=opt@entry=Poppler::FormFieldSignature::ValidateVerifyCertificate) at
/usr/src/debug/poppler/poppler-23.02.0/qt5/src/poppler-form.cc:967
#23 0x7f4364483365 in PopplerFormFieldSignature::PopplerFormFieldSignature
(this=, field=..., this=, field=...) at
/usr/src/debug/okular/okular-22.12.2/generators/poppler/formfields.cpp:404
#24 0x7f4364487f66 in PDFGenerator::getFormFields(Poppler::Page*) [clone
.constprop.0] (popplerPage=, this=) at
/usr/src/debug/okular/okular-22.12.2/generators/poppler/generator_pdf.cpp:1940
#25 0x7f43644790b6 in PDFGenerator::loadPages (rotation=0, clear=false,
pagesVector=.
[kio-extras] [Bug 453887] kio-s3 compilation fails
https://bugs.kde.org/show_bug.cgi?id=453887 Joost Cassee changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Joost Cassee --- Fixed in kio-s3 commit 891bded. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 453877] Allow multiple simultaneous auth methods to be used without having to fail at one of them, first via multiple PAM stacks
https://bugs.kde.org/show_bug.cgi?id=453877 Joost Cassee changed: What|Removed |Added CC||jo...@cassee.net -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 484742] New: unhandled instruction 0x4E9096B7
https://bugs.kde.org/show_bug.cgi?id=484742
Bug ID: 484742
Summary: unhandled instruction 0x4E9096B7
Classification: Developer tools
Product: valgrind
Version: 3.22.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: joost.vandevond...@gmail.com
Target Milestone: ---
On NVIDIA's Grace CPU valgrind fails to run a binary (that otherwise runs fine)
failing to handle an instruction:
```
==45347== Memcheck, a memory error detector
==45347== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==45347== Using Valgrind-3.22.0 and LibVEX; rerun with -h for copyright info
==45347== Command: ./stockfish bench
==45347==
Stockfish dev-20240329-ec598b38 by the Stockfish developers (see AUTHORS file)
Position: 1/48 (rnbqkbnr//8/8/8/8//RNBQKBNR w KQkq - 0 1)
info string NNUE evaluation using nn-1ceb1ade0001.nnue
info string NNUE evaluation using nn-baff1ede1f90.nnue
disInstr(arm64): unhandled instruction 0x4E9096B7
disInstr(arm64): 0100'1110 1001' 1001'0110 1011'0111
==45347== valgrind: Unrecognised instruction at address 0x40f684.
==45347==at 0x40F684:
Stockfish::Eval::NNUE::Network, Stockfish::Eval::NNUE::FeatureTransformer<2560u,
&Stockfish::StateInfo::accumulatorBig> >::evaluate(Stockfish::Position const&,
bool, int*, bool) const [clone .constprop.0] (in
/users/vjoost/Stockfish/src/stockfish)
==45347==by 0x40E667:
Stockfish::Eval::evaluate(Stockfish::Eval::NNUE::Networks const&,
Stockfish::Position const&, int) (in /users/vjoost/Stockfish/src/stockfish)
==45347==by 0x42A3F7: Stockfish::Search::Worker::iterative_deepening() (in
/users/vjoost/Stockfish/src/stockfish)
==45347==by 0x4280E7: Stockfish::Search::Worker::start_searching() (in
/users/vjoost/Stockfish/src/stockfish)
==45347==by 0x4210EB: Stockfish::Thread::idle_loop() (in
/users/vjoost/Stockfish/src/stockfish)
==45347==by 0x42103F: Stockfish::NativeThread::NativeThread(void (Stockfish::Thread::*&&)(),
Stockfish::Thread*&&)::{lambda(void*)#1}::_FUN(void*) (in
/users/vjoost/Stockfish/src/stockfish)
==45347==by 0x507875B: start_thread (in /lib64/libpthread-2.31.so)
==45347==by 0x54BFEEB: thread_start (in /lib64/libc-2.31.so)
```
Linux OS.
The program is compiled using `gcc version 12.3.0`, with target:
`-march=armv8.2-a+dotprod`.
/proc/cpuinfo gives:
```
Features: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp
asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 sm3 sm4 asimddp sha512 sve
asimdfhm dit uscat ilrcpc flagm ssbs sb paca pacg dcpodp sve2 sveaes svepmull
svebitperm svesha3 svesm4 flagm2 frint svei8mm svebf16 i8mm bf16 dgh bti
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part: 0xd4f
CPU revision: 0
```
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 484742] unhandled instruction 0x4E9096B7
https://bugs.kde.org/show_bug.cgi?id=484742 --- Comment #1 from Joost VandeVondele --- Also reproduces on a Raspberry Pi 5: Raspberry Pi 5 $ cat /proc/cpuinfo processor : 0 BogoMIPS: 108.00 Features: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x4 CPU part: 0xd0b CPU revision: 1 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 484742] unhandled instruction 0x4E9096B7
https://bugs.kde.org/show_bug.cgi?id=484742 --- Comment #2 from Joost VandeVondele --- ok, seems to be related to the +dotprod part of the isa (which we detect based on the asimddp flag). Probably acc = vdotq_s32(acc, a0, b0); or output[i] = vaddvq_s32(sum); -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 453887] New: kio-s3 compilation fails
https://bugs.kde.org/show_bug.cgi?id=453887 Bug ID: 453887 Summary: kio-s3 compilation fails Product: kio-extras Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: default Assignee: plasma-b...@kde.org Reporter: jo...@cassee.net Target Milestone: --- Created attachment 148880 --> https://bugs.kde.org/attachment.cgi?id=148880&action=edit kio-s3 compilation log [I'm not sure this is part of kio-extras, but because the kio-s3 repository has bugs disabled I assumed they want to have them reported here.] SUMMARY When compiling kio-s3 version (commit a0544f8), I get the following error: call of overloaded ‘ClientConfiguration(QByteArray&)’ is ambiguous STEPS TO REPRODUCE 1. git clone https://github.com/KDE/kio-s3.git 2. cd kio-s3 3. cmake . 4. make OBSERVED RESULT Compilation fails with the above error. EXPECTED RESULT Compilation succeeds. SOFTWARE/OS VERSIONS Linux/KDE Plasma on Arch Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION I have attached the compilation log. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452310] New: kwin crashes regularly
https://bugs.kde.org/show_bug.cgi?id=452310
Bug ID: 452310
Summary: kwin crashes regularly
Product: kwin
Version: 5.24.4
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kwin-bugs-n...@kde.org
Reporter: jo...@cassee.net
Target Milestone: ---
Application: kwin_x11 (5.24.4)
Qt Version: 5.15.3
Frameworks Version: 5.92.0
Operating System: Linux 5.17.1-arch1-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.24.4 [KCrashBackend]
-- Information about the crash:
- Unusual behavior I noticed:
Only happens when connected to an LG 34WK95U tiled monitor.
The crash can be reproduced sometimes.
-- Backtrace:
Application: KWin (kwin_x11), signal: Aborted
Content of s_kcrashErrorMessage: {_M_t = { >> = {_M_t = std::tuple containing = {[1] = 0x0,
[2] = {}}}, }}
[KCrash Handler]
#6 0x7fda0b07834c in __pthread_kill_implementation () at
/usr/lib/libc.so.6
#7 0x7fda0b02b4b8 in raise () at /usr/lib/libc.so.6
#8 0x7fda0b015534 in abort () at /usr/lib/libc.so.6
#9 0x7fd9fe60d563 in _iris_batch_flush() () at
../mesa-22.0.1/src/gallium/drivers/iris/iris_batch.c:1105
#10 0x7fd9ff245e0f in iris_fence_flush() () at
../mesa-22.0.1/src/gallium/drivers/iris/iris_fence.c:267
#11 0x7fd9fe88f097 in fence_sync() () at
../mesa-22.0.1/src/mesa/main/syncobj.c:294
#12 0x7fda0da9cd88 in KWin::WindowThumbnailItem::updateOffscreenTexture()
(this=0x558e34a86fc0) at
/usr/src/debug/kwin-5.24.4/src/scripting/thumbnailitem.cpp:432
#13 0x7fda0c12e463 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffce2a3d430, r=, this=0x558e35d9c260, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#14 doActivate(QObject*, int, void**) (sender=0x558e34ab2680,
signal_index=3, argv=0x7ffce2a3d430) at kernel/qobject.cpp:3886
#15 0x7fda0da743e6 in KWin::Scene::paintScreen(QRegion const&, QRegion
const&, QRegion*, QRegion*, KWin::RenderLoop*, QMatrix4x4 const&)
(this=0x558e34ab2680, damage=, repaint=...,
updateRegion=0x7ffce2a3d5d0, validRegion=0x7ffce2a3d5c8, renderLoop=, projection=...) at /usr/src/debug/kwin-5.24.4/src/scene.cpp:282
#16 0x7fda0db3a297 in KWin::SceneOpenGL::paint(KWin::AbstractOutput*,
QRegion const&, QList const&, KWin::RenderLoop*)
(this=0x558e34ab2680, output=0x0, damage=..., toplevels=,
renderLoop=0x558e347d1920) at
/usr/src/debug/kwin-5.24.4/src/scenes/opengl/scene_opengl.cpp:259
#17 0x7fda0d9d67f4 in KWin::Compositor::composite(KWin::RenderLoop*)
(this=0x558e34703cc0, renderLoop=0x558e347d1920) at
/usr/src/debug/kwin-5.24.4/src/composite.cpp:633
#18 0x7fda0d9d6d40 in KWin::X11Compositor::composite(KWin::RenderLoop*)
(this=0x558e34703cc0, renderLoop=) at
/usr/src/debug/kwin-5.24.4/src/composite.cpp:844
#19 0x7fda0c12e463 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffce2a3d8d0, r=, this=0x558e34aff7d0, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#20 doActivate(QObject*, int, void**) (sender=0x558e347d1920,
signal_index=5, argv=0x7ffce2a3d8d0) at kernel/qobject.cpp:3886
#21 0x7fda0d9947a7 in KWin::RenderLoop::frameRequested(KWin::RenderLoop*)
(this=, _t1=) at
/usr/src/debug/build/src/kwin_autogen/EWIEGA46WW/moc_renderloop.cpp:206
#22 0x7fda0da65c18 in KWin::RenderLoopPrivate::dispatch()
(this=0x558e347aa3a0) at /usr/src/debug/kwin-5.24.4/src/renderloop.cpp:150
#23 0x7fda0c12e463 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffce2a3d9f0, r=, this=0x558e347a76d0, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#24 doActivate(QObject*, int, void**) (sender=0x558e347aa3b8,
signal_index=3, argv=0x7ffce2a3d9f0) at kernel/qobject.cpp:3886
#25 0x7fda0c13069f in QTimer::timeout(QTimer::QPrivateSignal)
(this=, _t1=...) at .moc/moc_qtimer.cpp:205
#26 0x7fda0c121766 in QObject::event(QEvent*) (this=0x558e347aa3b8,
e=0x7ffce2a3db90) at kernel/qobject.cpp:1291
#27 0x7fda0b7291c6 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x558e347aa3b8, e=0x7ffce2a3db90) at
kernel/qapplication.cpp:3637
#28 0x7fda0c0fd5aa in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x558e347aa3b8, event=0x7ffce2a3db90) at
kernel/qcoreapplication.cpp:1064
#29 0x7fda0c148dd5 in QTimerInfoList::activateTimers()
(this=0x558e34439758) at kernel/qtimerinfo_unix.cpp:643
#30 0x7fda0c149272 in
QEventDispatcherUNIX::processEvents(QFlags)
(this=this@entry=0x558e345e3c90, flags=..., flags@entry=...) at
kernel/qeventdispatcher_unix.cpp:516
#31 0x7fda06028f83 in
QXcbUnixEventDispatcher::processEvents(QFlags)
(this=0x558e345e3c90, flags=...) at
/usr/src/debug/qtbase/src/plugins/platforms/xcb/qxcbeventdispatcher.cpp:60
#32 0x7fda0c0f588b in
QEventLoop::exec(Q
[systemsettings] [Bug 365091] "Start the Input Actions daemon on login" does nothing
https://bugs.kde.org/show_bug.cgi?id=365091 Joost Cassee changed: What|Removed |Added CC||jo...@cassee.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427545] Dual DisplayPort monitors (tiled, MST, e.g. 5k) are not supported by KWin
https://bugs.kde.org/show_bug.cgi?id=427545 Joost Cassee changed: What|Removed |Added CC||jo...@cassee.net -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 442806] New: Extension icon shows as disabled in Wavebox browser (but integration works)
https://bugs.kde.org/show_bug.cgi?id=442806 Bug ID: 442806 Summary: Extension icon shows as disabled in Wavebox browser (but integration works) Product: plasma-browser-integration Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: jo...@cassee.net Target Milestone: --- SUMMARY Wavebox is a (commercial) Chrome-based browser that has a package in the AUR. Adding the extension and copying org.kde.plasma.browser_integration.json enables Plasma integration. However, the icon is crossed out, suggesting it does not work. STEPS TO REPRODUCE 1. Install Wavebox. 2. Install the extension in Wavebox. 3. Install the Plasma browser integration. 4. Copy /etc/opt/chrome/native-messaging-hosts to /etc/wavebox/native-messaging-hosts. OBSERVED RESULT The integration works. The icon is crossed out, suggesting the integration is disabled. EXPECTED RESULT The icon shows the integration as enabled. Also, it would be nice if the native messaging host configuration were also copied to /etc/wavebox/native-messaging-hosts by the package. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I realize this is a request to accommodate commercial software, so rejecting it for that reason would be reasonable. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 449906] A monitor keeps power-cycling and disconnecting upon login
https://bugs.kde.org/show_bug.cgi?id=449906 Joost Cassee changed: What|Removed |Added CC||jo...@cassee.net -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 442806] Extension icon shows as disabled in Wavebox browser (but integration works)
https://bugs.kde.org/show_bug.cgi?id=442806 Joost Cassee changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #2 from Joost Cassee --- (In reply to Kai Uwe Broulik from comment #1) > Can't reproduce. I installed Wavebox, put the file in > /etc/wavebox/native-messaging-hosts, and the icon is displayed normally. Indeed. I hadn't looked at the icon for a while, and I see now that it is fully enabled. Thanks for taking the time to try to reproduce. I'm going to close the issue. -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 412189] No way to switch different cameras
https://bugs.kde.org/show_bug.cgi?id=412189 Joost Vandorp changed: What|Removed |Added CC||joostvand...@gmail.com --- Comment #10 from Joost Vandorp --- Hey everyone, I've been trying to fix this issue as well. I have never worked with QT Framework or KDE before so I am not 100% sure how to fix this issue, especially part 1 of this bug. I found there are 2 bugs here: 1. QComboBox popup hides under a parent window, similar to what this user reported: https://bugreports.qt.io/browse/QTBUG-61804 * see comment 9 on this bug report, https://bugs.kde.org/show_bug.cgi?id=412189#c9 * locally, I solved this in my fork by using buttons instead of the QComboBox 2. The Camera does not switch for me. The return on this line is the empty string: https://invent.kde.org/multimedia/kamoso/-/blob/master/src/device.cpp#L22 * I fixed it for myself my switching it back to using "device.path" instead of "object.id" I made a short ~4 minute video to show you what is going on for me if anyone is interested. https://www.youtube.com/watch?v=fJnKhqc2Vuc -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421778] Add feature to navigate to next and previous documents in current folder
https://bugs.kde.org/show_bug.cgi?id=421778 Joost Cassee changed: What|Removed |Added CC||jo...@cassee.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356899] Desktop Settings are not saved and loads default settings on reboot/startup.
https://bugs.kde.org/show_bug.cgi?id=356899 Joost Bremmer changed: What|Removed |Added CC||toos...@gmail.com --- Comment #26 from Joost Bremmer --- There does indeed seem to be some kind of regression as I am encountering this behaviour as well in 5.18.4 on Arch. This seems to be contained to "Desktop Settings" only, as panel changes are saved, but it also occurs between login/logout for me as well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421498] Desktop settings get nuked on every startup
https://bugs.kde.org/show_bug.cgi?id=421498 Joost Bremmer changed: What|Removed |Added CC||toos...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421498] Desktop settings get nuked on every startup
https://bugs.kde.org/show_bug.cgi?id=421498 --- Comment #2 from Joost Bremmer --- I am encountering this behaviour as well in 5.18.4 on Arch. This seems to be contained to "Desktop Settings" only, as panel changes are saved, but it also occurs between login/logout for me as well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376277] Right clicking on a system tray icon causes keeps focus on the icon even if user has moved elsewhere
https://bugs.kde.org/show_bug.cgi?id=376277 Joost Bremmer changed: What|Removed |Added CC||toos...@gmail.com --- Comment #4 from Joost Bremmer --- Also seem to still have this problem (plasma-workspace 5.9.4; Arch Linux). -- 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 #22 from Joost VandeVondele --- In my case, the issue has disappeared, and the 'only' thing changed is that the server has been updated and is now running Red Hat Enterprise Linux Server release 7.2, which for example includes a newer kernel 3.10.0-327.13.1.el7.x86_64. Valgrind, gcc etc. are still the same version. So, I would suspect this is some interaction with the OS causing this. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 356457] New: valgrind: m_mallocfree.c:2042 (vgPlain_arena_free): Assertion 'blockSane(a, b)' failed.
https://bugs.kde.org/show_bug.cgi?id=356457 Bug ID: 356457 Summary: valgrind: m_mallocfree.c:2042 (vgPlain_arena_free): Assertion 'blockSane(a, b)' failed. Product: valgrind Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: joost.vandevond...@mat.ethz.ch Our nightly tester runs a few thousand testcases, and usually this goes all fine. However, seemingly some rare condition can trigger the following assert: ==10071== Memcheck, a memory error detector ==10071== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==10071== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info ==10071== Command: /data/schuetto/auto_regtesting/regtests/cp2k/exe/local_valgrind/cp2k.sdbg O-B97-q6.inp ==10071== blockSane: fail -- redzone-hi valgrind: m_mallocfree.c:2042 (vgPlain_arena_free): Assertion 'blockSane(a, b)' failed. host stacktrace: ==10071==at 0x38083F48: show_sched_status_wrk (m_libcassert.c:343) ==10071==by 0x38084064: report_and_quit (m_libcassert.c:415) ==10071==by 0x380841F1: vgPlain_assert_fail (m_libcassert.c:481) ==10071==by 0x380925E6: vgPlain_arena_free (m_mallocfree.c:2042) ==10071==by 0x3811B51E: vgModuleLocal_img_done (image.c:778) ==10071==by 0x380BAFF0: vgModuleLocal_read_elf_debug_info (readelf.c:3027) ==10071==by 0x380B343A: di_notify_ACHIEVE_ACCEPT_STATE (debuginfo.c:749) ==10071==by 0x380B343A: vgPlain_di_notify_mmap (debuginfo.c:1067) ==10071==by 0x380D963D: vgModuleLocal_generic_PRE_sys_mmap (syswrap-generic.c:2367) ==10071==by 0x3810D6A1: vgSysWrap_amd64_linux_sys_mmap_before (syswrap-amd64-linux.c:637) ==10071==by 0x380D60A4: vgPlain_client_syscall (syswrap-main.c:1905) ==10071==by 0x380D2B9A: handle_syscall (scheduler.c:1118) ==10071==by 0x380D424E: vgPlain_scheduler (scheduler.c:1435) ==10071==by 0x380E37B6: thread_wrapper (syswrap-linux.c:102) ==10071==by 0x380E37B6: run_a_thread_NORETURN (syswrap-linux.c:155) sched status: running_tid=1 Thread 1: status = VgTs_Runnable (lwpid 10071) ==10071==at 0x3232A1761A: mmap (in /lib64/ld-2.12.so) ==10071==by 0x3232A076B9: _dl_map_object_from_fd (in /lib64/ld-2.12.so) ==10071==by 0x3232A08399: _dl_map_object (in /lib64/ld-2.12.so) ==10071==by 0x3232A0C3A1: openaux (in /lib64/ld-2.12.so) ==10071==by 0x3232A0E285: _dl_catch_error (in /lib64/ld-2.12.so) ==10071==by 0x3232A0CA84: _dl_map_object_deps (in /lib64/ld-2.12.so) ==10071==by 0x3232A0330F: dl_main (in /lib64/ld-2.12.so) ==10071==by 0x3232A160AD: _dl_sysdep_start (in /lib64/ld-2.12.so) ==10071==by 0x3232A014A3: _dl_start (in /lib64/ld-2.12.so) ==10071==by 0x3232A00B07: ??? (in /lib64/ld-2.12.so) ==10071==by 0x1: ??? ==10071==by 0xFFF000A32: ??? ==10071==by 0xFFF000A7C: ??? Note: see also the FAQ in the source distribution. I have attempted to reproduce this (running exactly the same commands and binary, etc.) but this didn't fail. The error appears to happen before our executable is really running, so maybe something is wrong on startup ? Reproducible: Couldn't Reproduce -- 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 #3 from Joost VandeVondele --- just happened again, but it is really rare. (this is a 12 core server running valgrind +-12h a day... and this seems to happen every +- 10 days). Is any of the suggestions mentioned above possible without runtime overhead and excessive IO ? ==25277== Memcheck, a memory error detector ==25277== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==25277== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info ==25277== Command: /data/schuetto/auto_regtesting/regtests/cp2k/exe/local_valgrind/cp2k.pdbg Pa.inp ==25277== blockSane: fail -- redzone-hi valgrind: m_mallocfree.c:2042 (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 #8 from Joost VandeVondele --- The failures are observed on RedHatEnterpriseServer Release:6.7 over the weekend, I have been running valgrind with as an argument essentially just a start of the relevant binary (and have it print the version number). With >20 runs (10s each) I had no failure. This is on different machine with Redhat 7.2 I'll try something similar on the other machine, but the failure is not so easy to trigger, seemingly. Dynamic libraries in my case are few, and standard I suppose: > ldd /data/vjoost/clean/cp2k/cp2k/exe/local_valgrind/cp2k.sdbg linux-vdso.so.1 => (0x7ffe09f0d000) libstdc++.so.6 => /data/vjoost/toolchain-r16447/install/lib64/libstdc++.so.6 (0x7f7d5a89) libgfortran.so.3 => /data/vjoost/toolchain-r16447/install/lib64/libgfortran.so.3 (0x7f7d5a56f000) libm.so.6 => /lib64/libm.so.6 (0x00323320) libgcc_s.so.1 => /data/vjoost/toolchain-r16447/install/lib64/libgcc_s.so.1 (0x7f7d5a33c000) libquadmath.so.0 => /data/vjoost/toolchain-r16447/install/lib64/libquadmath.so.0 (0x7f7d5a0fd000) libc.so.6 => /lib64/libc.so.6 (0x003232e0) /lib64/ld-linux-x86-64.so.2 (0x003232a0) There are many more static libraries involved, and all are compiled with debug info. The binary is also large (~142Mb). -- 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 #10 from Joost VandeVondele --- Created attachment 96782 --> https://bugs.kde.org/attachment.cgi?id=96782&action=edit self-hosting output 2 -- 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 #11 from Joost VandeVondele --- Created attachment 96783 --> https://bugs.kde.org/attachment.cgi?id=96783&action=edit self hosting output 3 -- 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 #12 from Joost VandeVondele --- Since the error is recurring, I have now tried to run the self-hosting. Running : /data/vjoost/test/outer/install/bin/valgrind --sim-hints=enable-outer --trace-children=yes --smc-check=all-non-file --run-libc-freeres=no --tool=memcheck -v /data/vjoost/test/inner/install/bin/valgrind --suppressions=/data/vjoost/toolchain-r16494/install/valgrind.supp --max-stackframe=2168152 --error-exitcode=42 --vgdb-prefix=./inner --core-redzone-size=1000 --tool=memcheck -v /data/schuetto/auto_regtesting/regtests/cp2k/exe/local_valgrind/cp2k.sdbg ethanol_both_rcut10.0_e1-1_v1-4_RSR.inp (I.e. self-hosting with added redzone, on the our executable corresponding to a failed run, with its arguments and parameters), I get a seemingly correct run. The output will be attached as out.innerouter.2 . Maybe it is worthwhile to look with expert eyes. However, after observing in that output a warning on stack switching, I added --max-stackframe=68009224472 (as suggested, seems a bit large;-), and that lead to a run with some other error (Memcheck: the 'impossible' happened: create_MC_Chunk: shadow area is accessible). -- 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 #14 from Joost VandeVondele --- Also no luck with --sanity-level=4 The fact that it is not reproducible on command is indeed not simplifying this. I wonder if this could be related to something external to valgrind triggering this. -- You are receiving this mail because: You are watching all bug changes.
