LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Puppy (http://www.linuxquestions.org/questions/puppy-71/)
-   -   Paket Manager do not work (http://www.linuxquestions.org/questions/puppy-71/paket-manager-do-not-work-915606/)

gundul3l3k 11-26-2011 04:03 AM

Paket Manager do not work
 
I just installed puppy slaco 5.3 and added some paket . I do not know what happend today i can not found my paket manager .somebody would helpme please

Karl Godt 11-26-2011 08:10 AM

Quote:

Originally Posted by gundul3l3k (Post 4534240)
I just installed puppy slaco 5.3 and added some paket . I do not know what happend today i can not found my paket manager .somebody would helpme please

When you have troubles it is worth to have a look into /tmp/xerrs.log .
To that file the standard error gets directed by the xwin script .

It is always good to know the application command line name .
This could be fetched by looking into the top command
OR
by opening the .desktop file for the app in /usr/share/applications .

The cli name for the Puppy Package Manager is " ppm " .
Code:

file `which ppm`
tells me
/usr/local/bin/ppm: symbolic link to `../petget/pkg_chooser.sh'

gundul3l3k 11-26-2011 08:31 AM

this is my xerror log file ,still do not understand any scpiting ,I just migrate my windows to puppy full installed.thanks,Should I post my ppm? its contain scrpts.need sugestion

"X.Org X Server 1.9.5
Release Date: 2011-03-17
X Protocol Version 11, Revision 0
Build Operating System: Slackware 13.37 Slackware Linux Project
Current Operating System: Linux puppypc23555 2.6.37.6 #1 SMP Sun Jul 10 08:27:28 EST 2011 i686
Kernel command line: root=/dev/sda1 ro
Build Date: 18 March 2011 12:08:03AM

Current version of pixman: 0.20.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Nov 26 22:02:06 2011
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/swrast_dri.so failed (/usr/lib/xorg/modules/dri/swrast_dri.so: cannot open shared object file: No such file or directory)
(EE) GLX: could not load software renderer
/usr/bin/jwm
/usr/sbin/delayedrun: line 239: 3212 Segmentation fault $a
/usr/sbin/pupdial_init_hotpluggable: line 272: 3617 Terminated yaf-splash -bg orange -placement center -close never -fontsize large -text "Please wait, probing for hotpluggable (external) modems..."
/usr/sbin/pupdial: line 615: 3989 Terminated /usr/X11R7/bin/yaf-splash -font "8x16" -outline 0 -margin 4 -bg orange -text "Reading modem configuration file..."

** ERROR **: gtkdialog: Error in line 30, near token '</vbox>': syntax error

aborting...
/usr/sbin/pupdial_init_hotpluggable: line 272: 6150 Terminated yaf-splash -bg orange -placement center -close never -fontsize large -text "Please wait, probing for hotpluggable (external) modems..."
/usr/sbin/pupdial: line 615: 6520 Terminated /usr/X11R7/bin/yaf-splash -font "8x16" -outline 0 -margin 4 -bg orange -text "Reading modem configuration file..."
GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
Failed to allocate XImage

(<unknown>:7102): Gtk-CRITICAL **: IA__gtk_widget_set_colormap: assertion `GDK_IS_COLORMAP (colormap)' failed
PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms


(ROX-Filer:3130): Gtk-CRITICAL **: IA__gtk_widget_set_colormap: assertion `GDK_IS_COLORMAP (colormap)' failed

(ROX-Filer:3130): Gtk-CRITICAL **: IA__gtk_widget_set_colormap: assertion `GDK_IS_COLORMAP (colormap)' failed
PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms


(ROX-Filer:3130): Gtk-CRITICAL **: IA__gtk_widget_set_colormap: assertion `GDK_IS_COLORMAP (colormap)' failed
PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms


(ROX-Filer:3130): Gtk-CRITICAL **: IA__gtk_widget_set_colormap: assertion `GDK_IS_COLORMAP (colormap)' failed
PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

PING 64.233.169.103 (64.233.169.103) 56(84) bytes of data.

--- 64.233.169.103 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms


(leafpad:18691): Gtk-CRITICAL **: IA__gtk_widget_set_colormap: assertion `GDK_IS_COLORMAP (colormap)' failed "

Karl Godt 11-26-2011 11:24 AM

There are many icons on the puppy desktop and one in the top row near the middle of the desktop is named " console " .
Clicking that should bring the cli == Command Line Interface .
Typing " ppm " and [Enter] should start the puppy package mnanger also .
The stderr should be shown in the console now .
What we mainly need is the stderr while running ppm , not the output or errors of other apps .
You might also start the copied output with a
Code:

tag and end it with
[/code] --The '#' icon in the "go advanced" interface does this .

gundul3l3k 11-27-2011 07:09 AM

I write in console 'ppm' and the out put is error gtkdialog error line 10 .neartoken '</*/vbox>' syntax error aborting

Karl Godt 11-27-2011 08:25 AM

YEP , there had been some changes in petget , probably see here :
http://bkhome.org/blog/?viewDetailed=02092

I am running a Puppy-511 atm and this does not include the changes .

Might be a bug due not checking if a variable is empty .

Looked into slacko.sfs and the gtkdialog part is completely rewritten .
While old the whole gtkdialog is in the script , now slacko seems to source the MAIN_DIALOG from
Code:

#110118 alternate User Interfaces...
touch /var/local/petget/ui_choice
UI="`cat /var/local/petget/ui_choice`"
[ "$UI" = "" ] && UI="Ziggy"
. /usr/local/petget/ui_${UI}

There is also a ui_Classic ...
So a solution might be to drop /var/local/petget/ui_choice :
Code:

#110118 alternate User Interfaces...
#touch /var/local/petget/ui_choice
#UI="`cat /var/local/petget/ui_choice`"
#[ "$UI" = "" ] && UI="Ziggy"
UI='Classic'
. /usr/local/petget/ui_${UI}

to be changed at the very end of /usr/local/petget/pkg_chooser.sh .

Bugs are likely in Puppy but very few and difficult to spot .

Another suggestion would be to post in the http://puppylinux.info/forum.php?id=4 slacko section there .
It is not a ^bug^ regarding slacko but of woof , the base slacko had been built from .
The ^bug^ might be simply not to check for user-failures OR user-adjustments to files/configs .

On the long run a Puppy user has to be comfortable with shell scripts and the CLI .:banghead::confused::study::hattip::)

darkcity 11-27-2011 08:29 AM

Is everything else working okay?

Also did you do Full or Frugal install?

gundul3l3k 11-27-2011 09:08 AM

@ Darkcity ...I do full installed .there is one more problem gedit does not appear too ,but its ok I have a leafpad.else is no problem.

@Karl Godt thanks for the code ..sorry my bad English I am from Surabaya,Indonesia and I dont have any knowledge of scripting espcialy unix..Thanks

I fond of linux (puppy) small but powerfull

gundul3l3k 11-27-2011 09:56 AM

I have changed /usr/local/petget/pkg_chooser.sh . with that scripts but nothing happened ,fliping only and gone.


All times are GMT -5. The time now is 11:06 AM.