An additional note: It seems if you remove the battery for a few hours
(the recommended 10 sec does not work) then plug it back in again
everything will work again. However, why has this started happening? I
still see a bug here somewhere. Somehow KDE or whatever is setting the
hardware in a odd
I'm having this same issue on my eeepc 900. When this happens the wifi
usually stops working also. If I boot from a USB stick everything works
fine. libpulse0 is installed, but removing it will uninstall much of
KDE, so I doubt this is a feasible option.
Any ideas of a fix here?
--
On Logon,
Yes, this fits in with my experiences. When I first had this problem I
compiled a version of the driver that I knew worked correctly on a
previous install of Linux and it still didn't work with my current
install, so I concluded that somehow the server itself was doing the
wrong thing with the MGA
Tormod,
I have attached two Xorg.0.log files the old and the current (after
installing the updated MGA driver). It still only gave me a max
resolution of 1400x1050. I have noticed in the new /etc/X11/xorg.conf
file that there ia very little and no reference to the monitor type at
all, just a
I ran Jaunty from the install CD, but did not install it, the best
resolution I could get was 1400x1050, 1600x1200 is not even shown in
the list of possible resolutions. I downloaded the package you
mentioned, but am hesitant to install it as it is for Karmic and I
have Hardy on the box and don't
As of April 24, 2009 this bug is back in Hardy, most likely a regression
issue.
/etc/cron.daily/apt:
No value set for `/system/http_proxy/use_http_proxy'
No value set for `/system/http_proxy/host'
No value set for `/system/http_proxy/port'
--
apt cron.daily script doesn't check value-existence
This is an upstream issue. Here is the URL to their bug report:
https://bugs.freedesktop.org/show_bug.cgi?id=11057
As I mentioned to them I compiled the driver that worked from a previous
release and dropped it into the /usr/lib/xorg/modules/drivers directory,
but the issue remained. This would
] wrote:
cnobile: Ah. The thing is that it wasn't actually asking about '' - it
was asking about '¨' (an umlaut/diaeresis). The intl variant of us has
that symbol, but plain us doesn't. This is still open on Hardy.
Perhaps we should avoid asking about that symbol due to ambiguity.
** Changed
As I have been keeping up with updates all along I am now suspecting
this was an update issue with a dependent package. The reason I mention
this is that I just tried Beryl after some time and it has started
working again. What package did it i don't know, but it is the only
thing(s) that have
The link below is from the Unofficial Matrox Technical Support Forum
it talks about the exact issues I'm having but with a slightly different
Matrox card and monitor.
http://matrox.tuxx-
home.at/viewtopic.php?p=1446sid=cb5daaa8024697b6e65be0be23ced93f
From looking deeper in my log file it seems
Public bug reported:
When I first installed Kubuntu Feisty the beryl-manager would load and
start beryl properly. However, if I remember correctly, there were some
updates to some beryl packages after which the beryl-manager would hang
and never start. At one point I could start beryl on the
I have had the same issues as stated above,
However, I noticed when setting_rcsparse = 1, the diffs stopped working, so it
is not as complete a fix to the problem as one might expect.
1) It looks like that either RCS changed in the way it works (not likely) or
viewcvs passes arguments
A caveat here is that the fix only worked until a reboot, it's back to what it
was before.
So I'm still looking for a permanent fix to this issue.
--
Single double quotes, tildys, etc. need to type twice.
https://bugs.launchpad.net/bugs/113444
You received this bug notification because you are
OK, I've done what you ask and I think I found the problem. At a certain
point in the detection of the keyboard layout it asks if specific
characters are present or at least accessible on your keyboard. Most of
these characters are from non-English character sets. However one key
can be in the
I had to change the command a bit, but this seems to have fixed my VT.
This is what I ran:
# setupcon --force /tmp/setupcon.out
It seems that without the --force it complains with: We are not on
the Linux console, exiting..
The results in /tmp/setupcon.out are:
Loading 256-chars 8x16 font
I'm no expert, but it seems that Ubuntu (I use kubuntu) will always
install the xserver-xorg-video-i810 package by default. I have a Lenovo
3000 N100 and the 914resolution package worked with both drivers. I also
upgraded to the xserver-xorg-viedo-intel package and found that direct
rendering
No there is no change on either machine.
However, I've been thinking. I used, as I mentioned above, the alternate
CD to install Feisty and I did the same exact things with both machines.
I found the process for determining the keyboard type to be a bit
confusing. It asks if various international
I have a related issue that may be related to the problem. After logging
out of my account the second time X crashes. This is very consistent it
always happens the 2nd time I logout of KDE. Killing X from a VT, then
switching back to the login with alt/ctl F7 locks up the display, mouse
and
I'm attaching the file.
** Attachment added: console-setup
http://librarian.launchpad.net/7678132/console-setup
--
Single double quotes, tildys, etc. need to type twice.
https://bugs.launchpad.net/bugs/113444
You received this bug notification because you are a member of Ubuntu
Bugs, which
Nope, sorry to say it's the same thing. I tried this only on my laptop
and rebooted after editing the file. My /etc/X11/xorg.conf file is still
at the old setting, but, as mentioned above, I found a fix for this.
Still there seems to be a setup bug when one first does the install for
both KDE and
Still no change, but yes u will produce ü.
--
Single double quotes, tildys, etc. need to type twice.
https://bugs.launchpad.net/bugs/113444
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Same here I'm using a Lenovo 3000 N100 duo core with the same kernel as
above.
--
Missing Intel Core2 CPU temperature monitor driver
https://bugs.launchpad.net/bugs/107663
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Public bug reported:
I have installed Feisty on two very different machines and both have the
same issues.
Many punctuation characters need to be typed twice before the appear
resulting in the correct character, but not in ASCII. This happens while
using almost any medium including this site. I
One machine is a standard US keyboard, the other is a laptop (3000
N100).
Both are set to Generic 104-key pc US English
I'm using Kubuntu not Ubuntu.
--
Single double quotes, tildys, etc. need to type twice.
https://bugs.launchpad.net/bugs/113444
You received this bug notification because you
I just tried something. I enabled in the KDE the Keyboard Layout, changed
nothing else and everything works fine when in KDE.
What is strange is that without clicking enable the grayed out keyboard
allocation was correct, just clicking it on fixed the issue in KDE.
However, when I switch to a VT
These are my files.
** Attachment added: Log file
http://librarian.launchpad.net/7560969/Xorg.0.log
--
mga driver no longer will display 1600x1200
https://bugs.launchpad.net/bugs/112238
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
** Attachment added: xorg.conf
http://librarian.launchpad.net/7560971/xorg.conf
--
mga driver no longer will display 1600x1200
https://bugs.launchpad.net/bugs/112238
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Public bug reported:
It seems that the newest xorg driver for MGA devices no longer support
1600x1200 resolution.
I've only found one place on the net that mentions this issue, they seem to
believe that it is the latest release of xorg.
I'm using Feisty on a fairly old machine.
I've removed
Has anything happened with this bug yet? I've kept my laptop updated and
nothing has come through as a fix yet.
--
Screensaver not working
https://launchpad.net/bugs/67391
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Edgy, read the 4th and other messages in this bug. This has been broken
forever. I'm a developer, so if nobody is working on this bug point me
in a direction and I'll take a look at it myself. As I intimated I don't
know this architecture at all, but I do know C and Python very well.
--
Public bug reported:
This bug happend with Kubuntu Edgy 6.10
Running on a Lenovo 3000 N100 Vender Item Code: 0768DLU
Below is a short list of my hardware using lspci
When I try to connect to a WIFI network on eth1 I loose my wired
connection. It seems the the /etc/resolv.conf gets modified with
This may be related to bug #62452 I also use the ipw3945 driver.
--
Wireless Assistant does not connect to network properly.
https://launchpad.net/bugs/74450
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
In my case this did nothing. I've had the monitor power saving on all
along. Also commenting out the wacom entries from /etc/X11/xorg.conf
caused me not to boot into X at all, so I put them back.
--
Screensaver not working
https://launchpad.net/bugs/67391
--
ubuntu-bugs mailing list
Confirmed, if you kill kdesktop then restart it the screensaver begins
to work. I found I had to put a sleep between the kill and restart like
this: killall kdesktop;sleep 1;kdesktop
The restart also gave me these errors which may or may not have any
significance:
X Error: BadDevice, invalid or
** Description changed:
Binary package hint: kubuntu-desktop
Kubuntu Dapper 6.0.6
KDE 3.5.5
- Since I upgraded to KDE 3.5.5 the screensaver stoped working normally.
+ Since I upgraded to KDE 3.5.5 the screensaver stopped working normally.
Instead of a chosen screensaver I get a
I have the exact same issue with KDE 3.5.5 on Kubuntu Edgy. I only get
the big X on occasion, most of the time the screen is just blank. It
seems some of the screensavers will display the X and some the blank
screen.
--
Screensaver not working
https://launchpad.net/bugs/67391
--
ubuntu-bugs
36 matches
Mail list logo
