In Ubuntu-Budgie the above trick doesn't solve the problem. I notice
that Ubuntu Desktop is using gdm3 whereas Ubuntu Budgie is using
lightdm. They are calling xorg with different arguments. So I
reconfigured Budgie for gdm3 and, after creating the monitor.xml file,
the flicker is gone.
I hope, th
Have to add to the above: after first login, I rearranged the screens
using the Display Settings. That creates a file ~/.config/monitors.xml.
That file does some magic in preventing the flickering. However, it
becomes effective only after logging out and logging in again, so I was
mislead when test
Hi,
first to say: I've been testing Ubuntu-Budgie. There is no option to run on
Wayland. So I downloaded (2021-02-02) and installed Ubuntu 21.04 Desktop to
perform the test and found some surprising results:
1. fresh installation, running on Xorg: the flickering is clearly visible. In
fact, the
Public bug reported:
When running on dual screen config, the cursor is heavily flickering.
Makes it a very unpleasant experience, if not renders it unusable. If
switched to only single screen, cursor is completely stable.
When issuing
xrandr --output HDMI-2 --scale 0.99x0.99
again cursor is stab
Is there any other information I could provide?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1890411
Title:
[bionic] Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.
To manage notific
I just added the crash report of gdm3: https://errors.ubuntu.com/oops
/1e6d888a-d7c5-11ea-ae81-fa163ee63de6
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1890411
Title:
[bionic] Xorg crashes wh
I followed step 1 and 2. I don't know how to get the ID. According to
step 2 the link to the crash report is https://errors.ubuntu.com/oops
/3d15afdc-d7b7-11ea-b244-fa163e983629
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
http
Was wrong package
** Package changed: apport (Ubuntu) => xorg-server (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1890411
Title:
Xorg crashes when starting gdm3. Bug in libgl1
** Attachment added: "/usr/share/xorg.conf.d/50-jabra.conf which solves the
issue"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581626/+attachment/4663460/+files/50-jabra.conf
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in U
Yet more info and a better fix:
xinput list --long provides this for the device:
⎜ ↳ GN Netcom A/S Jabra EVOLVE LINK MSid=15 [slave pointer (2)]
Reporting 16 classes:
Class originated from: 15. Type: XIButtonClass
Buttons supported: 12
A little more info:
'xinput list' provides the following when the device is plugged in:
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)]
⎜ ↳ ELAN Touchscreen id=12
Just to add, the device does have a set of buttons as well, so it might
be some sort of USB HID conflict? Only two of them show anything when
run under xev, XF86VolumeUp and XF86VolumeDown.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in
Public bug reported:
When I switch the primary sound device to a USB headset connected to my
laptop, mouse click events no longer work except in the Sound Settings
window. This does not seem to occur when the device is connected, only
when it is made the default audio device.
Once this occurs, t
And one more thing: make sure that file permissions for the script are
correctly set; otherwise, the script may not run when the system
resumes. I would suggest running the following command after copying it
to /etc/pm/sleep.d to make sure it will run when the system resumes:
sudo chmod +x /etc/pm
The attached script with the workaround mentioned in comment #19 ought
to do the trick. Simply copy it to the /etc/pm/sleep.d directory. I
tested it on my X201 Tablet, and I was able to get the touchscreen to
work on every resume.
** Attachment added: "Workaround script for X200T/X201T laptops"
I found a workaround from
https://answers.launchpad.net/ubuntu/+question/243145 that works with
the X201 tablet, and it does not require rebooting, logging off and on
again, or switching between virtual consoles. Try entering
sudo inputattach --daemon -w8001 /dev/ttyS4
If that does not work for
So, we have nv34, nv43 and nv44 affected by this. I updated the
bugreport title so hopefully more people will stumble on it earlier
(hope that is okay).
- nv44: GCC thread: During normal operation.
- nv43: Resuming from suspend-to-mem
- nv34: Resuming from suspend-to-disk
--
You received this bu
Public bug reported:
My initial bugreport was here:
https://bugs.freedesktop.org/show_bug.cgi?id=71116
- Recompiling libdrm with gcc 4.7 fixed the bug.
Upstream GCC mail thread here: http://gcc.gnu.org/ml/gcc-
help/2013-07/msg00103.html
This was fixed thanks to Emil Velikov from the nouveau pro
Mickey: Thank you for posting your results after your (probably) time
consuming research.
This used to work flawlessly with nouveau and (apparently) never with
the blob. I'm using your suggestion now.
For now, the nouveau drivers (apparently) suffers from the same issue.
But only after I upgraded
Public bug reported:
When I try to run qupzilla (or probably any other libqtwebkit4 browser),
I get this in gdb:
Program received signal SIGILL, Illegal instruction.
0xb739f773 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
I asked the author of qupzilla first, and he confirmed my susp
The Gazebo robotics simulation is working very slowly on my Thinkpad
X220 with Intel graphics and this is probably due to the same problem.
Ubuntu version is 12.04.
As pointed out to me, the important information here is in glxinfo (full
info attached) : "client glx vendor string: Mesa Project and
Public bug reported:
I want to start with the ufw activated but it it yeilds a purple screen.
So I have been using the reboot disk.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xorg 1:7.7+1ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
Uname: Linux 3.5.0-19-generic i686
.
Is there a plan for resolving the issue with nvidia-96 or is nVidia
unlikely to provide the same update for those cards? I have a GeForce MX
4000 that worked fine in 11.10 but now doesn't, and the 173 drivers
don't work with it. I know it's an old card, but sourcing AGP cards is
getting hard! I'd r
For me, the psmouse was the issue on a T420
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/41301
Title:
Mouse clicks stop working sporadically
To manage notifications about this bug go t
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1010838
Title:
Ubuntu 12.04 has a problem with my nvidia card
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sour
Public bug reported:
Hi,
I believe Ubuntu 12.04 (32bits) has a big problem with nvidia cards.
Since upgrade to it my system did not boot normally anymore, and only
with low resolutions.
I tried quite a lot, like switching between the nvidia, nouveau and vesa
driver but only the vesa driver worke
** Also affects: nvidia-graphics-drivers (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-180 in Ubuntu.
https://bugs.launchpad.net/bugs/461958
Title:
Black screen on
apport information
** Attachment added: "dmidecode.txt.txt"
https://bugs.launchpad.net/bugs/908161/+attachment/2649580/+files/dmidecode.txt.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.la
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/908161/+attachment/2649579/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/908161/+attachment/2649578/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/908161/+attachment/2649577/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "UnitySupportTest.txt"
https://bugs.launchpad.net/bugs/908161/+attachment/2649576/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://b
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/908161/+attachment/2649575/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/908161/+attachment/2649574/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bug
Just going to change my settings back to the way that they were when the
bug first appeared.
CompizConfig Settings Manager > Unity Plugin
Experimental > launcher icon size 32
Behavior > Hide Launcher Never
Settings are back to previous and icons are still visible.
--
You received thi
apport information
** Attachment added: "xkbcomp.txt"
https://bugs.launchpad.net/bugs/908161/+attachment/2649588/+files/xkbcomp.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "xinput.txt"
https://bugs.launchpad.net/bugs/908161/+attachment/2649587/+files/xinput.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/908161/+attachment/2649586/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.ne
apport information
** Attachment added: "setxkbmap.txt"
https://bugs.launchpad.net/bugs/908161/+attachment/2649583/+files/setxkbmap.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.
apport information
** Attachment added: "peripherals.txt"
https://bugs.launchpad.net/bugs/908161/+attachment/2649582/+files/peripherals.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/908161/+attachment/2649573/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/908161/+attachment/2649572/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/908161/+attachment/2649571/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "MonitorsUser.xml.txt"
https://bugs.launchpad.net/bugs/908161/+attachment/2649570/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://b
apport information
** Attachment added: "locale.txt"
https://bugs.launchpad.net/bugs/908161/+attachment/2649581/+files/locale.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/908161/+attachment/2649569/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/908161/+attachment/2649568/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/908161/+attachment/2649567/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "GdmLog2.txt"
https://bugs.launchpad.net/bugs/908161/+attachment/2649566/+files/GdmLog2.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "GdmLog1.txt"
https://bugs.launchpad.net/bugs/908161/+attachment/2649565/+files/GdmLog1.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "GdmLog.txt"
https://bugs.launchpad.net/bugs/908161/+attachment/2649564/+files/GdmLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "GconfCompiz.txt"
https://bugs.launchpad.net/bugs/908161/+attachment/2649563/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "BootLog.gz"
https://bugs.launchpad.net/bugs/908161/+attachment/2649560/+files/BootLog.gz
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/908161/+attachment/2649562/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/908161/+attachment/2649561/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.laun
I have just restarted after an update.
The icons are now displaying again. Though it is back to the default
icons rather than my customisation prior to my unity --reset and unity
--reset-icons
I do not know what was changed by the update so I am submitting a new
apport-collect with my current s
I have been unable to reproduce the issue due to bug 889532 which
prevents me from using Unity 3D with the proprietary nvidia driver, so
I'm not sure if it can be closed or not.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-driv
** Attachment added: "/var/log/syslog including a segfault"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/889532/+attachment/2594306/+files/syslog
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-driver
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/889532
Title:
GL applications segfault after updating nvidia driver
To manage notifications about this bug go to:
https://bugs.l
Public bug reported:
After a fresh install, the proprietary nvidia drivers worked correctly
in oneiric on my 64-bit install. However at some point they stopped
working and I automatically fell back to Unity 2D (and did not realize
this until I tried to play a GL-based game).
An example of the cr
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/859979
Title:
Poor performance in oneric beta 2 on nvidia geforce 7100 / nforce 630i
To manage notifications about this bug go t
Public bug reported:
The performance in oneric beta 2 on this card is noticeably slower than
on previous releases. Animations are jerky and slow -- sometimes the
dash takes around two seconds to finish disappearing. Icon highlights
in the application lens are very laggy, following several icons
I have the same problem i think. See my remarks (#90 and #91) at bug
728745. I am using the recommended version of the nvidia driver.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bu
This is how I found out Classic mode without visual effects cold be an
effective workaround: http://ubuntuforums.org/showthread.php?t=1755014
I hope the bug will be fixed soon. Else if Ubuntu 11.10 will no longer
support classic mode, I will not be able to upgrade anymore...
--
You received this
I think the bug is still present in latest release. For after my upgarde from
10.10 (in which Compiz worked fine) I had to major issues:
1. X did not start. It crashed and I ended up in console 1. Manually setting
the general vesa driver in /etc/Xorg worked was a temp solution. Final solution
is
Confirm same problem after upgrade from 10.10 to 11.04
x86_64
HP Pavilion dv9205us
NVIDIA GeForce Go 6150 (UMA)
"Recommended" nvidia driver causes white screen window if more than two
maximized windows.
Downgrading to 173 nvidia driver allows many maximized windows.
--
You received this bug no
I am not able to reproduce this problem. (Not willing to use my
production laptop to reinstall 10.04 and upgrade to 10.10 again). When I
encounter the same issue again upgrading to 11.04 I will file a new
bugreport.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Incomplete => Invali
I am unable to consistently reproduce this, as I do not have direct
physical access to the machine and it does not appear to happen to me
when I reboot it remotely.
K-9, could you follow the steps in the wiki page below to get a
backtrace and attach it to this bug?
https://wiki.ubuntu.com/X/Backt
I should make it clear that the previous post is the Xorg.0.log.old
file.
--
[GMA-500] Xorg spontaneously freezes (under heavy loads?) after a while
https://bugs.launchpad.net/bugs/393290
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-
** Attachment added: "I apologize for the long delay, but I was away from my
fit-PC2 for a long time."
http://launchpadlibrarian.net/37559443/Xorg.0.log.old
--
[GMA-500] Xorg spontaneously freezes (under heavy loads?) after a while
https://bugs.launchpad.net/bugs/393290
You received this bug
Ok, I installed mythbuntu 9.04 on a separate partition. After checking
that the problem still exists, I added the ppa mythtv repository and
updated all packages that were available for updating.
However, now neither mythtv-setup or mythfrontend will not start
anymore:
2009-09-01 23:21:56.201 Load
Marc, you are probably right that this is a better time to get this bug
fixed than after the release has been made. Your suggestion to try this
in a VM is not workable (I think) because the problem lies with specific
hardware support. I doubt that there is any VM that virtualizes the
cle266 graphic
After spending quite some time investigating this issue, with the
conclusion that changes in the way XvMC VLD is used in mythtv is the
likely source of this problem. The fact that xine runs smoothly also
indicates in this direction. The message "Unable to create XvMC
Surface." is actually harmless
** Changed in: mythtv (Ubuntu)
Status: Invalid => New
--
[CLE266] [jaunty] Cannot create openchrome XvMC Surface in mythfrontend
https://bugs.launchpad.net/bugs/371512
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchr
Leann,
This kernel seems to have fixed the issue! I will report back if the
behavior reoccurs.
Thank you -- my laptop is usable again :)
--
[i945] X flickers wildly whenever anything on-screen updates
https://bugs.launchpad.net/bugs/412492
You received this bug notification because you are a m
Further testing reveals that this appears to affect my display only when
set to its native resolution (1440x900). Changing to another
resolution, e.g. 1024x768, makes this problem go away.
--
X flickers wildly whenever anything on-screen updates
https://bugs.launchpad.net/bugs/412492
You receive
** Attachment added: "Video of the effect"
http://launchpadlibrarian.net/30222053/video-2009-08-12-08-20-25.3gp
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/30222054/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/30222055/Curren
Public bug reported:
Binary package hint: xorg
After dist-upgrading today on , X flickers and is unusable any time any
object on the screen is painted. Opening the main menu from the panel
causes the entire screen to flicker for around a second. Switching
desktops or opening/closing/moving a wi
** Attachment added: "This file contains the strace output of Xorg."
http://launchpadlibrarian.net/28493752/xorg-strace.txt
--
[GMA-500] Xorg spontaneously freezes (under heavy loads?) after a while
https://bugs.launchpad.net/bugs/393290
You received this bug notification because you are a me
Public bug reported:
Hello,
I have a Compulab fit-PC2 running Ubuntu Jaunty, and its graphics chip
is the Intel GMA-500. I am using the Poulsbo driver (xserver-xorg-
video-psb 0.31.0-0ubuntu1~904um1 with psb-modules
4.41.1-0ubuntu1~904um1) from Launchpad's Ubuntu Mobile PPA site.
However, I keep
We've a (related?) problem when playing video's in LTSP on our HP t5735
thin clients, exactly like the problem described in:
* #359831: [i945gm] all video players crash with BadAlloc error (no
Compiz)
Details:
* no compiz
* no /etc/X11/xorg.conf
--
Xv playback shows green screen on [1002:4c
My last comment seems to be handled in #365843
--
[i945gm] all video players crash with BadAlloc error (no Compiz)
https://bugs.launchpad.net/bugs/359831
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubuntu.
__
We are experiencing horizontal glitches showing very briefly (multi
color single pixel rows while moving cursor) using 1:6.12.1-0ubuntu2 on
our ltsp-clients (HP t5735).
--
[X1950] Vertical bands of interference around HW cursor
https://bugs.launchpad.net/bugs/320771
You received this bug notifica
This is also the case for all of our HP t5725 thin clients using
xserver-xorg-video-radeon!
--
[i945gm] all video players crash with BadAlloc error (no Compiz)
https://bugs.launchpad.net/bugs/359831
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xs
On a suggestion from the #unichrome mailing list (where openchrome is
discussed) I tried to run xine -V xxmc on a DVD.
This worked wonderfully, so aparently it is not openchrome XvMC that is the
problem here.
As it would seem, aparently mythtv is to blame.
Ronald
** Attachment added: "
85 matches
Mail list logo
