[Desktop-packages] [Bug 1827790] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Dell XPS 13 9380 - Screen brightness flashes

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

Bug description:
  Hello,

  I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu
  edition from Dell which came with 18.04, but I've since wiped it and
  installed 19.04 from a fresh ISO download. This is the non-touch non-
  4K version (13-inch 1080p).

  Every so often (maybe a couple of times per minute), the screen
  flashes brighter, as if the brightness has been turned up momentarily
  and then back down again.

  I previously had an issue with the brightness / colours changing
  slightly when I opened menus or if the screen content changed
  slightly, but I fixed that by disabling Dynamic Brightness in the
  BIOS. It is definitely a better experience with that turned off.

  However the screen flashing still persists.

  I booted a live image of Fedora 30 now that it has been released, and
  so far I have not seen the screen flashing, so I do not think the
  hardware is faulty.

  I ran apport-bug, so hopefully the collected information has been
  attached.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  5 15:59:45 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
  InstallationDate: Installed on 2019-04-28 (6 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS 13 9380
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes

[Daniel van Vugt]

** Package changed: mutter (Ubuntu) => linux (Ubuntu)

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

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

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

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

Title:
  Dell XPS 13 9380 - Screen brightness flashes

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

Bug description:
  Hello,

  I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu
  edition from Dell which came with 18.04, but I've since wiped it and
  installed 19.04 from a fresh ISO download. This is the non-touch non-
  4K version (13-inch 1080p).

  Every so often (maybe a couple of times per minute), the screen
  flashes brighter, as if the brightness has been turned up momentarily
  and then back down again.

  I previously had an issue with the brightness / colours changing
  slightly when I opened menus or if the screen content changed
  slightly, but I fixed that by disabling Dynamic Brightness in the
  BIOS. It is definitely a better experience with that turned off.

  However the screen flashing still persists.

  I booted a live image of Fedora 30 now that it has been released, and
  so far I have not seen the screen flashing, so I do not think the
  hardware is faulty.

  I ran apport-bug, so hopefully the collected information has been
  attached.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  5 15:59:45 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
  InstallationDate: Installed on 2019-04-28 (6 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS 13 9380
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes

[mactyr]

Thanks for the inquiry, vanvugt. I'm trying an Ubuntu on Wayland session
this evening and the brightness flashing has continued with about the
same frequency.

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

Title:
  Dell XPS 13 9380 - Screen brightness flashes

Status in mutter package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu
  edition from Dell which came with 18.04, but I've since wiped it and
  installed 19.04 from a fresh ISO download. This is the non-touch non-
  4K version (13-inch 1080p).

  Every so often (maybe a couple of times per minute), the screen
  flashes brighter, as if the brightness has been turned up momentarily
  and then back down again.

  I previously had an issue with the brightness / colours changing
  slightly when I opened menus or if the screen content changed
  slightly, but I fixed that by disabling Dynamic Brightness in the
  BIOS. It is definitely a better experience with that turned off.

  However the screen flashing still persists.

  I booted a live image of Fedora 30 now that it has been released, and
  so far I have not seen the screen flashing, so I do not think the
  hardware is faulty.

  I ran apport-bug, so hopefully the collected information has been
  attached.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  5 15:59:45 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
  InstallationDate: Installed on 2019-04-28 (6 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS 13 9380
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1828176] Re: Dock indicators do not work for snap apps

[Launchpad Bug Tracker]

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

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

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

Title:
  Dock indicators do not work for snap apps

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

Bug description:
  I have installed a minimal version of Ubuntu 19.04 and later I
  installed a few snap apps through the software center. Specifically,
  Caprine, Slack, Skype.

  Those apps load correctly, appear correctly on the dock at the bottom
  of the screen, however the indicators that should show a running app
  are absent for every such app.

  Tapping a snap application icon on the dock sometimes brings it on the
  foreground as expected (this happens with Slack), but other times (as
  with Caprine and Skype) nothing happens.

  Please note that tapping Activities (or hitting the Windows button)
  shows all the respective application windows which means that this is
  probably a snap & ubuntu dock only thing.

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

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

[Desktop-packages] [Bug 1829111] Re: Openvpn connection icons missing from display

[Launchpad Bug Tracker]

[Expired for network-manager-openvpn (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: network-manager-openvpn (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Openvpn connection icons missing from display

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

Bug description:
  Having upgraded to the unstable packages I no longer see an indication
  on the vpn dropdown to show what vpn's are connected and which are
  not.

  The last one active is shown at the top of the dropdown list, but
  others in the list are missing the indication that they used to have
  to say they are connected.

  The following appears in the log at the same time so I think its
  related.

  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #6   
7ffcd0736aa0 b   resource:///org/gnome/gjs/modules/signals.js:128 (7fc4db3cb820 
@ 386)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #7   
7ffcd0736b50 b   resource:///org/gnome/shell/ui/tweener.js:238 (7fc4db3cb3a0 @ 
159)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #8   
7ffcd0736bf0 b   resource:///org/gnome/shell/ui/tweener.js:209 (7fc4db3cb280 @ 
15)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: == Stack 
trace for context 0x55f2c9f241e0 ==
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #0   
55f2d255fca8 i   resource:///org/gnome/shell/ui/background.js:722 (7fc4daf08430 
@ 22)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #1   
55f2d255fc20 i   resource:///org/gnome/shell/ui/tweener.js:106 (7fc4db3c8940 @ 
37)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #2   
7ffcd0736720 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:208 
(7fc4db3d0670 @ 54)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #3   
7ffcd0736870 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:342 
(7fc4db3d0700 @ 1742)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #4   
7ffcd0736920 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:355 
(7fc4db3d0790 @ 100)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #5   
7ffcd07369b0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:370 
(7fc4db3d0820 @ 10)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #6   
7ffcd0736aa0 b   resource:///org/gnome/gjs/modules/signals.js:128 (7fc4db3cb820 
@ 386)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #7   
7ffcd0736b50 b   resource:///org/gnome/shell/ui/tweener.js:238 (7fc4db3cb3a0 @ 
159)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #8   
7ffcd0736bf0 b   resource:///org/gnome/shell/ui/tweener.js:209 (7fc4db3cb280 @ 
15)
  May 15 13:52:03 pnunn-XPS-13-9370 gnome-shell[2942]: g_object_run_dispose: 
assertion 'G_IS_OBJECT (object)' failed
  May 15 13:52:03 pnunn-XPS-13-9370 gnome-shell[2942]: Object Meta.Background 
(0x55f2cdc6f230), has been already deallocated — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  May 15 13:52:03 pnunn-XPS-13-9370 gnome-shell[2942]: g_object_run_dispose: 
assertion 'G_IS_OBJECT (object)' failed
  May 15 13:52:03 pnunn-XPS-13-9370 gnome-shell[2942]: Object Meta.Background 
(0x55f2cdc6f230), has been already deallocated — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: == Stack 
trace for context 0x55f2c9f241e0 ==
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #0   
55f2d255fca8 i   resource:///org/gnome/shell/ui/background.js:722 (7fc4daf08430 
@ 22)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #1   
55f2d255fc20 i   resource:///org/gnome/shell/ui/tweener.js:106 (7fc4db3c8940 @ 
37)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #2   
7ffcd0736720 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:208 
(7fc4db3d0670 @ 54)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #3   
7ffcd0736870 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:342 
(7fc4db3d0700 @ 1742)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #4   
7ffcd0736920 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:355 
(7fc4db3d0790 @ 100)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #5   
7ffcd07369b0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:370 
(7fc4db3d0820 @ 10)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #6   
7ffcd0736aa0 b   

[Desktop-packages] [Bug 1827417] Re: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only.

[Kai-Heng Feng]

Something like this http://cdimages.ubuntu.com/lubuntu/daily-
live/current/?

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

Title:
  Ubuntu 16.04 -  EMU10K1 / CT4832 lost ability to listen stereo on
  headphones -  there is upmixed  surround only.

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

Bug description:
  Hello,

  I have a problem - after one of the updates (sorry for being not precise - I 
can only track it back to the time I have been surely listening something on 
headphones - it has to be beginning of this year because last time I have been 
listening more on my SB Live for sure was in last one-two weeks of February 
2019 - I have suddenly lost "stereo" on my headphones.
  I have speakers connected to on-board sound card and headphones connected to 
SB Live Value for few years, so I did not mess with outputs or something - one 
day I changed Audacious output to SbLive in pavucontrol (as usually) and that 
time the sound was weirdly filtered.
  I have found that this must be "surround upmix" which I do not need and tried 
to disable it,
  enable-remixing = no and the same for "LFE remixing" in 
/etc/pulse/daemon.conf did not work.
  It does not matter what configuration I choose in pavucontrol- analog stereo 
duplex, "analog stereo output", "Analog surround 5.1" or 4.1 - for all "Analog 
output" scenarios the output is the same except for "mono" (no sound at all).
  I have tried do "skip" pulseaudio choosing "ALSA" output in Audacious + the 
alsa configuration for stereo but the upmix is still present.

  I have followed the old thread in Launchpad Answers:
  https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/169428
  =
  Hello,

  i'm on ubuntu 16.04LTS (AMD64, with emu10k1 based soundcard) and since the 
last update I have similar problem - I have lost ability to listen stereo music 
on my Soundblaster Live Value (i use earphones).
  Even system sounds , web browser content and mp3 files are up-mixed.
  Few days ago it was no problem to choose "analag stereo output" in 
pavucontrol, now it seems that at this output have rear surround channel only 
(as I suppose, there is "stereo" but vocals are like heard from the other room 
and there is sometimes reverb as in the bathroom) :/.
  I had tried adding "set enable-remixing=no" in both /etc/pulse/daemon.conf 
and in the home directory configuration file without success.
  I have purged pulseaudio but with the ALSA there is the same problem, I have 
tried purging alsa and reinstalling without effect.
  So i thought that it can be emu10k1 driver specific, after digging in the 
network for solutions I have had tried adding 
"hint.emu10kx.0.multichannel_disabled " to the module configuration file 
without visible (or rather soundible ;) effect.
  I have tried to check EMU10K1 configuration with aweset, but it gives error 
message, so maybe the bad magic sits somewhere around?

  aweset
  /dev/sequencer: No such file or directory

  Once again - everything worked fine until the last update. I use
  xubuntu desktop as my machine is quite old, in despair I have
  installed unity to find the sound settings / speaker configuration etc
  and button to "disable all effects" as I have seen somewhere, but
  there were no such options.

  Help me Obi Wan Kenobi, you're my only hope...
  =

  I have next tried to follow the path from ubuntu sound troubleshooting
  guide, I have purged everything, installed back and now I'm  here
  again with this "upmix" on SBLive! Value.

  Thanks in advance for help :)
  Tom
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=654027ee-6ab0-41ba-8537-452da07cda0e
  InstallationDate: Installed on 2011-10-07 (2765 days ago)
  InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 
(20110720.1)
  IwConfig:
   lono wireless extensions.
   
   lxcbr0no wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. M68MT-S2
  Package: pulseaudio 1:8.0-0ubuntu3.10
  PackageArchitecture: amd64
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic 
root=UUID=4559c496-f083-41a2-ad7c-1e03334389fd ro plymouth 
usbcore.autosuspend=-1
  ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-146-generic N/A
   linux-backports-modules-4.4.0-146-generic  N/A
   linux-firmware 1.157.21
  RfKill:
   
  Tags: xenial third-party-packages xenial
  Uname: Linux 4.4.0-146-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2018-05-23 (344 days ago)
  UserGroups: adm 

[Desktop-packages] [Bug 1810176] Re: libmtp error could not get object handles

[Gareth Evans]

I am experiencing this problem on Ubuntu Mate 18.04.2 reading/writing
the

/DCIM/Camera

folder on a Samsung Galaxy S5 mini with Android 6.0.1

The first ~250 of 550 jpg images copy successfully, then file the
operation window freezes and does not respond to clicking the cancel
button.

/var/log/syslog shows

Jul 15 03:24:41  gvfsd[3824]: Error 2: Error 02ff: PTP I/O Error
Jul 15 03:24:54  gvfsd[3824]: Error 2: PTP Layer error 02ff: 
LIBMTP_Get_Files_And_Folders(): could not get object handles.

When /DCIM/Camera/ is accessed, Caja navigation freezes, eventually
producing the "could not get object handles" error.

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

Title:
  libmtp error could not get object handles

Status in libmtp package in Ubuntu:
  Incomplete

Bug description:
  When connecting my android galaxy s7 phone via usb, I am unable to
  access my Music folder, which contains 380 subfolders.  The file
  manager is inactive for a long time, and finally displays the error:

  Sorry, could not display all the contents of "Music": libmtp error:
  could not get object handles.

  Adding one more subfolder on the android side seems to work around the
  issue, so the issue is related to the number of items.

  Given this, my issue appears to be a specific example of the issue described 
in the link below.
  https://sourceforge.net/p/libmtp/bugs/1808/

  Observed in linux mint 18.3 64 bit / ubuntu 16.04

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

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

[Desktop-packages] [Bug 1827790] Re: Dell XPS 13 9380 - Screen flashes

[Daniel van Vugt]

Does the problem occur in only Xorg sessions ("Ubuntu") or Wayland too
("Ubuntu on Wayland")?

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: Confirmed => Incomplete

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

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

** Summary changed:

- Dell XPS 13 9380 - Screen flashes
+ Dell XPS 13 9380 - Screen brightness flashes

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

Title:
  Dell XPS 13 9380 - Screen brightness flashes

Status in mutter package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu
  edition from Dell which came with 18.04, but I've since wiped it and
  installed 19.04 from a fresh ISO download. This is the non-touch non-
  4K version (13-inch 1080p).

  Every so often (maybe a couple of times per minute), the screen
  flashes brighter, as if the brightness has been turned up momentarily
  and then back down again.

  I previously had an issue with the brightness / colours changing
  slightly when I opened menus or if the screen content changed
  slightly, but I fixed that by disabling Dynamic Brightness in the
  BIOS. It is definitely a better experience with that turned off.

  However the screen flashing still persists.

  I booted a live image of Fedora 30 now that it has been released, and
  so far I have not seen the screen flashing, so I do not think the
  hardware is faulty.

  I ran apport-bug, so hopefully the collected information has been
  attached.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  5 15:59:45 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
  InstallationDate: Installed on 2019-04-28 (6 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS 13 9380
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1836418] Re: No HDMI audio device after resume, but pacmd list-cards sees it

[Daniel van Vugt]

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

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


** Tags added: bionic

** This bug has been marked a duplicate of bug 1718927
   No HDMI sound after suspend/resume on 16.04

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

Title:
  No HDMI audio device after resume, but pacmd list-cards sees it

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After suspend/resume, the HDMI audio device is missing from Sound
  Settings and pavucontrol.

  'pacmd list-cards' still shows the device.

  This on Ubuntu 18.04.2 LTS 18.04 kernel
  5.2.0-rc6-19.06.26.amdgpu.ubuntu

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

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

[Desktop-packages] [Bug 1718927] Re: No HDMI sound after suspend/resume on 16.04

[Daniel van Vugt]

** Tags added: bionic

** Summary changed:

- No HDMI sound after suspend/resume on 16.04
+ No HDMI sound after suspend/resume

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

Title:
  No HDMI sound after suspend/resume

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When plugging in a HDMI TV to Lenovo Carbon 3rd Edition, sound works
  perfectly, but when I suspend computer and resume it there is no sound
  via HDMI in TV. However sound via built in speakers works fine. The
  only thing I can do to restore sound is to reboot the machine. Similar
  problem was discussed in following thread
  https://ubuntuforums.org/showthread.php?t=2251651 with no solution. I
  tested it on several versions of kernel 4.4.0 and on 4.4.8. Still no
  solution.

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

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

[Desktop-packages] [Bug 1836434] Re: can not able to browse site which needed adobe flash player and latest graphic drivers

[Daniel van Vugt]

Please be careful to only report one issue per bug. It sounds like there
are multiple issues here. Which issue would you like this bug to be
about, and which web browser are you using?

** 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/1836434

Title:
  can not able to browse site which needed adobe flash player and latest
  graphic drivers

Status in Ubuntu:
  Incomplete

Bug description:
  can not able to browse site which needed adobe flash player and latest
  graphic drivers. and also can't ab;e to access the settings of ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 13 10:39:46 2019
  DistUpgraded: 2019-05-23 11:48:24,738 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   anbox, 1, 5.0.0-19-generic, x86_64: installed
   anbox, 1, 5.0.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF119 [GeForce GT 610] [1043:8496]
  InstallationDate: Installed on 2019-04-15 (88 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic 
root=UUID=fe96674e-a634-4474-9fab-b79d0d3d0a5b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to disco on 2019-05-23 (50 days ago)
  dmi.bios.date: 03/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.20
  dmi.board.name: H91M-XT PLUS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd03/27/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH91M-XTPLUS:rvr:cvnToBeFilledByO.E.M.: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.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1336274] Re: HDMI Audio and all other audio disappeared from input sources and output sources in the audio control panel and stereo system is looping between audio is coming an

[Daniel van Vugt]

The attachments show that pulseaudio was not running when the bug was
reported in 2014. That's why things seem to disappear in the GUI:

!!Sound Servers on this system
!!

Pulseaudio:
  Installed - Yes (/usr/bin/pulseaudio)
  Running - No

Please let us know if you still experience the problem, and if so then
in what Ubuntu version.

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

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

Title:
  HDMI Audio and all other audio disappeared from input sources and
  output sources in the audio control panel and stereo system is looping
  between audio is coming and audio is not coming from the computer.

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After I did an update via system update, my system stopped working
  with audio. I then viewed the audio control panel and non of my
  output/input sources appear. I'm assuming that a component that Pulse
  Audio uses has been updated and ether Pulse Audio does not know how to
  communicate with it, or the component was not tested before being
  released. I have not changed any of my hardware configurations, so it
  cannot be a hardware issue. Also using XBMC and I'm guessing XBMC
  backed down to using ASLA, I am able to set HDMI out (which I had to
  change from previous configuration which I'm assuming is because Pulse
  Audio is unable to start) and it works fine until I stop using it for
  awhile. After I stop using it for awhile, I have to reboot the system
  to get XBMC working again.

  The way my stereo system (A Yamaha Receiver) is reacting to this is
  it's showing it has audio coming from the computer one second, then
  the other second it doesn't have audio. I'm assuming this is the
  daemon of Pulse Audio restarting over and over again after it cannot
  start.

  I ran pulse audio in verbose mode to show what module is causing it to
  fail to load, and it is module-systemd-login. The reason it is failing
  to load is "Failed to create session monitor: No space left on device"
  but none of my disks are anywhere near being used up, nor is my ram,
  so I have no idea as to what it could be referring to... Maybe it's
  referring to space in the audio hardware??? I do not know... I have
  attached the logs on here.

  Any help would be useful in getting my audio back, I'm a
  hacker/developer/all around geek who loves the terminal, so please ask
  any questions! Please do feel free to email me, I want my audio back!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D8p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Tue Jul  1 08:34:09 2014
  InstallationDate: Installed on 2014-05-18 (43 days ago)
  InstallationMedia: It
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85-G41 PC Mate(MS-7850)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.4:bd12/02/2013:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnB85-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7850
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Desktop-packages] [Bug 1836051] Re: autamatic sleep notification cannot close

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1836051

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Changed in: gnome-shell (Ubuntu)
   Status: New => 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/1836051

Title:
  autamatic sleep notification cannot close

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I put my computer to sleep mode. 4 hours set afer no use. Vhen
  notification appeared, I put comp to sleep. After woke up,
  notification is still and can not close thru X. ubuntu-bug 18.04.2

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

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

[Desktop-packages] [Bug 1828393] Re: Unable to use bluetooth headset with mic and a2dp audio

[Daniel van Vugt]

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

Eric, it sounds like you're right about the "true bug".

However I also feel this bug report as it was originally worded is not
really any different to bug 508522.

I suggest the right thing to do here is to:

1. Open a new bug for what you describe.
2. Mark bug 1828393 as a duplicate of bug 508522 again.
3. Correct any misunderstandings in bug 508522 and link to your new bug. Maybe 
bug 508522 will become a duplicate of your new bug.

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

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

Title:
  Unable to use bluetooth headset with mic and a2dp audio

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Every device supports high fidelity audio while using headset with
  mic. This needs to enable two profiles at once: headset_head_unit and
  a2dp_sink. Right now this is impossible and I need to switch between
  profiles when listening to music and joining a call. In any case, the
  sound quality of HSP/HFP used in the headset_head_unit profile is
  horrible to have a call.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  9 13:20:26 2019
  InstallationDate: Installed on 2018-11-20 (169 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET35W (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET35W(1.17):bd12/21/2018:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1749481] Re: Wrong session marked as selected in session dropdown on login screen

[Daniel van Vugt]

Yes the upstream bug link (I just fixed up) is showing it was fixed in
gdm3 version 3.27.91, so before 18.04 was released.

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

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

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

** Changed in: gdm
 Remote watch: GNOME Bug Tracker #793456 => bugzilla.gnome.org/ #793609

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

** No longer affects: gnome-session (Ubuntu)

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

Title:
  Wrong session marked as selected in session dropdown on login screen

Status in gdm:
  Unknown
Status in gdm3 package in Ubuntu:
  Fix Released

Bug description:
  My usual session is "Ubuntu" (/usr/share/xsessions/ubuntu.desktop).
  When I reboot my machine, on the login screen if I click the cog icon
  to show the list of sessions available, a dot is displayed to the left
  of the first session in the list ("GNOME"), instead of "Ubuntu".

  If I don't click on a session to change it, when I log in the session
  used is "Ubuntu" as expected, not "GNOME".

  So the greeter fails to reflect which session is actually selected
  when first displaying the dropdown, but internally it doesn't mess up
  with session selection.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.26.2.1-2ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 16:00:38 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (591 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to bionic on 2018-01-29 (16 days ago)

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

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

[Desktop-packages] [Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation

[Daniel van Vugt]

The formal fix is awaiting review;

  https://gitlab.gnome.org/GNOME/mutter/merge_requests/600

but you can download it as a patch:

  https://gitlab.gnome.org/GNOME/mutter/merge_requests/600.patch

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

Title:
  [nvidia] Corrupted wallpaper after resuming from suspend or
  hibernation

Status in GNOME Shell:
  New
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Bionic:
  Confirmed
Status in mutter source package in Disco:
  Confirmed
Status in mutter source package in Eoan:
  In Progress

Bug description:
  https://trello.com/c/i5hENxSO

  Every other wake from sleep presents a corrupted screen with no unlock
  app.  There's a dock and system menu on a black background with pixel
  garbage.  Some personal information in the dock's large window
  thumbnails.  Bitmap garbage flashes on the screen when interacting
  with anything.  Only workaround is doing another sleep-wake cycle.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:4b:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13.1
  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: Thu Dec 20 22:19:29 2018
  DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-11-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-12-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162]
  InstallationDate: Installed on 2018-10-28 (54 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gigabyte Technology Co., Ltd. Default string
  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.18.0-12-generic 
root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F24
  dmi.board.asset.tag: Default string
  dmi.board.name: X99P-SLI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  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/gnome-shell/+bug/1809407/+subscriptions

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

[Desktop-packages] [Bug 1749481] Re: Wrong session marked as selected in session dropdown on login screen

[AsciiWolf]

Is this issue still happening? I think it was fixed in 18.04.

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

Title:
  Wrong session marked as selected in session dropdown on login screen

Status in gdm:
  Invalid
Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-session package in Ubuntu:
  Incomplete

Bug description:
  My usual session is "Ubuntu" (/usr/share/xsessions/ubuntu.desktop).
  When I reboot my machine, on the login screen if I click the cog icon
  to show the list of sessions available, a dot is displayed to the left
  of the first session in the list ("GNOME"), instead of "Ubuntu".

  If I don't click on a session to change it, when I log in the session
  used is "Ubuntu" as expected, not "GNOME".

  So the greeter fails to reflect which session is actually selected
  when first displaying the dropdown, but internally it doesn't mess up
  with session selection.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.26.2.1-2ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 16:00:38 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (591 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to bionic on 2018-01-29 (16 days ago)

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

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

[Desktop-packages] [Bug 1836499] Re: Ignores HintSystem (UDISKS_SYSTEM)

[Vojtěch Trefný]

The documentation is a little bit confusing here -- the "HintSystem"
property is not about the device access or filesystem permissions, it's
about "accessing" UDisks functions using PolicyKit.

See the policies here [1] for mounting filesystems -- "normal" devices
can be mounted by a "regular" user (in an active session), but "system"
devices require root authentication (similar policies exist for
unlocking encrypted devices, ejecting drives etc.)

[1] https://github.com/storaged-
project/udisks/blob/master/data/org.freedesktop.UDisks2.policy.in#L15

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

Title:
  Ignores HintSystem (UDISKS_SYSTEM)

Status in udisks2 package in Ubuntu:
  New

Bug description:
  [18.04 amd64]

  HintSystem (which can be set by a udev rule with
  ENV{UDISKS_SYSTEM}="1") is supposed to "require additional permissions
  to access" [0] but there is no difference in the mount permissions
  when it is set:

  # UDISKS_SYSTEM=0

  $ udisksctl info -b /dev/sr0  
   
/org/freedesktop/UDisks2/block_devices/sr0: 
  
org.freedesktop.UDisks2.Block:  

  Configuration:  []

  CryptoBackingDevice:'/'   

  Device: /dev/sr0  

  ...
  HintAuto:   true
  HintIconName:
  HintIgnore: false
  HintName:
  HintPartitionable:  false
  HintSymbolicIconName:
  HintSystem: false
  Id: by-uuid-2019-06-22-02-06-15-00
  ...
  UserspaceMountOptions:  uhelper=udisks2
org.freedesktop.UDisks2.Filesystem:
  MountPoints:/media/tj/Xubuntu 19.10 amd64
  Size:   0

  $ mount | grep media/tj
  /dev/sr0 on /media/tj/Xubuntu 19.10 amd64 type iso9660 
(ro,nosuid,nodev,relatime,nojoliet,check=s,map=n,blocksize=2048,uid=1000,gid=1000,dmode=500,fmode=400,uhelper=udisks2)

  # UDISKS_SYSTEM=1

  $ udisksctl info -b /dev/sr0
  /org/freedesktop/UDisks2/block_devices/sr0: 
org.freedesktop.UDisks2.Block: 
  Configuration:  []

  CryptoBackingDevice:'/'   

  Device: /dev/sr0  
  
  ...
  HintAuto:   true
  HintIconName:   
  HintIgnore: false   
  HintName:   
  HintPartitionable:  false 
  HintSymbolicIconName:
  HintSystem: true
  Id: by-uuid-2019-06-22-02-06-15-00
  ...
  UserspaceMountOptions:  uhelper=udisks2
org.freedesktop.UDisks2.Filesystem:
  MountPoints:/media/tj/Xubuntu 19.10 amd64
  Size:   0

  $ mount | grep media/tj
  /dev/sr0 on /media/tj/Xubuntu 19.10 amd64 type iso9660 
(ro,nosuid,nodev,relatime,nojoliet,check=s,map=n,blocksize=2048,uid=1000,gid=1000,dmode=500,fmode=400,u
  helper=udisks2)

  
  [0] 
http://storaged.org/doc/udisks2-api/latest/gdbus-org.freedesktop.UDisks2.Block.html#gdbus-property-org-freedesktop-UDisks2-Block.HintSystem

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

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

[Desktop-packages] [Bug 1836499] [NEW] Ignores HintSystem (UDISKS_SYSTEM)

[TJ]

Public bug reported:

[18.04 amd64]

HintSystem (which can be set by a udev rule with ENV{UDISKS_SYSTEM}="1")
is supposed to "require additional permissions to access" [0] but there
is no difference in the mount permissions when it is set:

# UDISKS_SYSTEM=0

$ udisksctl info -b /dev/sr0
 
/org/freedesktop/UDisks2/block_devices/sr0: 
  
  org.freedesktop.UDisks2.Block:
  
Configuration:  []  
  
CryptoBackingDevice:'/' 
  
Device: /dev/sr0
  
...
HintAuto:   true
HintIconName:
HintIgnore: false
HintName:
HintPartitionable:  false
HintSymbolicIconName:
HintSystem: false
Id: by-uuid-2019-06-22-02-06-15-00
...
UserspaceMountOptions:  uhelper=udisks2
  org.freedesktop.UDisks2.Filesystem:
MountPoints:/media/tj/Xubuntu 19.10 amd64
Size:   0

$ mount | grep media/tj
/dev/sr0 on /media/tj/Xubuntu 19.10 amd64 type iso9660 
(ro,nosuid,nodev,relatime,nojoliet,check=s,map=n,blocksize=2048,uid=1000,gid=1000,dmode=500,fmode=400,uhelper=udisks2)

# UDISKS_SYSTEM=1

$ udisksctl info -b /dev/sr0
/org/freedesktop/UDisks2/block_devices/sr0: 
  org.freedesktop.UDisks2.Block: 
Configuration:  []  
  
CryptoBackingDevice:'/' 
  
Device: /dev/sr0

...
HintAuto:   true
HintIconName:   
HintIgnore: false   
HintName:   
HintPartitionable:  false 
HintSymbolicIconName:
HintSystem: true
Id: by-uuid-2019-06-22-02-06-15-00
...
UserspaceMountOptions:  uhelper=udisks2
  org.freedesktop.UDisks2.Filesystem:
MountPoints:/media/tj/Xubuntu 19.10 amd64
Size:   0

$ mount | grep media/tj
/dev/sr0 on /media/tj/Xubuntu 19.10 amd64 type iso9660 
(ro,nosuid,nodev,relatime,nojoliet,check=s,map=n,blocksize=2048,uid=1000,gid=1000,dmode=500,fmode=400,u
helper=udisks2)


[0] 
http://storaged.org/doc/udisks2-api/latest/gdbus-org.freedesktop.UDisks2.Block.html#gdbus-property-org-freedesktop-UDisks2-Block.HintSystem

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

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

Title:
  Ignores HintSystem (UDISKS_SYSTEM)

Status in udisks2 package in Ubuntu:
  New

Bug description:
  [18.04 amd64]

  HintSystem (which can be set by a udev rule with
  ENV{UDISKS_SYSTEM}="1") is supposed to "require additional permissions
  to access" [0] but there is no difference in the mount permissions
  when it is set:

  # UDISKS_SYSTEM=0

  $ udisksctl info -b /dev/sr0  
   
/org/freedesktop/UDisks2/block_devices/sr0: 
  
org.freedesktop.UDisks2.Block:  

  Configuration:  []

  CryptoBackingDevice:'/'   

  Device: /dev/sr0  

  ...
  HintAuto:

[Desktop-packages] [Bug 1832988] Re: Intel 8260 Bluetooth not working

[MAshby]

I re-installed the default kernel using the following command:
$ sudo apt install --reinstall linux-image-5.0.0-20-generic
then installed the latest linux-firmware as directed above,
and now bluetooth is broken again, same as before. I guess this means that your 
fix is required Kai-Heng. 

Thanks for the assistance

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

Title:
  Intel 8260 Bluetooth not working

Status in gnome-bluetooth package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Expected behaviour:
  I can enable bluetooth in the system settings, and pair with my other devices.

  Actual behaviour:
  Always displays as 'off' in the settings dialog, and won't turn on. 

  Bluetooth worked on the same machine with previous Ubuntu releases
  (18.10) & no hardware changes.

  "dmesg | grep -i bluetooth" reports the following:
  ```
  [   14.445902] Bluetooth: Core ver 2.22
  [   14.445918] Bluetooth: HCI device and connection manager initialized
  [   14.445921] Bluetooth: HCI socket layer initialized
  [   14.445923] Bluetooth: L2CAP socket layer initialized
  [   14.445929] Bluetooth: SCO socket layer initialized
  [   14.494345] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
  [   14.499050] Bluetooth: hci0: Device revision is 5
  [   14.499052] Bluetooth: hci0: Secure boot is enabled
  [   14.499053] Bluetooth: hci0: OTP lock is enabled
  [   14.499053] Bluetooth: hci0: API lock is enabled
  [   14.499054] Bluetooth: hci0: Debug lock is disabled
  [   14.499055] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [   14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
  [   14.558347] Bluetooth: hci0: Failed to send firmware data (-38)
  [   15.497805] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   15.497806] Bluetooth: BNEP filters: protocol multicast
  [   15.497810] Bluetooth: BNEP socket layer initialized
  ```

  "lsb_release -rd" reports the following:
  ```
  Description:  Ubuntu 19.04
  Release:  19.04
  ```
  "cat /proc/version_signature" reports the following:
  ```
  Ubuntu 5.0.0-16.17-generic 5.0.8
  ```

  "apt-cache policy linux-firmware" reports the following:
  ```
  linux-firmware:
Installed: 1.178.1
Candidate: 1.178.1
Version table:
   *** 1.178.1 500
  500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 
Packages
  500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu disco-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu disco-security/main i386 
Packages
  100 /var/lib/dpkg/status
   1.178 500
  500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu disco/main i386 Packages
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-16-generic 5.0.0-16.17
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 2314 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 16 12:31:07 2019
  InstallationDate: Installed on 2019-06-02 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 003: ID 5986:066d Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: PC Specialist Limited N15_17RD
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-16-generic N/A
   linux-backports-modules-5.0.0-16-generic  N/A
   linux-firmware1.178.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N15_17RD
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.11:bd12/25/2015:svnPCSpecialistLimited:pnN15_17RD:pvrNotApplicable:rvnCLEVO:rnN15_17RD:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N15_17RD
  dmi.product.sku: Not Applicable
  

[Desktop-packages] [Bug 1832988] Re: Intel 8260 Bluetooth not working

[Kai-Heng Feng]

The custom kernel has a fix for this particular issue. Please use the
default kernel to test latest firmware.

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

Title:
  Intel 8260 Bluetooth not working

Status in gnome-bluetooth package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Expected behaviour:
  I can enable bluetooth in the system settings, and pair with my other devices.

  Actual behaviour:
  Always displays as 'off' in the settings dialog, and won't turn on. 

  Bluetooth worked on the same machine with previous Ubuntu releases
  (18.10) & no hardware changes.

  "dmesg | grep -i bluetooth" reports the following:
  ```
  [   14.445902] Bluetooth: Core ver 2.22
  [   14.445918] Bluetooth: HCI device and connection manager initialized
  [   14.445921] Bluetooth: HCI socket layer initialized
  [   14.445923] Bluetooth: L2CAP socket layer initialized
  [   14.445929] Bluetooth: SCO socket layer initialized
  [   14.494345] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
  [   14.499050] Bluetooth: hci0: Device revision is 5
  [   14.499052] Bluetooth: hci0: Secure boot is enabled
  [   14.499053] Bluetooth: hci0: OTP lock is enabled
  [   14.499053] Bluetooth: hci0: API lock is enabled
  [   14.499054] Bluetooth: hci0: Debug lock is disabled
  [   14.499055] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [   14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
  [   14.558347] Bluetooth: hci0: Failed to send firmware data (-38)
  [   15.497805] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   15.497806] Bluetooth: BNEP filters: protocol multicast
  [   15.497810] Bluetooth: BNEP socket layer initialized
  ```

  "lsb_release -rd" reports the following:
  ```
  Description:  Ubuntu 19.04
  Release:  19.04
  ```
  "cat /proc/version_signature" reports the following:
  ```
  Ubuntu 5.0.0-16.17-generic 5.0.8
  ```

  "apt-cache policy linux-firmware" reports the following:
  ```
  linux-firmware:
Installed: 1.178.1
Candidate: 1.178.1
Version table:
   *** 1.178.1 500
  500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 
Packages
  500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu disco-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu disco-security/main i386 
Packages
  100 /var/lib/dpkg/status
   1.178 500
  500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu disco/main i386 Packages
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-16-generic 5.0.0-16.17
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 2314 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 16 12:31:07 2019
  InstallationDate: Installed on 2019-06-02 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 003: ID 5986:066d Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: PC Specialist Limited N15_17RD
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-16-generic N/A
   linux-backports-modules-5.0.0-16-generic  N/A
   linux-firmware1.178.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N15_17RD
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.11:bd12/25/2015:svnPCSpecialistLimited:pnN15_17RD:pvrNotApplicable:rvnCLEVO:rnN15_17RD:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N15_17RD
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

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

-- 

[Desktop-packages] [Bug 1832988] Re: Intel 8260 Bluetooth not working

[MAshby]

Thanks Kai-Heng, 
I installed the latest firmware as you described and bluetooth works. 
Please note I didn't uninstall the custom kernel from before. I don't know if 
this matters.

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

Title:
  Intel 8260 Bluetooth not working

Status in gnome-bluetooth package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Expected behaviour:
  I can enable bluetooth in the system settings, and pair with my other devices.

  Actual behaviour:
  Always displays as 'off' in the settings dialog, and won't turn on. 

  Bluetooth worked on the same machine with previous Ubuntu releases
  (18.10) & no hardware changes.

  "dmesg | grep -i bluetooth" reports the following:
  ```
  [   14.445902] Bluetooth: Core ver 2.22
  [   14.445918] Bluetooth: HCI device and connection manager initialized
  [   14.445921] Bluetooth: HCI socket layer initialized
  [   14.445923] Bluetooth: L2CAP socket layer initialized
  [   14.445929] Bluetooth: SCO socket layer initialized
  [   14.494345] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
  [   14.499050] Bluetooth: hci0: Device revision is 5
  [   14.499052] Bluetooth: hci0: Secure boot is enabled
  [   14.499053] Bluetooth: hci0: OTP lock is enabled
  [   14.499053] Bluetooth: hci0: API lock is enabled
  [   14.499054] Bluetooth: hci0: Debug lock is disabled
  [   14.499055] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [   14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
  [   14.558347] Bluetooth: hci0: Failed to send firmware data (-38)
  [   15.497805] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   15.497806] Bluetooth: BNEP filters: protocol multicast
  [   15.497810] Bluetooth: BNEP socket layer initialized
  ```

  "lsb_release -rd" reports the following:
  ```
  Description:  Ubuntu 19.04
  Release:  19.04
  ```
  "cat /proc/version_signature" reports the following:
  ```
  Ubuntu 5.0.0-16.17-generic 5.0.8
  ```

  "apt-cache policy linux-firmware" reports the following:
  ```
  linux-firmware:
Installed: 1.178.1
Candidate: 1.178.1
Version table:
   *** 1.178.1 500
  500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 
Packages
  500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu disco-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu disco-security/main i386 
Packages
  100 /var/lib/dpkg/status
   1.178 500
  500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu disco/main i386 Packages
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-16-generic 5.0.0-16.17
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 2314 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 16 12:31:07 2019
  InstallationDate: Installed on 2019-06-02 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 003: ID 5986:066d Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: PC Specialist Limited N15_17RD
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-16-generic N/A
   linux-backports-modules-5.0.0-16-generic  N/A
   linux-firmware1.178.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N15_17RD
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.11:bd12/25/2015:svnPCSpecialistLimited:pnN15_17RD:pvrNotApplicable:rvnCLEVO:rnN15_17RD:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N15_17RD
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1787974] Re: Fingerprint authentication not available in 18.04

[Gunnar Hjalmarsson]

Note that the URL

https://help.ubuntu.com/stable/ubuntu-help/session-fingerprint.html

refers to the latest stable release (currently Ubuntu 19.04)

The URLs to the 18.04 docs is:

https://help.ubuntu.com/lts/ubuntu-help/session-fingerprint.html

or

https://help.ubuntu.com/18.04/ubuntu-help/session-fingerprint.html

Now that doesn't help; apparently the 18.04 docs is a bit insufficient
for 18.04. However, it would be too much work to go back and change the
18.04 docs, so closing.

@Mustafa: If you have problems to make it work, it's probably a support
matter or a bug against some other package, i.e. not a docs bug. You may
want to ask a question at e.g.  to get help and
find out.

** Package changed: ubuntu-docs (Ubuntu) => gnome-user-docs (Ubuntu)

** Changed in: gnome-user-docs (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Fingerprint authentication not available in 18.04

Status in gnome-user-docs package in Ubuntu:
  Won't Fix

Bug description:
  This page describes a feature not found in 18.04

  https://help.ubuntu.com/stable/ubuntu-help/session-fingerprint.html.en

  Starting from point 3. "Press on Disabled, next to Fingerprint Login
  to add a fingerprint for the selected account. If you are adding the
  fingerprint for a different user, you will first need to Unlock the
  panel." The option "Fingerprint Login" isn't available in the GUI (not
  displayed at all).

  The following steps to enroll fingers are therefore missing as well.

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

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

[Desktop-packages] [Bug 1787974] [NEW] Fingerprint authentication not available in 18.04

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

This page describes a feature not found in 18.04

https://help.ubuntu.com/stable/ubuntu-help/session-fingerprint.html.en

Starting from point 3. "Press on Disabled, next to Fingerprint Login to
add a fingerprint for the selected account. If you are adding the
fingerprint for a different user, you will first need to Unlock the
panel." The option "Fingerprint Login" isn't available in the GUI (not
displayed at all).

The following steps to enroll fingers are therefore missing as well.

** Affects: gnome-user-docs (Ubuntu)
 Importance: Low
 Status: Confirmed

-- 
Fingerprint authentication not available in 18.04
https://bugs.launchpad.net/bugs/1787974
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-user-docs in Ubuntu.

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

[Desktop-packages] [Bug 1743247] Re: B2 Python APIs are missing

[Kenneth Loafman]

** Changed in: duplicity
Milestone: 0.8.01 => None

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

Title:
  B2 Python APIs are missing

Status in Duplicity:
  In Progress
Status in duplicity package in Ubuntu:
  Confirmed

Bug description:
  When I try to use the B2 backend with
  0.7.16-0ubuntu1ppa1347~ubuntu16.04.1, I get the following error:

  > BackendException: B2 backend requires B2 Python APIs (pip install
  b2)

  It seems odd to me that the library would be installed outside of apt.
  I had an old package from trusty
  (duplicity_0.7.14-0ubuntu0ppa1316~ubuntu14.04.1_amd64.deb) with 0.7.14
  which works fine on 16.04, which makes me think this regression was in
  0.7.15 or 0.7.16.

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

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

[Desktop-packages] [Bug 1666432] Re: Internet drops every few minutes on wired and wireless connection

[Tom Reynolds]

Hi.

I am just a fellow Ubuntu user, but I am afraid this bug report is most
likely not something anyone could solve, because so many different
chipsets and issues are being discussed here (I assume this is also why
no developers felt inclined to touch it so far).

I very much recommend that anyone still experiencing wireless issues should 
(look for, and if none exists) file a new bug against their wireless driver, 
and anyone with Ethernet issues should (look for, and if none exists) file a 
new bug against their Ethernet driver. Your drivers will usually be listed in 
the output of one of these commands:
lspci -knn
lsusb

You are also welcome to check back with community support to check whether a 
fix (or a workaround) is already available for your very issue, or just to get 
help with filing a bug report that is specific and can get handled more easily. 
https://ubuntu.com/support/community-support

If TylerKinkade's issue (where both Wireless and Ethernet disconnect at
the same time, on a now supported Ubuntu version) persists then it is
more likely a platform (hardware / mainboard / ACPI / firmware) specific
issue and should be treated as such, affecting Inspiron 5567 with this
specific Ubuntu version (was 16.04.1 originally).

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

Title:
  Internet drops every few minutes on wired and wireless connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Internet drops every 1-30 minutes when connected via wired or wireless
  (i.e., this is a problem on both wired and wireless) even though
  connection icon indicates the computer is still connected.

  Disconnecting and reconnecting via the connection icon resets internet
  temporarily until the next time.

  Dropped internet is discovered with "The site can't be reached"
  screens in Chromium, or error messages when downloading/updating in
  Terminal, or missing connection in Ubuntu Software app, or stalled
  syncing in Insync application (occurred even without Insync).

  Internet drops more frequently on wireless than on wired.

  It seems to disconnect more frequently with heavier internet use
  (e.g., downloading multiple files, opening several webpages in quick
  succession).

  This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron
  15 5567 (dual boot). It occurs when running Live CD as well though.

  Ethernet and wifi both work without randomly disconnecting in Windows
  10 on the same machine, and ethernet and wifi work on other machines
  running Ubuntu and Windows with the same router, so it is not a
  hardware or router issue.

  Output from sudo lshw -class network

  *-network
     description: Wireless interface
     product: Wireless 3165
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:02:00.0
     logical name: wlp2s0
     version: 79
     serial: 58:fb:84:55:21:52
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 
link=yes multicast=yes wireless=IEEE 802.11abgn
     resources: irq:283 memory:df10-df101fff
    *-network
     description: Ethernet interface
     product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
     vendor: Realtek Semiconductor Co., Ltd.
     physical id: 0
     bus info: pci@:03:00.0
     logical name: enp3s0
     version: 07
     serial: 18:db:f2:3c:d5:37
     size: 10Mbit/s
     capacity: 100Mbit/s
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
     resources: irq:279 ioport:d000(size=256) memory:df00-df000fff 
memory:d030-d0303fff

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 21 16:36:55 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-02-20 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0  proto static  metric 600
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000
   

[Desktop-packages] [Bug 1177381] Re: Duplicity can't find its own tempdir

[Kenneth Loafman]

** Changed in: duplicity
Milestone: 0.8.01 => None

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

Title:
  Duplicity can't find its own tempdir

Status in Duplicity:
  In Progress
Status in duplicity package in Ubuntu:
  Confirmed

Bug description:
  My backups have been working normally for months, but today they
  failed with this error:

  Failed with an unknown error:
  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1411, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1404, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1386, in main
  incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 581, in incremental_backup
  globals.backend)
File "/usr/bin/duplicity", line 394, in write_multivol
  vi.set_hash("SHA1", gpg.get_hash("SHA1", tdp))
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 401, in 
get_hash
  fp = path.open("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 542, in open
  result = open(self.name, mode)
  IOError: [Errno 2] No such file or directory: 
'/tmp/duplicity-rWgqMw-tempdir/mktemp-fvN6e5-5'

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: deja-dup 26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Tue May  7 09:12:25 2013
  InstallationDate: Installed on 2010-09-17 (962 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to raring on 2013-01-25 (101 days ago)

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

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

[Desktop-packages] [Bug 1835467] Re: Repeatingly looking for the next occurrence of a word search in a webpage misses one occurrence.

[Martin Constantino–Bodin]

There have been a system update recently (I’m now in Firefox 67.0.4 (64
bits)), so I tried to reproduce the bug on the new version.  I’m sorry
to say that it is still present, with the same characteristics
(“addEventListener” missing the third occurrence, and “function” missing
the 8th, 13th, and 16th occurrences).  (The importance of the bug hasn’t
increase in any way, of course: it’s still a minor bug.)

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

Title:
  Repeatingly looking for the next occurrence of a word search in a
  webpage misses one occurrence.

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  This is probably the most unexpected bug that I have ever seen. Fortunately, 
it is benign.

  How to reproduce:
  - Go to the webpage https://www.w3schools.com/howto/howto_js_autocomplete.asp
  - Type Ctrl+f to look for a word through the webpage.
  - Search for addEventListener. Firefox successfully found 4 occurrences on 
the webpage.
  - Using the arrows next to the search box, loop through all occurrences. 
Firefox then jumps to the following occurrences, in order:
  1. inp.addEventListener("input", function(e) {
  2. b.addEventListener("click", function(e) {
  3. inp.addEventListener("keydown", function(e) { (In my screen is, it was 
hidden by the message about cookies: scrolling down by 1cm makes it appear.)
  4. document.addEventListener("click", function (e) {
  5. First occurrence again: inp.addEventListener("input", function(e) {
  6. Second occurrence again: b.addEventListener("click", function(e) {
  7. Firefox then directly jumps to the fourth occurrence, missing the third 
one: document.addEventListener("click", function (e) {
  8. (goes back to 5).

  In other words, although the first cycle through all occurrences was
  correct, the following cycles completely miss the third occurrence! I
  have restarted Firefox and still get this behaviour.

  If instead of clicking on the “down” arrow to look for the second
  occurrence one looks backwards with the “up” arrow, then it is
  “b.addEventListener("click", function(e) {” instead of
  “inp.addEventListener("keydown", function(e) {” which is missing from
  the loop: it seems that whenever cycling through all occurrences of a
  search in a webpage, if there are only four occurrences, then the
  third one is never reached except in the first cycle.

  I am sending a screenshot of the situation.

  This is a very unexpected behaviour, but of very minor consequence:
  there is no need to place a high level of importance for this bug, I
  guess.

  Regards,
  Martin.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 67.0.4+build1-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic x86_64
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-54-generic.
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC233 Analog [ALC233 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 1585 F pulseaudio
  BuildID: 20190620092152
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x9091 irq 95'
     Mixer name : 'Realtek ALC233'
     Components : 'HDA:10ec0235,17aa3825,0012 
HDA:80862882,80860101,0010'
     Controls  : 33
     Simple ctrls  : 14
  Channel: Unavailable
  CurrentDesktop: LXDE
  Date: Thu Jul  4 23:24:35 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-12-05 (941 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  IpRoute:
   default via 192.168.1.1 dev wlp4s0 proto dhcp metric 600
   192.168.1.0/24 dev wlp4s0 proto kernel scope link src 192.168.1.3 metric 600
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-7e1f310f-034d-4a7b-b742-54df41180319
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:1151
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=67.0.4/20190620092152 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-7e1f310f-034d-4a7b-b742-54df41180319
   bp-daebd85b-34c2-4ab9-88ea-1fc091180208
   bp-dd2282e2-f0cb-47f7-a13a-a16c20180102
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: 

[Desktop-packages] [Bug 1836481] [NEW] Every Backup Is A Complete Backup

[Stephen Allen]

Public bug reported:

The past couple of weeks, the following issue has occurred. Despite the 1st 
backup being done quite some time ago, recently the application asks for my 
password each time it runs, as it is creating a NEW backup, instead of 
appending to the existing.
This is very problematic as it often takes longer than 24hrs to complete.

I'm using Google Drive as my backup storage.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: duplicity 0.7.18.2-1ubuntu3.1
Uname: Linux 5.2.0-050200rc7-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Jul 14 08:53:11 2019
InstallationDate: Installed on 2019-02-23 (140 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco wayland-session

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

Title:
  Every Backup Is A Complete Backup

Status in duplicity package in Ubuntu:
  New

Bug description:
  The past couple of weeks, the following issue has occurred. Despite the 1st 
backup being done quite some time ago, recently the application asks for my 
password each time it runs, as it is creating a NEW backup, instead of 
appending to the existing.
  This is very problematic as it often takes longer than 24hrs to complete.

  I'm using Google Drive as my backup storage.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: duplicity 0.7.18.2-1ubuntu3.1
  Uname: Linux 5.2.0-050200rc7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jul 14 08:53:11 2019
  InstallationDate: Installed on 2019-02-23 (140 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1828393] Re: Unable to use bluetooth headset with mic and a2dp audio

[Eric Wild]

This is not a duplicate bug, bug 508522 covers automatic switching of
profiles since a2dp and hsp/hfp are mutually exclusive, there can not be
two profiles active at the same time.

The true bug here is the bad voice quality, which is caused by a lack of
codec negotiation. This is why bluetooth headsets will sound better
connected to a random (> 4.4) android phone, which will negotiate mSBC,
also known as "wide band speech", supported since HFP 1.6. This can be
mistaken for "a2dp and microphone active at the same time", even though
it is still a monaural configuration not related to a2dp, because it
sounds so much better.

The HSP/HFP mode is using the CVSD codec which sounds like a bad gsm
call, there have been attempts to merge proper codec negotiaton, but the
work has stalled for some reason - see the related thread at
https://www.spinics.net/lists/pulse-audio/msg29370.html and the stale
patchset at https://patchwork.freedesktop.org/series/30716/

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

Title:
  Unable to use bluetooth headset with mic and a2dp audio

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Every device supports high fidelity audio while using headset with
  mic. This needs to enable two profiles at once: headset_head_unit and
  a2dp_sink. Right now this is impossible and I need to switch between
  profiles when listening to music and joining a call. In any case, the
  sound quality of HSP/HFP used in the headset_head_unit profile is
  horrible to have a call.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  9 13:20:26 2019
  InstallationDate: Installed on 2018-11-20 (169 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET35W (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET35W(1.17):bd12/21/2018:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1828393] Re: Unable to use bluetooth headset with mic and a2dp audio

[Eric Wild]

** This bug is no longer a duplicate of bug 508522
   Mic is not available with A2DP Bluetooth profile

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

Title:
  Unable to use bluetooth headset with mic and a2dp audio

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Every device supports high fidelity audio while using headset with
  mic. This needs to enable two profiles at once: headset_head_unit and
  a2dp_sink. Right now this is impossible and I need to switch between
  profiles when listening to music and joining a call. In any case, the
  sound quality of HSP/HFP used in the headset_head_unit profile is
  horrible to have a call.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  9 13:20:26 2019
  InstallationDate: Installed on 2018-11-20 (169 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET35W (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET35W(1.17):bd12/21/2018:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1834566] Re: Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel - Realtek ALC298

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel
  - Realtek ALC298

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Unable to get system speakers working running 19.04.  At max volume,
  sound is barely perceptible through headphones.  Pavucontrol shows
  sounds is present, but no amount of adjustments makes a difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robert 3355 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun 28 00:44:13 2019
  InstallationDate: Installed on 2019-06-05 (22 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [930MBE, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02AHK.029.190425.PS
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP930MBE-K04US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9872A0S-C01-G001-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02AHK.029.190425.PS:bd04/25/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn930MBE:pvrP02AHK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP930MBE-K04US:rvrSGL9872A0S-C01-G001-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A:
  dmi.product.family: Notebook 9 Series
  dmi.product.name: 930MBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAHK
  dmi.product.version: P02AHK
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Desktop-packages] [Bug 1807056] Re: Occasional Keyboard freeze

[Dilip]

I found a new issue within this bug. At times, the mouse right-click
does not show any menu at all. Clicking on the dash search box fixes it
though.

At first, I thought I was trying to copy or paste ( my intended action )
on a folder on which I had no permission. But when the dash search box
typing issue fixed it, I thought of reporting here.

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

Title:
  Occasional Keyboard freeze

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/907

  ---

  I am using 18.04 and sometimes, whatever I type does not work. It is
  as if there is no keyboard connected while I have my laptop keyboard
  and an external keyboard connected to the machine. I even enabled On
  Screen Keyboard and tried to type through it. Same result.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Thu Dec  6 05:41:04 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-11-29 (6 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1178272] Re: Lubuntu: banshee, rhythmbox, etc cannot play audio without pulseaudio or gstreamer1.0-alsa

[Rüdiger Kupper]

Hello Chris Guiver,
I am not currently using Lubuntu on any device, so I cannot easily test if the 
problem still exists. User deutrino could have more information.

@deutrino: Has the bug reached attention upstream? Is it still present
in recent Lubuntu installs?

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

Title:
  Lubuntu: banshee, rhythmbox, etc cannot play audio without pulseaudio
  or gstreamer1.0-alsa

Status in banshee package in Ubuntu:
  Invalid
Status in gstreamer0.10 package in Ubuntu:
  Incomplete
Status in gstreamer1.0 package in Ubuntu:
  New
Status in lubuntu-meta package in Ubuntu:
  Incomplete
Status in rhythmbox package in Ubuntu:
  Invalid

Bug description:
  Lubuntu Raring (13.04).
  The Lubuntu standard installation comes without jack, and without pulse, just 
plain alsa. Gstreamer applications (rhythmbox, banshee) used to work fine after 
installing "ubuntu-restricted-extras", which pulls in the usual gstreamer 
plugins.
  On my system, gstreamer applications stopped working. They report:
  > Cannot connect to server socket err = No such file or directory
  > Cannot connect to server request channel
  > jack server is not running or cannot be started
  Since there is no jack on this system, never was, and is not intended to be 
there, I cannot understand this message. The applications do not produce sound.

  This looks like gstreamer tries to start up jackd, regardless whether
  it is installed or not.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libgstreamer0.10-0 0.10.36-1ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Thu May  9 15:38:20 2013
  InstallationDate: Installed on 2013-02-12 (85 days ago)
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1)
  MarkForUpload: True
  SourcePackage: gstreamer0.10
  UpgradeStatus: Upgraded to raring on 2013-04-25 (13 days ago)

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

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

[Desktop-packages] [Bug 1834795] Re: xubuntu ethernet does not reconnect unless computer restarted, after power off/on modem or manually off/on "enable networking"

[H]

- Logs begin at Wed 2019-07-10 19:00:46 BST, end at Sat 2019-07-13 05:18:08 
BST. --
Jul 13 05:07:50 mbox kernel: Linux version 4.18.0-25-generic 
(buildd@lgw01-amd64-033) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) 
#26~18.04.1-Ubuntu SMP Thu Jun 27 07:28:31 UTC 2019 (U
Jul 13 05:07:50 mbox kernel: Command line: 
BOOT_IMAGE=/vmlinuz-4.18.0-25-generic root=/dev/mapper/xubuntu--vg-root ro 
quiet splash vt.handoff=1
Jul 13 05:07:50 mbox kernel: KERNEL supported cpus:
Jul 13 05:07:50 mbox kernel:   Intel GenuineIntel
Jul 13 05:07:50 mbox kernel:   AMD AuthenticAMD
Jul 13 05:07:50 mbox kernel:   Centaur CentaurHauls
Jul 13 05:07:50 mbox kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 
floating point registers'
Jul 13 05:07:50 mbox kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE 
registers'
Jul 13 05:07:50 mbox kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX 
registers'
Jul 13 05:07:50 mbox kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  
256
Jul 13 05:07:50 mbox kernel: x86/fpu: Enabled xstate features 0x7, context size 
is 832 bytes, using 'standard' format.
Jul 13 05:07:50 mbox kernel: BIOS-provided physical RAM map:
Jul 13 05:07:50 mbox kernel: BIOS-e820: [mem 
0x-0x0009d7ff] usable
Jul 13 05:07:50 mbox kernel: BIOS-e820: [mem 
0x0009d800-0x0009] reserved
Jul 13 05:07:50 mbox kernel: BIOS-e820: [mem 
0x000e-0x000f] reserved
Jul 13 05:07:50 mbox kernel: BIOS-e820: [mem 
0x0010-0x1fff] usable
Jul 13 05:07:50 mbox kernel: BIOS-e820: [mem 
0x2000-0x201f] reserved
Jul 13 05:07:50 mbox kernel: BIOS-e820: [mem 
0x2020-0x40003fff] usable
Jul 13 05:07:50 mbox kernel: BIOS-e820: [mem 
0x40004000-0x40004fff] reserved
Jul 13 05:07:50 mbox kernel: BIOS-e820: [mem 
0x40005000-0x9bfa6fff] usable
Jul 13 05:07:50 mbox kernel: BIOS-e820: [mem 
0x9bfa7000-0x9c2cbfff] reserved
Jul 13 05:07:50 mbox kernel: BIOS-e820: [mem 
0x9c2cc000-0x9c2dbfff] ACPI data
Jul 13 05:07:50 mbox kernel: BIOS-e820: [mem 
0x9c2dc000-0x9c3f1fff] ACPI NVS
Jul 13 05:07:50 mbox kernel: BIOS-e820: [mem 
0x9c3f2000-0x9c68efff] reserved
Jul 13 05:07:50 mbox kernel: BIOS-e820: [mem 
0x9c68f000-0x9c68] usable
Jul 13 05:07:50 mbox kernel: BIOS-e820: [mem 
0x9c69-0x9c6d2fff] ACPI NVS
Jul 13 05:07:50 mbox kernel: BIOS-e820: [mem 
0x9c6d3000-0x9cff] usable
Jul 13 05:07:50 mbox kernel: BIOS-e820: [mem 
0x9d00-0x9f9f] reserved
Jul 13 05:07:50 mbox kernel: BIOS-e820: [mem 
0xf800-0xfbff] reserved
Jul 13 05:07:50 mbox kernel: BIOS-e820: [mem 
0xfec0-0xfec00fff] reserved
Jul 13 05:07:50 mbox kernel: BIOS-e820: [mem 
0xfed0-0xfed03fff] reserved
Jul 13 05:07:50 mbox kernel: BIOS-e820: [mem 
0xfed1c000-0xfed1] reserved
Jul 13 05:07:50 mbox kernel: BIOS-e820: [mem 
0xfee0-0xfee00fff] reserved
Jul 13 05:07:50 mbox kernel: BIOS-e820: [mem 
0xff00-0x] reserved
Jul 13 05:07:50 mbox kernel: BIOS-e820: [mem 
0x0001-0x00025f5f] usable
Jul 13 05:07:50 mbox kernel: NX (Execute Disable) protection: active
Jul 13 05:07:50 mbox kernel: SMBIOS 2.7 present.
Jul 13 05:07:50 mbox kernel: DMI:  /D33217CK, BIOS 
GKPPT10H.86A.0067.2019.0522.1041 05/22/2019
Jul 13 05:07:50 mbox kernel: e820: update [mem 0x-0x0fff] usable 
==> reserved
Jul 13 05:07:50 mbox kernel: e820: remove [mem 0x000a-0x000f] usable
Jul 13 05:07:50 mbox kernel: last_pfn = 0x25f600 max_arch_pfn = 0x4
Jul 13 05:07:50 mbox kernel: MTRR default type: uncachable
Jul 13 05:07:50 mbox kernel: MTRR fixed ranges enabled:
Jul 13 05:07:50 mbox kernel:   0-9 write-back

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

Title:
  xubuntu ethernet does not reconnect unless computer restarted, after
  power off/on modem or manually off/on "enable networking"

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Xubuntu 19.04, 64bit, encrypted drive, using a desktop computer with
  ethernet to connect. Connects fine. Use openvpn also (from terminal).
  When the modem is turned off and on, or when the modem remains on but
  the ethernet connection is disabled (by unticking) and then ticking
  again "enable networking" in the applet taskbar, the connection does
  not re-establish. This is irregardless of the vpn, which even if i
  turn off, will not affect the lack of reconnection.

  If i ping bing.com, after trying to reconnect, I get back one
  response, but no multiple responses.

  ping bing.com
  PING bing.com (204.79.197.200) 56(84) bytes of data.

  

[Desktop-packages] [Bug 1761913] Re: gnome-software crashed with SIGABRT in g_assertion_message_error → ensure_surface_for_gicon → gtk_icon_helper_load_surface → gtk_icon_helper_ensure_surface → gtk_i

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1627564
   Crash due to assertion failure in ensure_surface_for_gicon 
[gtkiconhelper.c:493] (when png loader is missing/during upgrades)

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

Title:
  gnome-software crashed with SIGABRT in g_assertion_message_error →
  ensure_surface_for_gicon → gtk_icon_helper_load_surface →
  gtk_icon_helper_ensure_surface → gtk_icon_helper_ensure_surface →
  _gtk_icon_helper_get_size → gtk_image_get_content_size

Status in gnome-software package in Ubuntu:
  New

Bug description:
  testing ubuntu 18.04, this error popped up while NOT using gnome-
  software...

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.0-0ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  7 11:52:45 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-04-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu7
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-software
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_error () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: gnome-software crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1819079] Re: /usr/lib/gcr/gcr-prompter:6:g_assertion_message:g_assertion_message_error:ensure_surface_for_gicon:gtk_icon_helper_load_surface:gtk_icon_helper_ensure_surface

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1627564
   Crash due to assertion failure in ensure_surface_for_gicon 
[gtkiconhelper.c:493] (when png loader is missing/during upgrades)

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

Title:
  /usr/lib/gcr/gcr-
  
prompter:6:g_assertion_message:g_assertion_message_error:ensure_surface_for_gicon:gtk_icon_helper_load_surface:gtk_icon_helper_ensure_surface

Status in gcr package in Ubuntu:
  New

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

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

[Desktop-packages] [Bug 1400036] Re: libvte9 shouldn't depend on libpango1.0-0 as it's a transitional package

[Vlad Orlov]

** No longer affects: vte (Debian)

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

Title:
  libvte9 shouldn't depend on libpango1.0-0 as it's a transitional
  package

Status in vte package in Ubuntu:
  Fix Released

Bug description:
  libvte9 should depend on libpango-1.0-0 instead of libpango1.0-0

  libpango1.0-0 is a transitional package.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libvte9 1:0.28.2-5ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-41.70-generic 3.13.11.11
  Uname: Linux 3.13.0-41-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Dec  7 02:39:58 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-11-01 (766 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: vte
  UpgradeStatus: Upgraded to trusty on 2014-09-04 (94 days ago)

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

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