Erik's patch was applied upstream and also included in radeontool
1.6.0-1 which has been synced into Lucid. Thanks for your contribution!
** Changed in: radeontool (Ubuntu)
Status: Confirmed => Fix Released
--
radeontool writes error messages to stdout
https://bugs.launchpad.net/bugs/3183
Patch sent upstream (Dave Airlied).
--
radeontool writes error messages to stdout
https://bugs.launchpad.net/bugs/318303
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://li
(Sorry for the late reply) erik.edelm...@iki.fi is probably best
--
radeontool writes error messages to stdout
https://bugs.launchpad.net/bugs/318303
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
Erik, thanks for your patch. I am forwarding this upstream. What is the
e-mail address you want to use in the Author header?
--
radeontool writes error messages to stdout
https://bugs.launchpad.net/bugs/318303
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Changed in: radeontool (Ubuntu)
Status: Incomplete => Confirmed
--
radeontool writes error messages to stdout
https://bugs.launchpad.net/bugs/318303
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
** Description changed:
Binary package hint: radeontool
Radeontool writes error messages to stdout:
$ sudo radeontool reg > regdump
$ cat regdump
usage: radeontool [options] [command]
--debug- show a little debug info
--skip=1 - use the s
Looking at the attachments in this bug report, I noticed that
"radeontool.diff" was not flagged as a patch. A patch contains changes
to an Ubuntu package that will resolve a bug and this attachment is one!
Subsequently, I've checked the patch flag for it. In the future when
submitting patches ple
This patch would fix the problem. It's not necessarily complete; I
didn't check whether there might be other cases of error messages going
to stdout instead of stderr, but this fixes at least one case. (And
maybe I should have sent this bug report directly to the radeontool
developers. Oh well, som
Ok, so here's my lspci -vvnn, Xorg.0.log and xorg.conf, if you think you
need them. I do, however, dare to claim that the problem is completely
independent of my hardware or X setup. It's caused by the fact that the
function usage() in file radeontool.c in the source code, uses
printf("..."), when
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/21580807/Xorg.0.log
--
radeontool writes error messages to stdout
https://bugs.launchpad.net/bugs/318303
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: "lspci-vvnn.log"
http://launchpadlibrarian.net/21580784/lspci-vvnn.log
--
radeontool writes error messages to stdout
https://bugs.launchpad.net/bugs/318303
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
Hi erik-edelmann,
Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log
file from after reproducing this issue. If you've made any customizations to
your /etc/X11/xorg.conf please attach that as well.
Please attach the output of `lspci -vvnn` too.
[This is an automat
12 matches
Mail list logo
