[Desktop-packages] [Bug 1196484] Re: package ibus 1.4.2-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Launchpad Bug Tracker]

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

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

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

Title:
  package ibus 1.4.2-0ubuntu2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 2

Status in “ibus” package in Ubuntu:
  Confirmed

Bug description:
  Recurring error during login

  ProblemType: Package
  DistroRelease: Ubuntu 13.04
  Package: ibus 1.4.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13
  Uname: Linux 3.8.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  Date: Fri Jun 28 21:48:24 2013
  DuplicateSignature: package:ibus:1.4.2-0ubuntu2:subprocess installed 
post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2012-07-28 (337 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  SourcePackage: ibus
  Title: package ibus 1.4.2-0ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 2
  UpgradeStatus: Upgraded to raring on 2013-06-23 (7 days ago)
  modified.conffile..etc.X11.xinit.xinput.d.ibus: [deleted]

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

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

[Desktop-packages] [Bug 493878] Re: dpkg: error processing ibus (--configure):

[Aron Xu]

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

** This bug has been marked a duplicate of bug 1196484
   package ibus 1.4.2-0ubuntu2 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 2

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

Title:
  dpkg: error processing ibus (--configure):

Status in “ibus” package in Ubuntu:
  New

Bug description:
  Binary package hint: ibus

  update-alternatives: error: alternative path /etc/X11/xinit/xinput.d/ibus 
doesn't exist.
  dpkg: error processing ibus (--configure):
   subprocess installed post-installation script returned error exit status 2
  Errors were encountered while processing:
   ibus

  I got the above message in Apt when upgrading 10.04testing, (a
  9.04>9.10>10.04 upgrade).

  I have a clean install of 10.04testing and I transplanted the missing
  file from there but it does not seem to be detected.

  ProblemType: Bug
  Architecture: amd64
  Date: Mon Dec  7 19:12:46 2009
  DistroRelease: Ubuntu 10.04
  Package: ibus 1.2.0.20091024-1
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-7.10-generic
  SourcePackage: ibus
  Tags: lucid
  Uname: Linux 2.6.32-7-generic x86_64

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

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

[Desktop-packages] [Bug 1234434] Re: [mako] after transitioning to Attached = 0; ofono never transitions back to Attached = 1

[Launchpad Bug Tracker]

** Branch linked: lp:~network-manager/network-manager/ubuntu

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

Title:
  [mako] after transitioning to Attached = 0; ofono never transitions
  back to Attached = 1

Status in “network-manager” package in Ubuntu:
  In Progress
Status in “ofono” package in Ubuntu:
  Fix Released

Bug description:
  This is the relevant excerpt from my syslog:

  Oct  2 22:10:31 ubuntu-phablet kernel: [  862.705020] adjust_soc: ibat_ua = 
-220300, vbat_uv = 4375587, soc = 96, batt_temp=306
  Oct  2 22:10:43 ubuntu-phablet NetworkManager[1087]:  (/ril_0): device 
state change: activated -> disconnected (reason 'user-requested') [100 30 39]
  Oct  2 22:10:43 ubuntu-phablet NetworkManager[1087]:  (/ril_0): 
deactivating device (reason 'user-requested') [39]
  Oct  2 22:10:43 ubuntu-phablet NetworkManager[1087]:  DNS: plugin 
dnsmasq update failed
  Oct  2 22:10:43 ubuntu-phablet dnsmasq[2077]: setting upstream servers from 
DBus
  Oct  2 22:10:43 ubuntu-phablet NetworkManager[1087]:  Removing DNS 
information from /sbin/resolvconf
  Oct  2 22:10:43 ubuntu-phablet NetworkManager[1087]:  WWAN now disabled 
by management service
  Oct  2 22:10:43 ubuntu-phablet dbus[653]: [system] Activating service 
name='org.freedesktop.nm_dispatcher' (using servicehelper)
  Oct  2 22:10:43 ubuntu-phablet whoopsie[1495]: offline
  Oct  2 22:10:43 ubuntu-phablet NetworkManager[1087]:  (/ril_0) marked 
enabled: 0
  Oct  2 22:10:43 ubuntu-phablet dbus[653]: [system] Successfully activated 
service 'org.freedesktop.nm_dispatcher'
  Oct  2 22:10:51 ubuntu-phablet kernel: [  882.695192] adjust_soc: ibat_ua = 
-216800, vbat_uv = 4375587, soc = 96, batt_temp=307
  Oct  2 22:11:03 ubuntu-phablet NetworkManager[1087]:  (/ril_0) failed 
to disconnect modem: Did not receive a reply. Possible causes include: the 
remote application did not send a reply, the message bus security policy 
blocked the reply, the reply timeout expired, or the network connection was 
broken.
  Oct  2 22:11:11 ubuntu-phablet kernel: [  902.685151] adjust_soc: ibat_ua = 
-214500, vbat_uv = 4375293, soc = 96, batt_temp=308
  Oct  2 22:11:31 ubuntu-phablet kernel: [  922.675080] adjust_soc: ibat_ua = 
-213400, vbat_uv = 4376176, soc = 96, batt_temp=308
  Oct  2 22:11:45 ubuntu-phablet ofonod[915]: ril_deactivate_data_call_cb: 
replay failure: GENERIC_FAILURE
  Oct  2 22:11:51 ubuntu-phablet kernel: [  942.665160] adjust_soc: ibat_ua = 
-208900, vbat_uv = 4376176, soc = 96, batt_temp=308
  Oct  2 22:12:11 ubuntu-phablet kernel: [  962.655150] adjust_soc: ibat_ua = 
-205400, vbat_uv = 4376766, soc = 96, batt_temp=308
  Oct  2 22:12:31 ubuntu-phablet kernel: [  982.645170] adjust_soc: ibat_ua = 
-195800, vbat_uv = 4374701, soc = 96, batt_temp=308

  
  This test was achieved by wrapping a Nexus 4 in tinfoil to block radio 
signals. When tinfoil is added; the connection properly drops and is 
disconnected by NetworkManager (note there is one message being sent that ofono 
never seems to respond to). Ofono successfully transitions to Attached = 0; 
Status = searching, etc. to indicate the GPRS connection was severed.

  When tinfoil is removed, oFono eventually moves back to Status =
  registered, but Attached never gets set back to 1. Because of this,
  NetworkManager cannot activate a data session. The context still
  appears to be active throughout, though.

  [ /ril_0 ]
  Features = sms net gprs sim 
  Emergency = 0
  Powered = 1
  Lockdown = 0
  Interfaces = org.ofono.CallVolume org.ofono.MessageManager 
org.ofono.NetworkRegistration org.ofono.VoiceCallManager 
org.ofono.ConnectionManager org.ofono.NetworkTime org.ofono.SimManager 
  Online = 1
  Model = Fake Modem Model
  Revision = M9615A-CEFWMAZM-2.0.1700.84
  Type = hardware
  Serial = 
  Manufacturer = Fake Manufacturer
  [ org.ofono.CallVolume ]
  Muted = 1
  SpeakerVolume = 0
  MicrophoneVolume = 0
  [ org.ofono.MessageManager ]
  [ org.ofono.NetworkRegistration ]
  Status = registered
  Strength = 22
  Name = Bell
  LocationAreaCode = 
  Mode = auto
  MobileCountryCode = 302
  Technology = umts
  CellId = 
  MobileNetworkCode = 610
  [ org.ofono.VoiceCallManager ]
  EmergencyNumbers = 08 000 999 110 112 911 118 119 
  [ org.ofono.ConnectionManager ]
  Attached = 0
  RoamingAllowed = 0
  Powered = 1
  [ org.ofono.NetworkTime ]
  [ org.ofono.SimManager ]
  Retries = 
  MobileCountryCode = 302
  FixedDialing = 0
  SubscriberNumbers =  
  PreferredLanguages = en fr 
  BarredDialing = 0
  ServiceNumbers = [Client Care - Int'l] = '+15144207748' [Client Care 
- Canada] = '*611' [#TAXI] = '#8294' [Directory Assist

[Desktop-packages] [Bug 1247160] Re: Ubuntu 13.10 [Studio Hybrid 140g, Realtek ALC888, Black Digital Out, HDMI] No sound at all

[Raymond]

do you find any similar message from drm which inform you that audio is
supported ?

[drm:drm_detect_monitor_audio], Monitor has basic audio support

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

Title:
  Ubuntu 13.10 [Studio Hybrid 140g, Realtek ALC888, Black Digital Out,
  HDMI] No sound at all

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

Bug description:
  The problem I reported regarding no audio/sound over HDMI in Ubuntu 11
  series as bug #793592, which was fixed in 12.04 and 12.10, has
  unfortunately reappeared in Ubuntu 13.10 following a fresh
  installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kitchen1763 F pulseaudio
   /dev/snd/controlC0:  kitchen1763 F pulseaudio
  Date: Fri Nov  1 17:49:50 2013
  InstallationDate: Installed on 2013-11-01 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kitchen1763 F pulseaudio
   /dev/snd/controlC0:  kitchen1763 F pulseaudio
  Symptom_Jack: Black Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [Studio Hybrid 140g, Realtek ALC888, Black Digital Out, HDMI] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/09/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 0P096C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: '01'
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd11/09/2009:svnDellInc.:pnStudioHybrid140g:pvr00:rvnDellInc.:rn0P096C:rvrA00:cvnDellInc.:ct3:cvr'01':
  dmi.product.name: Studio Hybrid 140g
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1235567] Re: ibus-ui-gtk3 crashed with SIGABRT

[Aron Xu]

** Information type changed from Private to Public

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT

Status in “ibus” package in Ubuntu:
  Confirmed

Bug description:
  Restarted system after installing updates was greeting me with that
  message

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: ibus 1.5.3-6ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Sat Oct  5 08:17:10 2013
  Disassembly: => 0x7f62f38f4f77:   Cannot access memory at address 
0x7f62f38f4f77
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2013-06-12 (114 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: ibus-ui-gtk3 crashed with SIGABRT
  UpgradeStatus: Upgraded to saucy on 2013-08-11 (55 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1247160] Re: Ubuntu 13.10 [Studio Hybrid 140g, Realtek ALC888, Black Digital Out, HDMI] No sound at all

[Raymond]

do you mean you cannot find these when "xrandr --verbose"


audio:  auto
supported: off  auto on

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

Title:
  Ubuntu 13.10 [Studio Hybrid 140g, Realtek ALC888, Black Digital Out,
  HDMI] No sound at all

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

Bug description:
  The problem I reported regarding no audio/sound over HDMI in Ubuntu 11
  series as bug #793592, which was fixed in 12.04 and 12.10, has
  unfortunately reappeared in Ubuntu 13.10 following a fresh
  installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kitchen1763 F pulseaudio
   /dev/snd/controlC0:  kitchen1763 F pulseaudio
  Date: Fri Nov  1 17:49:50 2013
  InstallationDate: Installed on 2013-11-01 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kitchen1763 F pulseaudio
   /dev/snd/controlC0:  kitchen1763 F pulseaudio
  Symptom_Jack: Black Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [Studio Hybrid 140g, Realtek ALC888, Black Digital Out, HDMI] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/09/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 0P096C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: '01'
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd11/09/2009:svnDellInc.:pnStudioHybrid140g:pvr00:rvnDellInc.:rn0P096C:rvrA00:cvnDellInc.:ct3:cvr'01':
  dmi.product.name: Studio Hybrid 140g
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1177305] Re: Unity freezes for few seconds when showing up Guake (F12) window

[Vincas Dargis]

This is not an issue in 13.10 anymore.

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

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

Title:
  Unity freezes for few seconds when showing up Guake (F12) window

Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 13.04 x86_64, GeForce 8400M GS 256MB with 310.44 (and same with
  older)

  Every time I want to lauch Guake terminal (F12 hot-key) desktop
  freezes for fews seconds. Cannot move or click anything, System Load
  Indicator does not repaint.

  After Guake successfully shows up I can see 100% CPU usage history in
  System Load Indicator for that "blackout".

  I submitting this as Unity bug because I have experienced similar
  effect after resizing (maximizing) some other windows I cannot
  currelty recall.

  In fact, this problem appeard on 12.10 (I am not sure about 12.04
  though), I waited for this release hoping it will go away as tempolar
  glitch.

  Interesint thing is that nividia-settings states:
  "Used Dedicated Memory: 123 MB (96%)"
  Maybe I just lack some "power"?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Aplankas: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  310.44  Wed Mar 27 14:51:30 
PDT 2013
   GCC version:  gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,imgpng,place,expo,move,vpswitch,session,workarounds,gnomecompat,grid,resize,regex,mousepoll,wall,unitymtgrabhandles,snap,fade,ezoom,scale,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue May  7 11:48:32 2013
  DistUpgraded: 2013-05-06 22:43:36,826 DEBUG enabling apt cron job
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-310-updates, 310.44, 3.8.0-19-generic, x86_64: installed
   vboxhost, 4.2.10, 3.7.0-7-generic, x86_64: installed
   vboxhost, 4.2.10, 3.8.0-19-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation G86M [GeForce 8400M GS] [10de:0427] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell Device [1028:01f1]
  InstallationDate: Installed on 2012-10-19 (199 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: Dell Inc. Inspiron 1520
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=lt_LT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=1121f846-dcd4-454e-9762-6d045c89df54 ro quiet splash
  SourcePackage: unity
  UpgradeStatus: Upgraded to raring on 2013-05-06 (0 days ago)
  dmi.bios.date: 11/05/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0KY768
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd11/05/2007:svnDellInc.:pnInspiron1520:pvr:rvnDellInc.:rn0KY768:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1520
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.44+git20130502.0112-0ubuntu0sarvatt
  version.libgl1-mesa-dri: libgl1-mesa-dri 
9.2.0~git20130503.e495d884-0ubuntu0sarvatt
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
9.2.0~git20130503.e495d884-0ubuntu0sarvatt
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  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.99+git20130315.3e5350be-0ubuntu0sarvatt
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.21.6+git20130502.5637c173-0ubuntu0sarvatt
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7-0ubuntu1
  xserver.bootTime: Tue May  7 11:39:08 2013
  xserver.configfile: /etc/X11/xorg.conf
  xserv

[Desktop-packages] [Bug 1248043] [NEW] evince's menus are useless with the HUD

[Chow Loong Jin]

Public bug reported:

In Ubuntu 13.10, most of Evince's menu items have been moved into the
gear cog on the upper right corner of the window like Nautilus, leaving
a single "Help" menu item on the application menu. This makes it
effectively useless with Unity's HUD, especially when the Help menu item
can be triggered with F1.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: evince 3.10.0-0ubuntu2
ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
Uname: Linux 3.11.5-hyper1 x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Tue Nov  5 14:35:34 2013
MarkForUpload: True
SourcePackage: evince
UpgradeStatus: Upgraded to saucy on 2013-10-16 (19 days ago)

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


** Tags: amd64 apport-bug saucy

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

Title:
  evince's menus are useless with the HUD

Status in “evince” package in Ubuntu:
  New

Bug description:
  In Ubuntu 13.10, most of Evince's menu items have been moved into the
  gear cog on the upper right corner of the window like Nautilus,
  leaving a single "Help" menu item on the application menu. This makes
  it effectively useless with Unity's HUD, especially when the Help menu
  item can be triggered with F1.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: evince 3.10.0-0ubuntu2
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.11.5-hyper1 x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Tue Nov  5 14:35:34 2013
  MarkForUpload: True
  SourcePackage: evince
  UpgradeStatus: Upgraded to saucy on 2013-10-16 (19 days ago)

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

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

[Desktop-packages] [Bug 585765] Re: [HP ProBook 6440b] Ubuntu 10.04 random freezes

[Runar Ingebrigtsen]

I am currently running 13.04 and the same problem is still present. It's
been with me since 12.04

But now I have discovered a pattern to these freezes: My power cord is
always unplugged when Ubuntu freezes.

I have a usage pattern that might have an impact: Whenever the screen
saver is starting (the desktop is fading out), I push shift or move my
mouse to avoid having to write the password. I know, it's odd behavior
since I could just prolong the timeout.

Clearly this has to do with power management, anyway.

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

Title:
  [HP ProBook 6440b] Ubuntu 10.04 random freezes

Status in The Linux Kernel:
  New
Status in “linux” package in Ubuntu:
  Incomplete
Status in “xorg-server” package in Ubuntu:
  Invalid

Bug description:
  Hello,

  on my new laptop, a HP ProBook 6440b (with Core i5 and a plain Intel
  Chipset, 4GB RAM) I get randomly freezes of the whole system. I can't
  reproduce that, what means I don't know a aplication or usage of the
  system making it freeze. sometimes I have uptimes of a day, without
  freeze and sometimes it freezes right after booting the system.

  I found out, that sometimes the MagicSysRQ (R-E-I-S-U-B) works and let
  me shut down the system, sometimes not. I don't know what makes that
  difference. In the system log I can't find any unusual entries. But I
  foun that the system log is still runing, so shuting down the wifi
  with the notebooks hardware switch for example is logged. Also the
  Wifi network connection to my router is not interrupted.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: linux-image-2.6.32-22-generic 2.6.32-22.33
  Regression: No
  Reproducible: No
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  florian1689 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd490 irq 17'
 Mixer name : 'Intel G45 DEVIBX'
 Components : 'HDA:111d7603,103c1722,00100202 
HDA:11c11040,103c3066,00100200 HDA:80862804,80860101,0010'
 Controls  : 23
 Simple ctrls  : 14
  Date: Wed May 26 11:03:07 2010
  EcryptfsInUse: Yes
  Frequency: Once a day.
  HibernationDevice: RESUME=UUID=24088f3d-7be1-4efd-a05a-d1fac42086df
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  MachineType: Hewlett-Packard HP ProBook 6440b
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic 
root=UUID=ac1bccdd-e231-45c3-bfde-991ae9549f0f ro quiet splash
  ProcEnviron:
   LANG=de_DE.utf8
   SHELL=/bin/bash
  RelatedPackageVersions: linux-firmware 1.34
  SourcePackage: linux
  dmi.bios.date: 01/27/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CDD Ver. F.04
  dmi.board.name: 1722
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 29.2B
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CDDVer.F.04:bd01/27/2010:svnHewlett-Packard:pnHPProBook6440b:pvr:rvnHewlett-Packard:rn1722:rvrKBCVersion29.2B:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 6440b
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open

[Daniel van Vugt]

Killing the whole login is pointless because you'd be killing that which a 
locked screen is meant to protect.
Killing just the X session (client) holding the lock is unacceptable because 
killing a user's apps or shell is worse than the bug itself.

If we can get the screensaver to just XUngrabKeyboard and XUngrabPointer
before it attempts to grab them itself, then that would be great. I'm
just not sure if X lets you ungrab grabs you didn't create, so it may
not work.

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

Title:
  screen doesn't lock when some menu is open

Status in GNOME Screensaver:
  Confirmed
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in X.Org X server:
  Confirmed
Status in “gnome-screensaver” package in Ubuntu:
  Triaged
Status in “gnome-screensaver” source package in Precise:
  Confirmed
Status in “xorg-server” package in Debian:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  I'm running a fresh install of Dapper with screensaver set to 'blank
  screen', and 'lock screen when screensaver is active' enabled.

  If a panel menu (e.g. Applications) is open and the machine is left
  idle, the screen fails to lock. It fades out after the time period as
  expected, but the desktop reappears after a few seconds.

  Ben (comments / criticism welcome, this is my first bug report)

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

-- 
Mailing list: https://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 1247160] Re: Ubuntu 13.10 [Studio Hybrid 140g, Realtek ALC888, Black Digital Out, HDMI] No sound at all

[Charles Timms]

Here it is...

kitchen@Eastford-Kitchen:~$ uname -r
3.11.0-12-generic
kitchen@Eastford-Kitchen:~$ sudo get-edid | parse-edid
parse-edid: parse-edid version 2.0.0
[sudo] password for kitchen:
get-edid: get-edid version 2.0.0

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
 Function supported
 Call successful

 VBE version 300
 VBE string at 0x11100 "Intel(r)GM965/PM965/GL960 Graphics Chip 
Accelerated VGA BIOS"

VBE/DDC service about to be called
 Report DDC capabilities

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
 Function supported
 Call successful

 Monitor and video card combination does not support DDC1 transfers
 Monitor and video card combination supports DDC2 transfers
 0 seconds per 128 byte EDID block transfer
 Screen is not blanked during DDC transfer

Reading next EDID block

VBE/DDC service about to be called
 Read EDID

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
 Function supported
 Call successful

EDID claims 1 more blocks left


*** Something special has happened!
Please contact the author, Matthew Kern
E-mail: pyrophobic...@gmail.com
Please include full output from this program (especially that to stderr)


Reading next EDID block

VBE/DDC service about to be called
 Read EDID

 Performing real mode VBE call
 Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
 Function supported
 Call successful

EDID claims 1 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
parse-edid: EDID checksum passed.

 # EDID version 1 revision 3
Section "Monitor"
 # Block type: 2:0 3:fd
 # Block type: 2:0 3:fc
 Identifier "SAMSUNG"
 VendorName "SAM"
 ModelName "SAMSUNG"
 # Block type: 2:0 3:fd
 HorizSync 26-68
 VertRefresh 24-75
 # Max dot clock (video bandwidth) 230 MHz
 # Block type: 2:0 3:fc
 # DPMS capabilities: Active off:no  Suspend:no  Standby:no

 Mode "1360x768"# vfreq 60.015Hz, hfreq 47.712kHz
 DotClock85.50
 HTimings1360 1424 1536 1792
 VTimings768 771 777 795
 Flags"+HSync" "+VSync"
 EndMode
 Mode "1280x720"# vfreq 60.000Hz, hfreq 45.000kHz
 DotClock74.25
 HTimings1280 1390 1430 1650
 VTimings720 725 730 750
 Flags"+HSync" "+VSync"
 EndMode
 # Block type: 2:0 3:fd
 # Block type: 2:0 3:fc
EndSection
kitchen@Eastford-Kitchen:~$


On 04/11/13 18:00, Raymond wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=48157#c9
>
> you should able to find edid of your HDMI monitor
>

-- 
email: timms.char...@gmail.com
phone:+27 (0)44 382 4992
cell: +27 (0)72 230 8049
skype: "charlestimms"

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

Title:
  Ubuntu 13.10 [Studio Hybrid 140g, Realtek ALC888, Black Digital Out,
  HDMI] No sound at all

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

Bug description:
  The problem I reported regarding no audio/sound over HDMI in Ubuntu 11
  series as bug #793592, which was fixed in 12.04 and 12.10, has
  unfortunately reappeared in Ubuntu 13.10 following a fresh
  installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kitchen1763 F pulseaudio
   /dev/snd/controlC0:  kitchen1763 F pulseaudio
  Date: Fri Nov  1 17:49:50 2013
  InstallationDate: Installed on 2013-11-01 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kitchen1763 F pulseaudio
   /dev/snd/controlC0:  kitchen1763 F pulseaudio
  Symptom_Jack: Black Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [Studio Hybrid 140g, Realtek ALC888, Black Digital Out, HDMI] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/09/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 0P096C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: '01'
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd11/09/2009:svnDellInc.:pnStudioHybrid140g:pvr00:rvnDellInc.:rn0P096C:rvrA00:cv

[Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open

[Obadz]

Either that and even if it doesn't work, can't we get a hack that kills
the entire X session in the event the lock is unsuccessful? Or call a
user-defined script? Those would be more useful than removing the
feature altogether.

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

Title:
  screen doesn't lock when some menu is open

Status in GNOME Screensaver:
  Confirmed
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in X.Org X server:
  Confirmed
Status in “gnome-screensaver” package in Ubuntu:
  Triaged
Status in “gnome-screensaver” source package in Precise:
  Confirmed
Status in “xorg-server” package in Debian:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  I'm running a fresh install of Dapper with screensaver set to 'blank
  screen', and 'lock screen when screensaver is active' enabled.

  If a panel menu (e.g. Applications) is open and the machine is left
  idle, the screen fails to lock. It fades out after the time period as
  expected, but the desktop reappears after a few seconds.

  Ben (comments / criticism welcome, this is my first bug report)

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

-- 
Mailing list: https://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 49579] Re: screen doesn't lock when some menu is open

[bar]

** Attachment added: "image002.jpg"
   https://bugs.launchpad.net/bugs/49579/+attachment/3900363/+files/image002.jpg

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

Title:
  screen doesn't lock when some menu is open

Status in GNOME Screensaver:
  Confirmed
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in X.Org X server:
  Confirmed
Status in “gnome-screensaver” package in Ubuntu:
  Triaged
Status in “gnome-screensaver” source package in Precise:
  Confirmed
Status in “xorg-server” package in Debian:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  I'm running a fresh install of Dapper with screensaver set to 'blank
  screen', and 'lock screen when screensaver is active' enabled.

  If a panel menu (e.g. Applications) is open and the machine is left
  idle, the screen fails to lock. It fades out after the time period as
  expected, but the desktop reappears after a few seconds.

  Ben (comments / criticism welcome, this is my first bug report)

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

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

[Desktop-packages] [Bug 1231778] Re: wifi not working on Saucy Salamander

[Tyler Hicks]

Here's a Trusty debdiff for apparmor to fix this bug, bug 1243932, and
bug 1247269. I've tested it using the manual tests mentioned in the
description of the first two bugs, as well as with QRT's test-
apparmor.py test script.

I've smoke tested the chromium-browser profile changes and manually
verified the Python abstraction fix, as well.

** Patch added: "apparmor_2.8.0-0ubuntu34.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1231778/+attachment/3900364/+files/apparmor_2.8.0-0ubuntu34.debdiff

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

Title:
  wifi not working on Saucy Salamander

Status in Enablement project for the Toshiba AC100 NetBook:
  New
Status in AppArmor Linux application security framework:
  In Progress
Status in “apparmor” package in Ubuntu:
  Triaged
Status in “network-manager” package in Ubuntu:
  Invalid

Bug description:
  [Impact]

  On older kernels that are missing certain AppArmor patches related to
  AppArmor D-Bus mediation, the presence of dbus rules in the binary
  AppArmor policy will result in policy load failures and, as a result,
  applications may run unconfined. On newer kernels that are missing the
  same patches mentioned above, the policy load will succeed but the
  dbus rules will be quietly ignored.

  [Test Case]

  * Install and reboot into older, unpatched mainline kernel (such as
  3.1.10-030110-generic)

  * Bad test results on the mainline 3.1.10 kernel:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Cache read/write disabled: /sys/kernel/security/apparmor/features interface 
file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
  apparmor_parser: Unable to replace "/t".  Profile doesn't conform to protocol

  * Good test results on the mainline 3.1.10 kernel with a patched 
apparmor_parser:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Cache read/write disabled: /sys/kernel/security/apparmor/features interface 
file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
  Warning from stdin (stdin line 2): profile /t dbus rules not enforced

  * Install and reboot into newer, unpatched mainline kernel (such as
  3.12.0-031200-generic)

  * Bad test results on the mainline 3.12.0 kernel:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin

  * Good test results on the mainline 3.12.0 kernel with a patched 
apparmor_parser:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
  Warning from stdin (stdin line 2): profile /t dbus rules not enforced

  * Reboot into Ubuntu 3.11.0-12-generic kernel

  * Good test results on the Ubuntu 3.11.0-12-generic kernel with or without a 
patched apparmor_parser:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin

  * Verify that dbus mediation occurs under the Ubuntu 3.11.0-12-generic kernel:
  $ echo "profile nodbus { file, }" | sudo apparmor_parser -rq
  $ dbus-send --print-reply --system --dest=org.freedesktop.DBus 
/org/freedesktop/DBus org.freedesktop.DBus.ListNames | head
  method return sender=org.freedesktop.DBus -> dest=:1.51 reply_serial=2
     array [
    string "org.freedesktop.DBus"
  ...
  $ aa-exec -p nodbus -- dbus-send --print-reply --system 
--dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.ListNames
  Failed to open connection to "system" message bus: An AppArmor policy 
prevents this sender from sending this message to this recipient, 0 matched 
rules; type="method_call", sender="(null)" (inactive) 
interface="org.freedesktop.DBus" member="Hello" error name="(unset)" 
requested_reply="0" destination="org.freedesktop.DBus" (bus)

  [Regression Potential]

  * The regression potential is minor because the fix is small and easy
  to test

  [Original Bug Report]

  Note that apparmor_parser warns that the dbus rule(s) will not be
  enforced and then loads the binary policy without any dbus rules.

  Lubuntu 13.10 installed from daily image have wifi not working, even
  with BT disabled.

  confirmed by stuw on IRC at Sun Sep 22
  15:40 < stuw> iz1glg, I saw similar problem, but I don't know the reason and 
solution.

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

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

[Desktop-packages] [Bug 1231778] Re: wifi not working on Saucy Salamander

[Tyler Hicks]

Here's a Saucy debdiff for apparmor to fix this bug and bug 1243932.
I've tested it using the manual tests mentioned in the description of
both bugs, as well as with QRT's test-apparmor.py test script.

** Patch added: "apparmor_2.8.0-0ubuntu31.1.debdiff"
   
https://bugs.launchpad.net/apparmor/+bug/1231778/+attachment/3900362/+files/apparmor_2.8.0-0ubuntu31.1.debdiff

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

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

Title:
  wifi not working on Saucy Salamander

Status in Enablement project for the Toshiba AC100 NetBook:
  New
Status in AppArmor Linux application security framework:
  In Progress
Status in “apparmor” package in Ubuntu:
  Triaged
Status in “network-manager” package in Ubuntu:
  Invalid

Bug description:
  [Impact]

  On older kernels that are missing certain AppArmor patches related to
  AppArmor D-Bus mediation, the presence of dbus rules in the binary
  AppArmor policy will result in policy load failures and, as a result,
  applications may run unconfined. On newer kernels that are missing the
  same patches mentioned above, the policy load will succeed but the
  dbus rules will be quietly ignored.

  [Test Case]

  * Install and reboot into older, unpatched mainline kernel (such as
  3.1.10-030110-generic)

  * Bad test results on the mainline 3.1.10 kernel:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Cache read/write disabled: /sys/kernel/security/apparmor/features interface 
file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
  apparmor_parser: Unable to replace "/t".  Profile doesn't conform to protocol

  * Good test results on the mainline 3.1.10 kernel with a patched 
apparmor_parser:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Cache read/write disabled: /sys/kernel/security/apparmor/features interface 
file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
  Warning from stdin (stdin line 2): profile /t dbus rules not enforced

  * Install and reboot into newer, unpatched mainline kernel (such as
  3.12.0-031200-generic)

  * Bad test results on the mainline 3.12.0 kernel:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin

  * Good test results on the mainline 3.12.0 kernel with a patched 
apparmor_parser:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
  Warning from stdin (stdin line 2): profile /t dbus rules not enforced

  * Reboot into Ubuntu 3.11.0-12-generic kernel

  * Good test results on the Ubuntu 3.11.0-12-generic kernel with or without a 
patched apparmor_parser:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin

  * Verify that dbus mediation occurs under the Ubuntu 3.11.0-12-generic kernel:
  $ echo "profile nodbus { file, }" | sudo apparmor_parser -rq
  $ dbus-send --print-reply --system --dest=org.freedesktop.DBus 
/org/freedesktop/DBus org.freedesktop.DBus.ListNames | head
  method return sender=org.freedesktop.DBus -> dest=:1.51 reply_serial=2
     array [
    string "org.freedesktop.DBus"
  ...
  $ aa-exec -p nodbus -- dbus-send --print-reply --system 
--dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.ListNames
  Failed to open connection to "system" message bus: An AppArmor policy 
prevents this sender from sending this message to this recipient, 0 matched 
rules; type="method_call", sender="(null)" (inactive) 
interface="org.freedesktop.DBus" member="Hello" error name="(unset)" 
requested_reply="0" destination="org.freedesktop.DBus" (bus)

  [Regression Potential]

  * The regression potential is minor because the fix is small and easy
  to test

  [Original Bug Report]

  Note that apparmor_parser warns that the dbus rule(s) will not be
  enforced and then loads the binary policy without any dbus rules.

  Lubuntu 13.10 installed from daily image have wifi not working, even
  with BT disabled.

  confirmed by stuw on IRC at Sun Sep 22
  15:40 < stuw> iz1glg, I saw similar problem, but I don't know the reason and 
solution.

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

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

[Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open

[Daniel van Vugt]

Initially I was tempted to say we can't fix it because popup menus own
("grab") the keyboard and that blocks the screensaver from taking
ownership of the keyboard. But now I wonder...

Can't the screensaver just force XUngrabKeyboard before trying to grab
it? Would that work?

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

Title:
  screen doesn't lock when some menu is open

Status in GNOME Screensaver:
  Confirmed
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in X.Org X server:
  Confirmed
Status in “gnome-screensaver” package in Ubuntu:
  Triaged
Status in “gnome-screensaver” source package in Precise:
  Confirmed
Status in “xorg-server” package in Debian:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  I'm running a fresh install of Dapper with screensaver set to 'blank
  screen', and 'lock screen when screensaver is active' enabled.

  If a panel menu (e.g. Applications) is open and the machine is left
  idle, the screen fails to lock. It fades out after the time period as
  expected, but the desktop reappears after a few seconds.

  Ben (comments / criticism welcome, this is my first bug report)

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

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

[Desktop-packages] [Bug 1202524] Re: [lts] Switch VGA mode will become black screen

[Yang Bai]

Tried to install ubuntu 12.10 on that machine but failed. The kernel in
the installation iso is 3.5.0-17, there is no i915-hsw module.

So I tried to do a fresh installation of 12.04.2. The xorg stack is lts-
quantal. Without 2:2.20.9-0ubuntu2.3~precise1 in precise-proposed, this
issue can be reproduced. After installing this package, this issue is
fixed.

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

Title:
  [lts] Switch VGA mode will become black screen

Status in HWE Next Project:
  In Progress
Status in OEM Priority Project:
  Invalid
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Fix Released
Status in “xserver-xorg-video-intel-lts-quantal” package in Ubuntu:
  Triaged
Status in “xserver-xorg-video-intel-lts-raring” package in Ubuntu:
  Triaged
Status in “xserver-xorg-video-intel” source package in Quantal:
  Fix Committed
Status in “xserver-xorg-video-intel-lts-quantal” source package in Quantal:
  New
Status in “xserver-xorg-video-intel” source package in Raring:
  Fix Released
Status in “xserver-xorg-video-intel-lts-raring” source package in Raring:
  Fix Committed

Bug description:
  [Impact]
  system hang in a common use-case with external monitor

  [Test case]
  hit the hotkey combo to switch modes and it'll hang

  [Regression potential]
  slim, this has been upstream for some time now

  --

  On a lenovo notebook running precise with quantal LTS stack has this
  issue. When connecting through VGA port, laptop monitor and external
  monitor will enter extend mode. But after pressing FN+F3 to switching
  mode, both laptop monitor and external monitor will become black
  screen, and system is hang, you need to force to power off. When
  connecting external monitor through HDMI, everything is OK.

  CPU: Intel(R) Core(TM) i3-4000M CPU @ 2.40GHz
  GPU: Intel Corporation Haswell Integrated Graphics Controller [8086:0416]

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1202524/+subscriptions

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

[Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open

[Tony]

Encompass wrote: "The computer should lock automatically when idle.
Instead of solving the problem you want to get rid of the feature."

But the feature only works some of the time, and the thread here makes
it clear it isn't going to be fixed while the system uses X.

A security feature that only works some of the time is like a set of
brakes that only works some of the time ... damn dangerous.

Remove it until we have something that can be trusted.

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

Title:
  screen doesn't lock when some menu is open

Status in GNOME Screensaver:
  Confirmed
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in X.Org X server:
  Confirmed
Status in “gnome-screensaver” package in Ubuntu:
  Triaged
Status in “gnome-screensaver” source package in Precise:
  Confirmed
Status in “xorg-server” package in Debian:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  I'm running a fresh install of Dapper with screensaver set to 'blank
  screen', and 'lock screen when screensaver is active' enabled.

  If a panel menu (e.g. Applications) is open and the machine is left
  idle, the screen fails to lock. It fades out after the time period as
  expected, but the desktop reappears after a few seconds.

  Ben (comments / criticism welcome, this is my first bug report)

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

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

[Desktop-packages] [Bug 1248034] [NEW] The "Restart" button in system menu does not make sense

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

On Saucy, there is a stand-alone "Restart" button in the system menu.
But when you click it, it brings up the same menu that "Shut down" will brings.
Furthermore, it will be focusing on "Shut down" instead of Restart

Maybe these two option in the system should be combined together.
Or at lease the "Restart" option should be highlighted when the menu was called 
by the Restart option.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-12-generic 3.11.0-12.19 [modified: 
boot/vmlinuz-3.11.0-12-generic]
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
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ubuntu 1407 F pulseaudio
CurrentDmesg:
 
Date: Tue Nov  5 00:36:56 2013
HibernationDevice: RESUME=UUID=0986bf55-0186-4118-93df-522940ac63d0
InstallationDate: Installed on 2013-11-05 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
IwConfig:
 eth0  no wireless extensions.
 
 lono wireless extensions.
MachineType: Dell Inc. Vostro 3560
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=51a4484a-5bd4-4d0e-acb5-6a826989ba8d ro rootdelay=60 quiet splash 
initcall_debug vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-12-generic N/A
 linux-backports-modules-3.11.0-12-generic  N/A
 linux-firmware 1.116
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
StagingDrivers: rts5139
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/03/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: X44
dmi.board.name: 05GV6H
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: X44
dmi.modalias: 
dmi:bvnDellInc.:bvrX44:bd08/03/2012:svnDellInc.:pnVostro3560:pvrX44:rvnDellInc.:rn05GV6H:rvrA00:cvnDellInc.:ct8:cvrX44:
dmi.product.name: Vostro 3560
dmi.product.version: X44
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug saucy staging
-- 
The "Restart" button in system menu does not make sense
https://bugs.launchpad.net/bugs/1248034
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to unity 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 1246929] Re: alsa bug in KVM virtual machines

[Raymond]

** Package changed: alsa-driver (Ubuntu) => qemu-kvm (Ubuntu)

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

Title:
  alsa bug in KVM virtual machines

Status in “pulseaudio” package in Ubuntu:
  New
Status in “qemu-kvm” package in Ubuntu:
  Incomplete

Bug description:
  I am on Ubuntu 13.10 desktop
  16GB ram
  asus sabertooth 990fx r2.0 motherboard
  amd 8346 cpu
  nvidia gtx650 video card

  Since upgrading to Ubuntu 13.10 audio no longer works in KVM.
  Checking SYSLOG I found this error being logged:

  Oct 31 15:32:31 bmullan-virtual-machine pulseaudio[1814]: [alsa-source-ID 21 
Analog] alsa-source.c: ALSA woke us up to read new data from the device, but 
there was actually nothing to read!
  Oct 31 15:32:31 bmullan-virtual-machine pulseaudio[1814]: [alsa-source-ID 21 
Analog] alsa-source.c: Most likely this is a bug in the ALSA driver 
'snd_hda_intel'. Please report this issue to the ALSA developers.
  Oct 31 15:32:31 bmullan-virtual-machine pulseaudio[1814]: [alsa-source-ID 21 
Analog] alsa-source.c: We were woken up with POLLIN set -- however a subsequent 
snd_pcm_avail() returned 0 or another value < min_avail.

  brian

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Thu Oct 31 19:45:53 2013
  InstallationDate: Installed on 2013-10-31 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131003)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1708
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1708:bd04/09/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

-- 
Mailing list: https://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 49579] Re: screen doesn't lock when some menu is open

[Kristian Erik Hermansen]

Yes. Remove it since it is a decade long bug.

-- 
Kristian Erik Hermansen
https://www.linkedin.com/in/kristianhermansen
https://profiles.google.com/kristian.hermansen
On Nov 4, 2013 9:20 PM, "encompass"  wrote:

> So are you proposing we get rid of the autolock functionality because we
> can't solve this bug?  Or is there some other solution your providing here?
>
>
> On Tue, Nov 5, 2013 at 6:58 AM, Kristian Erik Hermansen <
> kristian.herman...@gmail.com> wrote:
>
> > Yes but that idle lock feature doesn't work and cannot be trusted. It
> would
> > be like saying trust SSL but its using a NULL cipher...
> >
> > --
> > Kristian Erik Hermansen
> > https://www.linkedin.com/in/kristianhermansen
> > https://profiles.google.com/kristian.hermansen
> > On Nov 4, 2013 8:55 PM, "encompass"  wrote:
> >
> > > I totally disagree.
> > > The computer should lock automatically when idle.  Instead of solving
> the
> > > problem you want to get rid of the feature.
> > > There are times when people are distracted and walk away from the
> > > computer.  If someone wanted to be malicious this would be their
> > > opportunity. Just do a little "Kevin Mitnik" and your in.
> > >
> > >
> > > On Tue, Nov 5, 2013 at 4:08 AM, Kristian Erik Hermansen <
> > > kristian.herman...@gmail.com> wrote:
> > >
> > > > Tony -- exactly! Perfect analysis. Its a false sense of security
> which
> > > > should be abolished or rectified.
> > > >
> > > > --
> > > > Kristian Erik Hermansen
> > > > https://www.linkedin.com/in/kristianhermansen
> > > > https://profiles.google.com/kristian.hermansen
> > > > On Nov 4, 2013 5:30 PM, "Tony" <49...@bugs.launchpad.net> wrote:
> > > >
> > > > > I don't have a problem with manually locking the screen, especially
> > as
> > > I
> > > > > have worked in secure Defence facilities where that is standard
> > > > > pracrtice.
> > > > >
> > > > > But I do have a problem with a software interface that falsely
> claims
> > > to
> > > > > provide a facility which in fact doesn't work correctly if at all.
> > > > >
> > > > > To eliminate the immediate problem, distros could get rid of the
> > broken
> > > > > "Lock" setting from the settings menu, and instead just add a
> notice
> > > > > that CTRL-ALT-L (or whatever) will lock the screen.
> > > > >
> > > > > The security issue is not that there isn't an effective automatic
> > lock,
> > > > > but that the software creates a false and misleading impression
> that
> > > > > such a facility exists. That part of the problem could surely be
> > fixed
> > > > > easily by changing the setting dialog box as suggested.
> > > > >
> > > > > My programming days are long over (anyone remember assembly
> > language?),
> > > > > and I don't know what is involved in removing the "Lock" setting
> from
> > > > > the Screensaver/Lock dialog box. If I did know, I'd do it myself.
> > > > >
> > > > > --
> > > > > You received this bug notification because you are subscribed to a
> > > > > duplicate bug report (1226854).
> > > > > https://bugs.launchpad.net/bugs/49579
> > > > >
> > > > > Title:
> > > > >   screen doesn't lock when some menu is open
> > > > >
> > > > > To manage notifications about this bug go to:
> > > > >
> > https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions
> > > > >
> > > >
> > > > --
> > > > You received this bug notification because you are subscribed to a
> > > > duplicate bug report (139405).
> > > > https://bugs.launchpad.net/bugs/49579
> > > >
> > > > Title:
> > > >   screen doesn't lock when some menu is open
> > > >
> > > > To manage notifications about this bug go to:
> > > >
> https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions
> > > >
> > >
> > > --
> > > You received this bug notification because you are subscribed to a
> > > duplicate bug report (1226854).
> > > https://bugs.launchpad.net/bugs/49579
> > >
> > > Title:
> > >   screen doesn't lock when some menu is open
> > >
> > > To manage notifications about this bug go to:
> > > https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions
> > >
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (139405).
> > https://bugs.launchpad.net/bugs/49579
> >
> > Title:
> >   screen doesn't lock when some menu is open
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1226854).
> https://bugs.launchpad.net/bugs/49579
>
> Title:
>   screen doesn't lock when some menu is open
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions
>

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

Title:
  screen doesn't lock when some menu is open

Status in GNOM

Re: [Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open

[encompass]

So are you proposing we get rid of the autolock functionality because we
can't solve this bug?  Or is there some other solution your providing here?


On Tue, Nov 5, 2013 at 6:58 AM, Kristian Erik Hermansen <
kristian.herman...@gmail.com> wrote:

> Yes but that idle lock feature doesn't work and cannot be trusted. It would
> be like saying trust SSL but its using a NULL cipher...
>
> --
> Kristian Erik Hermansen
> https://www.linkedin.com/in/kristianhermansen
> https://profiles.google.com/kristian.hermansen
> On Nov 4, 2013 8:55 PM, "encompass"  wrote:
>
> > I totally disagree.
> > The computer should lock automatically when idle.  Instead of solving the
> > problem you want to get rid of the feature.
> > There are times when people are distracted and walk away from the
> > computer.  If someone wanted to be malicious this would be their
> > opportunity. Just do a little "Kevin Mitnik" and your in.
> >
> >
> > On Tue, Nov 5, 2013 at 4:08 AM, Kristian Erik Hermansen <
> > kristian.herman...@gmail.com> wrote:
> >
> > > Tony -- exactly! Perfect analysis. Its a false sense of security which
> > > should be abolished or rectified.
> > >
> > > --
> > > Kristian Erik Hermansen
> > > https://www.linkedin.com/in/kristianhermansen
> > > https://profiles.google.com/kristian.hermansen
> > > On Nov 4, 2013 5:30 PM, "Tony" <49...@bugs.launchpad.net> wrote:
> > >
> > > > I don't have a problem with manually locking the screen, especially
> as
> > I
> > > > have worked in secure Defence facilities where that is standard
> > > > pracrtice.
> > > >
> > > > But I do have a problem with a software interface that falsely claims
> > to
> > > > provide a facility which in fact doesn't work correctly if at all.
> > > >
> > > > To eliminate the immediate problem, distros could get rid of the
> broken
> > > > "Lock" setting from the settings menu, and instead just add a notice
> > > > that CTRL-ALT-L (or whatever) will lock the screen.
> > > >
> > > > The security issue is not that there isn't an effective automatic
> lock,
> > > > but that the software creates a false and misleading impression that
> > > > such a facility exists. That part of the problem could surely be
> fixed
> > > > easily by changing the setting dialog box as suggested.
> > > >
> > > > My programming days are long over (anyone remember assembly
> language?),
> > > > and I don't know what is involved in removing the "Lock" setting from
> > > > the Screensaver/Lock dialog box. If I did know, I'd do it myself.
> > > >
> > > > --
> > > > You received this bug notification because you are subscribed to a
> > > > duplicate bug report (1226854).
> > > > https://bugs.launchpad.net/bugs/49579
> > > >
> > > > Title:
> > > >   screen doesn't lock when some menu is open
> > > >
> > > > To manage notifications about this bug go to:
> > > >
> https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions
> > > >
> > >
> > > --
> > > You received this bug notification because you are subscribed to a
> > > duplicate bug report (139405).
> > > https://bugs.launchpad.net/bugs/49579
> > >
> > > Title:
> > >   screen doesn't lock when some menu is open
> > >
> > > To manage notifications about this bug go to:
> > > https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions
> > >
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1226854).
> > https://bugs.launchpad.net/bugs/49579
> >
> > Title:
> >   screen doesn't lock when some menu is open
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (139405).
> https://bugs.launchpad.net/bugs/49579
>
> Title:
>   screen doesn't lock when some menu is open
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions
>

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

Title:
  screen doesn't lock when some menu is open

Status in GNOME Screensaver:
  Confirmed
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in X.Org X server:
  Confirmed
Status in “gnome-screensaver” package in Ubuntu:
  Triaged
Status in “gnome-screensaver” source package in Precise:
  Confirmed
Status in “xorg-server” package in Debian:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  I'm running a fresh install of Dapper with screensaver set to 'blank
  screen', and 'lock screen when screensaver is active' enabled.

  If a panel menu (e.g. Applications) is open and the machine is left
  idle, the screen fails to lock. It fades out after the time period as
  expected, but the desktop reappears after a few seconds.

  Ben (comments / criticism wel

Re: [Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open

[Kristian Erik Hermansen]

Yes but that idle lock feature doesn't work and cannot be trusted. It would
be like saying trust SSL but its using a NULL cipher...

-- 
Kristian Erik Hermansen
https://www.linkedin.com/in/kristianhermansen
https://profiles.google.com/kristian.hermansen
On Nov 4, 2013 8:55 PM, "encompass"  wrote:

> I totally disagree.
> The computer should lock automatically when idle.  Instead of solving the
> problem you want to get rid of the feature.
> There are times when people are distracted and walk away from the
> computer.  If someone wanted to be malicious this would be their
> opportunity. Just do a little "Kevin Mitnik" and your in.
>
>
> On Tue, Nov 5, 2013 at 4:08 AM, Kristian Erik Hermansen <
> kristian.herman...@gmail.com> wrote:
>
> > Tony -- exactly! Perfect analysis. Its a false sense of security which
> > should be abolished or rectified.
> >
> > --
> > Kristian Erik Hermansen
> > https://www.linkedin.com/in/kristianhermansen
> > https://profiles.google.com/kristian.hermansen
> > On Nov 4, 2013 5:30 PM, "Tony" <49...@bugs.launchpad.net> wrote:
> >
> > > I don't have a problem with manually locking the screen, especially as
> I
> > > have worked in secure Defence facilities where that is standard
> > > pracrtice.
> > >
> > > But I do have a problem with a software interface that falsely claims
> to
> > > provide a facility which in fact doesn't work correctly if at all.
> > >
> > > To eliminate the immediate problem, distros could get rid of the broken
> > > "Lock" setting from the settings menu, and instead just add a notice
> > > that CTRL-ALT-L (or whatever) will lock the screen.
> > >
> > > The security issue is not that there isn't an effective automatic lock,
> > > but that the software creates a false and misleading impression that
> > > such a facility exists. That part of the problem could surely be fixed
> > > easily by changing the setting dialog box as suggested.
> > >
> > > My programming days are long over (anyone remember assembly language?),
> > > and I don't know what is involved in removing the "Lock" setting from
> > > the Screensaver/Lock dialog box. If I did know, I'd do it myself.
> > >
> > > --
> > > You received this bug notification because you are subscribed to a
> > > duplicate bug report (1226854).
> > > https://bugs.launchpad.net/bugs/49579
> > >
> > > Title:
> > >   screen doesn't lock when some menu is open
> > >
> > > To manage notifications about this bug go to:
> > > https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions
> > >
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (139405).
> > https://bugs.launchpad.net/bugs/49579
> >
> > Title:
> >   screen doesn't lock when some menu is open
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1226854).
> https://bugs.launchpad.net/bugs/49579
>
> Title:
>   screen doesn't lock when some menu is open
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions
>

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

Title:
  screen doesn't lock when some menu is open

Status in GNOME Screensaver:
  Confirmed
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in X.Org X server:
  Confirmed
Status in “gnome-screensaver” package in Ubuntu:
  Triaged
Status in “gnome-screensaver” source package in Precise:
  Confirmed
Status in “xorg-server” package in Debian:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  I'm running a fresh install of Dapper with screensaver set to 'blank
  screen', and 'lock screen when screensaver is active' enabled.

  If a panel menu (e.g. Applications) is open and the machine is left
  idle, the screen fails to lock. It fades out after the time period as
  expected, but the desktop reappears after a few seconds.

  Ben (comments / criticism welcome, this is my first bug report)

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

-- 
Mailing list: https://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 49579] Re: screen doesn't lock when some menu is open

[encompass]

I totally disagree.
The computer should lock automatically when idle.  Instead of solving the
problem you want to get rid of the feature.
There are times when people are distracted and walk away from the
computer.  If someone wanted to be malicious this would be their
opportunity. Just do a little "Kevin Mitnik" and your in.


On Tue, Nov 5, 2013 at 4:08 AM, Kristian Erik Hermansen <
kristian.herman...@gmail.com> wrote:

> Tony -- exactly! Perfect analysis. Its a false sense of security which
> should be abolished or rectified.
>
> --
> Kristian Erik Hermansen
> https://www.linkedin.com/in/kristianhermansen
> https://profiles.google.com/kristian.hermansen
> On Nov 4, 2013 5:30 PM, "Tony" <49...@bugs.launchpad.net> wrote:
>
> > I don't have a problem with manually locking the screen, especially as I
> > have worked in secure Defence facilities where that is standard
> > pracrtice.
> >
> > But I do have a problem with a software interface that falsely claims to
> > provide a facility which in fact doesn't work correctly if at all.
> >
> > To eliminate the immediate problem, distros could get rid of the broken
> > "Lock" setting from the settings menu, and instead just add a notice
> > that CTRL-ALT-L (or whatever) will lock the screen.
> >
> > The security issue is not that there isn't an effective automatic lock,
> > but that the software creates a false and misleading impression that
> > such a facility exists. That part of the problem could surely be fixed
> > easily by changing the setting dialog box as suggested.
> >
> > My programming days are long over (anyone remember assembly language?),
> > and I don't know what is involved in removing the "Lock" setting from
> > the Screensaver/Lock dialog box. If I did know, I'd do it myself.
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1226854).
> > https://bugs.launchpad.net/bugs/49579
> >
> > Title:
> >   screen doesn't lock when some menu is open
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (139405).
> https://bugs.launchpad.net/bugs/49579
>
> Title:
>   screen doesn't lock when some menu is open
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions
>

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

Title:
  screen doesn't lock when some menu is open

Status in GNOME Screensaver:
  Confirmed
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in X.Org X server:
  Confirmed
Status in “gnome-screensaver” package in Ubuntu:
  Triaged
Status in “gnome-screensaver” source package in Precise:
  Confirmed
Status in “xorg-server” package in Debian:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  I'm running a fresh install of Dapper with screensaver set to 'blank
  screen', and 'lock screen when screensaver is active' enabled.

  If a panel menu (e.g. Applications) is open and the machine is left
  idle, the screen fails to lock. It fades out after the time period as
  expected, but the desktop reappears after a few seconds.

  Ben (comments / criticism welcome, this is my first bug report)

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

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

[Desktop-packages] [Bug 1180288] Re: Update to 9.8

[Reinhard Tartler]

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

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

Title:
  Update to 9.8

Status in “libav” package in Ubuntu:
  Fix Released
Status in “libav” package in Debian:
  Fix Released

Bug description:
  Please update libav to 9.8 in saucy:
  http://git.libav.org/?p=libav.git;a=blob;f=Changelog;hb=refs/tags/v9.8
  and http://libav.org/releases/libav-9.8.release

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

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

[Desktop-packages] [Bug 1210101] Re: system crashed when I start gdm or lightdm

[Launchpad Bug Tracker]

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

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

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

Title:
  system crashed when I start gdm or lightdm

Status in “xorg” package in Ubuntu:
  Expired

Bug description:
  see my "ubuntu-bug xorg" file

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu5
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  Uname: Linux 3.10.0-6-generic x86_64
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu Aug  8 13:07:40 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2013-05-12 (87 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic 
root=UUID=5dad886d-c3d3-4b27-baa8-072bd3248f2e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77N-WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77N-WIFI:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  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.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu8
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu8
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2-0ubuntu9
  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.1.0+git20130801.g2ae6bb1-0ubuntu4
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.12-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.8-0ubuntu3
  xserver.bootTime: Thu Aug  8 12:10:12 2013
  xserver.configfile: default
  xserver.errors: Server terminated successfully (0). Closing log file.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.14.2-0ubuntu9

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

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

[Desktop-packages] [Bug 1219253] Re: terminal does not display correctly

[Launchpad Bug Tracker]

[Expired for nvidia-graphics-drivers-304 (Ubuntu) because there has been
no activity for 60 days.]

** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  terminal does not display correctly

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

Bug description:
  ubuntustudio 13.10

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu5
  ProcVersionSignature: Ubuntu 3.11.0-2.1-lowlatency 3.11.0-rc5
  Uname: Linux 3.11.0-2-lowlatency x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.88  Wed Mar 27 14:26:46 
PDT 2013
   GCC version:  gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-9ubuntu1)
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Aug 31 18:18:56 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-304, 304.88, 3.11.0-2-lowlatency, x86_64: installed
   nvidia-304, 304.88, 3.11.0-4-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation G96 [GeForce 9500 GT] [10de:0640] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:82fd]
  InstallationDate: Installed on 2013-08-28 (3 days ago)
  InstallationMedia: Ubuntu-Studio 13.10 "Saucy Salamander" - Alpha amd64 
(20130824)
  LightdmGreeterLog:
   (lightdm-gtk-greeter:1553): GLib-CRITICAL **: g_shell_parse_argv: assertion 
'command_line != NULL' failed
   
   ** (lightdm-gtk-greeter:1553): WARNING **: Failed to open sessions 
directory: Error opening directory '/usr/share/lightdm/sessions': No such file 
or directory
   
   ** (lightdm-gtk-greeter:1553): WARNING **: Failed to load user image: Failed 
to open file '/home/jl/.face': No such file or directory
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-2-lowlatency 
root=UUID=6105f1d0-3e35-47ba-b317-25b0af037a15 ro quiet splash
  SourcePackage: xorg
  UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', 
'-f'] failed with exit code 1: Error: no composite extension
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1801
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A88TD-M EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1801:bd08/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88TD-MEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4
  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-0ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Sat Aug 31 17:46:59 2013
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   Wacom Volito2 4x5 stylus: Invalid type 'touch' for this device.
   Wacom Volito2 4x5 stylus: Invalid type 'pad' for this device.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.14.2.901-2ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1219253/+subscriptions

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

[Desktop-packages] [Bug 1221365] Re: many crashes

[Launchpad Bug Tracker]

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

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

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

Title:
  many crashes

Status in “xorg” package in Ubuntu:
  Expired

Bug description:
  many crashes

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
  Uname: Linux 3.8.0-30-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.9.2-0ubuntu8.4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Sep  5 14:43:40 2013
  DistUpgraded: 2013-07-29 12:14:47,242 DEBUG enabling apt cron job
  DistroCodename: raring
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Device [1b0a:0152]
  InstallationDate: Installed on 2013-07-24 (43 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  MachineType: POSITIVO POS-PIQ77CL
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-30-generic 
root=UUID=e2a636c4-baeb-4eff-89d7-710748526817 ro plymouth:debug=1 quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to raring on 2013-07-29 (38 days ago)
  XorgLogOld:
   
  dmi.bios.date: 01/24/2013
  dmi.bios.vendor: Desenvolvida por Positivo Informatica SA
  dmi.bios.version: 0304R
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: POS-PIQ77CL
  dmi.board.vendor: Positivo Informatica SA
  dmi.board.version: POSITIVO
  dmi.chassis.type: 3
  dmi.chassis.vendor: Positivo Informatica SA
  dmi.chassis.version: 1.00
  dmi.modalias: 
dmi:bvnDesenvolvidaporPositivoInformaticaSA:bvr0304R:bd01/24/2013:svnPOSITIVO:pnPOS-PIQ77CL:pvr0304R_POSO:rvnPositivoInformaticaSA:rnPOS-PIQ77CL:rvrPOSITIVO:cvnPositivoInformaticaSA:ct3:cvr1.00:
  dmi.product.name: POS-PIQ77CL
  dmi.product.version: 0304R_POSO
  dmi.sys.vendor: POSITIVO
  version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1
  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: Thu Sep  5 08:07:01 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.3-0ubuntu6
  xserver.video_driver: intel

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

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

[Desktop-packages] [Bug 1221472] Re: Some system audio working while others don't, this also includes flash.

[Launchpad Bug Tracker]

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

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

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

Title:
  Some system audio working while others don't, this also includes
  flash.

Status in “pulseaudio” package in Ubuntu:
  Expired

Bug description:
  I've found that if I open Skype some system sound work while others
  don't.  If skype is open then I can slide the volume bar and I get
  audio feedback when the volume changes.  If I adjust the volume from
  my keyboard I get no feedback at all.  Additionally if skype is open
  most all system sounds do not produce feedback.  IE closing firefox
  with multiple tabs open.  Other 3rd party software is also effected.
  I get no audio via flash on youtube, pandora, etc.  If I start some
  sort of audio such as pandora, mp3's, youtube before opening Pandora
  then everything works fine.  It seems that Skype puts a lock somewhere
  on the system that isn't released when no audio is being used.

  Linux 3.8.0-30-generic #44-Ubuntu SMP Thu Aug 22 20:52:24 UTC 2013
  x86_64 x86_64 x86_64 GNU/Linux

  This problem appeared after an update to 3.8.0-30-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
  Uname: Linux 3.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  anon   3143 F pulseaudio
   /dev/snd/controlC0:  anon   3143 F pulseaudio
   /dev/snd/pcmC0D0p:   anon   3143 F...m pulseaudio
  Date: Thu Sep  5 17:49:37 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-08-31 (5 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB successful
  Symptom_Card: Built-in Audio - HDA ATI SB
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [To Be Filled By O.E.M., Realtek ALC892, Green Line Out, Rear] 
Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: 970 Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd06/26/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 1194985] Re: gnome-language-selector crashed with TypeError in getUserDefaultLanguage(): can't use a string pattern on a bytes-like object

[Launchpad Bug Tracker]

This bug was fixed in the package language-selector - 0.117

---
language-selector (0.117) trusty; urgency=low

  * LanguageSelector/LocaleInfo.py:
Fix TypeError (LP: #1194985).
 -- Gunnar HjalmarssonTue, 05 Nov 2013 02:34:00 +0100

** Changed in: language-selector (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  gnome-language-selector crashed with TypeError in
  getUserDefaultLanguage(): can't use a string pattern on a bytes-like
  object

Status in “language-selector” package in Ubuntu:
  Fix Released

Bug description:
  I tried to change language (or at least keyboard) and a window flashed
  up but was closed, and the apport system caught it. This is an
  installed Lubuntu 32-bit system (13.10 alpha)

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: language-selector-gnome 0.113
  ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7
  Uname: Linux 3.9.0-7-generic i686
  ApportVersion: 2.10.2-0ubuntu2
  Architecture: i386
  CrashCounter: 1
  Date: Wed Jun 26 20:29:41 2013
  ExecutablePath: /usr/bin/gnome-language-selector
  InstallationDate: Installed on 2013-06-25 (1 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130624)
  InterpreterPath: /usr/bin/python3.3
  MarkForUpload: True
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3.3 /usr/bin/gnome-language-selector
  PythonArgs: ['/usr/bin/gnome-language-selector']
  SourcePackage: language-selector
  Title: gnome-language-selector crashed with TypeError in 
getUserDefaultLanguage(): can't use a string pattern on a bytes-like object
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1194985/+subscriptions

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

[Desktop-packages] [Bug 628105] Re: [Upstream] Text not black in LibreOffice

[Peter Matulis]

When will 3.5.7-0ubuntu5 be pushed to precise-updates?

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

Title:
  [Upstream] Text not black in LibreOffice

Status in LibreOffice Productivity Suite:
  Fix Released
Status in “libreoffice” package in Ubuntu:
  Fix Released
Status in “libreoffice” source package in Precise:
  Fix Committed
Status in “libreoffice” source package in Quantal:
  Won't Fix

Bug description:
  Binary package hint: light-themes

  When using Ambiance theme the body text in Ooo Writer is not black but
  gray. This is quite uncomfortable when writing and thus renders the
  theme in effect unusable. See attached png.

  [Impact]

   * Auto-colored text is illegible on dark background in LibreOffice.
   * Use "High Contrast" theme, unacceptable to customer.
   * User has to mnaually change the color from "automatic" to white.
   * This is affecting a flagship customer.

  [Test Case]

   * In Libreoffice Impress the text with the color "automatic" is hard
  to read if the background color is set to black (example
  file/screenshot attached).

  [Regression Potential]

   * This patch is a backport form upstream, and has been tested. I do
  not see any possible regression potential here.

  [Workaround]
  Go to Tools -> Options... -> LibreOffice -> Appearance -> Font Color and 
change the color from Automatic to Black.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/628105/+subscriptions

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

[Desktop-packages] [Bug 874672] Re: Xorg compiz / unity crash with nouveau

[Solaris]

It seem rather then Xorg is the Kernel is unstable  (nouveau -> TRAP->  
compiz). therefore GUI is unstable and then crash after 10 minutes, mouse 
moving but graphic fade to black.
The only way to reboot is through "alt+sysrq +RSEINUB".
this is dydlog
kam-wrkst CRON[11885]: (root) CMD (command -v debian-sa1 > /dev/null && 
debian-sa1 1 1)
Nov  4 17:25:15 kam-wrkst whoopsie[1743]: online
Nov  4 17:26:16  whoopsie[1743]: last message repeated 23 times
Nov  4 17:27:40  whoopsie[1743]: last message repeated 8 times
Nov  4 17:27:40 kam-wrkst kernel: [185584.376374] nouveau E[  
PGRAPH][:01:00.0] TRAP ch 4 [0x023fc4 compiz[20883]]
Nov  4 17:27:40 kam-wrkst kernel: [185584.376388] nouveau E[  
PGRAPH][:01:00.0] GPC0/TPC1/MP trap: MULTIPLE_WARP_ERRORS GPR_OUT_OF_BOUNDS
Nov  4 17:27:40 kam-wrkst kernel: [185584.376401] nouveau E[  
PGRAPH][:01:00.0] GPC0/TPC2/MP trap: MULTIPLE_WARP_ERRORS GPR_OUT_OF_BOUNDS
Nov  4 17:27:40 kam-wrkst kernel: [185584.378340] nouveau E[  
PGRAPH][:01:00.0] TRAP ch 4 [0x023fc4 compiz[20883]]
Nov  4 17:27:40 kam-wrkst kernel: [185584.378353] nouveau E[  
PGRAPH][:01:00.0] GPC0/TPC3/MP trap: MULTIPLE_WARP_ERRORS GPR_OUT_OF_BOUNDS
Nov  4 17:27:40 kam-wrkst kernel: [185584.382198] nouveau E[  
PGRAPH][:01:00.0] TRAP ch 4 [0x023fc4 compiz[20883]]
Nov  4 17:27:40 kam-wrkst kernel: [185584.382212] nouveau E[  
PGRAPH][:01:00.0] GPC0/TPC0/MP trap: MULTIPLE_WARP_ERRORS GPR_OUT_OF_BOUNDS
Nov  4 17:27:40 kam-wrkst kernel: [185584.382248] nouveau E[  
PGRAPH][:01:00.0] TRAP ch 4 [0x023fc4 compiz[20883]]
Nov  4 17:27:40 kam-wrkst kernel: [185584.382257] nouveau E[  
PGRAPH][:01:00.0] SHADER 0x8204021e
Nov  4 17:27:40 kam-wrkst kernel: [185584.386341] nouveau E[   
PFIFO][:01:00.0] read fault at 0x0001283000 [PAGE_NOT_PRESENT] from 
PGRAPH/DISPATCH on channel 0x023fc4 [compiz[20883]]
Nov  4 17:27:43 kam-wrkst kernel: [185587.199812] SysRq : This sysrq operation 
is disabled.
Nov  4 17:27:43 kam-wrkst kernel: [185587.455500] SysRq : Emergency Sync
Nov  4 17:27:43 kam-wrkst kernel: [185587.671274] SysRq : This sysrq operation 
is disabled.

Nov  4 17:29:07 kam-wrkst rsyslog

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

Title:
  Xorg compiz / unity crash with nouveau

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

Bug description:
  After editing something in CCSM the unity dash and panels quit and compiz 
segfaults - i can restore desktop usability 
  with 
  DISPLAY=:0.0 compiz --replace &
  an tty1 (ctrl-alt-f1)

  After 
  unity --replace
  in a terminal window on the "repared" session , the screen corrupts again 
(requiring compiz --replace)

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: xorg 1:7.6+7ubuntu7
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,resize,compiztoolbox,imgpng,regex,mousepoll,gnomecompat,wall,place,animation,workarounds,move,session,snap,vpswitch,grid,expo,ezoom,staticswitcher,fade,scale,unityshell]
  CompositorRunning: compiz
  Date: Sat Oct 15 00:46:22 2011
  DistUpgraded: Log time: 2011-10-14 16:34:35.467033
  DistroCodename: oneiric
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   nVidia Corporation C77 [GeForce 8200] [10de:0849] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: nVidia Corporation Device [10de:cb84]
  MachineType: nknow Unknow
  ProcEnviron:
   PATH=(custom, user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=UUID=5ea65807-deec-4499-818f-3824159f2d62 ro 
libata.force=noncq
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (0 days ago)
  XorgConf:
   Section "Device"
   Identifier "n"
   Driver "nouveau"
   EndSection
  dmi.bios.date: 11/17/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: NF-MCP78
  dmi.board.vendor: nVIDIA
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd11/17/2009:svnnknow:pnUnknow:pvr:rvnnVIDIA:rnNF-MCP78:rvr:cvn:ct3:cvr:
  dmi.product.name: Unknow
  dmi.sys.vendor: nknow
  version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu5
  version.libdrm2: libdrm2 2.4.26-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
  version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A

[Desktop-packages] [Bug 1247719] Re: crackling, popping, clicking in playback to audigy2 surround51 device

[Raymond]

http://git.alsa-project.org/?p=alsa-
lib.git;a=blob_plain;f=test/chmap.c;hb=HEAD

chmap -D hw:0,0 query

chmap -D front query

chmap -D rear query

chmap -D center_left query

chmap -D surround40 query

chmap -D surround51 query

chmap -D default query

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

Title:
  crackling, popping, clicking in playback to audigy2 surround51 device

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

Bug description:
  After upgrading from Xubuntu 13.04 to 13.10, I hear lots of popping
  (aka crackle, click noises) during playback to my Audigy2 surround51
  device.  This was never a problem before the upgrade.  The noises do
  not show up if I use the card's default, front, or rear devices
  instead, but those leave me without surround sound, so they're no good
  for movie playback.

  The same problem shows up on the surround40 device.  I haven't tried
  the other surround* devices.

  I can reproduce problem in Totem or gst-launch playbin with an .asoundrc 
containing this:
  pcm.!default {
  type plug
  slave.pcm "surround51"
  }

  I can reproduce problem in Exaile with the custom sink pipeline set to
  "alsasink device=surround51" and no .asoundrc.

  I'm running the amd64 build of Xubuntu.

  My Audigy2 has the first alsa sound card slot, making it my default
  sound card.

  I am not using PulseAudio.

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

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

[Desktop-packages] [Bug 1247719] Re: crackling, popping, clicking in playback to audigy2 surround51 device

[Raymond]

http://git.alsa-project.org/?p=alsa-
lib.git;a=blob_plain;f=test/chmap.c;hb=HEAD

chmap hw:0,0 query

chmap front query

chmap rear query

chmap center_left query

chmap surround40 queryy

chmap surround51 query

chmap default query

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

Title:
  crackling, popping, clicking in playback to audigy2 surround51 device

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

Bug description:
  After upgrading from Xubuntu 13.04 to 13.10, I hear lots of popping
  (aka crackle, click noises) during playback to my Audigy2 surround51
  device.  This was never a problem before the upgrade.  The noises do
  not show up if I use the card's default, front, or rear devices
  instead, but those leave me without surround sound, so they're no good
  for movie playback.

  The same problem shows up on the surround40 device.  I haven't tried
  the other surround* devices.

  I can reproduce problem in Totem or gst-launch playbin with an .asoundrc 
containing this:
  pcm.!default {
  type plug
  slave.pcm "surround51"
  }

  I can reproduce problem in Exaile with the custom sink pipeline set to
  "alsasink device=surround51" and no .asoundrc.

  I'm running the amd64 build of Xubuntu.

  My Audigy2 has the first alsa sound card slot, making it my default
  sound card.

  I am not using PulseAudio.

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

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

[Desktop-packages] [Bug 1173551] Re: Evolution crashes on opening

[Brad G]

None of the above worked for me.
running from terminal gave this in the last lines
(evolution:6244): GLib-GObject-WARNING **: Attempt to add property 
EShellSettings::composer-prompt-reply-many-recips after class was initialised
Segmentation fault (core dumped)

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

Title:
  Evolution crashes on opening

Status in “evolution” package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I upgraded this morning, 27/4/2013, and now the mail application,
  Evolution, is not working.

  The problem is that if I open Evolution it displays my mails and then
  closes immediately. I cannot do anything ie open a mail, make a back
  up etc. It doesnt give me a chance to.

  1 - Ubuntu Release:
  michael@Home:~$ lsb_release -rd
  Description:  Ubuntu 13.04
  Release:  13.04

  2 - Evolution version:
  3.6.4-0ubuntu1

  3 - I expected Evolution to open and allow me to retrieve mails etc

  4 - Evolution closed on its own without giving me a chance to perform
  any functions

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: evolution 3.6.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Sat Apr 27 12:37:40 2013
  InstallationDate: Installed on 2011-11-27 (517 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  MarkForUpload: True
  SourcePackage: evolution
  UpgradeStatus: Upgraded to raring on 2013-04-27 (0 days ago)

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

-- 
Mailing list: https://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 879328] Re: Equalizer option is disabled / grayed out

[Chow Loong Jin]

On Tue, Nov 05, 2013 at 01:53:50AM -, Eric Ongerth wrote:
> Here's a screenshot showing banshee's View menu with equalizer option greyed 
> out (attached).
> Yes, I had to set a few seconds' delay in order to capture it.

Hmm, weird. I'm guessing you can't click the menu item? Just to rule
Unity out, could you start Banshee in a terminal as:

UBUNTU_MENUPROXY= banshee

And see if the option is grayed out there?

-- 
Kind regards,
Loong Jin

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

Title:
  Equalizer option is disabled / grayed out

Status in “banshee” package in Ubuntu:
  Confirmed

Bug description:
  Unsure as to the reason, there doesn't seem to be an option for it on
  the preferences menu (or anywhere that doesn't require me to look at
  code or recompile the whole thing) , but the equalizer option is
  inaccessible and has been since the 2.2 update (it was working
  before).

  Hopefully it's a real life bug and not a bad case of user n00bism (me)
  :)

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: banshee 2.2.0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Fri Oct 21 10:49:01 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: banshee
  UpgradeStatus: Upgraded to oneiric on 2011-09-01 (49 days ago)

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

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

[Desktop-packages] [Bug 1246929] Re: alsa bug in KVM virtual machines

[Raymond]

you have to ask the package maintainer since the default is specifed in
CONFIG_AUDIO_DRIVERS during build


/* Order of CONFIG_AUDIO_DRIVERS is import.
   The 1st one is the one used by default, that is the reason
that we generate the list.
*/
static struct audio_driver *drvtab[] = {
#ifdef CONFIG_SPICE
&spice_audio_driver,
#endif
CONFIG_AUDIO_DRIVERS
&no_audio_driver,
&wav_audio_driver
};

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

Title:
  alsa bug in KVM virtual machines

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

Bug description:
  I am on Ubuntu 13.10 desktop
  16GB ram
  asus sabertooth 990fx r2.0 motherboard
  amd 8346 cpu
  nvidia gtx650 video card

  Since upgrading to Ubuntu 13.10 audio no longer works in KVM.
  Checking SYSLOG I found this error being logged:

  Oct 31 15:32:31 bmullan-virtual-machine pulseaudio[1814]: [alsa-source-ID 21 
Analog] alsa-source.c: ALSA woke us up to read new data from the device, but 
there was actually nothing to read!
  Oct 31 15:32:31 bmullan-virtual-machine pulseaudio[1814]: [alsa-source-ID 21 
Analog] alsa-source.c: Most likely this is a bug in the ALSA driver 
'snd_hda_intel'. Please report this issue to the ALSA developers.
  Oct 31 15:32:31 bmullan-virtual-machine pulseaudio[1814]: [alsa-source-ID 21 
Analog] alsa-source.c: We were woken up with POLLIN set -- however a subsequent 
snd_pcm_avail() returned 0 or another value < min_avail.

  brian

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Thu Oct 31 19:45:53 2013
  InstallationDate: Installed on 2013-10-31 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131003)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1708
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1708:bd04/09/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

-- 
Mailing list: https://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 49579] Re: screen doesn't lock when some menu is open

[Kristian Erik Hermansen]

Tony -- exactly! Perfect analysis. Its a false sense of security which
should be abolished or rectified.

-- 
Kristian Erik Hermansen
https://www.linkedin.com/in/kristianhermansen
https://profiles.google.com/kristian.hermansen
On Nov 4, 2013 5:30 PM, "Tony" <49...@bugs.launchpad.net> wrote:

> I don't have a problem with manually locking the screen, especially as I
> have worked in secure Defence facilities where that is standard
> pracrtice.
>
> But I do have a problem with a software interface that falsely claims to
> provide a facility which in fact doesn't work correctly if at all.
>
> To eliminate the immediate problem, distros could get rid of the broken
> "Lock" setting from the settings menu, and instead just add a notice
> that CTRL-ALT-L (or whatever) will lock the screen.
>
> The security issue is not that there isn't an effective automatic lock,
> but that the software creates a false and misleading impression that
> such a facility exists. That part of the problem could surely be fixed
> easily by changing the setting dialog box as suggested.
>
> My programming days are long over (anyone remember assembly language?),
> and I don't know what is involved in removing the "Lock" setting from
> the Screensaver/Lock dialog box. If I did know, I'd do it myself.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1226854).
> https://bugs.launchpad.net/bugs/49579
>
> Title:
>   screen doesn't lock when some menu is open
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions
>

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

Title:
  screen doesn't lock when some menu is open

Status in GNOME Screensaver:
  Confirmed
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in X.Org X server:
  Confirmed
Status in “gnome-screensaver” package in Ubuntu:
  Triaged
Status in “gnome-screensaver” source package in Precise:
  Confirmed
Status in “xorg-server” package in Debian:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  I'm running a fresh install of Dapper with screensaver set to 'blank
  screen', and 'lock screen when screensaver is active' enabled.

  If a panel menu (e.g. Applications) is open and the machine is left
  idle, the screen fails to lock. It fades out after the time period as
  expected, but the desktop reappears after a few seconds.

  Ben (comments / criticism welcome, this is my first bug report)

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

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

[Desktop-packages] [Bug 1184451] Re: Ubuntu 13.10 random screen freeze while Normal OS activites

[James]

It happened to me as well. I semi-maximize a LibreOffice program to the
left or right (holding the title bar to the left or right), then I
maximize the window holding the title bar towards the top of the screen.
The animation of fullscreen comes up, but the system freezes. The mouse
works, but no clicks do. Also, the cursor stays with the "hand grabbing"
icon.

This happened on a recently installed Ubuntu 13.10.

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

Title:
  Ubuntu 13.10 random screen freeze while Normal OS activites

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

Bug description:
  I have recently, re-installed fresh ubuntu 13.10 distribution release.
  But everything worked fine. until recently i had strange problem of my 
display screen getting freezed randomly; but no response to either 
mouse/keyboard.
  But i want to point it out; it happens randomly and is not specific ?
  Other day, i had music player playing in background, but screen freezed. but 
my music was still running. 
  Kindly note, i used multiple monitor setup and same issue of screen freeze 
also cropped up.

  I,am not sure, whether it is bug ?

  thanks for the expertise support.

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

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

[Desktop-packages] [Bug 879328] Re: Equalizer option is disabled / grayed out

[Eric Ongerth]

Here's a screenshot showing banshee's View menu with equalizer option greyed 
out (attached).
Yes, I had to set a few seconds' delay in order to capture it.

** Attachment added: "Screenshot of Banshee with View menu equalizer option 
grey"
   
https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/879328/+attachment/3900270/+files/Screenshot%20from%202013-11-04%2017%3A50%3A53.png

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

Title:
  Equalizer option is disabled / grayed out

Status in “banshee” package in Ubuntu:
  Confirmed

Bug description:
  Unsure as to the reason, there doesn't seem to be an option for it on
  the preferences menu (or anywhere that doesn't require me to look at
  code or recompile the whole thing) , but the equalizer option is
  inaccessible and has been since the 2.2 update (it was working
  before).

  Hopefully it's a real life bug and not a bad case of user n00bism (me)
  :)

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: banshee 2.2.0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Fri Oct 21 10:49:01 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: banshee
  UpgradeStatus: Upgraded to oneiric on 2011-09-01 (49 days ago)

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

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

[Desktop-packages] [Bug 1194985] Re: gnome-language-selector crashed with TypeError in getUserDefaultLanguage(): can't use a string pattern on a bytes-like object

[Gunnar Hjalmarsson]

** Changed in: language-selector (Ubuntu)
   Status: New => In Progress

** Changed in: language-selector (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  gnome-language-selector crashed with TypeError in
  getUserDefaultLanguage(): can't use a string pattern on a bytes-like
  object

Status in “language-selector” package in Ubuntu:
  In Progress

Bug description:
  I tried to change language (or at least keyboard) and a window flashed
  up but was closed, and the apport system caught it. This is an
  installed Lubuntu 32-bit system (13.10 alpha)

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: language-selector-gnome 0.113
  ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7
  Uname: Linux 3.9.0-7-generic i686
  ApportVersion: 2.10.2-0ubuntu2
  Architecture: i386
  CrashCounter: 1
  Date: Wed Jun 26 20:29:41 2013
  ExecutablePath: /usr/bin/gnome-language-selector
  InstallationDate: Installed on 2013-06-25 (1 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130624)
  InterpreterPath: /usr/bin/python3.3
  MarkForUpload: True
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3.3 /usr/bin/gnome-language-selector
  PythonArgs: ['/usr/bin/gnome-language-selector']
  SourcePackage: language-selector
  Title: gnome-language-selector crashed with TypeError in 
getUserDefaultLanguage(): can't use a string pattern on a bytes-like object
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1194985/+subscriptions

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

[Desktop-packages] [Bug 1194985] Re: gnome-language-selector crashed with TypeError in getUserDefaultLanguage(): can't use a string pattern on a bytes-like object

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/language-selector

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

Title:
  gnome-language-selector crashed with TypeError in
  getUserDefaultLanguage(): can't use a string pattern on a bytes-like
  object

Status in “language-selector” package in Ubuntu:
  In Progress

Bug description:
  I tried to change language (or at least keyboard) and a window flashed
  up but was closed, and the apport system caught it. This is an
  installed Lubuntu 32-bit system (13.10 alpha)

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: language-selector-gnome 0.113
  ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7
  Uname: Linux 3.9.0-7-generic i686
  ApportVersion: 2.10.2-0ubuntu2
  Architecture: i386
  CrashCounter: 1
  Date: Wed Jun 26 20:29:41 2013
  ExecutablePath: /usr/bin/gnome-language-selector
  InstallationDate: Installed on 2013-06-25 (1 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130624)
  InterpreterPath: /usr/bin/python3.3
  MarkForUpload: True
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3.3 /usr/bin/gnome-language-selector
  PythonArgs: ['/usr/bin/gnome-language-selector']
  SourcePackage: language-selector
  Title: gnome-language-selector crashed with TypeError in 
getUserDefaultLanguage(): can't use a string pattern on a bytes-like object
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1194985/+subscriptions

-- 
Mailing list: https://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 879328] Re: Equalizer option is disabled / grayed out

[Chow Loong Jin]

On Mon, Nov 04, 2013 at 07:40:22PM -, Eric Ongerth wrote:
> Hi Loong Jin,
> 
> Well, this may be good news  --
> 
> Ctrl+E still activates the equalizer!  I had not thought to try it
> before since the option was grayed out on the View menu.
> 
> I suppose that is probably easier to deal with (though also lower
> priority) than if the equalizer was becoming totally inaccessible.  I'd
> love to see it fixed, but since it works for me by keyboard command I
> won't make any more noise on this bug.

Heheh, this gets weirder, then. Could you try getting a screenshot of the issue?
If you can't activate the screenshot tool while the menu is open, just set it to
grab a screenshot after a delay of X seconds.

-- 
Kind regards,
Loong Jin

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

Title:
  Equalizer option is disabled / grayed out

Status in “banshee” package in Ubuntu:
  Confirmed

Bug description:
  Unsure as to the reason, there doesn't seem to be an option for it on
  the preferences menu (or anywhere that doesn't require me to look at
  code or recompile the whole thing) , but the equalizer option is
  inaccessible and has been since the 2.2 update (it was working
  before).

  Hopefully it's a real life bug and not a bad case of user n00bism (me)
  :)

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: banshee 2.2.0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Fri Oct 21 10:49:01 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: banshee
  UpgradeStatus: Upgraded to oneiric on 2011-09-01 (49 days ago)

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

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

[Desktop-packages] [Bug 49579] Vacation reply

[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/49579

Title:
  screen doesn't lock when some menu is open

Status in GNOME Screensaver:
  Confirmed
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in X.Org X server:
  Confirmed
Status in “gnome-screensaver” package in Ubuntu:
  Triaged
Status in “gnome-screensaver” source package in Precise:
  Confirmed
Status in “xorg-server” package in Debian:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  I'm running a fresh install of Dapper with screensaver set to 'blank
  screen', and 'lock screen when screensaver is active' enabled.

  If a panel menu (e.g. Applications) is open and the machine is left
  idle, the screen fails to lock. It fades out after the time period as
  expected, but the desktop reappears after a few seconds.

  Ben (comments / criticism welcome, this is my first bug report)

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

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

[Desktop-packages] [Bug 1217244] Re: gnome-language-selector crashed with OSError in build_commit_lists(): [Errno 5] Input/output error

[Gunnar Hjalmarsson]

Thanks for your effort to help improving Ubuntu by reporting this bug!

It's not easy to troubleshoot this particular crash. Since there are no
similar crash reports, it appears to be some kind of rare glitch, so I
close the bug.

Please feel free to reopen this bug report, if you think it's an easily
reproducible issue that should be addressed separately.

** Changed in: language-selector (Ubuntu)
   Status: New => Won't Fix

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

Title:
  gnome-language-selector crashed with OSError in build_commit_lists():
  [Errno 5] Input/output error

Status in “language-selector” package in Ubuntu:
  Won't Fix

Bug description:
  It ocurred at startup.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: language-selector-gnome 0.114
  ProcVersionSignature: Ubuntu 3.11.0-3.7-generic 3.11.0-rc6
  Uname: Linux 3.11.0-3-generic i686
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: i386
  CasperVersion: 1.336
  CrashCounter: 1
  Date: Tue Aug 27 07:08:41 2013
  ExecutablePath: /usr/bin/gnome-language-selector
  InterpreterPath: /usr/bin/python3.3
  LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130822)
  MarkForUpload: True
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3.3 /usr/bin/gnome-language-selector
  ProcEnviron:
   LANGUAGE=en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/bin/gnome-language-selector']
  SourcePackage: language-selector
  Title: gnome-language-selector crashed with OSError in build_commit_lists(): 
[Errno 5] Input/output error
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1217244/+subscriptions

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

[Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open

[Tony]

I don't have a problem with manually locking the screen, especially as I
have worked in secure Defence facilities where that is standard
pracrtice.

But I do have a problem with a software interface that falsely claims to
provide a facility which in fact doesn't work correctly if at all.

To eliminate the immediate problem, distros could get rid of the broken
"Lock" setting from the settings menu, and instead just add a notice
that CTRL-ALT-L (or whatever) will lock the screen.

The security issue is not that there isn't an effective automatic lock,
but that the software creates a false and misleading impression that
such a facility exists. That part of the problem could surely be fixed
easily by changing the setting dialog box as suggested.

My programming days are long over (anyone remember assembly language?),
and I don't know what is involved in removing the "Lock" setting from
the Screensaver/Lock dialog box. If I did know, I'd do it myself.

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

Title:
  screen doesn't lock when some menu is open

Status in GNOME Screensaver:
  Confirmed
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in X.Org X server:
  Confirmed
Status in “gnome-screensaver” package in Ubuntu:
  Triaged
Status in “gnome-screensaver” source package in Precise:
  Confirmed
Status in “xorg-server” package in Debian:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  I'm running a fresh install of Dapper with screensaver set to 'blank
  screen', and 'lock screen when screensaver is active' enabled.

  If a panel menu (e.g. Applications) is open and the machine is left
  idle, the screen fails to lock. It fades out after the time period as
  expected, but the desktop reappears after a few seconds.

  Ben (comments / criticism welcome, this is my first bug report)

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

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

[Desktop-packages] [Bug 1247683] Re: Gnome-screensaver does not lock if "turn screen off" is disabled

[Tony]

Seth, thanks for the reference to bug 49579. I can see it's a messy
issue.

I don't have a problem with manually locking the screen, especially as I
have worked in secure Defence facilities where that is standard
pracrtice.

But I do have a problem with a software interface that falsely claims to
provide a facility which in fact doesn't work correctly if at all.

To get rid of the immediate problem, distros could get rid of the broken
"Lock" setting from the settings menu, and instead just add a notice
that CTRL-ALT-L (or whatever) will lock the screen.

The security issue is not that there isn't an effective automatic lock,
but that the software creates a false and misleading impression that
such a facility exists.

My programming days are long over (anyone remember assembly language?),
and I don't know what is involved in removing the "Lock" setting from
the Screensaver/Lock dialog box. If I did know, I'd do it myself.

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

Title:
  Gnome-screensaver does not lock if "turn screen off" is disabled

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

Bug description:
  The "Screensaver & Lock settings dialog" for the gnome screensaver is
  misleading and is a security risk.

  It allows you to specify whether or not the screen will be turned off
  after a certain time, and it allows you to specify whether or not the
  session will lock (and require a password) after a certain time. The
  dialog presents these as indpeendent options, but in reality, the lock
  will NEVER operate unless you also enable "Turn screen off ...".

  The "Lock" option should be grayed out/disabled if "Turn screen off"
  is not enabled.

  Much better would be to change the code so that the two functions are
  independent of each other. Surely it should be possible to lock the
  session after a set time even if you don't have the screen set to turn
  off.

  As it stands, users can be fooled into thinking that their session
  will lock after a set time when in reality that will not happen unless
  they have also enabled "Turn screen off".

  In addition, at present the Lock options for 30 secs, 1 minute, etc
  actually represent the time delay AFTER the screen is turned off. So
  for example if you set "Turn screen off" to 5 minutes and "Lock" to 2
  minutes, the session will lock after 5+2 = 7 minutes.

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

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

[Desktop-packages] [Bug 1247719] Re: crackling, popping, clicking in playback to audigy2 surround51 device

[Raymond]

how about


speaker-test -d -c 2 -t wav -D front

speaker-test -d -c 2 -t wav -D rear

speaker-test -d -c 2 -t wav -D center_lfe

speaker-test -d -c 4 -t wav -D surround40


speaker-test -d -c 2 -t wav -D default

speaker-test -d -c 4 -t wav -D default

speaker-test -d -c 6 -t wav -D default


http://git.alsa-project.org/?p=alsa-lib.git;a=history;f=src/conf/cards/Audigy2.conf;h=db45776e54c422c2bdb8317c45a65210c92bc499;hb=HEAD


http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/log/?qt=grep&q=emu10k1

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

Title:
  crackling, popping, clicking in playback to audigy2 surround51 device

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

Bug description:
  After upgrading from Xubuntu 13.04 to 13.10, I hear lots of popping
  (aka crackle, click noises) during playback to my Audigy2 surround51
  device.  This was never a problem before the upgrade.  The noises do
  not show up if I use the card's default, front, or rear devices
  instead, but those leave me without surround sound, so they're no good
  for movie playback.

  The same problem shows up on the surround40 device.  I haven't tried
  the other surround* devices.

  I can reproduce problem in Totem or gst-launch playbin with an .asoundrc 
containing this:
  pcm.!default {
  type plug
  slave.pcm "surround51"
  }

  I can reproduce problem in Exaile with the custom sink pipeline set to
  "alsasink device=surround51" and no .asoundrc.

  I'm running the amd64 build of Xubuntu.

  My Audigy2 has the first alsa sound card slot, making it my default
  sound card.

  I am not using PulseAudio.

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

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

[Desktop-packages] [Bug 1247719] Re: crackling, popping, clicking in playback to audigy2 surround51 device

[Raymond]

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

did the problem occur with non 48000Hz audio ?

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

Title:
  crackling, popping, clicking in playback to audigy2 surround51 device

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

Bug description:
  After upgrading from Xubuntu 13.04 to 13.10, I hear lots of popping
  (aka crackle, click noises) during playback to my Audigy2 surround51
  device.  This was never a problem before the upgrade.  The noises do
  not show up if I use the card's default, front, or rear devices
  instead, but those leave me without surround sound, so they're no good
  for movie playback.

  The same problem shows up on the surround40 device.  I haven't tried
  the other surround* devices.

  I can reproduce problem in Totem or gst-launch playbin with an .asoundrc 
containing this:
  pcm.!default {
  type plug
  slave.pcm "surround51"
  }

  I can reproduce problem in Exaile with the custom sink pipeline set to
  "alsasink device=surround51" and no .asoundrc.

  I'm running the amd64 build of Xubuntu.

  My Audigy2 has the first alsa sound card slot, making it my default
  sound card.

  I am not using PulseAudio.

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

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

[Desktop-packages] [Bug 1231778] Re: wifi not working on Saucy Salamander

[Tyler Hicks]

** Description changed:

  [Impact]
  
  On older kernels that are missing certain AppArmor patches related to
  AppArmor D-Bus mediation, the presence of dbus rules in the binary
  AppArmor policy will result in policy load failures and, as a result,
  applications may run unconfined. On newer kernels that are missing the
  same patches mentioned above, the policy load will succeed but the dbus
  rules will be quietly ignored.
  
  [Test Case]
  
  * Install older, unpatched mainline kernel (such as
  3.1.10-030110-generic)
  
- * Install newer, unpatched mainline kernel (such as
- 3.12.0-031200-generic)
- 
  * Bad test results on the mainline 3.1.10 kernel:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Cache read/write disabled: /sys/kernel/security/apparmor/features interface 
file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
  apparmor_parser: Unable to replace "/t".  Profile doesn't conform to protocol
  
- * Good test on the mainline 3.1.10 kernel with a patched apparmor_parser:
+ * Good test results on the mainline 3.1.10 kernel with a patched 
apparmor_parser:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Cache read/write disabled: /sys/kernel/security/apparmor/features interface 
file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
  Warning from stdin (stdin line 2): profile /t dbus rules not enforced
+ 
+ * Install newer, unpatched mainline kernel (such as
+ 3.12.0-031200-generic)
  
  * Bad test results on the mainline 3.12.0 kernel:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
  
  * Good test results on the mainline 3.12.0 kernel with a patched 
apparmor_parser:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
  Warning from stdin (stdin line 2): profile /t dbus rules not enforced
  
  * Good test results on the Ubuntu 3.11.0-12-generic kernel with or without a 
patched apparmor_parser:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
+ 
+ * Verify that dbus mediation occurs under the Ubuntu 3.11.0-12-generic kernel:
+ $ echo "profile nodbus { file, }" | sudo apparmor_parser -rq
+ $ dbus-send --print-reply --system --dest=org.freedesktop.DBus 
/org/freedesktop/DBus org.freedesktop.DBus.ListNames | head 
+ method return sender=org.freedesktop.DBus -> dest=:1.51 reply_serial=2
+array [
+   string "org.freedesktop.DBus"
+ 
+ ...
+ $ aa-exec -p nodbus -- dbus-send --print-reply --system 
--dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.ListNames
+ Failed to open connection to "system" message bus: An AppArmor policy 
prevents this sender from sending this message to this recipient, 0 matched 
rules; type="method_call", sender="(null)" (inactive) 
interface="org.freedesktop.DBus" member="Hello" error name="(unset)" 
requested_reply="0" destination="org.freedesktop.DBus" (bus)
  
  [Regression Potential]
  
  * The regression potential is minor because the fix is small and easy to
  test
  
  [Original Bug Report]
  
  Note that apparmor_parser warns that the dbus rule(s) will not be
  enforced and then loads the binary policy without any dbus rules.
  
  Lubuntu 13.10 installed from daily image have wifi not working, even
  with BT disabled.
  
  confirmed by stuw on IRC at Sun Sep 22
  15:40 < stuw> iz1glg, I saw similar problem, but I don't know the reason and 
solution.

** Description changed:

  [Impact]
  
  On older kernels that are missing certain AppArmor patches related to
  AppArmor D-Bus mediation, the presence of dbus rules in the binary
  AppArmor policy will result in policy load failures and, as a result,
  applications may run unconfined. On newer kernels that are missing the
  same patches mentioned above, the policy load will succeed but the dbus
  rules will be quietly ignored.
  
  [Test Case]
  
- * Install older, unpatched mainline kernel (such as
+ * Install and reboot into older, unpatched mainline kernel (such as
  3.1.10-030110-generic)
  
  * Bad test results on the mainline 3.1.10 kernel:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Cache read/write disabled: /sys/kernel/security/apparmor/features interface 
file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
  apparmor_parser: Unable to replace "/t".  Profile doesn't conform to protocol
  
  * Good test results on the mainline 3.1.10 kernel with a patched 
ap

[Desktop-packages] [Bug 1245979] Re: After Upgrade to Kubuntu 13.10 akondai fails to register at d-bus session, making kde-pim suit unusable

[webmarwell]

The way in comment #5 starts akonadi here too.
But whats the problem with akonadi?

I still have every 4 or 5 times starting kubuntu the problem.

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

Title:
  After Upgrade to Kubuntu 13.10 akondai fails to register at d-bus
  session, making kde-pim suit unusable

Status in “akonadi” package in Ubuntu:
  Confirmed

Bug description:
  Upon opening Kontact akonadi is supposed to be loaded but fails with
  the following error: Akonadi fails to register at d-bus session.

  I safed the self-test protocoll of the akonadi server and attached the
  report.

  I already deleted all my akonadi config files but it did not resolve
  the error.

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

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

[Desktop-packages] [Bug 1002978] Re: [meta-bug] Inverted Internal microphone (phase inversion)

[David Henningsson]

> Didn't manage to do anything to mute "Inverted Internal Mic", as does
not show up -> would this be the problem? (see screen shot)

You need to press "F4" to see capture controls. By default, only
playback controls are shown.

In case this does not work, please give alsa-info according to
https://wiki.ubuntu.com/Audio/AlsaInfo - maybe there is more than one ID
for eM350.

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

Title:
  [meta-bug] Inverted Internal microphone (phase inversion)

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

Bug description:
  This is a metabug for all machines that are having phase inverted
  internal microphones.

  If your internal mic is either completely silent (no signal), or you
  can possibly pick a very small sound, with much background noise, even
  though you have set gain to maximum, there is something you could try.

  Install the pavucontrol application, start it and go to the "Input Devices" 
tab. Unlock the channels (there is a keylock icon), then mute the right channel 
while keeping the left channel at the volume you want.
  If the internal mic is now working correctly, you have an inverted internal 
mic, so that your right channel cancels out the left one.

  (If you're not running PulseAudio, you can try doing the same through
  AlsaMixer instead (see https://wiki.ubuntu.com/Audio/Alsamixer ), try
  changing "Capture" level or "Internal Mic" or "Internal Mic Boost"
  using the Q,E,Z,C keys.)

  If so, please file a separate bug against the alsa-driver for your
  issue, make sure hardware info gets attached to it (either alsa-info
  as per https://wiki.ubuntu.com/Audio/AlsaInfo or the standard ones
  that follows when you do "ubuntu-bug alsa-driver" ), then write a
  comment in this bug, with your machine name and a pointer to the other
  bug.

  As time permits, I'll try to work on fixing them for the next Ubuntu release. 
Thanks!
   -- David Henningsson

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

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

[Desktop-packages] [Bug 1247990] Re: dbus: Fix endianness bug in Frequency and Signal properties

[Ubuntu Foundations Team Bug Bot]

The attachment "diff.txt" 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.]

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

Title:
  dbus: Fix endianness bug in Frequency and Signal properties

Status in “wpasupplicant” package in Ubuntu:
  New

Bug description:
  Please include the attached patch in the next update to wpasupplicant
  in Ubuntu 12.04 (Precise).

  The patch is based on this upstream commit
  
http://w1.fi/gitweb/gitweb.cgi?p=hostap-1.git;a=commitdiff;h=42f93a9a0f1858ba8492a1349515624965a64e34;hp=5045a668201f1027dbcc91bd8d092bbcee15a2e3

  The version of wpasupplicant currently in precise (and oneiric had the
  same problem) has the following PowerPC bug:

  To reproduce:

  1. connect to a wireless network by clicking on the name in the applet.
  2. check that the connection works.
  3. see that there is no network listed on "Wireless Networks" in the applet. 
(Although the "Disconnect" words are there and functional.)
  4. see that the signal strength is apparantly empty on the applet icon. (Yet 
the signal strength is actually quit strong.)
  5. check nmcli command and see that signal strength always shows 100 and 
frequency 0.

  Applying the patch to wpasupplicant 0.7.3-6ubuntu2.1 fixes the problem
  (on my PowerPC G4 iBook).  Before finding this patch I've had to work
  around the problem by installing wicd.

  Thanks

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

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

[Desktop-packages] [Bug 1247999] [NEW] gpu lockup

[pete]

Public bug reported:

crashing nouvea gpu lockup

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xorg 1:7.7+1ubuntu6
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.1
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Nov  5 00:13:35 2013
DistUpgraded: 2013-10-31 10:06:17,994 DEBUG enabling apt cron job
DistroCodename: saucy
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 NVIDIA Corporation G86 [GeForce 8400 GS] [10de:0422] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: XFX Pine Group Inc. Device [1682:2310]
InstallationDate: Installed on 2013-06-26 (131 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=e72f995f-0341-47a9-9695-b927a0c74fbb ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to saucy on 2013-10-31 (4 days ago)
dmi.bios.date: 09/20/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.16
dmi.board.name: 0CU409
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: OEM
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.16:bd09/20/2008:svnDellInc.:pnVostro200:pvr:rvnDellInc.:rn0CU409:rvr:cvnDellInc.:ct3:cvrOEM:
dmi.product.name: Vostro 200
dmi.sys.vendor: Dell 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-3ubuntu2
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: Tue Nov  5 00:04:13 2013
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputG-Tech CHINAUSB Wireless Mouse & KeyBoard V1.01   KEYBOARD, 
id 8
 inputG-Tech CHINAUSB Wireless Mouse & KeyBoard V1.01   KEYBOARD, 
id 9
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.14.3-3ubuntu2
xserver.video_driver: nouveau

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


** Tags: apport-bug i386 saucy 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/1247999

Title:
  gpu lockup

Status in “xorg” package in Ubuntu:
  New

Bug description:
  crashing nouvea gpu lockup

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  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.1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Nov  5 00:13:35 2013
  DistUpgraded: 2013-10-31 10:06:17,994 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   NVIDIA Corporation G86 [GeForce 8400 GS] [10de:0422] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: XFX Pine Group Inc. Device [1682:2310]
  InstallationDate: Installed on 2013-06-26 (131 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=e72f995f-0341-47a9-9695-b927a0c74fbb ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to saucy on 2013-10-31 (4 days ago)
  dmi.bios.date: 09/20/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.16
  dmi.board.name: 0CU409
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.16:bd09/20/2008:svnDellInc.:pnVostro200:pvr:rvnDellInc.:rn0CU409:rvr:cvnDellInc.:ct3:cvrOEM:
  dmi.product.name: Vostro 200
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubu

[Desktop-packages] [Bug 1222873] Re: No sound at all in Saucy

[Ray DeCampo]

Upgraded from 13.04 to 13.10 and lost my audio.  I am using nvidia HDMI.
I tried the workaround referenced above with no luck.  I tried a bunch
of different nvidia drivers with no luck.  Everything in the GUIs looks
fine but no sound emits.  This set up was working fine in 13.04.  Not
sure if this falls under this bug or if I should open a separate one,
please advise.

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

Title:
  No sound at all in Saucy

Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I upgraded to Saucy Salamander the last week. Sound output was working
  normally until today. Today I had to use Mumble to talk to my team,
  but sound input was not working, so I tried switching from PulseAudio
  to Alsa in the Mumble configuration, and that made my whole sound
  (input and output) go away. I can't hear anything anymore, neither in
  Mumble, or in the sound test from system settings, or in Rhythmbox, or
  anything else. No sound at all.

  Can you guys help me sort this out, please?

  Extra info:

  $ ▶lsb_release -a
  LSB Version:  
core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu Saucy Salamander (development branch)
  Release:  13.10
  Codename: saucy

  $ ▶apt-cache policy pulseaudio
  pulseaudio:
Instalado: 1:4.0-0ubuntu2+build1
Candidato: 1:4.0-0ubuntu2+build1
Tabela de versão:
   *** 1:4.0-0ubuntu2+build1 0
  500 http://br.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Thanks,

  Diogo

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: pulseaudio 1:4.0-0ubuntu2+build1
  ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
  Uname: Linux 3.11.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  diogobaeder   3039 F pulseaudio
   /dev/snd/controlC1:  diogobaeder   3039 F pulseaudio
   /dev/snd/controlC0:  diogobaeder   3039 F pulseaudio
  Date: Mon Sep  9 11:57:20 2013
  InstallationDate: Installed on 2012-12-02 (280 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to saucy on 2013-09-05 (3 days ago)
  dmi.bios.date: 03/10/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1503
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8P67
  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.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1503:bd03/10/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8P67:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1247683] Re: Gnome-screensaver does not lock if "turn screen off" is disabled

[Seth Arnold]

Time-based locking is unlikely to ever work correctly with X11; see also
bug 49579.

If having your session locked when you are away is important to you, you
should be locking your session manually before leaving.

Thanks

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

Title:
  Gnome-screensaver does not lock if "turn screen off" is disabled

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

Bug description:
  The "Screensaver & Lock settings dialog" for the gnome screensaver is
  misleading and is a security risk.

  It allows you to specify whether or not the screen will be turned off
  after a certain time, and it allows you to specify whether or not the
  session will lock (and require a password) after a certain time. The
  dialog presents these as indpeendent options, but in reality, the lock
  will NEVER operate unless you also enable "Turn screen off ...".

  The "Lock" option should be grayed out/disabled if "Turn screen off"
  is not enabled.

  Much better would be to change the code so that the two functions are
  independent of each other. Surely it should be possible to lock the
  session after a set time even if you don't have the screen set to turn
  off.

  As it stands, users can be fooled into thinking that their session
  will lock after a set time when in reality that will not happen unless
  they have also enabled "Turn screen off".

  In addition, at present the Lock options for 30 secs, 1 minute, etc
  actually represent the time delay AFTER the screen is turned off. So
  for example if you set "Turn screen off" to 5 minutes and "Lock" to 2
  minutes, the session will lock after 5+2 = 7 minutes.

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

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

[Desktop-packages] [Bug 1236601] Re: wrong background color when editing icons on desktop

[Aibara Iduas]

** Bug watch added: GNOME Bug Tracker #711447
   https://bugzilla.gnome.org/show_bug.cgi?id=711447

** Changed in: nautilus
   Importance: Undecided => Unknown

** Changed in: nautilus
   Status: New => Unknown

** Changed in: nautilus
 Remote watch: None => GNOME Bug Tracker #711447

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

Title:
  wrong background color when editing icons on desktop

Status in Nautilus:
  Unknown
Status in “nautilus” package in Ubuntu:
  Triaged
Status in “nautilus” source package in Saucy:
  Triaged

Bug description:
  When creating or renaming an icon on the desktop, nautilus no longers
  colors the background ellipse white, resulting in text being
  unreadable. See attached screenshot for comparison between Raring and
  Saucy.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Mon Oct  7 17:24:39 2013
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'1004x670+867+75'"
  InstallationDate: Installed on 2012-11-13 (328 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to saucy on 2013-08-19 (49 days ago)

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

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

[Desktop-packages] [Bug 1247990] Re: dbus: Fix endianness bug in Frequency and Signal properties

[Adam Smith]

** Description changed:

  Please include the attached patch in the next update to wpasupplicant in
  Ubuntu 12.04 (Precise).
  
  The patch is based on this upstream commit
  
http://w1.fi/gitweb/gitweb.cgi?p=hostap-1.git;a=commitdiff;h=42f93a9a0f1858ba8492a1349515624965a64e34;hp=5045a668201f1027dbcc91bd8d092bbcee15a2e3
  
  The version of wpasupplicant currently in precise (and oneiric had the
- same problem) has the following bug:
+ same problem) has the following PowerPC bug:
  
  To reproduce:
  
  1. connect to a wireless network by clicking on the name in the applet.
  2. check that the connection works.
  3. see that there is no network listed on "Wireless Networks" in the applet. 
(Although the "Disconnect" words are there and functional.)
  4. see that the signal strength is apparantly empty on the applet icon. (Yet 
the signal strength is actually quit strong.)
  5. check nmcli command and see that signal strength always shows 100 and 
frequency 0.
  
- Applying the patch to wpasupplicant 0.7.3-6ubuntu2.1 fixes the problem.
- Before finding this patch I've had to work around the problem by
- installing wicd.
+ Applying the patch to wpasupplicant 0.7.3-6ubuntu2.1 fixes the problem
+ (on my PowerPC G4 iBook).  Before finding this patch I've had to work
+ around the problem by installing wicd.
  
  Thanks

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

Title:
  dbus: Fix endianness bug in Frequency and Signal properties

Status in “wpasupplicant” package in Ubuntu:
  New

Bug description:
  Please include the attached patch in the next update to wpasupplicant
  in Ubuntu 12.04 (Precise).

  The patch is based on this upstream commit
  
http://w1.fi/gitweb/gitweb.cgi?p=hostap-1.git;a=commitdiff;h=42f93a9a0f1858ba8492a1349515624965a64e34;hp=5045a668201f1027dbcc91bd8d092bbcee15a2e3

  The version of wpasupplicant currently in precise (and oneiric had the
  same problem) has the following PowerPC bug:

  To reproduce:

  1. connect to a wireless network by clicking on the name in the applet.
  2. check that the connection works.
  3. see that there is no network listed on "Wireless Networks" in the applet. 
(Although the "Disconnect" words are there and functional.)
  4. see that the signal strength is apparantly empty on the applet icon. (Yet 
the signal strength is actually quit strong.)
  5. check nmcli command and see that signal strength always shows 100 and 
frequency 0.

  Applying the patch to wpasupplicant 0.7.3-6ubuntu2.1 fixes the problem
  (on my PowerPC G4 iBook).  Before finding this patch I've had to work
  around the problem by installing wicd.

  Thanks

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

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

[Desktop-packages] [Bug 1071739] Re: Unable to mount Blank DVD-R Disc

[Marty]

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

Update.
If anyone is still having problems.  The error came back for me after using my 
fix above using "dconf editor".
Navigated to "org/gnome/desktop/media-handling" and unticked "automount" and 
"automount-open".

So I used dconf-editor again and used the search function and searched
for "auto".   I found lots of matches but found that the auto-mount
settings for Caja (Cinammon desktop) were causing the auto-mount
warning/error even though I was using a Unity session.  The problem must
have come back when I started using Caja instead of Nautilus.

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

Title:
  Unable to mount Blank DVD-R Disc

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

Bug description:
  Each time I insert a blank DVD a window opens telling me that I just
  inserted a blank DVD and asking what to do with it.  Immediately
  another window opens on top of it and reads "Unable to mount Blank
  DVD-R Disc Location is already mounted"

  I can click OK to get back to the first window, but the error is
  really annoying and makes no sense.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-settings-daemon 3.4.2-0ubuntu14
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic i686
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: i386
  Date: Fri Oct 26 08:40:17 2012
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120724.2)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1241811] Re: USB disk not automatically mounted after upgrade to 13.10

[ArtDesire]

Have similar issue, automount doesn't work but can mount device
manually. Ubuntu 13.10 UNITY

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

Title:
  USB disk not automatically mounted after upgrade to 13.10

Status in Ubuntu GNOME:
  New
Status in “nautilus” package in Ubuntu:
  Incomplete
Status in “nautilus-udisks” package in Ubuntu:
  Invalid

Bug description:
  Since the upgrade to 13.10, my laptop stopped mounting the USB devices
  (and SD cards too) automatically.

  Inserting the USB I have in the log:

  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.570340] usb 3-2: new 
high-speed USB device number 3 using xhci_hcd
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.593170] usb 3-2: New USB 
device found, idVendor=090c, idProduct=1000
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.593181] usb 3-2: New USB 
device strings: Mfr=1, Product=2, SerialNumber=3
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.593187] usb 3-2: Product: 
Flash Disk
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.593192] usb 3-2: 
Manufacturer: USB
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.593196] usb 3-2: 
SerialNumber: FBF1009232400790
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.593492] usb 3-2: ep 0x81 - 
rounding interval to 128 microframes, ep desc says 255 microframes
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.593501] usb 3-2: ep 0x2 - 
rounding interval to 128 microframes, ep desc says 255 microframes
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.595232] scsi7 : 
usb-storage 3-2:1.0
  SYS: Oct 18 13:57:38 samsung-romano mtp-probe: checking bus 3, device 3: 
"/sys/devices/pci:00/:00:1c.4/:04:00.0/usb3/3-2"
  SYS: Oct 18 13:57:38 samsung-romano mtp-probe: bus: 3, device: 3 was not an 
MTP device
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.834382] scsi 7:0:0:0: 
Direct-Access USB  Flash Disk   1100 PQ: 0 ANSI: 0 CCS
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.835894] sd 7:0:0:0: 
Attached scsi generic sg3 type 0
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.836227] sd 7:0:0:0: [sdc] 
3915776 512-byte logical blocks: (2.00 GB/1.86 GiB)
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.836910] sd 7:0:0:0: [sdc] 
Write Protect is off
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.836926] sd 7:0:0:0: [sdc] 
Mode Sense: 43 00 00 00
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.837665] sd 7:0:0:0: [sdc] 
No Caching mode page present
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.837676] sd 7:0:0:0: [sdc] 
Assuming drive cache: write through
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.843552] sd 7:0:0:0: [sdc] 
No Caching mode page present
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.843562] sd 7:0:0:0: [sdc] 
Assuming drive cache: write through
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.844609]  sdc: sdc1
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.846982] sd 7:0:0:0: [sdc] 
No Caching mode page present
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.846990] sd 7:0:0:0: [sdc] 
Assuming drive cache: write through
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.846997] sd 7:0:0:0: [sdc] 
Attached SCSI removable disk

  But after that nothing happens. I checked the dconf variables as per
  https://help.ubuntu.com/community/Mount/USB but it's all correctly
  set. I can mount the disk by hand:

  % sudo mount /dev/sdc1 /mnt
  % mount | grep mnt
  /dev/sdc1 on /mnt type vfat (rw)

  ...and it works ok.

  Add: using from command line udisks works, too:

  (0)samsung-romano:~% udisks --mount /dev/sdc1
  Mounted /org/freedesktop/UDisks/devices/sdc1 at /media/PENDRIVE

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

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

[Desktop-packages] [Bug 1129818] Re: Yelp cannot find man page anymore

[Ivan Lucchese]

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

** This bug has been marked a duplicate of bug 952516
   man:[command] not working as expected

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

Title:
  Yelp cannot find man page anymore

Status in “yelp” package in Ubuntu:
  Confirmed

Bug description:
  Before migrating to Ubuntu Precise LTS, I was running Ubuntu Maverick.
  On Ubuntu Maverick, typing the name of a command which was given a man
  page, opened than manpage. On Ubuntu Precise, it does not work any
  more.

  The same if in the search field, I type `man:`.

  Finally, Yelp is able to find the man page only if it was requested to
  from a command line, like in `yelp man:`.

  I using Yelp a lot on Ubuntu Maverick, and I'm not using it any more
  on Ubuntu Precise, due to that it may tell you a documentation on a
  topic does not exist, while it exists.

  I also sometime get errors about XML or XSLT, don't remember, but that
  will be for another but report.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: yelp 3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-37.58-generic-pae 3.2.35
  Uname: Linux 3.2.0-37-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: i386
  CheckboxSubmission: 9b39dc487a858b4cfa15c3a2f5fa50d5
  CheckboxSystem: d00f84de8a555815fa1c4660280da308
  Date: Tue Feb 19 06:40:16 2013
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: yelp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1247948] Re: setting items should have a fix order

[Thibaut Brandscheid]

>  The issue you are reporting is an upstream one...
I'm sorry, but sending a bug report to GNOME is like sending something to 
/dev/null - it's useless (jep, it's pure frustration here).

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

Title:
  setting items should have a fix order

Status in Ayatana Design:
  New
Status in “gnome-control-center” package in Ubuntu:
  Confirmed

Bug description:
  The current system settings icon order is alphabetical.

  Problem 1:
  Not the most important items are displayed at first in every row. For example 
in the  'Hardware' category (English version), 'Bluetooth' is the first item, 
but it should be IMHO 'Diesplays'.

  Problem 2:
  Sorting the icons alphabetical results in having the icons on different 
places depending on the  language the system currently uses -> pretty bad when 
supporting other people through the phone...

  It would be much better to give the icons a fixed position. This would
  improve the system settings user experience, because the important
  buttons would be faster accessible.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu46
  ProcVersionSignature: Ubuntu 3.12.0-1.3-generic 3.12.0-rc7
  Uname: Linux 3.12.0-1-generic x86_64
  ApportVersion: 2.12.6-0ubuntu1
  Architecture: amd64
  Date: Mon Nov  4 20:24:54 2013
  InstallationDate: Installed on 2013-10-21 (14 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20131021.1)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131023.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1247948/+subscriptions

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

[Desktop-packages] [Bug 1231778] Re: wifi not working on Saucy Salamander

[Tyler Hicks]

** Description changed:

+ [Impact]
+ 
+ On older kernels that are missing certain AppArmor patches related to
+ AppArmor D-Bus mediation, the presence of dbus rules in the binary
+ AppArmor policy will result in policy load failures and, as a result,
+ applications may run unconfined. On newer kernels that are missing the
+ same patches mentioned above, the policy load will succeed but the dbus
+ rules will be quietly ignored.
+ 
+ [Test Case]
+ 
+ * Install older, unpatched mainline kernel (such as
+ 3.1.10-030110-generic)
+ 
+ * Install newer, unpatched mainline kernel (such as
+ 3.12.0-031200-generic)
+ 
+ * Bad test results on the mainline 3.1.10 kernel:
+ $ echo "/t { dbus, }" | sudo apparmor_parser -r
+ Cache read/write disabled: /sys/kernel/security/apparmor/features interface 
file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
+ Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
+ apparmor_parser: Unable to replace "/t".  Profile doesn't conform to protocol
+ 
+ * Good test on the mainline 3.1.10 kernel with a patched apparmor_parser:
+ $ echo "/t { dbus, }" | sudo apparmor_parser -r
+ Cache read/write disabled: /sys/kernel/security/apparmor/features interface 
file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
+ Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
+ Warning from stdin (stdin line 2): profile /t dbus rules not enforced
+ 
+ * Bad test results on the mainline 3.12.0 kernel:
+ $ echo "/t { dbus, }" | sudo apparmor_parser -r
+ Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
+ 
+ * Good test results on the mainline 3.12.0 kernel with a patched 
apparmor_parser:
+ $ echo "/t { dbus, }" | sudo apparmor_parser -r
+ Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
+ Warning from stdin (stdin line 2): profile /t dbus rules not enforced
+ 
+ * Good test results on the Ubuntu 3.11.0-12-generic kernel with or without a 
patched apparmor_parser:
+ $ echo "/t { dbus, }" | sudo apparmor_parser -r
+ Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
+ 
+ [Regression Potential]
+ 
+ * The regression potential is minor because the fix is small and easy to
+ test
+ 
+ [Original Bug Report]
+ 
+ Note that apparmor_parser warns that the dbus rule(s) will not be
+ enforced and then loads the binary policy without any dbus rules.
+ 
  Lubuntu 13.10 installed from daily image have wifi not working, even
  with BT disabled.
  
  confirmed by stuw on IRC at Sun Sep 22
  15:40 < stuw> iz1glg, I saw similar problem, but I don't know the reason and 
solution.

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

Title:
  wifi not working on Saucy Salamander

Status in Enablement project for the Toshiba AC100 NetBook:
  New
Status in AppArmor Linux application security framework:
  In Progress
Status in “apparmor” package in Ubuntu:
  Triaged
Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  On older kernels that are missing certain AppArmor patches related to
  AppArmor D-Bus mediation, the presence of dbus rules in the binary
  AppArmor policy will result in policy load failures and, as a result,
  applications may run unconfined. On newer kernels that are missing the
  same patches mentioned above, the policy load will succeed but the
  dbus rules will be quietly ignored.

  [Test Case]

  * Install older, unpatched mainline kernel (such as
  3.1.10-030110-generic)

  * Install newer, unpatched mainline kernel (such as
  3.12.0-031200-generic)

  * Bad test results on the mainline 3.1.10 kernel:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Cache read/write disabled: /sys/kernel/security/apparmor/features interface 
file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
  apparmor_parser: Unable to replace "/t".  Profile doesn't conform to protocol

  * Good test on the mainline 3.1.10 kernel with a patched apparmor_parser:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Cache read/write disabled: /sys/kernel/security/apparmor/features interface 
file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-complain via stdin
  Warning from stdin (stdin line 2): profile /t dbus rules not enforced

  * Bad test results on the mainline 3.12.0 kernel:
  $ echo "/t { dbus, }" | sudo apparmor_parser -r
  Warning from stdin (line 1): apparmor_parser: cannot use or update cache, 
disable, or force-compla

[Desktop-packages] [Bug 1247990] [NEW] dbus: Fix endianness bug in Frequency and Signal properties

[Adam Smith]

Public bug reported:

Please include the attached patch in the next update to wpasupplicant in
Ubuntu 12.04 (Precise).

The patch is based on this upstream commit
http://w1.fi/gitweb/gitweb.cgi?p=hostap-1.git;a=commitdiff;h=42f93a9a0f1858ba8492a1349515624965a64e34;hp=5045a668201f1027dbcc91bd8d092bbcee15a2e3

The version of wpasupplicant currently in precise (and oneiric had the
same problem) has the following bug:

To reproduce:

1. connect to a wireless network by clicking on the name in the applet.
2. check that the connection works.
3. see that there is no network listed on "Wireless Networks" in the applet. 
(Although the "Disconnect" words are there and functional.)
4. see that the signal strength is apparantly empty on the applet icon. (Yet 
the signal strength is actually quit strong.)
5. check nmcli command and see that signal strength always shows 100 and 
frequency 0.

Applying the patch to wpasupplicant 0.7.3-6ubuntu2.1 fixes the problem.
Before finding this patch I've had to work around the problem by
installing wicd.

Thanks

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


** Tags: patch powerpc ppc precise

** Patch added: "diff.txt"
   https://bugs.launchpad.net/bugs/1247990/+attachment/3900205/+files/diff.txt

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

Title:
  dbus: Fix endianness bug in Frequency and Signal properties

Status in “wpasupplicant” package in Ubuntu:
  New

Bug description:
  Please include the attached patch in the next update to wpasupplicant
  in Ubuntu 12.04 (Precise).

  The patch is based on this upstream commit
  
http://w1.fi/gitweb/gitweb.cgi?p=hostap-1.git;a=commitdiff;h=42f93a9a0f1858ba8492a1349515624965a64e34;hp=5045a668201f1027dbcc91bd8d092bbcee15a2e3

  The version of wpasupplicant currently in precise (and oneiric had the
  same problem) has the following bug:

  To reproduce:

  1. connect to a wireless network by clicking on the name in the applet.
  2. check that the connection works.
  3. see that there is no network listed on "Wireless Networks" in the applet. 
(Although the "Disconnect" words are there and functional.)
  4. see that the signal strength is apparantly empty on the applet icon. (Yet 
the signal strength is actually quit strong.)
  5. check nmcli command and see that signal strength always shows 100 and 
frequency 0.

  Applying the patch to wpasupplicant 0.7.3-6ubuntu2.1 fixes the
  problem.  Before finding this patch I've had to work around the
  problem by installing wicd.

  Thanks

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

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

[Desktop-packages] [Bug 1129818] Re: Yelp cannot find man page anymore

[Launchpad Bug Tracker]

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

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

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

Title:
  Yelp cannot find man page anymore

Status in “yelp” package in Ubuntu:
  Confirmed

Bug description:
  Before migrating to Ubuntu Precise LTS, I was running Ubuntu Maverick.
  On Ubuntu Maverick, typing the name of a command which was given a man
  page, opened than manpage. On Ubuntu Precise, it does not work any
  more.

  The same if in the search field, I type `man:`.

  Finally, Yelp is able to find the man page only if it was requested to
  from a command line, like in `yelp man:`.

  I using Yelp a lot on Ubuntu Maverick, and I'm not using it any more
  on Ubuntu Precise, due to that it may tell you a documentation on a
  topic does not exist, while it exists.

  I also sometime get errors about XML or XSLT, don't remember, but that
  will be for another but report.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: yelp 3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-37.58-generic-pae 3.2.35
  Uname: Linux 3.2.0-37-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: i386
  CheckboxSubmission: 9b39dc487a858b4cfa15c3a2f5fa50d5
  CheckboxSystem: d00f84de8a555815fa1c4660280da308
  Date: Tue Feb 19 06:40:16 2013
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: yelp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 992767] Re: Evince does not show comments from PDFs generated by LibreOffice

[Simos Xenitellis]

I also want to add https://bugs.freedesktop.org/show_bug.cgi?id=60126 to
this report but cannot figure it out. If someone can figure it out,
please add it.

>From a comment above: 
"The problem with both the LibreOffice and Latex generated PDF files seems to be
that they have a very small or zero volume /Rect field. The annotations in the
attached test case are in fact there. There is a very small area where hovering
the mouse shows the first comment.

Additionally, the annotations do not contain a /Popup field, which means
clicking them does nothing."

** Bug watch added: freedesktop.org Bugzilla #60126
   https://bugs.freedesktop.org/show_bug.cgi?id=60126

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

Title:
  Evince does not show comments from PDFs generated by LibreOffice

Status in Evince document viewer:
  Unknown
Status in “evince” package in Ubuntu:
  Confirmed

Bug description:
  Evince doesn't show comments which are highlighted. Example attached.
  First comment (yellow backgroudn) is invisible, second comment is
  visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: evince 2.32.0-0ubuntu12.4
  ProcVersionSignature: Ubuntu 2.6.38-14.58-generic 2.6.38.8
  Uname: Linux 2.6.38-14-generic x86_64
  Architecture: amd64
  Date: Tue May  1 19:58:34 2012
  ExecutablePath: /usr/bin/evince
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  ProcCmdline_: BOOT_IMAGE=/vmlinuz-2.6.38-14-generic 
root=UUID=6d9bf616-f5bf-4107-9297-2e1ae230cb11 ro quiet splash vt.handoff=7
  ProcEnviron:
   LANGUAGE=de_DE:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature_: Ubuntu 2.6.38-14.58-generic 2.6.38.8
  SourcePackage: evince
  UpgradeStatus: Upgraded to natty on 2011-11-02 (181 days ago)

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

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

[Desktop-packages] [Bug 992767] Re: Evince does not show highlighted comments

[Simos Xenitellis]

** Bug watch added: GNOME Bug Tracker #685334
   https://bugzilla.gnome.org/show_bug.cgi?id=685334

** Also affects: evince via
   https://bugzilla.gnome.org/show_bug.cgi?id=685334
   Importance: Unknown
   Status: Unknown

** Summary changed:

- Evince does not show highlighted comments 
+ Evince does not show comments from PDFs generated by LibreOffice

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

Title:
  Evince does not show comments from PDFs generated by LibreOffice

Status in Evince document viewer:
  Unknown
Status in “evince” package in Ubuntu:
  Confirmed

Bug description:
  Evince doesn't show comments which are highlighted. Example attached.
  First comment (yellow backgroudn) is invisible, second comment is
  visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: evince 2.32.0-0ubuntu12.4
  ProcVersionSignature: Ubuntu 2.6.38-14.58-generic 2.6.38.8
  Uname: Linux 2.6.38-14-generic x86_64
  Architecture: amd64
  Date: Tue May  1 19:58:34 2012
  ExecutablePath: /usr/bin/evince
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  ProcCmdline_: BOOT_IMAGE=/vmlinuz-2.6.38-14-generic 
root=UUID=6d9bf616-f5bf-4107-9297-2e1ae230cb11 ro quiet splash vt.handoff=7
  ProcEnviron:
   LANGUAGE=de_DE:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature_: Ubuntu 2.6.38-14.58-generic 2.6.38.8
  SourcePackage: evince
  UpgradeStatus: Upgraded to natty on 2011-11-02 (181 days ago)

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

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

[Desktop-packages] [Bug 1210785] Re: wpa_supplicant crashed with SIGSEGV

[Saikrishna Arcot]

See https://wiki.ubuntu.com/DebuggingProgramCrash#Debug_Symbol_Packages.

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

Title:
  wpa_supplicant crashed with SIGSEGV

Status in “wpa” package in Ubuntu:
  Triaged

Bug description:
  wpa_supplicant crashed with SIGSEGV

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: wpasupplicant 1.0-3ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4
  Uname: Linux 3.11.0-1-generic i686
  ApportVersion: 2.12-0ubuntu3
  Architecture: i386
  CrashCounter: 1
  Date: Sat Aug 10 16:58:28 2013
  ExecutablePath: /sbin/wpa_supplicant
  InstallationDate: Installed on 2013-08-06 (4 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130730)
  MarkForUpload: True
  ProcCmdline: /sbin/wpa_supplicant -B -P 
/run/sendsigs.omit.d/wpasupplicant.pid -u -s -O /var/run/wpa_supplicant
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x81028d0: mov0x4(%esi),%edx
   PC (0x081028d0) ok
   source "0x4(%esi)" (0x012d) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: wpa
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: wpa_supplicant crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1210785] Re: wpa_supplicant crashed with SIGSEGV

[nh2]

>From my error log (does anybody know how I can get debugging symbols for
wpa_supplicant?):

Disassembly:
 => 0x8102980:  mov(%edi),%ebx
0x8102982:  je 0x810291b
0x8102984:  mov%esi,0x20(%esp)
0x8102988:  mov%eax,%esi
0x810298a:  mov%ebp,0x1c(%esp)
0x810298e:  mov%edi,%ebp
0x8102990:  mov0x94(%esp),%edi
0x8102997:  jmp0x81029b3
0x8102999:  lea0x0(%esi,%eiz,1),%esi
0x81029a0:  add$0x1,%esi
0x81029a3:  mov(%ebx),%eax
0x81029a5:  cmp%ebx,0x1c(%esp)
0x81029a9:  je 0x810291b
0x81029af:  mov%ebx,%ebp
0x81029b1:  mov%eax,%ebx
0x81029b3:  cmp0x7c(%ebp),%edi
InstallationDate: Installed on 2011-04-28 (921 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MarkForUpload: True
Package: wpasupplicant 1.0-3ubuntu2
PackageArchitecture: i386
Registers:
 eax0x0 0
 ecx0x0 0
 edx0x7fa55c32  2141543474
 ebx0x8835620   142824992
 esp0x7fa55bd0  0x7fa55bd0
 ebp0x8831e78   0x8831e78
 esi0x8831e70   142810736
 edi0xd089089   218665097
 eip0x8102980   0x8102980
 eflags 0x210293[ CF AF SF IF RF ID ]
 cs 0x73115
InstallationDate: Installed on 2011-04-28 (921 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MarkForUpload: True
Package: wpasupplicant 1.0-3ubuntu2
PackageArchitecture: i386
Registers:
 eax0x0 0
PackageArchitecture: i386
Registers:
 eax0x0 0
 ecx0x0 0
 edx0x7fa55c32  2141543474
 ebx0x8835620   142824992
 esp0x7fa55bd0  0x7fa55bd0
 ebp0x8831e78   0x8831e78
 esi0x8831e70   142810736
 edi0xd089089   218665097
 eip0x8102980   0x8102980
 eflags 0x210293[ CF AF SF IF RF ID ]
 cs 0x73115
 ss 0x7b123
 ds 0x7b123
 es 0x7b123
 fs 0x0 0
 gs 0x3351
SegvAnalysis:
 Segfault happened at: 0x8102980:   mov(%edi),%ebx
 PC (0x08102980) ok
 source "(%edi)" (0x0d089089) not located in a known VMA region (needed 
readable region)!
 destination "%ebx" ok
SegvReason: reading unknown VMA
SourcePackage: wpa
Stacktrace:
 #0  0x08102980 in ?? ()
 No symbol table info available.
 #1  0x08059965 in ?? ()
 No symbol table info available.
 #2  0x0807bdc9 in ?? ()
 No symbol table info available.
 #3  0x08074039 in ?? ()
 No symbol table info available.
 #4  0x0812482a in ?? ()
 No symbol table info available.
 #5  0x08136847 in ?? ()
 No symbol table info available.
 #6  0x77727f3b in nl_recvmsgs_report () from /lib/i386-linux-gnu/libnl-3.so.200
 No symbol table info available.
 #7  0x777282c3 in nl_recvmsgs () from /lib/i386-linux-gnu/libnl-3.so.200
 No symbol table info available.
 #8  0x0812accd in ?? ()
 No symbol table info available.
 #9  0x0805a900 in ?? ()
 No symbol table info available.
 #10 0x0805af82 in ?? ()
 No symbol table info available.
 #11 0x08120a8e in ?? ()
 No symbol table info available.
 #12 0x08052a6d in ?? ()
 No symbol table info available.
 #13 0x77316905 in __libc_start_main (main=0x8052750, argc=8, 
ubp_av=0x7fa56704, init=0x813d050, fini=0x813d0c0, rtld_fini=0x7775f5f0 
<_dl_fini>, stack_end=0x7fa566fc) at libc-start.c:260
 result = 
 unwind_buf = {cancel_jmp_buf = {{jmp_buf = {2001391616, 0, 0, 0, 
-2146122782, -1475762189}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x8, 
0x8052aba}, data = {prev = 0x0, cleanup = 0x0, canceltype = 8}}}
 not_first_call = 
 #14 0x08052adb in ?? ()

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

Title:
  wpa_supplicant crashed with SIGSEGV

Status in “wpa” package in Ubuntu:
  Triaged

Bug description:
  wpa_supplicant crashed with SIGSEGV

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: wpasupplicant 1.0-3ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4
  Uname: Linux 3.11.0-1-generic i686
  ApportVersion: 2.12-0ubuntu3
  Architecture: i386
  CrashCounter: 1
  Date: Sat Aug 10 16:58:28 2013
  ExecutablePath: /sbin/wpa_supplicant
  InstallationDate: Installed on 2013-08-06 (4 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130730)
  MarkForUpload: True
  ProcCmdline: /sbin/wpa_supplicant -B -P 
/run/sendsigs.omit.d/wpasupplicant.pid -u -s -O /var/run/wpa_supplicant
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x81028d0: mov0x4(%esi),%edx
   PC (0x081028d0) ok
   source "0x4(%esi)" (0x012d) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11

[Desktop-packages] [Bug 984785] Re: .goutputstream files polluting $HOME

[Brian Murray]

If there is anybody interested in seeing this fixed in Precise and
willing to perform SRU verification as detailed at
http://wiki.ubuntu.com/StableReleaseUpdates, please add a comment to
this bug.  This way I'll know whether or not there is interest in seeing
this fixed.

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

Title:
  .goutputstream files polluting $HOME

Status in The "G" Library - GLib:
  Fix Released
Status in Light Display Manager:
  Fix Released
Status in X.Org X server:
  New
Status in “glib2.0” package in Ubuntu:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Invalid
Status in “glib2.0” source package in Precise:
  Triaged
Status in “lightdm” source package in Precise:
  Invalid

Bug description:
  .goutputstream files polluting $HOME.
  Which software or operation is creating these and why?

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xauth 1:1.0.6-1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia & ati
  ApportVersion: 2.0.1-0ubuntu4
  Architecture: amd64
  Date: Wed Apr 18 13:29:31 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin"
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xauth
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 984785] Re: .goutputstream files polluting $HOME

[Brian Murray]

The commit mentioned by seb128 in comment #102 has been committed to
glib2.0 in Saucy, so that bug task will be marked as Fix Released.
However, it should probably also be fixed in Ubuntu 12.04 (Precise).

** Changed in: glib2.0 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  .goutputstream files polluting $HOME

Status in The "G" Library - GLib:
  Fix Released
Status in Light Display Manager:
  Fix Released
Status in X.Org X server:
  New
Status in “glib2.0” package in Ubuntu:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Invalid
Status in “glib2.0” source package in Precise:
  Triaged
Status in “lightdm” source package in Precise:
  Invalid

Bug description:
  .goutputstream files polluting $HOME.
  Which software or operation is creating these and why?

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xauth 1:1.0.6-1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia & ati
  ApportVersion: 2.0.1-0ubuntu4
  Architecture: amd64
  Date: Wed Apr 18 13:29:31 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin"
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xauth
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1210785] Re: wpa_supplicant crashed with SIGSEGV

[nh2]

Network controller: Qualcomm Atheros AR93xx Wireless Network Adapter
(rev 01) - using ath9k wifi driver.

On my Chromebook (Samsung CR-48), this seems to happen in the running
system (not from suspend). Ubuntu 13.10.

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

Title:
  wpa_supplicant crashed with SIGSEGV

Status in “wpa” package in Ubuntu:
  Triaged

Bug description:
  wpa_supplicant crashed with SIGSEGV

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: wpasupplicant 1.0-3ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4
  Uname: Linux 3.11.0-1-generic i686
  ApportVersion: 2.12-0ubuntu3
  Architecture: i386
  CrashCounter: 1
  Date: Sat Aug 10 16:58:28 2013
  ExecutablePath: /sbin/wpa_supplicant
  InstallationDate: Installed on 2013-08-06 (4 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130730)
  MarkForUpload: True
  ProcCmdline: /sbin/wpa_supplicant -B -P 
/run/sendsigs.omit.d/wpasupplicant.pid -u -s -O /var/run/wpa_supplicant
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x81028d0: mov0x4(%esi),%edx
   PC (0x081028d0) ok
   source "0x4(%esi)" (0x012d) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: wpa
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: wpa_supplicant crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1243735] Re: Glitches in text rendering

[Thaddäus Tintenfisch]

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

Please read the comments in the linked launchpad report. On top of that,
take a look at the upstream bug report.

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

Title:
  Glitches in text rendering

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

Bug description:
  This happens since upgrading to 13.10. With 13.04 I did not have this
  problem.

  I notice glitches in the text rendering (randomly, one character in
  many will be rendered as noise). This happens in all applications
  (xterm, Mozilla, etc). Other that that I observe no crashes or
  problems.

  Attached is a snapshot that shows the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-core 2:1.14.3-3ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,snap,gnomecompat,compiztoolbox,resize,move,mousepoll,grid,imgpng,vpswitch,place,regex,animation,workarounds,unitymtgrabhandles,wall,expo,ezoom,fade,session,scale,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Oct 23 16:22:59 2013
  DistUpgraded: 2013-10-21 11:57:38,259 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.141+bdcom, 3.11.0-12-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.8.0-31-generic, x86_64: installed
   virtualbox, 4.2.16, 3.11.0-12-generic, x86_64: installed
   virtualbox, 4.2.16, 3.8.0-31-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:02bc]
 Subsystem: Dell Device [1028:02bc]
  InstallationDate: Installed on 2013-05-20 (156 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. Vostro 1520
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=5326adab-e228-4770-90ca-3c0261353884 ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to saucy on 2013-10-21 (2 days ago)
  dmi.bios.date: 10/27/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0T816J
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd10/27/2009:svnDellInc.:pnVostro1520:pvrNull:rvnDellInc.:rn0T816J:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.name: Vostro 1520
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  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-3ubuntu2
  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: Tue Oct 22 10:31:47 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id9079 
   vendor AUO
  xserver.version: 2:1.14.3-3ubuntu2

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

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

[Desktop-packages] [Bug 784435] Re: Launcher - Dragging and dropping a file directly on to the Thunderbird or Evolution Launcher icons should open a new email with the file attached

[Adolfo Jayme Barrientos]

** Changed in: evolution (Ubuntu)
   Status: Invalid => Triaged

** Changed in: thunderbird (Ubuntu)
   Status: Invalid => Triaged

** Changed in: unity (Ubuntu)
   Status: Invalid => Triaged

** Changed in: unity
   Status: Invalid => Confirmed

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

Title:
  Launcher - Dragging and dropping a file directly on to the Thunderbird
  or Evolution Launcher icons should open a new email with the file
  attached

Status in Ayatana Design:
  Fix Committed
Status in Unity:
  Confirmed
Status in “evolution” package in Ubuntu:
  Triaged
Status in “thunderbird” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  Desired functionality:

  Dragging and dropping a file directly on to the Thunderbird or
  Evolution Launcher icons should open a new email with the file
  attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/784435/+subscriptions

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

[Desktop-packages] [Bug 1247974] Re: network don't work after longtime suspend mode

[Thaddäus Tintenfisch]

Duplicate of bug 1184262.

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

Title:
  network don't work after longtime suspend mode

Status in “network-manager” package in Ubuntu:
  New

Bug description:
  when my system in suspend mode for long time (1 hour or more) -
  network connection is down. Only reboot saving.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.12.0-1.3-generic 3.12.0-rc7
  Uname: Linux 3.12.0-1-generic i686
  ApportVersion: 2.12.6-0ubuntu1
  Architecture: i386
  Date: Mon Nov  4 23:22:26 2013
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-07-26 (101 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130726)
  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.100  
metric 9
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2013-10-08T20:01:22.891003
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.4connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1247974/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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 alt+shift, ctrl+shift, etc.

[bademux]

Tested with gnome-control-center 1:3.6.3-0ubuntu45.1, gnome-settings-daemon 
3.8.5-0ubuntu11.1.
-Can't switch languages in Lock Screen
-CapsLock warning at LockSreen while CapsLock is used as kdb switcher
-Led blink while switching input langs (CapsLock is used as kdb switcher)
-Super + Space doesn't work
-No settings for for CapsLock&Co ( http://i.stack.imgur.com/ACsI1.png )

It is the worst decision to radically update Unity7 along with
Unity8\XMir active development...

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

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in Gnome Settings Daemon:
  Invalid
Status in Ubuntu GNOME:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” source package in Saucy:
  Triaged

Bug description:
  A PPA which should provide some relief for this issue is available at
  https://launchpad.net/~attente/+archive/1218322. There still remain
  issues regarding keyboard shortcuts though. To install:

  sudo add-apt-repository ppa:attente/1218322
  sudo apt-get update
  sudo apt-get upgrade

  === gnome-control-center ===

  Impact: the UI to change the layout switching keys doesn't work

  Test case:
  - open gnome-control-center's text input settings
  - click on the "next layout key" entry
  - try entering a key combinaison (e.g ctrl-space)
  -> the UI should reflect the new keys

  Regression potential: that UI was not working before, it should only
  be an improvement (some key combos are not working as expected, that's
  another issue and shouldn't be mixed with this one)

  === gnome-settings-daemon ===

  Impact: attempting to change keyboard layouts using only modifier keys
  doesn't work

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - press and release ctrl+left shift
  -> the current input source should change

  Regression potential: The input switching shortcut might capture other
  non-modifier shortcuts, but users will need to consider this when
  choosing their switching shortcut anyways. For users this bug affects,
  this represents a working solution for a critical bug.

  --

  Test results for different keyboard layout change hotkeys may be
  viewed and added in the Google Docs table, created by Norbert
  
(https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE&usp=sharing).

  --

  Separate bug reports for individual layout switching hotkey
  combinations:

  Super+Space and Shift+Super+Space:
     * Unity greeter (bug 1245137);
     * Unity session (bug 1245136);
     * lock screen - gnome-screensaver (bug 1245138, bug 1245256);
     * ubiquity installer (bug 1242572).

  Alt+Shift:
     * Unity greeter (bug 1245258)
     * Can't set keyboard layout change to Alt+Shift (bug 1245926)

  Ctrl+Shift:
     * lock screen - gnome-screensaver (bug 1245270)
     * Unity greeter (bug 1245268)
     * Can't set keyboard layout change to Ctrl+Shift (bug 1245991)
     * If keyboard layout switching hotkey is set to Ctrl+Shift, Ctrl+Shift+C/V 
are not working in gnome-terminal (bug 1246656)

  Shift+Shift:
     * Can't set keyboard layout change to Shift+Shift (bug 1245272)
     * lock screen - gnome-screensaver (bug 1245278)
     * Unity greeter (bug 1245280)

  Bugs which belong to keyboard layout switching:
     * Hotkeys not functional in non-latin keyboard layout in 13.10 (bug 
1226962)
     * Keyboard Layout Options window is missed in gnome-control-center 
keyboard (bug 1245064)
     * Unable to set keyboard LED to show alternative layout in 
gnome-control-center keyboard in Saucy (bug 1245188)
     * Unable to set Miscellaneous compatibility options in 
gnome-control-center keyboard in Saucy (bug 1245199)
     * Keyboard shortcut for changing keyboard layout does not work on lock 
screen (bug 1244548)
     * [FFe] indicator-keyboard not working under greeter (bug 1228207)
     * Lost ability to remap Caps Lock to Ctrl (bug 1215826)
     * gnome-control-center keyboard no longer has way to modify caps lock key 
behavior (bug 1224575)
     * Pressing Caps Lock toggles LED even when mapped to another key (bug 
1221403)
 * Switching layout turns off NumLock (bug 1247668)

  --

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

[Desktop-packages] [Bug 1247974] [NEW] network don't work after longtime suspend mode

[denkin]

Public bug reported:

when my system in suspend mode for long time (1 hour or more) - network
connection is down. Only reboot saving.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: network-manager 0.9.8.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.12.0-1.3-generic 3.12.0-rc7
Uname: Linux 3.12.0-1-generic i686
ApportVersion: 2.12.6-0ubuntu1
Architecture: i386
Date: Mon Nov  4 23:22:26 2013
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2013-07-26 (101 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130726)
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.100  metric 9
MarkForUpload: True
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2013-10-08T20:01:22.891003
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   
 wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
 eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   WIFI  
 WWAN-HARDWARE   WWAN  
 running 0.9.8.4connected   enabled   enabled 
enabledenabled disabled

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


** Tags: apport-bug i386 package-from-proposed trusty

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

Title:
  network don't work after longtime suspend mode

Status in “network-manager” package in Ubuntu:
  New

Bug description:
  when my system in suspend mode for long time (1 hour or more) -
  network connection is down. Only reboot saving.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.12.0-1.3-generic 3.12.0-rc7
  Uname: Linux 3.12.0-1-generic i686
  ApportVersion: 2.12.6-0ubuntu1
  Architecture: i386
  Date: Mon Nov  4 23:22:26 2013
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-07-26 (101 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130726)
  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.100  
metric 9
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2013-10-08T20:01:22.891003
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.4connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1247974/+subscriptions

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

[Desktop-packages] [Bug 706097] Invitation to connect on LinkedIn

[srivest]

LinkedIn



Bug,

I'd like to include you in my network to share updates and stay in
touch.

- Serge

Serge Rivest
Web Developer / Linux Systems Administrator at WebdevDural
Tasmania, Australia

Confirm that you know Serge Rivest:
https://www.linkedin.com/e/gtzdyn-hnm7sdz9-3v/isd/17798532003/-6UIih9h/?hs=false&tok=2V6sKC6nsyTBY1

--
You are receiving Invitation to Connect emails. Click to unsubscribe:
http://www.linkedin.com/e/gtzdyn-hnm7sdz9-3v/zr0b4Glh7dla4LItFgDR-PxhKIypHBzLvUOMgFq/goo/706097%40bugs%2Elaunchpad%2Enet/20061/I5870546330_1/?hs=false&tok=3U36dcbLoyTBY1

(c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA
94043, USA.

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

Title:
  [Realtek ALC269] ALSA test tone not correctly played back

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

Bug description:
  Sound does not work after a reboot (from windows or ubuntu). To fix, I
  need to shutdown the system (not reboot) and boot again.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: alsa-base 1.0.23+dfsg-1ubuntu4
  ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
  Uname: Linux 2.6.35-24-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
 Subdevices: 0/1
 Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  srivest1569 F pulseaudio
   /dev/snd/pcmC0D0p:   srivest1569 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf7eb8000 irq 43'
 Mixer name : 'Realtek ALC269'
 Components : 'HDA:10ec0269,1043834a,0014'
 Controls  : 10
 Simple ctrls  : 6
  Date: Fri Jan 21 22:31:35 2011
  InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 
(20101007)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SelectedCard: 0 Intel HDA-Intel - HDA Intel
  SourcePackage: alsa-driver
  Symptom: audio
  Title: [Realtek ALC269] ALSA test tone not correctly played back
  dmi.bios.date: 10/14/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1104
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1000HE
  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.:bvr1104:bd10/14/2009:svnASUSTeKComputerINC.:pn1000HE:pvrx.x:rvnASUSTeKComputerINC.:rn1000HE:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1000HE
  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/alsa-driver/+bug/706097/+subscriptions

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

[Desktop-packages] [Bug 1241796] Re: USB GSM-Modem ID 12d1:1506 doesn't hold the connection

[Jörg Frings-Fürst]

** Changed in: modemmanager (Ubuntu)
   Status: In Progress => 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/1241796

Title:
  USB GSM-Modem ID 12d1:1506 doesn't hold the connection

Status in Banshee Music Player:
  Invalid
Status in The Mozilla Firefox Browser:
  Invalid
Status in The Rhythmbox Music Management Application:
  Invalid
Status in Mozilla Thunderbird Mail and News:
  Invalid
Status in Ubuntu One Client:
  Invalid
Status in “modemmanager” package in Ubuntu:
  Confirmed

Bug description:
  When I have internet-connection via mobile broadband (that was configured by 
command 'sudo pppconfig'), USC think i didn't  connected. And not only USC - 
whole system don't think different.
  What happens in result:
  1) Can't install any app in USC

  What happens in other affected packages:
  2) Ubuntu One - do not synchronise
  3) Thunderbird - don't search new messages
  4) Firefox - always starts in Offline Mode
  5) Banshee - din't start synchronisation with Last.FM integration
  6) Rhythmbox - the same as Banshee

  I attached my settings, they have been configured via 'sudo pppconfig'
  and located at '/etc/ppp/peers/provider' file.

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

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

[Desktop-packages] [Bug 1241811] Re: USB disk not automatically mounted after upgrade to 13.10

[Romano Giannetti]

Tried right now --- this boot/login it  is working, and I have the
following in ~/.cache/upstart/gnome-settings-daemon.log

(gnome-settings-daemon:1896): color-plugin-WARNING **: failed to connect
to device: Failed to connect to missing device
/org/freedesktop/ColorManager/devices/cups_PDF

...and nothing more. (Is this file flushed all the time or I am supposed
to enter/exit the session?)

I have the saved file from yesterday (I suppose, it seems that file
there are rotated) when the automounting did not work. The content is
attached.

Hope this helps. I will try to check the log file when the problem
surfaces again.


** Attachment added: "~/.cache/upstart/gnome-settings-daemon.log.1 uncompressed"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1241811/+attachment/3900102/+files/gnome-settings-daemon.log

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

Title:
  USB disk not automatically mounted after upgrade to 13.10

Status in Ubuntu GNOME:
  New
Status in “nautilus” package in Ubuntu:
  Incomplete
Status in “nautilus-udisks” package in Ubuntu:
  Invalid

Bug description:
  Since the upgrade to 13.10, my laptop stopped mounting the USB devices
  (and SD cards too) automatically.

  Inserting the USB I have in the log:

  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.570340] usb 3-2: new 
high-speed USB device number 3 using xhci_hcd
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.593170] usb 3-2: New USB 
device found, idVendor=090c, idProduct=1000
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.593181] usb 3-2: New USB 
device strings: Mfr=1, Product=2, SerialNumber=3
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.593187] usb 3-2: Product: 
Flash Disk
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.593192] usb 3-2: 
Manufacturer: USB
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.593196] usb 3-2: 
SerialNumber: FBF1009232400790
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.593492] usb 3-2: ep 0x81 - 
rounding interval to 128 microframes, ep desc says 255 microframes
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.593501] usb 3-2: ep 0x2 - 
rounding interval to 128 microframes, ep desc says 255 microframes
  SYS: Oct 18 13:57:38 samsung-romano kernel: [  167.595232] scsi7 : 
usb-storage 3-2:1.0
  SYS: Oct 18 13:57:38 samsung-romano mtp-probe: checking bus 3, device 3: 
"/sys/devices/pci:00/:00:1c.4/:04:00.0/usb3/3-2"
  SYS: Oct 18 13:57:38 samsung-romano mtp-probe: bus: 3, device: 3 was not an 
MTP device
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.834382] scsi 7:0:0:0: 
Direct-Access USB  Flash Disk   1100 PQ: 0 ANSI: 0 CCS
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.835894] sd 7:0:0:0: 
Attached scsi generic sg3 type 0
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.836227] sd 7:0:0:0: [sdc] 
3915776 512-byte logical blocks: (2.00 GB/1.86 GiB)
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.836910] sd 7:0:0:0: [sdc] 
Write Protect is off
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.836926] sd 7:0:0:0: [sdc] 
Mode Sense: 43 00 00 00
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.837665] sd 7:0:0:0: [sdc] 
No Caching mode page present
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.837676] sd 7:0:0:0: [sdc] 
Assuming drive cache: write through
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.843552] sd 7:0:0:0: [sdc] 
No Caching mode page present
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.843562] sd 7:0:0:0: [sdc] 
Assuming drive cache: write through
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.844609]  sdc: sdc1
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.846982] sd 7:0:0:0: [sdc] 
No Caching mode page present
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.846990] sd 7:0:0:0: [sdc] 
Assuming drive cache: write through
  SYS: Oct 18 13:57:39 samsung-romano kernel: [  168.846997] sd 7:0:0:0: [sdc] 
Attached SCSI removable disk

  But after that nothing happens. I checked the dconf variables as per
  https://help.ubuntu.com/community/Mount/USB but it's all correctly
  set. I can mount the disk by hand:

  % sudo mount /dev/sdc1 /mnt
  % mount | grep mnt
  /dev/sdc1 on /mnt type vfat (rw)

  ...and it works ok.

  Add: using from command line udisks works, too:

  (0)samsung-romano:~% udisks --mount /dev/sdc1
  Mounted /org/freedesktop/UDisks/devices/sdc1 at /media/PENDRIVE

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

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

[Desktop-packages] [Bug 1245272] Re: Can't set keyboard layout change to Shift+Shift

[Sebastien Bacher]

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

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

Title:
  Can't set keyboard layout change to Shift+Shift

Status in “gnome-control-center” package in Ubuntu:
  Fix Released

Bug description:
  In Ubuntu 12.04 I was able to set keyboard layout switching shortcut to 
Shift+Shift.
  In Ubuntu 13.10 I can't set it from gnome-control-center keyboard.
  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu45
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Mon Oct 28 00:32:03 2013
  InstallationDate: Installed on 2013-10-20 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

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

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

[Desktop-packages] [Bug 1245926] Re: Can't set keyboard layout change to Alt+Shift

[Sebastien Bacher]

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

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

Title:
  Can't set keyboard layout change to Alt+Shift

Status in “gnome-control-center” package in Ubuntu:
  Fix Released

Bug description:
  In Ubuntu 12.04 I was able to set keyboard layout switching shortcut to 
Alt+Shift.
  In Ubuntu 13.10 I can't set it from gnome-control-center/Text Entry.

  And the default "Super + Space" combination does not work as well
  (this is bug 1245136).

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --
  --- 
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  InstallationDate: Installed on 2013-02-27 (244 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  NonfreeKernelModules: nvidia
  Package: gnome-control-center 1:3.6.3-0ubuntu44
  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-29 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

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

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

[Desktop-packages] [Bug 1247948] Re: setting items should have a fix order

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  setting items should have a fix order

Status in Ayatana Design:
  New
Status in “gnome-control-center” package in Ubuntu:
  Confirmed

Bug description:
  The current system settings icon order is alphabetical.

  Problem 1:
  Not the most important items are displayed at first in every row. For example 
in the  'Hardware' category (English version), 'Bluetooth' is the first item, 
but it should be IMHO 'Diesplays'.

  Problem 2:
  Sorting the icons alphabetical results in having the icons on different 
places depending on the  language the system currently uses -> pretty bad when 
supporting other people through the phone...

  It would be much better to give the icons a fixed position. This would
  improve the system settings user experience, because the important
  buttons would be faster accessible.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu46
  ProcVersionSignature: Ubuntu 3.12.0-1.3-generic 3.12.0-rc7
  Uname: Linux 3.12.0-1-generic x86_64
  ApportVersion: 2.12.6-0ubuntu1
  Architecture: amd64
  Date: Mon Nov  4 20:24:54 2013
  InstallationDate: Installed on 2013-10-21 (14 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20131021.1)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131023.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1247948/+subscriptions

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

[Desktop-packages] [Bug 1247719] Re: crackling, popping, clicking in playback to audigy2 surround51 device

[Forest]

speaker-test -c 6 -t wav -Dsurround51 produces clear test sounds; no
crackling.

I'm attaching the alsa-info.sh output.

$ pactl list
The program 'pactl' is currently not installed. You can install it by typing:
sudo apt-get install pulseaudio-utils

$ pactl stat
The program 'pactl' is currently not installed. You can install it by typing:
sudo apt-get install pulseaudio-utils

$ pulseaudio verbose log
The program 'pulseaudio' is currently not installed. You can install it by 
typing:
sudo apt-get install pulseaudio

(As I said, I'm not using PulseAudio.)


** Attachment added: "alsa-info.sh output"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1247719/+attachment/3900079/+files/alsa-info.txt

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

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

Title:
  crackling, popping, clicking in playback to audigy2 surround51 device

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

Bug description:
  After upgrading from Xubuntu 13.04 to 13.10, I hear lots of popping
  (aka crackle, click noises) during playback to my Audigy2 surround51
  device.  This was never a problem before the upgrade.  The noises do
  not show up if I use the card's default, front, or rear devices
  instead, but those leave me without surround sound, so they're no good
  for movie playback.

  The same problem shows up on the surround40 device.  I haven't tried
  the other surround* devices.

  I can reproduce problem in Totem or gst-launch playbin with an .asoundrc 
containing this:
  pcm.!default {
  type plug
  slave.pcm "surround51"
  }

  I can reproduce problem in Exaile with the custom sink pipeline set to
  "alsasink device=surround51" and no .asoundrc.

  I'm running the amd64 build of Xubuntu.

  My Audigy2 has the first alsa sound card slot, making it my default
  sound card.

  I am not using PulseAudio.

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

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

[Desktop-packages] [Bug 1193435] Re: right-click context menus behind window

[Mike]

I "upgraded" to 13.10 and haven't had this problem since.

On a related note, when am I going to learn to refuse upgrades and just
stick with fresh installs?

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

Title:
  right-click context menus behind window

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

Bug description:
  About once every-other week, the context menus from Chromium do not
  appear. This happens from left-clicking a bookmark folder in my
  toolbar, or right-clicking on a webpage. Nothing is displayed. If I
  un-maximize the window and right-click near the right edge, the menu
  is visible in the background. I can also see bookmark menus if they
  are at the extreme right of the application and hang off into the
  desktop background.

  When in this state, a right-click on the desktop also hides behind
  Chromium. But it overlays Firefox. Testing this is difficult since I
  can't interact with menus in the normal fashion.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: fglrx (not installed)
  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.2
  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: Fri Jun 21 11:57:27 2013
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices [AMD] nee ATI RV620 LE [Radeon HD 3450] [1002:95c5] 
(prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0342]
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120822.4)
  MachineType: Dell Inc. OptiPlex 960
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-48-generic 
root=UUID=138260dc-ec89-47b0-9c8c-42bfefa99f7d ro quiet splash vt.handoff=7
  SourcePackage: fglrx-installer
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0Y958C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd08/03/2010:svnDellInc.:pnOptiPlex960:pvr:rvnDellInc.:rn0Y958C:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 960
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.7.12-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.43-0ubuntu0.0.1
  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/fglrx-installer/+bug/1193435/+subscriptions

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

[Desktop-packages] [Bug 1245188] Re: Unable to set the physical keyboard LED to show an alternative layout

[Alberto Salvia Novella]

Since this bug is:

- Valid.
- Well described.
- Reported in the upstream bug tracker (GNOME).
- Ready to be worked on by a developer.

it's also triaged.

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

** Changed in: hundredpapercuts
   Status: Confirmed => Triaged

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

Title:
  Unable to set the physical keyboard LED to show an alternative layout

Status in GNOME Control Center:
  Unknown
Status in One Hundred Papercuts:
  Triaged
Status in Ubuntu GNOME:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Triaged

Bug description:
  **
   HOW TO REPRODUCE
  **

  - Go to "system configuration / keyboard", or "system configuration /
  text input".

  
   EXPECTED BEHAVIOUR
  

  - To be able to set the physical keyboard LED to show an alternative
  layout: "Caps Lock", "Num Lock" or "Scroll Lock".

  
   REAL BEHAVIOUR
  

  - Not to be able to configure the LED behaviour.
  - The problem with this is many people tend to look at the keyboard while 
typing, and it's somehow exhausting for them having to look at the keyboard 
indicator in the screen every time they want to check in which keyboard layout 
they at in that moment.

  *
   WORK-AROUND
  *

  - Unknown.

  **
   RELEVANT DETAILS
  **

  - Affects Ubuntu 13.10.
  - Doesn't affect Ubuntu versions prior to 13.10 (see screen-shot).
  - For other layout switching problems introduced in Ubuntu 13.10, you can see 
bug #1218322.

  ***
   TECHNICAL DETAILS
  ***

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu45
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Sun Oct 27 17:11:41 2013
  InstallationDate: Installed on 2013-10-20 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

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

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

[Desktop-packages] [Bug 829422] Re: evolution-alarm-notify crashed with SIGSEGV in e_client_get_backend_property()

[Jörg Frings-Fürst]

11.10 not longer supported
change status to invalid

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

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

Title:
  evolution-alarm-notify crashed with SIGSEGV in
  e_client_get_backend_property()

Status in “evolution” package in Ubuntu:
  Invalid

Bug description:
  Logged in, this is what I got :-)

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: libevolution 3.1.5-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1
  Uname: Linux 3.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Fri Aug 19 07:53:50 2011
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/evolution/3.2/evolution-alarm-notify
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  ProcCmdline: /usr/lib/evolution/3.2/evolution-alarm-notify
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fc854d2b428 : 
mov(%rbx),%r14
   PC (0x7fc854d2b428) ok
   source "(%rbx)" (0x440a0d6565764034) not located in a known VMA region 
(needed readable region)!
   destination "%r14" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution
  StacktraceTop:
   e_client_get_backend_property () from /usr/lib/libedataserver-1.2.so.15
   ?? () from /usr/lib/libedataserverui-3.0.so.1
   g_simple_async_result_complete (simple=0x7fc8567b1300) at 
/build/buildd/glib2.0-2.29.16/./gio/gsimpleasyncresult.c:749
   complete_in_idle_cb (data=0x7fc8567b1300) at 
/build/buildd/glib2.0-2.29.16/./gio/gsimpleasyncresult.c:761
   g_main_dispatch (context=0x7fc856647770) at 
/build/buildd/glib2.0-2.29.16/./glib/gmain.c:2439
  Title: evolution-alarm-notify crashed with SIGSEGV in 
e_client_get_backend_property()
  UpgradeStatus: Upgraded to oneiric on 2011-06-17 (62 days ago)
  UserGroups: adm admin audio cdrom dialout dip fax floppy fuse libvirtd 
lpadmin netdev plugdev sambashare tape video

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

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

[Desktop-packages] [Bug 821518] Re: evolution crashed with SIGSEGV in g_markup_escape_text()

[Jörg Frings-Fürst]

11.04 not longer supported
change status to invalid 

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

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

Title:
  evolution crashed with SIGSEGV in g_markup_escape_text()

Status in “evolution” package in Ubuntu:
  Invalid

Bug description:
  I opened Evolution to check my email and the first 20 seconds it runs 
normally until it closes automatically. Then I tried to reinstall packages 
'evolution', 'evolution-common', 'evolution-plugins' but it didn't work. Then I 
decided to reinstall the packages 'evolution', 'evolution-common', 
'evolution-data-server', 'evolution-data-server-common', 'evolution-webcal' and 
'evolution-plugins' through recovery meny and netroot and not only didn't it 
work but also the 'ubuntu-artwork' package was corrupted after it.
  Evolution version: 2.32.2-0ubuntu7
  Ubuntu version: 11.04 Natty installed through Wubi

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: evolution 2.32.2-0ubuntu7
  ProcVersionSignature: Ubuntu 2.6.38-11.47-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic i686
  NonfreeKernelModules: fglrx
  Architecture: i386
  CrashCounter: 1
  Date: Fri Aug  5 17:47:49 2011
  ExecutablePath: /usr/bin/evolution
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
  ProcCmdline: evolution --component=mail
  ProcEnviron:
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x1d5a9b6 :   movzbl 
(%esi),%eax
   PC (0x01d5a9b6) ok
   source "(%esi)" (0xaa0b) in non-readable VMA region: 
0xaa0b-0xaa10 ---p None
   destination "%eax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading VMA None
  Signal: 11
  SourcePackage: evolution
  StacktraceTop:
   g_markup_escape_text () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_markup_vprintf_escaped () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_markup_printf_escaped () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelimap.so
   camel_service_connect () from /usr/lib/libcamel-provider-1.2.so.19
  Title: evolution crashed with SIGSEGV in g_markup_escape_text()
  UpgradeStatus: Upgraded to natty on 2011-05-02 (95 days ago)
  UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev 
plugdev sambashare tape video
  XsessionErrors:
   (nautilus:1584): GdkPixbuf-CRITICAL **: gdk_pixbuf_format_get_name: 
assertion `format != NULL' failed
   (gnome-appearance-properties:1785): Gtk-CRITICAL **: 
gtk_tree_model_sort_real_unref_node: assertion `elt->ref_count > 0' failed
   (nautilus:1584): GdkPixbuf-CRITICAL **: gdk_pixbuf_format_get_name: 
assertion `format != NULL' failed

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

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

[Desktop-packages] [Bug 831842] Re: evolution crashed with signal 5 in e_load_ui_builder_definition()

[Jörg Frings-Fürst]

change status to Fix Relased (see gnome-bugs)

** Changed in: evolution (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  evolution crashed with signal 5 in e_load_ui_builder_definition()

Status in The Evolution Mail & Calendaring Tool:
  Fix Released
Status in “evolution” package in Ubuntu:
  Fix Released

Bug description:
  DId the same as here Bug #831308 ,but this time system generated
  automatic report

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: evolution 3.1.5-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-9.12-generic 3.0.3
  Uname: Linux 3.0.0-9-generic i686
  Architecture: i386
  CrashCounter: 1
  Date: Tue Aug 23 10:53:45 2011
  ExecutablePath: /usr/bin/evolution
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110814)
  ProcCmdline: evolution
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   LANGUAGE=en_US:en
  Signal: 5
  SourcePackage: evolution
  StacktraceTop:
   e_load_ui_builder_definition () from /usr/lib/evolution/3.2/libeutil.so.0
   ?? () from /usr/lib/evolution/3.2/modules/libevolution-module-addressbook.so
   ?? () from /usr/lib/evolution/3.2/modules/libevolution-module-addressbook.so
   g_simple_async_result_complete () from 
/usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/libedataserver-1.2.so.15
  Title: evolution crashed with signal 5 in e_load_ui_builder_definition()
  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/evolution/+bug/831842/+subscriptions

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

[Desktop-packages] [Bug 819748] Re: evolution html signature is not working

[Jörg Frings-Fürst]

11.04 not longer supported
change status to invalid 

** Changed in: evolution (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  evolution html signature is not working

Status in “evolution” package in Ubuntu:
  Invalid

Bug description:
  I have saved a HTML signature. but when I insert it in the email body,
  it behaves as a plain text signature. the links that are present in
  the HTML behaves as plain test.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: evolution 2.32.2-0ubuntu7
  ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
  Uname: Linux 2.6.38-10-generic i686
  NonfreeKernelModules: wl
  Architecture: i386
  Date: Tue Aug  2 16:24:12 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_IN:en
   LANG=en_IN
   LC_MESSAGES=en_IN.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 813312] Re: evolution crashed with SIGSEGV in pixbuf_set_transparency()

[Jörg Frings-Fürst]

11.10 not longer supported
change status to invalid 

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

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

Title:
  evolution crashed with SIGSEGV in pixbuf_set_transparency()

Status in The Unico Gtk+ Theming Engine:
  Fix Released
Status in “evolution” package in Ubuntu:
  Invalid

Bug description:
  Evolution crashed while running in the background.  It's done this a
  couple of times before with the same backtrace, so it looks like
  there's a semi-reproducible problem here.

  Possibly a problem in unico?

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: evolution 3.1.3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7
  Uname: Linux 3.0.0-5-generic x86_64
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Jul 20 15:09:24 2011
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/evolution
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110714)
  ProcCmdline: evolution
  ProcCwd: /home/chris
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, user)
   LANG=en_AU.UTF-8
   SHELL=/bin/zsh
  SegvAnalysis:
   Segfault happened at: 0x7fbec988a2c3 :  
movzbl (%rcx),%esi
   PC (0x7fbec988a2c3) ok
   source "(%rcx)" (0x0003) not located in a known VMA region (needed 
readable region)!
   destination "%esi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: evolution
  StacktraceTop:
   pixbuf_set_transparency (engine=, source=, size=) at ./unico-engine.c:394
   unico_engine_render_icon_pixbuf (engine=, source=, size=) at ./unico-engine.c:455
   gtk_icon_set_render_icon_pixbuf (icon_set=0x7fbedb699560, 
context=0x7fbede213990, size=GTK_ICON_SIZE_MENU) at 
/build/buildd/gtk+3.0-3.1.8/./gtk/gtkiconfactory.c:1730
   gtk_image_calc_size (image=0x7fbedb933480) at 
/build/buildd/gtk+3.0-3.1.8/./gtk/gtkimage.c:1906
   gtk_image_get_preferred_width (widget=, 
minimum=0x7fffd00c32e0, natural=0x7fffd00c32e4) at 
/build/buildd/gtk+3.0-3.1.8/./gtk/gtkimage.c:1956
  Title: evolution crashed with SIGSEGV in pixbuf_set_transparency()
  UpgradeStatus: Upgraded to oneiric on 2011-07-16 (3 days ago)
  UserGroups: admin sbuild

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

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

[Desktop-packages] [Bug 811835] Re: evolution crashed with SIGSEGV in html_object_is_text()

[Jörg Frings-Fürst]

11.10 not longer supported
change status to invalid 

** Changed in: evolution (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  evolution crashed with SIGSEGV in html_object_is_text()

Status in The Evolution Mail & Calendaring Tool:
  Confirmed
Status in “evolution” package in Ubuntu:
  Invalid

Bug description:
  Conf: ACER One D531h with Kubuntu 11.10 Oneiric alpha 2 updated dayly

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: evolution 3.1.3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7
  Uname: Linux 3.0.0-5-generic i686
  Architecture: i386
  CrashCounter: 1
  Date: Sun Jul 17 01:38:42 2011
  ExecutablePath: /usr/bin/evolution
  InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
  ProcCmdline: /usr/bin/evolution
  ProcEnviron:
   LANGUAGE=fr_FR
   LANG=fr_FR.UTF-8
   LC_MESSAGES=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x10539c57 :   mov
(%eax),%eax
   PC (0x10539c57) ok
   source "(%eax)" (0x2e74656c) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution
  StacktraceTop:
   html_object_is_text () from /usr/lib/libgtkhtml-4.0.so.0
   ?? () from /usr/lib/libgtkhtml-4.0.so.0
   ?? () from /usr/lib/libgtkhtml-4.0.so.0
   ?? () from /usr/lib/libgtkhtml-4.0.so.0
   g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: evolution crashed with SIGSEGV in html_object_is_text()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare

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

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

[Desktop-packages] [Bug 814544] Re: evolution crashed with SIGSEGV in g_type_check_instance_is_a()

[Jörg Frings-Fürst]

11.10 not longer supported
change status to invalid (see gnome-bugs)

** Changed in: evolution (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  evolution crashed with SIGSEGV in g_type_check_instance_is_a()

Status in The Evolution Mail & Calendaring Tool:
  Invalid
Status in “evolution” package in Ubuntu:
  Invalid

Bug description:
  This happened when I was in the "save" dialog to save email
  attachments from within evolution. the dialog at some point became
  unresponsive and a bit later, evolution crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: evolution 3.1.3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-6.7-generic 3.0.0-rc7
  Uname: Linux 3.0.0-6-generic x86_64
  Architecture: amd64
  Date: Fri Jul 22 12:27:46 2011
  ExecutablePath: /usr/bin/evolution
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  ProcCmdline: evolution
  ProcEnviron:
   LANGUAGE=en
   LANG=en_DK.utf8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f2f83f99ff0 :   
testb  $0x4,0x16(%rdi)
   PC (0x7f2f83f99ff0) ok
   source "$0x4" ok
   destination "0x16(%rdi)" (0x7f2f00100016) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: evolution
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_file_equal () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/libgtk-3.so.0
   ?? () from /usr/lib/libgtk-3.so.0
   ?? () from /usr/lib/libgtk-3.so.0
  Title: evolution crashed with SIGSEGV in g_type_check_instance_is_a()
  UpgradeStatus: Upgraded to oneiric on 2011-07-19 (3 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 818718] Re: evolution crashed with SIGSEGV in __strcmp_sse4_2()

[Jörg Frings-Fürst]

11.10 not longer supported
change status to Fix Released (see gnome-bugs)

** Changed in: evolution (Ubuntu)
   Status: Triaged => Invalid

** Changed in: evolution (Ubuntu)
   Status: Invalid => Fix Released

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

Title:
  evolution crashed with SIGSEGV in __strcmp_sse4_2()

Status in The Evolution Mail & Calendaring Tool:
  Fix Released
Status in “evolution” package in Ubuntu:
  Fix Released

Bug description:
  Only started evolution after update my system.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: evolution 3.1.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0
  Uname: Linux 3.0.0-7-generic i686
  NonfreeKernelModules: acpi_call
  Architecture: i386
  Date: Sat Jul 30 23:19:00 2011
  ExecutablePath: /usr/bin/evolution
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426)
  ProcCmdline: evolution
  SegvAnalysis:
   Segfault happened at: 0xa35677 <__strcmp_sse4_2+23>: movdqu (%edx),%xmm2
   PC (0x00a35677) ok
   source "(%edx)" (0x0e01fc86) not located in a known VMA region (needed 
readable region)!
   destination "%xmm2" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution
  StacktraceTop:
   __strcmp_sse4_2 () at ../sysdeps/i386/i686/multiarch/strcmp-sse4.S:70
   g_str_equal () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_intern_static_string () from /lib/i386-linux-gnu/libglib-2.0.so.0
   comp_editor_get_type () at comp-editor.c:210
  Title: evolution crashed with SIGSEGV in __strcmp_sse4_2()
  UpgradeStatus: Upgraded to oneiric on 2011-07-15 (15 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

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

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

[Desktop-packages] [Bug 817468] Re: evolution crashed with SIGSEGV in g_str_equal()

[Jörg Frings-Fürst]

11.10 not longer supported
change status to invalid (see gnome-bugs)

** Changed in: evolution (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  evolution crashed with SIGSEGV in g_str_equal()

Status in The Evolution Mail & Calendaring Tool:
  Invalid
Status in “evolution” package in Ubuntu:
  Invalid

Bug description:
  Freshly booted, opened Evolution while reading a website and this
  crash happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: evolution 3.1.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-7.8-generic 3.0.0
  Uname: Linux 3.0.0-7-generic i686
  Architecture: i386
  Date: Thu Jul 28 12:11:30 2011
  ExecutablePath: /usr/bin/evolution
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426)
  ProcCmdline: evolution
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
  SegvAnalysis:
   Segfault happened at: 0xb1ae0b:  cmp%cl,(%edx)
   PC (0x00b1ae0b) ok
   source "%cl" ok
   destination "(%edx)" (0x0128cc86) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: evolution
  StacktraceTop:
   ?? () from /lib/i386-linux-gnu/libc.so.6
   g_str_equal () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_intern_static_string () from /lib/i386-linux-gnu/libglib-2.0.so.0
   comp_editor_get_type () from 
/usr/lib/evolution/3.2/libevolution-calendar.so.0
  Title: evolution crashed with SIGSEGV in g_str_equal()
  UpgradeStatus: Upgraded to oneiric on 2011-07-26 (1 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 809353] Re: evolution crashed with SIGSEGV in g_type_check_instance_is_a()

[Jörg Frings-Fürst]

11.10 not longer supported
change status to invalid 

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

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

Title:
  evolution crashed with SIGSEGV in g_type_check_instance_is_a()

Status in “evolution” package in Ubuntu:
  Invalid

Bug description:
  want to take evolution backup from my ubuntu one folder -> result:
  Evolution crashes

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: evolution 3.1.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-4.5-generic 3.0.0-rc6
  Uname: Linux 3.0.0-4-generic x86_64
  Architecture: amd64
  Date: Tue Jul 12 16:19:48 2011
  ExecutablePath: /usr/bin/evolution
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110701)
  ProcCmdline: evolution
  ProcEnviron:
   SHELL=/bin/bash
   LANGUAGE=de_CH:de
   LANG=de_CH.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f52bbe44ff0 :   
testb  $0x4,0x16(%rdi)
   PC (0x7f52bbe44ff0) ok
   source "$0x4" ok
   destination "0x16(%rdi)" (0x7f52001e) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: evolution
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: evolution crashed with SIGSEGV in g_type_check_instance_is_a()
  UpgradeStatus: Upgraded to oneiric on 2011-07-11 (1 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

-- 
Mailing list: https://launchpad.net/~desktop-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 alt+shift, ctrl+shift, etc.

[Alberto Salvia Novella]

The other day I dreamed a blessed hope,
that an ant was climbing over my shorts.

So keep calm, and do easy ♡

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

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in Gnome Settings Daemon:
  Invalid
Status in Ubuntu GNOME:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” source package in Saucy:
  Triaged

Bug description:
  A PPA which should provide some relief for this issue is available at
  https://launchpad.net/~attente/+archive/1218322. There still remain
  issues regarding keyboard shortcuts though. To install:

  sudo add-apt-repository ppa:attente/1218322
  sudo apt-get update
  sudo apt-get upgrade

  === gnome-control-center ===

  Impact: the UI to change the layout switching keys doesn't work

  Test case:
  - open gnome-control-center's text input settings
  - click on the "next layout key" entry
  - try entering a key combinaison (e.g ctrl-space)
  -> the UI should reflect the new keys

  Regression potential: that UI was not working before, it should only
  be an improvement (some key combos are not working as expected, that's
  another issue and shouldn't be mixed with this one)

  === gnome-settings-daemon ===

  Impact: attempting to change keyboard layouts using only modifier keys
  doesn't work

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
"['Shift_L']"
  - press and release ctrl+left shift
  -> the current input source should change

  Regression potential: The input switching shortcut might capture other
  non-modifier shortcuts, but users will need to consider this when
  choosing their switching shortcut anyways. For users this bug affects,
  this represents a working solution for a critical bug.

  --

  Test results for different keyboard layout change hotkeys may be
  viewed and added in the Google Docs table, created by Norbert
  
(https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE&usp=sharing).

  --

  Separate bug reports for individual layout switching hotkey
  combinations:

  Super+Space and Shift+Super+Space:
     * Unity greeter (bug 1245137);
     * Unity session (bug 1245136);
     * lock screen - gnome-screensaver (bug 1245138, bug 1245256);
     * ubiquity installer (bug 1242572).

  Alt+Shift:
     * Unity greeter (bug 1245258)
     * Can't set keyboard layout change to Alt+Shift (bug 1245926)

  Ctrl+Shift:
     * lock screen - gnome-screensaver (bug 1245270)
     * Unity greeter (bug 1245268)
     * Can't set keyboard layout change to Ctrl+Shift (bug 1245991)
     * If keyboard layout switching hotkey is set to Ctrl+Shift, Ctrl+Shift+C/V 
are not working in gnome-terminal (bug 1246656)

  Shift+Shift:
     * Can't set keyboard layout change to Shift+Shift (bug 1245272)
     * lock screen - gnome-screensaver (bug 1245278)
     * Unity greeter (bug 1245280)

  Bugs which belong to keyboard layout switching:
     * Hotkeys not functional in non-latin keyboard layout in 13.10 (bug 
1226962)
     * Keyboard Layout Options window is missed in gnome-control-center 
keyboard (bug 1245064)
     * Unable to set keyboard LED to show alternative layout in 
gnome-control-center keyboard in Saucy (bug 1245188)
     * Unable to set Miscellaneous compatibility options in 
gnome-control-center keyboard in Saucy (bug 1245199)
     * Keyboard shortcut for changing keyboard layout does not work on lock 
screen (bug 1244548)
     * [FFe] indicator-keyboard not working under greeter (bug 1228207)
     * Lost ability to remap Caps Lock to Ctrl (bug 1215826)
     * gnome-control-center keyboard no longer has way to modify caps lock key 
behavior (bug 1224575)
     * Pressing Caps Lock toggles LED even when mapped to another key (bug 
1221403)
 * Switching layout turns off NumLock (bug 1247668)

  --

  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)
  InstallationMe

[Desktop-packages] [Bug 803266] Re: evolution crashed with SIGSEGV in g_type_check_instance_is_a()

[Jörg Frings-Fürst]

11.10 not longer supported
change status to invalid (see gnome-bugs)

** Changed in: evolution (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  evolution crashed with SIGSEGV in g_type_check_instance_is_a()

Status in The Evolution Mail & Calendaring Tool:
  Invalid
Status in “evolution” package in Ubuntu:
  Invalid

Bug description:
  Steps for reproducte:
  - Click on the new button for a new message.
  - complete the text box to: and the suject for the message
  - insert one sd-card in your computer.
  - attach any file from this sd-card in the message.
  - Evo freeze and crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: evolution 3.1.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0-2.3-generic 3.0.0-rc4
  Uname: Linux 3.0-2-generic i686
  Architecture: i386
  Date: Tue Jun 28 21:40:31 2011
  ExecutablePath: /usr/bin/evolution
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426)
  ProcCmdline: evolution
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LC_MESSAGES=en_US.utf8
   LANG=es_CL.utf8
   LANGUAGE=en_US:en
  SegvAnalysis:
   Segfault happened at: 0xe6ee10 : testb  
$0x4,0xe(%edi)
   PC (0x00e6ee10) ok
   source "$0x4" ok
   destination "0xe(%edi)" (0xeceeef0a) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: evolution
  StacktraceTop:
   g_type_check_instance_is_a (type_instance=0xb06d1000, iface_type=80) at 
/build/buildd/glib2.0-2.29.8/./gobject/gtype.c:3952
   g_object_unref (_object=0xb06d1000) at 
/build/buildd/glib2.0-2.29.8/./gobject/gobject.c:2680
   button_data_free (button_data=0xb0a1a110) at 
/build/buildd/gtk+3.0-3.1.6/./gtk/gtkpathbar.c:1370
   weak_refs_notify (data=0xad0d0a08) at 
/build/buildd/glib2.0-2.29.8/./gobject/gobject.c:2244
   g_data_set_internal (datalist=0x29a18680, key_id=54, data=0x0, 
destroy_func=0) at /build/buildd/glib2.0-2.29.8/./glib/gdataset.c:410
  Title: evolution crashed with SIGSEGV in g_type_check_instance_is_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

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

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

[Desktop-packages] [Bug 782363] Re: evolution crashed with SIGSEGV in e_tree_node_is_expanded()

[Jörg Frings-Fürst]

change status to Fix Released  (see gnome-bugs)

** Changed in: evolution (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  evolution crashed with SIGSEGV in e_tree_node_is_expanded()

Status in The Evolution Mail & Calendaring Tool:
  Fix Released
Status in “evolution” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: evolution

  Evolution hangup sometimes when i composing, sending, looking name on
  ldap server or formating messages, all of this bugs are present after
  upgrade to 11.04 :

  1)Description:Ubuntu 11.04, Release:  11.04
  2)evolution:
Instalados: 2.32.2-0ubuntu7
Candidato:  2.32.2-0ubuntu7
Tabla de versión:
   *** 2.32.2-0ubuntu7 0
  500 http://archive.ubuntu.com/ubuntu/ natty/main i386 Packages
  100 /var/lib/dpkg/status
  3) Evolution working weel as before the upgrade
  4)Hangup doen not work properly

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: evolution 2.32.2-0ubuntu7
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  Architecture: i386
  Date: Fri May 13 14:45:01 2011
  ExecutablePath: /usr/bin/evolution
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcCmdline: evolution
  ProcEnviron:
   LANGUAGE=es_VE:en
   PATH=(custom, user)
   LANG=es_VE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x4340a13 :mov
0x4(%eax),%eax
   PC (0x04340a13) ok
   source "0x4(%eax)" (0x0004) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: evolution
  StacktraceTop:
   e_tree_node_is_expanded () from /usr/lib/evolution/2.32/libetable.so.0
   ?? () from /usr/lib/evolution/2.32/libevolution-mail.so.0
   ?? () from /usr/lib/evolution/2.32/libevolution-mail.so.0
   ?? () from /usr/lib/evolution/2.32/libevolution-mail.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  Title: evolution crashed with SIGSEGV in e_tree_node_is_expanded()
  UpgradeStatus: Upgraded to natty on 2011-05-01 (11 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 806942] Re: evolution-settings crashed with SIGSEGV in g_pointer_bit_lock()

[Jörg Frings-Fürst]

11.10 not longer supported
change status to invalid 

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

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

Title:
  evolution-settings crashed with SIGSEGV in g_pointer_bit_lock()

Status in “evolution” package in Ubuntu:
  Invalid

Bug description:
  evolution settings would not open

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: evolution 3.1.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0-3.4-generic 3.0.0-rc5
  Uname: Linux 3.0-3-generic i686
  Architecture: i386
  Date: Thu Jul  7 08:27:16 2011
  ExecutablePath: /usr/bin/evolution-settings
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
  ProcCmdline: evolution-settings
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x678a98 :  lock bts 
%ecx,(%esi)
   PC (0x00678a98) ok
   source "%ecx" ok
   destination "(%esi)" (0x0008) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: evolution
  StacktraceTop:
   g_pointer_bit_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_datalist_id_get_data () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/evolution/3.2/libeshell.so.0
   g_object_newv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: evolution-settings crashed with SIGSEGV in g_pointer_bit_lock()
  UpgradeStatus: Upgraded to oneiric on 2011-07-07 (0 days ago)
  UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev 
plugdev powerdev sambashare tape video

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

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