[Desktop-packages] [Bug 724429] Re: If folder path to .cbz file contains [, file will fail to open reporting all pages are empty

[Sebastien Bacher]

The issue has been fixed in
https://git.gnome.org/browse/evince/commit/?id=c648cb2aa38c5004fc091d0067d63aa3beee748f

** Changed in: evince (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  If folder path to .cbz file contains [, file will fail to open
  reporting all pages are empty

Status in Evince:
  Fix Released
Status in evince package in Ubuntu:
  Fix Committed

Bug description:
  Binary package hint: evince

  If the folder path to a comic book archive file (.cbz at least)
  contains an open square-bracket ([), Document Viewer will not be able
  to open the file claiming the document only contains empty pages.

  This is not the case if the file name contains the opening bracket.

  The same file as zip (cbz and zip are the same files just using
  different extensions) opens as expected (Archive Manager).

  Image files (.jpg for example) open as expected in the same folder
  path (Eye of Gnome).

  Portable Document (.pdf) files open as expected in the same folder
  path (Document Viewer).

  Can anyone confirm this behavior?

  Can anyone direct me to the best place to file a bug report?

  Thanks.

  (I tested this on 9.10 (works properly) and 10.04 and 10.10 (broken as
  described above).)

  http://ubuntuforums.org/showthread.php?t=1693877

  This link includes bug confirmation and some additional information.
  You may contact me for additional information either through this
  forum page or via e-mail.

  
  James

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: evince 2.30.3-0ubuntu1.2
  ProcVersionSignature: Ubuntu 2.6.32-28.55-generic-pae 2.6.32.27+drm33.12
  Uname: Linux 2.6.32-28-generic-pae i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Thu Feb 24 09:01:25 2011
  ExecutablePath: /usr/bin/evince
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  KernLog:
   Feb 23 10:03:18 heckle kernel: [0.008027] Security Framework initialized
   Feb 23 10:03:18 heckle kernel: [0.008053] AppArmor: AppArmor initialized
   Feb 23 10:03:18 heckle kernel: [0.408002] AppArmor: AppArmor Filesystem 
Enabled
   Feb 23 10:03:18 heckle kernel: [0.470215] type=2000 
audit(1298484182.467:1): initialized
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: evince

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/724429/+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 871133] Re: Volume Step not changeable in Unity and GNOME desktops

[Tim]

** Also affects: ubuntu-gnome
   Importance: Undecided
   Status: New

** Changed in: ubuntu-gnome
Milestone: None => xenial

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

Title:
  Volume Step not changeable in Unity and GNOME desktops

Status in gnome-settings-daemon:
  Confirmed
Status in Ubuntu GNOME:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Changing the volume step in gconf-editor does not do anything when adjusting 
the volume on a hardware dial.
  --- 
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  DistroRelease: Ubuntu 11.10
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
  Package: gnome-settings-daemon 3.2.0-0ubuntu5
  PackageArchitecture: i386
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Tags:  oneiric running-unity
  Uname: Linux 3.0.0-12-generic i686
  UpgradeStatus: Upgraded to oneiric on 2011-10-08 (3 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/871133/+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 871133] Re: Volume Step not changeable in Unity and GNOME desktops

[Tim]

HEXcube, thanks for taking the time to attaching the patch, however for
a fix to be backported into the stable releases it must land in the
current development release (Xenial) first. However that said, I mostly
agree with upstream here and would not want to see it incorporated into
ubuntu except as a last resort, it really is just a hidden magic button
that glosses over potentially real bugs.

First I see reports (mostly in the upstream report) that people are
getting 10-30% steps in volume instead of the defined 6%. That is
clearly a bug, and should be fixed first since it is really unclear how
much that is contributing to the reported issues.

Second using a linear scale for a volume slider is really not ideal,
pulse audio uses a cubic scale to define volume, but from a quick glance
at the source code it may be that g-s-d is plugging linear values into
these structures. IF that is indeed true, then it is also going to mess
up the actual steps, of the actual audio volume.

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

Title:
  Volume Step not changeable in Unity and GNOME desktops

Status in gnome-settings-daemon:
  Confirmed
Status in Ubuntu GNOME:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Changing the volume step in gconf-editor does not do anything when adjusting 
the volume on a hardware dial.
  --- 
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  DistroRelease: Ubuntu 11.10
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
  Package: gnome-settings-daemon 3.2.0-0ubuntu5
  PackageArchitecture: i386
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Tags:  oneiric running-unity
  Uname: Linux 3.0.0-12-generic i686
  UpgradeStatus: Upgraded to oneiric on 2011-10-08 (3 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/871133/+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 418242] Re: Incorrect call to output plugins (with persistent error message) on copy

[Lepe]

Running inkscape 0.91 in Xfce4 and Netbeans.

I wouldn't suggest to just run the script from the comment #37. What
that script does is to comment some "fixed" range of lines in 3 scripts:
gimp_xcf.py, jessyInk_export.py and uniconv_output.py (located at:
/usr/share/inkscape/extensions/). However it seems those files may be
different depending on your version (as in mine, those lines didn't
match correctly and produces broken code). I strongly suggest to backup
your files if you want to give that script a try.

If you want to do the dirty job by yourself, this is what I did:
Comment (using "#" at the beginning of the line) this line at 
"uniconv_output.py": 

# sys.stderr.write(msg + "\n")

Comment these 2 lines at "jessyInk_export.py":

# if len(exportNodes) < 1:   
 # sys.stderr.write("No layers found.")

Comment this line at "gimp_xcf.py":

# inkex.errormsg(_('This extension requires at least one non empty
layer.'))

Give it a try. In my case that wasn't enough (as I have additional
plugins), but if you see an error message, copy that message and do a "
grep '' * "  in the /usr/share/inkscape/extensions/
directory. As before, comment any "inkex.errormsg" that may come up. For
example, I had to comment a line in "plotter.py" and "hpgl_output.py"
scripts (same line):

# inkex.errormsg(_("No paths where found. Please convert all objects you
want to plot into paths."))

I hope that helps. I wish there were a "Disable warnings" somewhere in
the options so we didn't have to do this kind of hacks.

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

Title:
  Incorrect call to output plugins (with persistent error message) on
  copy

Status in Inkscape:
  Triaged
Status in inkscape package in Ubuntu:
  Triaged
Status in inkscape package in Arch Linux:
  New
Status in inkscape package in Debian:
  Confirmed
Status in Gentoo Linux:
  Unknown

Bug description:
  UPDATE: After further investigation it turned out to be a problem related to 
the copy operation, in combination with a totally unrelated running Java 
program (FreeRapid).
  Reading some followups and other bug reports, it seems to be caused by the 
new clipboard management system (introduced as a fix for the bug #170185), as 
reported in bug #421597

  So far these applications are known to randomly trigger an input/output 
extension (on linux):
  - FreeRapid Downloader
  - jDownloader
  - xfce4-clipman-plugin 1.1.3
  - Netbeans
  - xfce4-settings-helper (Xfce 4.8)
  - Team Viewer (teamviewerd 10.0.36)

  -

  The original report was this:
  I'm getting this error when I try to edit a text object created previously 
with a font that's not available in this system.
  It looks like Inkscape has problems to resolve the font substitution and 
displays the error message in a popup window that keeps appearing again and 
again, leaving no other remedy than closing inkscape and reopening it.

  The error message is attached.

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

Re: [Desktop-packages] [Bug 1511330] Re: PPTP connection does not establish due to error: "Connection activation failed: the VPN service returned invalid configuration."

[R4kk00n]

Well, if I could work without static routes, I wouldn't see an issue. And
removing and reentering them doesn't help: I can connect with an empty
list, but it refuses to when I add a route.
I have "use this connection only for resources on its own network" checked
On 1 Dec 2015 05:45, "berend"  wrote:

> And it seems I either had a wrong static route (most likely) or re-
> entering it fixed it.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1511330
>
> Title:
>   PPTP connection does not establish due to error: "Connection
>   activation failed: the VPN service returned invalid configuration."
>
> Status in network-manager-pptp package in Ubuntu:
>   Confirmed
>
> Bug description:
>   The PPTP connection in question used to work on Vivid, now it does not
>   connect after an upgrade to Wily.
>
>   That error description in the title comes from nmcli; it looks
>   somewhat different in the notification popup
>
>   The relevant piece of syslog is in the attached syslog-snippet.txt
>
>   I'd say that the IP config as stated in the log looks valid to me
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 15.10
>   Package: network-manager-pptp 0.9.10.0-1ubuntu1
>   ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
>   Uname: Linux 4.2.0-16-generic x86_64
>   ApportVersion: 2.19.1-0ubuntu4
>   Architecture: amd64
>   CurrentDesktop: Unity
>   Date: Thu Oct 29 14:07:01 2015
>   InstallationDate: Installed on 2015-08-20 (69 days ago)
>   InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
>   SourcePackage: network-manager-pptp
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/1511330/+subscriptions
>

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

Title:
  PPTP connection does not establish due to error: "Connection
  activation failed: the VPN service returned invalid configuration."

Status in network-manager-pptp package in Ubuntu:
  Confirmed

Bug description:
  The PPTP connection in question used to work on Vivid, now it does not
  connect after an upgrade to Wily.

  That error description in the title comes from nmcli; it looks
  somewhat different in the notification popup

  The relevant piece of syslog is in the attached syslog-snippet.txt

  I'd say that the IP config as stated in the log looks valid to me

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: network-manager-pptp 0.9.10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Oct 29 14:07:01 2015
  InstallationDate: Installed on 2015-08-20 (69 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: network-manager-pptp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/1511330/+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 1501314] Re: xorg

[Launchpad Bug Tracker]

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

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

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

Title:
  xorg

Status in xorg package in Ubuntu:
  Expired

Bug description:
  xorg

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3.15
  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
  Date: Wed Sep 30 20:11:47 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Subsystem: ASUSTeK Computer Inc. Device [1043:844d]
   Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / 
R9 280] [1002:679a] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e210]
  InstallationDate: Installed on 2015-09-27 (2 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic 
root=UUID=562842d1-3170-43e9-a78f-a604210d831d ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0405
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-F
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0405:bd12/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH61M-F:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~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: Wed Sep 30 20:02:45 2015
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.1-0ubuntu3.1~trusty1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1501314/+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 1500312] Re: Graphics Driver issues

[Launchpad Bug Tracker]

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

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

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

Title:
  Graphics Driver issues

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Just tried this command to resolve graphics driver issues

  sudo apt-get install xserver-xorg-video-intel

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.15
  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: Mon Sep 28 10:58:50 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Device [8086:2049]
  InstallationDate: Installed on 2015-09-24 (3 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic.efi.signed 
root=UUID=62d3c93a-a1bd-4918-9bbc-748f1ce78785 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: MCH8710H.86A.0156.2014.0430.0904
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH87MC
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG74242-403
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrMCH8710H.86A.0156.2014.0430.0904:bd04/30/2014:svn:pn:pvr:rvnIntelCorporation:rnDH87MC:rvrAAG74242-403:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~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: Mon Sep 28 10:22:36 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.17.1-0ubuntu3~trusty1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1500312/+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 1501061] Re: nvidia driver

[Launchpad Bug Tracker]

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

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

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

Title:
  nvidia driver

Status in xorg package in Ubuntu:
  Expired

Bug description:
  still tears the screen when the computer has been on for a couple of
  hours, the pc cooling is fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26
  Uname: Linux 3.13.0-65-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  346.96  Sun Aug 23 21:32:53 PDT 
2015
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04)
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: i386
  Date: Tue Sep 29 21:46:54 2015
  DistUpgraded: 2015-09-19 23:28:07,799 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-63-generic, i686: installed
   bbswitch, 0.7, 3.13.0-65-generic, i686: installed
   bbswitch, 0.7, 3.2.0-90-generic-pae, i686: installed
   nvidia-346, 346.96, 3.13.0-63-generic, i686: installed
   nvidia-346, 346.96, 3.13.0-65-generic, i686: installed
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 630] [10de:0f00] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8429]
  InstallationDate: Installed on 2015-09-19 (10 days ago)
  InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1)
  MachineType: FOXCONN RS880M06-8KRS3HX
  ProcEnviron:
   LANGUAGE=en_GB
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic 
root=UUID=8d17b1db-12bf-41c7-b494-cdd864d3d816 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2015-09-19 (9 days ago)
  dmi.bios.date: 05/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.name: A88GMX
  dmi.board.vendor: FOXCONN
  dmi.board.version: FAB 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: FOXCONN
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/20/2010:svnFOXCONN:pnRS880M06-8KRS3HX:pvrFAB1.0:rvnFOXCONN:rnA88GMX:rvrFAB1.0:cvnFOXCONN:ct3:cvr:
  dmi.product.name: RS880M06-8KRS3HX
  dmi.product.version: FAB 1.0
  dmi.sys.vendor: FOXCONN
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Sep 29 21:13:07 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDaKai 2.4G RXKEYBOARD, id 8
   inputDaKai 2.4G RXKEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1501061/+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 1501849] Re: degrag?

[Launchpad Bug Tracker]

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

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

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

Title:
  degrag?

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Computer is so slow. need defragment?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-64.104-generic 3.13.11-ckt26
  Uname: Linux 3.13.0-64-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.16
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Oct  1 13:30:42 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV370/M22 [Mobility Radeon X300] 
[1002:5460] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:0944]
  InstallationDate: Installed on 2015-08-22 (40 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 002: ID 03f0:011d Hewlett-Packard Bluetooth 1.2 Interface 
[Broadcom BCM2035]
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Hewlett-Packard HP Compaq nc6230 (PU986AA#ABA)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-64-generic 
root=UUID=32d9b3bd-0ada-4280-addf-afb1d5710ea6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/27/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68DTA Ver. F.13
  dmi.board.name: 0944
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 40.22
  dmi.chassis.asset.tag: CNU52338VD
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68DTAVer.F.13:bd02/27/2007:svnHewlett-Packard:pnHPCompaqnc6230(PU986AA#ABA):pvrF.13:rvnHewlett-Packard:rn0944:rvrKBCVersion40.22:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq nc6230 (PU986AA#ABA)
  dmi.product.version: F.13
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Sep 28 22:30:28 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2.7
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1501849/+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 1502003] Re: Computer locks

[Launchpad Bug Tracker]

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

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

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

Title:
  Computer locks

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Computer locks

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-65.105-generic 3.13.11-ckt26
  Uname: Linux 3.13.0-65-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Oct  2 07:57:20 2015
  DistUpgraded: 2014-08-22 14:58:31,155 WARNING no activity on terminal for 300 
seconds (Valmistaudutaan tekemään asetukset: python2.7)
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-52-generic, x86_64: installed
   bbswitch, 0.7, 3.13.0-53-generic, x86_64: installed
   bbswitch, 0.7, 3.13.0-55-generic, x86_64: installed
   bbswitch, 0.7, 3.13.0-63-generic, x86_64: installed
   bbswitch, 0.7, 3.13.0-65-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation G86M [Quadro NVS 135M] [10de:042b] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell Device [1028:01f9]
  InstallationDate: Installed on 2014-04-12 (537 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MachineType: Dell Inc. Latitude D630
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic 
root=UUID=54c7b715-25be-443b-a9b2-d6f48c16d024 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-08-22 (405 days ago)
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0WM416
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0WM416:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D630
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1502003/+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 1501458] Re: issues with intel graphics card

[Launchpad Bug Tracker]

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

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

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

Title:
  issues with intel graphics card

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Tried a few drivers for the graphics - I cant seem to get it to work.
  Causing very low fps & good specs on computer.   i'm lost

  Intel® Core™ i7-4700MQ CPU @ 2.40GHz × 8
  Intel® Haswell Mobile = graphics? 
  15.6 GiB
  ubuntu 14.04
  64 bit

  When I run lspci | grep VGA:
  00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor 
Integrated Graphics Controller (rev 06)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-50.66~14.04.1-generic 3.16.7-ckt16
  Uname: Linux 3.16.0-50-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.15
  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: Wed Sep 30 14:38:55 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1965]
  InstallationDate: Installed on 2015-06-16 (106 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-50-generic.efi.signed 
root=UUID=de939647-8d10-41e7-8b39-3526b86290d6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf: Section "Device" Identifier "Card0" Driver "intel" Option 
"AccelMethod" "sna" EndSection
  dmi.bios.date: 05/05/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.62
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1965
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 93.51
  dmi.chassis.asset.tag: 5CG4513JHP
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.62:bd05/05/2014:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr097E11405E162:rvnHewlett-Packard:rn1965:rvrKBCVersion93.51:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY 17 Notebook PC
  dmi.product.version: 097E11405E162
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.65+git1509290630.4031dc~gd~t
  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: Tue Sep 29 15:48:25 2015
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 882 
   vendor LGD
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1501458/+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 1502119] Re: nvidia card

[Launchpad Bug Tracker]

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

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

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

Title:
  nvidia card

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Nvidia driver nv44 gforce 6200 turbocache (304)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.128  Wed Aug 26 10:38:05 
PDT 2015
   GCC version:  gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Oct  2 09:02:38 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus: nvidia-304, 304.128, 3.19.0-30-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation NV44 [GeForce 6200 TurboCache] [10de:0161] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Device [1682:2237]
  InstallationDate: Installed on 2015-10-01 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Gigabyte Technology Co., Ltd. GA-VM900M
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic 
root=UUID=29a4fccc-ea49-450b-942a-d49e3618e8da ro quiet splash
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] Arquivo ou diretório não encontrado: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F7a
  dmi.board.name: VM900M
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7a:bd08/16/2007:svnGigabyteTechnologyCo.,Ltd.:pnGA-VM900M:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnVM900M:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-VM900M
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Fri Oct  2 08:43:31 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.17.1-0ubuntu3.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1502119/+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 1500382] Re: Screen blanking out when using an external 4k monitor with the internal screen turned off in display settings.

[Launchpad Bug Tracker]

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

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

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

Title:
  Screen blanking out when using an external 4k monitor with the
  internal screen turned off in display settings.

Status in xorg package in Ubuntu:
  Expired

Bug description:
  [Summary]
  Screen blanking out when using an external 4k monitor with the internal 
screen turned off in display settings.

  [Reproduce Steps]
  1. Connect an external 4K monitor
  2. Turn off the internal screen in the display settings

  [Results]
  Expected: Normal output
  Actual: Blank Screen

  [Additional Information]
  Product Name: Ubuntu 14.04.3 LTS on Dell XPS 13 9343
  BIOS Version: BIOS A05 07/14/2015
  Kernel Version: 3.13.0-63-generic
  CPU: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz
  GPU: Intel Corporation Broadwell-U Integrated Graphics (rev 09)
  Monitor: Dell monitor, model P2715Q

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1500382/+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 1516218] Re: xmir fails to start

[Daniel van Vugt]

Hi,

If you're connecting any Mir client (which Xmir is) to Unity8 (the Mir server) 
then Unity8 requires the client to jump through an extra hoop:
   Xmir :0 --desktop_file_hint=unity8

This is a peculiarity of Unity8. Sorry about that.

** Tags added: xmir

** Changed in: xorg-server (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  xmir fails to start

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  When trying to start Xmir on my Ubuntu Phone (Aquaris BQ E5), I get
  the following error:

  phablet@ubuntu-phablet:~$ Xmir
  ARM architecture: Defaulting to software mode because glamor is not stable
  (EE) 
  Fatal server error:
  (EE) Failed to connect to Mir: Failed to send message to server: Broken pipe
  (EE)

  This happens no matter whether I do it from the terminal app or via a
  remote ssh session.

  
  Just trying to start an X application (hoping that Xmir would be started 
transparently) fails as well:

  phablet@ubuntu-phablet:~$ firefox
  Error: cannot open display: :0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1516218/+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 1507033] Re: lightdm.conf boolean values false if have trailing whitespace

[Mathew Hodson]

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

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

Title:
  lightdm.conf boolean values false if have trailing whitespace

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.16 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Released

Bug description:
  [Impact]
  Adding trailing whitespace to a boolean true value in LightDM configuration 
has it read as false.

  [Test Case]
  1. Set a boolean configuration value in lightdm.conf to true_ (_ is a space 
character)
  2. Run LightDM

  Expected result:
  The configured value is interpreted as true.

  Observed result:
  The configured value is interpreted as false.

  [Regression potential]
  Low. We just strip trailing whitespace when checking for the value "true".

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1507033/+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 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

[Mathew Hodson]

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

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

Title:
  xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.16 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Released

Bug description:
  [Impact]
  xserver-allow-tcp=true option no longer works with X.org 1.17.

  [Test Case]
  1. Edit /etc/lightdm/lightdm.conf and set [SeatDefaults] 
xserver-allow-tcp=true
  2. Start LightDM
  3. Attempt to connect to the X server using TCP

  Expected result:
  Able to connect

  Observed result:
  Unable to connect

  [Regression potential]
  Low. X.org changed their default behaviour from listen by default to listen 
if "-listen tcp" is passed as a command line flag. This is just the equivalent 
change in LightDM. Since this is a new flag to X.org if a user was to use 
another X server there is a risk it would not understand that flag. However it 
seems unlikely since X.org is the only actively developed X server.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1449282/+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 1513910] Re: libertine config of gimp for single window mode

[Daniel van Vugt]

"Xmir root window" means you need to run a window manager yourself. And
I can't see any titlebar etc from a window manager in the screenshot...?

The screenshot looks correct. Just user error. Or Libertine/whatever
failed to start a WM.

** Changed in: xorg-server (Ubuntu)
   Status: New => Invalid

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

Title:
  libertine config of gimp for single window mode

Status in canonical-pocket-desktop:
  New
Status in libertine package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  single window mode for gimp still not looking quite right

  see picture attached - we were using the very latest in the libertine
  team ppa version of xmir and libertine tools

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1513910/+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 724429] Re: If folder path to .cbz file contains [, file will fail to open reporting all pages are empty

[Bug Watch Updater]

** Changed in: evince
   Status: Confirmed => Fix Released

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

Title:
  If folder path to .cbz file contains [, file will fail to open
  reporting all pages are empty

Status in Evince:
  Fix Released
Status in evince package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  If the folder path to a comic book archive file (.cbz at least)
  contains an open square-bracket ([), Document Viewer will not be able
  to open the file claiming the document only contains empty pages.

  This is not the case if the file name contains the opening bracket.

  The same file as zip (cbz and zip are the same files just using
  different extensions) opens as expected (Archive Manager).

  Image files (.jpg for example) open as expected in the same folder
  path (Eye of Gnome).

  Portable Document (.pdf) files open as expected in the same folder
  path (Document Viewer).

  Can anyone confirm this behavior?

  Can anyone direct me to the best place to file a bug report?

  Thanks.

  (I tested this on 9.10 (works properly) and 10.04 and 10.10 (broken as
  described above).)

  http://ubuntuforums.org/showthread.php?t=1693877

  This link includes bug confirmation and some additional information.
  You may contact me for additional information either through this
  forum page or via e-mail.

  
  James

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: evince 2.30.3-0ubuntu1.2
  ProcVersionSignature: Ubuntu 2.6.32-28.55-generic-pae 2.6.32.27+drm33.12
  Uname: Linux 2.6.32-28-generic-pae i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Thu Feb 24 09:01:25 2011
  ExecutablePath: /usr/bin/evince
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  KernLog:
   Feb 23 10:03:18 heckle kernel: [0.008027] Security Framework initialized
   Feb 23 10:03:18 heckle kernel: [0.008053] AppArmor: AppArmor initialized
   Feb 23 10:03:18 heckle kernel: [0.408002] AppArmor: AppArmor Filesystem 
Enabled
   Feb 23 10:03:18 heckle kernel: [0.470215] type=2000 
audit(1298484182.467:1): initialized
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: evince

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/724429/+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 871133] Re: Volume Step not changeable in Unity and GNOME desktops

[Bug Watch Updater]

** Changed in: gnome-settings-daemon
   Status: Unknown => Confirmed

** Changed in: gnome-settings-daemon
   Importance: Unknown => Medium

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

Title:
  Volume Step not changeable in Unity and GNOME desktops

Status in gnome-settings-daemon:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Changing the volume step in gconf-editor does not do anything when adjusting 
the volume on a hardware dial.
  --- 
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  DistroRelease: Ubuntu 11.10
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
  Package: gnome-settings-daemon 3.2.0-0ubuntu5
  PackageArchitecture: i386
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Tags:  oneiric running-unity
  Uname: Linux 3.0.0-12-generic i686
  UpgradeStatus: Upgraded to oneiric on 2011-10-08 (3 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/871133/+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 1509005] Re: [regression] mir-client-platform-mesa-dev pkg-config file dropped

[Daniel van Vugt]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [regression] mir-client-platform-mesa-dev pkg-config file dropped

Status in Mir:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in mesa source package in Wily:
  Confirmed
Status in mir source package in Wily:
  Confirmed
Status in xorg-server source package in Wily:
  Fix Released

Bug description:
  the mir-client-platform-mesa-dev pkg-config file was dropped in wily,
  leading to build errors for such optional packages like mesa and xorg-
  server.

  Even if you have a feature freeze exception, you shouldn't break
  existing API's after feature freeze.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1509005/+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 1522212] Re: kernel panic involving threading

[beauxq]

Since I was going back and forth between nouveau and the proprietary
nvidia driver for testing this bug, I ended up creating this bug report
while the proprietary nvidia driver was loaded. I don't know if that
messes up the information that you would want to collect.

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

Title:
  kernel panic involving threading

Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  my system:
  intel core i5
  nvidia 310m
  lubuntu 15.10
  sfml libsfml-dev 2.3.2+dfsg-1
  g++ 4:5.2.1-3ubuntu1

  I'm running my own cross-platform multimedia application.
  The program works as expected on this same ubuntu system with the proprietary 
nvidia driver and works as expected in Windows.
  This is how I conclude that the bug is in nouveau.

  This program uses sfml and c++ std::thread
  I send a thread to load some textures (into video memory), main thread shows 
a simple loading screen.
  artifacts on screen, then kernel panic

  I can reproduce the crash 100% on this system. I don't have another system to 
test it with.
  I have been unable to reproduce the problem with a smaller amount of code, I 
can zip up the whole project for you if you want.

  The problem does not occur if I just call the same functions in the
  main thread, only when I create a separate thread to load the
  textures.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Wed Dec  2 18:41:45 2015
  InstallationDate: Installed on 2015-10-18 (45 days ago)
  InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1522212/+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 1445595] Re: Empty trash from Launcher results in Nautilus window opening

[Rasmus Underbjerg Pinnerup]

>This bug was fixed in the package nautilus - 1:3.18.2-1ubuntu1

Sounds good, but I wonder when this reaches Ubuntu then. Mine is
currently at 1:3.14.2-0ubuntu13.

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

Title:
  Empty trash from Launcher results in Nautilus window opening

Status in One Hundred Papercuts:
  Triaged
Status in Unity:
  Confirmed
Status in nautilus package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Triaged
Status in nautilus source package in Xenial:
  Fix Released
Status in unity source package in Xenial:
  Triaged

Bug description:
  Test case:
  - Add a file to trash if none already
  - Right click on Unity launcher trash icon > click on Empty Trash option
  - Nautilus open a window @ home folder

  When selecting 'Empty trash' from the launcher, I get a dialog to
  confirm the deletion and a Nautilus window. When emptying trash from
  Nautilus window, I get only a confirmation dialog as expected.

  Expected behavior:
  - Only confirmation dialog pops up

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1445595/+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 1522212] [NEW] kernel panic involving threading

[beauxq]

Public bug reported:

my system:
intel core i5
nvidia 310m
lubuntu 15.10
sfml libsfml-dev 2.3.2+dfsg-1
g++ 4:5.2.1-3ubuntu1

I'm running my own cross-platform multimedia application.
The program works as expected on this same ubuntu system with the proprietary 
nvidia driver and works as expected in Windows.
This is how I conclude that the bug is in nouveau.

This program uses sfml and c++ std::thread
I send a thread to load some textures (into video memory), main thread shows a 
simple loading screen.
artifacts on screen, then kernel panic

I can reproduce the crash 100% on this system. I don't have another system to 
test it with.
I have been unable to reproduce the problem with a smaller amount of code, I 
can zip up the whole project for you if you want.

The problem does not occur if I just call the same functions in the main
thread, only when I create a separate thread to load the textures.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Wed Dec  2 18:41:45 2015
InstallationDate: Installed on 2015-10-18 (45 days ago)
InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: xserver-xorg-video-nouveau
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xserver-xorg-video-nouveau (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wily

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

Title:
  kernel panic involving threading

Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  my system:
  intel core i5
  nvidia 310m
  lubuntu 15.10
  sfml libsfml-dev 2.3.2+dfsg-1
  g++ 4:5.2.1-3ubuntu1

  I'm running my own cross-platform multimedia application.
  The program works as expected on this same ubuntu system with the proprietary 
nvidia driver and works as expected in Windows.
  This is how I conclude that the bug is in nouveau.

  This program uses sfml and c++ std::thread
  I send a thread to load some textures (into video memory), main thread shows 
a simple loading screen.
  artifacts on screen, then kernel panic

  I can reproduce the crash 100% on this system. I don't have another system to 
test it with.
  I have been unable to reproduce the problem with a smaller amount of code, I 
can zip up the whole project for you if you want.

  The problem does not occur if I just call the same functions in the
  main thread, only when I create a separate thread to load the
  textures.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Wed Dec  2 18:41:45 2015
  InstallationDate: Installed on 2015-10-18 (45 days ago)
  InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1522212/+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 1445595] Re: Empty trash from Launcher results in Nautilus window opening

[Launchpad Bug Tracker]

This bug was fixed in the package nautilus - 1:3.18.2-1ubuntu1

---
nautilus (1:3.18.2-1ubuntu1) xenial; urgency=medium

  * New version (lp: #1463662) and resynchronize on Debian
- better layout in the icons view (lp: #589433, #1019298)
- can move link type .desktop (lp: #1278437)
  * The update uses GtkHeaderBar decorations and has no menubar for now,
the menus are coming back later and UI is likely to be tweaked again
based on the feedback from this version
  * Removed changed, deprecated or included in the new version
  * debian/patches/revert_remove_unused_GtkActions.patch:
  * debian/patches/restore-traditional-menu-bar.patch:
- not needed with the new proper menubar changeset
  * debian/patches/11_copy_skipping_pager.patch:
- the new version has no copy dialog
  * debian/patches/14_bring_del_instead_ctrl_del.patch:
- resolved in the new version
  * debian/patches/git_name_column.patch,
debian/patches/git_multiple_desktop_names.patch,
debian/patches/git_file_dnd.patch,
debian/patches/git_sidebar_selection.patch,
debian/patches/git_slot_order.patch,
debian/patches/git_unmount_seg.patch,
debian/patches/git_valid_list.patch,
debian/patches/git_nomodel_segfault.patch,
debian/patches/git_open_dir_with.patch,
debian/patches/git_wrap_label.patch,
debian/patches/git_null_uri.patch,
debian/patches/git_revert_location_entry.patch,
debian/patches/ignore-no-desktop-if-not-first-launch.patch,
0001-application-use-correct-order-to-watch-for-GSettings.patch:
- included in the new version
  * Remaining changes
  * debian/control.in:
- Build-Depends on dh-migrations, libunity-dev,
  updated gnome-pkg-tools requirement
- lower gnome-sushi Recommends to a Suggests
- don't recommends gnome-icon-theme-symbolic it's deprecated
- nautilus-data should not need to recommends nautilus,
  lower to a suggests so file-roller doesn't bring in nautilus
  * debian/changelog, debian/rules: set epoch number (which was added by error)
  * debian/mount-archive.desktop:
  * debian/mount-archive.desktop.in:
- New nautilus context menu item to allow mounting zip, iso, etc
  * debian/nautilus.install:
- don't move the autostart to usr
- install mount-archive menu
- install nautilus-folder-handler.desktop
  * debian/nautilus-data.install:
- install apport hook
  * debian/nautilus-folder-handler.desktop:
- ship a copy of nautilus.desktop with NoDisplay=true since some user
  configurations refer to it
  * debian/nautilus.migrations,
debian/nautilus-unity-launcher-icon-rename.py:
- change the nautilus.desktop entry in the unity configuration to the
  new org.gnome.Nautilus name (lp: #1436297)
  * debian/source_nautilus.py:
- Apport hook to list versions of files in /usr/lib/nautilus and reassign
  the crashes when there are not due to nautilus code directly
  * debian/rules:
- use dh_migrations and build compat desktop entries
  * debian/patches/03_translations_list_update.patch:
- Translate the mount-archive menu entry
  * debian/patches/04_suppress_umount_in_ltsp.patch:
- Don't list unmount and eject actions on LTSP clients
  * debian/patches/06_never_exec_nonexec_launchers.patch:
- Implement non-exec policy for .desktop handler.
  * debian/patches/08_clean_session_capplet.patch:
- use NoDisplay for the new autostart desktop to keep the capplet clean
  * debian/patches/12_unity_launcher_support.patch:
- unity launcher integration (list bookmarks in the context menu,
  display a bar on the icon during copies)
  * debian/patches/15_use-ubuntu-help.patch:
- use the ubuntu documentation
  * debian/patches/16_unity_new_documents.patch:
- display the "new document" menu under unity, even if there is no
  template installed (lp: #1113648)
  * debian/patches/17_static_unity_quicklist.patch:
- Use nautilus --new-window to open a New window
  * debian/patches/18_unity_icon_color.patch:
- specify a background color for the unity launcher icon (lp: #1081691)
  * debian/patches/dont_wrap_labels_after_dots.patch:
- don't wrap labels after a dot if they are followed by a number,
  the upstream code has a hack for 3 digit version numbers which
  doesn't really make sense (lp: #942539)
  * debian/patches/19_unity_open_location_xid.patch:
- don't try to call functions on null objects (lp: #1285895)
- delay dbus registration until we don't have a bus
  * debian/patches/ubuntu_revert_no_wallpaper.patch:
- revert upstream changes to use a rgba desktop view, until the other
  components are ready for that change, see lp #1159430 for details
  * debian/patches/interactive_search.patch:
- Restore interactive search as an option (lp: #1164016)
  * debian/patches/ubuntu_infobars_color.patch: set the infobars type
to "other" rather than "question" to avoid blue cluebars (lp: #1259059)
  * debian/patches/ubuntu_tracker_o

[Desktop-packages] [Bug 1522209] [NEW] after grub it takes a lot of time before I can login and after login it takes another lot of time before the desktop is usable

[Lilian Martins]

Public bug reported:

I'm not sure if it's xorg the problem at all

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-37.42-generic 3.19.8-ckt9
Uname: Linux 3.19.0-37-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:
 
ApportVersion: 2.17.2-0ubuntu1.8
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
Date: Wed Dec  2 22:15:31 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus: fglrx-updates-core, 15.200, 3.19.0-37-generic, x86_64: installed
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] 
[1002:6759] (prog-if 00 [VGA controller])
   Subsystem: XFX Pine Group Inc. Device [1682:3191]
InstallationDate: Installed on 2015-07-11 (144 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Gigabyte Technology Co., Ltd. GA-970A-D3
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-37-generic 
root=UUID=f8325395-4dff-4c5b-8289-7ce8286b5677 ro recovery nomodeset
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/16/2013
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F13b
dmi.board.name: GA-970A-D3
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.:bvrF13b:bd12/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-970A-D3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.12.1+15.04.20150922-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
xserver.bootTime: Wed Dec  2 20:42:28 2015
xserver.configfile: /etc/X11/xorg.conf
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.1-0ubuntu3.1
xserver.video_driver: fglrx

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu vivid

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

Title:
  after grub it takes a lot of time before I can login and after login
  it takes another lot of time before the desktop is usable

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm not sure if it's xorg the problem at all

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-37.42-generic 3.19.8-ckt9
  Uname: Linux 3.19.0-37-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.8
  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
  Date: Wed Dec  2 22:15:31 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus: fglrx-updates-core, 15.200, 3.19.0-37-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] 
[1002:6759] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Device [1682:3191]
  InstallationDate: Installed on 2015-07-11 (144 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Gigabyte Technology Co., Ltd. GA-970A-D3
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-37-generic 
root=UUID=f8325395-4dff-4c5b-8289-7ce8286b5677 ro recovery nomodeset
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/16/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F13b
  dmi.board.na

[Desktop-packages] [Bug 1278437] Re: can't move link type .desktop files around on desktop

[Launchpad Bug Tracker]

This bug was fixed in the package nautilus - 1:3.18.2-1ubuntu1

---
nautilus (1:3.18.2-1ubuntu1) xenial; urgency=medium

  * New version (lp: #1463662) and resynchronize on Debian
- better layout in the icons view (lp: #589433, #1019298)
- can move link type .desktop (lp: #1278437)
  * The update uses GtkHeaderBar decorations and has no menubar for now,
the menus are coming back later and UI is likely to be tweaked again
based on the feedback from this version
  * Removed changed, deprecated or included in the new version
  * debian/patches/revert_remove_unused_GtkActions.patch:
  * debian/patches/restore-traditional-menu-bar.patch:
- not needed with the new proper menubar changeset
  * debian/patches/11_copy_skipping_pager.patch:
- the new version has no copy dialog
  * debian/patches/14_bring_del_instead_ctrl_del.patch:
- resolved in the new version
  * debian/patches/git_name_column.patch,
debian/patches/git_multiple_desktop_names.patch,
debian/patches/git_file_dnd.patch,
debian/patches/git_sidebar_selection.patch,
debian/patches/git_slot_order.patch,
debian/patches/git_unmount_seg.patch,
debian/patches/git_valid_list.patch,
debian/patches/git_nomodel_segfault.patch,
debian/patches/git_open_dir_with.patch,
debian/patches/git_wrap_label.patch,
debian/patches/git_null_uri.patch,
debian/patches/git_revert_location_entry.patch,
debian/patches/ignore-no-desktop-if-not-first-launch.patch,
0001-application-use-correct-order-to-watch-for-GSettings.patch:
- included in the new version
  * Remaining changes
  * debian/control.in:
- Build-Depends on dh-migrations, libunity-dev,
  updated gnome-pkg-tools requirement
- lower gnome-sushi Recommends to a Suggests
- don't recommends gnome-icon-theme-symbolic it's deprecated
- nautilus-data should not need to recommends nautilus,
  lower to a suggests so file-roller doesn't bring in nautilus
  * debian/changelog, debian/rules: set epoch number (which was added by error)
  * debian/mount-archive.desktop:
  * debian/mount-archive.desktop.in:
- New nautilus context menu item to allow mounting zip, iso, etc
  * debian/nautilus.install:
- don't move the autostart to usr
- install mount-archive menu
- install nautilus-folder-handler.desktop
  * debian/nautilus-data.install:
- install apport hook
  * debian/nautilus-folder-handler.desktop:
- ship a copy of nautilus.desktop with NoDisplay=true since some user
  configurations refer to it
  * debian/nautilus.migrations,
debian/nautilus-unity-launcher-icon-rename.py:
- change the nautilus.desktop entry in the unity configuration to the
  new org.gnome.Nautilus name (lp: #1436297)
  * debian/source_nautilus.py:
- Apport hook to list versions of files in /usr/lib/nautilus and reassign
  the crashes when there are not due to nautilus code directly
  * debian/rules:
- use dh_migrations and build compat desktop entries
  * debian/patches/03_translations_list_update.patch:
- Translate the mount-archive menu entry
  * debian/patches/04_suppress_umount_in_ltsp.patch:
- Don't list unmount and eject actions on LTSP clients
  * debian/patches/06_never_exec_nonexec_launchers.patch:
- Implement non-exec policy for .desktop handler.
  * debian/patches/08_clean_session_capplet.patch:
- use NoDisplay for the new autostart desktop to keep the capplet clean
  * debian/patches/12_unity_launcher_support.patch:
- unity launcher integration (list bookmarks in the context menu,
  display a bar on the icon during copies)
  * debian/patches/15_use-ubuntu-help.patch:
- use the ubuntu documentation
  * debian/patches/16_unity_new_documents.patch:
- display the "new document" menu under unity, even if there is no
  template installed (lp: #1113648)
  * debian/patches/17_static_unity_quicklist.patch:
- Use nautilus --new-window to open a New window
  * debian/patches/18_unity_icon_color.patch:
- specify a background color for the unity launcher icon (lp: #1081691)
  * debian/patches/dont_wrap_labels_after_dots.patch:
- don't wrap labels after a dot if they are followed by a number,
  the upstream code has a hack for 3 digit version numbers which
  doesn't really make sense (lp: #942539)
  * debian/patches/19_unity_open_location_xid.patch:
- don't try to call functions on null objects (lp: #1285895)
- delay dbus registration until we don't have a bus
  * debian/patches/ubuntu_revert_no_wallpaper.patch:
- revert upstream changes to use a rgba desktop view, until the other
  components are ready for that change, see lp #1159430 for details
  * debian/patches/interactive_search.patch:
- Restore interactive search as an option (lp: #1164016)
  * debian/patches/ubuntu_infobars_color.patch: set the infobars type
to "other" rather than "question" to avoid blue cluebars (lp: #1259059)
  * debian/patches/ubuntu_tracker_o

[Desktop-packages] [Bug 1019298] Re: image preview size is small and not well ordered

[Launchpad Bug Tracker]

This bug was fixed in the package nautilus - 1:3.18.2-1ubuntu1

---
nautilus (1:3.18.2-1ubuntu1) xenial; urgency=medium

  * New version (lp: #1463662) and resynchronize on Debian
- better layout in the icons view (lp: #589433, #1019298)
- can move link type .desktop (lp: #1278437)
  * The update uses GtkHeaderBar decorations and has no menubar for now,
the menus are coming back later and UI is likely to be tweaked again
based on the feedback from this version
  * Removed changed, deprecated or included in the new version
  * debian/patches/revert_remove_unused_GtkActions.patch:
  * debian/patches/restore-traditional-menu-bar.patch:
- not needed with the new proper menubar changeset
  * debian/patches/11_copy_skipping_pager.patch:
- the new version has no copy dialog
  * debian/patches/14_bring_del_instead_ctrl_del.patch:
- resolved in the new version
  * debian/patches/git_name_column.patch,
debian/patches/git_multiple_desktop_names.patch,
debian/patches/git_file_dnd.patch,
debian/patches/git_sidebar_selection.patch,
debian/patches/git_slot_order.patch,
debian/patches/git_unmount_seg.patch,
debian/patches/git_valid_list.patch,
debian/patches/git_nomodel_segfault.patch,
debian/patches/git_open_dir_with.patch,
debian/patches/git_wrap_label.patch,
debian/patches/git_null_uri.patch,
debian/patches/git_revert_location_entry.patch,
debian/patches/ignore-no-desktop-if-not-first-launch.patch,
0001-application-use-correct-order-to-watch-for-GSettings.patch:
- included in the new version
  * Remaining changes
  * debian/control.in:
- Build-Depends on dh-migrations, libunity-dev,
  updated gnome-pkg-tools requirement
- lower gnome-sushi Recommends to a Suggests
- don't recommends gnome-icon-theme-symbolic it's deprecated
- nautilus-data should not need to recommends nautilus,
  lower to a suggests so file-roller doesn't bring in nautilus
  * debian/changelog, debian/rules: set epoch number (which was added by error)
  * debian/mount-archive.desktop:
  * debian/mount-archive.desktop.in:
- New nautilus context menu item to allow mounting zip, iso, etc
  * debian/nautilus.install:
- don't move the autostart to usr
- install mount-archive menu
- install nautilus-folder-handler.desktop
  * debian/nautilus-data.install:
- install apport hook
  * debian/nautilus-folder-handler.desktop:
- ship a copy of nautilus.desktop with NoDisplay=true since some user
  configurations refer to it
  * debian/nautilus.migrations,
debian/nautilus-unity-launcher-icon-rename.py:
- change the nautilus.desktop entry in the unity configuration to the
  new org.gnome.Nautilus name (lp: #1436297)
  * debian/source_nautilus.py:
- Apport hook to list versions of files in /usr/lib/nautilus and reassign
  the crashes when there are not due to nautilus code directly
  * debian/rules:
- use dh_migrations and build compat desktop entries
  * debian/patches/03_translations_list_update.patch:
- Translate the mount-archive menu entry
  * debian/patches/04_suppress_umount_in_ltsp.patch:
- Don't list unmount and eject actions on LTSP clients
  * debian/patches/06_never_exec_nonexec_launchers.patch:
- Implement non-exec policy for .desktop handler.
  * debian/patches/08_clean_session_capplet.patch:
- use NoDisplay for the new autostart desktop to keep the capplet clean
  * debian/patches/12_unity_launcher_support.patch:
- unity launcher integration (list bookmarks in the context menu,
  display a bar on the icon during copies)
  * debian/patches/15_use-ubuntu-help.patch:
- use the ubuntu documentation
  * debian/patches/16_unity_new_documents.patch:
- display the "new document" menu under unity, even if there is no
  template installed (lp: #1113648)
  * debian/patches/17_static_unity_quicklist.patch:
- Use nautilus --new-window to open a New window
  * debian/patches/18_unity_icon_color.patch:
- specify a background color for the unity launcher icon (lp: #1081691)
  * debian/patches/dont_wrap_labels_after_dots.patch:
- don't wrap labels after a dot if they are followed by a number,
  the upstream code has a hack for 3 digit version numbers which
  doesn't really make sense (lp: #942539)
  * debian/patches/19_unity_open_location_xid.patch:
- don't try to call functions on null objects (lp: #1285895)
- delay dbus registration until we don't have a bus
  * debian/patches/ubuntu_revert_no_wallpaper.patch:
- revert upstream changes to use a rgba desktop view, until the other
  components are ready for that change, see lp #1159430 for details
  * debian/patches/interactive_search.patch:
- Restore interactive search as an option (lp: #1164016)
  * debian/patches/ubuntu_infobars_color.patch: set the infobars type
to "other" rather than "question" to avoid blue cluebars (lp: #1259059)
  * debian/patches/ubuntu_tracker_o

[Desktop-packages] [Bug 1463662] Re: Update to 3.18

[Launchpad Bug Tracker]

This bug was fixed in the package nautilus - 1:3.18.2-1ubuntu1

---
nautilus (1:3.18.2-1ubuntu1) xenial; urgency=medium

  * New version (lp: #1463662) and resynchronize on Debian
- better layout in the icons view (lp: #589433, #1019298)
- can move link type .desktop (lp: #1278437)
  * The update uses GtkHeaderBar decorations and has no menubar for now,
the menus are coming back later and UI is likely to be tweaked again
based on the feedback from this version
  * Removed changed, deprecated or included in the new version
  * debian/patches/revert_remove_unused_GtkActions.patch:
  * debian/patches/restore-traditional-menu-bar.patch:
- not needed with the new proper menubar changeset
  * debian/patches/11_copy_skipping_pager.patch:
- the new version has no copy dialog
  * debian/patches/14_bring_del_instead_ctrl_del.patch:
- resolved in the new version
  * debian/patches/git_name_column.patch,
debian/patches/git_multiple_desktop_names.patch,
debian/patches/git_file_dnd.patch,
debian/patches/git_sidebar_selection.patch,
debian/patches/git_slot_order.patch,
debian/patches/git_unmount_seg.patch,
debian/patches/git_valid_list.patch,
debian/patches/git_nomodel_segfault.patch,
debian/patches/git_open_dir_with.patch,
debian/patches/git_wrap_label.patch,
debian/patches/git_null_uri.patch,
debian/patches/git_revert_location_entry.patch,
debian/patches/ignore-no-desktop-if-not-first-launch.patch,
0001-application-use-correct-order-to-watch-for-GSettings.patch:
- included in the new version
  * Remaining changes
  * debian/control.in:
- Build-Depends on dh-migrations, libunity-dev,
  updated gnome-pkg-tools requirement
- lower gnome-sushi Recommends to a Suggests
- don't recommends gnome-icon-theme-symbolic it's deprecated
- nautilus-data should not need to recommends nautilus,
  lower to a suggests so file-roller doesn't bring in nautilus
  * debian/changelog, debian/rules: set epoch number (which was added by error)
  * debian/mount-archive.desktop:
  * debian/mount-archive.desktop.in:
- New nautilus context menu item to allow mounting zip, iso, etc
  * debian/nautilus.install:
- don't move the autostart to usr
- install mount-archive menu
- install nautilus-folder-handler.desktop
  * debian/nautilus-data.install:
- install apport hook
  * debian/nautilus-folder-handler.desktop:
- ship a copy of nautilus.desktop with NoDisplay=true since some user
  configurations refer to it
  * debian/nautilus.migrations,
debian/nautilus-unity-launcher-icon-rename.py:
- change the nautilus.desktop entry in the unity configuration to the
  new org.gnome.Nautilus name (lp: #1436297)
  * debian/source_nautilus.py:
- Apport hook to list versions of files in /usr/lib/nautilus and reassign
  the crashes when there are not due to nautilus code directly
  * debian/rules:
- use dh_migrations and build compat desktop entries
  * debian/patches/03_translations_list_update.patch:
- Translate the mount-archive menu entry
  * debian/patches/04_suppress_umount_in_ltsp.patch:
- Don't list unmount and eject actions on LTSP clients
  * debian/patches/06_never_exec_nonexec_launchers.patch:
- Implement non-exec policy for .desktop handler.
  * debian/patches/08_clean_session_capplet.patch:
- use NoDisplay for the new autostart desktop to keep the capplet clean
  * debian/patches/12_unity_launcher_support.patch:
- unity launcher integration (list bookmarks in the context menu,
  display a bar on the icon during copies)
  * debian/patches/15_use-ubuntu-help.patch:
- use the ubuntu documentation
  * debian/patches/16_unity_new_documents.patch:
- display the "new document" menu under unity, even if there is no
  template installed (lp: #1113648)
  * debian/patches/17_static_unity_quicklist.patch:
- Use nautilus --new-window to open a New window
  * debian/patches/18_unity_icon_color.patch:
- specify a background color for the unity launcher icon (lp: #1081691)
  * debian/patches/dont_wrap_labels_after_dots.patch:
- don't wrap labels after a dot if they are followed by a number,
  the upstream code has a hack for 3 digit version numbers which
  doesn't really make sense (lp: #942539)
  * debian/patches/19_unity_open_location_xid.patch:
- don't try to call functions on null objects (lp: #1285895)
- delay dbus registration until we don't have a bus
  * debian/patches/ubuntu_revert_no_wallpaper.patch:
- revert upstream changes to use a rgba desktop view, until the other
  components are ready for that change, see lp #1159430 for details
  * debian/patches/interactive_search.patch:
- Restore interactive search as an option (lp: #1164016)
  * debian/patches/ubuntu_infobars_color.patch: set the infobars type
to "other" rather than "question" to avoid blue cluebars (lp: #1259059)
  * debian/patches/ubuntu_tracker_o

[Desktop-packages] [Bug 589433] Re: being able to reduce space between icons

[Launchpad Bug Tracker]

This bug was fixed in the package nautilus - 1:3.18.2-1ubuntu1

---
nautilus (1:3.18.2-1ubuntu1) xenial; urgency=medium

  * New version (lp: #1463662) and resynchronize on Debian
- better layout in the icons view (lp: #589433, #1019298)
- can move link type .desktop (lp: #1278437)
  * The update uses GtkHeaderBar decorations and has no menubar for now,
the menus are coming back later and UI is likely to be tweaked again
based on the feedback from this version
  * Removed changed, deprecated or included in the new version
  * debian/patches/revert_remove_unused_GtkActions.patch:
  * debian/patches/restore-traditional-menu-bar.patch:
- not needed with the new proper menubar changeset
  * debian/patches/11_copy_skipping_pager.patch:
- the new version has no copy dialog
  * debian/patches/14_bring_del_instead_ctrl_del.patch:
- resolved in the new version
  * debian/patches/git_name_column.patch,
debian/patches/git_multiple_desktop_names.patch,
debian/patches/git_file_dnd.patch,
debian/patches/git_sidebar_selection.patch,
debian/patches/git_slot_order.patch,
debian/patches/git_unmount_seg.patch,
debian/patches/git_valid_list.patch,
debian/patches/git_nomodel_segfault.patch,
debian/patches/git_open_dir_with.patch,
debian/patches/git_wrap_label.patch,
debian/patches/git_null_uri.patch,
debian/patches/git_revert_location_entry.patch,
debian/patches/ignore-no-desktop-if-not-first-launch.patch,
0001-application-use-correct-order-to-watch-for-GSettings.patch:
- included in the new version
  * Remaining changes
  * debian/control.in:
- Build-Depends on dh-migrations, libunity-dev,
  updated gnome-pkg-tools requirement
- lower gnome-sushi Recommends to a Suggests
- don't recommends gnome-icon-theme-symbolic it's deprecated
- nautilus-data should not need to recommends nautilus,
  lower to a suggests so file-roller doesn't bring in nautilus
  * debian/changelog, debian/rules: set epoch number (which was added by error)
  * debian/mount-archive.desktop:
  * debian/mount-archive.desktop.in:
- New nautilus context menu item to allow mounting zip, iso, etc
  * debian/nautilus.install:
- don't move the autostart to usr
- install mount-archive menu
- install nautilus-folder-handler.desktop
  * debian/nautilus-data.install:
- install apport hook
  * debian/nautilus-folder-handler.desktop:
- ship a copy of nautilus.desktop with NoDisplay=true since some user
  configurations refer to it
  * debian/nautilus.migrations,
debian/nautilus-unity-launcher-icon-rename.py:
- change the nautilus.desktop entry in the unity configuration to the
  new org.gnome.Nautilus name (lp: #1436297)
  * debian/source_nautilus.py:
- Apport hook to list versions of files in /usr/lib/nautilus and reassign
  the crashes when there are not due to nautilus code directly
  * debian/rules:
- use dh_migrations and build compat desktop entries
  * debian/patches/03_translations_list_update.patch:
- Translate the mount-archive menu entry
  * debian/patches/04_suppress_umount_in_ltsp.patch:
- Don't list unmount and eject actions on LTSP clients
  * debian/patches/06_never_exec_nonexec_launchers.patch:
- Implement non-exec policy for .desktop handler.
  * debian/patches/08_clean_session_capplet.patch:
- use NoDisplay for the new autostart desktop to keep the capplet clean
  * debian/patches/12_unity_launcher_support.patch:
- unity launcher integration (list bookmarks in the context menu,
  display a bar on the icon during copies)
  * debian/patches/15_use-ubuntu-help.patch:
- use the ubuntu documentation
  * debian/patches/16_unity_new_documents.patch:
- display the "new document" menu under unity, even if there is no
  template installed (lp: #1113648)
  * debian/patches/17_static_unity_quicklist.patch:
- Use nautilus --new-window to open a New window
  * debian/patches/18_unity_icon_color.patch:
- specify a background color for the unity launcher icon (lp: #1081691)
  * debian/patches/dont_wrap_labels_after_dots.patch:
- don't wrap labels after a dot if they are followed by a number,
  the upstream code has a hack for 3 digit version numbers which
  doesn't really make sense (lp: #942539)
  * debian/patches/19_unity_open_location_xid.patch:
- don't try to call functions on null objects (lp: #1285895)
- delay dbus registration until we don't have a bus
  * debian/patches/ubuntu_revert_no_wallpaper.patch:
- revert upstream changes to use a rgba desktop view, until the other
  components are ready for that change, see lp #1159430 for details
  * debian/patches/interactive_search.patch:
- Restore interactive search as an option (lp: #1164016)
  * debian/patches/ubuntu_infobars_color.patch: set the infobars type
to "other" rather than "question" to avoid blue cluebars (lp: #1259059)
  * debian/patches/ubuntu_tracker_o

[Desktop-packages] [Bug 1459359] Re: Gtk & Glib CRITICAL messages at startup (regression)

[Hao Hu]

I can confirm this still happens in 15.10.

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

Title:
  Gtk & Glib CRITICAL messages at startup (regression)

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Every time nautilus starts it emits several "CRITICAL" assertion error
  messages.  This is a regression (didn't happen in Ubuntu 14.10)

  $   nautilus

  (nautilus:4543): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen:
  assertion 'GDK_IS_SCREEN (screen)' failed

  (nautilus:4543): GLib-GObject-WARNING **: invalid (NULL) pointer
  instance

  (nautilus:4543): GLib-GObject-CRITICAL **: g_signal_connect_object:
  assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: nautilus 1:3.14.2-0ubuntu9
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 27 10:17:38 2015
  GsettingsChanges:
   b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 
'size', 'type', 'date_modified', 'where']"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'owner', 'group', 'permissions', 'mime_type', 'where', 
'date_accessed']"
  InstallationDate: Installed on 2013-08-06 (659 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1459359/+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 1507183] Re: "safely remove" remounts after a couple of seconds

[Phillip Susi]

If one device works properly and one doesn't that points to the device
being buggy.  It may be interesting to see though, whether the same
behavior is seen in other distros.

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

Title:
  "safely remove" remounts after a couple of seconds

Status in udisks2 package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 15.04
  Release 15.04

  fresh install

  Selecting 'Safely remove' on a USB drive shoudl than required it to be
  re-plugged in to be freshly detected and mounted.

  I'm seeing this only temporally remove the drive and within a few
  seconds the device is re-mounted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1507183/+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 1522177] [NEW] nautilus sporadically very slow to start/refresh

[Reece]

Public bug reported:

System: Ubuntu 15.10, x86_64, SSD drive

Nautilus is sporadically extremely slow to start up or refresh a view
even when already running. The effect is bimodal: response is either
nearly immediate or extremely slow. For example, "nautilus ~/" is either
immediately responsive or takes ~10 seconds.

The behavior is independent of directory and invocation method; for
example, invoking via Unity Dash or Chrome's "show in folder" exhibits
similar bimodal responsiveness.

The bimodal switch seems to be related to a combination of when the
directory was last read (likely a cache effect) and whether the
directory had been modified (e.g., perhaps based on directory mtime).

The attached script and output demonstrate the effect on my laptop. It
executes "nautilus ~/" ten times, with sleep times of 0-5 seconds
between each. The data suggest that the bimodal switch due to a putative
cache timeout is ~5 seconds. That is, *all* invocations separated by
more that 5 seconds exhibit the slow mode responsiveness.

This is consistent with my experience, namely that nautilus startup is
*always* slow because real-world use invocations are always more than 5
seconds apart.

Access to the same directories in the terminal are never slow. I am not
aware of any general filesystem sluggishness (e.g., with libreoffice,
emacs, etc).

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

** Attachment added: "nautilus invocation timings"
   
https://bugs.launchpad.net/bugs/1522177/+attachment/4528782/+files/nautilus-timing

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

Title:
  nautilus sporadically very slow to start/refresh

Status in nautilus package in Ubuntu:
  New

Bug description:
  System: Ubuntu 15.10, x86_64, SSD drive

  Nautilus is sporadically extremely slow to start up or refresh a view
  even when already running. The effect is bimodal: response is either
  nearly immediate or extremely slow. For example, "nautilus ~/" is
  either immediately responsive or takes ~10 seconds.

  The behavior is independent of directory and invocation method; for
  example, invoking via Unity Dash or Chrome's "show in folder" exhibits
  similar bimodal responsiveness.

  The bimodal switch seems to be related to a combination of when the
  directory was last read (likely a cache effect) and whether the
  directory had been modified (e.g., perhaps based on directory mtime).

  The attached script and output demonstrate the effect on my laptop. It
  executes "nautilus ~/" ten times, with sleep times of 0-5 seconds
  between each. The data suggest that the bimodal switch due to a
  putative cache timeout is ~5 seconds. That is, *all* invocations
  separated by more that 5 seconds exhibit the slow mode responsiveness.

  This is consistent with my experience, namely that nautilus startup is
  *always* slow because real-world use invocations are always more than
  5 seconds apart.

  Access to the same directories in the terminal are never slow. I am
  not aware of any general filesystem sluggishness (e.g., with
  libreoffice, emacs, etc).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1522177/+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 1522177] Re: nautilus sporadically very slow to start/refresh

[Reece]

** Attachment added: "script to generate nautilus timings"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1522177/+attachment/4528783/+files/time-nautilus

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

Title:
  nautilus sporadically very slow to start/refresh

Status in nautilus package in Ubuntu:
  New

Bug description:
  System: Ubuntu 15.10, x86_64, SSD drive

  Nautilus is sporadically extremely slow to start up or refresh a view
  even when already running. The effect is bimodal: response is either
  nearly immediate or extremely slow. For example, "nautilus ~/" is
  either immediately responsive or takes ~10 seconds.

  The behavior is independent of directory and invocation method; for
  example, invoking via Unity Dash or Chrome's "show in folder" exhibits
  similar bimodal responsiveness.

  The bimodal switch seems to be related to a combination of when the
  directory was last read (likely a cache effect) and whether the
  directory had been modified (e.g., perhaps based on directory mtime).

  The attached script and output demonstrate the effect on my laptop. It
  executes "nautilus ~/" ten times, with sleep times of 0-5 seconds
  between each. The data suggest that the bimodal switch due to a
  putative cache timeout is ~5 seconds. That is, *all* invocations
  separated by more that 5 seconds exhibit the slow mode responsiveness.

  This is consistent with my experience, namely that nautilus startup is
  *always* slow because real-world use invocations are always more than
  5 seconds apart.

  Access to the same directories in the terminal are never slow. I am
  not aware of any general filesystem sluggishness (e.g., with
  libreoffice, emacs, etc).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1522177/+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 1522175] Re: horizontal bar visual artifacts around windows and on text

[themusicgod1]

screenshot

** Attachment added: "Screenshot from 2015-12-02 17-55-27.png"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1522175/+attachment/4528780/+files/Screenshot%20from%202015-12-02%2017-55-27.png

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

Title:
  horizontal bar visual artifacts around windows and on text

Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  On the first reboot after upgrade from vivid to wily, horizontal bars
  surround windows, and scramble the text on terminal, as well as the
  xfce4 menu bar.  It is not the whole screen that gets these horizontal
  bar artifacts, only particular windows, and only particular images in
  particular windows.  For example firefox is almost entirely clear,
  except for the 'bookmarks' and other icons within it, and some jpegs
  rendered within it.

  xserver-xorg:
Installed: 1:7.7+7ubuntu4
Candidate: 1:7.7+7ubuntu4

  xfce4:
Installed: 4.12.1
Candidate: 4.12.1

  Ubuntu": 15.10 (fresh upgrade from 15.04)

  Linux tbpl-makerspace 4.2.0-19-generic #23-Ubuntu SMP Wed Nov 11
  11:39:30 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Dec  2 17:56:42 2015
  InstallationDate: Installed on 2015-05-07 (209 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to wily on 2015-12-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1522175/+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 1522174] [NEW] No signal from X Server after turn TV off then back on

[Mark A. Taff]

Public bug reported:

Hardware:
  Intel NUC NUC5i5RYK,  Intel HD Graphics 6000, core i5
  LG TV, model 47LA6200-UA

Bug is reproducible on demand.

I have the box connected to the TV via HDMI.

Steps to reproduce:
1) Turn on TV
2) Boot into Linux, log into KDE
3) Turn TV off, leave computer running
4) Turn TV back on
5) TV reports no signal for input

At state #5, cannot get the signal back by:
a) shaking mouse,
b) pressing keyboard keys
c) unplugging, then reconnecting, HDMI cable

At state #5:
  --login via ssh from remote computer works
  --top shows all processes running as typical for KDE
  --able to start x11vnc via ssh from remote machine, then connect to display 
:0 using KRDC as a client; KDE still works fine
  --I can get the signal back by killing X form a local tty, or remotely vis 
ssh, in which case X will restart and I will get the signal back until the next 
time I turn off the TV, though that requires me to relogin to KDE and start 
from scratch as the session isn't saved when you kill X that way.

Workaround (seems to work, at least for cases when TV is off for a few minutes):
  --Before shutting of TV, switch to tty1 (Ctrl+Alt+F1)
  --Shut off TV
  --Turn TV on when you next want to use it
  --tty1 will show up, switch to tty7 (vt7), and it works as expected.
  --on the prior step a console message is printed:
  [timestamp] [drm:gen8_irq_handler [i915]] *ERROR* The master control 
interrupt lied (SDE)!

The same message also repeats upon HDMI cable disconnect/reconnect.

I'm currently using the latest Intel drivers from
https://01.org/linuxgraphics but the issue also presents with default
kubuntu drivers.

I suspect the issue has to do with the HDMI handshake not being
renewed/restarted when the TV comes back on. Even when in state #5, the
TV detects when the HDMI cable is unplugged ("No cable connected" vs "No
signal from input").

Let me know if you need any additional information or if I can do
anything to help with debugging.

Thanks!

--Mark

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xserver-xorg-core 2:1.17.2-1ubuntu9.1
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Wed Dec  2 16:20:43 2015
ExecutablePath: /usr/bin/Xorg
InstallationDate: Installed on 2015-09-04 (89 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SourcePackage: xorg-server
UpgradeStatus: Upgraded to wily on 2015-12-01 (1 days ago)

** Affects: xorg-server (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hdmi intel wily

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

Title:
  No signal from X Server after turn TV off then back on

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Hardware:
Intel NUC NUC5i5RYK,  Intel HD Graphics 6000, core i5
LG TV, model 47LA6200-UA

  Bug is reproducible on demand.

  I have the box connected to the TV via HDMI.

  Steps to reproduce:
  1) Turn on TV
  2) Boot into Linux, log into KDE
  3) Turn TV off, leave computer running
  4) Turn TV back on
  5) TV reports no signal for input

  At state #5, cannot get the signal back by:
  a) shaking mouse,
  b) pressing keyboard keys
  c) unplugging, then reconnecting, HDMI cable

  At state #5:
--login via ssh from remote computer works
--top shows all processes running as typical for KDE
--able to start x11vnc via ssh from remote machine, then connect to display 
:0 using KRDC as a client; KDE still works fine
--I can get the signal back by killing X form a local tty, or remotely vis 
ssh, in which case X will restart and I will get the signal back until the next 
time I turn off the TV, though that requires me to relogin to KDE and start 
from scratch as the session isn't saved when you kill X that way.

  Workaround (seems to work, at least for cases when TV is off for a few 
minutes):
--Before shutting of TV, switch to tty1 (Ctrl+Alt+F1)
--Shut off TV
--Turn TV on when you next want to use it
--tty1 will show up, switch to tty7 (vt7), and it works as expected.
--on the prior step a console message is printed:
[timestamp] [drm:gen8_irq_handler [i915]] *ERROR* The master 
control interrupt lied (SDE)!

  The same message also repeats upon HDMI cable disconnect/reconnect.

  I'm currently using the latest Intel drivers from
  https://01.org/linuxgraphics but the issue also presents with default
  kubuntu drivers.

  I suspect the issue has to do with the HDMI handshake not being
  renewed/restarted when the TV comes back on. Even when in state #5,
  the TV detects when the HDMI cable is unplugged ("No cable connected"
  vs "No signal from input").

  Let me know if you need any additional information

[Desktop-packages] [Bug 1522174] Re: No signal from X Server after turn TV off then back on

[Mark A. Taff]

Also, this was happening in 15.04 as well, so it isn't likely to be
caused by the upgrade to 15.10.

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

Title:
  No signal from X Server after turn TV off then back on

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Hardware:
Intel NUC NUC5i5RYK,  Intel HD Graphics 6000, core i5
LG TV, model 47LA6200-UA

  Bug is reproducible on demand.

  I have the box connected to the TV via HDMI.

  Steps to reproduce:
  1) Turn on TV
  2) Boot into Linux, log into KDE
  3) Turn TV off, leave computer running
  4) Turn TV back on
  5) TV reports no signal for input

  At state #5, cannot get the signal back by:
  a) shaking mouse,
  b) pressing keyboard keys
  c) unplugging, then reconnecting, HDMI cable

  At state #5:
--login via ssh from remote computer works
--top shows all processes running as typical for KDE
--able to start x11vnc via ssh from remote machine, then connect to display 
:0 using KRDC as a client; KDE still works fine
--I can get the signal back by killing X form a local tty, or remotely vis 
ssh, in which case X will restart and I will get the signal back until the next 
time I turn off the TV, though that requires me to relogin to KDE and start 
from scratch as the session isn't saved when you kill X that way.

  Workaround (seems to work, at least for cases when TV is off for a few 
minutes):
--Before shutting of TV, switch to tty1 (Ctrl+Alt+F1)
--Shut off TV
--Turn TV on when you next want to use it
--tty1 will show up, switch to tty7 (vt7), and it works as expected.
--on the prior step a console message is printed:
[timestamp] [drm:gen8_irq_handler [i915]] *ERROR* The master 
control interrupt lied (SDE)!

  The same message also repeats upon HDMI cable disconnect/reconnect.

  I'm currently using the latest Intel drivers from
  https://01.org/linuxgraphics but the issue also presents with default
  kubuntu drivers.

  I suspect the issue has to do with the HDMI handshake not being
  renewed/restarted when the TV comes back on. Even when in state #5,
  the TV detects when the HDMI cable is unplugged ("No cable connected"
  vs "No signal from input").

  Let me know if you need any additional information or if I can do
  anything to help with debugging.

  Thanks!

  --Mark

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Wed Dec  2 16:20:43 2015
  ExecutablePath: /usr/bin/Xorg
  InstallationDate: Installed on 2015-09-04 (89 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to wily on 2015-12-01 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1522174/+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 1359211] Re: Mouse cursor tiny when hovering unity elements in high DPI mode

[Treviño]

Backport to wily is being prepared here:
 - https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-027

That will go through the SRU process, so it will take a while to reach
everybody. If you want to test it in the meanwhile, you can just use
that PPA (to be removed once installed, as it might then be reused by
other projects).

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

Title:
  Mouse cursor tiny when hovering unity elements in high DPI mode

Status in Compiz:
  Fix Committed
Status in Unity:
  Fix Committed
Status in Unity 7.3 series:
  In Progress
Status in compiz package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released

Bug description:
  On a high DPI screen (220 DPI) the mouse cursor is really tiny when
  hovering unity elements. There are various keys in dconf to change the
  cursor's scale factor or size. I've managed to change it in a way that
  it looks normal when inside application windows, but its still tiny
  when on unity elements.

  I think this should be set automatically by the scale factor setting
  in system settings.

  
  (Using unity 7.3.1+14.10.20140811-0ubuntu1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1359211/+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 1522175] Re: horizontal bar visual artifacts around windows and on text

[themusicgod1]

screenshot 2

** Attachment added: "Screenshot from 2015-12-02 17-55-36.png"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1522175/+attachment/4528781/+files/Screenshot%20from%202015-12-02%2017-55-36.png

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

Title:
  horizontal bar visual artifacts around windows and on text

Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  On the first reboot after upgrade from vivid to wily, horizontal bars
  surround windows, and scramble the text on terminal, as well as the
  xfce4 menu bar.  It is not the whole screen that gets these horizontal
  bar artifacts, only particular windows, and only particular images in
  particular windows.  For example firefox is almost entirely clear,
  except for the 'bookmarks' and other icons within it, and some jpegs
  rendered within it.

  xserver-xorg:
Installed: 1:7.7+7ubuntu4
Candidate: 1:7.7+7ubuntu4

  xfce4:
Installed: 4.12.1
Candidate: 4.12.1

  Ubuntu": 15.10 (fresh upgrade from 15.04)

  Linux tbpl-makerspace 4.2.0-19-generic #23-Ubuntu SMP Wed Nov 11
  11:39:30 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Dec  2 17:56:42 2015
  InstallationDate: Installed on 2015-05-07 (209 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to wily on 2015-12-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1522175/+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 1522175] Re: horizontal bar visual artifacts around windows and on text

[themusicgod1]

00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation 4 Series Chipset Integrated 
Graphics Controller (rev 03)
 *-cpu
  product: Intel(R) Core(TM)2 Quad  CPU   Q9300  @ 2.50GHz
  vendor: Intel Corp.
  physical id: 1
  bus info: cpu@0
  size: 2003MHz
  capacity: 2499MHz
  width: 64 bits
  capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht 
tm pbe syscall nx x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl 
aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm 
sse4_1 lahf_lm dtherm tpr_shadow vnmi flexpriority cpufreq
 *-pci
  description: Host bridge
  product: 4 Series Chipset DRAM Controller
  vendor: Intel Corporation
  physical id: 100
  bus info: pci@:00:00.0
  version: 03
  width: 32 bits
  clock: 33MHz
  configuration: driver=agpgart-intel
  resources: irq:0
*-display:0
 description: VGA compatible controller
 product: 4 Series Chipset Integrated Graphics Controller
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 03
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:28 memory:fe40-fe7f 
memory:d000-dfff ioport:dc00(size=8)
*-display:1 UNCLAIMED
 description: Display controller
 product: 4 Series Chipset Integrated Graphics Controller
 vendor: Intel Corporation
 physical id: 2.1
 bus info: pci@:00:02.1
 version: 03
 width: 64 bits
 clock: 33MHz
 capabilities: pm bus_master cap_list
 configuration: latency=0
 resources: memory:fe80-fe8f

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

Title:
  horizontal bar visual artifacts around windows and on text

Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  On the first reboot after upgrade from vivid to wily, horizontal bars
  surround windows, and scramble the text on terminal, as well as the
  xfce4 menu bar.  It is not the whole screen that gets these horizontal
  bar artifacts, only particular windows, and only particular images in
  particular windows.  For example firefox is almost entirely clear,
  except for the 'bookmarks' and other icons within it, and some jpegs
  rendered within it.

  xserver-xorg:
Installed: 1:7.7+7ubuntu4
Candidate: 1:7.7+7ubuntu4

  xfce4:
Installed: 4.12.1
Candidate: 4.12.1

  Ubuntu": 15.10 (fresh upgrade from 15.04)

  Linux tbpl-makerspace 4.2.0-19-generic #23-Ubuntu SMP Wed Nov 11
  11:39:30 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Dec  2 17:56:42 2015
  InstallationDate: Installed on 2015-05-07 (209 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to wily on 2015-12-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1522175/+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 1522175] [NEW] horizontal bar visual artifacts around windows and on text

[themusicgod1]

Public bug reported:

On the first reboot after upgrade from vivid to wily, horizontal bars
surround windows, and scramble the text on terminal, as well as the
xfce4 menu bar.  It is not the whole screen that gets these horizontal
bar artifacts, only particular windows, and only particular images in
particular windows.  For example firefox is almost entirely clear,
except for the 'bookmarks' and other icons within it, and some jpegs
rendered within it.

xserver-xorg:
  Installed: 1:7.7+7ubuntu4
  Candidate: 1:7.7+7ubuntu4

xfce4:
  Installed: 4.12.1
  Candidate: 4.12.1

Ubuntu": 15.10 (fresh upgrade from 15.04)

Linux tbpl-makerspace 4.2.0-19-generic #23-Ubuntu SMP Wed Nov 11
11:39:30 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Dec  2 17:56:42 2015
InstallationDate: Installed on 2015-05-07 (209 days ago)
InstallationMedia: Ubuntu-Studio 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
SourcePackage: xserver-xorg-video-intel
UpgradeStatus: Upgraded to wily on 2015-12-02 (0 days ago)

** Affects: xserver-xorg-video-intel (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wily

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

Title:
  horizontal bar visual artifacts around windows and on text

Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  On the first reboot after upgrade from vivid to wily, horizontal bars
  surround windows, and scramble the text on terminal, as well as the
  xfce4 menu bar.  It is not the whole screen that gets these horizontal
  bar artifacts, only particular windows, and only particular images in
  particular windows.  For example firefox is almost entirely clear,
  except for the 'bookmarks' and other icons within it, and some jpegs
  rendered within it.

  xserver-xorg:
Installed: 1:7.7+7ubuntu4
Candidate: 1:7.7+7ubuntu4

  xfce4:
Installed: 4.12.1
Candidate: 4.12.1

  Ubuntu": 15.10 (fresh upgrade from 15.04)

  Linux tbpl-makerspace 4.2.0-19-generic #23-Ubuntu SMP Wed Nov 11
  11:39:30 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Dec  2 17:56:42 2015
  InstallationDate: Installed on 2015-05-07 (209 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to wily on 2015-12-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1522175/+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 1485020] Re: firefox 40 shows a non-overrideable security error when talking to a captive portal

[Brian Murray]

** Changed in: firefox (Ubuntu)
 Assignee: Group_5 (santhoshsk12695) => (unassigned)

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

Title:
  firefox 40 shows a non-overrideable security error when talking to a
  captive portal

Status in firefox package in Ubuntu:
  New

Bug description:
  When trying to connect to the airport wifi at the Portland Airport
  
(https://flypdxconnect.portofportland.com:8443/guestportal/gateway?sessionId=eb0a3d0a003315a2c104ce55&portal=LOC1&action=cwa),
  firefox presents me with a non-overrideable security error:

  Secure Connection Failed

  An error occurred during a connection to
  flypdxconnect.portofportland.com:8443. SSL received a weak ephemeral
  Diffie-Hellman key in Server Key Exchange handshake message. (Error
  code: ssl_error_weak_server_ephemeral_dh_key)

  The page you are trying to view cannot be shown because the authenticity 
of the received data could not be verified.
  Please contact the website owners to inform them of this problem.

  When the user is behind a captive portal and talking to that portal is
  the only way to get Internet access, it is not acceptable to enforce
  an SSL security policy where the user has no way of overriding it, no
  way of fixing the server, and no reason to care about the security of
  the connection to this server.

  As a workaround for this issue, I ran chrome.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1485020/+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 1476702] Re: Xorg crash when using Spotify client

[Paul Smith]

Updating the BIOS seems to have fixed it: no crashes since then.  Thanks
for the support!

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

Title:
  Xorg crash when using Spotify client

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Ever since I upgraded from Ubuntu GNOME 14.04 to Ubuntu GNOME 15.04,
  I've had my entire desktop crash relatively quickly when using
  Spotify, if I mess around with the client much.  Just starting the
  client is no problem, and it plays songs OK, but for a while whenever
  I clicked one of my playlists it would immediately crash.  I stopped
  using the client for a while, but last week started using again and it
  was working for these simple cases.

  Today I started the client, picked a playlist, and grabbed the
  scrollbar and dragged it all the way to the top; as I was dragging my
  desktop crashed.  In my home directory I see a gnome-shell core:

  (gdb) thr a a bt

  Thread 2 (Thread 0x7f3da0ebd700 (LWP 16545)):
  #0  0x7f3db4d3b8dd in poll () at ../sysdeps/unix/syscall-template.S:81
  #1  0x7f3db5271ebc in g_main_context_iterate (priority=2147483647, 
n_fds=1, fds=0x7f3d9c0008e0, timeout=-1, context=0x1363e20) at 
/build/buildd/glib2.0-2.44.1/./glib/gmain.c:4103
  #2  0x7f3db5271ebc in g_main_context_iterate 
(context=context@entry=0x1363e20, block=block@entry=1, 
dispatch=dispatch@entry=1, self=) at 
/build/buildd/glib2.0-2.44.1/./glib/gmain.c:3803
  #3  0x7f3db5271fcc in g_main_context_iteration (context=0x1363e20, 
may_block=may_block@entry=1) at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3869
  #4  0x7f3db5272009 in glib_worker_main (data=) at 
/build/buildd/glib2.0-2.44.1/./glib/gmain.c:5618
  #5  0x7f3db5298955 in g_thread_proxy (data=0x1364000) at 
/build/buildd/glib2.0-2.44.1/./glib/gthread.c:764
  #6  0x7f3db50116aa in start_thread (arg=0x7f3da0ebd700) at 
pthread_create.c:333
  #7  0x7f3db4d46eed in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

  Thread 1 (Thread 0x7f3db81a4a40 (LWP 16538)):
  #0  0x7f3db5278d00 in g_logv (log_domain=0x7f3db6bfc260 "mutter", 
log_level=G_LOG_LEVEL_ERROR, format=, 
args=args@entry=0x7ffd6e47ad40) at 
/build/buildd/glib2.0-2.44.1/./glib/gmessages.c:1046
  #1  0x7f3db5278f3f in g_log (log_domain=log_domain@entry=0x7f3db6bfc260 
"mutter", log_level=log_level@entry=G_LOG_LEVEL_ERROR, 
format=format@entry=0x7f3db6bf4838 "Unable to initialize Clutter.\n") at 
/build/buildd/glib2.0-2.44.1/./glib/gmessages.c:1079
  #2  0x7f3db6b71a7e in meta_clutter_init () at backends/meta-backend.c:469
  #3  0x7f3db6ba1072 in meta_init () at core/main.c:358
  #4  0x00401ddb in main (argc=1, argv=0x7ffd6e47b1b8) at main.c:429

  but I think this is just a symptom of the X server crashing; in my X
  session log file (Xorg.0.log.old probably attached below) I see:

  [939562.032] (EE)
  [939562.064] (EE) Backtrace:
  [939562.212] (EE) 0: /usr/bin/X (xorg_backtrace+0x56) [0x7f5a10ef6556]
  [939562.212] (EE) 1: /usr/bin/X (0x7f5a10d43000+0x1b7749) [0x7f5a10efa749]
  [939562.212] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f5a0ea09000+0x352f0) 
[0x7f5a0ea3e2f0]
  [939562.212] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f5a0afe8000+0xfa6c3) [0x7f5a0b0e26c3]
  [939562.213] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f5a0afe8000+0x10cf60) [0x7f5a0b0f4f60]
  [939562.213] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f5a0afe8000+0x10e3ac) [0x7f5a0b0f63ac]
  [939562.213] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f5a0afe8000+0x10f343) [0x7f5a0b0f7343]
  [939562.213] (EE) 7: /usr/bin/X (DRI2SwapBuffers+0x1d0) [0x7f5a10ec9100]
  [939562.213] (EE) 8: /usr/bin/X (0x7f5a10d43000+0x187a7c) [0x7f5a10ecaa7c]
  [939562.213] (EE) 9: /usr/bin/X (0x7f5a10d43000+0x580a7) [0x7f5a10d9b0a7]
  [939562.213] (EE) 10: /usr/bin/X (0x7f5a10d43000+0x5c29b) [0x7f5a10d9f29b]
  [939562.213] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7f5a0ea29a40]
  [939562.213] (EE) 12: /usr/bin/X (0x7f5a10d43000+0x4662e) [0x7f5a10d8962e]
  [939562.213] (EE)
  [939562.215] (EE) Segmentation fault at address 0x7f5a1119b004
  [939562.215] (EE)
  Fatal server error:
  [939562.215] (EE) Caught signal 11 (Segmentation fault). Server aborting

  So maybe an issue with the Intel display driver?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Jul 21 10:25:08 2015
  DistUpgraded: 2015-04-27 12:05:00,462 DEBUG enabling apt cron job
  DistroCodename: vivid
  DistroVa

[Desktop-packages] [Bug 1518988] Re: Switching from "Plain Text" to "HTML" mode in Evolution composer keeps fixed width font

[Paul Smith]

I tested evolution 3.16.5-1ubuntu3.1 and the problem has been resolved.
Thanks!

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

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

Title:
  Switching from "Plain Text" to "HTML" mode in Evolution composer keeps
  fixed width font

Status in Evolution:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in evolution source package in Wily:
  Fix Committed

Bug description:
  * Impact
  the font used for writing html emails is sometime wrong and can't be changed

  * Test case
  - set the preference to html by default for new email
  - start and email
  - write some text
  - switch to "plain text" and back to "html"

  the text style should be the same before and after switching to plain
  text

  * Regression potential
  check that html emails have the correct style

  -

  I'm using Evolution 3.16.5-1ubuntu3 in Ubuntu GNOME 15.10, latest
  packages.

  My email starts by default in Plain Text mode.  However sometimes I
  want to switch to "HTML" mode.  When I do this, I get HTML-formatted
  email HOWEVER no matter what I do my font is still always fixed-width
  and never proportional.  I can change the size, the slant, etc. but
  it's always fixed-width.

  After discussing this on the Evolution mailing lists
  https://mail.gnome.org/archives/evolution-
  list/2015-November/msg00112.html it appears this is a bug that was
  fixed in 3.18.  However, the fix looks simple to backport: please
  consider pulling this into Ubuntu 15.10 version of Evolution to fix
  this extremely annoying problem:

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

  Fixed with this commit:

  
https://git.gnome.org/browse/evolution/commit/?id=8aa930e0634b22afa38753816be824d7b1622140

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1518988/+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 1503418] Re: [SRU] [REGRESSION] launching byobu from unity uses the terminal icon rather than the application icon

[Launchpad Bug Tracker]

This bug was fixed in the package byobu - 5.100-0ubuntu1

---
byobu (5.100-0ubuntu1) xenial; urgency=medium

  [ David Personette ]
  * usr/lib/byobu/include/config.py.in,
usr/lib/byobu/include/ec2instancespricing.py,
usr/lib/byobu/include/select-session.py:
- https://github.com/dustinkirkland/byobu/pull/11
- Python scripts 'futurize'd to support python3

  [ Dustin Kirkland ]
  * usr/share/applications/byobu.desktop:
- Revert upstream .desktop changes to match against
  gnome-terminal-server, LP: #1512498
  * === added directory usr/share/byobu/desktop, === added directory
usr/share/dbus-1, === added directory usr/share/dbus-1/services,
configure.ac, debian/control, debian/postinst, debian/postrm,
Makefile.am, usr/share/applications/byobu.desktop =>
usr/share/byobu/desktop/byobu.desktop,
usr/share/applications/Makefile.am =>
usr/share/byobu/desktop/Makefile.am,
usr/share/byobu/desktop/byobu.desktop.old, usr/share/dbus-
1/services/Makefile.am, usr/share/dbus-
1/services/us.kirkland.terminals.byobu.service: LP: #1512498, #1503418
- huge work around the mess that is gnome-terminal-server
- install two different desktop files to /usr/share/byobu/desktops/*
- in postinst, symlink the correct one into /usr/share/applications
- clean up that conditionally installed symlink in postinst
- suggest gnome-terminal package, as our new desktop file hardcodes
  gnome-terminal (this kind of sucks)
- in byobu.desktop, exec gnome-terminal with a --app-id hint, and
  drop the Terminal=true, as gnome-terminal will take care of that
- install a dbus service, as new gnome-terminal expects to launch
  via dbus
- fqdn namespace that service to us.kirkland.terminals.byobu
  + this is stupid, btw
  * usr/lib/byobu/include/select-session.py:
- fix regression introduced by r2448

 -- Dustin Kirkland   Sat, 14 Nov 2015 16:59:57
-0600

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

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

Title:
  [SRU] [REGRESSION] launching byobu from unity uses the terminal icon
  rather than the application icon

Status in BAMF:
  Triaged
Status in bamf package in Ubuntu:
  Triaged
Status in byobu package in Ubuntu:
  Fix Released
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in bamf source package in Wily:
  Confirmed
Status in byobu source package in Wily:
  Triaged
Status in gnome-terminal source package in Wily:
  Confirmed

Bug description:
  I just upgraded to Wily yesterday, and it seems this regression has
  crept up again (it happened around the Utopic timeframe too).

  Install Byobu.

  sudo apt-get install byobu

  Open from the Unity Launcher.  Press Windows icon.  Type 'byobu'.
  Click on the Ubuntu terminal icon.  Byobu open in the default terminal
  (as specified in the byobu.desktop file), but the icon on the left in
  the unity bar is the Terminal icon, not the Byobu one.

  
  [Impact] 

   * The icon is not displayed properly in the unity bar on the left

  
  [Test Case]

   * sudo apt-get install -y byobu
   * Press the Unity launcher key
   * Type 'byobu' and press enter
   * See the gnome terminal icon (black square with a prompt, like >_ on it)
   * Install the package from wily-proposed
   * Close byobu, and launch it again
   * See the byobu logo (a three panel Japanese screen)

  
  [Regression Potential] 

   * None

  [Other Info]
   
   * One line fix in the byobu.desktop file
   * Already applied upstream and released in xenial
   * Diff looks like this:

  === modified file 'usr/share/applications/byobu.desktop'
  --- a/usr/share/applications/byobu.desktop  2013-12-17 05:28:23 +
  +++ b/usr/share/applications/byobu.desktop  2015-10-28 00:34:48 +
  @@ -7,3 +7,4 @@
   Terminal=true
   Categories=GNOME;GTK;Utility;
   X-GNOME-Gettext-Domain=byobu
  +StartupWMClass=gnome-terminal-server

  
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/bamf/+bug/1503418/+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 1458340] Re: nm-applet crashs with segmentation fault (Cannot grab information for modem at /org/freedesktop/ModemManager1/Modem/7: No ModemManager support)

[littlelion]

I've got the same problem after updating from vivid to wily.

Usually one of the wi-fi or mobile internet connections are affected. The 
problem arises occasionally, somtimes immediately after bootup, sometimes ater 
resume from sleepmode. If it's the case in the syslog appears a similar warning 
how described in the initial post.
Additionally this warning occures:
gnome-session[1487]: (nm-applet:1690): nm-applet-WARNING **: ModemManager is 
not available for modem at /org/freedesktop/ModemManager1/Modem/0

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

Title:
  nm-applet crashs with segmentation fault (Cannot grab information for
  modem at /org/freedesktop/ModemManager1/Modem/7: No ModemManager
  support)

Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  This bug is regarding the nm-applet only. I am able to use WiFi and 4g
  modem connections without any problem but I do not have a GUI to
  manage the connections or choose one as the applet does crash whenever
  I try to run it:

  This is howit looks like:
  (nm-applet:9942): nm-applet-WARNING **: Cannot grab information for modem at 
/org/freedesktop/ModemManager1/Modem/7: No ModemManager support
  Speicherzugriffsfehler (Speicherabzug geschrieben)

  Where do I find the core dump in order to provide it as well?

  Any idea howto fix this issue?

  My setup:

  I am using a Lenovo x240 laptop and a ThinkPad EM7345 4gLTE modem (see
  http://support.lenovo.com/us/en/documents/pd031021 for details) .

  There is no package called 'network-manager-applet' so I provide the
  data for 'network-manager': 0.9.10.0-4ubuntu15.1

  Ubuntu Version: 15.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1458340/+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 1499827] Re: [ipv6] Network manager incorrectly lowers MTU when IPv6 is enabled

[Chris J Arges]

Hello Bryan, or anyone else affected,

Accepted network-manager into wily-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.0.4-0ubuntu5.2 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: network-manager (Ubuntu Wily)
   Status: Triaged => Fix Committed

** Tags added: verification-needed

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

Title:
  [ipv6] Network manager incorrectly lowers MTU when IPv6 is enabled

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Wily:
  Fix Committed

Bug description:
  [Impact]
  Users with IPv6-supporting networks will see the messages below in the bug 
description appear repeatedly as NM mistakes a 0 value for MTU in internal NM 
code with 0-size packets instead of meaning "use default MTU".

  [Test case]
  - Run network-manager on a network supporting IPv6.
  - Check /var/log/syslog for  messages from NetworkManager.

  [Regression Potential]
  This changes behavior for handling the MTU value for IPv6, which should be no 
higher than the device MTU. Since 0 is an invalid value for MTU anyway, this 
should not otherwise affect MTU handling for devices.
  Possible regressions from the change might include invalid (too high) set MTU 
for a device due to the failure to recognize cases where the MTU needs to be 
adjusted, leading to packet loss on IPv6.

  --

  Network manager is sending out a lot of warnings about changing the MTU:
  Sep 25 14:13:03 desktop NetworkManager[703]:   (wlan0): Lowering IPv6 
MTU (1480) to match device MTU (1280)
  Sep 25 14:13:21 desktop NetworkManager[703]:   (wlan0): Lowering IPv6 
MTU (1480) to match device MTU (0)
  Sep 25 14:13:21 desktop NetworkManager[703]:   (wlan0): IPv6 MTU (0) 
smaller than 1280, adjusting
  Sep 25 14:13:21 desktop NetworkManager[703]:   (wlan0): Raising device 
MTU (0) to match IPv6 MTU (1280)
  Sep 25 14:13:29 desktop NetworkManager[703]:   (wlan0): Lowering IPv6 
MTU (1480) to match device MTU (1280)

  Lowering IPv6 MTU (1480) to match device MTU (1280) repeats about 16
  times between the other messages (about 2 mins round).

  This doesn't appear to be Ubuntu specific -
  https://bbs.archlinux.org/viewtopic.php?pid=1552751

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: network-manager 1.0.4-0ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 25 14:09:20 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-01-08 (259 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150108)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to wily on 2015-08-12 (43 days ago)
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1499827/+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 1510998] Re: Xorg crashes with segfault on 15.10

[David N. Welton]

I have a very similar crash:

[ 10893.990] (EE) Backtrace:
[ 10893.990] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x557a5e41768e]
[ 10893.990] (EE) 1: /usr/bin/X (0x557a5e263000+0x1b89f9) [0x557a5e41b9f9]
[ 10893.990] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fb5b677a000+0x352f0) 
[0x7fb5b67af2f0]
[ 10893.990] (EE) 3: /usr/bin/X (WriteEventsToClient+0x3a) [0x557a5e2c635a]
[ 10893.990] (EE) 4: /usr/bin/X (0x557a5e263000+0x187cd8) [0x557a5e3eacd8]
[ 10893.990] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fb5b2b51000+0x85db3) [0x7fb5b2bd6db3]
[ 10893.990] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fb5b2b51000+0x8a5a2) [0x7fb5b2bdb5a2]
[ 10893.990] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fb5b2b51000+0x1020af) [0x7fb5b2c530af]
[ 10893.990] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fb5b2b51000+0x10469f) [0x7fb5b2c5569f]
[ 10893.990] (EE) 9: /usr/bin/X (0x557a5e263000+0x185c2c) [0x557a5e3e8c2c]
[ 10893.990] (EE) 10: /usr/bin/X (DRI2CopyRegion+0x8e) [0x557a5e3e934e]
[ 10893.991] (EE) 11: /usr/bin/X (0x557a5e263000+0x188723) [0x557a5e3eb723]
[ 10893.991] (EE) 12: /usr/bin/X (0x557a5e263000+0x5818f) [0x557a5e2bb18f]
[ 10893.991] (EE) 13: /usr/bin/X (0x557a5e263000+0x5c34b) [0x557a5e2bf34b]
[ 10893.991] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7fb5b679aa40]
[ 10893.991] (EE) 15: /usr/bin/X (_start+0x29) [0x557a5e2a96c9]
[ 10893.991] (EE) 
[ 10893.991] (EE) Segmentation fault at address 0xc98


I added the workaround referenced in the other bug, and will see how that goes. 
 It does slow things down, although now I have also disabled compositing in 
XFCE4.

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

Title:
  Xorg crashes with segfault on 15.10

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I updated my system from 15.04 to 15.10 yesterday. Since then the X
  server has already crashed 5 times, which renders the system close to
  unusable for me.

  The corresponding messages in Xorg.0.log.old are:
  [ 12125.023] (EE)
  [ 12125.023] (EE) Backtrace:
  [ 12125.023] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55953d82762e]
  [ 12125.023] (EE) 1: /usr/bin/X (0x55953d673000+0x1b8999) [0x55953d82b999]
  [ 12125.023] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f7c10e7b000+0x352f0) 
[0x7f7c10eb02f0]
  [ 12125.023] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x24edc) [0x7f7c0d276edc]
  [ 12125.023] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x26157) [0x7f7c0d278157]
  [ 12125.023] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x4a1e8) [0x7f7c0d29c1e8]
  [ 12125.023] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x4a7ec) [0x7f7c0d29c7ec]
  [ 12125.023] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x59103) [0x7f7c0d2ab103]
  [ 12125.023] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x593aa) [0x7f7c0d2ab3aa]
  [ 12125.023] (EE) 9: /usr/bin/X (0x55953d673000+0x13fb73) [0x55953d7b2b73]
  [ 12125.023] (EE) 10: /usr/bin/X (0x55953d673000+0x54ce3) [0x55953d6c7ce3]
  [ 12125.023] (EE) 11: /usr/bin/X (0x55953d673000+0x5818f) [0x55953d6cb18f]
  [ 12125.023] (EE) 12: /usr/bin/X (0x55953d673000+0x5c34b) [0x55953d6cf34b]
  [ 12125.023] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7f7c10e9ba40]
  [ 12125.023] (EE) 14: /usr/bin/X (_start+0x29) [0x55953d6b96c9]
  [ 12125.023] (EE)
  [ 12125.023] (EE) Segmentation fault at address 0x7f7e141995e0
  [ 12125.023] (EE)
  Fatal server error:
  [ 12125.023] (EE) Caught signal 11 (Segmentation fault). Server aborting

  I have attached the syslog file. The relevant messages for the three crashes 
from today can be found  at:
  Oct 28 15:56:36
  Oct 28 12:06:58
  Oct 28 09:08:51

  Unfortunately I have no clue how to reproduce the segfault. The last
  crash happened while I was reading some document and I did not push
  any button, moved the mouse or anything...

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Oct 28 16:30:43 2015
  DistUpgraded: 2015-10-27 11:46:32,614 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: kubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.19.0-31-generic, x86_64: installed
   bbswitch, 0.7, 4.2.0-16-generic, x86_64: installed
   nvidia-304, 304.128, 3.19.0-31-generic, x86_64: installed
   nvidia-304, 304.128, 4.2.0-16-generic, x86_64: installed
   vboxhost, 4.3.26, 3.19.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInteres

[Desktop-packages] [Bug 1518988] Re: Switching from "Plain Text" to "HTML" mode in Evolution composer keeps fixed width font

[Chris J Arges]

Hello Paul, or anyone else affected,

Accepted evolution into wily-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/evolution/3.16.5-1ubuntu3.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags added: verification-needed

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

Title:
  Switching from "Plain Text" to "HTML" mode in Evolution composer keeps
  fixed width font

Status in Evolution:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in evolution source package in Wily:
  Fix Committed

Bug description:
  * Impact
  the font used for writing html emails is sometime wrong and can't be changed

  * Test case
  - set the preference to html by default for new email
  - start and email
  - write some text
  - switch to "plain text" and back to "html"

  the text style should be the same before and after switching to plain
  text

  * Regression potential
  check that html emails have the correct style

  -

  I'm using Evolution 3.16.5-1ubuntu3 in Ubuntu GNOME 15.10, latest
  packages.

  My email starts by default in Plain Text mode.  However sometimes I
  want to switch to "HTML" mode.  When I do this, I get HTML-formatted
  email HOWEVER no matter what I do my font is still always fixed-width
  and never proportional.  I can change the size, the slant, etc. but
  it's always fixed-width.

  After discussing this on the Evolution mailing lists
  https://mail.gnome.org/archives/evolution-
  list/2015-November/msg00112.html it appears this is a bug that was
  fixed in 3.18.  However, the fix looks simple to backport: please
  consider pulling this into Ubuntu 15.10 version of Evolution to fix
  this extremely annoying problem:

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

  Fixed with this commit:

  
https://git.gnome.org/browse/evolution/commit/?id=8aa930e0634b22afa38753816be824d7b1622140

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1518988/+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 1449875] Re: ghostscript fails on some EPS files

[shaneonabike]

I can confirm that installing textlive-lang-cjk actually resolved this
issue. Can we resolve this by making whichever packages a requirement
because having this work seemless is fairly important for designers and
it's a simple fix (after you scower the internet for ages to find this
bug :/)

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

Title:
  ghostscript fails on some EPS files

Status in ghostscript package in Ubuntu:
  Fix Released
Status in texlive-lang package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 15.04, running in the cloud, I issue to following command to
  find the Bounding Box on the attached EPS. When I download the
  ghostscript binary from ghostscript.com or try the same on my FreeBSD
  server, it works just fine. Here's the command to reproduce:

  $ gs -q -sDEVICE=bbox -dNOPAUSE -dBATCH -dSAFER -dEPSCrop -r300
  broken-on-ubuntu-1504.eps

  The expected output:
  %%BoundingBox: 87 81 1515 1510
  %%HiResBoundingBox: 87.840941 81.63 1514.790058 1509.385370

  The output on Ubuntu 15.04:
  Error: /undefinedresource in resourcestatus
  Operand stack:
 false   ct_StyleDicts   --dict:0/4(L)--   Adobe-Japan1   --dict:0/4(L)--   
Serif   HeiseiMin-W3-83pv-RKSJ-H   Font   HeiseiMin-W3   CIDFont
  Execution stack:
 %interp_exit   .runexec2   --nostringval--   --nostringval--   
--nostringval--   2   %stopped_push   --nostringval--   --nostringval--   
--nostringval--   false   1   %stopped_push   1967   1   3   %oparray_pop   
1967   1   3   %oparray_pop   1966   1   3   %oparray_pop   --nostringval--   
1950   1   3   %oparray_pop   1836   1   3   %oparray_pop   --nostringval--   
%errorexec_pop   .runexec2   --nostringval--   --nostringval--   
--nostringval--   2   %stopped_push   --nostringval--   --nostringval--   
--nostringval--   1915   10   9   %oparray_pop
  Dictionary stack:
 --dict:1183/1684(ro)(G)--   --dict:0/20(G)--   --dict:87/200(L)--   
--dict:57/75(L)--   --dict:2/10(L)--   --dict:39/70(L)--   --dict:0/4(L)--   
--dict:0/4(L)--   --dict:20/27(ro)(G)--   --dict:20/26(ro)(G)--
  Current allocation mode is local
  Last OS error: No such file or directory
  GPL Ghostscript 9.15: Unrecoverable error, exit code 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1449875/+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 871133] Re: Volume Step not changeable in Unity and GNOME desktops

[Ubuntu Foundations Team Bug Bot]

The attachment "Add Volume Step setting for gnome-settings-daemon
v3.16.3" seems to be a patch.  If it isn't, please remove the "patch"
flag from the attachment, remove the "patch" tag, and if you are a
member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Volume Step not changeable in Unity and GNOME desktops

Status in gnome-settings-daemon:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Changing the volume step in gconf-editor does not do anything when adjusting 
the volume on a hardware dial.
  --- 
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  DistroRelease: Ubuntu 11.10
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
  Package: gnome-settings-daemon 3.2.0-0ubuntu5
  PackageArchitecture: i386
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Tags:  oneiric running-unity
  Uname: Linux 3.0.0-12-generic i686
  UpgradeStatus: Upgraded to oneiric on 2011-10-08 (3 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/871133/+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 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

[Chris J Arges]

Hello iMac, or anyone else affected,

Accepted lightdm into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lightdm/1.10.6-0ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: lightdm (Ubuntu Trusty)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.16 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Released

Bug description:
  [Impact]
  xserver-allow-tcp=true option no longer works with X.org 1.17.

  [Test Case]
  1. Edit /etc/lightdm/lightdm.conf and set [SeatDefaults] 
xserver-allow-tcp=true
  2. Start LightDM
  3. Attempt to connect to the X server using TCP

  Expected result:
  Able to connect

  Observed result:
  Unable to connect

  [Regression potential]
  Low. X.org changed their default behaviour from listen by default to listen 
if "-listen tcp" is passed as a command line flag. This is just the equivalent 
change in LightDM. Since this is a new flag to X.org if a user was to use 
another X server there is a risk it would not understand that flag. However it 
seems unlikely since X.org is the only actively developed X server.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1449282/+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 1470587] Re: dm-tool manpage has a typo

[Chris J Arges]

Hello Laine, or anyone else affected,

Accepted lightdm into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lightdm/1.10.6-0ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags added: verification-needed

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

Title:
  dm-tool manpage has a typo

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.12 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Vivid:
  Fix Committed

Bug description:
  [Impact]
  Small typo in dm-tool man page.

  [Test Case]
  1. View man page:
  $ man dm-tool

  Expected result:
  Says "switch"

  Observed result:
  Says "swith"

  [Regression potential]
  About as low as you can get...

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1470587/+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 1481561] Re: Connect to XDMCP clients on address requests come from if available

[Chris J Arges]

Hello Robert, or anyone else affected,

Accepted lightdm into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lightdm/1.10.6-0ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags removed: verification-failed

** Tags added: verification-needed

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

Title:
  Connect to XDMCP clients on address requests come from if available

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  New
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Committed

Bug description:
  [Impact]
  Currently LightDM connects to an XDMCP enabled X server using the first 
suitable address in the XDMCP Request packet. However, some clients may put a 
number of addresses in this message and potentially they are not all routable. 
If the address the request message came from is in the list we should use that 
first as that is more likely to be a routable address. This also matches the 
behaviour of GDM which ignores the contents of the Request packet anyway.

  [Test Case]
  1. Start LightDM with XDMCP enabled
  2. Connect with a client that puts a number of addresses in the Request packet

  Expected result:
  LightDM prefers the address the Request came from over the other addresses.

  Observed result:
  LightDM always picks the first address.

  [Regression Potential]
  There is a possibility of a behaviour change in existing clients that had two 
valid addresses, though the particular address shouldn't matter (unless complex 
firewalling / routing rules are being used). There is a risk that XDMCP 
behaviour could have been broken by the change (tested with regression tests).

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1481561/+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 1390808] Re: VNC / XDMCP server cannot be configured to listen on specific interfaces

[Chris J Arges]

Hello James, or anyone else affected,

Accepted lightdm into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lightdm/1.10.6-0ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: lightdm (Ubuntu Trusty)
   Status: Triaged => Fix Committed

** Tags added: verification-needed

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

Title:
  VNC / XDMCP server cannot be configured to listen on specific
  interfaces

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Triaged
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Vivid:
  Fix Committed

Bug description:
  [Impact]
  The XDMCP and VNC servers in LightDM allow connections on any network 
interface. It is desirable for these to be limited to a particular interface to 
limit who can connect (i.e. only allow local connections on 127.0.0.1).

  [Test Case]
  1. Enable the VNC server in LightDM in lightdm.conf:
  [VNCServer]
  enabled=true
  listen-address=127.0.0.1
  2. Start LightDM
  With this setup you should only be able to make a local connection.

  [Regression potential]
  Low. If the option is not set LightDM has the old behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1390808/+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 1197569] Re: Move from zeitgeist-1.0 to zeitgeist-2.0

[Mathew Hodson]

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

** Changed in: cairo-dock-plug-ins (Ubuntu)
   Importance: Undecided => Low

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

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

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

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

Title:
  Move from zeitgeist-1.0 to zeitgeist-2.0

Status in Bijiben:
  Fix Released
Status in Cairo-Dock Plug-ins:
  Fix Released
Status in Diodon:
  Fix Released
Status in Scratch:
  Fix Released
Status in Totem:
  Fix Released
Status in Ubuntu Application Launcher:
  Fix Released
Status in Unity:
  Fix Released
Status in unity-lens-applications:
  In Progress
Status in unity-lens-files:
  Fix Committed
Status in Unity Videos Lens:
  In Progress
Status in activity-log-manager package in Ubuntu:
  Fix Released
Status in bijiben package in Ubuntu:
  Fix Released
Status in cairo-dock-plug-ins package in Ubuntu:
  Fix Released
Status in diodon package in Ubuntu:
  Fix Released
Status in folks package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Confirmed
Status in synapse package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released
Status in unity-lens-applications package in Ubuntu:
  In Progress
Status in unity-lens-files package in Ubuntu:
  Fix Released
Status in unity-lens-video package in Ubuntu:
  In Progress
Status in upstart-app-launch package in Ubuntu:
  Fix Released

Bug description:
  The older libzeitgeist (http://launchpad.net/libzeitgeist) served its
  days and will be deprecated soon.

  All the apps should slowly move to libzeitgeist 2 (zeitgeist-2.0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/bijiben/+bug/1197569/+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 1504049] Re: Chromium not working in guest session (need more AppArmor rules)

[Chris J Arges]

Hello Hadmut, or anyone else affected,

Accepted lightdm into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lightdm/1.10.6-0ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: lightdm (Ubuntu Trusty)
   Status: Triaged => Fix Committed

** Tags added: verification-needed

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

Title:
  Chromium not working in guest session (need more AppArmor rules)

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.16 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Released

Bug description:
  [Impact]
  Unable to run Chromium from guest session.

  [Test Case]
  1. Start Ubuntu
  2. From greeter select guest session
  3. Load Chromium

  Expected result:
  Chromium runs.

  Observed result:
  Chromium does not run.

  [Regression Potential]
  Low. The change is a few additional apparmor rules. There is a low risk that 
the new rules might allow a guest program to access a flaw.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1504049/+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 1507033] Re: lightdm.conf boolean values false if have trailing whitespace

[Chris J Arges]

Hello Daniel, or anyone else affected,

Accepted lightdm into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lightdm/1.10.6-0ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: lightdm (Ubuntu Trusty)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  lightdm.conf boolean values false if have trailing whitespace

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.16 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Released

Bug description:
  [Impact]
  Adding trailing whitespace to a boolean true value in LightDM configuration 
has it read as false.

  [Test Case]
  1. Set a boolean configuration value in lightdm.conf to true_ (_ is a space 
character)
  2. Run LightDM

  Expected result:
  The configured value is interpreted as true.

  Observed result:
  The configured value is interpreted as false.

  [Regression potential]
  Low. We just strip trailing whitespace when checking for the value "true".

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1507033/+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 1517685] Re: XDMCP server starts without authentication if configured key does not exist

[Chris J Arges]

Hello Robert, or anyone else affected,

Accepted lightdm into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lightdm/1.10.6-0ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: lightdm (Ubuntu Trusty)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  XDMCP server starts without authentication if configured key does not
  exist

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.16 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Released
Status in lightdm package in Ubuntu:
  New
Status in lightdm source package in Precise:
  New
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Vivid:
  New
Status in lightdm source package in Wily:
  New

Bug description:
  [Impact]
  An incorrectly configured XDMCP server will start without authentication 
instead of disabling XDMCP / stopping LightDM.

  [Test Case]
  1. Set up LightDM to run an XDMCP server using an XDM authentication key, 
i.e. in lightdm.conf:
  [XDMCPServer]
  enabled=true
  key=key-name
  2. Do not create /etc/lightdm/keys.conf or do not define 'key-name' in 
keys.conf.
  3. Start LightDM
  4. Connect XDMCP client.

  Expected result:
  Either LightDM doesn't start or the XDMCP server doesn't start.

  Observed result:
  XDMCP server starts without authentication, any XDMCP client is able to 
connect. Debug message printed to log warning about missing key, but not easy 
to spot.

  [Regression Potential]
  Low - change is to not start LightDM if this case occurs. This could affect 
someone who currently has a misconfigured LightDM. In this case a warning 
message is printed to the log.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1517685/+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 1511259] Re: Session child does not inherit all LC_* variables

[Chris J Arges]

Hello Piotr, or anyone else affected,

Accepted lightdm into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lightdm/1.10.6-0ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags added: verification-needed

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

Title:
  Session child does not inherit all LC_* variables

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.16 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Released

Bug description:
  [Impact]
  Not all system locale variables are passed to sessions.

  [Test Case]
  1. Edit /etc/locale.conf and set LC_PAPER to a particular value
  2. Start LightDM
  3. Log into a session

  Expected result:
  LC_PAPER is set to the value in /etc/locale.conf

  Observed result:
  LC_PAPER is not set.

  [Regression potential]
  Low. We just added to an existing list of LC_* variables that are passed 
through to sessions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1511259/+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 1511545] Re: Implement XDMCP ForwardQuery

[Chris J Arges]

Hello Robert, or anyone else affected,

Accepted lightdm into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lightdm/1.10.6-0ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags added: verification-needed

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

Title:
  Implement XDMCP ForwardQuery

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.16 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  New
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Released

Bug description:
  [Impact]
  LightDM ignores the XDMCP ForwardQuery request.

  [Test Case]
  1. Set up XDMCP so queries are forwarded through a server
  2. Connect to LightDM

  Observed result:
  Connection fails

  Expected result:
  Connection succeeds.

  [Regression Potential]
  Some risk of existing XDMCP queries being broken by the change. Checked with 
regression tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1511545/+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 1197569] Re: Move from zeitgeist-1.0 to zeitgeist-2.0

[Mathew Hodson]

** Changed in: unity-lens-video (Ubuntu)
   Importance: Undecided => Medium

** Changed in: unity-lens-files (Ubuntu)
   Importance: Undecided => Medium

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

** Changed in: unity-lens-applications (Ubuntu)
   Importance: Undecided => Medium

** Changed in: activity-log-manager (Ubuntu)
   Importance: Undecided => Medium

** Changed in: upstart-app-launch (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Move from zeitgeist-1.0 to zeitgeist-2.0

Status in Bijiben:
  Fix Released
Status in Cairo-Dock Plug-ins:
  Fix Released
Status in Diodon:
  Fix Released
Status in Scratch:
  Fix Released
Status in Totem:
  Fix Released
Status in Ubuntu Application Launcher:
  Fix Released
Status in Unity:
  Fix Released
Status in unity-lens-applications:
  In Progress
Status in unity-lens-files:
  Fix Committed
Status in Unity Videos Lens:
  In Progress
Status in activity-log-manager package in Ubuntu:
  Fix Released
Status in bijiben package in Ubuntu:
  Fix Released
Status in cairo-dock-plug-ins package in Ubuntu:
  Fix Released
Status in diodon package in Ubuntu:
  Fix Released
Status in folks package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Confirmed
Status in synapse package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released
Status in unity-lens-applications package in Ubuntu:
  In Progress
Status in unity-lens-files package in Ubuntu:
  Fix Released
Status in unity-lens-video package in Ubuntu:
  In Progress
Status in upstart-app-launch package in Ubuntu:
  Fix Released

Bug description:
  The older libzeitgeist (http://launchpad.net/libzeitgeist) served its
  days and will be deprecated soon.

  All the apps should slowly move to libzeitgeist 2 (zeitgeist-2.0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/bijiben/+bug/1197569/+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 1287640] Re: UbuntuOne account plugin does not work

[Robert Ancell]

What would it take to make this work, i.e. to be able to create an
Ubuntu One account from the control center? I'd like to do this if it's
not too hard. How did the old Ubuntu One support work (e.g. Shotwell) -
did it use the control center or something else?

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

Title:
  UbuntuOne account plugin does not work

Status in Online Accounts: GNOME Control Center:
  In Progress
Status in webapps-sprint:
  In Progress
Status in gnome-control-center-signon package in Ubuntu:
  Confirmed
Status in ubuntuone-credentials package in Ubuntu:
  Confirmed
Status in gnome-control-center-signon source package in Xenial:
  Confirmed
Status in ubuntuone-credentials source package in Xenial:
  Confirmed

Bug description:
  When ubuntuone-credentials-common is installed, the Ubuntu One account
  is listed under the possible account types in gnome-control-center,
  but upon opening only a grey page is visible and errors are reported:

  (unity-control-center:22553): account-plugin-WARNING **:
  ap_client_load_plugin: module /usr/lib/libaccount-
  plugin-1.0/providers/libubuntuone.so not found: /usr/lib/libaccount-
  plugin-1.0/providers/libubuntuone.so: nie można otworzyć pliku obiektu
  dzielonego: Nie ma takiego pliku ani katalogu

  (unity-control-center:22553): credentials-cc-panel-CRITICAL **: cc-
  credentials-authorization-page.vala:54: No valid plugin found for
  provider ubuntuone

  What's more, it's currently possible to remove account-plugin-
  ubuntuone, but that doesn't remove the -common package above, so the
  account type is still listed as available.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center-signon 0.1.7~+14.04.20140211.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  4 11:30:18 2014
  SourcePackage: gnome-control-center-signon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center-signon/+bug/1287640/+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 1197569] Re: Move from zeitgeist-1.0 to zeitgeist-2.0

[Launchpad Bug Tracker]

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

** Changed in: totem (Ubuntu)
   Status: New => Confirmed

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

Title:
  Move from zeitgeist-1.0 to zeitgeist-2.0

Status in Bijiben:
  Fix Released
Status in Cairo-Dock Plug-ins:
  Fix Released
Status in Diodon:
  Fix Released
Status in Scratch:
  Fix Released
Status in Totem:
  Fix Released
Status in Ubuntu Application Launcher:
  Fix Released
Status in Unity:
  Fix Released
Status in unity-lens-applications:
  In Progress
Status in unity-lens-files:
  Fix Committed
Status in Unity Videos Lens:
  In Progress
Status in activity-log-manager package in Ubuntu:
  Fix Released
Status in bijiben package in Ubuntu:
  Fix Released
Status in cairo-dock-plug-ins package in Ubuntu:
  Fix Released
Status in diodon package in Ubuntu:
  Fix Released
Status in folks package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Confirmed
Status in synapse package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released
Status in unity-lens-applications package in Ubuntu:
  In Progress
Status in unity-lens-files package in Ubuntu:
  Fix Released
Status in unity-lens-video package in Ubuntu:
  In Progress
Status in upstart-app-launch package in Ubuntu:
  Fix Released

Bug description:
  The older libzeitgeist (http://launchpad.net/libzeitgeist) served its
  days and will be deprecated soon.

  All the apps should slowly move to libzeitgeist 2 (zeitgeist-2.0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/bijiben/+bug/1197569/+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 1503418] Re: [SRU] [REGRESSION] launching byobu from unity uses the terminal icon rather than the application icon

[Dustin Kirkland ]

** Changed in: byobu (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  [SRU] [REGRESSION] launching byobu from unity uses the terminal icon
  rather than the application icon

Status in BAMF:
  Triaged
Status in bamf package in Ubuntu:
  Triaged
Status in byobu package in Ubuntu:
  In Progress
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in bamf source package in Wily:
  Confirmed
Status in byobu source package in Wily:
  Triaged
Status in gnome-terminal source package in Wily:
  Confirmed

Bug description:
  I just upgraded to Wily yesterday, and it seems this regression has
  crept up again (it happened around the Utopic timeframe too).

  Install Byobu.

  sudo apt-get install byobu

  Open from the Unity Launcher.  Press Windows icon.  Type 'byobu'.
  Click on the Ubuntu terminal icon.  Byobu open in the default terminal
  (as specified in the byobu.desktop file), but the icon on the left in
  the unity bar is the Terminal icon, not the Byobu one.

  
  [Impact] 

   * The icon is not displayed properly in the unity bar on the left

  
  [Test Case]

   * sudo apt-get install -y byobu
   * Press the Unity launcher key
   * Type 'byobu' and press enter
   * See the gnome terminal icon (black square with a prompt, like >_ on it)
   * Install the package from wily-proposed
   * Close byobu, and launch it again
   * See the byobu logo (a three panel Japanese screen)

  
  [Regression Potential] 

   * None

  [Other Info]
   
   * One line fix in the byobu.desktop file
   * Already applied upstream and released in xenial
   * Diff looks like this:

  === modified file 'usr/share/applications/byobu.desktop'
  --- a/usr/share/applications/byobu.desktop  2013-12-17 05:28:23 +
  +++ b/usr/share/applications/byobu.desktop  2015-10-28 00:34:48 +
  @@ -7,3 +7,4 @@
   Terminal=true
   Categories=GNOME;GTK;Utility;
   X-GNOME-Gettext-Domain=byobu
  +StartupWMClass=gnome-terminal-server

  
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/bamf/+bug/1503418/+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 1422143] Re: No wifi connection after suspend with systemd due to missing "wpa_cli suspend"

[Vincent Gerris]

Funny thing I noticed is that if I close the lid again and open it
again, it does work again

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

Title:
  No wifi connection after suspend with systemd due to missing "wpa_cli
  suspend"

Status in One Hundred Papercuts:
  Confirmed
Status in NetworkManager:
  Unknown
Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Wily:
  Fix Committed
Status in wpa source package in Xenial:
  Fix Released

Bug description:
  Using systemd as my default init system if I resume from suspend my
  laptop, it doesn't automatically reconnect to the wireless network and
  it doesn't list the available network connections.

  The only way to get a wireless connection is to restart the network-
  manager daemon or going to the gnome-control-center, disable wireless
  and enable it again.

  SRU INFORMATION
  ===
  In some of these cases this bug can be worked around by calling "wpa_cli 
suspend/resume" before/after suspend, like we used to do with the old pm-utils 
quirks (/usr/lib/pm-utils/sleep.d/60_wpa_supplicant). This only affects 
particular hardware, and thus this needs to be tested by affected reporters, 
there is no general reproducer for arbitrary systems.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu6
  Uname: Linux 3.19.0-031900-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Sun Feb 15 18:27:39 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-10-22 (116 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  IpRoute:
   default via 10.0.0.1 dev wlan0  proto static  metric 1024
   10.0.0.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.36
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-01-13 (32 days ago)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlan0wifi  connected/org/freedesktop/NetworkManager/Devices/2  
openhost_caldas  09d1f69d-d3da-4978-a69c-d94455db7ecf  
/org/freedesktop/NetworkManager/ActiveConnection/0
   docker0  bridgeunavailable  /org/freedesktop/NetworkManager/Devices/3  
--   ----
   eth0 ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--   ----
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--   ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1422143/+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 1197569] Re: Move from zeitgeist-1.0 to zeitgeist-2.0

[Mathew Hodson]

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

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

Title:
  Move from zeitgeist-1.0 to zeitgeist-2.0

Status in Bijiben:
  Fix Released
Status in Cairo-Dock Plug-ins:
  Fix Released
Status in Diodon:
  Fix Released
Status in Scratch:
  Fix Released
Status in Totem:
  Fix Released
Status in Ubuntu Application Launcher:
  Fix Released
Status in Unity:
  Fix Released
Status in unity-lens-applications:
  In Progress
Status in unity-lens-files:
  Fix Committed
Status in Unity Videos Lens:
  In Progress
Status in activity-log-manager package in Ubuntu:
  Fix Released
Status in bijiben package in Ubuntu:
  Fix Released
Status in cairo-dock-plug-ins package in Ubuntu:
  Fix Released
Status in diodon package in Ubuntu:
  Fix Released
Status in folks package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Confirmed
Status in synapse package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released
Status in unity-lens-applications package in Ubuntu:
  In Progress
Status in unity-lens-files package in Ubuntu:
  Fix Released
Status in unity-lens-video package in Ubuntu:
  In Progress
Status in upstart-app-launch package in Ubuntu:
  Fix Released

Bug description:
  The older libzeitgeist (http://launchpad.net/libzeitgeist) served its
  days and will be deprecated soon.

  All the apps should slowly move to libzeitgeist 2 (zeitgeist-2.0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/bijiben/+bug/1197569/+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 1513662] Re: Lightdm login screen flashes black

[Patrick]

Clean install of 15.10. Also happens after locking computer, waiting for
the screen to turn black and then trying to enter the password.

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

Title:
  Lightdm login screen flashes black

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu 15.10

  lightdm 1.16.4

  Expected behaviour: At boot login screen appears and user can input
  password to reach desktop.

  What happened instead:  Boot login screen, approximately 1 second
  after appearing, flashes to black and then returns. Input appears to
  be interrupted often resulting in having to re-input user password.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: lightdm 1.16.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Nov  5 18:26:51 2015
  InstallationDate: Installed on 2015-11-05 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1513662/+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 1422143] Re: No wifi connection after suspend with systemd due to missing "wpa_cli suspend"

[Vincent Gerris]

Same issue for me on Lenovo Yoga 2 11 running Ubuntu 15.04 and systemd .
01:00.0 Network controller: Broadcom Corporation BCM43142 802.11b/g/n (rev 01)

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

Title:
  No wifi connection after suspend with systemd due to missing "wpa_cli
  suspend"

Status in One Hundred Papercuts:
  Confirmed
Status in NetworkManager:
  Unknown
Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Wily:
  Fix Committed
Status in wpa source package in Xenial:
  Fix Released

Bug description:
  Using systemd as my default init system if I resume from suspend my
  laptop, it doesn't automatically reconnect to the wireless network and
  it doesn't list the available network connections.

  The only way to get a wireless connection is to restart the network-
  manager daemon or going to the gnome-control-center, disable wireless
  and enable it again.

  SRU INFORMATION
  ===
  In some of these cases this bug can be worked around by calling "wpa_cli 
suspend/resume" before/after suspend, like we used to do with the old pm-utils 
quirks (/usr/lib/pm-utils/sleep.d/60_wpa_supplicant). This only affects 
particular hardware, and thus this needs to be tested by affected reporters, 
there is no general reproducer for arbitrary systems.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu6
  Uname: Linux 3.19.0-031900-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Sun Feb 15 18:27:39 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-10-22 (116 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  IpRoute:
   default via 10.0.0.1 dev wlan0  proto static  metric 1024
   10.0.0.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.36
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-01-13 (32 days ago)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlan0wifi  connected/org/freedesktop/NetworkManager/Devices/2  
openhost_caldas  09d1f69d-d3da-4978-a69c-d94455db7ecf  
/org/freedesktop/NetworkManager/ActiveConnection/0
   docker0  bridgeunavailable  /org/freedesktop/NetworkManager/Devices/3  
--   ----
   eth0 ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--   ----
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--   ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1422143/+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 1381625] Re: Adjust brightness to lowest value caused screen whole black

[Mathew Hodson]

** Branch linked: lp:~kaihengfeng/unity-settings-daemon/add-brightness-
limit-mechanism

** No longer affects: gnome-desktop3 (Ubuntu)

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

Title:
  Adjust brightness to lowest value caused screen whole black

Status in gnome-settings-daemon:
  Fix Released
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  In Progress
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-desktop3 source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  When adjusting screen brightness to lowest value, it turns screen
  backlight off.

  [Test Case]

  1. Install Image
  2. Press System's brightness hotkey to adjust the brightness level to the 
lowest or
  3. Go to System "Settings" -> "Brightness & Lock" to adjust brightness level 
to the lowest
  4. Check if the screen display still has backlight

  Expected results: There is still screen backlight

  Actual results: Sceen backlight is turned off

  [Regression Potential]
  None

  [Other Info]
  Ubuntu 14.04 has HWE stack lts-vivid 3.19 and it also has this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1381625/+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 1509721] Re: strange display pictures in 15.10 with intel GMA3100

[José]

Hello, I tested with Intel driver installer, but remains the same. In
Ubuntu 14.04 small faults occur, but do not bother. In 1510 it looks so
bad it can not read text.

https://www.dropbox.com/s/05dws5l8sb0jvbt/Captura%20de%20pantalla%20de%202015-12-02%2019%3A45%3A54.png?dl=0

I executed the following command
https://www.dropbox.com/s/7cs4bxjo40631s2/Captura%20de%20pantalla%20de%202015-12-02%2019%3A49%3A50.png?dl=0

https://www.dropbox.com/s/zlcdkdbav45aewd/Captura%20de%20pantalla%20de%202015-12-02%2020%3A11%3A37.png?dl=0

Is the virtual device can cause these failures?

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

Title:
  strange display pictures in 15.10 with intel GMA3100

Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  I have an HP computer with integrated graphics Intel G33 / G31 Express
  chipset GMA3100 (D VGA connector) with dual boot with ubuntu 15.10, in
  which I see strange images, here i upload some images.

  I tried to change the resolution (I have a couple of days) but the
  other operating system w7 or Ubuntu 14.04 has the same resolution at
  the same frequency and looks good.

  
https://www.dropbox.com/s/on3hmtb8nlyoq57/Captura%20de%20pantalla%20de%202015-10-20%2020-32-41.png?dl=0

  
https://www.dropbox.com/s/5eckl47unxaqfoy/Captura%20de%20pantalla%20de%202015-10-20%2020-36-50.png?dl=0

  
https://www.dropbox.com/s/qrmvvqtejyogzm4/Captura%20de%20pantalla%20de%202015-10-22%2019-36-47.png?dl=0

  During the first minute it looks good, but then increasingly seen more
  rare lines and images.

  Tranks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1509721/+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 1381625] Re: Adjust brightness to lowest value caused screen whole black

[Mathew Hodson]

** Changed in: gnome-desktop3 (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gnome-desktop3 (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: gnome-desktop3 (Ubuntu)
   Importance: Medium => High

** Changed in: gnome-desktop3 (Ubuntu Trusty)
   Importance: Medium => High

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

Title:
  Adjust brightness to lowest value caused screen whole black

Status in gnome-settings-daemon:
  Fix Released
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  In Progress
Status in gnome-desktop3 package in Ubuntu:
  Invalid
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-desktop3 source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  When adjusting screen brightness to lowest value, it turns screen
  backlight off.

  [Test Case]

  1. Install Image
  2. Press System's brightness hotkey to adjust the brightness level to the 
lowest or
  3. Go to System "Settings" -> "Brightness & Lock" to adjust brightness level 
to the lowest
  4. Check if the screen display still has backlight

  Expected results: There is still screen backlight

  Actual results: Sceen backlight is turned off

  [Regression Potential]
  None

  [Other Info]
  Ubuntu 14.04 has HWE stack lts-vivid 3.19 and it also has this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1381625/+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 1510824] Re: PolkitAgentSession incorrectly handles multiline output (as observed with pam_vas)

[Launchpad Bug Tracker]

This bug was fixed in the package policykit-1 - 0.105-11ubuntu3

---
policykit-1 (0.105-11ubuntu3) wily; urgency=medium

  * Fix handling of multi-line helper output. (LP: #1510824)

 -- Dariusz Gadomski   Fri, 20 Nov 2015
15:24:53 +0100

** Changed in: policykit-1 (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  PolkitAgentSession incorrectly handles multiline output (as observed
  with pam_vas)

Status in PolicyKit:
  Fix Released
Status in policykit-1 package in Ubuntu:
  Fix Released
Status in policykit-1 source package in Trusty:
  Fix Released
Status in policykit-1 source package in Vivid:
  Fix Released
Status in policykit-1 source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * Some PAM modules produce output of more than 1 line (e.g.
  PAM_TEXT_INFO may contain newlines in the message content). Polkit
  authentication agent is prepared to receive only single-line messages
  so it treats each line as a separate message. It fails to recognize
  the type of message for all of them except the first - hence failed
  authorization even if it was successful on the PAM-level.

   * The PAM specification does not require the modules to send only
  single-line messages. Thus, polkit needs to be fixed.

  * The helper component should escape (g_strescape) all messages before
  sending it up to the authentication agent. This way everything will be
  read as a single line and then unescaped to restore it's formatting
  with no changes required in PAM modules.

  [Test Case]

   * Use a pam module that returns a multi-line PAM_TEXT_INFO message on
  successful authentication (may require to artificially modify a pam
  module).

   * Perform a polkit authorization with e.g. pkexec ls

   * Correct authorization should end with a failure with an
  unrecognized PAM message

  [Regression Potential]

   * Fix makes advantage of the fact that polkit authentication agent
  already un-escapess (g_strcompress) all input from the helper
  component.

  * Fix is a backport of an upstream change.

  [Other Info]

   * Original bug description:

  There is an error observed when Ubuntu is configured to perform
  authentication via pam_vas (Vintela Authentication Services by Dell)
  in a disconnected mode (using cached authentication).

  Steps to reproduce:
  1. Configure pam_vas client authenticating to a remote server.
  2. Perform authentication to cache the credentials.
  3. Disconnect from the network where the server is reachable (to force using 
cached information).
  4. Perform an action requiring polkit authentication.

  Expected result:
  Authentication succeeds accompanied by the following message "You have logged 
in using cached account information.  Some network services will be 
unavailable".

  Actual result:
  Authentication fails accompanied by the following message "You have logged in 
using cached account information.  Some network services will be unavailable".

  Probable cause:
  The PolkitAgentSession part of polkit is designed to interpret only 1-line 
output, while interaction with pam_vas in the above scenario triggers helper to 
produce the following 2-line output:
  PAM_TEXT_INFO You have logged in using cached account information.  Some 
network services
  will be unavailable.

  The 'will be unavailable.' part is interpreted as an unknown message
  and causes failed authorization.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: policykit-1 0.105-4ubuntu2.14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-52.71~14.04.1-generic 3.16.7-ckt18
  Uname: Linux 3.16.0-52-generic x86_64
  NonfreeKernelModules: nvidia zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 28 09:01:37 2015
  InstallationDate: Installed on 2015-04-13 (197 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: policykit-1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1510824/+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 1513251] Re: Sync preferences not visible in device properties window

[Launchpad Bug Tracker]

This bug was fixed in the package rhythmbox - 3.2.1-1ubuntu3.1

---
rhythmbox (3.2.1-1ubuntu3.1) wily; urgency=medium

  * debian/patches/restore-traditional-menubar.patch:
- use correct keybinding label for play/pause (lp: #1274726)
  * debian/patches/git_sync_option.patch:
- don't have the sync option area having a 0 height (lp: #1513251)
  * debian/patches/git_sync_grid.patch:
- sync: replace the sync state GtkTable with a grid

 -- Sebastien Bacher   Thu, 05 Nov 2015 16:50:08
+0100

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

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

Title:
  Sync preferences not visible in device properties window

Status in Rhythmbox:
  Fix Released
Status in rhythmbox package in Ubuntu:
  Fix Released
Status in rhythmbox source package in Wily:
  Fix Released

Bug description:
  * Impact
  the Sync Preferences list tree box appears empty

  * Test Case
  - open rhythmbox
  - connect a device (phone, player, etc)
  - select it in the sidebar
  - click on the "properties" tab at the top of the screen
  - open the sync tab

  * Regression potential
  - check the layout of the sync dialog

  -

  After upgrading to wily the Sync Preferences list tree box appears
  empty. Resizing the window does not help. The same problem occurs when
  booting Ubuntu GNOME 15.10 from a live CD. The device I want to sync
  music to is an Ipod shuffle model xC323. I also tried resetting it to
  factory to no avail.

  I was expecting to see a list tree with my Music library on top and
  all my playlists as child nodes.

  The problem could in fact be a GTK problem, but I've only seen it in
  Rhythmbox so far.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: rhythmbox 3.2.1-1ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Nov  4 23:03:31 2015
  EcryptfsInUse: Yes
  SourcePackage: rhythmbox
  UpgradeStatus: Upgraded to wily on 2015-10-27 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/rhythmbox/+bug/1513251/+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 1508327] Re: ubiquity only mode: close/minimize/restore are on the right edge

[Launchpad Bug Tracker]

This bug was fixed in the package unity-settings-daemon -
15.04.1+15.10.20151029-0ubuntu1

---
unity-settings-daemon (15.04.1+15.10.20151029-0ubuntu1) wily; urgency=medium

  [ Lars Uebernickel ]
  * power: disconnect signals from rr_screen (LP: #1508327)

  [ Mitsuya Shibata ]
  * unity-settings-daemon should initialize org.gnome.desktop.input-
sources for fcitx as same as ibus when sources property is empty.
(LP: #1465535)

  [ Sebastien Bacher ]
  * remove g_warning debug leftover
  * xsettings: disconnect signal from plugin_settings

 -- Sebastien Bacher   Thu, 29 Oct 2015 10:19:55
+

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

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

Title:
  ubiquity only mode: close/minimize/restore are on the right edge

Status in Release Notes for Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Wily:
  Fix Released

Bug description:
  [Impact]
  Unity settings daemon has a tendency to crash in ubiquity only install mode. 
The result is that close/minimize/restore are suddenly shifted to the right

  [Test Case]
  1. Start the live iso, choose the ubiquity-only installer mode.
  2. Wait for some screen, opens some ubuntu control center windows -> you may 
get a crash (reliably on some machines) in the 30s. This results visually in 
the decorations button shifting to the right.
  3. Install the u-s-d package from -proposed (with break=casper-bottom) on the 
live and then pursue to ubiquity starting.
  4. Redo the some operation then 2 -> no crash should happen

  [Regression potential]
  The crash only happened on certain machine and only at install time. The fix 
will be there mostly for the LTS install time then, but still can be useful for 
any derivatives which don't want that crash to happeN.

  Fresh image from 21/10/2015, downloaded this morning.
  Choose ubiquity only mode (here in French).

  First, the window decoration are on the left, but after you open any
  other windows (like the text entry from the keyboard indicator, or try
  to grab a screenshot), any modal dialog in ubiquity (like "apply those
  changes to disk") or additional windows started from indicators like
  text entry settings for keyboard have their window decoration controls
  shifted to the right (see pictures attached).

  Looking at unity-settings-daemon, it's  on the ps list.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 21 08:59:05 2015
  InstallationDate: Installed on 2012-05-28 (1240 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: ubiquity
  UpgradeStatus: Upgraded to wily on 2014-10-31 (354 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1508327/+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 1510824] Re: PolkitAgentSession incorrectly handles multiline output (as observed with pam_vas)

[Launchpad Bug Tracker]

This bug was fixed in the package policykit-1 - 0.105-8ubuntu5

---
policykit-1 (0.105-8ubuntu5) vivid; urgency=medium

  * Fix handling of multi-line helper output. (LP: #1510824)

 -- Dariusz Gadomski   Fri, 20 Nov 2015
15:30:03 +0100

** Changed in: policykit-1 (Ubuntu Vivid)
   Status: Fix Committed => Fix Released

** Changed in: policykit-1 (Ubuntu Wily)
   Status: Fix Committed => Fix Released

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

Title:
  PolkitAgentSession incorrectly handles multiline output (as observed
  with pam_vas)

Status in PolicyKit:
  Fix Released
Status in policykit-1 package in Ubuntu:
  Fix Released
Status in policykit-1 source package in Trusty:
  Fix Released
Status in policykit-1 source package in Vivid:
  Fix Released
Status in policykit-1 source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * Some PAM modules produce output of more than 1 line (e.g.
  PAM_TEXT_INFO may contain newlines in the message content). Polkit
  authentication agent is prepared to receive only single-line messages
  so it treats each line as a separate message. It fails to recognize
  the type of message for all of them except the first - hence failed
  authorization even if it was successful on the PAM-level.

   * The PAM specification does not require the modules to send only
  single-line messages. Thus, polkit needs to be fixed.

  * The helper component should escape (g_strescape) all messages before
  sending it up to the authentication agent. This way everything will be
  read as a single line and then unescaped to restore it's formatting
  with no changes required in PAM modules.

  [Test Case]

   * Use a pam module that returns a multi-line PAM_TEXT_INFO message on
  successful authentication (may require to artificially modify a pam
  module).

   * Perform a polkit authorization with e.g. pkexec ls

   * Correct authorization should end with a failure with an
  unrecognized PAM message

  [Regression Potential]

   * Fix makes advantage of the fact that polkit authentication agent
  already un-escapess (g_strcompress) all input from the helper
  component.

  * Fix is a backport of an upstream change.

  [Other Info]

   * Original bug description:

  There is an error observed when Ubuntu is configured to perform
  authentication via pam_vas (Vintela Authentication Services by Dell)
  in a disconnected mode (using cached authentication).

  Steps to reproduce:
  1. Configure pam_vas client authenticating to a remote server.
  2. Perform authentication to cache the credentials.
  3. Disconnect from the network where the server is reachable (to force using 
cached information).
  4. Perform an action requiring polkit authentication.

  Expected result:
  Authentication succeeds accompanied by the following message "You have logged 
in using cached account information.  Some network services will be 
unavailable".

  Actual result:
  Authentication fails accompanied by the following message "You have logged in 
using cached account information.  Some network services will be unavailable".

  Probable cause:
  The PolkitAgentSession part of polkit is designed to interpret only 1-line 
output, while interaction with pam_vas in the above scenario triggers helper to 
produce the following 2-line output:
  PAM_TEXT_INFO You have logged in using cached account information.  Some 
network services
  will be unavailable.

  The 'will be unavailable.' part is interpreted as an unknown message
  and causes failed authorization.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: policykit-1 0.105-4ubuntu2.14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-52.71~14.04.1-generic 3.16.7-ckt18
  Uname: Linux 3.16.0-52-generic x86_64
  NonfreeKernelModules: nvidia zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 28 09:01:37 2015
  InstallationDate: Installed on 2015-04-13 (197 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: policykit-1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1510824/+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 1274726] Re: Rhythmbox "Control" menu states that Control-Space controls play/pause, but actually Control-P is the shortcut

[Launchpad Bug Tracker]

This bug was fixed in the package rhythmbox - 3.2.1-1ubuntu3.1

---
rhythmbox (3.2.1-1ubuntu3.1) wily; urgency=medium

  * debian/patches/restore-traditional-menubar.patch:
- use correct keybinding label for play/pause (lp: #1274726)
  * debian/patches/git_sync_option.patch:
- don't have the sync option area having a 0 height (lp: #1513251)
  * debian/patches/git_sync_grid.patch:
- sync: replace the sync state GtkTable with a grid

 -- Sebastien Bacher   Thu, 05 Nov 2015 16:50:08
+0100

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

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

Title:
  Rhythmbox "Control" menu states that Control-Space controls
  play/pause, but actually Control-P is the shortcut

Status in Rhythmbox:
  Invalid
Status in rhythmbox package in Ubuntu:
  Fix Released
Status in rhythmbox source package in Wily:
  Fix Released

Bug description:
  * Impact
  the keybinding in the menu are wrong

  * Test case
  open the rhythmbox control menu and look at the keybinding associated to 
play/pause, it should be "control-P", check that action actually works

  * Regression potential
  the change is only a label change in the menu, check that it matches the 
control

To manage notifications about this bug go to:
https://bugs.launchpad.net/rhythmbox/+bug/1274726/+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 1510824] Re: PolkitAgentSession incorrectly handles multiline output (as observed with pam_vas)

[Launchpad Bug Tracker]

This bug was fixed in the package policykit-1 - 0.105-4ubuntu3.14.04.1

---
policykit-1 (0.105-4ubuntu3.14.04.1) trusty; urgency=medium

  * Fix handling of multi-line helper output. (LP: #1510824)

 -- Dariusz Gadomski   Fri, 20 Nov 2015
15:36:30 +0100

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

Title:
  PolkitAgentSession incorrectly handles multiline output (as observed
  with pam_vas)

Status in PolicyKit:
  Fix Released
Status in policykit-1 package in Ubuntu:
  Fix Released
Status in policykit-1 source package in Trusty:
  Fix Released
Status in policykit-1 source package in Vivid:
  Fix Released
Status in policykit-1 source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * Some PAM modules produce output of more than 1 line (e.g.
  PAM_TEXT_INFO may contain newlines in the message content). Polkit
  authentication agent is prepared to receive only single-line messages
  so it treats each line as a separate message. It fails to recognize
  the type of message for all of them except the first - hence failed
  authorization even if it was successful on the PAM-level.

   * The PAM specification does not require the modules to send only
  single-line messages. Thus, polkit needs to be fixed.

  * The helper component should escape (g_strescape) all messages before
  sending it up to the authentication agent. This way everything will be
  read as a single line and then unescaped to restore it's formatting
  with no changes required in PAM modules.

  [Test Case]

   * Use a pam module that returns a multi-line PAM_TEXT_INFO message on
  successful authentication (may require to artificially modify a pam
  module).

   * Perform a polkit authorization with e.g. pkexec ls

   * Correct authorization should end with a failure with an
  unrecognized PAM message

  [Regression Potential]

   * Fix makes advantage of the fact that polkit authentication agent
  already un-escapess (g_strcompress) all input from the helper
  component.

  * Fix is a backport of an upstream change.

  [Other Info]

   * Original bug description:

  There is an error observed when Ubuntu is configured to perform
  authentication via pam_vas (Vintela Authentication Services by Dell)
  in a disconnected mode (using cached authentication).

  Steps to reproduce:
  1. Configure pam_vas client authenticating to a remote server.
  2. Perform authentication to cache the credentials.
  3. Disconnect from the network where the server is reachable (to force using 
cached information).
  4. Perform an action requiring polkit authentication.

  Expected result:
  Authentication succeeds accompanied by the following message "You have logged 
in using cached account information.  Some network services will be 
unavailable".

  Actual result:
  Authentication fails accompanied by the following message "You have logged in 
using cached account information.  Some network services will be unavailable".

  Probable cause:
  The PolkitAgentSession part of polkit is designed to interpret only 1-line 
output, while interaction with pam_vas in the above scenario triggers helper to 
produce the following 2-line output:
  PAM_TEXT_INFO You have logged in using cached account information.  Some 
network services
  will be unavailable.

  The 'will be unavailable.' part is interpreted as an unknown message
  and causes failed authorization.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: policykit-1 0.105-4ubuntu2.14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-52.71~14.04.1-generic 3.16.7-ckt18
  Uname: Linux 3.16.0-52-generic x86_64
  NonfreeKernelModules: nvidia zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 28 09:01:37 2015
  InstallationDate: Installed on 2015-04-13 (197 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: policykit-1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1510824/+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 1508327] Update Released

[Chris J Arges]

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

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

Title:
  ubiquity only mode: close/minimize/restore are on the right edge

Status in Release Notes for Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Wily:
  Fix Released

Bug description:
  [Impact]
  Unity settings daemon has a tendency to crash in ubiquity only install mode. 
The result is that close/minimize/restore are suddenly shifted to the right

  [Test Case]
  1. Start the live iso, choose the ubiquity-only installer mode.
  2. Wait for some screen, opens some ubuntu control center windows -> you may 
get a crash (reliably on some machines) in the 30s. This results visually in 
the decorations button shifting to the right.
  3. Install the u-s-d package from -proposed (with break=casper-bottom) on the 
live and then pursue to ubiquity starting.
  4. Redo the some operation then 2 -> no crash should happen

  [Regression potential]
  The crash only happened on certain machine and only at install time. The fix 
will be there mostly for the LTS install time then, but still can be useful for 
any derivatives which don't want that crash to happeN.

  Fresh image from 21/10/2015, downloaded this morning.
  Choose ubiquity only mode (here in French).

  First, the window decoration are on the left, but after you open any
  other windows (like the text entry from the keyboard indicator, or try
  to grab a screenshot), any modal dialog in ubiquity (like "apply those
  changes to disk") or additional windows started from indicators like
  text entry settings for keyboard have their window decoration controls
  shifted to the right (see pictures attached).

  Looking at unity-settings-daemon, it's  on the ps list.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 21 08:59:05 2015
  InstallationDate: Installed on 2012-05-28 (1240 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: ubiquity
  UpgradeStatus: Upgraded to wily on 2014-10-31 (354 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1508327/+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 1465535] Re: The Chinese input method cannot be enabled in the installed system

[Launchpad Bug Tracker]

This bug was fixed in the package unity-settings-daemon -
15.04.1+15.10.20151029-0ubuntu1

---
unity-settings-daemon (15.04.1+15.10.20151029-0ubuntu1) wily; urgency=medium

  [ Lars Uebernickel ]
  * power: disconnect signals from rr_screen (LP: #1508327)

  [ Mitsuya Shibata ]
  * unity-settings-daemon should initialize org.gnome.desktop.input-
sources for fcitx as same as ibus when sources property is empty.
(LP: #1465535)

  [ Sebastien Bacher ]
  * remove g_warning debug leftover
  * xsettings: disconnect signal from plugin_settings

 -- Sebastien Bacher   Thu, 29 Oct 2015 10:19:55
+

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

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

Title:
  The Chinese input method cannot be enabled in the  installed system

Status in Ubuntu Kylin:
  New
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Wily:
  Fix Released

Bug description:
  * Impact
  The Chinese input method cannot be enabled in the  installed system. Live 
session is OK.

  * Test case
  Do a new install, try to enable chinese input

  * Regression potential
  Check that ibus and fcitx work as they should

  -

  Configuration:
  PC: HP-Pavilion-Sleekbook-15-PC
  OS: UK15.10-0614-Daily-amd64&i386

  The Chinese input method cannot be enabled in the  installed system.
  Live session is OK.

  安装后的系统无法启用中文输入法在系统进行中文输入。Live模式试用时，中文输入法可用。

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntukylin/+bug/1465535/+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 1465535] Update Released

[Chris J Arges]

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

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

Title:
  The Chinese input method cannot be enabled in the  installed system

Status in Ubuntu Kylin:
  New
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Wily:
  Fix Released

Bug description:
  * Impact
  The Chinese input method cannot be enabled in the  installed system. Live 
session is OK.

  * Test case
  Do a new install, try to enable chinese input

  * Regression potential
  Check that ibus and fcitx work as they should

  -

  Configuration:
  PC: HP-Pavilion-Sleekbook-15-PC
  OS: UK15.10-0614-Daily-amd64&i386

  The Chinese input method cannot be enabled in the  installed system.
  Live session is OK.

  安装后的系统无法启用中文输入法在系统进行中文输入。Live模式试用时，中文输入法可用。

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntukylin/+bug/1465535/+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 1274726] Update Released

[Chris J Arges]

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

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

Title:
  Rhythmbox "Control" menu states that Control-Space controls
  play/pause, but actually Control-P is the shortcut

Status in Rhythmbox:
  Invalid
Status in rhythmbox package in Ubuntu:
  Fix Released
Status in rhythmbox source package in Wily:
  Fix Released

Bug description:
  * Impact
  the keybinding in the menu are wrong

  * Test case
  open the rhythmbox control menu and look at the keybinding associated to 
play/pause, it should be "control-P", check that action actually works

  * Regression potential
  the change is only a label change in the menu, check that it matches the 
control

To manage notifications about this bug go to:
https://bugs.launchpad.net/rhythmbox/+bug/1274726/+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 1513251] Update Released

[Chris J Arges]

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

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

Title:
  Sync preferences not visible in device properties window

Status in Rhythmbox:
  Fix Released
Status in rhythmbox package in Ubuntu:
  Fix Released
Status in rhythmbox source package in Wily:
  Fix Released

Bug description:
  * Impact
  the Sync Preferences list tree box appears empty

  * Test Case
  - open rhythmbox
  - connect a device (phone, player, etc)
  - select it in the sidebar
  - click on the "properties" tab at the top of the screen
  - open the sync tab

  * Regression potential
  - check the layout of the sync dialog

  -

  After upgrading to wily the Sync Preferences list tree box appears
  empty. Resizing the window does not help. The same problem occurs when
  booting Ubuntu GNOME 15.10 from a live CD. The device I want to sync
  music to is an Ipod shuffle model xC323. I also tried resetting it to
  factory to no avail.

  I was expecting to see a list tree with my Music library on top and
  all my playlists as child nodes.

  The problem could in fact be a GTK problem, but I've only seen it in
  Rhythmbox so far.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: rhythmbox 3.2.1-1ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Nov  4 23:03:31 2015
  EcryptfsInUse: Yes
  SourcePackage: rhythmbox
  UpgradeStatus: Upgraded to wily on 2015-10-27 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/rhythmbox/+bug/1513251/+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 1175947] Update Released

[Chris J Arges]

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

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

Title:
  gvfs-copy --preserve doesn't work with MTP devices

Status in gvfs:
  Fix Released
Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs source package in Vivid:
  Fix Released

Bug description:
  [Impact]

  * When using gvfs-copy --preserve from a MTP device to local, the timestamp
is not preserved.

  * touch "localfile" --reference="MTP file" works OK.

  * I assume --preserve is not working.

  [Test Case]

  * Copy files from a MTP device using the --preserve option and check
timestamps.

  [Regression Potential]

  * Verify files copied from MTP devices and their attributes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1175947/+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 1175947] Re: gvfs-copy --preserve doesn't work with MTP devices

[Launchpad Bug Tracker]

This bug was fixed in the package gvfs - 1.24.2-0ubuntu0.1

---
gvfs (1.24.2-0ubuntu0.1) vivid; urgency=medium

  * New upstream version
- udisks2: Fix a crash when unmounting (lp: #1500516)
- mtp: Copy mtime when pulling (lp: #1175947)
- gvfs-open: Do not alter uris before use (lp: #1453174)

 -- Sebastien Bacher   Tue, 29 Sep 2015 11:48:31
+0200

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

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

Title:
  gvfs-copy --preserve doesn't work with MTP devices

Status in gvfs:
  Fix Released
Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs source package in Vivid:
  Fix Released

Bug description:
  [Impact]

  * When using gvfs-copy --preserve from a MTP device to local, the timestamp
is not preserved.

  * touch "localfile" --reference="MTP file" works OK.

  * I assume --preserve is not working.

  [Test Case]

  * Copy files from a MTP device using the --preserve option and check
timestamps.

  [Regression Potential]

  * Verify files copied from MTP devices and their attributes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1175947/+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 1500516] Re: /usr/lib/gvfs/gvfs-udisks2-volume-monitor:11:g_type_check_instance_cast:unmount_operation_is_eject:unmount_data_complete:unmount_cb:g_simple_async_result_complete

[Launchpad Bug Tracker]

This bug was fixed in the package gvfs - 1.24.2-0ubuntu0.1

---
gvfs (1.24.2-0ubuntu0.1) vivid; urgency=medium

  * New upstream version
- udisks2: Fix a crash when unmounting (lp: #1500516)
- mtp: Copy mtime when pulling (lp: #1175947)
- gvfs-open: Do not alter uris before use (lp: #1453174)

 -- Sebastien Bacher   Tue, 29 Sep 2015 11:48:31
+0200

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

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

Title:
  /usr/lib/gvfs/gvfs-udisks2-volume-
  
monitor:11:g_type_check_instance_cast:unmount_operation_is_eject:unmount_data_complete:unmount_cb:g_simple_async_result_complete

Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs source package in Vivid:
  Fix Released

Bug description:
  * Impact
  the gvfs disk monitors segfaults sometimes

  * Test case 
  no defined one, but the e.u.c reports should stop with the update

  * Regression potential
  check if disks and external storage devices are still correctly handled 
(listed in the launcher, included in nautilus, etc)

  -

  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gvfs.  This problem was most recently seen with version 1.24.1-1ubuntu1, the 
problem page at 
https://errors.ubuntu.com/problem/5d8e0bd14d691af888168ae3ff6a80e7fa95ebf4 
contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1500516/+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 1453174] Update Released

[Chris J Arges]

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

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

Title:
  Opening of magnet links broken

Status in gvfs:
  Unknown
Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs source package in Vivid:
  Fix Released

Bug description:
  * Impact
  some urls are not correctly handled

  * Test case
  $ xdg-open "magnet:?xt=urn:btih:9BE2..."

  that should open a working dialog and not an error one

  * Regression potential
  check that the desktop handling of urls is correct (using xdg-open or click 
on e.g in website handlers in about dialogs)

  ---

  When clicking on a magnet link, transmission-remote-gtk always
  displays the error "invalid or corrupt torrent file".  This seems to
  be caused by xdg-open slightly modifying the link:

  $ xdg-open "magnet:?xt=urn:btih:9BE2..."

  results in

  $ transmission-remote-gtk "magnet:///?xt=urn:btih:9BE2..."

  which causes the problem mentioned.

  I'm using transmission-remote-gtk 1.1.1-1 from vivid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1453174/+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 1500516] Update Released

[Chris J Arges]

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

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

Title:
  /usr/lib/gvfs/gvfs-udisks2-volume-
  
monitor:11:g_type_check_instance_cast:unmount_operation_is_eject:unmount_data_complete:unmount_cb:g_simple_async_result_complete

Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs source package in Vivid:
  Fix Released

Bug description:
  * Impact
  the gvfs disk monitors segfaults sometimes

  * Test case 
  no defined one, but the e.u.c reports should stop with the update

  * Regression potential
  check if disks and external storage devices are still correctly handled 
(listed in the launcher, included in nautilus, etc)

  -

  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gvfs.  This problem was most recently seen with version 1.24.1-1ubuntu1, the 
problem page at 
https://errors.ubuntu.com/problem/5d8e0bd14d691af888168ae3ff6a80e7fa95ebf4 
contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1500516/+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 1510824] Update Released

[Chris J Arges]

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

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

Title:
  PolkitAgentSession incorrectly handles multiline output (as observed
  with pam_vas)

Status in PolicyKit:
  Fix Released
Status in policykit-1 package in Ubuntu:
  Fix Released
Status in policykit-1 source package in Trusty:
  Fix Committed
Status in policykit-1 source package in Vivid:
  Fix Committed
Status in policykit-1 source package in Wily:
  Fix Committed

Bug description:
  [Impact]

   * Some PAM modules produce output of more than 1 line (e.g.
  PAM_TEXT_INFO may contain newlines in the message content). Polkit
  authentication agent is prepared to receive only single-line messages
  so it treats each line as a separate message. It fails to recognize
  the type of message for all of them except the first - hence failed
  authorization even if it was successful on the PAM-level.

   * The PAM specification does not require the modules to send only
  single-line messages. Thus, polkit needs to be fixed.

  * The helper component should escape (g_strescape) all messages before
  sending it up to the authentication agent. This way everything will be
  read as a single line and then unescaped to restore it's formatting
  with no changes required in PAM modules.

  [Test Case]

   * Use a pam module that returns a multi-line PAM_TEXT_INFO message on
  successful authentication (may require to artificially modify a pam
  module).

   * Perform a polkit authorization with e.g. pkexec ls

   * Correct authorization should end with a failure with an
  unrecognized PAM message

  [Regression Potential]

   * Fix makes advantage of the fact that polkit authentication agent
  already un-escapess (g_strcompress) all input from the helper
  component.

  * Fix is a backport of an upstream change.

  [Other Info]

   * Original bug description:

  There is an error observed when Ubuntu is configured to perform
  authentication via pam_vas (Vintela Authentication Services by Dell)
  in a disconnected mode (using cached authentication).

  Steps to reproduce:
  1. Configure pam_vas client authenticating to a remote server.
  2. Perform authentication to cache the credentials.
  3. Disconnect from the network where the server is reachable (to force using 
cached information).
  4. Perform an action requiring polkit authentication.

  Expected result:
  Authentication succeeds accompanied by the following message "You have logged 
in using cached account information.  Some network services will be 
unavailable".

  Actual result:
  Authentication fails accompanied by the following message "You have logged in 
using cached account information.  Some network services will be unavailable".

  Probable cause:
  The PolkitAgentSession part of polkit is designed to interpret only 1-line 
output, while interaction with pam_vas in the above scenario triggers helper to 
produce the following 2-line output:
  PAM_TEXT_INFO You have logged in using cached account information.  Some 
network services
  will be unavailable.

  The 'will be unavailable.' part is interpreted as an unknown message
  and causes failed authorization.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: policykit-1 0.105-4ubuntu2.14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-52.71~14.04.1-generic 3.16.7-ckt18
  Uname: Linux 3.16.0-52-generic x86_64
  NonfreeKernelModules: nvidia zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 28 09:01:37 2015
  InstallationDate: Installed on 2015-04-13 (197 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: policykit-1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1510824/+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 871133] Re: Volume Step not changeable in Unity and GNOME desktops

[HEXcube]

I'm attaching the @george-edison55 (Nathan Osman)'s patch to fix the bug
here. It's from Nathan Osman's PPA ppa:george-edison55/gnome-settings-
daemon - https://launchpad.net/~george-edison55/+archive/ubuntu/gnome-
settings-daemon . The PPA contains bugfixed gnome-settings-daemon and
unity-settings-daemon packages for Ubuntu 14.04LTS, 15.04 and 15.10. The
patch attached here is for gnome-settings-daemon v3.16.3 in Ubuntu 15.10
"Wily Werewolf".

** Patch added: "Add Volume Step setting for gnome-settings-daemon v3.16.3"
   
https://bugs.launchpad.net/gnome-settings-daemon/+bug/871133/+attachment/4528723/+files/add_volume-step_setting.patch

** Tags removed: oneiric running-unity
** Tags added: gnome3 trusty wily

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

Title:
  Volume Step not changeable in Unity and GNOME desktops

Status in gnome-settings-daemon:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Changing the volume step in gconf-editor does not do anything when adjusting 
the volume on a hardware dial.
  --- 
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  DistroRelease: Ubuntu 11.10
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
  Package: gnome-settings-daemon 3.2.0-0ubuntu5
  PackageArchitecture: i386
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Tags:  oneiric running-unity
  Uname: Linux 3.0.0-12-generic i686
  UpgradeStatus: Upgraded to oneiric on 2011-10-08 (3 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/871133/+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 1368756] Re: "recently used" files not correctly right-clickable

[Bug Watch Updater]

** Changed in: nautilus
   Status: Unknown => Invalid

** Changed in: nautilus
   Importance: Unknown => Medium

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

Title:
  "recently used" files not correctly right-clickable

Status in Nautilus:
  Invalid
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Right-click menu in nautilus' recently used only partially works
  correctly

  - open nautilus
  - click on "Recently used" ("Zuletzt verwendet")
  - right-click on a file
  -- choose: "E-Mail..." ...nothing happens (thunderbird should open)
  -- choose: "open with gedit" (if its a text file) ...it's opened with the 
preferred editor, geany in my case, but not with gedit
  -- choose: "open with" and "other application"("Anderer Anwendung...") 
depending on the ending, proposed applications are useful (*.txt, *.png) or not 
(e.g. *.js). Further more, the file name is not displayed but a reference/link 
(?): instead of "Choose an application to open >>myimage.png<<" (Wählen Sie 
eine Anwendung zum Öffnen von >>meinbild.png<<) I get:  "Choose an application 
to open >>8ac8fd07221e00.<<" (possibly that causes the problems??)

  System Information:

  uname -a
  Linux itspc34 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

  lsb_release -a
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  Codename: trusty

  apt-cache policy nautilus
  nautilus:
Installiert:   1:3.10.1-0ubuntu9.3
Installationskandidat: 1:3.10.1-0ubuntu9.3
Versionstabelle:
   *** 1:3.10.1-0ubuntu9.3 0
  500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.10.1-0ubuntu8 0
  500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1368756/+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 1336627] Re: libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so

[Launchpad Bug Tracker]

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

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

** Changed in: libva (Ubuntu)
   Status: New => Confirmed

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

Title:
  libva info: Trying to open /usr/lib/x86_64-linux-
  gnu/dri/radeonsi_drv_video.so

Status in libva package in Ubuntu:
  Confirmed

Bug description:
  libva tries to open the wrong VA-API driver on my AMD Kabini (which
  uses the "radeon" driver, not "radeonsi"):

  $ vainfo
  libva info: VA-API version 0.35.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
  libva info: va_openDriver() returns -1
  vaInitialize failed with error code -1 (unknown libva error),exit

  $ sudo ln -s vdpau_drv_video.so /usr/lib/x86_64-linux-
  gnu/dri/radeonsi_drv_video.so

  $ vainfo
  libva info: VA-API version 0.35.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
  libva info: Found init function __vaDriverInit_0_32
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.35 (libva 1.3.0)
  vainfo: Driver version: Splitted-Desktop Systems VDPAU backend for VA-API - 
0.7.3
  vainfo: Supported profile and entrypoints
  […]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libva/+bug/1336627/+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 871133] Re: Ubuntu Oneric Volume Step Can Not be Changed

[HEXcube]

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

** Summary changed:

- Ubuntu Oneric Volume Step Can Not be Changed
+ Volume Step not changeable in Unity and GNOME desktops

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

Title:
  Volume Step not changeable in Unity and GNOME desktops

Status in gnome-settings-daemon:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Changing the volume step in gconf-editor does not do anything when adjusting 
the volume on a hardware dial.
  --- 
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  DistroRelease: Ubuntu 11.10
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
  Package: gnome-settings-daemon 3.2.0-0ubuntu5
  PackageArchitecture: i386
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Tags:  oneiric running-unity
  Uname: Linux 3.0.0-12-generic i686
  UpgradeStatus: Upgraded to oneiric on 2011-10-08 (3 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/871133/+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 1397142] Re: Bluetooth headset play/pause key not fully effective in various media players

[Treviño]

** Changed in: unity
   Status: New => Invalid

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

Title:
  Bluetooth headset play/pause key not fully effective in various media
  players

Status in gnome-shell:
  New
Status in Unity:
  Invalid
Status in gnome-settings-daemon package in Ubuntu:
  New
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  UPDATE:
  Function GnomeGrabber::Impl::ActivateDBusAction dont emit dbus signal 
"AcceleratorActivated" if be pressed key with keycodes 208 or 215 (its 
XF86AudioPlay).

  Can be reproduce:
  run in one terminal 'dbus-monitor "path=/org/gnome/Shell"'
  and in other run 'xdotool key NUMBER'
  where NUMBER - keycodes. Can be check 172, 172, 209, bugged 208 and 215 and 
other.

  -
  I have a Sony SRS-BTM8 Bluetooth speaker, and its audio side works fairly 
well with Ubuntu.  It also has a play/pause button and that doesn't work so 
well.  I think the problem lies in unity-settings-daemon.

  To demonstrate that the Bluetooth side is working, if I switch to a
  text console and run "evtest /dev/input/event9", then when pressing
  the button I get events for KEY_PLAYCD if the speaker is not playing
  anything, and alternating KEY_PAUSECD and KEY_PLAYCD if it is playing
  something.

  However, within the Unity desktop I find that if I'm running Banshee
  or Rhythmbox then pressing the button successfully pauses the music,
  but doesn't start it playing again.  If I run "xev" and give it the
  keyboard focus while testing this (so xev sees all ungrabbed
  keystrokes) then it sees only a KeyRelease event for XF86AudioPause,
  but both KeyPress and KeyRelease events for XF86AudioPlay.  I've
  attached the full output from xev.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-settings-daemon 14.04.0+14.04.20140606-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7
  Uname: Linux 3.16.0-25-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Nov 27 23:43:01 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-motts-20100121-3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-06-09 (1632 days ago)
  InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 
20100121-21:52
  SourcePackage: unity-settings-daemon
  UpgradeStatus: Upgraded to trusty on 2014-08-15 (104 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1397142/+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 1397142] Re: Bluetooth headset play/pause key not fully effective in various media players

[Franchesko Salias Hudro Pedros]

** Description changed:

- I have a Sony SRS-BTM8 Bluetooth speaker, and its audio side works
- fairly well with Ubuntu.  It also has a play/pause button and that
- doesn't work so well.  I think the problem lies in unity-settings-
- daemon.
+ UPDATE:
+ Function GnomeGrabber::Impl::ActivateDBusAction dont emit dbus signal 
"AcceleratorActivated" if be pressed key with keycodes 208 or 215 (its 
XF86AudioPlay).
+ 
+ -
+ I have a Sony SRS-BTM8 Bluetooth speaker, and its audio side works fairly 
well with Ubuntu.  It also has a play/pause button and that doesn't work so 
well.  I think the problem lies in unity-settings-daemon.
  
  To demonstrate that the Bluetooth side is working, if I switch to a text
  console and run "evtest /dev/input/event9", then when pressing the
  button I get events for KEY_PLAYCD if the speaker is not playing
  anything, and alternating KEY_PAUSECD and KEY_PLAYCD if it is playing
  something.
  
  However, within the Unity desktop I find that if I'm running Banshee or
  Rhythmbox then pressing the button successfully pauses the music, but
  doesn't start it playing again.  If I run "xev" and give it the keyboard
  focus while testing this (so xev sees all ungrabbed keystrokes) then it
  sees only a KeyRelease event for XF86AudioPause, but both KeyPress and
  KeyRelease events for XF86AudioPlay.  I've attached the full output from
  xev.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-settings-daemon 14.04.0+14.04.20140606-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7
  Uname: Linux 3.16.0-25-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Nov 27 23:43:01 2014
  DistributionChannelDescriptor:
-  # This is a distribution channel descriptor
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-motts-20100121-3
+  # This is a distribution channel descriptor
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-motts-20100121-3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-06-09 (1632 days ago)
  InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 
20100121-21:52
  SourcePackage: unity-settings-daemon
  UpgradeStatus: Upgraded to trusty on 2014-08-15 (104 days ago)

** Description changed:

  UPDATE:
  Function GnomeGrabber::Impl::ActivateDBusAction dont emit dbus signal 
"AcceleratorActivated" if be pressed key with keycodes 208 or 215 (its 
XF86AudioPlay).
+ 
+ Can be reproduce:
+ run in one terminal 'dbus-monitor "path=/org/gnome/Shell"'
+ and in other run 'xdotool key NUMBER'
+ where NUMBER - keycodes. Can be check 172, 172, 209, bugged 208 and 215 and 
other.
  
  -
  I have a Sony SRS-BTM8 Bluetooth speaker, and its audio side works fairly 
well with Ubuntu.  It also has a play/pause button and that doesn't work so 
well.  I think the problem lies in unity-settings-daemon.
  
  To demonstrate that the Bluetooth side is working, if I switch to a text
  console and run "evtest /dev/input/event9", then when pressing the
  button I get events for KEY_PLAYCD if the speaker is not playing
  anything, and alternating KEY_PAUSECD and KEY_PLAYCD if it is playing
  something.
  
  However, within the Unity desktop I find that if I'm running Banshee or
  Rhythmbox then pressing the button successfully pauses the music, but
  doesn't start it playing again.  If I run "xev" and give it the keyboard
  focus while testing this (so xev sees all ungrabbed keystrokes) then it
  sees only a KeyRelease event for XF86AudioPause, but both KeyPress and
  KeyRelease events for XF86AudioPlay.  I've attached the full output from
  xev.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-settings-daemon 14.04.0+14.04.20140606-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7
  Uname: Linux 3.16.0-25-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Nov 27 23:43:01 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-motts-20100121-3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-06-09 (1632 days ago)
  InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 
20100121-21:52
  SourcePackage: unity-settings-daemon
  UpgradeStatus: Upgraded to trusty on 2014-08-15 (104 days ago)

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

Title:
  Bluetooth headset play/pause key not fully effective in various media
  players

Status in gnome-shell:
  New
Stat

[Desktop-packages] [Bug 1518021]

[Chris Wilson]

Hmm, that doesn't even closely match upstream. What is the corresponding
source? Or probably better just to check with upstream first.

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

Title:
  
/usr/bin/Xorg:6:sna_dri2_event_free:sna_dri2_schedule_flip:sna_dri2_schedule_swap:DRI2SwapBuffers:ProcDRI2SwapBuffers

Status in xf86-video-intel:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  This occurs on my shiny new Lenovo Thinkpad T540p.

  I have my laptop docked in a Lenovo UltraDock running two external
  1080p displays.

  When I'm logged in, if I un-dock the laptop I get booted back out to
  the login screen (i.e.- X crashes). This seems to happen about 90% of
  the time, so it's reasonably easy to reproduce.

  In order to try and reproduce this, I installed the X server -dbg
  packages. However, with the -dbg packages installed I can't seem to
  reproduce this  any more (possibly a race condition?).

  ---

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding xorg-server.  This problem was most recently seen with
  version 2:1.17.2-1ubuntu9, the problem page at
  https://errors.ubuntu.com/problem/e58accb723690ba7801e7f3fbc9bc637f08e8641
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1518021/+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 1518021]

[Robert Ancell]

Created attachment 120199
Stacktrace.

Sorry, I guess you need an account to view it on errors.ubuntu.com.

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

Title:
  
/usr/bin/Xorg:6:sna_dri2_event_free:sna_dri2_schedule_flip:sna_dri2_schedule_swap:DRI2SwapBuffers:ProcDRI2SwapBuffers

Status in xf86-video-intel:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  This occurs on my shiny new Lenovo Thinkpad T540p.

  I have my laptop docked in a Lenovo UltraDock running two external
  1080p displays.

  When I'm logged in, if I un-dock the laptop I get booted back out to
  the login screen (i.e.- X crashes). This seems to happen about 90% of
  the time, so it's reasonably easy to reproduce.

  In order to try and reproduce this, I installed the X server -dbg
  packages. However, with the -dbg packages installed I can't seem to
  reproduce this  any more (possibly a race condition?).

  ---

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding xorg-server.  This problem was most recently seen with
  version 2:1.17.2-1ubuntu9, the problem page at
  https://errors.ubuntu.com/problem/e58accb723690ba7801e7f3fbc9bc637f08e8641
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1518021/+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 1397142] Re: Bluetooth headset play/pause key not fully effective in various media players

[Franchesko Salias Hudro Pedros]

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

** Tags added: amd64 wily

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

** Also affects: gnome-shell
   Importance: Undecided
   Status: New

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

Title:
  Bluetooth headset play/pause key not fully effective in various media
  players

Status in gnome-shell:
  New
Status in Unity:
  New
Status in gnome-settings-daemon package in Ubuntu:
  New
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  I have a Sony SRS-BTM8 Bluetooth speaker, and its audio side works
  fairly well with Ubuntu.  It also has a play/pause button and that
  doesn't work so well.  I think the problem lies in unity-settings-
  daemon.

  To demonstrate that the Bluetooth side is working, if I switch to a
  text console and run "evtest /dev/input/event9", then when pressing
  the button I get events for KEY_PLAYCD if the speaker is not playing
  anything, and alternating KEY_PAUSECD and KEY_PLAYCD if it is playing
  something.

  However, within the Unity desktop I find that if I'm running Banshee
  or Rhythmbox then pressing the button successfully pauses the music,
  but doesn't start it playing again.  If I run "xev" and give it the
  keyboard focus while testing this (so xev sees all ungrabbed
  keystrokes) then it sees only a KeyRelease event for XF86AudioPause,
  but both KeyPress and KeyRelease events for XF86AudioPlay.  I've
  attached the full output from xev.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-settings-daemon 14.04.0+14.04.20140606-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7
  Uname: Linux 3.16.0-25-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Nov 27 23:43:01 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-motts-20100121-3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-06-09 (1632 days ago)
  InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 
20100121-21:52
  SourcePackage: unity-settings-daemon
  UpgradeStatus: Upgraded to trusty on 2014-08-15 (104 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1397142/+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 1503168] Re: [Dell Inspiron 5551][8086:0f31] Unable to adjust brightness

[Anthony Wong]

I am confused, this bug is about brightness, but you mentioned wireless
hotkey in the last comments.

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

Title:
  [Dell Inspiron 5551][8086:0f31] Unable to adjust brightness

Status in HWE Next:
  Incomplete
Status in xorg package in Ubuntu:
  New

Bug description:
  Failed to adjust brightness.

  Unable to change brightness with hotkeys or even system settings.

  Additional information:
  There are two backlight interfaces and the system seems to use the wrong one.
  /sys/class/backlight$ ls
  acpi_video0  intel_backlight

  Following commands proof that intel interfaces can controll the backlight:
  sudo sh -c "echo 2500 >> /sys/class/backlight/intel_backlight/brightness"


  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26
  Uname: Linux 3.13.0-65-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.15
  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
  Date: Tue Oct  6 15:25:21 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0e) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Device [1028:06d7]
  InstallationDate: Installed on 2015-10-05 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Inspiron 5551
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic.efi.signed 
root=UUID=2e69c3f8-b60b-4e26-beed-33717212e1e9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X16
  dmi.board.asset.tag: AFTPASS
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: AFTPASS
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: X16
  dmi.modalias: 
dmi:bvnDellInc.:bvrX16:bd01/28/2015:svnDellInc.:pnInspiron5551:pvrX16:rvnDellInc.:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnDellInc.:ct8:cvrX16:
  dmi.product.name: Inspiron 5551
  dmi.product.version: X16
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Oct  6 14:20:56 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5100
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu2.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1503168/+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 1359211] Re: Mouse cursor tiny when hovering unity elements in high DPI mode

[Treviño]

** Also affects: unity/7.3
   Importance: Undecided
   Status: New

** Changed in: unity/7.3
   Status: New => In Progress

** Changed in: unity/7.3
   Importance: Undecided => Medium

** Changed in: unity/7.3
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: unity/7.3
Milestone: None => 7.3.4

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

Title:
  Mouse cursor tiny when hovering unity elements in high DPI mode

Status in Compiz:
  Fix Committed
Status in Unity:
  Fix Committed
Status in Unity 7.3 series:
  In Progress
Status in compiz package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released

Bug description:
  On a high DPI screen (220 DPI) the mouse cursor is really tiny when
  hovering unity elements. There are various keys in dconf to change the
  cursor's scale factor or size. I've managed to change it in a way that
  it looks normal when inside application windows, but its still tiny
  when on unity elements.

  I think this should be set automatically by the scale factor setting
  in system settings.

  
  (Using unity 7.3.1+14.10.20140811-0ubuntu1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1359211/+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 1359211] Re: Mouse cursor tiny when hovering unity elements in high DPI mode

[Launchpad Bug Tracker]

** Branch linked: lp:~3v1n0/compiz/wily-cursors-update-and-cache

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

Title:
  Mouse cursor tiny when hovering unity elements in high DPI mode

Status in Compiz:
  Fix Committed
Status in Unity:
  Fix Committed
Status in Unity 7.3 series:
  New
Status in compiz package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released

Bug description:
  On a high DPI screen (220 DPI) the mouse cursor is really tiny when
  hovering unity elements. There are various keys in dconf to change the
  cursor's scale factor or size. I've managed to change it in a way that
  it looks normal when inside application windows, but its still tiny
  when on unity elements.

  I think this should be set automatically by the scale factor setting
  in system settings.

  
  (Using unity 7.3.1+14.10.20140811-0ubuntu1)

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