[Bug 1622601] Re: Xubuntu 16.04 installer crashes in VirtualBox on Lenovo ThinkPad P50
I was able to resolve this issue by re-downloading the Xubuntu Live CD ISO. I didn't check the MD5 sum, but since re-downloading made the installation work without "input/output error", the previous ISO was probably corrupted. (Downloaded through BitTorrent the first time, while using a "normal" mirror the second time.) The error message seems a bit counter-intuitive. Is there a specific reason why an I/O error occurs instead of a more specific one? For the record, the following I tried did NOT resolve the issue: Deactivate PAE/NX on the VM, set HDD to not be detected as an SSD, changed virtual HDD from SATA to IDE. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622601 Title: Xubuntu 16.04 installer crashes in VirtualBox on Lenovo ThinkPad P50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1622601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1622601] Re: Xubuntu 16.04 installer crashes in VirtualBox on Lenovo ThinkPad P50
The full error message is: The installer encountered an error copying files to the hard disk: [Errno 5] Input/output error -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622601 Title: Xubuntu 16.04 installer crashes in VirtualBox on Lenovo ThinkPad P50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1622601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1622601] [NEW] Xubuntu 16.04 installer crashes in VirtualBox on Lenovo ThinkPad P50
Public bug reported: While trying to install from the Xubuntu 16.04 Live CD in VirtualBox, I get roughly to the keyboard layout selection screen before the installer crashes with a message roughly like "installer crashed, this could be due to a damaged install medium, try burning at a lower speed etc". Detailed information: * Host machine is a Lenovo ThinkPad P50 laptop, with Windows 10 (a pristine install, I turned on the laptop for the first time today) * Intel VT-x and VT-d are active inside the host BIOS * Trying to install inside Oracle VM VirtualBox 5p1p4 r110228 (Qt5.5.1) * Created a dynamically allocated VDI disk image to install on, 350 GB (on a physical 512 GB SSD) * Chose "erase whole drive to install Xubuntu" (the default) While selecting the keyboard layout, timezone or entering my user name and password, the installer suddenly displays the crash message. Apparently, some background process fails, so which UI step is shown when the crash happens varies on every try. I will provide additional information when needed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.2 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CasperVersion: 1.376 Date: Mon Sep 12 14:40:09 2016 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity LiveMediaBuild: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.63.2 xenial xubuntu ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1622601/+attachment/4739322/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622601 Title: Xubuntu 16.04 installer crashes in VirtualBox on Lenovo ThinkPad P50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1622601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1622601] Re: Xubuntu 16.04 installer crashes in VirtualBox on Lenovo ThinkPad P50
** Attachment added: "partman" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1622601/+attachment/4739330/+files/partman -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622601 Title: Xubuntu 16.04 installer crashes in VirtualBox on Lenovo ThinkPad P50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1622601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 645023] Re: libwv2 release package compiled with DEBUG flag
** Changed in: wv2 (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/645023 Title: libwv2 release package compiled with DEBUG flag -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 343242] Re: python-xml seems to be broken with python-2.6: xpath does not work
Streamlining the use of the standard library xml module is probably a good idea. However, the removal of python-xml breaks not only packages in universe, but also third party applications. At my company, various products include code built around PyXML's xpath module. While they run perfectly well on our servers using older Python and PyXML versions, I am currently only able to run test builds on my Ubuntu 9.04 workstation after I used the symlink booleans.so hack mentioned above. Is there a specific reason why PyXML shouldn't be in Ubuntu? Because now that python-xml has been removed completely, I probably won't be able to upgrade to future Ubuntu versions without pulling an outdated (or non- packaged) PyXML back in. -- python-xml seems to be broken with python-2.6: xpath does not work https://bugs.launchpad.net/bugs/343242 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 48563] Re: filesystem check fails on boot, but filesystem isn't bad
Andy, is the Ubuntu installation on your old machine still intact? Although you are currently not annoyed by this bug anymore, your input would still be helpful to either prove Theodore's thesis, or to prove it wrong. -- filesystem check fails on boot, but filesystem isn't bad https://bugs.launchpad.net/bugs/48563 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 84849] Re: (bash) ssh to other systems fails to connect
Could you please (as a test) try the connection with GSSAPIAuthentication disabled anyway? This would help to distinguish the issues you were experiencing from those described in bug #84899. The easiest way to do this: ssh -vvv -oGSSAPIAuthentication=no [EMAIL PROTECTED] ssh-nogssapi- nomdns.log 21 This will disable the GSSAPI setting only for this connection, and additionally log every single step taken by SSH to a file called »ssh- nogssapi-nomdns.log« in your current directory. Please attach this log file to your next comment. -- (bash) ssh to other systems fails to connect https://bugs.launchpad.net/bugs/84849 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 84899] Re: SSH with GSSAPIAuthentication option on SSH servers are very slow
Another user faced similar performance problems with SSH, documented in bug #84849. Again, the problem was solved by disabling mdns4_minimal resolution in nsswitch.conf. So far, some people benefited from disabling GSSAPI-Authentication, some others had to disable mDNS to regain acceptable performance. Do we have two separate issues here? -- SSH with GSSAPIAuthentication option on SSH servers are very slow https://bugs.launchpad.net/bugs/84899 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 84849] Re: (bash) ssh to other systems fails to connect
** Changed in: openssh (Ubuntu) Assignee: (unassigned) = Daniel Werner -- (bash) ssh to other systems fails to connect https://bugs.launchpad.net/bugs/84849 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 111434] Re: xen-image-2.6.19-4-server package metadeta is wrong
** Changed in: xen-source (Ubuntu) Status: Unconfirmed = Confirmed -- xen-image-2.6.19-4-server package metadeta is wrong https://bugs.launchpad.net/bugs/111434 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 47132] Re: Documentation index not available -- yelp confused
Fixed in upstream and released in Ubuntu. ** Changed in: bzr (Ubuntu) Status: Unconfirmed = Fix Released -- Documentation index not available -- yelp confused https://bugs.launchpad.net/bugs/47132 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 116371] bzr doc-base directs to wrong index page
Public bug reported: Binary package hint: bzr The bzr package contains several pages of HTML documentation. Yet, ever since bug #47132 was fixed, file:///usr/share/doc-base/bzr directs to file:///usr/share/doc/bzr/html/tutorial.htm as the index page, effectively making it impossible to access the other pages via Yelp. The doc-base entry should probably point at file:///usr/share/doc/bzr/html/index.htm instead. ** Affects: bzr (Ubuntu) Importance: Undecided Status: Unconfirmed ** Affects: bzr (Debian) Importance: Undecided Status: Unconfirmed ** Also affects: bzr (Debian) Importance: Undecided Status: Unconfirmed -- bzr doc-base directs to wrong index page https://bugs.launchpad.net/bugs/116371 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 111434] Re: xen-image-2.6.19-4-server package metadeta is wrong
The description makes another two contradictory statements, which may be oversights on part of the maintainer and/or indications of cruft: Supports Generic processors. As ski mentioned, there are xen-image-*-generic* packages already. Geared toward desktop systems. Isn't this supposed to be a xen-image-*-server package? -- xen-image-2.6.19-4-server package metadeta is wrong https://bugs.launchpad.net/bugs/111434 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 84849] Re: (bash) ssh to other systems fails to connect
There is now a slight pause (approx 3-4 sec) after the password is entered before ssh displays /etc/motd, is this due to the system checking what is specified in the hosts: files dns line in /etc/nsswitch.conf [?] A delay *after* authentication is probably caused by your login shell's startup sequence on the server side. For example, bash executes /etc/profile, /etc/bash.bashrc, ~/.bash_login, ~/.profile, and ~/.bashrc in order. You can trace how long each script takes to execute by adding a line like e.g. »echo /etc/profile« to the bottom. Anyway: To further cut down on delay *before* password authentication, add GSSAPIAuthentication no to /etc/ssh/ssh_config on your client. This will prevent SSH from requesting GSSAPI auth, which would fail silently anyway because it is disabled by the default sshd_config shipped in Ubuntu. (Except, of course, if you explicitly deployed Kerberos.) looking back on it I specified the LoginGraceTime value based on a Debian system hardening website/walk through thoughts? One could imagine a Distributed Denial of Service attack where multiple foreign hosts bombard the server with new connection attempts. This will leave this server's CPU(s) commited to answering connection attempts while doing little other work, exhaust the server's memory and file descriptor resources, and overflow the session tables of any stateful firewalls or NAT routers that happen to sit in front of the server. Lowering LoginGraceTime will shorten the timeout until sshd closes an unauthentified incoming connection. Lowering MaxStartups will limit the maximum number of concurrent unauthentified connections. These two settings will lessen the damage somewhat, though with a side effect: Your incoming SSH connections won't be treated any differently, effectively locking you out of your own system. There's probably more to it, but these are my thougths :) -- (bash) ssh to other systems fails to connect https://bugs.launchpad.net/bugs/84849 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 72624] Re: Message(s) too gender-specific
The ticket in pidgin's bug tracker referenced by this launchpad bug goes far beyond the scope I had in mind. Quoting from http://developer.pidgin.im/ticket/184 : Pidgin should be gender-aware English version of pidgin doesn't need to care much about gender, but many other languages need to. There should be some radio box to tell our own gender as well as buddies' gender (when the protocol doesn't already provide it) and use two strings to be translated. Furthermore, this is an issue with gaim-otr upstream, not with pidgin. The reference to pidgin's bug tracker should probably be removed. -- Message(s) too gender-specific https://bugs.launchpad.net/bugs/72624 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 115949] »Secure Connection« settings in account editor not user-friendly
Public bug reported: Binary package hint: evolution The account editor offers a »Use Secure Connection« option for sending as well as receiving mail. However, the order in which the items appear in the drop-down list does nothing to clarify which one should be preferred: »No encryption«, »TLS encryption«, »SSL encryption«. I suggest re-ordering the list by descending level of security provided, i.e. TLS, SSL, no encryption. The default value is another matter: Currently, no encryption is provided unless it is expressly selected, which requires the prior user knowledge of the server's encryption capabilities. It should be possible to »check for supported types« as is currently possible with Authentication Types. I would be grateful for some opinions on this matter, especially since I'm not a security expert. ** Affects: evolution (Ubuntu) Importance: Undecided Status: Unconfirmed -- »Secure Connection« settings in account editor not user-friendly https://bugs.launchpad.net/bugs/115949 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 115949] Re: »Secure Connection« set tings in account editor not user-friendly
This report is about the general unhelpfulness of the account editor's »Security« section towards non-technical users. I believe this situation could be improved by implementing the above-mentioned proposals, in order to help the user to decide which encryption mechanism to use. -- »Secure Connection« settings in account editor not user-friendly https://bugs.launchpad.net/bugs/115949 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 84849] Re: (bash) ssh to other systems fails to connect
Sorry for the bother Not at all! The Community is here to help. Regarding your problem with SSH: The resolution you described seems more like working around the problem. Changing UseDNS to no will simply prevent sshd from commencing a reverse DNS lookup. The real issue is thereby circumvented, not solved. A lot of people are having similar DNS-related problems with Feisty, so I strongly suspect that also in your case Avahi's mDNS is the real culprit. Please try the following: 1. Undo your changes to /etc/ssh/sshd_config (that's what you meant when you said sshd.conf, I suppose), i.e. remove the lines saying LoginGraceTime and useDNS. 2. In /etc/nsswitch.conf, replace the line hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 with hosts: files dns This will tell all nsswitch-aware programs (including SSH) to skip DNS lookups via mDNS, probably speeding up the lookup process so that SSH connection attempts won't hit the login grace time. (LoginGraceTime defaults to 120 seconds, by the way, so specifying 20 probably didn't contribute to improving your situation.) -- (bash) ssh to other systems fails to connect https://bugs.launchpad.net/bugs/84849 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 84849] Re: (bash) ssh to other systems fails to connect
Thank you for your bug report. To analyze the problem's potential cause, some debug output would be helpful. Please retry the connection with ssh -vvv [EMAIL PROTECTED] and attach the output. By the way, if the 15 sec delay appeared only after your upgrade to feisty, it may be related to bug #84899. -- (bash) ssh to other systems fails to connect https://bugs.launchpad.net/bugs/84849 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 60032] Re: no Umlaut in filenames from smbmount by default
codepage=cp852,iocharset=utf8 finally works. codepage=cp437,iocharset=utf8 also works. Note that the iocharset option must be given as well. Thanks a lot for these hints -- umlauts are converted correctly at my site, at last. Specifying the encoding as 'utf8' instead of 'utf-8' did the trick. However, I still don't get why smbmount didn't complain about the superfluous dash. Actually, it will happily accept even 'utf66' or 'foobar', only to silently ignore it. I fully agree with you on this matter, Jörg: More sensible defaults could spare some trouble. -- no Umlaut in filenames from smbmount by default https://bugs.launchpad.net/bugs/60032 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 35375] Re: Scorched3d SIGSEGV on startup
Maybe I can provide a solution for part of the mystery. Some weeks ago, I was quite amazed to find that on the very same machine, Scorched 3D ran on all user accounts but one. When started as the latter, Scorched segfaulted throwing the very backtrace mentioned in the initial report. wxGetUserName already hinted at the passwd file, and there dwelled the culprit: The account where Scorched 3D crashed had a German umlaut in its GECOS' full name field. After the offending character's removal, Scorched has stopped crashing ever since. wxGetUserName calling wcsncpy seems not to work as expected with actual wide characters. Or could it be a coincidence that Scorched 3D fails for Grundström, Bröckling, Bjørlo, and in my case, Müller ... ? ;) Could this be a bug in libc itself, or in wxGetUserName's handling of wchars? -- Scorched3d SIGSEGV on startup https://launchpad.net/bugs/35375 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59632] Re: Evolution throws error with imap/ssl
The settings not actually applied until restart issue has already been filed under Launchpad bug #34058. It seems this is a known upstream problem since at least 2001. The GNOME bug tracker has gathered half a dozen duplicate bug reports, which shows that people still keep stumbling over this one once in a while. -- Evolution throws error with imap/ssl https://launchpad.net/bugs/59632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59293] Re: Dosfsck Run On Every Boot on FAT
Duncan wrote: But since fat doesn't support it I suggest we don't try and make it make complicated than necessary With hindsight, I'll have to reluctantly agree. Kludging even more proprietary enhancements onto FAT has the potential to create more problems than it solves, especially because Windows would have ignored the magic fsck record anyway. Write a simple hidden text file with configuration info onto the fat partition. I might be called .mount-conf . I am concerned it would be unneccessarily difficult to access .mount- conf on an up to this point *unmounted* file system, especially if said file system might be in an inconsistent state, in which case we'd have to run fsck first, which has to access .mount-conf -- a chicken-and-egg problem. The boot sequence could probably be configured to run dosfsck at certain intervals of uptime. After the boot process has completed, the FAT partitions are probably mounted. I don't think dosfsck supports repairing live FAT volumes. If I remeber rightly, the final two numbers, both zero in this example, tell the system to continue booting if it can't find this partition (the first zero) According to fstab(5), it's a signal for dump whether this partition needs or needs not to be dumped. and to not check it's integrity (the second zero) This workaround works as long as users always cleanly unmount their filesystems. Which, in case of e.g. a kernel panic, is not given. Not checking at all and risking creeping integrity damage seems worse to me than checking too often. So, should we advise users to take this risk? -- Dosfsck Run On Every Boot on FAT https://launchpad.net/bugs/59293 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64220] Re: Confusing message
Chris, your patch looks good so far. If you'd like some more Python practice, you could now expand your patch to cater for cases where more than one package matches. At the moment, the message The program '%s' is currently not installed is not displayed if len(packages) 1. -- Confusing message https://launchpad.net/bugs/64220 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67726] Re: wrong exit code
Couldn't this be fixed by simply rewriting the 'try' clause in /usr/bin /command-not-found? I've got something like this in mind: try: ... #except KeyboardInterrupt: # don't need this anymore # ... finally: import sys sys.exit(1) This would ensure that no matter what, command-not-found always returns failure. Of course, exitting with another code would be impossible now, since finally clauses are executed even after a call to sys.exit(). -- wrong exit code https://launchpad.net/bugs/67726 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59632] Re: Evolution throws error with imap/ssl
I have been noticing a similar problem since the upgrade from Dapper to Edgy. Trying to contact my company's IMAP server always resulted in an Unknown error, not even in SSL negotiations failed. Refreshing folders etc. didn't work, not with TLS, not with SSL, not even with plaintext passwords (ugh). Not until I tried restarting Evolution after selecting SSL. Thank you, Fredrik -- it seems I too got fooled. This is an undesirable behaviour, by the way: Evolution should really apply the selected Security method when checking for Supported [Auth] Types. Should I file a new bug for this issue? The TLS problem remains, of course. -- Evolution throws error with imap/ssl https://launchpad.net/bugs/59632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72293] Re: Boot fs-check error - Differences between boot sector and back-up
There are some open questions remaining in Bug #48563 whose answers could be valuable. The more detailed information we can gather, the better. -- Boot fs-check error - Differences between boot sector and back-up https://launchpad.net/bugs/72293 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 34651] Re: ACPI does not work on Asus motherboard with nForce chipset
I can absolutely second this. After upgrading my girlfriend's ASUS K8N4-based system to Dapper, the onboard sound, Ethernet and USB controllers failed to configure correctly. This behaviour was also exhibited after wiping the hard drive and installing Kubuntu Edgy. Fortunately, the pci=nommconf workaround solved all of these problems. -- ACPI does not work on Asus motherboard with nForce chipset https://launchpad.net/bugs/34651 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 29050] Re: cupsys does not automatically detect parallel printer
...and another frustrated person to confirm this problem, this time with Debian. I've had the same no parallel port printer discovered problem for some time now. The antiquated HP LaserJet worked just fine when attached to a Debian 'sarge' system running LPRng. If I remember correctly, it still worked when I switched to CUPS last year (eventually ;). On Debian 'etch', though, it doesn't work at all. Currently recompiling my kernel package with ppdev-support. Let's see if this works... -- cupsys does not automatically detect parallel printer https://launchpad.net/bugs/29050 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 29050] Re: cupsys does not automatically detect parallel printer
Bad luck. Even with lp, ppdev, parport, parport_pc loaded and cupsys restarted, gnome-cups-add won't detect anything at all. Some kernel output: [EMAIL PROTECTED]:~$ dmesg | tail [drm] Setting GART location based on new memory map [drm] Loading R300 Microcode [drm] writeback test succeeded in 1 usecs pnp: Device 00:0a disabled. pnp: Device 00:0a activated. parport: PnPBIOS parport detected. parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA] parport0: Legacy device lp0: using parport0 (interrupt-driven). ppdev: user-space parallel port driver -- cupsys does not automatically detect parallel printer https://launchpad.net/bugs/29050 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 48563] Re: filesystem check fails on boot, but filesystem isn't bad
A google search turned up this thread: The guy in that thread not only inhibits checking the volume on boot, but also sets it no not mount automatically at boot. Mhh, I thought 'noauto' was the default setting for vfat partitions after installation. It should be worth trying to comment out the whole hda1 line in /etc/fstab. Could you please also provide a copy of your fstab, or at least the relevant lines? Of course, this is merely a workaround, not a solution. As a side note: The boot sector should match its backup in the first place. This seems to be a Windows problem, however, since I've also seen this quite often back in the days without a Linux installation. That being said, it would still be a Good Thing if fsck/mount failed more gracefully, or at least provided the user with enough information to solve the problem (it seems a lot of people get confused by this problem). Anyway: This is a bug in dosfsutils, not in e2fsprogs. You may therefore get more help by filing a new bug report against dosfstools. Feel free to quote any information I gave you that you mayf find noteworthy. -- filesystem check fails on boot, but filesystem isn't bad https://launchpad.net/bugs/48563 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59293] Re: Dosfsck Run On Every Boot on FAT
Agreed. On my system, those dosfscks actually take longer than the remaining boot process combined. Perhaps it should be run after a certain amount of mounts or a certain number of days. The problem is that unlike ext2, Reiser3 et al, FAT doesn't store such when-to-check information in its superblock equivalent, not even when the file system has last been mounted. The latter is kept track of somewhere in the Windows registry instead. In case the FAT partition in question is not the one where Windows is installed, I see no reasonable way to get at this registry information. In case the FAT partition is actually the one containing the registry, it would have to be mounted first, which at the time it is checked during boot, it hasn't. Parsing the registry is not a trivial task and, in my opinion, not worth the hassle anyway. The only solution I see (short of storing it on another file system) would be to keep the neccessary information in some part of the FAT filesystem which is generally ignored by Windows and its scandisk/defrag tools, so as not to break Windows compatibility. Perhaps a reserved sector after the boot sector could be used, provided that doesn't need re-creating of the file system. Could anyone with practical FAT experience please evaluate this? I'm willing to write up a spec if enough people are interested in this feature. -- Dosfsck Run On Every Boot on FAT https://launchpad.net/bugs/59293 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 48563] Re: filesystem check fails on boot, but filesystem isn't bad
Mathiasdm wrote: /dev/hda1 FAT32 +-3GB (Acer recovery partition) I've never heard of this Acer recovery before, but it may be liable to confuse dosfsck, causing it to take so long and ultimately fail. It may be worth a try to investigate if older versions of dosfsck have this problem, too. Why does it drop into a shell? If any of the file system checks at boot time should fail, you are automatically dropped into kind of an emergency root shell. This is to give you a chance to fix the problem before the boot procedure continues. You *should* be able to leave this shell using the 'exit' command or by pressing Ctrl-D. Ctrl-C and Ctrl-D didn't work anymore What do you mean by didn't work anymore? Do you get any screen output after pressing Ctrl-D? What happens? If your computer just doesn't react to keypresses (seems to be hanging), try holding Alt+SysRq and pressing 'R'. This will put your keyboard into raw mode. After that, repeat your Ctrl-... procedure. This is only a guess, though -- it all depends on what you mean by didn't work anymore ;) Anyway, whatever the problem with this partition is, there may be a temporary workaround. It seems you haven't laid your hands on the command line too often yet, so I'll try to be verbose, just in case. In the root shell, type in 'nano /etc/fstab'. Using the nano editor should be pretty much self-explanatory. Find the line which tries to mount your hda1 partition. The last character in this line, an integer, specifies which priority the partition should have in the boot-up file system check. Probably, it says '2' right now. Change this into '0', meaning skip this partition. Save your file, exit nano, and exit the shell. On the next reboot, the recovery partition won't be checked anymore. -- filesystem check fails on boot, but filesystem isn't bad https://launchpad.net/bugs/48563 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 48563] Re: filesystem check fails on boot, but filesystem isn't bad
When booting, the system falls back to a shell while checking /dev/hda1. Could you please quote the output of fsck just before Ubuntu enters the shell? Which boot loader does your system use (GRUB, NTLDR, LiLo)? The /boot partition being the last one on disk looks problematic, too. Is there any option in your BIOS setup like Logical Block Adressing (LBA), and if so, is it activated? -- filesystem check fails on boot, but filesystem isn't bad https://launchpad.net/bugs/48563 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 48563] Re: filesystem check fails on boot, but filesystem isn't bad
/: Root inode is not a directory. Now this is interesting. If the root inode of any file system wasn't a directory, how could you traverse the file system at all? I'm not too much into the internals of inode-based fs', but the output of ls -ld / /. /.. may prove useful. -- filesystem check fails on boot, but filesystem isn't bad https://launchpad.net/bugs/48563 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 48563] Re: filesystem check fails on boot, but filesystem isn't bad
The weird thing is that / (/dev/hda5) shouldn't be being checked at all at this point The root filesystem is first checked by /etc/init.d/checkroot.sh, but is checked again by checkfs.sh together with all other filesystems. Interestingly, during the aftermath of a power failure, I've come to encounter this very same message on a number of machines at work in the past weeks. fsck would not only complain about the root inode, but also about even graver inconsistencies. The ext2 filesystems were essentially wrecked, with no journal to recover from (*sigh*). The simplest solution to your problem is probably to boot from live CD, backup your root filesystem (e.g. `tar --create --one-file-system / -f /somewhere/else/root-backup.tar`), create a new ext3fs on hda5, then restore your backup. This won't tell you or me what went wrong in the first place, but at least it should give you a working system. PS: You're not, by chance, having this problem using a Pyramid server, are you? ;) -- filesystem check fails on boot, but filesystem isn't bad https://launchpad.net/bugs/48563 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 48563] Re: filesystem check fails on boot, but filesystem isn't bad
Could you please include the error messages you mentioned, even the minor ones? -- filesystem check fails on boot, but filesystem isn't bad https://launchpad.net/bugs/48563 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
