Page 3 of 13

Re: Porteus 3.0 final feedback

Posted: 14 Mar 2014, 09:36
by pchan
freestyler wrote:
pchan wrote:Will also appreciate if anyone can help me get a volume applet on the task panel.
I had that problem too, you need asound.conf here is the thread
Thanks. I downloaded xfcemixer using USM pakage manager and managed to get a mixer applet on my task panel.

Had to download and activate 4 files (dependencies) to get it to work.

gst-plugins-base-0.10.36-i486-2.xzm
gstreamer-0.10.36-i486-2.xzm
libvisual-0.4.0-i486-3.xzm
xfce4-mixer-4.8.0-i486-1.xzm

I am going to try your suggestion asound.conf

Without an applet on the task panel, I had to use terminal to call up alsamixer. Not so convenient.

I managed to install smplayer 0.86 using USM pakage manager.
I needed smplayer because I don't know how t get my internet browser (firefox and opera) to play youtube. Sometimes, youtube will play for a short while without sound the gives an error message. I tried flash plugin ver 11 and 10 but no luck. SMplayer did a good job playing youtube for now until someone teach me how to get internet browsers to play youtube in porteus 3.0

Re: Porteus 3.0 final feedback

Posted: 14 Mar 2014, 11:26
by brokenman
Firefox and opera use the latest linux flashplayer. Support for linux has ended (yay adobe, way to make friends!) and adobe will only issue security fixes from now on. I also get the error and ff will not play. Chrome has no problem since it uses it's own version of a flashplayer.

Re: Porteus 3.0 final feedback

Posted: 14 Mar 2014, 14:46
by francois
I am wondering if the proper place for issues with usm is in this thread, or if you would prefer the issues of usm coming with porteus 3.0 final being addressed on the usm thread:


Meanwhile, with porteus 3.0 final kde de, I get the following message when I try to run usm gui (it has been updated and repo have been synchronized) :

Code: Select all

 Cannot execute command ' /usr/bin/usmgui'
Trying to start directly with the script:

Code: Select all

root@porteus:~# cd /usr/bin/
root@porteus:/usr/bin# ./usmgui
awk: fatal: cannot open file `/etc/usm/usm.conf' for reading (No such file or directory)
/usr/bin/usm: line 61: /etc/usm/usm.conf: No such file or directory
/usr/bin/usm: line 62: /share/usm/funcelementCreate: No such file or directory
/usr/bin/usm: line 63: /share/usm/funccleanup: No such file or directory
/usr/bin/usm: line 64: /share/usm/funcsystemSetup: No such file or directory
/usr/bin/usm: line 65: /share/usm/funccli: No such file or directory
/usr/bin/usm: line 66: /share/usm/funcgtkDialogs: No such file or directory
/usr/bin/usm: line 67: /share/usm/functxtStatic: No such file or directory
/usr/bin/usm: line 68: /share/usm/funcpackageSearch: No such file or directory
/usr/bin/usm: line 69: /share/usm/funcpackageInfo: No such file or directory
/usr/bin/usm: line 70: /share/usm/funcchecks: No such file or directory
/usr/bin/usm: line 71: /share/usm/funcpackageGet: No such file or directory
/usr/bin/usm: line 72: /share/usm/funcupdateDatabase: No such file or directory
/usr/bin/usm: line 73: /share/usm/funcchangelogs: No such file or directory
/usr/bin/usm: line 74: /share/usm/funcslackbuilds: No such file or directory
/usr/bin/usm: line 75: /share/usm/funcsystemDeps: No such file or directory
/usr/bin/usm: line 97: export: package_search: not a function
/usr/bin/usm: line 98: export: package_info: not a function
/usr/bin/usm: line 99: export: package_keyword: not a function
/usr/bin/usm: line 100: export: package_get: not a function
/usr/bin/usm: line 101: export: gtk_processing: not a function
/usr/bin/usm: line 102: export: kill_processing: not a function
/usr/bin/usm: line 103: export: check_library: not a function
/usr/bin/usm: line 104: export: gtk_menu_from_variable: not a function
/usr/bin/usm: line 105: export: gtk_message: not a function
/usr/bin/usm: line 106: export: gtk_message1: not a function
/usr/bin/usm: line 107: export: gtk_message2: not a function
/usr/bin/usm: line 108: export: resolve_deps: not a function
/usr/bin/usm: line 157: system_setup: command not found
/usr/bin/usm: line 641: rbutCreate: command not found
/usr/bin/usm: line 641: rbutCreate: command not found
/usr/bin/usm: line 641: rbutCreate: command not found
/usr/bin/usm: line 641: butCreateStock: command not found
awk: fatal: cannot open file `/etc/usm/usm.conf' for reading (No such file or directory)

** (gtkdialog:9885): ERROR **: gtkdialog: Error in line 151, near token '<radiobutton>': syntax error

/usr/bin/usm: line 645:  9883 Done                    echo "$USM_MAIN"
      9884                       | sed '/^##/d'
      9885 Trace/breakpoint trap   | gtkdialog -c -s > /dev/null
/usr/bin/usm: line 647: cleanup: command not found
root@porteus:/usr/bin# 
I have a frugal install and I have changed my save folder twice yet.

Thanks. :)

Re: Porteus 3.0 final feedback

Posted: 14 Mar 2014, 15:05
by brokenman
Do you have anything in the folder /etc/usm ?

Perhaps you had the original version before I updated, and tried to automatically update. It may have removed the original but failed to correctly install the latest. If so please grab the slackware package from sourceforge and install it. Please direct any future bugs to the USM thread in bug reports.

Re: Porteus 3.0 final feedback

Posted: 15 Mar 2014, 07:29
by dustbunnies
needed smplayer because I don't know how t get my internet browser (firefox and opera) to play youtube
You can view youtube videos in firefox without installing flash by appending &html=1 to the end of any video page url

This add-on (when installed and enabled) will automagically append that for you:

"YouTube HTML5 Video" firefox addon
https://addons.mozilla.org/en-US/firefo ... src=search

I use this addon. I don't have flash installed b/c I can't think of any other site where I actually want/need flash content displayed.

The _ONLY_ caveat I've found regarding use of this addon:
it's a PITA when you're viewing a video page and you try to use the browser back button
(you're forced to click quickly, repeatedly, to overcome the forward autoredirection)
Easy workaround: click and HOLD the back button icon to expose history dropdown; choose destination from among the dropdown items

Re: Porteus 3.0 final feedback

Posted: 15 Mar 2014, 13:00
by jimwg
Good Work!

Just wish to know how does one uninstall and delete any USM (or even USM itself) downloads or libraries or modules to a "clean" pre-USM state?

Thanks!

Jim in NYC

Re: Porteus 3.0 final feedback

Posted: 15 Mar 2014, 17:20
by jimwg
I haven't been able to fully check, but I'm running XFCE from 3.0rc1 with 3.0 final base and can't run gnome mplayer; does XFCE from final 3.0 package run mplayer in 3.0 final core alright?

Also, my full 3.0 final install missed desktop icons of hard drive of the laptops that my Porteus stick is plugged into though you can see them in Thundar. I replaced XFCE from 3.0final with one from 3.0rc1 and full desktop appeared as normal.

Jim in NYC

Re: Porteus 3.0 final feedback

Posted: 15 Mar 2014, 19:14
by francois
@fanthom:
Finally, Santa really realized my wish. Thanks for slocate command included into porteus 3.0.

Overall, porteus is now a distro of choice, providing a lot of versatility. in a very small format. Modularity and usm ppm with its frugal, friendly and intuitive interface permits an infinite extension (or almost infinite) of this operating system to accomodate the user's fantasies.

Thanks to all. :D

Re: Porteus 3.0 final feedback

Posted: 15 Mar 2014, 20:55
by dustbunnies
Quoting a discussion thread from last year which grew to 6 pages, turned ugly, and got locked:
If you start porteus the first time from a FAT-fs you get a bright-yellow-message
at bootup:
"A Windows filesystem (FAT,NTFS) or other non-posix compatible filesystem has been detected on /porteus.Your changes cannot be saved directly to the specified storage media with this setup. Please use the Porteus save file manager to create a .dat container and use it for
saving your changes after your next reboot."
The devs and longtime users have lamented GEEZ, CAN IT BE ANY MORE OBVIOUS?!?

Yes, it can, and considering the recurrence of posts by stumbling new users, it needs to be somehow even MORE obvious.

First of all, many users are going to be overwhelmed during a first-time testdrive.
Bright yellow or not, any boot message (prior to xsession) is likely to be consciously dismissed
(I'll fiddle with the technical details later, first run I just wanna see if my sound works and...)
Clicking through an "I understand" prompt, displayed conditionally if no savefile.dat is found, might jog awareness
but ideally (IMO) that point should be conveyed via a window/dialog inside the session (idunno? launch geany /pathto/savefile_howto.txt)

As is, the message is linewrapped (impedes readability) and emphasizes via bolding, after your next reboot.
Broadening the emphasis for saving your changes after your next reboot would better serve as an immediate "call to action".
Ahhhhh... but this obvious, bright yellow, disclaimer is attempting to ALSO convey a separate point:
understand that your newly-created savefile isn't available/usable until you reboot

Another sticking/confusing point for the new user regarding savefile creation is:
WTF is "Porteus save file manager"? How do I find it, and once I do... whaddami s'posed to do/type/click?
Let's see: There's no desktop icon, nor rootmenu entry labeled "Porteus save file manager"...

When user eventually stumbles into finding the GUI (by clicking a tooltip-less "star" icon within control center app?)
? Am I expected to create a directory?
? Can I, should I, write to the root dir?
? Wait, whaddya mean the chosen path is inside the roofs? Aw for Pete's sake...
Seriously... the gui, the workflow, needs to be improved. Does the GUI contain an icon linking to a help document?

Empowering the user by exposing choices/flexibility is a wonderful IDEA(L)
but, in a first-run or test-drive context, consider:

-- Porteus is marketed as a Live+persistence distro

-- For nearly every other "live+persistence" distro the user has encountered,
persistence from the get-go is probably a presumed-to-be-desirable feature and has been transparently enabled, by default

-- menu offers an "Always Fresh" entry (implying 'no persistence this session') but user has NOT chosen that entry

Re: Porteus 3.0 final feedback

Posted: 15 Mar 2014, 21:37
by roadie
understand that your newly-created savefile isn't available/usable until you reboot
This is a bothering lil thing with me. Is there a way to create the save setup and then begin applying changes without a reboot?

On another note, I just built a 32bit Mate iso from the site and Engrampa is displaying the same error......running "update cache" command makes no difference.

roadie

Re: Porteus 3.0 final feedback

Posted: 15 Mar 2014, 21:38
by brokenman
Bright yellow or not, any boot message (prior to xsession) is likely to be consciously dismissed
Yes, this appears to be the case.

I can see where you are coming from here, and every point you make is valid. We need to review the way Porteus deals with having to create a savefile. Currently, many new users just aren't getting it. Having the savefile manager buried within another application certainly doesn't help the plight.

Perhaps a thread should be started to offer ideas and opinions on this.

Re: Porteus 3.0 final feedback

Posted: 15 Mar 2014, 21:52
by roadie
More on the 32bit Mate iso.
On booting it, there is a porteus-package-manager.desktop file on the root of the filesystem, size is 287
There is also a 'user' file size is 21170....seems to be involved with desktop or menu settings.

This is booting always fresh with no changes made to the system.


EDIT:...I fixed the Engrampa error by running 'glib-compile-schemas /usr/share/glib-2.0/schemas'

roadie

Re: Porteus 3.0 final feedback

Posted: 16 Mar 2014, 00:52
by donald
3.0 xfce 32bit
nvidia FX5200 + nVidia-173.14.39-porteus-v3.0-i486-1ftm.xzm
boot message:
Xorg failed to start up - removing proprietary driver(s)

root@porteus:~# modprobe nvidia
modprobe: ERROR: could not insert 'nvidia': Unknown symbol in module, or unknown parameter (see dmesg)

root@porteus:~# dmesg | grep nvidia
[ 17.507997] nvidia: module license 'NVIDIA' taints kernel.
[ 17.661753] nvidia: Unknown symbol acpi_os_wait_events_complete (err 0)
[ 26.220097] nvidia: Unknown symbol acpi_os_wait_events_complete (err 0)
[ 342.422617] nvidia: Unknown symbol acpi_os_wait_events_complete (err 0)
[ 513.979167] nvidia: Unknown symbol acpi_os_wait_events_complete (err 0)
[ 566.839744] nvidia: Unknown symbol acpi_os_wait_events_complete (err 0)
[ 794.320479] nvidia: Unknown symbol acpi_os_wait_events_complete (err 0)
[ 867.184749] nvidia: Unknown symbol acpi_os_wait_events_complete (err 0)
[ 948.391730] nvidia: Unknown symbol acpi_os_wait_events_complete (err 0)
[ 1220.899455] nvidia: Unknown symbol acpi_os_wait_events_complete (err 0)
root@porteus:~# .... :(

Re: Porteus 3.0 final feedback

Posted: 16 Mar 2014, 01:59
by francois
I just realized that slackyd does not come stock with porteus 3.0. Is it really intended?

Re: Porteus 3.0 final feedback

Posted: 16 Mar 2014, 08:19
by fanthom
I replaced XFCE from 3.0final with one from 3.0rc1 and full desktop appeared as normal.
best what you can do is to update whole box to 3.0 final without mixing components (that can bring only troubles).

Is there a way to create the save setup and then begin applying changes without a reboot?
unfortunately there is not (or at least i dont know how to remount rw aufs branch to other place)

We need to review the way Porteus deals with having to create a savefile.
i think i have heard all argumentation already but why not :)

Xorg failed to start up - removing proprietary driver(s)
please generate psinfo report and link in this thread. thanks

slackyd does not come stock with porteus 3.0. Is it really intended?
we had discussion about it and decided to drop slackyd in favor of usm. most (if not all) slackyd's functionality is already ported to usm and having one package manager is less confusing to the users.

thanks guys