Page 2 of 5

Re: Porteus Package Manager bug reports

Posted: 25 Oct 2012, 19:38
by brokenman
Thanks, i'll check it out. I have removed your duplicate post.

Re: Porteus Package Manager bug reports

Posted: 30 Nov 2012, 16:20
by francois
I did not know where to put this link. Maybe you are already far beyond the scope of the project with PPM. Anyway, I thought that it could be interesting for you brokenman, but also maybe to bigbass (it is said to be based on slapt-get), depending on how the package manager is built.

Slackpack:
http://www.linuxquestions.org/questions ... er-758501/

Citation:
"Slackpack has a friendly GUI environment and it can install
packages, list installed packages, remove Slackware Linux packages
(.tgz or .txz) and convert to .tgz format from .deb and .rpm.

Slackpack can also create Slackware Linux .tgz packages from application's source code. ... in the latest version (1.1.8) Slackpack has been ported to Qt4... "

The maintainer MysticalGroovy is leaving the project and offering it to the community:
http://www.slax.org/forum.php?action=vi ... ntID=82777

Re: Porteus Package Manager bug reports

Posted: 12 Dec 2012, 08:53
by Rava
brokenman, the GUI acts quite ugly when you run a light on dark style, like me with Nodoka-Midnight on XFCe.

The standard text colour is a very light grey (almost white) and the standard background is a very dark grey (almost black)

Now, part of your PPM define its own colours, but it also uses the system default.

This results in white background and in near white text, which cannot be read.

Like with the menus, only when i highlight an entry I can read it. But the other info on the main window with white background using my standard font colour I cannot highlight.

Which toolkit do you use? Me thinks you can define text colours in that, yes?

(I can provide screenshots if you need them, but it should be the same when you run XFCe Porteus and also choose Nodoka-Midnight)

Re: Porteus Package Manager bug reports

Posted: 12 Dec 2012, 11:48
by brokenman
Yes please provide screenshots. I only use a custom style for the splash screen and initial screen that asks you to choose a folder in which i have a custom background. All other windows should conform to your current GTK style.

Re: Porteus Package Manager bug reports

Posted: 12 Dec 2012, 14:37
by Rava
Image

I cannot provide the initial screen when PPM asks for its non union folder, but at the bottom there is also nearly white text on white background... since PPM no longer asks me that. What file do I have to delete so that PPM asks me again?


(And: Yes, the title of the current running window can hardly be read, a bug in that Nodoka-Midnight style, me thinks.)

Re: Porteus Package Manager bug reports

Posted: 14 Dec 2012, 18:33
by Ahau
I haven't tested this myself (stuck in windows atm), but one thing you might try is to empty your ~/.gtkrc-2.0 file. I recently discovered that Porteus-XFCE 1.2 inherits this file in 002-xorg.xzm from the standard edition, which messes a bit with the theme. You might have discovered that already, in which case you can ignore this post. Otherwise, try:

echo "" > ~/.gtkrc-2.0

then log out and back in to Xfce.

Re: Porteus Package Manager bug reports

Posted: 14 Dec 2012, 21:10
by Rava
@Ahau...

Could be a reason, in there is this line

Code: Select all

include "/usr/share/themes/Nodoka-Aqua/gtk-2.0/gtkrc"
and I sure am not using that theme/style.

I will give you heads up as soon as I managed to restart X... (since it does interrupt the work-flow)

Re: Porteus Package Manager bug reports

Posted: 14 Dec 2012, 21:33
by Ahau
Yes, that is the point of concern. Let us know how it looks once you get a chance to log out/in. This may not be the cause, however, as I don't know off-hand if PPM's dialog uses font colors that pull directly from the gtk theme or not.

Re: Porteus Package Manager bug reports

Posted: 15 Dec 2012, 00:54
by brokenman
Damn you're right. That is even uglier than my mirror. Your style is pulling from your default gtk for widgets but not for windows in general.

Here are the pertinent lines from PPM which is only for the splash screen.

Code: Select all

echo 'style "ppmbg"
{
  bg[NORMAL] = { 1.0, 1.0, 1.0 }
}
widget "GtkWindow" style "ppmbg"

Whatever you are using for a gtkrc (possible /root/.gtk-2.0 or .gtk-2.0-mine) you could try adding the style codeblock from above (changed to suit your colors) which will force the window background colour.

1.0, 1.0, 1.0 is white.

Re: Porteus Package Manager bug reports

Posted: 20 Dec 2012, 01:55
by Rava
brokenman wrote:Whatever you are using for a gtkrc (possible /root/.gtk-2.0 or .gtk-2.0-mine) you could try adding the style codeblock from above (changed to suit your colors) which will force the window background colour.

1.0, 1.0, 1.0 is white.
So far, so... okay, but where does PPM define the text colour? When it makes the background white, it needs to define the text colour as black.

Or not define it at all is also okay. The standard style is white BG and black text anyway.

Then a style like mine uses whatever it defines, and that is readable as well...

I tried looking up details on your above codeblock, but found nothing about "bg" in http://developer.gnome.org/gtk3/3.5/GtkWindow.html :(

//edit
I hoped ppm is a script and I could comment out the above snippet, but alas I was wrong:

Code: Select all

root@porteus:~# file /opt/porteus-scripts/porteus-package-manager
/opt/porteus-scripts/porteus-package-manager: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, corrupted section header size

Re: Porteus Package Manager bug reports

Posted: 20 Dec 2012, 18:28
by brokenman

Re: Porteus Package Manager bug reports

Posted: 11 Jan 2013, 03:30
by francois
I have tried PPM to make the libreoffice module(s). The libreoffice logo will appear but writer will not appear. As someone been able to make a functional libreoffice with PPM?

Thanks.

Re: Porteus Package Manager bug reports

Posted: 10 Feb 2013, 22:37
by Hamza
I'm having issue running Porteus Package Manager on Porteus 2.0 RC2 x86_64. I have unpacked the reset module present at /opt/ppm to root filesystem and when i'm starting a new instance of PPM, as always, i'll go make a search of a module. This time i chosen bluefish in development category. It has been found and i selected with dependency resolution activated. Everythings worked until it asks for resolution of a strange lib (can't remember name) and i accepted. It asked to confirm the download of 200Mb data related to Slackware packages database. I accepted and it frozen on "Testing repository link" status.

I'm having this issue on Porteus 2.0 x86_64 Release Candidate 2.

Here is what i'm having after some seconds. link


Thanks!

Re: Porteus Package Manager bug reports

Posted: 11 Feb 2013, 08:49
by libernux
I had this also some time ago.
I solved it by disabling ipv6 in networkmanager.
HTH.

Re: Porteus Package Manager bug reports

Posted: 11 Feb 2013, 09:31
by Hamza
Ok, I'll see with brokenman :)

Thanks.