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

[max chistyakov]

I noticed this error messages:
1) when switch the language keyboard layout (with Super+Space)
2) or when switch to the Firefox or Chromium applications (both installed 
through Snap

Despite I have catched this messages thousand times in a day, usually I
don't encounter the system freeze. Despite the source in logs is gnome-
shell, it appears in gnome applications also

Hardware: HP Pavilion 15-dk0064ur
Ubuntu 23.10
Gnome: 45.2 + Wayland

-- 
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 1955850] Re: /etc/X11/Xresources no longer loaded, error in patch

[Max]

The issue still remains and breaks xterm defaults on Ubuntu 22.04.

If Xresources is a folder, the upstream gdm3 Xsession script will fail
even with this change, so this bug was not introduced by them and should
not be fixed there.

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

Title:
  /etc/X11/Xresources no longer loaded, error in patch

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


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

[Bug 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking

[Max Lee]

verify fixed with mutter 42.9-0ubuntu7 in jammy-proposed.
SEV16_DVT1_C4 202309-32111

1. enable proposed
2. sudo apt update
3. sudo apt dist-upgrade
4. sudo reboot -i
5. sudo dpkg -l | grep mutter (make sure all mutter related were ugpraded to 
42.9ubuntu7)
6. Connect external monitor to the affected system
7. Switch display modes to mirror mode
8. Observe the mirror mode can be set successfully. So the issue is resolved.

** Tags removed: verification-needed
** Tags added: verification-done verification-done-jammy

** Tags removed: verification-needed-jammy

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

Title:
  Mirror mode doesn't work when panel only supports one refresh rate
  with reduced blanking

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2051074/+subscriptions


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

[Bug 2051829] [NEW] Nautilus file manager failed to connect to samba share with user without password

[Max Vasin]

Public bug reported:

Ubuntu 23.10

nautilus:
  Installed: 1:45~rc-1ubuntu1

I expected successful connection to a samba share with specific user
without password.

I have home samba server running on ubuntu server. It provides one share
with disabled anonymous access but with a user without password (blank).
Windows explorer, mac finder and other clients works fine, even terminal
smbclient, but then i try to connect with nautilus from ubuntu desktop
as "registered user" but leave password blank ->  i got "invalid
argument". When i create another samba user on the server with a
password - connection was successful.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: nautilus 1:45~rc-1ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 31 12:18:54 2024
GsettingsChanges:
 b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
 b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
InstallationDate: Installed on 2023-12-27 (35 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
 dropbox   2023.09.06
 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1

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


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

** Attachment added: "image_2024-01-31_122839837.png"
   
https://bugs.launchpad.net/bugs/2051829/+attachment/5743877/+files/image_2024-01-31_122839837.png

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

Title:
  Nautilus file manager failed to connect to samba share with user
  without password

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


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

[Bug 1966635] Re: can't move file/directory by drag and drop by using touch monitor

[Max Lee]

** Tags added: originate-from-2022991

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

Title:
  can't move file/directory by drag and drop by using touch monitor

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


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

[Bug 1430068] Re: Unable to launch gnome-system-monitor

[Max Mustermann]

executing

> sudo echo 512 > /proc/sys/fs/inotify/max_user_instances

does not work because it won't open the file as root but as your current user. 
This is because "> /proc/sys/fs/inotify/max_user_instances" is not part of what 
sudo executes. The command is interpreted by your shell as follows: open the 
file "/proc/sys/fs/inotify/max_user_instances
" for writing and execute the programm "sudo" with the following arguments 
["echo", "512"] and replace the output(stdout) of the program with said file 
for starting it. Since your shell is not running as root, it cannot open 
"/proc/sys/fs/inotify/max_user_instances" for writing.

You can either get a shell running as root (with "sudo -i" for example),
or do "echo 512 | sudo tee /proc/sys/fs/inotify/max_user_instances". The
2nd way works by passing the output of echo to sudo with in turn will
pass it on to tee which then will open the file, which it can do because
sudo invoked tee as root.

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

Title:
  Unable to launch gnome-system-monitor

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


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

[Bug 1964393] Re: gnome-shell crashed with assertion failure in meta_kms_update_set_power_save: !update->plane_assignments

[Max Overmeyer]

I saw on
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_1289561
that you introduced a new environment variable
MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING and subscribed to jammy-proposed
to try it out.

The problem does not occur since the updates!

I haven't even set the environment variable. Updated packages were:
2022-03-12 10:59:50 install libadwaita-1-0:amd64  1.1~rc-1
2022-03-12 10:59:50 install gir1.2-adw-1:amd64  1.1~rc-1
2022-03-12 10:59:50 install libopengl0:amd64  1.4.0-1
2022-03-12 10:59:50 install libmutter-10-0:amd64  42~beta-1ubuntu1
2022-03-12 10:59:50 install gir1.2-mutter-10:amd64  42~beta-1ubuntu1
2022-03-12 10:59:52 install xcvt:amd64  0.1.1-3


I also installed lutris since I reproduced the bug, probably uninteresting, but 
mention it nevertheless due to mesa-utils.
2022-03-11 20:25:52 install fluid-soundfont-gm:all  3.1-5.3
2022-03-11 20:25:53 install fluid-soundfont-gs:all  3.1-5.3
2022-03-11 20:25:53 install libz-mingw-w64:all  1.2.11+dfsg-3
2022-03-11 20:25:53 install libwine-development:amd64  6.0+repack-1ubuntu1
2022-03-11 20:25:58 install python3-lxml:amd64  4.8.0-1
2022-03-11 20:25:58 install python3-setproctitle:amd64  1.2.2-2
2022-03-11 20:25:58 install python3-magic:all  2:0.4.24-2
2022-03-11 20:25:58 install mesa-utils:amd64  8.4.0-1build1
2022-03-11 20:25:58 install lutris:all  0.5.9.1-1
2022-03-11 20:25:58 install python3-soupsieve:all  2.3.1-1
2022-03-11 20:25:58 install python3-bs4:all  4.10.0-2
2022-03-11 20:25:58 install python3-evdev:amd64  1.4.0+dfsg-1build1
2022-03-11 20:25:58 install python3-webencodings:all  0.5.1-4
2022-03-11 20:25:58 install python3-html5lib:all  1.1-3

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

Title:
  gnome-shell crashed with assertion failure in
  meta_kms_update_set_power_save: !update->plane_assignments

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


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

[Bug 1918044] Re: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore

[Max Harmathy]

This issue is spamming the log with messages


Failed to get Yr.no forecast data: 404 Not Found

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

Title:
  (Update libgweather to 3.36.2) Weather forecast and info is not
  available anymore

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


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

[Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.

[Max Waterman]

I have a similar problem on my Dell XPS 13 - if I boot the laptop with the 
headphones (3.5mm) plugged in, then it essentially disabled the 3.5mm headphone 
jack - nothing I've tried re-enabled it again (eg unplugging/replugging the 
headphone, all the settings, etc). Only a reboot without the headphones plugged 
in and plugging them in after logging in, fixes the problem.
I don't have this problem on my Lenovo T480s.
Perhaps this is a different problem?

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

Title:
  External audio device shows up in the sound output options but the
  sound keeps being emitted from the internal laptop speaker, or none at
  all.

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

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

[Bug 1857335] Re: System volume slider only works between ~90% and 100%.

[Max Waterman]

Not sure why there has been no activity...it certainly shouldn't be
'expired', in my view.

** Changed in: gnome-control-center (Ubuntu)
   Status: Expired => New

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

Title:
  System volume slider only works between ~90% and 100%.

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

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

[Bug 1876308] Re: in GIO 2.64.2 (Ubuntu 20.04) smb file attributes corrupted

[Max-Ulrich Farber]

*** This bug is a duplicate of bug 1872476 ***
https://bugs.launchpad.net/bugs/1872476

I have read the explication of Sergio Durigan Junior in bug 1872476 and
I am convinced now that there is a problem in Samba and not in GIO. So I
shall mark this bug as a duplicate of 1872476 now. Thanks, Sergio!

** This bug has been marked a duplicate of bug 1872476
   Shared files are shown as folders

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

Title:
  in GIO 2.64.2 (Ubuntu 20.04) smb file attributes corrupted

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

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

[Bug 1876308] Re: in GIO 2.64.2 (Ubuntu 20.04) smb file attributes corrupted

[Max-Ulrich Farber]

I tried the update in a virtual machine. It seems to work. The files on
the NAS are no more shown as empty folders even if they are mounted via
GIO. But it is not the same machine where the bug had occurred before,
so I must go on testing to be shure.

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

Title:
  in GIO 2.64.2 (Ubuntu 20.04) smb file attributes corrupted

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

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

[Bug 1876308] Re: in GIO 2.64.2 (Ubuntu 20.04) smb file attributes corrupted

[Max-Ulrich Farber]

It seems to be the same problem as bug 1872476, but there it seems to
affect samba. I found that samba 4.11.7 alone works fine and that the
bug only occurs if the samba shares are mounted with gio mount.
Therefore I suppose it is a gio bug.

Before installing a patched samba version in my system I would like to
know what has been done there. A patched samba can be quite a security
risk.

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

Title:
  in GIO 2.64.2 (Ubuntu 20.04) smb file attributes corrupted

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

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

[Bug 1876308] [NEW] in GIO 2.64.2 (Ubuntu 20.04) smb file attributes corrupted

[Max-Ulrich Farber]

Public bug reported:

If the samba protocol is reduced to SMB-1 (option client max protocol =
NT1 in smb.conf), in all samba shares mounted with gio mount, the
mounting used by file managers like Nautilus or Thunar, ordinary files
are displayed as empty folders and therefore not usable. The problem
seems to be new in Ubuntu 20.04 (samba 4.11 and GIO 2.64.2) because it
did not exist in Ubuntu 18.04 LTS (samba 4.7 and GIO 2.56.4).

In a shell opened by smbclient or in samba-shares mounted via
mount.cifs, in Ubuntu 20.02 all files are displayed correctly and
usable, even when the protocol is reduced to SMB-1 (client max protocol
= NT1 in smb.conf or mount-option vers 1.0). Therefore the problem seems
not to be a bug in samba 4.11 but one in the used GIO version.

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

** Description changed:

  If the samba protocol is reduced to SMB-1 (option client max protocol =
  NT1 in smb.conf), in all samba shares mounted with gio mount, the
  mounting used by file managers like Nautilus or Thunar, ordinary files
  are displayed as empty folders and therefore not usable. The problem
  seems to be new in Ubuntu 20.04 (samba 4.11 and GIO 2.64.2) because it
  did not exist in Ubuntu 18.04 LTS (samba 4.7 and GIO 2.56.4).
  
- In a shell opened by smbclient or in samba-shares mounted via gvfs-
- mount, in Ubuntu 20.02 all files are displayed correctly and usable,
- even when the protocol is reduced to SMB-1 (client max protocol = NT1 in
- smb.conf or mount-option vers 1.0). Therefore the problem seems not to
- be a bug in samba 4.11 but one in the used GIO version.
+ In a shell opened by smbclient or in samba-shares mounted via
+ mount.cifs, in Ubuntu 20.02 all files are displayed correctly and
+ usable, even when the protocol is reduced to SMB-1 (client max protocol
+ = NT1 in smb.conf or mount-option vers 1.0). Therefore the problem seems
+ not to be a bug in samba 4.11 but one in the used GIO version.

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

Title:
  in GIO 2.64.2 (Ubuntu 20.04) smb file attributes corrupted

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

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

[Bug 1845795] Re: authentication window got stuck over other windows at top left

[Max Barry]

*** This bug is a duplicate of bug 1824874 ***
https://bugs.launchpad.net/bugs/1824874

** This bug has been marked a duplicate of bug 1824874
   undismissable, unclickable authentication dialog left on screen (top-left 
corner) after policykit authentication [pushModal: invocation of begin_modal 
failed]

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

Title:
  authentication window got stuck over other windows at top left

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

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

[Bug 1867977] Re: [amdgpu] Gnome shell crashed when attempt to lock screen / open app drawer with an active window

[Max Loh]

Here's the result of apport-cli /var/crash/_usr_bin_gnome-
shell.1000.crash

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868046

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

Title:
  [amdgpu] Gnome shell crashed when attempt to lock screen / open app
  drawer with an active window

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

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

[Bug 1867977] Re: [amdgpu] Gnome shell crashed when attempt to lock screen / open app drawer with an active window

[Max Loh]

There was nothing related to the crash I encounter in
https://errors.ubuntu.com/user/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/1867977

Title:
  [amdgpu] Gnome shell crashed when attempt to lock screen / open app
  drawer with an active window

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

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

[Bug 1867977] Re: [amdgpu] Gnome shell crashed when attempt to lock screen / open app drawer with an active window

[Max Loh]

If I look into /var/crash/ folder, the closest filename match I found is 
_usr_bin_gnome-shell.1000.crash
Is that the right file to run the command?

When I encounter crash, there was no report dialog, but I saw a thick
blank border around windows. Does it means that Gnome didn't crash but
just restarts itself?

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

Title:
  [amdgpu] Gnome shell crashed when attempt to lock screen / open app
  drawer with an active window

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

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

[Bug 1867977] Re: Gnome shell crashed when attempt to lock screen / open app drawer with an active window

[Max Loh]

There was actually something like this in error log generated by
journalctl -b0

But I can't find these lines in log generated by ubuntu-bug


```
Mar 19 12:23:08 ubuntu-desktop gnome-shell[26624]: JS WARNING: 
[resource:///org/gnome/gjs/modules/signals.js 135]: Too many arguments to 
method Clutter.Actor.destroy: expected 0, got 1
Mar 19 12:23:08 ubuntu-desktop kernel: gnome-shell[26624]: segfault at 61626786 
ip 7feee2b5b0b0 sp 7fff2fd76a28 error 4 in 
libgobject-2.0.so.0.6200.1[7feee2b3+33000]
Mar 19 12:23:08 ubuntu-desktop kernel: Code: fc 03 00 00 77 3c 48 c1 e8 02 48 
8d 15 69 32 02 00 48 8b 04 c2 48 81 fe fc 03 00 00 76 31 48 83 e6 fc 45 31 c0 
48 85 c0 74 0e  40 16 04 74 05 48 85 f6 75 35 45 31 c0 44 89 c0 c3 66 0f 1f 
44
Mar 19 12:23:08 ubuntu-desktop systemd[8684]: gnome-shell-x11.service: Main 
process exited, code=killed, status=11/SEGV
Mar 19 12:23:08 ubuntu-desktop polkitd(authority=local)[1214]: Unregistered 
Authentication Agent for unix-session:13 (system bus name :1.3180, object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_HK.UTF-8) 
(disconnected from bus)
Mar 19 12:23:08 ubuntu-desktop gsd-media-keys[22316]: Couldn't lock screen: 
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected 
from message bus without replying
Mar 19 12:23:08 ubuntu-desktop systemd[8684]: gnome-shell-x11.service: Failed 
with result 'signal'.
Mar 19 12:23:08 ubuntu-desktop systemd[8684]: gnome-shell-x11.service: Service 
has no hold-off time (RestartSec=0), scheduling restart.
Mar 19 12:23:08 ubuntu-desktop systemd[8684]: gnome-shell-x11.service: 
Scheduled restart job, restart counter is at 3.
Mar 19 12:23:08 ubuntu-desktop systemd[8684]: Stopped target GNOME X11 Session 
(session: ubuntu).
Mar 19 12:23:08 ubuntu-desktop systemd[8684]: Stopping GNOME X11 Session 
(session: ubuntu).
Mar 19 12:23:08 ubuntu-desktop systemd[8684]: Stopped target GNOME X11 Session.
Mar 19 12:23:08 ubuntu-desktop systemd[8684]: Stopping GNOME X11 Session.
Mar 19 12:23:08 ubuntu-desktop systemd[8684]: Stopped target GNOME Shell on X11.
Mar 19 12:23:08 ubuntu-desktop systemd[8684]: Stopping GNOME Shell on X11.
Mar 19 12:23:08 ubuntu-desktop systemd[8684]: Stopped GNOME Shell on X11.
Mar 19 12:23:08 ubuntu-desktop systemd[8684]: Starting GNOME Shell on X11...
```

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

Title:
  [amdgpu] Gnome shell crashed when attempt to lock screen / open app
  drawer with an active window

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

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

[Bug 1867977] Re: Gnome shell crashed when attempt to lock screen / open app drawer with an active window

[Max Loh]

The bug may be Ubuntu-specific, as I did not encounter any crash yet in
regular gnome session (the gnome-session package)

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

Title:
  [amdgpu] Gnome shell crashed when attempt to lock screen / open app
  drawer with an active window

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

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

[Bug 1868035] [NEW] Gnome shell crashed when attempt to lock screen / open app drawer with an active window

[Max Loh]

*** This bug is a duplicate of bug 1867977 ***
https://bugs.launchpad.net/bugs/1867977

Public bug reported:

Please refer to https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1867977

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
Uname: Linux 5.3.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 19 12:14:55 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-03-14 (4 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan

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

Title:
  Gnome shell crashed when attempt to lock screen / open app drawer with
  an active window

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

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

[Bug 1867977] Re: Gnome shell crashed when attempt to lock screen / open app drawer with an active window

[Max Loh]

I ran the command "ubuntu-bug gnome-shell" right after the bug happens.

Here's the log generated: https://bugs.launchpad.net/ubuntu/+source
/gnome-shell/+bug/1868035

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

Title:
  Gnome shell crashed when attempt to lock screen / open app drawer with
  an active window

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

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

[Bug 1867977] Re: Gnome shell crashed when attempt to lock screen / open app drawer with an active window

[Max Loh]

** Summary changed:

- Gnome shell crashed when attempt to lock screen with Win + L with an active 
window
+ Gnome shell crashed when attempt to lock screen / open app drawer with an 
active window

** Description changed:

- Whenever I press Win + L with a active/focused window (e.g. terminal),
- Gnome shell crashes.
+ Step to reproduce the bug
+ 
+ 1. Have a active/focused window (e.g. terminal)
+ 
+ 2. lock screen with Win + L / press the bottom left "Show application"
+ button
+ 
+ 
+ After that, Gnome shell crashes.
+ 
+ 
+ I have Ubuntu 19.10 with GNOME Shell 3.34.1

** Description changed:

  Step to reproduce the bug
  
  1. Have a active/focused window (e.g. terminal)
  
- 2. lock screen with Win + L / press the bottom left "Show application"
- button
- 
+ 2. Try to lock screen with Win + L / press the bottom left "Show
+ application" button
  
  After that, Gnome shell crashes.
  
- 
  I have Ubuntu 19.10 with GNOME Shell 3.34.1

** Description changed:

  Step to reproduce the bug
  
  1. Have a active/focused window (e.g. terminal)
  
- 2. Try to lock screen with Win + L / press the bottom left "Show
- application" button
+ 2. Press the bottom left "Show application" button / try to lock the
+ screen with Win + L shortcut key
  
  After that, Gnome shell crashes.
  
+ 
  I have Ubuntu 19.10 with GNOME Shell 3.34.1

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

Title:
  Gnome shell crashed when attempt to lock screen / open app drawer with
  an active window

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

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

[Bug 1867977] Re: Gnome shell crashed when attempt to lock screen with Win + L with a terminal window

[Max Loh]

Update: turns out that Gnome will if there are output in the terminal
doesn't cause the crash

As long as I press Win + L with an active/focused window, Gnome would
crash.

** Description changed:

- Steps to reproduce the bug:
- 
- 1. Open a terminal window
- 
- 2. Type something and press "Enter", e.g. "aaa" (Gnome will only crash
- when there are output in the terminal window)
- 
- 3. Press Win + L with terminal as the active window
- 
- 
- After that, Gnome shell will crash.
+ Whenever I press Win + L with a active/focused window (e.g. terminal),
+ Gnome shell crashes.

** Summary changed:

- Gnome shell crashed when attempt to lock screen with Win + L with a terminal 
window
+ Gnome shell crashed when attempt to lock screen with Win + L with an active 
window

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

Title:
  Gnome shell crashed when attempt to lock screen with Win + L with an
  active window

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

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

[Bug 1867977] Re: Gnome shell crashed when attempt to lock screen with Win + L with a terminal window

[Max Loh]

Here are the error log generated from journalctl -b0

The most recent crash happens at Mar 19 03:30

** Attachment added: "log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867977/+attachment/5338502/+files/log.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/1867977

Title:
  Gnome shell crashed when attempt to lock screen with Win + L with a
  terminal window

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

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

[Bug 1867977] [NEW] Gnome shell crashed when attempt to lock screen with Win + L with a terminal window

[Max Loh]

Public bug reported:

Steps to reproduce the bug:

1. Open a terminal window

2. Type something and press "Enter", e.g. "aaa" (Gnome will only crash
when there are output in the terminal window)

3. Press Win + L with terminal as the active window


After that, Gnome shell will crash.

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

** Attachment added: "Steps to reproduce the bug"
   
https://bugs.launchpad.net/bugs/1867977/+attachment/5338501/+files/Screenshot%20from%202020-03-19%2003-24-54.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/1867977

Title:
  Gnome shell crashed when attempt to lock screen with Win + L with a
  terminal window

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

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

[Bug 1857656] Re: [resource:///org/gnome/gjs/modules/signals.js 135]: Too many arguments to method Clutter.Actor.destroy: expected 0, got 1

[Max Loh]

I experience this bug too.

Gnome crashed while I attempt to login by pressing Win + L

Here are the log generated from the command

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857656/+attachment/5338283/+files/journal.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/1857656

Title:
  [resource:///org/gnome/gjs/modules/signals.js 135]: Too many arguments
  to method Clutter.Actor.destroy: expected 0, got 1

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

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

[Bug 1857335] Re: System volume slider only works between ~90% and 100%.

[Max Waterman]

I had to install 'pavucontrol' and it exhibited the same behaviour, as
does the 'top panel control' (if I understand that correctly). I
couldn't find 'keus' though.

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

Title:
  System volume slider only works between ~90% and 100%.

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

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

[Bug 1865862] [NEW] 'sound' settings require changing device and back again

[Max Waterman]

Public bug reported:

I have two actual audio devices plugged in: 1. speaker under my monitor
plugged into the 3.5mm headphone jack, 2. a set of USB headphones.

The 'Sound' settings panel shows three devices:
1. Headphones - built in audio
2. Digital output (s/pdif) - Jambra UC Voice 750 MS
3. Headphones - Jambra UC Voice 750 MS

(I don't really know what 2 is - I usually ignore it)

Normally, after plugging the headphones in, it has 3 selected, but the
'Test' button still plays through 1.

I have to change the 'output device' to 1, then back to 3 in order to
make it work on 3.

So, this bug is that the control centre does not reflect reality when
you launch it. It looks like it is automatically selecting the
headphones just plugged in, but it hasn't actually changed.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-control-center 1:3.34.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8.4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar  3 17:59:30 2020
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2019-07-19 (227 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to eoan on 2019-10-28 (127 days ago)

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


** Tags: amd64 apport-bug eoan

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

Title:
  'sound' settings require changing device and back again

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

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

[Bug 1857335] Re: System volume slider only works between ~90% and 100%.

[Max Waterman]

FWIW, the speaker works fine on a Huawei Mate 30 Pro/Android 10.

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

Title:
  System volume slider only works between ~90% and 100%.

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

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

[Bug 1857335] [NEW] System volume slider only works between ~90% and 100%.

[Max Waterman]

Public bug reported:

This is only with my USB 2.0 speaker[1] - with other devices, it works
fine and the slider's 0% corresponds to silent and 100% full. With my
USB 2.0 speaker, with the 'output' set to 'Analogue Output - USB2.0
Device', it only has an effect between about 90% and 100%.

I took a video of the problem and uploaded it here:

http://davidmaxwaterman.fastmail.co.uk/xfer/ubuntu_volume_problem.mp4

[1]
https://www.amazon.co.uk/gp/product/B07W1KN1XD/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8=1

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-control-center 1:3.34.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 23 10:00:17 2019
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2019-07-19 (156 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to eoan on 2019-10-28 (56 days ago)

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


** Tags: amd64 apport-bug eoan

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

Title:
  System volume slider only works between ~90% and 100%.

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

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

[Bug 1775302] Re: /usr/bin/eog:*** Error in `eog': corrupted size vs. prev_size: ADDR ***

[Max Wittal]

I think the more files you already have in the folder the higher the
chance that another new file will trigger the bug. The more time it
needs to sort the list the more time for the race condition to occur,
and each new file is another shot.

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

Title:
  /usr/bin/eog:*** Error in `eog': corrupted size vs. prev_size: ADDR
  ***

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

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

[Bug 1775302] Re: /usr/bin/eog:*** Error in `eog': corrupted size vs. prev_size: ADDR ***

[Max Wittal]

No plugins as far as I know. Also no UI elements.

It doesn't look like a segfault, but rather a failed assert() in glibc.

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

Title:
  /usr/bin/eog:*** Error in `eog': corrupted size vs. prev_size: ADDR
  ***

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

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

[Bug 1775302] Re: /usr/bin/eog:*** Error in `eog': corrupted size vs. prev_size: ADDR ***

[Max Wittal]

https://errors.ubuntu.com/oops/b9742d32-072f-11ea-aff5-fa163e983629
https://errors.ubuntu.com/oops/4c711916-072a-11ea-b6b3-fa163e102db1

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

Title:
  /usr/bin/eog:*** Error in `eog': corrupted size vs. prev_size: ADDR
  ***

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

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

[Bug 1775302] Re: /usr/bin/eog:*** Error in `eog': corrupted size vs. prev_size: ADDR ***

[Max Wittal]

I'm running Ubuntu 19.04, and I did send the bug report.

It is 100% reproducible, I have a folder which an application is writing
about ~100 new PNG images per second into (ie. new image files added to
the folder), up to about 100,000 images. If I try to open one of those
images _during_ this process the bug is triggered 100%. If I open an
image after the process is finished it works just fine.

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

Title:
  /usr/bin/eog:*** Error in `eog': corrupted size vs. prev_size: ADDR
  ***

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

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

[Bug 1775302] Re: /usr/bin/eog:*** Error in `eog': corrupted size vs. prev_size: ADDR ***

[Max Wittal]

This bug is triggered when many new files are added to the folder in
which an image is opened.

(eog:6555): GLib-WARNING **: 23:38:42.199: Accessing a sequence while it
is being sorted or searched is not allowed

(eog:6555): GLib-WARNING **: 23:38:42.200: Accessing a sequence while it is 
being sorted or searched is not allowed
corrupted size vs. prev_size
Aborted (core dumped)

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

Title:
  /usr/bin/eog:*** Error in `eog': corrupted size vs. prev_size: ADDR
  ***

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

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

[Bug 1844354] Re: Starting indicator-multiload (with peculiar config) crashes gnome-shell

[max ulidtko]

Daniel, yes, this is the same crash as in bug 1787512.

It's not a duplicate IMO, since I'd researched the exact repro steps.
Any developer can trigger the crash now, by following the repro steps.

That's why I didn't use ubuntu-bug either; just follow the repro steps
and trigger the crash yourself, rather than blankly staring at my
recording of it.


** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => New

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

Title:
  Starting indicator-multiload (with peculiar config) crashes gnome-
  shell

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

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

[Bug 1844354] Re: Starting indicator-multiload (with peculiar config) crashes gnome-shell

[max ulidtko]

Please NOTE: the report is against gnome-shell, NOT indicator-multiload!

It's not so important to fix the indicator app. Rather, gnome-shell
needs to become sturdier.

There's a change to be made to gnome-shell so that it perseveres
assertion failures and keeps running.

Lurking around, I've seen plentiful variations of gnome-shell assertion-
crashing posted, with varying backtraces. I've also personally
witnessed, on multiple occasions, "Ubuntu dying" as they say, with very
similar symptoms and the exact same workaround, mv ~/.config{,.bugz}.

Mind that, in each of that crash story, reported and not, we've caused
suffering and disappointment in hundreds of people. The data is there at
errors.ubuntu.com waiting for you to check out.

Now that I've spent a day unearthing a concrete working reproducer, can
I expect a *PROPER FIX* for this disaster, not just a measly patch-over
as dozens of bugs before?

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

Title:
  Starting indicator-multiload (with peculiar config) crashes gnome-
  shell

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

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

[Bug 1787512] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from gtk_icon_info_load_icon_finish() ["assertion failed

[max ulidtko]

Hey Daniel! I hope you'll take a look here:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844354

TL;DR: I'd distilled the issue and worked out a gnome-shell crasher to
reproduce this in clean VM.

Hope that helps.

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort()
  from g_assertion_message() from g_assertion_message_expr() from
  gtk_icon_info_load_icon_finish() ["assertion failed:
  (icon_info_get_pixbuf_ready (icon_info))"]

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

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

[Bug 1844354] Re: Starting indicator-multiload crashes gnome-shell

[max ulidtko]

Repro steps have been verified in clean VM and now refined to include
the crasher.

** Description changed:

  ## Steps to reproduce ##
  
- 1. On bionic, apt install -y indicator-multiload
- 2. Run indicator-multiload
+ 1. On bionic, apt install -y indicator-multiload dconf-editor
+ 2. dconf load /de/mh21/indicator-multiload/ < crasher.dconf-dump
+ 3. Run indicator-multiload
  
  lsb_release -d: Ubuntu 18.04.3 LTS
  gnome-shell version: 3.28.4-0ubuntu18.04.1
  indicator-multiload version: 0.4-0ubuntu5
- 
  
  ## Actual result ##
  
  Whole desktop crashes.
  
  gnome-shell dies with SIGABRT, logging this assertion failure:
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787512
- 
  
  ## Expected result ##
  
  An applet appears, showing CPU/RAM load graphs.
  
  If not that -- an error is reported.
  
  If not that -- gnome-shell continues to work, rather than crashing and
  destroying everything unsaved I've been working on.
  
  The desktop should not crash because of one shitty program. Especially
- so if that program puts itself into ~/.config/autostart -- effectively
- rendering the OS dead to a simpleton user.
+ so if that program has put itself into ~/.config/autostart --
+ effectively rendering the OS dead to a simpleton user.

** Attachment added: "A presumably invalid, or corrupt, dconf fragment for 
indicator-multiload"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844354/+attachment/5289194/+files/crasher.dconf-dump

** Summary changed:

- Starting indicator-multiload crashes gnome-shell
+ Starting indicator-multiload (with peculiar config) crashes gnome-shell

** Description changed:

  ## Steps to reproduce ##
  
  1. On bionic, apt install -y indicator-multiload dconf-editor
  2. dconf load /de/mh21/indicator-multiload/ < crasher.dconf-dump
  3. Run indicator-multiload
- 
- lsb_release -d: Ubuntu 18.04.3 LTS
- gnome-shell version: 3.28.4-0ubuntu18.04.1
- indicator-multiload version: 0.4-0ubuntu5
  
  ## Actual result ##
  
  Whole desktop crashes.
  
  gnome-shell dies with SIGABRT, logging this assertion failure:
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787512
  
  ## Expected result ##
  
  An applet appears, showing CPU/RAM load graphs.
  
  If not that -- an error is reported.
  
  If not that -- gnome-shell continues to work, rather than crashing and
  destroying everything unsaved I've been working on.
  
  The desktop should not crash because of one shitty program. Especially
  so if that program has put itself into ~/.config/autostart --
  effectively rendering the OS dead to a simpleton user.
+ 
+ 
+ lsb_release -d: Ubuntu 18.04.3 LTS
+ gnome-shell version: 3.28.4-0ubuntu18.04.1
+ indicator-multiload version: 0.4-0ubuntu5

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

Title:
  Starting indicator-multiload (with peculiar config) crashes gnome-
  shell

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

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

[Bug 1844354] Re: Starting indicator-multiload crashes gnome-shell

[max ulidtko]

Also, I'd like to see feedback from @vanvugt (as he has triaged a lot of
gnome-shell crash reports), and Michael Hofmann  as the
original maintainer of indicator-multiload.

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

Title:
  Starting indicator-multiload crashes gnome-shell

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

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

[Bug 1844354] Re: Starting indicator-multiload crashes gnome-shell

[max ulidtko]

The repro steps aren't as exact as I'd like, since I found this on a
live machine with long history of rough usage (including wiping /var by
accident, and restoring from there), so the steps are a bit difficult to
isolate.

I'll try refining the steps as needed in a VM.

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

Title:
  Starting indicator-multiload crashes gnome-shell

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

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

[Bug 1844354] [NEW] Starting indicator-multiload crashes gnome-shell

[max ulidtko]

Public bug reported:

## Steps to reproduce ##

1. On bionic, apt install -y indicator-multiload
2. Run indicator-multiload

lsb_release -d: Ubuntu 18.04.3 LTS
gnome-shell version: 3.28.4-0ubuntu18.04.1
indicator-multiload version: 0.4-0ubuntu5


## Actual result ##

Whole desktop crashes.

gnome-shell dies with SIGABRT, logging this assertion failure:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787512


## Expected result ##

An applet appears, showing CPU/RAM load graphs.

If not that -- an error is reported.

If not that -- gnome-shell continues to work, rather than crashing and
destroying everything unsaved I've been working on.

The desktop should not crash because of one shitty program. Especially
so if that program puts itself into ~/.config/autostart -- effectively
rendering the OS dead to a simpleton user.

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


** Tags: 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/1844354

Title:
  Starting indicator-multiload crashes gnome-shell

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

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

[Bug 1787512] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from gtk_icon_info_load_icon_finish() ["assertion failed

[max ulidtko]

Found it.

In my case, this crash was triggered by .config/autostart/indicator-
multiload.desktop

If I rm the autostart file, gnome-shell logs in and works fine.

If run directly, indicator-multiload crashes gnome-shell. Package
version 0.4-0ubuntu5.

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort()
  from g_assertion_message() from g_assertion_message_expr() from
  gtk_icon_info_load_icon_finish() ["assertion failed:
  (icon_info_get_pixbuf_ready (icon_info))"]

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

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

[Bug 1787512] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from gtk_icon_info_load_icon_finish() ["assertion failed

[max ulidtko]

Nope, it didn't work.

Neither did this, the same failed assertion crash persisted:

gsettings set org.gnome.desktop.search-providers disabled
"['org.gnome.Nautilus.desktop']"

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort()
  from g_assertion_message() from g_assertion_message_expr() from
  gtk_icon_info_load_icon_finish() ["assertion failed:
  (icon_info_get_pixbuf_ready (icon_info))"]

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

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

[Bug 1787512] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from gtk_icon_info_load_icon_finish() ["assertion failed

[max ulidtko]

@vanvugt hi! Nice triage, appreciated.

Confirming I now have had this on 18.04, gnome-shell version
3.28.4-0ubuntu18.04.1.

*Removing or renaming $HOME/.config*, as a universal workaround, also
works in this case.

I'm going to test if disabling search-providers (as mentioned in
#1722599) helps, with the (I suspect, corrupted) $HOME/.config in place
intact. Since gnome-shell crashes and any GUI isn't accessible, here's
the gsettings command doing the equivalent:

gsettings set org.gnome.desktop.search-providers disable-external
true

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort()
  from g_assertion_message() from g_assertion_message_expr() from
  gtk_icon_info_load_icon_finish() ["assertion failed:
  (icon_info_get_pixbuf_ready (icon_info))"]

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

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

[Bug 1666681] Re: Restore interactive_search.patch (type-ahead search)

[Max]

https://gitlab.gnome.org/GNOME/nautilus/issues/1157

** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1157
   https://gitlab.gnome.org/GNOME/nautilus/issues/1157

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

Title:
  Restore interactive_search.patch (type-ahead search)

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

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

[Bug 1666681] Re: Restore interactive_search.patch (type-ahead search)

[Max]

Related bug in official nautilus repo

https://gitlab.gnome.org/GNOME/nautilus/issues/244

** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #244
   https://gitlab.gnome.org/GNOME/nautilus/issues/244

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

Title:
  Restore interactive_search.patch (type-ahead search)

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

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

[Bug 1505774] Re: Feature request: Display each network adapter in network history graph

[Max Waterman]

I agree with this.

I almost always use a VPN, and it seems to me like 'Network History' is
adding together the bandwidth for all interfaces. The effect of this is
that it shows double the bandwidth when I am connected to VPN compared
to when I am not connected. I presume it is adding both wlp58s0 and tun0
- or something to that effect.

I am using expressvpn, and speedtest.net to measure.

I would expect 'network history' to use the device associated with tun0.
If anything, I would expect it to show /less/ bandwidth when connected
to VPN (due to the overhead), but certainly not more.

Ideally, I'd like options - to select the interface, take the default
route interface, or show them all, like in this request.

At least, it should be clear about which interface is being measured, or
however else it is being calculated.

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

Title:
  Feature request: Display each network adapter in network history graph

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

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

[Bug 1292398] Re: Second screen position isn't saved from one session to another

[Max]

Using lightdm and xfce this problem exists as well. Additionally with
this setup there are no monitors.xml in ~/.config. Although the login
screen is on the main monitor, which is awkward.

There are also other slightly funny situations, as when closing the lid
on laptop then connecting laptop to additional monitors, the monitor
setup is sometimes(?) restored. That is most likely due to that laptop
was earlier connected to these monitors, then disconnected and then
later connected again.

Still really annoying bug when using laptop on- and off-site.

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

Title:
  Second screen position isn't saved from one session to another

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

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

[Bug 1729539] Re: copy/paste failed in gedit after a few hours of work

[Jean-Max Reymond]

It works now since 4 days.

** Changed in: gedit (Ubuntu)
   Status: New => Invalid

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

Title:
  copy/paste failed in gedit after a few hours of work

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

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

[Bug 1764724] Re: logn(x) parsed as log(n)(x)

[Max Marrone]

Done.  https://gitlab.gnome.org/GNOME/gnome-calculator/issues/92

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

Title:
  logn(x) parsed as log(n)(x)

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

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

[Bug 1738500] Re: Ctrl+Shift+E not working in Bionic

[max mallok]

For everyone who wants a command line solution:

gsettings set org.freedesktop.ibus.panel.emoji hotkey '[]'

kind regards,
iPUSH

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

Title:
  Ctrl+Shift+E not working in Bionic

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

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

[Bug 1370953] Re: layout switch is delayed

[Max]

I'm experiencing same bug on elementary OS 5.0. It really driving me nuts.
Added initial bounty on this.
https://www.bountysource.com/issues/63898369-slow-keyboard-layouts-switch

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

Title:
  layout switch is delayed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+subscriptions

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

[Bug 1729539] Re: copy/paste failed in gedit after a few hours of work

[Jean-Max Reymond]

it seems that it is the same bug as #1745907

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

Title:
  copy/paste failed in gedit after a few hours of work

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

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

[Bug 1729539] Re: copy/paste failed in gedit after a few hours of work

[Jean-Max Reymond]

same bug with ubuntu 18.04.1

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

Title:
  copy/paste failed in gedit after a few hours of work

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

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

[Bug 1730092] Re: package emacs25 25.2+1-6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Max Kaehn]

I got it working again on Ubuntu 18.04.1 by using Synaptic to reinstall
supporting libraries like otf and m17.

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

Title:
  package emacs25 25.2+1-6 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

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

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

[Bug 1777980] Re: crash of gedit while selecting all the text

[Jean-Max Reymond]

** Changed in: gedit (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  crash of gedit while selecting all the text

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

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

[Bug 854959] Re: Connect to windows share: gvfs slow, smbclient fast

[Max]

still present in 18.04

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

Title:
  Connect to windows share: gvfs slow, smbclient fast

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

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

[Bug 1777980] [NEW] crash of gedit while selecting all the text

[Jean-Max Reymond]

Public bug reported:

I select all the text in gedit with Ctrl A and console reports:

xkbcommon: ERROR: (input string):1:1: syntax error
xkbcommon: ERROR: Failed to parse input xkb string

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gedit 3.28.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 21 06:24:52 2018
InstallationDate: Installed on 2018-06-16 (4 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gedit
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  crash of gedit while selecting all the text

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

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

[Bug 1764724] [NEW] logn(x) parsed as log(n)(x)

[Max Marrone]

Public bug reported:

"logn" is common notation for log base n, e.g. log2(x) is log base 2 of
x.

gnome-calculator appears to always parse this notation as log(n)(x).
So, log10(2) is log(10)(2) = 2, rather than log10(2) ~= 0.301.

Arbitrary bases are already supported if the base is input as a
subscript.  But, typing the base without subscript is common enough that
it should be accounted for.  gnome-calculator should at least show an
error like "function 'log10' is not defined," to avoid silently
reporting incorrect results.


Ubuntu 17.10, gnome-calculator 3.25.92.

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

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

Title:
  logn(x) parsed as log(n)(x)

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

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

[Bug 1762261] [NEW] Bug in Ubuntu patch for synaptics support prevents me configuring my touchpad same as previous Ubuntu releases

[Max Bowsher]

Public bug reported:

Touchpad handling appears to have been refactored somewhat in bionic -
which led to the surprise of having my settings changed on upgrade 
but even when I tracked down the new gsettings property of
org.gnome.desktop.peripherals.touchpad click-method, it fails to behave
as documented, so I cannot get the behaviour I want, and had before.

The code in function meta_input_settings_x11_set_click_method_synaptics
added by the patch interprets click-method 'default' as setting specific
settings.

However, the gsettings schema description says 'default' should mean
"left as hardware default".

Please change the patch to follow that, and not change the settings at
all - as having a way to tell mutter to get out of the way and let the
user configure their own settings is more useful than insisting on
applying a given hardcoded choice.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: mutter 3.28.0-2
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr  8 23:49:12 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-08-16 (600 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: mutter
UpgradeStatus: Upgraded to bionic on 2018-04-04 (3 days ago)

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


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

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

Title:
  Bug in Ubuntu patch for synaptics support prevents me configuring my
  touchpad same as previous Ubuntu releases

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

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

[Bug 1730174] Re: [artful] mouse clicks are completely ignored both in Gnome's gdm and once logged in to the desktop

[Max Rumpf]

Update: So, no, EnableWayland=false didn't really fix the issue here.
Instead of the mouse being not clickable in gdm and gnome shell, gdm
works fine, but once I log in, I have artifacts all over the place
(greenish squares, single pixels from the normal image, etc). Leaving
EnableWayland=false commented out, but starting a X.org session from the
gear menu in gdm makes it work again.

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

Title:
  [artful] mouse clicks are completely ignored both in Gnome's gdm and
  once logged in to the desktop

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

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

[Bug 1730174] Re: [artful] mouse clicks are completely ignored both in Gnome's gdm and once logged in to the desktop

[Max Rumpf]

This bug also affects me. However, I don't use nvidia drivers, but mesa, since 
I have a AMD Radeon Vega 56.
Setting EnableWayland to false fixed the issue for me.
The bug occurred after updating a lot of packages today, including dbus, mesa, 
etc. I'm using the mesa drivers from the joe-yasi ppa.

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

Title:
  [artful] mouse clicks are completely ignored both in Gnome's gdm and
  once logged in to the desktop

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

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

[Bug 1746527] [NEW] Systemd User Service Cannot Start with ECryptFS Due to PAM Misconfiguration

[Max Ehrlich]

Public bug reported:

If a user encrypts their home directory using the standard Ubuntu
installer GUI, which uses ecryptfs, then the users home directory is
encrypted while systemd is trying to start their user services so they
cant be read. After consulting with the systemd developers, the problem
is remarkably simple to fix

Ubuntu releases /etc/pam.d/common-session with the follow entries:

session optionalpam_systemd.so
session optionalpam_ecryptfs.so unwrap

they need to be swapped to

session optionalpam_ecryptfs.so unwrap
session optionalpam_systemd.so

so that decryption happens before systemd user services are started.

Check the thread on the systemd developers mailing list at
https://lists.freedesktop.org/archives/systemd-
devel/2018-January/040301.html for further information

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu12.1
Uname: Linux 4.14.4-acso x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 31 09:25:10 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-11-04 (87 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Dell Inc. XPS 15 9560
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.14.4-acso 
root=/dev/mapper/ubuntu--vg-root ro quiet splash intel_iommu=on pci=noaer 
pcie_acs_override=downstream vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/30/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.0
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug artful

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

Title:
  Systemd User Service Cannot Start with ECryptFS Due to PAM
  Misconfiguration

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

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

[Bug 1264368] Re: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c

[Max]

Ubuntu:: 16.04.3
gnome-screensaver :: 3.6.1-7ubuntu4
libglib2.0-0:i386 :: 2.48.2-0ubuntu1

Another example:
org.gnome.ScreenSaver[1963]: (gnome-screensaver:2131): GLib-CRITICAL **: Source 
ID 4988 was not found when attempting to remove it

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

Title:
  GLib-CRITICAL **: Source ID was not found when attempting to remove it
  - warning when leaving Network menu of g-c-c

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

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

[Bug 1729326] Re: Following upgrade to 17.10 Fugi X20 not mounted

[Max Goodman]

Manually installing the libgphoto2 2.5.16 package in the bionic-proposed
repo fixed this issue for me.
https://launchpad.net/ubuntu/+source/libgphoto2/2.5.16-1

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

Title:
  Following upgrade to 17.10 Fugi X20 not mounted

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

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

[Bug 1729326] Re: Following upgrade to 17.10 Fugi X20 not mounted

[Max Goodman]

It looks like this was fixed upstream:

https://github.com/gphoto/libgphoto2/commit/472a9461b457b4d08ecf10a93bb7f1efdc2124c0

via
https://bugzilla.opensuse.org/show_bug.cgi?id=1048853
https://build.opensuse.org/package/view_file/openSUSE:Factory/libgphoto2/libgphoto2-fix-fuji.patch?rev=1a990f4295b7f4bbd99331eebd0752e0

** Bug watch added: bugzilla.opensuse.org/ #1048853
   https://bugzilla.opensuse.org/show_bug.cgi?id=1048853

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

Title:
  Following upgrade to 17.10 Fugi X20 not mounted

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

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

[Bug 1729326] Re: Following upgrade to 17.10 Fugi X20 not mounted

[Max Goodman]

I'm experiencing the same error w/ a Fujifilm X-T2.

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

Title:
  Following upgrade to 17.10 Fugi X20 not mounted

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

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

[Bug 1715811] Re: GDM crash loop Ubuntu 17.10 (Intel)

[Max Goodman]

I ran into this upgrading from 17.04 to 17.10 on an X1 Carbon 3rd Gen
(Intel HD Graphics 5500). Inspired by reading Mentis's comment. This
fixed it for me:

apt purge gdm gdm3
apt install gdm3 ubuntu-desktop (reinstalling ubuntu-desktop which got removed 
in the last step)

Then running `systemctl restart gdm` got gdm3 to start successfully. Is
it possible lingering config files from gdm (version 2?) are conflicting
with gdm3 on some upgraded machines?

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

Title:
  GDM crash loop Ubuntu 17.10 (Intel)

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

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

[Bug 1729539] Re: copy/paste failed in gedit after a few hours of work

[Jean-Max Reymond]

the bug in GNOME Bugzilla :
https://bugzilla.gnome.org/show_bug.cgi?id=789932

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

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

Title:
  copy/paste failed in gedit after a few hours of work

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

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

[Bug 1729539] [NEW] copy/paste failed in gedit after a few hours of work

[Jean-Max Reymond]

Public bug reported:

After a few hours of work, copy in gedit does not work with other applications. 
In clipit, no copied lines.
It is new with ubuntu 17.10

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gedit 3.22.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov  2 10:19:21 2017
InstallationDate: Installed on 2016-01-31 (640 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: gedit
UpgradeStatus: Upgraded to artful on 2017-10-28 (4 days ago)

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


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

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

Title:
  copy/paste failed in gedit after a few hours of work

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

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

[Bug 1722256] Re: Wifi connection status icon shows a "?" when connected

[Max Waterman]

https://bugzilla.gnome.org/show_bug.cgi?id=750260

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

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

Title:
  Wifi connection status icon shows a "?" when connected

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

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

[Bug 1723362] Re: gnome-software spams error messages to journald and causes 100% CPU usage

[Max D]

Same error shortly after boot and upgrade (could be coincidental):

Oct 15 15:38:08 XXX dbus-daemon[2685]: Activating service 
name='com.intel.dleyna-renderer'
Oct 15 15:38:08 XXX dleyna-renderer-service[5506]: dLeyna core version 0.4.0
Oct 15 15:38:08 XXX dleyna-renderer-service[5506]: dleyna-renderer-service 
version 0.4.0
Oct 15 15:38:09 XXX gnome-software[4142]: g_byte_array_remove_range: assertion 
'index_ + length <= array->len' failed
Oct 15 15:38:09 XXX gnome-software[4142]: Ignoring unexpected response

then the last two lines again and again :

Oct 15 15:38:10 XXX gnome-software[4142]: Ignoring unexpected response
Oct 15 15:38:10 XXX gnome-software[4142]: g_byte_array_remove_range: assertion 
'index_ + length <= array->len' failed


It filled my /var partition with a 5g syslog file in less than an hour. 
Computer almost completely  freeze (gradually, up to nothing responding at 
all). I managed to figure out that syslog was the issue, save it and delete it 
from /var just in time. "apt upgrade" was stuck for 10/15 minutes at " 
Generating /boot/initrd.img" step.

This bug might have had serious consequences.

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

Title:
  gnome-software spams error messages to journald and causes 100% CPU
  usage

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

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

[Bug 1716801] [NEW] Spurious creation of /stub-resolv.conf symlink

[Max Bowsher]

Public bug reported:

Code in /lib/systemd/system/systemd-resolved.service seeks to populate
/etc/resolv.conf if it is empty:

ExecStartPre=-+/bin/sh -c '[ ! -s /etc/resolv.conf ] && ln -snf
../run/systemd/resolve/stub-resolv.conf'


However the code is just wrong, and writes a symlink to /stub-resolv.conf 
rather than /etc/resolv.conf

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu9
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 13 00:55:32 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-08-16 (392 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: HP HP Spectre Notebook
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic 
root=UUID=4989886a-f95e-4802-ab51-dcbf53167aeb ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to artful on 2017-08-31 (12 days ago)
dmi.bios.date: 02/21/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.31
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81A0
dmi.board.vendor: HP
dmi.board.version: 48.54
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.31:bd02/21/2017:svnHP:pnHPSpectreNotebook:pvrType1ProductConfigId:rvnHP:rn81A0:rvr48.54:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
dmi.product.name: HP Spectre Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
modified.conffile..etc.systemd.resolved.conf: [modified]
mtime.conffile..etc.systemd.resolved.conf: 2017-09-02T14:44:21.354384

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


** Tags: amd64 apport-bug artful

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

Title:
  Spurious creation of /stub-resolv.conf symlink

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

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

[Bug 1164016] Re: restore type-ahead find

[Max D]

This is up to date again in 17.10

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

Title:
  restore type-ahead find

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

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

[Bug 1666681] Re: Drop interactive_search.patch (type-ahead search)

[Max D]

I definitely can't live without type-ahead. I just upgrade from 17.04
Ubuntu Gnome to default 17.10 to test it and Nautilus is unusable
without that feature.

I'm not sure why it can't be keep as default or optional behavior, but
it is a huge regression to me, and to many other users I suppose.

I've been using type-ahead search for years and there's no way I can
adapt to a search window opening each time I want to navigate folders. I
do agree with @mniess, Search and navigation really are too different
things.

Is there a way to downgrade nautilus to a usable version ?

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

Title:
  Drop interactive_search.patch (type-ahead search)

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

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

[Bug 1133477] Re: cut-n-paste move files got stuck forever

[max]

I experience the same problem with Ubuntu 16.04 on a samsung SSD. My kernel is 
4.4.0-79-generic
It happens when I move more than ~100 files even if mv does it immediately! Any 
clue of what is happening?

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

Title:
  cut-n-paste move files got stuck forever

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

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

[Bug 1666264] Re: FFe: Update gnome-terminal to 3.24 and vte to 0.48

[Max Ehrlich]

Just throwing my hat in the ring as absolutely no one of influence: I
think reverting functionality that is understood to be in a particular
version of a package is inviting breakage.

If VTE 0.48.x is understood to have PCRE2 support, as announced by the
VTE developers, then applications that depend on it are free to assume
they can use that functionality. If Ubuntu patches that out, then you
are going to break code that makes such an assumption. What's going on
with Tilix is a good example of this.

The best option here is #1, to add PCRE2 into main. Based on my reading
of #163, it really isn't that big a deal, but if the maintainers are
dead set against it, then do #2 leave gnome terminal and VTE at their
lower version numbers until there is more impetus to switch. #3 is
objectively the wrong decision.

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

Title:
  FFe: Update gnome-terminal to 3.24 and vte to 0.48

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

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

[Bug 1208993] Re: Ubuntu slows down and hangs while copying file from/to USB

[max]

I have this on ubuntu 17.04. It's very annoying; every time I copy large
files to/ from a USB drive the PC slows/ stutters until the copy has
finished

And I find it very surprising that this bug is still not assigned
despite being confirmed

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

Title:
  Ubuntu slows down and hangs while copying file from/to USB

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

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

[Bug 1664730] Re: GVFS violating UNIX permissions inside Samba shares

[Max-Ulrich Farber]

** Information type changed from Private Security to Public

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

Title:
  GVFS violating UNIX permissions inside Samba shares

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

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

[Bug 1581713] Re: Ubuntu Software always asks for an Ubuntu Single Sign-On account when installing or removing a snap package

[Max Kristen]

This really is annoying, and leads Desktop Users to believe that an
Ubuntu Acc is required to use the snap format. On another note: It is
also weird if people try to use Snappy Ubuntu Core, and need to have a
SSO Acc to start their machines..

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

Title:
  Ubuntu Software always asks for an Ubuntu Single Sign-On account when
  installing or removing a snap package

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

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

[Bug 1633162] Re: Files application throws an error 'Oops! Something went wrong' when clicked on 'Recents'

[Jean-Max Reymond]

as described in https://bugzilla.gnome.org/show_bug.cgi?id=773300

Adding "Environment=DISPLAY=:0" in the service file:
/usr/lib/systemd/user/gvfs-daemon.service, solves it.

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

Title:
  Files application throws an error 'Oops! Something went wrong' when
  clicked on 'Recents'

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

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

[Bug 1633162] Re: Files application throws an error 'Oops! Something went wrong' when clicked on 'Recents'

[Jean-Max Reymond]

same issue with regular user and update from 16.04 to 16.10

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

Title:
  Files application throws an error 'Oops! Something went wrong' when
  clicked on 'Recents'

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

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

[Bug 1485373] Re: Missing dependency - gnome-disk-utility needs cryptsetup

[max]

*** This bug is a duplicate of bug 1310174 ***
https://bugs.launchpad.net/bugs/1310174

I confirm this bug is still present in Ubuntu16.04-64 LTS!

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

Title:
  Missing dependency - gnome-disk-utility needs cryptsetup

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

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

[Bug 1633162] Re: Files application throws an error 'Oops! Something went wrong' when clicked on 'Recents'

[max]

I have the same issue. Let me know what information you need

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

Title:
  Files application throws an error 'Oops! Something went wrong' when
  clicked on 'Recents'

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

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

[Bug 1570227] Re: Open Recent Items show as always empty in Gedit

[Max Barry]

Looks like a Ubuntu issue to me, since in that Gnome bug, upstream says
recent files have been moved to beneath the "Open \/" button on gedit's
taskbar:

https://bugzilla.gnome.org/show_bug.cgi?id=742425#c3

And indeed they are there! However, on Ubuntu 16.04, gedit also has a
"File" -> "Open Recent" menu, which is now non-functional (it's always
empty).

It's a bit confusing since "File" -> "Open Recent" has always been the
way to find recent files. It should either be removed or work.

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

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

Title:
  Open Recent Items show as always empty in Gedit

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

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

[Bug 1472792] Re: evince does not open with broadway backend

[Max Chao]

** Tags added: xenial

** Package changed: gtk+3.0 (Ubuntu) => ubuntu

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

Title:
  evince does not open with broadway backend

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

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

[Bug 1367242] Re: File -> Send To... leads to error

[Max]

** Changed in: evince (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  File -> Send To... leads to error

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

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

[Bug 1577885] Re: 120sec delay during shutdown or reboot with still mounted cifs (via Wifi)

[Max-Ulrich Farber]

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

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

Title:
  120sec delay during shutdown or reboot with still mounted cifs (via
  Wifi)

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

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

[Bug 1292113] Re: CTRL+ALT+T - shortcut to open Terminal is does not work

[Max Waterman]

I see this problem in 16.04 after upgrading from 15.10.

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

Title:
  CTRL+ALT+T - shortcut to open Terminal is does not work

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

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

[Bug 1574191] Re: rhithmbox doesn't start in ubuntu 16.04

[Jean-Max Reymond]

works fine for me

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

Title:
  rhithmbox doesn't start in ubuntu 16.04

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

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

[Bug 1565537] Re: package gnome-menus 3.13.3-6ubuntu3 failed to install/upgrade: triggers looping, abandoned

[Max John]

*** This bug is a duplicate of bug 1510847 ***
https://bugs.launchpad.net/bugs/1510847

** This bug has been marked a duplicate of bug 1510847
   package gnome-menus 3.13.3-6ubuntu1 failed to install/upgrade: triggers 
looping, abandoned

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

Title:
  package gnome-menus 3.13.3-6ubuntu3 failed to install/upgrade:
  triggers looping, abandoned

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

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

[Bug 1573950] Re: package gnome-menus 3.13.3-6ubuntu3 failed to install/upgrade: triggers looping, abandoned

[Max John]

*** This bug is a duplicate of bug 1510847 ***
https://bugs.launchpad.net/bugs/1510847

** This bug has been marked a duplicate of bug 1510847
   package gnome-menus 3.13.3-6ubuntu1 failed to install/upgrade: triggers 
looping, abandoned

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

Title:
  package gnome-menus 3.13.3-6ubuntu3 failed to install/upgrade:
  triggers looping, abandoned

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

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

[Bug 1571664] Re: Cannot connect to guest Windows share

[Max]

@shinyblue: done

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

Title:
  Cannot connect to guest Windows share

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

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

[Bug 1571664] Re: Cannot connect to guest Windows share

[Max]

Confirm! The same problem. The same distro.

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

Title:
  Cannot connect to guest Windows share

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

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

[Bug 1565846] [NEW] gnome-terminal hides mouse pointer

[Max Waterman]

Public bug reported:

This is a problem when using gnome-terminal with focus-follow-mouse,
which is somewhat unusual.

It seems like gnome-terminal has a feature where it attempts to
declutter the screen by hiding the mouse pointer when it thinks it has
focus.

This seems to work ok under normal circumstances, but sometimes it seems
to not make the cursor visible again when it loses focus.

Here is an example of the situation I'm talking about :

(pointer means mouse pointer)

0) install unity tweak tool and use the Window Manager/Additional/Focus mode 
option to set 'focus mode' as 'mouse', and 'auto-raise' to 'off'
1) open a terminal
2) open chrome
3) move pointer over chrome and type
  chrome accepts input
  terminal doesn't and have cursor non-solid
4) move pointer over terminal and type
  chrome defocuses and doesn't accept input
  terminal accepts input, cursor turns solid, and pointer disappears
5) type alt-tab to send focus back to chrome and type

It is at this point that things can go wrong.

The 'correct' behaviour :
  chrome has focus and accepts input
  terminal doesn't accept input, cursor turns non-solid and pointer re-appears

However, when things 'go wrong' :
  chrome has focus and accepts input
  terminal doesn't accept input, cursor *remains solid* and pointer *remains 
hidden*

This leads to the situation where the user decides to change focus again
(pointer is hidden on top of terminal) but can't see where the pointer
is, and he/she moves the mouse around franticly trying to make it appear
again and/or see where it is (it can be difficult to see under normal
circumstances when it isn't moving).

My initial instinct is that there should be an option to stop the hiding
of the cursor, but while filing this bug, everything was working pretty
well, so perhaps this is actually bug and it should just be fixed.

I will attempt to pay closer attention to the situation leading up to
the problem and add comments here if I find anything. I notice other
people having trouble on ubuntu forums, though I suspect they're not
using focus-follows-mouse or have click-to-raise disabled, so perhaps
those aspects are 'red herrings' :



Description:Ubuntu 15.10
ii  gnome-terminal 3.16.2-1ubun amd64GNOME terminal emulator applicati
3.16.2-1ubuntu4

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

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

Title:
  gnome-terminal hides mouse pointer

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

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

[Bug 1236619] Re: gvfs smb / cifs file copy performance is terribly slow

[Max]

Changing one config in /etc/nsswitch.conf  appears to have fixed my
issue with this.

hosts:  files wins mdns4_minimal [NOTFOUND=return] dns


I did not discover this. Credit where credit is due.
http://charlieharvey.org.uk/page/slow_nautilus_browse_with_netbios

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

Title:
  gvfs smb / cifs file copy performance is terribly slow

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

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

[Bug 987986] Re: Cannot browse files via bluetooth on Android device

[Max Waterman]

still in 15.10 :(

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

Title:
  Cannot browse files via bluetooth on Android device

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

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

[Bug 1445595] Re: Empty trash from Launcher results in Nautilus window opening

[Joshua Max]

I've narrowed the problem down to https://bazaar.launchpad.net/~unity-
team/unity/trunk/view/head:/unity-shared/GnomeFileManager.cpp#L216.
Calling GnomeFileManager::Activate() from GnomeFileManager::EmptyTrash()
seems to no longer be necessary and causes Nautilus to open a window at
the user's home directory. Simpy removing the function call from my copy
of the unity sources fixes the problem with no side-effects as far as I
can tell.

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

Title:
  Empty trash from Launcher results in Nautilus window opening

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

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