| View previous topic :: View next topic |
| Author |
Message |
linuxsir320
n00b
Joined: 11 Mar 2010
Posts: 26
|
 Posted: Thu Mar 11, 2010 2:48 pm Post subject: obconf, Segmentation fault on ~amd64[solved] |
 |
|
[I] x11-misc/obconf
Available versions: 2.0.3 {nls}
Installed versions: 2.0.3(08:46:39 PM 02/27/2010)(-nls)
Homepage: http://icculus.org/openbox/index.php/ObConf:About
Description: ObConf is a tool for configuring the Openbox window manager.
[I] x11-wm/openbox
Available versions: (3) 3.4.7.2 3.4.10 (~)3.4.11
{+imlib nls (+)startup-notification xinerama}
Installed versions: 3.4.11(3)(07:57:47 PM 02/25/2010)(imlib startup-notification -nls -xinerama)
Homepage: http://icculus.org/openbox/
Description: A standards compliant, fast, light-weight, extensible window manager.
| Code: |
(obconf:18793): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(obconf:18793): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(obconf:18793): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(obconf:18793): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(obconf:18793): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(obconf:18793): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(obconf:18793): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(obconf:18793): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(obconf:18793): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(obconf:18793): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(obconf:18793): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(obconf:18793): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(obconf:18793): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(obconf:18793): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(obconf:18793): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(obconf:18793): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(obconf:18793): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(obconf:18793): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
Segmentation fault
|
Last edited by linuxsir320 on Sat Mar 13, 2010 6:48 am; edited 2 times in total |
|
| Back to top |
|
 |
Jaglover
Advocate
Joined: 29 May 2005
Posts: 3404
Location: Saint Amant, Acadiana
|
| Posted: Thu Mar 11, 2010 2:51 pm Post subject: |
|
|
Try emerge --resume
If it segfaults in same other place then you have a hardware problem. |
|
| Back to top |
|
|
linuxsir320
n00b
Joined: 11 Mar 2010
Posts: 26
|
| Posted: Fri Mar 12, 2010 3:03 pm Post subject: |
|
|
| Jaglover wrote: | Try emerge --resume
If it segfaults in same other place then you have a hardware problem. |
nothing to resume.
hardware problem ????? |
|
| Back to top |
|
|
Mike Hunt
Watchman
Joined: 19 Jul 2009
Posts: 5287
|
| Posted: Fri Mar 12, 2010 3:18 pm Post subject: |
|
|
Maybe first try emerging them in the proper order: | Code: | ~ # emerge -pq openbox obconf
[ebuild N ] media-libs/imlib2-1.4.2-r1
[ebuild N ] x11-wm/openbox-3.4.11
[ebuild N ] x11-misc/obconf-2.0.3 |
|
|
| Back to top |
|
|
krinn
Advocate
Joined: 02 May 2003
Posts: 3204
|
| Posted: Fri Mar 12, 2010 4:30 pm Post subject: |
|
|
| linuxsir320 wrote: | nothing to resume.
hardware problem ????? |
Resume has nothing to do with hardware problem, he was trying to explain: if you have an hardware problem, chances that the problem occurs at the same place/line of code are really low. So when you have a crash, if you rebuild and it crash again at a different place, this might (not always true) show an hardware problem.
If it crash always at the same place, then this is probably more a problem with the code itself (missing library...) but not hardware.
This is generally true for compile or segfault while compiling, but harder to see when running a program. Wihtout any debug infos, if the program crash at random place you can hardly tell it's hardware because you'll only get "segfault" error, so hard to say where it crash.
And even you success at finding you get random crash, you can still hardly tell it's hardware when speaking about a running program : the butterfly effect really could be apply to a running program: a problem somewhere could crash the program far later in some others random places
That's also what bugs generally do. A broken toolchain that was used to built the program also.
And i think it might get clearer if you consider he misunderstood it was a running program output. That's why he ask a --resume
I would say as them (mike hunt and jaglover): answer is certainly about compile troubles (considering you might have already tweak the program configuration file if any exist, and/or remove it). But i would (as i always do) rebuild toolchain first, then the program, and if you have twist cflags, lower them for that program: cflags not only have impact when compiling a program, they also impact how the program will run. |
|
| Back to top |
|
|
Mike Hunt
Watchman
Joined: 19 Jul 2009
Posts: 5287
|
| Posted: Fri Mar 12, 2010 4:51 pm Post subject: |
|
|
yes, yes.
now go ahead and post your emerge --info please |
|
| Back to top |
|
|
linuxsir320
n00b
Joined: 11 Mar 2010
Posts: 26
|
| Posted: Sat Mar 13, 2010 3:24 am Post subject: |
|
|
| krinn wrote: | | linuxsir320 wrote: | nothing to resume.
hardware problem ????? |
Resume has nothing to do with hardware problem, he was trying to explain: if you have an hardware problem, chances that the problem occurs at the same place/line of code are really low. So when you have a crash, if you rebuild and it crash again at a different place, this might (not always true) show an hardware problem.
If it crash always at the same place, then this is probably more a problem with the code itself (missing library...) but not hardware.
This is generally true for compile or segfault while compiling, but harder to see when running a program. Wihtout any debug infos, if the program crash at random place you can hardly tell it's hardware because you'll only get "segfault" error, so hard to say where it crash.
And even you success at finding you get random crash, you can still hardly tell it's hardware when speaking about a running program : the butterfly effect really could be apply to a running program: a problem somewhere could crash the program far later in some others random places
That's also what bugs generally do. A broken toolchain that was used to built the program also.
And i think it might get clearer if you consider he misunderstood it was a running program output. That's why he ask a --resume
I would say as them (mike hunt and jaglover): answer is certainly about compile troubles (considering you might have already tweak the program configuration file if any exist, and/or remove it). But i would (as i always do) rebuild toolchain first, then the program, and if you have twist cflags, lower them for that program: cflags not only have impact when compiling a program, they also impact how the program will run. |
Thank you very much!
I changed profile from hardened to default, rebuild world include GCC, and then rebuild obconf. It works.
USE "hardened" is disabled now. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
