date:20181014

per test the build with the commit in #9 that fourdollars prepare in
http://people.ubuntu.com/~fourdollars/1730211/, it fix the bug.

** Tags removed: artful
** Tags added: bionic

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

Title:
  Unable to type capital letters using onscreen keyboard

Status in OEM Priority Project:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Unable to type capital letters using onscreen keyboard:

  1. Launch a program where you can type text (gedit for example).
  2. Activate on screen keyboard (by touching the screen, foe example).
  3. Notice all the keys on the on screen keyboard display lowercase letters.

  4. Begin typing.  Lowercase characters are typed into the text area.

  5. Tap on the Shift (up arrow at left side of on screen keyboard) key of the 
on screen keyboard.
  6. Notice all the keys on the on screen keyboard now display capital letters.
  7. Begin typing.
  8. A lowercase character will be typed into the text area.

  This is not expected behavior.
  Instead, a capital letter should have been typed.

  (All the keys on the on screen keyboard revert to lower case. This is
  expected, since the on screen shift key would need to be pressed again
  in order to attempt to type another capital character).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: caribou 0.4.21-2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov  5 10:57:04 2017
  InstallationDate: Installed on 2017-11-03 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.23 amd64 "Custom Artful Aardvark"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: caribou
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1730211/+subscriptions

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

[Desktop-packages] [Bug 1760399] Re: New On-screen keyboard cannot be manually triggered to appear

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

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

Title:
  New On-screen keyboard cannot be manually triggered to appear

Status in OEM Priority Project:
  New
Status in caribou package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I have always used an on-screen keyboard as a virtual keyboard for
  entering text in a different layout than my physical keyboard. This
  time I cannot, since I cannot manually trigger the new OSK.

  Steps:

  1. Open Firefox
  2. Try to enter text in a different layout using the new OSK
  3. You cannot make the OSK appear

  When enabled, the new OSK appears automatically in Activities, but I
  cannot trigger it outside GNOME apps. You have to enable the new OSK
  first from Universal Access in Settings.

  I consider this a regression from 16.04 LTS, where On-board is easily
  triggered.

  Workaround:

  sudo apt install onboard

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  1 11:31:16 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-02 (180 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-03-27 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1760399/+subscriptions

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

[Desktop-packages] [Bug 1797834] Re: Ubuntu dash-to-dock "Show on" bug

Please run this command to send us more information

  apport-collect 1797834

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: New => Incomplete

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

Title:
  Ubuntu dash-to-dock "Show on" bug

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Incomplete

Bug description:
  Dear developers,

  How are you?

  I've noticed a bug/typo on the Settings->Dock->`Show on` settings on
  dual monitors: the Ubuntu Dock show on to the opposite of the display.
  In my case: I set "HP 23es" as my primary monitor while built-in
  screen as my secondary monitor, I then switch the "Show on" from "HP
  23es" to "Built-in" display, then back again to "HP 23es", now the
  Ubuntu dock show on the "Built-in" monitor instead of the "HP 23es".
  And if I switch to "Built-in" display, the dock display on "HP 23es",
  which is doing opposite operation. What I guess is that the Ubuntu
  dock shows the typo information since I've tried dash-to-dock
  extension without any problems.

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

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

[Desktop-packages] [Bug 1797835] Re: Shutdown or logout button have to click twice

Please run this command to send us more information:

  apport-collect 1797835

** Package changed: gnome-shell-extension-ubuntu-dock (Ubuntu) => gnome-
shell (Ubuntu)

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

** Tags added: bionic

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

Title:
  Shutdown or logout button have to click twice

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Dear developers,

  How are you? I've been fresh install the Ubuntu 18.04.1 LTS and facing
  a new bug randomly, that is the shutdown and logout button sometimes
  have to be clicked twice to take effects.

  Best,
  syscl

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

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

[Desktop-packages] [Bug 1766103] Re: bionic: VPN not working at all

2018-10-14 Thread Raatikka

I upgraded from Xenial to Bionic and noticed the same. I also noticed
that bug preventing from using VPN has been open for 6 months now! Could
this be added to your priority list?

Now, I need to be able to use VPN (like many who work for their living).
Is there anything I can do for it (in Bionic) or is the best option to
downgrade to Xenial?

Thanks

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

Title:
  bionic: VPN not working at all

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

Bug description:
  VPN is completely busted on bionic-desktop (4/21/2018).  In 17.10 my
  VPN was still working, "only" had to do a `killall nm-applet; nohup
  nm-applet &` to get the password prompt to show up.  In bionic, at
  least that portion now works without work-around.  However, I can't
  establish my VPN to my workplace at all.

  My VPN configuration in /etc/NetworkManager/system-connections/Test
  seems rather basic:

  [connection]
  id=Test
  uuid=ae916f15-2e8d-46b0-92d3-c2dece212c40
  type=vpn
  autoconnect=false
  permissions=user:thomas:;

  [vpn]
  domain=XX.XXX
  gateway=vpn.XX.XXX
  password-flags=2
  refuse-chap=yes
  refuse-eap=yes
  refuse-pap=yes
  require-mppe=yes
  user=Y
  service-type=org.freedesktop.NetworkManager.pptp

  [ipv4]
  dns=10.11.11.11;
  dns-search=
  method=auto
  never-default=true
  route1=10.11.0.0/16,10.11.31.31

  [ipv6]
  addr-gen-mode=stable-privacy
  dns-search=
  method=ignore

  Here's the logs from syslog:

  Apr 22 10:29:18 thomas-bionic NetworkManager[507]:   [1524414558.0300] 
audit: op="connection-activate" uuid="ae916f15-2e8d-46b0-92d3-c2dece212c40" 
name="Test" pid=1141 uid=1000 result="success"
  Apr 22 10:29:18 thomas-bionic gnome-shell[781]: JS ERROR: TypeError: item is 
undefined#012setActiveConnections/<@resource:///org/gnome/shell/ui/status/network.js:1518:17#012setActiveConnections@resource:///org/gnome/shell/ui/status/network.js:1515:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
  Apr 22 10:29:18 thomas-bionic NetworkManager[507]:   [1524414558.0445] 
vpn-connection[0x555885252640,ae916f15-2e8d-46b0-92d3-c2dece212c40,"Test",0]: 
Started the VPN service, PID 2601
  Apr 22 10:29:18 thomas-bionic NetworkManager[507]:   [1524414558.0631] 
vpn-connection[0x555885252640,ae916f15-2e8d-46b0-92d3-c2dece212c40,"Test",0]: 
Saw the service appear; activating connection
  Apr 22 10:29:21 thomas-bionic NetworkManager[507]:   [1524414561.2896] 
settings-connection[0x55588511f440,ae916f15-2e8d-46b0-92d3-c2dece212c40]: 
write: successfully updated (keyfile: update 
/etc/NetworkManager/system-connections/Test 
(ae916f15-2e8d-46b0-92d3-c2dece212c40,"Test")), connection was modified in the 
process
  Apr 22 10:29:21 thomas-bionic NetworkManager[507]:   [1524414561.3008] 
vpn-connection[0x555885252640,ae916f15-2e8d-46b0-92d3-c2dece212c40,"Test",0]: 
VPN connection: (ConnectInteractive) reply received
  Apr 22 10:29:21 thomas-bionic NetworkManager[507]:   [1524414561.3095] 
vpn-connection[0x555885252640,ae916f15-2e8d-46b0-92d3-c2dece212c40,"Test",0]: 
VPN plugin: state changed: starting (3)
  Apr 22 10:29:21 thomas-bionic pppd[2613]: Plugin 
/usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
  Apr 22 10:29:21 thomas-bionic NetworkManager[507]: Plugin 
/usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
  Apr 22 10:29:21 thomas-bionic pppd[2613]: pppd 2.4.7 started by root, uid 0
  Apr 22 10:29:21 thomas-bionic NetworkManager[507]:   [1524414561.3358] 
manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/5)
  Apr 22 10:29:21 thomas-bionic pppd[2613]: Using interface ppp0
  Apr 22 10:29:21 thomas-bionic NetworkManager[507]: Using interface ppp0
  Apr 22 10:29:21 thomas-bionic pppd[2613]: Connect: ppp0 <--> /dev/pts/0
  Apr 22 10:29:21 thomas-bionic NetworkManager[507]: Connect: ppp0 <--> 
/dev/pts/0
  Apr 22 10:29:21 thomas-bionic pptp[2620]: nm-pptp-service-2601 
log[main:pptp.c:353]: The synchronous pptp option is NOT activated
  Apr 22 10:29:21 thomas-bionic systemd-udevd[2617]: link_config: 
autonegotiation is unset or enabled, the speed and duplex are not writable.
  Apr 22 10:29:21 thomas-bionic NetworkManager[507]:   [1524414561.3610] 
devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
  Apr 22 10:29:21 thomas-bionic NetworkManager[507]:   [1524414561.3613] 
device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown 
configuration found.
  Apr 22 10:29:21 thomas-bionic pptp[2632]: nm-pptp-service-2601 
log[ctrlp_rep:pptp_ctrl.c:259]: Sent control packet type is 1 
'Start-Control-Connection-Request'
  Apr 22 10:29:21 thomas-bionic pptp[2632]: nm-pptp-service-2601 
log[ctrlp_disp:pptp_ctrl.c:781]: Received Sta

[Desktop-packages] [Bug 1797834] [NEW] Ubuntu dash-to-dock "Show on" bug

2018-10-14 Thread Yating

Public bug reported:

Dear developers,

How are you?

I've noticed a bug/typo on the Settings->Dock->`Show on` settings on
dual monitors: the Ubuntu Dock show on to the opposite of the display.
In my case: I set "HP 23es" as my primary monitor while built-in screen
as my secondary monitor, I then switch the "Show on" from "HP 23es" to
"Built-in" display, then back again to "HP 23es", now the Ubuntu dock
show on the "Built-in" monitor instead of the "HP 23es". And if I switch
to "Built-in" display, the dock display on "HP 23es", which is doing
opposite operation. What I guess is that the Ubuntu dock shows the typo
information since I've tried dash-to-dock extension without any
problems.

** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Ubuntu dash-to-dock "Show on" bug

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  Dear developers,

  How are you?

  I've noticed a bug/typo on the Settings->Dock->`Show on` settings on
  dual monitors: the Ubuntu Dock show on to the opposite of the display.
  In my case: I set "HP 23es" as my primary monitor while built-in
  screen as my secondary monitor, I then switch the "Show on" from "HP
  23es" to "Built-in" display, then back again to "HP 23es", now the
  Ubuntu dock show on the "Built-in" monitor instead of the "HP 23es".
  And if I switch to "Built-in" display, the dock display on "HP 23es",
  which is doing opposite operation. What I guess is that the Ubuntu
  dock shows the typo information since I've tried dash-to-dock
  extension without any problems.

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

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

[Desktop-packages] [Bug 1797835] [NEW] Shutdown or logout button have to click twice

2018-10-14 Thread Yating

Public bug reported:

Dear developers,

How are you? I've been fresh install the Ubuntu 18.04.1 LTS and facing a
new bug randomly, that is the shutdown and logout button sometimes have
to be clicked twice to take effects.

Best,
syscl

** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Shutdown or logout button have to click twice

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  Dear developers,

  How are you? I've been fresh install the Ubuntu 18.04.1 LTS and facing
  a new bug randomly, that is the shutdown and logout button sometimes
  have to be clicked twice to take effects.

  Best,
  syscl

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

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

[Desktop-packages] [Bug 1303864] Re: Reliance NetConnect is Not Detected

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

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

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

Title:
  Reliance NetConnect is Not Detected

Status in firefox package in Ubuntu:
  Expired

Bug description:
  my broadband modem is not detected. i need to restart my system 4
  times only then it gets detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: firefox 25.0.1+build1-0ubuntu0.12.10.1
  ProcVersionSignature: Ubuntu 3.5.0-44.67-generic 3.5.7.25
  Uname: Linux 3.5.0-44-generic i686
  AddonCompatCheckDisabled: False
  ApportVersion: 2.6.1-0ubuntu13
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gaut   1919 F pulseaudio
  BuildID: 20131115110227
  Channel: Unavailable
  Date: Mon Apr  7 20:14:01 2014
  ExecutablePath: /usr/lib/firefox/firefox
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-04-04 (367 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  IpRoute:
   default via 220.224.141.145 dev ppp0  proto static 
   169.254.0.0/16 dev ppp0  scope link  metric 1000 
   220.224.141.145 dev ppp0  proto kernel  scope link  src 115.242.237.2
  MarkForUpload: True
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=25.0.1/20131115110227 (In use)
  RelatedPackageVersions:
   google-talkplugin 4.9.1.0-1
   rhythmbox-mozilla 2.97-1ubuntu6.1
   totem-mozilla 3.4.3-0ubuntu5
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to quantal on 2013-11-25 (132 days ago)
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 050VP6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A10
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd10/20/2010:svnDellInc.:pnInspironN4010:pvrA10:rvnDellInc.:rn050VP6:rvrA10:cvnDellInc.:ct8:cvrA10:
  dmi.product.name: Inspiron N4010
  dmi.product.version: A10
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 812349] Re: on some pages video flash dont work correctly.The video appear with white zones in motion over the screen.

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

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

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

Title:
  on some pages video flash dont work correctly.The video appear with
  white zones in motion over the screen.

Status in firefox package in Ubuntu:
  Expired

Bug description:
  on some pages video flash don't work correctly.The video appear with
  white zones in motion over the screen.this bug happen for example
  on:www.nasa.gov  www.jibjab.comwww.ivid.it and many
  more.Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: firefox 5.0+build1+nobinonly-0ubuntu0.11.04.2
  ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
  Uname: Linux 2.6.38-10-generic x86_64
  NonfreeKernelModules: nvidia wl
  Architecture: amd64
  Date: Mon Jul 18 17:02:39 2011
  FirefoxPackages:
   firefox 5.0+build1+nobinonly-0ubuntu0.11.04.2
   flashplugin-installer 10.3.181.34ubuntu0.11.04.1
   adobe-flashplugin N/A
   icedtea-plugin 1.1~20110420-0ubuntu1.1
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  ProcEnviron:
   LANGUAGE=it_IT:en
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox
  UpgradeStatus: Upgraded to natty on 2011-07-15 (3 days ago)

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

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

[Desktop-packages] [Bug 839018] Re: restoring session only shows blank pages in every tab

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

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

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

Title:
  restoring session only shows blank pages in every tab

Status in firefox package in Ubuntu:
  Expired

Bug description:
  When you open Firefox after a crash, or after shutting down the system
  without closing firefox, it usually restores the last session.

  At random times, when it restores the last session, it does open as
  many tabs as were open in the last session and does show the correct
  addresses in the address bar, BUT all tabs only shows blank pages with
  (Untitled) as the title. You have to manually click each tab, click on
  the address bar and hit Enter.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: firefox 3.6.20+build1+nobinonly-0ubuntu0.10.10.1
  ProcVersionSignature: Ubuntu 2.6.35-30.56-generic 2.6.35.13
  Uname: Linux 2.6.35-30-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Thu Sep  1 21:07:10 2011
  FirefoxPackages:
   firefox 3.6.20+build1+nobinonly-0ubuntu0.10.10.1
   firefox-gnome-support 3.6.20+build1+nobinonly-0ubuntu0.10.10.1
   firefox-branding 3.6.20+build1+nobinonly-0ubuntu0.10.10.1
   abroswer N/A
   abrowser-branding N/A
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: firefox

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

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

[Desktop-packages] [Bug 912478] Re: url bar autocomplete outine appears for a split second before disappearing

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

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

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

Title:
  url bar autocomplete outine appears for a split second before
  disappearing

Status in firefox package in Ubuntu:
  Expired

Bug description:
  This was fixed several releases ago, and is reoccurring  in the 12.04 alpha 
release as of two or three days ago.
  When I start typing in the awesomebar, the outline of the autocomplete 
dropdown menu will appear for a split second before disappearing.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 10.0~b2+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7
  Uname: Linux 3.2.0-7-generic x86_64
  NonfreeKernelModules: fglrx
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.90-0ubuntu1
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ian1786 F pulseaudio
   /dev/snd/controlC0:  ian1786 F pulseaudio
  BuildID: 20120102174738
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xd452 irq 56'
 Mixer name : 'IDT 92HD81B1X5'
 Components : 'HDA:111d7605,103c3588,00100105 
HDA:11c11040,103c3066,00100200'
 Controls  : 15
 Simple ctrls  : 10
  Card1.Amixer.info:
   Card hw:1 'Generic'/'HD-Audio Generic at 0xd442 irq 57'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 5
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Channel: beta
  Date: Thu Jan  5 14:17:51 2012
  EcryptfsInUse: Yes
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   ShareMeNot - ID=shareme...@franziroesner.com, Version=1.0.0.6, 
minVersion=3.6, maxVersion=9.*, Location=app-profile, Type=extension, Active=Yes
   NoScript - ID={73a6fe31-595d-460b-a920-fcc0f8843232}, Version=2.2.5rc4, 
minVersion=1.9a2, maxVersion=1.9.6, Location=app-profile, Type=extension, 
Active=Yes
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
  IpRoute:
   default via 199.17.130.1 dev eth0  proto static 
   10.19.0.0/22 dev wlan0  proto kernel  scope link  src 10.19.1.234  metric 2 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   199.17.128.0/22 dev eth0  proto kernel  scope link  src 199.17.128.56  
metric 1
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=10.0/20120102174738 (Running)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: Upgraded to precise on 2012-01-03 (2 days ago)
  dmi.bios.date: 04/27/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.03
  dmi.board.name: 161C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.40
  dmi.chassis.asset.tag: CNU1240FN2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.03:bd04/27/2011:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.40:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8460p
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 737706] Re: Firefox plugin overwrites root window

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

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

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

Title:
  Firefox plugin overwrites root window

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Binary package hint: firefox

  ubuntu 10.10, i386
  xorg: 7.5+6ubuntu3
  nvidia driver: 260.19.06-0ubuntu1
  firefox 3.6.15+build1+nobinonly-0ubuntu0.10.10.1
  metacity 2.30.2-0ubuntu1

  After running flash content in the browser, the last frame shown
  remains in some part of the graphics buffer, and bleeds through into
  black pixels of any window moved on top of it. (ie, a semi-black
  background image shows the last flash frame only in the black area,
  and a terminal moved over the area shows the last frame everywhere
  except the white of the characters).

  I had originally assumed this was getting drawn onto the X root
  window, but the effect is not stored in screencaptures with either
  gimp or xvidcap. Killing firefox/plugin-container does not make the
  effect go away. Restarting metacity does remove it.

  I don't know if this is a bug in the flash plugin or plugin container
  (presumably related to hardware acceleration/DRI), or somewhere else
  in the X stack. Does anyone have suggestions for more useful
  diagnostics?

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

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

[Desktop-packages] [Bug 1259284] Re: Firefox stripped of its title when de-iconified via "firefox file://mumble"

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

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

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

Title:
  Firefox stripped of its title when de-iconified via "firefox
  file://mumble"

Status in firefox package in Ubuntu:
  Expired

Bug description:
  If one iconifies firefox up to and including 25.0.1 under 12.04, and
  then issues a "firefix file://mumble" command from a terminal window,
  the window's titlebar will not be displayed.  Re-iconifying and re-
  displaying the window via the window manager will cause the title bar
  to be restored.  This is via the classic gnome interface.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 25.0.1+build1-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.5.0-30.51~precise1-generic 3.5.7.9
  Uname: Linux 3.5.0-30-generic x86_64
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raj2740 F pulseaudio
  BuildID: 20131115110311
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf700 irq 74'
 Mixer name : 'Realtek ALC262'
 Components : 'HDA:10ec0262,103c1309,00100202'
 Controls  : 33
 Simple ctrls  : 17
  Channel: Unavailable
  Date: Mon Dec  9 11:03:06 2013
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MarkForUpload: True
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=25.0.1/20131115110311 (In use)
  RelatedPackageVersions:
   adobe-flashplugin 11.2.202.327-0precise1
   icedtea-6-plugin  1.2.3-0ubuntu0.12.04.3
   rhythmbox-mozilla 2.96-0ubuntu4.3
   totem-mozilla 3.0.1-0ubuntu21.1
   gecko-mediaplayer 1.0.4-2ubuntu1
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to precise on 2013-01-31 (312 days ago)
  WifiSyslog:
   
  dmi.bios.date: 09/13/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G3 v03.12
  dmi.board.asset.tag: 2UA05017VW
  dmi.board.name: 0B4Ch
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: D
  dmi.chassis.asset.tag: 2UA05017VW
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G3v03.12:bd09/13/2010:svnHewlett-Packard:pnHPZ400Workstation:pvr:rvnHewlett-Packard:rn0B4Ch:rvrD:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Z400 Workstation
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 728330] Re: Problemas con dni electrónico

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

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

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

Title:
  Problemas con dni electrónico

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Google translation:
  Hi, I have a newbie problem
  Followed the instructions to install the electronic identity card reader and 
everything went well. I checked the official website for the certificates dni 
work and verifies me perfectly. Now I try to use it in redtrabaja.es (I passed 
on other pages too) and no way. The message I get is:
  Secure Connection Failed

  An error occurred during a connection to isweb.redtrabaja.es.

  The other end of the SSL connection has had some unspecified issue
  with the certificate it received.

  (Error code: ssl_error_certificate_unknown_alert)
  When I wore the Windoze was the same used in Firefox and Explorer by going 
crazy. Is it a problem of Firefox, the pages or I have not done something right?
  Thank you very much in advance

  Binary package hint: firefox

  Buenas, tengo un problema de novato con
  He seguido las instrucciones para instalar el lector de dni electrónico y ha 
ido todo bien. He comprobado en el portal oficial del dni que los certificados 
funcionan y me los verifica perfectamente. Ahora intento utilizarlo en 
redtrabaja.es (me pasa en otras páginas también) y no hay manera. El mensaje 
que me sale es el siguiente:
  Conexión segura fallida

  Ha ocurrido un error durante una conexión a isweb.redtrabaja.es.

  El otro extremo de la conexión SSL ha tenido algún problema no
  especificado con el certificado que ha recibido.

  (Código de error: ssl_error_certificate_unknown_alert)
  Cuando usaba el maldito Güindous me pasaba lo mismo con el Firefox y 
utilizaba Explorer por no volverme loco. ¿Es un problema del Firefox, de las 
páginas o es que no he hecho algo bien?
  Muchas gracias por adelantado

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: firefox 3.6.14+build3+nobinonly-0ubuntu0.10.10.1
  ProcVersionSignature: Ubuntu 2.6.35-27.48-generic 2.6.35.11
  Uname: Linux 2.6.35-27-generic i686
  Architecture: i386
  Date: Thu Mar  3 10:21:10 2011
  FirefoxPackages:
   firefox 3.6.14+build3+nobinonly-0ubuntu0.10.10.1
   firefox-gnome-support 3.6.14+build3+nobinonly-0ubuntu0.10.10.1
   firefox-branding 3.6.14+build3+nobinonly-0ubuntu0.10.10.1
   abroswer N/A
   abrowser-branding N/A
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  ProcEnviron:
   LANG=es_ES.utf8
   SHELL=/bin/bash
  SourcePackage: firefox

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

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

[Desktop-packages] [Bug 1329870] Re: firefox disappeared, without displaying crash reporting window.

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

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

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

Title:
  firefox disappeared, without displaying crash reporting window.

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Not much to tell...

  I am currently using 28.0, as that is the latest version that I can
  use (29/30 each try to start up, open up most of the windows, and then
  disappear with the report firefox crash window).

  I had been using it for awhile (a couple of hours), been to many tabs,
  switched to another (unused so far today) tab, and firefox just
  vanished.

  Since I used ubuntu-bug to submit this, all the usual system/OS info
  should be already available, but if for some reason it doesn't get
  attached, I will add uname -a, etc. in a comment...

  It seems to me that in the last few (10 or so?) versions of FF, it has
  become somehow more fragile...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 28.0+build2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-29.53~ppa1-generic-tuxonice 3.13.11.2
  Uname: Linux 3.13.0-29-generic-tuxonice i686
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1437 F lxpanel
  BuildID: 20140410211157
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Channel: Unavailable
  CurrentDesktop: LXDE
  Date: Fri Jun 13 13:28:28 2014
  DefaultProfileIncompatibleExtensions:
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  DefaultProfilePrefSources: prefs.js
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-04-26 (48 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.3  metric 9
  MostRecentCrashID: bp-bb1ad564-2d32-4dae-bf50-46e8d2140612
  PciNetwork:
   
  Profile1IncompatibleExtensions:
   Global Menu Bar integration - globalm...@ubuntu.com
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  Profile1PrefSources: prefs.js
  Profiles:
   Profile0 (Default) - LastVersion=28.0/20140410211157
   Profile1 - LastVersion=28.0/20140410211157
  RelatedPackageVersions:
   icedtea-7-plugin 1.5-1ubuntu1
   browser-plugin-gnash 0.8.11~git20130903-3ubuntu1
   gecko-mediaplayer1.0.8-4ubuntu1
  RfKill:
   
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1802
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N68-AM Plus
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1802:bd06/10/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N68-AMPlus:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1103482] Re: about:addons exentsion search fails to find exentsions by name

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

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

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

Title:
  about:addons exentsion search fails to find exentsions by name

Status in firefox package in Ubuntu:
  Expired

Bug description:
  I wanted to install Firebug. about:addons > Search > firebug. This
  shows a bunch of exenstions loosely related to firebug, EXECPT firebug
  itself. I've had the same frustration with a particular named video
  download helper, e.g. "easy youtube video downloader" - not listed.
  Even adding in the author's name as search terms still does not find
  the right extension.

  Surely an exact match on a name should prevail over all the other
  cruft? Or is it just completely broken?

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 18.0.1+build1-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35
  Uname: Linux 3.2.0-36-generic x86_64
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  itmanager   4242 F pulseaudio
  BuildID: 20130117041235
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xfe52 irq 51'
 Mixer name : 'Intel CougarPoint HDMI'
 Components : 'HDA:10ec0892,80862000,00100302 
HDA:80862805,80862805,0010'
 Controls  : 53
 Simple ctrls  : 22
  Channel: Unavailable
  Date: Wed Jan 23 14:15:42 2013
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  IpRoute:
   default via 10.67.5.254 dev eth0  proto static 
   10.67.5.0/24 dev eth0  proto kernel  scope link  src 10.67.5.4  metric 1 
   169.254.0.0/16 dev eth0  scope link  metric 1000
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MarkForUpload: True
  PrefSources:
   prefs.js
   [Profile]/extensions/foxma...@kei.com/defaults/preferences/prefs.js
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=18.0.1/20130117041235 (In use)
  RelatedPackageVersions:
   rhythmbox-mozilla 2.96-0ubuntu4.2
   totem-mozilla 3.0.1-0ubuntu21.1
   gnome-shell   3.4.1-0ubuntu2
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0155.2012.0509.1620
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CF
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10215-207
  dmi.chassis.type: 3
  dmi.chassis.vendor: VeryPC
  dmi.chassis.version: Broadleaf
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0155.2012.0509.1620:bd05/09/2012:svnVeryPC:pnBL5340-D:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-207:cvnVeryPC:ct3:cvrBroadleaf:
  dmi.product.name: BL5340-D
  dmi.sys.vendor: VeryPC

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

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

[Desktop-packages] [Bug 1714787] Re: Launching chocolate-doom or prboom-plus crashes Wayland session

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

** Changed in: prboom-plus (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Launching chocolate-doom or prboom-plus crashes Wayland session

Status in chocolate-doom package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired
Status in prboom-plus package in Ubuntu:
  Expired

Bug description:
  When trying to launch Doom (both chocolate-doom and prboom-plus), the
  Wayland session will crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: mutter 3.25.91+20170902~ce515c5-1ubuntu1
  Uname: Linux 4.13.0-041300rc7-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  3 10:37:38 2017
  InstallationDate: Installed on 2017-09-02 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170829)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-09-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170829)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: mutter 3.25.91+20170902~ce515c5-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Tags:  artful wayland-session
  Uname: Linux 4.12.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1724732] Re: Wayland login options are missing when a radeon card is installed

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

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

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

Title:
  Wayland login options are missing when a radeon card is installed

Status in gdm3 package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired

Bug description:
  Wayland login options are missing when a radeon card is installed. GDM
  only offers Xorg sessions...

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cedar GL [FirePro 2270]
  Subsystem: Hewlett-Packard Company Cedar GL [FirePro 2270]
  Kernel driver in use: radeon
  Kernel modules: radeon

  And I'm not in hybrid mode either. The integrated graphics device is
  not listed by lspci.

  Strangely I can start weston on another VT successfully. Only
  mutter/gdm3 is refusing to show Wayland as an option.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.26.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Thu Oct 19 11:18:11 2017
  InstallationDate: Installed on 2017-05-03 (168 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2017-07-20T13:56:59.913179

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

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

[Desktop-packages] [Bug 1727035] Re: apps start maximized randomly

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

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

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

Title:
  apps start maximized randomly

Status in mutter package in Ubuntu:
  Expired

Bug description:
  Firefox, thunderbird, aisleriot, all start full screen randomly.
  Sometimes they start at the correct size at last close.
  To reproduce: open {aisleriot|firefox|thunderbird} change size to not full 
screen.
  Close {aisleriot|firefox|thunderbird}
  Open {aisleriot|firefox|thunderbird}
  Result: {aisleriot|firefox|thunderbird} is full screen
  Expected result: {aisleriot|firefox|thunderbird} is same size as when closed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: mutter 3.26.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 12:24:58 2017
  InstallationDate: Installed on 2017-05-23 (153 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: Upgraded to artful on 2017-10-22 (2 days ago)

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

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

[Desktop-packages] [Bug 1724732] Re: Wayland login options are missing when a radeon card is installed

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

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

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

Title:
  Wayland login options are missing when a radeon card is installed

Status in gdm3 package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired

Bug description:
  Wayland login options are missing when a radeon card is installed. GDM
  only offers Xorg sessions...

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cedar GL [FirePro 2270]
  Subsystem: Hewlett-Packard Company Cedar GL [FirePro 2270]
  Kernel driver in use: radeon
  Kernel modules: radeon

  And I'm not in hybrid mode either. The integrated graphics device is
  not listed by lspci.

  Strangely I can start weston on another VT successfully. Only
  mutter/gdm3 is refusing to show Wayland as an option.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.26.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Thu Oct 19 11:18:11 2017
  InstallationDate: Installed on 2017-05-03 (168 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2017-07-20T13:56:59.913179

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

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

[Desktop-packages] [Bug 1718393] Re: Keybindings stop working from time to time

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

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

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

Title:
  Keybindings stop working from time to time

Status in mutter package in Ubuntu:
  Expired

Bug description:
  For some reason keybindings (like L) stop working.
  As workaround I need to redefine them in control center, but it will work 
until reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: mutter 3.26.0-1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep 20 13:43:22 2017
  SourcePackage: mutter
  UpgradeStatus: Upgraded to artful on 2017-08-30 (21 days ago)

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

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

[Desktop-packages] [Bug 1716271] Re: Window resize handles outside of window

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

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

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

Title:
  Window resize handles outside of window

Status in mutter package in Ubuntu:
  Expired

Bug description:
  Window resize controls appear only when mouse is outside of window, on
  its shadow. If window is in the corner or edge of the screen - that
  makes impossible to resize window using mouse.

  Ubuntu 17.10 daily with mutter 3.25.91+20170902~ce515c5-1ubuntu1

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

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

[Desktop-packages] [Bug 1714787] Re: Launching chocolate-doom or prboom-plus crashes Wayland session

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

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

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

Title:
  Launching chocolate-doom or prboom-plus crashes Wayland session

Status in chocolate-doom package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired
Status in prboom-plus package in Ubuntu:
  Expired

Bug description:
  When trying to launch Doom (both chocolate-doom and prboom-plus), the
  Wayland session will crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: mutter 3.25.91+20170902~ce515c5-1ubuntu1
  Uname: Linux 4.13.0-041300rc7-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  3 10:37:38 2017
  InstallationDate: Installed on 2017-09-02 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170829)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-09-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170829)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: mutter 3.25.91+20170902~ce515c5-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Tags:  artful wayland-session
  Uname: Linux 4.12.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1723877] Re: bad rendering of ":" character (white rectangular block)

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

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

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

Title:
  bad rendering of ":" character (white rectangular block)

Status in gnome-shell package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired

Bug description:
  When selecting an Ubuntu (wayland or x) session, the ":" character in
  the top panel clock renders as a white rectangular block (see attached
  png screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 16 09:47:34 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2015-11-17 (698 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-03 (12 days ago)

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

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

[Desktop-packages] [Bug 1723877] Re: bad rendering of ":" character (white rectangular block)

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

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  bad rendering of ":" character (white rectangular block)

Status in gnome-shell package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired

Bug description:
  When selecting an Ubuntu (wayland or x) session, the ":" character in
  the top panel clock renders as a white rectangular block (see attached
  png screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 16 09:47:34 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2015-11-17 (698 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-03 (12 days ago)

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

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

[Desktop-packages] [Bug 1714787] Re: Launching chocolate-doom or prboom-plus crashes Wayland session

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

** Changed in: chocolate-doom (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Launching chocolate-doom or prboom-plus crashes Wayland session

Status in chocolate-doom package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired
Status in prboom-plus package in Ubuntu:
  Expired

Bug description:
  When trying to launch Doom (both chocolate-doom and prboom-plus), the
  Wayland session will crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: mutter 3.25.91+20170902~ce515c5-1ubuntu1
  Uname: Linux 4.13.0-041300rc7-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  3 10:37:38 2017
  InstallationDate: Installed on 2017-09-02 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170829)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-09-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170829)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: mutter 3.25.91+20170902~ce515c5-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Tags:  artful wayland-session
  Uname: Linux 4.12.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1714908] Re: Cannot use multiple monitors; xrandr causes segfault at 1a0 ip 00007f54021c9836 sp 00007fff 994f5b00 error 4 in libmutter-1.so.0.0.0[7f54020e5000+13f000]

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

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

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

Title:
  Cannot use multiple monitors; xrandr causes segfault at 1a0 ip
  7f54021c9836 sp 7fff 994f5b00 error 4 in
  libmutter-1.so.0.0.0[7f54020e5000+13f000]

Status in mutter package in Ubuntu:
  Expired

Bug description:
  Attempting to use multiple monitors from the graphical interface
  results in nothing happening:

  (gnome-control-center:8910): display-cc-panel-WARNING **: Error
  applying configuration:
  GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method
  ApplyConfiguration is not implemented on interface
  org.gnome.Mutter.DisplayConfig

  Attempting to set up the same from xrandr causes segmentation faults
  in libmutter:

  $ sudo dmesg --console-on
  $ xrandr --output eDP-1 --off  --output DP-1-2 --mode 1920x1080 --rotate left 
--pos 2160x0 --output DP-1-1 --pos 0x0 --mode 1920x1080 --rotate left --output 
DP-1-3 --pos 1080x0 --mode 1920x1080 --rotate left --verbose --scale 1x1
  screen 0: 3240x1920 858x508 mm  95.92dpi
  crtc 0:1920x1080  60.00 +1080+0 "DP-1-3"
  crtc 1:1920x1080  60.00 +2160+0 "DP-1-2"
  crtc 2:1920x1080  60.00 +0+0 "DP-1-1"
  [Sep 4 11:07] gnome-shell[3603]: segfault at 8 ip 7f79e651bda0 sp 
7ffd48c3d1b8 error 4 in libmutter-1.so.0.0.0[7f79e64c2000+13f000]

  It should be noted that all monitors are working as expected during
  boot (e.g. while typing my HDD unlock password)

  Regrettably the segfault information changes every time and apport
  doesn't seem able to capture reports for it.

  xfce sessions from lightdm start regularly and can use external
  monitors regularly.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libmutter-1-0 3.25.91+20170902~ce515c5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  4 11:02:06 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-08-14 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170814)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1727868] Re: New windows are unfocused and go below current window

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

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

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

Title:
  New windows are unfocused and go below current window

Status in mutter package in Ubuntu:
  Expired

Bug description:
  When new applications are launched from the terminal in 17.10, the
  windows are unfocused and appear below the current window. This is the
  opposite of the behavior in (at least) 16.10 and 17.04, where new
  windows would appear focused and on top. This appears to be a feature
  in Gnome 3, which is new in 17.10. Ubuntu users upgrading from earlier
  versions should not be assumed to be familiar Gnome 3, nor with how to
  tweak Gnome settings. The Release Notes should indicate this change
  and document how to turn it off. Also, and more importantly, there
  needs to actually be a way to restore the previous behavior. If there
  is, I've been unable to find it in Settings, gnome-tweak-tool, or
  dconf-editor.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: mutter 3.26.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 17:43:57 2017
  InstallationDate: Installed on 2016-12-27 (303 days ago)
  InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: mutter
  UpgradeStatus: Upgraded to artful on 2017-10-20 (6 days ago)

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

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

[Desktop-packages] [Bug 1722501] Re: Tiling gedit causes the gedit window to get stuck.

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

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

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

Title:
  Tiling gedit causes the gedit window to get stuck.

Status in mutter package in Ubuntu:
  Expired

Bug description:
  Using Ubuntu Budgie Beta2, fully updated, dragging a gedit window to
  be tiled causes the window to be stuck where it is dropped.

  Related: https://github.com/budgie-desktop/budgie-desktop/issues/1185
  and https://github.com/budgie-desktop/budgie-desktop/issues/1189

  After the fix, mentioned here:
  https://bugzilla.gnome.org/show_bug.cgi?id=788666, most windows can be
  tiled now, except for gedit windows. Those still make the desktop
  hang.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: mutter (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue Oct 10 11:35:24 2017
  InstallationDate: Installed on 2017-08-29 (41 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha amd64 
(20170829)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1722897] Re: Ubuntu Wayland seems to be allocating 2-3 framebuffer sized surfaces (more than Xorg)

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

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

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

Title:
  Ubuntu Wayland seems to be allocating 2-3 framebuffer sized surfaces
  (more than Xorg)

Status in mutter package in Ubuntu:
  Expired

Bug description:
  I'm fixing an issue with drm/vmwgfx on 17.10 Wayland desktop, and I'd
  like to chat with someone about how Ubuntu Wayland works.

  Specifically, when a VM is configured to have 4MB of GPU memory, we
  have trouble setting modes above 1024x768@32bpp even though there's
  technically enough GPU memory to handle the framebuffer.

  This does not happen with Ubuntu 17.10 Xorg desktop.

  From what I can see there are two things:

  1.  Ubuntu Wayland seems to be allocated 2-3 framebuffer sized
  surfaces.  Is it doing triple-buffering?

  2.  For certain modes, e.g. 1360x768 and 800x600, the pitch coming
  into .create_fb is greater than mode->width * bytes-per-pixel.  For
  instance, for 800x600@32bpp, the requested pitch is 3328 instead of
  3200.

  These two behaviors is different from what we assumed for low memory
  configurations, and so is causing some issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu2
  Uname: Linux 4.13.0-syeh-v4.13 x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 12:50:08 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2017-10-03 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-username-v4.13 
root=UUID=e5e24738-af43-4671-9595-cccd3f4c77b8 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet modprobe.blacklist=vmwgfx 
kgdboc=ttyS1,115200
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/19/2017
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Oct 11 12:38:36 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVMware VMware Virtual USB Mouse MOUSE, id 7
   inputVirtualPS/2 VMware VMMouse MOUSE, id 8
   inputVirtualPS/2 VMware VMMouse MOUSE, id 9
   inputAT Translated Set 2 keyboard KEYBOARD, id 10
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/fb0: No such file or directory
   vmware(0): Failed to open drm.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.3-1ubuntu7

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

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

[Desktop-packages] [Bug 1797543] Re: Gnome-software - unable to update software - Button Restart & Update, restarts no updates applied

2018-10-14 Thread Robert Ancell

It seems skipping gs_plugin_add_updates in plugins/packagekit/gs-plugin-
packagekit.c seems to fix this.

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

Title:
  Gnome-software - unable to update software  - Button Restart & Update,
  restarts no updates applied

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.10 beta (up to date as of 12-10-2018)
  Ubuntu software 3.30.2

  DESCRIPTION OF BEHAVIOUR
  When updates are available, Ubuntu-Software shows updates are available in 
the "Updates" tab.

  One of the updates available shows "OS Updates"

  The grey coloured heading right above the available updates, has
  "Requires Restart" on the left and a green button "Restart & Update".

  When the green button is clicked,  a popup window appears immediately
  showing "Restart, the system will restart automatically in 60 seconds"
  counting down. The restart can be cancelled or activated.

  When activated (either automatically or manually) the computer
  restarts immediately and no software is being updated.

  After logging in and starting up Ubuntu Software, the Updates tab
  checks and then shows the same updates being available as before.

  ---
  The button on the Updates tab should rather offer to update all available 
software and only offer to restart the computer after the updates are completed.

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

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

[Desktop-packages] [Bug 1797543] Re: Gnome-software - unable to update software - Button Restart & Update, restarts no updates applied

2018-10-14 Thread Robert Ancell

I'm guessing debian/patches/0006-packagekit-Disable-updates-
LP-1775226.patch is no longer working? Investigating why that might be
(I didn't work on that change before).

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

Title:
  Gnome-software - unable to update software  - Button Restart & Update,
  restarts no updates applied

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.10 beta (up to date as of 12-10-2018)
  Ubuntu software 3.30.2

  DESCRIPTION OF BEHAVIOUR
  When updates are available, Ubuntu-Software shows updates are available in 
the "Updates" tab.

  One of the updates available shows "OS Updates"

  The grey coloured heading right above the available updates, has
  "Requires Restart" on the left and a green button "Restart & Update".

  When the green button is clicked,  a popup window appears immediately
  showing "Restart, the system will restart automatically in 60 seconds"
  counting down. The restart can be cancelled or activated.

  When activated (either automatically or manually) the computer
  restarts immediately and no software is being updated.

  After logging in and starting up Ubuntu Software, the Updates tab
  checks and then shows the same updates being available as before.

  ---
  The button on the Updates tab should rather offer to update all available 
software and only offer to restart the computer after the updates are completed.

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

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

[Desktop-packages] [Bug 1730211] Re: Unable to type capital letters using onscreen keyboard

2018-10-14 Thread Shih-Yuan Lee

$ git tag --contains 85284acb000ddc70afcf716b6c198b4b5bf5741e
3.29.92
3.30.0
3.30.1

Cosmic is using 3.30.1-1 so it has contained the commit mentioned in
comment #8.

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

Title:
  Unable to type capital letters using onscreen keyboard

Status in OEM Priority Project:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Unable to type capital letters using onscreen keyboard:

  1. Launch a program where you can type text (gedit for example).
  2. Activate on screen keyboard (by touching the screen, foe example).
  3. Notice all the keys on the on screen keyboard display lowercase letters.

  4. Begin typing.  Lowercase characters are typed into the text area.

  5. Tap on the Shift (up arrow at left side of on screen keyboard) key of the 
on screen keyboard.
  6. Notice all the keys on the on screen keyboard now display capital letters.
  7. Begin typing.
  8. A lowercase character will be typed into the text area.

  This is not expected behavior.
  Instead, a capital letter should have been typed.

  (All the keys on the on screen keyboard revert to lower case. This is
  expected, since the on screen shift key would need to be pressed again
  in order to attempt to type another capital character).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: caribou 0.4.21-2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov  5 10:57:04 2017
  InstallationDate: Installed on 2017-11-03 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.23 amd64 "Custom Artful Aardvark"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: caribou
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1730211/+subscriptions

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

[Desktop-packages] [Bug 1756837] Re: Dock doesn't show badge count, if new notifications arrived when screen locked

2018-10-14 Thread Adolfo Jayme

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Dock doesn't show badge count, if new notifications arrived when
  screen locked

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  Gnome Shell disables extensions on screen lock.
  If, for example, new mail will arrived in Thunderbird during screen locked, 
no badges will be shown on unlock.
  Also, lock/unlock screen while badges displayed will clear them.

  So, in current implementation, badges looks very unreliable to rely on
  them, and looks more a mess than a feature.

  Solution may be adding a user space daemon, which interact with
  applications even when dock extension is disabled, and provide badges
  information for dock.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell-extension-ubuntu-dock 0.9
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 19 12:11:45 2018
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to bionic on 2017-10-24 (145 days ago)

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

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

[Desktop-packages] [Bug 1715214] Re: Use high resolution Thunderbird icon for task switcher

2018-10-14 Thread Adolfo Jayme

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

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

Title:
  Use high resolution Thunderbird icon for task switcher

Status in Mozilla Thunderbird:
  Unknown
Status in thunderbird package in Ubuntu:
  Fix Released

Bug description:
  Right now, Thunderbird in Ubuntu is packaged with a set of low-res
  icons. Because of this, is you use KDE Plasma with the Large Icons
  alt-tab task switcher, the Thunderbird icons look ugly:
  https://i.imgur.com/LdL7wlM.png

  openSUSE packagers patch in larger icons, and so in openSUSE, they
  look sharp and crisp: https://i.imgur.com/Le8ZhWg.png

  I have opened a ticket with Mozilla, but it has been ignored:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1371931

  So until they fix it upstream, we may want to consider adopting the
  openSUSE patch in Ubuntu:
  https://bugzilla.opensuse.org/show_bug.cgi?id=1057115

  This way, KDE Plasma users will get nice Thunderbird icons in their
  Large Icons alt-tab task switchers.

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

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

[Desktop-packages] [Bug 1764803] Re: failed install of nvidia-drivers-390

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-390
(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/1764803

Title:
  failed install of nvidia-drivers-390

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  insulation method using ubuntu-driver, blacklisting nouveau.
  also tried with the ppa added and driver from nvidia.com. All failed which 
hasnt happed before when installing (K)ubuntu 

  Black screen after reboot
  GPU running hot
  Kubuntu 18.04 final beta

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  BootLog: /dev/sda1: clean, 226700/2428272 files, 2097944/9707520 blocks
  Date: Tue Apr 17 17:30:25 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.48, 4.15.0-15-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0504]
   NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Acer Incorporated [ALI] GF108M [GeForce GT 620M/630M/635M/640M 
LE] [1025:0505]
  InstallationDate: Installed on 2018-04-12 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  MachineType: Acer Aspire 5755G
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=7ce01f2b-9fff-47af-a177-4bb10ec8e87f ro acpi_osi=Linux 
acpi_backlight=vendor quiet nomodset splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JV51_HR
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.15
  dmi.modalias: 
dmi:bvnAcer:bvrV1.15:bd10/07/2011:svnAcer:pnAspire5755G:pvrV1.15:rvnAcer:rnJV51_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.15:
  dmi.product.name: Aspire 5755G
  dmi.product.version: V1.15
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1797789] Re: Video Driver not found

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

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

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

Title:
  Video Driver not found

Status in Ubuntu:
  Incomplete

Bug description:
  Video Driver not found

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  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:Unity7:ubuntu
  Date: Sun Oct 14 22:59:52 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd 2nd Generation Core Processor 
Family Integrated Graphics Controller [1458:d000]
  InstallationDate: Installed on 2017-09-02 (406 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=2e2e3858-6ff9-4340-9216-6f95f78eaf2a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-DS2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd09/30/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Apr 19 17:07:03 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputA4TECH USB DeviceMOUSE, id 8
   inputA4TECH USB DeviceMOUSE, id 9
   inputA4TECH USB DeviceKEYBOARD, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2

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

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

[Desktop-packages] [Bug 1588009] Re: "libinput bug: timer offset negative" keeps coming up in syslog

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: gnome-shell (Ubuntu)
   Status: New => Confirmed

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

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

Title:
  "libinput bug: timer offset negative" keeps coming up in syslog

Status in libinput:
  Invalid
Status in Ubuntu GNOME:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in libinput package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I have just recently looked in my syslog and discovered that the
  following message shows up a lot daily so I thought I should report
  it:

  /usr/lib/gdm3/gdm-x-session[1707]: (EE) libinput bug: timer offset
  negative

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libinput10 1.2.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jun  1 18:39:08 2016
  InstallationDate: Installed on 2016-05-15 (17 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: libinput
  UpgradeStatus: Upgraded to xenial on 2016-05-28 (4 days ago)

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

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

[Desktop-packages] [Bug 1797769] Re: LCD backlight brighness reset to maximum after boot / resume / login

** Package changed: gnome-shell (Ubuntu) => gnome-settings-daemon
(Ubuntu)

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

Title:
  LCD backlight brighness reset to maximum after boot / resume / login

Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  The laptop LCD backlight brightness level is not preserved. The screen
  brightness always gets reset to 2-steps below the maximum level after
  login or resume from suspend. This is particularly annoying when
  working on battery, because after each resume, I have to make screen
  darker in order to preserve energy.

  It is possible to control brightness by keyboard buttons and by
  status-bar slider, so brightness control mostly works. The status-bar
  slider behaves a bit erratically when moved, but not sure if it is
  related.

  The problem seems to be not related to kernel version.
  The problem existed in 18.04 as well as 18.10.

  Hardware: Dell Precision 5520. 
  Graphics driver: Intel, using integrated GPU.
  Nvidia card turned off on boot, no proprietary Nvidia drivers loaded.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 14:25:37 2018
  DisplayManager: gdm3
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2017-04-12 (549 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1797759] Re: screen goes blank when mate loads - unable to see the login screen

Your kernel log suggests a problem with the GPU:

[15604.676163] intel ips :00:1f.6: failed to disable graphics turbo
[15609.796033] intel ips :00:1f.6: failed to disable graphics turbo
[15614.915894] intel ips :00:1f.6: failed to disable graphics turbo
[15620.035767] intel ips :00:1f.6: failed to disable graphics turbo

The reason why recovery/safe mode works for you would be because that
uses the 'nomodeset' option.

** Package changed: xorg (Ubuntu) => linux (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/1797759

Title:
  screen goes blank when mate loads - unable to see the login screen

Status in linux package in Ubuntu:
  New

Bug description:
  After a clean install of Ubuntu Mate 18.04.1 LTS 64bit on my laptop HP 
Elitebook 2540p Intel Core i7 CPU 640 @ 2.13GHz x 4 the screen goes blank 
before the login screen appears.
  Kernel Linux 4.15.0-36-generic x86_64.
  It was fine using Ubuntu Mate 16.x.
  I have found by booting to save mode and select boot from HDD everything 
works except the font is a bit large and some screens go off the bottom of the 
screen and I can't view this part of the screen.
  When checking software & updates there are no additional drivers loaded.
  The monitor preferences show monitor is known, resolution is 1280 x 800, 
refresh rates is 0 hz. None of this info can be changed.
  I have run the software update 3-4 times hoping that it would right itself.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Mon Oct 15 00:25:10 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:7008]
  InstallationDate: Installed on 2018-09-01 (43 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Hewlett-Packard HP EliteBook 2540p
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcEnviron:
   LANGUAGE=en_NZ:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--mate--vg-root ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CSU Ver. F.50
  dmi.board.name: 7008
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 38.34
  dmi.chassis.asset.tag: SGH038PG56
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CSUVer.F.50:bd07/08/2014:svnHewlett-Packard:pnHPEliteBook2540p:pvr:rvnHewlett-Packard:rn7008:rvrKBCVersion38.34:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 2540p
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1797588] Re: System lagging

David,

What shell are you using? Is it gnome-shell or Unity? Please take a
photo or screenshot and attach it here if unsure.


** Package changed: xorg (Ubuntu) => 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/1797588

Title:
  System lagging

Status in X.Org X server:
  Unknown
Status in Ubuntu:
  Incomplete

Bug description:
  The system is lagging and not opening programs well. even switching
  between windows is very slow.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Oct 12 08:37:51 2018
  DistUpgraded: 2018-09-28 22:03:01,394 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GT216 [GeForce GT 220] [1043:82f3]
  InstallationDate: Installed on 2018-01-02 (282 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=b73e1c3a-b0eb-4da1-9c26-2fba56feefa2 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-09-29 (13 days ago)
  dmi.bios.date: 06/01/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FC
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-DS3P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFC:bd06/01/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-DS3P:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Fri Sep 28 08:34:42 2018
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output DVI-I-1  
HDMI-1   VGA-1
  xserver.version: 2:1.19.6-1ubuntu4~16.04.1
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1797714] Re: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta

** Summary changed:

- No sound after upgrade to Kubuntu 18.10 beta
+ [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta

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

Title:
  [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I upgraded from Kubuntu 18.04 to 18.10 beta today, and I noticed I don't have 
sounds. The UI only shows a 'Dummy Device'. After doing a 'sudo alsa 
force-reload', KDE shows the audio device.
  When I execute alsamixer in a shell before executing the force-reload, the 
audio card is shown.

  My hardware: (from lspci)
  00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High 
Definition Audio (rev 05)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:12.2-0ubuntu4
  Uname: Linux 4.19.0-041900rc6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  juergen8924 F pulseaudio
   /dev/snd/controlC1:  juergen8924 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Oct 13 21:07:53 2018
  InstallationDate: Installed on 2015-02-16 (1334 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to cosmic on 2018-10-13 (0 days ago)
  dmi.bios.date: 10/06/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0KM426
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A02
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd10/06/2009:svnDellInc.:pnStudio1557:pvrA02:rvnDellInc.:rn0KM426:rvrA02:cvnDellInc.:ct8:cvrA02:
  dmi.product.name: Studio 1557
  dmi.product.version: A02
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1797628] Re: System hangs during boot at "Started configure plugged in printer"

** Package changed: xorg (Ubuntu) => linux (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/1797628

Title:
  System hangs during boot at "Started configure plugged in printer"

Status in linux package in Ubuntu:
  New

Bug description:
  System: Lenovo T430s with HP OfficeJet Pro 8600 attached via usb hub

  Followed general bug reporting instructions (including
  https://wiki.ubuntu.com/Bugs/FindRightPackage). This may be kernel
  related, not xorg.

  What I tried: rebooting
  What I expected: to see the login screen
  What happened: booting hangs

  Rebooted using 'E' option in grub to remove splash and quiet. Saw
  system hang at "Started configure plugged in printer"

  When I unplug the USB hub (to which the printer is connected), I can
  reboot and login fine then reinsert USB hub.

  After this "fix," I can reboot fine without unplugging anything. This
  bug appears to happen right after a system update (running Software
  Updater and there are kernel bits to update).

  This is new behaviour; I had the same system setup running and booting
  fine under 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12
  Uname: Linux 4.18.0-9-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 12 15:48:22 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fb]
  InstallationDate: Installed on 2018-10-02 (10 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  MachineType: LENOVO 2356CU8
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-9-generic 
root=UUID=e307efee-e562-4d24-9632-4a97a84073ee ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/22/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ET91WW (2.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2356CU8
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 529944
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG7ET91WW(2.51):bd01/22/2013:svnLENOVO:pn2356CU8:pvrThinkPadT430s:rvnLENOVO:rn2356CU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430s
  dmi.product.name: 2356CU8
  dmi.product.sku: LENOVO_MT_2356
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1797555] Re: headphone not detected on initialization

You can keep this bug report and instead just run:

  apport-collect 1797555

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

Title:
  headphone not detected on initialization

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  every time i initialize the computer with the headphone connected, there's no 
sound in the headphones. i have to take the headphone off and plug it again, 
then i'm prompted with the ubuntu window asking if it's a headphone, phone or 
mic. after selecting the headphone option the audio works fine. this happens 
every time, not a single exception to this behavior.
  my laptop is a Dell Inspiron 15-3567 with Ubuntu 18.04.

  1) Ubuntu 18.04.1
  2) Pulseaudio 1:11.1-1ubuntu7.1
  3) Expected to initialize the OS with the headphone connected and get the 
headphone recognized right away.
  4) There's no sound in the headphones, and i have to take them off and plug 
it again. Then after responding to the ubuntu audio window the sound goes back 
to working again

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

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

[Desktop-packages] [Bug 1797578] Re: unable to open Ubuntu Software

** Package changed: xorg (Ubuntu) => gnome-software (Ubuntu)

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

Title:
  unable to open Ubuntu Software

Status in gnome-software package in Ubuntu:
  New

Bug description:
  when i try to open Ubuntu Software it flashes on the launcher then the
  icon looks like it didn't open.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  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: Fri Oct 12 16:41:02 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:3616]
  InstallationDate: Installed on 2018-01-21 (264 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO Lenovo H420
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=510425b4-02db-49c7-91bd-587ef9d2671d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DPKT22A
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: LENOVO
  dmi.board.version: 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:bvnLENOVO:bvrDPKT22A:bd11/08/2011:svnLENOVO:pnLenovoH420:pvrLenovo:rvnLENOVO:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Lenovo H420
  dmi.product.version: Lenovo
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Oct 12 15:05:52 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   input  USB Keyboard   KEYBOARD, id 8
   input  USB Keyboard   KEYBOARD, id 9
   inputKYE SYSTEMS CORP. Wired Mouse MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4~16.04.1
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1797820] Re: Xwayland crashed with SIGABRT in glamor_bind_texture → glamor_set_composite_texture → glamor_composite_set_shader_blend → glamor_composite_with_shader → glamor_com

** Summary changed:

- 
/usr/bin/Xwayland:6:glamor_bind_texture:glamor_set_composite_texture:glamor_composite_set_shader_blend:glamor_composite_with_shader:glamor_composite_clipped_region
+ Xwayland crashed with SIGABRT in glamor_bind_texture → 
glamor_set_composite_texture → glamor_composite_set_shader_blend → 
glamor_composite_with_shader → glamor_composite_clipped_region

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

Title:
  Xwayland crashed with SIGABRT in glamor_bind_texture →
  glamor_set_composite_texture → glamor_composite_set_shader_blend →
  glamor_composite_with_shader → glamor_composite_clipped_region

Status in xorg-server package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xorg-server.  This problem was most recently seen with package version 
2:1.19.6-1ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/f8ea9bb558676edbe2acec52b0f386ab1321fdaf 
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/xorg-server/+bug/1797820/+subscriptions

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

[Desktop-packages] [Bug 1797002] Re: Bluetooth audio skips while the settings dialog is open

** Summary changed:

- all my bluetooth headsets skips terribly after todays update
+ Bluetooth audio skips while the settings dialog is open

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

** No longer affects: linux (Ubuntu)

** Changed in: bluez (Ubuntu)
   Importance: Undecided => Low

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

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Low

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

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => Low

** Tags added: a2dp a2dp-skip

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

Title:
  Bluetooth audio skips while the settings dialog is open

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

Bug description:
  all my bluetooth headsets skips terribly after today's system update.
  it is heavy noticeable even on audio setting test form.
  it work just fine today before i applied updates.

  even reinstall ubuntu from scratch - didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  9 18:40:44 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-10-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.66
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1968
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 93.52
  dmi.chassis.asset.tag: 5CG32907G7
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY 17 Notebook PC
  dmi.product.version: 088510305B0610100
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 68:17:29:62:BE:6A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:16831 acl:64 sco:0 events:1798 errors:0
TX bytes:688571 acl:2399 sco:0 commands:125 errors:0

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

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

[Desktop-packages] [Bug 1797198] Re: [nvidia] After login the screen goes black

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

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: New => Fix Released

** Changed in: xorg-server (Ubuntu)
   Status: New => Fix Released

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

Title:
  [nvidia] After login the screen goes black

Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  When I boot Cosmic, grub is working OK and login screen is presented OK, but 
after login the screen goes black.
  When I boot in Recovery Mode" and "Resume" all is working OK and Nvidia 
driver 390 is used.
  These bugs my be related
  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1770238
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1748656
  https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543192

  See attachment for syslog info.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 10 20:12:32 2018
  InstallationDate: Installed on 2018-10-10 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181010.1)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1797820] [NEW] Xwayland crashed with SIGABRT in glamor_bind_texture → glamor_set_composite_texture → glamor_composite_set_shader_blend → glamor_composite_with_shader → glamor_c

2018-10-14 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xorg-server.  This problem was most recently seen with package version 
2:1.19.6-1ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/f8ea9bb558676edbe2acec52b0f386ab1321fdaf 
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/.

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


** Tags: artful bionic

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

Title:
  Xwayland crashed with SIGABRT in glamor_bind_texture →
  glamor_set_composite_texture → glamor_composite_set_shader_blend →
  glamor_composite_with_shader → glamor_composite_clipped_region

Status in xorg-server package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
xorg-server.  This problem was most recently seen with package version 
2:1.19.6-1ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/f8ea9bb558676edbe2acec52b0f386ab1321fdaf 
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/xorg-server/+bug/1797820/+subscriptions

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

[Desktop-packages] [Bug 1773959] Re: High CPU usage by gnome-shell when only running gnome-terminal

Gustuv:

Please open a new bug for the issue you describe, by running:

  ubuntu-bug gnome-shell

If gnome-shell is idling with that much CPU usage then it's usually an
extension to blame.

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

Title:
  High CPU usage by gnome-shell when only running gnome-terminal

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Even when doing nothing but displaying a terminal screen with top
  running gnome-shell uses 10% of a CPU. That seems excessive. I
  disabled all extensions to try and make the test fair. Enabling the
  system monitor extension increases the load to 13-14%. It seems that
  the gnome-shell screen painting is highly CPU consuming even if screen
  updates are infrequent (1 a second for all these cases).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 29 11:38:05 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-10-27 (578 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-05-19 (9 days ago)

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

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

[Desktop-packages] [Bug 1767654] Re: Cursor gets stuck on left side of the screen

OK. Can you please provide a video or screencast of the problem?

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

Title:
  Cursor gets stuck on left side of the screen

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  When moving the cursor to the left side of the screen, it stops close
  to the edge. The cursor still moves over in the area but invisible
  until I move it out of the area. When it doesn't do this, glitching
  occurs on the screen where the cursor is until I log out. And on
  screen cast it shows the cursor going to the side of the screen and
  moving.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 09:49:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060]
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic 
root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 
initrd=boot\initrd.img-4.15.0-20-generic
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-408
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled

It's bugging me too. Unfortunately I don't know how long upstream will
take to accept the fix.

I have discussed getting it into Ubuntu sooner than upstream but the
Ubuntu developers with the power to do that seem to be too busy right
now getting 18.10 released.

Since this is a bug however, there is no policy preventing us from
getting the fix into 18.10 and 18.04 after this release.

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

Title:
  Top bar and shell dialogs are not displayed properly when zoom is
  enabled

Status in Mutter:
  In Progress
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Bionic:
  In Progress

Bug description:
  When zoom is enabled, the top bar and some shell dialogs (wireless
  network selection, shutdown dialog, etc.) are not displayed properly.
  (See the attached screenshots.)

  Steps to reproduce the issue:
  1. Enable Zoom in Setting > Universal Access
  2. (Optional) Set zoom factor to around 3 (or higher)
  3. Look at the top bar. You will notice that all texts and icons are now 
gone. If you move your cursor to the right of the top bar, and then click on 
the status menu, you will see that only a portion of the menu is shown.
  4. For the shell dialogs, go to the Settings app. In the Wifi section, choose 
one of the secured network available. You will see that the password dialog is 
not displayed in its entirety.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 12:54:24 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-size' b'96'
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207)

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  gnome-shell filling up syslog with thousands of entries (stack traces
  ending in osdWindow.js:206/207)

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I'm seeing a several gigs (more than 70GB) a day of the following
  entries on syslog:

  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b   
resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I   
self-hosted:915 (0x7f31d4df12b8 @ 367)
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for 
context 0x557ebb0a3320 ==
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I   
resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258)
  May 21 23:54:55 fc553042 gnome-shell[1469]: Object St.Icon (0x557eca1b2e90), 
has been already finalized. Impossible to set any property to it.
  May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71)

  gnome-shell:
    Installed: 3.28.1-0ubuntu2
    Candidate: 3.28.1-0ubuntu2
    Version table:
   *** 3.28.1-0ubuntu2 500
  500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic

  There's similar bug that should be related to this one 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747566 but that fix 
didn't work for me.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  DisplayManager: gdm3

[Desktop-packages] [Bug 1745888] Re: Two instances of a program launch whenever you touch a favorites icon

** Tags added: somerville

** Tags removed: somerville
** Tags added: bionic

** Tags removed: artful

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

Title:
  Two instances of a program launch whenever you touch a favorites icon

Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Using a touch screen, if you tap on a favorites icon on the ubuntu
  dock, two (or more) instances of an application launch.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-ubuntu-dock 0.7.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jan 28 19:47:17 2018
  InstallationDate: Installed on 2018-01-28 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2018.01.26 amd64 "Custom Artful Aardvark"
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1745888/+subscriptions

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

[Desktop-packages] [Bug 1730211] Re: Unable to type capital letters using onscreen keyboard

Per last comment of gnome-shell issue #135, the fix is merged at
https://gitlab.gnome.org/GNOME/mutter/merge_requests/146

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

** Changed in: oem-priority
   Status: New => Confirmed

** Changed in: oem-priority
   Importance: Undecided => High

** Tags added: 2in1

** Tags added: somerville

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

Title:
  Unable to type capital letters using onscreen keyboard

Status in OEM Priority Project:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Unable to type capital letters using onscreen keyboard:

  1. Launch a program where you can type text (gedit for example).
  2. Activate on screen keyboard (by touching the screen, foe example).
  3. Notice all the keys on the on screen keyboard display lowercase letters.

  4. Begin typing.  Lowercase characters are typed into the text area.

  5. Tap on the Shift (up arrow at left side of on screen keyboard) key of the 
on screen keyboard.
  6. Notice all the keys on the on screen keyboard now display capital letters.
  7. Begin typing.
  8. A lowercase character will be typed into the text area.

  This is not expected behavior.
  Instead, a capital letter should have been typed.

  (All the keys on the on screen keyboard revert to lower case. This is
  expected, since the on screen shift key would need to be pressed again
  in order to attempt to type another capital character).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: caribou 0.4.21-2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov  5 10:57:04 2017
  InstallationDate: Installed on 2017-11-03 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.23 amd64 "Custom Artful Aardvark"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: caribou
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1730211/+subscriptions

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

[Desktop-packages] [Bug 1783954] Re: [NVIDIA] GPU lockup (screen freeze) after resume from hibernation / suspend

As this bug was from a different machine, please open a new bug for the
machine on which you still experience a problem:

  ubuntu-bug xorg-server

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

Title:
  [NVIDIA] GPU lockup (screen freeze) after resume from hibernation /
  suspend

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
   This bug is reported against xorg as per
  . It is also
  reported to NVIDIA under
  .

  I have been experiencing GPU lockups after resuming from hibernation
  on KUbuntu 18.04.

  When this happens, the display freezes except for the mouse cursor. It
  is possible to ssh into the computer but killing X does not update the
  display either.

  These lockups seem to happen at a random time after hibernation. Sometimes 
the computer works correctly for hours after resuming, sometimes the lockup 
happen a few seconds after resuming. Actions that are prone to trigger the 
lockup are :
   - hovering over some task in KDE/Plasma panel and causing the miniature of 
the application window to be displayed (when a lockup happens, it is often when 
I do this, but doing this does not systematically incur a lockup) ;
   - with Spectacle (screenshot utility), start selecting a rectangular region 
(this has systematically caused a lockup when tried after resuming from 
hibernation/suspend).

  Following  I tried
  with the latest graphics drivers from the graphics-drivers PPA, the
  latest version of Xorg in the xorg-edgers PPA and the latest available
  kernel (4.17.0-996-generic).

  Attached are some logs, including a partial log produced by 
nvidia-bug-report. Indeed, the script could not complete. Inspection of the 
running processes with a second ssh connection while the script was hanging up 
shows that the blocking point is [code]cat 
/proc/driver/nvidia/./gpus/:01:00.0/information[/code]. Indeed, trying to 
manually read that file in the ssh console also caused it to hang. Of course 
doing this in normal operation works and gives
  [code]Model:   Quadro K620
  IRQ: 127
  GPU UUID:GPU-ea026ffc-2c0d-1301-c365-b1cceeb45601
  Video BIOS:  82.07.7a.00.1a
  Bus Type:PCIe
  DMA Size:40 bits
  DMA Mask:0xff
  Bus Location::01:00.0
  Device Minor:0[/code]

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

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

[Desktop-packages] [Bug 1797817] [NEW] ibus fail to use any input method except chewing for tradtional chinese

2018-10-14 Thread Samson Yeung

Public bug reported:

ibus in Ubuntu Cosmic Cuttlefish (development branch)

All chinese input method for traditional chinese cannot be used except 
ibus-chewing.
Input methods with ibus-table e,g, ibus-table-scj6 ibus-table-cangjie and 
ibus-cangjie are installed. These input methods can be seen in ibus-setup  and  
chosen to be used. But they do not shown up in the top panel drop down menu. 
Neither they can be initiated by short cut key which is set as super-space. 
ibus seems ignore all other input method except Chewing.

Since fcitx is also very buggy (for which i do not report here), there
is no better way to input chinese. Same problem may be true for all
asian language.

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

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

Title:
  ibus fail to use any input method except chewing for tradtional
  chinese

Status in ibus package in Ubuntu:
  New

Bug description:
  ibus in Ubuntu Cosmic Cuttlefish (development branch)

  All chinese input method for traditional chinese cannot be used except 
ibus-chewing.
  Input methods with ibus-table e,g, ibus-table-scj6 ibus-table-cangjie and 
ibus-cangjie are installed. These input methods can be seen in ibus-setup  and  
chosen to be used. But they do not shown up in the top panel drop down menu. 
Neither they can be initiated by short cut key which is set as super-space. 
ibus seems ignore all other input method except Chewing.

  Since fcitx is also very buggy (for which i do not report here), there
  is no better way to input chinese. Same problem may be true for all
  asian language.

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

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

[Desktop-packages] [Bug 1786951] Re: Update to 60.0

2018-10-14 Thread Adolfo Jayme

Uploaded without bug number in changelog, so there was no automatic
notification:

thunderbird (1:60.2.1+build1-0ubuntu1) cosmic; urgency=medium

  * New upstream stable release (60.2.1build1)

  [ Chris Coulson ]
  * Stop installing the NPAPI headers and make thunderbird-dev a transitional
package
- update debian/build/rules.mk
- update debian/control{,.in}
- remove debian/thunderbird-dev.install.in
- remove debian/thunderbird-dev.links.in
  * Update packaging to work with the reversed repository layout (comm in
mozilla)
- update debian/create-tarball.py
- update debian/build/rules.mk
- update debian/config/branch.mk
- update debian/config/mozconfig.in
- update debian/config/tarball.conf
- update debian/rules
  * Build using mach
- update debian/build/rules.mk
  * Don't clean Cargo.toml.orig files which are actually required
- update debian/build/rules.mk
  * Avoid direct dependency on libgtk2.0-0
- update debian/build/rules.mk
  * Drop the ancient and unused version of compare-locales from the
tarball
- update debian/build/create-tarball.py
- update debian/build/rules.mk
  * Update make-langpack-xpis target
- debian/build/rules.mk
  * Update build to work with language packs based on web extensions
- debian/build/xpi-id.py
  * Refresh shipped locales
- update debian/config/locales.all
- update debian/config/locales.shipped
- update debian/control{,.in}
  * Drop build-dependency on gconf
- update debian/config/mozconfig.in
- update debian/control{,.in}
  * Drop obsolete quilt and libgnomeui build-dependencies
- update debian/control{,.in}
  * Hopefully fix LP: #1711337 by building the armhf build with
-fno-schedule-insns to work around a compiler bug
  * Drop obsolete --enable-gio build flag
- update debian/config/mozconfig.in
  * Disable webrtc on non-x86 architectures
- update debian/config/mozconfig.in
  * Don't build with --enable-alsa
- update debian/config/mozconfig.in
  * Drop obsolete DISABLE_LIGHTNING_INSTALL export
- update debian/config/mozconfig.in
  * Bump rustc and cargo requirements
- update debian/control{,.in}
  * Build-depend on clang-4.0 / llvm-4.0-dev
- update debian/control{,.in}
  * Depend on libdbusmenu-gtk3-4 instead of the GTK+ 2 version
- update debian/control{,.in}
  * The gdata-provider extension is no longer built, so make
xul-ext-gdata-provider a transitional package now
- update debian/control{,.in}
- update debian/rules
  * Drop patches that are either fixed upstream or no longer needed
- remove debian/patches/dont-install-blessings-from-network.patch
- remove debian/patches/dont-override-general-useragent-locale.patch
- update debian/patches/series
  * mozbuild/shellutil.py: Don't treat '~' character as special
- add debian/patches/dont-treat-tilde-as-special.patch
- update debian/patches/series
  * Compile rust code with "debuginfo=1" on 32-bit hosts to reduce code size
and hopefully prevent the builds from running out of address space
- add debian/patches/reduce-rust-debuginfo-on-32bit-architectures.patch
- update debian/patches/series
  * Don't try to check checksums of windows-only binary files which are
not included in the tarball
- debian/patches/rust-drop-dll-checksums.patch
  * Refresh patches
- update debian/patches/set-prgname-to-remoting-name.patch
- update debian/patches/support-coinstallable-trunk-build.patch
- update debian/patches/unity-menubar.patch
  * Don't unpack the lightning xpi
- update debian/rules
  * Update install
- update debian/thunderbird.install.in
- update debian/thunderbird.links.in
  * Don't set distribution.searchplugins.defaultLocale, as it isn't needed
- update debian/vendor.js
  * Update messagingmenu-extension to 1.4
- adds compatibility for Thunderbird 60
- fixes an alignment issue in the preferences pane
  * Build with --disable-tests. We don't run any anyway, and this should
stop the build from trying to download python packages from the network
- update debian/config/mozconfig.in
  * Fix up the build-flags, ensuring we remove -g and optimization flags from
CFLAGS and CXXFLAGS, allowing the upstream build to choose these. Also
build with --enable-debug-symbols
- update debian/build/config.mk
- update debian/build/rules.mk
- update debian/config/mozconfig.in
  * Compile with reduced debug info on 32-bit hosts to stop the linker
from running out of address space
- update debian/config/mozconfig.in
- update debian/build/rules.mk
  * Set intl.locale.requested to an empty string so that Thunderbird picks
up the system locale
- update debian/vendor.js

  [ Rico Tzschichholz ]
  * Build with rustc and cargo
- update debian/control{,.in}
- update debian/config/mozconfig.in
  * Don't strip .gitignore files from the tarball. If these are stripped
from vendored rus

[Desktop-packages] [Bug 1771041] Re: Remove gconf from Ubuntu

** Description changed:

  gconf is being removed from Debian Testing. We should remove it from
  Ubuntu also.
  
  eclipse is troublesome. At a minimum, we can remove everything but
  eclipse and gconf.
  
- We are waiting on pulseaudio also (fixed in git master).
- 
  libgnome is a blocker so do it first LP: #1771031
  And remove libqt-gconf LP: #1740538 and xiphos LP: #1710318
- 
- thunderbird needs to be fixed (should happen for the 60 release expected
- "soon")

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

Title:
  Remove gconf from Ubuntu

Status in autopilot-legacy package in Ubuntu:
  New
Status in desktopnova package in Ubuntu:
  New
Status in ekiga package in Ubuntu:
  New
Status in evolution-indicator package in Ubuntu:
  New
Status in gconf package in Ubuntu:
  New
Status in gconf-editor package in Ubuntu:
  New
Status in gkdebconf package in Ubuntu:
  New
Status in gnome-mastermind package in Ubuntu:
  New
Status in gnome-phone-manager package in Ubuntu:
  New
Status in gnome-xcf-thumbnailer package in Ubuntu:
  New
Status in gnomint package in Ubuntu:
  New
Status in gtkwave package in Ubuntu:
  New
Status in guake-indicator package in Ubuntu:
  New
Status in gyrus package in Ubuntu:
  New
Status in jack-mixer package in Ubuntu:
  New
Status in jana package in Ubuntu:
  New
Status in morla package in Ubuntu:
  New
Status in mssh package in Ubuntu:
  New
Status in ogmrip package in Ubuntu:
  New
Status in ooo-thumbnailer package in Ubuntu:
  New
Status in planner package in Ubuntu:
  New

Bug description:
  gconf is being removed from Debian Testing. We should remove it from
  Ubuntu also.

  eclipse is troublesome. At a minimum, we can remove everything but
  eclipse and gconf.

  libgnome is a blocker so do it first LP: #1771031
  And remove libqt-gconf LP: #1740538 and xiphos LP: #1710318

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

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

[Desktop-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)

libpam-mount wasn't actually switched to pcre2. I filed a Debian bug to
let its maintainer know.

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

Title:
  demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2
  (10.x)

Status in aide package in Ubuntu:
  Incomplete
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in exim4 package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Triaged
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  Triaged
Status in libpam-mount package in Ubuntu:
  Incomplete
Status in libselinux package in Ubuntu:
  Triaged
Status in nginx package in Ubuntu:
  Incomplete
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php7.2 package in Ubuntu:
  Won't Fix
Status in php7.3 package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Incomplete
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Incomplete
Status in wget package in Ubuntu:
  Incomplete
Status in zsh package in Ubuntu:
  Incomplete

Bug description:
  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh

  --

  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just
  poorly named (according to jbicha).

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

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

[Desktop-packages] [Bug 1767654] Re: Cursor gets stuck on left side of the screen

2018-10-14 Thread will9183

Disabling Gnome Shell extensions does not fix the problem.

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

Title:
  Cursor gets stuck on left side of the screen

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  When moving the cursor to the left side of the screen, it stops close
  to the edge. The cursor still moves over in the area but invisible
  until I move it out of the area. When it doesn't do this, glitching
  occurs on the screen where the cursor is until I log out. And on
  screen cast it shows the cursor going to the side of the screen and
  moving.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 09:49:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060]
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic 
root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 
initrd=boot\initrd.img-4.15.0-20-generic
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-408
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)

https://launchpad.net/debian/+source/libpam-mount/2.16-8

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

Title:
  demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2
  (10.x)

Status in aide package in Ubuntu:
  Incomplete
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in exim4 package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Triaged
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  Triaged
Status in libpam-mount package in Ubuntu:
  Incomplete
Status in libselinux package in Ubuntu:
  Triaged
Status in nginx package in Ubuntu:
  Incomplete
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php7.2 package in Ubuntu:
  Won't Fix
Status in php7.3 package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Incomplete
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Incomplete
Status in wget package in Ubuntu:
  Incomplete
Status in zsh package in Ubuntu:
  Incomplete

Bug description:
  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh

  --

  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just
  poorly named (according to jbicha).

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

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

[Desktop-packages] [Bug 1561943] Re: Stylus coordinates wrong when screen is rotated on Dell Venue 11 Pro 7140

2018-10-14 Thread Steve Roberts

I also have the same issue on Mint 19 on HP Spectre x360

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

Title:
  Stylus coordinates wrong when screen is rotated on Dell Venue 11 Pro
  7140

Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  I am using the pre-release 16.04 Ubuntu Xenial Xerus (development
  branch) with kernel 4.4.0-15-generic on a Dell Venue 11 Pro 7140.
  Touchscreen and Stylus are recognised out of the box:

  xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Synaptics T Pad V 01.31 Touchpadid=9[slave  pointer 
 (2)]
  ⎜   ↳ SYNA7500:00 06CB:780E Pen   id=13   [slave  pointer 
 (2)]
  ⎜   ↳ SYNA7500:00 06CB:780E   id=14   [slave  pointer 
 (2)]

  When I am manually rotating the screen by 90° using the System
  Settings option (automatic screen rotation does not work), the
  touchscreen and touchpad work as expected, however, the stylus is not
  using the correct coordinates and the cursor is not following the
  stylus position. When I move the stylus left/right, the cursor moves
  up/down, and vice versa.

  I had hoped to get a work around by disabling and re-enabling the
  stylus after rotating the screen using

  xinput --disable "SYNA7500:00 06CB:780E Pen"
  xinput --enable "SYNA7500:00 06CB:780E Pen"

  but this didn't solve the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-15-generic 4.4.0-15.31 [modified: 
boot/vmlinuz-4.4.0-15-generic]
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asvin  1800 F pulseaudio
   /dev/snd/controlC1:  asvin  1800 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Mar 25 11:21:35 2016
  HibernationDevice: RESUME=UUID=f716048f-ce0e-4825-b3c4-563fa743242a
  InstallationDate: Installed on 2016-03-23 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  MachineType: Dell Inc. Venue 11 Pro 7140
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed 
root=UUID=a9cb1c53-fcf1-4691-a246-24b90dd908c6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0XMVMH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd10/27/2015:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7140
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1797782] Re: evince immediately seg faults

2018-10-14 Thread Matt Sienko

I tried to attach a file that was too big. Here is a smaller one that
also causes the crash.

On Sunday, October 14, 2018, 3:24:15 PM PDT, Matthew Sienko 
 wrote:  
 
  Christian,I attached a pdf that evince crashes trying to open, although every 
pdf I tried has caused a crash.
Here is the result of ls /var/crash:_usr_bin_evince.1001.crash   
_usr_bin_evince.1001.uploaded
_usr_bin_evince.1001.upload

Thanks,  -Matt

On Sunday, October 14, 2018, 11:15:37 AM PDT, Cristian Aravena Romero 
 wrote:  
 
 Hello,

Could you send a .pdf file to try to reproduce the error?

Best regards,
--
Cristian Aravena Romero (caravena)

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

Title:
  evince immediately seg faults

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  
  Description:    Ubuntu 18.04.1 LTS
  Release:    18.04

  evince:
    Installed: 3.28.2-1
    Candidate: 3.28.2-1
    Version table:
  *** 3.28.2-1 500
          500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
          100 /var/lib/dpkg/status

  Expected Behavior: evince opens and displays PDF document.

  What Happened: When launching evince, it crashes immediately with a
  segmentation fault. This happens every time. I have tried opening
  multiple PDF documents both from the command line and file browser.
  Launching evince from the command line without specifying a file also
  crashes. The PDF documents open fine in xpdf.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.2-1
  ProcVersionSignature: Ubuntu 4.15.0-1021.24-oem 4.15.18
  Uname: Linux 4.15.0-1021-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 08:29:01 2018
  InstallationDate: Installed on 2018-09-23 (20 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
  PATH=(custom, no user)
  XDG_RUNTIME_DIR=
  LANG=en_US.UTF-8
  SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

** Attachment added: "=?UTF-8?b?c2FtcGxlLnBkZg==?="
   
https://bugs.launchpad.net/bugs/1797782/+attachment/5200965/+files/%3D%3FUTF-8%3Fb%3Fc2FtcGxlLnBkZg%3D%3D%3F%3D

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

Title:
  evince immediately seg faults

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  evince:
Installed: 3.28.2-1
Candidate: 3.28.2-1
Version table:
   *** 3.28.2-1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Expected Behavior: evince opens and displays PDF document.

  What Happened: When launching evince, it crashes immediately with a
  segmentation fault. This happens every time. I have tried opening
  multiple PDF documents both from the command line and file browser.
  Launching evince from the command line without specifying a file also
  crashes. The PDF documents open fine in xpdf.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.2-1
  ProcVersionSignature: Ubuntu 4.15.0-1021.24-oem 4.15.18
  Uname: Linux 4.15.0-1021-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 08:29:01 2018
  InstallationDate: Installed on 2018-09-23 (20 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1797782] Re: evince immediately seg faults

2018-10-14 Thread Matt Sienko

I tried to a

On Sunday, October 14, 2018, 3:24:15 PM PDT, Matthew Sienko 
 wrote:  
 
  Christian,I attached a pdf that evince crashes trying to open, although every 
pdf I tried has caused a crash.
Here is the result of ls /var/crash:_usr_bin_evince.1001.crash   
_usr_bin_evince.1001.uploaded
_usr_bin_evince.1001.upload

Thanks,  -Matt

On Sunday, October 14, 2018, 11:15:37 AM PDT, Cristian Aravena Romero 
 wrote:  
 
 Hello,

Could you send a .pdf file to try to reproduce the error?

Best regards,
--
Cristian Aravena Romero (caravena)

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

Title:
  evince immediately seg faults

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  
  Description:    Ubuntu 18.04.1 LTS
  Release:    18.04

  evince:
    Installed: 3.28.2-1
    Candidate: 3.28.2-1
    Version table:
  *** 3.28.2-1 500
          500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
          100 /var/lib/dpkg/status

  Expected Behavior: evince opens and displays PDF document.

  What Happened: When launching evince, it crashes immediately with a
  segmentation fault. This happens every time. I have tried opening
  multiple PDF documents both from the command line and file browser.
  Launching evince from the command line without specifying a file also
  crashes. The PDF documents open fine in xpdf.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.2-1
  ProcVersionSignature: Ubuntu 4.15.0-1021.24-oem 4.15.18
  Uname: Linux 4.15.0-1021-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 08:29:01 2018
  InstallationDate: Installed on 2018-09-23 (20 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
  PATH=(custom, no user)
  XDG_RUNTIME_DIR=
  LANG=en_US.UTF-8
  SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Title:
  evince immediately seg faults

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  evince:
Installed: 3.28.2-1
Candidate: 3.28.2-1
Version table:
   *** 3.28.2-1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Expected Behavior: evince opens and displays PDF document.

  What Happened: When launching evince, it crashes immediately with a
  segmentation fault. This happens every time. I have tried opening
  multiple PDF documents both from the command line and file browser.
  Launching evince from the command line without specifying a file also
  crashes. The PDF documents open fine in xpdf.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.2-1
  ProcVersionSignature: Ubuntu 4.15.0-1021.24-oem 4.15.18
  Uname: Linux 4.15.0-1021-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 08:29:01 2018
  InstallationDate: Installed on 2018-09-23 (20 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1756632] Re: lightdm crashed with SIGSEGV in _dl_fini()

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

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

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

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

Title:
  lightdm crashed with SIGSEGV in _dl_fini()

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Crash occured on boot

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.25.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sat Mar 17 21:41:53 2018
  ExecutablePath: /usr/sbin/lightdm
  InstallationDate: Installed on 2017-10-24 (144 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  LightdmConfig:
   [Seat:*]
   autologin-guest=false
   autologin-user=skellat
   autologin-user-timeout=0
  ProcCmdline: lightdm --session-child 12 15
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7f4cc21acb3a <_dl_fini+410>: mov0x8(%rax),%r15
   PC (0x7f4cc21acb3a) ok
   source "0x8(%rax)" (0x7f4cbe73ee78) not located in a known VMA region 
(needed readable region)!
   destination "%r15" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: lightdm
  StacktraceTop:
   _dl_fini () at dl-fini.c:134
   __run_exit_handlers (status=0, listp=0x7f4cc0d19718 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at 
exit.c:108
   __GI_exit (status=) at exit.c:139
   ()
() at /lib/x86_64-linux-gnu/libc.so.6
  Title: lightdm crashed with SIGSEGV in _dl_fini()
  UpgradeStatus: Upgraded to bionic on 2018-02-19 (26 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1797805] Re: After Update to Ubuntu 18.04.1 LTS Libre Base wont open database

Hello Arne,

Apparently it is a problem of libreoffice.  I'm not sure.

Best regards,
--
Cristian Aravena Romero (caravena)

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

** No longer affects: libreoffice (Ubuntu)

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

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

Title:
  After Update to Ubuntu 18.04.1 LTS Libre Base wont open database

Status in libreoffice package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  A few days ago I updaet my System to Ubuntu 18.04.1 LTS.

  Today I found out that I can't open my Libre Base Adress-Database
  anymore.

  1) I start Libre Base.(German Version)
  2) The "Datenank-Assistent" asks me what I want to do. I continue by choosing 
to open my Adress-Database.
  3) The Libre Base Main Window apperas with my Database. At the left side are 
die Options "Tables", "Queries", "Forms" and "Reports". "Forms" is active. 
  4) I choose the only form stored with this database.
  5) Libre-Base crashes and takes all Instances of Libre Writer, etc. with it.
  6) I restart Libre Base. It wants to repair the broken Database. It does so 
succesfully.
  7) Continue with 3)

  My PC:
  CPU: Intel Celeron(r) CPU G1820 @ 2.70GHz x 2
   Grafik: Intel Haswell Desktop x86/MMX/SSE2
  RAM: 7.8 GB
Gnome: 3.28.2
  OS-TYpe: 32-bit
Disks: 1.1 TB

  libreoffice-base:
Installiert:   1:6.0.6-0ubuntu0.18.04.1
Installationskandidat: 1:6.0.6-0ubuntu0.18.04.1
Versionstabelle:
   *** 1:6.0.6-0ubuntu0.18.04.1 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/universe i386 
Packages
  100 /var/lib/dpkg/status
   1:6.0.3-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/universe i386 Packages

  
  Best regard

  Wannabe

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic i686
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  arne   2313 F pulseaudio
   /dev/snd/controlC0:  arne   2313 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 23:20:38 2018
  HibernationDevice: RESUME=UUID=47b31bba-205c-4d51-9e19-dcde4056d0cb
  InstallationDate: Installed on 2014-03-01 (1688 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=UUID=df276a8e-3485-4b48-b073-ebcb6e030df1 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-10-10 (4 days ago)
  dmi.bios.date: 12/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0701
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0701:bd12/03/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Desktop-packages] [Bug 1757226] Re: gnome-shell crashed with signal 5 in meta_xwayland_start()

** Information type changed from Private to Public

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

Title:
  gnome-shell crashed with signal 5 in meta_xwayland_start()

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Hello,

  I do not know why that happened...

  Regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Mar 19 16:56:39 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-13 (158 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CL.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_xwayland_start () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   ()
  Title: gnome-shell crashed with signal 5 in meta_xwayland_start()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 854382] Re: Simple Scan window not responding to keyboard shortcuts

2018-10-14 Thread Mathieu Dubois

@Colan Schwartz: thanks for the link. It suggests a workaround for the
issue: start simple-scan from terminal with `XDG_CURRENT_DESKTOP=XFCE
simple-scan` (each time). I confirm this is harmless (it doesn't change
anything on your system so if you retart simple-scan as usual it won't
work) and works under Ubuntu 18.04 (Ubuntu desktop). This seems to
indicate that the problem comes from the integration with the desktop.

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

Title:
  Simple Scan window not responding to keyboard shortcuts

Status in One Hundred Papercuts:
  Confirmed
Status in Simple Scan:
  Triaged
Status in simple-scan package in Ubuntu:
  Confirmed
Status in simple-scan package in Debian:
  Confirmed

Bug description:
  The menus indicate that a single page can be scanned by hitting Ctrl+1
  on the keyboard, but pressing Ctrl+1 does not cause a scan to occur.

  Additionally pressing the Delete key does not delete the currently
  selected page.

  Curiously, pressing Alt+D or Alt+P to open the Document or Page menu
  respectively does not result in the relevant menu opening.

  Pressing Tab does cause focus to shift back and forth between the page
  area and the toolbar.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: simple-scan 3.1.91-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic x86_64
  ApportVersion: 1.23-0ubuntu1
  Architecture: amd64
  Date: Tue Sep 20 12:45:41 2011
  DriverPackageVersions:
   libsane 1.0.22-2ubuntu1
   libsane-extras N/A
   hplip 3.11.7-0ubuntu5
   hpoj N/A
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: Hewlett-Packard HP Pavilion dv6500 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-11-generic 
root=UUID=7ceba223-c023-4c5b-825d-6680919457f0 ro quiet splash vt.handoff=7
  SimpleScanLog:
   
  SourcePackage: simple-scan
  UpgradeStatus: Upgraded to oneiric on 2011-09-12 (7 days ago)
  dmi.bios.date: 04/04/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.05
  dmi.board.name: 30CC
  dmi.board.vendor: Quanta
  dmi.board.version: 79.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.05:bd04/04/2007:svnHewlett-Packard:pnHPPaviliondv6500NotebookPC:pvrRev1:rvnQuanta:rn30CC:rvr79.10:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6500 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1786344] Re: Default IBus input method ignored in live session

2018-10-14 Thread Gunnar Hjalmarsson

@Andrea: When you get at this bug, please note bug #1796722 which was
marked as a duplicate of this one. The duplicate does include details in
the bug description which may be valuable to understand the nature of
the issue.

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

Title:
  Default IBus input method ignored in live session

Status in gnome-settings-daemon package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 18.10 iso (2018.8.7), select Simplified Chinese for booting, can't
  input Chinese character. From Settings -> Regions and Languages, selected
  Intelligent Pinyin, also could not input Chinese.

  ---

  18.10 镜像（2018.8.7）选择简体中文开机，无法输入中文。由 Settings -> Regions and
  Languages，选择 智能拼音，也无法输入中文。

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

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

[Desktop-packages] [Bug 1796722] Re: Unusual Region & Language settings on Live Session after clicking "Try Ubuntu"

2018-10-14 Thread Gunnar Hjalmarsson

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

On 2018-10-12 04:43, Jun Kobayashi wrote:
> It seems to me this bug is a little different from the bug #1786344.
> Comment #10 of the bug #1786344 you wrote could be related this bug,
> but other comments may be related to other problem on inputting
> chinese.

Yeah, but please note that one of the issues, which was originally
reported on bug #1786344, was moved to bug #1789665. So I agree with
Jeremy that this is actually a duplicate of the remaining issue there.

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

Title:
Unusual Region & Language settings on Live Session after clicking "Try
Ubuntu"

Status in gnome-settings-daemon package in Ubuntu:
Incomplete

Bug description:
I've faced this problem when I tried Cosmic daily iso with VirtualBox.

iso image: http://cdimage.ubuntu.com/daily-live/20181007/cosmic-
desktop-amd64.iso

Steps to Reproduce 1:
1. boot virtual pc with cosmic-desktop-amd64.iso
2. wait for Ubiquity dialoge
3. click "Try Ubuntu" button
4. wait for Live Session
5. input source selection menu is shown on right of topbar, including "en1",
"en2", "cm" and "en3"
6. open Settings app and select "Region & Language"
7. 4 input sources listed: English(US), English(Australian),
English(Cameroon), English(UK)

Steps to Reproduce 2:
1. boot virtual pc with cosmic-desktop-amd64.iso
2. wait for Ubiquity dialoge and select "Deutsch"
3. click "Ubuntu ausprobieren" button
4. wait for Live Session
5. input source selection menu is shown on right of topbar, including "de1",
"de2", "be" and "de3"
6. open Einstellungen app and select "Region und Sprache"
7. 4 input sources listed: Deutsch, Deutsch (Österreich), Belgisch, Deutsch
(Schweiz)
"English (United States)" for Sprache, "United States" for Formate

Steps to Reproduce 3:
1. boot virtual pc with cosmic-desktop-amd64.iso
2. wait for Ubiquity dialoge and select "日本語"
3. click "Ubuntuを試す" button
4. wait for Live Session
5. input source selection menu is shown on right of topbar, including "ja1",
"ja2", "ja3" and "ja4"
6. open Settings app and select "Region & Language"
7. 4 input sources listed: Japanese, Japanese (PC-98), Japanese (OADG 109A),
Japanese (Dvorak)
This setting don't supports inputting Japanese.

When I selected "Try Ubuntu without installing" on isolinux menu and login
directly into Live Session, only "English (US)" is shown for input source.This
seem to be normal setting.
When I selected "Deutsch" and boot Live Session, only "Deutsch" is shown for
input source.
When I selected "日本語" and boot Live Session, "Japanese" and "日本語(Mozc)" are
shown.This setting supports inputting Japanese.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubiquity 18.10.9
ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
Uname: Linux 4.18.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
CasperVersion: 1.396
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 8 17:11:12 2018
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper
initrd=/casper/initrd quiet splash --- maybe-ubiquity
LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181007)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=ja_JP.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1772191] Re: GNOME Mines desktop file icon too small

2018-10-14 Thread Bartosz Kosiorek

After install from proposed, the resolution of the mines icon is much better 
now (see attachment).
Verification complete successfully.

** Attachment added: "Zrzut ekranu z 2018-10-14 21-56-42.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-mines/+bug/1772191/+attachment/5200917/+files/Zrzut%20ekranu%20z%202018-10-14%2021-56-42.png

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

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

Title:
  GNOME Mines desktop file icon too small

Status in gnome-mines package in Ubuntu:
  Fix Released
Status in gnome-mines source package in Bionic:
  Fix Committed

Bug description:
  Impact
  --
  The icon of GNOME Mines in GNOME Shell Overview in Ubuntu 18.04 is blurred. 
This is because the icon resolution is too low. See the attached screenshot.

  Test Case
  -
  Check if /usr/share/icons/hicolor/256x256/apps/gnome-mines.png exists.

  Check if the app icon in the GNOME Shell Activities Overview looks
  less blurry than in the screenshot.

  Regression Potential
  
  This is a simple missing icon size from the meson build script. The patch is 
backported from gnome-mines 3.30.1. The icon was in our 3.26 builds but the 
regression was introduced when the project switched to meson.

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

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

[Desktop-packages] [Bug 854382] Re: Simple Scan window not responding to keyboard shortcuts

2018-10-14 Thread Colan Schwartz

The upstream Gnome bug is https://gitlab.gnome.org/GNOME/simple-
scan/issues/14, but Launchpad won't let me add that here.  Strangely,
the Debian bug report doesn't refer to it either.

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

Title:
  Simple Scan window not responding to keyboard shortcuts

Status in One Hundred Papercuts:
  Confirmed
Status in Simple Scan:
  Triaged
Status in simple-scan package in Ubuntu:
  Confirmed
Status in simple-scan package in Debian:
  Confirmed

Bug description:
  The menus indicate that a single page can be scanned by hitting Ctrl+1
  on the keyboard, but pressing Ctrl+1 does not cause a scan to occur.

  Additionally pressing the Delete key does not delete the currently
  selected page.

  Curiously, pressing Alt+D or Alt+P to open the Document or Page menu
  respectively does not result in the relevant menu opening.

  Pressing Tab does cause focus to shift back and forth between the page
  area and the toolbar.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: simple-scan 3.1.91-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic x86_64
  ApportVersion: 1.23-0ubuntu1
  Architecture: amd64
  Date: Tue Sep 20 12:45:41 2011
  DriverPackageVersions:
   libsane 1.0.22-2ubuntu1
   libsane-extras N/A
   hplip 3.11.7-0ubuntu5
   hpoj N/A
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: Hewlett-Packard HP Pavilion dv6500 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-11-generic 
root=UUID=7ceba223-c023-4c5b-825d-6680919457f0 ro quiet splash vt.handoff=7
  SimpleScanLog:
   
  SourcePackage: simple-scan
  UpgradeStatus: Upgraded to oneiric on 2011-09-12 (7 days ago)
  dmi.bios.date: 04/04/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.05
  dmi.board.name: 30CC
  dmi.board.vendor: Quanta
  dmi.board.version: 79.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.05:bd04/04/2007:svnHewlett-Packard:pnHPPaviliondv6500NotebookPC:pvrRev1:rvnQuanta:rn30CC:rvr79.10:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6500 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1797137] Re: HPLIP gui bug

2018-10-14 Thread APolihron

** Changed in: ubuntu-mate
   Status: Invalid => New

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

Title:
  HPLIP gui bug

Status in ubuntu-mate:
  New
Status in hplip package in Ubuntu:
  New

Bug description:
  Good afternoon

  After having installed the last version of HPLIP 3.18.9 with Ubuntu
  18.04 Mate, I found a bug concerning the page asking to select the
  printer connection type (WiFi, network or USB). If this page is called
  by using the HP icon and then by selecting add a device, it's
  impossible to reach the next page, by clicking on next. The page is
  coming back again and again.

  If I execute the instruction hp-setup in a terminal, the page asking
  to select the connection type is coming and then, a click on the Next
  button, is leading to the page where I can select the printer.

  So it seem that there is a bug concerning the HPLIP Gui.

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

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

[Desktop-packages] [Bug 1796614] Re: Ubuntu 18.10 - X fails to start on login

2018-10-14 Thread Christopher Patti

Hi there. Thanks for the triage. As per
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1795637/comments/25
this bug isn't a duplicate of the bug you mention. I've removed the
duplicate notation.

In fact this bug is being tracked in upstream Gnome bug
https://gitlab.gnome.org/GNOME/gdm/issues/428


** This bug is no longer a duplicate of bug 1795637
   No login screen when booting Cosmic due to plymouth racing with the rest of 
the boot process and not releasing DRM devices in time

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

Title:
  Ubuntu 18.10 - X fails to start on login

Status in gdm3 package in Ubuntu:
  New

Bug description:
  Running startx starts X just fine, but at login I just get a blank
  screen with a blinking cursor. If I hit Alt+F I can get a console
  which allows me to login and run 'startx' at which point Gnome starts
  normally after entering my keychain unlock password.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Oct  7 22:59:13 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Subsystem: Dell Device [1028:0877]
   NVIDIA Corporation GP104M [GeForce GTX 1070 Mobile] [10de:1be1] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell GP104M [GeForce GTX 1070 Mobile] [1028:0877]
  InstallationDate: Installed on 2018-10-07 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:2b8c Sunplus Innovation Technology Inc. 
   Bus 001 Device 002: ID 187c:0550 Alienware Corporation 
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Alienware Alienware 17 R5
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=c3d3798c-6179-472a-ba82-55ef94f4d382 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2018
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.5.0
  dmi.board.name: Alienware 17 R5
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.5.0:bd08/10/2018:svnAlienware:pnAlienware17R5:pvr1.5.0:rvnAlienware:rnAlienware17R5:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
  dmi.product.family: Alienware
  dmi.product.name: Alienware 17 R5
  dmi.product.sku: 0877
  dmi.product.version: 1.5.0
  dmi.sys.vendor: Alienware
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1797736] Re: Don't offer Facebook online account integration

This bug was fixed in the package gnome-initial-setup - 3.30.0-1ubuntu2

---
gnome-initial-setup (3.30.0-1ubuntu2) cosmic; urgency=medium

  * Add Don-t-show-Facebook-in-Ubuntu.patch:
- Don't offer Facebook login in Welcome to Ubuntu wizard since
  none of Ubuntu's default apps will use it. (LP: #1797736)

 -- Jeremy Bicha   Sat, 13 Oct 2018 22:28:02 -0400

** Changed in: gnome-initial-setup (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Don't offer Facebook online account integration

Status in gnome-initial-setup package in Ubuntu:
  Fix Released

Bug description:
  Impact
  ==
  Ubuntu does not install any apps by default that would use Facebook account 
in GOA.

  The supported apps are GNOME Photos and GNOME Maps.

  Therefore, we shouldn't offer Facebook in the Online Accounts page of
  the Welcome to Ubuntu wizard.

  The Online Accounts page isn't used in Ubuntu 18.04 LTS but it is used
  in Ubuntu 18.10

  Test Case
  =
  Install Ubuntu. After restarting your computer, the Welcome to Ubuntu wizard 
should launch. On the Online Accounts page, there should be Ubuntu Single 
Sign-On, Google, Nextcloud, and Microsoft. Facebook should not be present.

  Or you can use a shortcut to avoid needing to re-install Ubuntu. Just
  remove the empty ~/.config/gnome-initial-setup-done file to restart
  the wizard.

  Regression Potential
  
  None.

  Users can still sign in to Facebook from the Online Accounts page in
  the Settings app.

  GNOME doesn't show all the account types by default in gnome-initial-
  setup.

  This will only affect the Ubuntu sessions. Any one who logs in for the
  first time in the vanilla GNOME sessions will still have this option
  and will generally get the upstream GNOME experience rather than the
  Welcome to Ubuntu experience.

  Other Info
  ==
  The Welcome to Ubuntu wizard generally would only show up on first login 
(because the user should complete the wizard or close the wizard).

  Many Ubuntu desktop installs only have one user.

  Therefore, this won't be very beneficial as an SRU; it should be fixed
  before release.

  This issue was split off from LP: #1762192

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

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

[Desktop-packages] [Bug 1797796] [NEW] embedding OLE objects in Writer leads to blurred print

2018-10-14 Thread Wolf Rogner

Public bug reported:

Steps to create:

Open blank Writer document
Insert OLE object -> Libreoffice Calc
enter some numbers
leave OLE object

-> The object is rendered blurred.

Enter OLE object (double click)
-> the content is rendered correctly

Print document
-> the content of the OLE object is printed in lower quality than rest of 
document

Combined documents with text and calculations cannot be printed in unified 
quality.
-> This type of document is not up to office standards.

Only on Ubuntu (on Mac this cannot be observed)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libreoffice-writer 1:6.0.6-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 14 20:29:01 2018
InstallationDate: Installed on 2018-04-30 (167 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  embedding OLE objects in Writer leads to blurred print

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Steps to create:

  Open blank Writer document
  Insert OLE object -> Libreoffice Calc
  enter some numbers
  leave OLE object

  -> The object is rendered blurred.

  Enter OLE object (double click)
  -> the content is rendered correctly

  Print document
  -> the content of the OLE object is printed in lower quality than rest of 
document

  Combined documents with text and calculations cannot be printed in unified 
quality.
  -> This type of document is not up to office standards.

  Only on Ubuntu (on Mac this cannot be observed)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-writer 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 20:29:01 2018
  InstallationDate: Installed on 2018-04-30 (167 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1797782] Re: evince immediately seg faults

Hello,

Could you send a .pdf file to try to reproduce the error?

Best regards,
--
Cristian Aravena Romero (caravena)

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

Title:
  evince immediately seg faults

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  evince:
Installed: 3.28.2-1
Candidate: 3.28.2-1
Version table:
   *** 3.28.2-1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Expected Behavior: evince opens and displays PDF document.

  What Happened: When launching evince, it crashes immediately with a
  segmentation fault. This happens every time. I have tried opening
  multiple PDF documents both from the command line and file browser.
  Launching evince from the command line without specifying a file also
  crashes. The PDF documents open fine in xpdf.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.2-1
  ProcVersionSignature: Ubuntu 4.15.0-1021.24-oem 4.15.18
  Uname: Linux 4.15.0-1021-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 08:29:01 2018
  InstallationDate: Installed on 2018-09-23 (20 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1797782] Re: evince immediately seg faults

Hello Matt,

Please:

$ ls /var/crash

Best regards,
--
Cristian Aravena Romero (caravena)

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

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

Title:
  evince immediately seg faults

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  evince:
Installed: 3.28.2-1
Candidate: 3.28.2-1
Version table:
   *** 3.28.2-1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Expected Behavior: evince opens and displays PDF document.

  What Happened: When launching evince, it crashes immediately with a
  segmentation fault. This happens every time. I have tried opening
  multiple PDF documents both from the command line and file browser.
  Launching evince from the command line without specifying a file also
  crashes. The PDF documents open fine in xpdf.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.2-1
  ProcVersionSignature: Ubuntu 4.15.0-1021.24-oem 4.15.18
  Uname: Linux 4.15.0-1021-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 08:29:01 2018
  InstallationDate: Installed on 2018-09-23 (20 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1797791] [NEW] nvidia-340 installation issues need to be resolved and the package marked as 'tested'

2018-10-14 Thread Jack Howarth

Public bug reported:

The nvidia-graphics-drivers-340 is essential to many users. For example,
on my MacPro 3,1 equipped with an EVGA GTX-680 Mac version graphic card,
the nvidia 360, 390 and 396 drivers all fail due to issues with the new
nvidia_drm module resulting in no video output on DVI and HDMI.

https://devtalk.nvidia.com/default/topic/1042691/linux/black-screen-
with-mac-version-of-gtx-680/1

Similiar issues exist for a number of PC users as well...

https://devtalk.nvidia.com/default/topic/1037997/xid-61-black-screen-on-
startup-ubuntu-18-04-gtx-1060-mobile/

of which only some have been resolved. The nvidia-340 drivers are the
recommended fall back according to the Nvidia linux developers.

Unfortunately, the installation of the current nvidia-340
340.107-0ubuntu2 packaging is in really bad shape. The first error one
sees while attempting to install it are dpkg-divert errors like those
described in https://askubuntu.com/questions/419304/dpkg-divert-error-
rename-involves-overwriting-usr-lib-xorg-protocol-txt-wit but for the
files...

/usr/lib/x86_64-linux-gnu/libEGL.so.1.distrib
/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1.distrib
/usr/lib/x86_64-linux-gnu/libGLESv2.so.2.distrib.
/usr/lib/x86_64-linux-gnu/libGL.so.1.distrib

Currently one has to manually move these aside under a .bak suffix to
get past these post-removal script errors. I believe these issues may be
already addressed in the current nvidia-340 packaging residing on the
ppa:graphics-drivers/ppa repo.

The second installation issue that occurs is the same as that described
in https://askubuntu.com/questions/969352/uninstalling-and-then-
reinstalling-nvidia-384-kills-colord where currently the fix is the
same. One has to edit the installed nvidia-340.postinst file and change

NEWEST_KERNEL=$(get_newest_kernel "$(KERNEL")

to 
NEWEST_KERNEL=$(get_newest_kernel "$CURRENT_KERNEL")

following executing

sudo dpkg-reconfigure nvidia-340

to allow the installation to cleanly complete. Lastly, there seems to be
a missing dependency on the nvidia-340-dev that prevents akmods from
building the kernel modules which should be fixed.

The nvidia-340 drivers are supported until the end of 2019 by which time
hopefully Nvidia will finally clean up their current issues with the
newer drivers on problematic hardware.

https://nvidia.custhelp.com/app/answers/detail/a_id/3142

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: nvidia-340 340.107-0ubuntu2
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: wl nvidia
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 14 12:41:21 2018
InstallationDate: Installed on 2018-04-26 (170 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nvidia-graphics-drivers-340
UpgradeStatus: Upgraded to cosmic on 2018-09-30 (14 days ago)

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


** Tags: amd64 apport-bug cosmic

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

Title:
  nvidia-340 installation issues need to be resolved and the package
  marked as 'tested'

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  The nvidia-graphics-drivers-340 is essential to many users. For
  example, on my MacPro 3,1 equipped with an EVGA GTX-680 Mac version
  graphic card, the nvidia 360, 390 and 396 drivers all fail due to
  issues with the new nvidia_drm module resulting in no video output on
  DVI and HDMI.

  https://devtalk.nvidia.com/default/topic/1042691/linux/black-screen-
  with-mac-version-of-gtx-680/1

  Similiar issues exist for a number of PC users as well...

  https://devtalk.nvidia.com/default/topic/1037997/xid-61-black-screen-
  on-startup-ubuntu-18-04-gtx-1060-mobile/

  of which only some have been resolved. The nvidia-340 drivers are the
  recommended fall back according to the Nvidia linux developers.

  Unfortunately, the installation of the current nvidia-340
  340.107-0ubuntu2 packaging is in really bad shape. The first error one
  sees while attempting to install it are dpkg-divert errors like those
  described in https://askubuntu.com/questions/419304/dpkg-divert-error-
  rename-involves-overwriting-usr-lib-xorg-protocol-txt-wit but for the
  files...

  /usr/lib/x86_64-linux-gnu/libEGL.so.1.distrib
  /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1.distrib
  /usr/lib/x86_64-linux-gnu/libGLESv2.so.2.distrib.
  /usr/lib/x86_64-linux-gnu/libGL.so.1.distrib

  Currently one has to manually move these aside under a .bak suffix to
  get past these post-removal script errors. I believe these issues may
  be already addressed in th

[Desktop-packages] [Bug 1797789] [NEW] Video Driver not found

2018-10-14 Thread Faruk Hossain Surjo

Public bug reported:

Video Driver not found

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.4
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:Unity7:ubuntu
Date: Sun Oct 14 22:59:52 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [1458:d000]
InstallationDate: Installed on 2017-09-02 (406 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=2e2e3858-6ff9-4340-9216-6f95f78eaf2a ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/30/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F6
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-DS2
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd09/30/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Apr 19 17:07:03 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputA4TECH USB DeviceMOUSE, id 8
 inputA4TECH USB DeviceMOUSE, id 9
 inputA4TECH USB DeviceKEYBOARD, id 10
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2

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


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

Title:
  Video Driver not found

Status in xorg package in Ubuntu:
  New

Bug description:
  Video Driver not found

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  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:Unity7:ubuntu
  Date: Sun Oct 14 22:59:52 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd 2nd Generation Core Processor 
Family Integrated Graphics Controller [1458:d000]
  InstallationDate: Installed on 2017-09-02 (406 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=2e2e3858-6ff9-4340-9216-6f95f78eaf2a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade

[Desktop-packages] [Bug 1739897] Re: Background color of calc8 in Impress has unwanted offset

2018-10-14 Thread rogonow

Yes

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

Title:
  Background color of calc8 in Impress has unwanted offset

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  1) XFCE desktop enviroment 4.12

  2)
  Version: 5.4.3.2
  Build ID: 1:5.4.3~rc2-0ubuntu0.17.04.1~lo1
  CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk3; 
  Locale: nl-BE (en_US.UTF-8); Calc: group

  3) The background color respects the border

  4)The background color of pasted calc8 has an offset from the boarder.
  I made it visible with an object behind. (Screenshot)

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

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

[Desktop-packages] [Bug 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly

Norbert, please be respectful of other Ubuntu projects even if you don't
want to use them yourself.

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

Title:
  apt install xubuntu-desktop does not resolve dependencies properly

Status in apt package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in xubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1773697] RfKill.txt

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1773697/+attachment/5200878/+files/RfKill.txt

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

Title:
  [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed
  with error -22 after kernel upgrade

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

Bug description:
  Bug report has been generated on a partially working configuration.
  That allows ubuntu-bug to do more work.

  USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones
  started working when upgrading kernel from 4.13 to 4.15 series. Then
  it suddenly stopped working again on newer kernels. The bug report has
  been generated on the latest working mainline kernel 4.15.7. All newer
  kernels have some usb quirks in place, which should fix the playback
  sample rates to 48 kHz. The quirk seems not to be working correctly
  and hinder the audio system to recognize the USB-device as a sound
  device.

  The Headphones work on kernels before 4,15.7 when manually configuring
  pulseaudio to a default samplerate of 48 kHz.

  PX Headphones are on the newest firmware level.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.15.7-041507-lowlatency x86_64
  AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', 
'--no-upload'] failed with exit code 1: mktemp: failed to create directory via 
template '/tmp/zsh-1000/alsa-info.XX': No such file or directory
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun May 27 22:21:53 2018
  InstallationDate: Installed on 2016-02-05 (841 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful
  Symptom_Card: PX USB - PX USB
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [USB-Audio - PX USB, playback] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago)
  dmi.bios.date: 06/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET33W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS00Q00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS00Q00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dshr   3423 F pulseaudio
   /dev/snd/pcmC0D0c:   dshr   3423 F...m pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-02-07 (248 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128)
  MachineType: LENOVO 4291QQ1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/02/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET51WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291QQ1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not

[Desktop-packages] [Bug 1773697] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1773697/+attachment/5200879/+files/UdevDb.txt

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

Title:
  [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed
  with error -22 after kernel upgrade

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

Bug description:
  Bug report has been generated on a partially working configuration.
  That allows ubuntu-bug to do more work.

  USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones
  started working when upgrading kernel from 4.13 to 4.15 series. Then
  it suddenly stopped working again on newer kernels. The bug report has
  been generated on the latest working mainline kernel 4.15.7. All newer
  kernels have some usb quirks in place, which should fix the playback
  sample rates to 48 kHz. The quirk seems not to be working correctly
  and hinder the audio system to recognize the USB-device as a sound
  device.

  The Headphones work on kernels before 4,15.7 when manually configuring
  pulseaudio to a default samplerate of 48 kHz.

  PX Headphones are on the newest firmware level.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.15.7-041507-lowlatency x86_64
  AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', 
'--no-upload'] failed with exit code 1: mktemp: failed to create directory via 
template '/tmp/zsh-1000/alsa-info.XX': No such file or directory
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun May 27 22:21:53 2018
  InstallationDate: Installed on 2016-02-05 (841 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful
  Symptom_Card: PX USB - PX USB
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [USB-Audio - PX USB, playback] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago)
  dmi.bios.date: 06/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET33W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS00Q00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS00Q00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dshr   3423 F pulseaudio
   /dev/snd/pcmC0D0c:   dshr   3423 F...m pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-02-07 (248 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128)
  MachineType: LENOVO 4291QQ1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/02/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET51WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291QQ1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not

[Desktop-packages] [Bug 1773697] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1773697/+attachment/5200880/+files/WifiSyslog.txt

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

Title:
  [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed
  with error -22 after kernel upgrade

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

Bug description:
  Bug report has been generated on a partially working configuration.
  That allows ubuntu-bug to do more work.

  USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones
  started working when upgrading kernel from 4.13 to 4.15 series. Then
  it suddenly stopped working again on newer kernels. The bug report has
  been generated on the latest working mainline kernel 4.15.7. All newer
  kernels have some usb quirks in place, which should fix the playback
  sample rates to 48 kHz. The quirk seems not to be working correctly
  and hinder the audio system to recognize the USB-device as a sound
  device.

  The Headphones work on kernels before 4,15.7 when manually configuring
  pulseaudio to a default samplerate of 48 kHz.

  PX Headphones are on the newest firmware level.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.15.7-041507-lowlatency x86_64
  AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', 
'--no-upload'] failed with exit code 1: mktemp: failed to create directory via 
template '/tmp/zsh-1000/alsa-info.XX': No such file or directory
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun May 27 22:21:53 2018
  InstallationDate: Installed on 2016-02-05 (841 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful
  Symptom_Card: PX USB - PX USB
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [USB-Audio - PX USB, playback] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago)
  dmi.bios.date: 06/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET33W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS00Q00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS00Q00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dshr   3423 F pulseaudio
   /dev/snd/pcmC0D0c:   dshr   3423 F...m pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-02-07 (248 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128)
  MachineType: LENOVO 4291QQ1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/02/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET51WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291QQ1
  dmi.board.vendor: LENOVO
  dmi.board.ver

[Desktop-packages] [Bug 1773697] PulseList.txt

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1773697/+attachment/5200877/+files/PulseList.txt

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

Title:
  [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed
  with error -22 after kernel upgrade

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

Bug description:
  Bug report has been generated on a partially working configuration.
  That allows ubuntu-bug to do more work.

  USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones
  started working when upgrading kernel from 4.13 to 4.15 series. Then
  it suddenly stopped working again on newer kernels. The bug report has
  been generated on the latest working mainline kernel 4.15.7. All newer
  kernels have some usb quirks in place, which should fix the playback
  sample rates to 48 kHz. The quirk seems not to be working correctly
  and hinder the audio system to recognize the USB-device as a sound
  device.

  The Headphones work on kernels before 4,15.7 when manually configuring
  pulseaudio to a default samplerate of 48 kHz.

  PX Headphones are on the newest firmware level.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.15.7-041507-lowlatency x86_64
  AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', 
'--no-upload'] failed with exit code 1: mktemp: failed to create directory via 
template '/tmp/zsh-1000/alsa-info.XX': No such file or directory
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun May 27 22:21:53 2018
  InstallationDate: Installed on 2016-02-05 (841 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful
  Symptom_Card: PX USB - PX USB
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [USB-Audio - PX USB, playback] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago)
  dmi.bios.date: 06/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET33W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS00Q00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS00Q00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dshr   3423 F pulseaudio
   /dev/snd/pcmC0D0c:   dshr   3423 F...m pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-02-07 (248 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128)
  MachineType: LENOVO 4291QQ1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/02/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET51WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291QQ1
  dmi.board.vendor: LENOVO
  dmi.board.versi

[Desktop-packages] [Bug 1773697] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1773697/+attachment/5200874/+files/ProcCpuinfoMinimal.txt

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

Title:
  [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed
  with error -22 after kernel upgrade

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

Bug description:
  Bug report has been generated on a partially working configuration.
  That allows ubuntu-bug to do more work.

  USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones
  started working when upgrading kernel from 4.13 to 4.15 series. Then
  it suddenly stopped working again on newer kernels. The bug report has
  been generated on the latest working mainline kernel 4.15.7. All newer
  kernels have some usb quirks in place, which should fix the playback
  sample rates to 48 kHz. The quirk seems not to be working correctly
  and hinder the audio system to recognize the USB-device as a sound
  device.

  The Headphones work on kernels before 4,15.7 when manually configuring
  pulseaudio to a default samplerate of 48 kHz.

  PX Headphones are on the newest firmware level.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.15.7-041507-lowlatency x86_64
  AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', 
'--no-upload'] failed with exit code 1: mktemp: failed to create directory via 
template '/tmp/zsh-1000/alsa-info.XX': No such file or directory
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun May 27 22:21:53 2018
  InstallationDate: Installed on 2016-02-05 (841 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful
  Symptom_Card: PX USB - PX USB
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [USB-Audio - PX USB, playback] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago)
  dmi.bios.date: 06/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET33W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS00Q00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS00Q00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dshr   3423 F pulseaudio
   /dev/snd/pcmC0D0c:   dshr   3423 F...m pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-02-07 (248 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128)
  MachineType: LENOVO 4291QQ1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/02/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET51WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291QQ1
  dmi.board.vendor: LENOVO

[Desktop-packages] [Bug 1773697] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1773697/+attachment/5200876/+files/ProcModules.txt

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

Title:
  [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed
  with error -22 after kernel upgrade

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

Bug description:
  Bug report has been generated on a partially working configuration.
  That allows ubuntu-bug to do more work.

  USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones
  started working when upgrading kernel from 4.13 to 4.15 series. Then
  it suddenly stopped working again on newer kernels. The bug report has
  been generated on the latest working mainline kernel 4.15.7. All newer
  kernels have some usb quirks in place, which should fix the playback
  sample rates to 48 kHz. The quirk seems not to be working correctly
  and hinder the audio system to recognize the USB-device as a sound
  device.

  The Headphones work on kernels before 4,15.7 when manually configuring
  pulseaudio to a default samplerate of 48 kHz.

  PX Headphones are on the newest firmware level.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.15.7-041507-lowlatency x86_64
  AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', 
'--no-upload'] failed with exit code 1: mktemp: failed to create directory via 
template '/tmp/zsh-1000/alsa-info.XX': No such file or directory
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun May 27 22:21:53 2018
  InstallationDate: Installed on 2016-02-05 (841 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful
  Symptom_Card: PX USB - PX USB
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [USB-Audio - PX USB, playback] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago)
  dmi.bios.date: 06/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET33W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS00Q00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS00Q00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dshr   3423 F pulseaudio
   /dev/snd/pcmC0D0c:   dshr   3423 F...m pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-02-07 (248 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128)
  MachineType: LENOVO 4291QQ1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/02/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET51WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291QQ1
  dmi.board.vendor: LENOVO
  dmi.board.v

[Desktop-packages] [Bug 1773697] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1773697/+attachment/5200875/+files/ProcInterrupts.txt

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

Title:
  [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed
  with error -22 after kernel upgrade

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

Bug description:
  Bug report has been generated on a partially working configuration.
  That allows ubuntu-bug to do more work.

  USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones
  started working when upgrading kernel from 4.13 to 4.15 series. Then
  it suddenly stopped working again on newer kernels. The bug report has
  been generated on the latest working mainline kernel 4.15.7. All newer
  kernels have some usb quirks in place, which should fix the playback
  sample rates to 48 kHz. The quirk seems not to be working correctly
  and hinder the audio system to recognize the USB-device as a sound
  device.

  The Headphones work on kernels before 4,15.7 when manually configuring
  pulseaudio to a default samplerate of 48 kHz.

  PX Headphones are on the newest firmware level.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.15.7-041507-lowlatency x86_64
  AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', 
'--no-upload'] failed with exit code 1: mktemp: failed to create directory via 
template '/tmp/zsh-1000/alsa-info.XX': No such file or directory
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun May 27 22:21:53 2018
  InstallationDate: Installed on 2016-02-05 (841 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful
  Symptom_Card: PX USB - PX USB
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [USB-Audio - PX USB, playback] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago)
  dmi.bios.date: 06/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET33W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS00Q00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS00Q00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dshr   3423 F pulseaudio
   /dev/snd/pcmC0D0c:   dshr   3423 F...m pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-02-07 (248 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128)
  MachineType: LENOVO 4291QQ1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/02/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET51WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291QQ1
  dmi.board.vendor: LENOVO
  dmi.b

[Desktop-packages] [Bug 1773697] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1773697/+attachment/5200873/+files/ProcCpuinfo.txt

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

Title:
  [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed
  with error -22 after kernel upgrade

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

Bug description:
  Bug report has been generated on a partially working configuration.
  That allows ubuntu-bug to do more work.

  USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones
  started working when upgrading kernel from 4.13 to 4.15 series. Then
  it suddenly stopped working again on newer kernels. The bug report has
  been generated on the latest working mainline kernel 4.15.7. All newer
  kernels have some usb quirks in place, which should fix the playback
  sample rates to 48 kHz. The quirk seems not to be working correctly
  and hinder the audio system to recognize the USB-device as a sound
  device.

  The Headphones work on kernels before 4,15.7 when manually configuring
  pulseaudio to a default samplerate of 48 kHz.

  PX Headphones are on the newest firmware level.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.15.7-041507-lowlatency x86_64
  AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', 
'--no-upload'] failed with exit code 1: mktemp: failed to create directory via 
template '/tmp/zsh-1000/alsa-info.XX': No such file or directory
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun May 27 22:21:53 2018
  InstallationDate: Installed on 2016-02-05 (841 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful
  Symptom_Card: PX USB - PX USB
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [USB-Audio - PX USB, playback] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago)
  dmi.bios.date: 06/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET33W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS00Q00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS00Q00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dshr   3423 F pulseaudio
   /dev/snd/pcmC0D0c:   dshr   3423 F...m pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-02-07 (248 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128)
  MachineType: LENOVO 4291QQ1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/02/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET51WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291QQ1
  dmi.board.vendor: LENOVO
  dmi.board.v

[Desktop-packages] [Bug 1773697] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1773697/+attachment/5200871/+files/Lspci.txt

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

Title:
  [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed
  with error -22 after kernel upgrade

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

Bug description:
  Bug report has been generated on a partially working configuration.
  That allows ubuntu-bug to do more work.

  USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones
  started working when upgrading kernel from 4.13 to 4.15 series. Then
  it suddenly stopped working again on newer kernels. The bug report has
  been generated on the latest working mainline kernel 4.15.7. All newer
  kernels have some usb quirks in place, which should fix the playback
  sample rates to 48 kHz. The quirk seems not to be working correctly
  and hinder the audio system to recognize the USB-device as a sound
  device.

  The Headphones work on kernels before 4,15.7 when manually configuring
  pulseaudio to a default samplerate of 48 kHz.

  PX Headphones are on the newest firmware level.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.15.7-041507-lowlatency x86_64
  AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', 
'--no-upload'] failed with exit code 1: mktemp: failed to create directory via 
template '/tmp/zsh-1000/alsa-info.XX': No such file or directory
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun May 27 22:21:53 2018
  InstallationDate: Installed on 2016-02-05 (841 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful
  Symptom_Card: PX USB - PX USB
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [USB-Audio - PX USB, playback] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago)
  dmi.bios.date: 06/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET33W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS00Q00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS00Q00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dshr   3423 F pulseaudio
   /dev/snd/pcmC0D0c:   dshr   3423 F...m pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-02-07 (248 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128)
  MachineType: LENOVO 4291QQ1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/02/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET51WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291QQ1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not A

[Desktop-packages] [Bug 1773697] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1773697/+attachment/5200872/+files/Lsusb.txt

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

Title:
  [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed
  with error -22 after kernel upgrade

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

Bug description:
  Bug report has been generated on a partially working configuration.
  That allows ubuntu-bug to do more work.

  USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones
  started working when upgrading kernel from 4.13 to 4.15 series. Then
  it suddenly stopped working again on newer kernels. The bug report has
  been generated on the latest working mainline kernel 4.15.7. All newer
  kernels have some usb quirks in place, which should fix the playback
  sample rates to 48 kHz. The quirk seems not to be working correctly
  and hinder the audio system to recognize the USB-device as a sound
  device.

  The Headphones work on kernels before 4,15.7 when manually configuring
  pulseaudio to a default samplerate of 48 kHz.

  PX Headphones are on the newest firmware level.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.15.7-041507-lowlatency x86_64
  AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', 
'--no-upload'] failed with exit code 1: mktemp: failed to create directory via 
template '/tmp/zsh-1000/alsa-info.XX': No such file or directory
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun May 27 22:21:53 2018
  InstallationDate: Installed on 2016-02-05 (841 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful
  Symptom_Card: PX USB - PX USB
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [USB-Audio - PX USB, playback] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago)
  dmi.bios.date: 06/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET33W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS00Q00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS00Q00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dshr   3423 F pulseaudio
   /dev/snd/pcmC0D0c:   dshr   3423 F...m pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-02-07 (248 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128)
  MachineType: LENOVO 4291QQ1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/02/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET51WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291QQ1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not A

[Desktop-packages] [Bug 1773697] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1773697/+attachment/5200870/+files/IwConfig.txt

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

Title:
  [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed
  with error -22 after kernel upgrade

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

Bug description:
  Bug report has been generated on a partially working configuration.
  That allows ubuntu-bug to do more work.

  USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones
  started working when upgrading kernel from 4.13 to 4.15 series. Then
  it suddenly stopped working again on newer kernels. The bug report has
  been generated on the latest working mainline kernel 4.15.7. All newer
  kernels have some usb quirks in place, which should fix the playback
  sample rates to 48 kHz. The quirk seems not to be working correctly
  and hinder the audio system to recognize the USB-device as a sound
  device.

  The Headphones work on kernels before 4,15.7 when manually configuring
  pulseaudio to a default samplerate of 48 kHz.

  PX Headphones are on the newest firmware level.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.15.7-041507-lowlatency x86_64
  AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', 
'--no-upload'] failed with exit code 1: mktemp: failed to create directory via 
template '/tmp/zsh-1000/alsa-info.XX': No such file or directory
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun May 27 22:21:53 2018
  InstallationDate: Installed on 2016-02-05 (841 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful
  Symptom_Card: PX USB - PX USB
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [USB-Audio - PX USB, playback] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago)
  dmi.bios.date: 06/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET33W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS00Q00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS00Q00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dshr   3423 F pulseaudio
   /dev/snd/pcmC0D0c:   dshr   3423 F...m pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-02-07 (248 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128)
  MachineType: LENOVO 4291QQ1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/02/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET51WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291QQ1
  dmi.board.vendor: LENOVO
  dmi.board.version

[Desktop-packages] [Bug 1773697] AlsaInfo.txt

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1773697/+attachment/5200867/+files/AlsaInfo.txt

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

Title:
  [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed
  with error -22 after kernel upgrade

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

Bug description:
  Bug report has been generated on a partially working configuration.
  That allows ubuntu-bug to do more work.

  USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones
  started working when upgrading kernel from 4.13 to 4.15 series. Then
  it suddenly stopped working again on newer kernels. The bug report has
  been generated on the latest working mainline kernel 4.15.7. All newer
  kernels have some usb quirks in place, which should fix the playback
  sample rates to 48 kHz. The quirk seems not to be working correctly
  and hinder the audio system to recognize the USB-device as a sound
  device.

  The Headphones work on kernels before 4,15.7 when manually configuring
  pulseaudio to a default samplerate of 48 kHz.

  PX Headphones are on the newest firmware level.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.15.7-041507-lowlatency x86_64
  AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', 
'--no-upload'] failed with exit code 1: mktemp: failed to create directory via 
template '/tmp/zsh-1000/alsa-info.XX': No such file or directory
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun May 27 22:21:53 2018
  InstallationDate: Installed on 2016-02-05 (841 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful
  Symptom_Card: PX USB - PX USB
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [USB-Audio - PX USB, playback] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago)
  dmi.bios.date: 06/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET33W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS00Q00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS00Q00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dshr   3423 F pulseaudio
   /dev/snd/pcmC0D0c:   dshr   3423 F...m pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-02-07 (248 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128)
  MachineType: LENOVO 4291QQ1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/02/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET51WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291QQ1
  dmi.board.vendor: LENOVO
  dmi.board.version

[Desktop-packages] [Bug 1773697] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1773697/+attachment/5200869/+files/CurrentDmesg.txt

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

Title:
  [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed
  with error -22 after kernel upgrade

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

Bug description:
  Bug report has been generated on a partially working configuration.
  That allows ubuntu-bug to do more work.

  USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones
  started working when upgrading kernel from 4.13 to 4.15 series. Then
  it suddenly stopped working again on newer kernels. The bug report has
  been generated on the latest working mainline kernel 4.15.7. All newer
  kernels have some usb quirks in place, which should fix the playback
  sample rates to 48 kHz. The quirk seems not to be working correctly
  and hinder the audio system to recognize the USB-device as a sound
  device.

  The Headphones work on kernels before 4,15.7 when manually configuring
  pulseaudio to a default samplerate of 48 kHz.

  PX Headphones are on the newest firmware level.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.15.7-041507-lowlatency x86_64
  AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', 
'--no-upload'] failed with exit code 1: mktemp: failed to create directory via 
template '/tmp/zsh-1000/alsa-info.XX': No such file or directory
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun May 27 22:21:53 2018
  InstallationDate: Installed on 2016-02-05 (841 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful
  Symptom_Card: PX USB - PX USB
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [USB-Audio - PX USB, playback] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago)
  dmi.bios.date: 06/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET33W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS00Q00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS00Q00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dshr   3423 F pulseaudio
   /dev/snd/pcmC0D0c:   dshr   3423 F...m pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-02-07 (248 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128)
  MachineType: LENOVO 4291QQ1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/02/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET51WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291QQ1
  dmi.board.vendor: LENOVO
  dmi.board

[Desktop-packages] [Bug 1773697] CRDA.txt

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1773697/+attachment/5200868/+files/CRDA.txt

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

Title:
  [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed
  with error -22 after kernel upgrade

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

Bug description:
  Bug report has been generated on a partially working configuration.
  That allows ubuntu-bug to do more work.

  USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones
  started working when upgrading kernel from 4.13 to 4.15 series. Then
  it suddenly stopped working again on newer kernels. The bug report has
  been generated on the latest working mainline kernel 4.15.7. All newer
  kernels have some usb quirks in place, which should fix the playback
  sample rates to 48 kHz. The quirk seems not to be working correctly
  and hinder the audio system to recognize the USB-device as a sound
  device.

  The Headphones work on kernels before 4,15.7 when manually configuring
  pulseaudio to a default samplerate of 48 kHz.

  PX Headphones are on the newest firmware level.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.15.7-041507-lowlatency x86_64
  AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', 
'--no-upload'] failed with exit code 1: mktemp: failed to create directory via 
template '/tmp/zsh-1000/alsa-info.XX': No such file or directory
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun May 27 22:21:53 2018
  InstallationDate: Installed on 2016-02-05 (841 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful
  Symptom_Card: PX USB - PX USB
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [USB-Audio - PX USB, playback] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago)
  dmi.bios.date: 06/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET33W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS00Q00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS00Q00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dshr   3423 F pulseaudio
   /dev/snd/pcmC0D0c:   dshr   3423 F...m pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-02-07 (248 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128)
  MachineType: LENOVO 4291QQ1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/02/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET51WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291QQ1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Ava

[Desktop-packages] [Bug 1773697] Re: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade

Journalctl output after attaching USB device on Thinkpad X220 upgraded
to cosmic ...

Okt 14 17:46:10 ThinkPad-X220 kernel: usb 1-1.2: new full-speed USB device 
number 4 using ehci-pci
Okt 14 17:46:11 ThinkPad-X220 kernel: usb 1-1.2: New USB device found, 
idVendor=19b5, idProduct=0021, bcdDevice=25.20
Okt 14 17:46:11 ThinkPad-X220 kernel: usb 1-1.2: New USB device strings: Mfr=1, 
Product=2, SerialNumber=3
Okt 14 17:46:11 ThinkPad-X220 kernel: usb 1-1.2: Product: PX USB
Okt 14 17:46:11 ThinkPad-X220 kernel: usb 1-1.2: Manufacturer: Bowers & Wilkins
Okt 14 17:46:11 ThinkPad-X220 kernel: usb 1-1.2: SerialNumber: ABCDEF0123456789
Okt 14 17:46:11 ThinkPad-X220 mtp-probe[13033]: checking bus 1, device 4: 
"/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2"
Okt 14 17:46:11 ThinkPad-X220 mtp-probe[13033]: bus: 1, device: 4 was not an 
MTP device
Okt 14 17:46:11 ThinkPad-X220 kernel: usbcore: registered new interface driver 
snd-usb-audio
Okt 14 17:46:11 ThinkPad-X220 kernel: input: Bowers & Wilkins PX USB Consumer 
Control as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.2/0003:19B5:0021.0001/input/input16
Okt 14 17:46:11 ThinkPad-X220 kernel: input: Bowers & Wilkins PX USB as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.2/0003:19B5:0021.0001/input/input17
Okt 14 17:46:11 ThinkPad-X220 kernel: hid-generic 0003:19B5:0021.0001: 
input,hiddev2,hidraw0: USB HID v1.11 Device [Bowers & Wilkins PX USB] on 
usb-:00:1a.0-1.2/input2
Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (II) 
config/udev: Adding input device Bowers & Wilkins PX USB Consumer Control 
(/dev/input/event15)
Okt 14 17:46:11 ThinkPad-X220 systemd-udevd[13036]: Process '/usr/sbin/alsactl 
-E HOME=/run/alsa restore 1' failed with exit code 99.
Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (**) Bowers & 
Wilkins PX USB Consumer Control: Applying InputClass "libinput keyboard 
catchall"
Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (II) Using 
input driver 'libinput' for 'Bowers & Wilkins PX USB Consumer Control'
Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (II) 
systemd-logind: got fd for /dev/input/event15 13:79 fd 46 paused 0
Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (**) Bowers & 
Wilkins PX USB Consumer Control: always reports core events
Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (**) Option 
"Device" "/dev/input/event15"
Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (**) Option 
"_source" "server/udev"
Okt 14 17:46:11 ThinkPad-X220 pulseaudio[3423]: E: [pulseaudio] 
module-alsa-card.c: Failed to find a working profile.
Okt 14 17:46:11 ThinkPad-X220 pulseaudio[3423]: E: [pulseaudio] module.c: 
Failed to load module "module-alsa-card" (argument: "device_id="1" 
name="usb-Bowers___Wilkins_PX_USB_ABCDEF0123456789-00" 
card_name="alsa_card.usb-Bowers___Wilkins_PX_USB_ABCDEF0123456789-00" 
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no 
deferred_volume=yes use_ucm=yes 
card_properties="module-udev-detect.discovered=1""): initialization failed.
Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (II) event15 - 
Bowers & Wilkins PX USB Consumer Control: is tagged by udev as: Keyboard
Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (II) event15 - 
Bowers & Wilkins PX USB Consumer Control: device is a keyboard
Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (II) event15 - 
Bowers & Wilkins PX USB Consumer Control: device removed
Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (**) Option 
"config_info" 
"udev:/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.2/0003:19B5:0021.0001/input/input16/event15"
Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (II) XINPUT: 
Adding extended input device "Bowers & Wilkins PX USB Consumer Control" (type: 
KEYBOARD, id 13)
Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (**) Option 
"xkb_model" "pc105"
Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (**) Option 
"xkb_layout" "de"
Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (WW) Option 
"xkb_variant" requires a string value
Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (WW) Option 
"xkb_options" requires a string value
Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (II) event15 - 
Bowers & Wilkins PX USB Consumer Control: is tagged by udev as: Keyboard
Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (II) event15 - 
Bowers & Wilkins PX USB Consumer Control: device is a keyboard
Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (II) 
config/udev: Adding input device Bowers & Wilkins PX USB (/dev/input/event16)
Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-session[3218]: (II) No input 
driver specified, ignoring this device.
Okt 14 17:46:11 ThinkPad-X220 /usr/lib/gdm3/gdm-x-ses

[Desktop-packages] [Bug 1797785] [NEW] heap buffer overflow in ft_font_face_hash of gxps-fonts.c CVE-2018-10733