Re: [SailfishDevel] SailfishOS SDK in /opt
Well, after opening the VM in Virtualbox, it's gotten fixed. Thanks!
My installation log must've been overwritten, 'cause it has some
downloadable content stuff.
Thanks again!
--
Marcin
2014/1/4 christopher.l...@thurweb.ch
Hi Marcin
Did you get any further on this?
Zitat von Marcin M. marmistrz...@gmail.com:
I repeat, on this installation I've never had any SDK install. The remains
have been wiped with the system reinstall.
What's strange, the virtual machine exists. See the attached file
--
Marcin
As the files for the SDK vm are on your host, it looks like something went
wrong in the installation of the VM to VBox.
In your SailfishOS directory there should be a log file
InstallationLog.txt. Open this and search for MerSDK.vbox.
Around this entry you should find lots of commands for VBoxManage for the
SDK vm. I have pasted mine at the bottom of this mail.
As the files are in place, perhaps you will be able to run equivalent
commands via VBoxManage to activate the VM?
Alternatively you might find it easier to add the VM using the VirtualBox
Gui.
You should find this in /usr/share/virtualbox Start it with ./VirtualBox,
Then press the new icon.
Grüsse
Chris
backup org.merproject.mersdk operation: Execute
- arguments: /usr/bin/VBoxManage, setextradata, global,
GUI/SuppressMessages, remindAboutAutoCapture,remindAboutWrongColorDepth,
showRuntimeError.warning.HostAudioNotResponding,
remindAboutMouseIntegrationOff
Done
perform org.merproject.mersdk operation: Execute
- arguments: /usr/bin/VBoxManage, setextradata, global,
GUI/SuppressMessages, remindAboutAutoCapture,remindAboutWrongColorDepth,
showRuntimeError.warning.HostAudioNotResponding,
remindAboutMouseIntegrationOff
/usr/bin/VBoxManage started, arguments: setextradata global
GUI/SuppressMessages remindAboutAutoCapture,remindAboutWrongColorDepth,
showRuntimeError.warning.HostAudioNotResponding,
remindAboutMouseIntegrationOff
Done
backup org.merproject.mersdk operation: Execute
- arguments: /usr/bin/VBoxManage, createvm, --name, MerSDK,
--register, --basefolder, /Users/christopherlamb/SailfishOS/mersdk,
UNDOEXECUTE, /usr/bin/VBoxManage, unregistervm, --delete, MerSDK,
errormessage=Please shutdown the MerSDK VM
Done
perform org.merproject.mersdk operation: Execute
- arguments: /usr/bin/VBoxManage, createvm, --name, MerSDK,
--register, --basefolder, /Users/christopherlamb/SailfishOS/mersdk,
UNDOEXECUTE, /usr/bin/VBoxManage, unregistervm, --delete, MerSDK,
errormessage=Please shutdown the MerSDK VM
/usr/bin/VBoxManage started, arguments: createvm --name MerSDK
--register --basefolder /Users/christopherlamb/SailfishOS/mersdk
Virtual machine 'MerSDK' is created and registered.
UUID: 8d3ae826-1ce9-48db-a39c-e331f55997a4
Settings file: '/Users/christopherlamb/SailfishOS/mersdk/MerSDK/
MerSDK.vbox'
Done
backup org.merproject.mersdk operation: Execute
- arguments: /usr/bin/VBoxManage, modifyvm, MerSDK, --ostype,
Linux26, --memory, 512, --vram, 10, --ioapic, on, --pae, on, --nic1, nat,
--nictype1, virtio, --natpf1, guestssh,tcp,127.0.0.1,,,22, --natpf1,
guestwww,tcp,127.0.0.1,8080,,9292, --nic2, intnet, --intnet2,
sailfishsdk, --nictype2, virtio, --macaddress2, 08005A11F155
Done
perform org.merproject.mersdk operation: Execute
- arguments: /usr/bin/VBoxManage, modifyvm, MerSDK, --ostype,
Linux26, --memory, 512, --vram, 10, --ioapic, on, --pae, on, --nic1, nat,
--nictype1, virtio, --natpf1, guestssh,tcp,127.0.0.1,,,22, --natpf1,
guestwww,tcp,127.0.0.1,8080,,9292, --nic2, intnet, --intnet2,
sailfishsdk, --nictype2, virtio, --macaddress2, 08005A11F155
/usr/bin/VBoxManage started, arguments: modifyvm MerSDK --ostype Linux26
--memory 512 --vram 10 --ioapic on --pae on --nic1 nat --nictype1 virtio
--natpf1 guestssh,tcp,127.0.0.1,,,22 --natpf1
guestwww,tcp,127.0.0.1,8080,,9292 --nic2 intnet --intnet2 sailfishsdk
--nictype2 virtio --macaddress2 08005A11F155
Done
backup org.merproject.mersdk operation: Execute
- arguments: /usr/bin/VBoxManage, storagectl, MerSDK, --name,
SATA, --add, sata, --controller, IntelAhci, --bootable, on
Done
perform org.merproject.mersdk operation: Execute
- arguments: /usr/bin/VBoxManage, storagectl, MerSDK, --name,
SATA, --add, sata, --controller, IntelAhci, --bootable, on
/usr/bin/VBoxManage started, arguments: storagectl MerSDK --name SATA
--add sata --controller IntelAhci --bootable on
Done
backup org.merproject.mersdk operation: Execute
- arguments: {0,1}, /usr/bin/VBoxManage, closemedium, disk,
/Users/christopherlamb/SailfishOS/mersdk/mer.vdi
Done
perform org.merproject.mersdk operation: Execute
- arguments: {0,1}, /usr/bin/VBoxManage, closemedium, disk,
/Users/christopherlamb/SailfishOS/mersdk/mer.vdi
/usr/bin/VBoxManage started, arguments: closemedium disk
/Users/christopherlamb/SailfishOS/mersdk/mer.vdi
Done
backup
[SailfishDevel] SailfishOS SDK in /opt
Hi, I've installed the SDK into /opt, but I'm unable to launch the emulator nor the SDK VM - only the buttons are grayed out. Is there a known workaround, so that I can avoid reinstalling into /home/$USER/ ? thanks -- Marcin ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] SailfishOS SDK in /opt
That should work, I have it in opt and have no problem. Looks more like you have an issue with you project file? check the compile output/message screen if you get qmake errors or similar? also try build-clean all. On Wednesday 01 January 2014 11.12.58 Marcin M. wrote: Hi, I've installed the SDK into /opt, but I'm unable to launch the emulator nor the SDK VM - only the buttons are grayed out. Is there a known workaround, so that I can avoid reinstalling into /home/$USER/ ? thanks -- Marcin -- Skickat från Lenovo Thinkpad X230 running Kubuntu desktop ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] SailfishOS SDK in /opt
Marcin Do you have a project open? The Emulator and SDK launch buttons remain grey until you do Chris Zitat von Mikael Hermansson m...@7b4.se: That should work, I have it in opt and have no problem. Looks more like you have an issue with you project file? check the compile output/message screen if you get qmake errors or similar? also try build-clean all. On Wednesday 01 January 2014 11.12.58 Marcin M. wrote: Hi, I've installed the SDK into /opt, but I'm unable to launch the emulator nor the SDK VM - only the buttons are grayed out. Is there a known workaround, so that I can avoid reinstalling into /home/$USER/ ? thanks -- Marcin -- Skickat från Lenovo Thinkpad X230 running Kubuntu desktop ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] SailfishOS SDK in /opt
Well, I should've said it more precisely :) - I open a project created by the first alpha. I click the emulator button. It grays out, nothing happens. -- Sent from my Nokia N900 Marcin On Wed Jan 1 15:56:45 2014 christopher.l...@thurweb.ch wrote: Marcin Do you have a project open? The Emulator and SDK launch buttons remain grey until you do Chris Zitat von Mikael Hermansson m...@7b4.se: That should work, I have it in opt and have no problem. Looks more like you have an issue with you project file? check the compile output/message screen if you get qmake errors or similar? also try build-clean all. On Wednesday 01 January 2014 11.12.58 Marcin M. wrote: Hi, I've installed the SDK into /opt, but I'm unable to launch the emulator nor the SDK VM - only the buttons are grayed out. Is there a known workaround, so that I can avoid reinstalling into /home/$USER/ ? thanks -- Marcin -- Skickat från Lenovo Thinkpad X230 running Kubuntu desktop ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] SailfishOS SDK in /opt
marcin What do the following commands give you (in a terminal)' vboxmanage list vms vboxmanage list runningvms The first should show installed VMS, the second those currently running. You may also have the Virtualbox-qt gui installed somewhere giving similar info. Grüsse Chrsi Zitat von Marcin M. marmistrz...@gmail.com: Hi, Thanks, it was a (partial) fix. Now, when trying to build, I get: Virtual Machine 'MerSDK' is not installed! -- Marcin 2014/1/1 christopher.l...@thurweb.ch Hi Marcin The project templates have changed quite a bit since then, and I am fairly sure I have seen the same behaviour. Try a new default project. If that works, then you can copy across your c++ / qml files from your alpha project into the new default project. Chris Zitat von Marcin Mielniczuk marmistrz...@gmail.com: Well, I should've said it more precisely :) - I open a project created by the first alpha. I click the emulator button. It grays out, nothing happens. -- Sent from my Nokia N900 Marcin On Wed Jan 1 15:56:45 2014 christopher.l...@thurweb.ch wrote: Marcin Do you have a project open? The Emulator and SDK launch buttons remain grey until you do Chris Zitat von Mikael Hermansson m...@7b4.se: That should work, I have it in opt and have no problem. Looks more like you have an issue with you project file? check the compile output/message screen if you get qmake errors or similar? also try build-clean all. On Wednesday 01 January 2014 11.12.58 Marcin M. wrote: Hi, I've installed the SDK into /opt, but I'm unable to launch the emulator nor the SDK VM - only the buttons are grayed out. Is there a known workaround, so that I can avoid reinstalling into /home/$USER/ ? thanks -- Marcin -- Skickat från Lenovo Thinkpad X230 running Kubuntu desktop ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list ___ SailfishOS.org Devel mailing list
Re: [SailfishDevel] SailfishOS SDK in /opt
I'm using simply virtualbox-4.3 from the official repo:
$ apt-cache policy virtualbox-4.3
virtualbox-4.3:
Installed: 4.3.6-91406~Ubuntu~raring
Candidate: 4.3.6-91406~Ubuntu~raring
Version table:
*** 4.3.6-91406~Ubuntu~raring 0
500 http://download.virtualbox.org/virtualbox/debian/saucy/contrib
amd64 Packages
100 /var/lib/dpkg/status
4.3.0-89960~Ubuntu~raring 0
700 http://packages.linuxmint.com/ petra/import amd64 Packages
$ vboxmanage list vms
WinXP {4bfb163e-8537-470b-81ac-542629875e44}
SailfishOS Emulator {10d6d122-6581-42da-b6e0-562266fced05}
vboxmanage list runningvms shows nothing
--
Marcin
2014/1/1 christopher.l...@thurweb.ch
marcin
What do the following commands give you (in a terminal)'
vboxmanage list vms
vboxmanage list runningvms
The first should show installed VMS, the second those currently running.
You may also have the Virtualbox-qt gui installed somewhere giving similar
info.
Grüsse
Chrsi
Zitat von Marcin M. marmistrz...@gmail.com:
Hi,
Thanks, it was a (partial) fix.
Now, when trying to build, I get:
Virtual Machine 'MerSDK' is not installed!
--
Marcin
2014/1/1 christopher.l...@thurweb.ch
Hi Marcin
The project templates have changed quite a bit since then, and I am
fairly
sure I have seen the same behaviour.
Try a new default project.
If that works, then you can copy across your c++ / qml files from your
alpha project into the new default project.
Chris
Zitat von Marcin Mielniczuk marmistrz...@gmail.com:
Well, I should've said it more precisely :) - I open a project created
by
the first alpha. I click the emulator button. It grays out, nothing
happens.
--
Sent from my Nokia N900
Marcin
On Wed Jan 1 15:56:45 2014 christopher.l...@thurweb.ch wrote:
Marcin
Do you have a project open? The Emulator and SDK launch buttons remain
grey until you do
Chris
Zitat von Mikael Hermansson m...@7b4.se:
That should work, I have it in opt and have no problem.
Looks more like you have an issue with you project file?
check the compile output/message screen if you get qmake errors or
similar?
also try build-clean all.
On Wednesday 01 January 2014 11.12.58 Marcin M. wrote:
Hi,
I've installed the SDK into /opt, but I'm unable to launch the
emulator nor the SDK VM - only the buttons are grayed out. Is there
a known workaround, so that I can avoid reinstalling into
/home/$USER/ ?
thanks
--
Marcin
--
Skickat från Lenovo Thinkpad X230 running Kubuntu desktop
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] SailfishOS SDK in /opt
Hi Marcin
That is black and white confirmation that the SDK VM is not installed.
You mentioned an earlier alpha. My (educated?) guess is that a remnant
of that was still around when you installed the latest SDK.
Maybe you should a complete (yes complete) deinstall, then reinstall.
My experience is that before upgrading you need to deinstall, then
hunt all out all the hidden directories and remove those (.scratchbox2
etc.). If you search the archives of this mailing list you will find
reference to them.
Upgrading a Sailfish SDK reminds me just a little of upgrading Oracle
on Windows: hunting and eradicating every trace in the file system and
registry before install the new version ...).
Now I need to get a loaf of bread out of the oven ... It's smelling good!
Grüsse
Chris
Zitat von Marcin M. marmistrz...@gmail.com:
I'm using simply virtualbox-4.3 from the official repo:
$ apt-cache policy virtualbox-4.3
virtualbox-4.3:
Installed: 4.3.6-91406~Ubuntu~raring
Candidate: 4.3.6-91406~Ubuntu~raring
Version table:
*** 4.3.6-91406~Ubuntu~raring 0
500
http://download.virtualbox.org/virtualbox/debian/saucy/contrib
amd64 Packages
100 /var/lib/dpkg/status
4.3.0-89960~Ubuntu~raring 0
700 http://packages.linuxmint.com/ petra/import amd64 Packages
$ vboxmanage list vms
WinXP {4bfb163e-8537-470b-81ac-542629875e44}
SailfishOS Emulator {10d6d122-6581-42da-b6e0-562266fced05}
vboxmanage list runningvms shows nothing
--
Marcin
2014/1/1 christopher.l...@thurweb.ch
marcin
What do the following commands give you (in a terminal)'
vboxmanage list vms
vboxmanage list runningvms
The first should show installed VMS, the second those currently running.
You may also have the Virtualbox-qt gui installed somewhere giving similar
info.
Grüsse
Chrsi
Zitat von Marcin M. marmistrz...@gmail.com:
Hi,
Thanks, it was a (partial) fix.
Now, when trying to build, I get:
Virtual Machine 'MerSDK' is not installed!
--
Marcin
2014/1/1 christopher.l...@thurweb.ch
Hi Marcin
The project templates have changed quite a bit since then, and I am
fairly
sure I have seen the same behaviour.
Try a new default project.
If that works, then you can copy across your c++ / qml files from your
alpha project into the new default project.
Chris
Zitat von Marcin Mielniczuk marmistrz...@gmail.com:
Well, I should've said it more precisely :) - I open a project created
by
the first alpha. I click the emulator button. It grays out, nothing
happens.
--
Sent from my Nokia N900
Marcin
On Wed Jan 1 15:56:45 2014 christopher.l...@thurweb.ch wrote:
Marcin
Do you have a project open? The Emulator and SDK launch buttons remain
grey until you do
Chris
Zitat von Mikael Hermansson m...@7b4.se:
That should work, I have it in opt and have no problem.
Looks more like you have an issue with you project file?
check the compile output/message screen if you get qmake errors or
similar?
also try build-clean all.
On Wednesday 01 January 2014 11.12.58 Marcin M. wrote:
Hi,
I've installed the SDK into /opt, but I'm unable to launch the
emulator nor the SDK VM - only the buttons are grayed out. Is there
a known workaround, so that I can avoid reinstalling into
/home/$USER/ ?
thanks
--
Marcin
--
Skickat från Lenovo Thinkpad X230 running Kubuntu desktop
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list
Re: [SailfishDevel] SailfishOS SDK in /opt
If I remember correctly, you have to uninstall (completely remove) old SDK
first and install new version afterwards. I think I've seen this in release
notes.
Julius
On Wed, Jan 01, 2014 at 07:19:36PM +0100, christopher.l...@thurweb.ch wrote:
Hi Marcin
That is black and white confirmation that the SDK VM is not installed.
You mentioned an earlier alpha. My (educated?) guess is that a
remnant of that was still around when you installed the latest SDK.
Maybe you should a complete (yes complete) deinstall, then reinstall.
My experience is that before upgrading you need to deinstall, then
hunt all out all the hidden directories and remove those
(.scratchbox2 etc.). If you search the archives of this mailing list
you will find reference to them.
Upgrading a Sailfish SDK reminds me just a little of upgrading
Oracle on Windows: hunting and eradicating every trace in the file
system and registry before install the new version ...).
Now I need to get a loaf of bread out of the oven ... It's smelling good!
Grüsse
Chris
Zitat von Marcin M. marmistrz...@gmail.com:
I'm using simply virtualbox-4.3 from the official repo:
$ apt-cache policy virtualbox-4.3
virtualbox-4.3:
Installed: 4.3.6-91406~Ubuntu~raring
Candidate: 4.3.6-91406~Ubuntu~raring
Version table:
*** 4.3.6-91406~Ubuntu~raring 0
500
http://download.virtualbox.org/virtualbox/debian/saucy/contrib
amd64 Packages
100 /var/lib/dpkg/status
4.3.0-89960~Ubuntu~raring 0
700 http://packages.linuxmint.com/ petra/import amd64 Packages
$ vboxmanage list vms
WinXP {4bfb163e-8537-470b-81ac-542629875e44}
SailfishOS Emulator {10d6d122-6581-42da-b6e0-562266fced05}
vboxmanage list runningvms shows nothing
--
Marcin
2014/1/1 christopher.l...@thurweb.ch
marcin
What do the following commands give you (in a terminal)'
vboxmanage list vms
vboxmanage list runningvms
The first should show installed VMS, the second those currently running.
You may also have the Virtualbox-qt gui installed somewhere giving similar
info.
Grüsse
Chrsi
Zitat von Marcin M. marmistrz...@gmail.com:
Hi,
Thanks, it was a (partial) fix.
Now, when trying to build, I get:
Virtual Machine 'MerSDK' is not installed!
--
Marcin
2014/1/1 christopher.l...@thurweb.ch
Hi Marcin
The project templates have changed quite a bit since then, and I am
fairly
sure I have seen the same behaviour.
Try a new default project.
If that works, then you can copy across your c++ / qml files from your
alpha project into the new default project.
Chris
Zitat von Marcin Mielniczuk marmistrz...@gmail.com:
Well, I should've said it more precisely :) - I open a project created
by
the first alpha. I click the emulator button. It grays out, nothing
happens.
--
Sent from my Nokia N900
Marcin
On Wed Jan 1 15:56:45 2014 christopher.l...@thurweb.ch wrote:
Marcin
Do you have a project open? The Emulator and SDK launch buttons remain
grey until you do
Chris
Zitat von Mikael Hermansson m...@7b4.se:
That should work, I have it in opt and have no problem.
Looks more like you have an issue with you project file?
check the compile output/message screen if you get qmake errors or
similar?
also try build-clean all.
On Wednesday 01 January 2014 11.12.58 Marcin M. wrote:
Hi,
I've installed the SDK into /opt, but I'm unable to launch the
emulator nor the SDK VM - only the buttons are grayed out. Is there
a known workaround, so that I can avoid reinstalling into
/home/$USER/ ?
thanks
--
Marcin
--
Skickat från Lenovo Thinkpad X230 running Kubuntu desktop
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list
___
SailfishOS.org Devel mailing list
--
[ Julius Loman ][ l...@kyberia.net ][ http://lomo.kyberia.net ][ icq:35732873 ]
___
SailfishOS.org Devel mailing list
[SailfishDevel] SailfishOS SDK in /opt
Hello, I would like to have SailfishOS SDK installed in /opt but if I install as a normal user, it will ask Enter your password to authorize for sudo and by the end of the installation, fail with error Could not write installer configuration to /opt/SailfishOS/SDKMaintenanceTool.ini: Access error wich is similar to Qt5 SDK problem https://bugreports.qt-project.org/browse/QTIFW-191 but can be fixed by running installation as root. For SailfishOS SDK, installation as root is forbidden: You need to run this installer as a normal user, system wide installation not supported. How to fix this bug and why is installation as root not allowed? Thanks. ___ SailfishOS.org Devel mailing list
