[Bug 1573454] Re: Mouse pointer disappear after suspend in Xubuntu 16.04
This bug seems to lie in the code the requires a password atfer closing the laptop lid, rather than in the screensaver. Aside from the fact that the pointer disappears, this code that is supposedly for security shows the prior screen display after the laptop lid is opened, before blanking and asking for the login. This is a security hazard in the event that the laptop has been stolen because the contents of the display might be confidential. I have a HP Stream 13 with Xubuntu 16.04 XFCE Power Manager Power Manager Settings General: when power button is pressed - do nothing when sleep button is pressed - do nothing when hibernate button is pressed - do nothing tick - handle display brightness keys when laptop lis is closed - on battery, suspend - plugged in, suspecnt tick - show notifications tick - show system tray icon Security: Automatically lock the session - never Delay locking after screensave for - 1 seconds [= minimum] unticked - lock screen when system is going for sleep [Please can we change these to "1 second" and "going to sleep] Behaviour with these settings: I close the lid, wait and reopen it - pointer is still there I close the lid, wait and reopen it screen is on when I first open the lid then screen goes blank, power light flashes does not wake up when I stroke my finger across the touchpad does wake up when I hit return screen comes back, power light is on steadily, pointer is there pointer disappears when I hit any printing key on the keyboard (return, space, letters, digits, puctuation) but not when I hit tab arrows backspace escape (I am using Emacs) pointer comes back when I stroke my finger across the touchpad Change power manager settings: tick - lock screen when system is going for sleep I close the lid, wait and reopen it Sometimes the screen comes on and shows whatever was on it before (this might be confidential material, so this is a security hazard) Then screen goes blank if I hit a key after which it goes to the login screen but the pointer is shown while the login screen is displayed The pointer disappears after I have logged in and does not reappaear when I stroke the touchpad although it does if I do ctrl-alt-f2 and then ctrl-alt-f7. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573454 Title: Mouse pointer disappear after suspend in Xubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1573454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573454] Re: Mouse pointer disappear after suspend in Xubuntu 16.04
Confirm bug (and virtual console quick fix) for Xubuntu 16.04 on a HP Stream 13. Usually I do a clean installation on a different 10GB root partition, but this time I did an upgrade from 15.10 and therefore cannot easily revert - I'm not going to do that again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573454 Title: Mouse pointer disappear after suspend in Xubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1573454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 767030] Re: Banshee freezes after suspend whilst playing
From the debug information, it was BBC Radio 2 live stream which is: http://www.bbc.co.uk/radio/listen/live/r2.asx I remember testing it with other Windows Media streams, like Radio 1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/767030 Title: Banshee freezes after suspend whilst playing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/767030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 746875] Re: Xorg High CPU Usage with Gnome/Openbox
Unfortunately I no longer have Ubuntu installed so I cannot comment much further. I think I did test it in Natty (could have been perhaps the 2nd beta) and it still did the same thing. I did not test it in vesa graphics mode. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/746875 Title: Xorg High CPU Usage with Gnome/Openbox -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 767030] Re: Banshee freezes after suspend whilst playing
Yes I have attached a copy of the terminal output. ** Attachment added: Debug information while reproducing bug https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/767030/+attachment/2133451/+files/Banshee_bug_radio_suspend.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/767030 Title: Banshee freezes after suspend whilst playing -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 42052] Re: Screen not locked on resume from hibernate/suspend
I'm not sure if it's related, but I just then experienced the same thing. I was able to use the computer for about 30 seconds after being away from the computer for 20 minutes. The computer wasn't in sleep mode, but the screensaver had kicked in. When I moved the mouse I was able to do things, and 30 seconds later it took me to the resume screen requiring a password. I'm using ubuntu 11.04 64bit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/42052 Title: Screen not locked on resume from hibernate/suspend -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 459005] Re: Can not log into openbox from GDM in Karmic Beta/RC
This seems to be reoccurring in Ubuntu 11.04 beta 2 (and I think beta 1 I had the issue). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/459005 Title: Can not log into openbox from GDM in Karmic Beta/RC -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 767030] [NEW] Banshee freezes after suspend whilst playing
Public bug reported: Binary package hint: banshee If I play a radio stream, then suspend the system, upon resuming from sleep banshee freezes. I was playing back a windows media stream. Tested with an ogg stream, and freeze does not occur. Running Ubuntu 11.04, 64bit, Banshee 2.0.0-2ubuntu1 ** Affects: banshee (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/767030 Title: Banshee freezes after suspend whilst playing -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 746875] Re: Xorg High CPU Usage with Gnome/Openbox
I've had a read through but it seems fairly non-descriptive as to go about solving the problem. I took a look at the Xorg.log.old and have attached it to this post - nothing seems too out of place for me at least. The CPU usage is definitely true and not just being reported since my fan is kicking in when it usually wouldn't do. However, it's not 100%, more around 40% leaving the machine still usable. Performing the grep command produced: direct rendering: Yes OpenGL renderer string: Quadro FX 360M/PCI/SSE2 GL_NV_blend_square, GL_NV_complex_primitives, GL_NV_conditional_render, GL_NVX_conditional_render, GL_NVX_gpu_memory_info, GL_OES_depth24, GL_OES_fbo_render_mipmap, GL_OES_get_program_binary, GL_OES_mapbuffer, ** Attachment added: Xorg.0.log.old https://bugs.launchpad.net/ubuntu/+bug/746875/+attachment/1971784/+files/Xorg.0.log.old -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/746875 Title: Xorg High CPU Usage with Gnome/Openbox -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 746875] Re: Xorg High CPU Usage with Gnome/Openbox
I have the same issue, just tried to use openbox, but CPU usage was being used constantly. Similar specifications, but 64bit. NVIDIA card with latest drivers, ubuntu 10.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/746875 Title: Xorg High CPU Usage with Gnome/Openbox -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 686014] Re: update manager
Sorry for any confusion I tried to remove a conflicting application only to find i removed 90% of the operating system with it :( So i have done a new install strait to 10.10 which is perfect and gives me a lot more space because before i had several different Linux operating systems, now I only have 1 Thank you for your time Paul Taylor -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/686014 Title: update manager -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 686014] Re: update manager
** Changed in: update-manager (Ubuntu) Status: Incomplete = Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/686014 Title: update manager -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 686014] [NEW] update manager
Public bug reported: Binary package hint: update-manager could not install the upgrades kubuntu 9.10 to 10.04lts file:///var/log/dist-upgrade ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/686014 Title: update manager -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 429667] Re: apport-cli crashed with UnicodeDecodeError in ui_present_report_details()
Much the same problem here. I tried to report a bug with debian-
installer, and received the following (running as root):
# ubuntu-bug debian-installer
*** Collecting problem information
The collected information can be sent to the developers to improve the
application. This might take a few minutes.
Traceback (most recent call last):
File /usr/bin/apport-cli, line 403, in module
if not app.run_argv():
File /usr/lib/python2.6/dist-packages/apport/ui.py, line 435, in run_argv
return self.run_report_bug()
File /usr/lib/python2.6/dist-packages/apport/ui.py, line 370, in
run_report_bug
response = self.ui_present_report_details()
File /usr/bin/apport-cli, line 215, in ui_present_report_details
details += ' ' + _('(binary data)') + '\n'
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 57602:
ordinal not in range(128)
--
apport-cli crashed with UnicodeDecodeError in ui_present_report_details()
https://bugs.launchpad.net/bugs/429667
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 436340] Re: Installer fails: grub fails on Intel ICH10 raid
I struck the same problem with the 19 October daily build of karmic- alternate-amd64.iso (I didn't try the livecd.) During the installation, grub2 (grub-pc) was installed - not grub - and failed to detect the dmraid devices as above. Booting into rescue mode. Was asked if I wanted to initialise the SATA raid devices (yes), but received the error The installer could not find any partitions; it found the existing partitions during the installation process. Opened a shell; dmraid and /dev/mapper were configured correctly. Set up the chroot environment, removed grub-pc and installed grub. I eventually got grub to install correctly, but running update-grub created the menu.lst file with an extra comma on each of the root device definitions e.g. (hd0,2,). Script bug? (I tried to report it via ubuntu-bug, but it fails with it's own bug!) -- Installer fails: grub fails on Intel ICH10 raid https://bugs.launchpad.net/bugs/436340 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 222421] Re: initrd not configured in menu.lst after upgrade from Ubuntu 7.10 to 8.04
Ubuntu is a Good Thing, and I would like to recommend it to my friends, giving them CDs. However, I cannot do this when I know that the installation CD or a routine kernel upgrade could leave their computer in an unbootable state. Especially when it is now clear where the error lies. Please can we fix it? Earlier, Steve spelt out the sequence 1. kernel is unpacked 2. update-grub is called 3. initramfs is generated (in kernel package postinst) 4. update-grub is *not* called 5. kernel package postinst ends successfully, leaving the kernel configured but menu.lst broken suggesting that the fault lies in step 4 or 5. This is incorrect. The error is at step 2. As I said before, this fails to maintain the data invariant. If you don't like the theoretical description, let me spell it out with reference to the kernel upgrade that Ubtunu/Hardy has just done on my machine. I ran sudo apt-get update and then upgrade from a terminal, and a number of other packages arrived at the same time: acpid libcamel1.2-11 libebook1.2-9 libecal1.2-7 libedataserver1.2-9 libldap-2.4-2 linux-headers-2.6.24-23 linux-headers-2.6.24-23-generic linux-image-2.6.24-23-generic linux-libc-dev python-apt python-gobject vim-common vim-runtime vim-tiny ... Fetched 35.1MB in 1min57s (300kB/s) (Reading database ... 153425 files and directories currently installed.) Preparing to replace linux-image-2.6.24-23-generic 2.6.24-23.46 (using .../linux-image-2.6.24-23-generic_2.6.24-23.48_i386.deb) ... Done. Unpacking replacement linux-image-2.6.24-23-generic ... Running postrm hook script /sbin/update-grub. Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /boot/vmlinuz-2.6.24-23-generic Found kernel: /boot/vmlinuz-2.6.24-22-generic Found kernel: /boot/vmlinuz-2.6.24-21-generic Found kernel: /boot/vmlinuz-2.6.24-19-generic Found kernel: /boot/memtest86+.bin Replacing config file /var/run/grub/menu.lst with new version Updating /boot/grub/menu.lst ... done Now we have in /boot --- please notice the dates: 422838 2009-01-26 04:30 abi-2.6.24-23-generic 80051 2009-01-26 04:30 config-2.6.24-23-generic 7504607 2009-01-20 17:19 initrd.img-2.6.24-23-generic 7504424 2009-01-15 15:43 initrd.img-2.6.24-23-generic.bak 905809 2009-01-26 04:30 System.map-2.6.24-23-generic 1922904 2009-01-26 04:30 vmlinuz-2.6.24-23-generic So if I had had a power failure at this point, a reboot would try to run the kernel (vmlinuz) of 26th Jan with the (presumably incompatible) image (initrd) of 20th Jan. Alternatively, if a kernel with a new version number had been installed, there would have been no initrd at all. Either way, menu.lst is now CORRUPT, because it contains an invalid kernel configuration. There are a lot more installations, and therefore opportunities for crashes and power failures, before Unpacking replacement linux-headers-2.6.24-23 ... Preparing to replace linux-headers-2.6.24-23-generic 2.6.24-23.46 (using .../linux-headers-2.6.24-23-generic_2.6.24-23.48_i386.deb) ... Unpacking replacement linux-headers-2.6.24-23-generic ... Yet more installations take place before Setting up linux-image-2.6.24-23-generic (2.6.24-23.48) ... Running depmod. update-initramfs: Generating /boot/initrd.img-2.6.24-23-generic Not updating initrd symbolic links since we are being updated/reinstalled (2.6.24-23.46 was configured last, according to dpkg) Not updating image symbolic links since we are being updated/reinstalled (2.6.24-23.46 was configured last, according to dpkg) Running postinst hook script /sbin/update-grub. Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /boot/vmlinuz-2.6.24-23-generic Found kernel: /boot/vmlinuz-2.6.24-22-generic Found kernel: /boot/vmlinuz-2.6.24-21-generic Found kernel: /boot/vmlinuz-2.6.24-19-generic Found kernel: /boot/memtest86+.bin Updating /boot/grub/menu.lst ... done Finally /boot/grub/menu.lst is back in a safe state. So this is what I propose: update-grub should merely CONCATENATE (some list of grub options and) kernel configuration items that are in individual files, and not try to implement any of the logic of matching kernels with initrds. I don't understand what the circumstances might be in which a kernel might not want an initrd, but let us imagine a very general situation in which there are Unix kernels from different Linux distros, MacOSX, Salaris, BSD, etc etc. Each of them is built and installed in a different way, and needs different options in grub. So, as the last stage of the installation of a
[Bug 222421] Re: initrd not configured in menu.lst after upgrade from Ubuntu 7.10 to 8.04
With all due respect, Steve, I fear that you are never going to solve this/these bug(s) unless you are more critical of your own reasoning. Whilst I now use computers primarily for email and word processing, you can see from my web page that I was a computer science lecturer and have taught reasoned programming, based on methods due to Floyd, Hoare and Dijkstra. Correctness of a program depends on a clear statement of what you intend it to do, and on correctness of the parts. This is expressed by means of pre-, post- and mid-conditions, and by invariants for loops and data structures. It seems to me that these are missing here, and in particular the implementation CONFLATES FAILURE TO CREATE THE INITRAMFS WITH THE INTENDED ABSENCE that you claim is legitimate. Let me work backwards from the headline problem, namely failure to boot after a new Ubiquity installation. The precondition for booting is to have a valid (kernel,initramfs) pair. Ubiquity, and in particular update-grub, failed to satisfy this as their post-condition. The pre-condition for update-grub is that each kernel be accompanied by any initramfs that it needs; update-grub works according to the presence or absence of files whose names match certain patterns. It assumes that the absence of an initramfs indicates that none is needed. This assumption is wrong. the entire problem is that update-grub is being called (for a reason that I presume is legitimate) before the kernel postinst has a chance to do its job, and then kernel package installation is somehow failing to call update-grub afterwards. So the only reliable point at which we would generate the dummy initramfs is the same point at which we generate the real one. So we come to the data invariant. menu.lst is a representation of a data structure consisting of a list (with a preference order defined by the version numbers) of (kernel,initramfs) pairs. This is obtained from the representation in the filesystem, which is in turn modified by the programs that install kernels and generate initramfses. THESE PROGRAMS ARE NOT MAINTAINING THE DATA INVARIANT. You need to treat them as a single operation, and not two. Or, given that the data structure is encoded using filenames, they should be given temporary names and then renamed by a program that first verifies that both are valid, before putting them both in place at the same time. You claim that a kernel can legimately do without an initramfs. I know next to nothing about kernels, and acknowledge that you may be right, but I suggest that you examine that claim very carefully. Presumably it pertains to a multi-boot situation, given that the choice of the Linux kernel in Ubuntu is under the control of the Ubuntu design. This means that non-initramfs kernels come from somewhere else, not the program that instals the normal Ubuntu Linux kernel. So you can adjust the data invariant and the way that you maintain it accordingly. Given the severity of the consequences, I, like Micheal, ALSO think that there should be a subsequent check and fix in Ubiquity before it finishes the installation. Finally, there is the Ubuntu philosophy. As I understand it, the word means I am here because of everyone else. The whole open source world relies on the cooperation of users, both for good will and for information. With regard to reporting bugs in Launchpad, you have now said both The 'perfect' way is to make sure duplicate bug reports are never filed. and The ubiquity bug really should have been opened as a separate bug report. No database implementation can achieve this, except for the empty database. Mathematically, it depends on decidable equality of records, but saying whether one bug manifestation is the same as another is subjective. Usually, I have failed to report bugs at all because I cannot see my way through the morass of entries in Lauchpad. For those of you on the receiving end of the reports, you must either indulge ignorant users like me, or just not get my reports. Also, for me to submit a report that is diagnostically useful to you, your programs must first provide me with the diagnostic information, and then tell me politely where to submit it. This comes back to the formulation and verification of correctness conditions in the program. -- initrd not configured in menu.lst after upgrade from Ubuntu 7.10 to 8.04 https://bugs.launchpad.net/bugs/222421 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 222421] Re: initrd not configured in menu.lst after upgrade from Ubuntu 7.10 to 8.04
Thanks to Steve Langasek for his thinking allowed about this important bug. In his faulty sequence, and on the occasion that the bug hit me, the crucial failure is that ** there is kernel entry in menu.lst with no accompanying initrd ** (in particular, the default entry had this). Looking at the code in /usr/sbin/update-grub, I see that write_kernel_entry() and the loop in output_kernel_list() where it is called seem to have been written for the explicit possibility that initrd does not exist. First, is this a legitimate possibility? Even if it is, could it be eliminated by generating a dummy initramfs, even where it is not needed, or a file with the appropriate name but some cipher as its content to indicate to write_kernel_entry() that initramfs is INTENTIONALLY absent? What I propose is that update-grub should ONLY generate a kernel entry in menu.lst when the kernel and initramfs actually exist. (Maybe it could also call some program to verify that they are intact.) Failing this, it could print an error message to STDERR and leave a comment in menu.lst concerning the defective kernel. Bugs are like problems with one's house: some are like torn wallpaper, which can be left until you have both the time and the degree of irritation fix them, whilst others are like rainwater dripping on to your bed from a broken rooftile, which have to be fixed straight away. Now, I use my computer for email and wordprocessing, and wouldn't bother to make much fuss about bugs in packages. But, as I said above, this one left my machine in an unusable state, that I could only fix because I had had a bit of experience as a sysadmin. This is like water coming through the roof, and it should have the highest classification in launchpad. So I consider that there should be a belt-and-braces solution in this case. Ubiquity has overall responsibility for installation, and that should double-check, after the other programs have done their job, whether the system is safe and will be able to boot. If not, it should scream loudly to the user, try to fix the problem, and give copious debugging information, including the address of launchpad. I am not actually sure that Steve's sequence is correct, because in my case there was a .bak version of the initramfs (and not the properly named one). I think that my logfile above shows that mkinitramfs failed. I don't know why the .bak file existed, but it worked when I renamed it and rewrote menu.lst manually. Maybe mkinitramfs created the image correctly, with the .bak name, but failed just before it changed the name. I think that my logfile above shows that initramfs failed because of a lack of memory. When the next kernel came along, I was unable to install it for exactly this reason, and apt-get got into a confused state in which it would neither install nor remove packages. This forced me to buy some more RAM. (I also had far too small a partition for /, and later fixed this too.) However, this problem has still not competely gone away - the machine hangs whenever I run any of the Ubuntu GUI pacakage management tools, and so I jsut use apt-get from the terminal instead. But, once again, even if my hardware falls below the recommended spec, this is no excuse for leaving my machine in an unusable state without any explanation of what has really gone wrong. Presumably it is part of the Ubuntu philosophy that people without the money to buy the latest and sexiest computers still have the right to use a decent operating system. Finally, I noticed from a search of lauchpad that there have actually been lots of reports of this bug, dating back to 2006. -- initrd not configured in menu.lst after upgrade from Ubuntu 7.10 to 8.04 https://bugs.launchpad.net/bugs/222421 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 222421] Re: initrd not configured in menu.lst after upgrade from Ubuntu 7.10 to 8.04
Sorry, thinking aloud. And I do hate text boxes on web forms, and their assumption that carriage return means new paragraph. A preview button would help, to give one the opportunity to correct the line breaking. -- initrd not configured in menu.lst after upgrade from Ubuntu 7.10 to 8.04 https://bugs.launchpad.net/bugs/222421 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 222421] Re: initrd not configured in menu.lst after upgrade from Ubuntu 7.10 to 8.04
This dialogue seems to be split between two pages - it is not possible to merge them? if the initrd.img has not been created, then that's certainly a bug in its own right, though not a bug in grub, and we should still try to get that fixed. I would point out that in my case the initrd.img WAS created - that was how I eventually got 8.04 to work on my machine. But (1) it was called /boot/initrd.img-2.6.24-16-generic.bak and (2) it was not mentioned in menu.lst. The absolute priority here is that the user should at least be informed of what has happened before the installation CD quits, and provided at least with some advice as to how to get out of the mess and back to the old system. In particular, the installer should NOT TRASH THE OLD SYSTEM. The program that writes menu.lst (I am assuming that it is separate from the one that creates initrd.img) could do this check, try to make use of what is available, give an error report to the user and save debugging information for you. Apparently I have not been able to stress adequately the seriousness with which I view this bug. The installer left my machine in an unusable state. I will not do another Ubuntu installation or recommend Ubuntu to anyone else until this is fixed. In particular, I am considering putting Linux on my Mac laptop (instead of MACOS 10.3), but there is no way that I would risk a repetition of this experience, as I would have no equivalent of Knoppix to get me out of the mess. -- initrd not configured in menu.lst after upgrade from Ubuntu 7.10 to 8.04 https://bugs.launchpad.net/bugs/222421 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 222421] Re: initrd not configured in menu.lst after upgrade from Ubuntu 7.10 to 8.04
to Steve Langasek: How do you know that (occurrence of) this bug is rare? It renders the computer unusable, especially if it occurs during use of the installation CD. If this happens to someone who is just trying out Linux for the first time, they'll (re)install Windows Vista and never come back to Linux. If it happens to a more experienced Unix user, they'll switch to another Linux distro and never come back to Ubuntu. In neither case is the user likely to go to the trouble of submitting a big report. I can understand your intellectual frustration in not understanding what triggers the failure to create initrd.img, but the priority is surely to fail safely, or find a roundabout way of succeeding, as I eventually did myself, by using initrd.img.bak. I would suggest that the program that rewrites /boot/grub/menu.lst should refuse to do so unless it can find an initrd.img (or an initrd.img.bak). It could then also generate whatever debugging information you need, and ask the user to submit it here. I would also suggest that the installation CD should not trash the existing system, but leave it in a state that allows the user to revert to it, ideally via the GRUB menu. -- initrd not configured in menu.lst after upgrade from Ubuntu 7.10 to 8.04 https://bugs.launchpad.net/bugs/222421 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 222421] Re: initrd not configured in menu.lst after upgrade from Ubuntu 7.10 to 8.04
I find it shocking that nothing has been done about the fact that the installation CD can leave someone's computer in an unusable state, from which it is only possible to recover using other tools and considerable Linux experience. -- initrd not configured in menu.lst after upgrade from Ubuntu 7.10 to 8.04 https://bugs.launchpad.net/bugs/222421 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 145015] X freezes, hogging CPU
Maybe the bug has metamorphosed. At any rate, the following is similar, but I cannot work out the appropriate heading under which to report it - if you know, please redirect my report as appropriate. I now have Xubuntu 8.04 (from the 24 April CD image) on the same machine. On several occasions it (probably the X server) has frozen. This collection of log files comes from the first such occasion. The update-manager was doing its stuff in the background (fixing the SSL vulnerability), although that hangs too, and I think I had XDVI running, maybe Firefox. I was mainly using Emacs22-gtk. I deleted a line in a file, the lines either side appeared superimposed, then the mouse cursor disappeared. I managed to login remotely using ssh. I found that the X server was taking 98% of the CPU, so I killed it, but it resurrected itself and again hogged the CPU. This happenned several times. However, I managed to save these files from /var/log. I have had two more similar experiences, without being about to save the logs. Similar reports on other Linux web sites have said that X hogs the CPU when there is a remote session, but that I cannot see how to do diagnosis without having a remote session. ** Attachment added: /var/log http://launchpadlibrarian.net/14570432/pt.xcrash.080515.var.log.tar.gz -- Gnome session restarts spontaneously https://bugs.launchpad.net/bugs/145015 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 222421] Re: initrd not configured in menu.lst after upgrade from Ubuntu 7.10 to 8.04
Description of my hardware: Mainboard Gigabyte GA-7IX ATX SOYO 5EMA+ 100Mz (Skt7) ProcessorAMD K6-2-550 Memory 128Mb DIMM PC100 NB this is less RAM than the Xubuntu 8.04 documentation says that I need. ** Attachment added: lspci -vvnn http://launchpadlibrarian.net/14096128/machine -- initrd not configured in menu.lst after upgrade from Ubuntu 7.10 to 8.04 https://bugs.launchpad.net/bugs/222421 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 222421] Re: initrd not configured in menu.lst after upgrade from Ubuntu 7.10 to 8.04
Xubuntu 8.04 (24 April 2008) CD image downloaded My only differences from standard set-up: (1) Old hardware (2) DIY disk partitioning. On completion of the intallation, it failed to boot, with messages like this: VFS: cannot open root deveice UUID=hex stuff or unknown block (0,0) Please append a correct root= boot option; here are the available partitions: kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (0,0) Eventually I worked out that - the initrd command is missing from /boot/grub/menu.lst - the file /boot/initrd.img-2.6.24-16-generic is missing (actially, it's there, but called /boot/initrd.img-2.6.24-16-generic.bak) After correcting this, the new system booted correctly. Another thing that confused matters was that my internal IDE disk that had been called /dev/hda was now called /dev/sda which I thought meant a SCSI disk. On further investigation, I found that the installer failed to create initrd.img The relevant part of /var/log/installer/syslog is attached. For the enlightenment of novices like me: grub is part of the bootstrapping process, and loads the operating system kernel; to do this, it needs the executable binary of the kernel itself and also a minimal filesystem, which is what initrd.img provides (this is a gzip-compressed cpio-image of /bin, /conf, /etc, /init, /lib, /modules, /sbin, /scripts, /usr and /var) There are tools such as update_initramfs and others to create this image, but I could not work out how to do so unless you already have the target filesystem in place, which seems to require the target kernel too; in particular, I don't know how to set things up to use chroot. Since there is an initrd.img...bak file, somebody was presumably aware of the possibility that creation of the new initrd.img might fail during the installation process. There should be a check for this, and in this case the .bak file should be installed. As psl says, this is a critical bug, and one that could easily put people off using Linux for life. Ubuntu sells itself as Linux for human beings, which this kind of failure clearly is not. However, what makes me angry about this is not the bug itself, but the enthusiasm that the installation cd has for trashing my disk and pre-existing system (which was Ubuntu 6.10). Even though I had backed everything up, it took me about 20 hours work from giving the go-ahead to the Xubuntu 8.04 installation to recovering my old system in an approximately usable state. (cpio had very kindly changed many of the directory permissions to drwx--, making much the system unusable.) Ubuntu and other Linux distributions go to some length to provide dual boot with Micros**t, so why not a dual boot with the pre-existing Unix (Ubuntu) system? Then, after a failure like this one, the user can revert to the old but working system.If that's too difficult, then at least please move the old / /usr and /var to OLD, so that they can be restored using some other tool like Knoppix. If I hadn't had a Knoppix CD for fixing things, and a laptop to look stuff up on the Web, It would have had no way of recovering my computer. ** Attachment added: part of /var/log/installer/syslog http://launchpadlibrarian.net/14096022/xubuntu-var-log-installer-syslog-mkinitrd -- initrd not configured in menu.lst after upgrade from Ubuntu 7.10 to 8.04 https://bugs.launchpad.net/bugs/222421 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 145015] Re: Gnome session restarts spontaneously
It happened to me again this evening. Here's some stuff from /var/log /var/log/messages syslog and user.log: 21:04:44 localhost gconfd (pt-5429): Received signal 15, shutting down cleanly 21:04:53 localhost gconfd (pt-5429): Exiting auth.log: 21:04:51 localhost gdm[4876]: (pam_unix) session closed for user pt daemon.log: 21:04:53 localhost gdm[4876]: Error reinitilizing server Xorg.0.log: Fatal server error: Caught signal 4. Server aborting This was preceded by the following backtrace: 0: /usr/bin/X(xf86SigHandler+0x86) [0x80b4b06] 1: [0xe420] 2: /usr/lib/xorg/modules/extensions/libGLcore.so(_swrast_Triangle+0x2d) [0xb7b5b77d] 3: /usr/lib/xorg/modules/extensions/libGLcore.so [0xb7b9bae5] 4: /usr/lib/xorg/modules/extensions/libGLcore.so [0xb7bb325f] 5: /usr/lib/xorg/modules/extensions/libGLcore.so [0xb7bb45ab] 6: /usr/lib/xorg/modules/extensions/libGLcore.so(_tnl_run_pipeline+0x16e) [0xb7ba24b7] 7: /usr/lib/xorg/modules/extensions/libGLcore.so(_tnl_playback_vertex_list+0x4cc) [0xb7ba8c3c] 8: /usr/lib/xorg/modules/extensions/libGLcore.so [0xb7ac5872] 9: /usr/lib/xorg/modules/extensions/libGLcore.so(_mesa_CallList+0x47) [0xb7ac5d07] 10: /usr/lib/xorg/modules/extensions/libGLcore.so(glCallList+0x23) [0xb7aa9eed] 11: /usr/lib/xorg/modules/extensions/libglx.so(__glXDisp_CallList+0x1f) [0xb7cad3f3] 12: /usr/lib/xorg/modules/extensions/libglx.so(__glXRender+0xd0) [0xb7cc573f] 13: /usr/lib/xorg/modules/extensions/libglx.so [0xb7cc848d] 14: /usr/bin/X(Dispatch+0x19e) [0x8085d86] 15: /usr/bin/X(main+0x47c) [0x806e108] 16: /lib/tls/libc.so.6(__libc_start_main+0xd4) [0xb7de7ea4] 17: /usr/bin/X(FontFileCompleteXLFD+0x8d) [0x806d671] Hope this helps a bit. -- Gnome session restarts spontaneously https://bugs.launchpad.net/bugs/145015 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 145015] Re: Gnome session restarts spontaneously
I'm using Ubuntu Dapper on some elderly hardware. As with Jan Kalab, this has happened to me a number of times after a period of inactivity. On the last occasion, I had only a Gnome Terminal, Emacs and Xdvi running; I was sitting on the other side of the room, the screensaver was running, and then suddenly there was just a Gnome Login window. -- Gnome session restarts spontaneously https://bugs.launchpad.net/bugs/145015 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 40561] USB disk goes offline - but not in Knoppix 5.1.1 (Linux 2.6.19)
I used gparted to repartition my 80Gb disk with several ext3 partitions (and one for the Mac), and gparted, fdisk, cfdisk and the Mac agreed on the new partition table. Using cpio under Ubuntu Dapper / Linux 2.6.15, I then tried to copy the largest partition of my old disk (10Gb) on to it. This failed in the same way as before, but now after 3Gb. However, since I was now using the ext3 journaling filesystem, fsck now said that the disk was clean. But whereas it had originally been mounted as /dev/sda, it was remounted after the failure as /dev/sdb. Then I tried out Knoppix version 5.1.1 (www.knoppix.net), which is a year old; it includes the Linux kernel version 2.6.19. This successfully copied all of my smaller partitions. Since I had already spent time on the partial copy of the big partition, I didn't scrub it and start again, but copied the rest in bits by listing the missing files. Maybe I wasn't doing a big enough transfer to provoke it, but the previous failure DID NOT happen. So maybe this bug was fixed in Linux 2.6.19. However, it would be nice to hear from Chuck Short or anyone else with inside knowledge of the relevant code and its potential failure whether my report and the others pertain to something that is identifiable. -- Problem with USB Mass Storage https://bugs.launchpad.net/bugs/40561 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 40561] USB disk goes offline midtransfer
I have a new Freecom Classic SL 80GB USB hard drive connected to Ubuntu 6.06 Dapper Drake Linux 2.6.15-29-386 on old (2001) hardware also tried with Mac PowerBook G4 MacOS 10.3.9. After playing with the VFAT filesystem on the disk as it came, using both computers, I used GNU Parted 1.6.25.1 to put a single-partition EXT2 filesystem on it. However, fdisk v2.12r thinks that it's still VFAT, whilst (after doing the copies below) the Mac still sees the old VFAT files, but not the new EXT2 ones. I started trying to copy the partitions of the 20GB disk on the Linux machine, using GNU cpio v2.6. The two smallest ones (/=168MB and /var=316MB) were copied corrrectly, as verified using md5sums. When I tried the bigger ones (/usr=2168MB and /home=1754MB), the copy failed after some time (after almost 1GB on one occasion) and the disk was disconnected. STDERR said: cpio: write error: Input/output error dmesg said: Buffer I/O error on device sda1, logical block 8587112 and (repeatedly) rejecting I/O to dead device /var/log/messages contained lines like the following usb 1-1: new full speed USB device using uhci_hcd and address 3 scsi1 : SCSI emulation for USB Mass Storage devices Vendor: HDS72808 Model: 0PLAT20 Rev: 0 0 Type: Direct-Access ANSI SCSI revision: 00 SCSI device sdb: 160836480 512-byte hdwr sectors (82348 MB) sd 1:0:0:0: Attached scsi disk sdb Driver 'sd' needs updating - please use bus_type methods printk: 17347 messages suppressed. lost page write due to I/O error on sda1 After this, /dev/sda1 no longer appeared in the output of df, and both mount and umount denied the existence of /dev/sda1. However, usbview said that the usb device was still there. After turning the disk power off/on, it appeared as /dev/sdb1. A subsequent e2fsck found numerous errors with free block counts, unattached inodes, inode ref counts, directory counts, etc. This happened four times, including once using tar instead of cpio. I tried using e2fsck -c to check for bad blocks. The first 3% of the disk was ok, but took ages, so I went away to do something else. When I came back, the disk had been disconnected as before, but I couldn't see how far the bad block check had gone, as the screen saver wouldn't restore the text of that terminal window. Subsequent e2fsck was clean. I have no idea whether this is a Linux bug or faulty hardware. I am posting this report here because the comments above were the closest that I could find in a web search to the symptoms that I have. -- Problem with USB Mass Storage https://bugs.launchpad.net/bugs/40561 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
