I know that LINUX users prefer the terminal. However, sometimes you just need (at least I need) a file manager to do the job. So, to run Dolphin as root open a terminal window and type:
kdesu dbus-launch dolphin
I am using LINUX as OS and Lazarus for programming. Here are some issues I came across and the solutions I have found. I hope someone will find my posts useful... PS: A lot of credit goes to Linux/OpenSUSE/Lazarus community. Any suggestions, questions, observations or comments are welcomed!
marți, 13 noiembrie 2012
miercuri, 31 octombrie 2012
Indy 10, Lazarus 1 (OpenSUSE 12.1)
After hours of attempts to install Indy 10 for Linux on Lazarus 1.0, here's the solution:
1) Download Indy 10.2.0.3 from here
2) Extract from tar.gz file (copy file to Documents>right click>Extract here [...] autodetect subfolder) This will create a directory Indy-10.2.0.3
3) Open Lazarus>Package>Open package file.
4) Select Indy-10.2.0.3/lazarus/indylaz.lpk
5) Select Options
6) Go to Compiler options>Paths
7) On the first line (Other unit files ...) add: ../fpc On Windows it also required to add lib\i386-win32
8) Now select Use>Install. If it's not working, try Compile then Use>Install.
I tried to create a TCP server and more problems appeared. Here we go:
- In order to compile the project I had to add the path to Indy units in Project>Project Options>Compile Options>Paths>Other units file... If ../fpc does not solve your problem (like in step 7 from above), you must specify the path to the fpc directory from your package
- I received some error about using threads. The solution was to add a new line into project1.lpr, so it should look like this:
uses
{$DEFINE UseCThreads}
{$IFDEF UNIX}{$IFDEF UseCThreads}
cthreads,
{$ENDIF}{$ENDIF}
Interfaces, // this includes the LCL widgetset
Forms, Unit1, lnetvisual
- The TCP server must be forced to use IPv4, othervise it will say that the port or addres is blocked or in use. Before activating the component I added:
server1.Bindings.Add.IPVersion := Id_IPv4;
Now you can do:
server1.Active:=true;
Of course, now it said that Id_IPv4 is not defined. The solution is to add in the implementation area:
uses idglobal;
[UPDATE]
Newer versions of Indy are available. See my latest posts for installation of Indy 10.6
I tried to create a TCP server and more problems appeared. Here we go:
- In order to compile the project I had to add the path to Indy units in Project>Project Options>Compile Options>Paths>Other units file... If ../fpc does not solve your problem (like in step 7 from above), you must specify the path to the fpc directory from your package
- I received some error about using threads. The solution was to add a new line into project1.lpr, so it should look like this:
uses
{$DEFINE UseCThreads}
{$IFDEF UNIX}{$IFDEF UseCThreads}
cthreads,
{$ENDIF}{$ENDIF}
Interfaces, // this includes the LCL widgetset
Forms, Unit1, lnetvisual
- The TCP server must be forced to use IPv4, othervise it will say that the port or addres is blocked or in use. Before activating the component I added:
server1.Bindings.Add.IPVersion := Id_IPv4;
Now you can do:
server1.Active:=true;
Of course, now it said that Id_IPv4 is not defined. The solution is to add in the implementation area:
uses idglobal;
[UPDATE]
Newer versions of Indy are available. See my latest posts for installation of Indy 10.6
duminică, 28 octombrie 2012
VM Virtual Box (OpenSUSE 12.1/12.2)
OpenSUSE 12.2
After installing the VM Virtual Box version 4.2.6, it won't start. In terminal it displayed the following error: "Failed to open the X display"
The solution was to recompile the VirtualBox kernel. The following packages are needed:
kernel-devel
kernel-source
gcc
Than VirtualBox kernel can be recompiled:
sudo /etc/init.d/vboxdrv setup
OpenSUSE 12.1
After installing the VM Virtual Box version 4.2.0, when I tried to add an existing VM, I came across the following error: “Could not start process Cannot talk to klauncher: Not connected to D-Bus server”.
After installing the VM Virtual Box version 4.2.6, it won't start. In terminal it displayed the following error: "Failed to open the X display"
The solution was to recompile the VirtualBox kernel. The following packages are needed:
kernel-devel
kernel-source
gcc
Than VirtualBox kernel can be recompiled:
sudo /etc/init.d/vboxdrv setup
OpenSUSE 12.1
After installing the VM Virtual Box version 4.2.0, when I tried to add an existing VM, I came across the following error: “Could not start process Cannot talk to klauncher: Not connected to D-Bus server”.
The solution for now is to downgrade
the D-Bus packages to version 1.5.8.2.1.2/3. To do this,
step-by-step:
- Open YaST>Software Management
- Search for “dbus”
- On “dbus-1”, “dbus-1-devel”, “d-bus-1-devel-doc” and “dbus-1-x11” select the option to use version 1.5.8.2.1.2/3. To do this, select the package and on the lower part of the screen you will find the tab “Versions”. There you can select the version you want to be used.
Abonați-vă la:
Postări (Atom)