Differences between version 36 and predecessor to the previous major change of ApplicationErrorMessages.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 36 | Last edited on Tuesday, July 26, 2005 10:26:55 am | by JohnMcPherson | Revert |
| Older page: | version 35 | Last edited on Tuesday, May 10, 2005 1:27:11 am | by PedroDuran | Revert |
@@ -13,102 +13,23 @@
!!! GNOME 2.x - various sound applications/GStreamer
GStreamer-ERROR **: No default scheduler name - do you have a registry ?
aborting...
-
-Gnome 2 has moved to using the gstreamer suite for audio processing, including recording and playback. I got the above error message when trying to use gnome-sound-recorder. What happened (possibly debian specific) was that gnome-media depends on libgstreamer but not all the required gstreamer packages got installed. The extra packages I installed were:
- gstreamer-core
- gstreamer-tools
- gstreamer-oss (you might prefer gstreamer-alsa
or gstreamer-arts)
- gstreamer-runtime
-to get it not to crash, and some extra packages to actually get stuff working:
- gstreamer-misc
- gstreamer-plugin-libs
-
-Note - this was for the gnome2.2 back port for [Debian] 3.0 Woody. Other versions/distributions probably have different dependencies/package names.
-
-This happened again (much later) while running Debian Testing. The answer is to
-run the command "gst-register" or "gst-register-.6" or "gst-register-.8", although this should be done
-on package installation.
-
-
-Having upgraded my GStreamer installation (to .8.1), I got the following error message with every Gnome-based sound program:
-
+or
Failed to create the player: Couldn't initialize scheduler.
Did you run gst-register?
-Running gst-register as suggested this happened:
-<pre>
-Added plugin adder with 1 feature.
-Added plugin videobalance with 1 feature.
-Added plugin riff with 0 features.
-/usr/bin/gst-register-.8: relocation error: /usr/lib/
gstreamer-.8/libgstvorbis.so: undefined symbol: gst_tag_register_musicbrainz_tags
-</pre>
-Turns out that the error lies with this version of GStreamer. Upgrading to .8.8 gets rid of it
, but one must also upgrade libshout3 to ensure that it works. This is all running Ubuntu Hoary Hedgehog pre-relrease, but it affects other Debian-based distros with Gnome (
and Gnome generally, I suspect)
.
--- ''This sounds more like a distro packaging error rather than any error with gstreamer'' -- JohnMcPherson
+Gnome 2 has moved to using the
gstreamer suite for audio processing
, including recording
and playback
.
-** May 9 2005. On Ubuntu 5..4. Hoary I got the same error message (after I had been using Rythmbox for a couple of days) after I installed the windows codecs from the gstreamer0.8-mad package.
The solution was
to run gst-register-.8 with my non-root
user and it played my .mp3 files again
.
+The answer is
to run the command "
gst-register-.8" as your normal
user.
!!! tar(1)
tar: Failed open to read on /dev/nrst0 <No such file or directory>
You're using a BSD-derived tar, but using GNU-tar options - it got confused and is trying to use the default tape drive device. See PortableProgramming for tar option discussion.
-!!! Galeon
-
- Cannot find a schema for galeon preferences. Check your gconf setup, look at galeon FAQ for more info
-
-If you get this message in a dialog when starting galeon, the problem is the interaction between galeon and gconf2. If I manually start gconf1 before starting galeon (try "gconfd-1 &" from the command line) then galeon starts fine. (If you add that command to the /usr/bin/galeon script then it should all work fine all the time).
-
-(This happened after upgrading the gconf in debian testing as part of the move to [GNOME] version 2.4.) Note that galeon (gtk1 version) is pretty obsolete now. The only reason I was still using it was because there was no [GTK]2 browser for GNOME in debian testing. Now, at least, epiphany-browser is there, and the galeon from unstable can also be installed if you also grab a few extra libraries from unstable.
-
-!!! gdm(8)
-
- There already appears to be an X server running on display :0. Should I try another display number?
-
-gdm prints this out after trying to start more than one [XServer] on :0. (It also prints "Display :0 is busy. There is another X server running already" into the syslog). I got this after upgrading gdm to version 2.4.something in debian testing. This message persisted, even after the laptop was rebooted. I eventually got rid of it - however I'm not entirely sure which of the following fixed it:
-
-* I upgraded the __libgtk2.0-0__, __libgtk2.0-common__ and __libbonobo2__ packages.
-* After killing gdm and all X servers, I started "gdm" manually from the command line and then killed it.
-
-After doing these two steps, gdm behaved properly when started from /etc/init.d/gdm. If you determine how to fix it, please edit this page!
-
-__2004-05-14 9:43 EST__ The correct way to deal with this problem is:
-* Enable "debug" in your /etc/gdm/gdm.conf file under:
- ~[debug]
-
-!# This will enable debugging into the syslog, usually not neccessary and it creates a LOT of spew of random stuff to the syslog. However it can be useful in determining when something is going very wrong.
-
- Enable=true
-
-Then your messages will be logged to /var/log/syslog.
-
-* GDM has to always restart X with an entry like the following in gdm.conf:
- ~[daemon]
- ~AlwaysRestartServer=true
-
-* and finally, make sure that you have the following under the same daemon section:
-!# Automatic VT allocation. Right now only works on Linux. This way we force X to use specific vts. turn VTAllocation to false if this is causing problems.
-
- FirstVT=7
- VTAllocation=false
-
-!# Should double login be treated with a warning (and possibility to change vts on linux systems for console logins)
-
- ~DoubleLoginWarning=false
-
-That should be enough to at least know what the source of the problem is. Please note that the latest Debian gdm as of this writing, has issues with [UDev]. So if you have udev generating __/dev/vc*__ block files for you (and removing them when you close X), gdm can't get a hold on running X servers and it let's them running, trying to launch another one in a different vts!
-Therefore, you will have a few servers running in vt6, vt7, vt8, ..., vtN. The way to "kill them" without having to login in a console (vty1) is to "__CTRL+ALT+FN__", where N is the number of the vt. Say, for vt8: __CTRL+ALT+F8__. Once you are there, if you see an X server running (you will be able to move the mouse, but no other application might be running), hit __CTRL+ALT+BACKSPACE__ to kill it. Do the same with the others you may find.
-
-Hopefully somebody else might be able to write a better solution for this ;-). Or I'll come back once I find a more concrete answer.
-If you are the kind who avoids typing, you might want to make a copy of the __factory-gdm.conf__ file, found under __/etc/gdm__.
-
-!!!Evolution can't open ".DOC" files
-
-Even though [OpenOffice.org] was installed, [Evolution] only offered "Save As..." in the menu for .DOC file attachments.
-This is because the gnome2.8 mime system uses the mime type "application/vnd.ms-word" for .doc files, but for email the mime type is specified with the attachment and Microsoft products use the mime type "application/msword". The solution (for me at least) is to edit openoffice's /usr/share/applications/ooo645writer.desktop file and add "<tt>application/msword</tt>" to the list of types under "~MimeType".
!!![find(1)]
find: paths must precede expression%%%
