Public bug reported:
I start up my Ubuntu 16.04 machine and immediately after loginning in to
the GUI I get a crash report about the hub-service. Often this is
followed by one or two other reports but not today.
Today I followed the instructions on:
https://help.ubuntu.com/community/ReportingBu
This morning the second automated bug report prompted me to create
+bug1753393
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to hud in Ubuntu.
https://bugs.launchpad.net/bugs/1748844
Title:
hud-service crash with qmessageLogger::fatal() repo
Occurred again this morning and an automated bug report brought me back
here.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to hud in Ubuntu.
https://bugs.launchpad.net/bugs/1748844
Title:
hud-service crash with qmessageLogger::fatal() repor
Seems simple enough to recreate this each time I restart the machine.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to hud in Ubuntu.
https://bugs.launchpad.net/bugs/1748844
Title:
hud-service crash with qmessageLogger::fatal() reported at l
The problem happened again this morning.
As requested above I have filed a new report at #1756835. Hopefully
this will include more useful diagnostic information.
** Information type changed from Private to Public
--
You received this bug notification because you are a member of DX
Packages, w
Would +bug1756835 work better as a link?
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to hud in Ubuntu.
https://bugs.launchpad.net/bugs/1753393
Title:
window-stack-bridge crashed with SIGABRT in QMessageLogger::fatal()
Status in hud packag
Changing report to Public so that others can see it.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to hud in Ubuntu.
https://bugs.launchpad.net/bugs/1753393
Title:
window-stack-bridge crashed with SIGABRT in QMessageLogger::fatal()
Status i
Occurred again today. New report raised at +bug1756839
I raised a new report as this bug seems to happen as a pair with another
bug. The original pair that went with this bug (+bug1753393) asked me
to raise a new bug to see if better diagnostics were included. I have
done so and created +bug175
Happened again today. Raised #1760792 this morning to see if the trace
will work. If it does not I shall try adding more -dev packages to see
if the backtrace can be brought about.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to hud in Ubunt
9 matches
Mail list logo
