[krdc] [Bug 441630] I can't open the KRDC app

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=441630

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #4 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[krdc] [Bug 441630] I can't open the KRDC app

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=441630

--- Comment #3 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[krdc] [Bug 441630] I can't open the KRDC app

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=441630

--- Comment #2 from ldopra...@yahoo.com.br ---
leonardo@leonardo-Inspiron-N4030:~$ valgrind krdc
==6265== Memcheck, a memory error detector
==6265== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==6265== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==6265== Command: krdc
==6265== 

valgrind: m_debuginfo/image.c:579 (set_CEnt): Assertion '!sr_isError(sr)'
failed.

host stacktrace:
==6265==at 0x58039807: ??? (in /usr/lib/valgrind/memcheck-x86-linux)
==6265==by 0x5803993D: ??? (in /usr/lib/valgrind/memcheck-x86-linux)
==6265==by 0x58039A34: ??? (in /usr/lib/valgrind/memcheck-x86-linux)
==6265==by 0x580E63DC: ??? (in /usr/lib/valgrind/memcheck-x86-linux)
==6265==by 0x580E7129: ??? (in /usr/lib/valgrind/memcheck-x86-linux)
==6265==by 0x580E7E1C: ??? (in /usr/lib/valgrind/memcheck-x86-linux)
==6265==by 0x58000E6A: ??? (in /usr/lib/valgrind/memcheck-x86-linux)
==6265==by 0x5807609A: ??? (in /usr/lib/valgrind/memcheck-x86-linux)
==6265==by 0x5806E1F6: ??? (in /usr/lib/valgrind/memcheck-x86-linux)
==6265==by 0x5809AE9D: ??? (in /usr/lib/valgrind/memcheck-x86-linux)
==6265==by 0x580D59D5: ??? (in /usr/lib/valgrind/memcheck-x86-linux)
==6265==by 0x580974E0: ??? (in /usr/lib/valgrind/memcheck-x86-linux)
==6265==by 0x58093AFC: ??? (in /usr/lib/valgrind/memcheck-x86-linux)
==6265==by 0x580954B7: ??? (in /usr/lib/valgrind/memcheck-x86-linux)
==6265==by 0x580A6182: ??? (in /usr/lib/valgrind/memcheck-x86-linux)

sched status:
  running_tid=1

Thread 1: status = VgTs_Runnable (lwpid 6265)
==6265==at 0x401A7C0: mmap (mmap.c:42)
==6265==by 0x4005E29: _dl_map_segments (dl-map-segments.h:94)
==6265==by 0x4005E29: _dl_map_object_from_fd (dl-load.c:1181)
==6265==by 0x40087A5: _dl_map_object (dl-load.c:2460)
==6265==by 0x400D973: openaux (dl-deps.c:63)
==6265==by 0x40190A2: _dl_catch_exception (dl-error-skeleton.c:196)
==6265==by 0x400DBA5: _dl_map_object_deps (dl-deps.c:249)
==6265==by 0x4003CBC: dl_main (rtld.c:1726)
==6265==by 0x40180E0: _dl_sysdep_start (dl-sysdep.c:253)
==6265==by 0x40019FE: _dl_start_final (rtld.c:414)
==6265==by 0x40019FE: _dl_start (rtld.c:521)
==6265==by 0x4000C7A: ??? (in /lib/i386-linux-gnu/ld-2.27.so)


Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.

If that doesn't help, please report this bug to: www.valgrind.org

In the bug report, send all the above text, the valgrind
version, and what OS and version you are using.  Thanks.

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

[krdc] [Bug 441630] I can't open the KRDC app

[Albert Astals Cid]

https://bugs.kde.org/show_bug.cgi?id=441630

Albert Astals Cid  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Albert Astals Cid  ---
I would suggest you contact the Linux Mint people about this.

Anyhow one thing that may help you get more information is run it from the
command line with valgrind

valgrind krdc

and see what it says

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

[krdc] [Bug 441630] I can't open the KRDC app

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=441630

ldopra...@yahoo.com.br changed:

   What|Removed |Added

 CC||ldopra...@yahoo.com.br

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