[Desktop-packages] [Bug 1453933] Re: Pitivi crashes Ubuntu after minimise

[Ben]

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

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

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

Title:
  Pitivi crashes Ubuntu after minimise

Status in PiTiVi , Non-linear video editor:
  Unknown
Status in compiz package in Ubuntu:
  New
Status in pitivi package in Ubuntu:
  New

Bug description:
  After getting this bug I was going to report it to the pitivi bug
  tracker, but it was already there, and they blamed it on compiz. So, I
  decided to report it here. The bug is quite simple, after opening the
  latest version and pressing the minimise button, Ubuntu crashes then
  restarts.

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

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

[Desktop-packages] [Bug 1453933] [NEW] Pitivi crashes Ubuntu after minimise

[Ben]

Public bug reported:

After getting this bug I was going to report it to the pitivi bug
tracker, but it was already there, and they blamed it on compiz. So, I
decided to report it here. The bug is quite simple, after opening the
latest version and pressing the minimise button, Ubuntu crashes then
restarts.

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

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

Title:
  Pitivi crashes Ubuntu after minimise

Status in compiz package in Ubuntu:
  New

Bug description:
  After getting this bug I was going to report it to the pitivi bug
  tracker, but it was already there, and they blamed it on compiz. So, I
  decided to report it here. The bug is quite simple, after opening the
  latest version and pressing the minimise button, Ubuntu crashes then
  restarts.

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

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

[Desktop-packages] [Bug 1453933] Re: Pitivi crashes Ubuntu after minimise

[Ben]

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

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

Title:
  Pitivi crashes Ubuntu after minimise

Status in compiz package in Ubuntu:
  New
Status in pitivi package in Ubuntu:
  New

Bug description:
  After getting this bug I was going to report it to the pitivi bug
  tracker, but it was already there, and they blamed it on compiz. So, I
  decided to report it here. The bug is quite simple, after opening the
  latest version and pressing the minimise button, Ubuntu crashes then
  restarts.

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

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

[Desktop-packages] [Bug 1446457] Re: [HDA-Intel - HDA Intel PCH, recording] No autoswitch

[Ben]

i also have this problem with my acer aspire E3 (phone not recognised
when pluggin in headset) but i am not sure how to read the solutions in
here. i understand code a bit but i am not a pro. i would prefer a
simple solution, some lines i have to type into the terminal each time i
want to use the headset.

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

Title:
  [HDA-Intel - HDA Intel PCH, recording] No autoswitch

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Acer E3-112
  Ubuntu 14.04, 14.10, 15.04 
  After plugging in headset only headset earphones detected, mic from headset 
not detected and recording is only from built in mic.

  Appending 'options snd-hda-intel model=dell-headset-multi' to
  /etc/modprobe.d/alsa-base.conf helps to tell xubuntu that headset mic
  may be plugged, but after plugging in, xubuntu doesn't automaticaly
  detect that mic is plugged, it can see only headset's earphones, so i
  need evreytime in pavucontrol tell xubuntu that mic is plugged in even
  after adding option.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mishurov   2000 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Apr 21 07:03:19 2015
  InstallationDate: Installed on 2015-04-04 (16 days ago)
  InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Type: No auto-switch between inputs
  Title: [HDA-Intel - HDA Intel PCH, recording] No autoswitch
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: R2
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd08/20/2014:svnAcer:pnNC-E3-112-C97Q:pvrV1.10:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: NC-E3-112-C97Q
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-04-21T06:35:28.960726

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

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

[Desktop-packages] [Bug 1446457] Re: [HDA-Intel - HDA Intel PCH, recording] No autoswitch

[Ben]

I added the driver to the alsa-base.conf and can now use the headset,
but it makes strange noises while using skype. but it's just on my side.
the other person does not experience this. i am sorry for this non-pro
stuff here, but i bought this acer aspire e3, built in an SSD and
uploaded Lubuntu, like I did before in other laptops an PCs. its awesome
and I thank all the guys that are contributing to ubuntu and specially
Lubuntu since I love the lean design. can the problem be the mentioned
Dell fix?

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

Title:
  [HDA-Intel - HDA Intel PCH, recording] No autoswitch

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Acer E3-112
  Ubuntu 14.04, 14.10, 15.04 
  After plugging in headset only headset earphones detected, mic from headset 
not detected and recording is only from built in mic.

  Appending 'options snd-hda-intel model=dell-headset-multi' to
  /etc/modprobe.d/alsa-base.conf helps to tell xubuntu that headset mic
  may be plugged, but after plugging in, xubuntu doesn't automaticaly
  detect that mic is plugged, it can see only headset's earphones, so i
  need evreytime in pavucontrol tell xubuntu that mic is plugged in even
  after adding option.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mishurov   2000 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Apr 21 07:03:19 2015
  InstallationDate: Installed on 2015-04-04 (16 days ago)
  InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Type: No auto-switch between inputs
  Title: [HDA-Intel - HDA Intel PCH, recording] No autoswitch
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: R2
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd08/20/2014:svnAcer:pnNC-E3-112-C97Q:pvrV1.10:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: NC-E3-112-C97Q
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-04-21T06:35:28.960726

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

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

[Desktop-packages] [Bug 1051348] Re: No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta

[Ben]

Comment #21 fixed the issue for me. Bug does also apply to current 12.10
release (upgrade: 16/11/2012).

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

Title:
  No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta

Status in Ubuntu-Secure-Remix:
  Fix Committed
Status in “network-manager” package in Ubuntu:
  Invalid

Bug description:
  I'm assuming (based on the prefix of /var/run/nm-dns-dnsmasq.conf)
  that this is a network-manager issue, though I'm not certain.

  I recently upgraded to Ubuntu 12.10 Beta 1 from a more-or-less stock
  installation of Ubuntu 12.04 (it had only been installed for about 3-4
  hours before the upgrade). This means that I am now using network-
  manager 0.9.6.0-0ubuntu7. On startup, network-manager connects to my
  router without any issues, but I am then unable to resolve any domain
  names (beyond localhost); I can't browse to any websites, ping any
  servers using their domain names, etc. There were no problems doing
  any of this while using 12.04, and I did not do anything other than
  perform the upgrade to 12.10 Beta 1 before this happened, so what I
  was expecting to happen was that I would continue to be able to use
  DNS as usual.

  On poking around a bit, I discovered that dnsmasq is running as it
  should be (listening on 127.0.1.1) but that the config file that it is
  trying to use, /var/run/nm-dns-dnsmasq.conf, is completely empty. This
  appears to be the source ofthe problem, as I can fix the issue by
  doing the following:

  1) Kill the /usr/sbin/dnsmasq process that is automatically started (by 
network-manager?). 
  2) Manually create /var/run/nm-dns-dnsmasq.conf and add lines such as the 
following (this line identifies an OpenDNS server):

  server=208.67.222.222

  3) Manually start the /usr/sbin/dnsmasq using exactly the same options
  that were passed to it when it was started automatically.

  So, I'm guessing this file should be non-empty. (Another workaround,
  by the way, is to manually create an /etc/resolv.conf file with
  appropriate nameserver lines and then restart the networking service,
  but AFAIK that solution simply bypasses dnsmasq entirely.)

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: network-manager 0.9.6.0-0ubuntu7
  ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3
  Uname: Linux 3.5.0-14-generic x86_64
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  Date: Sat Sep 15 13:02:05 2012
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.21  metric 
9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to quantal on 2012-09-15 (0 days ago)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Wired connection 1500ef8b0-f9cf-48f6-9409-aabea4121a84   
802-3-ethernet1347727737   Sat 15 Sep 2012 12:48:57 PM EDTyes   
no /org/freedesktop/NetworkManager/Settings/1
   NotThat!  968fa0a6-be87-47bb-b306-daf2188393e9   
802-11-wireless   1347728337   Sat 15 Sep 2012 12:58:57 PM EDTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.6.0connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-secure-remix/+bug/1051348/+subscriptions

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

[Desktop-packages] [Bug 1080580] [NEW] Xorg freeze

[Ben]

Public bug reported:

System hangs during boot and displays various boot messages, but does
not show the logon manager screen. You can switch to the console and
login successfully. This behaviour is not reproducable, but occurs quite
often (once each two days).

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xorg 1:7.7+1ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
Uname: Linux 3.5.0-18-generic x86_64
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
Date: Mon Nov 19 08:15:17 2012
DistroCodename: quantal
DistroVariant: ubuntu
GpuHangFrequency: Several times a week
InstallationDate: Installed on 2012-10-16 (33 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to quantal on 2012-11-10 (8 days ago)

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


** Tags: amd64 apport-bug freeze quantal running-unity 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/1080580

Title:
  Xorg freeze

Status in “xorg” package in Ubuntu:
  New

Bug description:
  System hangs during boot and displays various boot messages, but does
  not show the logon manager screen. You can switch to the console and
  login successfully. This behaviour is not reproducable, but occurs
  quite often (once each two days).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Mon Nov 19 08:15:17 2012
  DistroCodename: quantal
  DistroVariant: ubuntu
  GpuHangFrequency: Several times a week
  InstallationDate: Installed on 2012-10-16 (33 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to quantal on 2012-11-10 (8 days ago)

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

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

[Desktop-packages] [Bug 1080580] Re: Xorg freeze

[Ben]

Logfiles during hang from console login copied from /var/log:
- bootlog
- console-setup.log
- container-detect.log
- dbus.log
- dmesg
- faillog
- hybrid-gfx.log
- kern.log
- syslog
- Xorg.0.log
- x-0-greeter.log
- rsyslog.log
- module-init-tools.log
- x-0.log
- ureadahead.log
- lightdm.log

** Attachment added: "Logfiles during hang from console login"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1080580/+attachment/3438296/+files/boothang-log.tar.gz

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

Title:
  Xorg freeze

Status in “xorg” package in Ubuntu:
  New

Bug description:
  System hangs during boot and displays various boot messages, but does
  not show the logon manager screen. You can switch to the console and
  login successfully. This behaviour is not reproducable, but occurs
  quite often (once each two days).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Mon Nov 19 08:15:17 2012
  DistroCodename: quantal
  DistroVariant: ubuntu
  GpuHangFrequency: Several times a week
  InstallationDate: Installed on 2012-10-16 (33 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to quantal on 2012-11-10 (8 days ago)

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

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

[Desktop-packages] [Bug 1080584] [NEW] rhythmbox mp3 and ogg ripping of cds fails

[Ben]

Public bug reported:

When starting to rip CD tracks to mp3 files (or ogg), rhythmboox
complains about missing plugins and starts downloading them. After
sucessfull download, the ripping fails. Watching the plugin install, I
think I have seen some text regrading "i386", while I use a 64-bit
platform? Two weeks ago the ripping worked fine (and without previous
download of plugins).

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: rhythmbox 2.97-1ubuntu5
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
Uname: Linux 3.5.0-18-generic x86_64
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
Date: Mon Nov 19 08:35:13 2012
InstallationDate: Installed on 2012-10-16 (33 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: rhythmbox
UpgradeStatus: Upgraded to quantal on 2012-11-10 (8 days ago)

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


** Tags: amd64 apport-bug quantal running-unity

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

Title:
  rhythmbox mp3 and ogg ripping of cds fails

Status in “rhythmbox” package in Ubuntu:
  New

Bug description:
  When starting to rip CD tracks to mp3 files (or ogg), rhythmboox
  complains about missing plugins and starts downloading them. After
  sucessfull download, the ripping fails. Watching the plugin install, I
  think I have seen some text regrading "i386", while I use a 64-bit
  platform? Two weeks ago the ripping worked fine (and without previous
  download of plugins).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: rhythmbox 2.97-1ubuntu5
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Mon Nov 19 08:35:13 2012
  InstallationDate: Installed on 2012-10-16 (33 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: rhythmbox
  UpgradeStatus: Upgraded to quantal on 2012-11-10 (8 days ago)

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

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

[Desktop-packages] [Bug 1078662] Re: Not Quick-Listing VPN Connections

[Ben]

I experience the same issue.

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

Title:
  Not Quick-Listing VPN Connections

Status in NetworkManager VPNC plugin:
  New
Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  I have number of cisco vpn connections configured using the network-
  manager-vpnc addon package.

  Typically, I'm able to connect to them by simply clicking on the
  networking indicator/applet icon and going to "VPN Connections" menu.
  There, I'll normally see a list of all VPNC connections I've
  configured. And then, by simply clicking one of them a connection
  becomes established.

  However, after rebooting, I now go there, and none of my VPN
  connections are listed under "VPN Connections". Yet, if I click
  "configure vpn", and go to the VPN tab (in the dialog that appears),
  the connections are definitely still there.

  Why is it that sometimes those VPN connections (I've configured) don't
  get quick-listed under the "VPN Connections" menu?

  It is annoying because when they are not quick-listed there, it
  requires additional steps for me to establish the connection.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: network-manager 0.9.6.0-0ubuntu7
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Wed Nov 14 04:42:16 2012
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2012-10-19 (26 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  IpRoute:
   default via 192.168.77.1 dev eth0  proto static
   169.254.0.0/16 dev eth0  scope link  metric 1000
   192.168.77.0/24 dev eth0  proto kernel  scope link  src 192.168.77.246  
metric 1
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:

  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH
   Best Transportation   b49dbee6-30c1-4101-b59c-8174c537026f   vpn 
  1352874709   Wed 14 Nov 2012 12:31:49 AM CSTnono 
/org/freedesktop/NetworkManager/Settings/2
   Best Stainless72d8235a-7994-4b39-8d31-984c40033cc6   vpn 
  1352736940   Mon 12 Nov 2012 10:15:40 AM CSTnono 
/org/freedesktop/NetworkManager/Settings/1
   Video Surveillance057ac134-a096-4aae-96de-b04a3bc9f6e3   
802-11-wireless   1352172603   Mon 05 Nov 2012 09:30:03 PM CSTyes   
no /org/freedesktop/NetworkManager/Settings/0
   Wired connection 1594d390a-b667-4c50-b31d-83503151b02b   
802-3-ethernet1352889611   Wed 14 Nov 2012 04:40:11 AM CSTyes   
no /org/freedesktop/NetworkManager/Settings/3
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH
   eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN
   running 0.9.6.0connected   enabled   enabled 
enabledenabled disabled

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

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

[Desktop-packages] [Bug 1104063] [NEW] X Server Crashes

[ben]

Public bug reported:

X Server crashes with the following error

[ 92342.726] (EE) Backtrace:
[ 92342.756] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7fbf591b6b76]
[ 92342.756] (EE) 1: /usr/bin/X (0x7fbf5900e000+0x1ac9a9) [0x7fbf591ba9a9]
[ 92342.756] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fbf58334000+0xfcb0) [0x7fbf58343cb0]
[ 92342.756] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(0x7fbf57ea2000+0x71e9d) [0x7fbf57f13e9d]
[ 92342.756] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(0x7fbf57ea2000+0x7220f) [0x7fbf57f1420f]
[ 92342.756] (EE) 5: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(pixman_blt+0x52) [0x7fbf57eac472]
[ 92342.756] (EE) 6: /usr/lib/xorg/modules/libfb.so (fbCopyNtoN+0x343) 
[0x7fbf54aa4b63]
[ 92342.756] (EE) 7: 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/glesx.so 
(0x7fbf52593000+0x8cd81) [0x7fbf5261fd81]
[ 92342.756] (EE) 8: 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/glesx.so 
(0x7fbf52593000+0x8ee45) [0x7fbf52621e45]
[ 92342.756] (EE) 9: /usr/bin/X (0x7fbf5900e000+0x1325d9) [0x7fbf591405d9]
[ 92342.756] (EE) 10: /usr/bin/X (0x7fbf5900e000+0xe5085) [0x7fbf590f3085]
[ 92342.756] (EE) 11: /usr/bin/X (0x7fbf5900e000+0xe5ea6) [0x7fbf590f3ea6]
[ 92342.756] (EE) 12: /usr/bin/X (0x7fbf5900e000+0xe490c) [0x7fbf590f290c]
[ 92342.756] (EE) 13: /usr/bin/X (0x7fbf5900e000+0x7e8c6) [0x7fbf5908c8c6]
[ 92342.756] (EE) 14: /usr/bin/X (MapWindow+0x1a2) [0x7fbf5908f662]
[ 92342.756] (EE) 15: /usr/bin/X (0x7fbf5900e000+0x502d0) [0x7fbf5905e2d0]
[ 92342.757] (EE) 16: /usr/bin/X (0x7fbf5900e000+0x55a91) [0x7fbf59063a91]
[ 92342.757] (EE) 17: /usr/bin/X (0x7fbf5900e000+0x4456a) [0x7fbf5905256a]
[ 92342.757] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) 
[0x7fbf56fb976d]
[ 92342.757] (EE) 19: /usr/bin/X (0x7fbf5900e000+0x448ad) [0x7fbf590528ad]
[ 92342.757] (EE) 
[ 92342.757] (EE) Segmentation fault at address 0x7fbf3507f000
[ 92342.757] 
Fatal server error:
[ 92342.757] Caught signal 11 (Segmentation fault). Server aborting
[ 92342.757] 
[ 92342.757] (EE)

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

** Attachment added: "Xorg.0.log.old"
   
https://bugs.launchpad.net/bugs/1104063/+attachment/3498195/+files/Xorg.0.log.old

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

Title:
  X Server Crashes

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

Bug description:
  X Server crashes with the following error

  [ 92342.726] (EE) Backtrace:
  [ 92342.756] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7fbf591b6b76]
  [ 92342.756] (EE) 1: /usr/bin/X (0x7fbf5900e000+0x1ac9a9) [0x7fbf591ba9a9]
  [ 92342.756] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fbf58334000+0xfcb0) [0x7fbf58343cb0]
  [ 92342.756] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(0x7fbf57ea2000+0x71e9d) [0x7fbf57f13e9d]
  [ 92342.756] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(0x7fbf57ea2000+0x7220f) [0x7fbf57f1420f]
  [ 92342.756] (EE) 5: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(pixman_blt+0x52) [0x7fbf57eac472]
  [ 92342.756] (EE) 6: /usr/lib/xorg/modules/libfb.so (fbCopyNtoN+0x343) 
[0x7fbf54aa4b63]
  [ 92342.756] (EE) 7: 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/glesx.so 
(0x7fbf52593000+0x8cd81) [0x7fbf5261fd81]
  [ 92342.756] (EE) 8: 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/glesx.so 
(0x7fbf52593000+0x8ee45) [0x7fbf52621e45]
  [ 92342.756] (EE) 9: /usr/bin/X (0x7fbf5900e000+0x1325d9) [0x7fbf591405d9]
  [ 92342.756] (EE) 10: /usr/bin/X (0x7fbf5900e000+0xe5085) [0x7fbf590f3085]
  [ 92342.756] (EE) 11: /usr/bin/X (0x7fbf5900e000+0xe5ea6) [0x7fbf590f3ea6]
  [ 92342.756] (EE) 12: /usr/bin/X (0x7fbf5900e000+0xe490c) [0x7fbf590f290c]
  [ 92342.756] (EE) 13: /usr/bin/X (0x7fbf5900e000+0x7e8c6) [0x7fbf5908c8c6]
  [ 92342.756] (EE) 14: /usr/bin/X (MapWindow+0x1a2) [0x7fbf5908f662]
  [ 92342.756] (EE) 15: /usr/bin/X (0x7fbf5900e000+0x502d0) [0x7fbf5905e2d0]
  [ 92342.757] (EE) 16: /usr/bin/X (0x7fbf5900e000+0x55a91) [0x7fbf59063a91]
  [ 92342.757] (EE) 17: /usr/bin/X (0x7fbf5900e000+0x4456a) [0x7fbf5905256a]
  [ 92342.757] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xed) [0x7fbf56fb976d]
  [ 92342.757] (EE) 19: /usr/bin/X (0x7fbf5900e000+0x448ad) [0x7fbf590528ad]
  [ 92342.757] (EE) 
  [ 92342.757] (EE) Segmentation fault at address 0x7fbf3507f000
  [ 92342.757] 
  Fatal server error:
  [ 92342.757] Caught signal 11 (Segmentation fault). Server aborting
  [ 92342.757] 
  [ 92342.757] (EE)

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

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

[Desktop-packages] [Bug 1104063] Re: X Server Crashes

[ben]

** Attachment added: "xorg.conf"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1104063/+attachment/3498196/+files/xorg.conf

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

Title:
  X Server Crashes

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

Bug description:
  X Server crashes with the following error

  [ 92342.726] (EE) Backtrace:
  [ 92342.756] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7fbf591b6b76]
  [ 92342.756] (EE) 1: /usr/bin/X (0x7fbf5900e000+0x1ac9a9) [0x7fbf591ba9a9]
  [ 92342.756] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fbf58334000+0xfcb0) [0x7fbf58343cb0]
  [ 92342.756] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(0x7fbf57ea2000+0x71e9d) [0x7fbf57f13e9d]
  [ 92342.756] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(0x7fbf57ea2000+0x7220f) [0x7fbf57f1420f]
  [ 92342.756] (EE) 5: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(pixman_blt+0x52) [0x7fbf57eac472]
  [ 92342.756] (EE) 6: /usr/lib/xorg/modules/libfb.so (fbCopyNtoN+0x343) 
[0x7fbf54aa4b63]
  [ 92342.756] (EE) 7: 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/glesx.so 
(0x7fbf52593000+0x8cd81) [0x7fbf5261fd81]
  [ 92342.756] (EE) 8: 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/glesx.so 
(0x7fbf52593000+0x8ee45) [0x7fbf52621e45]
  [ 92342.756] (EE) 9: /usr/bin/X (0x7fbf5900e000+0x1325d9) [0x7fbf591405d9]
  [ 92342.756] (EE) 10: /usr/bin/X (0x7fbf5900e000+0xe5085) [0x7fbf590f3085]
  [ 92342.756] (EE) 11: /usr/bin/X (0x7fbf5900e000+0xe5ea6) [0x7fbf590f3ea6]
  [ 92342.756] (EE) 12: /usr/bin/X (0x7fbf5900e000+0xe490c) [0x7fbf590f290c]
  [ 92342.756] (EE) 13: /usr/bin/X (0x7fbf5900e000+0x7e8c6) [0x7fbf5908c8c6]
  [ 92342.756] (EE) 14: /usr/bin/X (MapWindow+0x1a2) [0x7fbf5908f662]
  [ 92342.756] (EE) 15: /usr/bin/X (0x7fbf5900e000+0x502d0) [0x7fbf5905e2d0]
  [ 92342.757] (EE) 16: /usr/bin/X (0x7fbf5900e000+0x55a91) [0x7fbf59063a91]
  [ 92342.757] (EE) 17: /usr/bin/X (0x7fbf5900e000+0x4456a) [0x7fbf5905256a]
  [ 92342.757] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xed) [0x7fbf56fb976d]
  [ 92342.757] (EE) 19: /usr/bin/X (0x7fbf5900e000+0x448ad) [0x7fbf590528ad]
  [ 92342.757] (EE) 
  [ 92342.757] (EE) Segmentation fault at address 0x7fbf3507f000
  [ 92342.757] 
  Fatal server error:
  [ 92342.757] Caught signal 11 (Segmentation fault). Server aborting
  [ 92342.757] 
  [ 92342.757] (EE)

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

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

[Desktop-packages] [Bug 1080580] Re: Xorg freeze

[Ben]

apport information

** Tags added: apport-collected

** Description changed:

  System hangs during boot and displays various boot messages, but does
  not show the logon manager screen. You can switch to the console and
  login successfully. This behaviour is not reproducable, but occurs quite
  often (once each two days).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Mon Nov 19 08:15:17 2012
  DistroCodename: quantal
  DistroVariant: ubuntu
  GpuHangFrequency: Several times a week
  InstallationDate: Installed on 2012-10-16 (33 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to quantal on 2012-11-10 (8 days ago)
+ --- 
+ ApportVersion: 2.6.1-0ubuntu10
+ Architecture: amd64
+ DistroCodename: quantal
+ DistroRelease: Ubuntu 12.10
+ DistroVariant: ubuntu
+ InstallationDate: Installed on 2012-10-16 (140 days ago)
+ InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
+ MarkForUpload: True
+ Package: xorg 1:7.7+1ubuntu4
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=de_DE.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 3.5.0-25.39-generic 3.5.7.4
+ Tags:  quantal running-unity ubuntu
+ Uname: Linux 3.5.0-25-generic x86_64
+ UnreportableReason: Please work this issue through technical support channels 
first.
+ UpgradeStatus: Upgraded to quantal on 2012-11-10 (115 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1080580/+attachment/3558825/+files/Dependencies.txt

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

Title:
  Xorg freeze

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  System hangs during boot and displays various boot messages, but does
  not show the logon manager screen. You can switch to the console and
  login successfully. This behaviour is not reproducable, but occurs
  quite often (once each two days).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Mon Nov 19 08:15:17 2012
  DistroCodename: quantal
  DistroVariant: ubuntu
  GpuHangFrequency: Several times a week
  InstallationDate: Installed on 2012-10-16 (33 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to quantal on 2012-11-10 (8 days ago)
  --- 
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  DistroCodename: quantal
  DistroRelease: Ubuntu 12.10
  DistroVariant: ubuntu
  InstallationDate: Installed on 2012-10-16 (140 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  Package: xorg 1:7.7+1ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.5.0-25.39-generic 3.5.7.4
  Tags:  quantal running-unity ubuntu
  Uname: Linux 3.5.0-25-generic x86_64
  UnreportableReason: Please work this issue through technical support channels 
first.
  UpgradeStatus: Upgraded to quantal on 2012-11-10 (115 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 886327] Re: Nautilus window closes when unmounting currently explored filesystem

[Ben]

Confirmed in:

Ubuntu 12.04.2 fresh install
Unity 2d
Nautilus 3.4.2

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

Title:
  Nautilus window closes when unmounting currently explored filesystem

Status in Nautilus:
  Expired
Status in “nautilus” package in Ubuntu:
  Triaged

Bug description:
  What happens:
  In Nautilus, when exploring a mountable filesystem of a device (having it 
open in the active window/tab), unmounting this device by the unmount icon on 
the side panel causes whole window to close, having immediately followed 
unmounting. If the currently explored folder isn't the one on the filesystem 
that we unmount, then nothing happens to Nautilus window.

  Steps to reproduce:
  1. Mount a filesystem.
  2. Open Nautilus and explore the content of said filesystem.
  3. Unmount said filesystem, for example using the unmount icon on the side 
panel.
  4. In the current state of things, Nautilus window will close immediately due 
to unmount.

  What should happen:
  After unmounting an actively explored filesystem, the window/tab should 
change its focus to a default element, such as computer:/// - like it was 
before, or perhaps /media, /home?

  Alternatively:
  Because some consider the desired behaviour as a bug 
(https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/23293), there should 
be a possibility to change this behaviour to the way the end user wants it to 
be - either closing the Nautilus window/tab or changing address to a default 
element.

  It is similar to how Windows 7 explorer.exe works. I personally find
  this annoying - I have close to twenty partitions total and I like to
  unmount those on which work I have currently finished without fear of
  closing the program itself.

  It is only a matter of the last few days/weeks that I experienced this
  behaviour. Some time ago it used to work as described in "What should
  happen" section.

  Description:  Ubuntu 11.10
  Release:  11.10

  nautilus:
    Installed: 1:3.2.1-0ubuntu2
    Candidate: 1:3.2.1-0ubuntu2

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

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

[Desktop-packages] [Bug 491555] Re: In gedit's Replace window, a single Tab does not move focus from Search to Replace field

[Ben]

I confirmed this is still an issue with:

Ubuntu 12.04.2 64bit Alternate, Fresh Install
gEdit 3.4.1

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

Title:
  In gedit's Replace window, a single Tab does not move focus from
  Search to Replace field

Status in Light-Weight Text Editor for Gnome:
  New
Status in One Hundred Paper Cuts:
  Triaged
Status in “gedit” package in Ubuntu:
  Triaged

Bug description:
  When the user opens the Replace dialog (Search  > Replace...), the
  default input focus lies in the Search field. The user types the
  search string, and presses tab to enter the replacement string, but
  the input focus moves from the Search field to the choice disclosure
  control instead of to the Replace field. Pressing Tab in the Search
  field should move input focus to the Replace field. The search field
  can recall history by pressing Up/Down arrows, and offers
  autocomplete, so changing the Tab focus chain does not prevent the
  user from recalling a previous search string.

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

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

[Desktop-packages] [Bug 1173955] [NEW] Rhythmbox infinite loop fails

[Ben]

Public bug reported:

For a playlist with songs (wave files) the transition from on song to
another fails often. Sometimes the loop stops at the end of a song.
Sometimes the player continous at some random position in the next song.

In 12.10 this problem did not exist. After upgrading to 13.04 the
problem started.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: libgstreamer0.10-0 0.10.36-1ubuntu2
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: Sun Apr 28 15:34:12 2013
InstallationDate: Installed on 2012-10-16 (194 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: gstreamer0.10
UpgradeStatus: Upgraded to raring on 2013-04-28 (0 days ago)

** Affects: gstreamer0.10 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug raring

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

Title:
  Rhythmbox infinite loop fails

Status in “gstreamer0.10” package in Ubuntu:
  New

Bug description:
  For a playlist with songs (wave files) the transition from on song to
  another fails often. Sometimes the loop stops at the end of a song.
  Sometimes the player continous at some random position in the next
  song.

  In 12.10 this problem did not exist. After upgrading to 13.04 the
  problem started.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libgstreamer0.10-0 0.10.36-1ubuntu2
  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: Sun Apr 28 15:34:12 2013
  InstallationDate: Installed on 2012-10-16 (194 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer0.10
  UpgradeStatus: Upgraded to raring on 2013-04-28 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1173955/+subscriptions

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

[Desktop-packages] [Bug 1173957] [NEW] Pulseaudio stereo mixer for audio recording is missing

[Ben]

Public bug reported:

The feature to record the currently played audio stream - known to me as
the stereo mixer - disappeared from the drop down menu for recoding
devices in, for example, audacity. As far as I understood, this is due
to a failure of the underlying audio layer.

This problem appeared in 12.10 already (after some dist-upgrade in
march) and continous to not be available in 13.04 now.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: pulseaudio 1:3.0-0ubuntu6
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
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  benjamin   6940 F pulseaudio
 /dev/snd/controlC0:  benjamin   6940 F pulseaudio
 /dev/snd/controlC1:  benjamin   6940 F pulseaudio
Date: Sun Apr 28 15:47:35 2013
InstallationDate: Installed on 2012-10-16 (194 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to raring on 2013-04-28 (0 days ago)
dmi.bios.date: 08/10/2012
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: GA-78LMT-USB3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd08/10/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-78LMT-USB3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug raring

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

Title:
  Pulseaudio stereo mixer for audio recording is missing

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  The feature to record the currently played audio stream - known to me
  as the stereo mixer - disappeared from the drop down menu for recoding
  devices in, for example, audacity. As far as I understood, this is due
  to a failure of the underlying audio layer.

  This problem appeared in 12.10 already (after some dist-upgrade in
  march) and continous to not be available in 13.04 now.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: pulseaudio 1:3.0-0ubuntu6
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  benjamin   6940 F pulseaudio
   /dev/snd/controlC0:  benjamin   6940 F pulseaudio
   /dev/snd/controlC1:  benjamin   6940 F pulseaudio
  Date: Sun Apr 28 15:47:35 2013
  InstallationDate: Installed on 2012-10-16 (194 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to raring on 2013-04-28 (0 days ago)
  dmi.bios.date: 08/10/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd08/10/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1173966] [NEW] Nautilus bookmarks for smb shares disappear

[Ben]

Public bug reported:

Since upgrade to 13.04 the bookmarks for smb shares disappear in the
navigation bar at the left. Choosing files and bookmarks from the menu
bar shows all bookmarks including the smb shares. Rearranging the smb
shares in the bookmarks crashes nautilus. Restarting nautilus after the
crash makes the smb shares reappear inthe navigation bar.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: nautilus 1:3.6.3-0ubuntu16
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
Date: Sun Apr 28 16:17:23 2013
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'geometry' b"'927x621+991+426'"
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'237'
MarkForUpload: True
SourcePackage: nautilus
UpgradeStatus: Upgraded to raring on 2013-04-26 (2 days ago)

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


** Tags: amd64 apport-bug raring

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

Title:
  Nautilus bookmarks for smb shares disappear

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  Since upgrade to 13.04 the bookmarks for smb shares disappear in the
  navigation bar at the left. Choosing files and bookmarks from the menu
  bar shows all bookmarks including the smb shares. Rearranging the smb
  shares in the bookmarks crashes nautilus. Restarting nautilus after
  the crash makes the smb shares reappear inthe navigation bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun Apr 28 16:17:23 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'927x621+991+426'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'237'
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-04-26 (2 days ago)

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

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

[Desktop-packages] [Bug 1081298] [NEW] LightDM fails to display background image

[Ben]

Public bug reported:

Randomliy lightdm fails to load the background image for the login
screen. This happens for background images that are part of the default
installation of Ubuntu.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: lightdm 1.4.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
Uname: Linux 3.5.0-18-generic x86_64
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
Date: Tue Nov 20 21:31:02 2012
EcryptfsInUse: Yes
InstallationDate: Installed on 2011-10-26 (391 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MarkForUpload: True
SourcePackage: lightdm
UpgradeStatus: Upgraded to quantal on 2012-11-17 (3 days ago)

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


** Tags: amd64 apport-bug quantal running-unity

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

Title:
  LightDM fails to display background image

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Randomliy lightdm fails to load the background image for the login
  screen. This happens for background images that are part of the
  default installation of Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: lightdm 1.4.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Tue Nov 20 21:31:02 2012
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-10-26 (391 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to quantal on 2012-11-17 (3 days ago)

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

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

[Desktop-packages] [Bug 1082129] [NEW] Cheese crashes during the recording videos

[Ben]

Public bug reported:

Starting chesse and capturing pictures works fine. Switching to video
recording mode works, but immediatly after pressing the start recoding
button, Cheese crashs reproducable.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: cheese 3.6.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
Uname: Linux 3.5.0-18-generic x86_64
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
Date: Thu Nov 22 19:10:23 2012
InstallationDate: Installed on 2012-10-16 (37 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: cheese
UpgradeStatus: Upgraded to quantal on 2012-11-10 (12 days ago)

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


** Tags: amd64 apport-bug quantal running-unity

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

Title:
  Cheese crashes during the recording videos

Status in “cheese” package in Ubuntu:
  New

Bug description:
  Starting chesse and capturing pictures works fine. Switching to video
  recording mode works, but immediatly after pressing the start recoding
  button, Cheese crashs reproducable.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cheese 3.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Thu Nov 22 19:10:23 2012
  InstallationDate: Installed on 2012-10-16 (37 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: cheese
  UpgradeStatus: Upgraded to quantal on 2012-11-10 (12 days ago)

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

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

[Desktop-packages] [Bug 1084204] [NEW] Unmount message is not displayed

[Ben]

Public bug reported:

When writing to external USB devices (e.g., USB sticks or USB HDD), the
write progress bar is displayed correctly. After the write progress bar
is full and the progress window stops displaying, the status light of
the device signals, that still data is written to the device.
Previously, when you pressed the unmount button in nautilus, a window
apeared and displayed a warning not to remove the device. Since about
two weeks, this warning message is not displayed any more. When removing
the device before the write cache is empty, the filesystem of the device
is corrupted on the next mount. This behaviour is reproducable and
occurs every time. It also happens on other installation of 12.10 as
well.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
Uname: Linux 3.5.0-18-generic x86_64
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
Date: Wed Nov 28 20:03:37 2012
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'geometry' b"'917x683+65+24'"
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'237'
MarkForUpload: True
SourcePackage: nautilus
UpgradeStatus: Upgraded to quantal on 2012-11-13 (15 days ago)

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


** Tags: amd64 apport-bug quantal running-unity

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

Title:
  Unmount message is not displayed

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  When writing to external USB devices (e.g., USB sticks or USB HDD),
  the write progress bar is displayed correctly. After the write
  progress bar is full and the progress window stops displaying, the
  status light of the device signals, that still data is written to the
  device. Previously, when you pressed the unmount button in nautilus, a
  window apeared and displayed a warning not to remove the device. Since
  about two weeks, this warning message is not displayed any more. When
  removing the device before the write cache is empty, the filesystem of
  the device is corrupted on the next mount. This behaviour is
  reproducable and occurs every time. It also happens on other
  installation of 12.10 as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Wed Nov 28 20:03:37 2012
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'917x683+65+24'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'237'
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to quantal on 2012-11-13 (15 days ago)

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

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

[Desktop-packages] [Bug 1087495] [NEW] package libglib2.0-data 2.16.6-0ubuntu1.2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

[Ben]

Public bug reported:

Won't install.  Have tried multiple times

ProblemType: Package
DistroRelease: Ubuntu 12.10
Package: libglib2.0-data 2.16.6-0ubuntu1.2
ProcVersionSignature: Ubuntu 3.5.0-18.18-lowlatency 3.5.7
Uname: Linux 3.5.0-18-lowlatency i686
ApportVersion: 2.6.1-0ubuntu6
Architecture: i386
Date: Thu Dec  6 18:42:12 2012
ErrorMessage: subprocess new pre-installation script returned error exit status 
1
InstallationDate: Installed on 2012-07-31 (128 days ago)
InstallationMedia: Ubuntu-Studio 12.04 "Precise Pangolin" - Release i386 
(20120423)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: glib2.0
Title: package libglib2.0-data 2.16.6-0ubuntu1.2 failed to install/upgrade: 
subprocess new pre-installation script returned error exit status 1
UpgradeStatus: Upgraded to quantal on 2012-10-31 (36 days ago)

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 quantal

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

Title:
  package libglib2.0-data 2.16.6-0ubuntu1.2 failed to install/upgrade:
  subprocess new pre-installation script returned error exit status 1

Status in “glib2.0” package in Ubuntu:
  New

Bug description:
  Won't install.  Have tried multiple times

  ProblemType: Package
  DistroRelease: Ubuntu 12.10
  Package: libglib2.0-data 2.16.6-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.5.0-18.18-lowlatency 3.5.7
  Uname: Linux 3.5.0-18-lowlatency i686
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  Date: Thu Dec  6 18:42:12 2012
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  InstallationDate: Installed on 2012-07-31 (128 days ago)
  InstallationMedia: Ubuntu-Studio 12.04 "Precise Pangolin" - Release i386 
(20120423)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: glib2.0
  Title: package libglib2.0-data 2.16.6-0ubuntu1.2 failed to install/upgrade: 
subprocess new pre-installation script returned error exit status 1
  UpgradeStatus: Upgraded to quantal on 2012-10-31 (36 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1087495/+subscriptions

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

[Desktop-packages] [Bug 982889] Re: X trying to start before plymouth has finished using the drm driver

[ben]

Can confirm this bug on recent ubuntu 12.10.  The workaround from Bryce
Harrington (comment #5) fixed the problem for me. thanks!

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

Title:
  X trying to start before plymouth has finished using the drm driver

Status in “libdrm” package in Ubuntu:
  Incomplete
Status in “linux” package in Ubuntu:
  Incomplete
Status in “xorg-server” package in Ubuntu:
  Confirmed

Bug description:
  X server fails to start the first time after boot, it works fine when
  I start it again.

  Looks like a race condition with intel drm initialization, i guess X
  tries to start faster than drm driver is initialized so it fails.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Mon Apr 16 10:35:28 2012
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. Device [1462:7750]
   Advanced Micro Devices [AMD] nee ATI Barts XT [ATI Radeon HD 6800 Series] 
[1002:6738] (prog-if 00 [VGA controller])
 Subsystem: Giga-byte Technology Device [1458:21fa]
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  MachineType: MSI MS-7750
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-23-generic 
root=/dev/mapper/ssd-ubuntu--precise ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V4.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z68A-G43 (G3) (MS-7750)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV4.0:bd08/25/2011:svnMSI:pnMS-7750:pvr1.0:rvnMSI:rnZ68A-G43(G3)(MS-7750):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7750
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.7.6-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

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

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

[Desktop-packages] [Bug 1310746] Re: NetworkManager wired ethernet times out waiting for dhcp on 14.04 trusty tahr

[Ben]

confirmed fresh install of 14.04 with all updates as of 30 Jun 2014.
sometimes I have to disconnect the cable from both PC and switch, then
reconnect both and it will work. very random.

network-manager 0.9.8.8-0ubuntu7 amd64

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

Title:
  NetworkManager wired ethernet times out waiting for dhcp on 14.04
  trusty tahr

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

Bug description:
  I'm experiencing dhcp timeouts on 14.04 that I didn't experience in
  earlier releases (13.10 and 12.04 are in use in the office). Others in
  my office have similar complaints that "wired ethernet stops working
  in 14.04" which all equate to a dhcp timeout. When switching back to
  13.10 dhcp works flawlessly.

  network-manager 0.9.8.8-0ubuntu7 (the current version on trusty) contains the 
following changelog:
  * debian/tests/nm: Bump DHCP timeouts from 15 to 20 seconds, something in
  the stack got even slower as it used to be.
* debian/tests/nm: With the patch in 0.9.8.8-0ubuntu5, interfaces with PE
  disabled still get a temporary IP. Disable that check for now.
   -- Martin Pitt <_...@ubuntu.com>   Wed, 09 Apr 2014 15:41:11 +0200

  I don't think increasing the timeout in the test in order to get it to
  pass is the correct approach. It's likely masking the underlying issue
  that we're experiencing.

  -- 
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:  Ubuntu 14.04 LTS
  Release:  14.04
   
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  network-manager:
Installed: 0.9.8.8-0ubuntu7
Candidate: 0.9.8.8-0ubuntu7
Version table:
   *** 0.9.8.8-0ubuntu7 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  isc-dhcp-client:
Installed: 4.2.4-7ubuntu12
Candidate: 4.2.4-7ubuntu12
Version table:
   *** 4.2.4-7ubuntu12 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  isc-dhcp-common:
Installed: 4.2.4-7ubuntu12
Candidate: 4.2.4-7ubuntu12
Version table:
   *** 4.2.4-7ubuntu12 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  Ethernet to "just work"

  4) What happened instead
  Wired ethernet times out waiting for a dhcp connection. This does not occur 
on the same hardware using past releases of Ubuntu. It also doesn't happen when 
connecting via wireless.

  
  debug logs attached: sudo python debug-helper.py --nm debug ; tail -n0 -f 
/var/log/syslog | sed -e '/get_active_ap/d' -e '/dump_route/d' > /tmp/syslog

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

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

[Desktop-packages] [Bug 1313892] [NEW] Display Brightness not Adjustable

[Ben]

Public bug reported:

After upgrade to 14.04, display brightness is does no longer adjustable
through system configuration.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,imgpng,vpswitch,place,gnomecompat,move,mousepoll,resize,snap,grid,unitymtgrabhandles,wall,session,regex,animation,fade,workarounds,expo,scale,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Apr 28 21:45:36 2014
DistUpgraded: 2014-04-22 15:37:30,834 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 4.3.10, 3.11.0-19-generic, x86_64: installed
 virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Sony Corporation Device [104d:9084]
MachineType: Sony Corporation VPCZ21C5E
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/volgrp0-vol1 ro splash quiet nomdmonddf nomdmonisw vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to trusty on 2014-04-22 (6 days ago)
dmi.bios.date: 06/16/2011
dmi.bios.vendor: INSYDE
dmi.bios.version: R0170H5
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnINSYDE:bvrR0170H5:bd06/16/2011:svnSonyCorporation:pnVPCZ21C5E:pvrJ004MG71:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VPCZ21C5E
dmi.product.version: J004MG71
dmi.sys.vendor: Sony Corporation
version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
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: Sat Apr 26 16:17:49 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id  37 
 vendor MS_
xserver.version: 2:1.15.1-0ubuntu2

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


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

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

Title:
  Display Brightness not Adjustable

Status in “xorg” package in Ubuntu:
  New

Bug description:
  After upgrade to 14.04, display brightness is does no longer
  adjustable through system configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,imgpng,vpswitch,place,gnomecompat,move,mousepoll,resize,snap,grid,unitymtgrabhandles,wall,session,regex,animation,fade,workarounds,expo,scale,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 28 21:45:36 2014
  DistUpgraded: 2014-04-22 15:37:30,834 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.10, 3.11.0-19-generic, x86_64: installed
   virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Device [104d:9084]
  MachineType: Sony Corporation VPCZ21C5E
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/volgrp0-vol1 ro splash quiet nomdmonddf nomdmonisw vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-04-22 (6 days ago)
 

[Desktop-packages] [Bug 1316673] Re: Pressing umount button leads to sticky icon as mouse pointer

[Ben]

** Attachment added: "Screenshoot 1"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1316673/+attachment/4106605/+files/screenshoot_1.png

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

Title:
  Pressing umount button leads to sticky icon as mouse pointer

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  When pressing the umount button in nautilus (see screenshoot_1.png,
  #1), the mouse pointer changes to a hand - which is not recoreded by
  the screenshoot application - and carries around one of the fav-links.
  Pressing ESC solves the problem. This happens every time I press
  umount.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May  6 17:52:28 2014
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'owner', 'group', 'mime_type', 
'where', 'permissions', 'date_accessed']"
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to trusty on 2014-04-22 (14 days ago)

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

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

[Desktop-packages] [Bug 1316673] [NEW] Pressing umount button leads to sticky icon as mouse pointer

[Ben]

Public bug reported:

When pressing the umount button in nautilus (see screenshoot_1.png, #1),
the mouse pointer changes to a hand - which is not recoreded by the
screenshoot application - and carries around one of the fav-links.
Pressing ESC solves the problem. This happens every time I press umount.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: nautilus 1:3.10.1-0ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Tue May  6 17:52:28 2014
GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'owner', 'group', 'mime_type', 
'where', 'permissions', 'date_accessed']"
SourcePackage: nautilus
UpgradeStatus: Upgraded to trusty on 2014-04-22 (14 days ago)

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


** Tags: amd64 apport-bug trusty

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

Title:
  Pressing umount button leads to sticky icon as mouse pointer

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  When pressing the umount button in nautilus (see screenshoot_1.png,
  #1), the mouse pointer changes to a hand - which is not recoreded by
  the screenshoot application - and carries around one of the fav-links.
  Pressing ESC solves the problem. This happens every time I press
  umount.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May  6 17:52:28 2014
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'owner', 'group', 'mime_type', 
'where', 'permissions', 'date_accessed']"
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to trusty on 2014-04-22 (14 days ago)

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

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

[Desktop-packages] [Bug 1316673] Re: Pressing umount button leads to sticky icon as mouse pointer

[Ben]

** Attachment added: "Screenshoot 2"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1316673/+attachment/4106606/+files/screenshoot_2.png

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

Title:
  Pressing umount button leads to sticky icon as mouse pointer

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  When pressing the umount button in nautilus (see screenshoot_1.png,
  #1), the mouse pointer changes to a hand - which is not recoreded by
  the screenshoot application - and carries around one of the fav-links.
  Pressing ESC solves the problem. This happens every time I press
  umount.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May  6 17:52:28 2014
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'owner', 'group', 'mime_type', 
'where', 'permissions', 'date_accessed']"
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to trusty on 2014-04-22 (14 days ago)

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

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

[Desktop-packages] [Bug 1244594] [NEW] Lighting Extension Fails to Display Data

[Ben]

Public bug reported:

As the attached screenshoot shows, thunderbird and/or the lighting
extension is not able to display its calendar data. Most of the time it
even fails to display the logos of the calendar and todo list tab. As
you may guess, I need this feature to do my work. So I would be quite
thankful for advice.

Am I the only one with this problem?

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: thunderbird 1:24.0+build1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  benjamin   4983 F pulseaudio
BuildID: 20130917155107
Channel: Unavailable
Date: Fri Oct 25 11:15:07 2013
ForcedLayersAccel: False
IpRoute:
 default via 10.1.7.1 dev wlan0  proto static 
 10.1.7.0/24 dev wlan0  proto kernel  scope link  src 10.1.7.20  metric 9 
 192.168.25.0/24 dev vmnet1  proto kernel  scope link  src 192.168.25.1 
 192.168.36.0/24 dev vmnet8  proto kernel  scope link  src 192.168.36.1
MarkForUpload: True
PrefErrors: 'utf-8' codec can't decode byte 0xe4 in position 4742: invalid 
continuation byte
PrefSources: 
[Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
Profiles: Profile0 (Default) - LastVersion=24.0/20130917155107 (In use)
RelatedPackageVersions:
 icedtea-7-plugin  1.4-3ubuntu2
 gnome-shell   3.8.4-0ubuntu5
 totem-mozilla 3.8.2-0ubuntu1
 rhythmbox-mozilla 2.99.1-0ubuntu1
RunningIncompatibleAddons: False
SourcePackage: thunderbird
UpgradeStatus: Upgraded to saucy on 2013-10-17 (7 days ago)
dmi.bios.date: 06/16/2011
dmi.bios.vendor: INSYDE
dmi.bios.version: R0170H5
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnINSYDE:bvrR0170H5:bd06/16/2011:svnSonyCorporation:pnVPCZ21C5E:pvrJ004MG71:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VPCZ21C5E
dmi.product.version: J004MG71
dmi.sys.vendor: Sony Corporation

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


** Tags: amd64 apport-bug saucy

** Attachment added: "Screenshoot"
   
https://bugs.launchpad.net/bugs/1244594/+attachment/3890911/+files/screen_20131025.png

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

Title:
  Lighting Extension Fails to Display Data

Status in “thunderbird” package in Ubuntu:
  New

Bug description:
  As the attached screenshoot shows, thunderbird and/or the lighting
  extension is not able to display its calendar data. Most of the time
  it even fails to display the logos of the calendar and todo list tab.
  As you may guess, I need this feature to do my work. So I would be
  quite thankful for advice.

  Am I the only one with this problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: thunderbird 1:24.0+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  benjamin   4983 F pulseaudio
  BuildID: 20130917155107
  Channel: Unavailable
  Date: Fri Oct 25 11:15:07 2013
  ForcedLayersAccel: False
  IpRoute:
   default via 10.1.7.1 dev wlan0  proto static 
   10.1.7.0/24 dev wlan0  proto kernel  scope link  src 10.1.7.20  metric 9 
   192.168.25.0/24 dev vmnet1  proto kernel  scope link  src 192.168.25.1 
   192.168.36.0/24 dev vmnet8  proto kernel  scope link  src 192.168.36.1
  MarkForUpload: True
  PrefErrors: 'utf-8' codec can't decode byte 0xe4 in position 4742: invalid 
continuation byte
  PrefSources: 
[Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
  Profiles: Profile0 (Default) - LastVersion=24.0/20130917155107 (In use)
  RelatedPackageVersions:
   icedtea-7-plugin  1.4-3ubuntu2
   gnome-shell   3.8.4-0ubuntu5
   totem-mozilla 3.8.2-0ubuntu1
   rhythmbox-mozilla 2.99.1-0ubuntu1
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (7 days ago)
  dmi.bios.date: 06/16/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: R0170H5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDE:bvrR0170H5:bd06/16/2011:svnSonyCorporation:pnVPCZ21C5E:pvrJ004MG71:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VP

[Desktop-packages] [Bug 1026046] Re: Missing support for thumb resting on bottom of clickpad

[Ben]

I can confirm that this is an issue on the MacBook Air 4,2 Mid 2011.
Also seems to be an issue with any trackpad that supports multitouch and
has no click buttons, but a click pad. This is the reason I still don't
use ubuntu on my Mac. Please take this into consideration and add thumb
support and multitouch clickpad support. I use mtrack, but it isn't very
good, sometimes misses sensing my thumb.

Thanks

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

Title:
  Missing support for thumb resting on bottom of clickpad

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

Bug description:
  When using the trackpad on the MacBook Pro In Mac OS X it is possible to have 
the thumb resting (ready to click) on the bottom part of the touchpad while 
moving the mouse pointer around with your index or middle finger. 
  Likewise it is also possible to use two finger scrolling with the index and 
middle finger on the upper part on the track pad while resting the thumb on the 
lower part of the trackpad.

  This behaviour is not currently supported with the synaptics driver in
  12.04. It wil register a two finger scroll when the thumb is resting
  in the bottom part and index finger moves around in the upper part.

  I have tried playing aroud with the setting AreaBottomEdge that
  disables all motion on the bottom part of the touchpad. Unfortunately
  when this setting is enabled it still detects a finger in the area, so
  it wil register a two finger scroll like before.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1026046/+subscriptions

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

[Desktop-packages] [Bug 683972] Re: nautilus crashed with SIGSEGV in g_closure_invoke() ejecting drives

[Ben]

Still seeing this in 12.04.2 using Nautilus 3.4.2 with all updates
current as of 2013-07-03

Any chance of getting this fixed in the LTS release? This is serious
impediment to my workflow. Please let me know if I can be of any
assistance with troubleshooting

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

Title:
  nautilus crashed with SIGSEGV in g_closure_invoke() ejecting drives

Status in Nautilus:
  Fix Released
Status in “nautilus” package in Ubuntu:
  Fix Released
Status in “nautilus” source package in Maverick:
  Fix Released

Bug description:
  Binary package hint: nautilus

  TEST CASE:
  1. unmount a usb device, see nautilus crashes
  2. now installed nautilus from maverick-proposed
  3. see it does not crash anymore

  i was ejecting 2 drives, ejected the second before the very final
  phase of eject for the first -> crash; currently not at home, will
  verify if this is reproducible like this then

  will report on other g_closure_invoke bug i reported earlier, they
  were waiting for this crash dump

  ProblemType: Crash
  DistroRelease: Ubuntu 10.10
  Package: nautilus 1:2.32.0-0ubuntu1.1
  ProcVersionSignature: Ubuntu 2.6.37-7.18-generic 2.6.37-rc3
  Uname: Linux 2.6.37-7-generic x86_64
  Architecture: amd64
  Date: Wed Dec  1 18:42:21 2010
  ExecutablePath: /usr/bin/nautilus
  ProcCmdline: nautilus
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x44c5a6:  mov(%rax),%r14
   PC (0x0044c5a6) ok
   source "(%rax)" (0x64657469736976) not located in a known VMA region (needed 
readable region)!
   destination "%r14" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
   ?? () from /usr/lib/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in g_closure_invoke()
  UserGroups: adm admin cdrom dialout disk lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 1173966] Re: Nautilus bookmarks for smb shares disappear

[Ben]

To me it does not sound like a duplicate of #1168383, as the crash is
related to the sorting of bookmarks, rather than simply using them.

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

Title:
  Nautilus bookmarks for smb shares disappear

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  Since upgrade to 13.04 the bookmarks for smb shares disappear in the
  navigation bar at the left. Choosing files and bookmarks from the menu
  bar shows all bookmarks including the smb shares. Rearranging the smb
  shares in the bookmarks crashes nautilus. Restarting nautilus after
  the crash makes the smb shares reappear inthe navigation bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun Apr 28 16:17:23 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'927x621+991+426'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'237'
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-04-26 (2 days ago)

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

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

[Desktop-packages] [Bug 1173966] Re: Nautilus bookmarks for smb shares disappear

[Ben]

Removing all bookmarks from 12.10 and recreating them in 13.04 fixed the
issue for me.

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

Title:
  Nautilus bookmarks for smb shares disappear

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  Since upgrade to 13.04 the bookmarks for smb shares disappear in the
  navigation bar at the left. Choosing files and bookmarks from the menu
  bar shows all bookmarks including the smb shares. Rearranging the smb
  shares in the bookmarks crashes nautilus. Restarting nautilus after
  the crash makes the smb shares reappear inthe navigation bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun Apr 28 16:17:23 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'927x621+991+426'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'237'
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-04-26 (2 days ago)

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

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

[Desktop-packages] [Bug 1173966] Re: Nautilus bookmarks for smb shares disappear

[Ben]

If I mount one of your bookmarked shares, then unmount it, and then
close the nautilus window and re-open nautilus then the previously
mounted share is gone.

Regarding my previous comment #9: it is not fixed.

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

Title:
  Nautilus bookmarks for smb shares disappear

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  Since upgrade to 13.04 the bookmarks for smb shares disappear in the
  navigation bar at the left. Choosing files and bookmarks from the menu
  bar shows all bookmarks including the smb shares. Rearranging the smb
  shares in the bookmarks crashes nautilus. Restarting nautilus after
  the crash makes the smb shares reappear inthe navigation bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun Apr 28 16:17:23 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'927x621+991+426'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'237'
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-04-26 (2 days ago)

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

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

[Desktop-packages] [Bug 1354771] [NEW] package nvidia-331-updates (not installed) failed to install/upgrade: conflicting packages - not installing nvidia-331-updates

[Ben]

Public bug reported:

Trying to roll back to proprietary drivers, and I am encountering this
error.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: nvidia-331-updates (not installed)
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
Date: Sat Aug  9 20:50:14 2014
DpkgTerminalLog:
 Preparing to unpack .../libcuda1-331-updates_331.38-0ubuntu7.1_amd64.deb ...
 De-configuring libcuda1-304-updates (304.117-0ubuntu1) ...
 Unpacking libcuda1-331-updates (331.38-0ubuntu7.1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libcuda1-331-updates_331.38-0ubuntu7.1_amd64.deb 
(--unpack):
  trying to overwrite '/usr/lib/x86_64-linux-gnu/libcuda.so.1', which is also 
in package libcuda1-304-updates 304.117-0ubuntu1
DuplicateSignature: package:nvidia-331-updates:(not installed):conflicting 
packages - not installing nvidia-331-updates
ErrorMessage: conflicting packages - not installing nvidia-331-updates
InstallationDate: Installed on 2013-04-15 (481 days ago)
InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1)
SourcePackage: nvidia-graphics-drivers-331-updates
Title: package nvidia-331-updates (not installed) failed to install/upgrade: 
conflicting packages - not installing nvidia-331-updates
UpgradeStatus: Upgraded to trusty on 2014-08-04 (5 days ago)

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


** Tags: amd64 apport-package trusty

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

Title:
  package nvidia-331-updates (not installed) failed to install/upgrade:
  conflicting packages - not installing nvidia-331-updates

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

Bug description:
  Trying to roll back to proprietary drivers, and I am encountering this
  error.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Sat Aug  9 20:50:14 2014
  DpkgTerminalLog:
   Preparing to unpack .../libcuda1-331-updates_331.38-0ubuntu7.1_amd64.deb ...
   De-configuring libcuda1-304-updates (304.117-0ubuntu1) ...
   Unpacking libcuda1-331-updates (331.38-0ubuntu7.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libcuda1-331-updates_331.38-0ubuntu7.1_amd64.deb 
(--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libcuda.so.1', which is also 
in package libcuda1-304-updates 304.117-0ubuntu1
  DuplicateSignature: package:nvidia-331-updates:(not installed):conflicting 
packages - not installing nvidia-331-updates
  ErrorMessage: conflicting packages - not installing nvidia-331-updates
  InstallationDate: Installed on 2013-04-15 (481 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: package nvidia-331-updates (not installed) failed to install/upgrade: 
conflicting packages - not installing nvidia-331-updates
  UpgradeStatus: Upgraded to trusty on 2014-08-04 (5 days ago)

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

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

[Desktop-packages] [Bug 1307163] Re: not work gnome-screensaver-command -d

[Ben]

I think I've found a work-around.
Open dconf-editor.
Search (ctrl+f) for "screen-keyboard-enabled". 
Turn it on.
(I have both org.gnome.desktop.a11y.applications and 
org.cinnamon.desktop.a11y.applications. I'm not sure which you need.)

http://bazaar.launchpad.net/~unity-team/unity/trunk/view/head:/lockscreen/LockScreenController.cpp
http://bazaar.launchpad.net/~unity-team/unity/trunk/view/head:/lockscreen/LockScreenSettings.cpp
The Unity LockScreenController falls back to a org.gnome.ScreenSaver dbus proxy 
when settings->use_legacy, which is set to true when either the screen reader 
or the on-screen keyboard is enabled.

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

Title:
  not work gnome-screensaver-command -d

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

Bug description:
  After the upgrade not work gnome-screensaver-command --deactivate
  jwm + gnome-screensaver impossible to see video because not working 
gnome-screensaver-command -d

  not works:
  gnome-screensaver-command -a
  gnome-screensaver-command -d
  gnome-screensaver-command -l

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-screensaver 3.6.1-0ubuntu13
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 13 18:47:32 2014
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 0
  InstallationDate: Installed on 2014-04-11 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140410)
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1307163] Re: not work gnome-screensaver-command -d

[Ben]

On the command line:

gsettings set org.gnome.desktop.a11y.applications screen-keyboard-
enabled true

The on-screen keyboard appears when you first sign-in but you can close
it.

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

Title:
  not work gnome-screensaver-command -d

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

Bug description:
  After the upgrade not work gnome-screensaver-command --deactivate
  jwm + gnome-screensaver impossible to see video because not working 
gnome-screensaver-command -d

  not works:
  gnome-screensaver-command -a
  gnome-screensaver-command -d
  gnome-screensaver-command -l

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-screensaver 3.6.1-0ubuntu13
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 13 18:47:32 2014
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 0
  InstallationDate: Installed on 2014-04-11 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140410)
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1393648] [NEW] Simple Scan crashes after upgrade to Ubuntu 14.04. Using Brother ADS2000

[Ben]

x27; 
type=group size=4 cap=,advanced
[+3.49s] DEBUG: scanner.vala:737:   Description: 
[+3.49s] DEBUG: scanner.vala:884: sane_get_option_descriptor (8)
[+3.49s] DEBUG: scanner.vala:734: Option 8: name='tl-x' title='Top-left x' 
type=fixed size=4 unit=mm min=0.00, max=215.84, quant=6553 
cap=,soft-select,soft-detect
[+3.49s] DEBUG: scanner.vala:737:   Description: Top-left x position of scan 
area.
[+3.49s] DEBUG: scanner.vala:884: sane_get_option_descriptor (9)
[+3.49s] DEBUG: scanner.vala:734: Option 9: name='tl-y' title='Top-left y' 
type=fixed size=4 unit=mm min=0.00, max=355.51, quant=6553 
cap=,soft-select,soft-detect
[+3.49s] DEBUG: scanner.vala:737:   Description: Top-left y position of scan 
area.
[+3.49s] DEBUG: scanner.vala:884: sane_get_option_descriptor (10)
[+3.49s] DEBUG: scanner.vala:734: Option 10: name='br-x' title='Bottom-right x' 
type=fixed size=4 unit=mm min=0.00, max=215.84, quant=6553 
cap=,soft-select,soft-detect
[+3.49s] DEBUG: scanner.vala:737:   Description: Bottom-right x position of 
scan area.
[+3.49s] DEBUG: scanner.vala:884: sane_get_option_descriptor (11)
[+3.49s] DEBUG: scanner.vala:734: Option 11: name='br-y' title='Bottom-right y' 
type=fixed size=4 unit=mm min=0.00, max=355.51, quant=6553 
cap=,soft-select,soft-detect
[+3.49s] DEBUG: scanner.vala:737:   Description: Bottom-right y position of 
scan area.
[+3.49s] DEBUG: scanner.vala:884: sane_get_option_descriptor (12)
[+3.49s] WARNING: scanner.vala:946: Unable to set single page source, please 
file a bug
[+3.49s] DEBUG: scanner.vala:546: sane_control_option (2, 
SANE_ACTION_SET_VALUE, "24bit Color") -> (SANE_STATUS_GOOD, "24bit Color")
[+3.49s] DEBUG: scanner.vala:462: sane_control_option (3, 
SANE_ACTION_SET_VALUE, 300) -> (SANE_STATUS_GOOD, 300)
[+3.49s] DEBUG: scanner.vala:530: sane_control_option (10, 
SANE_ACTION_SET_VALUE, option.range.max) -> (SANE_STATUS_GOOD)
[+3.49s] DEBUG: scanner.vala:530: sane_control_option (11, 
SANE_ACTION_SET_VALUE, option.range.max) -> (SANE_STATUS_GOOD)
[+9.53s] DEBUG: scanner.vala:1209: sane_start (page=0, pass=0) -> 
SANE_STATUS_INVAL
[+9.53s] WARNING: scanner.vala:1216: Unable to start device: Invalid argument
[+9.53s] DEBUG: scanner.vala:764: sane_cancel ()
[+9.53s] DEBUG: scanner.vala:767: sane_close ()
[+9.64s] DEBUG: ui.vala:1739: Saving state to 
/home/p5yc071c/.cache/simple-scan/state
[+16.91s] DEBUG: autosave-manager.vala:194: Deleting autosave records
[+16.91s] DEBUG: scanner.vala:1583: Stopping scan thread
[+16.91s] DEBUG: scanner.vala:802: Processing request
[+16.91s] DEBUG: scanner.vala:1594: sane_exit ()

Any help would be greatly appreciated!

-Ben

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: simple-scan 3.12.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Nov 17 19:39:03 2014
DriverPackageVersions:
 libsane 1.0.23-3ubuntu3.1
 libsane-extras 1.0.22.3ubuntu1
 hplip 3.14.3-0ubuntu3.2
 hpoj N/A
InstallationDate: Installed on 2014-11-02 (15 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Apple Inc. MacBookPro11,2
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro libata.force=noncq quiet splash vt.handoff=7
SourcePackage: simple-scan
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/18/2013
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP112.88Z.0138.B02.1310181745
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-3CBD00234E554E41
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-3CBD00234E554E41
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B02.1310181745:bd10/18/2013:svnAppleInc.:pnMacBookPro11,2:pvr1.0:rvnAppleInc.:rnMac-3CBD00234E554E41:rvrMacBookPro11,2:cvnAppleInc.:ct10:cvrMac-3CBD00234E554E41:
dmi.product.name: MacBookPro11,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

** Affects: simple-scan (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: trusty

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

Title:
  Simple Scan crashes after upgrade to Ubuntu 14.04.  Using Brother
  ADS2000

Status in “simple-scan” package in Ubuntu:
  New

Bug description:
  I'm using ubuntu 14.04, recently upgraded from 12.04 where simple scan
  was working fine.  I'm using a Brother ADS-2000 (I've also been unable
  to connect to a Brother MFC-J875DW).  I've very carefully followed the
  directions on the Brother website for installing just about everyt

[Desktop-packages] [Bug 1390916] [NEW] package mythes-en-au 2.1-5.3ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/share/doc/mythes-en-au/copyright' to '/usr/share/doc/mythes-

[Ben]

Public bug reported:

its unposeble to update now so its a broblem

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: mythes-en-au 2.1-5.3ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic i686
ApportVersion: 2.14.1-0ubuntu3.5
AptOrdering:
 mythes-en-au: Install
 mythes-en-au: Configure
Architecture: i386
Date: Wed Oct 29 16:41:27 2014
DuplicateSignature: package:mythes-en-au:2.1-5.3ubuntu1:cannot copy extracted 
data for './usr/share/doc/mythes-en-au/copyright' to 
'/usr/share/doc/mythes-en-au/copyright.dpkg-new': unexpected end of file or 
stream
ErrorMessage: cannot copy extracted data for 
'./usr/share/doc/mythes-en-au/copyright' to 
'/usr/share/doc/mythes-en-au/copyright.dpkg-new': unexpected end of file or 
stream
InstallationDate: Installed on 2014-09-19 (51 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
PackageArchitecture: all
SourcePackage: openoffice.org-en-au
Title: package mythes-en-au 2.1-5.3ubuntu1 failed to install/upgrade: cannot 
copy extracted data for './usr/share/doc/mythes-en-au/copyright' to 
'/usr/share/doc/mythes-en-au/copyright.dpkg-new': unexpected end of file or 
stream
UpgradeStatus: Upgraded to trusty on 2014-10-29 (10 days ago)

** Affects: openoffice.org-en-au (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 need-duplicate-check trusty

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

Title:
  package mythes-en-au 2.1-5.3ubuntu1 failed to install/upgrade: cannot
  copy extracted data for './usr/share/doc/mythes-en-au/copyright' to
  '/usr/share/doc/mythes-en-au/copyright.dpkg-new': unexpected end of
  file or stream

Status in “openoffice.org-en-au” package in Ubuntu:
  New

Bug description:
  its unposeble to update now so its a broblem

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: mythes-en-au 2.1-5.3ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  AptOrdering:
   mythes-en-au: Install
   mythes-en-au: Configure
  Architecture: i386
  Date: Wed Oct 29 16:41:27 2014
  DuplicateSignature: package:mythes-en-au:2.1-5.3ubuntu1:cannot copy extracted 
data for './usr/share/doc/mythes-en-au/copyright' to 
'/usr/share/doc/mythes-en-au/copyright.dpkg-new': unexpected end of file or 
stream
  ErrorMessage: cannot copy extracted data for 
'./usr/share/doc/mythes-en-au/copyright' to 
'/usr/share/doc/mythes-en-au/copyright.dpkg-new': unexpected end of file or 
stream
  InstallationDate: Installed on 2014-09-19 (51 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  PackageArchitecture: all
  SourcePackage: openoffice.org-en-au
  Title: package mythes-en-au 2.1-5.3ubuntu1 failed to install/upgrade: cannot 
copy extracted data for './usr/share/doc/mythes-en-au/copyright' to 
'/usr/share/doc/mythes-en-au/copyright.dpkg-new': unexpected end of file or 
stream
  UpgradeStatus: Upgraded to trusty on 2014-10-29 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org-en-au/+bug/1390916/+subscriptions

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

[Desktop-packages] [Bug 1392083] [NEW] Black screen after boot screen - fglrx new installed and fixed

[Ben]

Public bug reported:

black screen problem. fglrx (proprietär) new installed and fixed. But
very long booting time now.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-40.68-generic 3.13.11.10
Uname: Linux 3.13.0-40-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Nov 12 23:05:46 2014
DistUpgraded: 2014-11-11 21:54:08,837 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 alsa-hda, 0.201303211238~precise1, 3.2.0-70-generic, x86_64: installed
 alsa-hda, 0.201303211238~precise1, 3.2.0-72-generic, x86_64: installed
 fglrx, 13.350.1, 3.13.0-40-generic, x86_64: installed
 vboxhost, 4.2.26, 3.13.0-40-generic, x86_64: installed
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 
250X] [1002:683d] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e214]
InstallationDate: Installed on 2012-05-28 (898 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic 
root=UUID=00b01f55-6329-416f-a706-a487895773ab ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2014-11-11 (1 days ago)
dmi.bios.date: 10/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: 990FX Extreme3
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd10/12/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn990FXExtreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs 20090808ubuntu36
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Wed Nov 12 21:26:03 2014
xserver.configfile: /etc/X11/xorg.conf
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputLogitech USB Receiver KEYBOARD, id 8
 inputLogitech USB Receiver KEYBOARD, id 9
 inputAT Translated Set 2 keyboard KEYBOARD, id 10
xserver.errors: AIGLX error: failed to open 
/usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2.2
xserver.video_driver: fglrx

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


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

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

Title:
  Black screen after boot screen - fglrx new installed and fixed

Status in “xorg” package in Ubuntu:
  New

Bug description:
  black screen problem. fglrx (proprietär) new installed and fixed. But
  very long booting time now.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-40.68-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Nov 12 23:05:46 2014
  DistUpgraded: 2014-11-11 21:54:08,837 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  Dkms

[Desktop-packages] [Bug 1405300] [NEW] Tri-Monitor Mouse Flickering in 14.10, not working at all in 14.04

[Ben]

Public bug reported:

I have a tri-monitor setup, two monitors going off of a GPU (Nvidia GTX
650 TI Boost Edition, MSI version so overclocked) and the third going
off of Integrated Graphics on my 4670k intel CPU. On the two monitors
using the GPU, the mouse has terrible flashing and flickering, and
sometimes it sometimes completely disappears. However, on the monitor
using the Intel Integrated graphics, it works fine and I have no
problems. I've done some testing, and on 14.04 the entirety of X server
works for a bit, then crashes completely after a few minutes (sometimes
gives GPU lockup errors after waiting for a while). On 14.10 it is
stable enough to use, but the mouse flickers terribly like I just talked
about. This same problem has been mentioned here
(http://askubuntu.com/questions/450655/mouse-flickering-on-one-of-my-
two-screens). The proprietary Nvidia drivers aren't exactly an option at
the moment, as they won't allow me to use the intel GPU for the third
monitor. Some research I've done seems to indicate it's a bug in X
server or the Nouveau drivers. My xrandr output is included in the
attachment.

Ubuntu version: 14.10

apt-cache policy xserver-xorg-video-nouveau
xserver-xorg-video-nouveau:
  Installed: 1:1.0.11-1ubuntu2
  Candidate: 1:1.0.11-1ubuntu2
  Version table:
 *** 1:1.0.11-1ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.7-0ubuntu8
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 Dec 23 16:48:15 2014
DistUpgraded: Fresh install
DistroCodename: utopic
DistroVariant: ubuntu
DkmsStatus: bbswitch, 0.7, 3.16.0-28-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Subsystem: ASRock Incorporation Device [1849:0412]
 NVIDIA Corporation GK106 [GeForce GTX 650 Ti Boost] [10de:11c2] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GeForce GTX 650 Ti Boost 
TwinFrozr II OC [1462:2874]
InstallationDate: Installed on 2014-12-23 (0 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed 
root=UUID=d824f919-2f35-45e5-8f2e-0a9b274fed80 ro quiet splash vt.handoff=7
SourcePackage: xserver-xorg-video-nouveau
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/26/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.30
dmi.board.name: Z87 Extreme6
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd12/26/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
xserver.bootTime: Tue Dec 23 16:29:04 2014
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.16.0-1ubuntu1.2
xserver.video_driver: nouveau

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


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

** Attachment added: "xrandr output"
   
https://bugs.launchpad.net/bugs/1405300/+attachment/4286726/+files/xrandr-output.txt

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

Title:
  Tri-Monitor Mouse Flickering in 1

[Desktop-packages] [Bug 1345753] [NEW] [Aspire V5-552G, Realtek ALC282, Mic, Internal] No sound at all

[Ben]

Public bug reported:

internal microphone will not register any sounds despite being turned
on.  the orange bars that usually record input level- this section shows
orange bars but they do not move.  I cannot use my program Rosetta Stone
because it cannot get any sound input.  This problem developed after I
had been using rosetta stone successfully with their voice recognition
feature.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  bearcube   2800 F pulseaudio
 /dev/snd/pcmC1D0c:   bearcube   2800 F...m pulseaudio
 /dev/snd/pcmC1D0p:   bearcube   2800 F...m pulseaudio
 /dev/snd/controlC0:  bearcube   2800 F pulseaudio
CurrentDesktop: Unity
Date: Sun Jul 20 16:42:41 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-06-15 (35 days ago)
InstallationMedia: It
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed
Symptom_Card: Built-in Audio - HD-Audio Generic
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  bearcube   2800 F pulseaudio
 /dev/snd/pcmC1D0c:   bearcube   2800 F...m pulseaudio
 /dev/snd/pcmC1D0p:   bearcube   2800 F...m pulseaudio
 /dev/snd/controlC0:  bearcube   2800 F pulseaudio
Symptom_Jack: Mic, Internal
Symptom_Type: No sound at all
Title: [Aspire V5-552G, Realtek ALC282, Mic, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/28/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.02
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Dazzle_RL
dmi.board.vendor: Acer
dmi.board.version: Type2 - A01 Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.02:bd05/28/2013:svnAcer:pnAspireV5-552G:pvrV2.02:rvnAcer:rnDazzle_RL:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire V5-552G
dmi.product.version: V2.02
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug trusty

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

Title:
  [Aspire V5-552G, Realtek ALC282, Mic, Internal] No sound at all

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

Bug description:
  internal microphone will not register any sounds despite being turned
  on.  the orange bars that usually record input level- this section
  shows orange bars but they do not move.  I cannot use my program
  Rosetta Stone because it cannot get any sound input.  This problem
  developed after I had been using rosetta stone successfully with their
  voice recognition feature.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bearcube   2800 F pulseaudio
   /dev/snd/pcmC1D0c:   bearcube   2800 F...m pulseaudio
   /dev/snd/pcmC1D0p:   bearcube   2800 F...m pulseaudio
   /dev/snd/controlC0:  bearcube   2800 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Jul 20 16:42:41 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-06-15 (35 days ago)
  InstallationMedia: It
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed
  Symptom_Card: Built-in Audio - HD-Audio Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bearcube   2800 F pulseaudio
   /dev/snd/pcmC1D0c:   bearcube   2800 F...m pulseaudio
   /dev/snd/pcmC1D0p:   bearcube   2800 F...m pulseaudio
   /dev/snd/controlC0:  bearcube   2800 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [Aspire V5-552G, Realtek ALC282, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.02
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Dazzle_RL
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi

[Desktop-packages] [Bug 1286863] [NEW] Network manager does not auto-connect to a configured wifi-network

[Ben]

Public bug reported:

Network manager (nm) does not auto-connect to a configured wifi-network
(e.g. "net-a") after upgrade from 13.04 to 13.10. Before the upgrade nm
auto-connected to the pre-configured wireless network (net-a). Now you
have to manually connect to the configured wifi-network (net-a). After
manual connect, the network performes normal.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: network-manager 0.9.8.0-0ubuntu22
ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
Uname: Linux 3.11.0-17-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Sun Mar  2 18:35:59 2014
EcryptfsInUse: Yes
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2011-10-26 (858 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
IpRoute:
 default via 192.168.2.1 dev wlan0  proto static 
 192.168.2.0/24 dev wlan0  proto kernel  scope link  src 192.168.2.21  metric 9
MarkForUpload: True
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to saucy on 2014-01-09 (51 days ago)
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   
 wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
 eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   WIFI  
 WWAN-HARDWARE   WWAN  
 running 0.9.8.0connected   enabled   enabled 
enabledenabled disabled

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


** Tags: amd64 apport-bug saucy

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

Title:
  Network manager does not auto-connect to a configured wifi-network

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

Bug description:
  Network manager (nm) does not auto-connect to a configured wifi-
  network (e.g. "net-a") after upgrade from 13.04 to 13.10. Before the
  upgrade nm auto-connected to the pre-configured wireless network
  (net-a). Now you have to manually connect to the configured wifi-
  network (net-a). After manual connect, the network performes normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu22
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Sun Mar  2 18:35:59 2014
  EcryptfsInUse: Yes
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2011-10-26 (858 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  IpRoute:
   default via 192.168.2.1 dev wlan0  proto static 
   192.168.2.0/24 dev wlan0  proto kernel  scope link  src 192.168.2.21  metric 
9
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to saucy on 2014-01-09 (51 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.0connected   enabled   enabled 
enabledenabled disabled

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

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

[Desktop-packages] [Bug 949637] [NEW] package gconf2 3.2.3-3ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 250

[Ben]

Public bug reported:

happened during upgrade from 11.10 to 12.04

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: gconf2 3.2.3-3ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic i686
ApportVersion: 1.94.1-0ubuntu1
Architecture: i386
Date: Wed Mar  7 19:57:08 2012
ErrorMessage: ErrorMessage: subprocess installed post-installation script 
returned error exit status 250
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
SourcePackage: gconf
Title: package gconf2 3.2.3-3ubuntu1 failed to install/upgrade: ErrorMessage: 
subprocess installed post-installation script returned error exit status 250
UpgradeStatus: Upgraded to precise on 2012-03-08 (0 days ago)

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


** Tags: apport-package i386 precise

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

Title:
  package gconf2 3.2.3-3ubuntu1 failed to install/upgrade: ErrorMessage:
  subprocess installed post-installation script returned error exit
  status 250

Status in “gconf” package in Ubuntu:
  New

Bug description:
  happened during upgrade from 11.10 to 12.04

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: gconf2 3.2.3-3ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
  Uname: Linux 3.2.0-18-generic i686
  ApportVersion: 1.94.1-0ubuntu1
  Architecture: i386
  Date: Wed Mar  7 19:57:08 2012
  ErrorMessage: ErrorMessage: subprocess installed post-installation script 
returned error exit status 250
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  SourcePackage: gconf
  Title: package gconf2 3.2.3-3ubuntu1 failed to install/upgrade: ErrorMessage: 
subprocess installed post-installation script returned error exit status 250
  UpgradeStatus: Upgraded to precise on 2012-03-08 (0 days ago)

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

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

[Desktop-packages] [Bug 949637] Re: package gconf2 3.2.3-3ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 250

[Ben]

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

Title:
  package gconf2 3.2.3-3ubuntu1 failed to install/upgrade: ErrorMessage:
  subprocess installed post-installation script returned error exit
  status 250

Status in “gconf” package in Ubuntu:
  New

Bug description:
  happened during upgrade from 11.10 to 12.04

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: gconf2 3.2.3-3ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
  Uname: Linux 3.2.0-18-generic i686
  ApportVersion: 1.94.1-0ubuntu1
  Architecture: i386
  Date: Wed Mar  7 19:57:08 2012
  ErrorMessage: ErrorMessage: subprocess installed post-installation script 
returned error exit status 250
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  SourcePackage: gconf
  Title: package gconf2 3.2.3-3ubuntu1 failed to install/upgrade: ErrorMessage: 
subprocess installed post-installation script returned error exit status 250
  UpgradeStatus: Upgraded to precise on 2012-03-08 (0 days ago)

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

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

[Desktop-packages] [Bug 649816] Re: Deleting Many Files Rapidly Crashes Nautilus

[Ben]

I have uploaded a crash report for this bug. I am able to replicate both
by holding down the DEL button, and also by pressing the DEL button in
rapid succession. When doing the latter, it often fails on the 3rd or
4th file

** Attachment added: "Crash Report"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/649816/+attachment/2635390/+files/_usr_bin_nautilus.1000.crash

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

Title:
  Deleting Many Files Rapidly Crashes Nautilus

Status in “nautilus” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: nautilus

  If you attempt to delete many files by clicking the top one in list
  view and holding down delete after about the seventh file nautilus
  will crash every time.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: nautilus 1:2.32.0-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  Architecture: amd64
  Date: Tue Sep 28 08:28:43 2010
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
  ProcEnviron:
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus

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

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

[Desktop-packages] [Bug 908347] [NEW] Unable to set emails for Follow up

[Ben]

Public bug reported:

I'm trying to flag an email for follow up at a later date.

The Mark for Follow Up option loads OK and I can choose from the various
flag options such as follow up, call etc but don't get any options for
setting the date and time for when it should remind me as there are no
options to select under "Due by"

If I continue and OK, I can see that Evolution has flagged the item
correctly as get options for flagging complete etc

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: evolution 3.2.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
Uname: Linux 3.0.0-14-generic i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Sat Dec 24 08:25:15 2011
ExecutablePath: /usr/bin/evolution
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
SourcePackage: evolution
UpgradeStatus: Upgraded to oneiric on 2011-10-29 (55 days ago)

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


** Tags: apport-bug apport-lpi i386 oneiric running-unity

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

Title:
  Unable to set emails for Follow up

Status in “evolution” package in Ubuntu:
  New

Bug description:
  I'm trying to flag an email for follow up at a later date.

  The Mark for Follow Up option loads OK and I can choose from the
  various flag options such as follow up, call etc but don't get any
  options for setting the date and time for when it should remind me as
  there are no options to select under "Due by"

  If I continue and OK, I can see that Evolution has flagged the item
  correctly as get options for flagging complete etc

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: evolution 3.2.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Uname: Linux 3.0.0-14-generic i686
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Sat Dec 24 08:25:15 2011
  ExecutablePath: /usr/bin/evolution
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
  SourcePackage: evolution
  UpgradeStatus: Upgraded to oneiric on 2011-10-29 (55 days ago)

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

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

[Desktop-packages] [Bug 908347] Re: Unable to set emails for Follow up

[Ben]

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

Title:
  Unable to set emails for Follow up

Status in “evolution” package in Ubuntu:
  New

Bug description:
  I'm trying to flag an email for follow up at a later date.

  The Mark for Follow Up option loads OK and I can choose from the
  various flag options such as follow up, call etc but don't get any
  options for setting the date and time for when it should remind me as
  there are no options to select under "Due by"

  If I continue and OK, I can see that Evolution has flagged the item
  correctly as get options for flagging complete etc

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: evolution 3.2.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Uname: Linux 3.0.0-14-generic i686
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Sat Dec 24 08:25:15 2011
  ExecutablePath: /usr/bin/evolution
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
  SourcePackage: evolution
  UpgradeStatus: Upgraded to oneiric on 2011-10-29 (55 days ago)

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

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

[Desktop-packages] [Bug 987220] Re: System does not power off reliably when "Shut Down" chosen from GUI

[Ben]

Charlotte's updated description is an exact match to what I am
experiencing on my ThinkPad T61 with the recommended Nvidia driver.

Card: Quadro NVS 140M
Driver Version: 295.40-0ubuntu1.1

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

Title:
  System does not power off reliably when "Shut Down" chosen from GUI

Status in The Session Menu:
  Incomplete
Status in “gnome-session” package in Ubuntu:
  Invalid
Status in “indicator-session” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Confirmed
Status in “upstart” package in Ubuntu:
  Invalid
Status in “gnome-session” source package in Precise:
  Invalid
Status in “indicator-session” source package in Precise:
  Invalid
Status in “linux” source package in Precise:
  Confirmed
Status in “upstart” source package in Precise:
  Invalid

Bug description:
  Shutting down the computer using the menue does not work always correct. It 
often does not complete turn off the computer. The power LED and the LED of the 
bluetooth unit remain on. Also the fan is still running and won't stop.
  Shutting down the computer with "sudo shutdown -h now" using the terminal 
works fine.

  I am using a Dell Inspiron 1720.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: indicator-session 0.3.96-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: i386
  Date: Mon Apr 23 12:26:10 2012
  ExecutablePath: /usr/lib/indicator-session/gtk-logout-helper
  InstallationMedia: Kubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 
(20100816.2)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
  SourcePackage: indicator-session
  UpgradeStatus: Upgraded to precise on 2012-04-21 (1 days ago)
  ---
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  NonfreeKernelModules: nvidia
  Package: upstart
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
  Tags:  precise
  Uname: Linux 3.2.0-24-generic-pae i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1007823] [NEW] Libreoffice Impress System Freeze

[Ben]

Public bug reported:

System frooze unexspected while writing text into libreoffice impress.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: libreoffice-impress 1:3.4.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-20.34-generic 3.0.30
Uname: Linux 3.0.0-20-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Sat Jun  2 15:29:48 2012
SourcePackage: libreoffice
UpgradeStatus: Upgraded to oneiric on 2011-11-21 (194 days ago)

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


** Tags: amd64 apport-bug oneiric running-unity

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

Title:
  Libreoffice Impress System Freeze

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  System frooze unexspected while writing text into libreoffice impress.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libreoffice-impress 1:3.4.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-20.34-generic 3.0.30
  Uname: Linux 3.0.0-20-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Sat Jun  2 15:29:48 2012
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to oneiric on 2011-11-21 (194 days ago)

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

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

[Desktop-packages] [Bug 1007823] Re: Libreoffice Impress System Freeze

[Ben]

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

Title:
  Libreoffice Impress System Freeze

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  System frooze unexspected while writing text into libreoffice impress.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libreoffice-impress 1:3.4.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-20.34-generic 3.0.30
  Uname: Linux 3.0.0-20-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Sat Jun  2 15:29:48 2012
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to oneiric on 2011-11-21 (194 days ago)

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

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

[Desktop-packages] [Bug 1010946] [NEW] totem freezes the whole system during watching a movie

[Ben]

Public bug reported:

While watching a movie (after about 15 minutes) the whole system froze,
replaying the last 5 seconds of sound in a loop.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: libgstreamer0.10-0 0.10.35-1
ProcVersionSignature: Ubuntu 3.0.0-20.34-generic 3.0.30
Uname: Linux 3.0.0-20-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Sat Jun  9 19:34:37 2012
SourcePackage: gstreamer0.10
UpgradeStatus: Upgraded to oneiric on 2011-11-21 (201 days ago)

** Affects: gstreamer0.10 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug oneiric running-unity

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

Title:
  totem freezes the whole system during watching a movie

Status in “gstreamer0.10” package in Ubuntu:
  New

Bug description:
  While watching a movie (after about 15 minutes) the whole system
  froze, replaying the last 5 seconds of sound in a loop.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libgstreamer0.10-0 0.10.35-1
  ProcVersionSignature: Ubuntu 3.0.0-20.34-generic 3.0.30
  Uname: Linux 3.0.0-20-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Sat Jun  9 19:34:37 2012
  SourcePackage: gstreamer0.10
  UpgradeStatus: Upgraded to oneiric on 2011-11-21 (201 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1010946/+subscriptions

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

[Desktop-packages] [Bug 1010946] Re: totem freezes the whole system during watching a movie

[Ben]

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

Title:
  totem freezes the whole system during watching a movie

Status in “gstreamer0.10” package in Ubuntu:
  New

Bug description:
  While watching a movie (after about 15 minutes) the whole system
  froze, replaying the last 5 seconds of sound in a loop.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libgstreamer0.10-0 0.10.35-1
  ProcVersionSignature: Ubuntu 3.0.0-20.34-generic 3.0.30
  Uname: Linux 3.0.0-20-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Sat Jun  9 19:34:37 2012
  SourcePackage: gstreamer0.10
  UpgradeStatus: Upgraded to oneiric on 2011-11-21 (201 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1010946/+subscriptions

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

[Desktop-packages] [Bug 424499] Re: rhythmbox does not set IM status in empathy

[ben]

i have the same bug in precise pangolin (beta)

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

Title:
  rhythmbox does not set IM status in empathy

Status in The Rhythmbox Music Management Application:
  Fix Released
Status in “rhythmbox” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: rhythmbox

  Enabling the IM status plugin does not do anything.

  ProblemType: Bug
  Architecture: i386
  CheckboxSubmission: 1ae7a1f14f02ba41dc1cc8734f40a3bc
  CheckboxSystem: faa41606b77ca9613dad823b5abbd8a8
  Date: Fri Sep  4 20:10:19 2009
  DistroRelease: Ubuntu 9.10
  Package: rhythmbox 0.12.4-1ubuntu1
  ProcEnviron:
   LANGUAGE=en_DK.UTF-8
   LANG=en_DK.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-9.29-generic
  SourcePackage: rhythmbox
  Uname: Linux 2.6.31-9-generic i686

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

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

[Desktop-packages] [Bug 1868519] Re: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from xf86MoveCursor() from miPointerMoveNoEvent() from miPointerSetPosition() from positionSprite()

[Ben]

Can confirm, using nvidia-driver-450 seems to resolve the issue. I
installed from here: https://launchpad.net/~graphics-
drivers/+archive/ubuntu/ppa

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

Title:
  [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from
  xf86MoveCursor() from miPointerMoveNoEvent() from
  miPointerSetPosition() from positionSprite()

Status in nvidia-graphics-drivers package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
nvidia-graphics-drivers.  This problem was most recently seen with package 
version 2:1.20.7-2ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/5a9ed7ea32a1d20e4222dbe8712aa9640b42a73c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1838577] Re: Default audio device changes on reboot; audio still outputs using my previously-selected device

[Ben]

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

After looking through the posted bug and comments I'm not sure that the
issues are related. It seems more like, in this case, GNOME is just out
of sync with pulse about what the default device is thanks to pulse
changing it out during login. Changing the selected device fixes the
issue (until the next login).

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

Title:
  Default audio device changes on reboot; audio still outputs using my
  previously-selected device

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This is present in Ubuntu 18.04, 18.10, 19.04, and 19.10 daily build.
  It was not present in Ubuntu 16.04.

  I have a USB microphone which also appears to pulse as a speaker.
  Pulse keeps picking it as the default audio device. I can switch audio
  devices to my analog line out, which works as expected until I reboot.

  After reboot, my audio device switches back to the USB "speaker", and
  Gnome shell / Gnome settings volume control adjusts the USB speaker
  volume. Despite  seeing the USB device as the current output device, I
  still hear sound from my line-out.

  In the interest of narrowing down this bug, I have found that
  disabling "module-switch-on-connect" fixes the problem (my line-out
  stays as the default audio device and I hear sound).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 31 17:39:38 2019
  InstallationDate: Installed on 2019-07-31 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4207
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B350M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4207:bd12/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1838577] Re: Default audio device changes on reboot; audio still outputs using my previously-selected device

[Ben]

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

Is it supposed to switch back on reboot though? If I select a certain
device I expect it to stay that way. It's not like I'm unplugging and
replugging my USB device. From a user's perspective this certainly
doesn't feel like the desired behavior.

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

Title:
  Default audio device changes on reboot; audio still outputs using my
  previously-selected device

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This is present in Ubuntu 18.04, 18.10, 19.04, and 19.10 daily build.
  It was not present in Ubuntu 16.04.

  I have a USB microphone which also appears to pulse as a speaker.
  Pulse keeps picking it as the default audio device. I can switch audio
  devices to my analog line out, which works as expected until I reboot.

  After reboot, my audio device switches back to the USB "speaker", and
  Gnome shell / Gnome settings volume control adjusts the USB speaker
  volume. Despite  seeing the USB device as the current output device, I
  still hear sound from my line-out.

  In the interest of narrowing down this bug, I have found that
  disabling "module-switch-on-connect" fixes the problem (my line-out
  stays as the default audio device and I hear sound).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 31 17:39:38 2019
  InstallationDate: Installed on 2019-07-31 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4207
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B350M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4207:bd12/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1875729] [NEW] Fractional Scaling crashes gnome-control-center

[Ben]

Public bug reported:

Overview:

When applying "Fractional Scaling" of 150% or 175%, the screen goes
black for a while, then after a little while it comes back unscaled and
gnome-control-center has crashed.


Found in:

Description:Ubuntu 20.04 LTS
Release:20.04

gnome-control-center:
  Installed: 1:3.36.1-1ubuntu5
  Candidate: 1:3.36.1-1ubuntu5
  Version table:
 *** 1:3.36.1-1ubuntu5 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status


Steps to reproduce:

1. Go into "Screen Display" in Settings.
2. Enable "Fractional Scaling".
3. Select "150%" or "175%".
4. Observe that the screen goes blank for about 5 seconds.
5. Observe that upon the screen coming back, the Settings application has 
crashed.


Additional details:

If instead of selecting "150%" or "175%" I select "125%", then the
screen will scale to 200% instead, but if I select and apply "125%"
again, then suddenly only just over of a quarter of the screen is
recognised as display and the rest just displays my background and top
bar extended.

I am using a 4k display over a display port cable.
I am using a GTX 1070 TI with the Nvidia 440.64 driver.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.1-1ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 28 19:37:27 2020
InstallationDate: Installed on 2020-04-25 (2 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Fractional Scaling crashes gnome-control-center

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

Bug description:
  Overview:

  When applying "Fractional Scaling" of 150% or 175%, the screen goes
  black for a while, then after a little while it comes back unscaled
  and gnome-control-center has crashed.

  
  Found in:

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  gnome-control-center:
Installed: 1:3.36.1-1ubuntu5
Candidate: 1:3.36.1-1ubuntu5
Version table:
   *** 1:3.36.1-1ubuntu5 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Steps to reproduce:

  1. Go into "Screen Display" in Settings.
  2. Enable "Fractional Scaling".
  3. Select "150%" or "175%".
  4. Observe that the screen goes blank for about 5 seconds.
  5. Observe that upon the screen coming back, the Settings application has 
crashed.

  
  Additional details:

  If instead of selecting "150%" or "175%" I select "125%", then the
  screen will scale to 200% instead, but if I select and apply "125%"
  again, then suddenly only just over of a quarter of the screen is
  recognised as display and the rest just displays my background and top
  bar extended.

  I am using a 4k display over a display port cable.
  I am using a GTX 1070 TI with the Nvidia 440.64 driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 19:37:27 2020
  InstallationDate: Installed on 2020-04-25 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1875729] Re: Fractional Scaling crashes gnome-control-center

[Ben]

Hi Sebastian and Daniel, thanks for getting back to me. Daniel, I think
you are likely correct with the 2 bugs you suggested, they seem to be
similar.

The links are:
https://errors.ubuntu.com/oops/13fe9496-8745-11ea-ac2d-fa163e983629
https://errors.ubuntu.com/oops/390d34ea-874a-11ea-a30e-fa163e6cac46
https://errors.ubuntu.com/oops/3547348e-897f-11ea-a33f-fa163e6cac46

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

Title:
  Fractional Scaling crashes gnome-control-center

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

Bug description:
  Overview:

  When applying "Fractional Scaling" of 150% or 175%, the screen goes
  black for a while, then after a little while it comes back unscaled
  and gnome-control-center has crashed.

  
  Found in:

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  gnome-control-center:
Installed: 1:3.36.1-1ubuntu5
Candidate: 1:3.36.1-1ubuntu5
Version table:
   *** 1:3.36.1-1ubuntu5 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Steps to reproduce:

  1. Go into "Screen Display" in Settings.
  2. Enable "Fractional Scaling".
  3. Select "150%" or "175%".
  4. Observe that the screen goes blank for about 5 seconds.
  5. Observe that upon the screen coming back, the Settings application has 
crashed.

  
  Additional details:

  If instead of selecting "150%" or "175%" I select "125%", then the
  screen will scale to 200% instead, but if I select and apply "125%"
  again, then suddenly only just over of a quarter of the screen is
  recognised as display and the rest just displays my background and top
  bar extended.

  I am using a 4k display over a display port cable.
  I am using a GTX 1070 TI with the Nvidia 440.64 driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 19:37:27 2020
  InstallationDate: Installed on 2020-04-25 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1830472] [NEW] 'mv' command without target address

[Ben]

Public bug reported:

When I was using the mv command, I forgot to enter the target folder,
but the terminal did not report an error and the source file was gone.
But when I tried it again， it report the error "mv: missing destination
file operand after 'filename'". Though the file is not important, I hope
you can figure it out. Thank you!

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-18-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat May 25 18:12:56 2019
ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
InstallationDate: Installed on 2019-03-07 (78 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "the wrong command screenshot"
   
https://bugs.launchpad.net/bugs/1830472/+attachment/5266487/+files/2019-05-25%2017-45-32%20%E7%9A%84%E5%B1%8F%E5%B9%95%E6%88%AA%E5%9B%BE.png

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

Title:
  'mv' command without target address

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  When I was using the mv command, I forgot to enter the target folder,
  but the terminal did not report an error and the source file was gone.
  But when I tried it again， it report the error "mv: missing
  destination file operand after 'filename'". Though the file is not
  important, I hope you can figure it out. Thank you!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 25 18:12:56 2019
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2019-03-07 (78 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1801540]

[ben]

(In reply to Marco from comment #100)

> Yea, I'm still trying to find the energy to begin to write a parser for the
> codec commands, but this will surely take quite a lot of time.

This actually sounds like something I would be interested in working on.
However I don't really have any experience working with low level audio
like this.

Are the dumps you gave for the ALC892?

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

Title:
  Microphone distorted sound on ALC892/1220 on AMD chipsets

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

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

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

[Desktop-packages] [Bug 1835625] Re: Shows old snap edge version of thunderbird

[Ben]

As I wrote on the snapcraft forums, that's a problem then as long as the
snap continues to be out of date/unstable, as the snap replaces the deb
version for users that don't have Thunderbird installed.

I don't mind if non-stable snaps appear in the store, but they should
not be default if a deb version is also available.

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

Title:
  Shows old snap edge version of thunderbird

Status in gnome-software package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Fix Released

Bug description:
  Test case:
  Open ubuntu-software, search thunderbird
  Version returned is an old edge version of thunderbird not meant to be used.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-software 3.30.6-2ubuntu8
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul  6 14:57:47 2019
  InstallationDate: Installed on 2019-07-03 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190703)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.30.6-2ubuntu8
  PackageArchitecture: all
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1838577] [NEW] Default audio device changes on reboot; audio still outputs using my previously-selected device

[Ben]

Public bug reported:

This is present in Ubuntu 18.04, 18.10, 19.04, and 19.10 daily build. It
was not present in Ubuntu 16.04.

I have a USB microphone which also appears to pulse as a speaker. Pulse
keeps picking it as the default audio device. I can switch audio devices
to my analog line out, which works as expected until I reboot.

After reboot, my audio device switches back to the USB "speaker", and
Gnome shell / Gnome settings volume control adjusts the USB speaker
volume. Despite  seeing the USB device as the current output device, I
still hear sound from my line-out.

In the interest of narrowing down this bug, I have found that disabling
"module-switch-on-connect" fixes the problem (my line-out stays as the
default audio device and I hear sound).

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: pulseaudio 1:12.2-2ubuntu3
ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
Uname: Linux 5.0.0-21-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul 31 17:39:38 2019
InstallationDate: Installed on 2019-07-31 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/07/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4207
dmi.board.asset.tag: Default string
dmi.board.name: PRIME B350M-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4207:bd12/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug bionic cosmic disco eoan

** Description changed:

  This is present in Ubuntu 18.04, 18.10, 19.04, and 19.10 daily build. It
  was not present in Ubuntu 16.04.
  
  I have a USB microphone which also appears to pulse as a speaker. Pulse
  keeps picking it as the default audio device. I can switch audio devices
  to my analog line out, which works as expected until I reboot.
  
  After reboot, my audio device switches back to the USB "speaker", and
- volume control adjusts the USB speaker volume. Despite pulse seeing the
- USB device as the current output device, I still hear sound from my
- line-out.
+ Gnome shell / Gnome settings volume control adjusts the USB speaker
+ volume. Despite  seeing the USB device as the current output device, I
+ still hear sound from my line-out.
  
  In the interest of narrowing down this bug, I have found that disabling
  "module-switch-on-connect" fixes the problem (my line-out stays as the
  default audio device and I hear sound).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 31 17:39:38 2019
  InstallationDate: Installed on 2019-07-31 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4207
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B350M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4207:bd12/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

Title:
  Default audio device changes on reboot; audio still outputs us

[Desktop-packages] [Bug 1801540]

[ben]

(In reply to Takashi Iwai from comment #127)
> Hm, interesting, AZX_DCAPS_POSFIX_LPIB basically sets the position reporting
> based on LPIB instead of the position buffer.  I thought the position buffer
> isn't available or unreliable on non-Intel chips, but it might be different
> on the recent AMD one.

Contrary to what Ernst experienced, removing AZX_DCAPS_POSFIX_LPIB
completely broke audio on my system (ASUS PRIME X470, also 1022:1457),
so I guess it's still unreliable as you mentioned.

Was looking through the pci_ids array in sound/pci/hda/hda_intel.c and
noticed that my audio controller (1022:1457) isn't listed.

The only thing I can see that would match is the following, which seems
to be intended for AMD GPUs.


{ PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_ANY_ID),
  .class = PCI_CLASS_MULTIMEDIA_HD_AUDIO << 8,
  .class_mask = 0xff,
  .driver_data = AZX_DRIVER_GENERIC | AZX_DCAPS_PRESET_ATI_HDMI },

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

Title:
  Microphone distorted sound on ALC892/1220 on AMD chipsets

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

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

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

[Desktop-packages] [Bug 550856] Re: page size setting is broken, use it as default crop or fix it by other means

[Ben]

Update: When I startup my PC the setting in the file ~/.cache/simple-
scan/state is

[window]
width=600
height=400
is-maximized=true
is-fullscreen=false

[last-page]
width=1240
height=1750
dpi=300
scan-direction=top-to-bottom

The displayed, empty page in simple scan is A4. Now I put in one A4 page
and start the scan via "CTL-F". During the scanning the page size
shrinks and after finishing the scan the file content changed to

heigh=1650.

This happens every time after an upstart of the PC. I can then set from
"A4" to "automatic", scan once and the right size comes up.

However, when shutting down the PC, this setting ("automatic") is going
to be loaded upon a fresh start. Then, the same thing happens (size is
correct, during scan it gets cropped). But now I have to change to
another size ("A4" for example) and then scan and then change to
"automatic" and scan to get the right size.

This is awkward and unnerving.

Please can someone help to fix this? I absolutely love simple scan and
use it every day!

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

Title:
  page size setting is broken, use it as default crop or fix it by other
  means

Status in Simple Scan:
  Fix Released
Status in Simple Scan 3.10 series:
  Fix Released
Status in Simple Scan 3.11 series:
  Fix Released
Status in simple-scan package in Ubuntu:
  Fix Released
Status in simple-scan source package in Saucy:
  Fix Released
Status in simple-scan source package in Trusty:
  Fix Released

Bug description:
  For some SANE drivers simple scan always scans the largest scan area
  ignoring the "Page Size" setting in the preferences.

  To reproduce:
  1. Open Simple Scan
  2. Set page size in Document > Prefrences > Page Size, e.g. to "4x6"
  3. Scan a document
  Expected result:
  The document is scanned at the requested size
  Observed result:
  The document is scanned at the maximum size

  Regression potential:
  Low. The fix was to set the page size using an alternative method for drivers 
that do not support the page-width, page-height options. There is a small 
chance that these settings might change behaviour / expose bugs on drivers that 
were previously working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/simple-scan/+bug/550856/+subscriptions

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

[Desktop-packages] [Bug 1708874] [NEW] Touchpad stops working after a few seconds

[Ben]

Public bug reported:

Hardware: Lenovo ideapad 320, AMD A12 processor
AMD A12-9720P RADEON R7, 12 COMPUTE CORES 4C+8G × 4 

Software: Ubuntu Mate 17.10
Description:Ubuntu Artful Aardvark (development branch)
Release:17.10

Expected Behavior: Touchpad working.

Actual Behavior: Touchpad works for about 30 or fewer seconds on boot,
then doesn't work again until reboot. Dmesg shows nothing happening when
it stops working.

Let me know if I need to do anything.

Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xserver-xorg-input-synaptics 1.9.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
CurrentDesktop: MATE
Date: Sat Aug  5 14:52:39 2017
InstallationDate: Installed on 2017-08-05 (0 days ago)
InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 
(20170725.1)
SourcePackage: xserver-xorg-input-synaptics
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
  Touchpad stops working after a few seconds

Status in xserver-xorg-input-synaptics package in Ubuntu:
  New

Bug description:
  Hardware: Lenovo ideapad 320, AMD A12 processor
  AMD A12-9720P RADEON R7, 12 COMPUTE CORES 4C+8G × 4 

  Software: Ubuntu Mate 17.10
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  Expected Behavior: Touchpad working.

  Actual Behavior: Touchpad works for about 30 or fewer seconds on boot,
  then doesn't work again until reboot. Dmesg shows nothing happening
  when it stops working.

  Let me know if I need to do anything.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xserver-xorg-input-synaptics 1.9.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sat Aug  5 14:52:39 2017
  InstallationDate: Installed on 2017-08-05 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 
(20170725.1)
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1708874/+subscriptions

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

[Desktop-packages] [Bug 1708874] Re: Touchpad stops working after a few seconds

[Ben]

I uploaded a video to YouTube showing what happens:

https://youtu.be/mRl0bVW1nxM

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

Title:
  Touchpad stops working after a few seconds

Status in xserver-xorg-input-synaptics package in Ubuntu:
  New

Bug description:
  Hardware: Lenovo ideapad 320, AMD A12 processor
  AMD A12-9720P RADEON R7, 12 COMPUTE CORES 4C+8G × 4 

  Software: Ubuntu Mate 17.10
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  Expected Behavior: Touchpad working.

  Actual Behavior: Touchpad works for about 30 or fewer seconds on boot,
  then doesn't work again until reboot. Dmesg shows nothing happening
  when it stops working.

  Let me know if I need to do anything.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xserver-xorg-input-synaptics 1.9.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sat Aug  5 14:52:39 2017
  InstallationDate: Installed on 2017-08-05 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 
(20170725.1)
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1708874/+subscriptions

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

[Desktop-packages] [Bug 1684213] [NEW] Intel Wireless 7260 often crashes

[Ben]

Public bug reported:

Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS 
enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses 
Intel 7260 wifi, rev. bb:
01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently, everything
(kernel, firmware, etc.) is stock. Issue has persisted across multiple
installations.

Bug: Wifi/Bluetooth crashes and refuses to come back up, even after
multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.)

When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, 
upon boot, it is not uncommon for the wireless to stop working within two 
minutes of login time. Curiously, the GUI usually still shows being 
"connected", though trying to change anything with the wifi shows otherwise. 
Other times, upon system resume when wireless was previously working, the GUI 
will show "device not ready" and refuse to continue. Dmesg shows the following:
[  423.814823] Bluetooth: hci0 command 0x1403 tx timeout
[  424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd
[  424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
[  424.173067] iwlwifi :01:00.0: Scan failed! ret -5
[  425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd
[  425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
[  425.194593] iwlwifi :01:00.0: Scan failed! ret -5

Solution: Rebooting doesn't fix the problem. Perhaps a different
firmware version will work better? Configuration settings? etc.?
Unknown.

Thanks ahead of time for the help. Let me know if there's anything you
need/commands I should run/solutions I can attempt.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-19-generic 4.10.0-19.21
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bmueller   1669 F pulseaudio
CurrentDesktop: MATE
Date: Wed Apr 19 10:34:11 2017
InstallationDate: Installed on 2017-04-13 (6 days ago)
InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:07dc Intel Corp.
 Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: GOOGLE Gnawty
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=45b1dd3f-10df-4a28-904c-74c694ef75a5 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-19-generic N/A
 linux-backports-modules-4.10.0-19-generic  N/A
 linux-firmware 1.164
SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-04-16 (2 days ago)
dmi.bios.date: 08/16/2015
dmi.bios.vendor: coreboot
dmi.chassis.type: 3
dmi.chassis.vendor: GOOGLE
dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
dmi.product.name: Gnawty
dmi.product.version: 1.0
dmi.sys.vendor: GOOGLE

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed

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

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


** Tags: amd64 apport-bug zesty

** Attachment added: "Dmesg output when issue is occuring."
   
https://bugs.launchpad.net/bugs/1684213/+attachment/4864922/+files/dmesg-errors.txt

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

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

** Description changed:

  Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS 
enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses 
Intel 7260 wifi, rev. bb:
  01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)
  
  Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently, everything
  (kernel, firmware, etc.) is stock. Issue has persisted across multiple
  installations.
  
- Bug: Wifi/Bluetooth crashes crashes and refuses to come back up, even
- after multiple reboots. Issue persists across distros (Arch, Ubuntu,
- etc.)
+ Bug: Wifi/Bluetooth crashes and refuses to come back up, even after
+ multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.)
  
  When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, 
upon boot, it is not uncommon for the wireless to stop working within two 
minutes of login time. Curiously, the GUI usually still shows being 
"connected", though trying to change anything with the wifi shows otherwise. 
Other times, upon system resume when wireless was previo

[Desktop-packages] [Bug 1684213] Re: Intel Wireless 7260 often crashes

[Ben]

Some additional notes after testing for a while...

The crashing behavior doesn't occur consistently in the same way.
Sometimes the Bluetooth crashes with the Wifi, while sometimes it
recovers fine and continues to work while the Wifi doesn't. In addition,
it seems that the Wifi crash breaks NetworkManager as well- when I try
to plug in a USB WiFi card, the networks show up but give me the
following error in dmesg whenever the usb adapter tries to connect:

[21857.875157] wlx002129e30688: authenticate with 8e:15:44:a9:86:22
[21857.924545] wlx002129e30688: send auth to 8e:15:44:a9:86:22 (try 1/3)
[21857.926882] wlx002129e30688: authenticated
[21863.316129] wlx002129e30688: authenticate with 8e:15:44:a9:85:f8
[21863.371861] wlx002129e30688: send auth to 8e:15:44:a9:85:f8 (try 1/3)
[21863.374438] wlx002129e30688: authenticated
[21868.376165] wlx002129e30688: aborting authentication with 8e:15:44:a9:85:f8 
by local choice (Reason: 3=DEAUTH_LEAVING)
[21868.740813] wlx002129e30688: authenticate with 8e:15:44:a9:82:fa
[21868.788615] wlx002129e30688: send auth to 8e:15:44:a9:82:fa (try 1/3)
[21868.790444] wlx002129e30688: authenticated
[21873.795552] wlx002129e30688: aborting authentication with 8e:15:44:a9:82:fa 
by local choice (Reason: 3=DEAUTH_LEAVING)

This repeats until it gives up trying to connect. Yet, tethering to my
Android phone over USB DOES usually work. Restarting the NetworkManager
service has no effect on the wifi issue.

@jsalisbury: This issue has persisted across kernel versions and Ubuntu
versions. I had the same issue on 16.10, as well as Arch when I used it,
upgrade or not. I'm not ruling out a regression however, but frankly I
have no qualifications to say what the issue is caused by. If I have
time (and I get desperate enough) I'll try 16.04 and 14.04 and let you
know if it's still present there.

I'll test the 4.11 kernel this weekend, in the meantime, I'll upload
some more dmesg outputs.

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

Title:
  Intel Wireless 7260 often crashes

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS 
enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses 
Intel 7260 wifi, rev. bb:
  01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently,
  everything (kernel, firmware, etc.) is stock. Issue has persisted
  across multiple installations.

  Bug: Wifi/Bluetooth crashes and refuses to come back up, even after
  multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.)

  When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, 
upon boot, it is not uncommon for the wireless to stop working within two 
minutes of login time. Curiously, the GUI usually still shows being 
"connected", though trying to change anything with the wifi shows otherwise. 
Other times, upon system resume when wireless was previously working, the GUI 
will show "device not ready" and refuse to continue. Dmesg shows the following:
  [  423.814823] Bluetooth: hci0 command 0x1403 tx timeout
  [  424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  424.173067] iwlwifi :01:00.0: Scan failed! ret -5
  [  425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  425.194593] iwlwifi :01:00.0: Scan failed! ret -5

  Solution: Rebooting doesn't fix the problem. Perhaps a different
  firmware version will work better? Configuration settings? etc.?
  Unknown.

  Thanks ahead of time for the help. Let me know if there's anything you
  need/commands I should run/solutions I can attempt.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bmueller   1669 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Apr 19 10:34:11 2017
  InstallationDate: Installed on 2017-04-13 (6 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp.
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Gnawty
  Pr

[Desktop-packages] [Bug 1684213] Re: Intel Wireless 7260 often crashes

[Ben]

** Attachment added: "Output dmesg crash on resume"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1684213/+attachment/4866130/+files/ucode-error-crash.txt

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

Title:
  Intel Wireless 7260 often crashes

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS 
enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses 
Intel 7260 wifi, rev. bb:
  01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently,
  everything (kernel, firmware, etc.) is stock. Issue has persisted
  across multiple installations.

  Bug: Wifi/Bluetooth crashes and refuses to come back up, even after
  multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.)

  When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, 
upon boot, it is not uncommon for the wireless to stop working within two 
minutes of login time. Curiously, the GUI usually still shows being 
"connected", though trying to change anything with the wifi shows otherwise. 
Other times, upon system resume when wireless was previously working, the GUI 
will show "device not ready" and refuse to continue. Dmesg shows the following:
  [  423.814823] Bluetooth: hci0 command 0x1403 tx timeout
  [  424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  424.173067] iwlwifi :01:00.0: Scan failed! ret -5
  [  425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  425.194593] iwlwifi :01:00.0: Scan failed! ret -5

  Solution: Rebooting doesn't fix the problem. Perhaps a different
  firmware version will work better? Configuration settings? etc.?
  Unknown.

  Thanks ahead of time for the help. Let me know if there's anything you
  need/commands I should run/solutions I can attempt.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bmueller   1669 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Apr 19 10:34:11 2017
  InstallationDate: Installed on 2017-04-13 (6 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp.
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Gnawty
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=45b1dd3f-10df-4a28-904c-74c694ef75a5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (2 days ago)
  dmi.bios.date: 08/16/2015
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Gnawty
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

[Desktop-packages] [Bug 1684213] Re: Intel Wireless 7260 often crashes

[Ben]

** Attachment added: "Output of modinfo iwlwifi"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1684213/+attachment/4866129/+files/modinfo-iwlwifi.txt

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

Title:
  Intel Wireless 7260 often crashes

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS 
enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses 
Intel 7260 wifi, rev. bb:
  01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently,
  everything (kernel, firmware, etc.) is stock. Issue has persisted
  across multiple installations.

  Bug: Wifi/Bluetooth crashes and refuses to come back up, even after
  multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.)

  When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, 
upon boot, it is not uncommon for the wireless to stop working within two 
minutes of login time. Curiously, the GUI usually still shows being 
"connected", though trying to change anything with the wifi shows otherwise. 
Other times, upon system resume when wireless was previously working, the GUI 
will show "device not ready" and refuse to continue. Dmesg shows the following:
  [  423.814823] Bluetooth: hci0 command 0x1403 tx timeout
  [  424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  424.173067] iwlwifi :01:00.0: Scan failed! ret -5
  [  425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  425.194593] iwlwifi :01:00.0: Scan failed! ret -5

  Solution: Rebooting doesn't fix the problem. Perhaps a different
  firmware version will work better? Configuration settings? etc.?
  Unknown.

  Thanks ahead of time for the help. Let me know if there's anything you
  need/commands I should run/solutions I can attempt.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bmueller   1669 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Apr 19 10:34:11 2017
  InstallationDate: Installed on 2017-04-13 (6 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp.
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Gnawty
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=45b1dd3f-10df-4a28-904c-74c694ef75a5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (2 days ago)
  dmi.bios.date: 08/16/2015
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Gnawty
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

[Desktop-packages] [Bug 1684213] Re: Intel Wireless 7260 often crashes

[Ben]

It took less than 10 minutes of testing for the issue to come back up
again under 4.11-rc7. Definitely NOT fixed upstream. I'll keep testing
and see if I find any other unique behaviours/error messages. Thanks
again, let me know if there's anything I can do!

** Tags added: kernel-bug-exists-upstream

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

Title:
  Intel Wireless 7260 often crashes

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS 
enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses 
Intel 7260 wifi, rev. bb:
  01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently,
  everything (kernel, firmware, etc.) is stock. Issue has persisted
  across multiple installations.

  Bug: Wifi/Bluetooth crashes and refuses to come back up, even after
  multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.)

  When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, 
upon boot, it is not uncommon for the wireless to stop working within two 
minutes of login time. Curiously, the GUI usually still shows being 
"connected", though trying to change anything with the wifi shows otherwise. 
Other times, upon system resume when wireless was previously working, the GUI 
will show "device not ready" and refuse to continue. Dmesg shows the following:
  [  423.814823] Bluetooth: hci0 command 0x1403 tx timeout
  [  424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  424.173067] iwlwifi :01:00.0: Scan failed! ret -5
  [  425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  425.194593] iwlwifi :01:00.0: Scan failed! ret -5

  Solution: Rebooting doesn't fix the problem. Perhaps a different
  firmware version will work better? Configuration settings? etc.?
  Unknown.

  Thanks ahead of time for the help. Let me know if there's anything you
  need/commands I should run/solutions I can attempt.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bmueller   1669 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Apr 19 10:34:11 2017
  InstallationDate: Installed on 2017-04-13 (6 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp.
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Gnawty
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=45b1dd3f-10df-4a28-904c-74c694ef75a5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (2 days ago)
  dmi.bios.date: 08/16/2015
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Gnawty
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

[Desktop-packages] [Bug 1684213] Re: Intel Wireless 7260 often crashes

[Ben]

Issue definitely persists on 4.11/upstream. I came across an interesting
output in dmesg which may explain why bluetooth works while the WiFi
doesn't:

[17326.525545] iwlwifi :01:00.0: Could not load the [0] uCode section
[17326.525697] iwlwifi :01:00.0: Failed to start INIT ucode: -5
[17326.525702] iwlwifi :01:00.0: Failed to run INIT ucode: -5
[17326.525705] iwlwifi :01:00.0: Failed to start RT ucode: -5
[17391.638774] usb 1-4: USB disconnect, device number 64
[17392.015275] usb 1-4: new full-speed USB device number 65 using xhci_hcd
[17392.156505] usb 1-4: New USB device found, idVendor=8087, idProduct=07dc
[17392.156520] usb 1-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[17392.179288] Bluetooth: hci0: read Intel version: 3707100180012d0d00
[17392.179426] Bluetooth: hci0: Intel Bluetooth firmware file: 
intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq
[17392.367199] Bluetooth: hci0: Intel Bluetooth firmware patch completed and 
activated


What's interesting is that iwlwifi "can't load" the uCode/firmware, causing the 
internet/wifi portion to fail, but Bluetooth uses a separate firmware file on 
the same card, which itself works fine. So this probably explains why the 
bluetooth still works.

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

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

Title:
  Intel Wireless 7260 often crashes

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS 
enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses 
Intel 7260 wifi, rev. bb:
  01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently,
  everything (kernel, firmware, etc.) is stock. Issue has persisted
  across multiple installations.

  Bug: Wifi/Bluetooth crashes and refuses to come back up, even after
  multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.)

  When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, 
upon boot, it is not uncommon for the wireless to stop working within two 
minutes of login time. Curiously, the GUI usually still shows being 
"connected", though trying to change anything with the wifi shows otherwise. 
Other times, upon system resume when wireless was previously working, the GUI 
will show "device not ready" and refuse to continue. Dmesg shows the following:
  [  423.814823] Bluetooth: hci0 command 0x1403 tx timeout
  [  424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  424.173067] iwlwifi :01:00.0: Scan failed! ret -5
  [  425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  425.194593] iwlwifi :01:00.0: Scan failed! ret -5

  Solution: Rebooting doesn't fix the problem. Perhaps a different
  firmware version will work better? Configuration settings? etc.?
  Unknown.

  Thanks ahead of time for the help. Let me know if there's anything you
  need/commands I should run/solutions I can attempt.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bmueller   1669 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Apr 19 10:34:11 2017
  InstallationDate: Installed on 2017-04-13 (6 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp.
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Gnawty
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=45b1dd3f-10df-4a28-904c-74c694ef75a5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (2 days ago)
  dmi.bios.date: 08/16/2015
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.p

Re: [Desktop-packages] [Bug 1316673] Re: Pressing umount button leads to sticky icon as mouse pointer

[Ben]

> Do you still see that issue in more recent Ubuntu versions?
> 
> ** Changed in: nautilus (Ubuntu)
>Status: New => Incomplete

No. Should be closed.

Cheers

Benjamin

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

Title:
  Pressing umount button leads to sticky icon as mouse pointer

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  When pressing the umount button in nautilus (see screenshoot_1.png,
  #1), the mouse pointer changes to a hand - which is not recoreded by
  the screenshoot application - and carries around one of the fav-links.
  Pressing ESC solves the problem. This happens every time I press
  umount.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May  6 17:52:28 2014
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'owner', 'group', 'mime_type', 
'where', 'permissions', 'date_accessed']"
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to trusty on 2014-04-22 (14 days ago)

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

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

[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

[Ben]

I've compiled 4.20-rc6 from VanVan's github repository, and it has no
effect on my UX391UA - still no sound.

I notice the patch doesn't actually refer specifically to the UX931UA
though, only other ASUS models.

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

[Ben]

I got an error when building the modules from @VanVan's github due to
/sound/pci/hda_codec.h having been moved to /include/sound/hda_codec.h

Fixing this let the compile finish without error (this is on Fedora 29).

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

[Ben]

Also works for me @vblack2006

I downloaded the current stable kernel from kernel.org (4.19.9), applied
the 3 patches that you linked to and added:

SND_PCI_QUIRK(0x1043, 0x10a1, "ASUS UX391UA", ALC294_FIXUP_ASUS_SPK

to /sound/pci/hda/patch_realtek.c

After compiling and installing, I now have sound working on my UX391UA
running Fedora 29!

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

[Ben]

The fixes in the 4.20-rc kernels are for other laptops, not the UX391UA.
You'll need to add:

SND_PCI_QUIRK(0x1043, 0x10a1, "ASUS UX391UA", ALC294_FIXUP_ASUS_SPK

to /sound/pci/hda/patch_realtek.c

to get sound working on this laptop.

I used the 4.19.9 kernel, applied the 3 linked patches and added the
line above.  If you're using 4.20-rc6 / 7, you may only need to add the
line to patch_realtek.c

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

[Ben]

@sojusnik

Yes, you're right, I missed the closing bracket.  The correct line to
add is:

SND_PCI_QUIRK(0x1043, 0x10a1, "ASUS UX391UA", ALC294_FIXUP_ASUS_SPK),

You won't find patch_realtek.c anywhere in /lib/modules/ because it's
already been compiled and installed.  You need to download the source
code, apply the patches, then compile and install the kernel.

Try downloading the 4.20-rc7 from kernel.org (the patches are already
applied to this version), extract it, and then edit
/sound/pci/hda/patch_realtek.c

Look for this line:

SND_PCI_QUIRK(0x1043, 0x14a1, "ASUS UX533FD", ALC294_FIXUP_ASUS_SPK),

And beneath it add:

SND_PCI_QUIRK(0x1043, 0x10a1, "ASUS UX391UA", ALC294_FIXUP_ASUS_SPK),

If you then compile and install the kernel, you should have working
sound on your UX391UA.

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

[Ben]

The UX391UA fix is not in 4.20 as it was already a release candidate.
To get sound working on this model you'll need to download the 4.20
source, apply the patch to sound/pci/hda/patch_realtek.c then compile
and install the kernel.

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 604798] Re: scanimage --batch crashed with SIGSEGV in gt68xx_line_reader_free_delays()

[Ben]

confirmed on Ubuntu MATE 16.04 fully patched as of 30 Aug 2016 with
Plustek OpticSlim M12 (networks scanner)

scanimage (sane-backends) 1.0.25git; backend version 1.0.25

scanimage -d gt68xx --batch="scanned_image-%d.tiff" --batch-prompt --format=tiff
Scanning -1 pages, incrementing by 1, numbering from 1
Place document no. 1 on the scanner.
Press  to continue.
Press Ctrl + D to terminate.

Scanning page 1
Scanned page 1. (scanner status = 5)
Place document no. 2 on the scanner.
Press  to continue.
Press Ctrl + D to terminate.

Scanning page 2
scanimage: sane_start: Invalid argument
Segmentation fault (core dumped)

The scanner feeds about 1mm of the second page then segfaults

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

Title:
  scanimage --batch crashed with SIGSEGV in
  gt68xx_line_reader_free_delays()

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  I'm using SANE with a Mustek BearPaw 1200CU Plus scanner, using the
  firmware from  (MD5 f2f275c5a8ad5dbdc43793f046612417).
  When I run "scanimage --batch", scanimage segfaults after scanning the
  first page and returning the head to the home position:

  bjh21@sole:~$ scanimage --batch
  Scanning -1 pages, incrementing by 1, numbering from 1
  Scanning page 1
  Scanned page 1. (scanner status = 5)
  Scanning page 2
  scanimage: sane_start: Invalid argument
  Segmentation fault (core dumped)

  Scanning multiple pages in succession using multiple invocations of
  "scanimage" works correctly.

  This bug differs from #117577 in that in my case the scanning head
  moves back to the home position and scanimage segfaults, neither of
  which happened there.  Otherwise it seems very similar.

  ProblemType: Crash
  DistroRelease: Ubuntu 10.04
  Package: sane-utils 1.0.20-13ubuntu2
  ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-23-generic i686
  NonfreeKernelModules: wl
  Architecture: i386
  Date: Mon Jul 12 21:57:57 2010
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-motts-20100121-3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/scanimage
  InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 
20100121-21:52
  ProcCmdline: scanimage --batch
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_GB.utf8
  SegvAnalysis:
   Segfault happened at: 0xde31c9 :   mov
0x88(%eax),%edx
   PC (0x00de31c9) ok
   source "0x88(%eax)" (0x0088) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: sane-backends
  StacktraceTop:
   gt68xx_line_reader_free_delays (reader=0x0) at gt68xx_mid.c:957
   gt68xx_line_reader_free (reader=0x0) at gt68xx_mid.c:1153
   gt68xx_scanner_stop_scan (scanner=0x9243128)
   sane_gt68xx_cancel (handle=0x9243128) at gt68xx.c:2108
   sane_dll_cancel (handle=0x922a348) at dll.c:1263
  Title: scanimage crashed with SIGSEGV in gt68xx_line_reader_free_delays()
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 1643467] Re: Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec

[Ben]

Judging from the posts in this bug report, it took 2 weeks and three
days to solve this problem for the end-users (for the other releases.
Support for precise ends in 16 weeks...

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

Title:
  Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec

Status in libav:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed
Status in libav package in Ubuntu:
  Invalid
Status in firefox source package in Precise:
  Fix Released
Status in libav source package in Precise:
  Confirmed
Status in firefox source package in Trusty:
  Fix Released
Status in libav source package in Trusty:
  Fix Released

Bug description:
  Whenever it tries to play a video, Firefox 50 displays this message at the 
top of every page:
  "libavcodec may be vulnerable or is not supported, and should be updated to 
play video"

  https://dxr.mozilla.org/mozilla-central/source/browser/locales/en-
  
US/chrome/browser/browser.properties?q=%22libavcodec+may+be+vulnerable%22&redirect_type=single#742

  Firefox refuses any libavcodec version prior to 54.35.1 (unless
  media.libavcodec.allow-obsolete==true).

  https://dxr.mozilla.org/mozilla-
  central/source/dom/media/platforms/ffmpeg/FFmpegLibWrapper.cpp#60

  Users should not be subjected to this warning, as it is vague (does not 
instruct them how to fix it).
  Ubuntu 14.04 LTS should ship with an updated version of libavcodec.

  DistroRelease: Ubuntu 14.04
  Package: firefox 50.0+build2-0ubuntu0.14.04.2

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

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

[Desktop-packages] [Bug 987060] Re: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04

[Ben]

16.10 have unity-panel-service taking up 3.5 GB of RAM. I've mainly
noticed it after resume, as Firefox randomly begins to crash/freeze
before the entire system becomes unstable.

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

Title:
  massive memory leak in unity-panel-service and hud-service when
  invoking the hud on Firefox profiles with large amounts of bookmarks
  LTS 12.04 14.04

Status in Unity HUD:
  Confirmed
Status in Application Menu Indicator:
  Confirmed
Status in Unity:
  Won't Fix
Status in firefox package in Ubuntu:
  Incomplete
Status in hud package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Invalid
Status in firefox source package in Xenial:
  Incomplete
Status in hud source package in Xenial:
  Confirmed
Status in unity source package in Xenial:
  Invalid

Bug description:
  unity-panel-service and hud-service quickly racks up memory and CPU
  usage until I kill it when invoking the HUD on Firefox. It's taking
  anywhere from a few minutes to half an hour, but it sometimes makes
  the system completely unusable.

  1. run Firefox 12.0 in the foreground
  2. hit Alt to bring up HUD
  3. type any text
  4. select one proposal from HUD
  5. wait for unity-panel-service and hud-service to fill up the remaining RAM 
and swap space.

  This is due to a high number of bookmarks in a user profile
  (hundreds).

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

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

[Desktop-packages] [Bug 1643042] [NEW] GUI Not Honoring Default GW Removal

[Ben]

Public bug reported:

I may be missing something, but I have done as much testing as I can
think of and have come up with the following:

OpenVPN Server v2.3.10-1ubuntu2 on Ubuntu Server 16.04.1 LTS 64bit
OpenVPN Client v2.3.10-1ubuntu2 on Ubuntu MATE 16.04 LTS 64bit
network-manager-openvpn-gnome version v1.1.93-1ubuntu1

When running OpenVPN from the CLI, and the server.conf instructs the
client to remove the default gateway and replace it with the tun0
adapter, it does as expected. However, using the same client.ovpn file
imported into the GUI does not remove the existing default gateway, it
simply moves it down the routing order. This can (and does) create a
routing leak on secure systems. Detailed info:

192.168.8.1 = local router (dirty router)
10.8.0.1= vpn server tun adapter (gateway)
10.8.0.5= laptop tun adapter address
12.34.56.78 = vpn server public internet address

# Connected to the dirty router, no VPN
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 192.168.8.1 0.0.0.0 UG60000 wlp2s0
192.168.8.0 0.0.0.0 255.255.255.0   U 60000 wlp2s0

# Connected to the OpenVPN using command line version 2.3.10-1ubuntu2
# sudo openvpn --config /path/to/client.ovpn
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 10.8.0.50.0.0.0 UG0  00 tun0
10.8.0.110.8.0.5255.255.255.255 UGH   0  00 tun0
10.8.0.50.0.0.0 255.255.255.255 UH0  00 tun0
12.34.56.78 192.168.8.1 255.255.255.255 UGH   0  00 wlp2s0

# Connected to the OpenVPN using network-manager-openvpn-gnome version 
1.1.93-1ubuntu1
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 10.8.0.50.0.0.0 UG50 00 tun0
0.0.0.0 192.168.8.1 0.0.0.0 UG60000 wlp2s0 
<== this entry is creating a routing leak
10.8.0.110.8.0.5255.255.255.255 UGH   50 00 tun0
10.8.0.50.0.0.0 255.255.255.255 UH50 00 tun0
12.34.56.78 192.168.8.1 255.255.255.255 UGH   60000 wlp2s0


Here is the relevant section of the server.conf;
push "redirect-gateway bypass-dhcp"
push "dhcp-option DNS 8.8.8.8"
push "dhcp-option DNS 8.8.4.4"

Note that the above does not include the 'def1' option in the push
redirect-gateway command, so the client is supposed to delete any
existing default gateways and install only the VPN default gateway. This
is the only way to be sure that 1) all traffic goes over the VPN, and 2)
when the client disconnects, the internet connection is severed and it's
much less likely that you accidentally lose your VPN and continue
transmitting unencrypted

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

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

Title:
  GUI Not Honoring Default GW Removal

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

Bug description:
  I may be missing something, but I have done as much testing as I can
  think of and have come up with the following:

  OpenVPN Server v2.3.10-1ubuntu2 on Ubuntu Server 16.04.1 LTS 64bit
  OpenVPN Client v2.3.10-1ubuntu2 on Ubuntu MATE 16.04 LTS 64bit
  network-manager-openvpn-gnome version v1.1.93-1ubuntu1

  When running OpenVPN from the CLI, and the server.conf instructs the
  client to remove the default gateway and replace it with the tun0
  adapter, it does as expected. However, using the same client.ovpn file
  imported into the GUI does not remove the existing default gateway, it
  simply moves it down the routing order. This can (and does) create a
  routing leak on secure systems. Detailed info:

  192.168.8.1 = local router (dirty router)
  10.8.0.1= vpn server tun adapter (gateway)
  10.8.0.5= laptop tun adapter address
  12.34.56.78 = vpn server public internet address

  # Connected to the dirty router, no VPN
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 192.168.8.1 0.0.0.0 UG60000 wlp2s0
  192.168.8.0 0.0.0.0 255.255.255.0   U 60000 wlp2s0

  # Connected to the OpenVPN using command line version 2.3.10-1ubuntu2
  # sudo openvpn --config /path/to/client.ovpn
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 10.8.0.50.0.0.0 UG0  00 tun0
  10.8.0.110.8.0.5255.255.255.255 UGH   0  00 tun0
  10.8.0.50.0.0.0 255.255.255.255 UH0  00 tun0
  12.34.56.78 192.168.8.1 255.255.255.255 UGH   0  00 wlp2s0

  # Connected to t

[Desktop-packages] [Bug 1434351] Re: X fonts and widgets disappear after suspend/resume cycle

[Ben]

I think I recently worked around this on Xubuntu (Ubuntu 16.04.2 LTS) by 
removing all xscreensaver remnants (which I believe to be conflicting with 
Light Locker). I did this, but use at your own risk:
```
sudo apt-get remove $(apt-cache search "^xscreensaver" | cut -d ' ' -f1 | tr 
'\n' ' ')
```

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

-- 
Mailing list: https://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 1434351] Re: X fonts and widgets disappear after suspend/resume cycle

[Ben]

I'm afraid I did not, no.

On 21 February 2017 at 10:16, Ben <1434...@bugs.launchpad.net> wrote:

> I think I recently worked around this on Xubuntu (Ubuntu 16.04.2 LTS) by
> removing all xscreensaver remnants (which I believe to be conflicting with
> Light Locker). I did this, but use at your own risk:
> ```
> sudo apt-get remove $(apt-cache search "^xscreensaver" | cut -d ' ' -f1 |
> tr '\n' ' ')
> ```
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1434351
>
> Title:
>   X fonts and widgets disappear after suspend/resume cycle
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   After a suspend/resume cycle, the screen comes up normally, but every
>   time I move my mouse over a piece of text, button, widget, etc, the
>   text vanishes and it's replaced by a plain rectangle.
>
>   This does not affect xterm, but it does affect any GTK apps, firefox,
>   etc.
>
>   xfce-panel vanishes, although it's still responding to mouse-clicks.
>   Newly opened menus are grey rectangles.
>
>   The lines underlining menu hotkeys do NOT disappear.
>
>   In the attached screenshot, you can clearly see which buttons I have
>   waved the mouse over, and which I have not.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 15.04
>   Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
>   ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
>   Uname: Linux 3.19.0-9-generic x86_64
>   ApportVersion: 2.16.2-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: XFCE
>   Date: Thu Mar 19 19:51:37 2015
>   InstallationDate: Installed on 2015-03-05 (14 days ago)
>   InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64
> (20150218.1)
>   SourcePackage: xserver-xorg-video-intel
>   UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+subscriptions
>

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

[Ben]

Hi,
I am also affected by this bug. Any chance to ask maintainers to upgrade both 
packages?

https://wiki.gnome.org/Projects/NetworkManager
https://git.gnome.org/browse/network-manager-openvpn

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

Title:
  NetworkManager ignores pushed openvpn routes

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

Bug description:
  Relevant information that may or may not have been included by ubuntu-
  bug:

  Ubuntu release 16.04
  Package network-manager 1.2.0-0ubuntu0.16.04.2
  Package network-manager-openvpn 1.1.93-1ubuntu1

  NetworkManager ignores pushed openvpn routes when "Use this connection
  only for resources on its network" is checked.  This is a behavior
  change since 14.04.

  To repeat:

  1) Use an OpenVpn server that pushes routes.  I suggest using a server
  that pushes several routes since this makes their absence obvious.
  Set up a NetworkManager VPN of type OpenVpn to this server.  Select
  "Use this connection only for resources on its network" in the
  "Routes" section of the IPV4 options.

  2) Set up a raw OpenVpn connection to the same server.

  3) Connect to the server using the raw OpenVpn connection.  The pushed
  routes are all there.

  4) Connect to the server using NetworkManager.  The only route added
  is a n interface level route to the tunnel device network.

  Using the same setup on 14.04, all pushed routes are added.

  
  The missing routes are also "Resources on the VPN network", and should be 
added in the absence of further direction.  Ignoring pushed routes should be 
controlled by the "Ignore automatically obtained routes" checkbox.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager-openvpn 1.1.93-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Jul 15 23:12:55 2016
  InstallationDate: Installed on 2016-05-04 (72 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1133477] Re: cut-n-paste move files got stuck forever

[Ben]

Apologies for the double comment - but I realized I missed one of your
questions. The size and type of files does not seem to matter. I've had
this happen with text, image, video, and "other" files of sizes from a
couple kilobytes up to several megabytes. I have not tested with a large
number of files of several gigabytes, though I don't imagine it would be
as noticeable since one would reasonably expect those to take a bit of
time to copy normally.

As far as I can tell there are no definite triggers. When I was first
doing a prototype build of Ubuntu 16.04 LTS and ran into this bug, I did
a fresh build, updated all packages, and then was able to easily
replicate after a clean boot and nothing running except the file
browser. My current system uses SSD drives only, but I have also
verified on a system with spindle disks.

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

Title:
  cut-n-paste move files got stuck forever

Status in nautilus package in Ubuntu:
  Incomplete
Status in pcmanfm package in Ubuntu:
  Incomplete

Bug description:
  With Nautilus, I navigated to a folder that contained about 2,000 gif files.
  I selected all of them
  I cut with Ctrl+X
  I navigated to another folder
  I pasted with Ctrl+V

  => A popup window appeared saying "Preparing to move N files", and it got 
stuck there forever.
  Nautilus stopped responding. I waited half an hour, then I had to kill it.

  Actually some of the files were moved. Which is the worst thing that
  could happen.

  I tried again with the remaining files and it happened again!! It's
  systematic!!

  I suspect it has to do with displaying the previews of a big number of
  files. Nautilus becomes completely unmanageable whenever you open
  folders with lots of files. Maximum priority should be given to the UI
  and actual operations; displaying of the previews should be done in
  the background and should never, ever slow down user operations the
  slightest bit. Seems pretty obvious.

  Also note that 2000 is not even that much. Actually it's very few
  files.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.5.0-25.38-generic 3.5.7.4
  Uname: Linux 3.5.0-25-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: i386
  Date: Tue Feb 26 18:23:52 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'1312x713+64+71'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'180'
   b'org.gnome.nautilus.window-state' b'start-with-status-bar' b'true'
  InstallationDate: Installed on 2010-06-23 (979 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to quantal on 2013-01-13 (44 days ago)

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

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

[Desktop-packages] [Bug 1133477] Re: cut-n-paste move files got stuck forever

[Ben]

I just tested this very easily, but unfortunately nothing was recorded
in any of the /var/logs. The steps I used to replicate on a Lenovo P50
running Ubuntu Mate 16.04 LTS (fully updated as of 29 March 2017)

1) Open Caja 1.12.7 (also tested using Nautilus on Ubuntu 16.04 LTS)
2) Navigate to a folder that has 500 text files in it of very small size 
(5-10kb is sufficient)
3) Press F3 to open a new pane (or optionally open a new window, doesn't 
matter) and navigate to an empty folder on the same drive (or a different 
drive, doesn't matter)
4) Highlight most or all of the files in the source directory, and press CTRL-X 
(or edit > cut, doesn't matter)
5) Go to the destination pane, and press CTRL-V (or edit > paste, doesn't 
matter)

Sometimes, the cut/paste will happen nearly instantly as it should.
Sometimes though, it will take a second or two to start, then spend
between 1 and 20 minutes sitting there, copying the files one-by-one,
very very very very very slowly. This issue is not reproducible using
the 'cp' or 'mv' command line programs.

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

Title:
  cut-n-paste move files got stuck forever

Status in nautilus package in Ubuntu:
  Incomplete
Status in pcmanfm package in Ubuntu:
  Incomplete

Bug description:
  With Nautilus, I navigated to a folder that contained about 2,000 gif files.
  I selected all of them
  I cut with Ctrl+X
  I navigated to another folder
  I pasted with Ctrl+V

  => A popup window appeared saying "Preparing to move N files", and it got 
stuck there forever.
  Nautilus stopped responding. I waited half an hour, then I had to kill it.

  Actually some of the files were moved. Which is the worst thing that
  could happen.

  I tried again with the remaining files and it happened again!! It's
  systematic!!

  I suspect it has to do with displaying the previews of a big number of
  files. Nautilus becomes completely unmanageable whenever you open
  folders with lots of files. Maximum priority should be given to the UI
  and actual operations; displaying of the previews should be done in
  the background and should never, ever slow down user operations the
  slightest bit. Seems pretty obvious.

  Also note that 2000 is not even that much. Actually it's very few
  files.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.5.0-25.38-generic 3.5.7.4
  Uname: Linux 3.5.0-25-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: i386
  Date: Tue Feb 26 18:23:52 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'1312x713+64+71'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'180'
   b'org.gnome.nautilus.window-state' b'start-with-status-bar' b'true'
  InstallationDate: Installed on 2010-06-23 (979 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to quantal on 2013-01-13 (44 days ago)

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

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

[Desktop-packages] [Bug 1133477] Re: cut-n-paste move files got stuck forever

[Ben]

Thanks again for taking the time.

It's difficult to say exactly the number at which it occurs because
there's a point at which the normal time to copy a small number of files
crosses the point where it is no longer normal to copy lots of small
files. I can say that I've never _noticed_ it with less than 50 files,
but then again - even if it happened with less than 50 files the delay
may have been small enough where I didn't realize the issue happened.
I've definitely noticed it with as few as 50 files. I did some testing
with 20 and 40 files this morning but didn't notice any issue.

This definitely has not occurred in Ubuntu 14.04 using Nautilus
1:3.10.1-0ubuntu8 and previous versions (all the way back to launch). It
definitely never happened with Ubuntu 10.04 LTS or 7.04 LTS and any
version of Nautilus included in their stable releases.

I'm almost certain it never happened with Linux Mint 17 and Linux Mint
17 MATE, but I can't say that for certain as I abandoned those distros
pretty quickly after finding it did not meet my needs.

I don't recall which version of Caja originally shipped with Ubuntu MATE
16.04 LTS, but I installed MATE 16.04 LTS on launch day and keep my
packages updated at least weekly, and this issue has been present in all
versions.

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

Title:
  cut-n-paste move files got stuck forever

Status in nautilus package in Ubuntu:
  Incomplete
Status in pcmanfm package in Ubuntu:
  Incomplete

Bug description:
  With Nautilus, I navigated to a folder that contained about 2,000 gif files.
  I selected all of them
  I cut with Ctrl+X
  I navigated to another folder
  I pasted with Ctrl+V

  => A popup window appeared saying "Preparing to move N files", and it got 
stuck there forever.
  Nautilus stopped responding. I waited half an hour, then I had to kill it.

  Actually some of the files were moved. Which is the worst thing that
  could happen.

  I tried again with the remaining files and it happened again!! It's
  systematic!!

  I suspect it has to do with displaying the previews of a big number of
  files. Nautilus becomes completely unmanageable whenever you open
  folders with lots of files. Maximum priority should be given to the UI
  and actual operations; displaying of the previews should be done in
  the background and should never, ever slow down user operations the
  slightest bit. Seems pretty obvious.

  Also note that 2000 is not even that much. Actually it's very few
  files.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.5.0-25.38-generic 3.5.7.4
  Uname: Linux 3.5.0-25-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: i386
  Date: Tue Feb 26 18:23:52 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'1312x713+64+71'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'180'
   b'org.gnome.nautilus.window-state' b'start-with-status-bar' b'true'
  InstallationDate: Installed on 2010-06-23 (979 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to quantal on 2013-01-13 (44 days ago)

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

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

[Desktop-packages] [Bug 1294899] Re: Import saved VPN connection has been Recently Broken

[Ben]

Is someone still working on this? I use Lubuntu 14.04. LTS and cannot
import an openvpn.ovpn file using the network manager. It says it cannot
read the "PPTP-configuration". Ist there any other way to generate a
openvpn-connection than importing a setup-file?

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

Title:
  Import saved VPN connection has been Recently Broken

Status in OpenVPN:
  Invalid
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-openvpn package in Ubuntu:
  Confirmed
Status in network-manager-applet source package in Trusty:
  Fix Released
Status in network-manager-openvpn source package in Trusty:
  Invalid
Status in network-manager-applet source package in Utopic:
  Fix Released
Status in network-manager-openvpn source package in Utopic:
  Invalid
Status in network-manager-openvpn package in Debian:
  New

Bug description:
  SRU Request:

  [Impact]
  Attempting to import a saved VPN connection file results in a segault. This 
is regression in Ubuntu 14.04 that worked correctly in previous versions.

  [Test Case]
  1- install network-manager-openvpn and network-manager-openvpn-gnome
  2- from the network-manager indicator, click on Edit Connections
  3- Click on Add
  4- Select Import a saved VPN configuration, and open the file in comment #28

  Expected results: a window should appear with the imported information
  Current results: network-manager's connection editor segfaults

  [Regression potential]
  This SRU simply adds a couple of missing sections to the 
11-user-connections.patch patch that went missing. If the fix is broken, either 
the vpn files won't import, or creating a new vpn connection could break 
completely.


  Original description:
  I believe recent changes have broken network-manager-openvpn feature that 
allows you to "Import saved VPN connection".

  I've tested this feature with bundles that I've definitely imported
  successfully in the past.

  Now, not only does it not import, but it gives absolutely no feedback
  at all; the window just disappears as though I didn't just ask it to
  import a VPN.conf file. The folder (I'm importing the .conf file from)
  includes all the necessary supporting files. I'm very sure this is not
  a user error on my part. I've done this several times in the past and
  I'm certain that the files (that are currently being ignored without
  dialog feedback) are exactly the same as they were when I was able to
  import successfully a few weeks ago.

  I've tested this on multiple machines that have Ubuntu 14.04 installed
  and fully updated.

  And, even if the files were indeed corrupted (which I'm certain they
  are not), the fact that the UI just disappears, instead of showing an
  error, is a bug within itself.

  Also, I'd like to point out, that I was able to set up this VPN bundle
  manually. The point of this bug is to report that the ability to
  import via .conf files (so that you don't have to set things manually)
  has recently became nonfunctional.

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

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

[Desktop-packages] [Bug 1534270] [NEW] [Latitude E7450, Realtek ALC3235, Speaker, Internal] No sound at all. Installed update to software, then no more sound (through headphones or laptop)

[Ben]

Public bug reported:

I have no idea why the sound went out (assuming because I installed an
update), and no idea where the problem is.  I tried a number of things
from the internet, but nothing worked.  Forced a reload of alsa - no
luck.  Re-installed alsa pulseaudio - no luck.

Please help!  Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-43.49~14.04.1-generic 3.19.8-ckt10
Uname: Linux 3.19.0-43-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC1D0p:   ben2320 F...m pulseaudio
 /dev/snd/controlC1:  ben2320 F pulseaudio
CurrentDesktop: Unity
Date: Thu Jan 14 14:10:05 2016
InstallationDate: Installed on 2015-09-29 (107 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [Latitude E7450, Realtek ALC3235, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/06/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 06HN6G
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd08/06/2015:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn06HN6G:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7450
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug trusty

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

Title:
  [Latitude E7450, Realtek ALC3235, Speaker, Internal] No sound at all.
  Installed update to software, then no more sound (through headphones
  or laptop)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have no idea why the sound went out (assuming because I installed an
  update), and no idea where the problem is.  I tried a number of things
  from the internet, but nothing worked.  Forced a reload of alsa - no
  luck.  Re-installed alsa pulseaudio - no luck.

  Please help!  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-43.49~14.04.1-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   ben2320 F...m pulseaudio
   /dev/snd/controlC1:  ben2320 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jan 14 14:10:05 2016
  InstallationDate: Installed on 2015-09-29 (107 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Latitude E7450, Realtek ALC3235, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 06HN6G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd08/06/2015:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn06HN6G:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 604798] Re: scanimage --batch crashed with SIGSEGV in gt68xx_line_reader_free_delays()

[Ben]

confirmed on Ubuntu 14.04.03 fully patched as of 27 Jan 2016 with
Plustek OpticSlim M12 (networks scanner)

scanimage (sane-backends) 1.0.23; backend version 1.0.23


scanimage -d gt68xx --batch="scanned_image-%d.tiff" --batch-prompt --format=tiff
Scanning -1 pages, incrementing by 1, numbering from 1
Place document no. 1 on the scanner.
Press  to continue.
Press Ctrl + D to terminate.

Scanning page 1
Scanned page 1. (scanner status = 5)
Place document no. 2 on the scanner.
Press  to continue.
Press Ctrl + D to terminate.

Scanning page 2
scanimage: sane_start: Invalid argument
Segmentation fault (core dumped)


The scanner feeds about 1mm of the second page then segfaults

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

Title:
  scanimage --batch crashed with SIGSEGV in
  gt68xx_line_reader_free_delays()

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  I'm using SANE with a Mustek BearPaw 1200CU Plus scanner, using the
  firmware from  (MD5 f2f275c5a8ad5dbdc43793f046612417).
  When I run "scanimage --batch", scanimage segfaults after scanning the
  first page and returning the head to the home position:

  bjh21@sole:~$ scanimage --batch
  Scanning -1 pages, incrementing by 1, numbering from 1
  Scanning page 1
  Scanned page 1. (scanner status = 5)
  Scanning page 2
  scanimage: sane_start: Invalid argument
  Segmentation fault (core dumped)

  Scanning multiple pages in succession using multiple invocations of
  "scanimage" works correctly.

  This bug differs from #117577 in that in my case the scanning head
  moves back to the home position and scanimage segfaults, neither of
  which happened there.  Otherwise it seems very similar.

  ProblemType: Crash
  DistroRelease: Ubuntu 10.04
  Package: sane-utils 1.0.20-13ubuntu2
  ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-23-generic i686
  NonfreeKernelModules: wl
  Architecture: i386
  Date: Mon Jul 12 21:57:57 2010
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-motts-20100121-3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/scanimage
  InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 
20100121-21:52
  ProcCmdline: scanimage --batch
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_GB.utf8
  SegvAnalysis:
   Segfault happened at: 0xde31c9 :   mov
0x88(%eax),%edx
   PC (0x00de31c9) ok
   source "0x88(%eax)" (0x0088) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: sane-backends
  StacktraceTop:
   gt68xx_line_reader_free_delays (reader=0x0) at gt68xx_mid.c:957
   gt68xx_line_reader_free (reader=0x0) at gt68xx_mid.c:1153
   gt68xx_scanner_stop_scan (scanner=0x9243128)
   sane_gt68xx_cancel (handle=0x9243128) at gt68xx.c:2108
   sane_dll_cancel (handle=0x922a348) at dll.c:1263
  Title: scanimage crashed with SIGSEGV in gt68xx_line_reader_free_delays()
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 253167] Re: Rhythmbox sort by "Album Artist" for guest/compilations

[Ben]

Cheers, I am using Rhythmbox in 2015. Let me explain why.

1. It is extremely clean, which I love and this also fits my Lubuntu
System. Banshee is not nice to look at.

2. It is supporting the folders of my NAs that I mount via SMB. Amarok
and GKTpod do not provide this.

That's why i decided to use it even after I recognised that I cannot
sort my compilations via albumartist. I decided to override all the
artists with only one. I like a simpe structure. But it feels wrong to
not have access to the real artists of the songs any more.

So I really would ask for someone to code this. Rhythmbox is an awesome
client and fits extremely well into the whole Lubuntu world.

Thank you very much,
Ben

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

Title:
  Rhythmbox sort by "Album Artist" for guest/compilations

Status in Rhythmbox:
  Confirmed
Status in rhythmbox package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: rhythmbox

  For guest artists on an album or compilations Apple allows definition
  of an album artist and artist for each track.  Rhythmnbox only allows
  browsing by track artists so many artists appear listed with only one
  track.

  Example, Red Book by Texas:

  1. 036 - Texas
  2. Getaway - Texas
  3. Can't Resist - Texas
  4. What About Us - Texas
  5. Cry - Texas
  6. Sleep - Texas featuring Paul Buchanan
  7. Get Down Tonight - Texas
  8. Nevermind - Texas
  9. Bad Weather - Texas
  10. Master Thief - Texas
  11. Just Holding On - Texas
  12. Red Book  - Texas

  The sixth track has artist "Texas featuring Paul Buchanan" whilst all
  others are "Texas".

  I want to browse by album artist selecting "Texas" and seeing all 12
  tracks on the album, not just the 11 that match.

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

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

[Desktop-packages] [Bug 1763662] [NEW] H264 missing from WebRTC (regression)

[Ben]

Public bug reported:

H264 is missing from WebRTC in Chromium 65.0.3325.181.
This is a regression. It worked in Chromium 64.0.3282.167.
According to the webrtc team it might be because of a missing flag [1].

Steps to reproduce:
1. Install Chromium on Ubuntu 16.04: sudo apt-get install -y chromium-browser 
chromium-codecs-ffmpeg-extra
2. open a tab with chrome://webrtc-internals
3. Create a room in https://appr.tc and join the room.
3. Check the SDP offer in webrtc-internals. Select the 
https://appr.tc/r/ tab and click on the createOfferOnSuccess event.

We should have H264 in the SDP offer but it's missing:
a=rtpmap:100 H264/9

[1] https://bugs.chromium.org/p/webrtc/issues/detail?id=9096

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  H264 missing from WebRTC (regression)

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  H264 is missing from WebRTC in Chromium 65.0.3325.181.
  This is a regression. It worked in Chromium 64.0.3282.167.
  According to the webrtc team it might be because of a missing flag [1].

  Steps to reproduce:
  1. Install Chromium on Ubuntu 16.04: sudo apt-get install -y chromium-browser 
chromium-codecs-ffmpeg-extra
  2. open a tab with chrome://webrtc-internals
  3. Create a room in https://appr.tc and join the room.
  3. Check the SDP offer in webrtc-internals. Select the 
https://appr.tc/r/ tab and click on the createOfferOnSuccess event.

  We should have H264 in the SDP offer but it's missing:
  a=rtpmap:100 H264/9

  [1] https://bugs.chromium.org/p/webrtc/issues/detail?id=9096

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

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

[Desktop-packages] [Bug 1763662] Re: H264 missing from WebRTC (regression)

[Ben]

Chrome 66 was released on April 17th.
When Chromium 66 is planned to be released?
Any reason not to sync Chrome and Chromium releases?

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

Title:
  H264 missing from WebRTC (regression)

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  H264 is missing from WebRTC in Chromium 65.0.3325.181.
  This is a regression. It worked in Chromium 64.0.3282.167.
  According to the webrtc team it might be because of a missing flag [1].

  Steps to reproduce:
  1. Install Chromium on Ubuntu 16.04: sudo apt-get install -y chromium-browser 
chromium-codecs-ffmpeg-extra
  2. open a tab with chrome://webrtc-internals
  3. Create a room in https://appr.tc and join the room.
  3. Check the SDP offer in webrtc-internals. Select the 
https://appr.tc/r/ tab and click on the createOfferOnSuccess event.

  We should have H264 in the SDP offer but it's missing:
  a=rtpmap:100 H264/9

  [1] https://bugs.chromium.org/p/webrtc/issues/detail?id=9096

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

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

[Desktop-packages] [Bug 1684213] Re: Intel Wireless 7260 often crashes

[Ben]

Just a few updates which may be of use to anyone else having the same
issues...

1). As this issue persists without a truly good solution, it may be a
good idea to simply replace the wifi card with, say, an Atheros one
which works better. You can find them relatively cheaply on ebay.

2). One of the major issues that I was having was that my main Wifi
would crash internally, then whenever I tried to plug in a USB Wifi
adapter they wouldn't work either, leaving me literally without any
method of getting (wireless) internet. I assumed these two issues were
connected, however, further research has led me to believe otherwise.

I tried entirely removing the internal wifi card to see if that would
make a difference on the USB wifi cards, yet still neither of mine
worked. Further looking revealed one or two strange oddities...

phy#1
Interface wlx000f6001cb1f
ifindex 3
wdev 0x10001
addr 00:0f:60:01:cb:1f
type managed
txpower 20.00 dBm

The interface is WAY out of convention. As explained here
(https://superuser.com/questions/1086632/wlan1-showing-as-weird-
characters#1086705), interface names are limited to 16 bytes. My theory
is that when network-manager tries to connect with this interface, it
breaks that limit. The solution suggested in that thread works, append
net.ifnames=0 to the kernel parameters in grub and suddenly all of my
USB wifi adapters work fantastically.

I have a feeling this itself may warrant a separate bug report, I'll do
some looking and see if anyone else is having the same issue/if
someone's already reported it.

TL;DR: If your USB wifi doesn't work and you get weird/long interface
names from "iw dev", use "net.ifnames=0" to fix the interface name and
take back your wifi.

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

Title:
  Intel Wireless 7260 often crashes

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS 
enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses 
Intel 7260 wifi, rev. bb:
  01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently,
  everything (kernel, firmware, etc.) is stock. Issue has persisted
  across multiple installations.

  Bug: Wifi/Bluetooth crashes and refuses to come back up, even after
  multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.)

  When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, 
upon boot, it is not uncommon for the wireless to stop working within two 
minutes of login time. Curiously, the GUI usually still shows being 
"connected", though trying to change anything with the wifi shows otherwise. 
Other times, upon system resume when wireless was previously working, the GUI 
will show "device not ready" and refuse to continue. Dmesg shows the following:
  [  423.814823] Bluetooth: hci0 command 0x1403 tx timeout
  [  424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  424.173067] iwlwifi :01:00.0: Scan failed! ret -5
  [  425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  425.194593] iwlwifi :01:00.0: Scan failed! ret -5

  Solution: Rebooting doesn't fix the problem. Perhaps a different
  firmware version will work better? Configuration settings? etc.?
  Unknown.

  Thanks ahead of time for the help. Let me know if there's anything you
  need/commands I should run/solutions I can attempt.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bmueller   1669 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Apr 19 10:34:11 2017
  InstallationDate: Installed on 2017-04-13 (6 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp.
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Gnawty
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=45b1dd3f-10df-4a28-904c-74c694ef75a5

[Desktop-packages] [Bug 550856] Re: page size setting is broken, use it as default crop or fix it by other means

[Ben]

Sylvain, I had the same issue recently (before it worked well) and your
workaround did the job! However, I had to change page size once after
restart from "A4" to "automatic" to take effect (changed it back then to
A4). Thanks a lot!

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

Title:
  page size setting is broken, use it as default crop or fix it by other
  means

Status in Simple Scan:
  Fix Released
Status in Simple Scan 3.10 series:
  Fix Released
Status in Simple Scan 3.11 series:
  Fix Released
Status in simple-scan package in Ubuntu:
  Fix Released
Status in simple-scan source package in Saucy:
  Fix Released
Status in simple-scan source package in Trusty:
  Fix Released

Bug description:
  For some SANE drivers simple scan always scans the largest scan area
  ignoring the "Page Size" setting in the preferences.

  To reproduce:
  1. Open Simple Scan
  2. Set page size in Document > Prefrences > Page Size, e.g. to "4x6"
  3. Scan a document
  Expected result:
  The document is scanned at the requested size
  Observed result:
  The document is scanned at the maximum size

  Regression potential:
  Low. The fix was to set the page size using an alternative method for drivers 
that do not support the page-width, page-height options. There is a small 
chance that these settings might change behaviour / expose bugs on drivers that 
were previously working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/simple-scan/+bug/550856/+subscriptions

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

[Desktop-packages] [Bug 2027790] [NEW] bash completion doesn't show "remove" option

[Ben Aceler]

Public bug reported:

Flatpak package contains bash script for bash completion feature. If I
say `flatpak in`, I will got `info` and `install` options.

Flatpak autocomplete options doesn't work for `remove` option. If I say
`flatpak rem`, I will got only `remote`, and `remove` will not be
suggested.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: flatpak 1.14.4-1ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12
Uname: Linux 6.2.0-24-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 14 13:30:21 2023
ProcEnviron:
 LANG=ru_RU.UTF-8
 PATH=(custom, no user)
 SHELL=/usr/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: flatpak
UpgradeStatus: Upgraded to lunar on 2023-05-14 (60 days ago)

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


** Tags: amd64 apport-bug lunar wayland-session

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

Title:
  bash completion doesn't show "remove" option

Status in flatpak package in Ubuntu:
  New

Bug description:
  Flatpak package contains bash script for bash completion feature. If I
  say `flatpak in`, I will got `info` and `install` options.

  Flatpak autocomplete options doesn't work for `remove` option. If I
  say `flatpak rem`, I will got only `remote`, and `remove` will
  not be suggested.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: flatpak 1.14.4-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12
  Uname: Linux 6.2.0-24-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 14 13:30:21 2023
  ProcEnviron:
   LANG=ru_RU.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: flatpak
  UpgradeStatus: Upgraded to lunar on 2023-05-14 (60 days ago)

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


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

[Desktop-packages] [Bug 2021929] [NEW] upgrade to exiv2 0.28.0

[Ben McCann]

Public bug reported:

The latest release is 0.28.0 and fixes some bugs I've encountered

https://github.com/Exiv2/exiv2/releases/tag/v0.28.0

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

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

Title:
  upgrade to exiv2 0.28.0

Status in exiv2 package in Ubuntu:
  New

Bug description:
  The latest release is 0.28.0 and fixes some bugs I've encountered

  https://github.com/Exiv2/exiv2/releases/tag/v0.28.0

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


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