Porteus

Hi Donald

It is working for me, but not without changing theme before I achieved. In Mate there is no problem with Pluma.

Cheers!

Correction -->

(I've misstyped before)

Hi M.Eerie
You are using APorteus which might have a different set of packages,do you?

I'm sorry but it does not work with 4.0-xfce-64Bit

I can link the folders with a slightly modified line:
cd ~/.local/share/gtksourceview-3.0/; ln -s . ../gtksourceview2.0 (or gtksourceview-2.0)
but the result is always the same.
The mousepad binary shipped with 4.0 doesn't display the color schemes correctly.


If i install gtksourceview-2.10.5 and use the mousepad binary from 3.2.2
(which is slightly bigger in size) it works.

donald wrote: ↑

09 Jun 2018, 20:48

You are using APorteus which might have a different set of packages,do you?

No, I'm not. The screenshot came from Porteus 4 with XFCE module. Have you tried to change the theme?

Your Mousepad is getting the installed styles, but the theme is not.

Look at the screenshot again. I'm using Qogir

(In Porteus Info, the package list, shows Mousepad 0.40 and GtkSourceview 3.18)


Cheers!

--> Have you tried to change the theme? <--...Yep


The color of the text box background in mousepad still does not change
according to the selected color scheme (cobalt)

The text field background should look like this
(color scheme = cobalt)

( just to show what the cobalt color scheme normally
select as background color.)

All I can say it is working for me, but for some reason (the regression ) you have to change the theme in order to GtkSourceView take effect.

I've uploaded some logs to pastebin, should you have the time to diff'em.

LOADED MODULES
LOADED PACKAGES
BOOT DISK & cmdline
BOOT INFO

Just trying to catch the bug with someone who knows... Certainly, I've observed some strange behaviours in XFCE. And it's a shame. I have Manjaro XFCE in my production machine, but after all these years, there are some strange behaviors coming to life from time to time (some of them not even solved):

• Close session, re-starts it twice

• 1px resize

• Duplicated service daemons at session startup

etc..

It's like trying to get the Millenium Falcon into shape again and again. And it's getting bored. So, given the fact of MATE/Budgie evolution, and the waste of resources, I'm leaving the XFCE bandwagon unless all those irritating bugs got sorted out soon.

As you stated before,

donald wrote: ↑

08 Jun 2018, 08:22

I'm just a user and not a developer,
so I don't care about the size of the module.
What is the point of stripping down a module to the bone
if you have to add MB's of stuff afterwards to make it work
like it did before?

and I feel like that. With today's hardware, (even 10 years old machines) there is no need to whip yourself with the lack of options/tools. Don't get me wrong, Porteus modularity is a must. A big must. Has proved to be helpfull in most case scenarios. And I think the team effort to bring 7 desktops to life, is enormous. We are users, right, but in the end, the developer is a user too...

On the other hand, Linux is already mature, but unfortunately there are too many brilliant solutions scattered, and no one bringing all togheter. We are trapped in the middle of the Minimalism vs BeProductive guerrilla.

(BTW, everyone here knows who's the teacher and who's the apprentice)

Cheers!

Thanks for being with me trying to find out what's going on.
It was an interesting task/weekend,wasn't it?

I'm still unsure why it doesn't work as expected..lol
May be that the new version has been stripped down a bit too much,
but because a solution has been found i mark this point as being solved.
(at least for me)

My suggestion: post these bugs (and how exactly we can reproduce them) inside Porteus 4 bug topic. I'll try to log them separating the most critical ones from the cosmetics ones.

Or a separate topic for each 4.0 DE needing tweaking.

@Ed_P, the idea is good, but most users don't know how to differentiate a DE issue from a generic Porteus issue.

USM in both 32 and 64 bit v4.0, ends up showing LIBS.txt error, visit me after 6 hours. Enough has been talked about this error and repeats in the new version.

HD Videos play well in v4.0rc1(mpv), but crawls in v4.0. USM error showed off, while building vlc.

Activated vlc3.0.2 for KDE by jss, along with his qt base module. VLC plays Full HD videos smooth and without any lag.

I continue to use , v3.2.2 - 32biit and v4.0rc1 - 64 bit or the latest nemisis(neko) or the rock stable ubuntu deepin derivative.

No one will like to get his system messed up again and again,. especially with "folder locks", while using mate or cinnamon.

raja wrote: ↑

11 Jun 2018, 10:36

USM in both 32 and 64 bit v4.0, ends up showing LIBS.txt error, visit me after 6 hours. Enough has been talked about this error and repeats in the new version.

And the solution is the same one used to fix it in 3.2.2: Firefox Quantum (Post by Ed_P #62912)

fulalas wrote: ↑

11 Jun 2018, 06:35

@Ed_P, the idea is good, but most users don't know how to differentiate a DE issue from a generic Porteus issue.

True, but most users don't know how to do this either.

fulalas wrote: ↑

10 Jun 2018, 21:36

post these bugs (and how exactly we can reproduce them)

Having a single topic with multiple unrelated problems makes it hard to follow what's what. imo

@Ed_P, that's why I said I will try to log them separating the most critical ones from the cosmetics ones

@donald, the module taking less space is not an advantage for the developers. Quite the opposite! It's easy to create a fat distro like Ubuntu family. It's hard to create a distro like TinyCore, regardless of what you prefer. So having just what is needed to work means being faster and consuming less memory at the user side. You may not be interested in that, but this is one of the main focus of Porteus: being lightweight and fast Of course, the idea of being minimalist should not break things. At least that's what we've been trying, and that's why we opened a release candidate for the public so we could hear your feedback before releasing the final release -- which, of course, will contain some bugs, since this is how softwares work.

When you say there's no sense in 'changes only for the sake of change without real improvement', I totally agree. However, the world is not just our subjective opinion, so what's an improvement for you could be a regression for others, and vice-versa. Try to think through other perspectives

BTW, I'm delegating some of the issues you reported to a friend of mine. Could you please describe with detail all the issues you've found inside Porteus 4 bug topic? Thanks!

fulalas wrote: ↑

12 Jun 2018, 23:42

..we opened a release candidate for the public so we could hear your feedback before releasing the final release

Yep, and the issues have been reported but were obviously,silently ignored.

fulalas wrote: ↑

12 Jun 2018, 23:42

@donald, ...one of the main focus of Porteus: being lightweight and fast...

There is a 3rd point:
being useable / userfriendly for anyone - beginners included.

....and then we got MPV...which is not userfriendly by any means.
1) There is no UI to make/change settings - I would not expect a user
to search for and learn the syntax of how changes can be made to MPV
and to tinker with *.conf files. That's not what I would call "userfriendly"

2) MPV does not play movie DVDs because MPV can not use the libdvdcss.
even with the syntax which is supposed to work/play DVDs
mpv dvdread://[WHATEVER]
gives:
....not supported or disabled at compile time.

All of those was possible/ easy to do with what we have in 3.2.2
...improvement?, no, it's regression...

some other issues are (now) listed here:
Mission, goals and mean: working toward a better porteus (Post by donald #65087)

Solution "find files/foders" UI
open a terminal and type pfilesearch

Solution "Get / Compare md5sum"
create a thunar custom action /opt/porteus-scripts/context-menu/clipsum %f

Solution mousepad
install gtksourceview-2.10.5 and copy over the mousepad binary
shipped with 3.2.2

Regarding the icon and / or panel disaster..
To recommend to install an additional Icon theme, which pulls in thousands
of files, is no solution at all to what should have worked in the first place.

A user, me included, does not care that much for the module size but he/she
cares for what is visible on the monitor.
If it's not working (s)he may register and report, or simply (quietly)
switch to something else.

Please note that most of the problems mentioned do not occur
in porteus 3.2.2 - so where exactly is the improvement from
the user's point of view?