[Desktop-packages] [Bug 1841024] Re: sreen captured

[Daniel van Vugt]

It sounds like your PrtSc (print screen) key might be getting stuck.

Please try tapping it a few times to unstick it, or using something flat
to lever it back up.

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

** 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 xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1841024

Title:
  sreen captured

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The system begins to make screen captures without stopping, making it
  impossible to use to the point of crashing the system and making a
  stressful noise.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 22 01:36:22 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1019:995b]
 Subsystem: Elitegroup Computer Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1019:995b]
  MachineType: Semp Toshiba IS 1414
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic 
root=UUID=fbbaea76-1d2d-4b24-850f-cb5685d71e24 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2010
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: MTVNCRB01.86C..X.00
  dmi.board.name: IS 1414
  dmi.board.vendor: Semp Toshiba
  dmi.board.version: CRB
  dmi.chassis.type: 10
  dmi.chassis.vendor: Semp Toshiba
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrMTVNCRB01.86C..X.00:bd05/07/2010:svnSempToshiba:pnIS1414:pvr20ga:rvnSempToshiba:rnIS1414:rvrCRB:cvnSempToshiba:ct10:cvr:
  dmi.product.name: IS 1414
  dmi.product.version: 20ga & ICH9M Chipset
  dmi.sys.vendor: Semp Toshiba
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1841023] [NEW] [Strix 15 GL503GE, Realtek ALC295, Black Headphone Out, Left] No sound at all

[Iqbal Rofindi]

Public bug reported:

sometimes headphone working, but sometimes are not working
if not working, im restart my laptop, sometimes fix this problem, but sometimes 
are not fix

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
Uname: Linux 5.0.0-25-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  sycloner  11744 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 22 11:42:04 2019
InstallationDate: Installed on 2019-08-14 (7 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
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_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  sycloner  11744 F pulseaudio
Symptom_Jack: Black Headphone Out, Left
Symptom_Type: No sound at all
Title: [Strix 15 GL503GE, Realtek ALC295, Black Headphone Out, Left] No sound 
at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/19/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GL503GE.316
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GL503GE
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No  Asset  Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL503GE.316:bd07/19/2019:svnASUSTeKCOMPUTERINC.:pnStrix15GL503GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503GE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: Strix
dmi.product.name: Strix 15 GL503GE
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug bionic

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

Title:
  [Strix 15 GL503GE, Realtek ALC295, Black Headphone Out, Left] No sound
  at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  sometimes headphone working, but sometimes are not working
  if not working, im restart my laptop, sometimes fix this problem, but 
sometimes are not fix

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sycloner  11744 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 22 11:42:04 2019
  InstallationDate: Installed on 2019-08-14 (7 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  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_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sycloner  11744 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [Strix 15 GL503GE, Realtek ALC295, Black Headphone Out, Left] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL503GE.316
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL503GE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL503GE.316:bd07/19/2019:svnASUSTeKCOMPUTERINC.:pnStrix15GL503GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503GE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: Strix
  dmi.product.name: Strix 15 GL503GE
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1841024] [NEW] sreen captured

[Muryllo Sirqueira Lopes dos Santos]

Public bug reported:

The system begins to make screen captures without stopping, making it
impossible to use to the point of crashing the system and making a
stressful noise.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
Uname: Linux 5.0.0-25-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 22 01:36:22 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Elitegroup Computer Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1019:995b]
   Subsystem: Elitegroup Computer Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1019:995b]
MachineType: Semp Toshiba IS 1414
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic 
root=UUID=fbbaea76-1d2d-4b24-850f-cb5685d71e24 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/07/2010
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: MTVNCRB01.86C..X.00
dmi.board.name: IS 1414
dmi.board.vendor: Semp Toshiba
dmi.board.version: CRB
dmi.chassis.type: 10
dmi.chassis.vendor: Semp Toshiba
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrMTVNCRB01.86C..X.00:bd05/07/2010:svnSempToshiba:pnIS1414:pvr20ga:rvnSempToshiba:rnIS1414:rvrCRB:cvnSempToshiba:ct10:cvr:
dmi.product.name: IS 1414
dmi.product.version: 20ga & ICH9M Chipset
dmi.sys.vendor: Semp Toshiba
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic corruption ubuntu

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

Title:
  sreen captured

Status in xorg package in Ubuntu:
  New

Bug description:
  The system begins to make screen captures without stopping, making it
  impossible to use to the point of crashing the system and making a
  stressful noise.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 22 01:36:22 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1019:995b]
 Subsystem: Elitegroup Computer Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1019:995b]
  MachineType: Semp Toshiba IS 1414
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic 
root=UUID=fbbaea76-1d2d-4b24-850f-cb5685d71e24 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2010
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: MTVNCRB01.86C..X.00
  dmi.board.name: IS 1414
  dmi.board.vendor: Semp Toshiba
  dmi.board.version: CRB
  dmi.chassis.type: 10
  dmi.chassis.vendor: Semp Toshiba
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrMTVNCRB01.86C..X.00:bd05/07/2010:svnSempToshiba:pnIS1414:pvr20ga:rvnSempToshiba:rnIS1414:rvrCRB:cvnSempToshiba:ct10:cvr:
  dmi.product.name: IS 1414
  dmi.product.version: 20ga & ICH9M Chipset
  dmi.sys.vendor: Semp Toshiba
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

[Desktop-packages] [Bug 1841018] Re: Unable to install Intel Latest Driver

[Chris Guiver]

The Ubuntu package xserver-xorg-video-intel-hwe-18.04 has different
requirements to that you listed in your message.

https://packages.ubuntu.com/bionic-updates/xserver-xorg-video-intel-
hwe-18.04  (it requires xorg-video-abi-24 not the -23 your message
reported)

Have you grabbed unofficial packages? or maybe check your mirror is up-
to-date (https://launchpad.net/ubuntu/+archivemirrors)  though Daniel's
prior comment may reveal some light..

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

Title:
  Unable to install Intel Latest Driver

Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  I was trying to install Intel's driver as the graphics keep freezing for 
couple of seconds, then continue to play...
  I used Terminal to install the graphics driver, But the error occured.
  >sudo apt-get install xserver-xorg-video-intel
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   xserver-xorg-video-intel : Depends: xorg-video-abi-23
  Depends: xserver-xorg-core (>= 2:1.18.99.901)
  E: Unable to correct problems, you have held broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 22 09:18:39 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2019-08-20 (1 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. Inspiron 3542
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-25-generic 
root=UUID=74b87668-96c3-4667-ad47-0905da0b45c2 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0C3NP7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A14
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0C3NP7:rvrA14:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.sku: 0651
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

Re: [Desktop-packages] [Bug 1840397] Re: do not display two screen

[Nguyen The Thuc]

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

Thank you so much

Vào Th 4, 21 thg 8, 2019 vào lúc 13:11 Daniel van Vugt <
daniel.van.v...@canonical.com> đã viết:

> *** This bug is a duplicate of bug 1840396 ***
> https://bugs.launchpad.net/bugs/1840396
>
> ** This bug has been marked a duplicate of bug 1840396
>do not display two screen
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1840397
>
> Title:
>   do not display two screen
>
> Status in xorg package in Ubuntu:
>   New
>
> Bug description:
>   maybe error drivers graphics for del
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.04
>   Package: xorg 1:7.7+19ubuntu12
>   ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
>   Uname: Linux 5.0.0-25-generic x86_64
>   ApportVersion: 2.20.10-0ubuntu27.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: Fri Aug 16 08:50:25 2019
>   DistUpgraded: 2019-06-26 14:49:28,001 ERROR Cache can not be locked (Can
> not lock '/var/lib/apt/lists/lock' )
>   DistroCodename: disco
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes
>   GraphicsCard:
>Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA
> controller])
>  Subsystem: Dell HD Graphics 620 [1028:078b]
>  Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430
> / R7 M520] [1028:078b]
>   InstallationDate: Installed on 2019-06-25 (51 days ago)
>   InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
> (20190210)
>   MachineType: Dell Inc. Inspiron 15-3567
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic
> root=UUID=981f9e6c-b414-4dbc-8a43-1e260574e929 ro quiet splash vt.handoff=1
>   SourcePackage: xorg
>   UpgradeStatus: Upgraded to disco on 2019-06-26 (50 days ago)
>   dmi.bios.date: 08/25/2017
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 2.0.3
>   dmi.board.vendor: Dell Inc.
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvr2.0.3:bd08/25/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
>   dmi.product.family: Inspiron
>   dmi.product.name: Inspiron 15-3567
>   dmi.product.sku: 078B
>   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.8-0ubuntu0~19.04.1
>   version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~19.04.1
>   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/xorg/+bug/1840397/+subscriptions
>

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

Title:
  do not display two screen

Status in xorg package in Ubuntu:
  New

Bug description:
  maybe error drivers graphics for del

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.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: Fri Aug 16 08:50:25 2019
  DistUpgraded: 2019-06-26 14:49:28,001 ERROR Cache can not be locked (Can not 
lock '/var/lib/apt/lists/lock' )
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:078b]
 Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 
M520] [1028:078b]
  InstallationDate: Installed on 2019-06-25 (51 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. Inspiron 15-3567
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic 
root=UUID=981f9e6c-b414-4dbc-8a43-1e260574e929 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to disco on 2019-06-26 (50 days ago)
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.0.3
  dmi.board.vendor: Dell Inc.
  

[Desktop-packages] [Bug 1841018] Re: Unable to install Intel Latest Driver

[Daniel van Vugt]

Could you please run:

  dpkg -l > allpackages.txt

and then attach the file 'allpackages.txt' ?

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: New => Incomplete

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

Title:
  Unable to install Intel Latest Driver

Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  I was trying to install Intel's driver as the graphics keep freezing for 
couple of seconds, then continue to play...
  I used Terminal to install the graphics driver, But the error occured.
  >sudo apt-get install xserver-xorg-video-intel
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   xserver-xorg-video-intel : Depends: xorg-video-abi-23
  Depends: xserver-xorg-core (>= 2:1.18.99.901)
  E: Unable to correct problems, you have held broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 22 09:18:39 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2019-08-20 (1 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. Inspiron 3542
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-25-generic 
root=UUID=74b87668-96c3-4667-ad47-0905da0b45c2 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0C3NP7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A14
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0C3NP7:rvrA14:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.sku: 0651
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1841018] Re: Unable to install Intel Latest Driver

[Daniel van Vugt]

The latest recommended driver for Intel GPUs is actually the one built
in to Xorg, called "modesetting".

You shouldn't need to install the old 'intel' driver for anything. But
if you do then yes it should at least install.

** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu)

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

Title:
  Unable to install Intel Latest Driver

Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  I was trying to install Intel's driver as the graphics keep freezing for 
couple of seconds, then continue to play...
  I used Terminal to install the graphics driver, But the error occured.
  >sudo apt-get install xserver-xorg-video-intel
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   xserver-xorg-video-intel : Depends: xorg-video-abi-23
  Depends: xserver-xorg-core (>= 2:1.18.99.901)
  E: Unable to correct problems, you have held broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 22 09:18:39 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2019-08-20 (1 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. Inspiron 3542
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-25-generic 
root=UUID=74b87668-96c3-4667-ad47-0905da0b45c2 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0C3NP7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A14
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0C3NP7:rvrA14:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.sku: 0651
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1841018] [NEW] Unable to install Intel Latest Driver

[ABHISHEK]

Public bug reported:

I was trying to install Intel's driver as the graphics keep freezing for couple 
of seconds, then continue to play...
I used Terminal to install the graphics driver, But the error occured.
>sudo apt-get install xserver-xorg-video-intel
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 xserver-xorg-video-intel : Depends: xorg-video-abi-23
Depends: xserver-xorg-core (>= 2:1.18.99.901)
E: Unable to correct problems, you have held broken packages.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
Uname: Linux 5.0.0-25-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 22 09:18:39 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
InstallationDate: Installed on 2019-08-20 (1 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: Dell Inc. Inspiron 3542
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-25-generic 
root=UUID=74b87668-96c3-4667-ad47-0905da0b45c2 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/23/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A14
dmi.board.name: 0C3NP7
dmi.board.vendor: Dell Inc.
dmi.board.version: A14
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0C3NP7:rvrA14:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 3542
dmi.product.sku: 0651
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Unable to install Intel Latest Driver

Status in xorg package in Ubuntu:
  New

Bug description:
  I was trying to install Intel's driver as the graphics keep freezing for 
couple of seconds, then continue to play...
  I used Terminal to install the graphics driver, But the error occured.
  >sudo apt-get install xserver-xorg-video-intel
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   xserver-xorg-video-intel : Depends: xorg-video-abi-23
  Depends: xserver-xorg-core (>= 2:1.18.99.901)
  E: Unable to correct problems, you have held broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 22 09:18:39 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics 

[Desktop-packages] [Bug 1807138] Re: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

[Hui Wang]

If the headphone doesn't work, please run:
sudo hdajacksensetest -a //without plugging the headphone

sudo hdajacksensetest -a //with plugging the headhone

Then upload the log.

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

Title:
  [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Running the command alsamixer allows me to manually increase the sound levels 
for the headset, and sound plays properly through them. This requires me to 
disable the auto-mute feature.
  I haven't rebooted my system yet to see if this is permanent.
  But the UI doesn't show the heaphones at all and only sends sound through the 
main speakers of the laptop.

  ➜  ~ lspci -nnk | grep -i -A7 audio
  00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801

  ➜  ~ cat /proc/asound/card0/codec* | grep Codec 
  Codec: Realtek ALC256
  Codec: Intel Kabylake HDMI

  Using for example pavucontrol allows me to select the headphone, which are 
marked as unplugged, and I can play audio through them as long as I keep the 
application open.
  If I reboot or close pavucontrol, everything is back to the original state 
and only the speakers work.

  Additional Information:

  ➜  ~ lsb_release -rd 
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  What I expect to happen:

  When I plug in my headphones, Ubuntu and the UI should see them and
  automatically redirect all sound through them.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   olivar 8320 F...m pulseaudio
   /dev/snd/controlC0:  olivar 8320 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec  6 13:02:14 2018
  InstallationDate: Installed on 2018-11-21 (15 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: Razer
  dmi.bios.version: 01.01
  dmi.board.name: DANA_MB
  dmi.board.vendor: Razer
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr:
  dmi.product.family: 1A582001 Razer Blade
  dmi.product.name: Blade
  dmi.product.version: 1.04
  dmi.sys.vendor: Razer

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

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

[Desktop-packages] [Bug 1840557] Re: [Dell Inspiron 7559] Battery of 66% shows full icon on 19.04

[Daniel van Vugt]

** Summary changed:

- Battery indicator at 66% show full icon on 19.04
+ [Dell Inspiron 7559] Battery of 66% shows full icon on 19.04

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

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

Title:
  [Dell Inspiron 7559] Battery of 66% shows full icon on 19.04

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The battery indicator at 66% show a full battery icon on 19.04
  At about 55%ish he started to show a different icon (about 80% full icon)
  Rebooting system did not help.
  Updating system did not help.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-08-05 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Tags:  disco
  Uname: Linux 5.0.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1839589] Re: pulseaudio FTBFS on eoan 12.2-2ubuntu4 [FAIL: cpu-volume-test]

[Daniel van Vugt]

pulseaudio (1:12.99.2-1ubuntu1) eoan; urgency=medium

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

** Changed in: pulseaudio (Ubuntu)
 Assignee: Dave Chiluk (chiluk) => Daniel van Vugt (vanvugt)

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

Title:
  pulseaudio FTBFS on eoan 12.2-2ubuntu4 [FAIL: cpu-volume-test]

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  pulseaudio fails to build from source on Eoan

  I was attempting to put together a patchset for LP#1839580, but it
  appears as if the packages are currently failing to build from source.
  Not sure how they built the first time around.

  Here's my ppa's buildlog, for a source package with my patch commented out of 
the series file.
  
https://launchpadlibrarian.net/436626918/buildlog_ubuntu-eoan-amd64.pulseaudio_1%3A12.2-2ubuntu4+lp1839580b2_BUILDING.txt.gz

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

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

[Desktop-packages] [Bug 1807138] Re: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

[Mike Clark]

Just an FYI, the netcat -U /var/run/acpid.socket is now seeing the
headphone jack event.  Everything appears to be working.

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

Title:
  [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Running the command alsamixer allows me to manually increase the sound levels 
for the headset, and sound plays properly through them. This requires me to 
disable the auto-mute feature.
  I haven't rebooted my system yet to see if this is permanent.
  But the UI doesn't show the heaphones at all and only sends sound through the 
main speakers of the laptop.

  ➜  ~ lspci -nnk | grep -i -A7 audio
  00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801

  ➜  ~ cat /proc/asound/card0/codec* | grep Codec 
  Codec: Realtek ALC256
  Codec: Intel Kabylake HDMI

  Using for example pavucontrol allows me to select the headphone, which are 
marked as unplugged, and I can play audio through them as long as I keep the 
application open.
  If I reboot or close pavucontrol, everything is back to the original state 
and only the speakers work.

  Additional Information:

  ➜  ~ lsb_release -rd 
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  What I expect to happen:

  When I plug in my headphones, Ubuntu and the UI should see them and
  automatically redirect all sound through them.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   olivar 8320 F...m pulseaudio
   /dev/snd/controlC0:  olivar 8320 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec  6 13:02:14 2018
  InstallationDate: Installed on 2018-11-21 (15 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: Razer
  dmi.bios.version: 01.01
  dmi.board.name: DANA_MB
  dmi.board.vendor: Razer
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr:
  dmi.product.family: 1A582001 Razer Blade
  dmi.product.name: Blade
  dmi.product.version: 1.04
  dmi.sys.vendor: Razer

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

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

[Desktop-packages] [Bug 1840996] Re: Working with smb

[El jinete sin cabeza]

Add:
https://gitlab.gnome.org/GNOME/nautilus/issues/1201

** Information type changed from Private to Public

** Description changed:

+ https://gitlab.gnome.org/GNOME/nautilus/issues/1201
+ 
+ ---
+ 
  I opened nautilus, accessed a shared resource with samba. Then I tried
  to write in that mounted folder. And he threw me that he had no writing
  privileges. I went to the samba server configuration and increased the
  privileges. And I tried to write *without* closing nautilus. It was
  something similar to what I mention.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.33.90-1ubuntu1
  Uname: Linux 5.2.9-050209-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 21 19:25:59 2019
  ExecutablePath: /usr/bin/nautilus
  ExecutableTimestamp: 1565361020
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2018-12-02 (262 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcCwd: /home/caravena
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=es_CL:es
   LANG=es_CL.UTF-8
  Signal: 6
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (262 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1201
   https://gitlab.gnome.org/GNOME/nautilus/issues/1201

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

Title:
  Working with smb

Status in nautilus package in Ubuntu:
  New

Bug description:
  https://gitlab.gnome.org/GNOME/nautilus/issues/1201

  ---

  I opened nautilus, accessed a shared resource with samba. Then I tried
  to write in that mounted folder. And he threw me that he had no
  writing privileges. I went to the samba server configuration and
  increased the privileges. And I tried to write *without* closing
  nautilus. It was something similar to what I mention.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.33.90-1ubuntu1
  Uname: Linux 5.2.9-050209-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 21 19:25:59 2019
  ExecutablePath: /usr/bin/nautilus
  ExecutableTimestamp: 1565361020
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2018-12-02 (262 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcCwd: /home/caravena
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=es_CL:es
   LANG=es_CL.UTF-8
  Signal: 6
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (262 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1840906] Re: Firefox could not hear streaming Radiko

[Seiichi Nakashima]

I think this is Patent problem.



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

Title:
  Firefox could not hear streaming Radiko

Status in firefox package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dear everyone.

  this is not a bug, but may bug.

  I use ubuntu-18.04.3, and Firefox 68.0.2.
  In Japan radio streaming site named Radiko (http://radiko.jp),
  Firefox could not hear this.

  1 or 2 years old, Firefox + Adobe Flash use could hear Radiko.
  But now Firefox do not support adobe Flash.

  Radiko site change to use adobe flash to HTML5,
  I expected to hear Radiko to use Firefox.
  but could not.

  few days ago, I install chrome(proprietory version),
  chrome could hear radiko streaming.

  what change to need my firefox to hear radkio.

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

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

[Desktop-packages] [Bug 1292041] Re: Lockscreen doesn't turn off the screen

[Janghou]

Ubuntu 19.04

- xset dpms force off

will turn monitors off, but somehow they wakeup in 10 seconds again.

So not sure if this is a bug in screensaver, but it is a nasty and
COSTLY bug.

It will burn 100 watts (3 monitors) and lower lifetime of my monitors.

What's the use of a screensaver or power mode, when it doesn't power off
monitors.

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

Title:
  Lockscreen doesn't turn off the screen

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project trusty series:
  Fix Released
Status in Unity:
  Fix Released
Status in gnome-screensaver package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  [ATTENTION] This bug report is strictly for lockscreen. When user
  activates lockscreen with Ctrl+Alt+L or Super+L shortcut or from
  indicator-session the screen should blank off after a couple seconds.

  The new Unity lock screen doesn't turn off the monitor screen.

  I can wait as long as 10 minutes after activating the lock screen and
  the monitor still doesn't turn off. Then when I unlock the screen and
  don't use mouse or keyboard monitor will turn off (it's about 5
  seconds after unlocking).

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

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

[Desktop-packages] [Bug 1840966] Re: libreoffice-core must not recommend gstreamer1.0-plugins-{bad, ugly}

[Marcus Tomlinson]

Oh damn, that was mistakenly pulled in during a sync with the Debian
packaging! Thanks for pointing this out, I'll have this fixed
immediately.

** Changed in: libreoffice (Ubuntu)
   Status: New => In Progress

** Changed in: libreoffice (Ubuntu)
 Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson)

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

Title:
  libreoffice-core must not recommend gstreamer1.0-plugins-{bad,ugly}

Status in libreoffice package in Ubuntu:
  In Progress

Bug description:
  libreoffice-core 1:6.3.0-0ubuntu1 in eoan-proposed now Recommends:
  gstreamer1.0-plugins-ugly and gstreamer1.0-plugins-bad.  This is not
  allowed.  Recommended packages are installed by default, which means
  that the recommends of any package in main must also be in main; and
  these collections of gstreamer plugins are ones which we explicitly do
  not want to seed in main as they constitute a significant security
  footprint.  (The full list of source packages that would have to go
  through MIR as a consequence of promoting these gstreamer plugins to
  main can be seen at https://people.canonical.com/~ubuntu-archive
  /component-mismatches-proposed).

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

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

[Desktop-packages] [Bug 1840966] [NEW] libreoffice-core must not recommend gstreamer1.0-plugins-{bad, ugly}

[Steve Langasek]

Public bug reported:

libreoffice-core 1:6.3.0-0ubuntu1 in eoan-proposed now Recommends:
gstreamer1.0-plugins-ugly and gstreamer1.0-plugins-bad.  This is not
allowed.  Recommended packages are installed by default, which means
that the recommends of any package in main must also be in main; and
these collections of gstreamer plugins are ones which we explicitly do
not want to seed in main as they constitute a significant security
footprint.  (The full list of source packages that would have to go
through MIR as a consequence of promoting these gstreamer plugins to
main can be seen at https://people.canonical.com/~ubuntu-archive
/component-mismatches-proposed).

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

** Changed in: libreoffice (Ubuntu)
   Importance: Undecided => High

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

Title:
  libreoffice-core must not recommend gstreamer1.0-plugins-{bad,ugly}

Status in libreoffice package in Ubuntu:
  New

Bug description:
  libreoffice-core 1:6.3.0-0ubuntu1 in eoan-proposed now Recommends:
  gstreamer1.0-plugins-ugly and gstreamer1.0-plugins-bad.  This is not
  allowed.  Recommended packages are installed by default, which means
  that the recommends of any package in main must also be in main; and
  these collections of gstreamer plugins are ones which we explicitly do
  not want to seed in main as they constitute a significant security
  footprint.  (The full list of source packages that would have to go
  through MIR as a consequence of promoting these gstreamer plugins to
  main can be seen at https://people.canonical.com/~ubuntu-archive
  /component-mismatches-proposed).

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

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

[Desktop-packages] [Bug 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish

[CoderGuy]

@Gunnar,

I've tested on my main PC.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.3 LTS
Release:18.04
Codename:   bionic

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

Title:
  genesys_gl847 scanners produce a black band in scanned images on
  Ubuntu 17.10+,  18.04 LTS and 18.10 Cosmic cuttlefish

Status in sane-backends:
  Unknown
Status in sane-backends package in Ubuntu:
  In Progress
Status in sane-backends source package in Bionic:
  In Progress
Status in sane-backends source package in Disco:
  In Progress
Status in sane-backends package in Debian:
  Unknown

Bug description:
  [Impact]

  When using a Genesys GL847 scanner, the documents get disfigured by a
  discolored bar. The proposed uploads should fix the issue. They are
  available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends

  [Test case]

  1. Install the libsane (libsane1 in bionic), libsane-common
 and sane-utils packages from {bionic,disco]-proposed.

  2. Use an affected device to scan, and find that the issue is
 no longer present.

  [Regression risk]

  Upstream commit, focused bug fix => low regression risk

  [Original description]

  On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
  black band on scanned image. The scanner is Canon CanoScan LIDE100.
  Libsane version is 1.0.27-1~experimental2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1731459/+subscriptions

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

[Desktop-packages] [Bug 218637] Re: Non-breaking space is easy to write accidentally and impossible or hard to distinguish from regular space.

[Timo Aaltonen]

you'd need to file this upstream

** Package changed: xorg (Ubuntu) => xkeyboard-config (Ubuntu)

** Changed in: xkeyboard-config (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: xkeyboard-config (Ubuntu)
   Status: Invalid => Opinion

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

Title:
  Non-breaking space is easy to write accidentally and impossible or
  hard to distinguish from regular space.

Status in Geany:
  New
Status in gedit:
  New
Status in GNOME Terminal:
  New
Status in nano:
  New
Status in xfce4-terminal:
  New
Status in xkeyboard-config package in Ubuntu:
  Opinion

Bug description:
  OS: from Hardy to at least Bionic.

  When you use Finnish keyboard, you have to hold Alt Gr down to type |
  or \ or certain other characters. When typing a shell command, you may
  often want to enter a space character after such characters. But it
  easily happens that Alt Gr is still down when you press space, and
  consequently you type non-breaking space character U+00A0 (at least,
  if you use UTF-8 keyboard layout, which is default in Ubuntu).

  $cd /tmp ; echo 0 > foo\ bar ; ls "foo bar"
  ls: cannot access foo bar: No such file or directory
  $cat foo bar | grep 0
  No command ' grep' found, but there are 16 similar ones
   grep: command not found

  Besides it may be hard to see the typing error, as non-breaking space
  character looks exactly same as regular space character.

  A way to avoid such typos would be to use another keyboard shortcut
  for non-breaking space. Besides non-breaking space should look
  different than regular space in terminal emulators and in editors.

  WORKAROUNDS:

  Run
  setxkbmap -option "nbsp:none"
  to make  type regular space character.

  Even better option is to use "classic", "mac" or "nodeadkeys" keyboard
  variant instead of "". This could be set up in /etc/default/keyboard
  and maybe in configuration dialog in your desktop environment.

  Non-breaking space can still be typed (in GTK apps) by u
  00a0, if needed. Another option is to use compose key:
.

  In Bash scripts you could also use `printf '\u00a0'` or `printf
  '\xc2\xa0'` to print a non-breaking space. (You could use `echo -en`
  instead of `printf`.) Or you could set up a variable `readonly
  nbsp=$'\u00a0'`.

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

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

[Desktop-packages] [Bug 1840906] Re: Firefox could not hear streaming Radiko

[Seiichi Nakashima]

I upload logfile.


FirefoxLog.txt and syslog

sorry FirefoxLog.txt is japanese.
last message video/mp4;codecs="mp4a.40.5" is hint?

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

Title:
  Firefox could not hear streaming Radiko

Status in firefox package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dear everyone.

  this is not a bug, but may bug.

  I use ubuntu-18.04.3, and Firefox 68.0.2.
  In Japan radio streaming site named Radiko (http://radiko.jp),
  Firefox could not hear this.

  1 or 2 years old, Firefox + Adobe Flash use could hear Radiko.
  But now Firefox do not support adobe Flash.

  Radiko site change to use adobe flash to HTML5,
  I expected to hear Radiko to use Firefox.
  but could not.

  few days ago, I install chrome(proprietory version),
  chrome could hear radiko streaming.

  what change to need my firefox to hear radkio.

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

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

[Desktop-packages] [Bug 1806257] Re: gnome-shell excessive logging cannot bind to x11-unix

[Sami Farin]

gnome-shell's failure to bind can also be caused by namespace.conf settings, 
currently gdm/gnome-shell etc do not take this into account, breaking gdm which 
worked fine without wayland.
https://manpages.ubuntu.com/manpages/trusty/man5/namespace.conf.5.html

Now, if you have in that file:
/tmp/tmp/tmp-inst/  userroot,adm
gdm etc write their files to /tmp/.X0-lock /tmp/.X11-unix/ and so on, but 
gnome-shell tries to open the files at /tmp/tmp-inst/luser/.X11-unix/ (after 
private namespaces have been polyinstantiated).

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

Title:
  gnome-shell excessive logging cannot bind to x11-unix

Status in mutter package in Ubuntu:
  New

Bug description:
  Since the latest mutter upgrade mutter:amd64 3.28.3-2~ubuntu18.04.1 to
  3.28.3-2~ubuntu18.04.2 the login screen can no longer be reached.
  Following symptoms are observed

  * keypresses are not registered; cannot even toggle NUM/CAPS lock
  * gnome-shell taking 100% CPU
  * logging gigabytes of messages to syslog
  * power-button does work and system shuts down when pressed
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2015-12-29 (1069 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  Package: mutter 3.28.3-2~ubuntu18.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-02-17 (287 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1840925] Re: [snap] chromium doesn't start under Wayland with GNOME 3.33

[Olivier Tilloy]

** Changed in: snapd
   Status: New => In Progress

** Changed in: snapd
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  [snap] chromium doesn't start under Wayland with GNOME 3.33

Status in snapd:
  In Progress
Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  (initially reported by Laney on IRC)

  I upgraded my eoan VM with silo 3762¹ which contains the gnome 3.33.90
  update, and after logging out and back into a Wayland session, the
  chromium snap fails to start:

  $ chromium
  No protocol specified
  (chrome:1917): Gtk-WARNING **: 16:08:39.262: cannot open display: :0

  I'm seeing the following denial in the journal:

  name="/run/user/1000/.mutter-Xwaylandauth.5J7F6Z",
  requested_mask="r", denied_mask="r"

  ¹ https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/3762/+packages

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

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

Re: [Desktop-packages] [Bug 1840185] Re: simple-scan app closes with a big delay

[Artyom Pozharov]

Can I help you to find this driver?

ср, 21 авг. 2019 г., 6:41 Robert Ancell :

> This is the SANE drivers taking a long time to shutdown. Simple Scan
> waits for them to complete, in case there is important things that need
> to be done. I don't know which driver takes a long time.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1840185
>
> Title:
>   simple-scan app closes with a big delay
>
> Status in simple-scan package in Ubuntu:
>   New
>
> Bug description:
>   When I touch closing button I will wait for a while for exiting from
> this program. There are details in my video.
>   Information from console:
>   ubuntenok@ubuntenok-HP-250-G6-Notebook-PC:~$ simple-scan
>   (simple-scan:13544): Gtk-WARNING **: 22:15:55.501: Failed to register
> client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to
> register client
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.10
>   Package: simple-scan 3.33.90-0ubuntu1
>   ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
>   Uname: Linux 5.2.0-10-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu7
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Aug 14 22:45:14 2019
>   InstallationDate: Installed on 2019-08-14 (0 days ago)
>   InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
>   Lsusb:
>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>Bus 001 Device 004: ID 05c8:0233 Cheng Uei Precision Industry Co., Ltd
> (Foxlink) HP Webcam
>Bus 001 Device 003: ID 8087:0aa7 Intel Corp.
>Bus 001 Device 002: ID 248a:8514 Maxxter Wireless Receiver
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   MachineType: HP HP 250 G6 Notebook PC
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-10-generic
> root=UUID=b1b8960c-e09c-4671-bcc2-1b3bd70c7ed4 ro quiet splash vt.handoff=7
>   SourcePackage: simple-scan
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 03/04/2019
>   dmi.bios.vendor: Insyde
>   dmi.bios.version: F.52
>   dmi.board.asset.tag: Type2 - Board Asset Tag
>   dmi.board.name: 832E
>   dmi.board.vendor: HP
>   dmi.board.version: 26.35
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: HP
>   dmi.chassis.version: Chassis Version
>   dmi.modalias:
> dmi:bvnInsyde:bvrF.52:bd03/04/2019:svnHP:pnHP250G6NotebookPC:pvrType1ProductConfigId:rvnHP:rn832E:rvr26.35:cvnHP:ct10:cvrChassisVersion:
>   dmi.product.family: 103C_5336AN HP 200
>   dmi.product.name: HP 250 G6 Notebook PC
>   dmi.product.sku: 3DN65ES#ACB
>   dmi.product.version: Type1ProductConfigId
>   dmi.sys.vendor: HP
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1840185/+subscriptions
>

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

Title:
  simple-scan app closes with a big delay

Status in simple-scan package in Ubuntu:
  New

Bug description:
  When I touch closing button I will wait for a while for exiting from this 
program. There are details in my video.
  Information from console:
  ubuntenok@ubuntenok-HP-250-G6-Notebook-PC:~$ simple-scan
  (simple-scan:13544): Gtk-WARNING **: 22:15:55.501: Failed to register client: 
GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register 
client

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: simple-scan 3.33.90-0ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 14 22:45:14 2019
  InstallationDate: Installed on 2019-08-14 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05c8:0233 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Webcam
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 248a:8514 Maxxter Wireless Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP 250 G6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-10-generic 
root=UUID=b1b8960c-e09c-4671-bcc2-1b3bd70c7ed4 ro quiet splash vt.handoff=7
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.52
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 832E
  dmi.board.vendor: HP
  dmi.board.version: 26.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.52:bd03/04/2019:svnHP:pnHP250G6NotebookPC:pvrType1ProductConfigId:rvnHP:rn832E:rvr26.35:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 

[Desktop-packages] [Bug 1840557] Re: Battery indicator at 66% show full icon on 19.04

[Daniel Szulc]

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1840557/+attachment/5283736/+files/dmesg.txt

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

Title:
  Battery indicator at 66% show full icon on 19.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The battery indicator at 66% show a full battery icon on 19.04
  At about 55%ish he started to show a different icon (about 80% full icon)
  Rebooting system did not help.
  Updating system did not help.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-08-05 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Tags:  disco
  Uname: Linux 5.0.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1840925] Re: [snap] chromium doesn't start under Wayland with GNOME 3.33

[Olivier Tilloy]

Proposed https://github.com/snapcore/snapd/pull/7303.

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

Title:
  [snap] chromium doesn't start under Wayland with GNOME 3.33

Status in snapd:
  New
Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  (initially reported by Laney on IRC)

  I upgraded my eoan VM with silo 3762¹ which contains the gnome 3.33.90
  update, and after logging out and back into a Wayland session, the
  chromium snap fails to start:

  $ chromium
  No protocol specified
  (chrome:1917): Gtk-WARNING **: 16:08:39.262: cannot open display: :0

  I'm seeing the following denial in the journal:

  name="/run/user/1000/.mutter-Xwaylandauth.5J7F6Z",
  requested_mask="r", denied_mask="r"

  ¹ https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/3762/+packages

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

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

[Desktop-packages] [Bug 1840557] Re: Battery indicator at 66% show full icon on 19.04

[Daniel Szulc]

DELL Inspiron 7559

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

Title:
  Battery indicator at 66% show full icon on 19.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The battery indicator at 66% show a full battery icon on 19.04
  At about 55%ish he started to show a different icon (about 80% full icon)
  Rebooting system did not help.
  Updating system did not help.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-08-05 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Tags:  disco
  Uname: Linux 5.0.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1840925] Re: [snap] chromium doesn't start under Wayland with GNOME 3.33

[Olivier Tilloy]

If that rule were to be added to the wayland interface, the chromium
snap would also need to declare a plug on wayland (it currently
doesn't).

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

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

Title:
  [snap] chromium doesn't start under Wayland with GNOME 3.33

Status in snapd:
  New
Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  (initially reported by Laney on IRC)

  I upgraded my eoan VM with silo 3762¹ which contains the gnome 3.33.90
  update, and after logging out and back into a Wayland session, the
  chromium snap fails to start:

  $ chromium
  No protocol specified
  (chrome:1917): Gtk-WARNING **: 16:08:39.262: cannot open display: :0

  I'm seeing the following denial in the journal:

  name="/run/user/1000/.mutter-Xwaylandauth.5J7F6Z",
  requested_mask="r", denied_mask="r"

  ¹ https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/3762/+packages

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

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

[Desktop-packages] [Bug 1840925] Re: [snap] chromium doesn't start under Wayland with GNOME 3.33

[Olivier Tilloy]

Adding the following rule to
/var/lib/snapd/apparmor/profiles/snap.chromium.chromium and reloading
the profile is enough to fix the problem:

/run/user/[0-9]*/.mutter-Xwaylandauth.* r,

** Description changed:

  (initially reported by Laney on IRC)
  
  I upgraded my eoan VM with silo 3762¹ which contains the gnome 3.33.90
  update, and after logging out and back into a Wayland session, the
  chromium snap fails to start:
  
- $ chromium
- No protocol specified
- (chrome:1917): Gtk-WARNING **: 16:08:39.262: cannot open display: :0
+ $ chromium
+ No protocol specified
+ (chrome:1917): Gtk-WARNING **: 16:08:39.262: cannot open display: :0
  
  I'm seeing the following denial in the journal:
  
- name="/run/user/1000/.mutter-Xwaylandauth-5J7F6Z",
+ name="/run/user/1000/.mutter-Xwaylandauth.5J7F6Z",
  requested_mask="r", denied_mask="r"
  
- 
- ¹ https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3762/+packages
+ ¹ https://launchpad.net/~ci-train-ppa-
+ service/+archive/ubuntu/3762/+packages

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

Title:
  [snap] chromium doesn't start under Wayland with GNOME 3.33

Status in snapd:
  New
Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  (initially reported by Laney on IRC)

  I upgraded my eoan VM with silo 3762¹ which contains the gnome 3.33.90
  update, and after logging out and back into a Wayland session, the
  chromium snap fails to start:

  $ chromium
  No protocol specified
  (chrome:1917): Gtk-WARNING **: 16:08:39.262: cannot open display: :0

  I'm seeing the following denial in the journal:

  name="/run/user/1000/.mutter-Xwaylandauth.5J7F6Z",
  requested_mask="r", denied_mask="r"

  ¹ https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/3762/+packages

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

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

[Desktop-packages] [Bug 1766230] Re: Strange window matching behaviour between Slack and Chrome

[Jim Campbell]

For reference, I also see this same issue with Firefox set as my default
browser, and I am using the snap version of Slack.

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

Title:
  Strange window matching behaviour between Slack and Chrome

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  There seems to be a window matching bug between the Slack snap and
  Chrome.

  If you open a URL from within Slack without Chrome open, then the
  launcher shows the extra pip next to Slack and doesn't add a Chrome
  icon to the launcher.  If you open Chrome first, then things work as
  expected.

  Steps to reproduce

  1.  Install Slack snap and Chrome deb.
  2.  Join a Slack channel and open a hyperlink.  Notice the extra pip next to 
Slack in the launcher.
  3.  Close Chrome and reopen it.
  4.  Open a URL from Slack again and notice the Chrome icon get added to the 
launcher.

  I'm not sure if this is an Ubuntu Dock or GNOME Shell issue.  EDIT:
  Spoke to didrocks, he says that matching is done by Shell.

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

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

[Desktop-packages] [Bug 1766230] Re: Strange window matching behaviour between Slack and Chrome

[Jim Campbell]

Seeing this behavior, as well. Others reference vscode (in the comment
above), so I am curious to know if this is related to electron, or if
this is a snap-specific issue.

I do see reference to it as a snap-specific issue here:
https://forum.snapcraft.io/t/slack-opening-file-browser-firefox-and-
chrome-in-the-snaps-context/8969/3

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

Title:
  Strange window matching behaviour between Slack and Chrome

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  There seems to be a window matching bug between the Slack snap and
  Chrome.

  If you open a URL from within Slack without Chrome open, then the
  launcher shows the extra pip next to Slack and doesn't add a Chrome
  icon to the launcher.  If you open Chrome first, then things work as
  expected.

  Steps to reproduce

  1.  Install Slack snap and Chrome deb.
  2.  Join a Slack channel and open a hyperlink.  Notice the extra pip next to 
Slack in the launcher.
  3.  Close Chrome and reopen it.
  4.  Open a URL from Slack again and notice the Chrome icon get added to the 
launcher.

  I'm not sure if this is an Ubuntu Dock or GNOME Shell issue.  EDIT:
  Spoke to didrocks, he says that matching is done by Shell.

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

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

[Desktop-packages] [Bug 1840925] Re: [snap] chromium doesn't start under Wayland with GNOME 3.33

[Olivier Tilloy]

Relevant upstream commit:
https://github.com/GNOME/mutter/commit/a8984a81c2e887623d69ec9989ae8a5025f7bd47.

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

Title:
  [snap] chromium doesn't start under Wayland with GNOME 3.33

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  (initially reported by Laney on IRC)

  I upgraded my eoan VM with silo 3762¹ which contains the gnome 3.33.90
  update, and after logging out and back into a Wayland session, the
  chromium snap fails to start:

  $ chromium
  No protocol specified
  (chrome:1917): Gtk-WARNING **: 16:08:39.262: cannot open display: :0

  I'm seeing the following denial in the journal:

  name="/run/user/1000/.mutter-Xwaylandauth-5J7F6Z",
  requested_mask="r", denied_mask="r"

  
  ¹ https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3762/+packages

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

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

[Desktop-packages] [Bug 1840925] [NEW] [snap] chromium doesn't start under Wayland with GNOME 3.33

[Olivier Tilloy]

Public bug reported:

(initially reported by Laney on IRC)

I upgraded my eoan VM with silo 3762¹ which contains the gnome 3.33.90
update, and after logging out and back into a Wayland session, the
chromium snap fails to start:

$ chromium
No protocol specified
(chrome:1917): Gtk-WARNING **: 16:08:39.262: cannot open display: :0

I'm seeing the following denial in the journal:

name="/run/user/1000/.mutter-Xwaylandauth-5J7F6Z",
requested_mask="r", denied_mask="r"


¹ https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3762/+packages

** Affects: chromium-browser (Ubuntu)
 Importance: High
 Assignee: Olivier Tilloy (osomon)
 Status: Triaged


** Tags: snap

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

Title:
  [snap] chromium doesn't start under Wayland with GNOME 3.33

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  (initially reported by Laney on IRC)

  I upgraded my eoan VM with silo 3762¹ which contains the gnome 3.33.90
  update, and after logging out and back into a Wayland session, the
  chromium snap fails to start:

  $ chromium
  No protocol specified
  (chrome:1917): Gtk-WARNING **: 16:08:39.262: cannot open display: :0

  I'm seeing the following denial in the journal:

  name="/run/user/1000/.mutter-Xwaylandauth-5J7F6Z",
  requested_mask="r", denied_mask="r"

  
  ¹ https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3762/+packages

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

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

[Desktop-packages] [Bug 1840921] Re: totem crashed with SIGABRT

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1501049, so 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.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1840921/+attachment/5283712/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1840921/+attachment/5283714/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1840921/+attachment/5283720/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1840921/+attachment/5283721/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1840921/+attachment/5283722/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1840921/+attachment/5283723/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1840921/+attachment/5283724/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1501049
   totem crashed with assertion failure 
[Totem:ERROR:totem-grilo.c:729:browse_cb: code should not be reached]

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  totem crashed with SIGABRT

Status in totem package in Ubuntu:
  New

Bug description:
  I don't know how it happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: totem 3.33.90-2ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.8-050208-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 15 16:52:27 2019
  ExecutablePath: /usr/bin/totem
  ExecutableTimestamp: 1565362808
  InstallationDate: Installed on 2018-12-02 (260 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcCwd: /home/caravena
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=es_CL:es
   LANG=es_CL.UTF-8
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libtotem.so.0
   () at /usr/lib/x86_64-linux-gnu/libgrilo-0.3.so.0
   g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (260 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1811824] Re: [MIR] xdg-dbus-proxy

[Sebastien Bacher]

Override component to main
xdg-dbus-proxy 0.1.1-1 in eoan: universe/misc -> main
xdg-dbus-proxy 0.1.1-1 in eoan amd64: universe/admin/optional/100% -> main
xdg-dbus-proxy 0.1.1-1 in eoan arm64: universe/admin/optional/100% -> main
xdg-dbus-proxy 0.1.1-1 in eoan armhf: universe/admin/optional/100% -> main
xdg-dbus-proxy 0.1.1-1 in eoan i386: universe/admin/optional/100% -> main
xdg-dbus-proxy 0.1.1-1 in eoan ppc64el: universe/admin/optional/100% -> main
xdg-dbus-proxy 0.1.1-1 in eoan s390x: universe/admin/optional/100% -> main
Override [y|N]? y


** Changed in: xdg-dbus-proxy (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [MIR] xdg-dbus-proxy

Status in xdg-dbus-proxy package in Ubuntu:
  Fix Released

Bug description:
  Availability
  
  Built for all supported architectures.

  In sync with Debian.

  Rationale
  =
  webkit2gtk 2.26 will release in September. It adds per-process sandboxing 
using bubblewrap and xdg-dbus-proxy.

  xdg-dbus-proxy was previously part of Flatpak but was split out for
  easier use by other projects.

  By the time this is needed, xdg-dbus-proxy in main will need to be
  backported to 18.04 LTS and 19.04. (New major webkit2gtk releases
  happen every March and September. Once a new major release is out, the
  old major release is no longer supported. New releases include
  security updates.)

  Security
  
  This will need a Security review.

  https://security-tracker.debian.org/tracker/source-package/xdg-dbus-proxy
  https://security-tracker.debian.org/tracker/source-package/flatpak

  There was one security issue (CVE-2018-6560) that has been fixed in
  all supported Ubuntu releases.

  Quality assurance
  =
  Bug subscriber: Desktop Packages

  https://bugs.launchpad.net/ubuntu/+source/xdg-dbus-proxy
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=xdg-dbus-proxy
  https://github.com/flatpak/xdg-dbus-proxy/issues

  tests are run as build tests (with dh_auto_test) and installed autopkgtests 
on Debian and Ubuntu.
  https://ci.debian.net/packages/x/xdg-dbus-proxy
  http://autopkgtest.ubuntu.com/packages/x/xdg-dbus-proxy

  Dependencies
  
  All binary dependencies are in main

  Standards compliance
  
  4.2.1

  Maintenance
  ===
  - Actively developed upstream
  https://github.com/flatpak/xdg-dbus-proxy

  - Maintained in Debian by the pkg-utopia team but more specifically,
  it is maintained by Simon McVittie (smcv) who also maintains Flatpak
  and ostree in Debian.

  short dh7 style rules, dh compat 11/12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-dbus-proxy/+bug/1811824/+subscriptions

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

[Desktop-packages] [Bug 1840915] Re: tracker-store crashed with SIGSEGV in tracker_events_add_delete()

[El jinete sin cabeza]

** Information type changed from Private to Public

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

Title:
  tracker-store crashed with SIGSEGV in tracker_events_add_delete()

Status in tracker package in Ubuntu:
  Invalid

Bug description:
  I don't know how it happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: tracker 2.1.8-2
  Uname: Linux 5.2.9-050209-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 21 08:28:15 2019
  ExecutablePath: /usr/lib/tracker/tracker-store
  InstallationDate: Installed on 2018-12-02 (261 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/lib/tracker/tracker-store
  ProcEnviron:
   LANG=es_CL.UTF-8
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x56172bf3c22d :
mov0x10(%rax),%rdi
   PC (0x56172bf3c22d) ok
   source "0x10(%rax)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: tracker
  StacktraceTop:
   tracker_events_add_delete ()
   ()
   () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so.0
   () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so.0
   () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so.0
  Title: tracker-store crashed with SIGSEGV in tracker_events_add_delete()
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (261 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 864494] Re: Wrong preview image in the file open dialog.

[Paul White]

** Changed in: hundredpapercuts
   Status: Triaged => Fix Released

** Changed in: gtk+3.0 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Wrong preview image in the file open dialog.

Status in GTK+:
  Fix Released
Status in One Hundred Papercuts:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  Hello,
  File open dialog seems to display wrong preview image in some cases.
  Please study this video:
  http://www.futuredesktop.com/tmp/file-open-test.ogv

  You can reproduce this issue with:
  1)  Open the program for change-desktop-background (appearance dialog).

  2) Click the [+] button and browse to Test/  images.

  3) In the file open dialog, press "b" letter to browse just the images
  that start with "b".  This is important, ok?

  4) Now use arrow-keys to move from one bimage* to another. The preview
  image is wrong.

  Notice: I could only produce this when I restricted the search with a
  letter or word, and then used ARROW-KEYS to jump to next/previous
  file. Selection with mouse works always right.

  Here are the actual Test/ images:
  http://www.futuredesktop.com/tmp/Test.tar.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: nautilus 1:3.2.0-0ubuntu5
  ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu2
  Architecture: amd64
  Date: Sun Oct  2 09:35:33 2011
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110919)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to oneiric on 2011-09-29 (2 days ago)

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

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

[Desktop-packages] [Bug 1840906] Re: Firefox could not hear streaming Radiko

[Paul White]

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

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

Title:
  Firefox could not hear streaming Radiko

Status in firefox package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dear everyone.

  this is not a bug, but may bug.

  I use ubuntu-18.04.3, and Firefox 68.0.2.
  In Japan radio streaming site named Radiko (http://radiko.jp),
  Firefox could not hear this.

  1 or 2 years old, Firefox + Adobe Flash use could hear Radiko.
  But now Firefox do not support adobe Flash.

  Radiko site change to use adobe flash to HTML5,
  I expected to hear Radiko to use Firefox.
  but could not.

  few days ago, I install chrome(proprietory version),
  chrome could hear radiko streaming.

  what change to need my firefox to hear radkio.

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

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

[Desktop-packages] [Bug 1029932] Re: Brightness and Volume laptop keys behave inconsistently

[Paul White]

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

This release of Ubuntu is no longer receiving maintenance updates. If
this is still an issue using a maintained version of Ubuntu please let
us know.

Paul White
[Ubuntu Bug Squad]

** Changed in: hundredpapercuts
   Status: Confirmed => Incomplete

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

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

Title:
  Brightness and Volume laptop keys behave inconsistently

Status in One Hundred Papercuts:
  Incomplete
Status in gnome-power-manager package in Ubuntu:
  Incomplete

Bug description:
  Holding the volume up button causes the volume to continually go up.
  The same doesn't work for brightness - the button has to be repeatedly
  pressed.

  This inconsistency can be confusing for users. I believe the
  preferable behaviour is that of the volume buttons.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-power-manager 3.4.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
  Uname: Linux 3.2.0-27-generic x86_64
  ApportVersion: 2.0.1-0ubuntu11
  Architecture: amd64
  CheckboxSubmission: 346c69198d9a34d2dea85736f0dd6571
  CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3
  Date: Fri Jul 27 14:13:03 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1840908] [NEW] Stick to 1.16 for eoan

[Sebastien Bacher]

Public bug reported:

There is no stable 1.18 planned for before eoan and nothing we really
need in 1.17

** Affects: cairo (Ubuntu)
 Importance: Wishlist
 Status: Triaged


** Tags: upgrade-software-version version-skip-1.17.2

** Changed in: cairo (Ubuntu)
   Status: New => Triaged

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

Title:
  Stick to 1.16 for eoan

Status in cairo package in Ubuntu:
  Triaged

Bug description:
  There is no stable 1.18 planned for before eoan and nothing we really
  need in 1.17

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

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

[Desktop-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

[dwmw2]

I have worked out the problem with the new NetworkManager which required
me to set ipv4.dns-priority=-1 (which, in turn, messes things up for
those with fresh installs that don't get the new NetworkManager).

The new NM sets ipv4.dns-search=~. automatically for full-tunnel VPNs
but it doesn't also set ipv4.dns-priority=-1. This means that any DNS
domain on a local network which isn't also explicitly matched by the VPN
config, is considered "more specific" and gets used instead of the VPN.

This is wrong; NetworkManager should also set ipv4.dns-priority=-1 for
full-tunnel VPNs.

The reason this was consistently problematic for our users is that we
have set up /etc/dhcp/dhclient.conf to *override* the domains given by
the local network to include the root of our corporate AD domain
"DOM.COMPANY.COM", because various non-FQDN hostnames in AD would
otherwise cause problems.

This realisation does give me a way out of my current problem, until a
newer version of NM correctly sets the priority automatically. Instead
of manually configuring ipv4.dns-priority=-1 and breaking things for
older NM, I can manually configure ipv4.dns-
search=dom.company.com;company.com which works for everyone. And there
*are* no other search domains which get leaked now, because our DHCP
config doesn't let them get discovered. (Deliberately ignoring RDNSS
here because if you live in the 21st century and have IPv6, you still
get to use that anyway even when you're on a full-tunnel Legacy IP VPN.
Nobody tell the IT folks please.)

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Fix Released
Status in network-manager source package in Cosmic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not

  [Test case]
  1) Set up a VPN with split tunneling:
a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".

  2) Connect to the VPN.

  3) Run 'systemd-resolve --status'; note the DNS servers configured:
a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).

  4) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  5) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  6) In yet another terminal, issue name resolution requests using dig:
a) For a name known to be reachable via the public network:
   'dig www.yahoo.com'
b) For a name known to be reachable only via the VPN:
   'dig '

  7) Check the output of each terminal running tcpdump. When requesting
  the public name, traffic can go through either. When requesting the
  "private" name (behind the VPN), traffic should only be going through
  the interface for the VPN. Additionally, ensure the IP receiving the
  requests for the VPN name is indeed the IP address noted above for the
  VPN's DNS server.

  If you see no traffic showing in tcpdump output when requesting a
  name, it may be because it is cached by systemd-resolved. Use a
  different name you have not tried before.

  
  [Regression potential]
  The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations

  -

  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't 

[Desktop-packages] [Bug 1380561] Re: "Unknown variable 'ansA'" when editing the result after converting to hexadecimal

[Paul White]

** Bug watch added: gitlab.gnome.org/GNOME/gnome-calculator/issues #39
   https://gitlab.gnome.org/GNOME/gnome-calculator/issues/39

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

** Changed in: gnome-calculator
   Status: Expired => Unknown

** Changed in: gnome-calculator
 Remote watch: GNOME Bug Tracker #748731 => 
gitlab.gnome.org/GNOME/gnome-calculator/issues #39

** Changed in: hundredpapercuts
   Status: Confirmed => Triaged

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

Title:
  "Unknown variable 'ansA'" when editing the result after converting to
  hexadecimal

Status in GNOME Calculator:
  Unknown
Status in One Hundred Papercuts:
  Triaged
Status in gnome-calculator package in Ubuntu:
  Triaged

Bug description:
  Version: 1:3.10.2-0ubuntu1.2

  I want to edit a result in hexadecimal:

  [Test Case]
  - open gnome-calculator
  - choose Programming mode
  - choose Decimal and enter a decimal number then press Enter
  - choose Hexadecimal to convert the number to hex
  - add A or any hexadecimal number A-F to the result and press Enter
  - you'll see "Unknown variable 'ansA'" where A is what you appended to the 
result

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

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

[Desktop-packages] [Bug 1839846] Re: Please sync librsync 2 from Debian

[Otto Kekäläinen]

Version 2.0.2-1 from Debian is in eoan-proposed but does not progress
from there and the reason for me is not visible:
https://launchpad.net/ubuntu/+source/librsync/+publishinghistory

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

Title:
  Please sync librsync 2 from Debian

Status in librsync package in Ubuntu:
  New

Bug description:
  Ubuntu has delta from Debian that was never upstreamed. Please drop
  the delta and sync librsync 2.0.2 from Debian so Ubuntu would not lag
  behind.

  See https://tracker.debian.org/pkg/librsync for details

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

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

[Desktop-packages] [Bug 1840799] Re: Chromium can't be set as default browser

[Olivier Tilloy]

Have you tried using chromium's built-in setting to set itself as the default 
browser?
Just browse to chrome://settings/defaultBrowser and click the button (under the 
covers this calls `xdg-settings set default-web-browser`).

** Changed in: chromium-browser (Ubuntu)
   Status: New => Incomplete

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

Title:
  Chromium can't be set as default browser

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I've tried setting chromium-browser to be the default browser by
  either xtools,lxde tools or just uninstalling firefox. Nothing seems
  to make it stop warning me about being a non default browser.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: chromium-browser 76.0.3809.100-0ubuntu0.19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: LXQt
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGEPCcABEWAQSVHRJ4Au8Fl1dUkiciUFQBAQEBAQEBAQEBAQEBAQEBuSKgoFCEGjAwIDYAHrMYEAAA/gBMU04xMzNCVDAxQTAy/ABDb2xvciBMQ0QKICAgAA==
   modes: 1440x900
  Date: Tue Aug 20 12:14:43 2019
  Desktop-Session:
   'Lubuntu'
   '/etc/xdg/xdg-Lubuntu:/etc/xdg:/etc:/usr/share'
   '/usr/share/Lubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2019-08-18 (1 days ago)
  InstallationMedia: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  InstalledPlugins:
   
  Load-Avg-1min: 0.30
  Load-Processes-Running-Percent:   0.2%
  MachineType: Apple Inc. MacBookAir6,2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=8c63961b-d119-49bc-b3d2-fceb7def3641 ro quiet splash vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2016
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA61.88Z.0099.B23.1610201523
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-7DF21CB3ED6977E5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir6,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-7DF21CB3ED6977E5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B23.1610201523:bd10/20/2016:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5:
  dmi.product.family: MacBook Air
  dmi.product.name: MacBookAir6,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1288182] Re: Cyrillic not displayed in the input field

[BHUPESH RATHORE]

The same problem reproduced with displaying PDF form in fresh Firefox and 
Chrome web browsers, that use JS rendering. So the problem is in PDF document - 
PDF document doesn't embed non-Cyrillic font letters in PDF file. For this 
cases is better to display symbols via some default font, instead of missing 
letters.

So can we add workaround for "warning: layout text: cannot convert U+65E5" - 
replace font for this symbol to system default?
https://www.socialmediagossips.com/

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

Title:
  Cyrillic not displayed in the input field

Status in Evince:
  Unknown
Status in Poppler:
  New
Status in evince package in Ubuntu:
  Triaged
Status in poppler package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 x64
  Evince 3.10.3
  Cyrillic not displayed in the input field.

  In attach screenshot: input field with text 'This сyrillic:
  "Кириллица"'

  Upd.

  Still actual for Ubuntu 16.04 x64
  Evince 3.18.2

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

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

[Desktop-packages] [Bug 1840900] [NEW] Gnome-shell-extension-ubuntu-dock not run in the absence of a display

[kirill]

Public bug reported:

Ubuntu 18.04.3, GeForce GTX 750, Nvidia proprietary driver v390
gnome-shell-extension-ubuntu-dock - 0.9.1ubuntu18.04.3

I need the graphical environment to start without a monitor. This is
necessary for testing applications.

For this, I have created a configuration
/usr/share/X11/xorg.conf.d/10-nvidia.conf:

Section "Monitor"
Identifier  "Configured Monitor"
HorizSync 5.0 - 1000.0
VertRefresh 5.0 - 200.0
ModeLine "1920x1080" 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +Hsync 
+Vsync
EndSection

Section "OutputClass"
Identifier "nvidia"
MatchDriver "nvidia-drm"
Driver "nvidia"
Option "AllowEmptyInitialConfiguration"
ModulePath "/usr/lib/x86_64-linux-gnu/nvidia/xorg"
EndSection

Section "Device"
Identifier "Idek Iiyama"
Option "ConnectedMonitor" "DFP-0"
EndSection


If I turn off and turn on the computer without a connected display, then I will 
get a standard Gnome3 without ubuntu-dock

When booting the system, I get an error:

Aug 21 11:22:51 box gnome-shell[3417]: JS WARNING: 
[resource:///org/gnome/shell/ui/workspaceThumbnail.js 891]: reference to 
undefined property "_switchWorkspaceNotifyId"
Aug 21 11:22:51 box gnome-shell[3417]: JS WARNING: 
[/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js 1778]: 
reference to undefined property "_workspaceIsolation"
Aug 21 11:22:51 box gnome-shell[3417]: JS ERROR: TypeError: 
this._workspaceIsolation is 
undefined#012DockManager<._deleteDocks@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1778:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012DockManager<._toggle@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1662:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
Aug 21 11:22:51 box gnome-shell[3417]: JS ERROR: TypeError: 
this._workspaceIsolation is 
undefined#012DockManager<._deleteDocks@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1778:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012DockManager<._toggle@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1662:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22


ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3
ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
Uname: Linux 5.0.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
Date: Wed Aug 21 12:35:20 2019
InstallationDate: Installed on 2019-05-06 (106 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "2.png"
   https://bugs.launchpad.net/bugs/1840900/+attachment/5283659/+files/2.png

** Description changed:

  Ubuntu 18.04.3, GeForce GTX 750, Nvidia proprietary driver v390
  gnome-shell-extension-ubuntu-dock - 0.9.1ubuntu18.04.3
  
  I need the graphical environment to start without a monitor. This is
  necessary for testing applications.
  
- For this, I have created a configuration 
/usr/share/X11/xorg.conf.d/10-nvidia.conf
- ```
+ For this, I have created a configuration
+ /usr/share/X11/xorg.conf.d/10-nvidia.conf:
+ 
  Section "Monitor"
- Identifier  "Configured Monitor"
- HorizSync 5.0 - 1000.0
- VertRefresh 5.0 - 200.0
- ModeLine "1920x1080" 148.50 1920 2448 2492 2640 1080 1084 1089 1125 
+Hsync +Vsync
+ Identifier  "Configured Monitor"
+ HorizSync 5.0 - 1000.0
+ VertRefresh 5.0 - 200.0
+ ModeLine "1920x1080" 148.50 1920 2448 2492 2640 1080 1084 1089 1125 
+Hsync +Vsync
  EndSection
  
  Section "OutputClass"
- Identifier "nvidia"
- MatchDriver "nvidia-drm"
- Driver "nvidia"
- Option "AllowEmptyInitialConfiguration"
- ModulePath "/usr/lib/x86_64-linux-gnu/nvidia/xorg"
+ Identifier "nvidia"
+ MatchDriver "nvidia-drm"
+ Driver "nvidia"
+ Option "AllowEmptyInitialConfiguration"
+ ModulePath "/usr/lib/x86_64-linux-gnu/nvidia/xorg"
  EndSection
  
  Section "Device"
- Identifier "Idek Iiyama"
- Option "ConnectedMonitor" "DFP-0"
+ Identifier "Idek Iiyama"
+ Option "ConnectedMonitor" "DFP-0"
  EndSection
- ```
  
- If I turn off and turn on the computer without a connected display, then
- I will get a standard Gnome3 without ubuntu-dock
+ 
+ If I turn off and turn on the computer without a connected display, then I 
will get a standard Gnome3 without ubuntu-dock
  
  When booting the system, I get an error:
- ```
+ 
  Aug 21 11:22:51 box gnome-shell[3417]: JS WARNING: 
[resource:///org/gnome/shell/ui/workspaceThumbnail.js 891]: reference to 
undefined property 

[Desktop-packages] [Bug 1232872] Re: NFS / lock problem with LibreOffice wth 13.04

[Marcus Tomlinson]

** Also affects: df-libreoffice via
   https://bugs.documentfoundation.org/show_bug.cgi?id=75488
   Importance: Unknown
   Status: Unknown

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

Title:
  NFS / lock problem with LibreOffice wth 13.04

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Hi all,

  I have a problem very similar to what is exposed in question #234375.

  Since I upgraded to Ubuntu 13.04 (host x86_64), I have trouble accessing 
documents via NFS with LibreOffice.
  The slash screen display for about 30s, then there is a popup warning saying 
that another user has opened the file, and offering to open a copy, open as 
readonly or cancel.

  The point is, no other user has opened that file (being the only user
  on my personal PC, but storing my documents on NAS).

  So I tried the suggestion about adding "noauto" in /etc/fstab and
  changing /etc/rc.local, with no luck.

  But the modification of /usr/lib/libreoffice/program/soffice:
  ##

  # 
  STAR_PROFILE_LOCKING_DISABLED=1
  export STAR_PROFILE_LOCKING_DISABLED
  #

  # file locking now enabled by default
  #SAL_ENABLE_FILE_LOCKING=1 # <<- if set to 0 ; same trouble ...
  #export SAL_ENABLE_FILE_LOCKING
  ###

  (That is, uncomment the first 2 lines, and commenting the other 2)
  This works OK.

  If this is the official way of fixing things, then I guess LibreOffice
  deserves an update on Ubuntu at least.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1232872/+subscriptions

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

[Desktop-packages] [Bug 1232872] Re: NFS / lock problem with LibreOffice wth 13.04

[Christophe Lyon]

I had traced this down to a problem with LibreOffice apparently not
releasing the locks.

I added comments to
https://bugs.documentfoundation.org/show_bug.cgi?id=75488

So, the problem is still here, but no one seems to care upstream.


** Bug watch added: Document Foundation Bugzilla #75488
   https://bugs.documentfoundation.org/show_bug.cgi?id=75488

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

Title:
  NFS / lock problem with LibreOffice wth 13.04

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Hi all,

  I have a problem very similar to what is exposed in question #234375.

  Since I upgraded to Ubuntu 13.04 (host x86_64), I have trouble accessing 
documents via NFS with LibreOffice.
  The slash screen display for about 30s, then there is a popup warning saying 
that another user has opened the file, and offering to open a copy, open as 
readonly or cancel.

  The point is, no other user has opened that file (being the only user
  on my personal PC, but storing my documents on NAS).

  So I tried the suggestion about adding "noauto" in /etc/fstab and
  changing /etc/rc.local, with no luck.

  But the modification of /usr/lib/libreoffice/program/soffice:
  ##

  # 
  STAR_PROFILE_LOCKING_DISABLED=1
  export STAR_PROFILE_LOCKING_DISABLED
  #

  # file locking now enabled by default
  #SAL_ENABLE_FILE_LOCKING=1 # <<- if set to 0 ; same trouble ...
  #export SAL_ENABLE_FILE_LOCKING
  ###

  (That is, uncomment the first 2 lines, and commenting the other 2)
  This works OK.

  If this is the official way of fixing things, then I guess LibreOffice
  deserves an update on Ubuntu at least.

  Thanks.

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

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

[Desktop-packages] [Bug 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1

[Timo Aaltonen]

I don't have a silver bullet to fix this, but you can try
ppa:ubuntu-x-swat/updates which has mesa 19.1.4

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

Title:
  Kodi package crash after the update of libdrm-amdgpu1

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Greetings,

  The last update of libdrm-amdgpu1 caused a bug on Kodi package, making
  it to crash after loading any video or reproduce a black image.

  Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC

libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium

* Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111)

   -- Timo Aaltonen  Wed, 10 Apr 2019 13:54:06
  +0300

  
  Kodi gives this error:

  #3  0x7f47676c60aa in ?? () from 
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
  #4  0x7f47676c5dd7 in ?? () from 
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so

  Repeated several times

  #3  0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1
  #4  0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1

  Team-Kodi stated these errors are in relation to 'Not supported GPU
  drivers', when Kodi can't find these files.

  
  I've found the cause, and a temporary solution:

  This bug was caused after an update for the latest version of libdrm-
  amdgpu1 2.4.97-1ubuntu1~18.04.1

  So I grabbed the previous version from 
  https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/

  installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb

  and now Kodi returns.

  
  I created a bug report, the problem affects multiple users.

  https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828

  
  We have a PointRelease coming soon, would we have time to fix this package?

  Thank you for your assistance.

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

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

[Desktop-packages] [Bug 1087075] Re: Duplex options ignored for printing Postscript

[Launchpad Bug Tracker]

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

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

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

Title:
  Duplex options ignored for printing Postscript

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Printing a Postscript file using

  lp -o Duplex=DuplexNoTumble foo.ps

  does not give duplex output. I have read other bug reports, turned
  collation off  and I can't see anything else that might be causing
  the problem. Printing from the gtk print dialog, the duplex setting I
  choose is respected, but because of a font-related bug with gtkprint,
  I'm using the lp command directly to print my Postscript file.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11.3
  ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
  Uname: Linux 3.5.0-19-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Thu Dec  6 00:59:07 2012
  InstallationDate: Installed on 2011-10-14 (418 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  Lpstat: device for bunyan: dnssd://Lexmark%20X543._ipp._tcp.local/
  MachineType: Apple Inc. MacBookAir4,2
  MarkForUpload: True
  Papersize: a4
  PpdFiles: bunyan: Lexmark X543
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-19-generic 
root=UUID=3f1df709-5d4e-4a93-8844-6cf574c52f87 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-10-20 (46 days ago)
  dmi.bios.date: 06/30/2011
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA41.88Z.0077.B00.1106300929
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-742912EFDBEE19B3
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir4,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-742912EFDBEE19B3
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B00.1106300929:bd06/30/2011:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3:
  dmi.product.name: MacBookAir4,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Desktop-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace

[Shih-Yuan Lee]

** Changed in: oem-priority/bionic
   Status: New => In Progress

** Changed in: oem-priority/bionic
   Importance: Undecided => Critical

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

Title:
  KEY_RFKILL is not passed to userspace

Status in OEM Priority Project:
  New
Status in OEM Priority Project bionic series:
  In Progress
Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in xorgproto package in Ubuntu:
  Fix Released
Status in libxkbcommon source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in xkeyboard-config source package in Bionic:
  Fix Committed
Status in xorgproto source package in Bionic:
  Fix Released
Status in libxkbcommon source package in Cosmic:
  Fix Released
Status in xkeyboard-config source package in Cosmic:
  Fix Released
Status in xorgproto source package in Cosmic:
  Fix Released

Bug description:
  * Impact
  the airplane mode key doesn't work in GNOME

  * Test case
  Use a laptop with a key to activate airplane mode, it should toggle the 
corresponding mode on/off when used

  * Regression potential
  The change adds a new key definition but doesn't touch any existing one, 
nothing specific to test out of the new key working

  -

  There are a couple things going on, that could be fixed by a Debian or
  Ubuntu maintainer:

  - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This
  introduces the RFKill key: https://lists.freedesktop.org/archives
  /wayland-devel/2017-August/034721.html

  - x11-proto needs a new release. This commit added RFKill, but it is
  not in a release:
  
https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf

  - Likely other X11 packages need to be rebuilt.

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

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

[Desktop-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

[Taran M]

This bug and the fact that there seems to be no care in fixing it made
me leave the Ubuntu distro behind. Pathetic. I no longer care if you fix
it or not.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Won't Fix

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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

[Desktop-packages] [Bug 1788420] Re: Update to 2:10.78.05-0.1

[Sebastien Bacher]

That was discussed on IRC #debian-gnome, the update is currently only in
experimental because review of copyright/non free files included needs
to be done before uploading to unstable

** Tags added: version-blocked

** Summary changed:

- Update to 2:10.78.05-0.1
+ Don't update netpbm-free to 2:10.78.05-0.1 for now

** Description changed:

  The new version is in Debian/experimental but has a soname change and
  require a transition. Unless we find a good reason to want to it now
- that's probably not for cosmic
+ that's probably not for eoan

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

Title:
  Don't update netpbm-free to 2:10.78.05-0.1 for now

Status in netpbm-free package in Ubuntu:
  Triaged
Status in netpbm-free package in Debian:
  New
Status in netpbm-free package in Fedora:
  Fix Released

Bug description:
  The new version is in Debian/experimental but has a soname change and
  require a transition. Unless we find a good reason to want to it now
  that's probably not for eoan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netpbm-free/+bug/1788420/+subscriptions

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

[Desktop-packages] [Bug 1840890] [NEW] PKCS#7 signature not signed with a trusted key

[SunBear]

Public bug reported:

After making nvidia drivers available in Ubuntu 18.04 via Ubuntu's
StableReleaseUpdates (SRU), I expected that all the usual error and
warning messages reported by `dmesg -l err` and `dmes -l warn` before
the nvidia drivers's transition to SRU should no longer appear. However,
I still find them. See below.

$ dmesg -l err
[2.322549] PKCS#7 signature not signed with a trusted key
[2.438684] PKCS#7 signature not signed with a trusted key
[2.439332] PKCS#7 signature not signed with a trusted key
[2.439727] PKCS#7 signature not signed with a trusted key
[2.445846] PKCS#7 signature not signed with a trusted key
$ dmesg -l warn
[2.322558] nvidia: loading out-of-tree module taints kernel.
[2.322565] nvidia: module license 'NVIDIA' taints kernel.
[2.322566] Disabling lock debugging due to kernel taint
[2.433159] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  430.26  Tue Jun  
4 17:40:52 CDT 2019

Expected outcome: The above error and warning msgs should no longer show
in dmesg.


$ uname -a 
Linux Machine 5.0.0-25-generic #26~18.04.1-Ubuntu SMP Thu Aug 1 13:51:02 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

$ dpkg -l | grep nvidia
ii  libnvidia-cfg1-430:amd64   430.26-0ubuntu0.18.04.2  
amd64NVIDIA binary OpenGL/GLX configuration library
ii  libnvidia-common-430   430.40-0ubuntu0~gpu18.04.1   
all  Shared files used by the NVIDIA libraries
ii  libnvidia-compute-430:amd64430.26-0ubuntu0.18.04.2  
amd64NVIDIA libcompute package
ii  libnvidia-compute-430:i386 430.26-0ubuntu0.18.04.2  
i386 NVIDIA libcompute package
ii  libnvidia-decode-430:amd64 430.26-0ubuntu0.18.04.2  
amd64NVIDIA Video Decoding runtime libraries
ii  libnvidia-decode-430:i386  430.26-0ubuntu0.18.04.2  
i386 NVIDIA Video Decoding runtime libraries
ii  libnvidia-encode-430:amd64 430.26-0ubuntu0.18.04.2  
amd64NVENC Video Encoding runtime library
ii  libnvidia-encode-430:i386  430.26-0ubuntu0.18.04.2  
i386 NVENC Video Encoding runtime library
ii  libnvidia-fbc1-430:amd64   430.26-0ubuntu0.18.04.2  
amd64NVIDIA OpenGL-based Framebuffer Capture runtime library
ii  libnvidia-fbc1-430:i386430.26-0ubuntu0.18.04.2  
i386 NVIDIA OpenGL-based Framebuffer Capture runtime library
ii  libnvidia-gl-430:amd64 430.26-0ubuntu0.18.04.2  
amd64NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan 
ICD
ii  libnvidia-gl-430:i386  430.26-0ubuntu0.18.04.2  
i386 NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan 
ICD
ii  libnvidia-ifr1-430:amd64   430.26-0ubuntu0.18.04.2  
amd64NVIDIA OpenGL-based Inband Frame Readback runtime 
library
ii  libnvidia-ifr1-430:i386430.26-0ubuntu0.18.04.2  
i386 NVIDIA OpenGL-based Inband Frame Readback runtime 
library
ii  nvidia-compute-utils-430   430.26-0ubuntu0.18.04.2  
amd64NVIDIA compute utilities
ii  nvidia-dkms-430430.26-0ubuntu0.18.04.2  
amd64NVIDIA DKMS package
ii  nvidia-driver-430  430.26-0ubuntu0.18.04.2  
amd64NVIDIA driver metapackage
ii  nvidia-kernel-common-430   430.26-0ubuntu0.18.04.2  
amd64Shared files used with the kernel module
ii  nvidia-kernel-source-430   430.26-0ubuntu0.18.04.2  
amd64NVIDIA kernel source package
ii  nvidia-prime   0.8.8.2  
all  Tools to enable NVIDIA's Prime
ii  nvidia-settings390.77-0ubuntu0.18.04.1  
amd64Tool for configuring the NVIDIA graphics driver
ii  nvidia-utils-430   430.26-0ubuntu0.18.04.2  
amd64NVIDIA driver support binaries
ii  xserver-xorg-video-nvidia-430  430.26-0ubuntu0.18.04.2  
amd64NVIDIA binary Xorg driver

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

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

Title:
  PKCS#7 signature not signed with a trusted key

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

Bug description:
  After making 

[Desktop-packages] [Bug 1840396] Re: External display ports (connected to radeon GPU?) not detected

[Daniel van Vugt]

Looks like the radeon Xorg driver is in use too. Is that meant to happen
when we already have modesetting?

** Summary changed:

- do not display two screen 
+ External display ports (connected to radeon GPU?) not detected

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

** Summary changed:

- External display ports (connected to radeon GPU?) not detected
+ [Dell Inspiron 15-3567] External display ports (connected to radeon GPU?) not 
detected

** Tags added: amdgpu hybrid radeon

** Also affects: xserver-xorg-video-ati (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [Dell Inspiron 15-3567] External display ports (connected to radeon
  GPU?) not detected

Status in xorg-server package in Ubuntu:
  New
Status in xserver-xorg-video-ati package in Ubuntu:
  New

Bug description:
  maybe error drivers graphics for del

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.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: Fri Aug 16 08:50:25 2019
  DistUpgraded: 2019-06-26 14:49:28,001 ERROR Cache can not be locked (Can not 
lock '/var/lib/apt/lists/lock' )
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:078b]
 Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 
M520] [1028:078b]
  InstallationDate: Installed on 2019-06-25 (51 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. Inspiron 15-3567
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic 
root=UUID=981f9e6c-b414-4dbc-8a43-1e260574e929 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to disco on 2019-06-26 (50 days ago)
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.0.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.0.3:bd08/25/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078B
  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.8-0ubuntu0~19.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~19.04.1
  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/xorg-server/+bug/1840396/+subscriptions

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

[Desktop-packages] [Bug 1840875] Re: genaral Swap for errors

[Daniel van Vugt]

Please be careful to only report one problem per bug.

Which problem would you like this bug to be about, and can you please
provide more details about it?

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

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

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

Title:
  genaral Swap for errors

Status in Ubuntu:
  Incomplete

Bug description:
  I have problem with my snap packages
  I have problem with DPKG being not able to do upgrades
  I have problem with my Livepatch since I can't sign in to it

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-59.66-generic 4.15.18
  Uname: Linux 4.15.0-59-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Aug 21 07:24:59 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0597]
  MachineType: Dell Inc. Inspiron 3521
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-59-generic 
root=UUID=fbe95d05-80c6-41a8-9680-336df596acb7 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 033MX4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A02
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd09/26/2012:svnDellInc.:pnInspiron3521:pvrA02:rvnDellInc.:rn033MX4:rvrA00:cvnDellInc.:ct8:cvrA02:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Inspiron 3521
  dmi.product.version: A02
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1822351] Re: Nautilus does not open after updating to 19.04

[Julien Olivier]

Hi,

in case that helps, I have noticed that this bug is 100% reproducible
for me hen I try to start Nautilus right after booting my laptop. If,
however, I wait for a few minutes after booting, I can start Nautilus
without any delay.

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

Title:
  Nautilus does not open after updating to 19.04

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  After updating to Ubuntu 19.04 dev branch, nautilus does not open at
  all. Moreover, trying to open nautilus from the terminal does not give
  any error, nor any output at all, and no window opens.

  I don't really know how to report this bug without any terminal
  output.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.32.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 29 13:58:12 2019
  InstallationDate: Installed on 2018-02-23 (398 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1840397] Re: do not display two screen

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1840396
   do not display two screen

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

Title:
  do not display two screen

Status in xorg package in Ubuntu:
  New

Bug description:
  maybe error drivers graphics for del

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.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: Fri Aug 16 08:50:25 2019
  DistUpgraded: 2019-06-26 14:49:28,001 ERROR Cache can not be locked (Can not 
lock '/var/lib/apt/lists/lock' )
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:078b]
 Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 
M520] [1028:078b]
  InstallationDate: Installed on 2019-06-25 (51 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. Inspiron 15-3567
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic 
root=UUID=981f9e6c-b414-4dbc-8a43-1e260574e929 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to disco on 2019-06-26 (50 days ago)
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.0.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.0.3:bd08/25/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078B
  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.8-0ubuntu0~19.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~19.04.1
  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/xorg/+bug/1840397/+subscriptions

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