More on this, adding to my comment above... My computer ceases its
ability to suspend again, without any updated etc. There was a notice
that a program had crashed yesterday evening, but the computer suspended
fine. This morning I noticed there was no sound (the speaker icon was
red in kubuntu 1
This occured to me today, seemingly after no update for changes made to
my laptop. I fixed in in the following way. Hope this helps
someone...
What did not work: Running the latest update, installing kernel 4.8.x or
4.4.25, or any of the fixes you can find doing a google search for
kubuntu 16.0
This is a continuing problem for me too. Every restart I have to
reschedule gnome-settings-daemon to "idle" or it grinds my system to a
halt on start-up for minutes on end.
In-case it helps someone else, I do the following:
$ ps -A|grep gnome-settings-daemon
- This will give you it's PID
$ ioni
I'm in the middle of experiencing exactly the same problem. To answer
Pedro's questions I can provide the following information:
1. the specific steps or actions you took that caused you to encounter the
problem.
Upgrading from karmic to lucid. Manually changed all occurrences of karmic to
lucid
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/26060618/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/26060619/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/26060620/ProcStatus.txt
--
Dead m
Public bug reported:
I have a monitor (VGA with a DVI converter) and a TV (DVI to HDMI)
connected to ubuntu.
When I move the mouse from the monitor to the TV (for instance) a dead
version of the cursor will remain on screen, roughly either a scroll bar
or half a scroll bar's distance from the edg
Just posting to confirm the same issue as reported on a Toshiba Pro U300
series (and the ctrl-alt-f1/ctrl-alt-f7 workaround does bring things
back)
--
Volume control wheel on laptop is sticking in ubuntu
https://bugs.launchpad.net/bugs/271706
You received this bug notification because you are a m
So far so good without the DVI cable plugged in. It's another LG
monitor, 22" and can handle different resolutions - like I said it's
actually been used in either gutsy or hardy yet - although it's been
plugged in for ages and made no difference in gutsy.
--
Intermittent "out of range" error, Ra
OK. Just got the same error with the minimal xorg.conf. I've now
unplugged the DVI cable so will see how it goes like that.
--
Intermittent "out of range" error, Radeon
https://bugs.launchpad.net/bugs/248430
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Hi Tormod,
Not been enough time yet to see if I get the 'out of range' error with
this specific config - it's usually once or twice a day so post back
if/when I get one.
I'll look to see if there's a gutsy log around. I have a monitor plugged
into the DVI port, but it's not configured or set up,
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/16193514/Xorg.0.log
--
Intermittent "out of range" error, Radeon
https://bugs.launchpad.net/bugs/248430
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
Ok back to a minimal xorg.conf, here's the xrandr output and log.
** Attachment added: "xrandr.txt"
http://launchpadlibrarian.net/16193511/xrandr.txt
--
Intermittent "out of range" error, Radeon
https://bugs.launchpad.net/bugs/248430
You received this bug notification because you are a member
And xorg.conf
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/16190985/xorg.conf
--
Intermittent "out of range" error, Radeon
https://bugs.launchpad.net/bugs/248430
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
Here's xrandr.
** Attachment added: "xrandr.txt"
http://launchpadlibrarian.net/16190982/xrandr.txt
--
Intermittent "out of range" error, Radeon
https://bugs.launchpad.net/bugs/248430
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Just had the out of range error with ModeDebug still on, so here's a log
from just now. Not sure if it's any help but can't hurt.
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/16190026/Xorg.0.log
--
Intermittent "out of range" error, Radeon
https://bugs.launchpad.net/bugs/24
Here's the xorg.conf with ModeDebug enabled.
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/16185799/Xorg.0.log
--
Intermittent "out of range" error, Radeon
https://bugs.launchpad.net/bugs/248430
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Worth adding there's an existing issue open for Radeon 9200/ATI/AGP
breakage over at https://bugs.launchpad.net/xorg-server/+bug/139210.
afaik it's a completely separate issue to this "out of range" error -
I've just subscribed over there and updated the issue.
Although it's intermittent, it seems
I can confirm this bug on an ATI Radeon 9200 - I had it in Gutsy, and
it's been exactly the same in Hardy. On booting up, the login screen is
distorted with only the cursor available.
As with others, adding Option "AGPMode" "4" to xorg.conf
allows X to work properly again.
--
ATI Radeon 9200 cra
Thanks again. Attached that too.
** Attachment added: "apt-cache_policy.txt"
http://launchpadlibrarian.net/16147648/apt-cache_policy.txt
--
Intermittent "out of range" error, Radeon
https://bugs.launchpad.net/bugs/248430
You received this bug notification because you are a member of Ubuntu
Bu
** Attachment added: "Xorg.0.log.old"
http://launchpadlibrarian.net/16147327/Xorg.0.log.old
--
Intermittent "out of range" error, Radeon
https://bugs.launchpad.net/bugs/248430
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/16147325/Xorg.0.log
--
Intermittent "out of range" error, Radeon
https://bugs.launchpad.net/bugs/248430
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
** Attachment added: "discover.txt"
http://launchpadlibrarian.net/16147320/discover.txt
--
Intermittent "out of range" error, Radeon
https://bugs.launchpad.net/bugs/248430
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
** Attachment added: "lspci.txt"
http://launchpadlibrarian.net/16147314/lspci.txt
--
Intermittent "out of range" error, Radeon
https://bugs.launchpad.net/bugs/248430
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
** Attachment added: "uname -a"
http://launchpadlibrarian.net/16147304/uname.txt
--
Intermittent "out of range" error, Radeon
https://bugs.launchpad.net/bugs/248430
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
I wasn't sure whether to put it as an autoconfiguration bug or the
driver, thanks for doing so.
I've attached the last two Xorg.log and the debugging information as
separate attachments. I should note that running with no xorg.conf (or
the one generated from dpkg-reconfigure xserver-xorg) gives me
Public bug reported:
Since upgrading to Hardy 8.04 I've been getting intermittent 'out of
range 17.3 / 16hz' errors on my LG Flatron L1915S. I can boot into X
fine, but every so often the monitor will show this error, then I have
to crash out of X (ctrl-tab-backspace) and login again. This happens
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/16015421/xorg.conf
--
Intermittent "out of range" error, Radeon
https://bugs.launchpad.net/bugs/248430
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
I get periodic black screens (out of range), and of course have the same
issue that dpkg-reconfigure xserver-xorg (and displayconfig-gtk) don't
allow me to reset in any sensible way, nor does my old gutsy xorg.conf
help. Having done a lot of searching for this particular bug, I can
confirm it's lea
28 matches
Mail list logo
