[Desktop-packages] [Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
This bug disappeared in my case, just when I switched to 2204 Jammy. I made a fresh install from scratch, not a dist-upgrade only. Is there anybody who still has this bug in Jammy, if his/her system is a fresh install from scratch? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height Status in GNOME Terminal: New Status in gnome-terminal package in Ubuntu: Triaged Bug description: 1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt + T) 2. "stty -a | grep rows" reports "rows 24; columns 80;" 3. Maximize the window (by clicking on the maximize button, or double clicking the title bar, or dragging the window up to the panel) 4. Do the same again to un-maximize the window 5. Now "stty -a | grep rows" reports "rows 23; columns 79;" Each time I do this, the window keeps getting one character shorter and one character narrower! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-terminal 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Mar 6 10:22:46 2014 InstallationDate: Installed on 2010-04-15 (1421 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
tags: added: impish ** Tags added: impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916890] Re: each maximisation + un-maximisation cycle of a gnome-termial windows will shrink the terminal by 1 row and by 1 column
*** This bug is a duplicate of bug 1288655 *** https://bugs.launchpad.net/bugs/1288655 Duplicate status is still correct. ** Tags added: impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1916890 Title: each maximisation + un-maximisation cycle of a gnome-termial windows will shrink the terminal by 1 row and by 1 column Status in gnome-shell package in Ubuntu: New Status in gnome-terminal package in Ubuntu: New Bug description: each maximisation + un-maximisation cycle of a gnome-termial windows will shrink the terminal by 1 row and by 1 column two such a sycles (maximize, unmaximize, maximize, unmaximize) shrinks from 80x42 to 78x40: prohlep@pc56:~$ resize COLUMNS=80; LINES=42; export COLUMNS LINES; prohlep@pc56:~$ resize COLUMNS=79; LINES=41; export COLUMNS LINES; prohlep@pc56:~$ resize COLUMNS=78; LINES=40; export COLUMNS LINES; prohlep@pc56:~$ My 20.10 is almost release default state, no extension, only a few kbd shortcuts, that's all. I use gnome shell with gnome-terminals. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1916890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925732] Re: gnome-terminal ignores the --geometry location requests
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 Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: gnome-terminal ignores the --geometry location requests Status in gnome-terminal package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in gnome-terminal package in Fedora: Invalid Bug description: The more gnome-specific and detailed bug description: the gnome-terminal either ignores or misinterprets the --geometry=+0+0 , --geometry=+0-0 , --geometry=-0+0 and --geometry=-0-0 requests, while mate-terminal executes the correct positioning in the same environment (display manager and window manager). In case of Wayland, the gnome-terminal ignores the requests listed above, while mate-terminal is correctly positioned, in contrary to the urban legend, that under Wayland such a positioning is imposibble. In case of Xorg, the gnome-terminal positions itself into the corners of the rectangle containing the physical screens, even if that corner is not inside any of the physical screens. I.e.: in case of Xorg the gnome-terminal is ready to position itself into a not visible corner of the virtual space contaning the physical screens instead of do the same as the mate-terminal can do: to position itself into a corner of the visible physical screen. === The bug of gnome-terminal is that it is not able to position intself into visible corners, while the mate-terminal can do it, ... and in general the usual graphical programs can do it since the 80's. *** The original bug description: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925732] Re: gnome-terminal ignores the --geometry location requests
tags:added: impish ** Tags added: impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: gnome-terminal ignores the --geometry location requests Status in gnome-terminal package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in gnome-terminal package in Fedora: Invalid Bug description: The more gnome-specific and detailed bug description: the gnome-terminal either ignores or misinterprets the --geometry=+0+0 , --geometry=+0-0 , --geometry=-0+0 and --geometry=-0-0 requests, while mate-terminal executes the correct positioning in the same environment (display manager and window manager). In case of Wayland, the gnome-terminal ignores the requests listed above, while mate-terminal is correctly positioned, in contrary to the urban legend, that under Wayland such a positioning is imposibble. In case of Xorg, the gnome-terminal positions itself into the corners of the rectangle containing the physical screens, even if that corner is not inside any of the physical screens. I.e.: in case of Xorg the gnome-terminal is ready to position itself into a not visible corner of the virtual space contaning the physical screens instead of do the same as the mate-terminal can do: to position itself into a corner of the visible physical screen. === The bug of gnome-terminal is that it is not able to position intself into visible corners, while the mate-terminal can do it, ... and in general the usual graphical programs can do it since the 80's. *** The original bug description: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1936238] Re: Lock screen does not properly give focus after unlocking on Wayland
*** This bug is a duplicate of bug 1928317 *** https://bugs.launchpad.net/bugs/1928317 ** Tags added: impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1936238 Title: Lock screen does not properly give focus after unlocking on Wayland Status in mutter package in Ubuntu: New Bug description: When using GDM on Wayland, after unlocking, the previously focused window (such as Firefox) is not focused. Alt+tab (or click) must be used to gain focus. On X, everything works as excepted (if you were using Firefox at the time of locking, Firefox will be focused after unlocking too). (Ubuntu 21.04, ThinkPad P14s) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1936238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928317] Re: window focus is lost after blank screen
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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1928317 Title: window focus is lost after blank screen Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Won't Fix Bug description: New in 21.04 hirsute default installation, the problem was not there in 20.10 . Environment: the default Wayland (source of other trubles as well, the most disturbing out of them is https://bugs.launchpad.net/ubuntu/+bug/1925732) and the Gnome shell Problem steps: (1) there are few windows on my screen and the focus is in one of them, I edit there something, (2) after 5 minutes of user inactivity the screen blanks, (3) I wish to resume the editing in the same window, hence I hit either a ctrl or shift key, or slightly move the mouse, (4) the view comes back, but none of the windows have the input focus! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1928317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928317] Re: window focus is lost after blank screen
tags:added: impish ** Tags added: impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1928317 Title: window focus is lost after blank screen Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Won't Fix Bug description: New in 21.04 hirsute default installation, the problem was not there in 20.10 . Environment: the default Wayland (source of other trubles as well, the most disturbing out of them is https://bugs.launchpad.net/ubuntu/+bug/1925732) and the Gnome shell Problem steps: (1) there are few windows on my screen and the focus is in one of them, I edit there something, (2) after 5 minutes of user inactivity the screen blanks, (3) I wish to resume the editing in the same window, hence I hit either a ctrl or shift key, or slightly move the mouse, (4) the view comes back, but none of the windows have the input focus! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1928317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
The bug is still present in 21.10 . This bug in 21.04 went away this August 2021 approx. But upgrading from 21.04 to 21.10 brought back the bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height Status in GNOME Terminal: New Status in gnome-terminal package in Ubuntu: Triaged Bug description: 1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt + T) 2. "stty -a | grep rows" reports "rows 24; columns 80;" 3. Maximize the window (by clicking on the maximize button, or double clicking the title bar, or dragging the window up to the panel) 4. Do the same again to un-maximize the window 5. Now "stty -a | grep rows" reports "rows 23; columns 79;" Each time I do this, the window keeps getting one character shorter and one character narrower! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-terminal 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Mar 6 10:22:46 2014 InstallationDate: Installed on 2010-04-15 (1421 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925732] Re: gnome-terminal ignores the --geometry location requests
** Description changed: + The more gnome-specific and detailed bug description: + + the gnome-terminal either ignores or misinterprets the + + --geometry=+0+0 , --geometry=+0-0 , --geometry=-0+0 and --geometry=-0-0 + + requests, while mate-terminal executes the correct positioning in the + same environment (display manager and window manager). + + In case of Wayland, the gnome-terminal ignores the requests listed + above, while mate-terminal is correctly positioned, in contrary to the + urban legend, that under Wayland such a positioning is imposibble. + + In case of Xorg, the gnome-terminal positions itself into the corners of + the rectangle containing the physical screens, even if that corner is + not inside any of the physical screens. + + I.e.: in case of Xorg the gnome-terminal is ready to position itself + into a not visible corner of the virtual space contaning the physical + screens instead of do the same as the mate-terminal can do: to position + itself into a corner of the visible physical screen. + + === The bug of gnome-terminal is that it is not able to position intself + into visible corners, while the mate-terminal can do it, ... and in + general the usual graphical programs can do it since the 80's. + + *** The original bug description: + The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. ** Tags removed: wayland wayland-session ** Tags added: geometry gnome-terminal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: gnome-terminal ignores the --geometry location requests Status in gnome-terminal package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in gnome-terminal package in Fedora: Invalid Bug description: The more gnome-specific and detailed bug description: the gnome-terminal either ignores or misinterprets the --geometry=+0+0 , --geometry=+0-0 , --geometry=-0+0 and --geometry=-0-0 requests, while mate-terminal executes the correct positioning in the same environment (display manager and window manager). In case of Wayland, the gnome-terminal ignores the requests listed above, while mate-terminal is correctly positioned, in contrary to the urban legend, that under Wayland such a positioning is imposibble. In case of Xorg, the gnome-terminal positions itself into the corners of the rectangle containing the physical screens, even if that corner is not inside any of the physical screens. I.e.: in case of Xorg the gnome-terminal is ready to position itself into a not visible corner of the virtual space contaning the physical screens instead of do the same as the mate-terminal can do: to position itself into a corner of the visible physical screen. === The bug of gnome-terminal is that it is not able to position intself into visible corners, while the mate-terminal can do it, ... and in general the usual graphical programs can do it since the 80's. *** The original bug description: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925732] Re: gnome-terminal ignores the --geometry location requests
** Summary changed: - [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal + gnome-terminal ignores the --geometry location requests -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: gnome-terminal ignores the --geometry location requests Status in gnome-terminal package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in gnome-terminal package in Fedora: Invalid Bug description: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925732] Re: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal
I have just made a couple of tests, and the result is: 1: mate-terminal interprets correctly the --geometry over the both of Wayland and Xorg ** hence it was rigth when I derived "theoretically" from the behaviour of the Gnome Shell, that also over Wayland the client programs can position their windows! Now we see, that even the mate-terminal is capable to position it's window on the base of my --geometry requests 2: gnome-terminal misinterprets the --geometry over Xorg but does something (see below) 3: gnome-terminal ignores the --geometry over Wayland ** hence the gnome-terminal is the package which has serious difficulties to interpret the --geometry requests, ... in detail: If the bottom of "left screen" is higher than the bottom of the "right screen" and the top of the "left screen" is also higher than the top of the "right screen", and the left bar is hidden, then IN XORG: gnome-terminal --geometry=+0+0 is not at the left edge gnome-terminal --geometry=+0-0 is neither at the left edge, but even worse: the bottom of the terminal, --- where we work usually, --- is below the left screen gnome-terminal --geometry=-0+0 is also at a wrong location: the top of it is over the top of the right screen gnome-terminal --geometry=-0-0 this is the only case, where it is at the right position: in the lower right corner, bravo! BUG / 1: in case of Xorg, the gnome-terminal takes the smallest rectangle containing the two screens, subtractes the hidden left bar asif it was shown there, and regardles whether there is a proper physical screen at the corner in question, it puts the window there, even if the user can not see it. BUG / 2: in case of Wayland, the gnome-terminal ignores the --geometry=-0+0 alike requests, while mate-terminal demonstrates, that all of these kind of requests can be correctly satisfied, even in spite of the urban legend, that it is imposibble over Wayland. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal Status in gnome-terminal package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in gnome-terminal package in Fedora: Invalid Bug description: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925732] Re: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal
** Changed in: gnome-terminal (Ubuntu) Status: Opinion => Confirmed ** Changed in: mutter (Ubuntu) Status: Opinion => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal Status in gnome-terminal package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in gnome-terminal package in Fedora: Invalid Bug description: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
The error works on 21.04 Wayland as well. This bug looks very stable, depending only on the gnome terminal itself, regardless of which version of it is used. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height Status in GNOME Terminal: New Status in gnome-terminal package in Ubuntu: Triaged Bug description: 1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt + T) 2. "stty -a | grep rows" reports "rows 24; columns 80;" 3. Maximize the window (by clicking on the maximize button, or double clicking the title bar, or dragging the window up to the panel) 4. Do the same again to un-maximize the window 5. Now "stty -a | grep rows" reports "rows 23; columns 79;" Each time I do this, the window keeps getting one character shorter and one character narrower! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-terminal 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Mar 6 10:22:46 2014 InstallationDate: Installed on 2010-04-15 (1421 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
The problem is still there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916890] Re: each maximisation + un-maximisation cycle of a gnome-termial windows will shrink the terminal by 1 row and by 1 column
*** This bug is a duplicate of bug 1288655 *** https://bugs.launchpad.net/bugs/1288655 Duplicate status looks correct. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1916890 Title: each maximisation + un-maximisation cycle of a gnome-termial windows will shrink the terminal by 1 row and by 1 column Status in gnome-shell package in Ubuntu: New Status in gnome-terminal package in Ubuntu: New Bug description: each maximisation + un-maximisation cycle of a gnome-termial windows will shrink the terminal by 1 row and by 1 column two such a sycles (maximize, unmaximize, maximize, unmaximize) shrinks from 80x42 to 78x40: prohlep@pc56:~$ resize COLUMNS=80; LINES=42; export COLUMNS LINES; prohlep@pc56:~$ resize COLUMNS=79; LINES=41; export COLUMNS LINES; prohlep@pc56:~$ resize COLUMNS=78; LINES=40; export COLUMNS LINES; prohlep@pc56:~$ My 20.10 is almost release default state, no extension, only a few kbd shortcuts, that's all. I use gnome shell with gnome-terminals. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1916890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928317] Re: window focus is lost after blank screen
OK, if a bug must be filed to a source package, and nobody who knows this much better than me did it in the last two weeks, then I will now signal my first guess: the windows manager, perhapes it handles the erroneous behaviour of blanking, I do not know. Sorry, if I made a wrong guess. ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1928317 Title: window focus is lost after blank screen Status in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: New in 21.04 hirsute default installation, the problem was not there in 20.10 . Environment: the default Wayland (source of other trubles as well, the most disturbing out of them is https://bugs.launchpad.net/ubuntu/+bug/1925732) and the Gnome shell Problem steps: (1) there are few windows on my screen and the focus is in one of them, I edit there something, (2) after 5 minutes of user inactivity the screen blanks, (3) I wish to resume the editing in the same window, hence I hit either a ctrl or shift key, or slightly move the mouse, (4) the view comes back, but none of the windows have the input focus! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1928317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925732] Re: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal
OK, if you think that Wayland is responsible for the but, then: 1: this but must be upstreamed to the developers of the Wayland protocol 2: and this bug is also a bug of the "21.04 release as a whole", since it is a bug that it makes this buggy Wayland as default. I understand that this bug reporting system is package oriented, ... ok, then the base package of "21.04 release as a whole" which defines what packages belong to the release and what are the default settings HAS this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal Status in gnome-terminal package in Ubuntu: Opinion Status in mutter package in Ubuntu: Opinion Status in gnome-terminal package in Fedora: Invalid Bug description: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925732] Re: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal
"Although dragging could be done by relative movements. Setting an absolute position does appear to be impossible in Wayland." If it was really impossibble, then how the Gnome shell or any window manager can position *itself*? We see, that the diverse components of the diverse window managers does not float around in an uncontrolled way, but *somehow* they are able to tell to Wayland where to position that components. The gnome-terminal should be able to do the same, either directly ask Wayland, or indirectly ask the window manager, in return of the --geometry argument. Hence it is confirmed, that the problem in question is 1: either a severe bug of the windows manager itself 2: or a severe bug of the applications receiving the --geometry arguments. I am extremly upset of keeping this bug report on the level of "opinion". There are so uncomfortable problems around the terminal windowing since 21.04, https://bugs.launchpad.net/ubuntu/+bug/1925823 https://bugs.launchpad.net/ubuntu/+bug/1928317 https://bugs.launchpad.net/ubuntu/+bug/1916890 https://bugs.launchpad.net/ubuntu/+bug/1888098 https://bugs.launchpad.net/ubuntu/+bug/1288655 or the too thick capture bar of a terminal wastes the vertical space that I seriousely consieder to change to other distro. My work depends heavily on the comfort of character terminals I became used to in the late 80's, and since 21.04 the level of comfort reached a treshold of pain. And now, I can not achieve that this serious bug is taken seriously. This bug crosses the basics of the windowing standars hold already for decades. Perhaps one of the iconic feature of a windowing system is that an application can position the other windows. This was possibble already in the mid 80's! I simply do not understand what is going here around the Wayland, while on the other hand it seems to be a very promising progress in the technology of the windowing system. But why it is a so big issue to position a window by an other application? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal Status in gnome-terminal package in Ubuntu: Opinion Status in mutter package in Ubuntu: Opinion Status in gnome-terminal package in Fedora: Invalid Bug description: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
The bug is still there in Ubuntu 21.04, and is very disturbing when I need frequent maximalisation and reset to normal 80 columns, especially when I give classes at the university. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height Status in GNOME Terminal: New Status in gnome-terminal package in Ubuntu: Triaged Bug description: 1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt + T) 2. "stty -a | grep rows" reports "rows 24; columns 80;" 3. Maximize the window (by clicking on the maximize button, or double clicking the title bar, or dragging the window up to the panel) 4. Do the same again to un-maximize the window 5. Now "stty -a | grep rows" reports "rows 23; columns 79;" Each time I do this, the window keeps getting one character shorter and one character narrower! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-terminal 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Mar 6 10:22:46 2014 InstallationDate: Installed on 2010-04-15 (1421 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925732] Re: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal
The definition of "confirmed" is that "Verified by someone other than the reporter.", hence in case of "gnome-terminal" it was wrong to remove the "confirmed" tag, since someone other than me reported as well that the "gnome-terminal" is affected, and hence it is totally right, that the "gnome-terminal" is non the list named "Affects" with the status of "Confirmed". No one told, that "gnome-terminal" is mainly responsible for the bug, but the title of the list is *not* "The responsible packages", *but* "Affects". And it is "Confirmed" that "gnome-terminal" is "Affected". Henc I ask someone else, especially who removed it, to put back the "Confirmed" status. Since the "opinion" or "invalid" vould be missleading, and simply the opposite of the real truth. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal Status in gnome-terminal package in Ubuntu: Opinion Status in mutter package in Ubuntu: Opinion Status in gnome-terminal package in Fedora: Invalid Bug description: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925732] Re: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal
The bug is clearly stated, reproducible and confirmed by others as well. Hence it can not be ONLY "invalid + opinion + opinion" at 3 packages, and no package is mentioned with "new" or "confirmed". It is acceptable, if someone's opinion is that "mutter is not new but opinion only". But it is not acceptable, if the same person does not mark any other package or the Ubuntu as a whole as "new" or "confirmed", --- since if all the packages mentioned already becomes either "invalid" or "opinion", then the bug report is rejected in fact, what would be a wrong decision since the bug is there confiredly. In fact, if wayland protocol is not advanced enough to provide the original standard facility to handle the positioning of windows, then ALL the packages that wish to use this original standard instead of the new facilities, all of them have the bug, because it is a buggy behaviour to rely on something what is not offerd by the underlying wayland. Therefore the releases 21.04 as a whole has this bug: makes something defuault what brakes the all the packages which wish to position the main window of it's own applications. A disturbing exampe: $ wmctrl -d Cannot get current desktop properties. (_NET_CURRENT_DESKTOP or _WIN_WORKSPACE property) $ wmctrl -l $ wmctrl -d does not "List all desktops managed by the window manager." wmctrl -l does not "List the windows being managed by the window manager." While the same "wmctrl" packages works fine with Xorg. However the "wmctrl" can not be added to the affected packages, since the bugs.launchpad does not accept "wmctrl" as an existing package! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal Status in gnome-terminal package in Ubuntu: Opinion Status in mutter package in Ubuntu: Opinion Status in gnome-terminal package in Fedora: Invalid Bug description: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925732] Re: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal
A very personal comment: the main reason why I use linux exclusively since 1994 is that I can work in character terminal using the unix command line programming environment for my everyday goals (teaching and researching math and computational math). This is the reason why I am so sensitive for the missing positioning of my terminals, since I frequently invoke and kill terminals, depending on the actual needs, I have never abandoned windows waiting for nothing. Sorry for this very personal comment, but I wanted to explain why I wish not to consider "invalid" ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal Status in gnome-terminal package in Ubuntu: Opinion Status in mutter package in Ubuntu: New Status in gnome-terminal package in Fedora: Invalid Bug description: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925732] Re: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal
Sorry to oppose the opinion of those who probaly know the system much better than me, but it is simply NOT TRUE that neither Ubuntu nor especially Mutter is responsible for the huge step backward, the missing positioning of windows on the screen what was always possible since the 80's. AND it is neither true, that USING Wayland becomes impossible to handle the positioning. Wayland side: now I am in Mutter over Wayland w/o Xorg, and the top bar on the screen is NOT appearing randomly depending on the situation, but it is always aligned on the top of the actual screen, and it never extends to the other screen. HENCE the location of top, the location of top-left corner and the location of the top-right corner CAN BE handled, --- and I need exactly that: gnome-terminal --geometry=+0+0 == I wish a terminal into the top-left corner gnome-terminal --geometry=-0+0 == I wish a terminal into the top-right corner Ubuntu side: it is not Wayland but Ubuntu who made DEFAULT this Wayland w/o Xorg any warnings at the login screen, and even the fact that "the current login will fall into Wayladn w/o Xorg OR there will be Xorg services" IS HIDDEN, NOT SHOWN rigth where the account name and the password is due. HENCE Ubuntu as a strategic decider IS involved in the case. Mutter side: it is not true that Mutter is not capable to handle the positioning w/o Xorg, there are PLENTY evidences and indications, that Muter DOES EXACLTY KNOW where the edges of my two physical screens are. HENCE in spite of the backward downgrading of the Wayland protocol, Mutter is NOT behindered in knowing the rectangles of my two physical creens. Therefore Mutter IS also responsible, that the positioning of a gnome- terminal dos not work any longer if the default of Ubuntu is Wayland w/o Xorg. Sorry, I understand, that I could invoke the Xorg services which are now considered obsolote by Ubuntu, ... ... but I use computers since 1972, I was an active adult in parallel with the development of computer systems. HENCE my experience, that better not to deviate from the defaults, otherwise I will have more trubles, than to stand out somehow the defaults. That is why so interesting for me, that the traditional standard positionings of windows should work even over raw Wayland w/o Xorg services. This is the derivation, why I think that it is proven that the categorisation of "invalid" is wrong. Since I am the first reporter, therefore I can not switch this "invalid" back to the previous "confirmed", henc my only possibility now to change it back to "new", SORRY for that, but the "invalid" is not true, and it would behinder the handling of the problem if I leve it "invalid". I changed only at "mutter", since the gnome-terminal looks forwarding the positioning requests. Hence I have choosed "opinion" for the terminal, since there is no better choice for the situation, that the proper use of the gnome- terminals are behindered, actually that was the reason why we descovered the problem around Wayland and the default decison of Ubuntu, but the gnome-terminal looks not responsible for it's insufficient behaviour in the daily use. ** Changed in: mutter (Ubuntu) Status: Invalid => New ** Changed in: gnome-terminal (Ubuntu) Status: Invalid => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal Status in gnome-terminal package in Ubuntu: Opinion Status in mutter package in Ubuntu: New Status in gnome-terminal package in Fedora: Invalid Bug description: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925732] Re: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal
If the "GNOME shell" is able to ask Wayland to position the diverse elements of the destop, then the cooperation of the "GNOME shell" and "gnome-terminal" should be able to do the same. Wayland can be asked to position the top bar to the top of the screen, to position the side bar to the left of the scereen, ... then "GNOME shell" and "gnome-terminal" should be able to request at Wayland the top-right or top-left positioning according to the original request of gnome-terminal --geometry=-0+0" or "gnome-terminal --geometry=+0+0" respectively. To position someting into one of the 4 corners is so common request, that there shuld be a solution for that, --- hence this bug report is anyways a real problem of the cooperation of "gnome-terminal" and "GNOME shell" with "Wayland". Yet another issue: "I think it's more of a security feature than a bug, ..." --- If Wayland doesn't support the positioning request due to security concerns, then even the size requests shuold be forbidden and make that features obsolote as weel, since a request for maximal possibble size implies the dangerous request of positioning, namely into the upper left corner, what positioning request is considered a security threat. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal Status in GNOME Shell: New Status in gnome-terminal package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Bug description: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1925732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925732] Re: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal
** Also affects: gnome-shell Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal Status in GNOME Shell: New Status in gnome-terminal package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Bug description: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1925732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925732] Re: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal
"* Find a gnome-shell extension that will remember window positions for you;" Thanks, perhaps this is the best direction for me to proceed. Hence I suggest to close this bug report as "successful". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal Status in gnome-terminal package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Bug description: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925732] Re: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal
I do not find how to add "Wayland" to the "affects" list, help please. Thanks. "wayland-protocols (wayland-protocols) (Choose another project) wayland- protocols doesn't use Launchpad to track its bugs. If you know this bug has been reported in another bug tracker, you can link to it; Launchpad will keep track of its status for you." -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal Status in gnome-terminal package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925732] Re: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal
"... this is expected because windows only have control over their size, and NEVER THEIR POSITION, in Wayland" This is really a tragedy. One significant benefit for me of the linux world over the micro and soft world, that I can POSITION the windows of a project from my shell script starting that project or during the project. This is a design bug of Wayland, what needs to be fixed, regardless of the outcome of the test with "Xorg" (I will do after the funeral today). If there was no other protocol, if the Wayland was the only protocol, even in that case this is a very serious design bug. Hence I suggest to add "Wayland" to the "affects" list. Do I have to leave the Wayland world, and switch back to Xorg? But it was told, that Wayland is more advanced, that is the new direction. Is the new direction in 2021 that I can not control the location of a new windows from script? Then why it STILL is allowed, that we can control the location of a new window using a mouse? Is it possibble --- as a further enhancement --- to disable also the window positioning by the mouse? I do not find how to add "Wayland" to the "affects" list, help please. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal Status in gnome-terminal package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop Packages, which is subscribed to gnome-terminal 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925732] [NEW] new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal
Public bug reported: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. ** Affects: ubuntu Importance: Undecided Status: New ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal Status in Ubuntu: New Status in gnome-terminal package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1925732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
The bug is still there in Ubuntu 20.10, see the riport in https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1916890 each maximisation + un-maximisation cycle of a gnome-termial windows will shrink the terminal by 1 row and by 1 column two such a sycles (maximize, unmaximize, maximize, unmaximize) shrinks from 80x42 to 78x40 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height Status in GNOME Terminal: New Status in gnome-terminal package in Ubuntu: Triaged Bug description: 1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt + T) 2. "stty -a | grep rows" reports "rows 24; columns 80;" 3. Maximize the window (by clicking on the maximize button, or double clicking the title bar, or dragging the window up to the panel) 4. Do the same again to un-maximize the window 5. Now "stty -a | grep rows" reports "rows 23; columns 79;" Each time I do this, the window keeps getting one character shorter and one character narrower! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-terminal 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Mar 6 10:22:46 2014 InstallationDate: Installed on 2010-04-15 (1421 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916890] [NEW] each maximisation + un-maximisation cycle of a gnome-termial windows will shrink the terminal by 1 row and by 1 column
Public bug reported: each maximisation + un-maximisation cycle of a gnome-termial windows will shrink the terminal by 1 row and by 1 column two such a sycles (maximize, unmaximize, maximize, unmaximize) shrinks from 80x42 to 78x40: prohlep@pc56:~$ resize COLUMNS=80; LINES=42; export COLUMNS LINES; prohlep@pc56:~$ resize COLUMNS=79; LINES=41; export COLUMNS LINES; prohlep@pc56:~$ resize COLUMNS=78; LINES=40; export COLUMNS LINES; prohlep@pc56:~$ My 20.10 is almost release default state, no extension, only a few kbd shortcuts, that's all. I use gnome shell with gnome-terminals. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1916890 Title: each maximisation + un-maximisation cycle of a gnome-termial windows will shrink the terminal by 1 row and by 1 column Status in gnome-shell package in Ubuntu: New Status in gnome-terminal package in Ubuntu: New Bug description: each maximisation + un-maximisation cycle of a gnome-termial windows will shrink the terminal by 1 row and by 1 column two such a sycles (maximize, unmaximize, maximize, unmaximize) shrinks from 80x42 to 78x40: prohlep@pc56:~$ resize COLUMNS=80; LINES=42; export COLUMNS LINES; prohlep@pc56:~$ resize COLUMNS=79; LINES=41; export COLUMNS LINES; prohlep@pc56:~$ resize COLUMNS=78; LINES=40; export COLUMNS LINES; prohlep@pc56:~$ My 20.10 is almost release default state, no extension, only a few kbd shortcuts, that's all. I use gnome shell with gnome-terminals. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1916890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Someone wrote, not to me: "Then log out and in again to verify the bug still occurs without extensions.". However my ubuntu 20.10 is in default release state, I added *no* extension to it (I disbled a few kbd shortcuts, added two kbd shortcuts, so it is basically in release state). And I have the same disturbing setting, that DVI-0 connected primary 2560x1440+0+0 (in the reality this is my main monitor) DVI-1 connected 1680x1050+2560+504 (in the reality this is located as secondary) and almost everithing arrives to DVI-1, regardless how I started, from wich termial, Extremly disturbing, since I do not find any possibility to tell a program, to wich monitor to arrive. In addition to this, the terminal and the firefox arrives maximalised, and the do not know their suggested default size what is larger, thatn the size of the wrong target, --- --- since I have 2 monitors, I have to adjust all the window sizes by hand, as if it was a Windows. Since 1995, all my programs are started with suggested locations and sizes, what does not work any longer ... OK, one thing works, because the main monitor is on the left side: if I tell gnome-terminal --geometry=+0+0 but the gnome-terminal --geometry=-0+0 it will give a maximalised trash on the wrong monitor, and forgets the default nom-maximalised size as well. In addition to this, EACH maximalization and non-maximalisation cycle SHRINKS the size of the gnome-erminal by one row and one column: 80 ... 79 ... 78 ... This is an other bug, but I mention here because it might happen the same problem: the window size and location subsystem has serious problems ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755106] Re: Bug 1755106
The solution provided by Khurshid Alam seems to work correctly in the last 25 days. Day by day more likely, that the problem is solved. Many tanks for the help! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load Status in unity-settings-daemon package in Ubuntu: Confirmed 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/unity-settings-daemon/+bug/1755106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755106] Re: Bug 1755106
The problem with the nature below is still there after upgrading to 18.10. > The custom binding of Ctrl+Alt+G to > >gnome-terminal --geometry=80x99-0+0 > > is missing more frequently, than the custom binding of > Ctrl+Alt+Backspace to > >gnome-session-quit --power-off > > Does this help to locate the problem? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load Status in unity-settings-daemon package in Ubuntu: Confirmed 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/unity-settings-daemon/+bug/1755106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755106] Re: Bug 1755106
The custom binding of Ctrl+Alt+G to gnome-terminal --geometry=80x99-0+0 is missing more frequently, than the custom binding of Ctrl+Alt+Backspace to gnome-session-quit --power-off Does this help to locate the problem? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load Status in unity-settings-daemon package in Ubuntu: Confirmed 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/unity-settings-daemon/+bug/1755106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755106] Re: Bug 1755106
The problem is still there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load Status in unity-settings-daemon package in Ubuntu: Confirmed 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/unity-settings-daemon/+bug/1755106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755106] Re: Bug 1755106
The problem is still there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load Status in unity-settings-daemon package in Ubuntu: Confirmed 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/unity-settings-daemon/+bug/1755106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755106] Re: Bug 1755106
My problem is NOT whether the custom shortcuts work just after setting them or I need a log-out/log-in cycle. The problem is, that a half dozen times (= boots, usually in the morning) the ctrl-alt-g works, and then for one or two boots fails to load, and then agin works for a few days (this computer not running when I sleep). I understand, that ctrl-alt-backspace MAY be affected by the x-server. But the ctrl-alt-g is a "virgin use" of that keystroke, and they are always together good or bad, they behave never different. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load Status in unity-settings-daemon package in Ubuntu: Confirmed 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/unity-settings-daemon/+bug/1755106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755106] Re: Bug 175510 custom-keybindings fails to load
Now I am just reading the referred similar bug: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1435020 I have the very similar problems. In addition to that, when I applied the suggested "unity-settings-daemon --replace" command, then not only my custon settings, but the usual Ctrl-Alt-T terminal short cut also went away. But interestingly not everything went away, for example the Alt-` is still working (switch between the windows of the same binary), this is not in the custom section, and formerly it was a default setting. prohlep@pc56:~$ ps ax | grep settings-daemon 1934 ?Sl 0:00 /usr/lib/unity-settings-daemon/unity-fallback-mount-helper 3287 pts/0Sl+0:00 unity-settings-daemon --replace 3296 pts/0Sl+0:00 /usr/lib/unity-settings-daemon/usd-locate-pointer 3340 pts/1S+ 0:00 grep settings-daemon prohlep@pc56:~$ unity-settings-daemon --replace ** (unity-settings-daemon:3287): WARNING **: 09:12:51.381: Failed to load PNP ids: Failed to open file “/usr/share/hwdata/pnp.ids”: No such file or directory (unity-settings-daemon:3287): Gtk-WARNING **: 09:12:51.462: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory ** (unity-settings-daemon:3287): WARNING **: 09:12:51.539: Failed to load PNP ids: Failed to open file “/usr/share/hwdata/pnp.ids”: No such file or directory ** (unity-settings-daemon:3287): WARNING **: 09:12:51.539: Failed to load PNP ids: Failed to open file “/usr/share/hwdata/pnp.ids”: No such file or directory (unity-settings-daemon:3287): media-keys-plugin-WARNING **: 09:12:51.552: Grab failed for some keys, another application may already have access the them. (usd-locate-pointer:3296): Gtk-WARNING **: 09:12:51.559: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory (unity-settings-daemon:3287): Gtk-WARNING **: 09:12:51.566: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory ** (unity-settings-daemon:3287): WARNING **: 09:12:51.582: Failed to load PNP ids: Failed to open file “/usr/share/hwdata/pnp.ids”: No such file or directory (unity-settings-daemon:3287): GLib-GIO-CRITICAL **: 09:13:15.145: g_dbus_proxy_call_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed here the last log item shows what happens, when I wist to refresh the key binding in the custom section. Everytime I try to set a keybinding this gets printed. Also the line "(unity-settings-daemon:3287): media-keys-plugin-WARNING **: 09:12:51.552: Grab failed for some keys, another application may already have access the them." is interesting, ... is this because I started "unity-settings-daemon --replace" manually, and therfore now the original is running and my new command is also running? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load Status in unity-settings-daemon package in Ubuntu: Confirmed 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/unity-settings-daemon/+bug/1755106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755106] Re: Bug 175510 custom-keybindings fails to load
In my case, I have the following result: prohlep@pc56:~$ G_MESSAGES_DEBUG=all unity-settings-daemon --replace & [1] 2773 prohlep@pc56:~$ (unity-settings-daemon:2773): Gtk-WARNING **: 09:06:24.599: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory ** (unity-settings-daemon:2773): WARNING **: 09:06:24.746: Failed to load PNP ids: Failed to open file “/usr/share/hwdata/pnp.ids”: No such file or directory ** (unity-settings-daemon:2773): WARNING **: 09:06:24.849: Failed to load PNP ids: Failed to open file “/usr/share/hwdata/pnp.ids”: No such file or directory ** (unity-settings-daemon:2773): WARNING **: 09:06:24.849: Failed to load PNP ids: Failed to open file “/usr/share/hwdata/pnp.ids”: No such file or directory (unity-settings-daemon:2773): media-keys-plugin-WARNING **: 09:06:24.938: Grab failed for some keys, another application may already have access the them. ** (unity-settings-daemon:2773): WARNING **: 09:06:24.942: Failed to load PNP ids: Failed to open file “/usr/share/hwdata/pnp.ids”: No such file or directory (unity-settings-daemon:2773): Gtk-WARNING **: 09:06:24.960: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory (usd-locate-pointer:2785): Gtk-WARNING **: 09:06:24.991: Theme parsing error: gtk-main.css:73:38: Failed to import: Error opening file /usr/share/themes/Radiance/gtk-3.20/apps/gnome-builder.css: No such file or directory -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load Status in unity-settings-daemon package in Ubuntu: Confirmed 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/unity-settings-daemon/+bug/1755106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
Exactly the same symptoms with SHIFT instead of ALT. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load Status in unity-settings-daemon package in Ubuntu: Confirmed 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/unity-settings-daemon/+bug/1755106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
https://pastebin.ubuntu.com/p/nrtyQZMPdB/
In my case the primary key is the ALT, actually the left alt.
As far as I know, no usage collision of alt-ctrl-g, alt-ctrl-backspaces,
...
I do not use any other setting manager. The problem is ther if I do it
'by hand' in Unity control center. However normally I set up almost
everything with script, here is the shortcut setting part:
CK='/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings'
DCONFWRITE='dconf write '
DCONFWRITE+="${CK}"
${DCONFWRITE}/custom0/name "'unset'"
${DCONFWRITE}/custom0/command "'unset'"
${DCONFWRITE}/custom0/binding "'unset'"
${DCONFWRITE}/custom0/name "'gnome-terminal --geometry=80x99-0+0'"
${DCONFWRITE}/custom0/command "'gnome-terminal --geometry=80x99-0+0'"
${DCONFWRITE}/custom0/binding "'g'"
${DCONFWRITE}/custom1/name "'unset'"
${DCONFWRITE}/custom1/command "'unset'"
${DCONFWRITE}/custom1/binding "'unset'"
${DCONFWRITE}/custom1/name "'gnome-session-quit --power-off'"
${DCONFWRITE}/custom1/command "'gnome-session-quit --power-off'"
${DCONFWRITE}/custom1/binding "'BackSpace'"
${DCONFWRITE} "['${CK}/custom0/','${CK}/custom1/']"
unset DCONFWRITE
unset CK
However, the problem is still there, if I do it by hand, and during the
debug command the setting is recorded only and it comes to alive after a
logout/login cycle.
I am ready to make further experiments, no comes the CTRL+SHIFT instead
of CTRL+ALT, how you have just suggested, ... many thanks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1755106
Title:
/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/
fails to load
Status in unity-settings-daemon package in Ubuntu:
Confirmed
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/unity-settings-daemon/+bug/1755106/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
First of all, many thanks for your help.
https://pastebin.ubuntu.com/p/nrtyQZMPdB/plain/
Firs I disabled the keystrokes at the two items in question, then I
removed the items as well.
Then I re-entered the two items ('gnome-session-quit --power-off' and
'gnome-terminal --geometry=80x99-0+0') and then configured keystrokes
for them ('BackSpace' and 'g').
The result is, that whenever I do this, the two keystrokes does NOT come
back until I logout and login again.
Later I discovered, that as soon as I commit the command "unity-
settings-daemon -r --debug", the keystrokes in question disappear.
Even later I discovered, that not only the custom bingins go away with
committing the debug command, but the redefined normal bindings: I like
the web browser (launchers / launc web browser) at 'f',
but it is not there anymore if I start the debug command.
An interesting side-effect is, that when the problem during debug
command arise, then the decoration of the Unity control center changes
from my usual Radiance back to the default Ambiance.
After logging out and back, the decoration and all the redefined or
custom bindings come back.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1755106
Title:
/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/
fails to load
Status in unity-settings-daemon package in Ubuntu:
Confirmed
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/unity-settings-daemon/+bug/1755106/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755106] Re: Bug 1755106
The problem is still there, and sometimes I need two reboots in order to get rid of the situation. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load Status in unity-settings-daemon package in Ubuntu: Confirmed 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/unity-settings-daemon/+bug/1755106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755106] Re: Bug 1755106
Will anyone ever tell me what to look for when the problem occurs? I did a fresh reinstall of the whole 18.04 system from scratch, but the problem is still there. I could provide more information if someone tells me what to look for. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load Status in unity-settings-daemon package in Ubuntu: Confirmed 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/unity-settings-daemon/+bug/1755106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755106] /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/
The problem is much more frequent in the last few days. What shall I test or record if this problem occures next? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load Status in unity-settings-daemon package in Ubuntu: Confirmed 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/unity-settings-daemon/+bug/1755106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
The problem is still there, twice a week approx, today 3 out of the 4 reboots were erratic wrt custom keybindings. Could anybody tell me, what kind of data and information should I collect, when next time the error occurs? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load Status in unity-settings-daemon package in Ubuntu: Confirmed 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/unity-settings-daemon/+bug/1755106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
The problem is still there. Can someone tell me what kind of test should I do in case of Unity? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load Status in unity-settings-daemon package in Ubuntu: Confirmed 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/unity-settings-daemon/+bug/1755106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
> if you are using unity then the issue is rather in unity-settings-daemon > and the gsd command I suggested are wrong OK, and can you tell me what kind of test should I do in case of Unity? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load Status in unity-settings-daemon package in Ubuntu: Confirmed 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/unity-settings-daemon/+bug/1755106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
Today I got similar result:
$ /usr/lib/gnome-settings-daemon/gsd-media-keys
(gsd-media-keys:2834): GLib-GIO-WARNING **: 23:34:21.130: Dropping
signal AcceleratorActivated of type (uuu) since the type from the
expected interface is (ua{sv})
(gsd-media-keys:2834): GLib-GIO-WARNING **: 23:34:37.681: Dropping
signal AcceleratorActivated of type (uuu) since the type from the
expected interface is (ua{sv})
(gsd-media-keys:2834): GLib-GIO-WARNING **: 23:34:44.777: Dropping
signal AcceleratorActivated of type (uuu) since the type from the
expected interface is (ua{sv})
DO I EXECUTE THE RIGHT OR SUITABLE TEST?
Tell me what to test next time?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1755106
Title:
/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/
fails to load
Status in gnome-settings-daemon package in Ubuntu:
Confirmed
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/gnome-settings-daemon/+bug/1755106/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
OK, I forget to tell, that I use Unity! and my custom settings are: $ 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' $ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load Status in gnome-settings-daemon package in Ubuntu: Confirmed 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/gnome-settings-daemon/+bug/1755106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
Today the problem occurred again, so I could test /usr/lib/gnome-
settings-daemon/gsd-media-keys. Do I understand correctly that in a
terminal running bash inside, I simply give this /usr/lib/gnome-
settings-daemon/gsd-media-keys fully qualified path as a command?
The result is that it does not return to bash prompt, and initially
gives no kind of messages. However, when I try any of the custom
keystrokes, or any of the usual but overridden keystrokes, then I get
the followings:
$ /usr/lib/gnome-settings-daemon/gsd-media-keys
(gsd-media-keys:2459): GLib-GIO-WARNING **: 22:32:43.149: Dropping
signal AcceleratorActivated of type (uuu) since the type from the
expected interface is (ua{sv})
(gsd-media-keys:2459): GLib-GIO-WARNING **: 22:32:57.476: Dropping
signal AcceleratorActivated of type (uuu) since the type from the
expected interface is (ua{sv})
(gsd-media-keys:2459): GLib-GIO-WARNING **: 22:33:01.756: Dropping
signal AcceleratorActivated of type (uuu) since the type from the
expected interface is (ua{sv})
(gsd-media-keys:2459): GLib-GIO-WARNING **: 22:33:02.460: Dropping
signal AcceleratorActivated of type (uuu) since the type from the
expected interface is (ua{sv})
(gsd-media-keys:2459): GLib-GIO-WARNING **: 22:33:04.076: Dropping
signal AcceleratorActivated of type (uuu) since the type from the
expected interface is (ua{sv})
(gsd-media-keys:2459): GLib-GIO-WARNING **: 22:33:04.500: Dropping
signal AcceleratorActivated of type (uuu) since the type from the
expected interface is (ua{sv})
(gsd-media-keys:2459): GLib-GIO-WARNING **: 22:33:04.804: Dropping
signal AcceleratorActivated of type (uuu) since the type from the
expected interface is (ua{sv})
(gsd-media-keys:2459): GLib-GIO-WARNING **: 22:33:05.675: Dropping
signal AcceleratorActivated of type (uuu) since the type from the
expected interface is (ua{sv})
(gsd-media-keys:2459): GLib-GIO-WARNING **: 22:37:17.075: Dropping
signal AcceleratorActivated of type (uuu) since the type from the
expected interface is (ua{sv})
(gsd-media-keys:2459): GLib-GIO-WARNING **: 22:37:26.746: Dropping
signal AcceleratorActivated of type (uuu) since the type from the
expected interface is (ua{sv})
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1755106
Title:
/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/
fails to load
Status in gnome-settings-daemon package in Ubuntu:
Confirmed
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/gnome-settings-daemon/+bug/1755106/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
In the last 9 days, the problem became less common, but today it has started again. The situation remained the same,as I described at earlier reports. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load Status in gnome-settings-daemon package in Ubuntu: Confirmed 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/gnome-settings-daemon/+bug/1755106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758373] Re: bison -Wconversion warning
HELP! I adjusted at the beginning of the bug report, that this is NOT a
gnome-settings-daemon bug, BUT a bison bug, ... there was a possibility
TO CHANGE THE PACKAGE WHAT IS AFFECTED, I do not know why it changed
back to gnome-settings-daemon?
Please, somebody who has enough right for this, change it to bison.
Thanks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1758373
Title:
bison -Wconversion warning
Status in gnome-settings-daemon package in Ubuntu:
New
Bug description:
I wish to use the -Wconversion at gcc (the warnings are instructive
for me, and they already taught me a lot), but then:
$ bash bison_conversion_bug.sh
y.tab.c: In function ‘yyparse’:
y.tab.c:1023:12: warning: conversion to ‘yytype_int16 {aka short int}’ from
‘int’ may alter its value [-Wconversion]
*yyssp = yystate;
^~~
y.tab.c:1028:25: warning: conversion to ‘long unsigned int’ from ‘long int’
may change the sign of the result [-Wsign-conversion]
YYSIZE_T yysize = yyssp - yyss + 1;
^
$
I get this problem even in an almost empty grammar and minimal C
source frame for it, see the attachment: an example for minimal
grammar and minimal C frame ALREADY providing the error.
This is the error in case of my Ubuntu 18.04 ( bison --version =
3.0.4, gcc --version = (Ubuntu 7.3.0-12ubuntu1) 7.3.0).
I could try Debian jessie, where I get exactly the same error at
exactly the same line position ( bison --version = 3.0.2, gcc
--version = (Debian 4.9.2-10+deb8u1) 4.9.2).
MY SUGGESTION: IF the bison developers are sure, that "yystate" and
"yyssp - yyss + 1" will always fit into "short int" or "long unsigned
int", THEN an explicit casting could be a solution. HOWEVER in case
of "yystate" it would be much more relaxing to make a decision whether
it should be an "int" or "short int".
The compilation commands are:
CCOPTS=''
CCOPTS+=' -std=c11'
CCOPTS+=' -Og -g'
CCOPTS+=' -Wabi'
CCOPTS+=' -Wfatal-errors'
CCOPTS+=' -Wall'
CCOPTS+=' -Wextra'
CCOPTS+=' -Wreturn-type'
CCOPTS+=' -Wconversion' ### bison has 2 conversion errors
CCOPTS+=' -fexceptions'
CCOPTS+=' -pedantic-errors'
CCOPTS+=' -fmax-errors=1'
rm -f y.output y.tab.h y.tab.c y.tab.o
bison --yacc --verbose -d "EXAMPLE_GIVEN_IN_THE_ATTACHMENT.y"
gcc -c ${CCOPTS} y.tab.c
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1758373/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758373] [NEW] bison -Wconversion warning
Public bug reported:
I wish to use the -Wconversion at gcc (the warnings are instructive for
me, and they already taught me a lot), but then:
$ bash bison_conversion_bug.sh
y.tab.c: In function ‘yyparse’:
y.tab.c:1023:12: warning: conversion to ‘yytype_int16 {aka short int}’ from
‘int’ may alter its value [-Wconversion]
*yyssp = yystate;
^~~
y.tab.c:1028:25: warning: conversion to ‘long unsigned int’ from ‘long int’ may
change the sign of the result [-Wsign-conversion]
YYSIZE_T yysize = yyssp - yyss + 1;
^
$
I get this problem even in an almost empty grammar and minimal C source
frame for it, see the attachment: an example for minimal grammar and
minimal C frame ALREADY providing the error.
This is the error in case of my Ubuntu 18.04 ( bison --version = 3.0.4,
gcc --version = (Ubuntu 7.3.0-12ubuntu1) 7.3.0).
I could try Debian jessie, where I get exactly the same error at exactly
the same line position ( bison --version = 3.0.2, gcc --version =
(Debian 4.9.2-10+deb8u1) 4.9.2).
MY SUGGESTION: IF the bison developers are sure, that "yystate" and
"yyssp - yyss + 1" will always fit into "short int" or "long unsigned
int", THEN an explicit casting could be a solution. HOWEVER in case of
"yystate" it would be much more relaxing to make a decision whether it
should be an "int" or "short int".
The compilation commands are:
CCOPTS=''
CCOPTS+=' -std=c11'
CCOPTS+=' -Og -g'
CCOPTS+=' -Wabi'
CCOPTS+=' -Wfatal-errors'
CCOPTS+=' -Wall'
CCOPTS+=' -Wextra'
CCOPTS+=' -Wreturn-type'
CCOPTS+=' -Wconversion' ### bison has 2 conversion errors
CCOPTS+=' -fexceptions'
CCOPTS+=' -pedantic-errors'
CCOPTS+=' -fmax-errors=1'
rm -f y.output y.tab.h y.tab.c y.tab.o
bison --yacc --verbose -d "EXAMPLE_GIVEN_IN_THE_ATTACHMENT.y"
gcc -c ${CCOPTS} y.tab.c
** Affects: gnome-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "minimal grammar with minimal C frame"
https://bugs.launchpad.net/bugs/1758373/+attachment/5088332/+files/bison_conversion_bug.y
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1758373
Title:
bison -Wconversion warning
Status in gnome-settings-daemon package in Ubuntu:
New
Bug description:
I wish to use the -Wconversion at gcc (the warnings are instructive
for me, and they already taught me a lot), but then:
$ bash bison_conversion_bug.sh
y.tab.c: In function ‘yyparse’:
y.tab.c:1023:12: warning: conversion to ‘yytype_int16 {aka short int}’ from
‘int’ may alter its value [-Wconversion]
*yyssp = yystate;
^~~
y.tab.c:1028:25: warning: conversion to ‘long unsigned int’ from ‘long int’
may change the sign of the result [-Wsign-conversion]
YYSIZE_T yysize = yyssp - yyss + 1;
^
$
I get this problem even in an almost empty grammar and minimal C
source frame for it, see the attachment: an example for minimal
grammar and minimal C frame ALREADY providing the error.
This is the error in case of my Ubuntu 18.04 ( bison --version =
3.0.4, gcc --version = (Ubuntu 7.3.0-12ubuntu1) 7.3.0).
I could try Debian jessie, where I get exactly the same error at
exactly the same line position ( bison --version = 3.0.2, gcc
--version = (Debian 4.9.2-10+deb8u1) 4.9.2).
MY SUGGESTION: IF the bison developers are sure, that "yystate" and
"yyssp - yyss + 1" will always fit into "short int" or "long unsigned
int", THEN an explicit casting could be a solution. HOWEVER in case
of "yystate" it would be much more relaxing to make a decision whether
it should be an "int" or "short int".
The compilation commands are:
CCOPTS=''
CCOPTS+=' -std=c11'
CCOPTS+=' -Og -g'
CCOPTS+=' -Wabi'
CCOPTS+=' -Wfatal-errors'
CCOPTS+=' -Wall'
CCOPTS+=' -Wextra'
CCOPTS+=' -Wreturn-type'
CCOPTS+=' -Wconversion' ### bison has 2 conversion errors
CCOPTS+=' -fexceptions'
CCOPTS+=' -pedantic-errors'
CCOPTS+=' -fmax-errors=1'
rm -f y.output y.tab.h y.tab.c y.tab.o
bison --yacc --verbose -d "EXAMPLE_GIVEN_IN_THE_ATTACHMENT.y"
gcc -c ${CCOPTS} y.tab.c
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1758373/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
I wish to provide better diagnostic information, but I do not know what to submit in this particular situation. I am also ready to install some sort of Watchdog daemon, which can better detect what is going on in this kind of situation. I can imagine a say a small shell script or something alike as well. Right now I have again a boot resulting no custom keybindings while all the other keybindings work. Again: "ps acuwx | fgrep gsd" is empty, and "journalctl | grep gsd" has no new entry since "Mar 12 08:47:48". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load Status in gnome-settings-daemon package in Ubuntu: Confirmed 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/gnome-settings-daemon/+bug/1755106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1750846] Re: several g-s-d services are timing out when booting a live session
Is it possible, that my issue https://bugs.launchpad.net/bugs/1755106 has some connection with this issue, see the journalctl | grep -i key | grep -i failed > journalctl_key_failed.txt attachment there: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/1755106/+attachment/5082123/+files/journalctl_key_failed.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1750846 Title: several g-s-d services are timing out when booting a live session Status in gnome-settings-daemon package in Ubuntu: New Status in gnome-settings-daemon source package in Bionic: New Bug description: The following g-s-d services are timing out when booting a live session: gsd-media-keys gsd-color gsd-wacom gsd-power One impact at least is that the shortcut to launch a terminal doesn't work From the journal: [ 82.368253] ubuntu gsd-media-keys[1865]: Failed to grab accelerators: Timeout was reached (24) [ 108.828263] ubuntu gsd-color[1863]: failed to get screens: Timeout was reached [ 108.836334] ubuntu gsd-wacom[1836]: Failed to construct RR screen: Timeout was reached [ 108.837764] ubuntu gsd-power[1823]: Could not create GnomeRRScreen: Timeout was reached [ 245.337228] ubuntu gsd-media-keys[1865]: Could not find accelerator for accel id 175 ^_ this last line is displayed when Ctrl+Alt+T is pressed to open a terminal ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CasperVersion: 1.388 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 21 15:20:00 2018 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180221) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1750846/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
[continuing the previous comment] The the output of "ps acuwx | fgrep gsd" is still empty. Should I see any process containing the substring "gsd"? Is it possible, that my issue has some connection with the followin issue: https://bugs.launchpad.net/bugs/1750846 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load Status in gnome-settings-daemon package in Ubuntu: Incomplete 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/gnome-settings-daemon/+bug/1755106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
Today I had again a possibility to check the issue. Tell me please, that what kind of information, what command outputs should I attach, when I face myself to the issue in question? Output of "dmesg | grep -i gsd" is empty. Outout of "journalctl | grep -i gsd" has no new items in the last 4 days. However I found interesting lines in journalctl, hence I try to add the result of "journalctl | grep -i key | grep -i failed > journalctl_key_failed.txt" as an attachment. ** Attachment added: "journalctl | grep -i key | grep -i failed > journalctl_key_failed.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1755106/+attachment/5082123/+files/journalctl_key_failed.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load Status in gnome-settings-daemon package in Ubuntu: Incomplete 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/gnome-settings-daemon/+bug/1755106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1756387] [NEW] Whish: a Unity like desktop bar in Gnome, or the default desktop manager of Ubuntu
Public bug reported: I wish a Unity like desktop bar in Gnome, or the default desktop manager of Ubuntu. More precisely: a desktop bar which is capable to steal, to take away the menu bars of the application windows, and show the menu bar of that application window which is in focus currently. I wish this in the default desktop manager, what is currently Gnome if I know correctly. The only reason why I still use the Unity is this feature what I find very comfortable. Can I configure the Gnome desktop this way right now, or it needs an amount of programming, and a better knowledge of the gnome system? If my wish is not only a simple configuration or a bit more only, and if the solution does not need far too deep knowledge of the Gnome desktop programming, then I am ready to program it, if someone gives me the references to concise reading materials enough for this work (I use and program computers since 1972 on regular daily base, and a I am fluent in unix/linux tools, including C/C++ what I teach regularly at the university). [[it was suggested me at the AskUbuntu, that this kind of wishes fits here to the bug reports better, and somebody with enough privileges will mark this as a "wish list" item]] ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1756387 Title: Whish: a Unity like desktop bar in Gnome, or the default desktop manager of Ubuntu Status in gnome-settings-daemon package in Ubuntu: New Bug description: I wish a Unity like desktop bar in Gnome, or the default desktop manager of Ubuntu. More precisely: a desktop bar which is capable to steal, to take away the menu bars of the application windows, and show the menu bar of that application window which is in focus currently. I wish this in the default desktop manager, what is currently Gnome if I know correctly. The only reason why I still use the Unity is this feature what I find very comfortable. Can I configure the Gnome desktop this way right now, or it needs an amount of programming, and a better knowledge of the gnome system? If my wish is not only a simple configuration or a bit more only, and if the solution does not need far too deep knowledge of the Gnome desktop programming, then I am ready to program it, if someone gives me the references to concise reading materials enough for this work (I use and program computers since 1972 on regular daily base, and a I am fluent in unix/linux tools, including C/C++ what I teach regularly at the university). [[it was suggested me at the AskUbuntu, that this kind of wishes fits here to the bug reports better, and somebody with enough privileges will mark this as a "wish list" item]] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756387/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
No I had a possibility to check the situation for the question: Do you have an active "gsd-media-keys" process when getting the issue? I have the /usr/lib/gnome-settings-daemon/gsd-media-keys ELV binary, but I do NOT see in the linting of "ps auxw", and even the output of "ps acuwx | fgrep gsd" is empty. Interestingly the output of "journalctl | grep gsd-media-keys" remained exactly the same, as 3 days before, no new entry. But none of the two user defined shortcuts work, while all the usual system default shortcuts work. I welcome further test suggestions in order to be prepared if next time the issue appears. One thing is interesting, that just after updating to 18.04, the frequency of the issue became high for a few days, and as soon as I submitted this issue, I had to wait 3 days (4 booting) in order to get the issue again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load Status in gnome-settings-daemon package in Ubuntu: Incomplete 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/gnome-settings-daemon/+bug/1755106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load
"Do other keybinding work?" --- YES they do work, only the "custom shortcuts" are affected, but ALL of them (I have only 2 custom shortcuts). "Does journalctl contains any error about gsd-media-keys?" journalctl | grep gsd-media-keysgives the following result (I upgraded to 18.04 one days before the first entry, Mar 10): Mar 10 19:30:35 pc56 dbus-daemon[884]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus- org.freedesktop.hostname1.service' requested by ':1.116' (uid=125 pid=8253 comm="/usr/lib/gnome-settings-daemon/gsd-media-keys " label="unconfined") Mar 10 19:58:38 pc56 dbus-daemon[883]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus- org.freedesktop.hostname1.service' requested by ':1.127' (uid=125 pid=5326 comm="/usr/lib/gnome-settings-daemon/gsd-media-keys " label="unconfined") Mar 10 19:59:07 pc56 gsd-media-keys[5326]: Error releasing name org.gnome.SettingsDaemon.MediaKeys: The connection is closed Mar 11 14:39:51 pc56 dbus-daemon[903]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus- org.freedesktop.hostname1.service' requested by ':1.115' (uid=125 pid=3011 comm="/usr/lib/gnome-settings-daemon/gsd-media-keys " label="unconfined") Mar 12 08:47:22 pc56 dbus-daemon[884]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus- org.freedesktop.hostname1.service' requested by ':1.121' (uid=125 pid=5137 comm="/usr/lib/gnome-settings-daemon/gsd-media-keys " label="unconfined") "Do you have an active "gsd-media-keys" process when getting the issue?" I had no possibility to check it, because I had only two cold boots since the last "Mar 12 08:47:22" occurence of the problem, and the both vere error free. But I do not find the process in question, do I test it correctly? : ps auxw | grep gsd-media-keys -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1755106 Title: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load Status in gnome-settings-daemon package in Ubuntu: Incomplete 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/gnome-settings-daemon/+bug/1755106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1751005] Re: libreoffice cannot open a document not within $HOME
If the bug is that terrorists abruptly divert aircrafts into high buildings, then the total disabling the whole air traffic IS NOT A BUGFIX, but it is a TEMPORARY WORK AROUND only! The real bug fix is when you reopen the public air traffic with a better safety configuration! To disable the apparmor is a temporary work around only. Since the foreign office documents are harmful, and hence it is a valuable gift, that the apparmor is suitable to protect say the local backup subtrees. It is in fact a conceptual bug to assume, that peope work in their home. Professionals, who were not brought up in the "My Documents", "My Photos" and "Downloads" world, do work elsewhere on regular base. Since the home tree became polluted by self invited and regularly changing system configuration data, typically not for tampering by the user. Remember please the happy 80's years, when the home containd exclusively only that kind of configuratkon files, which were edited only by the user itself. And as such, these user configuration files also belonged to the fruits of the users's onwn personal work. But nowadays, the professional approach is NOT to work in the home tree. ((I personally use 4 additional physical drives: /work and its local backup /, and /xtra and its local backup /ytra. Hence I wish to access by LibreOffice the regular /work and occassionally /xtra, and I wish to protect their local backups: / and /ytra .)) Hence I suggest NOT TO CONSIDER THIS BUG "Fix Released", since disabling of the protection IS NOT A BUGFIX. The bug is still there! There should be a user configurable list of user subtree roots. And there should be a HUGE WARNING in the LibreOffice error message, that where can the user find that configurable list of user subtree roots. Google the net please, and recognise please, how wide spread this bug is, and ho many discussions DO not recognies, that the problem is not directly with the LibreOffice itself, but only with the Windows-style missleading error message and bad access configuration. This bug is suitable to deter or discourage the users from LibreOffice and hence from Linux systems. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1751005 Title: libreoffice cannot open a document not within $HOME Status in libreoffice package in Ubuntu: Fix Released Bug description: Starting with today's update to LibreOffice 5.4.5.1 40m0(Build:1), files not within the user $HOME directory cannot be opened. This has nothing to do with ownership or permissions - the target document is owned by the user with full permissions. Moving the file to ~/Desktop allows it to be opened normally. Error message in popup window: Access to /home2/mico/documents/personal/2018 lists.ods was denied. Error message when launched from terminal: $: localc "2018 lists.ods" javaldx: Could not find a Java Runtime Environment! Please ensure that a JVM and the package libreoffice-java-common is installed. If it is already installed then try removing ~/.libreoffice/3/user/config/javasettings_Linux_*.xml Warning: failed to read path from javaldx The file mentioned in the error message does not exist. I removed the corresponding file under ~/.libreoffice/4/ but that makes no difference. This but started in Ubuntu 18.04 (alpha) around Feb. 15, and with today's update (Feb. 22) it appeared in Ubuntu 17.10. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice-core 1:5.4.5-0ubuntu0.17.10.1 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 22 09:35:49 2018 InstallationDate: Installed on 2018-01-27 (25 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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 DistroRelease:
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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-evdev
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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.
Re: [Desktop-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10
Ctrl-Alt-T doesn't open Terminal in russian layout. However, with m17n workaround works OK. Is there a latin letter T in the russian layout? I mean a real latin letter T, and not only a correspondig cyrillic letter. This is the REAL question. While it is not comfortable, but it is according to the standards, that if there is no FOO in a layout, then there is neither Ctrl-Alt-FOO in the same layout. If terminal in russian begins with the CYRILLIC letter say X, then you should open your terminal with Ctrl-Alt-X. I guess that m17n workaround is a tool to break the standards. I understand you, I also suffer from the fact, that I am neither a native english speaker. But there is no equal opportunity in this partikcular World. We have no equal chances. We have to afford more efforts to achieve the same result. Peter. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10 Status in IBus: New Status in Indicator keyboard: Fix Released Status in Mutter: New Status in The OpenOffice.org Suite: New Status in Unity: Invalid Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Fix Released Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters-keyboard-hotkeys-windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1226962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10
There is a letter T in the Greek layout. Also, terminal in Greek translates to τερματικό, both words start with a letter T. So, there is no excuse for the Ctrl-Alt-T Unity shortcut not working in Greek layout. Greek T is NOT identical to Latin T, they are DISTINCT letters, which only correspond to each other. This is not only a valid excuse, but otherwise we were not able to write a pure greek text containing properly shaped greek T letters. In other words, the unicode code point of greek T and latin T are luckily different. Even τερματικό is not identical to termatiko, there is only a natural correspondance there. Hence the correct solution is if Ctrl-Alt-τ works instead of Ctrl-Alt-t. While it is just a minor amount of difference in terms of the visual shape of the letters, but an essential difference in terms of unicode code points of them. I have no greek keyboard experince, but I am reluctant to think that your greek layout produces latin-t instead of greek-τ. Hence Ctrl-Alt-τ should work instead of Ctrl-Alt-t. I think that all of you have implicitely the following suggestion: the keyboardlayout should be Alt, Ctrl and Ctrl-Alt dependent and even if the plain state produces russian or greek letters, the Alt, Ctrl and Ctrl-Alt layers should be able to remain in US-English layout. However this would need the redesign of the keyboarlyout config tools, in order to make the users able to specify the 4 different layers: the plain, the Alt, the Ctrl and the Ctrl-Alt layers INDEPENDENTLY from each other. Peter. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10 Status in IBus: New Status in Indicator keyboard: Fix Released Status in Mutter: New Status in The OpenOffice.org Suite: New Status in Unity: Invalid Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Fix Released Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters-keyboard-hotkeys-windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1226962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10
What matters is that the *physical* keyboard shortcuts like Ctrl-Alt-T or Ctrl-C, Ctrl-V should just work no matter what the current layout is. That is, what you say, that the four layers, i.e. the plain, the Alt, the Ctrl and the Ctrl-Alt layers shuld be INDEPENDENT-ly configurable, and so we could keep the Ctrl-Alt layer in US-English layout. This is the implicite suggestion what I was mentioning at the end of my previous comment. If a layer is kept in the US-English layout, then we call it as that particular layer is in *physical* keyboard layout. Peter. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10 Status in IBus: New Status in Indicator keyboard: Fix Released Status in Mutter: New Status in The OpenOffice.org Suite: New Status in Unity: Invalid Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Fix Released Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters-keyboard-hotkeys-windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1226962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1226962]
Dear Norbert! IMHO below. In present time many problems come from GNOME fast destruction and simpility/stupidity behavior. GNOME reduces its functionality very fast, and this changes are not tested for all regressions and bugs, this changes are not discussed with gnome-users. So many problems are common for all distros - i.e. Ubuntu 13.10, OpenSuSe 12.3, Fedora 20, Mageia 4 and others will use the same buggy and untested GNOME 3.x. As the most conservative solution we can use CentOS 6.5 (with GNOME 2.28 !! ) or Gentoo (with GNOME 2.32), but this solution is not universal for all users. So If you choose Ubuntu, I recommend to use Ubuntu LTS ... Thanks for your detailed explanation, now I understand better why it is lucky, that my daugther (physicist and chemist) uses LTS. So I will leave her LTS alone until the next LTS. Best wishes, Peter. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10 Status in IBus: New Status in Indicator keyboard: Fix Released Status in Mutter: New Status in The OpenOffice.org Suite: New Status in Unity: Invalid Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Fix Released Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters-keyboard-hotkeys-windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1226962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1113364] [NEW] keyboard layout fails to be different for individual windows
Public bug reported: My case is a close variant of the following two bugs closely related to each other: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/885730 https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/622965 My usual setting in system settings ... / all settings / Keybord layout is as follows: allow different layout for individual windows (this allows me to fluently work in different languages in parallel) new windows use the default layout (this enables me to concentrate on the new window instead of the last one) Bug #885730 deterministically reproducable in my case: open firefox, switch to hungarian but the indicator remains ENG. Then switch back to ENG, and again to HUN, and starting from this second time not only the keybord input, but also the indicator reflects correctly the HUN state. This problem never happens working in terminal window. I do not use non-ENG in other applications, only in terminal or in firefox. Bug #885730 has now 4 substatuses: 2 fix release dated 2012-03-16, 1 invalid and 1 Won't Fix, this latter I hope is not true for the current and future releases. My case is essentially different from this bug: my case looks deterministic and restricted to the first switches. After the third switch indicator shows the state correctly. However, in normal work, there is never a second and third switch, hence this bug causes essentially ALWAYS a missleading language indication. Bug #622965 dated 2010-08-23 is even older, and my case is essentially different again, that in contrary to the old deterministically reproducable bug, right now, I can not reproduce the bug during this bug submitting period. While this old bug affects me, whenever I work in normal: usually I have a single terminal window, or rarely a single firefox window, and when I want to open the other kind of window, then the bug is there, but for later changes and new window, the bug is usually not there. The reason why I can not reproduce the bug during bug report is, that I can not close the firefox dufing the preparation of the bug report. What if the problem in my case is in the cooperation of firefox and the graphical event handling frame system? I use now 12.10 with all the possible updates, including proposals. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu19 ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Sat Feb 2 11:04:00 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2012-10-19 (105 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu4.2 deja-dup24.0-0ubuntu2 gnome-control-center-signon 0.0.18-0ubuntu1.1 indicator-datetime 12.10.2-0ubuntu3.1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1113364 Title: keyboard layout fails to be different for individual windows Status in “gnome-control-center” package in Ubuntu: New Bug description: My case is a close variant of the following two bugs closely related to each other: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/885730 https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/622965 My usual setting in system settings ... / all settings / Keybord layout is as follows: allow different layout for individual windows (this allows me to fluently work in different languages in parallel) new windows use the default layout (this enables me to concentrate on the new window instead of the last one) Bug #885730 deterministically reproducable in my case: open firefox, switch to hungarian but the indicator remains ENG. Then switch back to ENG, and again to HUN, and starting from this second time not only the keybord input, but also the indicator reflects correctly the HUN state. This problem never happens working in terminal window. I do not use non-ENG in other applications, only in terminal or in firefox. Bug #885730 has now 4 substatuses: 2 fix release dated 2012-03-16, 1 invalid and 1 Won't Fix, this latter I hope is not true for the current and future releases. My case is essentially different from this bug: my case looks deterministic and restricted to
