Looks right to me, we'll have to see what the xkeyboard-config folks say.
-alan-
On 10/ 5/16 09:55 AM, JC Ahangama wrote:
Mr. Coopersmith,
Did I do it right this time, please?
https://bugs.freedesktop.org/show_bug.cgi?id=98098
I appreciate your nudging me along the right path.
Regar
Anteja Vuk Macek composed on 2016-10-05 14:30 (UTC+0200):
I can't use Xorg 1.13.x because for make Fedora 18 MR2 I need to use Xorg
1.14.5 ...
For now I remove Xorg 1.13.x, and install Xorg 1.14.5, before I use both of
Xorg ( 1.13.3-3 and 1.14.5 ).
With new Xorg I can't start command startx.
Hi,
I can't use Xorg 1.13.x because for make Fedora 18 MR2 I need to use Xorg
1.14.5 ...
For now I remove Xorg 1.13.x, and install Xorg 1.14.5, before I use both of
Xorg ( 1.13.3-3 and 1.14.5 ).
With new Xorg I can't start command startx.
Best regards,
Anteja Vuk - Macek
Software Engineer
Dol
On Thu, Oct 06, 2016 at 12:31:59AM +0530, jeetu.gol...@gmail.com wrote:
Can you think of something else we can try so we can further pinpoint
where the problem lies or any thoughts at all on the above?
Only more wild guesses, maybe input/event handling?
GTK_IM_MODULE=xim GDK_CORE_DEVICE_EVENTS
jeetu.gol...@gmail.com composed on 2016-10-06 00:31 (UTC+0530):
Can you think of something else we can try so we can further pinpoint
where the problem lies or any thoughts at all on the above?
Try a substantially different environment, one without GDM, and as little of
GTK as possible (QT-ba
Hi Thomas,
I had the opportunity to run more tests based on your suggestion. The
following are my findings :
-
LIBGL_ALWAYS_INDIRECT=1
LIBGL_ALWAYS_SOFTWARE=1
LIBGL_DRI3_DISABLE=1
These environment variables do not seem to have made any difference. I
was still getting the desktop freeze with th
Mr. Coopersmith,
Did I do it right this time, please?
https://bugs.freedesktop.org/show_bug.cgi?id=98098
I appreciate your nudging me along the right path.
Regards,
JC
On 10/5/2016 10:17 AM, JC Ahangama wrote:
Thank you ever so much, Alan.
I am reading them.
JC
On 10/5/2016 9:37 AM, Al
Thank you ever so much, Alan.
I am reading them.
JC
On 10/5/2016 9:37 AM, Alan Coopersmith wrote:
You are still not sending it to the right place - the XKB keymaps are
maintained by the Xkeyboard-config project, which has it's own mailing
lists, bug trackers, etc.
See https://www.freedesktop.
On Wed, 2016-10-05 at 11:48 +0900, Ashe Goulding wrote:
> Is it safe to regard it as const char?
Yes. libX11 predates the wide availability of C89, so it tends not to
include things like 'const' in function signatures.
- ajax
___
xorg@lists.x.org: X.Org
Hi,
I'm going to say to file a bug in bugzilla when I found this link
https://www.freedesktop.org/wiki/Software/XKeyboardConfig/Rules/
https://bugs.freedesktop.org/enter_bug.cgi?product=xkeyboard-config
Using bugzilla, you will contact directly the maintainers and also your
request won't be lo
You are still not sending it to the right place - the XKB keymaps are
maintained by the Xkeyboard-config project, which has it's own mailing
lists, bug trackers, etc.
See https://www.freedesktop.org/wiki/Software/XKeyboardConfig/ and
https://www.freedesktop.org/wiki/Software/XKeyboardConfig/Devel
Hi,
To take a pure stab at this, not only ( probably ) does the open driver
NOT support that one in older kernels ( binary blobs etc etc ). I wonder
if something internal in the Kernel is needed also ( dependency ) for the
Nvidia driver should you go that route.
Regards
On Wed, Oct 5, 2016 a
On 10/ 4/16 07:48 PM, Ashe Goulding wrote:
Is it safe to regard it as const char?
Since it's declared as const char, yes:
#ifndef _Xconst
#define _Xconst const
#endif /* _Xconst */
extern Display *XOpenDisplay(
_Xconst char* /* display_name */
);
(The ifdef used to be much more com
I've tried exploring this on forums and such without answer. I can't find a
reason why my 980 GTX will work on Fedora but not Ubuntu or Linux Mint. The
major difference I spot is a kernel version difference?
Currently running mint w/o my 980
ZG Wolfe
On Wed, Oct 5, 2016 at 7:54 AM, John Lewis wrote:
> On 10/05/2016 03:08 AM, Michel Dänzer wrote:
>> On 04/10/16 09:40 PM, John Lewis wrote:
>>> It was the R7 360 that was causing the issue. Dual screens work just
>>> fine with Intel HD Graphics 4000.
>> Please attach the Xorg log file correspondin
I am repeating my request that I obviously did not send to the right place.
Please implement the following change to the
xkb_symbols "us" variant in the symbols/lk file. Thank you:
REPLACE these two rows:
key { [ d, D, q ] }; key { [ eth, ETH, VoidSymbol ] };
WITH these two: key { [ eth, ET
On 10/05/2016 03:08 AM, Michel Dänzer wrote:
> On 04/10/16 09:40 PM, John Lewis wrote:
>> It was the R7 360 that was causing the issue. Dual screens work just
>> fine with Intel HD Graphics 4000.
> Please attach the Xorg log file corresponding to the problem with the
> Radeon GPU.
>
>
It is now enc
Is it safe to regard it as const char?
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s
Hi,
I know that Fedora 18 is old, but only for fedora 18 intel has ISP driver.
Could you told me if is configuration is ok?
Best regards,
Teja
On Wed, Oct 5, 2016 at 8:46 AM, Olivier Fourdan wrote:
> Hi,
>
> On 4 October 2016 at 12:56, Anteja Vuk Macek
> wrote:
> > I try to install Fedora 18
Hi
On 5 October 2016 at 08:56, Anteja Vuk Macek wrote:
> I know that Fedora 18 is old, but only for fedora 18 intel has ISP driver.
Right, but my point was that you may want to use Xorg which ships with
Fedora 18 (iirc, Fedora 18 ships with Xorg 1.13.x) rather than
building your own.
> Could yo
On 04/10/16 09:40 PM, John Lewis wrote:
> It was the R7 360 that was causing the issue. Dual screens work just
> fine with Intel HD Graphics 4000.
Please attach the Xorg log file corresponding to the problem with the
Radeon GPU.
--
Earthling Michel Dänzer | http://www
21 matches
Mail list logo
