GNOME.org
 

Gtkmm-forge Digest, Vol 30, Issue 2

Send Gtkmm-forge mailing list submissions to
	gtkmm-forge lists sourceforge net

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.sourceforge.net/lists/listinfo/gtkmm-forge
or, via email, send a message with subject or body 'help' to
	gtkmm-forge-request lists sourceforge net

You can reach the person managing the list at
	gtkmm-forge-owner lists sourceforge net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Gtkmm-forge digest..."


gtkmm-forge is the mailing list that receives gtkmm bug reports from bugzilla.  A daily digest is sent to gtkmm-main, to encourage people to help fixing the bugs. Do not try to unsubscribe gtkmm-forge from gtkmm-list.


Today's Topics:

   1. [Bug 559186] New: No LIBGTKMM_SO_VERSION update	since 2.12.7
      (gtkmm (bugzilla.gnome.org))
   2. [Bug 558873] G++ warning when -Wunused-parameter	is specified
      (gnomemm (bugzilla.gnome.org))
   3. [Bug 559176] Fixes for clutter 0.9 (gnomemm (bugzilla.gnome.org))
   4. [Bug 559209] New: Gst::Element::get_factory() -
      Gst::ElementFactory refcount problem (gnomemm (bugzilla.gnome.org))
   5. [Bug 556570] Version 0.9.7 fails to build due to	call to
      ``GstBase::wrap_init()'' in gstreamer/gstreamermm/init.cc
      (gnomemm (bugzilla.gnome.org))
   6. [Bug 556570] Version 0.9.7 fails to build due to	call to
      ``GstBase::wrap_init()'' in gstreamer/gstreamermm/init.cc
      (gnomemm (bugzilla.gnome.org))


----------------------------------------------------------------------

Message: 1
Date: Mon,  3 Nov 2008 21:21:21 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 559186] New: No LIBGTKMM_SO_VERSION
	update	since 2.12.7
To: gtkmm-forge lists sourceforge net
Message-ID: <bug-559186-5595 http bugzilla gnome org/>
Content-Type: text/plain; charset=utf-8

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=559186

  gtkmm | build | Ver: 2.14.x
           Summary: No LIBGTKMM_SO_VERSION update since 2.12.7
           Product: gtkmm
           Version: 2.14.x
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: build
        AssignedTo: gtkmm-forge lists sourceforge net
        ReportedBy: gilles dartiguelongue esiee org
         QAContact: gtkmm-forge lists sourceforge net
     GNOME version: 2.23/2.24
   GNOME milestone: Unspecified


Hi,

the summary says it all, since 2.12.7, the variable didn't change while the
NEWS talks about added functions, some functions now have some defaults for
their parameters. I believe these should reflect in this variable like glibmm
does.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=559186.



------------------------------

Message: 2
Date: Mon,  3 Nov 2008 23:01:31 +0000 (UTC)
From: "gnomemm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 558873] G++ warning when
	-Wunused-parameter	is specified
To: gtkmm-forge lists sourceforge net
Message-ID: <20081103230131 284C223F513 label gnome org>
Content-Type: text/plain; charset=utf-8

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=558873

  gnomemm | cluttermm | Ver: unspecified

Murray Cumming changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |murrayc murrayc com
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED




------- Comment #2 from Murray Cumming  2008-11-03 23:01 UTC -------
Committed. Thanks.

Please patch the ChangeLog in future.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=558873.



------------------------------

Message: 3
Date: Mon,  3 Nov 2008 23:08:48 +0000 (UTC)
From: "gnomemm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 559176] Fixes for clutter 0.9
To: gtkmm-forge lists sourceforge net
Message-ID: <20081103230848 B6E8923F510 label gnome org>
Content-Type: text/plain; charset=utf-8

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=559176

  gnomemm | cluttermm | Ver: unspecified

Murray Cumming changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |murrayc murrayc com
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED




------- Comment #3 from Murray Cumming  2008-11-03 23:08 UTC -------
Both patches committed. Thanks for doing this - I didn't even know that
clutter-0.9 existed yet.

Please patch the ChangeLog in future.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=559176.



------------------------------

Message: 4
Date: Tue,  4 Nov 2008 00:09:32 +0000 (UTC)
From: "gnomemm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 559209] New:
	Gst::Element::get_factory() -	Gst::ElementFactory refcount problem
To: gtkmm-forge lists sourceforge net
Message-ID: <bug-559209-5595 http bugzilla gnome org/>
Content-Type: text/plain; charset=utf-8

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=559209

  gnomemm | gstreamermm | Ver: unspecified
           Summary: Gst::Element::get_factory() - Gst::ElementFactory
                    refcount problem
           Product: gnomemm
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gstreamermm
        AssignedTo: gtkmm-forge lists sourceforge net
        ReportedBy: richardf acres com au
         QAContact: gtkmm-forge lists sourceforge net
     GNOME version: 2.23/2.24
   GNOME milestone: Unspecified


Please describe the problem:
Gst::Element::get_factory() appears to currently be coded under the assumption
that callers of gst_element_get_factory() must unref the returned
GstElementFactory* when they are done with it. 

However, this is not the case (according to the gstreamer
gst_element_get_factory() doco: "no refcounting is needed").

As a result, calling Gst::Element::get_factory() twice on the same element
causes the element's factory to be prematurely and incorrectly disposed.

Seen in gstreamermm 0.9.7 (and earlier).


Steps to reproduce:
Glib::RefPtr<Gst::Element> element =
Gst::ElementFactory::create_element("fakesrc");
{
  std::cout << "Getting factory";
  Glib::RefPtr<Gst::ElementFactory> factory = element->get_factory();
  std::cout << "Factory name: " << factory->get_name();
}
std::cout << "Factory out of scope";
{
  std::cout << "Getting factory again";
  Glib::RefPtr<Gst::ElementFactory> factory = element->get_factory();
  std::cout << "Factory name: " << factory->get_name();
}
std::cout << "Factory out of scope again";



Actual results:
Run with Debug logging enabled, and you should see the element's factory
incorrectly get disposed before the last out of scope message.

Not surprisingly, any subsequent calls to get_factory() on the element,
incorrectly return NULL;


Expected results:
The factory not to get incorrectly/prematurely disposed.

Does this happen every time?
Yes.

Other information:
I tried the a workaround that passes "true" as the take_copy parameter to
Glib::wrap(GstElementFactory*, bool) in Gst::Element::get_factory(), but for
some reason I'm not sure about, the refcount on the factory, after all the
RefPtr's to it were destructed, ends up being set to 2, rather than 1 like I
would expect (in the logging it shows that the first get_factory() call causes
2 refs to take place rather than just 1 - something to do with floating
references??).

I'm not sure what the correct solution is: Does there need to be a similar
approach to wrapping in get_factory() that is used for the get_structure() call
in Gst::Message? Or, something similar to the get_source() call in
Gst::Message??


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=559209.



------------------------------

Message: 5
Date: Tue,  4 Nov 2008 08:57:11 +0000 (UTC)
From: "gnomemm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 556570] Version 0.9.7 fails to build
	due to	call to ``GstBase::wrap_init()'' in
	gstreamer/gstreamermm/init.cc
To: gtkmm-forge lists sourceforge net
Message-ID: <20081104085711 3D4E223F50D label gnome org>
Content-Type: text/plain; charset=utf-8

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=556570

  gnomemm | gstreamermm | Ver: unspecified




------- Comment #9 from Murray Cumming  2008-11-04 08:57 UTC -------
So, Jos?, is this a WONTFIX? Or is there something we should want to do?


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=556570.



------------------------------

Message: 6
Date: Tue,  4 Nov 2008 18:33:47 +0000 (UTC)
From: "gnomemm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 556570] Version 0.9.7 fails to build
	due to	call to ``GstBase::wrap_init()'' in
	gstreamer/gstreamermm/init.cc
To: gtkmm-forge lists sourceforge net
Message-ID: <20081104183347 9C58523F510 label gnome org>
Content-Type: text/plain; charset=utf-8

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=556570

  gnomemm | gstreamermm | Ver: unspecified




------- Comment #10 from Jos? Alburquerque  2008-11-04 18:33 UTC -------
I'm thinking it is a WONTFIX unless we decide to merge the gstreamerbasemm
branch into the gstreamermm branch.  The gstreamermm and the gstreamerbasemm
branches exist because they are a reflection of the core and the
gst-plugins-base modules of GStreamer, but if it is convenient they can be
merged in gstreamermm.  I can't modify the status of this bug, but if I had to
decide, I'd close it as a WONTFIX and suggest that it be re-opened in the
future if something else arises.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=556570.



------------------------------

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

------------------------------

_______________________________________________
Gtkmm-forge mailing list
Gtkmm-forge lists sourceforge net
https://lists.sourceforge.net/lists/listinfo/gtkmm-forge


End of Gtkmm-forge Digest, Vol 30, Issue 2
******************************************
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]