BionicPup32 (UPupBB) (27 June 2020)

[peebee]

03-aug-2019

iso md5 = 7cf3b9b9813ba4261553c3a673ed663c bionicpup32-8.0+11-uefi.iso

see post #1

Update to Ubuntu Bionic Beaver 18.04.3

devx also updated

[B.K. Johnson]

@peebee
I posted here about a problem with Recently Used (RU) in upupbb. A few weeks later you PMd that you didn't understand the problem, After exchanging several PMs, the tentative conclusion was that the problem must have been seen in an earlier version of upupbb, for I no longer had the problem. The version of upupbb (unknown plus number) I am now using correctly displays the filelist to the right, consistent with the arrow direction. Also, as I am now able to see pathnames of up to 109 characters, with space for more, the issue of long pathname seems moot.
So, at the end of the PM exchanges.

RU, when run from current offerings of upupbb, seems to display the filelist correctly - i.e. from menu right, and large display panel.
Long pathnames (up to 130 characters) can be accommodated.

Later: HOLD YOUR HORSES! See UPDATE below.

Related rant
It is unfortunate that a script offered in the public forum ended up modified in a distribution without acknowledgement, or discussion in the thread. It would have been nice for the script author and community to have had the opportunity to discuss and test during the 3 years since originally posted. peebee, there is discussion taking place in two threads now. Please join.

http://murga-linux.com/puppy/viewtopic. ... 40#1033240
http://www.murga-linux.com/puppy/viewtopic.php?t=95679

UPDATE
Recently Used (RU) is not working correctly anymore for me. I suspect it is conflicting with an unknown application I am using. Or an unknown operation I am doing. After our PM exchange, I would periodically bring up RU. I noticed that I was opening .html files but they were not added to RU's filelist. However, when a composer created file was saved, it was added. So I started to wonder "what does used mean". Then, without warning, when I switched to RU on one occasion, the display had reverted to hanging the list from the left. The display was never righted in a session, so I took the precaution to shut down without saving each session. The correct display returned after re booting every-time. I did this several times but then, just once I forgot to check the status before shutdown and saved my session. Now RU is permanently in bad mode. I haven't been able to have a good RU since. I replaced the pupsave with my last pupsave backup, but unfortunately it also has the bad RU. The backup prior to the last does not include many changes I do not remember or want to repeat.

@peebee, Is there a quick easy way to resuscitate RU to its former self?
TIA

[peebee]

Recently Used Documents in the Places menu comes from rootfs-packages - jwm-config - in Woof-CE and I make no changes to what Woof-CE provides.

However, BionicPup32 uses a previous version of Woof-CE from 22 March (although I cannot see any changes relating to RUD between the BionicPup32 version and the current version) ....
BUILD_FROM_WOOF='testing;c1a16e15;2019-03-22 12:34:12 +0800'

See:
https://github.com/puppylinux-woof-CE/w ... ly+used%22

If you want to turn off RUD amend line #8 of
/usr/local/jwm_config/menu_build_recent_docs
to 0 (zero)

https://github.com/puppylinux-woof-CE/w ... ecent_docs

shows the Woof-CE code - you will see it was last modified by zigbert on 27/sept/16

[B.K. Johnson]

Thanks peebee. We now have something we can dig into.

[B.K. Johnson]

Following up on posts here and here and your's here

To summarize the findings re Most Recently in the original thread

1. At my suggestion, Mochi has dropped the path. Only the file names now appear in his file-list.
2. Normally the display panel and pathnames (upupbb) or filenames (MM's MRUD) are displayed on the right (consistent with little black arrow).
3. When the length of a pathname or filename exceeds the panel width, the display shifts to the left.
4. The placement and immobility of the Places menu in upupbb prevents a normal display from ever re-appearing once shifted. With MRUD, repositioning the cursor on the desktop fixes the problem in most instances.
5. In RU, a pathname remains on the list after it has been renamed or moved. It is therefore possible that clicking on a moved pathname takes you to an empty directory. With MRUD, deleting or renaming a file on the list effectively removes it. This enables the user to easily remove a file that causes the display to stick on the left.
6. If one wants to continue to use RU, setting the number of items to zero as you suggested here is not practical. One has to start over if MochiMoppel's recommendation to delete recently-used.xbel file or s243a's to delete the folder in which it resides. It is not elegant but quite easy to manually remove the errant entry in the xbel file.

Perhaps you can encourage Zigbert to modify the Woof-CE in light of these developments.

[jamespoo]

in using Ubuntu Bionic 32-bit BionicPup32 8.0

where can i get wine as puppy palace manager is confusing i don't know what to download

thanks

[bigpup]

Make sure you download and install a 32bit version of Wine.

For Wine.

Make sure you have the latest version of Wine.
Good place to get Wine for Puppy.
http://murga-linux.com/puppy/viewtopic.php?t=88711
Read the first post carefully.
It is a lot of info.

Also, look on the first post of the Wine topic for a added 'wine_extras-v2.1.pet' that puts Wine entries in the menu.

When you get Wine installed and the Wine menu entries.
Run Wine config to setup Wine.
It will probably offer you a few more programs needed for Wine to run properly.
Should download and install them as part of the initial config.

Also, in Wine config->Drivers Select autodetect to get all the driver locations loaded in Wine.

A lot of settup options in Wine config, so check them all.

What version of Windows you want Wine to mimic can affect how a program runs. Wine Config->Applications.

About specific programs running in Wine.
Go to the Wine web site and see what it says about a specific program and issues.
http://www.winehq.org

Using Wine is almost like learning a new operating system.
Takes a while to learn how to use Wine and to get things working properly.

[jamespoo]

thanks

[jamespoo]

on http://version2013.yolasite.com/page1.php how do i know what version of wine is 32bit

[Mike Walsh]

@ jamespoo:-

As stated many times on this Forum - in umpteen different places - the more information you are able to give us, the better we can advise you....

WINE's a bit of a 'moving target', y'see. Generally, the best advice is to always use the newest available version; WINE is improving all the time, with extra support for more & more stuff. However; older versions of specific apps/programs may run better under an older WINE environment.....just like they sometimes run better in older versions of Windows.

So; if you can give us a rough idea of what you'd like to use it for, that'd be great. 10 to 1 somebody here on the Forums has probably already tried the particular app you want to run, and can confirm (or otherwise) how well it'll work.

---------------------------

Under normal circumstances I would say to use the newest version - you'll be looking at a 4-series build of WINE.....and if you're running Bionicpup, I would advise the v3 build, since this will have been compiled to take advantage of newer system components.

Let us have the requested info, though, and we'll see what's what.


Mike.

[jamespoo]

@ jamespoo:-

As stated many times on this Forum - in umpteen different places - the more information you are able to give us, the better we can advise you....

WINE's a bit of a 'moving target', y'see. Generally, the best advice is to always use the newest available version; WINE is improving all the time, with extra support for more & more stuff. However; older versions of specific apps/programs may run better under an older WINE environment.....just like they sometimes run better in older versions of Windows.

So; if you can give us a rough idea of what you'd like to use it for, that'd be great. 10 to 1 somebody here on the Forums has probably already tried the particular app you want to run, and can confirm (or otherwise) how well it'll work.

---------------------------

Under normal circumstances I would say to use the newest version - you'll be looking at a 4-series build of WINE.....and if you're running Bionicpup, I would advise the v3 build, since this will have been compiled to take advantage of newer system components.

Let us have the requested info, though, and we'll see what's what.


Mike.

well ive run wine in ubuntu on an old gen1 i3 laptop i used to have to play old pc games from 90's to like 2006 they ran fine im running puppy on old netbook wanting to play old games like halo half life ect

[bigpup]

The topic layout is a little confusing.

Just look on the first post here:
http://murga-linux.com/puppy/viewtopic.php?t=88711
About halfway down in the first post.

stable (32-bit):

1.2 | 1.2.1 | 1.2.2 | 1.2.3
1.4 | 1.4.1
1.6 | 1.6.1 | 1.6.2
1.8 | 1.8.1 | 1.8.2 | 1.8.3 | 1.8.4 | 1.8.5
2.0 | 2.0.1 | 2.0.2 | 2.0.3 | 2.0.4
3.0 | 3.0.1 | 3.0.2 | 3.0.3 | 3.0.4
4.0 |

These are the 32bit stable versions.
Each one of these numbers is a link to a pet package for that Wine version.

Example 4.0:
http://murga-linux.com/puppy/viewtopic. ... 32#1016832

Use the pet that was made for Tahrpup 6.0.5

Click on the [wine-4.0 mirrors] to actually go where the pet can be downloaded.

[pupper]

Has anyone been able to use video communications of any kind?

I have a rather quirky webcam but it works with camorama and both lsusb and /var/log/messages look ok but I have never been able to make it work in chromium or the official firefox esr build.

Tried many different flavours of firefox .pets and palemoon with no luck...

Am I missing a webrtc lib or something?

[Mike Walsh]

Hallo, pupper. And to the 'kennels'.

Now, then; video communications, huh? You mean, like, Skype.....that kind of thing?

Let's see. When you say a rather 'quirky' webcam, what exactly are we looking at here? Ideally, to work in Puppy - in fact, most Linux distros, come to that - the webcam really should be UVC-compliant (USB Video Class). If it is, then it should just work, period, since the UVC driver has been in the kernel for several years.

Would you do the following for me, please? Open a terminal, and issue the following command:-

Code: Select all

lsusb

.....followed by hitting 'Enter'. This will list all USB devices attached to the system. (Don't worry if yours is an 'internal' one, built-in to a laptop; most of these are internally connected to the USB bus anyway.) If you could then paste the output into your next post, that'd be great. It's the device ID I'm interested in, y'see. This can then be cross-referenced against a known list of UVC-compliant cams; if we get a match, great; if not, well, we know we have some more work to do....

(Quick intro to copy/paste in Puppy. To copy, simply highlight the relevant text. Don't click anything yet! To paste into your post, once you're in the right place to enter the terminal stuff, simply middle-click the mouse - click the scroll-wheel. This will paste your text into your post.)

Over to you....

[Edit:-] Give the following web-site a visit; try the test, report back what happens, please?

https://www.onlinemictest.com/webcam-test/

[Edit 2 :-] Download this wee app, and see if it recognises your webcam. It's a tiny, completely self-contained webcam viewer that'll work in just about any Pup:-

http://www.murga-linux.com/puppy/viewtopic.php?t=112299

Download it from the attachment. Install it, then click on Menu->Multimedia->VideoView. Accept the disclaimer; click on 'Open' - (are you seeing /dev/video0 in the drop-down box? If necessary, try the 'Detect' button.) If yes, then the window will expand; select the resolution you want, followed by 'Start preview'. Anything?


Mike.

[pupper]

Hello Mike thanks for the input!

Yes I'm looking to either use the web version of skype or any other video conferencing app.

Unfortunately VideoView was not able to detect my camera, for now the only application that works is an ubuntu build of Camorama.

I also did the online test, followed the instructions, firefox actually lists my camera as "USB camera" but when I click "Allow" the website says "Camera not authorized. Please check your media permissions settings." I also did a quick test with omegle.com and same thing happened.

I checked lsusb and got this

Code: Select all

Bus 001 Device 004: ID 0c45:60b0 Microdia Genius VideoCam Look

And also the kernel messages were not looking as good

Code: Select all

Sep 11 15:32:40 puppypc13717 kern.info kernel: usb 1-1.2: new full-speed USB device number 4 using ehci-pci
Sep 11 15:32:40 puppypc13717 kern.info kernel: gspca_main: sonixb-2.14.0 probing 0c45:60b0
Sep 11 15:32:40 puppypc13717 kern.info kernel: input: sonixb as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/input/input13
Sep 11 15:32:40 puppypc13717 daemon.err kernel: (spaw[13564]: failed to execute '/etc/udev/mtp-probe' '/etc/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2 1 4': No such file or directory
Sep 11 15:32:40 puppypc13717 daemon.warn kernel: udevd[13569]: Process '/usr/local/simple_network_setup/build_udevmodulelist' failed with exit code 1.
Sep 11 15:32:40 puppypc13717 daemon.warn kernel: udevd[13568]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 2' failed with exit code 99.

No idea what to do from here.

[perdido]

And also the kernel messages were not looking as good

Code: Select all

Sep 11 15:32:40 puppypc13717 kern.info kernel: usb 1-1.2: new full-speed USB device number 4 using ehci-pci
Sep 11 15:32:40 puppypc13717 kern.info kernel: gspca_main: sonixb-2.14.0 probing 0c45:60b0
Sep 11 15:32:40 puppypc13717 kern.info kernel: input: sonixb as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/input/input13
[b]Sep 11 15:32:40 puppypc13717 daemon.err kernel: (spaw[13564]: failed to execute '/etc/udev/mtp-probe' '/etc/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2 1 4': No such file or directory[/b]
Sep 11 15:32:40 puppypc13717 daemon.warn kernel: udevd[13569]: Process '/usr/local/simple_network_setup/build_udevmodulelist' failed with exit code 1.
Sep 11 15:32:40 puppypc13717 daemon.warn kernel: udevd[13568]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 2' failed with exit code 99.

No idea what to do from here.

Code: Select all

Sep 11 15:32:40 puppypc13717 daemon.err kernel: (spaw[13564]: failed to execute '/etc/udev/mtp-probe' '/etc/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2 1 4': No such file or directory

Maybe a hint about missing libs here

.

[peebee]

15-sep-2019

iso md5 = 6637fd6c4fd25bac314cb1a4ab4f4c40 bionicpup32-8.0+12-uefi.iso

see post #1

Ubuntu updates....

[pupper]

And also the kernel messages were not looking as good

Code: Select all

Sep 11 15:32:40 puppypc13717 kern.info kernel: usb 1-1.2: new full-speed USB device number 4 using ehci-pci
Sep 11 15:32:40 puppypc13717 kern.info kernel: gspca_main: sonixb-2.14.0 probing 0c45:60b0
Sep 11 15:32:40 puppypc13717 kern.info kernel: input: sonixb as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/input/input13
[b]Sep 11 15:32:40 puppypc13717 daemon.err kernel: (spaw[13564]: failed to execute '/etc/udev/mtp-probe' '/etc/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2 1 4': No such file or directory[/b]
Sep 11 15:32:40 puppypc13717 daemon.warn kernel: udevd[13569]: Process '/usr/local/simple_network_setup/build_udevmodulelist' failed with exit code 1.
Sep 11 15:32:40 puppypc13717 daemon.warn kernel: udevd[13568]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 2' failed with exit code 99.

No idea what to do from here.

Code: Select all

Sep 11 15:32:40 puppypc13717 daemon.err kernel: (spaw[13564]: failed to execute '/etc/udev/mtp-probe' '/etc/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2 1 4': No such file or directory

Maybe a hint about missing libs here

.

Thanks for the input, I tried that as well but it is still not working, maybe this issue is not exclusive to upupbb so I will try to ask to browser developers.

[john4gaming]

Who is the root password?

[bigpup]

Why are you asking?
A normal boot, you the user are already root user.
That is how Puppy normally runs.
One single user, root.