Crash?!?
Hello everyone Last night something weird happened. I was locally on my Debian GNU/Linux machine, doing some chatting, whilst suddenly the whole system seemed to get into an unusable state. I could still switch VTs, but could not login on any of them. Funnily was I able to login remotely, though. Today, I noticed the following (rather long) dump in /var/log/syslog. It doesn't look like a usual Oops, so I am unsure what caused this. Does anyone have a clue what was going on?? Thanks. Okay, here follows the dump: Feb 3 02:08:12 host kernel: Feb 3 02:08:12 host kernel: freesibling Feb 3 02:08:12 host kernel: task PCstack pid father child younger older Feb 3 02:08:12 host kernel: init 1 S C17F9EF8 5136 1 0 4438 Feb 3 02:08:12 host kernel:sig: 0 : X Feb 3 02:08:12 host kernel: kflushd2 S C17B5FA4 5656 2 1 3 Feb 3 02:08:12 host kernel:sig: 0 : X Feb 3 02:08:12 host kernel: kupdate3 S C17B3FB8 5868 3 1 4 2 Feb 3 02:08:12 host kernel:sig: 0 fffd : X Feb 3 02:08:12 host kernel: kpiod 4 S 0F00 6976 4 1 5 3 Feb 3 02:08:12 host kernel:sig: 0 : X Feb 3 02:08:12 host kernel: kswapd 5 S C17AFFC4 5436 5 1 129 4 Feb 3 02:08:12 host kernel:sig: 0 : X Feb 3 02:08:12 host kernel: syslogd 10 S 7FFF 5252 129 1 131 5 Feb 3 02:08:12 host kernel:sig: 0 : X Feb 3 02:08:12 host kernel: klogd 12 R C145C000 0 131 1 220 129 Feb 3 02:08:12 host kernel:sig: 0 : X Feb 3 02:08:12 host kernel: dhcpcd 8 S C151FF78 4 220 1 224 131 Feb 3 02:08:12 host kernel:sig: 0 : X Feb 3 02:08:12 host kernel: named 9 S C14D7EF8 376 224 1 229 220 Feb 3 02:08:12 host kernel:sig: 0 : X Feb 3 02:08:12 host kernel: inetd 7 S 7FFF 4932 229 1 235 224 Feb 3 02:08:12 host kernel:sig: 0 : X Feb 3 02:08:12 host kernel: nmbd 14 S C0325EF8 5988 235 1 237 229 Feb 3 02:08:12 host kernel:sig: 0 1080 : X Feb 3 02:08:12 host kernel: smbd 15 S 7FFF 6272 237 1 4005 244 235 Feb 3 02:08:12 host kernel:sig: 0 1080 : X Feb 3 02:08:12 host kernel: sshd 16 S 7FFF 5252 244 1 4483 249 237 Feb 3 02:08:12 host kernel:sig: 0 : X Feb 3 02:08:12 host kernel: atd 17 S C0F13F78 5732 249 1 253 244 Feb 3 02:08:12 host kernel:sig: 0 : X Feb 3 02:08:12 host kernel: cron 19 S C0CA7F78 3120 253 1 261 249 Feb 3 02:08:12 host kernel:sig: 0 : X Feb 3 02:08:12 host kernel: apache22 S C0B1BEF8 5508 261 1 1521 267 253 Feb 3 02:08:12 host kernel:sig: 0 : X Feb 3 02:08:12 host kernel: getty 21 S 7FFF 5448 267 1 268 261 Feb 3 02:08:12 host kernel:sig: 0 : X Feb 3 02:08:12 host kernel: getty 23 S 7FFF 0 268 1 269 267 Feb 3 02:08:12 host kernel:sig: 0 : X Feb 3 02:08:12 host kernel: getty 24 S 7FFF 2720 269 1 270 268 Feb 3 02:08:12 host kernel:sig: 0 : X Feb 3 02:08:12 host kernel: getty 25 S 7FFF20 270 1 4185 269 Feb 3 02:08:12 host kernel:sig: 0 : X Feb 3 02:08:12 host kernel: apache26 S C0A9BE74 5316 271 261 272 Feb 3 02:08:12 host kernel:sig: 0 : X Feb 3 02:08:12 host kernel: apache27 S C0A93E74 6064 272 261 273 271 Feb 3 02:08:12 host kernel:sig: 0 : X Feb 3 02:08:12 host kernel: apache28 S C0A87E74 6016 273 261 274 272 Feb 3 02:08:12 host kernel:sig: 0 : X Feb 3 02:08:12 host kernel: apache29 S C0A7DE74 6016 274 261 275 273 Feb 3 02:08:12 host kernel:sig: 0 : X Feb 3 02:08:12 host kernel: apache30 S C0A73E74 5936 275 261 1517 274 Feb 3 02:08:12 host kernel:sig: 0 : X Feb 3 02:08:12 host kernel: apache41 S C0C5DE74 5
crash
After a local crash I can't install/remove some (n=?) packages: pumuckl:~# dpkg -i isdnutils_3.1pre1b-22.deb (Reading database ... 87745 files and directories currently installed.) Preparing to replace isdnutils 1:3.1pre1b-22 (using isdnutils_3.1pre1b-22.deb) ... Checking whether you need the ipppd package... Unpacking replacement isdnutils ... dpkg: error processing isdnutils_3.1pre1b-22.deb (--install): dpkg: warning - old post-removal script killed by signal (Segmentation fault) dpkg: error while cleaning up: subprocess post-removal script killed by signal (Segmentation fault) Errors were encountered while processing: isdnutils_3.1pre1b-22.deb How can I fix this? -- Hans Gubitz <[EMAIL PROTECTED]>
[crash]
> "Karl" == Karl M Hegbloom <[EMAIL PROTECTED]> writes:
Karl> When XEmacs starts, it says:
Karl> /usr/local/src/XEmacs/xemacs-21.2/src/xemacs: Symbol `toggleClassRec'
has different size in shared object, consider re-linking
Karl> /usr/local/src/XEmacs/xemacs-21.2/src/xemacs: Symbol `labelClassRec'
has different size in shared object, consider re-linking
Known problem, grep for `toggleClassRec' in the xemacs-beta archvies.
Karl> Hey, in /etc/ld.so.conf, the Xaw3d lib is listed FIRST, at
Karl> the top of the file. I bet that's what's wrong. Do yous
Karl> think so?
Yes and no. This is what is supposed to happen. libXaw3d is a
"drop-in" replacement for libXaw. If you only use the public
interface, no problem. If you subclass, and thus must use the private
interfaces, you get hosed. I don't see any way around it given the
way the Xaw3d library was designed; I think you are going to get stuck
with multiple versions of XEmacs, one for each version of the fancy
widgets. (You might be able to avoid multiple XEmacs packages by
dynamically detecting the libraries and loading XEmacs-Xaw*-shim.so
modules, but I don't know how to do that, if it is possible.)
It is obviously intended to be used so that apps which do no
subclassing get 3D widgets by default. Such apps will not be broken
no matter which link-compatible Xaw3d is used. Probably you, as
Debian maintainer for XEmacs, are expected to use xaw-wrappers to
intervene with ld.so, since XEmacs _does_ do subclassing.
(Disclaimer: I'm just guessing based on the name "xaw-wrappers".)
Karl> Should I report this as a bug against the Debian
Karl> Xaw3d package? I think that's the correct course of action
Karl> here. I'm starting to think I ought not send this after
Karl> all...
Actually, this is a well-known problem. Reviewing the last couple of
months' traffic will show that this came up a lot. Some people do
think it's a Debian design bug, I have no opinion.
As of a few days ago, this worked properly for me with the
then-current Debian potato and the then-current XEmacs CVS checkout.
The current plan (as I understand it, either read the autoconf source
for ./configure or ask Daniel Pittman <[EMAIL PROTECTED]> for accurate
info) is to look for Xaw{3d,NeXt,xpm,...}, if found, link for them
explicitly (my ld line says -lXaw3d). It looks to me like in your
case it found them but did not link explicitly, so you may not have
the most recent XEmacs.
The patches to ./configure.in are only about 10 days old; make sure
everything is current, do a make clean (if you have real cojones, do a
make distclean; I don't think XEmacs uses too much auto* technology,
so probably everything will get regenerated even if you don't have
automake etc).
--
University of TsukubaTennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
_ _ _ _
What are those straight lines for? "XEmacs rules."
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
crash?
I am running unstable (also kernel 2.4.3). I was exporting a display and runnning a second instance of kde on a remote machine (seperate user). When I came back, my computer was very slow (almost all my 256MB RAM used, way more than normal). I closed everything and tried to get out of kde/X (at this time the remote computer had already logged off, etc). I eventually got to a black screen with an immobile mouse and an unresponsive keyboard. I had to reboot. I am not sure that the display export had anything to do with the "crash". Did I do something wrong? My computer hasn't had any problems like this for a long time (and I have had 2.4.2/3 & debian unstable for at least a month). Thanks for any advice, Jeff Davis
Crash.
I have installed Potato. Sometimes my computer hangs up. There appears: Unable to handle kernel NULL pointer dereference at virtual address... and so on. When I reboot, e2fsck starts checking something, but fails. I tried to run fsck manually. Sometimes it works, but not always. After all, if I try to boot from Debian GNU/Linux Potato CD, I get the same message: Unable to handle..., registers, stack and so on. Could you help me, please.
unexplained crash
Hello, Yesterday SSH on my desktop PC running Ubuntu 20.04 became unresponsive. The machine was responding to ping and "telnet 22" was briefly connecting before connection closed. The graphical login prompt was visible, but when I tried to log in, it threw me to the text console. No login prompt on any virtual consoles and Ctrl-Alt-Del did nothing. There is no information logged in wtmp, kern.log and dmesg. Nothing interesting in auth.log The last 40 lines from syslog look as below: Nov 16 17:04:23 ubu20 systemd[1]: session-5089.scope: Succeeded. Nov 16 17:04:33 ubu20 systemd[1]: Stopping User Manager for UID 0... Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Main User Target. Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Basic System. Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Paths. Nov 16 17:04:33 ubu20 systemd[1259208]: ubuntu-report.path: Succeeded. Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped Pending report trigger for Ubuntu Report. Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Sockets. Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Timers. Nov 16 17:04:33 ubu20 systemd[1259208]: dbus.socket: Succeeded. Nov 16 17:04:33 ubu20 systemd[1259208]: Closed D-Bus User Message Bus Socket. Nov 16 17:04:33 ubu20 systemd[1259208]: dirmngr.socket: Succeeded. Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG network certificate management daemon. Nov 16 17:04:33 ubu20 systemd[1259208]: gpg-agent-browser.socket: Succeeded. Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers). Nov 16 17:04:33 ubu20 systemd[1259208]: gpg-agent-extra.socket: Succeeded. Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG cryptographic agent and passphrase cache (restricted). Nov 16 17:04:33 ubu20 systemd[1259208]: gpg-agent-ssh.socket: Succeeded. Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG cryptographic agent (ssh-agent emulation). Nov 16 17:04:33 ubu20 systemd[1259208]: gpg-agent.socket: Succeeded. Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG cryptographic agent and passphrase cache. Nov 16 17:04:33 ubu20 systemd[1259208]: pk-debconf-helper.socket: Succeeded. Nov 16 17:04:33 ubu20 systemd[1259208]: Closed debconf communication socket. Nov 16 17:04:33 ubu20 systemd[1259208]: snapd.session-agent.socket: Succeeded. Nov 16 17:04:33 ubu20 systemd[1259208]: Closed REST API socket for snapd user session agent. Nov 16 17:04:33 ubu20 systemd[1259208]: Reached target Shutdown. Nov 16 17:04:33 ubu20 systemd[1259208]: systemd-exit.service: Succeeded. Nov 16 17:04:33 ubu20 systemd[1259208]: Finished Exit the Session. Nov 16 17:04:33 ubu20 systemd[1259208]: Reached target Exit the Session. Nov 16 17:04:33 ubu20 systemd[1]: user@0.service: Succeeded. Nov 16 17:04:33 ubu20 systemd[1]: Stopped User Manager for UID 0. Nov 16 17:04:33 ubu20 systemd[1]: Stopping User Runtime Directory /run/user/0... Nov 16 17:04:33 ubu20 systemd[2567]: run-user-0.mount: Succeeded. Nov 16 17:04:33 ubu20 systemd[1294]: run-user-0.mount: Succeeded. Nov 16 17:04:33 ubu20 systemd[1]: run-user-0.mount: Succeeded. Nov 16 17:04:33 ubu20 systemd[1]: user-runtime-dir@0.service: Succeeded. Nov 16 17:04:33 ubu20 systemd[1]: Stopped User Runtime Directory /run/user/0. Nov 16 17:04:33 ubu20 systemd[1]: Removed slice User Slice of UID 0. Does anybody have an idea what could have happened? Regards, Adam
Nautilus crash
Hi, Anyone is having problem with Nautilus crashing on launch using Buster ? Thanks -- Polyna-Maude R.-Summerside -Be smart, Be wise, Support opensource development
weekly crash
This lockup was different. System totally froze, clock stopped too while scrolling a long message from the coco mailing list using tbird. Gave it a 5 second tap on the reset button but the reset was delayed by the 30 second lag before it cleared the screen and dropped into the bios to reboot. Running normally for this system after the reboot. Data point? DIIK. Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
GIMP Crash
Here is the bug info
```
GNU Image Manipulation Program version 2.10.8
git-describe: GIMP_2_10_6-294-ga967e8d2c2
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 8.2.0-13'
--with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-8
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-libmpx --enable-plugin
--enable-default-pie --with-system-zlib --with-target-system-zlib
--enable-objc-gc=auto --enable-multiarch --disable-werror
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32
--enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none
--without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 8.2.0 (Debian 8.2.0-13)
using GEGL version 0.4.12 (compiled against version 0.4.12)
using GLib version 2.58.3 (compiled against version 2.58.1)
using GdkPixbuf version 2.38.1 (compiled against version 2.38.0)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)
```
> fatal error: Segmentation fault
Stack trace:
```
# Stack traces obtained from PID 16588 - Thread 16588 #
[New LWP 16589]
[New LWP 16590]
[New LWP 16592]
[New LWP 16593]
[New LWP 16605]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (nbytes=256, buf=0x7ffd5bc55ed0, fd=16) at
../sysdeps/unix/sysv/linux/read.c:26
Id Target Id Frame
* 1Thread 0x7a5aacd05e00 (LWP 16588) "gimp-2.10" __libc_read
(nbytes=256, buf=0x7ffd5bc55ed0, fd=16) at
../sysdeps/unix/sysv/linux/read.c:26
2Thread 0x7a5aab4ad700 (LWP 16589) "gmain" 0x7a5aae982819
in __GI___poll (fds=0x581ef2edf1c0, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
3Thread 0x7a5aaa957700 (LWP 16590) "gdbus" 0x7a5aae982819
in __GI___poll (fds=0x581ef2eb76a0, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
4Thread 0x7a5a97ac8700 (LWP 16592) "async" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
5Thread 0x7a5a972c7700 (LWP 16593) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
6Thread 0x7a5a95e51700 (LWP 16605) "swap writer" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Thread 6 (Thread 0x7a5a95e51700 (LWP 16605)):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1 0x7a5aaec97f9f in g_cond_wait () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x7a5aaf3310cd in ?? () from
/usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0
No symbol table info available.
#3 0x7a5aaec76415 in ?? () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7a5aaea5efa3 in start_thread (arg=) at
pthread_create.c:486
ret =
pd =
now =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {134529480464128,
4780554623439464532, 140726143112750, 140726143112751, 134529480464128,
96889976575168, -5268408010271233964, -5268459145313916844}, mask_was_saved
= 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup =
0x0, canceltype = 0}}}
not_first_call =
#5 0x7a5aae98d4cf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
No locals.
Thread 5 (Thread 0x7a5a972c7700 (LWP 16593)):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1 0x7a5aaec97f9f in g_cond_wait () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x581ef15b6423 in ?? ()
No symbol table info available.
#3 0x7a5aaec76415 in ?? () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7a5aaea5efa3 in start_thread (arg=) at
pthread_create.c:486
ret =
pd =
now =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {134529501918976,
4780554623439464532, 140726143118094, 140726143118095, 134529501918976,
96889925393344, -5268403142999545772, -5268459145313916844}, mask_was_saved
= 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup =
0x0, canceltype = 0}}}
not_first_cal
GIMP Crash
I was working with the Gnu Image Manipulation Program yesterday when a segmentation fault occurred. Attached is the information spit out in association with the event. Please let me know what additional information you need from me and I will pass it along. - Adam Haas ``` GNU Image Manipulation Program version 2.10.8 git-describe: GIMP_2_10_6-294-ga967e8d2c2 C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 8.2.0-13' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-8 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 8.2.0 (Debian 8.2.0-13) using GEGL version 0.4.14 (compiled against version 0.4.12) using GLib version 2.58.3 (compiled against version 2.58.1) using GdkPixbuf version 2.38.1 (compiled against version 2.38.0) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.42.3 (compiled against version 1.42.3) using Fontconfig version 2.13.1 (compiled against version 2.13.1) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > fatal error: Segmentation fault Stack trace: ``` /usr/lib/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x397)[0x7efecef12e27] gimp-2.10(+0xd14a0)[0x564d3eac34a0] gimp-2.10(+0xd18d8)[0x564d3eac38d8] gimp-2.10(+0xd2037)[0x564d3eac4037] /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7efece20e730] /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0(+0x179e4)[0x7efecee749e4] /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0(pango_attribute_copy+0xf)[0x7efecee742df] /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0(pango_attr_list_copy+0x28)[0x7efecee74c98] /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0(+0x20697)[0x7efecee7d697] /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0(+0x24143)[0x7efecee81143] /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0(+0x26302)[0x7efecee83302] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x12802a)[0x7efecf15a02a] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0xb1)[0x7efece4d4b91] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x244ec)[0x7efece4e84ec] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xd8e)[0x7efece4f125e] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_by_name+0x4b4)[0x7efece4f1df4] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x19f4e8)[0x7efecf1d14e8] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x84a35)[0x7efecf0b6a35] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0xb1)[0x7efece4d4b91] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x244ec)[0x7efece4e84ec] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xd8e)[0x7efece4f125e] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_by_name+0x4b4)[0x7efece4f1df4] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x19f4e8)[0x7efecf1d14e8] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0xf53bc)[0x7efecf1273bc] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0xb1)[0x7efece4d4b91] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x244ec)[0x7efece4e84ec] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xd8e)[0x7efece4f125e] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_by_name+0x4b4)[0x7efece4f1df4] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x19f4e8)[0x7efecf1d14e8] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x84a35)[0x7efecf0b6a35] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x1a52d2)[0x7efecf1d72d2] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0xb1)[0x7efece4d4b91] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x244ec)[0x7efece4e84ec] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xd8e)[0x7efece4f125e] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_by_name+0x4b4)[0x7efece4f1df4] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x19f4e8)[0x7efecf1d14e8] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x84a35)[0x7efecf0b6a35] /usr/l
libreoffice crash
Hi, I upgraded my system to Buster finally but after that then LibreOffice crashes on me. I have tried to uninstall it and reinstall, no luck there. I tried as a different user, same crash there. I am out of ideas. I have pasted an strace -f of opening localc from the command line https://pastebin.com/Ev55tVUH Any ideas on what could be the problem here? TIA, Oli
Panel Crash
Hi list, I've make an upgrade from potato to woody and now the gnome panel at startup crashes (segmentation fault) any idea on what i should check? pch ***Internet Email Confidentiality Footer*** Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of my firm shall be understood as neither given nor endorsed by it.
Crash recovery.
Hi Everyone, Had a fun experience today. Debian hung and refused any input. The only option I had was to power it down. The reboot failed dropping me at the command prompt to run fsck manually. This fixed this and that and place a number of things in to /lost+found. Rebooting again and this time we get stuck starting syslogd. Recreating the dir /var/run got me past that but there are obviously still issues from the problem. What I need to know is a way to either work out what was crunched and placed in /lost+found, whether or not knowing this is good enough, and some way of checking the current status of the system to repair what is now broken. Any input is appreciated. -- -Paul de Kievit
kernel crash.
I'm trying to share my PCMCIA multifunctional card (Psion Gold Card Netglobal 56K+10/100Mb CardBus, PCMCIA 3.1.22, debian 2.2r2, kernel 2.2.17) with an another debian computer on my network (2 machines on network, my laptop and duron based machine with crossover cable). PPPd seems to die and then the network hangs on a tx timeout, resulting in a complete freeze. Normally I just reset and try again with later releases of the drivers, however tonight I left the screen to see if it would unfreeze. I looked in an hour later and there was a kernel oops/crash on the screen (I'd been watching the eth0 debug messages on screen with tail -f /var/log/syslog). I seem to remember Aiee Mmmm killed interrupt handler.Mmmm.. killed idle task ? My question is as the machine has hung how do I get a copy of the crash data (dump ?). Is it stored somewhere or should I resort to pen and paper ? What are the most important bits to report ? Where do I report it, PCMCIA 3.1.22 bug, pppd bug, kernel bug ? Help ! Derm.
gmenu crash
Hi All I know that there is a bug reported to gnome.org for gmenu Nº 29855. If you are root and try to add a new menu item the application crashes even when you only select the point where you can insert the new item. Though in my case in a previous instalation (but wihtout USB support for a 2.2.17 Kernel) the error did not occur. I don`t know if the problem is resolved by gnome.org but i want to know if there is a config file or somehing where i can modify manually the actual menu item for the desktop. thanks --- Jose Fernando Carvajal Vión SOLUZIONA Software Factory Servicios Profesionales de Unión Fenosa C/ Pedro Teixeira, 8 - 28020 Madrid Teléfono: +34 91 555 33 61 Fax: +34 91 597 05 62 mailto:[EMAIL PROTECTED] http://www.uf-isf.es ---
KDM crash
I was working in KDE 2.0 fine. I had installed licq via dselect. I run Debian 2.2 r2. I tried to bring up the menu editor to make a link on it to licq. But everytime I clicked on the menu editor, it would not come up. Stupidly I hit ctrl+alt+backspace to get out of kde so I could restart the X server. KDM started to come up the the screen went back to console mode. I rebooted, but the same thing happens. I used dselect to un-install kdm and then reinstall it, no luck. I installed GDM, it comes up on boot, but when I try to log in, I choose KDE as the session to load, but it starts to load, then kicks me back out to GDM. If I type startx it x comes up, but without a window manager, just the grey screen. I've looked in the system error logs, but find nothing. If I type kdm it just gives me another prompt, no errors. Wayne
Re: Crash?!?
Sven Burgener <[EMAIL PROTECTED]> writes: [...] > Today, I noticed the following (rather long) dump in /var/log/syslog. > It doesn't look like a usual Oops, so I am unsure what caused this. [...] > Feb 3 02:08:12 host kernel: > freesibling > Feb 3 02:08:12 host kernel: task PCstack pid father > child younger older > Feb 3 02:08:12 host kernel: init 1 S C17F9EF8 5136 1 0 > 4438 [...] I suggest posting this to linux-kernel (http://www.tux.org/lkml). moritz -- Moritz Schulte <[EMAIL PROTECTED]> http://www.chaosdorf.de/moritz/ Debian/GNU supporter - http://www.debian.org/ http://www.gnu.org/ GPG fingerprint = 3A14 3923 15BE FD57 FC06 B501 0841 2D7B 6F98 4199
Crash-URL
Hello I once saw a link on a page that caused windows to crash immediately when clicked on. It was stated on that very page that this would happen. So then I tried it and it worked! Unfortunately I lost the URL. :*( Anyone know of this? Perhaps it's something like "NUL" or so which supposedly is a reserved name under windows? TIA! Sven
Crash-URL
Hello I once saw a link on a page that caused windows to crash immediately when clicked on. It was stated on that very page that this would happen. So then I tried it and it worked! Unfortunately I lost the URL. :*( Anyone know of this? Perhaps it's something like "NUL" or so which supposedly is a reserved name under windows? TIA! Sven
crash diagnostics
I am still having occasional kernel panics and don't know why. Today an Oops happened some hours before the panic (when I did 'make zImage'). The Oops left the kswaps daemon as zombie and I had to reboot the system. Following is the output of the Oops. I would really appreciate if somebody could give me any hint what could be wrong with my Debian system. I can't analyze the data with ksymoops because I couldn't compile ksymoops and I probably would experience another crash if I would try it. ## Jan 28 16:28:43 quod kernel: Unable to handle kernel paging request at virtual address 858994b4 Jan 28 16:28:43 quod kernel: current->tss.cr3 = 00101000, %cr3 = 00101000 Jan 28 16:28:43 quod kernel: *pde = Jan 28 16:28:43 quod kernel: Oops: Jan 28 16:28:43 quod kernel: CPU:0 Jan 28 16:28:43 quod kernel: EIP:0010:[] Jan 28 16:28:43 quod kernel: EFLAGS: 00010287 Jan 28 16:28:43 quod kernel: eax: 858994a0 ebx: c02dc6b0 ecx: 0006 edx: ffe0 Jan 28 16:28:43 quod kernel: esi: 858994a0 edi: c5899500 ebp: c02dc6b0 esp: c000dfa8 Jan 28 16:28:43 quod kernel: ds: 0018 es: 0018 ss: 0018 Jan 28 16:28:43 quod kernel: Process kswapd (pid: 4, process nr: 4, stackpage=c000d000) Jan 28 16:28:43 quod kernel: Stack: 0030 c000c000 c0119fd2 c02dc6b0 000d 0006 c011ed13 0006 Jan 28 16:28:43 quod kernel:0030 c01a9078 c000c1c1 c011edbf 0030 0f00 c0003fb4 Jan 28 16:28:43 quod kernel:c0106000 9000 c0106513 0f00 c01d5fd8 Jan 28 16:28:43 quod kernel: Call Trace: [] [] [] [] [] [] Jan 28 16:28:43 quod kernel: Code: 8b 76 14 83 78 20 00 75 06 f6 40 18 46 74 13 6a 00 e8 4c 01 ## I am running a kernel 2.2.10 with Hamm and the newer stuff needed for this kernel. I am guessing my problem is hardware dependend and I am going to exchange my quodry modules if I can't find any other cause for this troubles. I am having this kernel panics since my hosting provider had a power interruption. What kind of PC HW could get damaged by a power interruption resulting in such a behaviour I described? TIA, Werner
Re: crash
on Sat, Sep 22, 2001 at 11:23:58PM +0200, Hans Gubitz ([EMAIL PROTECTED]) wrote: > After a local crash I can't install/remove some (n=?) packages: > > pumuckl:~# dpkg -i isdnutils_3.1pre1b-22.deb > (Reading database ... 87745 files and directories currently > installed.) > Preparing to replace isdnutils 1:3.1pre1b-22 (using > isdnutils_3.1pre1b-22.deb) ... > Checking whether you need the ipppd package... > Unpacking replacement isdnutils ... > dpkg: error processing isdnutils_3.1pre1b-22.deb (--install): > dpkg: warning - old post-removal script killed by signal > (Segmentation fault) > > dpkg: error while cleaning up: > subprocess post-removal script killed by signal (Segmentation fault) > Errors were encountered while processing: >isdnutils_3.1pre1b-22.deb > > How can I fix this? Examine the script manually: /var/lib/dpkg/info/isdnutils.postrem If you can identify the specific problem with the script, modify it manually and try re-running the removal. Peace. -- Karsten M. Self http://kmself.home.netcom.com/ What part of "Gestalt" don't you understand? Home of the brave http://gestalt-system.sourceforge.net/Land of the free Free Dmitry! Boycott Adobe! Repeal the DMCA! http://www.freesklyarov.org Geek for Hire http://kmself.home.netcom.com/resume.html pgpQyBoyFAZLH.pgp Description: PGP signature
Re: crash
On Sat, Sep 22, 2001 at 03:55:33PM -0700, Karsten M. Self wrote: > on Sat, Sep 22, 2001 at 11:23:58PM +0200, Hans Gubitz ([EMAIL PROTECTED]) > wrote: > > After a local crash I can't install/remove some (n=?) packages: .. > > > > dpkg: error while cleaning up: > > subprocess post-removal script killed by signal (Segmentation fault) > > Errors were encountered while processing: > >isdnutils_3.1pre1b-22.deb > Examine the script manually: > > /var/lib/dpkg/info/isdnutils.postrem > I can't remove|install packages, that have a line like . /usr/share/debconf/confmodule in .postrm (apt-get still works on packages without this line). For the same reason I can't reinstall debconf. Hans Gubitz -- Hans Gubitz <[EMAIL PROTECTED]>
Re: crash
On Sun, Sep 23, 2001 at 11:31:09AM +0200, Hans Gubitz wrote: > > > After a local crash I can't install/remove some (n=?) packages: > > Examine the script manually: > > /var/lib/dpkg/info/isdnutils.postrem > > > I can't remove|install packages, that have a line like > . /usr/share/debconf/confmodule > in .postrm > > (apt-get still works on packages without this line). > > For the same reason I can't reinstall debconf. I guess you can still reboot your system. If so reboot system with rescue disk. Mount current system partition on harddisk to somewhere like /target. Run dpkg --root=/target -i to install working version of debconf to the harddisk using chroot trick. Some forcing option may be helpful here. (man dpkg) Life is easier if you have some partition whech can be overwritten. Then install minimum debian system to there to do above operation. Old swap partition may be a good candidate after fdisk. Then you have access to more command. Good luck :-) -- ~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ + Osamu Aoki <[EMAIL PROTECTED]>, GnuPG-key: 1024D/D5DE453D + + My debian quick-reference, http://www.aokiconsulting.com/quick/+
Re: crash
Thanks to all. I successfully reinstalled perl-base and debconf in this order. I think I fixed all the other problems in the same manner, Hans Gubitz -- Hans Gubitz <[EMAIL PROTECTED]>
Crash postmortem.
I've been experiencing some system instability lately. The system crashes like once a week or something. Ctrl-Alt-Delete has no effect. And I can't even ssh in from another host to do a graceful shutdown. Of course I'm not asking any of you to analyze my problem with this little informatation. Rather I'm asking for tips an general methods for analyzing crashes after the fact. Or maybe some prog that monitor all processes and warns me when something is starting to go haywire? -- oivvio polite cell +46 (0)709 30 40 30 / phone +46 (0)8 669 64 18 / fax +46 (0)8 84 00 18 varvsgatan 10A / s-117 29 stockholm / sweden
konqueror crash
Hi all, After a couple years working perfectly, kde session restoring begun to fail a few weeks ago, on my debian/testing laptop. At the user session opening, every konqueror instance, saved in the previous session, crashes. Here included the backtrace, from the crash window panel. lHowever, any new konqueror instaces start flawlessly. Any idea? thank you for your help -- Pol enc. (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1232545568 (LWP 10458)] [KCrash handler] #5 0x in ?? () #6 0xb5b6d940 in KonqKfmIconView::doOpenURL () from /usr/lib/kde3/konq_iconview.so #7 0xb65d6a0c in KonqDirPart::openURL () from /usr/lib/libkonq.so.4 #8 0xb66a9960 in KonqView::openURL () from /usr/lib/libkdeinit_konqueror.so #9 0xb66b537c in KonqMainWindow::openView () from /usr/lib/libkdeinit_konqueror.so #10 0xb66c0879 in KonqViewManager::loadItem () from /usr/lib/libkdeinit_konqueror.so #11 0xb66c0ec0 in KonqViewManager::loadItem () from /usr/lib/libkdeinit_konqueror.so #12 0xb66c0491 in KonqViewManager::loadItem () from /usr/lib/libkdeinit_konqueror.so #13 0xb66c2f67 in KonqViewManager::loadViewProfile () from /usr/lib/libkdeinit_konqueror.so #14 0xb66c3dcb in KonqMainWindow::readProperties () from /usr/lib/libkdeinit_konqueror.so #15 0xb6d54ca2 in KMainWindow::readPropertiesInternal () from /usr/lib/libkdeui.so.4 #16 0xb6d54e22 in KMainWindow::restore () from /usr/lib/libkdeui.so.4 #17 0xb66caf41 in kdemain () from /usr/lib/libkdeinit_konqueror.so #18 0xb7f38524 in kdeinitmain () from /usr/lib/kde3/konqueror.so #19 0x0804e457 in ?? () #20 0x0003 in ?? () #21 0x0807bda8 in ?? () #22 0x0001 in ?? () #23 0x in ?? () -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Eclipse crash
Hi, I am desperately trying to get Eclipse 3.2 working on my laptop. I upgrated java to JDK1.6 but it did not change anything. Crashes are not predicable and could happen at anytime. Starting Eclipse is not a problem. Buf, after a couple of minutes, I always get this kind of message: # An unexpected error has been detected by Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00010203, pid=7256, tid=1075764144 # # Java VM: Java HotSpot(TM) Client VM (1.6.0-b105 mixed mode, sharing) # Problematic frame: # C 0x00010203 # # An error report file with more information is saved as hs_err_pid7256.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # I read a lot of pages but none solved my problem. Any help would be gratefully appreciated. As I am quite new to Debian, I maybe forgot something important. Attached you can find the Eclipse last window before exit. If you need more information, kindly ask me. Thanks and regards, christian
firefox crash
Greetings, Can somebody please confirm the following crash in Debian Firefox 1.0.4-2: Load www.nbntv.com.au then open the forum (botton of the page in the middle) in another tab. 9 times out of 10 the forum crashes the browser for me. Thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
hugin crash
Hello, I am currently running lenny. hugin was working well when I tried last time, say about 10 days back. Today, when I tried it crashed with the following output : ~$ hugin Panorama obj created /usr/share/locale *** glibc detected *** hugin: double free or corruption (out): 0x09027f90 *** === Backtrace: = /lib/libc.so.6[0xb6e36e15] /lib/libc.so.6(cfree+0x90)[0xb6e3a8e0] /usr/lib/libglib-2.0.so.0(g_free+0x31)[0xb71494a1] /usr/lib/libwx_gtk2u_core-2.6.so.0[0xb7c18bfe] /usr/lib/libwx_gtk2u_core-2.6.so.0(_ZN8wxButton10SetDefaultEv+0x74)[0xb7c18cf4] /usr/lib/libwx_gtk2u_xrc-2.6.so.0(_ZN18wxButtonXmlHandler16DoCreateResourceEv+0x299)[0xb7f04809] /usr/lib/libwx_gtk2u_xrc-2.6.so.0(_ZN20wxXmlResourceHandler14CreateResourceEP9wxXmlNodeP8wxObjectS3_+0x1b1)[0xb7f45761] /usr/lib/libwx_gtk2u_xrc-2.6.so.0(_ZN13wxXmlResource17CreateResFromNodeEP9wxXmlNodeP8wxObjectS3_P20wxXmlResourceHandler+0x457)[0xb7f479c7] /usr/lib/libwx_gtk2u_xrc-2.6.so.0(_ZN17wxSizerXmlHandler16Handle_sizeritemEv+0xc4)[0xb7f29ff4] /usr/lib/libwx_gtk2u_xrc-2.6.so.0(_ZN17wxSizerXmlHandler16DoCreateResourceEv+0x3e)[0xb7f2a53e] /usr/lib/libwx_gtk2u_xrc-2.6.so.0(_ZN20wxXmlResourceHandler14CreateResourceEP9wxXmlNodeP8wxObjectS3_+0x1b1)[0xb7f45761] /usr/lib/libwx_gtk2u_xrc-2.6.so.0(_ZN13wxXmlResource17CreateResFromNodeEP9wxXmlNodeP8wxObjectS3_P20wxXmlResourceHandler+0x48a)[0xb7f479fa] /usr/lib/libwx_gtk2u_xrc-2.6.so.0(_ZN20wxXmlResourceHandler14CreateChildrenEP8wxObjectb+0x11c)[0xb7f47d0c] /usr/lib/libwx_gtk2u_xrc-2.6.so.0(_ZN17wxSizerXmlHandler12Handle_sizerEv+0x12d)[0xb7f2817d] /usr/lib/libwx_gtk2u_xrc-2.6.so.0(_ZN17wxSizerXmlHandler16DoCreateResourceEv+0x6e)[0xb7f2a56e] /usr/lib/libwx_gtk2u_xrc-2.6.so.0(_ZN20wxXmlResourceHandler14CreateResourceEP9wxXmlNodeP8wxObjectS3_+0x1b1)[0xb7f45761] /usr/lib/libwx_gtk2u_xrc-2.6.so.0(_ZN13wxXmlResource17CreateResFromNodeEP9wxXmlNodeP8wxObjectS3_P20wxXmlResourceHandler+0x457)[0xb7f479c7] /usr/lib/libwx_gtk2u_xrc-2.6.so.0(_ZN17wxSizerXmlHandler16Handle_sizeritemEv+0xc4)[0xb7f29ff4] /usr/lib/libwx_gtk2u_xrc-2.6.so.0(_ZN17wxSizerXmlHandler16DoCreateResourceEv+0x3e)[0xb7f2a53e] /usr/lib/libwx_gtk2u_xrc-2.6.so.0(_ZN20wxXmlResourceHandler14CreateResourceEP9wxXmlNodeP8wxObjectS3_+0x1b1)[0xb7f45761] /usr/lib/libwx_gtk2u_xrc-2.6.so.0(_ZN13wxXmlResource17CreateResFromNodeEP9wxXmlNodeP8wxObjectS3_P20wxXmlResourceHandler+0x48a)[0xb7f479fa] /usr/lib/libwx_gtk2u_xrc-2.6.so.0(_ZN20wxXmlResourceHandler14CreateChildrenEP8wxObjectb+0x11c)[0xb7f47d0c] /usr/lib/libwx_gtk2u_xrc-2.6.so.0(_ZN17wxSizerXmlHandler12Handle_sizerEv+0x12d)[0xb7f2817d] /usr/lib/libwx_gtk2u_xrc-2.6.so.0(_ZN17wxSizerXmlHandler16DoCreateResourceEv+0x6e)[0xb7f2a56e] /usr/lib/libwx_gtk2u_xrc-2.6.so.0(_ZN20wxXmlResourceHandler14CreateResourceEP9wxXmlNodeP8wxObjectS3_+0x1b1)[0xb7f45761] /usr/lib/libwx_gtk2u_xrc-2.6.so.0(_ZN13wxXmlResource17CreateResFromNodeEP9wxXmlNodeP8wxObjectS3_P20wxXmlResourceHandler+0x457)[0xb7f479c7] /usr/lib/libwx_gtk2u_xrc-2.6.so.0(_ZN20wxXmlResourceHandler14CreateChildrenEP8wxObjectb+0x11c)[0xb7f47d0c] /usr/lib/libwx_gtk2u_xrc-2.6.so.0(_ZN17wxFrameXmlHandler16DoCreateResourceEv+0x47f)[0xb7f107af] /usr/lib/libwx_gtk2u_xrc-2.6.so.0(_ZN20wxXmlResourceHandler14CreateResourceEP9wxXmlNodeP8wxObjectS3_+0x1b1)[0xb7f45761] /usr/lib/libwx_gtk2u_xrc-2.6.so.0(_ZN13wxXmlResource17CreateResFromNodeEP9wxXmlNodeP8wxObjectS3_P20wxXmlResourceHandler+0x457)[0xb7f479c7] /usr/lib/libwx_gtk2u_xrc-2.6.so.0(_ZN13wxXmlResource9LoadFrameEP7wxFrameP8wxWindowRK8wxString+0x7d)[0xb7f48afd] hugin[0x8131219] hugin[0x8079a9f] hugin[0x806013a] hugin(_ZN12wxAppConsole10CallOnInitEv+0x11)[0x8063571] /usr/lib/libwx_baseu-2.6.so.0(_Z7wxEntryRiPPw+0x40)[0xb79da430] /usr/lib/libwx_baseu-2.6.so.0(_Z7wxEntryRiPPc+0x36)[0xb79da506] hugin(__gxx_personality_v0+0x3d0)[0x805e540] /lib/libc.so.6(__libc_start_main+0xe0)[0xb6de3050] hugin(__gxx_personality_v0+0x291)[0x805e401] === Memory map: 08048000-0889 r-xp 08:01 43812 /usr/bin/hugin 0889-08892000 rw-p 00848000 08:01 43812 /usr/bin/hugin 08892000-093de000 rw-p 08892000 00:00 0 [heap] b650-b6521000 rw-p b650 00:00 0 b6521000-b660 ---p b6521000 00:00 0 b66fc000-b670b000 r--p 08:01 103309 /usr/share/fonts/truetype/ttf-bitstream-vera/VeraBd.ttf b670b000-b676b000 rw-s 00:08 884751 /SYSV (deleted) b676b000-b683d000 r-xp 08:01 103587 /usr/lib/libscim-1.0.so.8.2.3 b683d000-b684b000 rw-p 000d2000 08:01 103587 /usr/lib/libscim-1.0.so.8.2.3 b684b000-b68ab000 rw-s 00:08 851982 /SYSV (deleted) b68b3000-b68b6000 rw-s 00:08 1081360/SYSV (deleted) b68b6000-b68ba000 r-xp 08:01 80584 /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so b68ba000-b68bb000 rw-p 3000 08:01 80584 /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so b68bb000-b68cc000 r--p 08:01 103306 /usr/share/fonts/truetype/ttf-bitstream-vera/Vera.ttf b68cc000-b68ce000 r-xp 08:01 52716 /usr/lib/pango/1
firefox crash
I am running sid. After last update, firefox 1.5.dfsg+1.5.0.1-4 is crashing very often that in few sites. For example the following site also crashes. http://www.weather.com/weather/local/USCA1296?from=hrly_topnav_undeclared. Any body else is also experiencing this. -- L.V.Gandhi http://lvgandhi.tripod.com/ linux user No.205042
xdm crash
I have lost the ability to use xdm, run level 5, and would like to know how to restore it without reinstalling Debian. I can operate in run level 3 as long as I do not go into graphics. This is how it all happened. I downloaded some files using Debian and then transferred them to Windows because I wanted to save the files on a CD. After doing this, I tried to go back to Debian and got into run level 2. I then edited /etc/inittab, which had level 5 and changed it to level 3. Going into level 3, I tried to use startx, but got the following. startx No such file or directory: cannot stat /temp/.X11-unix, aborting _X11 TransSocketUNICConnect: Can't connect: error =111 giving up xinit: Connection refused (errno 111) : unable to connect to x sever xinit: No such process (errno 3). Server error I checked and I do have the command startx at /usr/X11R6/bin/startx. Any help would be appreciated.
X crash
Hello all, I did an apt-get dist-upgrade with "testing" in deb http (sources.list) and my X crashes. Can't anymore install task-x-window-system and other dependencies. What X can I install now? How to do? Sarimanok NetCourrier, votre bureau virtuel sur Internet : Mail, Agenda, Clubs, Toolbar... Une gamme d'outils gratuits et performants à votre service. Web/Wap : www.netcourrier.com Téléphone/Fax : 08 92 69 00 21 (0,34 E TTC/min - 2,21 F TTC/min) Minitel: 3615 NETCOURRIER (0,15 E TTC/min - 1,00 F TTC/min)
Re: [crash]
Karl M. Hegbloom wrote: > It linked against Xaw3d/libXaw, even though I told it `athena', not > `athena3d'... [snip] > % ldd /usr/local/src/XEmacs/xemacs-21.2/src/xemacs > libXaw.so.6 => /usr/X11R6/lib/Xaw3d/libXaw.so.6 (0x4001c000) It's linked against "libXaw.so.6". Exactly which "libXaw.so.6" will be used at run time depends upon first $LD_LIBRARY_PATH and then /etc/ld.so.cache. The problem is that only one of the libXaw's will work, i.e. the one which matches the headers with which XEmacs was compiled. > Hey, in /etc/ld.so.conf, the Xaw3d lib is listed FIRST, at the top of > the file. I bet that's what's wrong. Do yous think so? No. The bug is that the Xaw3d version of the library can actually be found somewhere under the name libXaw.so.6. > Should I report this as a bug against the Debian Xaw3d package? You should report the fact that the Xaw3d version is called "libXaw.so.6" as a Debian bug. It's not just Debian that has this bug, but that doesn't make it any less of a bug. If you look at your ldd output, you will notice that the dependencies all include the major version number. This is because different major versions are, at the binary level, completely different libraries. If a program was built with the headers for libX11.so.6, libX11.so.7 wouldn't be any more acceptable as a substitute than would libz.so.1. By the same token, libXaw3d.so.6 isn't an acceptable substitute for libXaw.so.6, so it shouldn't be available under the name libXaw.so.6. Not anywhere. If you want to support Xaw3d, then link with "-lXaw3d" so that the binaries explicitly require libXaw3d.so.6. It isn't hard to configure Xaw3d to look and feel like plain Xaw if you want it to. -- Glynn Clements <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Gimp Crash
G'Day, Unstable problem??? I can log longer run gimp-1.2 on a plain X (eg, using startx or *dm) it just crashes, if run from the gnome menu it displays the splash screen for a second then it disappears. If run from a terminal (aterm/xterm) it shows the splash screen then the terminal brings up a debugger type window. HOWEVER: If I run it via Xnest it works fine, no hassles. At first I thought it was the multiscreen but its not that, then I thought the windowmanager (I had changed from blackbox to windowmaker before it started happening) but it dosnt seem to matter what window manager it is. Does anyone have any ideas as to what can be done to fix it, its a neusense having to run a Xnest, and then if I want to access another window and shade Xnest, Xnest crashes (dont know the error it gives... only with gimp running however) Included below is a copy of the stack trace from gimp I cant understand how it would help any, but someone may find it usefull. -- 8< stack track gimp: fatal error: Segmentation fault gimp (pid:5621): [E]xit, [H]alt, show [S]tack trace or [P]roceed: S #0 0x4018d8b8 in g_on_error_stack_trace () from /usr/lib/libglib-1.2.so.0 #1 0x4018d7de in g_on_error_query () from /usr/lib/libglib-1.2.so.0 #2 0x080b3e3a in gimp_fatal_error () #3 0x08109236 in main () #4 0x402e97b8 in sigaction () from /lib/libc.so.6 #5 0x4032de44 in malloc () from /lib/libc.so.6 #6 0x401925f9 in g_malloc () from /usr/lib/libglib-1.2.so.0 #7 0x40192aef in g_mem_chunk_alloc () from /usr/lib/libglib-1.2.so.0 #8 0x400b347d in gtk_quit_add_full () from /usr/lib/libgtk-1.2.so.0 #9 0x400b364c in gtk_quit_add () from /usr/lib/libgtk-1.2.so.0 #10 0x400b3619 in gtk_quit_add_destroy () from /usr/lib/libgtk-1.2.so.0 #11 0x080c791b in gimp_context_get_standard () #12 0x0809a906 in context_manager_init () #13 0x0806e1e0 in app_init () #14 0x0806d453 in gimp_init () #15 0x081091de in main () #16 0x08162ed9 in user_install_verify () #17 0x081091a8 in main () #18 0x402d964f in __libc_start_main () from /lib/libc.so.6 -- 8< end stack track Notes about my system: Nvidia X11 driver, GIMP version 1.2.2 gimp Packages: Gimp-1.2, gimp1.2-nonfree, Gimp1.2-print, gtkam-gimp, libgimpprint1, libgimpprint4.1.99-a2, gimp-data-extras XFree86 version 4.1.0-14 ALSO just upgrade to the lastest in the package lists (1.2.3) and now all I get it 'gimp: fatal error: Segmentation fault' repeated, and it wont exit unless sent a SIGKILL (9) Any help will be appreciated. -- \\\ 8(o o)8 -ooO--(_)--Ooo- .-`~`-. | James Hook H O O K | [EMAIL PROTECTED] ~-._.-~ | http://hooksoft.8m.com -ooO---Ooo- ... Non Usefull Fact #37: Doc, Dopey, Sneezy, Happy, Grumpy, Sleepy and Bashful. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: crash?
on Wed, Apr 18, 2001 at 05:13:07PM -0700, Jeff Davis ([EMAIL PROTECTED]) wrote: > I am running unstable (also kernel 2.4.3). I was exporting a > display and runnning a second instance of kde on a remote machine > (seperate user). When I came back, my computer was very slow (almost > all my 256MB RAM used, way more than normal). Out-of-memory conditions can lead to a sluggish, and sometimes terminally swapped, system. Best thing to do is find and isolate the memory-hogging application and shut it down. > I closed everything and tried to get out of kde/X (at this time the > remote computer had already logged off, etc). Suggestions: - Switch to a virtual console window () rather than killing X. You're going to need a console anyway, and you can kill X from it. You might want to run 'screen' and get both a 'top' session and a shell prompt going. - Leave the remote connection open. It uses minimal overhead and is quite useful if you wedge the system. - Using top or other monitoring tools, start shutting down large processes. > I eventually got to a black screen with an immobile mouse and an > unresponsive keyboard. I had to reboot. Sometimes necessary, but often not. You'll also want to read up on the "magic sysrq" key combinations. I've got these taped up in strategic locations. > I am not sure that the display export had anything to do with the > "crash". Did I do something wrong? My computer hasn't had any > problems like this for a long time (and I have had 2.4.2/3 & debian > unstable for at least a month). Check your system logs for error messages, may be something there. Could just be userspace apps. You can set user limits (ulimit) to prevent runaway memory utilization. There's also low-memory cleanup support being added to the Linux kernel itself, though I believe this is still experimental and doesn't quite perform as expected or desired. -- Karsten M. Self http://kmself.home.netcom.com/ What part of "Gestalt" don't you understand? There is no K5 cabal http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org pgpVZy5duXT0S.pgp Description: PGP signature
Re: crash?
hi ya sometime netscape runs amockand need to be killed... ( what does "ps auxw" show ? ) - same for kde or gnome... when the system ran out of space... what were you doing??? - compiling stuff ??? - just in screen saver mode ?? get into a habit of running top and/or ps regularly to see what should be running... - maybe a hacker is running a chat session ??? - or sending out gazillion emails... have fun alvin On Wed, 18 Apr 2001, Karsten M. Self wrote: > on Wed, Apr 18, 2001 at 05:13:07PM -0700, Jeff Davis ([EMAIL PROTECTED]) > wrote: > > I am running unstable (also kernel 2.4.3). I was exporting a > > display and runnning a second instance of kde on a remote machine > > (seperate user). When I came back, my computer was very slow (almost > > all my 256MB RAM used, way more than normal). > > Out-of-memory conditions can lead to a sluggish, and sometimes > terminally swapped, system. Best thing to do is find and isolate the > memory-hogging application and shut it down. > > > I closed everything and tried to get out of kde/X (at this time the > > remote computer had already logged off, etc). > > Suggestions: > > - Switch to a virtual console window () rather than > killing X. You're going to need a console anyway, and you can kill > X from it. You might want to run 'screen' and get both a 'top' > session and a shell prompt going. > > - Leave the remote connection open. It uses minimal overhead and is > quite useful if you wedge the system. > > - Using top or other monitoring tools, start shutting down large > processes. > > > I eventually got to a black screen with an immobile mouse and an > > unresponsive keyboard. I had to reboot. > > Sometimes necessary, but often not. You'll also want to read up on the > "magic sysrq" key combinations. I've got these taped up in strategic > locations. > > > I am not sure that the display export had anything to do with the > > "crash". Did I do something wrong? My computer hasn't had any > > problems like this for a long time (and I have had 2.4.2/3 & debian > > unstable for at least a month). > > Check your system logs for error messages, may be something there. > Could just be userspace apps. > > You can set user limits (ulimit) to prevent runaway memory utilization. > There's also low-memory cleanup support being added to the Linux kernel > itself, though I believe this is still experimental and doesn't quite > perform as expected or desired. > > -- > Karsten M. Self http://kmself.home.netcom.com/ > What part of "Gestalt" don't you understand? There is no K5 cabal > http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org >
Re: crash?
> > I eventually got to a black screen with an immobile mouse and an > > unresponsive keyboard. I had to reboot. > > Sometimes necessary, but often not. You'll also want to read up on the > "magic sysrq" key combinations. I've got these taped up in strategic > locations. What are these "magic sysrq" key combinations and where could I read up on them? I thought I knew atleast some of them, but without knowing the kind of combinations you're talking about I can't be sure. They could help out on the few times I have issues I can't recover from and actually have to reboot. Thanks, Rob
Re: crash?
Subject: Re: crash? Date: Thu, Apr 19, 2001 at 10:21:34AM -0500 In reply to:[EMAIL PROTECTED] Quoting [EMAIL PROTECTED]([EMAIL PROTECTED]): > > What are these "magic sysrq" key combinations and where could I read > up on them? I thought I knew atleast some of them, but without > knowing the kind of combinations you're talking about I can't be sure. > They could help out on the few times I have issues I can't recover > from and actually have to reboot. > 1. grep -i magic /usr/src/linux/.config CONFIG_MAGIC_SYSRQ=y 2. less /usr/src/linux/Doc*/Configure.help 2a. search for it /CONFIG_MAGIC_SYSRQ CONFIG_MAGIC_SYSRQ If you say Y here, you will have some control over the system even if the system crashes for example during kernel debugging (e.g., you will be able to flush the buffer cache to disk, reboot the system immediately or dump some status information). This is accomplished by pressing various keys while holding SysRq (Alt+PrintScreen). It also works on a serial console (on PC hardware at least), if you send a BREAK and then within 5 seconds a command keypress. The keys are documented in Documentation/sysrq.txt. Don't say Y unless you really know what this hack does. 3. read about it less /usr/src/linux/Documentation/sysrq.txt Rather then RTFM, I thought a fishing lesson might be more productive today. -- Real programmers disdain structured programming. Structured programming is for compulsive neurotics who were prematurely toilet-trained. They wear neckties and carefully line up pencils on otherwise clear desks. ___
linux crash
i've got a problem at boot. my debian system crashes. it's using kernel 2.0.36. the error follows the check of the hardware. and the error is: unable to open initial console any help would be great. i've never had to deal with this so all information regarding booting from disk and any boot options would be appreciated. thanks, brad reid [EMAIL PROTECTED] http://home.cc.umanitoba.ca/~umreidbj
crash recovery
Hi, I just experienced a complete freeze of my laptop - amarok was stuck looping through the same second of music from an online stream, and the keyboard and mouse stopped responding completely. The screen appeared fixed, viewing an xpdf window. I couldn't even switch to a terminal to poke around there, as C-A-F1 etc. didn't respond. I'm running Lenny with fluxbox, and had just done an aptitude update. I don't recall anything heavy, about 40 packages including iceweasel. I had also just plugged in to the wall socket after running on battery power for several hours. I have checked /var/log/Xorg0.log.old, and the only EE messages are: (EE) Error compiling keymap (server-0) (EE) XKB: Couldn't compile keymap These show up periodically in this file, but not in /var/log/Xorg0.log, which I take it is the log for my current session. I use a USB keyboard and USB mouse sometimes, so maybe the error is when the keyboard is first plugged in or removed? I don't know where to begin trouble shooting - what's the first step? Is there something I can do to make it easier to find the problem if it happens again? I had similar problems in the past that I think were associated with doing some image manipulation in Inkscape or Gimp that were taking all of my RAM and CPU, but I wasn't doing anything like that today. Thanks, Tyler -- I never loan my books, for people never return them. The only books remaining in my library are those I’ve borrowed from others. --unknown -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
machine crash
Hey there, Today morning my machine locked up after 8 days of flawless run, before that it went down twice always between 6 and 6:30 am, before that it ran for over 80 days since the last power outage, i can't for the life of me figure out what is going on, the message on console display said something about 'unable to handle kernels null pointer at 0x0004'. the kernel version is 2.2.18pre21, it was installed off of official debian cd's [2000-12-07] this is what was in messages log [i stripped rest of the dates]: Jun 8 06:25:14 warlord kernel: Oops: 0002 CPU:0 EIP:0010:[fat_clear_inode+26/36] EFLAGS: 00010282 eax: ebx: c1336000 ecx: c1336000 edx: esi: 1e79 edi: c082feac ebp: c0001400 esp: c082fe70 ds: 0018 es: 0018 ss: 0018 Process find (pid: 2969, process nr: 86, stackpage=c082f000) Stack: c1336000 c10908e4 c013426d c1336000 c082feac 00022684 ebdb c01344da c082feac c02b67d8 00022684 c030314c c0001400 c314e08e c0145fb8 c3177e68 c1dfa290 c0134528 0c03 c02b67d8 00022684 c030314c c0001400 c53dae80 Call Trace: [dispose_list+29/80] [try_to_free_inodes+214/252] [ext2_find_entry+416/684] [grow_inodes+32/408] [get_new_inode+185/292] [iget4+113/124] [iget+17/24] [ext2_lookup+90/140] [real_lookup+77/160] [lookup_dentry+268/428] [__namei+38/88] [sys_newlstat+13/96] [system_call+52/56] Code: 89 50 04 89 02 5b c3 8d 76 00 53 8b 5c 24 08 8b 83 90 00 00 I'm at loss here, the log from messages file looks like it had something to do with the drives and the one that was on console looked like it was null pointer, beside that i have no idea how to find out which process it was or anything, any help would be appreciated. Dingo. ).|.( '.'___'.' ' '(>~<)' ' -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-ooO-=(_)=-Ooo-=-=-=-=-=-=-=-=-=-=-=-=-=- Petr [Dingo] Dvorak [EMAIL PROTECTED] Coder - Purple Dragon MUD pdragon.org port -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-[ 369D93 ]=-=- Debian version 2.2.18pre21, up 9 min, 4 users, load average: 0.43 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Re: Crash.
On Sat, 23 Jun 2001, Alexey wrote: > I have installed Potato. > > Sometimes my computer hangs up. There appears: > Unable to handle kernel NULL pointer dereference at virtual address... > and so on. > When I reboot, e2fsck starts checking something, but fails. > I tried to run fsck manually. Sometimes it works, but not always. > After all, if I try to boot from Debian GNU/Linux Potato CD, I get > the same message: Unable to handle..., registers, stack and so on. > Looks to me like a hardware problem then. Plug out all unneceary cards. Then, if you can, try to change memory modules, pocessor (you did not overclock it, did you?), vga card, motherboard. Perhaps a piece of hardware retired. Greetz, Sebastiaan
Re: Crash.
On Sat, Jun 23, 2001 at 12:13:07PM +0400, Alexey wrote: > I have installed Potato. Upgrade the kernel-image that come with it. It is old and if there are any bugs in it, there is a good chance that these are fixed in newer, already available kernels. > Sometimes my computer hangs up. There appears: > Unable to handle kernel NULL pointer dereference at virtual address... > and so on. Clear sign of kernel trouble. Can be kernel bug or hardware brokenness that is beyond coping for the poor kernel, which gets confused. > After all, if I try to boot from Debian GNU/Linux Potato CD, I get > the same message: Unable to handle..., registers, stack and so on. Sounds like definately hardware. Make a memtest86 bootfloppy and leave it running on your computer for a few nights and days. If nothing comes up, enable "ultra performance" options in the bios to set the chips to their performance edge and try again. Maybe overclock a few system busses a little (1 to 5 %) to actively trigger boundary conditions in the hardware. If nothing comes out of that still, try latest kernel (2.2.20-pre3, resp. 2.4.6-pre3 or 2.4.5-ac20 IIRC) and report any problems to [EMAIL PROTECTED] But not after reading the BugSubmitting.txt in the documentation directory of the linux kernel source, of course. Cheers, Joost
crash analysis?
Hi Folks, My system is doing something funny, where it seems to be crashing once a day, and there's not enough in my logs to figure out what's going on when it crashes. It looks like most of what I find about crash logging tools (by googling) is about 5 years old, so. can anybody offer more recent suggestions as to logging settings to change, tools to install, and so forth for capturing and analyzing crash events under Debian (running Lenny). Thanks much, Miles Fidelman -- In theory, there is no difference between theory and practice. In practice, there is. Yogi Berra -- 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/4c10cc07.6010...@meetinghouse.net
Firefox Crash
Hi, since a few weeks I see frequent firefox crashes. Even with a fresh configuration directory, I get rd@blackbox:~$ mv .mozilla/ .mozilla.bak rd@blackbox:~$ firefox Vector smash protection is enabled. ATTENTION: default value of option force_s3tc_enable overridden by environment. intel_do_flush_locked failed: Input/output error [NPAPI 29302] ###!!! ABORT: Aborting on channel error.: file /tmp/buildd/firefox-48.0/ipc/glue/MessageChannel.cpp, line 2046 [NPAPI 29302] ###!!! ABORT: Aborting on channel error.: file /tmp/buildd/firefox-48.0/ipc/glue/MessageChannel.cpp, line 2046 rd@blackbox:~$ Even rd@blackbox:~$ firefox -save-mode ATTENTION: default value of option force_s3tc_enable overridden by environment. intel_do_flush_locked failed: Input/output error rd@blackbox:~$ crashes. I run a jessie-backport from mozilla.debian.net rd@blackbox:~$ apt-cache policy firefox firefox: Installed: 48.0-1~bpo80+1 Candidate: 48.0-1~bpo80+1 Version table: 49.0~b1-1 0 250 http://ftp-stud.fht-esslingen.de/debian/ experimental/main i386 Packages 48.0-2 0 300 http://ftp-stud.fht-esslingen.de/debian/ sid/main i386 Packages *** 48.0-1~bpo80+1 0 500 http://mozilla.debian.net/ jessie-backports/firefox-release i386 Packages 100 /var/lib/dpkg/status rd@blackbox:~$ Any hint what could go wrong would be welcome. Many thanks Rainer -- Rainer Dorsch http://bokomoko.de/
system crash
Hello while using my system with the KDE desktop manager, my system became unresponsive for about 30 seconds, after I was able to only move the mouse around but nothing else was accessible. I could still see all the windows, then both my monitor went black. I had to do a cold boot to get everything working. How can I enter this bug using reportbug? I don't know what actually caused the entire system to lock up.
X-crash
Hy, I've got BIG problemm: I've got Debian some time and it was well, but I've just bought new mainboard (fic 502)and my X window started to crash ... "undefinied references in libX11.so.6, fatal error in freeing of nonexisting swap page, ... " But I've got RedHat 4.2 too, and it is unaffected by the change of board and work still well. I'm very thankful for any help. Martin Saturka PS I'm sorry, I'm not suscribed in list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Printing crash
I'm running 2.0.34, and trying to print to a HP Laserjet 4L. I had the printing system up and working perfectly, until I installed the lyx_0_12_0_final-0_1.deb package. Now, any program trying to access LPD outputs the following to stderr: : lp: getconnection: bad port number for LPD connection! :check 'lpd-port' in configuration file, or the :/etc/services file for a missing 'printer 515/tcp' entry - No such file or :directory :Host 'localhost' - cannot open connection to [EMAIL PROTECTED]' - No such file or :directory I'm not on a network, so there is no /etc/services file, and 'lpd port' in lpd.conf doesn't work when set to 'printer', 'lp', or 'dj'. Any help would really be appreciated. ...Mike Milligan _ You don't need to buy Internet access to use free Internet e-mail. Get completely free e-mail from Juno at http://www.juno.com Or call Juno at (800) 654-JUNO [654-5866]
Printing crash
I'm running 2.0.34, and trying to print to a HP Laserjet 4L. I had the printing system up and working perfectly, until I installed the lyx_0_12_0_final-0_1.deb package. Now, any program trying to access LPD outputs the following to stderr: : lp: getconnection: bad port number for LPD connection! :check 'lpd-port' in configuration file, or the :/etc/services file for a missing 'printer 515/tcp' entry - No such file or :directory :Host 'localhost' - cannot open connection to [EMAIL PROTECTED]' - No such file or :directory I'm not on a network, so there is no /etc/services file, and 'lpd port' in lpd.conf doesn't work when set to 'printer', 'lp', or 'dj'. Any help would really be appreciated. ...Mike Milligan _ You don't need to buy Internet access to use free Internet e-mail. Get completely free e-mail from Juno at http://www.juno.com Or call Juno at (800) 654-JUNO [654-5866]
Crash! (help)
What is device 03:01 ( see the syslog below. I assume its the swap partition) I did: swapoff /dev/hda2 mkswap -c /dev/hda2 swapon -a That should have reset a corrupt swap partition correct? here is the messages from the syslog: Nov 25 00:50:00 bitgate /USR/SBIN/CRON[24770]: (root) CMD (/root/ppp/bin/ppp_watch.sh > /dev/null 2>&1) Nov 25 00:50:10 bitgate kernel: Internal error: bad swap-device Nov 25 00:50:10 bitgate kernel: Trying to free nonexistent swap-page Nov 25 00:50:10 bitgate kernel: Internal error: bad swap-device Nov 25 00:50:10 bitgate kernel: Trying to free nonexistent swap-page Nov 25 00:50:10 bitgate last message repeated 3 times Nov 25 00:52:40 bitgate kernel: ll_rw_block: device 03:01: only 1024-char blocks implemented (1028) Nov 25 00:52:46 bitgate kernel: VFS: Wrong blocksize on device 03:01 Nov 25 01:56:35 bitgate syslogd 1.3-3#17.1: restart (remote reception). Nov 25 01:56:35 bitgate kernel: klogd 1.3-3, log source = /proc/kmsg started. Nov 25 01:56:35 bitgate kernel: Loaded 3542 symbols from /System.map. Nov 25 01:56:35 bitgate kernel: Symbols match kernel version 2.0.32. Thanks! -Eric Yocom -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
RE: Crash
Whenever I shutdown my home machine it says. System has halted and if I reboot it says system is rebooting. Crash doesn't sound to good to me either Rod Person "Humanity is the biggest cancer ever to be seen!" -Alx Hellid Contempt > -- > From: Andreas Kahari[SMTP:[EMAIL PROTECTED] > Sent: Monday, October 26, 1998 9:37 AM > To: debian-user@lists.debian.org > Subject: Crash > > Hi all! > > At work, if I reboot my Solaris workstation, the "last" command > reports > something like > > rebootsystem boot Fri Oct 23 09:54 > > or > > andreas console :0 Thu Aug 6 11:24 - down > (06:19) > > but at home, with Debian 2.0, it simply states that my system has > "crashed" at a specific time. > > Should I worry? > > I usually run "halt" as root to bring my system down, the same thing > happens if I run "reboot" as root. > > Everything works well, it's just that "crash" feels a little bit > worrying, it ought to say "down" or "reboot"... > > /A > > -- > Andreas K., Department of Scientific Computing, Uppsala Univ., Sweden > - - - - - - - - - - - - - - - - - - - - - - - - > Feet smell? Nose runs? You're built upside down! > -- >
Re: Crash
On Mon, 26 Oct 1998, Andreas Kahari wrote: > At work, if I reboot my Solaris workstation, the "last" command reports > something like > rebootsystem boot Fri Oct 23 09:54 > ... > but at home, with Debian 2.0, it simply states that my system has > "crashed" at a specific time. the 'halt' and 'reboot' commands are probably the hardcore method to bring the system down. On some distributions (maybe debian too, don't want to try out at the moment) 'sbin/shutdown -h now' goes into runlevel 0, goes trough /etc/init.d/* stop, halts then kills the remaining processes. this is the safe way, and would not 'crash'. I saw once that at the end of the shutdown, a 'halt' or 'reboot' is executed at the very end, so on these systems, typing 'halt' is like just pressing the power button. try if your problem goes away by using 'shutdown -r now'. -- Lukas Eppler (godot)
Re: Crash
I just looked at "last" on my system and noticed the same thing. Some reboots and shutdowns appear as crash. Yet I know everything was umounted correctly. WHY? John John Maheuphone (403) 492-2049 University of Alberta email [EMAIL PROTECTED] Dept. of Economics Edmonton, Alberta Canada, T6G 2H4 On Tue, 27 Oct 1998, Andreas Kahari wrote: > The 'halt' command in Debian behaves as if I typed 'shutdown -h now', > i.e. it sends TERM and KILL to all processes and stops all daemons, and > finally prints "System halted" (if I press the big red button, which I > won't do, this naturally won't happen). I still get "crash"... > > Here's some output from the 'last' command on my system: > andreas tty1 Mon Oct 26 18:53 still logged in > reboot system boot Mon Oct 26 18:53 > root tty1 Sun Oct 25 14:20 - 14:21 (00:00) > reboot system boot Sun Oct 25 14:20 > root tty1 Sun Oct 25 14:14 - crash (00:03) > reboot system boot Sun Oct 25 14:14 > andreas tty2 Sun Oct 25 13:59 - crash (00:12) > andreas tty1 Sun Oct 25 14:53 - crash (00:-41) > reboot system boot Sun Oct 25 14:53 > andreas tty1 Fri Oct 23 20:54 - crash (01:08) > > I notice now that 'reboot' won't cause a "crash", but 'halt' *and* > 'shutdown -h now' will. > > Also, CTRL-ALT-DEL (in inittab: "ca:12345:ctrlaltdel:/sbin/shutdown -t1 > -h now") will cause "crash" (I changed this entry in inittab from "-r" > to "-h", which is what I want CTRL-ALT-DEL to do). > > But, as I said, nothing appears to be wrong. Everything works fine, > except for the word "crash"... > > /A > > -- > Andreas K., Department of Scientific Computing, Uppsala Univ., Sweden > - - - - - - - - - - - - - - - - - - - - - - - - > Contentsofsignaturemaysettleduringshipping. > -- > > > On Tue, 27 Oct 1998, Lukas Eppler wrote: > > On Mon, 26 Oct 1998, Andreas Kahari wrote: > > > > > At work, if I reboot my Solaris workstation, the "last" command reports > > > something like > > > rebootsystem boot Fri Oct 23 09:54 > > > ... > > > but at home, with Debian 2.0, it simply states that my system has > > > "crashed" at a specific time. > > > > the 'halt' and 'reboot' commands are probably the hardcore method to bring > > the system down. On some distributions (maybe debian too, don't want to > > try out at the moment) 'sbin/shutdown -h now' goes into runlevel 0, goes > > trough /etc/init.d/* stop, halts then kills the remaining processes. this > > is the safe way, and would not 'crash'. I saw once that at the end of the > > shutdown, a 'halt' or 'reboot' is executed at the very end, so on these > > systems, typing 'halt' is like just pressing the power button. > > > > try if your problem goes away by using 'shutdown -r now'. > > > > -- > > Lukas Eppler (godot) > > > > > > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > >
Debian Crash
My Debian system just crashed. This has never happened before, which is one of the things I like about Linux. I've got a pretty standard Hamm system, and I was running X with emacs (20), xmix, and netscape, with a navigator and mail window open. I went on a webpage I've visited many times before (www.tomshardware.com), and everything seized up: the mouse wouldn't move, I couldn't move between virtual desktops and I couldn't move between virtual teminals. I waited a couple of minutes, then tried , then , neither of which had any effect whatsoever, so I pressed the big red button, and restarted that way. The only non-Debian software I have installed is xaudio, an X window mpeg layer 3 audio player, which is off /root/mpeg (I was just trying it out). My hardware is an old(ish) Cyrix 6x86 (M1) P200+ on a SuperMicro P5xtra motherboard, 32mb DRAM (2simms), Matrox millenium 4mb, WD harddrive, mitsumi Cd rom, soundblaster awe64 pnp, microsoft serial mouse. Up 'till now, everything seems to have been working fine (I've had random crashes under win95, but I think that's a feature of the OS). My questions: Is there a problem with my hardware (it's quite old)? Was there a problem with Linux? If not, is there now? If so, how do I fix it? What should I do to test the components in my system individually? I put it together myself (about 2 years ago), so I don't mind poking around inside.
Ack crash!
-BEGIN PGP SIGNED MESSAGE- Got this error yesterday, It filled the console and the machine was frozen: Oct 3 16:00:04 bitgate kernel: Problem: block on freelist at 00497210 isn't free. I booted to a resq partition and e2fsck the disk (a few errors 1 major one) and remade the swap partition. any clues what did it? The machine was up for 12 day uptime at that point. Thanks! - -Eric "Give me ambiguity or give me something else." -BEGIN PGP SIGNATURE- Version: 2.6.3a Charset: noconv iQCVAwUBNDZvJqDN4t3E2gMVAQGYEgQAmwDRGa0g78LzM2cvvN1C8XrrQ+VDZkms MrSliGCTCVbj0fubgl8PnuF5FOduPcFQiBAuSererIv4e55VVRjAodkW5I9wT62d CqRZ65Gynur7uwkQXXyVFNj4L9qklMAsKmVbzReeHWW5cqfCdKJ7hOdmn5FrXz+F G4w9JWF+VhI= =Z5Hz -END PGP SIGNATURE- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
APM - Crash ?
Hi, I have just installed Debian R3.0 onto a newish laptop (Packard Bell iGo 6000, which is a rebranded NEC Versa M300). If I enable APM, and cat /proc/apm I get a complete melt down - the screen fills with what appears to be registers, and it just loops and loops and loops ... I get the same problem if I boot with Knoppix and APM enabled , so it would appear to be an APM issue ? I have used apt-get to upgrade to testing / unstable, and upgraded the kernel to 2.4.22-1-686. Anyone have any ideas on how to get apm to work, as it would be nice to able to watch the battery level ... Andy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
APM - Crash ?
( Re-submitted - last copy did not appear - sent 18th at 2:20PM) > Hi, > > I have just installed Debian R3.0 onto a newish laptop (Packard Bell iGo > 6000, which is a rebranded NEC Versa M300). > > If I enable APM, and cat /proc/apm I get a complete melt down - the screen > fills with what appears to be registers, and it just loops and loops and > loops ... > > I get the same problem if I boot with Knoppix and APM enabled , so it would > appear to be an APM issue ? > > I have used apt-get to upgrade to testing / unstable, and upgraded the > kernel to 2.4.22-1-686. > > Anyone have any ideas on how to get apm to work, as it would be nice to able > to watch the battery level ... > > Andy > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
System crash
Hi, I have a problem with Sid. When system boots up, the disk starts reading and/or writing after a few minutes. This happens during a quite long time (the led of the disk is on all this time). After this time, no system device responds. I can only push reset button and restart the system (after that, the problem does not happen any more, it appears only when I boot Sid the first time). Can anyone help me? Sorry for my English and thanks in advance. Regards Rafael Arco Arredondo -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.2.3 (GNU/Linux) mQGiBD+gHS4RBACEjc26tE0P3lHb1kAi1+NSEoMpNSNdLL2C+a8KH3KemDQ9mber YUuqU6XYYMFVe1/WBL+N3SeB7EeprDUkDVdXvoR814f74VvHguJktAVJAInCQhKD sbGA9O9g6xiwIYJ0wYnFZaqAn7yiXqLiBtYlbqfgLb4kSLpYZWZxYfAWmwCg7pyE kwSdiXpkMD5TM8Y+oVaTY1MD/21elptacIozJ2daxJgVAmR7wBaA472z0KRz/2T4 lYu8V3znMsyjoo36bzPE/E/KyOin/Ld/zTpbNhw/Nbg8HayWI77DfLUY9VXtvJju eyGKBQwopKv8XSbz2oFMUfY9Qat+jPoi4Zh07A9a/zfYzTpaB72nLP9nsNZdYh5b bqn9A/439482wzDKXFurEBp9Ze9eB/zhs29yk+wCFHqIgbzYH6Cx2dKXBSCGiG8Y ilfNSE4OvSMFL+YPQ8g1X9ZED0aQnE1kXZ0uIY0w0Y10Sn2tQ5foLwfo8z9prFoy pNMw8pV7os2JRg2i5eO47zR44DRe5E+WU+euNR/KTrFONQB1qLRmUmFmYWVsIEFy Y28gQXJyZWRvbmRvIChFVFMgSW5nZW5pZXLDrWEgSW5mb3Jtw6F0aWNhIC0gVW5p dmVyc2lkYWQgZGUgR3JhbmFkYSkgPHJhZmFyY29AdGVsZWZvbmljYS5uZXQ+iF4E ExECAB4FAj+gHS4CGwMGCwkIBwMCAxUCAwMWAgECHgECF4AACgkQBFhDi4GiLIPI wACg5t7DKKi+q/0oWKf39FJMCVcoi8QAoNjkT8FqtvSkrypyZKlwjVHXGm4ctD5S YWZhZWwgQXJjbyBBcnJlZG9uZG8gKEhpc3BhTGlOVVgpIDxyYWZhZWwuYXJjb0Bo aXNwYWxpbnV4LmVzPoheBBMRAgAeBQI/oRWLAhsDBgsJCAcDAgMVAgMDFgIBAh4B AheAAAoJEARYQ4uBoiyDyvoAoIZ1+hq/0dJjTapTQEzJRSIlzD2BAKCx0PWm3bFZ 2BNiLmLTstEuR41rlrRiUmFmYWVsIEFyY28gQXJyZWRvbmRvIChFVFMgSW5nZW5p ZXLDrWEgSW5mb3Jtw6F0aWNhIC0gVW5pdmVyc2lkYWQgZGUgR3JhbmFkYSkgPHJh cmNvQGZlZHJvLnVnci5lcz6IXgQTEQIAHgUCP6EVtwIbAwYLCQgHAwIDFQIDAxYC AQIeAQIXgAAKCRAEWEOLgaIsg0O0AKCkq/5GWokxcOWlNcdVT606T+rnUQCfRHg9 azpkbEYWgboV0lQgED9CznW5AQ0EP6AdMhAEAJtYp8UD/MJOZSDBkBTSTqEIATXo 5XSMas7pJvaz6JozU+qh608Mb4oeuQAGyLsAQFf/9p7Y5hUg6tRxcW8AF3c7CHjM 8oQG6rIUv8RGrIepVTTDpeBDcPqXWqPwkIl+4XPZf6bNHG0KnGOuj59WPy5E9I0H 4CLYXOY7MzQtPMrDAAMFA/0aV8qUZ2GoGOQRRV1BvL+I0LRBOOwsKKfa972/ZA1u tP1dLUVKl5iJCcJIZEdjcGHe/nGwUMhZGgeOzf5VBzv+EJMfARPrqfknLK7LddQq 3CCYLEBWRwmgU0wCHRHA9YCIDCVDzfORvnliAzygmPqguLsxJv9MNexQomPyal3u VIhJBBgRAgAJBQI/oB0yAhsMAAoJEARYQ4uBoiyDRpIAn1rVcBTr35M8A2RSvt53 uEUxvZGdAKDXAzsz++WFO8xF0PTcKijKQkql3Q== =EWCw -END PGP PUBLIC KEY BLOCK- signature.asc Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada digitalmente
woody - crash.
squirelmail, proftpd + mysql lstat , ipfm , squid , dhcp , apache , apache-ssl , sshd , portsentry , named , courier + sql. What does the quite big number od '@' ? Successful try of string oveflow or buffer overflow that resulted in crash ? The problem is that i dont know what actually Oopsed. There is nothing about it in logs. Thank You for all sugestions and help. Best Regards. -- [ Pozdrawiam ] [ Dawid Chrzan ] [ http://f-net.pl ] [ RLU#212729 ] [ net/sys administrator ] [[EMAIL PROTECTED]] [ Adminie!!! Nie piłeś dzisiaj kawy? Wypij! - Piłeś? Wypij drugą... ] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
crash messages
hi everyone, failed to attach this part of my /var/log/messages, as promised. So I'll just insert it in this message. I assume the eth-00 messages are harmless? In which case all I can see are messages of this kind: Jan 6 17:12:34 pc09 kernel: keyboard.c: can't emulate rawmode for keycode 272 any hintas? PRE-CRASH MESSAGES: - Jan 6 17:00:03 pc09 kernel: IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:50:99:bf:df:18:08:00 SRC=128.100.34.3 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=43835 PROTO=2 Jan 6 17:02:08 pc09 kernel: IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:50:99:bf:df:18:08:00 SRC=128.100.34.3 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=43844 PROTO=2 Jan 6 17:02:42 pc09 kernel: keyboard.c: can't emulate rawmode for keycode 272 Jan 6 17:03:23 pc09 last message repeated 2 times Jan 6 17:04:00 pc09 last message repeated 13 times Jan 6 17:04:13 pc09 kernel: IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:50:99:bf:df:18:08:00 SRC=128.100.34.3 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=43853 PROTO=2 Jan 6 17:06:18 pc09 kernel: IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:50:99:bf:df:18:08:00 SRC=128.100.34.3 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=43872 PROTO=2 Jan 6 17:08:23 pc09 kernel: IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:50:99:bf:df:18:08:00 SRC=128.100.34.3 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=43885 PROTO=2 Jan 6 17:08:32 pc09 kernel: keyboard.c: can't emulate rawmode for keycode 272 Jan 6 17:08:35 pc09 last message repeated 5 times Jan 6 17:10:28 pc09 kernel: IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:50:99:bf:df:18:08:00 SRC=128.100.34.3 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=43894 PROTO=2 Jan 6 17:10:50 pc09 kernel: keyboard.c: can't emulate rawmode for keycode 272 Jan 6 17:10:50 pc09 kernel: keyboard.c: can't emulate rawmode for keycode 272 Jan 6 17:12:31 pc09 last message repeated 25 times Jan 6 17:12:33 pc09 kernel: IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:50:99:bf:df:18:08:00 SRC=128.100.34.3 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=43903 PROTO=2 Jan 6 17:12:34 pc09 kernel: keyboard.c: can't emulate rawmode for keycode 272 Jan 6 17:12:35 pc09 last message repeated 2 times Jan 6 17:12:57 pc09 kernel: keyboard.c: can't emulate rawmode for keycode 273 Jan 6 17:12:57 pc09 kernel: keyboard.c: can't emulate rawmode for keycode 273 Jan 6 17:12:58 pc09 kernel: keyboard.c: can't emulate rawmode for keycode 272 Jan 6 17:13:31 pc09 last message repeated 9 times Jan 6 17:14:29 pc09 last message repeated 16 times Jan 6 17:14:38 pc09 kernel: IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:50:99:bf:df:18:08:00 SRC=128.100.34.3 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=43919 PROTO=2 Jan 6 17:14:39 pc09 kernel: keyboard.c: can't emulate rawmode for keycode 272 Jan 6 17:15:26 pc09 last message repeated 8 times Jan 6 17:16:32 pc09 last message repeated 4 times Jan 6 17:16:32 pc09 last message repeated 3 times Jan 6 17:16:43 pc09 kernel: IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:50:99:bf:df:18:08:00 SRC=128.100.34.3 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=43936 PROTO=2 Jan 6 17:17:04 pc09 kernel: keyboard.c: can't emulate rawmode for keycode 272 Jan 6 17:17:29 pc09 last message repeated 11 times Jan 6 17:18:47 pc09 kernel: IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:50:99:bf:df:18:08:00 SRC=128.100.34.3 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=43948 PROTO=2 Jan 6 17:20:52 pc09 kernel: IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:50:99:bf:df:18:08:00 SRC=128.100.34.3 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=43958 PROTO=2 Jan 6 17:21:21 pc09 kernel: keyboard.c: can't emulate rawmode for keycode 272 Jan 6 17:21:22 pc09 kernel: keyboard.c: can't emulate rawmode for keycode 272 Jan 6 17:22:57 pc09 kernel: IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:50:99:bf:df:18:08:00 SRC=128.100.34.3 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=43968 PROTO=2 Jan 6 17:25:02 pc09 kernel: IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:50:99:bf:df:18:08:00 SRC=128.100.34.3 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=43981 PROTO=2 Jan 6 17:27:07 pc09 kernel: IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:50:99:bf:df:18:08:00 SRC=128.100.34.3 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=44001 PROTO=2 Jan 6 17:29:12 pc09 kernel: IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:50:99:bf:df:18:08:00 SRC=128.100.34.3 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=44011 PROTO=2 Jan 6 17:31:17 pc09 kernel: IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:50:99:bf:df:18:08:00 SRC=128.100.34.3 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=44019 PROTO=2 Jan 6 17:33:22 pc09 kernel: IN=eth0 OUT= MAC=01:00:5e:00:00:01:00:50:99:bf:df:18:08:00 SRC=128.100.34.3 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=44028 PROTO=2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Gnome Crash
It seems that I have caused Gnome to crash permanently. I had inadvertently dragged a copy of an item from the menu, and put it into the TRASH and then emptied it. At that point Gnome crashed. Any reattepts to login to a Gnome (2.4) setup bringing up a Gnome-panel crash. I've had to resort to KDE. I've tried blowing away all that I think is Gnome related (including stuff from /tmp as well!), and then reinstalling clean files from what /etc/skel would install for a new user. To no avail! Same crash situation. And any other users I've got (and new users) do now have such a problem. Any help would be appreciated...especically in tracking down where the key items for gnome-panel are in a typical user's directory. Thanks, Arlen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Galeon crash
Hi, I am trying to run galeon and after several error messages like the one below... ** CRITICAL **: file /home/erich/debian/galeon/galeon-1.2.6/src/mozilla/mozilla.cpp: line 134 (gboolean mozilla_preference_set(const char *, const char *)): assertion `new_value != NULL' failed. ... it starts opening the window and aborts with the following message: ** ERROR **: file /home/erich/debian/galeon/galeon-1.2.6/src/main.c: line 789 (galeon_exit): assertion failed: (g_list_length (all_embeds) == 0) aborting... Aborted What is the problem? Specs: Debian unstable, Galeon 1.2.6-2. Any idea of the reason for that? Thanks, Bruno. -- Bruno Diniz de Paula <[EMAIL PROTECTED]> Rutgers University signature.asc Description: This is a digitally signed message part
Re: unexplained crash
On Fri, Nov 17, 2023 at 07:17:08PM +, Adam Weremczuk wrote:
> Hello,
>
> Yesterday SSH on my desktop PC running Ubuntu 20.04 became unresponsive.
>
> The machine was responding to ping and "telnet 22" was briefly connecting
> before connection closed.
Guessing from the context, you tried to ssh into your desktop and
something went wrong ("became unresponsive"). What /exactly/ did
your ssh client say?
I'd guess along the lines of "connection closed by foreign host",
which would mean the ssh daemon is listening on the other side
but closes the connection shortly after establishing it.
You can gather a bit more of info by adding one (or more) -v options
to your ssh client invocation.
> The graphical login prompt was visible, but when I tried to log in, it threw
> me to the text console. No login prompt on any virtual consoles and
> Ctrl-Alt-Del did nothing.
>
> There is no information logged in wtmp, kern.log and dmesg. Nothing
> interesting in auth.log
>
> The last 40 lines from syslog look as below:
[...]
I'm not a systemd expert by a long shot, so I'll have to leave
this to others, but my first impression of the log is that of
a system shutting down (which is kind of strange).
Perhaps you've had a file system (or underlying drive media)
error and your root FS is mounted read only?
I understand that you managed to log into a console: what does
"mount" say?
Cheers
--
t
signature.asc
Description: PGP signature
Re: unexplained crash
On Sat 18 Nov 2023 at 07:06:49 (+0100), to...@tuxteam.de wrote:
> On Fri, Nov 17, 2023 at 07:17:08PM +, Adam Weremczuk wrote:
> > Yesterday SSH on my desktop PC running Ubuntu 20.04 became unresponsive.
> >
> > The machine was responding to ping and "telnet 22" was briefly connecting
> > before connection closed.
>
> Guessing from the context, you tried to ssh into your desktop and
> something went wrong ("became unresponsive"). What /exactly/ did
> your ssh client say?
>
> I'd guess along the lines of "connection closed by foreign host",
> which would mean the ssh daemon is listening on the other side
> but closes the connection shortly after establishing it.
>
> You can gather a bit more of info by adding one (or more) -v options
> to your ssh client invocation.
>
> > The graphical login prompt was visible, but when I tried to log in, it threw
> > me to the text console. No login prompt on any virtual consoles and
> > Ctrl-Alt-Del did nothing.
> >
> > There is no information logged in wtmp, kern.log and dmesg. Nothing
> > interesting in auth.log
> >
> > The last 40 lines from syslog look as below:
>
> [...]
>
> I'm not a systemd expert by a long shot, so I'll have to leave
> this to others, but my first impression of the log is that of
> a system shutting down (which is kind of strange).
They did say they tried Ctrl-Alt-Del. That shuts down (and reboots)
on my systems.
Cheers,
David.
Re: unexplained crash
On Fri, Nov 17, 2023 at 7:11 PM Adam Weremczuk wrote: > > Yesterday SSH on my desktop PC running Ubuntu 20.04 became unresponsive. > > The machine was responding to ping and "telnet 22" was briefly > connecting before connection closed. > > The graphical login prompt was visible, but when I tried to log in, it > threw me to the text console. No login prompt on any virtual consoles > and Ctrl-Alt-Del did nothing. > > There is no information logged in wtmp, kern.log and dmesg. Nothing > interesting in auth.log > > The last 40 lines from syslog look as below: > > Nov 16 17:04:23 ubu20 systemd[1]: session-5089.scope: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1]: Stopping User Manager for UID 0... > Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Main User Target. > Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Basic System. > Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Paths. > Nov 16 17:04:33 ubu20 systemd[1259208]: ubuntu-report.path: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped Pending report trigger > for Ubuntu Report. > Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Sockets. > Nov 16 17:04:33 ubu20 systemd[1259208]: Stopped target Timers. > Nov 16 17:04:33 ubu20 systemd[1259208]: dbus.socket: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1259208]: Closed D-Bus User Message Bus > Socket. > Nov 16 17:04:33 ubu20 systemd[1259208]: dirmngr.socket: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG network certificate > management daemon. > Nov 16 17:04:33 ubu20 systemd[1259208]: gpg-agent-browser.socket: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG cryptographic agent > and passphrase cache (access for web browsers). > Nov 16 17:04:33 ubu20 systemd[1259208]: gpg-agent-extra.socket: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG cryptographic agent > and passphrase cache (restricted). > Nov 16 17:04:33 ubu20 systemd[1259208]: gpg-agent-ssh.socket: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG cryptographic agent > (ssh-agent emulation). > Nov 16 17:04:33 ubu20 systemd[1259208]: gpg-agent.socket: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1259208]: Closed GnuPG cryptographic agent > and passphrase cache. > Nov 16 17:04:33 ubu20 systemd[1259208]: pk-debconf-helper.socket: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1259208]: Closed debconf communication socket. > Nov 16 17:04:33 ubu20 systemd[1259208]: snapd.session-agent.socket: > Succeeded. > Nov 16 17:04:33 ubu20 systemd[1259208]: Closed REST API socket for snapd > user session agent. > Nov 16 17:04:33 ubu20 systemd[1259208]: Reached target Shutdown. > Nov 16 17:04:33 ubu20 systemd[1259208]: systemd-exit.service: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1259208]: Finished Exit the Session. > Nov 16 17:04:33 ubu20 systemd[1259208]: Reached target Exit the Session. > Nov 16 17:04:33 ubu20 systemd[1]: user@0.service: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1]: Stopped User Manager for UID 0. > Nov 16 17:04:33 ubu20 systemd[1]: Stopping User Runtime Directory > /run/user/0... > Nov 16 17:04:33 ubu20 systemd[2567]: run-user-0.mount: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1294]: run-user-0.mount: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1]: run-user-0.mount: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1]: user-runtime-dir@0.service: Succeeded. > Nov 16 17:04:33 ubu20 systemd[1]: Stopped User Runtime Directory > /run/user/0. > Nov 16 17:04:33 ubu20 systemd[1]: Removed slice User Slice of UID 0. > > Does anybody have an idea what could have happened? Whenever I see Snap, I get suspicious. You should probably ask on the ubuntu-users list. The list has a person that answers Snap questions. . You should also show the SSH connection log for the client and server. I think that's 'ssh -vvv' for the client, and 'journalctl -u ssh' for the server. Jeff
Random X crash
I am getting seemingly random crashes of X. I have 3 monitors (2 external, 1 laptop), and occasionally they will flash black, and orientation gets reset to default. I have not been able to find any action that specifically triggers this, although when i look at dmesg, it seems to somehow be relate to my wifi. I have pasted (what I think) are the relevant bits of dmesg below, please let me know if I should provide more info. dmesg first instance: [14198.890344] bridge-wlan2: device is wireless, enabling SMAC [14198.890348] bridge-wlan2: up [14198.890353] bridge-wlan2: attached [14198.930206] wlan2: Limiting TX power to 30 (30 - 0) dBm as advertised by 80:ea:96:ee:dd:0a [14199.090477] userif-3: sent link down event. [14199.090481] userif-3: sent link up event. [16815.766004] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder A [16815.766009] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun [16815.767229] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR* uncleared fifo underrun on pipe A [16815.767234] [drm:ivb_err_int_handler] *ERROR* Pipe A FIFO underrun [17129.902962] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder A [17129.902966] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun [17129.917635] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR* uncleared fifo underrun on pipe A [17129.917639] [drm:ivb_err_int_handler] *ERROR* Pipe A FIFO underrun [17197.888252] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder A [17197.888256] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun [17197.898583] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR* uncleared fifo underrun on pipe A [17197.898588] [drm:ivb_err_int_handler] *ERROR* Pipe A FIFO underrun [17553.192289] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder A [17553.192294] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun [17553.196104] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR* uncleared fifo underrun on pipe A [17553.196108] [drm:ivb_err_int_handler] *ERROR* Pipe A FIFO underrun dmesg second instance: - [20155.260197] /dev/vmnet: port on hub 0 successfully opened [20155.260206] bridge-wlan2: device is wireless, enabling SMAC [20155.261377] bridge-wlan2: up [20155.261422] bridge-wlan2: attached [20155.341711] wlan2: Limiting TX power to 30 (30 - 0) dBm as advertised by 80:ea:96:ee:dd:0a [20155.411171] userif-3: sent link down event. [20155.412149] userif-3: sent link up event. [20416.556616] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder A [20416.556621] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun [20416.556772] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR* uncleared fifo underrun on pipe A [20416.556775] [drm:ivb_err_int_handler] *ERROR* Pipe A FIFO underrun [21122.359725] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder A [21122.359729] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun [21122.369766] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR* uncleared fifo underrun on pipe A [21122.369771] [drm:ivb_err_int_handler] *ERROR* Pipe A FIFO underrun [22666.750046] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder A [22666.750050] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun [22666.751890] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR* uncleared fifo underrun on pipe A [22666.751893] [drm:ivb_err_int_handler] *ERROR* Pipe A FIFO underrun [22988.645046] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder A [22988.645050] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun [22988.645987] [drm:ivybridge_set_fifo_underrun_reporting] *ERROR* uncleared fifo underrun on pipe A [22988.645989] [drm:ivb_err_int_handler] *ERROR* Pipe A FIFO underrun signature.asc Description: OpenPGP digital signature
Re: GIMP Crash
Ryan Young writes: > Here is the bug info > > ``` > GNU Image Manipulation Program version 2.10.8 In that case, if you are in Debian, you would be send bug report. So that the maintainer can be know what problem is. https://www.debian.org/Bugs/Reporting Actually, you must add contain keywords "Package" and "Version" ;;; Sincerely, Byung-Hee -- ^고맙습니다 _白衣從軍_ 감사합니다_^))//
Gimp 2.10.8 crash
``` GNU Image Manipulation Program version 2.10.8 git-describe: GIMP_2_10_6-294-ga967e8d2c2 C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:hsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 9.2.1-6' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-9 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 9.2.1 20190827 (Debian 9.2.1-6) using GEGL version 0.4.12 (compiled against version 0.4.14) using GLib version 2.60.6 (compiled against version 2.60.6) using GdkPixbuf version 2.38.1 (compiled against version 2.38.1) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.42.3 (compiled against version 1.42.3) using Fontconfig version 2.13.1 (compiled against version 2.13.1) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > fatal error: Errore di segmentazione Stack trace: ``` /usr/lib/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x398)[0x7f3915b9ff98] gimp-2.10(+0xd1590)[0x5645c93e3590] gimp-2.10(+0xd19b8)[0x5645c93e39b8] gimp-2.10(+0xd2029)[0x5645c93e4029] /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7f3915098730] gimp-2.10(gimp_gegl_mask_is_empty+0x91)[0x5645c97ce411] gimp-2.10(+0x3b7810)[0x5645c96c9810] gimp-2.10(+0x42ec18)[0x5645c9740c18] gimp-2.10(+0x3d5b50)[0x5645c96e7b50] gimp-2.10(+0x42f2aa)[0x5645c97412aa] gimp-2.10(gimp_drawable_set_buffer_full+0x1cb)[0x5645c96e69bb] gimp-2.10(gimp_drawable_set_buffer+0x11d)[0x5645c96e6f9d] gimp-2.10(gimp_drawable_new+0x106)[0x5645c96e7296] gimp-2.10(gimp_layer_new+0x90)[0x5645c97444d0] gimp-2.10(+0x3319cc)[0x5645c96439cc] gimp-2.10(gimp_procedure_execute+0x237)[0x5645c967c577] gimp-2.10(gimp_pdb_execute_procedure_by_name_args+0x1e9)[0x5645c9675a39] gimp-2.10(gimp_plug_in_handle_message+0x216)[0x5645c9680626] gimp-2.10(+0x36cf91)[0x5645c967ef91] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x158)[0x7f391527d898] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4ec88)[0x7f391527dc88] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0xb2)[0x7f391527df82] gimp-2.10(gimp_plug_in_manager_call_run+0x5fc)[0x5645c969035c] gimp-2.10(+0x376dbe)[0x5645c9688dbe] gimp-2.10(gimp_procedure_execute+0x237)[0x5645c967c577] gimp-2.10(gimp_pdb_execute_procedure_by_name_args+0x1e9)[0x5645c9675a39] gimp-2.10(gimp_pdb_execute_procedure_by_name+0x3cd)[0x5645c9675efd] gimp-2.10(file_open_image+0x33d)[0x5645c97766fd] gimp-2.10(file_open_with_proc_and_display+0x29d)[0x5645c977764d] gimp-2.10(+0x113573)[0x5645c9425573] gimp-2.10(+0x1138b7)[0x5645c94258b7] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19d)[0x7f3915363e8d] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x27555)[0x7f3915377555] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xd8e)[0x7f39153804ae] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f3915380b6f] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19d)[0x7f3915363e8d] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x27555)[0x7f3915377555] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xd8e)[0x7f39153804ae] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f3915380b6f] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x8de25)[0x7f3915d4ce25] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19d)[0x7f3915363e8d] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x276a4)[0x7f39153776a4] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xd8e)[0x7f39153804ae] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f3915380b6f] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x8cd69)[0x7f3915d4bd69] /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x1331eb)[0x7f3915df21eb] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19d)[0x7f3915363e8d] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x26dad)[0x7f3915376dad] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+
Re: GIMP Crash
Le 17/03/2019 à 01:27, Adam Haas a écrit : > I was working with the Gnu Image Manipulation Program yesterday when a > segmentation fault occurred. Attached is the information spit out in > association with the event. Please let me know what additional > information you need from me and I will pass it along. > > - Adam Haas Hello, Can you send the content of your /etc/apt/sources.list ? Thanks.
Re: libreoffice crash
On Sat, 8 Feb 2020 23:06:05 + "Ólafur Jens Sigurðsson" wrote: > Any ideas on what could be the problem here? What, if anything do you get if you try it from a terminal? Run "soffice". -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: libreoffice crash
On Sat, Feb 08, 2020 at 04:10:04PM -0700, Charles Curley wrote: > On Sat, 8 Feb 2020 23:06:05 + > "Ólafur Jens Sigurðsson" wrote: > > > Any ideas on what could be the problem here? > > What, if anything do you get if you try it from a terminal? Run > "soffice". The same as if I run localc, it crashes. See the pastebin link I gave in the first post for the results. Oli
Re: libreoffice crash
On 2020-02-08, Ólafur Jens Sigurðsson wrote:
> Hi, I upgraded my system to Buster finally but after that then
> LibreOffice crashes on me. I have tried to uninstall it and reinstall,
> no luck there. I tried as a different user, same crash there.
>
> I am out of ideas. I have pasted an strace -f of opening localc from the
> command line https://pastebin.com/Ev55tVUH
> Any ideas on what could be the problem here?
You might try moving your old config out of the way as a stab
in the dark to see if that might improve things.
mv ~/.config/libreoffice{,.old}
> TIA, Oli
>
>
--
"J'ai pour me guérir du jugement des autres toute la distance qui me sépare de
moi." Antonin Artaud
Re: libreoffice crash
On Sun, 9 Feb 2020 09:22:47 - (UTC) Curt wrote: Hello Curt, >You might try moving your old config out of the way as a stab >in the dark to see if that might improve things. Even easier is to, from the command line, start 'soffice --safe-mode' -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" The public gets what the public wants Going Underground - The Jam pgpWSWzH2Kb1l.pgp Description: OpenPGP digital signature
Re: libreoffice crash
On Sun, Feb 09, 2020 at 10:04:45AM +, Brad Rogers wrote: > On Sun, 9 Feb 2020 09:22:47 - (UTC) > Curt wrote: > > Hello Curt, > > >You might try moving your old config out of the way as a stab > >in the dark to see if that might improve things. > > Even easier is to, from the command line, start 'soffice --safe-mode' Hi, thanks for the suggestions but no luck, still crashes Cheers, Oli
Re: libreoffice crash
On 2020-02-09, Ólafur Jens Sigurðsson wrote: >> >> Even easier is to, from the command line, start 'soffice --safe-mode' > > Hi, thanks for the suggestions but no luck, still crashes I'm uncertain what version you're using in Buster (packages.debian.org is not responding from here), but another stab in the darkness would be to turn off opengl, which can be done in versions >= 5.3 soffice --safe-mode Select "Configure" -> "Disable Hardware Acceleration (OpenGL, OpenCL)" or in versions 5.2 and older by editing the 'registrymodifications.xcu' file found in your user profile folder and setting the 'UseOpenGL' and 'ForceOpenGL' entries to false. > Cheers, Oli > > -- "J'ai pour me guérir du jugement des autres toute la distance qui me sépare de moi." Antonin Artaud
Re: libreoffice crash
On Sun, Feb 09, 2020 at 01:04:18PM -, Curt wrote: > On 2020-02-09, Ólafur Jens Sigurðsson wrote: > >> > >> Even easier is to, from the command line, start 'soffice --safe-mode' > > > > Hi, thanks for the suggestions but no luck, still crashes > > I'm uncertain what version you're using in Buster (packages.debian.org > is not responding from here), but another stab in the darkness would be > to turn off opengl, which can be done in versions >= 5.3 > > soffice --safe-mode > Select "Configure" -> "Disable Hardware > Acceleration (OpenGL, OpenCL)" > > or in versions 5.2 and older by editing the 'registrymodifications.xcu' > file found in your user profile folder and setting the 'UseOpenGL' and > 'ForceOpenGL' entries to false. Well, dpkg -s libreoffice gives me "Version: 1:6.1.5-3+deb10u5", so that is > 5.3 and soffice --safe-mode crashes on me so I can't disable HA from there. Cheers, Oli
Re: libreoffice crash
On Sun, Feb 9, 2020 at 11:11 AM Ólafur Jens Sigurðsson wrote: > On Sun, Feb 09, 2020 at 01:04:18PM -, Curt wrote: > > On 2020-02-09, Ólafur Jens Sigurðsson wrote: > > >> > > >> Even easier is to, from the command line, start 'soffice --safe-mode' > > > > > > Hi, thanks for the suggestions but no luck, still crashes > I run sid, and had pretty consistent crashing after an "aptitude full-upgrade" a month or so back.Typically I'd leave a doc open while I went and did something else for a while, and then come back to find that LO was no longer open. I looked into it a bit, but not a lot, figuring, "Meh, I run sid; expect brokenness." Then after a week or two, another full-upgrade seems to have solved the problem. Sorry I don't have better info to help, but maybe there's a clue here that means something to someone. -- Kent West<")))>< Westing Peacefully - http://kentwest.blogspot.com
Re: libreoffice crash
On Sun, Feb 09, 2020 at 01:04:18PM -, Curt wrote: > On 2020-02-09, Ólafur Jens Sigurðsson wrote: > >> > >> Even easier is to, from the command line, start 'soffice --safe-mode' > > > > Hi, thanks for the suggestions but no luck, still crashes > > I'm uncertain what version you're using in Buster (packages.debian.org > is not responding from here), but another stab in the darkness would be > to turn off opengl, which can be done in versions >= 5.3 > > soffice --safe-mode > Select "Configure" -> "Disable Hardware > Acceleration (OpenGL, OpenCL)" Ahh, so sorry, my problem reporting skills are suboptimal at the moment it seems. The crash of libreoffice happens immediately, I don't get up any interface. This is why I ran strace and pasted it in pastebin so someone who knows how to read strace could perhaps find out what the problem is. Cheers, Oli
X server crash
Hey All, New to Debian...breaking from tradition and market forces. Just installed Debian on an older machine and configured X during setup. Computer = pentium pro 200 Video = Trident tgui 9680, svga 640x480,8 bpp Mouse = generic 2-button serial I keep getting "fatal server error: cannot open mouse(no such file or directory)" I've checked X11 config file and changed the mouse but still get the error.Any suggestions?...Thanks!
nfs client crash
Hi, I get the following message and the machine crashes, apparently when it tries to access our nfs server. nfs: task 588 cant get a request slot This is not the server problem (most probably) as the files can be accessed at the same time from someother client machine. This error occurs only in certain specific machines. The clients runs a mix of stormix and debian potato 2.2. The file systems are mounted in the client using autofs while in the server, they are mounted at boot time using /etc/fstab. Any suggestions? Suresh - Suresh Kumar.R Email: [EMAIL PROTECTED] Dept of Electronics & Communication College of Engineering, Trivandrum - 695 016 INDIA
Re: Panel Crash
On Mon, Oct 30, 2000 at 12:16:06PM +0100, [EMAIL PROTECTED] wrote: > > > Hi list, > I've make an upgrade from potato to woody and now the gnome panel at startup > crashes (segmentation fault) > any idea on what i should check? > Try to move away your ~/.gnome* directories. You will lose most of the personal settings this way. As they say, TANSTAAFL (or something like that). If it works and you have time on hands, you can try replacing the old files one by one up to find the actual one that crashed the panel (~/.gnome/panel is my guess). So you'll minimize the lost settings ( but it might be easier just to recreate them ). > > ***Internet Email Confidentiality Footer*** > A confidentiality note on a public mailing list does not make sense, and surely does not help you to get the answer you need. BTW, I'm not this debian-user your e-mail is addressed for, and as directed I inform you that your e-mail may be mis-directed. I hope for your business that noone on this list will misuse the top-secret information you inadvertently(I'm sure) gave away. :-) > > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
nfs client crash
Hi, I get the following message and the machine crashes, apparently when it tries to access our nfs server. nfs: task 588 cant get a request slot This is not the server problem (most probably) as the files can be accessed at the same time from someother client machine. This error occurs only in certain specific machines. The clients runs a mix of stormix and debian potato 2.2. The file systems are mounted in the client using autofs while in the server, they aremounted at boot time using /etc/fstab. Any suggestions? Suresh - Suresh Kumar.R Email: [EMAIL PROTECTED] Dept of Electronics & Communication College of Engineering, Trivandrum - 695 016 INDIA __ Do You Yahoo!? Yahoo! Messenger - Talk while you surf! It's FREE. http://im.yahoo.com/
Re: Crash recovery.
on Wed, Nov 01, 2000 at 11:01:28PM +1000, [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote: > > Hi Everyone, > > Had a fun experience today. Debian hung and refused any input. The > only option I had was to power it down. The reboot failed dropping me > at the command prompt to run fsck manually. This fixed this and that > and place a number of things in to /lost+found. Rebooting again and > this time we get stuck starting syslogd. Recreating the dir /var/run > got me past that but there are obviously still issues from the > problem. What I need to know is a way to either work out what was > crunched and placed in /lost+found, whether or not knowing this is > good enough, and some way of checking the current status of the system > to repair what is now broken. > > Any input is appreciated. Backups would be good to have at this point, wouldn't they? I ran mine this morning. First measure at this point is to decide what's valuable to you on the system, and make sure that it's safe. This would include personal data, system configuration data (/etc and your dpkg selections, also /var/backups), and anything under /usr/local. I would *avoid booting from the system* until I've had time to assess the extent of the damage. Your Debian installation disk, Tom's Root/Boot, or the LinuxCare Bootable Business card are all bootable GNU/Linux systems on removable media, and are strongly recommended. My personal favorite is the LinuxCare bootable, you can get the ISO image by rooting around at http://www.linuxcare.com/. I would run an e2fsck on all filesystems, *without* allowing correction of defects first. If you're dealing with only a few damanged files, it's probably OK to go ahead and allow the corrections. If there are lots (more than a dozen or so) of damaged files, chances are pretty good that there's a more fundamental problem. If possibly, you may want to salvage more of the system (backups from read-only mounted media). If the system isn't too badly hosed, you will need to identify which files under /lost+found directories are what. You're basically going to have to do some forensics here, there's no straightforward way of doing this. Until you've identified what is or isn't damaged, boot the system single-user mode *only*. You can spawn additional terminals if necessary (man getty), but it's a good idea to leave the system as quiescent as possible until you've patched things up. You may want to reinstall packages associated with more seriously damanged files. You should also look for any possible indication of a hack or other attack -- usually this will involve changed files under /bin, /sbin, /usr/bin, or /usr/sbin, and sometimes odd directory names like '...' or '.. ' (note the space). If the system *is* badly damaged, salvage what you can, buy a new disk drive, confirm that you don't have problems somewhere else down the line (controller, motherboard, CPU -- diagnostics, anyone?), and try a fresh installation using your existing package selection, then restore personal and local data. Good luck. -- Karsten M. Self http://www.netcom.com/~kmself Evangelist, Opensales, Inc.http://www.opensales.org What part of "Gestalt" don't you understand? There is no K5 cabal http://gestalt-system.sourceforge.net/http://www.kuro5hin.org pgpFhhHpqMCuU.pgp Description: PGP signature
Re: kernel crash.
on Tue, Dec 05, 2000 at 11:50:55PM -, Diarmuid Drew ([EMAIL PROTECTED])
wrote:
> I'm trying to share my PCMCIA multifunctional card (Psion Gold Card
> Netglobal 56K+10/100Mb CardBus, PCMCIA 3.1.22, debian 2.2r2, kernel 2.2.17)
> with an another debian computer on my network (2 machines on network, my
> laptop and duron based machine with crossover cable). PPPd seems to die and
> then the network hangs on a tx timeout, resulting in a complete freeze.
> Normally I just reset and try again with later releases of the drivers,
> however tonight I left the screen to see if it would unfreeze.
>
> I looked in an hour later and there was a kernel oops/crash on the screen
> (I'd been watching the eth0 debug messages on screen with tail -f
> /var/log/syslog). I seem to remember Aiee Mmmm killed interrupt
> handler.Mmmm.. killed idle task ?
>
> My question is as the machine has hung how do I get a copy of the crash data
> (dump ?). Is it stored somewhere or should I resort to pen and paper ?
>
> What are the most important bits to report ? Where do I report it, PCMCIA
> 3.1.22 bug, pppd bug, kernel bug ?
>
> Help !
>
> Derm.
There's a file under /usr/src/linux regarding kernel bug reporting and
what data you should provide. I've converted this to a script -- you
might use a log watcher to detect kernel oopses and/or find another
trigger to run this. Note that there are certain assumptions of
binaries that you should have installed on your system, noteably
ksymoops, which should be on your search path. I install this under
/usr/local/sbin.
Magic Sys-Rq might also be helpful to you in these circumstances.
Reporting: kernel bug, kernel version, suspected modules, activity ,
triggering behavior, and/or log output.
--
Karsten M. Self http://www.netcom.com/~kmself
Evangelist, Zelerate, Inc. http://www.zelerate.org
What part of "Gestalt" don't you understand? There is no K5 cabal
http://gestalt-system.sourceforge.net/http://www.kuro5hin.org
#!/bin/bash
# Kernel bug report generator script
# Script generated from prior bug report form by Karsten M. Self
# $Revision: 1.3 $ $Date: 2000/05/13 07:48:36 $ $Author: root $
#
# [Some of this is taken from Frohwalt Egerer's original linux-kernel FAQ]
#
# What follows is a suggested procedure for reporting Linux bugs. You
# aren't obliged to use the bug reporting format, it is provided as a guide
# to the kind of information that can be useful to developers - no more.
#
# If the failure includes an "OOPS:" type message in your log or on
# screen please read "Documentation/oops-tracing.txt" before posting your
# bug report. This explains what you should do with the "Oops" information
# to make it useful to the recipient.
#
# Send the output the maintainer of the kernel area that seems to
# be involved with the problem. Don't worry too much about getting the
# wrong person. If you are unsure send it to the person responsible for the
# code relevant to what you were doing. If it occurs repeatably try and
# describe how to recreate it. That is worth even more than the oops itself.
# The list of maintainers is in the MAINTAINERS file in this directory.
#
# If you are totally stumped as to whom to send the report, send it to
# [EMAIL PROTECTED] (For more information on the linux-kernel
# mailing list see http://www.tux.org/lkml/).
#
# This is a suggested format for a bug report sent to the Linux kernel mailing
# list. Having a standardized bug report form makes it easier for you not to
# overlook things, and easier for the developers to find the pieces of
# information they're really interested in. Don't feel you have to follow it.
#
#First run the ver_linux script included as scripts/ver_linux or
# at ftp://ftp.sai.msu.su/pub/Linux/ver_linux> It checks out
# the version of some important subsystems. Run it with the command
# "sh scripts/ver_linux"
#
# Use that information to fill in all fields of the bug report form, and
# post it to the mailing list with a subject of "PROBLEM: " for easy identification by the developers
#
# indent by one tabstop
function tabout () { sed -e '/^/s// /'; }
kversion=$( uname -r )
dmesg=dmesg
dmesg="cat /var/log/kern.log" # for debugging only
oops_number=$( $dmesg | grep Oops | tail -1 | sed -e '/^.*:/s///' )
oops_module=$( $dmesg | grep EIP | tail -1 | sed -e '/^.*:/s///' )
cat <
pgpxufpO6mj1q.pgp
Description: PGP signature
Re: KDM crash
Wayne, Didn't see a response to your mail. The kde address doesn't look correct either (what is it?). This sounds like a qt issue my friend had not very long ago (2-3weeks). Try to start kde2 without a manager so you can read the errors and see if that is the case. I am subscribed to debian-kde@lists.debian.org and that might be a good alternative for help with qt's. [EMAIL PROTECTED] Best of luck On Wednesday 31 January 2001 10:10, [EMAIL PROTECTED] wrote: > I was working in KDE 2.0 fine. I had installed licq via dselect. I run > Debian 2.2 r2. I tried to bring up the menu editor to make a link on it to > licq. But everytime I clicked on the menu editor, it would not come up. > Stupidly I hit ctrl+alt+backspace to get out of kde so I could restart the > X server. KDM started to come up the the screen went back to console mode. > I rebooted, but the same thing happens. I used dselect to un-install kdm > and then reinstall it, no luck. I installed GDM, it comes up on boot, but > when I try to log in, I choose KDE as the session to load, but it starts to > load, then kicks me back out to GDM. If I type startx it x comes up, but > without a window manager, just the grey screen. I've looked in the system > error logs, but find nothing. If I type kdm it just gives me another > prompt, no errors. > > Wayne -- Jaye Inabnit, ARS ke6sls e-mail: [EMAIL PROTECTED] 707-442-6579 h/m 707-268-4074 http://www.qsl.net/ke6slsICQ# 12741145 This mail composed with kmail on kde on X on linux warped by debian If it's stupid, but works, it ain't stupid.
Re: Crash-URL
On Fri, May 19, 2000 at 11:14:15PM +0200, Sven Burgener wrote: > Hello > > I once saw a link on a page that caused windows to crash immediately > when clicked on. It was stated on that very page that this would happen. > So then I tried it and it worked! Unfortunately I lost the URL. :*( > Anyone know of this? Perhaps it's something like "NUL" or so which > supposedly is a reserved name under windows? > > TIA! > Sven Probably so ... perhaps something like ? -- __ _ __ _ Justin Megawarne [ Solitude ] Tel: +44 (0)20 8863 0718 <[EMAIL PROTECTED]> Cel: +44 (0)7941 270 136 http://kholmes.dhis.net/ irc.destructor.net && irc.xchat.org - #Linux
Re: Crash-URL
try this: hello, please click me!! Regards, Shao. Sven Burgener [EMAIL PROTECTED] wrote: > Hello > > I once saw a link on a page that caused windows to crash immediately > when clicked on. It was stated on that very page that this would happen. > So then I tried it and it worked! Unfortunately I lost the URL. :*( > Anyone know of this? Perhaps it's something like "NUL" or so which > supposedly is a reserved name under windows? > > TIA! > Sven > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > > -- Shao Zhang - Running Debian 2.1 ___ _ _ Department of Communications/ __| |_ __ _ ___ |_ / |_ __ _ _ _ __ _ University of New South Wales \__ \ ' \/ _` / _ \ / /| ' \/ _` | ' \/ _` | Sydney, Australia |___/_||_\__,_\___/ /___|_||_\__,_|_||_\__, | Email: [EMAIL PROTECTED] |___/ _
Re: Crash-URL
No crash. Opera 3.62 for Win32 says, "Could not open file." T. Shao Zhang wrote (on 24 May 00, at 14:37): try this: hello, please click me!! Regards, Shao. Sven Burgener [EMAIL PROTECTED] wrote: > Hello > > I once saw a link on a page that caused windows to crash immediately > when clicked on. It was stated on that very page that this would happen. > So then I tried it and it worked! Unfortunately I lost the URL. :*( > Anyone know of this? Perhaps it's something like "NUL" or so which > supposedly is a reserved name under windows? > > TIA! > Sven > > > -- > Unsubscribe? mail -s unsubscribe debian-user- [EMAIL PROTECTED] < /dev/null > > -- __ __ Shao Zhang - Running Debian 2.1 ___ _ _ Department of Communications / __| |_ __ _ ___ |_ / |_ __ _ _ _ __ _ University of New South Wales \__ \ ' \/ _` / _ \ / /| ' \/ _` | ' \/ _` | Sydney, Australia |___/_||_\__,_\___/ /___|_||_\__,_|_||_\__, | Email: [EMAIL PROTECTED] |___/ __ ___ -- Unsubscribe? mail -s unsubscribe debian-user- [EMAIL PROTECTED] < /dev/null -- Tony Crawford -- [EMAIL PROTECTED] -- Phone: +49-3341-30 99 99 -- Fax: +49-3341-30 99 98
RE: Crash-URL
clever ol' opera. it certainly crashes ie4, 5. > -Original Message- > From: Tony Crawford [mailto:[EMAIL PROTECTED] > Sent: 24 May 2000 13:46 > To: debian-user@lists.debian.org > Subject: Re: Crash-URL > > > No crash. Opera 3.62 for Win32 says, "Could not open file." > > T. > > Shao Zhang wrote (on 24 May 00, at 14:37): > > try this: > hello, please click me!! > Regards, Shao. Sven Burgener [EMAIL PROTECTED] wrote: > Hello > > I > once saw a link on a page that caused windows to crash immediately > > when clicked on. It was stated on that very page that this would > happen. > So then I tried it and it worked! Unfortunately I lost the > URL. :*( > Anyone know of this? Perhaps it's something like "NUL" or > so which > supposedly is a reserved name under windows? > > TIA! > > Sven > > > -- > Unsubscribe? mail -s unsubscribe debian-user- > [EMAIL PROTECTED] < /dev/null > > -- > __ > __ Shao Zhang - Running Debian 2.1 ___ _ _ Department of > Communications / __| |_ __ _ ___ |_ / |_ __ _ _ _ __ _ University of > New South Wales \__ \ ' \/ _` / _ \ / /| ' \/ _` | ' \/ _` | Sydney, > Australia |___/_||_\__,_\___/ /___|_||_\__,_|_||_\__, | Email: > [EMAIL PROTECTED] |___/ > __ > ___ -- Unsubscribe? mail -s unsubscribe debian-user- > [EMAIL PROTECTED] < /dev/null > -- Tony Crawford > -- [EMAIL PROTECTED] > -- Phone: +49-3341-30 99 99 > -- Fax: +49-3341-30 99 98 > > > -- > Unsubscribe? mail -s unsubscribe > [EMAIL PROTECTED] < /dev/null >
RE: Crash-URL
> clever ol' opera. > it certainly crashes ie4, 5. > possibly opera has a work-around for it, but basically this is no browser issue - it's a winDOS (=win9x) one. you could theoretically make the same by opening c:\con\con from the file manager or something. on securityfocus (don't remember, which list it was) was (again) a discussion about that two or three months ago. however ... what has this question to do on THIS list?!?!? ;-) -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- If Windows is the answer, I want the problems back!
Re: crash diagnostics
try running your mahcine w/o a swap partition setup to see if the problem persists, (its just a shot in the dark..) you may have bad sectors on the drive where the swap partition resides. nate On Fri, 28 Jan 2000, Werner Reisberger wrote: werner >I am still having occasional kernel panics and don't know why. Today an Oops werner >happened some hours before the panic (when I did 'make zImage'). The Oops werner >left the kswaps daemon as zombie and I had to reboot the system. Following werner >is the output of the Oops. I would really appreciate if somebody could werner >give me any hint what could be wrong with my Debian system. I can't analyze werner >the data with ksymoops because I couldn't compile ksymoops and I probably werner >would experience another crash if I would try it. werner > werner >## werner >Jan 28 16:28:43 quod kernel: Unable to handle kernel paging request at virtual address 858994b4 werner >Jan 28 16:28:43 quod kernel: current->tss.cr3 = 00101000, %cr3 = 00101000 werner >Jan 28 16:28:43 quod kernel: *pde = werner >Jan 28 16:28:43 quod kernel: Oops: werner >Jan 28 16:28:43 quod kernel: CPU:0 werner >Jan 28 16:28:43 quod kernel: EIP:0010:[] werner >Jan 28 16:28:43 quod kernel: EFLAGS: 00010287 werner >Jan 28 16:28:43 quod kernel: eax: 858994a0 ebx: c02dc6b0 ecx: 0006 edx: ffe0 werner >Jan 28 16:28:43 quod kernel: esi: 858994a0 edi: c5899500 ebp: c02dc6b0 esp: c000dfa8 werner >Jan 28 16:28:43 quod kernel: ds: 0018 es: 0018 ss: 0018 werner >Jan 28 16:28:43 quod kernel: Process kswapd (pid: 4, process nr: 4, stackpage=c000d000) werner >Jan 28 16:28:43 quod kernel: Stack: 0030 c000c000 c0119fd2 c02dc6b0 000d 0006 c011ed13 0006 werner >Jan 28 16:28:43 quod kernel:0030 c01a9078 c000c1c1 c011edbf 0030 0f00 c0003fb4 werner >Jan 28 16:28:43 quod kernel:c0106000 9000 c0106513 0f00 c01d5fd8 werner >Jan 28 16:28:43 quod kernel: Call Trace: [] [] [] [] [] [] werner >Jan 28 16:28:43 quod kernel: Code: 8b 76 14 83 78 20 00 75 06 f6 40 18 46 74 13 6a 00 e8 4c 01 werner >## werner > werner >I am running a kernel 2.2.10 with Hamm and the newer stuff needed for this werner >kernel. I am guessing my problem is hardware dependend and I am going to werner >exchange my quodry modules if I can't find any other cause for this troubles. werner > werner >I am having this kernel panics since my hosting provider had a power werner >interruption. What kind of PC HW could get damaged by a power interruption werner >resulting in such a behaviour I described? werner > werner >TIA, werner > werner > Werner werner > werner > werner >-- werner >Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null werner > [mailto:[EMAIL PROTECTED] ]-- Vice President Network Operations http://www.firetrail.com/ Firetrail Internet Services Limited http://www.aphroland.org/ Everett, WA 425-348-7336http://www.linuxpowered.net/ Powered By:http://comedy.aphroland.org/ Debian 2.1 Linux 2.0.36 SMPhttp://yahoo.aphroland.org/ -[mailto:[EMAIL PROTECTED] ]-- 11:28am up 162 days, 23:36, 2 users, load average: 1.03, 1.05, 1.01
Re: crash diagnostics
On Sat, Jan 29, 2000 at 11:31:30AM -0800, aphro wrote:
> try running your mahcine w/o a swap partition setup to see if the problem
> persists, (its just a shot in the dark..) you may have bad sectors on the
> drive where the swap partition resides.
Is it possible to start linux w/o a swap partition? I checked the drive
(UW-SCSI) with the diagnostic program of the Adaptec-Controller and didn't
found any bad blocks.
I think it's rather a problem with the RAM. I just checked a core after
a program failed with seg fault. The message found ("Cannot access memory
in 0xa346e32") points to a RAM problem. I think I really have to exchange my
RAM.
Werner
Re: crash diagnostics
its possible to start w/o a swap. depends how much ram you have though
.. i never build linux boxes with less then 64 or 128MB in those cases
swap isn't that important so its easy to turn off..
it may be bad ram..there are a few memory testers out there for linux..try
em out.
nate
On Sun, 30 Jan 2000, Werner Reisberger wrote:
werner >On Sat, Jan 29, 2000 at 11:31:30AM -0800, aphro wrote:
werner >> try running your mahcine w/o a swap partition setup to see if the
problem
werner >> persists, (its just a shot in the dark..) you may have bad sectors on
the
werner >> drive where the swap partition resides.
werner >
werner >Is it possible to start linux w/o a swap partition? I checked the drive
werner >(UW-SCSI) with the diagnostic program of the Adaptec-Controller and
didn't
werner >found any bad blocks.
werner >
werner >I think it's rather a problem with the RAM. I just checked a core after
werner >a program failed with seg fault. The message found ("Cannot access
memory
werner >in 0xa346e32") points to a RAM problem. I think I really have to
exchange my
werner >RAM.
werner >
werner > Werner
werner >
[mailto:[EMAIL PROTECTED] ]--
Vice President Network Operations http://www.firetrail.com/
Firetrail Internet Services Limited http://www.aphroland.org/
Everett, WA 425-348-7336http://www.linuxpowered.net/
Powered By:http://comedy.aphroland.org/
Debian 2.1 Linux 2.0.36 SMPhttp://yahoo.aphroland.org/
-[mailto:[EMAIL PROTECTED] ]--
9:31pm up 164 days, 9:40, 1 user, load average: 1.22, 1.14, 1.05
Acroread/Netscape crash
I am using potato and I have the following problem. I just installed acroread from potato ( non-free ) version 4 and tried to read a pdf file using netscape. Netscape crashes with: Bus Error LD_PRELOAD=/lib/libBRokenLocale.so.1 $netscape "$@" I had this problem with acrobat version 3 as well. This is a problem with netscape clearly since acroread works Ok on its own. Netscape on its own is also OK, ( I have netscape -base 4.5 installed ) and I believe the netscape version is 4.51 Wherein lies the problem? Thanks. Sebastian Canagaratna Department of Chemistry Ohio Northern University Ada, OH 45810
Re: konqueror crash
pol wrote: > Hi all, > > After a couple years working perfectly, kde session restoring begun to > fail a few weeks ago, on my debian/testing laptop. > At the user session opening, every konqueror instance, saved in the > previous session, crashes. Here included the backtrace, from the crash > window panel. lHowever, any new konqueror instaces start flawlessly. > Any idea? Is your system up to date? Just update the system and see if the problem goes away! raju -- Kamaraju S Kusumanchi http://www.people.cornell.edu/pages/kk288/ http://malayamaarutham.blogspot.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
weird mdadm crash
Hello, Have an etch box that does nothing but rsync data with another. About every other day or so, the box will completely freeze. Everything, screen blank, no keyboard, and the hard drive light is on solid. I can hard reboot it and it comes up, and there is nothing in the logs that suggest anything. The root system is an mdadm raid 5 array, and everytime I reboot it from a crash, the array is always degraded. It auto rebuilds itself, and away it goes again. A few days later, it will lock up. I have no idea where to start looking for problems. I'm pretty sure its gotta be hardware, but not sure where to look first. Any suggestions would be great! Thx, Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Eclipse crash
On Tue, Mar 13, 2007 at 04:19:52PM +0100, Christian Ribeaud wrote: > I am desperately trying to get Eclipse 3.2 working on my laptop. I > upgrated java to JDK1.6 but it did not change anything. Crashes are not > predicable and could happen at anytime. Starting Eclipse is not a > problem. Buf, after a couple of minutes, I always get this kind of message: > > # An unexpected error has been detected by Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x00010203, pid=7256, tid=1075764144 > # > # Java VM: Java HotSpot(TM) Client VM (1.6.0-b105 mixed mode, sharing) > # Problematic frame: > # C 0x00010203 > # > # An error report file with more information is saved as hs_err_pid7256.log > # > # If you would like to submit a bug report, please visit: > # http://java.sun.com/webapps/bugreport/crash.jsp > # > This is a long-shot, but it could be a memory issue. Eclipse is a memory hog, how much memory do you have in your computer? How much memory was it using before it crashed? If you open several perspectives and views you will use more memory, so doing that can help you get it to crash more often to get more data about this. Try doing a memtest (with knoppix maybe?) and see if your memory is ok Also, what filesystem are you using in general and for the workspace specifically? -- Tarek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Eclipse crash
Christian Ribeaud wrote: > Hi, > > I am desperately trying to get Eclipse 3.2 working on my laptop. I > upgrated java to JDK1.6 but it did not change anything. Crashes are not > predicable and could happen at anytime. Starting Eclipse is not a > problem. Buf, after a couple of minutes, I always get this kind of message: > > # An unexpected error has been detected by Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x00010203, pid=7256, tid=1075764144 > # > # Java VM: Java HotSpot(TM) Client VM (1.6.0-b105 mixed mode, sharing) > # Problematic frame: > # C 0x00010203 > # > # An error report file with more information is saved as hs_err_pid7256.log > # > # If you would like to submit a bug report, please visit: > # http://java.sun.com/webapps/bugreport/crash.jsp > # > > I read a lot of pages but none solved my problem. Any help would be > gratefully appreciated. As I am quite new to Debian, I maybe forgot > something important. Attached you can find the Eclipse last window > before exit. Hi I had exactly the same problem on a desktop: this problem happened suddenly and never went away (I reinstalled eclipse from scratch but... no way). On the same computer, under Gentoo I'm not having this problem. The only solution I found was to re-install Debian and the problem went away (actually I installed Kubuntu this time) I had also filed a bug report at sun, but got no answer... Please, keep updated should you find a better solution cheers Lorenzo -- Lorenzo Bettini, PhD in Computer Science, DSI, Univ. di Firenze ICQ# lbetto, 16080134 (GNU/Linux User # 158233) HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com http://www.gnu.org/software/src-highlite http://www.gnu.org/software/gengetopt http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
hard disk crash
hi you all out there, one of my hd's crashed completely for unknown reasons. i tried several solutions without any result. knoppix 5.0 recognized the partition with data (/dev/hda1) but refuses to mount it: 'i could not determine the filesystem etc. etc. ' the debian etch network installer (rescue and rescuegui) speaks of 'incorrectable errors' on [ a series ] of hd blocks. mounting /dev/ide/host0/bus0/target0/lun0/partx is refused. a 'normal' boot of the machine (with which i started) stops dead at /boot/vmlinuz-2.6.18-4-686 root=/dev/hda1 ro error 25 disk read error press any key to continue gpart stopped dead analyzing the disk. somebody out there who can give me a helping hand to repair somehow the hd or point me to a method/way or program to rescue at least my holiday-photographs from france i put on the hd two hours before the crash...? any help much appreciated! regards, steef -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
hard disk crash
somebody out there who can give me a helping hand to repair somehow the hd or point me to a method/way or program to rescue at least my holiday-photographs from france i put on the hd two hours before the crash...? The most important thing is to avoid using the disk as much as possible (do not apply power, do not 'spin up' the disk). Then you need to set up to 'rescue' the data. If you have a second computer with Linux then you're off to a good start. You will need to: 1. determine how large a disk you need to create an image of the partitions on your failed drive. Of course you probably need to go out and buy some storage... 2. set up tools to: a. copy all readable blocks from the failed drive b. examine the image for the data you want The tools in (a) allow you to power up the bad drive and copy whatever is possible with the minimum use of the disk. It is not unusual for a disk to be permanently destroyed during this process or shortly afterwards - no fault of the tools, that's just the general way a disk fails. For (a) I would suggest 'ddrescue' which acts like 'dd' but skips bad blocks and simply moves on to the next block. This is the behavior you want - you don't want to attempt a retry at this stage because that can make matters worse. After your image recovery operation then you may consider a second image using something like gddrescue to try to get even more data. For (b) I would suggest 'testdisk'. It is generally used when people accidentally wipe the partition table, but it has good tools for recovering photos. It is very important that you don't try to hurry things - remember you will be lucky to have 1 shot at recovering data from a bad disk; you need to make absolutely sure that first try goes without a flaw. After setting up, practise using these tools on another disk - maybe a faulty floppy, or even just a good disk. You really don't want to make any mistakes when you get to the real job; especially not with a 'dd'-like tool. Once you have recovered an image with ddrescue (and maybe a second image with gddrescue) then you can take your time finding other recovery tools to extract even more data. Remember to mark these images 'read only' - you don't want to accidentally write to them. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
