Bug#511505: winff does not run at all

2009-03-16 Thread Tomáš Šafařík 
Hello,

for reference

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515035#27

Tomas



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#511505: winff does not run at all

2009-02-12 Thread Paul Gevers 
Hi Tomáš

Please run apt-get source winff in a directory where you want to have
the source. Then, in that directory, change debian/control to include
${misc:Depends} in the depends line, i.e. it should read:


Depends: ffmpeg, xterm | x-terminal-emulator, ${shlibs:Depends},
${misc:Depends}


Now, make sure you have installed: debhelper, lazarus-ide, fpc and fakeroot

Then run fakeroot debian/rules binary, and you should find a binary
(winff_xxx.deb file) in the directory below to install.

Info on: http://lyre.mit.edu/~powell/debian-howto/build-source.html

I hope this works.

Paul

Tomáš Šafařík wrote:
 Hello Paul,
 
 I can try to build winff from sources. Can you please send me some short
 notes how to do it and exactly with what options you need?
 
 Tomas
 
 P.S. I'd response earlier, but somehow I don't get emails when new comment
 is added to the bug.





signature.asc
Description: OpenPGP digital signature

Bug#511505: winff does not run at all

2009-01-28 Thread Paul Gevers 
Just for the record, via IRC (#debian-bugs) I had somebody with a
powerpc test winff and he got the following result. So I think it has to
do with the architecture. One remark (I don't know how to test this
without uploading a new version): I didn't include the ${misc:Depends}
in the Depends field because it didn't include any new dependencies on
my system. But maybe it needs that when building for powerpc... It would
be great if somebody with a ppc could build winff from source including
the ${misc:Depends} and confirm that the depends are different from the
original package.

Paul

u...@host: winff
TRasterImage.BitmapHandleNeeded: Unable to create handles, using default

(winff:3398): GLib-GObject-CRITICAL **: g_object_ref: assertion
`G_IS_OBJECT (object)' failed
TRasterImage.BitmapHandleNeeded: Unable to create handles, using default

(winff:3398): GLib-GObject-CRITICAL **: g_object_ref: assertion
`G_IS_OBJECT (object)' failed
TRasterImage.BitmapHandleNeeded: Unable to create handles, using default

(winff:3398): GLib-GObject-CRITICAL **: g_object_ref: assertion
`G_IS_OBJECT (object)' failed
TRasterImage.BitmapHandleNeeded: Unable to create handles, using default

(winff:3398): GLib-GObject-CRITICAL **: g_object_ref: assertion
`G_IS_OBJECT (object)' failed
TRasterImage.BitmapHandleNeeded: Unable to create handles, using default

(winff:3398): GLib-GObject-CRITICAL **: g_object_ref: assertion
`G_IS_OBJECT (object)' failed
TRasterImage.BitmapHandleNeeded: Unable to create handles, using default

(winff:3398): GLib-GObject-CRITICAL **: g_object_ref: assertion
`G_IS_OBJECT (object)' failed
[FORMS.PP] ExceptionOccurred
  Sender=EAccessViolation
  Exception=Access violation
  Stack trace:
  $BF92B114
  $0F8EB9EC
  $0F907020
  $0F9086EC
  $0F908C9C
  $0FD1FB50
  $0FB5EDC8
  $0F8FCB94
  $0F8E97D8
  $0F8EB9EC
  $0F906850
  $0F9086EC
  $0F908C9C
  $0FD1FB50
  $10270D8C
  $10270A24
  $1022C9C8
TApplication.HandleException Access violation
  Stack trace:
  $BF92B114
  $0F8EB9EC
  $0F907020
  $0F9086EC
  $0F908C9C
  $0FD1FB50
  $0FB5EDC8
  $0F8FCB94
  $0F8E97D8
  $0F8EB9EC
  $0F906850
  $0F9086EC
  $0F908C9C
  $0FD1FB50
  $10270D8C
  $10270A24
  $1022C9C8
[FORMS.PP] ExceptionOccurred
[FORMS.PP] ExceptionOccurred
[FORMS.PP] ExceptionOccurred



signature.asc
Description: OpenPGP digital signature

Bug#511505: winff does not run at all

2009-01-16 Thread Paul Gevers 
Thank you for supplying this bug report.

 I'll be happy to provide more info if needed.

I suspect I missed a dependency, but of course that is difficult testing
for me.

Could you run winff through strace? You may need to install strace
first. Than run strace -o winff.strace winff and attach the
winff.strace file to this bug report.

Thanks in advance.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#511505: winff does not run at all

2009-01-16 Thread Tomáš Šafařík 

Hello Paul,

I did the strace as you requested but I had to stop it with ctrl+c 
because it seemed to run forever. And I also bzipped it.


Hope it helps. If you need something more just let me know.

Tomas

Paul Gevers wrote:

Thank you for supplying this bug report.

  

I'll be happy to provide more info if needed.



I suspect I missed a dependency, but of course that is difficult testing
for me.

Could you run winff through strace? You may need to install strace
first. Than run strace -o winff.strace winff and attach the
winff.strace file to this bug report.

Thanks in advance.

Paul

  


winff.strace.bz2
Description: application/bzip

Bug#511505: winff does not run at all

2009-01-11 Thread Tomas Safarik 
Package: winff
Version: 0.45.1-1
Severity: important

Hi,

when I try to run winff it end with following error and it is not usable at all.

~$ winff
[WARNING] Out of OEM specific VK codes, changing to unassigned
[WARNING] Out of unassigned VK codes, assigning $FF
TRasterImage.BitmapHandleNeeded: Unable to create handles, using default

(winff:2774): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT 
(object)' failed
TRasterImage.BitmapHandleNeeded: Unable to create handles, using default

(winff:2774): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT 
(object)' failed
TRasterImage.BitmapHandleNeeded: Unable to create handles, using default

(winff:2774): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT 
(object)' failed
TRasterImage.BitmapHandleNeeded: Unable to create handles, using default

(winff:2774): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT 
(object)' failed
TRasterImage.BitmapHandleNeeded: Unable to create handles, using default

(winff:2774): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT 
(object)' failed
TRasterImage.BitmapHandleNeeded: Unable to create handles, using default

(winff:2774): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT 
(object)' failed
[FORMS.PP] ExceptionOccurred 
  Sender=EAccessViolation
  Exception=Access violation
  Stack trace:
  $BFB928C4
  $0F8D2C9C
  $0F8EF300
  $0F8F09A4
  $0F8F0F5C
  $0FCC90D0
  $0FB26B08
  $0F8E3E54
  $0F8D0A88
  $0F8D2C9C
  $0F8EEB30
  $0F8F09A4
  $0F8F0F5C
  $0FCC90D0
  $10270D8C
  $10270A24
  $1022C9C8
TApplication.HandleException Access violation
  Stack trace:
  $BFB928C4
  $0F8D2C9C
  $0F8EF300
  $0F8F09A4
  $0F8F0F5C
  $0FCC90D0
  $0FB26B08
  $0F8E3E54
  $0F8D0A88
  $0F8D2C9C
  $0F8EEB30
  $0F8F09A4
  $0F8F0F5C
  $0FCC90D0
  $10270D8C
  $10270A24
  $1022C9C8
Trace/breakpoint trap

I'll be happy to provide more info if needed.

Thank you

Tomas

-- System Information:
Debian Release: 5.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: powerpc (ppc)

Kernel: Linux 2.6.26-1-powerpc
Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages winff depends on:
ii  ffmpeg 3:0.svn20081115-1 multimedia player, server and enco
ii  gnome-terminal [x-term 2.24.2-1  The GNOME 2 terminal emulator appl
ii  libatk1.0-01.24.0-1  The ATK accessibility toolkit
ii  libc6  2.8+20080809-1GNU C Library: Shared libraries
ii  libglib2.0-0   2.18.3-1  The GLib library of C routines
ii  libgtk2.0-02.14.5-1  The GTK+ graphical user interface 
ii  libpango1.0-0  1.22.4-1  Layout and rendering of internatio
ii  libx11-6   2:1.1.99.2-1  X11 client-side library
ii  xterm [x-terminal-emul 238-2 X terminal emulator

winff recommends no packages.

winff suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org