https://bugzilla.suse.com/show_bug.cgi?id=1203916
Bug ID: 1203916
Summary: SeaMonkey: update to 2.53.14
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.4
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Firefox
Assignee: factory-mozilla(a)lists.opensuse.org
Reporter: psychonaut(a)nothingisreal.com
QA Contact: qa-bugs(a)suse.de
CC: Andreas.Stieger(a)gmx.de, maintenance(a)opensuse.org,
meissner(a)suse.com, security-team(a)suse.de,
wolfgang.engel(a)suse.com
Depends on: 1199197, 1201406
Found By: ---
Blocker: ---
+++ This bug was initially created as a clone of Bug #1201406 +++
Please update the SeaMonkey package in Leap 15.4 and Leap 15.3 to the SeaMonkey
2.53.14 packages provided by the mozilla/seamonkey package on OBS:
<https://build.opensuse.org/package/show/mozilla/seamonkey>
The latest version of SeaMonkey, 2.53.14, released on 11 July 2022, contains
new backports of important security fixes from Firefox 91.11 ESR and
Thunderbird 91.11 ESR.
--
You are receiving this mail because:
You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1199941
Bug ID: 1199941
Summary: kmozillahelper uses up all X clients given enough
logout/login cycles
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.4
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Firefox
Assignee: factory-mozilla(a)lists.opensuse.org
Reporter: marix(a)marix.org
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
A couple days ago I ran into the issue of applications no longer starting
reliably on my openSUSE Leap 15.4 system. Launching applications like "glxinfo"
or "xlsclients" would fail with the error message `Maximum number of clients
reached: unable to open display ":0"`.
In searching for the error message I came across
https://unix.stackexchange.com/questions/250920/debugging-maximum-number-of….
Using the method described there to get the application using up the most x
client connections, I found that kmozillahelper was using up more than 170 of
them. Closing Firefox and one `killall kmozillahelper` later I could reliably
start applications again.
While my immediate problem is gone, it seems that there seems to be a leak of
kmozillahelper process instances when restoring a KDE session after having
logged out with an open Firefox. I.e., on third login after the killall, a `ps
aux | grep kmozillahelper` will produce the following:
marix 5109 0.0 0.1 413872 44192 ? Sl 11:10 0:00
/usr/lib/mozilla/kmozillahelper -session
10ca646469000165348143300000027740024_1653489712_189016
marix 5144 0.0 0.1 413872 44184 ? Sl 11:10 0:00
/usr/lib/mozilla/kmozillahelper -session
10ca646469000165348930800000285810021_1653489712_189016
marix 6070 0.2 0.1 416140 46532 ? Sl 11:10 0:00
/usr/lib/mozilla/kmozillahelper
Stopping Firefox will kill the process that does not have a -session argument.
However, if I logout without closing Firefox first, the next login will show
four kmozillahelper processes of which three have a with -session. The two
already existing in the current session, and a third one with a new sessionid.
As the session-id-less process instance is properly cleaned up if Firefox is
closed during a session, the problem can be worked around by closing Firefox
before logging out. However, this kind of contradicts the point of having
resumable sessions.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1205406
Bug ID: 1205406
Summary: xdotool doesn't show the correcz titles of firefox
windows any longer
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: openSUSE Tumbleweed
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Firefox
Assignee: factory-mozilla(a)lists.opensuse.org
Reporter: opensuse(a)mike.franken.de
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 862867
--> https://bugzilla.suse.com/attachment.cgi?id=862867&action=edit
window properties
Starting with openSUSE Tumbleweed 20221113 xdotool doesn't show the correct
titles of firefox any longer, instead returns "Firefox" or an empty string.
This worked as expected until I installed this snapshot a few minutes ago.
xdotool search --classname firefox
45088769
45088831
45088954
$ xdotool getwindowname 45088769
Firefox
$ xdotool getwindowname 45088831
$ xdotool getwindowname 45088954
Firefox
Systemsettings / Window management / Window rules still shows the correct
titles (see attachement).
This breaks my complete window management 8-(
--
You are receiving this mail because:
You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1205693
Andreas Stieger <Andreas.Stieger(a)gmx.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|Other |Firefox
Assignee|screening-team-bugs(a)suse.de |factory-mozilla(a)lists.opens
| |use.org
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1205511https://bugzilla.suse.com/show_bug.cgi?id=1205511#c3
Zaoliang Luo <zluo(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(zluo(a)suse.com) |
--- Comment #3 from Zaoliang Luo <zluo(a)suse.com> ---
(In reply to Martin Sirringhaus from comment #2)
> Would it be possible to click "Tell Mozilla about this crash" to submit the
> crashreport upstream and post the report-number here? (I don't know if
> QA-machines have Internet connectivity).
> Upstream can analyze this almost fully automatic and then we'd see if this
> is a known issue or not.
actually no on openqa.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1205511https://bugzilla.suse.com/show_bug.cgi?id=1205511#c2
Martin Sirringhaus <martin.sirringhaus(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |martin.sirringhaus(a)suse.com
| |, zluo(a)suse.com
Flags| |needinfo?(zluo(a)suse.com)
--- Comment #2 from Martin Sirringhaus <martin.sirringhaus(a)suse.com> ---
Would it be possible to click "Tell Mozilla about this crash" to submit the
crashreport upstream and post the report-number here? (I don't know if
QA-machines have Internet connectivity).
Upstream can analyze this almost fully automatic and then we'd see if this is a
known issue or not.
--
You are receiving this mail because:
You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1205105
Bug ID: 1205105
Summary: Firefox ships broken xml files (or it's parser is
broken)
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: All
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Firefox
Assignee: factory-mozilla(a)lists.opensuse.org
Reporter: packaging(a)sp1rit.anonaddy.me
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 862671
--> http://bugzilla.opensuse.org/attachment.cgi?id=862671&action=edit
Screenshot showing indicator window showing the error
Firefox 106.0.3 is incapable of rendering the XHTML file that defines the look
of the WebRTC indicator (that small window that spawns when you join a
video/audio conference).
Instead of the indicator being rendered inside the window, Firefox is currently
showing the following error:
XML Parsing Error: no root element found
Location: chrome://browser/content/webrtcLegacyIndicator.xhtml
Line Number 1, Column 1:
^
this behavior can also be replicated when opening
chrome://browser/content/webrtcLegacyIndicator.xhtml in a new tab.
This is happening on Tumbleweed 20221103 with MozillaFirefox-106.0.3-1.1.x86_64
--
You are receiving this mail because:
You are the assignee for the bug.