Date: Fri, 07 Jan 2005 01:29:23 -0500 From: Joe Marcus Clarke <marcus@marcuscom.com> To: Ion-Mihai Tetcu <itetcu@apropo.ro> Cc: FreeBSD GNOME Users <gnome@freebsd.org> Subject: Re: gnome-panel startup problem (NOT /tmp/.ICE-unix ) Message-ID: <1105079363.98989.9.camel@shumai.marcuscom.com> In-Reply-To: <20050107010255.52290ad3@it.buh.cameradicommercio.ro> References: <20050107010255.52290ad3@it.buh.cameradicommercio.ro>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-JMlcm2IMdh/NekaMgLkO Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2005-01-07 at 01:02 +0200, Ion-Mihai Tetcu wrote: > Hi, >=20 >=20 > I'm "gnome-newbie" so please don't shoot to hard. >=20 > On a newly installed 5.3-STABLE with updated ports tree I've installed > gnome2 a few days ago, hoping is a little bit less resource-hungry > compared with kde. >=20 > Today, finding some time to play, I've log-in into gnome and enabled the > accessibility module (gnopernicus ?) plus added a few applets (?) (the > system monitor and a few others in the bottom bar).=20 >=20 > After logout when I login now I get a box saying: " I've detected a > panel already running and will now exit" - the result being no menu bar, > no bottom bar and no shortcuts (ALT+F1, Alt+F2..) working. >=20 > I've tried to remove gnome config files from my home dir (see below, I > don't think I've missed any, but..) with no good result. >=20 > Please give me some (doc) pointer on what to do. This might very well be related to gnopernicus. I don't think it's received much testing on FreeBSD. Did you enable gnopernicus each time you started GNOME on a fresh account? >=20 > itetcu@zetha >-SSH-> /home/itetcu [0:53:28] 1 > > ll -a > total 1652 > drwxr-xr-x 7 itetcu wheel 1024 Jan 7 00:40 . > drwxr-xr-x 3 root wheel 512 Dec 31 19:23 .. > -rw-r--r-- 1 itetcu wheel 767 Dec 31 19:23 .cshrc > -rw------- 1 itetcu wheel 1230 Jan 6 22:42 .history > drwx------ 2 itetcu wheel 512 Jan 3 17:22 .links > -rw-r--r-- 1 itetcu wheel 248 Dec 31 19:23 .login > -rw-r--r-- 1 itetcu wheel 158 Dec 31 19:23 .login_conf > -rw------- 1 itetcu wheel 373 Dec 31 19:23 .mail_aliases > -rw-r--r-- 1 itetcu wheel 331 Dec 31 19:23 .mailrc > -rw-r--r-- 1 itetcu wheel 797 Dec 31 19:23 .profile > -rw------- 1 itetcu wheel 276 Dec 31 19:23 .rhosts > -rw-r--r-- 1 itetcu wheel 975 Dec 31 19:23 .shrc > drwxr-xr-x 2 itetcu wheel 512 Jan 6 17:15 .ssh > -rw-r--r-- 1 itetcu wheel 29 Jan 3 17:22 .xinitrc > -rw-r--r-- 1 itetcu wheel 10739 Jan 3 18:16 .xscreensaver > drwxr-xr-x 2 itetcu wheel 512 Jan 3 17:26 Desktop > -rw-r--r-- 1 itetcu wheel 3473 Jan 3 17:34 XF86Config > drwxr-xr-x 18 root wheel 1024 Jan 7 00:37 _cccache > -rw------- 1 itetcu wheel 1 Jan 5 16:36 dead.letter > -rw-r--r-- 1 itetcu wheel 0 Jan 7 00:40 gol > drwxr-xr-x 2 root wheel 512 Dec 31 19:46 kernels > -rw------- 1 itetcu wheel 1613824 Jan 6 22:36 srcore.core This core file looks interesting. That's from gnopernicus. Rebuilding gnopernicus with debugging symbols, then running the core through gdb might give us an idea as to why srconf is crashing. You can also try adding one applet/feature at a time, and see which one causes the panel problems. Such problems are not common which is why I'm thinking it's related to gnopernicus. Joe >=20 >=20 > Thanks, >=20 --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-JMlcm2IMdh/NekaMgLkO Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBB3ixDb2iPiv4Uz4cRAkteAJ9phjHEi5AC8yT4oX0vhNW/VvxeyACgmgbh FwzjIhWyLIgCgLvi+HFTQt4= =ohm8 -----END PGP SIGNATURE----- --=-JMlcm2IMdh/NekaMgLkO--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1105079363.98989.9.camel>