Do you see a menu entry for Bitdefender (on the start menu)? Or maybe a desktop icon? If yes, try installing "cinnamon-menu-editor". After installing this program, open it and find Bitdefender on the menu editor. See which command is required to open it.
OK. Open the terminal and enter "bdgui", and when it crashes you paste what is shown in the terminal.
Well, if that's all it says, then you're gonna have to do a backtrace of it. I can't help you with that right now as I'm too busy, but there are quite a few tutorials for it It's quite easy.
OK I see something here https://wiki.ubuntu.com/Backtrace I don't know if is the correct method or not.
Good Lord - a 2-page thread tutorial on just how to get an antivirus installed? I thought linux had come further by this time
It's an on-demand scanner for one thing, secondly I also have a Windows PC and I don't want anything spreading to that, not to mention after the Linux Mint site was hacked it doesn't hurt to have some protection against possible infections. As Linux gains popularity so will Linux specific malware. I also have ClamTK and RKHunter installed but the reason I decided to install BD is because it has a better detection rate than ClamAV https://www.av-test.org/en/news/new...st-windows-and-linux-malware-put-to-the-test/
So? OP doesn't have much experience with Linux, there's no problem in helping. Besides, this isn't a common thing, usually double-clicking is enough to install a package. In addition, bitdefender puts their file as a .run, so it's not everybody who knows how to install this type of file.
Bitdefender can prove problematic to install. i have it running nicely on Xubuntu 14.04 964 bit) but on my other systems just use clam av. To get it to run properly and not crash, I followed some instructions from the forum https://forum.bitdefender.com/index.php?showtopic=30005 and if I remember correctly ran the following as super user:- Code: cat /opt/BitDefender-scanner/var/lib/scan/versions.dat.* |awk '/bdcore.so.linux/{print $3}'|while read bdcore_so;do touch /opt/BitDefender-scanner/var/lib/scan/$bdcore_so;bdscan --update;ln -s /opt/BitDefender-scanner/var/lib/scan/$bdcore_so /opt/BitDefender-scanner/var/lib/scan/bdcore.so;done followed by: # rm /opt/BitDefender-scanner/var/lib/scan/bdcore.so # ln -s /opt/BitDefender-scanner/var/lib/scan/bdcore.so.linux-x86_64 /opt/BitDefender-scanner/var/lib/scan/bdcore.so If initial command causes errors. The repo I referred to earlier is from http://download.bitdefender.com/repos/#
I saw the free BitDefender for Linux a few months ago and thought I'd give it a try . This worked perfectly for me with Mint :- $ sudo sh -c 'echo "deb http://download.bitdefender.com/repos/deb/ bitdefender non-free" >> /etc/apt/sources.list' $ wget http://download.bitdefender.com/repos/deb/bd.key.asc $ sudo apt-key add bd.key.asc $ sudo apt-get update $ sudo apt-get install bitdefender-scanner-gui Hope this helps .... ( I already had the key via email ) It runs just fine but only ever flags Wine related stuff.
Yes, it's all one code. Just tried to install in Kubuntu 15.10 running in VBox. There seems to be something iffy with the bdcore.so.linux-x86_64 file. Bitdefender would update but crash on scans. I then used a bdcore.so.linux-x86_64 file from my Xubuntu 14.04 where Bitdefender works properly, and overwrote the existing bdcore.so.linux-x86_64 in /opt/BitDefender-scanner/var/lib/scan. Finally all OK. I could attach the file if you want and if allowed.
Well I restored my system with Timeshift and tried quietman's installation method and the updater crashed the first time but the scanner worked just fine at first but when I used it again from a different user account it crashed so I tried my admin account again and still crashes. Ocky you mentiond there's some sort of bug in the bdcore.so.linux-x86_64 file? Its strange why is quietman able to run BD on Linux Mint? But I cant, Could it have something to do with Cinnamon or the fact I have RKhunter and ClamTK insatlled? BTW Ocky I got this error message: cannot touch ‘/opt/BitDefender-scanner/var/lib/scan/bdcore.so.linux-x86_64’: Permission denied BitDefender Antivirus Scanner for Unices v7.90123 Linux-amd64 Copyright (C) 1996-2009 BitDefender. All rights reserved. This program is licensed for home or personal use only. Usage in an office or production environment represents a violation of the license terms Error: You need superuser privileges in order to perform an update ln: failed to create symbolic link ‘/opt/BitDefender-scanner/var/lib/scan/bdcore.so’: File exists when I tried to fix it.
Yeah, I also have no idea why it works on some systems and is problematic on others. Remember you need to run the command as superuser (#) See screenshot. After that test to see if it updates and scans without crashing. If it crashes on scan try running both these as superuser: # rm /opt/BitDefender-scanner/var/lib/scan/bdcore.so # ln -s /opt/BitDefender-scanner/var/lib/scan/bdcore.so.linux-x86_64 /opt/BitDefender-scanner/var/lib/scan/bdcore.so If it then updates OK but fails to load av engines, as was the case with me, it seems to be the bdcore.so.linux-x86_64 file I replaced it as mentioned and all is fine.
I can't really shed any light on this problem. @SuperSapien I also have Clam installed so I doubt if that is the cause. I'm starting to question if it is worth using / keeping . As I mentioned earlier , it has only ever detected Wine components , which are surely FPs Also , on doing routine backups recently , Timeshift gave a message saying that a component of BitDefender couldn't be backed up . I should have taken a screenshot but forgot .... Doh ! I was running backups on three other machines at the time , and it just got overlooked. It may have given some clue as to the root of these problems you describe.
I entered sudo # rm /opt/BitDefender-scanner/var/lib/scan/bdcore.so and got this message: usage: sudo -h | -K | -k | -V usage: sudo -v [-AknS] [-g group] [-h host] [-p prompt] [-u user] usage: sudo -l [-AknS] [-g group] [-h host] [-p prompt] [-U user] [-u user] [command] usage: sudo [-AbEHknPS] [-r role] [-t type] [-C num] [-g group] [-h host] [-p prompt] [-u user] [VAR=value] [-i|-s] [<command>] usage: sudo -e [-AknS] [-r role] [-t type] [-C num] [-g group] [-h host] [-p prompt] [-u user] file ... sudo # ln -s /opt/BitDefender-scanner/var/lib/scan/bdcore.so.linux-x86_64 /opt/BitDefender-scanner/var/lib/scan/bdcore.so and this message: /bdcore.so.linux-x86_64 /opt/BitDefender-scanner/var/lib/scan/bdcore.so usage: sudo -h | -K | -k | -V usage: sudo -v [-AknS] [-g group] [-h host] [-p prompt] [-u user] usage: sudo -l [-AknS] [-g group] [-h host] [-p prompt] [-U user] [-u user] [command] usage: sudo [-AbEHknPS] [-r role] [-t type] [-C num] [-g group] [-h host] [-p prompt] [-u user] [VAR=value] [-i|-s] [<command>] usage: sudo -e [-AknS] [-r role] [-t type] [-C num] [-g group] [-h host] [-p prompt] [-u user] file ... I've also been noticing system bugs after installing BD such as keyboard bugs and tabs closing on me in Firefox plus I was unable to eject my thumbdrive yesterday.
Why? The "#" only specifies that the command represents the root user. Once you log in as root on the terminal you don't need sudo anymore. You'll only use sudo when there's a "$" at the beginning of the command, representing that you must enter that command as a regular user. Command as regular user: $ sudo foo Command as root: # foo Remember, you don't put the # or $ anywhere in the command, these are only to tell which user/provilege the command was entered. So: Command as regular user: sudo foo Command as root: foo
I tried both sudo foo and foo with those command lines and I get nothing. And I didn't put # in the terminal either.
OMG "Foo" is just an example that doesn't exist For example: Regular user: sudo apt update Root: apt update Now, if you're telling your friends commands for Linux, and you want them to know if they need to type the commands as root or regular user, you put # or $ in front of the actual command, like: Hey guys! Check out this new command: # rm -r /home If your friends know a little about Linux, they will know that the command above must be typed as root, because there's a "#" before the actual command. $ = the command must be typed as regular user # = the command must be typed as root To login as root on the terminal: su -
