kinkatta and suse 8.2

Jay

unread,

Jun 30, 2003, 4:12:30 PM6/30/03

to

kinkatta is not working in suse 8.2
I get "Segmentation fault".
Anyone know of a solution?

mjt

unread,

Jun 30, 2003, 8:26:45 PM6/30/03

to

Jay wrote:

... got the same thing. i ran strace against it and it didnt
reveal too much. so i went to suse's site and got the newest
version. still didnt work. so, i'm done :)

... personally, i prefer gaim, then kopete
.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Michael J. Tobler: motorcyclist, surfer, # Black holes result
skydiver, and author: "Inside Linux", # when God divides the
"C++ HowTo", "C++ Unleashed" # universe by zero

Jay

unread,

Jul 1, 2003, 5:16:21 AM7/1/03

to

kinkatta is not working in suse 8.2
I get "Segmentation fault".
Anyone know of a solution?

Trying to cancel this

stephan beal

unread,

Jul 1, 2003, 12:18:27 PM7/1/03

to

Jay wrote:

> kinkatta is not working in suse 8.2
> I get "Segmentation fault".
> Anyone know of a solution?

Can you post some info about the segfault? Try:
strace kinkatta | tee out
(or whatever the name of the file is)
then post the last part of the file 'out'. That will tell us where the
failure is likely to be.

--
----- stephan beal
Registered Linux User #71917 http://counter.li.org
I speak for myself, not my employer. Contents may
be hot. Slippery when wet. Reading disclaimers makes
you go blind. Writing them is worse. You have been Warned.

mjt

unread,

Jul 1, 2003, 7:26:04 PM7/1/03

to

stephan beal wrote:

> Can you post some info about the segfault? Try:
> strace kinkatta | tee out
> (or whatever the name of the file is)
> then post the last part of the file 'out'. That will tell us where the

... it's not terribly revealing - i get a segfault too:
...
getpid() = 6019
getpid() = 6019
modify_ldt(17, {entry_number:0, base_addr:0x812c438, limit:512,
seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:0,
seg_not_present:0, useable:1}, 16) = 0
mmap2(NULL, 643072, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x41b18000
brk(0x812f000) = 0x812f000
brk(0x8130000) = 0x8130000
brk(0x8131000) = 0x8131000
brk(0x8132000) = 0x8132000
brk(0x8133000) = 0x8133000
brk(0x8134000) = 0x8134000
brk(0x8135000) = 0x8135000
brk(0) = 0x8135000
brk(0x8136000) = 0x8136000
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
mtobler@stimpy:~>

Jay

unread,

Jul 1, 2003, 12:08:28 PM7/1/03

to

stephan beal wrote:

> Jay wrote:
>
>> kinkatta is not working in suse 8.2
>> I get "Segmentation fault".
>> Anyone know of a solution?
>
> Can you post some info about the segfault? Try:
> strace kinkatta | tee out
> (or whatever the name of the file is)
> then post the last part of the file 'out'. That will tell us where the
> failure is likely to be.
>
>

here it is

_sysctl({{CTL_KERN, KERN_VERSION}, 2, 0xbffff03c, 31, (nil), 0}) = 0
readlink("/proc/self/exe", "/opt/kde3/bin/kinkatta", 255) = 22
brk(0) = 0x812c2a8
brk(0x812d2a8) = 0x812d2a8
brk(0x812e000) = 0x812e000
getpid() = 2080
getpid() = 2080
modify_ldt(17, {entry_number:0, base_addr:0x812c378, limit:512, seg_32bit:1,
con tents:0, read_exec_only:0,

limit_in_pages:0, seg_not_present:0, useable:1}, 16)
= 0
mmap2(NULL, 643072, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)

= 0x 41b0d000

brk(0x812f000) = 0x812f000
brk(0x8130000) = 0x8130000
brk(0x8131000) = 0x8131000
brk(0x8132000) = 0x8132000
brk(0x8133000) = 0x8133000
brk(0x8134000) = 0x8134000
brk(0x8135000) = 0x8135000

Gilberto F da Silva

unread,

Mar 2, 2022, 9:40:08 PM3/2/22

to

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

mjt escreveu:

> Jay wrote:
>
>> kinkatta is not working in suse 8.2 I get "Segmentation fault".
>> Anyone know of a solution?
>
> ... got the same thing. i ran strace against it and it didnt reveal
> too much. so i went to suse's site and got the newest version.
> still didnt work. so, i'm done :)
>
> ... personally, i prefer gaim, then kopete .
>

Nessa época não existia o tumbleweed?

-----BEGIN PGP SIGNATURE-----
Comment: +-----------------------------------------------------+
Comment: ! https://t.me/Gilberto_F_da_Silva !
Comment: +-----------------------------------------------------+

iF0EARECAB0WIQR6BybJIKBLy3+8xXcnG6Ba0yEbDgUCYiAchwAKCRAnG6Ba0yEb
DkA6AJ0acvKHc5jnXKqF4CtL8NBa+HzSKACgshwepWLx4UAHMAXefG6yOy5J984=
=mWud
-----END PGP SIGNATURE-----

Andrew

unread,

Mar 3, 2022, 3:08:00 AM3/3/22

to

Suse 8.2 was released back around 2003, what are you talking about?
--
This mail has been tested by https://RKIvirus.com/ and has been found to
contain Covid-19. Disinfect after reading.