Re: Segmentation fault in Chromium

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

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

unknown package causing segmentation fault

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

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

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

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 8

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

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: > &

intel-media-va-driver segmentation fault in unstable

x27; 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 utilit

Re: Xorg fatal server error segmentation fault i686

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

Re: Xorg fatal server error segmentation fault i686

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

Re: Xorg fatal server error segmentation fault i686

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

Re: Xorg fatal server error segmentation fault i686

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:

Re: Xorg fatal server error segmentation fault i686

gt; 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. >> &

Re: Xorg fatal server error segmentation fault i686

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

Re: Xorg fatal server error segmentation fault i686

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.

Re: Xorg fatal server error segmentation fault i686

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.l

Re: Xorg fatal server error segmentation fault i686

ral 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

Re: Xorg fatal server error segmentation fault i686

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

Re: Xorg fatal server error segmentation fault i686

n 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?

Re: Xorg fatal server error segmentation fault i686

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/ I

Re: Xorg fatal server error segmentation fault i686

n 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

Xorg fatal server error segmentation fault i686

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.

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 ...

Re: [Python-Help] Python 3 Segmentation Fault

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, b

Re: Python 3 Segmentation Fault

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 >

Re: Python 3 Segmentation Fault

"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 ) w

Python 3 Segmentation Fault

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 (de

Re: Buster: klavaro crashes with segmentation fault?

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?

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 r

Re: Buster: klavaro crashes with segmentation fault?

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?

Re: Buster: klavaro crashes with segmentation fault?

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

Buster: klavaro crashes with segmentation fault?

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 "L

Apache Segmentation Fault

] 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 No

Re: Segmentation fault in top -b1 -hc

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 anythi

Re: Segmentation fault in top -b1 -hc

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 > >> &g

Re: Segmentation fault in top -b1 -hc

-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 > &g

Re: Segmentation fault in top -b1 -hc

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,

Segmentation fault in top -b1 -hc

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

Re: segmentation fault when playing videos

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 

segmentation fault when playing videos

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  0x7f1726489

Re: useradd segmentation fault

-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

Re: useradd segmentation fault

-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

Re: useradd segmentation fault

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_

Re: useradd segmentation fault

-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, tha

Re: useradd segmentation fault

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 No

Re: useradd segmentation fault

-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 > cored

Re: useradd segmentation fault

-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 > b

Re: useradd segmentation fault

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

Re: useradd segmentation fault

m /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

Re: useradd segmentation fault

-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 seg

Re: useradd segmentation fault

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? > th

Re: useradd segmentation fault

-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

Re: useradd segmentation fault

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 symbo

Re: useradd segmentation fault

Hi. On Sat, 08 Nov 2014 01:02:25 -0800 Joris Bolsens 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

Re: useradd segmentation fault

-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: 20

Re: useradd segmentation fault

ULT 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

Re: useradd segmentation fault

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) con

Re: useradd segmentation fault

rnames 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. >> >&g

Re: useradd segmentation fault

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 pa

Re: useradd segmentation fault

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: http

useradd segmentation fault

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

Re: dpkg segmentation fault

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 y

Re: dpkg segmentation fault

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, he

Re: dpkg segmentation fault

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

Re: dpkg segmentation fault

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 tryin

dpkg segmentation fault

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

Re: Vim and gvim yield segmentation fault in X

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. -- h

Vim and gvim yield segmentation fault in X

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. Reinst

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

en Uhlig wrote: >>>>>> The following PHP code exits in "segmentation fault". >>>>>> >>>>>> >>>>> function error_handler() { >>>>>> throw new Exception; >>>>>> } >>>>>

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

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". No segmentation fau

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

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". >>>> &g

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

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". No segmentation fault if I do either of these things: 1) disable xdebug 2) don't set_error_handler

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

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". >> >> > function error_handler() { >>throw new Exception; >> } >> set_error_handler('error_ha

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

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

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

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 fau

Re: relocation error: and segmentation fault

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

Re: relocation error: and segmentation fault

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 dire

Re: relocation error: and segmentation fault

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 -

Re: relocation error: and segmentation fault

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

relocation error: and segmentation fault

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

relocation error: and segmentation fault

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 subjec

Re: possible reasons to cause Segmentation fault

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

Re: possible reasons to cause Segmentation fault

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 wrote: > >> On Sun, 09 Oct 2011 23:44:00 +0800, lina wrote: >> >> > I met "Segmentation fault" in two places in one day, >> >&g

Re: possible reasons to cause Segmentation fault

On Mon, Oct 10, 2011 at 9:00 PM, Camaleón 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

Re: possible reasons to cause Segmentation fault

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

Re: possible reasons to cause Segmentation fault

The other information including: Setting-Error: type read mismatch (float) -1 Setting-Error: type read mismatch (int) 667 rlwrap: Command not found. (this one maybe not related, ) Thanks,

possible reasons to cause Segmentation fault

Hi, I met "Segmentation fault" in two places in one day, Which are the possible reasons for the segmentation fault. Thanks,

apt-get causes Segmentation fault

Hi all, I hope someone can help me with this one please. apt-get and aptitude on a Debian 6.0 server cause segmentation faults on anything I do. newusaxen:~# apt-get remove libvirt-bin Segmentation faultsts... 0% newusaxen:~# aptitude remove libvirt-bin [ 0%] Reading package listsSegmentation f

Re: Segmentation fault with iceape, etc.

On Thu, Apr 14, 2011 at 6:41 AM, Paul E Condon wrote: > On 20110413_202225, Javier Vasquez wrote: >> On Wed, Apr 13, 2011 at 8:02 PM, Don J wrote: >> > For a week or more, I've been having problems with iceape and a few >> > other programs.  As far as I can se

Re: Segmentation fault with iceape, etc.

On 20110413_202225, Javier Vasquez wrote: > On Wed, Apr 13, 2011 at 8:02 PM, Don J wrote: > > For a week or more, I've been having problems with iceape and a few > > other programs.  As far as I can see, they get a segmentation fault > > and just disappear.  From the

Re: Segmentation fault with iceape, etc.

On Wed, Apr 13, 2011 at 8:02 PM, Don J wrote: > For a week or more, I've been having problems with iceape and a few > other programs.  As far as I can see, they get a segmentation fault > and just disappear.  From the debugging and back traces that I've > done, it appears th

Segmentation fault with iceape, etc.

For a week or more, I've been having problems with iceape and a few other programs.  As far as I can see, they get a segmentation fault and just disappear.  From the debugging and back traces that I've done, it appears that I may be missing or have corrupted files relating to Gt

rdesktop segmentation fault

We have found that the Lenny rdestkop-1.6.0-2 package seg faults reliably when using seamlessrdp. In fact, it seg faults on every other access. Apparently this is a known problem. We did apply the known patch. It works and we have packaged internally as rdesktop-1.6.0-2.1. Should we do anything

Segmentation fault query.

Hi, all I need some direction. I am running Debian squeeze-amd64 and have encountered a problem. On shutting down with kernel 2.6.32-trunk-amd64 after the system halt, I get a "segmentation fault" and hangs. the system stays powered up. Booting with kernel 2.6.30-1 this does not occ

Re: apt-get update segmentation fault

On Wednesday 04 November 2009, Thomas H. George wrote: > just ran apt-get update with the following result: > > ... > > E: Method rred has died unexpectedly! > E: Sub-process rred received a segmentation fault. > dragon:~# exit > > Script done on Wed 04 Nov 2009 08:5

Re: apt-get update segmentation fault

On Wed, 04 Nov 2009 08:58:07 -0500 "Thomas H. George" wrote: > just ran apt-get update with the following result: i) read today's postings to the list ii) google the error iii) use the BTS Celejar -- foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator mailmin.sourceforge.net

apt-get update segmentation fault

Packages rred 0] E: Method rred has died unexpectedly! E: Sub-process rred received a segmentation fault. dragon:~# exit Script done on Wed 04 Nov 2009 08:53:24 AM EST I am using Squeeze on a 64 bit system and have updated successfully in the past. Tom -- To UNSUBSCRIBE

Re: Squeeze: Sub - Process rred received segmentation fault

On Wed, 04 Nov 2009 13:04:34 +0200 Γιώργος Πάλλας wrote: > Jason Filippou wrote: ... > > E: Method rred has died unexpectedly! > > E: Sub-process rred received a segmentation fault. ... > There is already a relevant bug submitted for package 'apt'. ht

Re: Squeeze: Sub - Process rred received segmentation fault

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Jason, Look at http://lists.debian.org/debian-user/2009/11/msg00225.html Jason Filippou wrote: > E: Method rred has died unexpectedly! > E: Sub-process rred received a segmentation fault. > > Am I to assume that there's some k

Re: Squeeze: Sub - Process rred received segmentation fault

t:10 http://http.us.debian.org unstable/non-free 2009-11-04-0016.39.pdiff [151kB] Get:11 http://http.us.debian.org experimental/main 2009-11-02-2358.21.pdiff [3,694B] E: Method rred has died unexpectedly! E: Sub-process rred received a segmentation fault. Am I to assume that there's some kind

  1   2   3   4   5   6   >