date:20140808

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

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

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1354287/+attachment/4172472/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1354287/+attachment/4172475/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1354287/+attachment/4172480/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1354287/+attachment/4172481/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1354287/+attachment/4172482/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1354287/+attachment/4172485/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1354287/+attachment/4172486/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1229021
   chromium-browser crashed with SIGSEGV

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  chromium-browser crashed with SIGSEGV in base::MessageLoop::RunTask()

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

Bug description:
  Crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: chromium-browser 35.0.1916.153-0ubuntu1~pkg1029
  Uname: Linux 3.16.0-031600-generic x86_64
  ApportVersion: 2.14.5-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Thu Aug  7 23:18:00 2014
  Desktop-Session:
   DESKTOP_SESSION = gnome
   XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2014-04-27 (102 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  ProcCmdline: chromium-browser\ --type=gpu-process\ 
--channel=3543.0.1309785003\ --disable-breakpad\ --supports-dual-gpus=false\ 
--gpu-driver-bug-workarounds=1,9,13\ --gpu-vendor-id=0x8086\ 
--gpu-device-id=0x0116\ --gpu-driver-vendor\ --gpu-driver-versi
  SegvAnalysis:
   Segfault happened at: 0x7f66ffe58f38:movl   $0x1337,0x0
   PC (0x7f66ffe58f38) ok
   source $0x1337 ok
   destination 0x0 (0x) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? () from /usr/lib/chromium-browser/libs/libcontent.so
   base::MessageLoop::RunTask(base::PendingTask const) () from 
/usr/lib/chromium-browser/libs/libbase.so
   base::MessageLoop::DeferOrRunPendingTask(base::PendingTask const) () from 
/usr/lib/chromium-browser/libs/libbase.so
   base::MessageLoop::DoDelayedWork(base::TimeTicks*) () from 
/usr/lib/chromium-browser/libs/libbase.so
   ?? () from /usr/lib/chromium-browser/libs/libbase.so
  Title: chromium-browser crashed with SIGSEGV in base::MessageLoop::RunTask()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-04-27T17:58:46.529285

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

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

[Desktop-packages] [Bug 1320020] Re: [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all

2014-08-08 Thread Raymond

Node 0x14 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out
  Control: name=Speaker Playback Switch, index=0, device=0
ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Control: name=Speaker Phantom Jack, index=0, device=0
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x80 0x80]
  Pincap 0x0001003c: IN OUT HP EAPD Detect
  EAPD 0x2: EAPD
  Pin Default 0x99130110: [Fixed] Speaker at Int ATAPI
Conn = ATAPI, Color = Unknown
DefAssociation = 0x1, Sequence = 0x0
Misc = NO_PRESENCE
  Pin-ctls: 0x00:
  Unsolicited: tag=00, enabled=0
  Power states:  D0 D1 D2 D3 EPSS
  Power: setting=D0, actual=D0
  Connection: 2
 0x0c 0x0d*



control.15 {
iface CARD
name 'Headphone Jack'
value true
comment {
access read
type BOOLEAN
count 1
}
}


your speaker was muted by driver when headphone is plugged


try hda jack sense test to test HP and mic

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

Title:
  [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all

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

Bug description:
  I can get perfect sound through headphones, and the kernel recognizes
  the internal speaker, but nothing is ever played through it. I have
  personally tested a pair of earbuds to make sure that sound could play
  through the headphone port, and that isn't a problem. The sound driver
  just refuses to recognize the existence of the speaker, even though
  the kernel does.

  I wouldn't be surprised if the last upstream update had something to
  do with it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  isiah  7361 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu May 15 18:07:52 2014
  InstallationDate: Installed on 2014-01-29 (106 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 
(20131017)
  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/controlC0:  isiah  7361 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to trusty on 2014-05-04 (11 days ago)
  dmi.bios.date: 03/23/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0M7CYJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A05
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd03/23/2011:svnDellInc.:pnInspiron1470:pvrA05123:rvnDellInc.:rn0M7CYJ:rvrA05:cvnDellInc.:ct8:cvrA05:
  dmi.product.name: Inspiron 1470
  dmi.product.version: A05123
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1320020] Re: [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all

2014-08-08 Thread Isiah Meadows

Also, I never used headphones in running alsa-test.sh. Thought that might
help.
On Aug 8, 2014 3:41 AM, Raymond 1320...@bugs.launchpad.net wrote:

 Node 0x14 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out
   Control: name=Speaker Playback Switch, index=0, device=0
 ControlAmp: chs=3, dir=Out, idx=0, ofs=0
   Control: name=Speaker Phantom Jack, index=0, device=0
   Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
   Amp-Out vals:  [0x80 0x80]
   Pincap 0x0001003c: IN OUT HP EAPD Detect
   EAPD 0x2: EAPD
   Pin Default 0x99130110: [Fixed] Speaker at Int ATAPI
 Conn = ATAPI, Color = Unknown
 DefAssociation = 0x1, Sequence = 0x0
 Misc = NO_PRESENCE
   Pin-ctls: 0x00:
   Unsolicited: tag=00, enabled=0
   Power states:  D0 D1 D2 D3 EPSS
   Power: setting=D0, actual=D0
   Connection: 2
  0x0c 0x0d*



 control.15 {
 iface CARD
 name 'Headphone Jack'
 value true
 comment {
 access read
 type BOOLEAN
 count 1
 }
 }


 your speaker was muted by driver when headphone is plugged


 try hda jack sense test to test HP and mic

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1320020

 Title:
   [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all

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

 Bug description:
   I can get perfect sound through headphones, and the kernel recognizes
   the internal speaker, but nothing is ever played through it. I have
   personally tested a pair of earbuds to make sure that sound could play
   through the headphone port, and that isn't a problem. The sound driver
   just refuses to recognize the existence of the speaker, even though
   the kernel does.

   I wouldn't be surprised if the last upstream update had something to
   do with it.

   ProblemType: Bug
   DistroRelease: Ubuntu 14.04
   Package: alsa-base 1.0.25+dfsg-0ubuntu4
   ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
   Uname: Linux 3.13.0-24-generic x86_64
   NonfreeKernelModules: wl
   ApportVersion: 2.14.1-0ubuntu3.1
   Architecture: amd64
   AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0:  isiah  7361 F pulseaudio
   CurrentDesktop: GNOME
   Date: Thu May 15 18:07:52 2014
   InstallationDate: Installed on 2014-01-29 (106 days ago)
   InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64
 (20131017)
   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/controlC0:  isiah  7361 F pulseaudio
   Symptom_Jack: Speaker, Internal
   Symptom_Type: No sound at all
   Title: [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all
   UpgradeStatus: Upgraded to trusty on 2014-05-04 (11 days ago)
   dmi.bios.date: 03/23/2011
   dmi.bios.vendor: Dell Inc.
   dmi.bios.version: A05
   dmi.board.name: 0M7CYJ
   dmi.board.vendor: Dell Inc.
   dmi.board.version: A05
   dmi.chassis.type: 8
   dmi.chassis.vendor: Dell Inc.
   dmi.chassis.version: A05
   dmi.modalias:
 dmi:bvnDellInc.:bvrA05:bd03/23/2011:svnDellInc.:pnInspiron1470:pvrA05123:rvnDellInc.:rn0M7CYJ:rvrA05:cvnDellInc.:ct8:cvrA05:
   dmi.product.name: Inspiron 1470
   dmi.product.version: A05123
   dmi.sys.vendor: Dell Inc.

 To manage notifications about this bug go to:

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


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

Title:
  [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all

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

Bug description:
  I can get perfect sound through headphones, and the kernel recognizes
  the internal speaker, but nothing is ever played through it. I have
  personally tested a pair of earbuds to make sure that sound could play
  through the headphone port, and that isn't a problem. The sound driver
  just refuses to recognize the existence of the speaker, even though
  the kernel does.

  I wouldn't be surprised if the last upstream update had something to
  do with it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  isiah  7361 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu May 15 18:07:52 2014
  InstallationDate: Installed on 2014-01-29

Re: [Desktop-packages] [Bug 1320020] Re: [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all

2014-08-08 Thread Isiah Meadows

And how would I go around to do that?
On Aug 8, 2014 3:41 AM, Raymond 1320...@bugs.launchpad.net wrote:

 Node 0x14 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out
   Control: name=Speaker Playback Switch, index=0, device=0
 ControlAmp: chs=3, dir=Out, idx=0, ofs=0
   Control: name=Speaker Phantom Jack, index=0, device=0
   Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
   Amp-Out vals:  [0x80 0x80]
   Pincap 0x0001003c: IN OUT HP EAPD Detect
   EAPD 0x2: EAPD
   Pin Default 0x99130110: [Fixed] Speaker at Int ATAPI
 Conn = ATAPI, Color = Unknown
 DefAssociation = 0x1, Sequence = 0x0
 Misc = NO_PRESENCE
   Pin-ctls: 0x00:
   Unsolicited: tag=00, enabled=0
   Power states:  D0 D1 D2 D3 EPSS
   Power: setting=D0, actual=D0
   Connection: 2
  0x0c 0x0d*



 control.15 {
 iface CARD
 name 'Headphone Jack'
 value true
 comment {
 access read
 type BOOLEAN
 count 1
 }
 }


 your speaker was muted by driver when headphone is plugged


 try hda jack sense test to test HP and mic

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1320020

 Title:
   [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all

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

 Bug description:
   I can get perfect sound through headphones, and the kernel recognizes
   the internal speaker, but nothing is ever played through it. I have
   personally tested a pair of earbuds to make sure that sound could play
   through the headphone port, and that isn't a problem. The sound driver
   just refuses to recognize the existence of the speaker, even though
   the kernel does.

   I wouldn't be surprised if the last upstream update had something to
   do with it.

   ProblemType: Bug
   DistroRelease: Ubuntu 14.04
   Package: alsa-base 1.0.25+dfsg-0ubuntu4
   ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
   Uname: Linux 3.13.0-24-generic x86_64
   NonfreeKernelModules: wl
   ApportVersion: 2.14.1-0ubuntu3.1
   Architecture: amd64
   AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0:  isiah  7361 F pulseaudio
   CurrentDesktop: GNOME
   Date: Thu May 15 18:07:52 2014
   InstallationDate: Installed on 2014-01-29 (106 days ago)
   InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64
 (20131017)
   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/controlC0:  isiah  7361 F pulseaudio
   Symptom_Jack: Speaker, Internal
   Symptom_Type: No sound at all
   Title: [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all
   UpgradeStatus: Upgraded to trusty on 2014-05-04 (11 days ago)
   dmi.bios.date: 03/23/2011
   dmi.bios.vendor: Dell Inc.
   dmi.bios.version: A05
   dmi.board.name: 0M7CYJ
   dmi.board.vendor: Dell Inc.
   dmi.board.version: A05
   dmi.chassis.type: 8
   dmi.chassis.vendor: Dell Inc.
   dmi.chassis.version: A05
   dmi.modalias:
 dmi:bvnDellInc.:bvrA05:bd03/23/2011:svnDellInc.:pnInspiron1470:pvrA05123:rvnDellInc.:rn0M7CYJ:rvrA05:cvnDellInc.:ct8:cvrA05:
   dmi.product.name: Inspiron 1470
   dmi.product.version: A05123
   dmi.sys.vendor: Dell Inc.

 To manage notifications about this bug go to:

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


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

Title:
  [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all

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

Bug description:
  I can get perfect sound through headphones, and the kernel recognizes
  the internal speaker, but nothing is ever played through it. I have
  personally tested a pair of earbuds to make sure that sound could play
  through the headphone port, and that isn't a problem. The sound driver
  just refuses to recognize the existence of the speaker, even though
  the kernel does.

  I wouldn't be surprised if the last upstream update had something to
  do with it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  isiah  7361 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu May 15 18:07:52 2014
  InstallationDate: Installed on 2014-01-29 (106 days ago)
  InstallationMedia:

[Desktop-packages] [Bug 1275416] Re: touchscreen do not work after suspend/resume

2014-08-08 Thread knyterant

@#15，@#16/#17，thanks，but，no effect for my x200t with 14.04。 :(

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

Title:
  touchscreen do not work after suspend/resume

Status in “xinput” package in Ubuntu:
  Confirmed

Bug description:
  My laptop (Thinkpad X200T with multi-touch screen) installed the
  'Trusty' ubuntu 14.04 (64bits), touchscreen works well after cold
  boot! But after suspend/resume, touchsreen do not response. Execute
  'xsetwacom --list' in terminal, there is nothing, both 'wacom touch'
  and 'wacom stylus' are gone. I must logout and relogin or reboot, the
  touchscreen can be normal again.

  By the way, the same problem happens in the 'Saucy' ubuntu 13.10
  (64bits). But in 'Raring' ubuntu 13.04 (64bits), this problem does no
  exist, touchscreen WORKS WELL after suspend/resume.

  This Thinkpad X200T updated the newest BIOS, and keep ubuntu OS up to
  date.

  Please fix this bug, because 14.04 is a very important version for
  touchscreen devices, and i think 'suspend/resume' function is
  important too. Thanks!

  ---
  Feb 4, 2014 update

  Oh I'm sorry, I find a new change for this bug that I never noticed
  before.

  I keep Trusty ubuntu up to date(Feb 4, 2014). When the OS's first boot
  from cold boot, touchscreen works well. Then if suspend/resume for the
  first time, touchscreen will not response. At this moment, logout and
  relogin, touchscreen works well again even after suspend/resume.

  Simply put, touchscreen do not response only after the first
  suspend/resume since a cold boot. Once the OS logout and relogin,
  touchscreen will work well after any suspend/resume. The key point is
  that the OS must logout and relogin for at least one time.

  Always keep 'Trusty' ubuntu OS updated.

  that's a strange bug

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

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

[Desktop-packages] [Bug 510059] Re: Gvfs keeps asking for password when trying to mount Samba share

2014-08-08 Thread borgelillebo

Xubuntu 14.04. Confirming problem with gvfs. Gigolo keeps prompting for
username, domain and password. The same happens with gvfs-mount in the
terminal.

I am able to mount the folder with cifs:
sudo mount -t cifs //xxx/xxx newfolder/ -o 
username=myusername,domain=mydomain,sec=ntlmssp,noperm

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

Title:
  Gvfs keeps asking for password when trying to mount Samba share

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

Bug description:
  Binary package hint: nautilus

  My Ubuntu Desktop (9.10, 64-bit) VM can't connect to my Windows 7
  (64-bit, Ultimate) File Share using Nautilus. I enter
  smb://comuterName in the address bar and then it comes up with a
  password dialog (see screenshot) and then after entering the correct
  login info, the dialog disappears for a second or two but then
  reappears again. The dialog always comes back up and the share is
  never mounted.

  * Connecting from an XP box on the network to the windows 7 share works 
just fine.
  * Connecting from the Ubuntu machine to the windows 7 share using the 
appropriate 'smbmount' command works just fine.
  * Connecting from the Ubuntu machine (using the nautilus GUI) to the XP 
box (password protected) works just fine.
  * Then I turned off password protection in Win7, rebooted the win7 
machine, and still all of the above tests turned out the same. And the Ubuntu 
machine still doesn't connect to the windows share using the nautilus GUI, and 
still displays the password dialog even though no password is required anymore.
  * I tried using smbclient to view the shares, here is the output (not 
sure if I should be trying something else using the smbclient program):
o eddie@eddie-ubuntu:~$ smbclient -L eddie-win7
  Enter eddie's password:
  session setup failed: SUCCESS - 0

  ProblemType: Bug
  Architecture: amd64
  Date: Sun Jan 17 15:41:28 2010
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/nautilus
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  Package: nautilus 1:2.28.1-0ubuntu3
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-server
  SourcePackage: nautilus
  Uname: Linux 2.6.31-17-server x86_64

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

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

[Desktop-packages] [Bug 1069964] Re: Unable to mount Blank CD-R disc. Location is already mounted.

2014-08-08 Thread Howy

** Also affects: unity-settings-daemon
   Importance: Undecided
   Status: New

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** No longer affects: unity-settings-daemon

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

Title:
  Unable to mount Blank CD-R disc. Location is already mounted.

Status in OEM Priority Project:
  New
Status in “glib2.0” package in Ubuntu:
  Confirmed
Status in “unity-settings-daemon” package in Ubuntu:
  Confirmed

Bug description:
  This error message comes up, while still able to burn, read/write etc. It 
occurs in quantal when inserting a CD/DVD into the drive, but it did not happen 
in precice.
  Screenshot:
  http://i47.tinypic.com/4v0aj6.png

  Burner: LG HL-DT-ST DVDRAM GH24NS90

  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 x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 22 19:50:35 2012
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.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/oem-priority/+bug/1069964/+subscriptions

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

[Desktop-packages] [Bug 1354313] [NEW] [Dell Inspiron 5721] Brightness control does not work with 12.04.5(with kernel 3.13)

2014-08-08 Thread Yung Shen

Public bug reported:

This is a system installed with latest stable 12.04.5 image.

The Brightness key will invoke the osd-notify indicator but the display
brightness won't change.

Verifying the value changing in backlight interface, system are using
acpi_video0 instead:

Steps to monitor the backlight interfaces:

Press the brightness key until maxium indicator shows:

ubuntu@201210-11863:/sys/class/backlight$ cat intel_backlight/brightness ; cat 
acpi_video0/brightness
3407
99
ubuntu@201210-11863:/sys/class/backlight$

Press the brightness key until to minimum indicator shows:

ubuntu@201210-11863:/sys/class/backlight$ cat intel_backlight/brightness ; cat 
acpi_video0/brightness
3407
0


-

The workaround found here could solve this issue:
http://itsfoss.com/fix-brightness-ubuntu-1310/

-

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.0.1-0ubuntu17.6
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 Aug  8 03:51:43 2014
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
DkmsStatus: fwts-efi-runtime-dkms, 14.07.00, 3.13.0-32-generic, x86_64: 
installed
ExtraDebuggingInterest: Yes, even including gdb or git bisection work if needed
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:05ba]
 Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] (rev 
ff) (prog-if ff)
InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 
(20140807.1)
MachineType: Dell Inc. Inspiron 5721
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=93a24f68-72a1-4335-938a-75f624f57e68 ro quiet splash initcall_debug 
vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/25/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 0KNF68
dmi.board.vendor: Dell Inc.
dmi.board.version: X01
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A12
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd10/25/2013:svnDellInc.:pnInspiron5721:pvrA12:rvnDellInc.:rn0KNF68:rvrX01:cvnDellInc.:ct8:cvrA12:
dmi.product.name: Inspiron 5721
dmi.product.version: A12
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.7.12-0ubuntu4
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1~precise1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

** Affects: linux-lts-trusty (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: 201210-11863 amd64 apport-bug compiz-0.9 precise referred-by-support 
running-unity taipei-lab ubuntu

** Also affects: linux-lts-trusty (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xorg (Ubuntu)
   Importance: Critical = Undecided

** Description changed:

  This is a system installed with latest stable 12.04.5 image.
  
  The Brightness key will invoke the osd-notify indicator but the display
  brightness won't change.
  
  Verifying the value changing in backlight interface, system are using
  acpi_video0 instead:
  
  Steps to monitor the backlight interfaces:
  
- 
  Press the brightness key until maxium indicator shows:
  
- ubuntu@201210-11863:/sys/class/backlight$ cat intel_backlight/brightness ; 
cat acpi_video0/brightness 
+ ubuntu@201210-11863:/sys/class/backlight$ cat intel_backlight/brightness ; 
cat acpi_video0/brightness
  3407
  99
  ubuntu@201210-11863:/sys/class/backlight$
  
- 
  Press the brightness key until to minimum indicator shows:
  
- ubuntu@201210-11863:/sys/class/backlight$ cat intel_backlight/brightness ; 
cat acpi_video0/brightness 
+ ubuntu@201210-11863:/sys/class/backlight$ cat intel_backlight/brightness ; 
cat acpi_video0/brightness
  3407
  0
+ 
+ 
+ -
+ 
+ The workaround found here could solve this issue:
+ http://itsfoss.com/fix-brightness-ubuntu-1310/
+ 
+ -
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic

[Desktop-packages] [Bug 1354318] [NEW] whoopsie-upload-all has a wrong check for whether the upload is done

2014-08-08 Thread Steve Langasek

Public bug reported:

Currently, the way whoopsie-upload-all works is that, whenever a new
.crash file is seen, /etc/init/apport-noui.conf triggers to run
whoopsie-upload-all from a single-threaded job that iterates through all
as-yet-unprocessed .crash files, process them via apport, marks them for
upload, and then waits for apport to upload them.

There are several problems with this:

 - The wait for apport to upload them is racy.  Once a report is submitted, 
it is legitimate for something to remove all of the related files (.crash, 
.upload, .uploaded).  On our test infrastructure, that has resulted in buggy 
behavior because the test harness is removing these files /while 
whoopsie-upload-all is polling/, causing it to poll for a very long time 
waiting for a file that will never be found and then time out.
 - waiting for apport to upload is pointless anyway for its designed use, since 
whoopsie-upload-all is called from an upstart job that's inotify-triggered so 
nothing waits for the return from this command anyway.  The utah scripts appear 
to currently be waiting for it; however this should be non-default, exceptional 
behavior, because...
 - since apport-noui is not an 'instance' job, as long as the job is running 
(presumably blocking on files that are never going to show up), *newly* created 
.crash files will not be processed.
 - the job furthermore is written to assume that it will be called separately 
for crashes done as different users.  However, since whoopsie-upload-all will 
process all the crashes that it can each time that it runs, there is a race 
condition whereby a crash written as non-root will be processed by 
whoopsie-upload-all running as root, resulting in wrong permissions on the 
related files anyway.

Proposed solution to this:

 - Change apport-noui to be 'instance $MATCH'.  This will result in a separate 
whoopsie-upload-all process spawned each time a new .crash is created.
 - Keep the current semantics of whoopsie-upload-all iterating over *all* 
.crash files that it finds and submitting them.  This ensures that if a 
previous crash is missed out for any reason, we manage to catch it later.
 - Ensure that process_report() can be safely called from multiple processes at 
the same time on the same .crash file (by locking with correct semantics and 
having subsequent calls skip)
 - Handle any necessary file uid changes /within/ whoopsie-upload-all, instead 
of relying on a racy sudo invocation from the upstart job.
 - Disable the current wait_uploaded() behavior unless a timeout argument is 
given explicitly; and also fix the behavior to detect when the .upload file has 
been removed after we started watching.

I believe with those changes, whoopsie-upload-all should give us
reliable report processing in all cases.

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

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

Title:
  whoopsie-upload-all has a wrong check for whether the upload is done

Status in “apport” package in Ubuntu:
  New

Bug description:
  Currently, the way whoopsie-upload-all works is that, whenever a new
  .crash file is seen, /etc/init/apport-noui.conf triggers to run
  whoopsie-upload-all from a single-threaded job that iterates through
  all as-yet-unprocessed .crash files, process them via apport, marks
  them for upload, and then waits for apport to upload them.

  There are several problems with this:

   - The wait for apport to upload them is racy.  Once a report is submitted, 
it is legitimate for something to remove all of the related files (.crash, 
.upload, .uploaded).  On our test infrastructure, that has resulted in buggy 
behavior because the test harness is removing these files /while 
whoopsie-upload-all is polling/, causing it to poll for a very long time 
waiting for a file that will never be found and then time out.
   - waiting for apport to upload is pointless anyway for its designed use, 
since whoopsie-upload-all is called from an upstart job that's 
inotify-triggered so nothing waits for the return from this command anyway.  
The utah scripts appear to currently be waiting for it; however this should be 
non-default, exceptional behavior, because...
   - since apport-noui is not an 'instance' job, as long as the job is running 
(presumably blocking on files that are never going to show up), *newly* created 
.crash files will not be processed.
   - the job furthermore is written to assume that it will be called separately 
for crashes done as different users.  However, since whoopsie-upload-all will 
process all the crashes that it can each time that it runs, there is a race 
condition whereby a crash written as non-root will be processed by 
whoopsie-upload-all running as root, resulting in wrong permissions on the 
related files anyway.

  Proposed solution to this:

   - Change

[Desktop-packages] [Bug 1354323] [NEW] [SVF14212SNW, Realtek ID 233, Speaker, Internal] No sound at all

2014-08-08 Thread Jimmy James

Public bug reported:

Installed ubuntu on sony vaio
but can't hear anything from the speakers.
installed the plugins.
updated everything...

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.2.0-67.101-generic-pae 3.2.60
Uname: Linux 3.2.0-67-generic-pae i686
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: i386
ArecordDevices:
  List of CAPTURE Hardware Devices 
 card 0: PCH [HDA Intel PCH], device 0: HDA Generic [HDA Generic]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jimmyjames   3445 F pulseaudio
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xc081 irq 45'
   Mixer name   : 'Intel PantherPoint HDMI'
   Components   : 'HDA:10ec0233,104d7300,0013 
HDA:80862806,104d7300,0010'
   Controls  : 10
   Simple ctrls  : 4
CurrentDmesg:
 [   22.350209] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
 [   22.596303] [drm:gen6_sanitize_pm] *ERROR* Power management discrepancy: 
GEN6_RP_INTERRUPT_LIMITS expected 1500, was 1206
 [   60.371121] [drm:gen6_sanitize_pm] *ERROR* Power management discrepancy: 
GEN6_RP_INTERRUPT_LIMITS expected 0007, was 1500
 [ 1842.217772] r8169 :0e:00.0: eth0: link up
Date: Fri Aug  8 13:54:20 2014
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_IN:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 3445  jimmyjames  F pulseaudio
   PID ACCESS COMMAND
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [SVF14212SNW, Realtek ID 233, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/15/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: R0210DA
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0210DA:bd07/15/2013:svnSonyCorporation:pnSVF14212SNW:pvrC10HQNXX:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: SVF14212SNW
dmi.product.version: C10HQNXX
dmi.sys.vendor: Sony Corporation

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 precise running-unity

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

Title:
  [SVF14212SNW, Realtek ID 233, Speaker, Internal] No sound at all

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

Bug description:
  Installed ubuntu on sony vaio
  but can't hear anything from the speakers.
  installed the plugins.
  updated everything...

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.2.0-67.101-generic-pae 3.2.60
  Uname: Linux 3.2.0-67-generic-pae i686
  NonfreeKernelModules: wl
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: HDA Generic [HDA Generic]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jimmyjames   3445 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xc081 irq 45'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:10ec0233,104d7300,0013 
HDA:80862806,104d7300,0010'
 Controls  : 10
 Simple ctrls  : 4
  CurrentDmesg:
   [   22.350209] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
   [   22.596303] [drm:gen6_sanitize_pm] *ERROR* Power management discrepancy: 
GEN6_RP_INTERRUPT_LIMITS expected 1500, was 1206
   [   60.371121] [drm:gen6_sanitize_pm] *ERROR* Power management discrepancy: 
GEN6_RP_INTERRUPT_LIMITS expected 0007, was 1500
   [ 1842.217772] r8169 :0e:00.0: eth0: link up
  Date: Fri Aug  8 13:54:20 2014
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 
(20120423)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:

[Desktop-packages] [Bug 1307877] Re: Laptop Monitor Brightness reduced to minimum and disabled after disconnection from external monitor.

2014-08-08 Thread Ryan

No brightness issues when I disconnect the external monitor while the
notebook screen has focus (click on a window or the empty desktop on the
notebook screen).

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

Title:
  Laptop Monitor Brightness reduced to minimum and disabled after
  disconnection from external monitor.

Status in The Linux Kernel:
  New
Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have the following problem under Ubuntu 14.04. As soon as I
  disconnect my external monitor from my Laptop (Lenovo X1 Carbon), the
  brigthness is reduced to minimum (backlight switches off) and I can
  not increase it again. When I use the brightness control keys the
  brightness bar shows that it is set to maximum even though it clearly
  is not. Using the control keys still changes the brightness bar but
  does nothing to the brightness itself.

  Upon a restart of the laptop the brightness returns to its maximum and
  is controllable again.

  I encountered this problem under the Unity version shipped with Ubuntu
  14.04, but it might happen with other desktop managers as well.

  This problem did not exist when my Laptop was running under Ubuntu
  13.10.

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

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

[Desktop-packages] [Bug 118522] Re: Word wrap is too commonly changed to be in preferences, should be a menu

2014-08-08 Thread Bug Watch Updater

** Changed in: gedit
   Status: Confirmed = Fix Released

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

Title:
  Word wrap is too commonly changed to be in preferences, should be a
  menu

Status in Light-Weight Text Editor for Gnome:
  Fix Released
Status in “gedit” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gedit

  Changing from word wrapped to non-wrapped happens too often to be in
  preferences.  It should be on a more easily accessible menu.

  ProblemType: Bug
  Architecture: i386
  Date: Sun Jun  3 11:30:22 2007
  DistroRelease: Ubuntu 7.04
  ExecutablePath: /usr/bin/gedit
  Package: gedit 2.18.1-0ubuntu1
  PackageArchitecture: i386
  ProcCmdline: gedit
  ProcCwd: /home/omegatron
  ProcEnviron:
   LANG=en_US.UTF-8
   
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
   SHELL=/bin/bash
  SourcePackage: gedit
  Uname: Linux Inspiron 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 
i686 GNU/Linux

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

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

[Desktop-packages] [Bug 881259] Re: Crash when losing IRC connection with signal SIGPIPE, Broken pipe in write () from /lib/x86_64-linux-gnu/libpthread.so.0

2014-08-08 Thread madbiologist

Does this still happen on Ubuntu 14.04 Trusty Tahr with pidgin
2.10.9-0ubuntu3.1 ?

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

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

Title:
  Crash when losing IRC connection with signal SIGPIPE, Broken pipe in
  write () from /lib/x86_64-linux-gnu/libpthread.so.0

Status in “pidgin” package in Ubuntu:
  Incomplete

Bug description:
  This has happened several times to me when being connected to an IRC
  server with a bad connection (mobile access through phone in train)
  but I hadn't installed the -dbg package until yet, so I can only
  provide an incomplete backtrace at this point, which however looks
  pretty obvious to me:

  bt
  #0  0x7789807d in write () from /lib/x86_64-linux-gnu/libpthread.so.0
  #1  0x7fffe0204047 in irc_send_len () from /usr/lib/purple-2/libirc.so
  #2  0x7fffe0201ab9 in irc_cmd_quit () from /usr/lib/purple-2/libirc.so
  #3  0x7fffe0203137 in ?? () from /usr/lib/purple-2/libirc.so
  #4  0x74bdff91 in _purple_connection_destroy () from 
/usr/lib/libpurple.so.0
  #5  0x74bcb6ee in purple_account_disconnect () from 
/usr/lib/libpurple.so.0
  #6  0x74bdf1e5 in ?? () from /usr/lib/libpurple.so.0
  #7  0x74efe23b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #8  0x74efca5d in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #9  0x74efd258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #10 0x74efd792 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #11 0x76333db7 in gtk_main () from 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
  #12 0x77f4718e in main ()

  
  (gdb) info registers
  rax0xffe0 -32
  rbx0x00
  rcx0x -1
  rdx0x10   16
  rsi0x792551a0 140737373360544
  rdi0x1b   27
  rbp0x788e5800 0x788e5800
  rsp0x7fffbb20 0x7fffbb20
  r8 0x782b40c0 140737356972224
  r9 0x1f11 7953
  r100x11
  r110x293  659
  r120x10   16
  r130x792e8580 140737373963648
  r140x751ac670 140737305560688
  r150x78212490 140737356309648
  rip0x7789807d 0x7789807d write+45
  eflags 0x293  [ CF AF SF IF ]
  cs 0x33   51
  ss 0x2b   43
  ds 0x00
  es 0x00
  fs 0x00
  gs 0x00

  (gdb) x/16i $pc
  = 0x7789807d write+45: mov(%rsp),%rdi
 0x77898081 write+49: mov%rax,%rdx
 0x77898084 write+52: callq  0x77897b30 
__pthread_disable_asynccancel
 0x77898089 write+57: mov%rdx,%rax
 0x7789808c write+60: add$0x8,%rsp
 0x77898090 write+64: cmp$0xf001,%rax
 0x77898096 write+70: jae0x77898099 write+73
 0x77898098 write+72: retq   
 0x77898099 write+73: mov0x208ed8(%rip),%rcx# 
0x77aa0f78
 0x778980a0 write+80: xor%edx,%edx
 0x778980a2 write+82: sub%rax,%rdx
 0x778980a5 write+85: mov%edx,%fs:(%rcx)
 0x778980a8 write+88: or $0x,%rax
 0x778980ac write+92: jmp0x77898098 write+72
 0x778980ae:nop
 0x778980af:nop

  (gdb) thread apply all backtrace

  Thread 4 (Thread 0x7fffda442700 (LWP 7956)):
  #0  0x748bc773 in poll () from /lib/x86_64-linux-gnu/libc.so.6
  #1  0x74efcf68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #2  0x74efd792 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #3  0x72d22516 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #4  0x74f222b6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #5  0x77890efc in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
  #6  0x748c889d in clone () from /lib/x86_64-linux-gnu/libc.so.6
  #7  0x in ?? ()

  Thread 2 (Thread 0x7fffe1c5e700 (LWP 7954)):
  #0  0x748c1913 in select () from /lib/x86_64-linux-gnu/libc.so.6
  #1  0x7fffe229386a in ?? () from /usr/lib/libtcl8.5.so.0
  #2  0x77890efc in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
  #3  0x748c889d in clone () from /lib/x86_64-linux-gnu/libc.so.6
  #4  0x in ?? ()

  Thread 1 (Thread 0x77ec79a0 (LWP 7953)):
  #0  0x7789807d in write () from /lib/x86_64-linux-gnu/libpthread.so.0
  #1  0x7fffe0204047 in irc_send_len () from /usr/lib/purple-2/libirc.so
  #2  0x7fffe0201ab9 in irc_cmd_quit () from /usr/lib/purple-2/libirc.so
  #3  0x7fffe0203137 in ?? () from

[Desktop-packages] [Bug 1354341] [NEW] 14.10 Wallpapers package

2014-08-08 Thread Iain Farrell

Public bug reported:

This is the bug we'll attach the wallpapers to for the 14.10 release!

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

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

Title:
  14.10 Wallpapers package

Status in “ubuntu-wallpapers” package in Ubuntu:
  New

Bug description:
  This is the bug we'll attach the wallpapers to for the 14.10 release!

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

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

[Desktop-packages] [Bug 1346583] Re: Can't select border color using Unity

2014-08-08 Thread jazzynico

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

** Tags added: ui

** Tags added: color

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

Title:
  Can't select border color using Unity

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

Bug description:
  Whenever I'm using Unity I can't get Inkscape to select the border
  color for an element. Whenever you use the grey bar
  (drive.google.com/file/d/0B54tZJ3fA3lVRHNFRS1XV0RDMzg/edit?usp=sharing)
  to navigate through the colors you can select the color with a right
  click but if you try to click with the left button it won't open the
  menu. Sometimes it does show the menu but it shows it empty for some
  reason (with no options to choose). The only solution to fix it is to
  restart Inkscake.I know it can be done with Shift + Click but it's
  kind of annoying for new users. I'm using Ubuntu 14.04 and Inkscape
  0.48.4  by the way. Sorry for my English, I'm still learning it and
  thanks in advance.

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

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

[Desktop-packages] [Bug 1354350] [NEW] Xorg memory leak on 14.04

2014-08-08 Thread Yosha872

Public bug reported:

Same kind of issue as :  Xorg memory leak on trusty
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1272338

After browsing a lot (Firefox 31,  Opera 12), after more than 10 hours Xorg 
uses over 1 GB (some times up to 2 GB). I have 8 GB RAM.
It seems to me that the system monitor increase the memory leak.

I'm on Linux Mint 17 (64 bits Cinnamon).
APU AMD Athlon 5350 (+ driver AMD Catalyst 14.4).


top - 12:44:32 up 19:08,  2 users,  load average: 1,04, 1,21, 1,30
Tasks: 178 total,   1 running, 177 sleeping,   0 stopped,   0 zombie
%Cpu(s): 22,2 us,  3,7 sy,  0,0 ni, 73,3 id,  0,6 wa,  0,2 hi,  0,0 si,  0,0 st
KiB Mem:   7528392 total,  7139440 used,   388952 free,   368300 buffers
KiB Swap:  9963572 total,   252560 used,  9711012 free.  1592828 cached Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND 
  
 4646 batman20   0 2720,8m 212,7m   6,5m S  35,4  2,9 354:46.81 java
 
 1447 root  20   0 3757,3m 3,305g 140,1m S  24,2 46,0 221:35.96 Xorg
 
 4534 batman20   0  520,9m  23,2m   9,7m S   9,9  0,3  96:48.76 
gnome-system-mo   
 3460 batman20   0  605,9m  16,2m   7,4m S   6,3  0,2   2:50.10 
gnome-terminal   
 2897 batman20   0 1827,5m 186,4m  43,1m S   5,6  2,5  66:31.93 cinnamon


My current system is:
X.Org X Server 1.15.1
Release Date: 2014-04-13
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.2.0-37-generic x86_64 Ubuntu

lsb_release -rd
Description:Linux Mint 17 Qiana
Release:17

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

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

Title:
   Xorg memory leak on 14.04

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

Bug description:
  Same kind of issue as :  Xorg memory leak on trusty
  https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
  intel/+bug/1272338

  After browsing a lot (Firefox 31,  Opera 12), after more than 10 hours Xorg 
uses over 1 GB (some times up to 2 GB). I have 8 GB RAM.
  It seems to me that the system monitor increase the memory leak.

  I'm on Linux Mint 17 (64 bits Cinnamon).
  APU AMD Athlon 5350 (+ driver AMD Catalyst 14.4).

  
  top - 12:44:32 up 19:08,  2 users,  load average: 1,04, 1,21, 1,30
  Tasks: 178 total,   1 running, 177 sleeping,   0 stopped,   0 zombie
  %Cpu(s): 22,2 us,  3,7 sy,  0,0 ni, 73,3 id,  0,6 wa,  0,2 hi,  0,0 si,  0,0 
st
  KiB Mem:   7528392 total,  7139440 used,   388952 free,   368300 buffers
  KiB Swap:  9963572 total,   252560 used,  9711012 free.  1592828 cached Mem

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   

   4646 batman20   0 2720,8m 212,7m   6,5m S  35,4  2,9 354:46.81 java  
   
   1447 root  20   0 3757,3m 3,305g 140,1m S  24,2 46,0 221:35.96 Xorg  
   
   4534 batman20   0  520,9m  23,2m   9,7m S   9,9  0,3  96:48.76 
gnome-system-mo   
   3460 batman20   0  605,9m  16,2m   7,4m S   6,3  0,2   2:50.10 
gnome-terminal   
   2897 batman20   0 1827,5m 186,4m  43,1m S   5,6  2,5  66:31.93 cinnamon  
  

  
  My current system is:
  X.Org X Server 1.15.1
  Release Date: 2014-04-13
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 3.2.0-37-generic x86_64 Ubuntu

  lsb_release -rd
  Description:  Linux Mint 17 Qiana
  Release:  17

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1354350/+subscriptions

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

[Desktop-packages] [Bug 1354350] Re: Xorg memory leak on 14.04

2014-08-08 Thread Yosha872

By the 'system monitor'  I mean the software (v3.6.0) that shows graphs
about CPU and memory.

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

Title:
   Xorg memory leak on 14.04

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

Bug description:
  Same kind of issue as :  Xorg memory leak on trusty
  https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
  intel/+bug/1272338

  After browsing a lot (Firefox 31,  Opera 12), after more than 10 hours Xorg 
uses over 1 GB (some times up to 2 GB). I have 8 GB RAM.
  It seems to me that the system monitor increase the memory leak.

  I'm on Linux Mint 17 (64 bits Cinnamon).
  APU AMD Athlon 5350 (+ driver AMD Catalyst 14.4).

  
  top - 12:44:32 up 19:08,  2 users,  load average: 1,04, 1,21, 1,30
  Tasks: 178 total,   1 running, 177 sleeping,   0 stopped,   0 zombie
  %Cpu(s): 22,2 us,  3,7 sy,  0,0 ni, 73,3 id,  0,6 wa,  0,2 hi,  0,0 si,  0,0 
st
  KiB Mem:   7528392 total,  7139440 used,   388952 free,   368300 buffers
  KiB Swap:  9963572 total,   252560 used,  9711012 free.  1592828 cached Mem

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   

   4646 batman20   0 2720,8m 212,7m   6,5m S  35,4  2,9 354:46.81 java  
   
   1447 root  20   0 3757,3m 3,305g 140,1m S  24,2 46,0 221:35.96 Xorg  
   
   4534 batman20   0  520,9m  23,2m   9,7m S   9,9  0,3  96:48.76 
gnome-system-mo   
   3460 batman20   0  605,9m  16,2m   7,4m S   6,3  0,2   2:50.10 
gnome-terminal   
   2897 batman20   0 1827,5m 186,4m  43,1m S   5,6  2,5  66:31.93 cinnamon  
  

  
  My current system is:
  X.Org X Server 1.15.1
  Release Date: 2014-04-13
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 3.2.0-37-generic x86_64 Ubuntu

  lsb_release -rd
  Description:  Linux Mint 17 Qiana
  Release:  17

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1354350/+subscriptions

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

[Desktop-packages] [Bug 1354313] Re: [Dell Inspiron 5721] Brightness control does not work with 12.04.5(with kernel 3.13)

2014-08-08 Thread Yung Shen

** Tags added: 201210-11865

** Attachment added: 201210-11865.apport
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1354313/+attachment/4172642/+files/201210-11865.apport

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

Title:
  [Dell Inspiron 5721] Brightness control does not work with
  12.04.5(with kernel 3.13)

Status in “linux-lts-trusty” package in Ubuntu:
  New
Status in “xorg” package in Ubuntu:
  New

Bug description:
  This is a system installed with latest stable 12.04.5 image.

  The Brightness key will invoke the osd-notify indicator but the
  display brightness won't change.

  Verifying the value changing in backlight interface, system are using
  acpi_video0 instead:

  Steps to monitor the backlight interfaces:

  Press the brightness key until maxium indicator shows:

  ubuntu@201210-11863:/sys/class/backlight$ cat intel_backlight/brightness ; 
cat acpi_video0/brightness
  3407
  99
  ubuntu@201210-11863:/sys/class/backlight$

  Press the brightness key until to minimum indicator shows:

  ubuntu@201210-11863:/sys/class/backlight$ cat intel_backlight/brightness ; 
cat acpi_video0/brightness
  3407
  0

  
  -

  The workaround found here could solve this issue:
  http://itsfoss.com/fix-brightness-ubuntu-1310/

  -

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.0.1-0ubuntu17.6
  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 Aug  8 03:51:43 2014
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  DkmsStatus: fwts-efi-runtime-dkms, 14.07.00, 3.13.0-32-generic, x86_64: 
installed
  ExtraDebuggingInterest: Yes, even including gdb or git bisection work if 
needed
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:05ba]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] 
(rev ff) (prog-if ff)
  InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 
(20140807.1)
  MachineType: Dell Inc. Inspiron 5721
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=93a24f68-72a1-4335-938a-75f624f57e68 ro quiet splash initcall_debug 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0KNF68
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd10/25/2013:svnDellInc.:pnInspiron5721:pvrA12:rvnDellInc.:rn0KNF68:rvrX01:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron 5721
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1354350] Re: Xorg memory leak on 14.04

2014-08-08 Thread Chris Wilson

Use xrestop to see how much memory X is using on behalf of its clients.

** Package changed: xserver-xorg-video-intel (Ubuntu) = fglrx-installer
(Ubuntu)

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

Title:
   Xorg memory leak on 14.04

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

Bug description:
  Same kind of issue as :  Xorg memory leak on trusty
  https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
  intel/+bug/1272338

  After browsing a lot (Firefox 31,  Opera 12), after more than 10 hours Xorg 
uses over 1 GB (some times up to 2 GB). I have 8 GB RAM.
  It seems to me that the system monitor increase the memory leak.

  I'm on Linux Mint 17 (64 bits Cinnamon).
  APU AMD Athlon 5350 (+ driver AMD Catalyst 14.4).

  
  top - 12:44:32 up 19:08,  2 users,  load average: 1,04, 1,21, 1,30
  Tasks: 178 total,   1 running, 177 sleeping,   0 stopped,   0 zombie
  %Cpu(s): 22,2 us,  3,7 sy,  0,0 ni, 73,3 id,  0,6 wa,  0,2 hi,  0,0 si,  0,0 
st
  KiB Mem:   7528392 total,  7139440 used,   388952 free,   368300 buffers
  KiB Swap:  9963572 total,   252560 used,  9711012 free.  1592828 cached Mem

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   

   4646 batman20   0 2720,8m 212,7m   6,5m S  35,4  2,9 354:46.81 java  
   
   1447 root  20   0 3757,3m 3,305g 140,1m S  24,2 46,0 221:35.96 Xorg  
   
   4534 batman20   0  520,9m  23,2m   9,7m S   9,9  0,3  96:48.76 
gnome-system-mo   
   3460 batman20   0  605,9m  16,2m   7,4m S   6,3  0,2   2:50.10 
gnome-terminal   
   2897 batman20   0 1827,5m 186,4m  43,1m S   5,6  2,5  66:31.93 cinnamon  
  

  
  My current system is:
  X.Org X Server 1.15.1
  Release Date: 2014-04-13
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 3.2.0-37-generic x86_64 Ubuntu

  lsb_release -rd
  Description:  Linux Mint 17 Qiana
  Release:  17

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

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

[Desktop-packages] [Bug 1351911] Re: package libreoffice-writer 1:4.1.3-0ubuntu1 failed to install/upgrade: не удалось скопировать извлечённые данные «./usr/lib/libreoffice/program/libswlo.so» в «/usr

2014-08-08 Thread Björn Michaelsen

unexpected end of stream for a package that has been out for ages
without known issues - corrupted download, not a LibreOffice bug.

** Changed in: libreoffice (Ubuntu)
   Status: New = Invalid

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

Title:
  package libreoffice-writer 1:4.1.3-0ubuntu1 failed to install/upgrade:
  не удалось скопировать извлечённые данные
  «./usr/lib/libreoffice/program/libswlo.so» в
  «/usr/lib/libreoffice/program/libswlo.so.dpkg-new»: неожиданный конец
  файла или потока

Status in “libreoffice” package in Ubuntu:
  Invalid

Bug description:
  This error was happened after executing:
  # apt-get -f install

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: libreoffice-writer 1:4.1.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-22.38-generic 3.11.10.8
  Uname: Linux 3.11.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Sun Aug  3 17:05:29 2014
  ErrorMessage: не удалось скопировать извлечённые данные 
«./usr/lib/libreoffice/program/libswlo.so» в 
«/usr/lib/libreoffice/program/libswlo.so.dpkg-new»: неожиданный конец файла или 
потока
  InstallationDate: Installed on 2012-03-01 (884 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  MarkForUpload: True
  SourcePackage: libreoffice
  Title: package libreoffice-writer 1:4.1.3-0ubuntu1 failed to install/upgrade: 
не удалось скопировать извлечённые данные 
«./usr/lib/libreoffice/program/libswlo.so» в 
«/usr/lib/libreoffice/program/libswlo.so.dpkg-new»: неожиданный конец файла или 
потока
  UpgradeStatus: Upgraded to saucy on 2014-06-01 (62 days ago)

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

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

[Desktop-packages] [Bug 1351480] Re: Metacity-common Critical issue

2014-08-08 Thread Christopher M. Penalver

Not In Progress as outlined in https://wiki.ubuntu.com/Bugs/Bug statuses
.

** Changed in: metacity (Ubuntu)
   Status: In Progress = Incomplete

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

Title:
  Metacity-common Critical issue

Status in “metacity” package in Ubuntu:
  Incomplete

Bug description:
  When 1 installs Metacity-common file from upgrade in Ubuntu 14.10 it wants to 
Remove Unity  and compiz. when 1 does so it removes the whole desktop and not 
able to run the desktop properly task bars and tool bar is removed and only 
shows wall paper area. 
  when 1 removes Metacity-common, and attempts to install unity and compiz back 
it wont let you and says has held broken packages in the process
  --- 
  ApportVersion: 2.14.5-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  darkangel   1777 F pulseaudio
   /dev/snd/controlC0:  darkangel   1777 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=569c56dd-f25c-4a2d-bd00-ca52486d4cea
  InstallationDate: Installed on 2014-08-01 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140731)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: eMachines EL1360G
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic 
root=UUID=4288519c-1dca-4080-92dd-ecb76fb750e3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-6-generic N/A
   linux-backports-modules-3.16.0-6-generic  N/A
   linux-firmware1.132
  RfKill:
   
  Tags:  utopic
  Uname: Linux 3.16.0-6-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/16/2011
  dmi.bios.vendor: AMI
  dmi.bios.version: P01-C1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: EL1360G
  dmi.board.vendor: eMachines
  dmi.chassis.type: 3
  dmi.chassis.vendor: eMachines
  dmi.modalias: 
dmi:bvnAMI:bvrP01-C1:bd11/16/2011:svneMachines:pnEL1360G:pvr:rvneMachines:rnEL1360G:rvr:cvneMachines:ct3:cvr:
  dmi.product.name: EL1360G
  dmi.sys.vendor: eMachines

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

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

[Desktop-packages] [Bug 1353051] Re: No libreoffice-evolution package in Ubuntu 14.04

2014-08-08 Thread Björn Michaelsen

** Changed in: libreoffice (Ubuntu)
   Importance: Undecided = Wishlist

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

Title:
  No libreoffice-evolution package in Ubuntu 14.04

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  Hi,

  why is there no package for libreoffice-evolution (and other e.g.
  exchange) connections any more since precise? This is crucial for
  connection the standard addressbook with theese external DataSources.

  Greets
  Axel

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

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

[Desktop-packages] [Bug 1220426] Re: [nvidia-prime]Freeze while using touchpad

2014-08-08 Thread Raja

Hi All,

This is Raja from NVIDIA-Linux support team.

Can someone share the exact repro steps to reproduce this issue?

Also, Please do share the nvidia-bug report by triggering the nvidia-
bug-report.sh from root user.

Here the notebook list, what we grep from this thread. Will try on one
of the available notebook.

Acer Aspire 5750G
Acer E1-570G
Acer V3-571G
ASUS B400VC
ASUS G750JM
ASUS N43SL
ASUS N46VM
ASUS K53S
ASUS K53SC
ASUS K53SV
ASUS K55VD
ASUS N550JK
ASUS N56JR
ASUS S550C
ASUS UX32VD
ASUS X75V
Clevo W230ST
Dell M3800
HP ENVY TS 15
Lenovo G700
Lenovo G710
Lenovo Ideapad U410
Lenovo Thinkpad T430
MSI CX61 2PC
Packard Bell EASYNOTE ENTV 11
Samsung Chronos 17
Toshiba Satellite S50-A
Toshiba Satellite S55

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

Title:
  [nvidia-prime]Freeze while using touchpad

Status in “nvidia-graphics-drivers-319” package in Ubuntu:
  Triaged
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Triaged
Status in “nvidia-prime” package in Ubuntu:
  Triaged

Bug description:
  I'm using an Optimus laptop (Asus N43SL)
  nvidia-prime is installed, so my nvidia dedicated graphics card (GT 540m) is 
in use.

  Once in a while, my screen will freeze, only when I use my touchpad.
  This does not happen with my USB mouse.
  This does not happen either when I uninstall nvidia-prime and use my intel 
integrated graphics (HD3000).

  I can temporarily solve the issue by doing a VT switch.

  
  In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: 
touchpad found each time I did a VT switch and regained control.

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

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

[Desktop-packages] [Bug 1291052] Re: calc: formula bar is not visible

2014-08-08 Thread Steffen Michalek

version now is
  Version: 4.3.0.4
  Build-ID: 430m0(Build:4)
bug still present, even after full remove of packages (purge) and 
reinstallation.

For my work, the bug is severe: It is the main instrument of editing
formula

The new screenshot shows, that the formula bar (german: Rechenleiste) 
is even not found in the list of bars, which can be edited in the options.
Seems like calc cannot find information about that bar - but reserves the
(grey) place for it.

** Attachment added: list of bar, which can be edited - but no Rechenleiste 
found
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1291052/+attachment/4172720/+files/14-08-08_calc_without_formula_bar_options.png

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

Title:
  calc: formula bar is not visible

Status in “libreoffice” package in Ubuntu:
  Confirmed

Bug description:
  in LibreOffice Calc:
  Even, if the formula bar (german: Rechenleiste) is chosen to be displayed in 
the menue View (german: Ansicht), there is no formula bar visible.
  The area above the sheet is enlarged / reduced when toggling the choice in 
the menue, but only a grey area appears /disappears.
  Even that narrow handle field at the left end of other bars is not visible.

  System and installed LibreOffice packages:

  Ubuntu 13.10
  Ii  libreoffice-avmedia-backend-gstreamer 
1:4.2.1-0ubuntu1~saucy1   amd64 GStreamer 
backend for LibreOffice
  ii  libreoffice-base-core 
1:4.2.1-0ubuntu1~saucy1   amd64 office 
productivity suite -- shared library
  ii  libreoffice-calc  
1:4.2.1-0ubuntu1~saucy1   amd64 office 
productivity suite -- spreadsheet
  ii  libreoffice-common
1:4.2.1-0ubuntu1~saucy1   all   office 
productivity suite -- arch-independent files
  ii  libreoffice-core  
1:4.2.1-0ubuntu1~saucy1   amd64 office 
productivity suite -- arch-dependent files
  ii  libreoffice-draw  
1:4.2.1-0ubuntu1~saucy1   amd64 office 
productivity suite -- drawing
  ii  libreoffice-help-de   
1:4.2.1-0ubuntu1~saucy1   all   office 
productivity suite -- German help
  ii  libreoffice-impress   
1:4.2.1-0ubuntu1~saucy1   amd64 office 
productivity suite -- presentation
  ii  libreoffice-java-common   
1:4.2.1-0ubuntu1~saucy1   all   office 
productivity suite -- arch-independent Java support files
  ii  libreoffice-kde   
1:4.2.1-0ubuntu1~saucy1   amd64 office 
productivity suite -- KDE integration
  ii  libreoffice-l10n-de   
1:4.2.1-0ubuntu1~saucy1   all   office 
productivity suite -- German language package
  ii  libreoffice-l10n-en-gb
1:4.2.1-0ubuntu1~saucy1   all   office 
productivity suite -- English_british language package
  ii  libreoffice-l10n-en-za
1:4.2.1-0ubuntu1~saucy1   all   office 
productivity suite -- English_southafrican language package
  ii  libreoffice-math  
1:4.2.1-0ubuntu1~saucy1   amd64 office 
productivity suite -- equation editor
  ii  libreoffice-pdfimport 
1:4.2.1-0ubuntu1~saucy1   amd64 PDF Import 
component for LibreOffice
  ii  libreoffice-style-human   
1:4.2.1-0ubuntu1~saucy1   all   office 
productivity suite -- Human symbol style
  ii  libreoffice-style-oxygen  
1:4.2.1-0ubuntu1~saucy1   all   office 
productivity suite -- Oxygen symbol style
  ii  libreoffice-writer
1:4.2.1-0ubuntu1~saucy1   amd64 office 
productivity suite -- word processor

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

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

[Desktop-packages] [Bug 1354392] [NEW] apport-collect does not confirm when upload complete

2014-08-08 Thread d❤vid seaward

Public bug reported:

Steps to reproduce:

* Run `apport-collect -p PACKAGE-NAME BUG-NUMBER`
* Confirm access to/from Launchpad
* Click Send button
* Window immediately closes

What should happen:

* Once upload complete, confirmation appears (options: in browser, new
window, command line)

What happens instead:

* No confirmation. (Although I noticed there were new messages on
Launchpad.)

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apport 2.14.1-0ubuntu3.3
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportLog:
 
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Aug  8 13:00:50 2014
InstallationDate: Installed on 2014-04-24 (105 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  apport-collect does not confirm when upload complete

Status in “apport” package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  * Run `apport-collect -p PACKAGE-NAME BUG-NUMBER`
  * Confirm access to/from Launchpad
  * Click Send button
  * Window immediately closes

  What should happen:

  * Once upload complete, confirmation appears (options: in browser, new
  window, command line)

  What happens instead:

  * No confirmation. (Although I noticed there were new messages on
  Launchpad.)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apport 2.14.1-0ubuntu3.3
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportLog:
   
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug  8 13:00:50 2014
  InstallationDate: Installed on 2014-04-24 (105 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1346583] Re: Can't select border color using Unity

2014-08-08 Thread Liam P. White

Might you be able to test this in a terminal:

$ LIBOVERLAY_SCROLLBAR=0 inkscape

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

Title:
  Can't select border color using Unity

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

Bug description:
  Whenever I'm using Unity I can't get Inkscape to select the border
  color for an element. Whenever you use the grey bar
  (drive.google.com/file/d/0B54tZJ3fA3lVRHNFRS1XV0RDMzg/edit?usp=sharing)
  to navigate through the colors you can select the color with a right
  click but if you try to click with the left button it won't open the
  menu. Sometimes it does show the menu but it shows it empty for some
  reason (with no options to choose). The only solution to fix it is to
  restart Inkscake.I know it can be done with Shift + Click but it's
  kind of annoying for new users. I'm using Ubuntu 14.04 and Inkscape
  0.48.4  by the way. Sorry for my English, I'm still learning it and
  thanks in advance.

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

-- 
Mailing list: https://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 1220426] Re: [nvidia-prime]Freeze while using touchpad

2014-08-08 Thread Flávio Augusto Ribeiro de Faria

Raja, you can also add Dell Vostro 3300 to this list.


On Fri, Aug 8, 2014 at 7:01 AM, Raja r...@nvidia.com wrote:

 Hi All,

 This is Raja from NVIDIA-Linux support team.

 Can someone share the exact repro steps to reproduce this issue?

 Also, Please do share the nvidia-bug report by triggering the nvidia-
 bug-report.sh from root user.

 Here the notebook list, what we grep from this thread. Will try on one
 of the available notebook.

 Acer Aspire 5750G
 Acer E1-570G
 Acer V3-571G
 ASUS B400VC
 ASUS G750JM
 ASUS N43SL
 ASUS N46VM
 ASUS K53S
 ASUS K53SC
 ASUS K53SV
 ASUS K55VD
 ASUS N550JK
 ASUS N56JR
 ASUS S550C
 ASUS UX32VD
 ASUS X75V
 Clevo W230ST
 Dell M3800
 HP ENVY TS 15
 Lenovo G700
 Lenovo G710
 Lenovo Ideapad U410
 Lenovo Thinkpad T430
 MSI CX61 2PC
 Packard Bell EASYNOTE ENTV 11
 Samsung Chronos 17
 Toshiba Satellite S50-A
 Toshiba Satellite S55

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1220426

 Title:
   [nvidia-prime]Freeze while using touchpad

 Status in “nvidia-graphics-drivers-319” package in Ubuntu:
   Triaged
 Status in “nvidia-graphics-drivers-331” package in Ubuntu:
   Triaged
 Status in “nvidia-prime” package in Ubuntu:
   Triaged

 Bug description:
   I'm using an Optimus laptop (Asus N43SL)
   nvidia-prime is installed, so my nvidia dedicated graphics card (GT
 540m) is in use.

   Once in a while, my screen will freeze, only when I use my touchpad.
   This does not happen with my USB mouse.
   This does not happen either when I uninstall nvidia-prime and use my
 intel integrated graphics (HD3000).

   I can temporarily solve the issue by doing a VT switch.


   In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech
 Touchpad: touchpad found each time I did a VT switch and regained control.

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319/+bug/1220426/+subscriptions


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

Title:
  [nvidia-prime]Freeze while using touchpad

Status in “nvidia-graphics-drivers-319” package in Ubuntu:
  Triaged
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Triaged
Status in “nvidia-prime” package in Ubuntu:
  Triaged

Bug description:
  I'm using an Optimus laptop (Asus N43SL)
  nvidia-prime is installed, so my nvidia dedicated graphics card (GT 540m) is 
in use.

  Once in a while, my screen will freeze, only when I use my touchpad.
  This does not happen with my USB mouse.
  This does not happen either when I uninstall nvidia-prime and use my intel 
integrated graphics (HD3000).

  I can temporarily solve the issue by doing a VT switch.

  
  In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: 
touchpad found each time I did a VT switch and regained control.

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

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

[Desktop-packages] [Bug 1220426] Re: [nvidia-prime]Freeze while using touchpad

2014-08-08 Thread Michael Steenbeek

Raja, the steps to reproduce:

1. Use of the laptop in your post and install Ubuntu.
2. Install the proprietary NVIDIA driver.
3. Switch to using the NVIDIA card using nvidia-settings.
4. Use the touchpad for a while.

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

Title:
  [nvidia-prime]Freeze while using touchpad

Status in “nvidia-graphics-drivers-319” package in Ubuntu:
  Triaged
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Triaged
Status in “nvidia-prime” package in Ubuntu:
  Triaged

Bug description:
  I'm using an Optimus laptop (Asus N43SL)
  nvidia-prime is installed, so my nvidia dedicated graphics card (GT 540m) is 
in use.

  Once in a while, my screen will freeze, only when I use my touchpad.
  This does not happen with my USB mouse.
  This does not happen either when I uninstall nvidia-prime and use my intel 
integrated graphics (HD3000).

  I can temporarily solve the issue by doing a VT switch.

  
  In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: 
touchpad found each time I did a VT switch and regained control.

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

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

[Desktop-packages] [Bug 1354424] Re: Xorg crashed with SIGABRT in xf86DeleteScreen()

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

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

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1354424/+attachment/4172781/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1354424/+attachment/4172784/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1354424/+attachment/4172794/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1354424/+attachment/4172796/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1354424/+attachment/4172797/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1354424/+attachment/4172798/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1354424/+attachment/4172799/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1353926

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  Xorg crashed with SIGABRT in xf86DeleteScreen()

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

Bug description:
  Xorg crashed with SIGABRT in xf86DeleteScreen()

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-core 2:1.15.1-0ubuntu9
  ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6
  Uname: Linux 3.16.0-5-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.5-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CrashCounter: 1
  Date: Fri Aug  8 09:13:26 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.14, 3.16.0-5-generic, x86_64: installed
   virtualbox, 4.3.14, 3.16.0-6-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] 
(rev 12) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Device [8086:0037]
  InstallationDate: Installed on 2014-05-16 (83 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-5-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so
   xf86DeleteScreen ()
   InitOutput ()
   ?? ()
   __libc_start_main (main=0x7f7e2f546dd0, argc=11, argv=0x7fff0dd4e648, 
init=optimized out, fini=optimized out, rtld_fini=optimized out, 
stack_end=0x7fff0dd4e638) at libc-start.c:287
  Title: Xorg crashed with SIGABRT in xf86DeleteScreen()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/19/2009
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: TCIBX10H.86A.0027.2009.1119.1517
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH55HC
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE70933-502
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrTCIBX10H.86A.0027.2009.1119.1517:bd11/19/2009:svn:pn:pvr:rvnIntelCorporation:rnDH55HC:rvrAAE70933-502:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.54-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.3-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri Aug  8 09:13:28 2014
  xserver.configfile: default

[Desktop-packages] [Bug 1230091] Re: [enhancement] Trusted Session surface management (required for appstore app trust model), modal subwindows

What is that bug?

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

Title:
  [enhancement] Trusted Session surface management (required for
  appstore app trust model), modal subwindows

Status in Content sharing/picking infrastructure and service:
  Triaged
Status in Mir:
  Triaged
Status in Unity Mir:
  Triaged
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  Confirmed
Status in “signon” package in Ubuntu:
  Confirmed
Status in “unity-mir” package in Ubuntu:
  Confirmed

Bug description:
  (I'm filing this as a bug in order to be able to point other people to
  it, and to track its progress; if there's a blueprint containing this
  task, please let me know)

  Some components (such as the Online Accounts trusted helper) need to
  be able to pop-up a window (typically, a dialog) on top of the running
  application. Such windows should be modal to the application, that is
  the user should not be able to interact with the application while the
  modal window is displayed on top of them. This also means that in the
  task switcher one shouldn't see two windows, but only the topmost
  modal window (and parts of the application window, in case the modal
  window on top is a non-fullscreen dialog).

  For developers, this API already exists in Qt: see 
https://qt-project.org/doc/qt-5.1/qtgui/qwindow.html#fromWinId
  It needs to be implemented in the QPA plugin, so feel free to add the 
relevant projects to the bug report.

  From jdstrand
  This is a hard requirement for application confinement because of our trust 
model-- permission to access sensitive data by AppStore apps is typically 
granted or denied at the time of access (caching the result for later use as 
appropriate), so users have a context for the access being requested. We do 
this instead of throwing up a permissions prompt at installation. However, for 
it to work, trusted helpers like online accounts and location require this 
functionality from unity-mir. A trust-store is also being implemented so other 
services like calendar and contacts can do the same. Because this feature is 
not implemented, the implementation for online accounts, location and the 
trust-store is blocked and appstore apps are therefore able to access these 
services without the user knowing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/content-hub/+bug/1230091/+subscriptions

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

[Desktop-packages] [Bug 1354424] Re: Xorg crashed with SIGABRT in xf86DeleteScreen()

2014-08-08 Thread Chris Wilson

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

Note that this a failure on an error path, but the crash will be fixed
by

commit 8d135867c886e98fa0bc5a7a21a1b3d84851daaa
Author: Chris Wilson ch...@chris-wilson.co.uk
Date:   Fri Aug 8 14:04:14 2014 +0100

sna: Update check for static driver data on loading error

Bugzilla: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1354424
Signed-off-by: Chris Wilson ch...@chris-wilson.co.uk

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

Title:
  Xorg crashed with SIGABRT in xf86DeleteScreen()

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

Bug description:
  Xorg crashed with SIGABRT in xf86DeleteScreen()

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-core 2:1.15.1-0ubuntu9
  ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6
  Uname: Linux 3.16.0-5-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.5-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CrashCounter: 1
  Date: Fri Aug  8 09:13:26 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.14, 3.16.0-5-generic, x86_64: installed
   virtualbox, 4.3.14, 3.16.0-6-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] 
(rev 12) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Device [8086:0037]
  InstallationDate: Installed on 2014-05-16 (83 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-5-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so
   xf86DeleteScreen ()
   InitOutput ()
   ?? ()
   __libc_start_main (main=0x7f7e2f546dd0, argc=11, argv=0x7fff0dd4e648, 
init=optimized out, fini=optimized out, rtld_fini=optimized out, 
stack_end=0x7fff0dd4e638) at libc-start.c:287
  Title: Xorg crashed with SIGABRT in xf86DeleteScreen()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/19/2009
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: TCIBX10H.86A.0027.2009.1119.1517
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH55HC
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE70933-502
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrTCIBX10H.86A.0027.2009.1119.1517:bd11/19/2009:svn:pn:pvr:rvnIntelCorporation:rnDH55HC:rvrAAE70933-502:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.54-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.3-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri Aug  8 09:13:28 2014
  xserver.configfile: default
  xserver.errors:
   intel: Failed to load module dri3 (module does not exist, 0)
   intel: Failed to load module present (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id9027 
   vendor AOC
  xserver.version: 2:1.15.1-0ubuntu9

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

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

[Desktop-packages] [Bug 1354439] [NEW] [2324BY9, Realtek ALC269VC, Speaker, Internal] fails after a while

2014-08-08 Thread KarstenM

Public bug reported:

Often occurs when playing youtube videos (sound stops in the middle of
the video). After restart sometimes no sound at all. Several restarts
usually fix the problem.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  karsten2080 F pulseaudio
 /dev/snd/pcmC0D0p:   karsten2080 F...m pulseaudio
CurrentDesktop: Unity
Date: Fri Aug  8 15:02:39 2014
InstallationDate: Installed on 2012-08-05 (733 days ago)
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_Type: Sound works for a while, then breaks
Title: [2324BY9, Realtek ALC269VC, Speaker, Internal] fails after a while
UpgradeStatus: Upgraded to trusty on 2014-04-24 (106 days ago)
dmi.bios.date: 04/22/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ETA1WW (2.61 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2324BY9
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA1WW(2.61):bd04/22/2014:svnLENOVO:pn2324BY9:pvrThinkPadX230:rvnLENOVO:rn2324BY9:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2324BY9
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

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

Title:
  [2324BY9, Realtek ALC269VC, Speaker, Internal] fails after a while

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

Bug description:
  Often occurs when playing youtube videos (sound stops in the middle of
  the video). After restart sometimes no sound at all. Several restarts
  usually fix the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  karsten2080 F pulseaudio
   /dev/snd/pcmC0D0p:   karsten2080 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Fri Aug  8 15:02:39 2014
  InstallationDate: Installed on 2012-08-05 (733 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Sound works for a while, then breaks
  Title: [2324BY9, Realtek ALC269VC, Speaker, Internal] fails after a while
  UpgradeStatus: Upgraded to trusty on 2014-04-24 (106 days ago)
  dmi.bios.date: 04/22/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA1WW (2.61 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324BY9
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA1WW(2.61):bd04/22/2014:svnLENOVO:pn2324BY9:pvrThinkPadX230:rvnLENOVO:rn2324BY9:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324BY9
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1354444] [NEW] Ubuntu 14.04 random screen freeze while Normal OS activites

2014-08-08 Thread Jerome Rousselot

Public bug reported:


Bug is very similar to 1184451

Intel driver, intermittent black screens between 1 and 10 s.

Using the keyboard, moving the mouse, switching terminals help bringing
back graphics.

Bug occurs without significant CPU activity.

My computer is almost unusable for work.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,gnomecompat,grid,imgpng,snap,mousepoll,place,resize,session,move,unitymtgrabhandles,regex,vpswitch,wall,animation,expo,ezoom,workarounds,fade,scale,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Aug  8 14:10:40 2014
DistUpgraded: 2014-04-22 21:18:59,342 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:21da]
InstallationDate: Installed on 2011-07-23 (1112 days ago)
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
MachineType: LENOVO 4293AA6
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=921169a1-61c5-4efa-acc5-631be67f09a0 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2014-04-22 (107 days ago)
dmi.bios.date: 05/18/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET46WW (1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4293AA6
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn4293AA6:pvrThinkPadX220:rvnLENOVO:rn4293AA6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4293AA6
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.11.1+14.04.20140701-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Fri Aug  8 11:57:10 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id4204 
 vendor AUO
xserver.version: 2:1.15.1-0ubuntu2

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


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

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

Title:
  Ubuntu 14.04 random screen freeze while Normal OS activites

Status in “xorg” package in Ubuntu:
  New

Bug description:
  
  Bug is very similar to 1184451

  Intel driver, intermittent black screens between 1 and 10 s.

  Using the keyboard, moving the mouse, switching terminals help
  bringing back graphics.

  Bug occurs without significant CPU activity.

  My computer is almost unusable for work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,gnomecompat,grid,imgpng,snap,mousepoll,place,resize,session,move,unitymtgrabhandles,regex,vpswitch,wall,animation,expo,ezoom,workarounds,fade,scale,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Aug  8 14:10:40 2014
  DistUpgraded: 2014-04-22 21:18:59,342 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on

[Desktop-packages] [Bug 1181106] Re: Failed to change profile to A2DP in 13.04 (Raring), 13.10 (saucy), and 14.04 (trusty)

2014-08-08 Thread Brooks B

Confirm that this is effecting 14.04 Trusty.


$ pacmd list-cards
. . . 
index: 4
name: bluez_card.00_18_9A_2E_B3_D1
driver: module-bluetooth-device.c
owner module: 28
properties:
device.description = PHILIPS BTM630
device.string = 00:18:9A:2E:B3:D1
device.api = bluez
device.class = sound
device.bus = bluetooth
device.form_factor = headset
bluez.path = /org/bluez/1121/hci0/dev_00_18_9A_2E_B3_D1
bluez.class = 0x240404
bluez.name = PHILIPS BTM630
device.icon_name = audio-headset-bluetooth
device.intended_roles = phone
profiles:
hsp: Telephony Duplex (HSP/HFP) (priority 20, available: 
unknown)
a2dp: High Fidelity Playback (A2DP) (priority 10, available: 
unknown)
off: Off (priority 0, available: yes)
active profile: off
ports:
headset-output: Headset (priority 0, latency offset 0 usec, 
available: unknown)
properties:

headset-input: Headset (priority 0, latency offset 0 usec, 
available: unknown)
properties:

$ pacmd set-card-profile 4 a2dp
Welcome to PulseAudio! Use help for usage information.
 Failed to set card profile to 'a2dp'.

$ pactl list | grep -i module-bluetooth
Name: module-bluetooth-policy
Name: module-bluetooth-discover
Name: module-bluetooth-device
Driver: module-bluetooth-device.c

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

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

Title:
  Failed to change profile to A2DP in 13.04 (Raring), 13.10 (saucy), and
  14.04 (trusty)

Status in Bluez Utilities:
  New
Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  I upgraded to 13.04 recently and my A2DP profile, which had been
  working great under 12.10 is suddenly gone.  Neither my blueman applet
  nor the built-in bluetooth manager applet can connect my external
  bluetooth speaker to the A2DP profile.  They can connect to the
  bluetooth device itself just fine.

  Steps I'm using:

  * using blueman, I can connect to the external bluetooth speaker and view the 
device in the devices listing
  * I can connect the device to the Audio sink and I get a message saying it is 
now connected and will show in the PulseAudio mixer
  * After connecting the external speaker to the audio sink, I can also see the 
device in the Play sound through listing in the Sound system control panel, 
but the icon has a circle with a line through it.
  * but if I right-click the device and choose Audio Profile from the context 
menu and try to select High Fidelity Playback (A2DP) as the new profile, I 
get an error message stating failed to change profile to a2dp

  I've already added Enable=Socket in /etc/bluetooth/audio.conf,
  without that I can't pair my headset. Now I can pair it, but I can't
  activate the A2DP profile.

  When I try to activate it, I see this message in my syslog :
  pulseaudio[2603]: [pulseaudio] module-bluetooth-device.c: Profile has no 
transport

  I tried the kernel 3.9.0 because of a sound problem with my soundcard,
  this kernel fixed my soundcard problem, but A2DP still doesn't work

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

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

[Desktop-packages] [Bug 1330108] Re: SVG exported from LibreOffice Draw messes up rotated text in Inkscape

2014-08-08 Thread ~suv

On OS X 10.7.5, latest Firefox (31.0), latest LO (4.3.0):

The vertical text in the SVG file exported by LO does _not_ render as
expected in current Firefox, nor in Chromium (recent devel snapshot) nor
in Squiggle (Batik 1.7). In my understanding, this is a (confirmed)
regression in LO's SVG export: the 'transform()' attribute should be
applied to the top-level text element, or to a parent container
element, but not to a (nested) tspan element:

Attribute:
  ‘transform’
Elements on which the attribute may be specified:
  ‘a’, ‘circle’, ‘clipPath’, ‘defs’, ‘ellipse’, ‘foreignObject’, ‘g’, ‘image’, 
‘line’, ‘path’, ‘polygon’, ‘polyline’, ‘rect’, ‘switch’, ‘text’, ‘use’
http://www.w3.org/TR/SVG11/attindex.html

Upstream ticket:
- 57215: Wrong text rotation in SVG Export (rotated text appears as 
non-rotated):
  https://bugs.freedesktop.org/show_bug.cgi?id=57215
«The attribute transform is in an element tspan in the example. But an 
element tspan does not allow an attribute transform, see list of attributes 
in http://www.w3.org/TR/SVG/text.html#TSpanElement. It should be on the element 
g. The syntax would allow it on the element text too, but neither Seamonkey 
nor Inkscape will rotate the text then.»
https://bugs.freedesktop.org/show_bug.cgi?id=57215#c13

Earlier report filed for Inkscape:
- Bug #1277517 “Rotation exported from LibreOffice Calc not honored”
  https://bugs.launchpad.net/inkscape/+bug/1277517

Proposing to link as duplicate to bug #1277517 (closed as 'Invalid' for
project Inkscape).

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

** Tags added: svg

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

Title:
  SVG exported from LibreOffice Draw messes up rotated text in Inkscape

Status in Inkscape: A Vector Drawing Tool:
  Triaged
Status in “inkscape” package in Ubuntu:
  Triaged

Bug description:
  When exporting a svg file to eps, vertical text gets messed up.

  Steps to reproduce:
  1. create a LibreOffice Draw document with vertical text (rotate it 90°)
  2. export drawing to svg
  3. $ inkscape -E drawing.eps drawing.svg
  4. open drawing.eps with your favourite document viewer
  - the vertical text is now horizontal

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: inkscape 0.48.4-3ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 14 19:53:11 2014
  InstallationDate: Installed on 2013-07-29 (319 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: inkscape
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (21 days ago)

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

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

[Desktop-packages] [Bug 978424] Re: Enable SSL by default for irc.ubuntu.com

This bug was fixed in the package irssi - 0.8.16-1ubuntu2

---
irssi (0.8.16-1ubuntu2) utopic; urgency=medium

  * Build witout libval-dev, it's in universe.
 -- Daniel Holbach daniel.holb...@ubuntu.com   Thu, 07 Aug 2014 14:32:37 +0200

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

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

Title:
  Enable SSL by default for irc.ubuntu.com

Status in xchat:
  Unknown
Status in “empathy” package in Ubuntu:
  Invalid
Status in “hexchat” package in Ubuntu:
  Invalid
Status in “irssi” package in Ubuntu:
  Fix Released
Status in “pidgin” package in Ubuntu:
  New
Status in “xchat” package in Ubuntu:
  New

Bug description:
  Enable SSL by default for irc.ubuntu.com / freenode (and other SSL-
  enhanced networks) to ensure privacy and integrity.

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

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

[Desktop-packages] [Bug 1342786] Re: Brightness OSD killed by nvidia-prime

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

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

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

Title:
  Brightness OSD killed by nvidia-prime

Status in “nvidia-prime” package in Ubuntu:
  Confirmed

Bug description:
  Installed Ubuntu 14.04 64 bit on an Acer Aspire 5750ZG Nvidia Optimus
  laptop.

  There was no issue with brightness until I installed the nvidia-prime
  package: I could adjust brightness in System Settings as well as with
  the brightness keys (Fn+left/right arrows). The brightness on-screen
  display used to appear fine on the screen while adjusting brightness
  with the function keys.

  After I had installed nvidia-prime, I could still adjust brightness in
  System Settings but no longer with the brightness keys. The osd
  disappeared, too.

  Adding acpi_osi=Linux to GRUB_CMDLINE_LINUX_DEFAULT in
  /etc/default/grub fixed the brightness keys but did not bring back the
  osd.

  Removing nvidia-prime did not help. The osd was lost for good.

  Reinstalled Ubuntu 14.04 formatting the / partition and now everything
  is fine again. Installed bumblebee with nvidia-331 and still
  everything is fine.

  The nvidia-prime packages seems to do something that breaks both the
  brightness keys (which can be fixed with acpi_osi=Linux) and the osd
  (which I could not bring back).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1342786/+subscriptions

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

[Desktop-packages] [Bug 1330527] Re: Inkscape: unable to access all objects after ungroup

2014-08-08 Thread jazzynico

 I'll try to investigate the crash later.

Crash not reproduced on Windows XP, Inkscape trunk revision 13502.
Possibly fixed by the patch committed revision 13474.

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

Title:
  Inkscape: unable to access all objects after ungroup

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

Bug description:
  After ungrouping, I am unable to access all objects. It seems one of
  them disappears completely.

  I am attaching the incriminated file.

  After playing around a bit with that, I managed to access the sky
  part (Earth, ray arrows...) by Object - Clip - Release.

  But there is still at least one object missing - the gray factories
  background. I am unable to access that.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: inkscape 0.48.4-3ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Jun 16 16:48:30 2014
  ExecutablePath: /usr/bin/inkscape
  InstallationDate: Installed on 2013-10-26 (233 days ago)
  InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016)
  SourcePackage: inkscape
  UpgradeStatus: Upgraded to trusty on 2014-06-11 (5 days ago)

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

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

[Desktop-packages] [Bug 1304531] Re: Removing an external monitor will move a maximized window to the current workspace

2014-08-08 Thread HRJ

I updated the compiz packages today, and I also noticed a reappearance
of the problem.

compiz (1:0.9.11.1+14.04.20140701-0ubuntu1) to
1:0.9.11.2+14.04.20140714-0ubuntu1

Should we open a fresh bug report?

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

Title:
  Removing an external monitor will move a maximized window to the
  current workspace

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  Fix Released
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  Many users tend to have maximized window opened on other workspaces
  and use an external monitor such as a projector or one connected to a
  laptop docking station.  When removing this monitor, these maximized
  windows will get shuffled to the current workspace.  This can be
  aggravating for users and is not a good user experience.

  [Test case]

  1. Have an external monitor.
  2. Use multiple workspaces.
  3. Open a window and maximize it on a workspace such as workspace 2.
  4. Move to another workspace such as workspace 3.
  5. Remove the external monitor.

  [Regression potential]

  The code here is quite fragile and can be prone to some unexpected
  behaviors.  I took great care in trying to make sure no new
  regressions are caused by this fix, but there may be some corner case
  that is unaccounted for.  Also note that there are already some broken
  behaviors in this area that are unfixed by this code, so keep that in
  mind when testing that it truly isn't a regression.

  * Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-
  trusty-sru-2.debdiff *

  Original Description:

  Removing an external monitor when using multiple workspaces will cause
  maximized windows on other workspaces to move to the current
  workspace.

  Scenario:
  1. Have an external monitor.
  2. Use multiple workspaces.
  3. Open a window and maximize it on a workspace such as workspace 2.
  4. Move to another workspace such as workspace 3.
  5. Remove the external monitor.

  Expected behavior:
  Maximized window will remain on the workspace it was opened on.

  Observed behavior:
  Maximized window moves to the current workspace

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

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

[Desktop-packages] [Bug 1304531] Re: Removing an external monitor will move a maximized window to the current workspace

2014-08-08 Thread Christopher Townsend

Yes, please open a new bug report and I will investigate.

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

Title:
  Removing an external monitor will move a maximized window to the
  current workspace

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  Fix Released
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  Many users tend to have maximized window opened on other workspaces
  and use an external monitor such as a projector or one connected to a
  laptop docking station.  When removing this monitor, these maximized
  windows will get shuffled to the current workspace.  This can be
  aggravating for users and is not a good user experience.

  [Test case]

  1. Have an external monitor.
  2. Use multiple workspaces.
  3. Open a window and maximize it on a workspace such as workspace 2.
  4. Move to another workspace such as workspace 3.
  5. Remove the external monitor.

  [Regression potential]

  The code here is quite fragile and can be prone to some unexpected
  behaviors.  I took great care in trying to make sure no new
  regressions are caused by this fix, but there may be some corner case
  that is unaccounted for.  Also note that there are already some broken
  behaviors in this area that are unfixed by this code, so keep that in
  mind when testing that it truly isn't a regression.

  * Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-
  trusty-sru-2.debdiff *

  Original Description:

  Removing an external monitor when using multiple workspaces will cause
  maximized windows on other workspaces to move to the current
  workspace.

  Scenario:
  1. Have an external monitor.
  2. Use multiple workspaces.
  3. Open a window and maximize it on a workspace such as workspace 2.
  4. Move to another workspace such as workspace 3.
  5. Remove the external monitor.

  Expected behavior:
  Maximized window will remain on the workspace it was opened on.

  Observed behavior:
  Maximized window moves to the current workspace

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

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

[Desktop-packages] [Bug 1304531] Re: Removing an external monitor will move a maximized window to the current workspace

2014-08-08 Thread Christopher Townsend

Also, just quickly looking between the two versions, the only thing that
changed was in the Scale plugin and I don't see how that has caused this
to regress.  I will need to dig in to this.

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

Title:
  Removing an external monitor will move a maximized window to the
  current workspace

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  Fix Released
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  Many users tend to have maximized window opened on other workspaces
  and use an external monitor such as a projector or one connected to a
  laptop docking station.  When removing this monitor, these maximized
  windows will get shuffled to the current workspace.  This can be
  aggravating for users and is not a good user experience.

  [Test case]

  1. Have an external monitor.
  2. Use multiple workspaces.
  3. Open a window and maximize it on a workspace such as workspace 2.
  4. Move to another workspace such as workspace 3.
  5. Remove the external monitor.

  [Regression potential]

  The code here is quite fragile and can be prone to some unexpected
  behaviors.  I took great care in trying to make sure no new
  regressions are caused by this fix, but there may be some corner case
  that is unaccounted for.  Also note that there are already some broken
  behaviors in this area that are unfixed by this code, so keep that in
  mind when testing that it truly isn't a regression.

  * Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-
  trusty-sru-2.debdiff *

  Original Description:

  Removing an external monitor when using multiple workspaces will cause
  maximized windows on other workspaces to move to the current
  workspace.

  Scenario:
  1. Have an external monitor.
  2. Use multiple workspaces.
  3. Open a window and maximize it on a workspace such as workspace 2.
  4. Move to another workspace such as workspace 3.
  5. Remove the external monitor.

  Expected behavior:
  Maximized window will remain on the workspace it was opened on.

  Observed behavior:
  Maximized window moves to the current workspace

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

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

[Desktop-packages] [Bug 1311399] Re: Ubuntu 14.04 forgets Display Settings from monitors.xml / xorg.conf (Dual-Screen Setup)

2014-08-08 Thread Alwin Mark

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

For me the best solution, was to delete all output information except of
the one i was setting in the ~/.config/monitors.xml

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

Title:
  Ubuntu 14.04 forgets Display Settings from monitors.xml / xorg.conf
  (Dual-Screen Setup)

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  Steps to Reproduce:
  1. Install Ubuntu Gnome14.04 on a freshly formatted PC with 2 screens
  2. Using Additional Drivers, install latest Nvidia driver (331)
  3. Modify screen settings (e.g. change position of 2 screens as depicted in 
attached Screens_good.gif)
  4. Turn secondary screen off and back on - OR - reboot
  5. Observe that screen settings have been reverted

  Actual Results:
  Ubuntu forgets the screen settings made in either NVidia-settings or Ubuntu's 
own Displays tool. The screen settings are reverted to the default (screen 2 
to the right of screen 1) after reboot or when turning the second screen off 
and back on.

  Expected Results:
  Ubuntu should apply the user's defined screen settings when the second screen 
is turned on.

  Notes:
  The test PC has two devices connected to a GeForce GTX 680 (Gigabyte 
GV-N680OC-2GD) card:
  1. Samsung SyncMaster screen via DVI
  2. Yamaha RX-V 661 5.1 surround receiver via HDMI (recognized by Ubuntu as a 
second screen)
  Encountered in Ubuntu Gnome 14.04, 64 bit
  Encountered with NVidia drivers 331, 331 update and 304 (legacy)

  Reading Xorg.0.log, one can see that the user's desired settings are
  actually applied more than once (exerpts):

  [ 5.252] (II) NVIDIA(0): Validated MetaModes:
  [ 5.252] (II) NVIDIA(0): 
DVI-I-0:1920x1200_60+0+1080,HDMI-0:1920x1080_60i+1920+0
  [ 5.252] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 2280
  [ 5.275] (--) NVIDIA(0): DPI set to (93, 95); computed from UseEdidDpi 
X config
  [ 5.275] (--) NVIDIA(0): option
  [ 5.275] (--) Depth 24 pixmap format is 32 bpp
  [ 5.275] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect 
memory
  [ 5.275] (II) NVIDIA: access.
  [ 5.281] (II) NVIDIA(0): Setting mode 
DVI-I-0:1920x1200_60+0+1080,HDMI-0:1920x1080_60i+1920+0

  At the very end, an unknown process takes over and reverts the
  previous desired settings to the undesired default (line 3):

  [ 7.196] (II) XKB: reuse xkmfile 
/var/lib/xkb/server-A237F4D5ECC0A2998042D3B58D9A7CE5E820BA0E.xkm
  [ 7.208] (II) NVIDIA(0): Setting mode NULL
  [ 7.270] (II) NVIDIA(0): Setting mode DVI-I-0: nvidia-auto-select 
@1920x1200 +0+0 {ViewPortIn=1920x1200, ViewPortOut=1920x1200+0+0}
  [ 7.469] (II) XKB: reuse xkmfile 
/var/lib/xkb/server-A237F4D5ECC0A2998042D3B58D9A7CE5E820BA0E.xkm
  [ 7.474] (II) XKB: reuse xkmfile 
/var/lib/xkb/server-A237F4D5ECC0A2998042D3B58D9A7CE5E820BA0E.xkm
  [ 7.496] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (CRT-0)) does 
not support NVIDIA
  [ 7.496] (II) NVIDIA(GPU-0): 3D Vision stereo.
  [41.097] (II) XKB: reuse xkmfile 
/var/lib/xkb/server-A237F4D5ECC0A2998042D3B58D9A7CE5E820BA0E.xkm
  [   511.720] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (CRT-0)) does 
not support NVIDIA

  Attachments: screenshots of desired screen settings (Screens_good.gif) and 
default screen settings (Screens.gif)
  This issue occurs regardless of whether the user makes the desired settings 
in Ubuntu's Display tool or NVidia-Settings.
  This issue persists even after specifically saving the desired settings to 
xorg.conf using NVidia-Settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Apr 22 18:14:34 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed
   nvidia-331-updates, 331.38, 3.13.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 680] [10de:1180] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:353c]
  InstallationDate: Installed on 2014-04-20 (2 days ago)

[Desktop-packages] [Bug 1342786] Re: Brightness OSD killed by nvidia-prime

2014-08-08 Thread Antonio J

I have an ASUS X552CL with a nvidia gforce 710M and the bug appeared
when I was using Ubuntu Gnome 14.04.1. I installed nvidia-331 drivers
with bumblebee (my laptop has two video cards, Intel and Nvidia)
(trought this video https://www.youtube.com/watch?v=nMqVFeFk9rI) and all
works fine but a week after I couldn't use brightness control neither
the keyboard nor gnome settings (the indicator dissapeared!).

After this, I installed Ubuntu 14.04.1 (original) and all works fine but
when I installed bumblebee and all necesary packs to use my two video
cards, the brightness indicator disappeared again, and keys of
brightness control didn't work.

I tryed to fix it trought:

1) Fist fix:

At first, I write this to know which video card manage the bright of my
display

ls /sys/class/backlight/
acpi_video0  acpi_video1  intel_backlight

After this I created a configuration file to intel videocard with:

sudo touch /usr/share/X11/xorg.conf.d/20-intel.conf
sudo gedit /usr/share/X11/xorg.conf.d/20-intel.conf

And I added the next parameters:

Section Device
Identifier  card0
Driver  intel
Option  Backlight  intel_backlight
BusID   PCI:0:2:0
EndSection

I rebooted my laptop and brightness control still didn't work.

Source (In spanish, sorry): http://www.atareao.es/ubuntu/corrigiendo-el-
brillo-en-ubuntu-trusty-tahr/

2) Second fix: the same fix that Arizsló, but didn't work.

3) Third fix:

I change the drivers from nvidia-331 to nvidia-340 and the brightness
control still didn't work.

Now, I only use intel videocard to brightness control works.

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

Title:
  Brightness OSD killed by nvidia-prime

Status in “nvidia-prime” package in Ubuntu:
  Confirmed

Bug description:
  Installed Ubuntu 14.04 64 bit on an Acer Aspire 5750ZG Nvidia Optimus
  laptop.

  There was no issue with brightness until I installed the nvidia-prime
  package: I could adjust brightness in System Settings as well as with
  the brightness keys (Fn+left/right arrows). The brightness on-screen
  display used to appear fine on the screen while adjusting brightness
  with the function keys.

  After I had installed nvidia-prime, I could still adjust brightness in
  System Settings but no longer with the brightness keys. The osd
  disappeared, too.

  Adding acpi_osi=Linux to GRUB_CMDLINE_LINUX_DEFAULT in
  /etc/default/grub fixed the brightness keys but did not bring back the
  osd.

  Removing nvidia-prime did not help. The osd was lost for good.

  Reinstalled Ubuntu 14.04 formatting the / partition and now everything
  is fine again. Installed bumblebee with nvidia-331 and still
  everything is fine.

  The nvidia-prime packages seems to do something that breaks both the
  brightness keys (which can be fixed with acpi_osi=Linux) and the osd
  (which I could not bring back).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1342786/+subscriptions

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

[Desktop-packages] [Bug 1061195] Re: Can't create EWS or MAPI account

2014-08-08 Thread m...@papersolve.com

I was experiencing this exact same bug as well.  Based on information I
read in the corresponding RedHat report
(https://bugzilla.redhat.com/show_bug.cgi?id=879773) I was able to get
this to work by removing all the Evolution configuration directories
(which did have some prior attempts at configuration from a long time
ago) and killing and restarting Evolution:

[Fri Aug  8 10:02:25 EDT 2014]  mike at ossy in ~  
  
↪ rm -rf .config/evolution/ .cache/evolution/ .local/share/evolution/
[Fri Aug  8 10:02:40 EDT 2014]  mike at ossy in ~  
  
↪ pkill evolution

I went through the account wizard again, and after adding the password
prompt showed up and I was able to type the password and add the
account.

** Bug watch added: Red Hat Bugzilla #879773
   https://bugzilla.redhat.com/show_bug.cgi?id=879773

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

Title:
  Can't create EWS or MAPI account

Status in “evolution-data-server” package in Ubuntu:
  Confirmed

Bug description:
  Evolution appears unable to create an EW or MAPI account. All the
  steps proceed normally, including fetching the URL (for EWS) or
  authenticating (for MAPI). However, at the conclusion of account
  creation process, no actual account appears in the list.

  I've tried starting Evolution from the command line using various
  DEBUG_ variables and there are no EWS- or MAPI-specific errors. So I'm
  not exactly sure what to do next.

  I am fairly certain the problem doesn't lie with my corporate Exchange
  server, as web mail works fine and any other EWS-capable client (like
  the mail app in Android).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: evolution 3.6.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Wed Oct  3 12:40:28 2012
  InstallationMedia: Ubuntu-Server 12.10 Quantal Quetzal - Beta amd64 
(20120925)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.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-data-server/+bug/1061195/+subscriptions

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

[Desktop-packages] [Bug 1319941] Re: libreoffice draw / impress crash if user service publishing is disabled in avahi

** Description changed:

- Both loimpress and lodraw fail to start with an error message related to
- avahi:
+ [Impact]
+ 
+  * Impress and Draw will not work (Crash) with Avahi enabled, but user/all 
publishing disabled.
+  * The fix is basically some check before free, and return earlier if failing.
+ 
+ [Test Case]
+ 
+  * Restart avahi daemon with either disable-user-service-publishing=yes or 
disable-publishing=yes.  This will cause the crash.
+  * Patch was also tested with avahi on, making sure it publishes and with 
avahi just to make sure a new bug was not introduced.
+ 
+ [Regression Potential]
+ 
+  * If a regression occurs it would be avahi specific and should only affect 
Impress and Draw.  It will be less likely to manifest in an outright crash now.
+  * I was unable to test actually using a remote control. (but the avahi 
service was published which is the only part my fix touches.
+ 
+ [Other Info]
+ Avahi is NOT enabled in Upstream LibreOffice builds (so don't try to test 
them for this bug) although pushing to have source fix included in 4.2.x and 
4.3.x anyways
+ Master Upstream fix (TB4.4): 
http://cgit.freedesktop.org/libreoffice/core/commit/?id=3c57701cf0a169bd8d1893d1b2271d48b8072147
+ Proposed 4.3: https://gerrit.libreoffice.org/#/c/10816/
+ Proposed 4.2: https://gerrit.libreoffice.org/#/c/10822/
+ 
+ 
+ Both loimpress and lodraw fail to start with an error message related to 
avahi:
  
  $ loimpress
  avahi_entry_group_new() failed: Not permitted
  soffice.bin: client.c:626: avahi_client_free: Assertion `client' failed.
  
  $ ps ax | grep avahi
-  7617 pts/0S+ 0:00 grep --color=auto avahi
+  7617 pts/0S+ 0:00 grep --color=auto avahi
  21356 ?S  0:07 avahi-daemon: running [hostname.local]
  21380 ?S  0:00 avahi-daemon: chroot helper
  
  This is the backtrace of the crash:
  
  $ cat gdbtrace.log
  warning: Currently logging to gdbtrace.log.  Turn the logging off and on to 
make the new setting effective.
  warning: Unable to find libthread_db matching inferior's thread library, 
thread debugging will not be available.
  
  Program received signal SIGABRT, Aborted.
  0x741f2f79 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:56
  56../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
  #0  0x741f2f79 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:56
  #1  0x741f6388 in __GI_abort () at abort.c:89
  #2  0x741ebe36 in __assert_fail_base (fmt=0x7433d718 %s%s%s:%u: 
%s%sAssertion `%s' failed.\n%n, assertion=assertion@entry=0x7fffe95b6919 
client, file=file@entry=0x7fffe95b6910 client.c, line=line@entry=626, 
function=function@entry=0x7fffe95b6fe0 avahi_client_free) at assert.c:92
  #3  0x741ebee2 in __GI___assert_fail (assertion=0x7fffe95b6919 
client, file=0x7fffe95b6910 client.c, line=626, function=0x7fffe95b6fe0 
avahi_client_free) at assert.c:101
  #4  0x7fffe95af06b in avahi_client_free () from 
/usr/lib/x86_64-linux-gnu/libavahi-client.so.3
  #5  0x7fffbac7c40c in ?? () from 
/usr/lib/libreoffice/program/../program/libsdlo.so
  #6  0x7fffbac7c678 in ?? () from 
/usr/lib/libreoffice/program/../program/libsdlo.so
  #7  0x7fffe95aec2c in ?? () from 
/usr/lib/x86_64-linux-gnu/libavahi-client.so.3
  #8  0x7fffe95af3aa in avahi_client_new () from 
/usr/lib/x86_64-linux-gnu/libavahi-client.so.3
  #9  0x7fffbac7c8a5 in ?? () from 
/usr/lib/libreoffice/program/../program/libsdlo.so
  #10 0x7fffbac7d195 in ?? () from 
/usr/lib/libreoffice/program/../program/libsdlo.so
  #11 0x7fffbac7d30b in ?? () from 
/usr/lib/libreoffice/program/../program/libsdlo.so
  #12 0x7fffbac74756 in ?? () from 
/usr/lib/libreoffice/program/../program/libsdlo.so
  #13 0x7fffbaa12b9b in ?? () from 
/usr/lib/libreoffice/program/../program/libsdlo.so
  #14 0x7fffbab83bc0 in sd_component_getFactory () from 
/usr/lib/libreoffice/program/../program/libsdlo.so
  
  This is on trusty.
  
  libreoffice-impress 1:4.2.3~rc3-0ubuntu

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

Title:
  libreoffice draw / impress crash if user service publishing is
  disabled in avahi

Status in LibreOffice Productivity Suite:
  Confirmed
Status in “libreoffice” package in Ubuntu:
  Confirmed
Status in “libreoffice” package in Debian:
  Fix Released

Bug description:
  [Impact]

   * Impress and Draw will not work (Crash) with Avahi enabled, but user/all 
publishing disabled.
   * The fix is basically some check before free, and return earlier if failing.

  [Test Case]

   * Restart avahi daemon with either disable-user-service-publishing=yes or 
disable-publishing=yes.  This will cause the crash.
   * Patch was also tested with avahi on, making sure it publishes and with 
avahi just to make sure a new bug was not

[Desktop-packages] [Bug 1354023] Re: Screen contents are not being redrawn unless moving window off screen.

2014-08-08 Thread Piotr Kloc

After some tests I can say it's compiz or nvidia blob. I have forced
full scene repaints in CCSM for now.

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

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

Title:
  Screen contents are not being redrawn unless moving window off screen.

Status in “compiz” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  New

Bug description:
  Nvidia 340.24 Ubuntu 14.04.1 GTX 550Ti

  Let's say that I'm scrolling through web page in firefox. It's not redrawing 
so I have to drag window for it to redraw.
  Another example: I'm in Ubuntu Tweak, just toggled some stuff but it's not 
showing button change. I have to drag window off screen to properly redraw.
  Another example: Nautilus, I'm scrolling but it's not showing that it's 
scrolling. Again need to move window off screen and back to see changes.
  Another one: I'm writing right now and when I press Enter nothing happens, I 
have to press it again but cursor goes two rows down. Oh and now word rows is 
still in previous line with cursor so I have one ghost cursor and one in front.

  I think it's understandable now.

  I have this bug since 14.04 alpha, I though it's some dev crap and
  just made switch to Arch. Since 14.04.1 you have nice Vsync so I'm
  back.

  My guess: Someone at Cannonical tried to implement reuse screen
  contents from Kwin but failed.

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

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

[Desktop-packages] [Bug 955355] Re: Compiz does not allow focusing on the desktop with click-to-focus disabled

2014-08-08 Thread TomasHnyk

14.04.01 and still present.

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

Title:
  Compiz does not allow focusing on the desktop with click-to-focus
  disabled

Status in Compiz:
  Confirmed
Status in Compiz Core:
  Confirmed
Status in “compiz” package in Ubuntu:
  Confirmed

Bug description:
  With click-to-focus disabled (follow focus), compiz does not allow
  focusing on the desktop with any non-minimized windows present.  If
  click-to-focus is enabled, then compiz behaves as expected.

  Steps to reproduce:

  - disable click-to-focus in compiz
  - open at least one application
  - try to rename a file on the desktop

  At this point the desktop will not receive focus, and typing will go
  into the last focused window, not the desktop (for file rename).

  lsb_release info:
    Ubuntu precise (development branch) 12.04

  compiz version:
    1:0.9.7.0+bzr3035-0ubuntu1

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

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

[Desktop-packages] [Bug 682788] Re: Improve Unity Global Menu

2014-08-08 Thread Aleve Sicofante

May I ask what fix was released, Marco, and what's exactly the nature of
the fix? Has it been fixed for the current Ubuntu version (14.04.1) or
is it fixed for an upcoming one? If it's the latter, which one: 14.10
or/and 14.04.2?

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

Title:
  Improve Unity Global Menu

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Invalid
Status in Unity:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity-control-center” package in Ubuntu:
  Triaged
Status in Baltix GNU/Linux:
  Confirmed

Bug description:
  ===+++ _ ! ALL USERS ! _ +++===
  ===+++ READ THIS BEFORE MAKING A COMMENT OR MODIFICATION +++===

  IMPORTANT 1: Please don't post any me too message; use the Does
  this bug affect you? feature you can find a bit above this bug
  description on Launchpad.

  IMPORTANT 2: Do not post anything if you haven't read all comments to
  verify that your point hasn't been made. If you feel tempted to stop
  reading because there are too many messages, that is a strong
  indicator that you shouldn't add even more comments. Developers have a
  tough time to find anything if you post redundant stuff. So please
  abstain from doing that.

  =
  Global menu in general (not only in Unity) is very unergonomic on large 
screens (see the attached screenshot) because if you have a small window 
somewhere near the low right corner you have to move the cursor all the way up 
to to panel to reach the menu. I understand why the global menu was used for 
the netbook edition (it saves space and most windows are maximized), but since 
Unity is intended to be for the desktop edition there should be an option to 
switch to the traditional position of the app menu. It would be welcomed by 
many desktop users. Please try to find a solution for it that works.

  A commonly suggested solution is:
   [ ] Global Menu on
   [ ] Global Menu off
   [ ] Global Menu only for maximized windows
  The default is usually suggested as either the first (on) or last (on only 
for maximized windows).

  -
  Desired change:

  Implement the 'Enhanced Menu' project for 12.10.  This project will
  address the issue described in this bug and also issues described in
  the duplicates of this bus.  Note this is the 'official' bug that
  tracks the implementation of this project.

  The following options will be added to 'System Settings/Appearance':

  ---
  Menus
  Location:Global/Local
  Visibility:  Hidden/Always displayed
  ---

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

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

[Desktop-packages] [Bug 1304531] Re: Removing an external monitor will move a maximized window to the current workspace

2014-08-08 Thread HRJ

@townsend

The specific regressions I am seeing are:

After switching monitors, windows can't be moved to a different workspace until 
they are un-maximised.
Also, windows that were not-maximised before the new monitor was plugged in, 
end up spanning multiple workspaces.

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

Title:
  Removing an external monitor will move a maximized window to the
  current workspace

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  Fix Released
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  Many users tend to have maximized window opened on other workspaces
  and use an external monitor such as a projector or one connected to a
  laptop docking station.  When removing this monitor, these maximized
  windows will get shuffled to the current workspace.  This can be
  aggravating for users and is not a good user experience.

  [Test case]

  1. Have an external monitor.
  2. Use multiple workspaces.
  3. Open a window and maximize it on a workspace such as workspace 2.
  4. Move to another workspace such as workspace 3.
  5. Remove the external monitor.

  [Regression potential]

  The code here is quite fragile and can be prone to some unexpected
  behaviors.  I took great care in trying to make sure no new
  regressions are caused by this fix, but there may be some corner case
  that is unaccounted for.  Also note that there are already some broken
  behaviors in this area that are unfixed by this code, so keep that in
  mind when testing that it truly isn't a regression.

  * Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-
  trusty-sru-2.debdiff *

  Original Description:

  Removing an external monitor when using multiple workspaces will cause
  maximized windows on other workspaces to move to the current
  workspace.

  Scenario:
  1. Have an external monitor.
  2. Use multiple workspaces.
  3. Open a window and maximize it on a workspace such as workspace 2.
  4. Move to another workspace such as workspace 3.
  5. Remove the external monitor.

  Expected behavior:
  Maximized window will remain on the workspace it was opened on.

  Observed behavior:
  Maximized window moves to the current workspace

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

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

[Desktop-packages] [Bug 1347305] Re: Address fields are grey when composing messages

2014-08-08 Thread Guido Zoellner

Thank you for pointing to the bugzilla report. By now, there has been quite 
some input over there and the developers have responded, too. Personal 
preferences for the look may vary. But to me, this is a usability issue: 
editable text fields should be recognisable as editable text fields. You can 
find the current discussion at
https://bugzilla.mozilla.org/show_bug.cgi?id=1042780
including this screenshot of Ubuntu 14.04 LTS with a workaround Thunderbird 
31 compose window
https://bug1042780.bugzilla.mozilla.org/attachment.cgi?id=8467753

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

Title:
  Address fields are grey when composing messages

Status in “thunderbird” package in Ubuntu:
  Confirmed

Bug description:
  When composing a message, any address field that does not have the
  cursor is shown as grey. While this is at first only a cosmetic
  glitch, it is also serious usability issue: Usually any field that can
  be edited is white and text that can't be edited is simply drawn grey.
  Now it looks like Thunderbird does not allow editing of the recipient
  addresses. Only when you try it regardless you discover that it is
  still editible.

  I attached a screenshot showing a stuffed up composer window.

  This bug appeared with the latest update of Thunderbird that was
  installed today.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: thunderbird 1:31.0+build1-0ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kaymes 2516 F pulseaudio
  BuildID: 20140721092545
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Wed Jul 23 10:37:17 2014
  ExecutablePath: /usr/lib/thunderbird/thunderbird
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Deutsch (DE) Language Pack - langpack...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2014-07-02 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  IpRoute:
   default via 10.33.0.1 dev eth0  proto static 
   10.33.0.0/22 dev eth0  proto kernel  scope link  src 10.33.1.197  metric 1
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  LocalLibraries: 
/home/kaymes/.thunderbird/dymzcbig.default/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/components/Linux_x86_64-gcc3/libcalbasecomps.so
  PrefSources:
   prefs.js
   
[Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
  Profiles: Profile0 (Default) - LastVersion=31.0/20140721092545 (In use)
  RelatedPackageVersions:
   rhythmbox-mozilla 3.0.2-0ubuntu2
   totem-mozilla 3.10.1-1ubuntu4
  RfKill:
   
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   Jul 23 08:56:13 uqbox kernel: [427030.548782] [drm] Setting output timings 
on SDVOB failed
   Jul 23 09:37:38 uqbox kernel: [429515.541016] [drm] Setting output timings 
on SDVOB failed
   Jul 23 10:06:02 uqbox kernel: [431219.445267] [drm] Setting output timings 
on SDVOB failed
   Jul 23 10:07:12 uqbox kernel: [431289.957320] [drm] Setting output timings 
on SDVOB failed
   Jul 23 10:23:06 uqbox kernel: [432243.381132] MATLAB[25882]: segfault at 8 
ip 7f2f4507bcfe sp 7f2f06cc5320 error 4
  dmi.bios.date: 10/27/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0J468K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd10/27/2011:svnDellInc.:pnOptiPlex960:pvr:rvnDellInc.:rn0J468K:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 960
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1336462] Re: Make apport collect some Power information

This bug was fixed in the package apport - 2.14.5-0ubuntu4

---
apport (2.14.5-0ubuntu4) utopic; urgency=medium

  [ Steve Langasek ]
  * Fix invalid shebang lines for apport-noui maintainer scripts which I
somehow overlooked.

  [ Martin Pitt ]
  * Add data/general-hooks/powerpc.py: Collect some PowerPC[64] information.
Thanks to Thierry FAUCK! (LP: #1336462)
 -- Martin Pitt martin.p...@ubuntu.com   Fri, 08 Aug 2014 15:13:16 +0200

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

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

Title:
  Make apport collect some Power information

Status in “apport” package in Ubuntu:
  Fix Released

Bug description:
  On power/ppc64el system, we would need to enhance current apport reporting 
tool which some information like file content or commands output including
/proc/device-tree/
  /proc/loadavg
  /proc/locks
 /proc/misc
  /proc/swaps
  /proc/version
  /dev/nvram
  /var/log/platform
  ppc64_cpu --smt
  ppc64_cpu --cores-present
  ppc64_cpu --cores-on
  ppc64_cpu --run-mode
 ppc64_cpu --frequency
 ppc64_cpu --dscr

  Readme says : For complete instructions, see 
/usr/share/doc/apport/package-hooks.txt but
  cat: /usr/share/doc/apport/package-hooks.txt: No such file or directory

  Do I understand correctly I would need to create a file (for example)
  named : /usr/share/apport/general-hooks/power.py ?

  Other questions:
  Do you have common functions to put output of commands in logfile ?
  do you have common functions to copy config file tree content to log file or 
should I create the list of file and copy content of each file to the logfile ?

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

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

[Desktop-packages] [Bug 1354313] Re: [Dell Inspiron 5721] Brightness control does not work with 12.04.5(with kernel 3.13)

2014-08-08 Thread Ara Pulido

** Also affects: hwe-next
   Importance: Undecided
   Status: New

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

Title:
  [Dell Inspiron 5721] Brightness control does not work with
  12.04.5(with kernel 3.13)

Status in HWE Next Project:
  New
Status in “linux-lts-trusty” package in Ubuntu:
  New
Status in “xorg” package in Ubuntu:
  New

Bug description:
  This is a system installed with latest stable 12.04.5 image.

  The Brightness key will invoke the osd-notify indicator but the
  display brightness won't change.

  Verifying the value changing in backlight interface, system are using
  acpi_video0 instead:

  Steps to monitor the backlight interfaces:

  Press the brightness key until maxium indicator shows:

  ubuntu@201210-11863:/sys/class/backlight$ cat intel_backlight/brightness ; 
cat acpi_video0/brightness
  3407
  99
  ubuntu@201210-11863:/sys/class/backlight$

  Press the brightness key until to minimum indicator shows:

  ubuntu@201210-11863:/sys/class/backlight$ cat intel_backlight/brightness ; 
cat acpi_video0/brightness
  3407
  0

  
  -

  The workaround found here could solve this issue:
  http://itsfoss.com/fix-brightness-ubuntu-1310/

  -

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.0.1-0ubuntu17.6
  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 Aug  8 03:51:43 2014
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  DkmsStatus: fwts-efi-runtime-dkms, 14.07.00, 3.13.0-32-generic, x86_64: 
installed
  ExtraDebuggingInterest: Yes, even including gdb or git bisection work if 
needed
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:05ba]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] 
(rev ff) (prog-if ff)
  InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 
(20140807.1)
  MachineType: Dell Inc. Inspiron 5721
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=93a24f68-72a1-4335-938a-75f624f57e68 ro quiet splash initcall_debug 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0KNF68
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd10/25/2013:svnDellInc.:pnInspiron5721:pvrA12:rvnDellInc.:rn0KNF68:rvrX01:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron 5721
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1354474] Re: chromium-browser crashed with SIGSEGV in base::MessageLoop::RunTask()

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

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

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1354474/+attachment/4172891/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1354474/+attachment/4172894/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1354474/+attachment/4172897/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1354474/+attachment/4172898/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1354474/+attachment/4172899/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1354474/+attachment/4172902/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1354474/+attachment/4172903/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1229021
   chromium-browser crashed with SIGSEGV

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  chromium-browser crashed with SIGSEGV in base::MessageLoop::RunTask()

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

Bug description:
  No idea what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: chromium-browser 35.0.1916.153-0ubuntu1~pkg1029
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.5-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug  8 14:36:16 2014
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  DiskUsage:
   b'DateisystemTyp  Gr\xc3\xb6\xc3\x9fe Benutzt Verf. Verw% 
Eingeh\xc3\xa4ngt auf\n/dev/sda5  ext4   98G 73G   21G   79% 
/\nnone   tmpfs 4,0K   0  4,0K0% /sys/fs/cgroup\nudev   
devtmpfs  3,9G4,0K  3,9G1% /dev\ntmpfs  tmpfs 788M
1,2M  787M1% /run\nnone   tmpfs 5,0M4,0K  5,0M1% 
/run/lock\nnone   tmpfs 3,9G 18M  3,9G1% /run/shm\nnone 
  tmpfs 100M 60K  100M1% /run/user\n'
   
   Inodes:
   b'DateisystemInodes IBenutzt IFrei IUse% Eingeh\xc3\xa4ngt 
auf\n/dev/sda56,3M 464K  5,8M8% /\nnone 984K
4  984K1% /sys/fs/cgroup\nudev 974K  544  973K1% 
/dev\ntmpfs984K  599  984K1% /run\nnone 984K
7  984K1% /run/lock\nnone 984K   42  984K1% 
/run/shm\nnone 984K   39  984K1% /run/user\n'
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2013-12-22 (229 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131221)
  ProcCmdline: chromium-browser\ --type=gpu-process\ 
--channel=19420.0.1201971480\ --supports-dual-gpus=false\ 
--gpu-driver-bug-workarounds=1,9,13\ --disable-accelerated-video-decode\ 
--gpu-vendor-id=0x8086\ --gpu-device-id=0x0126\ --gpu-driver-vendor\ 
--gpu-driver-versi
  SegvAnalysis:
   Segfault happened at: 0x7f3009a22f38:movl   $0x1337,0x0
   PC (0x7f3009a22f38) ok
   source $0x1337 ok
   destination 0x0 (0x) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? () from /usr/lib/chromium-browser/libs/libcontent.so
   base::MessageLoop::RunTask(base::PendingTask const) () from 
/usr/lib/chromium-browser/libs/libbase.so
   base::MessageLoop::DeferOrRunPendingTask(base::PendingTask const) () from 
/usr/lib/chromium-browser/libs/libbase.so
   base::MessageLoop::DoDelayedWork(base::TimeTicks*) () from 
/usr/lib/chromium-browser/libs/libbase.so
   ?? () from /usr/lib/chromium-browser/libs/libbase.so
  Title: chromium-browser crashed with SIGSEGV in base::MessageLoop::RunTask()
  UpgradeStatus: No upgrade log present (probably

[Desktop-packages] [Bug 1311399] Re: Ubuntu 14.04 forgets Display Settings from monitors.xml / xorg.conf (Dual-Screen Setup)

2014-08-08 Thread Alwin Mark

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

Forget it, I had to do both!

so editing monitors.xml and pkill -9 -f gnome-settings-daemon at
startup

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

Title:
  Ubuntu 14.04 forgets Display Settings from monitors.xml / xorg.conf
  (Dual-Screen Setup)

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  Steps to Reproduce:
  1. Install Ubuntu Gnome14.04 on a freshly formatted PC with 2 screens
  2. Using Additional Drivers, install latest Nvidia driver (331)
  3. Modify screen settings (e.g. change position of 2 screens as depicted in 
attached Screens_good.gif)
  4. Turn secondary screen off and back on - OR - reboot
  5. Observe that screen settings have been reverted

  Actual Results:
  Ubuntu forgets the screen settings made in either NVidia-settings or Ubuntu's 
own Displays tool. The screen settings are reverted to the default (screen 2 
to the right of screen 1) after reboot or when turning the second screen off 
and back on.

  Expected Results:
  Ubuntu should apply the user's defined screen settings when the second screen 
is turned on.

  Notes:
  The test PC has two devices connected to a GeForce GTX 680 (Gigabyte 
GV-N680OC-2GD) card:
  1. Samsung SyncMaster screen via DVI
  2. Yamaha RX-V 661 5.1 surround receiver via HDMI (recognized by Ubuntu as a 
second screen)
  Encountered in Ubuntu Gnome 14.04, 64 bit
  Encountered with NVidia drivers 331, 331 update and 304 (legacy)

  Reading Xorg.0.log, one can see that the user's desired settings are
  actually applied more than once (exerpts):

  [ 5.252] (II) NVIDIA(0): Validated MetaModes:
  [ 5.252] (II) NVIDIA(0): 
DVI-I-0:1920x1200_60+0+1080,HDMI-0:1920x1080_60i+1920+0
  [ 5.252] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 2280
  [ 5.275] (--) NVIDIA(0): DPI set to (93, 95); computed from UseEdidDpi 
X config
  [ 5.275] (--) NVIDIA(0): option
  [ 5.275] (--) Depth 24 pixmap format is 32 bpp
  [ 5.275] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect 
memory
  [ 5.275] (II) NVIDIA: access.
  [ 5.281] (II) NVIDIA(0): Setting mode 
DVI-I-0:1920x1200_60+0+1080,HDMI-0:1920x1080_60i+1920+0

  At the very end, an unknown process takes over and reverts the
  previous desired settings to the undesired default (line 3):

  [ 7.196] (II) XKB: reuse xkmfile 
/var/lib/xkb/server-A237F4D5ECC0A2998042D3B58D9A7CE5E820BA0E.xkm
  [ 7.208] (II) NVIDIA(0): Setting mode NULL
  [ 7.270] (II) NVIDIA(0): Setting mode DVI-I-0: nvidia-auto-select 
@1920x1200 +0+0 {ViewPortIn=1920x1200, ViewPortOut=1920x1200+0+0}
  [ 7.469] (II) XKB: reuse xkmfile 
/var/lib/xkb/server-A237F4D5ECC0A2998042D3B58D9A7CE5E820BA0E.xkm
  [ 7.474] (II) XKB: reuse xkmfile 
/var/lib/xkb/server-A237F4D5ECC0A2998042D3B58D9A7CE5E820BA0E.xkm
  [ 7.496] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (CRT-0)) does 
not support NVIDIA
  [ 7.496] (II) NVIDIA(GPU-0): 3D Vision stereo.
  [41.097] (II) XKB: reuse xkmfile 
/var/lib/xkb/server-A237F4D5ECC0A2998042D3B58D9A7CE5E820BA0E.xkm
  [   511.720] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (CRT-0)) does 
not support NVIDIA

  Attachments: screenshots of desired screen settings (Screens_good.gif) and 
default screen settings (Screens.gif)
  This issue occurs regardless of whether the user makes the desired settings 
in Ubuntu's Display tool or NVidia-Settings.
  This issue persists even after specifically saving the desired settings to 
xorg.conf using NVidia-Settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Apr 22 18:14:34 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed
   nvidia-331-updates, 331.38, 3.13.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 680] [10de:1180] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:353c]
  InstallationDate: Installed on 2014-04-20 (2 days ago)
  InstallationMedia: Ubuntu-GNOME

[Desktop-packages] [Bug 682788] Re: Improve Unity Global Menu

2014-08-08 Thread Treviño

@Aleve:

This bug was actually fixed by the Locally Integrated Menus release, but
as for the option to make the menus always visible is something that
we're going to fix ASAP.

By the way, since I think that it's a different bug, then I prefer to
close this and moving to another clean bug for the visibility thing (and
feel free to open it, if there isn't another).

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

Title:
  Improve Unity Global Menu

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Invalid
Status in Unity:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity-control-center” package in Ubuntu:
  Triaged
Status in Baltix GNU/Linux:
  Confirmed

Bug description:
  ===+++ _ ! ALL USERS ! _ +++===
  ===+++ READ THIS BEFORE MAKING A COMMENT OR MODIFICATION +++===

  IMPORTANT 1: Please don't post any me too message; use the Does
  this bug affect you? feature you can find a bit above this bug
  description on Launchpad.

  IMPORTANT 2: Do not post anything if you haven't read all comments to
  verify that your point hasn't been made. If you feel tempted to stop
  reading because there are too many messages, that is a strong
  indicator that you shouldn't add even more comments. Developers have a
  tough time to find anything if you post redundant stuff. So please
  abstain from doing that.

  =
  Global menu in general (not only in Unity) is very unergonomic on large 
screens (see the attached screenshot) because if you have a small window 
somewhere near the low right corner you have to move the cursor all the way up 
to to panel to reach the menu. I understand why the global menu was used for 
the netbook edition (it saves space and most windows are maximized), but since 
Unity is intended to be for the desktop edition there should be an option to 
switch to the traditional position of the app menu. It would be welcomed by 
many desktop users. Please try to find a solution for it that works.

  A commonly suggested solution is:
   [ ] Global Menu on
   [ ] Global Menu off
   [ ] Global Menu only for maximized windows
  The default is usually suggested as either the first (on) or last (on only 
for maximized windows).

  -
  Desired change:

  Implement the 'Enhanced Menu' project for 12.10.  This project will
  address the issue described in this bug and also issues described in
  the duplicates of this bus.  Note this is the 'official' bug that
  tracks the implementation of this project.

  The following options will be added to 'System Settings/Appearance':

  ---
  Menus
  Location:Global/Local
  Visibility:  Hidden/Always displayed
  ---

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

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

[Desktop-packages] [Bug 1354439] Re: [2324BY9, Realtek ALC269VC, Speaker, Internal] fails after a while

2014-08-08 Thread Raymond

109.611744] hda-intel :00:1b.0: spurious response 0x0:0x0, last
cmd=0x324011

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

Title:
  [2324BY9, Realtek ALC269VC, Speaker, Internal] fails after a while

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

Bug description:
  Often occurs when playing youtube videos (sound stops in the middle of
  the video). After restart sometimes no sound at all. Several restarts
  usually fix the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  karsten2080 F pulseaudio
   /dev/snd/pcmC0D0p:   karsten2080 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Fri Aug  8 15:02:39 2014
  InstallationDate: Installed on 2012-08-05 (733 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Sound works for a while, then breaks
  Title: [2324BY9, Realtek ALC269VC, Speaker, Internal] fails after a while
  UpgradeStatus: Upgraded to trusty on 2014-04-24 (106 days ago)
  dmi.bios.date: 04/22/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA1WW (2.61 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324BY9
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA1WW(2.61):bd04/22/2014:svnLENOVO:pn2324BY9:pvrThinkPadX230:rvnLENOVO:rn2324BY9:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324BY9
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 40537] Re: Cannot write to NFS files

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Could you confirm this issue still affects Ubuntu 14.04?
In addition are the error messages, etc still correct?

If so : 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/Freedesktop. 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: libreoffice (Ubuntu)
   Status: Confirmed = Incomplete

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

Title:
  Cannot write to NFS files

Status in The OpenOffice.org Suite:
  Confirmed
Status in “libreoffice” package in Ubuntu:
  Incomplete
Status in “openoffice.org” package in Ubuntu:
  Fix Released
Status in “openoffice.org” package in Debian:
  Fix Released

Bug description:
  SOLUTION:
  1. Use NFSv4 if possible
  2. Install nfs-common package if not installed

  ==

  Opening a file within an NFS mounted
  filesystem causes OpenOffice to show the file in read-only mode, and
  remove the margins and various other editing widgets from the
  application window. Any attempt to save a document to an NFS mount
  results in an error dialog that contains the text:-

  Error saving the document Filename.odt:
  General Error.
  General input/output error.

  This makes the application extremely awkward to use in an office type
  environment, and is a huge step backwards in functionality from the
  OpenOffice.org 1.1.4 package it replaced for me.

  
  This bug is know in debian as bug #335742.

  It was closed by un upstream release.

  In breezy, there is no way to work around the bug wich make ooo
  unusable in breezy in an office environment with NFS.

  A partial solution would be to release a backport for openoffice.org2
  from dapper, as the version in dapper works.

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

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

[Desktop-packages] [Bug 978424] Re: Enable SSL by default for irc.ubuntu.com

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

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

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

Title:
  Enable SSL by default for irc.ubuntu.com

Status in xchat:
  Unknown
Status in “empathy” package in Ubuntu:
  Invalid
Status in “hexchat” package in Ubuntu:
  Invalid
Status in “irssi” package in Ubuntu:
  Fix Released
Status in “pidgin” package in Ubuntu:
  Confirmed
Status in “xchat” package in Ubuntu:
  Confirmed

Bug description:
  Enable SSL by default for irc.ubuntu.com / freenode (and other SSL-
  enhanced networks) to ensure privacy and integrity.

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

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

[Desktop-packages] [Bug 978424] Re: Enable SSL by default for irc.ubuntu.com

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

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

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

Title:
  Enable SSL by default for irc.ubuntu.com

Status in xchat:
  Unknown
Status in “empathy” package in Ubuntu:
  Invalid
Status in “hexchat” package in Ubuntu:
  Invalid
Status in “irssi” package in Ubuntu:
  Fix Released
Status in “pidgin” package in Ubuntu:
  Confirmed
Status in “xchat” package in Ubuntu:
  Confirmed

Bug description:
  Enable SSL by default for irc.ubuntu.com / freenode (and other SSL-
  enhanced networks) to ensure privacy and integrity.

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

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

[Desktop-packages] [Bug 1202383] Re: Unable to add search providers to Firefox

2014-08-08 Thread Krzysztof Kosinski

This bug still happens in trusty.

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

Title:
Unable to add search providers to Firefox

Status in “unity-firefox-extension” package in Ubuntu:
Confirmed

Bug description:
---+ Abstract
As long as the Unity Desktop Integration 2.4.6 plugin is enabled I could
not add search providers to Firefox.

I.e. when I want to add startpage.com and click on the install link for
either HTTP or HTTPS nothing happens.
When I disable the plugin and restart the browser, it works.
WebDeveloper Console dislays the following error:
---SNIP---
[22:29:56.955] TypeError: window.external.AddSearchProvider is not a function
@ https://eu.startpage.com/eng/download-startpage-plugin.html:2121
---SNAP---

When I enable the plugin and restart the browser it's again broken.

---+ Reproducible
Allways

---+ Steps to reproduce
1. Ensure that the Unity Desktop Integration plugin is enabled.
2. Goto https://eu.startpage.com/eng/download-startpage-plugin.html
3. Click on either one of the install buttons

---+ Expected behaviour
A dialog should pop up asking me if I want to add the search provider.

---+ Actual behaviour
Noting happens.

---+ Additional Info
This is also happening when trying to add a search provider from
http://searchplugin.net.
It however displays the following javascript generated message:
---SNIP---
You need to be using a browser which supports OpenSearch

You can also install search plugins by using the drop down menu to the right
of the search box.
---SNAP---

When you enable/disable the browser plugin you do not need to restart
your browser for the effect to occur but you need to refresh the page.
If you do not refresh the page, the behaviour won't change.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: xul-ext-unity 2.4.7bzr13.04.15-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
Uname: Linux 3.8.0-26-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
Date: Wed Jul 17 22:08:35 2013
InstallationDate: Installed on 2013-07-04 (13 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: unity-firefox-extension
UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-firefox-extension/+bug/1202383/+subscriptions

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

[Desktop-packages] [Bug 1069531] Re: Cannot login to Empathy after setting up Google online account

2014-08-08 Thread Roberto Leibman

For what is worth this issue is still not fixed, and yes killing
signonpluginprocess makes it all magically work. 14.04

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

Title:
  Cannot login to Empathy after setting up Google online account

Status in “empathy” package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 12.10
  Release:  12.10

  empathy:
Installed: 3.6.0.3-0ubuntu1
Candidate: 3.6.0.3-0ubuntu1
Version table:
   *** 3.6.0.3-0ubuntu1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages
  100 /var/lib/dpkg/status

  Expected behaviour:

  * New installation of 12.10 Ubuntu
  * Expected to be able to use Google Talk in Empathy after adding a Google 
account under Online Accounts

  Actual behaviour:

  * Account can be added successfully, however Empathy displays Google Talk 
Account requires authorisation
  * Clicking on the icon opens Online Accounts but does not offer an option to 
perform any further authorisation.

  Investigation:

  * Seahorse shows two entries for the Google account, one of which lists the 
correct password, the other of which lists a seemingly random collection of 
characters separated by percentage symbols
  * Checked Google account, Ubuntu has permission to access: Picasa Web Albums, 
Profile Information, Google Docs, Google Talk
  * Google account is not set up to use 2-step verification
  * Removed account and seahorse entries, set up from scratch
  * If possible, will use non-alphanumeric characters in passwords, so tested 
with only alphanumeric password - no difference
  * Not going through a proxy

  Activating empathy-debugger shows:

  wocky/-DEBUG: 21/10/12 11:22:20.784214: _end_element_ns: Received stanza
  * failure xmlns='urn:ietf:params:xml:ns:xmpp-sasl'
  * not-authorized
  * missing-username xmlns='google:auth'
  wocky/-DEBUG: 21/10/12 11:22:20.784320: auth_failed: wocky-sasl-auth.c:274: 
Authentication failed!: Authentication failed: not-authorized
  gabbleauthentication-DEBUG: 21/10/12 11:22:20.784421: 
gabble_server_sasl_channel_fail (server-sasl-channel.c:929): auth failed: 
WOCKY_AUTH_ERROR_FAILURE (#6): Authentication failed: not-authorized
  gabbleconnection-DEBUG: 21/10/12 11:22:20.784534: connector_error_disconnect 
(connection.c:1760): Interactive authentication error, reason 3, dbus error 
org.freedesktop.Telepathy.Error.AuthenticationFailed

  So, it seems that seahorse has the correct password in place, and the
  Google account is set up in such a way as to allow the application to
  work. That being the case, it makes no sense to be getting an
  authorisation error, unless there is something else that isn't
  immediately obvious.

  Have checked for open bugs here:

  * https://bugs.launchpad.net/ubuntu/+source/empathy/+bugs
  * https://bugs.freedesktop.org/buglist.cgi?quicksearch=telepathy

  However nothing that matched this exact problem jumped out - a lot of
  issues seem to be with 2-step verification (but as mentioned earlier
  this has not been enabled).

  Asked for advice here:
  * 
http://askubuntu.com/questions/204062/cannot-login-to-empathy-after-setting-up-google-online-account

  Was advised to log a bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: empathy 3.6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Sun Oct 21 21:21:36 2012
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: empathy
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 682788] Re: Improve Unity Global Menu

2014-08-08 Thread TomasHnyk

Marco: that would be this bug: https://bugs.launchpad.net/ayatana-
design/+bug/955193 - right? It is a duplicate of this one but has some
design to it.

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

Title:
  Improve Unity Global Menu

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Invalid
Status in Unity:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity-control-center” package in Ubuntu:
  Triaged
Status in Baltix GNU/Linux:
  Confirmed

Bug description:
  ===+++ _ ! ALL USERS ! _ +++===
  ===+++ READ THIS BEFORE MAKING A COMMENT OR MODIFICATION +++===

  IMPORTANT 1: Please don't post any me too message; use the Does
  this bug affect you? feature you can find a bit above this bug
  description on Launchpad.

  IMPORTANT 2: Do not post anything if you haven't read all comments to
  verify that your point hasn't been made. If you feel tempted to stop
  reading because there are too many messages, that is a strong
  indicator that you shouldn't add even more comments. Developers have a
  tough time to find anything if you post redundant stuff. So please
  abstain from doing that.

  =
  Global menu in general (not only in Unity) is very unergonomic on large 
screens (see the attached screenshot) because if you have a small window 
somewhere near the low right corner you have to move the cursor all the way up 
to to panel to reach the menu. I understand why the global menu was used for 
the netbook edition (it saves space and most windows are maximized), but since 
Unity is intended to be for the desktop edition there should be an option to 
switch to the traditional position of the app menu. It would be welcomed by 
many desktop users. Please try to find a solution for it that works.

  A commonly suggested solution is:
   [ ] Global Menu on
   [ ] Global Menu off
   [ ] Global Menu only for maximized windows
  The default is usually suggested as either the first (on) or last (on only 
for maximized windows).

  -
  Desired change:

  Implement the 'Enhanced Menu' project for 12.10.  This project will
  address the issue described in this bug and also issues described in
  the duplicates of this bus.  Note this is the 'official' bug that
  tracks the implementation of this project.

  The following options will be added to 'System Settings/Appearance':

  ---
  Menus
  Location:Global/Local
  Visibility:  Hidden/Always displayed
  ---

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

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

[Desktop-packages] [Bug 1298903] Re: Lockscreen: ibus input method selection doesn't work in lock screen

2014-08-08 Thread Andrea Azzarone

** Changed in: unity
 Assignee: Brandon Schaefer (brandontschaefer) = Andrea Azzarone (andyrock)

** Changed in: unity/7.2
 Assignee: (unassigned) = Andrea Azzarone (andyrock)

** Changed in: unity (Ubuntu)
 Assignee: (unassigned) = Andrea Azzarone (andyrock)

** Also affects: indicator-keyboard
   Importance: Undecided
   Status: New

** Changed in: indicator-keyboard
 Assignee: (unassigned) = Andrea Azzarone (andyrock)

** Changed in: indicator-keyboard
   Status: New = In Progress

** Changed in: unity
   Status: Triaged = Invalid

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

** Changed in: indicator-keyboard
   Importance: Undecided = Medium

** Changed in: unity/7.2
   Status: Triaged = Invalid

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

Title:
  Lockscreen: ibus input method selection doesn't work in lock screen

Status in Indicator keyboard:
  In Progress
Status in Unity:
  Invalid
Status in Unity 7.2 series:
  Invalid
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  Earlier, I switched my ibus daemon to the Japanese/anthy input mode
  and locked my screen. I couldn't key in my password (consisting solely
  of ascii characters), as it appeared to be inputting everything in
  Japanese (the typical underlines were there, but everything was
  starred as it was a password input field).

  There didn't appear to be a way to switch it back to a standard qwerty
  input mode, so I was kind of stuck.

  Workaround:
  I managed to get back in by activating the switch user menu item and logging 
back in from there.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140321-0ubuntu1
  Uname: Linux 3.13.4-hyper1 x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,copytex,compiztoolbox,decor,vpswitch,extrawm,text,resize,ring,screenshot,place,commands,put,mousepoll,move,gnomecompat,annotate,blur,clone,widget,regex,imgpng,animation,obs,workarounds,neg,bicubic,resizeinfo,grid,expo,session,wall,showmouse,ezoom,unitymtgrabhandles,fade,scale,scalefilter,showdesktop,scaleaddon,unityshell]
  CurrentDesktop: Unity
  Date: Fri Mar 28 17:56:06 2014
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-03-03 (24 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-keyboard/+bug/1298903/+subscriptions

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

[Desktop-packages] [Bug 955193] Re: Menu bar - add option for the global menu to make it always visible

2014-08-08 Thread Treviño

** This bug is no longer a duplicate of bug 682788
   Improve Unity Global Menu

** Changed in: unity
   Importance: Undecided = Medium

** No longer affects: unity-2d

** Changed in: unity
Milestone: backlog = 7.3.2

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

Title:
  Menu bar - add option for the global menu to make it always visible

Status in Ayatana Design:
  Triaged
Status in Unity:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  
  1) In System Settings/Appearance/Behavior ( see section 2.2 of 
http://tinyurl.com/7c7nofq ), the Application Menu options should be 
Integrated in menu bar and hidden (default) and Integrated in menu bar and 
visible

  2) If Integrated in menu bar and visible is selected, the menus
  should always be shown, in exactly the same manner they are currently
  displayed when the pointer is moved over the menu bar.

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

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

[Desktop-packages] [Bug 156381] Re: [Upstream] [hardy] Goal Seek hangs Calc indefinitely

This is fixed in Libreoffice 4.1+ (in 14.04, etc).
Closing.

** Changed in: libreoffice (Ubuntu)
   Status: Triaged = Fix Released

** Changed in: openoffice
   Importance: Unknown = Undecided

** Changed in: openoffice
   Status: Confirmed = New

** Changed in: openoffice
 Remote watch: OpenOffice.org Issue Tracker #83130 = None

** Changed in: openoffice
   Status: New = Invalid

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

Title:
  [Upstream] [hardy] Goal Seek hangs Calc indefinitely

Status in LibreOffice Productivity Suite:
  Fix Released
Status in The OpenOffice.org Suite:
  Invalid
Status in “libreoffice” package in Ubuntu:
  Fix Released
Status in “openoffice.org” package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org-calc

  1) lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

  2) apt-cache policy libreoffice-calc
  libreoffice-calc:
    Installed: 1:3.3.2-1ubuntu5
    Candidate: 1:3.3.2-1ubuntu5
    Version table:
   *** 1:3.3.2-1ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 
Packages
  500 http://us.archive.ubuntu.com/ubuntu/ natty-proposed/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.3.2-1ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

  3) What is expected to happen in LibreOffice Calc via the Terminal:

  cd ~/Desktop  wget
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/156381/+attachment/167142/+files/sample.ods
   localc -nologo sample.ods

  Tools - Goal Seek... - Formula Cell $F$110 - Target 0 - Variable
  Cell $E$7 - OK button

  and it does so quickly and successfully.

  4) What happens instead is it hangs Calc (waited ~10 minutes than
  killed process).

  WORKAROUND: Use Gnumeric as it performs the calculation instantly.

  apt-cache policy gnumeric
  gnumeric:
    Installed: 1.10.13-1ubuntu1
    Candidate: 1.10.13-1ubuntu1
    Version table:
   *** 1.10.13-1ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages
  100 /var/lib/dpkg/status

  Original Reporter Comments: If you use the Goal Seek on a
  spreadsheet that exceeds 105 rows OOO calc hangs completely, taking
  over 50% of CPU and you have to force the exit.

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

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

[Desktop-packages] [Bug 481592] Re: [upstream] Save as ... dialog forgets chosen file name and directory after format pop-up question

This bug may be fixed, can anyone confirm it still affects them?

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

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

Title:
  [upstream] Save as ... dialog forgets chosen file name and directory
  after format pop-up question

Status in LibreOffice Productivity Suite:
  Incomplete
Status in The OpenOffice.org Suite:
  Confirmed
Status in “libreoffice” package in Ubuntu:
  Incomplete
Status in “openoffice.org” package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  I opened a .doc from an evolution mail attachement and modified it. To
  save it permanently (i.e. not in ~/.evolition/...) I selected the
  save as ... menu entry. In the dialog I changed the name and and
  created and selected a subdirectory of my home directory. After
  pressing the Save button I was asked whether I wanted to keep the
  .doc format or save in .odf format.

  After choosing the .odf option (i.e. I changed the format from .doc to
  .odf), all the selections that I had done before (file name,
  directory) were lost. So pressing the Save button once again leads
  to storing the file in the original temporary location
  (~/.evolution/...).

  When I did this the first time I just wondered that the directory was
  empty after I thought I had stored the file there ...

  An easy way to loose hours of work 

  ProblemType: Bug
  Architecture: amd64
  Date: Thu Nov 12 22:47:44 2009
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  NonfreeKernelModules: nvidia
  Package: openoffice.org-core 1:3.1.1-5ubuntu1
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: openoffice.org
  Uname: Linux 2.6.31-14-generic x86_64

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

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

[Desktop-packages] [Bug 283666] Re: [upstream] impress slideshow does not show cropped .eps images

Is this still an issue for anyone?

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

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

Title:
  [upstream] impress slideshow does not show cropped .eps images

Status in LibreOffice Productivity Suite:
  Won't Fix
Status in The OpenOffice.org Suite:
  Unknown
Status in “libreoffice” package in Ubuntu:
  Incomplete
Status in “openoffice.org” package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  1) lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

  2) apt-cache policy libreoffice-impress
  libreoffice-impress:
Installed: 1:3.3.2-1ubuntu5
Candidate: 1:3.3.2-1ubuntu5
Version table:
   *** 1:3.3.2-1ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-proposed/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.3.2-1ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

  3) What is expected to happen in LibreOffice Impress via the Terminal:

  cd ~/Desktop  wget
  
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/283666/+attachment/403321/+files/croptest.odp
   loimpress -nologo croptest.odp

  press F5, the cropped .eps graph viewable in edit mode is viewed in
  Slide Show successfully.

  4) What happens instead is it shows a blank slide in Slide Show.

  WORKAROUND: click the graph - Format - Default Format and notice the
  graph is viewable in Slide Show.

  WORKAROUND Crop the file in an alternate image manipulation program,
  then insert the file.

  Original Reporter Comments:
  When an .eps image is cropped in OOo Impress, this appears to work in the 
editing view, but in the slideshow the image either disappears completely or 
shows a tiny part from the top left corner (whose size appears to be unrelated 
to the cropping parameters).  Uncropping the image causes it to reappear.

  This bug does not affect cropping of .jpg, .bmp, .png, .gif or .svg
  images.

  Present in amd64 Hardy, amd64 Intrepid and amd64 Jaunty.

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

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

[Desktop-packages] [Bug 1325023] Re: if copied text is inserted, the insert window is not active -- Enter fails

2014-08-08 Thread LAZA

Same problem with printing.

It is *very* annoying if somebody works a lot with the keyboard, hits
CTRL+p and then Enter - nothing happens!

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

Title:
  if copied text is inserted, the insert window is not active --
  Enter fails

Status in “libreoffice” package in Ubuntu:
  Triaged

Bug description:
  I copy a lot of things from the Internet into Calc.

  In the 4.2 version is a bug that the window, that comes at the
  insertion is *not* active. In german it is called Importeinstellungen.

  WORKAROUND: Every time I try to insert the text i have to change from
  keyboard to mouse and click Okay in the LO window to insert the
  text.

  Steps to reproduce:
  - start LO Calc
  - start Firefox
  - copy some text from FF via CTRL+c
  - change window with ALT+Tab
  - insert text in LO via CTRL+v
  - import window comes up, not active
  - hit Enter
  -- nothing happens  :-(

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libreoffice-calc 1:4.2.3~rc3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri May 30 18:35:27 2014
  InstallationDate: Installed on 2014-03-16 (75 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140225)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 987032] Re: Guest account Error saving the document

I'm not sure when this was fixed, but it is fixed in 14.04/.10.

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

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

Title:
  Guest account Error saving the document

Status in “libreoffice” package in Ubuntu:
  Fix Released

Bug description:
  Guest account geeky error message when trying to save a document in
  user's home directory. LibreOffice 3.5 has a problem:

  Error saving the document FILENAME:
  /home/USERNAME/Desktop/FILENAME.odt does not exist.

  I can read from the home directory on the guest account. I'm shure we
  want avoid this for the Ubuntu 12.04 LTS (Precise Pangolin) release,
  when the final has been released. I'm using Ubuntu 12.04 LTS (Precise
  Pangolin) Beta 2 with latest update as of today.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice-core 1:3.5.2-2ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic-pae 3.2.12
  Uname: Linux 3.2.0-20-generic-pae i686
  ApportVersion: 1.95-0ubuntu1
  Architecture: i386
  Date: Mon Apr 23 00:06:01 2012
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120328)
  ProcEnviron:
   LANGUAGE=se_NO:nb_NO:nb:no_NO:no:nn_NO:nn:da:sv:en
   LANG=se_NO
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1202806] Re: [mako] Cannot connect to hidden wifi network (touch|android)

2014-08-08 Thread Seth Forshee

I just reflashed my mako device using ubuntu-device-flash and cannot
find the Other network option. I see there are updates, but none of
them look related (and they won't install anyway for some reason). Plus
there seems to be some timeout or something on the wifi password dialog
that disregards user input, as I'd get almost done entering the
passphrase for a non-hidden network and it would just disappear (I use
long, complex passphrases which take a while on mobile keyboards). On
another network it was failing to connect, so I wanted to check or
reenter the passphrase, but I can't find any way to do that, nor any way
to forget the network. So in all I am _not_ having a good experience
with the wifi settings UI.

If I need to do something specific in order to test this, please let me
know.

** Changed in: indicator-network (Ubuntu)
   Status: Incomplete = Confirmed

** Changed in: indicator-network (Ubuntu)
 Assignee: Seth Forshee (sforshee) = Antti Kaijanmäki (kaijanmaki)

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

Title:
  [mako] Cannot connect to hidden wifi network (touch|android)

Status in “indicator-network” package in Ubuntu:
  Confirmed
Status in “network-manager” package in Ubuntu:
  Incomplete

Bug description:
  There's no UI for this right now that I can find, but if I try to
  connect to a hidden wireless network on mako by manually creating the
  wpa_supplicant.conf file and launching wpa_supplicant by hand,
  authentication with the network fails. The same operation works fine
  on maguro, so odds are this is a driver bug. The network in question
  has WPA2-PSK security.

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

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

[Desktop-packages] [Bug 1354514] [NEW] ModemManager crashed with SIGSEGV in g_simple_async_result_complete()

2014-08-08 Thread Dmitry Shachnev

Public bug reported:

Crashes regularly when I am trying to connect to / disconnect from a
mobile network.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: modemmanager 1.0.0-2ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic i686
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: i386
CrashCounter: 1
Date: Fri Aug  8 15:45:20 2014
Disassembly: = 0x0:Cannot access memory at address 0x0
ExecutablePath: /usr/sbin/ModemManager
InstallationDate: Installed on 2010-03-20 (1602 days ago)
InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta i386 (20100318)
ProcCmdline: /usr/sbin/ModemManager
ProcEnviron:
 PATH=(custom, no user)
 TERM=linux
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: modemmanager
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 g_simple_async_result_complete () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
Title: ModemManager crashed with SIGSEGV in g_simple_async_result_complete()
UpgradeStatus: Upgraded to trusty on 2013-09-29 (313 days ago)
UserGroups:

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


** Tags: apport-crash i386 need-i386-retrace trusty

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

Title:
  ModemManager crashed with SIGSEGV in g_simple_async_result_complete()

Status in “modemmanager” package in Ubuntu:
  New

Bug description:
  Crashes regularly when I am trying to connect to / disconnect from a
  mobile network.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: modemmanager 1.0.0-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: i386
  CrashCounter: 1
  Date: Fri Aug  8 15:45:20 2014
  Disassembly: = 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/sbin/ModemManager
  InstallationDate: Installed on 2010-03-20 (1602 days ago)
  InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta i386 (20100318)
  ProcCmdline: /usr/sbin/ModemManager
  ProcEnviron:
   PATH=(custom, no user)
   TERM=linux
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: modemmanager
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   g_simple_async_result_complete () from 
/usr/lib/i386-linux-gnu/libgio-2.0.so.0
  Title: ModemManager crashed with SIGSEGV in g_simple_async_result_complete()
  UpgradeStatus: Upgraded to trusty on 2013-09-29 (313 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1354514]

StacktraceTop:
 ?? ()
 interface_disabling_step (ctx=0x992d648) at mm-iface-modem-messaging.c:601
 mm_iface_modem_messaging_disable (self=0x9937210, 
callback=callback@entry=0x80a8f20 iface_modem_messaging_disable_ready, 
user_data=user_data@entry=0x995ff78) at mm-iface-modem-messaging.c:664
 disabling_step (ctx=0x995ff78) at mm-broadband-modem.c:8152
 bearer_list_disconnect_all_bearers_ready (list=0x98ffe70, res=0xb5c017a8, 
ctx=0x995ff78) at mm-broadband-modem.c:8055

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

Title:
  ModemManager crashed with SIGSEGV in interface_disabling_step()

Status in “modemmanager” package in Ubuntu:
  New

Bug description:
  Crashes regularly when I am trying to connect to / disconnect from a
  mobile network.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: modemmanager 1.0.0-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: i386
  CrashCounter: 1
  Date: Fri Aug  8 15:45:20 2014
  Disassembly: = 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/sbin/ModemManager
  InstallationDate: Installed on 2010-03-20 (1602 days ago)
  InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta i386 (20100318)
  ProcCmdline: /usr/sbin/ModemManager
  ProcEnviron:
   PATH=(custom, no user)
   TERM=linux
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: modemmanager
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   g_simple_async_result_complete () from 
/usr/lib/i386-linux-gnu/libgio-2.0.so.0
  Title: ModemManager crashed with SIGSEGV in g_simple_async_result_complete()
  UpgradeStatus: Upgraded to trusty on 2013-09-29 (313 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1354514] StacktraceSource.txt

** Attachment added: StacktraceSource.txt
   
https://bugs.launchpad.net/bugs/1354514/+attachment/4172950/+files/StacktraceSource.txt

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

Title:
  ModemManager crashed with SIGSEGV in interface_disabling_step()

Status in “modemmanager” package in Ubuntu:
  New

Bug description:
  Crashes regularly when I am trying to connect to / disconnect from a
  mobile network.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: modemmanager 1.0.0-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: i386
  CrashCounter: 1
  Date: Fri Aug  8 15:45:20 2014
  Disassembly: = 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/sbin/ModemManager
  InstallationDate: Installed on 2010-03-20 (1602 days ago)
  InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta i386 (20100318)
  ProcCmdline: /usr/sbin/ModemManager
  ProcEnviron:
   PATH=(custom, no user)
   TERM=linux
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: modemmanager
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   g_simple_async_result_complete () from 
/usr/lib/i386-linux-gnu/libgio-2.0.so.0
  Title: ModemManager crashed with SIGSEGV in g_simple_async_result_complete()
  UpgradeStatus: Upgraded to trusty on 2013-09-29 (313 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1354514] ThreadStacktrace.txt

** Attachment added: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1354514/+attachment/4172951/+files/ThreadStacktrace.txt

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1354514/+attachment/4172933/+files/CoreDump.gz

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

** Summary changed:

- ModemManager crashed with SIGSEGV in g_simple_async_result_complete()
+ ModemManager crashed with SIGSEGV in interface_disabling_step()

** Tags removed: need-i386-retrace

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

Title:
  ModemManager crashed with SIGSEGV in interface_disabling_step()

Status in “modemmanager” package in Ubuntu:
  New

Bug description:
  Crashes regularly when I am trying to connect to / disconnect from a
  mobile network.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: modemmanager 1.0.0-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: i386
  CrashCounter: 1
  Date: Fri Aug  8 15:45:20 2014
  Disassembly: = 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/sbin/ModemManager
  InstallationDate: Installed on 2010-03-20 (1602 days ago)
  InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta i386 (20100318)
  ProcCmdline: /usr/sbin/ModemManager
  ProcEnviron:
   PATH=(custom, no user)
   TERM=linux
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: modemmanager
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   g_simple_async_result_complete () from 
/usr/lib/i386-linux-gnu/libgio-2.0.so.0
  Title: ModemManager crashed with SIGSEGV in g_simple_async_result_complete()
  UpgradeStatus: Upgraded to trusty on 2013-09-29 (313 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1354514] Stacktrace.txt

** Attachment added: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1354514/+attachment/4172949/+files/Stacktrace.txt

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

Title:
  ModemManager crashed with SIGSEGV in interface_disabling_step()

Status in “modemmanager” package in Ubuntu:
  New

Bug description:
  Crashes regularly when I am trying to connect to / disconnect from a
  mobile network.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: modemmanager 1.0.0-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: i386
  CrashCounter: 1
  Date: Fri Aug  8 15:45:20 2014
  Disassembly: = 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/sbin/ModemManager
  InstallationDate: Installed on 2010-03-20 (1602 days ago)
  InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta i386 (20100318)
  ProcCmdline: /usr/sbin/ModemManager
  ProcEnviron:
   PATH=(custom, no user)
   TERM=linux
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: modemmanager
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   g_simple_async_result_complete () from 
/usr/lib/i386-linux-gnu/libgio-2.0.so.0
  Title: ModemManager crashed with SIGSEGV in g_simple_async_result_complete()
  UpgradeStatus: Upgraded to trusty on 2013-09-29 (313 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 960307] Re: lowriter fails to start

Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed with some of the updates. It would help us a lot if
you could test it on a currently supported Ubuntu version and report
back if this is still an issue for you.

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

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

Title:
  lowriter fails to start

Status in “libreoffice” package in Ubuntu:
  Incomplete

Bug description:
  If I try to start lowriter, it will fail to start after 1 second:
  avilella@magneto:~$ /usr/bin/lowriter 

  (soffice:9838): Gtk-WARNING **: Unable to locate theme engine in
  module_path: pixmap,

  (soffice:9838): Gtk-WARNING **: Unable to locate theme engine in
  module_path: pixmap,

  (soffice:9838): Gtk-WARNING **: Unable to locate theme engine in
  module_path: pixmap,

  (soffice:9838): Gtk-WARNING **: Unable to locate theme engine in module_path: 
pixmap,
  avilella@magneto:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libreoffice-writer 1:3.4.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-16.29-generic-pae 3.0.20
  Uname: Linux 3.0.0-16-generic-pae i686
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Tue Mar 20 15:30:25 2012
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to oneiric on 2012-02-12 (37 days ago)

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

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

[Desktop-packages] [Bug 958955] Re: In the Find Replace dialog in libreoffice, the right click replace with option is limited to only the ubuntu font

Still a bug on 14.10 with LibreOffice 4.2.4.

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

** Changed in: libreoffice (Ubuntu)
 Assignee: (unassigned) = Bryan Quigley (bryanquigley)

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

Title:
  In the Find  Replace dialog in libreoffice, the right click
  replace with option is limited to only the ubuntu font

Status in “libreoffice” package in Ubuntu:
  Confirmed

Bug description:
  To reproduce:
  1. open libreoffice writer
  2. go to Find  Replace
  3. right click replace with field and choose special character

  Expected result:
  -- The special characters dialog pops up and you can pick any font from 
which to choose a special character from.

  Actual result:
  -- The special characters dialog pops up, but the font drop down box is set 
to the ubuntu font, and it is shaded out so that it can't be changed.

  WORKAROUND: After the text has been replaced, highlight the desired
  text and change the font.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libreoffice-writer 1:3.4.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-16.29-generic-pae 3.0.20
  Uname: Linux 3.0.0-16-generic-pae i686
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Sun Mar 18 22:00:38 2012
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1325992] Re: Synaptics Driver

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

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

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

Title:
  Synaptics Driver

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

Bug description:
  I am having problems with the synaptics touch pad on my HP 255 G2
  running Ubuntu 14.04 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Jun  3 15:48:13 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8210] [1002:9834] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:2192]
  InstallationDate: Installed on 2014-05-28 (5 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP 255 G2 Notebook PC
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic.efi.signed 
root=UUID=2fe52a2d-a3ca-4138-8261-72c1bd9edcc3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.07
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 2192
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 41.18
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.07:bd11/13/2013:svnHewlett-Packard:pnHP255G2NotebookPC:pvr097510405F1610181:rvnHewlett-Packard:rn2192:rvr41.18:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 255 G2 Notebook PC
  dmi.product.version: 097510405F1610181
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Jun  3 09:27:29 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1313289] Re: Low Graphics Mode with AMD R9 270X

2014-08-08 Thread madbiologist

Which version of Ubuntu are you using?  Can you please paste the output
of uname -srm?

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

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

Title:
  Low Graphics Mode with AMD R9 270X

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I have an AMD R9 270X graphics card and Ubuntu will occasionally go
  into low-graphics mode when starting up. At that point I cannot do
  anything apart from drop into the terminal.

  It happens sporadically, about 3/4 of the time. Often a reboot will
  fix it however because it happens so often, it's very annoying.

  I've tried installing fglrx and fglrx-updates along with the latest
  proprietary AMD drivers including 14.4 stable and 14.3 beta. However
  it still occurs.

  I've also tried using failsafeX settings among other things without
  success.

  Attached are the Xorg and Xorg.failsafe log files.

  There's a segmentation fault at the bottom of the failsafe log files
  which may have something to do with it?

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

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

[Desktop-packages] [Bug 1248174] Re: The Ubuntu colour palette in Inkscape is different from the one in design.ubuntu.com

2014-08-08 Thread jazzynico

Sorry for the delay. I seems the Inkscape and Ubuntu teams were waiting
for each other...

The patch from comment #16 looks good, but only changes the Accent
Orange value. If I understand correctly, the original report is not
about one specific color but requests a whole update of the palette file
(The colours listed in the palette from Inkscape have no relationship
with the ones in design.ubuntu.com.).

Thus I'd rather use one of the files suggested by ~suv comments #15 and #17.
Could someone from the Ubuntu design team confirm that the current Inkscape 
palette file is outdated, not the Accent Orange color only? Thanks!

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

Title:
  The Ubuntu colour palette in Inkscape is different from the one in
  design.ubuntu.com

Status in Inkscape: A Vector Drawing Tool:
  Triaged
Status in Ubuntu Accomplishments Daemon:
  New
Status in Ubuntu Accomplishments Extra Information:
  New
Status in Ubuntu Accomplishments System:
  New
Status in Ubuntu Accomplishments Viewer:
  New
Status in Ubuntu Accomplishments Web Gallery:
  New
Status in Ubuntu Brand Guidelines:
  New
Status in Ubuntu Community:
  New
Status in Ubuntu Community Accomplishments:
  New
Status in Ubuntu Desktop Accomplishments:
  New
Status in “inkscape” package in Ubuntu:
  In Progress

Bug description:
  
  HOW TO REPRODUCE
  

  1. In Inkscape create a figure colored Accent Orange, from the Ubuntu 
colour palette.
  2. Compare colour with Ubuntu Orange in 
http://design.ubuntu.com/brand/colour-palette.

  **
  EXPECTED BEHAVIOUR
  **

  - The colour to be the same.

  **
  REAL BEHAVIOUR
  **

  - The colour is different.
  - The colours listed in the palette from Inkscape have no relationship with 
the ones in design.ubuntu.com.

  ***
  WORK-AROUND
  ***

  - To use the colours in http://design.ubuntu.com/brand/colour-palette
  instead.

  
  RELEVANT DETAILS
  

  - Orange colour is very similar, but not equal. So it's very probable someone 
use the wrong colour in their designs for Ubuntu.
  - In fact, the logo of Ubuntu project in Launchpad is affected 
(https://launchpad.net/ubuntu).
  - A demonstrative image is attached to this bug.

  **
  TECHNICAL INFO
  **

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: inkscape 0.48.4-1ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13
  Uname: Linux 3.8.0-25-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Tue Nov  5 13:47:52 2013
  InstallationDate: Installed on 2013-05-21 (167 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: inkscape
  UpgradeStatus: Upgraded to saucy on 2013-10-18 (18 days ago)

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

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

[Desktop-packages] [Bug 1202806] Re: [mako] Cannot connect to hidden wifi network (touch|android)

2014-08-08 Thread Seth Forshee

All right, it turns out I didn't run ubuntu-device-flash the right way
and ended up with an old image. I tested with devel-proposed, and I'd
say that it's mostly fixed.

The UI is there, and I can use it to connect to a hidden network, but I
did have a few of problems. First, when the keyboard was present on the
screen to setup up the network it resulted in the test field for
entering the passphrase getting covered by buttons, making it impossible
to select the field until I dismissed the keyboard. Second, once
connected I didn't have the little wifi connected icon in the top bar
that I get when connected to a non-hidden network, just a blank space
where it should have been. Finally, after I connected to the hidden
network the list of available networks showed that network twice, once
with a check mark and high signal indication and again unchecked with
the graphic showing no signal. When I tapped the network with no signal
it just disappeared.

Oh, one more thing. The hidden network always appears at the bottom of
the list of available network, regardless of relative signal strength,
and even when I'm connected to that network.

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

Title:
  [mako] Cannot connect to hidden wifi network (touch|android)

Status in “indicator-network” package in Ubuntu:
  Confirmed
Status in “network-manager” package in Ubuntu:
  Incomplete

Bug description:
  There's no UI for this right now that I can find, but if I try to
  connect to a hidden wireless network on mako by manually creating the
  wpa_supplicant.conf file and launching wpa_supplicant by hand,
  authentication with the network fails. The same operation works fine
  on maguro, so odds are this is a driver bug. The network in question
  has WPA2-PSK security.

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

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

[Desktop-packages] [Bug 1033219] Re: Main Gimp window looses focus every time an option is used

2014-08-08 Thread Jarda Pavlicek

Hi, could I contribute to solution of this bug? If some senior developer
showed me the way I'd go and try to solve it.

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

Title:
  Main Gimp window looses focus every time an option is used

Status in “gimp” package in Ubuntu:
  Confirmed

Bug description:
  In order to use the Gimp menu, the main window has to be selected.

  However, after running almost any option from the menu, the focus does
  not return the main window but changes aleatory  to one of the other
  windows (either Toolbox or Layers).

  Those windows do not have menus, so you neither can use Alt+ to get to
  the menus nor take advantage of the HUD.

  I could say that this happens with any option that launch a dialog
  window. For instance:

  Color - Hue-Saturation
  Filter - Blur - Gaussian Blur
  Etc.

  This also happens when you switch to another workspace and come back.

  I appreciate your time to review this bug.
  Kind Regards.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gimp 2.6.12-1ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
  Uname: Linux 3.2.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu11
  Architecture: amd64
  Date: Sun Aug  5 10:22:47 2012
  ExecutablePath: /usr/bin/gimp-2.6
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gimp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1202806] Re: [mako] Cannot connect to hidden wifi network (touch|android)

2014-08-08 Thread Antti Kaijanmäki

OK, but you _can connect_  to the hidden network, so this bug is Fix
Released.

the keyboard issue: bug #1333135


Could you file a new bug about the indicator visual problem and attach the 
following information to it:

=== with phablet-shell from the device ===
$ dbus-send --session --print-reply --dest=com.canonical.indicator.network 
/com/canonical/indicator/network/phone org.gtk.Menus.Start array:uint32:1,0  
menumodel.txt

$ nmcli d wifi list  nmcli_d_wifi_list.txt

$ dbus-send --print-reply --dest=com.canonical.indicator.network 
/com/canonical/indicator/network org.gtk.Actions.DescribeAll  actiongroup.txt
==

=== on the host computer with the device attached via USB ===
1. open the network indicator and take a screenshot of it's wrong contents:

$ phablet-screenshot indicator.png
==

Download the files from the device with adb:
$ adb pull /home/phablet/filename

** Changed in: indicator-network (Ubuntu)
   Status: Confirmed = Fix Released

** Changed in: network-manager (Ubuntu)
   Status: Incomplete = Fix Released

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

Title:
  [mako] Cannot connect to hidden wifi network (touch|android)

Status in “indicator-network” package in Ubuntu:
  Fix Released
Status in “network-manager” package in Ubuntu:
  Fix Released

Bug description:
  There's no UI for this right now that I can find, but if I try to
  connect to a hidden wireless network on mako by manually creating the
  wpa_supplicant.conf file and launching wpa_supplicant by hand,
  authentication with the network fails. The same operation works fine
  on maguro, so odds are this is a driver bug. The network in question
  has WPA2-PSK security.

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

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

[Desktop-packages] [Bug 1342312] Re: ghostscript hangs reading certain pdfs

** Changed in: ghostscript (Ubuntu)
   Importance: Undecided = Low

** Information type changed from Private Security to Public Security

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

Title:
  ghostscript hangs reading certain pdfs

Status in “ghostscript” package in Ubuntu:
  New

Bug description:
  On a few pdfs, gs hangs and uses 100% cpu forever.

  This could be used as a denial of service through imagemagick which
  uses ghostscript as a delegate, and commonly used in php etc... which
  is how I found the issue.

  The packages from utopic (9.14~dfsg-0ubuntu3) processes these pdfs
  correctly.

  To reproduce:
  gs WaddellAndReedJCL0814ThirdHProvSE.pdf

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ghostscript 9.10~dfsg-0ubuntu10.2
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Tue Jul 15 14:34:26 2014
  InstallationDate: Installed on 2014-04-20 (86 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  Lpstat:
   device for Bizhub7222: socket://10.0.0.201:9100
   device for HP-Photosmart-6520-series: 
dnssd://Photosmart%206520%20series%20%5B1B47AD%5D._ipp._tcp.local/
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  Papersize: letter
  PpdFiles:
   HP-Photosmart-6520-series: HP Photosmart 6520 Series, hpcups 3.14.3
   Bizhub7222: HP LaserJet 5L - CUPS+Gutenprint v5.2.10-pre2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic 
root=UUID=2f256b0b-ee87-463a-af04-e892e0be9192 ro quiet splash pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1
  SourcePackage: ghostscript
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.213
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.213:bd11/16/2012:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1220426] Re: [nvidia-prime]Freeze while using touchpad

2014-08-08 Thread Raja

Thanks Michael,

Could you please run the nvidia-bug report by triggering the nvidia-bug-
report.sh from root user and share the same here?

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

Title:
  [nvidia-prime]Freeze while using touchpad

Status in “nvidia-graphics-drivers-319” package in Ubuntu:
  Triaged
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Triaged
Status in “nvidia-prime” package in Ubuntu:
  Triaged

Bug description:
  I'm using an Optimus laptop (Asus N43SL)
  nvidia-prime is installed, so my nvidia dedicated graphics card (GT 540m) is 
in use.

  Once in a while, my screen will freeze, only when I use my touchpad.
  This does not happen with my USB mouse.
  This does not happen either when I uninstall nvidia-prime and use my intel 
integrated graphics (HD3000).

  I can temporarily solve the issue by doing a VT switch.

  
  In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: 
touchpad found each time I did a VT switch and regained control.

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

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

[Desktop-packages] [Bug 1354496] Re: Screen doesn't always lock correctly after inactivity

2014-08-08 Thread Seth Arnold

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 49579, so it is being marked as such.

This is a fundamental bug in the design of X11 and cannot be easily
fixed within X11.

You should manually lock your screen if a locked session is important to
you.

Please continue to report any other bugs you may find.

** Information type changed from Private Security to Public

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

** This bug has been marked a duplicate of bug 49579
   screen doesn't lock when some menu is open

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

Title:
  Screen doesn't always lock correctly after inactivity

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

Bug description:
  When my laptop shuts off the screen due to inactivity, when I come
  back, the screen isn't locked.  I can start back to work and interact
  with my apps, then the screen locks after I've started back to work.

  Expected behavior:  The screen locks after the inactivity timeout has
  expired (5 minutes in my case).

  Actual behavior:  When I wake up the screen, it's not locked, but
  then locks a few seconds after I've started to work.

  I use my laptop for system administration, including access to a
  production environmnent, and can't have it left unlocked.

  The behavior doesn't seem to be consistent, but I'll keep testing to
  see if there are specific scenarios under which this occurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-screensaver 3.6.1-0ubuntu13
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug  8 10:55:22 2014
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 300
  InstallationDate: Installed on 2014-07-28 (10 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1086058] Re: my unity laucher and environment disappeared when i changed certain permission in dpkg file while installing hadoop.

Thanks for your comments. This does not appear to be a bug report and we
are closing it. We appreciate the difficulties you are facing, but it
would make more sense to raise your question in the support tracker.
Please visit https://answers.launchpad.net/ubuntu/+addquestion

** Information type changed from Private Security to Public

** Changed in: unity
   Status: New = Invalid

** Changed in: unity (Ubuntu)
   Status: New = Invalid

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

Title:
  my unity laucher and environment disappeared when i changed certain
  permission in dpkg file while installing hadoop.

Status in Unity:
  Invalid
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  my settings for flashdrive is not working.
  users and groups are disabled. error: configuration cannot be loaded.

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

-- 
Mailing list: https://launchpad.net/~desktop-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

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

** Changed in: unity (Ubuntu Precise)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/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 Unity:
  Triaged
Status in Unity 7.2 series:
  Triaged
Status in X.Org X server:
  Confirmed
Status in “gnome-screensaver” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Confirmed
Status in “gnome-screensaver” source package in Precise:
  Confirmed
Status in “unity” 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 1284308] Re: Bogus another operation in progress error. Can't copy files from a bluetooth device

2014-08-08 Thread Alistair Buxton

Subsribed additional packages to try to get some eyes on this.

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

Title:
  Bogus another operation in progress error. Can't copy files from a
  bluetooth device

Status in “bluez” package in Ubuntu:
  Confirmed
Status in “gvfs” package in Ubuntu:
  Confirmed
Status in “obex-data-server” package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 13.10.

  And as usual, with the upgrade, a whole new bluetooth issue, which
  this times makes transferring files from the phone to the computer
  (which already was painful) completely impossible!

  How I reproduce (100% systematic):
  1 - click on the Bluetooth icon in the notification area
  2 - from the dropdown menu, choose bluetooth settings
  3 - select the phone among the listed devices
  4 - click on Browse files
  5 - A Nautilus windows opens, allowing me to browse files on the phone. Open 
the DCIM/Camera folder
  6 - Select a couple of files. Either drag and drop them, or copy and then 
paste them, into a folder on the computer

  = I systematically get an error, but it can be any of the two
  variants shown in the two screenshots (one says there was an error
  copying the file, the other says there was an error getting
  information about the file; in both cases the given reason is another
  operation in progress. Note also that in one case there is a Retry
  button, in the other there is not - pure nonsense).

  I then ejected the phone with  the eject button next to its name in
  Nautilus, and repeated the whole process.

  I randomly get any of three outcomes:
  - the one described above (MOST of the times)
  - at step 4, I get an error This location could not be displayed. Another 
operation in progress, so I cannot even browse files
  or
  - at some point (not sure whether it was at step 4 above or when ejecting 
the phone) something CRASHES (I get the usual Ubuntu message informing me of 
that).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Feb 24 21:24:05 2014
  InstallationDate: Installed on 2013-10-11 (136 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Acer Aspire V3-571G
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: A4:17:31:0D:4A:70  ACL MTU: 1022:8  SCO MTU: 183:5
    UP RUNNING PSCAN ISCAN
    RX bytes:44318 acl:198 sco:0 events:355 errors:0
    TX bytes:6132 acl:178 sco:0 commands:82 errors:0

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

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

[Desktop-packages] [Bug 1284308] Re: Bogus another operation in progress error. Can't copy files from a bluetooth device

2014-08-08 Thread Alistair Buxton

Today my workaround didn't work. This suggests the problem is in gvfsd
or obex-data-server.

** Also affects: obex-data-server (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** Changed in: obex-data-server (Ubuntu)
   Status: New = Confirmed

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

Title:
  Bogus another operation in progress error. Can't copy files from a
  bluetooth device

Status in “bluez” package in Ubuntu:
  Confirmed
Status in “gvfs” package in Ubuntu:
  Confirmed
Status in “obex-data-server” package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 13.10.

  And as usual, with the upgrade, a whole new bluetooth issue, which
  this times makes transferring files from the phone to the computer
  (which already was painful) completely impossible!

  How I reproduce (100% systematic):
  1 - click on the Bluetooth icon in the notification area
  2 - from the dropdown menu, choose bluetooth settings
  3 - select the phone among the listed devices
  4 - click on Browse files
  5 - A Nautilus windows opens, allowing me to browse files on the phone. Open 
the DCIM/Camera folder
  6 - Select a couple of files. Either drag and drop them, or copy and then 
paste them, into a folder on the computer

  = I systematically get an error, but it can be any of the two
  variants shown in the two screenshots (one says there was an error
  copying the file, the other says there was an error getting
  information about the file; in both cases the given reason is another
  operation in progress. Note also that in one case there is a Retry
  button, in the other there is not - pure nonsense).

  I then ejected the phone with  the eject button next to its name in
  Nautilus, and repeated the whole process.

  I randomly get any of three outcomes:
  - the one described above (MOST of the times)
  - at step 4, I get an error This location could not be displayed. Another 
operation in progress, so I cannot even browse files
  or
  - at some point (not sure whether it was at step 4 above or when ejecting 
the phone) something CRASHES (I get the usual Ubuntu message informing me of 
that).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Feb 24 21:24:05 2014
  InstallationDate: Installed on 2013-10-11 (136 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Acer Aspire V3-571G
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: A4:17:31:0D:4A:70  ACL MTU: 1022:8  SCO MTU: 183:5
    UP RUNNING PSCAN ISCAN
    RX bytes:44318 acl:198 sco:0 events:355 errors:0
    TX bytes:6132 acl:178 sco:0 commands:82 errors:0

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

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

[Desktop-packages] [Bug 1354496] Re: Screen doesn't always lock correctly after inactivity