Bug 24780 - drakbug fails to send to firefox
Summary: drakbug fails to send to firefox
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2019-05-06 07:42 CEST by Franz Holzinger
Modified: 2020-07-10 03:47 CEST (History)
4 users (show)

See Also:
Source RPM: firefox? drakxtools?
CVE:
Status comment:


Attachments

Description Franz Holzinger 2019-05-06 07:42:15 CEST
When drakbug opens due to a crashing application of the Network Center, then the sending of the bug report fails.

This has been reported as bug #24768

I can see tabs "about:sessionrestore" and "bug.mageia.org/enter_bug", but I cannot open these tabs.
Comment 1 Marja Van Waes 2019-05-07 14:38:54 CEST
(In reply to Franz Holzinger from comment #0)
> When drakbug opens due to a crashing application of the Network Center, then
> the sending of the bug report fails.
> 
> This has been reported as bug #24768
> 
> I can see tabs "about:sessionrestore" and "bug.mageia.org/enter_bug", but I
> cannot open these tabs.

The "about:sessionrestore" page is displayed after a Firefox crash. This sounds like it then froze immediately upon restarting.

If firefox-66.0.4-1.mga7 doesn't work better, then please rename your /home/<you>/.mozilla to something else and try whether you still get such crashes/freezes



In bug #24768, comment #2, you said:
> I get the first connection with the GPRS modem where I enter the 4 digit PIN
> code. Then the Connect button gets activated. But I do not press on it. I
> press on the Configure button. Then I click on an item on the top list which
> is selected. I click on the cursor down button on the keyboard. Then it
> crashes the whole Network Center applet.
> 

At that point, when it the applet crashes, do you then have internet access? What do you see when you run, in a terminal/konsole:

   ping bugs.mageia.org

You can stop it with Ctrl C after the first few lines are written.

CC: (none) => marja11
Keywords: (none) => NEEDINFO

Comment 2 Franz Holzinger 2019-05-07 20:06:55 CEST
firefox-66.0.4-1.mga7 is not available yet.

After the application crash I still do have internet access over the WLAN cable connection.


[franz@localhost ~]$    ping bugs.mageia.org
PING bugs.mageia.org(sucuk.mageia.org (2a02:2178:2:7::7)) 56 data bytes
64 bytes from sucuk.mageia.org (2a02:2178:2:7::7): icmp_seq=1 ttl=59 time=33.8 ms
64 bytes from sucuk.mageia.org (2a02:2178:2:7::7): icmp_seq=1 ttl=59 time=34.4 ms (DUP!)
64 bytes from sucuk.mageia.org (2a02:2178:2:7::7): icmp_seq=2 ttl=59 time=33.3 ms
64 bytes from sucuk.mageia.org (2a02:2178:2:7::7): icmp_seq=2 ttl=59 time=33.9 ms (DUP!)
64 bytes from sucuk.mageia.org (2a02:2178:2:7::7): icmp_seq=3 ttl=59 time=34.0 ms
64 bytes from sucuk.mageia.org (2a02:2178:2:7::7): icmp_seq=3 ttl=59 time=34.4 ms (DUP!)
64 bytes from sucuk.mageia.org (2a02:2178:2:7::7): icmp_seq=4 ttl=59 time=33.6 ms
64 bytes from sucuk.mageia.org (2a02:2178:2:7::7): icmp_seq=4 ttl=59 time=34.4 ms (DUP!)
^C
--- bugs.mageia.org ping statistics ---
4 packets transmitted, 4 received, +4 duplicates, 0% packet loss, time 8ms
rtt min/avg/max/mdev = 33.260/33.974/34.413/0.445 ms


When I use the drakbug dialog box to report this issue, then a new firefox window with 2 tabs opens. And there is a lot of activity on the harddrive. However nothing else seems to happen.
Comment 3 Marja Van Waes 2019-05-07 22:10:18 CEST
Thanks for the feedback, Franz.

I hope firefox-66.0.4-1.mga7 fixes the issue (if it doesn't, then please try again as a new user or after moving ~/.mozilla away)

CC'ing the mageiatools maintainers (for drakbug) and all packagers collectively (for firefox).

CC: (none) => mageiatools, pkg-bugs
Source RPM: (none) => firefox? drakxtools?

Comment 4 Thierry Vignaud 2020-07-10 03:47:27 CEST
Presumed fixed as no report for 1 year

Resolution: (none) => OLD
CC: (none) => thierry.vignaud
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.