I have seen this happen before with other programs and am not sure what it means... But I have downloaded the Audacity version rpm for SuSE 9.1 from the Packman site, and installed (have tried both as root and as user) on my SuSE 9.2 Pro system and noticed 2 initial problems: 1. No icons are created, Audacity doesn't show up anywhere in a menu. 2. When I go off to try and figure out what to run, I find: usr/bin/audacity looks like an executable, it's 8.5Mb... usr/share/audacity a folder with a couple of folders full of libraries or something. usr/share/doc/packages/audacity a folder full of some files, looks like something your supposed to compile manually... ?? should we have to compile the documentation files before use??... Anyway, since there was no icon created, I click on the /usr/bin/audacity file and nothing happens. Well, not exactly accurate. The harddrive starts a flurry of activity, etc. but after about 60 seconds, all that is done and no application opens on the display. Any ideas how I can figure out why Audacity won't run when I click on it's executable? -- ______________________________________________ Check out the latest SMS services @ http://www.linuxmail.org This allows you to send and receive SMS through your mailbox. Powered by Outblaze
On Friday 25 March 2005 10:22 pm, Steve Lett wrote:
I have seen this happen before with other programs and am not sure what it means...
But I have downloaded the Audacity version rpm for SuSE 9.1 from the Packman site, and installed (have tried both as root and as user) on my SuSE 9.2 Pro system and noticed 2 initial problems: 1. No icons are created, Audacity doesn't show up anywhere in a menu. 2. When I go off to try and figure out what to run, I find: usr/bin/audacity looks like an executable, it's 8.5Mb... usr/share/audacity a folder with a couple of folders full of libraries or something. usr/share/doc/packages/audacity a folder full of some files, looks like something your supposed to compile manually... ?? should we have to compile the documentation files before use??...
Anyway, since there was no icon created, I click on the /usr/bin/audacity file and nothing happens. Well, not exactly accurate. The harddrive starts a flurry of activity, etc. but after about 60 seconds, all that is done and no application opens on the display.
Any ideas how I can figure out why Audacity won't run when I click on it's executable?
Usually the best way to track these little problems is to use the shell to start the program. You'll pretty much get your answer there of why it won't start. Good rule of thumb to use, the shell. Lee -- --- KMail v1.8 --- SuSE Linux Pro v9.2 --- Registered Linux User #225206 "He's not my brother, he's just heavy." ........Bucky Katt
On Friday 25 March 2005 10:22 pm, Steve Lett wrote: Hi Steve,
I have seen this happen before with other programs and am not sure what it means...
But I have downloaded the Audacity version rpm for SuSE 9.1 from the Packman site, and installed (have tried both as root and as user) on my SuSE 9.2 Pro system and noticed 2 initial problems:
Is this a typo? Or did you actually use the 9.1 rpm to install it? On your 9.2 Pro system?
1. No icons are created, Audacity doesn't show up anywhere in a menu.
2. When I go off to try and figure out what to run, I find: usr/bin/audacity looks like an executable, it's 8.5Mb... usr/share/audacity a folder with a couple of folders full of libraries or something. usr/share/doc/packages/audacity a folder full of some files, looks
I've had very good luck in this regard with packman packages, with two caveats: a) It seems sometimes to take an init 3 -> init 5 cycle for items to appear in the menus and b) sometimes they show up in a different place than you might expect them to show up. I believe the classification declared by the packager (i.e. "internet" or "multimedia" or "development" etc.) affects where in the menu tree things show up. like something your supposed to compile manually... ?? should we have to compile the documentation files before use??... "bin" stands for "binary" and, yes, you found the executable.
Anyway, since there was no icon created, I click on the /usr/bin/audacity file and nothing happens.
Open a terminal and, (not as root) run "/usr/bin/audacity &" (no quotes, of course) to bypasses the menu system and launch it directly from the command line. FYI the " &" launches it as a background process so you keep control of the terminal, which means you can close it without also closing the program that you just launched.
Well, not exactly accurate. The harddrive starts a flurry of activity, etc. but after about 60 seconds, all that is done and no application opens on the display.
Any ideas how I can figure out why Audacity won't run when I click on it's executable?
First, verify you've installed the correct version (9.2 and not 9.1) and then try the init 3 -> init 5 cycle; /then/ search your menus. You can always add it if it doesn't show up, but try these things first. regards, - Carl p.s.: If you haven't checked this resource out before, you should: Send Audacity-users mailing list submissions to audacity-users@lists.sourceforge.net To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/audacity-users or, via email, send a message with subject or body 'help' to audacity-users-request@lists.sourceforge.net You can reach the person managing the list at audacity-users-admin@lists.sourceforge.net -- _______________________________________________________________________ C. E. Hartung Business Development & Support Services http://www.cehartung.com/ carlh@cehartung.com Dover Foxcroft, Maine, USA Public Keys 68396713 & F8207216 Reg. Linux User #350527 http://counter.li.org/ ----->>>>>http://www.fsf.org/campaigns/supportlinuxbios.html <<<<<-----
participants (3)
-
BandiPat -
Carl E. Hartung -
Steve Lett