I can not update or install packages on Suse 12.3

English Applications
1

Hello guys,
I just formatted my machine with OpenSuse 12.3.
Since formated could not install anything! Anything I have installed the Yast arrives sometime appears that this message!

Subprocess failed. Error: RPM failed: Command was killed by signal 11 (Segmentation fault).

If I try the terminal appears the same. Sometimes reports that “Installation was interrupted by the User.”
Note: this happens in any program I try to install both the Yast2 as the terminal using zypper.
I tried to upgrade the system and the same mistake was made​​.
Until some packages updated but always shows this error.

# zypper dup
...
Retrieving package kde-gtk-config-2.1.1-4.1.1.x86_64                                                                                                   (345/537),  81.9 KiB (306.8 KiB unpacked)
Retrieving: kde-gtk-config-2.1.1-4.1.1.x86_64.rpm ........................................................................................................................................[done]
Retrieving package kde-gtk-config-lang-2.1.1-4.1.1.noarch                                                                                              (346/537),  30.9 KiB (275.3 KiB unpacked)
Retrieving: kde-gtk-config-lang-2.1.1-4.1.1.noarch.rpm ......................................................................................................................[done (13.4 KiB/s)]
Retrieving package okular-4.10.3-1.28.1.x86_64                                                                                                         (347/537),   1.4 MiB (  4.4 MiB unpacked)
Retrieving: okular-4.10.3-1.28.1.x86_64.rpm ................................................................................................................................[done (538.3 KiB/s)]
(  1/537) Installing: bash-doc-4.2-61.1.3 ...............................................................................................................................................[error]
Installation of bash-doc-4.2-61.1.3 failed:
(with --nodeps --force) Error: Subprocess failed. Error: RPM failed: Command was killed by signal 11 (Segmentation fault).

Abort, retry, ignore? [a/r/i] (a): i
(  2/537) Installing: bluedevil-lang-1.3-2.1.2 ..........................................................................................................................................[error]
Installation of bluedevil-lang-1.3-2.1.2 failed:
(with --nodeps --force) Error: Subprocess failed. Error: RPM failed: Command was killed by signal 11 (Segmentation fault).

I do not understand what is happening. I’ve used this same distro, including the same version and had no problem.
Now appreciate the help.
Thank you.

2

Mot that I understand why you have this problem, but just to make a few things clear:

. When you say “I just formatted my machine with OpenSuse 12.3.”, you mean you did a fresh installation of openSUSE?

. When you did a fresh installation, why then do you do “zypper dup”?

. Can we see your repos?

zypper lr -d
3

On 2013-06-27 14:06, hcvv wrote:
>
> Mot that I understand why you have this problem, but just to make a few
> things clear:

All package managers in the end call “rpm”, and this one crashes.

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

4

Sounds to me like you have a broken installation, possibly due to an interrupted “zypper dup”

As hcvv suggests,
It might be useful to know <what> repos you’re using to upgrade your openSUSE.

After verifying that you have a valid repo source configured (eg DVD, ISO or online sources), you probably will need to run “zypper dup” again <to conclusion>. And then, if necessary address minor fixes for things that might not have configured properly (At least for me, I found that zypper dup upgrading is flawless but zypper dup repairing might not be 100%).

Then, after that <do not ever> run “zypper dup” again except for repair or upgrade to the next version of openSUSE (use zypper up or zypper patch instead for normal maintenance).

If I were to guess, you’re running “zypper dup” without a valid repo source, you probably only have repos configured which do not support that command.

HTH,
TSU

5

On 2013-06-27 18:36, tsu2 wrote:
>
> Sounds to me like you have a broken installation, possibly due to an
> interrupted “zypper dup”
>
> As hcvv suggests,
> It might be useful to know <what> repos you’re using to upgrade your
> openSUSE.

Indeed.

> After verifying that you have a valid repo source configured (eg DVD,
> ISO or online sources), you probably will need to run “zypper dup” again
> <to conclusion>.

As rpm is broken, it will not work. To repair, he would have to do an
upgrade of 12.3 to 12.3 using the DVD method (boot, choose upgrade).

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

6

On 06/27/2013 03:33 PM, Carlos E. R. pecked at the keyboard and wrote:
> On 2013-06-27 18:36, tsu2 wrote:
>> Sounds to me like you have a broken installation, possibly due to an
>> interrupted “zypper dup”
>>
>> As hcvv suggests,
>> It might be useful to know <what> repos you’re using to upgrade your
>> openSUSE.
> Indeed.
>
>> After verifying that you have a valid repo source configured (eg DVD,
>> ISO or online sources), you probably will need to run “zypper dup” again
>> <to conclusion>.
> As rpm is broken, it will not work. To repair, he would have to do an
> upgrade of 12.3 to 12.3 using the DVD method (boot, choose upgrade).
>

The method I find quite reliable is to modify all repos to the newer
version and then:


zypper ref
zypper patch  (should install newer version of rpm and zypp)
zypper dup

Hasn’t failed me yet but YMMV.

Ken

7

On 2013-06-27 22:22, Ken Schneider wrote:
> On 06/27/2013 03:33 PM, Carlos E. R. pecked at the keyboard and wrote:

>> As rpm is broken, it will not work. To repair, he would have to do an
>> upgrade of 12.3 to 12.3 using the DVD method (boot, choose upgrade).
>>
>
> The method I find quite reliable is to modify all repos to the newer
> version and then:

Again. The rpm command segfaults in his system. He can not use any of
zypper, yast, apper, because ALL will fail as long as rpm is broken. And
you can not install the rpm toolchain if you can not run any package
manager nor even rpm!

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

8

Instead of repeating yourself in talking to everybody but the OP, maybe you could start talking to the OP and suggest something he should show/do/explain to get on the road to repair this.

9

Guys,
I preferred to reinstalling the OpenSuse. But, after the process, when it appears show the grub menu and I click in OpenSuse (the first option), I wait a few seconds, and the computer is restarted.
Whats happening? This is really very strange.
Could be a hardware with problem?

(I’m brazilian. So sorry per errors of writing)

10

On 2013-06-28 12:26, hcvv wrote:
>
> robin_listas;2567883 Wrote:
>>
>> Again. The rpm command segfaults in his system. He can not use any of
>> zypper, yast, apper, because ALL will fail as long as rpm is broken.
>> And
>> you can not install the rpm toolchain if you can not run any package
>> manager nor even rpm!

> Instead of repeating yourself in talking to everybody but the OP, maybe
> you could start talking to the OP and suggest something he should
> show/do/explain to get on the road to repair this.

I already did, 18 hours ago, but he does not come back and comment on
how he succeeds or fails to do it.

I have to warn about wrong advices, too.

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

11

So guys,
Somebody have any idea that what’s happening?

12

Yes, as has been mentioned, rpm is crashing. But why we have yet to find out.

What output do you get if you run:

rpm -q rpm
13

rpm has nothing to do with the boot process. It sounds like his HDD is dying. rafaelfrazao, boot to a live CD to rescue your data. Run *fsck *to test the root/boot partitions. Paste the results back here.

14

Ok. I am in work right now. But when I get home, I post the result.
Thanks.

15

Pardon?
Who said anything about the boot process?

I thought he can’t update or install packages on Suse 12.3…:stuck_out_tongue:

16

Read message #9. He isn’t getting past the grub menu now. A new post should probably be started.

17

Ah well. I somehow missed that sentence.

That really sounds like a bad harddisk then, I’m afraid.

18

On 2013-06-28 19:06, wolfi323 wrote:
>
> chief_sealth;2568120 Wrote:
>> rpm has nothing to do with the boot process. It sounds like his HDD is
>> dying. rafaelfrazao, boot to a live CD to rescue your data.
>> Run -fsck -to test the root/boot partitions. Paste the results back
>> here.
> Pardon?
> Who said anything about the boot process?
>
> I thought he can’t update or install packages on Suse 12.3…

He said he had reinstalled openSUSE. It is difficult to understand him,
I know.

He said: «I preferred to reinstalling the OpenSuse. But, after the
process, when it appears show the grub menu and I click in OpenSuse (the
first option), I wait a few seconds, and the computer is restarted.»

So, now it is no longer the problem in the tittle, but a boot problem on
a new install. IMO, he should start a new thread with an appropriate tittle.

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

19

So guys,
Bad hard disk? But the installation was finished normally.
Until the grub, the computer are working normally. But when I click in OpenSuse 12.3 in the grub menu, the computer is rebooted.

Sorry for errors writing again and thanks for the helps.

20

Well, the harddisk doesn’t necessarily have to be bad.
But it would be a possible explanation.

Could you boot with a LiveCD and post the output of:

sudo smartctl -a /dev/sda