razer_bcd service is not running in my system

[jsanzdev]

Hello, I have linux mint 17.3 and I try to install the driver in my system. I have a few problems.

1- I don't have the .desktop app in my system. I have to go manualy to /usr/share/razer_chroma_controller to initiate the app.

2- The second thing when I use the app it says that.

I have razer mamba 2012.

Thanks for the help!

[lah7]

1. I presume this is the Cinnamon desktop edition? The .desktop probably wants editing, I had to do the same for the MATE desktop.

(I think we ought to remove the "OnlyShowIn=Unity;MATE;" entry)

---

2. What do you see when you type: sudo service razer_bcd start

[jsanzdev]

Hello, yes I'm using the Cinnamon desktop edition.

sudo service razer_bcd start razer_bcd start/post-stop, process 12904

[terricain]

Also the mamba isn't fully integrated into the daemon. You'll have to use the raw driver files for that

[incryptx]

Does someone have a fix for this?

I get the graphic shown above, with the D-Dbus with the razer_bcd error?

I also get the application icons and clicking on the razer taskbar icon does nothing.

I blew up my system following some instructions about root level permissions for D-Bus and how easy it is to muck it up, which I apparently did.

Also, when "making" this, I get some "system violation" about poorly written code?

What's that about?

A fix or solution, would be nice.

New to all of this.

Thanks

[terricain]

@incryptx

Also, when "making" this, I get some "system violation" about poorly written code?

Examples of this would help.

[incryptx]

It's some dialog presented by Ubuntu 14.04 in a GUI Window referencing the package would not work, and giving me two buttons, "Continue Anyway" or "Cancel". I think it may be from the repository?

On 02/24/2016 12:45 PM, Terry Cain wrote:

@incryptx https://github.com/incryptx

Also, when "making" this, I get some "system violation" about
poorly written code?

Examples of this would help.

— Reply to this email directly or view it on GitHub https://github.com/pez2001/razer_chroma_drivers/issues/77#issuecomment-188447478.

[terricain]

I don't think anything in this repo would bring up such dialog. If you could get a screenshot that would help more.

[incryptx]

I'll try!

On 02/24/2016 02:23 PM, Terry Cain wrote:

I don't think anything in this repo would bring up such dialog. If you could get a screenshot that would help more.

— Reply to this email directly or view it on GitHub https://github.com/pez2001/razer_chroma_drivers/issues/77#issuecomment-188481670.

[incryptx]

Ok,

In following your instructions from the readme, there is a "typo" in the line which changes directories, and ends in the word "drive".

This word should be "driver" and those who cut & paste the line will get an error, path not found.

|git clone --depth=1
https://github.com/pez2001/razer_blackwidow_chroma_driver.git cd
razer_blackwidow_chroma_*drive"r"* |

Install the packages needed to build the software:

|sudo apt-get install -y dpkg-dev libdbus-1-dev jq libsdl2-dev
libsdl2-image-dev libfftw3-dev |

Build the software and driver:

|make |

Build the package:

|./package_for_ubuntu.sh OR ./package_for_debian.sh|

After I built the .deb file and installed it with ./ubuntu.sh, the warning comes from the "Ubuntu System OS" warning of "bad code" which can break the system, and warning not to install this. I ignored the warning and installed anyway, and now on backups, I get warnings that DBus could not be backed up.

I think the error might be associated or repo-ed by building the .deb and installing with Ubuntu.sh on Ubuntu (which is based on debian)/

I wonder if I installed the .deb with the ./debian.sh if I would still get the warning, or if it would allow it to work?

I will attempt to take a screenshot (but as I just came from Windows and this stuff is new), I will need to figure out how first, and then remove the package and attempt to reinstall it.

Thanks for the assist here.

On 02/24/2016 07:46 PM, IT Support wrote:

I'll try!

On 02/24/2016 02:23 PM, Terry Cain wrote:

I don't think anything in this repo would bring up such dialog. If you could get a screenshot that would help more.

— Reply to this email directly or view it on GitHub https://github.com/pez2001/razer_chroma_drivers/issues/77#issuecomment-188481670.

[terricain]

How did you install the deb?

[incryptx]

Through USC, by right clicking on the .deb

I was going to try both processes today, installing from the .deb and installing pure debian and see if I could capture some screens?

Right now, I have a problem with the build tools on the same machine, which this install (via DBus) blew the OS and had to be rebuilt. Now rebuilt, I am reloading build tools and one is balking.

Depends: libsdl2-2.0-0 (= 2.0.2+dfsg1-3ubuntu1.1)

Something about wayland and mesa i386 binaries. Attempting to resolve the issues now.

Although I run a AMD64, most of the tools and binaries for this and steam, seem to require the i386 set to get anything done.

I was a SDET for MS on NT for ten years. Although coding is second nature, it's been twenty years since I looked at Linux.

It's matured now. Back then it was childish and confusing.

I will take some screenshots and get back to you.

Thanks for the assist. I just don't understand why HW makers like Logitech, Saitek, Razor, and others don't release Linux versions of drivers just to keep there options open in the Linux community, should the market place open, they would be set. It's also just a neighborly thing to do.

On 02/25/2016 08:16 AM, Terry Cain wrote:

How did you install the deb?

— Reply to this email directly or view it on GitHub https://github.com/pez2001/razer_chroma_drivers/issues/77#issuecomment-188859673.

[terricain]

Not a clue, would be so much easier if razer provided a driver, and in future don't use software centre, its a pile of rubbish. Just sudo dpkg -i file.deb and then sudo apt-get install -f

[incryptx]

Attached is a screenshot recieved after attempting to install the .deb

It is a warning thrown by the Software Center.

On 02/25/2016 08:32 AM, IT Support wrote:

Through USC, by right clicking on the .deb

I was going to try both processes today, installing from the .deb and installing pure debian and see if I could capture some screens?

Right now, I have a problem with the build tools on the same machine, which this install (via DBus) blew the OS and had to be rebuilt. Now rebuilt, I am reloading build tools and one is balking.

Depends: libsdl2-2.0-0 (= 2.0.2+dfsg1-3ubuntu1.1)

Something about wayland and mesa i386 binaries. Attempting to resolve the issues now.

Although I run a AMD64, most of the tools and binaries for this and steam, seem to require the i386 set to get anything done.

I was a SDET for MS on NT for ten years. Although coding is second nature, it's been twenty years since I looked at Linux.

It's matured now. Back then it was childish and confusing.

I will take some screenshots and get back to you.

Thanks for the assist. I just don't understand why HW makers like Logitech, Saitek, Razor, and others don't release Linux versions of drivers just to keep there options open in the Linux community, should the market place open, they would be set. It's also just a neighborly thing to do.

On 02/25/2016 08:16 AM, Terry Cain wrote:

How did you install the deb?

— Reply to this email directly or view it on GitHub https://github.com/pez2001/razer_chroma_drivers/issues/77#issuecomment-188859673.

[incryptx]

Here are the details.

I did build and use the .deb on a user called /susan and saved the .deb

Then used it again on the same machine, but renamed the user /bill when I installed the .deb

I see the permissions problem, and can rebuild the OS with that name to test it again by rebuilding the .deb

BUT, this same error happened on that machine, with the proper user name, and still gave the "bad code" pop-up.

Details: http://pastebin.com/Q8snh3qL

in future use pastebin links

On 02/25/2016 09:49 AM, IT Support wrote:

Attached is a screenshot recieved after attempting to install the .deb

It is a warning thrown by the Software Center.

On 02/25/2016 08:32 AM, IT Support wrote:

Through USC, by right clicking on the .deb

I was going to try both processes today, installing from the .deb and installing pure debian and see if I could capture some screens?

Right now, I have a problem with the build tools on the same machine, which this install (via DBus) blew the OS and had to be rebuilt. Now rebuilt, I am reloading build tools and one is balking.

Depends: libsdl2-2.0-0 (= 2.0.2+dfsg1-3ubuntu1.1)

Something about wayland and mesa i386 binaries. Attempting to resolve the issues now.

Although I run a AMD64, most of the tools and binaries for this and steam, seem to require the i386 set to get anything done.

I was a SDET for MS on NT for ten years. Although coding is second nature, it's been twenty years since I looked at Linux.

It's matured now. Back then it was childish and confusing.

I will take some screenshots and get back to you.

Thanks for the assist. I just don't understand why HW makers like Logitech, Saitek, Razor, and others don't release Linux versions of drivers just to keep there options open in the Linux community, should the market place open, they would be set. It's also just a neighborly thing to do.

On 02/25/2016 08:16 AM, Terry Cain wrote:

How did you install the deb?

— Reply to this email directly or view it on GitHub https://github.com/pez2001/razer_chroma_drivers/issues/77#issuecomment-188859673.

[incryptx]

It's not my place to say, being the lesser knowledgeable one here, but some "dialog" in the .deb file which warns the user, "Hey, Your not Susan" or "Your not Root, either" or "Dummy, you can't copy the .deb to another machine" would be useful in warning us less fortunate of the errors of our ways.

Just a thought.

On 02/25/2016 08:45 AM, Terry Cain wrote:

Not a clue, would be so much easier if razer provided a driver, and in future don't use software centre, its a pile of rubbish. Just |sudo dpkg -i file.deb| and then |sudo apt-get install -f|

— Reply to this email directly or view it on GitHub https://github.com/pez2001/razer_chroma_drivers/issues/77#issuecomment-188871864.

[incryptx]

I'm sure I'm making mistakes you never thought a user would do, so I will try your suggestions, rebuild the .deb on the right machine, log in as root and use your non-SC commands and see where I am.

I will post those results when I have them.

Has anyone other than you been able to use this?

I ask, because sometimes devs have tools and dependancies for build processes they don't consider when the final product works in their build environment. As well, you only have us dumb end users for beta test, and the first OP has lost interest and moved on. Let's work it out so this works for everyone. My next project, after the mouse runs, is getting my Saitek X52Pro builds to work. They are just GUI front ends and don't mess with the HID layer.

[lah7]

Attached is a screenshot recieved after attempting to install the .deb

Please could you re-add the screenshot to your previous page? GitHub doesn't accept e-mail attachments, so we haven't seen the screenshot.

From the sounds of things, that's the Ubuntu Software Centre producing the message, possibly because of how its packaged - it's not a sophisticated Debian package after all.

E: razer-chroma-driver: wrong-file-owner-uid-or-gid

Just to clarify, is your project directory on a Unix filesystem? (Not one like NTFS, as it appears you have media mounted?). Only root (sudo for Debian/Ubuntu) is needed to install the package.

Has anyone other than you been able to use this?

Works perfectly fine in Ubuntu 15.10.

[incryptx]

If I may suggest:

These should be in the "readme" if this is the preferred method of install for uneducated users.

You know the SC is crap, but the rest of us are stuck with it.

|sudo dpkg -i file.deb| |sudo apt-get install -f

| | |

[incryptx]

Bad Code Message

On 02/25/2016 10:33 AM, Luke Horwell wrote:

Attached is a screenshot recieved after attempting to install the .deb
Please could you re-add the screenshot to your previous page?
GitHub doesn't accept e-mail attachments, so we haven't seen the
screenshot.

From the sounds of things, that's the Ubuntu Software Centre producing the message, possibly because of how its packaged - it's not a sophisticated Debian package after all.

E: razer-chroma-driver: wrong-file-owner-uid-or-gid
Just to clarify, is your project directory on a Unix filesystem?
(Not one like NTFS, as it appears you have media mounted?). Only
root (|sudo| for Debian/Ubuntu) is needed to install the package.

Has anyone other than you been able to use this?
Works perfectly fine in Ubuntu 15.10.

— Reply to this email directly or view it on GitHub https://github.com/pez2001/razer_chroma_drivers/issues/77#issuecomment-188920912.

[incryptx]

The .deb file was on a USB stick, probably formatted FAT32 but not NTFS and run from there.

I guess I was dumb again and should have moved it to a local drive first. Opps. But that did not cause th bad code error, as when I first built the .deb file, I was /susan and I was /root.

The GUID error is most likely the Razor Mamba not being connected at the time the .deb was run and install took place. Just a guess on my part, but again, when first attempted, the mouse was connected and nothing has changed. I still get the GUI for the Razer Configuration with the DBus error first reported by the OP.

Maybe some error checking in the scripts would help. i.e., is the mouse present? Is the user root? Is the user actually the user?

(This has always, throughout the existence of Linux, been it's deficiency. Granted, the scripts are very simple, but unintelligent and uninformative as well)

On 02/25/2016 10:33 AM, Luke Horwell wrote:

Attached is a screenshot recieved after attempting to install the .deb
Please could you re-add the screenshot to your previous page?
GitHub doesn't accept e-mail attachments, so we haven't seen the
screenshot.

From the sounds of things, that's the Ubuntu Software Centre producing the message, possibly because of how its packaged - it's not a sophisticated Debian package after all.

E: razer-chroma-driver: wrong-file-owner-uid-or-gid
Just to clarify, is your project directory on a Unix filesystem?
(Not one like NTFS, as it appears you have media mounted?). Only
root (|sudo| for Debian/Ubuntu) is needed to install the package.

Has anyone other than you been able to use this?
Works perfectly fine in Ubuntu 15.10.

— Reply to this email directly or view it on GitHub https://github.com/pez2001/razer_chroma_drivers/issues/77#issuecomment-188920912.

[terricain]

Yes lintian moans about the package, that is irrelevant (just a lot of spam, but should be fixed eventually).

Give me a few months, am not touching the code base until my year at uni is finished but last time I checked the deb installed on both Ubuntu 14.04 and 15.04, using the dpkg and apt commands, software centre is too dumb to handle this and thankfully in 16.04 is being scrapped I believe (or 16.10 god knows)

[incryptx]

Ok. Ah, what is was to be a student.

On 02/25/2016 11:23 AM, Terry Cain wrote:

Yes lintian moans about the package, that is irrelevant (just a lot of spam, but should be fixed eventually).

Give me a few months, am not touching the code base until my year at uni is finished but last time I checked the deb installed on both Ubuntu 14.04 and 15.04, using the |dpkg| and |apt| commands, software centre is too dumb to handle this.

— Reply to this email directly or view it on GitHub https://github.com/pez2001/razer_chroma_drivers/issues/77#issuecomment-188939486.

[incryptx]

Terry

I have a clean install, no errors.

After looking at the graphic the OP posted, I think now the only ting lacking or in error, is the "razer_bcd" service is not starting/started.

Because this is v14.04, as explained in the readme, I have an "upstart" system as opposed to a "systemd" service system. The command "sudo status razer_bcd" always says "razer_bcd stop/waiting" and does not change even after rebooting.

I think the service is just stuck somehow. I read one article about the service being "masked" somehow?

Any ideas on starting the service?

And if I get it to start, how can I insure it starts at bootup?

Thanks for the assist.

On 02/25/2016 11:23 AM, Terry Cain wrote:

Yes lintian moans about the package, that is irrelevant (just a lot of spam, but should be fixed eventually).

Give me a few months, am not touching the code base until my year at uni is finished but last time I checked the deb installed on both Ubuntu 14.04 and 15.04, using the |dpkg| and |apt| commands, software centre is too dumb to handle this.

— Reply to this email directly or view it on GitHub https://github.com/pez2001/razer_chroma_drivers/issues/77#issuecomment-188939486.

[incryptx]

Hello Terry

If I do "status razer_bcd" it returns: unknown job.

Upstart states this means the job or service has not been converted to upstart. A converted service would typically output the current status, i.e. Starting, Stopping, and a process ID. A non-converted service would give an error about an unknown job.

Your readme states you included an "upstart" equivilent script or converted service, but I don't think it is loading or active.

I think this is the reason the razer_bcd service will not start, which leads to the dialog error when starting the Razer Chroma Application.

The init script is not running or starting. From here, I don't know what to do or how to fix it.

Thanks for the assist.

On 02/25/2016 04:34 PM, IT Support wrote:

Terry

I have a clean install, no errors.

After looking at the graphic the OP posted, I think now the only ting lacking or in error, is the "razer_bcd" service is not starting/started.

Because this is v14.04, as explained in the readme, I have an "upstart" system as opposed to a "systemd" service system. The command "sudo status razer_bcd" always says "razer_bcd stop/waiting" and does not change even after rebooting.

I think the service is just stuck somehow. I read one article about the service being "masked" somehow?

Any ideas on starting the service?

And if I get it to start, how can I insure it starts at bootup?

Thanks for the assist.

On 02/25/2016 11:23 AM, Terry Cain wrote:

Yes lintian moans about the package, that is irrelevant (just a lot of spam, but should be fixed eventually).

Give me a few months, am not touching the code base until my year at uni is finished but last time I checked the deb installed on both Ubuntu 14.04 and 15.04, using the |dpkg| and |apt| commands, software centre is too dumb to handle this.

— Reply to this email directly or view it on GitHub https://github.com/pez2001/razer_chroma_drivers/issues/77#issuecomment-188939486.

[terricain]

@incryptx run status razer_bcd as root. Ubuntu's upstart gets very funny about who runs the status and service commands.

Could you put the /var/log/upstart/razer_bcd.log on pastebin. If its converted it to a .some_number.gz file then uncompress (or lesspipe) and put on pastebin.

[nekkz]

Same problem with Ubuntu 12.04 (elementary OS freya), using razer mamba tournament edition.

dmesg dump, after a sudo service razer_bcd start

[  585.228859] init: razer_bcd main process (4396) terminated with status 1
[  585.228873] init: razer_bcd main process ended, respawning
[  585.258179] init: razer_bcd main process (4425) terminated with status 1
[  585.258192] init: razer_bcd main process ended, respawning
[  585.278786] init: razer_bcd main process (4448) terminated with status 1
[  585.278798] init: razer_bcd main process ended, respawning
[  585.290727] init: razer_bcd main process (4471) terminated with status 1
[  585.290745] init: razer_bcd main process ended, respawning
[  585.301776] init: razer_bcd main process (4494) terminated with status 1
[  585.301784] init: razer_bcd main process ended, respawning
[  585.312930] init: razer_bcd main process (4517) terminated with status 1
[  585.312943] init: razer_bcd main process ended, respawning
[  585.325580] init: razer_bcd main process (4540) terminated with status 1
[  585.325589] init: razer_bcd main process ended, respawning
[  585.345174] init: razer_bcd main process (4563) terminated with status 1
[  585.345186] init: razer_bcd main process ended, respawning
[  585.358303] init: razer_bcd main process (4586) terminated with status 1
[  585.358317] init: razer_bcd main process ended, respawning
[  585.370537] init: razer_bcd main process (4609) terminated with status 1
[  585.370544] init: razer_bcd main process ended, respawning
[  585.381221] init: razer_bcd main process (4632) terminated with status 1
[  585.381228] init: razer_bcd respawning too fast, stopped

[terricain]

If I remember correctly the mamba may or may not be added to the daemon.

[terricain]

The mamba's been added to the daemon now. Anyone still having problems

[apol1]

I'm having trouble as well, I first installed the Chroma Linux Drivers from the website here:

https://pez2001.github.io/razer_chroma_drivers/

I followed the instructions for Ubuntu and Debian

Everything seemed to work as far as I can tell (new to Linux)

I then installed PolyChromatic from here:

https://github.com/lah7/polychromatic/releases/tag/v0.1.0

However in command line after entering ./install/install.sh I received this message:

The razer-chroma-drivers Python modules are missing! Please install them from http://pez2001.github.io/razer_chroma_drivers/ It could be possible that they are in a different path to '/usr/lib/python3/dist-packages/razer/'

---

Continue anyway? [y]

I tried running the script as root by adding sudo, same message appeared

I still see the same error message as the screen shot above

Im running Linux Ubuntu 16.04 LTS

[lah7]

It sounds like the service isn't running or didn't auto-start. What happens when you run:

sudo service razer_bcd restart

---

The razer-chroma-drivers Python modules are missing! It could be possible that they are in a different path to '/usr/lib/python3/dist-packages/razer/'

I just realised v0.1.0 has a typo in the install script, so it will keep saying that. :-1: I've released a new version of Polychromatic., so everyone will be on the same page again. :+1: