[Bug 1947606] [NEW] Unmaximizing window results in different number of rows from before maximizing it

2021-10-18 Thread abcdef
Public bug reported:

When having e.g. a 7 rows high window (with two tabs) and maximizing +
unmaximizing it, the result is a 6 rows high window. Repeat it and it
goes to 5, 4, and finally 3 rows in height. It doesn't shrink past 3
rows.

It is especially noticeable with a long narrow window along the bottom
of the screen, where the distance to the bottom screen edge increases
every time the window height shrinks.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gnome-terminal 3.38.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 18 17:19:44 2021
InstallationDate: Installed on 2020-10-30 (353 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to impish on 2021-09-17 (31 days ago)

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


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

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

Title:
  Unmaximizing window results in different number of rows from before
  maximizing it

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


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

[Bug 1947507] [NEW] Dock does not react to clicks on screen edge pixels

2021-10-17 Thread abcdef
Public bug reported:

The dock is wasting its entire screen edge of valuable edge pixels by
not reacting to actual clicks on them.

I have the dock on the left edge.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 17 17:54:03 2021
InstallationDate: Installed on 2020-10-30 (352 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: Upgraded to impish on 2021-09-17 (30 days ago)

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


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

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

Title:
  Dock does not react to clicks on screen edge pixels

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


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

[Bug 1938596] Re: Always on top windows obscure context menus and tooltips

2021-08-01 Thread abcdef
** Attachment added: "Illustrating how a Files window's context menu is hidden 
by another, always on top Files window"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1938596/+attachment/5515157/+files/aot%20on%20context%20menu.png

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

Title:
  Always on top windows obscure context menus and tooltips

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


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

[Bug 1938596] monitors.xml.txt

2021-07-31 Thread abcdef
** Attachment added: "monitors.xml.txt"
   
https://bugs.launchpad.net/bugs/1938596/+attachment/5515006/+files/monitors.xml.txt

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

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

** Attachment removed: "monitors.xml.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1938596/+attachment/5515006/+files/monitors.xml.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/1938596

Title:
  Always on top windows obscure context menus and tooltips

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


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

[Bug 1938596] ShellJournal.txt

2021-07-31 Thread abcdef
** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/1938596/+attachment/5515005/+files/ShellJournal.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/1938596

Title:
  Always on top windows obscure context menus and tooltips

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


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

[Bug 1938596] ProcCpuinfoMinimal.txt

2021-07-31 Thread abcdef
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1938596/+attachment/5515004/+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/1938596

Title:
  Always on top windows obscure context menus and tooltips

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


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

[Bug 1938596] GsettingsChanges.txt

2021-07-31 Thread abcdef
** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1938596/+attachment/5515003/+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/1938596

Title:
  Always on top windows obscure context menus and tooltips

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


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

[Bug 1938596] Re: Always on top windows obscure context menus and tooltips

2021-07-31 Thread abcdef
apport information

** Tags added: apport-collected hirsute wayland-session

** Description changed:

  "Always on top" windows are meant to be on top of other non-transient
  windows (its peers), but they're also on top of other windows' transient
  GUI components like context menus and tooltips.
  
  It is not constructive to obscure menus and tooltips with always on top
  windows any more than it is helpful to obscure the actual mouse cursor
  with AOT windows. They are short lived. Users can't decide where to
  place them. They will disappear by themselves when the user is done with
  them. A hidden tooltip or context menu helps no one.
  
  ubuntu 21.04 gnome wayland
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu65.1
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 21.04
+ InstallationDate: Installed on 2020-10-30 (274 days ago)
+ InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
+ NonfreeKernelModules: wl
+ Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=sv_SE.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
+ RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
+ Tags:  wayland-session hirsute
+ Uname: Linux 5.11.0-25-generic x86_64
+ UpgradeStatus: Upgraded to hirsute on 2021-04-23 (99 days ago)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1938596/+attachment/5515002/+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/1938596

Title:
  Always on top windows obscure context menus and tooltips

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


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

[Bug 1938596] Re: Always on top windows obscure context menus and tooltips

2021-07-31 Thread abcdef
Thank you for your suggestions, I will look into it. If there's a
particular point that could be made clearer then I'll absolutely submit
a screenshot and try and clarify it.

As for ubuntu-bug, I did run it. It guided me to report a bug against an
Xorg package. Would you say that that would've been a constructive
identification of the affected package, despite running a Wayland
session? If so I'll heed your recommendation in the future; if not I
will have to continue to dismiss ubuntu-bug as unmaintained.

The page on bug reporting guidelines is also dismissed by default, since
it has never been able to properly guide me to the correct package. But
I'll try:

Attempt 1: Jump to section 6 ("non-crash bugs") → "use ubuntu-bug" →
Xorg — is that correct, despite using Wayland?

Attempt 2: Jump to section 7 ("no particular package") → Follow the link
to the "FindRightPackage" page → jump to section 1.6 "Graphical
environment" → "The Ubuntu graphical environment is provided by [...]
the X Window System (aka X.org)" — really? Despite using Wayland? But
okay → "In Ubuntu [...] the no-effects window manager is metacity" — is
that really correct? If so I'll change the package to "metacity".

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

Title:
  Always on top windows obscure context menus and tooltips

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


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

[Bug 1922808] [NEW] Terminal doesn't focus the search field when I Ctrl+Shift+F

2021-04-06 Thread abcdef
Public bug reported:

I press ctrl+shift+f to do a search.
The search field is focused and I input my keywords with the keyboard.
I perform the search.
I use the mouse to select and copy another piece of text in the terminal window 
in order to do another search.
I press ctrl+shift+f again.
The terminal window remains focused. The search window is still open and 
staring at me, waiting for me to use the mouse to click on it.

I expect the search field to be focused and ready to receive input after
I press ctrl+shift+f, regardless of whether it resides in a separate
window and whether that window is already open.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-terminal 3.38.0-1ubuntu1.1
ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
Uname: Linux 5.8.0-48-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  6 23:08:29 2021
InstallationDate: Installed on 2020-10-30 (158 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Description changed:

- I press ctrl+shift+f to do a search. 
+ I press ctrl+shift+f to do a search.
  The search field is focused and I input my keywords with the keyboard.
- I perform the search. 
+ I perform the search.
  I use the mouse to select and copy another piece of text in the terminal 
window in order to do another search.
  I press ctrl+shift+f again.
  The terminal window remains focused. The search window is still open and 
staring at me, waiting for me to use the mouse to click on it.
  
  I expect the search field to be focused and ready to receive input after
  I press ctrl+shift+f, regardless of whether it resides in a separate
- window and whether that window is already open or not.
+ window and whether that window is already open.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-terminal 3.38.0-1ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  6 23:08:29 2021
  InstallationDate: Installed on 2020-10-30 (158 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=sv_SE.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=sv_SE.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-terminal
  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-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1922808

Title:
  Terminal doesn't focus the search field when I Ctrl+Shift+F

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

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

[Bug 1920776] Re: Source window raised on drag-n-drop -- drag-n-drop destination window not raised while hovering over it

2021-04-06 Thread abcdef
Thanks for moving it to the right place

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

Title:
  Source window raised on drag-n-drop -- drag-n-drop destination window
  not raised while hovering over it

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

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

[Bug 1915674] [NEW] Sharing folder in Files: "net usershare" returned error 255

2021-02-14 Thread abcdef
Public bug reported:

I'm just guessing package name since I can't simply read my way to that
information in the GUI...

I'm trying to share my games folder on the network by right clicking and
selecting the Share on local network option.

I tick Share this folder, and confirm. I expected the folder to be
shared, but instead I get the message:

"net usershare" returned error 255: net usershare add: share name games
is already a valid system user name

Ubuntu 20.10

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: nautilus 1:3.38.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 15 02:05:28 2021
InstallationDate: Installed on 2020-10-30 (107 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
 evince3.38.0-1
 file-roller   3.38.0-1
 nautilus-extension-gnome-terminal 3.38.0-1ubuntu1.1
 nautilus-share0.7.3-2ubuntu3

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


** Tags: amd64 apport-bug groovy 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/1915674

Title:
  Sharing folder in Files: "net usershare" returned error 255

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

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

[Bug 1908608] Re: Crash to login screen when plugging in/out external monitor

2021-01-04 Thread abcdef
Hello and thank you for following up.

Thank you for your suggestions. I will look into them.

I will be on the lookout for new crashes and report them here.

While uninstalling the unofficial desktop icon extension would seem like
a good idea in the context of this bug report, that would result in an
unusable system and therefore in no additional crashes or information.

Hopefully they're not the source, but otherwise it may underline the
apparent architectural problem of giving small utility extensions the
power to crash the entire session along with every application on the
system, or alternatively the apparent social problem of encouraging
people to write trivial utilities as gnome extensions when it's not a
suitable extension point for the task. (Assuming those problems are not
already readily acknowledged in the community. I don't know much about
people's attitudes towards that)

(That the OS will become unusable is just a natural consequence of a
desktop OS with subpar built-in support for desktop icons: I'm then
forced to find a replacement extension that offers the minimum set of
functionality that can reasonably be expected from any desktop OS. The
default desktop icon extension simply does not deliver — with it I would
need to use another OS)

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

Title:
  Crash to login screen when plugging in/out external monitor

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

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

[Bug 1908608] Re: Crash to login screen when plugging in/out external monitor

2020-12-18 Thread abcdef
Just a FYI, I'm a bit confused regarding the ID. The .uploaded file has
a timestamp earlier than the .crash file (about 12 hours earlier than
when I actually experienced the crash most recently) and the .uploaded
file doesn't change its contents after running ubuntu-bug, even as
superuser.

It doesn't appear to correspond to the actual upload? Or am I just
tricked by some sort of deduplication mechanism that prevents subsequent
uploads of identical crashes? If so I guess it's the correct ID since
I've experienced it multiple times, but can't really be sure since I
don't have permission to inspect the uploaded file.

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

Title:
  Crash to login screen when plugging in/out external monitor

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

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

[Bug 1908608] Re: Crash to login screen when plugging in/out external monitor

2020-12-18 Thread abcdef
Thanks for taking a look.

I see. Found it - UUID from crash.uploaded: 362c2716-4051-11eb-
8be3-fa163ee63de6

Thank you for the suggestion. Did you spot any specific indication that
that extension was the source of the crash? Anyway, if you do, I can
reach out to them.

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

Title:
  Crash to login screen when plugging in/out external monitor

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

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

[Bug 1908608] Re: Crash to login screen when plugging in/out external monitor

2020-12-17 Thread abcdef
I also ran 'ubuntu-bug /var/crash/_my_crash_report.crash' for my crash
report, and was led to believe that a new bug would be created as a
result (in another issue I was there told to "tell us the ID of the
newly-created bug" after running that command), but I was given no
information by the time the command finished.

Did I miss a step in order to receive an ID?

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

Title:
  Crash to login screen when plugging in/out external monitor

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

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

[Bug 1908608] Re: Crash to login screen when plugging in/out external monitor

2020-12-17 Thread abcdef
When trying to mark this bug as private I get the message "The bug will
become invisible because there is no-one with permissions to see Private
bugs". Is that a mistake? Shouldn't someone be able to see 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/1908608

Title:
  Crash to login screen when plugging in/out external monitor

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

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

[Bug 1908608] [NEW] Crash to login screen when plugging in/out external monitor

2020-12-17 Thread abcdef
Public bug reported:

This matches the title of
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1717170 but I
don't want to assume it is the same considering that was allegedly fixed
three years ago.

journal:

dec 17 23:12:51 computer-name kernel: usb 3-1: USB disconnect, device number 8
dec 17 23:12:51 computer-name kernel: usb 3-1.1: USB disconnect, device number 
10
dec 17 23:12:51 computer-name acpid[716]: input device has been disconnected, 
fd 7
dec 17 23:12:51 computer-name gnome-shell[2891]: libinput error: event6  - 
bcm5974: client bug: event processing lagging behind by 42ms, your system is 
too slow
dec 17 23:12:51 computer-name acpid[716]: input device has been disconnected, 
fd 8
dec 17 23:12:51 computer-name acpid[716]: input device has been disconnected, 
fd 15
dec 17 23:12:51 computer-name kernel: usb 3-1.4: USB disconnect, device number 9
dec 17 23:12:53 computer-name gnome-shell[2891]: 
meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < 
n_logical_monitors' failed
dec 17 23:12:53 computer-name fwupd[3384]: 22:12:53:0711 FuEngine 
nitrokey failed to change udev device 
/sys/devices/pci:00/:00:02.0/drm/card0: cannot ensure ID: FuUdevDevice:
dec 17 23:12:53 computer-name fwupd[3384]: Unknown Device
dec 17 23:12:53 computer-name fwupd[3384]:   Flags:none
dec 17 23:12:53 computer-name gnome-shell[2891]: DING: GNOME nautilus 3.38.1
dec 17 23:12:53 computer-name gnome-shell[2891]: 
meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < 
n_logical_monitors' failed
dec 17 23:12:53 computer-name gnome-shell[2891]: 
meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) 
number < g_list_length (manager->logical_monitors)' failed
dec 17 23:12:53 computer-name gnome-shell[2891]: 
meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' 
failed
dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: 
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: 
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: 
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: 
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: 
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
dec 17 23:12:54 computer-name gnome-shell[2891]: Window manager warning: 
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
dec 17 23:12:55 computer-name gnome-shell[2891]: GNOME Shell crashed with 
signal 11
dec 17 23:12:55 computer-name gnome-shell[2891]: == Stack trace for context 
0x55db60db91a0 ==
dec 17 23:13:06 computer-name nautilus[3814]: Error reading events from 
display: Brutet rör
dec 17 23:13:06 computer-name unknown[3089]: Error reading events from display: 
Brutet rör
dec 17 23:13:06 computer-name org.kde.kdeconnect.daemon.desktop[3092]: The 
Wayland connection broke. Did the Wayland compositor die?
dec 17 23:13:06 computer-name gsd-power[3032]: Error reading events from 
display: Brutet rör
dec 17 23:13:06 computer-name polkitd(authority=local)[738]: Unregistered 
Authentication Agent for unix-session:2 (system bus name :1.82, object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale sv_SE.UTF-8) 
(disconnected from bus)
dec 17 23:13:06 computer-name unknown[3020]: Error reading events from display: 
Brutet rör
dec 17 23:13:06 computer-name unknown[3031]: Error reading events from display: 
Brutet rör
dec 17 23:13:06 computer-name unknown[3030]: Error reading events from display: 
Brutet rör
dec 17 23:13:06 computer-name unknown[3064]: Error reading events from display: 
Brutet rör
dec 17 23:13:06 computer-name systemd[2728]: 
org.gnome.SettingsDaemon.Color.service: Main process exited, code=exited, 
status=1/FAILURE
dec 17 23:13:06 computer-name systemd[2728]: org.gnome.Shell@wayland.service: 
Main process exited, code=dumped, status=11/SEGV
dec 17 23:13:06 computer-name systemd[2728]: 
org.gnome.SettingsDaemon.Keyboard.service: Main process exited, code=exited, 
status=1/FAILURE
dec 17 23:13:06 computer-name systemd[2728]: 
org.gnome.SettingsDaemon.MediaKeys.service: Main process exited, code=exited, 
status=1/FAILURE
dec 17 23:13:06 computer-na

[Bug 1797002] Re: Bluetooth audio skips while the settings dialog is open

2020-12-15 Thread abcdef
Hello,

Thank you for looking at this issue.

If source code propagate downstream, then I think it would be a good
idea to come up with a system that propagates bug reports upstream.

If that effort is underway I will consider registering on arbitrary
other bug trackers in the meantime as a stopgap solution.

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

Title:
  Bluetooth audio skips while the settings dialog is open

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

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

[Bug 1906919] Re: Saving a file in gedit crashes desktop to login screen

2020-12-07 Thread abcdef
So where can one find the desktopManager.js file that would need the
fix? I can't find a single mention online of where system bundled gnome
extensions are located.

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

Title:
  Saving a file in gedit crashes desktop to login screen

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

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

[Bug 1906919] Re: Saving a file in gedit crashes desktop to login screen

2020-12-07 Thread abcdef
A glance through journal.txt did not give me confidence that it wasn't
bleeding all sorts of info, since my name was on every line.

Here's a relevant excerpt:

```
   
_updateDesktopIfChanged@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:418:17
   
_monitorDesktopFolder/<@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:340:94
dec 07 11:53:27 computer-name gnome-shell[1606]: Error getting desktop unix 
mode: Gio.IOErrorEnum: Fel vid hämtning av information om filen 
”/home/username/Skrivbord/.goutputstream-PG8WU0”: Filen eller katalogen finns 
inte
dec 07 11:53:27 computer-name gnome-shell[1606]: Error getting desktop unix 
mode: Gio.IOErrorEnum: Fel vid hämtning av information om filen 
”/home/username/Skrivbord/.goutputstream-PG8WU0”: Filen eller katalogen finns 
inte
dec 07 11:53:27 computer-name gnome-shell[1606]: Error getting desktop unix 
mode: Gio.IOErrorEnum: Fel vid hämtning av information om filen 
”/home/username/Skrivbord/.goutputstream-PG8WU0”: Filen eller katalogen finns 
inte
dec 07 11:53:27 computer-name gnome-shell[1606]: libinput error: event5  - 
bcm5974: client bug: event processing lagging behind by 17ms, your system is 
too slow
dec 07 11:53:27 computer-name gnome-shell[1606]: JS ERROR: TypeError: fileItem 
is undefined
   
_updateDesktopIfChanged@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:418:17
   
_monitorDesktopFolder/<@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:340:94
dec 07 11:53:27 computer-name gnome-shell[1606]: Error getting desktop unix 
mode: Gio.IOErrorEnum: Fel vid hämtning av information om filen 
”/home/username/Skrivbord/.goutputstream-TOKPU0”: Filen eller katalogen finns 
inte
dec 07 11:53:27 computer-name gnome-shell[1606]: Error getting desktop unix 
mode: Gio.IOErrorEnum: Fel vid hämtning av information om filen 
”/home/username/Skrivbord/.goutputstream-TOKPU0”: Filen eller katalogen finns 
inte
dec 07 11:53:27 computer-name gnome-shell[1606]: Error getting desktop unix 
mode: Gio.IOErrorEnum: Fel vid hämtning av information om filen 
”/home/username/Skrivbord/.goutputstream-TOKPU0”: Filen eller katalogen finns 
inte
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: 
assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: 
assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: 
assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: 
assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: 
assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: 
assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: 
assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: 
assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: 
assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: 
assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: 
assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: 
assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: **
dec 07 11:53:28 computer-name gnome-shell[1606]: 
St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child 
== NULL)
dec 07 11:53:28 computer-name gnome-shell[1606]: Bail out! 
St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child 
== NULL)
dec 07 11:53:28 computer-name gnome-shell[1606]: GNOME Shell crashed with 
signal 6
dec 07 11:53:28 computer-name gnome-shell[1606]: == Stack trace for context 
0x55789c2411b0 ==
dec 07 11:53:28 computer-name gnome-shell[1606]: #0   55789c6da140 i   
/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:234 
(aa6a22a0420 @ 10)
dec 07 11:53:28 computer-name gnome-shell[1606]: #1   7ffdd4d298e0 b   
self-hosted:225 (39bd78b6a100 @ 273)
dec 07 11:53:28 computer-name gnome-shell[1606]: #2   55789c6da0a8 i   
/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:234 
(aa6a22a0470 @ 43)
dec 07 11:53:28 computer-name gnome-shell[1606]: #3   55789c6da018 i   
/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:209 
(aa6a22a05b0 @ 32)
d

[Bug 1906919] Re: Saving a file in gedit crashes desktop to login screen

2020-12-07 Thread abcdef
I can recreate the crash at will so I can do that zero to many times
depending on what you need.

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

Title:
  Saving a file in gedit crashes desktop to login screen

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

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

[Bug 1906919] Re: Saving a file in gedit crashes desktop to login screen

2020-12-06 Thread abcdef
Thank you for demonstrating interest. Here is the link that you
requested:

https://errors.ubuntu.com/oops/b287c9e0-3850-11eb-86ea-fa163e6cac46

More info:
The crash only happens when saving a file residing on the desktop. Upon saving, 
the entire desktop blinks, suggesting some heavy-handed graphics operation upon 
modifying a desktop file. The first time this occurred I got a glimpse of some 
console output mentioning "iXXX" where X were digits, which reminded me of the 
name of Intel graphics drivers.

The crash can be reproduced by saving approximately 10 times, or by just
holding down Ctrl+S (gedit allows saving an unedited document, for some
reason).

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

Title:
  Saving a file in gedit crashes desktop to login screen

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

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

[Bug 1906919] monitors.xml.txt

2020-12-05 Thread abcdef
apport information

** Attachment added: "monitors.xml.txt"
   
https://bugs.launchpad.net/bugs/1906919/+attachment/5441356/+files/monitors.xml.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/1906919

Title:
  Saving a file in gedit crashes desktop to login screen

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

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

[Bug 1906919] Re: Saving a file in gedit crashes desktop to login screen

2020-12-05 Thread abcdef
apport information

** Tags added: apport-collected groovy wayland-session

** Description changed:

  When saving a file in gedit (or whatever the default text editor is) it
  crashes my entire desktop, and I end up on the login screen.
  
  ubuntu 20.10
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu50.2
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: sddm
+ DistroRelease: Ubuntu 20.10
+ InstallationDate: Installed on 2020-10-30 (36 days ago)
+ InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
+ NonfreeKernelModules: wl
+ Package: gnome-shell 3.38.1-1ubuntu1.1
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=sv_SE.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17
+ RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1
+ Tags:  wayland-session groovy
+ Uname: Linux 5.8.0-31-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1906919/+attachment/5441352/+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/1906919

Title:
  Saving a file in gedit crashes desktop to login screen

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

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

[Bug 1906919] ShellJournal.txt

2020-12-05 Thread abcdef
apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/1906919/+attachment/5441355/+files/ShellJournal.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/1906919

Title:
  Saving a file in gedit crashes desktop to login screen

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

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

[Bug 1906919] GsettingsChanges.txt

2020-12-05 Thread abcdef
apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1906919/+attachment/5441353/+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/1906919

Title:
  Saving a file in gedit crashes desktop to login screen

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

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

[Bug 1906919] ProcCpuinfoMinimal.txt

2020-12-05 Thread abcdef
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1906919/+attachment/5441354/+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/1906919

Title:
  Saving a file in gedit crashes desktop to login screen

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

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

[Bug 1906919] Re: Saving a file in gedit crashes desktop to login screen

2020-12-05 Thread abcdef
I tried, but I apparently used the wrong account and now it just refuses
every time.

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

Title:
  Saving a file in gedit crashes desktop to login screen

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

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