Hi all
This app is proving to a pain in the butt.
If I was running win32 I’d be looking for a virus.
4 times its screwed the system by making the OS think everything is read only, with gdm being effected most, so it cant shut down cleanly. The last failure even managed to effect the bios, so that the SATA2 HD, new couldn’t be seen when booting.
Albeit I’ve run this app as root as it will run and you can write and compile, but with the ICD2 programer on USB it does not want to talk to the PIC programer.
I checked on my previous OS Fed13 and its still the same there.
I suspect as this a QT3 app that its unhappy being run on gnome, which shouldn’t happen.
Has anyone else seen anything similar with this app ?
Its now got its own little home on another HD in a 10GB partition with KDE.
I’m aware of the risks running apps as root, but this behavior with ICEauthority is strange.
TIA
rb004a0345 wrote:
> this behavior with ICEauthority is strange.
not if you know what to expect.
–
DenverD
CAVEAT: http://is.gd/bpoMD [posted via NNTP w/openSUSE 10.3]
Any chance of sharing your wisdom then ?
Richard
It wrecks KDE when run as root, and disastrous effect on Kubuntu when run as sudo.
For access control is suse using just udev or udev and PAM or something else.
I’ve added 26-microchip.rules to /etc/udev/rules.d
with this line
#ICD2
ATTR{idVendor}==“04d8”, ATTR{idProduct}==“8001”, OWNER:=“root”, GROUP:=“microchip”,MODE:=“0660”
lsusb shows:-
Bus 003 Device 002: ID 04d8:8001 Microchip Technology, Inc. ICD2 in-circuit debugger
But when selecting the ICD2 programer within the piklab setup as a user the error message of libusb cant write to /dev/bus/usb/xxx/xxx ( I forgot the numbers)
I’ve tried changing recursively the permission to 660 on /dev/bus/usb
with same error message
recursively changing the permissions on /dev to 660 stops the error message , but it still can’t connect to the ICD2 programmer.
Running piklab from a terminal, as user, shows :-
richard@richard-g8jvm:~/Downloads> piklab
kbuildsycoca running…
DCOP Cleaning up dead connections.
piklab: version 0.15.10 (rev. distribution)
richard@richard-g8jvm:~/Downloads> ICE default IO error handler doing an exit(), pid = 6913, errno = 11
The ICE message appears about 5 secs after the app is closed down
What did I miss
Richard
rb004a0345 wrote:
> Any chance of sharing your wisdom then ?
piklab should not need to be launched as root, right?
that it is the only way it will run on your system, is evidence that
something is wrong with your system…(what is wrong, or how that
happened is not known by me…but i can guess that something went
haywire with the permissions when you built/installed Piklab)…
so, instead of running the app as root, solve the problem which keeps
it from running as expected when launched by a normal user…
another way to say that is: if you can’t run an app as a normal user
then that is the problem, and running as root is NOT a viable
solution for the problem, instead it is simply a means to mask the
symptom of the problem…
a little more: never compile as root…always compile as a regular
user and then install as root…
–
DenverD
CAVEAT: http://is.gd/bpoMD [posted via NNTP w/openSUSE 10.3]