[Bug 865567] Re: ubuntuone-client-gnome needs to install gsettings schemas
Again here was the same, removing nautilus-open-terminal fixed for me as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/865567 Title: ubuntuone-client-gnome needs to install gsettings schemas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntuone-client-gnome/+bug/865567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 563878] Re: Ubuntu splashscreen big and ugly after installing ATI/nVidia proprietary graphics driver
** Changed in: plymouth (Ubuntu) Status: Triaged = Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/563878 Title: Ubuntu splashscreen big and ugly after installing ATI/nVidia proprietary graphics driver -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315947] Re: forcedeth NIC fails to operate
I found this when trying to figure out why my dual-boot win7 and ubuntu 10.10 machine kept failing to acquire DHCP from my router. http://forums.fedoraforum.org/showthread.php?t=240880 Scroll down to post #3 to get the fix he used. Here is a brief on it. Basically the person had the same issues I had. Dual booting win7 and Linux (most likely any distro), and almost randomly switching between the two OS's would cause a DHCP failure in usually the linux install but less frequently the Win7 install. The firmware is all there, the drivers, et al. The NIC (s) would be recognized and functioning, but it would fail to register itself with a DNS lookup with a DHCP server. He found 2 issues . From the post: I've managed to sort the problem after a bit of playing with both Linux and the CentOS server. For anyone looking for a solution to the same problem, it was down to two separate faults: 1) The Linux installations (both Ubuntu 9.10 and Fedora 12) needed to have the DHCP client ID field set to the NICs MAC address - this is within the eth0 IPv4 panel of Network Manager. This allows the DHCP clients to appear to be as the same machine to the server, as Windows sends this DHCP uuid to the server by default. 2) There was also a mis-configuration of the DNS zone files, with the trailing dot being left off on the reverse lookup zone, so it might have been unrelated but it could have contributed to the overall not-working- ness of the server. After refreshing the DHCP lease caches on both the server and the clients, all three OSes on the PC are now assigned the same IP. This problem can really only occur on machines multi-booting, but it could be useful nonetheless Thanks I have been using this with no issues for two days now. Hope this helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/315947 Title: forcedeth NIC fails to operate -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 563878] Re: Ubuntu splashscreen big and ugly after installing ATI/nVidia proprietary graphics driver
In response to #116: Microsoft charges you $200 and up for a full version of Windows 7, they do not run an X-server environment but rather have direct input and cooperation with the drivers and their respective manufacturers. They don't run a X server because they have full on mutual cooperation from hardware vendors. Linux on the other hand (at this point in time) is not granted full on access to the code by the vendors for their drivers. All open source linux drivers are reverse engineered and being that windows holds the lions share of the market and has the most money, and most games are written to run in windows using their mutual windows and hardware vendors directx API and drivers, this is going to have problems no matter what. All all video card hardware is designed to use DirectX, thats where the games and entertainment money is, all use of Open GL and X-Server functionality is an afterthought at best and often times not even addressed at all (ATI until recently). They do not write Linux drivers well, nor do they care to try very hard, because: 1. No money in games for linux. No gamers money, no need for the expensive gaming hardware with 1 gig of gddr3 memory. 2. In their minds (business men) there is no protection for their intellectual property if the drivers and firmware are freely shared. 3. Microsoft wouldn't like their API technology freely shared with a free and faster alternative OS. And that again besides illegal, would cut into microsoft market and money. The drivers for the hardware vendors like ATI and Nvidia are closed source. Meaning they do not share code openly and freely with anyone they do not have a deal with. Linux by its very nature will not make any such deal because it goes against the very principles it adheres to. And even if they would they couldn't. Microsoft wouldn't allow it and further the costs would make linux no longer free. The only reason we get any proprietary drivers from ATI and Nvidia is by their good graces and only as an appeasement to satisfy their customers wanting to use linux. They don't write drivers for big servers and infrastructure appliances running a linux kernel, they don't want or need a fancy new video card to run a game. SO any and all 3d functionality is a waste. They write those drivers for the people who play the games, games written to run in windows. And when they feel like it they throw the linux people a bone. Ubuntu had NO way to know ahead of time about an issue with a closed source driver. To say it was their fault because windows doesn't have an issue with a driver written to run hardware specifically designed to their OS, is an unfair claim to say the least. As far as Ubuntu not looking professional, they manage to take a bit of an unstable branch of Debian (not a very desktop centric Disto at all) and not only make it as stable as any other distro if not more so, but at the same time manage to make it as user friendly to an average person as any distro ever. They do this and make it attractive to look at, package it nicely, make it easy for anyone with an internet connection to find and get a copy, and at the same time maintain several different styles of desktops, and different versions supporting all kinds of hardware, all of this and it costs us nothing to use... Microsoft with infinite resources and money, with hardware vendors all making their products specifically for them, writing their code specifically for them, and how many architectures do they support?.. And how much does it cost??? Professional?? A professional deals with what he has to and makes the most of what he has to work with, and if they can even make it work well enough to get a user base then they are the professionals. Microsoft releases a new OS every 5-8 years, or whenever they want to usurp more of the market. And you don't get a choice in how it works or how it runs, and very little choice in how it looks. Frankly if you install linux to impress your friends then you must have had enough knowledge to snazz it up somewhat. The best thing about linux as far aesthetics is the fact it is completely customizable. Want it to look like your wife's Apple ipads interface? Well there is most likely a package for that and best of all its free of charge. Have a problem? Well there are places like this with all kinds of people all willing to take the time to help you and again its free of charge for a personal user. And most likely some person smarter than I will write a patch for this little blemish very soon and that too will be free of charge. Sorry if this got long and turned into a rant, but I always root for the underdog, and ya can't get anymore of an underdog than linux. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/563878 Title: Ubuntu splashscreen big and ugly after installing ATI/nVidia proprietary graphics driver -- ubuntu-bugs
[Bug 563878] Re: Ubuntu splashscreen big and ugly after installing ATI/nVidia proprietary graphics driver
Nathaniel, I too am sorry you felt you had engage capslock.LOL You said it embarrassed you when friends looked over your shoulder while the loading screen was displayed. As another poster pointed out thats the real problem here. Many of us here told you how to fix it, you can try one of those or not, its up to you. But telling us how its ubuntu's fault when it wasn't their drivers issue but rather those from the vendor, is going to ruffle more than a few feathers. Please try the one of or all of the fixes mentioned on here, and one of them will most likely fix the issue. Or you can sit there and tell us all how unprofessional Ubuntu is again. Either way now its on you. Good luck. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/563878 Title: Ubuntu splashscreen big and ugly after installing ATI/nVidia proprietary graphics driver -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 563878] Re: Ubuntu splashscreen big and ugly after installing ATI/nVidia proprietary graphics driver
The work arounds work to varying degrees for most people experiencing this issue, and I won't rehash them. That being said, I run the ATI proprietary driver in Ubuntu 10.10 and had this issue as well. This is an issue with proprietary drivers and NOT plymouth itself or Ubuntu. This is a prime example of closed versus open source and these type of things can and do happen. Until vendors such as ATI, Nvidia, et al, share openly with open source programmers these issues will pop up from time to time. My issue was fixed using a combination of startup manager (as mentioned above) and grabbing the latest stable release of the ATI proprietary driver. Frankly I cannot be sure which actually fixed the issue because I used startup manager while the latest driver was downloading. I didn't see the issue as being a big deal and really didn't pay much attention to it. All I really know is now the issue is fixed and the only changes I made were to use startup manager, install the Latest ATI prop driver, and a bit later install Zorin splash screen utility (can't remember its name ATM). So one of these or all of them fixed it for me. Sorry I cannot be more specific but as I said before this was not a big concern of mine and so the fix wasn't a priority. Personally I feel this is a simple cosmetic problem and being that it is not harming the functionality and only on screen for a few seconds, it most likely will never be a high priority to fix. Oh I am sure it will be fixed sooner or later but not before things like the ethernet/DHCP issues and such are ironed out. Those issues are effecting the functionality so rightly should be a higher priority. Along with that, ATI and Nvidia are not going to go out of their way for this cosmetic issue any time soon. Bottom line is try the work arounds mentioned several times here, or wait for the next update and hope they or ATI/Nvidia fix it. This is the current price we pay for a completely free (as in to use) OS. As long as big M, big U, and big A are able to do what they do unhindered, these things will continue to pop up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/563878 Title: Ubuntu splashscreen big and ugly after installing ATI/nVidia proprietary graphics driver -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 677701] Re: Wired network eth0 not working with 2.6.35-22-generic and Intel e1000e driver version 1.0.2-k4
Okay went and tried other distros over the last week or so... First I think your problem is specific to the intel NIC/chip on your machine(s). That being said, updating the specific intel driver may work fine in your situation, but I was addressing the larger more general issues regarding ethernet connections over the last few months using the .33 - .35 kernels. I have a nvidia MCP-67 chipset ethernet controller. It actually uses realtek chips. I also went and installed a seperate PCI ethernet card, an older Linksys. I get the same problem with either NIC and it is not right away nor is it all the time. It only happens AFTER I log into windows 7 then try and login to linux. At first I can reset my router and all is working again but this is a temporary fix. As I said I have gone with Ubuntu 10.04 which worked fine until either the updated kernel or I installed WIndows 7(no idea which because Windows 7 install was just before the kernel update). Soon after I had an issue with my NIC not connecting. I went through every forum I could find and met with varied levels of success using all kinds of methods. I updated fiirmware, and it worked. After a couple days I had to restart my router to get DHCP to work. I tried updating to 10.10 again same thing. Tried using Puppy linux and the tools there to get a connection and no luck. I tried Kubuntu 10.10, same issues, Pinguy OS, Gentoo live dvd, Debian squeeze, Slackware, and with every single one I got the same problem. Now my router is working fine, and has had no issues for over a year of use. Windows XP and WIndows 7 works with it without a single problem. Yet somehow with these linux kernels the thing has DHCP issues. The OS's (linux) all recognize my NIC's (both of them), both are recognized fully and show no problems at all. Yet somehow after running windows7 and then logging back into linux I cannot connect with either card. And the only thing that has worked for me reliably has been to restart my router and ensure my linux OS uses the same PC name as my Win7. Now it must be something with either DHCP and the kernels, a windows 7 problem involving home networking and such, or some other issue i am unaware of. Updating firmware worked in 10.04 for a short time only but 10.10 which shows the firmware installed in synaptic, still has the same issues. This is the same in every distro I have tried using any combination of those kernels. I can make it work by swapping the Eth cable between the two NIC's and restarting the router but as long as I have to do that I don't think I will be using the Linux drive very much... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/677701 Title: Wired network eth0 not working with 2.6.35-22-generic and Intel e1000e driver version 1.0.2-k4 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 677701] Re: Wired network eth0 not working with 2.6.35-22-generic and Intel e1000e driver version 1.0.2-k4
*update* Okay I think this may not really be a linux/debian/Ubuntu et al problem or bug. Regardless of the documented bug with network manager with Debain and therefore subsequent derivatives, there is an issue that is Windows 7 related that I think will clear up a lot of these issues. Now this may get rather verbose and long, but I did this so it can be understand by anyone even us noobs or at least semi noobs. When you have a dual boot scenario with windows 7 or vista I believe ( not sure if vista is same never used it) Windows must be first as usual. So being first it would seem logical that most of us installed win7 then installed our various linux ditros accordingly after the win7 install and initial setup. I assume most of us (me especially) setup their win7 install and got it running and in particular got the networking all arranged so we would have internet right away. And in so doing most of us set up homegroup network to share files and data amongst other pc's on the same network/router connection. When we did that we set up the home network not just in the win7 environment but in the network itself. I cannot explain it properly in technical terms but the simple mans take on it would be win7 has to make changes in the router settings or somewhere non-OS dependent to allow the homegroup magic to happen unhindered and simply as possible for the average non tech home user. This started when we chose the name of our computer at installation/setup of windows 7. More simply what ever name you gave your PC in windows 7 you must also use for your linux install if you use a dual boot scenario of any hardrive or partition scheme. I cannot explain the particulars as to why in a simple manner quick enough here, but doing this one thing fixed all of my networking problems in linux. So in your windows 7 install if your PC's name is Fred's PC or whatever, you must name your PC in the linux install the exact same name. Do not confuse your PC's name with your login or admin names. Those are different. This was not the case in XP but if you have a working win7 install you have to make sure the PC names match for both linux and win7. No matter the dual boot scenario, they must match. If not your only other option would be to somehow get both your router/server/network to see your linux install as a different PC altogether and that seems a bit of a nuisance when this is such a simple thing to do. Well I know this cured all of my network issues in linux right away. Running both Ubuntu 10.10 64 bit and Kubuntu 10.10 64 bit with out a single networking issue for two days now (knock on wood). And used a Puppy Linux Live CD to see if it worked there as well. Sure enough no connection until I set the PC name to the same as windows7 then Bingo! it worked. Anyway thanks for reading I hope it helps someone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/677701 Title: Wired network eth0 not working with 2.6.35-22-generic and Intel e1000e driver version 1.0.2-k4 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 635475] Re: [Maverick] Auto eth0 not working after latest package upgrade
I am a relative noob to linux in general, admittedly most of my knowledge or experience in linux is a hodgepodge of miscellaneous things to fix what I have broken usually. Because of this I have found this same or similar problems on virtually every Debian/Ubuntu et al., board or forum I have seen. Seems its a really big issue that isn't just one port of the latest Debs. I had the same issue with the latest puppy linux from the live cd, and with all the tools and different utilities in it I got the same problem. I also read of a similar problem using Fedora, and Mandriva so perhaps its a source problem. In my case, I had the idea to try the latest Debian stable squeeze and first had issues with it not writing grub2 at the install finish, then tried to go back to ubuntu only to have it take several tries to even install correctly. Ever since I have had various issues from faulty installations to undetected hardware and of course the networking card not connecting. To be honest at this point I am ready to wipe this drive and go with either a Gentoo or in the very least a non-Deb distro. I don't know but maybe its not even an actual linux issue at all. Microsoft comes out with a new OS and suddenly the most popular distros have a rash of issues ranging from serious to bothersome, and to this point no real fixes for the lions share of them. Very odd I had no problems with any Ubuntu/Deb distro beyond the random xorg/ATI issue, until I replaced windows xp (kept on a separate disk for the kids and wife) with windows 7. I'm smelling a MS rat but then thats me, I don't trust them at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/635475 Title: [Maverick] Auto eth0 not working after latest package upgrade -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 677701] Re: Wired network eth0 not working with 2.6.35-22-generic and Intel e1000e driver version 1.0.2-k4
Just found this on the debian wikki network manager page. Might be applicable here and to various other NIC card issues I have seen here lately. http://wiki.debian.org/NetworkManager Scroll down to the section marked NetworkManager in Squeeze and it says the following.. NetworkManager in Squeeze Wired Networks are Unmanaged As of Debian Squeeze, NetworkManager does not manage any interface defined in /etc/network/interfaces by default. Unmanaged devices means NetworkManager doesn't handle those network devices. This occurs when two conditions are met: The file /etc/network/interfaces contains anything about the interface, even: allow-hotplug eth0 iface eth0 inet dhcp And /etc/NetworkManager/NetworkManager.conf contains: [main] plugins=ifupdown,keyfile [ifupdown] managed=false Since network-manager version 0.8.1-4, existing wired/wireless interfaces in /etc/network/interfaces are disabled with a #NetworkManager# prefix during package installation, then re-enabled when the network-manager package is removed (Debian bug 530024). Enabling Interface Management If you want NetworkManager to handle interfaces that are enabled in /etc/network/interfaces: Set managed=true in /etc/NetworkManager/NetworkManager.conf. Restart NetworkManager: /etc/init.d/network-manager restart Auto Ethernet and Auto eth0 Auto Ethernet means Select an Ethernet interface automatically Auto eth0 means autconfigure the eth0 interface. I think its relative... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/677701 Title: Wired network eth0 not working with 2.6.35-22-generic and Intel e1000e driver version 1.0.2-k4 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
