[Bug 459403] Re: OpenLDAP server instructions out of date: slapd no longer creates initial directory
Would it be possible to setup some ppa with the version of slapd from jaunty and compatible with Karmic? -- OpenLDAP server instructions out of date: slapd no longer creates initial directory https://bugs.launchpad.net/bugs/459403 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 386820] Re: X Server is already running on Display 0:
** Description changed: Whenever I try to log into the computer from GDM, I get a bug saying that there is already an X Server running on Display 0:. It gives me an option to start a new one on the next display. If I say yes, it has me log on again, and then just tells me there's already an X server running on that display. If I say no, it has me log on again and tells me the same error. I'm told that I could work around this bug if I could remove the X server lock in temp, however, the tty shells appear to be broken too. I try to log into them and then they just have me enter my credentials again. I have never had this kind of negative experience before with Ubuntu, but this is simply intolerable. I'd like some kind of fix. For reference sake, my video card is an nVidia 9500. This bug occured with both the 173 drivers and the 180 drivers, so it would seem drivers are unrelated. + + UPDATE - I've decided to go back to 8.04 LTS, as this bug has remained + unfixed for so incredibly long that I've been convinced the team that + works on 9.04 just plain doesn't care. -- X Server is already running on Display 0: https://bugs.launchpad.net/bugs/386820 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 386820] [NEW] X Server is already running on Display 0:
Public bug reported: Whenever I try to log into the computer from GDM, I get a bug saying that there is already an X Server running on Display 0:. It gives me an option to start a new one on the next display. If I say yes, it has me log on again, and then just tells me there's already an X server running on that display. If I say no, it has me log on again and tells me the same error. I'm told that I could work around this bug if I could remove the X server lock in temp, however, the tty shells appear to be broken too. I try to log into them and then they just have me enter my credentials again. I have never had this kind of negative experience before with Ubuntu, but this is simply intolerable. I'd like some kind of fix. For reference sake, my video card is an nVidia 9500. This bug occured with both the 173 drivers and the 180 drivers, so it would seem drivers are unrelated. ** Affects: ubuntu Importance: Undecided Status: New ** Description changed: Whenever I try to log into the computer from GDM, I get a bug saying that there is already an X Server running on Display 0:. It gives me an option to start a new one on the next display. If I say yes, it has me log on again, and then just tells me there's already an X server running on that display. If I say no, it has me log on again and tells me the same error. I'm told that I could work around this bug if I could remove the X server lock in temp, however, the tty shells appear to be broken too. I try to log into them and then they just have me enter my credentials again. I have never had this kind of negative experience before with Ubuntu, but this is simply intolerable. I'd like some kind of fix. + + For reference sake, my video card is an nVidia 9500. This bug occured + with both the 173 drivers and the 180 drivers, so it would seem drivers + are unrelated. -- X Server is already running on Display 0: https://bugs.launchpad.net/bugs/386820 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 283165] Re: Intrepid beta kernel panic acx.ko with TNET1130 incorrect firmware version
Hi Jap1968, I suggest you try alternative firmware versions as I was able to get the driver to be stable with 1.2.1.34. You can find the available firmware versions by looking in the readme file in /lib/firmware/acx/README.txt. You then set the firmware version by adding a line to the /etc/modprobe.d/options file like 'option acx firmware_ver=1.2.1.34' Regards Andrew L -- Intrepid beta kernel panic acx.ko with TNET1130 incorrect firmware version https://bugs.launchpad.net/bugs/283165 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 283165] Re: Intrepid beta kernel panic acx.ko with TNET1130 incorrect firmware version
I ended up doing md5sums on all the hotplug supplied firmware files to match the version of firmware I was using with ndiswrapper. It turns out that I was using 1.2.1.34, although the documentation that came with the windows driver I was using did not mention this. When I set the firmware_ver option to 1.2.1.34 the driver loaded and the system was stable. After stuffing around trying to get wpa_supplicant to work for a while I RTFM'd and realised that WPA wasn't supported. I ended up using ndiswrapper and connected without too many issues. ** Summary changed: - Intrepid beta kernel panic acx.ko with TNET1130 and WPA network + Intrepid beta kernel panic acx.ko with TNET1130 incorrect firmware version -- Intrepid beta kernel panic acx.ko with TNET1130 incorrect firmware version https://bugs.launchpad.net/bugs/283165 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 283165] Re: Intrepid beta kernel panic acx.ko with TNET1130 and WPA network
** Summary changed: - Intrepid beta kernel panic acx.ko incorrectly identifying TNET1130 as ACX111 + Intrepid beta kernel panic acx.ko with TNET1130 and WPA network ** Description changed: My Texas Instruments TNET1130 wireless NIC has not been fully supported in earlier versions of Ubuntu - I have had both 8.04 and 7.10 installed, and each time I had to install ndiswrapper and use the windows driver to get WPA support. - When I installed both Alpha6 and Beta of Intrepid, it initially worked OK, but when I configured my WPA wireless network and rebooted, I would get to the login screen, hear the drums and attempt to login before I ended up with a kernel panic (caps and scroll lights on keyboard would go on solid and I would get a hard freeze). Booting to single user mode was fine. - I changed to console view before the panic and got a partial stack trace on the screen, which included several references to acx. - I disabled the acx module by moving /lib/modules/2.6.27-4-generic/kernel/ubuntu/misc/wireless/acx/acx.ko out of modules directory. I have since run lspci and the Ubuntu hardware testing applet and in both cases the wireless card was identified as a Texas Instruments ACX 111 54Mbps Wireless Interface [104c:9066]. I do not think this is correct. I have been using the TNET1130 driver. - + When I installed both Alpha6 and Beta of Intrepid, it initially worked OK, but when I configured my WPA wireless network and rebooted, I would get to the login screen, hear the drums and attempt to login before I ended up with a kernel panic (caps and scroll lights on keyboard would flash and I would get a hard freeze). Booting to single user mode was fine. + I changed to console view before the panic and got a partial stack trace on the screen, which included several references to acx and wpa_supplicant. + I disabled the acx module by adding to /etc/modprobe.d/blacklist and moving /lib/modules/2.6.27-4-generic/kernel/ubuntu/misc/wireless/acx/acx.ko out of modules directory. I have since run lspci and the Ubuntu hardware testing applet and in both cases the wireless card was identified as a Texas Instruments ACX 111 54Mbps Wireless Interface [104c:9066]. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 8.10 Package: linux-image-2.6.27-4-generic 2.6.27-4.6 [modified: lib/modules/2.6.27-4-generic/modules.pcimap lib/modules/2.6.27-4-generic/modules.dep lib/modules/2.6.27-4-generic/modules.ieee1394map lib/modules/2.6.27-4-generic/modules.usbmap lib/modules/2.6.27-4-generic/modules.isapnpmap lib/modules/2.6.27-4-generic/modules.inputmap lib/modules/2.6.27-4-generic/modules.seriomap lib/modules/2.6.27-4-generic/modules.alias lib/modules/2.6.27-4-generic/modules.symbols] ProcCmdLine: User Name=UUID=e3ce3882-7578-4078-b3cd-1602f113f158 ro quiet splash ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_AU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.27-4.6-generic SourcePackage: linux UnreportableReason: This is not a genuine Ubuntu package ** Attachment added: messagesExtract http://launchpadlibrarian.net/18648940/messagesExtract -- Intrepid beta kernel panic acx.ko with TNET1130 and WPA network https://bugs.launchpad.net/bugs/283165 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 283165] Re: Intrepid beta kernel panic acx.ko incorrectly identifying TNET1130 as ACX111
Further info - upgrading to 2.6.27-7-generic did not prevent panic. I disabled acx.ko again and system has been stable since. -- Intrepid beta kernel panic acx.ko incorrectly identifying TNET1130 as ACX111 https://bugs.launchpad.net/bugs/283165 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 283165] [NEW] Intrepid beta kernel panic acx.ko incorrectly identifying TNET1130 as ACX111
Public bug reported: My Texas Instruments TNET1130 wireless NIC has not been fully supported in earlier versions of Ubuntu - I have had both 8.04 and 7.10 installed, and each time I had to install ndiswrapper and use the windows driver to get WPA support. When I installed both Alpha6 and Beta of Intrepid, it initially worked OK, but when I configured my WPA wireless network and rebooted, I would get to the login screen, hear the drums and attempt to login before I ended up with a kernel panic (caps and scroll lights on keyboard would go on solid and I would get a hard freeze). Booting to single user mode was fine. I changed to console view before the panic and got a partial stack trace on the screen, which included several references to acx. I disabled the acx module by moving /lib/modules/2.6.27-4-generic/kernel/ubuntu/misc/wireless/acx/acx.ko out of modules directory. I have since run lspci and the Ubuntu hardware testing applet and in both cases the wireless card was identified as a Texas Instruments ACX 111 54Mbps Wireless Interface [104c:9066]. I do not think this is correct. I have been using the TNET1130 driver. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 8.10 Package: linux-image-2.6.27-4-generic 2.6.27-4.6 [modified: lib/modules/2.6.27-4-generic/modules.pcimap lib/modules/2.6.27-4-generic/modules.dep lib/modules/2.6.27-4-generic/modules.ieee1394map lib/modules/2.6.27-4-generic/modules.usbmap lib/modules/2.6.27-4-generic/modules.isapnpmap lib/modules/2.6.27-4-generic/modules.inputmap lib/modules/2.6.27-4-generic/modules.seriomap lib/modules/2.6.27-4-generic/modules.alias lib/modules/2.6.27-4-generic/modules.symbols] ProcCmdLine: User Name=UUID=e3ce3882-7578-4078-b3cd-1602f113f158 ro quiet splash ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_AU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.27-4.6-generic SourcePackage: linux UnreportableReason: This is not a genuine Ubuntu package ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- Intrepid beta kernel panic acx.ko incorrectly identifying TNET1130 as ACX111 https://bugs.launchpad.net/bugs/283165 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 283165] Re: Intrepid beta kernel panic acx.ko incorrectly identifying TNET1130 as ACX111
** Attachment added: lspciOutput.txt http://launchpadlibrarian.net/18529550/lspciOutput.txt ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/18529551/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/18529552/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/18529553/Dependencies.txt ** Attachment added: HalComputerInfo.txt http://launchpadlibrarian.net/18529554/HalComputerInfo.txt ** Attachment added: LsUsb.txt http://launchpadlibrarian.net/18529555/LsUsb.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/18529556/Lspci.txt ** Attachment added: ProcCpuInfo.txt http://launchpadlibrarian.net/18529557/ProcCpuInfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/18529558/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/18529559/ProcModules.txt -- Intrepid beta kernel panic acx.ko incorrectly identifying TNET1130 as ACX111 https://bugs.launchpad.net/bugs/283165 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 153994] Re: dbmail cannot find create_user during postinst
I used for the installation packages for hardy and they worked OK. -- dbmail cannot find create_user during postinst https://bugs.launchpad.net/bugs/153994 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 153994] Re: dbmail cannot find create_user during postinst
I am having the same problem. -- dbmail cannot find create_user during postinst https://bugs.launchpad.net/bugs/153994 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 153013] Re: 7.10 RC Update Installation Errors
*** This bug is a duplicate of bug 116193 *** https://bugs.launchpad.net/bugs/116193 The Fix- Set your timezone to London for a second. It's weird, but it works. -- 7.10 RC Update Installation Errors https://bugs.launchpad.net/bugs/153013 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 84060] Re: [apport] alacarte crashed with AttributeError in __getPath()
I find it insulting that the priority of this bug is set to Low, and that one person even bothered to claim that this is not a real crash. I, myself, experience it every single time I try to revert the applicaitons menu, and all my applications links are GONE. If Ubuntu intends to be a distribution focusing on user empowerment, it needs to stop ignoring its users on bugs this large. -- [apport] alacarte crashed with AttributeError in __getPath() https://bugs.launchpad.net/bugs/84060 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 133503] [Gutsy] Screens And Graphics on ATI
Public bug reported: Binary package hint: xorg I love the new screens and graphics manager. It adds a lot of function that just wasn't their before. But I've found a flaw in Dual display on my card. To reproduce: Run Gutsy up to date on an ATI 9200 SE, hooked up to be Dual Display composite video, one TV, one CRT. [note: when starting with said update, I noticed that it can actually disable the TV, which is more good than anything else, because number one, it means it can send messages, and number two, it gets rid of the ugly glitches when I turn on the TV.] Set to dual display, with the TV as secondary. Hit test Screen turns gray as to ask you for confirmation, however instead, a strange box appears as your mouse, and the TV shows absolutely nothing. See what you can do with this one. I love how close it's gotten to finally having ATI TV support without the dreaded fglrx drivers. If you can get this done, then Ubuntu is greater than all other Operating systems. (Granted that's true already. But you know what I mean.) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- [Gutsy] Screens And Graphics on ATI https://bugs.launchpad.net/bugs/133503 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 133503] Re: [Gutsy] Screens And Graphics on ATI
*** This bug is a duplicate of bug 37764 *** https://bugs.launchpad.net/bugs/37764 This bug isn't a duplicate... This is describing the new Gutsy versions which have some TV out support for ATI cards, provided by the GATOS team. Fix the marking. -- [Gutsy] Screens And Graphics on ATI https://bugs.launchpad.net/bugs/133503 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 126494] Re: wired network shown as disabled after boot
Same thing happens in Gnome. -- wired network shown as disabled after boot https://bugs.launchpad.net/bugs/126494 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 125368] Re: networking is disabled when starting Gutsy
Sorry, this bug was NOT fixed. It's still here. I have it too. -- networking is disabled when starting Gutsy https://bugs.launchpad.net/bugs/125368 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
