Re: Segmentation fault in Chromium

[Marco M.]

Am 02.10.2023 um 13:16:24 Uhr schrieb Richmond:

> I received a segmentation fault from chromium. Would it be logged
> anywhere?

Install gdb and run it with that to get more information.

Segmentation fault in Chromium

[Richmond]

I received a segmentation fault from chromium. Would it be logged
anywhere? I searched journalctl but no mention of it.

Chromium 117.0.5938.132 built on Debian 11.7, running on Debian 11.7

5.10.0-25-amd64 #1 SMP Debian 5.10.191-1 (2023-08-16) x86_64 GNU/Linux

I expect such things cannot be logged but it would be good to find out
what it is.

unknown package causing segmentation fault

[Nicholas Quednow]

Greetings,

I have been trying to figure out why in the world I am getting a
segmentation fault on trying to restart the networking service and using
the ip command.

At this point the server has been restarted and the problem has gone away,
but I did think to dump the dmesg log to a file before restarting.

The offending parts appear only at the very end of the logs, and I was not
sure what to file the report under.

Parts of the log for the segmentation fault The jump in time was me waking
up after a power outage from this morning a few hours prior):
[   61.069997] ip[8355]: segfault at 0 ip 560cde35e530 sp
7ffcfda51c68 error 6 in ip[560cde2f4000+6d000] likely on CPU 5 (core 2,
socket 0)
[   61.070016] Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
<00> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 8110.663298] show_signal_msg: 5 callbacks suppressed
[ 8110.663303] ip[8642]: segfault at 0 ip 559203f34530 sp
7ffd79a02db8 error 6 in ip[559203eca000+6d000] likely on CPU 4 (core 2,
socket 1)
[ 8110.663319] Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
<00> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 8115.767137] ip[8643]: segfault at 0 ip 55d213aab530 sp
7ffc310e04d8 error 6 in ip[55d213a41000+6d000] likely on CPU 6 (core 8,
socket 1)
[ 8115.767154] Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
<00> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 8152.184701] ip[8663]: segfault at 0 ip 558356545530 sp
7fffd65a1928 error 6 in ip[5583564db000+6d000] likely on CPU 8 (core 9,
socket 1)
[ 8152.184721] Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
<00> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[ 8152.192623] ip[8668]: segfault at 0 ip 55c958855530 sp
7ffc42addbd8 error 6 in ip[55c9587eb000+6d000] likely on CPU 8 (core 9,
socket 1)
[ 8152.192640] Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
<00> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Thank you,
Nicholas Quednow

Re: intel-media-va-driver segmentation fault in unstable

[Jörg-Volker Peetz]

Is already in Debian BTS: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007992

Regards,
Jörg.

Re: intel-media-va-driver segmentation fault in unstable

[Miguel A. Vallejo]

Karthik () wrote:
>
> Same here

I took a look at the syslog and found something:

Mar 23 13:21:51 kernel: [  347.474189] vlc[2625]: segfault at
30200 ip 7f75b88659ae sp 7f75 b8d23b00 error 4 in
libigdgmm.so.12.1.0[7f75b87fc000+78000]
Mar 23 13:21:51 kernel: [  347.474197] Code: ff 4c 8b 55 c8 31 c0 b9
40 00 00 00 4c 8b 45 b8 4c 89 fe 49 8d 92 b0 33 00 00 48 89 d7 f3 41
0f 6f 00 ba c4 06 00 00 f3 48 ab <49> 8b 06 49 8d 7a 44 41 c7 82 b8 35
00 00 0a 00 00 00 f3 41 0f 6f
Mar 23 13:23:11 kernel: [  427.398576] vainfo[2646]: segfault at
30200 ip 7fc7348059ae sp 7 ffd46cdc950 error 4 in
libigdgmm.so.12.1.0[7fc73479c000+78000]
Mar 23 13:23:11 kernel: [  427.398584] Code: ff 4c 8b 55 c8 31 c0 b9
40 00 00 00 4c 8b 45 b8 4c 89 fe 49 8d 92 b0 33 00 00 48 89 d7 f3 41
0f 6f 00 ba c4 06 00 00 f3 48 ab <49> 8b 06 49 8d 7a 44 41 c7 82 b8 35
00 00 0a 00 00 00 f3 41 0f 6f

So the culprit is libigdgmm. With this info and a quick search I found this:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007992

A downgrade of libigdgmm12 (both amd64 and i386) to a previous version
fixes it temporarily

Re: intel-media-va-driver segmentation fault in unstable

[Karthik]

On Wed, Mar 23, 2022, 5:54 PM Miguel A. Vallejo  wrote:

> Hello!
>
> Since the lass update last night in Sid / Unstable, I'm getting
> segmentation faults from some programs, like VLC:
>
Same here

>
> vlc video.mkv
> VLC media player 3.0.17.3 Vetinari (revision 3.0.13-8-g41878ff4f2)
> [55c0d2e29460] main libvlc: Running vlc with the default
> interface. Use 'cvlc' to use vlc without interface.
> [7f758c004380] gl gl: Initialized libplacebo v4.192.1 (API v192)
> libva info: VA-API version 1.14.0
> libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
> libva info: Found init function __vaDriverInit_1_14
> Segmentation fault


> Every program using libva drivers segfaults like vlc,mpv

Current solution is to disable hardware acceleration in them
>
> Even utilities like vainfo fails:
>
> vainfo
> libva info: VA-API version 1.14.0
> libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
> libva info: Found init function __vaDriverInit_1_14
> Segmentation fault
>
>
> Any ideas? Thanks in advance


>
> Chromium also disabled GPU Acceleration due to gpu process crash


> This can be confirmed by going into

chrome://gpu


> Im thinking something messed up with nvidia driver update in optimus
> systems

Are you using optimus system?

intel-media-va-driver segmentation fault in unstable

[Miguel A. Vallejo]

Hello!

Since the lass update last night in Sid / Unstable, I'm getting
segmentation faults from some programs, like VLC:

vlc video.mkv
VLC media player 3.0.17.3 Vetinari (revision 3.0.13-8-g41878ff4f2)
[55c0d2e29460] main libvlc: Running vlc with the default
interface. Use 'cvlc' to use vlc without interface.
[7f758c004380] gl gl: Initialized libplacebo v4.192.1 (API v192)
libva info: VA-API version 1.14.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_14
Segmentation fault


Even utilities like vainfo fails:

vainfo
libva info: VA-API version 1.14.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_14
Segmentation fault


Any ideas? Thanks in advance

Re: Xorg fatal server error segmentation fault i686

[Felix Miata]

Richmond composed on 2021-05-05 12:49 (UTC+0100):

> I installed debian on an old PC i686. I chose the mate desktop. When I
> tried to log in throught display manager I could not, so:

> I closed X down with telinit 3
> I logged in on the console as root
> I ran xinit -- :0
> I switched to a non root user in the xterm window on the display
> I typed export DISPLAY=:0
> I ran mate-session
> X crashed with a segmentation fault

> The backtrace is on the console so I cannot cut and paste it. It says it
> is in Xorg at _start+0x31

> What can I do? Perhaps use a different xserver. The display driver is
> nouveau.

I use nouveau kernel driver, modesetting X driver:
# inxi -CGISxxy
System:
  Host: gx27c Kernel: 4.19.0-16-686 i686 bits: 32 compiler: gcc v: 8.3.0
  Desktop: Trinity R14.0.10 tk: Qt 3.5.0 wm: Twin dm: TDM
  Distro: Debian GNU/Linux 10 (buster)
CPU:
  Info: Single Core model: Intel Pentium 4 bits: 32 type: MCP
  arch: Netburst Northwood rev: 9 cache: L1: 8 KiB L2: 512 KiB
  flags: pae sse sse2 bogomips: 4788
  Speed: 2394 MHz min/max: N/A Core speed (MHz): 1: 2394
Graphics:
  Device-1: NVIDIA NV11 [GeForce2 MX/MX 400] vendor: Palit Microsystems
  driver: nouveau v: kernel bus-ID: 01:00.0 chip-ID: 10de:0110
  Display: x11 server: X.Org 1.20.4 driver: loaded: modesetting
  resolution: 1680x1050~60Hz s-dpi: 96
  OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6
  compat-v: 3.1 direct render: Yes
Info:
  Processes:...Shell: Bash v: 5.0.3 running-in: konsole  inxi: 3.3.04
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: Xorg fatal server error segmentation fault i686

[Richmond]

Dan Ritter  writes:

> Richmond wrote: 
>> I installed debian on an old PC i686. I chose the mate desktop. When I
>> tried to log in throught display manager I could not, so:
>> 
>> I closed X down with telinit 3
>> I logged in on the console as root
>> I ran xinit -- :0
>> I switched to a non root user in the xterm window on the display
>> I typed export DISPLAY=:0
>> I ran mate-session
>> X crashed with a segmentation fault
>> 
>> The backtrace is on the console so I cannot cut and paste it. It says it
>> is in Xorg at _start+0x31
>> 
>> What can I do? Perhaps use a different xserver. The display driver is
>> nouveau.
>
> I wouldn't expect that to segfault, but I also wouldn't expect
> it to work -- you did not authorize your non-root user to run in
> that X session.
>
> Try this:
>
> As your non-root user, write a .xinitrc:
>
> #!/bin/sh
> xterm &
> exec mate-session
>
> and then run
>
> startx
>
> Tell us what happens then. If it crashes, let us see your
> /etc/apt/sources.list and anything in sources.list.d/
>
> -dsr-

It crashed. The errors on the console are several fatal errors from
mate-panel, marco, mate-session, and xterm. The xorg log shows a
segmentation fault but I cannot be sure when it happened as the date is
in an inhuman format.

I'll bet it is to do with desktop effects.

Here is the sources.list. There is nothing in sources.d. I don't
understand this file because I installed from the DVD-1, and I am using an
i686. After the installation I commented out the second cdrom line
because it was prompting me when I tried to install software. The first
line was already commented out. During the installation I enabled online
repos so that it would be up to date.




# 

# deb cdrom:[Debian GNU/Linux 10.8.0 _Buster_ - Official amd64 NETINST 
20210206-10:34]/ buster main

# deb cdrom:[Debian GNU/Linux 10.8.0 _Buster_ - Official amd64 NETINST 
20210206-10:34]/ buster main

deb http://deb.debian.org/debian/ buster main contrib non-free
deb-src http://deb.debian.org/debian/ buster main

deb http://security.debian.org/debian-security buster/updates main
deb-src http://security.debian.org/debian-security buster/updates main

# buster-updates, previously known as 'volatile'
deb http://deb.debian.org/debian/ buster-updates main
deb-src http://deb.debian.org/debian/ buster-updates main

deb http://deb.debian.org/debian buster-backports main

# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.

Re: Xorg fatal server error segmentation fault i686

[Brad Rogers]

On Wed, 05 May 2021 18:36:50 +0100
Richmond  wrote:

Hello Richmond,

>package called nvidia-detect for this architecture.

Oops, I'm sorry - you're right - I didn't check properly.

Again, sorry about getting your hopes up.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
Well I don't want you to think I'm being obscene
Fish - The Damned


pgptFdSed0sr1.pgp
Description: OpenPGP digital signature

Re: Xorg fatal server error segmentation fault i686

[Richmond]

Brad Rogers  writes:

> On Wed, 05 May 2021 15:31:25 +0100
> Richmond  wrote:
>
> Hello Richmond,
>
>>01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV11
>>[GeForce2 MX/MX 400] [10de:0110] (rev b2)
>
> As mentioned by Greg;
>
> On Wed, 5 May 2021 11:14:44 -0400
> Greg Wooledge  wrote:
>>Or else look for this nvidia detection script that I've heard about
>>in the past, which is supposed to tell you.
>
> The package you'll need is nvidia-detect.  It runs from the command
> line (simply; nvidia-detect) and gives an output which includes a
> recommendation as to which suite of packages to use (i.e. current, or
> one of the legacy packages).
>
> As an example;
>
> brad@earth:~$ nvidia-detect 
> Detected NVIDIA GPUs:
> 07:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU116
> [GeForce GTX 1650 SUPER] [10de:2187] (rev a1)
>
> Checking card:  NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER] (rev
> a1) Your card is supported by the default drivers.
> Your card is also supported by the Tesla 460 drivers series.
> Your card is also supported by the Tesla 450 drivers series.
> It is recommended to install the
> nvidia-driver
> package.

I have added non-free contrib to sources but there does not seem to be a
package called nvidia-detect for this architecture. There is such a
package on a laptop I have but that is 64 bit.

I think the driver is this one:

https://www.nvidia.co.uk/Download/driverResults.aspx/1252/en-uk

But I don't want to risk installing it from there.

Certainly I have used an nvidia driver on the PC many years ago with
opensuse but they don't support 32 bit anymore except with tumbleweed
and that doesn't include nvidia driver installation.

Re: Xorg fatal server error segmentation fault i686

[Richmond]

Dan Ritter  writes:

> Richmond wrote: 
>> Dan Ritter  writes:
>> 
>> > Richmond wrote: 
>> >> I installed debian on an old PC i686. I chose the mate desktop. When I
>> >> tried to log in throught display manager I could not, so:
> ...
>> >> What can I do? Perhaps use a different xserver. The display driver is
>> >> nouveau.
>> >
>> > I wouldn't expect that to segfault, but I also wouldn't expect
>> > it to work -- you did not authorize your non-root user to run in
>> > that X session.
>> 
>> It crashed. The errors on the console are several fatal errors from
>> mate-panel, marco, mate-session, and xterm. The xorg log shows a
>> segmentation fault but I cannot be sure when it happened as the date is
>> in an inhuman format.
>> 
>> I'll bet it is to do with desktop effects.
>> 
>> Here is the sources.list. There is nothing in sources.d. I don't
>
> Good, we're making progress. Time to chase down Greg's idea,
> which is that you have driver problems.
>
> Answer his questions about lspci and such, and check for the
> installation of
>
> firmware-misc-nonfree
>
> You probably need that for your graphics card, and it probably
> needs a full reboot after.
>
> -dsr-

I managed to get mate working after a fashion by installing mate-tweaks,
then changing the window manager to marco nocompositor. So mate works,
but there was nothing on the panel so I had to add a menu.

Re: Xorg fatal server error segmentation fault i686

[Brad Rogers]

On Wed, 05 May 2021 15:31:25 +0100
Richmond  wrote:

Hello Richmond,

>01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV11
>[GeForce2 MX/MX 400] [10de:0110] (rev b2)

As mentioned by Greg;

On Wed, 5 May 2021 11:14:44 -0400
Greg Wooledge  wrote:
>Or else look for this nvidia detection script that I've heard about
>in the past, which is supposed to tell you.

The package you'll need is nvidia-detect.  It runs from the command
line (simply; nvidia-detect) and gives an output which includes a
recommendation as to which suite of packages to use (i.e. current, or
one of the legacy packages).

As an example;

brad@earth:~$ nvidia-detect 
Detected NVIDIA GPUs:
07:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU116
[GeForce GTX 1650 SUPER] [10de:2187] (rev a1)

Checking card:  NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER] (rev
a1) Your card is supported by the default drivers.
Your card is also supported by the Tesla 460 drivers series.
Your card is also supported by the Tesla 450 drivers series.
It is recommended to install the
nvidia-driver
package.



-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
All these things are mine!
Money is Not Our God -  Killing Joke


pgpQ2Sxv_qxlc.pgp
Description: OpenPGP digital signature

Re: Xorg fatal server error segmentation fault i686

[Greg Wooledge]

On Wed, May 05, 2021 at 03:31:25PM +0100, Richmond wrote:
> > 1) Identify your video hardware.  Use "lspci -nn" for this.
> 
> 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV11
> [GeForce2 MX/MX 400] [10de:0110] (rev b2)

OK.  This is... a rather old device.


has instructions for three different proprietary nvidia drivers.
The problem is I don't know which one you need.  You may just need
to try all three, one at a time, and see what happens.

Or else look for this nvidia detection script that I've heard about
in the past, which is supposed to tell you.

There are links to lists of supported devices, and yours is listed under
the section that says it's supported by something called the "96.43.xx"
driver, but I do not know how that designation maps to any of the three
different Debian package names for nvidia drivers.

Re: Xorg fatal server error segmentation fault i686

[Richmond]

Greg Wooledge  writes:

> On Wed, May 05, 2021 at 08:20:21AM -0400, Dan Ritter wrote:
>> As your non-root user, write a .xinitrc:
>> 
>> #!/bin/sh
>> xterm &
>> exec mate-session
>> 
>> and then run
>> 
>> startx
>> 
>> Tell us what happens then. If it crashes, let us see your
>> /etc/apt/sources.list and anything in sources.list.d/
>
> In addition to this:
>
> 1) Identify your video hardware.  Use "lspci -nn" for this.

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV11
[GeForce2 MX/MX 400] [10de:0110] (rev b2)

>
> 2) Check for any missing firmware.  Use "dmesg | grep -i firmware" for
>this.
>

No output.

Re: Xorg fatal server error segmentation fault i686

[Dan Ritter]

Richmond wrote: 
> Dan Ritter  writes:
> 
> > Richmond wrote: 
> >> I installed debian on an old PC i686. I chose the mate desktop. When I
> >> tried to log in throught display manager I could not, so:
...
> >> What can I do? Perhaps use a different xserver. The display driver is
> >> nouveau.
> >
> > I wouldn't expect that to segfault, but I also wouldn't expect
> > it to work -- you did not authorize your non-root user to run in
> > that X session.
> 
> It crashed. The errors on the console are several fatal errors from
> mate-panel, marco, mate-session, and xterm. The xorg log shows a
> segmentation fault but I cannot be sure when it happened as the date is
> in an inhuman format.
> 
> I'll bet it is to do with desktop effects.
> 
> Here is the sources.list. There is nothing in sources.d. I don't

Good, we're making progress. Time to chase down Greg's idea,
which is that you have driver problems.

Answer his questions about lspci and such, and check for the
installation of

firmware-misc-nonfree

You probably need that for your graphics card, and it probably
needs a full reboot after.

-dsr-

Re: Xorg fatal server error segmentation fault i686

[Richmond]

Scrap the previous /etc/apt/sources I forgot I was using ssh into a
different pc.

cat /etc/apt/sources.list
# 

# deb cdrom:[Debian GNU/Linux 10.9.0 _Buster_ - Official i386 DVD Binary-1 
20210327-10:50]/ buster contrib main

# deb cdrom:[Debian GNU/Linux 10.9.0 _Buster_ - Official i386 DVD Binary-1 
20210327-10:50]/ buster contrib main

deb http://deb.debian.org/debian/ buster main
deb-src http://deb.debian.org/debian/ buster main

deb http://security.debian.org/debian-security buster/updates main contrib
deb-src http://security.debian.org/debian-security buster/updates main contrib

# buster-updates, previously known as 'volatile'
deb http://deb.debian.org/debian/ buster-updates main contrib
deb-src http://deb.debian.org/debian/ buster-updates main contrib

Re: Xorg fatal server error segmentation fault i686

[Richmond]

Richmond  writes:

> I installed debian on an old PC i686. I chose the mate desktop. When I
> tried to log in throught display manager I could not, so:
>
> I closed X down with telinit 3
> I logged in on the console as root
> I ran xinit -- :0
> I switched to a non root user in the xterm window on the display
> I typed export DISPLAY=:0
> I ran mate-session
> X crashed with a segmentation fault
>
> The backtrace is on the console so I cannot cut and paste it. It says it
> is in Xorg at _start+0x31

I think that was start_

>
> What can I do? Perhaps use a different xserver. The display driver is
> nouveau.

I am currently using icewm manager instead but would rather use Mate.

Re: Xorg fatal server error segmentation fault i686

[Greg Wooledge]

On Wed, May 05, 2021 at 08:20:21AM -0400, Dan Ritter wrote:
> As your non-root user, write a .xinitrc:
> 
> #!/bin/sh
> xterm &
> exec mate-session
> 
> and then run
> 
> startx
> 
> Tell us what happens then. If it crashes, let us see your
> /etc/apt/sources.list and anything in sources.list.d/

In addition to this:

1) Identify your video hardware.  Use "lspci -nn" for this.

2) Check for any missing firmware.  Use "dmesg | grep -i firmware" for
   this.

   If there are any missing firmware files that the kernel wants to use,
   figure out which (non-free) package they're in, install that, and
   reboot.

The OP mentioned "nouveau", which means an nvidia device is in play.  This
means it may also be necessary to install some proprietary nvidia drivers.
We won't know for sure until we know which device it is.

Re: Xorg fatal server error segmentation fault i686

[Dan Ritter]

Richmond wrote: 
> I installed debian on an old PC i686. I chose the mate desktop. When I
> tried to log in throught display manager I could not, so:
> 
> I closed X down with telinit 3
> I logged in on the console as root
> I ran xinit -- :0
> I switched to a non root user in the xterm window on the display
> I typed export DISPLAY=:0
> I ran mate-session
> X crashed with a segmentation fault
> 
> The backtrace is on the console so I cannot cut and paste it. It says it
> is in Xorg at _start+0x31
> 
> What can I do? Perhaps use a different xserver. The display driver is
> nouveau.

I wouldn't expect that to segfault, but I also wouldn't expect
it to work -- you did not authorize your non-root user to run in
that X session.

Try this:

As your non-root user, write a .xinitrc:

#!/bin/sh
xterm &
exec mate-session

and then run

startx

Tell us what happens then. If it crashes, let us see your
/etc/apt/sources.list and anything in sources.list.d/

-dsr-

Xorg fatal server error segmentation fault i686

[Richmond]

I installed debian on an old PC i686. I chose the mate desktop. When I
tried to log in throught display manager I could not, so:

I closed X down with telinit 3
I logged in on the console as root
I ran xinit -- :0
I switched to a non root user in the xterm window on the display
I typed export DISPLAY=:0
I ran mate-session
X crashed with a segmentation fault

The backtrace is on the console so I cannot cut and paste it. It says it
is in Xorg at _start+0x31

What can I do? Perhaps use a different xserver. The display driver is
nouveau.

Re: sqlitebrowser -> segmentation fault

[Laurent COOPER]

  
  
Bonjour
Cela ressemble, si c'est reproductible, à un méchant bug. Il est
  toujours possible d'ouvrir un rapport de bug debian, mais c'est
  sans doute un bug upstream, peut être déjà résolu (il faut voir au
  niveau de sqlitebrowser)
En espérant être utile
Laurent

Le 26/09/2020 à 13:42, Fabrice
  Delvallée a écrit :


  
   
   Bonjour
  
  
  J’ignore si c’est
la bonne méthode, mais je suis persuadé que vous pourrez
m’auguiller.
  
  
  J’utilise
« sqlitebrowser » dans une buster à jour. ( DB Browser pour
SQLite version 3.10.1.)
  
  
  Sur plusieurs
machines différentes celui-ci plante « segmentation fault»
lorsqu’on essaye de modifier une table et changer le type d’un
champ
  
  
  Détail des
manipulations :
  
  
  Nouvelle base de
données
  Table : Test
  Ajouter un
champ→Nom (je laisse integer)
  Ok pour valider
la création de la table
  Sélection de la
table puis, Modifier une table
  Quand on clique
que le menu déroulant du type→ segmentation fault
  
  
  Par avance merci
pour vos réponses
  


  

sqlitebrowser -> segmentation fault

[Fabrice Delvallée]

Bonjour


J’ignore si c’est la bonne méthode, mais je suis persuadé que vous 
pourrez m’auguiller.



J’utilise « sqlitebrowser » dans une buster à jour. ( DB Browser pour 
SQLite version 3.10.1.)



Sur plusieurs machines différentes celui-ci plante « segmentation fault» 
lorsqu’on essaye de modifier une table et changer le type d’un champ



Détail des manipulations :


Nouvelle base de données

Table : Test

Ajouter un champ→Nom (je laisse integer)

Ok pour valider la création de la table

Sélection de la table puis, Modifier une table

Quand on clique que le menu déroulant du type→ segmentation fault


Par avance merci pour vos réponses

a little bit off-topic (Was: Re: Python 3 Segmentation Fault)

[황병희]

Cindy Sue Causey  writes:

> Mine's Python 3.8.5 on Bullseye..

Howdy, Cindy^^^
*Because* i like very so much Bullseye^^^ 

Sincerely, Byung-Hee from South Korea

-- 
^고맙습니다 _白衣從軍_ 감사합니다_^))//

Re: Python 3 Segmentation Fault

[황병희]

Dear Arun,

"J.Arun Mani"  writes:

> Hello.
> I'm using Debian Testing (upgraded from Debian 10). Today I started Python 3, 
> but it was not able to interpret any
> commands from stdin and resulted in Segmentation Fault. Luckily
> modules (python3 -m ) and files ...

Just i guess because you are in Debian *Testing*. Many people say Testing
is always dangerous. So you would be try to Debian stable or Ubuntu LTS?

Sincerely, Byung-Hee (my python3 is 3.6.9 in Ubuntu 18.04 LTS)

-- 
^고맙습니다 _白衣從軍_ 감사합니다_^))//

Re: [Python-Help] Python 3 Segmentation Fault

[J.Arun Mani]

Hello all.

I found a crazy fix to this issue. Running Python in Isolation mode raises no 
problem ! That is, you need to run Python like this:
 $ python3 -I

So having the isolation mode fix the issue, what next step shall I take to make 
the fix permanent (I mean tweak or look at which modules, binaries etc.) ?

Thanks
J Arun Mani

Re: Python 3 Segmentation Fault

[Cindy Sue Causey]

On 8/4/20, J.Arun Mani  wrote:
> Hello.
> I'm using Debian Testing (upgraded from Debian 10). Today I started Python
> 3, but it was not able to interpret any commands from stdin and resulted in
> Segmentation Fault. Luckily modules (python3 -m ) and files (python3
> ) works fine though.
>
> Observed:
> $ python3
> Python 3.8.3rc1 (default, Apr 30 2020, 07:33:30)
> [GCC 9.3.0] on linux
> Type "help", "copyright", "credits" or "license" for more information.
>>>> print
> 
> 
> Segmentation fault


Hi... A C(omputer)C(opy) was sent to that help@python address for
informational purposes. If it bounces, that's cool, but I'll be
checking that out, too. Appreciate the lead there. :)

So I get this while attempting your path above:

 BEGIN TEST +++
$ python3
Python 3.8.5 (default, Jul 20 2020, 18:32:44)
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> print

 END TEST 

Mine's Python 3.8.5 on Bullseye.. I STARTED TO ASK: Did you run
something similar to "apt-get update" before reinstalling?

But in addition to that: Did you also try
installing/reinstalling/upgrading Python3.8? It took a few seconds of
nosing around to figure out that's where *my* "Python 3.8.5" came from
(and NOT from e.g. Python3 nor Python):

 BEGIN APT-CACHE POLICY 
$ apt-cache policy python3.8
python3.8:
  Installed: 3.8.5-1
  Candidate: 3.8.5-1
  Version table:
 *** 3.8.5-1 500
500 http://deb.debian.org/debian bullseye/main amd64 Packages
100 /var/lib/dpkg/status
 END APT-CACHE POLICY 

N.B. as an aside: There's a Debian-Python list out there:

https://lists.debian.org/debian-python/

Debian-Python's description is:

"Discussion of issues related to Python on Debian systems with a
stress on packaging standards. Therefore relevant for maintainers of
Python related packages."

It's for Developer types who are either creating or maintaining
Debian's Python-based packages. They're VERY helpful when inquiries
contain all the pertinent details necessary to work through issues.

Cindy :)

PS #ThankYou! You just helped me a little, too. I'm messing around
with something that's having GTK issues... and there is... a list for
that, too! Score!

https://lists.debian.org/completeindex.html

-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with birdseed.. && yet another shiny new deboostrap... *

Re: Python 3 Segmentation Fault

[Kushal Kumaran]

"J.Arun Mani"  writes:

> Hello.
> I'm using Debian Testing (upgraded from Debian 10). Today I started
> Python 3, but it was not able to interpret any commands from stdin and
> resulted in Segmentation Fault. Luckily modules (python3 -m )
> and files (python3 ) works fine though.
>
> Observed:
> $ python3
> Python 3.8.3rc1 (default, Apr 30 2020, 07:33:30)

Where did you get this from?
https://tracker.debian.org/pkg/python3-defaults says testing has version
3.8.2-3.

The output of the command "apt policy python3" and looking at your
sources.list and /etc/apt/sources.list.d/* will help.

> [GCC 9.3.0] on linux
> Type "help", "copyright", "credits" or "license" for more information.
>>>> print
> 
> 
> Segmentation fault
>
> Screen capture that could help :
> https://www.dropbox.com/s/9w941t93ymem1x1/python3_issue-2020-08-04_19.38.28.mp4?dl=0
>
> Some additional info:
> 1. I tried running a file that takes input from user (using input
> function), it also didn't work. So I think something regarding
> standard input has broken.
> 2. Python 2 also has the exact, same issue. So both Pythons face the problem !
>
> I have IPython installed, which works fine without any issue.
> The very recent installations I made :
> Installed Emacs (~ 2 days ago)
> Installed and removed Neovim (~ 1 day ago)
>
> I tried reinstalling Python by : sudo apt reinstall python3
> But it didn't fix the issue.
>
> Though I hardly use live session of Python 3 (I use IPython for live
> sessions), having a broken Python 3 scares me. Any help regarding the
> issue is greatly appreciated. :)
>
> Thanks
> J Arun Mani

Python 3 Segmentation Fault

[J.Arun Mani]

Hello.
I'm using Debian Testing (upgraded from Debian 10). Today I started Python 3, 
but it was not able to interpret any commands from stdin and resulted in 
Segmentation Fault. Luckily modules (python3 -m ) and files (python3 
) works fine though.

Observed:
$ python3
Python 3.8.3rc1 (default, Apr 30 2020, 07:33:30)
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> print


Segmentation fault

Screen capture that could help : 
https://www.dropbox.com/s/9w941t93ymem1x1/python3_issue-2020-08-04_19.38.28.mp4?dl=0

Some additional info:
1. I tried running a file that takes input from user (using input function), it 
also didn't work. So I think something regarding standard input has broken.
2. Python 2 also has the exact, same issue. So both Pythons face the problem !

I have IPython installed, which works fine without any issue.
The very recent installations I made :
Installed Emacs (~ 2 days ago)
Installed and removed Neovim (~ 1 day ago)

I tried reinstalling Python by : sudo apt reinstall python3
But it didn't fix the issue.

Though I hardly use live session of Python 3 (I use IPython for live sessions), 
having a broken Python 3 scares me. Any help regarding the issue is greatly 
appreciated. :)

Thanks
J Arun Mani

Re: Buster: klavaro crashes with segmentation fault?

[local10]

Jan 23, 2019, 9:36 AM by a...@cityscape.co.uk:

> Doesn't crash here.
>

Thanks. 

Filed a bug report, looks like there may be a patch soon, for more info see 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920179 

Re: Buster: klavaro crashes with segmentation fault?

[Brian]

On Wed 23 Jan 2019 at 05:00:40 +0100, local10 wrote:

> Jan 22, 2019, 6:51 PM by delop...@gmail.com:
> 
> > install gdb and run it through - do backtrace - it will tell you more.
> >
> > it is gtk app - could be also you are missing something gtk or have wrong
> > dependencies
> >
> 
> Can anyone running Buster install klavaro app and see if it crashes in
> your setup? It's a small app, shouldn't take more than a couple of
> minutes to test. Thanks

Doesn't crash here.

-- 
Brian.

Re: Buster: klavaro crashes with segmentation fault?

[local10]

Jan 22, 2019, 6:51 PM by delop...@gmail.com:

> install gdb and run it through - do backtrace - it will tell you more.
>
> it is gtk app - could be also you are missing something gtk or have wrong
> dependencies
>

Can anyone running Buster install klavaro app and see if it crashes in your 
setup? It's a small app, shouldn't take more than a couple of minutes to test. 
Thanks

Re: Buster: klavaro crashes with segmentation fault?

[deloptes]

local10 wrote:

> I normally use KDE launcher to start Klavaro, the command prompt output
> below was just for test purposes to see what could be wrong.

install gdb and run it through - do backtrace - it will tell you more.

it is gtk app - could be also you are missing something gtk or have wrong
dependencies

not using kalvaro (I can already type :) )

regards

Buster: klavaro crashes with segmentation fault?

[local10]

Package: klavaro   
Version: 3.03-1

Hi,

Anyone else having this issue? Klavaro is crashing for me with a segmentation 
fault when I try to start it in Buster. Tried running 'export 
LC_ALL="en_US.UTF-8"' before starting Klavaro, it removed the "Locale not 
supported by C library" message (see below) but still resulted in the 
segmentation fault.

I normally use KDE launcher to start Klavaro, the command prompt output below 
was just for test purposes to see what could be wrong.

Thanks


$ klavaro

(process:18844): Gtk-WARNING **: 06:04:48.155: Locale not supported by C 
library.
    Using the fallback 'C' locale.
Segmentation fault


$ locale -a
C
C.UTF-8
en_US.utf8
POSIX



$ locale
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME=en_GB.UTF-8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

Apache Segmentation Fault

[H.]

Hi,

I have a web server running Testing with apache 2.4.37 and php 7.3. The
purpose of the server is to run owncloud. However, after the nightly
restart the server stops working. The logs show the following:

/var/log/apache2/error.log.1
[Fri Nov 23 00:00:01.526101 2018] [mpm_prefork:notice] [pid 2858]
AH00171: Graceful restart requested, doing restart

/var/log/apache2/error.log
[Fri Nov 23 00:00:01.622137 2018] [mpm_prefork:notice] [pid 2858]
AH00163: Apache/2.4.37 (Debian) OpenSSL/1.1.1 configured -- resuming
normal operations
[Fri Nov 23 00:00:01.622156 2018] [core:notice] [pid 2858] AH00094:
Command line: '/usr/sbin/apache2'
[Fri Nov 23 00:00:01.626193 2018] [core:notice] [pid 2858] AH00052:
child pid 5383 exit signal Segmentation fault (11)
[Fri Nov 23 00:00:01.626217 2018] [core:notice] [pid 2858] AH00052:
child pid 5384 exit signal Segmentation fault (11)
[Fri Nov 23 00:00:01.626222 2018] [core:notice] [pid 2858] AH00052:
child pid 5385 exit signal Segmentation fault (11)
[Fri Nov 23 00:00:01.626227 2018] [core:notice] [pid 2858] AH00052:
child pid 5386 exit signal Segmentation fault (11)

These segmentation faults keep going so that the error.log file grows
to hundreds of MB within a few hours.

When I do "service apache2 restart" the server works properly again
until the next nightly restart.

Any idea what could cause this problem?

Package versions:
libapache2-mod-php7.3/testing,now 7.3.0~rc4-1 amd64
php-apcu/testing,now 5.1.12+4.0.11-2 amd64
php-redis/testing,now 4.2.0~rc2-1 amd64
php7.3-opcache/testing,now 7.3.0~rc4-1 amd64
certbot/testing,now 0.28.0-1 all

First I had the opcache enabled in /etc/php/7.3/apache2/php.ini, but
then I disabled it since many people reported issues with opcache
causing segfaults. However, the problem still persists. I also tried to
switch the memcache setting of owncloud from APCu to Redis, but also no
effect. Owncloud's cron.php is executed via www-data's crontab.

I also ran "certbot renew", but it does nothing because the server's
certificate is still valid and thus the server keeps running.

Best regards,
Dino

Re: Segmentation fault in top -b1 -hc

[Curt]

On 2017-05-09, Bob McGowan  wrote:
>>
> I just tried the OP's command line and got the following error:
>
> $ top -b1 -hc
>   procps-ng 3.3.12
> Usage:
>   top -hv | -bcHiOSs -d secs -n max -u|U user -p pid(s) -o field -w [cols]
>
> I can say with assurance that I have not manually installed anything
> related to procps or top.
>
> And the policy for procps says:
>
> $ apt-cache policy procps  
> procps:
>   Installed: 2:3.3.12-3
>   Candidate: 2:3.3.12-3
>   Version table:
>
> Those version numbers match the numeric part of the 'top' output.
>
> Could it be that Debian has just dropped the '-ng' from the name?
>

I'm reading that in 2011 Debian, Fedora and openSUSE forked procps (which became
'procps-ng'-- next generation). I guess the package has gone back to being
called procps (or something)?

https://gitlab.com/procps-ng/procps/wikis/faq



-- 
"It might be a vision--of a shell, of a wheelbarrow, of a fairy kingdom on the
far side of the hedge; or it might be the glory of speed; no one knew." --Mrs.
Ramsay, speculating on why her little daughter might be dashing about, in "To
the Lighthouse," by Virginia Woolf.

Re: Segmentation fault in top -b1 -hc

[Bob McGowan]

On 05/08/2017 03:28 AM, to...@tuxteam.de wrote:
> On Mon, May 08, 2017 at 11:46:13AM +0200, Peter Ludikovsky wrote:
> > On 05/08/2017 11:19 AM, Valentin Bajrami wrote:
> >> Hi,
> >>
> >> There is a segmentation fault when top is used as follow
> >>
> >> top -b1 -hc
> >>
> >> I think the args are not parsed properly.  The version used is:
> >> procps-ng version 3.3.10
> >>
> >> --
> >> Met vriendelijke groet,
> >>
> >> Valentin Bajrami
>
> > There's no package procps-ng [0].
>
> Indeed. There seems to be one props-ng floating around, but it doesn't
> come from Debian's official repos.
>
> To find out where that package comes from, try
>
>   apt-cache policy procps-ng-3.3.10
>
> (or however that package is really called, you can find that out
> with "aptitude search procps-ng" or something similar).
>
> HTH
> -- tomás
>
I just tried the OP's command line and got the following error:

$ top -b1 -hc
  procps-ng 3.3.12
Usage:
  top -hv | -bcHiOSs -d secs -n max -u|U user -p pid(s) -o field -w [cols]

I can say with assurance that I have not manually installed anything
related to procps or top.

And the policy for procps says:

$ apt-cache policy procps  
procps:
  Installed: 2:3.3.12-3
  Candidate: 2:3.3.12-3
  Version table:

Those version numbers match the numeric part of the 'top' output.

Could it be that Debian has just dropped the '-ng' from the name?

Bob

Re: Segmentation fault in top -b1 -hc

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, May 08, 2017 at 11:46:13AM +0200, Peter Ludikovsky wrote:
> On 05/08/2017 11:19 AM, Valentin Bajrami wrote:
> > Hi,
> > 
> > There is a segmentation fault when top is used as follow
> > 
> > top -b1 -hc
> > 
> > I think the args are not parsed properly.  The version used is:
> > procps-ng version 3.3.10
> > 
> > -- 
> > Met vriendelijke groet,
> > 
> > Valentin Bajrami
> 
> There's no package procps-ng [0].

Indeed. There seems to be one props-ng floating around, but it doesn't
come from Debian's official repos.

To find out where that package comes from, try

  apt-cache policy procps-ng-3.3.10

(or however that package is really called, you can find that out
with "aptitude search procps-ng" or something similar).

HTH
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlkQSFkACgkQBcgs9XrR2kbX3gCfXDWfXzu0pWvamzNf/zhrB+oy
FRoAnArOJblkZjkgdcqayi4spPSu6uMq
=V0kt
-END PGP SIGNATURE-

Re: Segmentation fault in top -b1 -hc

[Peter Ludikovsky]

On 05/08/2017 11:19 AM, Valentin Bajrami wrote:
> Hi,
> 
> There is a segmentation fault when top is used as follow
> 
> top -b1 -hc
> 
> I think the args are not parsed properly.  The version used is:
> procps-ng version 3.3.10
> 
> -- 
> Met vriendelijke groet,
> 
> Valentin Bajrami

There's no package procps-ng [0].

procps is version 3.3.9 in Stable, and 3.3.12 in Testing/Unstable [1].
Update to the current version, and if the problem persists please report
the issue via the reportbug [2][3] utility.

Regards
/peter

[0] https://packages.debian.org/search?keywords=procps-ng
[1] https://packages.debian.org/search?keywords=procps
[2] https://wiki.debian.org/reportbug
[3] https://www.debian.org/Bugs/Reporting



signature.asc
Description: OpenPGP digital signature

Segmentation fault in top -b1 -hc

[Valentin Bajrami]

Hi,

There is a segmentation fault when top is used as follow

top -b1 -hc

I think the args are not parsed properly.  The version used is: procps-ng
version 3.3.10

-- 
Met vriendelijke groet,

Valentin Bajrami

Résolu Re: Caja segmentation fault

[Raphaël POITEVIN]

J’ai vidé le home de ses fichiers cachés et ça remarche.

Cordialement,
-- 
Raphaël
Hypra S.A.S.

Re: Caja segmentation fault

[igor80]

Bonjour,

Il y a un bug très similaire

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823192

caja crashes on debian jessie mate (not opening again after system reboot)

Un début de solution lié au répertoire .config/

Cordialement, 

--
igor

Re: Caja segmentation fault

[Bernard Schoenacker]

Le Fri, 03 Jun 2016 15:09:45 +0200,
raphael.poite...@gmail.com (Raphaël POITEVIN) a écrit :

> Bonjour,
> 
> Debian Jessie, Mate + Compiz
> 
> Quand on ouvre depuis le bureau le dossier personnel, caja se crash.
> Il en va de même pour le poste de travail.
> 
> J’ai relevé ce log noyau :
> Jun  2 16:03:25 hypra-chiesa kernel: [ 1156.458518] caja[2785]:
> segfault at 0 ip 7f449ec2fd8e sp 7fffabe1f9a8 error 4 in
> libc-2.19.so[7f449eb9e000+1a2000]
> 
> Apparemment survenu subitement. L’utilisateur n’a rien fait de
> spécial. En tous cas, rien en root, il n’en a pas les compétences.
> 
> Quelqu’un a-t-il déjà connu cette situation ?
> 
> En vous remerciant,
> 
> Cordialement,

bonjour,

en faisant quelques recherche sur caja avec cette expression :

Caja segmentation fault

j'ai trouvé ceci :

https://github.com/mate-desktop/caja/issues/487
https://forums.insynchq.com/t/caja-segmentation-fault-on-debian/2651

résultat: le paquet est débogué sur linuxmint à partir de la version
1.12 (debian stable 1.8.x)

et par acquis de conscience j'ai employé rmadison (paquet devscripts)

rmadison -a amd64 caja
caja   | 1.8.1-2~bpo70+1 | wheezy-backports | amd64
caja   | 1.8.2-3+deb8u1  | stable   | amd64
caja   | 1.14.1-1| testing  | amd64
caja   | 1.14.1-1| unstable | amd64


étant donné la fraîcheur des paquets il serait très sage de passer en
testing ou sid pour le poste de travail 


slt
bernard

Re: Caja segmentation fault

[Raphaël POITEVIN]

Frédéric MASSOT  writes:
> Caja est à jour ?

C’est une install fraîche de 3 semaines.
>
> Pour Jessie c'est la version : 1.8.2-3+deb8u1

j’ai oublié de vérifier mais de toutes façon je pense que c’est à jour.
>
> J'ai eu le cas sur un poste de travail lors de l'accès à la corbeille,
> je ne me souviens plus de la version de Caja, il y avait un fichier qui
> faisait planter la génération des miniatures. J'ai vidé la corbeille
> avec un "rm".

Là le pb c’est que même le poste de travail plante. Pour info, oublié de
préciser que le pb du poste de travail est survenu après le pb de
l’accès aux dossiers personnels. Au début, on arrivait à accéder au
poste de travail, on pouvait constater que ça plantait lorsqu’on entrait
dans la racine où que l’on tentait d’accéder directement à ~/.

Cordialement,
-- 
Raphaël
Hypra S.A.S.

Re : Re: Caja segmentation fault

[MENGUAL Jean-Philippe]

Tu as tenté de vider le home, ou du moins le .config, et de retester?



Jean-Philippe MENGUAL

HYPRA, progressons ensemble

Tél.: 01 84 73 06 61

Mail: cont...@hypra.fr

Site Web: http://www.hypra.fr

- Raphaël POITEVIN  a écrit :
> Salut camarade,
> Jérémy Prégo  writes:
> > un aptitude ou apt-get reinstall libc6 ne résou-t-il pas le soucis ?
> 
> Merci pour la suggestion ; malheureusement ça ne résoud pas.
> -- 
> Raphaël
> Hypra S.A.S.
> 

Re: Caja segmentation fault

[Raphaël POITEVIN]

Salut camarade,
Jérémy Prégo  writes:
> un aptitude ou apt-get reinstall libc6 ne résou-t-il pas le soucis ?

Merci pour la suggestion ; malheureusement ça ne résoud pas.
-- 
Raphaël
Hypra S.A.S.

Re: Caja segmentation fault

[Frédéric MASSOT]

Le 03/06/2016 15:09, Raphaël POITEVIN a écrit :
> Bonjour,
> 
> Debian Jessie, Mate + Compiz
> 
> Quand on ouvre depuis le bureau le dossier personnel, caja se crash. Il
> en va de même pour le poste de travail.
> 
> J’ai relevé ce log noyau :
> Jun  2 16:03:25 hypra-chiesa kernel: [ 1156.458518] caja[2785]: segfault
> at 0 ip 7f449ec2fd8e sp 7fffabe1f9a8 error 4 in
> libc-2.19.so[7f449eb9e000+1a2000]
> 
> Apparemment survenu subitement. L’utilisateur n’a rien fait de
> spécial. En tous cas, rien en root, il n’en a pas les compétences.
> 
> Quelqu’un a-t-il déjà connu cette situation ?

Caja est à jour ?

Pour Jessie c'est la version : 1.8.2-3+deb8u1

J'ai eu le cas sur un poste de travail lors de l'accès à la corbeille,
je ne me souviens plus de la version de Caja, il y avait un fichier qui
faisait planter la génération des miniatures. J'ai vidé la corbeille
avec un "rm".


Pour info, MATE 1.14 est arrivé aujourd'hui dans testing.

-- 
==
|  FRÉDÉRIC MASSOT   |
| http://www.juliana-multimedia.com  |
|   mailto:frede...@juliana-multimedia.com   |
| +33.(0)2.97.54.77.94  +33.(0)6.67.19.95.69 |
===Debian=GNU/Linux===

Re: Caja segmentation fault

[Jérémy Prégo]

bonjour,

un aptitude ou apt-get reinstall libc6 ne résou-t-il pas le soucis ?

lorsque cela m'arrive, je réinstalle le paquet associé au .so, et 
généralement, ça fonctionne ...


jerem

Le 03/06/2016 15:09, Raphaël POITEVIN a écrit :

Bonjour,

Debian Jessie, Mate + Compiz

Quand on ouvre depuis le bureau le dossier personnel, caja se crash. Il
en va de même pour le poste de travail.

J’ai relevé ce log noyau :
Jun  2 16:03:25 hypra-chiesa kernel: [ 1156.458518] caja[2785]: segfault
at 0 ip 7f449ec2fd8e sp 7fffabe1f9a8 error 4 in
libc-2.19.so[7f449eb9e000+1a2000]

Apparemment survenu subitement. L’utilisateur n’a rien fait de
spécial. En tous cas, rien en root, il n’en a pas les compétences.

Quelqu’un a-t-il déjà connu cette situation ?

En vous remerciant,

Cordialement,

Caja segmentation fault

[Raphaël POITEVIN]

Bonjour,

Debian Jessie, Mate + Compiz

Quand on ouvre depuis le bureau le dossier personnel, caja se crash. Il
en va de même pour le poste de travail.

J’ai relevé ce log noyau :
Jun  2 16:03:25 hypra-chiesa kernel: [ 1156.458518] caja[2785]: segfault
at 0 ip 7f449ec2fd8e sp 7fffabe1f9a8 error 4 in
libc-2.19.so[7f449eb9e000+1a2000]

Apparemment survenu subitement. L’utilisateur n’a rien fait de
spécial. En tous cas, rien en root, il n’en a pas les compétences.

Quelqu’un a-t-il déjà connu cette situation ?

En vous remerciant,

Cordialement,
-- 
Raphaël
Hypra S.A.S.

segmentation fault when playing videos

[Christian Hödl]

Hi,
  playing videos in debian jessie leads to seg faults on my machine (fresh 
installation, 
  vlc and xine output attached).
  According to gdb it looks like there could be some problem in libavutil:
vlc
gdb -c core vlc
Reading symbols from vlc...(no debugging symbols found)...done.
[New LWP 3498]
[New LWP 3483]
[New LWP 3492]
[New LWP 3484]
[New LWP 3494]
[New LWP 3495]
[New LWP 3496]
[New LWP 3497]
[New LWP 3488]
[New LWP 3499]
[New LWP 3491]
[New LWP 3485]
[New LWP 3489]
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
Core was generated by `vlc -vvv 
/mnt/data/mediathek/Concert/Concert-Monty_Python_s_Flying_Circus_-_Sex'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f1726489743 in av_freep () from 
/usr/lib/x86_64-linux-gnu/libavutil.so.54
(gdb) bt
#0  0x7f1726489743 in av_freep () from 
/usr/lib/x86_64-linux-gnu/libavutil.so.54
#1  0x7f172647ee6a in av_dict_free () from 
/usr/lib/x86_64-linux-gnu/libavutil.so.54
#2  0x7f1726483832 in av_frame_unref () from 
/usr/lib/x86_64-linux-gnu/libavutil.so.54
#3  0x7f1726acecb3 in avcodec_decode_video2 () from 
/usr/lib/x86_64-linux-gnu/libavcodec.so.56
#4  0x7f172762a19d in ?? () from 
/usr/lib/vlc/plugins/codec/libavcodec_plugin.so
#5  0x7f175c2fbaff in ?? () from /usr/lib/libvlccore.so.8
#6  0x7f175c2fd3da in ?? () from /usr/lib/libvlccore.so.8
#7  0x7f175cb740a4 in start_thread (arg=0x7f1740109700) at 
pthread_create.c:309
#8  0x7f175c6a504d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111
 
xine
gdb -c core xine
GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
http://gnu.org/licenses/gpl.html[https://3c.gmx.net/mail/client/dereferrer?redirectUrl=http%3A%2F%2Fgnu.org%2Flicenses%2Fgpl.html]
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
Type show configuration for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/[https://3c.gmx.net/mail/client/dereferrer?redirectUrl=http%3A%2F%2Fwww.gnu.org%2Fsoftware%2Fgdb%2Fbugs%2F].
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/[https://3c.gmx.net/mail/client/dereferrer?redirectUrl=http%3A%2F%2Fwww.gnu.org%2Fsoftware%2Fgdb%2Fdocumentation%2F].
For help, type help.
Type apropos word to search for commands related to word...
Reading symbols from xine...(no debugging symbols found)...done.
[New LWP 3544]
[New LWP 3545]
[New LWP 3549]
[New LWP 3550]
[New LWP 3548]
[New LWP 3537]
[New LWP 3546]
[New LWP 3543]
[New LWP 3539]
[New LWP 3554]
[New LWP 3542]
[New LWP 3536]
[New LWP 3547]
[New LWP 3551]
[New LWP 3552]
[New LWP 3553]
[New LWP 3538]
[New LWP 3540]
[New LWP 3541]
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
Core was generated by `xine --verbose 
/mnt/data/mediathek/Concert/Concert-Monty_Python_s_Flying_Circus'.
Program terminated with signal SIGABRT, Aborted.
#0  0x7f79cd291107 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:56
56    ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  0x7f79cd291107 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x7f79cd2924e8 in __GI_abort () at abort.c:89
#2  0x7f79cd2cf204 in __libc_message (do_abort=do_abort@entry=1, 
fmt=fmt@entry=0x7f79cd3c1fe0 *** Error in `%s': %s: 0x%s ***\n) at 
../sysdeps/posix/libc_fatal.c:175
#3  0x7f79cd2d49de in malloc_printerr (action=1, str=0x7f79cd3be09e 
free(): invalid pointer, ptr=optimized out) at malloc.c:4996
#4  0x7f79cd2d56e6 in _int_free (av=optimized out, p=optimized out, 
have_lock=0) at malloc.c:3840
#5  0x7f79cc50d60d in av_buffer_unref () from 
/usr/lib/x86_64-linux-gnu/libavutil.so.54
#6  0x7f79cc51783e in av_frame_unref () from 
/usr/lib/x86_64-linux-gnu/libavutil.so.54
#7  0x7f79c44c8cb3 in avcodec_decode_video2 () from 
/usr/lib/x86_64-linux-gnu/libavcodec.so.56
#8  0x7f798d9fdbdf in ?? () from 
/usr/lib/xine/plugins/2.5/xineplug_decode_ff.so
#9  0x7f79cf5b6e55 in ?? () from /usr/lib/libxine.so.2
#10 0x7f79cd8150a4 in start_thread (arg=0x7f79b3a0f700) at 
pthread_create.c:309
#11 0x7f79cd34204d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111
 
Because with wheezy I could play all kinds of video files I would be interested 
in any clues what could
be the problem. Playing dvd's doesn't work, too (gdb dump looks similar).
 
Best Regards,
  Christian

vlc_trace
Description: Binary data


xine_trace
Description: Binary data

Re: segmentation fault when playing videos

[Thomas Schmitt]

Hi,

Christian Hödl wrote:
 [...] vlc [...]
 Program terminated with signal SIGSEGV, Segmentation fault.
 #0  0x7f1726489743 in av_freep () from 
 /usr/lib/x86_64-linux-gnu/libavutil.so.54
 [...] xine [...]
 Program terminated with signal SIGABRT, Aborted.
 #0  0x7f79cd291107 in __GI_raise (sig=sig@entry=6) at
 ../nptl/sysdeps/unix/sysv/linux/raise.c:56
 56    ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.

Both look like (software) memory corruption.
Usually caused by writing over the limits of an allocated
piece of memory or by de-allocating allocated memory twice.

The culprit is often hard to find because the memory management
might need quite some time until it is rotten enough to crash.


 #0  0x7f79cd291107 in __GI_raise (sig=sig@entry=6) at 
 ../nptl/sysdeps/unix/sysv/linux/raise.c:56
 #1  0x7f79cd2924e8 in __GI_abort () at abort.c:89
 #2  0x7f79cd2cf204 in __libc_message (do_abort=do_abort@entry=1,
 fmt=fmt@entry=0x7f79cd3c1fe0 *** Error in `%s': %s: 0x%s ***\n) at
 ../sysdeps/posix/libc_fatal.c:175

Underneath xine, libc seems to have noticed the problem
before it lead to a crash. I guess it issued a message 
and then deliberately threw signal 6 = SIGABRT (man 7 signal).


A standard tool to catch the culprit is valgrind.
Often awfully slow. So it might produce its own problems with
video display.
Nevertheless it might find the first memory abuse which starts
the whole mess.

  valgrind xine ...xine.options... 21 | tee -i /tmp/valgrind_xine.log

In any case the output will be useful if you file a bug report.


Have a nice day :)

Thomas

Re: useradd segmentation fault

[Joris Bolsens]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Sorry about late reply, got a bit busy with other things.

On 11/07/2014 11:43 PM, Reco wrote:
 Hi.
 
 I'd try adding some memory (or swapspace) to this VM to satisfy
 mremap's wish to remap to exactly 8G virtual memory.
 
 Reco

Tried this, set the VMs memory to 8gb and still get the segfault, the
strace and core dumb look pretty identical to before.

Also still not sure why I don't have the debug symbol things for the
ldap lib, tried a few more times to install it to no avail.

- -Joris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJUYpWUAAoJEORnMHMHY2Fro8wQALSgyakp9fXsP063F51s3av4
3kc698UvCW8Qy1TY/CfsstOhiOPaLUjtJIKNwzc7YaFi8NhzsZcJzTeikFGWSpKg
TfxDlEv9kJQWQiKxKY4RLzW6ZXKqPJjFoN1ob/rY3hdy/OoNUD1rGApzallwptZ/
pAx0my0g7edZQwD5sbtKfo3unSTWD8j3XDJF0N0BwxqsT6HncpIAtbiNQ+PJpfm4
gQRnJYd/ZQ8aGb9CpxqrtAAbf4dAqVBYmRa4jl+2crRKFL9DX+se83OimDQzJk6C
DlEPIxPk5vRNtKbqYfYLc8G4YBPYVY1q3OoBlizvEQvgLkpamoWp07smg4TjRqWo
tsp6b2ORkpmCxDeH8W6Lt+uhrkszQm3g6WWKPJbbMQpoaytg3rLdI0e9n20axzgo
RAa0XyD26xHWdAK0IjnzQjrjllplkbx/seRo3d0b0NudNZKy/yQIJvdw19UA2GoE
c7d+AYgBcA3ulY+LUc4hNnfyNqtuzALJWiQ/kO0V9plOkGd/1Smn546iBBxxCC7q
P3LWqP72HfX4VA1i+/+7TQL3i9/HegnvA5h+HVmRSU38bYYiKKdKKZh+DC1unBaW
dTov6Q04N9iEo4bZdBla+UhDkV3awpwfJ1v4s8JO6Eircly0btIrrqnq2euC7dTL
yUpIjET51WlRtOD+oUla
=0htc
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54629597.4060...@linux.com

Re: useradd segmentation fault

[Joris Bolsens]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



On 11/08/2014 03:43 PM, Don Armstrong wrote:

 No, just don't send the whole core dump itself (the file called
 core) to the BTS (or this mailing list). It almost certainly has
 your machine ldap password in it.
that makes sense, wont do that, thanks.

 You should at least have the symbols for libnss-ldap... can you
 check the output of nm -a for that library to make sure it actually
 has the debugging symbols?
Where do i find the object file for libnss-ldap? I tried running nm -a
on pretty much every file I could find with libnss-ldap in the name
and it said it didn't recognize the file type.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJUX87bAAoJEORnMHMHY2Frkv4QAI8i1wfJfKh3LCuxeDDvnmmU
0WgtVSdJTgV+AfuFAq7Ud5/FHeHDAh2gxP3g3x6A4VMAKL7om9Zqu2uO+OkjJuXk
m0Fq9BULBA6iaPvutfZ6YlvSG6OsMwS/U80W1++4B3GtQBGW2lOboj3z6r4vP9R3
Dba8hzvDJA5oiapgNagh30jIIl/Vs8Q4Ak/cs4aVssZMaM8LVIVFf7OZT3YikfSq
8K2mksTfscGMdlhZxVNeN5lgIq/17/noZ1ieYAQRvXcRTGGsKhXLVeOVqsuyHUFz
uvx2+y0LURCKJmPtsSnKVIQAzBqS3KOro3QvrIALMTIyzi3iCKHjxlGnIhXVpje8
vMJNAezeQU1xluxBm/TrYBoo4Xrakc5uDYIzsiZGoOpperxeL5qh8RwntnR+7pTa
zfv5sKOg4H0hWO4pizuqxS476rQiNjMXpyJzwSZX304lDp/DjoEgl+PFzN+X1CRj
nZBRR26rPH/46GBZwTDyxs1MWh1DpKrNQAsladGQe/RgLHZmHqVgAknrfvwwuGay
FU8DMCcam4UsjeBti96RyY4VNysaiTIXZw/jTqBld9j6ixNqH7pX2Jxau/gvl2YB
Whpad+z4TVDw+A4CTY7jBiAuIMcX6UX7gF1XUp4knSNvM6OsjIWgVmPwxFr0u3pf
TjqIWdT7sXkvhEGI6y5Z
=3N+u
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/545fcede.6000...@gmail.com

Re: useradd segmentation fault

[Don Armstrong]

On Sun, 09 Nov 2014, Joris Bolsens wrote:
 Where do i find the object file for libnss-ldap? I tried running nm -a
 on pretty much every file I could find with libnss-ldap in the name
 and it said it didn't recognize the file type.

It should be symlinked from /lib64/libnss_ldap.so.2 or
/lib/x86_64-linux-gnu/ and nm -Da or similar should do it.


-- 
Don Armstrong  http://www.donarmstrong.com

There is no such thing as social gambling. Either you are there to
cut the other bloke's heart out and eat it--or you're a sucker. If you
don't like this choice--don't gamble.
 -- Robert Heinlein _Time Enough For Love_ p250


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141109205516.gf29...@teltox.donarmstrong.com

Re: useradd segmentation fault

[Joris Bolsens]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



On 11/09/2014 12:55 PM, Don Armstrong wrote:
 On Sun, 09 Nov 2014, Joris Bolsens wrote:
 Where do i find the object file for libnss-ldap? I tried running
  nm -a on pretty much every file I could find with libnss-ldap in
  the name and it said it didn't recognize the file type.
 
 It should be symlinked from /lib64/libnss_ldap.so.2 or 
 /lib/x86_64-linux-gnu/ and nm -Da or similar should do it.
 
Thanks, found it. here is the output,

# nm -Da libnss_ldap.so.2
34d8 t .init
 A EXPORTED
 w _ITM_deregisterTMCloneTable
 w _ITM_registerTMCloneTable
 w _Jv_RegisterClasses
 U __assert_fail
 U __ctype_b_loc
 w __cxa_finalize
 U __dn_expand
 U __errno_location
 U __fxstat
 w __gmon_start__
 w __pthread_mutex_lock
 w __pthread_mutex_unlock
 U __register_atfork
 U __res_init
 U __res_search
 U __res_state
 U __snprintf_chk
 U __stack_chk_fail
 U __stpcpy_chk
 U __strdup
 U __syslog_chk
 U __xstat
b010 T _nss_ldap_endaliasent
d380 T _nss_ldap_endautomntent
cdc0 T _nss_ldap_endetherent
9810 T _nss_ldap_endgrent
a450 T _nss_ldap_endhostent
a860 T _nss_ldap_endnetent
9af0 T _nss_ldap_endnetgrent
aac0 T _nss_ldap_endprotoent
8210 T _nss_ldap_endpwent
9f80 T _nss_ldap_endrpcent
b480 T _nss_ldap_endservent
ae90 T _nss_ldap_endspent
afa0 T _nss_ldap_getaliasbyname_r
b040 T _nss_ldap_getaliasent_r
d3b0 T _nss_ldap_getautomntbyname_r
d250 T _nss_ldap_getautomntent_r
cdf0 T _nss_ldap_getetherent_r
9840 T _nss_ldap_getgrent_r
9780 T _nss_ldap_getgrgid_r
9710 T _nss_ldap_getgrnam_r
a350 T _nss_ldap_gethostbyaddr_r
a270 T _nss_ldap_gethostbyname2_r
a320 T _nss_ldap_gethostbyname_r
a480 T _nss_ldap_gethostent_r
ccb0 T _nss_ldap_gethostton_r
a680 T _nss_ldap_getnetbyaddr_r
a5f0 T _nss_ldap_getnetbyname_r
a890 T _nss_ldap_getnetent_r
9c10 T _nss_ldap_getnetgrent_r
cd00 T _nss_ldap_getntohost_r
aa00 T _nss_ldap_getprotobyname_r
aa50 T _nss_ldap_getprotobynumber_r
aaf0 T _nss_ldap_getprotoent_r
8240 T _nss_ldap_getpwent_r
8150 T _nss_ldap_getpwnam_r
81a0 T _nss_ldap_getpwuid_r
9ec0 T _nss_ldap_getrpcbyname_r
9f10 T _nss_ldap_getrpcbynumber_r
9fb0 T _nss_ldap_getrpcent_r
b350 T _nss_ldap_getservbyname_r
b3d0 T _nss_ldap_getservbyport_r
b4b0 T _nss_ldap_getservent_r
aec0 T _nss_ldap_getspent_r
ae20 T _nss_ldap_getspnam_r
96e0 T _nss_ldap_initgroups
9400 T _nss_ldap_initgroups_dyn
aff0 T _nss_ldap_setaliasent
d1e0 T _nss_ldap_setautomntent
cda0 T _nss_ldap_setetherent
97f0 T _nss_ldap_setgrent
a430 T _nss_ldap_sethostent
a840 T _nss_ldap_setnetent
9b40 T _nss_ldap_setnetgrent
aaa0 T _nss_ldap_setprotoent
81f0 T _nss_ldap_setpwent
9f60 T _nss_ldap_setrpcent
b460 T _nss_ldap_setservent
ae70 T _nss_ldap_setspent
 U access
 U ber_bvfree
 U ber_free
 U ber_pvt_opt_on
 U ber_set_option
 U calloc
 U close
 U dup
 U dup2
 U ether_aton
 U ether_ntoa
 U fclose
 U fcntl
 U fgets
 U fileno
 U fopen
 U free
 U geteuid
 U getpeername
 U getpid
 U getsockname
 U gss_krb5_ccache_name
 U inet_addr
 U inet_makeaddr
 U inet_network
 U inet_ntoa
 U ldap_abandon
 U ldap_control_free
 U ldap_controls_free
 U ldap_count_entries
 U ldap_count_values
 U ldap_create_page_control
 U ldap_err2string
 U ldap_explode_dn
 U ldap_explode_rdn
 U ldap_first_attribute
 U ldap_first_entry
 U ldap_get_dn
 U ldap_get_option
 U ldap_get_values
  

Re: useradd segmentation fault

[Joris Bolsens]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



On 11/07/2014 11:43 PM, Reco wrote:

 
 So, chances are - you've found a bug.
 
Awesome, where/how should I report it?


 
 and memory info on top:
 
 KiB Mem:   2061128 total,   263680 used,  1797448 free,75180
 buffers KiB Swap:  2094076 total,0 used,  2094076 free,
 118000 cached
 
 I'd try adding some memory (or swapspace) to this VM to satisfy
 mremap's wish to remap to exactly 8G virtual memory.
 

I'll give that a go and reply back,

machine is in use right now so cant mess with memory, but will try asap.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJUXdwcAAoJEORnMHMHY2FrjEkP+QHkFC7KwuCMZoKpOGLAIqiv
o1b7TsWisfunlBux8s7la9ipsbWZJ9lGy2rfSPuEGv/u5XGjiIODSRnXMD+H/DHq
TQv7EQsdNPqEakcCL8XRTmFEkHQTy5Vb6Jjxt/bgusAcbYa/doItk0aVp56yqHY2
nTa6G8dr6/QkPDfGz4Gbby6xRdlMeHvEbtjix7vCA4fFW9bntE7O8/2SLR7RuCY2
6xM0zDNEfvznGPb5FFB4EVRBsJRzMXpcPDD0AHmIttMMSk1ZrXYbQEabxHDNQr8h
1R6IUsYUGRV+nVuPorYxeGzmNv2MJFRgSFwBGBS9+JHahoXf0L7fSyeqqVuRfIqy
qaY6sUHv+b4drf0djKtY/69HWYmRF9st5b2ZgTdRj5nTp9PtqVZEchAjhNM9lF5V
8EReauywy6xa6fqSZMnz8Yf1FhzpTqGv0I50gmHF4p9oPcHJ7Dr06DBTcSsGPio0
I54bfrXxZ9NEu+NtdSbkLCUnBwzLrtQoyJexkzj+eon/MST2uUZxX4/i2OLOPZ61
1GXtTok5JdR/G8y0GphsqM6VJJqUWQrHRvMNpVkyD7ddldWmUHAiq+WovSP5o11w
vGSEw3KCheIn6d0gP2vw9/RW7n+ZzFTwKPBiKdvzrBtlRhUNxm48d7mECuij7aGh
MdlZg++FFBbvHZ3KCzNE
=Sn9q
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/545ddc21.5030...@linux.com

Re: useradd segmentation fault

[Reco]

 Hi.

On Sat, 08 Nov 2014 01:02:25 -0800
Joris Bolsens jo...@linux.com wrote:

  
  So, chances are - you've found a bug.
  
 Awesome, where/how should I report it?

Install reportbug package. Invoke 'reportbug passwd'.
The rest of the process will be explained to you by the reportbug.

Reportbug requires sending specially-crafted e-mail to
sub...@bugs.debian.org, so you may want to produce such e-mail with
reportbug, and send it by hand to that address.

Reco


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20141108122101.8583d128c28636c13b972...@gmail.com

Re: useradd segmentation fault

[Don Armstrong]

On Fri, 07 Nov 2014, Joris Bolsens wrote:
 Ran into a bit of a strange error with useradd today, whenever i run
 useradd I get a Segmentation fault.

Before filing a bug, please

1) Enable coredumps
2) Get a coredump
3) Backtrace it
4) Install any missing -dbg packages which provide symbols for the bits
which are segfaulting

If you are still missing the appropriate symbols for useradd, please
rebuild it with DEB_BUILD_OPTS=nostrip, and try again.

-- 
Don Armstrong  http://www.donarmstrong.com

With one simple pill
we cured unhappiness
and art
 -- a softer world #437
http://www.asofterworld.com/index.php?id=437


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141108173937.gs29...@teltox.donarmstrong.com

Re: useradd segmentation fault

[Joris Bolsens]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Sorry, pretty new to linux still. put a few questions in-line.


On 11/08/2014 09:39 AM, Don Armstrong wrote:

 Before filing a bug, please
 
 1) Enable coredumps
Did some googling, I have to recompile the kernel for this?
the one thing i did find on how to do it without was for the fedora
kernel.

 2) Get a coredump 3) Backtrace it
Not sure how to do this, or what I would be looking for here.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJUXmXyAAoJEORnMHMHY2FrK68P/Azq1Bu+NHmB1rK8c3DAJIhW
rNHdbA+S+6J1dcgYVCLB+SSldUR+14z6N5hUzgm86LjyCeKaYrpcTF+wxJJ3gvvn
CP6Bbk/V7sAK56/4OwVYBu+DYWTVJnm6dOGVO03+vUFWXPjkQUmIopabq6IV6zNb
hjyTCOEUBpUUrfDoowiny/U5GuBG6vit77ukaAhrlAjTk0nDZM2seHG+Ueh78gRf
s8XUeSG9KAoaB5dq3i1VzvKENcImiRzzkNY2WNSZwX0oodlUGD9+i6iVwka8o9cX
kjDIagVAc6sZQBeOShc+YSgQ7kwwROpz8uc6IqPuC4ZMH8zpZe8xjsatLIEDBVNJ
pdEXjG8EBs4ZI11pi4/NyHsMdm31pySxPcikY1BJw7qyJYhBXXw+hBveFCbKGqD7
KDAyDUwXov+Kv81uvb0phLgYv2PuSuiGhQkGlq/6HWPsXlrHbAShSIFwg7NUZbbm
wEMJksILjaP8pe9oX9O8/vozJQ1LUd/yOPkio9PnEyHDUl6CYjVEsBWvEAcAEpRq
OCpL+GW5vT2eoZ+Ut16WxSgboQcPhOxpxviRheM4S9AMJp4m7aF45q624gdQj/Et
QzLnbJEgc23Ccnh08WJIfr0e59jFeABhkMuXBDbey75M2q8RNhqU7cpnMec4p+47
47U1Wdgjgdcf0Xcw/T1e
=r/PK
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/545e65f8.6060...@gmail.com

Re: useradd segmentation fault

[Don Armstrong]

On Sat, 08 Nov 2014, Joris Bolsens wrote:
 Sorry, pretty new to linux still. put a few questions in-line.

No worries.
 
 On 11/08/2014 09:39 AM, Don Armstrong wrote:
 
  Before filing a bug, please
  
  1) Enable coredumps
 Did some googling, I have to recompile the kernel for this?
 the one thing i did find on how to do it without was for the fedora
 kernel.

Nah. All you have to do is something like the following:

ulimit -c unlimited;
useradd foo;
gdb /usr/sbin/useradd core;
bt full;

or similar.

You'll also want to install libc6-dbg gdb; and similar.

This will give you an idea of where the code is segfaulting, and whether
it's in a library which useradd is calling, or something else entirely.

If the backtrace doesn't look at all useful, something like:

apt-get build-dep passwd;
DEB_BUILD_OPTS=nostrip,noopt apt-get source -b passwd;

should in theory give you a passwd .deb file with debugging symbols and
no optimization which you can then install to give you a more useful
backtrace.

You also might start by just reinstalling passwd in case there was some
corruption somewhere to make sure you can replicate the segfault.

-- 
Don Armstrong  http://www.donarmstrong.com

I finally developed
a computer with feelings.
It just doesn't have
feelings for me.
 -- a softer world #633
http://www.asofterworld.com/index.php?id=633


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141108191639.gv29...@teltox.donarmstrong.com

Re: useradd segmentation fault

[Joris Bolsens]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



On 11/08/2014 11:16 AM, Don Armstrong wrote:

 ulimit -c unlimited; useradd foo; gdb /usr/sbin/useradd core; bt
 full; or similar.
 
 You'll also want to install libc6-dbg gdb; and similar.
 
 This will give you an idea of where the code is segfaulting, and
 whether it's in a library which useradd is calling, or something
 else entirely.
 
 If the backtrace doesn't look at all useful, something like:
 
 apt-get build-dep passwd; DEB_BUILD_OPTS=nostrip,noopt apt-get
 source -b passwd;
 
 should in theory give you a passwd .deb file with debugging symbols
 and no optimization which you can then install to give you a more
 useful backtrace.
 
 You also might start by just reinstalling passwd in case there was
 some corruption somewhere to make sure you can replicate the
 segfault.
 


Awesome, ill give all this a go and also maybe try settings its ram to
8gb and update with what happens.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJUXm2zAAoJEORnMHMHY2FrZgAQAJWST7FWrcHKkkpCEAg7NSHQ
dHaE6ASyDuIY3iMtyGSrVRogHC9C0rooL0tEaUekynJcG5MH96XaWZoDAIZ0APpb
fBfFigvRZF+LLFsU4N4CG9GvPsSX5MIFGP9zqme51j22IUCqVUedS25D4Rd4qLeV
qa0GvA4xStk/d3pCKsVOIt8tC302PV5OcFuvfzrVBPKRRxUweXAP4wiQupb9UzVr
iXdqlc1UtFaOUhvu6KGC0iF7VzLBn6hZnRPxUBQmzgphCkPGpRSxv4zdVG/s13VR
Zapi2kOxtTqarpBtxG95Krp+E1lzlO70xOrOqjbUhGnBAzc1d4jW8PP8WhDmSzH7
MYmPpmLF7cWlIBwvsf0TOO+NL7Xk0yvl2p9bf6GnDsw5sstu/B7k3ISWgtybsvCD
5Ys4OzteYzM2ekfmKFmGuT8nZG03fjOdM8Wtn+XFg75/Vbdbp58ZECGdzYTTcFeB
+AKkb7PHznu99I32djg7ICWQRGdFhe4EWB3W/Qo4u2AYcZgEn2jn+8Lz+agytTLh
Zcf+2jvZoabT8VhCqYhuBi6peDLsZsV2k4GBR+/CFevYGD48s26b1+cAJgB0/dWp
OJwAW5nSXTpIlXS21axZkyTkEF+mzPhBuNL6WJBOq5i1J/9fTFGQt5/L2wv/Olyj
YD7hsadQ8qN5xBzO0GQd
=iKYV
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/545e6dba.5000...@linux.com

Re: useradd segmentation fault

[Joris Bolsens]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I can't be 100% certain because I'm not sure what any of this means,
but it would seem I messed up somewhere as it shows `No Symbol Table
info available` for libnss_ldap.

This bit also seems possibly problematic
`warning: Can't read pathname for load map: Input/output error.1`

# gdb /usr/sbin/useradd core
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/sbin/useradd...(no debugging symbols
found)...done.
[New LWP 9929]

warning: Can't read pathname for load map: Input/output error.
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
Core was generated by `useradd foo'.
Program terminated with signal 11, Segmentation fault.
#0  0x7f880fad5f0b in ?? () from
/lib/x86_64-linux-gnu/libnss_ldap.so.2
(gdb) bt full
#0  0x7f880fad5f0b in ?? () from
/lib/x86_64-linux-gnu/libnss_ldap.so.2
No symbol table info available.
#1  0x7f880fad3ef1 in ?? () from
/lib/x86_64-linux-gnu/libnss_ldap.so.2
No symbol table info available.
#2  0x7f880fad4a34 in ?? () from
/lib/x86_64-linux-gnu/libnss_ldap.so.2
No symbol table info available.
#3  0x7f880fad4bde in ?? () from
/lib/x86_64-linux-gnu/libnss_ldap.so.2
No symbol table info available.
#4  0x7f880fad6276 in _nss_ldap_getpwent_r () from
/lib/x86_64-linux-gnu/libnss_ldap.so.2
No symbol table info available.
#5  0x7f88108f1840 in __nss_getent_r
(getent_func_name=0x7f8810952156 getpwent_r,
setent_func_name=optimized out,
lookup_fct=0x7f88108f1ad0 *__GI___nss_passwd_lookup2,
nip=0x7f8810b8cd60, startp=optimized out, last_nip=optimized out,
stayopen_tmp=0x0, res=0, resbuf=0x7f8810b8cca0, buffer=0x0,
buflen=8589934592, result=0x7fffbff02008, h_errnop=0x0)
at getnssent_r.c:171
fct = {f = 0x7f880fad6240 _nss_ldap_getpwent_r, ptr =
0x7f880fad6240}
no_more = optimized out
status = 277813968
#6  0x7f88108af0a6 in __getpwent_r (resbuf=optimized out,
buffer=optimized out, buflen=optimized out, result=0x0)
at ../nss/getXXent_r.c:162
status = 0
save = 0
#7  0x7f88108f1463 in __nss_getent (func=0x7f88108af010
__getpwent_r, resbuf=0x7f8810b8cca0, buffer=0x7f8810b8ae18,
buflen=optimized out, buffer_size=0x7f8810b8ccd0, h_errnop=0x0)
at getnssent.c:38
result = optimized out
#8  0x7f88108aece2 in getpwent () at ../nss/getXXent.c:84
buffer_size = 8589934592
resbuf = {l = {pw_name = 0x7f860d33d012 Address
0x7f860d33d012 out of bounds, pw_passwd = 0x0, pw_uid = 628342823,
pw_gid = 3, pw_gecos = 0x1637b49 ¸\020\210\177,
pw_dir = 0x1637b50 0{c\001, pw_shell = 0x1637b5d },
  ptr = 0x7f860d33d012}
save = 0
#9  0x00408815 in ?? ()
No symbol table info available.
#10 0x004043e5 in ?? ()
No symbol table info available.
#11 0x7f8810822ead in __libc_start_main (main=optimized out,
argc=optimized out, ubp_av=optimized out,
init=optimized out, fini=optimized out, rtld_fini=optimized
out, stack_end=0x7fffbff023f8) at libc-start.c:244
result = optimized out
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0,
4098621885896654353, 4218724, 140736413574144, 0, 0,
- -4098762729259336175,
-4039416709317984751}, mask_was_saved = 0}}, priv =
{pad = {0x0, 0x0, 0x40ff50, 0x7fffbff02408}, data = {
  prev = 0x0, cleanup = 0x0, canceltype = 4259664}}}
not_first_call = optimized out
#12 0x00405f8d in ?? ()
No symbol table info available.
#13 0x7fffbff023f8 in ?? ()
No symbol table info available.
#14 0x001c in ?? ()
No symbol table info available.
#15 0x0002 in ?? ()
No symbol table info available.
#16 0x7fffbff02e90 in ?? ()
No symbol table info available.
#17 0x7fffbff02e98 in ?? ()
No symbol table info available.
#18 0x in ?? ()
No symbol table info available.
(gdb)
#0  0x7f880fad5f0b in ?? () from
/lib/x86_64-linux-gnu/libnss_ldap.so.2
No symbol table info available.
#1  0x7f880fad3ef1 in ?? () from
/lib/x86_64-linux-gnu/libnss_ldap.so.2
No symbol table info available.
#2  0x7f880fad4a34 in ?? () from
/lib/x86_64-linux-gnu/libnss_ldap.so.2
No symbol table info available.
#3  0x7f880fad4bde in ?? () from
/lib/x86_64-linux-gnu/libnss_ldap.so.2
No symbol table info available.
#4  0x7f880fad6276 in _nss_ldap_getpwent_r () from
/lib/x86_64-linux-gnu/libnss_ldap.so.2
No symbol table info available.
#5  0x7f88108f1840 in __nss_getent_r
(getent_func_name=0x7f8810952156 getpwent_r

Re: useradd segmentation fault

[Don Armstrong]

On Sat, 08 Nov 2014, Joris Bolsens wrote:
 I can't be 100% certain because I'm not sure what any of this means,
 but it would seem I messed up somewhere as it shows `No Symbol Table
 info available` for libnss_ldap.

Awesome. It looks like it's segfaulting in libnss_ldap, which you didn't
build symbols for (and unfortunately, they're not currently available).

apt-get build-dep libnss-ldap;
DEB_BUILD_OPTS=nostrip,noopt apt-get source -b libnss-ldap;

will give you those symbols. 

Then you can rerun /usr/sbin/useradd foo; and re-analyze the coredump.

Please double check the bt full; output for any obvious password strings
too before posting to this mailing list. [I should have told you to do
that too, but I don't see any below, so you should be OK.]
 
And also don't send the core file to the BTS either, unless you're going
to change your ldap machine passwords.


-- 
Don Armstrong  http://www.donarmstrong.com

The game of science is, in principle, without end. He who decides one
day that scientific statements do not call for any further test, and
that they can be regarded as finally verified, retires from the game.
 -- Sir Karl Popper _The Logic of Scientific Discovery_ §11


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141108201650.gx29...@teltox.donarmstrong.com

Re: useradd segmentation fault

[Joris Bolsens]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



On 11/08/2014 12:16 PM, Don Armstrong wrote:

 Please double check the bt full; output for any obvious password
 strings too before posting to this mailing list. [I should have
 told you to do that too, but I don't see any below, so you should
 be OK.]
Yea i did a quick read through to make sure no identifying information
was present before sending :p
 
 And also don't send the core file to the BTS either, unless you're
 going to change your ldap machine passwords.
Not sure what you mean by this, don't post the full output of the command?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJUXp6hAAoJEORnMHMHY2Frg54QAKhSRkfZuH+SNXXb4daaDJ8E
USRZirhICEnvtzeDu6Bz4BsCG6hX0Zv6PXufQvXQcqHodvbfWBBbOPjE2CDHlnhI
oKewZJdYcWTym9HYxwBN5Y/FG+gyNygiVsSBFja37P+LkpH6I52BdNSyIhTDkukX
1EgKbWntn+AVCQJoxpuZ0rNUbdO7YTsYkgo+CBA+1vg46H68AqJ8DGQ5KrYDWu/g
i0N5bS7j7SyZnO4L5jolWNeBXDW6vh/JIYa8uNc24jj8ndg4LmjJokH56jDFsA6C
mS4j69sWjaHcm84BuIi9mgzcB6feiWFP7M5qkj6LrzEUutjE+Tur85pPR0ZfDy4U
d5CgzVkrqAOh0qCPWQt6onozpoVjPXvT1V+KrwihSoNGkM2hebzNDOH+SljaYRO7
qO5FhWqeGj3nsNXe99yDeWAYzGXNToajTlOl9Z2DYYUF5ps3EAsqVFspMCskMrxZ
o7ItPu81IATdtNknGQ0yxubXCiGiw0cxbuEugdNaF6VLKoNAnPmA68laJOrty5T1
H4A9gsq6kBaAFUZLaU501jzmR3Z0quYgzV9A6b81jZNphr2f1GXtXzdai6jsJ6yk
yMDM6J+Ce7/oZXfYnMKDRrK7Bt6NrXd79NNSzucpF3YmavKg9bwTwKfKzQMHlp0R
Trv80S1QtZJkjaZJY2Eu
=sk4N
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/545e9ea4.3050...@gmail.com

Re: useradd segmentation fault

[Joris Bolsens]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



On 11/08/2014 12:16 PM, Don Armstrong wrote:

 apt-get build-dep libnss-ldap; DEB_BUILD_OPTS=nostrip,noopt
 apt-get source -b libnss-ldap;
 
 will give you those symbols.
 
 Then you can rerun /usr/sbin/useradd foo; and re-analyze the
 coredump.
The coredump looks identical to before i built/installed the new
libnss-ldap
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJUXqEhAAoJEORnMHMHY2FrDa0P/1OLykX1o9050yn1Lg/W6W3g
cTO6qQNF6big1tikRyjvJ4vubo1OYcuZyxVZxHL7SGMxX7S7ndzRpZWPmEgyg+nG
wj0GxZoVN8tJTREEaa5foIw4nSO9glPjM61gdCUKdHSnyBFy3Nq+c3asLhb8UGBY
o6OPshKbFL8C/bbK1AJvMVoi3tu7LmmPJLHfMefXun8Z4ENa4uO/xfrLL8dK2Wie
KzOAG3FpoKdTOAJ5uQdjM9pu8joTZq3/zWYfOyvQoImKZkdFb2whjFHDK1hu88Bf
UHxsf7pgMIyqt7qWEN9ExjEstiwTSqTJXkP2I731q/UAaHpJQUjAdqwpZVtwptd3
U/YTd8LVKExZBG/jY5VUasDZ++D7g08jzI61+B27+syFGFGh7mUZMvGj9LHzitqb
N5ckjk1ItlMPJr2YoJ8Jv8cTYrNw9KD7YuT/bKjd9zr89MIUcieX9JjVZndvWZQB
Nmeo/vE3KqnScGou6yxuS1YNgAZoGYSPHQg83MlgVRrrGFqaQOaBifwIgp12yJYz
p66stYt8eiZTJcgQ5VMOpgeo2zoiJpbi0S+mtv8RK2zVXeVDpMpTFqWd31Xo0S0m
cIKTzei0SJJ6NaNVXUa85jfaMupE0anANeL5ofg1i1CcMYhuJSIrHVJ9YYf4agL4
rMtBcSUWdeKd9xLZE9D1
=5Ry2
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/545ea123.9050...@gmail.com

Re: useradd segmentation fault

[Don Armstrong]

On Sat, 08 Nov 2014, Joris Bolsens wrote:
 Not sure what you mean by this, don't post the full output of the
 command?

No, just don't send the whole core dump itself (the file called core) to
the BTS (or this mailing list). It almost certainly has your machine
ldap password in it.

On Sat, 08 Nov 2014, Joris Bolsens wrote:
 The coredump looks identical to before i built/installed the new
 libnss-ldap

You should at least have the symbols for libnss-ldap... can you check
the output of nm -a for that library to make sure it actually has the
debugging symbols?


-- 
Don Armstrong  http://www.donarmstrong.com

Of course Pacman didn't influence us as kids. If it did, we'd be
running around in darkened rooms, popping pills and listening to
repetitive music.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141108234354.gz29...@teltox.donarmstrong.com

useradd segmentation fault

[Joris Bolsens]

Ran into a bit of a strange error with useradd today, 
whenever i run useradd I get a Segmentation fault.

I tried running fsck as i read it might be due to corrupt filesystem, but that 
didn't report any problems.
I reinstalled the passwd package, also to no avail.

I ran an strace and it seems it cannot allocate memory, which is strange as it 
is running as a vm on a machine with 32gb of ram, 
and is provisioned to use whatever it needs and has 2gb reserved to it, not to 
mention that top shows only a fraction of that being in use.

I recently added ldap integration if that matters at all, 
although none of the other VMs seem to be having issues with this 
(granted the others are running CentOs, this being the ldap server)

Output of strace:

rt_sigaction(SIGPIPE, {SIG_DFL, [], SA_RESTORER, 0x7f259c6461e0}, NULL, 8) = 0
rt_sigaction(SIGPIPE, {SIG_IGN, [], SA_RESTORER, 0x7f259c6461e0}, {SIG_DFL, [], 
SA_RESTORER, 0x7f259c6461e0}, 8) = 0
rt_sigaction(SIGPIPE, {SIG_DFL, [], SA_RESTORER, 0x7f259c6461e0}, NULL, 8) = 0
rt_sigaction(SIGPIPE, {SIG_IGN, [], SA_RESTORER, 0x7f259c6461e0}, {SIG_DFL, [], 
SA_RESTORER, 0x7f259c6461e0}, 8) = 0
rt_sigaction(SIGPIPE, {SIG_DFL, [], SA_RESTORER, 0x7f259c6461e0}, NULL, 8) = 0
rt_sigaction(SIGPIPE, {SIG_IGN, [], SA_RESTORER, 0x7f259c6461e0}, {SIG_DFL, [], 
SA_RESTORER, 0x7f259c6461e0}, 8) = 0
rt_sigaction(SIGPIPE, {SIG_DFL, [], SA_RESTORER, 0x7f259c6461e0}, NULL, 8) = 0
rt_sigaction(SIGPIPE, {SIG_IGN, [], SA_RESTORER, 0x7f259c6461e0}, {SIG_DFL, [], 
SA_RESTORER, 0x7f259c6461e0}, 8) = 0
rt_sigaction(SIGPIPE, {SIG_DFL, [], SA_RESTORER, 0x7f259c6461e0}, NULL, 8) = 0
rt_sigaction(SIGPIPE, {SIG_IGN, [], SA_RESTORER, 0x7f259c6461e0}, {SIG_DFL, [], 
SA_RESTORER, 0x7f259c6461e0}, 8) = 0
rt_sigaction(SIGPIPE, {SIG_DFL, [], SA_RESTORER, 0x7f259c6461e0}, NULL, 8) = 0
brk(0x2354000)  = 0x2354000
brk(0x234c000)  = 0x234c000
rt_sigaction(SIGPIPE, {SIG_IGN, [], SA_RESTORER, 0x7f259c6461e0}, {SIG_DFL, [], 
SA_RESTORER, 0x7f259c6461e0}, 8) = 0
rt_sigaction(SIGPIPE, {SIG_DFL, [], SA_RESTORER, 0x7f259c6461e0}, NULL, 8) = 0
rt_sigaction(SIGPIPE, {SIG_IGN, [], SA_RESTORER, 0x7f259c6461e0}, {SIG_DFL, [], 
SA_RESTORER, 0x7f259c6461e0}, 8) = 0
rt_sigaction(SIGPIPE, {SIG_DFL, [], SA_RESTORER, 0x7f259c6461e0}, NULL, 8) = 0
mmap(NULL, 266240, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f25990db000
brk(0x233c000)  = 0x233c000
rt_sigaction(SIGPIPE, {SIG_IGN, [], SA_RESTORER, 0x7f259c6461e0}, {SIG_DFL, [], 
SA_RESTORER, 0x7f259c6461e0}, 8) = 0
rt_sigaction(SIGPIPE, {SIG_DFL, [], SA_RESTORER, 0x7f259c6461e0}, NULL, 8) = 0
mremap(0x7f25990db000, 266240, 528384, MREMAP_MAYMOVE) = 0x7f259905a000
rt_sigaction(SIGPIPE, {SIG_IGN, [], SA_RESTORER, 0x7f259c6461e0}, {SIG_DFL, [], 
SA_RESTORER, 0x7f259c6461e0}, 8) = 0
rt_sigaction(SIGPIPE, {SIG_DFL, [], SA_RESTORER, 0x7f259c6461e0}, NULL, 8) = 0
mremap(0x7f259905a000, 528384, 1052672, MREMAP_MAYMOVE) = 0x7f2598f59000
rt_sigaction(SIGPIPE, {SIG_IGN, [], SA_RESTORER, 0x7f259c6461e0}, {SIG_DFL, [], 
SA_RESTORER, 0x7f259c6461e0}, 8) = 0
rt_sigaction(SIGPIPE, {SIG_DFL, [], SA_RESTORER, 0x7f259c6461e0}, NULL, 8) = 0
mremap(0x7f2598f59000, 1052672, 2101248, MREMAP_MAYMOVE) = 0x7f2598d58000
rt_sigaction(SIGPIPE, {SIG_IGN, [], SA_RESTORER, 0x7f259c6461e0}, {SIG_DFL, [], 
SA_RESTORER, 0x7f259c6461e0}, 8) = 0
rt_sigaction(SIGPIPE, {SIG_DFL, [], SA_RESTORER, 0x7f259c6461e0}, NULL, 8) = 0
mremap(0x7f2598d58000, 2101248, 4198400, MREMAP_MAYMOVE) = 0x7f2598957000
rt_sigaction(SIGPIPE, {SIG_IGN, [], SA_RESTORER, 0x7f259c6461e0}, {SIG_DFL, [], 
SA_RESTORER, 0x7f259c6461e0}, 8) = 0
rt_sigaction(SIGPIPE, {SIG_DFL, [], SA_RESTORER, 0x7f259c6461e0}, NULL, 8) = 0
mremap(0x7f2598957000, 4198400, 8392704, MREMAP_MAYMOVE) = 0x7f2598156000
rt_sigaction(SIGPIPE, {SIG_IGN, [], SA_RESTORER, 0x7f259c6461e0}, {SIG_DFL, [], 
SA_RESTORER, 0x7f259c6461e0}, 8) = 0
rt_sigaction(SIGPIPE, {SIG_DFL, [], SA_RESTORER, 0x7f259c6461e0}, NULL, 8) = 0
mremap(0x7f2598156000, 8392704, 16781312, MREMAP_MAYMOVE) = 0x7f2597155000
rt_sigaction(SIGPIPE, {SIG_IGN, [], SA_RESTORER, 0x7f259c6461e0}, {SIG_DFL, [], 
SA_RESTORER, 0x7f259c6461e0}, 8) = 0
rt_sigaction(SIGPIPE, {SIG_DFL, [], SA_RESTORER, 0x7f259c6461e0}, NULL, 8) = 0
mremap(0x7f2597155000, 16781312, 33558528, MREMAP_MAYMOVE) = 0x7f2595154000
rt_sigaction(SIGPIPE, {SIG_IGN, [], SA_RESTORER, 0x7f259c6461e0}, {SIG_DFL, [], 
SA_RESTORER, 0x7f259c6461e0}, 8) = 0
rt_sigaction(SIGPIPE, {SIG_DFL, [], SA_RESTORER, 0x7f259c6461e0}, NULL, 8) = 0
mremap(0x7f2595154000, 33558528, 67112960, MREMAP_MAYMOVE) = 0x7f2591153000
rt_sigaction(SIGPIPE, {SIG_IGN, [], SA_RESTORER, 0x7f259c6461e0}, {SIG_DFL, [], 
SA_RESTORER, 0x7f259c6461e0}, 8) = 0
rt_sigaction(SIGPIPE, {SIG_DFL, [], SA_RESTORER, 0x7f259c6461e0}, NULL, 8) = 0
mremap(0x7f2591153000, 67112960, 134221824, MREMAP_MAYMOVE) = 0x7f2589152000
rt_sigaction(SIGPIPE, {SIG_IGN, [], SA_RESTORER, 0x7f259c6461e0}, {SIG_DFL, [], 
SA_RESTORER

Re: useradd segmentation fault

[Joris Bolsens]

it seems that using the adduser works fine, not sure why i didn't think to try 
that before.
However I am still curious why this occurred.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/545d84dc.7050...@linux.com

Re: useradd segmentation fault

[Marty]

On 11/07/2014 09:04 PM, Joris Bolsens wrote:

Ran into a bit of a strange error with useradd today,
whenever i run useradd I get a Segmentation fault.

I tried running fsck as i read it might be due to corrupt filesystem, but that 
didn't report any problems.
I reinstalled the passwd package, also to no avail.

I ran an strace and it seems it cannot allocate memory, which is strange as it 
is running as a vm on a machine with 32gb of ram,
and is provisioned to use whatever it needs and has 2gb reserved to it, not to 
mention that top shows only a fraction of that being in use.

I recently added ldap integration if that matters at all,
although none of the other VMs seem to be having issues with this
(granted the others are running CentOs, this being the ldap server)

Output of strace:

rt_sigaction(SIGPIPE, {SIG_DFL, [], SA_RESTORER, 0x7f259c6461e0}, NULL, 8) = 0


No idea, but why are you using realtime (rt_*) system calls?



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/545d9b70.1060...@ix.netcom.com

Re: useradd segmentation fault

[Joris Bolsens]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

No idea, that's just what i got when I ran the command, I left out a
bit at the top that did the ldap lookups, that all looked find and
didn't want to include that as 1) dont think it's relevant and 2)
contains some sensitive data (usernames and such), do you think that
could have something to do with it?

On 11/07/2014 08:26 PM, Marty wrote:
 On 11/07/2014 09:04 PM, Joris Bolsens wrote:
 Ran into a bit of a strange error with useradd today, whenever i
 run useradd I get a Segmentation fault.
 
 I tried running fsck as i read it might be due to corrupt
 filesystem, but that didn't report any problems. I reinstalled
 the passwd package, also to no avail.
 
 I ran an strace and it seems it cannot allocate memory, which is 
 strange as it is running as a vm on a machine with 32gb of ram, 
 and is provisioned to use whatever it needs and has 2gb reserved
 to it, not to mention that top shows only a fraction of that
 being in use.
 
 I recently added ldap integration if that matters at all, 
 although none of the other VMs seem to be having issues with
 this (granted the others are running CentOs, this being the ldap
 server)
 
 Output of strace:
 
 rt_sigaction(SIGPIPE, {SIG_DFL, [], SA_RESTORER,
 0x7f259c6461e0}, NULL, 8) = 0
 
 No idea, but why are you using realtime (rt_*) system calls?
 
 
 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJUXZwnAAoJEORnMHMHY2FrZKsP/i3vOnWrDuqb8JKPEuQF7Iyh
fJbmca1Y/Tqc3YFoZAkJ4+tqeZfe5XmMTL3m1AhkW/YxkaSOduKFaRcdjMV8DZQG
0thZ3EsNziXvVRTpBelj+9i4mYjkuS9ghc5gsRRN74R7ICAT4gX3Ifm+63+yK1h/
4PmBGafweXCpxxLoyA/KNkbdtGjvAVGXECGnelRDAtXl/7OR7/CSL0TBRYmiMJN9
NoqN+x6CJQ9wDGr+HTjlPTbC9VmYr0lCGajbt57xrFccWsEUpGOZ71zr2Y549sFM
uH4atUjPobIQtjZd/sFgoggqi4dTgGiwvPbVFvGWfckXuZnc8fLHI1g9C3g/nJnQ
auYmwOmr08QmoYqdmWq4IcSU1CWZ0IpGbvIXgCbXAOGQxX1OJlGMIFmNtVNyxRcC
36xxEFlJswr5Q5ClPcI/OsbyVyj84zT45B8omkOlma/MQRDQwsXdQXjt5IZRF1Fq
LhTbqBSWWRRPzrtmHF/CijDXCm076LLX802eLIRr0OAYVpnJoytVhGDWKMhd8rIZ
RG0gBjzeBmyOA1+KsVanCyRylc6KlosybLaq7y342JCS2S7CLIofkKwrL31oD994
IMIUgKwKz/QPwANhivEGFMYmaN5gE4kO7Ci8jrtKRDy3EyLUGFXspm2/bFvwWwT0
rG0gSoLWIoUUszy1R9ig
=9URa
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/545d9c2b.3060...@linux.com

Re: useradd segmentation fault

[Marty]

On 11/07/2014 11:29 PM, Joris Bolsens wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

No idea, that's just what i got when I ran the command, I left out a
bit at the top that did the ldap lookups, that all looked find and
didn't want to include that as 1) dont think it's relevant and 2)
contains some sensitive data (usernames and such), do you think that
could have something to do with it?


Well I think yes if that's what you are doing, Linux realtime support is 
still experimental



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/545da752.3040...@ix.netcom.com

Re: useradd segmentation fault

[Reco]

 Hi.

On Fri, 07 Nov 2014 18:04:25 -0800
Joris Bolsens jo...@linux.com wrote:

skip
 mremap(0x7f239914d000, 4294971392, 8589938688, MREMAP_MAYMOVE) = -1 EFAULT 
 (Bad address)

It goes downhill from here. Apparently useradd does not checks a return
status of mremap, and, according to the mremap(2), EFAULT is defined as:

EFAULT Segmentation fault. Some address in the range old_address to
old_address+old_size is an invalid  virtual  memory address for this
process.  You can also get EFAULT even if there exist mappings that
cover the whole address space requested, but those mappings are of
different types.


So, chances are - you've found a bug.


 and memory info on top:
 
 KiB Mem:   2061128 total,   263680 used,  1797448 free,75180 buffers
 KiB Swap:  2094076 total,0 used,  2094076 free,   118000 cached

I'd try adding some memory (or swapspace) to this VM to satisfy mremap's
wish to remap to exactly 8G virtual memory.


 and another interesting not, groupadd works fine, but groupdel also gives a 
 segmentation fault.
 # groupadd testgrp
 # groupdel testgrp
 Segmentation fault

And groupdel fails at the same

 output of strace on groupdel:
 mremap(0x7f7f71f1c000, 4294971392, 8589938688, MREMAP_MAYMOVE) = -1 EFAULT 
 (Bad address)

Reco


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20141108104313.fa2a07ed7b979d9b0d829...@gmail.com

Re: XServer Segmentation Fault

[Vangelis Mouhtsis]

Στις 2014-03-22 07:10, John Proios έγραψε:

Παλιά είχε να κάνει με τον driver της nvidia
αν αυτός ήταν ο official.
 Αν έκανες αναβάθμιση τον kernel και
έχεις τέτοιο driver δοκίμασε να
ξανακάνεις εγκατάσταση τον driver.

 Στις 03/21/2014 07:04 PM, ο/η Nick Zarkadas έγραψε:


Γεια σας
Μετά την τελευταία αναβάθμιση όλα
έγιναν  μαύρα.
Το γραφικό περιβάλλον (kde) δεν
εμφανίζεται και τη θέση
του έχει πάρει μια μαύρη οθόνη.
Οι τελευταίες γραμμές του Xorg.0.log
είναι οι ακόλουθες:
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb777999f]
(EE) 1: /usr/bin/X (0xb75d2000+0x1ab774) [0xb777d774]
(EE) 2: linux-gate.so.1 (__kernel_rt_sigreturn+0x0) [0xb75b040c]
(EE) 3: /usr/lib/xorg/modules/linux/libglx.so (0xb5be9000+0x1203d5)
[0xb5d093d5]
(EE) 4: /lib/i386-linux-gnu/i686/cmov/libc.so.6
(__libc_start_main+0xf3) [0xb70e2a63]
(EE)
(EE) Segmentation fault at address 0x0
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)
(EE)

Το PC μου τρέχει Debian  testing και λίγο
unstable.
Η κάρτα γραφικών είναι η nvidia FX5200.
(Είναι λίγο παλιό αλλά τη δουλεια του
την κάνει)
Έχεις κανείς καμιά ιδέα για το πως
διορθώνεται το πρόβλημα;;
Ευχαριστώ.


Εάν υπάρχει xorg.conf πρέπει να το αφαιρέσεις απο /etc/X11/xorg.conf
Μετά δες εαν έχεις εγκαταστήσει τα linux-headers.
Ο καλύτερος τρόπος ειναι: apt-get install module-assistant και στη
συνέχεια m-a update και m-a prepare.
Οταν τελειώσεις με αυτά, apt-get install nvidia-detect
Με αυτό το εργαλείο θα ανιχνεύσεις ποιόν ακριβώς nvidia driver
χρειάζεσαι. Για κάθε άλλη πληροφορία έλα στο #debian-gr on
irc.oftc.net
--
pub:   2048R/4DD72410
Key fingerprint:  A5BC 4190 DB4F E4F8 E1C2  CE15 59B2 3691 4DD7 2410


--
To UNSUBSCRIBE, email to debian-user-greek-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/7753afe38ad623ffd630394e9ab04...@gnugr.org

Re: XServer Segmentation Fault

[Dimitris Anogiatis]

Δες αν εχει αναβαθμιστει ο driver της NVidia που χρησιμοποιεις.
Ο τελευταιος official driver με υποστήρηξη για την FX 5200 συμφωνα
παντα με το site της NVidia ειναι ο 173xx

Αν το πακετο με τους drivers της NVidia αναβαθμήστικε στο τελευταιο
update τοτε δοκιμασε να φορτωσεις το nvidia-legacy-173xx-driver που
ειναι μεταπακετο και θα ξανακατεβασει ολα τα υπολοιπα dependencies.

Aν οι drivers δεν εχουν αλλάξει τότε κοιτα μην υπάρχουν αλλαγες σε αλλα
πακετα (πχ libc6) που μπορει να σου πεταει το segfault.

Ελπίζω να βοήθησα (και να μην σε μπερδεψα παραπανω).


2014-03-22 3:19 GMT-06:00 Vangelis Mouhtsis vange...@gnugr.org:

 Στις 2014-03-22 07:10, John Proios έγραψε:

  Παλιά είχε να κάνει με τον driver της nvidia
 αν αυτός ήταν ο official.
  Αν έκανες αναβάθμιση τον kernel και
 έχεις τέτοιο driver δοκίμασε να
 ξανακάνεις εγκατάσταση τον driver.

  Στις 03/21/2014 07:04 PM, ο/η Nick Zarkadas έγραψε:

  Γεια σας
 Μετά την τελευταία αναβάθμιση όλα
 έγιναν  μαύρα.
 Το γραφικό περιβάλλον (kde) δεν
 εμφανίζεται και τη θέση
 του έχει πάρει μια μαύρη οθόνη.
 Οι τελευταίες γραμμές του Xorg.0.log
 είναι οι ακόλουθες:
 (EE)
 (EE) Backtrace:
 (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb777999f]
 (EE) 1: /usr/bin/X (0xb75d2000+0x1ab774) [0xb777d774]
 (EE) 2: linux-gate.so.1 (__kernel_rt_sigreturn+0x0) [0xb75b040c]
 (EE) 3: /usr/lib/xorg/modules/linux/libglx.so (0xb5be9000+0x1203d5)
 [0xb5d093d5]
 (EE) 4: /lib/i386-linux-gnu/i686/cmov/libc.so.6
 (__libc_start_main+0xf3) [0xb70e2a63]
 (EE)
 (EE) Segmentation fault at address 0x0
 (EE)
 Fatal server error:
 (EE) Caught signal 11 (Segmentation fault). Server aborting
 (EE)
 (EE)

 Το PC μου τρέχει Debian  testing και λίγο
 unstable.
 Η κάρτα γραφικών είναι η nvidia FX5200.
 (Είναι λίγο παλιό αλλά τη δουλεια του
 την κάνει)
 Έχεις κανείς καμιά ιδέα για το πως
 διορθώνεται το πρόβλημα;;
 Ευχαριστώ.


 Εάν υπάρχει xorg.conf πρέπει να το αφαιρέσεις απο /etc/X11/xorg.conf
 Μετά δες εαν έχεις εγκαταστήσει τα linux-headers.
 Ο καλύτερος τρόπος ειναι: apt-get install module-assistant και στη
 συνέχεια m-a update και m-a prepare.
 Οταν τελειώσεις με αυτά, apt-get install nvidia-detect
 Με αυτό το εργαλείο θα ανιχνεύσεις ποιόν ακριβώς nvidia driver
 χρειάζεσαι. Για κάθε άλλη πληροφορία έλα στο #debian-gr on
 irc.oftc.net
 --
 pub:   2048R/4DD72410
 Key fingerprint:  A5BC 4190 DB4F E4F8 E1C2  CE15 59B2 3691 4DD7 2410


 --
 To UNSUBSCRIBE, email to debian-user-greek-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive: https://lists.debian.org/7753afe38ad623ffd630394e9ab04b
 4...@gnugr.org

Re: XServer Segmentation Fault

[Thanos Ad.]

Εφόσον χρησιμοποιείς τους κλειστούς drivers, για να δημιουργηθεί ξανά το
xorg.conf θα πρέπει να ξανατρέξεις nvidia-xconfig.


Στις 22 Μαρτίου 2014 - 3:50 μ.μ., ο χρήστης Nick Zarkadas 
nzark...@gmail.com έγραψε:

  Επανεγκατέστησα τους drivers της nvidia αλλά τίποτα δεν άλλαξε.
 Διέγραψα το xorg.conf αλλά μου βγάζει το μήνυμα  : EE no screens found.
 Θυμάμαι ότι όταν εγκατέστησα το Debian τη τελευταία φορά, δεν υπήρχε
 xorg.conf στο /etc/X11 και ότι ο Χ λειτουργούσε και χωρίς .conf.
 Αυτό το έφτιαξα με το nvidia-xconfig για να χρησιμοποιήσω τον επίσημο
 driver της nvidia και όχι τον nv. Εδώ νομίζω ότι κάτι μου διαφεύγει. Αφού
 λοιπόν διέγραψα το
 xorg.conf τ.ωρα πρέπει να φτιάξω καινούργιο ή να κάνω κάποια άλλη ενέργεια;

 Αυρίο (μάλλον) θα δοκιμάσω να κάνω debug στον X σύμφωνα με τις οδηγίες
 του http://www.x.org/wiki/Development/Documentation/ServerDebugging/.
 Αν καταφέρω να πάρω κανένα log θα το στείλω να μου πείτε τη γνώμη σας.
 Σας ευχαριστώ
 On 03/22/14 14:41, Dimitris Anogiatis wrote:

  Δες αν εχει αναβαθμιστει ο driver της NVidia που χρησιμοποιεις.
  Ο τελευταιος official driver με υποστήρηξη για την FX 5200 συμφωνα
 παντα με το site της NVidia ειναι ο 173xx

  Αν το πακετο με τους drivers της NVidia αναβαθμήστικε στο τελευταιο
 update τοτε δοκιμασε να φορτωσεις το nvidia-legacy-173xx-driver που
 ειναι μεταπακετο και θα ξανακατεβασει ολα τα υπολοιπα dependencies.

  Aν οι drivers δεν εχουν αλλάξει τότε κοιτα μην υπάρχουν αλλαγες σε αλλα
 πακετα (πχ libc6) που μπορει να σου πεταει το segfault.

  Ελπίζω να βοήθησα (και να μην σε μπερδεψα παραπανω).


 2014-03-22 3:19 GMT-06:00 Vangelis Mouhtsis vange...@gnugr.org:

 Στις 2014-03-22 07:10, John Proios έγραψε:

  Παλιά είχε να κάνει με τον driver της nvidia
 αν αυτός ήταν ο official.
  Αν έκανες αναβάθμιση τον kernel και
 έχεις τέτοιο driver δοκίμασε να
 ξανακάνεις εγκατάσταση τον driver.

  Στις 03/21/2014 07:04 PM, ο/η Nick Zarkadas έγραψε:

  Γεια σας
 Μετά την τελευταία αναβάθμιση όλα
 έγιναν  μαύρα.
 Το γραφικό περιβάλλον (kde) δεν
 εμφανίζεται και τη θέση
 του έχει πάρει μια μαύρη οθόνη.
 Οι τελευταίες γραμμές του Xorg.0.log
 είναι οι ακόλουθες:
 (EE)
 (EE) Backtrace:
 (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb777999f]
 (EE) 1: /usr/bin/X (0xb75d2000+0x1ab774) [0xb777d774]
 (EE) 2: linux-gate.so.1 (__kernel_rt_sigreturn+0x0) [0xb75b040c]
 (EE) 3: /usr/lib/xorg/modules/linux/libglx.so (0xb5be9000+0x1203d5)
 [0xb5d093d5]
 (EE) 4: /lib/i386-linux-gnu/i686/cmov/libc.so.6
 (__libc_start_main+0xf3) [0xb70e2a63]
 (EE)
 (EE) Segmentation fault at address 0x0
 (EE)
 Fatal server error:
 (EE) Caught signal 11 (Segmentation fault). Server aborting
 (EE)
 (EE)

 Το PC μου τρέχει Debian  testing και λίγο
 unstable.
 Η κάρτα γραφικών είναι η nvidia FX5200.
 (Είναι λίγο παλιό αλλά τη δουλεια του
 την κάνει)
 Έχεις κανείς καμιά ιδέα για το πως
 διορθώνεται το πρόβλημα;;
 Ευχαριστώ.


  Εάν υπάρχει xorg.conf πρέπει να το αφαιρέσεις απο /etc/X11/xorg.conf
 Μετά δες εαν έχεις εγκαταστήσει τα linux-headers.
 Ο καλύτερος τρόπος ειναι: apt-get install module-assistant και στη
 συνέχεια m-a update και m-a prepare.
 Οταν τελειώσεις με αυτά, apt-get install nvidia-detect
 Με αυτό το εργαλείο θα ανιχνεύσεις ποιόν ακριβώς nvidia driver
 χρειάζεσαι. Για κάθε άλλη πληροφορία έλα στο #debian-gr on
 irc.oftc.net
 --
 pub:   2048R/4DD72410
 Key fingerprint:  A5BC 4190 DB4F E4F8 E1C2  CE15 59B2 3691 4DD7 2410


 --
 To UNSUBSCRIBE, email to debian-user-greek-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive:
 https://lists.debian.org/7753afe38ad623ffd630394e9ab04...@gnugr.org

XServer Segmentation Fault

[Nick Zarkadas]

Γεια σας
Μετά την τελευταία αναβάθμιση όλα έγιναν  μαύρα.
Το γραφικό περιβάλλον (kde) δεν εμφανίζεται και τη θέση
του έχει πάρει μια μαύρη οθόνη.
Οι τελευταίες γραμμές του Xorg.0.log είναι οι ακόλουθες|:|
|(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb777999f]
(EE) 1: /usr/bin/X (0xb75d2000+0x1ab774) [0xb777d774]
(EE) 2: linux-gate.so.1 (__kernel_rt_sigreturn+0x0) [0xb75b040c]
(EE) 3: /usr/lib/xorg/modules/linux/libglx.so (0xb5be9000+0x1203d5) 
[0xb5d093d5]
(EE) 4: /lib/i386-linux-gnu/i686/cmov/libc.so.6 (__libc_start_main+0xf3) 
[0xb70e2a63]

(EE)
(EE) Segmentation fault at address 0x0
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)
(EE)


Το PC μου τρέχει Debian  testing και λίγο unstable.
Η κάρτα γραφικών είναι η nvidia FX5200. (Είναι λίγο παλιό αλλά τη 
δουλεια του την κάνει)

Έχεις κανείς καμιά ιδέα για το πως διορθώνεται το πρόβλημα;;
Ευχαριστώ.
|

Re: XServer Segmentation Fault

[John Proios]

Παλιά είχε να κάνει με τον driver της nvidia αν αυτός ήταν ο official.
Αν έκανες αναβάθμιση τον kernel και έχεις τέτοιο driver δοκίμασε να
ξανακάνεις εγκατάσταση τον driver.

Στις 03/21/2014 07:04 PM, ο/η Nick Zarkadas έγραψε:
 Γεια σας
 Μετά την τελευταία αναβάθμιση όλα έγιναν  μαύρα.
 Το γραφικό περιβάλλον (kde) δεν εμφανίζεται και τη θέση
 του έχει πάρει μια μαύρη οθόνη.
 Οι τελευταίες γραμμές του Xorg.0.log είναι οι ακόλουθες|:|
 |(EE)
 (EE) Backtrace:
 (EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb777999f]
 (EE) 1: /usr/bin/X (0xb75d2000+0x1ab774) [0xb777d774]
 (EE) 2: linux-gate.so.1 (__kernel_rt_sigreturn+0x0) [0xb75b040c]
 (EE) 3: /usr/lib/xorg/modules/linux/libglx.so (0xb5be9000+0x1203d5)
 [0xb5d093d5]
 (EE) 4: /lib/i386-linux-gnu/i686/cmov/libc.so.6
 (__libc_start_main+0xf3) [0xb70e2a63]
 (EE)
 (EE) Segmentation fault at address 0x0
 (EE)
 Fatal server error:
 (EE) Caught signal 11 (Segmentation fault). Server aborting
 (EE)
 (EE)


 Το PC μου τρέχει Debian  testing και λίγο unstable.
 Η κάρτα γραφικών είναι η nvidia FX5200. (Είναι λίγο παλιό αλλά τη
 δουλεια του την κάνει)
 Έχεις κανείς καμιά ιδέα για το πως διορθώνεται το πρόβλημα;;
 Ευχαριστώ.
 | 

dpkg segmentation fault

[Bob Proulx]

I am helping a buddy with his Sid system.  He went several months
without upgrading.  Then recently tried to upgrade.  This resulted in
some problems.  Currently the system produces a segmentation fault
when trying to install packages.  For example:

  # dpkg-reconfigure debconf
  Segmentation fault

  # dpkg -i debconf_1.5.49_all.deb 
  (Reading database ... 387854 files and directories currently installed.)
  Preparing to replace debconf 1.5.49 (using debconf_1.5.49_all.deb) ...
  Unpacking replacement debconf ...
  Setting up debconf (1.5.49) ...
  dpkg: error processing debconf (--install):
   subprocess installed post-installation script was killed by signal 
(Segmentation fault)
  Errors were encountered while processing:
   debconf

Of course the segfault makes it difficult to make any forward progress
with dpkg.  dpkg is up to date Sid version 1.17.1.  But almost all
other packages are older revs from previous days of Sid.  I tried
downgrading dpkg to the version in Wheezy but the result was the same.

Thought before I did extreme things that I would ask here in case
someone already hit this in Sid sometime between a few months ago and
now?  If so what was the solution?

Thanks!
Bob


signature.asc
Description: Digital signature

Re: dpkg segmentation fault

[Florian Kulzer]

On Wed, Oct 02, 2013 at 03:11:24 -0600, Bob Proulx wrote:
 I am helping a buddy with his Sid system.  He went several months
 without upgrading.  Then recently tried to upgrade.  This resulted in
 some problems.  Currently the system produces a segmentation fault
 when trying to install packages.  For example:
 
   # dpkg-reconfigure debconf
   Segmentation fault
 
   # dpkg -i debconf_1.5.49_all.deb 
   (Reading database ... 387854 files and directories currently installed.)
   Preparing to replace debconf 1.5.49 (using debconf_1.5.49_all.deb) ...
   Unpacking replacement debconf ...
   Setting up debconf (1.5.49) ...
   dpkg: error processing debconf (--install):
subprocess installed post-installation script was killed by signal 
 (Segmentation fault)
   Errors were encountered while processing:
debconf
 
 Of course the segfault makes it difficult to make any forward progress
 with dpkg.  dpkg is up to date Sid version 1.17.1.  But almost all
 other packages are older revs from previous days of Sid.  I tried
 downgrading dpkg to the version in Wheezy but the result was the same.
 
 Thought before I did extreme things that I would ask here in case
 someone already hit this in Sid sometime between a few months ago and
 now?  If so what was the solution?

My guess would be an incomplete or otherwise screwed-up Perl transition
(dpkg-reconfigure is a Perl script and debconf's postinst calls a bunch
of Perl scripts as well). Check the status of the Perl packages on your
friend's machine, here is what I have on up-to-date Sid/amd64:

$ dpkg -l perl\* libperl\* | awk '/^ii/{print $2,$3}'
libperl4-corelibs-perl 0.003-1
libperl5.18 5.18.1-4
perl 5.18.1-4
perl-base 5.18.1-4
perl-doc 5.18.1-4
perl-modules 5.18.1-4
perl-tk 1:804.031-1+b1
perlmagick 8:6.7.7.10-6

Other than that, I can only say that I cannot recall having any problems
with my Sid system in recent months, even though upgrading all packages
that can be upgraded is how I start almost every day.

-- 
Regards,|
  Florian   | http://www.florian-kulzer.eu


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131002193058.GA14522@isar.localhost

Re: dpkg segmentation fault

[Hugo Vanwoerkom]

Florian Kulzer wrote:

On Wed, Oct 02, 2013 at 03:11:24 -0600, Bob Proulx wrote:

I am helping a buddy with his Sid system.  He went several months
without upgrading.  Then recently tried to upgrade.  This resulted in
some problems.  Currently the system produces a segmentation fault
when trying to install packages.  For example:

  # dpkg-reconfigure debconf
  Segmentation fault

  # dpkg -i debconf_1.5.49_all.deb 
  (Reading database ... 387854 files and directories currently installed.)

  Preparing to replace debconf 1.5.49 (using debconf_1.5.49_all.deb) ...
  Unpacking replacement debconf ...
  Setting up debconf (1.5.49) ...
  dpkg: error processing debconf (--install):
   subprocess installed post-installation script was killed by signal 
(Segmentation fault)
  Errors were encountered while processing:
   debconf

Of course the segfault makes it difficult to make any forward progress
with dpkg.  dpkg is up to date Sid version 1.17.1.  But almost all
other packages are older revs from previous days of Sid.  I tried
downgrading dpkg to the version in Wheezy but the result was the same.

Thought before I did extreme things that I would ask here in case
someone already hit this in Sid sometime between a few months ago and
now?  If so what was the solution?


My guess would be an incomplete or otherwise screwed-up Perl transition
(dpkg-reconfigure is a Perl script and debconf's postinst calls a bunch
of Perl scripts as well). Check the status of the Perl packages on your
friend's machine, here is what I have on up-to-date Sid/amd64:

$ dpkg -l perl\* libperl\* | awk '/^ii/{print $2,$3}'
libperl4-corelibs-perl 0.003-1
libperl5.18 5.18.1-4
perl 5.18.1-4
perl-base 5.18.1-4
perl-doc 5.18.1-4
perl-modules 5.18.1-4
perl-tk 1:804.031-1+b1
perlmagick 8:6.7.7.10-6

Other than that, I can only say that I cannot recall having any problems
with my Sid system in recent months, even though upgrading all packages
that can be upgraded is how I start almost every day.



I get fewer Perl hits with an uptodate Sid:

hugo@hdbb:/sdc1$ dpkg -l perl\* libperl\* | awk '/^ii/{print $2,$3}'
+ dpkg -l 'perl*' 'libperl*'
+ awk '/^ii/{print $2,$3}'
libperl4-corelibs-perl 0.003-1
perl 5.18.1-4
perl-base 5.18.1-4
perl-modules 5.18.1-4

Hugo


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/l2i0jb$u97$1...@ger.gmane.org

Re: dpkg segmentation fault

[Bob Proulx]

Hugo Vanwoerkom wrote:
 Florian Kulzer wrote:
  My guess would be an incomplete or otherwise screwed-up Perl transition
  (dpkg-reconfigure is a Perl script and debconf's postinst calls a bunch
  of Perl scripts as well). Check the status of the Perl packages on your
  friend's machine, here is what I have on up-to-date Sid/amd64:

A good suggestion.  Very likely related.  I manually walked through
the packages and upgraded them with dpkg -i perl-foo_X.Y.deb and I
think all of them are now at current Sid levels.  Unfortunately the
dpkg segfault continues.

I also found a large number of removed-config state packages.

  dpkg -l | awk '$1~/^rc/{print$2}'| wc -l
  469

Mostly libraries.

  dpkg -l | awk '$1~/^rc/$2~/^lib/{print$2}' | wc -l 345

Those seem safe to purge so purging them to simplify things somewhat.

  dpkg -l | awk '$1~/^rc/{print$2}'| wc -l
  124

I am able to manually upgrade by 'dpkg -i' for individual packages.  A
little tedious.  But making some progress.  I am going to try to get
perl completely up to date.  That hopefully will fix the sig segv
problem.

Thanks!
Bob


signature.asc
Description: Digital signature

Re: dpkg segmentation fault

[Bob Proulx]

Bob Proulx wrote:
 Hugo Vanwoerkom wrote:
  Florian Kulzer wrote:
   My guess would be an incomplete or otherwise screwed-up Perl transition
   (dpkg-reconfigure is a Perl script and debconf's postinst calls a bunch
   of Perl scripts as well). Check the status of the Perl packages on your
   friend's machine, here is what I have on up-to-date Sid/amd64:
  
   $ dpkg -l perl\* libperl\* | awk '/^ii/{print $2,$3}'
 
 A good suggestion.  Very likely related.  I manually walked through
 the packages and upgraded them with dpkg -i perl-foo_X.Y.deb and I
 think all of them are now at current Sid levels.  Unfortunately the
 dpkg segfault continues.
 ...
 I am able to manually upgrade by 'dpkg -i' for individual packages.  A
 little tedious.  But making some progress.  I am going to try to get
 perl completely up to date.  That hopefully will fix the sig segv
 problem.

# dpkg -l | awk '$2~/-perl/{print$2}' | wc -l
374

I scripted a quick command line for loop to download using apt-get
(apt-get download foo) and then install it (dpkg -i foo) and walked
through all of the perl packages.  That took some machine time to
complete but I could let it run without my interaction to slow it
down.  After that the segfault problem was gone.  Yay!  Then it was
off to 'apt-get -f install' to fix the rest of things.  A few other
fixes and the next set of things are just normal Sid upgrade issues.

Those hints set me on the path to success.

Thanks!
Bob


signature.asc
Description: Digital signature

Vim and gvim yield segmentation fault in X

[CN]

Hi! I have just made a fresh wheezy installation. /usr/bin/vim.gtk and
/usr/bin/vim.athena run without problem in virtual consoles but they
both output segmentation fault immediately after they are launched
from xterm or aterm. I did not encounter such trouble in squeeze.

Reinstalling all packages except perl related ones does not fix the
problem:

COLUMNS=300 dpkg -l | awk '/^i/ {print $2}' | xargs apt-get --reinstall
install

Helps will be greatly appreciated!

Regards,
CN

-- 
http://www.fastmail.fm - Access all of your messages and folders
  wherever you are


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1374922424.5636.2174407.19c75...@webmail.messagingengine.com

Re: Vim and gvim yield segmentation fault in X

[CN]

Hi! I am answering my own question.

user1@host1:~$ locale

locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or
directory
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=zh_TW.utf8
LANGUAGE=
LC_CTYPE=zh_TW.utf8
LC_NUMERIC=zh_TW.utf8
LC_TIME=zh_TW.utf8
LC_COLLATE=zh_TW.utf8
LC_MONETARY=zh_TW.utf8
LC_MESSAGES=zh_TW.utf8
LC_PAPER=zh_TW.utf8
LC_NAME=zh_TW.utf8
LC_ADDRESS=zh_TW.utf8
LC_TELEPHONE=zh_TW.utf8
LC_MEASUREMENT=zh_TW.utf8
LC_IDENTIFICATION=zh_TW.utf8
LC_ALL=

After running LANG=C dpkg-reconfigure locales, both gvim and vim works
perfectly in X.

Regards,
CN

On Sat, Jul 27, 2013, at 06:53 PM, CN wrote:
 Hi! I have just made a fresh wheezy installation. /usr/bin/vim.gtk and
 /usr/bin/vim.athena run without problem in virtual consoles but they
 both output segmentation fault immediately after they are launched
 from xterm or aterm. I did not encounter such trouble in squeeze.

-- 
http://www.fastmail.fm - mmm... Fastmail...


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1374988382.20631.2381135.7d54a...@webmail.messagingengine.com

Re: Debian sid, PHP cli, xdebug, set_error_handler, mysql_list_dbs, throw = Segmentation fault

[Sven Uhlig]

On 19.03.2013 21:41, Jerry Stuckle wrote:
 On 3/19/2013 3:08 PM, Sven Uhlig wrote:
 On 17.03.2013 23:40, Jerry Stuckle wrote:
 On 3/17/2013 2:54 PM, Sven Uhlig wrote:
 On 17.03.2013 16:01, Jerry Stuckle wrote:
 On 3/17/2013 9:20 AM, Sven Uhlig wrote:
 The following PHP code exits in segmentation fault.

 ?php
 function error_handler() {
  throw new Exception;
 }
 set_error_handler('error_handler');
 mysql_list_dbs();
 ?

 No segmentation fault if I do either of these things:
 1) disable xdebug
 2) don't set_error_handler
 3) don't throw exception
 4) throw exception after mysql_list_dbs but outside of error_handler

 $ php -v
 PHP 5.4.4-14 (cli) (built: Mar  4 2013 14:08:43)
 Copyright (c) 1997-2012 The PHP Group
 Zend Engine v2.4.0, Copyright (c) 1998-2012 Zend Technologies
with Xdebug v2.2.1, Copyright (c) 2002-2012, by Derick Rethans

 # uname -a
 Linux baldur 3.2.0-4-amd64 #1 SMP Debian 3.2.39-2 x86_64 GNU/Linux

 Impossible to tell from the (lack of) information you supplied.

 What do you need?

 Well, if it happened to me, I'd get a dump of the problem, preferably
 with a debug version of the binaries, and a trace leading up to the
 problem.  Then I'd dig in and see where the problem lies.

 Because I am no C developer, I have no idea where to look for the cause
 of the problem. All I can do is to help someone else fixing the code of
 xdebug/php. But I am really not the right person to do this.


 I'm not sure about anyone else on this list, but unfortunately I don't
 have the time it would take to duplicate your environment then try to
 duplicate your problem.
 
 I understand you're not a C programmer - which is why I suggested you
 start with the developer of xdebug.  It's where I would start if I had
 this problem.

Jerry, sorry. I totally got you wrong before. I tought you wanted me to
fix the problem...

I have forwarded the bug report to xdebug
http://bugs.xdebug.org/view.php?id=936

Best regards
Sven.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5149df1d.8020...@web.de

Re: Debian sid, PHP cli, xdebug, set_error_handler, mysql_list_dbs, throw = Segmentation fault

[Sven Uhlig]

On 17.03.2013 23:40, Jerry Stuckle wrote:
 On 3/17/2013 2:54 PM, Sven Uhlig wrote:
 On 17.03.2013 16:01, Jerry Stuckle wrote:
 On 3/17/2013 9:20 AM, Sven Uhlig wrote:
 The following PHP code exits in segmentation fault.

 ?php
 function error_handler() {
 throw new Exception;
 }
 set_error_handler('error_handler');
 mysql_list_dbs();
 ?

 No segmentation fault if I do either of these things:
 1) disable xdebug
 2) don't set_error_handler
 3) don't throw exception
 4) throw exception after mysql_list_dbs but outside of error_handler

 $ php -v
 PHP 5.4.4-14 (cli) (built: Mar  4 2013 14:08:43)
 Copyright (c) 1997-2012 The PHP Group
 Zend Engine v2.4.0, Copyright (c) 1998-2012 Zend Technologies
   with Xdebug v2.2.1, Copyright (c) 2002-2012, by Derick Rethans

 # uname -a
 Linux baldur 3.2.0-4-amd64 #1 SMP Debian 3.2.39-2 x86_64 GNU/Linux

 Impossible to tell from the (lack of) information you supplied.

 What do you need?

 Well, if it happened to me, I'd get a dump of the problem, preferably
 with a debug version of the binaries, and a trace leading up to the
 problem.  Then I'd dig in and see where the problem lies.

Because I am no C developer, I have no idea where to look for the cause
of the problem. All I can do is to help someone else fixing the code of
xdebug/php. But I am really not the right person to do this.

Here is the backtrace of gdb after I have installed php5-dbg.

#0  _zend_mm_alloc_int (heap=0xdb92b0, size=32) at
/tmp/buildd/php5-5.4.4/Zend/zend_alloc.c:1906
#1  0x0069eeda in zend_error (type=8192, format=0xa77fdf %s)
at /tmp/buildd/php5-5.4.4/Zend/zend.c:1105
#2  0x0063d376 in php_verror (docref=0xdb84c0
x\255\377\377\377\177,
params=0x1 Address 0x1 out of bounds, type=8192, format=0x1
Address 0x1 out of bounds, args=0x1)
at /tmp/buildd/php5-5.4.4/main/main.c:853
#3  0x0063d79e in php_error_docref0 (docref=0xdb92b0 \001,
type=32,
format=0x1 Address 0x1 out of bounds) at
/tmp/buildd/php5-5.4.4/main/main.c:865
#4  0x745f86e1 in ?? () from /usr/lib/php5/20100525/mysql.so
#5  0x74a2aedc in xdebug_execute_internal
(current_execute_data=0x74f26060, return_value_used=0)
at /srv/debian_developer/xdebug/xdebug-2.2.1/build-php5/xdebug.c:1483
#6  0x00746a3e in zend_do_fcall_common_helper_SPEC
(execute_data=0x74f26060)
at /tmp/buildd/php5-5.4.4/Zend/zend_vm_execute.h:644
#7  0x00700447 in execute (op_array=0x74f592f0) at
/tmp/buildd/php5-5.4.4/Zend/zend_vm_execute.h:410
#8  0x74a2aa81 in xdebug_execute (op_array=0x74f592f0)
at /srv/debian_developer/xdebug/xdebug-2.2.1/build-php5/xdebug.c:1391
#9  0x006a028e in zend_execute_scripts (type=8,
retval=0x74f592b8, file_count=3)
at /tmp/buildd/php5-5.4.4/Zend/zend.c:1279
#10 0x0063f863 in php_execute_script (primary_file=0x75b44ec0)
at /tmp/buildd/php5-5.4.4/main/main.c:2473
#11 0x007491b3 in do_cli (argc=0, argv=0x7fffe8f1) at
/tmp/buildd/php5-5.4.4/sapi/cli/php_cli.c:988
#12 0x0043110a in main (argc=32767, argv=0xdb9210) at
/tmp/buildd/php5-5.4.4/sapi/cli/php_cli.c:1361


Sven.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5148b7a9.3010...@web.de

Re: Debian sid, PHP cli, xdebug, set_error_handler, mysql_list_dbs, throw = Segmentation fault

[Jerry Stuckle]

On 3/19/2013 3:08 PM, Sven Uhlig wrote:

On 17.03.2013 23:40, Jerry Stuckle wrote:

On 3/17/2013 2:54 PM, Sven Uhlig wrote:

On 17.03.2013 16:01, Jerry Stuckle wrote:

On 3/17/2013 9:20 AM, Sven Uhlig wrote:

The following PHP code exits in segmentation fault.

?php
function error_handler() {
 throw new Exception;
}
set_error_handler('error_handler');
mysql_list_dbs();
?

No segmentation fault if I do either of these things:
1) disable xdebug
2) don't set_error_handler
3) don't throw exception
4) throw exception after mysql_list_dbs but outside of error_handler

$ php -v
PHP 5.4.4-14 (cli) (built: Mar  4 2013 14:08:43)
Copyright (c) 1997-2012 The PHP Group
Zend Engine v2.4.0, Copyright (c) 1998-2012 Zend Technologies
   with Xdebug v2.2.1, Copyright (c) 2002-2012, by Derick Rethans

# uname -a
Linux baldur 3.2.0-4-amd64 #1 SMP Debian 3.2.39-2 x86_64 GNU/Linux


Impossible to tell from the (lack of) information you supplied.


What do you need?


Well, if it happened to me, I'd get a dump of the problem, preferably
with a debug version of the binaries, and a trace leading up to the
problem.  Then I'd dig in and see where the problem lies.


Because I am no C developer, I have no idea where to look for the cause
of the problem. All I can do is to help someone else fixing the code of
xdebug/php. But I am really not the right person to do this.

Here is the backtrace of gdb after I have installed php5-dbg.

#0  _zend_mm_alloc_int (heap=0xdb92b0, size=32) at
/tmp/buildd/php5-5.4.4/Zend/zend_alloc.c:1906
#1  0x0069eeda in zend_error (type=8192, format=0xa77fdf %s)
at /tmp/buildd/php5-5.4.4/Zend/zend.c:1105
#2  0x0063d376 in php_verror (docref=0xdb84c0
x\255\377\377\377\177,
 params=0x1 Address 0x1 out of bounds, type=8192, format=0x1
Address 0x1 out of bounds, args=0x1)
 at /tmp/buildd/php5-5.4.4/main/main.c:853
#3  0x0063d79e in php_error_docref0 (docref=0xdb92b0 \001,
type=32,
 format=0x1 Address 0x1 out of bounds) at
/tmp/buildd/php5-5.4.4/main/main.c:865
#4  0x745f86e1 in ?? () from /usr/lib/php5/20100525/mysql.so
#5  0x74a2aedc in xdebug_execute_internal
(current_execute_data=0x74f26060, return_value_used=0)
 at /srv/debian_developer/xdebug/xdebug-2.2.1/build-php5/xdebug.c:1483
#6  0x00746a3e in zend_do_fcall_common_helper_SPEC
(execute_data=0x74f26060)
 at /tmp/buildd/php5-5.4.4/Zend/zend_vm_execute.h:644
#7  0x00700447 in execute (op_array=0x74f592f0) at
/tmp/buildd/php5-5.4.4/Zend/zend_vm_execute.h:410
#8  0x74a2aa81 in xdebug_execute (op_array=0x74f592f0)
 at /srv/debian_developer/xdebug/xdebug-2.2.1/build-php5/xdebug.c:1391
#9  0x006a028e in zend_execute_scripts (type=8,
retval=0x74f592b8, file_count=3)
 at /tmp/buildd/php5-5.4.4/Zend/zend.c:1279
#10 0x0063f863 in php_execute_script (primary_file=0x75b44ec0)
 at /tmp/buildd/php5-5.4.4/main/main.c:2473
#11 0x007491b3 in do_cli (argc=0, argv=0x7fffe8f1) at
/tmp/buildd/php5-5.4.4/sapi/cli/php_cli.c:988
#12 0x0043110a in main (argc=32767, argv=0xdb9210) at
/tmp/buildd/php5-5.4.4/sapi/cli/php_cli.c:1361


Sven.




Sven,

I'm not sure about anyone else on this list, but unfortunately I don't 
have the time it would take to duplicate your environment then try to 
duplicate your problem.


I understand you're not a C programmer - which is why I suggested you 
start with the developer of xdebug.  It's where I would start if I had 
this problem.



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/5148cd68.4040...@attglobal.net

Debian sid, PHP cli, xdebug, set_error_handler, mysql_list_dbs, throw = Segmentation fault

[Sven Uhlig]

Hello again,

this time I write to this list to report a bug, a segmentation fault.
Couldn't find any lead to this bug anywhere else. And because of so many
related packages, I dont know where to post it. Did I find the right place?

The following PHP code exits in segmentation fault.

?php
function error_handler() {
  throw new Exception;
}
set_error_handler('error_handler');
mysql_list_dbs();
?

No segmentation fault if I do either of these things:
1) disable xdebug
2) don't set_error_handler
3) don't throw exception
4) throw exception after mysql_list_dbs but outside of error_handler

As I only wanted to use mysql_list_dbs() for testing purposes I don't
need an alternative solution. I know that this function is deprecated in
PHP5.4.

Some technical details:
$ strace php test.php 21 |tail -n 3
read(3, \7\0\0\2\0\0\0\2\0\0\0, 16384) = 11
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++

$ php -v
PHP 5.4.4-14 (cli) (built: Mar  4 2013 14:08:43)
Copyright (c) 1997-2012 The PHP Group
Zend Engine v2.4.0, Copyright (c) 1998-2012 Zend Technologies
with Xdebug v2.2.1, Copyright (c) 2002-2012, by Derick Rethans

$ cat /etc/apt/sources.list
deb http://ftp2.de.debian.org/debian/ sid main non-free
deb-src http://ftp2.de.debian.org/debian/ sid main non-free

# (apt-get update  apt-get upgrade)|tail -n 1
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

# uname -a
Linux baldur 3.2.0-4-amd64 #1 SMP Debian 3.2.39-2 x86_64 GNU/Linux

Best regards
Sven.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5145c329.6060...@web.de

Re: Debian sid, PHP cli, xdebug, set_error_handler, mysql_list_dbs, throw = Segmentation fault

[Jerry Stuckle]

On 3/17/2013 9:20 AM, Sven Uhlig wrote:

Hello again,

this time I write to this list to report a bug, a segmentation fault.
Couldn't find any lead to this bug anywhere else. And because of so many
related packages, I dont know where to post it. Did I find the right place?

The following PHP code exits in segmentation fault.

?php
function error_handler() {
   throw new Exception;
}
set_error_handler('error_handler');
mysql_list_dbs();
?

No segmentation fault if I do either of these things:
1) disable xdebug
2) don't set_error_handler
3) don't throw exception
4) throw exception after mysql_list_dbs but outside of error_handler

As I only wanted to use mysql_list_dbs() for testing purposes I don't
need an alternative solution. I know that this function is deprecated in
PHP5.4.

Some technical details:
$ strace php test.php 21 |tail -n 3
read(3, \7\0\0\2\0\0\0\2\0\0\0, 16384) = 11
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++

$ php -v
PHP 5.4.4-14 (cli) (built: Mar  4 2013 14:08:43)
Copyright (c) 1997-2012 The PHP Group
Zend Engine v2.4.0, Copyright (c) 1998-2012 Zend Technologies
 with Xdebug v2.2.1, Copyright (c) 2002-2012, by Derick Rethans

$ cat /etc/apt/sources.list
deb http://ftp2.de.debian.org/debian/ sid main non-free
deb-src http://ftp2.de.debian.org/debian/ sid main non-free

# (apt-get update  apt-get upgrade)|tail -n 1
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

# uname -a
Linux baldur 3.2.0-4-amd64 #1 SMP Debian 3.2.39-2 x86_64 GNU/Linux

Best regards
Sven.




Impossible to tell from the (lack of) information you supplied. 
However, personally, I would start with xdebug.  I've seen more problems 
with it than anything else in your list.  I finally got rid of it.



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/5145dac1.4070...@attglobal.net

Re: Debian sid, PHP cli, xdebug, set_error_handler, mysql_list_dbs, throw = Segmentation fault

[Sven Uhlig]

On 17.03.2013 16:01, Jerry Stuckle wrote:
 On 3/17/2013 9:20 AM, Sven Uhlig wrote:
 The following PHP code exits in segmentation fault.

 ?php
 function error_handler() {
throw new Exception;
 }
 set_error_handler('error_handler');
 mysql_list_dbs();
 ?

 No segmentation fault if I do either of these things:
 1) disable xdebug
 2) don't set_error_handler
 3) don't throw exception
 4) throw exception after mysql_list_dbs but outside of error_handler

 As I only wanted to use mysql_list_dbs() for testing purposes I don't
 need an alternative solution. I know that this function is deprecated in
 PHP5.4.

 Some technical details:
 $ strace php test.php 21 |tail -n 3
 read(3, \7\0\0\2\0\0\0\2\0\0\0, 16384) = 11
 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
 +++ killed by SIGSEGV +++

 $ php -v
 PHP 5.4.4-14 (cli) (built: Mar  4 2013 14:08:43)
 Copyright (c) 1997-2012 The PHP Group
 Zend Engine v2.4.0, Copyright (c) 1998-2012 Zend Technologies
  with Xdebug v2.2.1, Copyright (c) 2002-2012, by Derick Rethans

 $ cat /etc/apt/sources.list
 deb http://ftp2.de.debian.org/debian/ sid main non-free
 deb-src http://ftp2.de.debian.org/debian/ sid main non-free

 # (apt-get update  apt-get upgrade)|tail -n 1
 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

 # uname -a
 Linux baldur 3.2.0-4-amd64 #1 SMP Debian 3.2.39-2 x86_64 GNU/Linux
 
 Impossible to tell from the (lack of) information you supplied.

What do you need?

 However,
 personally, I would start with xdebug.  I've seen more problems with it
 than anything else in your list.  I finally got rid of it.

As stated above, disabling xdebug does the trick. But that cannot be a
permanent solution and I think a segmentation fault is always worth fixing.

Sven.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5146115b.8040...@web.de

Re: Debian sid, PHP cli, xdebug, set_error_handler, mysql_list_dbs, throw = Segmentation fault

[Jerry Stuckle]

On 3/17/2013 2:54 PM, Sven Uhlig wrote:

On 17.03.2013 16:01, Jerry Stuckle wrote:

On 3/17/2013 9:20 AM, Sven Uhlig wrote:

The following PHP code exits in segmentation fault.

?php
function error_handler() {
throw new Exception;
}
set_error_handler('error_handler');
mysql_list_dbs();
?

No segmentation fault if I do either of these things:
1) disable xdebug
2) don't set_error_handler
3) don't throw exception
4) throw exception after mysql_list_dbs but outside of error_handler

As I only wanted to use mysql_list_dbs() for testing purposes I don't
need an alternative solution. I know that this function is deprecated in
PHP5.4.

Some technical details:
$ strace php test.php 21 |tail -n 3
read(3, \7\0\0\2\0\0\0\2\0\0\0, 16384) = 11
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++

$ php -v
PHP 5.4.4-14 (cli) (built: Mar  4 2013 14:08:43)
Copyright (c) 1997-2012 The PHP Group
Zend Engine v2.4.0, Copyright (c) 1998-2012 Zend Technologies
  with Xdebug v2.2.1, Copyright (c) 2002-2012, by Derick Rethans

$ cat /etc/apt/sources.list
deb http://ftp2.de.debian.org/debian/ sid main non-free
deb-src http://ftp2.de.debian.org/debian/ sid main non-free

# (apt-get update  apt-get upgrade)|tail -n 1
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

# uname -a
Linux baldur 3.2.0-4-amd64 #1 SMP Debian 3.2.39-2 x86_64 GNU/Linux


Impossible to tell from the (lack of) information you supplied.


What do you need?


However,
personally, I would start with xdebug.  I've seen more problems with it
than anything else in your list.  I finally got rid of it.


As stated above, disabling xdebug does the trick. But that cannot be a
permanent solution and I think a segmentation fault is always worth fixing.

Sven.




Well, if it happened to me, I'd get a dump of the problem, preferably 
with a debug version of the binaries, and a trace leading up to the 
problem.  Then I'd dig in and see where the problem lies.


But as I said before - my suspicion would be xdebug.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/51464643.2040...@attglobal.net

Re: relocation error: and segmentation fault

[Dennis Wicks]

Arno, et al,

Thanks for the help and detail instructions. It isn't easy, 
but better than the alternative of a complete rebuild.


And no, I can't run dpkg. The only things that run are those 
that were up at the time aptitude crashed. Like Thunderbird, 
browser, gthumb, OpenOffice, etc.


Thanks again,
Dennis


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4edbee4e.5000...@mgssub.com

Re: relocation error: and segmentation fault

[Dennis Wicks]

It looks like I am going to have to restore some libraries 
at the least.


Is there any way that I can refresh or reinstall my system 
without wiping out all the other things I have on the same 
disk? eg /home and other user directories and optional software.


Tia for any and all help,
Dennis


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4eda7aba.6090...@mgssub.com

Re: relocation error: and segmentation fault

[Arno Schuring]

Dennis Wicks (w...@mgssub.com on 2011-12-03 13:38 -0600):
 It looks like I am going to have to restore some libraries 
 at the least.
 
 Is there any way that I can refresh or reinstall my system 
 without wiping out all the other things I have on the same 
 disk? eg /home and other user directories and optional software.

Can you still run dpkg? Then your best bet is to use a different
machine to download just enough to get apt working again (that's only
libc6, libgcc1, libstdc++6 and zlib1g on testing). If some configure
script cannot run because of a missing library, you can postpone it by
using dpkg --unpack instead of dpkg -i.

When you have apt working, you can work on restoring the rest of your
system. My advice would be to (re)install aptitude first, see below why.


You can use ldd to find out which libraries are missing, and dpkg -S to
get the package to which they belong. As an example:

$ ldd `which apt-get`
linux-gate.so.1 =  (0xf7757000)
libapt-pkg.so.4.10 = /usr/lib/libapt-pkg.so.4.10 (0xf7634000)
[..]
libdl.so.2 = /lib/i386-linux-gnu/i686/cmov/libdl.so.2 (..)
libz.so.1 = /usr/lib/libz.so.1 (0xf739)
/lib/ld-linux.so.2 (0xf7758000)
$ dpkg -S /usr/lib/libz.so.1
zlib1g: /usr/lib/libz.so.1

If libraries are missing, they will show as '= not found'. That means
you will have to guess the full path, use another system as reference,
use apt-file to search for the package, or just guess. Most libraries
are in /lib or /usr/lib on Squeeze, but on Wheezy you'll find some in
the old location and most in an architecture-specific location such as
shown above.


When you have aptitude working, you're almost home. A full system
rebuild can be done with
# aptitude reinstall ~i

Or just the libraries:
# aptitude reinstall ~slibs
(Don't about the tons of not installed, so not reinstall messages).


Best of luck,
Arno


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111204011531.2185c...@neminis.intra.loos.site

Re: relocation error: and segmentation fault

[Johann Klammer]

Dennis Wicks wrote:

Sorry!! I clicked the wrong icon and sent the previous message by mistake!)

I was running aptitude and it canceled for some reason. Now
I am getting


relocation error: /lib/libproc-3.2.7.so: symbol memset, version
GLIBC_2.0 not defined in file libc.so.6 with link time reference


and also


symbol lookup error: /usr/lib/i386-linux-gnu/libstdc++.so.6:
undefined symbol: _ZNSt8messagesIcE2idE, version GLIBCXX_3.4


and also segmentation fault.

This happens when I try to do something in a console window or a
gnome-terminal window. And nothing else happens. I am also getting a ton
of segmentation fault message in my f1 console session.

I'm afraid to try shutting down and restarting because I'm fearful that
it may not even come up!


Yes, that's _very_ likely.



Any suggestions? Oh yes, aptitude, apt-get and dpkg won't start.


I guess you've lost some important library.
The easiest way would be to use a live distro on a cdrom or USB stick 
and use that to mount your system partitions and install the missing 
packages.

downloaded packages may still be in /var/cache/apt.
/var/log/apt/history might tell you what went wrong.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4ed7de18.7010...@aon.at

relocation error: and segmentation fault

[Dennis Wicks]

I was running aptitude and it canceled for some reason. Now 
I am getting


relocation error: /lib/libproc-3.2.7.so: symbol memset, 
version GLIBC_2.0 not defined in file libc.so.6 with link time reference


and also



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4ed6d7e9.70...@mgssub.com

relocation error: and segmentation fault

[Dennis Wicks]

Sorry!! I clicked the wrong icon and sent the previous 
message by mistake!)


I was running aptitude and it canceled for some reason. Now
I am getting

relocation error: /lib/libproc-3.2.7.so: symbol memset, 
version GLIBC_2.0 not defined in file libc.so.6 with link time reference


and also


symbol lookup error: /usr/lib/i386-linux-gnu/libstdc++.so.6:
undefined symbol: _ZNSt8messagesIcE2idE, version GLIBCXX_3.4


and also segmentation fault.

This happens when I try to do something in a console window 
or a gnome-terminal window. And nothing else happens. I am 
also getting a ton of segmentation fault message in my f1 
console session.


I'm afraid to try shutting down and restarting because I'm 
fearful that it may not even come up!


Any suggestions? Oh yes, aptitude, apt-get and dpkg won't 
start.


Thanks for any help!
Dennis





--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4ed6dada.9050...@mgssub.com

Re: possible reasons to cause Segmentation fault

[Camaleón]

On Sun, 09 Oct 2011 23:44:00 +0800, lina wrote:

 I met Segmentation fault in two places in one day,

What are those places?

Crystal balls are expensive :-)

 Which are the possible reasons for the segmentation fault.

Wow, there can be many. You need to provide more data.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.10.10.13.00...@gmail.com

Re: possible reasons to cause Segmentation fault

[lina]

On Mon, Oct 10, 2011 at 9:00 PM, Camaleón noela...@gmail.com wrote:

 On Sun, 09 Oct 2011 23:44:00 +0800, lina wrote:

  I met Segmentation fault in two places in one day,

 What are those places?

Hi,

On laptop, later I figured out due to the recent update of one package which
cause its crashed.
after downgrading, it's fixed.

Another segmental fault is on cluster:
mpirun noticed that process rank 17 with PID 12834 on node c10 exited
on signal 11 (Segmentation fault).
(I guess this problem will keep it as it is. don't wanna trouble the
administrator, but if you have suggestions welcome to let me know)


 Crystal balls are expensive :-)

Ha ... I am your crystal ball now, ask me more if you want. and ... and ..
it's free!!!
(a bit kidding here, sorry I should have provided more info. before)


  Which are the possible reasons for the segmentation fault.

 Wow, there can be many. You need to provide more data.'

I choose some which I thought might be important data.

Signal: Segmentation fault (11)
Signal code: Address not mapped (1)
Failing at address: 0xd1
[ 0] /lib64/libpthread.so.0 [0x3ec8e0e7c0]
[ 1] /usr/local/mpi/intel/lib/openmpi/mca_pml_ob1.so [0x2b7c80a013e8]
:
:
[14] /lib64/libc.so.6(__libc_start_main+0xf4) [0x3ec861d994]
[15] mdrun_mpi_d(do_cg+0x1c1) [0x40b359]

Thanks,


 Greetings,

 --
 Camaleón


 --
 To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive: http://lists.debian.org/pan.2011.10.10.13.00...@gmail.com

Re: possible reasons to cause Segmentation fault

[Camaleón]

On Mon, 10 Oct 2011 23:04:53 +0800, lina wrote:

(care with that html...)

 On Mon, Oct 10, 2011 at 9:00 PM, Camaleón noela...@gmail.com wrote:
 
 On Sun, 09 Oct 2011 23:44:00 +0800, lina wrote:

  I met Segmentation fault in two places in one day,

 What are those places?

 On laptop, later I figured out due to the recent update of one package
 which cause its crashed.
 after downgrading, it's fixed.

Good.

Maybe you can report a regression bug :-?

 Another segmental fault is on cluster: mpirun noticed that process rank
 17 with PID 12834 on node c10 exited on signal 11 (Segmentation fault).
 (I guess this problem will keep it as it is. don't wanna trouble the
 administrator, but if you have suggestions welcome to let me know)

(...)

Mmm, for this I can't tell, as I don't know what mpirun is or does.

What you can try is to get a trace for the segfault, some binaries 
provide debugging tools (by means of -debug flags you can pass to 
daemon) or even provide the corresponding -gdb packages to get a 
insightful trace.

  Which are the possible reasons for the segmentation fault.

 Wow, there can be many. You need to provide more data.'
 
 I choose some which I thought might be important data.

But what command did you run? 

 Signal: Segmentation fault (11)
 Signal code: Address not mapped (1)
 Failing at address: 0xd1
 [ 0] /lib64/libpthread.so.0 [0x3ec8e0e7c0] 
 [ 1] /usr/local/mpi/intel/lib/openmpi/mca_pml_ob1.so [0x2b7c80a013e8] 
 :
 :
 [14] /lib64/libc.so.6(__libc_start_main+0xf4) [0x3ec861d994] 
 [15] mdrun_mpi_d(do_cg+0x1c1) [0x40b359]

Ah, okay, I guess this comes from the mentioned daemon (mpirun), right?

I'm afraid that goes beyond my knowledge, sorry, let's see if someone can 
give you any hint :-)

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.10.10.16.08...@gmail.com