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

[Julie Brandon]

Seeing the same problem since upgrading from 15.10 to 16.04.

The vm.dirty workarounds and disabling swap don't make a difference.

Once this problem kicks in ALL disk writes become stupidly slow (2MB/s)
until next reboot on both SSD and spinning HDD.

i5-4460/16Gb RAM/ASUS Z97-K

This is an enormous problem not to have at least been assigned to
someone!

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

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

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

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

[Bug 1635023] Re: Regression: quotas prevent yakkety from booting (boots once every ~4 attempts)

[Sergio Callegari]

Sorry, I'm not understanding your comment.

What I understood is that the systemd developers said "It is not our
responsibility if ubuntu does not boot, this is not a systemd bug! In
fact, the issue in booting is caused by some quota related units,
shipped by Ubuntu, that are not part of systemd". Then, I saw that the
faulty systemd units are shipped with the "quota" package, just as you
say. Yet, the upstream quota package does not contain these units. The
systemd quota related units and scripts are a downstream ubuntu (maybe
from debian) addition (in fact, they live in the debian dir of the
package).

This is why I was reporting that the systemd developers suggest that
this is a downstream bug (a bug in the Ubuntu distro), not an upstream
bug (a bug in systemd 231).

I never implied that ubuntu forgot to ship some units. I'm only saying
that the quota units shipped with ubuntu evidently mistake something,
because when they are masked the system boots, otherwise it doesn't.

Possibly, the issue is only triggered if one has quotas+lvm2+fake or
soft raid. This may explain why the mistake got unnoticed when it
slipped in.

I suppose that this bug should be fixed by the maintainers of the quota
package in ubuntu, possibly with the help of the systemd maintainers.

** Package changed: systemd (Ubuntu) => quota (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/1635023

Title:
  Regression: quotas prevent yakkety from booting (boots once every ~4
  attempts)

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

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

[Bug 1620806] Re: gedit edit window is transparent when using Ambiance and Radiance themes

[recepchakan]

** No longer affects: gedit

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

Title:
  gedit edit window  is transparent when using Ambiance and Radiance
  themes

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

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

[Bug 1620806] Re: gedit edit window is transparent when using Ambiance and Radiance themes

[recepchakan]

** Also affects: gedit
   Importance: Undecided
   Status: New

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

Title:
  gedit edit window  is transparent when using Ambiance and Radiance
  themes

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

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

[Bug 1637855] [NEW] Composite characters or Japanese input gets sometimes sent to the wrong terminal window

[Stephane Lapie]

Public bug reported:

At times (I have not found the trigger to reproduce it at will), one
terminal window out of many will refuse to receive complex input
sequences (such as the French composite accented character "ê" (which is
typed with "^ + e" on a french keyboard), or IBus/Anthy Japanese input),
and only these characters will be redirected to another terminal window.

This means that for two terminals, typing in terminal 1 : "Verbe être" results 
in this :
Terminal 1 : "Verbe tre"
Terminal 2 : "ê"

When this happens, the following workarounds work to put things in order :
- close the affected terminal window
- spawn a new one and close it

I am not sure whether this is an IBus problem, or a Gnome Terminal
problem at its core.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: gnome-terminal 3.16.2-1ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
Uname: Linux 4.2.0-35-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Mon Oct 31 01:51:06 2016
InstallationDate: Installed on 2010-01-30 (2465 days ago)
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to wily on 2016-04-16 (197 days ago)

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


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

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

Title:
  Composite characters or Japanese input gets sometimes sent to the
  wrong terminal window

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

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

[Bug 1637854] [NEW] Totem does not allow changing the playback speed on subsequent files

[Dylan Borg]

Public bug reported:

Totem has for as far as I remember, allowed the playback of subsequent
files without closing and reopening the UI. One can simply double click
the next file using nautilus and totem would switch files and start
playback. However when the new UI for changing playback speed was
introduced this has regressed. If I try to change teh playback speed on
one of the subsequent media files, totem would freeze then crash. The
only way to play a subsequent file and change its playback speed is to
close then reopen totem.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: totem 3.22.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
Uname: Linux 4.8.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Oct 30 17:45:32 2016
InstallationDate: Installed on 2016-02-19 (253 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: totem
UpgradeStatus: Upgraded to yakkety on 2016-10-13 (16 days ago)

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


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

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

Title:
  Totem does not allow changing the playback speed on subsequent files

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

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

[Bug 1635677] Re: Right click rename: auto emptying file name is counter-productive.

[Jiawen Chen]

New Finding: This bug happens only when I use the Chinese input method.
The input method is called ibus-Chewing.

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

Title:
  Right click rename: auto emptying file name is counter-productive.

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

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

[Bug 1632964] Re: Regression: systemd does not send all queued DBus Signals when a unit gets inactive

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 231-10

---
systemd (231-10) unstable; urgency=medium

  [ Martin Pitt ]
  * systemctl: Add --wait option to wait until started units terminate again.
  * nss-resolve: return NOTFOUND instead of UNAVAIL on resolution errors.
This makes it possible to configure a fallback to "dns" without breaking
DNSSEC, with "resolve [!UNAVAIL=return] dns".
  * libnss-resolve.postinst: Skip dns fallback if resolve is present.
Only fall back to "dns" if nss-resolve is not installed (for the
architecture of the calling program). Once it is, we never want to fall
back to "dns" as that breaks enforcing DNSSEC verification and also
pointlessly retries NXDOMAIN failures. (LP: #1624071)
  * unit: sent change signal before removing the unit if necessary
(LP: #1632964)
  * networkd: Fix assertion crash on adding VTI with IPv6 addresses
(LP: #1633274)
  * debian/tests/upstream: Stop specifying initrd, it is autodetected now.
  * debian/tests/upstream: Add gcc/libc-dev/make test dependencies,
so that the tests can build helper binaries.

  [ Felipe Sateler ]
  * Explicitly disable installing the upstream-provided PAM configuration.
  * Register interest in the status of dracut and initramfs-tools in reportbug
template

  [ Michael Biebl ]
  * Stop creating systemd-update-utmp-runlevel.service symlinks manually

 -- Martin Pitt   Wed, 26 Oct 2016 13:24:37 +0200

** Changed in: systemd (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

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

Title:
  Regression: systemd does not send all queued DBus Signals when a unit
  gets inactive

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

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

[Bug 1633274] Re: Systemd-networkd crashes with core dump

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 231-10

---
systemd (231-10) unstable; urgency=medium

  [ Martin Pitt ]
  * systemctl: Add --wait option to wait until started units terminate again.
  * nss-resolve: return NOTFOUND instead of UNAVAIL on resolution errors.
This makes it possible to configure a fallback to "dns" without breaking
DNSSEC, with "resolve [!UNAVAIL=return] dns".
  * libnss-resolve.postinst: Skip dns fallback if resolve is present.
Only fall back to "dns" if nss-resolve is not installed (for the
architecture of the calling program). Once it is, we never want to fall
back to "dns" as that breaks enforcing DNSSEC verification and also
pointlessly retries NXDOMAIN failures. (LP: #1624071)
  * unit: sent change signal before removing the unit if necessary
(LP: #1632964)
  * networkd: Fix assertion crash on adding VTI with IPv6 addresses
(LP: #1633274)
  * debian/tests/upstream: Stop specifying initrd, it is autodetected now.
  * debian/tests/upstream: Add gcc/libc-dev/make test dependencies,
so that the tests can build helper binaries.

  [ Felipe Sateler ]
  * Explicitly disable installing the upstream-provided PAM configuration.
  * Register interest in the status of dracut and initramfs-tools in reportbug
template

  [ Michael Biebl ]
  * Stop creating systemd-update-utmp-runlevel.service symlinks manually

 -- Martin Pitt   Wed, 26 Oct 2016 13:24:37 +0200

** Changed in: systemd (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

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

Title:
  Systemd-networkd crashes with core dump

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

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

[Bug 647236] Re: gvfsd-dnssd crashed with signal 7 in avahi_service_resolver_event()

[Amr Ibrahim]

This bug is also fixed in 1.28.3. An SRU request for Xenial is here Bug
#1579505.

** Changed in: gvfs (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  gvfsd-dnssd crashed with signal 7 in avahi_service_resolver_event()

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

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

[Bug 647236] Re: gvfsd-dnssd crashed with signal 7 in avahi_service_resolver_event()

[Amr Ibrahim]

Oops, upstream reopened this bug and they attached new patches in the
upstream bug report which are waiting for testing.

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

Title:
  gvfsd-dnssd crashed with signal 7 in avahi_service_resolver_event()

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

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

[Bug 1637822] [NEW] autosave freezes editor and loses keystrokes

[Stephane Lapie]

Public bug reported:

The very useful autosave feature that runs every five minutes locks up
the editor when it runs, and when it happens, any keystrokes typed
during the interval are lost.

Such that when typing the following (for example) :
abcdefghijklmnopqrstuvwxyz

If autosave runs during that interval, here is an example of what ends up being 
processed :
abcdefghpqrstuvwxyz

As is obvious, keystrokes for "ijklmno" are lost.
This happens every time.

I am not sure if this is specific to gedit, or to the input framework I
am using (IBus, and at times Anthy for Japanese input)

This is quite annoying as it forces me to re-read absolutely everything
I typed to make sure gedit did not miss anything.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: gedit 3.10.4-0ubuntu13
ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
Uname: Linux 4.2.0-35-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Sun Oct 30 20:37:04 2016
InstallationDate: Installed on 2010-01-30 (2464 days ago)
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
SourcePackage: gedit
UpgradeStatus: Upgraded to wily on 2016-04-16 (196 days ago)

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


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

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

Title:
  autosave freezes editor and loses keystrokes

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

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

[Bug 1633824] Re: nautilus ignores trash on external drives

[Wolf Rogner]

I'm not as lucky as clel.

On 4 machines running 16.10 this can be reproduced (no logout/login helps).
3 are Macs, 1 HP.
Different drives (USB-Sticks, HDs, SSDs) used to test.

I could not reproduce this with internal disks though.

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

Title:
  nautilus ignores trash on external drives

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

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

[Bug 1633824] Re: nautilus ignores trash on external drives

[clel]

After logging out and in again to test something else, it just worked
for me (cannot reproduce it), until I rebooted.

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

Title:
  nautilus ignores trash on external drives

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

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

[Bug 1579505] Re: [SRU] Update to 1.28.3 in Xenial

[Amr Ibrahim]

** Description changed:

+ [Description]
+ 
+ Upstream have released a new bugfix release 1.28.3.
+ 
+ [Changes]
+ 
  https://git.gnome.org/browse/gvfs/tree/NEWS?h=gnome-3-20
  
  Major changes in 1.28.3
  ===
  * dnssd: Fix crashes when mount failed
  * gvfs-open: Fix spawning of applications with dashses in their app IDs
  * daemon: Fix crashes caused by NULL certificates
  * afc: Many fixes for iOS support
  * client: Fix missing mount prefix in cached fuse paths
  * dav: Fix IPv6 address handling
  * Translation updates
+ 
+ [QA, testing, regression potential]
+ 
+ Under the GNOME MRE, you can believe all bugs upstream says are fixed
+ are really fixed. Just test the system and make sure there are no
+ regressions (e.g. look at errors.ubuntu.com).

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

Title:
  [SRU] Update to 1.28.3 in Xenial

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

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

[Bug 1193382] Re: Music is always shared even if "share my music" is unselected in the daap plugin

[vrishab]

Not reproducible in latest rhythmbox ( 3.4.1 ).

System details:
--

bugs@ubuntu:~$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.10
DISTRIB_CODENAME=yakkety
DISTRIB_DESCRIPTION="Ubuntu 16.10"

bugs@ubuntu:~$ uname -a
Linux ubuntu 4.8.0-26-generic #28-Ubuntu SMP Tue Oct 18 14:39:52 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux


** Attachment added: "Screenshot: Showing connection refused dialog in DAAP 
client, when 'sharing' is disabled in DAAP server."
   
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1193382/+attachment/4769668/+files/Screenshot%20from%202016-10-30%2012-39-53.png

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

Title:
  Music is always shared even if "share my music" is unselected in the
  daap plugin

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

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