[krdc] [Bug 460089] Blue screen after conection

2022-12-06 Thread Libor Klepac
https://bugs.kde.org/show_bug.cgi?id=460089 --- Comment #14 from Libor Klepac --- Hi, it fixed itself somehow for me, on debian unstable. There is still qt5.15.6. I don't know what could fix it. I needed to reboot today and my kernel changed to 6.0.10. -- You are receiving this mail be

[krdc] [Bug 461060] New: Microphone not forwarded to remote system

2022-10-27 Thread Libor Klepac
(for "just works for everyone")? Thanks Libor *** STEPS TO REPRODUCE 1. select "Sound: On this computer" when connecting 2. test microphone on remote machine OBSERVED RESULT does not work EXPECTED RESULT works SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian GNU/Linux (avail

[krdc] [Bug 460089] Blue screen after conection

2022-10-17 Thread Libor Klepac
https://bugs.kde.org/show_bug.cgi?id=460089 Libor Klepac changed: What|Removed |Added CC||li...@klepac.cz --- Comment #2 from Libor

[valgrind] [Bug 458915] syscall sometimes returns its number instead of return code when vgdb is attached

2022-10-17 Thread Libor Peltan
https://bugs.kde.org/show_bug.cgi?id=458915 Libor Peltan changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #28 from Libor Peltan

[valgrind] [Bug 458915] syscall sometimes returns its number instead of return code when vgdb is attached

2022-10-04 Thread Libor Peltan
https://bugs.kde.org/show_bug.cgi?id=458915 --- Comment #24 from Libor Peltan --- Hi Philippe, if you have a mood to try out with Knot DNS, these are the instruction to reproduce: 1) download Knot DNS sources from https://gitlab.nic.cz/knot/knot-dns . It's OK to stay at the `master` bran

[valgrind] [Bug 458915] syscall sometimes returns its number instead of return code when vgdb is attached

2022-09-30 Thread Libor Peltan
https://bugs.kde.org/show_bug.cgi?id=458915 --- Comment #22 from Libor Peltan --- (In reply to Philippe Waroquiers from comment #21) > Valgrind should stop by itself when it finds an error (when using > --vgdb-error argument) The error mentioned by me is an error in application logic. Va

[valgrind] [Bug 458915] syscall sometimes returns its number instead of return code when vgdb is attached

2022-09-27 Thread Libor Peltan
https://bugs.kde.org/show_bug.cgi?id=458915 Libor Peltan changed: What|Removed |Added Summary|syscall sometimes returns |syscall sometimes returns

[valgrind] [Bug 458915] syscall sometimes returns its number instead of return code

2022-09-27 Thread Libor Peltan
https://bugs.kde.org/show_bug.cgi?id=458915 --- Comment #20 from Libor Peltan --- Thank you for your observations! Based on this, we actually found out that the issue happens exactly (sometimes!) when we attach vgdb to the running process, like this: ``` /usr/bin/gdb -ex "set confirm off

[valgrind] [Bug 458915] syscall sometimes returns its number instead of return code

2022-09-26 Thread Libor Peltan
https://bugs.kde.org/show_bug.cgi?id=458915 --- Comment #18 from Libor Peltan --- Created attachment 152437 --> https://bugs.kde.org/attachment.cgi?id=152437&action=edit Logs of wrong syscall retvals with no signals observed. -- You are receiving this mail because: You are watching

[valgrind] [Bug 458915] syscall sometimes returns its number instead of return code

2022-09-26 Thread Libor Peltan
https://bugs.kde.org/show_bug.cgi?id=458915 --- Comment #17 from Libor Peltan --- Thank you much for looking at this issue constantly! I confirm that with --tool=none, the issue reproduces as well. This is also true for --tool=helgrind, as I said earlier. Even with --vex-iropt-register-updates

[valgrind] [Bug 458915] syscall sometimes returns its number instead of return code

2022-09-19 Thread Libor Peltan
https://bugs.kde.org/show_bug.cgi?id=458915 --- Comment #14 from Libor Peltan --- Created attachment 152228 --> https://bugs.kde.org/attachment.cgi?id=152228&action=edit Strace failing syscalls from a reproducing scenario. -- You are receiving this mail because: You are watching

[valgrind] [Bug 458915] syscall sometimes returns its number instead of return code

2022-09-19 Thread Libor Peltan
https://bugs.kde.org/show_bug.cgi?id=458915 --- Comment #13 from Libor Peltan --- (In reply to Paul Floyd from comment #12) > And do you see any ERESTARTNOINTR with strace? No. I see only those return error from any failed syscalls: EAGAIN ECONNREFUSED EEXIST EINPROGRESS EINTR EINVAL ENO

[valgrind] [Bug 458915] syscall sometimes returns its number instead of return code

2022-09-19 Thread Libor Peltan
https://bugs.kde.org/show_bug.cgi?id=458915 --- Comment #11 from Libor Peltan --- Created attachment 152221 --> https://bugs.kde.org/attachment.cgi?id=152221&action=edit The log of valgrind returning wrong syscall value five times. -- You are receiving this mail because: You are watch

[valgrind] [Bug 458915] syscall sometimes returns its number instead of return code

2022-09-19 Thread Libor Peltan
https://bugs.kde.org/show_bug.cgi?id=458915 --- Comment #10 from Libor Peltan --- @Philippe Thanks much for your deep analysis! I wouldn't be able to see such things in conext. However, I think you are not entirely correct. I think the observed bug is not caused by other thread aborting.

[valgrind] [Bug 458915] syscall sometimes returns its number instead of return code

2022-09-16 Thread Libor Peltan
https://bugs.kde.org/show_bug.cgi?id=458915 --- Comment #7 from Libor Peltan --- Created attachment 152095 --> https://bugs.kde.org/attachment.cgi?id=152095&action=edit The log of valgrind crashing knotd after mishandled epoll_wait syscall. -- You are receiving this mail because:

[valgrind] [Bug 458915] syscall sometimes returns its number instead of return code

2022-09-16 Thread Libor Peltan
https://bugs.kde.org/show_bug.cgi?id=458915 --- Comment #6 from Libor Peltan --- I frankly don't understand the flags of futex syscall. This is what glibc does. To possibly bring more light to the issue, I'm going to upload a log from completely different reproducer. This time, th

[valgrind] [Bug 458915] syscall sometimes returns its number instead of return code

2022-09-15 Thread Libor Peltan
https://bugs.kde.org/show_bug.cgi?id=458915 --- Comment #4 from Libor Peltan --- Created attachment 152081 --> https://bugs.kde.org/attachment.cgi?id=152081&action=edit The log of valgrind crashing glibc by mishandled futex syscall. -- You are receiving this mail because: You are w

[valgrind] [Bug 458915] syscall sometimes returns its number instead of return code

2022-09-15 Thread Libor Peltan
https://bugs.kde.org/show_bug.cgi?id=458915 --- Comment #3 from Libor Peltan --- @Paul Helgrind reports oh so many errors, I can hardly find any clue in them. I guess this tool is not intended for debugging (mostly) lockless multi-threaded programs (where concurrency is controlled by libRCU or

[valgrind] [Bug 458915] New: syscall sometimes returns its number instead of return code

2022-09-09 Thread Libor Peltan
https://bugs.kde.org/show_bug.cgi?id=458915 Bug ID: 458915 Summary: syscall sometimes returns its number instead of return code Product: valgrind Version: 3.18.1 Platform: Ubuntu Packages OS: Linux

[krunner] [Bug 383554] New: Cannot start app by Alt-F2

2017-08-15 Thread Libor
https://bugs.kde.org/show_bug.cgi?id=383554 Bug ID: 383554 Summary: Cannot start app by Alt-F2 Product: krunner Version: 5.9.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi

[kaffeine] [Bug 367517] Kaffein crash, when I was traying play mp4 video.

2016-09-15 Thread Libor Lacina via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367517 --- Comment #2 from Libor Lacina --- After distribution upgrade (terminal: zypper dup) is forking fine. Thanks. -- You are receiving this mail because: You are watching all bug changes.

[kaffeine] [Bug 367517] New: Kaffein crash, when I was traying play mp4 video.

2016-08-18 Thread Libor Lacina via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367517 Bug ID: 367517 Summary: Kaffein crash, when I was traying play mp4 video. Product: kaffeine Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED