[Bug 80856] Re: F-Spot as default for importing photos
I agree with making F-Spot the default for importing photos and removing gThumb from the CD. Just let F-spot act as the photo management application and, let Eye of GNOME be used for image viewing. Having two applications for photo management, both F-Spot and gThumb, is unnecessary duplication and a waste of CD space. Sure F-Spot is not perfect, I've filed a lot of bugreports for it on GNOME's Bugzilla, but I haven't experienced the rampant crashing described by Martin Pitt. If people complain about F-Spot so much, maybe we could wait until it develops further, and then review this case again? -- F-Spot as default for importing photos https://bugs.launchpad.net/bugs/80856 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 106864] Re: Feisty boot fail can't access tty IDE SATA problem
Henrik Nilsen Onma, in my comment, comment #69, (https://bugs.launchpad.net/ubuntu/+source/linux- source-2.6.20/+bug/106864/comments/69) I already reported reproducing it on Gutsy/7.10 three months ago. -- Feisty boot fail can't access tty IDE SATA problem https://bugs.launchpad.net/bugs/106864 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 135228] Re: GNOME session freezes to black screen, Failsafe GNOME session works fine
nainu, thank you for your comment. Disabling the desktop effects and disabling AddARGBGLXVisuals (not sure if both are necessary or just disabling desktop effects is enough) in my xorg.conf allowed me to log in normally to the GNOME session. The xsession-errors file which I attached also lists an error message for Compiz. Have we verified that this is a bug caused by X.org/Compiz not playing nice with gnome-session and can I mark this bug as a duplicate of bug #125902? Or do you still want me to ask the question in the support tracker, Sebastien? -- GNOME session freezes to black screen, Failsafe GNOME session works fine https://bugs.launchpad.net/bugs/135228 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 135228] Re: GNOME session freezes to black screen, Failsafe GNOME session works fine
Hmm, ok. I did not know how to provide debugging information for this bug because the crash happens when I log in. I have used GDB in the past to provide backtraces, but AFAIK there is no way to start GDB or something like that to get a backtrace before I log in, or is there? I've read the information on the wiki for debugging procedures - https://wiki.ubuntu.com/DebuggingProcedures - the document which describes my situation most closely there is probably - https://help.ubuntu.com/community/DebuggingSystemCrash - but that only deals with reproducing crashes on a text console, which is probably not what I need to do if my crash happens when I log in to GNOME. To be honestly I don't know how to provide the correct debugging information then, there is no info on the Ubuntu wiki either. The only way I could think of was providing some log files, I thought the .xsession-errors file was useful? -- GNOME session freezes to black screen, Failsafe GNOME session works fine https://bugs.launchpad.net/bugs/135228 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 135228] Re: GNOME session freezes to black screen, Failsafe GNOME session works fine
Thank you for your reply, but could you please go into more details instead of giving a standard answer? I don't understand, if this freezing at login is not intended behavior how can it not be a bug? -- GNOME session freezes to black screen, Failsafe GNOME session works fine https://bugs.launchpad.net/bugs/135228 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 135228] Re: GNOME session freezes to black screen, Failsafe GNOME session works fine
I had the idea that I was describing this bug as clearly as possible to get it fixed as a consequence, and that getting it fixed would help me getting my system working again. To be clear, I certainly was trying to write a bugreport, not a help request. Writing a good bugreport was my intention, and if the bug could be fixed and I'd have a correctly functioning system again that would be a good thing, but not the goal of this bugreport. Are you implying that I did not describe the bug properly (not clearly enough, as you emphasized)? Besides that, you still haven't explained why you don't accept this bugreport. Could you please tell me why this is not a valid bug? Is my description not correct or is information missing? Is the bug fixed already, is it a duplicate? I believe that I have described the steps necessary to reproduce the bug, described the effects of the bug, and that the effects of the bug are not normal behavior. Am I missing something here? -- GNOME session freezes to black screen, Failsafe GNOME session works fine https://bugs.launchpad.net/bugs/135228 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 135228] Re: GNOME session freezes to black screen, Failsafe GNOME session works fine
Yes, ping localhost works: [EMAIL PROTECTED]:~$ ping localhost PING localhost (127.0.0.1) 56(84) bytes of data. 64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.029 ms 64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.025 ms 64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.025 ms And my network/internet connection also works, most of the time. Sometimes after I log in to the Failsafe GNOME session, I notice that my network connection is not working. Then I simply right-click the NetworkManager applet and uncheck Enable Networking and then check it again, then NetworkManager establishes a working connection again. And I don't now if it's useful in any way, but I attached the .xsession- errors file, which was located as a hidden file in my home directory, it gives some error messages. ** Attachment added: .xsession-errors http://launchpadlibrarian.net/9098992/copy_.xsession-errors -- GNOME session freezes to black screen, Failsafe GNOME session works fine https://bugs.launchpad.net/bugs/135228 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 135228] Re: GNOME session freezes to black screen, Failsafe GNOME session works fine
I forgot to change the status from incomplete to new after giving the required extra information, so I'm doing that now. ** Changed in: gnome-session (Ubuntu) Status: Incomplete = New -- GNOME session freezes to black screen, Failsafe GNOME session works fine https://bugs.launchpad.net/bugs/135228 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 135228] Re: GNOME session freezes to black screen, Failsafe GNOME session works fine
I created another user and tried to log in to the GNOME session with that user. That worked. However, if I try to log out with that other user, the system freezes (similar to what I experienced with my normal user, as I described previously), and it displays the desktop wallpaper with GNONE's empty taskbars, only the mouse is moveable and it doesn't respond to keyboard input. I had to hit the reset button of my system. However, unlike my normal user, I can still log in tot the GNOME session with the other user after the crash on logout (it doesn't crash to a black screen if I log in with the other user). If I try to log in to the Failsafe GNOME session with the other user, it does not freeze when I log out. -- GNOME session freezes to black screen, Failsafe GNOME session works fine https://bugs.launchpad.net/bugs/135228 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 49827] Re: Available resolutions incompletely set to 1024x768, 800x600, 640x480
I'm still affected by this problem as well. With Ubuntu 7.10 Tribe 5, a daily build of 27 August to be exact, Ubuntu still doesn't choose the right resolution. Installing the NVIDIA driver (nvidia-glx-new) for my NVIDIA GeForce 7800 GT didn't change anything, and I had to manually edit xorg.conf to be able to use the 1680 x 1050 resolution on my Dell 2007 WFP 20 inch widescreen monitor, Ubuntu defaults to 1280 x 1024. I'll attach the full output of 'sudo lspci -vvnn', /etc/X11/xorg.conf and /var/log/Xorg.0.log (of course from before I installed the NVIDIA driver or edited xorg.conf). Don't know if it's any use, but I hope so. ** Attachment added: xorg.conf http://launchpadlibrarian.net/9022373/contents_xorg_conf -- Available resolutions incompletely set to 1024x768, 800x600, 640x480 https://bugs.launchpad.net/bugs/49827 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 49827] Re: Available resolutions incompletely set to 1024x768, 800x600, 640x480
** Attachment added: output of 'sudo lspci -vvnn' http://launchpadlibrarian.net/9022382/lspci_output -- Available resolutions incompletely set to 1024x768, 800x600, 640x480 https://bugs.launchpad.net/bugs/49827 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 49827] Re: Available resolutions incompletely set to 1024x768, 800x600, 640x480
** Attachment added: Xorg.0.log http://launchpadlibrarian.net/9022379/contents_xorg_log -- Available resolutions incompletely set to 1024x768, 800x600, 640x480 https://bugs.launchpad.net/bugs/49827 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 135228] GNOME session freezes to black screen, Failsafe GNOME session works fine
Public bug reported: Binary package hint: gnome-session I installed Ubuntu 7.10 Tribe 4 and downloaded all the latest updates as of yesterday, 27 August, so the gnome-session version is 2.19.90-0ubuntu2. I was about to shut down my PC, but before I did so I opened System - Preferences - Sessions - Session Options and enabled Automatically remember running applications when logging out so that session saving was enabled. Then I shut down. Ubuntu didn't shut down properly, the GNOME Panel and applications disappeared, but the wallpaper on my desktop background didn't and kept being displayed. I waited a while, but after a few minutes I hit the reset button because Ubuntu had obviously frozen. After starting up again, I logged in from GDM (without changing the session, so by default I was logging in to the Last session). After entering my username and password, GNOME didn't load. It crashed to a black screen, with my mouse cursor still visible and responsive. I hit Ctrl + Alt + Backspace to kill X and return to GDM, there I chose the Failsafe GNOME session this time, and logged in succesfully. However, if I try to log in to the GNOME session again, it still produces the same crash. ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New -- GNOME session freezes to black screen, Failsafe GNOME session works fine https://bugs.launchpad.net/bugs/135228 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 63560] Re: installing 915resolution for the correct resolution shouldn't be necessary
I can confirm that the fix works in my case. When I installed Gutsy Tribe 4 on the same notebook as I mentioned in my initial bugreport here, Ubuntu chose the correct resolution - 1280 by 800 pixels - by default. However, when I install Tribe 4 on my desktop PC, which has a Dell 2007WFP 20 inch widescreen monitor (which has a resolution of 1680 by 1050 pixels) connected to a NVIDIA GeForce 7800 GT, it still chooses the wrong resolution of 1280 by 1024 pixels. I shall file a separate bugreport for that according to your instructions, Brian Murray. -- installing 915resolution for the correct resolution shouldn't be necessary https://bugs.launchpad.net/bugs/63560 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 106864] Re: Feisty boot fail can't access tty IDE SATA problem
Same here, I tried the Ubuntu 7.10 Tribe 1 i386 Live CD, and I got the same error. I also experienced that the floppy drive was busy, even though it didn't have a disk inserted. And I don't have SATA harddisks, if that is relevant to this problem. I'd really like to be able to boot Tribe 1, so I tried to follow the workaround posted by Ben Collins - https://bugs.launchpad.net/ubuntu/+source/linux- source-2.6.20/+bug/106864/comments/13 - but it didn't work. As soon as I start up my PC and see the Live CD menu, I hit F6, type break=top (without the quotation marks of course), and I press Enter. After a while I see this error message: Loading, please wait... Spawning shell within the initramfs Busybox v1.1.3 (Debian 1:1.1.3-4ubuntu3) Built-in shell (ash) Enter 'help' for a list of built-in commands. /bin/sh: can't access tty; job control turned off (initramfs) the text input cursor flashes here However, if I try to type modprobe piix, no text will appear, the flashing text input cursor doesn't do anything. The same happened when I tried the workaround with the Ubuntu 7.04 release i386 Live CD. Why doesn't it accept any text input? A solution which works would be appreciated, because I'd really like to install Tribe 1. -- Feisty boot fail can't access tty IDE SATA problem https://bugs.launchpad.net/bugs/106864 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 91470] filename of ubuntu and derivative distro iso's aren't distinguishable
Public bug reported: Take a look at the ISO image download pages for Ubuntu, Edubuntu, Kubuntu and Xubuntu: http://cdimage.ubuntu.com/releases/feisty/herd-5/ http://cdimage.ubuntu.com/kubuntu/releases/feisty/herd-5/ http://cdimage.ubuntu.com/edubuntu/releases/feisty/herd-5/ http://cdimage.ubuntu.com/xubuntu/releases/feisty/herd-5/ All these four distributions have a desktop CD for the i386 architecture. The filename is identical for all four distributions: feisty-desktop-i386.iso. The same goes for the alternate, server, amd64 and sparc variants. This makes it difficult to tell what the contents of the ISO image are, to distinguish between the ISO images for the different distro's, and even to distinguish between alpha and final releases for the same distro. Also it's annoying that if I download ISO images for two distro's with my bittorrent client (which downloads everything to the same directory), that I'm forced to change the filename because two files with identical filenames can't exist in the same directory. So I propose a more detailed naming scheme for the ISO images to distinguish between distro and release. For example: distribution-release-CD-type.iso. With this you would get better filenames, like ubuntu-feisty- herd5-desktop.iso or kubuntu-feisty-desktop.iso (that would be the final release). Personally I'd prefer the version number in the filename, for example ubuntu-704-herd5-desktop.iso. For me, a codename like feisty says nothing, while 7.04 says it's the release of the fourth month of 2007, which allows me to distinguish it from older version numbers as newer (however, I understand Canonical favors the codenames approach, so I don't expect that to happen). This is a minor problem, but nevertheless a very annoying problem. Could this please be fixed? I assume changing the file naming policy would be easy. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- filename of ubuntu and derivative distro iso's aren't distinguishable https://launchpad.net/bugs/91470 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63551] Re: X.org doesn't detect widescreen resolution
I just downloaded Ubuntu 7.04 Herd 5, and when I started the LiveCD it still automatically detected a resolution of 1280x1024. I'm still using the same hardware, a Dell 2007WFP with a resolution of 1680x1050 which is connected to a NVIDIA GeForce 7800GT. I thought that Herd 5 has X.org 7.2 included, which is supposed to have improved autoconfiguration. But why can't it still detect widescreen resolutions properly? -- X.org doesn't detect widescreen resolution https://launchpad.net/bugs/63551 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63551] Re: X.org doesn't detect widescreen resolution
** Bug watch added: Freedesktop Bugzilla #10169 https://bugs.freedesktop.org/show_bug.cgi?id=10169 ** Also affects: xorg-server (upstream) via https://bugs.freedesktop.org/show_bug.cgi?id=10169 Importance: Unknown Status: Unknown -- X.org doesn't detect widescreen resolution https://launchpad.net/bugs/63551 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63551] Re: X.org doesn't detect widescreen resolution
Ok, so because there wasn't any Ubuntu dev giving any attention to this bug, I decided to report it upstream myself. I just added a remote bug watch. Within a few hours I already got a reply on my bugreport, the bug is apparantly not X.org's fault, but Ubuntu's fault. I can imagine that the Ubuntu dev's are busy, but I'm a bit disappointed that nothing has been done on this serious bug for quite a few months. -- X.org doesn't detect widescreen resolution https://launchpad.net/bugs/63551 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67193] Re: on gnome start i get a crash report
I just came here searching for the relevant bug after getting tired of the constant warnings that Gaim crashed (when in fact it doesn't crash during my use of it, and works fine for me), and it seems to me that my problem is indeed more like bug #67361. Sebastian, you are annoyed by people who misidentify their problem as belonging to this bug. To end the confusion, what about marking this as a duplicate of #67361? If it's marked as a duplicate it won't show up in the search, so there won't be anyone who makes the error to post their crash reports here. Besides that, you mentioned that the orginal description doesn't have enough useful information, this bug is a few months old already and the original reporter has not added any info since then. I'll just take the liberty to mark it as a dup, I hope that's ok with you? -- on gnome start i get a crash report https://launchpad.net/bugs/67193 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67193] Re: on gnome start i get a crash report
Hmm, never mind, just see that it already is a duplicate of bug #67361. I wonder then why this one is still visible in the search results? -- on gnome start i get a crash report https://launchpad.net/bugs/67193 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63551] Re: X.org doesn't detect widescreen resolution
My Dell 2007WFP 20 widescreen is connected to a NVIDIA video card, so I did not use 915resolution because 915resolution only applies to Intel chips. So I had to edit my xorg.conf. -- X.org doesn't detect widescreen resolution https://launchpad.net/bugs/63551 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70092] Re: package description of nvidia-glx(-legacy) is misleading, both drivers not working
Changed package, because this package contains the NVIDIA driver if I'm correct. ** Changed in: xorg (Ubuntu) Sourcepackagename: xorg = linux-restricted-modules-2.6.17 -- package description of nvidia-glx(-legacy) is misleading, both drivers not working https://launchpad.net/bugs/70092 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70092] Re: package description of nvidia-glx is misleading
So I've reinstalled the PC I was talking about in my first comment. I installed nvidia-glx-legacy, and this time I made sure of where to find the backup xorg.conf which sudo nvidia-glx-config enable writes. I restarted, being sure that this time it would work because nvidia-glx- legacy was the correct choice for a GeForce 2 MX. However, when I restarted I was kicked to the command prompt after starting up Kubuntu 6.10 and X wouldn't start. I restored the backup of xorg.conf and everything as fine, but I want the driver to work. I need it because I have a vertical black bar on the left side of the visible area of the monitor. I've experienced this on more than one occassion when I installed Linux distro's, and installing the drivers would fix the black area on the visible area of the monitor. I've included the backupped xorg.conf, and the xorg.conf after doing sudo nvidia-glx-config enable. ** Attachment added: working backup of xorg.conf http://librarian.launchpad.net/5347250/backup_xorg.conf -- package description of nvidia-glx(-legacy) is misleading, both drivers not working https://launchpad.net/bugs/70092 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70092] Re: package description of nvidia-glx is misleading
Because I can't add two attachments to one post, here is the xorg.conf after sudo nvidia-glx-config enable which does not work and prevents X for working. ** Attachment added: not working xorg.conf http://librarian.launchpad.net/5347252/defect_xorg.conf ** Summary changed: - package description of nvidia-glx is misleading + package description of nvidia-glx(-legacy) is misleading, both drivers not working -- package description of nvidia-glx(-legacy) is misleading, both drivers not working https://launchpad.net/bugs/70092 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70092] Re: package description of nvidia-glx(-legacy) is misleading, both drivers not working
Not sure if it's X.org's fault, but I thought a guess is better than nothing. ** Changed in: Ubuntu Sourcepackagename: None = xorg -- package description of nvidia-glx(-legacy) is misleading, both drivers not working https://launchpad.net/bugs/70092 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70092] Re: X won't start after sudo nvidia-glx-config enable
Can't choose the the nvidia-glx package for some reason, and I can't change the title description of this bug to a better title? ** Changed in: linux-restricted-modules-2.6.17 (Ubuntu) Sourcepackagename: linux-restricted-modules-2.6.17 = None ** Summary changed: - X won't start after sudo nvidia-glx-config enable + package description of nvidia-glx is misleading -- package description of nvidia-glx is misleading https://launchpad.net/bugs/70092 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70092] Re: package description of nvidia-glx is misleading
Nevermind, just changed the title. -- package description of nvidia-glx is misleading https://launchpad.net/bugs/70092 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70092] Re: X won't start after sudo nvidia-glx-config enable
Thank you very much for your comment. Could it be that the GeForce 1/2 drivers have been moved to the nvidia-glx-legacy package recently? If I'm correct I used to install the non-legacy package for GeForce 2 videocards, and this is the first time I noticed that has changed. Now that we know that the drivers themselves or X.org are not the problem, I think the description of the packages are a problem. Let's compare the package descriptions: * nvidia-glx * These XFree86 4.x/X.Org binary drivers provide optimized hardware acceleration of OpenGL applications via a direct-rendering X Server and support the newer GeForce, nForce and Quadro families of NVIDIA chipsets. AGP, TV-out and flat panel displays are also supported. If you have a TNT, TNT2, or older GeForce, you may need the nvidia-glx- legacy package instead of this one. To enable the driver, run sudo nvidia-glx-config enable. * nvidia-glx-legacy * These XFree86 4.x/X.Org binary drivers provide optimized hardware acceleration of OpenGL applications via a direct-rendering X Server and supports the TNT, TNT2, TNT Ultra, GeForce, and GeForce2 chipsets. AGP, TV-out and flat panel displays are also supported. This is the 'legacy' driver for older chipsets. Unless your chipset is explicitly listed in the above paragraph, please use the nvidia-glx driver, which is much more up to date. To enable the driver, run sudo nvidia-glx-config enable. I only read the description for nvidia-glx. That description does not specify which series of GeForce video cards are older and which are newer. I could not know that I had to use nvidia-glx-legacy if I only read the description of the nvidia-glx package. Only in the description of nvidia-glx-legacy it is mentioned explicitly that I should use legacy if I have a GeForce 1/2 videocard. The nvidia-glx package description should mention this as well. -- package description of nvidia-glx is misleading https://launchpad.net/bugs/70092 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63560] Re: installing 915resolution for the correct resolution shouldn't be necessary
Thanks for your information, I'd be happy to help. However, how do we edit that specification and what more do we need to do in order for this problem to get the developers attention? If I visit the edit page it says I don't have permission. My Jabber ID is [EMAIL PROTECTED], please add me so that we can talk. -- installing 915resolution for the correct resolution shouldn't be necessary https://launchpad.net/bugs/63560 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70087] searching in khelpcenter is broken
Public bug reported: Binary package hint: khelpcenter You're new to Kubuntu and you want to know how to install Java, flash and other stuff. Go to K Menu - Help and try to search for Java or Flash. Nothing will happen. By the way, such essential information on installing Java and Flash should be very easily accessible. Currently it is too hard for newcomers to figure this out. ** Affects: kdebase (Ubuntu) Importance: Undecided Status: Unconfirmed -- searching in khelpcenter is broken https://launchpad.net/bugs/70087 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 70088] should tell that CD will be ejected automatically
Public bug reported: When the installation is finished, the installer ask the user to remove the CD before restarting. I believe this is incorrect, as that is not what happens. After clicking restart, the CD will eject automatically. So please tell the user that this will happen automatically after the user clicks restart. Currently it's a bit confusing, when I received the dialog I tried ejecting the CD before clicking restart, and the CD would not eject. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: Unconfirmed ** Changed in: kdebase (Ubuntu) Sourcepackagename: kdebase = ubiquity -- should tell that CD will be ejected automatically https://launchpad.net/bugs/70088 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70092] X won't start after sudo nvidia-glx-config enable
Public bug reported: Binary package hint: nvidia-glx I installed Kubuntu 6.10 succesfully on a machine and downloaded the NVIDIA drivers (the machine has a GeForce 2 MX, so that would be the appropriate driver (no nvidia-glx-legacy)), then did sudo nvidia-glx- config enable in the terminal. After a restart X wouldn't come up anymore. I know sudo nvidia-glx-config enable writes a backup, but I didn't remember to which location it writes that backup. So I tried manually editing the xorg.conf file, trying vesa instead of nv or nvidia, I also tried dpkg-reconfigure xserver-xorg, but to no avail. I installed it on a machine I use as a backup machine, so I'd be happy to reinstall Kubuntu entirely and doing the same thing again to reproduce the bug if necessary. ** Affects: linux-restricted-modules-2.6.17 (Ubuntu) Importance: Undecided Status: Unconfirmed -- X won't start after sudo nvidia-glx-config enable https://launchpad.net/bugs/70092 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70095] adept-installer and adept-manager should be one application
Public bug reported: Binary package hint: adept Today I installed Kubuntu 6.10 after not having used Kubuntu since the first release. First thing I wanted to do after the installation was install extra stuff, flash and java. In the K Menu, there is add and remove applications which refers to adept-installer. I tried to use this to search for flash and java and (after enabling universe and multiverse) but I found nothing. I was very confused. Later I figured out that I should have used adept-manager, which is located in the System (or Utilities, don't know exactly anymore) submenu of the K menu. That worked, but it is very confusing that there are two different applications for installing stuff. Can't they be merged in one application? ** Affects: adept (Ubuntu) Importance: Undecided Status: Unconfirmed -- adept-installer and adept-manager should be one application https://launchpad.net/bugs/70095 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63551] Re: X.org doesn't detect widescreen resolution
Thanks for your comments everybody, I didn't expect this many reactions. I also have a notebook with Intel GMA onboard video which required me to install 915resolution in order to get the correct resolution. Essentially it is the same problem, however I filed a different bugreport for that: bug #63560 -- X.org doesn't detect widescreen resolution https://launchpad.net/bugs/63551 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69544] Re: if you type quickly after you start GNOME Terminal, text is in front of your username
If it's not a bug, ok then. But could you please explain in more detail why this is normal behavior? Isn't this an undesirable cosmetic error? Doesn't it look ugly if the username displayed in the terminal is messed up if you start hitting the keyboard to soon? -- if you type quickly after you start GNOME Terminal, text is in front of your username https://launchpad.net/bugs/69544 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69544] if you type quickly after you start GNOME Terminal, text is in front of your username
Public bug reported: Binary package hint: bash Original bugreport is here, posting it here because the GNOME Terminal dev's say they can't fix a slow .bashrc: http://bugzilla.gnome.org/show_bug.cgi?id=358946 GNOME Terminal accepts keyboard input before the username and computername are displayed in it's startup sequence. There is enough time between startup and displaying username and computername to type letters in front of the username and computer name. For example, this can lead to [EMAIL PROTECTED]:~$ becoming [EMAIL PROTECTED]:~$. This looks ugly. I suggest that if this happens, GNOME Terminal moves the typed text to after the username and computer name, e.g. [EMAIL PROTECTED]:~$ should become [EMAIL PROTECTED]:~$ ggg. Steps to reproduce: 1. Open GNOME Terminal, do not type on the keyboard. 2. Observe that the the username and computername are displayed. 3. In my case this is [EMAIL PROTECTED]:~$. 4. Open GNOME Terminal, quickly hit random keys before names are displayed. 5. Observe that keyboard output is now in front of username and computer name. 6. For example [EMAIL PROTECTED]:~$ ** Affects: bash (Ubuntu) Importance: Undecided Status: Unconfirmed -- if you type quickly after you start GNOME Terminal, text is in front of your username https://launchpad.net/bugs/69544 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 33968] Re: dhclient fails when not using UTC in hwclock
It seems this bug is no more, so I took the liberty to close this... ** Changed in: dhcp3 (Ubuntu) Status: Confirmed = Fix Released -- dhclient fails when not using UTC in hwclock https://launchpad.net/bugs/33968 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 33968] Re: dhclient fails when not using UTC in hwclock
I'm currently using the latest Ubuntu 6.10, and the problem seems to be gone for me. -- dhclient fails when not using UTC in hwclock https://launchpad.net/bugs/33968 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 35039] Re: Thumb mouse button doesn't open links in new tabs anymore in Epiphany
Closing this, because this bug report probably doesn't make much sense. If I'm correct the thumb button on the G5 is used by default as the back button for web browsing, not as the middle mouse button (which happens to open links in new tabs in Epiphany). And the fact that it was recognized as the middle mouse button in Breezy was probably and accident, and not functionality to be expected. However, I still think that there should be functionality in GNOME for configuring extra mouse buttons, but that is GNOME-related. I will post a feature request for that in GNOME's Bugzilla. ** Changed in: xserver-xorg-input-mouse (Ubuntu) Status: Confirmed = Rejected -- Thumb mouse button doesn't open links in new tabs anymore in Epiphany https://launchpad.net/bugs/35039 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 62723] Re: Totem doesn't auto-resize
Just found this bug via the search, I'm using Ubuntu 6.10 beta and I'm also experiencing it. As said, resizing doesn't work at all. For example, download this - http://www.gran-turismo.com/jp/movie/index.do?id=385 - video. It's 720p, if I play it with Media Player Classic under Windows XP Media Player Classic auto-resizes to 1:1 and the vid nearly occupies the entire viewable area of my 20 widescreen monitor. In Ubuntu 6.10 beta this video is displayed by Totem in a very tiny window, and the option to resize it to 1:1 doesn't work. Maybe this is related with this bug: https://launchpad.net/distros/ubuntu/+source/totem/+bug/35055 ? -- Totem doesn't auto-resize https://launchpad.net/bugs/62723 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63551] X.org doesn't detect widescreen resolution
Public bug reported: Binary package hint: xorg I have a Dell 2007WFP 20 inch widescreen monitor. It has a resolution of 1680 x 1050 pixels. I booted up the latest Ubuntu 6.10 beta Live CD, and I noticed that the resolution was set at 1280 x 1024, which looked absolutely terrible. With no way to set the correct resolution in System - Preferences - Screen Resolution, I had to edit my xorg.conf and add 1680x1050 to it, as seen below: Section Screen Identifier Default Screen Device NVIDIA Corporation NVIDIA Default Card Monitor DELL 2007WFP DefaultDepth24 SubSection Display Depth 1 Modes 1280x1024 1152x864 1024x768 800x600 720x400 640x480 EndSubSection SubSection Display Depth 4 Modes 1280x1024 1152x864 1024x768 800x600 720x400 640x480 EndSubSection SubSection Display Depth 8 Modes 1280x1024 1152x864 1024x768 800x600 720x400 640x480 EndSubSection SubSection Display Depth 15 Modes 1280x1024 1152x864 1024x768 800x600 720x400 640x480 EndSubSection SubSection Display Depth 16 Modes 1280x1024 1152x864 1024x768 800x600 720x400 640x480 EndSubSection SubSection Display Depth 24 Modes 1680x1050 1280x1024 1152x864 1024x768 800x600 720x400 640x480 EndSubSection EndSection What if I did not know how to edit my xorg.conf? In the worst case scenario I would give up on Ubuntu because it didn't detect the correct resolution and there was no easy way to set the correct resolution. 1280x1024 on a monitor which should be set to 1680x1050 is very annoying to work with, your display is a total blur and with the wrong aspect ration it's all out of proportion. Why can't X.org detect the correct resolution? Windows can. Ubuntu has a serious problem if users of widescreen monitors (which are getting more common) have to edit a config file to get the correct resolution. ** Affects: xorg (Ubuntu) Importance: Undecided Status: Unconfirmed -- X.org doesn't detect widescreen resolution https://launchpad.net/bugs/63551 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63560] installing 915resolution for the correct resolution shouldn't be necessary
Public bug reported: Binary package hint: xorg Recently I got a notebook, a Fujitsu Siemens Amilo 1505 Pi. It has an Intel 945GM chipset and an Intel GMA 950 video chip. Ubuntu works nicely with it, but there is one problem. The display resolution wasn't detected correctly, and installing the package 915resolution fixed this problem. However, just like I said in bug #63551, you can't expect users to know that they have to install the package 915resolution to get Ubuntu set to the correct resolution. New users who don't have the expertise we hardcore Linux fans have do not know they have to install that, and they will be very annoyed that their laptop will not use the correct resolution. Ubuntu should be user friendly, so maybe it would be a good idea to include the fixes in the package 915resolution in X.org by default? ** Affects: xorg (Ubuntu) Importance: Undecided Status: Unconfirmed -- installing 915resolution for the correct resolution shouldn't be necessary https://launchpad.net/bugs/63560 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63578] detects two harddisks, but can only choose one harddisk in manually edit partition table
Public bug reported: Binary package hint: ubiquity I installed Ubuntu 6.10 beta using the Live CD installer. I have two harddisks in my PC, no RAID, and aside from the Live CD installer everything is working fine. When I was going through the Live CD installer, the installer detected my two disks (sda and sdb) at select a disk. When I chose manually edit partition table, I couldn't choose to see sdb from the dropdown box however, only sda. Even though manually edit partition table didn't work for me, I just gave the command to erase sdb (SCSI4) and install there, and the installation went fine. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: Unconfirmed -- detects two harddisks, but can only choose one harddisk in manually edit partition table https://launchpad.net/bugs/63578 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 33968] Re: dhclient fails when not using UTC in hwclock
I'm worried about the amount of attention this bug receives from the developers. I thought Dapper was supposed to be a long term support release? Martin Pitt's (the assignee for this bug) last reply was two months ago, with the question if there are still people having huge problems with this in Dapper. Well, Dapper still doesn't display the correct time here, which is a critical problem for me. I would really appreciate it if this could be fixed. -- dhclient fails when not using UTC in hwclock https://launchpad.net/bugs/33968 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
