Bug #172833 “gnome-app-install crashed with SIGSEGV” : Bugs : gnome-app-install package : Ubuntu

Revision history for this message

anonimosanremese (anonimosanremese) wrote on 2007-11-29:

#1

Dependencies.txt Edit (5.2 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (837 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (27.7 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (667 bytes, text/plain; charset="utf-8")
Registers.txt Edit (513 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (598 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (625 bytes, text/plain; charset="utf-8")

Revision history for this message

Paul Dufresne (paulduf) wrote on 2007-11-29:

#2

I have the same StackTrace top, was just after Totem Movie Player (in Mozilla Firefox) had apparently finished searching codecs to play a video:
http://typo3.netfielders.de/xvid/mtb1_1_getting_started_install_the_dummy_package.avi

Decided not to fill a new report.

Will rename my crash (apport seems to just take 1 crash by program and refuse to overwrite an old one by a more recent, should probably report this as a bug) in case it would be needed later, and be able to get a new one if it appears again.

Revision history for this message

Paul Dufresne (paulduf) wrote on 2007-11-29:

#3

Last lines of my .xsession-errors:
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3, rate=(int)22050, channels=(int)1, codec_data=(buffer)010002000000680001007105
** Message: Error: You do not have a decoder installed to handle this file. You might need to install the necessary plugins.
gstplaybasebin.c(2280): prepare_output (): /play

** (gnome-codec-install:7115): WARNING **: return value of custom widget handler was not a GtkWidget

(gnome-codec-install:7115): GStreamer-CRITICAL **: gst_structure_empty_new: assertion `gst_structure_validate_name (name)' failed
checking for valid crashreport now
checking for valid crashreport now
checking for valid crashreport now
checking for valid crashreport now
checking for valid crashreport now
** Message: Missing plugin installation failed: installer-exit-unclean
checking for valid crashreport now
checking for valid crashreport now
checking for valid crashreport now
checking for valid crashreport now
paul@paul-desktop:~$

Revision history for this message

wolfen69 (wolfen69) wrote on 2007-11-30:

#4

i had the same problem as the OP.

Revision history for this message

Dmytro Korzhevin (korg) wrote on 2007-11-30:

#5

Ubuntu 8.04
Same problem. Crash, when i typed "backup" in search box.

Revision history for this message

Bartek Szopka (bartoszopka) wrote on 2007-12-02:

#6

Same problem here.
Application hang for a while when I started to type in search box and then it crashed.

Revision history for this message

Albert Damen (albrt) wrote on 2007-12-02:

#7

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 173118, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

Revision history for this message

Kbo_Marquez (fire9194) wrote on 2007-12-07:

#8

Ubuntu 8.04
Same problem. Crash, when i typed w/e in search box.

Revision history for this message

kamaraopoa (kamaraopoa) wrote on 2007-12-10: Re: [Bug 172833] Re: gnome-app-install crashed with SIGSEGV

#9

Download full text (7.0 KiB)

First, I will show how we can get a full report of the problem, so that
in other forums of life can help us. Then, the more adventurous, I
decided to show my problem and did the network of such PC work in
Ubuntu. Who knows you can not solve your problem as well?
Most of the following commands to be executed as root. In Ubuntu you can
run as root adding the command "sudo" before the command, or using the
command "sudo su" to login as root. In other distribution, use the
command "su -" to gain root access.

Step 1: collecting information on the problem

The first thing to do is to discover how the system sees the hardware
problem. There is no advance in the forum say that your network card of
the SIS is not working. It must describe the model, and this information
can you get with `` lspci. It will list your network card, your video
card, modem and other devices, something fine. Here we go:

# Lspci - nn

00:04.0 Ethernet controller [0200]: Silicon Integrated Systems (SIS) 190
Gigabit Ethernet Adapter [1039:0190] (rev 01)

Seen? Placed only the line of the network card not to pollute the text,
but you should learn more about ten lines. Look problem and the hardware
store and two paragraphs in particular: the first block of numbers that
appears - in the case there from above, the "00:04.0" - and the ID of
the device-in finalzinho, in brackets: 1039:0190.
The module of the hardware problem
Is the module of the device was loaded? Furthermore ... What is the
module him? To discover this we use the ID of the device (in my case, as
we saw above, is 1039:0190).
The ID of the device has two parts: the first four numbers (1039)
indicate the manufacturer (in our case the SIS). The last four (0190)
the model. To learn what is the driver of the device in question between
with this command, obviously replacing the numbers of their ID by:

# Modprobe-c | egrep'1039 .* 0190 '

Alias pci: v00001039d00000190sv * * sd bc * sc * i * sis190

The module is that there at the end of the line, the sis190. Does he is
charged? Enter the command "lsmod | grep sis190." If the command does
not return anything, try to manually load the module using the modprobe
sis190 "(always as root, do not forget). The module loaded, but the
network still does not work? Then continue reading.
Ask kernel: why the hardware does not work?
Now let's see what's happening with the hardware problem during boot
Linux. Therefore, we use the command `dmesg", which shows us the log
with all the "events" of the kernel during boot. But we peneirar the
result, for which only the lines relating to our hardware esquisitão
appear. Therefore, I will filter the output of dmesg by grep, asking him
to show us only the lines containing "00:04.0" - getting that number go
up with the command lspci - nn, remember? Be sure to replace the
"00:04.0" by the block of numbers on your hardware.

# Dmesg | grep'00: 04.0 '
0000:00:04.0: Read MAC address from APIC
0000:00:04.0: Can not find ISA bridge

A-ago, the network card does not find the ISA bridge! What this means? I
know there, the important thing is that the error is this. If you want
to do a search on google or ask for help in th...

First, I will show how we can get a full report of the problem, so that 
in other forums of life can help us. Then, the more adventurous, I 
decided to show my problem and did the network of such PC work in 
Ubuntu. Who knows you can not solve your problem as well?
Most of the following commands to be executed as root. In Ubuntu you can 
run as root adding the command "sudo" before the command, or using the 
command "sudo su" to login as root. In other distribution, use the 
command "su -" to gain root access.

Step 1: collecting information on the problem

The first thing to do is to discover how the system sees the hardware 
problem. There is no advance in the forum say that your network card of 
the SIS is not working. It must describe the model, and this information 
can you get with `` lspci. It will list your network card, your video 
card, modem and other devices, something fine. Here we go:

# Lspci - nn

00:04.0 Ethernet controller [0200]: Silicon Integrated Systems (SIS) 190 
Gigabit Ethernet Adapter [1039:0190] (rev 01)

Seen? Placed only the line of the network card not to pollute the text, 
but you should learn more about ten lines. Look problem and the hardware 
store and two paragraphs in particular: the first block of numbers that 
appears - in the case there from above, the "00:04.0" - and the ID of 
the device-in finalzinho, in brackets: 1039:0190.
The module of the hardware problem
Is the module of the device was loaded? Furthermore ... What is the 
module him? To discover this we use the ID of the device (in my case, as 
we saw above, is 1039:0190).
The ID of the device has two parts: the first four numbers (1039) 
indicate the manufacturer (in our case the SIS). The last four (0190) 
the model. To learn what is the driver of the device in question between 
with this command, obviously replacing the numbers of their ID by:

# Modprobe-c | egrep'1039 .* 0190 '

Alias pci: v00001039d00000190sv * * sd bc * sc * i * sis190

The module is that there at the end of the line, the sis190. Does he is 
charged? Enter the command "lsmod | grep sis190." If the command does 
not return anything, try to manually load the module using the modprobe 
sis190 "(always as root, do not forget). The module loaded, but the 
network still does not work? Then continue reading.
Ask kernel: why the hardware does not work?
Now let's see what's happening with the hardware problem during boot 
Linux. Therefore, we use the command `dmesg", which shows us the log 
with all the "events" of the kernel during boot. But we peneirar the 
result, for which only the lines relating to our hardware esquisitão 
appear. Therefore, I will filter the output of dmesg by grep, asking him 
to show us only the lines containing "00:04.0" - getting that number go 
up with the command lspci - nn, remember? Be sure to replace the 
"00:04.0" by the block of numbers on your hardware.

# Dmesg | grep'00: 04.0 '
0000:00:04.0: Read MAC address from APIC
0000:00:04.0: Can not find ISA bridge

A-ago, the network card does not find the ISA bridge! What this means? I 
know there, the important thing is that the error is this. If you want 
to do a search on google or ask for help in the forums of life, already 
have all the information you need. Go to your favorite forum and give 
this information to your friends:

* Hardware: Silicon Integrated Systems (SIS) 190 Gigabit Ethernet 
Adapter
     * ID hardware: 1039:0190
     * Module hardware: sis190
     * Messages kernel related to the hardware: the output of the 
command post dmesg we saw just above.

If anyone knows solve the problem, it will not be for lack of 
information that will help you stop. Now, if you want to understand what 
is happening and try to solve the problem on their own, continue reading.

Step 2: solving the problem

The command dmesg the problem showed that the kernel is having with our 
hardware: "0000:00:04.0: Can not find ISA bridge." What this means?
I was using a relatively new board of ECS, with chipset SIS (SIS of the 
chipsets tend to be problematic in Linux). The module that supports my 
network card is the sis190. Supposedly the network should be running, 
but our favorite network card is having trouble finding the ISA bridge. 
Why is?
To solve the problem, we take a look at the source code of the module. 
Perhaps we can set the problem and compile the module again, already 
fixed. It's not as difficult as it seems.
Getting the kernel sources
The module network sis190 comes embedded in the kernel. Then we download 
and unpack the source code of the kernel, which brings the source of 
sis190, the module problematic:

# Sudo apt-get install linux-source-`uname-r`
# Tar jxvf / usr/src/linux-source- `uname-r`. Tar.bz2

Now we take a quick peek at the source code of the module in question:

# Gedit / usr/src/linux-source- `uname-r` / drivers/net/sis190.c

Oops, see only what I thought in the middle of the code module:

Isa_bridge = pci_get_device (PCI_VENDOR_ID_SI, 0x0965, NULL);
If (! Isa_bridge) (
Net_probe (tp, KERN_INFO "% s: Can not find ISA bridge.",
Pci_name (pdev));
Return-EIO;
)

Is not, the error message "Can not find ISA bridge!" Here is the problem 
that I was accusing kernel-reminiscent of the command when used dmesg? 
In this case, it is good information on my ISA Bridge to know why the 
driver is not finding it.

# Lspci - nn

00:02.0 ISA bridge [0601]: Silicon Integrated Systems [SiS] Unknown 
device 0966 [1039:0966] (rev 59)

Again the command lspci - nn, but this time is the line that interests 
me. Hmm. .. See that strange: the ID that the lspci complains to my ISA 
bridge is 1039:0966. But there in the code of the driver we have this 
line that says isa_bridge = pci_get_device (PCI_VENDOR_ID_SI, 0x0965, 
NULL); Reparou? The driver says the network card that my ISA bridge is a 
model 0965, but the lspci showed that my model is 0966! The module is 
pointing to the wrong place! Let's change the 0965 to 0966 in the code 
of the module, save the modified file and compile it.

Compiling the new driver

To compile the driver we need the package build-essential. Take one:

Sudo apt-get install build-essential

Let's for the directory of the source and will use some basic commands 
to be able to compile the driver:

# Cd / usr/src/linux-source- `uname-r`
# Make menuconfig

After the last command, and choose exit yes. And the collection itself:

# Make drivers/net/sis190.ko

Ready, the new driver has been compiled. Let's flush the old module, 
copy the new place in it and loads it:

# Rmmod sis190.ko
# Cp drivers/net/sis190.ko / lib / modules / `uname-r` / kernel / 
drivers / net /
# Modprobe sis190

If all went well, you solved the problem and its network is working! You 
can go tell their friends :-)

Kbo_Marquez escreveu:
> *** This bug is a duplicate of bug 173118 ***
>     https://bugs.launchpad.net/bugs/173118
>
> Ubuntu 8.04
> Same problem. Crash, when i typed w/e in search box.
>
>

-- 
Edson Araujo - (Kamarão)
51-8412.7198
Porto Alegre-RS
kmarao@msn.com
OFFICE:51-3737.0144
skype=kamaraopoa
Power by Ubuntu-hARDY - 8.04-ALPHA1*

Revision history for this message

Emilio Pozuelo Monfort (pochu) wrote on 2007-12-10:

#10

Download full text (7.4 KiB)

kamaraopoa wrote:
> *** This bug is a duplicate of bug 173118 ***
> https://bugs.launchpad.net/bugs/173118

The bug has already been fixed. Just update to the latest gnome-app-install and
you will get the fix.

And you don't need to compile any kernel modules - the information you gave is
completely useless.

>
> First, I will show how we can get a full report of the problem, so that
> in other forums of life can help us. Then, the more adventurous, I
> decided to show my problem and did the network of such PC work in
> Ubuntu. Who knows you can not solve your problem as well?
> Most of the following commands to be executed as root. In Ubuntu you can
> run as root adding the command "sudo" before the command, or using the
> command "sudo su" to login as root. In other distribution, use the
> command "su -" to gain root access.
>
> Step 1: collecting information on the problem
>
> The first thing to do is to discover how the system sees the hardware
> problem. There is no advance in the forum say that your network card of
> the SIS is not working. It must describe the model, and this information
> can you get with `` lspci. It will list your network card, your video
> card, modem and other devices, something fine. Here we go:
>
> # Lspci - nn
>
> 00:04.0 Ethernet controller [0200]: Silicon Integrated Systems (SIS) 190
> Gigabit Ethernet Adapter [1039:0190] (rev 01)
>
> Seen? Placed only the line of the network card not to pollute the text,
> but you should learn more about ten lines. Look problem and the hardware
> store and two paragraphs in particular: the first block of numbers that
> appears - in the case there from above, the "00:04.0" - and the ID of
> the device-in finalzinho, in brackets: 1039:0190.
> The module of the hardware problem
> Is the module of the device was loaded? Furthermore ... What is the
> module him? To discover this we use the ID of the device (in my case, as
> we saw above, is 1039:0190).
> The ID of the device has two parts: the first four numbers (1039)
> indicate the manufacturer (in our case the SIS). The last four (0190)
> the model. To learn what is the driver of the device in question between
> with this command, obviously replacing the numbers of their ID by:
>
> # Modprobe-c | egrep'1039 .* 0190 '
>
> Alias pci: v00001039d00000190sv * * sd bc * sc * i * sis190
>
> The module is that there at the end of the line, the sis190. Does he is
> charged? Enter the command "lsmod | grep sis190." If the command does
> not return anything, try to manually load the module using the modprobe
> sis190 "(always as root, do not forget). The module loaded, but the
> network still does not work? Then continue reading.
> Ask kernel: why the hardware does not work?
> Now let's see what's happening with the hardware problem during boot
> Linux. Therefore, we use the command `dmesg", which shows us the log
> with all the "events" of the kernel during boot. But we peneirar the
> result, for which only the lines relating to our hardware esquisitão
> appear. Therefore, I will filter the output of dmesg by grep, asking him
> to show us only the lines containing "00:04.0" - getting that number...

kamaraopoa wrote:
> *** This bug is a duplicate of bug 173118 ***
>     https://bugs.launchpad.net/bugs/173118

The bug has already been fixed. Just update to the latest gnome-app-install and
you will get the fix.

And you don't need to compile any kernel modules - the information you gave is
completely useless.

> 
> First, I will show how we can get a full report of the problem, so that 
> in other forums of life can help us. Then, the more adventurous, I 
> decided to show my problem and did the network of such PC work in 
> Ubuntu. Who knows you can not solve your problem as well?
> Most of the following commands to be executed as root. In Ubuntu you can 
> run as root adding the command "sudo" before the command, or using the 
> command "sudo su" to login as root. In other distribution, use the 
> command "su -" to gain root access.
> 
> Step 1: collecting information on the problem
> 
> The first thing to do is to discover how the system sees the hardware 
> problem. There is no advance in the forum say that your network card of 
> the SIS is not working. It must describe the model, and this information 
> can you get with `` lspci. It will list your network card, your video 
> card, modem and other devices, something fine. Here we go:
> 
> # Lspci - nn
> 
> 00:04.0 Ethernet controller [0200]: Silicon Integrated Systems (SIS) 190 
> Gigabit Ethernet Adapter [1039:0190] (rev 01)
> 
> Seen? Placed only the line of the network card not to pollute the text, 
> but you should learn more about ten lines. Look problem and the hardware 
> store and two paragraphs in particular: the first block of numbers that 
> appears - in the case there from above, the "00:04.0" - and the ID of 
> the device-in finalzinho, in brackets: 1039:0190.
> The module of the hardware problem
> Is the module of the device was loaded? Furthermore ... What is the 
> module him? To discover this we use the ID of the device (in my case, as 
> we saw above, is 1039:0190).
> The ID of the device has two parts: the first four numbers (1039) 
> indicate the manufacturer (in our case the SIS). The last four (0190) 
> the model. To learn what is the driver of the device in question between 
> with this command, obviously replacing the numbers of their ID by:
> 
> # Modprobe-c | egrep'1039 .* 0190 '
> 
> Alias pci: v00001039d00000190sv * * sd bc * sc * i * sis190
> 
> The module is that there at the end of the line, the sis190. Does he is 
> charged? Enter the command "lsmod | grep sis190." If the command does 
> not return anything, try to manually load the module using the modprobe 
> sis190 "(always as root, do not forget). The module loaded, but the 
> network still does not work? Then continue reading.
> Ask kernel: why the hardware does not work?
> Now let's see what's happening with the hardware problem during boot 
> Linux. Therefore, we use the command `dmesg", which shows us the log 
> with all the "events" of the kernel during boot. But we peneirar the 
> result, for which only the lines relating to our hardware esquisitão 
> appear. Therefore, I will filter the output of dmesg by grep, asking him 
> to show us only the lines containing "00:04.0" - getting that number go 
> up with the command lspci - nn, remember? Be sure to replace the 
> "00:04.0" by the block of numbers on your hardware.
> 
> # Dmesg | grep'00: 04.0 '
> 0000:00:04.0: Read MAC address from APIC
> 0000:00:04.0: Can not find ISA bridge
> 
> A-ago, the network card does not find the ISA bridge! What this means? I 
> know there, the important thing is that the error is this. If you want 
> to do a search on google or ask for help in the forums of life, already 
> have all the information you need. Go to your favorite forum and give 
> this information to your friends:
> 
>      * Hardware: Silicon Integrated Systems (SIS) 190 Gigabit Ethernet 
> Adapter
>      * ID hardware: 1039:0190
>      * Module hardware: sis190
>      * Messages kernel related to the hardware: the output of the 
> command post dmesg we saw just above.
> 
> If anyone knows solve the problem, it will not be for lack of 
> information that will help you stop. Now, if you want to understand what 
> is happening and try to solve the problem on their own, continue reading.
> 
> Step 2: solving the problem
> 
> The command dmesg the problem showed that the kernel is having with our 
> hardware: "0000:00:04.0: Can not find ISA bridge." What this means?
> I was using a relatively new board of ECS, with chipset SIS (SIS of the 
> chipsets tend to be problematic in Linux). The module that supports my 
> network card is the sis190. Supposedly the network should be running, 
> but our favorite network card is having trouble finding the ISA bridge. 
> Why is?
> To solve the problem, we take a look at the source code of the module. 
> Perhaps we can set the problem and compile the module again, already 
> fixed. It's not as difficult as it seems.
> Getting the kernel sources
> The module network sis190 comes embedded in the kernel. Then we download 
> and unpack the source code of the kernel, which brings the source of 
> sis190, the module problematic:
> 
> # Sudo apt-get install linux-source-`uname-r`
> # Tar jxvf / usr/src/linux-source- `uname-r`. Tar.bz2
> 
> Now we take a quick peek at the source code of the module in question:
> 
> # Gedit / usr/src/linux-source- `uname-r` / drivers/net/sis190.c
> 
> Oops, see only what I thought in the middle of the code module:
> 
> Isa_bridge = pci_get_device (PCI_VENDOR_ID_SI, 0x0965, NULL);
> If (! Isa_bridge) (
> Net_probe (tp, KERN_INFO "% s: Can not find ISA bridge.",
> Pci_name (pdev));
> Return-EIO;
> )
> 
> Is not, the error message "Can not find ISA bridge!" Here is the problem 
> that I was accusing kernel-reminiscent of the command when used dmesg? 
> In this case, it is good information on my ISA Bridge to know why the 
> driver is not finding it.
> 
> # Lspci - nn
> 
> 00:02.0 ISA bridge [0601]: Silicon Integrated Systems [SiS] Unknown 
> device 0966 [1039:0966] (rev 59)
> 
> Again the command lspci - nn, but this time is the line that interests 
> me. Hmm. .. See that strange: the ID that the lspci complains to my ISA 
> bridge is 1039:0966. But there in the code of the driver we have this 
> line that says isa_bridge = pci_get_device (PCI_VENDOR_ID_SI, 0x0965, 
> NULL); Reparou? The driver says the network card that my ISA bridge is a 
> model 0965, but the lspci showed that my model is 0966! The module is 
> pointing to the wrong place! Let's change the 0965 to 0966 in the code 
> of the module, save the modified file and compile it.
> 
> Compiling the new driver
> 
> To compile the driver we need the package build-essential. Take one:
> 
> Sudo apt-get install build-essential
> 
> Let's for the directory of the source and will use some basic commands 
> to be able to compile the driver:
> 
> # Cd / usr/src/linux-source- `uname-r`
> # Make menuconfig
> 
> After the last command, and choose exit yes. And the collection itself:
> 
> # Make drivers/net/sis190.ko
> 
> Ready, the new driver has been compiled. Let's flush the old module, 
> copy the new place in it and loads it:
> 
> # Rmmod sis190.ko
> # Cp drivers/net/sis190.ko / lib / modules / `uname-r` / kernel / 
> drivers / net /
> # Modprobe sis190
> 
> If all went well, you solved the problem and its network is working! You 
> can go tell their friends :-)
> 
> Kbo_Marquez escreveu:
>> *** This bug is a duplicate of bug 173118 ***
>>     https://bugs.launchpad.net/bugs/173118
>>
>> Ubuntu 8.04
>> Same problem. Crash, when i typed w/e in search box.
>>
>>   
>

Ubuntu
gnome-app-install package

gnome-app-install crashed with SIGSEGV

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntugnome-app-install package

gnome-app-install crashed with SIGSEGV

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
gnome-app-install package