From: Stef van der Made <svdmade@planet.nl>
To: Radoslaw Szkodzinski <astralstorm@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Gnome-2.8 stoped working on kernel-2.6.9-rc4-mm1
Date: Wed, 13 Oct 2004 23:16:34 +0200 [thread overview]
Message-ID: <416D9B32.5030408@planet.nl> (raw)
In-Reply-To: <f44c5fdf041013134726043453@mail.gmail.com>
Unpatching optimize-profile-path-slightly.patchsolved the issue. Thanks
for the tip. You also gave the tip that I should compile without
-fomit-frame-pointer. I've done this for years without any problem. What
problems could this cause ?
Thanks again for your help,
Stef
Radoslaw Szkodzinski wrote:
>On Wed, 13 Oct 2004 22:38:19 +0200, Stef van der Made <svdmade@planet.nl> wrote:
>
>
>>I'm trying to get kernel-2.6.9-rc4-mm1 to work with gnome-2.8. While
>>2.6.9-rc4 works fine with gnome-2.8 the mm1 version has an issue. Any
>>process that I'm trying to start that uses gnome libraries crashes
>>immediatly after startup. Mozilla, nautilus and gnome terminal to name a
>>few. The reason for using mm1 is that I'm using reiser4 for one of my
>>partitions.
>>
>>The output that I get in bugbuddy is as following:
>>
>>Backtrace was generated from '/usr/test/garnome2/lib/nautilus'
>>
>><snip>
>>
>>
>This was useless, w/o any information.
>Next time please compile with debugging (-g) and without
>-fomit-frame-pointer. (in case of gcc <3.5)
>
>
>
>>And on the terminal that I started X windows:
>>
>>"/usr/test/garnome2/lib/nautilus": not in executable format: Is a directory
>>/home/stef/405: No such file or directory.
>>/usr/local/mozilla/run-mozilla.sh: line 423: 460 Segmentation
>>fault "$prog" ${1+"$@"}
>><snip>
>>/usr/local/mozilla/run-mozilla.sh: line 423: 483 Segmentation
>>fault "$prog" ${1+"$@"}
>>
>>
>>
>
>Looks like you need to back out this patch, the root of all evil:
>http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.9-rc4/2.6.9-rc4-mm1/broken-out/optimize-profile-path-slightly.patch
>like this:
>cd linux-2.6.9-rc4-mm1
>patch -p1 -R < /download-dir/optimize-profile-path-slightly.patch
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
next prev parent reply other threads:[~2004-10-13 21:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 19:11 [OOPS] 2.6.9-rc4, dual Opteron, NUMA, 8GB Brad Fitzpatrick
2004-10-13 20:01 ` Jeff Garzik
2004-10-13 20:09 ` Brad Fitzpatrick
2004-10-13 20:12 ` Randy.Dunlap
2004-10-13 20:32 ` Brad Fitzpatrick
2004-10-13 20:34 ` Randy.Dunlap
2004-10-13 21:21 ` Andi Kleen
2004-10-14 6:07 ` Brad Fitzpatrick
2004-10-14 18:29 ` Brad Fitzpatrick
2004-10-14 18:40 ` Andi Kleen
2004-10-13 20:45 ` Jeff Garzik
2004-10-13 20:49 ` Brad Fitzpatrick
2004-10-13 20:50 ` Jeff Garzik
2004-10-13 20:38 ` Gnome-2.8 stoped working on kernel-2.6.9-rc4-mm1 Stef van der Made
2004-10-13 20:47 ` Radoslaw Szkodzinski
2004-10-13 21:16 ` Stef van der Made [this message]
2004-10-13 22:08 ` Buddy Lucas
2004-10-13 23:07 ` Jon Masters
2004-10-13 21:13 ` Jesse Stockall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=416D9B32.5030408@planet.nl \
--to=svdmade@planet.nl \
--cc=astralstorm@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox