Áron, the reporter's description actually seems fairly complete to me.
Please specify exactly what additional information he/she should be
supplying. The specific things we need for bugs is (1) the actions
taken, (2) the expected behavior (3) the actual behavior. For crashes,
we usually need traces. 1 through 3 have been provided.
RainCT, I have been experiencing this problem for a long time myself
(though it's much more like 2 seconds than 7, unless the box is fairly
busy), but had not tried Ctrl-C as a solution. I assumed it was just
bash taking a good time to load.
However, now that I've tried Ctrl-C, I discover that various things
(such as my customized prompt) are not correct. This leads me to believe
that the problem is that it takes a long time for bash to load its
initialization files. I imagine that (for instance) bash-completion
takes a while to load, among other things. Starting bash as "bash
--norc" seems to confirm this problem: it comes up _instantly_.
Do you have customizations made to your .bashrc? Please move your custom
.bashrc out of the way, and copy /etc/skel/.bashrc to your home
directory, and see if this makes a difference. If there is a significant
improvement, then the "bug" lies with your custom .bashrc, and this
report should be closed. If not, then it should be considered a bug in
the distributed rcfiles, and we'll handle it appropriately.
Moving bug from gnome-terminal to bash; reassigning to me, as I don't
see a request for specific information from Áron, and I have just asked
the reporter for information on results from various invocations.
** Changed in: bash (Ubuntu)
Sourcepackagename: gnome-terminal => bash
Assignee: Áron Sisak => Micah Cowan
--
Slow start time
https://bugs.launchpad.net/bugs/119526
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
