crash on start. DirectFBError [DirectFBCreate (&adfb) ]: Initialization error!

Bug #305411 reported by Aapo Rantalainen
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
DirectFB
New
Undecided
Unassigned
directvnc (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: directvnc

I try to start directvnc, (I see on serverside it connects) but then it says
dfb.c <47>:
             (#) DirectFBError [DirectFBCreate ( &adfb )]: Initialization error!

I found this is older issue http://ohioloco.ubuntuforums.org/showthread.php?t=178804

I tried compiling from source too. I need this patching, because of newer libdirectfb
http://mail.directfb.org/pipermail/directfb-users/2005-April/000182.html
I got same error message than repository version.

Checked on Hardy and Intrepid.
directvnc 0.7.5
libdirect
libdirectfb-1.0-0 versions:
hardy:1.0.1-7ubuntu3
intrepid:1.0.1-9ubuntu1

Revision history for this message
helix84 (helix84) wrote :

I ran into this issue on karmic i386 after I upgraded to 0.7.6-1 from Debian sid due to bug #523106.

Revision history for this message
Loris B. (lboillet69) wrote :

helix84, what is/was your libdirectfb version? Are you sure the bug is related to directvnc and not to your directfb setup? what does the dfbinfo command output (from libdirectfb-bin package).

Revision history for this message
helix84 (helix84) wrote :

rc libdirectfb-0.9-25 0.9.25.1-6ubuntu3 direct frame buffer graphics - shared libraries
rc libdirectfb-1.0-0 1.0.1-11ubuntu1 direct frame buffer graphics - shared libraries
ii libdirectfb-1.2-0 1.2.7-2ubuntu1 direct frame buffer graphics - shared libraries
ii libdirectfb-dev 1.2.7-2ubuntu1 direct frame buffer graphics library - development files
ii libdirectfb-extra 1.2.7-2ubuntu1 direct frame buffer graphics - extra providers
ii directvnc 0.7.6-1 VNC client using the framebuffer as display

$ dfbinfo

   ~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.2.7 |~~~~~~~~~~~~~~~~~~~~~~~~~~
        (c) 2001-2008 The world wide DirectFB Open Source Community
        (c) 2000-2004 Convergence (integrated media) GmbH
      ----------------------------------------------------------------

(*) DirectFB/Core: Single Application Core. (2009-06-02 06:33)
(!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed
    --> No such file or directory
(!) DirectFB/FBDev: Error opening framebuffer device!
(!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment variable.
(!) DirectFB/Core: Could not initialize 'system_core' core!
    --> Initialization error!
(#) DirectFBError [DirectFBCreate() failed]: Initialization error!

Seems you were right, this is the very same message directvnc gives me. I added directvnc to affects, but they don't seem to track bugs in LP and I have yet to find the upstream tracker.

Revision history for this message
Loris Boillet (drinkmilk007) wrote :

Months passed but...

I guess you meant "added directFB to affects"?

Anyway, directFB has a bug tracker (the link is on their main page), but it seems to be down at the moment. To limit confusion, I changed the status to "invalid" for directvnc, but I am not familiar enough with LP to know if that's the right way to do it so feel free to "fix" it if needed.

Changed in directvnc (Ubuntu):
status: New → Invalid
Revision history for this message
Aapo Rantalainen (aapo-rantalainen) wrote :

I can't remember anymore what computer I was using when reporting this first time.

Where is up to date instructions how to use directFB with Lucid Lynx?
(e.g. is there needed kernel modules in stock kernel and so on)

http://www.tldp.org/HOWTO/Framebuffer-HOWTO.html contains comparisons between Linux kernel 2.1 and 2.2.

Revision history for this message
helix84 (helix84) wrote :

> I guess you meant "added directFB to affects"?

That's coorect.

> Anyway, directFB has a bug tracker (the link is on their main page), but it seems to be down at the moment.

I see, I notified them of their tracker being down and I hope I'll remember to report this bug when they get the tracker running.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.