I was going to upload syslog with the correct info (what ubuntu-bug
uploads seems only about since current boot).
It seems the freeze is that severe (nothing on 3.19.0-17) or early that
nothing gets appended to syslog.
$ ls -lrt /var/log/syslog*
..
-rw-r- 1 syslog adm 52942 maí 1 13:17 /v
Public bug reported:
First READ about how I deceived ubuntu-bug!
I'm not sure it matters or what info ubuntu-bug collects, but I didn't
do "ubuntu-bug linux" since it gave an error:
"Problem in linux-image-3.19.0-13-generic
The problem cannot be reported:
This is not an official Ubuntu package
** Attachment added: "Shuold show what I updated after the boot (but not still
in effect)"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1452255/+attachment/4392194/+files/dpkg.log.1
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg
Public bug reported:
What I know for sure:
Locked screen - machine was frozen when I got back after
minutes/seconds. Has happened several times before but does not happen
most/all of the time.
Of course very annoying (so I'll switch from nouveau to propriatary as a
desperate move.. I really do n
Public bug reported:
[I reported with ubuntu-bug, seems ok, and provides same info as
"ubuntu-bug xorg" (as I then chose xorg)?]
I locked the screen (yes, I have dual screen setup) and when coming back
seconds/minutes later the pointer was frozen and I could not type in a
password. Note, I see th
Not sure about this. This package and/or gnome-session (and/or compiz)?
** Package changed: ubuntu => xserver-xorg-video-intel (Ubuntu)
** Description changed:
- [Update, see comment #5 and my response at #6.]
+ [Update, see first comment #7 and #8 (or first comment #5 and my
+ response at #6).]
[Not sure what (mesa) package to tag, there is a gnome-session[-bin] on likely
(more so than mesa that is not included in logs). Gnome-session without -bin
ending isn't even installed (GNOME3).]
Thanks for clarifying, I think you are saying, about here is the first
real error:
Apr 12 14:30:38
** Attachment added: "Really?: "Server terminated successfully (0). Closing log
file""
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1443116/+attachment/4373204/+files/Xorg.0.log.old
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg
** Attachment added: "Just in case, seems this only shows correct startup after
crash"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1443116/+attachment/4373205/+files/Xorg.0.log
** Summary changed:
- Xorg crash (probably out of memory)
+ Xorg crash(?) (probably out of memory)
--
You
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1443116/+attachment/4373203/+files/syslog
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1443116
Title:
Xorg
Public bug reported:
If memory runs out, maybe not much can be done, but I believe this has
not happened to me in older Ubuntu versions:
Apr 12 14:29:51 Ryksugan kernel: [15064.494054] Xorg: page allocation failure:
order:0, mode:0xa00d4
Apr 12 14:29:51 Ryksugan kernel: [15064.494063] CPU: 0 PID
11 matches
Mail list logo
