Page 5 of 6
Re: Porteus Nemesis v3.4 BUG REPORTS
Posted: 23 Dec 2015, 22:02
by brokenman
I built 32bit and somewhere along the way, something was updated that broke consolekit. Now there is no shutdown button, only logout.
It seems i wasn't crazy. In 32bit, libdbus was upgraded but the dbus-openrc package from 'nosystemd' hasn't yet been updated. This is what I feared. Relying on another. Nothing I can do until the versions match up. I tried downgrading libdbus to what dbus-openrc needs but it broke. Really annoying to spend this time on things only to find my initial apprehension realized. It my have to be manjaro for me. Well, it can wait until after xmas. Merry xmas to all.
Re: Porteus Nemesis v3.4 BUG REPORTS
Posted: 23 Dec 2015, 23:16
by Ed_P
A Merry Christmas to you also brokenman.
Re: Porteus Nemesis v3.4 BUG REPORTS
Posted: 24 Dec 2015, 00:01
by aus9
merry xmas
based on peeking into /mnt/live/memory/images/ glibc locales xzm
I think I can see why I don't have aussie locales?
etc/locale.gen has a comment against my en_AU UTF8 line
Re: Porteus Nemesis v3.4 BUG REPORTS
Posted: 25 Dec 2015, 16:35
by kalo86
Merry Christmas!
Regarding the latest v3.4 I have an issue with mouse: when LXDE is loaded, there is not any mouse on my screen.
Rebooting several times it is shown but I don't know the reason.
Regards,
kalo86
Re: Porteus Nemesis v3.4 BUG REPORTS
Posted: 26 Dec 2015, 02:00
by brokenman
Rebooting several times it is shown but I don't know the reason.
What does this mean? After you reboot several times you have a working mouse? Can you please show the output of:
xinput list
Re: Porteus Nemesis v3.4 BUG REPORTS
Posted: 26 Dec 2015, 18:02
by kalo86
Hi Brokenman,
Sorry if I am not so precise describing the issue, I am trying again.
After the boot, when you see the picture in background of LXDE, there is not any working mouse pointer.
This is in 90% of cases. But rebooting more and more times, sometimes I have a working mouse.
And this happens with both the touchpad and USB mouse.
With Porteus-Nemesis v3.3 this does not happen.
Soon I will post the output of 'xinput list'.
Regards,
kalo86
EDIT: This is the output of "xinput list": Unable to connect to X server
Re: Porteus Nemesis v3.4 BUG REPORTS
Posted: 26 Dec 2015, 18:40
by Ed_P
I can confirm touchpad not working in 3.4 but working in 3.3 on new HP laptop. Haven't tried multiple reboots to see it works.
Code: Select all
guest ~ $ xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ ELAN Touchscreen id=10 [slave pointer (2)]
⎜ ↳ ELAN Touchscreen Pen id=11 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Power Button id=8 [slave keyboard (3)]
↳ HP Truevision HD id=9 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)]
↳ HP WMI hotkeys id=14 [slave keyboard (3)]
↳ HP Wireless hotkeys id=15 [slave keyboard (3)]
guest ~ $
Re: Porteus Nemesis v3.4 BUG REPORTS
Posted: 27 Dec 2015, 15:33
by brokenman
It seems libinput is not doing such a good job. I will look at switching back to evdev and synaptics driver.
Re: Porteus Nemesis v3.4 BUG REPORTS
Posted: 29 Dec 2015, 18:44
by Michele13
I'm trying Nemesis 32bit version. I've downloaded the ISO that brokenman built before christmas.
if I give the command get-devel as root it tries to download the module from this website
http://brokenman.porteus.org/porteus//m ... -devel.xzm
the url misses the i686 wich should be provided by the $ARCH variable..the problem is that it is not set when I run the script.
The problem could be at the line number 8
Code: Select all
[ "$HOSTTYPE" = x86_64 ] && ARCH=x86_64 || arch=i686
it should be
Code: Select all
[ "$HOSTTYPE" = x86_64 ] && ARCH=x86_64 || ARCH=i686
Re: Porteus Nemesis v3.4 BUG REPORTS
Posted: 29 Dec 2015, 19:10
by roadie
Michele13 wrote:I'm trying Nemesis 32bit version. I've downloaded the ISO that brokenman built before christmas.
if I give the command get-devel as root it tries to download the module from this website
http://brokenman.porteus.org/porteus//m ... -devel.xzm
the url misses the i686 wich should be provided by the $ARCH variable..the problem is that it is not set when I run the script.
The problem could be at the line number 8
Code: Select all
[ "$HOSTTYPE" = x86_64 ] && ARCH=x86_64 || arch=i686
it should be
Code: Select all
[ "$HOSTTYPE" = x86_64 ] && ARCH=x86_64 || ARCH=i686
That is confirmed here, downloads and activates properly with the change.....good catch.
EDIT: Actually, activate is installing extra files on /....INSTALL, .MTREE and .PKGINFO
Re: Porteus Nemesis v3.4 BUG REPORTS
Posted: 30 Dec 2015, 17:44
by brokenman
Thanks. Foxed this in my script now.
Re: Porteus Nemesis v3.4 BUG REPORTS
Posted: 02 Jan 2016, 18:58
by kalo86
Hi Brokenman, any news about the next release? I feel very comfortable with the new base Arch. The "pman" tool is really fantastic.
It's not a "must" but I would really appreciate if you could add the option in the contextual menu to activate/deactivate a module and to create a module from a folder.
Best regards,
kalo86
Re: Porteus Nemesis v3.4 BUG REPORTS
Posted: 02 Jan 2016, 21:28
by brokenman
It's taking a little longer this time but I want to go through and test as much as I can before the next release. It will be within the next 10 days as I have to return to work.
Re: Porteus Nemesis v3.4 BUG REPORTS
Posted: 19 Jan 2016, 02:20
by rchase
On my Kangaroo (with an Atom X5-Z8500), in both 3.4 and 3.5 (lxde), Nemesis boots to the desktop and my mouse seems to work properly -- except that the graphical cursor is invisible.
Re: Porteus Nemesis v3.4 BUG REPORTS
Posted: 19 Jan 2016, 08:58
by aus9
@rchase
This thread has not been locked and I am reluctant to do so at this time. I have copied your post to v 3.5 where it hopefully will get more attention.
Normally Nemesis bug reports are only addressed in the most recent version. Thanks for your understanding