[opensuse] multimedia repository chaos
I spent a miserable few hours over the weekend trying to get an 11.2 box play multimedia. After I realized why I couldn't play anything I discovered http://opensuse-community.org/Restricted_formats/11.2 and clicked on the "codecs-gnome.ymp" link. After that some things started working but others didn't, so I looked at the troubleshooting section. I removed totem with no problem but when I asked it to remove gstreamer it removed lots of things including openoffice and evolution for example before I aborted it. I reenabled the other repositories and appear to have successfully reinstalled the things it deleted but of course my multimedia still doesn't work. When I have just packman and libdvdcss enabled, I can see that there are upgrades available for gstreamer but when I try to apply them, many won't because of broken dependencies on packages that I guess are in the standard repositories. But if I reenable the standard repositories, it no longer offers me the upgrades. Is there some way to tell YaST to do the upgrades? Thanks, Dave PS I wanted to add a note to the troubleshooting section of http://opensuse-community.org/Restricted_formats/11.2 warning about the possibility of damaging your system by following those instructions. But apparently I can't do that without creating yet another online persona - my novell persona soesn't seem to be good enough for example. Is there some way around that? I'm no longer willing to create new identities for every website I visit. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
When I have just packman and libdvdcss enabled, I can see that there are upgrades available for gstreamer but when I try to apply them, many won't because of broken dependencies on packages that I guess are in the standard repositories. But if I reenable the standard repositories, it no longer offers me the upgrades. Is there some way to tell YaST to do the upgrades?
It is important to have the entire gstreamer framework from packman. For libdvdcss, use the vlc repo and after it is installed, disable vlc. It's likely packman's gstreamer is newer than OSS. In YaST Software Management search on gstreamer, right click in the list, click All In List/Update if newer version available. Or, in YaST Software Repositories, assign a priority of 100 to packman, then again try Update if newer version available or Update unconditionally (veryify under the Installation Summarythat the updates are coming from Packman). Or, in Software Management, click on the Repositories tab, on the left select the Packman repo, then at the top of the list click on "Switch system packages to the versions in this repository." You may want to try this method first, as it is likely that the packages you have from Packman are either not in OSS or are preferred over those in OSS. You will also need the w32codec-all and xine/libxine1 packages from Packman. Flash (flash-player) and java (java-1_6_0_sun) come from Non-OSS (actually, more recently from the Update repo). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, Oct 04, 2010 at 01:15:48PM -0400, dwgallien wrote:
[...] Or, in YaST Software Repositories, assign a priority of 100 to packman, then again try Update if newer version available or Update unconditionally (veryify under the Installation Summarythat the updates are coming from Packman). [...]
Note that lower number means higher priority, the default priority is 99... Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/4/2010 10:15 AM, dwgallien wrote:
When I have just packman and libdvdcss enabled, I can see that there are upgrades available for gstreamer but when I try to apply them, many won't because of broken dependencies on packages that I guess are in the standard repositories. But if I reenable the standard repositories, it no longer offers me the upgrades. Is there some way to tell YaST to do the upgrades?
It is important to have the entire gstreamer framework from packman. For libdvdcss, use the vlc repo and after it is installed, disable vlc.
Its not necessary to disable VLC as I use their (beta) version which seems to be weeks ahead of pacman. -- _____________________________________ At one time I had a Real Sig. Its been downsized. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/4/2010 10:15 AM, dwgallien wrote:
When I have just packman and libdvdcss enabled, I can see that there are upgrades available for gstreamer but when I try to apply them, many won't because of broken dependencies on packages that I guess are in the standard repositories. But if I reenable the standard repositories, it no longer offers me the upgrades. Is there some way to tell YaST to do the upgrades?
It is important to have the entire gstreamer framework from packman. For libdvdcss, use the vlc repo and after it is installed, disable vlc.
Its not necessary to disable VLC as I use their (beta) version which seems to be weeks ahead of pacman.
I've used the vlc in both the vlc and packman repo's, which have worked fine. However, the long-standing advice on the Forums is to use the packman version, IIRC due to differences in compilation. YMMV. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* dwgallien
I've used the vlc in both the vlc and packman repo's, which have worked fine. However, the long-standing advice on the Forums is to use the packman version, IIRC due to differences in compilation. YMMV.
I believe that the present advice is to use one or the other, but *not* to *mix* them. I use vlc from videolan and all others from pacman w/o any problems. Videolan's version of vlc is more recent which is to be expected as videolan is the author :^) -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
dwgallien said the following on 10/04/2010 01:15 PM:
[....]
Or, in YaST Software Repositories, assign a priority of 100 to packman, then again try Update if newer version available or Update unconditionally (veryify under the Installation Summarythat the updates are coming from Packman).
OUCH! Normally I run the command line - zypper - but this time I tried the GUI: kdesu yast2 Its worked in the past - months back - but this time I get kdesu(7223)/kdesu (kdelibs) KDESu::KDESuPrivate::KCookie::getXCookie: No X authentication info set for display ":0" I'm not sure what to make of that. Where has my authentication cookie gone? Has there been some update to the libraries or PAM of the last moth or so that affects this? -- There are two ways to slide easily through life: to believe everything or to doubt everything; both ways save us from thinking. -- Alfred Korzybski -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/4/2010 10:48 AM, Anton Aylward wrote:
dwgallien said the following on 10/04/2010 01:15 PM:
[....]
Or, in YaST Software Repositories, assign a priority of 100 to packman, then again try Update if newer version available or Update unconditionally (veryify under the Installation Summarythat the updates are coming from Packman).
OUCH! Normally I run the command line - zypper - but this time I tried the GUI:
kdesu yast2
Its worked in the past - months back - but this time I get
kdesu(7223)/kdesu (kdelibs) KDESu::KDESuPrivate::KCookie::getXCookie: No X authentication info set for display ":0"
I'm not sure what to make of that. Where has my authentication cookie gone? Has there been some update to the libraries or PAM of the last moth or so that affects this?
Just launch yast from the KDE menues or yast from a shell. Your X server does not appear to be set up correctly. -- _____________________________________ At one time I had a Real Sig. Its been downsized. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
John Andersen said the following on 10/04/2010 02:12 PM:
On 10/4/2010 10:48 AM, Anton Aylward wrote:
dwgallien said the following on 10/04/2010 01:15 PM:
[....]
Or, in YaST Software Repositories, assign a priority of 100 to packman, then again try Update if newer version available or Update unconditionally (veryify under the Installation Summarythat the updates are coming from Packman).
OUCH! Normally I run the command line - zypper - but this time I tried the GUI:
kdesu yast2
Its worked in the past - months back - but this time I get
kdesu(7223)/kdesu (kdelibs) KDESu::KDESuPrivate::KCookie::getXCookie: No X authentication info set for display ":0"
I'm not sure what to make of that. Where has my authentication cookie gone? Has there been some update to the libraries or PAM of the last moth or so that affects this?
Just launch yast from the KDE menues or yast from a shell. Your X server does not appear to be set up correctly.
I think you misunderstand me. That *is* the response I get when trying to start from a shell. Starting from the menu I get the KDESU password dialog then ... nothing ... presumably because Stderr doesn't go the GUI. :-/ If, instead of the KDESU from a terminal window I "su" instead" I get /home/anton # yast2 No protocol specified y2controlcenter: cannot connect to X server :0 whcih does make sense to me - the environment isn't passed though to the shell by "su". Trying to run Yast2 as root I get the Curses version. UGH! You say there's something wrong with my X setup. Well maybe so, but its not a result of any 'edits' I've done, though it may be a result of side-effects of upgrades carried out with the comand line "zypper up". -- "The top line is the value you give. The bottom line is the value you get. Companies that worry about the top line never have to worry about the bottom line." -- Christopher Anvil, "Top Line" Analog Science Fiction, February 1, 1982 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/4/2010 11:53 AM, Anton Aylward wrote:
John Andersen said the following on 10/04/2010 02:12 PM:
On 10/4/2010 10:48 AM, Anton Aylward wrote:
dwgallien said the following on 10/04/2010 01:15 PM:
[....]
Or, in YaST Software Repositories, assign a priority of 100 to packman, then again try Update if newer version available or Update unconditionally (veryify under the Installation Summarythat the updates are coming from Packman).
OUCH! Normally I run the command line - zypper - but this time I tried the GUI:
kdesu yast2
Its worked in the past - months back - but this time I get
kdesu(7223)/kdesu (kdelibs) KDESu::KDESuPrivate::KCookie::getXCookie: No X authentication info set for display ":0"
I'm not sure what to make of that. Where has my authentication cookie gone? Has there been some update to the libraries or PAM of the last moth or so that affects this?
Just launch yast from the KDE menues or yast from a shell. Your X server does not appear to be set up correctly.
I think you misunderstand me.
That *is* the response I get when trying to start from a shell.
Starting from the menu I get the KDESU password dialog then ... nothing ... presumably because Stderr doesn't go the GUI. :-/
If, instead of the KDESU from a terminal window I "su" instead" I get
/home/anton # yast2 No protocol specified y2controlcenter: cannot connect to X server :0
whcih does make sense to me - the environment isn't passed though to the shell by "su".
Trying to run Yast2 as root I get the Curses version. UGH!
You say there's something wrong with my X setup. Well maybe so, but its not a result of any 'edits' I've done, though it may be a result of side-effects of upgrades carried out with the comand line "zypper up".
Yes, perhaps I did understand. For my kde4.5 menuing system lists the yast2 command as /usr/bin/xdg-su -c /sbin/yast2 and when I copy/paste that into a shell it works just fine, but does pop up an authorization window. If I ssh into the machine remotely (or locally I suppose) as root and type yast2 it pops up graphically. If I ssh into the machine as a regular user and enter /usr/bin/xdg-su -c /sbin/yast2 it prompts for roots password and then fires up the graphical Yast2. -- _____________________________________ At one time I had a Real Sig. Its been downsized. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
John Andersen said the following on 10/04/2010 03:18 PM:
On 10/4/2010 11:53 AM, Anton Aylward wrote:
John Andersen said the following on 10/04/2010 02:12 PM:
On 10/4/2010 10:48 AM, Anton Aylward wrote:
dwgallien said the following on 10/04/2010 01:15 PM:
[....]
Or, in YaST Software Repositories, assign a priority of 100 to packman, then again try Update if newer version available or Update unconditionally (veryify under the Installation Summarythat the updates are coming from Packman).
OUCH! Normally I run the command line - zypper - but this time I tried the GUI:
kdesu yast2
Its worked in the past - months back - but this time I get
kdesu(7223)/kdesu (kdelibs) KDESu::KDESuPrivate::KCookie::getXCookie: No X authentication info set for display ":0"
I'm not sure what to make of that. Where has my authentication cookie gone? Has there been some update to the libraries or PAM of the last moth or so that affects this?
Just launch yast from the KDE menues or yast from a shell. Your X server does not appear to be set up correctly.
I think you misunderstand me.
That *is* the response I get when trying to start from a shell.
Starting from the menu I get the KDESU password dialog then ... nothing ... presumably because Stderr doesn't go the GUI. :-/
If, instead of the KDESU from a terminal window I "su" instead" I get
/home/anton # yast2 No protocol specified y2controlcenter: cannot connect to X server :0
whcih does make sense to me - the environment isn't passed though to the shell by "su".
Trying to run Yast2 as root I get the Curses version. UGH!
You say there's something wrong with my X setup. Well maybe so, but its not a result of any 'edits' I've done, though it may be a result of side-effects of upgrades carried out with the comand line "zypper up".
Yes, perhaps I did understand.
For my kde4.5 menuing system lists the yast2 command as /usr/bin/xdg-su -c /sbin/yast2 and when I copy/paste that into a shell it works just fine, but does pop up an authorization window.
If I ssh into the machine remotely (or locally I suppose) as root and type yast2 it pops up graphically.
If I ssh into the machine as a regular user and enter /usr/bin/xdg-su -c /sbin/yast2 it prompts for roots password and then fires up the graphical Yast2.
Yes. It used to be,but something changed all that. Except for the face that this is the machine I ssh FROM, you are describing the set up I had running. * menu worked (with authorization window) * CLI "kdesu /sbin/yast2" worked (with authorization window) from an xterm (well 'konsole' atually) But something has changed. As I say, its no by me hand exiting anything. So I'm going to "init 3" and clean out /tmp/, /var/tmp/, ~*/tmp/ and and stray .xauth* I don't see why I should, but it will make me eel better :-) -- The radical of one century is the conservative of the next. The radical invents the views. When he has worn them out, the conservative adopts them. --Mark Twain -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2010-10-04 at 14:28 +0100, Dave Howorth wrote:
I removed totem with no problem but when I asked it to remove gstreamer it removed lots of things including openoffice and evolution for example before I aborted it.
You must look at the list of things it is going to do before clicking on tha go ahead button.
I reenabled the other repositories and appear to have successfully reinstalled the things it deleted but of course my multimedia still doesn't work.
When I have just packman and libdvdcss enabled, I can see that there are upgrades available for gstreamer but when I try to apply them, many won't because of broken dependencies on packages that I guess are in the standard repositories. But if I reenable the standard repositories, it no longer offers me the upgrades. Is there some way to tell YaST to do the upgrades?
You must have the standard repos enabled, and packman. Adjusts the priorities and switch multimedia packages to the packman version - not remove, but change.
But apparently I can't do that without creating yet another online persona - my novell persona soesn't seem to be good enough for example.
It is not a Novell site, which is why it can pack what it packs. - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAkyqH8gACgkQtTMYHG2NR9Xa+gCffuX3rIVLPtuWQLhhcohlSSP5 l+wAnA3yJFQUgz57fglIIIB4w3G3Lyaa =fuZW -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Dave Howorth wrote:
I spent a miserable few hours over the weekend trying to get an 11.2 box play multimedia.
Hi y'all, I fixed it last night. Unfortunately I hadn't then had the chance to read any of your postings so I wasn't able to take advantage of any of your advice, but thanks anyway. For the benefit of posterity, here's what I did: I found [1] which seems to be a pretty good guide and started following its instructions but I kept getting errors at various points. So I decided to post another request for help and in accordance with what [1] says, I ran the commands at [2]. Most commands worked as they should. Where they didn't, I fixed the specific problem that the command highlighted (like still having a bunch of videolan packages installed) and when I got to the end of the list of ten commands with a clean set of output, my multimedia was working! So IMHO: (a) The procedure at [3] is dangerous and the page should be removed. (b) The procedure at [1] is much better and ought to work if you follow it from the start (c) If you do get in trouble, the diagnostic procedure at [2] is excellent. I also learned a couple of things about YaST that I'd never had cause to use before: - the view tab allows you to choose to view packages from a particular repository - the bottom 2 entries on the Package menu are useful :) It's also necessary to use the qt version of YaST but then I do that anyway because the gnome version is so naff. Cheers, Dave [1] http://forums.opensuse.org/english/information-new-users/new-user-how-faq-re... [2] http://forums.opensuse.org/english/get-help-here/multimedia/400119-check-you... [3] http://opensuse-community.org/Restricted_formats/11.2 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (7)
-
Anton Aylward -
Carlos E. R. -
Dave Howorth -
dwgallien -
John Andersen -
Michael Schroeder -
Patrick Shanahan