[Bug 93491] Re: Crash
Well, I don't know. For the first part, I didn't even know how to reproduce it first when it happened. It crashed, and the crash-reporting tool (was it's name Apport?) popped up and asked me to report the bug, and so I did. Besides, I don't even use ogle anymore. So I think this bug could be closed. Sorry if I have taken up your time unneccessarily. -- Crash https://bugs.launchpad.net/bugs/93491 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 184683] Re: [Gutsy] Occasional hangs at boot when HyperThreading enabled
I have now booted a lot of times with Hardy, with HT enabled, and it works like a charm. So the bug could be closed altogether now. -- [Gutsy] Occasional hangs at boot when HyperThreading enabled https://bugs.launchpad.net/bugs/184683 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 158461] Re: Eclipse documentation not installed
The problem with missing documentation still persists on the Hardy. -- Eclipse documentation not installed https://bugs.launchpad.net/bugs/158461 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 175286] Re: Feature request: save files read-only when invoking external viewers
Yes, everyone here has convinced me that this proposal has more drawbacks than advantages. However, Pluckduck, I'm quite convinced there is a problem for people who are sometimes stupid/sleepy (like me). So no matter how experienced you are, you are still able to make mistakes. And not to talk about newbies, which Ubuntu are supposed to target also. But that said, I think this bug can be closed now. Thanks everyone for your thoughts about this. ** Changed in: firefox (Ubuntu) Sourcepackagename: mozilla-firefox = firefox Assignee: (unassigned) = Pär Lidén (par-liden) ** Changed in: firefox (Ubuntu) Status: New = Invalid ** Changed in: firefox (Ubuntu) Assignee: Pär Lidén (par-liden) = (unassigned) -- Feature request: save files read-only when invoking external viewers https://bugs.launchpad.net/bugs/175286 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 175286] Re: Feature request: save files read-only when invoking external viewers
Now I changed the status to Invalid. Is this the right thing to do, or is there something else that I'm supposed to do also? -- Feature request: save files read-only when invoking external viewers https://bugs.launchpad.net/bugs/175286 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 175286] Re: Feature request: save files read-only when invoking external viewers
Hmm, it seems that you are right, at least with openoffice 2.4 when I just tried. Thanks for your thoughts about this. Well, maybe these are heavy enough arguments to not implement this change in behavior. I still ponder over if there could be some other way to get some kind of protection when a user saves changes to such a temporary file? This would need to be a quite different way of doing it though, and I can't come up with any good ideas for it myself (except for some very complicated solutions). Do you have any ideas for this? ** Attachment added: unnamed http://launchpadlibrarian.net/15050627/unnamed -- Feature request: save files read-only when invoking external viewers https://bugs.launchpad.net/bugs/175286 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 175286] Re: Feature request: save files read-only when invoking external viewers
Well, changing this behavior won't prevent totally stupid users (like me) from doing stupid things. But in the current form as the idea is, it will definitely help to a certain degree. It is more like a quick hack to provide some kind of hint to the user to not do a stupid thing in some situations. Can you see any drawbacks with the idea in it's current form? If there are no significant drawbacks, I can't see any reason to not implement it (except the time involved, and maybe compatibility problems with existing applications relying on the old behavior). -- Feature request: save files read-only when invoking external viewers https://bugs.launchpad.net/bugs/175286 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 12301] Re: monitor off at boot causes bad resolution
This bug is present for me now, using Hardy and a Nvidia Geforce 4 MX card, Philips 201b4 monitor. I think it used to work in Gutsy, but don't do after the upgrade. Booting up with the monitor turned off gives low resolution (640x480), and it get's fixed if I restart X after turning monitor on. So the bug should probably be reopened. -- monitor off at boot causes bad resolution https://bugs.launchpad.net/bugs/12301 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 65071] Re: Hang on boot when Sandisk Cruzer Micro USB-stick attached
Again a video clip for the kernel bugzilla ** Attachment added: Failed boot - git build.avi http://launchpadlibrarian.net/13538636/Failed%20boot%20-%20git%20build.avi -- Hang on boot when Sandisk Cruzer Micro USB-stick attached https://bugs.launchpad.net/bugs/65071 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 65071] Re: Hang on boot when Sandisk Cruzer Micro USB-stick attached
** Summary changed: - Hang on coldboot when USB-stick attached + Hang on boot when Sandisk Cruzer Micro USB-stick attached -- Hang on boot when Sandisk Cruzer Micro USB-stick attached https://bugs.launchpad.net/bugs/65071 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 65071] Re: Hang on boot when Sandisk Cruzer Micro USB-stick attached
** Description changed: Binary package hint: linux-image-2.6.15-27-686 I have a problem with the kernel in ubuntu 6.06. When I have my USB- stick attached, it just hangs at boot. This is not a very severe problem, because it does boot correctly when the usb-stick is not attached, and it seems to be only on coldboots on which the system hangs, so if I restart the system with it attached, it uses to work, or if I push the reset button when it has hanged, it will also work. Pressing ctrl-alt-del wont work. At least this is what happened when I just tried to test the problem a bit today, maybe it has been so that it has hanged even on restarts sometimes, I don't really remember that. This is what it says before it hangs:Booting 'Ubuntu, kernel 2.6.15-27-686' root (hd0,4) Filesystem typ ext2fs, partition type 0x83 kernel /boot/vmlinuz-2.6.15-27-686 root=/dev/sda5 [Linuz-bzimage, setup = 0x1c00, size=0x1170433] initrd /boot/initrd.img-2.6.15-27-686 [Linux-initrd @0x1f948000,0x6a78b3 bytes] savedefault boot Uncompressing Linux... Ok, booting the kernel And then it just waits there forever. + + [Edit: The info above is old info and mostly irrelevant, see below for + up-to-date info.] + My system: ASUS P4C800 Motherboard, P4 2.8 GHz, 2x 512 mb Corsair memory Seagate ST3120023AS harddisk, SATA 120gb Nvidia GeForce 4Mx graphics card Logitech Cordless keyboard, attached to usb ps2 mouse Plextor cd-writer samsung dvd-reader I was before a bit used to dealing with the kernel stuff, to the degree that I used to compile my own kernels and things like that, so if you want me to test things like that, I probably knows how to do that. -- Hang on boot when Sandisk Cruzer Micro USB-stick attached https://bugs.launchpad.net/bugs/65071 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 65071] Re: Hang on coldboot when USB-stick attached
Yes, Zhang Rui suggested that I should check out that bug also (at kernel bug 10406). I've been looking there, but I don't really understand how to check out if mine is a duplicate of that. The difference seems to be that for me just certain usb-devices cause the hang, and at bug 6208 every device will cause a hang. A mouse, a keyboard and a digicam I own seems to work fine. That seems to be the main difference between me and those people at that bug. The usb-stick which caused me originally to report this problem (above) is now dead, so I can't test that one again unfortunately. Do you have any suggestions on how to further investigate the inter- connectedness of the that bug and mine? I know I haven't tried hard enough myself to check that yet, so maybe I'm not qualified to ask that question for now... ;-) When I get the time I could do some more testing, like testing with the Ubuntu 7.04 kernel and some other tests. -- Hang on coldboot when USB-stick attached https://bugs.launchpad.net/bugs/65071 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 65071] Re: Hang on coldboot when USB-stick attached
I'm now reporting this bug upstream, but the kernels bugzilla doesn't accept files larger than 1 meg, so I upload it here instead. ** Attachment added: Boot hang 2.6.25-rc8.avi http://launchpadlibrarian.net/13148876/Boot%20hang%202.6.25-rc8.avi ** Changed in: linux (Ubuntu) Sourcepackagename: linux-source-2.6.15 = linux ** Bug watch added: Linux Kernel Bug Tracker #10406 http://bugzilla.kernel.org/show_bug.cgi?id=10406 ** Also affects: linux via http://bugzilla.kernel.org/show_bug.cgi?id=10406 Importance: Unknown Status: Unknown -- Hang on coldboot when USB-stick attached https://bugs.launchpad.net/bugs/65071 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 65071] Re: Hang on coldboot when USB-stick attached
Looks like I forgot to attach the video clip... It ends with the message: ACPI: Looking for DSDT in initramfs... error, file /DSDT.aml not found and then just halts. I'm not able to take ctrl-alt-del, I have to do a hard reset. ** Attachment added: mvi_1351.avi http://launchpadlibrarian.net/13115650/mvi_1351.avi -- Hang on coldboot when USB-stick attached https://bugs.launchpad.net/bugs/65071 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 65071] Re: Hang on coldboot when USB-stick attached
Maybe the BIOS could be to blame, so I post this one also. ** Attachment added: dmidecode.out http://launchpadlibrarian.net/13065120/dmidecode.out ** Changed in: linux-source-2.6.15 (Ubuntu) Status: Fix Released = New -- Hang on coldboot when USB-stick attached https://bugs.launchpad.net/bugs/65071 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 65071] Re: Hang on coldboot when USB-stick attached
** Attachment added: lspci-vvnn.log http://launchpadlibrarian.net/13059463/lspci-vvnn.log -- Hang on coldboot when USB-stick attached https://bugs.launchpad.net/bugs/65071 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 65071] Re: Hang on coldboot when USB-stick attached
I'm experiencing this bug again, both on Ubuntu 7.10, and on Hardy Heron. I attach a little video snapshot which shows what happens in the boot when the usb-stick is attached. The results posted here are for Hardy Heron. My original usb-stick got destroyed, so I don't know if the bug applies to that one still. This is with a Sandisk Cruzer Micro 512mb. uname, dmesg, and lspci are on a subsequent boot with the usb-stick connected. uname -a: Linux loa-desktop 2.6.24-12-generic #1 SMP Wed Mar 12 23:01:54 UTC 2008 i686 GNU/Linux ** Attachment added: dmesg.log http://launchpadlibrarian.net/13059072/dmesg.log -- Hang on coldboot when USB-stick attached https://bugs.launchpad.net/bugs/65071 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 65071] Re: Hang on coldboot when USB-stick attached
** Attachment added: version.log http://launchpadlibrarian.net/13061734/version.log -- Hang on coldboot when USB-stick attached https://bugs.launchpad.net/bugs/65071 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 174434] Re: [ATI X1300] Could not generate /etc/X11/xorg.conf.failsafe
With the Beta1 live-cd, X works fine for me. So this bug seems to be solved for me! :-) Sadly, there are still multiple other bugs left affecting my hardware... :-( Cheers to the developers! -- [ATI X1300] Could not generate /etc/X11/xorg.conf.failsafe https://bugs.launchpad.net/bugs/174434 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 88746] Re: ehci_hcd module causes I/O errors in USB 2.0 devices
I think the rationale for the won'f fix stamp is that the kernel team deamed it unlikely tha this bug would get fixed in time for Hardy. Probably they will try to fix it for later Ubuntu versions (hopefully the 8.10). So the won't fix stamp should probably be read as: won't fix for Hardy, if I've understood things correctly. 2008/3/5, Ric Flomag [EMAIL PROTECTED]: Robert: Yes I did try your procedure too, no luck. As for the Won't fix stamp, the log says that we should ask Henrik :) -- ehci_hcd module causes I/O errors in USB 2.0 devices https://bugs.launchpad.net/bugs/88746 You received this bug notification because you are a direct subscriber of the bug. -- ehci_hcd module causes I/O errors in USB 2.0 devices https://bugs.launchpad.net/bugs/88746 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 184683] Re: [Gutsy] Occasional hangs at boot when HyperThreading enabled
Thanks for your post. I have already Hardy installed on the computer, and has booted a few times without problems. But it's a bit difficult to know if the bug is actually gone or not as it just happens once in maybe 10 or 20 times, (seemingly random, however just on cold-boots I think). I have saved all log files from most of the failing boots, if there would be any use to attach some of them, please tell me. I will anyways try to boot some more times with Hardy, and see if the bug still appears. -- [Gutsy] Occasional hangs at boot when HyperThreading enabled https://bugs.launchpad.net/bugs/184683 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 88746] Re: ehci_hcd module causes I/O errors in USB 2.0 devices
From what I've seen on another (GNOME) bug, some of the info entered in the LP bug was also forwarded to gnome bugzilla by the developer. But I don't think this always happens though. For those of you here who are really interested in getting the bug fixed, I strongly recommend you should report it yourself upstream. You might look at this link for more info on that: https://wiki.ubuntu.com/KernelTeam/GitKernelBuild. From what I've seen, the kernel developers are generally much more responsive about bug reports than the ubuntu developers. But you have to test with the upstream kernel versions for that, and follow their guidelines for reporting bugs. This might be helpful: http://www.kernel.org/pub/linux/docs/lkml/reporting-bugs.html. You also have to enable some debugging in the compilation, I think there is an USB_DEBUG option or similar. Probably this bug exists in many flavors, one is where USB_SUSPEND is the cause, but there are many others. Some of you have reported that it worked with a certain kernel version, but then stopped working. If you can find out precisely at what upstream -git version it broke, you have probably come a long way towards fixing the bug. But it is a lot of work in testing out that of course, and trying many different versions until you nail down the correct one. Comments https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88746/comments/79and https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88746/comments/177above lists some of the upstream bugs about this, which might be helpful. -- ehci_hcd module causes I/O errors in USB 2.0 devices https://bugs.launchpad.net/bugs/88746 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
Re: [Bug 184683] Re: [Gutsy] Occasional hangs at boot when HyperThreading enabled
Ok, thanks for that information. Then I have no clue about how to debug this problem. Hope someone else might see this and help out with the bug. -- [Gutsy] Occasional hangs at boot when HyperThreading enabled https://bugs.launchpad.net/bugs/184683 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
Re: [Bug 88746] Re: ehci_hcd module causes I/O errors in USB 2.0 devices
@Elias: I don't mean to sound rude, but it feels for me that you have no problem complaining about what others should and should not do, but then you are yourself not ready to do much about it. Well, you might say that Ubuntu is a proprietary project, because there is a corporation behind it, but all code it produces are completely free and open-source. Many developers work totatally for free on Ubuntu. I suggest that instead of telling others what to do, you just go ahead and do it yourself. I understand that you may not have the time for that, but maybe you would then understand that other people (the paid developers) also has a lot of other work to do, and maybe does not have time for your favorite issue? And regarding bug 3382: Yes, I agree with you, it sounds like a good idea, great thinking from you Elias. But, please, I ask you, could you stop posting about it here in this bug? I at least would be happy if you wouldn't. You have already posted about it many times here, you don't need to post it again. I think the message has gone through clear to everyone here. Also, if you would to like to support the developers in some way to do a better job, you would be much better of giving words of encouragement, instead of words of complain. I am totally sure that you criticising them won't give them any more energy (and definitely not any more time) to work on development. This is meant as a friendly advice, I hope you don't feel dismayed or something. I also want take the opportunity to thank the developers for all the hard work they are doing, from which I can benefit completely for free. 2008/2/9, Elias Humbolt [EMAIL PROTECTED]: @Ben Collins Ben, I am happy that somebody from Ubuntu is finally reacting to this Bug report. If not for fixing it than at least with an official statement what devs are actually thinking about the issue. And why obvious simple measures are not taken. Your argumentations surely is not bare any logic. My first reaction however was, well if suspend/resume is ought to be broken after removing/disabling the autosuspend feature, why can I still successfully suspend/resume on my laptop after disabling it. So now I have both, USB 2.0 and suspend/resume. You understand that some doubts did arise in me about your claim removal of autosuspend might screw up suspend/resume for many people. However, these doubts do not have many grounds just yet, except for my single perception on one type of system. Therefore I presume what you are claiming are well tested facts. I am wondering however, if it would not be possible to enable autosuspend for the one crowd of chipsets while disabling it for the other. Sure, not an easy task to identify, which systems to enable and which not. Extracting all this information from bug reports surly is hell. And yet, if you have talked everybody into submitting their data again, you still will have to ask all of them to test whether or not disabling autosuspend breaks suspend/resume for them. This is a challenge for itslef. Undoable if you ask me, at least with the tools available. I therefore understand, why literally nothing is done about it! Undoable, well not if Launchpad had the proper toolset for this! I actually proposed a feature which would enable you to handle a task like that: The attach HW profiles to launchpad accounts I proposed a while ago. https://bugs.launchpad.net/bugs/3382 I just had a couple of more ideas on how else this feature could be used with a little more code. Oh man, somebody needs to implement that! Have a look. I am happy to share the idea, but I wont code for free on a proprietary project. And well, the idea was mine, so don't start crying if RedHat or anybody else is copying it. This idea is a free for all still! Imagine how much better bug tracking would work if you could start a simple poll: Does disabling autosuspend fix your USB2.0 problem ? yes/no Does disabling autosuspend break your suspend/hibernate/resume? yes/no If more than one HW profile is registered with your launchpad account the following question shows up: Select the systems these answers apply to ? Choose form list. And at the end you would know not just for how may people disabling autosuspend works ... but also what chipsets are affected! Wouldn't that be coding hours wisely spent? Whether you use it for the ehci_hcd bug or any other HW related bug in the future? I am sure kernel devs upstream would be happy to whitelist/blacklist autosuspend accordingly if they were provided a detailed list for whom, wouldn't they? I'd be delighted if you would share your thoughts on the feature I proposed for launchpad as well as on whether or not it could be a viable solution to whitelist/blacklist autosuspend in kernel if the proper information would be available for whom. On Mon, 2008-02-04 at 21:13 +, Ben Collins wrote: Elias, you are over simplifying this issue. If we disable
Re: [Bug 184692] Re: [Hardy] screen flashes blank four times when X loading, X not coming up, ATI X1250
I have now tested with alpha4, it seems to behave in exactly the same way, the screen flashes blank fout times when it is trying to load X when starting from the live-cd. The alternate-installer still hangs during the installation-process (at a later stage than alpha3, but nevertheless hangs completely). So, sorry, no progress here. And (FYI), I'm traveling abroad now for six weeks, and I'm not able to take this computer with me, so unfortunately I will not be able to do any testing before mid/end of march something. But I will do some testing then when I comes back. -- [Hardy] screen flashes blank four times when X loading, X not coming up, ATI X1250 https://bugs.launchpad.net/bugs/184692 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 184692] Re: [Hardy] screen flashes blank four times when X loading, X not coming up, ATI X1250
Hello again, I noticed that I forgot to mention that it behaves the same way if I start up in failsafe graphics mode, no difference there. And the live-cd also sometimes hangs on boot-up even if the wireless is disabled. I also tried using the alternate-installer, but it hangs somewhere even before it comes to start X. So it looks like this machine has multiple problems with Linux. -- [Hardy] screen flashes blank four times when X loading, X not coming up, ATI X1250 https://bugs.launchpad.net/bugs/184692 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
Re: [Bug 98955] Re: logd not running
Ok, I see. Well, then this behavior is probably preferred. Thankyou 2008/1/27, Sergei Ivanov [EMAIL PROTECTED]: Yes, I sure understand that you don't want to be a maintainer for it, that would probably be quite a lot of work. For me the [ok] comes on it's own separate: Sun Jan 27 21:52:32 2008: * Starting system message bus dbus Sun Jan 27 21:52:32 2008: [ OK ] Is this intentional? Otherwise this seems much nicer than before. Well, bootlogd *has* a maintainer, it's Debian sysvinit team. Maybe I'll send the fixes there some day. The OK placement is yes, sort of intentional. They use a lot of terminal trickery to make output look better, and logging it correctly would require many changes to the code. I had to choose from a couple of simple rules, and the other choices led to worse results. After all, this OK is a separate message and its timing may be useful. You can make it appear on the same line by changing the source as follows. Go to bootlog.c line 361, there will be a part of switch like this: case '\n': case '\r: ... Change it to: case '\r': break; case '\n': ... (that is, interchange the two cases and insert break; between them). But then you will lose, among other things, the summary of a long fsck run (it will be truncated as a part of one extra long line). -- logd not running https://bugs.launchpad.net/bugs/98955 You received this bug notification because you are a direct subscriber of the bug. -- logd not running https://bugs.launchpad.net/bugs/98955 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
Re: [Bug 98955] Re: logd not running
Yes, I sure understand that you don't want to be a maintainer for it, that would probably be quite a lot of work. For me the [ok] comes on it's own separate: Sun Jan 27 21:52:32 2008: * Starting system message bus dbus Sun Jan 27 21:52:32 2008: [ OK ] Is this intentional? Otherwise this seems much nicer than before. Keep up the good work! 2008/1/26, Sergei Ivanov [EMAIL PROTECTED]: I am not willing to maintain it seriously, it is too system-dependent. Nevertheless, here is a new version. Changes are: - Improved logfile formatting. - The logfile is renamed to /var/log/bootmsg, to avoid conflict with logd in the future. Again, please do not install it blindly. You cannot be sure that I am not giving you a trojan. ** Attachment added: bootlogd_2.86.02.tar.gz http://launchpadlibrarian.net/11578525/bootlogd_2.86.02.tar.gz -- logd not running https://bugs.launchpad.net/bugs/98955 You received this bug notification because you are a direct subscriber of the bug. -- logd not running https://bugs.launchpad.net/bugs/98955 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 184692] Re: [Hardy] screen flashes blank four times when X loading, X not coming up, ATI X1250
** Summary changed: - [Hardy] screen turns blank when X loading, ATI X1250 + [Hardy] screen flashes blank four times when X loading, X not coming up, ATI X1250 -- [Hardy] screen flashes blank four times when X loading, X not coming up, ATI X1250 https://bugs.launchpad.net/bugs/184692 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 98955] Re: logd not running
Segei: I think you forgot to attach the actual file. ;-) Your description of it seems very nice though, I hope they could include a package like this in the universe. I think many users would appreciate that possibility. Maybe even a package from you, if you would have the time to be maintaining it? Cheers Pär -- logd not running https://bugs.launchpad.net/bugs/98955 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
Re: [Bug 98955] Re: logd not running
Ok, I see, then you did not forget it after all. :-) I installed your version, it works nicely for me, and the /var/log/boot file looks nicer than it did with my old one. Thankyou for this work. Maybe you could submit this package to getdeb.net for inclusion in their archive, along with some warning that it may not work on all system? Just a thought though. 2008/1/25, Sergei Ivanov [EMAIL PROTECTED]: I did attach it! Maybe launchpad does not allow this via email. Now I am trying to do this using the web interface. ** Attachment added: bootlogd_2.86.01.tar.gz (unofficial package) http://launchpadlibrarian.net/11569042/bootlogd_2.86.01.tar.gz -- logd not running https://bugs.launchpad.net/bugs/98955 You received this bug notification because you are a direct subscriber of the bug. -- logd not running https://bugs.launchpad.net/bugs/98955 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 98955] Re: logd not running
I think there is a good reason that they are not using bootlogd by default. I think I read somewhere that bootlogd is quite buggy on some systems, and it is hard to make it work correctly the way it is designed. So the proper fix in the long run would be to redesign it completely, as Scott is intending to do with logd in the future. I don't remember where I read this however... Probably tekknokrat ran into one of those problems. You may try the original 2.86 version, it may work better? -- logd not running https://bugs.launchpad.net/bugs/98955 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 184692] Re: [Hardy] screen turns blank when X loading, ATI X1250
Hello, I've done some further testing, and I've actually found that the probably the wireless driver is to blame for the lockups. 64-bit or 32-bit does not seem to make any difference. If I disable the wireless functionality by pressing that button on the computer, it won't lock up. X is still acting quite weirdly though. It generates two log files, but the only difference seems to be the time: [EMAIL PROTECTED]:~$ diff Xorg.0.log Xorg.0.log.old 23c23 (==) Log file: /var/log/Xorg.0.log, Time: Thu Jan 24 21:52:27 2008 --- (==) Log file: /var/log/Xorg.0.log, Time: Thu Jan 24 21:52:20 2008 Note: I'm using the 64-bit version from now on. ** Attachment added: Xorg.0.log http://launchpadlibrarian.net/11532044/Xorg.0.log -- [Hardy] screen turns blank when X loading, ATI X1250 https://bugs.launchpad.net/bugs/184692 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 184692] Re: [Hardy] screen turns blank when X loading, ATI X1250
I booted again, and this time Xorg.0.log.old was exactly the same as the one posted above (except for the time), however Xorg.0.log was different. ** Attachment added: Xorg.0.log-second_boot http://launchpadlibrarian.net/11532182/Xorg.0.log-second_boot -- [Hardy] screen turns blank when X loading, ATI X1250 https://bugs.launchpad.net/bugs/184692 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 184692] Re: [Hardy] screen turns blank when X loading, ATI X1250
I also made a little video shot of this boot. Notice how the screen blanks four times. The computer is perfectly usable in terminal mode (net access via cable) and works without any lockups. btw: $ which xresprobe /usr/sbin/xresprobe so it's still there. However, the xresprobe bug seems quite different, as it happened in a later stage of the install, and not at the bootup of the live cd. ** Attachment added: booting.avi http://launchpadlibrarian.net/11532218/booting.avi -- [Hardy] screen turns blank when X loading, ATI X1250 https://bugs.launchpad.net/bugs/184692 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 184692] Re: [Hardy] screen turns blank when X loading, ATI X1250
** Attachment added: xorg.conf http://launchpadlibrarian.net/11532229/xorg.conf -- [Hardy] screen turns blank when X loading, ATI X1250 https://bugs.launchpad.net/bugs/184692 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 184692] Re: [Hardy] screen turns blank when X loading, ATI X1250
lspci-nn |grep VGA 01:05.0 VGA compatible controller [0300]: ATI Technologies Inc RS690M [Radeon X1200 Series] [1002:791f] and attaching full output of lspci -vvnn ** Attachment added: lspci-vvnn http://launchpadlibrarian.net/11532240/lspci-vvnn -- [Hardy] screen turns blank when X loading, ATI X1250 https://bugs.launchpad.net/bugs/184692 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 184692] Re: [Hardy] screen turns blank when X loading, ATI X1250
** Attachment added: ooutput of /proc/acpi/dsdt http://launchpadlibrarian.net/11532263/dsdt -- [Hardy] screen turns blank when X loading, ATI X1250 https://bugs.launchpad.net/bugs/184692 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 184692] Re: [Hardy] screen turns blank when X loading, ATI X1250
** Attachment added: uname-a.log http://launchpadlibrarian.net/11532305/uname-a.log -- [Hardy] screen turns blank when X loading, ATI X1250 https://bugs.launchpad.net/bugs/184692 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 184692] Re: [Hardy] screen turns blank when X loading, ATI X1250
** Attachment added: version.log http://launchpadlibrarian.net/11532308/version.log -- [Hardy] screen turns blank when X loading, ATI X1250 https://bugs.launchpad.net/bugs/184692 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 184692] Re: [Hardy] screen turns blank when X loading, ATI X1250
I tried installing xorg-driver-fglrx, but that didn't seem to make any difference. I also did a few times sudo /etc/init.d/gdm restart What is strange, it that alternately it yields a [OK] to stopping, but [fail] on starting, and nothing more. And alternately [ok] on both, and same error as described above (screen blanking four times, and then nothing more). This is the same regardless if fglrx is installed or not. Hope this could be of some help in investigating the problem. Please tell me if there is any additional testing you think I should do. I'd also like to test installing with alternate installer. To do this, I need to shrink my existing partition where windows is installed. The most difficult part of this is however getting my wifes permission, which could probably be quite tricky... So it could probably take some time... ;-) If I get the time I might try to debug and report that problem with the wireless also. -- [Hardy] screen turns blank when X loading, ATI X1250 https://bugs.launchpad.net/bugs/184692 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 184692] Re: [Hardy] screen turns blank when X loading, ATI X1250
Thanks for your fast reply, I will try out those solutions you suggested as soon as I get the time. -- [Hardy] screen turns blank when X loading, ATI X1250 https://bugs.launchpad.net/bugs/184692 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 184683] [Feisty] Occasional hangs at boot when HyperThreading enabled
Public bug reported:
Binary package hint: upstart
I'm having a problem with occasional bootup hangs. They started after I
upgraded to Gutsy. I never experienced this problem with Ubuntu 7.04.
Most of the times there is no problem, but maybe once out of 10 or 20
bootups the booting process stops. Since I disabled HT, I've never seen
this happen anymore.
What happens is this: Almost all of the booting process works fine, but
after it has come to Running local boot scripts (/etc/rc.local), not
much more happens. X is not coming up.
The first strange thing is that it says Reloading OpenBSD Secure Shell
server's configuration sshd. I have no idea why it does this. According to
/var/log/boot, it does this every time I boot though. After that (a few of the
times it has hung), it also started reloading cupsd (after a minute or so), and
then the system log daemon. Some other times it just hung after Reloading
openbsd..., and nothing more happend.
After that nothing more seems to happen with the booting. I am able to access
other VTs and Internet acess works, so the machine is not really hung, it is
just the booting process which won't get any further.
The reason why I guess the problem lies within Upstart is because the
reloading of the daemons, but this is mostly a guess on my part.
I have a suspicion that it is in some way related to the networking.
That could at least explain why it just happens at some boots, and not
at others. Maybe my router is a bit flaky, and sometimes uses longer
time (which could in turn trigger some bug in Ubuntu). But this is just
a another guesss.
The computer itself is a 4 year old Pentium 4 2.8 ghz, 1 gig ram, with a
ASUS P4C800 mobo, connected to the router through the built-in ethernet
port, ps2 mouse and usb keyboard, nvidia graphics card.
This bug might be related to #58752.
I have been digging through the logs (/var/log) to try and see if there
is something particular happening with the boots when the booting
freezes. I haven't found something which is only in the logs those times
the boot process stops. However, I've found some things which seems a
bit wrong, but these errors are in the logs even on those boots which
works. But maybe they are related despite that. Below are excerpts from
the log files, with just the lines reporting errors I could find listed
(# denotes that the line is my comment). Maybe there are other errors I
missed. If you wish, you might check these error messages out.
in kern.log:
Failure registering capabilities with primary security module.
intel_rng: FWH not detected
in daemon.log:
#Networkmanager warns several times about dhcdbd not running, lines such as
NetworkManager: WARN nm_dhcp_manager_get_state_for_device(): dhcdbd not
running!
#(However, eventually DHCP and the network connection will work)
avahi-autoipd(eth1)[5887]: fopen() failed: Permission denied
# (The network connection actually used is eth0)
#many errors about ntpd
NetworkManager: WARN nm_spawn_process(): nm_spawn_process('/usr/sbin/nscd -i
hosts'): could not spawn process. (Failed to execute child process
/usr/sbin/nscd (No such file or directory))
in boot:
/etc/rcS.d/S40ifrename: 19: /sbin/ifrename: not found
When comparing boot and daemon.log, I can see that dhclient gets a
DHCPACK a couple of seconds after the dhcbd is started, 8-12 secs for
those boots I investigated.
Is there someone here who has got any suggestion of what to do?
Specifically if you has any ideas of how to debug this problem, and what
sorts of things I should look for (in the logs and elsewhere). I really
don't know how to proceed investigating this problem. This must be some
kind of bug in Ubuntu, but I don't know what causes the bug.
Notes:
- in order to get /var/log/boot to work, I had to manually compile and
install bootlogd. I did this in order to be able to debug these problems
better. The problems existed before this, so this should not affect the
booting process in any negative way.
- This is a desktop computer with a wired net connection, so those
things about Networkmanager probably has nothing do to with this
problem.
- I was also watching top, and noticed almost no activity, except for
updatedb at around 3% cpu utilisation one of the times this happened.
Otherwise nothing.
Thankyou
Pär
** Affects: upstart (Ubuntu)
Importance: Undecided
Status: New
--
[Feisty] Occasional hangs at boot when HyperThreading enabled
https://bugs.launchpad.net/bugs/184683
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 184692] [Hardy] screen turns blank when X loading, ATI X1250
Public bug reported: Binary package hint: xserver-xorg I have an ATI Raderon X1250 card, using a hp 6715s notebook with an amd sempron 3600+ processor (64-bit capabale) and 1gig ram. Using the alpha2 live cd, I got exactly the same error message as those in bug #174434. I tried to copy over all the relevant log files via ssh to post them there. But before I had the time to do that, the screen just turned black, and the computer froze completely. This happened several times, every time within a few minutes. So, every time, before I had the time to scp the files over, the computer froze. With the alpha3 live-cd, things has gotten worse: - With usplash enabled it get's quite far in the booting process, and then suddenly just turns blank, and freezes completely, at about the time that I suppose that X should begin loading. - If I disable usplash it will come past starting gdm, then switch between blank screen and the bootup-text screen a few times, and after that nothing happens. I'm still able to use the computer in terminal-mode, but it does not even put out an error message that configuring X failed, like it did with alpha2. Maybe my problem with the freezing is due to something else than X, i don't know, but it seems quite likely as it freezes as the screen turns blank, and about the same time when X was supposed to start. Note: This notebook did not work with Gutsy either. I'm using the 32-bit version of ubuntu. Testing results from the laptop team about Feisty and Gutsy: https://wiki.ubuntu.com/LaptopTestingTeam/HPCompaq6715s. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- [Hardy] screen turns blank when X loading, ATI X1250 https://bugs.launchpad.net/bugs/184692 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 136529] Re: Can't log in after upgrading
There seems to be different problems reported at the same bug number here. One problem is caused by gnome-keyring. Killing gnome-keyring makes the boot proceed. The latest updates seem to solve the problem mostly for me, but I have experienced still at least one time where I had to kill gnome-keyring. This problem is related to bug #175682, and gnome bug #502603 (http://bugzilla.gnome.org/show_bug.cgi?id=502603), and affects only users of gdm. Then there seems to be some people where the bug is fixed by changing /tmp permissions, others change keyboard layouts, switch video drivers, and so on. Shouldn't those be separated, and each put in it's own bug, as it quite clearly must be completely different underlying problems? Just that the symptom is the same, log in hangs. Just a thought, but I'm not the one in charge here though. ;-) -- Can't log in after upgrading https://bugs.launchpad.net/bugs/136529 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 184683] Re: [Gutsy] Occasional hangs at boot when HyperThreading enabled
** Summary changed: - [Feisty] Occasional hangs at boot when HyperThreading enabled + [Gutsy] Occasional hangs at boot when HyperThreading enabled -- [Gutsy] Occasional hangs at boot when HyperThreading enabled https://bugs.launchpad.net/bugs/184683 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 174434] Re: [ATI X1300] Could not generate /etc/X11/xorg.conf.failsafe
Well, they were exactly the same for alpha2, so I would not say they are completely different. However, I will file this as a new bug whenever I get the time. Thanks for your advice. -- [ATI X1300] Could not generate /etc/X11/xorg.conf.failsafe https://bugs.launchpad.net/bugs/174434 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 174434] Re: [ATI X1300] Could not generate /etc/X11/xorg.conf.failsafe
I have an ATI X1250 card, using a hp 6715s notebook with an amd sempron 3600+ processor and 1gig ram. Using alpha2, I got exactly the same error message as the others here. I tried to copy over all the relevant log files via ssh to post them here. But before I had the time to do that, the screen just turned black, and the computer froze completely. This happened several times, every time within a few minutes. So, every time, before I had the time to scp the files over, the computer froze. With alpha3, if I disable usplash this will happen: It will come past starting gdm, then switch between blank screen and the bootup-text screen a few times, and after that nothing happens. I'm still able to use the computer in terminal-mode, but it does not even put out an error message that configuring X failed. With usplash enabled it get's quite far in the booting process, and then suddenly just turns blank, and freezes completely. So alpha3 works worse for me. Maybe my problem with the freezing is due to something else than X, i don't know, but it seems quite likely as it freezes as the screen turns blank, and about the same time when X was supposed to start. It's quite hard to investigate any further when it is completely frozen. ;-) Note: This notebook did not work with Gutsy either. I'm using the 32-bit version of ubuntu. -- [ATI X1300] Could not generate /etc/X11/xorg.conf.failsafe https://bugs.launchpad.net/bugs/174434 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 136529] Re: Can't log in after upgrading
I want to add to jtholmes summary above about the problem: for me logging in did not work even the first time on the first boot. I had to try several times before I got a successful login. What did solve the problem for me however, was putting the computer in uniprocessor mode, ie. disabling Hyperthreading in my case. What seems to be common for me and some other people here is that I have an Nvidia graphics card. -- Can't log in after upgrading https://bugs.launchpad.net/bugs/136529 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 136529] Re: Can't log in after upgrading
Debian bug 455 694 seems to be solved as the source for the setuid/setgid messages are fixed. However, those messages are still there for me, even though login and the rest of the system works perfectly. So in my case, this will probably not solve the problem. -- Can't log in after upgrading https://bugs.launchpad.net/bugs/136529 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 179552] Re: [Hardy] gnome-session hangs on log in
*** This bug is a duplicate of bug 136529 *** https://bugs.launchpad.net/bugs/136529 Hello, Bernhard, this bug has just marked as a duplicate of https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/136529 by the developers, so I suppose you should file your information there. Also, as a suggestion from another user, you might want to try turning of the dual-core functionality of your computer. You might do so either in the bios, or perhaps with acpi=off. Maybe booting in uniprocessor mode will work-around the problem. This solved the problem for me (albeit mine is just hyperthreaded, not real dual-core). -- [Hardy] gnome-session hangs on log in https://bugs.launchpad.net/bugs/179552 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 136529] Re: Can't log in after upgrading
Hello, I've had this problem too. At first I reported it as https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/179552, but found out that mine must be a duplicate of this bug. I found out that if I disable Hyperthreading in the bios, it works perfectly. The GTK setuid/setgid error messages are still there, so they are probably totally unrelated to the bug itself. As this problem seems to happen a bit unpredictably, I believe that it is some sort of race condition in some multithreaded part of gnome-session, or between different processes. Another argument for that theory is that when I strace'd gdm (like Adrian did), login worked almost all of the times (usually something was broken when I was logged in though, such as the terminal not starting). I have no kind of authority around here, ;-) but I would anyway suggest that everyone here tries disabling hyperthreading/smp, ie booting in uniprocessor mode. I'd also like to repeat a finding I did and reported at that other bug, which I've not seen anyone here report: By echo'ing messages in the startup files, I've confirmed that it runs through /etc/gdm/PreSession/Default. Then it runs through /etc/gdm/Xsession, however, that script calls /etc/X11/Xsession.d/99x11-common-start, which calls /usr/bin/gnome-session and after that, I can see no more output from the script. This indicates the problem lies within gnome-session. My computer is a desktop, Pentium 4 2.8 Ghz, asus P4C800 motherboard with Intel 875P chipset, 1 Gb ram, wired net connection. I'm using Hardy, installed from alpha2, with latest updates applied. It works fine under Gutsy on the same machine. -- Can't log in after upgrading https://bugs.launchpad.net/bugs/136529 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 179552] Re: gnome-session hangs on log in
I've tried to find out which programs constitute to those pids in .xsession-errors, but I've been unable to find out that. However. if the pid of gnome-session is x, then the first of the pids in .xsession- errors is a little bit higher than x, maybe x+[34], and the and the next is maybe x + [8-10]. I wrote a small shell script that would do ps ax to a file every 0.01 second, and between two file outputs, it seems that those pid hase managed to both start and disappear, so it happens very fast. What is very odd, is that once when I did ran this script and logged in, it did work! Then I immediately logged out and in, and since then it has not worked again. :-( ps ax reveals that gconfd-2 is running, with pid=x + ~50-60, and gnome- keyring-daemon, pid = x - [1-3] Hope this could be of some relevance. What would probably be helpful is to found out which programs constitute to those pids, but I am not skilled enough in Linux to find out that by myself unfortunately. Could anyone please tell me how to find out this? ** Summary changed: - gnome-session hangs on log in + [Hardy] gnome-session hangs on log in -- [Hardy] gnome-session hangs on log in https://bugs.launchpad.net/bugs/179552 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 179552] Re: [Hardy] gnome-session hangs on log in
Ok, I've investigated the problem a little further, and there seems to be many more people that experienced the same sort of error message with various versions of gnome, both on fedora, debian and ubuntu, for example here http://ubuntuforums.org/showthread.php?t=585635page=13, here http://forums.fedoraforum.org/archive/index.php/t-113359.html, and here bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=456824. I want to add some things: - /tmp looks fine - Gutsy works fine on the same machine - large amount of diskspace free on / so that is not the problem - gnome failsafe works equally bad - I tried waiting over 10 minutes, no difference - screen just plainly brown, nothing else. but the mouse-pointer works though - adding another user with adduser and logging in with that makes no difference - deleting /etc/profile and ~/.* doesn't help - i did sudo apt-get install --reinstall gnome-session, and then I could login once. strange. but no success on subsequent logins though. repeating the re-install helped nothing, so maybe that was just a coincidence. - I actually managed to log in once more, and checked .xsession-errors. The same error were there. I did some strace'ing, and I found this: The two pids reported are gdmflexiserver. What is very strange, is that it seems that every time I do an strace of gdm, I seem to be able to actually log in (but things usually don't work very well once I'm logged in though). A few times I got in there completely and things worked. Once I came in there, and firefox and terminal worked, but not logout. Once I just got an error about nautilus, and nothing more happened. I also found out that probably this is duplicate of https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/136529. So sorry if I caused unneccessary work for you by filing duplicate. Should I paste my experiences there, or what should I do? Sorry that I could not put all info in at the beginning, and spams you with many posts... -- [Hardy] gnome-session hangs on log in https://bugs.launchpad.net/bugs/179552 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 179552] Re: gnome-session hangs on log in
** Attachment added: The .xsession-errors file http://launchpadlibrarian.net/11104068/.xsession-errors -- gnome-session hangs on log in https://bugs.launchpad.net/bugs/179552 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 179552] gnome-session hangs on log in
Public bug reported: Binary package hint: gnome-session Hello, I'm testing out Hardy Heron. The live cd works fine, but once installed, I'm unable to log in with gnome. After I type my username and password and press enter, I hear some disk activity, but then the system stops completely. However, there is an error message in .xsession-errors: (I think this is the most releveant part, complete file attached) (process:20800): Gtk-WARNING **: This process is currently running setuid or setgid. This is not a supported use of GTK+. You must create a helper program instead. By echo'ing messages in the startup files, I've found out that when /etc/X11/Xsession.d/99x11-common-start tries to execute /usr/bin/gnome- session, it hangs. This suggests something is wrong with with /usr/bin /gnome-session. This is on a fresh install from alpha2, only with upgrades applied. I tried installing KDE, and logging in there works fine. Please tell me how I should debug this further, I 'm happy for any suggestions. The computer is a Pentium 4 2.8 Ghz, asus P4C800 motherboard with Intel 875 chipset, 1 Gb ram, wired net connection. I suppose more detailed hw info is not required here, but please tell me if I should provide that. Regards Pär ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New -- gnome-session hangs on log in https://bugs.launchpad.net/bugs/179552 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 88746] Re: ehci_hcd module causes I/O errors in USB 2.0 devices
FYI: I've filed a wishlist bug about automatic fallback to usb 1.1 if 2.0 doesn't work. In that way you won't manually have to unload ehci- hcd, so it could be some sort of workaround for your problem here (at least for most of you) You can look at https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/177430 if you're interested. It worked equally bad for me with Hardy alpha2, but as I said I think my problem is bad internal cabling. -- ehci_hcd module causes I/O errors in USB 2.0 devices https://bugs.launchpad.net/bugs/88746 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 177430] USB 1.1 automatic fallback if 2.0 fails
Public bug reported: Binary package hint: linux-source My idea is that if a USB device gets plugged in, and Linux isn't able to initialize it properly at usb 2.0, it should try initializing it with usb 1.1 instead. I have a problem where some of my usb-ports (the front ports) work only at usb 1.1 speeds. If I plug in lower speed devices, such as my keyboard, it works perfectly from the front ports. But when i connect higher speed devices, such as usb-sticks, or my digital camera, it won't work. It just fails silently. However, if I remove the usb 2.0 support from the kernel (unloading that module, ie sudo rmmod ehci-hcd), and then insert the usb-stick after that, it works, but only at usb 1.1 speeds of course. I am using Ubuntu 7.10 Gutsy Gibbon. So I think it would be quite nice if Ubuntu could do this: When a usb 2.0 device device gets connected on a 2.0 capable port (ie one that is connected to an ehci controller), it should of course first try to init it with usb 2.0 (ehci). If that doesn't work, try with usb 1.1 (uhci/ohci), and preferably put up some message to the user that the device is not working at full 2.0 speed. (This is what win xp does.) I think that a lot of users gets confused when their devices just silently fails at some ports of their computer. And if initializing it with uhci/ohci doesn't work either, then pop up some error message then also of course. I don't know if this is hard to implement, I'm no kernel hacker. I suppose that the fallback itself would be implemented purely in the kernel (thats why I reported this against linux-source), but bringing forth the message to the user would require probably involving at least udev and HAL also. This is the error message I get when I plug in my usb-stick: Dec 19 11:47:41 desktopen kernel: [ 5133.285580] usb 5-6: new high speed USB device using ehci_hcd and address 7 Dec 19 11:47:41 desktopen kernel: [ 5133.397338] usb 5-6: device descriptor read/64, error -71 Dec 19 11:47:41 desktopen kernel: [ 5133.612779] usb 5-6: device descriptor read/64, error -71 Dec 19 11:47:41 desktopen kernel: [ 5133.828252] usb 5-6: new high speed USB device using ehci_hcd and address 8 Dec 19 11:47:42 desktopen kernel: [ 5133.939976] usb 5-6: device descriptor read/64, error -71 Dec 19 11:47:42 desktopen kernel: [ 5134.155446] usb 5-6: device descriptor read/64, error -71 Dec 19 11:47:42 desktopen kernel: [ 5134.371765] usb 5-6: new high speed USB device using ehci_hcd and address 9 Dec 19 11:47:42 desktopen kernel: [ 5134.777916] usb 5-6: device not accepting address 9, error -71 Dec 19 11:47:42 desktopen kernel: [ 5134.889652] usb 5-6: new high speed USB device using ehci_hcd and address 10 Dec 19 11:47:43 desktopen kernel: [ 5135.296644] usb 5-6: device not accepting address 10, error -71 I'm pretty sure the cause for me is that the internal cabling to front ports is bad. The two front usb ports are connected via one cable to a 10-pin connector on the motherboard. The back ports, which connect directly to he motherboard, work perfectly. I've looked at bug #88746, which describes the same symptoms, and the same solution (unloading ehci-hcd). However, in my case, I don't think Linux or the motherboard is to blame, but just the cables, as it works in winxp (but at 1.1 speeds). Maybe this bug would be rated as a feature request then. But implementing this feature would certainly help those people affected by bug #88746, and not computer-savvy enough to unload ehci-hcd. This feature would then provide a workaround for them that at least enables them to use their devices (albeit at low speeds). Please tell me if you need some clarification, or something else. And thanks for your work in putting together a highly usable operating system. ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- USB 1.1 automatic fallback if 2.0 fails https://bugs.launchpad.net/bugs/177430 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 88746] Re: ehci_hcd module causes I/O errors in USB 2.0 devices
Elias: Maybe it's not because of the length of the cables, but then the quality of them, in my case (case as in situation, not box). I bought the parts in 2003, and probably the case model is older than that. Maybe usb 2.0 was too new then for them to test it properly. Maybe my problem is a bit different than the others here. In Winxp I'm able to use the devices, but just at 1.1 speeds. That is why i suspect the cabling and not the os in my case. And a similar feature as in winxp would be very nice in my case. I've built the computer myself, and know exactly what's in there. The front ports are connected with wires straight to the pins at the motherboard, so that's not what I would call a hub. But it doesn't work anyway. The ports which does work are the ports directly from the motherboard (no wires), at the back fo the of the case. However, I'm not sure exactly what defines a hub. I place one 10-pin connector to the motherboard, but has two usb-ports at the front. Maybe there is a hub then? So maybe my case would support your theory. -- ehci_hcd module causes I/O errors in USB 2.0 devices https://bugs.launchpad.net/bugs/88746 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 175286] Feature request: save files read-only when invoking external viewers
Public bug reported: Binary package hint: mozilla-firefox I think that Firefox should save files readonly to /tmp when a user click on files that require apps external to Firefox. The reason is this: if a user opens a file from within Firefox, and then does some editing and tries to save the file, he will get an error message if the file is saved readonly. And I think that would be helpful. Here is my story behind this problem (much abbreviated version): I was sitting at gmail, and reading a mail with an attachment. I clicked that attachment, to open it in openoffice. I made a lot of changes, and after that I saved. Then I rebooted my computer, started openoffice and tried to open the file (from the file-recently documents menu). And BANG, error message file does not exist. So, the problem was that I forgot that I had opened it from Firefox. I should have taken Save as instead. And Firefox first saves the file to /tmp, and then invokes Openoffice (or whatever program it is) to open the file. And as I use shmfs for /tmp, everything of course got erased from there. My fix for this problem is that Firefox should save these files in read- only mode to /tmp. Then when stupid users (like me) tries to save them, they will get an error message. To get a really helpful message, we would have to modify openoffice (and every other application), and make the browser open them with some special flag (telling the apps that it is a temporary file). Then the apps could display some error message like Warning: you are saving this file to temporary space. Probably you will not be able to open this file in the future, and then all your changes will be lost. Save the file in a different location instead, using File - Save as. But modifying all other programs is certainly not feasible IMO. So the user still has to do Save as in order to store the file safely. My important point is that the user should in some way get a note that he is doing something stupid when he tries to save that file. Use cases: Per is a knowledgeable computer user, but with a bad a memory. He would benefit from getting an error message when trying to save a file which he forgot where he opened it from. Ralf is a computer newbie who sometimes edits and saves files he has opened from Firefox, and never understand why they disappear. He would probably benefit from getting an error message when trying do to so, as he then might ask someone more skilled who can help him. This fix would probably be quite easy to implement, I think. And I suppose that I'm not the only one which has done this kind of mistake, it would probably be of benefit to a lot of people, especially newbies. And I can't really see any big downsides with this behavior. Please tell me if I should clarify something. You might also want to look at this forum thread: http://ubuntuforums.org/showthread.php?t=630532. This is where the idea about this started. ** Affects: mozilla-firefox (Ubuntu) Importance: Undecided Status: New -- Feature request: save files read-only when invoking external viewers https://bugs.launchpad.net/bugs/175286 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 88746] Re: ehci_hcd module causes I/O errors in USB 2.0 devices
I've had the same problem, but just on my front ports. And I'm pretty sure it is because the wires are longer, and of lower quality, to the front ports. The back ports are connected directly to mainboard, via a riser. Usb 1.1 devices (such as mice and keyboards) work at the front ports, but not usb 2.0 devices (such as camera or memory sticks). If I unload usb-ehci it works. So IMO, a solution to this could be some sort of fallback. If usb 2.0 doesn't work, try 1.1, and then notify the user. Win xp does this for my front ports. I don't know if this is hard to implement, I'm no kernel hacker. I was just about to post a feature request about this thing when I found this bug. I have a ASUS P4C800 motherboard, with intel 875 chipset, and an Antec Sonata case (the original model). And I think the wires from the case are to blame in this case. -- ehci_hcd module causes I/O errors in USB 2.0 devices https://bugs.launchpad.net/bugs/88746 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
