Upgrading Salix 13.0 to 13.1

[ceeslans]

I upgraded Salix 13.0 to 13.1 using the wiki how-to page http://www.salixos.org/wiki/index.php/H ... .0_to_13.1
There are some left-over problems though:

When opening terminal and logging in as root (su), I get configuration error:

Code: Select all

cees[~]$ su
configuration error - unknown item 'DIALUPS_CHECK_ENAB' (notify administrator)
configuration error - unknown item 'NOLOGIN_STR' (notify administrator)
Password: 
root[cees]# 

I can execute commands as root - but how to get rid of the configuration error?

The application 'Cheese' - which ran just fine under 13.0 - is starting up as it should, until it shows error message:

check your gstreamer installation: one or more needed gstreamer elements are missing: gconfaudiosrc, gconfvideosink

- and then close down.
afaik these elements are part of the gst-plugins-good - and this package is obviously already installed.

[gapan]

I upgraded Salix 13.0 to 13.1 using the wiki how-to page http://www.salixos.org/wiki/index.php/H ... .0_to_13.1
There are some left-over problems though:

When opening terminal and logging in as root (su), I get configuration error:

Code: Select all

cees[~]$ su
configuration error - unknown item 'DIALUPS_CHECK_ENAB' (notify administrator)
configuration error - unknown item 'NOLOGIN_STR' (notify administrator)
Password: 
root[cees]# 

I can execute commands as root - but how to get rid of the configuration error?

You have to run dotnew, to accept/reject new configuration files. Be careful not to touch system files like /etc/shadow, /etc/passwd and /etc/group. One of the updated files fixes that, don't remember which one right now.

The application 'Cheese' - which ran just fine under 13.0 - is starting up as it should, until it shows error message:

check your gstreamer installation: one or more needed gstreamer elements are missing: gconfaudiosrc, gconfvideosink

- and then close down.
afaik these elements are part of the gst-plugins-good - and this package is obviously already installed.

This has been reported before but noone provided additional information when I asked for it. Do you have all gstreamer plugins + libs installed? Run salix-codecs-installer and try again. It might need a rebuild.

[ceeslans]

dotnew did the trick. the config error in terminal is gone. thanks!

as for the missing gstreamer elements: yes, i have all gstreamer plug-ins and libraries installed.
have re-run salix-codecs-installer and re-installed 'cheese' - but to no avail.
also audacious-crossfade plugin doesnt seem to like 13.1 - 'audacious' refuse to start up with this plugin enabled. could it also be related to missing gstreamer elements?

[gapan]

OK, that was really helpful. The problem with cheese should be fixed with the new gst-plugins-good package in the repositories.

I have removed the audacious-crossfade plugin from the repositories, audacious apparently has built-in support for crossfade in the latest version and the plugin is not needed/used anymore.

[ceeslans]

with the updated gst-plugins-good package, the application start up - but dies after about 5 seconds.
ran it again from terminal and got following error messages:

Code: Select all

root[cees]# cheese

** (cheese:4590): WARNING **: Unable to connect to dbus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

** (cheese:4590): CRITICAL **: dbus_g_connection_register_g_object: assertion `connection != NULL' failed

** (cheese:4590): CRITICAL **: dbus_g_proxy_new_for_name: assertion `connection != NULL' failed

** (cheese:4590): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
Segmentation fault
root[cees]#

@gapan: maybe this is helpful to you?

[gapan]

Don't run as root!!!

[ceeslans]

did fresh install 13.1RC1.
Cheese still dying out on me. this is terminal error message:

Code: Select all

cees[~]$ cheese
The program 'cheese' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadIDChoice (invalid resource ID chosen for this connection)'.
  (Details: serial 1303 error_code 14 request_code 1 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
cees[~]$ cheese --sync
The program 'cheese' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadIDChoice (invalid resource ID chosen for this connection)'.
  (Details: serial 2503 error_code 14 request_code 1 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
cheese: xcb_io.c:249: process_responses: Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' failed.
Aborted
cees[~]$ 

[gapan]

What graphics card do you have and what drivers are you using?

[ceeslans]

ehhh... how to read these details

[Shador]

The easiest way is probably to install LSHW and to search your graphics card in that tool.
It will include information about the device built into your system as well as the driver currently in use.