You are not logged in.
There should be a better place to post this question, but 4L is a closed-source piece of #$%^, so I'm throwing myself at the mercy of the Arch forum.
I downloaded the '4l' package from the Arch User Repository, and I installed it and its dependencies without issue. I run the software, scale my CD artwork, select my Lightscribe drive, insert my Lightscribe media, check the print preview, and then press the 'print' button. "Printing requires root privileges." Okay, well, that's annoying.
I run 4L-gui with 'sudo,' this time, and go through all of the steps, again, except that, this time, it can't find a Lightscribe drive for me to use (and doesn't allow me to search for it manually), so that's as far as I can get. What the @#$%?
So, apparently, 4L-gui uses 4L-cli for a lot of its functions, as you might expect, including enumerating the available Lightscribe drives. Check this out:
[david@myhost bin]$ ls
4L-cli 4L-gui
[david@myhost bin]$ ./4L-cli enumerate
Using /etc/lightscribe.rc
Drive path: /dev/sr0
Usable: 1
Full name: TSSTcorp CDDVDW TS-H653N 0208 164
Model: CDDVDW TS-H653N
Manufacturer: TSSTcorp
Capabilities: monochrome
Drive inner radius: 21700
Drive outer radius: 59000
[david@myhost bin]$ sudo ./4L-cli enumerate
[sudo] password for david:
Using /etc/lightscribe.rc
[david@myhost bin]$ Wha-... Why?! It doesn't see any of my drives when I'm the root user, which means that I can't print onto my discs as either a regular user ~or~ root. I read a rumor that it uses /proc/sys/dev/cdrom/info to find the drives that it's supposed to query, and that info obviously doesn't change depending on the user. I also read a lot that 4L-gui can only find optical drives whose names begin with 'sr,' which can be a problem on some flavors of Linux, but that's obviously not my problem, since my drive is sr0.
Can anyone think of any reason that '4L-cli enumerate' would find my Lightscribe drive without issue when I'm a regular user, but not when I'm a super user? This bull@#$% is driving me crazy. Closed source software can suck my @#$%. What a simple, stupid problem to be impeding me from using my hardware: can't find the device as root, but can find it as anybody else.
Thanks for any help that you can offer.
-David Hernandez
[EDIT 08/29/13] I think that the problem is related to the fact that the package in the aur doesn't really 'install'; that is, it fails to copy the binary files into any directory in the PATH, and so, when running as root, it couldn't find 4L-cli from 4L-gui... although that doesn't really explain why my default user was able to get as far as it did. Maybe it has something to do with the fact that I was using symlinks, or... it could be a permissions issue... I should have really isolated my attempts, better, to figure out exactly what solved the problem, but here's how I was able to get it to work:
I moved my working directory to the actual location of 4L-cli and 4L-gui (rather than using symlinks), and I chmodded them both 777. This didn't change the result that I got when trying to run 4L-gui as a normal user ("Printing requires root privileges"), but, when I ran 4L-gui with sudo, it worked, so... yeah.
Good luck, anybody reading this message in the future! My recommendation, really, is to just make sure that 4L is installed properly into the PATH. My guess is that, when running 4L-gui as root, it wasn't able to find 4L-cli where it was expecting to find it.
Last edited by vencabot (2013-08-29 05:39:33)
Offline