Bionicpup64 8.0 CE

Message

belham2 · #376 Post by **belham2** » Wed 28 Nov 2018, 17:30

[Update 3]

Well, it gets even weirder.

Downloaded (using the working Firefox, installed from PPM, running in Spot) the latest Palemoon, 28.2.1

Used pArchive to get at it.

Then went to /opt (where Palemoon that comes with 7.9.7) is located.

Deleted everything in the Palemoon /opt folder.

Copied everything over from the downloaded 28.2.1 into /opt

And wouldn't you know, Bob is your Uncle, now Palemoon and permissions and downloads are working correctly. Was it the fact that the included Palemoon in the 7.9.7 ISO was not working correctly? I find that hard to believe. Maybe I got a bad download....but the md5 checked out.

Will keep at Chromium to see if I can get it going.

[Update 4]

Got Chromium working in Spot now, did the same thing to it as I did to Palemoon (download, wipe its content folder, and copy everything over). This all leads me to think I got a partially scrambled download on my end of the ISO.

Only thing now is cannot get Palemoon nor Firefox (despite linking everything in /usr/lib64/apulse folder to the usr/lib64//firefox folder), can't get either one of them to play sound. But Chromium does, so, goodbye to Palemoon and Firefox.

TTFOSS · #377 Post by **TTFOSS** » Thu 29 Nov 2018, 00:58

@666PhilB

BionicPup64 7.9.7 iso file.

I have no problem creating a non-root user, setting up permissions and logging in as that user.

xwin always failed with permission errors so I only ever used it as root.

When I try to start X using
/usr/bin/xinit $HOME/.xinitrc -- -br -nolisten tcp
or
/usr/lib/xorg/Xorg :0 -br -nolisten tcp

I get the following error messages in the log/screen

modeset(0): drmSetMaster failed: permission denied

Fatal server error: (EE) AddScreen/ScreenInit failed for driver 0

It is a common error according to
x.org/wiki/FAQErrorMessages

"This kind of problem typically occurs when you're using a big monitor with an old graphics card. You can solve it by deleting some of the highest resolutions of the deepest colour mode in the Screen section of your xorg.conf, or even the whole last Display subsection"

I tried many different combinations using xorgwizard with no improvement.
BTW the display using xorgwizard looks bad (distorted).

Have tried to set chmod 4755 on X and xinit with no luck.
As a non-root user the command "sudo xinit ..." will start X but as user root.

I am not sure the above information is helpful or indicative of the real problem.

I am trying to test the BionicPup64 7.9.7 iso on a 64bit Win-dozer-7 system using VirtualBox 5.2.22 (latest version and yes I should be using Linux but that machine is a long story that need not be discussed on this forum).

In previous Puppy-derived systems running X as a non-root user was simply a matter of modifying the inittab file (to remove the auto-login), opening up some permissions in the /dev directory and starting X with a one line script (calling xinit).

This time around I am having a tough time figuring out the permissions to hack the system.

I had similar display problems with QuirkyBionicBeaver64 8.7.1

It would be great if you could help solve this problem.
I am certainly willing to test any solution that you can get to work.

If I am not able to run X as a non-root user then I will keep looking for another system.

I have no problems running X with either FatDog64 7.2.1 or AntiX64 17.2 Full as a non-root user on the test machine.

Thanks

Revolverve · #378 Post by **Revolverve** » Fri 30 Nov 2018, 16:42

About .7 mount/unmount empty rox thing, refresh(reload) rox and everything show up .

Unrelated question out of simple curiosity:
If the answer is obvious...probably will bump in blank reply..could have ask it on fatdog or upupbb/cc topics:
startx and xwin use to gave same result??
in tahrpup it did!
Why asking? learning...
how come?
Ctrl-Alt-Backspace goes to prompt,
if:startx= goes to x + exit/restart graphical server goes to prompt.
if:xwin= goes to x + exit/restart graphical server goes to x.

bigpup · #379 Post by **bigpup** » Fri 30 Nov 2018, 16:44

I can confirm LateAdopter's observation of abnormal behavior
when mounting and unmounting partitions. I did a "from scratch" frugal of 7.9.7

It seems that when you click on a desktop drive icon.
Rox seems to open and is not a fresh display of the drive.
Seems to be same view from last time the icon was clicked on.

If you have Rox window displaying drive contents.
Click on drive icon to unmount.
Rox window goes blank, but does not close.
Close Rox window.
Click on drive icon to mount it.
Rox opens with a blank window.
Click on the Rox window refresh and it now shows drive contents.

666philb · #380 Post by **666philb** » Fri 30 Nov 2018, 19:21

bigpup and LateAdopter,

i've also noticed some oddness with rox, where clicks aren't registered.
does this older rox fix it for you? (note root warning hasn't been removed)
http://distro.ibiblio.org/puppylinux/te ... ox_old.pet

woodenshoe-wi · #381 Post by **woodenshoe-wi** » Fri 30 Nov 2018, 20:47

The problem with mounting drives looks like what radky2 reported here: https://github.com/puppylinux-woof-CE/w ... -441514667

666philb wrote:i've also noticed some oddness with rox, where clicks aren't registered.

Does this happen in a way you can easily reproduce or does it happen intermittently/randomly?

artsown · #382 Post by **artsown** » Fri 30 Nov 2018, 21:18

@666philb
So far so good using the rox_old.pet to eliminate the blank page bug
when viewing partition contents. I'll keep using 7.9.7 daily and report
here if the bug recurs (it was intermittent).

Edit: Unfortunately it didn't take long to misbehave again

Art

ITSMERSH · #383 Post by **ITSMERSH** » Fri 30 Nov 2018, 22:33

woodenshoe-wi wrote:The problem with mounting drives looks like what radky2 reported here: https://github.com/puppylinux-woof-CE/w ... -441514667

666philb wrote:i've also noticed some oddness with rox, where clicks aren't registered.
Does this happen in a way you can easily reproduce or does it happen intermittently/randomly?

I made similar experiences when trying to open a partition by drive icon on the desktop.

But I suspected it being caused by my new but very ugly cheap mouse.

On the other hand, I like the new Rox filer definitely, so it's worth to sort out and fix the bug (if it is any), to have this version of Rox filer default in next Puppies.

woodenshoe-wi · #384 Post by **woodenshoe-wi** » Fri 30 Nov 2018, 23:41

There could be two different problems being discussed here.

The problem with mounting partitions should now be, or is being fixed in woof-CE.

The problem "where clicks aren't registered" might be something I just noticed now that when using small icons there is a gap between the icon and name where clicking has no effect. I see the same problem with the rox_old.pet but the latest jun7 version doesn't seem to have the problem and does have the copy/paste functionality.

bigpup · #385 Post by **bigpup** » Sat 01 Dec 2018, 00:41

Gimp sucks for a simple graphics image editor.
Bring back Mtpaint!!

Look at what Gimp gives you for file type options to save as.....

ITSMERSH · #386 Post by **ITSMERSH** » Sat 01 Dec 2018, 01:32

woodenshoe-wi wrote:There could be two different problems being discussed here.

The problem with mounting partitions should now be, or is being fixed in woof-CE.

The problem "where clicks aren't registered" might be something I just noticed now that when using small icons there is a gap between the icon and name where clicking has no effect. I see the same problem with the rox_old.pet but the latest jun7 version doesn't seem to have the problem and does have the copy/paste functionality.

Sorry for not being clear enough.

I was talking about clicking a drive icon of a drive which is already mounted, but it didn't open a window when clicking the icon. Noticed this in 7.9.6.

bigpup · #387 Post by **bigpup** » Sat 01 Dec 2018, 01:55

666philb wrote:bigpup and LateAdopter,

i've also noticed some oddness with rox, where clicks aren't registered.
does this older rox fix it for you? (note root warning hasn't been removed)
http://distro.ibiblio.org/puppylinux/te ... ox_old.pet

Seems to have no affect on issue.

How can I tell if I am actually now using this Rox and not the original?

ITSMERSH · #388 Post by **ITSMERSH** » Sat 01 Dec 2018, 02:43

Rox right-click menu has Extended attributes and Duplicate entries e.g.

artsown · #389 Post by **artsown** » Sat 01 Dec 2018, 11:18

How can I tell if I am actually now using this Rox and not the original?

In PPM click on uninstall to see list of installed packages. I removed rox_old
and it apparently reverted back (??).

Art

666philb · #390 Post by **666philb** » Sat 01 Dec 2018, 22:28

bigpup wrote:Gimp sucks for a simple graphics image editor.
Bring back Mtpaint!!

Look at what Gimp gives you for file type options to save as.....

hi bigpup,

in gimp you use the export option

666philb · #391 Post by **666philb** » Sat 01 Dec 2018, 22:32

some good news.
I've got Bluetooth working pretty much. i can tether to my phone's internet connection, and have sound streaming to a speaker, from deadbeef, mpv and browsers.

just got to think on how to implement it... it'll probably be pretty clunky

bigpup · #392 Post by **bigpup** » Sun 02 Dec 2018, 00:26

About the problem with the desktop icons and Rox when mounting and unmounting a drive partition.

Here is an issue about it in Woof-CE on Github.
https://github.com/puppylinux-woof-CE/w ... ssues/1240
The issue is closed, so there is suppose to be a fix for this.

gyro · #393 Post by **gyro** » Mon 03 Dec 2018, 22:40

An issue.

if /usr/local/bin/defaultconnect contains the line:

Code: Select all

exec net-setup.sh

this activates a bug in the current /etc/rc.d/rc.shutdown file, and bionicpup64 might not shutdown cleanly.

if /usr/local/bin/defaultconnect contains some other line, e.g.:

Code: Select all

exec connectwizard "$@"

then the bug will not be activated.

The bug can be avoided by not setting any of the Network setup utilites as the default.
You are most likely to do this when prompted after the successful setup of a wifi connection.

if your /usr/local/bin/defaultconnect file is already activating the bug, you can safely edit it to replace the offending line with the safe line, per above.

Note1: If you are not running with a "pfix=fsckp,fsck" boot parameter, you would probably not see any evidence of the bug being activated.

Note2: I have already raised this as a woof-ce issue.

gyro

rerwin · #394 Post by **rerwin** » Tue 04 Dec 2018, 04:18

gyro,
Thank you for calling attention to the shutdown bug. I have responded in woofCE and offered a fix. The simple change anyone can make to file /etc/rc.d/rc.shutdown: replace line 139 with:

Code: Select all

/usr/local/network-wizard/rc.network stop

petihar · #395 Post by **petihar** » Tue 04 Dec 2018, 08:31

some good news.
I've got Bluetooth working pretty much

Hello 666philb
Very good news indeed

! On my side I continued the tests and investigations to make the connection with my phone and my hi fi system work without success. I must say that I proceed in a very empirical way without really understanding the why of the how, I don't have the knowledge to do that. So I can't wait to get your lighting to make this damn Bluetooth work.
Yours sincerely . petihar.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Bionicpup64 8.0 CE

Problem Starting X as non-root user BionicPup64_7.9.7

ROX-filer

Re: ROX-filer

@ 666philb - bluetooth