Mailinglist Archive: opensuse-bugs (13468 mails)
| < Previous | Next > |
[Bug 334632] New: amdcccle (ATI catalyst control center) does not start
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Wed, 17 Oct 2007 10:47:47 -0600 (MDT)
- Message-id: <bug-334632-21960@xxxxxxxxxxxxxxxxxxxxxxxxx/>
https://bugzilla.novell.com/show_bug.cgi?id=334632
Summary: amdcccle (ATI catalyst control center) does not start
Product: openSUSE 10.3
Version: Final
Platform: x86
OS/Version: openSUSE 10.3
Status: NEW
Severity: Blocker
Priority: P5 - None
Component: X11 3rd Party Driver
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: gdanov@xxxxxxxxx
QAContact: sndirsch@xxxxxxxxxx
Found By: ---
Hi,
amdccle installed from http://www2.ati.com/suse/10.3 does not start :
~>amdcccle
amdcccle: xcb_io.c:350: _XReply: Assertion `!dpy->xcb->reply_data' failed.
Aborted
Classified as Blocker as this prevents me from using Dual Head configuration on
monitors with different resolution, so I am forced to use the lowest common
resolution on both monitors.
Regards,
Georgi
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Summary: amdcccle (ATI catalyst control center) does not start
Product: openSUSE 10.3
Version: Final
Platform: x86
OS/Version: openSUSE 10.3
Status: NEW
Severity: Blocker
Priority: P5 - None
Component: X11 3rd Party Driver
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: gdanov@xxxxxxxxx
QAContact: sndirsch@xxxxxxxxxx
Found By: ---
Hi,
amdccle installed from http://www2.ati.com/suse/10.3 does not start :
~>amdcccle
amdcccle: xcb_io.c:350: _XReply: Assertion `!dpy->xcb->reply_data' failed.
Aborted
Classified as Blocker as this prevents me from using Dual Head configuration on
monitors with different resolution, so I am forced to use the lowest common
resolution on both monitors.
Regards,
Georgi
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
| < Previous | Next > |