date:20131013

There is an audio path from 0x1e -> 0x1d -> 0x2b -> (0x15 , 0x16 or
0x17)

the amp out at node 0x1e can be use as playback volume for the speaker
or mic jack if other amp-in except node 0s2b  in node 0x1d are muted

Node 0x1d [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
  Amp-In caps: ofs=0x17, nsteps=0x1f, stepsize=0x05, mute=1
  Amp-In vals:  [0x97 0x97] [0x97 0x97] [0x97 0x97] [0x97 0x97] [0x97 0x97]
  Connection: 5
 0x28 0x29 0x2a 0x2b 0x12
Node 0x1e [Audio Selector] wcaps 0x30010d: Stereo Amp-Out
  Amp-Out caps: ofs=0x1f, nsteps=0x1f, stepsize=0x05, mute=1
  Amp-Out vals:  [0x9f 0x9f]
  Connection: 1
 0x1d

Node 0x2b [Audio Selector] wcaps 0x300101: Stereo
  Connection: 3
 0x15* 0x16 0x17

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

Title:
  Dell 1535 no sound from speakers, headphone out is ok

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  System: Dell studi 1535 with 12.04.03 i686 
  There is 3 jacks at left panel: mic, headphone, headphone.  Also system has 
buildin speackers. They doesnt work. 
  1) I've tried with alsamixer and pavucontrol - no luck.
  2) Tried with different modprobe options like options  snd-hda-intel 
model=dell-m6 / auto . No luck

  Any idea how to fix it one and forewer ?


  System information
  #uname -a
  Linux necron 3.8.0-31-generic #46~precise1-Ubuntu SMP Wed Sep 11 17:49:16 UTC 
2013 i686 i686 i386 GNU/Linux Description:  Ubuntu 12.04.3 LTS

  # lspci | grep Audio
  00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio 
Controller (rev 03)
  01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] RV620 HDMI Audio 
[Radeon HD 3400 Series]

  alsactl version 1.0.25

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1238144/+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 1239536] [NEW] GLib-GIO-CRITICAL g_dbus_connection_call_internal: assertion 'object_path != NULL && g_variant_is_object_path (object_path)' failed

2013-10-13 Thread ZhangJing

Public bug reported:

I just upgraded Ubuntu AMD64 version to Saucy from Raring, and installed
gnome-shell from default source. Gnome-shell not works well so I check
syslog and find this message.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: gnome-session 3.9.90-0ubuntu3
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
Architecture: amd64
Date: Mon Oct 14 14:23:27 2013
InstallationDate: Installed on 2013-01-21 (265 days ago)
InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: gnome-session
UpgradeStatus: Upgraded to saucy on 2013-10-12 (1 days ago)

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


** Tags: amd64 apport-bug saucy

** Description changed:

- I just upgraded Ubuntu to Saucy from , and installed gnome-shell from
- default source. Gnome-shell not works well so I check syslog and find
- this message.
+ I just upgraded Ubuntu AMD64 version to Saucy from Raring, and installed
+ gnome-shell from default source. Gnome-shell not works well so I check
+ syslog and find this message.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-session 3.9.90-0ubuntu3
  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
  Architecture: amd64
  Date: Mon Oct 14 14:23:27 2013
  InstallationDate: Installed on 2013-01-21 (265 days ago)
  InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to saucy on 2013-10-12 (1 days ago)

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

Title:
  GLib-GIO-CRITICAL g_dbus_connection_call_internal: assertion
  'object_path != NULL && g_variant_is_object_path (object_path)' failed

Status in “gnome-session” package in Ubuntu:
  New

Bug description:
  I just upgraded Ubuntu AMD64 version to Saucy from Raring, and
  installed gnome-shell from default source. Gnome-shell not works well
  so I check syslog and find this message.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-session 3.9.90-0ubuntu3
  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
  Architecture: amd64
  Date: Mon Oct 14 14:23:27 2013
  InstallationDate: Installed on 2013-01-21 (265 days ago)
  InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to saucy on 2013-10-12 (1 days ago)

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

** Branch linked: lp:~fourdollars/ubuntu/quantal/upower/fix-
bluetooth-1153488-1237329

-- 
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:
  Confirmed
Status in “gnome-power-manager” source package in Quantal:
  Invalid
Status in “upower” source package in Quantal:
  Confirmed
Status in “gnome-power-manager” source package in Raring:
  Invalid
Status in “upower” source package in Raring:
  Confirmed
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
   linux-backports-modules-3.5.0-23-generic  N/A
   linux-firmware1.79.1
  SourcePackage: linux
  StagingDrivers: rts_pstor
  UpgradeStatus: No upgrad

[Desktop-packages] [Bug 803627] Re: empathy crashed with signal 5 in gtk_box_size_allocate()

2013-10-13 Thread Timothy Arceri

Is this still an issue with a more recent version?

** Package changed: empathy (Ubuntu) => gtk+3.0 (Ubuntu)

** Project changed: empathy => gtk

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

Title:
  empathy crashed with signal 5 in gtk_box_size_allocate()

Status in GTK+ GUI Toolkit:
  New
Status in “gtk+3.0” package in Ubuntu:
  Triaged

Bug description:
  Open empathy and click in "link contacts..." (Facebook) and crash. My
  acount is Gabble, butterfly and IRC.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: empathy 3.1.2.1-1ubuntu1
  Uname: Linux 3.0.0-0300rc5-generic x86_64
  Architecture: amd64
  Date: Wed Jun 29 16:02:32 2011
  ExecutablePath: /usr/bin/empathy
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110531.1)
  ProcCmdline: empathy
  ProcEnviron:
   LANGUAGE=es_ES:en
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
   LC_MESSAGES=es_ES.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: empathy
  StacktraceTop:
   gtk_box_size_allocate (widget=, allocation=) at /build/buildd/gtk+3.0-3.1.6/./gtk/gtkbox.c:480
   g_closure_invoke (closure=0x27815b0, return_value=0x0, n_param_values=2, 
param_values=0x7f19e4066760, invocation_hint=) at 
/build/buildd/glib2.0-2.29.8/./gobject/gclosure.c:771
   signal_emit_unlocked_R (node=, detail=0, 
instance=0x301dcb0, emission_return=0x0, instance_and_params=0x7f19e4066760) at 
/build/buildd/glib2.0-2.29.8/./gobject/gsignal.c:3186
   g_signal_emit_valist (instance=, signal_id=, detail=, var_args=0x7fff9337b688) at 
/build/buildd/glib2.0-2.29.8/./gobject/gsignal.c:2987
   g_signal_emit (instance=, signal_id=, detail=) at 
/build/buildd/glib2.0-2.29.8/./gobject/gsignal.c:3044
  Title: empathy crashed with signal 5 in gtk_box_size_allocate()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/803627/+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 1237329] Re: Apple Wireless Keyboard/Mouse is not listed as its original name. It stripped non-ascii characters (UTF-8 valid).

** Branch linked: lp:~fourdollars/ubuntu/quantal/upower/fix-
bluetooth-1153488-1237329

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

Title:
  Apple Wireless Keyboard/Mouse is not listed as its original name. It
  stripped non-ascii characters (UTF-8 valid).

Status in “upower” package in Ubuntu:
  Fix Released
Status in “upower” source package in Precise:
  Triaged
Status in “upower” source package in Quantal:
  Confirmed
Status in “upower” source package in Raring:
  Confirmed
Status in “upower” source package in Saucy:
  Fix Released

Bug description:
  [Impact]

   * For some Bluetooth devices such as Apple Wireless Keyboard/Mouse,
  you can name them by valid UTF-8 string. However those UTF-8 strings
  are not showed. It is very annoying for the users that they can not
  see those valid UTF-8 strings.

  [Test Case]

   * Pair some Bluetooth devices, such as Apple Wireless Mouse or Apple 
Wireless Keyboard.
   * Open gnome-power-statistics, you have find that the 'Model' field of Apple 
Wireless Mouse shows only ASCII without the correct name.

  [Regression Potential]

   * There is no obvious regression as I know.

  [Other Info]

   * This issue is fixed in Saucy but not in Precise, Quantal and Raring.
   * We still need another patch from 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d0a934b764c67b4bf626f5b7cf725a6e3066afd2
 to make Apple Wireless Keyboard show.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1237329/+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 239930] Re: scanner port detection

2013-10-13 Thread Thomas Hotz

I'm sorry that nobody cared about your bugs for such a long time. Are
you still having problems. Thank for telling us!

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

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

Title:
  scanner port detection

Status in “sane-backends” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: sane-utils

  hello,

  this info posted also on bug 205496 ( diff topic but related to sane,
  xsane; it was reported before I decided to file this)

  I'm running hardy amd64 with last upgrades/updates installed

  uname -r
  2.6.24-18-generic

   uname -a
  Linux ubuntu-HARDY 2.6.24-18-generic #1 SMP Wed May 28 19:28:38 UTC 2008 
x86_64 GNU/Linux

  . the scanner used to work ok with previous version 14, 16. didn't use
  it for a while; now I'm getting

  error failed to open device 'snapscan:libusb:002:010':invalid argument

  and this output

  lsusb

  Bus 002 Device 010: ID 06bd:208f AGFA-Gevaert NV SnapScan e50
  Bus 002 Device 007: ID 0d8d:0105 Promotion & Display Technology, Ltd
  Bus 002 Device 004: ID 0ace:1215 ZyDAS WLA-54L WiFi
  Bus 002 Device 003: ID 050d:0224 Belkin Components F5U224 USB 2.0 4-Port Hub
  Bus 002 Device 001: ID :
  Bus 001 Device 010: ID 050d:0980 Belkin Components
  Bus 001 Device 009: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
  Bus 001 Device 008: ID 0451:1446 Texas Instruments, Inc. TUSB2040/2070 Hub
  Bus 001 Device 001: ID :

  and

  scanimage -L
  device `snapscan:libusb:002:010' is a AGFA SNAPSCAN flatbed scanner

  and, ...  this

  sane-find-scanner

# sane-find-scanner will now attempt to detect your scanner. If the
# result is different from what you expected, first make sure your
# scanner is powered up and properly connected to your computer.

# No SCSI scanners found. If you expected something different, make sure 
that
# you have loaded a kernel SCSI driver for your SCSI adapter.

  found USB scanner (vendor=0x06bd [AGFA ], product=0x208f [SNAPSCAN]) at 
libusb:002:009
  found USB scanner (vendor=0x0ace, product=0x1215) at libusb:002:004
  found USB scanner (vendor=0x067b, product=0x2303) at libusb:001:009

  pls notice the difference --> 009 on last command output

   vs

  before last command 010 and the error message.

  is there any fix to this or why it happens ?.

  any help is appreciated.

  best regards,
  peter b

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/239930/+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 1239351] Re: Hang or crash after installing nvidia-319 (amd64 only)

2013-10-13 Thread Jacob Nielsen

Log file from /var/lib/dkms/nvidia-319/kernel-3.11.0-12-generic-
x86_64/log. I'll try to get info from the failed boot later today.

** Attachment added: "make.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319/+bug/1239351/+attachment/3877256/+files/make.log

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

Title:
  Hang or crash after installing nvidia-319 (amd64 only)

Status in “nvidia-graphics-drivers-319” package in Ubuntu:
  Incomplete

Bug description:
  A fresh install of Saucy/amd64 from either the final beta or today's
  daily build fails to boot after installing the proprietary nvidia
  driver. A parallel install of the same daily build, only x86, is not
  affected.

  My graphics card (Zotac GT430 (GF108 chip)) is apparently not
  supported by nouveau, and not recognized as such, so I must add
  nomodeset in order to boot the live cd and install. In both cases the
  proprietary driver was installed from System Settings / Software &
  Updates / Additional Drivers after the first boot. I then removed
  "nomodeset" from /etc/default/grub, did update-grub -u -k all and
  rebooted.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: nvidia-319 319.32-0ubuntu7
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Sun Oct 13 15:26:42 2013
  InstallationDate: Installed on 2013-10-13 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131013)
  MarkForUpload: True
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-graphics-drivers-319
  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-319/+bug/1239351/+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 1239298] Re: Fails to install Broadcom wireless drivers from Kubuntu live session

2013-10-13 Thread Scott Kitterman

Note: there was a small error in the partial patch from yesterday, it
should just be pkg instead of pkg.name in the mark_install line.

Kubuntu had planned to switch away from jockey for 13.10, but it didn't
get done.  We're already working on it for 14.04.

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

Title:
  Fails to install Broadcom wireless drivers from Kubuntu live session

Status in “jockey” package in Ubuntu:
  New
Status in “jockey” source package in Saucy:
  New

Bug description:
  I think this is the relevant bit from the log:

  Traceback (most recent call last):
File "/usr/bin/jockey-kde", line 286, in on_button_toggle_clicked
  if self.set_handler_enable(h_id, 'toggle', False):
File "/usr/lib/python2.7/dist-packages/jockey/ui.py", line 670, in 
set_handler_enable
  handler_id, enable)
File "/usr/lib/python2.7/dist-packages/jockey/backend.py", line 98, in 
convert_dbus_exceptions
  return fn(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/jockey/backend.py", line 90, in 
dbus_sync_call_signal_wrapper
  raise _h_exception_exc
  dbus.exceptions.DBusException: org.freedesktop.DBus.Python.AttributeError: 
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/dbus/service.py", line 707, in 
_message_cb
  retval = candidate_method(self, *args, **keywords)
File "/usr/lib/python2.7/dist-packages/jockey/backend.py", line 337, in 
_f_result_wrapper
  self._f_result = f()
File "/usr/share/jockey/handlers/broadcom_wl.py", line 53, in enable
  Handler.enable(self)
File "/usr/lib/python2.7/dist-packages/jockey/handlers.py", line 263, in 
enable
  self.repository_sign_fp)
File "/usr/lib/python2.7/dist-packages/jockey/backend.py", line 635, in 
install_package
  repository, fingerprint)
File "/usr/lib/python2.7/dist-packages/jockey/oslib.py", line 258, in 
install_package
  class MyFetchProgress(apt.FetchProgress):
  AttributeError: 'module' object has no attribute 'FetchProgress'

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: jockey-kde 0.9.7-0ubuntu14
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  CasperVersion: 1.336ubuntu1
  Date: Sun Oct 13 09:05:22 2013
  LiveMediaBuild: Kubuntu 13.10 "Saucy Salamander" - Beta i386 (20131013)
  MachineType: Dell Inc. Inspiron 1011
  MarkForUpload: True
  PackageArchitecture: all
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/username.seed boot=casper maybe-ubiquity 
initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
  SourcePackage: jockey
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/20/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: CN0Y53
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A00
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd03/20/2009:svnDellInc.:pnInspiron1011:pvrA00:rvnDellInc.:rnCN0Y53:rvrA00:cvnDellInc.:ct8:cvrA00:
  dmi.product.name: Inspiron 1011
  dmi.product.version: A00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1239298/+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 1239298] Re: Fails to install Broadcom wireless drivers from Kubuntu live session

2013-10-13 Thread Scott Kitterman

I didn't see the actual traceback in the log, so here it is.

** Attachment added: "New traceback"
   
https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1239298/+attachment/3877241/+files/traceback

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

Title:
  Fails to install Broadcom wireless drivers from Kubuntu live session

Status in “jockey” package in Ubuntu:
  New
Status in “jockey” source package in Saucy:
  New

Bug description:
  I think this is the relevant bit from the log:

  Traceback (most recent call last):
File "/usr/bin/jockey-kde", line 286, in on_button_toggle_clicked
  if self.set_handler_enable(h_id, 'toggle', False):
File "/usr/lib/python2.7/dist-packages/jockey/ui.py", line 670, in 
set_handler_enable
  handler_id, enable)
File "/usr/lib/python2.7/dist-packages/jockey/backend.py", line 98, in 
convert_dbus_exceptions
  return fn(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/jockey/backend.py", line 90, in 
dbus_sync_call_signal_wrapper
  raise _h_exception_exc
  dbus.exceptions.DBusException: org.freedesktop.DBus.Python.AttributeError: 
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/dbus/service.py", line 707, in 
_message_cb
  retval = candidate_method(self, *args, **keywords)
File "/usr/lib/python2.7/dist-packages/jockey/backend.py", line 337, in 
_f_result_wrapper
  self._f_result = f()
File "/usr/share/jockey/handlers/broadcom_wl.py", line 53, in enable
  Handler.enable(self)
File "/usr/lib/python2.7/dist-packages/jockey/handlers.py", line 263, in 
enable
  self.repository_sign_fp)
File "/usr/lib/python2.7/dist-packages/jockey/backend.py", line 635, in 
install_package
  repository, fingerprint)
File "/usr/lib/python2.7/dist-packages/jockey/oslib.py", line 258, in 
install_package
  class MyFetchProgress(apt.FetchProgress):
  AttributeError: 'module' object has no attribute 'FetchProgress'

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: jockey-kde 0.9.7-0ubuntu14
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  CasperVersion: 1.336ubuntu1
  Date: Sun Oct 13 09:05:22 2013
  LiveMediaBuild: Kubuntu 13.10 "Saucy Salamander" - Beta i386 (20131013)
  MachineType: Dell Inc. Inspiron 1011
  MarkForUpload: True
  PackageArchitecture: all
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/username.seed boot=casper maybe-ubiquity 
initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
  SourcePackage: jockey
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/20/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: CN0Y53
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A00
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd03/20/2009:svnDellInc.:pnInspiron1011:pvrA00:rvnDellInc.:rnCN0Y53:rvrA00:cvnDellInc.:ct8:cvrA00:
  dmi.product.name: Inspiron 1011
  dmi.product.version: A00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1239298/+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 1239298] Re: Fails to install Broadcom wireless drivers from Kubuntu live session

2013-10-13 Thread Scott Kitterman

** Attachment added: "New jockey log"
   
https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1239298/+attachment/3877240/+files/jockey.log

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

Title:
  Fails to install Broadcom wireless drivers from Kubuntu live session

Status in “jockey” package in Ubuntu:
  New
Status in “jockey” source package in Saucy:
  New

Bug description:
  I think this is the relevant bit from the log:

  Traceback (most recent call last):
File "/usr/bin/jockey-kde", line 286, in on_button_toggle_clicked
  if self.set_handler_enable(h_id, 'toggle', False):
File "/usr/lib/python2.7/dist-packages/jockey/ui.py", line 670, in 
set_handler_enable
  handler_id, enable)
File "/usr/lib/python2.7/dist-packages/jockey/backend.py", line 98, in 
convert_dbus_exceptions
  return fn(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/jockey/backend.py", line 90, in 
dbus_sync_call_signal_wrapper
  raise _h_exception_exc
  dbus.exceptions.DBusException: org.freedesktop.DBus.Python.AttributeError: 
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/dbus/service.py", line 707, in 
_message_cb
  retval = candidate_method(self, *args, **keywords)
File "/usr/lib/python2.7/dist-packages/jockey/backend.py", line 337, in 
_f_result_wrapper
  self._f_result = f()
File "/usr/share/jockey/handlers/broadcom_wl.py", line 53, in enable
  Handler.enable(self)
File "/usr/lib/python2.7/dist-packages/jockey/handlers.py", line 263, in 
enable
  self.repository_sign_fp)
File "/usr/lib/python2.7/dist-packages/jockey/backend.py", line 635, in 
install_package
  repository, fingerprint)
File "/usr/lib/python2.7/dist-packages/jockey/oslib.py", line 258, in 
install_package
  class MyFetchProgress(apt.FetchProgress):
  AttributeError: 'module' object has no attribute 'FetchProgress'

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: jockey-kde 0.9.7-0ubuntu14
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  CasperVersion: 1.336ubuntu1
  Date: Sun Oct 13 09:05:22 2013
  LiveMediaBuild: Kubuntu 13.10 "Saucy Salamander" - Beta i386 (20131013)
  MachineType: Dell Inc. Inspiron 1011
  MarkForUpload: True
  PackageArchitecture: all
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/username.seed boot=casper maybe-ubiquity 
initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
  SourcePackage: jockey
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/20/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: CN0Y53
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A00
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd03/20/2009:svnDellInc.:pnInspiron1011:pvrA00:rvnDellInc.:rnCN0Y53:rvrA00:cvnDellInc.:ct8:cvrA00:
  dmi.product.name: Inspiron 1011
  dmi.product.version: A00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1239298/+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 1239520] [NEW] AR9462 Atheros packet loss with android hotspot

2013-10-13 Thread Sonny To

Public bug reported:

I just got a dell xps 13 developer edition. unfortunately the wifi does not 
work well so I upgraded to ubuntu 13.04 but no luck.
Other people are having similar problems: 
http://askubuntu.com/questions/301442/atheros-ar9462-wifi-very-unstable-package-loss

 Read that the problem is fixed in the 3.11 kernel but it is not.  I installed 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.5-saucy and still doesnt 
work.  Then I installed the 3.12 kernel 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc5-saucy/
still has high packet loss.   However if I turn off security on my android 
hotspot (no WPA) I get no packet loss.

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

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

Title:
  AR9462  Atheros packet loss with android hotspot

Status in “gnome-nettool” package in Ubuntu:
  New

Bug description:
  I just got a dell xps 13 developer edition. unfortunately the wifi does not 
work well so I upgraded to ubuntu 13.04 but no luck.
  Other people are having similar problems: 
http://askubuntu.com/questions/301442/atheros-ar9462-wifi-very-unstable-package-loss

   Read that the problem is fixed in the 3.11 kernel but it is not.  I 
installed http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.5-saucy and still 
doesnt work.  Then I installed the 3.12 kernel 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc5-saucy/
  still has high packet loss.   However if I turn off security on my android 
hotspot (no WPA) I get no packet loss.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-nettool/+bug/1239520/+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 1239519] [NEW] evolution: Opening appointments can be too wide for screen - 1024x768

Public bug reported:

evolution: Opening appointments can be too wide for screen - 1024x768.

This only affects opening of existing appointments and not the creation
of new ones.

See attached screenshot.

Appointments dialog on a screen of 1024x768 is too wide and is not
resizable for width.

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
Architecture: amd64
Date: Mon Oct 14 06:07:23 2013
InstallationDate: Installed on 2013-09-12 (32 days ago)
InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
MarkForUpload: True
SourcePackage: evolution
UpgradeStatus: Upgraded to saucy on 2013-09-12 (32 days ago)

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


** Tags: amd64 apport-bug gnome3 saucy

** Attachment added: "Appointment opened that is too wide for screen @ width of 
1024"
   
https://bugs.launchpad.net/bugs/1239519/+attachment/3877236/+files/Screenshot%20from%202013-10-14%2006%3A02%3A41.png

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

Title:
  evolution: Opening appointments can be too wide for screen - 1024x768

Status in “evolution” package in Ubuntu:
  New

Bug description:
  evolution: Opening appointments can be too wide for screen - 1024x768.

  This only affects opening of existing appointments and not the
  creation of new ones.

  See attached screenshot.

  Appointments dialog on a screen of 1024x768 is too wide and is not
  resizable for width.

  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
  Architecture: amd64
  Date: Mon Oct 14 06:07:23 2013
  InstallationDate: Installed on 2013-09-12 (32 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  SourcePackage: evolution
  UpgradeStatus: Upgraded to saucy on 2013-09-12 (32 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1239519/+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 1239019] Re: Jockey is failing to list any nvidia drivers

Re: #3

According to the logs supplied with your bug report you have 2 graphics
devices. See the LSPCI log you supplied.

Device 1:

00:02.0 Display controller [0380]: Intel Corporation 2nd Generation Core
Processor Family Integrated Graphics Controller [8086:0112] (rev 09)

Device 2:

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF114
[GeForce GTX 560] [10de:1201] (rev a1) (prog-if 00 [VGA controller])

Please see: https://wiki.ubuntu.com/X/Config/HybridGraphics

You may also look at your BIOS and setting the PCI-e device as primary
or disable the onboard Intel device.


** Changed in: jockey (Ubuntu)
   Status: New => Invalid

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

Title:
  Jockey is failing to list any nvidia drivers

Status in “jockey” package in Ubuntu:
  Invalid

Bug description:
  Suddenly, both jockey-gtk and jockey-text are failing to recommend me
  any nvidia drivers!

  This makes maintaining drivers in a Ubuntu-friendly way difficult.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: jockey-common 0.9.7-0ubuntu7.11
  ProcVersionSignature: Ubuntu 3.2.0-54.82-generic 3.2.50
  Uname: Linux 3.2.0-54-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.5
  Architecture: amd64
  CheckboxSubmission: f14e403bdb8f84f871603c9cde62a6ec
  CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2
  Date: Sat Oct 12 10:43:55 2013
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: Gigabyte Technology Co., Ltd. Z68AP-D3
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-54-generic 
root=UUID=20aa0109-67bb-46a0-95c6-626f0f0487eb ro quiet splash
  SourcePackage: jockey
  UpgradeStatus: Upgraded to precise on 2012-04-26 (533 days ago)
  dmi.bios.date: 10/12/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FB
  dmi.board.name: Z68AP-D3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/12/2011:svnGigabyteTechnologyCo.,Ltd.:pnZ68AP-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68AP-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: Z68AP-D3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1239019/+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 1209324] Re: nm-applet does not appear in live cd mode

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

** Changed in: network-manager-applet (Ubuntu)
   Status: New => Confirmed

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

Title:
  nm-applet does not appear in live cd mode

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

Bug description:
  When starting the system in live mode, the nm-applet does not appear
  in the panel.

  Even though the network is working, e.g. I can access a WLAN when
  starting the installation assistant.

  When opening a terminal and starting "nm-applet", three icons appear in the 
panel.
  The terminal gives message: ** Message: applet now removed from the 
notification area

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager-gnome 0.9.8.0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  Uname: Linux 3.10.0-6-generic i686
  ApportVersion: 2.12-0ubuntu2
  Architecture: i386
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  CasperVersion: 1.336
  Date: Wed Aug  7 17:03:33 2013
  ExecutablePath: /usr/bin/nm-applet
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.106  
metric 9
  LiveMediaBuild: Lubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130802)
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   surveillance cam #3   f09d4b9b-990d-49b7-b93c-18fa794d1188   
802-11-wireless   1375894972   Wed 07 Aug 2013 05:02:52 PM UTCyes   
no /org/freedesktop/NetworkManager/Settings/1
   Wired connection 1a86a4650-3e02-4613-99f7-8d9136f0a518   
802-3-ethernet1375900672   Wed 07 Aug 2013 06:37:52 PM UTCyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.0connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1209324/+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 642792] Re: ALT+PrtSc not recognised: breaks built-in screenshot function

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

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

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

Title:
  ALT+PrtSc not recognised: breaks built-in screenshot function

Status in Release Notes for Ubuntu:
  Invalid
Status in “compiz” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Expired
Status in “metacity” package in Ubuntu:
  Invalid
Status in “compiz” source package in Maverick:
  Invalid
Status in “linux” source package in Maverick:
  Invalid
Status in “metacity” source package in Maverick:
  Invalid

Bug description:
  Binary package hint: xkeyboard-config

  On an EN-GB keyboard (and maybe others) ALT+PrtSc is the default
  keyboard shortcut for "Take a screenshot of a window" as configured in
  System -> Preferences -> Keyboard Shortcuts. However the system
  doesn't seem to respond to that keyboard combination at all. Pressing
  ALT+PrtSc on a default Maverick install does nothing. Indeed
  attempting to _set_ that keyboard shortcut in the Keyboard Shortcuts
  dialog results in it not being registered.

  Workaround:
  sudo sysctl -w kernel.sysrq=0

  Steps to reproduce:-

  1) Try to screenshot the entire desktop with PrtSc - this works
  2) Try to take a screenshot of one active window with ALT+PrtSc - nothing 
happens.

  Additionally

  1) Navigate to System -> Preferences -> Keyboard Shortcuts
  2) Scroll down to Desktop -> Take a screenshot of a window, and then click 
that line in order to set a keyboard shortcut for the action
  3) Press ALT+PrtSc - nothing happens
  4) Press a different keyboard combination such as CTRL+PrtSc or 
Super/Windows+PrtSc - this works

  Additionally

  1) Open a terminal
  2) Run 'xev' and then press ALT+PrtSc. Observe data in the xev terminal 
window when ALT is pressed, but nothing for ALT+PrtSc

  Seems a fairly critical regression bug given we document this keyboard
  shortcut in the help, and it's very commonly used by documenters and
  people getting support. It works fine in previous releases.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: xkb-data 1.8-1ubuntu8
  ProcVersionSignature: Ubuntu 2.6.35-22.32-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  256.53  Fri Aug 27 20:27:48 
PDT 2010
   GCC version:  gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu4)
  Architecture: amd64
  CurrentDmesg:
   [   22.090007] eth1: no IPv6 routers present
   [  691.401253] show_signal_msg: 9 callbacks suppressed
   [  691.401258] gnome-help[2307]: segfault at 35a3f08 ip 7f9f58d3043e sp 
7d377130 error 4 in libxml2.so.2.7.7[7f9f58cae000+147000]
  Date: Sun Sep 19 14:19:15 2010
  Dependencies:

  DkmsStatus:
   nvidia-current, 256.53, 2.6.35-22-generic, x86_64: installed
   nvidia-current, 256.53, 2.6.35-21-generic, x86_64: installed
   nvidia-current, 256.53, 2.6.35-20-generic, x86_64: installed
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: System manufacturer System Product Name
  PackageArchitecture: all
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic 
root=UUID=fb22b4e1-1576-4bf8-8272-15300bc7de38 ro quiet splash
  ProcEnviron:
   LANG=en_GB.utf8
   SHELL=/bin/bash
  SourcePackage: xkeyboard-config
  dmi.bios.date: 04/24/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS P5N32-E SLI ACPI BIOS Revision 1801
  dmi.board.name: P5N32-E SLI
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N32-ESLIACPIBIOSRevision1801:bd04/24/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N32-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  glxinfo: Error: [Errno 2] No such file or directory
  system:
   distro: Ubuntu
   codename:   maverick
   architecture:   x86_64
   kernel: 2.6.35-22-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/642792/+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 1227920] Re: after suspend/resume, the Unity HUD is always open when I unlock the screen

2013-10-13 Thread Walter Garcia-Fontes

I tried it also using Xmir and in my system the HUD is not shown when
waking after suspend by closing the lid.

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

Title:
  after suspend/resume, the Unity HUD is always open when I unlock the
  screen

Status in Unity:
  Invalid
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  Traveling at a conference, so I'm doing a lot of suspending and
  resuming of my laptop.  Every time I open my laptop back up after
  resume and unlock the desktop, the Unity dash is open.  This does not
  happen if I lock my screen using the "lock screen" hotkey, and does
  not happen if my screen is locked by a lid close event; only when the
  system suspends and resumes.  But it is 100% reproducible.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.0+13.10.20130903.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
  Uname: Linux 3.11.0-7-generic x86_64
  ApportVersion: 2.12.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,imgpng,snap,place,grid,resize,regex,mousepoll,gnomecompat,unitymtgrabhandles,vpswitch,move,animation,expo,session,wall,ezoom,staticswitcher,workarounds,fade,scale,unityshell]
  Date: Thu Sep 19 17:51:29 2013
  InstallationDate: Installed on 2010-09-24 (1091 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to saucy on 2013-05-06 (136 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1227920/+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 1239019] Re: Jockey is failing to list any nvidia drivers

2013-10-13 Thread Vadim Peretokin

** Changed in: jockey (Ubuntu)
   Status: Invalid => New

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

Title:
  Jockey is failing to list any nvidia drivers

Status in “jockey” package in Ubuntu:
  New

Bug description:
  Suddenly, both jockey-gtk and jockey-text are failing to recommend me
  any nvidia drivers!

  This makes maintaining drivers in a Ubuntu-friendly way difficult.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: jockey-common 0.9.7-0ubuntu7.11
  ProcVersionSignature: Ubuntu 3.2.0-54.82-generic 3.2.50
  Uname: Linux 3.2.0-54-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.5
  Architecture: amd64
  CheckboxSubmission: f14e403bdb8f84f871603c9cde62a6ec
  CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2
  Date: Sat Oct 12 10:43:55 2013
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: Gigabyte Technology Co., Ltd. Z68AP-D3
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-54-generic 
root=UUID=20aa0109-67bb-46a0-95c6-626f0f0487eb ro quiet splash
  SourcePackage: jockey
  UpgradeStatus: Upgraded to precise on 2012-04-26 (533 days ago)
  dmi.bios.date: 10/12/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FB
  dmi.board.name: Z68AP-D3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/12/2011:svnGigabyteTechnologyCo.,Ltd.:pnZ68AP-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68AP-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: Z68AP-D3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1239019/+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 774475] Re: Lexmark multifunction printer does not work as scanner after upgrade to Natty

2013-10-13 Thread sdaau

Just had this with a custom Ubuntu 12.04 - I got the "unknown sensor
1235" as per #11.

So I downloaded the sources for "quantal/sane-backends" as per #12,
built them on 11.04 (using the -d override switch of `dpkg-
buildpackage`); copied the resulting *.debs to 12.04 machine.

After installing both libsane-common_1.0.23-0ubuntu1_i386.deb and
libsane_1.0.23-0ubuntu1_i386.deb on the 12.04 machine, finally I could
get  "is a Lexmark X1100/rev. B2 flatbed scanner" as in #15, but only
with `sudo` - and after that, I could finally call `sudo simple-scan`,
and it works properly with the scanner.

Thanks to all for the useful info in this thread, 
Cheers!

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

Title:
  Lexmark multifunction printer does not work as scanner after upgrade
  to Natty

Status in “sane-backends” package in Ubuntu:
  Confirmed
Status in “xsane” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: xsane

  Dear friends of the forum, after upgrading my ubuntu station to Natty,
  scanner of my multifunctions Lexmark X1110 stopped working. I mean
  that the device still operates correctly as printer, but the scanner
  is not found. Before upgrading, under Maverick, all functions of X1110
  worked correctly

  Here is the result of scanimage -L command
  [CODE]
  No scanners were identified. If you were expecting something different,
  check that the scanner is plugged in, turned on and detected by the
  sane-find-scanner tool (if appropriate). Please read the documentation
  which came with this software (README, FAQ, manpages).
  [/CODE]But if I type sudo lsusb, here is the reply of the terminal
  [CODE]
  Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 006 Device 004: ID 046d:08af Logitech, Inc. QuickCam Easy/Cool
  Bus 006 Device 002: ID 058f:9254 Alcor Micro Corp. Hub
  Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 005 Device 010: ID 043d:007b Lexmark International, Inc. InkJet Color 
Printer
  Bus 005 Device 009: ID 043d:007c Lexmark International, Inc. Lexmark 
X1110/X1130/X1140/X1150/X1170/X1180/X1185
  Bus 005 Device 008: ID 043d:007a Lexmark International, Inc. Generic Hub
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [/CODE]It means that the device is found: that's why the printer works 
correctly, after installing the right drivers. Thus, I run on terminal sudo 
sane-find-scanner -p. Here is the result
  [CODE]
# sane-find-scanner will now attempt to detect your scanner. If the
# result is different from what you expected, first make sure your
# scanner is powered up and properly connected to your computer.

# No SCSI scanners found. If you expected something different, make sure 
that
# you have loaded a kernel SCSI driver for your SCSI adapter.

  found USB scanner (vendor=0x046d, product=0x08af) at libusb:006:004
  found USB scanner (vendor=0x043d, product=0x007c, chip=rts8858c) at 
libusb:005:009
# Your USB scanner was (probably) detected. It may or may not be supported 
by
# SANE. Try scanimage -L and read the backend's manpage.

# No Mustek parallel port scanners found. If you expected something
# different, make sure the scanner is correctly connected to your computer
# and you have apropriate access rights.

# Most Scanners connected to the parallel port or other proprietary ports
# can't be detected by this program.
  [/CODE]Please, note that sane-utils and xsane are installed, saned user is 
present and enabled within /etc/default/saned, and the demon is started by the 
command
  [CODE]
  sane-portstreamtcpnowaitsaned:saned/usr/sbin/saned saned
  [/CODE]included within the file /etc/inetd.conf.

  After all these attempts, I completely uninstalled xsane and sane-
  utils, trying to make a scan by using simple-scan package,
  unsuccessfully. I installed again xsane and sane-utils, applying the
  configuration they had under maverick, but still unsuccessfully.

  I verified that the driver lexmark in /etc/sane.d/dll.conf was
  uncommented. Any idea on how to solve this issue, please?

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: xsane 0.998-1ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  Architecture: amd64
  Date: Sun May  1 00:00:49 2011
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  ProcEnviron:
   LANGUAGE=it_IT:en
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: xsane
  UpgradeStatus: Upgraded to natty on 2011-04-28 (2 days ago)

To m

[Desktop-packages] [Bug 1180513] Re: lid close actions are ignored laptop always suspends

2013-10-13 Thread Hari Kotcherlakota

I can confirm that I see the same bug on Toshiba Portege R835-P94.

uname -a
3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:12:00 UTC 2013 i686 i686 i686 
GNU/Linux

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

Title:
  lid close actions are ignored laptop always suspends

Status in “gnome-settings-daemon” package in Ubuntu:
  Fix Released

Bug description:
  I tried setting Power -> 'When lid is closed' to 'do nothing', closed
  lid and laptop suspended.

  I also tried using dconf-editor to change org.gnome.settings-
  daemon.plugins.power.lid-close-{ac,battery}-action to both "nothing"
  and "blank" both suspended.

  Both tests were done on AC power.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.9.0-2-generic 3.9.0-2.6
  ProcVersionSignature: Ubuntu 3.9.0-2.6-generic 3.9.2
  Uname: Linux 3.9.0-2-generic i686
  ApportVersion: 2.10.1-0ubuntu1
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Wed May 15 14:57:59 2013
  HibernationDevice: RESUME=UUID=1183f3a4-085e-42ce-9528-8dc899ce034f
  InstallationDate: Installed on 2013-05-15 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130514)
  MachineType: ASUSTeK Computer INC. 900HA
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-2-generic 
root=UUID=1bfb549e-ed93-4d40-b138-0ede0bbebc16 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.9.0-2-generic N/A
   linux-backports-modules-3.9.0-2-generic  N/A
   linux-firmware   1.108
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/23/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0203
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 900HA
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0203:bd09/23/2008:svnASUSTeKComputerINC.:pn900HA:pvrx.x:rvnASUSTeKComputerINC.:rn900HA:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
  dmi.product.name: 900HA
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1180513/+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 1238144] Re: Dell 1535 no sound from speakers, headphone out is ok

In theory, audio 0x17 can be used by the mic for center/lfe for 5.1
support



Node 0x0e [Pin Complex] wcaps 0x400183: Stereo Amp-In
  Control: name="Mic Jack Mode", index=0, device=0
ControlAmp: chs=0, dir=In, idx=0, ofs=0
  Control: name="Mic Capture Volume", index=0, device=0
ControlAmp: chs=3, dir=In, idx=0, ofs=0
  Control: name="Mic Jack", index=0, device=0
  Amp-In caps: N/A
  Amp-In vals:  [0x00 0x00]
  Pincap 0x1737: IN OUT Detect Trigger ImpSense
Vref caps: HIZ 50 GRD 80
  Pin Default 0x03a11020: [Jack] Mic at Ext Left
Conn = 1/8, Color = Black
DefAssociation = 0x2, Sequence = 0x0
  Pin-ctls: 0x24: IN VREF_80
  Unsolicited: tag=03, enabled=1
  Connection: 4
 0x15* 0x16 0x17 0x1e


Node 0x0d [Pin Complex] wcaps 0x400183: Stereo Amp-In
  Control: name="Speaker Phantom Jack", index=0, device=0
  Amp-In caps: N/A
  Amp-In vals:  [0x00 0x00]
  Pincap 0x003f: IN OUT HP Detect Trigger ImpSense
  Pin Default 0x90170110: [Fixed] Speaker at Int N/A
Conn = Analog, Color = Unknown
DefAssociation = 0x1, Sequence = 0x0
Misc = NO_PRESENCE
  Pin-ctls: 0x00:
  Unsolicited: tag=00, enabled=0
  Connection: 4
 0x15 0x16 0x17* 0x1e

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

Title:
  Dell 1535 no sound from speakers, headphone out is ok

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  System: Dell studi 1535 with 12.04.03 i686 
  There is 3 jacks at left panel: mic, headphone, headphone.  Also system has 
buildin speackers. They doesnt work. 
  1) I've tried with alsamixer and pavucontrol - no luck.
  2) Tried with different modprobe options like options  snd-hda-intel 
model=dell-m6 / auto . No luck

  Any idea how to fix it one and forewer ?


  System information
  #uname -a
  Linux necron 3.8.0-31-generic #46~precise1-Ubuntu SMP Wed Sep 11 17:49:16 UTC 
2013 i686 i686 i386 GNU/Linux Description:  Ubuntu 12.04.3 LTS

  # lspci | grep Audio
  00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio 
Controller (rev 03)
  01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] RV620 HDMI Audio 
[Radeon HD 3400 Series]

  alsactl version 1.0.25

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1238144/+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 1239499] [NEW] Java error using xserver-xorg-xmir

2013-10-13 Thread marcobra (Marco Braida)

Public bug reported:

Description:Ubuntu 13.10
Release:13.10
Codename:   saucy

I was trying Mir with Josm (Java Open Street Map) editor

Please read  http://josm.openstreetmap.de/ticket/9184

Sounds like a problem of "Mir" or java with "Mir".

Thank...

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


** Tags: java mir

** Tags added: mir

** Tags added: java

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

Title:
  Java error using xserver-xorg-xmir

Status in “xorg-server” package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 13.10
  Release:  13.10
  Codename: saucy

  I was trying Mir with Josm (Java Open Street Map) editor

  Please read  http://josm.openstreetmap.de/ticket/9184

  Sounds like a problem of "Mir" or java with "Mir".

  Thank...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1239499/+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 1238144] Re: Dell 1535 no sound from speakers, headphone out is ok

seem support 4.0  but still missing Headphone Jack Mode for switch two
headphones to Line Out


> PCM 0 p 44100 4 16
Open PCM 92HD73C1X5 Analog for play
Available PCM parameters:
  channels: 2/4
  formats: S16_LE S32_LE
  rates: 44100 48000 88200 96000 192000
Prepare PCM, rate=44100, channels=4, format=16 bits
PCM format_val = 0x4013
hda_codec_setup_stream: NID=0x15, stream=0x1, channel=0, format=0x4013
send: NID=0x15, VERB=0xf06(get_channel_streamid), PARM=0x0
receive: 0x0
send: NID=0x15, VERB=0x706(set_channel_streamid), PARM=0x10
send: NID=0x15, VERB=0xa00(get_stream_format), PARM=0x0
receive: 0x0
send: NID=0x15, VERB=0x240(set_stream_format), PARM=0x13
hda_codec_setup_stream: NID=0x16, stream=0x1, channel=2, format=0x4013
send: NID=0x16, VERB=0xf06(get_channel_streamid), PARM=0x0
receive: 0x0
send: NID=0x16, VERB=0x706(set_channel_streamid), PARM=0x12
send: NID=0x16, VERB=0xa00(get_stream_format), PARM=0x0
receive: 0x0
send: NID=0x16, VERB=0x240(set_stream_format), PARM=0x13
hda_codec_setup_stream: NID=0x17, stream=0x1, channel=0, format=0x4013
send: NID=0x17, VERB=0xf06(get_channel_streamid), PARM=0x0
receive: 0x0
send: NID=0x17, VERB=0x706(set_channel_streamid), PARM=0x10
send: NID=0x17, VERB=0xa00(get_stream_format), PARM=0x0
receive: 0x0
send: NID=0x17, VERB=0x240(set_stream_format), PARM=0x13
PCM Clean up
hda_codec_cleanup_stream: NID=0x15
hda_codec_cleanup_stream: NID=0x16
hda_codec_cleanup_stream: NID=0x17
Close PCM

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

Title:
  Dell 1535 no sound from speakers, headphone out is ok

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  System: Dell studi 1535 with 12.04.03 i686 
  There is 3 jacks at left panel: mic, headphone, headphone.  Also system has 
buildin speackers. They doesnt work. 
  1) I've tried with alsamixer and pavucontrol - no luck.
  2) Tried with different modprobe options like options  snd-hda-intel 
model=dell-m6 / auto . No luck

  Any idea how to fix it one and forewer ?


  System information
  #uname -a
  Linux necron 3.8.0-31-generic #46~precise1-Ubuntu SMP Wed Sep 11 17:49:16 UTC 
2013 i686 i686 i386 GNU/Linux Description:  Ubuntu 12.04.3 LTS

  # lspci | grep Audio
  00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio 
Controller (rev 03)
  01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] RV620 HDMI Audio 
[Radeon HD 3400 Series]

  alsactl version 1.0.25

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1238144/+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 1239351] Re: Hang or crash after installing nvidia-319 (amd64 only)

Is the nvidia driver failing to build? Is it complete in /var/lib/dkms/... ?
The attachment in comment #1 does not show any nvidia driver installed. So 
please look for logs in:
/var/lib/dkms/nvidia* ...
and attach them here.

If it is installed, please confirm with "dpkg -l | grep nvidia" and also
try to get some kind of log from the failed kernel boot. Or even photos.

** Changed in: nvidia-graphics-drivers-319 (Ubuntu)
   Status: New => Incomplete

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

Title:
  Hang or crash after installing nvidia-319 (amd64 only)

Status in “nvidia-graphics-drivers-319” package in Ubuntu:
  Incomplete

Bug description:
  A fresh install of Saucy/amd64 from either the final beta or today's
  daily build fails to boot after installing the proprietary nvidia
  driver. A parallel install of the same daily build, only x86, is not
  affected.

  My graphics card (Zotac GT430 (GF108 chip)) is apparently not
  supported by nouveau, and not recognized as such, so I must add
  nomodeset in order to boot the live cd and install. In both cases the
  proprietary driver was installed from System Settings / Software &
  Updates / Additional Drivers after the first boot. I then removed
  "nomodeset" from /etc/default/grub, did update-grub -u -k all and
  rebooted.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: nvidia-319 319.32-0ubuntu7
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Sun Oct 13 15:26:42 2013
  InstallationDate: Installed on 2013-10-13 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131013)
  MarkForUpload: True
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-graphics-drivers-319
  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-319/+bug/1239351/+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 1238144] Re: Dell 1535 no sound from speakers, headphone out is ok

1. Sound play from both HP jack
2. when HP are plugged to left one and unplugged first time - sound doesnt go 
to speakers
3. when HP are plugged to right one and unplugged first time - sound plays from 
speakers
4. After 3'd option sound also plays from speakers in 2'd option.


> jack 0x0a 1
send: NID=0xa, VERB=0xf09(get_pin_sense), PARM=0x0
receive: 0x8000
send: NID=0xd, VERB=0x707(set_pin_ctl), PARM=0x0
send: NID=0x1, VERB=0x7ec(set_power_map), PARM=0xf6
CTL Notify: Headphone Front Jack:0, mask=1
JACK report Headphone Front, status 1
JACK report Headphone Surround, status 0
JACK report Mic, status 0
> jack 0x0f 1
send: NID=0xf, VERB=0xf09(get_pin_sense), PARM=0x0
receive: 0x8000
send: NID=0x1, VERB=0x7ec(set_power_map), PARM=0xd6
JACK report Headphone Front, status 1
CTL Notify: Headphone Surround Jack:0, mask=1
JACK report Headphone Surround, status 1
JACK report Mic, status 0
> PCM 0 p 44100 2 16
Open PCM 92HD73C1X5 Analog for play
Available PCM parameters:
  channels: 2/4
  formats: S16_LE S32_LE
  rates: 44100 48000 88200 96000 192000
Prepare PCM, rate=44100, channels=2, format=16 bits
PCM format_val = 0x4011
hda_codec_setup_stream: NID=0x15, stream=0x1, channel=0, format=0x4011
send: NID=0x15, VERB=0xf06(get_channel_streamid), PARM=0x0
receive: 0x0
send: NID=0x15, VERB=0x706(set_channel_streamid), PARM=0x10
send: NID=0x15, VERB=0xa00(get_stream_format), PARM=0x0
receive: 0x0
send: NID=0x15, VERB=0x240(set_stream_format), PARM=0x11
hda_codec_setup_stream: NID=0x16, stream=0x1, channel=0, format=0x4011
send: NID=0x16, VERB=0xf06(get_channel_streamid), PARM=0x0
receive: 0x0
send: NID=0x16, VERB=0x706(set_channel_streamid), PARM=0x10
send: NID=0x16, VERB=0xa00(get_stream_format), PARM=0x0
receive: 0x0
send: NID=0x16, VERB=0x240(set_stream_format), PARM=0x11
hda_codec_setup_stream: NID=0x17, stream=0x1, channel=0, format=0x4011
send: NID=0x17, VERB=0xf06(get_channel_streamid), PARM=0x0
receive: 0x0
send: NID=0x17, VERB=0x706(set_channel_streamid), PARM=0x10
send: NID=0x17, VERB=0xa00(get_stream_format), PARM=0x0
receive: 0x0
send: NID=0x17, VERB=0x240(set_stream_format), PARM=0x11
PCM Clean up
hda_codec_cleanup_stream: NID=0x15
hda_codec_cleanup_stream: NID=0x16
hda_codec_cleanup_stream: NID=0x17
Close PCM


> jack 0x0a 0
send: NID=0xa, VERB=0xf09(get_pin_sense), PARM=0x0
receive: 0x0
send: NID=0x1, VERB=0x7ec(set_power_map), PARM=0xd7
CTL Notify: Headphone Front Jack:0, mask=1
JACK report Headphone Front, status 0
JACK report Headphone Surround, status 1
JACK report Mic, status 0


> jack 0x0f 0
send: NID=0xf, VERB=0xf09(get_pin_sense), PARM=0x0
receive: 0x0
send: NID=0xd, VERB=0x707(set_pin_ctl), PARM=0x40
send: NID=0x1, VERB=0x7ec(set_power_map), PARM=0xf7
JACK report Headphone Front, status 0
CTL Notify: Headphone Surround Jack:0, mask=1
JACK report Headphone Surround, status 0
JACK report Mic, status 0


pinctl of speaker node 0x0d change to 0x40 OUT after both headphones are 
unplugged


> list
1: Headphone Playback Volume:0 (1)
2: Headphone Playback Switch:0 (1)
3: Headphone Playback Volume:1 (1)
4: Headphone Playback Switch:1 (1)

http://cgit.freedesktop.org/pulseaudio/pulseaudio/tree/src/modules/alsa/mixer/paths

did pulseaudio check the "Headphone Front Jack" and "Headphone Surround
Jack" ?


do the user manual or spec of this notebook mention support of surround51 by 
two hp and mic jacks ?

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

Title:
  Dell 1535 no sound from speakers, headphone out is ok

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  System: Dell studi 1535 with 12.04.03 i686 
  There is 3 jacks at left panel: mic, headphone, headphone.  Also system has 
buildin speackers. They doesnt work. 
  1) I've tried with alsamixer and pavucontrol - no luck.
  2) Tried with different modprobe options like options  snd-hda-intel 
model=dell-m6 / auto . No luck

  Any idea how to fix it one and forewer ?


  System information
  #uname -a
  Linux necron 3.8.0-31-generic #46~precise1-Ubuntu SMP Wed Sep 11 17:49:16 UTC 
2013 i686 i686 i386 GNU/Linux Description:  Ubuntu 12.04.3 LTS

  # lspci | grep Audio
  00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio 
Controller (rev 03)
  01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] RV620 HDMI Audio 
[Radeon HD 3400 Series]

  alsactl version 1.0.25

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1238144/+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 1239051] Re: fglrx 2:13.200-0ubuntu1: fglrx kernel module failed to build

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

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 1195705, 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 1195705
   fglrx kernel module fails to build on kernel 3.10 [error: implicit 
declaration of function ‘create_proc_entry’]

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

Title:
  fglrx 2:13.200-0ubuntu1: fglrx kernel module failed to build

Status in “fglrx-installer” package in Ubuntu:
  New

Bug description:
  I uninstall "fglrx*" in the "recovery mode".  And then I upgrade the
  system, then I reboot. And the error occur.

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: fglrx (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DKMSKernelVersion: 3.11.0-12-generic
  Date: Sat Oct 12 13:03:18 2013
  DistUpgraded: 2013-09-06 00:20:42,753 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.2.16, 3.11.0-11-generic, i686: installed
   virtualbox, 4.2.16, 3.11.0-12-generic, i686: installed
   virtualbox, 4.2.16, 3.11.0-7-generic, i686: installed
   virtualbox, 4.2.16, 3.11.0-8-generic, i686: installed
   virtualbox, 4.2.16, 3.11.0-9-generic, i686: installed
  DuplicateSignature: 
dkms:fglrx:2:13.200-0ubuntu1:/var/lib/dkms/fglrx/12.104/build/2.6.x/drm_proc.h:98:2:
 error: implicit declaration of function ‘create_proc_entry’ 
[-Werror=implicit-function-declaration]
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Radeon HD 7470M [1043:2002]
  InstallationDate: Installed on 2013-08-26 (47 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MachineType: ASUSTeK Computer Inc. K54HR
  MarkForUpload: True
  PackageVersion: 2:13.200-0ubuntu1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=8f13661b-be64-4220-acfb-8f2684193dd4 ro plymouth:debug drm.debug=0xe 
radeon.dpm=1
  SourcePackage: fglrx-installer
  Title: fglrx 2:13.200-0ubuntu1: fglrx kernel module failed to build
  UpgradeStatus: Upgraded to saucy on 2013-09-05 (36 days ago)
  dmi.bios.date: 06/20/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K54HR.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K54HR
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK54HR.205:bd06/20/2012:svnASUSTeKComputerInc.:pnK54HR:pvr1.0:rvnASUSTeKComputerInc.:rnK54HR:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K54HR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Sat Oct 12 13:38:56 2013
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output  HDMI-0
LVDS   VGA-0
  xserver.version: 2:1.14.3-3ubuntu1
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1239051/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : deskto

[Desktop-packages] [Bug 1238624] Re: fglrx 2:9.010-0ubuntu3: fglrx kernel module failed to build

You seem to be missing DKMSBuildLog.txt or similar.

Please try reproducing the bug again and log a new bug report.

** Changed in: fglrx-installer (Ubuntu)
   Status: New => Incomplete

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

Title:
  fglrx 2:9.010-0ubuntu3: fglrx kernel module failed to build

Status in “fglrx-installer” package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 12.10 to 13.04 I have had many issues with 'low
  graphics mode' & cannot fix this, despite trying everything suggested
  in various pages. So I decided to try & install flgrx to see if that
  would help. Which resulted in this issue.

  I am installing on a Dell Inspiron R15.

  ProblemType: Package
  DistroRelease: Ubuntu 13.04
  Package: fglrx 2:9.010-0ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  Uname: Linux 3.8.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDmesg:
   [ 1618.380222] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
   [ 1618.380309] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
   [ 1618.380394] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
   [ 1618.380481] ERROR @wl_dev_intvar_get : error (-1)
   [ 1618.380561] ERROR @wl_cfg80211_get_tx_power : error (-1)
  DKMSKernelVersion: 3.8.0-31-generic
  Date: Fri Oct 11 12:52:06 2013
  DistUpgraded: 2013-10-11 07:33:05,373 DEBUG enabling apt cron job
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.20.155.1+bdcom, 3.5.0-41-generic, x86_64: installed
   bcmwl, 6.20.155.1+bdcom, 3.8.0-31-generic, x86_64: installed
   fglrx, 9.010: added
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 18) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0447]
  InstallationDate: Installed on 2011-10-21 (720 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  Lsusb:
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0c45:641d Microdia 1.3 MPixel Integrated Webcam
  MachineType: Dell Inc. Inspiron N5010
  MarkForUpload: True
  PackageVersion: 2:9.010-0ubuntu3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic 
root=UUID=1f0d6077-6462-40fc-b5bf-9ba187069fb2 ro recovery nomodeset
  SourcePackage: fglrx-installer
  Title: fglrx 2:9.010-0ubuntu3: fglrx kernel module failed to build
  UnitySupportTest:
   Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with 
exit code 1: X Error of failed request:  BadRequest (invalid request code or no 
such operation)
 Major opcode of failed request:  153 (GLX)
 Minor opcode of failed request:  19 (X_GLXQueryServerString)
 Serial number of failed request:  22
 Current serial number in output stream:  22
  UpgradeStatus: Upgraded to raring on 2013-10-11 (0 days ago)
  dmi.bios.date: 04/21/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0WXY9J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A13
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A13
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd04/21/2011:svnDellInc.:pnInspironN5010:pvrA13:rvnDellInc.:rn0WXY9J:rvrA13:cvnDellInc.:ct8:cvrA13:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A13
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.43-0ubuntu1.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1238624/+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 969860] Re: fglrx uses 100% CPU when screen turns off (spinning in glXWaitVideoSyncSGI or glXSwapBuffers)

OK then. I haven't retested myself but trust both comment #105 and the
upstream bug info. Therefore fix released somewhere around:

fglrx-installer (2:13.101-0ubuntu1) saucy; urgency=low
fglrx-installer-updates (2:13.101-0ubuntu1) saucy; urgency=low

** Changed in: fglrx-installer (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: fglrx-installer-updates (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  fglrx uses 100% CPU when screen turns off (spinning in
  glXWaitVideoSyncSGI or glXSwapBuffers)

Status in Compiz:
  Invalid
Status in Compiz 0.9.8 series:
  Invalid
Status in Compiz Core:
  Invalid
Status in AMD fglrx video driver:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  Fix Released
Status in “compiz” package in Ubuntu:
  Invalid
Status in “fglrx-installer” package in Ubuntu:
  Fix Released
Status in “fglrx-installer-updates” package in Ubuntu:
  Fix Released
Status in “gnome-shell” package in Ubuntu:
  Invalid

Bug description:
  WORKAROUND (1):
  1. Open Catalyst Control Center.
  2. Go to 3D > More Settings.
  3. Set "Wait for vertical refresh" to "On, unless application specifies".
  And if that doesn't work, then also do:
  4. Run "ccsm"
  5. In Workarounds, enable "Force full screen redraw (buffer swap) on repaint".

  WORKAROUND (2):
  1. Run ccsm (from package compizconfig-settings-manager)
  2. In OpenGL > Sync To VBlank = OFF

  TEST CASE:
  1. Monitor compiz CPU usage (from /proc//stat or top in batch 
mode)
  2. In "brightness and lock" settings set "Turn screen off when inactive" to 1 
minute
  3. Wait until screen turns off
  4. Move mouse or press a key to turn screen back on
  5. Check the CPU usage from the monitor

  ACTUAL RESULT:
  When screen turns off compiz goes to 100%
  When the screen turns back on, cpu usage drops immediately to a normal value
  The graph attached shows %CPU of compiz with a sample per second. The graph 
has been captured on a system with  a Radeon HD5770 and fglrx if that matter

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: compiz 1:0.9.7.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
  Uname: Linux 3.2.0-21-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:

  ApportVersion: 2.0-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Sat Mar 31 10:17:48 2012
  DistUpgraded: 2012-02-01 00:15:24,616 DEBUG enabling apt cron job
  DistroCodename: precise
  DistroVariant: ubuntu
  MachineType: Gigabyte Technology Co., Ltd. GA-890GPA-UD3H
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-21-generic 
root=UUID=cf89ba34-108b-404d-9804-32d54a1df2ea ro quiet splash vt.handoff=7
  SourcePackage: compiz
  UpgradeStatus: Upgraded to precise on 2012-01-31 (59 days ago)
  dmi.bios.date: 07/23/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FD
  dmi.board.name: GA-890GPA-UD3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd07/23/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-890GPA-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-890GPA-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-890GPA-UD3H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.7.2-0ubuntu4
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/969860/+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 1170172] Re: totally unreadable weird symbols instead of text in update-manager / update-notifier / ubuntu-release-upgrader

** Changed in: lightdm
   Status: New => Invalid

** No longer affects: lightdm

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

Title:
  totally unreadable weird symbols instead of text in update-manager /
  update-notifier / ubuntu-release-upgrader

Status in “fontconfig” package in Ubuntu:
  New
Status in “ubuntu-release-upgrader” package in Ubuntu:
  New
Status in “update-manager” package in Ubuntu:
  New
Status in “update-notifier” package in Ubuntu:
  New
Status in “xorg-server” package in Ubuntu:
  New

Bug description:
  Every so often the update-manager, update-notifier or ubuntu-release-
  upgrader normally pops up a window mentioning the latest new Ubuntu
  release. However, after installing lots of Ubuntu fonts and some
  graphite fonts, the upgrade notification popup window has stopped
  showing any text and started showing only weird symbols like boxes and
  dots, making it totally unreadable. All of the installed fonts
  installed without errors and all of them seem to be shown correctly in
  gucharmap. Other applications like gnome-terminal, gedit, konqueror
  etc are still working ok without displaying these weird symbols.

  Why are the Ubuntu release upgrade notifications suddenly being
  displayed in a weird font?

  This is update-manager 1:0.156.14.11 and update-notifier
  0.119ubuntu8.6 in Ubuntu 12.04.02 precise.

  See the sequence attached of 12 screenshots of the weird symbols in
  ubuntu-release-upgrader, showing an attempt to copy-select the lines
  of symbols in the popup window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1170172/+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 1238144] Re: Dell 1535 no sound from speakers, headphone out is ok

post the output of amixer -c0 contents


using hda-emu, the pin fixup change 0x0f Line Out to another headphone


autoconfig: line_outs=1 (0xd/0x0/0x0/0x0/0x0) type:speaker
   speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
   hp_outs=2 (0xa/0xf/0x0/0x0/0x0)
   mono: mono_out=0x0
   inputs:
 Mic=0xe
 Internal Mic=0x13

==> Best config: lo_type=2, wired=1, mio=1
multi_outs = a/f/0/0 : 15/16/0/0 (type HP)
  out path: depth=2 :15:0a
  out path: depth=2 :16:0f
spk_outs = d/0/0/0 : 17/0/0/0
  spk path: depth=2 :17:0d
  mix path: depth=5 :15:2b:1d:1e:0a
  mix path: depth=5 :15:2b:1d:1e:0d

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

Title:
  Dell 1535 no sound from speakers, headphone out is ok

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  System: Dell studi 1535 with 12.04.03 i686 
  There is 3 jacks at left panel: mic, headphone, headphone.  Also system has 
buildin speackers. They doesnt work. 
  1) I've tried with alsamixer and pavucontrol - no luck.
  2) Tried with different modprobe options like options  snd-hda-intel 
model=dell-m6 / auto . No luck

  Any idea how to fix it one and forewer ?


  System information
  #uname -a
  Linux necron 3.8.0-31-generic #46~precise1-Ubuntu SMP Wed Sep 11 17:49:16 UTC 
2013 i686 i686 i386 GNU/Linux Description:  Ubuntu 12.04.3 LTS

  # lspci | grep Audio
  00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio 
Controller (rev 03)
  01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] RV620 HDMI Audio 
[Radeon HD 3400 Series]

  alsactl version 1.0.25

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1238144/+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 1239382] Re: [ICH4 - Intel 82801DB-ICH4, playback] No sound at all

https://wiki.ubuntu.com/PulseAudio/Log

post the pulseaudio verbose log



** Changed in: alsa-driver (Ubuntu)
   Status: New => Incomplete

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

Title:
  [ICH4 - Intel 82801DB-ICH4, playback] No sound at all

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  My sound devices are not working  on lxde 12 4.I am using intel
  d845gvsr board.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.5.0-41.64~precise1-generic 3.5.7.21
  Uname: Linux 3.5.0-41-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.0.1-0ubuntu17.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kh 2257 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with ALC202 at irq 17'
 Mixer name : 'Realtek ALC202 rev 0'
 Components : 'AC97a:414c4740'
 Controls  : 37
 Simple ctrls  : 23
  Date: Sun Oct 13 21:09:04 2013
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:I82801DBICH4 
failed
  Symptom_Card: Built-in Audio - Intel 82801DB-ICH4
  Symptom_DevicesInUse:
   2257/dev/snd/controlC0:  khF pulseaudio
   AND
  Symptom_Type: No sound at all
  Title: [ICH4 - Intel 82801DB-ICH4, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserAsoundrc:
   
  dmi.bios.date: 02/16/2004
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: VA84510A.86A.0030.P10.0402160229
  dmi.board.name: D845GVSR
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAC45439-302
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrVA84510A.86A.0030.P10.0402160229:bd02/16/2004:svn:pn:pvr:rvnIntelCorporation:rnD845GVSR:rvrAAC45439-302:cvn:ct2:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1239382/+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 1239382] Re: [ICH4 - Intel 82801DB-ICH4, playback] No sound at all

take a look at the block diagram in ALC202 datasheet

http://www.realtek.com.tw/products/productsView.aspx?Langid=1&PFid=29&Level=5&Conn=4&ProdID=53

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

Title:
  [ICH4 - Intel 82801DB-ICH4, playback] No sound at all

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  My sound devices are not working  on lxde 12 4.I am using intel
  d845gvsr board.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.5.0-41.64~precise1-generic 3.5.7.21
  Uname: Linux 3.5.0-41-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.0.1-0ubuntu17.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kh 2257 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with ALC202 at irq 17'
 Mixer name : 'Realtek ALC202 rev 0'
 Components : 'AC97a:414c4740'
 Controls  : 37
 Simple ctrls  : 23
  Date: Sun Oct 13 21:09:04 2013
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:I82801DBICH4 
failed
  Symptom_Card: Built-in Audio - Intel 82801DB-ICH4
  Symptom_DevicesInUse:
   2257/dev/snd/controlC0:  khF pulseaudio
   AND
  Symptom_Type: No sound at all
  Title: [ICH4 - Intel 82801DB-ICH4, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserAsoundrc:
   
  dmi.bios.date: 02/16/2004
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: VA84510A.86A.0030.P10.0402160229
  dmi.board.name: D845GVSR
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAC45439-302
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrVA84510A.86A.0030.P10.0402160229:bd02/16/2004:svn:pn:pvr:rvnIntelCorporation:rnD845GVSR:rvrAAC45439-302:cvn:ct2:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1239382/+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 1236689] Re: Banshee crashes while playing music

2013-10-13 Thread divinebovine

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

Loong Jin, looks like you're right.  Disabling gapless playback prevents
banshee from crashing.

** This bug has been marked a duplicate of bug 879076
   Banshee crashes with System.ObjectDisposed exception in Hyena.Data.Sqlite 
code from System.Threading

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

Title:
  Banshee crashes while playing music

Status in “banshee” package in Ubuntu:
  New

Bug description:
  While banshee is playing music in the background, it crashes randomly
  (after playing several songs).  Running from the command line yields
  the following:

  Unhandled Exception: System.ObjectDisposedException: The object was used 
after being disposed.
at System.Threading.WaitHandle.CheckDisposed () [0x0] in :0 
at System.Threading.EventWaitHandle.Reset () [0x0] in :0 
at (wrapper remoting-invoke-with-check) 
System.Threading.EventWaitHandle:Reset ()
at Hyena.Data.Sqlite.HyenaSqliteCommand.Execute 
(Hyena.Data.Sqlite.HyenaSqliteConnection hconnection, 
Hyena.Data.Sqlite.Connection connection) [0x0] in :0 
at Hyena.Data.Sqlite.HyenaSqliteConnection.ProcessQueue () [0x0] in 
:0 
at System.Threading.Thread.StartInternal () [0x0] in :0 
  [ERROR] FATAL UNHANDLED EXCEPTION: System.ObjectDisposedException: The object 
was used after being disposed.
at System.Threading.WaitHandle.CheckDisposed () [0x0] in :0 
at System.Threading.EventWaitHandle.Reset () [0x0] in :0 
at (wrapper remoting-invoke-with-check) 
System.Threading.EventWaitHandle:Reset ()
at Hyena.Data.Sqlite.HyenaSqliteCommand.Execute 
(Hyena.Data.Sqlite.HyenaSqliteConnection hconnection, 
Hyena.Data.Sqlite.Connection connection) [0x0] in :0 
at Hyena.Data.Sqlite.HyenaSqliteConnection.ProcessQueue () [0x0] in 
:0 
at System.Threading.Thread.StartInternal () [0x0] in :0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1236689/+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 1097521] Re: black screen with using ssd

** Project changed: lightdm => lightdm (Ubuntu)

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

Title:
  black screen with using ssd

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Some Ubuntu users are reporting LightDM errors when using a SSD: about
  half the time when starting the computer, LightDM (the default Ubuntu
  display manager) doesn't load correctly and only a black screen and a
  blinking command line cursor shows up

  http://www.webupd8.org/2013/01/ubuntu-lightdm-black-screen-when-
  using.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1097521/+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 1097521] Re: black screen with using ssd

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

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

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

Title:
  black screen with using ssd

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Some Ubuntu users are reporting LightDM errors when using a SSD: about
  half the time when starting the computer, LightDM (the default Ubuntu
  display manager) doesn't load correctly and only a black screen and a
  blinking command line cursor shows up

  http://www.webupd8.org/2013/01/ubuntu-lightdm-black-screen-when-
  using.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1097521/+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 1080111] Re: VNC (vino) doesn't operate until a particular user is logged in

LightDM already supports VNC login, see
http://askubuntu.com/questions/79753/how-can-i-start-an-xvnc-server-at-
boot

** Changed in: lightdm
   Status: New => Invalid

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

Title:
  VNC (vino) doesn't operate until a particular user is logged in

Status in Light Display Manager:
  Invalid
Status in “unity” package in Ubuntu:
  New

Bug description:
  Vino doesn't start until a particular user is logged in, and that user
  has "desktop sharing" enabled. Consequently, unless "auto log-in" is
  set for a user, and "desktop sharing" is enabled for that user, there
  is no way to use VNC (vinagre) to log-in to a remote Ubuntu system.
  Vino should be operable at the log-in phase (lightdm) to enable the
  very basic functionality of remote access to a Ubuntu desktop system.

  My suggestion is to have a way to start vino at the point where
  lightdm is started. Even if I had to restart vinagre after logging in
  via lightdm, at least it would be possible to remotely access the
  desktop environment.

  Alternatively, I have submitted a bug report on the fact that "auto
  log-in" only functions on initial bootstrap - it doesn't function
  after log-out.

  lsb_release -rd
  Description:  Ubuntu 12.04.1 LTS
  Release:  12.04
  (However, this problem has been present for several releases.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1080111/+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 1239490] [NEW] gdm: When left at login and falls to power saving. Background image is not footfall.

Public bug reported:

gdm: When left at login and falls to power saving. Background image is
not footfall.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: gdm 3.8.4-0ubuntu2
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
Architecture: amd64
Date: Mon Oct 14 03:07:30 2013
InstallationDate: Installed on 2013-09-12 (31 days ago)
InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
MarkForUpload: True
SourcePackage: gdm
UpgradeStatus: Upgraded to saucy on 2013-09-12 (31 days ago)
mtime.conffile..etc.init.d.gdm: 2013-10-09T16:41:02

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


** Tags: amd64 apport-bug gnome3 saucy

** Tags added: gnome3

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

Title:
  gdm: When left at login and falls to power saving. Background image is
  not footfall.

Status in “gdm” package in Ubuntu:
  New

Bug description:
  gdm: When left at login and falls to power saving. Background image is
  not footfall.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gdm 3.8.4-0ubuntu2
  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
  Architecture: amd64
  Date: Mon Oct 14 03:07:30 2013
  InstallationDate: Installed on 2013-09-12 (31 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  SourcePackage: gdm
  UpgradeStatus: Upgraded to saucy on 2013-09-12 (31 days ago)
  mtime.conffile..etc.init.d.gdm: 2013-10-09T16:41:02

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1239490/+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 1097521] [NEW] black screen with using ssd

You have been subscribed to a public bug:

Some Ubuntu users are reporting LightDM errors when using a SSD: about
half the time when starting the computer, LightDM (the default Ubuntu
display manager) doesn't load correctly and only a black screen and a
blinking command line cursor shows up

http://www.webupd8.org/2013/01/ubuntu-lightdm-black-screen-when-
using.html

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

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

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

[Desktop-packages] [Bug 1239392] Re: Lenovo IdeaPad Yoga 13: Inverted Internal microphone (phase inversion)

http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?id=e4db0952e542090c605fd41d31d761f1b4624f4a

seem other ideapad also use same PCI SSID 17aa:3977

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

Title:
Lenovo IdeaPad Yoga 13: Inverted Internal microphone (phase inversion)

Status in “alsa-driver” package in Ubuntu:
New

Bug description:
As per this meta-bug:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978

Reporting for Lenovo IdeaPad Yoga 13. Inverted channel is visible when
recording stereo in audacity. Mono recording via pulseaudio gives
silence with occasional cracks somewhat corresponding to the sound
level around. Skype and pavucontrol level gauges are also affected.

Changes in balance in pavucontrol do not help with mono recording, I
don't know why.

I'm attaching two patches against oem-audio-hda-daily-
dkms-0.201310111402~ubuntu13.10.1 (https://launchpad.net/~ubuntu-
audio-dev/+archive/alsa-daily); either of them fixes the problem for
me (the -alt one may affect other hardware, though). No additional
steps were needed after applying a patch, building and installing the
package.

Output of alsa-info.sh is also attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1239392/+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 1239483] Re: mission-control-5 crashed with SIGSEGV in __libc_start_main()

2013-10-13 Thread Apport retracing service

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

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 #621048, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 621048
   mission-control-5 crashed with SIGSEGV in __libc_start_main()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  mission-control-5 crashed with SIGSEGV in __libc_start_main()

Status in “telepathy-mission-control-5” package in Ubuntu:
  New

Bug description:
  Error keeps on popping, all the time.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: telepathy-mission-control-5 1:5.14.1-1ubuntu6
  ProcVersionSignature: Ubuntu 3.10.0-5.15-generic 3.10.2
  Uname: Linux 3.10.0-5-generic x86_64
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  Date: Mon Oct 14 06:07:40 2013
  ExecutablePath: /usr/lib/telepathy/mission-control-5
  MarkForUpload: True
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.10.0-5-generic 
root=UUID=d8042cf6-4e66-47d9-828d-56a14e87db80 ro quiet splash vt.handoff=7
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
  SegvAnalysis:
   Segfault happened at: 0x410260:  mov0x18(%rdi),%rdi
   PC (0x00410260) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: telepathy-mission-control-5
  StacktraceTop:
   ?? ()
   ?? ()
   __libc_start_main (main=0x40e2a0, argc=1, ubp_av=0x7fff00039088, 
init=, fini=, rtld_fini=, 
stack_end=0x7fff00039078) at libc-start.c:260
   ?? ()
  Title: mission-control-5 crashed with SIGSEGV in __libc_start_main()
  UpgradeStatus: Upgraded to saucy on 2013-06-12 (123 days ago)
  UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1239483/+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 1239392] Re: Lenovo IdeaPad Yoga 13: Inverted Internal microphone (phase inversion)

but Vendor Id: 0x14f1506e identify CX20590

you need PCI SSID 17aa:3977 or codec SSID 0x17aaa001  to identify your
Lenovo IdeaPad Yoga 13


Advanced information - PCI Vendor/Device/Subsystem ID's
!!---

00:1b.0 0403: 8086:1e20 (rev 04)
Subsystem: 17aa:3977


!!HDA-Intel Codec information
!!---


Codec: Conexant CX20590
Address: 0
AFG Function Id: 0x1 (unsol 1)
Vendor Id: 0x14f1506e
Subsystem Id: 0x17aaa001
Revision Id: 0x13

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

Title:
  Lenovo IdeaPad Yoga 13: Inverted Internal microphone (phase inversion)

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  As per this meta-bug:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978

  Reporting for Lenovo IdeaPad Yoga 13. Inverted channel is visible when
  recording stereo in audacity. Mono recording via pulseaudio gives
  silence with occasional cracks somewhat corresponding to the sound
  level around. Skype and pavucontrol level gauges are also affected.

  Changes in balance in pavucontrol do not help with mono recording, I
  don't know why.

  I'm attaching two patches against oem-audio-hda-daily-
  dkms-0.201310111402~ubuntu13.10.1 (https://launchpad.net/~ubuntu-
  audio-dev/+archive/alsa-daily); either of them fixes the problem for
  me (the -alt one may affect other hardware, though). No additional
  steps were needed after applying a patch, building and installing the
  package.

  Output of alsa-info.sh is also attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1239392/+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: [N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound at all: Subwoofer not working

http://git.alsa-project.org/?p=alsa-
utils.git;a=commit;h=951cb2c2974293db6e12ef067ae7001074887932

speaker test also allow you to specify chmap "FL,FR,FC,LFE"

it seem pulseaudio still not support chmap

you better send email to Tiwai and the reporter of
https://bugzilla.novell.com/show_bug.cgi?id=841645

how to change the 4 channel chmap when presence detect of node 0x1e if
this can indicate the presence of the subwoofer

** Bug watch added: Novell/SUSE Bugzilla #841645
   https://bugzilla.novell.com/show_bug.cgi?id=841645

-- 
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:
  Confirmed

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
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC663 Analog [ALC663 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC663 Analog [ALC663 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sam1898 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf7a1 irq 47'
     Mixer name : 'Realtek ALC663'
     Components : 'HDA:10ec0663,10431477,0012'
     Controls  : 23
     Simple ctrls  : 13
  CheckboxSubmission: 54021779511d0213081a2b1707bf951c
  CheckboxSystem: 4c773cd91921f9618cc2f1893bc1a87a
  Date: Thu Aug 23 22:38:00 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   1898  sam   F pulseaudio
   PID ACCESS COMMAND
  Symptom_Jack: Black Headphone Out, Right
  Symptom_Type: No sound at all
  Title: [N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N56VZ.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N56VZ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.204:bd05/11/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:

[Desktop-packages] [Bug 1040873] Re: [N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound at all: Subwoofer not working

2013-10-13 Thread meomic

if i understand this whole thing correctly then yes...

best if i could do live testing - i mean this can be done via dkms alsa? or i 
would need to compile whole kernel?
guide me a little bit where i should start to change code and i will do it

-- 
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:
  Confirmed

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
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC663 Analog [ALC663 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC663 Analog [ALC663 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sam1898 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf7a1 irq 47'
     Mixer name : 'Realtek ALC663'
     Components : 'HDA:10ec0663,10431477,0012'
     Controls  : 23
     Simple ctrls  : 13
  CheckboxSubmission: 54021779511d0213081a2b1707bf951c
  CheckboxSystem: 4c773cd91921f9618cc2f1893bc1a87a
  Date: Thu Aug 23 22:38:00 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   1898  sam   F pulseaudio
   PID ACCESS COMMAND
  Symptom_Jack: Black Headphone Out, Right
  Symptom_Type: No sound at all
  Title: [N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N56VZ.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N56VZ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.204:bd05/11/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N56VZ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  modified.conffile..etc.modprobe.d.alsa.base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2012-0

[Desktop-packages] [Bug 636720] Re: Touchpad sends a middle click instead of left click.

2013-10-13 Thread simplexion

This no longer appears to be an issue.

** Changed in: xserver-xorg-input-synaptics (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Touchpad sends a middle click instead of left click.

Status in “xserver-xorg-input-synaptics” package in Ubuntu:
  Invalid

Bug description:
  [Sorry. I thought it was a Firefox problem. Probably it is not.]
  It happens randomly.
  I use the left physical button of the touchpad and it fires a middle-click 
event.
  It doesn't happen on lucid using the same hardware.

  EDIT: I investigated further.
  This happens with any program.
  It does not happen when you tap to click, it occurs only when using the 
toucpad physical button.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
  Uname: Linux 2.6.35-20-generic i686
  NonfreeKernelModules: wl
  Architecture: i386
  Date: Mon Sep 13 01:51:14 2010
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
  ProcEnviron:
   LANG=it_IT.utf8
   SHELL=/bin/bash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/636720/+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 1199201] Re: [drm:i915_hangcheck_elapsed] ERROR Hangcheck timer elapsed... GPU hung

2013-10-13 Thread Akshay Bhat

I had a couple more instances of the bug. Ubuntu folks, let me know if
you guys care about finding the root cause of the issue. I am willing to
help debug.

Oct 13 20:01:15 Sweet kernel: [95880.715734] [drm:i915_hangcheck_elapsed] 
*ERROR* Hangcheck timer elapsed... GPU hung
Oct 13 20:01:15 Sweet kernel: [95880.715757] [drm] capturing error event; look 
for more information in /debug/dri/0/i915_error_state
Oct 13 20:01:15 Sweet kernel: [95880.741220] [drm:i915_wait_request] *ERROR* 
i915_wait_request returns -11 (awaiting 5692377 at 5692374, next 5692378)
Oct 13 20:03:48 Sweet kernel: [96033.918311] Watchdog[3582]: segfault at 0 ip 
7fd5a5faa79e sp 7fd598ead520 error 6 in chrome[7fd5a36db000+57c8000]
Oct 13 20:04:01 Sweet kernel: [96046.568390] Watchdog[32090]: segfault at 0 ip 
7fe65731d79e sp 7fe64a220520 error 6 in chrome[7fe654a4e000+57c8000]

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

Title:
  [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU
  hung

Status in “xorg” package in Ubuntu:
  New

Bug description:
  Issue has happened twice in the week now.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-48.74-generic 3.2.46
  Uname: Linux 3.2.0-48-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,resize,animation,workarounds,move,gnomecompat,imgpng,mousepoll,grid,snap,wall,place,vpswitch,unitymtgrabhandles,expo,session,ezoom,staticswitcher,fade,scale,unityshell]
  CompositorRunning: None
  Date: Mon Jul  8 21:43:08 2013
  DistUpgraded: 2012-04-27 04:49:48,715 DEBUG enabling apt cron job
  DistroCodename: precise
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes,
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21ce]
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root 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 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  MachineType: LENOVO 4177CTO
  MarkForUpload: True
  ProcEnviron:
   SHELL=/bin/bash
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-48-generic 
root=UUID=478a278b-dcf5-4f8b-8e3a-3d04f592c44a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to precise on 2012-04-27 (437 days ago)
  dmi.bios.date: 05/17/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET57WW (1.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4177CTO
  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:bvr83ET57WW(1.27):bd05/17/2011:svnLENOVO:pn4177CTO:pvrThinkPadT420:rvnLENOVO:rn4177CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4177CTO
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.7.12-0ubuntu2
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.39-0ubuntu0.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.6
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.13
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1199201/+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: [N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound at all: Subwoofer not working

do you mean the chaanel map when using asus-mode4 should be


Type = FIXED, Channels = 4
   FL FR NA LFE

-- 
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:
  Confirmed

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
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC663 Analog [ALC663 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC663 Analog [ALC663 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sam1898 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf7a1 irq 47'
     Mixer name : 'Realtek ALC663'
     Components : 'HDA:10ec0663,10431477,0012'
     Controls  : 23
     Simple ctrls  : 13
  CheckboxSubmission: 54021779511d0213081a2b1707bf951c
  CheckboxSystem: 4c773cd91921f9618cc2f1893bc1a87a
  Date: Thu Aug 23 22:38:00 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   1898  sam   F pulseaudio
   PID ACCESS COMMAND
  Symptom_Jack: Black Headphone Out, Right
  Symptom_Type: No sound at all
  Title: [N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N56VZ.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N56VZ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.204:bd05/11/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N56VZ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  modified.conffile..etc.modprobe.d.alsa.base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2012-08-23T22:27:03.314416

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1040873/+subsc

[Desktop-packages] [Bug 1239472] [NEW] nvidia driver breaks ubuntu irreversibly (uninstalling the package doesn't fix it)

Public bug reported:

Fresh install of Ubuntu 13.04
- sudo apt-get install nvidia-current
- reboot

=> the whole system becomes completely unusable. When you boot, there's
no Unity launcher nor Unity's top bar. Only an empty desktop. Windows
don't have borders nor title bars (apparently compiz crashes at
startup).

And the worst thing is that uninstalling nvidia-current (or nvidia-304),
won't revert the situation.

The only way I got Unity running again was by purging nvidia* (sudo apt-
get purge nvidia*) AND manually deleting /etc/X11/xorg.conf.

So
1 - either nvidia driver is broken, or sudo apt-get nvidia-current doesn't 
install it properly
2 - sudo apt-get remove should completely reverse the installation and it 
doesn't.

If you have the unlucky idea to try and install nvidia-current you may
end up with an unusable and apparently unrecoverable system, which can
be pretty hard to figure out how to fix.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: nvidia-current (not installed)
ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
Uname: Linux 3.8.0-31-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
Date: Mon Oct 14 01:42:19 2013
InstallationDate: Installed on 2013-10-11 (2 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
SourcePackage: nvidia-graphics-drivers-304
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug raring

** Description changed:

  Fresh install of Ubuntu 13.04
  - sudo apt-get install nvidia-current
  - reboot
  
  => the whole system becomes completely unusable. When you boot, there's
  no Unity launcher nor Unity's top bar. Only an empty desktop. Windows
  don't have borders nor title bars (apparently compiz crashes at
  startup).
  
  And the worst thing is that uninstalling nvidia-current (or nvidia-304),
  won't revert the situation.
  
  The only way I got Unity running again was by purging nvidia* (sudo apt-
  get purge nvidia*) AND manually deleting /etc/X11/xorg.conf.
  
  So
- 1 - nvidia driver is broken, or sudo apt-get nvidia-current doesn't install 
it properly
+ 1 - either nvidia driver is broken, or sudo apt-get nvidia-current doesn't 
install it properly
  2 - sudo apt-get remove should completely reverse the installation and it 
doesn't.
  
  If you have the unlucky idea to try and install nvidia-current you may
  end up with an unusable and apparently unrecoverable system, which can
  be pretty hard to figure out how to fix.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nvidia-current (not installed)
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  Uname: Linux 3.8.0-31-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Mon Oct 14 01:42:19 2013
  InstallationDate: Installed on 2013-10-11 (2 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: nvidia-graphics-drivers-304
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  nvidia driver breaks ubuntu irreversibly (uninstalling the package
  doesn't fix it)

Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  New

Bug description:
  Fresh install of Ubuntu 13.04
  - sudo apt-get install nvidia-current
  - reboot

  => the whole system becomes completely unusable. When you boot,
  there's no Unity launcher nor Unity's top bar. Only an empty desktop.
  Windows don't have borders nor title bars (apparently compiz crashes
  at startup).

  And the worst thing is that uninstalling nvidia-current (or
  nvidia-304), won't revert the situation.

  The only way I got Unity running again was by purging nvidia* (sudo
  apt-get purge nvidia*) AND manually deleting /etc/X11/xorg.conf.

  So
  1 - either nvidia driver is broken, or sudo apt-get nvidia-current doesn't 
install it properly
  2 - sudo apt-get remove should completely reverse the installation and it 
doesn't.

  If you have the unlucky idea to try and install nvidia-current you may
  end up with an unusable and apparently unrecoverable system, which can
  be pretty hard to figure out how to fix.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nvidia-current (not installed)
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  Uname: Linux 3.8.0-31-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Mon Oct 14 01:42:19 2013
  InstallationDate: Installed on 2013-10-11 (2 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: nvidia-graphics-drivers-304
  UpgradeStatus: No upgrade log

[Desktop-packages] [Bug 1215098] Re: iPhone with iOS 7 does not work on Ubuntu

2013-10-13 Thread Jeffery von Ronne

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

** This bug has been marked a duplicate of bug 1207812
   Iphone with iOS 7 does not work on Ubuntu

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

Title:
  iPhone with iOS 7 does not work on Ubuntu

Status in “libimobiledevice” package in Ubuntu:
  Confirmed

Bug description:
  Devices running iOS 7 now have a USB Pair Trust prompt that appears
  when the device is plugged into a machine. This prompt reads "Trust
  This Computer? Your settings and data will be accessible from this
  computer when connected via USB or Wi-Fi. [Trust] [Don't Trust]"

  Repro:
  1) Plug powered-on Apple device with iOS 7 into Ubuntu USB port

  Expected results: 
  The device should pair with the Ubuntu machine when "Trust" is tapped.

  Actual results: 
  When plugged into an Ubuntu machine, when the Trust button on the prompt is 
clicked, the iPhone buzzes twice, then repeats the prompt. This will repeat 
endlessly. 

  On the Ubuntu machine, a dialog reading "The device "[name of device]"
  is locked. Enter the passcode on the device and click "Try again".
  [Cancel] [Try again]" is displayed. However, no opportunity to enter
  the passcode on the device is ever displayed. Clicking "Try again"
  only re-displays this dialog, endlessly.

  
  System and package information:
  Description:  Ubuntu 13.04
  Release:  13.04

  libimobiledevice-utils:
Installed: 1.1.4-1ubuntu6.2
Candidate: 1.1.4-1ubuntu6.2
Version table:
   *** 1.1.4-1ubuntu6.2 0
  500 http://us.archive.ubuntu.com/ubuntu/ raring-updates/universe i386 
Packages
  500 http://security.ubuntu.com/ubuntu/ raring-security/universe i386 
Packages
  100 /var/lib/dpkg/status
   1.1.4-1ubuntu6 0
  500 http://us.archive.ubuntu.com/ubuntu/ raring/universe i386 Packages
  pcfqa@Lenovo-Ubuntu:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libimobiledevice-utils 1.1.4-1ubuntu6.2
  ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
  Uname: Linux 3.8.0-29-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: i386
  Date: Wed Aug 21 12:16:57 2013
  InstallationDate: Installed on 2012-04-27 (481 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libimobiledevice
  UpgradeStatus: Upgraded to raring on 2013-04-25 (117 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1215098/+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 1239159] Re: On renaming Documents folder for new language no renaming occure - a second Document folder is created

2013-10-13 Thread Gunnar Hjalmarsson

I noticed that there are previous bug reports about this way to deal
with renaming of folders with contents. You may want to check out bug
#226436, bug #556933, and bug #1001438.

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

Title:
  On renaming Documents folder for new language no renaming occure - a
  second Document folder is created

Status in “xdg-user-dirs” package in Ubuntu:
  Incomplete

Bug description:
  The original system language for installation was US english. Some
  days ago I have decided to set the system to a different
  language(german). On new login the system ask if the names of the
  standard folders in the home directory should be kept, or should be
  renamed.

  On choosing renaming from US-enlish to german names there is no
  renaming.

  Instead a second Documents folder in german language is
  created(called: Dokumente).

  As a result I have two Documents folders. One called in english the
  other in german.

  The really big problem is that they contain different files and do not
  share the files with each other.

  Steps to reproduce:
  1.Install the system in US-English
  2. After finished installation use the system settings -> Language to set the 
language to german
  3.Restart the system
  4.After login the system ask if the standard folders in the home folder 
directory should be renamed: Choose yes, rename in german
  5.See that instead of renaming the old "Documents" folder still exist and 
just a second (in german) "Dokumente" folder was created.
  6. See taht the contained files a different for both folders

  Expected: The renaming should be a renaming and not a creation of a
  second standard Document folder in a different language(here: German:
  "Dokumente")

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: language-selector-gnome 0.116
  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
  Architecture: amd64
  Date: Sat Oct 12 17:44:06 2013
  ExecutablePath: /usr/bin/gnome-language-selector
  InstallationDate: Installed on 2013-05-03 (162 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterpreterPath: /usr/bin/python3.3
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: language-selector
  UpgradeStatus: Upgraded to saucy on 2013-10-05 (7 days ago)
  --- 
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Dependencies:
   gcc-4.8-base 4.8.1-10ubuntu8
   libc6 2.17-93ubuntu4
   libgcc1 1:4.8.1-10ubuntu8
   multiarch-support 2.17-93ubuntu4
  DistroRelease: Ubuntu 13.10
  InstallationDate: Installed on 2013-05-03 (162 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  Package: xdg-user-dirs 0.15-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Tags:  saucy
  Uname: Linux 3.11.0-12-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2013-10-05 (7 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1239159/+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 1239159] Re: On renaming Documents folder for new language no renaming occure - a second Document folder is created

2013-10-13 Thread Gunnar Hjalmarsson

Thanks for the additional info.

The dialog shown, when you log in the first time after having switched
to German, states: "Hinweis: Bestehende Inhalte verden nicht
verschoben." (Please see the attachment xdg-user-dirs-dialog.png.) In
other words, it's expected behavior to keep old folders with contents.
This way the feature does not alter the paths to existing files, which
makes sense IMO.

Assuming that you had saved files in the Documents and Pictures folders,
I think this bug should be marked as invalid. However, I await your
further comments before doing so. Please let me know whether you agree
on my conclusion.

** Attachment added: "xdg-user-dirs-dialog.png"
   
https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1239159/+attachment/3877076/+files/xdg-user-dirs-dialog.png

** Changed in: xdg-user-dirs (Ubuntu)
   Status: New => Incomplete

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

Title:
  On renaming Documents folder for new language no renaming occure - a
  second Document folder is created

Status in “xdg-user-dirs” package in Ubuntu:
  Incomplete

Bug description:
  The original system language for installation was US english. Some
  days ago I have decided to set the system to a different
  language(german). On new login the system ask if the names of the
  standard folders in the home directory should be kept, or should be
  renamed.

  On choosing renaming from US-enlish to german names there is no
  renaming.

  Instead a second Documents folder in german language is
  created(called: Dokumente).

  As a result I have two Documents folders. One called in english the
  other in german.

  The really big problem is that they contain different files and do not
  share the files with each other.

  Steps to reproduce:
  1.Install the system in US-English
  2. After finished installation use the system settings -> Language to set the 
language to german
  3.Restart the system
  4.After login the system ask if the standard folders in the home folder 
directory should be renamed: Choose yes, rename in german
  5.See that instead of renaming the old "Documents" folder still exist and 
just a second (in german) "Dokumente" folder was created.
  6. See taht the contained files a different for both folders

  Expected: The renaming should be a renaming and not a creation of a
  second standard Document folder in a different language(here: German:
  "Dokumente")

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: language-selector-gnome 0.116
  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
  Architecture: amd64
  Date: Sat Oct 12 17:44:06 2013
  ExecutablePath: /usr/bin/gnome-language-selector
  InstallationDate: Installed on 2013-05-03 (162 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterpreterPath: /usr/bin/python3.3
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: language-selector
  UpgradeStatus: Upgraded to saucy on 2013-10-05 (7 days ago)
  --- 
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Dependencies:
   gcc-4.8-base 4.8.1-10ubuntu8
   libc6 2.17-93ubuntu4
   libgcc1 1:4.8.1-10ubuntu8
   multiarch-support 2.17-93ubuntu4
  DistroRelease: Ubuntu 13.10
  InstallationDate: Installed on 2013-05-03 (162 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  Package: xdg-user-dirs 0.15-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Tags:  saucy
  Uname: Linux 3.11.0-12-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2013-10-05 (7 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1239159/+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 969860] Re: fglrx uses 100% CPU when screen turns off (spinning in glXWaitVideoSyncSGI or glXSwapBuffers)

2013-10-13 Thread David

I've just upgraded to the Catalyst 13.11 Beta Drivers linked in #104 and
my CPU utilization issue has gone away.  When the monitor shuts off, the
CPU usage goes down instead of to 100%

I'm going to say "fixed for me with latest 13.11 drivers"

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

Title:
  fglrx uses 100% CPU when screen turns off (spinning in
  glXWaitVideoSyncSGI or glXSwapBuffers)

Status in Compiz:
  Invalid
Status in Compiz 0.9.8 series:
  Invalid
Status in Compiz Core:
  Invalid
Status in AMD fglrx video driver:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  Fix Released
Status in “compiz” package in Ubuntu:
  Invalid
Status in “fglrx-installer” package in Ubuntu:
  Confirmed
Status in “fglrx-installer-updates” package in Ubuntu:
  Confirmed
Status in “gnome-shell” package in Ubuntu:
  Invalid

Bug description:
  WORKAROUND (1):
  1. Open Catalyst Control Center.
  2. Go to 3D > More Settings.
  3. Set "Wait for vertical refresh" to "On, unless application specifies".
  And if that doesn't work, then also do:
  4. Run "ccsm"
  5. In Workarounds, enable "Force full screen redraw (buffer swap) on repaint".

  WORKAROUND (2):
  1. Run ccsm (from package compizconfig-settings-manager)
  2. In OpenGL > Sync To VBlank = OFF

  TEST CASE:
  1. Monitor compiz CPU usage (from /proc//stat or top in batch 
mode)
  2. In "brightness and lock" settings set "Turn screen off when inactive" to 1 
minute
  3. Wait until screen turns off
  4. Move mouse or press a key to turn screen back on
  5. Check the CPU usage from the monitor

  ACTUAL RESULT:
  When screen turns off compiz goes to 100%
  When the screen turns back on, cpu usage drops immediately to a normal value
  The graph attached shows %CPU of compiz with a sample per second. The graph 
has been captured on a system with  a Radeon HD5770 and fglrx if that matter

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: compiz 1:0.9.7.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
  Uname: Linux 3.2.0-21-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:

  ApportVersion: 2.0-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Sat Mar 31 10:17:48 2012
  DistUpgraded: 2012-02-01 00:15:24,616 DEBUG enabling apt cron job
  DistroCodename: precise
  DistroVariant: ubuntu
  MachineType: Gigabyte Technology Co., Ltd. GA-890GPA-UD3H
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-21-generic 
root=UUID=cf89ba34-108b-404d-9804-32d54a1df2ea ro quiet splash vt.handoff=7
  SourcePackage: compiz
  UpgradeStatus: Upgraded to precise on 2012-01-31 (59 days ago)
  dmi.bios.date: 07/23/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FD
  dmi.board.name: GA-890GPA-UD3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd07/23/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-890GPA-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-890GPA-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-890GPA-UD3H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.7.2-0ubuntu4
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/969860/+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 1234400] Re: Cannot log in users if their Xauthority file is corrupt.

2013-10-13 Thread Edwin Fine

This seems to happen every time I install a raring update or upgrade,
but I haven't updated often enough to swear to this.  I can tell you
that I had this problem twice, which is exactly 2 times more than I
should have.

Basically, I get the login greeter screen, type in my password, it goes
away for a couple of seconds, and then returns to the greeter screen
without any visible error message. This is a serious WTF moment.

I was able to work around it (after a *lot* of scratching around and
looking in /var/log/lightdm/ and elsewhere, which really didn't help
much, and online searches, which did, eventually), as follows.

In desperation, I created a new user using a console (Ctrl-Alt-F1)
session and usermod (lucky for me, I know a bit of sysadmin stuff). It
was able to log in with no problems, of course. After getting a clue
that .Xauthority was the likely culprit, I simply copied the new user's
.Xauthority file over the one in my home directory.

This is not necessarily the best way to do it (probably deleting the
file and running 'xauth generate :0 . trusted' is), but that's what got
me over the hump.

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

Title:
  Cannot log in users if their Xauthority file is corrupt.

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.6 series:
  Fix Released
Status in Light Display Manager 1.7 series:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “lightdm” source package in Raring:
  Fix Committed
Status in “lightdm” source package in Saucy:
  Fix Released

Bug description:
  Impact:
  If a users X authority file contains invalid data the user will not be able 
to log in with LightDM until the file is corrected or removed. The reason for 
the corruption has not been identified.

  To reproduce:
  1. Stop lightdm
  $ sudo stop lightdm
  2. Create an invalid X authority file in the home directory of a user, e.g. 
from a text VT:
  $ cp /etc/hostname ~/.Xauthority
  3. Start lightdm
  $ sudo start lightdm
  4. Log into the user account in the greeter

  Expected result:
  Logged into graphical session.

  Observed result:
  Returned to greeter, graphical session not shown.

  Regression potential:
  Change is small and was a regression in 1.6 due to accidental removal line 
resetting the error variable after reading the existing X authority file. Seems 
unlikely to cause any side-effects.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1234400/+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 1127767] Re: Lightdm service does not run with fglrx installed

** Changed in: lightdm
   Status: Incomplete => Invalid

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

Title:
  Lightdm service does not run with fglrx installed

Status in AMD fglrx video driver:
  New
Status in Light Display Manager:
  Invalid
Status in X.Org X server:
  New
Status in “xserver-xorg-video-ati” package in Ubuntu:
  New

Bug description:
  Hardware is AMD Radeon R6770 Juniper XT from vendor XFS
  Ubuntu 12.04.02 LTS

  Fglrx had been installed and working previously but X no longer starts
  on reboot after most recent update through apt-get update. Have tried
  the most recent versions in the 12.04 repos for fglrx, fglrx-updates,
  and fglrx-experimental-9 but all experience same error and X does not
  start. The previously working version 12.6 no longer functions when
  installed from amd site. Currently using radeon generic driver which
  allows system to fully boot and X to start but can only login to
  unity2d session.

  Not able to install fglrx successfully from additional drivers tool.

  When fglrx is installed and system is restarted grub loader will
  display, followed by plymouth bootsplash, and the system then hangs
  before X starts. I can login to a cli session using ctrl+alt+F1-F6.

  There are several errors that appear when fglrx is installed from the 
repositories although successful installation is reported.
  See paste.ubuntu.com/1667470

  Installation of v13.1 using amd installer fails as the installer is unable to 
build .deb package and seems to indicate installer is looking in the wrong 
place for libqtcore4 and libqtgui4. These are located in 
/arch/x86/usr/share/ati/lib. It should be noted both packages are already 
installed so perhaps this should be being detected and this step bypassed?
  See paste.ubuntu.com/1668129

  With fglrx installed from repos X fails to start
  See:
  dmesg paste.ubuntu.com/1667304
  Xorg.0.log paste.ubuntu.com/1667292
  Xorg.failsafe.log paste.ubuntu.com/1667300
  lspci -k output paste.ubuntu.com/1667360
  dpkg paste.ubuntu.com/1667346

  Output of avivotool regs all
  working: paste.ubuntu.com/1668142
  non-working: paste.ubuntu.com/1668139

  I have not been able to resolve this issue through current questions,
  bugs, or google-fu. Please advise.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-37.58-generic-pae 3.2.35
  Uname: Linux 3.2.0-37-generic-pae i686
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,move,regex,snap,imgpng,vpswitch,resize,place,gnomecompat,mousepoll,grid,wall,session,animation,expo,fade,scale,workarounds,ezoom,unityshell]
  Date: Sat Feb 16 20:51:04 2013
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx, 9.012, 3.2.0-37-generic-pae, i686: installed
   virtualbox, 4.1.12, 3.2.0-35-generic-pae, i686: installed
   virtualbox, 4.1.12, 3.2.0-37-generic, i686: installed
   virtualbox, 4.1.12, 3.2.0-37-generic-pae, i686: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes,
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last few days
  GraphicsCard:
   Advanced Micro Devices [AMD] nee ATI Juniper XT [AMD Radeon HD 6000 Series] 
[1002:68ba] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Device [1682:3150]
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  JockeyStatus:
   kmod:rt3573sta - RT2870 Wireless Lan Linux Driver (Free, Enabled, In use)
   xorg:fglrx - ATI/AMD proprietary FGLRX graphics driver (Proprietary, 
Enabled, In use)
   xorg:fglrx_experimental_9 - ATI/AMD proprietary FGLRX graphics driver 
(**experimental** beta) (Proprietary, Disabled, Not in use)
   xorg:fglrx_updates - ATI/AMD proprietary FGLRX graphics driver (post-release 
updates) (Proprietary, Disabled, Not in use)
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-37-generic-pae 
root=UUID=4d29504a-81eb-4e08-89df-7a006fcb8703 ro quiet splash nomodeset 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2204
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q SE PLUS
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.moda

[Desktop-packages] [Bug 1108311] Re: Launch two compiz processes if we have 2 X screens

Seems an unlikely case to support, but would be in the session as the
comment says, not the display manager.

** Project changed: lightdm => gnome-session (Ubuntu)

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

Title:
  Launch two compiz processes if we have 2 X screens

Status in “gnome-session” package in Ubuntu:
  New

Bug description:
  Recently, compiz dropped support for multiple X screens. I discussed
  with Sam Spilsbury about it, his answer is pasted below.

  > There is no support for Multiple X screens in compiz, this was removed in
  > 0.9 and will not be added  back because it adds further instability.
  >
  > The recommended configuration is to run one compiz instance per screen.
  > This should be done through a patch to gnome-session, or we can have a 
wrapper script
  > which will launch one instance per screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1108311/+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 1108311] [NEW] Launch two compiz processes if we have 2 X screens

You have been subscribed to a public bug:

Recently, compiz dropped support for multiple X screens. I discussed
with Sam Spilsbury about it, his answer is pasted below.

> There is no support for Multiple X screens in compiz, this was removed in
> 0.9 and will not be added  back because it adds further instability.
>
> The recommended configuration is to run one compiz instance per screen.
> This should be done through a patch to gnome-session, or we can have a 
> wrapper script
> which will launch one instance per screen.

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

-- 
Launch two compiz processes if we have 2 X screens
https://bugs.launchpad.net/bugs/1108311
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-session 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 237721] Re: Secure attention key

** Changed in: lightdm
   Status: New => Triaged

** Changed in: lightdm
   Importance: Undecided => Wishlist

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

Title:
  Secure attention key

Status in GDM: The Gnome Display Manager:
  New
Status in KDE Base Components:
  Confirmed
Status in Light Display Manager:
  Triaged
Status in “gdm” package in Ubuntu:
  Confirmed
Status in “kdebase-workspace” package in Ubuntu:
  Won't Fix
Status in “lightdm” package in Ubuntu:
  New
Status in “ubuntu-meta” package in Ubuntu:
  Invalid
Status in “xdm” package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: gdm

  In many environments computers are left unattended (e.g. schools,
  libraries, etc) and people can launch applications which mimic the
  look-and-feel of the login application (GDM) in order to get the users
  username and password.

  This is called login spoofing.
  * http://en.wikipedia.org/wiki/Login_spoofing

  Login spoofing can be prevented by using a secure attention key which is a 
key combination pressed before the user login to launch the password request 
dialog. This key can only be seen by the kernel, and not sniffed by any 
application.
  * http://en.wikipedia.org/wiki/Secure_attention_key

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/237721/+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 1035074] Re: Behavior of '~' in Spanish keyboard is wrong

2013-10-13 Thread Adolfo Jayme Barrientos

** Also affects: xkeyboard-config (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Behavior of '~' in Spanish keyboard is wrong

Status in “linux” package in Ubuntu:
  Confirmed
Status in “xkeyboard-config” package in Ubuntu:
  New

Bug description:
  On Spanish keyboards, whey you hit AltGr+4, a "~" sign is immediately 
printed. Instead, nothing should be printed until you hit the next key; if the 
next key you hit is a vowel or any latter that can have a tilde over it, then 
that character should be produced. For example, if you hit AltGr+4 and then 
"a", you should get an ã
  In order to type a plain ~ you should have to hit AltGr+4 followed by a 
space. 
  In other words the character "~" should work the same way as "`", "´" and "¨" 
and "^" do.

  I'm almost sure this was how it used to work until very recently, so I
  thing this is a regression introduced by some recent update.

  I guess the correct package is not "linux" but I have no idea which
  package it is and how to figure it out.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-29-generic 3.2.0-29.46
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  teo2293 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
 Mixer name : 'Realtek ALC660-VD'
 Components : 'HDA:10ec0660,1043,0011 
HDA:10573055,10431316,00100700'
 Controls  : 28
 Simple ctrls  : 16
  Date: Thu Aug  9 22:20:13 2012
  HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MachineType: ASUSTeK Computer Inc. M51Sn
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic 
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-29-generic N/A
   linux-backports-modules-3.2.0-29-generic  N/A
   linux-firmware1.79
  SourcePackage: linux
  StagingDrivers: zram
  UpgradeStatus: Upgraded to precise on 2012-05-17 (84 days ago)
  UserAsoundrc:
   pcm.!default { type pulse }
   ctl.!default { type pulse }
   pcm.pulse { type pulse }
   ctl.pulse { type pulse }
  dmi.bios.date: 12/24/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: M51Sn
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: M51Sn
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1035074/+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 771661] Re: Allow .xsession-errors to be a symlink

** Changed in: lightdm
   Status: New => Triaged

** Changed in: lightdm
   Importance: Undecided => Wishlist

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

Title:
  Allow .xsession-errors to be a symlink

Status in GDM: The Gnome Display Manager:
  Fix Released
Status in Light Display Manager:
  Triaged
Status in Lucid Backports:
  Fix Released
Status in “gdm” package in Ubuntu:
  Fix Released
Status in “kde-workspace” package in Ubuntu:
  Won't Fix
Status in “gdm” source package in Lucid:
  Fix Released

Bug description:
  Binary package hint: gdm

  Bug 60448 discusses the problem about ~/.xsession-errors growing
  unbearably large when there are buggy programs spamming it. One remedy
  is to allow ~/.xsession-errors to be a symlink to e. g. /dev/null or a
  local file, so that you can at least avoid network contention if ~ is
  on NFS.

  scm sent a first patch for this 
(https://launchpadlibrarian.net/70203386/gdm-session-worker.c.diff). This 
should be cleaned up to use g_file_test() and reported upstream.
   
  SRU TEST CASE:
   * Remove ~/.xsession-errors and ~/.xsession-errors.old
   * ln -s /tmp/xe ~/.xsession-errors
   * Reboot and log back in.
 -> Current behavior: the ~/.xsession-errors symlink gets rotated to 
~/.xsession-errors.old, and a new ~/.xsession-errors is created as a regular 
file.
 -> Desired behaviour: ~/.xsession-errors remains a symlink, and the target 
file /tmp/xe is truncated for the new session.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/771661/+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 986843] Re: Onboard randomly sets as default in login screen

** Project changed: lightdm => unity-greeter

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

Title:
  Onboard randomly sets as default in login screen

Status in GDM: The Gnome Display Manager:
  New
Status in Onboard on-screen keyboard:
  New
Status in Unity Greeter:
  New
Status in “onboard” package in Ubuntu:
  Fix Released

Bug description:
  The onboard randomly is set to default when unlocking the screen.
  I can't reproduce the bug. It's happens to me twice times, in different 
contexts.
  Each time I have to go to onboard settings and unclick "show onboard when 
unlokcing the screen".
  Also, in askubuntu:
  
http://askubuntu.com/questions/84050/how-do-i-disable-the-on-screen-keyboard-in-the-unlock-screen
  The user indicates that " I'm not sure how I activated these settings in the 
first place though" and I'm sure that is the same issue that happens to me.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-shell 3.2.2.1-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22
  Uname: Linux 3.0.0-17-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Sun Apr 22 14:39:46 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/986843/+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 915377] Re: Inconsistency in wording used to describe password error

** Changed in: lightdm
   Status: New => Triaged

** Changed in: lightdm
   Importance: Undecided => Low

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

Title:
  Inconsistency in wording used to describe password error

Status in The "GKSu" Gnome Frontend for "su":
  New
Status in GNOME Terminal:
  New
Status in One Hundred Paper Cuts:
  Invalid
Status in Light Display Manager:
  Triaged
Status in PolicyKit:
  New
Status in “gnome-screensaver” package in Ubuntu:
  Confirmed

Bug description:
  In a new installation of Ubuntu there are incosistencies in the text
  used to describe when a user enters their password incorrectly. The
  ones I have found are:

  Logging in from boot:
  "Invalid password, please try again"

  Unlocking your computer:
  "Incorrect password"

  PolicyKit: Authenticating an operation e.g. installing an application:
  "Your authentication attempt was unsuccessful. Please try again."

  sudo: Putting in a password in the terminal:
  "Sorry, try again."

  Entering a password on tty1-6
  "Login incorrect"

  It could be argued that the text used for logging in should be
  different to the other tasks, but even then there are inconsistencies

To manage notifications about this bug go to:
https://bugs.launchpad.net/gksu/+bug/915377/+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 1024482] Re: Mouse cursor theme does not change from default after login

** Project changed: lightdm => unity-greeter

** No longer affects: lightdm (Ubuntu)

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

Title:
  Mouse cursor theme does not change from default after login

Status in Unity Greeter:
  Confirmed
Status in “lightdm” package in Debian:
  Confirmed

Bug description:
  When using LightDM to login to a GNOME Shell session, the mouse
  cursor's appearance does not change from what it is in the lightdm
  login screen (black pointer from default X theme). Any custom mouse
  cursor theme actually does apply within any open application windows,
  but hovering the cursor over the window title bar, the root window, or
  the Shell interface changes it back to the default black pointer,
  leading to an inconsistent appearance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-greeter/+bug/1024482/+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 1239431] Re: doing an "aptitude upgrade" on a new installation of xubuntu 13.10

2013-10-13 Thread Thaddäus Tintenfisch

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

** This bug has been marked a duplicate of bug 1161283
   Problems reported with .desktop files for sonic-visualiser

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

Title:
  doing an "aptitude upgrade" on a new installation of xubuntu 13.10

Status in “software-center” package in Ubuntu:
  New

Bug description:
  This resulted:
  INFO:softwarecenter.db.pkginfo_impl.aptcache:aptcache.open()
  WARNING:softwarecenter.db.update:The file: 
'/usr/share/app-install/desktop/sonic-visualiser:x-sonicvisualiser-layer.desktop'
 could not be read correctly. The application associated with this file will 
not be included in the software catalog. Please consider raising a bug report 
for this issue with the maintainer of that application

  WARNING:softwarecenter.db.update:The file: '/usr/share/app-
  install/desktop/sonic-visualiser:x-sonicvisualiser.desktop' could not
  be read correctly. The application associated with this file will not
  be included in the software catalog. Please consider raising a bug
  report for this issue with the maintainer of that application

  (The repeat was verbatin)
   After this message the message "Software catalog update was successful." 
appeared.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: software-center 13.10-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: fglrx wl
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Sun Oct 13 20:31:37 2013
  InstallationDate: Installed on 2013-10-11 (2 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: software-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1239431/+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 1239413] Re: rhythmbox: Should refer to 'tracks' not 'songs'. Not all audio is a song.

2013-10-13 Thread Adolfo Jayme Barrientos

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

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

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

Title:
  rhythmbox: Should refer to 'tracks' not 'songs'. Not all audio is a
  song.

Status in “rhythmbox” package in Ubuntu:
  Confirmed

Bug description:
  rhythmbox: Should refer to 'tracks' not 'songs'. Not all audio is
  songs.

  As an example. See attached screenshot of rhythmbox status bar.

  This may sound picky, but it is something to be discussed as a
  wishlist item.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: rhythmbox 2.99.1-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
  Architecture: amd64
  Date: Sun Oct 13 19:48:26 2013
  InstallationDate: Installed on 2013-09-12 (31 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  SourcePackage: rhythmbox
  UpgradeStatus: Upgraded to saucy on 2013-09-12 (31 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1239413/+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 995111] Re: Print failure since upgrade to 12.04

2013-10-13 Thread Edmund Laugasson

Any solution? I use 64-bit Ubuntu 12.04 LTS wit all updates and tried also 
http://unquietwiki.blogspot.com/2012/05/fixing-pdf-printing-problems-on-ubuntu.html
 but this did not work either. Even test page gave error when I tried these 
suggestions.
Adding ppa:till-kamppeter/ppa does not upgrade anything - is this intentional? 
I see that cups in that repository is older than in current Ubuntu 12.04. 
Actually the problem is cups-pdf - does this PPA fix also cups-pdf issue? 
Nothing will come into $HOME/PDF when trying to print...

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

Title:
  Print failure since upgrade to 12.04

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups” source package in Precise:
  Triaged

Bug description:
  Since upgrade to 12.04 LTS have had difficulty printing which persists even 
after re-installing Oneiric.  I do not think this is a printer malfunction as 
netbook  running Ubuntu 10.04 cups 1.4.3-1ubuntu1.5 prints just fine. Often 
occurring with second jobs when the first page appears with a single line of 
characters at the top and then the printer churns out repeated blank pages 
until stopped by hitting the printer "stop" button. Currently having the 
problem with Ubuntu 11.10 with cups 1.5.0-8 and Ubuntu 12.04 with cups 
1.5.2-9ubuntu1.  Cups Error log does not report an error.  The line of 
characters is not always identical but often similar.  The clearest is
  ERROR:
  undefined
  OFFENDING COMMAND:
  5rCj3Lri1"+f$rI5+n6R8\*imVK6JF'6bb
  STACK:

  More usually
  5rCj3Lri1"+f$rI5+n6R8\*imVK6JF'6bb
   
K6LhR1->%^S_n48hjF.$II@,f_rC4^-LP1_'P3RLc;\M

  Have tried using different driver from bchemnet and in Ubuntu 12.04
  installing cups 1.5.0 from archive but these either have not helped or
  have proved beyond my ability.  I think I need some help

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/995111/+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 1239392] Re: Lenovo IdeaPad Yoga 13: Inverted Internal microphone (phase inversion)

2013-10-13 Thread Ubuntu Foundations Team Bug Bot

The attachment "inverted-mic-lenovo-yoga-13.diff" seems to be a patch.
If it isn't, please remove the "patch" flag from the attachment, remove
the "patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

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

** Tags added: patch

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

Title:
  Lenovo IdeaPad Yoga 13: Inverted Internal microphone (phase inversion)

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  As per this meta-bug:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978

  Reporting for Lenovo IdeaPad Yoga 13. Inverted channel is visible when
  recording stereo in audacity. Mono recording via pulseaudio gives
  silence with occasional cracks somewhat corresponding to the sound
  level around. Skype and pavucontrol level gauges are also affected.

  Changes in balance in pavucontrol do not help with mono recording, I
  don't know why.

  I'm attaching two patches against oem-audio-hda-daily-
  dkms-0.201310111402~ubuntu13.10.1 (https://launchpad.net/~ubuntu-
  audio-dev/+archive/alsa-daily); either of them fixes the problem for
  me (the -alt one may affect other hardware, though). No additional
  steps were needed after applying a patch, building and installing the
  package.

  Output of alsa-info.sh is also attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1239392/+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 994745] Re: [HP Folio 13-1050ca Notebook PC] Power indicator fails to recognise unplug

2013-10-13 Thread Bug Watch Updater

** Changed in: upower
   Status: Confirmed => Won't Fix

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

Title:
  [HP Folio 13-1050ca Notebook PC] Power indicator fails to recognise
  unplug

Status in The Linux Kernel:
  Fix Released
Status in Upower:
  Won't Fix
Status in “linux” package in Ubuntu:
  Invalid
Status in “upower” package in Ubuntu:
  Invalid
Status in “linux” package in Debian:
  Fix Released

Bug description:
  Upon unplugging the power on HP Folio 13 running Precise the power indicator 
fails to recognise the unplug. 
  The charging laptop symbol remains. Power-statistics also becomes 
unresponsive/empty of data.

  Powertop recognises the unplug, but Jupiter which I have installed
  does not.

  If I suspend and resume or restart, the fact that I am on battery
  power is once again recognised.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: indicator-power 2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Fri May  4 11:00:11 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-power
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/994745/+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 1234968] Re: package libreoffice-common (not installed) failed to install/upgrade: intentando sobreescribir `/usr/bin/soffice', que está también en el paquete openoffice-debian

2013-10-13 Thread Björn Michaelsen

You seem to have installed the unsupported Apache OpenOffice. Dont do that 
unless you are aware of how to remove these unsupported software.
Support request => Turned into a question.

** Changed in: libreoffice (Ubuntu)
   Status: Confirmed => Invalid

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/libreoffice/+question/237294

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

Title:
  package libreoffice-common (not installed) failed to install/upgrade:
  intentando sobreescribir `/usr/bin/soffice', que está también en el
  paquete openoffice-debian-menus 4.0-9702

Status in “libreoffice” package in Ubuntu:
  Invalid

Bug description:
  I can't make the sudo app-get -f install, the above error is present,
  the correct for that is what?

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: libreoffice-common (not installed)
  ProcVersionSignature: Ubuntu 3.5.0-40.62~precise1-generic 3.5.7.20
  Uname: Linux 3.5.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: amd64
  Date: Thu Oct  3 16:21:34 2013
  DpkgHistoryLog:
   Start-Date: 2013-10-03  16:21:26
   Commandline: apt-get -f install
   Install: libreoffice-common:amd64 (3.5.7-0ubuntu4, automatic)
  DpkgTerminalLog:
   Desempaquetando libreoffice-common (de 
.../libreoffice-common_1%3a3.5.7-0ubuntu4_all.deb) ...
   dpkg: error al procesar 
/var/cache/apt/archives/libreoffice-common_1%3a3.5.7-0ubuntu4_all.deb 
(--unpack):
intentando sobreescribir `/usr/bin/soffice', que está también en el paquete 
openoffice-debian-menus 4.0-9702
  DuplicateSignature: package:libreoffice-common:(not installed):intentando 
sobreescribir `/usr/bin/soffice', que está también en el paquete 
openoffice-debian-menus 4.0-9702
  ErrorMessage: intentando sobreescribir `/usr/bin/soffice', que está también 
en el paquete openoffice-debian-menus 4.0-9702
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  MarkForUpload: True
  SourcePackage: libreoffice
  Title: package libreoffice-common (not installed) failed to install/upgrade: 
intentando sobreescribir `/usr/bin/soffice', que está también en el paquete 
openoffice-debian-menus 4.0-9702
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1234968/+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 994745]

2013-10-13 Thread Bugzilla-x

Looks like the kernel bug got fixed, so closing this report.

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

Title:
  [HP Folio 13-1050ca Notebook PC] Power indicator fails to recognise
  unplug

Status in The Linux Kernel:
  Fix Released
Status in Upower:
  Won't Fix
Status in “linux” package in Ubuntu:
  Invalid
Status in “upower” package in Ubuntu:
  Invalid
Status in “linux” package in Debian:
  Fix Released

Bug description:
  Upon unplugging the power on HP Folio 13 running Precise the power indicator 
fails to recognise the unplug. 
  The charging laptop symbol remains. Power-statistics also becomes 
unresponsive/empty of data.

  Powertop recognises the unplug, but Jupiter which I have installed
  does not.

  If I suspend and resume or restart, the fact that I am on battery
  power is once again recognised.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: indicator-power 2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Fri May  4 11:00:11 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-power
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/994745/+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 1239186] Re: External screens shut off randomly

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

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: New => Confirmed

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

Title:
  External screens shut off randomly

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

Bug description:
  I've been trying to figure out what's going on with my external
  display port screens with no luckbut I think I'm getting closer to
  the right direction.

  I upgraded to the latest 13.10 build and turned on DRM debugging with:

  # /etc/modprobe.d/drm.conf
  # We are turning on debug information here

  options drm debug=0xe

  In doing so my logs lit up with lots of graphics activity. However the
  two events that actually had some meaning in terms of a pain point
  where lines like this:

  Oct 12 11:22:02 rnavarro-thinkpad kernel: [  673.201706] 
[drm:ironlake_irq_handler], Pipe B FIFO underrun
  Oct 12 11:22:02 rnavarro-thinkpad kernel: [  673.201719] 
[drm:cpt_serr_int_handler], PCH transcoder B FIFO underrun

  and

  Oct 12 11:22:31 rnavarro-thinkpad kernel: [  702.411812]
  [drm:ironlake_irq_handler], Pipe A FIFO underrun

  I noticed that right before either one of my monitors would blank and
  shut off, this message would be emitted in my kern.log

  I think there was some stuff added upstream to detect this, as noted
  here:

  http://lists.freedesktop.org/archives/intel-gfx/2013-July/029882.html

  But i'm not sure what's causing it, much less how to fix it.

  What other information can I give that would help debug?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  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
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,regex,mousepoll,imgpng,vpswitch,grid,wall,gnomecompat,animation,compiztoolbox,move,place,snap,resize,unitymtgrabhandles,workarounds,fade,expo,session,scale,ezoom,unityshell]
  CompositorRunning: None
  Date: Sat Oct 12 11:45:47 2013
  DistUpgraded: 2013-10-12 10:47:24,030 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   i915-3.9-3.8, 0.02, 3.8.0-31-generic, x86_64: installed
   vboxhost, 4.2.18, 3.11.0-12-generic, x86_64: installed
   vboxhost, 4.2.18, 3.8.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2013-06-30 (103 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MachineType: LENOVO 4286CTO
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic 
root=/dev/mapper/vg_rnavarro--leno-lv_root ro quiet splash i915.semaphores=0 
vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to saucy on 2013-10-12 (0 days ago)
  XorgConf:
   Section "Device"
   Identifier "intel"
   Driver "intel"
   Option "AccelMethod" "sna"
   EndSection
  dmi.bios.date: 02/14/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET58WW (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4286CTO
  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:bvr8DET58WW(1.28):bd02/14/2012:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4286CTO
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 
9.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Sat Oct 12 11:20:57 2013
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16510 
   vendor DEL
  xserver.version: 2:1.14.3-3ubuntu

[Desktop-packages] [Bug 1232299] Re: gnome-session-flashback with Compiz launches Unity

2013-10-13 Thread Fred

I am running Ubuntu 13.10 and it does not work fine.
I tried your suggested solution and it did not work.

Compiz does not gets loaded, and I have to open a terminal and type;
compiz --replace
To get it to work:

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

Title:
  gnome-session-flashback with Compiz launches Unity

Status in “compiz” package in Ubuntu:
  Confirmed
Status in “gnome-panel” package in Ubuntu:
  New

Bug description:
  gnome-session-flashback (Flashback (No Effects)) which runs with Metacity 
works fine.
  gnome-session-flashback (Flashback) which runs with Compiz starts Unity 
instead.

  It works very well with Metacity, but if you use Compiz, then you get
  a conflict with Unity. That is; you get both Unity and Gnome Panel
  running at the same time.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-session-flashback 1:3.6.2-0ubuntu15
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Sat Sep 28 01:18:08 2013
  GsettingsChanges: b'org.gnome.gnome-panel.run-dialog' b'history' b"['compiz', 
'ubuntu-bug fontconfig', 'update-manager -c -d']"
  InstallationDate: Installed on 2011-10-21 (707 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: gnome-panel
  UpgradeStatus: Upgraded to saucy on 2013-09-16 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1232299/+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 1067414] Re: gdm crashes if a user account is deleted or added (nslcd, ldap)

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

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

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

Title:
  gdm crashes if a user account is deleted or added (nslcd,ldap)

Status in “accountsservice” package in Ubuntu:
  Confirmed
Status in “gdm” package in Ubuntu:
  Confirmed

Bug description:
  Scenario:

  * LDAP User Account (NFS Home Directory)
  * nslcd and gdm are used
  * user account information is manipulated, e.g. apt-get remove --purge 
tomcat7*

  Result:
  gdm session crashed

  Syslog:
  Oct 16 17:48:29 dilbert kernel: [24735.236935] gdm-session-wor[4316] general 
protection ip:7f28a91545a1 sp:7fff6dc110d0 error:0 in l

  This can be reproduced on 2 different machines and user accounts

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gdm 3.0.4-0ubuntu15
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
  Uname: Linux 3.2.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu14
  Architecture: amd64
  Date: Tue Oct 16 18:00:05 2012
  SourcePackage: gdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm.Xsession: 2012-06-25T12:57:29.554078

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1067414/+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 1239287] Vacation reply

2013-10-13 Thread mikael hammarlind

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

Title:
  Multimedia or layout changing keys doesn't work  after killing gnome-
  screensaver

Status in “gnome-screensaver” package in Ubuntu:
  Confirmed

Bug description:
  After killing gnome-screensaver multimedia and layout changing keys doesn't 
work. To reproduce this bug you need kill gnome-screensaver
  killall -9 gnome-screensaver

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-screensaver 3.6.1-0ubuntu6
  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
  Architecture: amd64
  Date: Sun Oct 13 11:30:16 2013
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 300
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationDate: Installed on 2013-10-09 (3 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131009)
  MarkForUpload: True
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1239287/+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 1067414] Re: gdm crashes if a user account is deleted or added (nslcd, ldap)

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

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

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

Title:
  gdm crashes if a user account is deleted or added (nslcd,ldap)

Status in “accountsservice” package in Ubuntu:
  Confirmed
Status in “gdm” package in Ubuntu:
  Confirmed

Bug description:
  Scenario:

  * LDAP User Account (NFS Home Directory)
  * nslcd and gdm are used
  * user account information is manipulated, e.g. apt-get remove --purge 
tomcat7*

  Result:
  gdm session crashed

  Syslog:
  Oct 16 17:48:29 dilbert kernel: [24735.236935] gdm-session-wor[4316] general 
protection ip:7f28a91545a1 sp:7fff6dc110d0 error:0 in l

  This can be reproduced on 2 different machines and user accounts

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gdm 3.0.4-0ubuntu15
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
  Uname: Linux 3.2.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu14
  Architecture: amd64
  Date: Tue Oct 16 18:00:05 2012
  SourcePackage: gdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm.Xsession: 2012-06-25T12:57:29.554078

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1067414/+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 1239287] Re: Multimedia or layout changing keys doesn't work after killing gnome-screensaver

2013-10-13 Thread Haron Prime

Confirm
Ubuntu 13.10 x86_64 
3.11.0-12-generic

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

Title:
  Multimedia or layout changing keys doesn't work  after killing gnome-
  screensaver

Status in “gnome-screensaver” package in Ubuntu:
  Confirmed

Bug description:
  After killing gnome-screensaver multimedia and layout changing keys doesn't 
work. To reproduce this bug you need kill gnome-screensaver
  killall -9 gnome-screensaver

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-screensaver 3.6.1-0ubuntu6
  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
  Architecture: amd64
  Date: Sun Oct 13 11:30:16 2013
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 300
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationDate: Installed on 2013-10-09 (3 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131009)
  MarkForUpload: True
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Desktop-packages] [Bug 1239019] Re: Jockey is failing to list any nvidia drivers

2013-10-13 Thread Vadim Peretokin

No... I only have one video card, always did, and I assembled the computer
myself.

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

Title:
  Jockey is failing to list any nvidia drivers

Status in “jockey” package in Ubuntu:
  Invalid

Bug description:
  Suddenly, both jockey-gtk and jockey-text are failing to recommend me
  any nvidia drivers!

  This makes maintaining drivers in a Ubuntu-friendly way difficult.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: jockey-common 0.9.7-0ubuntu7.11
  ProcVersionSignature: Ubuntu 3.2.0-54.82-generic 3.2.50
  Uname: Linux 3.2.0-54-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.5
  Architecture: amd64
  CheckboxSubmission: f14e403bdb8f84f871603c9cde62a6ec
  CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2
  Date: Sat Oct 12 10:43:55 2013
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: Gigabyte Technology Co., Ltd. Z68AP-D3
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-54-generic 
root=UUID=20aa0109-67bb-46a0-95c6-626f0f0487eb ro quiet splash
  SourcePackage: jockey
  UpgradeStatus: Upgraded to precise on 2012-04-26 (533 days ago)
  dmi.bios.date: 10/12/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FB
  dmi.board.name: Z68AP-D3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/12/2011:svnGigabyteTechnologyCo.,Ltd.:pnZ68AP-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68AP-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: Z68AP-D3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1239019/+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 1239287] Re: Multimedia or layout changing keys doesn't work after killing gnome-screensaver

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

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

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

Title:
  Multimedia or layout changing keys doesn't work  after killing gnome-
  screensaver

Status in “gnome-screensaver” package in Ubuntu:
  Confirmed

Bug description:
  After killing gnome-screensaver multimedia and layout changing keys doesn't 
work. To reproduce this bug you need kill gnome-screensaver
  killall -9 gnome-screensaver

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-screensaver 3.6.1-0ubuntu6
  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
  Architecture: amd64
  Date: Sun Oct 13 11:30:16 2013
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 300
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationDate: Installed on 2013-10-09 (3 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131009)
  MarkForUpload: True
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1239287/+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 1222718] Re: Tabs not displaying titles

2013-10-13 Thread Paul Sarraffe

This appears related to
https://code.google.com/p/chromium/issues/detail?id=123104 which was
first reported in April 2012. I did not see this problem with Xubuntu
13.04 64-bit, but I do see it in Xubuntu 13.10 64-bit.  Perhaps this is
the reason that Firefox is still the default web browser for Ubuntu
13.10.

** Bug watch added: code.google.com/p/chromium/issues #123104
   http://code.google.com/p/chromium/issues/detail?id=123104

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

Title:
  Tabs not displaying titles

Status in “chromium-browser” package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  My problem is that Chrome/Chromium (have both installed) are not displaying 
page titles rendering many pages.
  Actually, because of bug of keybindings in Gnome 3.9 I can't create 
screenshot, but with most pages I have favicon displayed and not any text like 
page title.

  It doesn't matter if GPU rendering is enabled or disabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1222718/+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 1239405] Re: Cannot access internet via Huawei E352 modem.

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

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

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

Title:
  Cannot access internet via Huawei E352 modem.

Status in “modemmanager” package in Ubuntu:
  Confirmed

Bug description:
  Settings in the "/etc/NetworkManager/system-connections/Megafon RUS"
  file:

  [connection]
  id=Megafon RUS
  uuid=d8a3a742-fadb-4abd-81bb-8258c9855975
  type=gsm
  autoconnect=false

  [gsm]
  number=*99#
  username=gdata
  password=gdata
  apn=internet

  [ppp]
  lcp-echo-failure=5
  lcp-echo-interval=30

  [serial]
  baud=115200

  [ipv4]
  method=auto



  Summary:
  After configuring this modem and trying to connect to the internet always 
happens disconnect, and i don't know why, when and where)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1239405/+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 1222718] Re: Tabs not displaying titles

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

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

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

Title:
  Tabs not displaying titles

Status in “chromium-browser” package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  My problem is that Chrome/Chromium (have both installed) are not displaying 
page titles rendering many pages.
  Actually, because of bug of keybindings in Gnome 3.9 I can't create 
screenshot, but with most pages I have favicon displayed and not any text like 
page title.

  It doesn't matter if GPU rendering is enabled or disabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1222718/+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 1239422] [NEW] 'Show Desktop' icon in Unity Launcher unresponsive

2013-10-13 Thread oda_krell

Public bug reported:

My apologies if I am not filing this bug properly, for example, I'm not
sure if a bug related to the Unity Launcher belongs to x.org or not.

I selected "Add show desktop icon to the launcher" under Settings ->
Appearance. The icon appears in the launcher, and usually works as
intended, but sometimes it doesn't react on the first left click, but
only after a second click. A pretty minor bug, but I thought I should
report it.

I think I know how to reproduce the effect:

1) starting point: desktop *without* any program in fullscreen view

2) open a program via unity launcher, e.g. firefox, already running in
fullscreen view (i.e. when opened, it will be immediately in fullscreen
view)

3)  if the next launcher icon that is pressed is the 'show desktop'
icon, no reaction (the bug). second click on same icon: desktop shown,
as intended.

Let me know if this helps/is of interest.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: xorg 1:7.7+1ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
Uname: Linux 3.8.0-31-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.9.2-0ubuntu8.3
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: Sun Oct 13 20:55:49 2013
DistUpgraded: Fresh install
DistroCodename: raring
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices [AMD] nee ATI RV710/M92 [Mobility Radeon HD 
4530/4570/545v] [1002:9553] (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:2129]
InstallationDate: Installed on 2013-10-12 (0 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic 
root=UUID=c9edd2cb-5c62-4549-8d9c-4c49146c67b4 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/11/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 6JET90WW (1.48 )
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:bvr6JET90WW(1.48):bd08/11/2011:svnLENOVO:pn:pvrThinkPadSL510:rvnLENOVO:rn:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.version: ThinkPad SL510
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.43-0ubuntu1.1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1
xserver.bootTime: Sun Oct 13 19:29:10 2013
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.13.3-0ubuntu6
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 raring 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/1239422

Title:
  'Show Desktop' icon in Unity Launcher unresponsive

Status in “xorg” package in Ubuntu:
  New

Bug description:
  My apologies if I am not filing this bug properly, for example, I'm
  not sure if a bug related to the Unity Launcher belongs to x.org or
  not.

  I selected "Add show desktop icon to the launcher" under Settings ->
  Appearance. The icon appears in the launcher, and usually works as
  intended, but sometimes it doesn't react on the first left click, but
  only after a second click. A pretty minor bug, but I thought I should
  report it.

  I think I know how to reproduce the effect:

  1) starting point: desktop *without* any program in fullscreen view

  2) open a program via unity launcher, e.g. firefox, already running in
  fullscreen view (i.e. when opened, it will be immediately in
  fullscreen view)

  3)  if the next launcher icon that is pressed is the 'show desktop'
  icon, no reaction (the bug). second click on same icon: desktop shown,
  as intended.

  Let me know if this helps/is of interest.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  Uname: Linux 3.8.0-31-generic x86_64
  .tmp.unity.support.test.0:
   
  Apport

[Desktop-packages] [Bug 1239406] Re: cache folder belongs to root, causing firefox to fail to run

2013-10-13 Thread Chris Coulson

This is absolutely nothing to do with Firefox. The only way that can
happen is by running Firefox with sudo, which is completely unsupported

** Package changed: firefox (Ubuntu) => ubuntu

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

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

Title:
  cache folder belongs to root, causing firefox to fail to run

Status in Ubuntu:
  Invalid

Bug description:
  On a freshly installed Ubuntu 13.04 64bit on a brand new computer, I had 
Firefox 20 running fine.
  Then I updated it via sudo apt-get install firefox, which updated it to 24.

  After that, any attempt to run Firefox would fail with the error popup (more 
or less) "Your profile cannot be loaded. It may be missing or inaccessible".
  If run from a command line, it would show this error: "Error reading profile 
directory: access denied", or something like that.

  After a whole day of googling and forum posting and useless attempt to
  sort it out, I found out that the issue was that ~/.cache/mozilla had
  "root" as the owner and group. Deleting that folder fixed the issue (a
  new one was created which now correctly belongs to my user).

  Needless to say, I didn't do anything that would legitimate the wrong
  owner of the ~/.cache/mozilla folder. I never touched it, so if it got
  the wrong owner there's a bug somewhere.

  Please do not underestimate the importance of this bug, which renders firefox 
unusable, and whose workaround, though extremely easy, is very hard to figure 
out.
  Also, I bet most user who face this will almost surely delete their profile 
(as I did) in a useless attempt to fix it, because that's the most common 
answer to profile loading problems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1239406/+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 1239413] [NEW] rhythmbox: Should refer to 'tracks' not 'songs'. Not all audio is a song.

Public bug reported:

rhythmbox: Should refer to 'tracks' not 'songs'. Not all audio is songs.

As an example. See attached screenshot of rhythmbox status bar.

This may sound picky, but it is something to be discussed as a wishlist
item.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: rhythmbox 2.99.1-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
Architecture: amd64
Date: Sun Oct 13 19:48:26 2013
InstallationDate: Installed on 2013-09-12 (31 days ago)
InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
MarkForUpload: True
SourcePackage: rhythmbox
UpgradeStatus: Upgraded to saucy on 2013-09-12 (31 days ago)

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


** Tags: amd64 apport-bug gnome3 saucy

** Attachment added: "rhythmbox status bar"
   
https://bugs.launchpad.net/bugs/1239413/+attachment/3876918/+files/Screenshot%20from%202013-10-13%2019%3A45%3A54.png

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

Title:
  rhythmbox: Should refer to 'tracks' not 'songs'. Not all audio is a
  song.

Status in “rhythmbox” package in Ubuntu:
  New

Bug description:
  rhythmbox: Should refer to 'tracks' not 'songs'. Not all audio is
  songs.

  As an example. See attached screenshot of rhythmbox status bar.

  This may sound picky, but it is something to be discussed as a
  wishlist item.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: rhythmbox 2.99.1-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
  Architecture: amd64
  Date: Sun Oct 13 19:48:26 2013
  InstallationDate: Installed on 2013-09-12 (31 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  SourcePackage: rhythmbox
  UpgradeStatus: Upgraded to saucy on 2013-09-12 (31 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1239413/+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 1239204] Re: keys get stuck often on a bluetooth keyboard

2013-10-13 Thread Artyom Kazak

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

** Description changed:

  I have a Logitech K810 Bluetooth keyboard. The trouble is as follows:
  every now and then a pressed key causes Ubuntu to think that the key is
  being held; for instance, when I try to type “google”, I may get
  something like “oogee”. It happens to any
  key including arrows and Backspace; sometimes multiple times over typing
  a single word, sometimes I can type for five or ten minutes without
  experiencing the bug.
  
  The laptop’s original keyboard is unaffected.
  
  It is not a hardware bug, as a) the keyboard works fine when connected
  to an iPad, and b) the keyboard worked fine on 13.04.
  
  The bug isn’t limited to any particular program and is also present
  while typing in terminal (the Ctrl-F1 one) or at login.
  
+ The bug disappears when I load Ubuntu with old (3.8) kernel from 13.04.
+ 
+ ---
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic i686
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,grid,resize,vpswitch,imgpng,unitymtgrabhandles,regex,move,gnomecompat,place,snap,animation,expo,mousepoll,workarounds,wall,fade,session,ezoom,scale,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Oct 13 00:25:35 2013
  DistUpgraded: 2013-10-02 05:31:23,728 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a001] (rev 02) (prog-if 00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. Device [1043:8446]
-Subsystem: ASUSTeK Computer Inc. Device [1043:8446]
-  NVIDIA Corporation GT218 [ION 2] [10de:0a76] (rev ff) (prog-if ff)
+  Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a001] (rev 02) (prog-if 00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. Device [1043:8446]
+    Subsystem: ASUSTeK Computer Inc. Device [1043:8446]
+  NVIDIA Corporation GT218 [ION 2] [10de:0a76] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2012-08-01 (437 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  MachineType: ASUSTeK Computer INC. 1215N
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-11-generic 
root=UUID=74d20978-496e-40a4-9cc5-d22d57c062b5 ro quiet splash acpi_osi= 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to saucy on 2013-10-02 (10 days ago)
  dmi.bios.date: 07/14/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0203
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1215N
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0203:bd07/14/2010:svnASUSTeKComputerINC.:pn1215N:pvrx.x:rvnASUSTeKComputerINC.:rn1215N:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1215N
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.
  version.compiz: compiz 1:0.9.10+13.10.20130927.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Oct 12 02:55:07 2013
  xserver.configfile: default
  xserver.errors:
-  Failed to load module "modesetting" (module does not exist, 0)
-  Failed to load module "modesetting" (module does not exist, 0)
+  Failed to load module "modesetting" (module does not exist, 0)
+  Failed to load module "modesetting" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id1206 
-  vendor HSD
+  product id1206
+  vendor HSD
  xserver.version: 2:1.14.3-3ubuntu1

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

Title:
  keys get stuck

[Desktop-packages] [Bug 1067414] Re: gdm crashes if a user account is deleted or added (nslcd, ldap)

2013-10-13 Thread patrizio

** This bug is no longer a duplicate of bug 1004515
   segfault in accounts-daemon when logging in / gdm crash if user account is 
added or deleted

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

Title:
  gdm crashes if a user account is deleted or added (nslcd,ldap)

Status in “accountsservice” package in Ubuntu:
  New
Status in “gdm” package in Ubuntu:
  New

Bug description:
  Scenario:

  * LDAP User Account (NFS Home Directory)
  * nslcd and gdm are used
  * user account information is manipulated, e.g. apt-get remove --purge 
tomcat7*

  Result:
  gdm session crashed

  Syslog:
  Oct 16 17:48:29 dilbert kernel: [24735.236935] gdm-session-wor[4316] general 
protection ip:7f28a91545a1 sp:7fff6dc110d0 error:0 in l

  This can be reproduced on 2 different machines and user accounts

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gdm 3.0.4-0ubuntu15
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
  Uname: Linux 3.2.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu14
  Architecture: amd64
  Date: Tue Oct 16 18:00:05 2012
  SourcePackage: gdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm.Xsession: 2012-06-25T12:57:29.554078

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1067414/+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 1239198] Re: Several extensions doesn't work with Chromium

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

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

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

Title:
  Several extensions doesn't work with Chromium

Status in “chromium-browser” package in Ubuntu:
  Confirmed

Bug description:
  I recently discovered that TamperMonkey extension doesn't work with Chromium 
29.0.1547.65-0ubuntu2 from an Ubuntu repository, however it works perfectly 
with Chrome 30.0.1599.66-1 from Google stable repository.
  A bug occurs with both my usual profile and a fresh one (created via 
"chromium-browser --temp-profile").
  Another extensions which doesn't work is VkOpt. Native UserScripts are not 
working too. Both VkOpt, UserScripts and TamperMonkey are modifying a content 
of a page. Other extensions works fine.
  I have used this extensions for ages and they certainly work with Chromium.
  To check this bug, please follow this steps:
  1) Install TamperMonkey from a Google extensions store.
  2) Install any extension from http://userscripts.org/
  3) Check if pages are (not) being modified.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: chromium-browser 29.0.1547.65-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Sat Oct 12 22:28:27 2013
  Desktop-Session:
   DESKTOP_SESSION = kde-plasma
   XDG_CONFIG_DIRS = /etc/xdg/xdg-kde-plasma:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share:/usr/share/kde-plasma:/usr/local/share/:/usr/share/
  DetectedPlugins:
   => Chromoting Viewer
  - enabled = True
  - path= internal-remoting-viewer
   => Chromoting Viewer
  - enabled = True
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2013-09-27 (15 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  MarkForUpload: True
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1239198/+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 1216840] Re: webdavs files not acccessible to POSIX apps

2013-10-13 Thread Stephen Parry

A proposed patch is now available upstream on the gnome bug report.
Could we try this patch please?

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

Title:
  webdavs files not acccessible to POSIX apps

Status in GVFS:
  New
Status in “gvfs” package in Ubuntu:
  Triaged

Bug description:
  Mounting webdavs share via GVFS (in my case using gigolo), remote file system 
should be accessible via gvfs-fuse at /run/user//gvfs/. Instead just 
get input/output errors when listing and reading files.
  Steps to reproduce:
  Use gigolo to connect to remote DAVS file storage using Actions -> Connect, 
Actions-> Open
  Check connectivity via gvfs:

  gvfs-ls davs://remoteu...@www.somesite.com/somepath
  gvfs-cat davs://remoteu...@www.somesite.com/somepath/somefile.txt

  In my case, these work fine. Now try:

  ls -l 
/run/user/localuser/gvfs/dav\:host\=www.somesite.com\,ssl\=true\,user\=remoteuser/somepath
  cat 
/run/user/localuser/gvfs/dav\:host\=www.somesite.com\,ssl\=true\,user\=remoteuser/somepath/somefile.txt

  Get these errors:

  ls: cannot access 
/run/user/parrysg/gvfs/dav:host=www.mainscreen.com,ssl=true,user=parry2sg/files/test.txt:
 Input/output error
  :
  :
  cat: 
/run/user/parrysg/gvfs/dav:host=www.mainscreen.com,ssl=true,user=parry2sg/files/test.txt:
 Input/output error

  This affects 13.04 but works fine under 12.04

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gvfs-fuse 1.16.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-27.19-lowlatency 3.8.13.4
  Uname: Linux 3.8.0-27-lowlatency i686
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: i386
  Date: Mon Aug 26 10:41:58 2013
  InstallationDate: Installed on 2012-07-05 (416 days ago)
  InstallationMedia: Ubuntu-Studio 12.04 "Precise Pangolin" - Release i386 
(20120423)
  MarkForUpload: True
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to raring on 2013-05-11 (107 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1216840/+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 1239405] Re: Cannot access internet via Huawei E352 modem.

2013-10-13 Thread Full inu

I captured error log with command "tail -n0 -f /var/log/syslog >
/tmp/syslog"

** Attachment added: "/tmp/syslog captured"
   
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1239405/+attachment/3876882/+files/tmp_syslog

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

Title:
  Cannot access internet via Huawei E352 modem.

Status in “modemmanager” package in Ubuntu:
  New

Bug description:
  Settings in the "/etc/NetworkManager/system-connections/Megafon RUS"
  file:

  [connection]
  id=Megafon RUS
  uuid=d8a3a742-fadb-4abd-81bb-8258c9855975
  type=gsm
  autoconnect=false

  [gsm]
  number=*99#
  username=gdata
  password=gdata
  apn=internet

  [ppp]
  lcp-echo-failure=5
  lcp-echo-interval=30

  [serial]
  baud=115200

  [ipv4]
  method=auto



  Summary:
  After configuring this modem and trying to connect to the internet always 
happens disconnect, and i don't know why, when and where)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1239405/+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 1239406] [NEW] cache folder belongs to root, causing firefox to fail to run

Public bug reported:

On a freshly installed Ubuntu 13.04 64bit on a brand new computer, I had 
Firefox 20 running fine.
Then I updated it via sudo apt-get install firefox, which updated it to 24.

After that, any attempt to run Firefox would fail with the error popup (more or 
less) "Your profile cannot be loaded. It may be missing or inaccessible".
If run from a command line, it would show this error: "Error reading profile 
directory: access denied", or something like that.

After a whole day of googling and forum posting and useless attempt to
sort it out, I found out that the issue was that ~/.cache/mozilla had
"root" as the owner and group. Deleting that folder fixed the issue (a
new one was created which now correctly belongs to my user).

Needless to say, I didn't do anything that would legitimate the wrong
owner of the ~/.cache/mozilla folder. I never touched it, so if it got
the wrong owner there's a bug somewhere.

Please do not underestimate the importance of this bug, which renders firefox 
unusable, and whose workaround, though extremely easy, is very hard to figure 
out.
Also, I bet most user who face this will almost surely delete their profile (as 
I did) in a useless attempt to fix it, because that's the most common answer to 
profile loading problems.

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

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

Title:
  cache folder belongs to root, causing firefox to fail to run

Status in “firefox” package in Ubuntu:
  New

Bug description:
  On a freshly installed Ubuntu 13.04 64bit on a brand new computer, I had 
Firefox 20 running fine.
  Then I updated it via sudo apt-get install firefox, which updated it to 24.

  After that, any attempt to run Firefox would fail with the error popup (more 
or less) "Your profile cannot be loaded. It may be missing or inaccessible".
  If run from a command line, it would show this error: "Error reading profile 
directory: access denied", or something like that.

  After a whole day of googling and forum posting and useless attempt to
  sort it out, I found out that the issue was that ~/.cache/mozilla had
  "root" as the owner and group. Deleting that folder fixed the issue (a
  new one was created which now correctly belongs to my user).

  Needless to say, I didn't do anything that would legitimate the wrong
  owner of the ~/.cache/mozilla folder. I never touched it, so if it got
  the wrong owner there's a bug somewhere.

  Please do not underestimate the importance of this bug, which renders firefox 
unusable, and whose workaround, though extremely easy, is very hard to figure 
out.
  Also, I bet most user who face this will almost surely delete their profile 
(as I did) in a useless attempt to fix it, because that's the most common 
answer to profile loading problems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1239406/+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 1239405] [NEW] Cannot access internet via Huawei E352 modem.

2013-10-13 Thread Full inu

Public bug reported:

Settings in the "/etc/NetworkManager/system-connections/Megafon RUS"
file:

[connection]
id=Megafon RUS
uuid=d8a3a742-fadb-4abd-81bb-8258c9855975
type=gsm
autoconnect=false

[gsm]
number=*99#
username=gdata
password=gdata
apn=internet

[ppp]
lcp-echo-failure=5
lcp-echo-interval=30

[serial]
baud=115200

[ipv4]
method=auto


Summary:
After configuring this modem and trying to connect to the internet always 
happens disconnect, and i don't know why, when and where)

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

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

Title:
  Cannot access internet via Huawei E352 modem.

Status in “modemmanager” package in Ubuntu:
  New

Bug description:
  Settings in the "/etc/NetworkManager/system-connections/Megafon RUS"
  file:

  [connection]
  id=Megafon RUS
  uuid=d8a3a742-fadb-4abd-81bb-8258c9855975
  type=gsm
  autoconnect=false

  [gsm]
  number=*99#
  username=gdata
  password=gdata
  apn=internet

  [ppp]
  lcp-echo-failure=5
  lcp-echo-interval=30

  [serial]
  baud=115200

  [ipv4]
  method=auto



  Summary:
  After configuring this modem and trying to connect to the internet always 
happens disconnect, and i don't know why, when and where)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1239405/+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 1232299] Re: gnome-session-flashback with Compiz launches Unity

2013-10-13 Thread Felix Moreno

To fix it i use this bug report..
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1180556

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

Title:
  gnome-session-flashback with Compiz launches Unity

Status in “compiz” package in Ubuntu:
  Confirmed
Status in “gnome-panel” package in Ubuntu:
  New

Bug description:
  gnome-session-flashback (Flashback (No Effects)) which runs with Metacity 
works fine.
  gnome-session-flashback (Flashback) which runs with Compiz starts Unity 
instead.

  It works very well with Metacity, but if you use Compiz, then you get
  a conflict with Unity. That is; you get both Unity and Gnome Panel
  running at the same time.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-session-flashback 1:3.6.2-0ubuntu15
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Sat Sep 28 01:18:08 2013
  GsettingsChanges: b'org.gnome.gnome-panel.run-dialog' b'history' b"['compiz', 
'ubuntu-bug fontconfig', 'update-manager -c -d']"
  InstallationDate: Installed on 2011-10-21 (707 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: gnome-panel
  UpgradeStatus: Upgraded to saucy on 2013-09-16 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1232299/+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 1234394] Re: I can't log off or shutdown witn gnome-panel ubuntu 13.10

2013-10-13 Thread Felix Moreno

** Description changed:

  I just installed a fresh ubuntu 13.10 last beta after that:
  sudo apt-get install gnome-panel
  then I log off and choos gnome panel flashback session with effects and 
then...
  Just try to shut down or log off under gnome-panel and u can't...
  
  is not working, no menu appear to logg off or shut down...
+ 
+ IMPORTANT, IN A FRESH INSTALL OF UBUNTU 13.10 BETA 2 DE PROBLEM IS NOT
+ THERE, BUT AFTER THAT IF YOU UPDATE UBUNTU 13.10 THE BUG WILL BE THERE
+ AND YOU CANT LOG OFF OR SHUT DOWN..

** Tags added: 13.10 regression-release regression-update saucy ubuntu
ubuntu-bug

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

Title:
  I can't log off or shutdown witn gnome-panel ubuntu 13.10

Status in “gnome-panel” package in Ubuntu:
  New

Bug description:
  I just installed a fresh ubuntu 13.10 last beta after that:
  sudo apt-get install gnome-panel
  then I log off and choos gnome panel flashback session with effects and 
then...
  Just try to shut down or log off under gnome-panel and u can't...

  is not working, no menu appear to logg off or shut down...

  IMPORTANT, IN A FRESH INSTALL OF UBUNTU 13.10 BETA 2 DE PROBLEM IS NOT
  THERE, BUT AFTER THAT IF YOU UPDATE UBUNTU 13.10 THE BUG WILL BE THERE
  AND YOU CANT LOG OFF OR SHUT DOWN..

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1234394/+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 939335] Re: Missing options to run at critical battery level as hibernate and suspend [Ubuntu 12.04 alpha 2]

** Attachment added: "Screenshot from 2013-10-13 19:24:31.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/939335/+attachment/3876870/+files/Screenshot%20from%202013-10-13%2019%3A24%3A31.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/939335

Title:
  Missing options to run at critical battery level as hibernate and
  suspend [Ubuntu 12.04 alpha 2]

Status in “gnome-power-manager” package in Ubuntu:
  Confirmed

Bug description:
  [EN] In power options are no longer present the battery power save
  options

  [IT] In Ubuntu 12.04 alpha 2 mancano le opzioni che vengono eseguite
  quando la carica della batteria raggiunge il livello critico

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/939335/+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 939335] Re: Missing options to run at critical battery level as hibernate and suspend [Ubuntu 12.04 alpha 2]

The "hibernate" option is now present, but greyed out, which I guess is
because hibernation is disabled globally, which in turn I guess is
because hibernation doesn't work in most cases (very sad that nothing
has been done to fix that yet).

The "suspend" option is missing completely, though it is actually the action 
that is taken by default.
I wonder what happens if you change it and choose "turn off". You probably 
won't be able to ever set it to "suspend" again, which inconsistent with the 
fact that it is the one configured by default. On a fresh install, in the Power 
settings the current option is shown as an empty item, and it does not appear 
when you unfold the dropdown (see screenshot).

By the way, suspend does not work at all with low batter, see #1239402.
Perhaps that is the reason why it has been removed as a choice? But if so, then 
it shouldn't be the default one.

I can't understand how such huge issues don't get attention, when they
are the most critical ones which are making Ubuntu a terribly unstable
system which cannot be used safely.

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

Title:
  Missing options to run at critical battery level as hibernate and
  suspend [Ubuntu 12.04 alpha 2]

Status in “gnome-power-manager” package in Ubuntu:
  Confirmed

Bug description:
  [EN] In power options are no longer present the battery power save
  options

  [IT] In Ubuntu 12.04 alpha 2 mancano le opzioni che vengono eseguite
  quando la carica della batteria raggiunge il livello critico

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/939335/+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 1218322] Re: Can't set keyboard layout change to ctrl+shift

2013-10-13 Thread Raven

I confirm this bug on Ubuntu 13.10 х64

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

Title:
  Can't set keyboard layout change to ctrl+shift

Status in Indicator keyboard:
  New
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged

Bug description:
  Can't set keyboard layout change to ctrl+shift, Caps Lock, alt+shift
  etc. "Shift", "CapsLock" keys are just ignored in settings. Also the
  default shortcut was set to "Super+Space" that is inconveniently,
  because Dash is opening when you swich your keyboard layout.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Thu Aug 29 14:21:54 2013
  InstallationDate: Installed on 2013-07-31 (28 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130730)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-keyboard/+bug/1218322/+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 1167560] Re: Audio preview for split track is muted

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

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

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

Title:
  Audio preview for split track is muted

Status in “brasero” package in Ubuntu:
  Confirmed

Bug description:
  Doing an audio preview inside the split track menu for an audio cd
  doesn't allow you to set the volume. In addition by default it seems
  to be muted.

  To reproduce:

  Launch brasero
  Start a new audio cd
  Add a music file
  Select the music file and click split track
  Click the green play arrow
  --- no sound is produced
  Click the volume slider next to the track
  --- it's set to muted, but doesn't allow adjustment

  Is this some pulse/esound/alsa audio stack issue or something else?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: brasero 3.6.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
  Uname: Linux 3.8.0-17-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Wed Apr 10 16:19:44 2013
  InstallationDate: Installed on 2012-07-13 (271 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  SourcePackage: brasero
  UpgradeStatus: Upgraded to raring on 2012-11-16 (145 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1167560/+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 1239398] Re: /dev/disk/by-path not being populated

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

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

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

Title:
  /dev/disk/by-path not being populated

Status in “udisks2” package in Ubuntu:
  Confirmed

Bug description:
  It looks like /dev/disk/by-path isn't getting populated with my SATA
  drives:

  dg@major:/dev/disk$ ls -l by-path
  total 0
  lrwxrwxrwx 1 root root  9 Oct 13 12:05 
pci-:00:1d.0-usb-0:1.5:1.0-scsi-0:0:0:0 -> ../../sdc
  lrwxrwxrwx 1 root root 10 Oct 13 12:05 
pci-:00:1d.0-usb-0:1.5:1.0-scsi-0:0:0:0-part1 -> ../../sdc1

  dg@major:/dev/disk$ ls -l by-uuid/
  total 0
  lrwxrwxrwx 1 root root 10 Oct 13 14:39 0af33ca5-b8f5-4f9b-9431-371a43459e7b 
-> ../../dm-0
  lrwxrwxrwx 1 root root 10 Oct 13 12:06 1bc920db-d852-493a-9959-89006e4b58f3 
-> ../../dm-1
  lrwxrwxrwx 1 root root 10 Oct 13 12:05 65811f37-962c-43ba-95a5-d3cddb3a8759 
-> ../../sdc1
  lrwxrwxrwx 1 root root 10 Oct 13 12:06 6f692bcf-9da3-442b-854d-1d1c129a65fd 
-> ../../sda2
  lrwxrwxrwx 1 root root 10 Oct 13 12:05 711860b7-f028-46b1-83bb-c2be5dc8044d 
-> ../../sdb1
  lrwxrwxrwx 1 root root 10 Oct 13 12:05 985b0eb1-c149-486d-a66d-3113788778b1 
-> ../../sdb5
  lrwxrwxrwx 1 root root 11 Oct 13 14:39 ce84c41a-bf5b-4c2a-a353-6fa2bfda70ea 
-> ../../dm-11
  lrwxrwxrwx 1 root root 10 Oct 13 12:06 d8314979-8ace-401c-88df-728ad6b89cb5 
-> ../../sda1

  dg@major:/dev/disk$ ls -l /sys/class/block/
  total 0
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 dm-0 -> ../../devices/virtual/block/dm-0
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 dm-1 -> ../../devices/virtual/block/dm-1
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 dm-10 -> 
../../devices/virtual/block/dm-10
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 dm-11 -> 
../../devices/virtual/block/dm-11
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 dm-2 -> ../../devices/virtual/block/dm-2
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 dm-3 -> ../../devices/virtual/block/dm-3
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 dm-4 -> ../../devices/virtual/block/dm-4
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 dm-5 -> ../../devices/virtual/block/dm-5
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 dm-6 -> ../../devices/virtual/block/dm-6
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 dm-7 -> ../../devices/virtual/block/dm-7
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 dm-8 -> ../../devices/virtual/block/dm-8
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 dm-9 -> ../../devices/virtual/block/dm-9
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 loop0 -> 
../../devices/virtual/block/loop0
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 loop1 -> 
../../devices/virtual/block/loop1
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 loop2 -> 
../../devices/virtual/block/loop2
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 loop3 -> 
../../devices/virtual/block/loop3
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 loop4 -> 
../../devices/virtual/block/loop4
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 loop5 -> 
../../devices/virtual/block/loop5
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 loop6 -> 
../../devices/virtual/block/loop6
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 loop7 -> 
../../devices/virtual/block/loop7
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram0 -> ../../devices/virtual/block/ram0
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram1 -> ../../devices/virtual/block/ram1
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram10 -> 
../../devices/virtual/block/ram10
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram11 -> 
../../devices/virtual/block/ram11
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram12 -> 
../../devices/virtual/block/ram12
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram13 -> 
../../devices/virtual/block/ram13
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram14 -> 
../../devices/virtual/block/ram14
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram15 -> 
../../devices/virtual/block/ram15
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram2 -> ../../devices/virtual/block/ram2
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram3 -> ../../devices/virtual/block/ram3
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram4 -> ../../devices/virtual/block/ram4
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram5 -> ../../devices/virtual/block/ram5
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram6 -> ../../devices/virtual/block/ram6
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram7 -> ../../devices/virtual/block/ram7
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram8 -> ../../devices/virtual/block/ram8
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram9 -> ../../devices/virtual/block/ram9
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 sda -> 
../../devices/pci:00/:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sda
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 sda1 -> 
../../devices/pci:00/:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sda/sda1
  lrwxrwxrwx 1 root root 0 Oct 13 18:28 sda2 -> 
../../devices/pci:00/:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sda/sda2
  lrwxrwxrwx 1 root root 0 Oct 13 18:2

[Desktop-packages] [Bug 1229186] Re: Segmentation fault terminating users-admin

2013-10-13 Thread Thaddäus Tintenfisch

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

** This bug has been marked a duplicate of bug 1185396
   users-admin crashed with SIGSEGV in gst_user_profiles_get_for_user()

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

Title:
  Segmentation fault terminating users-admin

Status in “gnome-system-tools” package in Ubuntu:
  New

Bug description:
  Consistant Segmentation fault in users-admin during termination.

  System log entry
  Sep 23 09:21:37 cliffsyx kernel: [ 7296.047153] traps: users-admin[8934] 
general protection ip:414f7c sp:75fd4890 error:0 in 
users-admin[40+22000]

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-system-tools 3.0.0-2ubuntu2
  ProcVersionSignature: Ubuntu 3.10.0-5.15-generic 3.10.2
  Uname: Linux 3.10.0-5-generic x86_64
  ApportVersion: 2.12.4-0ubuntu1
  Architecture: amd64
  Date: Mon Sep 23 09:24:00 2013
  InstallationDate: Installed on 2013-07-28 (56 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 
(20130728)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-system-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/1229186/+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 1239398] [NEW] /dev/disk/by-path not being populated

2013-10-13 Thread Dave Gilbert

Public bug reported:

It looks like /dev/disk/by-path isn't getting populated with my SATA
drives:

dg@major:/dev/disk$ ls -l by-path
total 0
lrwxrwxrwx 1 root root  9 Oct 13 12:05 
pci-:00:1d.0-usb-0:1.5:1.0-scsi-0:0:0:0 -> ../../sdc
lrwxrwxrwx 1 root root 10 Oct 13 12:05 
pci-:00:1d.0-usb-0:1.5:1.0-scsi-0:0:0:0-part1 -> ../../sdc1

dg@major:/dev/disk$ ls -l by-uuid/
total 0
lrwxrwxrwx 1 root root 10 Oct 13 14:39 0af33ca5-b8f5-4f9b-9431-371a43459e7b -> 
../../dm-0
lrwxrwxrwx 1 root root 10 Oct 13 12:06 1bc920db-d852-493a-9959-89006e4b58f3 -> 
../../dm-1
lrwxrwxrwx 1 root root 10 Oct 13 12:05 65811f37-962c-43ba-95a5-d3cddb3a8759 -> 
../../sdc1
lrwxrwxrwx 1 root root 10 Oct 13 12:06 6f692bcf-9da3-442b-854d-1d1c129a65fd -> 
../../sda2
lrwxrwxrwx 1 root root 10 Oct 13 12:05 711860b7-f028-46b1-83bb-c2be5dc8044d -> 
../../sdb1
lrwxrwxrwx 1 root root 10 Oct 13 12:05 985b0eb1-c149-486d-a66d-3113788778b1 -> 
../../sdb5
lrwxrwxrwx 1 root root 11 Oct 13 14:39 ce84c41a-bf5b-4c2a-a353-6fa2bfda70ea -> 
../../dm-11
lrwxrwxrwx 1 root root 10 Oct 13 12:06 d8314979-8ace-401c-88df-728ad6b89cb5 -> 
../../sda1

dg@major:/dev/disk$ ls -l /sys/class/block/
total 0
lrwxrwxrwx 1 root root 0 Oct 13 18:28 dm-0 -> ../../devices/virtual/block/dm-0
lrwxrwxrwx 1 root root 0 Oct 13 18:28 dm-1 -> ../../devices/virtual/block/dm-1
lrwxrwxrwx 1 root root 0 Oct 13 18:28 dm-10 -> ../../devices/virtual/block/dm-10
lrwxrwxrwx 1 root root 0 Oct 13 18:28 dm-11 -> ../../devices/virtual/block/dm-11
lrwxrwxrwx 1 root root 0 Oct 13 18:28 dm-2 -> ../../devices/virtual/block/dm-2
lrwxrwxrwx 1 root root 0 Oct 13 18:28 dm-3 -> ../../devices/virtual/block/dm-3
lrwxrwxrwx 1 root root 0 Oct 13 18:28 dm-4 -> ../../devices/virtual/block/dm-4
lrwxrwxrwx 1 root root 0 Oct 13 18:28 dm-5 -> ../../devices/virtual/block/dm-5
lrwxrwxrwx 1 root root 0 Oct 13 18:28 dm-6 -> ../../devices/virtual/block/dm-6
lrwxrwxrwx 1 root root 0 Oct 13 18:28 dm-7 -> ../../devices/virtual/block/dm-7
lrwxrwxrwx 1 root root 0 Oct 13 18:28 dm-8 -> ../../devices/virtual/block/dm-8
lrwxrwxrwx 1 root root 0 Oct 13 18:28 dm-9 -> ../../devices/virtual/block/dm-9
lrwxrwxrwx 1 root root 0 Oct 13 18:28 loop0 -> ../../devices/virtual/block/loop0
lrwxrwxrwx 1 root root 0 Oct 13 18:28 loop1 -> ../../devices/virtual/block/loop1
lrwxrwxrwx 1 root root 0 Oct 13 18:28 loop2 -> ../../devices/virtual/block/loop2
lrwxrwxrwx 1 root root 0 Oct 13 18:28 loop3 -> ../../devices/virtual/block/loop3
lrwxrwxrwx 1 root root 0 Oct 13 18:28 loop4 -> ../../devices/virtual/block/loop4
lrwxrwxrwx 1 root root 0 Oct 13 18:28 loop5 -> ../../devices/virtual/block/loop5
lrwxrwxrwx 1 root root 0 Oct 13 18:28 loop6 -> ../../devices/virtual/block/loop6
lrwxrwxrwx 1 root root 0 Oct 13 18:28 loop7 -> ../../devices/virtual/block/loop7
lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram0 -> ../../devices/virtual/block/ram0
lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram1 -> ../../devices/virtual/block/ram1
lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram10 -> ../../devices/virtual/block/ram10
lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram11 -> ../../devices/virtual/block/ram11
lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram12 -> ../../devices/virtual/block/ram12
lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram13 -> ../../devices/virtual/block/ram13
lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram14 -> ../../devices/virtual/block/ram14
lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram15 -> ../../devices/virtual/block/ram15
lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram2 -> ../../devices/virtual/block/ram2
lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram3 -> ../../devices/virtual/block/ram3
lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram4 -> ../../devices/virtual/block/ram4
lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram5 -> ../../devices/virtual/block/ram5
lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram6 -> ../../devices/virtual/block/ram6
lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram7 -> ../../devices/virtual/block/ram7
lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram8 -> ../../devices/virtual/block/ram8
lrwxrwxrwx 1 root root 0 Oct 13 18:28 ram9 -> ../../devices/virtual/block/ram9
lrwxrwxrwx 1 root root 0 Oct 13 18:28 sda -> 
../../devices/pci:00/:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sda
lrwxrwxrwx 1 root root 0 Oct 13 18:28 sda1 -> 
../../devices/pci:00/:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sda/sda1
lrwxrwxrwx 1 root root 0 Oct 13 18:28 sda2 -> 
../../devices/pci:00/:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sda/sda2
lrwxrwxrwx 1 root root 0 Oct 13 18:28 sda3 -> 
../../devices/pci:00/:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sda/sda3
lrwxrwxrwx 1 root root 0 Oct 13 18:28 sdb -> 
../../devices/pci:00/:00:1f.2/ata6/host5/target5:0:0/5:0:0:0/block/sdb
lrwxrwxrwx 1 root root 0 Oct 13 18:28 sdb1 -> 
../../devices/pci:00/:00:1f.2/ata6/host5/target5:0:0/5:0:0:0/block/sdb/sdb1
lrwxrwxrwx 1 root root 0 Oct 13 18:28 sdb2 -> 
../../devices/pci:00/:00:1f.2/ata6/host5/target5:0:0/5:0:0:0/block/sdb/sdb2
lrwxrwxrwx 1 root root 0 Oct 13 18:28 sdb5 -> 
..

[Desktop-packages] [Bug 1234968] Re: package libreoffice-common (not installed) failed to install/upgrade: intentando sobreescribir `/usr/bin/soffice', que está también en el paquete openoffice-debian