[Bug 373862] [NEW] jaunty release is broken, replaced with debian.lenny release and it works
Public bug reported: 1) lsb_release -rd Description:Ubuntu 9.04 Release:9.04 2) amanda-client: Installed: 1:2.5.2p1-4 Candidate: 1:2.5.2p1-4 Version table: 1:2.5.2p1-4 0 500 http://mirror.cc.vt.edu jaunty/universe Packages *** 1:2.5.2p1-4 0 100 /var/lib/dpkg/status 3) I expected amanda-client to provide backups to the amanda-server as normal and as it has for years on this computer. 4) what happened instead Right after I upgraded to jaunty from intrepid this bug appeared. I have several debian and ubuntu machines and have isolated the problem to the jaunty amanda package. Even though the version is the same between jaunty and debian/lenny at 2.5.2p1-4, apparently the packaging is different because the lenny version works and the jaunty does not. The sympton is that when the jaunty client is dumping to the amanda tape server, is times out and fails. It happens every time. This makes amanda from jaunty unusable as a client. As a workaround, I installed the debian/lenny bindary debs and held the packages until this bug is corrected. ** Affects: amanda (Ubuntu) Importance: Undecided Status: New -- jaunty release is broken, replaced with debian.lenny release and it works https://bugs.launchpad.net/bugs/373862 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 54897] no longer relevant
I responded earlier to this bug report that it was fixed by a kernel upgrade. The machine that I had this bug on is not running Ubuntu, but is running Debian/Etch. Therefore, I cannot test this new kernel against this bug. Sorry. -- James D. Freels, Ph.D. Oak Ridge National Laboratory [EMAIL PROTECTED] -- SCSI / AIC7xxx / Tape Library Problem https://bugs.launchpad.net/bugs/54897 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 50587] wrong owner on /etc/shadow
Public bug reported: Binary package hint: passwd this bug is identical to bug #166793 of the Debian tracking system and was corrected at 4.0.13-1 of Debian. The version in Dapper is 4.0.13-7ubuntu3, however it still lingers. The version in Debian/Testing is now 4.0.15 and the version in Debian/Unstable is 4.0.16. The version in Debian/Stable is 4.0.3 (much older). Presently, the owner of /etc/shadow is set to root.root each time the system is booted. The correct ownership should be root.shadow. Without the correct ownership, screensavers such as kscreensaver will not allow for a locked screen to open back up (password check fails). I have corrected the problem by manually changing the ownership of the //etc/shadow file to root.shadow at the console (Ctrl-Alt-F1). I also am trying a 4.0.16 build from unstable to see if it works after a reboot. ** Affects: shadow (Ubuntu) Importance: Untriaged Status: Unconfirmed -- wrong owner on /etc/shadow https://launchpad.net/bugs/50587 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50587] Re: [Bug 50587] Re: wrong owner on /etc/shadow
Due to my shortcomings in record-keeping of this bug and how I was led to file it, I too cannot see any good reason to pursue this further. I agree with you to clear the bug report as user error. Also, I will try to be less confrontational and I am very grateful for Ubuntu and all your good help. Perhaps I was looking at some of the old bug reports filed on the Debian side which confirmed my concern for this bug. On Wed, 2006-08-16 at 15:16 +, Mark Reitblatt wrote: > James, I did a quick search on the forum for "/etc/shadow permission" > and this was the only relevant link that came up: > http://ubuntuforums.org/showthread.php?t=97880&highlight=%2Fetc%2Fshadow+permission > , and it seems to be user error. Can you tell us if this happens for you > on a fresh install? > > What exactly do you want us to do here? No one else has been able to > reproduce the bug, and you haven't been giving us any suggestions as to > where your differences are coming from. I'm strongly inclined to chalk > it up to user error unless you show us that this happens on a clean > install for you. Otherwise, the logical conclusion is that this is > happening because of something you installed or some later update. In > which case it would be helpful to track down if it came from Ubuntu. > > Also, please be a little less confrontational. We are not "chastising > you" for "daring to file a bug", we are just trying to understand what > exactly is going on here. > -- James D. Freels, Ph.D. Oak Ridge National Laboratory [EMAIL PROTECTED] http://www.comsol.com/stories/hfir/ -- wrong owner on /etc/shadow https://launchpad.net/bugs/50587 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50587] Re: [Bug 50587] Re: [Bug 50587] Re: wrong owner on /etc/shadow
I beg your pardon, I did respond and was promptly chastised for doing so. Inserted is my last correspondence offering whatever help you may want to fix the problem. The user forums are full of messages relating to this problem if you care to take a look. I just happened to be the only one who would "dare" to file a bug. Who would dare find a bug ? I of source have no control of when you do or do not call a bug a bug. All I can do is report what happened. From: Freels, James D. <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [Bug 50587] Re: wrong owner on /etc/shadow Date: Thu, 22 Jun 2006 13:12:29 -0400 Point well taken. I did not mean to sound negative. If there is anything I can do to help fix this problem, please let me know and I will be glad to help out. On Thu, 2006-06-22 at 12:02 -0400, Mark Reitblatt wrote: > In which case you should have made it clear that this was an upgraded > system. That would seem to be relevant, wouldn't it? We are merely > showing that the bug doesn't seem exist on a clean dapper install. > Just to be sure, I reinstalled from scratch in VMWare, and checked. It > is still root:shadow. We weren't trying to tell you that your bug > doesn't exist. > > On 6/22/06, Freels, James D. <[EMAIL PROTECTED]> wrote: > Gentlemen, > > This bug has occurred on two separate systems that upgraded > from Breezy > to Dapper. In addition, the bug reappears after manually > correcting > the /etc/shadow file to fix the problem. Further, I have seen > this same > issue raised on numerous entries in the Ubuntu-forums even > after the > Dapper release. Therefore, I have no doubt of the bug, hence, > why it > was filed. > > On Wed, 2006-06-21 at 21:59 +, Mark Reitblatt wrote: > > It is root shadow here on a clean Dapper install. > > > -- > James D. Freels, Ph.D. > Oak Ridge National Laboratory > [EMAIL PROTECTED] > http://www.comsol.com/stories/hfir/ > > > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.2.2 (GNU/Linux) > > iD8DBQBEmpq4A77TwLIGdmIRAurUAJ4hNvgqW6qvvitdSEengdkSA > +Z94gCgkkZC > 7TkHqyp46LpDyyhHt3IxY3E= > =IfXF > -END PGP SIGNATURE- > > > > > > -- > Clothes make the man. Naked people have little or no influence in > society -- Mark Twain On Thu, 2006-07-27 at 03:06 +, Dennis Kaarsemaker wrote: > Given that the original reporter didn't respond and no one can reproduce > it, I'm rejecting this bug. > > status Rejected > > > ** Changed in: shadow (Ubuntu) >Status: Needs Info => Rejected > -- James D. Freels, Ph.D. Oak Ridge National Laboratory [EMAIL PROTECTED] http://www.comsol.com/stories/hfir/ -- wrong owner on /etc/shadow https://launchpad.net/bugs/50587 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 71255] Edgy versions are in compatible with older version
Public bug reported: Binary package hint: amanda-client After I upgraded to Edgy from Dapper, the amanda client on my desktop stopped backing up to the amanda server on a Debian/Sarge/Stable system. The remote server system is running version 2.4.4p3 of amanda whereas this version on my desktop is at v2.5.0p2. I fixed the problem by installing the Debian/Sarge/Stable packages onto my Ubuntu/Edgy system and holding the packages with dselect. I don't know why this problem exists and I searched the forums, bug reports, and the web and found no reason for this. ** Affects: amanda (Ubuntu) Importance: Undecided Status: Unconfirmed -- Edgy versions are in compatible with older version https://launchpad.net/bugs/71255 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 71255] Re: Edgy versions are in compatible with older version
lem. Without some sort of error > message it will be hard to reproduce and confirm the bug. Please specify > the error/info message you get that is indicative of the version > incompatibilities. > > ** Changed in: amanda (Ubuntu) >Status: Unconfirmed => Needs Info > -- James D. Freels, Ph.D. Oak Ridge National Laboratory [EMAIL PROTECTED] http://www.comsol.com/stories/hfir/ -- Edgy versions are in compatible with older version https://launchpad.net/bugs/71255 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 71255] Re: Edgy versions are in compatible with older version
I have now confirmed this bug to exist on a second Ubuntu/Edgy system which is my home machine. The home machine is an amanda server & client and serves only itself. I have had these errors and only level 0 backups since the upgrade to edgy on this machine. Home machine errors started on 10-22 Work machine errors started about 10-26 (I upgraded to edgy on the work machine after the home machine upgrade went OK) I should have paid closer attention. These amanda problems have existed since the edgy upgrade. This may be related to bug #32330. I am not sure, but I will try to find out. On Fri, 2006-11-10 at 21:49 +, Jeremy Teale wrote: > Hello and thank you for reporting. Your initial description lacks the > detail necessary to diagnose the problem. Without some sort of error > message it will be hard to reproduce and confirm the bug. Please specify > the error/info message you get that is indicative of the version > incompatibilities. > > ** Changed in: amanda (Ubuntu) >Status: Unconfirmed => Needs Info > -- James D. Freels, Ph.D. Oak Ridge National Laboratory [EMAIL PROTECTED] http://www.comsol.com/stories/hfir/ -- Edgy versions are in compatible with older version https://launchpad.net/bugs/71255 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 71255] perhaps this bug is caused by tar ?
0]: estimate time for hdb3 level 0: 0.121 sendsize[8710]: estimate size for hdb3 level 0: 10 KB sendsize[8710]: time 0.162: waiting for /bin/tar "hdb3" child sendsize[8710]: time 0.162: after /bin/tar "hdb3" wait sendsize[8710]: time 0.163: getting size via gnutar for hdb3 level 1 sendsize[8710]: time 0.165: spawning /usr/lib/amanda/runtar in pipeline sendsize[8710]: argument list: /bin/tar --create --file /dev/null --directory /mp3s --one-file-system --numeric-owner --listed-incremental /var/lib/amanda/gnutar-lists/fea_homehdb3_1.new --sparse --ignore-failed-read --totals --exclude-from /tmp/amanda/sendsize.hdb3.20061113111632000.exclude . sendsize[8710]: time 0.174: /bin/tar: Unexpected field value in snapshot file sendsize[8710]: time 0.175: /bin/tar: Error is not recoverable: exiting now sendsize[8710]: time 0.176: . sendsize[8710]: estimate time for hdb3 level 1: 0.011 sendsize[8710]: no size line match in /bin/tar output for "hdb3" sendsize[8710]: . sendsize[8710]: estimate size for hdb3 level 1: -1 KB sendsize[8710]: time 0.176: waiting for /bin/tar "hdb3" child sendsize[8710]: time 0.176: after /bin/tar "hdb3" wait sendsize[8710]: time 0.177: done with amname 'hdb3', dirname '/mp3s', spindle -1 sendsize[8706]: time 0.177: child 8710 terminated normally sendsize[8706]: time 0.177: waiting for any estimate child: 1 running sendsize[8712]: time 0.178: /bin/tar: Error is not recoverable: exiting now sendsize[8712]: time 0.179: . sendsize[8712]: estimate time for hdb9 level 1: 0.041 sendsize[8712]: no size line match in /bin/tar output for "hdb9" sendsize[8712]: . sendsize[8712]: estimate size for hdb9 level 1: -1 KB sendsize[8712]: time 0.179: waiting for /bin/tar "hdb9" child sendsize[8712]: time 0.179: after /bin/tar "hdb9" wait sendsize[8712]: time 0.180: done with amname 'hdb9', dirname '/iso', spindle -1 sendsize[8706]: time 0.180: child 8712 terminated normally sendsize: time 0.180: pid 8706 finish time Mon Nov 13 11:16:32 2006 -- James D. Freels, Ph.D. Oak Ridge National Laboratory [EMAIL PROTECTED] http://www.comsol.com/stories/hfir/ -- Edgy versions are in compatible with older version https://launchpad.net/bugs/71255 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 71255] the apparent amanda bug was caused by tar !
Having isolated the problem, I downgraded the tar package from v1.15.91-2 normally installed with Ubuntu/Edgy to the older v1.14-2.2 that is installed with the current Debian/Sarge/Stable. This, indeed, fixed the problem. So, should I file a tar bug report ? P.S. I did not try the new v1.16-1 that is available via Debian/Testing/Unstable. -- James D. Freels, Ph.D. Oak Ridge National Laboratory [EMAIL PROTECTED] http://www.comsol.com/stories/hfir/ -- Edgy versions are in compatible with older version https://launchpad.net/bugs/71255 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 117731] Re: Python crashes after attaching pty to a konsole kpart
I now have this problem in feisty due to an upgrade to kdebase et al on 09/26 (3.5.6-0ubuntu20.4). I would rather not upgrade to gutsy at the moment and my konsole is NOT usable. Crashes with the following error message: konsole kdecore (KProcess): WARNING: _attachPty() 11 KCrash: Application 'konsole' crashing... when opened from gnome-terminal ! -- Python crashes after attaching pty to a konsole kpart https://bugs.launchpad.net/bugs/117731 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 54897] Re: SCSI / AIC7xxx / Tape Library Problem
This issue was corrected by a patch that is going to be in the 2.6.23 release of the kernel. This issue was corrected only about a month ago. On Sun, 2007-09-09 at 11:23 +, Jérôme Guelfucci wrote: > Thank you for your bug report. Do you still have this issue with the > latest stable release of Ubuntu ? > > ** Changed in: linux-source-2.6.15 (Ubuntu) >Importance: Undecided => Medium >Status: New => Incomplete > James D. Freels, Ph.D. Senior Research Staff, HFIR Cold Source, ORNL http://sunsite.utk.edu/wuot/mt/podcast/051807HIFER.mp3 -- SCSI / AIC7xxx / Tape Library Problem https://bugs.launchpad.net/bugs/54897 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 86426] Re: MASTER: [Feisty] Evolution always tries to print A4
This is a bad bug. As a work around until it is fixed, I found I could print to file (.pdf will work), then open acroread and print from there and retain all the output as it should be. -- MASTER: [Feisty] Evolution always tries to print A4 https://bugs.launchpad.net/bugs/86426 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 68904] /sbin/init of upstart is different from /sbin/init of sysvinit and causes hang on boot
Public bug reported: Binary package hint: upstart I discovered this bug when upgrading from Dapper to Edgy. The upgraded system contained upstart and dependent packages ubuntu-minimal, upstart- compat-sysv, startup-tasks, system-services, upstart-logd. After upgrading, I rebooted and the system hang at the message "Freeing unused kernel memory: 204K freed". After much searching on the web for the cause of the problem, I discovered that a corrupt /sbin/init could be the cause, and if I issued "init=/bin/sh" at the kernel prompt at boot time, I could verify this; which I did. My system at home was similarly upgraded from Dapper to Edgy. However, for some reasson, it was installed with sysvinit and NOT upstart and dependent packages. Since my home system did not need upstart and dependent packages to work properly, I realized I could delete them from my work machine and then install sysvinit instead. So, I booted up under the Dapper live CD (don't have an Edby CD yet) and performed this task after copying the /sbin/init file and the sysvinit*.deb file from my home machine. My system now boots properly without upstart. The size of the /sbin/init file in upstart is different from sysvinit, so they ARE different. Why it does not work in upstart for my system is a puzzle I do not care to solve further, since I must now use my system for working. ** Affects: upstart (Ubuntu) Importance: Undecided Status: Unconfirmed -- /sbin/init of upstart is different from /sbin/init of sysvinit and causes hang on boot https://launchpad.net/bugs/68904 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 68904] Re: /sbin/init of upstart is different from /sbin/init of sysvinit and causes hang on boot
Scott, I tried this as you suggested. This basically just undoes what I had to do to fix the problem. So, when I undid things (added back the packages I deleted and then deleted sysvinit), then it caused the system to behave the same way. The --debug switch gave me no information when /sbin/init runs and it hung the system again. So, I put the system back the way it was (replacing upstart et. al., with sysvinit) and rebooted so I can send you this message. I also checked the log files in /var/log and nothing there from the --debug output either. For your information, I also run a custom kernel at v2.6.18.1. The .config for that kernel is attached. On Mon, 2006-10-30 at 13:10 +, Scott James Remnant wrote: > Please reinstall ubuntu-minimal (and thus upstart, etc.) and boot your > system removing "quiet" and "splash" from the kernel command-line, and > adding "--debug" > > (you can do this from the GRUB menu) > > Take a photo of the screen at the point it hangs > > ** Changed in: upstart (Ubuntu) > Assignee: (unassigned) => Scott James Remnant >Status: Unconfirmed => Needs Info > > ** Summary changed: > > - /sbin/init of upstart is different from /sbin/init of sysvinit and causes > hang on boot > + upstart causes hang on boot > -- James D. Freels, Ph.D. Oak Ridge National Laboratory [EMAIL PROTECTED] http://www.comsol.com/stories/hfir/ # # Automatically generated make config: don't edit # Linux kernel version: 2.6.18.1 # Sat Oct 14 16:26:19 2006 # CONFIG_X86_32=y CONFIG_GENERIC_TIME=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_X86=y CONFIG_MMU=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SYSVIPC=y # CONFIG_POSIX_MQUEUE is not set CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set # CONFIG_TASKSTATS is not set # CONFIG_AUDIT is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y # CONFIG_CPUSETS is not set # CONFIG_RELAY is not set CONFIG_INITRAMFS_SOURCE="" CONFIG_CC_OPTIMIZE_FOR_SIZE=y # CONFIG_EMBEDDED is not set CONFIG_UID16=y CONFIG_SYSCTL=y CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_SLAB=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # CONFIG_SLOB is not set # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y CONFIG_MODVERSIONS=y # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y CONFIG_STOP_MACHINE=y # # Block layer # # CONFIG_LBD is not set # CONFIG_BLK_DEV_IO_TRACE is not set # CONFIG_LSF is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y # CONFIG_IOSCHED_AS is not set # CONFIG_IOSCHED_DEADLINE is not set CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_AS is not set # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="cfq" # # Processor type and features # CONFIG_SMP=y CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set CONFIG_MPENTIUM4=y # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MGEODE_LX is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_CMPXCHG64=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_X86_TSC=y CONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y CONFIG_NR_CPUS=4 CONFIG_SCHED_SMT=y CONFIG_SCHED_MC=y # CONFIG_PREEMPT_NONE is not set # CONFIG_PREEMPT_VOLUNTARY is not set CONFIG_PREEMPT=y CONFIG_PREEMPT_BKL=y CONFIG_X86_LOCAL_APIC=y CONFI
Re: [Bug 68904] Re: upstart causes hang on boot
OK. I will try this again and quote everything I see on the screen. I will try to find a digital camera for the screen image too ! And add the inotify switch to the kernel configuration. Then let you know. Hopefully later today. On Wed, 2006-11-01 at 12:58 +, Scott James Remnant wrote: > Yes, I'm afraid that it's important that your system is reverted to the > non-working state for us to find out what's wrong. So far, you are the > only person with this problem out of the millions of people who are now > running edgy; so we need to figure out what's special about your system > and fix things. > > Does upstart literally not print anything? You don't see a line > beginning "init:" ? I would really appreciate a photo of the screen at > that point, there may be something really important on the screen at > that point that you've missed, or the lack of something important may be > what tells me what's wrong. > > There won't be anything in /var/log, at that point the system hasn't > booted so the filesystem isn't writable. We need to debug this the old > fashioned way I'm afraid. > > One thing I noticed in your kernel config: > > # CONFIG_INOTIFY is not set > > Could you try building a kernel with inotify support? > > I have a feeling that the failure to configure an inotify watch may > cause configuration files to not get parsed! > > ** Summary changed: > > - upstart causes hang on boot > + upstart causes hang on boot (possible inotify) > -- James D. Freels, Ph.D. Oak Ridge National Laboratory [EMAIL PROTECTED] http://www.comsol.com/stories/hfir/ -- upstart causes hang on boot (possible inotify) https://launchpad.net/bugs/68904 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 68904] Re: upstart causes hang on boot
Dear Scott et al.: Adding the CONFIG_INOTIFY flag to my kernel fixed this problem. Wonderful. upstart and dependent packages are now install on my system. This leads to another question. Perhaps I am the only one of millions of Unbuntu/Edgy users who likes to build my own kernel, but this seems incredible to me. I like a "lean" kernel with only what is necessary and only the proprietary drivers loaded as drivers (nvidia, vmware). I have been maintaining my linux systems for years this way long before Ubuntu was even thought of. I would like to continue to do this. I have two Ubuntu desktops and 3 Debian/stable servers I maintain in this fashion. Exclusive of the hardware drivers required, is there a list of kernel flag options that Ubuntu expects to be active that I can reference to make sure I am using all that Ubuntu has to offer ? (such as this one INOTIFY ?) Thanks for you help ! It is fixed and this bug can be removed. On Wed, 2006-11-01 at 12:58 +, Scott James Remnant wrote: > Yes, I'm afraid that it's important that your system is reverted to the > non-working state for us to find out what's wrong. So far, you are the > only person with this problem out of the millions of people who are now > running edgy; so we need to figure out what's special about your system > and fix things. > > Does upstart literally not print anything? You don't see a line > beginning "init:" ? I would really appreciate a photo of the screen at > that point, there may be something really important on the screen at > that point that you've missed, or the lack of something important may be > what tells me what's wrong. > > There won't be anything in /var/log, at that point the system hasn't > booted so the filesystem isn't writable. We need to debug this the old > fashioned way I'm afraid. > > One thing I noticed in your kernel config: > > # CONFIG_INOTIFY is not set > > Could you try building a kernel with inotify support? > > I have a feeling that the failure to configure an inotify watch may > cause configuration files to not get parsed! > > ** Summary changed: > > - upstart causes hang on boot > + upstart causes hang on boot (possible inotify) > -- James D. Freels, Ph.D. Oak Ridge National Laboratory [EMAIL PROTECTED] http://www.comsol.com/stories/hfir/ -- upstart causes hang on boot (possible inotify) https://launchpad.net/bugs/68904 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72002] v1.15.91-2 of Edgy incompatible with amanda-2.5.0p2-1 also of edgy
Public bug reported: Binary package hint: tar Please see bug #71255 for the explanation of this bug. The bug was worked around by installing an older version of tar from Debian/Sarge/Stable at v1.14-2.2. ** Affects: tar (Ubuntu) Importance: Undecided Status: Unconfirmed -- v1.15.91-2 of Edgy incompatible with amanda-2.5.0p2-1 also of edgy https://launchpad.net/bugs/72002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54897] Re: SCSI / AIC7xxx / Tape Library Problem
Hello. I think this bug is similar, if not identical, to a long- standing bug I have reported in the debian bug reports, then later in the kernel bug reports. Please take a look here: http://bugme.osdl.org/show_bug.cgi?id=5268 Perhaps if someone other than myself can verify this bug and demonstrate a 2nd, totally unrelated computer, has the same problem, it will gain a little priority and get fixed. Presently, I have just quite using this tape drive and using the later kernels since I have another tape drive that is doing the backups. But, I would like to gain this tape drive back. It worked fine under 2.6.12.6 and earlier. -- SCSI / AIC7xxx / Tape Library Problem https://launchpad.net/bugs/54897 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
