[Bug 2003610] Re: Cannot log in, keeps asking username

[Ben White]

I had this same issue and mine was also a keyring/security issue. In my
case I had setup a PKI smart card to login to US DoD services from my
home computer, but forgot to remove the card after a reboot, so gdm3 was
trying to access the card. Once I removed the card and unplugged the
card reader I was able to login, but not before I had used TTY and
startx command to get to a desktop. So definitely check your credentials
management or keyring for this issue.

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

Title:
  Cannot log in, keeps asking username

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


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

[Bug 2027790] [NEW] bash completion doesn't show "remove" option

[Ben Aceler]

Public bug reported:

Flatpak package contains bash script for bash completion feature. If I
say `flatpak in`, I will got `info` and `install` options.

Flatpak autocomplete options doesn't work for `remove` option. If I say
`flatpak rem`, I will got only `remote`, and `remove` will not be
suggested.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: flatpak 1.14.4-1ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12
Uname: Linux 6.2.0-24-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 14 13:30:21 2023
ProcEnviron:
 LANG=ru_RU.UTF-8
 PATH=(custom, no user)
 SHELL=/usr/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: flatpak
UpgradeStatus: Upgraded to lunar on 2023-05-14 (60 days ago)

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


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

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

Title:
  bash completion doesn't show "remove" option

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


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

[Bug 1990277] [NEW] Nautilus crashes when open a new window from the panel

[Ben Aceler]

Public bug reported:

Nautilus can add it's favorites to the panel icon. So, the user can
right-click on an icon to open any favorites folder.

If a Nautilus windows is already open, opening any folder from favorites
crashes nautilus.

journalctl -e:
сен 20 15:32:42 Compy kernel: nautilus[107750]: segfault at 0 ip 
 sp 7ffe8815c688 error 14 in nautilus[5612a329f000+>
сен 20 15:32:42 Compy kernel: Code: Unable to access opcode bytes at RIP 
0xffd6.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nautilus 1:42.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 20 15:30:40 2022
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/usr/bin/fish
SourcePackage: nautilus
UpgradeStatus: Upgraded to jammy on 2022-06-08 (103 days ago)
usr_lib_nautilus:
 file-roller3.42.0-1
 nautilus-share 0.7.3-2ubuntu6

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


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

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

Title:
  Nautilus crashes when open a new window from the panel

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


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

[Bug 1978260] Re: Evolution not closing emails after sending

[Ben Romer]

This is probably a duplicate of
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1983794

Upstream bug report was closed and is here
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972

I was also affected by this bug. It seems to be an issue with
libcanberra-gtk3-module, which I had no real need for, so I was able to
uninstall and it appears to have solved the problem.

** Bug watch added: gitlab.gnome.org/GNOME/evolution/-/issues #1972
   https://gitlab.gnome.org/GNOME/evolution/-/issues/1972

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

Title:
  Evolution not closing emails after sending

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


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

[Bug 1980936] [NEW] Flatpaked apps doesn't start under wayland, if called from another app

[Ben Aceler]

Public bug reported:

I run Gnome Wayland session and I have several apps installed from
flatpak - gthumb and evince are among them.

If I download a file using a web-browser and try to open this file from
the browser's "download" menu, the PDF or JPG files won't open. I can
fix it by setting up evince or gthumb to run x11 by disabling wayland
with flatseal.

Web-browser is not installed by a flatpak or snap, so it can be vivaldi
or yandex-browser.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: flatpak 1.12.7-1
ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
Uname: Linux 5.15.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul  7 12:09:43 2022
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: flatpak
UpgradeStatus: Upgraded to jammy on 2022-06-08 (28 days ago)

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


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

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

Title:
  Flatpaked apps doesn't start under wayland, if called from another app

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


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

[Bug 1978707] [NEW] Dragging windows cause gnome-shell to hangs up temporarily

[Ben Aceler]

Public bug reported:

Ubuntu 22.04, upgraded from previous versions, AMD Ryzen 7 5700G
integrated video card, Wayland session.

Steps to reproduce:
1. Open an app window. I used Chromium, but can also reproduce with nautilus or 
even gnome-settings.
2. Move it constantly.

Expected behavior:
Window moves.

Actual behavior:
Whole gnome-shell session hangs up for a several seconds with a lot of "Stack 
trace for context" errors in the logs.

I attached a demo video.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.1-0ubuntu0.1
ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
Uname: Linux 5.15.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 14 19:59:38 2022
DisplayManager: gdm3
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42.1-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-06-08 (5 days ago)

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


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

** Attachment added: "Запись экрана от 14.06.2022 19:58:43.webm"
   
https://bugs.launchpad.net/bugs/1978707/+attachment/5597258/+files/%D0%97%D0%B0%D0%BF%D0%B8%D1%81%D1%8C%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%2014.06.2022%2019%3A58%3A43.webm

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

Title:
  Dragging windows cause gnome-shell to hangs up temporarily

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


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

[Bug 1969584] Re: Evolution does not allow editing email content on Wayland

[Ben.]

I just upgrade today to Jammy and replying to an email (html or text)
leave the text form empty then crashed evolution.

Version 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
evolution 3.44.0-1 

I switch to -proposed and it fixes the problem for me

evolution 3.44.0-1ubuntu1


I will try to add the tag verification-done-jammy as request to this ticket

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

Title:
  Evolution does not allow editing email content on Wayland

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


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

[Bug 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists

[Ben Aceler]

I can say, that I have this dialog only if I have a flatpak updates, not
apt updates.

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

Title:
  Ubuntu reboots instead of powering off if a software updates exists

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


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

[Bug 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists

[Ben Aceler]

As far as I can say, the dialog itself works as intended. The bug is,
that the Ubuntu box is rebooting instead of turninging off.

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

Title:
  Ubuntu reboots instead of powering off if a software updates exists

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


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

[Bug 1962346] [NEW] Ubuntu reboots instead of powering off if a software updates exists

[Ben Aceler]

Public bug reported:

When I want to turn off a computer, I got a checkbox "Install deferred
updates" (see screenshot, I'm not sure if my back-translation is
correct).

If the checkbox is checked, Ubuntu box reboots instead of powering off.
It is not "rebopot to install updates". It just reboots to desktop
again. If I uncheck the box, it powers off normally.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gnome-shell 40.5-1ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19
Uname: Linux 5.13.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 26 00:05:44 2022
DisplayManager: gdm3
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago)

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


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

** Attachment added: "Снимок экрана от 2022-02-01 11-25-20.png"
   
https://bugs.launchpad.net/bugs/1962346/+attachment/5563780/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202022-02-01%2011-25-20.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/1962346

Title:
  Ubuntu reboots instead of powering off if a software updates exists

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


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

[Bug 1927970] Re: Maximised gnome-terminal not returning to normal size

[Ben Hardill]

Looks like there is a matching upstream

https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/359

** Bug watch added: gitlab.gnome.org/GNOME/gnome-terminal/-/issues #359
   https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/359

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

Title:
  Maximised gnome-terminal not returning to normal size

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

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

[Bug 1927970] [NEW] Maximised gnome-terminal not returning to normal size

[Ben Hardill]

Public bug reported:

The default terminal size is 80x24

If the terminal is maximised then returned to normal by double clicking
on the title bar the terminal ends up being 79x23 the first time, 78x22
the second time and so on.

it can be reset by clicking on the burger menu -> advanced -> 80x24

I expect it to return to the same size it started at (80x24)

lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04


apt-cache policy gnome-terminal
gnome-terminal:
  Installed: 3.36.2-1ubuntu1~20.04
  Candidate: 3.36.2-1ubuntu1~20.04
  Version table:
 *** 3.36.2-1ubuntu1~20.04 500
500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 3.36.1.1-1ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-terminal 3.36.2-1ubuntu1~20.04
ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon May 10 14:37:05 2021
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00
ExecutablePath: /usr/libexec/gnome-terminal-server
InstallationDate: Installed on 2020-09-23 (228 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
ProcEnviron:
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to focal on 2021-03-16 (54 days ago)

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


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

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

Title:
  Maximised gnome-terminal not returning to normal size

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

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

[Bug 1919071] [NEW] Gsd media keys crashed SIGSEGV

[Ben Heron]

Public bug reported:

Hi there

Extremely new user and a newly built pc.

I’ve experienced some crashes / system locks and am hoping for some tips
and thoughts to help me out.

The error message I received last night is as follows:

Executable gsd-media-keys

Package gnome settings daemon 3.36.q

Title gsd media keys crashed with SIGSEGV in tcache get()

I’m on app version 2.20.11-0ubuntu27.16

On AMD with integrated graphics

I wondered if it was to do with the usb wireless HP keyboard? However
this morning I had Firefox crash. I am currently using WiFi via my ASUS
B450 onboard WiFi which again I wondered might be the cause?

Appreciate some help. I’m a little experienced with hardware and PCs
albeit very, very new to Ubuntu and Linux!

Appreciated

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

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

Title:
  Gsd media keys crashed SIGSEGV

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

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

[Bug 1909037] [NEW] Weird sorting occurs on numbers sequence filenames

[Ben Aceler]

Public bug reported:

I have a lot of files from the camera, named ACE_0001.nef, ACE_0002.nef
and so on. I imported these files into darktable. Darktable places a
corresponding xmp file near every nef file, resulting in
ACE_0001.nef.xmp, ACE_0002.nef.xmp and so on.

The problem is, for files less then 100 in numbers, xmp files are sorted
before nef files, but starting ACE_0100.nef* xmp files are sorted after
nef.

See attached screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.3-0ubuntu1
Uname: Linux 5.10.0-051000rc4-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 22 23:16:38 2020
InstallationDate: Installed on 2019-11-16 (402 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: Upgraded to focal on 2020-05-02 (234 days ago)
usr_lib_nautilus:

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


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

** Attachment added: "Снимок экрана от 2020-12-22 23-17-21.png"
   
https://bugs.launchpad.net/bugs/1909037/+attachment/5445993/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202020-12-22%2023-17-21.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/1909037

Title:
  Weird sorting occurs on numbers sequence filenames

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

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

[Bug 1903910] Re: Mouse settings ignored when plugging in a new mouse

[Ben James]

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

> @Ben: Can you please install the mutter packages from this PPA

I can confirm that the suggested package works - I've tried with
multiple mice and all keep adopt the expected settings when I unplug and
plug them in again.

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

Title:
  Mouse settings ignored when plugging in a new mouse

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

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

[Bug 1903910] Re: Primary mouse button setting reverts to default

[Ben James]

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

I can also confirm that gsettings shows the correct value when
disconnecting the mouse, but when the mouse is reconnected, the setting
is reverted silently (gsettings and gnome-control-center show the wrong
value).

gsettings and gnome-control-center are in sync, but both wrong.

Steps to reproduce:

1) Plug in two USB mice.
2) Set Primary Button: Right.
3) Confirm - both buttons work as expected on both mice, gsettings shows 
"left-handed true"
4) Unplug one mouse.
5) The remaining mouse works fine, gsettings and gnome-control-center both show 
the right setting.
6) Plug the second mouse in again.
7) gsettings and gnome-control-center still show the same setting, however the 
two mice have different behaviour.

Summary: Mouse settings are not applied to a new mouse.

** Summary changed:

- Primary mouse button setting reverts to default
+ Mouse settings ignored when plugging in a new mouse

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

Title:
  Mouse settings ignored when plugging in a new mouse

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

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

[Bug 1903910] Re: Primary mouse button setting reverts to default

[Ben James]

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

After a bit more debug, it appears the problem occurs when any external
mouse is disconnected and reconnected (ruling out the USB hub and switch
as a factor).

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

Title:
  Primary mouse button setting reverts to default

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

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

[Bug 1903910] [NEW] Primary mouse button setting reverts to default

[Ben James]

Public bug reported:

I'm running Ubuntu 20.04 LTS on a Dell XPS 13 laptop with an external
mouse and keyboard connected via a USB switch.*

I've set the mouse to left-handed operation (i.e. primary mouse button =
right) using gnome-control-center; this works fine for a while and shows
the expected setting on the command line:

> gsettings get org.gnome.desktop.peripherals.mouse left-handed
true

...however if I leave the laptop for a while and come back to it, the
mouse has reverted back to right-handed operation.  The really curious
thing is that gnome-control-center still shows the expected setting
(primary mouse button = right).

To set the mouse as desired, I have to change the primary mouse button
to left and then back to right in gnome-control-center.

It's almost as if gsettings is reverting the mouse configuration and
becoming out of sync with gnome-control-center.


*The laptop is connected to a monitor using a single USB-C cable; the monitor 
acts as a USB hub and is connected to a USB switch such that I can use a single 
keyboard and mouse with two machines.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.4-0ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 11 19:51:39 2020
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2020-08-04 (99 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to focal on 2020-09-22 (50 days ago)

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


** Tags: amd64 apport-bug focal

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

Title:
  Primary mouse button setting reverts to default

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

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

[Bug 1903383] Re: XWayland applications respect scale only if a scaled output is primary on a mixed-scale setup

[Ben Aceler]

** Description changed:

  The bug occurs with any XWayland application. I tried VSCode, Chrome,
  Audacity, Darktable...
  
  I have two monitors with a different DPI. One is 4K HiDPI monitor and
  the second in LowDPI 2K monitor. I can setup 200% scale for a HiDPI
  monitor and 100% scale for a LowDPI. All native gnome applications are
  fine.
  
  The bug: when I select LowDPI monitor as a primary, XWayland
  applications stop scaling on a HiDPI monitor. They run 100% scale on
  both monitors. If I select HiDPI monitor as the primary, XWayland
- applications scales fine — 200% on the primary monitor and 100% on the
- secondary.
+ applications scales 200% on both monitors.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.6-1ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  7 12:28:53 2020
  InstallationDate: Installed on 2019-11-16 (356 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=ru_RU.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=ru_RU.UTF-8
+  SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: Upgraded to focal on 2020-05-02 (189 days ago)

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

Title:
  XWayland applications respect scale only if a scaled output is primary
  on a mixed-scale setup

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

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

[Bug 1903383] [NEW] XWayland applications respect scale only if a scaled output is primary on a mixed-scale setup

[Ben Aceler]

Public bug reported:

The bug occurs with any XWayland application. I tried VSCode, Chrome,
Audacity, Darktable...

I have two monitors with a different DPI. One is 4K HiDPI monitor and
the second in LowDPI 2K monitor. I can setup 200% scale for a HiDPI
monitor and 100% scale for a LowDPI. All native gnome applications are
fine.

The bug: when I select LowDPI monitor as a primary, XWayland
applications stop scaling on a HiDPI monitor. They run 100% scale on
both monitors. If I select HiDPI monitor as the primary, XWayland
applications scales fine — 200% on the primary monitor and 100% on the
secondary.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: mutter 3.36.6-1ubuntu0.20.04.2
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov  7 12:28:53 2020
InstallationDate: Installed on 2019-11-16 (356 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: mutter
UpgradeStatus: Upgraded to focal on 2020-05-02 (189 days ago)

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


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

** Attachment added: "LowDPI monitor is primary"
   
https://bugs.launchpad.net/bugs/1903383/+attachment/5432115/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202020-11-07%2012-26-28.png

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

Title:
  XWayland applications respect scale only if a scaled output is primary
  on a mixed-scale setup

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

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

[Bug 1903383] Re: XWayland applications respect scale only if a scaled output is primary on a mixed-scale setup

[Ben Aceler]

** Attachment added: "HiDPI monitor is primary"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903383/+attachment/5432118/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202020-11-07%2012-26-50.png

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

Title:
  XWayland applications respect scale only if a scaled output is primary
  on a mixed-scale setup

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

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

[Bug 1798166] Re: “Mouse battery low” notification can't be disabled

[Ben Landin]

This bug is NOT invalid. This issue has remained unaddressed for years.
Worse still, workarounds that used to mitigate the problem (dconf
tweaks, etc) no longer seem effective.

PLEASE, do not close this bug.

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

Title:
  “Mouse battery low” notification can't be disabled

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

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

[Bug 1295627] Re: Wrong language (German) after fresh install

[Ben Van Aerde]

This is still an issue in Ubuntu 20.04.
I changed it manually:

Settings > Language and Region > Manage Installed Languages
Install/remove languages
choose: other (it only shows a small list at first), and check "Dutch".

Afterwards, go to tab "Regional Formats". Here, you'll see "Deutsch" as a 
display language for numbers, dates and currencies.
Now you can select "Nederlands (België)".

Press "Apply system-wide". After logging it again, it should be
"solved".

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

Title:
  Wrong language (German) after fresh install

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

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

[Bug 1888574] [NEW] Dark mode highlight is too similar to text color

[Ben Bromley]

Public bug reported:

Hi all!

This is just a wishlist bug, but the dark mode in Gedit on Ubuntu
doesn't work well for me. In dark mode, the highlight color and the text
color are very similar, and the lack of contrast makes it difficult to
the see text. Perhaps changing the highlight color to purple or
something else to enhance contrast would be much appreciated.

Thanks!

Ubuntu 20.04
Installed: 3.36.2-0ubuntu1

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

** Attachment added: "gedit.png"
   https://bugs.launchpad.net/bugs/1888574/+attachment/5395032/+files/gedit.png

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

Title:
  Dark mode highlight is too similar to text color

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

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

[Bug 1691908] Re: fstab binds appear as mounts (x-gvfs-hide is being ignored)

[Ben Bell]

+1 to bionic backport please

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

Title:
  fstab binds appear as mounts (x-gvfs-hide is being ignored)

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

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

[Bug 1877589] Re: Wayland windows does not redraw itself

[Ben Aceler]

Yes, I am pretty sure:

$ apt-cache policy mutter
mutter:
  Installed: 3.36.2-1ubuntu1~20.04.1
  Candidate: 3.36.2-1ubuntu1~20.04.1
  Version table:
 *** 3.36.2-1ubuntu1~20.04.1 500
500 http://ru.archive.ubuntu.com/ubuntu focal-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 3.36.1-3ubuntu3 500
500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 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/1877589

Title:
  Wayland windows does not redraw itself

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

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

[Bug 1877589] Re: Wayland windows does not redraw itself

[Ben Aceler]

After updating to 3.36.2 problem still occurs.

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

Title:
  Wayland windows does not redraw itself

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

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

[Bug 1759462] Re: Keyboard shortcuts not operational on 18.04

[Nimrod Ben-Nes]

Just to be clear about the comment I wrote above, the solution is not
really related to Skype, its probably just the fact that something new
is loading up on log in and removing it will (hopefully) solve the
issue.

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

Title:
  Keyboard shortcuts not operational on 18.04

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

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

[Bug 1759462] Re: Keyboard shortcuts not operational on 18.04

[Nimrod Ben-Nes]

Had issues with keyboard shortcuts for changing language, up/down
volume, open terminal and so on...

First I tried comment #55 and logged out and back in, it didn't help.

I went to try comment #11 (sleep solution) but then I remembered that
few days ago I installed Skype and it was auto starting when I logged in
and maybe cause of that the "timing went off", so instead of setting the
sleep I just removed Skype from the auto start and restarted... and it
worked!

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

Title:
  Keyboard shortcuts not operational on 18.04

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

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

[Bug 1877589] Re: Wayland windows does not redraw itself

[Ben Aceler]

Yes, I disabled all extensions to ensure that is is not an extension
problem.

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

Title:
  Wayland windows does not redraw itself

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

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

[Bug 1877589] [NEW] Wayland windows does not redraw itself

[Ben Aceler]

Public bug reported:

I'm not sure, if it is not a bug of certain Wayland applications.

Under Ubuntu 20.04, Gnome 3.36, some Wayland-native applications, namely
Audacity(2.3.3) and Firefox (76.0), does not redraw themselves unless I
change their size, or switch to another window or overview. For example,
audacity does not redraw current position marker, and I need to click
with a mouse, or resize the window to see it. Firefox sometimes just
freeze, until I click or until I resize its window, or I switch to
overview.

What kind of trace shoud I perform to obtain more information?

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-session-wayland (not installed)
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri May  8 17:27:24 2020
InstallationDate: Installed on 2019-11-16 (173 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-session
UpgradeStatus: Upgraded to focal on 2020-05-02 (6 days ago)

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


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

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

Title:
  Wayland windows does not redraw itself

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

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

[Bug 1875729] Re: Fractional Scaling crashes gnome-control-center

[Ben]

Hi Sebastian and Daniel, thanks for getting back to me. Daniel, I think
you are likely correct with the 2 bugs you suggested, they seem to be
similar.

The links are:
https://errors.ubuntu.com/oops/13fe9496-8745-11ea-ac2d-fa163e983629
https://errors.ubuntu.com/oops/390d34ea-874a-11ea-a30e-fa163e6cac46
https://errors.ubuntu.com/oops/3547348e-897f-11ea-a33f-fa163e6cac46

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

Title:
  Fractional Scaling crashes gnome-control-center

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

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

[Bug 1875729] [NEW] Fractional Scaling crashes gnome-control-center

[Ben]

Public bug reported:

Overview:

When applying "Fractional Scaling" of 150% or 175%, the screen goes
black for a while, then after a little while it comes back unscaled and
gnome-control-center has crashed.


Found in:

Description:Ubuntu 20.04 LTS
Release:20.04

gnome-control-center:
  Installed: 1:3.36.1-1ubuntu5
  Candidate: 1:3.36.1-1ubuntu5
  Version table:
 *** 1:3.36.1-1ubuntu5 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status


Steps to reproduce:

1. Go into "Screen Display" in Settings.
2. Enable "Fractional Scaling".
3. Select "150%" or "175%".
4. Observe that the screen goes blank for about 5 seconds.
5. Observe that upon the screen coming back, the Settings application has 
crashed.


Additional details:

If instead of selecting "150%" or "175%" I select "125%", then the
screen will scale to 200% instead, but if I select and apply "125%"
again, then suddenly only just over of a quarter of the screen is
recognised as display and the rest just displays my background and top
bar extended.

I am using a 4k display over a display port cable.
I am using a GTX 1070 TI with the Nvidia 440.64 driver.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.1-1ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 28 19:37:27 2020
InstallationDate: Installed on 2020-04-25 (2 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Fractional Scaling crashes gnome-control-center

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

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

[Bug 1848852] Re: Counter-Strike Global Offensive freezes in gnome-shell

[Ben Romer]

I can confirm both the bug with CS:GO (and several other games that go
non-responsive for a short while after starting) and that the fix works.

I installed the packages from the ppa and have tested with CS:GO and a
couple of others I was experiencing the problem on (Dying Light and TF2
behave similarly) and the games start correctly now and do not block the
UI or crash gnome-shell, though they still display the Force Quit
dialog.

I can do any further testing needed but this LGTM.

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

Title:
  Counter-Strike Global Offensive freezes in gnome-shell

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

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

[Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes

[Ben Bromley]

I also hit Fn-A, which I saw somewhere (sorry to not have the link) that
would disable adaptive brightness.

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

Title:
  Dell XPS 13 9380 - Screen brightness flashes

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

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

[Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes

[Ben Bromley]

Alright, here we go.

I have the kernel listed above installed: Linux shadeball
5.2.0-9-generic #10~bfo110511 SMP Tue Jul 16 13:17:28 CST 2019 x86_64
x86_64 x86_64 GNU/Linux

I then went into the Power settings and turned Dim Screen When Inactive
to off, Blank Screen to Never and so far there have been basically no
flickers. There may have been one or two, but I can't confirm that I saw
them and cannot reproduce them.

I have tried it both on AC power and on battery, and with success on
both.

Thank you so much!

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

Title:
  Dell XPS 13 9380 - Screen brightness flashes

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

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

[Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes

[Ben Bromley]

But just to confirm, I think the patched kernel did improve the amount
of flickering.

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

Title:
  Dell XPS 13 9380 - Screen brightness flashes

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

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

[Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes

[Ben Bromley]

Huh, I wonder if this is a Gnome Shell issue and not a kernel issue
after all. After switching to Ubuntu Mate, and uninstalling the kernel
mentioned above, I have not had a flicker yet. Anecdotally, I have also
heard of people installing KDE on an XPS 13 9380 and also not having
this issue.

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

Title:
  Dell XPS 13 9380 - Screen brightness flashes

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

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

[Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes

[Ben Bromley]

Another error message from a flicker

Sep 12 20:28:01 shadeball org.gnome.Shell.desktop[5959]:
[6514:6514:0912/202801.632870:ERROR:gl_surface_presentation_helper.cc(259)]
GetVSyncParametersIfAvailable() failed for 1280 times!

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

Title:
  Dell XPS 13 9380 - Screen brightness flashes

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

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

[Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes

[Ben Bromley]

I ran "journalctl --user" after the last flicker and this is the output
from the time around the flicker

Sep 12 20:12:34 shadeball org.gnome.Shell.desktop[5959]: 
[1:1:0912/201234.077664:ERROR:child_process_sandbox_support_impl_linux.cc(81)] 
FontService unique font name matching request did not receive a response.
Sep 12 20:12:34 shadeball org.gnome.Shell.desktop[5959]: 
[1:1:0912/201234.078033:ERROR:child_process_sandbox_support_impl_linux.cc(81)] 
FontService unique font name matching request did not receive a response.
Sep 12 20:12:34 shadeball org.gnome.Shell.desktop[5959]: 
[1:1:0912/201234.084532:ERROR:child_process_sandbox_support_impl_linux.cc(81)] 
FontService unique font name matching request did not receive a response.
Sep 12 20:12:34 shadeball org.gnome.Shell.desktop[5959]: 
[1:1:0912/201234.084847:ERROR:child_process_sandbox_support_impl_linux.cc(81)] 
FontService unique font name matching request did not receive a response.

I can post the full multi-day output of journalctl --user if that would
be useful to you all.

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

Title:
  Dell XPS 13 9380 - Screen brightness flashes

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

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

[Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes

[Ben Bromley]

I am running Ubuntu 19.04 with an XPS 13 9380 with Intel graphics. I
installed the kernel mentioned above, and the problem is still
occurring. I do a dmesg everytime I see it happen, but I don't see a
consistent message every time it happens. I am more than willing to do
any and all testing you all need, so if you think of something I could
do to further investigate, let me know!

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

Title:
  Dell XPS 13 9380 - Screen brightness flashes

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

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

[Bug 1835625] Re: Shows old snap edge version of thunderbird

[Ben]

As I wrote on the snapcraft forums, that's a problem then as long as the
snap continues to be out of date/unstable, as the snap replaces the deb
version for users that don't have Thunderbird installed.

I don't mind if non-stable snaps appear in the store, but they should
not be default if a deb version is also available.

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

Title:
  Shows old snap edge version of thunderbird

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

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

[Bug 1830472] [NEW] 'mv' command without target address

[Ben]

Public bug reported:

When I was using the mv command, I forgot to enter the target folder,
but the terminal did not report an error and the source file was gone.
But when I tried it again， it report the error "mv: missing destination
file operand after 'filename'". Though the file is not important, I hope
you can figure it out. Thank you!

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-18-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat May 25 18:12:56 2019
ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
InstallationDate: Installed on 2019-03-07 (78 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "the wrong command screenshot"
   
https://bugs.launchpad.net/bugs/1830472/+attachment/5266487/+files/2019-05-25%2017-45-32%20%E7%9A%84%E5%B1%8F%E5%B9%95%E6%88%AA%E5%9B%BE.png

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

Title:
  'mv' command without target address

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

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

[Bug 1702151] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets()

[Ben Klein]

I'm on 19.04 and I seem to be able to reproduce this at least once a day
while I leave my screen locked overnight.

Am willing to provide logs and core dumps if possible.

Just let me know how/what you need to capture.

Each morning when I log back in, the screen will sit and freeze for a
minute or so while gnome shell crashes and restarts, but at least it
keeps my windows and workspaces open / in place. A bit after that is
when apport gives me the dialog.

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

Title:
  gnome-shell crashed with SIGSEGV in
  g_type_check_instance_is_fundamentally_a() from g_object_ref() from
  st_theme_get_custom_stylesheets()

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

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

[Bug 1828720] Re: eog (Ubuntu image viewer) consumes all memory when opening a tiff file

[Ben Weiner]

OK well with more resources in use the behaviour I am getting is that
Image Viewer boots, shows a blank window, and then exits. So that's a
little bit like my comment #4.

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

Title:
  eog (Ubuntu image viewer) consumes all memory when opening a tiff file

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

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

[Bug 1828720] Re: eog (Ubuntu image viewer) consumes all memory when opening a tiff file

[Ben Weiner]

This file is identical in pixel dimensions to one that caused the bug
earlier. It is 1-bit with a size of 10332px x 4148px. It is LZW
compressed and contains an entirely white image.

*Opening this file with Image Viewer (eog) doesn't trigger the bug* with
the resources available on my system now, though it takes a bit of time
to appear and requires over 1GB of memory. I will load up more software
and see if that affects the outcome, and I will try the one of the files
that did trigger it earlier at the current system usage level (I cannot
upload that as it's a private scan from a book and sharing it would
violate copyright).


** Attachment added: "Sample LZW compressed 1-bit TIFF"
   
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1828720/+attachment/5263279/+files/1bit-test-compressed.tiff

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

Title:
  eog (Ubuntu image viewer) consumes all memory when opening a tiff file

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

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

[Bug 1828720] Re: eog (Ubuntu image viewer) consumes all memory when opening a tiff file

[Ben Weiner]

OK the original trigger file is OK now and uses a similar amount of
memory to load.

I guess it would be more appropriate to say that there's nothing to stop
eog loading a file that's impracticably large, and a refinement would be
to do a rough calculation of the memory requirement and ask the user to
confirm they want to open it.

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

Title:
  eog (Ubuntu image viewer) consumes all memory when opening a tiff file

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

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

[Bug 1828720] [NEW] eog (Ubuntu image viewer) consumes all memory when opening a tiff file

[Ben Weiner]

Public bug reported:

The ImageViewer app (/usr/bin/eog) will go into a loop if a TIFF files
are opened. Any TIFF file can cause a loop even if less than 1MB in
size, so it seems that the program is encountering an internal issue
with the TIFF format.

The loop quickly consumes all free memory and locks up the machine (I do
not have any swap).

Steps to reproduce:
* open any TIFF file using ImageViewer, the default image file handler.


ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: eog 3.28.1-1
ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
Uname: Linux 4.15.0-48-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun May 12 11:11:02 2019
InstallationDate: Installed on 2015-02-21 (1540 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: eog
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: eog (Ubuntu)
 Importance: High
 Status: Incomplete


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

** Description changed:

  The ImageViewer app (/usr/bin/eog) will go into a loop if a TIFF files
- are opened. Any TIFF file can cause a loop risky even if less than 1MB
- in size, so it seems that the program is encountering an internal issue
+ are opened. Any TIFF file can cause a loop even if less than 1MB in
+ size, so it seems that the program is encountering an internal issue
  with the TIFF format.
  
  The loop quickly consumes all free memory and locks up the machine (I do
  not have any swap).
  
  Steps to reproduce:
  * open any TIFF file using ImageViewer, the default image file handler.
  
- OS:
- Description:  Ubuntu 18.04.2 LTS
- Release:  18.04
- 
- Package:
- eog:
-   Installed: 3.28.1-1
-   Candidate: 3.28.1-1
-   Version table:
-  *** 3.28.1-1 500
- 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
- 100 /var/lib/dpkg/status
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: eog 3.28.1-1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 12 11:11:02 2019
  InstallationDate: Installed on 2015-02-21 (1540 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: eog
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  eog (Ubuntu image viewer) consumes all memory when opening a tiff file

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

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

Re: [Bug 1316673] Re: Pressing umount button leads to sticky icon as mouse pointer

[Ben]

> Do you still see that issue in more recent Ubuntu versions?
> 
> ** Changed in: nautilus (Ubuntu)
>Status: New => Incomplete

No. Should be closed.

Cheers

Benjamin

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

Title:
  Pressing umount button leads to sticky icon as mouse pointer

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

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

[Bug 1724810] Re: 17.10/wayland causing flashes in virtualbox

[Ben Mishkanian]

Is it possible to implement the fix in the upstream gnome-shell? It
seems Fedora's gnome-shell is also affected by this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1520005

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

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

Title:
  17.10/wayland causing flashes in virtualbox

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

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

[Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

[Ben M.]

Hey all,

Kubuntu (which means plasma and KDE) is no exception. Running default config.
But for some time it worked. So it must have been in an update of the past few 
weeks,

It's not just alt+arrow for me. Even alt+f1 through alt+f8 will switch
(to) console.


I guess this is a problem:

$ sudo dumpkeys | grep -E '(\W+)alt(\W+)keycode.*Cons'
alt keycode  59 = Console_1   
shift   alt keycode  59 = Console_13  
control alt keycode  59 = Console_1   
shift   control alt keycode  59 = Console_13  
alt keycode  60 = Console_2   
shift   alt keycode  60 = Console_14  
control alt keycode  60 = Console_2   
shift   control alt keycode  60 = Console_14  
alt keycode  61 = Console_3   
shift   alt keycode  61 = Console_15  
control alt keycode  61 = Console_3   
shift   control alt keycode  61 = Console_15  
alt keycode  62 = Console_4   
shift   alt keycode  62 = Console_16  
control alt keycode  62 = Console_4   
shift   control alt keycode  62 = Console_16  
alt keycode  63 = Console_5   
shift   alt keycode  63 = Console_17  
control alt keycode  63 = Console_5   
shift   control alt keycode  63 = Console_17  
alt keycode  64 = Console_6   
shift   alt keycode  64 = Console_18  
control alt keycode  64 = Console_6   
shift   control alt keycode  64 = Console_18  
alt keycode  65 = Console_7   
shift   alt keycode  65 = Console_19  
control alt keycode  65 = Console_7   
shift   control alt keycode  65 = Console_19  
alt keycode  66 = Console_8   
shift   alt keycode  66 = Console_20  
control alt keycode  66 = Console_8   
shift   control alt keycode  66 = Console_20  
alt keycode  67 = Console_9   
shift   alt keycode  67 = Console_21  
control alt keycode  67 = Console_9   
shift   control alt keycode  67 = Console_21  
alt keycode  68 = Console_10  
shift   alt keycode  68 = Console_22  
control alt keycode  68 = Console_10  
shift   control alt keycode  68 = Console_22  
alt keycode  87 = Console_11  
shift   alt keycode  87 = Console_23  
control alt keycode  87 = Console_11  
shift   control alt keycode  87 = Console_23  
alt keycode  88 = Console_12  
shift   alt keycode  88 = Console_24  
control alt keycode  88 = Console_12  
shift   control alt keycode  88 = Console_24  
alt keycode  99 = Last_Console
shift   alt keycode  99 = Last_Console
altgr   alt keycode  99 = Last_Console
shift   altgr   alt keycode  99 = Last_Console
alt keycode 105 = Decr_Console
alt keycode 106 = Incr_Console

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

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

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

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

[Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

[Ben M.]

I just modified comment 31 (https://bugs.launchpad.net/ubuntu/+source
/gnome-shell/+bug/1508146/comments/31):

$ sudo dumpkeys | grep -v -E '^(\W+)alt(\W+)keycode.*Cons' | sudo
loadkeys

Everything with alt at the beginning and Console will not switch (to)
consoles anymore.

** Also affects: kubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

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

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

[Bug 1786233] GsettingsChanges.txt

[Ben Aceler]

apport information

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

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

Title:
  Can't rename a desktop file

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

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

[Bug 1786233] Re: Can't rename a desktop file

[Ben Aceler]

apport information

** Tags added: apport-collected bionic third-party-packages wayland-
session

** Description changed:

  Nautilus allows to rename any generic file, including the extension
  part. For example, I can rename "Image.jpeg" to "Image.jpg" or even
  "Image.png" which is not right, but still possible.
  
- Dekstop files are different. If I try to rename firefox.desktop to
- firefox.txt in order to edit this file manually, I can't do so, because
- nautilus always add desktop extension. If I accidentially rename regular
- file to a desktop file, I can't rename it back, because Nautilus throw
- an error, that this desktop file has a wrong format (obviously because
- it is not a desktop file).
+ Dekstop files are different. If I try to rename firefox.desktop to 
firefox.txt in order to edit this file manually, I can't do so, because 
nautilus always add desktop extension. If I accidentially rename regular file 
to a desktop file, I can't rename it back, because Nautilus throw an error, 
that this desktop file has a wrong format (obviously because it is not a 
desktop file).
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.3
+ Architecture: amd64
+ CurrentDesktop: pop:GNOME
+ DistroRelease: Pop!_OS 18.04
+ InstallationDate: Installed on 2018-01-08 (213 days ago)
+ InstallationMedia: Pop_OS 17.10 "Artful Aardvark" - Release amd64 (20171219)
+ Package: nautilus 1:3.26.3-0ubuntu4 [origin: Ubuntu]
+ PackageArchitecture: amd64
+ Tags: third-party-packages wayland-session bionic
+ Uname: Linux 4.18.0-041800rc8-generic x86_64
+ UnreportableReason: Этот пакет не является официальным пакетом Pop!_OS. 
Пожалуйста, удалите все сторонние пакеты и попробуйте снова.
+ UpgradeStatus: Upgraded to bionic on 2018-05-04 (97 days ago)
+ UserGroups: adm kvm lpadmin sudo tty vboxusers video
+ _MarkForUpload: True
+ usr_lib_nautilus:

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

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

Title:
  Can't rename a desktop file

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

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

[Bug 1786233] ProcCpuinfoMinimal.txt

[Ben Aceler]

apport information

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

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

Title:
  Can't rename a desktop file

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

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

[Bug 1786233] ProcEnviron.txt

[Ben Aceler]

apport information

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

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

Title:
  Can't rename a desktop file

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

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

[Bug 1786233] [NEW] Can't rename a desktop file

[Ben Aceler]

Public bug reported:

Nautilus allows to rename any generic file, including the extension
part. For example, I can rename "Image.jpeg" to "Image.jpg" or even
"Image.png" which is not right, but still possible.

Dekstop files are different. If I try to rename firefox.desktop to
firefox.txt in order to edit this file manually, I can't do so, because
nautilus always add desktop extension. If I accidentially rename regular
file to a desktop file, I can't rename it back, because Nautilus throw
an error, that this desktop file has a wrong format (obviously because
it is not a desktop file).

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

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

Title:
  Can't rename a desktop file

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

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

[Bug 1766799] Re: gnome-control-center (ERROR) ../shell/cc-panel-list.c → 926 → cc_panel_list_set_active_panel → assertion failed → (data != NULL)

[Ben Roberts]

I get this trying to use gnome-control-center under the "Gnome Classic"
session.

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

Title:
  gnome-control-center (ERROR) ../shell/cc-panel-list.c → 926 →
  cc_panel_list_set_active_panel → assertion failed → (data != NULL)

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

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

[Bug 1755887] Re: Duplicate Login keyring created on every login, results in multiple keyring unlock requests on each login

[Ben Davis]

I'm experiencing the same issue. I tried deleting all "Login" keyrings,
and a new one gets created every time I log in.

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

Title:
  Duplicate Login keyring created on every login, results in multiple
  keyring unlock requests on each login

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

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

[Bug 1759300] [NEW] touchpad right click

[Ben-Ja]

Public bug reported:

The right (second) touchpad click does not work.
It ceased to work about three months ago.
ubuntu 18,04 aser ex2519

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: 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/1759300

Title:
  touchpad right click

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

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

[Bug 1755010] [NEW] package systemd 237-3ubuntu4 failed to install/upgrade: triggers looping, abandoned

[Ben Romer]

Public bug reported:

Tried upgrading from Artful to Bionic this weekend, had problems.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Sun Mar 11 13:47:24 2018
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2017-10-08 (153 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: ASUSTeK COMPUTER INC. G752VY
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=2bbeb898-f4c5-4a25-ba8d-f7874903809e ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt  1.6~beta1
SourcePackage: systemd
Title: package systemd 237-3ubuntu4 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: Upgraded to bionic on 2018-03-11 (0 days ago)
dmi.bios.date: 06/29/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G752VY.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G752VY
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VY.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: G
dmi.product.name: G752VY
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-package bionic

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

Title:
  package systemd 237-3ubuntu4 failed to install/upgrade: triggers
  looping, abandoned

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

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

[Bug 1714039] [NEW] nslcd shuts down before sshd, causing errors

[ben thielsen]

Public bug reported:

1] >lsb_release -rd
Description:Ubuntu 17.04
Release:17.04

2] >apt-cache policy systemd
systemd:
  Installed: 232-21ubuntu5
  Candidate: 232-21ubuntu5
  Version table:
 *** 232-21ubuntu5 500
500 http://dca-ubuntu-repo.ipipenet.com/ubuntu zesty-updates/main amd64 
Packages
500 http://dca-ubuntu-repo.ipipenet.com/ubuntu-security 
zesty-security/main amd64 Packages
100 /var/lib/dpkg/status
 232-21ubuntu2 500
500 http://dca-ubuntu-repo.ipipenet.com/ubuntu zesty/main amd64 Packages

3] i expected nslcd to not be terminated when sshd still needs it
4] it was

logs:
Aug 30 15:17:26 template nslcd[956]: thread 1 is still running, shutting down 
anyway
Aug 30 15:17:26 template sshd[988]: pam_ldap(sshd:session): error opening 
connection to nslcd: No such file or directory
Aug 30 15:17:26 template sshd[988]: pam_systemd(sshd:session): Failed to 
release session: Connection reset by peer
Aug 30 15:17:26 template sshd[988]: pam_mail(sshd:session): user unknown
Aug 30 15:17:26 template sshd[988]: fatal: login_init_entry: Cannot find user 
"jdoe"

** Affects: systemd (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/1714039

Title:
  nslcd shuts down before sshd, causing errors

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

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

[Bug 1709384] [NEW] failed to unmount filesystems during shutdown, reboot hangs

[ben thielsen]

Public bug reported:

i'd done a new install of 17.04, and this had been working ok.  this
morning, i did an update, and now the system complains about being
unable to unmount certain filesystems, as well as hanging during the
shutdown process upon displaying "[ ok ] reached target shutdown"

Aug  8 16:11:48 template systemd[1]: Failed unmounting /home/foo.example.com.
Aug  8 16:11:49 template systemd[1]: Failed unmounting /var/log.
Aug  8 16:11:49 template systemd[1]: Failed unmounting /tmp.
Aug  8 16:11:49 template systemd[1]: Failed unmounting /home.
Aug  8 16:11:49 template systemd[1]: Failed unmounting /var.

1] >lsb_release -rd
Description:Ubuntu 17.04
Release:17.04

2] >apt-cache policy systemd
systemd:
  Installed: 232-21ubuntu5
  Candidate: 232-21ubuntu5
  Version table:
 *** 232-21ubuntu5 500
500 http://us.archive.ubuntu.com/ubuntu zesty-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu zesty-security/main amd64 Packages
100 /var/lib/dpkg/status
 232-21ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages

3] i expected the system to not fail when unmounting filesystems during shutdown
4] it did

** Affects: systemd (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/1709384

Title:
  failed to unmount filesystems during shutdown, reboot hangs

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

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

[Bug 1708201] Re: gnome-calendar does not use the proper system timezone

[Ben Yanke]

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

** Also affects: gnome-calendar via
   https://bugzilla.gnome.org/show_bug.cgi?id=785743
   Importance: Unknown
   Status: Unknown

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

Title:
  gnome-calendar does not use the proper system timezone

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

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

[Bug 1708201] [NEW] gnome-calendar does not use the proper system timezone

[Ben Yanke]

Public bug reported:

Calendar source: 
Evolution (exchange calendar via evolution-ews)

In evolution, the calendar properly shows events in my timezone (CST).
For example, Event1 at 9:30am and Event2 at 3pm (actual examples, just
changed names).

In gnome-calendar, these events show up at 4:30am and 10am,
respectively. This issue also appears in the California calendar.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-calendar 3.20.4-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-27-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Aug  2 11:29:21 2017
ExecutablePath: /usr/bin/gnome-calendar
InstallationDate: Installed on 2017-07-03 (29 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
ProcEnviron:
 XDG_RUNTIME_DIR=
 SHELL=/bin/bash
 LANGUAGE=en_US
 PATH=(custom, user)
 LANG=en_US.UTF-8
SourcePackage: gnome-calendar
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  gnome-calendar does not use the proper system timezone

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

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

[Bug 1690355] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Tomer David Ben Zohar]

Public bug reported:

...

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
Date: Fri May 12 14:01:31 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-05-11 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check zesty

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

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

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

[Bug 9441] Re: the locate pointer option breaks other keybindings

[Ben Abrams]

This is still not fixed or is a regression in xenial. Should we re-open
or create a new request?

I can replicate this with keepass2 and virtualbox.

Replication steps:
1. Go to gnome tweak tool and change "Show location of pointer" to "ON"
2. attempt to use the ctrl key such as ctrl + c, all ctrl key combinations are 
swallowed.
3. Go to gnome tweak tool and change "Show location of pointer" to "OFF"
4. attempt to use the ctrl key such as ctrl + c, everything should work as 
intended.

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

Title:
  the locate pointer option breaks other keybindings

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

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

[Bug 1615732] Re: Execution of filter 'Junk check' fails with "Empty cache file"

[Ben Holness]

Even more debug! Identifying information replaced with [snipped]

[imapx:M] Have token 'FETCH' id 4366
[imapx:N] Unmark connection 0x5601d92b5240 (server:0x5601d74b93a0) busy after 
failure, error: Empty cache file: 
/home/[snipped]/.cache/evolution/mail/[snipped]@[snipped]/folders/INBOX/cur/0f/504517
[imapx:M] got untagged response

(evolution:5063): camel-WARNING **: Error in execution: Failed to
retrieve message

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

Title:
  Execution of filter 'Junk check' fails with "Empty cache file"

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

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

[Bug 1615732] Re: Execution of filter 'Junk check' fails with "Empty cache file"

[Ben Holness]

More information: I get this error each time it happens:

(evolution:2569): camel-WARNING **: Error in execution: Failed to
retrieve message

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

Title:
  Execution of filter 'Junk check' fails with "Empty cache file"

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

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

[Bug 1615732] Re: Execution of filter 'Junk check' fails with "Empty cache file"

[Ben Holness]

I also have this problem. I do not have a filter named "junk check" so I
presume it is something built in. I turned of junk handling options in
Evolution's preferences and now I get the same message but the filter is
the top one of my filters list. I have checked in the filesystem and the
file exists and is indeed 0 size.

I am using:

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS"

Evolution 3.18.5.2

This is a big issue if these are real messages that are being truncated!
If they are not real messages, or it's just the caching that failed and
the message is intact, it's not a big deal.

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

Title:
  Execution of filter 'Junk check' fails with "Empty cache file"

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1615732/+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

[Ben]

Thanks again for taking the time.

It's difficult to say exactly the number at which it occurs because
there's a point at which the normal time to copy a small number of files
crosses the point where it is no longer normal to copy lots of small
files. I can say that I've never _noticed_ it with less than 50 files,
but then again - even if it happened with less than 50 files the delay
may have been small enough where I didn't realize the issue happened.
I've definitely noticed it with as few as 50 files. I did some testing
with 20 and 40 files this morning but didn't notice any issue.

This definitely has not occurred in Ubuntu 14.04 using Nautilus
1:3.10.1-0ubuntu8 and previous versions (all the way back to launch). It
definitely never happened with Ubuntu 10.04 LTS or 7.04 LTS and any
version of Nautilus included in their stable releases.

I'm almost certain it never happened with Linux Mint 17 and Linux Mint
17 MATE, but I can't say that for certain as I abandoned those distros
pretty quickly after finding it did not meet my needs.

I don't recall which version of Caja originally shipped with Ubuntu MATE
16.04 LTS, but I installed MATE 16.04 LTS on launch day and keep my
packages updated at least weekly, and this issue has been present in all
versions.

-- 
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 1133477] Re: cut-n-paste move files got stuck forever

[Ben]

Apologies for the double comment - but I realized I missed one of your
questions. The size and type of files does not seem to matter. I've had
this happen with text, image, video, and "other" files of sizes from a
couple kilobytes up to several megabytes. I have not tested with a large
number of files of several gigabytes, though I don't imagine it would be
as noticeable since one would reasonably expect those to take a bit of
time to copy normally.

As far as I can tell there are no definite triggers. When I was first
doing a prototype build of Ubuntu 16.04 LTS and ran into this bug, I did
a fresh build, updated all packages, and then was able to easily
replicate after a clean boot and nothing running except the file
browser. My current system uses SSD drives only, but I have also
verified on a system with spindle disks.

-- 
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 1133477] Re: cut-n-paste move files got stuck forever

[Ben]

I just tested this very easily, but unfortunately nothing was recorded
in any of the /var/logs. The steps I used to replicate on a Lenovo P50
running Ubuntu Mate 16.04 LTS (fully updated as of 29 March 2017)

1) Open Caja 1.12.7 (also tested using Nautilus on Ubuntu 16.04 LTS)
2) Navigate to a folder that has 500 text files in it of very small size 
(5-10kb is sufficient)
3) Press F3 to open a new pane (or optionally open a new window, doesn't 
matter) and navigate to an empty folder on the same drive (or a different 
drive, doesn't matter)
4) Highlight most or all of the files in the source directory, and press CTRL-X 
(or edit > cut, doesn't matter)
5) Go to the destination pane, and press CTRL-V (or edit > paste, doesn't 
matter)

Sometimes, the cut/paste will happen nearly instantly as it should.
Sometimes though, it will take a second or two to start, then spend
between 1 and 20 minutes sitting there, copying the files one-by-one,
very very very very very slowly. This issue is not reproducible using
the 'cp' or 'mv' command line programs.

-- 
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 1633732] Re: File operation popup and icon progress bar do not go away

[Ben Klein]

I filed a bug report at
https://bugzilla.gnome.org/show_bug.cgi?id=780553

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

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

Title:
  File operation popup and icon progress bar do not go away

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

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

[Bug 1643042] [NEW] GUI Not Honoring Default GW Removal

[Ben]

Public bug reported:

I may be missing something, but I have done as much testing as I can
think of and have come up with the following:

OpenVPN Server v2.3.10-1ubuntu2 on Ubuntu Server 16.04.1 LTS 64bit
OpenVPN Client v2.3.10-1ubuntu2 on Ubuntu MATE 16.04 LTS 64bit
network-manager-openvpn-gnome version v1.1.93-1ubuntu1

When running OpenVPN from the CLI, and the server.conf instructs the
client to remove the default gateway and replace it with the tun0
adapter, it does as expected. However, using the same client.ovpn file
imported into the GUI does not remove the existing default gateway, it
simply moves it down the routing order. This can (and does) create a
routing leak on secure systems. Detailed info:

192.168.8.1 = local router (dirty router)
10.8.0.1= vpn server tun adapter (gateway)
10.8.0.5= laptop tun adapter address
12.34.56.78 = vpn server public internet address

# Connected to the dirty router, no VPN
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 192.168.8.1 0.0.0.0 UG60000 wlp2s0
192.168.8.0 0.0.0.0 255.255.255.0   U 60000 wlp2s0

# Connected to the OpenVPN using command line version 2.3.10-1ubuntu2
# sudo openvpn --config /path/to/client.ovpn
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 10.8.0.50.0.0.0 UG0  00 tun0
10.8.0.110.8.0.5255.255.255.255 UGH   0  00 tun0
10.8.0.50.0.0.0 255.255.255.255 UH0  00 tun0
12.34.56.78 192.168.8.1 255.255.255.255 UGH   0  00 wlp2s0

# Connected to the OpenVPN using network-manager-openvpn-gnome version 
1.1.93-1ubuntu1
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 10.8.0.50.0.0.0 UG50 00 tun0
0.0.0.0 192.168.8.1 0.0.0.0 UG60000 wlp2s0 
<== this entry is creating a routing leak
10.8.0.110.8.0.5255.255.255.255 UGH   50 00 tun0
10.8.0.50.0.0.0 255.255.255.255 UH50 00 tun0
12.34.56.78 192.168.8.1 255.255.255.255 UGH   60000 wlp2s0


Here is the relevant section of the server.conf;
push "redirect-gateway bypass-dhcp"
push "dhcp-option DNS 8.8.8.8"
push "dhcp-option DNS 8.8.4.4"

Note that the above does not include the 'def1' option in the push
redirect-gateway command, so the client is supposed to delete any
existing default gateways and install only the VPN default gateway. This
is the only way to be sure that 1) all traffic goes over the VPN, and 2)
when the client disconnects, the internet connection is severed and it's
much less likely that you accidentally lose your VPN and continue
transmitting unencrypted

** Affects: network-manager-openvpn (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  GUI Not Honoring Default GW Removal

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

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

[Bug 887821] Re: "Show copy dialog" right click launcher entry doesn't work (on nautilus copy)

[Ben Capewell]

I'm having this problem on 16.04 LTS.

I did not minimise the copy dialog, but it seems that something
triggered Kodi to come to the foreground while my TV was switched off
overnight, after which I was unable to return to the copy dialog by any
of the suggested means.

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

Title:
  "Show copy dialog" right click launcher entry doesn't work (on
  nautilus copy)

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

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

[Bug 1607583] [NEW] package metacity-common 1:2.34.13-0ubuntu4.1 failed to install/upgrade: package metacity-common is already installed and configured

[Ben Saini]

Public bug reported:

Occurred during UBUNTU upgrade from 14.04 to 16.04 via GUI.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: metacity-common 1:3.18.5-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.20.1-0ubuntu2.1
AptTermLog:
 
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
Date: Fri Jul 29 02:12:58 2016
DuplicateSignature:
 package:metacity-common:1:2.34.13-0ubuntu4.1
 Setting up libprotobuf9v5:amd64 (2.6.1-1.3) ...
 dpkg: error processing package compiz-core (--configure):
  package compiz-core is already installed and configured
ErrorMessage: package metacity-common is already installed and configured
InstallationDate: Installed on 2014-06-13 (776 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: metacity
Title: package metacity-common 1:2.34.13-0ubuntu4.1 failed to install/upgrade: 
package metacity-common is already installed and configured
UpgradeStatus: Upgraded to xenial on 2016-07-29 (0 days ago)

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


** Tags: already-installed amd64 apport-package xenial

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

Title:
  package metacity-common 1:2.34.13-0ubuntu4.1 failed to
  install/upgrade: package metacity-common is already installed and
  configured

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

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

[Bug 1573206] Re: GNOME Software does not install third-party .deb packages

[Jonathan Ben Yhochanan Reich Abohab Da Fonseca]

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

Seems to instal with GDebi as also via terminal but at the end does not
work

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

Title:
  GNOME Software does not install third-party .deb packages

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

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

[Bug 1581997] [NEW] The gnome-disks utility allows users to select LUKS+EXT4 without having cryptsetup installed

[Ben Mathews]

Public bug reported:

Using a clean install of Ubuntu 16.04, the gnome-disks utility offers
users the option of selecting UKS+EXT4 when formatting disks.  This
fails with:

Error creating LUKS device: Error spawning command-line `cryptsetup
luksOpen "/dev/sdb" "': Failed to execute child process "cryptsetup" (No
such file or directory) (g-exec-error-quark, 8) (udisks-error-quark, 0)

Installing the cryptsetup package resolves this error.

Suggested resolution:
1) Don't offer LUKS+EXT4 as an option if cryptsetup is not installed
 - or -
2) Rather than failing in the current manner, suggest to the user to install 
cryptsetup
 - or - 
3) Include cryptsetup in the base install by default

Additional information:
1) Release of Ubuntu I am using:
 Description:   Ubuntu 16.04 LTS
 Release:   16.04

2) The version of the package I are using:
gnome-disk-utility:
  Installed: 3.18.3.1-1ubuntu1
  Candidate: 3.18.3.1-1ubuntu1
  Version table:
 *** 3.18.3.1-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

3) What I expected to happen: See above

4) What happened instead: See above

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-disk-utility 3.18.3.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Sun May 15 10:22:40 2016
InstallationDate: Installed on 2016-04-22 (23 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: gnome-disk-utility
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  The gnome-disks utility allows users to select LUKS+EXT4 without
  having cryptsetup installed

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

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

[Bug 1575452] [NEW] Copy/move dialog cannot be switched to

[Ben High]

Public bug reported:

When copying or moving a large file, Nautilus opens a window with the
progress of the operation. If the user were to pull a larger window
forward, that dialog cannot be accessed through Alt+tab or the Unity
bar. The user would have to move the obscuring window out of the way in
order to pull the progress dialog forward.

How to recreate:
1. Copy or move a large file. I recommend copying or moving to or from an SD 
card, USB key, or network device because they tend to be much slower than the 
local hard disk.
2. When the copy or move progress dialog appears, move a larger or maximized 
window over the dialog so it is obscured. Alternately, just click a different 
window to select it.
3. Click the Nautilus icon in the Unity bar, or press Alt+tab.

Expected behavior: The copy/move dialog will be brought to the front.
Actual behavior: The last used normal (non-dialog) Nautilus window will be 
brought to the front.
Frequency: Every time.

Nautilus version: 3.18.4.is.3.14.3-0ubuntu4
Ubuntu version: Ubuntu 16.04 LTS
Linux kernel version: 4.4.0-21-generic
Architecture: x86_64

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


** Tags: xenial

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

Title:
  Copy/move dialog cannot be switched to

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

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

[Bug 253167] Re: Rhythmbox sort by "Album Artist" for guest/compilations

[Ben Olson]

This bug was first noticed in 2008, and it is now 7 years later, near
the end of 2015, and it still hasn't been resolved. Rhythmbox is the
default music player for the GNOME desktop, and I simply can't use it
without this bug being resolved.  I'll try to poke through the source
and see what needs to be done to resolve it.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/253167

Title:
  Rhythmbox sort by "Album Artist" for guest/compilations

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

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

[Bug 253167] Re: Rhythmbox sort by "Album Artist" for guest/compilations

[Ben Olson]

** Also affects: rhythmbox (Debian)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/253167

Title:
  Rhythmbox sort by "Album Artist" for guest/compilations

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

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

[Bug 253167] Re: Rhythmbox sort by "Album Artist" for guest/compilations

[Ben]

Cheers, I am using Rhythmbox in 2015. Let me explain why.

1. It is extremely clean, which I love and this also fits my Lubuntu
System. Banshee is not nice to look at.

2. It is supporting the folders of my NAs that I mount via SMB. Amarok
and GKTpod do not provide this.

That's why i decided to use it even after I recognised that I cannot
sort my compilations via albumartist. I decided to override all the
artists with only one. I like a simpe structure. But it feels wrong to
not have access to the real artists of the songs any more.

So I really would ask for someone to code this. Rhythmbox is an awesome
client and fits extremely well into the whole Lubuntu world.

Thank you very much,
Ben

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/253167

Title:
  Rhythmbox sort by "Album Artist" for guest/compilations

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

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

[Bug 1490337] Re: Doubleclicking some.desktop file returns wrong %k variable

[Ben High]

Thanks for reporting this problem! I was able to replicate this bug in
Thunar 1.6.10, as well as in Nautilus 3.14.2, but PCManFM does not have
this problem, as said in the report.

** Also affects: nautilus (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: thunar (Ubuntu)
   Status: New => 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/1490337

Title:
  Doubleclicking some.desktop file returns wrong %k variable

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

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

[Bug 938751] Re: jpeg images are washed out or colors are skewed

[Ben Scholzen 'DASPRiD']

I was wondering about this as well, but I figured that it doesn't seem
to be a bug at all. The reason why it looks for some of you "correct" in
Gimp is, because you don't have color management for your monitor
enabled in the preferences (either set a specific monitor profile there,
or tick the fallback option, which will make it use the color profile
from the window manager).

Thus, what Gimp is showing you all is the image without your monitor
profile applied, while EOG always uses your monitor profile. So when the
image in EOG looks dull to you, that's actually how it's supposed to
look like.

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

Title:
  jpeg images are washed out or colors are skewed

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

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

[Bug 942131] Re: Sometimes I have to select logout/shut down twice before it has effect

[Ben Scholzen 'DASPRiD']

By now I kinda have the feeling that it's the fault of some program.
Because when clicking shutdown, a few programs are closed, while other's
stay open. Only after the second shutdown, all close. So one program is
apparently not responding to the signal the first time.

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

Title:
  Sometimes I have to select logout/shut down twice before it has effect

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

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

[Bug 1468091] Re: Ubuntu 15.04 Alpha-1 candidates do not boot in EC2

[Ben Howard]

Confirmed that this is not happening on OpenStack.

I suspect that this is cause is that /dev/disk/by-*/ targets are missing
for Xen Block devices.

** Changed in: ubuntu
   Status: New = Confirmed

** Changed in: ubuntu
   Importance: Undecided = Critical

** Package changed: ubuntu = systemd (Ubuntu)

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

Title:
  Ubuntu 15.10 Alpha-1 candidates do not boot in EC2

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

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

Re: [Bug 517021] Re: gvfsd-metadata causes 100% CPU usage

[Ben Bucksch]

Launchpad Bug Tracker wrote on 06.05.2015 20:01:
 ** Changed in: gvfs (Ubuntu Precise)
 Status: Fix Committed = Fix Released

Fix tested and confirmed in Ubuntu 12.04 Precise.

Before, I reproducibly ran into this bug when saving a data: URL from a 
Firefox-based webapp to a local file using the normal Firefox download 
dialog.

I installed the Precise update from the normal Precise update package 
repositories.

I save now, and I do not see the 100% CPU usage anymore. Bug fixed.

Thanks a lot to Ross Lagerwall,Tomas Bzate, Alexander Larsson, Ondrej 
Holy (all GNOME https://bugzilla.gnome.org/show_bug.cgi?id=637095), 
Monsta, Marc Deslauriers (here) and everybody else involved!

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/517021

Title:
  gvfsd-metadata causes 100% CPU usage

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

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

Re: [Bug 517021] Re: gvfsd-metadata causes 100% CPU usage

[Ben Bucksch]

Monsta wrote on 21.04.2015 12:47:
 ** Attachment added: debdiff with the fix for Precise
 
 https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+attachment/4380477/+files/gvfs-precise-debdiff

Thank you! :-)

What's the process of getting this into the release distro?

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/517021

Title:
  gvfsd-metadata causes 100% CPU usage

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

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

[Bug 517021] Re: gvfsd-metadata causes 100% CPU usage

[Ben Bucksch]

 The Bug 637095 is no longer available, where should we find a patch?

Not the one here, but on gnome.
From comment #49:
 apply mentioned patch from upstream Bug 637095 to fix problems with metadata:
 https://bugzilla.gnome.org/show_bug.cgi?id=637095

---

This must be backported to Precise (Ubuntu 12.04 LTS), too. Precise is
still suported, and this is trashing hardware.

** Tags added: hang precise

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/517021

Title:
  gvfsd-metadata causes 100% CPU usage

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

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

[Bug 942131] Re: Sometimes I have to select logout/shut down twice before it has effect

[Ben Scholzen 'DASPRiD']

Happens on Ubuntu GNOME 14.04 now as well since about a week.

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

Title:
  Sometimes I have to select logout/shut down twice before it has effect

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

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

Re: [Bug 517021] Re: gvfsd-metadata causes 100% CPU usage

[Ben Bucksch]

Philip,

when I said Please make noise, I didn't meant that you should make 100
comments in the bug. I meant to raise awareness of the bug at the Ubuntu
maintainers who decide which hotfixes to include in a LTS release. I
don't know how that works.

Ben

Philip J Reilly wrote, On 08.03.2015 18:59:
 https://www.linuxliteos.com/forums/index.php?topic=1688.0


-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/517021

Title:
  gvfsd-metadata causes 100% CPU usage

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

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

[Bug 517021] Re: gvfsd-metadata causes 100% CPU usage

[Ben Bucksch]

See the remote bug watches on the right here. It links to gnome-bugs
#637095 https://bugzilla.gnome.org/show_bug.cgi?id=637095 , which is
FIXED.

Given that this bug can trash SSDs on hardware level, by making so many
writes that the lifespan is considerably reduced, by doing billions of
write calls in a matter of hours, I'm asking for a hotfix in Ubuntu
12.04 precise.

Given that SSDs are silent, a user wouldn't even notice this unless he
has a CPU or disk meter or similar showing. I do, but I still missed
this once and it ran for 10 hours overnight IIRC.

How can we escalate this for a hotfix in a stable distro? I don't know
launchpad well enough. Could somebody please make some noise? There's
already a straight-forward fix, and commited to the GNOME repo, it's
just a matter of shipping it for the stable Ubuntu distros.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/517021

Title:
  gvfsd-metadata causes 100% CPU usage

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

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

[Bug 517021] Re: gvfsd-metadata causes 100% CPU usage

[Ben Bucksch]

Philip, the reproduction using Firefox has been investigated and
confirmed to be a gvfs bug (not Firefox bug), and has already been FIXED
(!) in the GNOME bug that I've been linking above.

This is just Ubuntu being inactive in shipping the fix.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/517021

Title:
  gvfsd-metadata causes 100% CPU usage

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

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

[Bug 517021] Re: gvfsd-metadata causes 100% CPU usage

[Ben Bucksch]

** Description changed:

  Binary package hint: gvfs
  
- My disk space was really full at one moment, no byte left free. People say, 
that does corrupt the files in the ~/.local/share/gvfs-metadata folder, so the 
gvfsd-metadata can't read it without being screwed up.
- Workaround: run rm -rf ~/.local/share/gvfs-metadata
+ Failure to write metadata results in an infinite loop that keeps trying
+ to write, thousands of times per second.
  
- Expected results:
- gvfsd-metadata should be able to handle the no space left situation.
+ Steps to reproduce:
+ 1. Open Firefox
+ 2. Save a data: URL (very long URL, usually generated by webapps or 
extensions) as file
+ 
+ Actual result:
+ - File is saved
+ - 100% CPU
+ - Extremely high number of file operations by gvfs - billions
+ - Never stops
+ 
+ Expected result:
+ Failure to write metadata should just fail, not try again
+ 
+ Fix:
+ Patch available and accepted by GNOME
+ https://bugzilla.gnome.org/show_bug.cgi?id=637095
+ 
  
  --- Original description ---
  After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or 
Gnome-commander take several minutes when there are many files in it e.g. 
10.000. Interestingly Midnight-commander does not have this problem. Opening 
such folders does not hang with MC.
  Using top i can see that gvfsd-metadata is using 100% CPU and when i kill 
it the computer stops hanging. I am using the 32bit version of Karmic too and 
there is no such Problem (although tested on a different computer).
  
  Please fix this because it is highly annyoing. Right now i am killing it
  every 20s with the watch command to be able to work at all.

** Description changed:

  Binary package hint: gvfs
  
  Failure to write metadata results in an infinite loop that keeps trying
  to write, thousands of times per second.
  
  Steps to reproduce:
  1. Open Firefox
- 2. Save a data: URL (very long URL, usually generated by webapps or 
extensions) as file
+ 2. Save a data: URL (URL that contains the content, with several thousands 
bytes, often generated by webapps or extensions) as file
+ 
+ (There are other ways to run into this problem, e.g. disk full or other
+ error situations. data: URLs are just the easiest way to reproduce.)
  
  Actual result:
  - File is saved
  - 100% CPU
  - Extremely high number of file operations by gvfs - billions
  - Never stops
  
  Expected result:
  Failure to write metadata should just fail, not try again
  
  Fix:
  Patch available and accepted by GNOME
  https://bugzilla.gnome.org/show_bug.cgi?id=637095
  
- 
  --- Original description ---
  After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or 
Gnome-commander take several minutes when there are many files in it e.g. 
10.000. Interestingly Midnight-commander does not have this problem. Opening 
such folders does not hang with MC.
  Using top i can see that gvfsd-metadata is using 100% CPU and when i kill 
it the computer stops hanging. I am using the 32bit version of Karmic too and 
there is no such Problem (although tested on a different computer).
  
  Please fix this because it is highly annyoing. Right now i am killing it
  every 20s with the watch command to be able to work at all.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/517021

Title:
  gvfsd-metadata causes 100% CPU usage

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

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

[Bug 1422815] [NEW] Evolution sometimes discards text when inserting signature into reply

[Ben Klein]

Public bug reported:

When I try to reply to a message in Evolution (version 3.12.7-0ubuntu1),
I fill in the reply text and then a signature block. Upon doing the
latter, however, the text sometimes disappears and is replaced by the
signature block instead of having the signature block inserted at the
cursor's location.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: evolution 3.12.7-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: i386
CurrentDesktop: LXDE
Date: Tue Feb 17 11:58:02 2015
InstallationDate: Installed on 2015-01-17 (31 days ago)
InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: evolution
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 utopic

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

Title:
  Evolution sometimes discards text when inserting signature into reply

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

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

[Bug 1395301] [NEW] Inconsistent terminology for Bluetooth pairing

[Ben Harris]

Public bug reported:

The Personal File Sharing Preferences window has two sections relating
to Bluetooth, and those use different terminology (and user interface
features) to describe Bluetooth pairing, both from one another and from
the main Bluetooth settings.

Under Share Files over Bluetooth, the requirement for pairing is
controlled by a tickbox labelled Require remote devices to bond with
this computer, while under Receive Files over Bluetooth, it's
controlled by a pop-up menu labelled Accept files: with options
Always and Only for set up devices.  As far as I can tell from the
docuementation (which disagrees slightly about how the user interface
should look), these controls have equivalent effects and control whether
files can be respectively browsed or sent by unpaired devices.
Meanwhile, the Bluetooth indicator menu uses the phrase Set-up [sic]
New Device, the Bluetooth pane of System Settings describes certain
devices as Paired, and the Ubuntu Desktop Guide explains how to
Connect your computer to a Bluetooth device but helpfully explains
that This is also called pairing the Bluetooth devices.

Personally, I think that both of these settings should be tickboxes, and
their labels should both be phrased in terms of paired deviced, since
that's standard Bluetooth terminology.  For consistency with the Ubuntu
Desktop Guide, perhaps connected would be better (but I think it's
less obvious what it means).

PS: I've just found the Control sharing over Bluetooth page of the
Ubuntu Desktop Guide, which adds to the fun by introducing trusted
devices, which are apparently yet another way of talking about paired
devices.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gnome-user-share 3.0.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic i686
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: i386
CurrentDesktop: Unity
Date: Sat Nov 22 10:53:26 2014
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-motts-20100121-3
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-file-share-properties
InstallationDate: Installed on 2010-06-09 (1626 days ago)
InstallationMedia: Ubuntu GNU/Linux 9.10 Karmic - Build i386 LIVE Binary 
20100121-21:52
SourcePackage: gnome-user-share
UpgradeStatus: Upgraded to trusty on 2014-08-15 (98 days ago)

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


** Tags: apport-bug i386 trusty

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

Title:
  Inconsistent terminology for Bluetooth pairing

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

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

[Bug 1292282] Re: background transparency is not working on gnome terminal

[Ben Scholzen 'DASPRiD']

Will it be backported to LTS?

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

Title:
  background  transparency is not working on gnome terminal

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

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

[Bug 367372] Re: Gedit uses 100% of the CPU while editing files

[Ben Parmeter]

Just installed a fresh install of 14.10 two days ago and I am
experiencing exactly the same thing as user pguth is describing as well.
I really don't have anything else installed, except for the nVidia
graphics drivers, chrome, and steam.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/367372

Title:
  Gedit uses 100% of the CPU while editing files

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

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

[Bug 1224575] Re: gnome-control-center keyboard no longer has way to modify caps lock key behavior

[Ben Davis]

Why was this set to Won't Fix?

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

Title:
  gnome-control-center keyboard no longer has way to modify caps lock
  key behavior

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

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