This is a support request, and thusly does not need to be filed as a
separate bug report.
** Changed in: xorg (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
This is also just a support request and does not need to be filed as a
bug. If you need technical assistance, please ask a new question using
the following link https://answers.launchpad.net/ubuntu/+addquestion.
** Changed in: xorg (Ubuntu)
Status: New = Invalid
--
You received this bug
I'm ever so slightly confused. What exactly is the issue and why might
xorg be the cause?
** Changed in: xorg (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Please add a description detailing the issue you are running into. After
doing that, set the bug status here back to new.
** Changed in: xorg (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in
Please attempt to add some information as to what happened to prompt you
to report this bug. After adding some background information, set the
status here back to new.
** Changed in: xorg (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of
This may be an X issue, or may be a kernel issue. After waking from
suspend, ssh into the affected machine and run sudo service lightdm
stop if the screen lights back up after killing LightDM the issue
probably lies in Xorg, where if the screen remains dark after killing
LightDM it's probably a
It seems like the inability to turn off your system from the cog in the
right corner is probably unrelated to cairo-dock. All of this is
completely unrelated to xorg, hence changing this over to cairo-dock.
** Package changed: xorg (Ubuntu) = cairo-dock (Ubuntu)
--
You received this bug
There might be a few things going on here, this is a bit of a guess.
Reassign if needed.
** Package changed: xorg (Ubuntu) = gnome-session (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information.
At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the
problem,
2.
*** This bug is a duplicate of bug 1275212 ***
https://bugs.launchpad.net/bugs/1275212
** This bug has been marked a duplicate of bug 1275212
NOT SURE
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
*** This bug is a duplicate of bug 1272975 ***
https://bugs.launchpad.net/bugs/1272975
** This bug has been marked a duplicate of bug 1272975
blak screen after lgin
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
** Summary changed:
- blak screen after lgin
+ black screen after login
--
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/1272975
Title:
black screen after login
To manage notifications about
** Summary changed:
- Screen lightness to high
+ Brightness settings aren't retained on reboot
--
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/1272913
Title:
Brightness settings aren't retained
Execute sudo apt-get update and then sudo apt-get upgrade --fix-
missing. Let us know if this impacts your issue in any way.
** Package changed: xorg (Ubuntu) = apt (Ubuntu)
** Changed in: apt (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1223199 ***
https://bugs.launchpad.net/bugs/1223199
** This bug has been marked a duplicate of bug 1223199
libegl1-mesa-dev should not depend on libmirclient-dev
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** Package changed: xorg (Ubuntu) = ubuntu
--
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/1257525
Title:
network
To manage notifications about this bug go to:
Potentially this ties in with bug #1252843.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server-lts-raring in Ubuntu.
https://bugs.launchpad.net/bugs/1246384
Title:
xserver-common-lts-raring does not always get correctly removed.
To
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/1246203
Title:
Mouse pointer does not appear
*** This bug is a duplicate of bug 1247424 ***
https://bugs.launchpad.net/bugs/1247424
** This bug has been marked a duplicate of bug 1247424
Dual monitor nightmare :)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Opening duplicate reports will not lead to a resolution of you issue any
faster than opening one report will.
Quinn Balazs
--
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/1247424
Title:
Dual
*** This bug is a duplicate of bug 1247424 ***
https://bugs.launchpad.net/bugs/1247424
** This bug has been marked a duplicate of bug 1247424
Dual monitor nightmare :)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Bluez handles the detection of USB devices. Since the cursor moves (even
though it is not displayed), the detection seems to have happened fine.
The actual displaying/functionality of the mouse is handled by X, in
particular xserver-xorg-input-evdev.
Please collect logs for this report using
. It would also be helpful if you could tell us what the
text of the X error that you experienced was, as that will make it
easier to tell if we are targeting Cinnamon or X in this issue.
Thanks,
Quinn Balazs
--
You received this bug notification because you are a member of Ubuntu-X,
which
Let's target xorg-server to start with. In addition to the logs from
xorg-server, please upload the logs contained in /var/log/lightdm.
Collecting the xorg-server logs should be as easy as running apport-
collect 1245474.
** Package changed: ubuntu = xorg-server (Ubuntu)
** Changed in:
** Tags removed: regression
** Tags added: regression-release
** Changed in: xorg-server (Ubuntu)
Status: Incomplete = New
** Changed in: xorg-server (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
It would make it easier if you detailed the text of the error.
Thanks,
Quinn Balazs
** Changed in: xorg (Ubuntu)
Status: New = Incomplete
--
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
Also, is this with Cinnamon Version 1.7.4-2ubuntu4, or with a version
found in the PPA?
--
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/1245730
Title:
just installed ubuntu and found this.
To
This was probably done with some purpose, but I don't know what the
rational for this change would have been.
** Package changed: ubuntu = xkeyboard-config (Ubuntu)
** Changed in: xkeyboard-config (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a
This isn't a LightDM issue. LightDM only deals with the login
environment. Please use apport collect bug# in order to get relevant
logs attached here.
Quinn Balazs
** Changed in: ubuntu
Status: New = Incomplete
** Package changed: ubuntu = xorg-server (Ubuntu)
--
You received this bug
Would you mind getting a screen grab of this issue the next time it
happens, and posting it here as an attachment?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1233737
Is this a request to add a better explained message for when the system
partition is full?
--
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/1232220
Title:
Xorg do not start, but the system
Can't help if you don't explain what the problem is. Add some detail to
the extent of: What happened, what was expected to happen, what you were
doing when it happened, and then we can attempt to help you.
** Changed in: xorg (Ubuntu)
Status: New = Incomplete
--
You received this bug
Which build of Saucy was this issue found in? (beta-1, or one of the
daily builds)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1228506
Title:
Frequent display artifacts,
On what basis was this determined to be an X issue?
--
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/1226091
Title:
irregular crash
To manage notifications about this bug go to:
IvyBridge came out that also fixed GPU
hangs. Wheter or not this is helpful, I hope this gets resolved quickly,
as it does unfortunately make the device a pain in the ass to use.
~Quinn Balazs
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg
If suspend fixes it, then it would seem that it is a kernel issue. Would
you mind booting into the latest Mainline Build of the kernel, as that
will verify that it is the root cause. Instructions on how to boot into
the mainline build can be found here
I have a few questions and a couple suggestions. First, are you using
fglrx, or the open source radeon driver? Would you mind attaching the
output of the following dmesg | egrep 'drm|radeon' Generally issues
like these are caused by broken/misloaded drivers. Also it would be
interesting to see if
Could you add what sort of a problem you encountered?
** Changed in: xorg (Ubuntu)
Status: New = Incomplete
--
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/1222845
Title:
I dont know
To
You've given all of the relevant information. Let us know if the fresh
install works for you. If it doesn't then we will take a more earnest
look into what might be going on.
Quinn Balazs
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg
information would expedite the process as some possibilities
could be ruled out.
~Quinn Balazs
** Changed in: xorg (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https
** Package changed: xorg (Ubuntu) = nvidia-graphics-drivers (Ubuntu)
--
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/1216902
Title:
system freezes
To manage notifications
This isn't the first issue with Xorg freezes using version 304.88 of the
nvidia driver, however there is a newer version out (310.19) that may
solve the problem, as it seems that a fix for this was released from
what I can tell. Use the following to ensure it gets loaded properly:
Execute the
** Changed in: xorg (Ubuntu)
Status: Incomplete = New
--
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/1211207
Title:
Keyboard and Mouse stop working after undefined time
To manage
was not specified. The next thing to look at would be
why it's doing this after a period of time. I am working on that and
will get back to you once I've figured out what particularly is to fault
with the devices are refreshing themselves and having to be reloaded.
Quinn Balazs
** Changed
Before trying this, attempt to switch to a virtual terminal using the
frozen keyboard on the off chance that that hotkey combo still is
received. If that works just execute the commands there, but if not you
will have to do the following:
They will not contain relevant information after reboot,
Also, just as something that I noticed looking over the logs that you
already provided, is there an integrated keyboard and touchpad included
with the machine? And if there is, do those cease functioning when the
USB keyboard and mouse do. It does however look like everything is
normally detected
** Summary changed:
- Crashes
+ Unity and Gnome-Shell often crash during graphics intensive activity (e.g.
streaming video or playing games)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
give enough information for the problem to be weeded
out.
As always, If you have any issues with these directions, feel free to
contact me through launchpad, or ask for help in irc at either #ubuntu-
bugs or #ubuntu-X
~Quinn Balazs
(also this bug is an Xorg issue and is hereby marked that way
48 matches
Mail list logo
