[Bug 438224] Re: On Logon, Claims Sound Devices Were Removed
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 stage upon exiting. Having to unplug the battery for a while is not a reasonable long term solution. -- On Logon, Claims Sound Devices Were Removed https://bugs.launchpad.net/bugs/438224 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 438224] Re: On Logon, Claims Sound Devices Were Removed
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, Claims Sound Devices Were Removed https://bugs.launchpad.net/bugs/438224 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 112238] Re: mga driver no longer will display 1600x1200
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 driver. -Carl On Mon, Jun 29, 2009 at 7:46 AM, Tormod Voldenbugpost.tor...@gmail.com wrote: The monitor is autodetected, so it does not need configuration. It seems the server discards the 1600x1200 modes even though they are reported by the monitor. -- mga driver no longer will display 1600x1200 https://bugs.launchpad.net/bugs/112238 You received this bug notification because you are a direct subscriber of the bug. --- Carl J. Nobile (Software Engineer) carl.nob...@gmail.com --- -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 112238] Re: mga driver no longer will display 1600x1200
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 generic reference. Also System Settings (KDE4) will not allow me to choose a monitor, MOF it doesn't even give me the choice anymore. -Carl On Tue, Jun 23, 2009 at 12:03 PM, Tormod Voldenbugpost.tor...@gmail.com wrote: The PPA package is actually for Jaunty, so you can try it out on the Jaunty Desktop CD. Just log out after installing the package so that X restarts. Please attach the Xorg.0.log you get in Jaunty. -- mga driver no longer will display 1600x1200 https://bugs.launchpad.net/bugs/112238 You received this bug notification because you are a direct subscriber of the bug. -- --- Carl J. Nobile (Software Engineer) carl.nob...@gmail.com --- ** Attachment added: Xorg.0.log.old.jaunty http://launchpadlibrarian.net/28485125/Xorg.0.log.old.jaunty ** Attachment added: Xorg.0.log.jaunty http://launchpadlibrarian.net/28485126/Xorg.0.log.jaunty -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 112238] Re: mga driver no longer will display 1600x1200
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 want to upgrade at this time. If there is an issue with the MGA driver I don't think it is the only issue since dropping a version of this driver that I know used to work into /usr/lib/xorg/modules/drivers/ doesn't fix the issues at all. So, this looks like there is some sort of miss match between the driver and the X server itself. -Carl On Mon, Jun 22, 2009 at 5:43 PM, Tormod Voldenbugpost.tor...@gmail.com wrote: There have been a number of fixes to the mga driver since last time we heard from you. Can you please try Jaunty, Karmic or packages from my PPA https://launchpad.net/~tormodvolden/+archive/ppa ? ** Changed in: xserver-xorg-video-mga (Ubuntu) Status: Confirmed = Incomplete ** Changed in: xserver-xorg-video-mga (Ubuntu) Assignee: (unassigned) = Tormod Volden (tormodvolden) -- mga driver no longer will display 1600x1200 https://bugs.launchpad.net/bugs/112238 You received this bug notification because you are a direct subscriber of the bug. -- --- Carl J. Nobile (Software Engineer) carl.nob...@gmail.com --- -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223502] Re: apt cron.daily script doesn't check value-existence
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 https://bugs.launchpad.net/bugs/223502 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112238] Re: mga driver no longer will display 1600x1200
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 tell me something in the X server itself has broken the MGA driver. You are right it is most likely something to do with the pixel clock of 150.00 MHz. I came to the same conclusion. -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 113444] Re: us:intl selected instead of plain us
This has been a while, I was using Feisty at the time and am now using Gutsy. I have as of yet not update to Hardy. Yes, my main point was the AMBIGUITY and for that reason alone at least a comment should be added to the screen mentioning the issue. On 4/29/08, Colin Watson [EMAIL PROTECTED] 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 in: keymapper (Ubuntu) Sourcepackagename: console-setup = keymapper -- us:intl selected instead of plain us https://bugs.launchpad.net/bugs/113444 You received this bug notification because you are a direct subscriber of the bug. ** Attachment added: unnamed http://launchpadlibrarian.net/14017750/unnamed -- us:intl selected instead of plain us https://bugs.launchpad.net/bugs/113444 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 124247] Re: Beryl no longer functions correctly with KDE
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 changed. -- Beryl no longer functions correctly with KDE https://bugs.launchpad.net/bugs/124247 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112238] Re: mga driver no longer will display 1600x1200
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 obvious to me that the driver is incorrectly comparing the available modelines to the horizontal and/or vertical frequencies. I have been able to get the monitor to work with this modeline 1680x1050 147.14 1680 1784 1968 2256 1050 1051 1054 1087 -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 124247] Beryl no longer functions correctly with KDE
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 command line then start the beryl-manager and everything would be OK, how the beryl- manager will not start no matter what I do. Without the manager beryl is somewhat uncontrollable, so I've stopped using it. I'm a Lenovo 3000 N100 laptop Centrino Duo and the 64bit kernel. I have found in general that 3D desktops work better with Gnome than with KDE. ** Affects: Ubuntu Importance: Undecided Status: New -- Beryl no longer functions correctly with KDE https://bugs.launchpad.net/bugs/124247 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91484] Re: use_rcsparse is necessary to display new cvs modules
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 differently (more likely) causing this problem. 2) The new Python code that does this when setting rcsparse = 1 is still buggy (or not completed yet) as the comments in viewcvs.conf seem to indicate when it says this feature is experimental. -- use_rcsparse is necessary to display new cvs modules https://bugs.launchpad.net/bugs/91484 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 113444] Re: Single double quotes, tildys, etc. need to type twice.
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 a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 113444] Re: Single double quotes, tildys, etc. need to type twice.
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 English character set (at least in the way it is represented in text mode) and that is where it asks if '' is present. In my original install I said yes then it told me my keyboard appeared to be us:intl (you are correct, I didn't remember properly). This time I went back and said no for the '' choice and the keyboard was determined to be us. This was definitely confusing especially for a first time Alternate CD user. I assume that the '' that is asked for is not actually what I just typed. I suppose that somehow this needs to be better explained or a different character needs to be tested to derive the correct keyboard type. OK, how do I fix this? As I mentioned above I was able to get KDE to work correctly, but am still having this issue when I go to a VT. Thanks. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 113444] Re: Single double quotes, tildys, etc. need to type twice.
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 from file `/etc/console-setup/Lat15-VGA16.psf.gz'. Setting kernel SFM. Loading 256-chars 8x16 font from file `/etc/console-setup/Lat15-VGA16.psf.gz'. Setting kernel SFM. Loading 256-chars 8x16 font from file `/etc/console-setup/Lat15-VGA16.psf.gz'. Setting kernel SFM. Loading 256-chars 8x16 font from file `/etc/console-setup/Lat15-VGA16.psf.gz'. Setting kernel SFM. Loading 256-chars 8x16 font from file `/etc/console-setup/Lat15-VGA16.psf.gz'. Setting kernel SFM. Loading 256-chars 8x16 font from file `/etc/console-setup/Lat15-VGA16.psf.gz'. Setting kernel SFM. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112733] Re: Ubuntu 7.04 X11 driver for Intel 950 GMA is incorrect in
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 worked where it didn't with the default package, but the resolution degraded to 75x59 dots per inch. I don't remember the resolution with the default driver, but it was closer to 100x100. I've been reading about these packages and the newer one is xserver- xorg-viedo-intel. -- Ubuntu 7.04 X11 driver for Intel 950 GMA is incorrect in https://bugs.launchpad.net/bugs/112733 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 113444] Re: Single double quotes, tildys, etc. need to type twice.
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 characters exist on your
keyboard and I answered no to all except the last one which was ('').
Then it said that my keyboard seems to be a 'us-en' which I thought was
correct so I never gave this another thought. I did think this to be a
little unusual since I would expect a double quote to be on almost any
keyboard. Could I have made the wrong choice here?
--
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112238] Re: mga driver no longer will display 1600x1200
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 keyboard. The only thing I can do is login from my laptop and do a (shutdown -r now) to fix it. -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 113444] Re: Single double quotes, tildys, etc. need to type twice.
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 is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 113444] Re: Single double quotes, tildys, etc. need to type twice.
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 the VT. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 113444] Re: Single double quotes, tildys, etc. need to type twice.
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107663] Re: Missing Intel Core2 CPU temperature monitor driver
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 113444] Single double quotes, tildys, etc. need to type twice.
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 installed from the alternate disk, one was 64 bit the other 32 bit. This is an example [´¨~`^]. They seem to be characters used in the Latin character sets. This happens even on virtual terminals and xterms. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 113444] Re: Single double quotes, tildys, etc. need to type twice.
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 are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 113444] Re: Single double quotes, tildys, etc. need to type twice.
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 I still have to type these chararters twice to get them. I should have mentioned that the laptop is a Lenovo. Below is the entry in both machine's my xorg.conf. Section InputDevice Identifier Generic Keyboard Driver kbd Option CoreKeyboard Option XkbRules xorg Option XkbModel pc105 Option XkbLayout us Option XkbVariantintl EndSection -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112238] Re: mga driver no longer will display 1600x1200
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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112238] Re: mga driver no longer will display 1600x1200
** 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112238] mga driver no longer will display 1600x1200
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 all the modeline statement in the xorg.conf file to let the VESA preset timing modes in my ViewSonic GS790 monitor control the modes. My video card is a MGA G400 Max (32M) duel monitor card, but I'm only using a single monitor. This always worked fine previous installs that were not Ubuntu based. The pertinent lines in my xorg.cone are below. - Section Monitor identifier GS790 vendorname ViewSonic modelname ViewSonic GS790 HorizSync 30-97 VertRefresh 50-180 #gamma 1.05 1.0 1.03 EndSection Section Screen Identifier Default Screen Device Matrox Graphics, Inc. MGA G400/G450 Monitor GS790 DefaultDepth 24 SubSection Display depth 24 modes 1600x1200 1280x1024 1024x768 800x600 640x480 EndSubSection EndSection ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67391] Re: Screensaver not working
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
[Bug 67391] Re: Screensaver not working
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. -- 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
[Bug 74450] Wireless Assistant does not connect to network properly.
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 the subnet route host and no external DNS's. When I installed the Gnome NetworkManager applet things seemed to work correctly, however I still couldn't have two networks established at the same time. Maybe because there is no way to have different networks use a different set of DNS's. Another related issue is a delay in the booting of the system. I've isolated this to the configuration of eth1 (WIFI). You will see a delay in acquiring the eth1 connection. See below: # /etc/init.d/networking restart * Reconfiguring network interfaces... There is already a pid file /var/run/dhclient.eth0.pid with pid 4319 killed old client process, removed PID file Internet Systems Consortium DHCP Client V3.0.4 Copyright 2004-2006 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/eth0/00:0f:b0:cc:2f:1d Sending on LPF/eth0/00:0f:b0:cc:2f:1d Sending on Socket/fallback DHCPRELEASE on eth0 to 192.168.1.1 port 67 There is already a pid file /var/run/dhclient.eth1.pid with pid 3561 killed old client process, removed PID file Internet Systems Consortium DHCP Client V3.0.4 Copyright 2004-2006 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/eth1/00:18:de:0c:f7:b7 Sending on LPF/eth1/00:18:de:0c:f7:b7 Sending on Socket/fallback DHCPRELEASE on eth1 to 192.168.0.1 port 67 send_packet: Network is unreachable send_packet: please consult README file regarding broadcast address. There is already a pid file /var/run/dhclient.eth0.pid with pid 134993416 Internet Systems Consortium DHCP Client V3.0.4 Copyright 2004-2006 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/eth0/00:0f:b0:cc:2f:1d Sending on LPF/eth0/00:0f:b0:cc:2f:1d Sending on Socket/fallback DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 DHCPOFFER from 192.168.1.1 DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPACK from 192.168.1.1 bound to 192.168.1.101 -- renewal in 38975 seconds. There is already a pid file /var/run/dhclient.eth1.pid with pid 134993416 Internet Systems Consortium DHCP Client V3.0.4 Copyright 2004-2006 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/eth1/00:18:de:0c:f7:b7 Sending on LPF/eth1/00:18:de:0c:f7:b7 Sending on Socket/fallback DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 13 DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15 DHCPOFFER from 192.168.0.1 DHCPREQUEST on eth1 to 255.255.255.255 port 67 DHCPACK from 192.168.0.1 SIOCADDRT: File exists bound to 192.168.0.105 -- renewal in 298169 seconds. There is already a pid file /var/run/dhclient.eth2.pid with pid 134993416 Internet Systems Consortium DHCP Client V3.0.4 Copyright 2004-2006 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ SIOCSIFADDR: No such device eth2: ERROR while getting interface flags: No such device eth2: ERROR while getting interface flags: No such device Bind socket to interface: No such device Failed to bring up eth2. There is already a pid file /var/run/dhclient.ath0.pid with pid 134993416 Internet Systems Consortium DHCP Client V3.0.4 Copyright 2004-2006 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ SIOCSIFADDR: No such device ath0: ERROR while getting interface flags: No such device ath0: ERROR while getting interface flags: No such device Bind socket to interface: No such device Failed to bring up ath0. There is already a pid file /var/run/dhclient.wlan0.pid with pid 134993416 Internet Systems Consortium DHCP Client V3.0.4 Copyright 2004-2006 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ SIOCSIFADDR: No such device wlan0: ERROR while getting interface flags: No such device wlan0: ERROR while getting interface flags: No such device Bind socket to interface: No such device Failed to bring up wlan0. # lspci 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03) 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express
[Bug 74450] Re: Wireless Assistant does not connect to network properly.
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
[Bug 67391] Re: Screensaver not working
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67391] Re: Screensaver not working
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 uninitialized input device 168 Major opcode: 145 Minor opcode: 3 Resource id: 0x0 Failed to open device X Error: BadDevice, invalid or uninitialized input device 168 Major opcode: 145 Minor opcode: 3 Resource id: 0x0 Failed to open device By-the-way, I'm using a Lenovo 3000 N100 laptop. -- 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
[Bug 67391] Re: Screensaver not working
** 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 blank screen and when the machine goes to sleep instead of a blank screen I get a black screen with a large X character on it. -- 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
[Bug 67391] Re: Screensaver not working
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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
