After deleting the .Xauthority file, I can now successfully log into a
Unity session.
The problem seems to be gone (rebooting worked fine after this). Maybe
somebody can figure out how I got into this situation, but otherwise the
bug can be closed as far as I'm concerned.
--
You received this
If I *remove* xserver-xorg-video-intel, lightdm is able to show me the
login screen. However, there is corruption on the screen and trying to
log into a Unity or Gnome session just shows a blank screen and then
puts me back into the login screen after 1 second.
--
You received this bug
Public bug reported:
After updating from 16.04 to 16.10, lightdm doesn't start.
Adding 'nomodeset' for booting allows it to start, but apparently lacks
all acceleration.
Trying different kernels doesn't help, including the one from 16.04.
Sorry for brevity, I'm writing this on my phone...
99,9% sure that the problem is a material one, since my graphic card is
not supported by any Linux distribution.I will not do any additionnal test and
I will install a new graphic card soon.
Thanks
Remi
Le lundi 23 février 2015 23h26, Christopher M. Penalver
christopher.m.penal
with Linux and I asked for help on a french
forum since this is my native language.
Remi
Le mardi 24 février 2015 7h15, Christopher M. Penalver
christopher.m.penal...@gmail.com a écrit :
Remi, as per http://xorg.freedesktop.org/wiki/RadeonFeature/ there is no
indication your card
Swâmi,
We've all laid out these arguments many times over. Yes, this issue is
frustrating (and I regret having vented some of my own frustration in my
first comments) but let's keep it civil.
There are proposed solutions. I, for one, think Andreas' proposal is the
best way out of the current
Swâmi,
We've all laid out these arguments many times over. Yes, this issue is
frustrating (and I regret having vented some of my own frustration in my
first comments) but let's keep it civil.
There are proposed solutions. I, for one, think Andreas' proposal is the
best way out of the current
Nicolas,
Where does the need to *have* a key for nbsp come from? Isn't a compose
combo more appropriate and less error-prone?
Cheers
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
Nicolas,
Where does the need to *have* a key for nbsp come from? Isn't a compose
combo more appropriate and less error-prone?
Cheers
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
I'm at a loss as to what to do to help find a solution for everyone.
fr-oss is a great layout with many useful improvements over fr-latin9,
but the missing ControlR is a deal breaker. I'm personally back to using
the default fr layout and I'll advise users to do the same if they
want their
I'm at a loss as to what to do to help find a solution for everyone.
fr-oss is a great layout with many useful improvements over fr-latin9,
but the missing ControlR is a deal breaker. I'm personally back to using
the default fr layout and I'll advise users to do the same if they
want their
Public bug reported:
I regularly lost image on my screen. This happen instantly and I believe this
is a graphic card issue with Ubuntu since it work correctly with Windows.
I get stuck with vertical lines grey/blue screen image and the only solution
is to restart the computer. No more icons,
(In reply to comment #60)
Gentlemen, I am really stuck at that point.
Allow me to sum it up.
- Nicolas is the sole advocate of having Control_R mapped to Level5.
- The rest of us want to go back to having both left and right Control
behaving the same way.
I'm not quite sure how you want us
(In reply to comment #60)
Gentlemen, I am really stuck at that point.
Allow me to sum it up.
- Nicolas is the sole advocate of having Control_R mapped to Level5.
- The rest of us want to go back to having both left and right Control
behaving the same way.
I'm not quite sure how you want us
For some reason, I found myself using the 'fr oss' layout in Gnome 3.10.
And I must say that finding out that this layout was picked as the
default left me speechless: two keys on my keyboard no longer behave
according to what's *on* the actual key:
- the right control key, which just says Ctrl,
For some reason, I found myself using the 'fr oss' layout in Gnome 3.10.
And I must say that finding out that this layout was picked as the
default left me speechless: two keys on my keyboard no longer behave
according to what's *on* the actual key:
- the right control key, which just says Ctrl,
Never mind
sudo apt-get update sudo apt-get upgrade
did work for me
--
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/259219
Title:
Broken TLS support in libGL.so AKA: software-center crashed
Updating does not fixes this here, Maverick meerkat
--
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/259219
Title:
Broken TLS support in libGL.so AKA: software-center crashed with
SIGSEGV in
More information:
If Vsync is enabled in Catalyst control centre, and gl video output is
used, then video does not tear, *as long as desktop effects are not
enabled*. It appears as though compiz prevents vsync from working. I
don't know if this bug should be filed against compiz, or remain with
I can confirm that XV output in karmic and flgrx still tears. I can use
gl output, but that corrupts the video in interesting ways when using
Compiz (seems to work well without compiz). However, if not using
Compiz, I get perfect XV video output with the open source drivers.
--
[RV730XT]
20 matches
Mail list logo
