boinc doesnt display data sets in tasks tab

[Jonathan Aquilina]

i just joined a project im a member of and for some reason its showing that it has downloaded the data set/s and for some reason though the usual stuff that appears in tasks there is nothing

[Jonathan Aquilina (eagles051387)]

just looked at it again it says that its resuming computation but yet nothing shows in the task tab that a data set is present

[Daniel Hahler (blueyed)]

Thank you for your bug report. Please provide more information, by answering the following questions.
Does it actually do anything? I mean, is there a task running (but not displayed in the GUI) (you should be able to see this using "top" or any other system process monitoring tool)
Is there any hint in the "Messages" tab? You may want to copy'n'paste it here.
Have you tried another project and/or are you using already other projects?
Have you just upgraded boinc-client (e.g. from Gutsy to Hardy)?
Which Ubuntu version are you using? (Ubuntu Hardy has boinc-client 5.10.45-1)
Have you tried, if restarting boinc-client helps ("sudo invoke-rc.d boinc-client restart")

[Jonathan Aquilina (eagles051387)]

Sun 13 Apr 2008 08:52:17 AM CEST||Starting BOINC client version 5.10.45 for x86_64-pc-linux-gnu
Sun 13 Apr 2008 08:52:17 AM CEST||log flags: task, file_xfer, sched_ops
Sun 13 Apr 2008 08:52:17 AM CEST||Libraries: libcurl/7.18.0 OpenSSL/0.9.8g zlib/1.2.3.3 libidn/1.1
Sun 13 Apr 2008 08:52:17 AM CEST||Data directory: /var/lib/boinc-client
Sun 13 Apr 2008 08:52:17 AM CEST||Processor: 1 AuthenticAMD AMD Athlon(tm) 64 Processor 3200+ [Family 15 Model 15 Stepping 0]
Sun 13 Apr 2008 08:52:17 AM CEST||Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm 3dnowext 3dnow up rep_good
Sun 13 Apr 2008 08:52:17 AM CEST||OS: Linux: 2.6.24-16-generic
Sun 13 Apr 2008 08:52:17 AM CEST||Memory: 1.23 GB physical, 3.08 GB virtual
Sun 13 Apr 2008 08:52:17 AM CEST||Disk: 70.33 GB total, 41.36 GB free
Sun 13 Apr 2008 08:52:17 AM CEST||Local time is UTC +2 hours
Sun 13 Apr 2008 08:52:17 AM CEST|uFluids|URL: http://www.ufluids.net/; Computer ID: 72595; location: (none); project prefs: default
Sun 13 Apr 2008 08:52:17 AM CEST||No general preferences found - using BOINC defaults
Sun 13 Apr 2008 08:52:17 AM CEST||Reading preferences override file
Sun 13 Apr 2008 08:52:17 AM CEST||Preferences limit memory usage when active to 628.26MB
Sun 13 Apr 2008 08:52:17 AM CEST||Preferences limit memory usage when idle to 1130.87MB
Sun 13 Apr 2008 08:52:17 AM CEST||Preferences limit disk usage to 9.31GB

doesnt seem like its doing anything even im going ot try dumping the current data set and redownloading it to see if it changes anything

[Jonathan Aquilina (eagles051387)]

i reset the project and its not downloading anything now im on hardy beta x64. restarting the boinc client didnt do anything. its not dowloading any data now

[Frank S. Thomas (fst)]

On Sunday 13 April 2008 10:20, eagles051387 wrote:
> Sun 13 Apr 2008 08:52:17 AM CEST|uFluids|URL: http://www.ufluids.net/;

Is uFluids the only project your client is attached to? As you can see here
http://www.ufluids.net/apps.php, uFluids does not provide an application for
your platform (x86_64-pc-linux-gnu) or any other Linux platform.

Check out another project that provides an application for your platform. This
wiki page may help you finding one http://wiki.debian.org/BOINC/Projects.

Cheers,
--
Frank S. Thomas <email address hidden> PGP public key ID: 0xDC426429
Debian Developer finger <email address hidden>

[Jonathan Aquilina (eagles051387)]

im attached to a number of other projects. shouldnt the projects work regardless of being on linux or windows.

[Jonathan Aquilina (eagles051387)]

im goign to go ahead and mark this bug as invalid due to it being an issue with that particular project. sry for bothering u

[Brian Murray (brian-murray)]

Thanks for reporting this crash and helping to make Ubuntu better. This bug is actually a duplicate of bug 204631 and is being marked as such. Any discussions regarding this bug should take place in bug 204631. Feel free to submit any future bugs you may find.