Summary: | Amarok crash on session start | ||
---|---|---|---|
Product: | [Frameworks and Libraries] kio | Reporter: | Vítězslav Papiež <vitezslav.papiez> |
Component: | smb | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | andresbajotierra |
Priority: | NOR | ||
Version: | 4.3 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Vítězslav Papiež
2009-12-23 10:14:06 UTC
Sorry, but your bug description doesn't make any sense, it talks about Akregator while it is reported as an Amarok crash, and the backtrace shows a KIO problem... Check your Samba setup, seems to be the culprit. Reassigning to KIO. Yes, You are absolutely right. I make mistake. From teh backtrace: #6 0x00007f7c8c755065 in __run_exit_handlers (status=1, listp=0x7f7c8ca754a8, run_list_atexit=true) at exit.c:78 #7 0x00007f7c8c7550b5 in exit (status=22535596) at exit.c:100 #8 0x00007f7c650f41dc in load_interfaces () from /lib64/libnss_wins.so.2 #9 0x00007f7c65008205 in _nss_wins_gethostbyname_r () from /lib64/libnss_wins.so.2 libnss is forcing and exit, crashing the app. This has the same root cause as your other bug reports, you need to fix your installation Regards *** This bug has been marked as a duplicate of bug 214621 *** |