[Bug 1991901] Re: JS ERROR: Failed to initialize fprintd service: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available

2024-07-02 Thread Alexander
Having 100% reproduce of this bug on every suspend-resume of my laptop (yes, it 
has fingerprint device)
There are tons of these errors in system logs... 
why?


lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.4 LTS
Release:22.04
Codename:   jammy

○ → uname -a
Linux tplevo347 5.15.0-113-generic #123-Ubuntu SMP Mon Jun 10 08:16:17 UTC 2024 
x86_64 x86_64 x86_64 GNU/Linux




Jul 02 19:10:37 tplevo347 gnome-shell[2667]: JS ERROR: Failed to initialize 
fprintd service: Gio.IOErrorEnum: 
GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: Object St.BoxLayout 
(0x55bdbffe5050), has been already disposed — impossible to set any property on 
it. This might be caused by the object having been destroyed from C code using 
something such as destroy(), dispose(), or remove() vfuncs.
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: Object 
.Gjs_ui_unlockDialog_UnlockDialogClock (0x55bdbf3a55a0), has been already 
disposed — impossible to set any property on it. This might be caused by the 
object having been destroyed from C code using something such as destroy(), 
dispose(), or remove() vfuncs.
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: == Stack trace for context 
0x55bdbc82a190 ==
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: #0   7ffd24ca6810 b   
resource:///org/gnome/shell/ui/unlockDialog.js:739 (97742ee6790 @ 26)
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: #1   7ffd24ca68d0 b   
resource:///org/gnome/shell/ui/unlockDialog.js:493 (97742ee6330 @ 27)
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: == Stack trace for context 
0x55bdbc82a190 ==
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: #0   7ffd24ca6810 b   
resource:///org/gnome/shell/ui/unlockDialog.js:740 (97742ee6790 @ 46)
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: #1   7ffd24ca68d0 b   
resource:///org/gnome/shell/ui/unlockDialog.js:493 (97742ee6330 @ 27)
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: == Stack trace for context 
0x55bdbc82a190 ==
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: #0   7ffd24ca6740 b   
resource:///org/gnome/gjs/modules/core/overrides/GObject.js:685 (1a22493bc100 @ 
25)
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: #1   7ffd24ca6810 b   
resource:///org/gnome/shell/ui/unlockDialog.js:742 (97742ee6790 @ 93)
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: #2   7ffd24ca68d0 b   
resource:///org/gnome/shell/ui/unlockDialog.js:493 (97742ee6330 @ 27)
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: == Stack trace for context 
0x55bdbc82a190 ==
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: #0   7ffd24ca6740 b   
resource:///org/gnome/gjs/modules/core/overrides/GObject.js:685 (1a22493bc100 @ 
25)
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: #1   7ffd24ca6810 b   
resource:///org/gnome/shell/ui/unlockDialog.js:742 (97742ee6790 @ 93)
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: #2   7ffd24ca68d0 b   
resource:///org/gnome/shell/ui/unlockDialog.js:493 (97742ee6330 @ 27)
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: == Stack trace for context 
0x55bdbc82a190 ==
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: #0   7ffd24ca6740 b   
resource:///org/gnome/gjs/modules/core/overrides/GObject.js:685 (1a22493bc100 @ 
25)
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: #1   7ffd24ca6810 b   
resource:///org/gnome/shell/ui/unlockDialog.js:749 (97742ee6790 @ 238)
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: #2   7ffd24ca68d0 b   
resource:///org/gnome/shell/ui/unlockDialog.js:493 (97742ee6330 @ 27)
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: == Stack trace for context 
0x55bdbc82a190 ==
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: #0   7ffd24ca6740 b   
resource:///org/gnome/gjs/modules/core/overrides/GObject.js:685 (1a22493bc100 @ 
25)
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: #1   7ffd24ca6810 b   
resource:///org/gnome/shell/ui/unlockDialog.js:749 (97742ee6790 @ 238)
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: #2   7ffd24ca68d0 b   
resource:///org/gnome/shell/ui/unlockDialog.js:493 (97742ee6330 @ 27)
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: Object St.Button (0x55bdbfdeb460), 
has been already disposed — impossible to set any property on it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: == Stack trace for context 
0x55bdbc82a190 ==
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: #0   7ffd24ca6740 b   
resource:///org/gnome/gjs/modules/core/overrides/GObject.js:685 (1a22493bc100 @ 
25)
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: #1   7ffd24ca6810 b   
resource:///org/gnome/shell/ui/unlockDialog.js:749 (97742ee6790 @ 238)
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: #2   7ffd24ca68d0 b   
resource:///org/gnome/shell/ui/unlockDialog.js:493 (97742ee6330 @ 27)
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: == Stack trace for context 
0x55bdbc82a190 ==
Jul 02 19:10:38 tplevo347 gnome-shell[2667]: #0   

[Bug 1991901] Re: JS ERROR: Failed to initialize fprintd service: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available

2024-07-02 Thread Alexander
attaching as file as post has limits


** Attachment added: "full logs for above message (that was trimmed by site)"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1991901/+attachment/5794228/+files/fprintd.err.txt

-- 
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/1991901

Title:
  JS ERROR: Failed to initialize fprintd service: Gio.IOErrorEnum:
  GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices
  available

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


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

[Bug 1857392] Re: Window manager warning: Overwriting existing binding of keysym...

2024-06-30 Thread Alexander
seeing same huge amount of logs when switching language using keyboard
shortcuts  (Win + Space) or my another combinatino - Alt + Shift

eg:


Jun 30 16:45:02 tplevo347 gnome-shell[6781]: Window manager warning: 
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Jun 30 16:45:02 tplevo347 gnome-shell[6781]: Window manager warning: 
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Jun 30 16:45:02 tplevo347 gnome-shell[6781]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Jun 30 16:45:02 tplevo347 gnome-shell[6781]: Window manager warning: 
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Jun 30 16:45:02 tplevo347 gnome-shell[6781]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Jun 30 16:45:02 tplevo347 gnome-shell[6781]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Jun 30 16:45:02 tplevo347 gnome-shell[6781]: Window manager warning: 
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Jun 30 16:45:02 tplevo347 gnome-shell[6781]: Window manager warning: 
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Jun 30 16:45:02 tplevo347 gnome-shell[6781]: Window manager warning: 
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).


Jun 30 16:45:12 tplevo347 gnome-shell[6781]: Window manager warning: 
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Jun 30 16:45:12 tplevo347 gnome-shell[6781]: Window manager warning: 
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Jun 30 16:45:12 tplevo347 gnome-shell[6781]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Jun 30 16:45:12 tplevo347 gnome-shell[6781]: Window manager warning: 
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Jun 30 16:45:12 tplevo347 gnome-shell[6781]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Jun 30 16:45:12 tplevo347 gnome-shell[6781]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Jun 30 16:45:12 tplevo347 gnome-shell[6781]: Window manager warning: 
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Jun 30 16:45:12 tplevo347 gnome-shell[6781]: Window manager warning: 
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Jun 30 16:45:12 tplevo347 gnome-shell[6781]: Window manager warning: 
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).



 130 ❯ uname -a
Linux tplevo347 5.15.0-113-generic #123-Ubuntu SMP Mon Jun 10 08:16:17 UTC 2024 
x86_64 x86_64 x86_64 GNU/Linux

❯ cat /etc/issue
Ubuntu 22.04.4 LTS \n \l


How to get rid of these messages?

-- 
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/1857392

Title:
  Window manager warning: Overwriting existing binding of keysym...

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


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

[Bug 2065674] [NEW] GIMP crashed with a fatal error: fatal error: Minnesegmentsfeil

2024-05-14 Thread Alexander Vinbæk Strand
Public bug reported:




```
GNU Image Manipulation Program version 2.10.36
git-describe: GIMP_2_10_36
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
13.2.0-23ubuntu3' --with-bugurl=file:///usr/share/doc/gcc-13/README.Bugs 
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-13 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/libexec --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new 
--enable-libstdcxx-backtrace --enable-gnu-unique-object --disable-vtable-verify 
--enable-plugin --enable-default-pie --with-system-zlib 
--enable-libphobos-checking=release --with-target-system-zlib=auto 
--enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-13-OiuXZC/gcc-13-13.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-13-OiuXZC/gcc-13-13.2.0/debian/tmp-gcn/usr
 --enable-offload-defaulted --without-cuda-driver --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu3) 

# Libraries #
using babl version 0.1.108 (compiled against version 0.1.108)
using GEGL version 0.4.48 (compiled against version 0.4.48)
using GLib version 2.80.0 (compiled against version 2.80.0)
using GdkPixbuf version 2.42.10 (compiled against version 2.42.10)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.52.1 (compiled against version 1.52.1)
using Fontconfig version 2.15.0 (compiled against version 2.15.0)
using Cairo version 1.18.0 (compiled against version 1.18.0)

```
> fatal error: Minnesegmentsfeil

Stack trace:
```

# Stack traces obtained from PID 14282 - Thread 14282 #


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from 
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 14468]
[New LWP 14310]
[New LWP 14307]
[New LWP 14303]
[New LWP 14302]
[New LWP 14301]
[New LWP 14300]
[New LWP 14299]
[New LWP 14298]
[New LWP 14297]
[New LWP 14296]
[New LWP 14295]
[New LWP 14294]
[New LWP 14293]
[New LWP 14292]
[New LWP 14291]
[New LWP 14290]
[New LWP 14289]
[New LWP 14288]
[New LWP 14287]
[New LWP 14286]
[New LWP 14285]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7241b291ba9a in __GI___libc_read (nbytes=256, buf=0x7fff70cffcb0, fd=18) 
at ../sysdeps/unix/sysv/linux/read.c:26
  Id   Target IdFrame 
* 1Thread 0x7241b2082640 (LWP 14282) "gimp-2.10"0x7241b291ba9a in 
__GI___libc_read (nbytes=256, buf=0x7fff70cffcb0, fd=18) at 
../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x724197e006c0 (LWP 14468) "swap writer"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7241896006c0 (LWP 14310) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x72418aa006c0 (LWP 14307) "async"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x72419cc006c0 (LWP 14303) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x72419d6006c0 (LWP 14302) "gdbus"0x7241b291b4cd in 
__GI___poll (fds=0x72413c000b90, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  7Thread 0x72419e0006c0 (LWP 14301) "gmain"0x7241b291b4cd in 
__GI___poll (fds=0x5d3b68d0cdc0, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  8Thread 0x72419ea006c0 (LWP 14300) "pool-spawner" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  9Thread 0x72419f4006c0 (LWP 14299) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x72419fe006c0 (LWP 14298) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  11   Thread 0x7241a50006c0 (LWP 14297) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  12   Thread 0x7241a5a006c0 (LWP 14296) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  13   Thread 0x7241a64006c0 

[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

2024-03-06 Thread Alexander Browne
I am seeing this with the (relatively new) Mozilla-provided Firefox deb
package (https://support.mozilla.org/en-US/kb/install-firefox-
linux#w_install-firefox-deb-package-for-debian-based-distributions).

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

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


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

[Bug 1900167] Re: gnome-software unable to install updates (Prepared update not found)

2023-12-17 Thread Alexander
I got it also in recent version, you need then to go to system software
update, and then it is now working. But from a user perspective, not
good.

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

Title:
  gnome-software unable to install updates (Prepared update not found)

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


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

[Bug 1711538] Re: Tap-to-click does not work on the GDM login screen

2023-12-08 Thread Alexander Browne
Still an issue with current releases. Default GNOME/libinputa doesn't
enable tap-to-click, but Ubuntu does for the GNOME desktop, and
therefore it should also for GDM.

Easy workaround posted in duplicate bug:
https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1968315/comments/1

-- 
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/1711538

Title:
  Tap-to-click does not work on the GDM login screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1711538/+subscriptions


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

[Bug 2038789] Re: Password for VPN not saved

2023-10-09 Thread Alexander Koskovich
Ubuntu 23.10 (mantic), and disregard. Reinstalled and it's not any issue
anymore(?)

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

Title:
  Password for VPN not saved

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


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

[Bug 2038789] [NEW] Password for VPN not saved

2023-10-08 Thread Alexander Koskovich
Public bug reported:

Cannot change password of a VPN connection. It doesn't get saved when
you click "Apply".

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


** Tags: mantic

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

Title:
  Password for VPN not saved

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


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

[Bug 2037011] Re: Can't create ovpn

2023-09-24 Thread Alexander Koskovich
Worth noting this looks to be a bug in the official GNOME 45 release?

** Also affects: network-manager-openvpn (Fedora)
   Importance: Undecided
   Status: New

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

Title:
  Can't create ovpn

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/2037011/+subscriptions


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

[Bug 2032119] Re: unable to open gnome-software

2023-08-25 Thread Alexander Vinbæk Strand
here are some files from apport from the crash on my PC.

** Attachment added: "Gnome-software crash info.zip"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2032119/+attachment/5695077/+files/Gnome-software%20crash%20info.zip

** Tags added: crash

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

Title:
  unable to open gnome-software

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


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

[Bug 2032119] Re: unable to open gnome-software

2023-08-25 Thread Alexander Vinbæk Strand
** Attachment added: "ProcEnviron"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2032119/+attachment/5695076/+files/ProcEnviron

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

Title:
  unable to open gnome-software

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


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

[Bug 2032119] Re: unable to open gnome-software

2023-08-25 Thread Alexander Vinbæk Strand
** Attachment added: "Dependencies"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2032119/+attachment/5695075/+files/Dependencies

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

Title:
  unable to open gnome-software

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


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

[Bug 2032119] Re: unable to open gnome-software

2023-08-25 Thread Alexander Vinbæk Strand
Same problem here, upgraded from 23.04 today and unable to open gnome-
software on Ubuntu 23.10

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

Title:
  unable to open gnome-software

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


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

[Bug 2023776] Re: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions

2023-07-26 Thread Alexander
PS: Before I forget, I also tested something else, see attached
screenshot. Going into nvidia-settings and manually setting the
PowerMizer mode to "prefer maximum performance" makes all animations,
the overview and everything related to it super smooth fps-wise. You can
make this permanent by adding these changes to the startup applications
/ commands so that it sticks upon reboot. I opened the overview 30 times
in a row right now, not a single fps-drop. However, this does not fix
the low fps-rate and sluggish behaviour when trying to resize individual
windows (files). The latter only gets a performance boost when turning
off vsync in nvidia-settings. The downside to this is of course the
higher power consumption, but it does indicate that the lag might be
connected to the lower power modes. Iirc sluggish 3d animations on the
desktop with Nvidia was also an issue all the way back on Ubuntu during
the good old Compiz days, and I remember fixing it by adjusting the
PowerMizer mode to prefer a higher performance mode.

** Attachment added: "Bildschirmfoto vom 2023-07-26 17-12-03.png"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023776/+attachment/5688578/+files/Bildschirmfoto%20vom%202023-07-26%2017-12-03.png

-- 
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/2023776

Title:
  Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions

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


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

[Bug 2023776] Re: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions

2023-07-26 Thread Alexander
xrandrv.txt as requested by Dan

** Attachment added: "xrandrv.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023776/+attachment/5688576/+files/xrandrv.txt

-- 
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/2023776

Title:
  Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions

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


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

[Bug 2023776] Re: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions

2023-07-26 Thread Alexander
Hi Daniel,

I will follow your suggestion and try to find the time to create a new
bug report for the additional issues that occured. That said, since the
drive on this machine suffered from what I wrote above, I decided to
quickly format and perform the steps that you suggested on a fresh
Ubuntu 23.04 install. First of all, I am happy to report that checking
the checkbox for "additional drivers" (proprietary gpu and wifi drivers)
during the installation of 23.04 did in fact successfully and flawlessly
install the proprietary Nvidia drivers this time around - namely the
Nvidia driver 535 that killed my 22.04 installation. This was not the
case the first two times that I installed 23.04, so it seems that we
have already made some progress in this regard.

That said, back to the initial issue:

  MUTTER_DEBUG_TRIPLE_BUFFERING=always
  MUTTER_DEBUG_TRIPLE_BUFFERING=never
  CLUTTER_PAINT=disable-dynamic-max-render-time
  
I tried all of these under 23.04 separately per reboot, sadly no change. 23.04 
still shows signs of sluggish or low fps when resizing windows and also when 
opening the overview with a few programs open (Firefox, Software Center, text 
editor etc). Sometimes the overview is buttery smooth, but at some point it 
drops in performance and loses a few fps, just like mentioned in my initial 
post. For example, opening the overview while writing this text I can clearly 
see an fps-drop, but after repeating the process two or three times it becomes 
buttery smooth all of a sudden. The only thing that makes everything super fast 
all the time is when disabling vsync in nvidia-settings -> opengl. Doing this 
results in buttery smooth 60+ fps animations all the time - and no lag when 
resizing windows either. 

I attached the xrandrv.txt that you requested further below.

Please note: I will be formatting this Nvidia powered machine tonight in
order to install another distro onto it, so I won't be able to further
test these things on this particular machine. That said, I want to
reiterate that I will still continue to use Ubuntu on many of my other
computers that are equipped with AMD and Intel gpu hardware. Your triple
buffering vsync patches work beautifully on Amd and even on super low-
end Intel igpu hardware. I love Ubuntu, and I highly appreciate your
personal efforts for everything related to triple buffering / vsync and
more, which is why I am going to be donating a couple of bucks to you
guys this weekend in order to contribute my fair share since
troubleshooting these Nvidia specific issues is too time consuming for
me right now.

Thanks Dan, appreciate all the help!

-- 
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/2023776

Title:
  Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions

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


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

[Bug 2023776] Re: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions

2023-07-24 Thread Alexander
** Attachment added: "Bildschirmfoto vom 2023-07-25 05-42-01.png"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023776/+attachment/5688204/+files/Bildschirmfoto%20vom%202023-07-25%2005-42-01.png

-- 
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/2023776

Title:
  Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions

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


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

[Bug 2023776] Re: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions

2023-07-24 Thread Alexander
Screenshots: Ubuntu 22.04.2 LTS, partial upgrade option after Nvidia
driver 535 went live.

** Attachment added: "Bildschirmfoto vom 2023-07-25 05-42-07.png"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023776/+attachment/5688203/+files/Bildschirmfoto%20vom%202023-07-25%2005-42-07.png

-- 
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/2023776

Title:
  Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions

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


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

[Bug 2023776] Re: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions

2023-07-24 Thread Alexander
Hello Daniel, I apologize for the huge delay, but I have been
experiencing a number of show stopping issues that I have yet to recover
from.

As written above: After all the issues that I had with Ubuntu 23.04, I
decided to "downgrade" to Ubuntu 22.04.2, which was working just fine at
first, see comment above. I was using the recommended and "tested"
Nvidia driver 525, which was the one that the Ubuntu additional drivers
tool suggested. Recently Nvidia released the proprietary Nvidia driver
version 535, which was made available via Ubuntu 22.04.2. So I ran the
Ubuntu system updates utility like I usually would, in the hopes of
Ubuntu picking up the newest Nvidia driver automatically, like it has
always done in the past. Ubuntu did find and suggest to install the new
Nvidia driver, but...

Just like on Ubuntu 23.04, Ubuntu 22.04.2 also mentioned something about
a "partial upgrade", see attached screenshots below. Trying to click on
"continue" instead didn't offer any updates, so I went back to the
"partial upgrade" option, because my system wasn't getting any updates
whatsoever ever since this "issue" appeared out of nowhere. In the
middle of the "partial upgrade" my 22.04.2 system went black, meaning
all of my screens turned off randomly, and the computer would not react
to any user input whatsoever. After being forced to perform a hard
reboot, the computer did not want to boot, spitting out several "journal
errors" during the boot process.

I would like to mention that this was a fresh install of 22.04.2 - not a
single ppa etc. was added manually - just a handful of native apps
installed as Snap via the official Ubuntu Software Center (including
Steam, also installed via the Ubuntu Software Center). I hardly used the
system, because I was still in the process of transferring over the data
that I had to recover from my busted 23.04 install.

A few notes here:

- this happened totally randomly
- previous system updates were completed without any issues whatsoever
- there were no issues whatsoever before the new Nvidia driver 535
- the partial upgrade option mentioned a bunch of Nvidia 535 modules to be 
installed
- and the old 530 driver to be removed
- and it also mentioned a ton of other things to be updated as well, including 
the kernel and a bunch of Ubuntu desktop files

Digging around I found out that both this and the low latency kernel
subject is a common and repeating issue:

- https://askubuntu.com/questions/1443779/why-doesnt-this-software-
updater-warning-tell-me-what-is-going-to-be-installed

-
https://www.reddit.com/r/Kubuntu/comments/14ndb7a/why_do_i_keep_getting_these_oracle_and_lowlatency/

- https://askubuntu.com/questions/1334791/not-all-updates-can-be-
installed-in-software-updater

- https://askubuntu.com/questions/725481/ubuntu-software-updater-not-
all-updates-can-be-installed

- https://www.google.com/search?channel=fs=ubuntu-
sn=ubuntu+nvidia+partial+upgrade

Verdict:

Now I have to recover my freshly installed 22.04.2 system again, just
like I did with 23.04 a few days ago. Since I don't have the time to
troubleshoot this yet again, I am now forced to go for a clean install
again, but I will be using a different distro this time around as it
seems that even Ubuntu LTS has become highly unstable / unusable for
Nvidia users. This is extremely aggravating to say the least. This
entire ordeal will set me back another one or two weeks at the very
least. Been an Ubuntu user for decades now, and recently switched from
AMD to Nvidia gpu, and it's been nothing but trouble thus far, sadly.
Using an AMD gpu was flawless for the most part, but on Nvidia it's one
headache after another on 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/2023776

Title:
  Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions

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


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

[Bug 2023776] Re: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions

2023-06-20 Thread Alexander
Hey there Daniel,

thanks for helping out! I can confirm that what nuked my 23.04 install
is bug 2023946, which I responded to a few days ago. While trying to fix
the issue at hand, before I read your suggestion on how to potentially
fix it, I followed a howto online, which was more or less suggesting the
same thing that you asked me to try. Something went wrong while trying
the potential fix and I was left with blinking cursor upon reboot again.
I gave up at this point, saved my data and reverted back to 22.04.2 LTS
for the machine in question. It took me an entire day to troubleshoot
23.04 and revert back to 22.04, but now everything is stable again. What
I also noticed is how trying to install the proprietary Nvidia drivers
during the initial install of 23.04 was causing issues, not so on
22.04.2 LTS, the latter which didn't install the proprietary Nvidia
drivers at all during a fresh installation of the OS (even though the
box for this was enabled / activated). I had to manually select the
newest proprietary Nvidia driver for 22.04.2 after the OS was fully
installed (using the preinstalled drivers tool app), and it worked like
a charm. 22.04.2 is running well, no issues when resizing windows or any
of the other things noticed in 23.04. The only thing that I notice on
22.04.2 LTS is that the framerate is a bit low when opening the Gnome
overview initially (feels like 20-30 fps), but it gets super smooth at
60 fps when opening the overview for a second time right after the first
attempt. In other words, it takes Ubuntu some time to catch up and make
it smooth again, but when it does it's actually really smooth.

That said, I have a secondary machine here with 23.04 and an Nvidia gpu
with proprietary drivers installed. I will be testing the suggestions
that you wrote on 2023-06-16 later tonight, if I am able to bypass the
issue in bug report 2023946 for the secondary machine. Will report back
by tomorrow night with my findings - - - WIP.

-- 
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/2023776

Title:
  Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions

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


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

[Bug 2023776] Re: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions

2023-06-16 Thread Alexander
This is what Ubuntu wanted to download after the first update attempt

** Attachment added: "Nvidia 530 on 2304 nuke"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023776/+attachment/5680190/+files/nvidia%20nuke%202304.png

-- 
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/2023776

Title:
  Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions

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


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

[Bug 2023776] Re: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions

2023-06-16 Thread Alexander
Hello Daniel,

thanks for taking a look! Not sure if I am going to be able to test this
after all. I just ran Ubuntu 23.04 updates like I always do, and noticed
that 23.04 now has access to Nvidia driver 530, so I ran Ubuntu updates,
which unfortunately nuked my Ubuntu install.

This is what happened:

- I ran the preinstalled Ubuntu 23.04 update tool
- Ubuntu mentioned a bunch of Nvidia packages that needed to be updated and a 
bunch of Linux headers to be removed
- I let Ubuntu do its thing and update the system
- After a reboot I had nvidia-settings installed, but it was missing everything 
feature-wise and was pretty much blank, no hardware acceleration
- So I ran Ubuntu updates again and this time it had a bunch of old Nvidia 525 
files and Linux headers to remove
- I proceeded and rebooted
- Nvidia-settings is still blank, no 3d acceleration whatsoever
- So I opened the driver utility tool and switched from Nvidia 525 to the Xorg 
Nouveau driver and rebooted
- Now Ubuntu won't boot and shows a blinking cursor on the top left corner, 
which freezes after a while
- So after a hard reset of the pc, I pressed and held "shift" upon boot
- I added "nomodeset" to the kernel boot options (btw, Ubuntu is now using a 
"low latency kernel" by default for some reason)
- Which allowed me to boot into Ubuntu
- Now I switched over to the new Nvidia 530 driver and rebooted
- Still a blank Nvidia-settings app and still no hardware acceleration
- Tried reinstalled the Nvidia driver again, to no avail

After some digging around I found:

- https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-530/+bug/2023946

- https://forums.developer.nvidia.com/t/530-doesnt-work-on-
ubuntu-23-04/256721/3

- https://bugs.launchpad.net/ubuntu/+bug/2015775

Since this is a stable production system, I am considering downgrading
back to the 22.04 LTS at this point.

-- 
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/2023776

Title:
  Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions

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


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

[Bug 1922047]

2023-06-16 Thread Alexander Browne
> in gtk, kinetic scrolling stops after you put a finger on the touchpad
(zwp_pointer_gesture_hold_v1 event), but in firefox it doesn't, you have
to wait

In GTK 4, and Firefox uses GTK 3. So either someone need to add it to
GTK 3 or Firefox needs to use to GTK 4.

-- 
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/1922047

Title:
  Touchpad scrolling is too fast

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1922047/+subscriptions


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

[Bug 2023776] Re: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps

2023-06-14 Thread Alexander
Btw, I just noticed that some drop down windows, such as the ones in the
Chromium Snap, also have a little bit of pixelation in them when vsync
is active in nvidia-settings.

-- 
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/2023776

Title:
  Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps

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


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

[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

2023-03-31 Thread Alexander
I run Ubuntu 22.04.02 on a Lenovo Legion 5i pro.
There was a bug when I switched on Wayland session.
I followed instructions that are described above and deleted gnome extention 
aplication.
And I've got no issues any more with lock my laptop and black screen. It's 
fantastic!
My conclusion is, set up latest version of Linux kernel, latest version of 
Nvidia driver(in my case I'm using Nvidia Server Driver 252) in Wayland 
session. And don't use Gnome extensions. Good luck :)

-- 
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/1968040

Title:
  Blanked screen doesn't wake up after locking [drmModeAtomicCommit:
  Argument invalide] [drmModeAtomicCommit: Invalid argument]

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


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

[Bug 2002886] Re: Can't copy and paste from Geany (and SciTE?) in Wayland with GTK 3.24.35

2023-01-20 Thread Alexander Browne
Resolved since GTK was updated to 3.24.36. (Tested with
3.24.36-1ubuntu1.)

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Fix Released

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

Title:
  Can't copy and paste from Geany (and SciTE?) in Wayland with GTK
  3.24.35

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2002886/+subscriptions


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

[Bug 2002886] [NEW] Can't copy and paste from Geany (and SciTE?) in Wayland with GTK 3.24.35

2023-01-14 Thread Alexander Browne
Public bug reported:

With GTK 3.24.35, when running under Wayland, it's not possible to copy
and paste from Geany. (Others report the same issue with SciTE, which
also uses the Scintilla editor.)

The Geany upsteam bug isolated the issue to a GTK change
(https://github.com/geany/geany/issues/3345#issuecomment-1360370992).

The GTK bug (https://gitlab.gnome.org/GNOME/gtk/-/issues/5397) was
resolved
(https://gitlab.gnome.org/GNOME/gtk/-/commit/eca445672a48ac4a870790efa63339f8d974c2fd)
and the fix is in GTK 3.24.36.

I installed the libgtk-3-0_3.24.36-1_amd64.deb and
libgtk-3-common_3.24.36-1_all.deb packages from Debian on a Lunar test
system and this did resolve the issue.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: libgtk-3-0 3.24.35-3ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.24.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan 14 14:22:01 2023
InstallationDate: Installed on 2022-12-28 (17 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221228)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gtk+3.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug lunar uec-images wayland-session

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

Title:
  Can't copy and paste from Geany (and SciTE?) in Wayland with GTK
  3.24.35

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2002886/+subscriptions


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

[Bug 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently

2022-08-28 Thread Alexander E. Patrakov
Also note that there is no requirement to have Secure Boot enabled in
Cyber Essentials.

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

Title:
  43: New Device Security feature is confusing and unhelpful currently

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


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

[Bug 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently

2022-08-28 Thread Alexander E. Patrakov
@billdietrich444

Note: my comment is a trolling attempt, and hopefully an obvious one due
to the choice of an obviously unimplementable-in-a-useful-way standard.
Please take only 10% seriously.

It may be a good idea to stop talking about pure security according to
our own set of criteria (because it's up to discussion what's good
enough) and start talking about compliance to recognized standards. We
can start with the UK standard named Cyber Essentials, which is required
for all organizations that need to deal with the UK government. The
standard itself is available at https://www.ncsc.gov.uk/files/Cyber-
Essentials-Requirements-for-Infrastructure-v3-0-January-2022.pdf

It has the following testable requirements related to technical
controls:

* Firewalls - we can check that the firewall is installed and configured
to "block unauthenticated inbound connections by default".

* Secure configuration - this also includes removing unneeded or unused
services (and this means that it is forbidden to run the SSH server
unless there is a documented business need) and uninstalling unused
software. So we might want to display when each piece of software was
last used so that to ease the audit. Another testable requirement is
that any auto-run feature is disabled or configured to "ask". And also
there are some checkable requirements related to device unlocking.

* User access control - we could list administrative accounts. Also, if
a fingerprint reader is detected, or another form of 2FA is available,
we can list all all non-enrolled accounts as non-compliant. We can also
check if the password quality requirements are implemented and the
mandatory unsuccessful login throttling (or lock-out) policy is enforced
by PAM.

* Malware protection - with specific requirements, related to on-access
scanning of all files (including those on network shares, so sorry,
ClamAV is not compliant) and web pages. This was the reason I had to
tell one of my clients that they have to stop using Linux or stop
dealing with the UK government.

* Security update management - we can check Ubuntu-specific settings
related to the freshness of the database, whether a reboot is needed for
something to apply (e.g. are there running copies of deleted and
replaced binaries, or do they use deleted libraries), and whether the
updates are configured to install automatically.

* Backups - we can test whether they configured through known backup
applications.

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

Title:
  43: New Device Security feature is confusing and unhelpful currently

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


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

[Bug 1879566] Re: gnome-control-center crashed with SIGSEGV in gdk_display_get_event()

2021-11-10 Thread Alexander Heavens
*** This bug is a duplicate of bug 1873075 ***
https://bugs.launchpad.net/bugs/1873075

I was also affected by this.  From journalctl it looked driver-related.
Updated drivers, logged in and out seemed to fix it.

Will update if it happens again.

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

Title:
  gnome-control-center crashed with SIGSEGV in gdk_display_get_event()

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


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

[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

2021-07-01 Thread Geoff Alexander
I'm seeing the same symptoms, screen scaling 125% gives 200%, when
accessing a Ubuntu 20.04 VMware system via xdrp from Windows 10.  My
graphics driver is

root@geoff-ubuntu-2004:~# lshw -c video
  *-display 
   description: VGA compatible controller
   product: SVGA II Adapter
   vendor: VMware
   physical id: f
   bus info: pci@:00:0f.0
   version: 00
   width: 32 bits
   clock: 33MHz
   capabilities: vga_controller bus_master cap_list rom
   configuration: driver=vmwgfx latency=64
   resources: irq:16 ioport:1070(size=16) memory:e800-efff 
memory:fe00-fe7f memory:c-d

-- 
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/1870736

Title:
  [nvidia] Screen scaling 125% gives 200%

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

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

[Bug 1928073] Re: Display settings don't persist across reboot / sleep

2021-05-12 Thread Alexander List
I stand corrected: fractional scaling on/off persists. The scale (100%)
does not, it jumps back to 200% and my Chrome windows that were on the
external screens are back on the internal display.

The latter was already reported as
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1927948

I am using Wayland yes, which I guess is default in 21.04.


Sorry for this off-topic comment, but I'm a bit frustrated:

What I'm also missing is instructions how to get things working nicely
in 21.04 with Wayland, this still looks like a massive WIP /
construction site. Don't get me wrong, ppl with external monitors and
HiDPI internal screen are probably a minority, so I appreciate not
everything can be fully tested by devs/QA before release.

I've tried to follow instructions here:

https://wiki.archlinux.org/title/HiDPI#Multiple_external_monitors

...but only some of them help. I would appreciate Ubuntu documentation
on how to get Chrome, Thunderbird, Skype, Signal Desktop, Telegram, ...
working nicely with this setup.

I will take some time to dig deeper and report appropriate bugs against
respective packages, if appropriate.

-- 
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/1928073

Title:
  Display settings don't persist across reboot / sleep

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

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

[Bug 1928073] [NEW] Display settings don't persist across reboot / sleep

2021-05-11 Thread Alexander List
Public bug reported:

My setup:

Dell XPS 13 7390 2-in-1, internal display (3840x2400)

First external monitor: Dell 24" running at 2560x1440 connected via 
USB-C/Thunderbolt
Second external monitor: same, connected to the first monitor via DP

Scale of the internal display set to 200%, fractional scaling on
Scale of the external displays set to 100%, fractional scaling on


What I expect:

Settings persist across reboot / sleep / resume.

What I observe:

Settings for external monitors are back to 200% scale, fractional
scaling off.

Looks like there's a problem detecting the external monitors/resolutions
in time.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.4-1ubuntu2
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue May 11 12:12:28 2021
DisplayManager: gdm3
InstallationDate: Installed on 2019-12-02 (525 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to hirsute on 2021-05-05 (5 days ago)

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


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

-- 
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/1928073

Title:
  Display settings don't persist across reboot / sleep

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

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

[Bug 1927948] Re: Windows switch monitor after resuming from sleep

2021-05-10 Thread Alexander List
I have a Dell XPS 13 7390 2-in-1 with two external monitors.

The first external monitor is connected via USB-C/Thunderbolt, the
second one via DP from the first external monitor.

-- 
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/1927948

Title:
  Windows switch monitor after resuming from sleep

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

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

[Bug 1927948] [NEW] Windows switch monitor after resuming from sleep

2021-05-10 Thread Alexander List
Public bug reported:

What I expect:

Window layout/positioning is identical after resume from sleep.

What I observe:

After resume from sleep, windows appear on a different monitor than
before.

I found this possibly relevant GNOME bug:

https://gitlab.gnome.org/GNOME/mutter/-/issues/1419

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: mutter 3.38.4-1ubuntu2
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon May 10 13:40:28 2021
InstallationDate: Installed on 2019-12-02 (524 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: mutter
UpgradeStatus: Upgraded to hirsute on 2021-05-05 (4 days ago)

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


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

-- 
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/1927948

Title:
  Windows switch monitor after resuming from sleep

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

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

[Bug 1926574] [NEW] Not possible to share windows in a video conference

2021-04-29 Thread Alexander Kallenbach
Public bug reported:

I don't know if it is the right package against which I opened the bug report.
Unfortunately, under the new Ubuntu version 21.04, it is not possible to share 
windows of many applications in videoconferences (due to Wayland?). This is a 
big problem considering that many in the current pandemic work in 
videoconferences on a daily basis.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: mutter (not installed)
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 29 09:53:28 2021
InstallationDate: Installed on 2021-02-09 (78 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: mutter
UpgradeStatus: Upgraded to hirsute on 2021-04-23 (5 days ago)

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


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

-- 
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/1926574

Title:
  Not possible to share windows in a video conference

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

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

[Bug 1925982] [NEW] GNOME Settings automatically closes on open.

2021-04-23 Thread Alexander Koskovich
Public bug reported:

Segfaults seemingly, I haven't changed any theme stuff and it worked on
a fresh install so I don't know what's causing this.

Also if it's helpful this doesn't seem to be an issue with Ubuntu itself
as it happened on Intel's Clear Linux so it appears to be GNOME.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-control-center 1:3.38.5-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 23 16:57:08 2021
InstallationDate: Installed on 2021-04-23 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RebootRequiredPkgs:
 linux-image-5.11.0-16-generic
 linux-base
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug hirsute

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

Title:
  GNOME Settings automatically closes on open.

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

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

[Bug 1918007] Re: This happens from time to time, gnome-shell creates large files in the var/crash directory.

2021-03-06 Thread Alexander
And here, too:
Section "InputClass"
Identifier "libinput touchscreen catchall"
MatchIsTouchscreen "on"
MatchDevicePath "/dev/input/event*"
Option "InvertY" "true"
Driver "libinput"
EndSection

-- 
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/1918007

Title:
  This happens from time to time, gnome-shell creates large files in the
  var/crash directory.

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

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

[Bug 1918007] Re: This happens from time to time, gnome-shell creates large files in the var/crash directory.

2021-03-06 Thread Alexander
It was added to the intel_vt blacklist to make the volume buttons work.
`blacklist intel_vbtn`

-- 
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/1918007

Title:
  This happens from time to time, gnome-shell creates large files in the
  var/crash directory.

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

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

[Bug 1918007] Re: This happens from time to time, gnome-shell creates large files in the var/crash directory.

2021-03-06 Thread Alexander
I did the same thing in Chrome Browser. 
The Chrome Browser does not select the text well and copies it.

-- 
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/1918007

Title:
  This happens from time to time, gnome-shell creates large files in the
  var/crash directory.

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

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

[Bug 1918007] Re: This happens from time to time, gnome-shell creates large files in the var/crash directory.

2021-03-06 Thread Alexander
This is a clean minimal installation. In addition, Yandex Browser was installed 
and the command was executed:
sudo apt-get install chrome-gnome-shell.

Installed extensions:

Desktop Icons
Block Caribou 36
Horizontal workspaces
Ubuntu AppIndicators
Ubuntu Dock
User Themes
Window List
Workspace Indicator

-- 
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/1918007

Title:
  This happens from time to time, gnome-shell creates large files in the
  var/crash directory.

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

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

[Bug 1918007] Re: This happens from time to time, gnome-shell creates large files in the var/crash directory.

2021-03-06 Thread Alexander
** Description changed:

- Now it seemed that my car would take off. The fan was spinning long and
- loud, and the three files are _usr_bin_gnome-shell. 1000*were created in
- the var/crash /directory.
+ Now it seemed that my car would take off. The fan was spinning long and loud, 
and the three files are _usr_bin_gnome-shell. 1000*were created in the 
var/crash/ directory.
+ But it seems to me that he is already used to it and does not get more.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
- Date: Sat Mar  6 17:21:30 2021
+ Date: Sat Mar 6 17:21:30 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-03-05 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
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/1918007

Title:
  This happens from time to time, gnome-shell creates large files in the
  var/crash directory.

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

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

[Bug 1917660] Re: This happens from time to time, gnome-shell creates large files in the var/crash/ directory.

2021-03-06 Thread Alexander
I had to make a new report: https://bugs.launchpad.net/ubuntu/+source
/gnome-shell/+bug/1918007

-- 
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/1917660

Title:
  This happens from time to time, gnome-shell creates large files in the
  var/crash/ directory.

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

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

[Bug 1918007] [NEW] This happens from time to time, gnome-shell creates large files in the var/crash directory.

2021-03-06 Thread Alexander
Public bug reported:

Now it seemed that my car would take off. The fan was spinning long and
loud, and the three files are _usr_bin_gnome-shell. 1000*were created in
the var/crash /directory.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar  6 17:21:30 2021
DisplayManager: gdm3
InstallationDate: Installed on 2021-03-05 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

-- 
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/1918007

Title:
  This happens from time to time, gnome-shell creates large files in the
  var/crash directory.

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

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

[Bug 1917660] Re: This happens from time to time, gnome-shell creates large files in the var/crash/ directory.

2021-03-06 Thread Alexander
Thank you, I temporarily lost my account and had to contact customer
support.

-- 
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/1917660

Title:
  This happens from time to time, gnome-shell creates large files in the
  var/crash/ directory.

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

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

[Bug 1917660] Re: This happens from time to time, gnome-shell creates large files in the var/crash/ directory.

2021-03-03 Thread Alexander
** Attachment removed: "monitors.xml.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917660/+attachment/5472220/+files/monitors.xml.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917660/+attachment/5472218/+files/ProcCpuinfoMinimal.txt

** Attachment removed: "ShellJournal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917660/+attachment/5472219/+files/ShellJournal.txt

** Attachment removed: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917660/+attachment/5472217/+files/GsettingsChanges.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917660/+attachment/5472216/+files/Dependencies.txt

-- 
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/1917660

Title:
  This happens from time to time, gnome-shell creates large files in the
  var/crash/ directory.

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

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

[Bug 1917660] Re: This happens from time to time, gnome-shell creates large files in the var/crash/ directory.

2021-03-03 Thread Alexander
** Description changed:

- Now it seemed that my device would take off. The fan was spinning for a
- long time and loudly, and three files _usr_bin_gnome-shell.1000*were
- created in the var/crash/ directory.
+ Теперь казалось, что мой аппарат взлетит. Вентилятор крутился долго и громко, 
а три файла _usr_bin_gnome-shell.1000*были созданы в каталоге var/crash/.
+ We'll probably be saying goodbye to ubuntu soon.
  
- ProblemType: Bug
+ 
+ ProblemType: Ошибка
  DistroRelease: Ubuntu 20.04
- Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
- ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
+ Пакет: gnome-shell 3.36.4 -1ubuntu1~20.04.2
+ ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-Общие сведения 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
- ApportVersion: 2.20.11-0ubuntu27.16
- Architecture: amd64
- CasperMD5CheckResult: skip
+ Аппортверсия: 2.20.11-0ubuntu27.16
+ Архитектура: amd64
+ CasperMD5CheckResult: пропустить
  CurrentDesktop: ubuntu:GNOME
- Date: Wed Mar  3 21:58:59 2021
+ Дата: СР 3 Марта 21:58:59 2021
  DisplayManager: gdm3
- InstallationDate: Installed on 2021-02-28 (3 days ago)
- InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
- ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
+ Дата установки: установлен на 2021-02-28 (3 дня назад)
+ InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - релиз amd64 (20200731)
+ Проценвирон:
+  Терм=xterm-256color
+  PATH=(пользовательский, без пользователя)
+  XDG_RUNTIMEDIR= < set > 
   LANG=ru_RU.UTF-8
-  SHELL=/bin/bash
- RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
+  SHELL= / bin / bash
+ RelatedPackageVersions: mutter-common 3.36.7+git20201123 -0.20.04.1
  SourcePackage: gnome-shell
- UpgradeStatus: No upgrade log present (probably fresh install)
+ UpgradeStatus: журнал обновления отсутствует (вероятно, новая установка)

-- 
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/1917660

Title:
  This happens from time to time, gnome-shell creates large files in the
  var/crash/ directory.

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

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

[Bug 1917660] [NEW] This happens from time to time, gnome-shell creates large files in the var/crash/ directory.

2021-03-03 Thread Alexander
Public bug reported:

Now it seemed that my device would take off. The fan was spinning for a
long time and loudly, and three files _usr_bin_gnome-shell.1000*were
created in the var/crash/ directory.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar  3 21:58:59 2021
DisplayManager: gdm3
InstallationDate: Installed on 2021-02-28 (3 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

-- 
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/1917660

Title:
  This happens from time to time, gnome-shell creates large files in the
  var/crash/ directory.

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

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

[Bug 1917629] [NEW] Nautilus doesn't work correctly for touch screens

2021-03-03 Thread Alexander
Public bug reported:

This error is not caused by additional software, it occurs in the file manager 
even before installing ubuntu in trial mode.
These are black pop-ups that block subsequent input of commands, and that 
remain on the screen for too long.
These windows are descriptions of functions or folders, for example: Downloads 
(window: "/home/user/Downloads").
The window (/home/user/Downloads) remains on the screen even when you touch to 
any other area of the screen.

In addition, you need to click on the folders several times to open them and 
this happens randomly, sometimes just one touch is enough to open any of the 
folders, but most often three or four times.
And so, it can't be used correctly on my device.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar  3 16:53:38 2021
InstallationDate: Installed on 2021-02-28 (3 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug focal

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

Title:
  Nautilus doesn't work correctly for touch screens

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

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

[Bug 588569] Re: Uses excessive memory on import

2021-02-20 Thread Alexander Kallenbach
Opened a bug report on Gnomes Gitlab:
https://gitlab.gnome.org/GNOME/shotwell/-/issues/323

** Bug watch added: gitlab.gnome.org/GNOME/shotwell/-/issues #323
   https://gitlab.gnome.org/GNOME/shotwell/-/issues/323

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

Title:
  Uses excessive memory on import

To manage notifications about this bug go to:
https://bugs.launchpad.net/shotwell/+bug/588569/+subscriptions

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

[Bug 588569] Re: Uses excessive memory on import

2021-02-20 Thread Alexander Kallenbach
More than ten years later, I still have the same problem. (Ubuntu 20.10;
Shotwell 0.30.10)). Shouldn't such a bug also be marked as a security
issue? Isn't such a memory overflow potentially dangerous?

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

Title:
  Uses excessive memory on import

To manage notifications about this bug go to:
https://bugs.launchpad.net/shotwell/+bug/588569/+subscriptions

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

[Bug 1904474] Re: Black/purple screen after booting Ubuntu

2020-11-24 Thread Rabensteiner Alexander
BTW now the screen also gets stuck as black-screen when I close my
laptop lid, wait some seconds and open it again.

And the functions keys to regulate screen brightness are working no more
(I also tried to change brightness with this tool
http://ubuntuhandbook.org/index.php/2017/05/install-brightness-
controller-utility-in-ubuntu-16-04-higher/ but it had no effect ...)

Could this be related to the above described issue?

Best
Alexander

-- 
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/1904474

Title:
  Black/purple screen after booting Ubuntu

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

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

[Bug 1904474] Re: Black/purple screen after booting Ubuntu

2020-11-24 Thread Rabensteiner Alexander
Thanks for the answer,

you can find the the requested file appended.

Best
Alexander

** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904474/+attachment/5437516/+files/lspci.txt

-- 
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/1904474

Title:
  Black/purple screen after booting Ubuntu

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

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

[Bug 427168] Re: usb keyboard settings (repeat rate and delay) reset on plugin

2020-11-20 Thread Alexander Adam
> I can confirm that toggling repeat keys off and on again fixes the
issue temporarily for the current session.

Also changing the repeat speed.

It would be nice if this toggling would be possible from CLI.
This way I wouldn't have to go in the settings every time my computer woke up 
from sleep.

-- 
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/427168

Title:
  usb keyboard settings (repeat rate and delay) reset on plugin

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

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

[Bug 1904474] Re: Black/purple screen after booting Ubuntu

2020-11-19 Thread Rabensteiner Alexander
Ok,

I booted, waited some minutes where the screen gets stuck black/purple,
powered off and booted to recovery mode to collect `journalctl -b-1`.
You can find the file appended.

Maybe my system is booting correctly but the X Windows System is not
able to load?

Best
Alexander

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904474/+attachment/5435977/+files/prevboot.txt

-- 
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/1904474

Title:
  Black/purple screen after booting Ubuntu

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

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

[Bug 1904474] Re: Black/purple screen after booting Ubuntu

2020-11-17 Thread Rabensteiner Alexander
Sorry, the BTW above was nonsense.

When trying to boot using `Advanced Options` in BIOS and choose Ubuntu
there, the screen shows

`
Loading Linux5.4.0-53-generic ...
Loading initial ramdisk
`

and gets stuck there.

The strange comes now: if I open the bootscript for Ubuntu in BIOS
removing one of the two spaces in the line `ro  nomodeset quiet splash`
or  `ro  nouveau.noaccel=1 quiet splash` (between ro and the other
stuff) works fine, boots like a charm.

I am really curious what is going on here :-)

-- 
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/1904474

Title:
  Black/purple screen after booting Ubuntu

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

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

[Bug 1904474] Re: Black/purple screen after booting Ubuntu

2020-11-17 Thread Rabensteiner Alexander
** Attachment added: "prevboot2.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904474/+attachment/5435258/+files/prevboot2.txt

-- 
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/1904474

Title:
  Black/purple screen after booting Ubuntu

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

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

[Bug 1904474] Re: Black/purple screen after booting Ubuntu

2020-11-17 Thread Rabensteiner Alexander
sorry appended file abve seems not to work.

** Attachment added: "prevboot1.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904474/+attachment/5435257/+files/prevboot1.txt

-- 
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/1904474

Title:
  Black/purple screen after booting Ubuntu

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

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

[Bug 1904474] Re: Black/purple screen after booting Ubuntu

2020-11-17 Thread Rabensteiner Alexander
Hi,

I have followed your suggestion and recorded the output of `journalctl
-b-1` to the files appended.

`prevboot1.text` is with

`GRUB_CMDLINE_LINUX_DEFAULT="nouveau.noaccel=1 quiet splash"`

and `prevboot2.txt` is with

`GRUB_CMDLINE_LINUX_DEFAULT="nomodeset quiet splash"`

in `/etc/default/grub`, which both fail to boot (or is X not loaded
properly?).

BTW I have found that my Ubuntu starts properly if I boot it with the
entry in `Advanced Options` in BIOS and choose it there; only using the
Ubuntu entry first displayed when BIOS pops up gets stucked in
black/purple screen.

Best
Alexander

** Attachment added: "prevboot"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904474/+attachment/5435256/+files/prevboot

-- 
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/1904474

Title:
  Black/purple screen after booting Ubuntu

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

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

[Bug 1904474] ProcEnviron.txt

2020-11-17 Thread Rabensteiner Alexander
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1904474/+attachment/5435255/+files/ProcEnviron.txt

-- 
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/1904474

Title:
  Black/purple screen after booting Ubuntu

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

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

[Bug 1904474] ProcCpuinfoMinimal.txt

2020-11-17 Thread Rabensteiner Alexander
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1904474/+attachment/5435254/+files/ProcCpuinfoMinimal.txt

-- 
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/1904474

Title:
  Black/purple screen after booting Ubuntu

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

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

[Bug 1904474] GsettingsChanges.txt

2020-11-17 Thread Rabensteiner Alexander
apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1904474/+attachment/5435253/+files/GsettingsChanges.txt

-- 
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/1904474

Title:
  Black/purple screen after booting Ubuntu

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

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

[Bug 1904474] Re: Black/purple screen after booting Ubuntu

2020-11-17 Thread Rabensteiner Alexander
apport information

** Tags added: apport-collected

** Description changed:

  Hi,
  
  I am failing to boot into a freshly installed Ubuntu 18.04.5 LTS on my
  ThinkPad-T460. When choosing the right bootloader in BIOS I get a dark
  screen, Ubuntu is not booting (also after 15mins of waiting ...).
  
  I first thought my issue would be a *Black/purple screen after you boot
  Ubuntu for the first time* like over here:
  https://askubuntu.com/questions/162075/my-computer-boots-to-a-black-
  screen-what-options-do-i-have-to-fix-it
  
  So I added ```ǹomodeset``` in the script executed before booting Ubuntu.
  Interestingly I was able to boot and then made this change persistent by
  updating the bootloader. I tried some more times to boot and suddenly it
  stopped working properly (with same blackscreen as before). I also took
  a look to the bootscript, ```ǹomodeset``` was present there.
  
  Then I played around with some other obscure suggestions like adding
  ```nouveau.noaccel=1``` instead of ```nomodeset``` and replace ```qiuiet
  splash``` by ```noapic noacpi nosplash inqpoll```, but nothing gave me a
  soultion which did not get stuck with black screen of death after some
  reboots.
  
  I am a little bit clueless at the moment, so I have appended the uncompressed 
logs in ```/var/log```, captured like in 
https://wiki.ubuntu.com/DebuggingKernelBoot .
  The files appended are from a boot that got stuck, I have killed my laptop 
after 10mins of nothing happening.
  
  Btw. I have a dual boot with Windows 10, but I do not know if this is
  relevant for this issue.
  
  Best
  Alexander
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.20
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2020-11-16 (1 days ago)
+ InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
+ Package: gnome-shell 3.28.4-0ubuntu18.04.3
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-53.59~18.04.1-generic 5.4.65
+ Tags:  bionic
+ Uname: Linux 5.4.0-53-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1904474/+attachment/5435252/+files/Dependencies.txt

-- 
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/1904474

Title:
  Black/purple screen after booting Ubuntu

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

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

[Bug 427168] Re: usb keyboard settings (repeat rate and delay) reset on plugin

2020-11-11 Thread Alexander Adam
Bug is still happening on Ubuntu 20.04.1 LTS.
I'm using an external Apple Alu Keyboard.
The interesting thing is, that repeat rate and delay are correct for the 
internal keyboard of the notebook but they are wrong for the plugged in 
keyboard.

If I go into settings and set it again it is correct for this session.
But it will be reset on the next time.

-- 
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/427168

Title:
  usb keyboard settings (repeat rate and delay) reset on plugin

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

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

[Bug 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS

2020-10-22 Thread Tyler Alexander Driggers
** Changed in: mutter (Ubuntu Bionic)
 Assignee: Daniel van Vugt (vanvugt) => Tyler Alexander Driggers (exderia)

** Changed in: mutter (Ubuntu Bionic)
 Assignee: Tyler Alexander Driggers (exderia) => (unassigned)

-- 
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/1763892

Title:
  144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1763892/+subscriptions

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

[Bug 1895062] [NEW] Regression: text scaling factor lost for GNOME Shell when logging out

2020-09-09 Thread Alexander Browne
Public bug reported:

As of a few weeks ago or so, GNOME Shell loses the text scaling factor
(it's set back to 1) when logging out and logging back in again. It is
preserved for other programs, just not the shell (top bar, menus, dash).
Setting it to another value and then back to the desired value changes
it until the next log out. I tried with a new user account and a second
machine, and I see the same thing.

Steps to reproduce:

1. Set a text scaling factor. (Something larger is easier to notice the change 
for.)
$ gsettings set org.gnome.desktop.interface text-scaling-factor 1.5

2. Notice apps and the shell have larger fonts now.

3. Log out and log back in (or restart).

4. Notice now that the top bar and other parts of the Shell are back to
a scale factor of 1, while other apps still have larger fonts.

5. Change the text scaling factor to something else (like 1) and then
back to the desired number.

$ gsettings set org.gnome.desktop.interface text-scaling-factor 1
$ gsettings set org.gnome.desktop.interface text-scaling-factor 1.5

6. Now the Shell does have large fonts, until step 3 is repeated.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep  9 17:10:02 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-04-01 (160 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

-- 
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/1895062

Title:
  Regression: text scaling factor lost for GNOME Shell when logging out

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

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

[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%

2020-06-08 Thread Alexander Bolshakov
As for me this advertised feature of 20.04 was the main factor to
install this OS on my hardware, because previous 3 years the lack of
this feature prevented me from using Ubuntu.

Sadly, this bug affects me too - I am using Nvidia RTX 2070 Super
together with Asrock X570 Taichi and Ryzen 3600.

-- 
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/1870736

Title:
  [nvidia] Screen scaling 125% gives 200%

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

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

[Bug 1792085] Re: Regression: MTP not working/very slow

2020-05-23 Thread Alexander Kassai
I have the same issue, and recommend those who haven't tried it out yet,
to look at post #10 (
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1792085/comments/10
) and use this application in the meantime. It works reliably for me.

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

Title:
  Regression: MTP not working/very slow

To manage notifications about this bug go to:
https://bugs.launchpad.net/libmtp/+bug/1792085/+subscriptions

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

[Bug 1872201] [NEW] Gnome 3 dock "restarts" every 35 (or so) seconds. Causing massive IO overhead (text boxes pause, game fps drops).

2020-04-11 Thread Alexander Göransson
Public bug reported:

Added some gnome extensions, but this was always present. Maybe the
multi monitor setup is at fault?

Attached output is from running 'sudo strace -p' on gnome-shell. The
whole FUTEX part in the middle is only observable during one of these
"stutters". The parts before and after is just to show what "normally"
is going on. I have no idea what any of this means. I hope this is
somewhat useful.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: mutter 3.34.3-1ubuntu1~19.10.1
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 11 15:48:33 2020
InstallationDate: Installed on 2020-03-22 (20 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan

** Attachment added: "Output from strace during a "stutter"."
   
https://bugs.launchpad.net/bugs/1872201/+attachment/5351910/+files/strace_gnome-shell.txt

-- 
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/1872201

Title:
  Gnome 3 dock "restarts" every 35 (or so) seconds. Causing massive IO
  overhead (text boxes pause, game fps drops).

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

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

[Bug 1865283] Re: gnome calendar icon missing Ubuntu 20.04

2020-02-29 Thread Alexander Vinbæk Strand
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 29 14:34:01 2020
Dependencies:
 accountsservice 0.6.55-0ubuntu10
 acl 2.2.53-5ubuntu1
 adduser 3.118ubuntu1
 adwaita-icon-theme 3.34.0-1ubuntu1
 apg 2.2.3.dfsg.1-5
 apport 2.20.11-0ubuntu18
 apport-symptoms 0.22
 apt 1.9.10
 apt-utils 1.9.10
 aptdaemon 1.1.1+bzr982-0ubuntu31
 aptdaemon-data 1.1.1+bzr982-0ubuntu31
 aspell 0.60.8-1
 aspell-en 2018.04.16-0-1
 at-spi2-core 2.35.1-1
 avahi-daemon 0.7-4ubuntu6
 avahi-utils 0.7-4ubuntu6
 base-files 11ubuntu2
 bash 5.0-6ubuntu1
 bash-completion 1:2.10-1ubuntu1
 bind9-host 1:9.11.14+dfsg-3ubuntu1
 bluez 5.53-0ubuntu1
 bolt 0.8-4
 bsdmainutils 11.1.2ubuntu2
 bsdutils 1:2.34-0.1ubuntu7
 bubblewrap 0.4.0-1ubuntu3
 bzip2 1.0.8-2
 ca-certificates 20190110
 cheese-common 3.34.0-1
 colord 1.4.4-1ubuntu2
 colord-data 1.4.4-1ubuntu2
 coreutils 8.30-3ubuntu2
 cpp 4:9.2.1-3.1ubuntu1
 cpp-9 9.2.1-30ubuntu1
 cracklib-runtime 2.9.6-3.1ubuntu1
 crda 3.18-1build1
 cups-pk-helper 0.2.6-1ubuntu3
 dbus 1.12.16-2ubuntu2
 dbus-user-session 1.12.16-2ubuntu2
 dbus-x11 1.12.16-2ubuntu2
 dconf-cli 0.35.1-1
 dconf-gsettings-backend 0.35.1-1
 dconf-service 0.35.1-1
 debconf 1.5.73
 debconf-i18n 1.5.73
 debianutils 4.9.1
 desktop-file-utils 0.24-1ubuntu1
 dictionaries-common 1.28.1
 distro-info-data 0.43ubuntu1
 dmsetup 2:1.02.167-1ubuntu1
 dns-root-data 2019052802
 dnsmasq-base 2.80-1.1ubuntu1
 dpkg 1.19.7ubuntu2
 emacsen-common 3.0.4
 enchant-2 2.2.7+repack1-1
 evolution-data-server 3.34.3-2
 evolution-data-server-common 3.34.3-2
 file 1:5.38-4
 fontconfig 2.13.1-2ubuntu2
 fontconfig-config 2.13.1-2ubuntu2
 fonts-dejavu-core 2.37-1
 fprintd 1.90.1-1
 gcc-10-base 10-20200222-1ubuntu1
 gcc-9-base 9.2.1-30ubuntu1
 gcr 3.34.0-1ubuntu1
 gdm3 3.34.1-1ubuntu1
 geoclue-2.0 2.5.6-0ubuntu1
 geoip-database 20191224-2
 gettext-base 0.19.8.1-10
 gir1.2-accountsservice-1.0 0.6.55-0ubuntu10
 gir1.2-atk-1.0 2.35.1-1ubuntu1
 gir1.2-atspi-2.0 2.35.1-1
 gir1.2-freedesktop 1.63.2-1
 gir1.2-gck-1 3.34.0-1ubuntu1
 gir1.2-gcr-3 3.34.0-1ubuntu1
 gir1.2-gdesktopenums-3.0 3.35.91-0ubuntu1
 gir1.2-gdkpixbuf-2.0 2.40.0+dfsg-2
 gir1.2-gdm-1.0 3.34.1-1ubuntu1
 gir1.2-geoclue-2.0 2.5.6-0ubuntu1
 gir1.2-glib-2.0 1.63.2-1
 gir1.2-gnomebluetooth-1.0 3.34.0-1
 gir1.2-gnomedesktop-3.0 3.34.2-2ubuntu1
 gir1.2-gtk-3.0 3.24.13-1ubuntu1
 gir1.2-gweather-3.0 3.34.0-1
 gir1.2-ibus-1.0 1.5.21-5ubuntu1
 gir1.2-json-1.0 1.4.4-2ubuntu1
 gir1.2-mutter-5 3.34.3-1ubuntu1
 gir1.2-nm-1.0 1.22.8-1ubuntu1
 gir1.2-nma-1.0 1.8.24-1ubuntu2
 gir1.2-notify-0.7 0.7.8-1ubuntu4
 gir1.2-packagekitglib-1.0 1.1.13-2build1
 gir1.2-pango-1.0 1.44.7-1ubuntu3
 gir1.2-polkit-1.0 0.105-26ubuntu1
 gir1.2-rsvg-2.0 2.46.4-1ubuntu1
 gir1.2-secret-1 0.19.1-1build2
 gir1.2-soup-2.4 2.69.90-1
 gir1.2-upowerglib-1.0 0.99.11-1build2
 gir1.2-vte-2.91 0.59.91-0ubuntu1
 gjs 1.58.1-2ubuntu2
 gkbd-capplet 3.26.1-1
 glib-networking 2.63.91-1ubuntu1
 glib-networking-common 2.63.91-1ubuntu1
 glib-networking-services 2.63.91-1ubuntu1
 gnome-control-center 1:3.35.91-0ubuntu1
 gnome-control-center-data 1:3.35.91-0ubuntu1
 gnome-control-center-faces 1:3.35.91-0ubuntu1
 gnome-desktop3-data 3.34.2-2ubuntu1
 gnome-keyring 3.35.90-1ubuntu1
 gnome-keyring-pkcs11 3.35.90-1ubuntu1
 gnome-menus 3.32.0-1ubuntu1
 gnome-online-accounts 3.35.90-1ubuntu1
 gnome-session-bin 3.35.3-1ubuntu2
 gnome-session-common 3.35.3-1ubuntu2
 gnome-settings-daemon 3.34.1-1ubuntu2
 gnome-settings-daemon-common 3.34.1-1ubuntu2
 gnome-shell 3.34.3-1ubuntu1
 gnome-shell-common 3.34.3-1ubuntu1
 gnome-startup-applications 3.35.3-1ubuntu2
 gnome-user-docs 3.34.0-2ubuntu1
 gpgv 2.2.17-3ubuntu1
 groff-base 1.22.4-4
 gsettings-desktop-schemas 3.35.91-0ubuntu1
 gstreamer1.0-clutter-3.0 3.0.27-1
 gstreamer1.0-gl 1.16.2-2ubuntu4
 gstreamer1.0-plugins-base 1.16.2-2ubuntu4
 gstreamer1.0-plugins-good 1.16.2-1ubuntu1
 gstreamer1.0-pulseaudio 1.16.2-1ubuntu1
 gstreamer1.0-x 1.16.2-2ubuntu4
 gtk-update-icon-cache 3.24.13-1ubuntu1
 hicolor-icon-theme 0.17-2
 humanity-icon-theme 0.6.15
 hunspell-en-us 1:2018.04.16-1
 ibus 1.5.21-5ubuntu1
 ibus-data 1.5.21-5ubuntu1
 ibus-gtk 1.5.21-5ubuntu1
 ibus-gtk3 1.5.21-5ubuntu1
 iio-sensor-proxy 2.8-1
 im-config 0.43-1ubuntu3
 init-system-helpers 1.57
 ippusbxd 1.34-2ubuntu1
 iptables 1.8.4-3ubuntu1
 iso-codes 4.4-1
 iw 5.4-1
 keyboard-configuration 1.194ubuntu2
 kmod 27-1ubuntu1
 krb5-locales 1.17-6ubuntu4
 language-selector-common 0.202
 language-selector-gnome 0.202
 libaa1 1.4p5-46
 libaccountsservice0 0.6.55-0ubuntu10
 libacl1 2.2.53-5ubuntu1
 libapparmor1 2.13.3-7ubuntu2
 libappindicator3-1 12.10.1+18.04.20180322.1-0ubuntu5
 libappstream4 0.12.10-1
 libapt-pkg5.90 1.9.10
 libarchive13 3.4.0-1build1
 libargon2-1 0~20171227-0.2
 libasn1-8-heimdal 7.7.0+dfsg-1
 libasound2 1.2.1.2-2ubuntu2
 libasound2-data 1.2.1.2-2ubuntu2
 libasound2-plugins 1.2.1-1ubuntu1
 libaspell15 0.60.8-1
 libassuan0 2.5.3-7ubuntu2
 libasyncns0 0.8-6
 libatk-bridge2.0-0 2.34.1-2ubuntu1
 libatk1.0-0 

[Bug 1865283] Re: gnome calendar icon missing Ubuntu 20.04

2020-02-29 Thread Alexander Vinbæk Strand
alexstrand7@alexstrand7-vmware:~$ lsb_release -a && uname -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Focal Fossa (development branch)
Release:20.04
Codename:   focal
Linux alexstrand7-vmware 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux
alexstrand7@alexstrand7-vmware:~$ gnome-calendar --version
gnome-calendar: Version 3.35.2

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

Title:
  gnome calendar icon missing Ubuntu 20.04

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

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

[Bug 1865283] [NEW] gnome calendar icon missing Ubuntu 20.04

2020-02-29 Thread Alexander Vinbæk Strand
Public bug reported:

see screenshot

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


** Tags: focal

** Attachment added: "Ubuntu 20.04-2020-02-29-14-23-28.png"
   
https://bugs.launchpad.net/bugs/1865283/+attachment/5332199/+files/Ubuntu%2020.04-2020-02-29-14-23-28.png

** Tags added: focal

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

Title:
  gnome calendar icon missing Ubuntu 20.04

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

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

[Bug 1652618] Re: Impossible to unlock the screen when using non-English language

2020-01-24 Thread Alexander Vlasov
@daniel, please reopen, I still have no permission to do that

-- 
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/1652618

Title:
  Impossible to unlock the screen when using non-English language

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

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

[Bug 1652618] Re: Impossible to unlock the screen when using non-English language

2020-01-24 Thread Alexander Vlasov
This bug is reproducible on 19.10

-- 
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/1652618

Title:
  Impossible to unlock the screen when using non-English language

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

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

[Bug 1852018] Re: Audio Stops Playing Briefly When Emptying Trash

2019-12-27 Thread Alexander Pistoletov
> A secondary problem, which might be an unfixable design choice, is
that it sounds like PulseAudio clients can block the sound of the entire
server.

If that's unfixable, then perhaps it makes sense to remove this behavior
from clients which are bundled with Ubuntu, such as Nautilus. They don't
have to block the sound of the entire server, right?

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

Title:
  Audio Stops Playing Briefly When Emptying Trash

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

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

[Bug 1852018] Re: Audio Stops Playing Briefly When Emptying Trash

2019-12-27 Thread Alexander Pistoletov
Does the same thing happen if you try to shift+delete something in Nautilus? 
(this also causes a dialog window to pop up)  
I have a very similar issue if I play music in foobar2000 through Wine using 
its "wasapi shared" output method and do that - the sound stutters for a brief 
amount of time.

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

Title:
  Audio Stops Playing Briefly When Emptying Trash

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

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

[Bug 1795021] Re: gsd-xsettings high memory usage

2019-09-12 Thread Alexander Adam
…and could this issue be related to this one?
https://bugzilla.redhat.com/show_bug.cgi?id=1668808

-- 
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/1795021

Title:
  gsd-xsettings high memory usage

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

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

[Bug 1795021] Re: gsd-xsettings high memory usage

2019-09-12 Thread Alexander Adam
I'm having the same problem on Ubuntu 18.04.3 LTS.
gsd-xsettings is the reason my system is even fully filling the SWAP. Is there 
any possibility to debug this?

** Bug watch added: Red Hat Bugzilla #1668808
   https://bugzilla.redhat.com/show_bug.cgi?id=1668808

-- 
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/1795021

Title:
  gsd-xsettings high memory usage

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

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

[Bug 1841826] Re: Going to sleep instead of logging in while lid closed & external display

2019-09-02 Thread Alexander Bischoff
That might be but that doesn't explain why the system goes to the
"desktop" straight after pressing the power-button w/o identification.

I disabled "energy mode if laptop-lid is closed" in "Tweak" (for gnome),
no improvement.

If I let open the lid for 2...3 cm it workes, but then the login-screen
is always in the built-in laptop-screen.

-- 
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/1841826

Title:
  Going to sleep instead of logging in while lid closed & external
  display

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

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

[Bug 1841826] [NEW] Going to sleep instead of logging in while lid closed & external display

2019-08-28 Thread Alexander Bischoff
Public bug reported:

I have the above described problem, which seems to be very similar to
bug #1716160

- laptop is in docking station and 2 monitors are connected (HDMI, DVI)

- If the lid is closed and I boot the laptop I can input my credentials
in the login screen and after hitting ENTER the laptop goes to sleep

- If I then press the power button of the docking station the laptop
wakes up and goes straight to the ubuntu environment w/o any user
identification

The device is a Lenovo T420 with classic docking station. Ubuntu 18.04.3
LTS. Internal graphics Intel integrated grafics and dedicated Nvidia
Quadro NVS 4200M with propriety driver 390.116. Behavior independent of
the graphics used.

I do not know what to do now since the latest state of bug #1716160 is
"fix released" and so I guess it should be part of the ubuntu version I
use?

Thank you very much.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.4-0ubuntu18.04.1
ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
Uname: Linux 5.0.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 28 20:10:15 2019
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'app-picker-view' b'uint32 1'
 b'org.gnome.shell' b'favorite-apps' redacted by apport
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.interface' b'show-battery-percentage' b'true'
 b'org.gnome.desktop.interface' b'clock-show-date' b'true'
InstallationDate: Installed on 2019-08-13 (14 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

-- 
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/1841826

Title:
  Going to sleep instead of logging in while lid closed & external
  display

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

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

[Bug 1716160] Re: System goes to sleep with external monitor and lid closed after login

2019-08-26 Thread Alexander Bischoff
I am very sorry coz after studying many webpages I end up here since
this pages covers my problem most. If it was wrong posting my problem
here just give me a hint and delete my post.

I have the above described problem:

- laptop is in docking station and 2 monitors are connected (HDMI, DVI)

- If the lid is closed and I boot the laptop I can input my credentials
in the login screen and after hitting ENTER the laptop goes to sleep

- If I then press the power button of the docking station the laptop
wakes up and goes straight to the ubuntu environment w/o any user
identification

The device is a Lenovo T420 with classic docking station. Ubuntu 18.04.3
LTS. Internal graphics Intel integrated grafics and dedicated Nvidia
Quadro NVS 4200M with propriety driver 390.116. Behavior independent of
the graphics used.

I do not know what to do now since the latest state is "fix released"
and so I guess it should be part of the ubuntu version I use?

Thank you very much.

-- 
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/1716160

Title:
  System goes to sleep with external monitor and lid closed after login

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1716160/+subscriptions

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

[Bug 1652618] Re: Impossible to unlock the screen when using non-English language

2019-07-22 Thread Alexander Vlasov
Please reopen the bug and change status to Confirmed

-- 
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/1652618

Title:
  Impossible to unlock the screen when using non-English language

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

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

[Bug 1652618] Re: Impossible to unlock the screen when using non-English language

2019-07-22 Thread Alexander Vlasov
I still can reproduce it on latest version of Ubuntu - 19.04

-- 
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/1652618

Title:
  Impossible to unlock the screen when using non-English language

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

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

[Bug 1758512] Re: No virtual terminals (CTRL+ALT+F?) when no user logged in; erratic behaviour when user logged in.

2019-07-02 Thread Alexander Lit
The same problem 
Dell Vostro 5648, i5-7200U

Even more, after pressing any time CTR-ALT-F# 
Gnome desktop process terminates and i've got 
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO 
underrun
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO 
underrun

-- 
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/1758512

Title:
  No virtual terminals (CTRL+ALT+F?) when no user logged in; erratic
  behaviour when user logged in.

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

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

[Bug 1819128] [NEW] Can't open exFAT-USB-Stick

2019-03-08 Thread Alexander Kallenbach
Public bug reported:

I've got an exFAT-USB-Stick. If I'm plugging the stick it seems to be
mounted (the mounted symbol appears in nautlius). But I'm not able to
open the stick to open files or for writing new files to the stick. Just
if I'm formatting the stick with GNOME Disks and mounting it directly
after formatting about GNOME Disks I can open the stick. After
unmounting the same problem appears.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: nautilus 1:3.26.4-0ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar  8 10:00:28 2019
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'206'
 b'org.gnome.nautilus.window-state' b'geometry' b"'856x481+26+23'"
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
InstallationDate: Installed on 2018-11-30 (97 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


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

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

Title:
  Can't open exFAT-USB-Stick

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

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

[Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)

2019-02-03 Thread Alexander Mashin
Yes, I think it should be backported.

I also noticed that keyboard layout indicator is cleared not only after
suspension but more often.

-- 
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/1812266

Title:
  Keyboard layout indicator does not indicate current layout (18.04
  Bionic beaver)

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

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

[Bug 1652618] Re: Impossible to unlock the screen when using non-English language

2019-01-31 Thread Alexander Vlasov
Please reopen the bug

-- 
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/1652618

Title:
  Impossible to unlock the screen when using non-English language

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

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

[Bug 1652618] Re: Impossible to unlock the screen when using non-English language

2019-01-31 Thread Alexander Vlasov
This is not 16.10 bug, it's reproducible on all latest Ubuntu versions
including 18.10

-- 
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/1652618

Title:
  Impossible to unlock the screen when using non-English language

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

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

Re: [Bug 1811599] Re: When booting, the computer hangs at a purple screen and no login prompt is ever displayed [Apple Macbook 2, 1 - Intel GMA 950]

2019-01-22 Thread Alexander A Theiler
Hey Daniel,

The other thing I noticed in the the boot logs are a seemingly futile
loop:

Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]:
gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in
'/usr/share/gdm/greeter/autostart'
Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]:
gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in
'/var/lib/gdm3/.config/autostart'
Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]:
gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in
'/usr/share/gdm/greeter/gnome/autostart'
Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]:
gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in
'/usr/local/share/gnome/autostart'
Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]:
gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in
'/usr/share/gnome/autostart'
Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]:
gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in
'/etc/xdg/autostart'
Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]:
gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in
'/var/lib/gdm3/.local/share/applications'
Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]:
gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in
'/usr/share/gdm/greeter/applications'
Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]:
gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in
'/usr/local/share/applications'
Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]:
gnome-session-binary[1430]: DEBUG(+): GsmUtil: Looking in
'/usr/share/applications'
Jan 22 11:38:36 HackBook /usr/lib/gdm3/gdm-wayland-session[1419]:
gnome-session-binary[1430]: DEBUG(+): GsmUtil: found in XDG dirs:
'/etc/xdg/autostart/org.gnome.SettingsDaemon.Housekeeping.desktop'


This appears first at 11:38:36 in the first boot log, and then repeats
over and over and over until the machine turns off.  The same loop
appears in longhangprevboot2.txt and starts at 12:21:55.  What is the
machine trying to do here?  I suspect that this is what's happening in
the background when the computer hangs, and it may even describe why
it does not record the whole boot sequence for the 20 minutes after it
hangs.  Thoughts?


I have not used Ubuntu 16.04, nor Lubuntu 18.04.1.  I'll download
Lubuntu and see how that works out.  But, I am a little concerned
about getting it to install correctly.  Whenever I try to get the
computer to recognize the CD image and to boot from it, I have to spam
"1" and "Enter" over and over and sometimes it works.  Have you run
into this issue before?


Alex


On Tue, Jan 22, 2019 at 8:05 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> You're right - those logs are apparently from short boots.
>
> longhangprevboot.txt lasted less than 2 minutes and only 2 seconds
> between GLSL errors and the machine beginning to shutdown.
>
> longhangprevboot2.txt lasted 2 minutes and again was only 4 seconds
> between GLSL errors and the machine beginning shutting down.
>
> Maybe that's a hint at a bigger problem if the system clock is running
> slower than reality..?
>
> Do older releases like Ubuntu 16.04 work on it? How about Lubuntu
> 18.04.1?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1811599
>
> Title:
>   When booting, the computer hangs at a purple screen and no login
>   prompt is ever displayed [Apple Macbook 2,1 - Intel GMA 950]
>
> Status in gdm3 package in Ubuntu:
>   Incomplete
> Status in mutter package in Ubuntu:
>   Incomplete
>
> Bug description:
>   After a fresh install of Ubuntu 18.04.1, on its first boot, the
>   computer hung at a purple screen.  No login prompt was ever displayed.
>   After holding the power button, the computer boot into Ubuntu without
>   difficulty.  I applied the workaround described in bug 1727356,
>   uncommenting WaylandEnable=False and rebooted the machine, but it
>   again hung at the purple screen.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gdm3 3.28.3-0ubuntu18.04.3
>   ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
>   Uname: Linux 4.15.0-43-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.5
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Jan 13 10:59:26 2019
>   InstallationDate: Installed on 2019-01-11 (2 days ago)
>   InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
> (20180725)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gdm3
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   mtime.conffile..e

Re: [Bug 1811599] Re: When booting, the computer hangs at a purple screen and no login prompt is ever displayed [Apple Macbook 2, 1 - Intel GMA 950]

2019-01-22 Thread Alexander A Theiler
Hey Daniel,

I've recorded two long hangs for you and your team to analyze.

Please find attached longhangprevboot.txt and longhangprevboot2.txt.

The only difference between the two is that longhangprevboot.txt followed
the following timeline:
normal mode -> restart to long hang -> restart to recovery mode and record
previous boot

Whereas, longhangprevboot2.txt followed the following:
normal mode -> restart to long hang -> restart to normal mode and record
previous boot

I let both of these boots hang for about 20 minutes before restarting the
machine.  Strangely, both logs don't seem to reflect that.  Unless they do,
and I simply didn't interpret the data correctly.  Ideas?

Thanks

Alex


On Mon, Jan 21, 2019 at 9:00 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> Yes please for a new log.
>
> This bug is almost certainly fixable. We just need a complete log, and
> then a lot of patience to wait for some upstream developer to get around
> to figuring it out.
>
> If you can't wait and want to use the machine now then Lubuntu might be a
> better option:
>
> http://cdimage.ubuntu.com/lubuntu/releases/18.04/release/lubuntu-18.04.1-desktop-amd64.iso
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1811599
>
> Title:
>   When booting, the computer hangs at a purple screen and no login
>   prompt is ever displayed [Apple Macbook 2,1 - Intel GMA 950]
>
> Status in gdm3 package in Ubuntu:
>   Incomplete
> Status in mutter package in Ubuntu:
>   Incomplete
>
> Bug description:
>   After a fresh install of Ubuntu 18.04.1, on its first boot, the
>   computer hung at a purple screen.  No login prompt was ever displayed.
>   After holding the power button, the computer boot into Ubuntu without
>   difficulty.  I applied the workaround described in bug 1727356,
>   uncommenting WaylandEnable=False and rebooted the machine, but it
>   again hung at the purple screen.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gdm3 3.28.3-0ubuntu18.04.3
>   ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
>   Uname: Linux 4.15.0-43-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.5
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Jan 13 10:59:26 2019
>   InstallationDate: Installed on 2019-01-11 (2 days ago)
>   InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
> (20180725)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gdm3
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   mtime.conffile..etc.gdm3.custom.conf: 2019-01-11T10:47:37.073441
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1811599/+subscriptions
>


-- 
Alexander A Theiler, MHS, MS, PA-C
CAQ in Emergency Medicine


** Attachment added: "longhangprevboot.txt"
   
https://bugs.launchpad.net/bugs/1811599/+attachment/5231528/+files/longhangprevboot.txt

** Attachment added: "longhangprevboot2.txt"
   
https://bugs.launchpad.net/bugs/1811599/+attachment/5231529/+files/longhangprevboot2.txt

-- 
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/1811599

Title:
  When booting, the computer hangs at a purple screen and no login
  prompt is ever displayed [Apple Macbook 2,1 - Intel GMA 950]

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

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

Re: [Bug 1811599] Re: When booting, the computer hangs at a purple screen and no login prompt is ever displayed [Apple Macbook 2, 1 - Intel GMA 950]

2019-01-21 Thread Alexander A Theiler
Hey Daniel,

Yeah, at the beginning of this all, I thought it was taking a long time to
boot as well, but even after letting the system sit at the purple screen
for quite some time, it never went anywhere.  I had a though that my
ancient laptop might simply be too old to properly run Ubuntu, but I was
optimistic.  What's strange is that after it crashes, it boots entirely
normally, and runs very well without any lag or video issues at all.

I'll chalk this up to being a bug related to my system being quite old.

Do you still want that new boot log after 15 minutes of waiting?

Thanks

Alex



On Mon, Jan 21, 2019 at 8:40 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> Alex,
>
> It's unclear how long this bug will take to get resolved, if at all.
> Even if you find the machine does start up after 15 minutes or so, it
> might not perform well enough to be usable.
>
> If you would like to use Ubuntu on it then maybe the lighter weight
> Lubuntu is a better solution right now:
>
> http://cdimage.ubuntu.com/lubuntu/releases/18.04/release/lubuntu-18.04.1
> -desktop-amd64.iso
> <http://cdimage.ubuntu.com/lubuntu/releases/18.04/release/lubuntu-18.04.1-desktop-amd64.iso>
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1811599
>
> Title:
>   When booting, the computer hangs at a purple screen and no login
>   prompt is ever displayed [Apple Macbook 2,1 - Intel GMA 950]
>
> Status in gdm3 package in Ubuntu:
>   Incomplete
> Status in mutter package in Ubuntu:
>   Incomplete
>
> Bug description:
>   After a fresh install of Ubuntu 18.04.1, on its first boot, the
>   computer hung at a purple screen.  No login prompt was ever displayed.
>   After holding the power button, the computer boot into Ubuntu without
>   difficulty.  I applied the workaround described in bug 1727356,
>   uncommenting WaylandEnable=False and rebooted the machine, but it
>   again hung at the purple screen.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gdm3 3.28.3-0ubuntu18.04.3
>   ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
>   Uname: Linux 4.15.0-43-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.5
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Jan 13 10:59:26 2019
>   InstallationDate: Installed on 2019-01-11 (2 days ago)
>   InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
> (20180725)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gdm3
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   mtime.conffile..etc.gdm3.custom.conf: 2019-01-11T10:47:37.073441
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1811599/+subscriptions
>


-- 
Alexander A Theiler, MHS, MS, PA-C
CAQ in Emergency Medicine

-- 
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/1811599

Title:
  When booting, the computer hangs at a purple screen and no login
  prompt is ever displayed [Apple Macbook 2,1 - Intel GMA 950]

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

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

Re: [Bug 1811599] Re: When booting, the computer hangs at a purple screen and no login prompt is ever displayed

2019-01-21 Thread Alexander A Theiler
Hey Daniel,

You were right - the computer was stuck in recovery mode.  I manually
booted it into normal mode and then restarted it and re-produced a hang.  I
then rebooted into recovery mode and recorded that boot with journalctl
-b-1 > prevboot.txt.  Please see attached.

The log states that the boot began on 1/11/19 and continues until 1/21/19.
However, if you look at the log itself, the only data recorded is from
today, 1/21/19.  I don't know where it's getting 1/11/19 from.  So, despite
the log at the top stating that the boot record spans several days, the
record itself only reflects one day.  And the file is appropriately small.
I sincerely hope this is what you're looking for, despite incorrect dates.
Can you take a look?

Thanks a ton,

Alex


On Sun, Jan 20, 2019 at 10:40 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> Although you have provided some logs that are not in recovery mode,
> those logs span multiple days so are not helpful in pinpointing the
> immediate problem.
>
> When sending logs in future please ensure they don't mention "recovery
> nomodeset", AND that the earliest and oldest dates in the log file are
> the same day within a few minutes of each other. That should be
> guaranteed by following the steps in comment #2 closely.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1811599
>
> Title:
>   When booting, the computer hangs at a purple screen and no login
>   prompt is ever displayed
>
> Status in gdm3 package in Ubuntu:
>   Incomplete
>
> Bug description:
>   After a fresh install of Ubuntu 18.04.1, on its first boot, the
>   computer hung at a purple screen.  No login prompt was ever displayed.
>   After holding the power button, the computer boot into Ubuntu without
>   difficulty.  I applied the workaround described in bug 1727356,
>   uncommenting WaylandEnable=False and rebooted the machine, but it
>   again hung at the purple screen.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gdm3 3.28.3-0ubuntu18.04.3
>   ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
>   Uname: Linux 4.15.0-43-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.5
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Jan 13 10:59:26 2019
>   InstallationDate: Installed on 2019-01-11 (2 days ago)
>   InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
> (20180725)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gdm3
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   mtime.conffile..etc.gdm3.custom.conf: 2019-01-11T10:47:37.073441
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1811599/+subscriptions
>


-- 
Alexander A Theiler, MHS, MS, PA-C
CAQ in Emergency Medicine


** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/bugs/1811599/+attachment/5231174/+files/prevboot.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/1811599

Title:
  When booting, the computer hangs at a purple screen and no login
  prompt is ever displayed

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

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

Re: [Bug 1811599] Re: When booting, the computer hangs at a purple screen and no login prompt is ever displayed

2019-01-20 Thread Alexander A Theiler
Hey Daniel,

I'm honestly not sure what I'm doing wrong.  Here's precisely what I'm
doing.  Tell me where I'm messing up:

First, I booted into recovery mode by hitting Esc on bootup, and selecting
boot into recovery mode.  The computer then boots, and reaches a point at
which it I have multiple options, the first one being continue into a
regular boot, and a then there are a few others, like "drop into root."

In the previous email, with the previous file, after booting into recovery
mode, I then selected "continue regular boot" and then I edited the
/etc/gdm3/custom.conf to enable debugging.  I then rebooted and reproduced
the hang.  I then rebooted into recovery mode, and then continued booting
into normal mode.  I then sent the files, were were apparently wrong.

Here are two more files.  Since /etc/gdm3/custom.conf already had debugging
enabled, I did not reboot the computer into recovery mode.  I simply
rebooted the machine, let it boot as normal and hang while loading as it
usually does.  I then rebooted the machine, tapped Esc, and selected "boot
into recovery mode." It paused after booting for a few seconds, and gave me
a few options.  This time, I chose "drop into root" and ran the command
"journalctl -b-1 > prev_boot.txt" but I'm not sure where it saved.  I then
selected for the computer to boot as normal, out of recovery mode.  When I
entered Ubuntu, I ran two commands, "journalctl -b-1 > prev_boot.txt" and
attached it here.  I also ran "journalctl -b >prev_boot2.txt." Between the
two boot records, I hope one is correct.  Prev_boot.txt is extremely large
again for some reason, and in the logs, it says the boot sequence started
on 1/11/19, which is absurd.  What's going on with that?  Strangely,
prev_boot2.txt is much smaller but also states that the boot sequence took
over a week.

Sorry for the lengthy email.  Where am I messing up on recording the
boot?

Sincerely,

Alex


On Sun, Jan 20, 2019 at 7:40 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> Please try again. The log in comment #7 is from recovery mode :(
>
> I think you forgot step 2 in comment #2.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1811599
>
> Title:
>   When booting, the computer hangs at a purple screen and no login
>   prompt is ever displayed
>
> Status in gdm3 package in Ubuntu:
>   Incomplete
>
> Bug description:
>   After a fresh install of Ubuntu 18.04.1, on its first boot, the
>   computer hung at a purple screen.  No login prompt was ever displayed.
>   After holding the power button, the computer boot into Ubuntu without
>   difficulty.  I applied the workaround described in bug 1727356,
>   uncommenting WaylandEnable=False and rebooted the machine, but it
>   again hung at the purple screen.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gdm3 3.28.3-0ubuntu18.04.3
>   ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
>   Uname: Linux 4.15.0-43-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.5
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Jan 13 10:59:26 2019
>   InstallationDate: Installed on 2019-01-11 (2 days ago)
>   InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
> (20180725)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gdm3
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   mtime.conffile..etc.gdm3.custom.conf: 2019-01-11T10:47:37.073441
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1811599/+subscriptions
>


-- 
Alexander A Theiler, MHS, MS, PA-C
CAQ in Emergency Medicine


** Attachment added: "prev_boot2.txt"
   
https://bugs.launchpad.net/bugs/1811599/+attachment/5230895/+files/prev_boot2.txt

** Attachment added: "prev_boot.tar.xz"
   
https://bugs.launchpad.net/bugs/1811599/+attachment/5230896/+files/prev_boot.tar.xz

-- 
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/1811599

Title:
  When booting, the computer hangs at a purple screen and no login
  prompt is ever displayed

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

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

Re: [Bug 1811599] Re: When booting, the computer hangs at a purple screen and no login prompt is ever displayed

2019-01-19 Thread Alexander A Theiler
My apologies, I've been out of town for a few days.  Here is the updated
version, which was just created, with debugging enabled.

Please see attached.

Alex

On Tue, Jan 15, 2019 at 11:45 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> That boot seems to be starting from 11 Jan. Does it also include debug
> enabled per comment #2?
>
> Regardless, it's a little too old and unnecessarily large. Please follow
> the steps in comment #2 more carefully and do it again.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1811599
>
> Title:
>   When booting, the computer hangs at a purple screen and no login
>   prompt is ever displayed
>
> Status in gdm3 package in Ubuntu:
>   Incomplete
>
> Bug description:
>   After a fresh install of Ubuntu 18.04.1, on its first boot, the
>   computer hung at a purple screen.  No login prompt was ever displayed.
>   After holding the power button, the computer boot into Ubuntu without
>   difficulty.  I applied the workaround described in bug 1727356,
>   uncommenting WaylandEnable=False and rebooted the machine, but it
>   again hung at the purple screen.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gdm3 3.28.3-0ubuntu18.04.3
>   ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
>   Uname: Linux 4.15.0-43-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.5
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Jan 13 10:59:26 2019
>   InstallationDate: Installed on 2019-01-11 (2 days ago)
>   InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
> (20180725)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gdm3
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   mtime.conffile..etc.gdm3.custom.conf: 2019-01-11T10:47:37.073441
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1811599/+subscriptions
>


-- 
Alexander A Theiler, MHS, MS, PA-C
CAQ in Emergency Medicine


** Attachment added: "prev_boot.txt"
   
https://bugs.launchpad.net/bugs/1811599/+attachment/5230586/+files/prev_boot.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/1811599

Title:
  When booting, the computer hangs at a purple screen and no login
  prompt is ever displayed

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

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

[Bug 1085706] Re: pam_ecryptfs: seteuid error

2019-01-16 Thread Alexander McColl
Affected on Mint 19.1 running i3lock
locks and unlocks fine, but systemd reports:

"pam_ecryptfs: seteuid error"

-- 
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/1085706

Title:
  pam_ecryptfs: seteuid error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ecryptfs/+bug/1085706/+subscriptions

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

Re: [Bug 1811599] Re: When booting, the computer hangs at a purple screen and no login prompt is ever displayed

2019-01-15 Thread Alexander A Theiler
Here it is.

Alex


On Tue, Jan 15, 2019 at 7:20 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> Alex,
>
> The log in comment #3 is from recovery mode, not what we need.
>
> Please follow the steps in comment #2 again, but before sending
> 'prev_boot.txt' try compressing it to make it smaller:
>
>   xz prev_boot.txt
>
> and then send us 'prev_boot.txt.xz'
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1811599
>
> Title:
>   When booting, the computer hangs at a purple screen and no login
>   prompt is ever displayed
>
> Status in gdm3 package in Ubuntu:
>   Incomplete
>
> Bug description:
>   After a fresh install of Ubuntu 18.04.1, on its first boot, the
>   computer hung at a purple screen.  No login prompt was ever displayed.
>   After holding the power button, the computer boot into Ubuntu without
>   difficulty.  I applied the workaround described in bug 1727356,
>   uncommenting WaylandEnable=False and rebooted the machine, but it
>   again hung at the purple screen.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gdm3 3.28.3-0ubuntu18.04.3
>   ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
>   Uname: Linux 4.15.0-43-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.5
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Jan 13 10:59:26 2019
>   InstallationDate: Installed on 2019-01-11 (2 days ago)
>   InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
> (20180725)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gdm3
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   mtime.conffile..etc.gdm3.custom.conf: 2019-01-11T10:47:37.073441
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1811599/+subscriptions
>


-- 
Alexander A Theiler, MHS, MS, PA-C
CAQ in Emergency Medicine


** Attachment added: "prev_boot.txt.xz"
   
https://bugs.launchpad.net/bugs/1811599/+attachment/5229498/+files/prev_boot.txt.xz

-- 
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/1811599

Title:
  When booting, the computer hangs at a purple screen and no login
  prompt is ever displayed

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

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

Re: [Bug 1811599] Re: When booting, the computer hangs at a purple screen and no login prompt is ever displayed

2019-01-15 Thread Alexander A Theiler
I received an error from Launchpad stating that the previous file I sent
was too large (14 MB) and could not be delivered, and so I repeated the
above steps again.  Here's another failed boot log, and for some reason,
it's much, much smaller (836 KB).

Alex

On Tue, Jan 15, 2019 at 10:35 AM Alex Thëil 
wrote:

> Here you are. Please see attached.
>
> Alex
>
> On Mon, Jan 14, 2019 at 7:05 PM Daniel van Vugt <
> daniel.van.v...@canonical.com> wrote:
>
>> Please:
>>
>> 1. Boot into recovery mode and enable (uncomment) debugging in
>> /etc/gdm3/custom.conf
>> 2. Reboot into normal mode and reproduce the hang.
>> 3. Reboot again into recovery mode and run:
>>
>>journalctl -b-1 > prev_boot.txt
>>
>>and then send us the file 'prev_boot.txt'.
>>
>> ** Changed in: gdm3 (Ubuntu)
>>Status: New => Incomplete
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1811599
>>
>> Title:
>>   When booting, the computer hangs at a purple screen and no login
>>   prompt is ever displayed
>>
>> Status in gdm3 package in Ubuntu:
>>   Incomplete
>>
>> Bug description:
>>   After a fresh install of Ubuntu 18.04.1, on its first boot, the
>>   computer hung at a purple screen.  No login prompt was ever displayed.
>>   After holding the power button, the computer boot into Ubuntu without
>>   difficulty.  I applied the workaround described in bug 1727356,
>>   uncommenting WaylandEnable=False and rebooted the machine, but it
>>   again hung at the purple screen.
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 18.04
>>   Package: gdm3 3.28.3-0ubuntu18.04.3
>>   ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
>>   Uname: Linux 4.15.0-43-generic x86_64
>>   ApportVersion: 2.20.9-0ubuntu7.5
>>   Architecture: amd64
>>   CurrentDesktop: ubuntu:GNOME
>>   Date: Sun Jan 13 10:59:26 2019
>>   InstallationDate: Installed on 2019-01-11 (2 days ago)
>>   InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
>> (20180725)
>>   ProcEnviron:
>>TERM=xterm-256color
>>PATH=(custom, no user)
>>XDG_RUNTIME_DIR=
>>    LANG=en_US.UTF-8
>>SHELL=/bin/bash
>>   SourcePackage: gdm3
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>   mtime.conffile..etc.gdm3.custom.conf: 2019-01-11T10:47:37.073441
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1811599/+subscriptions
>>
>
>
> --
> Alexander A Theiler, MHS, MS, PA-C
> CAQ in Emergency Medicine
>


-- 
Alexander A Theiler, MHS, MS, PA-C
CAQ in Emergency Medicine


** Attachment added: "prev_boot2.txt"
   
https://bugs.launchpad.net/bugs/1811599/+attachment/5229396/+files/prev_boot2.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/1811599

Title:
  When booting, the computer hangs at a purple screen and no login
  prompt is ever displayed

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

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

[Bug 1811599] [NEW] When booting, the computer hangs at a purple screen and no login prompt is ever displayed

2019-01-13 Thread Alexander A Theiler
Public bug reported:

After a fresh install of Ubuntu 18.04.1, on its first boot, the computer
hung at a purple screen.  No login prompt was ever displayed.  After
holding the power button, the computer boot into Ubuntu without
difficulty.  I applied the workaround described in bug 1727356,
uncommenting WaylandEnable=False and rebooted the machine, but it again
hung at the purple screen.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gdm3 3.28.3-0ubuntu18.04.3
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 13 10:59:26 2019
InstallationDate: Installed on 2019-01-11 (2 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.gdm3.custom.conf: 2019-01-11T10:47:37.073441

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


** Tags: amd64 apport-bug bionic

-- 
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/1811599

Title:
  When booting, the computer hangs at a purple screen and no login
  prompt is ever displayed

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

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

[Bug 502642] Re: .ts files always get recognized as application/x-linguist and never as video/mp2t (mpeg transport stream)

2018-12-27 Thread Alexander Amelkin
I second comment #48. Ubuntu 16.04 (well, Mint 18.3 Sylvia actually, but
it uses Xenial repositories).


```
$ hexdump -C -n 16 .ts 
  47 ff ff 50 52 49 56 54  3a 04 00 00 39 04 00 00  |G..PRIVT:...9...|
$ mimetype --all .ts 
.ts: text/vnd.trolltech.linguist
.ts: application/octet-stream

```

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

Title:
  .ts files always get recognized as application/x-linguist and never as
  video/mp2t (mpeg transport stream)

To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/502642/+subscriptions

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

  1   2   3   4   5   6   7   8   9   10   >