[Bug 1722353] Re: Screen blanking and/or screen lock crashes gnome-shell user session on wayland - Ubuntu 17.10 beta
I did some experimenting. The wayland gnome-shell crash and monitor power-saving issue seems to be limited to a hdmi connection, and has something to do with the monitor searching for a signal on other inputs after it has been blanked. I dug out an old d-sub vga cable and connected the monitor to the graphics card with that. Timed blanking of the screen or locking the desktop manually did not cause a gnome-shell crash on wayland when using the d-sub cable. Monitor power saving worked as expected. The next thing I tried was reconnecting the hdmi cable and locking the monitor to the hdmi input and turning off the automatic signal selection. With the monitor configured that way, both timed blanking and manual locking of the desktop worked as expected. The monitor successfully went to sleep and the session resumed after user input. I also tried plugging in a tv using hdmi. That didn't produce any session crashes. However the tv makes no attempt to blank itself or enter a power-saving mode; it just stays on with a "No Signal" notice. I also connected an old 1680x1050 monitor using a dvi cable. That simply refused to boot past the Ubuntu splash screen. However the same monitor works perfectly when booting into the 17.10 beta live-cd, but the live-cd runs on a xorg session and not wayland. Next I connected that same old monitor using dvi together with the newer dell over hdmi simultaneously, and booted successfully into a wayland session. (That this combination actually worked and booted barely makes sense. Also the primary monitor was changed between login prompt and the desktop being loaded, but whatever...) With multiple monitors connected timed blanking or desktop locking did not crash the gnome-shell session, but they still did not blank properly. After blanking both screens, they were immediately both turned on again with a only a black background and the mouse cursor on the primary monitor. And that is how they stayed, with backlights both still on. No blanking or power-saving was done thereafter. Mouse or keyboard input would return the lock-screen to the displays and unlocking with a password would successfully return the active user session. Lastly, after again locking the dell monitor to the hdmi input and turning off the automatic signal selection, both monitors would successfully enter power-saving modes and the user session could be resumed after unlocking with a password. TL;DR = It seems that the monitor disconnecting itself from the blanked/inactive hdmi input in order to search for an active vga input signal is what is triggering the gnome-shell crash and/or preventing the monitor from entering its power-saving mode. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1722353 Title: Screen blanking and/or screen lock crashes gnome-shell user session on wayland - Ubuntu 17.10 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1722353/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722353] Re: Screen blanking and/or screen lock crashes gnome-shell user session on wayland - Ubuntu 17.10 beta
Filed against Xorg due to selection limitations of apport. Mutter is the best guess of responsible application/package. ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1722353 Title: Screen blanking and/or screen lock crashes gnome-shell user session on wayland - Ubuntu 17.10 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1722353/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 118433] Re: mahjongg scoreboard: sometimes cannot enter name
The bug appears to be fixed in 12.04.1. Thanks for the reminder Thomas. We only upgraded our production machines after the LTS point release, so we hadn't noticed yet. Some nice improvements made as well! For the sake of completeness, here are how things stand at the moment: Ubuntu Precise 12.04.1 LTS (32 bit) Mahjongg 3.4.1 Packages: mahjongg (precise-updates) 1:3.4.1-0ubuntu2.1; gnome-games-data (precise-updates) 1:3.4.1-0ubuntu2.1; etc. I'm going to (try) mark the bug as completed and close it, as I was the one who resurrected it in Lucid. If anyone disagrees, feel free to change it. Thank you to everyone who worked on this. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/118433 Title: mahjongg scoreboard: sometimes cannot enter name To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-games/+bug/118433/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 118433] Re: mahjongg scoreboard: sometimes cannot enter name
Fixed in 12.04 ** Changed in: gnome-games (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/118433 Title: mahjongg scoreboard: sometimes cannot enter name To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-games/+bug/118433/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 978218] [NEW] Account editor renders outside borders of small screens
Public bug reported: On small displays (such as 1024x600 netbook) the account editor window is to big to fit inside the available space. Parts of the window are rendered off the screen and cannot be accesssed (particularly the Cancel and OK buttons). The window can also not be resized or moved to a position where these controls can be reached. The cause seems to be that the account editor window has no scrollbars whatsoever and therefore cannot resized small enough to fit within these small displays. There seems to be a regression here as in Evolution 2.28.3 on Ubuntu 10.04 Netbook Remix this was not an issue. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: evolution 3.2.3-0ubuntu5 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14 Uname: Linux 3.2.0-22-generic-pae i686 ApportVersion: 2.0-0ubuntu4 Architecture: i386 Date: Tue Apr 10 19:21:44 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120328) ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug apport-lpi i386 precise -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/978218 Title: Account editor renders outside borders of small screens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/978218/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 978218] Re: Account editor renders outside borders of small screens
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/978218 Title: Account editor renders outside borders of small screens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/978218/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 118433] Re: mahjongg scoreboard: sometimes cannot enter name
This is still easily reproducible in Lucid Lynx. If your high-score slots are clear, you should be able to reproduce it by the end of the second game, but it is sometimes pretty random. Though in my experience it has never produced the error on the first game. After the first game, change the default user name entry to something else. Most often (but not always) after the second game, it will enter the user's name into the high scores without any option to edit it. After the second game, the occurrence of the error is seemingly random, but I agree that it occurs about roughly 1/4 of the time. I have also used ctrl-h hints the whole way through the game to speed this up (can't play as fast as my wife), and it seems to make no difference. There is normally no terminal output at all. I did however randomly get the following a few times during a sequential set of games: ** (mahjongg:3033): WARNING **: Clock not started, cannot add seconds! This didn't seem to affect the game, scores, or the bug in any way though. If anything it seemed to produce the score entry bug less often while it was randomly producing the terminal error. I could try to run it with a debug flag, but have no idea if there is one. Anybody know of one? There is no mention of it in the help or man entries. This bug has been filed upstream since 2007-07-27: Bug 460966 - GamesScoresDialog shouldn't use an editable entry for retrieving the name (https://bugzilla.gnome.org/show_bug.cgi?id=460966) and recently refiled on 2010-06-07: Bug 620916 - sometimes cannot enter name into highscore - already computername filled in! (https://bugzilla.gnome.org/show_bug.cgi?id=620916) Not much activity on either of the bugs filed. ** Bug watch added: GNOME Bug Tracker #460966 https://bugzilla.gnome.org/show_bug.cgi?id=460966 ** Bug watch added: GNOME Bug Tracker #620916 https://bugzilla.gnome.org/show_bug.cgi?id=620916 -- mahjongg scoreboard: sometimes cannot enter name https://bugs.launchpad.net/bugs/118433 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 130152] Re: Mp3 profile is active in gnome-audio-profiles-properties but not choosable in sound-juicer, Rhythmbox and sound-recorder drop down list
I can confirm that this is still present in the karmic release.
GuyS (comment #10) has nailed this one. Someone please fix this.
Any entries made or modified with gnome-audio-profiles-properties, creates a
xml file entry for gconf
(~/.gconf/system/gstreamer/0.10/audio/profiles/profile_name/%gconf.xml).
The created gconf .xml file entries have syntax errors, which means that they
are not parsed/loaded correctly. This then results in them not being accessible
or usable by the client programs like rhythmbox.
Here is a line from a new profile I added:
{{{
entry name=active mtime=1258801687 type=bool value=true/
}}}
This is how it should read:
{{{
entry name=active mtime=1258473372 type=bool value=true
/entry
}}}
Specifically:/ should read /entry
Once the entries are corrected and a logout/login cycle completed, then
everything works as advertised.
Thanks,
David
Package: gnome-media
Section: gnome
Maintainer: Ubuntu Desktop Team ubuntu-desk...@lists.ubuntu.com
Architecture: amd64
Version: 2.28.1-0ubuntu1
--
Mp3 profile is active in gnome-audio-profiles-properties but not choosable in
sound-juicer, Rhythmbox and sound-recorder drop down list
https://bugs.launchpad.net/bugs/130152
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 425931] Re: Failure to Display Attached Images in Evolution
This bug is still present in Karmic Beta (Evolution 2.28.0) ** Changed in: evolution (Ubuntu) Status: Invalid = Incomplete -- Failure to Display Attached Images in Evolution https://bugs.launchpad.net/bugs/425931 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278112] Re: Screensaver doesn't start
I can confirm that the patch Thierry posted does allow the screensaver to start normally. The lock screen... checkbox in gnome-screensaver didn't cause any issues here. However, it still introduces the white screen when switching users with the User Switcher on the panel. Black screen on resume is no longer an issue. Here is a possible solution; I just don't know how to implement it: If a user wants to lock screen after switching users when using the User Switcher applet, why not return to the GDM login screen for the password? The click on System, Log out, Switch user approach to switching users seemed to work. So, that could be an easy workaround. If a user doesn't lock their session, then the white screen is not an issue when you return to that session. Sorry about the repeated misspelling of Unredirect Fullscreen Windows in the previous post! -- Screensaver doesn't start https://bugs.launchpad.net/bugs/278112 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278112] Re: Screensaver doesn't start
I may have found some problems with the proposed solution (i.e. unchecking Undirect fullscreen windows) when you have multiple users. Could someone please try these steps and confirm? Firstly, uncheck Undirect fullscreen windows in CCSM so that the screensaver works. Also, make sure that the User Switcher applet preferences are on its default setting, with Lock screen after switching users checked. Set the screensaver preferences to its default setting with Lock screen when screensaver is active unchecked. (I tried with it checked as well, and don't think that it makes a difference.) Now create a new user if you don't already have another. Without logging out of the first session, switch to another user. In the new session, uncheck Undirect fullscreen windows in CCSM so that the screensaver works for the new user. Switch between the two user sessions using the User Switcher applet on the panel. (I get a white screen instead of the password prompt. If I blindly type the password it will switch sessions and restore the display to normal.) Assuming you still have two user sessions logged in, Suspend the computer (standby) rather than shutting down normally. Resume the computer from its standby state. (I get a totally black screen except for the mouse cursor, but there is display corruption in a small square around the cursor. Again, blindly typing the password will usually restore the session.) I've found 2 workarounds to the white-screen problem. The first is to click on System, Log out, Switch user rather than using the fast user switcher. This seems to always take you to the GDM login screen, rather than the usual locked-screen window, and prevents the white screen. The second is to uncheck the Lock screen after switching users in the fast user switcher preferences for both users. This again avoids the locked-screen password prompt, which seems to be causing the white screen problem when using the fast user switcher. I have no idea how to fix the black-screen on resume issue, except by leaving Undirect fullscreen windows checked. Once again, this may be an issue with the locked-screen password prompt itself, or how compiz uses it. I've also believe that setting the screensaver preferences to Lock screen when screensaver is active is more of workaround than a real solution to the screensaver not starting. With this option checked the screensaver should start immediately after the pre-set time, and only show the password prompt when theres activity again (move the mouse/keyboard/whatever). With compiz on, it shows the prompt, and after it times out (login period expires), only then does the screensaver start. Turn off compiz and you'll see what I mean. The screen-lock seems to prevent compiz from blocking the screensaver. Disabling compiz for all users also fixes all these issues, and then everything works as advertised. -Nvidia 8600GT with version 177 restricted drivers -- Screensaver doesn't start https://bugs.launchpad.net/bugs/278112 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278086] Re: Compiz inhibits screensaver or causes crash on resume
*** This bug is a duplicate of bug 159263 *** https://bugs.launchpad.net/bugs/159263 ** Attachment added: lspci.txt http://launchpadlibrarian.net/18217335/lspci.txt ** This bug has been marked a duplicate of bug 159263 Gnome-screensaver does not stay on -- Compiz inhibits screensaver or causes crash on resume https://bugs.launchpad.net/bugs/278086 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu (via bug 159263). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 159263] Re: Gnome-screensaver does not stay on
Filed a duplicate before finding this. See Bug #278086 in duplicates section. I'm using Intrepid (beta packages) and Nvidia 8600GT with Nvidia-glx-177 restricted driver. 'Undirect Fullscreen Windows' fixed the screensaver problem, but is causing black screen after resume from standby, particularly when two user sessions are logged on when the machine is put into standby. Blindly typing password allowed logon, and alt-tab restored correct display of the desktop. Disabling compiz allowed screensaver and display-blanking, as well as standby/hibernate/resume to function correctly. -- Gnome-screensaver does not stay on https://bugs.launchpad.net/bugs/159263 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
