From: Mark W. <mar...@nt...> - 2010-08-05 21:54:52
Attachments:
ROXBug
|
Not sure what it is, but it seems to affect ROX-Filer windows |
From: Tony H. <h...@re...> - 2010-08-06 13:04:09
|
On Thu, 05 Aug 2010 22:54:28 +0100 Mark Williams <mar...@nt...> wrote: > Not sure what it is, but it seems to affect ROX-Filer windows No, it's an old bug, affecting DevTray and TaskTray. You need to upgrade libwnck. |
From: Mark W. <mar...@nt...> - 2010-08-06 13:48:12
|
Tony Houghton wrote: > On Thu, 05 Aug 2010 22:54:28 +0100 > Mark Williams<mar...@nt...> wrote: > >> Not sure what it is, but it seems to affect ROX-Filer windows > > No, it's an old bug, affecting DevTray and TaskTray. You need to upgrade > libwnck. > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev I did. I even applied your patch. |
From: Abrolag <ab...@us...> - 2010-08-06 17:57:31
|
On Fri, 06 Aug 2010 14:47:40 +0100 Mark Williams <mar...@nt...> wrote: > Tony Houghton wrote: > > On Thu, 05 Aug 2010 22:54:28 +0100 > > Mark Williams<mar...@nt...> wrote: > > > >> Not sure what it is, but it seems to affect ROX-Filer windows > > > > No, it's an old bug, affecting DevTray and TaskTray. You need to upgrade > > libwnck. > > > > ------------------------------------------------------------------------------ > > This SF.net email is sponsored by > > > > Make an app they can't live without > > Enter the BlackBerry Developer Challenge > > http://p.sf.net/sfu/RIM-dev2dev > > I did. I even applied your patch. There is indeed something screwy about this. I've found that trying to update old versions of debian squeeze to the current state doesn't work, but a fresh install does :? -- Will J Godfrey http://www.musically.me.uk Say you have a poem and I have a tune. Exchange them and we can both have a poem, a tune, and a song. |
From: Mark W. <mar...@nt...> - 2010-08-06 18:22:20
|
Abrolag wrote: > On Fri, 06 Aug 2010 14:47:40 +0100 > Mark Williams<mar...@nt...> wrote: > >> Tony Houghton wrote: >>> On Thu, 05 Aug 2010 22:54:28 +0100 >>> Mark Williams<mar...@nt...> wrote: >>> >>>> Not sure what it is, but it seems to affect ROX-Filer windows >>> >>> No, it's an old bug, affecting DevTray and TaskTray. You need to upgrade >>> libwnck. >>> >>> ------------------------------------------------------------------------------ >>> This SF.net email is sponsored by >>> >>> Make an app they can't live without >>> Enter the BlackBerry Developer Challenge >>> http://p.sf.net/sfu/RIM-dev2dev >> >> I did. I even applied your patch. > > There is indeed something screwy about this. > I've found that trying to update old versions of debian squeeze > to the current state doesn't work, but a fresh install does :? > It's like they liked the old bug so much they decided to keep it. When you say "fresh install" what do you mean? |
From: Abrolag <ab...@us...> - 2010-08-06 18:57:46
|
On Fri, 06 Aug 2010 19:21:53 +0100 Mark Williams <mar...@nt...> wrote: > Abrolag wrote: > > On Fri, 06 Aug 2010 14:47:40 +0100 > > Mark Williams<mar...@nt...> wrote: > > > >> Tony Houghton wrote: > >>> On Thu, 05 Aug 2010 22:54:28 +0100 > >>> Mark Williams<mar...@nt...> wrote: > >>> > >>>> Not sure what it is, but it seems to affect ROX-Filer windows > >>> > >>> No, it's an old bug, affecting DevTray and TaskTray. You need to upgrade > >>> libwnck. > >>> > >>> ------------------------------------------------------------------------------ > >>> This SF.net email is sponsored by > >>> > >>> Make an app they can't live without > >>> Enter the BlackBerry Developer Challenge > >>> http://p.sf.net/sfu/RIM-dev2dev > >> > >> I did. I even applied your patch. > > > > There is indeed something screwy about this. > > I've found that trying to update old versions of debian squeeze > > to the current state doesn't work, but a fresh install does :? > > > It's like they liked the old bug so much they decided to keep it. > > When you say "fresh install" what do you mean? A new debian 'net' install on a blank partition of the same machine. -- Will J Godfrey http://www.musically.me.uk Say you have a poem and I have a tune. Exchange them and we can both have a poem, a tune, and a song. |
From: Mark W. <mar...@nt...> - 2010-08-06 19:37:44
|
Abrolag wrote: > On Fri, 06 Aug 2010 19:21:53 +0100 > Mark Williams<mar...@nt...> wrote: > >> Abrolag wrote: >>> On Fri, 06 Aug 2010 14:47:40 +0100 >>> Mark Williams<mar...@nt...> wrote: >>> >>>> Tony Houghton wrote: >>>>> On Thu, 05 Aug 2010 22:54:28 +0100 >>>>> Mark Williams<mar...@nt...> wrote: >>>>> >>>>>> Not sure what it is, but it seems to affect ROX-Filer windows >>>>> >>>>> No, it's an old bug, affecting DevTray and TaskTray. You need to upgrade >>>>> libwnck. >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> This SF.net email is sponsored by >>>>> >>>>> Make an app they can't live without >>>>> Enter the BlackBerry Developer Challenge >>>>> http://p.sf.net/sfu/RIM-dev2dev >>>> >>>> I did. I even applied your patch. >>> >>> There is indeed something screwy about this. >>> I've found that trying to update old versions of debian squeeze >>> to the current state doesn't work, but a fresh install does :? >>> >> It's like they liked the old bug so much they decided to keep it. >> >> When you say "fresh install" what do you mean? > > > A new debian 'net' install on a blank partition of the same machine. > I was afraid you were going to say that :-( |
From: Mark W. <mar...@nt...> - 2010-08-20 21:57:36
|
Update. I reinstalled Ubuntu and it's still happening with tasktray (this window demands attention). I suspect the app itself needs some attention. Mark Williams wrote: > Abrolag wrote: >> On Fri, 06 Aug 2010 19:21:53 +0100 >> Mark Williams<mar...@nt...> wrote: >> >>> Abrolag wrote: >>>> On Fri, 06 Aug 2010 14:47:40 +0100 >>>> Mark Williams<mar...@nt...> wrote: >>>> >>>>> Tony Houghton wrote: >>>>>> On Thu, 05 Aug 2010 22:54:28 +0100 >>>>>> Mark Williams<mar...@nt...> wrote: >>>>>> >>>>>>> Not sure what it is, but it seems to affect ROX-Filer windows >>>>>> >>>>>> No, it's an old bug, affecting DevTray and TaskTray. You need to upgrade >>>>>> libwnck. >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> This SF.net email is sponsored by >>>>>> >>>>>> Make an app they can't live without >>>>>> Enter the BlackBerry Developer Challenge >>>>>> http://p.sf.net/sfu/RIM-dev2dev >>>>> >>>>> I did. I even applied your patch. >>>> >>>> There is indeed something screwy about this. >>>> I've found that trying to update old versions of debian squeeze >>>> to the current state doesn't work, but a fresh install does :? >>>> >>> It's like they liked the old bug so much they decided to keep it. >>> >>> When you say "fresh install" what do you mean? >> >> >> A new debian 'net' install on a blank partition of the same machine. >> > I was afraid you were going to say that :-( > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev |
From: Mark W. <mar...@nt...> - 2010-08-21 09:09:16
|
Here's what I got attempting to compile libwnck with the patch in debian/patches make[1]: Leaving directory `/home/mark/libwnck-2.30.0' if [ "debian/stamp-patched" = "reverse-patches" ]; then rm -f debian/stamp-patched; fi patches: debian/patches/01_glib_mkenums.patch debian/patches/99_ltmain_as-needed.patch debian/patches/python-wnck-fix-enums.patch Trying patch debian/patches/01_glib_mkenums.patch at level 1 ... success. Trying patch debian/patches/99_ltmain_as-needed.patch at level 1 ... 0 ... success. Trying patch debian/patches/python-wnck-fix-enums.patch at level 1 ... 0 ... 2 ... failure. make: *** [debian/stamp-patched] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 debuild: fatal error at line 1340: dpkg-buildpackage -rfakeroot -D -us -uc failed Mark Williams wrote: > Update. I reinstalled Ubuntu and it's still happening with tasktray > (this window demands attention). > > I suspect the app itself needs some attention. > > > Mark Williams wrote: >> Abrolag wrote: >>> On Fri, 06 Aug 2010 19:21:53 +0100 >>> Mark Williams<mar...@nt...> wrote: >>> >>>> Abrolag wrote: >>>>> On Fri, 06 Aug 2010 14:47:40 +0100 >>>>> Mark Williams<mar...@nt...> wrote: >>>>> >>>>>> Tony Houghton wrote: >>>>>>> On Thu, 05 Aug 2010 22:54:28 +0100 >>>>>>> Mark Williams<mar...@nt...> wrote: >>>>>>> >>>>>>>> Not sure what it is, but it seems to affect ROX-Filer windows >>>>>>> >>>>>>> No, it's an old bug, affecting DevTray and TaskTray. You need to upgrade >>>>>>> libwnck. >>>>>>> >>>>>>> ------------------------------------------------------------------------------ >>>>>>> This SF.net email is sponsored by >>>>>>> >>>>>>> Make an app they can't live without >>>>>>> Enter the BlackBerry Developer Challenge >>>>>>> http://p.sf.net/sfu/RIM-dev2dev >>>>>> >>>>>> I did. I even applied your patch. >>>>> >>>>> There is indeed something screwy about this. >>>>> I've found that trying to update old versions of debian squeeze >>>>> to the current state doesn't work, but a fresh install does :? >>>>> >>>> It's like they liked the old bug so much they decided to keep it. >>>> >>>> When you say "fresh install" what do you mean? >>> >>> >>> A new debian 'net' install on a blank partition of the same machine. >>> >> I was afraid you were going to say that :-( >> >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by >> >> Make an app they can't live without >> Enter the BlackBerry Developer Challenge >> http://p.sf.net/sfu/RIM-dev2dev > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev |
From: Abrolag <ab...@us...> - 2010-08-21 09:46:32
|
On Fri, 20 Aug 2010 22:57:06 +0100 Mark Williams <mar...@nt...> wrote: > Update. I reinstalled Ubuntu and it's still happening with tasktray > (this window demands attention). > > I suspect the app itself needs some attention. Which version of ubuntu? I find a completely new install of debian squeeze solves the problem. -- Will J Godfrey http://www.musically.me.uk Say you have a poem and I have a tune. Exchange them and we can both have a poem, a tune, and a song. |
From: Mark W. <mar...@nt...> - 2010-08-21 09:59:57
|
Abrolag wrote: > On Fri, 20 Aug 2010 22:57:06 +0100 > Mark Williams<mar...@nt...> wrote: > >> Update. I reinstalled Ubuntu and it's still happening with tasktray >> (this window demands attention). >> >> I suspect the app itself needs some attention. > > Which version of ubuntu? > > I find a completely new install of debian squeeze solves the problem. > 10.04. And I did do a reinstall of the OS but I left my home partition as it was. |
From: Mark W. <mar...@nt...> - 2010-09-07 15:28:10
|
Abrolag wrote: > On Sat, 21 Aug 2010 10:59:35 +0100 > Mark Williams<mar...@nt...> wrote: > >> Abrolag wrote: >>> On Fri, 20 Aug 2010 22:57:06 +0100 >>> Mark Williams<mar...@nt...> wrote: >>> >>>> Update. I reinstalled Ubuntu and it's still happening with tasktray >>>> (this window demands attention). >>>> >>>> I suspect the app itself needs some attention. >>> >>> Which version of ubuntu? >>> >>> I find a completely new install of debian squeeze solves the problem. >>> >> 10.04. And I did do a reinstall of the OS but I left my home partition >> as it was. > > Very strange. Are you using the version of ROX in the ubuntu repository > or installing from scratch? I find there is something slightly odd about > the debian version and only tend to use it on a new install to help me > set everything else up. I then replace it with the latest version > compiled on that machine. > > I may be doing a fresh install on another machine soon, if so, I'll see > if that behaves any differently. > I'm using a new version that Tom linked me to. It's probably some new bug in libwnck that the previous patch doesn't address. |
From: Mark W. <mar...@nt...> - 2010-09-18 21:22:19
|
It's definitely python-wnck. Tasklist depends on lib-wnck and that runs fine. Tasktray depends on python-wnck and that generates the windows state error message. |
From: Tony H. <h...@re...> - 2010-09-18 23:43:31
|
On Sat, 18 Sep 2010 22:21:54 +0100 Mark Williams <mar...@nt...> wrote: > It's definitely python-wnck. Tasklist depends on lib-wnck and that runs > fine. Tasktray depends on python-wnck and that generates the windows > state error message. The problem was that the GObject type used for some constants didn't match the type the python bindings thought they should be. The bug was in libwnck, not in python-wnck, because the python bindings were right about what the type should be and libwnck had it wrong, but to C programs it didn't matter which type was used. If you patched python-wnck and started using a newer, fixed libwnck, that would create the problem in reverse but with identical symptoms. I think libwnck 2.30.0 was the release that fixed it, so if you're using that or newer make sure your python bindings are up to date and *not* patched. -- TH * http://www.realh.co.uk |
From: Mark W. <mar...@nt...> - 2010-09-19 05:53:06
|
Tony Houghton wrote: > On Sat, 18 Sep 2010 22:21:54 +0100 > Mark Williams<mar...@nt...> wrote: > >> It's definitely python-wnck. Tasklist depends on lib-wnck and that runs >> fine. Tasktray depends on python-wnck and that generates the windows >> state error message. > > The problem was that the GObject type used for some constants didn't > match the type the python bindings thought they should be. The bug was > in libwnck, not in python-wnck, because the python bindings were right > about what the type should be and libwnck had it wrong, but to C > programs it didn't matter which type was used. > > If you patched python-wnck and started using a newer, fixed libwnck, > that would create the problem in reverse but with identical symptoms. I > think libwnck 2.30.0 was the release that fixed it, so if you're using > that or newer make sure your python bindings are up to date and *not* > patched. > It doesn't matter what I do the bug remains. I've tried everything from getting rid of all instances of libwnck and then reinstalling it from the Synaptic to reinstalling the entire OS. But still that bug pops up. I really have no idea what could be causing it. It's very frustrating. |
From: Mark W. <mar...@nt...> - 2010-10-25 22:01:44
|
Abrolag wrote: > On Sun, 19 Sep 2010 00:23:10 +0100 > Tony Houghton<h...@re...> wrote: > >> On Sat, 18 Sep 2010 22:21:54 +0100 >> Mark Williams<mar...@nt...> wrote: >> >>> It's definitely python-wnck. Tasklist depends on lib-wnck and that runs >>> fine. Tasktray depends on python-wnck and that generates the windows >>> state error message. >> >> The problem was that the GObject type used for some constants didn't >> match the type the python bindings thought they should be. The bug was >> in libwnck, not in python-wnck, because the python bindings were right >> about what the type should be and libwnck had it wrong, but to C >> programs it didn't matter which type was used. >> >> If you patched python-wnck and started using a newer, fixed libwnck, >> that would create the problem in reverse but with identical symptoms. I >> think libwnck 2.30.0 was the release that fixed it, so if you're using >> that or newer make sure your python bindings are up to date and *not* >> patched. > > This problem seems to be finally cured with the latest updates for debian > squeeze. > Sadly, for me, I'm using Ubuntu. I don't think that's based on Squeeze. |
From: Liam P. <lp...@gm...> - 2010-10-25 23:52:52
|
On Mon, Oct 25, 2010 at 11:01 PM, Mark Williams <mar...@nt...> wrote: >> > Sadly, for me, I'm using Ubuntu. > > I don't think that's based on Squeeze. Oh, don't be too sad. I've been running Ubuntu since the first ever version, 4.10, and every couple of years, emboldened, I try again to install Debian. Last time was last week. I got it working fine but with no sound and an 800*600 screen on a 1024*768 laptop. I then updated to "testing" and broke it utterly. /Still/ not man enough, clearly. :¬) So, [a] I think you're better off with Ubuntu, and [b] as Squeeze isn't out yet, we're talking "testing" or "unstable". What version of Ubuntu are you running? If you're on 10.10 or 10.04, you are effectively on Squeeze, yes. As Wikipedia says: Debian 5.0 (lenny) was released February 14, 2009 ... meaning that Ubuntu 9.10 and onwards will be based off sources recent enough to be described as "Squeeze". This is not particularly useful information, but I thought it might be a comfort. -- Liam Proven • Info & profile: http://www.google.com/profiles/lproven Email: lp...@ci... • GMail/GoogleTalk/Orkut: lp...@gm... Tel: +44 20-8685-0498 • Cell: +44 7939-087884 • Fax: + 44 870-9151419 AIM/Yahoo/Skype: liamproven • MSN: lp...@ho... • ICQ: 73187508 |
From: Abrolag <ab...@us...> - 2010-08-24 11:09:27
|
On Sat, 21 Aug 2010 10:59:35 +0100 Mark Williams <mar...@nt...> wrote: > Abrolag wrote: > > On Fri, 20 Aug 2010 22:57:06 +0100 > > Mark Williams<mar...@nt...> wrote: > > > >> Update. I reinstalled Ubuntu and it's still happening with tasktray > >> (this window demands attention). > >> > >> I suspect the app itself needs some attention. > > > > Which version of ubuntu? > > > > I find a completely new install of debian squeeze solves the problem. > > > 10.04. And I did do a reinstall of the OS but I left my home partition > as it was. Very strange. Are you using the version of ROX in the ubuntu repository or installing from scratch? I find there is something slightly odd about the debian version and only tend to use it on a new install to help me set everything else up. I then replace it with the latest version compiled on that machine. I may be doing a fresh install on another machine soon, if so, I'll see if that behaves any differently. -- Will J Godfrey http://www.musically.me.uk Say you have a poem and I have a tune. Exchange them and we can both have a poem, a tune, and a song. |
From: Tony H. <h...@re...> - 2010-09-19 12:53:58
|
On Sun, 19 Sep 2010 06:52:42 +0100 Mark Williams <mar...@nt...> wrote: > It doesn't matter what I do the bug remains. I've tried everything from > getting rid of all instances of libwnck and then reinstalling it from > the Synaptic to reinstalling the entire OS. But still that bug pops up. What version are you using now? > I really have no idea what could be causing it. It's very frustrating. Could it be using an outdated 0install version instead of the OS version? -- TH * http://www.realh.co.uk |
From: Mark W. <mar...@nt...> - 2010-09-19 15:51:58
|
Tony Houghton wrote: > On Sun, 19 Sep 2010 06:52:42 +0100 > Mark Williams<mar...@nt...> wrote: > >> It doesn't matter what I do the bug remains. I've tried everything from >> getting rid of all instances of libwnck and then reinstalling it from >> the Synaptic to reinstalling the entire OS. But still that bug pops up. > > What version are you using now? > >> I really have no idea what could be causing it. It's very frustrating. > > Could it be using an outdated 0install version instead of the OS > version? > Well I did download the most recent version of tasktray from berlios.de (not the 0install one). So I can't see why it'd be using the 0install version of libwnck. But you never know. |
From: Tony H. <h...@re...> - 2010-09-19 17:39:31
|
On Sun, 19 Sep 2010 00:23:10 +0100 Tony Houghton <h...@re...> wrote: > If you patched python-wnck and started using a newer, fixed libwnck, > that would create the problem in reverse but with identical symptoms. It looks like that's exactly what happened, but it was the gnome-python people that did it, affecting everybody. I've filed new bug reports, <https://bugs.launchpad.net/debian/+source/gnome-python-desktop/+bug/642913> is the one for Ubuntu and has links to the GNOME and Debian bugs. I've also added a fixed version for Lucid to my PPA at <https://launchpad.net/~h-realh/+archive/ppa>. -- TH * http://www.realh.co.uk |
From: Mark W. <mar...@nt...> - 2010-09-19 17:44:08
|
Tony Houghton wrote: > On Sun, 19 Sep 2010 00:23:10 +0100 > Tony Houghton<h...@re...> wrote: > >> If you patched python-wnck and started using a newer, fixed libwnck, >> that would create the problem in reverse but with identical symptoms. > > It looks like that's exactly what happened, but it was the > gnome-python people that did it, affecting everybody. I've filed new bug > reports, > <https://bugs.launchpad.net/debian/+source/gnome-python-desktop/+bug/642913> > is the one for Ubuntu and has links to the GNOME and Debian bugs. > > I've also added a fixed version for Lucid to my PPA at > <https://launchpad.net/~h-realh/+archive/ppa>. > I don't flipping believe it. What a bunch of maroons. Sometimes I really think Linux development needs to be more tightly controlled. |
From: Abrolag <ab...@us...> - 2010-10-25 21:28:47
|
On Sun, 19 Sep 2010 00:23:10 +0100 Tony Houghton <h...@re...> wrote: > On Sat, 18 Sep 2010 22:21:54 +0100 > Mark Williams <mar...@nt...> wrote: > > > It's definitely python-wnck. Tasklist depends on lib-wnck and that runs > > fine. Tasktray depends on python-wnck and that generates the windows > > state error message. > > The problem was that the GObject type used for some constants didn't > match the type the python bindings thought they should be. The bug was > in libwnck, not in python-wnck, because the python bindings were right > about what the type should be and libwnck had it wrong, but to C > programs it didn't matter which type was used. > > If you patched python-wnck and started using a newer, fixed libwnck, > that would create the problem in reverse but with identical symptoms. I > think libwnck 2.30.0 was the release that fixed it, so if you're using > that or newer make sure your python bindings are up to date and *not* > patched. This problem seems to be finally cured with the latest updates for debian squeeze. -- Will J Godfrey http://www.musically.me.uk Say you have a poem and I have a tune. Exchange them and we can both have a poem, a tune, and a song. |