After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 311185 - Mini-Commander input area will not accept focus
Mini-Commander input area will not accept focus
Status: RESOLVED DUPLICATE of bug 311068
Product: gnome-applets
Classification: Other
Component: mini-commander
2.8.x
Other other
: Normal major
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-07-21 20:38 UTC by superbiskit
Modified: 2005-08-21 04:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description superbiskit 2005-07-21 20:38:51 UTC
Distribution: Debian testing/unstable
Package: gnome-applets
Severity: major
Version: GNOME2.10.2 2.8.x
Gnome-Distributor: Debian
Synopsis: Mini-Commander input area will not accept focus
Bugzilla-Product: gnome-applets
Bugzilla-Component: mini-commander
Bugzilla-Version: 2.8.x
Description:
Description of the crash:
not crash
The mini-commander applet does not permit typing into the inpur area,
selection from history is possible but the applet crashes after
launching the application

Steps to reproduce the crash:
1.  Place "Command-Prompt" on bottom-panel
2.  Attempt to enter a command
3. 

Expected Results:
Execute command

How often does this happen?
Every time

Additional Information:



Debugging Information:

Backtrace was generated from
'/usr/lib/gnome-applets/mini_commander_applet'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1222254464 (LWP 10676)]
[New Thread -1233208400 (LWP 10791)]
[New Thread -1232942160 (LWP 10790)]
[New Thread -1232675920 (LWP 10789)]
[New Thread -1224283216 (LWP 10737)]
0xffffe410 in __kernel_vsyscall ()




------- Bug moved to this database by unknown@gnome.bugs 2005-07-21 20:38 UTC -------


The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@gnome.bugs.
   Previous reporter was superbiskit@cox.net.

Comment 1 Danielle Madeley 2005-07-22 02:00:26 UTC
This bug occurs when running Metacity 2.10 with g-applets 2.8. Upgrade to
g-applets 2.10.

Not sure about the crash, could be related.
Comment 2 Sebastien Bacher 2005-08-07 21:30:47 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful in
determining the cause of the crash. Can you get us one with debugging symbols?
Please see [WWW]http://live.gnome.org/GettingTraces for more information on how
to do so.
Comment 3 Allison Karlitskaya (desrt) 2005-08-21 04:20:23 UTC
Crash is explained and fixed in bug 311068.

*** This bug has been marked as a duplicate of 311068 ***