First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 42232
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Alpha Porters <alpha@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Polyhead <polyhead@polyhead.net>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 42232 depends on: Show dependency tree
Show dependency graph
Bug 42232 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2004-02-20 02:15 0000 
Setiathome segfaults on current (~alpha) portage tree on alpha cpu's.  Before
this happend setiathome always had to be ran with the -nolock option to get it
to run at all.  (I've seen the problem also occur on debian and redhat)

Reproducible: Always
Steps to Reproduce:
1.run the setiathome binary using /opt/setiathome/setiathome
2.setiathome segfaults.
3.

Actual Results:  
seg fualt

Expected Results:  
Crunching packets would have been nice :)

Setiathome should be masked on alpha.

------- Comment #1 From Aron Griffis (RETIRED) 2004-02-26 12:20:28 0000 ------- 
Could you provide me with the tarball as an attachment to this bug?  I'm having
trouble downloading it right now, the site isn't responding.  I'd like to try
once before removing the keyword.  Thanks

------- Comment #2 From Aron Griffis (RETIRED) 2004-02-26 14:21:37 0000 ------- 
thanks, I verified this segfaults and added -alpha to KEYWORDS.  unfortunately
that's the best we can do until a Linux/alpha binary appears on the website
First Last Prev Next    No search results available      Search page      Enter new bug