[Touch-packages] [Bug 1925823] Re: Ubuntu version of BASH losts or misinterprets the newline character coming from mouse paste
This bug is still there, I am interested in discussing it, but nobody assigned this bug to anybody. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1925823 Title: Ubuntu version of BASH losts or misinterprets the newline character coming from mouse paste Status in bash package in Ubuntu: Confirmed Bug description: Quiete a few experients shows, that bash misinterprets the newline- character coming from mouse paste, while in the same terminals the emacs or vim or alpine and many other character oriented programs interprest correctly. The problem is specific to the situation when we are at a bash prompt of a new version of bash we got in Ubuntu 21.04. As soon as I invoke an ssh session, the interpretation of the newline-caharcter becomes correct, since the remote older bash interprets correctly. >>> Newline bug of first kind: If there is a complete bash command with terminating newline in the cut and paste buffer, and it is pasted into a gnome-terminal, then the command is *not* executed, the newline is ignored by the terminal. >>> Newline bug of second kind: If I prepare a bash command say cp target-directory and I collect into the paste buffer "source-file newline-character" and I drop it IN BETWEEN the prepared "cp" and "target-directory" then the result is wrong: instead of interpreting the newline-character as "push enter" the command is broken into the followint 2 lines: cp source-file target-directory and I get an error message about missing target specification. cp: missing destination file operand after 'source-file' Try 'cp --help' for more information. bash: target-directory: Is a directory I found better to make this original bug descripton more informative. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1925823/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925823] Re: Ubuntu version of BASH losts or misinterprets the newline character coming from mouse paste
tags:added: impish ** Tags added: impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1925823 Title: Ubuntu version of BASH losts or misinterprets the newline character coming from mouse paste Status in bash package in Ubuntu: Confirmed Bug description: Quiete a few experients shows, that bash misinterprets the newline- character coming from mouse paste, while in the same terminals the emacs or vim or alpine and many other character oriented programs interprest correctly. The problem is specific to the situation when we are at a bash prompt of a new version of bash we got in Ubuntu 21.04. As soon as I invoke an ssh session, the interpretation of the newline-caharcter becomes correct, since the remote older bash interprets correctly. >>> Newline bug of first kind: If there is a complete bash command with terminating newline in the cut and paste buffer, and it is pasted into a gnome-terminal, then the command is *not* executed, the newline is ignored by the terminal. >>> Newline bug of second kind: If I prepare a bash command say cp target-directory and I collect into the paste buffer "source-file newline-character" and I drop it IN BETWEEN the prepared "cp" and "target-directory" then the result is wrong: instead of interpreting the newline-character as "push enter" the command is broken into the followint 2 lines: cp source-file target-directory and I get an error message about missing target specification. cp: missing destination file operand after 'source-file' Try 'cp --help' for more information. bash: target-directory: Is a directory I found better to make this original bug descripton more informative. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1925823/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925823] Re: losts or misinterprets the newline character coming from mouse paste
In addition to the correct behaviour of the GNU bash, I will not get that disturbing fancy behaviour of the Ubuntu 21.04 version, that instead of executing the command the dropped command is shown in reverse video. Hence the bug in question is clearly an Ubuntu re-packaging issue. ** Summary changed: - losts or misinterprets the newline character coming from mouse paste + Ubuntu version of BASH losts or misinterprets the newline character coming from mouse paste -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1925823 Title: Ubuntu version of BASH losts or misinterprets the newline character coming from mouse paste Status in bash package in Ubuntu: Confirmed Bug description: Quiete a few experients shows, that bash misinterprets the newline- character coming from mouse paste, while in the same terminals the emacs or vim or alpine and many other character oriented programs interprest correctly. The problem is specific to the situation when we are at a bash prompt of a new version of bash we got in Ubuntu 21.04. As soon as I invoke an ssh session, the interpretation of the newline-caharcter becomes correct, since the remote older bash interprets correctly. >>> Newline bug of first kind: If there is a complete bash command with terminating newline in the cut and paste buffer, and it is pasted into a gnome-terminal, then the command is *not* executed, the newline is ignored by the terminal. >>> Newline bug of second kind: If I prepare a bash command say cp target-directory and I collect into the paste buffer "source-file newline-character" and I drop it IN BETWEEN the prepared "cp" and "target-directory" then the result is wrong: instead of interpreting the newline-character as "push enter" the command is broken into the followint 2 lines: cp source-file target-directory and I get an error message about missing target specification. cp: missing destination file operand after 'source-file' Try 'cp --help' for more information. bash: target-directory: Is a directory I found better to make this original bug descripton more informative. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1925823/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925823] Re: losts or misinterprets the newline character coming from mouse paste
The bug is NOT the error of the original GNU package, but of the way how it is integrated into the Ubuntu 21.04, because if I download the GNU package itself, compile and try, then it works fine. In detail what I did: mkdir -p ~/bash cd ~/bash rm -fr bash-* sudo apt-get -y install byacc wget https://ftp.gnu.org/gnu/bash/bash-5.1.tar.gz tar xvzf bash-*.tar.gz rm bash-*.tar.gz cd bash-* time ( ./configure ; make ) env -i PATH="$PWD:$PATH" ./bash --noprofile --norc and here if I do the same cut and paste tests, and drop a command with a terminating line feed character, then this bash binary will simply execute it ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1925823 Title: Ubuntu version of BASH losts or misinterprets the newline character coming from mouse paste Status in bash package in Ubuntu: Confirmed Bug description: Quiete a few experients shows, that bash misinterprets the newline- character coming from mouse paste, while in the same terminals the emacs or vim or alpine and many other character oriented programs interprest correctly. The problem is specific to the situation when we are at a bash prompt of a new version of bash we got in Ubuntu 21.04. As soon as I invoke an ssh session, the interpretation of the newline-caharcter becomes correct, since the remote older bash interprets correctly. >>> Newline bug of first kind: If there is a complete bash command with terminating newline in the cut and paste buffer, and it is pasted into a gnome-terminal, then the command is *not* executed, the newline is ignored by the terminal. >>> Newline bug of second kind: If I prepare a bash command say cp target-directory and I collect into the paste buffer "source-file newline-character" and I drop it IN BETWEEN the prepared "cp" and "target-directory" then the result is wrong: instead of interpreting the newline-character as "push enter" the command is broken into the followint 2 lines: cp source-file target-directory and I get an error message about missing target specification. cp: missing destination file operand after 'source-file' Try 'cp --help' for more information. bash: target-directory: Is a directory I found better to make this original bug descripton more informative. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1925823/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925823] Re: losts or misinterprets the newline character coming from mouse paste
If I remain inside Ubuntu 21.04, but compile the previous version of bash, then the error disappears, ... this suggest that the erorr is not the consequence of the version of Ubuntu, but the "bash, version 5.1.4(1)-release" itself, or perhaps an Ubuntu specific configuration of the environment. In detail: mkdir ~/bash cd ~/bash wget https://ftp.gnu.org/gnu/bash/bash-5.0.tar.gz tar xvzf bash-5.0.tar.gz cd bash-5.0 sudo apt-get install byacc ./configure make env -i PATH="$PWD:$PATH" ./bash --noprofile --norc and here if I drop something containing a line feed character, the bash will correctly execute the currently edited commandline -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1925823 Title: losts or misinterprets the newline character coming from mouse paste Status in bash package in Ubuntu: Confirmed Bug description: Quiete a few experients shows, that bash misinterprets the newline- character coming from mouse paste, while in the same terminals the emacs or vim or alpine and many other character oriented programs interprest correctly. The problem is specific to the situation when we are at a bash prompt of a new version of bash we got in Ubuntu 21.04. As soon as I invoke an ssh session, the interpretation of the newline-caharcter becomes correct, since the remote older bash interprets correctly. >>> Newline bug of first kind: If there is a complete bash command with terminating newline in the cut and paste buffer, and it is pasted into a gnome-terminal, then the command is *not* executed, the newline is ignored by the terminal. >>> Newline bug of second kind: If I prepare a bash command say cp target-directory and I collect into the paste buffer "source-file newline-character" and I drop it IN BETWEEN the prepared "cp" and "target-directory" then the result is wrong: instead of interpreting the newline-character as "push enter" the command is broken into the followint 2 lines: cp source-file target-directory and I get an error message about missing target specification. cp: missing destination file operand after 'source-file' Try 'cp --help' for more information. bash: target-directory: Is a directory I found better to make this original bug descripton more informative. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1925823/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925823] Re: losts or misinterprets the newline character coming from mouse paste
Sorry that I edited the original bug report, but I think it was better to make it more informative, and not to grab these improvements of the bug description among the comments. Read please, re-read please the new version of the bug report. ** Description changed: + Quiete a few experients shows, that bash misinterprets the newline- + character coming from mouse paste, while in the same terminals the emacs + or vim or alpine and many other character oriented programs interprest + correctly. + + The problem is specific to the situation when we are at a bash prompt of + a new version of bash we got in Ubuntu 21.04. As soon as I invoke an ssh + session, the interpretation of the newline-caharcter becomes correct, + since the remote older bash interprets correctly. + + >>> Newline bug of first kind: + If there is a complete bash command with terminating newline in the cut and paste buffer, and it is pasted into a gnome-terminal, then the command is *not* executed, the newline is ignored by the terminal. - But in return this bug, the pasted command is showed in reverse - coloring, + >>> Newline bug of second kind: - what is very disturbing when a command is not executed, but decorated in - a funny way instead. + If I prepare a bash command say - This is new in 21.04, the dropping commands into a gnome-terminal worked - fine in 20.10, ... + cp target-directory - ... and in the last 27 years of my linux usage. + and I collect into the paste buffer "source-file newline-character" + + and I drop it IN BETWEEN the prepared "cp" and "target-directory" + + then the result is wrong: + + instead of interpreting the newline-character as "push enter" + + the command is broken into the followint 2 lines: + + cp source-file + + target-directory + + and I get an error message about missing target specification. + + cp: missing destination file operand after 'source-file' + Try 'cp --help' for more information. + bash: target-directory: Is a directory + + I found better to make this original bug descripton more informative. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1925823 Title: losts or misinterprets the newline character coming from mouse paste Status in bash package in Ubuntu: Confirmed Bug description: Quiete a few experients shows, that bash misinterprets the newline- character coming from mouse paste, while in the same terminals the emacs or vim or alpine and many other character oriented programs interprest correctly. The problem is specific to the situation when we are at a bash prompt of a new version of bash we got in Ubuntu 21.04. As soon as I invoke an ssh session, the interpretation of the newline-caharcter becomes correct, since the remote older bash interprets correctly. >>> Newline bug of first kind: If there is a complete bash command with terminating newline in the cut and paste buffer, and it is pasted into a gnome-terminal, then the command is *not* executed, the newline is ignored by the terminal. >>> Newline bug of second kind: If I prepare a bash command say cp target-directory and I collect into the paste buffer "source-file newline-character" and I drop it IN BETWEEN the prepared "cp" and "target-directory" then the result is wrong: instead of interpreting the newline-character as "push enter" the command is broken into the followint 2 lines: cp source-file target-directory and I get an error message about missing target specification. cp: missing destination file operand after 'source-file' Try 'cp --help' for more information. bash: target-directory: Is a directory I found better to make this original bug descripton more informative. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1925823/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925823] Re: losts or misinterprets the newline character coming from mouse paste
** Summary changed: - losts or ignore the newline character coming from mouse paste + losts or misinterprets the newline character coming from mouse paste -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1925823 Title: losts or misinterprets the newline character coming from mouse paste Status in bash package in Ubuntu: Confirmed Bug description: If there is a complete bash command with terminating newline in the cut and paste buffer, and it is pasted into a gnome-terminal, then the command is *not* executed, the newline is ignored by the terminal. But in return this bug, the pasted command is showed in reverse coloring, what is very disturbing when a command is not executed, but decorated in a funny way instead. This is new in 21.04, the dropping commands into a gnome-terminal worked fine in 20.10, ... ... and in the last 27 years of my linux usage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1925823/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925823] Re: losts or ignore the newline character coming from mouse paste
bash --version gives: GNU bash, version 5.1.4(1)-release (x86_64-pc- linux-gnu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1925823 Title: losts or ignore the newline character coming from mouse paste Status in bash package in Ubuntu: Confirmed Bug description: If there is a complete bash command with terminating newline in the cut and paste buffer, and it is pasted into a gnome-terminal, then the command is *not* executed, the newline is ignored by the terminal. But in return this bug, the pasted command is showed in reverse coloring, what is very disturbing when a command is not executed, but decorated in a funny way instead. This is new in 21.04, the dropping commands into a gnome-terminal worked fine in 20.10, ... ... and in the last 27 years of my linux usage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1925823/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925823] [NEW] gnome-terminal losts or ignore the newline character coming from mouse paste
Public bug reported: If there is a complete bash command with terminating newline in the cut and paste buffer, and it is pasted into a gnome-terminal, then the command is *not* executed, the newline is ignored by the terminal. But in return this bug, the pasted command is showed in reverse coloring, what is very disturbing when a command is not executed, but decorated in a funny way instead. This is new in 21.04, the dropping commands into a gnome-terminal worked fine in 20.10, ... ... and in the last 27 years of my linux usage. ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Also affects: bash (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1925823 Title: gnome-terminal losts or ignore the newline character coming from mouse paste Status in bash package in Ubuntu: New Status in gnome-terminal package in Ubuntu: New Bug description: If there is a complete bash command with terminating newline in the cut and paste buffer, and it is pasted into a gnome-terminal, then the command is *not* executed, the newline is ignored by the terminal. But in return this bug, the pasted command is showed in reverse coloring, what is very disturbing when a command is not executed, but decorated in a funny way instead. This is new in 21.04, the dropping commands into a gnome-terminal worked fine in 20.10, ... ... and in the last 27 years of my linux usage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1925823/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
What kind of information shall I attach? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load Status in apport package in Ubuntu: New Bug description: $ dconf dump /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ [custom1] binding='BackSpace' command='gnome-session-quit --power-off' name='gnome-session-quit --power-off' [custom0] binding='g' command='gnome-terminal --geometry=80x99-0+0' name='gnome-terminal --geometry=80x99-0+0' $ In spite of the above, time to time, not always, but since 18.04 much much more frequently this settings fails to become active just after booting, ... my account is logged in automatically just after boot. If I log out and log in again, then these key bindings work. If I go to the system settings, and define again, then these work again. Earlier, before 18.04 this phenomenon was rare, namely once a week at most. But since 18.04 it is almost guaranteed, not deterministic, but highly probable, that after an initial boot or a warm reboot these key bindings will not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1755106/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1755106] [NEW] /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
Public bug reported: $ dconf dump /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ [custom1] binding='BackSpace' command='gnome-session-quit --power-off' name='gnome-session-quit --power-off' [custom0] binding='g' command='gnome-terminal --geometry=80x99-0+0' name='gnome-terminal --geometry=80x99-0+0' $ In spite of the above, time to time, not always, but since 18.04 much much more frequently this settings fails to become active just after booting, ... my account is logged in automatically just after boot. If I log out and log in again, then these key bindings work. If I go to the system settings, and define again, then these work again. Earlier, before 18.04 this phenomenon was rare, namely once a week at most. But since 18.04 it is almost guaranteed, not deterministic, but highly probable, that after an initial boot or a warm reboot these key bindings will not work. ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load Status in apport package in Ubuntu: New Bug description: $ dconf dump /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ [custom1] binding='BackSpace' command='gnome-session-quit --power-off' name='gnome-session-quit --power-off' [custom0] binding='g' command='gnome-terminal --geometry=80x99-0+0' name='gnome-terminal --geometry=80x99-0+0' $ In spite of the above, time to time, not always, but since 18.04 much much more frequently this settings fails to become active just after booting, ... my account is logged in automatically just after boot. If I log out and log in again, then these key bindings work. If I go to the system settings, and define again, then these work again. Earlier, before 18.04 this phenomenon was rare, namely once a week at most. But since 18.04 it is almost guaranteed, not deterministic, but highly probable, that after an initial boot or a warm reboot these key bindings will not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1755106/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754877] Re: either apport-gtk crashed with SIGSEGV or x-server crashed because of xzgv magnifying
*** This bug is a duplicate of bug 1552577 *** https://bugs.launchpad.net/bugs/1552577 Half of this bug is the duplicate of https://bugs.launchpad.net/bugs/1754885 and NOT of https://bugs.launchpad.net/bugs/1552577 SINCE in 1552577 and 1754885 the situations what caus the problems are different, only the resulting signal is the same. The other half of this bug is the duplicate of https://bugs.launchpad.net/bugs/1754887 During the creation of this error report it was not clear, which report of the three parallel reports remained alive. But later experiments made me clear the situation, and therefore later I allowed the apport- gtk produce the SEPARATE much more precise reports 1754885 and 1754887. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1754877 Title: either apport-gtk crashed with SIGSEGV or x-server crashed because of xzgv magnifying Status in apport package in Ubuntu: New Bug description: It happens time to time, when I try to magnify a scanned text-picture in XZGV, suddenly the whole graphical session terminates, I see the monitor in framebuffer character mode, and then I can log in for an other graphical session. Usually I reboot just after this login, and after this reboot I get the crash report possibility, ... this time three in parallel, but only the "apport-gtk crashed with SIGSEGV" out of these was successful to submit a crash report. This is the reason why the summary is a bit unsure: "either apport-gtk crashed with SIGSEGV or x-server crashed because of xzgv magnifying". I am not sure whether there is any problem with apport-gtk, because it might happen, that only the reboot disturbed it (I make the reboots before any crash report opportunity window shows up). I think the real problem is, that magnifying a larger picture in XZGV can kill the graphical session, regadless what other jobs wanted to remain alive in it. (this is 18.04 development branch, and xzgv 0.9.1-4, everything (evrypackage) are fresh up to date) ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: apport-gtk 2.20.8-0ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Mar 10 19:30:33 2018 ExecutablePath: /usr/share/apport/apport-gtk ExecutableTimestamp: 1518540671 InstallationDate: Installed on 2017-07-13 (240 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterpreterPath: /usr/bin/python3.6 JournalErrors: -- Logs begin at Fri 2018-03-09 12:38:41 CET, end at Sat 2018-03-10 19:35:01 CET. -- Mar 10 19:32:21 pc56 spice-vdagent[1670]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Mar 10 19:32:21 pc56 pulseaudio[1703]: [pulseaudio] pid.c: Daemon already running. Mar 10 19:32:46 pc56 pulseaudio[1499]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcCwd: /home/prohlep Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 SegvAnalysis: Segfault happened at: 0x7f43f443e5a9:mov(%rbx),%rdi PC (0x7f43f443e5a9) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGSEGV UpgradeStatus: Upgraded to bionic on 2018-03-09 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1754877/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754887] Re: apport-gtk crashed with SIGSEGV
*** This bug is a duplicate of bug 1552577 *** https://bugs.launchpad.net/bugs/1552577 "Comment here only if you think the duplicate status is wrong.", OK I do it. Because that bug is "Crash displayed after logging in.". And this bug is: apport-gtk crash IF no running firefox, and the apport wants to brig me to bugs.lunchpad.net to continue and finish the bug report. The resulting end is the same: "apport-gtk crashed with SIGSEGV", but the situation, context and reason is really different, hence it seems to be a different problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1754887 Title: apport-gtk crashed with SIGSEGV Status in apport package in Ubuntu: New Bug description: This is a fork of the compound "Bug 1754877", see https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1754877 This fork will be devoted to the "apport-gtk crashed with SIGSEGV" part of the compound bug 1754877, and the other fork parallel to this will contain to the original XZGV + Xorg issue. Due to the original issue (see bug 1754877) I usually reboot before any bug report possibility shows up, or even I do not login before the reboot. After reboot, the bug report possibility shows up earlier, than my firefox is started. Due to the original compound bug, I always get at least two bug report possibilities in parallel. When I try to answer the first immediately, and when this process arrives to that point, where the apport program tries to open the bugs.lunchpad.net for me, then I can see the ICON of firefox for a short second only in the left icon bar, and then it disapperas, and I get NO firefox at all. Then, when I open the firefox, and AFTER THIS OPENING I handle the other, second apport window waiting for me already since the beginnings, then it already can simply open a tab in the running firefox for me to continue the bug report there. My feeling is, that "apport-gtk crashed with SIGSEGV" belongs to the unsuccesful firefox opening, since the first bug report usually disappears. Whenever I try to reproduce the other "XZGV + Xorg issue", and the firefox is NOT opened IN ADVANCE,then I have an unsuccessful firefox opening experience with apport program: that report trial dies out, disappears. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: apport-gtk 2.20.8-0ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Mar 10 19:58:35 2018 ExecutablePath: /usr/share/apport/apport-gtk ExecutableTimestamp: 1518540671 InstallationDate: Installed on 2017-07-13 (240 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterpreterPath: /usr/bin/python3.6 JournalErrors: -- Logs begin at Fri 2018-03-09 12:38:41 CET, end at Sat 2018-03-10 20:13:45 CET. -- Mar 10 19:59:48 pc56 spice-vdagent[1675]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Mar 10 19:59:48 pc56 pulseaudio[1723]: [pulseaudio] pid.c: Daemon already running. Mar 10 20:00:13 pc56 pulseaudio[1521]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcCwd: /home/prohlep Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 SegvAnalysis: Segfault happened at: 0x7f19de99b5a9:mov(%rbx),%rdi PC (0x7f19de99b5a9) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGSEGV UpgradeStatus: Upgraded to bionic on 2018-03-09 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1754887/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393062] [NEW] Xorg freeze
Public bug reported: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1386534 the problem in question is kernel dependent, I use ALWAYS the current NOT necessairly LTS version, at the moment the version 14.10 3.13.0-36-generic NO problem 3.13.0-37-generic problem in question 3.16.0-23-generic problem in question 3.16.0-24-generic problem in question just at the starting of x the view collapses within 2-3 seconds and also the xkeyboard freeses but if I switch during the initial 2-3 grace seconds to Ctrl-Alt-1 virtual terminal, then I was successful to run the apport program in text mode this report session is the result of this apport trial, using the unique link provided at the end ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Nov 15 20:34:57 2014 DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (142 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to utopic on 2014-10-27 (19 days ago) dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sat Nov 15 20:31:23 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputA4Tech PS/2+USB Mouse MOUSE, id 8 inputCypress Cypress USB Keyboard / PS2 Mouse KEYBOARD, id 9 inputCypress Cypress USB Keyboard / PS2 Mouse KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze ubuntu utopic -- 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/1393062 Title: Xorg freeze Status in “xorg” package in Ubuntu: New Bug description: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1386534 the problem in question is kernel dependent, I use ALWAYS the current NOT necessairly LTS version, at the moment the version 14.10 3.13.0-36-generic NO problem 3.13.0-37-generic problem in question 3.16.0-23-generic problem in question 3.16.0-24-generic problem in question just at the starting of x the view collapses within 2-3 seconds and also the xkeyboard freeses but if I switch during the initial 2-3 grace seconds to Ctrl-Alt-1 virtual terminal, then I was successful to run the apport program in text mode this report session is the result of this apport trial, using the unique link provided at the end ProblemType: Bug Distr
[Touch-packages] [Bug 1386534] Re: kernel dependent deterministic view crash on X startup
There is a typo at the last item of the list above, so the correct list is: 3.13.0-36-generic NO problem 3.13.0-37-generic problem in question 3.16.0-23-generic problem in question 3.16.0-24-generic problem in question -- 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/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2
[Touch-packages] [Bug 1386534] Re: kernel dependent deterministic view crash on X startup
I have just received the new kernel 3.16.0-24-generic. but the problem is still there. 3.13.0-36-generic NO problem using the SAME system and config as in the problematik 3 other cases below: 3.13.0-37-generic problem in question 3.16.0-23-generic problem in question 3.16.0-23-generic problem in question -- 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/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+
[Touch-packages] [Bug 1386534] Re: kernel dependent deterministic view crash on X startup
WARNING: the apport above is with the kernel 3.13.0-36-generic, where there is no problem (see the origonal post), hence it is useful only for getting the configuration of my machine. In case of 3.16.0-23-generic I am not able to get a non-blank X neither a readable console, hence I can not provide an apport-collect result for that kernel. However, if someone could provide me a shell script for BLIND use, then I can login blindly into a character console and run that shell script, but I have NO CHANCE to answer any question or to make any selection, since I sen NOTHING useful: the character console is broken in a different way: the usual left edge is vibrating somewhere at the 80% of the width, an only every second scan row is visible, and what is beyond the rigth edge, that appears really fuzzy on the left side. Many thanks in advance, Péter. -- 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/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer
[Touch-packages] [Bug 1386534] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247525/+files/Lspci.txt -- 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/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-d
[Touch-packages] [Bug 1386534] LightdmGreeterLog.txt
apport information ** Attachment added: "LightdmGreeterLog.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247522/+files/LightdmGreeterLog.txt -- 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/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu
[Touch-packages] [Bug 1386534] LightdmGreeterLogOld.txt
apport information ** Attachment added: "LightdmGreeterLogOld.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247523/+files/LightdmGreeterLogOld.txt -- 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/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0
[Touch-packages] [Bug 1386534] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247534/+files/XorgLog.txt -- 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/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-m
[Touch-packages] [Bug 1386534] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247526/+files/Lsusb.txt -- 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/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-d
[Touch-packages] [Bug 1386534] LightdmLog.txt
apport information ** Attachment added: "LightdmLog.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247524/+files/LightdmLog.txt -- 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/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.li
[Touch-packages] [Bug 1386534] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247535/+files/XorgLogOld.txt -- 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/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.li
[Touch-packages] [Bug 1386534] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247532/+files/UdevLog.txt -- 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/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-m
[Touch-packages] [Bug 1386534] xserver.outputs.txt
apport information ** Attachment added: "xserver.outputs.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247538/+files/xserver.outputs.txt -- 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/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
[Touch-packages] [Bug 1386534] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247530/+files/ProcModules.txt -- 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/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.
[Touch-packages] [Bug 1386534] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247527/+files/ProcCpuinfo.txt -- 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/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.
[Touch-packages] [Bug 1386534] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247537/+files/xdpyinfo.txt -- 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/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1
[Touch-packages] [Bug 1386534] UnitySupportTest.txt
apport information ** Attachment added: "UnitySupportTest.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247533/+files/UnitySupportTest.txt -- 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/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
[Touch-packages] [Bug 1386534] GconfCompiz.txt
apport information ** Attachment added: "GconfCompiz.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247520/+files/GconfCompiz.txt -- 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/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.
[Touch-packages] [Bug 1386534] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247536/+files/Xrandr.txt -- 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/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa
[Touch-packages] [Bug 1386534] LightdmDisplayLog.txt
apport information ** Attachment added: "LightdmDisplayLog.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247521/+files/LightdmDisplayLog.txt -- 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/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu
[Touch-packages] [Bug 1386534] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247529/+files/ProcInterrupts.txt -- 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/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 ve
[Touch-packages] [Bug 1386534] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247531/+files/UdevDb.txt -- 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/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa
[Touch-packages] [Bug 1386534] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247528/+files/ProcEnviron.txt -- 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/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.
[Touch-packages] [Bug 1386534] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247518/+files/Dependencies.txt -- 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/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 versio
[Touch-packages] [Bug 1386534] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247519/+files/DpkgLog.txt -- 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/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-m
[Touch-packages] [Bug 1386534] BootLog.txt
apport information ** Attachment added: "BootLog.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247517/+files/BootLog.txt -- 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/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-m
[Touch-packages] [Bug 1386534] Re: kernel dependent deterministic view crash on X startup
apport information ** Tags added: apport-collected compiz-0.9 ubuntu utopic ** Description changed: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. - I try to send the remaining information after my work day, now I have to - leave, sorry. + I try to send the remaining information after my work day, now I have to leave, sorry. + --- + .tmp.unity.support.test.0: + + ApportVersion: 2.14.7-0ubuntu8 + Architecture: amd64 + CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' + CompositorRunning: compiz + CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' + CompositorUnredirectFSW: true + CurrentDmesg: + [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning + [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service + [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service + [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. + [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. + DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job + DistroCodename: utopic + DistroRelease: Ubuntu 14.10 + DistroVariant: ubuntu + ExtraDebuggingInterest: Yes, including running git bisection searches + GraphicsCard: + Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) +Subsystem: XFX Pine Group Inc. Device [1682:3195] + InstallationDate: Installed on 2014-06-26 (124 days ago) + InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) + MachineType: System manufacturer System Product Name + Package: xorg 1:7.7+7ubuntu2 + PackageArchitecture: amd64 + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro + ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 + Tags: utopic ubuntu compiz-0.9 + Uname: Linux 3.13.0-36-generic x86_64 + UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 07/18/2011 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 2301 + dmi.board.asset.tag: To Be Filled By O.E.M. + dmi.board.name: M4A89GTD-PRO/USB3 + dmi.board.vendor: ASUSTeK Computer INC. + dmi.board.version: Rev 1.xx + dmi.chassis.asset.tag: Asset-1234567890 + dmi.chassis.type: 3 + dmi.chassis.vendor: Chassis Manufacture + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: + dmi.product.name: System Product Name + dmi.product.version: System Version + dmi.sys.vendor: System manufacturer + version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 + version.ia32-libs: ia32-libs N/A + version.libdrm2: libdrm2 2.4.56-1 + version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 + version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A + version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 + version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 + version.xserver-xorg-input-evdev: xserver-xorg-input-evde
[Touch-packages] [Bug 1386534] [NEW] kernel dependent deterministic view crash on X startup
Public bug reported: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- 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/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1386534/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
