Porteus-v5.0x86_64_bugs reports

[babam]

Porteus GNOME
Dash to Dock Settings not working.

[donald]

Virtualbox crashes just after startwindow ops up

old one (VirtualBox 6.1.34) does not support kernel 5.18.8

Are you sure?
Host porteus 5 x86_64-xfce - kernel 5.18.8 - vbox 6.1.34
running another porteus 5 in a VM


This module:
http://ftp.vim.org/ftp/os/Linux/distr/p ... 4-1prt.xzm
(no devel or crippled sources module needed)

[AcnapyxoB]

Are you sure?

According to: https://www.virtualbox.org/wiki/Changelog > 6.1.36 > line 17 "Introduced initial support for kernels 5.18, 5.19"

[ncmprhnsbl]

@AcnapyxoB , the first version of /x86_64/Porteus-v5.0/kernel/VirtualBox-6.1.34-porteus-v5.0-x86_64-1prt.xzm i uploaded wasn't patched for 5.18 but did work (mostly, there were a couple of kernel modules that didn't build)
then i reuploaded (same name) a patched(with a patch i adapted from arch) version with all kernel modules present and added the patch to the update-vbox-live script...
since then, as version 6.1.36 doesn't need the 5.18 patch i've removed it from update-vbox-live script and we're in the process of placing the new prebuilt VirtualBox-6.1.36-porteus-v5.0-x86_64-1prt.xzm on the server...

short version: the vbox builder (system menu) always builds the latest version, which as of now is 6.1.36 ...

[Payoon]

Hi folks,
to clarify my Virtualbox problem:
I have first used VB 6.1.34 which didn't work. After that I have used the VB Builder from the menu ( dev.xzm and crippled sources.xzm both activated).
So I got at the end this file VirtualBox-6.1.36-porteus-v5.0-x86_64-1prt.xzm. The building went down without any error. md5sum is 9c2ff4dae34081a0050e2ecefd4e819f.

When I start VB from the menu now the startscreen opens shortly (1 -2 sec) then crashes. When I start from the console I get the follwing:

Code: Select all

process:9346): GLib-GObject-WARNING **: 05:45:57.386: cannot register existing type 'NMAgentManagerError'

(process:9346): GLib-CRITICAL **: 05:45:57.386: g_once_init_leave: assertion 'result != 0' failed

(process:9346): GLib-GObject-WARNING **: 05:45:57.386: cannot retrieve class for invalid (unclassed) type '<invalid>'
Speicherzugriffsfehler ******(that means memeory access error in German)***

P.S. Maybe I should mention: I have googled the

Code: Select all

 GLib-CRITICAL **: 05:45:57.386: g_once_init_leave: assertion 'result != 0' failed

and other people reported also, but not in connection with VB.

[AcnapyxoB]

@ncmprhnsbl sorry for the confusion but I had no way to know about these changes.
I did a test (most likely with the old vbox server version) with which Porteus 5.0 failed to start, read the VirtialBox changelog and made a conclusion.

[ncmprhnsbl]

@ncmprhnsbl sorry for the confusion but I had no way to know about these changes.

no problem, it seems there's varying degrees of function going on.. eg. all versions have worked for me and none are working for Payoon ...
@Payoon, you're using xfce4? as donald has shown, that shouldn't be a problem .. maybe try it "Always Fresh" to see if there's something conflicting..
actually, this looks like exactly the same thing: https://forums.virtualbox.org/viewtopic.php?t=102257
something to do with conflicting qt libs or something?

[Payoon]

@AcnapyxoB and ncmprhnsbl
thanks for advice. I have done the following:
I removed absolutely all modules except the base folder. Even language packs and firefox.I use XFCE4
The started again with the VB BUilder ( devel.xzm and crippled sources.xzm both activated).But the result is the same.Same error messages when starting from the console.
I think I will try some experiments and let you know.
Put on hold for now.
Payoon

[donald]

@Payoon
Did you try the module linked above in my post?
md5sum:
cbc32b7c53cff53fff64e7c9db121f80 VirtualBox-6.1.34-porteus-v5.0-x86_64-1prt.xzm

[Payoon]

@Donald
Hi Donald,
yes I did. The result is the same. The VB start window pops up for a second then VB crashes. I also tried the "virgin" Porteus 5 XFCE with all other modules removed (even language pack and firefox) same story. When i start VB from console I get the messages (which I cannot interprete) posted above. The only explanation that I have is something with my hardware. I have ACER Aspire ES 15 with 16 GB RAM. That should be modern enough, but who knows. Normally I was happy with Porteus 64 3.2 but sometimes third party software wants a newer glib cor similar things, so I decided to upgrade. On Porteus 3.2 I am running VB 5.1 with windows guest system. I don't like windows, but I need the Volkswagen sparepart catalog with all blueprints and that is only available in Windows.
Anyway thank you for your help. I think I wait sometime and maybe try later with a "ready to eat" 6.1.36 module from Porteus.

Thanks again
Payoon

[Payoon]

Hi folks
I have promised to put the thing on hold but couldn't stop trying.
The problem is partially fenced in. All the above said happened, when I was root via autologin. So I tried with 6.1.34 Module as user guest and it works ( after I had to change ownership if my old VB folder with XP guest system). So as user guest all works fine as user root the crash happens (should not be in Porteus 3.2 root works fine). But it is also possible that this limitation is coming from Oracle itself. Against that speaks that I have VB 6.1.34 host system running on Debian SID as root, wich works fine also. It would be good to know if someone could confirm that by login as root and then start VB. All very strange.
I will stay quiet now. Thanks to you all.

Payoon

[AcnapyxoB]

So as user guest all works fine as user root the crash happens

As I thought from the beginning and I wrote here:
Porteus Kernel Builder (Post by AcnapyxoB #83715)
"VirtualBox have a starts and closes bug (if Check for Updates is on), I read here and there and solved the problem by pre-creating a settings file in /home/guest/.config/VirtualBox/VirtualBox.xml"
You can try to create and put this file in /root/.config/VirtualBox/VirtualBox.xml (file is auto generated during vbox build, but only for guest)

Code: Select all

<?xml version="1.0"?>
<!--
** DO NOT EDIT THIS FILE.
** If you make changes to this file while any VirtualBox related application
** is running, your changes will be overwritten later, without taking effect.
** Use VBoxManage or the VirtualBox Manager GUI to make changes.
-->
<VirtualBox xmlns="http://www.virtualbox.org/" version="1.12-linux">
  <Global>
    <ExtraData>
      <ExtraDataItem name="GUI/Details/Elements" value="general,system,preview,display,storage,audio,network,usb,sharedFolders,description"/>
      <ExtraDataItem name="GUI/LastItemSelected" value="n=GLOBAL"/>
      <ExtraDataItem name="GUI/LastWindowPosition" value="360,225,720,450"/>
      <ExtraDataItem name="GUI/SplitterSizes" value="189,530"/>
      <ExtraDataItem name="GUI/Toolbar/MachineTools/Order" value="None"/>
      <ExtraDataItem name="GUI/Tools/LastItemsSelected" value="Welcome,Details"/>
      <ExtraDataItem name="GUI/UpdateCheckCount" value="2"/>
      <ExtraDataItem name="GUI/UpdateDate" value="never"/>
    </ExtraData>
    <MachineRegistry/>
    <NetserviceRegistry>
      <DHCPServers>
        <DHCPServer networkName="HostInterfaceNetworking-vboxnet0" IPAddress="192.168.56.100" networkMask="255.255.255.0" lowerIP="192.168.56.101" upperIP="192.168.56.254" enabled="1"/>
      </DHCPServers>
    </NetserviceRegistry>
    <SystemProperties defaultMachineFolder="/home/guest/VirtualBox" defaultHardDiskFormat="VDI" VRDEAuthLibrary="VBoxAuth" webServiceAuthLibrary="VBoxAuth" LogHistoryCount="3" proxyMode="0" exclusiveHwVirt="true"/>
    <USBDeviceFilters/>
  </Global>
</VirtualBox>

[Payoon]

@AcnapyxoB
I will try that and give feedback.
Thanks a lot.

[Payoon]

@AcnapyxoB
Good news. You solved it for me. I inserted the xml file into the module and now VB works as root and as guest. I am very glad.

Thanks very much again.

[rych]

Probably not a bug but a feature: `~/.bash_profile` is not used anymore? Had to move my `export PATH=$PATH:` etc. to `~/.bashrc` for them to come into effect