date:20141020

You have been subscribed to a public bug:

Fail to scroll content with trackpoint and middle button.

Steps to reproduce:

1. hold the middle button (should be on center-top area, since it's button-less 
touchpad)
2. move the trackpoint

Actual results:

nothing move, tried using xev to capture information but nothing return.

Expected result:

Content/page should scroll as TrackPoint move around.


Additoinal Information:

ubuntu@201307-13930:~$ xinput --list
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPadid=10   [slave  pointer  (2)]
⎜   ↳ TPPS/2 IBM TrackPoint id=11   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Video Bus id=7[slave  keyboard (3)]
↳ Integrated Camera id=8[slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=9[slave  keyboard (3)]
↳ ThinkPad Extra Buttonsid=12   [slave  keyboard (3)]

ubuntu@201307-13930:~$ xinput --list-props 11
Device 'TPPS/2 IBM TrackPoint':
Device Enabled (136):   1
Coordinate Transformation Matrix (138): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (260): 0
Device Accel Constant Deceleration (261):   1.00
Device Accel Adaptive Deceleration (262):   1.00
Device Accel Velocity Scaling (263):10.00
Device Product ID (254):2, 10
Device Node (255):  "/dev/input/event4"
Evdev Axis Inversion (301): 0, 0
Evdev Axes Swap (303):  0
Axis Labels (304):  "Rel X" (146), "Rel Y" (147)
Button Labels (305):"Button Left" (139), "Button Middle" (140), 
"Button Right" (141), "Button Wheel Up" (142), "Button Wheel Down" (143), 
"Button Horiz Wheel Left" (144), "Button Horiz Wheel Right" (145)
Evdev Scrolling Distance (306): 0, 0, 0
Evdev Middle Button Emulation (307):0
Evdev Middle Button Timeout (308):  50
Evdev Third Button Emulation (309): 0
Evdev Third Button Emulation Timeout (310): 1000
Evdev Third Button Emulation Button (311):  3
Evdev Third Button Emulation Threshold (312):   20
Evdev Wheel Emulation (313):1
Evdev Wheel Emulation Axes (314):   6, 7, 4, 5
Evdev Wheel Emulation Inertia (315):10
Evdev Wheel Emulation Timeout (316):200
Evdev Wheel Emulation Button (317): 2
Evdev Drag Lock Buttons (318):  0

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-23-generic 3.16.0-23.30
ProcVersionSignature: Ubuntu 3.16.0-23.30-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
ApportVersion: 2.14.7-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  ubuntu 2066 F pulseaudio
 /dev/snd/controlC0:  ubuntu 2066 F pulseaudio
CurrentDesktop: Unity
Date: Mon Oct 20 03:43:58 2014
HibernationDevice: RESUME=UUID=ef079530-e68a-45a8-95b6-84a3dd18dfd6
InstallationDate: Installed on 2014-10-20 (0 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
MachineType: LENOVO 20ANZ039US
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic 
root=UUID=fe4fceda-a7bb-4159-a6b0-84357353090c ro rootdelay=60 quiet splash 
initcall_debug vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-23-generic N/A
 linux-backports-modules-3.16.0-23-generic  N/A
 linux-firmware 1.136
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/24/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: GLET21WW (0.21)
dmi.board.asset.tag: Not Available
dmi.board.name: 20ANZ039US
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:bvrGLET21WW(0.21):bd05/24/2013:svnLENOVO:pn20ANZ039US:pvrThinkPadT440p:rvnLENOVO:rn20ANZ039US:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20ANZ039US
dmi.product.version: ThinkPad T440p
dmi.sys.vendor: LENOVO

** Affects: xserver-xorg-input-synaptics (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug utopic
-- 
[Lenovo T440p] New Trackpad: middle button with TrackPoint are not able to 
perform scroll
https://bugs.launchpad.net/bugs/1383157
You received this bug notification because you are a member of Desktop 
Pack

[Desktop-packages] [Bug 1383157] [NEW] [Lenovo T440p] New Trackpad: middle button with TrackPoint are not able to perform scroll

2014-10-20 Thread Yung Shen

Public bug reported:

Accroding to bug #1294515 , this feature should be included.


Fail to scroll content with trackpoint and middle button.

Steps to reproduce:

1. hold the middle button (should be on center-top area, since it's button-less 
touchpad)
2. move the trackpoint

Actual results:

nothing move, tried using xev to capture information but nothing return.

Expected result:

Content/page should scroll as TrackPoint move around.


-
Additoinal Information:

ubuntu@201307-13930:~$ xinput --list
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPadid=10   [slave  pointer  (2)]
⎜   ↳ TPPS/2 IBM TrackPoint id=11   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Video Bus id=7[slave  keyboard (3)]
↳ Integrated Camera id=8[slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=9[slave  keyboard (3)]
↳ ThinkPad Extra Buttonsid=12   [slave  keyboard (3)]

ubuntu@201307-13930:~$ xinput --list-props 11
Device 'TPPS/2 IBM TrackPoint':
 Device Enabled (136):  1
 Coordinate Transformation Matrix (138):1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
 Device Accel Profile (260):0
 Device Accel Constant Deceleration (261):  1.00
 Device Accel Adaptive Deceleration (262):  1.00
 Device Accel Velocity Scaling (263):   10.00
 Device Product ID (254):   2, 10
 Device Node (255): "/dev/input/event4"
 Evdev Axis Inversion (301):0, 0
 Evdev Axes Swap (303): 0
 Axis Labels (304): "Rel X" (146), "Rel Y" (147)
 Button Labels (305):   "Button Left" (139), "Button Middle" (140), "Button 
Right" (141), "Button Wheel Up" (142), "Button Wheel Down" (143), "Button Horiz 
Wheel Left" (144), "Button Horiz Wheel Right" (145)
 Evdev Scrolling Distance (306):0, 0, 0
 Evdev Middle Button Emulation (307):   0
 Evdev Middle Button Timeout (308): 50
 Evdev Third Button Emulation (309):0
 Evdev Third Button Emulation Timeout (310):1000
 Evdev Third Button Emulation Button (311): 3
 Evdev Third Button Emulation Threshold (312):  20
 Evdev Wheel Emulation (313):   1
 Evdev Wheel Emulation Axes (314):  6, 7, 4, 5
 Evdev Wheel Emulation Inertia (315):   10
 Evdev Wheel Emulation Timeout (316):   200
 Evdev Wheel Emulation Button (317):2
 Evdev Drag Lock Buttons (318): 0


-

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-23-generic 3.16.0-23.30
ProcVersionSignature: Ubuntu 3.16.0-23.30-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
ApportVersion: 2.14.7-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  ubuntu 2066 F pulseaudio
 /dev/snd/controlC0:  ubuntu 2066 F pulseaudio
CurrentDesktop: Unity
Date: Mon Oct 20 03:43:58 2014
HibernationDevice: RESUME=UUID=ef079530-e68a-45a8-95b6-84a3dd18dfd6
InstallationDate: Installed on 2014-10-20 (0 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
MachineType: LENOVO 20ANZ039US
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic 
root=UUID=fe4fceda-a7bb-4159-a6b0-84357353090c ro rootdelay=60 quiet splash 
initcall_debug vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-23-generic N/A
 linux-backports-modules-3.16.0-23-generic  N/A
 linux-firmware 1.136
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/24/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: GLET21WW (0.21)
dmi.board.asset.tag: Not Available
dmi.board.name: 20ANZ039US
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:bvrGLET21WW(0.21):bd05/24/2013:svnLENOVO:pn20ANZ039US:pvrThinkPadT440p:rvnLENOVO:rn20ANZ039US:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20ANZ039US
dmi.product.version: ThinkPad T440p
dmi.sys.vendor: LENOVO

** Affects: xserver-xorg-input-synaptics (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: 201307-13930 amd64 apport-bug taipei-lab utopic

** Package changed: linux (Ubuntu) => xserver-xorg-input-synaptics
(Ubuntu)

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

** Tags added: 201307-13930 taipei-lab

** Description changed:

+ Accroding to bug #1294515 , this feature should be included.
+ 
+ 
  Fail to scroll content

[Desktop-packages] [Bug 1174529] Re: Nautilus searches All Files when it should search Home

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

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

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

Title:
  Nautilus searches All Files when it should search Home

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  To replicate, on Raring

  Open Nautilus on the users Home folder.
  Click in the right hand pane
  Type, for example, the word down
  Nautilus shows the results of searching for 'down' in All Files even though 
Home is selected to the right of the search window.  It should only show 
matching files in the current folder.  Clicking on All Files and Home refreshes 
the view but still all matching files are shown.

  I believe that this is a regression introduced recently as I have been
  using Raring Alpha for some time and I have not noticed the problem
  previously.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Mon Apr 29 21:25:40 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'1136x520+1427+249'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'213'
  InstallationDate: Installed on 2012-08-01 (271 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120730.1)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1371372] Re: Support for Lenovo new TrackPad (ClickPad)

2014-10-20 Thread Yung Shen

** Description changed:

  *This bug is under developing
  
  Affected model:
  
  L440 - with Ubuntu release: 12.04.5
  w540 - with Ubuntu release: 12.04.5
  X240
+ T440p with Ubuntu release: 14.10(daily),  issue reported separately here with 
this bug #1383157
  
  Description:
  
  The Lenovo new TrackPad since 2014 starting to unify buttons into
  ClickPad, but in most case for now, upper middle scroll(selection) and
  upper left click, in generally it is not effecting normal use, however
  it is a trouble for user who use Trackpoint(Pointing Stick), which makes
  it useless since there is no wait to scroll with TrackPoint.
  
  Steps to reproduce:
  
  1. Open any webpage
  2. Trying to scroll page with TrackPoint
  
  1. Open any textfile with any editors
  2.  Trying to select and copy some text while using TrackPoint
  
  Actual result:
  
  Users need to move their hands off the keyboard and use the bottom of
  touchpad to perform actions all over again.
  
  Expected results:
  
  5 buttons on new TrackPad should works as expected.
  
- 
  -
  Additional information:
  
  New Trackpad should be supported in Utopic according to this bug:
  https://bugs.launchpad.net/ubuntu/+source/libevdev/+bug/1294515
- 
  
  -
  Reference information about the unified touchpad:
  
  ThinkPad TrackPad features promote page:
  http://shop.lenovo.com/us/en/laptops/thinkpad/trackpad/
  
  Synaptics ClickPad solution:
  http://www.synaptics.com/en/clickpad.php

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

Title:
  Support for Lenovo new TrackPad (ClickPad)

Status in HWE Next Project:
  New
Status in “xserver-xorg-input-synaptics” package in Ubuntu:
  Confirmed

Bug description:
  *This bug is under developing

  Affected model:

  L440 - with Ubuntu release: 12.04.5
  w540 - with Ubuntu release: 12.04.5
  X240
  T440p with Ubuntu release: 14.10(daily),  issue reported separately here with 
this bug #1383157

  Description:

  The Lenovo new TrackPad since 2014 starting to unify buttons into
  ClickPad, but in most case for now, upper middle scroll(selection) and
  upper left click, in generally it is not effecting normal use, however
  it is a trouble for user who use Trackpoint(Pointing Stick), which
  makes it useless since there is no wait to scroll with TrackPoint.

  Steps to reproduce:

  1. Open any webpage
  2. Trying to scroll page with TrackPoint

  1. Open any textfile with any editors
  2.  Trying to select and copy some text while using TrackPoint

  Actual result:

  Users need to move their hands off the keyboard and use the bottom of
  touchpad to perform actions all over again.

  Expected results:

  5 buttons on new TrackPad should works as expected.

  -
  Additional information:

  New Trackpad should be supported in Utopic according to this bug:
  https://bugs.launchpad.net/ubuntu/+source/libevdev/+bug/1294515

  -
  Reference information about the unified touchpad:

  ThinkPad TrackPad features promote page:
  http://shop.lenovo.com/us/en/laptops/thinkpad/trackpad/

  Synaptics ClickPad solution:
  http://www.synaptics.com/en/clickpad.php

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

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

[Desktop-packages] [Bug 971018] Re: Auto-hide Unity Launcher will not reveal when mouse pushed to left side in VirtualBox or VMware

2014-10-20 Thread Michał Szwejkowski

Still present on Ubuntu 14.10 VBox 4.3.18

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

Title:
  Auto-hide Unity Launcher will not reveal when mouse pushed to left
  side in VirtualBox or VMware

Status in Unity:
  Incomplete
Status in “libxfixes” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Incomplete
Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Precise 12.04 Beta 2 AMD64 DVD:
   
   
  I am running Ubuntu Precise 12.04 Beta 2 in a VirtualBox 4.1.8 session.  
VirtualBox Guest Additions have been installed via "jockey-gtk" from the Ubuntu 
Precise repository, and Unity is running in 3D mode with Compiz.
   
   
  When the Unity Launcher is set to "autohide," the Launcher will never reveal 
when the mouse pointer is moved to the left edge of the screen.  It does not 
matter how much "pressure" is applied; the Launcher never appears.
   
   
  I have tried the following VirtualBox window "form-factors," all with the 
same result (the Launcher never appears):
   
  -- VirtualBox session running in a non-maximized window
  -- VirtualBox session running in a maximized window
  -- VirtualBox session running full-screen
   
   
  I have attached a screen capture (OGV) with Ubuntu Precise running in a 
maximized VirtualBox window.
   
   
  Note:  This Bug may be related to the following other Bugs reported on 
LaunchPad:
   
  -- Bug 965643:  Unity 5.8: auto-hide using mouse reveals launcher 
inconsistently
  -- -- https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/965643

  -- Bug 923749:  New "push mouse offscreen" feature really difficult to get
  -- -- https://bugs.launchpad.net/unity/+bug/923749

  -- Bug 937792:  Left launcher does not revel when in autohide mode on 
multi-monitor setups
  -- -- https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/937792

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
  Uname: Linux 3.2.0-21-generic x86_64
  ApportVersion: 2.0-0ubuntu2
  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]
  Date: Sun Apr  1 14:46:23 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  ProcEnviron:
   TERM=xterm
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1383174] [NEW] i am a new user

2014-10-20 Thread Debasis Chaudhuri

Public bug reported:

i dont know what to do?

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 i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Oct 20 14:01:42 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6290] [1002:9807] 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:104c]
InstallationDate: Installed on 2014-08-24 (57 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
LightdmGreeterLog:
 ** (lightdm-gtk-greeter:9160): WARNING **: Failed to load user image: Failed 
to open file '/home/debasis/.face': No such file or directory
 g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1601): WARNING **: Failed to load 
user image: Failed to open file '/home/debasis/.face': No such file or directory
MachineType: ASUSTeK Computer Inc. K53U
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=479ef2c5-a812-47cc-a4cf-5a2f9f42be3d ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 221
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: K53U
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.:bvr221:bd03/12/2012:svnASUSTeKComputerInc.:pnK53U:pvr1.0:rvnASUSTeKComputerInc.:rnK53U:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: K53U
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
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.1
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.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Oct 20 13:45:05 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2.1
xserver.video_driver: radeon

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


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

Title:
  i am a new user

Status in “xorg” package in Ubuntu:
  New

Bug description:
  i dont know what to do?

  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 i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Oct 20 14:01:42 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6290] [1002:9807] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:104c]
  InstallationDate: Installed on 2014-08-24 (57 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:9160): WARNING **: Failed to load user image: Failed 
to open file '/home/debasis/.face': No such file or directory
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1601): WARNING **: Failed to 
load user image: Failed to open file '/home/debasis/.face': No such file or 
directory
  MachineType: ASUSTeK Computer Inc. K53U
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-

[Desktop-packages] [Bug 1041790]

2014-10-20 Thread Mika-kuoppala

*** Bug 85194 has been marked as a duplicate of this bug. ***

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

Title:
  [snb] GPU lockup  IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround
  i915.semaphores=0

Status in X.org xf86-video-intel:
  In Progress
Status in “linux” package in Ubuntu:
  Incomplete
Status in “sandybridge-meta” package in Ubuntu:
  Confirmed
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Triaged

Bug description:
  X locks up periodically for a 2 to ten seconds at a time and this
  crash log gets generated. It's significantly more than several times a
  day but not quite continuous. If you indeed have this bug, that should
  stop the lockups from happening. Irrespective, please file a new bug
  report so your hardware may be tracked.

  WORKAROUND: Edit your /etc/default/grub from:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

  to:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.semaphores=0"

  run the following and reboot:
  sudo update-grub

  The side effects of this is rendering throughput is dropped by 10%
  with SNA, or as much as 3x with UXA. OpenGL performance is likely to
  be reduced by about 30%. More CPU time is spent waiting for the GPU
  with rc6 disabled, so increased power consumption.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: xserver-xorg-video-intel 2:2.20.3-0ubuntu1
  Uname: Linux 3.6.0-rc3-git-20120826.1015 x86_64
  ApportVersion: 2.5.1-0ubuntu2
  Architecture: amd64
  Chipset: sandybridge-m-gt2
  Date: Sun Aug 26 16:06:32 2012
  DistroCodename: quantal
  DistroVariant: ubuntu
  DuplicateSignature: [sandybridge-m-gt2] GPU lockup  IPEHR: 0x0b160001 IPEHR: 
0x0b140001 Ubuntu 12.10
  EcryptfsInUse: Yes
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  GpuHangFrequency: Continuously
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
  InterpreterPath: /usr/bin/python3.2mu
  MachineType: Dell Inc. Dell System XPS L502X
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.0-rc3-git-20120826.1015 
root=UUID=135c8090-427c-460a-909d-eff262cd44b6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu3
   libdrm2  2.4.38-0ubuntu2
   xserver-xorg-video-intel 2:2.20.3-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Title: [sandybridge-m-gt2] GPU lockup  IPEHR: 0x0b160001 IPEHR: 0x0b140001
  UdevDb: Error: [Errno 2] No such file or directory: 'udevadm'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 05/29/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1383197] [NEW] eog half of the time freezes when pressing F11

2014-10-20 Thread Martin Vysny

Public bug reported:

Since upgrade to Utopic, pressing F11 in eog would cause sometimes eog
to freeze (the eog window goes black&white, the "Program stopped
responding" dialog pops out)

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: eog 3.12.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-23.30-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
ApportVersion: 2.14.7-0ubuntu7
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Oct 20 10:58:56 2014
InstallationDate: Installed on 2014-03-07 (226 days ago)
InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
SourcePackage: eog
UpgradeStatus: Upgraded to utopic on 2014-10-16 (3 days ago)

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


** Tags: amd64 apport-bug utopic

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

Title:
  eog half of the time freezes when pressing F11

Status in “eog” package in Ubuntu:
  New

Bug description:
  Since upgrade to Utopic, pressing F11 in eog would cause sometimes eog
  to freeze (the eog window goes black&white, the "Program stopped
  responding" dialog pops out)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: eog 3.12.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-23.30-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 20 10:58:56 2014
  InstallationDate: Installed on 2014-03-07 (226 days ago)
  InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  SourcePackage: eog
  UpgradeStatus: Upgraded to utopic on 2014-10-16 (3 days ago)

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

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

[Desktop-packages] [Bug 1383202] [NEW] Left touch pad button not working on Ubuntu (Gnome) 14.10 and kernel above 3.16.0-20

2014-10-20 Thread George Karavasilev

Public bug reported:

So, I've this Lenovo B50 laptop that runs Ubuntu Gnome 14.10 and for
some reason kernels:

3.16.0-23
3.16.0-22
3.16.0-21

Don't seem to recognise my left touchpad button, however it worked up to
kernel 3.16.0-20 and I've tested on Windows 8.1 (which I have installed
just in case) and the touchpad is perfectly functional and the left
button works like a charm. I am willing to provide any info you guys
need. Oh and - left clicking works with a mouse. Also - xorg edgers PPA
and using 3.17 mainline kernel don't seem to fix this.

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

** Description changed:

  So, I've this Lenovo B50 laptop that runs Ubuntu Gnome 14.10 and for
  some reason kernels:
  
  3.16.0-23
  3.16.0-22
  3.16.0-21
- Don't seem to recognise my left touchpad button, however it worked up to 
kernel 3.16.0-20 and I've tested on Windows 8.1 (which I have installed just in 
case) and the touchpad is perfectly functional and the left button works like a 
charm. I am willing to provide any info you guys need. Oh and - left clicking 
works with a mouse. Also - xorg edgers PPA and using 3.17 mainline kernel don't 
seem to fix this.
+ 
+ Don't seem to recognise my left touchpad button, however it worked up to
+ kernel 3.16.0-20 and I've tested on Windows 8.1 (which I have installed
+ just in case) and the touchpad is perfectly functional and the left
+ button works like a charm. I am willing to provide any info you guys
+ need. Oh and - left clicking works with a mouse. Also - xorg edgers PPA
+ and using 3.17 mainline kernel don't seem to fix this.

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

Title:
  Left touch pad button not working on Ubuntu (Gnome) 14.10 and kernel
  above 3.16.0-20

Status in “xorg” package in Ubuntu:
  New

Bug description:
  So, I've this Lenovo B50 laptop that runs Ubuntu Gnome 14.10 and for
  some reason kernels:

  3.16.0-23
  3.16.0-22
  3.16.0-21

  Don't seem to recognise my left touchpad button, however it worked up
  to kernel 3.16.0-20 and I've tested on Windows 8.1 (which I have
  installed just in case) and the touchpad is perfectly functional and
  the left button works like a charm. I am willing to provide any info
  you guys need. Oh and - left clicking works with a mouse. Also - xorg
  edgers PPA and using 3.17 mainline kernel don't seem to fix this.

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

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

[Desktop-packages] [Bug 1383207] [NEW] Different system settings show different sound cards and chosen sound card will only play on command line test.

2014-10-20 Thread Jamil V

Public bug reported:

$ lsb_release -rd
Description:Ubuntu 14.04.1 LTS
Release:14.04


Sound has been troublesome on my system.

I noticed this happened twice. I have two different system settings
programs (because of the first time this happened). In one program (KDE
system settings), my soundcard is listed, in the other (Ubuntu's default
system settings),  it is not listed. I cannot play sound out of it with
graphical desktop programs, but `aplay
/usr/share/sounds/alsa/Front_Center.wav` does play sound fine.

I followed these instructions:
https://help.ubuntu.com/community/SoundTroubleshooting

`pacmd` looked fine. My chosen sound card had an asterisk next to it.

`aplay /usr/share/sounds/alsa/Front_Center.wav` ran as user fine

`sudo aplay -l` lists it accurately

`find /lib/modules/`uname -r` | grep snd` gave an appropriate driver:
/lib/modules/3.13.0-37-generic/kernel/sound/pci/echoaudio/snd-layla24.ko

`lspci -v | grep -A7 -i "audio"` showed my sound card:
03:00.0 PCI bridge: Pericom Semiconductor PI7C9X111SL PCIe-to-PCI Reversible 
Bridge (rev 02) (prog-if 00 [Normal decode])
--
Subsystem: Echo Digital Audio Corporation Layla24
Flags: bus master, medium devsel, latency 192, IRQ 18
Memory at fa20 (32-bit, non-prefetchable) [size=1M]
Kernel driver in use: snd_layla24

I tried `modprobe snd_layla24` and `modprobe snd-layla24` with no
difference being made.


I tried adding it to /etc/modprobe.d/alsa-base.conf, but it still doesn't show 
up in the ubuntu system settings (gnome I think), which I think is the one that 
determines if it'll play through regular desktop applications or not (7th to 
last line snd_layla24):
--
# autoloader aliases
install sound-slot-0 /sbin/modprobe snd-card-0
install sound-slot-1 /sbin/modprobe snd-card-1
install sound-slot-2 /sbin/modprobe snd-card-2
install sound-slot-3 /sbin/modprobe snd-card-3
install sound-slot-4 /sbin/modprobe snd-card-4
install sound-slot-5 /sbin/modprobe snd-card-5
install sound-slot-6 /sbin/modprobe snd-card-6
install sound-slot-7 /sbin/modprobe snd-card-7

# Cause optional modules to be loaded above generic modules
install snd /sbin/modprobe --ignore-install snd $CMDLINE_OPTS && { 
/sbin/modprobe --quiet --use-blacklist snd-ioctl32 ; /sbin/modprobe --quiet 
--use-blacklist snd-seq ; }
#
# Workaround at bug #499695 (reverted in Ubuntu see LP #319505)
install snd-pcm /sbin/modprobe --ignore-install snd-pcm $CMDLINE_OPTS && { 
/sbin/modprobe --quiet --use-blacklist snd-pcm-oss ; : ; }
install snd-mixer /sbin/modprobe --ignore-install snd-mixer $CMDLINE_OPTS && { 
/sbin/modprobe --quiet --use-blacklist snd-mixer-oss ; : ; }
install snd-seq /sbin/modprobe --ignore-install snd-seq $CMDLINE_OPTS && { 
/sbin/modprobe --quiet --use-blacklist snd-seq-midi ; /sbin/modprobe --quiet 
--use-blacklist snd-seq-oss ; : ; }
#
install snd-rawmidi /sbin/modprobe --ignore-install snd-rawmidi $CMDLINE_OPTS 
&& { /sbin/modprobe --quiet --use-blacklist snd-seq-midi ; : ; }
# Cause optional modules to be loaded above sound card driver modules
install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 $CMDLINE_OPTS 
&& { /sbin/modprobe --quiet --use-blacklist snd-emu10k1-synth ; }
install snd-via82xx /sbin/modprobe --ignore-install snd-via82xx $CMDLINE_OPTS 
&& { /sbin/modprobe --quiet --use-blacklist snd-seq ; }

# Load saa7134-alsa instead of saa7134 (which gets dragged in by it anyway)
install saa7134 /sbin/modprobe --ignore-install saa7134 $CMDLINE_OPTS && { 
/sbin/modprobe --quiet --use-blacklist saa7134-alsa ; : ; }
# Prevent abnormal drivers from grabbing index 0
options bt87x index=-2
options cx88_alsa index=-2
options saa7134-alsa index=-2
options snd-atiixp-modem index=-2
options snd-intel8x0m index=-2
options snd-via82xx-modem index=-2
options snd-usb-audio index=-2
options snd-usb-caiaq index=-2
options snd-usb-ua101 index=-2
options snd-usb-us122l index=-2
options snd-usb-usx2y index=-2
options snd_layla24 index=0
# Ubuntu #62691, enable MPU for snd-cmipci
options snd-cmipci mpu_port=0x330 fm_port=0x388
# Keep snd-pcsp from being loaded as first soundcard
options snd-pcsp index=-2
# Keep snd-usb-audio from beeing loaded as first soundcard
options snd-usb-audio index=-2
--

I tried `sudo alsa reload`, `pulseaudio -k`, and `sudo pulseaudio -k`

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


** Tags: alsa audio pulseaudio sound sound-card

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

Title:
  Different system settings show different sound cards and chosen sound
  card will only play on command line test.

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

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  

  Sound has been troublesome on my system.

  I not

[Desktop-packages] [Bug 1363637] Re: Pitivi wont start TypeError: function takes at most 0 arguments (1 given)

2014-10-20 Thread sam tygier

seems fixed with 0.93-4ubuntu1

** Changed in: pitivi (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: gst-python1.0 (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Pitivi wont start TypeError: function takes at most 0 arguments (1
  given)

Status in PiTiVi , Non-linear video editor:
  Fix Released
Status in “gst-python1.0” package in Ubuntu:
  Fix Released
Status in “pitivi” package in Ubuntu:
  Fix Released

Bug description:
  Pitivi fails to start with the following backtrace

  Traceback (most recent call last):
File "/usr/bin/pitivi", line 136, in 
  _run_pitivi()
File "/usr/bin/pitivi", line 123, in _run_pitivi
  sys.exit(ptv.main(sys.argv))
File "/usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/application.py", line 
416, in main
  ptv = StartupWizardGuiPitivi(debug=options.debug)
File "/usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/application.py", line 
362, in __init__
  self.projectManager.newBlankProject(emission=False)
File "/usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/project.py", line 419, 
in newBlankProject
  project = Project(_("New Project"))
File "/usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/project.py", line 559, 
in __init__
  Gst.Caps("application/ogg"),
  TypeError: function takes at most 0 arguments (1 given)

  Looks like same as https://bugzilla.redhat.com/show_bug.cgi?id=1109481
  and https://bugzilla.gnome.org/show_bug.cgi?id=730596

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: pitivi 0.93-4
  ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1
  Uname: Linux 3.16.0-11-generic x86_64
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: amd64
  Date: Sun Aug 31 12:00:53 2014
  InstallationDate: Installed on 2014-08-09 (21 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - Alpha amd64 (20140731)
  SourcePackage: pitivi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1331813] Re: Support ipv6 mobile connections

2014-10-20 Thread richard mccormick

adb push is giving me permissions denied :/  ive tried everything
including the adb she manual setting of the apn and i still have no 3g
data, im only able to receive texts and make calls any idea on how to
circumvent this? i installed ubuntu touch through multi rom on the n5 if
that makes any difference

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

Title:
  Support ipv6 mobile connections

Status in “network-manager” package in Ubuntu:
  Confirmed
Status in “ofono” package in Ubuntu:
  Confirmed
Status in “ubuntu-download-manager” package in Ubuntu:
  Confirmed

Bug description:
  My new T-Mobile SIM only has Apn contexts using IPv6 so cellular data is not 
working
  Purchased the SIM a couple weeks ago.

  The output of the /usr/share/ofono/list-contexts is:

  [ /ril_0 ]
  [ /ril_0/context1 ]
  MessageProxy =
  Type = internet
  Password =
  Active = 1
  MessageCenter = http://mms.msg.eng.t-mobile.com/mms/wapenc
  Username =
  IPv6.Settings = { Interface=rmnet_usb0 }
  AccessPointName = fast.t-mobile.com
  Settings = { }
  Name = T-Mobile GPRS
  Protocol = ipv6

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

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

[Desktop-packages] [Bug 790173] [NEW] Cron doesn't send output properly

You have been subscribed to a public bug:

Binary package hint: cron

I have a bash script checking for new versions of Vim (in Bram
Moolenaar's Mercurial repository) that's run by cron. The script saves
its output into a log file and, if there is something interesting to
say, at the and does 'cat $LOG_FILE'. The problem is that when run by
cron on my newly installed Ubuntu 10.04.2 I don't get the output in mail
but only 'expr: syntax error' line instead.

Obviously I thought there was some error in the script at first, but
after trying and checking I've found none. Besides, the script runs OK
from command line and the same script runs OK from cron on Ubuntu 8.04.
And I've also found (via checking the script's log whilst it was
running) that it actually runs OK even here on Ubuntu 10.04.2, only I
don't get the output. Therefore I'm not even sure whether this bug
belongs to Cron or Postfix.

I've also tried to run by cron different parts of the script separately,
they worked OK and output in mail was OK too.

I think this might perhaps be related with this discussion I've googled:
http://www.howtoforge.com/forums/showthread.php?t=45202

Thx.

** Affects: speech-dispatcher (Ubuntu)
 Importance: Undecided
 Status: Fix Released

-- 
Cron doesn't send output properly
https://bugs.launchpad.net/bugs/790173
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to speech-dispatcher in Ubuntu.

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

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

2014-10-20 Thread Daniel Llewellyn

seems fixed after installing ibus-dbg along with the utopic updates
accumulated for a week or so installed just now at 09:40 GMT on the 20th
october. Unsure whether it was the ibus-dbg and it's dependencies or the
latest utopic updates that fixed things.

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT

Status in IBus:
  Unknown
Status in “ibus” package in Ubuntu:
  Triaged

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

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

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

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

[Desktop-packages] [Bug 790173] Re: Cron doesn't send output properly

2014-10-20 Thread Christian Kastner

Fix

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

** Package changed: cron (Ubuntu) => speech-dispatcher (Ubuntu)

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

Title:
  Cron doesn't send output properly

Status in “speech-dispatcher” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: cron

  I have a bash script checking for new versions of Vim (in Bram
  Moolenaar's Mercurial repository) that's run by cron. The script saves
  its output into a log file and, if there is something interesting to
  say, at the and does 'cat $LOG_FILE'. The problem is that when run by
  cron on my newly installed Ubuntu 10.04.2 I don't get the output in
  mail but only 'expr: syntax error' line instead.

  Obviously I thought there was some error in the script at first, but
  after trying and checking I've found none. Besides, the script runs OK
  from command line and the same script runs OK from cron on Ubuntu
  8.04. And I've also found (via checking the script's log whilst it was
  running) that it actually runs OK even here on Ubuntu 10.04.2, only I
  don't get the output. Therefore I'm not even sure whether this bug
  belongs to Cron or Postfix.

  I've also tried to run by cron different parts of the script
  separately, they worked OK and output in mail was OK too.

  I think this might perhaps be related with this discussion I've
  googled: http://www.howtoforge.com/forums/showthread.php?t=45202

  Thx.

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

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

[Desktop-packages] [Bug 1164083] Re: libreoffice spams stdout with "Fontconfig warning: ignoring C.UTF-8: not a valid language tag"

2014-10-20 Thread Mike Gerow

Facing the same issue. According to  this has been fixed in fontconfig=2.11.0-2

** Bug watch added: Debian Bug tracker #717423
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717423

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

Title:
  libreoffice spams stdout with "Fontconfig warning: ignoring C.UTF-8:
  not a valid language tag"

Status in “fontconfig” package in Ubuntu:
  New

Bug description:
  when libreoffice is started from the shell command line, it spams the 
terminal window with a stream of messages
  "Fontconfig warning: ignoring C.UTF-8: not a valid language tag"
  This message should be reported at most once per libreoffice invocation.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: fontconfig 2.10.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6
  Uname: Linux 3.5.0-26-generic x86_64
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  Date: Wed Apr  3 14:22:46 2013
  InstallationDate: Installed on 2011-11-01 (519 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  SourcePackage: fontconfig
  UpgradeStatus: Upgraded to quantal on 2013-03-21 (12 days ago)

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

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

[Desktop-packages] [Bug 1243806] Re: The names column has its width dictated by other columns

2014-10-20 Thread Todor Andreev

This is not ANNOYING. This is work BLOCKING! Please, realize it!

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

Title:
  The names column has its width dictated by other columns

Status in Nautilus:
  Invalid
Status in “nautilus” package in Ubuntu:
  Triaged
Status in “nautilus” source package in Trusty:
  Triaged

Bug description:
  Folder names in Location area keeps the width even though when I go back to 
upper folder.
  First of all this new downgraded nautilus folder section holds its width and 
I cannot even change the width at all.
  Then when I go deep down lower folders or open folder with long name, it 
would squeeze down the "Name" part and I cannot even see names anymore. Then 
when I go up to upper folder or root, I cannot see the names anymore becaue 
location column takes up all the space. Once I click one of the unseen folder, 
I may see the names again. 
  This is one of too many problems of 13.10.

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

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

[Desktop-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script

2014-10-20 Thread Martin Pitt

Gunnar,

Running it through "sh -n" is definitively a good way how to test a
shell script. It of course will miss a lot of errors (variable typos,
failing programs in a set -e script, etc.), but it at least will catch
obvious syntax errors. So ignoring faulty scripts and showing some error
message (in ~/.xsession-errors or even a dialog) seems appropriate to
me.

Thanks for working on this! I'll review the MP now.

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

Title:
  Error message for a faulty ~/.profile script

Status in Light Display Manager:
  In Progress
Status in “gdm” package in Ubuntu:
  Triaged
Status in “lightdm” package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: gdm

  After adding "function AddPath { PATH="$1:$PATH" }" to $HOME/.profile
  made the Xorg startup fail. (At that moment I had already forgotten
  the changes made to the .profile). As I had autologin that meant it
  kept trying to login and finally showed me the graphics
  reconfiguration screen. That sent me to a huge hunt for xorg conf and
  setup problems.

  Anyway finally tracked this down. I had used bash syntax in .profile
  file whereas it was run with sh.

  This is not a bug per se but I think a user mistake in ".profile"
  shouldn't bring the whole xorg startup to a halt as it does with
  autologin. I propose running user ".profile" and ".xprofile" scripts
  so that Xsession script continues running even if they have errors.
  I'm not sure whether this change would have some negative effects as
  well.

  1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 
16 19:48:22 UTC 2010 i686 GNU/Linux
  2) gdm 2.30.2.is.2.30.0-0ubuntu4

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

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

[Desktop-packages] [Bug 905686] Re: nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed.

2014-10-20 Thread Andy Smith

I don't know if this is at all relevant, but I also got the error
message:

"xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed" after
rebuilding and running an OPEN Windows (xview) application as a 32-bit
executable on a CentoS 6.4 x86_64 architecture. There is apparently no
native 64-bit xview - presumably because the data structures inherent in
the package assume 4 bytes for address pointers, and too much trouble to
re-engineer, hence the 32-bit build and the error here.

The problem was resolved here by explicitly linking to the dynamic run
time library:

"/usr/lib/libX11-xcb.so.1".

The linker does not require the libX11-xcb.so.1 to be specified, but it
clearly defaults to the 64-bit /usr/lib64/libX11-xcb.so.1 version. For
users where they only have a 32 bit binary xview application, there is
probably some Linux command to reset the default  libX11-xcb.so.1
dynamic library path.

Frankly I don't know much at all about the inner workings of Linux, but
this post may be hepful to anyone else who is having similar problems.
If irrelevant, please ignore.

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

Title:
  nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID:
  Assertion `ret != inval_id' failed.

Status in Modular X11 Libraries:
  Confirmed
Status in “libx11” package in Ubuntu:
  Triaged
Status in “nautilus” package in Ubuntu:
  Triaged

Bug description:
  Here is a backtrace from Ubuntu Precise.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.2.1-2ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-5.11-generic-pae 3.2.0-rc5
  Uname: Linux 3.2.0-5-generic-pae i686
  ApportVersion: 1.90-0ubuntu1
  Architecture: i386
  AssertionMessage: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret 
!= inval_id' failed.
  Date: Sat Dec 17 14:16:03 2011
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/nautilus
  ExecutableTimestamp: 1324036665
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcCmdline: nautilus -n
  ProcCwd: /
  Signal: 6
  SourcePackage: nautilus
  StacktraceTop:
   __kernel_vsyscall ()
   raise () from /lib/i386-linux-gnu/libc.so.6
   abort () from /lib/i386-linux-gnu/libc.so.6
   __assert_fail () from /lib/i386-linux-gnu/libc.so.6
   _XAllocID () from /usr/lib/i386-linux-gnu/libX11.so.6
  Title: nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID: 
Assertion `ret != inval_id' failed.
  UpgradeStatus: Upgraded to precise on 2011-12-16 (1 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare 
vboxusers

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

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

[Desktop-packages] [Bug 1382775] Re: XScreenSaver doesn't lock screen on suspend

2014-10-20 Thread Giulio De Pasquale

I added "sleep 2; xscreensaver-command -lock" in the shortcut but that
doesn't change anything. Even without sleeping the shortcut worked. When
I close the lid of my laptop (a Lenovo x230) I get the default Unity
lock screen and when the time set in xscreensaver settings expires, I
even have to unlock my desktop twice. I just want the xscreensaver one.

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

Title:
  XScreenSaver doesn't lock screen on suspend

Status in “xscreensaver” package in Ubuntu:
  Incomplete

Bug description:
  XScreenSaver does not lock screen on suspend even with gnome-screensaver 
removed. With the standard "CTRL-ALT-L" shortcut the screen is NOT locked with 
xscreensaver; this is solved by setting that shortcut to 'xscreensaver-command 
-lock'. 
  Even with these "workarounds" the screen is locked using Ubuntu's standard 
lock screen and not with xscreensaver's one.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xscreensaver 5.15-3ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Oct 18 12:03:02 2014
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: xscreensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1381475] Re: Firewire sound card registered by the name of the fw controller

2014-10-20 Thread Andras Muranyi

BTW not only Gnome Settings but also `pactl list` has the same info.
The right names are there too, however.

alsa.card = "0"
alsa.card_name = "PHASE 88 Rack FW"
alsa.long_card_name = "TerraTec Electronic Gmb PHASE 88 Rack FW 
(id:3, rev:1), GUID 000aac0300592827 a"
alsa.driver_name = "snd_bebob"
device.bus_path = "pci-:01:09.0"
sysfs.path = 
"/devices/pci:00/:00:09.0/:01:09.0/fw2/fw2.0/sound/card0"
udev.id = "firewire-0x000aac0300592827"
device.bus = "firewire"
device.vendor.name = "Texas Instruments"
device.product.name = "TSB43AB22A IEEE-1394a-2000 Controller 
(PHY/Link) [iOHCI-Lynx]"
device.string = "0"
device.description = "TSB43AB22A IEEE-1394a-2000 Controller 
(PHY/Link) [iOHCI-Lynx]"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-firewire"
profiles:
input:10-channels: 10 Channels Input (priority 10, available: 
unknown)
output:10-channels: 10 Channels Output (priority 1000, 
available: unknown)
output:10-channels+input:10-channels: 10 Channels Output + 10 
Channels Input (priority 1010, available: unknown)

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

Title:
  Firewire sound card registered by the name of the fw controller

Status in “pulseaudio” package in Ubuntu:
  Triaged

Bug description:
  I am testing the new snd-firewire ALSA module which is currently getting 
accepted into the kernel.
  I have noticed that while ALSA recognizes the correct name for the card, 
PulseAudio displays another, wrong name, which is apparently the name of the 
FireWire controller through which the sound card is connected.

  $ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: FW [PHASE 88 Rack FW], device 0: BeBoB [PHASE 88 Rack FW PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0

  $ pacmd list-sinks
  Welcome to PulseAudio! Use "help" for usage information.
  >>> 4 sink(s) available.
  [...]
  index: 2
name: 
driver: 
flags: HARDWARE DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
state: SUSPENDED
suspend cause: IDLE 
priority: 9000
volume: 0: 100% 1: 100% 2: 100% 3: 100% 4: 100% 5: 100% 6: 100% 7: 100% 
8: 100% 9: 100%
0: 0,00 dB 1: 0,00 dB 2: 0,00 dB 3: 0,00 dB 4: 0,00 dB 5: 0,00 
dB 6: 0,00 dB 7: 0,00 dB 8: 0,00 dB 9: 0,00 dB
balance 0,00
base volume: 100%
 0,00 dB
volume steps: 65537
muted: no
current latency: 0,00 ms
max request: 0 KiB
max rewind: 0 KiB
monitor source: 5
sample spec: s16le 10ch 44100Hz
channel map: 
front-left,front-right,rear-left,rear-right,front-center,lfe,side-left,side-right,aux0,aux1
used by: 0
linked by: 0
configured latency: 0,00 ms; range is 0,50 .. 185,76 ms
card: 3 
module: 8
properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "PHASE 88 Rack FW PCM"
alsa.id = "BeBoB"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "0"
alsa.card_name = "PHASE 88 Rack FW"
alsa.long_card_name = "TerraTec Electronic Gmb PHASE 88 Rack FW 
(id:3, rev:1), GUID 000aac0300592827 a"
alsa.driver_name = "snd_bebob"
device.bus_path = "pci-:01:09.0"
sysfs.path = 
"/devices/pci:00/:00:09.0/:01:09.0/fw2/fw2.0/sound/card0"
udev.id = "firewire-0x000aac0300592827"
device.bus = "firewire"
device.vendor.name = "Texas Instruments"
device.product.name = "TSB43AB22A IEEE-1394a-2000 Controller 
(PHY/Link) [iOHCI-Lynx]"
device.string = "hw:0"
device.buffering.buffer_size = "163840"
device.buffering.fragment_size = "81920"
device.access_mode = "mmap+timer"
device.profile.name = "10-channels"
device.profile.description = "10 Channels"
device.description = "TSB43AB22A IEEE-1394a-2000 Controller 
(PHY/Link) [iOHCI-Lynx] 10 Channels"
alsa.mixer_name = "PHASE 88 Rack FW"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-firewire"

  
  PulseAudio 1:4.0-0ubuntu11

To manage notifications about this bug go to:
https://bugs.launchpad

[Desktop-packages] [Bug 1240198] Re: Wrong keyboard layout active after booting into desktop

2014-10-20 Thread Cheddie Merai

My problem was when I run gnome-shell --replace, the keyboard layout
changes fron UK to US.

I fixed it by following https://bugs.launchpad.net/ubuntu/+source/indicator-
keyboard/+bug/1240198">Comment 19's fix.

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

Title:
  Wrong keyboard layout active after booting into desktop

Status in “ibus” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged

Bug description:
  I upgraded from raring to saucy.

  After booting into the desktop (unity), the english keyboard layout is
  active, although everything on the system is set to be german
  (keyboard layout, language...)

  Switching to a virtual terminal (ctrl+alt+f1) fixes the problem and
  changes the layout to the german layout.

  all the time, the new input settings indicator says the german layout
  is active.

  locale says: 
  LANG=de_DE.UTF-8
  LANGUAGE=de_DE
  LC_CTYPE="de_DE.UTF-8"
  LC_NUMERIC="de_DE.UTF-8"
  LC_TIME="de_DE.UTF-8"
  LC_COLLATE="de_DE.UTF-8"
  LC_MONETARY="de_DE.UTF-8"
  LC_MESSAGES="de_DE.UTF-8"
  LC_PAPER="de_DE.UTF-8"
  LC_NAME="de_DE.UTF-8"
  LC_ADDRESS="de_DE.UTF-8"
  LC_TELEPHONE="de_DE.UTF-8"
  LC_MEASUREMENT="de_DE.UTF-8"
  LC_IDENTIFICATION="de_DE.UTF-8"
  LC_ALL=

  /etc/default/keyboard says:
  # Check /usr/share/doc/keyboard-configuration/README.Debian for
  # documentation on what to do after having modified this file.

  # The following variables describe your keyboard and can have the same
  # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options
  # in /etc/X11/xorg.conf.

  XKBMODEL="pc105"
  XKBLAYOUT="de"
  XKBVARIANT=""
  XKBOPTIONS=""

  # If you don't want to use the XKB layout on the console, you can
  # specify an alternative keymap.  Make sure it will be accessible
  # before /usr is mounted.
  # KMAP=/etc/console-setup/defkeymap.kmap.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20131010.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:49:03 2013
  InstallationDate: Installed on 2013-04-26 (171 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: indicator-keyboard
  UpgradeStatus: Upgraded to saucy on 2013-10-13 (2 days ago)

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

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

[Desktop-packages] [Bug 1383144] [NEW] Apple devices won't unmount after they are unplugged, plugging in again causes windows to appear that don't respond to user input

You have been subscribed to a public bug:

Version: Linux Mint 17
What I did: I simply plugged in my iPhone to charge it and then unplugged it 
after Mint recognized it and the Autorun windows popped up. I then disconnected 
my iPhone and reconnected it later.
What happened: Well, a couple of things. First, when I unplugged, the Autorun 
windows disappeared, as expected. However, the real problem lies when I plug 
the phone back in. I plug it in and Mint tells me, "Location is already 
mounted," and that window, along with the Autorun windows, will not go away. I 
have to restart my computer in order to make these windows go away, or remember 
to unmount the drive before disconnecting (which can be hard when using the 
computer simply for USB power).
What I expected to happen instead: I expected these windows not to show up and 
for the iPhone to unmount automatically when I disconnected it. There are two 
partitions (I guess they're partitions?) that should have unmounted upon 
disconnecting: The main partition and the Documents partition.
This problem always happens with the mentioned steps. It also happens with my 
iPod Touch.

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


** Tags: apple iphone ipod mount mounting unmount unmounting
-- 
Apple devices won't unmount after they are unplugged, plugging in again causes 
windows to appear that don't respond to user input
https://bugs.launchpad.net/bugs/1383144
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to libimobiledevice in Ubuntu.

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

[Desktop-packages] [Bug 1383144] Re: Apple devices won't unmount after they are unplugged, plugging in again causes windows to appear that don't respond to user input

2014-10-20 Thread Monsta

** Project changed: linuxmint => libimobiledevice (Ubuntu)

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

Title:
  Apple devices won't unmount after they are unplugged, plugging in
  again causes windows to appear that don't respond to user input

Status in “libimobiledevice” package in Ubuntu:
  New

Bug description:
  Version: Linux Mint 17
  What I did: I simply plugged in my iPhone to charge it and then unplugged it 
after Mint recognized it and the Autorun windows popped up. I then disconnected 
my iPhone and reconnected it later.
  What happened: Well, a couple of things. First, when I unplugged, the Autorun 
windows disappeared, as expected. However, the real problem lies when I plug 
the phone back in. I plug it in and Mint tells me, "Location is already 
mounted," and that window, along with the Autorun windows, will not go away. I 
have to restart my computer in order to make these windows go away, or remember 
to unmount the drive before disconnecting (which can be hard when using the 
computer simply for USB power).
  What I expected to happen instead: I expected these windows not to show up 
and for the iPhone to unmount automatically when I disconnected it. There are 
two partitions (I guess they're partitions?) that should have unmounted upon 
disconnecting: The main partition and the Documents partition.
  This problem always happens with the mentioned steps. It also happens with my 
iPod Touch.

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

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

[Desktop-packages] [Bug 1237121] Re: Keyboard: cannot bind "Alt L" to "Key to show the HUD" => Disabled

2014-10-20 Thread Silviu C.

This happens on Ubuntu 14.04 too with keyboard configured to English US.
No other mappings.

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

Title:
  Keyboard: cannot bind "Alt L" to "Key to show the HUD" => Disabled

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

Bug description:
  When clicking on "Key to show the HUD" in the Keyboard's Shortcuts settings, 
I cannot set the default itself:
   1. Pressing the left Alt key results in the shortcut to get disabled (it 
says "Disabled" then)
   2. There's no possibility to cancel the editing
   3. There's no possibility to reset the value to its defaul

  WORKAROUND: use ccsm and (re-)configure the shortcut in the Ubuntu
  Unity Plugin.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu43
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Wed Oct  9 00:47:05 2013
  InstallationDate: Installed on 2012-05-28 (498 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to saucy on 2013-10-08 (0 days ago)

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

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

[Desktop-packages] [Bug 1315264] Re: "More extensions..." link inside gThumb UI leads to non-existing page

2014-10-20 Thread Monsta

** Package changed: gtk+2.0 (Ubuntu) => ubuntu

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

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

Title:
  "More extensions..." link inside gThumb UI leads to non-existing page

Status in “gthumb” package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Open gThumb on up-to-date Ubuntu 2014.04
  2. Click Settings > Extensions
  3. Click on "More extensions..."
  4. Browser is opened at https://wiki.gnome.org/gthumb/extensions
  5. PROBLEM: That page says "This page does not exist yet"

  Reproducibility: Always
  gThumb version: 3.2.7

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

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

[Desktop-packages] [Bug 1381475] Re: Firewire sound card registered by the name of the fw controller

2014-10-20 Thread Takashi Sakamoto

Hi David,

> The ID_MODEL_FROM_DATABASE is probably set (for the firewire controller) by 
> udev/systemd,
> see the "hwdb" directory of systemd sources.

Exactly. I've already realized it and it require discussion between
ALSA, PulseAudio and systemd about which part of userspace has these
information for FireWire sound devices. This requires a batch of time so
I made it pending. Currently I would like to concentrate on my work for
ALSA kernel-land.

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

Title:
  Firewire sound card registered by the name of the fw controller

Status in “pulseaudio” package in Ubuntu:
  Triaged

Bug description:
  I am testing the new snd-firewire ALSA module which is currently getting 
accepted into the kernel.
  I have noticed that while ALSA recognizes the correct name for the card, 
PulseAudio displays another, wrong name, which is apparently the name of the 
FireWire controller through which the sound card is connected.

  $ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: FW [PHASE 88 Rack FW], device 0: BeBoB [PHASE 88 Rack FW PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0

  $ pacmd list-sinks
  Welcome to PulseAudio! Use "help" for usage information.
  >>> 4 sink(s) available.
  [...]
  index: 2
name: 
driver: 
flags: HARDWARE DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
state: SUSPENDED
suspend cause: IDLE 
priority: 9000
volume: 0: 100% 1: 100% 2: 100% 3: 100% 4: 100% 5: 100% 6: 100% 7: 100% 
8: 100% 9: 100%
0: 0,00 dB 1: 0,00 dB 2: 0,00 dB 3: 0,00 dB 4: 0,00 dB 5: 0,00 
dB 6: 0,00 dB 7: 0,00 dB 8: 0,00 dB 9: 0,00 dB
balance 0,00
base volume: 100%
 0,00 dB
volume steps: 65537
muted: no
current latency: 0,00 ms
max request: 0 KiB
max rewind: 0 KiB
monitor source: 5
sample spec: s16le 10ch 44100Hz
channel map: 
front-left,front-right,rear-left,rear-right,front-center,lfe,side-left,side-right,aux0,aux1
used by: 0
linked by: 0
configured latency: 0,00 ms; range is 0,50 .. 185,76 ms
card: 3 
module: 8
properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "PHASE 88 Rack FW PCM"
alsa.id = "BeBoB"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "0"
alsa.card_name = "PHASE 88 Rack FW"
alsa.long_card_name = "TerraTec Electronic Gmb PHASE 88 Rack FW 
(id:3, rev:1), GUID 000aac0300592827 a"
alsa.driver_name = "snd_bebob"
device.bus_path = "pci-:01:09.0"
sysfs.path = 
"/devices/pci:00/:00:09.0/:01:09.0/fw2/fw2.0/sound/card0"
udev.id = "firewire-0x000aac0300592827"
device.bus = "firewire"
device.vendor.name = "Texas Instruments"
device.product.name = "TSB43AB22A IEEE-1394a-2000 Controller 
(PHY/Link) [iOHCI-Lynx]"
device.string = "hw:0"
device.buffering.buffer_size = "163840"
device.buffering.fragment_size = "81920"
device.access_mode = "mmap+timer"
device.profile.name = "10-channels"
device.profile.description = "10 Channels"
device.description = "TSB43AB22A IEEE-1394a-2000 Controller 
(PHY/Link) [iOHCI-Lynx] 10 Channels"
alsa.mixer_name = "PHASE 88 Rack FW"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-firewire"

  
  PulseAudio 1:4.0-0ubuntu11

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

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

[Desktop-packages] [Bug 1243806] Re: The names column has its width dictated by other columns

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

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

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

** Changed in: nautilus
 Remote watch: GNOME Bug Tracker #693459 => GNOME Bug Tracker #732004

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

Title:
  The names column has its width dictated by other columns

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

Bug description:
  Folder names in Location area keeps the width even though when I go back to 
upper folder.
  First of all this new downgraded nautilus folder section holds its width and 
I cannot even change the width at all.
  Then when I go deep down lower folders or open folder with long name, it 
would squeeze down the "Name" part and I cannot even see names anymore. Then 
when I go up to upper folder or root, I cannot see the names anymore becaue 
location column takes up all the space. Once I click one of the unseen folder, 
I may see the names again. 
  This is one of too many problems of 13.10.

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

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

[Desktop-packages] [Bug 1383283] [NEW] Видеокарта 63: проба на режим 800x600@60Hz с изход 1920x1080@60Hz

2014-10-20 Thread Кристиян

Public bug reported:

os -vmware worcstation guest ubunu

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Oct 20 05:32:30 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2014-10-11 (8 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 004: ID 0471:032d Philips (or NXP) SPC 210NC PC Camera
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=bbaf7775-a595-444a-a59e-2067c8300bda ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/31/2013
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
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.1
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.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Oct 20 05:30:06 2014
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputVMware VMware Virtual USB Mouse MOUSE, id 7
 inputgspca_zc3xx  KEYBOARD, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
 inputImPS/2 Generic Wheel Mouse MOUSE, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: OutputVirtual2 
   Virtual3Virtual4Virtual5Virtual6Virtual7 
   Virtual8
xserver.version: 2:1.15.1-0ubuntu2.1
xserver.video_driver: vmware

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


** Tags: apport-bug compiz-0.9 i386 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/1383283

Title:
  Видеокарта 63: проба на режим 800x600@60Hz с изход 1920x1080@60Hz

Status in “xorg” package in Ubuntu:
  New

Bug description:
  os -vmware worcstation guest ubunu

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Oct 20 05:32:30 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2014-10-11 (8 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0471:032d Philips (or NXP) SPC 210NC PC Camera
   Bus 002 Device 003: ID 0e0f:0002 VMware,

[Desktop-packages] [Bug 1243806] Re: The names column has its width dictated by other columns

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

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

Title:
  The names column has its width dictated by other columns

Status in Nautilus:
  Unknown
Status in “nautilus” package in Ubuntu:
  Fix Committed
Status in “nautilus” source package in Trusty:
  Triaged

Bug description:
  Folder names in Location area keeps the width even though when I go back to 
upper folder.
  First of all this new downgraded nautilus folder section holds its width and 
I cannot even change the width at all.
  Then when I go deep down lower folders or open folder with long name, it 
would squeeze down the "Name" part and I cannot even see names anymore. Then 
when I go up to upper folder or root, I cannot see the names anymore becaue 
location column takes up all the space. Once I click one of the unseen folder, 
I may see the names again. 
  This is one of too many problems of 13.10.

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

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

[Desktop-packages] [Bug 1243806] Re: The names column has its width dictated by other columns

2014-10-20 Thread floid

Oof.  Well, glad someone may be addressing it - kudos and all love to
Carlos Soriano, it appears?

https://bugzilla.gnome.org/show_bug.cgi?id=732004#c3

Apparently it's a simple one-liner: https://bug732004.bugzilla-
attachments.gnome.org/attachment.cgi?id=284244

...that won't be in upstream until GNOME 3.16, and Ubuntu is sticking
with GNOME 3.12 stuff for Ubuntu 14.10.  Any chance that is cherry-pick-
able?

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

Title:
  The names column has its width dictated by other columns

Status in Nautilus:
  Unknown
Status in “nautilus” package in Ubuntu:
  Fix Committed
Status in “nautilus” source package in Trusty:
  Triaged

Bug description:
  Folder names in Location area keeps the width even though when I go back to 
upper folder.
  First of all this new downgraded nautilus folder section holds its width and 
I cannot even change the width at all.
  Then when I go deep down lower folders or open folder with long name, it 
would squeeze down the "Name" part and I cannot even see names anymore. Then 
when I go up to upper folder or root, I cannot see the names anymore becaue 
location column takes up all the space. Once I click one of the unseen folder, 
I may see the names again. 
  This is one of too many problems of 13.10.

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

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

[Desktop-packages] [Bug 1243806] Re: The names column has its width dictated by other columns

@floid, already done, 
https://launchpad.net/ubuntu/utopic/+queue?queue_state=1&queue_text=nautilus

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

Title:
  The names column has its width dictated by other columns

Status in Nautilus:
  Unknown
Status in “nautilus” package in Ubuntu:
  Fix Committed
Status in “nautilus” source package in Trusty:
  Triaged

Bug description:
  Folder names in Location area keeps the width even though when I go back to 
upper folder.
  First of all this new downgraded nautilus folder section holds its width and 
I cannot even change the width at all.
  Then when I go deep down lower folders or open folder with long name, it 
would squeeze down the "Name" part and I cannot even see names anymore. Then 
when I go up to upper folder or root, I cannot see the names anymore becaue 
location column takes up all the space. Once I click one of the unseen folder, 
I may see the names again. 
  This is one of too many problems of 13.10.

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

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

[Desktop-packages] [Bug 1381721] Re: unity8 crashed with SIGSEGV in intelClear()

** Changed in: mir
   Status: New => Incomplete

** Changed in: mesa (Ubuntu)
   Status: New => Incomplete

** Changed in: mir (Ubuntu)
   Status: New => Incomplete

** Changed in: unity8 (Ubuntu)
   Status: New => Incomplete

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

Title:
  unity8 crashed with SIGSEGV in intelClear()

Status in Mir:
  Incomplete
Status in “mesa” package in Ubuntu:
  Incomplete
Status in “mir” package in Ubuntu:
  Incomplete
Status in “unity8” package in Ubuntu:
  Incomplete

Bug description:
  I tied the daliy image on my eeepc t91mt but it looks like it crashed on 
startup.
  I just see a black screen and the cursor.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: unity8 8.00+14.10.20141013.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic i686
  ApportVersion: 2.14.7-0ubuntu6
  Architecture: i386
  CasperVersion: 1.345
  Date: Wed Oct 15 19:38:11 2014
  ExecutablePath: /usr/bin/unity8
  ExecutableTimestamp: 1413216480
  LiveMediaBuild: Ubuntu-Desktop-Next 14.10 "Utopic Unicorn" - Alpha i386 
(20141015)
  ProcCmdline: unity8
  ProcCwd: /home/ubuntu-desktop-next
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xb15f9921:cmpl   $0x2,0x18(%eax)
   PC (0xb15f9921) ok
   source "$0x2" ok
   destination "0x18(%eax)" (0x0018) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so
   ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so
   QSGBindable::clear(QFlags) const () from 
/usr/lib/i386-linux-gnu/libQt5Quick.so.5
   QSGBatchRenderer::Renderer::renderBatches() () from 
/usr/lib/i386-linux-gnu/libQt5Quick.so.5
   QSGBatchRenderer::Renderer::render() () from 
/usr/lib/i386-linux-gnu/libQt5Quick.so.5
  SystemImageInfo:
   current build number: 0
   device name:
   channel: daily
   last update: Unknown
  Title: unity8 crashed with SIGSEGV in QSGBindable::clear()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  upstart.unity8-dash.log:
   UbuntuClientIntegration: connection to Mir server failed. Check that a Mir 
server is
   running, and the correct socket is being used and is accessible. The shell 
may have
   rejected the incoming connection, so check its log file

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

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

[Desktop-packages] [Bug 1381721] Re: unity8 crashed with SIGSEGV in intelClear()

I wouldn't expect this crash on i915 but we are aware that GL clients
like Unity8 will be all-black right now. That's bug 1275398.

Once bug 1275398 is solved then this bug might go away. Last I heard, we should 
expect that to get fixed when Mesa 10.3.1 enters utopic:
https://launchpad.net/ubuntu/+source/mesa

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

Title:
  unity8 crashed with SIGSEGV in intelClear()

Status in Mir:
  New
Status in “mesa” package in Ubuntu:
  New
Status in “mir” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  I tied the daliy image on my eeepc t91mt but it looks like it crashed on 
startup.
  I just see a black screen and the cursor.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: unity8 8.00+14.10.20141013.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic i686
  ApportVersion: 2.14.7-0ubuntu6
  Architecture: i386
  CasperVersion: 1.345
  Date: Wed Oct 15 19:38:11 2014
  ExecutablePath: /usr/bin/unity8
  ExecutableTimestamp: 1413216480
  LiveMediaBuild: Ubuntu-Desktop-Next 14.10 "Utopic Unicorn" - Alpha i386 
(20141015)
  ProcCmdline: unity8
  ProcCwd: /home/ubuntu-desktop-next
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xb15f9921:cmpl   $0x2,0x18(%eax)
   PC (0xb15f9921) ok
   source "$0x2" ok
   destination "0x18(%eax)" (0x0018) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so
   ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so
   QSGBindable::clear(QFlags) const () from 
/usr/lib/i386-linux-gnu/libQt5Quick.so.5
   QSGBatchRenderer::Renderer::renderBatches() () from 
/usr/lib/i386-linux-gnu/libQt5Quick.so.5
   QSGBatchRenderer::Renderer::render() () from 
/usr/lib/i386-linux-gnu/libQt5Quick.so.5
  SystemImageInfo:
   current build number: 0
   device name:
   channel: daily
   last update: Unknown
  Title: unity8 crashed with SIGSEGV in QSGBindable::clear()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  upstart.unity8-dash.log:
   UbuntuClientIntegration: connection to Mir server failed. Check that a Mir 
server is
   running, and the correct socket is being used and is accessible. The shell 
may have
   rejected the incoming connection, so check its log file

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

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

[Desktop-packages] [Bug 1381721] Re: unity8 crashed with SIGSEGV in intelClear()

** Information type changed from Private to Public

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

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

Title:
  unity8 crashed with SIGSEGV in intelClear()

Status in Mir:
  New
Status in “mesa” package in Ubuntu:
  New
Status in “mir” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  I tied the daliy image on my eeepc t91mt but it looks like it crashed on 
startup.
  I just see a black screen and the cursor.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: unity8 8.00+14.10.20141013.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic i686
  ApportVersion: 2.14.7-0ubuntu6
  Architecture: i386
  CasperVersion: 1.345
  Date: Wed Oct 15 19:38:11 2014
  ExecutablePath: /usr/bin/unity8
  ExecutableTimestamp: 1413216480
  LiveMediaBuild: Ubuntu-Desktop-Next 14.10 "Utopic Unicorn" - Alpha i386 
(20141015)
  ProcCmdline: unity8
  ProcCwd: /home/ubuntu-desktop-next
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xb15f9921:cmpl   $0x2,0x18(%eax)
   PC (0xb15f9921) ok
   source "$0x2" ok
   destination "0x18(%eax)" (0x0018) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so
   ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so
   QSGBindable::clear(QFlags) const () from 
/usr/lib/i386-linux-gnu/libQt5Quick.so.5
   QSGBatchRenderer::Renderer::renderBatches() () from 
/usr/lib/i386-linux-gnu/libQt5Quick.so.5
   QSGBatchRenderer::Renderer::render() () from 
/usr/lib/i386-linux-gnu/libQt5Quick.so.5
  SystemImageInfo:
   current build number: 0
   device name:
   channel: daily
   last update: Unknown
  Title: unity8 crashed with SIGSEGV in QSGBindable::clear()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  upstart.unity8-dash.log:
   UbuntuClientIntegration: connection to Mir server failed. Check that a Mir 
server is
   running, and the correct socket is being used and is accessible. The shell 
may have
   rejected the incoming connection, so check its log file

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

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

[Desktop-packages] [Bug 1243806] Re: The names column has its width dictated by other columns

2014-10-20 Thread floid

@Sebastien Bacher:  Awesome, thanks!  From the timing I guess that
landed between visiting Launchpad and finishing typing.   (Obviously got
all that from your link to the GNOME bug just prior but I wasn't sure
how much activity that indicated.)

Now to actually try it out after work... :)

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

Title:
  The names column has its width dictated by other columns

Status in Nautilus:
  Fix Released
Status in “nautilus” package in Ubuntu:
  Fix Committed
Status in “nautilus” source package in Trusty:
  Triaged

Bug description:
  Folder names in Location area keeps the width even though when I go back to 
upper folder.
  First of all this new downgraded nautilus folder section holds its width and 
I cannot even change the width at all.
  Then when I go deep down lower folders or open folder with long name, it 
would squeeze down the "Name" part and I cannot even see names anymore. Then 
when I go up to upper folder or root, I cannot see the names anymore becaue 
location column takes up all the space. Once I click one of the unseen folder, 
I may see the names again. 
  This is one of too many problems of 13.10.

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

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

[Desktop-packages] [Bug 1381484] Re: Fails to connect to irc.slack.com with an SSL error

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

** Also affects: xchat-gnome via
   https://bugzilla.gnome.org/show_bug.cgi?id=738870
   Importance: Unknown
   Status: Unknown

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

Title:
  Fails to connect to irc.slack.com with an SSL error

Status in GNOME frontend to the popular xchat IRC client:
  Unknown
Status in “xchat-gnome” package in Ubuntu:
  Confirmed
Status in “xchat-gnome” source package in Precise:
  Confirmed
Status in “xchat-gnome” source package in Trusty:
  Confirmed
Status in “xchat-gnome” source package in Utopic:
  Confirmed

Bug description:
  slack.com is a chat service with optional IRC integration.  Since
  today I can no longer connect to their IRC gateway using XChat-GNOME.
  The error is:

  > * Nepavyko prisijungti. Klaida: (336130315) error:1408F10B:SSL 
routines:SSL3_GET_RECORD:wrong version number
  > Ar tai tikrai SSL šifravimą palaikantis serveris ir prievadas?

  which, translated from lt_LT, means

  > * Cannot connect.  Error: (336130315) error:1408F10B:SSL 
routines:SSL3_GET_RECORD:wrong version number
  > Does the server/port really support SSL?

  I think this is part of the fallout of CVE-2014-3566 (aka POODLE).
  XChat-GNOME is trying to use the insecure SSL protocol version 3, and
  Slack, reasonably enough, rejects that.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xchat-gnome 1:0.30.0~git20131003.d20b8d+really20110821-0.2ubuntu12
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct 15 14:50:57 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-07-25 (811 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: xchat-gnome
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (180 days ago)

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

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

[Desktop-packages] [Bug 1383321] [NEW] Support XDG DesktopNames field in session files

2014-10-20 Thread Robert Ancell

Public bug reported:

[Impact]
LightDM doesn't support the XDG standard "DesktopNames" field in session 
.desktop files. Instead we only support X-LightDM-DesktopName which was used 
before the standard was set. Newer sessions might expect DesktopNames to work.

[Test Case]
1. Install a session which has DesktopNames set in 
/usr/share/xsessions/name.desktop. i.e. DesktopNames=GNOME;Unity;
2. Start this session
Expected result:
XDG_CURRENT_DESKTOP is set to GNOME:Unity
Observed result:
XDG_CURRENT_DESKTOP is not set

[Regression Potential]
Low. This feature is only activated if the field is set.

** Affects: lightdm
 Importance: Medium
 Status: Fix Released

** Affects: lightdm/1.10
 Importance: Medium
 Status: Fix Committed

** Affects: lightdm (Ubuntu)
 Importance: Medium
 Status: Fix Released

** Affects: lightdm (Ubuntu Trusty)
 Importance: Medium
 Status: New

** Affects: lightdm (Ubuntu Utopic)
 Importance: Medium
 Status: Fix Released

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

** Also affects: lightdm (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: lightdm (Ubuntu Utopic)
   Importance: Undecided
   Status: New

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

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

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

** Also affects: lightdm/1.10
   Importance: Undecided
   Status: New

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

** Changed in: lightdm
   Status: New => Fix Released

** Changed in: lightdm/1.10
   Status: New => Fix Committed

** Changed in: lightdm/1.10
   Importance: Undecided => Medium

** Changed in: lightdm/1.10
Milestone: None => 1.10.4

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

Title:
  Support XDG DesktopNames field in session files

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “lightdm” source package in Trusty:
  New
Status in “lightdm” source package in Utopic:
  Fix Released

Bug description:
  [Impact]
  LightDM doesn't support the XDG standard "DesktopNames" field in session 
.desktop files. Instead we only support X-LightDM-DesktopName which was used 
before the standard was set. Newer sessions might expect DesktopNames to work.

  [Test Case]
  1. Install a session which has DesktopNames set in 
/usr/share/xsessions/name.desktop. i.e. DesktopNames=GNOME;Unity;
  2. Start this session
  Expected result:
  XDG_CURRENT_DESKTOP is set to GNOME:Unity
  Observed result:
  XDG_CURRENT_DESKTOP is not set

  [Regression Potential]
  Low. This feature is only activated if the field is set.

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

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

[Desktop-packages] [Bug 1292113] Re: CTRL+ALT+T - shortcut to open Terminal is does not work

2014-10-20 Thread Ajith R Nair

i have the same issue!

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

Title:
  CTRL+ALT+T - shortcut to open Terminal is does not work

Status in GNOME Terminal:
  New
Status in “gnome-terminal” package in Ubuntu:
  Confirmed

Bug description:
  The global shortcut CTRL+ALT+T to open a new terminal windows is missing in 
Ubuntu since 14.04
  Please reenable it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-terminal 3.6.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 13 18:01:32 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-10 (92 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to trusty on 2014-03-07 (6 days ago)

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

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

[Desktop-packages] [Bug 1243806] Re: The names column has its width dictated by other columns

2014-10-20 Thread Bug Watch Updater

** Changed in: nautilus
   Status: Unknown => Fix Released

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

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

Title:
  The names column has its width dictated by other columns

Status in Nautilus:
  Fix Released
Status in “nautilus” package in Ubuntu:
  Fix Committed
Status in “nautilus” source package in Trusty:
  Triaged

Bug description:
  Folder names in Location area keeps the width even though when I go back to 
upper folder.
  First of all this new downgraded nautilus folder section holds its width and 
I cannot even change the width at all.
  Then when I go deep down lower folders or open folder with long name, it 
would squeeze down the "Name" part and I cannot even see names anymore. Then 
when I go up to upper folder or root, I cannot see the names anymore becaue 
location column takes up all the space. Once I click one of the unseen folder, 
I may see the names again. 
  This is one of too many problems of 13.10.

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

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

[Desktop-packages] [Bug 1383321] Re: Support XDG DesktopNames field in session files

** Branch linked: lp:lightdm/1.10

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

Title:
  Support XDG DesktopNames field in session files

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “lightdm” source package in Trusty:
  New
Status in “lightdm” source package in Utopic:
  Fix Released

Bug description:
  [Impact]
  LightDM doesn't support the XDG standard "DesktopNames" field in session 
.desktop files. Instead we only support X-LightDM-DesktopName which was used 
before the standard was set. Newer sessions might expect DesktopNames to work.

  [Test Case]
  1. Install a session which has DesktopNames set in 
/usr/share/xsessions/name.desktop. i.e. DesktopNames=GNOME;Unity;
  2. Start this session
  Expected result:
  XDG_CURRENT_DESKTOP is set to GNOME:Unity
  Observed result:
  XDG_CURRENT_DESKTOP is not set

  [Regression Potential]
  Low. This feature is only activated if the field is set.

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

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

[Desktop-packages] [Bug 1373404] Re: [notification] No warning of high volume level

2014-10-20 Thread kevin gunn

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

** Changed in: unity-notifications (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [notification] No warning of high volume level

Status in Sound Menu:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in “indicator-sound” package in Ubuntu:
  In Progress
Status in “pulseaudio” package in Ubuntu:
  Invalid
Status in “ubuntu-system-settings” package in Ubuntu:
  In Progress
Status in “unity-notifications” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released
Status in “indicator-sound” package in Ubuntu RTM:
  Fix Released
Status in “unity-notifications” package in Ubuntu RTM:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  Fix Released

Bug description:
  The EU has a legal requirement for personal music players to prevent hearing 
damage.
  http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009D0490&rid=1
  

  Desired resolution:

  - For RTM the design spec'ed in the following section of the Sound
  wiki page should be implemented
  
https://wiki.ubuntu.com/Sound#Warnings_.28note:_This_section_should_be_implemented_for_RTM.29

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

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

[Desktop-packages] [Bug 812394] Re: Disable hibernate option by default

2014-10-20 Thread TomaszChmielewski

I'm using Samsung Ativ 5 laptop.

Unfortunately suspend to RAM does not work here - the laptop does
suspend, but never wakes up.

On the other hand, suspend to disk works fine - the laptop does suspend
and wakes up correctly.


Leaving a broken suspend to RAM option is a bug in my opinion, especially that 
the only working option of suspending to disk was removed.

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

Title:
  Disable hibernate option by default

Status in Ayatana Design:
  Fix Released
Status in Pantheon Session Indicator:
  Invalid
Status in PolicyKit:
  Invalid
Status in “policykit-desktop-privileges” package in Ubuntu:
  Fix Released
Status in “policykit-desktop-privileges” source package in Precise:
  Fix Released

Bug description:
  
-
  TO RE-ENABLE HIBERNATE: If the hibernate option is supported by your system 
and you need it, you can re-enable it as follows: 
https://help.ubuntu.com/12.04/ubuntu-help/power-hibernate.html

  You may be also interested in subscribing to the bug #882040, which tracks 
the implementation of a configuration tool to toggle hibernate and suspend.
  
-

  I'd like to propose a change in the design of Power preferences in the
  GNOME control center: https://wiki.ubuntu.com/Power

  Instead of going through the "certification" path, we can simply
  disable the options about suspend/hibernate if it's not supported on
  the current hardware (we have API for this in upower).

  I think this solution is more scalable, as we do not need to maintain
  a database with "certified" hardware. Also, we can add a button or a
  informative text when suspend/hibernate doesn't work to guide the
  users about what to do.

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

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

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

Hey Aron, could you look at that?

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

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT

Status in IBus:
  Unknown
Status in “ibus” package in Ubuntu:
  Triaged

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

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

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

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

[Desktop-packages] [Bug 1349871] Re: 3G gets enabled on returning from Flight mode

2014-10-20 Thread Tony Espy

ubuntu-system-settings isn't really involved here, so marking the task
as Invalid.

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  3G gets enabled on returning from Flight mode

Status in “network-manager” package in Ubuntu:
  Confirmed
Status in “ofono” package in Ubuntu:
  Invalid
Status in “ubuntu-system-settings” package in Ubuntu:
  Invalid

Bug description:
  Most probably I have selected the wrong package.

  1. disable 3G
  2. switch to flight mode
  3. switch off flight mode

  What happens:
  3G gets enabled automatically

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubuntu-system-settings 0.3+14.10.20140725.4-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: armhf
  Date: Tue Jul 29 19:08:28 2014
  InstallationDate: Installed on 2014-07-29 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140729-052958)
  SourcePackage: ubuntu-system-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1381484] Re: Fails to connect to irc.slack.com with an SSL error

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

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

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

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

** Changed in: xchat (Ubuntu Utopic)
 Assignee: (unassigned) => Steve Beattie (sbeattie)

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

Title:
  Fails to connect to irc.slack.com with an SSL error

Status in GNOME frontend to the popular xchat IRC client:
  Unknown
Status in “xchat” package in Ubuntu:
  Confirmed
Status in “xchat-gnome” package in Ubuntu:
  Confirmed
Status in “xchat” source package in Precise:
  Confirmed
Status in “xchat-gnome” source package in Precise:
  Confirmed
Status in “xchat” source package in Trusty:
  Confirmed
Status in “xchat-gnome” source package in Trusty:
  Confirmed
Status in “xchat” source package in Utopic:
  Confirmed
Status in “xchat-gnome” source package in Utopic:
  Confirmed

Bug description:
  slack.com is a chat service with optional IRC integration.  Since
  today I can no longer connect to their IRC gateway using XChat-GNOME.
  The error is:

  > * Nepavyko prisijungti. Klaida: (336130315) error:1408F10B:SSL 
routines:SSL3_GET_RECORD:wrong version number
  > Ar tai tikrai SSL šifravimą palaikantis serveris ir prievadas?

  which, translated from lt_LT, means

  > * Cannot connect.  Error: (336130315) error:1408F10B:SSL 
routines:SSL3_GET_RECORD:wrong version number
  > Does the server/port really support SSL?

  I think this is part of the fallout of CVE-2014-3566 (aka POODLE).
  XChat-GNOME is trying to use the insecure SSL protocol version 3, and
  Slack, reasonably enough, rejects that.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xchat-gnome 1:0.30.0~git20131003.d20b8d+really20110821-0.2ubuntu12
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct 15 14:50:57 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-07-25 (811 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: xchat-gnome
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (180 days ago)

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

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

[Desktop-packages] [Bug 1104230] Re: DisplayPort 1.2 MST support is missing in the Intel driver

Hi Vincent,

If I understand correctly your docking station performs the role of a dp
mst hub (can you please confirm this with the documentation of your
docking station or provide its model to verify this online?), so it
should be a good setup to test.

Ideally to make this working you would need 2 things:
1. Patched kernel (I am hoping the one from my ppa is sufficient)
2. MST-aware intel driver (available from the xorg-edgers repository).

Can you please confirm that both conditions are satisfied in your test
case?

Thanks,
Dariusz

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

Title:
  DisplayPort 1.2 MST support is missing in the Intel driver

Status in X.org xf86-video-intel:
  Unknown
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Confirmed

Bug description:
  I have two recent DisplayPort monitors, both supporting the 1.2
  version of the standard and one containing an MST hub (DELL 2913WM).

  I have an Intel Haswell based NUC connected over mini-displayport to
  the display containing the hub, then the second display is plugged in
  that one over DisplayPort.

  DisplayPort 1.2 is enabled on the display containing the hub and the
  second display lights up fine but just works as a clone of the first
  display, without ever showing up in xrandr, dmesg or any other useful
  logs I could find.

  My understanding of MST is that the second display should show up as
  DP2 on my laptop so I can configure it as I would any other display.

  UPDATE: Updated the bug report after it was pointed out that the
  original test hardware, a Lenovo x230 isn't DP 1.2 capable. The same
  test on hardware also fails, due to missing support for MST in the
  driver.

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

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

[Desktop-packages] [Bug 1381484] Re: Fails to connect to servers that disable SSLv3

** Summary changed:

- Fails to connect to irc.slack.com with an SSL error
+ Fails to connect to servers that disable SSLv3

** Description changed:

+ SRU REQUEST:
+ 
+ [Impact]
+ 
+ Xchat-Gnome (and xchat) for the use of SSLv3. Since the Poodle attack on
+ SSLv3, many servers are now disabling the use of SSLv3, making xchat-
+ gnome unsable to connect successfully.
+ 
+ [Test Case]
+ 
+ Install xchat-gnome and connect to an irc server that no longer offers
+ SSLv3.
+ 
+ [Regression Potential]
+ 
+ This update may possibly introduce compatibility issues with sites that
+ don't properly handle TLSv1.2 negotiations. While such sites existed in
+ the past, they aren't likely to be common at the present time.
+ Unfortunately, there is no ultimate solution that would be compatible
+ with both scenarios.
+ 
+ 
+ Original report:
+ 
  slack.com is a chat service with optional IRC integration.  Since today
  I can no longer connect to their IRC gateway using XChat-GNOME.  The
  error is:
  
  > * Nepavyko prisijungti. Klaida: (336130315) error:1408F10B:SSL 
routines:SSL3_GET_RECORD:wrong version number
  > Ar tai tikrai SSL šifravimą palaikantis serveris ir prievadas?
  
  which, translated from lt_LT, means
  
  > * Cannot connect.  Error: (336130315) error:1408F10B:SSL 
routines:SSL3_GET_RECORD:wrong version number
  > Does the server/port really support SSL?
  
  I think this is part of the fallout of CVE-2014-3566 (aka POODLE).
  XChat-GNOME is trying to use the insecure SSL protocol version 3, and
  Slack, reasonably enough, rejects that.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xchat-gnome 1:0.30.0~git20131003.d20b8d+really20110821-0.2ubuntu12
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct 15 14:50:57 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-07-25 (811 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: xchat-gnome
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (180 days ago)

** Changed in: xchat-gnome (Ubuntu Precise)
   Status: Confirmed => In Progress

** Changed in: xchat-gnome (Ubuntu Trusty)
   Status: Confirmed => In Progress

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

Title:
  Fails to connect to servers that disable SSLv3

Status in GNOME frontend to the popular xchat IRC client:
  Unknown
Status in “xchat” package in Ubuntu:
  Confirmed
Status in “xchat-gnome” package in Ubuntu:
  Confirmed
Status in “xchat” source package in Precise:
  Confirmed
Status in “xchat-gnome” source package in Precise:
  In Progress
Status in “xchat” source package in Trusty:
  Confirmed
Status in “xchat-gnome” source package in Trusty:
  In Progress
Status in “xchat” source package in Utopic:
  Confirmed
Status in “xchat-gnome” source package in Utopic:
  Confirmed

Bug description:
  SRU REQUEST:

  [Impact]

  Xchat-Gnome (and xchat) for the use of SSLv3. Since the Poodle attack
  on SSLv3, many servers are now disabling the use of SSLv3, making
  xchat-gnome unsable to connect successfully.

  [Test Case]

  Install xchat-gnome and connect to an irc server that no longer offers
  SSLv3.

  [Regression Potential]

  This update may possibly introduce compatibility issues with sites
  that don't properly handle TLSv1.2 negotiations. While such sites
  existed in the past, they aren't likely to be common at the present
  time. Unfortunately, there is no ultimate solution that would be
  compatible with both scenarios.

  
  Original report:

  slack.com is a chat service with optional IRC integration.  Since
  today I can no longer connect to their IRC gateway using XChat-GNOME.
  The error is:

  > * Nepavyko prisijungti. Klaida: (336130315) error:1408F10B:SSL 
routines:SSL3_GET_RECORD:wrong version number
  > Ar tai tikrai SSL šifravimą palaikantis serveris ir prievadas?

  which, translated from lt_LT, means

  > * Cannot connect.  Error: (336130315) error:1408F10B:SSL 
routines:SSL3_GET_RECORD:wrong version number
  > Does the server/port really support SSL?

  I think this is part of the fallout of CVE-2014-3566 (aka POODLE).
  XChat-GNOME is trying to use the insecure SSL protocol version 3, and
  Slack, reasonably enough, rejects that.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xchat-gnome 1:0.30.0~git20131003.d20b8d+really20110821-0.2ubuntu12
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct 15 14:50:57 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-07-25 (811 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd6

[Desktop-packages] [Bug 1373404] Re: [notification] No warning of high volume level

2014-10-20 Thread kevin gunn

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

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

Title:
  [notification] No warning of high volume level

Status in Sound Menu:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in “indicator-sound” package in Ubuntu:
  In Progress
Status in “pulseaudio” package in Ubuntu:
  Invalid
Status in “ubuntu-system-settings” package in Ubuntu:
  In Progress
Status in “unity-notifications” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  In Progress
Status in “indicator-sound” package in Ubuntu RTM:
  Fix Released
Status in “unity-notifications” package in Ubuntu RTM:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  Fix Released

Bug description:
  The EU has a legal requirement for personal music players to prevent hearing 
damage.
  http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009D0490&rid=1
  

  Desired resolution:

  - For RTM the design spec'ed in the following section of the Sound
  wiki page should be implemented
  
https://wiki.ubuntu.com/Sound#Warnings_.28note:_This_section_should_be_implemented_for_RTM.29

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

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

[Desktop-packages] [Bug 1381484] Re: Fails to connect to servers that disable SSLv3

** Branch linked: lp:ubuntu/utopic-proposed/xchat-gnome

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

Title:
  Fails to connect to servers that disable SSLv3

Status in GNOME frontend to the popular xchat IRC client:
  Unknown
Status in “xchat” package in Ubuntu:
  Confirmed
Status in “xchat-gnome” package in Ubuntu:
  Confirmed
Status in “xchat” source package in Precise:
  Confirmed
Status in “xchat-gnome” source package in Precise:
  In Progress
Status in “xchat” source package in Trusty:
  Confirmed
Status in “xchat-gnome” source package in Trusty:
  In Progress
Status in “xchat” source package in Utopic:
  Confirmed
Status in “xchat-gnome” source package in Utopic:
  Confirmed

Bug description:
  SRU REQUEST:

  [Impact]

  Xchat-Gnome (and xchat) for the use of SSLv3. Since the Poodle attack
  on SSLv3, many servers are now disabling the use of SSLv3, making
  xchat-gnome unsable to connect successfully.

  [Test Case]

  Install xchat-gnome and connect to an irc server that no longer offers
  SSLv3.

  [Regression Potential]

  This update may possibly introduce compatibility issues with sites
  that don't properly handle TLSv1.2 negotiations. While such sites
  existed in the past, they aren't likely to be common at the present
  time. Unfortunately, there is no ultimate solution that would be
  compatible with both scenarios.

  
  Original report:

  slack.com is a chat service with optional IRC integration.  Since
  today I can no longer connect to their IRC gateway using XChat-GNOME.
  The error is:

  > * Nepavyko prisijungti. Klaida: (336130315) error:1408F10B:SSL 
routines:SSL3_GET_RECORD:wrong version number
  > Ar tai tikrai SSL šifravimą palaikantis serveris ir prievadas?

  which, translated from lt_LT, means

  > * Cannot connect.  Error: (336130315) error:1408F10B:SSL 
routines:SSL3_GET_RECORD:wrong version number
  > Does the server/port really support SSL?

  I think this is part of the fallout of CVE-2014-3566 (aka POODLE).
  XChat-GNOME is trying to use the insecure SSL protocol version 3, and
  Slack, reasonably enough, rejects that.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xchat-gnome 1:0.30.0~git20131003.d20b8d+really20110821-0.2ubuntu12
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct 15 14:50:57 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-07-25 (811 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: xchat-gnome
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (180 days ago)

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

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

[Desktop-packages] [Bug 1104230] Re: DisplayPort 1.2 MST support is missing in the Intel driver

Hi Elvis,

Looks like you have the perfect setup to test this case.

Please make sure you have ppa-purge installed so you can revert the
package updates if anything goes wrong.

Please follow these steps:
1. sudo add-apt-repository -y ppa:dgadomski/linux-mst
2. sudo add-apt-repository -y ppa:xorg-edgers/ppa
3. sudo apt-get update
Make sure that the output of:
4. apt-cache policy linux-image-3.16.0-19-generic
states
Candidate: 3.16.0-19.26~14.04hf71858v20141008b1
5. sudo apt-get install linux-image-3.16.0-19-generic
6. reboot to use the new kernel
7. sudo apt-get install  xserver-xorg-video-intel 
8. reboot to use the new intel driver

Assuming that you are connected to Monitor #1 and it is daisy-chained to
Monitor #2 you should see 2 monitors available in the Ubuntu display
settings panel.

I would appreciate your feedback.

Thanks,
Dariusz

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

Title:
  DisplayPort 1.2 MST support is missing in the Intel driver

Status in X.org xf86-video-intel:
  Unknown
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Confirmed

Bug description:
  I have two recent DisplayPort monitors, both supporting the 1.2
  version of the standard and one containing an MST hub (DELL 2913WM).

  I have an Intel Haswell based NUC connected over mini-displayport to
  the display containing the hub, then the second display is plugged in
  that one over DisplayPort.

  DisplayPort 1.2 is enabled on the display containing the hub and the
  second display lights up fine but just works as a clone of the first
  display, without ever showing up in xrandr, dmesg or any other useful
  logs I could find.

  My understanding of MST is that the second display should show up as
  DP2 on my laptop so I can configure it as I would any other display.

  UPDATE: Updated the bug report after it was pointed out that the
  original test hardware, a Lenovo x230 isn't DP 1.2 capable. The same
  test on hardware also fails, due to missing support for MST in the
  driver.

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

-- 
Mailing list: https://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 1104230] Re: DisplayPort 1.2 MST support is missing in the Intel driver

2014-10-20 Thread Vincent Gerris

Hi Dariusz,

I think I have this part:
Manufacturer Part# : XX6F0 | Dell Part# : 331-6307
I am not sure if that is a DP hub, it is beyond my knowledge.
I used your kernel and the xserver-xorg-video intel driver from  URI was:
http://ppa.launchpad.net/pool/main/x/xserver-xorg-video-intel/xserver-xorg-video-intel_2.99.916+git20141016.6b98f162-0ubuntu0sarvatt~trusty_amd64.changelog
How does the xorg-edgers repo provide a driver?
I don't see it, while the repo is enabled.
When I had a fully working situation the last time, I did not see any
xserver-xorg-video-intel driver installed.
Is it another driver or package you are referring to?

Kind regards,
Vincent

On Mon, Oct 20, 2014 at 4:48 PM, Dariusz Gadomski <
1104...@bugs.launchpad.net> wrote:

> Hi Vincent,
>
> If I understand correctly your docking station performs the role of a dp
> mst hub (can you please confirm this with the documentation of your
> docking station or provide its model to verify this online?), so it
> should be a good setup to test.
>
> Ideally to make this working you would need 2 things:
> 1. Patched kernel (I am hoping the one from my ppa is sufficient)
> 2. MST-aware intel driver (available from the xorg-edgers repository).
>
> Can you please confirm that both conditions are satisfied in your test
> case?
>
> Thanks,
> Dariusz
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1104230
>
> Title:
>   DisplayPort 1.2 MST support is missing in the Intel driver
>
> Status in X.org xf86-video-intel:
>   Unknown
> Status in “xserver-xorg-video-intel” package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I have two recent DisplayPort monitors, both supporting the 1.2
>   version of the standard and one containing an MST hub (DELL 2913WM).
>
>   I have an Intel Haswell based NUC connected over mini-displayport to
>   the display containing the hub, then the second display is plugged in
>   that one over DisplayPort.
>
>   DisplayPort 1.2 is enabled on the display containing the hub and the
>   second display lights up fine but just works as a clone of the first
>   display, without ever showing up in xrandr, dmesg or any other useful
>   logs I could find.
>
>   My understanding of MST is that the second display should show up as
>   DP2 on my laptop so I can configure it as I would any other display.
>
>   UPDATE: Updated the bug report after it was pointed out that the
>   original test hardware, a Lenovo x230 isn't DP 1.2 capable. The same
>   test on hardware also fails, due to missing support for MST in the
>   driver.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1104230/+subscriptions
>

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

Title:
  DisplayPort 1.2 MST support is missing in the Intel driver

Status in X.org xf86-video-intel:
  Unknown
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Confirmed

Bug description:
  I have two recent DisplayPort monitors, both supporting the 1.2
  version of the standard and one containing an MST hub (DELL 2913WM).

  I have an Intel Haswell based NUC connected over mini-displayport to
  the display containing the hub, then the second display is plugged in
  that one over DisplayPort.

  DisplayPort 1.2 is enabled on the display containing the hub and the
  second display lights up fine but just works as a clone of the first
  display, without ever showing up in xrandr, dmesg or any other useful
  logs I could find.

  My understanding of MST is that the second display should show up as
  DP2 on my laptop so I can configure it as I would any other display.

  UPDATE: Updated the bug report after it was pointed out that the
  original test hardware, a Lenovo x230 isn't DP 1.2 capable. The same
  test on hardware also fails, due to missing support for MST in the
  driver.

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

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

[Desktop-packages] [Bug 1243806] Re: The names column has its width dictated by other columns

** Branch linked: lp:ubuntu/utopic-proposed/nautilus

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

Title:
  The names column has its width dictated by other columns

Status in Nautilus:
  Fix Released
Status in “nautilus” package in Ubuntu:
  Fix Committed
Status in “nautilus” source package in Trusty:
  Triaged

Bug description:
  Folder names in Location area keeps the width even though when I go back to 
upper folder.
  First of all this new downgraded nautilus folder section holds its width and 
I cannot even change the width at all.
  Then when I go deep down lower folders or open folder with long name, it 
would squeeze down the "Name" part and I cannot even see names anymore. Then 
when I go up to upper folder or root, I cannot see the names anymore becaue 
location column takes up all the space. Once I click one of the unseen folder, 
I may see the names again. 
  This is one of too many problems of 13.10.

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

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

[Desktop-packages] [Bug 1381484] Re: Fails to connect to servers that disable SSLv3

2014-10-20 Thread Bug Watch Updater

** Changed in: xchat-gnome
   Status: Unknown => New

** Changed in: xchat-gnome
   Importance: Unknown => Medium

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

Title:
  Fails to connect to servers that disable SSLv3

Status in GNOME frontend to the popular xchat IRC client:
  New
Status in “xchat” package in Ubuntu:
  Confirmed
Status in “xchat-gnome” package in Ubuntu:
  Fix Released
Status in “xchat” source package in Precise:
  Confirmed
Status in “xchat-gnome” source package in Precise:
  In Progress
Status in “xchat” source package in Trusty:
  Confirmed
Status in “xchat-gnome” source package in Trusty:
  In Progress
Status in “xchat” source package in Utopic:
  Confirmed
Status in “xchat-gnome” source package in Utopic:
  Fix Released
Status in “xchat-gnome” package in Debian:
  Unknown

Bug description:
  SRU REQUEST:

  [Impact]

  Xchat-Gnome (and xchat) for the use of SSLv3. Since the Poodle attack
  on SSLv3, many servers are now disabling the use of SSLv3, making
  xchat-gnome unsable to connect successfully.

  [Test Case]

  Install xchat-gnome and connect to an irc server that no longer offers
  SSLv3.

  [Regression Potential]

  This update may possibly introduce compatibility issues with sites
  that don't properly handle TLSv1.2 negotiations. While such sites
  existed in the past, they aren't likely to be common at the present
  time. Unfortunately, there is no ultimate solution that would be
  compatible with both scenarios.

  
  Original report:

  slack.com is a chat service with optional IRC integration.  Since
  today I can no longer connect to their IRC gateway using XChat-GNOME.
  The error is:

  > * Nepavyko prisijungti. Klaida: (336130315) error:1408F10B:SSL 
routines:SSL3_GET_RECORD:wrong version number
  > Ar tai tikrai SSL šifravimą palaikantis serveris ir prievadas?

  which, translated from lt_LT, means

  > * Cannot connect.  Error: (336130315) error:1408F10B:SSL 
routines:SSL3_GET_RECORD:wrong version number
  > Does the server/port really support SSL?

  I think this is part of the fallout of CVE-2014-3566 (aka POODLE).
  XChat-GNOME is trying to use the insecure SSL protocol version 3, and
  Slack, reasonably enough, rejects that.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xchat-gnome 1:0.30.0~git20131003.d20b8d+really20110821-0.2ubuntu12
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct 15 14:50:57 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-07-25 (811 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: xchat-gnome
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (180 days ago)

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

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

[Desktop-packages] [Bug 1381484] Re: Fails to connect to servers that disable SSLv3

** Bug watch added: Debian Bug tracker #766065
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766065

** Also affects: xchat-gnome (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766065
   Importance: Unknown
   Status: Unknown

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

Title:
  Fails to connect to servers that disable SSLv3

Status in GNOME frontend to the popular xchat IRC client:
  New
Status in “xchat” package in Ubuntu:
  Confirmed
Status in “xchat-gnome” package in Ubuntu:
  Fix Released
Status in “xchat” source package in Precise:
  Confirmed
Status in “xchat-gnome” source package in Precise:
  In Progress
Status in “xchat” source package in Trusty:
  Confirmed
Status in “xchat-gnome” source package in Trusty:
  In Progress
Status in “xchat” source package in Utopic:
  Confirmed
Status in “xchat-gnome” source package in Utopic:
  Fix Released
Status in “xchat-gnome” package in Debian:
  Unknown

Bug description:
  SRU REQUEST:

  [Impact]

  Xchat-Gnome (and xchat) for the use of SSLv3. Since the Poodle attack
  on SSLv3, many servers are now disabling the use of SSLv3, making
  xchat-gnome unsable to connect successfully.

  [Test Case]

  Install xchat-gnome and connect to an irc server that no longer offers
  SSLv3.

  [Regression Potential]

  This update may possibly introduce compatibility issues with sites
  that don't properly handle TLSv1.2 negotiations. While such sites
  existed in the past, they aren't likely to be common at the present
  time. Unfortunately, there is no ultimate solution that would be
  compatible with both scenarios.

  
  Original report:

  slack.com is a chat service with optional IRC integration.  Since
  today I can no longer connect to their IRC gateway using XChat-GNOME.
  The error is:

  > * Nepavyko prisijungti. Klaida: (336130315) error:1408F10B:SSL 
routines:SSL3_GET_RECORD:wrong version number
  > Ar tai tikrai SSL šifravimą palaikantis serveris ir prievadas?

  which, translated from lt_LT, means

  > * Cannot connect.  Error: (336130315) error:1408F10B:SSL 
routines:SSL3_GET_RECORD:wrong version number
  > Does the server/port really support SSL?

  I think this is part of the fallout of CVE-2014-3566 (aka POODLE).
  XChat-GNOME is trying to use the insecure SSL protocol version 3, and
  Slack, reasonably enough, rejects that.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xchat-gnome 1:0.30.0~git20131003.d20b8d+really20110821-0.2ubuntu12
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct 15 14:50:57 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-07-25 (811 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: xchat-gnome
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (180 days ago)

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

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

[Desktop-packages] [Bug 1381484] Re: Fails to connect to servers that disable SSLv3

This bug was fixed in the package xchat-gnome -
1:0.30.0~git20131003.d20b8d+really20110821-0.2ubuntu14

---
xchat-gnome (1:0.30.0~git20131003.d20b8d+really20110821-0.2ubuntu14) utopic; 
urgency=medium

  * Don't force the use of SSLv3 (LP: #1381484)
- debian/patches/dont_force_sslv3.patch: use SSLv23_client_method() so
  the best method gets automatically negotiated in src/common/ssl.c.
 -- Marc DeslauriersMon, 20 Oct 2014 10:14:47 
-0400

** Changed in: xchat-gnome (Ubuntu Utopic)
   Status: Confirmed => Fix Released

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

Title:
  Fails to connect to servers that disable SSLv3

Status in GNOME frontend to the popular xchat IRC client:
  New
Status in “xchat” package in Ubuntu:
  Confirmed
Status in “xchat-gnome” package in Ubuntu:
  Fix Released
Status in “xchat” source package in Precise:
  Confirmed
Status in “xchat-gnome” source package in Precise:
  In Progress
Status in “xchat” source package in Trusty:
  Confirmed
Status in “xchat-gnome” source package in Trusty:
  In Progress
Status in “xchat” source package in Utopic:
  Confirmed
Status in “xchat-gnome” source package in Utopic:
  Fix Released
Status in “xchat-gnome” package in Debian:
  Unknown

Bug description:
  SRU REQUEST:

  [Impact]

  Xchat-Gnome (and xchat) for the use of SSLv3. Since the Poodle attack
  on SSLv3, many servers are now disabling the use of SSLv3, making
  xchat-gnome unsable to connect successfully.

  [Test Case]

  Install xchat-gnome and connect to an irc server that no longer offers
  SSLv3.

  [Regression Potential]

  This update may possibly introduce compatibility issues with sites
  that don't properly handle TLSv1.2 negotiations. While such sites
  existed in the past, they aren't likely to be common at the present
  time. Unfortunately, there is no ultimate solution that would be
  compatible with both scenarios.

  
  Original report:

  slack.com is a chat service with optional IRC integration.  Since
  today I can no longer connect to their IRC gateway using XChat-GNOME.
  The error is:

  > * Nepavyko prisijungti. Klaida: (336130315) error:1408F10B:SSL 
routines:SSL3_GET_RECORD:wrong version number
  > Ar tai tikrai SSL šifravimą palaikantis serveris ir prievadas?

  which, translated from lt_LT, means

  > * Cannot connect.  Error: (336130315) error:1408F10B:SSL 
routines:SSL3_GET_RECORD:wrong version number
  > Does the server/port really support SSL?

  I think this is part of the fallout of CVE-2014-3566 (aka POODLE).
  XChat-GNOME is trying to use the insecure SSL protocol version 3, and
  Slack, reasonably enough, rejects that.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xchat-gnome 1:0.30.0~git20131003.d20b8d+really20110821-0.2ubuntu12
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct 15 14:50:57 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-07-25 (811 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: xchat-gnome
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (180 days ago)

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

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

[Desktop-packages] [Bug 812394] Re: Disable hibernate option by default

2014-10-20 Thread Bob Bib

2014-10-20 from TomaszChmielewski:
> I'm using Samsung Ativ 5 laptop.
> ...
> Leaving a broken suspend to RAM option is a bug in my opinion,
> especially that the only working option of suspending to disk was removed.

1) Please report a new bug about the suspend-to-RAM problem on your system: 
https://wiki.ubuntu.com/DebuggingKernelSuspend
2) Regarding the hibernation feature, please check the bug #882040; meanwhile, 
probably you can still use the "sudo pm-hibernate" from console.

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

Title:
  Disable hibernate option by default

Status in Ayatana Design:
  Fix Released
Status in Pantheon Session Indicator:
  Invalid
Status in PolicyKit:
  Invalid
Status in “policykit-desktop-privileges” package in Ubuntu:
  Fix Released
Status in “policykit-desktop-privileges” source package in Precise:
  Fix Released

Bug description:
  
-
  TO RE-ENABLE HIBERNATE: If the hibernate option is supported by your system 
and you need it, you can re-enable it as follows: 
https://help.ubuntu.com/12.04/ubuntu-help/power-hibernate.html

  You may be also interested in subscribing to the bug #882040, which tracks 
the implementation of a configuration tool to toggle hibernate and suspend.
  
-

  I'd like to propose a change in the design of Power preferences in the
  GNOME control center: https://wiki.ubuntu.com/Power

  Instead of going through the "certification" path, we can simply
  disable the options about suspend/hibernate if it's not supported on
  the current hardware (we have API for this in upower).

  I think this solution is more scalable, as we do not need to maintain
  a database with "certified" hardware. Also, we can add a button or a
  informative text when suspend/hibernate doesn't work to guide the
  users about what to do.

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

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

[Desktop-packages] [Bug 1104230] Re: DisplayPort 1.2 MST support is missing in the Intel driver

VIncent, according to [1] this hardware is displayport 1.2 compatible.
"Plus, the Display Port 1.2 adds the ability to daisy chain displays (4 
displays via 1 connector)."

However, I have not been able to determine whether this works in such a
way that it takes MST output from your laptop's displayport and
distributes it via vga and dvi ports.

Do you remember what feature have you been cherry picking to your
patched kernel? Maybe you were using another feature.

The perfect setup to test this feature is the one Elvishas - daisy
chained Dell monitors.

Regarding your question on the xorg-edgers driver: can you please try
sudo add-apt-repository -y ppa:xorg-edgers/ppa
sudo apt-get update
apt-cache policy xserver-xorg-video-intel

Please provide the output of the last command. Thanks.

[1]
http://accessories.us.dell.com/sna/productdetail.aspx?c=us&l=en&s=gen&sku=331-6307

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

Title:
  DisplayPort 1.2 MST support is missing in the Intel driver

Status in X.org xf86-video-intel:
  Unknown
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Confirmed

Bug description:
  I have two recent DisplayPort monitors, both supporting the 1.2
  version of the standard and one containing an MST hub (DELL 2913WM).

  I have an Intel Haswell based NUC connected over mini-displayport to
  the display containing the hub, then the second display is plugged in
  that one over DisplayPort.

  DisplayPort 1.2 is enabled on the display containing the hub and the
  second display lights up fine but just works as a clone of the first
  display, without ever showing up in xrandr, dmesg or any other useful
  logs I could find.

  My understanding of MST is that the second display should show up as
  DP2 on my laptop so I can configure it as I would any other display.

  UPDATE: Updated the bug report after it was pointed out that the
  original test hardware, a Lenovo x230 isn't DP 1.2 capable. The same
  test on hardware also fails, due to missing support for MST in the
  driver.

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

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

[Desktop-packages] [Bug 1383349] [NEW] $ ubuntu-bug xorg

2014-10-20 Thread magitadi

Public bug reported:

$ ubuntu-bug xorg

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-38.65-lowlatency 3.13.11.8
Uname: Linux 3.13.0-38-lowlatency i686
.tmp.unity.support.test.1:
 
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Oct 20 18:33:48 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GK208 [GeForce GT 630 Rev. 2] [10de:1284] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:8461]
InstallationDate: Installed on 2014-10-18 (2 days ago)
InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.1)
LightdmGreeterLog:
 ** (lightdm-gtk-greeter:6094): WARNING **: Failed to load user image: Failed 
to open file '/home/magita/.face': No such file or directory
 
 (lightdm-gtk-greeter:6094): Gdk-WARNING **: lightdm-gtk-greeter: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
LightdmGreeterLogOld:
 ** (lightdm-gtk-greeter:5814): WARNING **: Failed to load user image: Failed 
to open file '/home/magita/.face': No such file or directory
 g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
MachineType: HP-Pavilion GJ434AA-B1A a6140.gr
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-38-lowlatency 
root=UUID=bf40b7c3-5d35-4cf4-97a2-37d942f122e5 ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/07/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.20
dmi.board.name: Leonite2
dmi.board.vendor: ASUSTek Computer INC.
dmi.board.version: 6.00
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: 
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.20:bd06/07/2007:svnHP-Pavilion:pnGJ434AA-B1Aa6140.gr:pvr:rvnASUSTekComputerINC.:rnLeonite2:rvr6.00:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: GJ434AA-B1A a6140.gr
dmi.sys.vendor: HP-Pavilion
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
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.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Oct 20 14:10:53 2014
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputLogitech USB Receiver MOUSE, id 8
 inputLogitech USB Receiver KEYBOARD, id 9
 inputLogitech Unifying Device. Wireless PID:4004 KEYBOARD, id 10
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(0): Error creating GPU channel: -19
 NOUVEAU(0): Error initialising acceleration.  Falling back to NoAccel
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2.1
xserver.video_driver: nouveau

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


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

Title:
  $ ubuntu-bug xorg

Status in “xorg” package in Ubuntu:
  New

Bug description:
  $ ubuntu-bug xorg

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-38.65-lowlatency 3.13.11.8
  Uname: Linux 3.13.0-38-lowlatency i686
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Oct 20 18:33:48 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK208 [GeForce GT 630 Rev. 2] [10de:1284] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8461]
  InstallationDate: Installed on 2014-10-18 (2 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.1)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:6094): WARNING **: Failed to load user image: Failed 
to open file '/home/ma

[Desktop-packages] [Bug 512220] Re: cupsd crash "Closing on unknown HTTP state 0"

2014-10-20 Thread Bryan Quigley

Has anyone upgraded to 14.04 yet?   If so, do you still see this issue?

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

Title:
  cupsd crash "Closing on unknown HTTP state 0"

Status in “cups” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: cups

  I often get trouble with cupsd crashing and Apport saying the
  following:

  The problem cannot be reported:
  The program crashed on an assertion failure, but the message could not be 
retrieved. Apport does not support reporting these crashes.

  I think the crash is due to my having a saved Firefox session with
  Cups' administration window (http://localhost:631/admin) in it. The
  crash seems to occur when this session is restored as part of the
  session restore when I log in to my desktop environment.

  I have turned on debug-logging and can see the following:
  D [25/Jan/2010:08:57:16 +0100] cupsdReadClient: 11 GET /images/cups-icon.png 
HTTP/1.1
  D [25/Jan/2010:08:57:16 +0100] cupsdSetBusyState: Active clients
  D [25/Jan/2010:08:57:16 +0100] cupsdAuthorize: No authentication data 
provided.
  D [25/Jan/2010:08:57:16 +0100] cupsdReadClient: 11 Closing on EOF
  D [25/Jan/2010:08:57:16 +0100] cupsdCloseClient: 11
  D [25/Jan/2010:08:57:16 +0100] cupsdSetBusyState: Not busy
  D [25/Jan/2010:08:57:16 +0100] cupsdWriteClient: 1354538648 Closing on 
unknown HTTP state 0
  D [25/Jan/2010:08:57:16 +0100] cupsdCloseClient: 1354538648

  How to reproduce:
  0) Make sure you have session restore activated. Make sure your favorite 
browser is set to restore the last session on reload.
  1) Load http://localhost:631/admin in your favorite browser.
  2) Restart your computer.
  3) Log in to your desktop environment.

  Expected result: The CUPS administration window should be loaded in your 
browser.
  Actual result: The CUPS administration window fails to load. The browser 
says: "The connection to the server was reset while the page was loading."

  It is not consistently reproducible, but I would say I see a failure
  rate of 80 %. It happens on both of my test machines.

  ProblemType: Bug
  Architecture: amd64
  Date: Mon Jan 25 09:00:30 2010
  DistroRelease: Ubuntu 10.04
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: LG Electronics P300-T.APE4V
  NonfreeKernelModules: nvidia
  Package: cups 1.4.2-6
  Papersize: letter
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-11-generic 
root=UUID=01ebab7a-379c-48c8-87d6-a2800f6dccfd ro quiet splash
  ProcVersionSignature: Ubuntu 2.6.32-11.15-generic
  SourcePackage: cups
  Uname: Linux 2.6.32-11-generic x86_64
  dmi.bios.date: 06/30/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: ELGNSF18
  dmi.board.name: ELGON
  dmi.board.vendor: LG Electronics
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LG Electronics
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrELGNSF18:bd06/30/2008:svnLGElectronics:pnP300-T.APE4V:pvrNotApplicable:rvnLGElectronics:rnELGON:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A:
  dmi.product.name: P300-T.APE4V
  dmi.product.version: Not Applicable
  dmi.sys.vendor: LG Electronics

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

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

[Desktop-packages] [Bug 1383355] [NEW] mouse right click responsiveness only after button being held down for 5-10 seconds

2014-10-20 Thread Robert Bullard

Public bug reported:

My Ubuntu terminal session returns command lsb_release -a as:
root@BobbyB-LinuxLaptop:/home/bobbyb# lsb_release -a
LSB Version:
core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch:core-4.0-ia32:core-4.0-noarch

Distributor ID: Ubuntu
Description:Ubuntu 12.04.5 LTS
Release:12.04
Codename: precise

I have the unity-2d-shell running and the attached .png image file is
from my desktop_window Nautilus. The only other 'application" that I
have started is "Screenshot" to take the .png image to reference what I
am reporting as the issue.

As a reference the .png image I took using the application Screenshot
after hoklding the right click mouse button down for about 10 seconds
more or less (Screenshot 2014-10-20 09:49:07
TenSecondHoldMouseRightClickButton.png).

The problem is that if I right click the mouse while the pointer is over
anything on my desktop (e.g., a file, a folder, an image, etc etc etc)
and this right click is just a simple one time single right mouse button
click done just once, the drop down contextual menu (such as shown in
the .png image) does not appear/drop down. I have to hold the right
click mouse button down for an extended period of time (sometimes it is
a few seconds, sometimes 10seconds, sometimes a bit longer) and then the
drop down menu appears. This is the problemfailure to respond to a
single simple right mouse click without my having to hold the button
down for an extended period of time.

This same type of thing happens when I am in my browser (e.g., Chromium
or Firefox. I do a GOOGLE Search for example and the response comes
back showing a list of web page possibilities and I put the mouse
pointer over the link I want to open and right click the mouse once,
nothing happens. I right click the mouse once again (or once again or
again or again etc etc etc) waiting seconds between any subsequent right
mouse button pressing and nothing happens. If, however, I position the
mouse pointer over the web page link and I right click the mouse and
hold the right click button down for a few seconds (maybe as long as ten
seconds sometimes more or less) then the web link is activated as I had
initially expected that it should. This delay in responding to the
right click is annoying and was not there a week ago but is there
consistently now. How do I change the mouse responsiveness or better
yet, why has it changed to behave like it does?

I have had this problem many many months ago off and on and on different
loads in 12.04LTS. Not sure if it does or does not occur on any
previous releases or in 13.10 or 14.04. It would occur for weeks on end
and then I would not see it again and mouse right click goes back to
working 'normally'. I cannot say I did anything to change the mouse
right click behaviour. But, now it is back again. It seems to be
elusive in when it will/may occur and I cannot say for certain that it
is in relation to anything else I am doing or any other application I
have activated or using or that it is related to any specific mouse
activities or sequence of actions. I have not changed/adjusted any
parameters related to mouse responsiveness and know of nothing available
that I may use to query mouse responsiveness or reset/change the mouse
right click responsiveness.

I am using and have more than always used a USB optical Microsoft 3
button wheel mouse. I am right handed. I don't think the mouse
type/manufacture or whether it is right or left handed is significant to
the problem. I get no logs or anything indicating that there is a
problem with messaging or any problem with the system or the USB
hardware or the mouse itself.

I know that once it starts occurring then it happens all the time for a
period of sometime then, magically, it seems to clear itself up
reverting back to a one click mouse right click responding immediately
as expected. Sometimes it reverts back only after days/weeks of
computer use. I have restarted my system many times with nothing
changing. I have used different USB ports for the mouse and it still
happens. I have tried different types/makes/models/manufacturers of
mouse(s) (mice??) and it happens. It happened when I had 12.04:LTS
Linux 3.2.0-67-generic or even with this latest updated kernel load that
was downloaded/applied just a week or so ago as a regular update offered
by Ubuntu software services (e.g., Linux 3.2.0-70-generic). I have
never done any changes to change/reset any configuration files or
settings files so I cannot see why the responsiveness to the right click
button on the mouse has changed and is now behaving as it is.

As I said in the above text this has happened before. It started out of
the blue as far as I can tell, the same thing with the mouse right click
not being responded to, then it didn't happen for a while and a single
non-held right click of the mouse worked as expected, then it

[Desktop-packages] [Bug 428500] Re: Gnome Power Manager does not detect battery

2014-10-20 Thread Paolo Poli

I have the exact same problem on my Dell.

I won't describe what happens on my pc again because it's just like
"Hari Kotcherlakota" described in his comment #8

- Dell Inspiron 14" 7437
- Running Kubuntu 14.04.1 LTS AMD64
- Linux Inspiron-7437 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 
2014 x86_64 x86_64 x86_64 GNU/Linux
- All updates installed

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

Title:
  Gnome Power Manager does not detect battery

Status in “gnome-power-manager” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gnome-power-manager

  After removing and re-inserting the battery gpm's notification icon
  did not return. After enabling the icon to be always visible (instead
  of only when battery present) the icon provides no information on my
  battery and seems to think I'm just running off AC all the time (even
  when running on battery).

  If I go to "Power History" from the context menu, the battery is
  visible with the correct State. The state is also updated as I
  plug/unplug AC.

  Killing and running a new gnome-power-manager provides battery info
  again.

  ProblemType: Bug
  Architecture: amd64
  Date: Sat Sep 12 12:58:56 2009
  DistroRelease: Ubuntu 9.10
  Package: gnome-power-manager 2.27.92-0ubuntu1
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_CA.UTF-8
  ProcVersionSignature: Ubuntu 2.6.31-10.32-generic
  SourcePackage: gnome-power-manager
  Uname: Linux 2.6.31-10-generic x86_64

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

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

[Desktop-packages] [Bug 1383363] [NEW] Impossible to enable networking after wake-up the laptop from suspension

2014-10-20 Thread Eduardo

Public bug reported:

After suspending my laptop and wake it up, I am not able to connect to
any network (neither ethernet nor wifi). I must reboot my system to
enable networking.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: network-manager 0.9.8.8-0ubuntu7
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Oct 20 17:52:36 2014
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2014-10-05 (15 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
IpRoute:
 default via 10.26.210.1 dev eth0  proto static 
 10.26.210.0/24 dev eth0  proto kernel  scope link  src 10.26.210.115  metric 1
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAME  UUID   TYPE  
TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
 Wired connection 12cbca619-a37c-4cb3-ae5a-80349b04047b   
802-3-ethernet1413820269   Po 20. říjen 2014, 17:51:09 CEST   yes   
no /org/freedesktop/NetworkManager/Settings/1
 MyWifi0ce63e67-720d-4e44-9134-2ba0bb97cb33   
802-11-wireless   1413738709   Ne 19. říjen 2014, 19:11:49 CEST   yes   
no /org/freedesktop/NetworkManager/Settings/0
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   
 wlan0  802-11-wireless   disconnected  
/org/freedesktop/NetworkManager/Devices/1  
 eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   WIFI  
 WWAN-HARDWARE   WWAN  
 running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

** Affects: network-manager (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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1383363

Title:
  Impossible to enable networking after wake-up the laptop from
  suspension

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

Bug description:
  After suspending my laptop and wake it up, I am not able to connect to
  any network (neither ethernet nor wifi). I must reboot my system to
  enable networking.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 20 17:52:36 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-10-05 (15 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IpRoute:
   default via 10.26.210.1 dev eth0  proto static 
   10.26.210.0/24 dev eth0  proto kernel  scope link  src 10.26.210.115  metric 
1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Wired connection 12cbca619-a37c-4cb3-ae5a-80349b04047b   
802-3-ethernet1413820269   Po 20. říjen 2014, 17:51:09 CEST   yes   
no /org/freedesktop/NetworkManager/Settings/1
   MyWifi0ce63e67-720d-4e44-9134-2ba0bb97cb33   
802-11-wireless   1413738709   Ne 19. říjen 2014, 19:11:49 CEST   yes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   disconnected  
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

[Desktop-packages] [Bug 1382915] Re: problems

2014-10-20 Thread Seth Arnold

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  problems

Status in “xorg” package in Ubuntu:
  New

Bug description:
  recover by getting driver

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Oct 19 11:48:23 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   ndiswrapper, 1.59, 3.13.0-35-generic, i686: installed
   ndiswrapper, 1.59, 3.13.0-36-generic, i686: installed
   ndiswrapper, 1.59, 3.13.0-37-generic, i686: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 82G33/G31 Express Integrated Graphics Controller 
[8086:29c2] (rev 10) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. P5KPL-VM Motherboard [1043:82b0]
  InstallationDate: Installed on 2014-08-26 (53 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=dfd9b7a6-34ec-489b-850e-5c2b24819e0a ro rootflags=sync drm.debug=0xe 
plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/03/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0502
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5KPL-AM/PS
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0502:bd03/03/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-AM/PS:rvrx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  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.1
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sun Oct 19 07:29:07 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputMicrosoft Basic Optical Mouse MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id2216 
   vendor SAM
  xserver.version: 2:1.15.1-0ubuntu2.1

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

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

[Desktop-packages] [Bug 1381484] Re: Fails to connect to servers that disable SSLv3

** Changed in: xchat (Ubuntu Precise)
   Status: Confirmed => In Progress

** Changed in: xchat (Ubuntu Precise)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

** Changed in: xchat (Ubuntu Trusty)
   Status: Confirmed => In Progress

** Changed in: xchat (Ubuntu Trusty)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

** Changed in: xchat (Ubuntu Utopic)
   Status: Confirmed => Fix Committed

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

Title:
  Fails to connect to servers that disable SSLv3

Status in GNOME frontend to the popular xchat IRC client:
  New
Status in “xchat” package in Ubuntu:
  Fix Committed
Status in “xchat-gnome” package in Ubuntu:
  Fix Released
Status in “xchat” source package in Precise:
  In Progress
Status in “xchat-gnome” source package in Precise:
  In Progress
Status in “xchat” source package in Trusty:
  In Progress
Status in “xchat-gnome” source package in Trusty:
  In Progress
Status in “xchat” source package in Utopic:
  Fix Committed
Status in “xchat-gnome” source package in Utopic:
  Fix Released
Status in “xchat-gnome” package in Debian:
  Unknown

Bug description:
  SRU REQUEST:

  [Impact]

  Xchat-Gnome (and xchat) for the use of SSLv3. Since the Poodle attack
  on SSLv3, many servers are now disabling the use of SSLv3, making
  xchat-gnome unsable to connect successfully.

  [Test Case]

  Install xchat-gnome and connect to an irc server that no longer offers
  SSLv3.

  [Regression Potential]

  This update may possibly introduce compatibility issues with sites
  that don't properly handle TLSv1.2 negotiations. While such sites
  existed in the past, they aren't likely to be common at the present
  time. Unfortunately, there is no ultimate solution that would be
  compatible with both scenarios.

  
  Original report:

  slack.com is a chat service with optional IRC integration.  Since
  today I can no longer connect to their IRC gateway using XChat-GNOME.
  The error is:

  > * Nepavyko prisijungti. Klaida: (336130315) error:1408F10B:SSL 
routines:SSL3_GET_RECORD:wrong version number
  > Ar tai tikrai SSL šifravimą palaikantis serveris ir prievadas?

  which, translated from lt_LT, means

  > * Cannot connect.  Error: (336130315) error:1408F10B:SSL 
routines:SSL3_GET_RECORD:wrong version number
  > Does the server/port really support SSL?

  I think this is part of the fallout of CVE-2014-3566 (aka POODLE).
  XChat-GNOME is trying to use the insecure SSL protocol version 3, and
  Slack, reasonably enough, rejects that.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xchat-gnome 1:0.30.0~git20131003.d20b8d+really20110821-0.2ubuntu12
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct 15 14:50:57 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-07-25 (811 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: xchat-gnome
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (180 days ago)

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

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

[Desktop-packages] [Bug 1383382] [NEW] Adding indicator-applet appmenu does not export all menu items to panel (Utopic)

2014-10-20 Thread Khurshid Alam

Public bug reported:

Current Scenerio
1. install indicator-applet-appmenu
2. add it to panel.
3. In the panel, It is showing only a single menu; File->close. All other menu 
items remains in the app.

Expected Scenario:

Adding indicator-applet-appmenu or global menu should move all the menu
items from local app to panel.

Gnome-Panel version on Utopic: 1:3.8.1-2ubuntu4

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

** Summary changed:

- Adding indicator-applet appmenu does not export all menu items to panel
+ Adding indicator-applet appmenu does not export all menu items to panel 
(Utopic)

** Description changed:

  Current Scenerio
  1. install indicator-applet-appmenu
  2. add it to panel.
- 3. It is showing only a single menu; File->close. All other menu items 
remains in the app.
+ 3. In the panel, It is showing only a single menu; File->close. All other 
menu items remains in the app.
  
  Expected Scenario:
  
  Adding indicator-applet-appmenu or global menu should move all the menu
  items from local app to panel.
  
  Gnome-Panel version on Utopic: 1:3.8.1-2ubuntu4

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

Title:
  Adding indicator-applet appmenu does not export all menu items to
  panel (Utopic)

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

Bug description:
  Current Scenerio
  1. install indicator-applet-appmenu
  2. add it to panel.
  3. In the panel, It is showing only a single menu; File->close. All other 
menu items remains in the app.

  Expected Scenario:

  Adding indicator-applet-appmenu or global menu should move all the
  menu items from local app to panel.

  Gnome-Panel version on Utopic: 1:3.8.1-2ubuntu4

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

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

[Desktop-packages] [Bug 1383382] Re: Adding indicator-applet appmenu does not export all menu items to panel (Utopic)

2014-10-20 Thread Dmitry Shachnev

Which application(s) did you test it with? Please make sure that you
have these packages installed:

unity-gtk3-module (for Gtk+ 3 apps)
unity-gtk2-module (for Gtk+ 2 apps)
appmenu-qt (for Qt 4 apps)

** Changed in: gnome-panel (Ubuntu)
   Status: New => Incomplete

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

Title:
  Adding indicator-applet appmenu does not export all menu items to
  panel (Utopic)

Status in “gnome-panel” package in Ubuntu:
  Incomplete

Bug description:
  Current Scenerio
  1. install indicator-applet-appmenu
  2. add it to panel.
  3. In the panel, It is showing only a single menu; File->close. All other 
menu items remains in the app.

  Expected Scenario:

  Adding indicator-applet-appmenu or global menu should move all the
  menu items from local app to panel.

  Gnome-Panel version on Utopic: 1:3.8.1-2ubuntu4

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

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

[Desktop-packages] [Bug 1383386] [NEW] display at 648 x 480

2014-10-20 Thread lazzasurf

Public bug reported:

cant change resolution

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 i686
.tmp.unity.support.test.1:
 
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Oct 20 18:03:27 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Silicon Integrated Systems [SiS] 771/671 PCIE VGA Display Adapter [1039:6351] 
(rev 10) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:19e2]
InstallationDate: Installed on 2014-10-19 (0 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
Lsusb:
 Bus 001 Device 002: ID 13d3:5094 IMC Networks 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ASUSTeK Computer Inc. K50C
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=65cb1af0-4388-4a83-88df-6074608341b3 ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/30/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 207
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K50C
dmi.board.vendor: ASUS CORPORATION
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr207:bd09/30/2009:svnASUSTeKComputerInc.:pnK50C:pvr1.0:rvnASUSCORPORATION:rnK50C:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
dmi.product.name: K50C
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
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: Mon Oct 20 17:24:29 2014
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.15.1-0ubuntu2

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


** Tags: apport-bug compiz-0.9 i386 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/1383386

Title:
  display at 648 x 480

Status in “xorg” package in Ubuntu:
  New

Bug description:
  cant change resolution

  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 i686
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Oct 20 18:03:27 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Silicon Integrated Systems [SiS] 771/671 PCIE VGA Display Adapter 
[1039:6351] (rev 10) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:19e2]
  InstallationDate: Installed on 2014-10-19 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  Lsusb:
   Bus 001 Device 002: ID 13d3:5094 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTeK Computer Inc. K50C
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=65cb1af0-4388-4a83-88df-6074608341b3 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 207
  dmi.board.as

[Desktop-packages] [Bug 1381484] Re: Fails to connect to servers that disable SSLv3

This bug was fixed in the package xchat - 2.8.8-7.1ubuntu7

---
xchat (2.8.8-7.1ubuntu7) utopic; urgency=medium

  * Don't force the use of SSLv3 (LP: #1381484)
- debian/patches/dont_force_sslv3.patch: use SSLv23_client_method()
  so the best method gets automatically negotiated in
  src/common/ssl.c.
 -- Steve BeattieMon, 20 Oct 2014 10:54:31 -0400

** Changed in: xchat (Ubuntu Utopic)
   Status: Fix Committed => Fix Released

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

Title:
  Fails to connect to servers that disable SSLv3

Status in GNOME frontend to the popular xchat IRC client:
  New
Status in “xchat” package in Ubuntu:
  Fix Released
Status in “xchat-gnome” package in Ubuntu:
  Fix Released
Status in “xchat” source package in Precise:
  In Progress
Status in “xchat-gnome” source package in Precise:
  In Progress
Status in “xchat” source package in Trusty:
  In Progress
Status in “xchat-gnome” source package in Trusty:
  In Progress
Status in “xchat” source package in Utopic:
  Fix Released
Status in “xchat-gnome” source package in Utopic:
  Fix Released
Status in “xchat-gnome” package in Debian:
  New

Bug description:
  SRU REQUEST:

  [Impact]

  Xchat-Gnome (and xchat) for the use of SSLv3. Since the Poodle attack
  on SSLv3, many servers are now disabling the use of SSLv3, making
  xchat-gnome unsable to connect successfully.

  [Test Case]

  Install xchat-gnome and connect to an irc server that no longer offers
  SSLv3.

  [Regression Potential]

  This update may possibly introduce compatibility issues with sites
  that don't properly handle TLSv1.2 negotiations. While such sites
  existed in the past, they aren't likely to be common at the present
  time. Unfortunately, there is no ultimate solution that would be
  compatible with both scenarios.

  
  Original report:

  slack.com is a chat service with optional IRC integration.  Since
  today I can no longer connect to their IRC gateway using XChat-GNOME.
  The error is:

  > * Nepavyko prisijungti. Klaida: (336130315) error:1408F10B:SSL 
routines:SSL3_GET_RECORD:wrong version number
  > Ar tai tikrai SSL šifravimą palaikantis serveris ir prievadas?

  which, translated from lt_LT, means

  > * Cannot connect.  Error: (336130315) error:1408F10B:SSL 
routines:SSL3_GET_RECORD:wrong version number
  > Does the server/port really support SSL?

  I think this is part of the fallout of CVE-2014-3566 (aka POODLE).
  XChat-GNOME is trying to use the insecure SSL protocol version 3, and
  Slack, reasonably enough, rejects that.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xchat-gnome 1:0.30.0~git20131003.d20b8d+really20110821-0.2ubuntu12
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct 15 14:50:57 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-07-25 (811 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: xchat-gnome
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (180 days ago)

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

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

[Desktop-packages] [Bug 1381484] Re: Fails to connect to servers that disable SSLv3

2014-10-20 Thread Bug Watch Updater

** Changed in: xchat-gnome (Debian)
   Status: Unknown => New

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

Title:
  Fails to connect to servers that disable SSLv3

Status in GNOME frontend to the popular xchat IRC client:
  New
Status in “xchat” package in Ubuntu:
  Fix Released
Status in “xchat-gnome” package in Ubuntu:
  Fix Released
Status in “xchat” source package in Precise:
  In Progress
Status in “xchat-gnome” source package in Precise:
  In Progress
Status in “xchat” source package in Trusty:
  In Progress
Status in “xchat-gnome” source package in Trusty:
  In Progress
Status in “xchat” source package in Utopic:
  Fix Released
Status in “xchat-gnome” source package in Utopic:
  Fix Released
Status in “xchat-gnome” package in Debian:
  New

Bug description:
  SRU REQUEST:

  [Impact]

  Xchat-Gnome (and xchat) for the use of SSLv3. Since the Poodle attack
  on SSLv3, many servers are now disabling the use of SSLv3, making
  xchat-gnome unsable to connect successfully.

  [Test Case]

  Install xchat-gnome and connect to an irc server that no longer offers
  SSLv3.

  [Regression Potential]

  This update may possibly introduce compatibility issues with sites
  that don't properly handle TLSv1.2 negotiations. While such sites
  existed in the past, they aren't likely to be common at the present
  time. Unfortunately, there is no ultimate solution that would be
  compatible with both scenarios.

  
  Original report:

  slack.com is a chat service with optional IRC integration.  Since
  today I can no longer connect to their IRC gateway using XChat-GNOME.
  The error is:

  > * Nepavyko prisijungti. Klaida: (336130315) error:1408F10B:SSL 
routines:SSL3_GET_RECORD:wrong version number
  > Ar tai tikrai SSL šifravimą palaikantis serveris ir prievadas?

  which, translated from lt_LT, means

  > * Cannot connect.  Error: (336130315) error:1408F10B:SSL 
routines:SSL3_GET_RECORD:wrong version number
  > Does the server/port really support SSL?

  I think this is part of the fallout of CVE-2014-3566 (aka POODLE).
  XChat-GNOME is trying to use the insecure SSL protocol version 3, and
  Slack, reasonably enough, rejects that.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xchat-gnome 1:0.30.0~git20131003.d20b8d+really20110821-0.2ubuntu12
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct 15 14:50:57 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-07-25 (811 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: xchat-gnome
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (180 days ago)

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

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

[Desktop-packages] [Bug 1383157] Re: [Lenovo T440p] New Trackpad: middle button with TrackPoint are not able to perform scroll

2014-10-20 Thread Joseph Salisbury

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.18 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc1-utopic/

** Changed in: xserver-xorg-input-synaptics (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [Lenovo T440p] New Trackpad: middle button with TrackPoint are not
  able to perform scroll

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

Bug description:
  Accroding to bug #1294515 , this feature should be included.

  
  Fail to scroll content with trackpoint and middle button.

  Steps to reproduce:

  1. hold the middle button (should be on center-top area, since it's 
button-less touchpad)
  2. move the trackpoint

  Actual results:

  nothing move, tried using xev to capture information but nothing
  return.

  Expected result:

  Content/page should scroll as TrackPoint move around.

  
  -
  Additoinal Information:

  ubuntu@201307-13930:~$ xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=10   [slave  pointer 
 (2)]
  ⎜   ↳ TPPS/2 IBM TrackPoint   id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Integrated Camera   id=8[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=9[slave  
keyboard (3)]
  ↳ ThinkPad Extra Buttons  id=12   [slave  
keyboard (3)]

  ubuntu@201307-13930:~$ xinput --list-props 11
  Device 'TPPS/2 IBM TrackPoint':
   Device Enabled (136):1
   Coordinate Transformation Matrix (138):  1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
   Device Accel Profile (260):  0
   Device Accel Constant Deceleration (261):1.00
   Device Accel Adaptive Deceleration (262):1.00
   Device Accel Velocity Scaling (263): 10.00
   Device Product ID (254): 2, 10
   Device Node (255):   "/dev/input/event4"
   Evdev Axis Inversion (301):  0, 0
   Evdev Axes Swap (303):   0
   Axis Labels (304):   "Rel X" (146), "Rel Y" (147)
   Button Labels (305): "Button Left" (139), "Button Middle" (140), "Button 
Right" (141), "Button Wheel Up" (142), "Button Wheel Down" (143), "Button Horiz 
Wheel Left" (144), "Button Horiz Wheel Right" (145)
   Evdev Scrolling Distance (306):  0, 0, 0
   Evdev Middle Button Emulation (307): 0
   Evdev Middle Button Timeout (308):   50
   Evdev Third Button Emulation (309):  0
   Evdev Third Button Emulation Timeout (310):  1000
   Evdev Third Button Emulation Button (311):   3
   Evdev Third Button Emulation Threshold (312):20
   Evdev Wheel Emulation (313): 1
   Evdev Wheel Emulation Axes (314):6, 7, 4, 5
   Evdev Wheel Emulation Inertia (315): 10
   Evdev Wheel Emulation Timeout (316): 200
   Evdev Wheel Emulation Button (317):  2
   Evdev Drag Lock Buttons (318):   0

  
  -

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-23-generic 3.16.0-23.30
  ProcVersionSignature: Ubuntu 3.16.0-23.30-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2066 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2066 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Oct 20 03:43:58 2014
  HibernationDevice: RESUME=UUID=ef079530-e68a-45a8-95b6-84a3dd18dfd6
  InstallationDate: Installed on 2014-10-20 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  MachineType: LENOVO 20ANZ039US
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic 
root=UUID=fe4fceda-a7bb-4159-a6b0-84357353090c ro rootdelay=60 quiet splash 
initcall_debug vt.handoff=7
  RelatedPackageVersi

[Desktop-packages] [Bug 1373404] Re: [notification] No warning of high volume level

2014-10-20 Thread Michał Sawicz

** Changed in: unity-notifications (Ubuntu)
   Status: Fix Released => In Progress

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

Title:
  [notification] No warning of high volume level

Status in Sound Menu:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in “indicator-sound” package in Ubuntu:
  In Progress
Status in “pulseaudio” package in Ubuntu:
  Invalid
Status in “ubuntu-system-settings” package in Ubuntu:
  In Progress
Status in “unity-notifications” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  In Progress
Status in “indicator-sound” package in Ubuntu RTM:
  Fix Released
Status in “unity-notifications” package in Ubuntu RTM:
  Fix Released
Status in “unity8” package in Ubuntu RTM:
  Fix Released

Bug description:
  The EU has a legal requirement for personal music players to prevent hearing 
damage.
  http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009D0490&rid=1
  

  Desired resolution:

  - For RTM the design spec'ed in the following section of the Sound
  wiki page should be implemented
  
https://wiki.ubuntu.com/Sound#Warnings_.28note:_This_section_should_be_implemented_for_RTM.29

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

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

[Desktop-packages] [Bug 1326903] Re: remmina and mumble windows get lost

2014-10-20 Thread Alexander Karatarakis

This still occurs in the latest version of Trusty. In order to retrieve
it, you either have to minimize every other window in the same desktop,
or simply quit and restart mumble.

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

Title:
  remmina and mumble windows get lost

Status in “bamf” package in Ubuntu:
  Confirmed

Bug description:
  Steps to repro:
  * start mumble
  * focus another window
  * click on mumble icon in launcher
  * switch to mumble through alt+tab

  Expected:
  * mumble window is focused and brought to front

  Current:
  * NOTHING ;)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bamfdaemon 0.5.1+14.04.20140409-0ubuntu1
  ProcVersionSignature: Ubuntu 3.15.0-5.10-generic 3.15.0-rc8
  Uname: Linux 3.15.0-5-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jun  5 19:19:19 2014
  SourcePackage: bamf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1326903] Re: remmina and mumble windows get lost

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

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

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

Title:
  remmina and mumble windows get lost

Status in “bamf” package in Ubuntu:
  Confirmed

Bug description:
  Steps to repro:
  * start mumble
  * focus another window
  * click on mumble icon in launcher
  * switch to mumble through alt+tab

  Expected:
  * mumble window is focused and brought to front

  Current:
  * NOTHING ;)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bamfdaemon 0.5.1+14.04.20140409-0ubuntu1
  ProcVersionSignature: Ubuntu 3.15.0-5.10-generic 3.15.0-rc8
  Uname: Linux 3.15.0-5-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jun  5 19:19:19 2014
  SourcePackage: bamf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1383382] Re: Adding indicator-applet appmenu does not export/move all menu items to panel (Utopic)

2014-10-20 Thread Khurshid Alam

** Summary changed:

- Adding indicator-applet appmenu does not export all menu items to panel 
(Utopic)
+ Adding indicator-applet appmenu does not export/move all menu items to panel 
(Utopic)

** Description changed:

  Current Scenerio
  1. install indicator-applet-appmenu
  2. add it to panel.
- 3. In the panel, It is showing only a single menu; File->close. All other 
menu items remains in the app.
+ 3. In the panel, It is showing only a single menu; File->close (for example 
for gnome-terminal). All other menu items remains in the app. For some gtk apps 
it doesn't show any menu at all.
+ 4. Surprisingly for Firefox it does move all the menus to panel
  
  Expected Scenario:
  
  Adding indicator-applet-appmenu or global menu should move all the menu
  items from local app to panel.
  
  Gnome-Panel version on Utopic: 1:3.8.1-2ubuntu4

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

Title:
  Adding indicator-applet appmenu does not export/move all menu items to
  panel (Utopic)

Status in “gnome-panel” package in Ubuntu:
  Incomplete

Bug description:
  Current Scenerio
  1. install indicator-applet-appmenu
  2. add it to panel.
  3. In the panel, It is showing only a single menu; File->close (for example 
for gnome-terminal). All other menu items remains in the app. For some gtk apps 
it doesn't show any menu at all.
  4. Surprisingly for Firefox it does move all the menus to panel

  Expected Scenario:

  Adding indicator-applet-appmenu or global menu should move all the
  menu items from local app to panel.

  Gnome-Panel version on Utopic: 1:3.8.1-2ubuntu4

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

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

[Desktop-packages] [Bug 1104230] Re: DisplayPort 1.2 MST support is missing in the Intel driver

2014-10-20 Thread Elvis Morales Fernandez

Hi Dariusz, will test your ppa asap I get home now. Question just to
confirm myself, should I have enabled DisplayPort 1.2 in my both Dell
monitors? Or, just the first one which is connected to the laptop.

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

Title:
  DisplayPort 1.2 MST support is missing in the Intel driver

Status in X.org xf86-video-intel:
  Unknown
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Confirmed

Bug description:
  I have two recent DisplayPort monitors, both supporting the 1.2
  version of the standard and one containing an MST hub (DELL 2913WM).

  I have an Intel Haswell based NUC connected over mini-displayport to
  the display containing the hub, then the second display is plugged in
  that one over DisplayPort.

  DisplayPort 1.2 is enabled on the display containing the hub and the
  second display lights up fine but just works as a clone of the first
  display, without ever showing up in xrandr, dmesg or any other useful
  logs I could find.

  My understanding of MST is that the second display should show up as
  DP2 on my laptop so I can configure it as I would any other display.

  UPDATE: Updated the bug report after it was pointed out that the
  original test hardware, a Lenovo x230 isn't DP 1.2 capable. The same
  test on hardware also fails, due to missing support for MST in the
  driver.

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

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

[Desktop-packages] [Bug 1383382] Re: Adding indicator-applet appmenu does not export/move all menu items to panel (Utopic)

2014-10-20 Thread Khurshid Alam

@Dmitry

I tested with mainly gtk3 apps (gnome-terminal, nautilus, eog..etc). For
gnome-terminal the panel only have File->Close (Screenshot:
http://i.imgur.com/cIcoSMW.png). For nautilus,  it does NOT move any
menu item to panel at all.

However for Firefox it is working alright.

And yes, I have unity-gtk2/3-module packages installed (updated in the
bug description).

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

Title:
  Adding indicator-applet appmenu does not export/move all menu items to
  panel (Utopic)

Status in “gnome-panel” package in Ubuntu:
  Incomplete

Bug description:
  Current Scenario

  1. install indicator-applet-appmenu
  2. add it to panel.

  3. In the panel, For some gtk apps (gnome-terminal) It is showing only
  a single menu; File->close. All other menu items remains in the app.
  For some gtk apps (i.e. Nautilus) it doesn't show any menu at all.

  4. Surprisingly for Firefox it does properly move all the menus to
  panel.

  
  Expected Scenario:

  Adding indicator-applet-appmenu or global menu should move all the
  menu items from local app to panel.

  Gnome-Panel version on Utopic: 1:3.8.1-2ubuntu4
  unity-gtk-module: 0.0.0+14.10.20140716-0ubuntu1
  gtk3+: 3.12.2-0ubuntu14
  indicator-appmenu: 12.10.2+14.04.20140403-0ubuntu1

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

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

[Desktop-packages] [Bug 1383409] [NEW] Support TLS (not just SSLv3)

2014-10-20 Thread Ian Young

Public bug reported:

Starting recently, I've been receiving this message when I try to
connect to my (previously working) mail account: 'The reported error was
"Could not connect to 'mail.messagingengine.com:143': TCP connection
reset by peer".'

Due to the timing, I suspect that this is occurring because my mail
provider (Fastmail) disabled SSLv3 support due to the POODLE
vulnerability. I also found this thread
(https://bugzilla.redhat.com/show_bug.cgi?id=1153052) concerning the
same issue from Red Hat, so it seems a fix exists but needs to be
released in the Ubuntu packages. This is a fairly serious problem, as I
am now unable to acccess my mail from Evolution (and if I was able to
access it, I would be doing so via a dangerously broken protocol).

Ubuntu 14.04
Evolution 3.10.4-0ubuntu2

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

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

Title:
  Support TLS (not just SSLv3)

Status in “evolution” package in Ubuntu:
  New

Bug description:
  Starting recently, I've been receiving this message when I try to
  connect to my (previously working) mail account: 'The reported error
  was "Could not connect to 'mail.messagingengine.com:143': TCP
  connection reset by peer".'

  Due to the timing, I suspect that this is occurring because my mail
  provider (Fastmail) disabled SSLv3 support due to the POODLE
  vulnerability. I also found this thread
  (https://bugzilla.redhat.com/show_bug.cgi?id=1153052) concerning the
  same issue from Red Hat, so it seems a fix exists but needs to be
  released in the Ubuntu packages. This is a fairly serious problem, as
  I am now unable to acccess my mail from Evolution (and if I was able
  to access it, I would be doing so via a dangerously broken protocol).

  Ubuntu 14.04
  Evolution 3.10.4-0ubuntu2

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

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

[Desktop-packages] [Bug 1383018] Re: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to build

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

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

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

Title:
  nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to
  build

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

Bug description:
  while installing updates

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-uvm 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  ApportVersion: 2.14.7-0ubuntu7
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-23-generic
  Date: Sun Oct 19 21:59:24 2014
  InstallationDate: Installed on 2013-10-03 (380 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131003)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to 
build
  UpgradeStatus: Upgraded to utopic on 2014-10-09 (10 days ago)

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

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

[Desktop-packages] [Bug 1382943] Re: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

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

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

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

Title:
  nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

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

Bug description:
  Error on apt-get dist-upgrade. Did not read the messages

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
  Uname: Linux 3.13.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu7
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-23-generic
  Date: Sun Oct 19 10:29:39 2014
  InstallationDate: Installed on 2013-11-27 (326 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
  UpgradeStatus: Upgraded to utopic on 2014-09-26 (22 days ago)

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

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

[Desktop-packages] [Bug 1382858] Re: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to build

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

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

Title:
  nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to
  build

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

Bug description:
  Running Software Updater

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-uvm 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu7
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-23-generic
  Date: Sat Oct 18 13:08:23 2014
  InstallationDate: Installed on 2012-04-02 (929 days ago)
  InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 
(20120328)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1382760] Re: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

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

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

Title:
  nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

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

Bug description:
  just updating 14.10 Beta.
  the actual nvidea driver works fine.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu7
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-23-generic
  Date: Sat Oct 18 08:24:56 2014
  InstallationDate: Installed on 2013-03-09 (587 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130308)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1382612] Re: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

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

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

Title:
  nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

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

Bug description:
  update, restart

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331
  ProcVersionSignature: Ubuntu 3.16.0-23.30-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu7
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-23-generic
  Date: Fri Oct 17 16:34:05 2014
  InstallationDate: Installed on 2014-04-18 (181 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
  UpgradeStatus: Upgraded to utopic on 2014-10-10 (7 days ago)
  modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted]

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

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

[Desktop-packages] [Bug 1382344] Re: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to build

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

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

Title:
  nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to
  build

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

Bug description:
  get this on boot up

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-uvm 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu7
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-22-generic
  Date: Sat Oct 11 13:04:22 2014
  InstallationDate: Installed on 2014-09-28 (19 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1382746] Re: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

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

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

Title:
  nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

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

Bug description:
  Lenovo ideapad y510p -- nvidia geforce gt 755m

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-23.30-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu7
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-23-generic
  Date: Fri Oct 17 20:55:37 2014
  InstallationDate: Installed on 2014-09-28 (19 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1382409] Re: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to build

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

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

Title:
  nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to
  build

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

Bug description:
  Upgrading from Ubuntu 14.04 LTS to 14.10. Previous nvidia driver:
  331.38.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-uvm 331.89-0ubuntu5
  Uname: Linux 3.16.5-031605-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu7
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-22-generic
  Date: Fri Oct 17 10:07:53 2014
  InstallationDate: Installed on 2012-03-21 (939 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to 
build
  UpgradeStatus: Upgraded to utopic on 2014-10-17 (0 days ago)

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

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

[Desktop-packages] [Bug 1382786] Re: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to build

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

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

Title:
  nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to
  build

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

Bug description:
  After running game from Steam. I was loggt out and got this bug

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-uvm 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  ApportVersion: 2.14.7-0ubuntu7
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-23-generic
  Date: Sat Oct 18 11:12:03 2014
  InstallationDate: Installed on 2013-10-12 (370 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Beta amd64 
(20130926)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to 
build
  UpgradeStatus: Upgraded to utopic on 2014-10-13 (4 days ago)

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

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

[Desktop-packages] [Bug 1382544] Re: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel module failed to build

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

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

Title:
  nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel
  module failed to build

Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Confirmed

Bug description:
  Kernel linux

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-updates-uvm
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu7
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-23-generic
  Date: Fri Oct 17 07:56:10 2014
  InstallationDate: Installed on 2014-08-16 (61 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel 
module failed to build
  UpgradeStatus: Upgraded to utopic on 2014-10-16 (0 days ago)

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

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

[Desktop-packages] [Bug 1382592] Re: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to build

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

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

Title:
  nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to
  build

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

Bug description:
  just upgraded...

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-uvm 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  ApportVersion: 2.14.7-0ubuntu7
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-23-generic
  Date: Fri Oct 17 16:48:08 2014
  InstallationDate: Installed on 2013-01-14 (640 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to 
build
  UpgradeStatus: Upgraded to utopic on 2014-09-14 (33 days ago)

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

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

[Desktop-packages] [Bug 1104230] Re: DisplayPort 1.2 MST support is missing in the Intel driver

Hi Elvis, unfortunately I do not know that. Please consult your user's
manual. I haven't got access to those monitors. Thank you!

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

Title:
  DisplayPort 1.2 MST support is missing in the Intel driver

Status in X.org xf86-video-intel:
  Unknown
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Confirmed

Bug description:
  I have two recent DisplayPort monitors, both supporting the 1.2
  version of the standard and one containing an MST hub (DELL 2913WM).

  I have an Intel Haswell based NUC connected over mini-displayport to
  the display containing the hub, then the second display is plugged in
  that one over DisplayPort.

  DisplayPort 1.2 is enabled on the display containing the hub and the
  second display lights up fine but just works as a clone of the first
  display, without ever showing up in xrandr, dmesg or any other useful
  logs I could find.

  My understanding of MST is that the second display should show up as
  DP2 on my laptop so I can configure it as I would any other display.

  UPDATE: Updated the bug report after it was pointed out that the
  original test hardware, a Lenovo x230 isn't DP 1.2 capable. The same
  test on hardware also fails, due to missing support for MST in the
  driver.

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

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

[Desktop-packages] [Bug 1382484] Re: nvidia-331 331.38-0ubuntu7.1: nvidia-331 kernel module failed to build

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

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

Title:
  nvidia-331 331.38-0ubuntu7.1: nvidia-331 kernel module failed to build

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

Bug description:
  Automatic bug report

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu7.1
  ProcVersionSignature: Ubuntu 3.13.0-38.65-generic 3.13.11.8
  Uname: Linux 3.13.0-38-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-38-generic
  Date: Thu Oct 16 18:49:36 2014
  InstallationDate: Installed on 2012-10-20 (726 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  PackageVersion: 331.38-0ubuntu7.1
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.38-0ubuntu7.1: nvidia-331 kernel module failed to build
  UpgradeStatus: Upgraded to trusty on 2014-04-28 (171 days ago)

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

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

[Desktop-packages] [Bug 1382609] Re: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build