[krfb] [Bug 407206] krfb 19.4.0 crash report

2019-05-22 Thread nl.smart
https://bugs.kde.org/show_bug.cgi?id=407206

--- Comment #11 from nl.smart  ---
you're welcome

Le mer. 22 mai 2019 à 23:48, Christoph Feck  a
écrit :

> https://bugs.kde.org/show_bug.cgi?id=407206
>
> Christoph Feck  changed:
>
>What|Removed |Added
>
> 
>  Resolution|--- |UPSTREAM
>  Status|REPORTED|RESOLVED
>
> --- Comment #10 from Christoph Feck  ---
> Thanks for the update; changing status.
>
> --
> You are receiving this mail because:
> You reported the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krfb] [Bug 407206] krfb 19.4.0 crash report

2019-05-22 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=407206

Christoph Feck  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|REPORTED|RESOLVED

--- Comment #10 from Christoph Feck  ---
Thanks for the update; changing status.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krfb] [Bug 407206] krfb 19.4.0 crash report

2019-05-22 Thread Alexey Min
https://bugs.kde.org/show_bug.cgi?id=407206

--- Comment #9 from Alexey Min  ---
Your issue 303 indeed looks like duplicate of libvncservers 219, stack trace is
the same.

After reading https://github.com/LibVNC/libvncserver/issues/219 it looks like
the issue is not specific to krfb, x11vnc is also having it with combination of
libvncserver + gnutls.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krfb] [Bug 407206] krfb 19.4.0 crash report

2019-05-22 Thread nl.smart
https://bugs.kde.org/show_bug.cgi?id=407206

--- Comment #8 from nl.smart  ---
Hi,

please find below the post let on the libvncserver github page ( I sent the
same to gnutls, but no reply)

https://github.com/LibVNC/libvncserver/issues/303

sorry, I maybe wrong...


Le mar. 21 mai 2019 à 21:47, Christoph Feck  a
écrit :

> https://bugs.kde.org/show_bug.cgi?id=407206
>
> --- Comment #7 from Christoph Feck  ---
> Could you please add the links for the upstream tickets? The information
> added
> there by developers might be useful to decide if this is an krfb issue.
>
> --
> You are receiving this mail because:
> You reported the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krfb] [Bug 407206] krfb 19.4.0 crash report

2019-05-21 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=407206

--- Comment #7 from Christoph Feck  ---
Could you please add the links for the upstream tickets? The information added
there by developers might be useful to decide if this is an krfb issue.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krfb] [Bug 407206] krfb 19.4.0 crash report

2019-05-18 Thread Alexey Min
https://bugs.kde.org/show_bug.cgi?id=407206

--- Comment #6 from Alexey Min  ---
*** Bug 406660 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[krfb] [Bug 407206] krfb 19.4.0 crash report

2019-05-18 Thread Alexey Min
https://bugs.kde.org/show_bug.cgi?id=407206

--- Comment #5 from Alexey Min  ---
*** Bug 407502 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[krfb] [Bug 407206] krfb 19.4.0 crash report

2019-05-09 Thread nl.smart
https://bugs.kde.org/show_bug.cgi?id=407206

--- Comment #4 from nl.smart  ---
Hi,
I reported the bugs to gnutls and libvncserver.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krfb] [Bug 407206] krfb 19.4.0 crash report

2019-05-06 Thread Alexey Min
https://bugs.kde.org/show_bug.cgi?id=407206

--- Comment #3 from Alexey Min  ---
You may also want report to gnutls. According to their changelogs they often
fix crashes like that. And to make backtrace even more useful, get debug
information. As I understand, if manjaro is a fork of Arch - follow this
manual: https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces . This is
not so easy on arch, though... seems they don't have debuginfo packages ready.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krfb] [Bug 407206] krfb 19.4.0 crash report

2019-05-05 Thread nl.smart
https://bugs.kde.org/show_bug.cgi?id=407206

--- Comment #2 from nl.smart  ---
Hi,
Thank you for your message.
The device is an odroid c2.
Ok, I'll report this bugg to manjaro.

Le lun. 6 mai 2019 à 01:22, Alexey Min  a écrit :

> https://bugs.kde.org/show_bug.cgi?id=407206
>
> Alexey Min  changed:
>
>What|Removed |Added
>
> 
>  CC||alexey@gmail.com
>
> --- Comment #1 from Alexey Min  ---
> Manjaro arm? On what device, I'm curious?
>
> Looking at stack trace, seems similar to ones mentioned in 406660, 406834.
> Crash is deep inside libvncserver / gnutls, looks like manjaro builds
> libvncserver with gnutls and not with openssl, and it fails somewhere
> internally.
>
> --
> You are receiving this mail because:
> You reported the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krfb] [Bug 407206] krfb 19.4.0 crash report

2019-05-05 Thread Alexey Min
https://bugs.kde.org/show_bug.cgi?id=407206

Alexey Min  changed:

   What|Removed |Added

 CC||alexey@gmail.com

--- Comment #1 from Alexey Min  ---
Manjaro arm? On what device, I'm curious?

Looking at stack trace, seems similar to ones mentioned in 406660, 406834.
Crash is deep inside libvncserver / gnutls, looks like manjaro builds
libvncserver with gnutls and not with openssl, and it fails somewhere
internally.

-- 
You are receiving this mail because:
You are watching all bug changes.