Galeon crashes while navigating in https://bugs.launchpad.net/ubuntu

Bug #226750 reported by Amit Tendulkar
4
Affects Status Importance Assigned to Milestone
galeon (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Steps to reproduce:
- Start Galoen
- Go to https://bugs.launchpad.net/ubuntu
- Click "Report a bug" link
- Enter description as "Dummy bug" and click continue
- Select "No, I'd like to report a new bug"
- Under "In what package did you find this bug?" select "Choose"
- In the pop up box (I guess a DHTML page) click cancel.
- Galeon crashes

Other notes:
- I tried to collect the crash report. However I couldn't get the Galeon package with debugging symbols. Here is the output,
$ sudo apt-get install galeon-dbgsym
[sudo] password for amit:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  galeon-dbgsym: Depends: galeon (= 2.0.2-4ubuntu1) but 2.0.4-1ubuntu1 is to be installed
E: Broken packages

I checked the Galeon's version through synaptic and it is showing me as 2.0.4-1ubuntu1

Revision history for this message
Amit Tendulkar (amit-tendulkar-gmail) wrote :

My system details,

Ubuntu Hardy Heron

$ uname -a
Linux lap432 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thanks for your report. Launchpad interface has greatly changed since you've reported this issue. Are you able to reproduce it with the current version ?

Thanks in advance.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in galeon:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.