… witters something about [l] packman being an invalid address?
lenovo S10e
1.5GB mem
opensuse 11.4 fresh install* with kde desktop
any idea why?
- no, i really haven’t touched repos, this is the way it ‘arrived’
… witters something about [l] packman being an invalid address?
lenovo S10e
1.5GB mem
opensuse 11.4 fresh install* with kde desktop
any idea why?
bump…
If you have pacman repository
su
# zypper install codecs-kde.ymp
If not
Open a terminal
su
# zypper addrepo -f http://download.opensuse.org/repositories/Kernel:/openSUSE-11.4/openSUSE_Factory/i586/
# zypper refresh
It didn’t work for me. I had to substitute the link to packman provided by the one click installer with :
Index of /packman/suse/11.4
Although stamostolias solution most likely works as well I wouldn’t add factory repo if I were You.
Best regards,
Greg
Worked perfectly for me except that, at one point in the download, a repo was not available; however, when I clicked retry it worked.
I just checked the code in those files and it looks correct.
Also, running it on my machine all looked fine. I didn’t complete it, as I already have it all installed.
It may be you folks hit a hiccup in the big switch over etc…
*Other users. Please continue to post issues here if you have any.
This might well be the case. Anyway it makes my life so much easier so thanks again for the one click
Best regards,
Greg
Worked perfectly for me clicking in FF4. Maybe the packman repos were very busy? (My system was upgraded from 11.3 to 11.4 with the release DVD.)
Sorry but I have not upgraded yet. I will upgrade in April. Anyway here the correct URL Index of /pub/linux/misc/packman/suse/openSUSE_11.4
I did a live upgrade from 11.3. I think busy packman repos is the most likely explanation of this problem. Anyway after switching the repo URL to what I posted previously it worked like charm.
Best regards,
Greg
I hope that this late-date (this thread has been dead since 2011) entry will be allowed, because I have a suggestion that might apply to others who might have arrived here with a “1-click failed to install, leaving me with a dangling .ymp document, and which might be causing me problems” issue, just as I did, via a Google query - via the following Google query, in fact:
how can i remove a .ymp file that failed to install?
Well, I went to openSUSE to download a 1-Click Install Okular package, and installation, via Yast, ran into problems, leaving me with an uninstalled Okular package, but with a residual .ymp file that I couldn’t delete, even after installing Okular via Terminal (“zypper install Okular”). Even more spooky, this weird situation was interfering, I’m certain, with my “su” logon to Yast - the logon would freeze, failing utterly to log me on!
Being a believer in reboot as, if not a panacea, then at least a solution to a lot of woes (but not all woes, I have a nagging problem with my Ethernet card not working every other time, though ONLY on my Linux-only backup desktop PC, meaning that I at least have my dual-boot PC that I can use for Internet access, but still, it’s a pain in the butt!), I decided to simply reboot and see if Yast would log me on - it would! Moreover, I noticed that when I went to “Recently used”, the pesky residual .ymp document was gone, so now I expect that THAT issue has resolved itself, via a simple reboot.
(I hope that this posting will prove useful to others plagued with a residual .ymp document left over from a failed 1-Click Install!)
isusogdus
On Fri, 25 Apr 2014 19:36:01 GMT, isusogdus
<isusogdus@no-mx.forums.opensuse.org> wrote:
>
>I hope that this late-date (this thread has been dead since 2011) entry
>will be allowed, because I have a suggestion that might apply to others
>who might have arrived here with a “1-click failed to install, leaving
>me with a dangling .ymp document, and which might be causing me
>problems” issue, just as I did, via a Google query - via the following
>Google query, in fact:
>
>how can i remove a .ymp file that failed to install?
>
>Well, I went to openSUSE to download a 1-Click Install Okular package,
>and installation, via Yast, ran into problems, leaving me with an
>uninstalled Okular package, but with a residual .ymp file that I
>couldn’t delete, even after installing Okular via Terminal (“zypper
>install Okular”). Even more spooky, this weird situation was
>interfering, I’m certain, with my “su” logon to Yast - the logon would
>freeze, failing utterly to log me on!
>
>Being a believer in reboot as, if not a panacea, then at least a
>solution to a lot of woes (but not all woes, I have a nagging problem
>with my Ethernet card not working every other time, though ONLY on my
>Linux-only backup desktop PC, meaning that I at least have my dual-boot
>PC that I can use for Internet access, but still, it’s a pain in the
>butt!), I decided to simply reboot and see if Yast would log me on - it
>would! Moreover, I noticed that when I went to “Recently used”, the
>pesky residual .ymp document was gone, so now I expect that THAT issue
>has resolved itself, via a simple reboot.
>
>(I hope that this posting will prove useful to others plagued with a
>residual .ymp document left over from a failed 1-Click Install!)
>
>isusogdus
Well one thing i do know is that a reboot closes all files and releases
all file locks. So i got to thinking that there may be a non-reboot way
to address this issue.
lsof lists open files, but there are a lot of them, so pipe that to grep
with a filter term. Figure on using two or more passes through grep.
/code
Sorry about the wrap, i use nntp and my editor wrapped the output.
With a tight enough filter you could find the offending processes and kill
them, releasing all the files and the locks associated. Then any loose
files could be cleaned up with a simple rm.
?-)