Actually
https://git.launchpad.net/ubuntu/+source/apport/commit/apport/ui.py?h=ubuntu/quantal=5080c104ebb3a02c4f16a3f6646449db8c72b545
lists a fix (--hanging) for this being available since quantal.
** Tags removed: focal
** Changed in: apport (Ubuntu)
Status: Confirmed => Fix Released
*** This bug is a duplicate of bug 1861609 ***
https://bugs.launchpad.net/bugs/1861609
Exact reproduction conditions of bug #1891636 and bug #1891745 unknown.
At least OOPS ID 6647d368-df04-11ea-af91-fa163ee63de6 uploaded to
errors.ubuntu.com now, marking these two as duplicates for now.
**
Also https://errors.ubuntu.com/user/$(sudo cat /var/lib/whoopsie
/whoopsie-id) claims "No errors have been reported from this system",
which is consistent with no ".uploaded" files appearing.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Description changed:
[Impact]
1. When trying to send a report manually, you can not
- 2. When next possibly unrelated crash of same process happens, .crash
gets overwritten even if .crash.upload exists (= upload not yet
completed?)
- 3. When trying to copy-paste the stacktrace as text,
** Description changed:
[Impact]
1. When trying to send a report manually, you can not
- 2. When trying to copy-paste the stacktrace as text, you can not
+ 2. When next possibly unrelated crash of same process happens, .crash
gets overwritten even if .crash.upload exists (= upload not yet
Public bug reported:
This instance happened after lockscreen, as such may be suspend-resume
related. On the other hand at least 0 and 10 parts on backtrace appear
similar to bug #1891636
While this appears to be a recent regression, DpkgLog.txt doesn't
contain xorg references. Could it be
Public bug reported:
[Impact]
1. When trying to send a report manually, you can not
2. When trying to copy-paste the stacktrace as text, you can not
[Test Case]
Start Ubuntu
Open terminal
$ ubuntu-bug /var/crash/.crash does not appear to send anything to
errors.ubuntu.com, when NetworkManager
No such feature seen yet on Focal version of ubuntu-bug either.
** Tags added: focal
** Changed in: apport (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
Not reproducible on fresh install on same hardware.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1871916
Title:
Navi gpu falls back to vesa/radeon/fbdev/etc drivers
Public bug reported:
Installed (upgraded 16->18->20 beta) ubuntu appears to utilize incorrect
x.org drivers for RX 5500 XT. Those drivers appear to be missing
features like multi-monitor support. On the other hand live-usb of 20.04
beta did manage to utilize all 3 connected monitors (before
Semi-worksforme @ OTA-15, as in symptoms disappeared for now.
But we shall see whether actual bug(s) were addressed as well after
after 10 weeks assuming no OTA-16 before that.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Confirming identical symptoms (symantec sites) to the ones mentioned in
chromium issue linked above. Please consider removing misleading "self-
signed" -part from bug title.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Removed reference to one client of mine who happens to prefer security
by obscurity over crystal box approaches. Clarified description a little
bit as well and changed report to public. Test cases available on
request, although shouldn't really be needed unless we want to
white/blacklist this
Is this just useragent-sniffing / them mis-identifying the browser as
chrome 35? Or did you get other errors besides them complaining about
browser version?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in
Public bug reported:
Kernel logs from unattended-upgrades doing mkinitrd resemble Bug
#1253155 symptoms.
Mar 12 06:31:51 network kernel: [213747.796032] Request for unknown module key
'Magrathea: Glacier signing key: c7613364bc2aa19d70bf0c6e59bf8acaff65c879' err
-11
Mar 12 06:31:51 network
Got matching issue because of /usr full on an old unattended precise setup that
was trying to upgrade firefox.
Almost-interesting part of dpkg log just in case:
Errors were encountered while processing:
/var/cache/apt/archives/firefox_32.0.3+build1-0ubuntu0.12.04.1_amd64.deb
16 matches
Mail list logo
