[Desktop-packages] [Bug 1564778] Re: package libsane-common 1.0.25+git20150528-1ubuntu2 failed to install/upgrade: trying to overwrite '/etc/sane.d/hp.conf', which is also in package libsane:i386 1.0.

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: sane-backends (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1564778

Title:
  package libsane-common 1.0.25+git20150528-1ubuntu2 failed to
  install/upgrade: trying to overwrite '/etc/sane.d/hp.conf', which is
  also in package libsane:i386 1.0.23-3ubuntu3.1

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Unknown error. I Don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libsane-common 1.0.25+git20150528-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: i386
  Date: Fri Apr  1 13:53:51 2016
  ErrorMessage: trying to overwrite '/etc/sane.d/hp.conf', which is also in 
package libsane:i386 1.0.23-3ubuntu3.1
  InstallationDate: Installed on 2013-06-17 (1019 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.9
  SourcePackage: sane-backends
  Title: package libsane-common 1.0.25+git20150528-1ubuntu2 failed to 
install/upgrade: trying to overwrite '/etc/sane.d/hp.conf', which is also in 
package libsane:i386 1.0.23-3ubuntu3.1
  UpgradeStatus: Upgraded to xenial on 2016-03-28 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1564778/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1577704] Re: package libsane-common 1.0.25+git20150528-1ubuntu2 failed to install/upgrade: tentative de remplacement de « /etc/sane.d/hp.conf », qui appartient aussi au paquet

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1564778
   package libsane-common 1.0.25+git20150528-1ubuntu2 failed to 
install/upgrade: trying to overwrite '/etc/sane.d/hp.conf', which is also in 
package libsane:i386 1.0.23-3ubuntu3.1

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1577704

Title:
  package libsane-common 1.0.25+git20150528-1ubuntu2 failed to
  install/upgrade: tentative de remplacement de « /etc/sane.d/hp.conf »,
  qui appartient aussi au paquet libsane:i386 1.0.23-3ubuntu3.1

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I don't know how to do I novice I passe ubuntu 14.02 LTS to 16.04 LTS
  and I have this

  dpkg: erreur de traitement du paquet linux-image-generic-lts-vivid 
(--configure) :
   problèmes de dépendances - laissé non configuré
  Des erreurs ont été rencontrées pendant l'exécution :
   linux-image-extra-4.4.0-21-generic
   linux-image-generic
   linux-generic
   linux-generic-lts-vivid
   linux-image-generic-lts-vivid
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libsane-common 1.0.25+git20150528-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  Date: Mon May  2 16:23:53 2016
  ErrorMessage: tentative de remplacement de « /etc/sane.d/hp.conf », qui 
appartient aussi au paquet libsane:i386 1.0.23-3ubuntu3.1
  InstallationDate: Installed on 2016-03-13 (50 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: sane-backends
  Title: package libsane-common 1.0.25+git20150528-1ubuntu2 failed to 
install/upgrade: tentative de remplacement de « /etc/sane.d/hp.conf », qui 
appartient aussi au paquet libsane:i386 1.0.23-3ubuntu3.1
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1577704/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1596541] Re: package libsane 1.0.25+git20150528-1ubuntu2 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: trying to overwrite shared '/lib/udev/rules.d/

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1533780
   package libsane 1.0.25+git20150528-1ubuntu2 [modified: 
lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: trying to 
overwrite shared '/lib/udev/rules.d/40-libsane.rules', which is different from 
other instances of package libsane:i386

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1596541

Title:
  package libsane 1.0.25+git20150528-1ubuntu2 [modified:
  lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: trying
  to overwrite shared '/lib/udev/rules.d/40-libsane.rules', which is
  different from other instances of package libsane:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I have added this:
  -
  # Brother scanners
  ATTRS{idVendor}=="04f9", ENV{libsane_matched}="yes"
  -
  To make my brother dcp-195c work

  to
  /lib/udev/rules.d/40-libsane.rules

  and got this error on upgrade

  1.
  ~$ lsb_release -rd
  Description:  Ubuntu 15.10
  Release:  15.10

  2. 
  :~$ apt-cache policy libsane
  libsane:
Installed: 1.0.25+git20150528-1ubuntu2
Candidate: 1.0.25+git20150528-1ubuntu2
Version table:
   *** 1.0.25+git20150528-1ubuntu2 0
  500 http://il.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  3. upgrade should read the rules and handle new ones
  4. it didn't.

  ** the error popped after reboot (and not after update/upgrade)

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: libsane 1.0.25+git20150528-1ubuntu2 [modified: 
lib/udev/rules.d/40-libsane.rules]
  ProcVersionSignature: Ubuntu 4.2.0-38.45-generic 4.2.8-ckt10
  Uname: Linux 4.2.0-38-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Fri Jun 24 12:34:04 2016
  ErrorMessage: trying to overwrite shared 
'/lib/udev/rules.d/40-libsane.rules', which is different from other instances 
of package libsane:i386
  InstallationDate: Installed on 2016-03-30 (88 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu3
  SourcePackage: sane-backends
  Title: package libsane 1.0.25+git20150528-1ubuntu2 [modified: 
lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: trying to 
overwrite shared '/lib/udev/rules.d/40-libsane.rules', which is different from 
other instances of package libsane:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1596541/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1545436] Re: package libsane-common 1.0.23-3ubuntu3.1 failed to install/upgrade: trying to overwrite '/etc/sane.d/hp.conf', which is also in package libsane:amd64 1.0.23-3ubunt

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1544331
   package libsane-common 1.0.23-3ubuntu3.1 failed to install/upgrade: 
tentative de remplacement de « /etc/sane.d/hp.conf », qui appartient aussi au 
paquet libsane:amd64 1.0.23-3ubuntu3.1

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1545436

Title:
  package libsane-common 1.0.23-3ubuntu3.1 failed to install/upgrade:
  trying to overwrite '/etc/sane.d/hp.conf', which is also in package
  libsane:amd64 1.0.23-3ubuntu3.1

Status in sane-backends package in Ubuntu:
  New

Bug description:
  NA

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libsane-common 1.0.23-3ubuntu3.1
  ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
  Uname: Linux 3.19.0-49-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Sun Feb 14 18:55:14 2016
  Dependencies:
   
  DuplicateSignature: package:libsane-common:1.0.23-3ubuntu3.1:trying to 
overwrite '/etc/sane.d/hp.conf', which is also in package libsane:amd64 
1.0.23-3ubuntu3.1
  ErrorMessage: trying to overwrite '/etc/sane.d/hp.conf', which is also in 
package libsane:amd64 1.0.23-3ubuntu3.1
  InstallationDate: Installed on 2015-11-28 (78 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.1.10
  SourcePackage: sane-backends
  Title: package libsane-common 1.0.23-3ubuntu3.1 failed to install/upgrade: 
trying to overwrite '/etc/sane.d/hp.conf', which is also in package 
libsane:amd64 1.0.23-3ubuntu3.1
  UpgradeStatus: Upgraded to xenial on 2016-02-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1545436/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1544331] Re: package libsane-common 1.0.23-3ubuntu3.1 failed to install/upgrade: tentative de remplacement de « /etc/sane.d/hp.conf », qui appartient aussi au paquet libsane:am

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: sane-backends (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1544331

Title:
  package libsane-common 1.0.23-3ubuntu3.1 failed to install/upgrade:
  tentative de remplacement de « /etc/sane.d/hp.conf », qui appartient
  aussi au paquet libsane:amd64 1.0.23-3ubuntu3.1

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Updating from trusty to xenial

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libsane-common 1.0.23-3ubuntu3.1
  ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
  Uname: Linux 3.19.0-49-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Wed Feb 10 23:38:25 2016
  Dependencies:
   
  ErrorMessage: tentative de remplacement de « /etc/sane.d/hp.conf », qui 
appartient aussi au paquet libsane:amd64 1.0.23-3ubuntu3.1
  InstallationDate: Installed on 2016-02-10 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.1.10
  SourcePackage: sane-backends
  Title: package libsane-common 1.0.23-3ubuntu3.1 failed to install/upgrade: 
tentative de remplacement de « /etc/sane.d/hp.conf », qui appartient aussi au 
paquet libsane:amd64 1.0.23-3ubuntu3.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1544331/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1603151] Re: systemctl isolate anyname.target not working

[Martin Pitt]

This is the same with "systemctl stop lightdm", btw. I'm reassigning
this to lightdm.

** Summary changed:

- systemctl isolate anyname.target not working
+ stopping lightdm ends up in an empty console, should switch to VT1

** Package changed: systemd (Ubuntu) => lightdm (Ubuntu)

** Changed in: lightdm (Ubuntu)
   Importance: Undecided => Low

** Changed in: lightdm (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  stopping lightdm ends up in an empty console, should switch to VT1

Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  On Ubuntu 16.04 Cinammon, systemctl isolate multi-user.target hangs the 
system.
  I've tried editing the multi-user.target file as a snippet, or the whole 
thing, but with no fix.
  The system flashes a very momentary prompt to login as a single user without 
a GUI, but then the screen goes black and the system is hung.
  Same on Linux Mint 18.
  systemctl isolate multi-user.target works successfully on OpenSuse Leap 42.1, 
and CentOS 7, as I tested the command on these other systems to check. The 
glaring difference I noticed is that in the multi-user.target unit file, 
AllowIsolate and CanIsolate is set to yes in the other Linux systems, but to no 
in Ubuntu.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1603151] [NEW] stopping lightdm ends up in an empty console, should switch to VT1

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

On Ubuntu 16.04 Cinammon, systemctl isolate multi-user.target hangs the system.
I've tried editing the multi-user.target file as a snippet, or the whole thing, 
but with no fix.
The system flashes a very momentary prompt to login as a single user without a 
GUI, but then the screen goes black and the system is hung.
Same on Linux Mint 18.
systemctl isolate multi-user.target works successfully on OpenSuse Leap 42.1, 
and CentOS 7, as I tested the command on these other systems to check. The 
glaring difference I noticed is that in the multi-user.target unit file, 
AllowIsolate and CanIsolate is set to yes in the other Linux systems, but to no 
in Ubuntu.

** Affects: lightdm (Ubuntu)
 Importance: Low
 Status: Triaged

-- 
stopping lightdm ends up in an empty console, should switch to VT1
https://bugs.launchpad.net/bugs/1603151
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to lightdm in Ubuntu.

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout

[Launchpad Bug Tracker]

[Expired for metacity (Ubuntu) because there has been no activity for 60
days.]

** Changed in: metacity (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome
  session to logout

Status in metacity package in Ubuntu:
  Expired

Bug description:
  This bug seemed to occur already since earlier versions of Ubuntu, and
  usually would just end up leaving me with undecorated windows, from
  which recovery was as easy as restarting metacity by hand, but in this
  release of Ubuntu (15.04), it seems gnome-session tries to restart it
  too many times in a too short span, and then decides arbitrarily that
  it failed so bad it has to kill the whole session.

  So, while the metacity bug is really a thing, my real problem actually might 
be a gnome-session-bin bug.
  I expect metacity crashing would not bring down the whole session, as is the 
case currently.

  At any rate, this is extremely annoying, I am hitting this bug about
  every two days, and because of it and the regression in crash
  handling, I end up losing all my windows and running programs. (In all
  fairness, I am suspecting a hardware issue, but the problem remains
  that a sub process dying should not cause the parent process to die
  like this)

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: metacity 1:3.14.3-1ubuntu7
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Tue Oct 20 05:19:37 2015
  ExecutablePath: /usr/bin/metacity
  InstallationDate: Installed on 2010-01-30 (2088 days ago)
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
  ProcCmdline: metacity
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  Signal: 5
  SourcePackage: metacity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XGetRequest () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XFixesCopyRegion () from /usr/lib/x86_64-linux-gnu/libXfixes.so.3
  Title: metacity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: Upgraded to vivid on 2015-09-05 (44 days ago)
  UserGroups: adm admin audio cdrom dialout libvirtd lpadmin plugdev pulse 
pulse-access sambashare vboxusers video

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1506358] Re: libmirclient gives up and terminates prematurely with "std::exception::what: disconnected: no new buffers" via ExchangeSemantics::submit()

[Daniel van Vugt]

It wasn't till today, but finally there's a bug report of this happening
in the wild on desktop -> bug 1603739

** Changed in: mir
Milestone: None => 0.25.0

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1506358

Title:
  libmirclient gives up and terminates prematurely with
  "std::exception::what: disconnected: no new buffers" via
  ExchangeSemantics::submit()

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Under heavy resizing (stress testing under Valgrind), my Mir client
  (Xmir) crashed with:

  [1444895332.392862]  MirBufferStreamAPI: Caught exception at client 
library boundary (in mir_buffer_stream_swap_buffers): 
/build/mir-7io2Aj/mir-0.16.0+15.10.20150921.1/src/client/buffer_stream.cpp(169):
 Throw in function virtual MirWaitHandle* 
{anonymous}::ExchangeSemantics::submit(const std::function&, 
mir::geometry::Size, MirPixelFormat, int)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: disconnected: no new buffers

  The strange thing is it's only the client that died. The server
  survived and I can connect new clients to it.

  Duplicate bug reports now show Unity8 is another such client suffering
  from this crash. It's occurring on phones in the wild.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1506358/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1602561] Re: supertux2 fails to start, and then Xmir crashes on client exit

[Daniel van Vugt]

Correct, rootless works, seemingly because that's a workaround for bug
1504422 :)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1602561

Title:
  supertux2 fails to start, and then Xmir crashes on client exit

Status in Libertine:
  Invalid
Status in libsdl2 package in Ubuntu:
  Won't Fix
Status in supertux package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  In Progress

Bug description:
  supertux doesn't start

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1588126] Re: [regression] [OTA-11] Wifi never connects since flashing OTA-11 (unless you flash OTA-10 first then upgrade)

[Daniel van Vugt]

** Description changed:

  I've just flashed clean images of OTA-11 from the stable channel onto a
  BQ Aquaris E4.5 (krillin) and a Nexus 4 (mako). In both cases the phones
  can see the wifi networks but can't connect to any of them any more.
  
  The wifi networks continue to work for non-Ubuntu devices.
+ 
+ Explanation:
+ 
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1593686/comments/11

** Summary changed:

- [regression] [OTA-11] Wifi never connects since flashing OTA-11 (unless you 
flash OTA-10 first then upgrade)
+ [regression] [OTA-11] Adding new wifi networks (with long passwords) never 
connect at all since OTA-11

** Description changed:

  I've just flashed clean images of OTA-11 from the stable channel onto a
  BQ Aquaris E4.5 (krillin) and a Nexus 4 (mako). In both cases the phones
  can see the wifi networks but can't connect to any of them any more.
  
  The wifi networks continue to work for non-Ubuntu devices.
  
+ Also, forcefully flashing a device with OTA-10 fixes the problem. The
+ regression began in OTA-11.
+ 
  Explanation:
  
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1593686/comments/11

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

Title:
  [regression] [OTA-11] Adding new wifi networks (with long passwords)
  never connect at all since OTA-11

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I've just flashed clean images of OTA-11 from the stable channel onto
  a BQ Aquaris E4.5 (krillin) and a Nexus 4 (mako). In both cases the
  phones can see the wifi networks but can't connect to any of them any
  more.

  The wifi networks continue to work for non-Ubuntu devices.

  Also, forcefully flashing a device with OTA-10 fixes the problem. The
  regression began in OTA-11.

  Explanation:
  
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1593686/comments/11

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588126/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1593686] Re: Wi-Fi passphrase limit introduced in OTA-11

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1588126
   [regression] [OTA-11] Wifi never connects since flashing OTA-11 (unless you 
flash OTA-10 first then upgrade)

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

Title:
  Wi-Fi passphrase limit introduced in OTA-11

Status in Canonical System Image:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  After installing OTA-11, connectivity to a Cisco AP1131AG AP (IOS
  12.4-25d.JA2) stopped working, possibly due to the length of the WPA
  pass-phrase, which was 29 characters long.  The pass-phrase
  requirement is from 8 to 63 characters.  After reducing the pass-
  phrase to 14 (and sometimes 15) characters connectivity is restored.

  Attempting to connect to a Cisco 1702i (IOS 15.3-3.JC1) which has both
  802.11 ac (wave 1) and 802.11n radios has similar problems: (a) it
  cannot "see" the 802.11ac radio at all (interface Dot11Radio0) and
  although it "sees" the 802.11n radio (interface Dot11Radio1) it cannot
  connect.  The pass-phrase length requirement on both radios is 18 to
  128 characters.

  In both cases the Cisco APs do not log any event.

  Prior to OTA 11 connectivity worked normally on OTA 10.1

  OS: Ubuntu 15.04 (OTA-11) on BQ Aquaris E5

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1593686/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 482836] Re: Samba shared printers not accessible under Vista and Windows7

[Mathew Hodson]

** Package changed: fedora => ubuntu

** No longer affects: ubuntu

** Also affects: samba via
   https://bugzilla.samba.org/show_bug.cgi?id=6888
   Importance: Unknown
   Status: Unknown

** Changed in: cups (Ubuntu)
   Importance: Undecided => Medium

** No longer affects: cups (Ubuntu)

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

Title:
  Samba shared printers not accessible under Vista and Windows7

Status in samba:
  Unknown
Status in samba package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: samba

  1. Ubuntu release:

  #uname -a
  Linux maedchentank 2.6.31-15-generic #49-Ubuntu SMP Fri Nov 6 09:55:13 UTC 
2009 x86_64 GNU/Linux
  # lsb_release -rd
  Description:Ubuntu 9.10
  Release:9.10

  2. involved packages:

  ~# apt-cache policy cups
  cups:
    Installiert: 1.4.1-5ubuntu2.1
    Kandidat: 1.4.1-5ubuntu2.1
  ...
  ~# apt-cache policy samba
  samba:
    Installiert: 2:3.4.0-3ubuntu5.1
    Kandidat: 2:3.4.0-3ubuntu5.1
  ...

  3. What should happen:
  Connecting to shared printers on my ubuntu 9.10 server from within windows 
vista64 and windows7 brings up the windows printer dialog - as is happened in 
ubuntu 9.04.

  4, What happens instead

  Connecting to shared printers on my ubuntu 9.10 server from within windows 
vista(64 Bit) and windows7 (64 Bit)  brings a "Druckerverbindung kann nicht 
hergestellt werden - 0x000d" on Windows (exact english translation not 
known - should be something like "unable to connect to printer - 0x000d". 
Windows isn't telling more. The Windows Support Entry in the web about this 
error number is compete nonsense.
  However Windows XP (32 Bit) clients connect without a problem.
  Note that exactly the same Vista (64 Bit) machine (even without any 
LSA-Manipulations within the registry (as it is still recommanded here and 
there)) did work with the same smb.conf on the same server with ubuntu 9.04 (it 
was updated to 9.10 - meaning it was not a fresh install).
  Typical folder shares on the server are no problem for vista and windows7.

  BTW: Trying to get a clean new smb file is not easy because of this
  dpkg-reconfigure samba crash

  # dpkg-reconfigure samba
   * Stopping Samba daemons 
   [ OK ]
     [doing stuff within the nc gui until the "create 
/var/lib/samba/passdb.tdb?" Question and then...]
  sed: -e Ausdruck #1, Zeichen 143: Unbekannte Option für `s'

  However I am sure to have a clean smb.conf. The most interesting
  section is this (and I already tried to "open" it up as much as it may
  be helpful)

  --
  load printers = yes

     printing = cups
     printcap name = cups

  [...]

  [printers]
     comment = All Printers
     browseable = no
     path = /var/spool/samba
     printable = yes
     guest ok = yes
     read only = yes
     create mask = 0700
  #  inserted ny me
     use client driver = yes

  # Windows clients look for this share name as a source of downloadable
  # printer drivers

  # disabling or not disabling - the [print$] Section is of course not
  changig anything here

  # --
  # [print$]
  #   comment = Printer Drivers
  #   path = /var/lib/samba/printers
  #   browseable = yes
  #   read only = yes
  # #   guest ok = no
  # # changed by me
  # guest ok = yes
  # -

  [...]
  --

  Security levels is users. Password backend is tdbsam.
  Users trying to connect to the printers (2 printers - one usb and cups-pdf) 
are already connected to shared folders on the server successfully (so it is 
not a credentials problem from this side). They are also known to samba thanks 
to smbpasswd.

  On the cups side both printers are set to shared. So anything should
  just work like it does perfectly with Windows XP Clients (32Bit)
  within the same network or like unter Ubuntu 9.04 with the same
  configuration (also with vista64 Clients there).

  I've tried alot about this with no success.
  I was surprised not to find a bug report about this, because, if you google 
about "karmic printer vista" you find a lot forum questions about this - and 
they all try a lot even unrelated things to get rid of this - but the issue 
remains unsolved.
  Like here: 

  Sidenote: Also strange: After starting/restarting the whole server,
  all samba folder shares work perfectly - but not even one printer is
  showing up (at least not on the vista/win7 clients here).  Doing a
  "/etc/init.d/samba restart" on the server makes them visible. This
  can't be a sort of "late usb printer detection" issue, as cups-pdf
  shouldn't be affected by such things. I did not investigate much into
  

[Desktop-packages] [Bug 482836] Re: Samba shared printers not accessible under Vista and Windows7

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ubuntu
   Status: New => Confirmed

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

Title:
  Samba shared printers not accessible under Vista and Windows7

Status in samba:
  Unknown
Status in samba package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: samba

  1. Ubuntu release:

  #uname -a
  Linux maedchentank 2.6.31-15-generic #49-Ubuntu SMP Fri Nov 6 09:55:13 UTC 
2009 x86_64 GNU/Linux
  # lsb_release -rd
  Description:Ubuntu 9.10
  Release:9.10

  2. involved packages:

  ~# apt-cache policy cups
  cups:
    Installiert: 1.4.1-5ubuntu2.1
    Kandidat: 1.4.1-5ubuntu2.1
  ...
  ~# apt-cache policy samba
  samba:
    Installiert: 2:3.4.0-3ubuntu5.1
    Kandidat: 2:3.4.0-3ubuntu5.1
  ...

  3. What should happen:
  Connecting to shared printers on my ubuntu 9.10 server from within windows 
vista64 and windows7 brings up the windows printer dialog - as is happened in 
ubuntu 9.04.

  4, What happens instead

  Connecting to shared printers on my ubuntu 9.10 server from within windows 
vista(64 Bit) and windows7 (64 Bit)  brings a "Druckerverbindung kann nicht 
hergestellt werden - 0x000d" on Windows (exact english translation not 
known - should be something like "unable to connect to printer - 0x000d". 
Windows isn't telling more. The Windows Support Entry in the web about this 
error number is compete nonsense.
  However Windows XP (32 Bit) clients connect without a problem.
  Note that exactly the same Vista (64 Bit) machine (even without any 
LSA-Manipulations within the registry (as it is still recommanded here and 
there)) did work with the same smb.conf on the same server with ubuntu 9.04 (it 
was updated to 9.10 - meaning it was not a fresh install).
  Typical folder shares on the server are no problem for vista and windows7.

  BTW: Trying to get a clean new smb file is not easy because of this
  dpkg-reconfigure samba crash

  # dpkg-reconfigure samba
   * Stopping Samba daemons 
   [ OK ]
     [doing stuff within the nc gui until the "create 
/var/lib/samba/passdb.tdb?" Question and then...]
  sed: -e Ausdruck #1, Zeichen 143: Unbekannte Option für `s'

  However I am sure to have a clean smb.conf. The most interesting
  section is this (and I already tried to "open" it up as much as it may
  be helpful)

  --
  load printers = yes

     printing = cups
     printcap name = cups

  [...]

  [printers]
     comment = All Printers
     browseable = no
     path = /var/spool/samba
     printable = yes
     guest ok = yes
     read only = yes
     create mask = 0700
  #  inserted ny me
     use client driver = yes

  # Windows clients look for this share name as a source of downloadable
  # printer drivers

  # disabling or not disabling - the [print$] Section is of course not
  changig anything here

  # --
  # [print$]
  #   comment = Printer Drivers
  #   path = /var/lib/samba/printers
  #   browseable = yes
  #   read only = yes
  # #   guest ok = no
  # # changed by me
  # guest ok = yes
  # -

  [...]
  --

  Security levels is users. Password backend is tdbsam.
  Users trying to connect to the printers (2 printers - one usb and cups-pdf) 
are already connected to shared folders on the server successfully (so it is 
not a credentials problem from this side). They are also known to samba thanks 
to smbpasswd.

  On the cups side both printers are set to shared. So anything should
  just work like it does perfectly with Windows XP Clients (32Bit)
  within the same network or like unter Ubuntu 9.04 with the same
  configuration (also with vista64 Clients there).

  I've tried alot about this with no success.
  I was surprised not to find a bug report about this, because, if you google 
about "karmic printer vista" you find a lot forum questions about this - and 
they all try a lot even unrelated things to get rid of this - but the issue 
remains unsolved.
  Like here: 

  Sidenote: Also strange: After starting/restarting the whole server,
  all samba folder shares work perfectly - but not even one printer is
  showing up (at least not on the vista/win7 clients here).  Doing a
  "/etc/init.d/samba restart" on the server makes them visible. This
  can't be a sort of "late usb printer detection" issue, as cups-pdf
  shouldn't be affected by such things. I did not investigate much into
  this however.

  Regards,
  Herr Irrtum.

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

-- 
Mailing list: 

[Desktop-packages] [Bug 785701] Re: Inkscape freezes at opening

[Jadzia Dax]

Same bug on Gentoo (up-to-date version).

I had an sshfs mounted permanently on my filesystem.

The solution which worked was also to change the maxrecentdocuments
setting to 0 in ~/.config/inkscape/preferences.xml

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

Title:
  Inkscape freezes at opening

Status in Inkscape:
  Triaged
Status in inkscape package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: inkscape

  I use Ubuntu 11.04 classic. Very often Inkscape freezes at opening, even if 
empty. We have the same problem in Ubuntu 10.04. Since I hadn't noticed it up 
to recently (1 month or so) it's possible that it is due to a modification in 
another package than Inkscape, for instance a library. But Im' not an intensive 
user of Inkscape.
  Steps to reproduce the problem: choose in the general menu Applications → 
Graphics → "Inskape Vector Graphics Editor".
  What happens: Inkscape is launched but, often clicking any button has no 
effect, resizing the window doesn't resize the inside. After a while, 
Inkscape's window is greyished and, if I close it, I first get a "The window 
'New document 1 - Inkscape' is not responding." message. Relaunching Inkscape 
never solves the issue. Login out and in sometimes solves it, sometimes not.
  What is expected to happen: that Inkscape respond to clicks.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: inkscape 0.48.1-2ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Fri May 20 19:02:33 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   LANG=fr_FR.utf8
   LC_MESSAGES=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: inkscape
  UpgradeStatus: Upgraded to natty on 2011-05-01 (19 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1185489] Re: soundcloud will not play in chromium on ubuntu 13.04

[Tim]

** Changed in: chromium-browser (Ubuntu)
   Status: Invalid => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1185489

Title:
  soundcloud will not play in chromium on ubuntu 13.04

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  soundcloud will not play in chromium 13.04

  firefox 21.0 is working fine

  maybe because of the ubuntu restricted extras i installed?
   
  never a problem before

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: chromium-browser 25.0.1364.160-0ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Wed May 29 17:24:40 2013
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2013-05-10 (18 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = b''/desktop/gnome/interface/gtk_theme 
= b''

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1185489/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1603824] [NEW] compiz crashes when using static switcher

[Francesco Visin]

Public bug reported:

lsb_release -rd
Description:Ubuntu 14.04.4 LTS
Release:14.04

apt-cache policy xorg
xorg:
  Installed: 1:7.7+1ubuntu8.1
  Candidate: 1:7.7+1ubuntu8.1
  Version table:
 *** 1:7.7+1ubuntu8.1 0
500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
100 /var/lib/dpkg/status
 1:7.7+1ubuntu8 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

apt-cache policy compiz
compiz:
  Installed: 1:0.9.11.3+14.04.20160425-0ubuntu1
  Candidate: 1:0.9.11.3+14.04.20160425-0ubuntu1
  Version table:
 *** 1:0.9.11.3+14.04.20160425-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
100 /var/lib/dpkg/status
 1:0.9.11+14.04.20140409-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

X crashed taking me back to the login screen after using alt+tab to
switch window.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
Uname: Linux 4.2.0-42-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sun Jul 17 18:33:24 2016
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:054d]
InstallationDate: Installed on 2014-05-08 (801 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Dell Inc. XPS L421X
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic 
root=UUID=727c-f0ea-4ee7-afd9-626e5597fb5d ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/07/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A13
dmi.board.name: 0X86WT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A13
dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd12/07/2012:svnDellInc.:pnXPSL421X:pvrA13:rvnDellInc.:rn0X86WT:rvrA00:cvnDellInc.:ct8:cvrA13:
dmi.product.name: XPS L421X
dmi.product.version: A13
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Sun Jul 17 18:32:54 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id4158 
 vendor AUO
xserver.version: 2:1.17.2-1ubuntu9.1~trusty1

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


** Tags: amd64 apport-bug compiz-0.9 crash possible-manual-nvidia-install 
trusty ubuntu

** Summary changed:

- Xorg crash
+ compiz crashes when using static switcher

** Package changed: xorg (Ubuntu) => compiz (Ubuntu)

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

Title:
  compiz crashes when using static switcher

Status in compiz package in Ubuntu:
  New

Bug description:
  lsb_release -rd
  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04

  apt-cache policy xorg
  xorg:
Installed: 1:7.7+1ubuntu8.1
Candidate: 1:7.7+1ubuntu8.1
Version table:
   *** 1:7.7+1ubuntu8.1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:7.7+1ubuntu8 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  apt-cache policy compiz
  compiz:
Installed: 1:0.9.11.3+14.04.20160425-0ubuntu1
Candidate: 1:0.9.11.3+14.04.20160425-0ubuntu1
Version table:
   *** 1:0.9.11.3+14.04.20160425-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:0.9.11+14.04.20140409-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  X crashed taking me back to 

[Desktop-packages] [Bug 1570653] Re: 4K Monitor not detected properly

[kelargo]

Hi,  apologize for late response.  I am pretty sure I was using FGLRX
driver in 15.10. It was awhile ago.. memory is foggy.

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

Title:
  4K Monitor not detected properly

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  4K monitor is not properly detected.

  using xfce desktop "Display" utility, my monitor is detected as
  "Goldstar Company Ltd 27" with a resolution of 3840x2160 and 60.0Hz

  The actual monitor is an LG 31MU97-B Black 31" with a resolution of
  4096x2160.

  I'm pretty sure the Monitor's resolution was properly detected in 15.10 
(4096x2160).  It was called "Goldstar Company Ltd" but
  I do not recall which size was detected.  (27" or 31")

  I remember seeing a 4K youtube video in 15.10 and noting the black
  bands on each side of the display, due to the difference between 3840
  and 4096.

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: 2016-04-14 20:11:08,467 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 
270/370 OEM] [1002:6811] (prog-if 00 [VGA controller])
     Subsystem: PC Partner Limited / Sapphire Technology Curacao PRO [Radeon R7 
370 / R9 270/370 OEM] [174b:e271]
  InstallationDate: Installed on 2015-11-24 (204 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  LightdmGreeterLog:
   upstart: indicator-application main process (2191) killed by TERM signal
   Invalid MIT-MAGIC-COOKIE-1 key
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   upstart: indicator-application main process (1802) killed by TERM signal
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-lowlatency 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-22.40-lowlatency 4.4.8
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-22-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-15 (62 days ago)
  UserGroups: adm audio cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/08/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1557866] Re: connecting to samba share doesn't show all items

[Kieran Grant]

If I manually mount the share with cifs it works as expected. For now I
am going to rely on the Linux cifs support rather than userspace tools.

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

Title:
  connecting to samba share doesn't show all items

Status in gvfs package in Ubuntu:
  New

Bug description:
  When connecting to certain Shares from a Windows computer (Windows 10, but 
happened also from when it was Windows 7). I get this error:
  Sorry, could not display all the contents of “google drive on 
wrs-scanner-pc”: Invalid argument
  But when accessing other shares on this folder I can access it.
  Other Windows computers on the network can access it fine no problem.
  Sometimes I can see an item or two from the Google Drive share, other times 0 
items, and other times that error.
  It looks to me like a gvfs-mount problem.
  As far as I can tell, I am not hitting the max share limit on non-server 
Windows versions. (Which limit to a maximum of 20 connections, we don't have 
that many connecting it)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gvfs 1.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 16 14:29:12 2016
  InstallationDate: Installed on 2016-03-16 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1603578] Re: unable to enumerate USB device

[Martin Pitt]

** Package changed: udisks2 (Ubuntu) => linux (Ubuntu)

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

Title:
  unable to enumerate USB device

Status in linux package in Ubuntu:
  New

Bug description:
  ubuntu 16.04 LTS

  When I start the operating system, I get the messages:
  usb 5-1: device descriptor read/64, error -71
  usb 5-1: device not accepting address 4, error -71
  usb 5-1: device not accepting address 5, error -71
  usb usb5-port1: unable to enumerate USB device

  My external Seagate USB harddisk does not work.

  This problem started after the latest software update.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udisks2 2.1.7-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jul 16 08:30:51 2016
  HotplugNewDevices: /dev/sdd1 /dev/sdd
  HotplugNewMounts: /dev/sdd1 /media/colin/Seagate\040Expansion\040Drive 
fuseblk 
rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096
 0 0
  InstallationDate: Installed on 2016-06-11 (34 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. P55-UD3
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=8c0c09d5-9860-4049-a4db-3e06124c9601 ro quiet splash
  SourcePackage: udisks2
  Symptom: storage
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/23/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9
  dmi.board.name: P55-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd06/23/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1603815] [NEW] after updating to ubuntu 16.04 the network manager is unable to connect me to the wifi network. I can see the network, but once I introduce the password, it asks

[Miguel Fernandez]

Public bug reported:

after updating to ubuntu 16.04 the network manager is unable to connect
me to the wifi network. I can see the network, but once I introduce the
password, it asks me for the password after a few seconds and never
connects. I use different devices connected to the same wifi so it is
not a problem of writting the wrong password.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.1.93-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Jul 17 16:58:17 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-07-16 (1 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IpRoute:
 default via 192.168.2.1 dev enp2s0  proto static  metric 100 
 169.254.0.0/16 dev enp2s0  scope link  metric 1000 
 192.168.2.0/24 dev enp2s0  proto kernel  scope link  src 192.168.2.242  metric 
100
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAME UUID  TYPE 
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
 Conexión cableada 1  9e376788-1744-46de-a314-eeb07aad8c13  802-3-ethernet   
1468789026  dom 17 jul 2016 16:57:06 CDT  yes  4294966297no 
   /org/freedesktop/NetworkManager/Settings/2  yes enp2s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 BELL419 28bd64cc4-181f-449b-95a3-edc74cf2a9a6  802-11-wireless  0  
 never yes  0 no
/org/freedesktop/NetworkManager/Settings/1  no  --  -- --
nmcli-dev:
 DEVICETYPE  STATE DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
 enp2s0ethernet  connected /org/freedesktop/NetworkManager/Devices/1  
Conexión cableada 1  9e376788-1744-46de-a314-eeb07aad8c13  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 wlp3s0b1  wifi  disconnected  /org/freedesktop/NetworkManager/Devices/0  
--   ----   
  
 loloopback  unmanaged /org/freedesktop/NetworkManager/Devices/2  
--   ----
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: 
Error: Object 'nm' is unknown, try 'nmcli help'.

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


** Tags: amd64 apport-bug xenial

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

Title:
  after updating to ubuntu 16.04 the network manager is unable to
  connect me to the wifi network. I can see the network, but once I
  introduce the password, it asks me for the password after a few
  seconds and never connects.

Status in network-manager package in Ubuntu:
  New

Bug description:
  after updating to ubuntu 16.04 the network manager is unable to
  connect me to the wifi network. I can see the network, but once I
  introduce the password, it asks me for the password after a few
  seconds and never connects. I use different devices connected to the
  same wifi so it is not a problem of writting the wrong password.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jul 17 16:58:17 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-07-16 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.2.1 dev enp2s0  proto static  metric 100 
   169.254.0.0/16 dev enp2s0  scope link  metric 1000 
   192.168.2.0/24 dev enp2s0  proto kernel  scope link  src 192.168.2.242  
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL 

[Desktop-packages] [Bug 1308922] Re: There is no way to change the bluetooth system name from the standard GUI

[Norbert]

Ubuntu 12.04 LTS is affected by this bug too.

** Tags added: precise

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

Title:
  There is no way to change the bluetooth system name from the standard
  GUI

Status in Unity Control Center:
  Invalid
Status in unity-control-center package in Ubuntu:
  Triaged

Bug description:
  The built-in bluetooth adapter of my laptop (running 14.04 Trusty
  Tahr, upgraded from 13.10 Saucy Salamander) appears with the default
  name "ubuntu-0". I could not find a way to change this name through
  the GUI tools (eg. System Settings->Bluetooth Settings or System
  Settings->Details->Overview->Device name)).  This seems to be related
  to https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/989817 and
  probably caused by
  https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/644198 as my
  hostname is properly configured.

  The explanation of the source of the problem in
  https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/989817/comments/12
  seems to match the situation and so appears to be correct. The "Device
  name" in System Settings->Details->Overview is the proper hostname,
  and it is also greyed-out, so I can't make any modifications there.
  Unfortunately, short of editing manually
  /var/lib/bluetooth/[$ADDR]/config or creating /etc/machine-info I
  couldn't find a way to solve the problem. /etc/bluetooth/main.conf
  contains the default "Name = %h-%d".

  I'm not completely sure how this could be solved - either there should
  be a way to set the name through "System Settings"  if it has been
  stored already in /var/lib/bluetooth/[$ADDR]/config or ubiquity
  package should replace "ubuntu-0" with the hostname during the post-
  installation phase, after a proper hostname has been configured.

  Please, feel free to reassign this bug to one of the other packages if
  you think that it should be solved there.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140410-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 17 11:23:21 2014
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2013-12-19 (119 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to trusty on 2014-04-03 (13 days ago)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu13
   deja-dup 30.0-0ubuntu4
   gnome-control-center 1:3.6.3-0ubuntu56

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1533480] Re: banshee stops respondiing during media import

[Frann]

Also affected (Ubuntu MATE 16.04 - Banshee 2.9.0+really2.6.2-7ubuntu2)
and unchecking the Podcast plugin is not an option since I need Banshee
to import podcasts on an iPod (worked fine in Ubuntu 14.04).

Banshee freezes upon trying to:
- scan music library
- import music by another mean (right-click > import, drag & drop from window 
manager)
- check the automatic library scan plugin

Aside from that, Banshee fails to:
- subscribe to any podcast (nothing happens when submitting a podcast feed url)
- find any content on my iPod (the iPod shows up, displays correct amount of 
used/free space, but the library appears empty)

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

Title:
  banshee stops respondiing during media import

Status in banshee package in Ubuntu:
  Confirmed

Bug description:
  Trying to import media to banshee in ubuntu 16.04 freezes banshee.
  Import works fine in rhythmbox. Problem only with banshee

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.3.0-5-generic 4.3.0-5.16
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  krishnan   1972 F pulseaudio
   /dev/snd/controlC0:  krishnan   1972 F pulseaudio
  Date: Wed Jan 13 10:20:16 2016
  HibernationDevice: RESUME=UUID=1f4f89ff-6e3c-4610-8450-a25509f5b5c5
  InstallationDate: Installed on 2015-12-26 (17 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  MachineType: LENOVO INVALID
  ProcFB:
   0 radeondrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-5-generic.efi.signed 
root=UUID=0bf37a84-dc7d-4bd4-999a-f8df2baffc39 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.3.0-5-generic N/A
   linux-backports-modules-4.3.0-5-generic  N/A
   linux-firmware   1.155
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83CN12WW(V1.01)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo G505s
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G505s
  dmi.modalias: 
dmi:bvnLENOVO:bvr83CN12WW(V1.01):bd04/23/2013:svnLENOVO:pnINVALID:pvrLenovoG505s:rvnLENOVO:rnLenovoG505s:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG505s:
  dmi.product.name: INVALID
  dmi.product.version: Lenovo G505s
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1603791] Re: syndaemon "-t" option fails, in turn making touchpad disable while typing not work

[Christopher Barrington-Leigh]

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

** This bug has been marked a duplicate of bug 1351772
   "disable touchpad while typing" doesn't work

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1603791

Title:
  syndaemon "-t" option fails, in turn making  touchpad disable while
  typing not work

Status in xserver-xorg-input-synaptics package in Ubuntu:
  New

Bug description:
  I'm on Lenovo T450s, but there are reports of others having the same
  problem that touchpad disabling, which is no longer an explicit
  option, is not working. This leads to data loss and frustration when
  typing/editing, etc.

  With default settings, I find that syndaemon has been run with the
  following options:

  $ ps aux|grep synd
  meuser 2798  0.0  0.0  22504  2784 ?SJul15   0:02 syndaemon 
-i 1.0 -t -K -R

  However, this fails. My palms/ base of my thumbs, in particular, hover
  over my touchpad while typing and frequently cause unintended  motion
  AND mouse-click events, highlighting and deleting text, switching
  windows, etc.

  The diagnosis seems to be (http://askubuntu.com/questions/299868
  /disable-touchpad-while-typing-does-not-work) that the -t option is
  not working, ie mouse clicks are still allowed when it is called.

  The following two commands are a work-around for me under 16.04 on
  this hardware. They result in perfect touchpad disabling while typing:

  killall syndaemon
  syndaemon -i 1 -KRd

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-input-synaptics 1.8.2-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jul 17 12:17:26 2016
  DistUpgraded: 2016-05-24 18:07:00,267 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-02-12 (155 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20BXCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=ea2fb511-8d62-4b96-bdaa-4b3f7bf79cc6 ro noprompt quiet splash 
vt.handoff=7
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: Upgraded to xenial on 2016-05-24 (53 days ago)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Jul 15 21:21:11 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   20104 
   vendor GSM
  xserver.version: 2:1.18.3-1ubuntu2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1603791/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1603791] [NEW] syndaemon "-t" option fails, in turn making touchpad disable while typing not work

[Christopher Barrington-Leigh]

Public bug reported:

I'm on Lenovo T450s, but there are reports of others having the same
problem that touchpad disabling, which is no longer an explicit option,
is not working. This leads to data loss and frustration when
typing/editing, etc.

With default settings, I find that syndaemon has been run with the
following options:

$ ps aux|grep synd
meuser 2798  0.0  0.0  22504  2784 ?SJul15   0:02 syndaemon -i 
1.0 -t -K -R

However, this fails. My palms/ base of my thumbs, in particular, hover
over my touchpad while typing and frequently cause unintended  motion
AND mouse-click events, highlighting and deleting text, switching
windows, etc.

The diagnosis seems to be (http://askubuntu.com/questions/299868
/disable-touchpad-while-typing-does-not-work) that the -t option is not
working, ie mouse clicks are still allowed when it is called.

The following two commands are a work-around for me under 16.04 on this
hardware. They result in perfect touchpad disabling while typing:

killall syndaemon
syndaemon -i 1 -KRd

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-input-synaptics 1.8.2-1ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Jul 17 12:17:26 2016
DistUpgraded: 2016-05-24 18:07:00,267 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-02-12 (155 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: LENOVO 20BXCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=ea2fb511-8d62-4b96-bdaa-4b3f7bf79cc6 ro noprompt quiet splash 
vt.handoff=7
SourcePackage: xserver-xorg-input-synaptics
UpgradeStatus: Upgraded to xenial on 2016-05-24 (53 days ago)
dmi.bios.date: 11/06/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: JBET54WW (1.19 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BXCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20BXCTO1WW
dmi.product.version: ThinkPad T450s
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Jul 15 21:21:11 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   20104 
 vendor GSM
xserver.version: 2:1.18.3-1ubuntu2.2

** Affects: xserver-xorg-input-synaptics (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ubuntu xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1603791

Title:
  syndaemon "-t" option fails, in turn making  touchpad disable while
  typing not work

Status in xserver-xorg-input-synaptics package in Ubuntu:
  New

Bug description:
  I'm on Lenovo T450s, but there are reports of others having the same
  problem that touchpad disabling, which is no longer an explicit
  option, is not working. This leads to data loss and frustration when
  typing/editing, etc.

  With default settings, I find that syndaemon has been run with the
  following options:

  $ ps aux|grep synd
  meuser 2798  0.0  0.0  22504  2784 ?SJul15   0:02 syndaemon 
-i 1.0 -t -K -R

  However, this fails. My palms/ base of my thumbs, in particular, hover
  over my touchpad while typing and frequently cause unintended  motion
  AND mouse-click events, highlighting and deleting text, switching
  windows, etc.

  The diagnosis seems to be (http://askubuntu.com/questions/299868
  /disable-touchpad-while-typing-does-not-work) that the -t option is
  not working, ie mouse clicks are still allowed when it is called.

  The following two commands are a work-around for me under 16.04 on
  this hardware. They result in perfect touchpad disabling while typing:

  killall syndaemon
  

Re: [Desktop-packages] [Bug 1580203] Re: Android smtp-tools doublons in desktop

[LORAIN]

J'ai fait un mtp-detect si ça peut aidé !

/home/ubuntu>sudo mtp-detect
[sudo] Mot de passe de ubuntu :
libmtp version: 1.1.10

Listing raw device(s)
Device 0 (VID=0e79 and PID=5229) is UNKNOWN in libmtp v1.1.10.
Please report this VID/PID and the device model to the libmtp development
team
   Found 1 device(s):
   0e79:5229 @ bus 3, dev 50
Attempting to connect device(s)
ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session,
trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
Android device detected, assigning default bug flags
USB low-level info:
   bcdUSB: 512
   bDeviceClass: 0
   bDeviceSubClass: 0
   bDeviceProtocol: 0
   idVendor: 0e79
   idProduct: 5229
   IN endpoint maxpacket: 512 bytes
   OUT endpoint maxpacket: 512 bytes
   Raw device info:
  Bus location: 3
  Device number: 50
  Device entry info:
 Vendor: (null)
 Vendor id: 0x0e79
 Product: (null)
 Vendor id: 0x5229
 Device flags: 0x18008106
Configuration 0, interface 0, altsetting 0:
   Interface description contains the string "MTP"
   Device recognized as MTP, no further probing.
Device info:
   Manufacturer: Archos
   Model: Archos 50 Helium Plus
   Device version: 1.0
   Serial number: FERKGY7HJ7IR5SHU
   Vendor extension ID: 0x0006
   Vendor extension description: microsoft.com: 1.0; android.com: 1.0;
   Detected object size: 64 bits
   Extensions:
microsoft.com: 1.0
android.com: 1.0
Supported operations:
   1001: get device info
   1002: Open session
   1003: Close session
   1004: Get storage IDs
   1005: Get storage info
   1006: Get number of objects
   1007: Get object handles
   1008: Get object info
   1009: Get object
   100a: Get thumbnail
   100b: Delete object
   100c: Send object info
   100d: Send object
   1014: Get device property description
   1015: Get device property value
   1016: Set device property value
   1017: Reset device property value
   101b: Get partial object
   9801: Get object properties supported
   9802: Get object property description
   9803: Get object property value
   9804: Set object property value
   9810: Get object references
   95c1: Get Partial Object (64bit Offset)
   95c2: Send Partial Object
   95c3: Truncate Object
   95c4: Begin Edit Object
   95c5: End Edit Object
Events supported:
   0x4002
   0x4003
   0x4004
   0x4005
   0x4006
   0x4007
   0x400c
Device Properties Supported:
   0xd401: Synchronization Partner
   0xd402: Friendly Device Name
   0x5003: Image Size
   0x5001: Battery Level
Playable File (Object) Types and Object Properties Supported:
   3000: Undefined Type
  dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
  dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
  dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ
ONLY
  dc04: Object Size UINT64 data type READ ONLY
  dc07: Object File Name STRING data type GET/SET
  dc09: Date Modified STRING data type DATETIME FORM READ ONLY
  dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
  dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
  dc44: Name STRING data type READ ONLY
  dce0: Display Name STRING data type READ ONLY
  dc4e: Date Added STRING data type DATETIME FORM READ ONLY
   3001: Association/Directory
  dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
  dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
  dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ
ONLY
  dc04: Object Size UINT64 data type READ ONLY
  dc07: Object File Name STRING data type GET/SET
  dc09: Date Modified STRING data type DATETIME FORM READ ONLY
  dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
  dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
  dc44: Name STRING data type READ ONLY
  dce0: Display Name STRING data type READ ONLY
  dc4e: Date Added STRING data type DATETIME FORM READ ONLY
   3004: Text
  dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
  dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
  dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ
ONLY
  dc04: Object Size UINT64 data type READ ONLY
  dc07: Object File Name STRING data type GET/SET
  dc09: Date Modified STRING data type DATETIME FORM READ ONLY
  dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
  dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
  dc44: Name STRING data type READ ONLY
  dce0: Display Name STRING data type READ ONLY
  dc4e: Date Added STRING data type DATETIME FORM READ ONLY
   3005: HTML
  dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
  dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
  dc03: 

[Desktop-packages] [Bug 1598894] Re: system freezing

[Ahmad Abdulnasir Shu'aib]

Hello, thank you for the response.

I have updated the BIOS , for almost two days one freezing, so I adjust
the BIOS settings and disable secure boot, the problem is now gone.

Thenk you once again.

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

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

Title:
  system freezing

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  system freeze without pattern, it keep freezing at one point with open 
program or not.
  I'm using Ubuntu-gnome 16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   Scanning for Btrfs filesystems
   /dev/sda2: clean, 353590/6586368 files, 9437287/26316288 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Jul  4 17:14:57 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 5.0.24, 4.4.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [1025:0845]
  InstallationDate: Installed on 2016-06-19 (15 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Acer E1-510
  ProcEnviron:
   LANGUAGE=en_NG:en
   PATH=(custom, no user)
   LANG=en_NG
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed 
root=UUID=acec12ef-46b4-4043-8df0-17282313c373 ro quiet splash acpi=force 
acpi=restart halt=poweroff quiet splash acpi=force vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2014
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.name: E1-510
  dmi.board.vendor: Acer
  dmi.board.version: V2.07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd03/04/2014:svnAcer:pnE1-510:pvrV2.07:rvnAcer:rnE1-510:rvrV2.07:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.name: E1-510
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Jul  2 19:33:54 2016
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.2

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1603742] Re: Instructions for upgrading to latest GNOME version should be given in documentation

[Jeremy Bicha]

** Package changed: yelp (Ubuntu) => gnome-user-docs (Ubuntu)

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

Title:
  Instructions for upgrading to latest GNOME version should be given in
  documentation

Status in Ubuntu GNOME:
  New
Status in gnome-user-docs package in Ubuntu:
  New

Bug description:
  I believe that somewhere in the GNOME documentation (Help/Yelp) that
  is pre-installed there should be instructions to upgrade to the latest
  GNOME version using the gnome3 and gnome3-staging PPAs, even if it's
  an "Advanced User" section or something with a warning, I believe that
  it should be easier to find out about it through the official built-in
  means.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1598770] Re: Unity in low-graphics mode has animations and unneeded redraws

[Treviño]

What profile are you running?
 echo $COMPIZ_CONFIG_PROFILE

Is lowgfx option enabled in your CCSM settings?
  gsettings set 
org.compiz.unityshell:/org/compiz/profiles/unity/plugins/unityshell/ 
low-graphics-mode false
  gsettings set 
org.compiz.unityshell:/org/compiz/profiles/unity/plugins/unityshell/ 
dash-blur-experimental 2

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

Title:
  Unity in low-graphics mode has animations and unneeded redraws

Status in compiz package in Ubuntu:
  Fix Released
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Fix Released
Status in compiz source package in Xenial:
  Fix Committed
Status in nux source package in Xenial:
  Fix Committed
Status in unity source package in Xenial:
  Fix Committed
Status in unity-control-center source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  When unity is in Low graphics mode (because of software rendering)
  there are still window animations and fade effects which we should get
  rid of.

  
  [Test case]

  This should apply naturally to a (virtual-)machine with no hardware
  acceleration or There are multiple ways to force low-gfx mode:

  1) Add an upstart job such as:

  cat << EOF > ~/.config/upstart/lowgfx.conf
  start on starting unity7

  pre-start script
#initctl set-env --global UNITY_LOW_GFX_MODE=1
initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1
  end script
  EOF 

  
  2) Run unity with:
 COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx

  On login unity should use opaque views (dash, switcher, launcher,
  shortcut-dialogs) with no fading and reduced effects. Windows should
  also use smaller shadows.

  
  [Regression potential]

  Some settings from unity-control-center couldn't be applied to normal
  profile. Low graphics mode might be used as normal one.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1308800] Re: Unity doesn't respawn all the times on crashes

[Treviño]

** Changed in: unity (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: unity (Ubuntu Xenial)
   Status: In Progress => Fix Released

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

Title:
  Unity doesn't respawn all the times on crashes

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  In Progress
Status in gnome-session package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in gnome-session source package in Xenial:
  Fix Released
Status in unity source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Killing compiz repeatedly doesn't make unity to reload all the times.

  This is caused by the fact that due to a regression unity7 is not
  loaded anymore by upstart (but by gnome-session) and thus it seems
  that sometimes it doesn't properly gets restarted.

  This is also a security issue, because if the session was locked, and
  unity is not reloaded the session won't be locked anymore.

  [Test Case]
  From a terminal run killall -9 compiz multiple times, it should always 
reload, but it fails after a couple of times.

  [Regression Potential]
  The fix is about always making unity to be launched by upstart.
  Regression potential is low, since upstart is now used by most ubuntu desktop 
applications, and it ensures compiz will run properly anyway.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 303681] Re: print preview broken in non gnome environments (evince missing)

[Bug Watch Updater]

** Changed in: inkscape (Debian)
   Status: Confirmed => Fix Released

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

Title:
  print preview broken in non gnome environments (evince missing)

Status in Inkscape:
  Invalid
Status in inkscape package in Ubuntu:
  Invalid
Status in inkscape package in Debian:
  Fix Released
Status in inkscape package in Mandriva:
  Unknown

Bug description:
  Inkscape 0.46 Linux assumes that evince is installed on the machine
  that it is running on. This causes error messages when print preview
  is attempted: "Failed to execute child process "evince" (No such file
  or directory)".

  This is a simple problem; perhaps evince could be listed as a
  dependency, or alternatively a more helpful error message could be
  displayed which would explaining the problem (many users will not know
  what "evince" is or means). It could say something like 'an external
  program is required to use the print preview function, please install
  evince'.

  Ideally inkscape would be able to use KDE components to display print
  preview, as well as Gnome ones. I don't know how easy/possible this
  would be to implement.

  This bug has been written up elsewhere, including bug #238609.
  However, it is not very well described there, and I think it is
  sufficiently important and easy to remedy that it merited a new bug
  submission (print preview is a very popular function on any graphics
  app).

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1603610] Re: Snaps have no screenshots

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Snaps have no screenshots

Status in Snappy:
  New
Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Snaps have no screenshots

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1603610] Re: Snaps have no screenshots

[Emanuele Antonio Faraone]

+1

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

Title:
  Snaps have no screenshots

Status in Snappy:
  New
Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Snaps have no screenshots

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1577738] Re: pm-utils does not write pm-suspend.log file

[HHS]

Ubuntu 16.06 LTS with todays updates from stable repositories.

Same problem here, but when I use "pm-suspend" all working fine.
Logfiles are created and hook scripts working fine.

Only the automatic unity mode with settings over the gnome-system-tools GUI 
system settings -> "Leistung" set with suspend after xx minutes are not working.
The system go in suspend mode without creating logfiles and without execute the 
/etc/pm/sleep.d/scripts.

They use other functions in the background?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1577738

Title:
  pm-utils does not write pm-suspend.log file

Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I hope I'm filing this information the proper way and I thank you for
  reading it.

  1) Kubuntu 16.04
  2) pm-utils 1.4.1-16

  3) As far as the info I could find, the package "pm-utils" is supposed
  to write log files in /var/log, such as "pm-suspend.log". These log
  files, as you know, help troubleshoot hibernate/resume issues.

  I happen to have one issue with hooks that don't run on resume, that
  do run prior to hibernate when I run them manually and don't after
  resume when I run them the same manual way. (different issue than this
  bug report)

  4) Therefore I need to scan through pm-suspeng.log file, but the file
  is not created on my machine, anywhere on the HDD.

  I have added my user to the "systemd-journal", "root" and "sudo"
  groups, in case that could help, I still don't see the log file.

  With previous Kubuntu versions (13.10 and others before, didn't try
  between 13.10 and 16.04), this log file was created right away.

  After searching and trying things out, I'm leaning towards the
  possibility of a bug, which is the reason why I am posting here.

  I do not know what other information to provide.

  
  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1577738/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1603742] [NEW] Instructions for upgrading to latest GNOME version should be given in documentation

[Nikita Yerenkov-Scott]

Public bug reported:

I believe that somewhere in the GNOME documentation (Help/Yelp) that is
pre-installed there should be instructions to upgrade to the latest
GNOME version using the gnome3 and gnome3-staging PPAs, even if it's an
"Advanced User" section or something with a warning, I believe that it
should be easier to find out about it through the official built-in
means.

** Affects: ubuntu-gnome
 Importance: Undecided
 Status: New

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


** Tags: gnome3 gnome3-staging

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

** Tags added: gnome3 gnome3-staging

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

Title:
  Instructions for upgrading to latest GNOME version should be given in
  documentation

Status in Ubuntu GNOME:
  New
Status in yelp package in Ubuntu:
  New

Bug description:
  I believe that somewhere in the GNOME documentation (Help/Yelp) that
  is pre-installed there should be instructions to upgrade to the latest
  GNOME version using the gnome3 and gnome3-staging PPAs, even if it's
  an "Advanced User" section or something with a warning, I believe that
  it should be easier to find out about it through the official built-in
  means.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1603719] Re: NFS client: access problems after updating to kernel 4.4.0-31-generic

[Christopher M. Penalver]

Jurgen Schellaert, thank you for reporting this and helping to make Ubuntu 
better. Please execute the following command only once, as it will 
automatically gather debugging information, in a terminal:
apport-collect 1603719

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Package changed: libreoffice (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

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

Title:
  NFS client: access problems after updating to kernel 4.4.0-31-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am denied access to the subfilesystems exported by my nfs server
  (the top level filesystem itself is unaffected).

  The client is reporting that I do not have the necessary permissions.
  However, all was fine until the day before yesterday.

  When I revert my client to 4.4.0-28, everything is in working order
  again. I assume the permission problem is really a bug in kernel
  4.4.0-31.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1598316] Re: gtk2-engines-murrine desktop text shadow problem

[Jason]

I don't think it's the numix theme either as I was using the Arc theme. Here's 
a post showing the screen shot of the issue I was having until I downgraded the 
package:
http://askubuntu.com/questions/798778/desktop-icon-foreground-text-is-way-offset

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk2-engines-murrine in Ubuntu.
https://bugs.launchpad.net/bugs/1598316

Title:
  gtk2-engines-murrine desktop text shadow problem

Status in Numix GTK theme:
  Fix Released
Status in gtk2-engines-murrine package in Ubuntu:
  Triaged
Status in shimmer-themes package in Ubuntu:
  Triaged

Bug description:
  Upgraded my xubuntu 16.04 system on 01 Jul 2016.  The apt update
  included an upgrade to gtk2-engines-murrine.  However, after the
  upgrade and boot, the any desktop text, folder, launcher, etc. had a
  problem with the text and shadow being quite far apart.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp