Your message dated Sat, 29 Jul 2006 03:40:49 +0100
with message-id <[EMAIL PROTECTED]>
and subject line [Fwd: Re: Still a problem?]
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: ogle-mmx
Version: 0.9.2-2.2
Severity: important

Hi

I've recently upgraded to the latest version of Ogle (0.9.2-2.2) from a
previous Debian release (0.9.2-2) and have immediately started experiencing
a serious problem with shutting down the application after watching a DVD.
Using any GUI tool I have tried currently including Goggles, Okle and
Ogle-gui, closing the control GUI results in that single window
disappearing, but the DVD often continues to run in the background. If I
close the video window, the DVD still continues to play, as I can hear the
sound. In some cases, the DVD playing stops, but the running processes
remain active in memory. The only way to shut down the application fully is
to manually kill all remaining processes.

The only clue to what is happening is displayed upon closing the GUI window.
The following messages are displayed. 

X connection to :0.0 broken (explicit kill or server shutdown).
ctrl: waitpid failed: Invalid argument
ctrl: waitpid failed: Invalid argument

The following processes are left running after shutdown

/bin/sh /usr/bin/ogle
/usr/lib/ogle/ogle_ctrl
[ogle_gui] <defunct>
ogle_nav
ogle_mpeg_ps
[ogle_vout] <defunct>
ogle_mpeg_vs
ogle_audio

This problem does not occur under Ogle 0.9.2-2. Any idea what it might be? 

Regards, 

Barrie

-- System Information:
Debian Release: 3.0
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27-bm041127-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages ogle-mmx depends on:
ii  liba52-0.7.4              0.7.4-1        Library for decoding ATSC A/52 str
ii  libasound2                1.0.9-3        ALSA library
ii  libc6                     2.3.5-3        GNU C Library: Shared libraries an
ii  libdvdread3               0.9.4-3        Simple foundation for reading DVDs
ii  libice6                   6.8.2.dfsg.1-6 Inter-Client Exchange library
ii  libjpeg62                 6b-10          The Independent JPEG Group's JPEG 
ii  libmad0                   0.15.1b-1      MPEG audio decoder library
ii  libsm6                    6.8.2.dfsg.1-6 X Window System Session Management
ii  libx11-6                  6.8.2.dfsg.1-6 X Window System protocol client li
ii  libxext6                  6.8.2.dfsg.1-6 X Window System miscellaneous exte
ii  libxinerama1              6.8.2.dfsg.1-6 X Window System multi-head display
ii  libxml2                   2.6.22-1       GNOME XML library
ii  libxv1                    6.8.2.dfsg.1-6 X Window System video extension li
ii  libxxf86vm1               6.8.2.dfsg.1-6 X Video Mode selection library
ii  xlibs                     6.8.2.dfsg.1-6 X Window System client libraries m
ii  zlib1g                    1:1.2.3-4      compression library - runtime

-- no debconf information


--- End Message ---
--- Begin Message ---
Closing this bug.
Justification: Submitter says it no longer exists. If anyone has information to the contrary please reopen this bug and let me know.

Thanks,
Alan
--- Begin Message ---
Hi 

I've installed and tried the new unstable versions of the Ogle
packages and can confirm that this bug no longer appears to exist.

Thanks

Regards,

Barrie

On Tue, 25 Jul 2006 18:20:30 +0100
Alan Woodland <[EMAIL PROTECTED]> wrote:

> Hi, I'm the new Debian maintainer for Ogle. I'm currently trying to
sort 
> through some of the outstanding bug reports. With the current version
of 
> Ogle in unstable (0.9.2-4) I'm not seeing this behaviour. Can you 
> confirm for me if this is still a problem? If it is I'm going to need 
> some further information to fix it if at all possible.
> 
> Thanks,
> Alan

--- End Message ---

--- End Message ---

Reply via email to