[Desktop-packages] [Bug 1496542] Re: Running processes left after disabling screen reader

2023-12-16 Thread Jeroen Hoek
The issue of these speech-dispatcher processes spawning for some unknown
reason and distorting sound (as mentioned above a few users) is still
present in 22.04 for me.

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

Title:
  Running processes left after disabling screen reader

Status in speech-dispatcher package in Ubuntu:
  Triaged

Bug description:
  After I disabled my screen reader, I noticed that when running "ps xa
  | grep -P 'speech-dispatcher.*\.conf'" I get:

  17906 tty2 Sl+0:09 /usr/lib/speech-dispatcher-modules/sd_espeak 
/etc/speech-dispatcher/modules/espeak.conf
  17911 tty2 Sl+0:01 /usr/lib/speech-dispatcher-modules/sd_cicero 
/etc/speech-dispatcher/modules/cicero.conf
  17915 tty2 Sl+0:01 /usr/lib/speech-dispatcher-modules/sd_generic 
/etc/speech-dispatcher/modules/generic.conf
  17918 tty2 Sl+0:01 /usr/lib/speech-dispatcher-modules/sd_dummy 
/etc/speech-dispatcher/modules/dummy.conf
  24407 pts/0S+ 0:00 grep --color=auto -P speech-dispatcher.*\.conf

  So it seems as though it left some running processes behind after I
  disabled it. I have also attached a screenshot of my Sound settings
  which show that they are still running (Sound_Application_List2.png).

  ---

  OS Information:

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 15.04
  Release:  15.04
  Codename: vivid

  Package Information:

  speech-dispatcher:
Installed: 0.8.1-0ubuntu1
Candidate: 0.8.1-0ubuntu1
Version table:
   *** 0.8.1-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: speech-dispatcher 0.8.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep 16 20:27:00 2015
  InstallationDate: Installed on 2015-07-29 (49 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: speech-dispatcher
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1958267] Re: wpa can't connect to servers using TLS 1.1 or older

2022-06-15 Thread Jeroen Bruinink
I enabled propsed and updated wpasupplicant to 2:2.10-6ubuntu2 and I'm
now able to connect to the corporate WiFi network again. Thanks!

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

Title:
  wpa can't connect to servers using TLS 1.1 or older

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Jammy:
  Fix Committed
Status in wpa package in Debian:
  New

Bug description:
  * Impact
  wpa built with in openssl3 fails to connect to TLS 1.1 or lower server

  * Test case
  try to connect to a TLS <= 1.1 access point

  * Regression potential
  the patch lowers the security level in some situation for compatibility, it 
shouldn't prevent connecting to newer hardware, still try to connect to 
different type of wifi with different security levels

  ---

  those uses MD5-SHA1 as digest in its signature algorithm which no
  longer meets OpenSSL default level of security of 80 bits

  http://lists.infradead.org/pipermail/hostap/2022-May/040563.html

  Workaround are described in #22 and #36 by basically using
  CipherString = DEFAULT@SECLEVEL=0

  which lowers the security level

  ---

  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 433231] Re: xorg: directory "/usr/share/fonts/X11/cyrillic" does not exist.

2020-04-07 Thread Jeroen
sudo apt-get install xfonts-cyrillic fixed it on ubuntu 18.04

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

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

Title:
  xorg: directory "/usr/share/fonts/X11/cyrillic" does not exist.

Status in X.Org X server:
  Invalid
Status in xorg package in Ubuntu:
  New

Bug description:
  Hello,

  I run on Kubuntu Karmic 64,  2.6.31-10-genericx86 64

  In my log are this error:

  Avertissement   The directory "/usr/share/fonts/X11/cyrillic" does not
  exist.

  [lspci]
  01:00.0 VGA compatible controller [0300]: nVidia Corporation G92 [GeForce 
9800 GTX] [10de:0612] (rev a2)
Subsystem: ASUSTeK Computer Inc. Device [1043:82a6]

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

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


[Desktop-packages] [Bug 1851833] [NEW] Unable to adjust brightness of backlight

2019-11-08 Thread Jeroen Bruinink
Public bug reported:

I am unable to adjust the brightness of the backlight of my laptop
screen either by using the slider of by changing the value in
/sys/class/backlight/intel_backlight/brightness directly.

I have tried changing my GRUB configuration:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor"
But that did not help.

I am using Ubuntu 19.10

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
 GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov  8 14:03:33 2019
DistUpgraded: 2019-10-09 11:42:34,460 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 435.21, 5.3.0-19-generic, x86_64: installed
 virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed
 virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
   Subsystem: CLEVO/KAPOK Computer UHD Graphics 630 (Mobile) [1558:65d1]
 NVIDIA Corporation TU106M [GeForce RTX 2070 Mobile] [10de:1f10] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer TU106M [GeForce RTX 2070 Mobile] [1558:65d1]
InstallationDate: Installed on 2019-10-09 (30 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: Notebook PB50_70RF,RD,RC
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_backlight=vendor 
vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to eoan on 2019-10-09 (30 days ago)
dmi.bios.date: 02/01/2019
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.07
dmi.board.asset.tag: Tag 12345
dmi.board.name: PB50_70RF,RD,RC
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.07:bd02/01/2019:svnNotebook:pnPB50_70RF,RD,RC:pvrNotApplicable:rvnNotebook:rnPB50_70RF,RD,RC:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: PB50_70RF,RD,RC
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug eoan 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/1851833

Title:
  Unable to adjust brightness of backlight

Status in xorg package in Ubuntu:
  New

Bug description:
  I am unable to adjust the brightness of the backlight of my laptop
  screen either by using the slider of by changing the value in
  /sys/class/backlight/intel_backlight/brightness directly.

  I have tried changing my GRUB configuration:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor"
  But that did not help.

  I am using Ubuntu 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun 

[Desktop-packages] [Bug 1600299] Re: Giving up after 5 attempts. Error: g-io-error-quark: The specified location is not mounted

2019-01-04 Thread Jeroen Evens
same issue
backup was working fine 2 weeks ago, now it started giving this error
Ubuntu 18.04

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

Title:
  Giving up after 5 attempts. Error: g-io-error-quark: The specified
  location is not mounted

Status in Déjà Dup:
  Triaged
Status in deja-dup package in Ubuntu:
  Triaged
Status in deja-dup package in Mandriva:
  New

Bug description:
  I've got my system set up with off-site backup over sftp. This works
  fine but the problem is that while deja-dup is gathering files and
  calculating the backup delta the connection to the server times out.
  This means that it's not available when deja-dup actually tries to
  push files to the server and results in this error message:

  Giving up after 5 attempts. Error: g-io-error-quark: The specified
  location is not mounted (16)

  By sitting in the file manager and jumping between folders the
  connection can be kept alive but that's rather annoying and requires
  my presence. Would really like to see deja-dup actually trying to set
  up the connection again instead.

  
  Using:
  Manjaro 16.06.1
  deja-dup 34.2-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1600299/+subscriptions

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


[Desktop-packages] [Bug 1318030] Re: Cannot login-without-password when home folder is encrypted

2018-11-03 Thread Jeroen
** Summary changed:

- Cannot login-without-password when home folder in encrypted
+ Cannot login-without-password when home folder is encrypted

** Description changed:

- Users of which the home folder is encrypted using the CLI (unfortunately
+ Users of whom the home folder is encrypted using the CLI (unfortunately
  there is no GUI option for this, see
  https://bugs.launchpad.net/ubuntu/+source/gnome-control-
  center/+bug/1279766), and for which the 'login without password' is set,
  cannot login.
  
  Steps to reproduce:
  1. Using an Administrator account, create a new user in System Settings > 
User Accounts and set a password.
  2. Open a shell and encrypt the newly created user folder by 'sudo 
ecryptfs-migrate-home -u '
  3. Login into the new account: successful
  4. Logout and login into the Administrator account and select 'Login without 
password' for the newly created user.
  5. Login into the new account: cannot login (the password field for this 
users now displays 'Log in' but trying to login results in a flickering screen 
and back to the login screen.
  
  Ubuntu 14.04 x64 (reproducable on two different machines)

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

Title:
  Cannot login-without-password when home folder is encrypted

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

Bug description:
  Users of whom the home folder is encrypted using the CLI
  (unfortunately there is no GUI option for this, see
  https://bugs.launchpad.net/ubuntu/+source/gnome-control-
  center/+bug/1279766), and for which the 'login without password' is
  set, cannot login.

  Steps to reproduce:
  1. Using an Administrator account, create a new user in System Settings > 
User Accounts and set a password.
  2. Open a shell and encrypt the newly created user folder by 'sudo 
ecryptfs-migrate-home -u '
  3. Login into the new account: successful
  4. Logout and login into the Administrator account and select 'Login without 
password' for the newly created user.
  5. Login into the new account: cannot login (the password field for this 
users now displays 'Log in' but trying to login results in a flickering screen 
and back to the login screen.

  Ubuntu 14.04 x64 (reproducable on two different machines)

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

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


[Desktop-packages] [Bug 1766495] Re: "your libfreerdp does not support h264"

2018-09-24 Thread Jeroen
Same here, Ubuntu 18.04.1 LTS (Lubuntu), latest Remmina version.
Workaround the same as above, changing color depth to True Color (32bpp) fixed 
it.

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

Title:
  "your libfreerdp does not support h264"

Status in remmina package in Ubuntu:
  Confirmed

Bug description:
  When I try to connect via RDP, Remmina gives this error:

  "You requested an h264 GFX mode for server , but your
  libfreerdp does not support h264. Please check color depth settings."

  However, (1) I don't see any color depth settings in Remmina GUI, and
  (2) ubuntu-restricted-extras is installed. I have libx264-152 version
  2:0.152.2854+gite9a5903-2.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: remmina 1.2.0-rcgit.29+dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Apr 24 09:29:44 2018
  InstallationDate: Installed on 2018-03-23 (31 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  SourcePackage: remmina
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 29894] Re: can't take screenshot when menu on panel is opened

2018-09-19 Thread Jeroen
Today I wanted to make a screenshot on Ubuntu 18.04.1 LTS with a menu
open but it still fails and the issue still persists.

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

Title:
  can't take screenshot when menu on panel is opened

Status in GNOME Panel:
  In Progress
Status in Unity:
  Triaged
Status in gnome-panel package in Ubuntu:
  Fix Released
Status in gnome-screenshot package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  I can always press the "Print screen" key to take a screenshot of my
  desktop. When i click on say, the System menu in the gnome-panel, it
  just doesn't work anymore.

  Note: this is in fact only a symptom of bug 10905 that states that no
  hotkeys/shortcuts whatsoever can be triggered when a menu is open.
  there seems to be a dispute if that is a bug or an intended design
  decision. thus bug 10905 and its duplicates always get closed. people
  seem to agree that not being able to take screenshots is not intended
  bahavior and considered a bug. thus this report is allowed to stay
  open :)

  a known workaround for taking screenshots of menus is to directly launch the 
screengrabber with a delay like so:
  gnome-screenshot --delay=5

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

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


[Desktop-packages] [Bug 1711087] Re: ad2p sink profile mic not available

2018-09-16 Thread Jeroen
Yes, this is a duplicate of bug #508522. IMHO I think that we should
close this issue and re-open bug #508533.

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

Title:
  ad2p sink profile mic not available

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I have a bose soundsport bluetooth headset. When I select the ad2p
  sink profile there is no microphone available. Only with the HSP
  profile my microphone is available.

  It's really annoying to have to switch between profiles to make a call
  or to listen to normal quality music.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jeroen 3801 F pulseaudio
   /dev/snd/controlC0:  jeroen 3801 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Aug 16 11:02:37 2017
  InstallationDate: Installed on 2017-05-10 (98 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1773IMS.106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1773
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.name: GS70 2QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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


[Desktop-packages] [Bug 1711087] Re: ad2p sink profile mic not available

2018-09-16 Thread Jeroen
*re-open #508522

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

Title:
  ad2p sink profile mic not available

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I have a bose soundsport bluetooth headset. When I select the ad2p
  sink profile there is no microphone available. Only with the HSP
  profile my microphone is available.

  It's really annoying to have to switch between profiles to make a call
  or to listen to normal quality music.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jeroen 3801 F pulseaudio
   /dev/snd/controlC0:  jeroen 3801 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Aug 16 11:02:37 2017
  InstallationDate: Installed on 2017-05-10 (98 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1773IMS.106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1773
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.name: GS70 2QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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


[Desktop-packages] [Bug 1791421] [NEW] Nautilus hangs when opening a password protected .7z file

2018-09-08 Thread Jeroen
Public bug reported:

Very simple scenario: On a fresh Ubuntu 18.04 installation (with Unity
and pzip-full installed) I try to open a password protected .7z file
(created in an older Ubuntu version). Nautilus starts flickering, CPU
usage rises to 80% for minutes and Nautilus is not usable for a long
time. Minimising doesn't work, however terminating does, where after CPU
usage turns to normal.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.3-0ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sat Sep  8 12:30:29 2018
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'196'
 b'org.gnome.nautilus.window-state' b'geometry' b"'890x540+226+183'"
 b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'"
InstallationDate: Installed on 2018-09-01 (6 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus: dropbox 2015.10.28

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


** Tags: amd64 apport-bug bionic

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

Title:
  Nautilus hangs when opening a password protected .7z file

Status in nautilus package in Ubuntu:
  New

Bug description:
  Very simple scenario: On a fresh Ubuntu 18.04 installation (with Unity
  and pzip-full installed) I try to open a password protected .7z file
  (created in an older Ubuntu version). Nautilus starts flickering, CPU
  usage rises to 80% for minutes and Nautilus is not usable for a long
  time. Minimising doesn't work, however terminating does, where after
  CPU usage turns to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat Sep  8 12:30:29 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'196'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x540+226+183'"
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'"
  InstallationDate: Installed on 2018-09-01 (6 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: dropbox 2015.10.28

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

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


[Desktop-packages] [Bug 1003682] Re: Borderless printing doesn't work on the Photosmart B8500 with hpcups

2018-09-04 Thread Jeroen Dekkers
I don't longer have access to a photosmart printer so I can't confirm if
it is still a problem or not.

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

Title:
  Borderless printing doesn't work on the Photosmart B8500 with hpcups

Status in HPLIP:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  I can't get borderless printing to work on the Photosmart B8500 with
  the hpcups drivers. Borderless printing does work with the hpijs
  drivers, but those drivers have some quality problems. The problem is
  that the hpijs driver give green lines with some prints, changing to
  the hpcups driver solves that problem (and hpcups is also the
  preferred driver if I'm right), but then borderless printing doesn't
  work. Searching for a solution I encountered this bug
  https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/405116 and thus
  upgraded from 10.04 to 12.04, but I still get margins when trying to
  print something borderless. I did add all the printers again to make
  sure I was using the newer drivers.

  I've attached the debug log of an example job. As you can the PageSize
  is correctly set to A4.FB, but somehow that doesn't work. I've also
  attached the output of hp-check.

  I am a programmer, so if you can give any hints as to where in the
  code the problem might be or what I could try changing to see if the
  problems goes away that would also be very welcome. I've already tried
  changing a lot of settings and looking quickly at the code, but I'm a
  bit stuck at the moment.

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

-- 
Mailing list: https://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 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() f

2018-04-15 Thread Jeroen Donkervoort
Same here, after I read this message, I changed my login settings to Ubuntu
on Wayland and never got this error again

2018-04-14 8:38 GMT+02:00 Per-Inge :

> I always get this bug when I start with an Xorg session. I started with
> a Wayland session and didn't get the bug.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1752815).
> https://bugs.launchpad.net/bugs/1748450
>
> Title:
>   gnome-shell crashed with SIGTRAP in _g_log_abort() from
>   g_log_default_handler() from default_log_handler(message="Connection
>   to xwayland lost") from g_logv() from g_log() from 
>
> Status in gnome-shell package in Ubuntu:
>   Triaged
> Status in gnome-shell source package in Bionic:
>   Triaged
>
> Bug description:
>   *** This is a duplicate of bug 1505409, but is being kept separate so
>   as to automatically collect duplicate reports since the stacktrace
>   signature has changed recently. Any resolution and discussion should
>   occur in bug 1505409. ***
>
>   See also:
>   https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988
> f78ecd0f95
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-shell 3.26.2-0ubuntu2
>   ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
>   Uname: Linux 4.13.0-33-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu8
>   Architecture: amd64
>   CurrentDesktop: GNOME-Greeter:GNOME
>   Date: Thu Feb  8 23:50:23 2018
>   DisplayManager: gdm3
>   ExecutablePath: /usr/bin/gnome-shell
>   GsettingsChanges:
>
>   InstallationDate: Installed on 2016-03-21 (690 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64
> (20160307)
>   ProcCmdline: /usr/bin/gnome-shell
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/false
>   Signal: 5
>   SourcePackage: gnome-shell
>   StacktraceTop:
>() at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
>_XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>_XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>() at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
>   Title: gnome-shell crashed with signal 5
>   UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
>   UserGroups:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+
> bug/1748450/+subscriptions
>

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler(message="Connection
  to xwayland lost") from g_logv() from g_log() from 

Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell source package in Bionic:
  Triaged

Bug description:
  *** This is a duplicate of bug 1505409, but is being kept separate so
  as to automatically collect duplicate reports since the stacktrace
  signature has changed recently. Any resolution and discussion should
  occur in bug 1505409. ***

  See also:
  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
  Uname: Linux 4.13.0-33-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Feb  8 23:50:23 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2016-03-21 (690 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
  UserGroups:

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

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


[Desktop-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started

2018-02-02 Thread Jeroen Hoek
I hope something can be worked out before this lands in the next LTS-
release. This breaks one of the most common uses of a VPN (remote work).

Right now a workaround is using this script after connecting to a VPN-
server:

https://github.com/jonathanio/update-systemd-resolved

It calls systemd-resolved via DBus to add the proper settings after the
OpenVPN connection is established.

Of course this means abandoning NetworkManager for use with OpenVPN,
because there is also no way to specify --up and --down parameters.

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

Title:
  DNS domain search paths not updated when VPN started

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager-openvpn package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I connect to work with openvpn through network-manager-openvpn.  I'm
  selecting automatic (DHCP) to get an IP address, and "Use this
  connection only for resources on its network" to support split
  tunneling.

  In the last few versions of Ubuntu I used, this all worked fine.  In
  Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both
  my VPN network and the internet, BUT I have to use FQDN for my VPN
  network hosts: the updates to the DNS search path provided by my VPN
  DHCP server are never being applied.

  Investigating the system I see that /etc/resolv.conf is pointing to
  /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not
  have any of the VPN's search path settings in it:

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual 
nameservers.
nameserver 127.0.0.53

search home

  In previous versions of Ubuntu, where NetworkManager controlled the
  resolver not systemd, /etc/resolv.conf pointed to
  /run/NetworkManager/resolv.conf and there was a local dnsmasq instance
  that managed all the complexity.  In Ubuntu 17.10 when I look in
  /run/NetworkManager/resolv.conf file, I see that the search paths ARE
  properly updated there:

$ cat /run/NetworkManager/resolv.conf 
# Generated by NetworkManager
search internal.mycorp.com other.mycorp.com home
nameserver 127.0.1.1

  However this file isn't being used, and also there's no dnsmasq
  running on the system so if I switch my /etc/resolv.conf to point to
  this file instead, then all lookups fail.

  Strangely, if I look at the systemd-resolv status I see that in theory
  systemd-resolve does seem to know about the proper search paths:

$ systemd-resolve --status
   ...
Link 3 (tun0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 10.3.0.10
  10.8.42.2
  DNS Domain: ~internal.mycorp.com
  ~other.mycorp.com

  but for whatever reason the search domains are not getting put into
  the resolv.conf file:

$ host mydesk
;; connection timed out; no servers could be reached

$ host mydesk.internal.mycorp.com
mydesk.internal.mycorp.com has address 10.8.37.74

  (BTW, the timeout in the failed attempt above takes 10s: it is SUPER
  frustrating when all your host lookups are taking that long just to
  fail).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 22 15:08:57 2017
  InstallationDate: Installed on 2017-10-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.typ

[Desktop-packages] [Bug 1711087] Re: ad2p sink profile mic not available

2017-12-21 Thread Jeroen
*** This bug is a duplicate of bug 508522 ***
https://bugs.launchpad.net/bugs/508522

Can you maybe re-open bug 508522? It will ensure that this issue get's
the priority it deserves.

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

Title:
  ad2p sink profile mic not available

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have a bose soundsport bluetooth headset. When I select the ad2p
  sink profile there is no microphone available. Only with the HSP
  profile my microphone is available.

  It's really annoying to have to switch between profiles to make a call
  or to listen to normal quality music.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jeroen 3801 F pulseaudio
   /dev/snd/controlC0:  jeroen 3801 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Aug 16 11:02:37 2017
  InstallationDate: Installed on 2017-05-10 (98 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1773IMS.106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1773
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.name: GS70 2QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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


[Desktop-packages] [Bug 1711087] Re: ad2p sink profile mic not available

2017-12-21 Thread Jeroen
*** This bug is a duplicate of bug 508522 ***
https://bugs.launchpad.net/bugs/508522

It seems like PulseAudio can handle ad2p correctly but maybe the audio
configuration is not using the right parameters to initialize the sound
system.

I'm a Java developer. I'm willing to take a look at the source code but
it would take me some time to get started. I have no Linux developer
experience.

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

Title:
  ad2p sink profile mic not available

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have a bose soundsport bluetooth headset. When I select the ad2p
  sink profile there is no microphone available. Only with the HSP
  profile my microphone is available.

  It's really annoying to have to switch between profiles to make a call
  or to listen to normal quality music.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jeroen 3801 F pulseaudio
   /dev/snd/controlC0:  jeroen 3801 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Aug 16 11:02:37 2017
  InstallationDate: Installed on 2017-05-10 (98 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1773IMS.106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1773
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.name: GS70 2QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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


[Desktop-packages] [Bug 1711087] Re: ad2p sink profile mic not available

2017-12-21 Thread Jeroen
*** This bug is a duplicate of bug 508522 ***
https://bugs.launchpad.net/bugs/508522

Actually it's a duplicate of a bug that has been fixed before (with high
priority).

** This bug has been marked a duplicate of bug 508522
   Mic is not available with A2DP Bluetooth profile

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

Title:
  ad2p sink profile mic not available

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have a bose soundsport bluetooth headset. When I select the ad2p
  sink profile there is no microphone available. Only with the HSP
  profile my microphone is available.

  It's really annoying to have to switch between profiles to make a call
  or to listen to normal quality music.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jeroen 3801 F pulseaudio
   /dev/snd/controlC0:  jeroen 3801 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Aug 16 11:02:37 2017
  InstallationDate: Installed on 2017-05-10 (98 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1773IMS.106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1773
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.name: GS70 2QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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


[Desktop-packages] [Bug 1711087] Re: ad2p sink profile mic not available

2017-12-21 Thread Jeroen
It keeps the high quality.

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

Title:
  ad2p sink profile mic not available

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have a bose soundsport bluetooth headset. When I select the ad2p
  sink profile there is no microphone available. Only with the HSP
  profile my microphone is available.

  It's really annoying to have to switch between profiles to make a call
  or to listen to normal quality music.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jeroen 3801 F pulseaudio
   /dev/snd/controlC0:  jeroen 3801 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Aug 16 11:02:37 2017
  InstallationDate: Installed on 2017-05-10 (98 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1773IMS.106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1773
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.name: GS70 2QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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


[Desktop-packages] [Bug 1711087] Re: ad2p sink profile mic not available

2017-12-21 Thread Jeroen
As you can see there are no recording devices present.

** Attachment added: "ad2p sink; no input devices.png"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711087/+attachment/5025541/+files/ad2p%20sink%3B%20no%20input%20devices.png

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

Title:
  ad2p sink profile mic not available

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a bose soundsport bluetooth headset. When I select the ad2p
  sink profile there is no microphone available. Only with the HSP
  profile my microphone is available.

  It's really annoying to have to switch between profiles to make a call
  or to listen to normal quality music.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jeroen 3801 F pulseaudio
   /dev/snd/controlC0:  jeroen 3801 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Aug 16 11:02:37 2017
  InstallationDate: Installed on 2017-05-10 (98 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1773IMS.106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1773
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.name: GS70 2QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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


[Desktop-packages] [Bug 1711087] Re: ad2p sink profile mic not available

2017-12-21 Thread Jeroen
However if I select the HSP/HPF profile, it is. However with very low quality 
audio.
The strange thing that if I switch back to the AD2p Source profile. The 
microphone is available.

I've tested this using Skype version 8.11.0.4

** Attachment added: "HSP,HPF profile; bose input devices present.png"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711087/+attachment/5025542/+files/HSP%2CHPF%20profile%3B%20bose%20input%20devices%20present.png

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

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

Title:
  ad2p sink profile mic not available

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a bose soundsport bluetooth headset. When I select the ad2p
  sink profile there is no microphone available. Only with the HSP
  profile my microphone is available.

  It's really annoying to have to switch between profiles to make a call
  or to listen to normal quality music.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jeroen 3801 F pulseaudio
   /dev/snd/controlC0:  jeroen 3801 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Aug 16 11:02:37 2017
  InstallationDate: Installed on 2017-05-10 (98 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1773IMS.106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1773
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.name: GS70 2QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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


[Desktop-packages] [Bug 1711087] Re: ad2p sink profile mic not available

2017-12-21 Thread Jeroen
When I select the ad2p source/sink profile the mic won't work anywhere.

** Attachment added: "bluetooth profile selection screen"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711087/+attachment/5025540/+files/ad2p%20sink%20profile.png

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

Title:
  ad2p sink profile mic not available

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a bose soundsport bluetooth headset. When I select the ad2p
  sink profile there is no microphone available. Only with the HSP
  profile my microphone is available.

  It's really annoying to have to switch between profiles to make a call
  or to listen to normal quality music.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jeroen 3801 F pulseaudio
   /dev/snd/controlC0:  jeroen 3801 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Aug 16 11:02:37 2017
  InstallationDate: Installed on 2017-05-10 (98 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1773IMS.106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1773
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.name: GS70 2QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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


[Desktop-packages] [Bug 1711087] Re: ad2p sink profile mic not available

2017-08-17 Thread Jeroen
PS Sorry I didn't mean to be disrespectful, I love (K)ubuntu, it has
been my main operating system for a decade now. Just a bit disappointed
that the relatively new android operating system is more mature here. I
will provide more info later. Thanks for the help so far.

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

Title:
  ad2p sink profile mic not available

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I have a bose soundsport bluetooth headset. When I select the ad2p
  sink profile there is no microphone available. Only with the HSP
  profile my microphone is available.

  It's really annoying to have to switch between profiles to make a call
  or to listen to normal quality music.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jeroen 3801 F pulseaudio
   /dev/snd/controlC0:  jeroen 3801 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Aug 16 11:02:37 2017
  InstallationDate: Installed on 2017-05-10 (98 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1773IMS.106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1773
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.name: GS70 2QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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


[Desktop-packages] [Bug 1711087] Re: ad2p sink profile mic not available

2017-08-17 Thread Jeroen
not a bug but a feature then lol?

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

Title:
  ad2p sink profile mic not available

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I have a bose soundsport bluetooth headset. When I select the ad2p
  sink profile there is no microphone available. Only with the HSP
  profile my microphone is available.

  It's really annoying to have to switch between profiles to make a call
  or to listen to normal quality music.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jeroen 3801 F pulseaudio
   /dev/snd/controlC0:  jeroen 3801 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Aug 16 11:02:37 2017
  InstallationDate: Installed on 2017-05-10 (98 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1773IMS.106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1773
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.name: GS70 2QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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


[Desktop-packages] [Bug 1711087] Re: ad2p sink profile mic not available

2017-08-17 Thread Jeroen
Then why is it that it works perfectly in android?

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

Title:
  ad2p sink profile mic not available

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I have a bose soundsport bluetooth headset. When I select the ad2p
  sink profile there is no microphone available. Only with the HSP
  profile my microphone is available.

  It's really annoying to have to switch between profiles to make a call
  or to listen to normal quality music.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jeroen 3801 F pulseaudio
   /dev/snd/controlC0:  jeroen 3801 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Aug 16 11:02:37 2017
  InstallationDate: Installed on 2017-05-10 (98 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1773IMS.106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1773
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.name: GS70 2QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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


[Desktop-packages] [Bug 508522] Re: Mic is not available with A2DP Bluetooth profile

2017-08-16 Thread Jeroen
I've created a new bug report to provide more information:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711087

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

Title:
  Mic is not available with A2DP Bluetooth profile

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: pulseaudio

  I'm testing a Nokia BH-905i headset (see 
http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The 
Bluetooth module correctly identifies the headset and the both audio profiles 
"HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music 
playback only A2DP is suitable (HSP/HFP sounds like listening to music played 
through an old telephone). A2DP does not have an INPUT mode, so use of the 
headset for VoiP isn't possible.
  What would be needed is a separate selection to allow to select A2DP for 
output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do 
that (or they switch on the fly?).

  Formal structure:
  1) Ubuntu 10.10
  2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1
  consisting og pluseaudio, pulseaudio-esound-compat, 
pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, 
pulseaudio-utils
  3) Select high quality audio output and still use the Bluetooth microphone
  4) Had to choose: either high quality audio or "telephone quality" with 
microphone

  I can change the profile without the Bluetooth connection dropping,
  but that's ridiculous. E.g. listening to music, a call comes in. Then
  I would need to switch the profile before answering. Please note that
  in Windows, Mac OS, iOS, Android, and Windows Mobile it's done
  automatically.

  Check out attached screencast.

  ProblemType: Bug
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oivasyuv   2309 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17'
     Mixer name : 'Analog Devices AD1984A'
     Components : 'HDA:11d4194a,103c30e8,00100400'
     Controls  : 22
     Simple ctrls  : 14
  Date: Sat Jan 16 22:31:41 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: pulseaudio 1:0.9.19-0ubuntu4
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae
  SourcePackage: pulseaudio
  Uname: Linux 2.6.31-17-generic-pae i686

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

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


[Desktop-packages] [Bug 1711087] [NEW] ad2p sink profile mic not available

2017-08-16 Thread Jeroen
Public bug reported:

I have a bose soundsport bluetooth headset. When I select the ad2p sink
profile there is no microphone available. Only with the HSP profile my
microphone is available.

It's really annoying to have to switch between profiles to make a call
or to listen to normal quality music.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: pulseaudio 1:10.0-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  jeroen 3801 F pulseaudio
 /dev/snd/controlC0:  jeroen 3801 F pulseaudio
CurrentDesktop: KDE
Date: Wed Aug 16 11:02:37 2017
InstallationDate: Installed on 2017-05-10 (98 days ago)
InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/15/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E1773IMS.106
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MS-1773
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:0.B
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
dmi.product.name: GS70 2QE
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


** Tags: amd64 apport-bug zesty

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

Title:
  ad2p sink profile mic not available

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a bose soundsport bluetooth headset. When I select the ad2p
  sink profile there is no microphone available. Only with the HSP
  profile my microphone is available.

  It's really annoying to have to switch between profiles to make a call
  or to listen to normal quality music.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jeroen 3801 F pulseaudio
   /dev/snd/controlC0:  jeroen 3801 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Aug 16 11:02:37 2017
  InstallationDate: Installed on 2017-05-10 (98 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1773IMS.106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1773
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.name: GS70 2QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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


[Desktop-packages] [Bug 508522] Re: Mic is not available with A2DP Bluetooth profile

2017-08-16 Thread Jeroen
I'm on kubuntu 17.04 with pulseaudio 10.0, I'm still having this issue.
Is this a kubuntu only issue?

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

Title:
  Mic is not available with A2DP Bluetooth profile

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: pulseaudio

  I'm testing a Nokia BH-905i headset (see 
http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The 
Bluetooth module correctly identifies the headset and the both audio profiles 
"HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music 
playback only A2DP is suitable (HSP/HFP sounds like listening to music played 
through an old telephone). A2DP does not have an INPUT mode, so use of the 
headset for VoiP isn't possible.
  What would be needed is a separate selection to allow to select A2DP for 
output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do 
that (or they switch on the fly?).

  Formal structure:
  1) Ubuntu 10.10
  2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1
  consisting og pluseaudio, pulseaudio-esound-compat, 
pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, 
pulseaudio-utils
  3) Select high quality audio output and still use the Bluetooth microphone
  4) Had to choose: either high quality audio or "telephone quality" with 
microphone

  I can change the profile without the Bluetooth connection dropping,
  but that's ridiculous. E.g. listening to music, a call comes in. Then
  I would need to switch the profile before answering. Please note that
  in Windows, Mac OS, iOS, Android, and Windows Mobile it's done
  automatically.

  Check out attached screencast.

  ProblemType: Bug
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oivasyuv   2309 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17'
     Mixer name : 'Analog Devices AD1984A'
     Components : 'HDA:11d4194a,103c30e8,00100400'
     Controls  : 22
     Simple ctrls  : 14
  Date: Sat Jan 16 22:31:41 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: pulseaudio 1:0.9.19-0ubuntu4
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae
  SourcePackage: pulseaudio
  Uname: Linux 2.6.31-17-generic-pae i686

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

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


[Desktop-packages] [Bug 975749] Re: writer mail merge cannot select address book

2017-05-01 Thread Jeroen Hoek
*** This bug is a duplicate of bug 986205 ***
https://bugs.launchpad.net/bugs/986205

This is still an issue with Ubuntu 16.04. Without the full LibreOffice
package Writer will crash without any message when you try to add a
database for a mail merge.

Can someone remove the duplicate tag?

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

Title:
  writer mail merge cannot select address book

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  When starting the Mail Merge Wizard in LibreOffice Writer. I get to
  stage 3 (select address list). When I click the Select Address List
  button I presented with the following error:

  Loading Component Library Failed:
  file:///usr/lib/libreoffice/program/.../program/libdbalo.so

  I was hoping to be able t oselect an address list, but it never
  happened.

  Version Details:
  LibreOffice 3.5.1.2 
  Build ID: 350m1(Build:102)

  OS:
  Ubuntu 12.04 beta 2 x64

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Sat Apr  7 18:20:13 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   LANGUAGE=en_NZ:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to precise on 2012-04-06 (0 days ago)

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

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


[Desktop-packages] [Bug 1504792] Re: nm applet displays inaccurate notification when user disconnects from VPN

2017-04-10 Thread Jeroen Hoek
I am seeing this behaviour since the 'Disconnect from VPN' menu entry
was removed. Was that removal intentionally? It used to be possible to
click that (which disconnected the VPN connection without this
'Connection Failed' message).

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

Title:
  nm applet displays inaccurate notification when user disconnects from
  VPN

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

Bug description:
  When the user voluntarily disconnects from a vpn connection, network
  manager displays the error message  "VPN Connection Failed." See the
  attached screenshot. However, since a disconnection in this case is a
  success, not a failure, something more neutral like "Successfully
  disconnected" would be more appropriate.

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

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


[Desktop-packages] [Bug 1631095] Re: pushed dns servers not being used

2017-04-03 Thread Jeroen Hoek
This issue is now present in 16.04 as well. As Matthew mentions, the
first time you connect to a VPN with OpenVPN DNS works, the second time
it doesn't.

In case anyone stumbles upon this issue, this workaround (restarting
dnsmasq) makes name resolution work again for a single VPN session:

sudo pkill dnsmasq

You can execute it either before or after the VPN connection is made.

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

Title:
  pushed dns servers not being used

Status in network-manager-openvpn package in Ubuntu:
  Confirmed

Bug description:
  After the upgrade from yenial to yakkety, the internal DNS servers
  (pushed by the openvpn server) are not being used by dnsmasq.

  Symptom:

  I connect via openvpn (called from network manager), the connection is
  established successfully but INTERNAL hostnames cannot be resolved.

  The system itself is using dnsmasq.

  I then have to kill the running dnsmasq instance. After it's been
  (automagically) restarted, internal DNS names can be resolved.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager-openvpn 1.1.93-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Oct  6 20:06:33 2016
  InstallationDate: Installed on 2014-02-07 (972 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: Upgraded to yakkety on 2016-10-01 (5 days ago)

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

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


[Desktop-packages] [Bug 1633003] [NEW] (Cisco) VPN name resolution breaks after upgrade to 1.2.2-0ubuntu0.16.04.3

2016-10-13 Thread Jeroen Ruigrok van der Werven
Public bug reported:

After upgrading my 16.04 installation today I noticed my VPN sessions
suddenly had no name resolution anymore.

Digging through /var/log/apt/history.log I noticed these were the
updates:

Start-Date: 2016-10-13  09:00:37
Commandline: apt dist-upgrade
Requested-By: jeroenr (1000)
Upgrade: libnm-glib4:amd64 (1.2.2-0ubuntu0.16.04.1, 1.2.2-0ubuntu0.16.04.3), 
libsystemd0:amd64 (229-4ubuntu10, 229-4ubuntu11), libsystemd0:i386 
(229-4ubuntu10, 229-4ubuntu11), libdbusmenu-glib4:amd64 
(12.10.3+16.04.20160223.1-0ubuntu1, 16.04.1+16.04.20160927-0ubuntu1), 
google-chrome-stable:amd64 (53.0.2785.143-1, 54.0.2840.59-1), 
libnm-glib-vpn1:amd64 (1.2.2-0ubuntu0.16.04.1, 1.2.2-0ubuntu0.16.04.3), 
udev:amd64 (229-4ubuntu10, 229-4ubuntu11), libnm0:amd64 
(1.2.2-0ubuntu0.16.04.1, 1.2.2-0ubuntu0.16.04.3), network-manager:amd64 
(1.2.2-0ubuntu0.16.04.1, 1.2.2-0ubuntu0.16.04.3), libdbusmenu-gtk4:amd64 
(12.10.3+16.04.20160223.1-0ubuntu1, 16.04.1+16.04.20160927-0ubuntu1), kbd:amd64 
(1.15.5-1ubuntu4, 1.15.5-1ubuntu5), libudev1:amd64 (229-4ubuntu10, 
229-4ubuntu11), libudev1:i386 (229-4ubuntu10, 229-4ubuntu11), libnm-util2:amd64 
(1.2.2-0ubuntu0.16.04.1, 1.2.2-0ubuntu0.16.04.3), libappstream-glib8:amd64 
(0.5.13-1ubuntu3, 0.5.13-1ubuntu4), gnome-calculator:amd64 (1:3.18.3-0ubuntu1, 
1:3.18.3-0ub
 untu1.16.04.1), systemd-sysv:amd64 (229-4ubuntu10, 229-4ubuntu11), 
libpam-systemd:amd64 (229-4ubuntu10, 229-4ubuntu11), systemd:amd64 
(229-4ubuntu10, 229-4ubuntu11), gir1.2-dbusmenu-glib-0.4:amd64 
(12.10.3+16.04.20160223.1-0ubuntu1, 16.04.1+16.04.20160927-0ubuntu1), 
libdbusmenu-gtk3-4:amd64 (12.10.3+16.04.20160223.1-0ubuntu1, 
16.04.1+16.04.20160927-0ubuntu1), lightdm:amd64 (1.18.2-0ubuntu2, 
1.18.3-0ubuntu1), liblightdm-gobject-1-0:amd64 (1.18.2-0ubuntu2, 
1.18.3-0ubuntu1)
End-Date: 2016-10-13  09:01:06

After downloading version 1.2.2-0ubuntu0.16.04.1 copies of libnm-glib-
vpn1:amd64 libnm-glib4:amd64 libnm-util2:amd64 libnm0:amd64 network-
manager:amd64 and installing them via: sudo -H dpkg -i *.deb my name
resolution started working again.

Additional information:

% lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04

% apt-cache policy libnm-glib-vpn1 libnm-glib4 libnm-util2 libnm0 
network-manager
libnm-glib-vpn1:
  Installed: 1.2.2-0ubuntu0.16.04.1
  Candidate: 1.2.2-0ubuntu0.16.04.3
  Version table:
 1.2.2-0ubuntu0.16.04.3 500
500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
 *** 1.2.2-0ubuntu0.16.04.1 100
100 /var/lib/dpkg/status
 1.1.93-0ubuntu4 500
500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
libnm-glib4:
  Installed: 1.2.2-0ubuntu0.16.04.1
  Candidate: 1.2.2-0ubuntu0.16.04.3
  Version table:
 1.2.2-0ubuntu0.16.04.3 500
500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
 *** 1.2.2-0ubuntu0.16.04.1 100
100 /var/lib/dpkg/status
 1.1.93-0ubuntu4 500
500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
libnm-util2:
  Installed: 1.2.2-0ubuntu0.16.04.1
  Candidate: 1.2.2-0ubuntu0.16.04.3
  Version table:
 1.2.2-0ubuntu0.16.04.3 500
500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
 *** 1.2.2-0ubuntu0.16.04.1 100
100 /var/lib/dpkg/status
 1.1.93-0ubuntu4 500
500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
libnm0:
  Installed: 1.2.2-0ubuntu0.16.04.1
  Candidate: 1.2.2-0ubuntu0.16.04.3
  Version table:
 1.2.2-0ubuntu0.16.04.3 500
500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
 *** 1.2.2-0ubuntu0.16.04.1 100
100 /var/lib/dpkg/status
 1.1.93-0ubuntu4 500
500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
network-manager:
  Installed: 1.2.2-0ubuntu0.16.04.1
  Candidate: 1.2.2-0ubuntu0.16.04.3
  Version table:
 1.2.2-0ubuntu0.16.04.3 500
500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
 *** 1.2.2-0ubuntu0.16.04.1 100
100 /var/lib/dpkg/status
 1.1.93-0ubuntu4 500
500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
% apt-cache policy vpnc   
vpnc:
  Installed: 0.5.3r550-2build1
  Candidate: 0.5.3r550-2build1
  Version table:
 *** 0.5.3r550-2build1 500
500 http://nl.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
100 /var/lib/dpkg/status


Expected
After updating that connecting to my existing and working Cisco VPN would work

What happened
Name resolution failed. Could not ping hosts over VPN anymore.

Most likely cause
It seems that /etc/resolv.conf is not getting the search argument added to the 
file anymore. With .3 installed I only had a nameserver 127.0.0.1 line. Now 
with .1 installed I see that I have both that nameserver 127.0.0.1 line as well 
as search 

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification b

[Desktop-packages] [Bug 1625790] [NEW] Cannot enter character via shift-ctrl-u shortcut

2016-09-20 Thread Jeroen Hoek
Public bug reported:

In most Gnome applications I can use shift-ctrl-u to directly enter a
character via its Unicode codepoint. So, for example, to enter the
character € via this method, one does:

shift-ctrl-u 2 0 A C enter

This works in gedit and gnome-terminal today.

I use this often in gucharmap when dealing with a character I don't
recognize, and can't easily directly copy from the source. Since
updating to Ubuntu 16.04, the gucharmap version shipped with Ubuntu has
started to ignore the shift-ctrl-u shortcut in the search text field.

Upstream reports that this appears to be a Ubuntu specific issue:

https://bugzilla.gnome.org/show_bug.cgi?id=769327

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gucharmap 1:3.18.2-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Sep 20 21:55:13 2016
InstallationDate: Installed on 2014-09-16 (735 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: gucharmap
UpgradeStatus: Upgraded to xenial on 2016-05-26 (117 days ago)

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


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

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

Title:
  Cannot enter character via shift-ctrl-u shortcut

Status in gucharmap package in Ubuntu:
  New

Bug description:
  In most Gnome applications I can use shift-ctrl-u to directly enter a
  character via its Unicode codepoint. So, for example, to enter the
  character € via this method, one does:

  shift-ctrl-u 2 0 A C enter

  This works in gedit and gnome-terminal today.

  I use this often in gucharmap when dealing with a character I don't
  recognize, and can't easily directly copy from the source. Since
  updating to Ubuntu 16.04, the gucharmap version shipped with Ubuntu
  has started to ignore the shift-ctrl-u shortcut in the search text
  field.

  Upstream reports that this appears to be a Ubuntu specific issue:

  https://bugzilla.gnome.org/show_bug.cgi?id=769327

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gucharmap 1:3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep 20 21:55:13 2016
  InstallationDate: Installed on 2014-09-16 (735 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: gucharmap
  UpgradeStatus: Upgraded to xenial on 2016-05-26 (117 days ago)

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

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


[Desktop-packages] [Bug 572628] Re: "Liyama" spelling error

2016-05-23 Thread Jeroen Hoek
The patch I sent was ultimately accepted upstream. 'Liyama' should now
be spelled as 'Iiyama' on system's using this database.

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

Title:
  "Liyama" spelling error

Status in gnome-desktop:
  Invalid
Status in gnome-desktop3 package in Ubuntu:
  Invalid
Status in hwdata package in Ubuntu:
  New

Bug description:
  Binary package hint: gnome-control-center

  Lucid final release amd64 alternate install CD
  iiyama ProLite H511S LCD monitor

  gnome-control-center1:2.30.0-0ubuntu4

  Preferences -> Monitors brings up a green box containing the text
  "Liyama North America 20". It should be iiyama, not Liyama. (And FWIW
  the monitor was purchased in England.)

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

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


[Desktop-packages] [Bug 1455097] Re: /etc/pm/sleep.d/ is no more processed

2016-04-06 Thread Jeroen Massar
On 2016-04-06 17:46, ChristianEhrhardt wrote:
> I did the task of identifying the remaining packages that are affected.
> 
> $ apt-file search /etc/pm/sleep.d/
> 
> aiccu: /etc/pm/sleep.d/60aiccu

There has been a bug out for this for 4 years already that this should
never ever have existed:

 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689584

Short version: please remove any kind of trace from /etc/pm/sleep.d for
aiccu.

That should take care of your bug report for aiccu at least.

Greets,
 Jeroen


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

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

Title:
  /etc/pm/sleep.d/ is no more processed

Status in aiccu package in Ubuntu:
  New
Status in ceph package in Ubuntu:
  New
Status in grub2 package in Ubuntu:
  New
Status in ifplugd package in Ubuntu:
  New
Status in lizardfs package in Ubuntu:
  New
Status in oss4 package in Ubuntu:
  New
Status in pm-utils package in Ubuntu:
  Won't Fix
Status in toshset package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  I added a new script in /etc/pm/sleep.d/ that worked fine before the
  upgrade to vivid. I was wondering why it doesn't work and I find out
  that /var/log/pm-suspend.log is empty, and pm-powersave.log too (last
  logs from pm-suspend were on Apr 28, when I upgraded from utopic to
  vivid.

  The laptop suspends and wakes fine, it just seems that no pm scripts
  are run after suspend/powersave.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: pm-utils 1.4.1-15
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 14 15:36:26 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-03-12 (792 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1516153] Re: Wifi does not work after suspending.

2015-11-14 Thread Jeroen Mathon
** Description changed:

  After resuming from a suspend, sometimes(very often) the wifi does not show 
any connections.
  Even if i uncheck and recheck the Enable wifi checkbox it still does not show 
any connections.
  
  I am using Ubuntu 15.10.
  NetworkManager is at version 1.0.4.
  
  My hardware is a Asus X750J.
+ 
+ A quick workaround is restarting the NetworkManager service.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: network-manager 1.0.4-0ubuntu5.1
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  Date: Fri Nov 13 22:07:24 2015
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig:
-  # interfaces(5) file used by ifup(8) and ifdown(8)
-  auto lo
-  iface lo inet loopback
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
  InstallationDate: Installed on 2015-10-27 (17 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NetworkManager.state:
-  [main]
-  NetworkingEnabled=true
-  WirelessEnabled=true
-  WWANEnabled=true
-  WimaxEnabled=true
+  [main]
+  NetworkingEnabled=true
+  WirelessEnabled=true
+  WWANEnabled=true
+  WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
-  DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
-  enp3s0  ethernet  connected /org/freedesktop/NetworkManager/Devices/0  
Wired connection 1  a6283be3-2692-4d49-87d6-4c2f7cf00e2f  
/org/freedesktop/NetworkManager/ActiveConnection/4 
-  tun0tun   connected /org/freedesktop/NetworkManager/Devices/3  
tun08a335ba2-ebce-4e08-9431-d8a4322cfa26  
/org/freedesktop/NetworkManager/ActiveConnection/5 
-  wlp2s0  wifi  disconnected  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
-  lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
+  DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
+  enp3s0  ethernet  connected /org/freedesktop/NetworkManager/Devices/0  
Wired connection 1  a6283be3-2692-4d49-87d6-4c2f7cf00e2f  
/org/freedesktop/NetworkManager/ActiveConnection/4
+  tun0tun   connected /org/freedesktop/NetworkManager/Devices/3  
tun08a335ba2-ebce-4e08-9431-d8a4322cfa26  
/org/freedesktop/NetworkManager/ActiveConnection/5
+  wlp2s0  wifi  disconnected  /org/freedesktop/NetworkManager/Devices/2  
--  ----
+  lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

Title:
  Wifi does not work after suspending.

Status in network-manager package in Ubuntu:
  New

Bug description:
  After resuming from a suspend, sometimes(very often) the wifi does not show 
any connections.
  Even if i uncheck and recheck the Enable wifi checkbox it still does not show 
any connections.

  I am using Ubuntu 15.10.
  NetworkManager is at version 1.0.4.

  My hardware is a Asus X750J.

  A quick workaround is restarting the NetworkManager service.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: network-manager 1.0.4-0ubuntu5.1
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  Date: Fri Nov 13 22:07:24 2015
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-27 (17 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   enp3s0  ethernet  connected /org/freedesktop/NetworkManager/Devices/0  
Wired connection 1  a6283be3-2692-4d49-87d6-4c2f7cf00e2f  
/org/freedesktop/NetworkManager/ActiveConnection

[Desktop-packages] [Bug 1516153] [NEW] Wifi does not work after suspending.

2015-11-13 Thread Jeroen Mathon
Public bug reported:

After resuming from a suspend, sometimes(very often) the wifi does not show any 
connections.
Even if i uncheck and recheck the Enable wifi checkbox it still does not show 
any connections.

I am using Ubuntu 15.10.
NetworkManager is at version 1.0.4.

My hardware is a Asus X750J.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: network-manager 1.0.4-0ubuntu5.1
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
Date: Fri Nov 13 22:07:24 2015
ExecutablePath: /usr/sbin/NetworkManager
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2015-10-27 (17 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 enp3s0  ethernet  connected /org/freedesktop/NetworkManager/Devices/0  
Wired connection 1  a6283be3-2692-4d49-87d6-4c2f7cf00e2f  
/org/freedesktop/NetworkManager/ActiveConnection/4 
 tun0tun   connected /org/freedesktop/NetworkManager/Devices/3  
tun08a335ba2-ebce-4e08-9431-d8a4322cfa26  
/org/freedesktop/NetworkManager/ActiveConnection/5 
 wlp2s0  wifi  disconnected  /org/freedesktop/NetworkManager/Devices/2  --  
----
 
 lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  --  
----
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: 
Error: Object 'nm' is unknown, try 'nmcli help'.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wily

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

Title:
  Wifi does not work after suspending.

Status in network-manager package in Ubuntu:
  New

Bug description:
  After resuming from a suspend, sometimes(very often) the wifi does not show 
any connections.
  Even if i uncheck and recheck the Enable wifi checkbox it still does not show 
any connections.

  I am using Ubuntu 15.10.
  NetworkManager is at version 1.0.4.

  My hardware is a Asus X750J.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: network-manager 1.0.4-0ubuntu5.1
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  Date: Fri Nov 13 22:07:24 2015
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-27 (17 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   enp3s0  ethernet  connected /org/freedesktop/NetworkManager/Devices/0  
Wired connection 1  a6283be3-2692-4d49-87d6-4c2f7cf00e2f  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   tun0tun   connected /org/freedesktop/NetworkManager/Devices/3  
tun08a335ba2-ebce-4e08-9431-d8a4322cfa26  
/org/freedesktop/NetworkManager/ActiveConnection/5 
   wlp2s0  wifi  disconnected  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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


[Desktop-packages] [Bug 269441] Re: Trash always full

2015-10-30 Thread Jeroen Mathon
This problem persists in 15.10.
Someone seriously needs to fix this.

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

Title:
  Trash always full

Status in gnome-applets package in Ubuntu:
  Confirmed

Bug description:
  I've seen other users having problems with that the trash appears
  empty even though it isn't. I have the opposite problem: my trash icon
  on the desktop always appears full, even if empty.

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

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


[Desktop-packages] [Bug 1498274] Re: init.d script doesn't respect `version` argument

2015-09-24 Thread Jeroen de Vries
** Attachment added: "supporting init.d-functions script"
   
https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1498274/+attachment/4473744/+files/init.d-functions

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

Title:
  init.d script doesn't respect `version` argument

Status in postgresql-common package in Ubuntu:
  Confirmed

Bug description:
  Release: Ubuntu 15.04

  It seems that the current version of the /etc/init.d/postgresql script
  doesn't respect the `version` flag.  Help text states:

  Usage: /etc/init.d/postgresql {start|stop|restart|reload|force-
  reload|status} [version ..]

  But with 2 installations and called as follows:

  /etc/init.d/postgresql start 9.4

  or

 service postgresql start 9.4

  Both 9.4 and 9.3 are started, I expected just 9.4 to start.

  
  Package info:
  # apt-cache policy postgresql-common
  postgresql-common:
Installed: 169.pgdg14.04+1
Candidate: 169.pgdg70+1
Version table:
   169.pgdg70+1 0
  500 http://apt.postgresql.org/pub/repos/apt/ wheezy-pgdg/main amd64 
Packages
   *** 169.pgdg14.04+1 0
  100 /var/lib/dpkg/status
   166bzr2 0
  500 http://mirror.hetzner.de/ubuntu/packages/ vivid/main amd64 
Packages
  500 http://de.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages

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

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


[Desktop-packages] [Bug 1498274] Re: init.d script doesn't respect `version` argument

2015-09-24 Thread Jeroen de Vries
Hi Eoghan,

I found out that the service start, stop and status commands are
interfering with the start(), stop() and status() functions defined in
the /usr/share/postgresql-common/init.d-functions script which is loaded
from /etc/init.d/postgresql

You can have the scripts changed to use commands like pgstart instead of
start then it works. See attached scripts.


** Attachment added: "init.d script"
   
https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1498274/+attachment/4473743/+files/postgresql

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

Title:
  init.d script doesn't respect `version` argument

Status in postgresql-common package in Ubuntu:
  Confirmed

Bug description:
  Release: Ubuntu 15.04

  It seems that the current version of the /etc/init.d/postgresql script
  doesn't respect the `version` flag.  Help text states:

  Usage: /etc/init.d/postgresql {start|stop|restart|reload|force-
  reload|status} [version ..]

  But with 2 installations and called as follows:

  /etc/init.d/postgresql start 9.4

  or

 service postgresql start 9.4

  Both 9.4 and 9.3 are started, I expected just 9.4 to start.

  
  Package info:
  # apt-cache policy postgresql-common
  postgresql-common:
Installed: 169.pgdg14.04+1
Candidate: 169.pgdg70+1
Version table:
   169.pgdg70+1 0
  500 http://apt.postgresql.org/pub/repos/apt/ wheezy-pgdg/main amd64 
Packages
   *** 169.pgdg14.04+1 0
  100 /var/lib/dpkg/status
   166bzr2 0
  500 http://mirror.hetzner.de/ubuntu/packages/ vivid/main amd64 
Packages
  500 http://de.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages

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

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


[Desktop-packages] [Bug 1498274] Re: init.d script doesn't respect `version` argument

2015-09-24 Thread Jeroen de Vries
** Changed in: postgresql-common (Ubuntu)
   Status: New => Confirmed

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

Title:
  init.d script doesn't respect `version` argument

Status in postgresql-common package in Ubuntu:
  Confirmed

Bug description:
  Release: Ubuntu 15.04

  It seems that the current version of the /etc/init.d/postgresql script
  doesn't respect the `version` flag.  Help text states:

  Usage: /etc/init.d/postgresql {start|stop|restart|reload|force-
  reload|status} [version ..]

  But with 2 installations and called as follows:

  /etc/init.d/postgresql start 9.4

  or

 service postgresql start 9.4

  Both 9.4 and 9.3 are started, I expected just 9.4 to start.

  
  Package info:
  # apt-cache policy postgresql-common
  postgresql-common:
Installed: 169.pgdg14.04+1
Candidate: 169.pgdg70+1
Version table:
   169.pgdg70+1 0
  500 http://apt.postgresql.org/pub/repos/apt/ wheezy-pgdg/main amd64 
Packages
   *** 169.pgdg14.04+1 0
  100 /var/lib/dpkg/status
   166bzr2 0
  500 http://mirror.hetzner.de/ubuntu/packages/ vivid/main amd64 
Packages
  500 http://de.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages

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

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


[Desktop-packages] [Bug 1498274] Re: init.d script doesn't respect `version` argument

2015-09-24 Thread Jeroen de Vries
Hi Eoghan,

I could reproduce the situation. First installed Postgres 9.3 then 9.4.
ps shows both versions running.

I looked at the /etc/init.d/postgresql script and the status command would 
effectively execute this:
echo "`pg_lsclusters -h`" | awk 'BEGIN {rc=0} {if (match($4, "down")) rc=3; 
printf ("%s/%s (port %s): %s\n", $1, $2, $3, $4)}; END {exit rc}'

which should result in this output:
9.3/main (port 5432): online
9.4/main (port 5433): online

but instead running '/etc/init.d/postgresql status' outputs this:
● postgresql.service - PostgreSQL RDBMS
   Loaded: loaded (/lib/systemd/system/postgresql.service; enabled; vendor 
preset: enabled)
   Active: active (exited) since Thu 2015-09-24 10:28:20 UTC; 3min 13s ago
  Process: 851 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
 Main PID: 851 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/postgresql.service


Looks like Upstart is taking over somewhere and may indeed not honour the extra 
options like the version number.

I am not sure if this is really a bug or not. It is at least not
behaving as you would expect from what you read in the script.

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

Title:
  init.d script doesn't respect `version` argument

Status in postgresql-common package in Ubuntu:
  New

Bug description:
  Release: Ubuntu 15.04

  It seems that the current version of the /etc/init.d/postgresql script
  doesn't respect the `version` flag.  Help text states:

  Usage: /etc/init.d/postgresql {start|stop|restart|reload|force-
  reload|status} [version ..]

  But with 2 installations and called as follows:

  /etc/init.d/postgresql start 9.4

  or

 service postgresql start 9.4

  Both 9.4 and 9.3 are started, I expected just 9.4 to start.

  
  Package info:
  # apt-cache policy postgresql-common
  postgresql-common:
Installed: 169.pgdg14.04+1
Candidate: 169.pgdg70+1
Version table:
   169.pgdg70+1 0
  500 http://apt.postgresql.org/pub/repos/apt/ wheezy-pgdg/main amd64 
Packages
   *** 169.pgdg14.04+1 0
  100 /var/lib/dpkg/status
   166bzr2 0
  500 http://mirror.hetzner.de/ubuntu/packages/ vivid/main amd64 
Packages
  500 http://de.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages

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

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


[Desktop-packages] [Bug 1498274] Re: init.d script doesn't respect `version` argument

2015-09-23 Thread Jeroen de Vries
Hi Eoghan,


Can you explain how do you see both 9.4 and 9.3 are started? Which command or 
logs are you using or checking?

You state you are running on Ubuntu 15.04 which did not ship with
Postgres 9.3, can you explain how you got postgresql 9.3 on this Ubuntu
release?

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

Title:
  init.d script doesn't respect `version` argument

Status in postgresql-common package in Ubuntu:
  New

Bug description:
  Release: Ubuntu 15.04

  It seems that the current version of the /etc/init.d/postgresql script
  doesn't respect the `version` flag.  Help text states:

  Usage: /etc/init.d/postgresql {start|stop|restart|reload|force-
  reload|status} [version ..]

  But with 2 installations and called as follows:

  /etc/init.d/postgresql start 9.4

  or

 service postgresql start 9.4

  Both 9.4 and 9.3 are started, I expected just 9.4 to start.

  
  Package info:
  # apt-cache policy postgresql-common
  postgresql-common:
Installed: 169.pgdg14.04+1
Candidate: 169.pgdg70+1
Version table:
   169.pgdg70+1 0
  500 http://apt.postgresql.org/pub/repos/apt/ wheezy-pgdg/main amd64 
Packages
   *** 169.pgdg14.04+1 0
  100 /var/lib/dpkg/status
   166bzr2 0
  500 http://mirror.hetzner.de/ubuntu/packages/ vivid/main amd64 
Packages
  500 http://de.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages

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

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


[Desktop-packages] [Bug 1481178] [NEW] nvidia-331-updates-uvm 331.113-0ubuntu0.1: nvidia-331-updates-uvm kernel module failed to build

2015-08-03 Thread Jeroen T. Vermeulen
Public bug reported:

Laptop insisted on upgrade from 14.10 to 15.04 on the day before travel.
Took hours, so I let it upgrade overnight.  Partway through it got stuck
on some pointless press-OK-to-acknowledge dialog, so it wasn't done the
following morning; there was no way to stop the upgrade and suspend
didn't work, so I had to turn the machine off while it was installing.
After that, things were of course broken to the point where they need
hours more of work in the shell to fix up and complete the upgrade.
This is one of several crashes which occurred while completing the
upgrade.

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: nvidia-331-updates-uvm 331.113-0ubuntu0.1
ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
Uname: Linux 3.16.0-44-generic i686
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: i386
DKMSBuildLog:
 DKMS make.log for nvidia-331-updates-uvm-331.113 for kernel 3.19.0-25-generic 
(i686)
 Tue Aug  4 12:50:38 ICT 2015
 Makefile:216: 
/var/lib/dkms/nvidia-331-updates/331.113/build/nvidia-modules-common.mk: No 
such file or directory
 make: *** No rule to make target 
'/var/lib/dkms/nvidia-331-updates/331.113/build/nvidia-modules-common.mk'.  
Stop.
DKMSKernelVersion: 3.19.0-25-generic
Date: Tue Aug  4 12:50:46 2015
InstallationDate: Installed on 2012-11-27 (979 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
PackageVersion: 331.113-0ubuntu0.1
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt  1.0.9.7ubuntu4.1
SourcePackage: nvidia-graphics-drivers-331-updates
Title: nvidia-331-updates-uvm 331.113-0ubuntu0.1: nvidia-331-updates-uvm kernel 
module failed to build
UpgradeStatus: Upgraded to vivid on 2015-08-01 (2 days ago)

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


** Tags: apport-package i386 vivid

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

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

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

Bug description:
  Laptop insisted on upgrade from 14.10 to 15.04 on the day before
  travel.  Took hours, so I let it upgrade overnight.  Partway through
  it got stuck on some pointless press-OK-to-acknowledge dialog, so it
  wasn't done the following morning; there was no way to stop the
  upgrade and suspend didn't work, so I had to turn the machine off
  while it was installing.  After that, things were of course broken to
  the point where they need hours more of work in the shell to fix up
  and complete the upgrade.  This is one of several crashes which
  occurred while completing the upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: nvidia-331-updates-uvm 331.113-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic i686
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: i386
  DKMSBuildLog:
   DKMS make.log for nvidia-331-updates-uvm-331.113 for kernel 
3.19.0-25-generic (i686)
   Tue Aug  4 12:50:38 ICT 2015
   Makefile:216: 
/var/lib/dkms/nvidia-331-updates/331.113/build/nvidia-modules-common.mk: No 
such file or directory
   make: *** No rule to make target 
'/var/lib/dkms/nvidia-331-updates/331.113/build/nvidia-modules-common.mk'.  
Stop.
  DKMSKernelVersion: 3.19.0-25-generic
  Date: Tue Aug  4 12:50:46 2015
  InstallationDate: Installed on 2012-11-27 (979 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  PackageVersion: 331.113-0ubuntu0.1
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.1
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates-uvm 331.113-0ubuntu0.1: nvidia-331-updates-uvm 
kernel module failed to build
  UpgradeStatus: Upgraded to vivid on 2015-08-01 (2 days ago)

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

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


[Desktop-packages] [Bug 1371274] Re: Unable to use the widevine plugin with Chromium

2015-05-11 Thread Jeroen
sudo cp /opt/google/chrome-beta/libwidevinecdm* /usr/lib/chromium-
browser/

Installed your ppa, upgraded, no effect

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

Title:
  Unable to use the widevine plugin with Chromium

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  Chromium is unable to use the widevine component from google chrome :
  libwidevinecdmadapter.so and libwidevinecdm.so

  How to reproduce :

  - copy the 2 files the chrome archive in /usr/lib/chromium-browser
  - check chrome://components/
  - Widevine does not appear

  it seems widevine support is only activated when branding=chrome

  as seen in

  
  
https://github.com/scheib/chromium/blob/master/third_party/widevine/cdm/widevine_cdm.gyp

  Widevine support would enable EME playing such as Netflix

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 37.0.2062.94-0ubuntu0.14.04.1~pkg1042
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Thu Sep 18 21:11:17 2014
  InstallationDate: Installed on 2013-10-02 (350 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: chromium-browser
  SystemImageInfo: Error: [Errno 2] Aucun fichier ou dossier de ce type: 
'system-image-cli'
  UpgradeStatus: Upgraded to trusty on 2014-05-31 (109 days ago)
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-06-01T14:14:23.245932

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

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


[Desktop-packages] [Bug 1437765] [NEW] No desktop after upgrade to 14.10

2015-03-28 Thread Jeroen T. Vermeulen
Public bug reported:

After upgrading my desktop machine from 14.04 to 14.10, I no longer have
a desktop.  The login screen works, but after logging in, I get just the
backdrop image and a mouse pointer.  Nothing else.

The pointer responds to mouse movements, and I can switch to a text
console using ctrl-alt-F, which is how I installed KDE in order to
file this bug.  But I can no longer open a terminal with ctrl-alt-T, or
switch workspaces with ctrl-alt-.

My .xsession-errors after logging in showed:

X Error of failed request:  BadRequest (invalid request code or no such 
operation)
  Major opcode of failed request:  155 (GLX)
  Minor opcode of failed request:  19 (X_GLXQueryServerString)
  Serial number of failed request:  22
  Current serial number in output stream:  22
openConnection: connect: No such file or directory
cannot connect to brltty at :0
Script for ibus started at run_im.
Script for auto started at run_im.
Script for default started at run_im.
upstart: hud main process (2389) terminated with status 1
upstart: unity-settings-daemon main process (2393) terminated with status 1
upstart: unity7 main process (2405) terminated with status 1
upstart: gnome-session (Unity) main process (2411) terminated with status 1
upstart: unity-panel-service main process (2422) terminated with status 1
upstart: indicator-keyboard main process (2496) terminated with status 1
upstart: indicator-printers main process (2502) terminated with status 1
upstart: upstart-dbus-session-bridge main process (2366) terminated with status 
1
upstart: indicator-bluetooth main process (2485) killed by TERM signal
upstart: indicator-power main process (2486) killed by TERM signal
upstart: indicator-datetime main process (2494) killed by TERM signal
upstart: indicator-sound main process (2501) killed by TERM signal
upstart: indicator-session main process (2503) killed by TERM signal
upstart: indicator-application main process (2536) killed by TERM signal
upstart: Disconnected from notified D-Bus bus

This is quite a slow machine, so normally it'd take a while to complete
a graphical login.  But now, when I log in and immediately switch to a
graphical console to run "top," it doesn't show much going on.  External
filesystem volumes are not auto-mounted under /media the way they
usually are.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: unity 7.3.1+14.10.20141016-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7
Uname: Linux 3.16.0-33-generic i686
NonfreeKernelModules: fglrx
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: KDE
Date: Sun Mar 29 09:23:52 2015
InstallationDate: Installed on 2012-11-25 (853 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
SourcePackage: unity
UpgradeStatus: Upgraded to utopic on 2015-03-28 (0 days ago)

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


** Tags: apport-bug i386 utopic

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

Title:
  No desktop after upgrade to 14.10

Status in unity package in Ubuntu:
  New

Bug description:
  After upgrading my desktop machine from 14.04 to 14.10, I no longer
  have a desktop.  The login screen works, but after logging in, I get
  just the backdrop image and a mouse pointer.  Nothing else.

  The pointer responds to mouse movements, and I can switch to a text
  console using ctrl-alt-F, which is how I installed KDE in order to
  file this bug.  But I can no longer open a terminal with ctrl-alt-T,
  or switch workspaces with ctrl-alt-.

  My .xsession-errors after logging in showed:

  X Error of failed request:  BadRequest (invalid request code or no such 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  19 (X_GLXQueryServerString)
Serial number of failed request:  22
Current serial number in output stream:  22
  openConnection: connect: No such file or directory
  cannot connect to brltty at :0
  Script for ibus started at run_im.
  Script for auto started at run_im.
  Script for default started at run_im.
  upstart: hud main process (2389) terminated with status 1
  upstart: unity-settings-daemon main process (2393) terminated with status 1
  upstart: unity7 main process (2405) terminated with status 1
  upstart: gnome-session (Unity) main process (2411) terminated with status 1
  upstart: unity-panel-service main process (2422) terminated with status 1
  upstart: indicator-keyboard main process (2496) terminated with status 1
  upstart: indicator-printers main process (2502) terminated with status 1
  upstart: upstart-dbus-session-bridge main process (2366) terminated with 
status 1
  upstart: indicator-bluetooth main process (2485) killed by TERM signa

[Desktop-packages] [Bug 1300557] Re: Screen resolution no longer works

2015-03-18 Thread Jeroen T. Vermeulen
The version that was installed on March 31 was 3.13.0.20.24.  The
version I uninstalled right after that was 3.13.0.18.38.

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

Title:
  Screen resolution no longer works

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My display's native resolution is 2560×1440 pixels.  Prior to, I
  think, Saucy I could only reach this resolution by adding it using
  xrandr, and then calling xrandr on boot/login to select that
  resolution.  The Display preferences did not show any higher options
  than 1920×1200.

  In Saucy, the native resolution just worked, and I could stop using
  xrandr.  It also worked in Trusty in the alpha releases, up to (and I
  think including) beta-1.  But today (this is not an April's fool, is
  it?) I rebooted after an upgrade, and found myself back in 1920×1200.
  Again, the Display preferences list that resolution as the highest
  possible.  But this time, attempts to ‘xrandr --addmode’ my native
  resolution failed.

  The error message wasn't very helpful; I'll try to reproduce it later
  but it throws my display into yet a lower resolution that's hard to
  work with.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr  1 09:59:00 2014
  DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2013-08-03 (240 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic 
root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago)
  dmi.bios.date: 05/16/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-D3HP-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z87-D3HP
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  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
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Apr  1 09:52:36 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16510
   vendor DEL
  xserver.version: 2:1.15.0-1ubuntu7

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

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


[Desktop-packages] [Bug 1300557] Re: Screen resolution no longer works

2015-03-12 Thread Jeroen T. Vermeulen
According to the dpkg.log for that date,  quite a lot: libc-bin for
amd64.  Also gcc-4.8, gcc-4.9, along with g++, cpp, libgcc1, libstdc++6
etc, for amd64 and i386; and libitm1, libgomp1, libgfortran3, libasan0,
libatomic1, libtsan0, libquadmath0, libthumbnailer0, apport, apport-gtk,
python3-problem-report, python3-apport, binfmt-support, dh-apport,
libgtk2-perl, python-boto, python-lxml, python3-lxml, unity-webapps-qml,
mobile-broadband-provider-info, python-keystoneclient,

The day before I upgraded among other things libffi6 (for i386 and
amd64) and libffi-dev, dconf-gsettings-backend, dconf-service,
libdconf1, various dconf tools and frontends, libglib2.0-*, libunity-
control-center1 and unity-control-center,  libido3-0.1-0, lxc and
related packages, libapparmor1 and apparmor, libqt5positioning5,
libunity-gtk3-parser0, openjdk-7 and icedtea-7, ubuntu-release-upgrader
and update-manager, libcompizconfig0, compiz-gnome, compiz-plugins-
default, libdecoration0, compiz-core, compiz, im-config, kerneloops-
daemon, indicator-*, unity-scope-*, libreoffice, unity, libunity-
core-6.0.9, unity-services, ubuntu-mono, libvirt, the kernel, and dh-
apparmor.

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

Title:
  Screen resolution no longer works

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My display's native resolution is 2560×1440 pixels.  Prior to, I
  think, Saucy I could only reach this resolution by adding it using
  xrandr, and then calling xrandr on boot/login to select that
  resolution.  The Display preferences did not show any higher options
  than 1920×1200.

  In Saucy, the native resolution just worked, and I could stop using
  xrandr.  It also worked in Trusty in the alpha releases, up to (and I
  think including) beta-1.  But today (this is not an April's fool, is
  it?) I rebooted after an upgrade, and found myself back in 1920×1200.
  Again, the Display preferences list that resolution as the highest
  possible.  But this time, attempts to ‘xrandr --addmode’ my native
  resolution failed.

  The error message wasn't very helpful; I'll try to reproduce it later
  but it throws my display into yet a lower resolution that's hard to
  work with.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr  1 09:59:00 2014
  DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2013-08-03 (240 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic 
root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago)
  dmi.bios.date: 05/16/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-D3HP-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z87-D3HP
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  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
  version.x

[Desktop-packages] [Bug 1300557] Re: Screen resolution no longer works

2015-03-11 Thread Jeroen T. Vermeulen
No change in 15.04.  I can add the resolution with xrandr, and after
that I can use it.  But after reboot, I have to do it again.

The upgrade got stuck with a black screen and no networking, but I
eventually got out of it with the "apt-get dist-upgrade" dance from the
console.  I hope that hasn't messed things up.

It may matter that I've got the monitor's DVI port hooked up to my
computer's HDMI port.  It was the only way to get things working: the
monitor doesn't support its full native resolution on HDMI, and the
Haswell builtin graphics only supports the resolution on HDMI.  But, the
hardware can do it and it used to work from the settings GUI without
hackery.

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

Title:
  Screen resolution no longer works

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My display's native resolution is 2560×1440 pixels.  Prior to, I
  think, Saucy I could only reach this resolution by adding it using
  xrandr, and then calling xrandr on boot/login to select that
  resolution.  The Display preferences did not show any higher options
  than 1920×1200.

  In Saucy, the native resolution just worked, and I could stop using
  xrandr.  It also worked in Trusty in the alpha releases, up to (and I
  think including) beta-1.  But today (this is not an April's fool, is
  it?) I rebooted after an upgrade, and found myself back in 1920×1200.
  Again, the Display preferences list that resolution as the highest
  possible.  But this time, attempts to ‘xrandr --addmode’ my native
  resolution failed.

  The error message wasn't very helpful; I'll try to reproduce it later
  but it throws my display into yet a lower resolution that's hard to
  work with.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr  1 09:59:00 2014
  DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2013-08-03 (240 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic 
root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago)
  dmi.bios.date: 05/16/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-D3HP-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z87-D3HP
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  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
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Apr  1 09:52:36 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16510
   vendor DEL
  xserver.version: 2:1.15.0-1ubuntu7

To manage notifications about this bug go to:
htt

[Desktop-packages] [Bug 1300557] Re: Screen resolution no longer works

2015-03-11 Thread Jeroen T. Vermeulen
I first upgraded to 14.10; that didn't change anything.  Trying 15.04
now.

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

Title:
  Screen resolution no longer works

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My display's native resolution is 2560×1440 pixels.  Prior to, I
  think, Saucy I could only reach this resolution by adding it using
  xrandr, and then calling xrandr on boot/login to select that
  resolution.  The Display preferences did not show any higher options
  than 1920×1200.

  In Saucy, the native resolution just worked, and I could stop using
  xrandr.  It also worked in Trusty in the alpha releases, up to (and I
  think including) beta-1.  But today (this is not an April's fool, is
  it?) I rebooted after an upgrade, and found myself back in 1920×1200.
  Again, the Display preferences list that resolution as the highest
  possible.  But this time, attempts to ‘xrandr --addmode’ my native
  resolution failed.

  The error message wasn't very helpful; I'll try to reproduce it later
  but it throws my display into yet a lower resolution that's hard to
  work with.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr  1 09:59:00 2014
  DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2013-08-03 (240 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic 
root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago)
  dmi.bios.date: 05/16/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-D3HP-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z87-D3HP
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  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
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Apr  1 09:52:36 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16510
   vendor DEL
  xserver.version: 2:1.15.0-1ubuntu7

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

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


[Desktop-packages] [Bug 1300557] Re: Screen resolution no longer works

2015-03-11 Thread Jeroen T. Vermeulen
Something happened to this bug's conversation: the message asking me to
upgrade the BIOS has been removed/hidden.

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

Title:
  Screen resolution no longer works

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My display's native resolution is 2560×1440 pixels.  Prior to, I
  think, Saucy I could only reach this resolution by adding it using
  xrandr, and then calling xrandr on boot/login to select that
  resolution.  The Display preferences did not show any higher options
  than 1920×1200.

  In Saucy, the native resolution just worked, and I could stop using
  xrandr.  It also worked in Trusty in the alpha releases, up to (and I
  think including) beta-1.  But today (this is not an April's fool, is
  it?) I rebooted after an upgrade, and found myself back in 1920×1200.
  Again, the Display preferences list that resolution as the highest
  possible.  But this time, attempts to ‘xrandr --addmode’ my native
  resolution failed.

  The error message wasn't very helpful; I'll try to reproduce it later
  but it throws my display into yet a lower resolution that's hard to
  work with.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr  1 09:59:00 2014
  DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2013-08-03 (240 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic 
root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago)
  dmi.bios.date: 05/16/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-D3HP-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z87-D3HP
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  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
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Apr  1 09:52:36 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16510
   vendor DEL
  xserver.version: 2:1.15.0-1ubuntu7

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

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


[Desktop-packages] [Bug 1300557] Re: Screen resolution no longer works

2015-03-10 Thread Jeroen T. Vermeulen
Okay, I got out of that situation with the help of the flashrom people.
My BIOS is now updated.

It helped a bit in that I can now define and add my resolution again
using xrandr.  It won't stay added though: I need to define and add it
every time I boot.  Otherwise, the resolution is not in the Displays
settings dropdown.

The dmidecode output is:

F7
08/12/2014

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

Title:
  Screen resolution no longer works

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My display's native resolution is 2560×1440 pixels.  Prior to, I
  think, Saucy I could only reach this resolution by adding it using
  xrandr, and then calling xrandr on boot/login to select that
  resolution.  The Display preferences did not show any higher options
  than 1920×1200.

  In Saucy, the native resolution just worked, and I could stop using
  xrandr.  It also worked in Trusty in the alpha releases, up to (and I
  think including) beta-1.  But today (this is not an April's fool, is
  it?) I rebooted after an upgrade, and found myself back in 1920×1200.
  Again, the Display preferences list that resolution as the highest
  possible.  But this time, attempts to ‘xrandr --addmode’ my native
  resolution failed.

  The error message wasn't very helpful; I'll try to reproduce it later
  but it throws my display into yet a lower resolution that's hard to
  work with.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr  1 09:59:00 2014
  DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2013-08-03 (240 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic 
root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago)
  dmi.bios.date: 05/16/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-D3HP-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z87-D3HP
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  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
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Apr  1 09:52:36 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16510
   vendor DEL
  xserver.version: 2:1.15.0-1ubuntu7

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

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


[Desktop-packages] [Bug 1300557] Re: Screen resolution no longer works

2015-03-10 Thread Jeroen T. Vermeulen
I'm trying the BIOS upgrade as per those instructions.  The only
applicable option was the flashrom one, which seems to have hosed my
BIOS.  It's still on now, but I won't be able to boot it again.  Kindly
mark this bug New again to give me time to recover and retry!

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

Title:
  Screen resolution no longer works

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My display's native resolution is 2560×1440 pixels.  Prior to, I
  think, Saucy I could only reach this resolution by adding it using
  xrandr, and then calling xrandr on boot/login to select that
  resolution.  The Display preferences did not show any higher options
  than 1920×1200.

  In Saucy, the native resolution just worked, and I could stop using
  xrandr.  It also worked in Trusty in the alpha releases, up to (and I
  think including) beta-1.  But today (this is not an April's fool, is
  it?) I rebooted after an upgrade, and found myself back in 1920×1200.
  Again, the Display preferences list that resolution as the highest
  possible.  But this time, attempts to ‘xrandr --addmode’ my native
  resolution failed.

  The error message wasn't very helpful; I'll try to reproduce it later
  but it throws my display into yet a lower resolution that's hard to
  work with.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr  1 09:59:00 2014
  DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2013-08-03 (240 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic 
root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago)
  dmi.bios.date: 05/16/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-D3HP-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z87-D3HP
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  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
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Apr  1 09:52:36 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16510
   vendor DEL
  xserver.version: 2:1.15.0-1ubuntu7

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

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


[Desktop-packages] [Bug 1414620] [NEW] Rhythmbox freezes when seeking in m4a files.

2015-01-26 Thread Jeroen Mathon
Public bug reported:

Rhythmbox freezes when i seek forward in a m4a file.
It stops at the timestamp i forward it to.

Ubuntu version: 14.04
Rhythmbox Version: 3.0.2-0ubuntu2+grilo

I expected it to seek forward in the song.

What happened instead was that it froze Rhythmbox.

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


** Tags: freezing m4a rhythmbox

** Attachment added: "A file containing the -d output of rhythmbox"
   
https://bugs.launchpad.net/bugs/1414620/+attachment/4305744/+files/debug%20log

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

Title:
  Rhythmbox freezes when seeking in m4a files.

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Rhythmbox freezes when i seek forward in a m4a file.
  It stops at the timestamp i forward it to.

  Ubuntu version: 14.04
  Rhythmbox Version: 3.0.2-0ubuntu2+grilo

  I expected it to seek forward in the song.

  What happened instead was that it froze Rhythmbox.

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

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


[Desktop-packages] [Bug 1374961] [NEW] disable touchpad when typing does not work

2014-09-28 Thread Jeroen
Public bug reported:

There is an option 'disable touchpad when typing' in the mouse settings
menu. However setting this options has no effect on my HP ProBook 6560b
running Ubuntu 14.04 LTS, and as a result the cursor/focus moves
frequently to other controls/windows while typing which is quite
frustrating.

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

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

Title:
  disable touchpad when typing does not work

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

Bug description:
  There is an option 'disable touchpad when typing' in the mouse
  settings menu. However setting this options has no effect on my HP
  ProBook 6560b running Ubuntu 14.04 LTS, and as a result the
  cursor/focus moves frequently to other controls/windows while typing
  which is quite frustrating.

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

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


[Desktop-packages] [Bug 1168582] Re: Google talk "Requires Authorization" after suspend/resume

2014-09-24 Thread Jeroen Hoek
This problem persists in 14.04 for me as well. One of the two Google
accounts I add will fail even during the same session with the
"authorisation required" error.

I have stopped using Empathy and the Online Accounts configurator
completely due to this bug, although I give it a go whenever I move to a
newer version of Ubuntu to see if the bug persists. Oddly enough, other
messaging applications seem fine with my Google accounts, and no
authorisation of any kind is needed beyond my credentials.

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

Title:
  Google talk "Requires Authorization" after suspend/resume

Status in “empathy” package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of raring with all updates. After suspend/resuming my
  laptop, the google talk account refuses to reconnect, and emparthy
  says it requires authorization, if I click the button next to requires
  authorzation it just brings me to UOA and nothing happens. toggling
  the gtalk account on and off doesn't help, it just requires
  authorization again. only way to get it back is to reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: empathy 3.6.4-0ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
  Uname: Linux 3.8.0-17-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Fri Apr 12 20:14:00 2013
  InstallationDate: Installed on 2013-04-12 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130411)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: empathy
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1322530] Re: Most system settings have gone

2014-05-26 Thread Jeroen
The issue is likely caused by an attempt to remove Evolution from my
system (I wouldn't expect the system panel got weed out by removing
Evolution though). I faced the same problem on another machine where I
removed Evolution from the standard Ubuntu install. This issue can
therefore be closed as far as I'm concerned.

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

Title:
  Most system settings have gone

Status in “unity-control-center” package in Ubuntu:
  Incomplete

Bug description:
  When I open the System Settings panel most of the regular settings are gone.
  The only things left are Language, Security, Printers, Firewall (added by 
gufw), Landscape services, Software and Updates. 
  See attached image.

  After a reboot I have the same and other accounts have the same
  situation.

  Ubuntu 14.04 64 bit.

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

-- 
Mailing list: https://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 1322530] Re: Most system settings have gone

2014-05-23 Thread Jeroen
Hello Iain,

I start system settings in the regular way, i.e. from the notification var
in the upper right corner.
I just have restored a saved image as this situation was unworkable for me,
however I saved the logfiles in /var/log if that might be of any help.
Beside the standard ppa's I used ppa's from Chrome and Dropbox, and used
Grive in the past.

Regards,
Jeroen



On 23 May 2014 11:18, Iain Lane  wrote:

> Hello Jeroen,
>
> The desktop "System Settings" is called unity-control-center, not
> ubuntu-system-settings, so I've reassigned this bug there.
>
> It sounds like you are managing to launch "gnome-control-center"
> somehow, which is not the version that Ubuntu is using. How are you
> launching the system settings? Can you tell me which version of gnome-
> control-center and unity-control-center you have installed and whether
> you are using any PPAs?
>
> If you type alt-f2 to bring up a "run" entry and launch "unity-control-
> center" from there, do you see all of the other panels?
>
> ** Package changed: ubuntu-system-settings (Ubuntu) => unity-control-
> center (Ubuntu)
>
> ** Changed in: unity-control-center (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1322530
>
> Title:
>   Most system settings have gone
>
> Status in “unity-control-center” package in Ubuntu:
>   Incomplete
>
> Bug description:
>   When I open the System Settings panel most of the regular settings are
> gone.
>   The only things left are Language, Security, Printers, Firewall (added
> by gufw), Landscape services, Software and Updates.
>   See attached image.
>
>   After a reboot I have the same and other accounts have the same
>   situation.
>
>   Ubuntu 14.04 64 bit.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1322530/+subscriptions
>

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

Title:
  Most system settings have gone

Status in “unity-control-center” package in Ubuntu:
  Incomplete

Bug description:
  When I open the System Settings panel most of the regular settings are gone.
  The only things left are Language, Security, Printers, Firewall (added by 
gufw), Landscape services, Software and Updates. 
  See attached image.

  After a reboot I have the same and other accounts have the same
  situation.

  Ubuntu 14.04 64 bit.

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

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


[Desktop-packages] [Bug 950790] Re: Pidgin-sipe connection error after upgrade to Ubuntu 12.04

2014-05-22 Thread Jeroen
Quick fix: change user angent to:

UCCAPI/15.0.4481.1000 OC/15.0.4481.1000 (Microsoft Lync)

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

Title:
  Pidgin-sipe connection error after upgrade to Ubuntu 12.04

Status in “pidgin” package in Ubuntu:
  Confirmed
Status in “pidgin-sipe” package in Debian:
  Fix Released

Bug description:
  Have upgraded from Ubuntu 11.10 to Ubuntu 12.04 and I'm no longer able to 
connect to Microsoft Office Communicator.
  Every time I try to reconnect I get a "Read error".

  Any support is appreciated.

  Regards,
  Tibi

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

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


[Desktop-packages] [Bug 1318030] [NEW] Cannot login-without-password when home folder in encrypted

2014-05-09 Thread Jeroen
*** This bug is a security vulnerability ***

Public security bug reported:

Users of which the home folder is encrypted using the CLI (unfortunately
there is no GUI option for this, see
https://bugs.launchpad.net/ubuntu/+source/gnome-control-
center/+bug/1279766), and for which the 'login without password' is set,
cannot login.

Steps to reproduce:
1. Using an Administrator account, create a new user in System Settings > User 
Accounts and set a password.
2. Open a shell and encrypt the newly created user folder by 'sudo 
ecryptfs-migrate-home -u '
3. Login into the new account: successful
4. Logout and login into the Administrator account and select 'Login without 
password' for the newly created user.
5. Login into the new account: cannot login (the password field for this users 
now displays 'Log in' but trying to login results in a flickering screen and 
back to the login screen.

Ubuntu 14.04 x64 (reproducable on two different machines)

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

** Information type changed from Private Security to Public Security

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

Title:
  Cannot login-without-password when home folder in encrypted

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

Bug description:
  Users of which the home folder is encrypted using the CLI
  (unfortunately there is no GUI option for this, see
  https://bugs.launchpad.net/ubuntu/+source/gnome-control-
  center/+bug/1279766), and for which the 'login without password' is
  set, cannot login.

  Steps to reproduce:
  1. Using an Administrator account, create a new user in System Settings > 
User Accounts and set a password.
  2. Open a shell and encrypt the newly created user folder by 'sudo 
ecryptfs-migrate-home -u '
  3. Login into the new account: successful
  4. Logout and login into the Administrator account and select 'Login without 
password' for the newly created user.
  5. Login into the new account: cannot login (the password field for this 
users now displays 'Log in' but trying to login results in a flickering screen 
and back to the login screen.

  Ubuntu 14.04 x64 (reproducable on two different machines)

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

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


[Desktop-packages] [Bug 1315135] Re: xorg.conf deleted during upgrade; native resolution no longer works

2014-05-01 Thread Jeroen T. Vermeulen
It's beginning to look like an nvidia driver problem.  I tried switching
to Noveau; that left me with a resolution of 640×480, with no other
options.  (In case you're wondering: it looks great but isn't very
practical).  Switching back to the proprietary driver deleted my
xorg.conf again.  After a few times back and forth between the two
drivers, and restoring xorg.conf, I now suddenly find that most of the
fuzzy pixels are gone, the GUI fonts look good again, the menu bars are
back to the Unity style, and looking at the screen no longer hurts my
eyes!

No idea what happened, or why making the same changes earlier didn't
produce the same effects.  Let's just hope it stays the way it looks
now.

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

Title:
  xorg.conf deleted during upgrade; native resolution no longer works

Status in “xorg” package in Ubuntu:
  New

Bug description:
  I just upgraded a desktop system from 13.10 to 14.04, and to my horror
  found that the monitor's native resolution was no longer supported:
  the best setting offered was 1024×768 or somesuch.

  Turns out the upgrade deleted xorg.conf.  There were two backups: one
  with the date as a suffix (.01052014) and one with just ".backup" as a
  suffix.  The one with the date didn't look like what I had before, so
  I restored xorg.conf from xorg.conf.backup instead.

  Now I think I'm back in the resolution I had before (after going to
  the Display settings), but there's something wrong.  The resolution
  isn't quite the native one so many pixels are fuzzy, causing my eyes
  to ache, and the font inside menus looks a few sizes too small.  It's
  hard to read and leaves a lot of horizontal space in the menus unused.
  It also makes kerning look irregular.

  The monitor is an Iiyama ProLite E2407HDSV.  It's supposed to do
  1920×1080, but the best I can get working properly in the Display
  settings is 1680×1050.  The next step up, 1920×1080, won't show the
  entire screen — large swathes of the desktop fall outside the physical
  display.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  304.117  Tue Nov 26 21:36:39 
PST 2013
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May  1 21:47:44 2014
  DistUpgraded: 2014-05-01 21:23:35,494 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-304-updates, 304.117, 3.11.0-20-generic, i686: installed
   nvidia-304-updates, 304.117, 3.13.0-24-generic, i686: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: CardExpert Technology Device [10b0:1401]
  InstallationDate: Installed on 2011-02-17 (1168 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=5e1d12d5-4c62-426b-aa1a-ab9e6aac90b7 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-05-01 (0 days ago)
  dmi.bios.date: 06/17/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2102
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A79XTD EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0X
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2102:bd06/17/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A79XTDEVO:rvrRevX.0X:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A

[Desktop-packages] [Bug 1315135] Re: xorg.conf deleted during upgrade; native resolution no longer works

2014-05-01 Thread Jeroen T. Vermeulen
Also, I don't know if these are related, but window menus now appear not
only at the top of the screen or in the window's title bar (depending on
the new configuration setting in 14.04), but also in the classic pre-
Unity location: right below the window's title bar.

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

Title:
  xorg.conf deleted during upgrade; native resolution no longer works

Status in “xorg” package in Ubuntu:
  New

Bug description:
  I just upgraded a desktop system from 13.10 to 14.04, and to my horror
  found that the monitor's native resolution was no longer supported:
  the best setting offered was 1024×768 or somesuch.

  Turns out the upgrade deleted xorg.conf.  There were two backups: one
  with the date as a suffix (.01052014) and one with just ".backup" as a
  suffix.  The one with the date didn't look like what I had before, so
  I restored xorg.conf from xorg.conf.backup instead.

  Now I think I'm back in the resolution I had before (after going to
  the Display settings), but there's something wrong.  The resolution
  isn't quite the native one so many pixels are fuzzy, causing my eyes
  to ache, and the font inside menus looks a few sizes too small.  It's
  hard to read and leaves a lot of horizontal space in the menus unused.
  It also makes kerning look irregular.

  The monitor is an Iiyama ProLite E2407HDSV.  It's supposed to do
  1920×1080, but the best I can get working properly in the Display
  settings is 1680×1050.  The next step up, 1920×1080, won't show the
  entire screen — large swathes of the desktop fall outside the physical
  display.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  304.117  Tue Nov 26 21:36:39 
PST 2013
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May  1 21:47:44 2014
  DistUpgraded: 2014-05-01 21:23:35,494 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-304-updates, 304.117, 3.11.0-20-generic, i686: installed
   nvidia-304-updates, 304.117, 3.13.0-24-generic, i686: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: CardExpert Technology Device [10b0:1401]
  InstallationDate: Installed on 2011-02-17 (1168 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=5e1d12d5-4c62-426b-aa1a-ab9e6aac90b7 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-05-01 (0 days ago)
  dmi.bios.date: 06/17/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2102
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A79XTD EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0X
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2102:bd06/17/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A79XTDEVO:rvrRevX.0X:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  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
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xser

[Desktop-packages] [Bug 1315135] [NEW] xorg.conf deleted during upgrade; native resolution no longer works

2014-05-01 Thread Jeroen T. Vermeulen
Public bug reported:

I just upgraded a desktop system from 13.10 to 14.04, and to my horror
found that the monitor's native resolution was no longer supported: the
best setting offered was 1024×768 or somesuch.

Turns out the upgrade deleted xorg.conf.  There were two backups: one
with the date as a suffix (.01052014) and one with just ".backup" as a
suffix.  The one with the date didn't look like what I had before, so I
restored xorg.conf from xorg.conf.backup instead.

Now I think I'm back in the resolution I had before (after going to the
Display settings), but there's something wrong.  The resolution isn't
quite the native one so many pixels are fuzzy, causing my eyes to ache,
and the font inside menus looks a few sizes too small.  It's hard to
read and leaves a lot of horizontal space in the menus unused.  It also
makes kerning look irregular.

The monitor is an Iiyama ProLite E2407HDSV.  It's supposed to do
1920×1080, but the best I can get working properly in the Display
settings is 1680×1050.  The next step up, 1920×1080, won't show the
entire screen — large swathes of the desktop fall outside the physical
display.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic i686
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86 Kernel Module  304.117  Tue Nov 26 21:36:39 PST 
2013
 GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3
Architecture: i386
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu May  1 21:47:44 2014
DistUpgraded: 2014-05-01 21:23:35,494 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 nvidia-304-updates, 304.117, 3.11.0-20-generic, i686: installed
 nvidia-304-updates, 304.117, 3.13.0-24-generic, i686: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: CardExpert Technology Device [10b0:1401]
InstallationDate: Installed on 2011-02-17 (1168 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=5e1d12d5-4c62-426b-aa1a-ab9e6aac90b7 ro quiet splash
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2014-05-01 (0 days ago)
dmi.bios.date: 06/17/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2102
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A79XTD EVO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0X
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2102:bd06/17/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A79XTDEVO:rvrRevX.0X:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
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
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: Thu May  1 21:45:41 2014
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
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/1315135

Title:
  xorg.conf deleted during upgrade; native resolution no longer works

Status in “xorg” package in Ubuntu:
  New

Bug description:
  I just upgraded a 

[Desktop-packages] [Bug 1300557] Re: Screen resolution no longer works

2014-03-31 Thread Jeroen T. Vermeulen
** Description changed:

  My display's native resolution is 2560×1440 pixels.  Prior to, I think,
  Saucy I could only reach this resolution by adding it using xrandr, and
  then calling xrandr on boot/login to select that resolution.  The
  Display preferences did not show any higher options than 1920×1200.
  
  In Saucy, the native resolution just worked, and I could stop using
  xrandr.  It also worked in Trusty in the alpha releases, up to (and I
  think including) beta-1.  But today (this is not an April's fool, is
  it?) I rebooted after an upgrade, and found myself back in 1920×1200.
- Again, the Display preferences list that as the highest possible
- resolution.  But this time, attempts to ‘xrandr --admode’ my native
+ Again, the Display preferences list that resolution as the highest
+ possible.  But this time, attempts to ‘xrandr --addmode’ my native
  resolution failed.
  
  The error message wasn't very helpful; I'll try to reproduce it later
  but it throws my display into yet a lower resolution that's hard to work
  with.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr  1 09:59:00 2014
  DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
-Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
+  Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
+    Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2013-08-03 (240 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic 
root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago)
  dmi.bios.date: 05/16/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-D3HP-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z87-D3HP
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  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
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Apr  1 09:52:36 2014
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id   16510 
-  vendor DEL
+  product id   16510
+  vendor DEL
  xserver.version: 2:1.15.0-1ubuntu7

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

Title:
  Screen resolution no longer works

Status in “xorg” package in Ubuntu:
  New

Bug description:
  My display's native resolution is 2560×1440 pixels.  Prior to, I
  think, Saucy I could only reach this resolution by adding it using
  xrandr, and then calling xrandr on boot/login to select that
  resolution.  The Display preferences did n

[Desktop-packages] [Bug 1300557] [NEW] Screen resolution no longer works

2014-03-31 Thread Jeroen T. Vermeulen
Public bug reported:

My display's native resolution is 2560×1440 pixels.  Prior to, I think,
Saucy I could only reach this resolution by adding it using xrandr, and
then calling xrandr on boot/login to select that resolution.  The
Display preferences did not show any higher options than 1920×1200.

In Saucy, the native resolution just worked, and I could stop using
xrandr.  It also worked in Trusty in the alpha releases, up to (and I
think including) beta-1.  But today (this is not an April's fool, is
it?) I rebooted after an upgrade, and found myself back in 1920×1200.
Again, the Display preferences list that as the highest possible
resolution.  But this time, attempts to ‘xrandr --admode’ my native
resolution failed.

The error message wasn't very helpful; I'll try to reproduce it later
but it throws my display into yet a lower resolution that's hard to work
with.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Apr  1 09:59:00 2014
DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
InstallationDate: Installed on 2013-08-03 (240 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic 
root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago)
dmi.bios.date: 05/16/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F4
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z87-D3HP-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: Z87-D3HP
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
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
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Tue Apr  1 09:52:36 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   16510 
 vendor DEL
xserver.version: 2:1.15.0-1ubuntu7

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


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

Title:
  Screen resolution no longer works

Status in “xorg” package in Ubuntu:
  New

Bug description:
  My display's native resolution is 2560×1440 pixels.  Prior to, I
  think, Saucy I could only reach this resolution by adding it using
  xrandr, and then calling xrandr on boot/login to select that
  resolution.  The Display preferences did not show any higher options
  than 1920×1200.

  In Saucy, the native resolution just worked, and I could stop using
  xrandr.  It also worked in Trusty in the alpha releases, up to (and I
  think including) beta-1.  But today (this is not an April's fool, is
  it?) I rebooted after an upgrade, and found myself back in 1920×1200.
  Again, the Display preferences list that as the highest possible
  resolution.  But this time, attempts to ‘xrandr --admode’ my native
  resoluti

[Desktop-packages] [Bug 968759]

2014-02-05 Thread Jeroen Roovers
(In reply to Jeroen Roovers from comment #11)
> I'll let it run rampant in www-plugins/adobe-flash-11.2.202.291-r1 for a 
> while.

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

Title:
  adobe-flashplugin 11.2.202.228-0lucid1freezes firefox display -
  crashes some webkit programs (depends on cpu)

Status in “adobe-flashplugin” package in Ubuntu:
  Confirmed
Status in “flashplugin-nonfree” package in Ubuntu:
  Confirmed
Status in Baltix GNU/Linux:
  Confirmed
Status in “flashplugin-nonfree” package in Debian:
  Fix Released
Status in Gentoo Linux:
  Won't Fix

Bug description:
  Using Firefox 11.0 and the Adobe's Shockwave Flash 11.1.202.228 in youtube. 
Youtube and all flash sites shows a black box instead of the player. It works 
fine on Google Chrome.
  i'm reinstall this package and nothing happend.

  im using Ubuntu lucid 10.04.3 Adobe-flashplugin 11.2.202.228-0lucid1
  adobe-flash-properties-gtk works fine.

  This package is not stable.
  -
  This is apparently caused by the use of SSE2 instructions in new versions of 
adobe flash binaries, but only on older CPU's not implementing SSE2. There is 
an upstream bug reported for this: 
https://bugbase.adobe.com/index.cfm?event=bug&id=3161034

  Note that this code is binary only outside of Adobe.

  Where lernid, and apparently epiphany-browser use webkit they don't
  catch SIGILL. Both crash  and close with the message "Illegal
  Instruction" sent to the console.

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

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


[Desktop-packages] [Bug 1253962] Re: hangs on startup

2013-12-18 Thread Jeroen Meijer
Same here, but it also happen on the play button in Rhythmbox itself. It
is an almost-certainty after the first login or boot (for me this is
virtually the same thing). Time counter and slider stay on 0:00, one
core goes to 100%, UI freezes. Closing brings up the dialog if I want to
kill it. Doing so and restarting Rhythmbox most of the times fixes the
problem, but not always.

Most definately started after moving from 13:04 to 13:10.

Hope this helps.

Jeroen

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

Title:
  hangs on startup

Status in “rhythmbox” package in Ubuntu:
  Confirmed

Bug description:
  Rhthmbox Hangs on every first time startup.

  Mostly happens when I clicks on Play button directly placed on
  dropdown on system indicator area on right top.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: rhythmbox 2.99.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Fri Nov 22 15:19:14 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-11-08 (13 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1058315] Re: ubuntu firefox modifications add-on makes firefox is unresponsive when accessing webserver using windows based authentication

2013-08-30 Thread Jeroen
I am seeing this behaviour as well when trying to log in to my
employer's intranet and erp sites. These servers use windows
authentication.

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

Title:
  ubuntu firefox modifications add-on makes firefox is unresponsive when
  accessing webserver using windows based authentication

Status in “ubufox” package in Ubuntu:
  Confirmed

Bug description:
  When accessing a Windows based webserver from work where my work
  (Active Directory) credentials are required Firefox becomes largely
  unresponsive. It does seem to process the website, but it isn't usable
  anymore and the firefox windows greys out for most of the time. It
  even sometimes causes the whole desktop to become unresponsive forcing
  me to switch to a VT and kill firefox.

  It took me a while to find out that disabling the 'Ubuntu Firefox
  Modifications' add-on that fixed the problem.

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

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


[Desktop-packages] [Bug 1218731] [NEW] package unity-webapps-common 2.4.16+13.10.20130715-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/icons/hicolor/128x128/apps/ubuntuone-music

2013-08-29 Thread Jeroen T. Vermeulen
Public bug reported:

Automatically reported crash.  I think it happened while upgrading.

ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: unity-webapps-common 2.4.16+13.10.20130715-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-3.7-generic 3.11.0-rc6
Uname: Linux 3.11.0-3-generic i686
NonfreeKernelModules: fglrx
ApportVersion: 2.12.1-0ubuntu2
Architecture: i386
Date: Fri Aug 30 11:45:29 2013
DuplicateSignature: 
package:unity-webapps-common:2.4.16+13.10.20130715-0ubuntu1:trying to overwrite 
'/usr/share/icons/hicolor/128x128/apps/ubuntuone-music.png', which is also in 
package unity-asset-pool 0.8.24daily13.06.10-0ubuntu1
ErrorMessage: trying to overwrite 
'/usr/share/icons/hicolor/128x128/apps/ubuntuone-music.png', which is also in 
package unity-asset-pool 0.8.24daily13.06.10-0ubuntu1
InstallationDate: Installed on 2012-11-25 (277 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: webapps-applications
Title: package unity-webapps-common 2.4.16+13.10.20130715-0ubuntu1 failed to 
install/upgrade: trying to overwrite 
'/usr/share/icons/hicolor/128x128/apps/ubuntuone-music.png', which is also in 
package unity-asset-pool 0.8.24daily13.06.10-0ubuntu1
UpgradeStatus: Upgraded to saucy on 2013-08-21 (8 days ago)

** Affects: webapps-applications (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 package-conflict saucy

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

Title:
  package unity-webapps-common 2.4.16+13.10.20130715-0ubuntu1 failed to
  install/upgrade: trying to overwrite
  '/usr/share/icons/hicolor/128x128/apps/ubuntuone-music.png', which is
  also in package unity-asset-pool 0.8.24daily13.06.10-0ubuntu1

Status in “webapps-applications” package in Ubuntu:
  New

Bug description:
  Automatically reported crash.  I think it happened while upgrading.

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: unity-webapps-common 2.4.16+13.10.20130715-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-3.7-generic 3.11.0-rc6
  Uname: Linux 3.11.0-3-generic i686
  NonfreeKernelModules: fglrx
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: i386
  Date: Fri Aug 30 11:45:29 2013
  DuplicateSignature: 
package:unity-webapps-common:2.4.16+13.10.20130715-0ubuntu1:trying to overwrite 
'/usr/share/icons/hicolor/128x128/apps/ubuntuone-music.png', which is also in 
package unity-asset-pool 0.8.24daily13.06.10-0ubuntu1
  ErrorMessage: trying to overwrite 
'/usr/share/icons/hicolor/128x128/apps/ubuntuone-music.png', which is also in 
package unity-asset-pool 0.8.24daily13.06.10-0ubuntu1
  InstallationDate: Installed on 2012-11-25 (277 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: webapps-applications
  Title: package unity-webapps-common 2.4.16+13.10.20130715-0ubuntu1 failed to 
install/upgrade: trying to overwrite 
'/usr/share/icons/hicolor/128x128/apps/ubuntuone-music.png', which is also in 
package unity-asset-pool 0.8.24daily13.06.10-0ubuntu1
  UpgradeStatus: Upgraded to saucy on 2013-08-21 (8 days ago)

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

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


[Desktop-packages] [Bug 968759]

2013-06-19 Thread Jeroen Roovers
(In reply to Matt Turner from comment #10)
> (In reply to Matt Turner from comment #6)
> > Jim, there was a whole thread on the gentoo-dev mailing list about this
> > sse2check (that apparently you did not see?)
> > 
> > Wouldn't it be better if we just did this?
> > 
> > IUSE="... sse2"
> > REQUIRED_USE="sse2"
> 
> Jeroen,
> Now that you're maintaining adobe-flash, might I ask you to consider using
> REQUIRED_USE="sse2" to allow users to immediately know that SSE2 is required?

I don't think Jim ever found the time to consider this solution. I'll
let it run rampant in www-plugins/adobe-flash-11.2.202.291-r1 for a
while.

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

Title:
  adobe-flashplugin 11.2.202.228-0lucid1freezes firefox display -
  crashes some webkit programs (depends on cpu)

Status in “adobe-flashplugin” package in Ubuntu:
  Confirmed
Status in “flashplugin-nonfree” package in Ubuntu:
  Confirmed
Status in Baltix GNU/Linux:
  Confirmed
Status in “flashplugin-nonfree” package in Debian:
  Fix Released
Status in Gentoo Linux:
  Unknown

Bug description:
  Using Firefox 11.0 and the Adobe's Shockwave Flash 11.1.202.228 in youtube. 
Youtube and all flash sites shows a black box instead of the player. It works 
fine on Google Chrome.
  i'm reinstall this package and nothing happend.

  im using Ubuntu lucid 10.04.3 Adobe-flashplugin 11.2.202.228-0lucid1
  adobe-flash-properties-gtk works fine.

  This package is not stable.
  -
  This is apparently caused by the use of SSE2 instructions in new versions of 
adobe flash binaries, but only on older CPU's not implementing SSE2. There is 
an upstream bug reported for this: 
https://bugbase.adobe.com/index.cfm?event=bug&id=3161034

  Note that this code is binary only outside of Adobe.

  Where lernid, and apparently epiphany-browser use webkit they don't
  catch SIGILL. Both crash  and close with the message "Illegal
  Instruction" sent to the console.

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

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


[Desktop-packages] [Bug 681002] Re: gpg: problem with the agent: Bad CA certificate

2013-05-15 Thread Jeroen
I had deja-dup running on ubuntu 12.04 when moving to 13.04, i could not
restore since deja-dup keeps asking for a pasword, I never set

deja-dup26.0-0ubuntu1
duplicity   0.6.21-0ubuntu1

What to do?

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

Title:
  gpg: problem with the agent: Bad CA certificate

Status in Déjà Dup Backup Tool:
  Invalid
Status in GNOME keyring services:
  Fix Released
Status in “gnome-keyring” package in Ubuntu:
  Fix Released

Bug description:
  If I don't encrypt the backup all works well, otherwise...

  [...]
  DUPLICITY: INFO 1
  DUPLICITY: . GPG error detail: Traceback (most recent call last):
  DUPLICITY: .   File "/usr/bin/duplicity-2.6", line 1245, in 
  DUPLICITY: . with_tempdir(main)
  DUPLICITY: .   File "/usr/bin/duplicity-2.6", line 1238, in with_tempdir
  DUPLICITY: . fn()
  DUPLICITY: .   File "/usr/bin/duplicity-2.6", line 1220, in main
  DUPLICITY: . incremental_backup(sig_chain)
  DUPLICITY: .   File "/usr/bin/duplicity-2.6", line 488, in incremental_backup
  DUPLICITY: . globals.backend)
  DUPLICITY: .   File "/usr/bin/duplicity-2.6", line 295, in write_multivol
  DUPLICITY: . globals.gpg_profile, globals.volsize)
  DUPLICITY: .   File "/usr/lib64/python2.6/site-packages/duplicity/gpg.py", 
line 291, in GPGWriteFile
  DUPLICITY: . file.close()
  DUPLICITY: .   File "/usr/lib64/python2.6/site-packages/duplicity/gpg.py", 
line 180, in close
  DUPLICITY: . self.gpg_failed()
  DUPLICITY: .   File "/usr/lib64/python2.6/site-packages/duplicity/gpg.py", 
line 165, in gpg_failed
  DUPLICITY: . raise GPGError, msg
  DUPLICITY: . GPGError: GPG Failed, see log below:
  DUPLICITY: . = Begin GnuPG log =
  DUPLICITY: . gpg: problem with the agent: Bad CA certificate
  DUPLICITY: . = End GnuPG log =
  DUPLICITY: . 
  DUPLICITY: . 

  DUPLICITY: ERROR 31 GPGError
  DUPLICITY: . GPGError: GPG Failed, see log below:
  DUPLICITY: . = Begin GnuPG log =
  DUPLICITY: . gpg: problem with the agent: Bad CA certificate
  DUPLICITY: . = End GnuPG log =
  DUPLICITY: . 
  [...]

  I'm using duplicity-0.6.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/681002/+subscriptions

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


[Desktop-packages] [Bug 1168582] Re: Google talk "Requires Authorization" after suspend/resume

2013-05-14 Thread Jeroen Hoek
I have two Google accounts as well, could that be a relevant factor?

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

Title:
  Google talk "Requires Authorization" after suspend/resume

Status in “empathy” package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of raring with all updates. After suspend/resuming my
  laptop, the google talk account refuses to reconnect, and emparthy
  says it requires authorization, if I click the button next to requires
  authorzation it just brings me to UOA and nothing happens. toggling
  the gtalk account on and off doesn't help, it just requires
  authorization again. only way to get it back is to reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: empathy 3.6.4-0ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
  Uname: Linux 3.8.0-17-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Fri Apr 12 20:14:00 2013
  InstallationDate: Installed on 2013-04-12 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130411)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: empathy
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 572628] Re: "Liyama" spelling error

2013-05-11 Thread Jeroen Hoek
In 2011 I sent a patch fixing this to the then-maintainer of hwdata.
That patch apparently never made it through, possibly because of a
maintainer change. Today I've sent the patch again to the developer who
last made commits to the project.

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

Title:
  "Liyama" spelling error

Status in GNOME Desktop Common Files:
  Invalid
Status in “gnome-desktop3” package in Ubuntu:
  Invalid
Status in “hwdata” package in Ubuntu:
  New

Bug description:
  Binary package hint: gnome-control-center

  Lucid final release amd64 alternate install CD
  iiyama ProLite H511S LCD monitor

  gnome-control-center1:2.30.0-0ubuntu4

  Preferences -> Monitors brings up a green box containing the text
  "Liyama North America 20". It should be iiyama, not Liyama. (And FWIW
  the monitor was purchased in England.)

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

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


[Desktop-packages] [Bug 1174936] Re: online-accounts-preferences crashes immediately when opened

2013-05-10 Thread Jeroen Hoek
I'm not using two-factor authentication and I get the same issue.

After going offline and removing my two Google accounts the crashing
stops, but I still get this message:

credentials-cc-panel-Message: cc-credentials-account-applications-
model.vala:156: No valid plugin found for application 'shotwell' with
account '7'

Before removing the previous two account it was '6'.

In seahorse the two accounts I have added are now represented by these
four entries:

Ubuntu Web Account: id 10-1
Ubuntu Web Account: id 10-3
Ubuntu Web Account: id 11-1
Ubuntu Web Account: id 11-3

There is something really strange going on with authentication. The
Google accounts fail to connect half the time. Removing and readding
them works, but that is not much of a workaround.

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

Title:
  online-accounts-preferences crashes immediately when opened

Status in Online Accounts: GNOME Control Center:
  New
Status in “empathy” package in Ubuntu:
  Confirmed
Status in “gnome-control-center-signon” package in Ubuntu:
  Confirmed

Bug description:
  `online-accounts-preferences` crashes immediately when opened. It
  crashes when you launch it by first opening "System Settings" via the
  launcher then choosing "Online Accounts" as well as when you open it
  directly by choosing "Online Accounts" from the launcher. It also
  crashes immediately when opened by running the `online-accounts-
  preferences` command on the command line.

  Here's the output it gives:

  % online-accounts-preferences
  credentials-cc-panel-Message: 
cc-credentials-account-applications-model.vala:156: No valid plugin found for 
application 'shotwell' with account '1'
  credentials-cc-panel-Message: 
cc-credentials-account-applications-model.vala:156: No valid plugin found for 
application 'unity-scope-gdrive' with account '1'
  credentials-cc-panel-Message: 
cc-credentials-account-applications-model.vala:156: No valid plugin found for 
application 'unity-lens-photos' with account '1'
  **
  ERROR:empathy-user-info.c:252:fill_contact_info_grid: assertion failed: (spec 
!= NULL)
  Aborted

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center-signon 0.1.6bzr13.04.05-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Tue Apr 30 14:03:48 2013
  InstallationDate: Installed on 2012-10-18 (194 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm-color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: gnome-control-center-signon
  UpgradeStatus: Upgraded to raring on 2013-04-26 (4 days ago)

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

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


[Desktop-packages] [Bug 659793] Re: xserver-xephyr: Couldn't find keyboard driver evdev

2012-10-12 Thread Jeroen Dekkers
** Bug watch added: Debian Bug tracker #646686
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646686

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

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

Title:
  xserver-xephyr: Couldn't find keyboard driver evdev

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

Bug description:
  Binary package hint: xserver-xephyr

  When starting Xephyr with the following command line:

  Xephyr :5 -ac -screen 1280x1024 -mouse evdev,,device=/dev/input/by-id
  /usb-04d9_0499-event-mouse -keybd evdev,,device=/dev/input/by-id/usb-
  Logitech_Logitech_USB_Keyboard-event-
  
kbd,xkbrules=xorg,xkbmodel=evdev,xkblayout=de,xkbvariant=nodeadkeys,xkboptions="lv3:ralt_switch,compose:caps"
  -dpi 100

  The following messages are printed on the console:

  [dix] Could not init font path element /usr/share/fonts/X11/cyrillic, 
removing from list!
  Kbd option key (compose:caps) of value ((null)) not assigned!
  Couldn't find pointer driver evdev
  Couldn't find keyboard driver evdev

  The keyboard and mouse are not working.

  When downgrading xserver-xephyr to version 2:1.7.6-2ubuntu7, the error
  messages about evdev don't appear and keyboard and mouse work as
  expected.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: xserver-xephyr 2:1.9.0-0ubuntu7
  Architecture: amd64
  ExecutablePath: /usr/bin/Xephyr
  SourcePackage: xorg-server

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

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


[Desktop-packages] [Bug 998223] Re: Turns on IPv6 privacy extensions with latest update, even when turned off by sysctl

2012-05-12 Thread Jeroen Dekkers
Is there a reason why /etc/sysctl.conf is parsed instead of getting the
current configuration from /proc/sys/net/ipv6/conf/default/use_tempaddr?

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

Title:
  Turns on IPv6 privacy extensions with latest update, even when turned
  off by sysctl

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

Bug description:
  After installing the latest network-manager package that fixes  bug
  990011, I noticed that my IPv6 address was suddenly different because
  IPv6 privacy extensions had been turned on. Turning them off in
  /etc/sysctl.d/10-ipv6-privacy.conf doesn't stop network-manager from
  enabling it. I'm using the default automatically generated wired
  connection, so there are no connection settings in /etc/NetworkManager
  /system-connections.

  If I change some settings so that NM writes the connection to system-
  connections and then add ip6-privacy=0 to the configuration the
  privacy extensions are turned off, but it would be nice if that was
  also the case when it is turned of using
  /etc/sysctl.d/10-ipv6-privacy.conf.

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

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


[Desktop-packages] [Bug 998223] Re: Turns on IPv6 privacy extensions with latest update, even when turned off by sysctl

2012-05-11 Thread Jeroen Dekkers
** Attachment added: "NetworkManager.conf"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/998223/+attachment/3141873/+files/NetworkManager.conf

** Description changed:

- After installing the latest network-manage package that fixes  bug
+ After installing the latest network-manager package that fixes  bug
  990011, I noticed that my IPv6 address was suddenly different because
  IPv6 privacy extensions had been turned on. Turning them off in
  /etc/sysctl.d/10-ipv6-privacy.conf doesn't stop network-manager from
  enabling it. I'm using the default automatically generated wired
  connection, so there are no connection settings in /etc/NetworkManager
  /system-connections.
  
  If I change some settings so that NM writes the connection to system-
  connections and then add ip6-privacy=0 to the configuration the privacy
  extensions are turned off, but it would be nice if that was also the
  case when it is turned of using /etc/sysctl.d/10-ipv6-privacy.conf.

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

Title:
  Turns on IPv6 privacy extensions with latest update, even when turned
  off by sysctl

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

Bug description:
  After installing the latest network-manager package that fixes  bug
  990011, I noticed that my IPv6 address was suddenly different because
  IPv6 privacy extensions had been turned on. Turning them off in
  /etc/sysctl.d/10-ipv6-privacy.conf doesn't stop network-manager from
  enabling it. I'm using the default automatically generated wired
  connection, so there are no connection settings in /etc/NetworkManager
  /system-connections.

  If I change some settings so that NM writes the connection to system-
  connections and then add ip6-privacy=0 to the configuration the
  privacy extensions are turned off, but it would be nice if that was
  also the case when it is turned of using
  /etc/sysctl.d/10-ipv6-privacy.conf.

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

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


[Desktop-packages] [Bug 998223] Re: Turns on IPv6 privacy extensions with latest update, even when turned off by sysctl

2012-05-11 Thread Jeroen Dekkers
** Attachment added: "sysctl.conf"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/998223/+attachment/3141872/+files/sysctl.conf

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

Title:
  Turns on IPv6 privacy extensions with latest update, even when turned
  off by sysctl

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

Bug description:
  After installing the latest network-manager package that fixes  bug
  990011, I noticed that my IPv6 address was suddenly different because
  IPv6 privacy extensions had been turned on. Turning them off in
  /etc/sysctl.d/10-ipv6-privacy.conf doesn't stop network-manager from
  enabling it. I'm using the default automatically generated wired
  connection, so there are no connection settings in /etc/NetworkManager
  /system-connections.

  If I change some settings so that NM writes the connection to system-
  connections and then add ip6-privacy=0 to the configuration the
  privacy extensions are turned off, but it would be nice if that was
  also the case when it is turned of using
  /etc/sysctl.d/10-ipv6-privacy.conf.

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

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


[Desktop-packages] [Bug 998223] Re: Turns on IPv6 privacy extensions with latest update, even when turned off by sysctl

2012-05-11 Thread Jeroen Dekkers
** Attachment added: "10-ipv6-privacy.conf"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/998223/+attachment/3141871/+files/10-ipv6-privacy.conf

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

Title:
  Turns on IPv6 privacy extensions with latest update, even when turned
  off by sysctl

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

Bug description:
  After installing the latest network-manager package that fixes  bug
  990011, I noticed that my IPv6 address was suddenly different because
  IPv6 privacy extensions had been turned on. Turning them off in
  /etc/sysctl.d/10-ipv6-privacy.conf doesn't stop network-manager from
  enabling it. I'm using the default automatically generated wired
  connection, so there are no connection settings in /etc/NetworkManager
  /system-connections.

  If I change some settings so that NM writes the connection to system-
  connections and then add ip6-privacy=0 to the configuration the
  privacy extensions are turned off, but it would be nice if that was
  also the case when it is turned of using
  /etc/sysctl.d/10-ipv6-privacy.conf.

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

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


[Desktop-packages] [Bug 998223] [NEW] Turns on IPv6 privacy extensions with latest update, even when turned off by sysctl

2012-05-11 Thread Jeroen Dekkers
Public bug reported:

After installing the latest network-manager package that fixes  bug
990011, I noticed that my IPv6 address was suddenly different because
IPv6 privacy extensions had been turned on. Turning them off in
/etc/sysctl.d/10-ipv6-privacy.conf doesn't stop network-manager from
enabling it. I'm using the default automatically generated wired
connection, so there are no connection settings in /etc/NetworkManager
/system-connections.

If I change some settings so that NM writes the connection to system-
connections and then add ip6-privacy=0 to the configuration the privacy
extensions are turned off, but it would be nice if that was also the
case when it is turned of using /etc/sysctl.d/10-ipv6-privacy.conf.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Turns on IPv6 privacy extensions with latest update, even when turned
  off by sysctl

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

Bug description:
  After installing the latest network-manager package that fixes  bug
  990011, I noticed that my IPv6 address was suddenly different because
  IPv6 privacy extensions had been turned on. Turning them off in
  /etc/sysctl.d/10-ipv6-privacy.conf doesn't stop network-manager from
  enabling it. I'm using the default automatically generated wired
  connection, so there are no connection settings in /etc/NetworkManager
  /system-connections.

  If I change some settings so that NM writes the connection to system-
  connections and then add ip6-privacy=0 to the configuration the
  privacy extensions are turned off, but it would be nice if that was
  also the case when it is turned of using
  /etc/sysctl.d/10-ipv6-privacy.conf.

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

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


[Desktop-packages] [Bug 990011] Re: use_tempaddr is *still* not set properly for default eth0 connections

2012-05-11 Thread Jeroen Dekkers
This patch changes the way how existing installations get their IPv6
address which is something that really shouldn't be done in an update to
an LTS release in my opinion. Even worse it completely overrules
configuration in /etc/sysctl.d/10-ipv6-privacy.conf and if you change
the configuration on a running system network-manager changes it back
within a second! For example

runge:~# sysctl -w net.ipv6.conf.eth0.use_tempaddr=0
net.ipv6.conf.eth0.use_tempaddr = 0

wait a few seconds while network-manager says something about
disconnected wired interface

runge:~# sysctl net.ipv6.conf.eth0.use_tempaddr 
net.ipv6.conf.eth0.use_tempaddr = 2

Network-manager shouldn't overrule the system configuration, especially
when network-manager currently has no toggle for privacy extensions. If
you think changing the default is okay in a stable update (I really
don't), at least it should be done in a way that makes it possible to
easily go back to the previous behaviour. Given that the sysctl default
is already what we want as default, I don't see why NM has to explicitly
set it again and if it doesn't do that it would be possible to change
the configuration in /etc/sysctl.

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

Title:
  use_tempaddr is *still* not set properly for default eth0 connections

Status in “network-manager” package in Ubuntu:
  Fix Released
Status in “network-manager” source package in Precise:
  Fix Released

Bug description:
  [Impact]
  Only affects IPv6 connections, but we established that the default should be 
to maintain our users' privacy on IPv6 connections; we want all IPv6 external 
connections to be established using temporary, dynamic addresses.

  [Development Fix]
  Very minor patch to threat an unknown value (-1) as (2), aka, enabling and 
preferring privacy extensions. Patch is attached.

  [Stable Fix]
  See "Development fix".

  [Test case]
  Connect a wire to your system. With NetworkManager running, the value 
returned by 'sysctl net.ipv6.conf.eth0.use_tempaddr' should be 2 at all times 
unless configured otherwise (though the default is set to 2 by default). 
Without the patch, the value is reset to 0 when NetworkManager is running, and 
correctly set to 2 when NetworkManager is stopped (since it reverts the value 
to the value when NM started).

  [Regression Potential]
  Low, impact may be failing connections in case of issues with the privacy 
extensions system in the Linux kernel.

  

  The use_tempaddr sysctl defaults to 0 in NetworkManager if it's not
  set elsewhere, such as it is the case for the default NM-created,
  automatic wired connection. That connection is never "completed"
  (because it's internal magic), and nm_backend_ipv6_use_tempaddr()
  doesn't have a chance of returning a valid system-wide default value
  since the function it calls, nm_generic_ipv6_use_tempaddr() only
  checks in /etc/sysctl.conf and /lib/sysctl.d/sysctl.conf for a system
  default value.

  (Regardless, this wouldn't work since we generate a setting based on a
  number of files in /etc/sysctl.d)

  Change the behavior slightly to default to a string of -1 as a default
  value in nm-system.c; then make sure that if that value is never
  changed by the result of nm_backend_ipv6_use_tempaddr(), we just don't
  touch that sysctl at all.

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

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


[Desktop-packages] [Bug 978620] Re: import music does not work correctly

2012-04-10 Thread Jeroen Tiel
-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/978620

Title:
  import music does not work correctly

Status in “rhythmbox” package in Ubuntu:
  New

Bug description:
  Not sure this is a bug or a feature request.

  I found the import music confusing, it gives the impression music is 
transferred to Rythembox but it stays at its location.
  I lost some files recently because I assumed Rythembox manages the music 
directory in simular ways as a lot of other music applications. Copying files 
to the set music folder and managing this.

  two points: import file/folder > add file/folder   -  better description in 
my view.
  A feature request > manage music directory

  Jeroen

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: rhythmbox 2.96-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Wed Apr 11 08:35:50 2012
  ExecutablePath: /usr/bin/rhythmbox
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: rhythmbox
  UpgradeStatus: Upgraded to precise on 2012-03-02 (39 days ago)

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

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


[Desktop-packages] [Bug 978620] [NEW] import music does not work correctly

2012-04-10 Thread Jeroen Tiel
Public bug reported:

Not sure this is a bug or a feature request.

I found the import music confusing, it gives the impression music is 
transferred to Rythembox but it stays at its location.
I lost some files recently because I assumed Rythembox manages the music 
directory in simular ways as a lot of other music applications. Copying files 
to the set music folder and managing this.

two points: import file/folder > add file/folder   -  better description in my 
view.
A feature request > manage music directory

Jeroen

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: rhythmbox 2.96-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic x86_64
ApportVersion: 2.0-0ubuntu4
Architecture: amd64
Date: Wed Apr 11 08:35:50 2012
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: rhythmbox
UpgradeStatus: Upgraded to precise on 2012-03-02 (39 days ago)

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


** Tags: amd64 apport-bug apport-lpi precise

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

Title:
  import music does not work correctly

Status in “rhythmbox” package in Ubuntu:
  New

Bug description:
  Not sure this is a bug or a feature request.

  I found the import music confusing, it gives the impression music is 
transferred to Rythembox but it stays at its location.
  I lost some files recently because I assumed Rythembox manages the music 
directory in simular ways as a lot of other music applications. Copying files 
to the set music folder and managing this.

  two points: import file/folder > add file/folder   -  better description in 
my view.
  A feature request > manage music directory

  Jeroen

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: rhythmbox 2.96-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Wed Apr 11 08:35:50 2012
  ExecutablePath: /usr/bin/rhythmbox
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: rhythmbox
  UpgradeStatus: Upgraded to precise on 2012-03-02 (39 days ago)

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

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


[Desktop-packages] [Bug 835972] Re: after resume the "Disconnected - you are now offline" notification doesn't disappear

2012-03-21 Thread Jeroen Meijer
I agree to increase its importance, but it does not happen only to
Xubuntu users, I am using gnome 3.2 and seeing the exact same thing. I
often make my laptop go in standby, so I am experiencing this at least
once a day. An annoyance is an understatement.

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

Title:
  after resume the "Disconnected - you are now offline" notification
  doesn't disappear

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

Bug description:
  Observed behaviour:
  When I resume from standby, the "Disconnected - you are now offline" 
notification (which probably appeared when standby was started) stays on the 
screen and doesn't go away until I close it manually.
  Network (LAN - eth0) works, so in fact I'm online and the notification is 
false.
  Notifications are set to disappear after 4 seconds, which they do, except 
this naughty one.

  Expected behaviour:
  The "Disconnected - you are now offline" notification should not appear or 
disappear after the selected amount of time.
  The best thing would be to display a "Connected - you are now online" 
notification.

  used version:
  0.2.1-1 on Xubuntu Natty
  (all updates up to date)

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

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


[Desktop-packages] [Bug 338785] Re: [MASTER] Updates while firefox is running cause various problems until restart

2012-03-19 Thread jeroen jansen
** Changed in: firefox (Ubuntu)
   Status: Triaged => Fix Committed

** Changed in: thunderbird (Ubuntu)
   Status: Incomplete => Opinion

** Changed in: thunderbird (Ubuntu)
   Status: Opinion => Fix Committed

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

Title:
  [MASTER] Updates while firefox is running cause various problems until
  restart

Status in The Mozilla Firefox Browser:
  New
Status in “firefox” package in Ubuntu:
  Fix Committed
Status in “firefox-3.0” package in Ubuntu:
  Won't Fix
Status in “thunderbird” package in Ubuntu:
  Fix Committed

Bug description:
  Workaround: if you see this, ensure that you properly restarted
  firefox. unfortunately only way to be sure is to re-login or restart
  your system

  ===
  Summary:
  After updating firefox to 3.0.7, i'd got assertion failed on startup, and 
later if i try to access any website
  Assertion is showed in GUI window.
  Error text:
  ASSERT: *** Search: _installLocation: engine has no file!
  Stack Trace:
  0:ENSURE_WARN(false,_installLocation: engine has no file!,2147500037)
  1:()
  2:()
  3:()
  4:epsGetAttr([object Object],hidden)
  5:()
  6:()
  7:currentEngine()
  8:get_currentEngine()
  9:updateDisplay()
  10:init()
  11:([object XULElement],6)

  LANG=C apt-cache policy firefox-3.0
  firefox-3.0:
    Installed: 3.0.6+nobinonly-0ubuntu0.8.10.1
    Candidate: 3.0.7+nobinonly-0ubuntu0.8.10.1
    Version table:
   3.0.7+nobinonly-0ubuntu0.8.10.1 0
  500 http://security.ubuntu.com intrepid-security/main Packages
   *** 3.0.6+nobinonly-0ubuntu0.8.10.1 0
  500 http://ru.archive.ubuntu.com intrepid-updates/main Packages
  100 /var/lib/dpkg/status
   3.0.3+nobinonly-0ubuntu2 0
  500 http://ru.archive.ubuntu.com intrepid/main Packages

  Note: At this moment i were downgraded firefox version, installed
  were: 3.0.7+nobinonly-0ubuntu0.8.10.1

  WORKAROUND (If Firefox won't quit):
  1. killall -HUP firefox
  or
  2. restart your computer

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

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


[Desktop-packages] [Bug 929403] Re: Wireless login ignores its stored password

2012-03-13 Thread Jeroen T. Vermeulen
I think the problem may have gone away in the meantime.  I haven't seen
it for a while, and I'm no longer near the network I originally noticed
it in.  It was the normal network-manager wi-fi password dialog, not the
keyring one.  And it needed the network's password, not any personal
password.

I'm trying to get to the connection in question, but failing: when I
double-click on it, in the Wireless pane of the Network Connections, I
get an error saying “Error initializing editor / No agents were
available for this request.”

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

Title:
  Wireless login ignores its stored password

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

Bug description:
  On the Precise beta, every time I log in, the wireless login prompt
  appears, asking me to log into our password-protected wifi network.

  This is similar to what you get when you lose wifi signal, *except*
  that now the password entry box is empty, not pre-filled with the
  stored password.

  This could be related to warnings I've been getting from e.g. apt-get
  about not having a keyring socket to connect to.  I would reproduce
  the exact message, except I don't seem to be getting it now.

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

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


[Desktop-packages] [Bug 929403] [NEW] Wireless login ignores its stored password

2012-02-09 Thread Jeroen T. Vermeulen
Public bug reported:

On the Precise beta, every time I log in, the wireless login prompt
appears, asking me to log into our password-protected wifi network.

This is similar to what you get when you lose wifi signal, *except* that
now the password entry box is empty, not pre-filled with the stored
password.

This could be related to warnings I've been getting from e.g. apt-get
about not having a keyring socket to connect to.  I would reproduce the
exact message, except I don't seem to be getting it now.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Wireless login ignores its stored password

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

Bug description:
  On the Precise beta, every time I log in, the wireless login prompt
  appears, asking me to log into our password-protected wifi network.

  This is similar to what you get when you lose wifi signal, *except*
  that now the password entry box is empty, not pre-filled with the
  stored password.

  This could be related to warnings I've been getting from e.g. apt-get
  about not having a keyring socket to connect to.  I would reproduce
  the exact message, except I don't seem to be getting it now.

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

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


[Desktop-packages] [Bug 835972] Re: after resume the "Disconnected - you are now offline" notification doesn't disappear

2012-01-05 Thread Jeroen Meijer
At the moment I am having the same problem running Gnome 3 on ubuntu
11.10.

Will there be a patch released?

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

Title:
  after resume the "Disconnected - you are now offline" notification
  doesn't disappear

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

Bug description:
  Observed behaviour:
  When I resume from standby, the "Disconnected - you are now offline" 
notification (which probably appeared when standby was started) stays on the 
screen and doesn't go away until I close it manually.
  Network (LAN - eth0) works, so in fact I'm online and the notification is 
false.
  Notifications are set to disappear after 4 seconds, which they do, except 
this naughty one.

  Expected behaviour:
  The "Disconnected - you are now offline" notification should not appear or 
disappear after the selected amount of time.
  The best thing would be to display a "Connected - you are now online" 
notification.

  used version:
  0.2.1-1 on Xubuntu Natty
  (all updates up to date)

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

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


[Desktop-packages] [Bug 832603] Re: gnome-settings-daemon crashed with SIGSEGV in g_simple_async_result_complete()

2011-09-20 Thread Jeroen T. Vermeulen
I'm still getting the crash dialogs, yes, and clicking Cancel makes more
and more of them come.

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

Title:
  gnome-settings-daemon crashed with SIGSEGV in
  g_simple_async_result_complete()

Status in Gnome Settings Daemon:
  Incomplete
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” source package in Oneiric:
  Triaged

Bug description:
  random rash after upgrade

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gnome-settings-daemon 3.1.4-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
  Uname: Linux 3.0.0-9-generic i686
  Architecture: i386
  Date: Wed Aug 24 13:41:30 2011
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110817)
  ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  ProcEnviron:
   SHELL=/bin/false
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x81ebf6d: mov0x8(%edx),%edx
   PC (0x081ebf6d) ok
   source "0x8(%edx)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   ?? () from /usr/lib/gnome-settings-daemon-3.0/libmedia-keys.so
   g_simple_async_result_complete () from 
/usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
  Title: gnome-settings-daemon crashed with SIGSEGV in 
g_simple_async_result_complete()
  UpgradeStatus: Upgraded to oneiric on 2011-08-24 (0 days ago)
  UserGroups:

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

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


[Desktop-packages] [Bug 836222] Re: Unable to rename samba network shares on desktop

2011-09-15 Thread Jeroen
I'm using Ubuntu; this is also mentioned in the description of the
issue. Why would it be 'about Kubuntu'?

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

Title:
  Unable to rename samba network shares on desktop

Status in “nautilus” package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Natty: I connect to a server location (Places | Connect to server), 
connect to a Windows share, specify a folder and add a bookmark. It connects 
perfectly to the network location but it puts a 'shortcut' icon (sorry for this 
terminology; I come from the  Windows world) on the desktop, called 'username$ 
on 10.0.0.10'. Unfortunately I cannot rename this shortcut, which is quite 
annoying, since this name doesn't make any sense for non-technical members of 
my family. 
  Even worse, when I add another bookmark to a different folder on this server 
it adds a shortcut with exactly the same name:  'username$ on 10.0.0.10', even 
though they point to different folders.
  I believe this is the same issue as reported in #109260 but that was closed 
no change.
  Please make it possible to rename these entries, or at least assign them the 
friendly BOOKMARK name.

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

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


[Desktop-packages] [Bug 832603] Re: gnome-settings-daemon crashed with SIGSEGV in g_simple_async_result_complete()

2011-09-08 Thread Jeroen T. Vermeulen
Then it may be something to do with the ridiculous amounts of CPU dbus-
daemon seems to gobble up.

As for my .xsession-errors, for me the last page is all lines like this
one:

unity-2d-launcher: [WARNING] void
LauncherApplicationsList::onRemoteEntryUpdated(QString, QMap): Application sent an update but we don't seem to have it in
the launcher: "application://nautilus.desktop"

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

Title:
  gnome-settings-daemon crashed with SIGSEGV in
  g_simple_async_result_complete()

Status in Gnome Settings Daemon:
  New
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” source package in Oneiric:
  Triaged

Bug description:
  random rash after upgrade

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gnome-settings-daemon 3.1.4-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
  Uname: Linux 3.0.0-9-generic i686
  Architecture: i386
  Date: Wed Aug 24 13:41:30 2011
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110817)
  ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  ProcEnviron:
   SHELL=/bin/false
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x81ebf6d: mov0x8(%edx),%edx
   PC (0x081ebf6d) ok
   source "0x8(%edx)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   ?? () from /usr/lib/gnome-settings-daemon-3.0/libmedia-keys.so
   g_simple_async_result_complete () from 
/usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
  Title: gnome-settings-daemon crashed with SIGSEGV in 
g_simple_async_result_complete()
  UpgradeStatus: Upgraded to oneiric on 2011-08-24 (0 days ago)
  UserGroups:

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

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