On 2018-08-08 12:22 AM, ppanon wrote:
And... today it's broken again.
--
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/1784240
Title:
Driver doesn't correctly probe Samsung U28D590D 28-inch 4k
--
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/1784240
Title:
Driver doesn't correctly probe Samsung U28D590D 28-inch 4k after
recent update
To manage notifications about this bug go to:
This log shows updated driver deployments on July 23rd coincident with
the start of the detection problems.
** Attachment added: "dpkg.log"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1784240/+attachment/5169276/+files/dpkg.log
--
You received this bug notification because you are a
This log shows that the probing detects the high resolution modes
[ 111.418] (II) AMDGPU(0): Printing probed modes for output DisplayPort-0
[ 111.418] (II) AMDGPU(0): Modeline "3840x2160"x60.0 533.25 3840 3888 3920
4000 2160 2163 2168 +hsync -vsync (133.3 kHz eP)
[ 111.418] (II)
Public bug reported:
This monitor was correctly detected and worked properly at maximum
resolution for the last 2 years, but X no longer correctly identifies
the monitor and now only proposes a maximum display resolution of
1368x768 since a recent update.
ProblemType: Bug
DistroRelease: Ubuntu
Looks like I may be running into issues related to bug #506437 (and perhaps bug
#506435) because the workaround of setting
export LIBGL_DRIVERS_PATH=/usr/lib32/dri
suggested in bug #248392 seems to allow wine to properly detect/use Direct
rendering.
--
[xorg-edgers] after rebuilding, Wine
After upgrading to 2.6.32-13-generic, the machine failed to boot and I had to
do a manual
update-initramfs -c -k 2.6.32-13-generic
while booting from the old kernel.
After doing that initramfs, the system booted and the Natural 4000
keyboard behaviour returned to be the same as with Karmic. The
I've been working pretty hard trying to add Mesa support to Wine for the
Feb. 18 feature freeze, so it would be really nice if this could work in
Lucid x64
--
[xorg-edgers] after rebuilding, Wine doesn't get same results with DRI R600 as
glxinfo
https://bugs.launchpad.net/bugs/515933
You
Public bug reported:
Binary package hint: xserver-xorg-input-evdev
This may or may not be related to bug #295849.
I have a Microsoft Natural 4000 Keyboard with a USB connector and a
Logitech Mouse which can be connected either via USB or PS/2 mouse
connector. The two devices don't seem to work
** Attachment added: version_signature
http://launchpadlibrarian.net/39041082/version_signature
--
Microsoft Natural 4000 Keyboard and logitech mouse initialization conflicts
https://bugs.launchpad.net/bugs/520226
You received this bug notification because you are a member of Ubuntu-X,
which
** Attachment added: uname -a output with USB keyboard and mouse after having
re-plugged in the mouse to get it working
http://launchpadlibrarian.net/39041026/uname-a
--
Microsoft Natural 4000 Keyboard and logitech mouse initialization conflicts
https://bugs.launchpad.net/bugs/520226
You
** Attachment added: Xorg.log with Nat KB, PS/2 mouse, PS.2 KB after coldboot
http://launchpadlibrarian.net/39041147/Xorg.0.log.coldboot
--
Microsoft Natural 4000 Keyboard and logitech mouse initialization conflicts
https://bugs.launchpad.net/bugs/520226
You received this bug notification
** Attachment added: lspci -vvnn output with USB keyboard and mouse after
having re-plugged in the mouse to get it working
http://launchpadlibrarian.net/39041040/lspci-vvnn
--
Microsoft Natural 4000 Keyboard and logitech mouse initialization conflicts
https://bugs.launchpad.net/bugs/520226
** Attachment added: Xorg.log with Nat KB, PS/2 mouse, PS.2 KB after warmboot
http://launchpadlibrarian.net/39041261/Xorg.0.log.warmboot
--
Microsoft Natural 4000 Keyboard and logitech mouse initialization conflicts
https://bugs.launchpad.net/bugs/520226
You received this bug notification
** Attachment added: dmesg with Nat KB, PS/2 mouse, PS.2 KB after warmboot
http://launchpadlibrarian.net/39041283/dmesg.warmboot
--
Microsoft Natural 4000 Keyboard and logitech mouse initialization conflicts
https://bugs.launchpad.net/bugs/520226
You received this bug notification because
** Attachment added: dmesg with Nat KB, USB mouse after warmboot
http://launchpadlibrarian.net/39041362/dmesg.warmboot
--
Microsoft Natural 4000 Keyboard and logitech mouse initialization conflicts
https://bugs.launchpad.net/bugs/520226
You received this bug notification because you are a
** Attachment added: diff of warm/cold boot Xorg.log with Nat KB, USB mouse
http://launchpadlibrarian.net/39041406/Xorg.log.usbmouse.warmcolddiff
--
Microsoft Natural 4000 Keyboard and logitech mouse initialization conflicts
https://bugs.launchpad.net/bugs/520226
You received this bug
** Attachment added: Xorg.log with Nat KB, USB mouse after warmboot
http://launchpadlibrarian.net/39041339/Xorg.0.log.usbmouse.warmboot
--
Microsoft Natural 4000 Keyboard and logitech mouse initialization conflicts
https://bugs.launchpad.net/bugs/520226
You received this bug notification
Sorry, that first paragraph should have been:
I have a Microsoft Natural 4000 Keyboard with a USB connector and a
Logitech Mouse which can be connected either via USB or PS/2 mouse
connector. The two devices don't seem to work well with each other if
both are connected via USB (when the keyboard
** Attachment added: dmesg with Nat KB, PS/2 mouse, PS.2 KB after coldboot
http://launchpadlibrarian.net/39041160/dmesg.coldboot
--
Microsoft Natural 4000 Keyboard and logitech mouse initialization conflicts
https://bugs.launchpad.net/bugs/520226
You received this bug notification because
Thanks. I was starting to wonder if it might be something specific to
the Karmic PPA and was getting ready to try to upgrade to Lucid when I
saw your post. I've just finished upgrading to Lucid and will now try to
rebuild Wine packages from the PPA source since the Wine PPA doesn't
have support
I don't know, I still seem to be having problems with wine1.2 after
upgrading to Lucid.
fixme:mixer:ALSA_MixerInit No master control found on USB Device 0x46d:0x8c2,
disabling mixer
fixme:mixer:ALSA_MixerInit No master control found on HDA ATI HDMI, disabling
mixer
trace:d3d:DllMain WineD3D
Yeah there's quite a few
ii libdrm-intel1
2.4.17+git20100204.1802e1a4-0ubuntu0sarvatt~karmic
ii libdrm-radeon1
2.4.17+git20100204.1802e1a4-0ubuntu0sarvatt~karmic
ii libdrm2
That totally cleaned up my machine and Wine now returns the expected
glinfo values. Thank you very much!
--
[xorg-edgers] after rebuilding, Wine doesn't get same results with DRI R600 as
glxinfo
https://bugs.launchpad.net/bugs/515933
You received this bug notification because you are a member
Looks like I spoke/posted too soon.
trace:wgl:X11DRV_WineGL_InitOpenglInfo GL version : 1.4 (1.5 Mesa
7.7).
trace:wgl:X11DRV_WineGL_InitOpenglInfo GL renderer: Mesa DRI R600
(RV670 9505) 20090101 TCL DRI2.
trace:wgl:X11DRV_WineGL_InitOpenglInfo GLX version:
Note that the referenced WineHQ bug report contains wine debug traces by
other users of the R600 and R300 drivers which show the correct values
for Client GLX vendor and Direct rendering enabled, but who probably
aren't running Ubuntu w/ PPA updates. So either this is a problem with
the Ubuntu PPA
Public bug reported:
Binary package hint: xorg
I'm trying to rebuild Wine to develop a patch to better handle Mesa DRI R3/600
drivers from the xorg-edgers PPA.
What happens is that the glx data Wine retrieves after recompilation doesn't
match what I see in glxinfo. For more info, see
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/38658112/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/38658116/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/38658119/Dependencies.txt
**
Architecture: amd64
DistroRelease: Ubuntu 9.10
MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7388
Package: xorg 1:7.4+3ubuntu10
PackageArchitecture: amd64
ProcCmdLine: root=/dev/mapper/Raid1Group-RootVol ro quiet splash
ProcEnviron:
SHELL=/bin/bash
LANG=en_CA.UTF-8
ProcVersionSignature:
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/37401984/BootDmesg.txt
--
Can't VSYNC properly on ATI (Mobility Radeon HD 2600 XT)
https://bugs.launchpad.net/bugs/214154
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: CurrentDmesg.gz
http://launchpadlibrarian.net/37401988/CurrentDmesg.gz
--
Can't VSYNC properly on ATI (Mobility Radeon HD 2600 XT)
https://bugs.launchpad.net/bugs/214154
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/37401989/Dependencies.txt
--
Can't VSYNC properly on ATI (Mobility Radeon HD 2600 XT)
https://bugs.launchpad.net/bugs/214154
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: Lspci.txt
http://launchpadlibrarian.net/37401995/Lspci.txt
--
Can't VSYNC properly on ATI (Mobility Radeon HD 2600 XT)
https://bugs.launchpad.net/bugs/214154
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: PciDisplay.txt
http://launchpadlibrarian.net/37402000/PciDisplay.txt
--
Can't VSYNC properly on ATI (Mobility Radeon HD 2600 XT)
https://bugs.launchpad.net/bugs/214154
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: Lsusb.txt
http://launchpadlibrarian.net/37401996/Lsusb.txt
--
Can't VSYNC properly on ATI (Mobility Radeon HD 2600 XT)
https://bugs.launchpad.net/bugs/214154
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: XorgConf.txt
http://launchpadlibrarian.net/37402020/XorgConf.txt
--
Can't VSYNC properly on ATI (Mobility Radeon HD 2600 XT)
https://bugs.launchpad.net/bugs/214154
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: XorgLog.txt
http://launchpadlibrarian.net/37402025/XorgLog.txt
--
Can't VSYNC properly on ATI (Mobility Radeon HD 2600 XT)
https://bugs.launchpad.net/bugs/214154
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: ProcCpuinfo.txt
http://launchpadlibrarian.net/37402004/ProcCpuinfo.txt
--
Can't VSYNC properly on ATI (Mobility Radeon HD 2600 XT)
https://bugs.launchpad.net/bugs/214154
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: ProcModules.txt
http://launchpadlibrarian.net/37402010/ProcModules.txt
--
Can't VSYNC properly on ATI (Mobility Radeon HD 2600 XT)
https://bugs.launchpad.net/bugs/214154
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: ProcInterrupts.txt
http://launchpadlibrarian.net/37402008/ProcInterrupts.txt
--
Can't VSYNC properly on ATI (Mobility Radeon HD 2600 XT)
https://bugs.launchpad.net/bugs/214154
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: Xrandr.txt
http://launchpadlibrarian.net/37402028/Xrandr.txt
--
Can't VSYNC properly on ATI (Mobility Radeon HD 2600 XT)
https://bugs.launchpad.net/bugs/214154
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: UdevDb.txt
http://launchpadlibrarian.net/37402011/UdevDb.txt
--
Can't VSYNC properly on ATI (Mobility Radeon HD 2600 XT)
https://bugs.launchpad.net/bugs/214154
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/37402030/XsessionErrors.txt
--
Can't VSYNC properly on ATI (Mobility Radeon HD 2600 XT)
https://bugs.launchpad.net/bugs/214154
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: glxinfo.txt
http://launchpadlibrarian.net/37402031/glxinfo.txt
--
Can't VSYNC properly on ATI (Mobility Radeon HD 2600 XT)
https://bugs.launchpad.net/bugs/214154
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: setxkbmap.txt
http://launchpadlibrarian.net/37402036/setxkbmap.txt
--
Can't VSYNC properly on ATI (Mobility Radeon HD 2600 XT)
https://bugs.launchpad.net/bugs/214154
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: xdpyinfo.txt
http://launchpadlibrarian.net/37402042/xdpyinfo.txt
--
Can't VSYNC properly on ATI (Mobility Radeon HD 2600 XT)
https://bugs.launchpad.net/bugs/214154
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: xkbcomp.txt
http://launchpadlibrarian.net/37402043/xkbcomp.txt
--
Can't VSYNC properly on ATI (Mobility Radeon HD 2600 XT)
https://bugs.launchpad.net/bugs/214154
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: UdevLog.txt
http://launchpadlibrarian.net/37402019/UdevLog.txt
--
Can't VSYNC properly on ATI (Mobility Radeon HD 2600 XT)
https://bugs.launchpad.net/bugs/214154
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: monitors.xml.txt
http://launchpadlibrarian.net/37402035/monitors.xml.txt
--
Can't VSYNC properly on ATI (Mobility Radeon HD 2600 XT)
https://bugs.launchpad.net/bugs/214154
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
49 matches
Mail list logo
