Hi Joseph,
It works!
Thanks for giving me the detailed information. So actually the firmware of my
raidcard is old.
Is this something I could easily update? Or best to stay with the current
version now that the patch was made?
Thanks!
--
You received this bug notification because you are a
Hi Joseph,
I installed the image files and tested and it runs.
However, as before I could not install all: specifically the tools file gave a
problem.
Not sure if it matters for you or not, so
I copy the last part of the messages, so you can see it seems to be a
dependency error.
COPY:
Yep, bug resolved. Thank you very much for your effort and time.
Do you know in what ubuntu update it will be?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237392
Title:
kernels following
This one shows the error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237392
Title:
kernels following version 3.8.0-27 do not start
To manage notifications about this bug go to:
It Works!! I can't help but feel victory when it works only, though I
think I understand how a bisect works: like a binary search right?
Anyway: it works!!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Indeed the kernel runs again. Are we getting closer to the culprit?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237392
Title:
kernels following version 3.8.0-27 do not start
To manage
Right. This one runs ok! I will just keep it running and await your next
kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237392
Title:
kernels following version 3.8.0-27 do not start
To
Nope, didn't work. Looking forward to your next kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237392
Title:
kernels following version 3.8.0-27 do not start
To manage notifications about
Nope, not working. same same.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237392
Title:
kernels following version 3.8.0-27 do not start
To manage notifications about this bug go to:
Well: it works! The kernel start, I can logon, and do stuff!! Very
encouraging.
Let me know when you have the next kernel to do according to the bisect.
And thank you for your effort
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I must choose my words more carefully: I did dpkg -i *.deb (without the header
file this time).
It did not work for this kernel. Before I compile a new kernel, I remove the
old one.
Let me know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Sorry, said compile again: mean dpkg -i.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237392
Title:
kernels following version 3.8.0-27 do not start
To manage notifications about this bug go to:
Not sure what went wrong. First I compiled the kernel, and I saw that
the name was the same as an existing kernel. It didnt work, same error.
However, to be sure I uninstalled all the handmade kernels using
synaptic and now I cannot compile the kernel.
Also, I am missing one deb if I compare with
thanks, did that. The kernel does not work. It displays the same
problems.
Does that mean this is the offending patch? Do we need more installs to
find the commit that did it?
Let me know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The kernel you proposed to install, I installed. It produces pretty much the
same behaviour. So I guess it is not solved upstream.
I cannot change the status to kernel-bug-exists-upstream, it is not part of
the options. So I changed it to confirmed.
Hopefully you can change the status properly.
Right. Done that. Not sure how you got to these 2 kernels, but you are
absolutely right!
3.8.13.4 works: just booted, logged on and rebooted. No problem there.
3.8.13.5 had the same symptoms as the non-working kernels. i checked with the
recovery kernel and got largely the same output. It had
I installed the kernel, but it shows the same errors. Weird though, if
this is the only commit related to Areca Raid Controller.
What I notice is that the messages are mostly from arcmsr2 like: arcmsr2:
executing hw bus reset and
arcmsr: scsi bus reset eh returns with success and also:
As stated, using the recovery kernel, I drop to a terminal. The prompt
is {initramfs} and does not contain the program apport-collect. It is
not possible to run this command.
I am sorry. Will set the status to Confirmed as requested by the
previous note.
** Changed in: linux (Ubuntu)
Public bug reported:
All kernel updates on ubuntu following kernel 3.8.0-27 result in an
empty screen with no indication of startup, no response to the keyboard.
I can only start up using kernel version 3.8.0-27-generic. All following
numbers (up to and including 3.8.0-31-generic) do not result
This bug also effects tomcat6
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat7 in Ubuntu.
https://bugs.launchpad.net/bugs/1053090
Title:
tomcat7 cannot find server.xml in /usr/share/tomcat7/conf
To manage notifications about
I think I found what was wrong. In stead of calling
/usr/share/tomcat6/shutdown.sh directly, one should call service
tomcat6 restart : that works fine.
Will close this bug. Maybe docs do need some adjustment as the default
tomcat server still points to executing the shutdown.sh directly.
P.S.
This bug also effects tomcat6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1053090
Title:
tomcat7 cannot find server.xml in /usr/share/tomcat7/conf
To manage notifications about this bug go to:
I think I found what was wrong. In stead of calling
/usr/share/tomcat6/shutdown.sh directly, one should call service
tomcat6 restart : that works fine.
Will close this bug. Maybe docs do need some adjustment as the default
tomcat server still points to executing the shutdown.sh directly.
P.S.
Public bug reported:
Right after installing tomcat7, I added a user to /var/lib/tomcat7/conf
/tomcat-users.xml, when i wanted to restart the tomcat server.
So I went to /usr/share/tomcat7/bin where startup.sh and shutdown.sh are
located and started with ./shutdown.sh. This returned the following
Public bug reported:
Right after installing tomcat7, I added a user to /var/lib/tomcat7/conf
/tomcat-users.xml, when i wanted to restart the tomcat server.
So I went to /usr/share/tomcat7/bin where startup.sh and shutdown.sh are
located and started with ./shutdown.sh. This returned the following
Public bug reported:
Hi,
The antlr3.jar file from the website since version 3.1 contains gunit
functionality.
In the (K)ubuntu repository, antlr3 package has no jars containing gunit.
Gunit is a submodule of antlr3 provided to do junit-like testing on
antlr grammars.
Is it possible to include
Public bug reported:
Hi,
The antlr3.jar file from the website since version 3.1 contains gunit
functionality.
In the (K)ubuntu repository, antlr3 package has no jars containing gunit.
Gunit is a submodule of antlr3 provided to do junit-like testing on
antlr grammars.
Is it possible to include
Including tar gz of /var/log/dist-upgrade.
** Attachment added: tar gz of /var/log/dist-upgrade
http://launchpadlibrarian.net/19296092/dist-upgrade.tgz
--
During upgrade of 7.04 to 8.10 with adept-manager atop could not be installed
https://bugs.launchpad.net/bugs/292488
You received this
Public bug reported:
Binary package hint: update-manager
During the installation phase of the upgrade, the upgrade-manager informed me
that installation of 'atop' did not succeed.
The error message shown (Dutch) was:
subproces post-installation script gaf een foutwaarde 1 terug
which means:
Hi Richard,
I cannot reproduce the problem any more: the books I read using chm now all
turn out fine.
I apologize for the inconvenience.
P.S. I will leave it to you to close the question and the bug.
unless someone else still has the issue.
Guus.
--
Reading books in Kchmviewer:
30 matches
Mail list logo
