gnome-volume-manager-2.17 in gnome-2.20

[Joe Marcus Clarke]

Eric L. Chen wrote:
> On Thu, 2007-10-18 at 19:41 -0400, Joe Marcus Clarke wrote:
>> On Thu, 2007-10-18 at 09:46 +0800, Eric L. Chen wrote:
>>> On Wed, 2007-10-17 at 22:29 +0800, Eric L. Chen wrote:
>>>> On Wed, 2007-10-17 at 09:14 +0800, Eric L. Chen wrote:
>>>>> Hi,
>>>>> My gnome-volume-manager cannot startup after upgrade to gnome-2.20.
>>>>> That caused gnome will not mount USB disk automatically, this is a
>>>>> little problem because I've be using gnome+freebsd as my desktop 
>>>>> for a long time.
>>>>>
>>>>> After googled, this is not FreeBSD specified problem, it happened
>>>>> in archlinux, too. See http://bbs.archlinux.org/viewtopic.php?id=37544
>>>>> Discuss more at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=428810
>>>>> I applied their patch and my gnome now can mount USB disk/CDROM
>>>>> automatically.
>>>> Hi Marcus,
>>>> I saw you committed patch to solve local user problem.
>>>> ----
>>>> Fix a dumb bug where we would not be able to detect the local user
>>>> properly.
>>>> This bug was exposed when the integer overflow bug was fixed.  This should
>>>> prevent g-v-m from terminating on startup.
>>>> ----
>>>> But I still cannot startup g-v-m successfully, like:
>>>> ----
>>>>  ~> gnome-volume-manager 
>>>>  ~> ps -ax|grep gnome-volume-manager
>>>>  ~> gnome-volume-manager -n
>>>>  ~> ps -ax | grep gnome-volume-manager
>>>>  2232  p1  R+     0:00.00 grep gnome-volume-manager
>>>>  ~> gnome-volume-manager --sm-disable
>>>>  ~> ps -ax | grep gnome-volume-manager
>>>>  2236  p1  R+     0:00.00 grep gnome-volume-manager
>>>>  ~> ps -ax | grep gnome-volume-manager
>>>>  ~> gnome-volume-manager -d yes
>>>>  ~> ps -ax | grep gnome-volume-manager
>>>> ----
>>>> I am using Intel 2200BG wireless card, maybe it still has problem with wireless connection.
>>>>
>>> After more test, sometimes g-v-m cannot startup automatically, but
>>> sometimes not.
>> I cannot reproduce this behavior on either my i386 or amd64 GNOME 2.20
>> machines.  At the very least you will need to provide ktrace output of
>> when g-v-m does not start properly.  Preferably, you should use gdb to
>> set breakpoints, and figure out why g-v-m is exiting prematurely.
>>
>> Joe
>>
> ktrace attached.
> g-v-m cannot auto startup, set in
> [System]->[Preferences]->[Sessions]->[Startup Programs].
> But can start by [Alt]-[F2] "Run Application".

Looks like /var/run/utmp is 0 bytes.  g-v-m opens this file, and scans
through it to confirm whether or not the current user is logged in
locally on the console.  To do this, it looks for a utmp record on
either one of the ttyv devices or connected from :0.X where X is >= 0
and <= 9.

Looks like there might be some issue with the way you run X, or some
other problem manipulating /var/run/utmp.

Joe

-- 
Joe Marcus Clarke
FreeBSD GNOME Team	::	gnome at FreeBSD.org
FreeNode / #freebsd-gnome
http://www.FreeBSD.org/gnome