The link works okay for me.
So it sounds like this is an ACPI / Kernel issue rather than an Xorg
issue. I'll refile accordingly.
** Changed in: linux (Ubuntu)
Sourcepackagename: xserver-xorg-video-trident = linux
Importance: Undecided = Medium
Status: Incomplete = Triaged
** Summary
That posted Link doesnt't work. Can you repost it in correct way?
Thanks!
--
Change Toshiba Portege R100 screen brightness corrupts X resolution
https://bugs.launchpad.net/bugs/104745
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This issue is now fixable:
http://ubuntuforums.org/archive/index.php/t-533793.html
--
Change Toshiba Portege R100 screen brightness corrupts X resolution
https://bugs.launchpad.net/bugs/104745
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags added: valid-xorg-conf
--
Change Toshiba Portege R100 screen brightness corrupts X resolution
https://bugs.launchpad.net/bugs/104745
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/16417232/Xorg.0.log
--
Change Toshiba Portege R100 screen brightness corrupts X resolution
https://bugs.launchpad.net/bugs/104745
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
We need /var/log/Xorg.0.log, not xorg.conf (although thanks for
including it too). Leaving as Incomplete since we still don't have the
info needed to conduct troubleshooting.
** Changed in: xserver-xorg-video-trident (Ubuntu)
Importance: High = Undecided
--
Change Toshiba Portege R100
I also can report this problem under Kubuntu 8.04 (hardy).
When I first installed the system, the monitor couldn't be automatically
detected, I had to fix this using xfailsafedialog.
Originally, on a screen brightness change, the top-left quarter of the
screen was magnified to fill the whole
Please attach your /var/log/Xorg.0.log
** Changed in: xserver-xorg-video-trident (Ubuntu)
Sourcepackagename: xorg = xserver-xorg-video-trident
Importance: Undecided = High
Status: New = Incomplete
--
Change Toshiba Portege R100 screen brightness corrupts X resolution
** Changed in: xorg (Ubuntu)
Sourcepackagename: None = xorg
Assignee: Brian Murray (brian-murray) = (unassigned)
Status: Incomplete = New
--
Change Toshiba Portege R100 screen brightness corrupts X resolution
https://bugs.launchpad.net/bugs/104745
You received this bug notification
This bug is present in Hardy Beta as well. Additionally, the screen
gets garbled intermittently, see attached screenshots. I am yet to
figure out what causes that.
What's worse, X now forces a reconfiguration at every reboot and
switches back to the broken trident driver if I set fbdev through
Autoconfig redeemed. I stopped gdm, killing X, and edited xorg.conf by
hand. X -probeonly reported no /dev/fb0 - it never occurred to me to
look. The generic kernel no longer has the framebuffer enabled, so
using fbdev is no longer possible in the default config. There was a
way to force
The bug is still present in Hardy Alpha 6. A workaround is to use the
fbdev driver in xorg.conf - this way X uses the framebuffer, which knows
how to handle this video chip correctly, at the expense of acceleration.
This was reported way back when at
Well the bug is a bit better with Hardy Alpha 5 in that it gets the
correct resolution on startup. However when I manually changed the
brightness of the screen (the brightness function + F6,F7 keys,
unplugging AC power, or letting the computer go idle dont actually
change the brightness of the
The issue that you reported is one that should be reproducable with the
live environment of the Desktop CD of the development release - Hardy
Heron. It would help us greatly if you could test with it so we can
work on getting it fixed in the actively developed kernel. You can find
out more about
I have recently run into this same problem as well with a fresh install
of Ubuntu 7.10 on a Toshiba R100 as well. After some reading I've found
a few other people with the same problem, namely the first link below
which is another launchpad bug. As it has been mentioned before, any
changes to
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in recently. We were wondering if this is still and issue
for you? Thanks in advance.
** Changed in: ubuntu
Assignee: (unassigned) =
16 matches
Mail list logo
