[Desktop-packages] [Bug 1179180] Re: Impossible to open Empathy contact list window if already started with '-h' option

2015-02-06 Thread Jan Kaláb
Hey, here is patch: https://bug729282.bugzilla-
attachments.gnome.org/attachment.cgi?id=294177

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

Title:
  Impossible to open Empathy contact list window if already started with
  '-h' option

Status in Chat app, and Telepathy user interface:
  New
Status in empathy package in Ubuntu:
  Confirmed

Bug description:
  If I add Empathy to 'Startup Applications' to start it with '-h'
  option, I'll never be able to open the contact list window.

  Tried:
  - If query with 'ps -ef | grep emapthy', I can see empathy is running.
  - If run 'empathy' from command line, the command exits without any output, 
but nothing happens after that.
  - If choose 'Empathy Internet Messaging' from Unity Dashboard, nothing 
happens.
  - If choose from the locked lens, I can see the icon blinks slowly (if you 
know what I mean, I'm not native speaker of English), and then it stops 
blinking, nothing happens after that.

  However, if I didn't start Empathy with '-h' option, everything seems
  normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: empathy 3.6.4-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 12 18:27:52 2013
  InstallationDate: Installed on 2012-08-12 (273 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: empathy
  UpgradeStatus: Upgraded to raring on 2013-04-26 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/empathy/+bug/1179180/+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 1179180] Re: Impossible to open Empathy contact list window if already started with '-h' option

2015-02-06 Thread Jan Kaláb
Also still in Utopic. :(

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

Title:
  Impossible to open Empathy contact list window if already started with
  '-h' option

Status in Chat app, and Telepathy user interface:
  New
Status in empathy package in Ubuntu:
  Confirmed

Bug description:
  If I add Empathy to 'Startup Applications' to start it with '-h'
  option, I'll never be able to open the contact list window.

  Tried:
  - If query with 'ps -ef | grep emapthy', I can see empathy is running.
  - If run 'empathy' from command line, the command exits without any output, 
but nothing happens after that.
  - If choose 'Empathy Internet Messaging' from Unity Dashboard, nothing 
happens.
  - If choose from the locked lens, I can see the icon blinks slowly (if you 
know what I mean, I'm not native speaker of English), and then it stops 
blinking, nothing happens after that.

  However, if I didn't start Empathy with '-h' option, everything seems
  normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: empathy 3.6.4-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 12 18:27:52 2013
  InstallationDate: Installed on 2012-08-12 (273 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: empathy
  UpgradeStatus: Upgraded to raring on 2013-04-26 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/empathy/+bug/1179180/+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 1324693] Re: Hang on import of pdf files

2015-02-06 Thread jazzynico
** Changed in: inkscape
   Importance: Undecided = High

** Tags removed: critical hang import
** Tags added: crash importing

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

Title:
  Hang on import of pdf files

Status in Inkscape: A Vector Drawing Tool:
  New
Status in inkscape package in Ubuntu:
  New

Bug description:
  Inkcsapce daily build (ppa) installed on Kubuntu 12.04 hangs evrytime
  while importing a pdf file. It does not depend on the file and the
  dialog to preview the file is not opened. The program just frezes.

  The output on the terminal is:
  (inkscape:3367): Gtk-CRITICAL **: IA__gtk_widget_get_visible: assertion 
`GTK_IS_WIDGET (widget)' failed

  I have poppler .26 installed (self compiled) and okular, kile (live
  preview of pdf), Scribus and GIMP (import pdf) working fine.

  I cant even compile inkscape with poppler 0.26 and I get a lot of
  errors (but this is not the same bug I think).

  Thanks for helping...

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1324693/+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 1342271] Re: lpq has long hang before completion.

2015-02-06 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: cups (Ubuntu)
   Status: New = Confirmed

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

Title:
  lpq has long hang before completion.

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 12.04 does not have this long hang issue.

  See attached straces - one from a machine with 12.04 and one to the
  same remote cups server using a 14.04 client.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups-client 1.7.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Tue Jul 15 14:26:40 2014
  InstallationDate: Installed on 2014-06-18 (27 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-30-generic 
root=UUID=a86d2294-0ef2-4c23-b951-ea3199bad7e7 ro rootflags=subvol=@ quiet 
splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2202
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 LE R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2202:bd12/12/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1342271/+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 1418827] Re: The update of ubuntu 13.04 to 13.10 on a UEFI system failed. Ubuntu is dual booted with Windows 8.

2015-02-06 Thread Ubuntu Foundations Team Bug Bot
** Attachment removed: VarLogDistupgradeTermlog.gz
   
https://bugs.launchpad.net/bugs/1418827/+attachment/4313695/+files/VarLogDistupgradeTermlog.gz

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

Title:
  The update of ubuntu 13.04 to 13.10 on a UEFI system failed. Ubuntu is
  dual booted with Windows 8.

Status in tex-common package in Ubuntu:
  New

Bug description:
  no idea

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: tex-common 4.04
  ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13
  Uname: Linux 3.8.0-35-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Fri Feb  6 00:27:48 2015
  DuplicateSignature: package:tex-common:4.04:ErrorMessage: subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: ErrorMessage: subprocess installed post-installation script 
returned error exit status 1
  InstallationDate: Installed on 2013-07-26 (560 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: tex-common
  Title: package tex-common 4.04 failed to install/upgrade: ErrorMessage: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to saucy on 2015-02-05 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1418827/+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 1418424] Re: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4: nvidia-331-updates-uvm kernel module failed to build

2015-02-06 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1373136 ***
https://bugs.launchpad.net/bugs/1373136

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


** This bug has been marked a duplicate of bug 1373136
   nvidia-331-uvm 331.38-0ubuntu7.1: nvidia-331-uvm kernel module failed to 
build [nvidia-modules-common.mk: No such file or directory]

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1418424

Title:
  nvidia-331-updates-uvm 331.113-0ubuntu0.0.4: nvidia-331-updates-uvm
  kernel module failed to build

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  New

Bug description:
  it failed to download and install.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic i686
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: i386
  DKMSBuildLog:
   DKMS make.log for nvidia-331-updates-uvm-331.113 for kernel 
3.13.0-45-generic (i686)
   Thu Feb  5 00:03:11 GET 2015
   Makefile:216: 
/var/lib/dkms/nvidia-331-updates/331.113/build/nvidia-modules-common.mk: No 
such file or directory
   make: *** No rule to make target 
`/var/lib/dkms/nvidia-331-updates/331.113/build/nvidia-modules-common.mk'.  
Stop.
  DKMSKernelVersion: 3.13.0-45-generic
  Date: Thu Feb  5 00:03:35 2015
  InstallationDate: Installed on 2014-12-21 (45 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 
(20140722.2)
  PackageVersion: 331.113-0ubuntu0.0.4
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates-uvm 331.113-0ubuntu0.0.4: nvidia-331-updates-uvm 
kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1418424/+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 1418746] Re: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build

2015-02-06 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1268257 ***
https://bugs.launchpad.net/bugs/1268257

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


** This bug has been marked a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with only error: objdump: '... .tmp_nv.o': No such file

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

Title:
  nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to
  build

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  New

Bug description:
  on startup

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: i386
  DKMSKernelVersion: 3.13.0-45-generic
  Date: Thu Feb  5 22:46:30 2015
  InstallationDate: Installed on 2005-01-01 (3687 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  PackageVersion: 331.113-0ubuntu0.0.4
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to 
build
  UpgradeStatus: Upgraded to trusty on 2014-08-12 (177 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1418746/+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 1418827] Re: The update of ubuntu 13.04 to 13.10 on a UEFI system failed. Ubuntu is dual booted with Windows 8.

2015-02-06 Thread Apport retracing service
*** This bug is a duplicate of bug 1236951 ***
https://bugs.launchpad.net/bugs/1236951

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1236951
   package tex-common 4.04 failed to install/upgrade: ErrorMessage: subprocess 
installed post-installation script returned error exit status 1

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

Title:
  The update of ubuntu 13.04 to 13.10 on a UEFI system failed. Ubuntu is
  dual booted with Windows 8.

Status in tex-common package in Ubuntu:
  New

Bug description:
  no idea

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: tex-common 4.04
  ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13
  Uname: Linux 3.8.0-35-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Fri Feb  6 00:27:48 2015
  DuplicateSignature: package:tex-common:4.04:ErrorMessage: subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: ErrorMessage: subprocess installed post-installation script 
returned error exit status 1
  InstallationDate: Installed on 2013-07-26 (560 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: tex-common
  Title: package tex-common 4.04 failed to install/upgrade: ErrorMessage: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to saucy on 2015-02-05 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1418827/+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 1414999] Re: double free in mir egl display when calling eglTerminate and gbm_device_destroy

2015-02-06 Thread Daniel van Vugt
** Changed in: mir
Milestone: None = 0.12.0

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

Title:
  double free in mir egl display when calling eglTerminate and
  gbm_device_destroy

Status in Mir:
  New
Status in mesa package in Ubuntu:
  New
Status in mir package in Ubuntu:
  New

Bug description:
  In my standalone Xmir I do the following things:

  /* Init code */
  if (xmir_screen-gbm) /* NULL on !mesa */
  mir_connection_drm_set_gbm_device(xmir_screen-conn, xmir_screen-gbm);

  xmir_screen-egl_display =
  eglGetDisplay(mir_connection_get_egl_native_display(xmir_screen-conn));

  /* Shutdown code */
  eglTerminate(xmir_screen-egl_display);

  if (xmir_screen-gbm)
  gbm_device_destroy(xmir_screen-gbm);

  This works as expected when gbm is NULL, but I'm getting a double free in 
gbm_device_destroy with the eglTerminate.
  Calling eglGetDisplay(xmir_screen-gbm) instead works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1414999/+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 1364025] Re: system-config-printer fails with cups-client talking to cups 1.3 server

2015-02-06 Thread ubuntu-tester
system-config-printer-gnome 1.4.3+20140219-0ubuntu2.5
python-cups 1.9.66-0ubuntu2
libcups2 1.7.2-0ubuntu1.2

I use 1.7.2 CUPS clients with a 1.4.2 CUPS server.

To access to print menu in any applications, it was very slow (about 2
minutes), I have configured the version=1.1 option in /etc/cups
client.conf, and now all works fine except system-config-printer so it
may confirm that it doesn't respect  the version=1.1 option in
client.conf and still use IPP 2.0.

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

Title:
  system-config-printer fails with cups-client talking to cups 1.3
  server

Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  system-config-printer-gnome version 1.4.3+20140219-0ubuntu2.1
  python-cups version 1.9.66-0ubuntu2
  libcups2 version 1.7.2-0ubuntu1.1

  I have my systems configured to talk to a cups 1.3 server, which only
  speaks IPP 1.1, so I have in /etc/cups/client.conf:

  ServerName cups-serv.example.com/version=1.1

  ...and printing from applications and the command line works fine.

  When I run system-config-printer, all the printers are shown in a
  dialogue box, but attempting to refresh the dialogue box or perform
  any operation on any of the printer icons in the box produces an error
  box saying:

  CUPS server error

  There was an error during the CUPS operation: 'Bad Request'.

  
  Viewing the network traffic with wireshark I see that system-config-printer 
is making some requests with IPP version 2.0, and it is these requests which 
the CUPS server is objecting to.  system-config-printer (or perhaps the python 
CUPS libraries it uses, or perhaps the underlying C CUPS API) should respect 
the version=1.1 option in client.conf.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1364025/+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 222208]

2015-02-06 Thread Rkent-3
Re Postbox: In the Thunderbird dev cycle, we will accept changes that
result in failures if users run a modern Thunderbird, and then downgrade
to a version of Thunderbird prior to Thunderbird 17. Postbox branched
from Thunderbird prior to version 3, and it is unknown how much
functionality they have backported. So I would not automatically assume
that you could run Thunderbird, then run the same profile on Postbox.

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

Title:
  user-id and password not sent automatically for rss-feed

Status in Mozilla Thunderbird Mail and News:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: thunderbird

  This is a bug I have seen for quite some time.  I am in the make
  hardy the best release there ever was-mood today and have brought
  myself to really reporting every single bit of problem I have put off
  for so long so somebody with the needed skills has a chance to fix it.

  I subscribe to an RSS feed hosted on a password-protected https-site
  in Thunderbird.  TB works fine but periodically asks me for the
  password although I have marked save password with password manager
  in the dialog.  In fact, the necessary fields are displayed filled in,
  but the pop-up comes back to me from time to time and I have to hit
  the OK button.

  I have set up a test installation which is exactly the same as the one
  I am having problems with at https://clients.leggewie.biz/tester/.
  The ssl-certificate is from cacert.org, so your browser might throw
  that up at first.  The user you need to get in is tb-tester and the
  password is launchpad.  The RSS feed is at
  
https://clients.leggewie.biz/tester/index.php?title=Special:Recentchangesfeed=rss
  When you susbscribe to that in TB and save the login credentials, you
  should have TB nagging you from time to time to with a login screen.

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

2015-02-06 Thread Neil-httl
(In reply to Joshua Cranmer from comment #118)
  +  from = MimeHeaders_get(mdd-headers, HEADER_FROM, false, false);
 
 This hunk seems unnecessary?

I accidentally already checked it in without review, so this is post-
facto review, so to speak.

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

Title:
  Editing the From field for the current email only (as text, not
  dropdown)

Status in Mozilla Thunderbird Mail and News:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: thunderbird

  I want to quite often use a particular email address (e.g. for writing
  to a mailing list), where I do not have added the email address to the
  account settings yet.

  However, Thunderbird does not allow to edit the From field, but only
  provides the configured email addresses in a dropdown.

  It would be nice, if you could also edit the From field in a text
  input.

  KMail provides this, for example, and there appear to be some
  extensions for it, but I'd like to avoid using an addon for this, but
  rather think it's a nice feature to have by default.

  I could imagine, that the last entry in the dropdown would say
  Edit... or Custom... and change the dropdown into a text field.

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  NonfreeKernelModules: nvidia
  Package: mozilla-thunderbird 2.0.0.21+nobinonly-0ubuntu1
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: thunderbird
  Uname: Linux 2.6.28-11-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/357864/+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 778054] Re: Packages shouldn't depend on the transitional package python-gobject

2015-02-06 Thread Mathew Hodson
** Summary changed:

- Trouble when removing transitional packages
+ Packages shouldn't depend on the transitional package python-gobject

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

Title:
  Packages shouldn't depend on the transitional package python-gobject

Status in aptdaemon package in Ubuntu:
  Fix Released
Status in desktopcouch package in Ubuntu:
  Invalid
Status in eglibc package in Ubuntu:
  Invalid
Status in gnome-utils package in Ubuntu:
  Invalid
Status in libreoffice package in Ubuntu:
  Fix Released
Status in openoffice.org package in Ubuntu:
  Won't Fix
Status in system-config-printer package in Ubuntu:
  Fix Released
Status in wine1.4 package in Ubuntu:
  Fix Released
Status in zeitgeist package in Ubuntu:
  In Progress
Status in aptdaemon source package in Trusty:
  Fix Released
Status in desktopcouch source package in Trusty:
  Invalid
Status in eglibc source package in Trusty:
  Invalid
Status in gnome-utils source package in Trusty:
  Invalid
Status in libreoffice source package in Trusty:
  Fix Released
Status in openoffice.org source package in Trusty:
  Invalid
Status in system-config-printer source package in Trusty:
  Fix Released
Status in wine1.4 source package in Trusty:
  Invalid
Status in zeitgeist source package in Trusty:
  In Progress

Bug description:
  [Impact]

  python-zeitgeist depends on python-gobject, which means python-gobject
  cannot be removed from the system. python-gobject is a transitional
  package, and packages should be updated to no longer depend on it.

  [Test Case]

  * Install python-zeitgeist, and verify that python-gobject is not
  installed with it.

  * If it is already installed, you should be able to run 'apt-get purge
  python-gobject' without removing python-zeitgeist.

  [Regression Potential]

  Negligible. There are no code changes. The fix only removes a
  dependency on a transitional package that doesn't provide any files.

  ---

  [Impact]

  system-config-printer-gnome depends on python-gobject, which means
  python-gobject cannot be removed from the system. python-gobject is a
  transitional package, and packages should be updated to no longer
  depend on it.

  [Test Case]

  * Install system-config-printer-gnome, and verify that python-gobject
  is not installed with it.

  * If it is already installed, you should be able to run 'apt-get purge
  python-gobject' without removing system-config-printer-gnome.

  [Regression Potential]

  Negligible. There are no code changes. The fix only removes a
  dependency on a transitional package that doesn't provide any files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/778054/+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 970844] Re: Session off center when starting

2015-02-06 Thread jshanks
Hasn't been any activity recently?  Has anyone tried to fix it?  I can
confirm that it happens 100% of the time on Ubuntu 14.04 LTS using both
RDP and VNC remotes.

Start Remmina, connect to remote PC with RDP or VNC.  The remote screen
starts off center.  Have to manually center the screen to view the
remote.

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

Title:
  Session off center when starting

Status in remmina package in Ubuntu:
  Incomplete

Bug description:
  When Initially starting a saved machine the session is offcenter (see
  screenshot)

  A maximise and restore re-centers it

  This is repeatable.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: remmina 1.0.0-1ubuntu5
  ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
  Uname: Linux 3.2.0-21-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0-0ubuntu2
  Architecture: amd64
  CheckboxSubmission: af9307c19616fbaba8ec60ff67c8c56e
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Mon Apr  2 02:24:00 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301)
  ProcEnviron:
   LANGUAGE=en_NZ:en
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: remmina
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/970844/+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 1416794] Re: Can't mount exFAT on Ubuntu 14.10

2015-02-06 Thread unrud
I've traced the problem to udev.
The ID_FS_* properties are missing from the udev device.
udisks2 uses the ID_FS_TYPE property to determine the filesystem type.

** Package changed: udisks2 (Ubuntu) = udev (Ubuntu)

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

Title:
  Can't mount exFAT on Ubuntu 14.10

Status in udev package in Ubuntu:
  New

Bug description:
  I've installed the packages exfat-fuse and exfat-utils but I can't mount 
exFAT filesystems through udisks2.
  $ udisksctl mount --block-device /dev/sdb1
  Object /org/freedesktop/UDisks2/block_devices/sdb1 is not a mountable 
filesystem.

  Mounting with
  $ sudo mount /dev/sdb1 ...
  works fine.

  It works fine on Ubuntu 14.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1416794/+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 1153488] Re: Treats bluetooth input device batteries as batteries

2015-02-06 Thread redman
@Shih-Yuan Lee
Is your patch included in Ubuntu 14.10?

Because I did not install it manually

Screenshot attached

** Attachment added: battery.png
   
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1153488/+attachment/4313971/+files/battery.png

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

Title:
  Treats bluetooth input device batteries as batteries

Status in gnome-power-manager package in Ubuntu:
  Invalid
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-power-manager source package in Precise:
  Invalid
Status in upower source package in Precise:
  Fix Released
Status in gnome-power-manager source package in Quantal:
  Invalid
Status in upower source package in Quantal:
  Won't Fix
Status in gnome-power-manager source package in Raring:
  Invalid
Status in upower source package in Raring:
  Fix Released
Status in gnome-power-manager source package in Saucy:
  Invalid
Status in upower source package in Saucy:
  Fix Released

Bug description:
  [Impact]

   * There are many Bluetooth devices with battery information inside.
  When they are treated as system battery, it will make the system
  poweroff/suspend/hibernate when some Bluetooth device has critical low
  battery. It is a very annoying behavior for the users. Originally,
  there is no such Bluetooth battery information until Ubuntu 12.04
  brings linux-quantal-lts and linux-raring-lts, so those linux kernels
  also bring this issue.

  [Test Case]

   * Pair some Bluetooth devices, such as Apple Wireless Mouse or Apple 
Wireless Keyboard.
   * Click the power indicator and you can find Apple Wireless Mouse is listed 
as system battery, and there is no Apple Wireless Keyboard. If you open 
gnome-power-statistics, you can find the 'Supply' field of Apple Wireless Mouse 
is 'Yes' but it should not be.

  [Regression Potential]

   * There is no obvious regression as I know.

  [Other Info]

   * Most patches are from upstream, modified to fix the conflicts, and made by 
the same developer (i.e. fourdollars).
   * We need another patch from 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d0a934b764c67b4bf626f5b7cf725a6e3066afd2
 to make Apple Wireless Keyboard showing.

  [Original Bug Description]

  This is a weird one... the system is an HP Pavilion 23 All In One and
  is powered by a large power supply brick.

  I currently have an Apple Magic Mouse connected via Bluetooth.  As
  soon as the mouse is connected, the Battery indicator shows up and
  clicking on that shows that the system is reading my mouse as a
  battery!

  See the attached screen shot for what I see in the Power status.

  Looking at hcitool:
  ubuntu@201206-11396:~$ hcitool dev
  Devices:
   hci0 9C:B7:0D:80:71:DB

  To make matters even more weird, I actually observed the battery
  indicator go from full to Critically Low and the system suspended
  itself.  Keep in mind, again, that this system has NO battery, it's
  reading my bluetooth mouse as a battery device.

  I disconnected the magic mouse and the battery indicator went to Empty
  Red outline and status showed Battery Disconnected.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1
  ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic x86_64
  NonfreeKernelModules: wl fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC 
Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC 
Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1726 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb4 irq 16'
     Mixer name : 'Realtek ALC269VC'
     Components : 'HDA:10ec0269,103c2aee,00100202'
     Controls  : 21
     Simple ctrls  : 10
  Date: Mon Mar 11 03:54:36 2013
  HibernationDevice: RESUME=UUID=ccd7a21f-7a71-4fa5-b95d-e2898c3dae24
  InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 
(20130213)
  MachineType: Hewlett-Packard a654
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic 
root=UUID=e2a5f4ae-dfa2-40be-a6c5-3ddb85dcf68e ro quiet splash initcall_debug 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-23-generic N/A
   

[Desktop-packages] [Bug 222208]

2015-02-06 Thread Leho Kraav
Eric, you're right, this bug actually has a split personality for me.

1. Saved passwords are not getting automatically used
2. Some (exact criteria unknown) login and password combos are not getting 
saved at all, despite repeated form fills (comment 67)

They may or may not have the same underlying mechanism responsible.
Pointers to more related bugs are welcome here.

SPE addon fixes scenario 2, which is even worse, because you have to
manually copy/paste from another password db like KeePass on every
Thunderbird startup.

But yes, I still have to Enter key currently through 4 authentication
prompts, an amount which can only increase. Still, thanks to SPE, my
life is incrementally better now and I can focus on looking for a
solution to scenario 1.

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

Title:
  user-id and password not sent automatically for rss-feed

Status in Mozilla Thunderbird Mail and News:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: thunderbird

  This is a bug I have seen for quite some time.  I am in the make
  hardy the best release there ever was-mood today and have brought
  myself to really reporting every single bit of problem I have put off
  for so long so somebody with the needed skills has a chance to fix it.

  I subscribe to an RSS feed hosted on a password-protected https-site
  in Thunderbird.  TB works fine but periodically asks me for the
  password although I have marked save password with password manager
  in the dialog.  In fact, the necessary fields are displayed filled in,
  but the pop-up comes back to me from time to time and I have to hit
  the OK button.

  I have set up a test installation which is exactly the same as the one
  I am having problems with at https://clients.leggewie.biz/tester/.
  The ssl-certificate is from cacert.org, so your browser might throw
  that up at first.  The user you need to get in is tb-tester and the
  password is launchpad.  The RSS feed is at
  
https://clients.leggewie.biz/tester/index.php?title=Special:Recentchangesfeed=rss
  When you susbscribe to that in TB and save the login credentials, you
  should have TB nagging you from time to time to with a login screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/08/+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 1419111] [NEW] memory leak

2015-02-06 Thread LAZA
Public bug reported:

memory leak - after 8 days running /usr/bin/X uses 60% of 8 GB RAM  --
machine is unusable

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xserver-xorg-core 2:1.15.1-0ubuntu2.6
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
Date: Fri Feb  6 19:54:53 2015
ExecutablePath: /usr/bin/Xorg
InstallationDate: Installed on 2014-03-16 (327 days ago)
InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140225)
ProcEnviron:

SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Description changed:

- memory leak - after 16 h uses 60% of 8 GB RAM
+ memory leak - after 8 days /usr/bin/X uses 60% of 8 GB RAM  -- machine
+ is unusable
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-core 2:1.15.1-0ubuntu2.6
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Fri Feb  6 19:54:53 2015
  ExecutablePath: /usr/bin/Xorg
  InstallationDate: Installed on 2014-03-16 (327 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140225)
  ProcEnviron:
-  
+ 
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

- memory leak - after 8 days /usr/bin/X uses 60% of 8 GB RAM  -- machine
- is unusable
+ memory leak - after 8 days running /usr/bin/X uses 60% of 8 GB RAM  --
+ machine is unusable
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-core 2:1.15.1-0ubuntu2.6
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Fri Feb  6 19:54:53 2015
  ExecutablePath: /usr/bin/Xorg
  InstallationDate: Installed on 2014-03-16 (327 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140225)
  ProcEnviron:
  
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- memory leak - after 16 h uses 60% of 8 GB RAM
+ memory leak

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

Title:
  memory leak

Status in xorg-server package in Ubuntu:
  New

Bug description:
  memory leak - after 8 days running /usr/bin/X uses 60% of 8 GB RAM
  -- machine is unusable

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-core 2:1.15.1-0ubuntu2.6
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Fri Feb  6 19:54:53 2015
  ExecutablePath: /usr/bin/Xorg
  InstallationDate: Installed on 2014-03-16 (327 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140225)
  ProcEnviron:

  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1419111/+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 1365926] Re: The “Enable this account” item in the new account settings page doesn’t work.

2015-02-06 Thread Aron Xu
** Also affects: unity-control-center (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  The “Enable this account” item in the new account settings page
  doesn’t work.

Status in Ubuntu Kylin:
  Confirmed
Status in unity-control-center package in Ubuntu:
  New

Bug description:
  The “Enable this account” item in the new account settings page
  doesn’t work.

  Steps:
  1. Enter into System settings--User Accounts
  2. Click Unlock in this page
  3. Add a new account
  4. Enter into the new account setting page, click the drop list at the right 
of Password item
  5. Chose Enable this account from Action list
  --Failed. This item doesn't work

  Configuration:
  PC: Dell Vostro
  OS: Ubuntu Kylin 14.10 x32 Daily 20140905

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntukylin/+bug/1365926/+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 1419131] [NEW] Can't unlock screen saver with pam_mysql

2015-02-06 Thread Mitch Claborn
Public bug reported:

Description:Ubuntu 14.04.1 LTS
Release:14.04
unity:
  Installed: 7.2.4+14.04.20141217-0ubuntu1

We are using pam_mysql to login to the workstation.  Excerpt from
/etc/pam.d/lightdm.conf:

auth required  pam_mysql.so verbose=1 user=x passwd=x
db= host=xxx table=operator usercolumn=username
passwdcolumn=password crypt=0 where=operator.enabled=1

There is a similar line in /etc/pam.d/gnome-screensaver

Login to the workstation works fine.  Up until this week, unlocking the
screen saver worked fine also.  Now it is not working to unlock from the
screen saver.  I added the verbose=1 option and can see the logging when
user logs in, but no logging shows up when the user attempts to unlock
the screen saver, leading me to believe it is not calling pam_mysql.

I tried a similar config in /etc/pam.d/unity but that did not help.

This are the entries from /var/log/apt/history.log from the day it stopped 
working:
Start-Date: 2015-02-05  05:12:23
Install: 
linux-image-extra-3.13.0-45-generic:amd64 (3.13.0-45.74, automatic), 
linux-image-3.13.0-45-generic:amd64 (3.13.0-45.74, automatic), 
linux-headers-3.13.0-45-generic:amd64 (3.13.0-45.74, automatic), 
linux-headers-3.13.0-45:amd64 (3.13.0-45.74, automatic)
Upgrade: 
libclamav6:amd64 (0.98.5+addedllvm-0ubuntu0.14.04.1, 
0.98.6+dfsg-0ubuntu0.14.04.1), 
linux-headers-generic:amd64 (3.13.0.44.51, 3.13.0.45.52), 
unity:amd64 (7.2.3+14.04.20140826-0ubuntu1, 
7.2.4+14.04.20141217-0ubuntu1), 
indicator-session:amd64 (12.10.5+14.04.20140410-0ubuntu1, 
12.10.5+14.04.20140925-0ubuntu1), 
libunity-core-6.0-9:amd64 (7.2.3+14.04.20140826-0ubuntu1, 
7.2.4+14.04.20141217-0ubuntu1), 
tzdata-java:amd64 (2014i-0ubuntu0.14.04, 2015a-0ubuntu0.14.04), 
file:amd64 (5.14-2ubuntu3.2, 5.14-2ubuntu3.3), 
libmagic1:amd64 (5.14-2ubuntu3.2, 5.14-2ubuntu3.3), 
unity-services:amd64 (7.2.3+14.04.20140826-0ubuntu1, 
7.2.4+14.04.20141217-0ubuntu1), 
clamav-freshclam:amd64 (0.98.5+addedllvm-0ubuntu0.14.04.1, 
0.98.6+dfsg-0ubuntu0.14.04.1), 
clamav-base:amd64 (0.98.5+addedllvm-0ubuntu0.14.04.1, 
0.98.6+dfsg-0ubuntu0.14.04.1), 
unzip:amd64 (6.0-9ubuntu1.1, 6.0-9ubuntu1.2), 
clamav:amd64 (0.98.5+addedllvm-0ubuntu0.14.04.1, 
0.98.6+dfsg-0ubuntu0.14.04.1), 
tzdata:amd64 (2014i-0ubuntu0.14.04, 2015a-0ubuntu0.14.04), 
linux-libc-dev:amd64 (3.13.0-44.73, 3.13.0-45.74), 
linux-image-generic:amd64 (3.13.0.44.51, 3.13.0.45.52), 
linux-generic:amd64 (3.13.0.44.51, 3.13.0.45.52)
End-Date: 2015-02-05  05:13:35

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.4+14.04.20141217-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
Uname: Linux 3.13.0-45-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Fri Feb  6 13:47:10 2015
InstallationDate: Installed on 2015-01-22 (15 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64+mac 
(20140722.2)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  Can't unlock screen saver with pam_mysql

Status in unity package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  unity:
Installed: 7.2.4+14.04.20141217-0ubuntu1

  We are using pam_mysql to login to the workstation.  Excerpt from
  /etc/pam.d/lightdm.conf:

  auth required  pam_mysql.so verbose=1 user=x passwd=x
  db= host=xxx table=operator usercolumn=username
  passwdcolumn=password crypt=0 where=operator.enabled=1

  There is a similar line in /etc/pam.d/gnome-screensaver

  Login to the workstation works fine.  Up until this week, unlocking
  the screen saver worked fine also.  Now it is not working to unlock
  from the screen saver.  I added the verbose=1 option and can see the
  logging when user logs in, but no logging shows up when the user
  attempts to unlock the screen saver, leading me to believe it is not
  calling pam_mysql.

  I tried a similar config in /etc/pam.d/unity but that did not help.

  This are the entries from /var/log/apt/history.log from the day it stopped 
working:
  Start-Date: 2015-02-05  05:12:23
  Install: 
linux-image-extra-3.13.0-45-generic:amd64 (3.13.0-45.74, automatic), 
linux-image-3.13.0-45-generic:amd64 (3.13.0-45.74, automatic), 

[Desktop-packages] [Bug 1419168] [NEW] Creating a hidden directory let temporarly a directory named New Directory

2015-02-06 Thread gael
Public bug reported:


I have created a new directory named .env in my home, with right-click  New 
Directory. When I pressed Enter to validate the name, the hidden directory 
was... hidden (!), which is quite logic, but there was at its place a directory 
named witth the default name of a new one New directory. If I refresh, all 
returns to normal: New directory is no more here. 

It's not a really bug, but the New Directory should not appears. 
  
Ubuntu 14.10
nautilus : 1:3.10.1-0ubuntu15

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

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

Title:
  Creating a hidden directory let temporarly a directory named New
  Directory

Status in nautilus package in Ubuntu:
  New

Bug description:
  
  I have created a new directory named .env in my home, with right-click  New 
Directory. When I pressed Enter to validate the name, the hidden directory 
was... hidden (!), which is quite logic, but there was at its place a directory 
named witth the default name of a new one New directory. If I refresh, all 
returns to normal: New directory is no more here. 

  It's not a really bug, but the New Directory should not appears. 

  Ubuntu 14.10
  nautilus : 1:3.10.1-0ubuntu15

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1419168/+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 1061554] [NEW] assertion failure `trap != NULL' displayed by all GTK3 software

2015-02-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

All GTK3/GNOME3 software I tried (gedit, evince, evolution, ...) display
the following error message:

$ gedit

(gedit:5387): Gdk-CRITICAL **: gdk_error_trap_pop_internal: assertion
`trap != NULL' failed

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: libgtk-3-0 3.6.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-16.15-lowlatency 3.5.4
Uname: Linux 3.5.0-16-lowlatency i686
ApportVersion: 2.6.1-0ubuntu1
Architecture: i386
Date: Thu Oct  4 13:56:41 2012
EcryptfsInUse: Yes
SourcePackage: gtk+3.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gtk+3.0 (Ubuntu)
 Importance: Low
 Status: Fix Released


** Tags: apport-bug i386 quantal
-- 
assertion failure `trap != NULL' displayed by all GTK3 software
https://bugs.launchpad.net/bugs/1061554
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gtk+3.0 in Ubuntu.

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


[Desktop-packages] [Bug 1358340] Re: [Indicators] Complete greeter profiles

2015-02-06 Thread Michael Terry
OK, after looking at this some more, I'm not going to implement comment
#26 yet.  There was one case left off that complicated matters (locked
and A is on but B is off -- in this case, we'd enable indicators even
though they asked us not to?  We could disable A when B is off, but they
are in separate screens and not obviously connected).

So my current thinking is to land a branch that enables all the
underpinnings of the shell changing profiles on the fly, but just not
use it quite yet until the settings panel design is done.  This support
would also be useful for a split greeter.  So it's all good changes.
But I'm going to hold off on actually using the dynamic profile
switching logic.

So to be clear, I'm not going to make the A option visible yet, nor
change how B disables/enables the indicators when locked.  But I will
land some code that makes such changes much easier in future.

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

Title:
  [Indicators] Complete greeter profiles

Status in The Date and Time Indicator:
  Invalid
Status in The Messaging Menu:
  Fix Released
Status in Transfer Indicator:
  Fix Released
Status in Ubuntu UX bugs:
  Fix Released
Status in The Unity 8 shell:
  Fix Released
Status in gsettings-ubuntu-touch-schemas package in Ubuntu:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in indicator-messages package in Ubuntu:
  Fix Released
Status in indicator-sound package in Ubuntu:
  Fix Released
Status in indicator-transfer package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  A recent change in the interest of security removed access to the
  indicators when the phone is locked and the greeter is showing.

  This was an accentual change based on a misunderstanding

  There had been a plan to support media playback control via the sound
  indicator. Without this the user must unlock the phone in order to
  simply pause the music or change songs, etc.

  
  Desired resolution:

  - Revert the change that caused this issue

  - Add a switch to System Settings to enable security conscious user to
  switch off Launcher and Greeter access while the phone is locked.
  This setting should *always* be off by default.
  https://wiki.ubuntu.com/SecurityAndPrivacySettings#Locking

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1358340/+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 1247366] Re: Evolution is missing bogofilter integration

2015-02-06 Thread Bug Watch Updater
** Changed in: evolution
   Status: Confirmed = Fix Released

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

Title:
  Evolution is missing bogofilter integration

Status in The Evolution Mail  Calendaring Tool:
  Fix Released
Status in evolution package in Ubuntu:
  Confirmed

Bug description:
  Evolution is missing bogofilter integration since Ubuntu 13.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: evolution 3.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sat Nov  2 05:15:42 2013
  ExecutablePath: /usr/bin/evolution
  InstallationDate: Installed on 2013-10-27 (6 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1247366/+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 1419180] [NEW] No proprietary drivers available for Nvidia GM107 [GeForce GTX 750 Ti] (rev a2)

2015-02-06 Thread Kurt
Public bug reported:

This is probably a duplicate of Bug #1351699 with the difference being
it happened on Ubuntu Studio 14.04 after an aptitude update, aptitude
upgrade I performed around February 5, 2015. My 27 display went from
WQHD (2560 x 1440) down to VGA (640x480). When I tried to open the
Settings Manager's  Additional Drivers I got the notice, No additional
drivers available.

** Affects: ubuntu-drivers-common (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  This is probably a duplicate of Bug #1351699 with the difference being
  it happened on Ubuntu Studio 14.04 after an aptitude update, aptitude
- upgrade I performed around February 5, 2015. The my 27 display went
- from WQHD (2560 x 1440) down to VGA (640x480). When I tried to open the
+ upgrade I performed around February 5, 2015. My 27 display went from
+ WQHD (2560 x 1440) down to VGA (640x480). When I tried to open the
  Settings Manager's  Additional Drivers I got the notice, No additional
  drivers available.

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

Title:
  No proprietary drivers available for Nvidia GM107 [GeForce GTX 750 Ti]
  (rev a2)

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  This is probably a duplicate of Bug #1351699 with the difference being
  it happened on Ubuntu Studio 14.04 after an aptitude update,
  aptitude upgrade I performed around February 5, 2015. My 27 display
  went from WQHD (2560 x 1440) down to VGA (640x480). When I tried to
  open the Settings Manager's  Additional Drivers I got the notice, No
  additional drivers available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1419180/+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 1419155] [NEW] changing nvidia drivers (under system settings) blows up unity/compiz (probably only config file - for current user [under guest account works fine])

2015-02-06 Thread Sebastian Łepczyński
Public bug reported:

There was default nouveau driver, but these one freezes ubuntu while
after login (on nvidia gti 5xx cards), so i installed recommended nvidia
binary driver 331, but there was some problems (like spreading windows
causes some strange flickering in unity/compiz), so i tried the
nvidia-331-updates driver from system settings, but then i couldn't do
aptitude upgrade (there was some errors about nvidia blocking dkpg
--reconfigure), so i tried to go back to nouveau driver (but changing
driver from system settings was imposible) so i uninstalled al nvidia-*
packages, installed nvidia-common, echoed `nouveau` to /etc/modules and
reboot.

Any way, this didn't work out.

At the moment no window manager after login on my user.

Is there any way to get back default config?

Mayby that's important, but on the guest account everything is fine.
Wokrs as expected.

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-331-updates (not installed)
ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
Date: Fri Feb  6 19:38:50 2015
DuplicateSignature: package:nvidia-331-updates:(not installed):podproces 
zainstalowany skrypt post-removal zwrócił kod błędu 8
ErrorMessage: podproces zainstalowany skrypt post-removal zwrócił kod błędu 8
InstallationDate: Installed on 2015-02-04 (1 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
SourcePackage: nvidia-graphics-drivers-331-updates
Title: package nvidia-331-updates (not installed) failed to install/upgrade: 
podproces zainstalowany skrypt post-removal zwrócił kod błędu 8
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-331-updates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package utopic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1419155

Title:
  changing nvidia drivers (under system settings) blows up unity/compiz
  (probably only config file - for current user [under guest account
  works fine])

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  New

Bug description:
  There was default nouveau driver, but these one freezes ubuntu while
  after login (on nvidia gti 5xx cards), so i installed recommended
  nvidia binary driver 331, but there was some problems (like spreading
  windows causes some strange flickering in unity/compiz), so i tried
  the nvidia-331-updates driver from system settings, but then i
  couldn't do aptitude upgrade (there was some errors about nvidia
  blocking dkpg --reconfigure), so i tried to go back to nouveau driver
  (but changing driver from system settings was imposible) so i
  uninstalled al nvidia-* packages, installed nvidia-common, echoed
  `nouveau` to /etc/modules and reboot.

  Any way, this didn't work out.

  At the moment no window manager after login on my user.

  Is there any way to get back default config?

  Mayby that's important, but on the guest account everything is fine.
  Wokrs as expected.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-updates (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  Date: Fri Feb  6 19:38:50 2015
  DuplicateSignature: package:nvidia-331-updates:(not installed):podproces 
zainstalowany skrypt post-removal zwrócił kod błędu 8
  ErrorMessage: podproces zainstalowany skrypt post-removal zwrócił kod błędu 8
  InstallationDate: Installed on 2015-02-04 (1 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: package nvidia-331-updates (not installed) failed to install/upgrade: 
podproces zainstalowany skrypt post-removal zwrócił kod błędu 8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1419155/+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 1419155] Re: changing nvidia drivers (under system settings) blows up unity/compiz (probably only config file - for current user [under guest account works fine])

2015-02-06 Thread Apport retracing service
** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1419155

Title:
  changing nvidia drivers (under system settings) blows up unity/compiz
  (probably only config file - for current user [under guest account
  works fine])

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  New

Bug description:
  There was default nouveau driver, but these one freezes ubuntu while
  after login (on nvidia gti 5xx cards), so i installed recommended
  nvidia binary driver 331, but there was some problems (like spreading
  windows causes some strange flickering in unity/compiz), so i tried
  the nvidia-331-updates driver from system settings, but then i
  couldn't do aptitude upgrade (there was some errors about nvidia
  blocking dkpg --reconfigure), so i tried to go back to nouveau driver
  (but changing driver from system settings was imposible) so i
  uninstalled al nvidia-* packages, installed nvidia-common, echoed
  `nouveau` to /etc/modules and reboot.

  Any way, this didn't work out.

  At the moment no window manager after login on my user.

  Is there any way to get back default config?

  Mayby that's important, but on the guest account everything is fine.
  Wokrs as expected.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-updates (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  Date: Fri Feb  6 19:38:50 2015
  DuplicateSignature: package:nvidia-331-updates:(not installed):podproces 
zainstalowany skrypt post-removal zwrócił kod błędu 8
  ErrorMessage: podproces zainstalowany skrypt post-removal zwrócił kod błędu 8
  InstallationDate: Installed on 2015-02-04 (1 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: package nvidia-331-updates (not installed) failed to install/upgrade: 
podproces zainstalowany skrypt post-removal zwrócił kod błędu 8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1419155/+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 1061554] Re: assertion failure `trap != NULL' displayed by all GTK3 software

2015-02-06 Thread Mathew Hodson
** Package changed: ubuntu = gtk+3.0 (Ubuntu)

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

Title:
  assertion failure `trap != NULL' displayed by all GTK3 software

Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  All GTK3/GNOME3 software I tried (gedit, evince, evolution, ...)
  display the following error message:

  $ gedit

  (gedit:5387): Gdk-CRITICAL **: gdk_error_trap_pop_internal: assertion
  `trap != NULL' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: libgtk-3-0 3.6.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-16.15-lowlatency 3.5.4
  Uname: Linux 3.5.0-16-lowlatency i686
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: i386
  Date: Thu Oct  4 13:56:41 2012
  EcryptfsInUse: Yes
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1061554/+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 1308105]

2015-02-06 Thread Andreldm1989-j
Created attachment 5908
HDMI and Screen On Event Patch(Updated)

@Liviu
Here you are =)

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

Title:
  Xfce resets TV mode to NULL when power cycled

Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
  Confirmed
Status in xfce4-settings:
  Incomplete
Status in nvidia-graphics-drivers package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Invalid
Status in xfce4-settings package in Ubuntu:
  Confirmed

Bug description:
  I had an HTPC with Mythbuntu 12.04 installed.  Upon upgrading a new
  behavior that if the TV is power cycled it no longer detects a link
  with the HTPC.

  When this happens I can find in the xorg log that there is an
  accompanying log item:

  [ 39829.509] (II) NVIDIA(0): Setting mode NULL

  After debugging with NVIDIA at
  https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being-
  detected/ we've deteremined it's a X client that reacts to the RANDR
  events causing the mode to be set to NULL.

  Working through the list in an Xfce environment, the culprit is
  xfsettingsd.  If xfsettingsd is running, it causes the TV to come up
  in a NULL mode.  If it's killed, it remains in the mode it was
  previously running in.

  
  Until this is fixed, this behavior can be worked around with a simple shell 
script:
  ==
  #!/bin/sh
  #Fix TV state when HDMI link is lost.
  #By Mario Limonciello supe...@ubuntu.com

  OUTPUT=HDMI-0
  BAD_MODE=1280x720
  GOOD_MODE=1920x1080

  for MODE in $BAD_MODE $GOOD_MODE; do
   DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE
   sleep 2
  done
  ==

To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/1308105/+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 1412602] Re: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a

2015-02-06 Thread Erick Brunzell
I have been able to reproduce that a few times in a gnome-shell session
but it's not specific to any one task. It crashed/froze twice just
looking for logs and once again while launching Firefox. OTOH I can use
the classic session w/o a problem - in fact I'm streaming the nightly
news right now.

I know that X actually freezes when the screen tears because I'd set
Ctrl+Alt+Backspace to kill X and tested it in both sessions. When the
screen tears as shown in the attached pic the keyboard is just totally
unresponsive causing me to do a hard reset.

There are no .xsession-errors in Home and I don't see anything unusual
in /var/log/Xorg.0.log but there is also an /var/log/Xorg.0.log.old that
I can't read.

FYI sometime tomorrow I'll add some storage to that box so I can retain
4 or 5 installs at the same time. That way I can dig for logs and/or do
some retesting without having to reinstall and update each time.

** Attachment added: IMG_4817.JPG
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1412602/+attachment/4314052/+files/IMG_4817.JPG

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

Title:
  No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a

Status in Accelerated Xorg driver for nVidia cards:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New
Status in linux source package in Trusty:
  Confirmed
Status in xserver-xorg-video-nouveau source package in Trusty:
  New
Status in linux source package in Utopic:
  Confirmed
Status in xserver-xorg-video-nouveau source package in Utopic:
  New
Status in linux source package in Vivid:
  Confirmed
Status in xserver-xorg-video-nouveau source package in Vivid:
  New

Bug description:
  I've been testing the Ubuntu GNOME Vivid daily images in anticipation
  of Alpha 2 and I noticed that with this specific hardware I get no
  graphics at all other than a blank screen (see attached photo):

  AMD Sempron Processor LE-1250 @ 2.2 GHz
  nVidia C61 [GeForce 7025 / nForce 630a] (rev a2)
  nVidia MCP61 High Definition Audio (rev a2)
  nVidia MCP61 Ethernet (rev a2)
  2GB DDR2 RAM

  In fact I never even get as far as the screen offering to Try or
  Install, but I can enter the Advanced Boot Options screen and select
  either Try or Install from there, but with both options I still get
  the same blank screen.

  Further testing reveals the same results with Ubuntu and Ubuntu GNOME
  but I found that both the Xubuntu and Lubuntu images will boot
  properly on this box so I installed Lubuntu and then installed the
  ubuntu-desktop, ubuntu-gnome-desktop, and gnome-session-flashback
  meta-packages just to try some things.

  After doing so I found that the Unity, GNOME Shell, Gnome Classic, and
  Flashback w/Compiz sessions produce broken graphics just as the Ubuntu
  GNOME and Ubuntu live images do. So basically Compiz and Mutter both
  fail to display any usable UI. OTOH both the Lubuntu and Flashback
  w/Metacity sessions work just fine.

  I next opened the Additional drivers UI and chose nvidia-304.125
  (current) and all DE's perform quite well with the proprietary drivers
  so I deduced that nouveau might be the culprit.

  The last known working Ubuntu and Ubuntu GNOME live images are
  14.04.1. I hadn't tried Utopic on this box yet but it's also a fail.
  I'll try the proposed 14.04.2 images ASAP (probably after Vivid Alpha
  2 is released).

  But I see no point in trying to fix this for Utopic (or even 14.04.2
  if it's effected) because of the 9 month life-cycle for Utopic and the
  continued availability of the 14.04.1 images. In fact I'd be cool with
  this not being fixed until 16.04 as long as it's documented so people
  know what versions will and will not work.

  I'm probably forgetting something but that's all I can think of ATM.
  Sorry in advance if I did this totally wrong.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon Jan 19 17:41:32 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Biostar Microtech Int'l Corp Device [1565:1405]
  InstallationDate: Installed on 2015-01-19 (0 days ago)
  InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150118)
  Lsusb:
   Bus 001 Device 001: ID 

[Desktop-packages] [Bug 1419217] Re: gnome-terminal displays unreadble letters in main window and title

2015-02-06 Thread Karl-Philipp Richter
** Attachment added: gnome_terminal_unreadable_output.png
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1419217/+attachment/4314051/+files/gnome_terminal_unreadable_output.png

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

Title:
  gnome-terminal displays unreadble letters in main window and title

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  unclear whether the letters belong to a charset or are just random
  junk bytes, see attached screenshot for details. This might be related
  to an invokation of `cat /dev/urandom`, but the issues can't be
  reproduced constantly, but multiple times.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gnome-terminal 3.6.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb  7 04:00:45 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-01-26 (11 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1419217/+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 1416601] Re: touchpad does not respond to tap-to-clicks in I2C mode in Ubuntu 15.04 on 2015 XPS 13 (9343)

2015-02-06 Thread Major Hayden
Done with the git bisect.  It's somewhere in the late days of 3.17 and
early days of 3.18.  Here's the RHBZ with the patch:

  https://bugzilla.redhat.com/show_bug.cgi?id=1188439#c25

I'm hoping someone with more knowledge than me around this part of the
kernel can make sense of it.  If I pull the patch, the touchpad works
extremely well (see RHBZ entry for more).

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

Title:
  touchpad does not respond to tap-to-clicks in I2C mode in Ubuntu 15.04
  on 2015 XPS 13 (9343)

Status in Dell Sputnik:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-synaptics package in Fedora:
  Unknown

Bug description:
  Tap-to-click does not work unless I tap several times really fast
  (which is really hard to do), which also causes the cursor to move.
  This is a poor user experience.

  Relatedly, sometimes when using two-finger scrolling, the touchpad
  will get stuck such that I can let go and the cursor won't move. I can
  continue using two fingers to try scrolling, which works, but I can't
  get the cursor to move. If I tap the cursor several times really fast,
  I can eventually get the cursor unstuck so it moves again. I suspect
  that this is related to the tap-to-click issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-12-generic 3.18.0-12.13
  ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4
  Uname: Linux 3.18.0-12-generic x86_64
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jared  3714 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jan 30 20:12:17 2015
  HibernationDevice: RESUME=UUID=af18bf4f-1453-4c8c-8b8e-abdc5d4e0674
  InstallationDate: Installed on 2014-11-03 (89 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia 
   Bus 001 Device 003: ID 04f3:2051 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-12-generic 
root=/dev/mapper/ubuntu--vg-root ro video.use_native_backlight=1 
video.use_native_backlight=1
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-12-generic N/A
   linux-backports-modules-3.18.0-12-generic  N/A
   linux-firmware 1.141
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-01-08 (23 days ago)
  dmi.bios.date: 11/04/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0144PA
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd11/04/2014:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1416601/+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 1220426]

2015-02-06 Thread snafu109
Now patch is merged, should status be updated?

Reference:
http://cgit.freedesktop.org/xorg/xserver/commit/?id=fe4c774c572e3f55a7417f0ca336ae1479a966ad

It would be great to update status so this flows to Ubuntu's bug
tracker.

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

Title:
  [nvidia-prime]Freeze while using touchpad

Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Using Asus N43SL laptop as an example, with nvidia-prime installed, so
  the dedicated NVIDIA graphics card (GT 540m) is in use, once in a
  while, my screen will freeze when I use my touchpad.

  WORKAROUND: Use USB mouse.

  WORKAROUND: Uninstall nvidia-prime and use integrated graphics.

  WORKAROUND: Do a VT switch via Ctrl+Alt+F1 then Ctrl+Alt+F7.

  In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: 
touchpad found each time I did a VT switch and regained control:
  
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1220426/+attachment/3801516/+files/Xorg.0.log

  The following upstream report has a patch that addresses this issue:
  https://bugs.freedesktop.org/show_bug.cgi?id=86288

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1220426/+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 1220426] Re: [nvidia-prime]Freeze while using touchpad

2015-02-06 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed = Fix Released

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

Title:
  [nvidia-prime]Freeze while using touchpad

Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Using Asus N43SL laptop as an example, with nvidia-prime installed, so
  the dedicated NVIDIA graphics card (GT 540m) is in use, once in a
  while, my screen will freeze when I use my touchpad.

  WORKAROUND: Use USB mouse.

  WORKAROUND: Uninstall nvidia-prime and use integrated graphics.

  WORKAROUND: Do a VT switch via Ctrl+Alt+F1 then Ctrl+Alt+F7.

  In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: 
touchpad found each time I did a VT switch and regained control:
  
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1220426/+attachment/3801516/+files/Xorg.0.log

  The following upstream report has a patch that addresses this issue:
  https://bugs.freedesktop.org/show_bug.cgi?id=86288

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1220426/+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 1307162] Re: Can't open ODT documents that are in the trash

2015-02-06 Thread Launchpad Bug Tracker
[Expired for libreoffice (Ubuntu) because there has been no activity for
60 days.]

** Changed in: libreoffice (Ubuntu)
   Status: Incomplete = Expired

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

Title:
  Can't open ODT documents that are in the trash

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  If I create an empty ODT document, move it to the trash and then
  double-click on it, it isn't automatically opened in LibreOffice.
  Instead, a Choose filter window opens (see attachment). It does work
  for ODS and ODP documents, so this is probably Writer-specific.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice-writer 1:3.5.7-0ubuntu5
  Uname: Linux 3.2.0-60-generic x86_64
  Architecture: amd64
  Date: Sun Apr 13 18:04:31 2014
  InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 
20120905-10:42
  LiveMediaBuild: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 
20120905-10:42
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1307162/+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 594257] Re: cannot disable system beep [10.04]

2015-02-06 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete = Expired

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

Title:
  cannot disable system beep [10.04]

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Tried:
  - Sound--Alertvolume: Slider to 0
  - Sound--Alertvolume: Mute enabled
  - Blacklisting pcspkr according to this:
  
http://www.arsgeek.com/2006/08/23/how-to-turn-off-the-annoying-system-beep-in-linux-debianubuntu/
  - and at least one other forum topic, i cant remember which though

  It still beeps annoyingly loud everytime I put the laptop to sleep or
  shut it down

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/594257/+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 1386257] Re: intel-microcode should be installed by default, when the CPU is GenuineIntel

2015-02-06 Thread Aron Xu
** Also affects: ubuntukylin-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  intel-microcode should be installed by default, when the CPU is
  GenuineIntel

Status in intel:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntukylin-meta package in Ubuntu:
  Fix Committed

Bug description:
  intel-microcode should be installed by default on the bare-metal
  systems which are running on GenuineIntel CPUs, by the installers.

  Similarly other microcode packages for other CPUs brands should be
  considered for inclusion (e.g. amd64-microcode).

  I hope that ubuntu-drivers-common can gain ability to detect cpu
  series and/or vendors, packages that provide microcodes similarly
  declare support for cpu series and/or vendors, the microcode packages
  are shipped on the CDs in the pool directory, and installed on to the
  target machines as part of the installation.

  This should help with rapid correction of bugs and behaviour of the
  CPUs in the field.

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1386257/+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 1412602] Re: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a

2015-02-06 Thread Tim
That looks like video corruption, and it is possible that gnome-classic
has some of the animations disabled compared to gnome-shell, but I can't
think of any other difference.

.xsession-errors is obsolete, logs will by default be in
~/.cache/upstart/gnome-session-GNOME.log under upstart boot or
`journalctl -b /usr/bin/gnome-session` under systemd init.

But either way it seems likely that is a bug in Nouveau, so those logs
might not be too useful either.

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

Title:
  No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a

Status in Accelerated Xorg driver for nVidia cards:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New
Status in linux source package in Trusty:
  Confirmed
Status in xserver-xorg-video-nouveau source package in Trusty:
  New
Status in linux source package in Utopic:
  Confirmed
Status in xserver-xorg-video-nouveau source package in Utopic:
  New
Status in linux source package in Vivid:
  Confirmed
Status in xserver-xorg-video-nouveau source package in Vivid:
  New

Bug description:
  I've been testing the Ubuntu GNOME Vivid daily images in anticipation
  of Alpha 2 and I noticed that with this specific hardware I get no
  graphics at all other than a blank screen (see attached photo):

  AMD Sempron Processor LE-1250 @ 2.2 GHz
  nVidia C61 [GeForce 7025 / nForce 630a] (rev a2)
  nVidia MCP61 High Definition Audio (rev a2)
  nVidia MCP61 Ethernet (rev a2)
  2GB DDR2 RAM

  In fact I never even get as far as the screen offering to Try or
  Install, but I can enter the Advanced Boot Options screen and select
  either Try or Install from there, but with both options I still get
  the same blank screen.

  Further testing reveals the same results with Ubuntu and Ubuntu GNOME
  but I found that both the Xubuntu and Lubuntu images will boot
  properly on this box so I installed Lubuntu and then installed the
  ubuntu-desktop, ubuntu-gnome-desktop, and gnome-session-flashback
  meta-packages just to try some things.

  After doing so I found that the Unity, GNOME Shell, Gnome Classic, and
  Flashback w/Compiz sessions produce broken graphics just as the Ubuntu
  GNOME and Ubuntu live images do. So basically Compiz and Mutter both
  fail to display any usable UI. OTOH both the Lubuntu and Flashback
  w/Metacity sessions work just fine.

  I next opened the Additional drivers UI and chose nvidia-304.125
  (current) and all DE's perform quite well with the proprietary drivers
  so I deduced that nouveau might be the culprit.

  The last known working Ubuntu and Ubuntu GNOME live images are
  14.04.1. I hadn't tried Utopic on this box yet but it's also a fail.
  I'll try the proposed 14.04.2 images ASAP (probably after Vivid Alpha
  2 is released).

  But I see no point in trying to fix this for Utopic (or even 14.04.2
  if it's effected) because of the 9 month life-cycle for Utopic and the
  continued availability of the 14.04.1 images. In fact I'd be cool with
  this not being fixed until 16.04 as long as it's documented so people
  know what versions will and will not work.

  I'm probably forgetting something but that's all I can think of ATM.
  Sorry in advance if I did this totally wrong.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon Jan 19 17:41:32 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Biostar Microtech Int'l Corp Device [1565:1405]
  InstallationDate: Installed on 2015-01-19 (0 days ago)
  InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150118)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 046d:c52e Logitech, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: BIOSTAR Group N68SB-M2S
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-9-generic 
root=UUID=acf0fd65-0d6d-4da6-9532-2adc558bc0a7 ro quiet splash 
init=/lib/systemd/systemd
  SourcePackage: xserver-xorg-video-nouveau
  UdevLog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 06/24/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: N68SB-M2S

[Desktop-packages] [Bug 1220426]

2015-02-06 Thread Aaron Plattner
Yeah, it should.  Thanks for the ping.

Marking fixed with commit fe4c774c572e3f55a7417f0ca336ae1479a966ad
Author: Nikhil Mahale nmah...@nvidia.com
Date:   Sat Jan 24 17:06:59 2015 -0800

os: Fix timer race conditions

Fixing following kind of race-conditions -

WaitForSomething()
|
  // timers - timer-1 - timer-2 - null
   while (timers  (int) (timers-expires - now) = 0)
   // prototype - DoTimer(OsTimerPtr timer, CARD32 now, 
OsTimerPtr *prev)
   DoTimer(timers, now, timers)
   |
   |
    OsBlockSignals();   OS Signal comes just before 
blocking it,
 timer-1 handler gets called.
 // timer-1 gets served and 
scheduled again;
 // timers - timer-2 - 
timer-1 - null

 *prev = timer-next;
  timer-next = NULL;   // timers - null
  // timers list gets corrupted here and timer-2 gets 
removed from list.

Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=86288
Signed-off-by: Nikhil Mahale nmah...@nvidia.com
Reviewed-by: Julien Cristau jcris...@debian.org

v2: Apply warning fixes from Keith Packard kei...@keithp.com

Reviewed-by: Aaron Plattner aplatt...@nvidia.com
Signed-off-by: Aaron Plattner aplatt...@nvidia.com
Signed-off-by: Keith Packard kei...@keithp.com

 os/WaitFor.c | 41 ++---
 1 file changed, 26 insertions(+), 15 deletions(-)

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

Title:
  [nvidia-prime]Freeze while using touchpad

Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Using Asus N43SL laptop as an example, with nvidia-prime installed, so
  the dedicated NVIDIA graphics card (GT 540m) is in use, once in a
  while, my screen will freeze when I use my touchpad.

  WORKAROUND: Use USB mouse.

  WORKAROUND: Uninstall nvidia-prime and use integrated graphics.

  WORKAROUND: Do a VT switch via Ctrl+Alt+F1 then Ctrl+Alt+F7.

  In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: 
touchpad found each time I did a VT switch and regained control:
  
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1220426/+attachment/3801516/+files/Xorg.0.log

  The following upstream report has a patch that addresses this issue:
  https://bugs.freedesktop.org/show_bug.cgi?id=86288

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1220426/+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 1153488] Re: Treats bluetooth input device batteries as batteries

2015-02-06 Thread Shih-Yuan Lee
@redman,

My patch has been included in the upstream, and it is also in the Ubuntu 14.10.
It is also modified by other developers, so it has been a little different from 
the one I made in Ubuntu 12.04.
I think the problem is that some rule is changed  in UPower, but the mechanism 
to detect Bluetooth input devices doesn't change accordingly.
So it failed.

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

Title:
  Treats bluetooth input device batteries as batteries

Status in gnome-power-manager package in Ubuntu:
  Invalid
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-power-manager source package in Precise:
  Invalid
Status in upower source package in Precise:
  Fix Released
Status in gnome-power-manager source package in Quantal:
  Invalid
Status in upower source package in Quantal:
  Won't Fix
Status in gnome-power-manager source package in Raring:
  Invalid
Status in upower source package in Raring:
  Fix Released
Status in gnome-power-manager source package in Saucy:
  Invalid
Status in upower source package in Saucy:
  Fix Released

Bug description:
  [Impact]

   * There are many Bluetooth devices with battery information inside.
  When they are treated as system battery, it will make the system
  poweroff/suspend/hibernate when some Bluetooth device has critical low
  battery. It is a very annoying behavior for the users. Originally,
  there is no such Bluetooth battery information until Ubuntu 12.04
  brings linux-quantal-lts and linux-raring-lts, so those linux kernels
  also bring this issue.

  [Test Case]

   * Pair some Bluetooth devices, such as Apple Wireless Mouse or Apple 
Wireless Keyboard.
   * Click the power indicator and you can find Apple Wireless Mouse is listed 
as system battery, and there is no Apple Wireless Keyboard. If you open 
gnome-power-statistics, you can find the 'Supply' field of Apple Wireless Mouse 
is 'Yes' but it should not be.

  [Regression Potential]

   * There is no obvious regression as I know.

  [Other Info]

   * Most patches are from upstream, modified to fix the conflicts, and made by 
the same developer (i.e. fourdollars).
   * We need another patch from 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d0a934b764c67b4bf626f5b7cf725a6e3066afd2
 to make Apple Wireless Keyboard showing.

  [Original Bug Description]

  This is a weird one... the system is an HP Pavilion 23 All In One and
  is powered by a large power supply brick.

  I currently have an Apple Magic Mouse connected via Bluetooth.  As
  soon as the mouse is connected, the Battery indicator shows up and
  clicking on that shows that the system is reading my mouse as a
  battery!

  See the attached screen shot for what I see in the Power status.

  Looking at hcitool:
  ubuntu@201206-11396:~$ hcitool dev
  Devices:
   hci0 9C:B7:0D:80:71:DB

  To make matters even more weird, I actually observed the battery
  indicator go from full to Critically Low and the system suspended
  itself.  Keep in mind, again, that this system has NO battery, it's
  reading my bluetooth mouse as a battery device.

  I disconnected the magic mouse and the battery indicator went to Empty
  Red outline and status showed Battery Disconnected.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1
  ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic x86_64
  NonfreeKernelModules: wl fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC 
Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC 
Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1726 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb4 irq 16'
     Mixer name : 'Realtek ALC269VC'
     Components : 'HDA:10ec0269,103c2aee,00100202'
     Controls  : 21
     Simple ctrls  : 10
  Date: Mon Mar 11 03:54:36 2013
  HibernationDevice: RESUME=UUID=ccd7a21f-7a71-4fa5-b95d-e2898c3dae24
  InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 
(20130213)
  MachineType: Hewlett-Packard a654
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic 
root=UUID=e2a5f4ae-dfa2-40be-a6c5-3ddb85dcf68e ro quiet splash initcall_debug 

[Desktop-packages] [Bug 1386257] Re: intel-microcode should be installed by default, when the CPU is GenuineIntel

2015-02-06 Thread Aron Xu
** Changed in: ubuntukylin-meta (Ubuntu)
   Status: New = Fix Committed

** Branch linked: lp:~ubuntukylin-members/ubuntu-seeds/ubuntukylin.vivid

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

Title:
  intel-microcode should be installed by default, when the CPU is
  GenuineIntel

Status in intel:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntukylin-meta package in Ubuntu:
  Fix Committed

Bug description:
  intel-microcode should be installed by default on the bare-metal
  systems which are running on GenuineIntel CPUs, by the installers.

  Similarly other microcode packages for other CPUs brands should be
  considered for inclusion (e.g. amd64-microcode).

  I hope that ubuntu-drivers-common can gain ability to detect cpu
  series and/or vendors, packages that provide microcodes similarly
  declare support for cpu series and/or vendors, the microcode packages
  are shipped on the CDs in the pool directory, and installed on to the
  target machines as part of the installation.

  This should help with rapid correction of bugs and behaviour of the
  CPUs in the field.

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1386257/+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 1416601] Re: touchpad does not respond to tap-to-clicks in I2C mode in Ubuntu 15.04 on 2015 XPS 13 (9343)

2015-02-06 Thread Geoff Teale
I see this also on 3.18.0-12-generic.

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

Title:
  touchpad does not respond to tap-to-clicks in I2C mode in Ubuntu 15.04
  on 2015 XPS 13 (9343)

Status in Dell Sputnik:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-synaptics package in Fedora:
  Unknown

Bug description:
  Tap-to-click does not work unless I tap several times really fast
  (which is really hard to do), which also causes the cursor to move.
  This is a poor user experience.

  Relatedly, sometimes when using two-finger scrolling, the touchpad
  will get stuck such that I can let go and the cursor won't move. I can
  continue using two fingers to try scrolling, which works, but I can't
  get the cursor to move. If I tap the cursor several times really fast,
  I can eventually get the cursor unstuck so it moves again. I suspect
  that this is related to the tap-to-click issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-12-generic 3.18.0-12.13
  ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4
  Uname: Linux 3.18.0-12-generic x86_64
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jared  3714 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jan 30 20:12:17 2015
  HibernationDevice: RESUME=UUID=af18bf4f-1453-4c8c-8b8e-abdc5d4e0674
  InstallationDate: Installed on 2014-11-03 (89 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia 
   Bus 001 Device 003: ID 04f3:2051 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-12-generic 
root=/dev/mapper/ubuntu--vg-root ro video.use_native_backlight=1 
video.use_native_backlight=1
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-12-generic N/A
   linux-backports-modules-3.18.0-12-generic  N/A
   linux-firmware 1.141
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-01-08 (23 days ago)
  dmi.bios.date: 11/04/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0144PA
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd11/04/2014:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1416601/+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 1040873] Re: [pulseaudio-discuss] Profile switching on headphone plugging (was: LFE filter)

2015-02-06 Thread Raymond

 Hrm, that is actually a good question. In theory, I would expect
 module-switch-on-port-available to switch profiles between 2.0 and 2.1
 as headphones are plugged in and out, but in practice,

   - I'm not 100% sure if our don't switch to HDMI might prevent
 switching from 2.1 to 2.0 when headphones are plugged in, and

   - As the 2.0 profile is available on speakers, that will continue to
 be selected when headphones are unplugged.

 So, while this is not directly related to whether there is an LFE filter
 or not - we already have a 2.1, 5.1, etc, profiles - indeed the problem
 might become worse with the LFE filter.


 Well, I have just tested how today's git version of pulseaudio (without
your patch) behaves when plugging headphones. Yes - the problem is
pre-existing.

 The PC under test has analog outputs on the back panel that,
theoretically, can be used as analog 5.1 outputs, and also has headphone
and microphone sockets at the front panel.

 So, the test is:

 1. Make sure something (I tested with a cable extender) is plugged in the
line output on the back panel.
 2. Select the analog stereo duplex profile in pavucontrol.
 3. Look at the Playback devices tab. It should say: Port: Line Out
(plugged in).
 4. Plug in headphones at the front. Note that the port changes to:
Headphones (plugged in). I.e. exactly as expected.
 5. Unplug the headphones, watch how the port changes back to Line Out
(plugged in).
 5. Now select the Analog Surround 5.1 + Stereo Input as a profile. Now
the port stays as Line Out (plugged in), but the volume control becomes
6-channel.
 6. Plug headphones in. Result: the port stays as Line Out (plugged in),
with 6-channel volume control, and speaker-test -c6 does not reach
headphones.

 Sorry, I cannot retest this at home without additional jack-retasking
(which could make the result untrustworthy), because my home PC does not
have any audio sockets at the front panel.


I have doubt about changing 5.1 profile to stereo when headphone is plugged
since most user use 5.1 profile to watch movie, changing 5.1 profile to
stereo require stop playback of 5.1 and start stereo playback , how can the
application perform video audio sync for this kind of profile switching

Do pulseaudio switch back to 5.1 profile when headphone is pkugged ?

https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1040873

For those Asus N series notebook with external Sonic Master subwoofer,
Seem using jack detection of spdif pin complex for the propretiary jack of
the subwoofer , you need driver create an adhoc jack detection control if
you want to switch from stereo to 2.1 profile when the subwoofer is plugged

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

Title:
  [N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound at all:
  Subwoofer not working

Status in alsa-driver package in Ubuntu:
  Triaged

Bug description:
  Hi,

  this bug is a fork of https://bugs.launchpad.net/ubuntu/+source/alsa-
  driver/+bug/871808 because #871808 stands for a different hardware
  with a different solution, so people may get confused.

  Here is a summary (see post #48 to #54 of #871808):
  The subwoofer of Asus N56VZ laptop doesn't work out of the box.

  #sudo hda-jack-sense-test -a :
  *** Without subwoofer:
  Pin 0x1e (Black SPDIF Out): present = No
  *** With subwoofer:
  Pin 0x1e (Black SPDIF Out): present = Yes

  http://www.alsa-
  project.org/db/?f=2778e7f430aa95ae219d0b2bc3cb5e46abd0a33a

  -- There are two ways of making it work:

  #1
  a. Add to rc.local :
  echo 0x1e 0x99130112  /sys/class/sound/hwC0D0/user_pin_configs
  echo 1  /sys/class/sound/hwC0D0/reconfig
  b. Add options snd-hda-intel model=asus-mode4 in 
/etc/modprobe.d/alsa-base.conf
  c. Reboot
  d. Set the mode to Analog Stereo Output and then to Analog Surround 5.1 
output in the sound settings panel. You have to do this each time you reboot!!!

  #2
  a. Add to rc.local :
  echo 0x16 0x99130111  /sys/class/sound/hwC0D0/user_pin_configs
  echo 0x1e 0x99130112  /sys/class/sound/hwC0D0/user_pin_configs
  echo 1  /sys/class/sound/hwC0D0/reconfig
  b. Reboot
  c. Set the mode to Analog Stereo Output and then to Analog Surround 5.1 
output in the sound settings panel. You have to do this each time you reboot!!!

  Both give the same results and fix the bug.

  -- Can you make it work out of the box?

  There is still two other bugs on this laptop :
  - crackling audio when playing with sound volume: see 
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1040867
  - When I put the omputer in sleep mode, there is no way to get sound working 
on resume: should I open a new bug to investigate this?

  Regards
  Sam

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  

[Desktop-packages] [Bug 1419236] [NEW] locks up

2015-02-06 Thread abiticus
Public bug reported:

trash bin will not empty locks up

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
Uname: Linux 3.13.0-45-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.6
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: Sat Feb  7 00:24:18 2015
DistUpgraded: 2014-08-23 11:35:14,510 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 ndiswrapper, 1.59, 3.13.0-44-generic, x86_64: installed
 ndiswrapper, 1.59, 3.13.0-45-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:3602]
   Subsystem: Hewlett-Packard Company Device [103c:3602]
InstallationDate: Installed on 2014-08-23 (167 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 
(20140204)
MachineType: Hewlett-Packard HP Pavilion dv5 Notebook PC
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=3dfaf310-04bd-441f-9441-71cd7d70b824 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2014-08-23 (167 days ago)
dmi.bios.date: 01/23/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.14
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3602
dmi.board.vendor: Quanta
dmi.board.version: 02.22
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.14:bd01/23/2009:svnHewlett-Packard:pnHPPaviliondv5NotebookPC:pvrRev1:rvnQuanta:rn3602:rvr02.22:cvnQuanta:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv5 Notebook PC
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1~ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6
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.4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Fri Feb  6 20:12:24 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.15.1-0ubuntu2.6

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


** Tags: amd64 apport-bug compiz-0.9 package-from-proposed trusty ubuntu

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

Title:
  locks up

Status in xorg package in Ubuntu:
  New

Bug description:
  trash bin will not empty locks up

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.6
  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: Sat Feb  7 00:24:18 2015
  DistUpgraded: 2014-08-23 11:35:14,510 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   ndiswrapper, 1.59, 3.13.0-44-generic, x86_64: installed
   ndiswrapper, 1.59, 3.13.0-45-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:3602]
 Subsystem: Hewlett-Packard Company Device [103c:3602]
  InstallationDate: Installed on 2014-08-23 (167 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 
(20140204)
  MachineType: Hewlett-Packard HP Pavilion dv5 Notebook PC
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=3dfaf310-04bd-441f-9441-71cd7d70b824 ro quiet splash vt.handoff=7
  

[Desktop-packages] [Bug 1418987] Re: cups usblp hangs with Sharp AR5316e printer

2015-02-06 Thread Damien Ulrich
** Description changed:

  hi all,
- Base informations : 
+ Base informations :
  
  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  Codename: trusty
  
  # uname -a
  Linux school 3.13.0-44-generic #73-Ubuntu SMP Tue Dec 16 00:22:43 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux
  
  # dpkg -l cups* | grep ii | awk '{ print $2\t$3 }'
  cups  1.7.2-0ubuntu1.2
  cups-browsed  1.0.52-0ubuntu1.2
  cups-client   1.7.2-0ubuntu1.2
  cups-common   1.7.2-0ubuntu1.2
  cups-core-drivers 1.7.2-0ubuntu1.2
  cups-daemon   1.7.2-0ubuntu1.2
  cups-filters  1.0.52-0ubuntu1.2
  cups-filters-core-drivers 1.0.52-0ubuntu1.2
  cups-pdf  2.6.1-9
  cups-pk-helper0.2.5-0ubuntu1
  cups-ppdc 1.7.2-0ubuntu1.2
  cups-server-common1.7.2-0ubuntu1.2
  
  # lsusb | grep Sharp
- Bus 007 Device 032: ID 04dd:9135 Sharp Corp. 
+ Bus 007 Device 032: ID 04dd:9135 Sharp Corp.
  
- # cat /etc/udev/rules.d/10-usbprinter.rules 
- SUBSYSTEM==usb, ATTR{idVendor}==04dd, ATTR{idProduct}==9135, 
MODE:=0660, GROUP:=lp 
+ # cat /etc/udev/rules.d/10-usbprinter.rules
+ SUBSYSTEM==usb, ATTR{idVendor}==04dd, ATTR{idProduct}==9135, 
MODE:=0660, GROUP:=lp
  
  # modinfo usblp | grep srcversion
  srcversion: BD8A318D5C286F1E78768B9
  
  Everytime I try to use usb port on /dev/usb/lp0
  with usb_printerid or /usr/lib/cups/backend/usb
  The usb connections starts hanging, with in dmesg :
  
  [ 4733.189816] usblp0: removed
  [ 4733.195557] usblp: can't set desired altsetting 0 on interface 0
  [ 4733.232192] usb 7-1: USB disconnect, device number 30
  [ 4733.600097] usb 7-1: new full-speed USB device number 31 using uhci_hcd
  [ 4733.809564] usb 7-1: New USB device found, idVendor=04dd, idProduct=9135
  [ 4733.809571] usb 7-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 4733.809576] usb 7-1: Product: AR-5316E
  [ 4733.809580] usb 7-1: Manufacturer: SHARP
  [ 4733.809584] usb 7-1: SerialNumber: 0502080312093024
  [ 4733.845699] usblp 7-1:1.0: usblp0: USB Bidirectional printer dev 31 if 0 
alt 0 proto 2 vid 0x04DD pid 0x9135
  [ 4734.899038] usblp0: removed
  
  but obtaining Unknow printer
  
  so I tried with this script to go further without identification :
  
- # cat /usr/lib/cups/backend/usblp0 
+ # cat /usr/lib/cups/backend/usblp0
  #! /bin/bash
  # Have debug info in /var/log/cups/error_log:
  set -x
  # Output device discovery information on stdout:
  if test $# = 0
  then echo 'direct usblp0:/dev/usb/lp0 Unknown any USB printer'
-  exit 0
+  exit 0
  fi
  # Have the input at fd0 (stdin) in any case:
  if test -n $6
  then exec $6
  fi
  # Infinite retries to access the device file:
  until cat /dev/null /dev/usb/lp0
  do echo 'INFO: cannot access /dev/usb/lp0 - retry in 30 seconds' 12
-sleep 30
+    sleep 30
  done
  echo 'INFO: sending data to /dev/usb/lp0' 12
  # Forward the data from stdin to the device file:
  if cat - /dev/usb/lp0
  then echo 'INFO:' 12
-  exit 0
+  exit 0
  else echo 'ERROR: failed to send data to /dev/usb/lp0' 12
-  exit 1
+  exit 1
  fi
  
  Configured with the Sharp AR-M207 PS Foomatic/Postscript 
  been told by a Sharp technician that it could be a similar driver for it
  
  but no chance, trying to print directly on /dev/usb/lp0 gives no page...
  
  I write a bug here, because I think it could be similar to bug #997040
  https://bugs.launchpad.net/ubuntu/+source/cups/+bug/997040
  
  PS: It's for a school ;)

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

Title:
  cups usblp hangs with Sharp AR5316e printer

Status in cups package in Ubuntu:
  New

Bug description:
  hi all,
  Base informations :

  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  Codename: trusty

  # uname -a
  Linux school 3.13.0-44-generic #73-Ubuntu SMP Tue Dec 16 00:22:43 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

  # dpkg -l cups* | grep ii | awk '{ print $2\t$3 }'
  cups  1.7.2-0ubuntu1.2
  cups-browsed  1.0.52-0ubuntu1.2
  cups-client   1.7.2-0ubuntu1.2
  cups-common   1.7.2-0ubuntu1.2
  cups-core-drivers 1.7.2-0ubuntu1.2
  cups-daemon   1.7.2-0ubuntu1.2
  cups-filters  1.0.52-0ubuntu1.2
  cups-filters-core-drivers 1.0.52-0ubuntu1.2
  cups-pdf  2.6.1-9
  cups-pk-helper0.2.5-0ubuntu1
  cups-ppdc 1.7.2-0ubuntu1.2
  cups-server-common1.7.2-0ubuntu1.2

  # lsusb | grep Sharp
  Bus 007 Device 032: ID 04dd:9135 Sharp Corp.

  # cat /etc/udev/rules.d/10-usbprinter.rules
  SUBSYSTEM==usb, ATTR{idVendor}==04dd, ATTR{idProduct}==9135, 
MODE:=0660, GROUP:=lp

  # modinfo usblp | grep srcversion
  srcversion: BD8A318D5C286F1E78768B9

  Everytime I try to use usb port on /dev/usb/lp0
  with usb_printerid or /usr/lib/cups/backend/usb
  The usb connections starts 

[Desktop-packages] [Bug 1026254] Re: Open with on folders was removed, Ubuntu should consider patching back

2015-02-06 Thread Doug McMahon
** Tags added: nosense utopic vivid

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

Title:
  Open with on folders was removed, Ubuntu should consider patching back

Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Note, bug has been open long enough to be fixed so who cares ... -
  If you wish this back,  ppa here -
  https://launchpad.net/~mc3man/+archive/nauty-open

  This rev removed the context option.
  http://bazaar.launchpad.net/~vcs-imports/nautilus/master-git/revision/16061

  While unlikely to be reconsidered upstream I know many Ubuntu users find the 
option handy.
  I guess this report could be considered an Opinion  like other opinions in 
Ubuntu land the validity of such rests solely on 'who' agrees or disagrees

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6
  Uname: Linux 3.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.3-0ubuntu4
  Architecture: amd64
  Date: Wed Jul 18 13:22:46 2012
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b'1043x619+132+204'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'165'
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120707)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1026254/+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 1416939] Re: Black screen when in nvidia mode after updating to kernel 3.13.0-45

2015-02-06 Thread Andy C
Ver similar/identical issue with my Acer Desktop System running Ubuntu 14.04 
AMD64 dual screen with Nvidia driver ver 331.113.
Upgraded the kernel to 3.13.0-45 today (6 Feb 2015) and GUI (Gnome Desktop) 
freezes after logon. Also 2nd screen appears to be be dead.
No such problems on prior kernel release 3.13.0-44.

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

Title:
  Black screen when in nvidia mode after updating to kernel  3.13.0-45

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed

Bug description:
  After I updated to kernel 3.13.0-45, I cannot use nvidia anymore. Whenever I 
try to switch to nvidia mode, my laptop screen goes black. I cannot even switch 
to terminal mode using ctrl+alt+F1. However, I can type the following without 
seeing anything on the screen: 
  first type my password to login and press enter (without seeing anythin). 
wait a little bit.
  ctrl+alt+T
  sudo prime-select intel (then password and hit Enter)
  sudo reboot

  The laptop reboots and then I get my screen again in intel mode. So it seems 
that while not being able to see anything with the black screen, everything is 
still working in background.
  This happens whatever the version of nvidia I am using.

  My laptop is a Lenovo T430. I am using ubuntu 14.04 and I am also
  using nvidia-prime. My kernel version is 3.13.0-45.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1416939/+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 1412602] Re: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a

2015-02-06 Thread Erick Brunzell
Perhaps oddly (perhaps not oddly at all) I decided to reboot and select
GNOME Classic rather than booting into the standard GNOME Shell and it
seems to work fine - no screen tearing or X-freezes under fairly heavy
use. So maybe nouveau itself is simply not capable of running GNOME
Shell.

I find that a bit odd as I'd assumed both use mutter but Tim could
probably provide some insight in that regard. I should probably try that
same kernel with Ubuntu in a Unity session to see what happens.

ATM I'm inclined to think that kernel fixes this specific issue, but
that other underlying issues exist in nouveau itself which may actually
be an Xorg issue beyond the scope of this bug  or is
it???

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

Title:
  No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a

Status in Accelerated Xorg driver for nVidia cards:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New
Status in linux source package in Trusty:
  Confirmed
Status in xserver-xorg-video-nouveau source package in Trusty:
  New
Status in linux source package in Utopic:
  Confirmed
Status in xserver-xorg-video-nouveau source package in Utopic:
  New
Status in linux source package in Vivid:
  Confirmed
Status in xserver-xorg-video-nouveau source package in Vivid:
  New

Bug description:
  I've been testing the Ubuntu GNOME Vivid daily images in anticipation
  of Alpha 2 and I noticed that with this specific hardware I get no
  graphics at all other than a blank screen (see attached photo):

  AMD Sempron Processor LE-1250 @ 2.2 GHz
  nVidia C61 [GeForce 7025 / nForce 630a] (rev a2)
  nVidia MCP61 High Definition Audio (rev a2)
  nVidia MCP61 Ethernet (rev a2)
  2GB DDR2 RAM

  In fact I never even get as far as the screen offering to Try or
  Install, but I can enter the Advanced Boot Options screen and select
  either Try or Install from there, but with both options I still get
  the same blank screen.

  Further testing reveals the same results with Ubuntu and Ubuntu GNOME
  but I found that both the Xubuntu and Lubuntu images will boot
  properly on this box so I installed Lubuntu and then installed the
  ubuntu-desktop, ubuntu-gnome-desktop, and gnome-session-flashback
  meta-packages just to try some things.

  After doing so I found that the Unity, GNOME Shell, Gnome Classic, and
  Flashback w/Compiz sessions produce broken graphics just as the Ubuntu
  GNOME and Ubuntu live images do. So basically Compiz and Mutter both
  fail to display any usable UI. OTOH both the Lubuntu and Flashback
  w/Metacity sessions work just fine.

  I next opened the Additional drivers UI and chose nvidia-304.125
  (current) and all DE's perform quite well with the proprietary drivers
  so I deduced that nouveau might be the culprit.

  The last known working Ubuntu and Ubuntu GNOME live images are
  14.04.1. I hadn't tried Utopic on this box yet but it's also a fail.
  I'll try the proposed 14.04.2 images ASAP (probably after Vivid Alpha
  2 is released).

  But I see no point in trying to fix this for Utopic (or even 14.04.2
  if it's effected) because of the 9 month life-cycle for Utopic and the
  continued availability of the 14.04.1 images. In fact I'd be cool with
  this not being fixed until 16.04 as long as it's documented so people
  know what versions will and will not work.

  I'm probably forgetting something but that's all I can think of ATM.
  Sorry in advance if I did this totally wrong.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon Jan 19 17:41:32 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Biostar Microtech Int'l Corp Device [1565:1405]
  InstallationDate: Installed on 2015-01-19 (0 days ago)
  InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150118)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 046d:c52e Logitech, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: BIOSTAR Group N68SB-M2S
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-9-generic 
root=UUID=acf0fd65-0d6d-4da6-9532-2adc558bc0a7 ro quiet splash 
init=/lib/systemd/systemd
  

[Desktop-packages] [Bug 1417651] Re: Lenovo W520: display for one screen stretched over both when docked

2015-02-06 Thread Rockwalrus
The external monitor connected to the dock doesn't get detected by
nouveau at all, so it doesn't occur in this form.  This problem occurred
in Trusty as well.  Before that I was using a different configuration,
so I don't know if it would have occurred.  It looks like 331.113 is the
latest version available.

** Changed in: xorg (Ubuntu)
   Status: Incomplete = New

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

Title:
  Lenovo W520: display for one screen stretched over both when docked

Status in xorg package in Ubuntu:
  New

Bug description:
  When using the proprietary Nvidia drivers 331.113, the output from one
  window is often stretched to cover both by Unity. One thing that I
  noticed is that the standard xrandr-based Displays panel in System
  Settings shows both outputs, but nvidia-settings shows only the
  external monitor.

  WORKAROUND: Use another window manager.

  WORKAROUND: In Unity, manually configure the display output locations
  and sizes in ccsm.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.113  Mon Dec  1 21:08:13 
PST 2014
   GCC version:  gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6)
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu8.1
  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: Tue Feb  3 11:00:10 2015
  DistUpgraded: 2015-02-02 14:33:00,623 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:21d1]
   NVIDIA Corporation GF108GLM [Quadro 1000M] [10de:0dfa] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Lenovo Device [17aa:21d1]
  InstallationDate: Installed on 2013-01-29 (735 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MachineType: LENOVO 42763JU
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=9109c691-e957-4565-9b36-125458c0d242 ro quiet splash 
resume=UUID=9109c691e95745659b36125458c0d242:0x194ac758 crashkernel=384M-:128M
  SourcePackage: xorg
  UpgradeStatus: Upgraded to utopic on 2015-02-02 (0 days ago)
  dmi.bios.date: 07/26/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8BET62WW (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42763JU
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8BET62WW(1.42):bd07/26/2013:svnLENOVO:pn42763JU:pvrThinkPadW520:rvnLENOVO:rn42763JU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42763JU
  dmi.product.version: ThinkPad W520
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
  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.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Mon Feb  2 18:16:27 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16562
   vendor LEN
  xserver.version: 2:1.16.0-1ubuntu1.2

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

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

[Desktop-packages] [Bug 1126185] Re: baobag count up or show size badly

2015-02-06 Thread Forest
I have this problem on ubuntu 14.04 LTS with baobab 3.8.2.

Baobab is telling me that a cifs-mounted directory is 182 GiB, while
Thunar reports the correct size of 55 GiB.

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

Title:
  baobag count up or show size badly

Status in baobab package in Ubuntu:
  Confirmed

Bug description:
  i have a problem with baobad

  when baobab do analys show that /home/administrator uses 88GB

  but when show directories below it shows size about 1-2GB

  WHERE IS THE REST 86 GB !!!

  see enclosure

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: baobab 3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35
  Uname: Linux 3.2.0-36-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  Date: Fri Feb 15 13:45:37 2013
  InstallationMedia:
   
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: baobab
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/baobab/+bug/1126185/+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 1126185] Re: baobag count up or show size badly

2015-02-06 Thread Forest
When run on the cifs server, du -sh also reports 55G. When run on the
client machine, it reports 170G, unless I use the --apparent-size
option, which makes it report the correct value. It seems that baobab
needs to be modified to act like du --apparent-size when it operates on
cifs-mounted directories.

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

Title:
  baobag count up or show size badly

Status in baobab package in Ubuntu:
  Confirmed

Bug description:
  i have a problem with baobad

  when baobab do analys show that /home/administrator uses 88GB

  but when show directories below it shows size about 1-2GB

  WHERE IS THE REST 86 GB !!!

  see enclosure

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: baobab 3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35
  Uname: Linux 3.2.0-36-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  Date: Fri Feb 15 13:45:37 2013
  InstallationMedia:
   
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: baobab
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/baobab/+bug/1126185/+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 1395802] Re: Mutter 3.14 / Gnome-shell 3.14 doesnt load with Nvidia-Prime when NVIDIA is selected

2015-02-06 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-prime (Ubuntu)
   Status: New = Confirmed

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

Title:
  Mutter 3.14 / Gnome-shell 3.14 doesnt load with Nvidia-Prime when
  NVIDIA is selected

Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Version: 14.10 Utopic AMD64
  Nvidia-Prime Version: Nvidia-Prime 0.6.7
  Nvidia Driver Version: Nvidia-331
  Graphic Cards: Intel HD 3000 Sandy Bridge, Nvidia 540M  
  Xrandr Version: 1.4.1
  Xorg Version: X.Org X Server 1.16.0
  X Protocol Version 11, Revision 0

  Mutter / Gnome-Shell Doesnt Load and Crashes With Following Error if
  NVIDIA Card is selected:

  X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  30 (RRSetOutputPrimary)
  Serial number of failed request:  169
  Current serial number in output stream:  172

  Gnome 3.14 session runs fine with intel card selected.

  --

  Xorg.conf File Output:

  Section ServerLayout
  Identifier layout
  Screen 0 nvidia
  Inactive intel
  EndSection

  Section Device
  Identifier intel
  Driver intel
  BusID PCI:0@0:2:0
  Option AccelMethod SNA
  EndSection

  Section Screen
  Identifier intel
  Device intel
  EndSection

  Section Device
  Identifier nvidia
  Driver nvidia
  BusID PCI:1@0:0:0
  Option ConstrainCursor off
  EndSection

  Section Screen
  Identifier nvidia
  Device nvidia
  Option AllowEmptyInitialConfiguration on
  Option IgnoreDisplayDevices CRT
  EndSection
   
  -- End

  GPU-Manager Log Output:

  log_file: /var/log/gpu-manager.log
  last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
  new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
  grep dmesg status 256
  dmesg status 256 == 0? No
  Is nvidia loaded? yes
  Was nvidia unloaded? no
  Is nvidia blacklisted? no
  Is fglrx loaded? no
  Was fglrx unloaded? no
  Is fglrx blacklisted? no
  Is intel loaded? yes
  Is radeon loaded? no
  Is radeon blacklisted? no
  Is nouveau loaded? no
  Is nouveau blacklisted? yes
  Is fglrx kernel module available? no
  Is nvidia kernel module available? yes
  Vendor/Device Id: 8086:116
  BusID PCI:0@0:2:0
  Is boot vga? yes
  Vendor/Device Id: 10de:df4
  BusID PCI:1@0:0:0
  Is boot vga? no
  Skipping /dev/dri/card1, driven by nvidia-drm
  Skipping /dev/dri/card0, driven by i915
  Skipping /dev/dri/card1, driven by nvidia-drm
  Skipping /dev/dri/card0, driven by i915
  Skipping /dev/dri/card1, driven by nvidia-drm
  Found /dev/dri/card0, driven by i915
  output 0:
LVDS connector
  Number of connected outputs for /dev/dri/card0: 1
  Does it require offloading? yes
  last cards number = 1
  Has amd? no
  Has intel? yes
  Has nvidia? yes
  How many cards? 2
  The number of cards has changed!
  Has the system changed? Yes
  main_arch_path x86_64-linux-gnu, other_arch_path i386-linux-gnu
  Current alternative: /usr/lib/nvidia-331-updates/ld.so.conf
  Current core alternative: (null)
  Is nvidia enabled? yes
  Is fglrx enabled? no
  Is mesa enabled? no
  Is pxpress enabled? no
  Is prime enabled? no
  Is nvidia available? yes
  Is fglrx available? no
  Is fglrx-core available? no
  Is mesa available? yes
  Is pxpress available? no
  Is prime available? yes
  System configuration has changed
  Intel IGP detected
  Intel hybrid system
  Nvidia driver version 331.89 detected
  intel_matches: 1, nvidia_matches: 1, intel_set: 1, nvidia_set: 1 
x_options_matches: 4, accel_method_matches: 1
  No need to modify xorg.conf. Path: /etc/X11/xorg.conf
  No need to change the current bbswitch status

  -- End

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1395802/+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 1222356] Re: ** (apport-gtk:3020): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a

2015-02-06 Thread Mathew Hodson
** Bug watch added: Debian Bug tracker #732618
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732618

** Also affects: at-spi2-core (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732618
   Importance: Unknown
   Status: Unknown

** Package changed: apport (Ubuntu) = at-spi2-core (Ubuntu)

** Summary changed:

- ** (apport-gtk:3020): WARNING **: Couldn't register with accessibility bus: 
Did not receive a reply. Possible causes include: the remote application did 
not send a reply, the message bus security policy blocked the reply, the reply 
timeout expired, or the network connection was broken.
+ Couldn't register with accessibility bus: Did not receive a reply.

** Summary changed:

- Couldn't register with accessibility bus: Did not receive a reply.
+ WARNING: Couldn't register with accessibility bus: Did not receive a reply.

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

Title:
  WARNING: Couldn't register with accessibility bus: Did not receive a
  reply.

Status in at-spi2-core package in Ubuntu:
  Confirmed
Status in at-spi2-core package in Debian:
  Unknown

Bug description:
  The following warnings/errors appear after calling ubuntu-bug

  ** (apport-gtk:3020): WARNING **: Couldn't register with accessibility
  bus: Did not receive a reply. Possible causes include: the remote
  application did not send a reply, the message bus security policy
  blocked the reply, the reply timeout expired, or the network
  connection was broken.

  (process:4192): GLib-CRITICAL **: g_slice_set_config: assertion
  'sys_page_size == 0' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: apport-gtk 2.12.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Sun Sep  8 10:54:01 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-09-01 (371 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120823.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to saucy on 2013-09-05 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1222356/+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 1022488] Re: [region]: does not modify /etc/default/keyboard

2015-02-06 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-control-center (Ubuntu)
   Status: New = Confirmed

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

Title:
  [region]: does not modify /etc/default/keyboard

Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  After fresh installation of Ubuntu 12.04 I have changed the settings of 
switching between keyboard layouts. Unfortunately the new settings work maximum 
until a reboot or even some applications stop usage of the new settings during 
current session.
  Some investigations show up that file /etc/default/keyboard was not 
modified during implementation of settings.
  After manual change of the file switch between layouts works as expected, but 
further attempts to change toggle combination of keys or keyboard indicator for 
layouts via gnome-control-center do not work.
  --- 
  ApportVersion: 2.0.1-0ubuntu11
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  Package: gnome-control-center 1:3.4.2-0ubuntu0.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
  Tags:  precise
  Uname: Linux 3.2.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3
   deja-dup22.0-0ubuntu2
   gnome-bluetooth 3.2.2-0ubuntu5
   indicator-datetime  0.3.94-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1022488/+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 876446] Re: at-spi2-registryd crashed with SIGSEGV in __libc_start_main()

2015-02-06 Thread Mathew Hodson
The similar crash in saucy was fixed in bug #1037357.

The trace service couldn't process this original report in order to get
sufficient information for the developers because of outdated packages.

** Changed in: at-spi2-core (Ubuntu)
   Status: Confirmed = Invalid

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

Title:
  at-spi2-registryd crashed with SIGSEGV in __libc_start_main()

Status in at-spi2-core package in Ubuntu:
  Invalid

Bug description:
  1. I have the Orca screen reader enabled at the moment.
  2. I'm suffering from Bug #876406: Orca is not really functional on my system 
at the moment, because no speech synthesizer is installed.

  I'm not sure what might have caused this crash.  If it helps, I think
  the only apps I had open (other than Orca) was Firefox and gnome-
  terminal.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: at-spi2-core 2.2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 17 13:14:29 2011
  ExecutablePath: /usr/lib/at-spi2-core/at-spi2-registryd
  ProcCmdline: /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, user)
  SegvAnalysis:
   Segfault happened at: 0x403f7a:  mov0x8(%rax),%rcx
   PC (0x00403f7a) ok
   source 0x8(%rax) (0x0008) not located in a known VMA region (needed 
readable region)!
   destination %rcx ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: at-spi2-core
  StacktraceTop:
   ?? ()
   __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
   ?? ()
   ?? ()
   ?? ()
  Title: at-spi2-registryd crashed with SIGSEGV in __libc_start_main()
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (3 days ago)
  UserGroups: adm admin cdrom dialout dip fax floppy fuse plugdev tape video
  XsessionErrors:
   (nautilus:2146): Gtk-CRITICAL **: gtk_action_set_visible: assertion 
`GTK_IS_ACTION (action)' failed
   (nautilus:2146): Gtk-CRITICAL **: gtk_action_set_visible: assertion 
`GTK_IS_ACTION (action)' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/876446/+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 1416939] Re: Black screen when in nvidia mode after updating to kernel 3.13.0-45

2015-02-06 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-graphics-drivers-331 (Ubuntu)
   Status: New = Confirmed

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

Title:
  Black screen when in nvidia mode after updating to kernel  3.13.0-45

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed

Bug description:
  After I updated to kernel 3.13.0-45, I cannot use nvidia anymore. Whenever I 
try to switch to nvidia mode, my laptop screen goes black. I cannot even switch 
to terminal mode using ctrl+alt+F1. However, I can type the following without 
seeing anything on the screen: 
  first type my password to login and press enter (without seeing anythin). 
wait a little bit.
  ctrl+alt+T
  sudo prime-select intel (then password and hit Enter)
  sudo reboot

  The laptop reboots and then I get my screen again in intel mode. So it seems 
that while not being able to see anything with the black screen, everything is 
still working in background.
  This happens whatever the version of nvidia I am using.

  My laptop is a Lenovo T430. I am using ubuntu 14.04 and I am also
  using nvidia-prime. My kernel version is 3.13.0-45.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1416939/+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 1173033] Re: at-spi2-registryd crashes with SIGSEGV

2015-02-06 Thread Mathew Hodson
*** This bug is a duplicate of bug 1037357 ***
https://bugs.launchpad.net/bugs/1037357

** Changed in: at-spi2-core (Ubuntu)
   Status: Confirmed = Fix Released

** This bug has been marked a duplicate of bug 1037357
   at-spi2-registryd crashed with SIGSEGV in register_client()

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

Title:
  at-spi2-registryd crashes with SIGSEGV

Status in Assistive Technology Service Provider Interface:
  Fix Released
Status in at-spi2-core package in Ubuntu:
  Fix Released

Bug description:
  Each time when I log in, after some time I get an error popup that at-
  spi2-registr has crashed.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: at-spi2-core 2.4.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.2.0-40.64-generic-pae 3.2.40
  Uname: Linux 3.2.0-40-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.2
  Architecture: i386
  Date: Fri Apr 26 08:29:53 2013
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 
(20120423)
  MarkForUpload: True
  SourcePackage: at-spi2-core
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/at-spi/+bug/1173033/+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 1412602] Re: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a

2015-02-06 Thread Erick Brunzell
@ Joseph Salisbury,

There seemed to be some improvement in Ubuntu GNOME Utopic with the
amd64 version of 3.16.7-031607-generic, at least I was able to boot that
kernel w/o adding the nouveau.config=NvMSI=0 boot parameter, but then
after spending a couple of minutes fiddling around when I attempted to
open the System Settings UI the screen tore and X froze. So nouveau is
still a failure with that specific GPU.

I doubt it's arch specific so I'll move on to testing the Vivid mainline
kernel next.

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

Title:
  No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a

Status in Accelerated Xorg driver for nVidia cards:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New
Status in linux source package in Trusty:
  Confirmed
Status in xserver-xorg-video-nouveau source package in Trusty:
  New
Status in linux source package in Utopic:
  Confirmed
Status in xserver-xorg-video-nouveau source package in Utopic:
  New
Status in linux source package in Vivid:
  Confirmed
Status in xserver-xorg-video-nouveau source package in Vivid:
  New

Bug description:
  I've been testing the Ubuntu GNOME Vivid daily images in anticipation
  of Alpha 2 and I noticed that with this specific hardware I get no
  graphics at all other than a blank screen (see attached photo):

  AMD Sempron Processor LE-1250 @ 2.2 GHz
  nVidia C61 [GeForce 7025 / nForce 630a] (rev a2)
  nVidia MCP61 High Definition Audio (rev a2)
  nVidia MCP61 Ethernet (rev a2)
  2GB DDR2 RAM

  In fact I never even get as far as the screen offering to Try or
  Install, but I can enter the Advanced Boot Options screen and select
  either Try or Install from there, but with both options I still get
  the same blank screen.

  Further testing reveals the same results with Ubuntu and Ubuntu GNOME
  but I found that both the Xubuntu and Lubuntu images will boot
  properly on this box so I installed Lubuntu and then installed the
  ubuntu-desktop, ubuntu-gnome-desktop, and gnome-session-flashback
  meta-packages just to try some things.

  After doing so I found that the Unity, GNOME Shell, Gnome Classic, and
  Flashback w/Compiz sessions produce broken graphics just as the Ubuntu
  GNOME and Ubuntu live images do. So basically Compiz and Mutter both
  fail to display any usable UI. OTOH both the Lubuntu and Flashback
  w/Metacity sessions work just fine.

  I next opened the Additional drivers UI and chose nvidia-304.125
  (current) and all DE's perform quite well with the proprietary drivers
  so I deduced that nouveau might be the culprit.

  The last known working Ubuntu and Ubuntu GNOME live images are
  14.04.1. I hadn't tried Utopic on this box yet but it's also a fail.
  I'll try the proposed 14.04.2 images ASAP (probably after Vivid Alpha
  2 is released).

  But I see no point in trying to fix this for Utopic (or even 14.04.2
  if it's effected) because of the 9 month life-cycle for Utopic and the
  continued availability of the 14.04.1 images. In fact I'd be cool with
  this not being fixed until 16.04 as long as it's documented so people
  know what versions will and will not work.

  I'm probably forgetting something but that's all I can think of ATM.
  Sorry in advance if I did this totally wrong.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon Jan 19 17:41:32 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Biostar Microtech Int'l Corp Device [1565:1405]
  InstallationDate: Installed on 2015-01-19 (0 days ago)
  InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150118)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 046d:c52e Logitech, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: BIOSTAR Group N68SB-M2S
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-9-generic 
root=UUID=acf0fd65-0d6d-4da6-9532-2adc558bc0a7 ro quiet splash 
init=/lib/systemd/systemd
  SourcePackage: xserver-xorg-video-nouveau
  UdevLog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 06/24/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  

[Desktop-packages] [Bug 1390628] Re: Mouse pointer invisible after upgrade to Ubuntu 14.10

2015-02-06 Thread Cyprian Guerra
Just to expand on the issue as an Ubuntu GNOME 14.10 user: the mouse
pointer is invisible on login screen (GDM 3.14.1), in overview and when
hovering over the top bar, left dock, run dialog (alt+F2),
notifications, message try or any context menu / drop-down list these
surfaces generate (GNOME Shell 3.14.3). It does, however, display
correctly on desktop surface as well as in all other applications.

The property `active` of  `gsettings set org.gnome.settings-
daemon.plugins.cursor' is indeed set to `true` but setting it to `false`
doesn't help (tried to reset, restart and finally reboot afterwards -
all to no avail).

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

Title:
  Mouse pointer invisible after upgrade to Ubuntu 14.10

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Debian:
  New

Bug description:
  After upgrading from Xubuntu 14.04 to 14.10, the mouse pointer became
  invisible AFTER the user session start. This is why it looks like an
  XFCE problem (although it might be another problem with Xorg or the
  graphics stack triggered by XFCE).

  The mouse works perfectly in the login page, and when logging in with
  an user, it works fine when the XFCE logo is shown while starting the
  session, but afterwards, a graphics mode seems to change (I can see
  some activity in Xorg.log) and after that I can't see the mouse
  pointer anymore. The mouse works, the pointer is just invisible. I can
  even use it through VNC, I can see the VNC client showing the pointer
  perfectly too.

  This is rendering my computer virtually unusable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1390628/+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 1412602] Re: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a

2015-02-06 Thread Tim
Lance, gnome-classic is gnome-shell with a bunch of extensions, so for
classic to work and Shell not does seem odd. Was the issue in gnome-
shell repeatable or a one of crash?

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

Title:
  No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a

Status in Accelerated Xorg driver for nVidia cards:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New
Status in linux source package in Trusty:
  Confirmed
Status in xserver-xorg-video-nouveau source package in Trusty:
  New
Status in linux source package in Utopic:
  Confirmed
Status in xserver-xorg-video-nouveau source package in Utopic:
  New
Status in linux source package in Vivid:
  Confirmed
Status in xserver-xorg-video-nouveau source package in Vivid:
  New

Bug description:
  I've been testing the Ubuntu GNOME Vivid daily images in anticipation
  of Alpha 2 and I noticed that with this specific hardware I get no
  graphics at all other than a blank screen (see attached photo):

  AMD Sempron Processor LE-1250 @ 2.2 GHz
  nVidia C61 [GeForce 7025 / nForce 630a] (rev a2)
  nVidia MCP61 High Definition Audio (rev a2)
  nVidia MCP61 Ethernet (rev a2)
  2GB DDR2 RAM

  In fact I never even get as far as the screen offering to Try or
  Install, but I can enter the Advanced Boot Options screen and select
  either Try or Install from there, but with both options I still get
  the same blank screen.

  Further testing reveals the same results with Ubuntu and Ubuntu GNOME
  but I found that both the Xubuntu and Lubuntu images will boot
  properly on this box so I installed Lubuntu and then installed the
  ubuntu-desktop, ubuntu-gnome-desktop, and gnome-session-flashback
  meta-packages just to try some things.

  After doing so I found that the Unity, GNOME Shell, Gnome Classic, and
  Flashback w/Compiz sessions produce broken graphics just as the Ubuntu
  GNOME and Ubuntu live images do. So basically Compiz and Mutter both
  fail to display any usable UI. OTOH both the Lubuntu and Flashback
  w/Metacity sessions work just fine.

  I next opened the Additional drivers UI and chose nvidia-304.125
  (current) and all DE's perform quite well with the proprietary drivers
  so I deduced that nouveau might be the culprit.

  The last known working Ubuntu and Ubuntu GNOME live images are
  14.04.1. I hadn't tried Utopic on this box yet but it's also a fail.
  I'll try the proposed 14.04.2 images ASAP (probably after Vivid Alpha
  2 is released).

  But I see no point in trying to fix this for Utopic (or even 14.04.2
  if it's effected) because of the 9 month life-cycle for Utopic and the
  continued availability of the 14.04.1 images. In fact I'd be cool with
  this not being fixed until 16.04 as long as it's documented so people
  know what versions will and will not work.

  I'm probably forgetting something but that's all I can think of ATM.
  Sorry in advance if I did this totally wrong.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon Jan 19 17:41:32 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Biostar Microtech Int'l Corp Device [1565:1405]
  InstallationDate: Installed on 2015-01-19 (0 days ago)
  InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150118)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 046d:c52e Logitech, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: BIOSTAR Group N68SB-M2S
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-9-generic 
root=UUID=acf0fd65-0d6d-4da6-9532-2adc558bc0a7 ro quiet splash 
init=/lib/systemd/systemd
  SourcePackage: xserver-xorg-video-nouveau
  UdevLog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 06/24/2010
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: N68SB-M2S
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.chassis.version: N68SB-M2S
  dmi.modalias: 

Re: [Desktop-packages] [Bug 1275353] Re: Make HPLIP working with Python 3

2015-02-06 Thread Dimitri John Ledkov
On 6 February 2015 at 12:46, dino99 1275...@bugs.launchpad.net wrote:
 Note: to avoid upcoming upgrading issues, it should be preferable to
 remove the 3.15.2 packages from proposed archive


huh? vivid-proposed must not be used by humans, and should not be
enabled during development stage of the release.
it is guaranteed to contain broken packages, and has upgrade skew.
vivid suite on the other hand is safe-guarded away from such breaks.

-- 
Regards,

Dimitri.

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

Title:
  Make HPLIP working with Python 3

Status in HP Linux Imaging and Printing:
  In Progress
Status in hplip package in Ubuntu:
  Fix Released
Status in hplip source package in Trusty:
  Confirmed
Status in hplip package in Fedora:
  New

Bug description:
  In Ubuntu Linux we want to switch over completely to Python 3 and are
  on the way to eliminate everything which needs Python 2.

  Therefore I want to know whether HPLIP is already tested with Python 3
  at HP and whether there was already effort on adapting HPLIP to Python
  3.

  As Python 3 will also get standard in the other distros I would
  appreciate very much if HPLIP could be switched over to using Python
  3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1275353/+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 1235745] Re: at-spi2-registryd crashed with SIGSEGV in __libc_start_main()

2015-02-06 Thread Mathew Hodson
*** This bug is a duplicate of bug 1037357 ***
https://bugs.launchpad.net/bugs/1037357

** This bug has been marked a duplicate of bug 1037357
   at-spi2-registryd crashed with SIGSEGV in register_client()

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

Title:
  at-spi2-registryd crashed with SIGSEGV in __libc_start_main()

Status in at-spi2-core package in Ubuntu:
  Confirmed

Bug description:
  at-spi2-registryd crashed after system upgrade and migration from
  unity to gdb/gnome. Not sure about the reason, but hope that apport-
  retracer can produce a readable stacktrace.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: at-spi2-core 2.10.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-8-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Sat Oct  5 21:38:30 2013
  ExecutablePath: /usr/lib/at-spi2-core/at-spi2-registryd
  InstallationDate: Installed on 2012-02-05 (608 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120201.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
  SegvAnalysis:
   Segfault happened at: 0x7f8671735a77:mov0x8(%rax),%rcx
   PC (0x7f8671735a77) ok
   source 0x8(%rax) (0x0008) not located in a known VMA region (needed 
readable region)!
   destination %rcx ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: at-spi2-core
  StacktraceTop:
   ?? ()
   __libc_start_main (main=0x7f86717357a0, argc=2, ubp_av=0x7fffc6533c08, 
init=optimized out, fini=optimized out, rtld_fini=optimized out, 
stack_end=0x7fffc6533bf8) at libc-start.c:260
   ?? ()
  Title: at-spi2-registryd crashed with SIGSEGV in __libc_start_main()
  UpgradeStatus: Upgraded to saucy on 2013-05-19 (139 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1235745/+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 1126185] Re: baobag count up or show size badly

2015-02-06 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: baobab (Ubuntu)
   Status: New = Confirmed

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

Title:
  baobag count up or show size badly

Status in baobab package in Ubuntu:
  Confirmed

Bug description:
  i have a problem with baobad

  when baobab do analys show that /home/administrator uses 88GB

  but when show directories below it shows size about 1-2GB

  WHERE IS THE REST 86 GB !!!

  see enclosure

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: baobab 3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35
  Uname: Linux 3.2.0-36-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  Date: Fri Feb 15 13:45:37 2013
  InstallationMedia:
   
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: baobab
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/baobab/+bug/1126185/+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 1222356] Re: WARNING: Couldn't register with accessibility bus: Did not receive a reply.

2015-02-06 Thread Bug Watch Updater
** Changed in: at-spi2-core (Debian)
   Status: Unknown = Fix Released

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

Title:
  WARNING: Couldn't register with accessibility bus: Did not receive a
  reply.

Status in at-spi2-core package in Ubuntu:
  Confirmed
Status in at-spi2-core package in Debian:
  Fix Released

Bug description:
  The following warnings/errors appear after calling ubuntu-bug

  ** (apport-gtk:3020): WARNING **: Couldn't register with accessibility
  bus: Did not receive a reply. Possible causes include: the remote
  application did not send a reply, the message bus security policy
  blocked the reply, the reply timeout expired, or the network
  connection was broken.

  (process:4192): GLib-CRITICAL **: g_slice_set_config: assertion
  'sys_page_size == 0' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: apport-gtk 2.12.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Sun Sep  8 10:54:01 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-09-01 (371 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120823.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to saucy on 2013-09-05 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1222356/+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 1419217] [NEW] gnome-terminal displays unreadble letters in main window and title

2015-02-06 Thread Karl-Philipp Richter
Public bug reported:

unclear whether the letters belong to a charset or are just random junk
bytes, see attached screenshot for details. This might be related to an
invokation of `cat /dev/urandom`, but the issues can't be reproduced
constantly, but multiple times.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: gnome-terminal 3.6.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Feb  7 04:00:45 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-01-26 (11 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  gnome-terminal displays unreadble letters in main window and title

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  unclear whether the letters belong to a charset or are just random
  junk bytes, see attached screenshot for details. This might be related
  to an invokation of `cat /dev/urandom`, but the issues can't be
  reproduced constantly, but multiple times.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gnome-terminal 3.6.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb  7 04:00:45 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-01-26 (11 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1419217/+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 222208]

2015-02-06 Thread EricP
Hi Leho, I'm now using Postbox, which still has the bug (once each
session I must click OK on a password prompt, but the name/password are
already filled in), but apparently Postbox is not compatible with this
add-on.

Were you having the same problem and using this add-on made the problem
disappear? I don't quite understand, because it's clear that my password
is already saved in the password database, so I don't understand how
this add-on would help.

If it really does fix it, then I'll install Thunderbird and fix my
profile, which presumably would then work correctly in Postbox.

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

Title:
  user-id and password not sent automatically for rss-feed

Status in Mozilla Thunderbird Mail and News:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: thunderbird

  This is a bug I have seen for quite some time.  I am in the make
  hardy the best release there ever was-mood today and have brought
  myself to really reporting every single bit of problem I have put off
  for so long so somebody with the needed skills has a chance to fix it.

  I subscribe to an RSS feed hosted on a password-protected https-site
  in Thunderbird.  TB works fine but periodically asks me for the
  password although I have marked save password with password manager
  in the dialog.  In fact, the necessary fields are displayed filled in,
  but the pop-up comes back to me from time to time and I have to hit
  the OK button.

  I have set up a test installation which is exactly the same as the one
  I am having problems with at https://clients.leggewie.biz/tester/.
  The ssl-certificate is from cacert.org, so your browser might throw
  that up at first.  The user you need to get in is tb-tester and the
  password is launchpad.  The RSS feed is at
  
https://clients.leggewie.biz/tester/index.php?title=Special:Recentchangesfeed=rss
  When you susbscribe to that in TB and save the login credentials, you
  should have TB nagging you from time to time to with a login screen.

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

2015-02-06 Thread Joshua Cranmer
Comment on attachment 8551328
Backend changes

Review of attachment 8551328:
-

::: mailnews/mime/src/mimedrft.cpp
@@ +1203,5 @@
}
  }
  else
  {
 +  from = MimeHeaders_get(mdd-headers, HEADER_FROM, false, false);

This hunk seems unnecessary?

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

Title:
  Editing the From field for the current email only (as text, not
  dropdown)

Status in Mozilla Thunderbird Mail and News:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: thunderbird

  I want to quite often use a particular email address (e.g. for writing
  to a mailing list), where I do not have added the email address to the
  account settings yet.

  However, Thunderbird does not allow to edit the From field, but only
  provides the configured email addresses in a dropdown.

  It would be nice, if you could also edit the From field in a text
  input.

  KMail provides this, for example, and there appear to be some
  extensions for it, but I'd like to avoid using an addon for this, but
  rather think it's a nice feature to have by default.

  I could imagine, that the last entry in the dropdown would say
  Edit... or Custom... and change the dropdown into a text field.

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  NonfreeKernelModules: nvidia
  Package: mozilla-thunderbird 2.0.0.21+nobinonly-0ubuntu1
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: thunderbird
  Uname: Linux 2.6.28-11-generic i686

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

2015-02-06 Thread Leho Kraav
https://addons.mozilla.org/en-US/thunderbird/addon/saved-password-
editor/?src=search allows us to create custom entries in the password
database, effectively filling the gap of this bug going unfixed for
ages. Awesomeness.

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

Title:
  user-id and password not sent automatically for rss-feed

Status in Mozilla Thunderbird Mail and News:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: thunderbird

  This is a bug I have seen for quite some time.  I am in the make
  hardy the best release there ever was-mood today and have brought
  myself to really reporting every single bit of problem I have put off
  for so long so somebody with the needed skills has a chance to fix it.

  I subscribe to an RSS feed hosted on a password-protected https-site
  in Thunderbird.  TB works fine but periodically asks me for the
  password although I have marked save password with password manager
  in the dialog.  In fact, the necessary fields are displayed filled in,
  but the pop-up comes back to me from time to time and I have to hit
  the OK button.

  I have set up a test installation which is exactly the same as the one
  I am having problems with at https://clients.leggewie.biz/tester/.
  The ssl-certificate is from cacert.org, so your browser might throw
  that up at first.  The user you need to get in is tb-tester and the
  password is launchpad.  The RSS feed is at
  
https://clients.leggewie.biz/tester/index.php?title=Special:Recentchangesfeed=rss
  When you susbscribe to that in TB and save the login credentials, you
  should have TB nagging you from time to time to with a login screen.

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

2015-02-06 Thread Mkmelin+mozilla
Postbox 3 - the latest - is (according to mozillazine) using the same platform 
that was Thunderbird 7.
So, at this point it probably has most of the  security holes that were fixed 
in mozilla products the last 4 years.

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

Title:
  user-id and password not sent automatically for rss-feed

Status in Mozilla Thunderbird Mail and News:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: thunderbird

  This is a bug I have seen for quite some time.  I am in the make
  hardy the best release there ever was-mood today and have brought
  myself to really reporting every single bit of problem I have put off
  for so long so somebody with the needed skills has a chance to fix it.

  I subscribe to an RSS feed hosted on a password-protected https-site
  in Thunderbird.  TB works fine but periodically asks me for the
  password although I have marked save password with password manager
  in the dialog.  In fact, the necessary fields are displayed filled in,
  but the pop-up comes back to me from time to time and I have to hit
  the OK button.

  I have set up a test installation which is exactly the same as the one
  I am having problems with at https://clients.leggewie.biz/tester/.
  The ssl-certificate is from cacert.org, so your browser might throw
  that up at first.  The user you need to get in is tb-tester and the
  password is launchpad.  The RSS feed is at
  
https://clients.leggewie.biz/tester/index.php?title=Special:Recentchangesfeed=rss
  When you susbscribe to that in TB and save the login credentials, you
  should have TB nagging you from time to time to with a login screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/08/+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 1306857] Re: apport authentication windows isn't localized

2015-02-06 Thread Aron Xu
** Summary changed:

- apport 认证窗口含有未汉化内容
+ apport authentication windows isn't localized

** Description changed:

- approt 认证窗口含有未汉化内容,见auth.png
+ apport authentication windows isn't localized, see auth.png

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

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

** Branch linked: lp:~happyaron/apport/lp-1306857

** Changed in: ubuntukylin
   Status: New = In Progress

** Changed in: apport (Ubuntu)
 Assignee: (unassigned) = Aron Xu (happyaron)

** Changed in: apport (Ubuntu)
   Importance: Undecided = Medium

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

Title:
  apport authentication windows isn't localized

Status in Apport crash detection/reporting:
  New
Status in Ubuntu Kylin:
  In Progress
Status in apport package in Ubuntu:
  New

Bug description:
  apport authentication windows isn't localized, see auth.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1306857/+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 1418295] Re: Black screen after resuming from suspend

2015-02-06 Thread Chris Wilson
Hmm. Can you attach a new Xorg.0.log? Next time it freezes, gdb --pid
`pidof unity-panel-server` and type bt -- and please paste the output.

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

Title:
  Black screen after resuming from suspend

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

Bug description:
  Using Ubuntu 14.10 on a Lenovo Yoga 2, when I resume the laptop from
  suspend I frequently (around 50% of the time) get a blank black screen
  with a mouse cursor on it, and am unable to login or interact with the
  desktop at all. Often (also about 50% of the time) switching over to a
  text terminal and killing unity-panel-service --lockscreen-mode
  causes it to snap out of it and prompt me with the unlock dialog when
  I switch back to X.

  Using xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu8.1
  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 Feb  4 20:42:38 2015
  DistUpgraded: 2014-11-15 17:52:46,161 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.18, 3.16.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3978]
  InstallationDate: Installed on 2014-06-28 (221 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed 
root=UUID=d1c3a7eb-265e-441f-9aac-eb15636dfe61 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to utopic on 2014-11-15 (81 days ago)
  dmi.bios.date: 06/27/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN38WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN38WW:bd06/27/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
  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.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Mon Feb  2 11:10:08 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.0-1ubuntu1.2
  xserver.video_driver: intel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1418295/+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 1409200] Re: HWCursor artifacts on custom cursors using Intel driver

2015-02-06 Thread Chris Wilson
It's a combination of kernel bugs and -intel that have been long fixed
upstream.

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

Title:
  HWCursor artifacts on custom cursors using Intel driver

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

Bug description:
  In fresh install (even in live cd) when accessing some app / website
  that use custom cursor, it wil artifact, the cursor turns to a box
  with trailers pointers and diferent background.

  Example: when visiting http://foro.elhacker.net (spanish forum) 
  http://postimg.org/image/wlza8fbvd/

  Also happens when using VirtualBox with Windows (see Attachment) 
  http://postimg.org/image/8zzsr4cen/
  (Virtual Machine downloaded from 
https://www.modern.ie/es-es/virtualization-tools  - Windows 7 with IE 9)

  A workarround is disable HWCursor using xorg.conf or xorg.conf.d
  files. But that wont let me do multiple monitor with two gpu's
  (discrete gpu and intel igpu)

  Hardware:
  Asus P8H77-M PRO
  Intel i5 2500

  Other Info
  Description:Ubuntu 14.10
  Release:14.10

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Jan 10 00:37:19 2015
  InstallationDate: Installed on 2014-10-24 (77 days ago)
  InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  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-intel/+bug/1409200/+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 1418295] Re: Black screen after resuming from suspend

2015-02-06 Thread Chris Wilson
Also worth attaching a dmesg from after the freeze just in case there is
anything interesting there as well.

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

Title:
  Black screen after resuming from suspend

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

Bug description:
  Using Ubuntu 14.10 on a Lenovo Yoga 2, when I resume the laptop from
  suspend I frequently (around 50% of the time) get a blank black screen
  with a mouse cursor on it, and am unable to login or interact with the
  desktop at all. Often (also about 50% of the time) switching over to a
  text terminal and killing unity-panel-service --lockscreen-mode
  causes it to snap out of it and prompt me with the unlock dialog when
  I switch back to X.

  Using xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu8.1
  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 Feb  4 20:42:38 2015
  DistUpgraded: 2014-11-15 17:52:46,161 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.18, 3.16.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3978]
  InstallationDate: Installed on 2014-06-28 (221 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed 
root=UUID=d1c3a7eb-265e-441f-9aac-eb15636dfe61 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to utopic on 2014-11-15 (81 days ago)
  dmi.bios.date: 06/27/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN38WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN38WW:bd06/27/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
  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.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Mon Feb  2 11:10:08 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.0-1ubuntu1.2
  xserver.video_driver: intel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1418295/+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 1418295] Re: Black screen after resuming from suspend

2015-02-06 Thread Treviño
Mh... Did you ever click on an indicator before/after suspend (like to
suspend when the losckreen was there)?

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

Title:
  Black screen after resuming from suspend

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

Bug description:
  Using Ubuntu 14.10 on a Lenovo Yoga 2, when I resume the laptop from
  suspend I frequently (around 50% of the time) get a blank black screen
  with a mouse cursor on it, and am unable to login or interact with the
  desktop at all. Often (also about 50% of the time) switching over to a
  text terminal and killing unity-panel-service --lockscreen-mode
  causes it to snap out of it and prompt me with the unlock dialog when
  I switch back to X.

  Using xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu8.1
  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 Feb  4 20:42:38 2015
  DistUpgraded: 2014-11-15 17:52:46,161 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.18, 3.16.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3978]
  InstallationDate: Installed on 2014-06-28 (221 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed 
root=UUID=d1c3a7eb-265e-441f-9aac-eb15636dfe61 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to utopic on 2014-11-15 (81 days ago)
  dmi.bios.date: 06/27/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN38WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN38WW:bd06/27/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
  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.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Mon Feb  2 11:10:08 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.0-1ubuntu1.2
  xserver.video_driver: intel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1418295/+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 1342271] Re: lpq has long hang before completion.

2015-02-06 Thread ubuntu-tester
Hello,

I use remote printers over CUPS server and I have the same issue on my
computers installed with Ubuntu 14.04 (no problem with Ubuntu 12.04)  :

$ time lpq printer
printer is ready
no entries

real  1m0.082s
user  0m0.010s
sys   0m0.007s

If you need information or if you want me to perform tests, don't
hesitate to ask me.

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

Title:
  lpq has long hang before completion.

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 12.04 does not have this long hang issue.

  See attached straces - one from a machine with 12.04 and one to the
  same remote cups server using a 14.04 client.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups-client 1.7.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Tue Jul 15 14:26:40 2014
  InstallationDate: Installed on 2014-06-18 (27 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-30-generic 
root=UUID=a86d2294-0ef2-4c23-b951-ea3199bad7e7 ro rootflags=subvol=@ quiet 
splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2202
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 LE R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2202:bd12/12/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1342271/+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 1414753] Re: Chromium browser 39.0.2171.65 does not load policies

2015-02-06 Thread Launchpad Bug Tracker
This bug was fixed in the package chromium-browser -
40.0.2214.94-0ubuntu1.1120

---
chromium-browser (40.0.2214.94-0ubuntu1.1120) vivid; urgency=medium

  * Upstream release 40.0.2214.94.
  * Upstream release 40.0.2214.93.
  * Upstream release 40.0.2214.91. (LP: #1414753)
- CVE-2014-7923: Memory corruption in ICU.
- CVE-2014-7924: Use-after-free in IndexedDB.
- CVE-2014-7925: Use-after-free in WebAudio.
- CVE-2014-7926: Memory corruption in ICU.
- CVE-2014-7927: Memory corruption in V8.
- CVE-2014-7928: Memory corruption in V8.
- CVE-2014-7930: Use-after-free in DOM.
- CVE-2014-7931: Memory corruption in V8.
- CVE-2014-7929: Use-after-free in DOM.
- CVE-2014-7932: Use-after-free in DOM.
- CVE-2014-7933: Use-after-free in FFmpeg.
- CVE-2014-7934: Use-after-free in DOM.
- CVE-2014-7935: Use-after-free in Speech.
- CVE-2014-7936: Use-after-free in Views.
- CVE-2014-7937: Use-after-free in FFmpeg.
- CVE-2014-7938: Memory corruption in Fonts.
- CVE-2014-7939: Same-origin-bypass in V8.
- CVE-2014-7940: Uninitialized-value in ICU.
- CVE-2014-7941: Out-of-bounds read in UI.
- CVE-2014-7942: Uninitialized-value in Fonts.
- CVE-2014-7943: Out-of-bounds read in Skia.
- CVE-2014-7944: Out-of-bounds read in PDFium.
- CVE-2014-7945: Out-of-bounds read in PDFium.
- CVE-2014-7946: Out-of-bounds read in Fonts.
- CVE-2014-7947: Out-of-bounds read in PDFium.
- CVE-2014-7948: Caching error in AppCache.
  * debian/patch/search-credit: Don't force client in GOOG suggestions search.
(LP: #1398900)
  * debian/patches/dri3-within-sandbox: Backport V41 sandbox, fixing DRI3.
(LP: #1378627)
  * debian/patches/macro-templates-not-match: Remove. No longer necessary.
  * debian/patches/arm-neon.patch: Kill armv7=neon assumption. Fix typos.
  * debian/rules: chrpath for all packages.  (LP: #141)
 -- Chad MILLER chad.mil...@canonical.com   Fri, 30 Jan 2015 15:48:09 -0500

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete = Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7923

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7924

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7925

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7926

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7927

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7928

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7929

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7930

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7931

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7932

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7933

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7934

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7935

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7936

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7937

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7938

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7939

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7940

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7941

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7942

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7943

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7944

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7945

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7946

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7947

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7948

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

Title:
  Chromium browser 39.0.2171.65 does not load policies

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Following the information I gathered from

  http://www.chromium.org/administrators/linux-quick-start
  http://www.chromium.org/administrators/linux-quick-start
  https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1373802

  I tried to set a simple policy for the browser.
  All I did is create a file policy.json in /etc/chromium-
  browser/policies/managed with the following content:

  {
HomepageLocation: www.chromium.org
  }

  However when starting chromium there is no sign of the policy: about:policy 
  does not show any policy being set. Running 'strings /usr/lib/chromium-
  

[Desktop-packages] [Bug 1410765] Re: GIMP uses more system resources than necessary

2015-02-06 Thread Bug Watch Updater
** Changed in: gimp
   Status: New = Incomplete

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

Title:
  GIMP uses more system resources than necessary

Status in The GNU Image Manipulation Program (GIMP):
  Incomplete
Status in The Linux Lowlatency Kernel:
  Unknown
Status in gimp package in Ubuntu:
  New
Status in gimp package in Debian:
  Unknown

Bug description:
  I am using GNU Image Manipulation Program version 2.8.14 on Ubuntu 14.10 x64 
on
  my AMD Phonom II X4 machine packed with 8GB DDR3 RAM and more than the
  recommended amount of SWAP-Space found in multiple locations throughout my PC,
  and even though I have all this caching space and more plus a powerful
  processor, GIMP still eats my computer's system resources alive even while
  doing some quick editing and touch-ups, specifically when using the Heal tool 
-
  The window will freeze up and continue what it's doing in the background, but
  for that time being, it won't let me do much besides that. 

  It has now gotten to a point where GIMP uses so many system resources all at
  one time where it locks up my (USB 2.0) keyboard for all apps and won't let me
  use the keyboard at all until GIMP is done doing what it is doing. 

  I have even switched to the LowLatency Linux Kernel to help speed up my PC and
  keep only needed background tasks while using minimal RAM. 


  
  See below for a HardInfo chart I pasted stating my Operating System
  information:

  
  -Version-
  Kernel: Linux 3.16.0-29-lowlatency (x86_64)
  Compiled: #39-Ubuntu SMP PREEMPT Mon Dec 15 22:55:59 UTC 2014
  C Library: Unknown
  Default C Compiler: GNU C Compiler version 4.9.1 (Ubuntu
  4.9.1-16ubuntu6) 
  Distribution: Ubuntu 14.10
  -Current Session-
  Computer Name: SDB
  User Name: jeb (Jeb Eldridge)
  Home Directory: /home/jeb
  Desktop Environment: Unity (ubuntu)
  -Misc-
  Uptime: 1 day, 16 hours and 52 minutes
  Load Average: 0.29, 0.44, 0.76

  
  Attached is also a screenshot with About This Computer info shown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gimp/+bug/1410765/+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 1418262] Re: apport hook to detect wayland sessions

2015-02-06 Thread Launchpad Bug Tracker
This bug was fixed in the package apport - 2.16-0ubuntu1

---
apport (2.16-0ubuntu1) vivid; urgency=medium

  * New upstream release:
- Add a new method ProblemReport.extract_keys() which writes binary keys
  (which can be very large) directly to files without loading them all
  into memory first. Use that in apport-unpack. Thanks Louis Bouchard!
  (LP: #1307413)
- launchpad backend: Work with Python 3, now that launchpadlib exists for
  Python 3. (LP: #1153671)
- apport-bug, apport-gtk: Also check for $WAYLAND_SESSION, to use
  apport-gtk instead of apport-cli under Wayland. Thanks Tim Lunn.
  (LP: #1418766)
- apport-gtk: When running under Wayland, avoid Gdk/Wnck operation for
  setting crash window modal to the PID of the crashed window; these only
  work under X11.
- Don't install the test suite any more, to save 1 MB of installed space.
  It can be run out of trunk easily enough, and distributions can install
  it from tests/ if they desire.
- hookutils, attach_root_command_outputs(): Fix UnicodeDecodeError crash
  for non-textual values. (LP: #1370259)
- ui.py: Only provide a UI to hooks if the crash db will accept the
  report. This avoids asking questions if the report is merely sent to
  whoopsie for Ubuntu stable releases. Thanks Brian Murrary.
  (LP: #1084979)
- whoopsie-upload-all: Add package information to the report before
  calling package hooks. Thanks Brian Murray.
- Fix check for available terminal when checking whether to display the
  Examine locally button.
  * Add general hook for detecting Wayland sessions and tagging them with
wayland-session. Thanks Timm Lunn! (LP: #1418262)
  * debian/tests/upstream-system: Copy tests from source tree, as
/usr/share/apport/testsuite/ does not exist any more.
 -- Martin Pitt martin.p...@ubuntu.com   Fri, 06 Feb 2015 10:11:30 +0100

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

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

Title:
  apport hook to detect wayland sessions

Status in Ubuntu GNOME:
  New
Status in apport package in Ubuntu:
  Fix Released

Bug description:
  Now that we have an experimental GNOME wayland session in vivid, it
  would be somewhat useful for apport to detect if a bug report is from
  a wayland session. It probably makes sense for this to be global
  since other projects will eventually offer wayland sessions as well.
  Not sure on the best place for this to live though in apport or in
  wayland packaging or elsewhere?

  detecting WAYLAND_DISPLAY env is probably enough to detect a running
  session, and there may be a few other useful env variables such as
  (GDK/CLUTTER)_BACKEND etc

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apport 2.15.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4
  Uname: Linux 3.18.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportLog:
   
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Feb  5 10:51:38 2015
  InstallationDate: Installed on 2012-09-23 (864 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 Quantal Quetzal - Alpha 
amd64(20120922)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1418262/+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 1084979] Re: Submitting error report asks confounding questions

2015-02-06 Thread Launchpad Bug Tracker
This bug was fixed in the package apport - 2.16-0ubuntu1

---
apport (2.16-0ubuntu1) vivid; urgency=medium

  * New upstream release:
- Add a new method ProblemReport.extract_keys() which writes binary keys
  (which can be very large) directly to files without loading them all
  into memory first. Use that in apport-unpack. Thanks Louis Bouchard!
  (LP: #1307413)
- launchpad backend: Work with Python 3, now that launchpadlib exists for
  Python 3. (LP: #1153671)
- apport-bug, apport-gtk: Also check for $WAYLAND_SESSION, to use
  apport-gtk instead of apport-cli under Wayland. Thanks Tim Lunn.
  (LP: #1418766)
- apport-gtk: When running under Wayland, avoid Gdk/Wnck operation for
  setting crash window modal to the PID of the crashed window; these only
  work under X11.
- Don't install the test suite any more, to save 1 MB of installed space.
  It can be run out of trunk easily enough, and distributions can install
  it from tests/ if they desire.
- hookutils, attach_root_command_outputs(): Fix UnicodeDecodeError crash
  for non-textual values. (LP: #1370259)
- ui.py: Only provide a UI to hooks if the crash db will accept the
  report. This avoids asking questions if the report is merely sent to
  whoopsie for Ubuntu stable releases. Thanks Brian Murrary.
  (LP: #1084979)
- whoopsie-upload-all: Add package information to the report before
  calling package hooks. Thanks Brian Murray.
- Fix check for available terminal when checking whether to display the
  Examine locally button.
  * Add general hook for detecting Wayland sessions and tagging them with
wayland-session. Thanks Timm Lunn! (LP: #1418262)
  * debian/tests/upstream-system: Copy tests from source tree, as
/usr/share/apport/testsuite/ does not exist any more.
 -- Martin Pitt martin.p...@ubuntu.com   Fri, 06 Feb 2015 10:11:30 +0100

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

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

Title:
  Submitting error report asks confounding questions

Status in Apport crash detection/reporting:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Trusty:
  In Progress
Status in apport source package in Utopic:
  In Progress

Bug description:
  Test Case
  -
  1) start totem in a terminal
  2) pkill -11 totem
  3) observe apport crash dialog
  4) make sure send an error report is checked
  5) click Leave Closed
  6) Observe an apport dialog about How would you describe the issue?

  With the version of apport from -proposed the apport dialog will not
  appear.

  
  Original report
  ---
  Ubuntu 12.04
  apport 2.6.1-0ubuntu10, Ubuntu 12.10
  apport 2.12.5-0ubuntu2.2, Ubuntu 13.10

  1. In a release version of Ubuntu, trigger an error in something that
  has Apport hooks.

  What happens: You are asked questions which are often false and
  usually not understandable. For example:

  It seems you have modified the contents of '/etc/cups/cupsd.conf'.
  Would you like to add the contents of it to your bug report?
  https://launchpadlibrarian.net/124496439/apport-question.png -- You
  haven't, and there is no bug report.

  Thanks for reporting this bug on unity. Is the issue you are reporting 
purely graphical (will report more information about your graphic configuration 
and will report the bug against compiz)?
  
https://launchpadlibrarian.net/117922627/apport%20%28ubuntu-bug%20unity%20%231%29.png
 -- Purely grapical is unexplained, and there is no bug report.

  Did your system recently lock up or require a hard reboot? -- What's
  a hard reboot?

  What should happen: You are not asked any questions.

  If all reporters of actual bugs are expected to use English, hiding
  these questions from non-reporters might also resolve bug 855337.

  [Originally reported by Katie Taylor.]

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1084979/+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 1153671] Re: Port to python3-launchpadlib

2015-02-06 Thread Launchpad Bug Tracker
This bug was fixed in the package apport - 2.16-0ubuntu1

---
apport (2.16-0ubuntu1) vivid; urgency=medium

  * New upstream release:
- Add a new method ProblemReport.extract_keys() which writes binary keys
  (which can be very large) directly to files without loading them all
  into memory first. Use that in apport-unpack. Thanks Louis Bouchard!
  (LP: #1307413)
- launchpad backend: Work with Python 3, now that launchpadlib exists for
  Python 3. (LP: #1153671)
- apport-bug, apport-gtk: Also check for $WAYLAND_SESSION, to use
  apport-gtk instead of apport-cli under Wayland. Thanks Tim Lunn.
  (LP: #1418766)
- apport-gtk: When running under Wayland, avoid Gdk/Wnck operation for
  setting crash window modal to the PID of the crashed window; these only
  work under X11.
- Don't install the test suite any more, to save 1 MB of installed space.
  It can be run out of trunk easily enough, and distributions can install
  it from tests/ if they desire.
- hookutils, attach_root_command_outputs(): Fix UnicodeDecodeError crash
  for non-textual values. (LP: #1370259)
- ui.py: Only provide a UI to hooks if the crash db will accept the
  report. This avoids asking questions if the report is merely sent to
  whoopsie for Ubuntu stable releases. Thanks Brian Murrary.
  (LP: #1084979)
- whoopsie-upload-all: Add package information to the report before
  calling package hooks. Thanks Brian Murray.
- Fix check for available terminal when checking whether to display the
  Examine locally button.
  * Add general hook for detecting Wayland sessions and tagging them with
wayland-session. Thanks Timm Lunn! (LP: #1418262)
  * debian/tests/upstream-system: Copy tests from source tree, as
/usr/share/apport/testsuite/ does not exist any more.
 -- Martin Pitt martin.p...@ubuntu.com   Fri, 06 Feb 2015 10:11:30 +0100

** Changed in: apport (Ubuntu)
   Status: Triaged = Fix Released

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

Title:
  Port to python3-launchpadlib

Status in apport package in Ubuntu:
  Fix Released
Status in python-launchpadlib package in Ubuntu:
  Fix Released

Bug description:
  Apport-cli depends on python3-launchpadlib for some actions, but it is
  not installable (currently). For example,

  apport-cli -u 542452
  ERROR: The launchpadlib Python module is not installed. This functionality is 
not available.

  The current candidates for installation on raring only include python-
  launchpadlib (which is python2 based).  I believe this bug is
  relevant:

  https://bugs.launchpad.net/launchpadlib/+bug/1060734

  I'm  filing this against apport in the event raring is shipped without
  a python3-launchpadlib package. I would recommend updating the error
  to make what is needing to be installed more clear. IE,

  ERROR: The launchpadlib Python3 module is not installed
  (python3-launchpadlib). This functionality is not available.

  Also consider adding the library as a suggested dependency.  In
  addition, should the package not land, further steps may be required.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1153671/+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 1307413] Re: apport-unpack requires too much main memory to run

2015-02-06 Thread Launchpad Bug Tracker
This bug was fixed in the package apport - 2.16-0ubuntu1

---
apport (2.16-0ubuntu1) vivid; urgency=medium

  * New upstream release:
- Add a new method ProblemReport.extract_keys() which writes binary keys
  (which can be very large) directly to files without loading them all
  into memory first. Use that in apport-unpack. Thanks Louis Bouchard!
  (LP: #1307413)
- launchpad backend: Work with Python 3, now that launchpadlib exists for
  Python 3. (LP: #1153671)
- apport-bug, apport-gtk: Also check for $WAYLAND_SESSION, to use
  apport-gtk instead of apport-cli under Wayland. Thanks Tim Lunn.
  (LP: #1418766)
- apport-gtk: When running under Wayland, avoid Gdk/Wnck operation for
  setting crash window modal to the PID of the crashed window; these only
  work under X11.
- Don't install the test suite any more, to save 1 MB of installed space.
  It can be run out of trunk easily enough, and distributions can install
  it from tests/ if they desire.
- hookutils, attach_root_command_outputs(): Fix UnicodeDecodeError crash
  for non-textual values. (LP: #1370259)
- ui.py: Only provide a UI to hooks if the crash db will accept the
  report. This avoids asking questions if the report is merely sent to
  whoopsie for Ubuntu stable releases. Thanks Brian Murrary.
  (LP: #1084979)
- whoopsie-upload-all: Add package information to the report before
  calling package hooks. Thanks Brian Murray.
- Fix check for available terminal when checking whether to display the
  Examine locally button.
  * Add general hook for detecting Wayland sessions and tagging them with
wayland-session. Thanks Timm Lunn! (LP: #1418262)
  * debian/tests/upstream-system: Copy tests from source tree, as
/usr/share/apport/testsuite/ does not exist any more.
 -- Martin Pitt martin.p...@ubuntu.com   Fri, 06 Feb 2015 10:11:30 +0100

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

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

Title:
  apport-unpack requires too much main memory to run

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  when running apport-unpack on large apport reports (linux-image kernel
  dumps is a good example), it requires an enormous amount of main
  memory to run.

  An example is a 1.3Gb apport report that runs for more than 24 hours
  with more than 4Gb of RSS.

  The command should requires less memory to extract those big reports.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1307413/+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 1418932] [NEW] Stops scanning after a few pages, requires restart

2015-02-06 Thread Marius Gedminas
Public bug reported:

1. Try to scan an 18-page document: launch simple-scan
2. Press the scan button, get a page
3. Repeat for pages 2 to 7
4. Press the scan button again, get an error
5. Futilely retry a few times, try to unplug and re-plug the USB cable, nothing 
helps
6. Launch xsane, try to acquire image preview -- it works
7. Close xsane, Alt-Tab back to simple-scan, try again a few times -- same error
8. Save the incomplete document, close simple-scan, launch simple-scan agani
9. Try to scan again, it works now
10. Repeat for pages 9 to 18
11. Save the second incomplete half, search the Internet for solutions for 
stitching two PDF files together

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: simple-scan 3.14.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Feb  6 13:09:30 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-07-25 (925 days ago)
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
Lsusb:
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 4291WJF
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=36079681-53fc-4ca2-80ac-98321c07e8d2 ro quiet splash vt.handoff=7
SourcePackage: simple-scan
UpgradeStatus: Upgraded to utopic on 2015-02-05 (1 days ago)
dmi.bios.date: 07/18/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET69WW (1.39 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4291WJF
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn4291WJF:pvrThinkPadX220:rvnLENOVO:rn4291WJF:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4291WJF
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO

** Affects: simple-scan (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug gnome3-ppa third-party-packages utopic

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

Title:
  Stops scanning after a few pages, requires restart

Status in simple-scan package in Ubuntu:
  New

Bug description:
  1. Try to scan an 18-page document: launch simple-scan
  2. Press the scan button, get a page
  3. Repeat for pages 2 to 7
  4. Press the scan button again, get an error
  5. Futilely retry a few times, try to unplug and re-plug the USB cable, 
nothing helps
  6. Launch xsane, try to acquire image preview -- it works
  7. Close xsane, Alt-Tab back to simple-scan, try again a few times -- same 
error
  8. Save the incomplete document, close simple-scan, launch simple-scan agani
  9. Try to scan again, it works now
  10. Repeat for pages 9 to 18
  11. Save the second incomplete half, search the Internet for solutions for 
stitching two PDF files together

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: simple-scan 3.14.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Feb  6 13:09:30 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-07-25 (925 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 4291WJF
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=36079681-53fc-4ca2-80ac-98321c07e8d2 ro quiet splash vt.handoff=7
  SourcePackage: simple-scan
  UpgradeStatus: Upgraded to utopic on 2015-02-05 (1 days ago)
  dmi.bios.date: 07/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET69WW (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291WJF
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn4291WJF:pvrThinkPadX220:rvnLENOVO:rn4291WJF:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4291WJF
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

To manage notifications 

[Desktop-packages] [Bug 1418928] Re: New upstream microreleases 9.1.15, 9.3.6, 9.4.1

2015-02-06 Thread Martin Pitt
** Changed in: postgresql-9.4 (Ubuntu Utopic)
   Status: New = In Progress

** Changed in: postgresql-9.4 (Ubuntu Utopic)
 Assignee: (unassigned) = Martin Pitt (pitti)

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

Title:
  New upstream microreleases 9.1.15, 9.3.6, 9.4.1

Status in postgresql-8.4 package in Ubuntu:
  Invalid
Status in postgresql-9.1 package in Ubuntu:
  Invalid
Status in postgresql-9.3 package in Ubuntu:
  Invalid
Status in postgresql-9.4 package in Ubuntu:
  Fix Committed
Status in postgresql-8.4 source package in Lucid:
  New
Status in postgresql-9.1 source package in Precise:
  New
Status in postgresql-9.1 source package in Trusty:
  New
Status in postgresql-9.3 source package in Trusty:
  New
Status in postgresql-9.4 source package in Utopic:
  In Progress
Status in postgresql-9.4 source package in Vivid:
  Fix Committed

Bug description:
  PostgreSQL has released new versions yesterday:
  http://www.postgresql.org/about/news/1569/

  These fix a bunch of security issues, as well as the usual set of bug
  fixes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+bug/1418928/+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 1418937] Re: Import Clip Art is not working in 0.91

2015-02-06 Thread ~suv
You need gvfs (with http/https support, used via GIO) for this to work.
Not an inkscape issue - AFAIU this is about runtime config of the local
system, and its support for GIO modules (Glib).

(See also bug #943148 - packaging issue for new ocal dialog on osx)

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

** Tags added: linux openclipart

** Tags added: packaging

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

Title:
  Import Clip Art is not working in 0.91

Status in Inkscape: A Vector Drawing Tool:
  New
Status in inkscape package in Ubuntu:
  New

Bug description:
  I am trying to use the Import Clip Art... feature in inkscape 0.91,
  installed in a Kubuntu 14.04 from the following ppa repository:

  deb http://ppa.launchpad.net/inkscape.dev/stable/ubuntu trusty main

  $ apt-cache policy inkscape
  inkscape: 
 
Installed: 0.91.0+40~ubuntu14.04.1
Candidate: 0.91.0+40~ubuntu14.04.1
Version table:
   *** 0.91.0+40~ubuntu14.04.1 0
  500 http://ppa.launchpad.net/inkscape.dev/stable/ubuntu/ trusty/main 
amd64 Packages
  100 /var/lib/dpkg/status
   0.48.4-3ubuntu2 0
  500 http://no.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  
  The Import Clip Art dialog comes up, but no matter what I search I get no 
results.

  The following error is printed in the console:

  (inkscape:5338): glibmm-CRITICAL **: 
  unhandled exception (type Glib::Error) in signal handler:
  domain: g-io-error-quark
  code  : 15
  what  : The specified location is not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1418937/+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 1153671] Re: Port to python3-launchpadlib

2015-02-06 Thread Martin Pitt
Reopening, this isn't sufficient yet. I still need to flip the package
dependencies around once a fixed py3-lplib lands.

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

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

Title:
  Port to python3-launchpadlib

Status in apport package in Ubuntu:
  In Progress
Status in python-launchpadlib package in Ubuntu:
  Fix Released

Bug description:
  Apport-cli depends on python3-launchpadlib for some actions, but it is
  not installable (currently). For example,

  apport-cli -u 542452
  ERROR: The launchpadlib Python module is not installed. This functionality is 
not available.

  The current candidates for installation on raring only include python-
  launchpadlib (which is python2 based).  I believe this bug is
  relevant:

  https://bugs.launchpad.net/launchpadlib/+bug/1060734

  I'm  filing this against apport in the event raring is shipped without
  a python3-launchpadlib package. I would recommend updating the error
  to make what is needing to be installed more clear. IE,

  ERROR: The launchpadlib Python3 module is not installed
  (python3-launchpadlib). This functionality is not available.

  Also consider adding the library as a suggested dependency.  In
  addition, should the package not land, further steps may be required.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1153671/+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 1418928] [NEW] New upstream microreleases 9.1.15, 9.3.6, 9.4.1

2015-02-06 Thread Martin Pitt
Public bug reported:

PostgreSQL has released new versions yesterday:
http://www.postgresql.org/about/news/1569/

These fix a bunch of security issues, as well as the usual set of bug
fixes.

** Affects: postgresql-8.4 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: postgresql-9.1 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: postgresql-9.3 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: postgresql-9.4 (Ubuntu)
 Importance: Undecided
 Status: Fix Committed

** Affects: postgresql-8.4 (Ubuntu Lucid)
 Importance: Undecided
 Status: New

** Affects: postgresql-9.1 (Ubuntu Precise)
 Importance: Undecided
 Status: New

** Affects: postgresql-9.1 (Ubuntu Trusty)
 Importance: Undecided
 Status: New

** Affects: postgresql-9.3 (Ubuntu Trusty)
 Importance: Undecided
 Status: New

** Affects: postgresql-9.4 (Ubuntu Utopic)
 Importance: Undecided
 Status: New

** Affects: postgresql-9.4 (Ubuntu Vivid)
 Importance: Undecided
 Status: Fix Committed

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-0241

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-0242

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-0243

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-0244

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-8161

** Also affects: postgresql-9.3 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: postgresql-9.4 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: postgresql-9.1 (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Also affects: postgresql-9.3 (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Also affects: postgresql-9.4 (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Also affects: postgresql-9.1 (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: postgresql-9.3 (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: postgresql-9.4 (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: postgresql-9.1 (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: postgresql-9.3 (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: postgresql-9.4 (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: postgresql-9.1 (Ubuntu Lucid)
   Importance: Undecided
   Status: New

** Also affects: postgresql-9.3 (Ubuntu Lucid)
   Importance: Undecided
   Status: New

** Also affects: postgresql-9.4 (Ubuntu Lucid)
   Importance: Undecided
   Status: New

** Also affects: postgresql-9.1 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: postgresql-9.3 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: postgresql-9.4 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: postgresql-8.4 (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: postgresql-8.4 (Ubuntu Precise)

** No longer affects: postgresql-8.4 (Ubuntu Trusty)

** No longer affects: postgresql-8.4 (Ubuntu Utopic)

** No longer affects: postgresql-9.1 (Ubuntu Lucid)

** No longer affects: postgresql-9.4 (Ubuntu Trusty)

** No longer affects: postgresql-9.4 (Ubuntu Precise)

** No longer affects: postgresql-9.4 (Ubuntu Lucid)

** No longer affects: postgresql-8.4 (Ubuntu Vivid)

** Changed in: postgresql-8.4 (Ubuntu)
   Status: New = Invalid

** No longer affects: postgresql-9.1 (Ubuntu Vivid)

** No longer affects: postgresql-9.1 (Ubuntu Utopic)

** Changed in: postgresql-9.1 (Ubuntu)
   Status: New = Invalid

** No longer affects: postgresql-9.3 (Ubuntu Lucid)

** No longer affects: postgresql-9.3 (Ubuntu Vivid)

** No longer affects: postgresql-9.3 (Ubuntu Precise)

** No longer affects: postgresql-9.3 (Ubuntu Utopic)

** Changed in: postgresql-9.3 (Ubuntu)
   Status: New = Invalid

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

Title:
  New upstream microreleases 9.1.15, 9.3.6, 9.4.1

Status in postgresql-8.4 package in Ubuntu:
  Invalid
Status in postgresql-9.1 package in Ubuntu:
  Invalid
Status in postgresql-9.3 package in Ubuntu:
  Invalid
Status in postgresql-9.4 package in Ubuntu:
  Fix Committed
Status in postgresql-8.4 source package in Lucid:
  New
Status in postgresql-9.1 source package in Precise:
  New
Status in postgresql-9.1 source package in Trusty:
  New
Status in postgresql-9.3 source package in Trusty:
  New
Status in postgresql-9.4 source package in Utopic:
  New
Status in postgresql-9.4 source package in Vivid:
  Fix Committed

Bug description:
  PostgreSQL has released new versions yesterday:
  

[Desktop-packages] [Bug 1418928] Re: New upstream microreleases 9.1.15, 9.3.6, 9.4.1

2015-02-06 Thread Martin Pitt
https://launchpad.net/ubuntu/+source/postgresql-9.4/9.4.1-1 is in vivid-
proposed, but currently stuck on some reverse test dependency failures.

** Changed in: postgresql-9.4 (Ubuntu Vivid)
   Status: New = Fix Committed

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

Title:
  New upstream microreleases 9.1.15, 9.3.6, 9.4.1

Status in postgresql-8.4 package in Ubuntu:
  Invalid
Status in postgresql-9.1 package in Ubuntu:
  Invalid
Status in postgresql-9.3 package in Ubuntu:
  Invalid
Status in postgresql-9.4 package in Ubuntu:
  Fix Committed
Status in postgresql-8.4 source package in Lucid:
  New
Status in postgresql-9.1 source package in Precise:
  New
Status in postgresql-9.1 source package in Trusty:
  New
Status in postgresql-9.3 source package in Trusty:
  New
Status in postgresql-9.4 source package in Utopic:
  New
Status in postgresql-9.4 source package in Vivid:
  Fix Committed

Bug description:
  PostgreSQL has released new versions yesterday:
  http://www.postgresql.org/about/news/1569/

  These fix a bunch of security issues, as well as the usual set of bug
  fixes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+bug/1418928/+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 1240088] Re: add network (nm-applet) to login screen

2015-02-06 Thread Seyeong Kim
unity-greeter   0.2.9-0ubuntu1.5
network-manager-gnome   0.9.4.1-0ubuntu2.4 

** 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 network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1240088

Title:
  add network (nm-applet) to login screen

Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in unity-greeter package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Precise:
  Fix Committed
Status in unity-greeter source package in Precise:
  Fix Committed

Bug description:
  [Impact] 
   * User has a hard time to login via network, (krb5) if nm-applet is not 
accessible via login screen. 

  [Test Case]
  1) make sure the system is configure to authenticate via krb5
  2) login with user A and disconnect from the network via nm-applet, logout
  3) Try to login with user B

   a. Actual Results:
  User B is not able to authenticate because the system is not connected to the 
network so we are not able to talk to the krb servers

   b. Expected Results:
  Users should be able to use network manager from within unity greater and 
reconnect to the network before attempting to login.

  
  [Regression Potential] 
   * n/a . The patch is a backport from upstream

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1240088/+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 1418766] Re: ubuntu-bug launches in CLI mode under wayland session

2015-02-06 Thread Launchpad Bug Tracker
This bug was fixed in the package apport - 2.16-0ubuntu1

---
apport (2.16-0ubuntu1) vivid; urgency=medium

  * New upstream release:
- Add a new method ProblemReport.extract_keys() which writes binary keys
  (which can be very large) directly to files without loading them all
  into memory first. Use that in apport-unpack. Thanks Louis Bouchard!
  (LP: #1307413)
- launchpad backend: Work with Python 3, now that launchpadlib exists for
  Python 3. (LP: #1153671)
- apport-bug, apport-gtk: Also check for $WAYLAND_SESSION, to use
  apport-gtk instead of apport-cli under Wayland. Thanks Tim Lunn.
  (LP: #1418766)
- apport-gtk: When running under Wayland, avoid Gdk/Wnck operation for
  setting crash window modal to the PID of the crashed window; these only
  work under X11.
- Don't install the test suite any more, to save 1 MB of installed space.
  It can be run out of trunk easily enough, and distributions can install
  it from tests/ if they desire.
- hookutils, attach_root_command_outputs(): Fix UnicodeDecodeError crash
  for non-textual values. (LP: #1370259)
- ui.py: Only provide a UI to hooks if the crash db will accept the
  report. This avoids asking questions if the report is merely sent to
  whoopsie for Ubuntu stable releases. Thanks Brian Murrary.
  (LP: #1084979)
- whoopsie-upload-all: Add package information to the report before
  calling package hooks. Thanks Brian Murray.
- Fix check for available terminal when checking whether to display the
  Examine locally button.
  * Add general hook for detecting Wayland sessions and tagging them with
wayland-session. Thanks Timm Lunn! (LP: #1418262)
  * debian/tests/upstream-system: Copy tests from source tree, as
/usr/share/apport/testsuite/ does not exist any more.
 -- Martin Pitt martin.p...@ubuntu.com   Fri, 06 Feb 2015 10:11:30 +0100

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

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

Title:
  ubuntu-bug launches in CLI mode under wayland session

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  Launching ubuntu-bug from a terminal under wayland session launches in
  CLI mode, rather than in Xwayland. Presumably this is because $DISPLAY
  doesnt seem to be set under wayland by default.

  Perhaps apport should also check for WAYLAND_DISPLAY in
  ui_run_terminal(), since X is still available in that case via
  Xwayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apport 2.15.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4
  Uname: Linux 3.18.0-12-generic x86_64
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Feb  6 10:46:41 2015
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to vivid on 2015-01-09 (27 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1418766/+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 1418255] Re: /usr/share/session-migration/scripts/03_unity_first_run_stamp_move:OSError:/usr/share/session-migration/scripts/03_unity_first_run_stamp_move@35

2015-02-06 Thread Launchpad Bug Tracker
This bug was fixed in the package unity - 7.3.1+15.04.20150205-0ubuntu1

---
unity (7.3.1+15.04.20150205-0ubuntu1) vivid; urgency=medium

  [ Brandon Schaefer ]
  * Try to set the folder permission otherwise Handle permission error.
(LP: #1418255)

  [ Andrea Azzarone ]
  * Actually connect to changed::* signal in MenuManager.cpp. (LP:
#1411620)
  * Actually connect to changed::* signal in UnitySettings.cpp. (LP:
#1408212)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Thu, 05 Feb 2015 
17:27:47 +

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

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

Title:
  /usr/share/session-
  migration/scripts/03_unity_first_run_stamp_move:OSError:/usr/share
  /session-migration/scripts/03_unity_first_run_stamp_move@35

Status in Unity:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity.  This problem was most recently seen with version
  7.3.1+14.10.20141016-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/57a7a85987b3cae2d64f9afadcc51f008ef62e76
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1418255/+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 1418932] Re: Stops scanning after a few pages, requires restart

2015-02-06 Thread Marius Gedminas
Ah, the bug I filed last time was #1261440 and it was a different
situation (scanning failed in the middle of a page).

It's the same office scanner, though (HP Color LaserJet 2840).

The fact that simple-scan failed to scan the page several times in a row
and then succeeded after I restarted simple-scan (without touching the
USB cable or any scanner buttons) makes me suspect a software bug rather
than a hardware quirk.  If not in simple-scan itself, then maybe some
global state in libsane didn't get reset properly.

(I'm sure there are multiple bugs that interfere with my scanning.  I
had situations in the past where restarting simple-scan didn't help
either.)

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

Title:
  Stops scanning after a few pages, requires restart

Status in simple-scan package in Ubuntu:
  New

Bug description:
  1. Try to scan an 18-page document: launch simple-scan
  2. Press the scan button, get a page
  3. Repeat for pages 2 to 7
  4. Press the scan button again, get an error
  5. Futilely retry a few times, try to unplug and re-plug the USB cable, 
nothing helps
  6. Launch xsane, try to acquire image preview -- it works
  7. Close xsane, Alt-Tab back to simple-scan, try again a few times -- same 
error
  8. Save the incomplete document, close simple-scan, launch simple-scan agani
  9. Try to scan again, it works now
  10. Repeat for pages 9 to 18
  11. Save the second incomplete half, search the Internet for solutions for 
stitching two PDF files together

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: simple-scan 3.14.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Feb  6 13:09:30 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-07-25 (925 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 4291WJF
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=36079681-53fc-4ca2-80ac-98321c07e8d2 ro quiet splash vt.handoff=7
  SourcePackage: simple-scan
  UpgradeStatus: Upgraded to utopic on 2015-02-05 (1 days ago)
  dmi.bios.date: 07/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET69WW (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291WJF
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn4291WJF:pvrThinkPadX220:rvnLENOVO:rn4291WJF:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4291WJF
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1418932/+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 1418932] Re: Stops scanning after a few pages, requires restart

2015-02-06 Thread Marius Gedminas
I have vague memories of filing this bug in the past, reproducing the
issue, attaching a log file, and seeing libsane getting all the blame
(since it's libsane returning error codes from sane_read).

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

Title:
  Stops scanning after a few pages, requires restart

Status in simple-scan package in Ubuntu:
  New

Bug description:
  1. Try to scan an 18-page document: launch simple-scan
  2. Press the scan button, get a page
  3. Repeat for pages 2 to 7
  4. Press the scan button again, get an error
  5. Futilely retry a few times, try to unplug and re-plug the USB cable, 
nothing helps
  6. Launch xsane, try to acquire image preview -- it works
  7. Close xsane, Alt-Tab back to simple-scan, try again a few times -- same 
error
  8. Save the incomplete document, close simple-scan, launch simple-scan agani
  9. Try to scan again, it works now
  10. Repeat for pages 9 to 18
  11. Save the second incomplete half, search the Internet for solutions for 
stitching two PDF files together

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: simple-scan 3.14.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Feb  6 13:09:30 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-07-25 (925 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 4291WJF
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=36079681-53fc-4ca2-80ac-98321c07e8d2 ro quiet splash vt.handoff=7
  SourcePackage: simple-scan
  UpgradeStatus: Upgraded to utopic on 2015-02-05 (1 days ago)
  dmi.bios.date: 07/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET69WW (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291WJF
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn4291WJF:pvrThinkPadX220:rvnLENOVO:rn4291WJF:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4291WJF
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1418932/+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 1418932] Re: Stops scanning after a few pages, requires restart

2015-02-06 Thread Marius Gedminas
Unfortunately simple-scan doesn't do log rotation, so I don't have a
copy of ~/.cache/simple-scan/simple-scan.log with the failures.

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

Title:
  Stops scanning after a few pages, requires restart

Status in simple-scan package in Ubuntu:
  New

Bug description:
  1. Try to scan an 18-page document: launch simple-scan
  2. Press the scan button, get a page
  3. Repeat for pages 2 to 7
  4. Press the scan button again, get an error
  5. Futilely retry a few times, try to unplug and re-plug the USB cable, 
nothing helps
  6. Launch xsane, try to acquire image preview -- it works
  7. Close xsane, Alt-Tab back to simple-scan, try again a few times -- same 
error
  8. Save the incomplete document, close simple-scan, launch simple-scan agani
  9. Try to scan again, it works now
  10. Repeat for pages 9 to 18
  11. Save the second incomplete half, search the Internet for solutions for 
stitching two PDF files together

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: simple-scan 3.14.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Feb  6 13:09:30 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-07-25 (925 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 4291WJF
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=36079681-53fc-4ca2-80ac-98321c07e8d2 ro quiet splash vt.handoff=7
  SourcePackage: simple-scan
  UpgradeStatus: Upgraded to utopic on 2015-02-05 (1 days ago)
  dmi.bios.date: 07/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET69WW (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291WJF
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn4291WJF:pvrThinkPadX220:rvnLENOVO:rn4291WJF:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4291WJF
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1418932/+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 1418929] [NEW] package tex-common 4.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2015-02-06 Thread Jesús María Zamarreño
Public bug reported:

Was upgrading from 12.04 LTS to 14.04 LTS

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: tex-common 4.04
ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
Uname: Linux 3.13.0-45-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
Date: Fri Feb  6 12:03:27 2015
DuplicateSignature: package:tex-common:4.04:subprocess installed 
post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2012-07-27 (924 days ago)
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
PackageArchitecture: all
SourcePackage: tex-common
Title: package tex-common 4.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
UpgradeStatus: Upgraded to trusty on 2015-02-06 (0 days ago)

** Affects: tex-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package dist-upgrade need-duplicate-check trusty

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

Title:
  package tex-common 4.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  Was upgrading from 12.04 LTS to 14.04 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: tex-common 4.04
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Fri Feb  6 12:03:27 2015
  DuplicateSignature: package:tex-common:4.04:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2012-07-27 (924 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  PackageArchitecture: all
  SourcePackage: tex-common
  Title: package tex-common 4.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to trusty on 2015-02-06 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1418929/+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 1378627] Re: chromium-browser crashed with SIGSEGV

2015-02-06 Thread Launchpad Bug Tracker
This bug was fixed in the package chromium-browser -
40.0.2214.94-0ubuntu1.1120

---
chromium-browser (40.0.2214.94-0ubuntu1.1120) vivid; urgency=medium

  * Upstream release 40.0.2214.94.
  * Upstream release 40.0.2214.93.
  * Upstream release 40.0.2214.91. (LP: #1414753)
- CVE-2014-7923: Memory corruption in ICU.
- CVE-2014-7924: Use-after-free in IndexedDB.
- CVE-2014-7925: Use-after-free in WebAudio.
- CVE-2014-7926: Memory corruption in ICU.
- CVE-2014-7927: Memory corruption in V8.
- CVE-2014-7928: Memory corruption in V8.
- CVE-2014-7930: Use-after-free in DOM.
- CVE-2014-7931: Memory corruption in V8.
- CVE-2014-7929: Use-after-free in DOM.
- CVE-2014-7932: Use-after-free in DOM.
- CVE-2014-7933: Use-after-free in FFmpeg.
- CVE-2014-7934: Use-after-free in DOM.
- CVE-2014-7935: Use-after-free in Speech.
- CVE-2014-7936: Use-after-free in Views.
- CVE-2014-7937: Use-after-free in FFmpeg.
- CVE-2014-7938: Memory corruption in Fonts.
- CVE-2014-7939: Same-origin-bypass in V8.
- CVE-2014-7940: Uninitialized-value in ICU.
- CVE-2014-7941: Out-of-bounds read in UI.
- CVE-2014-7942: Uninitialized-value in Fonts.
- CVE-2014-7943: Out-of-bounds read in Skia.
- CVE-2014-7944: Out-of-bounds read in PDFium.
- CVE-2014-7945: Out-of-bounds read in PDFium.
- CVE-2014-7946: Out-of-bounds read in Fonts.
- CVE-2014-7947: Out-of-bounds read in PDFium.
- CVE-2014-7948: Caching error in AppCache.
  * debian/patch/search-credit: Don't force client in GOOG suggestions search.
(LP: #1398900)
  * debian/patches/dri3-within-sandbox: Backport V41 sandbox, fixing DRI3.
(LP: #1378627)
  * debian/patches/macro-templates-not-match: Remove. No longer necessary.
  * debian/patches/arm-neon.patch: Kill armv7=neon assumption. Fix typos.
  * debian/rules: chrpath for all packages.  (LP: #141)
 -- Chad MILLER chad.mil...@canonical.com   Fri, 30 Jan 2015 15:48:09 -0500

** Changed in: chromium-browser (Ubuntu)
   Status: Fix Committed = Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7923

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7924

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7925

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7926

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7927

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7928

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7929

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7930

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7931

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7932

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7933

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7934

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7935

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7936

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7937

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7938

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7939

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7940

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7941

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7942

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7943

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7944

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7945

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7946

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7947

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7948

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

Title:
  chromium-browser crashed with SIGSEGV

Status in Chromium Browser:
  Unknown
Status in Mesa:
  Won't Fix
Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser package in Debian:
  Confirmed
Status in chromium-browser package in Fedora:
  Unknown

Bug description:
  No idea what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: chromium-browser 37.0.2062.94-0ubuntu1~pkg1065
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  ApportVersion: 2.14.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Wed Oct  8 07:12:48 2014
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: 

[Desktop-packages] [Bug 1408212] Re: Turn on/off the Large Text in Universal Access, it doesn't work immediately

2015-02-06 Thread Launchpad Bug Tracker
This bug was fixed in the package unity - 7.3.1+15.04.20150205-0ubuntu1

---
unity (7.3.1+15.04.20150205-0ubuntu1) vivid; urgency=medium

  [ Brandon Schaefer ]
  * Try to set the folder permission otherwise Handle permission error.
(LP: #1418255)

  [ Andrea Azzarone ]
  * Actually connect to changed::* signal in MenuManager.cpp. (LP:
#1411620)
  * Actually connect to changed::* signal in UnitySettings.cpp. (LP:
#1408212)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Thu, 05 Feb 2015 
17:27:47 +

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1408212

Title:
  Turn on/off the Large Text in Universal Access, it doesn't work
  immediately

Status in Ubuntu Kylin:
  New
Status in Unity:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  Turn on/off the Large Text in Universal Access, it doesn't work
  immediately.

  打开或关闭大号文本,该设置不会立马生效

  Steps:
  1. Enter into system settings--Universal Access--Seeing
  2. Turn on/off the Large Text, check the result
  --Failed. It doesn't work immediately.

  Configuration:
  OS: Vivid x64 Daily Build 20150106

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntukylin/+bug/1408212/+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 1411620] Re: Unity requires restart after enabling always-show-menus or LIM

2015-02-06 Thread Launchpad Bug Tracker
This bug was fixed in the package unity - 7.3.1+15.04.20150205-0ubuntu1

---
unity (7.3.1+15.04.20150205-0ubuntu1) vivid; urgency=medium

  [ Brandon Schaefer ]
  * Try to set the folder permission otherwise Handle permission error.
(LP: #1418255)

  [ Andrea Azzarone ]
  * Actually connect to changed::* signal in MenuManager.cpp. (LP:
#1411620)
  * Actually connect to changed::* signal in UnitySettings.cpp. (LP:
#1408212)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Thu, 05 Feb 2015 
17:27:47 +

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

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

Title:
  Unity requires restart after enabling always-show-menus or LIM

Status in Unity:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  Unity requires restart after enabling always-show-menus or LIM. When
  I first tested the always-show-menus (about 3-4 weeks ago, by using
  Marco's branch), I don't remember it requiring a restart.

  Also, enabling LIM in Ubuntu 14.04 and 14.10 doesn't require
  restarting Unity but it does with the latest Unity in Ubuntu 15.04
  Vivid Vervet.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20150115-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic i686
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Jan 16 13:23:00 2015
  InstallationDate: Installed on 2015-01-16 (0 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20150116)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1411620/+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 1415555] Re: error while loading shared libraries: libui_base.so

2015-02-06 Thread Launchpad Bug Tracker
This bug was fixed in the package chromium-browser -
40.0.2214.94-0ubuntu1.1120

---
chromium-browser (40.0.2214.94-0ubuntu1.1120) vivid; urgency=medium

  * Upstream release 40.0.2214.94.
  * Upstream release 40.0.2214.93.
  * Upstream release 40.0.2214.91. (LP: #1414753)
- CVE-2014-7923: Memory corruption in ICU.
- CVE-2014-7924: Use-after-free in IndexedDB.
- CVE-2014-7925: Use-after-free in WebAudio.
- CVE-2014-7926: Memory corruption in ICU.
- CVE-2014-7927: Memory corruption in V8.
- CVE-2014-7928: Memory corruption in V8.
- CVE-2014-7930: Use-after-free in DOM.
- CVE-2014-7931: Memory corruption in V8.
- CVE-2014-7929: Use-after-free in DOM.
- CVE-2014-7932: Use-after-free in DOM.
- CVE-2014-7933: Use-after-free in FFmpeg.
- CVE-2014-7934: Use-after-free in DOM.
- CVE-2014-7935: Use-after-free in Speech.
- CVE-2014-7936: Use-after-free in Views.
- CVE-2014-7937: Use-after-free in FFmpeg.
- CVE-2014-7938: Memory corruption in Fonts.
- CVE-2014-7939: Same-origin-bypass in V8.
- CVE-2014-7940: Uninitialized-value in ICU.
- CVE-2014-7941: Out-of-bounds read in UI.
- CVE-2014-7942: Uninitialized-value in Fonts.
- CVE-2014-7943: Out-of-bounds read in Skia.
- CVE-2014-7944: Out-of-bounds read in PDFium.
- CVE-2014-7945: Out-of-bounds read in PDFium.
- CVE-2014-7946: Out-of-bounds read in Fonts.
- CVE-2014-7947: Out-of-bounds read in PDFium.
- CVE-2014-7948: Caching error in AppCache.
  * debian/patch/search-credit: Don't force client in GOOG suggestions search.
(LP: #1398900)
  * debian/patches/dri3-within-sandbox: Backport V41 sandbox, fixing DRI3.
(LP: #1378627)
  * debian/patches/macro-templates-not-match: Remove. No longer necessary.
  * debian/patches/arm-neon.patch: Kill armv7=neon assumption. Fix typos.
  * debian/rules: chrpath for all packages.  (LP: #141)
 -- Chad MILLER chad.mil...@canonical.com   Fri, 30 Jan 2015 15:48:09 -0500

** Changed in: chromium-browser (Ubuntu)
   Status: Fix Committed = Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7923

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7924

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7925

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7926

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7927

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7928

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7929

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7930

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7931

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7932

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7933

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7934

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7935

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7936

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7937

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7938

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7939

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7940

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7941

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7942

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7943

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7944

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7945

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7946

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7947

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7948

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

Title:
  error while loading shared libraries: libui_base.so

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  There is a missing library needed by chromium-chromedriver in utopic

  ii  chromium-browser 
39.0.2171.65-0ubuntu0.14.10.1.1106  amd64Chromium web browser, 
open-source version of Chrome
  ii  chromium-chromedriver
39.0.2171.65-0ubuntu0.14.10.1.1106  amd64WebDriver driver for 
the Chromium Browser

  chrpath -l /usr/lib/chromium-browser/chromedriver
  /usr/lib/chromium-browser/chromedriver: RPATH=$ORIGIN/lib/

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1398900] Re: No search suggestions in chromium omnibox

2015-02-06 Thread Launchpad Bug Tracker
This bug was fixed in the package chromium-browser -
40.0.2214.94-0ubuntu1.1120

---
chromium-browser (40.0.2214.94-0ubuntu1.1120) vivid; urgency=medium

  * Upstream release 40.0.2214.94.
  * Upstream release 40.0.2214.93.
  * Upstream release 40.0.2214.91. (LP: #1414753)
- CVE-2014-7923: Memory corruption in ICU.
- CVE-2014-7924: Use-after-free in IndexedDB.
- CVE-2014-7925: Use-after-free in WebAudio.
- CVE-2014-7926: Memory corruption in ICU.
- CVE-2014-7927: Memory corruption in V8.
- CVE-2014-7928: Memory corruption in V8.
- CVE-2014-7930: Use-after-free in DOM.
- CVE-2014-7931: Memory corruption in V8.
- CVE-2014-7929: Use-after-free in DOM.
- CVE-2014-7932: Use-after-free in DOM.
- CVE-2014-7933: Use-after-free in FFmpeg.
- CVE-2014-7934: Use-after-free in DOM.
- CVE-2014-7935: Use-after-free in Speech.
- CVE-2014-7936: Use-after-free in Views.
- CVE-2014-7937: Use-after-free in FFmpeg.
- CVE-2014-7938: Memory corruption in Fonts.
- CVE-2014-7939: Same-origin-bypass in V8.
- CVE-2014-7940: Uninitialized-value in ICU.
- CVE-2014-7941: Out-of-bounds read in UI.
- CVE-2014-7942: Uninitialized-value in Fonts.
- CVE-2014-7943: Out-of-bounds read in Skia.
- CVE-2014-7944: Out-of-bounds read in PDFium.
- CVE-2014-7945: Out-of-bounds read in PDFium.
- CVE-2014-7946: Out-of-bounds read in Fonts.
- CVE-2014-7947: Out-of-bounds read in PDFium.
- CVE-2014-7948: Caching error in AppCache.
  * debian/patch/search-credit: Don't force client in GOOG suggestions search.
(LP: #1398900)
  * debian/patches/dri3-within-sandbox: Backport V41 sandbox, fixing DRI3.
(LP: #1378627)
  * debian/patches/macro-templates-not-match: Remove. No longer necessary.
  * debian/patches/arm-neon.patch: Kill armv7=neon assumption. Fix typos.
  * debian/rules: chrpath for all packages.  (LP: #141)
 -- Chad MILLER chad.mil...@canonical.com   Fri, 30 Jan 2015 15:48:09 -0500

** Changed in: chromium-browser (Ubuntu)
   Status: Fix Committed = Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7923

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7924

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7925

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7926

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7927

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7928

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7929

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7930

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7931

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7932

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7933

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7934

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7935

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7936

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7937

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7938

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7939

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7940

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7941

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7942

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7943

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7944

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7945

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7946

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7947

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-7948

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

Title:
  No search suggestions in chromium omnibox

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Version 39.0.2171.65 Ubuntu 14.04 (64-bit)
  Ubuntu 14.04.1 LTS

  No search suggestions are shown when I type in omnibox. Default search engine 
set to Google.
  Maybe the same reason as in previous similar bug (autocomplete request)
  https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1244774
  https://code.google.com/p/chromium/issues/detail?id=304560

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

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

[Desktop-packages] [Bug 1418679] Re: Multiline text controls occasionally get corrupted on refresh

2015-02-06 Thread Michael von Glasow
Attached is another screenshot from Eclipse. This one happened after
scrolling. The first four lines of the command_new function body are
missing completely (the second line of that block is empty anyway,
however), the fifth line is clipped. Also note the discoloration of the
first two missing lines and the one preceding it.

** Attachment added: Missing lines in Eclipse
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1418679/+attachment/4313884/+files/Screenshot_Eclipse.png

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

Title:
  Multiline text controls occasionally get corrupted on refresh

Status in xorg package in Ubuntu:
  New

Bug description:
  I have recently updated from Ubuntu 12.04 (32-bit) to Ubuntu MATE
  14.10 (64-bit).

  After upgrading, I find that some text controls have a refresh issue
  that seems to get triggered either by scrolling or adding a new line
  when the text already contains more lines than can be displayed at a
  time. This happens infrequently and is not always reproducible.

  The issue is that some lines in the text control show as blank lines.
  I have noticed this happen in the following applications:

  * Eclipse 3.8
  * Thunderbird (various versions)
  * Firefox (various versions). In Firefox text is occasionally clipped, but 
not necessarily at line boundaries.

  Other applications seem fine, it might be related to the widget
  toolkit (OTOH, the apps above use two different widget toolkits –
  Eclipse uses SWT while the other two use XUL).

  I am also seeing a different kind of output corruption in Terminal,
  which may or may not be related. Similar to the above, it happens when
  I press ENTER while at the bottom of the terminal window.

  I have seen the same issue on a second computer running a custom Linux
  build based on Kubuntu 12.04 (32-bit) with some components (including
  the kernel) being later versions than what is included in 12.04.

  A third computer, also running Ubuntu MATE 14.10, does not seem to
  have this issue.

  This seems to be a bug introduced into Ubuntu after 12.04, though I
  can't tell which component is at fault. It is possibly related to
  https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1239607.

  I will post more details (including screenshots) soon, so bear with
  me.

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


  1   2   >