Description of problem: I have reinstall this system suck has been working for about 24 hous every 15 minutes getting the news and with out any warning i get this: *** stack smashing detected ***: /usr/libexec/news/suck terminated ======= Backtrace: ========= /lib64/libc.so.6[0x3cc2e75d9f] /lib64/libc.so.6(__fortify_fail+0x37)[0x3cc2f06bd7] /lib64/libc.so.6(__fortify_fail+0x0)[0x3cc2f06ba0] /usr/libexec/news/suck[0x40959e] /usr/libexec/news/suck[0x402feb] /lib64/libc.so.6(__libc_start_main+0xf5)[0x3cc2e21d65] /usr/libexec/news/suck[0x403da9] etc I have not done any system updates before this happend, ther where also no system changes with exeption of creating new partions Version-Release number of selected component: suck-4.3.2-42.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/libexec/news/suck news.gtm.iss.as9143.net -c -A -bp -n -q -W 1 10 -sg -hl localhost -dt /var/lib/news/suck -dm /var/lib/news/suck/Msgs -dd /var/lib/news/suck -u -Q crash_function: do_lockfile executable: /usr/libexec/news/suck kernel: 3.12.5-302.fc20.x86_64 runlevel: N 5 type: CCpp uid: 9 Truncated backtrace: Thread no. 1 (1 frames) #5 do_lockfile at suckutils.c:216
Created attachment 842746 [details] File: backtrace
Created attachment 842747 [details] File: cgroup
Created attachment 842748 [details] File: core_backtrace
Created attachment 842749 [details] File: dso_list
Created attachment 842750 [details] File: environ
Created attachment 842751 [details] File: limits
Created attachment 842752 [details] File: maps
Created attachment 842753 [details] File: open_fds
Created attachment 842754 [details] File: proc_pid_status
Created attachment 842755 [details] File: var_log_messages
Unfortunately, I could not reporduced your faiure, so I wold like to suggest an full update of your system. It may be nice, if you can report the result of your test run after the update.
(In reply to Jochen Schmitt from comment #11) > Unfortunately, I could not reproduce your faiure, so I wold like to suggest > an full update of your system. It may be nice, if you can report the result > of your test run after the update. Hello, I have updated the system and tried to get news but i got the same error b.t.w. the system was created on the 26th December and was up to date the moment the problem occurred. I was busy in the morning when it happened for the first time creating swap partitions and data partitions, and had not done any os updates until the issue appeared. I i can give you any more information let me know. Ronald
Ok I have done the following: removed suck with: yum erase suck installed suck: yum install suck in apper enabled the Fedora 20 debug repository in apper installed the debug information for suck.. While trying to find out how to use the debug information I tried to extract the command line to use the suck executable To my big surprise suck worked and the the last 24 hours keep on working... I am abit at a loss and do not know what to do now.... I will wait another 24 hours and put the above in Bugzilla and close the ticket. Suck has been working well for the last couple of days. Thanks for your support in this strange issue.