PDA

View Full Version : Help!!!



derekeverett
July 4th, 2009, 03:51 PM
I been using this here Ubuntu for a while now.

I like it fine enough cept' the do-hicky don't always work proper.

Everytime I click on the thingy it spits out a buncha jibber-jabber...

subdivision
July 4th, 2009, 03:53 PM
I been using this here Ubuntu for a while now.

I like it fine enough cept' the do-hicky don't always work proper.

Everytime I click on the thingy it spits out a buncha jibber-jabber...

Kick your computer as hard as you can. Percussive maintenance is the answer.

Ra-Hoor-Khuit
July 4th, 2009, 03:54 PM
It's a feature!

xpod
July 4th, 2009, 04:42 PM
Try running the thingymajiggery in the whatyamacallit and see if that helps explain the jibber jabber.

LifeOnMaths
July 4th, 2009, 05:57 PM
I been using this here Ubuntu for a while now.

I like it fine enough cept' the do-hicky don't always work proper.

Everytime I click on the thingy it spits out a buncha jibber-jabber...

This sounds disturbingly like some (non-geek) friends of mine...

howefield
July 4th, 2009, 06:01 PM
Don't touch the machine, the do-hicky will start working when you change the user.

TBOL3
July 4th, 2009, 06:03 PM
press Alt+F2, type in 'gnome-terminal', and hit enter.

Then type in 'apt-get moo'

That should fix everything.

But if it doesn't, try:

aptitude moo
then
aptitude moo -v
then
aptitude moo -vv
keep going, you get the idea...

H2SO_four
July 4th, 2009, 06:05 PM
You may find a solution to your problem at this site.

Best of luck!!

http://pebkac.ubergoth.net/

koenn
July 4th, 2009, 06:29 PM
It is advised to use a descriptive topic title, that means a topic title that gives some clue about the content in the thread itself...

A generic topic title like "noob here" or "need help" does not help at all. As you may have noticed, just about everyone posting in here has some kind of a problem or issue or question ;)

And it is also adviced to use seperate threads for unrelated problems so that you can mark each one individually as solved.

Or in short terms: Help others to help you ;)


Also, when you are asked to post output from (config) files or from a command, use
brackets around (each) output. That makes it also easier to read.

.

sdlynx
July 4th, 2009, 06:36 PM
have you tried connecting the do-hicky to the thingamabob and rebooting?

CharmyBee
July 4th, 2009, 06:41 PM
have you checked the man pages?

try:

man thingy

MikeTheC
July 4th, 2009, 07:01 PM
Just be careful, because sometimes they flange without warning!

koenn
July 4th, 2009, 07:13 PM
I been using this here Ubuntu for a while now.

I like it fine enough cept' the do-hicky don't always work proper.

Everytime I click on the thingy it spits out a buncha jibber-jabber...
You're going about it the windows way. remember, Linux is not windows.

It' sounds like your permissions are all wrong. did you mess with them or run nautilus with sudo or as root ?

Other than that, it's probably a DNS issue.

CharmyBee
July 4th, 2009, 07:15 PM
remember, Linux is not windows.

Linux is not Unix either. <insert gnu argument that would derail the thread into closure here etc>

swoll1980
July 4th, 2009, 07:22 PM
Sound 'n' like you needs ur self a new johnson rod.

greenstar
July 4th, 2009, 07:39 PM
Maybe you should put some new batteries in your chemlights, open up the box and have a look-see. You might find that your wireless radio has run plumb out of squelch while you weren't paying attention - you probably forgot & left it on. You'll know this is the case by examining the gauge on your wireless radio card. Although some of the older models have a dipstick instead of a gauge, it more or less works the same.

They carry the appropriate size cans of squelch at Radio Shack. Due to the perishable nature of squelch, they don't usually keep it on the shelf but instead keep it in a cooler in the back. Just ask any of the staff to get you can or two and you'll be good to go.

Edgeworth
July 4th, 2009, 08:46 PM
Just be careful, because sometimes they flange without warning!

However, flanging can be useful if you know what you're doing. Just press the emergency photoscamps on the back of the seat behind you.

WatchingThePain
July 4th, 2009, 08:53 PM
Maybe the pc just needs a wash.

tuskenraider
July 4th, 2009, 09:02 PM
...run plumb out of squelch while you weren't paying attention - you probably forgot & left it on....


that is exactly what happend to mine... ran out of squelch.. you would think.. its 2009 we have thingamabobs that fly.. whojamafidigts that can go to all depths of the ocean.. and bazillion core computrons... you would think some einstein would come up with non-expiring squelch.. Ill bet they manufacture that stuff to fail...

they just dont build em like they used to...

:lolflag:

tusken

koenn
July 4th, 2009, 09:04 PM
Maybe the pc just needs a wash.

I'm not convinced it's a hardware problem.

It's probably related to a bug in dohicky (https://bugs.launchpad.net/dohickey/+bug/197379 ), although I wouldn't rule out the messed up permissions.

And it's probably a DNS issue.

I recommend running

apt-get update && apt-get upgrade && apt-get dist-upgrade to make sure the system is fully up to date.

calrogman
July 4th, 2009, 09:11 PM
http://www.2dayblog.com/images/dell_explosion.jpg
Well there's your problem!

TBOL3
July 4th, 2009, 09:11 PM
No, you're all thinking in the wrong vein.

Look, just connect the trans-mogifier, to the receptor, hit the big red button, and run, that should d the trick.

koenn
July 4th, 2009, 10:07 PM
you'd never have this sort of problems on Arch

Superkoop
July 4th, 2009, 11:01 PM
I been using this here Ubuntu for a while now.

I like it fine enough cept' the do-hicky don't always work proper.

Everytime I click on the thingy it spits out a buncha jibber-jabber...

I have the same problem!!! :O

Just last night I double-hit the thinger and a bigger thinger blows up in my face, so I hit the little thingy which made the bigger thinger less bigger. So I hit the other little thingy next to the other and the not so bigger bigger thinger was washed away.
Problem was I need to double-hit the thinger to do stuff, so I tried again and it happened all over again! :'(

So I concocted a plot to blow this thinger right outa the hole! I figured I play dirty and I double-hit this other thinger which blows up a bigger thinger which was less bigger than the other bigger thinger that happened the other times, and I flipping hammered the letterboard until trails of jibber-jabber was flying all over the bigger thinger! At this point the watchamacallit decided to go done dark!!! Boy, I thought I beat it that time! But turned out the watchamacallit was just playin a sneak attack!!! Well I knew I wasn't about to let it defeat me, so I done yanked the watchamacallit's bright head off, entails still attached and I threw it out ma window! After that I threw the watchamacallit's body out too, right on top of it's head! Just to make sure it wasn't coming back from the dead, I grabbed ma trusty sledgehammer and I hammered that watchamacallit until it turned into flipping pieces!

I had a problem and I faced it head on, and I won! 8-) I recommend you do the same!

Gizenshya
July 4th, 2009, 11:19 PM
does the HDD light still work? sounds like you may need some blinker fluid.

monsterstack
July 4th, 2009, 11:37 PM
Look, this is simple. All you have to do is compile the doohickey against the jibber libs in a 32-bit chroot, then bootstrap the root shell with the flux-capacitor modules to engage the BIOS amps. Once you've got that sorted out, just recompile your LAMP server to drop Apache pingbacks 2 seconds after HALD boots, and dselect whatever gets dumped in your var logs to a perl script to give you traceback on the kernel messages. Then it's just a case of simply condensing the binaries into a floating-point array alongside your file system, and checking the input for burst transfer rates every few days.

CJ Master
July 4th, 2009, 11:46 PM
1) Open up the computer.
2) Smash the hard drive with a sledgehammer.
3) There is no 3.

xpod
July 4th, 2009, 11:58 PM
I have the same problem!!! :O

Just last night I double-hit the thinger and a bigger thinger blows up in my face, so I hit the little thingy which made the bigger thinger less bigger. So I hit the other little thingy next to the other and the not so bigger bigger thinger was washed away.
Problem was I need to double-hit the thinger to do stuff, so I tried again and it happened all over again! :'(

So I concocted a plot to blow this thinger right outa the hole! I figured I play dirty and I double-hit this other thinger which blows up a bigger thinger which was less bigger than the other bigger thinger that happened the other times, and I flipping hammered the letterboard until trails of jibber-jabber was flying all over the bigger thinger! At this point the watchamacallit decided to go done dark!!! Boy, I thought I beat it that time! But turned out the watchamacallit was just playin a sneak attack!!! Well I knew I wasn't about to let it defeat me, so I done yanked the watchamacallit's bright head off, entails still attached and I threw it out ma window! After that I threw the watchamacallit's body out too, right on top of it's head! Just to make sure it wasn't coming back from the dead, I grabbed ma trusty sledgehammer and I hammered that watchamacallit until it turned into flipping pieces!

I had a problem and I faced it head on, and I won! I recommend you do the same!

And i thought i`d ripped the (edit)posterior out of it away back in post 4.

myusername
July 5th, 2009, 12:09 AM
Acidentally 93 mb of .RAR files

MaxIBoy
July 5th, 2009, 12:25 AM
Maybe the drivers for your flux capacitor are out of date? Or perhaps your RAM needs to be rotated?

EDIT: Looks like Ubuntu Q.04 has a major regression in the drivers for certain flux capacitors.
https://bugs.launchpad.net/libflux0/+bug/123975
The error is SO BAD, looks like it's even entrangled its own bug report page!

Follow these (http://www.dosgames.com/forum/about12576.html) directions to revert your drivers.

HermanAB
July 5th, 2009, 01:18 AM
Hmm, if you install Citadel and Pidgin, then your Jabber will work, but I cannot help you with the other problems.

http://www.citadel.org/doku.php/faq:everydayuse:jabber#configuring.a.jabber.client .to.access.citadel

koenn
July 5th, 2009, 08:17 AM
you would think some einstein would come up with non-expiring squelch..
it's been patented by microsoft in relation to the Microsoft Surface, but most of the software is stolen from BSD anyway. Most open source developers are afraid to touch it because of the patent treats. It is rumoured that Novell has developed a Mono interface that can interact with it but it's still very alpha, SCO claims they hold all the intellectual property rights but IBM seems willing to go to court over that based on their own patents and their initial contracts with Microsoft over DOS.

There are about 527 entries in Brainstorm about this, most of them have been tagged, prioritized, and then ignored. The next + 1 release of Ubuntu is planned to have a workaround for the issue, it seems they'll include a squelch expiry monitor made available through the restricted drivers tool which will interact with the dbus API, while Canonical is working with the Gnome project to have it report through the new notification system. Mark Shutllewoth has written about it in his blog. It could also severely mess up X, but that will be fixed in the next release +2.

WatchingThePain
July 5th, 2009, 07:25 PM
it's been patented by microsoft in relation to the Microsoft Surface, but most of the software is stolen from BSD anyway. Most open source developers are afraid to touch it because of the patent treats. It is rumoured that Novell has developed a Mono interface that can interact with it but it's still very alpha, SCO claims they hold all the intellectual property rights but IBM seems willing to go to court over that based on their own patents and their initial contracts with Microsoft over DOS.

There are about 527 entries in Brainstorm about this, most of them have been tagged, prioritized, and then ignored. The next + 1 release of Ubuntu is planned to have a workaround for the issue, it seems they'll include a squelch expiry monitor made available through the restricted drivers tool which will interact with the dbus API, while Canonical is working with the Gnome project to have it report through the new notification system. Mark Shutllewoth has written about it in his blog. It could also severely mess up X, but that will be fixed in the next release +2.

Promises, Promises ;)

Old_Grey_Wolf
July 5th, 2009, 08:31 PM
Just do a clean install. Upgrades never work.

RiceMonster
July 5th, 2009, 08:37 PM
1) Open up the computer.
2) Smash the hard drive with a sledgehammer.
3) There is no 3.

1) Open up computer
2) Smash hard drive with sledgehammer
3) ???
4) Profit

tuskenraider
July 5th, 2009, 08:40 PM
1) Open up computer
2) Smash hard drive with sledgehammer
3) ???
4) Profit

you know.. i suscribe to that 4 step process too... but i can never get to step 4.... profit always eludes me. =(



tusken :lolflag:

koenn
July 5th, 2009, 10:19 PM
...
I like it fine enough cept' the do-hicky don't always work proper.


It worked just fine in Dapper, disappeared in Feisty, and came back in Hardy but apparently there are some problems with it. Looks like the 6 month release cycle is too short to avoid regressions ....

But none of this would be a problem if the manufacturers would provide open source drivers or release the specs of their hardware so the community can create higher quality drivers.