2013-07-27 13:43:07 |
Erick Brunzell |
bug |
|
|
added bug |
2013-07-28 13:35:37 |
Ubuntu QA Website |
tags |
|
iso-testing |
|
2013-08-25 02:30:54 |
Launchpad Janitor |
xorg (Ubuntu): status |
New |
Confirmed |
|
2013-08-25 02:31:57 |
Jane Atkinson |
bug |
|
|
added subscriber Jane Atkinson |
2013-08-25 09:41:36 |
Jackson Doak |
bug |
|
|
added subscriber Jackson Doak |
2013-09-03 09:29:53 |
Erick Brunzell |
attachment added |
|
Xorg.0 https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1205643/+attachment/3800608/+files/Xorg.0 |
|
2013-09-03 09:31:22 |
Erick Brunzell |
attachment added |
|
syslog https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1205643/+attachment/3800609/+files/syslog |
|
2013-09-03 09:32:20 |
Erick Brunzell |
attachment added |
|
dmseg https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1205643/+attachment/3800610/+files/dmseg |
|
2013-10-27 18:25:44 |
RĂ¼diger Kupper |
bug |
|
|
added subscriber RĂ¼diger Kupper |
2013-11-30 13:30:40 |
Erick Brunzell |
tags |
iso-testing |
iso-testing saucy trusty |
|
2013-12-02 17:09:16 |
Maarten Lankhorst |
affects |
xorg (Ubuntu) |
xserver-xorg-video-openchrome (Ubuntu) |
|
2013-12-02 17:09:39 |
Maarten Lankhorst |
xserver-xorg-video-openchrome (Ubuntu): importance |
Undecided |
Low |
|
2013-12-02 17:09:47 |
Maarten Lankhorst |
xserver-xorg-video-openchrome (Ubuntu): status |
Confirmed |
Incomplete |
|
2013-12-03 14:52:27 |
Erick Brunzell |
summary |
VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy |
VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy & Trusty |
|
2013-12-07 15:13:53 |
Andrea |
bug |
|
|
added subscriber Andrea |
2014-01-19 08:50:44 |
Erick Brunzell |
summary |
VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy & Trusty |
VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy & 12.04.4 candidate |
|
2014-01-19 09:15:55 |
Erick Brunzell |
xserver-xorg-video-openchrome (Ubuntu): status |
Incomplete |
Confirmed |
|
2014-01-28 10:21:24 |
Dmitry Shachnev |
nominated for series |
|
Ubuntu Precise |
|
2014-01-28 10:21:24 |
Dmitry Shachnev |
nominated for series |
|
Ubuntu Saucy |
|
2014-01-28 10:21:24 |
Dmitry Shachnev |
nominated for series |
|
Ubuntu Trusty |
|
2014-01-29 13:55:13 |
Maarten Lankhorst |
xserver-xorg-video-openchrome (Ubuntu): status |
Confirmed |
Fix Released |
|
2014-01-29 13:55:21 |
Maarten Lankhorst |
bug task added |
|
xserver-xorg-video-openchrome (Ubuntu Trusty) |
|
2014-01-29 13:59:16 |
Maarten Lankhorst |
bug task added |
|
xserver-xorg-video-openchrome (Ubuntu Saucy) |
|
2014-01-29 13:59:32 |
Maarten Lankhorst |
xserver-xorg-video-openchrome (Ubuntu Saucy): assignee |
|
Dmitry Shachnev (mitya57) |
|
2014-01-29 13:59:36 |
Maarten Lankhorst |
xserver-xorg-video-openchrome (Ubuntu Saucy): importance |
Undecided |
Low |
|
2014-01-29 13:59:42 |
Maarten Lankhorst |
xserver-xorg-video-openchrome (Ubuntu Saucy): status |
New |
In Progress |
|
2014-01-29 14:18:43 |
Maarten Lankhorst |
xserver-xorg-video-openchrome (Ubuntu Saucy): assignee |
Dmitry Shachnev (mitya57) |
Erick Brunzell (lbsolost) |
|
2014-01-29 14:19:31 |
Dmitry Shachnev |
bug |
|
|
added subscriber Dmitry Shachnev |
2014-01-29 23:41:14 |
Erick Brunzell |
xserver-xorg-video-openchrome (Ubuntu Saucy): assignee |
Erick Brunzell (lbsolost) |
|
|
2014-01-29 23:41:53 |
Erick Brunzell |
xserver-xorg-video-openchrome (Ubuntu Saucy): status |
In Progress |
Confirmed |
|
2014-01-30 06:28:55 |
Dmitry Shachnev |
xserver-xorg-video-openchrome (Ubuntu Saucy): status |
Confirmed |
Won't Fix |
|
2014-04-09 03:31:39 |
Alberto Jovito |
bug |
|
|
added subscriber Alberto Jovito |
2014-04-09 08:03:21 |
Erick Brunzell |
attachment added |
|
history.log https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1205643/+attachment/4076652/+files/history.log |
|
2014-04-09 08:05:14 |
Erick Brunzell |
attachment added |
|
term.log https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1205643/+attachment/4076654/+files/term.log |
|
2014-04-11 08:56:44 |
Alberto Jovito |
bug task added |
|
xserver-xorg-video-openchrome-lts-saucy (Ubuntu) |
|
2014-04-11 08:59:35 |
Alberto Jovito |
bug task deleted |
xserver-xorg-video-openchrome-lts-saucy (Ubuntu Trusty) |
|
|
2014-04-11 08:59:51 |
Alberto Jovito |
bug task deleted |
xserver-xorg-video-openchrome-lts-saucy (Ubuntu Saucy) |
|
|
2014-04-11 13:00:34 |
Erick Brunzell |
xserver-xorg-video-openchrome-lts-saucy (Ubuntu): status |
New |
Confirmed |
|
2014-04-12 09:06:44 |
Dmitry Shachnev |
xserver-xorg-video-openchrome (Ubuntu Saucy): status |
Won't Fix |
Fix Released |
|
2014-04-14 02:13:45 |
Alberto Jovito |
attachment added |
|
xserver-xorg-video-openchrome-lts-saucy_precise-proposed https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1205643/+attachment/4083057/+files/xserver-xorg-video-openchrome-lts-saucy_precise-proposed.debdiff.gz |
|
2014-04-14 02:30:03 |
Alberto Jovito |
description |
Please bear with me and read all of this. Since I can't get a working display in Saucy with that graphics chip I need to use this method to file the initial bug report, but I can provide info using a chroot or replacing the "quiet splash" boot parameter with "text" which takes me to a tty interface.
I hope using the tty interface provided by using the "text" boot parameter I can use "apport-collect" to collect the info needed from an installed Lubuntu 13.10 but I won't do so until asked by a dev in case some "switch" needs to be set to collect the appropriate info.
I also want to say that I'm fully aware that graphics chip is not supported by Ubuntu/compiz itself, or even GNOME's mutter window manager, but I think it should still work with the openbox, metacity, and Xfwm window managers ...... at least I hope so :^)
So onto what actually happens. When I try to boot either Lubuntu or Xubuntu Saucy Alpha 2, either the live image or an installed version, I just get a frozen progress bar. So it's just 5 frozen dots on the screen. If I try booting through the recovery mode or otherwise trying to "startx" or "'sudo service lightdm start' I just get a blank screen. I can see the backlight is working but that's all.
This is the specific hardware:
VIA C7 CPU @ 1500MHz
VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] (rev 01)
VIA VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
1GB DDR2 RAM
I did take a pic of the live image boot process while dealing with an unrelated d-i bug during Lubuntu Alpha 2 testing process:
https://launchpadlibrarian.net/145894508/P4M800_xfreeze.JPG
Now I'm wondering what else to say ............... the same Saucy images and installs work with two other totally different sets of hardware.
I'm ready to roll up my sleeves to help gather any needed info. Thanks in advance. |
* Impact:
- the driver doesn't work with the X.org version in 12.04 with the Saucy hardware enablement stack.
* Test case:
- try using 12.04 with the Saucy hardware enablement stack on a machine needing the openchrome driver.
* regression potential:
- check that xorg sessions work as they should. The patches have received testing in Saucy/Debian/Trusty and upstream, so presumably should be fairly safe. The number of people using openchrome is relatively small compared to the main X drivers, so the scope of risk is rather small here.
----------
Saucy Hardware Enablement Stack:
https://wiki.ubuntu.com/Kernel/LTSEnablementStack
-------
Please bear with me and read all of this. Since I can't get a working display in Saucy with that graphics chip I need to use this method to file the initial bug report, but I can provide info using a chroot or replacing the "quiet splash" boot parameter with "text" which takes me to a tty interface.
I hope using the tty interface provided by using the "text" boot parameter I can use "apport-collect" to collect the info needed from an installed Lubuntu 13.10 but I won't do so until asked by a dev in case some "switch" needs to be set to collect the appropriate info.
I also want to say that I'm fully aware that graphics chip is not supported by Ubuntu/compiz itself, or even GNOME's mutter window manager, but I think it should still work with the openbox, metacity, and Xfwm window managers ...... at least I hope so :^)
So onto what actually happens. When I try to boot either Lubuntu or Xubuntu Saucy Alpha 2, either the live image or an installed version, I just get a frozen progress bar. So it's just 5 frozen dots on the screen. If I try booting through the recovery mode or otherwise trying to "startx" or "'sudo service lightdm start' I just get a blank screen. I can see the backlight is working but that's all.
This is the specific hardware:
VIA C7 CPU @ 1500MHz
VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] (rev 01)
VIA VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
1GB DDR2 RAM
I did take a pic of the live image boot process while dealing with an unrelated d-i bug during Lubuntu Alpha 2 testing process:
https://launchpadlibrarian.net/145894508/P4M800_xfreeze.JPG
Now I'm wondering what else to say ............... the same Saucy images and installs work with two other totally different sets of hardware.
I'm ready to roll up my sleeves to help gather any needed info. Thanks in advance. |
|
2014-04-14 02:31:35 |
Alberto Jovito |
tags |
iso-testing saucy trusty |
iso-testing patch saucy trusty |
|
2014-04-14 02:33:12 |
Alberto Jovito |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
2014-04-14 02:52:47 |
Alberto Jovito |
description |
* Impact:
- the driver doesn't work with the X.org version in 12.04 with the Saucy hardware enablement stack.
* Test case:
- try using 12.04 with the Saucy hardware enablement stack on a machine needing the openchrome driver.
* regression potential:
- check that xorg sessions work as they should. The patches have received testing in Saucy/Debian/Trusty and upstream, so presumably should be fairly safe. The number of people using openchrome is relatively small compared to the main X drivers, so the scope of risk is rather small here.
----------
Saucy Hardware Enablement Stack:
https://wiki.ubuntu.com/Kernel/LTSEnablementStack
-------
Please bear with me and read all of this. Since I can't get a working display in Saucy with that graphics chip I need to use this method to file the initial bug report, but I can provide info using a chroot or replacing the "quiet splash" boot parameter with "text" which takes me to a tty interface.
I hope using the tty interface provided by using the "text" boot parameter I can use "apport-collect" to collect the info needed from an installed Lubuntu 13.10 but I won't do so until asked by a dev in case some "switch" needs to be set to collect the appropriate info.
I also want to say that I'm fully aware that graphics chip is not supported by Ubuntu/compiz itself, or even GNOME's mutter window manager, but I think it should still work with the openbox, metacity, and Xfwm window managers ...... at least I hope so :^)
So onto what actually happens. When I try to boot either Lubuntu or Xubuntu Saucy Alpha 2, either the live image or an installed version, I just get a frozen progress bar. So it's just 5 frozen dots on the screen. If I try booting through the recovery mode or otherwise trying to "startx" or "'sudo service lightdm start' I just get a blank screen. I can see the backlight is working but that's all.
This is the specific hardware:
VIA C7 CPU @ 1500MHz
VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] (rev 01)
VIA VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
1GB DDR2 RAM
I did take a pic of the live image boot process while dealing with an unrelated d-i bug during Lubuntu Alpha 2 testing process:
https://launchpadlibrarian.net/145894508/P4M800_xfreeze.JPG
Now I'm wondering what else to say ............... the same Saucy images and installs work with two other totally different sets of hardware.
I'm ready to roll up my sleeves to help gather any needed info. Thanks in advance. |
* Impact:
- the driver doesn't work with the X.org version in 12.04 with the Saucy hardware enablement stack.
* Test case:
- try using 12.04 with the Saucy hardware enablement stack on a machine needing the openchrome driver.
* regression potential:
- check that xorg sessions work as they should. The patches have received testing in Debian/Trusty/Saucy and upstream, so presumably should be fairly safe. The number of people using openchrome is relatively small compared to the main X drivers, so the scope of risk is rather small here.
----------
Saucy Hardware Enablement Stack:
https://wiki.ubuntu.com/Kernel/LTSEnablementStack
-------
Please bear with me and read all of this. Since I can't get a working display in Saucy with that graphics chip I need to use this method to file the initial bug report, but I can provide info using a chroot or replacing the "quiet splash" boot parameter with "text" which takes me to a tty interface.
I hope using the tty interface provided by using the "text" boot parameter I can use "apport-collect" to collect the info needed from an installed Lubuntu 13.10 but I won't do so until asked by a dev in case some "switch" needs to be set to collect the appropriate info.
I also want to say that I'm fully aware that graphics chip is not supported by Ubuntu/compiz itself, or even GNOME's mutter window manager, but I think it should still work with the openbox, metacity, and Xfwm window managers ...... at least I hope so :^)
So onto what actually happens. When I try to boot either Lubuntu or Xubuntu Saucy Alpha 2, either the live image or an installed version, I just get a frozen progress bar. So it's just 5 frozen dots on the screen. If I try booting through the recovery mode or otherwise trying to "startx" or "'sudo service lightdm start' I just get a blank screen. I can see the backlight is working but that's all.
This is the specific hardware:
VIA C7 CPU @ 1500MHz
VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] (rev 01)
VIA VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
1GB DDR2 RAM
I did take a pic of the live image boot process while dealing with an unrelated d-i bug during Lubuntu Alpha 2 testing process:
https://launchpadlibrarian.net/145894508/P4M800_xfreeze.JPG
Now I'm wondering what else to say ............... the same Saucy images and installs work with two other totally different sets of hardware.
I'm ready to roll up my sleeves to help gather any needed info. Thanks in advance. |
|
2014-04-16 21:40:33 |
george |
xserver-xorg-video-openchrome (Ubuntu Saucy): assignee |
|
george (george98-2010) |
|
2014-06-19 16:12:34 |
Dmitry Shachnev |
xserver-xorg-video-openchrome-lts-saucy (Ubuntu): status |
Confirmed |
Incomplete |
|
2014-06-22 15:08:29 |
Dmitry Shachnev |
xserver-xorg-video-openchrome-lts-saucy (Ubuntu): status |
Incomplete |
In Progress |
|
2014-06-30 08:33:06 |
Iain Lane |
xserver-xorg-video-openchrome-lts-saucy (Ubuntu): status |
In Progress |
Won't Fix |
|