[Bug 1755800] Re: Greeter/lockscreen fails to authenicate in an endless loop. Repeated "No space left on device" errors and strange swap file configuration

2018-05-26 Thread Martin D. Weinberg
We can close this bug report at this point.  But I do appreciate the
follow up!

It turns out that there were two problems.  The first was that 18.04 had
misconfigured the cryptoswap so that was not working at all.  I reported
this separately before the release of bionic and I believe that this bug
has been fixed by the maintainers.  The second was that the kernel was
running out of inotify watches and this prevented (for some reason) gdm3
from allowing logins to complete.   The inotify watches were being
consumed by the Crashplan java app.  I increased the
fs.inotify.max_user_watches  to 1048576 and that solved the problem.  I
realize that this consumes some unswappable ram, but I rather have
Crashplan than not.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1755800

Title:
  Greeter/lockscreen fails to authenicate in an endless loop. Repeated
  "No space left on device" errors and strange swap file configuration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1755800/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1768610] Re: No acceleration after upgrading to 18.04: gnome-session-check-accelerated incorrectly picks llvmpipe

2018-05-23 Thread Martin D. Weinberg
xorg.conf has been replaced by the rules in /usr/share/X11/xorg.conf.d.
You can see if there is some older cruft in there.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1768610

Title:
  No acceleration after upgrading to 18.04: gnome-session-check-
  accelerated incorrectly picks llvmpipe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1768610/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1768610] Re: No acceleration after upgrading to 18.04: gnome-session-check-accelerated incorrectly picks llvmpipe

2018-05-22 Thread Martin D. Weinberg
If you want to try that, you can grab a more recent kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/ but I doubt that this
will fix your issue.  I'd bet on a configuration thing, but not sure
what.   You don't, by any chance, have a custom xorg.conf (in /etc/X11
or /usr/share/X11)? I think that working under Wayland but not Xorg is
an important clue.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1768610

Title:
  No acceleration after upgrading to 18.04: gnome-session-check-
  accelerated incorrectly picks llvmpipe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1768610/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1768610] Re: No acceleration after upgrading to 18.04: gnome-session-check-accelerated incorrectly picks llvmpipe

2018-05-21 Thread Martin D. Weinberg
Yes, I would make a new comment to your bug report with the logs under
xorg session.  I hope that one of the Ubuntu developers have a clue
about this.  I'm curious myself.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1768610

Title:
  No acceleration after upgrading to 18.04: gnome-session-check-
  accelerated incorrectly picks llvmpipe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1768610/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1768610] Re: No acceleration after upgrading to 18.04: gnome-session-check-accelerated incorrectly picks llvmpipe

2018-05-21 Thread Martin D. Weinberg
P.S. I also note that you are using wayland.  No reason to think it will
matter, but just of of curiosity, have you tried the xorg session?

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1768610

Title:
  No acceleration after upgrading to 18.04: gnome-session-check-
  accelerated incorrectly picks llvmpipe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1768610/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1768610] Re: No acceleration after upgrading to 18.04: gnome-session-check-accelerated incorrectly picks llvmpipe

2018-05-21 Thread Martin D. Weinberg
I look a quick look at your posted data.  It does seem odd that your
system starts out configuring the drm and then uses fb.  Do you have
anything custom on your boot line, like some video parameters?  E.g.
'cat /proc/cmdline'.  More grabbing at straws.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1768610

Title:
  No acceleration after upgrading to 18.04: gnome-session-check-
  accelerated incorrectly picks llvmpipe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1768610/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1768610] Re: No acceleration after upgrading to 18.04: gnome-session-check-accelerated incorrectly picks llvmpipe

2018-05-21 Thread Martin D. Weinberg
Well, this sounds like a different problem.  The problem I reported was
very clearly the result of an incomplete package upgrade/removal
resulting in a failed test for unity compatibility leading to setting
that environment variable for software gl.

You might consider opening an new bug report with a complete system
info.  E.g. you didn't report your video chipset, but I have heard that
there are nuances with nvidia.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1768610

Title:
  No acceleration after upgrading to 18.04: gnome-session-check-
  accelerated incorrectly picks llvmpipe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1768610/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1768610] Re: No acceleration after upgrading to 18.04: gnome-session-check-accelerated incorrectly picks llvmpipe

2018-05-21 Thread Martin D. Weinberg
Emiliano: I'm grabbing at straws, but try checking for other files in
'/etc/X11/Xsession.d/' that might be setting 'export
LIBGL_ALWAYS_SOFTWARE=1' in the environment.  E.g. 'grep -H LIBGL
/etc/X11/Xsession.d/*'

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1768610

Title:
  No acceleration after upgrading to 18.04: gnome-session-check-
  accelerated incorrectly picks llvmpipe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1768610/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1768610] Re: No acceleration after upgrading to 18.04: gnome-session-check-accelerated incorrectly picks llvmpipe

2018-05-21 Thread Martin D. Weinberg
I'm not an expert, but you might want to see if you can gain some
insight from the output of 'journalctl -b0'.

E.g. is your system using the framebuffer driver "fbcon: xxx" or "[drm]
..." during boot up?

In the 'journalctl -b0' output I posted above,you can see that it's
using the frame buffer.  That is what lead me to track down system
configuration issues.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1768610

Title:
  No acceleration after upgrading to 18.04: gnome-session-check-
  accelerated incorrectly picks llvmpipe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1768610/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1768610] Re: No acceleration after upgrading to 18.04: gnome-session-check-accelerated incorrectly picks llvmpipe

2018-05-21 Thread Martin D. Weinberg
Emiliano: the problem file is
'/etc/X11/Xsession.d/50_check_unity_support'.  You might want to confirm
that this is gone with the purge.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1768610

Title:
  No acceleration after upgrading to 18.04: gnome-session-check-
  accelerated incorrectly picks llvmpipe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1768610/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1768610] Re: No acceleration after upgrading to 18.04: gnome-session-check-accelerated incorrectly picks llvmpipe

2018-05-02 Thread Martin D. Weinberg
I have figured out the problem: the installer removed nux-tools, left
over from unity, but did not purge it.  This left a start up script in
/etc/X11/Xsession.d which interfered with gnome.  Purged that and the
problem was gone.

So this is a dependency bug in the nux-tools package (or perhaps some
mistakenly identified changed file which turned into evil cruft).  Sigh.
Took me a long time to find this.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1768610

Title:
  No acceleration after upgrading to 18.04: gnome-session-check-
  accelerated incorrectly picks llvmpipe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1768610/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1768610] Re: No acceleration after upgrading to 18.04: gnome-session-check-accelerated incorrectly picks llvmpipe

2018-05-02 Thread Martin D. Weinberg
** Summary changed:

- No acceleration after upgrading to 18:04 gnome-session-check-accelerated 
incorrectly picks llvmpipe
+ No acceleration after upgrading to 18.04: gnome-session-check-accelerated 
incorrectly picks llvmpipe

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1768610

Title:
  No acceleration after upgrading to 18.04: gnome-session-check-
  accelerated incorrectly picks llvmpipe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1768610/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1768610] [NEW] No acceleration after upgrading to 18:04 gnome-session-check-accelerated incorrectly picks llvmpipe

2018-05-02 Thread Martin D. Weinberg
Public bug reported:

After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
animations were gone.  After some digging, it seems that gnome-session
incorrectly assumes that my graphics has no acceleration, when in fact
it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
(i915 driver).

I've tried this with and without the xserver-xorg-video-intel package
(a.k.a. Intel driver) with the same behavior.

The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
256 bits)  however the system should have DRM 2.0 capability.

GL checks (e.g. glxinfo, glxgears produce the expected output from a
working DRM system).

mesa-utils and mesa-utils-extra are both installed.

I can't find a work around.  Perhaps there is something wrong with my
install/upgrade?

Everything else works fine, although the graphical transitions are no
longer smooth.  But it would be nice to restore the expected behavior.

I have attached the log of 'journalctl -b0'

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-session 3.28.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed May  2 13:06:00 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-04-22 (739 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-session
UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

** Affects: gnome-session (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

** Attachment added: "Output of journalctl -b0"
   https://bugs.launchpad.net/bugs/1768610/+attachment/5132312/+files/today.log

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1768610

Title:
  No acceleration after upgrading to 18:04 gnome-session-check-
  accelerated incorrectly picks llvmpipe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1768610/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from

2018-03-30 Thread Martin D. Weinberg
I continue to see this problem on a daily basis, often after a resume
from suspend, I am not running Wayland, and this crashes my
gnome-session half the time, so something there is some confusion/bug
somewhere.  This morning's crash resulted in message from xorg-server so
I let apport file a bug against that package too (#1760123).


On 03/30/2018 06:38 AM, Amr Ibrahim wrote:
> There is a mix of duplicates with and without Wayland. Mine was without
> Wayland.
>

-- 
Martin Weinberg
6 Grass Hill Rd
West Whately, MA
010039

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1748450

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler(message="Connection
  to xwayland lost") from g_logv() from g_log() from 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748450/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1755800] Re: Greeter/lockscreen fails to authenicate in an endless loop

2018-03-26 Thread Martin D. Weinberg
I've been studying the swap mess.  It seems that the installer made a
swapfile called /swapfile and entered the line in /etc/crypttab as:

cryptswap1 /target/swapfile /dev/urandom swap,offset=1024,cipher=aes-
xts-plain64

which is the wrong, non-existent filename. So that seems to be an issue with 
the installer scripts.
 
Also, I do not believe that the installer even asked me about a swap partition. 
 I recall being surprised at the time.

Anyway, after fixing that and rerunning ecryptfs-setup-swap, I was able
to use cryptdisks_start to get the encrypted swap going and reboot with
encrypted swap successfully.  I wonder if this has been the root of my
problem all along?

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1755800

Title:
  Greeter/lockscreen fails to authenicate in an endless loop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1755800/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 1755800] Re: Greeter/lockscreen fails to authenicate in an endless loop

2018-03-26 Thread Martin D. Weinberg
Thanks.  Your comments led me to look at swap.  There is no swap!

I installed from iso image several weeks ago (I am traveling and had a
bad ecryptfs corruption, not sure how this happened, and needed to
reinstall, and had this on my memory stick for testing).

I selected encrypted and had an prexisting swap partition.   The
installer made a 2GB swapfile (okay) but the ecryptfs swap did not get
configured correctly, so no swap.  So there is some inconsistency with
the installer, clearly, that should be ironed out.

I made normal swap on both the swapfile and the swap partition, followed
by swapon -a.  Now there is plenty of swap.  I wonder if this is the
cause of the lockscreen behavior?  Difficultly with swap.

I will observe.  Any pointers on correctly configuring my ecryptfs swap
at this point?  Thanks!!


On 03/26/2018 12:21 AM, Daniel van Vugt wrote:
> Come to think of it, some code might be returning ENOSPC ("No space left
> on device") for a RAM-based operation.
>
> So please also check how much RAM your system has before and after the
> problem (run 'free -m'), and check 'ps' to see if any process is
> unusually large.
>
> ** Changed in: gdm3 (Ubuntu)
>Status: New => Incomplete
>
> ** No longer affects: gnome-shell-extension-appindicator (Ubuntu)
>
> ** No longer affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
>

-- 
Martin Weinberg
6 Grass Hill Rd
West Whately, MA
010039

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1755800

Title:
  Greeter/lockscreen fails to authenicate in an endless loop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1755800/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 1755800] Re: Greeter/lockscreen fails to authenicate in an endless loop

2018-03-25 Thread Martin D. Weinberg
I saw that.  But the disk is far from full.  Don't know what's up with
the /snap loopback devices.  The hard drive itself is at 35%.  Here's
the df output:

Filesystem   Size  Used Avail Use% Mounted on
udev 3.8G 0  3.8G   0% /dev
tmpfs    767M  1.9M  765M   1% /run
/dev/sda5    450G  148G  279G  35% /
tmpfs    3.8G  4.0K  3.8G   1% /dev/shm
tmpfs    5.0M  4.0K  5.0M   1% /run/lock
tmpfs    3.8G 0  3.8G   0% /sys/fs/cgroup
/dev/loop1   163M  163M 0 100% /snap/spotify/6
/dev/loop0    82M   82M 0 100% /snap/core/4206
tmpfs    767M   16K  767M   1% /run/user/120
tmpfs    767M   36K  767M   1% /run/user/1000
/home/weinberg/.Private  450G  148G  279G  35% /home/weinberg


On 03/25/2018 10:59 PM, Daniel van Vugt wrote:
> Your log is showing "No space left on device"
>
> So one of your disks is full, which may be the problem. Please check by
> running:
>
>   df -h
>

-- 
Martin Weinberg
6 Grass Hill Rd
West Whately, MA
010039

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1755800

Title:
  Greeter/lockscreen fails to authenicate in an endless loop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1755800/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1755800] Re: Greeter/lockscreen fails to authenicate in an endless loop

2018-03-24 Thread Martin D. Weinberg
I'm still getting failures.  This is with a fixed variety and no gnome-
shell extensions other than the default ubuntu extensions.

I don't see but reports similar to this, so I gather that others are not
generally plagued by this problem.  Nonetheless, I appreciate any advice
or comment you have on what to do here.

I'd like to contribute to improving Ubuntu, but at some point, I going
to have to do something to make this stop just for my own sanity; having
to reboot at random times so that I can log in to my laptop is really
not a good thing.   Switch to a different session type?

I will attach another journanctl -b0 log

Thanks!

** Attachment added: "todays-journal2.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1755800/+attachment/5089039/+files/todays-journal2.txt

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1755800

Title:
  Greeter/lockscreen fails to authenicate in an endless loop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1755800/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 1755800] Re: Greeter/lockscreen fails to authenicate in an endless loop

2018-03-19 Thread Martin D. Weinberg
Thanks.  That variety script was from an old version of variety, it
seems.  I removed that and checked that the current scripts  in
/usr/share/variety/scripts do not have that bug (looked like an
operation on a shell variable that may not exist).  I did notice a few
variety crashes, but they do not seem to coincide with screenlock failure.

I did have "clipboard indicator" and "media player indicator" enabled. 
Disabled those.  Will see what happens.  I can uninstall variety if I
see more issues with that.


On 03/19/2018 10:07 PM, Daniel van Vugt wrote:
> Thanks. I can see two recurring issues that might be the cause:
>
> 1. Something called 'variety' is failing:
>
> Mar 17 08:16:14 magpie variety.desktop[1860]:
> /home/weinberg/.config/variety/scripts/set_wallpaper: line 121: [: ==:
> unary operator expected
>
> Try fixing your script, or try uninstalling 'variety'.
>
> 2. Multiple crashes in extensions:
>
> /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/*
> /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/*
>
> But also:
>
> 3. Please check that you don't have any gnome-shell extensions installed
> other than the two default Ubuntu ones (mentioned above). Since they all
> run in the same process, any buggy extension can break the entire shell.
>
>
> ** Also affects: gnome-shell-extension-appindicator (Ubuntu)
>Importance: Undecided
>Status: New
>
> ** Changed in: gnome-shell-extension-appindicator (Ubuntu)
>Status: New => Incomplete
>
> ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
>Importance: Undecided
>Status: New
>
> ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
>Status: New => Incomplete
>

-- 
Martin Weinberg
6 Grass Hill Rd
West Whately, MA
010039

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1755800

Title:
  Greeter/lockscreen fails to authenicate in an endless loop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1755800/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1755800] Re: Greeter/lockscreen fails to authenicate in an endless loop

2018-03-19 Thread Martin D. Weinberg
Daniel,

I took a few days, but it did again fail with the same issue.  I'm
attaching the log, collected shortly after the failure by switch to
console while running the Wayland session, as you requested.  Had to
reboot afterwards, to be able to log on to the desktop.

Hope this helps you spot the issue.

** Attachment added: "Output of journalctl -b0"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1755800/+attachment/5083910/+files/todays-journal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1755800

Title:
  Greeter/lockscreen fails to authenicate in an endless loop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1755800/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1755800] Re: Greeter/lockscreen fails to authenicate in an endless loop

2018-03-14 Thread Martin D. Weinberg
** Tags removed: wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1755800

Title:
  Greeter/lockscreen fails to authenicate in an endless loop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1755800/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1755800] Re: Greeter/lockscreen fails to authenicate in an endless loop

2018-03-14 Thread Martin D. Weinberg
Also a problem with the Wayland session.  Not a big surprise.   For now,
I've turn off the screen lock.

Not sure what else to do.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1755800

Title:
  Greeter/lockscreen fails to authenicate in an endless loop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1755800/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1755800] Re: Greeter/lockscreen fails to authenicate in an endless loop

2018-03-14 Thread Martin D. Weinberg
Addendum: I was running the Xorg ("Ubuntu") session when the problems
occurred.  I'm trying the Wayland session now, so the autogenerated tag
is not correct, and maybe not relevant.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1755800

Title:
  Greeter/lockscreen fails to authenicate in an endless loop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1755800/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1755800] [NEW] Greeter/lockscreen fails to authenicate in an endless loop

2018-03-14 Thread Martin D. Weinberg
Public bug reported:

After a recent install of the 18.04 (why is a separate story), I notice
that after some number of successful screen locks, I become locked out
of the desktop with an authentication failure.  During those
unsuccessful attempts to log in, syslog shows:

Mar 13 22:46:04 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" "21"
Mar 13 22:46:04 magpie kernel: [83554.367969] rfkill: input handler enabled
Mar 13 22:46:04 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event2  - Power B
utton: device removed
Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" "25"
Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event4  - Video B
us: device removed
Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" "27"
Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event1  - Sleep B
utton: device removed
Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" "24"
Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event17 - Integra
ted Camera: Integrated C: device removed
Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" "29"
Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event3  - AT Tran
slated Set 2 keyboard: device removed
Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" "28"
Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event5  - 
SynPS/2 Synaptics TouchPad: device removed
Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" "30"
Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event6  - TPPS/2 
IBM TrackPoint: device removed
Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" "62"
Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event7  - 
ThinkPad Extra Buttons: device removed
Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) AIGLX: 
Suspending AIGLX clients for VT switch
Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) systemd-logind: 
got pause for 13:81
Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) systemd-logind: 
got pause for 13:68
Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) systemd-logind: 
got pause for 226:0
Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) systemd-logind: 
got pause for 13:71
Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) systemd-logind: 
got pause for 13:66

one new line for each attempted log in.  This is occurring once or twice
a day.  Sometimes, it works again.  Last time, I needed to reboot.

Since this is a fresh install, albeit with my desktop files being
restored via CrashPlan (which could be part of the problem?), I thought
that this warranted a report.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gdm3 3.27.92-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 14 07:58:11 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-03-12 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180114)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gdm3 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1755800

Title:
  Greeter/lockscreen fails to authenicate in an endless loop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1755800/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1730093] Re: Gnome suspends or blanks external monitor when laptop is docked

2017-11-07 Thread Martin D. Weinberg
I refiled the bug at bugzilla.gnome.org as bug 790040.

The link is:  https://bugzilla.gnome.org/show_bug.cgi?id=790040

I'm really surprised that there are not more complaints about this.  To
be fair, the dock+external monitor setup has NOT worked perfectly in any
release Ubuntu release, including 16.04.  Although, before 17.10,
trouble only arose when moving the laptop between docks with different
monitors, so it was tolerable.

I sure hope this can be fixed.  I suppose I could cook up some sort of
udev script to handle dock changes for my situation but that is horrible
kludge, not a fix.

On 11/07/2017 05:13 PM, Sebastien Bacher wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. The issue you are reporting is an upstream one and it
> would be nice if somebody having it could send the bug to the developers
> of the software by following the instructions at
> https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
> tell us the number of the upstream bug (or the link), so we can add a
> bugwatch that will inform us about its status. Thanks in advance.
>
> ** Package changed: gnome-settings-daemon (Ubuntu) => gnome-shell
> (Ubuntu)
>
> ** Changed in: gnome-shell (Ubuntu)
>Importance: Undecided => Low
>

-- 
Martin Weinberg
6 Grass Hill Rd
West Whately, MA
010039



** Bug watch added: GNOME Bug Tracker #790040
   https://bugzilla.gnome.org/show_bug.cgi?id=790040

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1730093

Title:
  Gnome suspends or blanks external monitor when laptop is docked

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730093/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1730093] Re: Gnome suspends or blanks external monitor when laptop is docked

2017-11-04 Thread Martin D. Weinberg
Just to make sure, I again repeated the sequence of events outlined
above on the stock 17.10 kernel:

Linux magpie 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux

The behavior is identical to that reported above.

One minor elaboration: when I open the control panel->Devices->Displays
with the lid action set to "ignore", I have to toggle the external
monitor, even if it is currently selected, in order to prevent the lid
close from blanking the display.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1730093

Title:
  Gnome suspends or blanks external monitor when laptop is docked

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1730093/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1730093] [NEW] Gnome suspends or blanks external monitor when laptop is docked

2017-11-04 Thread Martin D. Weinberg
Public bug reported:

In the default configuration, resuming my T440s on the Lenovo ultradock
results in not detecting the external monitor followed by a suspend.

If I open the lid while on the dock, gnome detects the external monitor
and blanks the laptop display.  Then, closing the lid results in
suspend.

As a work around, using tweak tool (or UPower) to ignore the lid, does
prevent the suspend.  But it is not automatic; each time, one must bring
up the gnome control panel->devices->displays and manually select single
display.  Then the lid may be closed without suspend.

This worked fine in 17.04, so I'm hoping that the provides enough clues
that this can be fixed easily.

Thanks!  I am enjoying the new Ubuntu 17.10 generally, but this
situation is annoying.

System details:

linux magpie 4.13.9-041309-generic #201710211231 SMP Sat Oct 21 16:32:44
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

I'm trying a kernel from mainline, just to see if that matters; it
doesn't.  Same behavior on stock 17.10 kernel.

Software version:

Package: gnome-settings-daemon
Versions: 
3.26.1-0ubuntu5 
(/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_artful_main_binary-amd64_Packages)
 (/var/lib/dpkg/status)

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-settings-daemon 3.26.1-0ubuntu5
Uname: Linux 4.13.9-041309-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov  4 12:32:43 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-05-06 (546 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-settings-daemon
UpgradeStatus: Upgraded to artful on 2017-10-20 (15 days ago)

** Affects: gnome-settings-daemon (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1730093

Title:
  Gnome suspends or blanks external monitor when laptop is docked

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1730093/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725698] Re: Size decreases when cycling between full-screen mode using F11

2017-10-24 Thread Martin D. Weinberg
Yes, no problem with GNOME on Xorg.  Thanks for the heads up.

I found another problem with Wayland handling the dock + laptop lid that
works correctly with Xorg.  Just trying to help.  Not sure what package
to file a bug on, do you?  Would that be xwayland?

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1725698

Title:
  Size decreases when cycling between full-screen mode using F11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1725698/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725698] Re: Size decreases when cycling between full-screen mode using F11

2017-10-24 Thread Martin D. Weinberg
Yes, GNOME on Wayland.  I will try GNOME on X.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1725698

Title:
  Size decreases when cycling between full-screen mode using F11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1725698/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725698] [NEW] Size decreases when cycling between full-screen mode using F11

2017-10-21 Thread Martin D. Weinberg
Public bug reported:

Launch an gnome-terminal and cycle between full screen and normal by
pressing F11 twice.  The original size of the terminal is not restored.
Doing this multiple times, the window continues to shrink.

This did not occur on 17.04 or earlier.  I use this regularly as part of
my workflow.  Obviously, this is a minor issue, but it sure is annoying.

This bug does not exist in terminator FWIW.  I'd prefer not to switch to
terminator, however.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-terminal 3.24.2-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 21 09:49:18 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-04-22 (546 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to artful on 2017-10-20 (1 days ago)

** Affects: gnome-terminal (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1725698

Title:
  Size decreases when cycling between full-screen mode using F11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1725698/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 841541] Re: num lock is on warning remains even after num lock is turned off

2011-11-11 Thread Martin D. Weinberg
Regarding Comment #6: I can confirm that changing the BIOS setting on
numlock behavior from independent to synchronized does indeed solve
the problem here.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/841541

Title:
  num lock is on warning remains even after num lock is turned off

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/841541/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs