Jonathan, you strongly suspected, you never knew and you still don't
know. The arguments you gave are valid and decrease the likelihood of a
QT bug, but not to 0.
While it probably was nobody's intent to completely close this ticket,
essentially that's what was rapidly happening yesterday morning
Fully closing this bug was not my nor anyone else's goal. My goal was
only to close the extraneous tasks against packages that I knew weren't
causing the problem; a proper form a triage. I would have no qualms
whatsoever if this bug was pursued against the xserver-xorg-video-ati
driver, which is cu
C, thank you for your message. I don't think I fell foul of the CoC. I
don't have any problem to stand by any word I said, although I will
gladly admit that Jonathan's behaviour infuriated me. And no, I don't
think I opened any of the tasks unnecessarily. Unfortunately, it seems
that these days
@R0lf: please respect the CoC. Bewing aggressive will not help any. On
the same token, opening task against all possible culprits also does not
help...
Thank you.
--
screen corruption
https://bugs.launchpad.net/bugs/401776
You received this bug notification because you are a member of Ubuntu
Bu
Does it happen if you run the apps locally?
Try disabling acceleration on the karmic host, by adding Option
"NoAccel" to the Device section in your xorg.conf.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: New => Incomplete
--
screen corruption
https://bugs.launchpad.net/bugs/401
If I am not committing bug fix to a piece of software you filed a bug
against, I therefore must not understand at all how any of the said
software works. Brilliant logic.
The fact is that this bug is affecting software at a level *lower* than
either the application or toolkit layer, hence somewher
Jonathan, congratulations on your complete non-understanding of triaging
this bug.
BTW, your logic is flawed and you are not helping to fix or triage this
issue. I kindly ask you to stay away from this ticket and let those who
are not only after increasing their "bragging rights" try and find the
Happens in a GTK+ app too -> Not a Qt issue.
** Changed in: qt-x11-free (Ubuntu)
Status: New => Invalid
--
screen corruption
https://bugs.launchpad.net/bugs/401776
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
It very likely is something lower than any of the apps. It may even be
something lower than the libs listed so far. Timo raised the
possibility this may be a driver issue. I've added an ATI task here and
will test later tonight.
--
screen corruption
https://bugs.launchpad.net/bugs/401776
You r
Sorry Rolf. I assumed it was something lower that FSlint when other apps were
affected.
I can confirm that FSlint is a pygtk app.
--
screen corruption
https://bugs.launchpad.net/bugs/401776
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yeah, guys. Really cool! Padraig did not even bother making a comment
when setting to invalid. Pretty soon, this bug will be completely off
the radar. I'm quite certain that it's not an issue per se in the last
two remaining applications. This bug hasn't even been open for 24
hours. Is it bot
*really* understanding a bug is a precondition to fixing a bug. We're
not there yet. The race to *fix* this bug has only just started.
--
screen corruption
https://bugs.launchpad.net/bugs/401776
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
** Changed in: fslint (Ubuntu)
Status: New => Invalid
--
screen corruption
https://bugs.launchpad.net/bugs/401776
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b...@lists.ubuntu.com
https://li
There haven't really been all that many changed in Qt3 either, (it's
till at the same/latest upstream release) so it's probably not that
either.
** Changed in: qt-x11-free (Ubuntu)
Status: New => Invalid
--
screen corruption
https://bugs.launchpad.net/bugs/401776
You received this bug not
libxext is the same version on both jaunty and karmic, and libx11 is an
unlikely candidate as well. Maybe the driver to blame.
** Changed in: libxext (Ubuntu)
Status: New => Invalid
** Changed in: libx11 (Ubuntu)
Status: New => Invalid
--
screen corruption
https://bugs.launchpad.n
Robert, not thus far. I've listed the apps that give me problems here.
Although I do experience something very similar in my XFCE desktop (no
ssh forwarding at all). File names are displayed fine, but when I
select an icon, a very similar corruption of the filename occurs. Not
sure if this isn't
thinking about it, I remember now that fslint-gui was affected as well
when forwarded from hardy over ssh. fslint-gui is based on GTK.
** Attachment added: "fslint-corrupted.png"
http://launchpadlibrarian.net/29544050/fslint-corrupted.png
--
screen corruption
https://bugs.launchpad.net/bugs/
17 matches
Mail list logo
