[openbox] Hi Future Of Obconf -Warning & Critical?

Das dasfox at gmail.com
Thu Jul 18 21:39:23 EDT 2013 

As I mentioned before, since I don't use a Display Manager to log into
Openbox, just 'startx', when I log out of Openbox back to the console the
messages are still appering in the console, so this isn't working;
<command>sh -c "obconf > /dev/null"</command>

hmmm



On Thu, Jul 18, 2013 at 3:33 PM, Dana Jansens <dana at orodu.net> wrote:

> I think you are looking for <command>sh -c "obconf >
> /dev/null"</command>
>
>
> On Thu, Jul 18, 2013 at 6:29 PM, Das <dasfox at gmail.com> wrote:
>
>> In the menu.xml it's
>> <command></command>
>>
>> So I tried it and it's still not working;
>>
>> <command>obconf &gt /dev/null 2&gt&amp1</command>
>>
>> Openbox gives me a popup for syntax error...
>>
>>
>> Thanks
>>
>>
>>
>> On Thu, Jul 18, 2013 at 3:25 PM, Jamie Macdonald <jamie.alban at gmail.com>wrote:
>>
>>> the entry for:
>>> obconf > /dev/null 2>&1
>>> would be:
>>> <execute>
>>>     obconf &gt /dev/null 2&gt&amp1
>>> </execute>
>>>
>>> because clearly, the angled brackets and ampersands serve a special
>>> purpose in xml.
>>>
>>> I suggest using the obmenu gui if you want to enter commands verbatim,
>>> and have the xml autogenerated.
>>>
>>>
>>> On Thu, Jul 18, 2013 at 9:16 PM, Das <dasfox at gmail.com> wrote:
>>>
>>>> I'm looking at this and I see this;
>>>>
>>>> > > >
>>>> So I'm trying it, but not getting anywhere with it... :(
>>>>
>>>> Someone please show how to make this?
>>>>
>>>> THANKS
>>>>
>>>>
>>>>
>>>> On Thu, Jul 18, 2013 at 3:11 PM, Das <dasfox at gmail.com> wrote:
>>>>
>>>>> Thanks Dana, but I suck at coding, haven't a clue as how to make this?
>>>>>
>>>>> Hmm
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Jul 18, 2013 at 3:01 PM, Dana Jansens <dana at orodu.net> wrote:
>>>>>
>>>>>> On Thu, Jul 18, 2013 at 5:58 PM, Das <dasfox at gmail.com> wrote:
>>>>>>
>>>>>>> In the mean time since I know these aren't hurting anything, how can
>>>>>>> we make running from a terminal; obconf > /dev/null 2>&1 work in the
>>>>>>> menu.xml  <command> </command>?
>>>>>>>
>>>>>>> Thanks...
>>>>>>
>>>>>>
>>>>>> http://google.com?q=xml+escape+codes
>>>>>>
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Jul 18, 2013 at 2:41 PM, Anthony Thyssen <
>>>>>>> A.Thyssen at griffith.edu.au> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> Pretty much every GTK application I have see generates mega-loads of
>>>>>>>> these type of warnings. I think it is mostly because no machine is
>>>>>>>> ever
>>>>>>>> quite the same as the developers machine.
>>>>>>>>
>>>>>>>> It is actually rather annoying to have to wade through this garbage
>>>>>>>> when trying to track down a REAL problem. Just because most users
>>>>>>>> never
>>>>>>>> need to took at X window session error logs does not mean it is
>>>>>>>> okay to
>>>>>>>> flood it with junk.  It is a sign of a bad programmer, somewhere
>>>>>>>> along
>>>>>>>> the dependency chain.
>>>>>>>>
>>>>>>>> Better to get them fixed, or (globally turn them off) when no longer
>>>>>>>> debugging the GTK side of an application.
>>>>>>>>
>>>>>>>>
>>>>>>>>   Anthony Thyssen ( System Programmer )    <
>>>>>>>> A.Thyssen at griffith.edu.au>
>>>>>>>>
>>>>>>>>  --------------------------------------------------------------------------
>>>>>>>>    If you can get into Orbit, you're half way to anywhere!
>>>>>>>>                                                -- Robert Heinlein
>>>>>>>>
>>>>>>>>  --------------------------------------------------------------------------
>>>>>>>>    Anthony's Castle     http://www.ict.griffith.edu.au/anthony/
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, 18 Jul 2013 15:18:23 -0700
>>>>>>>> Dana Jansens <dana at orodu.net> wrote:
>>>>>>>> | These warnings have been present in ObConf forever. Patches are
>>>>>>>> welcome,
>>>>>>>> | but it may not be worth the effort, as it works fine anyways.
>>>>>>>> |
>>>>>>>> |
>>>>>>>> | On Thu, Jul 18, 2013 at 3:16 PM, Das <dasfox at gmail.com> wrote:
>>>>>>>> |
>>>>>>>> | > Hi Guys,
>>>>>>>> | >
>>>>>>>> | > How's the future looking for obconf going final with a version
>>>>>>>> release
>>>>>>>> | > soon?
>>>>>>>> | >
>>>>>>>> | > So far I believe I'm using the latest from git, but the last
>>>>>>>> time I
>>>>>>>> | > checked there hasn't been any activity on obconf for quite some
>>>>>>>> time...
>>>>>>>> | >
>>>>>>>> | > When I run it from a terminal it gets flooded with quite a lot
>>>>>>>> of output
>>>>>>>> | > about libglade;
>>>>>>>> | >
>>>>>>>> | >
>>>>>>>> | > (obconf:2174): libglade-WARNING **: unknown attribute `swapped'
>>>>>>>> for
>>>>>>>> | > <signal>.
>>>>>>>> | >
>>>>>>>> | >
>>>>>>>> | > Also I'm getting these GdkPixbuf messages below;
>>>>>>>> | >
>>>>>>>> | >
>>>>>>>> | > (obconf:2174): GdkPixbuf-CRITICAL **: gdk_pixbuf_new: assertion
>>>>>>>> `height >
>>>>>>>> | > 0' failed
>>>>>>>> | >
>>>>>>>> | > (obconf:2174): GdkPixbuf-CRITICAL **: gdk_pixbuf_fill: assertion
>>>>>>>> | > `GDK_IS_PIXBUF (pixbuf)' failed
>>>>>>>> | >
>>>>>>>> | > (obconf:2174): GdkPixbuf-CRITICAL **: gdk_pixbuf_copy_area:
>>>>>>>> assertion
>>>>>>>> | > `src_pixbuf != NULL' failed
>>>>>>>> | >
>>>>>>>> | > (obconf:2174): GdkPixbuf-CRITICAL **: gdk_pixbuf_new: assertion
>>>>>>>> `height >
>>>>>>>> | > 0' failed
>>>>>>>> | >
>>>>>>>> | > (obconf:2174): GdkPixbuf-CRITICAL **: gdk_pixbuf_fill: assertion
>>>>>>>> | > `GDK_IS_PIXBUF (pixbuf)' failed
>>>>>>>> | >
>>>>>>>> | > (obconf:2174): GdkPixbuf-CRITICAL **: gdk_pixbuf_copy_area:
>>>>>>>> assertion
>>>>>>>> | > `src_pixbuf != NULL' failed
>>>>>>>> | >
>>>>>>>> | > I'm a Slack Geek and I only run Openbox and when it comes to
>>>>>>>> pretty much
>>>>>>>> | > most apps and the kernel I roll my own as they say, so I love
>>>>>>>> to see no
>>>>>>>> | > messages, warnings etc, I guess I'm just a neat freak, like it
>>>>>>>> squeaky
>>>>>>>> | > clean, LOL...
>>>>>>>> | >
>>>>>>>> | > So anyway to get these cleaned up in the code PLEASE?
>>>>>>>> | >
>>>>>>>> | > I'm running Slackware64 14 and these are the versions I'm using;
>>>>>>>> | >
>>>>>>>> | > gdk-pixbuf2-2.26
>>>>>>>> | > libglade-2.6.4
>>>>>>>> | > ObConf 2.0.4
>>>>>>>> | >
>>>>>>>> | > THANKS
>>>>>>>> | >
>>>>>>>> | > _______________________________________________
>>>>>>>> | > openbox mailing list
>>>>>>>> | > openbox at icculus.org
>>>>>>>> | > http://icculus.org/mailman/listinfo/openbox
>>>>>>>> | >
>>>>>>>> | >
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> openbox mailing list
>>>>>>>> openbox at icculus.org
>>>>>>>> http://icculus.org/mailman/listinfo/openbox
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> openbox mailing list
>>>>>>> openbox at icculus.org
>>>>>>> http://icculus.org/mailman/listinfo/openbox
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> openbox mailing list
>>>>>> openbox at icculus.org
>>>>>> http://icculus.org/mailman/listinfo/openbox
>>>>>>
>>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> openbox mailing list
>>>> openbox at icculus.org
>>>> http://icculus.org/mailman/listinfo/openbox
>>>>
>>>>
>>>
>>> _______________________________________________
>>> openbox mailing list
>>> openbox at icculus.org
>>> http://icculus.org/mailman/listinfo/openbox
>>>
>>>
>>
>> _______________________________________________
>> openbox mailing list
>> openbox at icculus.org
>> http://icculus.org/mailman/listinfo/openbox
>>
>>
>
> _______________________________________________
> openbox mailing list
> openbox at icculus.org
> http://icculus.org/mailman/listinfo/openbox
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://icculus.org/pipermail/openbox/attachments/20130718/69788bd5/attachment-0001.html>

More information about the openbox mailing list