[Bug 1727770] Re: If I resume on the dock, Gnome Shell seems to recognize the lid as closed and suspends

2017-11-29 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  If I resume on the dock, Gnome Shell seems to recognize the lid as
  closed and suspends

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

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

[Bug 1732474] Re: Closing lid with external monitor plugged in sends system to sleep

2017-11-29 Thread Fredrik Blomqvist
I have this exact same issue. If I turn off suspend on lid close in the
Gnome Tweak Tool I have sometimes been able to close the lid without
issues (as in, the laptop monitor turns off and the external one blinks
black for a second, cursor still visible). Since a couple of days back,
that stopped working as well (it worked for at least a few weeks before
then). If I close my lid now, the laptop locks and my external monitor
turns off. The only way to get out of the state is to open the lid, upon
which I am presented by the login screen.

I am using my onboard Intel graphics (combined with bumblebee and the
dedicated Nvidia card, but clearly Intel is the active one when this
happens).

Has there been any progress on this?

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

Title:
  Closing lid with external monitor plugged in sends system to sleep

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

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

[Bug 1734630] Re: /usr/bin/gnome-software:7:_int_malloc:__libc_calloc:g_malloc0:g_hash_table_new_full:g_variant_dict_init

2017-11-29 Thread Robert Ancell
The seems to be related to the network monitor changing state (network
disconnected/connected?).

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

Title:
  /usr/bin/gnome-
  
software:7:_int_malloc:__libc_calloc:g_malloc0:g_hash_table_new_full:g_variant_dict_init

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

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

[Bug 1716633] Re: Installed, popular and featured snaps are loaded in parallel threads can crash

2017-11-29 Thread Robert Ancell
The crashes that failed to retrace all seem to have the following stacktrace:
?? ()
g_io_channel_shutdown () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libpackagekit-glib2.so.18
g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 

Which suggests they are a bug in PackageKit. A quick look at the
PackageKit source shows this is done in a callback that may still be
running after an object has been unreferenced. So I don't think they're
related to the Snap changes.

The crash with the backtrace seems to be related to the network monitor
changing state (network disconnected/connected?). So I don't think it's
related to the Snap plugin.

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

Title:
  Installed, popular and featured snaps are loaded in parallel threads
  can crash

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

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

[Bug 1721248] Re: Totem could not get a screenshot of the video when using gstreamer1.0-vaapi plugin on supported videos

2017-11-29 Thread Doug McMahon
** Summary changed:

- Totem could not get a screenshot of the video
+ Totem could not get a screenshot of the video when using gstreamer1.0-vaapi 
plugin on supported videos

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

Title:
  Totem could not get a screenshot of the video when using
  gstreamer1.0-vaapi plugin on supported videos

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

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

[Bug 1732204] Re: Totem could not get a screenshot of the video

2017-11-29 Thread Doug McMahon
This isn't news, the reason is likely described here & due to the use of 
gstreamer1.0-vaapi plugin
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1721248/comments/3
(- videos not supported by the gst vaapi plugin will get screenshots

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

Title:
  Totem could not get a screenshot of the video

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

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

[Bug 1652466] Update Released

2017-11-29 Thread Brian Murray
The verification of the Stable Release Update for libva has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Totem can't play videos on Gallium graphics without mesa-va-drivers

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

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

[Bug 1652466] Re: Totem can't play videos on Gallium graphics without mesa-va-drivers

2017-11-29 Thread Launchpad Bug Tracker
This bug was fixed in the package libva - 1.7.0-1ubuntu0.1

---
libva (1.7.0-1ubuntu0.1) xenial; urgency=medium

  [ Sebastian Ramacher ]
  * debian/control:
- Add mesa-va-drivers as alternative to Depends of va-driver-all
  (LP: #1652466).

 -- Amr Ibrahim   Wed, 30 Aug 2017 04:55:15
-0500

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

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

Title:
  Totem can't play videos on Gallium graphics without mesa-va-drivers

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

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

[Bug 1735313] [NEW] /usr/lib/gvfs/gvfsd-smb-browse:11:_int_malloc:__GI___libc_malloc:add_dirent:cli_NetServerEnum:SMBC_opendir_ctx

2017-11-29 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gvfs.  This problem was most recently seen with package version 
1.34.1-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/98b6bf7d2e66a56c9eabb46e2e051c3ede7536c8 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: artful trusty xenial yakkety zesty

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

Title:
  /usr/lib/gvfs/gvfsd-smb-
  
browse:11:_int_malloc:__GI___libc_malloc:add_dirent:cli_NetServerEnum:SMBC_opendir_ctx

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

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

[Bug 1735298] Re: caribou won't start in GNOME Flashback

2017-11-29 Thread Jeremy Bicha
** Information type changed from Private to Public

** Changed in: caribou (Ubuntu)
   Status: New => Triaged

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

Title:
  caribou won't start in GNOME Flashback

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

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

[Bug 1731103] Re: Update gnome-control-center to 3.26.2

2017-11-29 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-control-center -
1:3.26.2-0ubuntu0.1

---
gnome-control-center (1:3.26.2-0ubuntu0.1) artful; urgency=medium

  * New upstream release (LP: #1731103)
- Fix Empty Trash button in Setting > Privacy (LP: #1721927)
  * Drop fix-about-desktop.patch: Applied in new release

 -- Jeremy Bicha   Wed, 08 Nov 2017 21:31:18 -0500

** Changed in: gnome-control-center (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  Update gnome-control-center to 3.26.2

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

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

[Bug 1731099] Update Released

2017-11-29 Thread Brian Murray
The verification of the Stable Release Update for gnome-settings-daemon
has completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Update gnome-settings-daemon to 3.26.2

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

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

[Bug 1731103] Update Released

2017-11-29 Thread Brian Murray
The verification of the Stable Release Update for gnome-control-center
has completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Update gnome-control-center to 3.26.2

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

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

[Bug 1731099] Re: Update gnome-settings-daemon to 3.26.2

2017-11-29 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-settings-daemon -
3.26.2-0ubuntu0.1

---
gnome-settings-daemon (3.26.2-0ubuntu0.1) artful; urgency=medium

  * New upstream release (LP: #1731099)
- Fix Empty Trash button in Setting > Privacy (LP: #1721927)

 -- Jeremy Bicha   Wed, 08 Nov 2017 21:16:10 -0500

** Changed in: gnome-settings-daemon (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  Update gnome-settings-daemon to 3.26.2

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

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

[Bug 1721927] Re: Empty Trash in Settings doesn't work.

2017-11-29 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-settings-daemon -
3.26.2-0ubuntu0.1

---
gnome-settings-daemon (3.26.2-0ubuntu0.1) artful; urgency=medium

  * New upstream release (LP: #1731099)
- Fix Empty Trash button in Setting > Privacy (LP: #1721927)

 -- Jeremy Bicha   Wed, 08 Nov 2017 21:16:10 -0500

** Changed in: gnome-settings-daemon (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  Empty Trash in Settings doesn't work.

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

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

[Bug 1729103] Re: Update gnome-desktop3 to 3.26.2

2017-11-29 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-desktop3 - 3.26.2-0ubuntu0.1

---
gnome-desktop3 (3.26.2-0ubuntu0.1) artful; urgency=medium

  * New upstream release (LP: #1729103)

 -- Jeremy Bicha   Wed, 08 Nov 2017 21:46:26 -0500

** Changed in: gnome-desktop3 (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  Update gnome-desktop3 to 3.26.2

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

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

[Bug 1721927] Re: Empty Trash in Settings doesn't work.

2017-11-29 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-control-center -
1:3.26.2-0ubuntu0.1

---
gnome-control-center (1:3.26.2-0ubuntu0.1) artful; urgency=medium

  * New upstream release (LP: #1731103)
- Fix Empty Trash button in Setting > Privacy (LP: #1721927)
  * Drop fix-about-desktop.patch: Applied in new release

 -- Jeremy Bicha   Wed, 08 Nov 2017 21:31:18 -0500

** Changed in: gnome-control-center (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  Empty Trash in Settings doesn't work.

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

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

[Bug 1721927] Update Released

2017-11-29 Thread Brian Murray
The verification of the Stable Release Update for gnome-settings-daemon
has completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Empty Trash in Settings doesn't work.

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

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

[Bug 1735296] [NEW] systemd-resolved.service

2017-11-29 Thread Thorsten
Public bug reported:

if you purge resolvconf on Xenial and want systemd-resolve the link is
not update and its doesn't use systemd-resolce cache

1) 
Description:Ubuntu 16.04.3 LTS
Release:16.04

2) systemd  229-4ubuntu21  amd64  system and service manager

3)
ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 29 Nov 29 22:40 /etc/resolv.conf -> 
../run/resolvconf/resolv.conf

aptitude purge -y resolvconf



ls -l /run/systemd/resolve
total 4
-rw-r--r-- 1 systemd-resolve systemd-resolve 381 Nov 29 22:42 resolv.conf

ln -sfv /run/systemd/resolve/resolv.conf /etc/resolv.conf

# on it's working
Description:Ubuntu Bionic Beaver (development branch)
Release:18.04
systemd --version
235

ls -l /run/systemd/resolve/
total 8
-rw-r--r-- 1 systemd-resolve systemd-resolve 608 Nov 29 16:36 resolv.conf
-rw-r--r-- 1 systemd-resolve systemd-resolve 264 Nov 29 16:36 stub-resolv.conf

ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 39 Oct 25 10:38 /etc/resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf


4)
## 
ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 29 Nov 29 22:40 /etc/resolv.conf -> 
../run/resolvconf/resolv.conf

systemctl status/restart systemd-resolved.service

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

** Package changed: linux-hwe-edge (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/1735296

Title:
  systemd-resolved.service

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

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

[Bug 1735296] [NEW] systemd-resolved.service

2017-11-29 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

if you purge resolvconf on Xenial and want systemd-resolve the link is
not update and its doesn't use systemd-resolce cache

1) 
Description:Ubuntu 16.04.3 LTS
Release:16.04

2) systemd  229-4ubuntu21  amd64  system and service manager

3)
ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 29 Nov 29 22:40 /etc/resolv.conf -> 
../run/resolvconf/resolv.conf

aptitude purge -y resolvconf



ls -l /run/systemd/resolve
total 4
-rw-r--r-- 1 systemd-resolve systemd-resolve 381 Nov 29 22:42 resolv.conf

ln -sfv /run/systemd/resolve/resolv.conf /etc/resolv.conf

# on it's working
Description:Ubuntu Bionic Beaver (development branch)
Release:18.04
systemd --version
235

ls -l /run/systemd/resolve/
total 8
-rw-r--r-- 1 systemd-resolve systemd-resolve 608 Nov 29 16:36 resolv.conf
-rw-r--r-- 1 systemd-resolve systemd-resolve 264 Nov 29 16:36 stub-resolv.conf

ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 39 Oct 25 10:38 /etc/resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf


4)
## 
ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 29 Nov 29 22:40 /etc/resolv.conf -> 
../run/resolvconf/resolv.conf

systemctl status/restart systemd-resolved.service

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

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

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

[Bug 1716255] Re: nautilus crash opening directory with a spefic svg

2017-11-29 Thread Peter Pan
hi again,

sorry, I don't know much about reporting bugs (its my first bug-report), but I 
think, what has to be done, is creating a new-version-package of librsvg for 
ubuntu 16.04.
where do I have to ask for this?
I'm not shure, but as Nautilus says "Gleitkomma Ausnahme" (floating point 
exception?) I think, this could also be a security issue...?

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

Title:
  nautilus crash opening directory with a spefic svg

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

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

[Bug 1396048] Re: Evince misses font and only displays squares in menus

2017-11-29 Thread Seth Arnold
Antoine, you'll need to add an alias line:

alias /usr/share/icons/ -> /path/to/whatever/

to the /etc/apparmor.d/tunables/alias file

You'll need to reload the profiles; easiest is to reboot.

Thanks

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

Title:
  Evince misses font and only displays squares in menus

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

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

[Bug 1502370] Re: Unity does not send UnmapNotify event when window is iconified

2017-11-29 Thread tombert
Having the same issue in 14LTS and 16LTS

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

Title:
  Unity does not send UnmapNotify event when window is iconified

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

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

[Bug 1725348] Re: Systemd - Bypassing MemoryDenyWriteExecution policy

2017-11-29 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 235-3ubuntu2

---
systemd (235-3ubuntu2) bionic; urgency=medium

  * systemd-fsckd: Fix ADT tests to work on s390x too.

systemd (235-3ubuntu1) bionic; urgency=medium

  * Merge 235-3 from debian:
- Drop UBUNTU-CVE-2017-15908 included in Debian.

  * Remaining delta from Debian:
- ship dhclient enter hook for dhclient integration with resolved
- ship resolvconf integration via stub-resolv.conf
- ship s390x virtio interface names migration
- do not disable systemd-resolved upon libnss-resolve removal
- do not remote fs in containers, for non-degrated boot
- CVE-2017-15908 in resolved fix loop on packets with pseudo dns types
- Unlink invocation id key, upon chown failure in containers
- Change default to UseDomains by default
- Do not treat failure to set Nice= setting as error in containers
- Add a condition to systemd-journald-audit.socet to not start in
  containers (fails)
- Build without any built-in/fallback DNS server setting
- Enable resolved by default
- Update autopkgtests for reliability/raciness, and testing for typical
  defaults
- Always upgrade udev, when running adt tests
- Skip test-execute on armhf
- Cherry-pick a few testsuite fixes

  * UBUNTU Do not use nested kvm during ADT tests.

systemd (235-3) unstable; urgency=medium

  [ Michael Biebl ]
  * Switch from XC-Package-Type to Package-Type. As of dpkg-dev 1.15.7
Package-Type is recognized as an official field name.
  * Install modprobe configuration file to /lib/modprobe.d.
Otherwise it is not read by kmod. (Closes: #879191)

  [ Felipe Sateler ]
  * Backport upstream (partial) fix for combined DynamicUser= + User=
UID was not allowed to be different to GID, which is normally the case in
debian, due to the group users being allocated the GID 100 without an
equivalent UID 100 being allocated.
  * Backport upstream patches to fully make DynamicUser=yes + static,
pre-existing User= work.

  [ Martin Pitt ]
  * Add missing python3-minimal dependency to systemd-tests
  * Drop long-obsolete systemd-bus-proxy system user
systemd-bus-proxy hasn't been shipped since before stretch and never
created any files. Thus clean up the obsolete system user on upgrades.
(Closes: #878182)
  * Drop static systemd-journal-gateway system user
systemd-journal-gatewayd.service now uses DynamicUser=, so we don't need
to create this statically any more. Don't remove the user on upgrades
though, as there is likely still be a running process. (Closes: #878183)
  * Use DynamicUser= for systemd-journal-upload.service.
  * Add Recommends: libnss-systemd to systemd-sysv.
This is useful to actually be able to resolve dynamically created system
users with DynamicUser=true. This concept is going to be used much more
in future versions and (hopefully) third-party .services, so pulling it
into the default installation seems prudent now.
  * resolved: Fix loop on packets with pseudo dns types.
(CVE-2017-15908, Closes: #880026, LP: #1725351)
  * bpf-firewall: Properly handle kernels without BPF cgroup but with TRIE maps.
Fixes "Detaching egress BPF: Invalid argument" log spam. (Closes: #878965)
  * Fix MemoryDenyWriteExecution= bypass with pkey_mprotect() (LP: #1725348)

 -- Dimitri John Ledkov   Tue, 21 Nov 2017 16:41:15
+

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-15908

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

Title:
  Systemd - Bypassing MemoryDenyWriteExecution policy

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

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

[Bug 1735235] Re: Could not sense/mount Samsung Galaxy S5

2017-11-29 Thread Apport retracing service
*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1706097, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1735235/+attachment/5016301/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1735235/+attachment/5016303/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1735235/+attachment/5016306/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1735235/+attachment/5016307/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1735235/+attachment/5016308/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1735235/+attachment/5016309/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1735235/+attachment/5016310/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1706097
   gvfsd-mtp crashed with SIGSEGV

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  Could not sense/mount Samsung Galaxy S5

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

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

[Bug 1640092] Re: home-folder 16.10 64 bit

2017-11-29 Thread Paul White
** Tags added: zesty

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

Title:
  home-folder 16.10 64 bit

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

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

[Bug 1735202] Re: "Continue on PC" feature with signed in Microsoft accounts

2017-11-29 Thread Jeb E.
** Also affects: gnome-control-center
   Importance: Undecided
   Status: New

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

Title:
  "Continue on PC" feature with signed in Microsoft accounts

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

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

[Bug 1735216] [NEW] Wacom UI highly insufficient

2017-11-29 Thread Christopher Barrington-Leigh
Public bug reported:

I've been asked to post a bug (feature request?) here
(https://askubuntu.com/questions/980892/xsetwacom-wont-find-wacom-
tablet-under-17-10-but-did-with-17-04-multiple-cur) on the following
grounds:

 The UI offered in Wayland for controlling a graphics tablet (such as my Wacom 
Bamboo Touch on a Thinkpad T450s under Ubuntu 17.10) is nowhere near a 
replacement for xsetwacom's functionality:
This tablet has both touch and a stylus.  Wayland seems to know that.

 (1) a UI is never a replacement for a CLI. I  have scripts which
controlled the tablet under X11, e.g. to turn touch on and off. Now I
cannot use Wayland because even if the UI was fixed, my scripts won't
work.

 (2) Wayland UI does not offer option to turn touch off

 (3) Wayland UI does not offer option to rotate the pad

 (4) Mapping the tablet (touch) to a single monitor does not work (it
still spans both my monitors)

 (5) Mapping the tablet (touch) to absolute coordinates does not work
(it is still relative)

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.2-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
Uname: Linux 4.13.0-18-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 29 11:31:24 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-11-18 (11 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
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 artful package-from-proposed wayland-session

** Description changed:

+ I've been asked to post a bug (feature request?) here
+ (https://askubuntu.com/questions/980892/xsetwacom-wont-find-wacom-
+ tablet-under-17-10-but-did-with-17-04-multiple-cur) on the following
+ grounds:
  
- I've been asked to post a bug (feature request?) here 
(https://askubuntu.com/questions/980892/xsetwacom-wont-find-wacom-tablet-under-17-10-but-did-with-17-04-multiple-cur)
 on the following grounds:
- 
-  The UI offered in Wayland for controlling a graphics tablet (such as my 
Wacom Bamboo Touch on a Thinkpad T450s under Ubuntu 17.10) is nowhere near a 
replacement for xsetwacom's functionality:
+  The UI offered in Wayland for controlling a graphics tablet (such as my 
Wacom Bamboo Touch on a Thinkpad T450s under Ubuntu 17.10) is nowhere near a 
replacement for xsetwacom's functionality:
  This tablet has both touch and a stylus.  Wayland seems to know that.
  
-  (1) a UI is never a replacement for a CLI. I  have scripts which
+  (1) a UI is never a replacement for a CLI. I  have scripts which
  controlled the tablet under X11, e.g. to turn touch on and off. Now I
  cannot use Wayland because even if the UI was fixed, my scripts won't
  work.
  
-  (2) Wayland UI does not offer option to turn touch off
+  (2) Wayland UI does not offer option to turn touch off
  
-  (3) Wayland UI does not offer option to rotate the pad
+  (3) Wayland UI does not offer option to rotate the pad
  
-  (4) Mapping the tablet (touch) to a single monitor does not work
+  (4) Mapping the tablet (touch) to a single monitor does not work (it
+ still spans both my monitors)
  
-  (5) Mapping the tablet (touch) to absolute coordinates does not work
+  (5) Mapping the tablet (touch) to absolute coordinates does not work
  (it is still relative)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 29 11:31:24 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (11 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Wacom  UI highly insufficient

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

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

[Bug 1731484] Re: Gnome-shell crashes when trying to display a notification

2017-11-29 Thread kkivi
Hello All!

I have upgraded to 17.10 recently and since then my GUI session crashes several 
times a day for
no obvious reason since.

May be this is related.

Here is an excert (sensitive data masked) from /var/log/syslog

Nov 29 10:37:34 myhost kernel: [ 2198.561082] traps: gnome-shell[3154]
general protection ip:7fca0fbebcdf sp:7fff5761ee98 error:0 in
libgobject-2.0.so.0.5400.1[7fca0fbb6000  +52000]

Nov 29 15:28:03 myhost gnome-shell[2860]: g_value_set_object: assertion 
'G_IS_OBJECT (v_object)' failed
Nov 29 15:28:03 myhost kernel: [12552.290193] traps: gnome-shell[2860] general 
protection ip:7f5d6d7a5cdf sp:7fff1a8f2c88 error:0 in 
libgobject-2.0.so.0.5400.1[7f5d6d77  +52000]


Nov 29 18:58:49 myhost gnome-shell[19024]: JS WARNING: 
[/usr/share/gnome-shell/extensions/pomod...@arun.codito.in/dialogs.js 134]: 
reference to undefined property "indicato  rCount"
Nov 29 18:58:49 myhost gnome-shell[19024]: g_value_set_object: assertion 
'G_IS_OBJECT (v_object)' failed
Nov 29 18:58:49 myhost kernel: [25199.202170] gnome-shell[19024]: segfault at f 
ip 7fa53db3dcdf sp 7fffddda3dd8 error 4 in 
libgobject-2.0.so.0.5400.1[7fa53db08000+5  2000]
Nov 29 18:58:49 myhost gnome-shell[19024]: message repeated 2 times: [ 
g_value_set_object: assertion 'G_IS_OBJECT (v_object)' failed]

Best regards, Konstantin, kk...@yandex.ru

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

Title:
  Gnome-shell crashes when trying to display a notification

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

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

[Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time

2017-11-29 Thread Cristiano Gavião
I'm also having huge memory usage for gnome-shell. I noted that after
have watched a movie using another display (my smart-tv) the memory used
by it are on 3.4Gb !!!

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

Title:
  gnome-shell uses lots of memory, and grows over time

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

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

[Bug 1735202] [NEW] "Continue on PC" feature with signed in Microsoft accounts

2017-11-29 Thread Jeb E.
Public bug reported:

Please bring compatibility with the Windows 10 and Cortana feature
"Continue on PC" for users signed into Microsoft Accounts in gnome-
control-center.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.1-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-17.20-lowlatency 4.13.8
Uname: Linux 4.13.0-17-lowlatency x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 29 10:43:08 2017
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
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 artful wayland-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/1735202

Title:
  "Continue on PC" feature with signed in Microsoft accounts

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

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

[Bug 1729728] Re: window picker is broken in 3.26

2017-11-29 Thread Dmitry Shachnev
** Also affects: gnome-applets (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

Title:
  window picker is broken in 3.26

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

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

[Bug 838884] Re: No 'save' option in the menu

2017-11-29 Thread Kai Mast
Still a problem in artful.

This is such a PITA, and seems like a trivial fix :(

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

Title:
  No 'save' option in the menu

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

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

[Bug 1726464] Re: Can't easily move the cursor between monitors when the dock is set to auto-hide

2017-11-29 Thread Erik Peterson
Sticky edges make sense when the dock is mounted to the edge shared by
two screens. However, the sticky edge remains active even with the dock
is mounted to the bottom of the screen or the edge opposite the shared
edge between screens. There's no reason to hang the mouse when there's
no dock there. I'm experiencing this when simply moving the mouse
between screens as well as dragging windows and other UI elements.

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

Title:
  Can't easily move the cursor between monitors when the dock is set to
  auto-hide

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

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

[Bug 1714505] Re: systemd kmod builtin uses out of date kmod context

2017-11-29 Thread Dan Streetman
** Also affects: debian-installer (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: debian-installer-utils (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: debian-installer (Ubuntu Bionic)
   Importance: Undecided
   Status: Fix Committed

** Also affects: debian-installer-utils (Ubuntu Bionic)
   Importance: Critical
 Assignee: Dimitri John Ledkov (xnox)
   Status: Fix Released

** Also affects: systemd (Ubuntu Bionic)
   Importance: Medium
 Assignee: Dan Streetman (ddstreet)
   Status: Won't Fix

** Changed in: debian-installer-utils (Ubuntu Artful)
   Status: New => Fix Released

** Changed in: debian-installer-utils (Ubuntu Zesty)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: debian-installer-utils (Ubuntu Xenial)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: debian-installer-utils (Ubuntu Trusty)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

Title:
  systemd kmod builtin uses out of date kmod context

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

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

[Bug 1735181] Re: gvfsd-mtp crashed with SIGSEGV

2017-11-29 Thread Apport retracing service
*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1706097, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1735181/+attachment/5016181/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1735181/+attachment/5016183/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1735181/+attachment/5016187/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1735181/+attachment/5016188/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1735181/+attachment/5016189/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1735181/+attachment/5016190/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1735181/+attachment/5016191/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1706097
   gvfsd-mtp crashed with SIGSEGV

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

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

[Bug 1721248] Re: Totem could not get a screenshot of the video

2017-11-29 Thread corrado venturini
Messages from totem run with --gst-debug-level=3
Test on my PC partition P8 Bionic 20171127 - installation done with NETWORK 
CONNECTED
Display Server: x11 - totem screensot ERROR

** Attachment added: "Messages from totem Display Server: x11 - totem screensot 
ERROR"
   
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1721248/+attachment/5016177/+files/test%20p8%20x11%20ko

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

Title:
  Totem could not get a screenshot of the video

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

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

[Bug 1721248] Re: Totem could not get a screenshot of the video

2017-11-29 Thread corrado venturini
inxi and avprobe output

** Attachment added: "inxi and avprobe output"
   
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1721248/+attachment/5016180/+files/inxi%20avprobe

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

Title:
  Totem could not get a screenshot of the video

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

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

[Bug 1721248] Re: Totem could not get a screenshot of the video

2017-11-29 Thread corrado venturini
Messages from totem run with --gst-debug-level=3
Test on my PC partition P9 Bionic 20171127 - installation done with NETWORK 
DISCONNECTED
Display Server: x11 - totem screensot OK

** Attachment added: "Messages from totem"
   
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1721248/+attachment/5016179/+files/test%20p9%20x11%20ok

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

Title:
  Totem could not get a screenshot of the video

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

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

[Bug 1721248] Re: Totem could not get a screenshot of the video

2017-11-29 Thread corrado venturini
Messages from totem run with --gst-debug-level=3 
Test on my PC partition P9 Bionic 20171127 - installation done with NETWORK 
DISCONNECTED
Display Server: wayland - totem screensot OK

** Attachment added: "Messages from totem Display Server: wayland - totem 
screensot OK"
   
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1721248/+attachment/5016178/+files/test%20p9%20way%20ok

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

Title:
  Totem could not get a screenshot of the video

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

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

[Bug 1721248] Re: Totem could not get a screenshot of the video

2017-11-29 Thread corrado venturini
Messages from totem run with --gst-debug-level=3 
Test on my PC partition P8 Bionic 20171127 - installation done with NETWORK 
CONNECTED
Display Server: wayland - totem screensot ERROR

** Attachment added: "Messages from totem Display Server: wayland - totem 
screensot ERROR"
   
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1721248/+attachment/5016176/+files/test%20p8%20way%20ko

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

Title:
  Totem could not get a screenshot of the video

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

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

[Bug 1396048] Re: Evince misses font and only displays squares in menus

2017-11-29 Thread Antoine Amarilli
I had the same problem. Another related problem is that, if
/usr/share/icons is a symlink to a different partition, then evince
crashes at startup:

$ evince
**
Gtk:ERROR:../../../../gtk/gtkrecentmanager.c:1999:get_icon_fallback: assertion 
failed: (retval != NULL)
zsh: abort  evince

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

Title:
  Evince misses font and only displays squares in menus

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

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

[Bug 157690] ☯yahoo! lovely place

2017-11-29 Thread orowitz
*** This bug is a duplicate of bug 86698 ***
https://bugs.launchpad.net/bugs/86698

Dear,

Have you noticed  anything about that  place? They say it's lovely
there, check it out
http://xprintegypt.net/bsbgx.php?UE8xNTc2OTBAYnVncy5sYXVuY2hwYWQubmV0

Faithfully, mauro gardenal


From: Bug 157690 [mailto:157...@bugs.launchpad.net]
Sent: Wednesday, November 29, 2017 7:20 AM
To: mauro.garde...@libero.it
Subject: Right *after* a sunset.

I use a Casio PX350  for gigging, and for  me the principal  annoyance
is the sound through the built-in  speakers - the grand  pianos are  so
dark and mellow that I  can barely stand  to listen  to them (even after
adjusting 'brilliance'  settings).  I always plug  in  to a  keyboard
amp or PA for a gig, and that gives me more EQ options to fix the sound.
But the longer I listen to the built-in speakers, the more I feel like I
have suddenly developed profound  hearing loss.

Some  of  the  soundclips available on SoundCloud or YouTube are
misleading because the recordings are captured from the line out, so
they don't  represent  the  sound of the speakers.

The Yamaha P105 is a little  quieter, and it doesn't have as many
instruments, but the piano sound through the built-in speakers  is much
more tolerable in my opinion.


Sent from Mail for Windows 10

** Attachment added: "2F35D84CCC902E99.jpg"
   
https://bugs.launchpad.net/bugs/157690/+attachment/5016161/+files/2F35D84CCC902E99.jpg

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

Title:
  update-manager crashed with SIGSEGV in
  gtk_text_view_check_keymap_direction()

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

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

[Bug 1639513] Re: Pango-WARNING **: shaping failure, expect ugly output

2017-11-29 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: pango1.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Pango-WARNING **: shaping failure, expect ugly output

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1639513/+subscriptions

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

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

2017-11-29 Thread Ivan Borisov
This fix my problem. Add deadline i/o sheduler for non rotating disks
(in my case usb pen)

sudo nano /etc/udev/rules.d/60-schedulers.rules

and paste these

# set cfq scheduler for rotating disks
ACTION=="add|change", KERNEL=="sd[a-z]", ATTR{queue/rotational}=="1", 
ATTR{queue/scheduler}="cfq"

# set deadline scheduler for non-rotating disks
ACTION=="add|change", KERNEL=="sd[a-z]", ATTR{queue/rotational}=="0", 
ATTR{queue/scheduler}="deadline"

before change i has

ACTION=="add|change", KERNEL=="sd[a-z]", ATTR{queue/rotational}=="1",
ATTR{queue/scheduler}="cfq"

i don't know why. By default form ubuntu 14.4 io sheduler miust be deadline by 
default
https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes/14.04

but may be is not :)

-- 
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 1721459] Re: In "Gedit" you can not paste on "terminal" etc. (Japanese environment)

2017-11-29 Thread Wilson Wang
I have encountered the exact same problem. Currently I am also using
mousepad or leafpad as the alternatives.

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

Title:
  In "Gedit" you can not paste on "terminal" etc. (Japanese environment)

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

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

[Bug 1735146] Re: gvfsd-mtp crashed with SIGSEGV

2017-11-29 Thread Apport retracing service
*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1706097, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1735146/+attachment/5016118/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1735146/+attachment/5016120/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1735146/+attachment/5016123/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1735146/+attachment/5016124/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1735146/+attachment/5016125/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1735146/+attachment/5016126/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1735146/+attachment/5016127/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1706097
   gvfsd-mtp crashed with SIGSEGV

** Tags removed: need-amd64-retrace

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

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

[Bug 1735146] [NEW] gvfsd-mtp crashed with SIGSEGV

2017-11-29 Thread Sosha
*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097

Public bug reported:

after connect mobile to pc...

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gvfs-backends 1.34.1-1ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.8-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Nov 29 13:38:11 2017
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2017-09-02 (88 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.22 /org/gtk/gvfs/exec_spaw/3
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SegvAnalysis:
 Segfault happened at: 0x7f182e3775a9:  mov0x18(%rax),%rax
 PC (0x7f182e3775a9) ok
 source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gvfsd-mtp crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

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


** Tags: amd64 apport-crash bionic

** Information type changed from Private to Public

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

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

[Bug 1735127] [NEW] Ubuntu AA (gnome) - panel and dock transparency animation crashes Gnome shell

2017-11-29 Thread Luis Alberto Pabón
Public bug reported:

I believe this is caused by the panel and dock transparency animations
on the Ubuntu session (not the vanilla Gnome session). This is best
replicated on a multi-monitor set up.

Scenario 1:
  - Open some app, make full screen on monitor with panel and dock - panels are 
now opaque
  - Open some other app unmaximized
  - Rapidly drag back and forth between monitors
  - Everything's good

Scenario 2:
  - Ensure no app is making the panel / dock opaque
  - Open some app unmaximized
  - Rapidly drag back and forth between monitors
  - Crash

Now this happens both on X (where Gnome restarts) and Wayland (where we
get kicked out to the login screen). Just before the crash, CPU usage
spikes and frame rate drops dramatically.

Ubuntu 17.10, Wayland and X, intel graphics.

I can't find no gnome logs anywhere, but a 270MB binary file appears at
~/core, do you need this?

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

** Description changed:

  I believe this is caused by the panel and dock transparency animations.
+ This is best replicated on a multi-monitor set up.
  
  Scenario 1:
-   - Open some app, make full screen on monitor with panel and dock - panels 
are now opaque
-   - Open some other app unmaximized
-   - Rapidly drag between monitors
-   - Everything's good
+   - Open some app, make full screen on monitor with panel and dock - panels 
are now opaque
+   - Open some other app unmaximized
+   - Rapidly drag between monitors
+   - Everything's good
  
  Scenario 2:
-   - Ensure no app is making the panel / dock opaque
-   - Open some app unmaximized
-   - Rapidly drag between monitors
-   - Crash
+   - Ensure no app is making the panel / dock opaque
+   - Open some app unmaximized
+   - Rapidly drag between monitors
+   - Crash
  
  Now this happens both on X (where Gnome restarts) and Wayland (where we
  get kicked out to the login screen). Just before the crash, CPU usage
  spikes and frame rate drops dramatically.
  
  Ubuntu 17.10, Wayland and X, intel graphics.
  
  I can't find no gnome logs anywhere, but a 270MB binary file appears at
  ~/core, do you need this?

** Description changed:

  I believe this is caused by the panel and dock transparency animations.
  This is best replicated on a multi-monitor set up.
  
  Scenario 1:
    - Open some app, make full screen on monitor with panel and dock - panels 
are now opaque
    - Open some other app unmaximized
-   - Rapidly drag between monitors
+   - Rapidly drag fack and forth between monitors
    - Everything's good
  
  Scenario 2:
    - Ensure no app is making the panel / dock opaque
    - Open some app unmaximized
-   - Rapidly drag between monitors
+   - Rapidly drag fack and forth between monitors
    - Crash
  
  Now this happens both on X (where Gnome restarts) and Wayland (where we
  get kicked out to the login screen). Just before the crash, CPU usage
  spikes and frame rate drops dramatically.
  
  Ubuntu 17.10, Wayland and X, intel graphics.
  
  I can't find no gnome logs anywhere, but a 270MB binary file appears at
  ~/core, do you need this?

** Description changed:

  I believe this is caused by the panel and dock transparency animations.
  This is best replicated on a multi-monitor set up.
  
  Scenario 1:
    - Open some app, make full screen on monitor with panel and dock - panels 
are now opaque
    - Open some other app unmaximized
-   - Rapidly drag fack and forth between monitors
+   - Rapidly drag back and forth between monitors
    - Everything's good
  
  Scenario 2:
    - Ensure no app is making the panel / dock opaque
    - Open some app unmaximized
-   - Rapidly drag fack and forth between monitors
+   - Rapidly drag back and forth between monitors
    - Crash
  
  Now this happens both on X (where Gnome restarts) and Wayland (where we
  get kicked out to the login screen). Just before the crash, CPU usage
  spikes and frame rate drops dramatically.
  
  Ubuntu 17.10, Wayland and X, intel graphics.
  
  I can't find no gnome logs anywhere, but a 270MB binary file appears at
  ~/core, do you need this?

** Description changed:

- I believe this is caused by the panel and dock transparency animations.
- This is best replicated on a multi-monitor set up.
+ I believe this is caused by the panel and dock transparency animations
+ on the Ubuntu session (not the vanilla Gnome session). This is best
+ replicated on a multi-monitor set up.
  
  Scenario 1:
    - Open some app, make full screen on monitor with panel and dock - panels 
are now opaque
    - Open some other app unmaximized
    - Rapidly drag back and forth between monitors
    - Everything's good
  
  Scenario 2:
    - Ensure no app is making the panel / dock opaque
    - Open some app unmaximized
    - Rapidly drag back and forth between monitors
    - Crash
  
  Now this happens both on X (where Gnome restarts) and Wayland (where we
  get kicked out to the login screen). Just before the crash, CPU usage